--QUESTO ARTICOLO E' ANCHE IN LINGUA ITALIANA!-- --QUESTO ARTICOLO E' ANCHE IN LINGUA ITALIANA!-- --QUESTO ARTICOLO E' ANCHE IN LINGUA ITALIANA!--
ENGLISH:
Download the Superboot image from here:
--> SuperBoot -768Mhz - Default Kernel (please use this non overclocked image if you are new to all this modding/flashing/rooting stuff)
--> SuperBoot Overclocked @880 Mhz
--> SuperBoot Overclocked @920Mhz (using phhusson kernel with ramzswap + TS fix + SVS)
- Download Android SDK --> http://developer.android.com/sdk/index.html
- Extract the Android SDK in C:\ (your path should look like this : C:\android-sdk-windows)
- Extract Vache's Superboot image in --> C:\android-sdk-windows\tools
- Connect your device to your PC (make sure Debug USB is activated on your phone <-- go to Settings/Applications/Development/USB Debugging)
- Open a Command Prompt (please use "Run as administrator" if you are on Win7) and type the following commands :
cd C:\android-sdk-windows\tools
adb reboot bootloader
fastboot -i 0x0502 flash boot bootxx-xxx.img (replace bootxx-xxx with the name of the image you are using)
fastboot -i 0x0502 reboot
That's it,if you did everything well your phone will reboot and will be rooted
----------------------------------------------------------------------------------
PER ITALIANI:
----------------------------------------------------------------------------------
Scaricare le Immagini superboot con kernel modificato e non , da questi siti:--> SuperBoot -768Mhz - Kernel Default (please use this non overclocked image if you are new to all this modding/flashing/rooting stuff)
--> SuperBoot Kernel Overcloccato a @880 Mhz
--> SuperBoot Kernel overcloccato a @920Mhz (uso del kernel di phhusson con ramzswap + TS fix + SVS CONSIGLIATO)
Scaricare Android sdk : http://developer.android.com/sdk/index.html
Estrarre android sdk in : C:\
Estratte Il kernel scaricato precedentamente in : C:\android-sdk-windows\tools
Collegare il dispositivo al pc ( Controllare di aver attivato la modalita' Debug USB nel telefono.. andare su Impostazioni / Applicazioni / Sviluppo/ Debug USB
Apri il Command Prompt (DOS) e digitare i seguenti commandi:
cd C:\android-sdk-windows\tools
adb reboot bootloader
fastboot -i 0x0502 flash boot bootxx-xxx.img (replace bootxx-xxx with the name of the image you are using)
fastboot -i 0x0502 reboot
Nice copy/paste from my Original Guide on Modaco Forums...thx for the credits and your hard work "paesà".
lorenzo.themax92 said:
--QUESTO ARTICOLO E' ANCHE IN LINGUA ITALIANA!-- --QUESTO ARTICOLO E' ANCHE IN LINGUA ITALIANA!-- --QUESTO ARTICOLO E' ANCHE IN LINGUA ITALIANA!--
Click to expand...
Click to collapse
Next time give proper credits to the guide's original author.
Where may I find Hong Kong version?
Acer_Liquid_1.001.05_AAP_CSL
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?
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:
hi all,
for the first time, i must restore a nandroid backup in my xiaomi mi a1.
when i restore it, it's go wrong because:
"
controllo sull'Digest in corso...
TWRP installer for Mi A1
unpacking the installer..
Running boot image patcher..
- Error: Unable to find boot block location!
- Aborting..
Failed to pacth boot image
il processo updater è terminato con errore: 1
errore durante l'installazione dello zip '/sdcard/pie/twrp-3.2.1.1-1-installer-tissot-FIXED_By_DroidMester.zip'
Aggiornamento dei dettagli della partizione...
Impossibile montare '/vendor' (invalid argoment).
...fatto
"
any solution?
what is /vendor error? i've never seen it.
tnx
Hello friends, I came here to ask a question, I updated my device with a stock rom (bootloader unlocked), I was using normal, so I accidentally installed an OTA update,
after that it is in an infinite loop, goes into fastboot mode (recognizes the device serial but cannot flash anything, also tried ROMs via flash (unsuccessful), tried also via qfil and also unsuccessfully said that I wanted to know if anyone you can give me some instructions or I killed my phone.
Thank you very much in advance
willamy.lemos said:
Hello friends, I came here to ask a question, I updated my device with a stock rom (bootloader unlocked), I was using normal, so I accidentally installed an OTA update,
after that it is in an infinite loop, goes into fastboot mode (recognizes the device serial but
cannot flash anything
, also tried ROMs via flash (unsuccessful), tried also via qfil and also unsuccessfully said that I wanted to know if anyone you can give me some instructions or I killed my phone.
Thank you very much in advance
Click to expand...
Click to collapse
Mod edit - translated by https://www.deepl.com/translator:
Hello friend, this problem of yours I believe you can solve with ADB Flash Tools. I am having a similar problem. recently my device turned off and didn't turn on again. It connects as Qualcomm 9008. But it shows the following error in QFIL:
21:32:36: {ERROR: Unable to write to 'COM4. \ COM4', Windows API WriteFile Failed! Your device is probably *not* on this port, tried 100 times}
Write record to 'C: \ Users \ Nizack \ AppData \ Roaming \ Qualcomm \ QFIL \ COMPORT_4 \ port_trace.txt' may take a minute
The log is 'C: \ Users \ Nizack \ AppData \ Roaming \ Qualcomm \ QFIL \ COMPORT_4 \ port_trace.txt'
Download failed: FireHose failed: FHLoader failed: Process failed
Could someone please help me?
Thank you for your attention.
******************************************************
Olá amigo, esse seu problema acredito que consiga resolver com o ADB Flash Tools. Eu estou com um problema parecido. recentemente meu aparelho desligou e não ligou mais. ELE Conecta Como Qualcomm 9008. Porem apresenta o Seguinte Erro no QFIL:
21:32:36: {ERRO: Não foi possível gravar em '\\. \ COM4', Falha de WriteFile da API do Windows! Seu dispositivo provavelmente * não * está nesta porta, tentadas 100 vezes}
Gravar o registro em 'C: \ Users \ Nizack \ AppData \ Roaming \ Qualcomm \ QFIL \ COMPORT_4 \ port_trace.txt' pode demorar um minuto
O log é 'C: \ Usuários \ Nizack \ AppData \ Roaming \ Qualcomm \ QFIL \ COMPORT_4 \ port_trace.txt'
Falha no download: Falha no FireHose: Falha no FHLoader: Falha no processo
Alguém poderia me ajudar?
Obrigado pela atenção.