Hola buen día.
Tengo un Nexus S que hace 2 meses le puse una rom de CyanogenMod y después de una semana se me apago lo puse a cargar (cargador de pared) cuando lo prendí se quedo en la pantalla de inicio donde dice "Google" y ya no continuo, le quite la pila y en seguida se la puse y ya no prendió.
Estoy en México y no he encontrado nadie que lo pueda arreglar, hace 15 días lo intente prender y prendió de nuevo hasta la misma pantalla de "Google" y lo conecte a la pc y con el comando "adb devices" me listo el dispositivo después intente correr el comando "abd shell" y me dijo que no encontraba el archivo después use "adb reboot bootloader" el telefono se reinicio y no volvió a prender hasta hoy en la mañana que lo intente de nuevo use "vol up + power" y entro al recovery.
Pensé en recargarle el recovery.img que esta en este sitio
theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s
megaupload.com/?d=C933QJOO
usando "fastboot flash recovery recovery.img" cargue de nuevo el recovery.img el proceso se completo sin problema, pero cuando seleccione la opción "Recovery" el telefono se reinicio y no volvió a prender lo intente prender de nuevo con "vol up + power", "power", "vol down + power" y no prendió ahora esperare unos días para que prenda.
La pregunta es
Lo podré recuperar?
Puedo instalar otra rom estando en fasboot?
Cada vez que se apaga se bloquea por algún fallo de Hardware?
espero me puedan ayudar.
si alguien me puede dar un tip de como buscar este problema en la red por que no he encontrado nada parecido.
Saludos y gracias.
primero que todo, aquí en XDA solamente se postea en ingles
si no sabes ingles usa google translate, y le hace la copy y paste, para que te lo traduzca todo
este es tu primer aviso, si te encuentro de nuevo posteando sin traducción a ingles recibirás una multa
re: tema sobre su dead NS
ese es un caso conocido con unas cuantas versiones de CM7
la versión mas estable es CM7 RC1, las otras versiones como te has dado cuenta no funciona tan bien.
en cuando a su ROM que esta jodido, la mejor manera seria de usar ODIN con el USB jig, y luego flashear el stock ODIN ROM de la NS
después de eso tu Tele debería de reiniciar correctamente para el OS
tengo ladilla de traducir todo lo que tipee así que voy a usar google translate como te aconseje
english translation **************************************************
first of all, here at XDA is posted in English only
if you can not use google translate English, and makes the copy and paste [/ I], to translate it for you all
this is your first warning, if you encounter a new English translation by posting without receive a fine
re: your dead topic NS
this is a known case with a few versions of CM7
more stable version RC1 CM7, other versions as you noticed does not work so well.
when his ROM in this ****ed up, the best way would be to use the USB ODIN jig, and then flash the stock ROM NS ODIN
after that restart your Tele should correctly for the OS
crab I have to translate everything you type so I'll use google translate and advise you
LMAO google translate has horrible grammar
anyways... we had our fun, no lets get back on topic
I had another phone (a LG GW620) to the one I charged ROMs through fastboot using "fastboot flash boot boot.img" and "fastboot flash system system.img", where "boot.img" and "system.img" were images that I had stored in the same folder as the fastboot executable. I think that for the Nexus S it's the same, but I HAVE'NT TRYED IT.
Before that commands, I remember that I have to use some other command to wipe the phone via fastboot, but I can't remember what it was.
You can find System and Boot images in the Backup folder made by ClockworkMod Recovery.
I hope I've helped you =)
********************
Tuve otro telefono (un LG GW620) al que le cargaba las rom mediante fastboot con los comandos "fastboot flash boot boot.img" y "fastboot flash system system.img", donde "boot.img" y "system.img" eran imagenes de boot y sistema que tenía en la misma carpeta donde estaba el programa de fastboot. Imagino que para el Nexus S es lo mismo, PERO NO LO HE PROBADO. Antes de eso habia que hacer un wipe mediante fastboot, pero no recuerdo cuál era el comando. Puedes obtener imagenes de boot y system de algun respaldo hecho con ClockWorkMod Recovery.
Espero haber ayudado.
Saludos,
t3b4n
I have no idea what's going on here, even with the translation.
sorry
Sorry, i did not think was very important.
I used JIG on the nexus s, and I can turn the phone into recovery mode but can not find partition to install the system.
Odin is also when you are installing your system I guess it's the same thing.
any idea???
no, you need to use the JIG to boot into the Download Mode, not recovery mod
in Download Mode, unplug, then re-plug the USB back into the phone
then Odin will see the phone, and you can flash the stock ROM
yes, use ODIN in mode download (use JIG) but the process not complete, don't load system.img
check out this http://forum.xda-developers.com/showthread.php?t=1397393
Status:
Nexus S turn on in recovery mode and download mode but in download mode ODIN3 (1.81) no complete the process (on 10 hrs).
Code:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> bootloader.img
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
In recovery mode dont load system.img
In recovery mode
Code:
$ fastboot erase boot
erasing 'boot'... OKAY
$ fastboot erase system
erasing 'system'... OKAY
$ adb shell
/proc # ls -l /dev/block/
brw------- 1 root root 7, 0 Jan 1 12:00 loop0
brw------- 1 root root 7, 1 Jan 1 12:00 loop1
brw------- 1 root root 7, 2 Jan 1 12:00 loop2
brw------- 1 root root 7, 3 Jan 1 12:00 loop3
brw------- 1 root root 7, 4 Jan 1 12:00 loop4
brw------- 1 root root 7, 5 Jan 1 12:00 loop5
brw------- 1 root root 7, 6 Jan 1 12:00 loop6
brw------- 1 root root 7, 7 Jan 1 12:00 loop7
brw------- 1 root root 31, 0 Jan 1 12:00 mtdblock0
brw------- 1 root root 31, 1 Jan 1 12:00 mtdblock1
brw------- 1 root root 31, 2 Jan 1 12:00 mtdblock2
brw------- 1 root root 31, 3 Jan 1 12:00 mtdblock3
brw------- 1 root root 31, 4 Jan 1 12:00 mtdblock4
brw-rw---- 1 radio radio 31, 5 Jan 1 12:00 mtdblock5
brw------- 1 root root 31, 6 Jan 1 12:00 mtdblock6
drwxr-xr-x 3 root root 60 Jan 1 12:00 platform
brw------- 1 root root 1, 0 Jan 1 12:00 ram0
brw------- 1 root root 1, 1 Jan 1 12:00 ram1
brw------- 1 root root 1, 10 Jan 1 12:00 ram10
brw------- 1 root root 1, 11 Jan 1 12:00 ram11
brw------- 1 root root 1, 12 Jan 1 12:00 ram12
brw------- 1 root root 1, 13 Jan 1 12:00 ram13
brw------- 1 root root 1, 14 Jan 1 12:00 ram14
brw------- 1 root root 1, 15 Jan 1 12:00 ram15
brw------- 1 root root 1, 2 Jan 1 12:00 ram2
brw------- 1 root root 1, 3 Jan 1 12:00 ram3
brw------- 1 root root 1, 4 Jan 1 12:00 ram4
brw------- 1 root root 1, 5 Jan 1 12:00 ram5
brw------- 1 root root 1, 6 Jan 1 12:00 ram6
brw------- 1 root root 1, 7 Jan 1 12:00 ram7
brw------- 1 root root 1, 8 Jan 1 12:00 ram8
brw------- 1 root root 1, 9 Jan 1 12:00 ram9
/dev/block/platform # ls -la
drwxr-xr-x 3 root root 60 Jan 1 12:00 .
drwxr-xr-x 3 root root 680 Jan 1 12:00 ..
drwxr-xr-x 2 root root 180 Jan 1 12:00 s5pc110-onenand
/dev/block/platform/s5pc110-onenand # ls -l
lrwxrwxrwx 1 root root 20 Jan 1 12:00 mtdblock0 -> /dev/block/mtdblock0
lrwxrwxrwx 1 root root 20 Jan 1 12:00 mtdblock1 -> /dev/block/mtdblock1
lrwxrwxrwx 1 root root 20 Jan 1 12:00 mtdblock2 -> /dev/block/mtdblock2
lrwxrwxrwx 1 root root 20 Jan 1 12:00 mtdblock3 -> /dev/block/mtdblock3
lrwxrwxrwx 1 root root 20 Jan 1 12:00 mtdblock4 -> /dev/block/mtdblock4
lrwxrwxrwx 1 root root 20 Jan 1 12:00 mtdblock5 -> /dev/block/mtdblock5
lrwxrwxrwx 1 root root 20 Jan 1 12:00 mtdblock6 -> /dev/block/mtdblock6
~ # cat /proc/mtd
dev: size erasesize name
mtd0: 00200000 00040000 "bootloader"
mtd1: 00140000 00040000 "misc"
mtd2: 00800000 00040000 "boot"
mtd3: 00800000 00040000 "recovery"
mtd4: 1d580000 00040000 "cache"
mtd5: 00d80000 00040000 "radio"
mtd6: 006c0000 00040000 "efs"
"system" not found.
more info:
~ # dmesg | grep mmc
<6>[ 0.000000] sclk_mmc: source is mout_mpll (6), rate is 51307692
<6>[ 0.000000] sclk_mmc: source is mout_mpll (6), rate is 47642857
<6>[ 0.000000] sclk_mmc: source is mout_mpll (6), rate is 47642857
<6>[ 0.000000] sclk_mmc: source is mout_mpll (6), rate is 47642857
<6>[ 2.606926] s3c-sdhci s3c-sdhci.0: clock source 0: hsmmc (133400000 Hz)
<6>[ 2.607043] s3c-sdhci s3c-sdhci.0: clock source 1: hsmmc (133400000 Hz)
<6>[ 2.607248] s3c-sdhci s3c-sdhci.0: clock source 2: sclk_mmc (51307692 Hz)
<6>[ 2.607575] mmc0: SDHCI controller on samsung-hsmmc [s3c-sdhci.0] using ADMA
<6>[ 2.607813] s3c-sdhci s3c-sdhci.2: clock source 0: hsmmc (133400000 Hz)
<6>[ 2.608015] s3c-sdhci s3c-sdhci.2: clock source 1: hsmmc (133400000 Hz)
<6>[ 2.608135] s3c-sdhci s3c-sdhci.2: clock source 2: sclk_mmc (47642857 Hz)
<6>[ 2.608735] mmc1: SDHCI controller on samsung-hsmmc [s3c-sdhci.2] using ADMA
<6>[ 2.608940] s3c-sdhci s3c-sdhci.3: clock source 0: hsmmc (133400000 Hz)
<6>[ 2.609141] s3c-sdhci s3c-sdhci.3: clock source 1: hsmmc (133400000 Hz)
<6>[ 2.609259] s3c-sdhci s3c-sdhci.3: clock source 2: sclk_mmc (47642857 Hz)
<6>[ 2.609555] mmc2: SDHCI controller on samsung-hsmmc [s3c-sdhci.3] using ADMA
<3>[ 4.240377] mmc0: error -110 whilst initialising MMC card
Error: mmc0: error -110 whilst initialising MMC card
no mount the mmc card
any idea?
Sorry for the post in spanish,
cambie de rom, en mi telefono y resulta que ahora, no me guarda niunguna configuracion, al reinicar el telefono, queda como de 0, no me guarda absolutamete nada, creo q meti la pata, intente hacer todos los wipe y etc etc, del custom recovery, del "stock recovery, creo que se le dice...
si alguien me dice que tan grande meti la pata
otra cosa, me aparecen ls errores .
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
first, write in english, second, flash the stock froyo sbf via rsd lite
Bonjour,
J'ai un Motorola Defy + avec carte SD 8G , j'ai rooter le téléphone et vérifie avec application( howtoroot).
je voudrais changer la Rom de mon téléphone, mais je n'y arrive pas.
Je lance le téléphone en boot log (avec rom manager 5.5.3.7, batterie charge ) ,
il redémarre page boot log , => j’appuie sur [- et +]
je vais sur apply update for SDcarde
et il me met message d'erreur
"E:failed to verify whole-file signatuture
E : Signature verification failed"
quelqu'un aurais une idée ?
Hello,
I have a Motorola Defy + with 8G SD card, I rooter and checks with the phone application (howtoroot).
I want to change my phone's ROM, but I can not.
I throw the phone in boot log (rom manager with 5.5.3.7, battery charging)
it restarts page boot log, => I press [- or +]
I go to apply update for SDcarde
and it puts me error
"E: failed to verify whole-file signatuture
E: Signature verification failed "
someone would have an idea?
1) baixe o WPinternals 2.4 e o Windows Device Recovery Tool
2) Instale o Windows Device Recovery Tool.
3) Abra o WPinternals 2.4 na area de trabalho ( ele é auto executavel),em platform clique em download.
agora em producttype digite o modelo do lumia o meu é :RM-1116 e em productcode digite o do seu aparelho
(basta abrir a tampa do celular e lá vc encontrará qual será o modelo e o codigo o meu é:059X5B5)
clique em search e faça o download.
4) Após o download Vá até disco local C: e habilite o modo de exibição das pastas ocultas.
Vá até C:\ProgramData\WPInternals\Repository\RM-1116 e copie os
arquivos de emergencia: RM1116_fh.edp e o MPRG8994_fh.ede (lembrando que vai depender do modelo do seu celular ok.
5) cole os arquivos na pasta C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool.
conecte o seu lumia no pc via usb e segure o botão power até vc ouvir o barulho no pc (nada irá acontecer com seu aparelho).
6) Agora,Vamos abrir o CMD que ficará assim C:\WINDOWS\system32
Então iremos digitar com aspas:
cd "C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool"
Clique enter e digite sem aspas:
thor2 -mode emergency -hexfile MPRG8994_fh.ede -edfile RM1116_fh.edp -orig_gpt
aguarde todo o processo......
ao final aparecerá esta mensagem no CMD
Clearing the backup GPT...SKIPPED!
Unable to parse FFU file. File open failed
programming operation failed!
UEFI FLASH END
Operation took about 24.00 seconds.
FFU_PARSING_ERROR
THOR2 1.8.2.18 exited with error code 2228224 (0x220000)
C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool>
O seu lumia ficará com a tela vermelha mostrando o modo recovery(as duas flechas se encontrando).Feche o CMD vamos para o proximo passo.
7) Abra o WPinternals 2.4 e clique em Flash do lado direito escolha a opção Flash original FFU
e clique em FFU escolha a rom que baixou e clique em FlashFFU image.
Aguarde todo o processo e pronto, seu aparelho ressuscitou!:legal:
Eu apaguei o celular pelo twrp e fui instalar o twrp atualizado nisso meu leeco le 2 x522, fico sem twrp porquê deu bug.
Ai eu fui volta com o twrp antigo não deu certo, da false para o desbloqueio do bootloader.
Vou deixa os comandos pra vocês verem e me ajudarem só agradeço pela atenção de vocês.
COMO EU DESBLOQUEIO O BOOTLOADER??
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
7e60b741 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device product name: [s2_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.010s]
finished. total time: 0.010s
C:\Program Files (x86)\Minimal ADB and Fastboot>
COMO EU DESBLOQUEIO O BOOTLOADER??
Click to expand...
Click to collapse
1. Enable developer options:
In Settings go to 'About Device' and click 7 x on 'Build Number'. New settings menu 'Developer Options' appears in Settings.
2. Allow OEM Unlock:
Go to 'Developer Options' and check 'Enable OEM Unlock' and 'Enable USB Debugging'