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:
Related
To Synchronize through ActiveSync and Server
===================================
En el registro y en la siguiente clave,
HKLM - System - Inbox
debemos tener lo siguiente en las claves
a) Attachments
AttsDir ------------------- Inbox.mst29915526.3837362304
BottomDir------------------ Mail Attachments
b) Settings
AttachPath \SD Card\Inbox.mst29915526.3837362304\Mail Attachments
PropertyPath \SD Card\Inbox.mst29915526.3837362304
--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
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
Español
Buenas tardes, tengo el siguiente problema:
El dia de ayer reinicie mi telefono de forma habitual, como en veces anteriores, pero esta vez se quedo en la imagen de ASUS (Loader).
He intentado actualizarlo por ADB y me dice que no tengo permisos para flashear, intente actualizarlo por SD y tampoco me deja, dice que la Firma es Invalida..
Mi telefono es un Ze551KL.. ¿Que puedo hacer? que me aconsejan..
English
Good afternoon , I have the following problem:Yesterday restart my phone frequently, such as in times past , but this time stayed in the image ASUS ( Loader) .I tried to update it by ADB and tells me I do not have permissions to flash, try upgrading by SD and not let me, he says the firm is Overrides ..My phone is a Ze551KL .. What can I do ? What do you advise me.. :crying::crying::crying::crying::crying::crying:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (29420 KB)...
OKAY [ 1.195s]
writing 'recovery'...
FAILED (remote: Permission denied, phone is protected)
finished. total time: 1.217s
C:\adb>fastboot oem device-info
...
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.021s]
finished. total time: 0.024s
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.