Unbrick Hard Bricked Moto G (2nd.Gen) [5.0/4.4.4]

Status
Not open for further replies.
Search This thread

Sandivisi

Senior Member
Jun 12, 2014
650
203
West Java

Attachments

  • 1.png
    1.png
    127.6 KB · Views: 13,727

Sandivisi

Senior Member
Jun 12, 2014
650
203
West Java
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
 

Attachments

  • 2.png
    2.png
    120.1 KB · Views: 9,228
  • 3.png
    3.png
    132.1 KB · Views: 8,980
Last edited:
  • Like
Reactions: Renez1n

MadL1fe

Senior Member
Aug 28, 2014
100
18
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
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....
 

Sandivisi

Senior Member
Jun 12, 2014
650
203
West Java
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....
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.
 

Lucas Eugene

Senior Member
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

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.
 

Sandivisi

Senior Member
Jun 12, 2014
650
203
West Java
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 is on XT-1033
yes, iam also unzipped all the files to a folderbut still no work
i tired all switching the usb cable but still get some problem

I think, this guide not work on new bootloader until someone get MBM-CI from Android 5 or someone create singleimage
In my country no motorola...
so just wait until someone can help us
 

liveroy

Senior Member
Jun 8, 2007
588
188
/dev/null
www.gear-bg.com
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.
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?
 

Lucas Eugene

Senior Member
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?
Yes it works with 5.0 boot loader (41.3 or something)

Sent from my XT1031 using Tapatalk
 

liveroy

Senior Member
Jun 8, 2007
588
188
/dev/null
www.gear-bg.com
Yes it works with 5.0 boot loader (41.3 or something)

Sent from my XT1031 using Tapatalk
Nope.


OKAY [ 1.815s]
identifying device
...serial = 0x23EC8AD
...chip-id = 0x800 (MSM8226)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.007s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.003s]
validating files
OKAY [ 0.026s]
switching to download mode
OKAY [ 0.001s]
greeting device for image downloading
OKAY [ 0.002s]
sending programmer
OKAY [ 0.011s]
flashing singleimage
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet)
 

sumondhk1

Senior Member
Oct 15, 2013
1,170
257
Dhaka
My bootloader v 0x4816.
i have just updated to lollipop based on 1064 firware.
i got 1068.
Is my bootloader for lollipop
 

VictoriousShooter

Senior Member
Jun 11, 2012
753
348
25
Sanford/Lake Mary
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
 
Last edited:
Y

yeshwanthvshenoy

Guest
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

man u atleast got to fastboot but we are still stuck on blank screen...btw did u flash the lollipop ota? wer u on 4.4.4 bootloader or 5.0 bootloadeR?
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    @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!

    You can't do anything else except returning your device to motorola.
    You (im the same boat lol) are stuck in bulk mode 9008,(if you googled you probably found many threads in the lg forums, but in the lg world being stuck in qcom bulk mode means 9006 bulk mode where emmc mounts itself on linux so you could dd firmware back without passing any signature check). which means you need programmer files compatible with your bootloader (saw your method of installing the soak test on xt1068, so i assume your device got bricked that way like mine.) so that would be 6.0
    To be honest i doubt motorola will leak them, so your best (and only) option would be returning it to motorola.
    Hope they accept it ;) (if you plan on sending it to them).
    1
    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?
    1
    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
    1
    Not able to see any See qhsusb_bulk on my 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


    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


    today just now i have flash an other model zip file through twrp in my moto g2
    flashing was successfully but unfortunately i don't know what happen the phone gone through complete blank screen
    i have tried almost 10 times to go through recovery but every time no response the phone not even going through power on by power buttn
    also not a single response for the power bottom tried every key combination for few mins too still no response complete blank screen
    no response while doing charging too
    i think its had hard brick but i am afraid of changing motherboard which is too expensive
    one think that happen good is when i have connect to pc something QHSUB_BULK was detecting on my pc i dont what was that
    completely confused what to do
    after seeing yours thread i have again connected my brick phone to pc but this i am unable to see any QHSUB_BULK
    not any response even on fastboot mode in your ADB command
    pls help if u really have any solution
    thanks in advance :crying: