yashsingh1/xdaforums huggingface dataset:
[Moto G Q&A, Help & Troubleshooting] 20111161:
For people stucked in Lollipop hard bricked, have you guys try this out: http://xdaforums.com/moto-g/orig-development/bootloader-tool-motoflasher-t2959076

A guy sent me this link on G+ community. But I don't bring my phone home so can't try this!
[Moto G Q&A, Help & Troubleshooting] qd42:
It's only a tool that makes flashing easier, It's can't repair phone without mbm-ci files.
[Moto G Q&A, Help & Troubleshooting] thatoneguydownthestreet:
oh please. most people here haves spent upwards of 2 months.

if there is no solution for everyone else what makes you think that you telling us your story will change anything.
[Moto G Q&A, Help & Troubleshooting] reiseb:
It's simple. Unfollow this thread subscription and let us in peace!
[Moto G Q&A, Help & Troubleshooting] tbkbone:
Subscribing here and waiting for MBM-CI 5 to unbrick my Moto G... Hope they publish it soon.
[Moto G Q&A, Help & Troubleshooting] daniel84cs:
+1
[Moto G Q&A, Help & Troubleshooting] supertonino:
:good:
[Moto G Q&A, Help & Troubleshooting] thatoneguydownthestreet:
If you haven't noticed I am also looking for a way to fix my G. This thread is supposed to be for legitimate questions, not questions that have been asked hundredths of times.

When the method comes over sleeper will inform us, for now we can only wait. And creating 1000 pages of useless material will only get this thread shut down.
[Moto G Q&A, Help & Troubleshooting] mashaal95:
Help please?

My device shows a "device descriptor request failed" on my pc, its running windows 8.1, does this have to be done only on windows 7?

Or is my device bricked beyond repair? :(
[Moto G Q&A, Help & Troubleshooting] qd42:
Did you followed instructions from the first post in this thread (disable drivers signature check, install Riff BOX JTAG drivers, etc.)?
[Moto G Q&A, Help & Troubleshooting] mashaal95:
I didn't even get that qhsusb_bulk as my device when I first started putting the usb connection to my phone!
[Moto G Q&A, Help & Troubleshooting] benek1988:
Try press power more than 20 seconds or vol+/vol- with power.

Wysłane z mojego Nexus 7 przy użyciu Tapatalka
[Moto G Q&A, Help & Troubleshooting] thatoneguydownthestreet:
remember you have to go to devices and printers to look at the device
[Moto G Q&A, Help & Troubleshooting] mascote9rc:
put device to charge untill the LED light turn off, remove from charger, press and hold volume up and connect, i always do that!

i guess that happen because there's many variants of XT103X, some of them use power button, some volume up...
[Moto G Q&A, Help & Troubleshooting] mashaal95:
Thank you so much! But now its failing the blank flash for some reason, the LED lights start blinking and then I have to start the whole process again, whats the problem now?
[Moto G Q&A, Help & Troubleshooting] Silvermatrix:
is there any method for detecting device in UBUNTU ?

it is detected as ->

Bus 002 Device 094: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

but when i tried with qboot it is stuck with waiting for devices... even after specifying the port

rnztx@RnzTx-PC:blankflash$ ./qboot.exe --port=/dev/ttyUSB0 blank-flash
< waiting for device >
[Moto G Q&A, Help & Troubleshooting] ffosilva:
1st) Why are you using qboot.exe instead qboot? (Or... how you made qboot.exe working on linux?!!)

2nd) You need to be root to run qboot or add a udev rule for vid:05c6 pid:9008 to able your user to unrestricted access.

You don't need to specify a port if you have only one Qualcomm device in 9008 mode connected to your computer.
[Moto G Q&A, Help & Troubleshooting] mascote9rc:
the reason is: bootloader corrupted, only a new mbm-CI 5.0 could rewrite yr bootloader, gain access to fastboot and flash any rom again...

appreciate your feedback, but all people here in this thread have tried this with the same result. please wait the OP update first post.
[Moto G Q&A, Help & Troubleshooting] Silvermatrix:
1]

root@RnzTx-PC:blankflash$ ./qboot blank-flash
bash: ./qboot: cannot execute binary file: Exec format error

2] i have wine installed.. and making "chmod +x qboot.exe qboot" allowed me to run on UBUNTU BUT even with root

root@RnzTx-PC:blankflash$ ./qboot.exe blank_flash
< waiting for device >

that problem exist...

think may be i need to find Windows PC
[Moto G Q&A, Help & Troubleshooting] mnhs1010:
Unbricking is not possible from those guys in market who have jtag z3x devices etc etc for various purposes? If YES pls tell me will make round to market :P
[Moto G Q&A, Help & Troubleshooting] ffosilva:
Your Linux is 64-bit?
[Moto G Q&A, Help & Troubleshooting] Silvermatrix:
nope 32bit.
[Moto G Q&A, Help & Troubleshooting] ffosilva:
This is why you can't run. qboot is an x86_64 binary.
[Moto G Q&A, Help & Troubleshooting] pfufle:
First, uninstall all your drivers related to your device from device manager, and then reinstall them again...Also, try connecting your Phone to a windows 7 PC with necessary drivers installed...The second method should definitely work...
[Moto G Q&A, Help & Troubleshooting] brav09:
I tried to connect it to a Windows 7 PC, install all drivers, but still got the same problem (error code 43, can't update driver). By the way, what do you mean by using another driver, oversleeper? I can't install the driver since the Windows said the driver is already up to date. :\

And finally here are the screenshots:
[Moto G Q&A, Help & Troubleshooting] keviiinn:
is there anything that can be done if the phone is totally bricked? meaning it won't charge, it won't turn on, there's no LED light when plugged in, and a computer won't even recognize it if it's plugged in via USB?
[Moto G Q&A, Help & Troubleshooting] oversleeper:
Uninstall that driver and try those drivers I linked... If still doesn't work I can't help sorry.

It's not bricked... it's dead if computer doesn't recognize the phone at least as qhsusb_bulk. I think nothing can be done by you. Send it to motorola or sell it for replace parts:(
[Moto G Q&A, Help & Troubleshooting] :
Unplug moto g, then press power for more than 30 seconds, then connect usb, and press volume down+power for 30 seconds or more again, then it should connect!
[Moto G Q&A, Help & Troubleshooting] albertowen_acid:
Downgrade bootloader ver!

Hello! Thanks u for this tut, but i did not find info about downgrade moto g bootloader version. So, can u answer me how can i downgrade my boot

P.S.: I have xt1031 and i forgot read spc before flashing to 4.4.4 so i need downgrade

Thanks
[Moto G Q&A, Help & Troubleshooting] synclicious:
i get this weird error and cant find it anywhere :(

D:\Desktop\MBM-CI_4.4.4>qboot.exe blank-flash
opening device: \\.\COM10
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.004s]
greeting device for command mode
ReadFile() failed, error=31
opening device: \\.\COM10
opening device: \\.\COM10
opening device: \\.\COM10
OKAY [ 0.004s]
greeting device for command mode
OKAY [ 0.004s]
identifying device
Unexpected packet: 4. Was expecting: 14
FAILED (blank-flash:sahara-chip-stat:unexpected packet)

D:\Desktop\MBM-CI_4.4.4>

sometimes it show this

D:\Desktop\MBM-CI_4.4.4>qboot.exe blank-flash
opening device: \\.\COM10
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.005s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.005s]
greeting device for command mode
FAILED (blank-flash:greet-device:error reading packet)
[Moto G Q&A, Help & Troubleshooting] MotoZilla:
please post a link for 4.4.4. thank you

please post a link to 4.4.4
[Moto G Q&A, Help & Troubleshooting] BenvdH:
Problems with flashing software

this is the device info

(bootloader) version: 0.5

(bootloader) version-bootloader: 4113(*)

(bootloader) product: falcon

(bootloader) secure: yes

(bootloader) hwrev: 0x83C0

(bootloader) radio: 0x1

(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17

(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb

(bootloader) cpu: MSM8226 CS

(bootloader) serialno: 251803d6

(bootloader) cid: 0xFFFF

(bootloader) channelid: 0xDEAD

(bootloader) uid: 76523A020F000000000000000000

(bootloader) unlocked: Not supported

(bootloader) iswarrantyvoid: Not supported

(bootloader) mot_sst: 8

(bootloader) max-download-size: 536870912

(bootloader) reason: Failed to initialize partition t

(bootloader) imei:

(bootloader) meid:

(bootloader) date:

(bootloader) sku:

(bootloader) iccid:

(bootloader) cust_md5:

(bootloader) max-sparse-size: 268435456

(bootloader) current-time:

(bootloader) ro.build.fingerprint:

(bootloader) ro.build.version.full:

(bootloader) ro.build.version.qcom:

(bootloader) version-baseband:

(bootloader) kernel.version:

(bootloader) sdi.git:

(bootloader) sbl1.git:

(bootloader) rpm.git:

(bootloader) tz.git:

(bootloader) aboot.git: git=MBM-NG-V41.13-0-g7dc8e78

(bootloader) qe:

(bootloader) ro.carrier:

all: listed above

finished. total time: 0.047s

Press any key to continue . . .

this is what it says when i try to flash the brazillian 4.4.4

(bootloader) version: 0.5

(bootloader) version-bootloader: 4113(*)

(bootloader) product: falcon

(bootloader) secure: yes

(bootloader) hwrev: 0x83C0

(bootloader) radio: 0x1

(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17

(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb

(bootloader) cpu: MSM8226 CS

(bootloader) serialno: 251803d6

(bootloader) cid: 0xFFFF

(bootloader) channelid: 0xDEAD

(bootloader) uid: 76523A020F000000000000000000

(bootloader) unlocked: Not supported

(bootloader) iswarrantyvoid: Not supported

(bootloader) mot_sst: 8

(bootloader) max-download-size: 536870912

(bootloader) reason: Failed to initialize partition t

(bootloader) imei:

(bootloader) meid:

(bootloader) date:

(bootloader) sku:

(bootloader) iccid:

(bootloader) cust_md5:

(bootloader) max-sparse-size: 268435456

(bootloader) current-time:

(bootloader) ro.build.fingerprint:

(bootloader) ro.build.version.full:

(bootloader) ro.build.version.qcom:

(bootloader) version-baseband:

(bootloader) kernel.version:

(bootloader) sdi.git:

(bootloader) sbl1.git:

(bootloader) rpm.git:

(bootloader) tz.git:

(bootloader) aboot.git: git=MBM-NG-V41.13-0-g7dc8e78

(bootloader) qe:

(bootloader) ro.carrier:

all: listed above

finished. total time: 0.047s

Press any key to continue . . .

and it says hab check failed for recovery on my moto g

plz help me :(:(
[Moto G Q&A, Help & Troubleshooting] c43211:
Problem

I get this:

'C:\Moto G>mfastboot.exe flash partition gpt.bin

target max-sparse-size: 256MB

sending 'partition' (32 KB)...

OKAY [ 0.060s]

writing 'partition'...

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 0.433s'

Is there a fix?
[Moto G Q&A, Help & Troubleshooting] BitingChaos:
Wow, people seem to just make up or change terms as they go.

When a device is bricked, it's broken. It's a good as a brick (hence the term "brick"). For all intents and purposes, this is permanent. The only way you can recover from a bricked device usually requires something like soldering additional components to the device, such as a JTAG cable, since the device is unable to operate.

Some how, this concept seemed too difficult for some people to understand. If a device didn't boot because you accidentally toggled the wrong setting, instead of simply changing the setting back or wiping your config, people would just say they "bricked" their device. Invalid config? Bricked! Deleted ntdetect.com from your laptop? Bricked! Firefox won't open? Bricked!

Because so many people kept saying they "bricked" something for every stupid system issue, it really made the word lose any value.

Enter the "hard brick". Because "brick" is a now a destroyed word because of its incorrect use, people started using "hard brick" to describe an actual bricked device. Something you cannot simply fix through software.

Now I see your post. Congratulations. You're now helping to destroy the meaning of "hard brick". How the heck can a "hard brick" be fixed by simply running an app and re-installing some software? If you can get the device working as easily as that, then it was NEVER BRICKED in the first place.

http://en.wikipedia.org/wiki/Brick_(electronics)

I appreciate that you're trying to help people, but a device that can be fixed by loading software to it through its regular USB connection isn't anywhere close to being bricked.
[Moto G Q&A, Help & Troubleshooting] oversleeper:
I don't agree with your statement. According to Wikipedia a device can be called "bricked" if it doesn't work due to misconfiguration, wrong firmware, and so on.

My device, as described by Wiki, was like dead, there was no way to turn it on. To resolve this I used JTAG drivers not released from Motorola and a special tool that rewrites the bootloader, so I think this is enough to call it "hard bricked". Usually we call "soft bricked" a device that doesn't turn on but fixable by flashing the correct firmware, "hard bricked" when the device is basically dead, but (maybe) still fixable with a low level access to the internal memory. I don't think that "hard bricked" = "broken", otherwise people could just say "broken".
[Moto G Q&A, Help & Troubleshooting] brav09:
Didn't work. Is there any way to bring it back to life? Maybe with Linux? Mac OS? Or maybe you can explain me about what it does so I'll have more ideas about what I'm doing (somehow I make a new way to fix it). Sounds kinda crazy, but anyway, nothing to lose. I also searched to other forums and sites but seems like they do the same.

(I don't believe if my Moto G is completely dead, as it still shows some signs of life.)
[Moto G Q&A, Help & Troubleshooting] KaaPaa:
Good job

there is same problem with razr m xt907 can anybody make same tool for xt907?
[Moto G Q&A, Help & Troubleshooting] shinta90:
problem

Device is LOCKED. status code: 0

device info tool:

[IMG="device info tool"]http://xdaforums.com/attachment.php?attachmentid=2976183&stc=1&d=1413670723[/IMG]

i try to unlock but not work

[IMG="try unlock"]http://xdaforums.com/attachment.php?attachmentid=2976184&stc=1&d=1413670723[/IMG]

what can i do ?
[Moto G Q&A, Help & Troubleshooting] :
What's your current bootloader version?

Try flashing a gpt.bin from 4.4.4
[Moto G Q&A, Help & Troubleshooting] c43211:
I didn't read the last bit of your post about flashing the gpt.bin from 4.4.4, thanks. I hope this works.
[Moto G Q&A, Help & Troubleshooting] :
Good luck :) thanksbuttonnn xD
[Moto G Q&A, Help & Troubleshooting] DrTangalanga3:
Hey, I have a problem. I can't unlock it, stays in status code: 0. And my IMEI number is deleted, I don't know why. I can't unlock the bootloader. Can you help me, please?
[Moto G Q&A, Help & Troubleshooting] prz0007:
mfastboot flash motoboot motoboot.img starting from this command nothing flashes it sends ok but it failed at write

error message failed remote failure what could it be and what can I do thanks
[Moto G Q&A, Help & Troubleshooting] Silvermatrix:
i just installed windows 8 X64 but now stuck with these Errors. May be that other thread is wrong.. it only works with Moto G. not for Moto E

opening device: \\.\COM4
OKAY [ 0.004s]
greeting device for command mode
OKAY [ 0.003s]
identifying device
...serial = 0x3AD4049
...chip-id = 0x811
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.011s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.007s]
validating files
OKAY [ 0.002s]
switching to download mode
OKAY [ 0.003s]
greeting device for image downloading
OKAY [ 0.004s]
sending programmer
OKAY [ 0.014s]
flashing singleimage
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet)

C:\Users\RnzTx\Downloads\other\condor_unbrick\blankflash>pause
Press any key to continue . . .
[Moto G Q&A, Help & Troubleshooting] falcon1033:
Waits over

Got my phone now with new board covered under warranty ...:D
[Moto G Q&A, Help & Troubleshooting] daniel84cs:
Woow now send my MotoG to Motorola dont whait for MBM files , thanks for the news...:)
[Moto G Q&A, Help & Troubleshooting] ejpe17:
ALGUNA sOLUCION

ANY SOLUTION TO REVIVE MY Motog ??? WHEN THE DANE VOLVI OF A 4.4.4 5.0.1 ....

Any solution ?????????????????? Porfa tell me What If ... T_T

---------------------------------------------------------------------------------------------------------

ALGUNA SOLUCION PARA REVIVIR MI MOTOG??? LO DAÑE CUANDO VOLVI DE 5.0.1 A 4.4.4....

Alguna solucion?????????????????? Porfa diganme que si... T_T
[Moto G Q&A, Help & Troubleshooting] tri_vis:
I also got my phone with replaced motherboard from service center, covered under warranty.

So now not gonna playing it with as warranty is now over as one year passed after purchasing.

:D
[Moto G Q&A, Help & Troubleshooting] Silvermatrix:
you were rooted ?

and how much time do They Take for Service ?
[Moto G Q&A, Help & Troubleshooting] LyfL3ss:
seems like they wont release mbm-ci :(
[Moto G Q&A, Help & Troubleshooting] redbull93:
I tried this in Germany and my phone was immediately shipped back to me, unrepaired. They quickly noticed, that I unlocked the Bootloader and that the software has been changed ... but maybe you will be luckier than me ;)
[Moto G Q&A, Help & Troubleshooting] hananmeer:
4.4.4 mbm ci file also came almost after 2-3 months of release.. so we still have to wait long for it i guess..

Sent from my XT1032
[Moto G Q&A, Help & Troubleshooting] falcon1033:
Yes

Rooted and unlocked bootloader...they don't understood what's the problem is and told that the board was shorted...so they gave it to motorola and replaced the board..:good:
[Moto G Q&A, Help & Troubleshooting] mascote9rc:
is where are the sources of motorola? is sure that the mbm files will be there when lenovo motorola release the fw?
[Moto G Q&A, Help & Troubleshooting] ffosilva:
Until these files are not leaked, the future is uncertain. All previous versions have firmware package with mbm-ci included (except 4.4.3). Based on this fact we can expect a package with mbm-ci released soon (or not [emoji14])
[Moto G Q&A, Help & Troubleshooting] MadL1fe:
Moto G the best phone i'v seen, motorola the best company...i believe they will not throw us
[Moto G Q&A, Help & Troubleshooting] rohanraarora:
Try your luck at Service Center !!

Hi i was also dealing with the same issue.

Before getting a new device i thought of getting my moto g checked by authorized service center. As expected these guys were not able to get the issue itself, but that's the cool part :laugh:. They can't turn on the device to check whether it is unlocked or not and fortunately they were too busy to check online and replaced the whole whole with a new one :p.

Now my device is as good as new with a locked bootloader ;)

So i will advice you guys to go out and give it a try :).
[Moto G Q&A, Help & Troubleshooting] :
I tried sending mine in for repair this week and unfortunately the german repair service seems to check if the device was previously unlocked. I don't really believe anymore that there will be a leak anytime soon so I'm going to send it in again and ask for a quote on the repair (I'm going to guess 60€ max? since the device itself can be had for as low as 120€ by now).
[Moto G Q&A, Help & Troubleshooting] hananmeer:
does the 4.4.3 users r still locked like us? (who downgraded at that time) or 4.4.4 mbm-CI file helped in fixing it? [just for info] thanks

Sent from my XT1032
[Moto G Q&A, Help & Troubleshooting] tommark75:
Probably yes, but since the 4.4.3 was out for maximum a week or two and really not so many region got the update a really few people can be stucked like us. (Plus the 4.4.3 frimware most likely not going to released anymore but the lollipop will be so we are in a much better position.)
[Moto G Q&A, Help & Troubleshooting] redbull93:
Hey, could you tell me about the costs for repair when you'll now about them? I tried the same and my device was also returned ...
[Moto G Q&A, Help & Troubleshooting] RedChili57:
Could not open device

Hej guys. i have a huge problem. I pluged in my moto g to motoflasher 2.1.2.2 and i have error - Could not open device - ...:(

I was tried everything.. i pressed the power buttor for 2 mins, for 30s ect. , i recharged the baterry..

Led blinks, PC sees moto g like "QUALCOMM loader 9008" but motoflasher has that stupid error...

I know that mbm-ci 5 files arent available at this time, but i wanted to know that my moto g is prepared for reaniamation when lillipop files will comes..

Motoflasher 2.1.2.2 -> FAILED (blank-flash:device-open:serial-open:could not open device)

Bricked form 5.0.2brasil.->4.4.2 gpe -OTA->PHONE IS DEAD

tell me how can i fit it :/

@i want to see this information in my motoflasher.

opening device: \\.\COM38

OKAY [ 0.004s]

greeting device for command mode

OKAY [ 0.003s]

identifying device

...serial = 0x2E83504

...chip-id = 0x800 (MSM8226)

...chip-rev = 0x0

...sv-sbl = 0x0

OKAY [ 0.009s]

finding files

...programmer = programmer.mbn

...singleimage = singleimage.bin

OKAY [ 0.007s]

validating files

OKAY [ 0.001s]

switching to download mode

OKAY [ 0.002s]

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)

I think it is better than could not open device :(
[Moto G Q&A, Help & Troubleshooting] mujahidyousaf:
Are you people sure that MBM CL-5 would be release by motorola?:rolleyes:
[Moto G Q&A, Help & Troubleshooting] ZauCunha:
No
[Moto G Q&A, Help & Troubleshooting] mujahidyousaf:
Plz dont give me heart attack !!! :(
[Moto G Q&A, Help & Troubleshooting] ZauCunha:
Thinking in what I read here until now, we have chance to get the mbm in few months, but no one is sure about it.
[Moto G Q&A, Help & Troubleshooting] ffosilva:
In my opinion it will not be released. :( why? Because every handset launched after xt10xx doesn't have firmwares with mbm-ci released, although it uses same bootloader recovery protocol.
[Moto G Q&A, Help & Troubleshooting] RedChili57:
Could not open

so what can i do if i see error "could not ocen device" im motoflasher? Is it something bad with my moto g? Or maybe it is normal?
[Moto G Q&A, Help & Troubleshooting] ZauCunha:
:/ really sad to know it
[Moto G Q&A, Help & Troubleshooting] mujahidyousaf:
May be MBM CL files for handsets released after xt10** are in process !!!

As Moto G 2014 has firmware with MBM CL files,although released after 1st gen, isnt it ???
[Moto G Q&A, Help & Troubleshooting] Sandivisi:
sayonara moto g :(
[Moto G Q&A, Help & Troubleshooting] naniabhi:
Not recogionsed by pc

My phone is dead and not even recognized by my pc,anything i can do? and any other way to use this on linux?

Thank you
[Moto G Q&A, Help & Troubleshooting] fengjiong:
Hi,I got same problem , did you used the blank flash tool which is for other phones or the wrong version for moto G?
[Moto G Q&A, Help & Troubleshooting] tommark75:
This in one thing, but in the other hand only the brazil/india region got the update to this day. In my opinion wait until the rest of the world got the update. According to some german sites and users they will get the update "very soon" (yea we all know what is that mean at motorola....). Keep our hopes up, and wait until the EU/US release and their frimwares. Hopefully one of them will contain the stuff we need.