My Moto G bootloader (v41.13 from 4.4.4 upgrade) is corrupted and the device is recognized by computer as "qhsusb_bulk". So I installed Riffbox JTAG drivers and now it's recognized as "Qualcomm HS-USB QDLoader 9008". I tried to run many times the flashblank tool but I keep getting errors. This is what I get:
Code:
C:\qualcomm_boot_tool>.\qboot.exe blank-flash
opening device: \\.\COM19
OKAY [ -0.000s]
greeting device for command mode
OKAY [ -0.000s]
identifying device
...serial = 0x3B93E14
...chip-id = 0x800 (MSM8226)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.010s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.010s]
validating files
OKAY [ -0.000s]
switching to download mode
OKAY [ -0.000s]
greeting device for image downloading
OKAY [ -0.000s]
sending programmer
OKAY [ 0.010s]
flashing singleimage
[B]FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)[/B]
or:
Code:
C:\qualcomm_boot_tool>.\qboot.exe blank-flash
opening device: \\.\COM19
OKAY [ 0.010s]
greeting device for command mode
OKAY [ 0.000s]
identifying device
...serial = 0x3B93E14
...chip-id = 0x800 (MSM8226)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.010s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.010s]
validating files
OKAY [ 0.000s]
switching to download mode
OKAY [ 0.010s]
greeting device for image downloading
OKAY [ 0.000s]
sending programmer
OKAY [ 0.010s]
flashing singleimage
[B]FAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet)[/B]
debug log:
Code:
I - opening device: \\.\COM16
D - \\.\COM16 opened
I - OKAY [ 0.004s]
I - greeting device for command mode
D - Receiving HELLO packet
D - TARGET PROTOCOL INFO:
D - name: sahara
D - version: 2
D - compatible version: 1
D - maximum packet length: 1024
D - mode: Image transfer pending
D - Switching to "Command" mode
D - Sending HELLO_RESP packet
D - Receiving COMMAND_READY packet
I - OKAY [ 0.026s]
I - identifying device
D - Reading device serial number
D - Sending CMD_EXEC packet, cmd=1
D - Receiving CMD_EXEC_RESP packet
D - Reading device id
D - Sending CMD_EXEC packet, cmd=2
D - Receiving CMD_EXEC_RESP packet
D - Reading SBL SV
D - Sending CMD_EXEC packet, cmd=7
D - Receiving CMD_EXEC_RESP packet
I - ...serial = 0x3B93E14
I - ...chip-id = 0x800 (MSM8226)
I - ...chip-rev = 0x0
I - ...sv-sbl = 0x0
I - OKAY [ 0.043s]
I - finding files
I - ...programmer = programmer.mbn
I - ...singleimage = singleimage.bin
I - OKAY [ 0.020s]
I - validating files
I - OKAY [ 0.003s]
I - switching to download mode
D - Sending CMD_SWITCH_MODE packet
I - OKAY [ 0.005s]
I - greeting device for image downloading
D - Receiving HELLO packet
D - TARGET PROTOCOL INFO:
D - name: sahara
D - version: 2
D - compatible version: 1
D - maximum packet length: 1024
D - mode: Image transfer pending
D - Sending HELLO_RESP packet
I - OKAY [ 0.031s]
I - sending programmer
D - Loading file: programmer.mbn
D - Receiving READ_DATA packet
D - Sending 80 bytes
D - Receiving READ_DATA packet
D - Sending 4096 bytes
D - Receiving READ_DATA packet
D - Sending 4096 bytes
D - Receiving READ_DATA packet
D - Sending 4096 bytes
D - Receiving READ_DATA packet
D - Sending 4096 bytes
D - Receiving READ_DATA packet
D - Sending 4096 bytes
D - Receiving READ_DATA packet
D - Sending 4096 bytes
D - Receiving READ_DATA packet
D - Sending 4096 bytes
D - Receiving READ_DATA packet
D - Sending 4096 bytes
D - Receiving READ_DATA packet
D - Sending 4096 bytes
D - Receiving READ_DATA packet
D - Sending 4096 bytes
D - Receiving READ_DATA packet
D - Sending 4096 bytes
D - Receiving READ_DATA packet
D - Sending 3452 bytes
D - Receiving END_IMAGE_TX packet
D - Sending DONE packet
D - Receiving DONE_RESP packet
I - OKAY [ 0.070s]
I - flashing singleimage
D - Loading file: singleimage.bin
D - Pinging RDL...
D - \\.\COM16 closed
FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
Any developer can help me to figure out how to fix this?
I have the same problem.
I see from your signature that the device was upgraded to 4.4.4 like mine. I understand the 4.4.4 upgrade repartitions the phone, perhaps this also changes the bootloader section so that blank-flash tool does not have the correct file to flash?
If so, hopefully a new file will become available.
I'd like to ask the question in the thread for the blank-flash tool but don't have enough posts yet to to do so.
I have this too it happened after i tried to flash gpe firmware possibly 4.4.4 (dont know) and tried bootloader corrupter to try to downgrade the bootloader but then got this currently cant do anything.
Yeah probably the tool doesn't work due to 4.4.4 upgrade, maybe the boot partition needs to be repartitioned or something like that, in order to flash singleimage.bin.
I'm pretty sure there is (or there will be) a way to unbrick our device. The flash-blank tool I used comes from 4.3 JellyBean tar.gz official firmware, if our argument is right we need a 4.4.4 tar.gz package to extract a working flash-blank tool, but I never saw a tar.gz firmware after 4.3... I also thought to try with the factory cable but probably nothing would change unless you bricked with low battery (mine was around 50%). A lot of people bricked and got that kind of error so I'm sure a solution is coming. Let's wait for a fix, maybe Boss442 can help us as well.:good:
my xt1033 brinked on bootloader 41.11
fastboot dont write nothing on then..
i recive OK feedback, but nothing change..
i try use another versions but i recive 'downgrade' msg's
where is the 41.13 image?,
think i will can instal it in my device, because is a upgrade..
maybe work.
i put various logs about this on my thread
see: http://forum.xda-developers.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228
hansdepaula said:
my xt1033 brinked on bootloader 41.11
fastboot dont write nothing on then..
i recive OK feedback, but nothing change..
i try use another versions but i recive 'downgrade' msg's
where is the 41.13 image?,
think i will can instal it in my device, because is a upgrade..
maybe work.
i put various logs about this on my thread
see: http://forum.xda-developers.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228
Click to expand...
Click to collapse
Wrong thread, here we discuss about hard brick, you soft bricked. I think you just need to pick up the motoboot.img from a 4.4.4 firmware to get the 41.13 bootloader.
no man, my bootloader as corrupted..
this dont write nothing on my phone..
my partition is all 'RAW' system..
i try flash 4.4.4 files taked on OTA, not work..
nothing change..
i cant enter in recovery or anything, only bootloader..
we are together on bricked..
hard or soft i d'nt know but my (and your?) device stay unusable. :/
if you have time to waste,
see my thread: http://forum.xda-developers.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228
hansdepaula said:
no man, my bootloader as corrupted..
this dont write nothing on my phone..
my partition is all 'RAW' system..
i try flash 4.4.4 files taked on OTA, not work..
nothing change..
i cant enter in recovery or anything, only bootloader..
we are together on bricked..
hard or soft i d'nt know but my (and your?) device stay unusable. :/
if you have time to waste,
see my thread: http://forum.xda-developers.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228
Click to expand...
Click to collapse
Seems something is gone wrong with partitioning... You could try the bootloader bricker tool but even if it works you will get a completely dead Moto G like us so I think it's not a good idea... The flashblank tool can't fix the 41.13 bootloader for now, we are all waiting for a solution. Stay tuned.
moto g muerto
hola amigos, disculpen por escribir en español. sucede que instale la rom GPE 4.4.2 y actualice a 4.4.4. luego, no se porque, quize regresar a GPE 4.4.2, y fue ahi donde se me jodio el bootloader. trate de instalar todas las rom que se me cruzo por el camino y nada. luego encontre el post de boss442 e hice todos los pasos y el resultado es como se decribe al inicio. los mismo errores. espero que pronto algun desarrollador nos ayude a resucitar nuestros moto g. realmente ya no se que mas hacer. gracias
diosdiablo said:
hola amigos, disculpen por escribir en español. sucede que instale la rom GPE 4.4.2 y actualice a 4.4.4. luego, no se porque, quize regresar a GPE 4.4.2, y fue ahi donde se me jodio el bootloader. trate de instalar todas las rom que se me cruzo por el camino y nada. luego encontre el post de boss442 e hice todos los pasos y el resultado es como se decribe al inicio. los mismo errores. espero que pronto algun desarrollador nos ayude a resucitar nuestros moto g. realmente ya no se que mas hacer. gracias
Click to expand...
Click to collapse
Don't despair. My sixth sense tell me we can solve this issue with an updated singleimage.bin
Please be patient, if we are lucky we have to wait weeks... otherwise months. I can't do nothing until an official 4.4.4 full image (not OTA) will be released. Stay tuned (or buy a new device).
I'm too hardbricked my moto g with blbrick, but i have a lower bootloader, 41.11, it's from 4.4.3, i suppose, does anyone can extract it from stock rom of us.retail.umts?
i can unpack some files from firmwares, may it can help?
kenji3111 said:
I'm too hardbricked my moto g with blbrick, but i have a lower bootloader, 41.11, it's from 4.4.3, i suppose, does anyone can extract it from stock rom of us.retail.umts?
i can unpack some files from firmwares, may it can help?
Click to expand...
Click to collapse
Did you get error? It's strange, the old tool should work with the 4.4.3...
oversleeper said:
Did you get error? It's strange, the old tool should work with the 4.4.3...
Click to expand...
Click to collapse
no, it's not working, the same error
where can i find the needed files in firmware?
kenji3111 said:
no, it's not working, the same error
where can i find the needed files in firmware?
Click to expand...
Click to collapse
I will post those file when they will be available... At the moment the last available is for 4.4.2...
oversleeper said:
I will post those file when they will be available... At the moment the last available is for 4.4.2...
Click to expand...
Click to collapse
can you post it, just for try?
kenji3111 said:
can you post it, just for try?
Click to expand...
Click to collapse
I can't, it doesn't exist. You must wait a few weeks or more.
qpst
May be QPST may help us?
I tried it, the phone is stuck on download mode and if you try to flash something you will get "Could Not Communicate with Flash Programmer". I don't wanna try more, the risk to mess up my device even more is high with a such program. Unfortunately nobody can/want help us with our issue, we have to wait until a new blankflash tool will be released...
oversleeper said:
I tried it, the phone is stuck on download mode and if you try to flash something you will get "Could Not Communicate with Flash Programmer". I don't wanna try more, the risk to mess up my device even more is high with a such program. Unfortunately nobody can/want help us with our issue, we have to wait until a new blankflash tool will be released...
Click to expand...
Click to collapse
my also gives me the same error
Me sumo al pedido, tengo un xt1032 brickeado probando kernels. Solo lo detecta como Hs-Usb QUalcomm
Desde ya gracias, un abrazo.
Me too brick mine (xt1032) changing kernel in Slimkat 4.4.4. Only is detected HS-USB QUALCOMM.
If anyone want try a solution with my Moto G, just tell me.
Thanks in advance.
English :
Good evening, I install the Rom:
12.1-cm-YOG4PAS2QL-bacon-signed-fastboot
in fastboot mode to zero to put my phone
Everything is going well
It is unlocked
When I install the recovery TWRP Touch Recovery 2.8.7.0
the phone does not reboot, I did check the developer and also debugging options, and have clear the update of Cyanogen recovery.
It remains blocked on Cyanogen screen.
Thanks for your help.
J'obtiens un false, avec fastboot oem device-info, pourquoi ?
C:\fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.007s
French :
Bonsoir, j'ai installer la rom :
cm-12.1-YOG4PAS2QL-bacon-signed-fastboot
en mode fastboot pour remettre mon téléphone à zéro
Tout se passe bien
Il est unlocked
Lorsque j'installe le recovery TWRP Touch Recovery 2.8.7.0
le téléphone ne redémarre plus, j'ai bien cocher les options développeur et aussi de débogage, et ai décocher la mise a jour du recovery Cyanogen.
Il reste bloquer sur l'écran Cyanogen.
Merci de votre aide.
J'obtiens un false, avec fastboot oem device-info, pourquoi ?
C:\fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.007s
Saludos,
Recientemente compré un MOTO G XT1039 que al principio no entraba al recovery, baje una infinidad de recoverys, ninguno conseguia flashearlo, logré hacerlo con la herramienta Mototools AIOV3, pero no puedo instalar roms, ni recovery, nada, el bootloader esta desbloqueado.
logre bootear el TWRP con el comando
fastboot boot recovery.img
de ahi pruebo instalar los recovery o roms pero no los flashea, cuando enciende enciende como si no hubiera hecho nada. los errores que obtengo flasheando desde fastboot son "hab check failed for boot" "hab check failed for recovery" o "preflash validation failed"
la version de recovery actual el Android System Recovery PLB23.13-17
El telefono antes de morir tenia 5.1
Aca el log de una instalacion de un firmware 4.4.4
C:\4.4.4>mfastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.045s]
writing 'partition'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.357s
EN EL CELULAR: Version downgraded for primary_gpt
(Estoy haciendo un downgrade asique este fallo estaría bien)
C:\4.4.4>mfastboot flash motoboot motoboot.img
sending 'motoboot' (1953 KB)...
OKAY [ 0.124s]
writing 'motoboot'...
Motoboot: Preflash validation for tz
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.406s
EN EL CELULAR: version downgraded for tz
C:\4.4.4>mfastboot flash logo logo.bin
sending 'logo' (1060 KB)...
OKAY [ 0.112s]
writing 'logo'...
OKAY [ 0.086s]
finished. total time: 0.198s
C:\4.4.4>mfastboot flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 0.409s]
writing 'boot'...
OKAY [ 0.647s]
finished. total time: 1.057s
EN EL CELULAR: hab check failed for boot
C:\4.4.4>mfastboot flash recovery recovery.img
sending 'recovery' (10240 KB)...
OKAY [ 0.416s]
writing 'recovery'...
OKAY [ 0.638s]
finished. total time: 1.056s
EN EL CELULAR: hab check failed for recovery
Hasta aca deberia estar una parte
Ahora los comandos, este telefono es europeo asique debe llevar estos
C:\4.4.4>mfastboot flash system system.img_sparsechunk.0
sending 'system' (248267 KB)...
OKAY [ 7.857s]
writing 'system'...
OKAY [ 8.538s]
finished. total time: 16.395s
C:\4.4.4>mfastboot flash system system.img_sparsechunk.1
sending 'system' (248994 KB)...
OKAY [ 7.873s]
writing 'system'...
OKAY [ 7.609s]
finished. total time: 15.481s
C:\4.4.4>mfastboot flash system system.img_sparsechunk.2
sending 'system' (257391 KB)...
OKAY [ 8.132s]
writing 'system'...
OKAY [ 8.055s]
finished. total time: 16.187s
C:\4.4.4>mfastboot flash system system.img_sparsechunk.3
sending 'system' (20588 KB)...
OKAY [ 0.732s]
writing 'system'...
OKAY [ 13.263s]
finished. total time: 13.995s
C:\4.4.4>mfastboot flash modem NON-HLOS.bin
sending 'modem' (59132 KB)...
OKAY [ 1.874s]
writing 'modem'...
OKAY [ 0.985s]
finished. total time: 2.860s
C:\4.4.4>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.011s]
finished. total time: 0.011s
C:\4.4.4>
C:\4.4.4>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.011s]
finished. total time: 0.012s
C:\4.4.4>mfastboot flash fsg fsg.mbn
sending 'fsg' (710 KB)...
OKAY [ 0.065s]
writing 'fsg'...
OKAY [ 3.169s]
finished. total time: 3.234s
C:\4.4.4>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.015s]
finished. total time: 0.015s
C:\4.4.4>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.018s]
finished. total time: 0.018s
pero cuando reinicio solo se queda en la pantalla del bootloader desbloqueado, si pruebo instalando desde el recovery me pone que no hubo fallos pero cuando reinicio no pasa nada.
cuando instalo un recovery no lo instala, los comandos no muestran errores, pero cuando reinicio no cambió el recovery
ya he intentado todo, la unica herramienta que pudo modificarme en algo el telefono fue mototools AIO v3
Hello,
please edit your post with an English translation.
Kind regards
Trafalgar Square
XDA Assist
first we need to have the correct firmware of the device in case something goes wrong to reinstall again
second step
as you already have the previously installed recovery you must enter the recovery and give it delete to clear cache, delete software and delete internal storage and restart it no matter that it says it has no operating system the device will be in bootlogo or simply restart in the own recovery TWRP at that time that really does not have software the device we put it in bootloader mode.
third step reinstall the correct firmware of the device through ADB with the following commands that appear below
fastboot devices
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
let it restart the software, and once restarted you turn it off again and leave it in bootloader mode you install the twrp right away.
at that precise moment you enter the recovery you configure it and you will notice that already the internal storage is visible and there is no problem of encryption you can restart the software and ready problem solved.
me funciono pero ahora se me queda en el logo de motorola :'''v
Lautii 18 said:
me funciono pero ahora se me queda en el logo de motorola :'''v
Click to expand...
Click to collapse
Bueno amigo tienes que limpiar el sistema como si estuviera restableciendo lo de fabrica a través de recovery si no te funciona reinstalar nuevamente el recovery a veces el recovery da error y no deja arrancar el software
Hello, it does not work for me on a motorcycle e5 play xt1920-18 when I give a deletion system or any other partition it gives me an error and there is nothing you can possibly help me thanks.
Hola, no me funciona en moto e5 play xt1920-18 cuando doy sistema de borrado o cualquier otra partición me da error y no hay nada quiza puedas ayudarme gracias.
telegram... @motoe5dev ...... @Pettyl
juanito1987_9 said:
telegram... @motoe5dev ...... @Pettyl
Click to expand...
Click to collapse
Pode me arrumar ?
is there any solution for this on moto e5 plus. i had a pattern lock and my os crashed and now when i try to inter my storage from recovery it says my data is encrypted and both my internal and sd card isn't showing. now i can't even install new rom. is there any solution?
MOD EDIT: ENGLISH TRANSLATION ADDED
This is the last update of the x4 bike they're making available because when I needed it I realized that no one had it, so how I got it here, this is for those with hard-bricks. soft-brick, among other errors that the device has no wi-fi, no known signal the chip this rom will clear any doubts I will be answering in the comments
DISCLAIMER
I cannot be held responsible for any damage that occurs to your device during this process. You are responsible for any transmission notice (if) to your device during this process.
DESCRIPTION
Android Pie retail ROM (version number PAYTON_PPW29.69_40_4) for Moto X4
REQUIREMENTS
Make sure your device is over 80% charged.
We recommend creating a backup of all your important files before starting this process.
HOW TO INSTALL STOCK ROM ON MOTO X4:
Rom https://drive.google.com/file/d/121Tq7BzLsYGsn_PNmKTtD-jeppZZyM3D/view?usp=sharing
Install Motorola driver and ADB Fastboot on your PC.
Now extra firmware from stock in ADB Fastboot folder.
Turn off the device and boot into the bootloader press the volume down button + the power button.
Connect your device to the PC via a USB cable.
open from Adb Fastboot, and paste the commands below or run flash-all.bat
------------------------------------------------------------------------
Esta é a última atualização da moto x4 que está disponibilizando porque quando eu precisoi percebi que ninguém tinha, então como eu consegui aqui, isso é para aqueles com hard-brick. soft-brick, entre outros erros que o aparelho fica sem wi-fi, nenhum sinal conhecido o chip esta rom vai tirar qualquer duvida estarei respondendo nos comentários
ISENÇÃO DE RESPONSABILIDADE
Não posso ser responsabilizado por quaisquer danos que ocorram ao seu dispositivo durante este processo. Você é responsável por qualquer aviso de transmissão (se) ao seu dispositivo durante este processo.
DESCRIÇÃO
ROM de varejo do Android Pie (número da versão PAYTON_PPW29.69_40_4) para Moto X4
REQUISITOS
Certifique-se de que seu dispositivo está carregado acima de 80%.
Recomendamos criar um backup de todos os seus arquivos importantes antes de iniciar este processo.
COMO INSTALAR STOCK ROM NO MOTO X4:
Rom https://drive.google.com/file/d/121Tq7BzLsYGsn_PNmKTtD-jeppZZyM3D/view?usp=sharing
Instale o driver da Motorola e o ADB Fastboot em seu PC.
Agora extra firmware de estoque na pasta ADB Fastboot.
Desligue o dispositivo e inicialize no bootloader pressiona o botão de diminuir o volume + o botão liga / desliga.
Conecte seu dispositivo ao PC por meio de um cabo USB.
abra do Adb Fastboot, e cole os comandos abaixo ou execute o flash-all.bat
[CÓDIGO]
fastboot devices
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash fsg_b fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash dsp_b dspso.bin
fastboot flash logo logo.bin
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
new links ?
Can you please provide .qcn file backup of Moto x4