yashsingh1/xdaforums huggingface dataset:
[Moto G Original Android Development] Sandivisi:
if my moto g brought to motorola services center it can be fixed?

I am still not sure if they could, and therefore I have not brought my phone to motorola services center in my country, when I spoke many things to them, they just say "bring it here first your moto g"

please answer this question so I am more confident to bring my phone to Services Center, no matter what with mooney, which is important my phone could live again. [MENTION=5659583]GI0\/\NNI[/MENTION]
[Moto G Original Android Development] Boss442:
Yes it will repair, in worst case they change the motherboard, but it will be expensive.

Or, if you wait, you will had the repair for 0$ when The oficial 5.0 comes, you choose
[Moto G Original Android Development] Sandivisi:
thank you very much, now I've got a choice.

I still have one more question,

if I take my phone to service center, if it took a long time (a few days) to fix or just a few hours.
[Moto G Original Android Development] Boss442:
Depend on your service center
[Moto G Original Android Development] :
okay so i dont understand it quite well...but the thing right now is we need motoboot.img of 5.0? is that right?
[Moto G Original Android Development] Boss442:
Yep
[Moto G Original Android Development] sonwilu:
Brick. Help me please

i brick mi moto g when i try come back of 5.0 to 4.4.2, what MCI i need? 5.0? another question, the rar of mb.CI 4.4.4 i can't extract, can somebody pass me a good link or solution?
[Moto G Original Android Development] ralp88:
you must sent guarentee or wait about 2 months for 5.0 mbci folder. thats what i did on monday
[Moto G Original Android Development] Myrtana:
Why 2 months?
[Moto G Original Android Development] ralp88:
maybe more maybe less. boss442 said this 1 or 2 pages ago
[Moto G Original Android Development] gregbradley:
Thread closed at OP request
[Moto G Original Android Development] Upo_hu:
Is there a way that we can "backup" something from our working phone and when imei=0 appears than we just "restore" to get back original imei?
[Moto G Original Android Development] Boss442:
At the moment no, because we don't know where become the problem, if someone that have the imei 0 problem and can't use the phone wants to send me the phone i can check it and maybe i can find something that repairs the error, or find the source of the problem...
[Moto G Original Android Development] vientodearena:
Hi, in my computer, the device (moto g) is connected and i look "qhsusb_bulk", install the driver but change the port com number and i look the message "the driver is not intended for this platform", who is the error?? My windows 7 its 32bits. Sorry for my bad english.
[Moto G Original Android Development] vientodearena:
Ok problem solved. Add the drivers works on win7 32 bit.

The moto g turn on to fastboot mode (failed to initialize partition table)
[Moto G Original Android Development] kaz93:
HI, if my phone can enter recovery but then it goes blank..can i use this tool? Because my phone light sensor suddenly has problem, so I reboot and then it wont boot into system, It can enter recovery but goes blank..reflashing stock also failed at sparsechunk files. I was on 4.4 rooted btw. I flashed 4.3 stock because xt1033 dont have 4.4 image yet.
[Moto G Original Android Development] vientodearena:
For the correctly flash (enter to fastboot mode vol- and power button):

fastboot flash partition gpt.bin

fastboot flash motoboot motoboot.img

fastboot reboot-bootloader

fastboot flash logo logo.bin

fastboot flash boot boot.img

fastboot flash recovery recovery.img

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

Depends of the version you need type (for the problem with sparsechunk files):

para 4.4 EU

fastboot flash system system.img_sparsechunk.0

fastboot flash system system.img_sparsechunk.1

fastboot flash system system.img_sparsechunk.2

para 4.4 US

fastboot flash system system.img_sparsechunk1

fastboot flash system system.img_sparsechunk2

fastboot flash system system.img_sparsechunk3

para 4.3

fastboot flash system system.img

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

And continue with these commands:

fastboot flash modem NON-HLOS.bin

fastboot erase modemst1

fastboot erase modemst2

fastboot flash fsg fsg.mbn

fastboot erase cache

fastboot erase userdata

fastboot reboot

If you need custom recovery rename the file of the custom recovery (CWM...) to "recovery.img" for reflasing with:

fastboot flash recovery recovery.img
[Moto G Original Android Development] ebsbow:
Hi Boss442, I accidentally ran the BLBROKER bat file right out of the rar file.. Now the device doesn't do anything..

Windows detects an device but doesn't recognize it, the device also doesn't boot anymore..

Please tell me this can be fix? Help?

edit; OK, I have run over the procedure in the post above using the script. It boots again! Thank you!
[Moto G Original Android Development] sprockkets:
Question, if I intentionally break the bootloader to have it go into recovery, can I do this to go from an aio bootloader to a retail one so I can flash in a stock firmware instead?
[Moto G Original Android Development] Boss442:
what aio bootloader? i only know the retail bootloader, and yes, reinstalling the bootloader you will need to flash the stock firmware
[Moto G Original Android Development] sprockkets:
As it is the bootloader won't allow me to flash files from the retail firmware, but only the aio carrier firmware. So what you are saying is, I'd have to use the boot.img from the aio firmware and not the retail since it still can check for this?
[Moto G Original Android Development] Boss442:
try repairing the bootloader with the files from retail firmware. Maybe will allow flash
[Moto G Original Android Development] sprockkets:
It seems that the motoboot.img is universally accepted but the other files fail validation. Was worth a try.
[Moto G Original Android Development] Boss442:
Yes fail validation but still flash and work
[Moto G Original Android Development] sinkadorable:
my moto g was unlocked and rooted. now cannot boot into rom and just stuck at unlock warning message. when i try to enter recovery it just bootlooping at unlock warning message too

can i use this tool to recover my phone

i wish u help me to recover my phone

if u want contact me. please find me in Facebook
[Moto G Original Android Development] vardhanram:
unable to activate the emergency downloader

i was destroy my moto g bootloader to activate the emergency downloader...

now my phaone is dead not responding...

how can i activate the emergency downloader...

pls help me
[Moto G Original Android Development] Boss442:
Follow the tutorial, is the only way to make it work

Enviado desde mi Moto G mediante Tapatalk
[Moto G Original Android Development] vardhanram:
unable to run blank-flash.bat

drivers installed manuvally ... but i am not sure working properly...?

i am stuck in blanl-flash.bat

waiting for device....
[Moto G Original Android Development] vardhanram:
After Flash Stock Firmware unable to boot up

first ....Sorry for my bad english and i am using Moto G XT1033

i did all steps... what u mentioned above

i used following firmwares(4.4 & 4.3)

1) RETAIL-AS_FALCON_KXB20.25-1.31_cid7_CFC_1FF.xml

2) fastboot_falcon_asia_ds_user_4.3_14.10.0Q3.X-84-7-LCG-4_4_release-keys-cid7-AsiaRetail_03

i flashed every thing is correctly by manual

i executed each cmd carefully and finished with "OKAY" massage....

after rebooting it will struck in boatloader warning logo, after 5 sec., ful black screen was appeared ... after 5sec., restarting...

and same thing happen continuously....

i faced this problem last 15days back

now i was hope less...

i dont know what should i do now...

plz help me out of this problem..

my contact details

Facebook - Vardhan Ram(vardhan.plus@gmail.com) from nellore

G+ - vardhan.plus@gmail.com
[Moto G Original Android Development] ceyad:
following the tutorial and now my moto G cannot boot to fastboot, and recognized as Zeus flash device

what should i do to repair it?
[Moto G Original Android Development] Boss442:
How you brick the phone? you reach the fastboot, flash the firmware and before the phone doesnt work?

Are you using my drivers? on devices administrators select manually the driver, and search "Qualcomm HS-USB QDLoader 9008"
[Moto G Original Android Development] Erovia:
[MENTION=4749802]Boss442[/MENTION]: Hi, my Moto G was bricked so I had to run your BLBROKE script. It finished as it should, I've installed the Qualcomm driver, my pc sees the phone as "Qualcomm HS-USB QDLoader 9008 (COM10)".

The problem is when I execute the blank-flash.bat it says "opening device: \\.\COM10" a few times and it gives a "FAILED (blank-flash:device-open:serial-open:could not open device)" error.

I've tried all usb ports and the error is the same.

I'm open to any idea. Thanks!
[Moto G Original Android Development] Boss442:
push the power on button & conect the usb, and try again
[Moto G Original Android Development] danilocps87:
Guys, I signed the driver, but every time I try to "update driver", it changes the port to a com number and i look the message "the driver is not intended for this platform"...

I already tried on 3 differents computers, running, XP 32bits, Win7 32bits and Win8 32bits...

In this way, I can't use the qbtm because it stuck at <waiting for device>

Please, anybody can help me.
[Moto G Original Android Development] sprockkets:
There was a different driver I had to use, it was posted somewhere in this thread I think. The whole signing thing is kinda weird/dumb. Only vista and up on 64 bit editions require signing, and if you don't want it to enforce it, the directions could just have you hit F5 and boot without driver verification.

But whatever.
[Moto G Original Android Development] vientodearena:
Look the page 4 and test this driver (work on my windows7 32 bits):

http://xdaforums.com/attachment.php?attachmentid=2627620&d=1394671732
[Moto G Original Android Development] danilocps87:
It's alive!!!

It works! Now it boots to fastboot mode. I flashed only GPT and Motoboot, and I was able to enter recovery again (TWRP). I restored a backup, but it was stucked at bootlogo...

So, now I'm doing a backup from the internal memory (using adb pull command). When it will done, I'll flash all the others partitions, reinstall CM11 and restore the backup again.

Thank you all for the help!!! :highfive:
[Moto G Original Android Development] danilocps87:
Guys, I already installed CM11 again and restore backup.

All is working fine, but, I can't delete or copy new files into folders from internal storage using file manager apps or ADB... it is saying me that I need root permissions.

I already renew super user permissions, and use the "fix permissions" option in recovery, but doesn't solve it.

I can delete or copy files in the root of internal storage, but in folders not...

When using MTP or into TWRP recovery, I can delete or write files...

I think it can be a folders permissions issue, but I can't change the permissions too.

Any tip about how to solve it?
[Moto G Original Android Development] vientodearena:
I think, you have su (bin) busybox etc in xbin folder?
[Moto G Original Android Development] danilocps87:
I don't know what caused it, but I solved it just deleting all the internal storage content and coping again from pc using MTP. (previously I was coping using ADB push command).
[Moto G Original Android Development] tseptiana:
I've run "blank-flash.bat" but getting problems as attached image.

Please help.

Thanks
[Moto G Original Android Development] Boss442:
Some have the problem but i cannot replicate this, what is your model? mine is xt1032
[Moto G Original Android Development] SamsungAdmire:
fixed
[Moto G Original Android Development] tseptiana:
yes it's Moto G 8gm dual sim a.k XT1032
[Moto G Original Android Development] Erovia:
[MENTION=4532285]SamsungAdmire[/MENTION]: I've had the same issue. Repeatedly plugged the device in and out and eventually it's been recognized. This worked for me more than once.
[Moto G Original Android Development] m_loaiza:
error

from Boss442 to XDA

opening device: \\.\COM38

OKAY [ 0.003s]

greeting device for command mode

OKAY [ 0.001s]

identifying device

...serial = 0x2E83504

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

...chip-rev = 0x0

...sv-sbl = 0x0

OKAY [ 0.006s]

finding files

...programmer = programmer.mbn

...singleimage = singleimage.bin

OKAY [ 0.005s]

validating files

OKAY [ 0.002s]

switching to download mode

OKAY [ 0.001s]

greeting device for image downloading

OKAY [ 0.002s]

sending programmer

OKAY [ 0.012s]

flashing singleimage

FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)

Presione una tecla para continuar

any idea? or solution
[Moto G Original Android Development] thefO_Okupkid:
one>fastboot flash motoboot motoboot.img

'fastboot' is not recognized as an internal or external command,

operable program or batch file.

yelp
[Moto G Original Android Development] Boss442:
install fastboot
[Moto G Original Android Development] vientodearena:
You need (fastboot.exe, adbwinapi.dll and/or adb.exe) (and .img files to flash) in one folder to be installed fastboot. In windows you press shift key + right click in the mouse and select open command (prompt, cmd) window here, for send the comands fastboot in theame folder where you have the fastboot and img files.
[Moto G Original Android Development] m_loaiza:
still dead my moto g

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 have windows 7 64 bit
[Moto G Original Android Development] estanenmi:
Can use this por adaptar for Nexus 5???

Enviado desde mi XT1032 mediante Tapatalk
[Moto G Original Android Development] Boss442:
Really i don't know, and i dont have a nexus to probe if i can port it. On moto x works
[Moto G Original Android Development] estanenmi:
not works on nexus, maybe need other files!!! :(
[Moto G Original Android Development] Boss442:
maybe need work to port it to Nexus, add me on Google+ or Facebook and will talk

Enviado desde mi Moto G mediante Tapatalk
[Moto G Original Android Development] tseptiana:
that all have the same issue, any idea for this problems? please help.

Thanks
[Moto G Original Android Development] Guicrith:
Can someone test for me fastboot get_unlock_data after corrupting and recovering the bootloader but before flashing anything else.(trying to find a way to unlock CDMA prepaid moto g)
[Moto G Original Android Development] carpon:
thats what i get when i use bootloader bricker tool .. any help ?
[Moto G Original Android Development] Boss442:
seems like your phone is really broken. i have one that i cannot repair with the same problem, what do you do to brick the phone like this?
[Moto G Original Android Development] carpon:
literally nothing !

just was using the phone as a USB tether suddenly it reboots by it self and stuck on Bootloader unlocked warning

tried to do a wipe through TWRP it completed then i was able to boot into room again but it freezed at some point when you have to choose language .. rebooted into recovery tried to perform another one it says " can't mount sd "

i went to fastboot .. i thind i did this command " erase all "

after all of this i can't do anything ,, it keeps says what mentioned above
[Moto G Original Android Development] Boss442:
i think emmc is blown, so do you havnt warranty?

contact to me on google+
[Moto G Original Android Development] sinkadorable:
cannot flash stock firmware after run bootloader bricker. how to solve this? :/
[Moto G Original Android Development] Boss442:
Try again, push the power button before flashing
[Moto G Original Android Development] HaGeK:
I have the same problem:

opening device: \\.\COM3

OKAY [ 0.004s]

greeting device for command mode

OKAY [ 0.002s]

identifying device

...serial = 0x1BA7E90

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

...chip-rev = 0x0

...sv-sbl = 0x0

OKAY [ 0.014s]

finding files

...programmer = programmer.mbn

...singleimage = singleimage.bin

OKAY [ 0.010s]

validating files

OKAY [ 0.002s]

switching to download mode

OKAY [ 0.002s]

greeting device for image downloading

OKAY [ 0.003s]

sending programmer

OKAY [ 0.012s]

flashing singleimage

FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)

Presione una tecla para continuar . . .

I use windows 7 64bit

any idea?
[Moto G Original Android Development] peporras:
Another one with the same problem

Originally Posted by m_loaiza View Post

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)

And A-novo deny me the warranty is somehow have access to phone and data is now handled know that if I have a large brick
[Moto G Original Android Development] carpon:
i don't

i added you into my circles now

thnx dude
[Moto G Original Android Development] sinkadorable:
So what step must i do?
[Moto G Original Android Development] AlmapekeDj:
Hi, im use the BLBRICK and i can´t recover my Moto g, my pc didn´t detect the phone, sound when the phone is plug to the pc but, nothing happen. Its posible recover the Moto G? Sorry for for my very, very bad english :D
[Moto G Original Android Development] Boss442:
if the pc sounds when the phone is plugged is because its recognized

the same, but before pluging the phone on the pc push 2 sec. the power button
[Moto G Original Android Development] HaGeK:
Be careful that the application blbrick leaves terminal unusable because the qboot application fails.

Many users still have waiting a solution for the brick.

Please do not use the blbrick, I say caution.

Sorry for my english

Thanks
[Moto G Original Android Development] peporras:
Any solution?

we're screwed ostia
[Moto G Original Android Development] Boss442:
If only you and the other people read at the bottom of the post...

ATM i cannot reply this type of "bug" that the people had, tested on 2 motoG (xt1032 & xt1034) and works on the two

Maybe can try this:

-Put "qualcomm_boot_tool" on C:\

-Open cmd and do this:

cd C:\qualcomm_boot_tool

if your phone is MSM8226:

qboot.exe blank-flash programmer.mbn singleimage.bin

if your phone is MSM8626:

qboot.exe blank-flash programmer_8626.mbn singleimage_8626.bin
[Moto G Original Android Development] AlmapekeDj:
Hey, thx for all, my Moto G nos full working
[Moto G Original Android Development] Guicrith:
greeting device for command mode

OKAY [ 0.006s]

identifying device

...serial = 0x25E258B

...chip-id = 0x801 (MSM8626)

...chip-rev = 0x0

...sv-sbl = 0x0

OKAY [ 0.005s]

finding files

...programmer = programmer_8626.mbn

...singleimage = singleimage_8626.bin

OKAY [ 0.004s]

validating files

OKAY [ 0.001s]

switching to download mode

OKAY [ 0.002s]

greeting device for image downloading

OKAY [ 0.002s]

sending programmer

OKAY [ 0.013s]

flashing singleimage

FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)

wont flash please help
[Moto G Original Android Development] oversleeper:
Same here:

from Boss442 to XDA

opening device: \\.\COM6

OKAY [ 0.005s]

greeting device for command mode

OKAY [ 0.002s]

identifying device

...serial = 0x3B93E14

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

...chip-rev = 0x0

...sv-sbl = 0x0

OKAY [ 0.006s]

finding files

...programmer = programmer.mbn

...singleimage = singleimage.bin

OKAY [ 0.005s]

validating files

OKAY [ 0.001s]

switching to download mode

OKAY [ 0.002s]

greeting device for image downloading

OKAY [ 0.003s]

sending programmer

OKAY [ 0.011s]

flashing singleimage

FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)

Why doesn't work?
[Moto G Original Android Development] hansdepaula:
i have a xt1033 br

my device show a "USB\VID_05C6&PID_9025&MI**"

and driver your post dont have suport for that..

definitely my fastboot as corrupted..

this d'nt write nothing on my device..

where i can download the 'VID_05C6&PID_9025' drivers?

someone have a idea?

see details:

i make a thread about my proble, maybe you can help me: http://xdaforums.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228/post53917374
[Moto G Original Android Development] carpon:
I sent you A message on G+

My profile

https://plus.google.com/u/0/
[Moto G Original Android Development] Boss442:
Just force it to use the quallcom driver...

I will check :)
[Moto G Original Android Development] oversleeper:
I tried the flashblank tool from 4.4.2 package but i got the same error... I think we'll need the one from 4.4.4 pack or a modified file to make it work with v41.13 bootloader.
[Moto G Original Android Development] sinkadorable:
hey guys now i can enter cwm recovery. how to flash rom using recovery
[Moto G Original Android Development] hansdepaula:
no work for me.. :/

my device dont go to emergency mode..

i try flash te second tool to break my bootloader, but not work..

my bootloader dont write nothing,, :/

i think my eMMC as bronked, maybe.

on device boot (it stay on logo loop), my pc see 5 'ports' for my device, but no one work for this tool..

adb see my device too, but on unathorized state..

img:

some one have a idea to change unathorized state?

o another mode to go on emergency mode? a key combination maybe..

i'm waiting, but with less hope.. :/
[Moto G Original Android Development] oversleeper:
It's unauthorized because you don't have access to device in order to authorize your pc to debugging with ADB. ADB will never works in a bricked device. I think you will need the blank flash image of the v41.13 bootloader that all us are waiting for.

The errors we get:

FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)

and

FAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet)

are probably due to old singleimage.bin (made for the v41.11 bootloader), we upgraded to 4.4.4 therefore we need a new singleimage.bin for v41.13 bootloader. I can extract the new one from a 4.4.4 firmware package but till now the latest I found is 4.4.2. I guess we have to wait weeks or months...
[Moto G Original Android Development] Guicrith:
How do you extract a new one.
[Moto G Original Android Development] oversleeper:
The tool is inside every tar.gz package of official Motorola firmware.
[Moto G Original Android Development] HaGeK:
Please, when who knowns the way of being able flash this image for the new bootloader, to share it hereabouts, I have the mobile KO already two weeks and need it to work: (
[Moto G Original Android Development] Astinog:
I was monitoring the battery life of my Moto G and I let it lost the whole battery charge. So after the phone shut down I crearly put it to recharge. I pluged it to my computer with HIS OWN usb cable. The 0% image of the battery showed up but after that, the phone didn't turn on! I tryed to use the adapter to plug in a normal home socket but nothing changed! I'm really worried now, cause I don't know what to do.

I tryed to plug in it back to the computer and the LED showed up but then nothing again. What can I do now?
[Moto G Original Android Development] hansdepaula:
i try take parts of 4.4.4 ota, d'nt work for me..

my fastboot dont write nothing..

but try, maybe work for you..

like it, see:

http://forum.xda-develope[/MENTION]rs.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228/page2