It's possible to force downgrade bootloader from 5.0 to 4.4.4, or better to 4.4.2 with this method in working devices, not bricked ones?
@Falcon G my phone still not booting on bootloader
i think this guide not work on new bootloader android 5.0
look this pic, i follow your guide. this right?It will work on 5.0 if you see qhsusb_bulk when you plug in your phone
# MSM8626
[config 0x801]
programmer=programmer_8626.mbn
singleimage=singleimage_8626.bin
[config 0x805]
programmer=programmer_8926.mbn
singleimage=singleimage_8926.bin
[diag error.0x010B0C0D]
count=2
message="blank-flash:sdl-transfer-image:sdl-hello:error reading packet"
last-seen="Mon Dec 08 13:03:37 2014, SE Asia Standard Time"
first-seen="Mon Dec 08 12:29:14 2014, SE Asia Standard Time"
chip=MSM8226
chip.sn=0x306CBE3
chip.id=0x800
chip.rev=0
chip.sv-sbl=0
qboot.version=2.4
hostname=SANDY-PC
[diag blank-flash]
fail=3
pass=0
yield=0.00%
dphu=100.00
[diag error.0x010B0C13]
count=1
message="blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame"
last-seen="Mon Dec 08 13:04:29 2014, SE Asia Standard Time"
first-seen="Mon Dec 08 13:04:29 2014, SE Asia Standard Time"
chip=MSM8226
chip.sn=0x306CBE3
chip.id=0x800
chip.rev=0
chip.sv-sbl=0
qboot.version=2.4
hostname=SANDY-PC
I have the same problem. I installed brazilian soak test, then set 4.4.2 and updated on OTA to 4.4.4, during installation my device is dead. Now in Task Manager Qualcomm HS-USB QDLoader 9008. Probably i think need this utility for 5.0 bootloader, MBM-CL or qboot, i do not know....see pic again,
and this after i run blankflash.bat
Code:# MSM8626 [config 0x801] programmer=programmer_8626.mbn singleimage=singleimage_8626.bin [config 0x805] programmer=programmer_8926.mbn singleimage=singleimage_8926.bin [diag error.0x010B0C0D] count=2 message="blank-flash:sdl-transfer-image:sdl-hello:error reading packet" last-seen="Mon Dec 08 13:03:37 2014, SE Asia Standard Time" first-seen="Mon Dec 08 12:29:14 2014, SE Asia Standard Time" chip=MSM8226 chip.sn=0x306CBE3 chip.id=0x800 chip.rev=0 chip.sv-sbl=0 qboot.version=2.4 hostname=SANDY-PC [diag blank-flash] fail=3 pass=0 yield=0.00% dphu=100.00 [diag error.0x010B0C13] count=1 message="blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame" last-seen="Mon Dec 08 13:04:29 2014, SE Asia Standard Time" first-seen="Mon Dec 08 13:04:29 2014, SE Asia Standard Time" chip=MSM8226 chip.sn=0x306CBE3 chip.id=0x800 chip.rev=0 chip.sv-sbl=0 qboot.version=2.4 hostname=SANDY-PC
maybe i give up now, because no dev or someone cant help us!I have the same problem. I installed brazilian soak test, then set 4.4.2 and updated on OTA to 4.4.4, during installation my device is dead. Now in Task Manager Qualcomm HS-USB QDLoader 9008. Probably i think need this utility for 5.0 bootloader, MBM-CL or qboot, i do not know....
see pic again,
and this after i run blankflash.bat
Code:# MSM8626 [config 0x801] programmer=programmer_8626.mbn singleimage=singleimage_8626.bin [config 0x805] programmer=programmer_8926.mbn singleimage=singleimage_8926.bin [diag error.0x010B0C0D] count=2 message="blank-flash:sdl-transfer-image:sdl-hello:error reading packet" last-seen="Mon Dec 08 13:03:37 2014, SE Asia Standard Time" first-seen="Mon Dec 08 12:29:14 2014, SE Asia Standard Time" chip=MSM8226 chip.sn=0x306CBE3 chip.id=0x800 chip.rev=0 chip.sv-sbl=0 qboot.version=2.4 hostname=SANDY-PC [diag blank-flash] fail=3 pass=0 yield=0.00% dphu=100.00 [diag error.0x010B0C13] count=1 message="blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame" last-seen="Mon Dec 08 13:04:29 2014, SE Asia Standard Time" first-seen="Mon Dec 08 13:04:29 2014, SE Asia Standard Time" chip=MSM8226 chip.sn=0x306CBE3 chip.id=0x800 chip.rev=0 chip.sv-sbl=0 qboot.version=2.4 hostname=SANDY-PC
maybe i give up now, because no dev or someone cant help us!
i will bought my moto g to service center motorola, tommorrow maybe
hope my device get back.
yes, it is on XT-1033Hi is this the XT1033 you are running blankflash on?
Have you unzipped all the files to a folder.
Also have you tried switching the usb cable with a different one.
so just wait until someone can help us
Are you sure this is contains the 5.0 bootloader image or 4.4.4?Hi is this the XT1033 you are running blankflash on?
Have you unzipped all the files to a folder.
Also have you tried switching the usb cable with a different one.
Yes it works with 5.0 boot loader (41.3 or something)Are you sure this is contains the 5.0 bootloader image or 4.4.4?
These errors the ppl get if they tried to install the OTA to 4.4.4 from 4.4.2 are due to bootloader downgrade which ofc doesnt work.Now they need the 5.0 bootloader to blankflash it and get the devices working.
Can you confirm which version you're offering in the OP?
Nope.Yes it works with 5.0 boot loader (41.3 or something)
Sent from my XT1031 using Tapatalk
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot devices
a0918259 fastboot
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot flash bootl
oader motoboot.img
target max-sparse-size: 256MB
sending 'bootloader' (1953 KB)...
OKAY [ 0.100s]
writing 'bootloader'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.127s
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot flash parti
tion gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.023s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.367s
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>fastboot boot recover
y.img
downloading 'boot.img'...
OKAY [ 0.339s]
booting...
FAILED (remote failure)
finished. total time: 0.343s
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot boot recove
ry.img
downloading 'boot.img'...
OKAY [ 0.342s]
booting...
FAILED (remote failure)
finished. total time: 0.346s
This works to a small degree. It fixes the brick part and gets to boot-loader, but that's as far as it'll go. It'll give either a "Permission Denied" or a "Preflash Validation Failed" or a "Remote Failure" for every and any file you try to flash or boot into afterwards, be it in fastboot or mfastboot.
Code:C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\ RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot devices a0918259 fastboot C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\ RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot flash bootl oader motoboot.img target max-sparse-size: 256MB sending 'bootloader' (1953 KB)... OKAY [ 0.100s] writing 'bootloader'... (bootloader) Permission denied FAILED (remote failure) finished. total time: 0.127s C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\ RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot flash parti tion gpt.bin target max-sparse-size: 256MB sending 'partition' (32 KB)... OKAY [ 0.023s] writing 'partition'... (bootloader) Preflash validation failed FAILED (remote failure) finished. total time: 0.367s C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\ RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>fastboot boot recover y.img downloading 'boot.img'... OKAY [ 0.339s] booting... FAILED (remote failure) finished. total time: 0.343s C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\ RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot boot recove ry.img downloading 'boot.img'... OKAY [ 0.342s] booting... FAILED (remote failure) finished. total time: 0.346s
@Lucas Eugene or anyone else, I have the same problem. If I can know if there is hope or now I'm already satisfied. Thanks!
# MSM8626
[config 0x801]
programmer=programmer_8626.mbn
singleimage=singleimage_8626.bin
[config 0x805]
programmer=programmer_8926.mbn
singleimage=singleimage_8926.bin
[diag error.0x010B0C0D]
count=2
message="blank-flash:sdl-transfer-image:sdl-hello:error reading packet"
last-seen="Mon Dec 08 13:03:37 2014, SE Asia Standard Time"
first-seen="Mon Dec 08 12:29:14 2014, SE Asia Standard Time"
chip=MSM8226
chip.sn=0x306CBE3
chip.id=0x800
chip.rev=0
chip.sv-sbl=0
qboot.version=2.4
hostname=SANDY-PC
[diag blank-flash]
fail=3
pass=0
yield=0.00%
dphu=100.00
[diag error.0x010B0C13]
count=1
message="blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame"
last-seen="Mon Dec 08 13:04:29 2014, SE Asia Standard Time"
first-seen="Mon Dec 08 13:04:29 2014, SE Asia Standard Time"
chip=MSM8226
chip.sn=0x306CBE3
chip.id=0x800
chip.rev=0
chip.sv-sbl=0
qboot.version=2.4
hostname=SANDY-PC
Unbrick Your Device
What is A Brick?
A Brick Usually Occurs when you Flash a Wrong Firmware on your device or you try to downgrade your bootloader. In both the cases if you see nothing but a blank screen and "qhsusb_bulk" when connecting to the computer (Check Devices and Printers on your PC) .
Prerequisites
- Stock Moto G Firmware of your Choice
- Motorola USB Drivers
- MFastbootv2
- Blanflash
- RiffBox JTAG Drivers
INSTRUCTIONS
If you have A 64-Bit Processor you'll need to disable driver signature Enforcement. Press F8 while the computer is booting and then choose the option.
- Go To Start and search for Device Manager
- Plug in your Moto G
- You'll See qhsusb_bulk
- Now select update driver Software
- Choose from the Riffbox Jtag Drivers.
- Now you'll see Qualcomm HS-USB QLoader 9008
- Unzip the motorola qboot utility and run blankflash.bat
- Now Enter into fastboot from your Moto g
- You can now flash the firmwares compatible with your bootloader version