 |
|
||
|
#181
24/05/12, 22:57:38
|
||||
|
||||
 Cita: Originalmente Escrito por Erathorn
Pues bienvenido!
Enviado desde mi GT-I9100 usando Tapatalk  PD: estas respondiendo a la gente desde el mismo movil o me lo parece a mi? 
|
|
|
|
#182
24/05/12, 23:21:56
|
||||
|
||||
|
Neo, me sale lo mismo de ayer. Carga algo llamado Daemon pero luego me dice que no encuentra el dispositivo. En el siguiente comando dice que no entiende lo que es "mount".
|
|
#183
24/05/12, 23:22:37
|
||||
|
||||
|
Cita: Originalmente Escrito por jorgesm89
Hilo mitico... espero que todo salga bien, sino ese movil debe estar en un museo.
PD: estas respondiendo a la gente desde el mismo movil o me lo parece a mi?
|
|
#184
24/05/12, 23:31:54
|
||||
|
||||
|
E leído algo de este hilo es increíble ver que uno quiere lo que otros tienen miedo.
Ya por darte una idea mas, as probado con el mobileodin flashear una rom del i9000, i9003.... Tambien restaurar un nandroid de uno de ellos? No se por probar.
__________________
|
|
#185
25/05/12, 00:28:51
|
||||
|
||||
|
erathorn, bajate el terminal emulator, version free, del google play alias market, jejeje, y sigue la secuencia de comandos que te comento neo, pero desde dentro del movil
si con esa lista de comandos, y desde el propio terminal, no lo fries, eso es que tienes algun circuito que esta rechazando cualquier modificacion un saludo 
|
| Gracias de parte de: | ||
|
#187
25/05/12, 04:32:51
|
||||
|
||||
|
Cita: Originalmente Escrito por Erathorn
Neo, me sale lo mismo de ayer. Carga algo llamado Daemon pero luego me dice que no encuentra el dispositivo. En el siguiente comando dice que no entiende lo que es "mount".
__________________
|
|
#188
25/05/12, 05:11:13
|
||||
|
||||
|
pero qué ignorantes sois todos....
(Click para mostrar/ocultar)
fuera de coñas, ya que están jodidas las Memorias, creo que lo correcto sería atacar al Hardware de manera silenciosa. una alta tensión estática cercana podría joderlo sin dejar rastro. imanes podrían ser otros grandes aliados, pero no se como actuarían estos con el terminal. freirlo con electricidad por dentro creo que sería demasiado evidente. suerte, y aqui uno que viene del foro del optimus black para observar el fenómeno. saludos! Enviado desde el Olimpo, a través de Zeus
__________________
|
|
#189
25/05/12, 10:53:15
|
||||
|
||||
|
Cita: Originalmente Escrito por rush3232
pero qué ignorantes sois todos....
(Click para mostrar/ocultar)
fuera de coñas, ya que están jodidas las Memorias, creo que lo correcto sería atacar al Hardware de manera silenciosa. una alta tensión estática cercana podría joderlo sin dejar rastro. imanes podrían ser otros grandes aliados, pero no se como actuarían estos con el terminal. freirlo con electricidad por dentro creo que sería demasiado evidente. suerte, y aqui uno que viene del foro del optimus black para observar el fenómeno. saludos! Enviado desde el Olimpo, a través de Zeus Enviado desde la Wildfire SE (Supervitaminada y embarazada de 3,5A)
|
|
#190
25/05/12, 11:12:23
|
||||
|
||||
|
Al final he podido meter todos los comandos pero no por recovery, ni por Terminal Emulator. Pero Obi-Wan me dio la idea y probé por SSHDroid.
El bicho se ha quedado con la pantalla apagada, los leds de los botones encendidos y no reacciona. No sé si quitarle la batería o dejarlo más tiempo.
|
|
#191
25/05/12, 11:15:33
|
||||
|
||||
|
Cita: Originalmente Escrito por Erathorn
Al final he podido meter todos los comandos pero no por recovery, ni por Terminal Emulator. Pero Obi-Wan me dio la idea y probé por SSHDroid.
El bicho se ha quedado con la pantalla apagada, los leds de los botones encendidos y no reacciona. No sé si quitarle la batería o dejarlo más tiempo. Y si flasheas normal ahora? Abrazos! Enviado desde la Wildfire SE (Supervitaminada y embarazada de 3,5A)
|
|
#193
25/05/12, 11:21:48
|
||||
|
||||
|
Aquí parte del log, ha ido borrando lo primero y esto es lo que ha quedado.
Pass 2: Checking directory structure Pass 3: Checking directory connectivity /lost+found not found. Create? yes Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/block/mmcblk0p12: ***** FILE SYSTEM WAS MODIFIED ***** 14 inodes used (0.04%) 0 non-contiguous files (0.0%) 0 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 0/0/0 Extent depth histogram: 5 5511 blocks used (4.20%) 0 bad blocks 0 large files 2 regular files 2 directories 0 character device files 0 block device files 0 fifos 0 links 0 symbolic links (0 fast symbolic links) 0 sockets -------- 4 files # e2fsck -yfv /dev/block/mmcblk0 e2fsck 1.41.11 (14-Mar-2010) ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0 is mounted. e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0 Filesystem mounted or opened exclusively by another program? # e2fsck -yfv /dev/block/mmcblk1 e2fsck 1.41.11 (14-Mar-2010) ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk1 is mounted. e2fsck: Superblock invalid, trying backup blocks... e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk1 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -p /dev/block/mmcblk0boot0 ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0boot0 is mounted. e2fsck: No such file or directory while trying to open /dev/block/mmcblk0boot0 /dev/block/mmcblk0boot0: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -p /dev/block/mmcblk0boot1 ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0boot1 is mounted. e2fsck: No such file or directory while trying to open /dev/block/mmcblk0boot1 /dev/block/mmcblk0boot1: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -p /dev/block/mmcblk0p11 ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0p11 is mounted. e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p11 /dev/block/mmcblk0p11: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -p /dev/block/mmcblk0p2 ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0p2 is mounted. e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p2 /dev/block/mmcblk0p2: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -p /dev/block/mmcblk0p3 ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0p3 is mounted. e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p3 /dev/block/mmcblk0p3: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -p /dev/block/mmcblk0p6 ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0p6 is mounted. e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p6 /dev/block/mmcblk0p6: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -p /dev/block/mmcblk1p1 ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk1p1 is mounted. e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk1p1 /dev/block/mmcblk1p1: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -yfv /dev/block/mmcblk0boot0 e2fsck 1.41.11 (14-Mar-2010) ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0boot0 is mounted. e2fsck: No such file or directory while trying to open /dev/block/mmcblk0boot0 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -yfv /dev/block/mmcblk0boot1 e2fsck 1.41.11 (14-Mar-2010) ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0boot1 is mounted. e2fsck: No such file or directory while trying to open /dev/block/mmcblk0boot1 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -yfv /dev/block/mmcblk0p11 e2fsck 1.41.11 (14-Mar-2010) ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0p11 is mounted. e2fsck: Superblock invalid, trying backup blocks... e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p11 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -yfv /dev/block/mmcblk0p2 e2fsck 1.41.11 (14-Mar-2010) ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0p2 is mounted. e2fsck: Superblock invalid, trying backup blocks... e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p2 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -yfv /dev/block/mmcblk0p3 e2fsck 1.41.11 (14-Mar-2010) ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0p3 is mounted. e2fsck: Superblock invalid, trying backup blocks... e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p3 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -yfv /dev/block/mmcblk0p6 e2fsck 1.41.11 (14-Mar-2010) ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0p6 is mounted. e2fsck: Superblock invalid, trying backup blocks... e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p6 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -yfv /dev/block/mmcblk1p1 e2fsck 1.41.11 (14-Mar-2010) ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk1p1 is mounted. e2fsck: Superblock invalid, trying backup blocks... e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk1p1 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> #
|
| Gracias de parte de: | ||
|
#194
25/05/12, 11:26:23
|
||||
|
||||
|
Cita: Originalmente Escrito por Erathorn
¡Y renace de sus cenizas! Ha sido quitarle la batería, ponérsela y ahí está otra vez dando por culo.
Abrazos. Enviado desde la Wildfire SE (Supervitaminada y embarazada de 3,5A)
|
|
#195
25/05/12, 11:38:45
|
||||
|
||||
|
Digo yo, ¿por qué no mandas el teléfono al CERN y que lo metan en alguno de los túneles del acelerador de partículas a ver qué pasa? Lo malo es que en vez de romperse el teléfono se rompiera el acelerador y te pasen la factura (por lo visto es carillo), pero bueno, por intentarlo...
|
|
#196
25/05/12, 11:43:02
|
||||
|
||||
|
Cita: Originalmente Escrito por Erathorn
Aquí parte del log, ha ido borrando lo primero y esto es lo que ha quedado.
Pass 2: Checking directory structure Pass 3: Checking directory connectivity /lost+found not found. Create? yes Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/block/mmcblk0p12: ***** FILE SYSTEM WAS MODIFIED ***** 14 inodes used (0.04%) 0 non-contiguous files (0.0%) 0 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 0/0/0 Extent depth histogram: 5 5511 blocks used (4.20%) 0 bad blocks 0 large files 2 regular files 2 directories 0 character device files 0 block device files 0 fifos 0 links 0 symbolic links (0 fast symbolic links) 0 sockets -------- 4 files # e2fsck -yfv /dev/block/mmcblk0 e2fsck 1.41.11 (14-Mar-2010) ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0 is mounted. e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0 Filesystem mounted or opened exclusively by another program? # e2fsck -yfv /dev/block/mmcblk1 e2fsck 1.41.11 (14-Mar-2010) ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk1 is mounted. e2fsck: Superblock invalid, trying backup blocks... e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk1 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -p /dev/block/mmcblk0boot0 ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0boot0 is mounted. e2fsck: No such file or directory while trying to open /dev/block/mmcblk0boot0 /dev/block/mmcblk0boot0: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -p /dev/block/mmcblk0boot1 ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0boot1 is mounted. e2fsck: No such file or directory while trying to open /dev/block/mmcblk0boot1 /dev/block/mmcblk0boot1: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -p /dev/block/mmcblk0p11 ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0p11 is mounted. e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p11 /dev/block/mmcblk0p11: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -p /dev/block/mmcblk0p2 ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0p2 is mounted. e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p2 /dev/block/mmcblk0p2: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -p /dev/block/mmcblk0p3 ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0p3 is mounted. e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p3 /dev/block/mmcblk0p3: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -p /dev/block/mmcblk0p6 ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0p6 is mounted. e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p6 /dev/block/mmcblk0p6: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -p /dev/block/mmcblk1p1 ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk1p1 is mounted. e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk1p1 /dev/block/mmcblk1p1: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -yfv /dev/block/mmcblk0boot0 e2fsck 1.41.11 (14-Mar-2010) ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0boot0 is mounted. e2fsck: No such file or directory while trying to open /dev/block/mmcblk0boot0 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -yfv /dev/block/mmcblk0boot1 e2fsck 1.41.11 (14-Mar-2010) ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0boot1 is mounted. e2fsck: No such file or directory while trying to open /dev/block/mmcblk0boot1 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -yfv /dev/block/mmcblk0p11 e2fsck 1.41.11 (14-Mar-2010) ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0p11 is mounted. e2fsck: Superblock invalid, trying backup blocks... e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p11 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -yfv /dev/block/mmcblk0p2 e2fsck 1.41.11 (14-Mar-2010) ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0p2 is mounted. e2fsck: Superblock invalid, trying backup blocks... e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p2 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -yfv /dev/block/mmcblk0p3 e2fsck 1.41.11 (14-Mar-2010) ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0p3 is mounted. e2fsck: Superblock invalid, trying backup blocks... e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p3 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -yfv /dev/block/mmcblk0p6 e2fsck 1.41.11 (14-Mar-2010) ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0p6 is mounted. e2fsck: Superblock invalid, trying backup blocks... e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p6 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # e2fsck -yfv /dev/block/mmcblk1p1 e2fsck 1.41.11 (14-Mar-2010) ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk1p1 is mounted. e2fsck: Superblock invalid, trying backup blocks... e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk1p1 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> # eso si, tienes que intentar meterlos desde el recovery, con busybox umount etc, porque sino te va a dar todas las particiones como montadsa y a la hora de desmontarlas te va a decir que estan "ocupadas" y no te las va a desmontar.
__________________
Última edición por NeoPhyTe Día 25/05/12 a las 11:46:14.
|
|
#197
30/05/12, 22:56:53
|
||||
|
||||
|
Estoy igual que tu, desesperado, alguna solucion?
|
|
#198
30/05/12, 23:37:48
|
||||
|
||||
|
Yo lo único que no entiendo es para que enviarlo al sat si funciona todo, brickeandolo conseguirás estar más de un mes sin móvil y te lo devolverán con una placa nueva, ya que el móvil al completo no lo cambian en estos casos.
|
|
#199
30/05/12, 23:44:38
|
||||
|
||||
|
Cita: Originalmente Escrito por Warlock7
Yo lo único que no entiendo es para que enviarlo al sat si funciona todo, brickeandolo conseguirás estar más de un mes sin móvil y te lo devolverán con una placa nueva, ya que el móvil al completo no lo cambian en estos casos.
|
|
|
|
#200
30/05/12, 23:54:40
|
||||
|
||||
|
No me he leido todas las paginas pero ¿ya has probado a hacer un format system y flashear una rom de SGS?
|
 |
Estás aquí
|
||||||
|
||||||
![Array
[xs_avatar]](https://avatar.htcmania.com/avatares/avatar650709_1.gif){kind=avatar}
![Array
[xs_avatar]](https://avatar.htcmania.com/avatares/avatar341436_5.gif){kind=avatar}
![Array
[xs_avatar]](https://avatar.htcmania.com/avatares/avatar602192_3.gif){kind=avatar}
![Array
[xs_avatar]](https://avatar.htcmania.com/avatares/unknown.gif)
![Array
[xs_avatar]](https://avatar.htcmania.com/avatares/avatar176622_12.gif){kind=avatar}
#NeoPhyTe_x360![Array
[xs_avatar]](https://avatar.htcmania.com/avatares/avatar798278_1.gif){kind=avatar}
![Array
[xs_avatar]](https://avatar.htcmania.com/avatares/avatar474311_2.gif){kind=avatar}
![Array
[xs_avatar]](https://avatar.htcmania.com/avatares/avatar523281_1.gif){kind=avatar}
![Array
[xs_avatar]](https://avatar.htcmania.com/avatares/avatar527242_4.gif){kind=avatar}