• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[HOW TO] Unbrick hard bricked Moto G (for Android 4.4.4 (5.x now available))

Search This thread

oversleeper

Senior Member
Jun 24, 2014
202
245
Melbourne
If you hard bricked after the 4.4.4 (or 5.x) upgrade and your device looks dead and it's only recognized by pc as "qhsusb_bulk" this is the right place for you. This procedure has been tested with Win7 on Moto G XT1032 and should be fine for every model.

You will need:


First of all you will need to extract Riff BOX drivers in a folder (you will find both 32bit and 64bit versions). Open dseo13b.exe and choose "Sign a System File", follow the program instructions and there you go, the program will ask you to reboot. While you reboot press F8 many times until you get a menu, choose "Disable Driver Signature Enforcement", now click on Windows Start button and write "devmgmt.msc" without quotes, you will get the Device Manager window. Go on "qhsusb_bulk" (if not shown unplug and plug again your Moto G or long press the power button) then choose "Update Driver Software", choose the manually way and put the path of your previously extracted and signed drivers. Your Moto G is now recognized as "Qualcomm HS-USB QLoader 9008" under Ports (COM & LPT). Now extract the Motorola qboot utility and run the blank-flash.bat, your Moto G should be able to enter in fastboot mode! Now your device shows "Status Code :0", to get the correct status just flash a gpt.bin and a motoboot.img from a random 4.4.4 (or 5.x) Moto G firmware. It's done, now you can flash the firmware you like more... as always!

zr488jD.jpg


-----------------------------------------------------------------------------------------------------------------
MORE TOOLS:
  • Device Info Tool: Just a shortcut for the "getvar all" command, it shows all the info of your device
  • Bootloader Refresh Tool: You could need this if you think your bootloader needs to be upgraded or refreshed to the version 41.13, which is the latest. (OUTDATED)
  • Bootloader Bricker Tool: If the previous tool had no effect or you think your bootloader is seriously damaged, this script will make your phone recognized as "qhsusb_bulk" so you can perform a blank flash
    The bricker should be used very carefully and only on Android 4.4.4 with 41.13 bootloader. DO NOT use it on higher versions.
I'm not responsible for the bad usage of these tools.

TOOLS PACK DOWNLOAD
-----------------------------------------------------------------------------------------------------------------

Thanks to cellzealot and Boss442:good:
 
Last edited:

diosdiablo

Member
Jul 6, 2014
17
0
gracias

hola amigos, primero para agradecerles por esta solucion al brickeo del moto g, por fin ya arranca en modo fastboot. quizas podrian ayudarme en la manera de instalar una rom. primero como soluciono esto de fastboot reason: failed to initialize partition table. gracias otra vez por el apoyo.
 

oversleeper

Senior Member
Jun 24, 2014
202
245
Melbourne
hola amigos, primero para agradecerles por esta solucion al brickeo del moto g, por fin ya arranca en modo fastboot. quizas podrian ayudarme en la manera de instalar una rom. primero como soluciono esto de fastboot reason: failed to initialize partition table. gracias otra vez por el apoyo.

Now you have to install a stock rom. My advice, if you have a XT1032, is to use this rom

Once you downloaded put the mfastboot in a folder, put the extracted firmware rom in the same folder then open notepad, copy-paste the following commands and save the file as ".bat". Then run the ".bat" and there you go!

Code:
SET fastboot=mfastboot.exe
%fastboot% flash partition gpt.bin
%fastboot% flash motoboot motoboot.img
%fastboot% flash logo logo.bin
%fastboot% flash boot boot.img
%fastboot% flash recovery recovery.img
%fastboot% flash system system.img_sparsechunk.0
%fastboot% flash system system.img_sparsechunk.1
%fastboot% flash system system.img_sparsechunk.2
%fastboot% flash modem NON-HLOS.bin
%fastboot% erase modemst1
%fastboot% erase modemst2
%fastboot% flash fsg fsg.mbn
%fastboot% erase cache
%fastboot% erase userdata
pause
 

diosdiablo

Member
Jul 6, 2014
17
0
hola .... gracias por el apoyo, pero sucede que no pasa de warning bootloader unlocked .... veo que sale muchos errores durante el proceso de flasheo .... gracias por tu apoyo otra vez
 

maurote

Member
Oct 14, 2009
12
0
One question, need full batery?
I have Battery low and the result is:

In the display:

Fastboot Reason: failed to initializa partition table

In the cmd of .bat:

E:\Celulares\XT1032\revivir>SET fastboot=mfastboot.exe

E:\Celulares\XT1032\revivir>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.076s]
writing 'partition'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.119s

E:\Celulares\XT1032\revivir>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.138s]
writing 'motoboot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.187s

E:\Celulares\XT1032\revivir>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [ 0.110s]
writing 'logo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.154s

E:\Celulares\XT1032\revivir>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.406s]
writing 'boot'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.447s

E:\Celulares\XT1032\revivir>mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.406s]
writing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.424s

E:\Celulares\XT1032\revivir>mfastboot.exe flash system system.img_sparsechunk.0

target max-sparse-size: 256MB
sending 'system' (249379 KB)...
OKAY [ 8.172s]
writing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 8.217s

E:\Celulares\XT1032\revivir>mfastboot.exe flash system system.img_sparsechunk.1

target max-sparse-size: 256MB
sending 'system' (252566 KB)...
OKAY [ 8.285s]
writing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 8.307s

E:\Celulares\XT1032\revivir>mfastboot.exe flash system system.img_sparsechunk.2

target max-sparse-size: 256MB
sending 'system' (248947 KB)...
OKAY [ 8.160s]
writing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 8.206s

E:\Celulares\XT1032\revivir>mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (47152 KB)...
OKAY [ 1.585s]
writing 'modem'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 1.605s

E:\Celulares\XT1032\revivir>mfastboot.exe erase modemst1
erasing 'modemst1'...
(bootloader) Invalid partition name modemst1
FAILED (remote failure)
finished. total time: 0.032s

E:\Celulares\XT1032\revivir>mfastboot.exe erase modemst2
erasing 'modemst2'...
(bootloader) Invalid partition name modemst2
FAILED (remote failure)
finished. total time: 0.038s

E:\Celulares\XT1032\revivir>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.084s]
writing 'fsg'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.107s

E:\Celulares\XT1032\revivir>mfastboot.exe erase cache
erasing 'cache'...
(bootloader) Invalid partition name cache
FAILED (remote failure)
finished. total time: 0.028s

E:\Celulares\XT1032\revivir>mfastboot.exe erase userdata
erasing 'userdata'...
(bootloader) Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.038s

E:\Celulares\XT1032\revivir>pause
Presione una tecla para continuar . . .
 
Last edited:

oversleeper

Senior Member
Jun 24, 2014
202
245
Melbourne
One question, need full batery?
I have Battery low and the result is:

In the display:

Fastboot Reason: failed to initializa partition table

In the cmd of .bat:

E:\Celulares\XT1032\revivir>SET fastboot=mfastboot.exe

E:\Celulares\XT1032\revivir>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.076s]
writing 'partition'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.119s

E:\Celulares\XT1032\revivir>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.138s]
writing 'motoboot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.187s

E:\Celulares\XT1032\revivir>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [ 0.110s]
writing 'logo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.154s

E:\Celulares\XT1032\revivir>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.406s]
writing 'boot'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.447s

E:\Celulares\XT1032\revivir>mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.406s]
writing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.424s

E:\Celulares\XT1032\revivir>mfastboot.exe flash system system.img_sparsechunk.0

target max-sparse-size: 256MB
sending 'system' (249379 KB)...
OKAY [ 8.172s]
writing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 8.217s

E:\Celulares\XT1032\revivir>mfastboot.exe flash system system.img_sparsechunk.1

target max-sparse-size: 256MB
sending 'system' (252566 KB)...
OKAY [ 8.285s]
writing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 8.307s

E:\Celulares\XT1032\revivir>mfastboot.exe flash system system.img_sparsechunk.2

target max-sparse-size: 256MB
sending 'system' (248947 KB)...
OKAY [ 8.160s]
writing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 8.206s

E:\Celulares\XT1032\revivir>mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (47152 KB)...
OKAY [ 1.585s]
writing 'modem'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 1.605s

E:\Celulares\XT1032\revivir>mfastboot.exe erase modemst1
erasing 'modemst1'...
(bootloader) Invalid partition name modemst1
FAILED (remote failure)
finished. total time: 0.032s

E:\Celulares\XT1032\revivir>mfastboot.exe erase modemst2
erasing 'modemst2'...
(bootloader) Invalid partition name modemst2
FAILED (remote failure)
finished. total time: 0.038s

E:\Celulares\XT1032\revivir>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.084s]
writing 'fsg'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.107s

E:\Celulares\XT1032\revivir>mfastboot.exe erase cache
erasing 'cache'...
(bootloader) Invalid partition name cache
FAILED (remote failure)
finished. total time: 0.028s

E:\Celulares\XT1032\revivir>mfastboot.exe erase userdata
erasing 'userdata'...
(bootloader) Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.038s

E:\Celulares\XT1032\revivir>pause
Presione una tecla para continuar . . .

Yeah, keep your battery in charge for at least 1 hour, shoud be shown battery low (charging).
When you get the green "battery ok" you can proceed.
 

marknoll

Senior Member
May 13, 2014
2,932
300
I am thinking of getting a moto g. The Verizon version from Walmart. I have att, so is there a way to get the moto to work on att?
 

hansdepaula

Member
Jun 26, 2014
49
3
man, i'm happy for you..
but my moto g xt1033 stay bricked..
and my thread as forgotten
see: http://forum.xda-developers.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228
have some logs, maybe important for understand my problem..

but ok..

i try this method..
but my pc dont see "qhsusb_bulk"
i try run blank flash, not work:


Code:
WARNING: READ CAREFULLY BEFORE YOU PROCEED!

THIS SCRIPT WILL DESTROY THE BOOTLOADER OF YOUR DEVICE.
DO NOT ATTEMPT TO USE UNLESS YOU'RE SURE ABOUT WHAT YOU'RE DOING.
ONLY YOU ARE RESPONSIBLE FOR YOUR ACTIONS.

Do you want to continue [Y/N]?y

target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [  0.023s]
writing 'fsg'...
OKAY [  3.142s]
finished. total time: 3.165s
target max-sparse-size: 256MB
sending 'rpm' (200 KB)...
OKAY [  0.035s]
writing 'rpm'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.322s
target max-sparse-size: 256MB
sending 'sbl1' (264 KB)...
OKAY [  0.052s]
writing 'sbl1'...
OKAY [  0.031s]
finished. total time: 0.085s
target max-sparse-size: 256MB
sending 'sdi' (32 KB)...
OKAY [  0.053s]
writing 'sdi'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.363s
target max-sparse-size: 256MB
sending 'tz' (400 KB)...
OKAY [  0.081s]
writing 'tz'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.374s
rebooting...

finished. total time: 0.020s

Your device is now hard bricked!

Pressione qualquer tecla para continuar. . .

my bootloader show 41.11, maybe i can run a blank flash for this version?

i show on this page: http://forum.xda-developers.com/showthread.php?t=2623587&page=11
a better close i can get for "qhsusb_bulk"..

see again:
rsy5gx.png


the code for QcomDevice90080 is: USB\VID_05C6&PID_9008
i get variations off \VID_05C6&PID_9025

man, i really want use my device again..
maybe you can help me :)
and sorry for poor english.

@edit..
i see it on another thread:
As far as I can tell, battery is not actually required. "qhsusb_bulk" still loads for me, even when the battery isn't hooked up. I only know because at first I thought a new battery might fix the problem and opened my Moto G and replaced it/tried it without. Just FYI.

if i open my device and 'remove' battery i will get "qhsusb_bulk" on connect?
 
Last edited:

oversleeper

Senior Member
Jun 24, 2014
202
245
Melbourne
man, i'm happy for you..
but my moto g xt1033 stay bricked..
and my thread as forgotten
see: http://forum.xda-developers.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228
have some logs, maybe important for understand my problem..

but ok..

i try this method..
but my pc dont see "qhsusb_bulk"
i try run blank flash, not work:


Code:
WARNING: READ CAREFULLY BEFORE YOU PROCEED!

THIS SCRIPT WILL DESTROY THE BOOTLOADER OF YOUR DEVICE.
DO NOT ATTEMPT TO USE UNLESS YOU'RE SURE ABOUT WHAT YOU'RE DOING.
ONLY YOU ARE RESPONSIBLE FOR YOUR ACTIONS.

Do you want to continue [Y/N]?y

target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [  0.023s]
writing 'fsg'...
OKAY [  3.142s]
finished. total time: 3.165s
target max-sparse-size: 256MB
sending 'rpm' (200 KB)...
OKAY [  0.035s]
writing 'rpm'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.322s
target max-sparse-size: 256MB
sending 'sbl1' (264 KB)...
OKAY [  0.052s]
writing 'sbl1'...
OKAY [  0.031s]
finished. total time: 0.085s
target max-sparse-size: 256MB
sending 'sdi' (32 KB)...
OKAY [  0.053s]
writing 'sdi'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.363s
target max-sparse-size: 256MB
sending 'tz' (400 KB)...
OKAY [  0.081s]
writing 'tz'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.374s
rebooting...

finished. total time: 0.020s

Your device is now hard bricked!

Pressione qualquer tecla para continuar. . .

my bootloader show 41.11, maybe i can run a blank flash for this version?

i show on this page: http://forum.xda-developers.com/showthread.php?t=2623587&page=11
a better close i can get for "qhsusb_bulk"..

see again:
rsy5gx.png


the code for QcomDevice90080 is: USB\VID_05C6&PID_9008
i get variations off \VID_05C6&PID_9025

man, i really want use my device again..
maybe you can help me :)
and sorry for poor english.

@edit..
i see it on another thread:


if i open my device and 'remove' battery i will get "qhsusb_bulk" on connect?

Can you still use fastboot or your device is completely dead?
 

oversleeper

Senior Member
Jun 24, 2014
202
245
Melbourne
I try to give you some solutions.
First try to download this.
Run the DeviceInfo.bat and post the result (delete the "serialno" and "imei" info before to post).
Do not run the other tools for now.
 
Last edited:

hansdepaula

Member
Jun 26, 2014
49
3
I try to give you some solutions.
First try to download this.
Run the DeviceInfo.bat and post the result (delete the "serialno" and "imei" info before to post).
Do not run the other tools for now.


getvar all:
Code:
C:\androidsdk\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
[b](bootloader) version-bootloader: 4111[/b]
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x5
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
[b](bootloader) serialno: 0425016712
(bootloader) cid: 0x000C[/b]
(bootloader) channelid: 0x00
(bootloader) uid: 997643020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
[b](bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:[/b]
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jul  3 10:11:24 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retbr_ds/falcon_um
(bootloader) ro.build.fingerprint[1]: tsds:4.4.3/KXB21.14-L1.32/30:user/
(bootloader) ro.build.fingerprint[2]: release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.32.falcon_umt
(bootloader) ro.build.version.full[1]: sds.Brasil.en.BR
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.020
[b](bootloader) version-baseband:[/b]
(bootloader) kernel.version[0]: Linux version 3.4.42-g6095065 [b]([email protected]
(bootloader) kernel.version[1]: ilclbld54)[/b] (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri May 30 13:52:19 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.11-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.11-0-gcff5797
(bootloader) rpm.git: git=MBM-NG-V41.11-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.11-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.11-0-g7d46a5a
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.202s


ps: i dont hide no one information..
my device have a blank IMEI and blank other strings!?


anything work for me..
i try reflash 4.4.3, 4.4.2, 4.3, and nothing change,
try all modes and read all posts( like http://forum.xda-developers.com/showthread.php?t=2542219)
recive ok from all flash on fastboot
see :
Code:
C:\Users\Hans\Desktop\443>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [  0.097s]
writing 'partition'...
[B](bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...[/B]
OKAY [  0.390s]
finished. total time: 0.490s

C:\Users\Hans\Desktop\443>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [  0.171s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [  1.136s]
finished. total time: 1.308s

C:\Users\Hans\Desktop\443>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [  0.139s]
writing 'logo'...
OKAY [  0.076s]
finished. total time: 0.218s

C:\Users\Hans\Desktop\443>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [  0.435s]
writing 'boot'...
OKAY [  0.662s]
finished. total time: 1.101s

C:\Users\Hans\Desktop\443>mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [  0.432s]
writing 'recovery'...
OKAY [  0.661s]
finished. total time: 15.360s

C:\Users\Hans\Desktop\443>mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (249247 KB)...
OKAY [  8.308s]
writing 'system'...
OKAY [  8.400s]
finished. total time: 16.710s

C:\Users\Hans\Desktop\443>mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (250602 KB)...
OKAY [  8.332s]
writing 'system'...
OKAY [  7.630s]
finished. total time: 15.965s

C:\Users\Hans\Desktop\443>mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (248370 KB)...
OKAY [  8.268s]
writing 'system'...
OKAY [ 15.916s]
finished. total time: 24.186s

C:\Users\Hans\Desktop\443>mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (47152 KB)...
OKAY [  1.612s]
writing 'modem'...
OKAY [  0.787s]
finished. total time: 2.401s

C:\Users\Hans\Desktop\443>mfastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [  0.012s]
finished. total time: 0.013s

C:\Users\Hans\Desktop\443>mfastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [  0.036s]
finished. total time: 0.037s

C:\Users\Hans\Desktop\443>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [  0.086s]
writing 'fsg'...
OKAY [  3.173s]
finished. total time: 3.261s

C:\Users\Hans\Desktop\443>mfastboot.exe erase cache
erasing 'cache'...
OKAY [  0.016s]
finished. total time: 0.017s

C:\Users\Hans\Desktop\443>mfastboot.exe erase userdata
erasing 'userdata'...
OKAY [  0.046s]
finished. total time: 0.047s

C:\Users\Hans\Desktop\443>pause
Pressione qualquer tecla para continuar. . .

my custom bootlogo stay after flash stock (the stock "M" or "boounlock warning" dont apear!!??)
my bronked recovery stay after fash stock or TWRP / CWM philz, i try all versions
and on first boot i revice infinite FC
on next boot it stuck on infinity bootlogo (my custom boot logo)

can not enter on recovery, i try everyone
and every time it return a black screen
and i stay recive vibration feedback on touch.

i really disaponted because the bootlogo/recovery dont change..
fastboot dont write nothing on my phone!?

i try format some partition but not work..
i think my sd card or/and partitions was break, like 'bad disk'

it say "RAW" dont format

please see:
Code:
C:\androidsdk\sdk\platform-tools>fastboot devices
[B]0425016712      fastboot[/B]

[B]C:\androidsdk\sdk\platform-tools>fastboot format all
Formatting is not supported for filesystem with type ''.[/B]
[B]
C:\androidsdk\sdk\platform-tools>fastboot format recovery
Formatting is not supported for filesystem with type 'raw

C:\androidsdk\sdk\platform-tools>fastboot format userdata
Formatting is not supported for filesystem with type 'raw'.

C:\androidsdk\sdk\platform-tools>fastboot format cache
Formatting is not supported for filesystem with type 'raw'.[/B]


i try flash various recovery, but no one work
see:
Code:
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.711.img
target reported max download size of 536870912 bytes
sending 'recovery' (7692 KB)...
OKAY [  0.272s]
writing 'recovery'...
OKAY [  0.150s]
finished. total time: 0.423s

C:\androidsdk\sdk\platform-tools>
[b]
it say ok, but on try go on recovery i stuck on black screen a
and every click on screen return a vibration for me.
[/b]
i need long click (10seg) on power button to go away
and vol down for fastboot again, or i get a stuck on my old custom boot logo
and on fast boot i can try flash again another version's. 

:/
--------------------------------------------------------------------
same on 2.7.0.0:  

C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.70.img
target reported max download size of 536870912 bytes
sending 'recovery' (7912 KB)...
OKAY [  0.284s]
writing 'recovery'...
OKAY [  0.154s]
finished. total time: 0.440s

black screen and every click on screen return a vibration.
---------------------------------------------------------------------
same on 2.6.3.3

C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.63.img
target reported max download size of 536870912 bytes
sending 'recovery' (8678 KB)...
OKAY [  0.307s]
writing 'recovery'...
OKAY [  0.197s]
finished. total time: 0.506s

black screen and every click on screen return a vibration.
-------------------------------------------------------------------------
See:

[B]C:\androidsdk\sdk\platform-tools>fastboot format recovery
Formatting is not supported for filesystem with type 'raw'.[/B]

i really think fastboot dont write anything on my device..
bootlogo.img and recovery.img
dont change and i flash it 1000x with OK report.
 
Last edited:

oversleeper

Senior Member
Jun 24, 2014
202
245
Melbourne
getvar all:
Code:
C:\androidsdk\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
[b](bootloader) version-bootloader: 4111[/b]
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x5
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
[b](bootloader) serialno: 0425016712
(bootloader) cid: 0x000C[/b]
(bootloader) channelid: 0x00
(bootloader) uid: 997643020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
[b](bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:[/b]
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jul  3 10:11:24 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retbr_ds/falcon_um
(bootloader) ro.build.fingerprint[1]: tsds:4.4.3/KXB21.14-L1.32/30:user/
(bootloader) ro.build.fingerprint[2]: release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.32.falcon_umt
(bootloader) ro.build.version.full[1]: sds.Brasil.en.BR
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.020
[b](bootloader) version-baseband:[/b]
(bootloader) kernel.version[0]: Linux version 3.4.42-g6095065 [b]([email protected]
(bootloader) kernel.version[1]: ilclbld54)[/b] (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri May 30 13:52:19 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.11-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.11-0-gcff5797
(bootloader) rpm.git: git=MBM-NG-V41.11-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.11-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.11-0-g7d46a5a
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.202s


ps: i dont hide no one information..
my device have a blank IMEI and blank other strings!?


anything work for me..
i try reflash 4.4.3, 4.4.2, 4.3, and nothing change,
try all modes and read all posts( like http://forum.xda-developers.com/showthread.php?t=2542219)
recive ok from all flash on fastboot
see :
Code:
C:\Users\Hans\Desktop\443>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [  0.097s]
writing 'partition'...
[B](bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...[/B]
OKAY [  0.390s]
finished. total time: 0.490s

C:\Users\Hans\Desktop\443>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [  0.171s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [  1.136s]
finished. total time: 1.308s

C:\Users\Hans\Desktop\443>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [  0.139s]
writing 'logo'...
OKAY [  0.076s]
finished. total time: 0.218s

C:\Users\Hans\Desktop\443>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [  0.435s]
writing 'boot'...
OKAY [  0.662s]
finished. total time: 1.101s

C:\Users\Hans\Desktop\443>mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [  0.432s]
writing 'recovery'...
OKAY [  0.661s]
finished. total time: 15.360s

C:\Users\Hans\Desktop\443>mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (249247 KB)...
OKAY [  8.308s]
writing 'system'...
OKAY [  8.400s]
finished. total time: 16.710s

C:\Users\Hans\Desktop\443>mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (250602 KB)...
OKAY [  8.332s]
writing 'system'...
OKAY [  7.630s]
finished. total time: 15.965s

C:\Users\Hans\Desktop\443>mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (248370 KB)...
OKAY [  8.268s]
writing 'system'...
OKAY [ 15.916s]
finished. total time: 24.186s

C:\Users\Hans\Desktop\443>mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (47152 KB)...
OKAY [  1.612s]
writing 'modem'...
OKAY [  0.787s]
finished. total time: 2.401s

C:\Users\Hans\Desktop\443>mfastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [  0.012s]
finished. total time: 0.013s

C:\Users\Hans\Desktop\443>mfastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [  0.036s]
finished. total time: 0.037s

C:\Users\Hans\Desktop\443>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [  0.086s]
writing 'fsg'...
OKAY [  3.173s]
finished. total time: 3.261s

C:\Users\Hans\Desktop\443>mfastboot.exe erase cache
erasing 'cache'...
OKAY [  0.016s]
finished. total time: 0.017s

C:\Users\Hans\Desktop\443>mfastboot.exe erase userdata
erasing 'userdata'...
OKAY [  0.046s]
finished. total time: 0.047s

C:\Users\Hans\Desktop\443>pause
Pressione qualquer tecla para continuar. . .

my custom bootlogo stay after flash stock (the stock "M" or "boounlock warning" dont apear!!??)
my bronked recovery stay after fash stock or TWRP / CWM philz, i try all versions
and on first boot i revice infinite FC
on next boot it stuck on infinity bootlogo (my custom boot logo)

can not enter on recovery, i try everyone
and every time it return a black screen
and i stay recive vibration feedback on touch.

i really disaponted because the bootlogo/recovery dont change..
fastboot dont write nothing on my phone!?

i try format some partition but not work..
i think my sd card or/and partitions was break, like 'bad disk'

it say "RAW" dont format

please see:
Code:
C:\androidsdk\sdk\platform-tools>fastboot devices
[B]0425016712      fastboot[/B]

[B]C:\androidsdk\sdk\platform-tools>fastboot format all
Formatting is not supported for filesystem with type ''.[/B]
[B]
C:\androidsdk\sdk\platform-tools>fastboot format recovery
Formatting is not supported for filesystem with type 'raw

C:\androidsdk\sdk\platform-tools>fastboot format userdata
Formatting is not supported for filesystem with type 'raw'.

C:\androidsdk\sdk\platform-tools>fastboot format cache
Formatting is not supported for filesystem with type 'raw'.[/B]


i try flash various recovery, but no one work
see:
Code:
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.711.img
target reported max download size of 536870912 bytes
sending 'recovery' (7692 KB)...
OKAY [  0.272s]
writing 'recovery'...
OKAY [  0.150s]
finished. total time: 0.423s

C:\androidsdk\sdk\platform-tools>
[b]
it say ok, but on try go on recovery i stuck on black screen a
and every click on screen return a vibration for me.
[/b]
i need long click (10seg) on power button to go away
and vol down for fastboot again, or i get a stuck on my old custom boot logo
and on fast boot i can try flash again another version's. 

:/
--------------------------------------------------------------------
same on 2.7.0.0:  

C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.70.img
target reported max download size of 536870912 bytes
sending 'recovery' (7912 KB)...
OKAY [  0.284s]
writing 'recovery'...
OKAY [  0.154s]
finished. total time: 0.440s

black screen and every click on screen return a vibration.
---------------------------------------------------------------------
same on 2.6.3.3

C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.63.img
target reported max download size of 536870912 bytes
sending 'recovery' (8678 KB)...
OKAY [  0.307s]
writing 'recovery'...
OKAY [  0.197s]
finished. total time: 0.506s

black screen and every click on screen return a vibration.
-------------------------------------------------------------------------
See:

[B]C:\androidsdk\sdk\platform-tools>fastboot format recovery
Formatting is not supported for filesystem with type 'raw'.[/B]

i really think fastboot dont write anything on my device..
bootlogo.img and recovery.img
dont change and i flash it 1000x with OK report.

Ok man, try to run the other 2 tools inside my package, first the hard bricker, post the result, then if doesn't work try the bootloader tool and post the result:good: Your device is ok, just the bootloader is corrupted but don't worry, we have resurrected devices in worst situations.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 82
    If you hard bricked after the 4.4.4 (or 5.x) upgrade and your device looks dead and it's only recognized by pc as "qhsusb_bulk" this is the right place for you. This procedure has been tested with Win7 on Moto G XT1032 and should be fine for every model.

    You will need:


    First of all you will need to extract Riff BOX drivers in a folder (you will find both 32bit and 64bit versions). Open dseo13b.exe and choose "Sign a System File", follow the program instructions and there you go, the program will ask you to reboot. While you reboot press F8 many times until you get a menu, choose "Disable Driver Signature Enforcement", now click on Windows Start button and write "devmgmt.msc" without quotes, you will get the Device Manager window. Go on "qhsusb_bulk" (if not shown unplug and plug again your Moto G or long press the power button) then choose "Update Driver Software", choose the manually way and put the path of your previously extracted and signed drivers. Your Moto G is now recognized as "Qualcomm HS-USB QLoader 9008" under Ports (COM & LPT). Now extract the Motorola qboot utility and run the blank-flash.bat, your Moto G should be able to enter in fastboot mode! Now your device shows "Status Code :0", to get the correct status just flash a gpt.bin and a motoboot.img from a random 4.4.4 (or 5.x) Moto G firmware. It's done, now you can flash the firmware you like more... as always!

    zr488jD.jpg


    -----------------------------------------------------------------------------------------------------------------
    MORE TOOLS:
    • Device Info Tool: Just a shortcut for the "getvar all" command, it shows all the info of your device
    • Bootloader Refresh Tool: You could need this if you think your bootloader needs to be upgraded or refreshed to the version 41.13, which is the latest. (OUTDATED)
    • Bootloader Bricker Tool: If the previous tool had no effect or you think your bootloader is seriously damaged, this script will make your phone recognized as "qhsusb_bulk" so you can perform a blank flash
      The bricker should be used very carefully and only on Android 4.4.4 with 41.13 bootloader. DO NOT use it on higher versions.
    I'm not responsible for the bad usage of these tools.

    TOOLS PACK DOWNLOAD
    -----------------------------------------------------------------------------------------------------------------

    Thanks to cellzealot and Boss442:good:
    29
    Good news guys! The new flashblank tool should be available in few days!:good:
    18
    I have happened to brick another XT1032 (this time without updating to Android 5.x) so I had the opportunity to perform some tests:
    It turns out that while both programmers that are included with MotoFlasher pass digital signature verification against my device, only one of them is able to flash singleimage.bin to my device.
    this proves that programmer.mbn itself perform an additional check before it agrees to receive and flash singleimage.bin.

    After some reverse engineering, I was able to locate that check:
    Programmer-4.3.0 Checks that BOOTLOADER <= 0:
    Programmer_4_3_0.png

    Programmer-4.4.4 Checks that BOOTLOADER <= 2:
    Programmer_4_4_4.png


    The programmer checks which BOOTLOADER version is blown to the qfuses of the device (by counting the number of blown bits), and if this version is higher than expected it powers down the device.
    Since Lollipop has BOOTLOADER = 3, none of the existing programmer.mbn are able to blank-flash it.
    Unfortunately, once we modify programmer.mbn, the existing signature is no longer valid.

    Additional notes:
    - The BOOTLOADER version of the device can be read using 'fastboot oem read_sv' starting from fastboot v41.13.
    - At a later stage, programmer.mbn checks that singleimage.bin is not larger than 0x500000 bytes.
    - Programmer 4.3.0 MD5: 10A2296D307A8BD0A3B1DD9A15616BC1
    - Programmer 4.4.4 MD5: 252E3D28C8C4957C4F684221B83F3F83
    16
    This is so lame , talking rubbish yourself and calling me idiot

    And talk properly no need you use such language

    There is a reason why is said that
    There are people who have subscribed to this thread for getting updates on unbricking tool, and what do that get - false alarms

    Besides @oversleeper know more and would make the blankflasher work as soon as right files are leaked

    Exactly. Unfortunately those files are still unavaible. I'm currently overseas and I can't spend much time on the forum. The xda-dev community is great and very helpful though, thank you guys. I keep looking forward to release the next blankflash tool :good:
    14
    Hi everyone,

    I've been very busy in the last period and I couldn't answer most of you. Basically the question I get is always the same: why the unbrick tool doesn't work?
    It doesn't work because it's outdated. Unfortunately my forecast about the updated version has been wrong, due to a delay of leakers. I noticed the community is trying to keep it up through this thread, I'm happy about that. Obviously I'll release the new tool as soon as possible.

    Cheers :good: