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:
Riff BOX JTAG drivers + Driver Signature Enforcement Overrider
Motorola qboot utility v2.4
Motorola qboot utility lollipop update [thanks to @ilikered]
Motorola USB drivers
Motorola Fastboot
An official Motorola Moto G firmware (4.4.4)
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!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-----------------------------------------------------------------------------------------------------------------
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:
Official 4.4.4?
Ok, but where can I get an official 4.4.4 firmware? I can't find any.
tomDienes said:
Ok, but where can I get an official 4.4.4 firmware? I can't find any.
Click to expand...
Click to collapse
http://www.filefactory.com/folder/c6cdedc45a775d27
Here! if you got a XT1032 the best choice right now is the retail version of Brazilian 4.4.4
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.
diosdiablo said:
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.
Click to expand...
Click to collapse
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
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
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 . . .
maurote said:
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 . . .
Click to expand...
Click to collapse
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.
Thanks !!
After charge, everything is ok...
THANKS PEOPLE !!
You're welcome
Guys I forgot to tell you can easily downgrade once you flashed a 4.4.4 ROM. I installed the Brazilian retail then downgraded to 4.4.3, then 4.4.2. Once you downgraded to 4.4.2 you can switch to GPE or whatever you want
Sent from my XT1032 using XDA Premium 4 mobile app
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?
This thread is about hard bricked devices... I don't know about Verizon phones anyway, I'm in Europe...
Sent from my XT1032 using XDA Premium 4 mobile app
Ooops. My bad. Posted in wrong section. Sorry
No problem
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:
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.
Click to expand...
Click to collapse
if i open my device and 'remove' battery i will get "qhsusb_bulk" on connect?
hansdepaula said:
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:
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?
Click to expand...
Click to collapse
Can you still use fastboot or your device is completely dead?
i can use fastboot, but none i have flash, work..
i cant acess recovery or flash a new recovery..
fastboot say ok, but nothing change on device..
my custom boot logo or a black recovery dont change never..
i try flash more that 50 diferent firmwares..
see my help thread, you dont will waste much time..
http://forum.xda-developers.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228
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.
oversleeper said:
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.
Click to expand...
Click to collapse
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.
hansdepaula said:
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.
Click to expand...
Click to collapse
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.
Unlock The Motorola G (Moto G) Bootloader! doesnt work. Flash doesnt work.
ok This is what I did.
Go Motorola Moto G 3rd Gen. Android 5.0.1, than I download the KingRoot App, to uninstall some bloadware apps. was fine. than few days ago, I updated Motorola to Android 6. Next day I watched some youtube videos and it went to hard reset mode. Since than I can do nothing. Cant unlock the boot loader even with the code from Motorola. Cant flash it just nothing. Im out of ideas. Would like to take a hammer and just smash it. Please someone help me. And I cant turn on the developer mode. take a look on the error which I get, over and over and over again.
C:\Users\Nikon\Desktop\adb-fastboot-latest_win_linux>adb reboot-bootloader
error: device '(null)' not found
C:\Users\Nikon\Desktop\adb-fastboot-latest_win_linux>fastboot devices
ZY2225JZ7Z fastboot
C:\Users\Nikon\Desktop\adb-fastboot-latest_win_linux>adb reboot-bootloader
error: device '(null)' not found
C:\Users\Nikon\Desktop\adb-fastboot-latest_win_linux>fastboot oem fb_mode_set
...
OKAY [ 0.130s]
finished. total time: 0.140s
C:\Users\Nikon\Desktop\adb-fastboot-latest_win_linux>fastboot flash partition gp
t.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.090s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.600s
C:\Users\Nikon\Desktop\adb-fastboot-latest_win_linux>fastboot flash bootloader b
ootloader.img
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.270s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing rpm ...
OKAY [ 1.850s]
finished. total time: 2.130s
C:\Users\Nikon\Desktop\adb-fastboot-latest_win_linux>fastboot flash bootloader b
ootloader.img
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.250s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing rpm ...
OKAY [ 1.890s]
finished. total time: 2.150s
C:\Users\Nikon\Desktop\adb-fastboot-latest_win_linux>fastboot flash logo logo.bi
n
target reported max download size of 268435456 bytes
sending 'logo' (917 KB)...
OKAY [ 0.220s]
writing 'logo'...
OKAY [ 0.180s]
finished. total time: 0.410s
C:\Users\Nikon\Desktop\adb-fastboot-latest_win_linux>fastboot flash boot boot.im
g
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.680s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.350s
C:\Users\Nikon\Desktop\adb-fastboot-latest_win_linux>fastboot flash recovery rec
overy.img
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.670s]
writing 'recovery'...
OKAY [ 1.410s]
finished. total time: 2.090s
C:\Users\Nikon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system syste
m.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (261561 KB)...
OKAY [ 8.290s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.970s
C:\Users\Nikon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system syste
m.img_sparsechunk.1
target reported max download size of 268435456 bytes
sending 'system' (262142 KB)...
OKAY [ 8.310s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.440s
C:\Users\Nikon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system syste
m.img_sparsechunk.2
target reported max download size of 268435456 bytes
sending 'system' (262140 KB)...
OKAY [ 8.310s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.470s
C:\Users\Nikon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system syste
m.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (240126 KB)...
OKAY [ 7.620s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.710s
C:\Users\Nikon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system syste
m.img_sparsechunk.4
target reported max download size of 268435456 bytes
sending 'system' (242526 KB)...
OKAY [ 7.700s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.820s
C:\Users\Nikon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system syste
m.img_sparsechunk.5
target reported max download size of 268435456 bytes
sending 'system' (121656 KB)...
OKAY [ 3.910s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 4.030s
C:\Users\Nikon\Desktop\adb-fastboot-latest_win_linux>fastboot flash modem NON-HL
OS.bin
< waiting for device >
target reported max download size of 268435456 bytes
sending 'modem' (36932 KB)...
OKAY [ 1.170s]
writing 'modem'...
OKAY [ 2.430s]
finished. total time: 3.620s
C:\Users\Nikon\Desktop\adb-fastboot-latest_win_linux>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.060s]
finished. total time: 0.070s
C:\Users\Nikon\Desktop\adb-fastboot-latest_win_linux>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.030s]
finished. total time: 0.030s
C:\Users\Nikon\Desktop\adb-fastboot-latest_win_linux>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (1923 KB)...
OKAY [ 0.250s]
writing 'fsg'...
OKAY [ 0.170s]
finished. total time: 0.420s
C:\Users\Nikon\Desktop\adb-fastboot-latest_win_linux>fastboot erase cache
erasing 'cache'...
OKAY [ 0.130s]
finished. total time: 0.140s
C:\Users\Nikon\Desktop\adb-fastboot-latest_win_linux>fastboot reboot
rebooting...
Please someone help
plz tell me you didnt flash an android 5.0 bootloader.img on a device that has been previously updated to 6.0 .. . If you did then you may have hard bricked it. Try downloading 6.0 firmware
therealduff1 said:
plz tell me you didnt flash an android 5.0 bootloader.img on a device that has been previously updated to 6.0 .. . If you did then you may have hard bricked it. Try downloading 6.0 firmware
Click to expand...
Click to collapse
Thank you for your Info. never thought that it would be so quick here. So yesterday I downloaded android 6, did the flashing again. and it works fine now.
So for all the other Motorola Moto G 3rd generations users.
When you root the phone in Android 5, and you update it with official OTA Android 6, don't root the phone again with some App like KingRoot, as the phone OS might be bricked. Also to flash the Motorola, in that status which I got. You don't need the boot loader unlocking code from Motorola, eather you don't need to activate developer mode. Just download Android 6, and flash it. FASTBOOT DEVICES - code to be sure your phone is recognize it by your PC.
Thanks again to the XDA people and (therealduff1) which help me very quick
I was on latest stock German retail firmware and unlocked the bootloader and then tried to flash twrp via fastboot. Somehow the recovery didn't boot
and I've tried to reflash stock 5.1 firmware. Now the partition table or bootloader seems broken:
It reports Bootloader 41.1A in fastboot and "Device is UNLOCKED. Status Code: 3"
Using the stock flash method every partition seems to be gone:
All partitions report back: "(bootloader) has-slot:xxx: not found", I can still format system partition.
Code:
[email protected]:/.../stock # fastboot flash partition gpt.bin
(bootloader) has-slot:partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.046s]
writing 'partition'...
(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...
OKAY [ 0.326s]
finished. total time: 0.372s
[email protected]:/.../stock # fastboot flash motoboot motoboot.img
(bootloader) has-slot:motoboot: not found
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.141s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.081s]
finished. total time: 1.222s
[email protected]:/.../stock # fastboot flash logo logo.bin
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (295 KB)...
OKAY [ 0.089s]
writing 'logo'...
OKAY [ 0.102s]
finished. total time: 0.192s
I only have Linux systems around to play with adb and fastboot. No chance to use blankflash windows tools. Any idea how I can unbrick the phone?
Depending on the distro, root is required to run fastboot properly. For example, in Ubunutu the command is: sudo fastboot devices
"root" is in front of the command line
Hi,
I wanted to use the method described here to flash the last update to my Pixel3a, stuck to the october update : https://forum.xda-developers.com/t/...ut-twrp-take-ota-updates-once-rooted.3929053/
I did everything described, but the update doesn't work.
Here what I have in the end of the flash process on the CMD window :
Code:
target reported max download size of 268435456 bytes
sending 'bootloader' (8373 KB)...
OKAY [ 0.265s]
writing 'bootloader'...
(bootloader) Flashing Pack version b4s4-0.3-6863017
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition cmnlib_b
(bootloader) Flashing partition cmnlib64_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition storsec_b
OKAY [ 0.235s]
finished. total time: 0.525s
rebooting into bootloader...
OKAY [ 0.053s]
finished. total time: 0.053s
target reported max download size of 268435456 bytes
sending 'radio' (73372 KB)...
OKAY [ 1.734s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g670-00084-201008-B-6891501
(bootloader) Flashing partition modem_b
OKAY [ 0.550s]
finished. total time: 2.309s
rebooting into bootloader...
OKAY [ 0.063s]
finished. total time: 0.074s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: b4s4-0.3-6863017
Baseband Version.....: g670-00084-201008-B-6891501
Serial Number........: [HIDDEN FOR THIS POST]
--------------------------------------------
checking product...
OKAY [ 0.061s]
checking version-bootloader...
OKAY [ 0.059s]
checking version-baseband...
OKAY [ 0.055s]
sending 'boot' (65536 KB)...
OKAY [ 1.519s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 1.982s
Press any key to exit...
I see that the "fail" happens while writing 'boot' but I ignore while it does fail. *
Could you please help me ?
Thanks in advance.
oldbear3 said:
Hi,
I wanted to use the method described here to flash the last update to my Pixel3a, stuck to the october update : https://forum.xda-developers.com/t/...ut-twrp-take-ota-updates-once-rooted.3929053/
I did everything described, but the update doesn't work.
Here what I have in the end of the flash process on the CMD window :
Code:
target reported max download size of 268435456 bytes
sending 'bootloader' (8373 KB)...
OKAY [ 0.265s]
writing 'bootloader'...
(bootloader) Flashing Pack version b4s4-0.3-6863017
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition cmnlib_b
(bootloader) Flashing partition cmnlib64_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition storsec_b
OKAY [ 0.235s]
finished. total time: 0.525s
rebooting into bootloader...
OKAY [ 0.053s]
finished. total time: 0.053s
target reported max download size of 268435456 bytes
sending 'radio' (73372 KB)...
OKAY [ 1.734s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g670-00084-201008-B-6891501
(bootloader) Flashing partition modem_b
OKAY [ 0.550s]
finished. total time: 2.309s
rebooting into bootloader...
OKAY [ 0.063s]
finished. total time: 0.074s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: b4s4-0.3-6863017
Baseband Version.....: g670-00084-201008-B-6891501
Serial Number........: [HIDDEN FOR THIS POST]
--------------------------------------------
checking product...
OKAY [ 0.061s]
checking version-bootloader...
OKAY [ 0.059s]
checking version-baseband...
OKAY [ 0.055s]
sending 'boot' (65536 KB)...
OKAY [ 1.519s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 1.982s
Press any key to exit...
I see that the "fail" happens while writing 'boot' but I ignore while it does fail. *
Could you please help me ?
Thanks in advance.
Click to expand...
Click to collapse
Did you try flashing the system image instead of the OTA? Also did you try a different cord?
MoistPicklez said:
Did you try flashing the system image instead of the OTA? Also did you try a different cord?
Click to expand...
Click to collapse
Sorry, in fact I use the factory image because there is no flash_all.bat in the OTA zip.
I will try with another cord but I'd be surprised it would change anything, as all other operations worked well with this cable...
Also, I can't enter in recovery mode : when I enter into recovery mode, I don't have any options : it says "No Command"... I don't know why.
Ok i tried the other way with OTA updates via recovery.
Thanks for yout help !
I want to flash my Motorola fusion+ phone with official firmware... I have downloaded flash firmware from official site and tried to flash it using RSDlite but the device is not showing there ..
I have installed Motorola adb drivers dowloaded from their site (Version 6.4.0 )
Also I have tried using adb devices command but it doesnt show any devices connected but when I use fastboot devices command in cmd 1 device is showing...
I don't know whats wrong with it....
I am using windows 10 os...
Thanks in advance
You can only access phone by means od ADB if "USB debug" got enabled in Android Settings -> Developer options & phone got rebooted afterwards.
jwoegerbauer said:
You can only access phone by means od ADB if "USB debug" got enabled in Android Settings -> Developer options & phone got rebooted afterwards.
Click to expand...
Click to collapse
But my phone is stuck in bootloop and can't able to boot and change developer settings Also I am not able to get into recovery mode
Because Fastboot is working, as you say, it should be possible to re-flash phone's Stock ROM.
jwoegerbauer said:
Because Fastboot is working, as you say, it should be possible to re-flash phone's Stock ROM.
Click to expand...
Click to collapse
Yes but I don't know how to re-flash using fastboot.
Motorola One Fusion Plus XT2067-2 Stock ROM Firmware (Flash File)
Download the official Motorola One Fusion Plus XT2067-2 Stock Firmware (Flash File) for your Motorola Smartphone. We also provide all other Motorola Stock Firmware.
motostockrom.com
jwoegerbauer said:
Motorola One Fusion Plus XT2067-2 Stock ROM Firmware (Flash File)
Download the official Motorola One Fusion Plus XT2067-2 Stock Firmware (Flash File) for your Motorola Smartphone. We also provide all other Motorola Stock Firmware.
motostockrom.com
Click to expand...
Click to collapse
I have tried to flash it downloaded from above link but I am getting some errors. I have sent you a message with the errors.
I don't react on PMs. Publsh them here.
jwoegerbauer said:
I don't react on PMs. Publsh them here.
Click to expand...
Click to collapse
But please I really need your help...
I have tried to run the flashfile.bat
and I didn't understand are there any errors
I am attaching the executed script... Please help
max-sparse-size: 268435456
finished. total time: 0.013s
...
OKAY [ 0.003s]
finished. total time: 0.012s
target reported max download size of 805306368 bytes
sending 'partition' (206 KB)...
OKAY [ 0.014s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.367s]
finished. total time: 0.394s
target reported max download size of 805306368 bytes
sending 'bootloader' (13800 KB)...
OKAY [ 0.382s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'storsec.mbn' to 'storsec'
(bootloader) - flashing 'uefi_sec.mbn' to 'uefisecapp'
(bootloader) - flashing 'prov64.mbn' to 'prov'
(bootloader) - flashing 'aop.mbn' to 'aop'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'qupfw.elf' to 'qupfw'
(bootloader) - flashing 'xbl_config.elf' to 'xbl_config'
(bootloader) - flashing 'xbl.elf' to 'xbl'
OKAY [ 0.239s]
finished. total time: 0.625s
target reported max download size of 805306368 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ 0.003s]
writing 'vbmeta_a'...
(bootloader) WARNING: vbmeta_a anti rollback downgrade, 5 vs 6
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.105s
target reported max download size of 805306368 bytes
sending 'radio' (96861 KB)...
OKAY [ 2.142s]
writing 'radio'...
(bootloader) Validating 'radio.default.xml'
(bootloader) Committing 'radio.default.xml'
(bootloader) - flashing 'NON-HLOS.bin' to 'modem'
(bootloader) - flashing 'fsg.mbn' to 'fsg'
(bootloader) - erasing 'modemst1'
(bootloader) - erasing 'modemst2'
OKAY [ 0.498s]
finished. total time: 2.647s
target reported max download size of 805306368 bytes
sending 'bluetooth_a' (660 KB)...
OKAY [ 0.017s]
writing 'bluetooth_a'...
OKAY [ 0.018s]
finished. total time: 0.040s
target reported max download size of 805306368 bytes
sending 'dsp_a' (32768 KB)...
OKAY [ 0.764s]
writing 'dsp_a'...
OKAY [ 0.144s]
finished. total time: 0.919s
target reported max download size of 805306368 bytes
sending 'logo_a' (5944 KB)...
OKAY [ 0.154s]
writing 'logo_a'...
OKAY [ 0.168s]
finished. total time: 0.337s
target reported max download size of 805306368 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 2.051s]
writing 'boot_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.396s
target reported max download size of 805306368 bytes
sending 'dtbo_a' (24576 KB)...
OKAY [ 0.590s]
writing 'dtbo_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.721s
target reported max download size of 805306368 bytes
sending 'recovery_a' (65536 KB)...
OKAY [ 1.583s]
writing 'recovery_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.146s
target reported max download size of 805306368 bytes
sending 'super' (524144 KB)...
OKAY [ 15.207s]
writing 'super'...
(bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing super image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.324s
target reported max download size of 805306368 bytes
sending 'super' (524284 KB)...
OKAY [ 12.658s]
writing 'super'...
(bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing super image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 12.797s
target reported max download size of 805306368 bytes
sending 'super' (524284 KB)...
OKAY [ 12.552s]
writing 'super'...
(bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing super image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 12.666s
target reported max download size of 805306368 bytes
sending 'super' (524284 KB)...
OKAY [ 16.994s]
writing 'super'...
(bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing super image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 17.109s
target reported max download size of 805306368 bytes
sending 'super' (487576 KB)...
OKAY [ 11.650s]
writing 'super'...
(bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing super image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 11.764s
target reported max download size of 805306368 bytes
sending 'super' (501408 KB)...
OKAY [ 12.024s]
writing 'super'...
(bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing super image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 12.175s
target reported max download size of 805306368 bytes
sending 'super' (524284 KB)...
OKAY [ 12.555s]
writing 'super'...
(bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing super image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 12.679s
target reported max download size of 805306368 bytes
sending 'super' (394924 KB)...
OKAY [ 9.476s]
writing 'super'...
(bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing super image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 9.592s
erasing 'carrier'...
OKAY [ 0.010s]
finished. total time: 0.012s
erasing 'userdata'...
OKAY [ 1.270s]
finished. total time: 1.276s
erasing 'metadata'...
OKAY [ 0.009s]
finished. total time: 0.013s
erasing 'ddr'...
OKAY [ 0.010s]
finished. total time: 0.012s
target reported max download size of 805306368 bytes
sending 'bluetooth_a' (660 KB)...
OKAY [ 0.060s]
writing 'bluetooth_a'...
OKAY [ 0.030s]
finished. total time: 0.103s
...
OKAY [ 0.002s]
finished. total time: 0.004s
-------------------------------------------------------------------------
please scroll up and check your flash for any errors
-------------------------------------------------------------------------
Press any key to continue . . .
Why it fails is mentioned
Code:
bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing super image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
Before flashing you have to disable dm-verity and/or AVB using Fastboot
Example code
Code:
fastboot devices
fastboot --disable-verity --disable-verification flash vbmeta <vbmeta.img>
what you've to do with all existing vbmeta images, of course
jwoegerbauer said:
Why it fails is mentioned
Code:
bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing super image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
Before flashing you have to disable dm-verity and/or AVB using Fastboot
Example code
Code:
fastboot devices
fastboot --disable-verity --disable-verification flash vbmeta <vbmeta.img>
what you've to do with all existing vbmeta images, of course
Click to expand...
Click to collapse
after trying below command I am getting this result....
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
target reported max download size of 805306368 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ 0.004s]
writing 'vbmeta_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.099s
Smithanthony said:
after trying below command I am getting this result....
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
target reported max download size of 805306368 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ 0.004s]
writing 'vbmeta_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.099s
Click to expand...
Click to collapse
Seems to me vbmeta.img you passed to fastboot isn't suitable.
jwoegerbauer said:
Seems to me vbmeta.img you passed to fastboot isn't suitable.
Click to expand...
Click to collapse
I have downloaded the right firmware of the same model number.
So what should I do now?
To be honest: IDK
Can you please tell me, Is this happening because of any motherboard issue or is motherboard damaged or it is only android problem?
I don't what could be the problem with your phone. But it stuck on the Moto logo I would recommend you to do a factory reset once. You may lose your data in it but you may get your phone back.
To-Do factory Reset Try this:-
1. Press and hold the power + volume down button until some sort of text appears on the screen.
2. Then by using the volume button navigate to Recovery mode and then press the power button to select it.
3. No command screen will appear.
4. Then hold the power button and just press the volume up button once.
5. You will be in Recovery mode.
6. Select the factory reset option and press the power button.
Then Restart your phone.
If it worked for you give a like.
Hope it may help someone save their phone without need to change motherboard.
Try this for more reference:- https://forum.xda-developers.com/t/...stall-firmware-moto-g9-play-official.4316641/