yashsingh1/xdaforums huggingface dataset:
[Moto G Original Android Development] :
Here you are

http://www.filefactory.com/file/2tk...6-LGG-8_54_release-keys-cid7-Retail_GB.tar.gz

If it doesn't flash try to replace the motoboot.img and gpt.bin inside the firmware folder and try again:

http://puu.sh/aSk6h/83852d88fb.zip

Hit thanks if worked, by the way it's the wrong thread ;)
[Moto G Original Android Development] derekokelly:
Unfortunately, neither solution worked. I know that it's the wrong thread, but I need some answers that could help. You've definitely come the closest so far
[Moto G Original Android Development] :
Okay, one difference is that 4.4.x images are splitted IMG chunks due the partition layout, I guess we need to chunk the system.img first?
[Moto G Original Android Development] derekokelly:
I've given up at this point xD Thank you so much for your help, though. The links you provided above were very close in succeeding.

[size=+2]Thanks again![/size]
[Moto G Original Android Development] :
Use thanks button ;)

I'll try to chunk the system when I'm not busy with school. There is software which can do the trick. But is 4.3 better than 4.4.4??
[Moto G Original Android Development] derekokelly:
I think that stock KitKat is very laggy, and I feel that the Moto G is much more optimised for Jelly Bean.
[Moto G Original Android Development] :
I'll create ASAP (want to try by myself also!) It's alsof my 17th birthday today guys :D
[Moto G Original Android Development] derekokelly:
Happy Birthday! :) I'm only 16 too :P
[Moto G Original Android Development] :
What about this one?

http://www.filefactory.com/file/6jt...14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF_svc.xml.zip

Remember to replace gpt.bin and motoboot.img from 4.4.4
[Moto G Original Android Development] derekokelly:
Downloading now. Taking forever though!

EDIT: Did not work either.
[Moto G Original Android Development] :
Give me a log AND is there one system.img file inside?
[Moto G Original Android Development] derekokelly:
I don't know how to give a log as it does not even boot. No there are 3 system.img's inside
[Moto G Original Android Development] :
With a log i mean CMD, and did you what I told you? First replace gpt.bin and motoboot.img from 4.4.4 inside the 4.3 folder and then run the bat file!
[Moto G Original Android Development] derekokelly:
How do you log..? Yes, I replaced everything you said to replace and it still didn't work.
[Moto G Original Android Development] oversleeper:
Want to downgrade to 4.3? Try this:

1) first flash this

2) then flash this
[Moto G Original Android Development] derekokelly:
I've already tried that, and unfortunately it doesn't work either. However, I will give it another go.

EDIT: Have these been edited in any way or are they completely stock?
[Moto G Original Android Development] oversleeper:
Full stock images, retail GB.
[Moto G Original Android Development] derekokelly:
That doesn't work either.
[Moto G Original Android Development] :
Yeah expected that already! Let me create jellybean, I'll send ASAP! (I'll try EU first okay?)
[Moto G Original Android Development] derekokelly:
That's perfect! Thank you!
[Moto G Original Android Development] pm.mohanani@gmail.com:
getting error while flashing falcon on MOTO G

dear i am Getting Following Error

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

C:\Users\Notebook\Desktop\fastboot>fastboot flash system system.img_sparsechunk1

target reported max download size of 536870912 bytes

sending 'system' (256836 KB)...

OKAY [ 10.369s]

writing 'system'...

(bootloader) Invalid signed image

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 10.839s

C:\Users\Notebook\Desktop\fastboot>fastboot flash system system.img_sparsechunk2

target reported max download size of 536870912 bytes

sending 'system' (243320 KB)...

OKAY [ 9.840s]

writing 'system'...

(bootloader) Invalid signed image

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 9.905s

C:\Users\Notebook\Desktop\fastboot>fastboot flash system system.img_sparsechunk3

target reported max download size of 536870912 bytes

sending 'system' (232905 KB)...

OKAY [ 9.446s]

writing 'system'...

(bootloader) Invalid signed image

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 9.516s

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

can you please guide
[Moto G Original Android Development] :
You need to unlock your bootloader, or flash another firmware!
[Moto G Original Android Development] matmutant:
the following may help :

http://xdaforums.com/showpost.php?p=55658557&postcount=565
[Moto G Original Android Development] pm.mohanani@gmail.com:
Already unlocked n rooted too.

The device is now rebooting in 2 secs.
[Moto G Original Android Development] Boss442:
there is no fix for preflash validation at the moment.

Sorry for let this thread but i dont have time because i study, but im making a more easy app to flash bootloaders:
[Moto G Original Android Development] capitanbiglio:
I followed the instructions but i received this message of error: "target error" and cannot do nothing... any suggestions?
[Moto G Original Android Development] Boss442:
Send me the full log
[Moto G Original Android Development] capitanbiglio:
Here we are. Thanks for your support!

opening device: \\.\COM3
OKAY [ 0.010s]
greeting device for command mode
OKAY [ 0.002s]
identifying device
...serial = 0x21062C4
...chip-id = 0x800 (MSM8226)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.007s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.005s]
validating files
OKAY [ 0.007s]
switching to download mode
OKAY [ 0.001s]
greeting device for image downloading
OKAY [ 0.003s]
sending programmer
OKAY [ 0.013s]
flashing singleimage
Target LOG: Open multi failed, unknown error
Target ERROR: 7 - Open multi failed, unknown error
FAILED (sdl-transfer-image:send-image:sdl-open-multi:target error)
[Moto G Original Android Development] Boss442:
Try with another MBM-CI image, but i'm uploading the new tool, so this thread will be marked as OBSOLETE
[Moto G Original Android Development] capitanbiglio:
I tried with another MBM-CI but i received the 'version error' (due to different firmware).

I look forward to use your tool.

Thank you again!
[Moto G Original Android Development] Boss442:
Did you try pushing Power Button after plugin in?

If this doesnt work, push power button for 20 secs , push power button again and plug in
[Moto G Original Android Development] capitanbiglio:
yes i pushed it but without success :(
[Moto G Original Android Development] Boss442:
Well try to find any 4.3 firmware with 'mbm-ci' folder inside, if this dont work or you can't find anything, chat me on PM
[Moto G Original Android Development] capitanbiglio:
Ok i'll search it and try tonight. But does it make difference if i'm sure i have a 4.4 firmware?

Thanks
[Moto G Original Android Development] :
Doesn't make any sense. I spoke to four guys with this problem. We need 4.4.3 mbm-ci
[Moto G Original Android Development] Boss442:
Well he said me that he had 4.3, we need the firmware that correspond to the most updated android version that he used (officialy)
[Moto G Original Android Development] capitanbiglio:
Sorry maybe i said wrong, but I have the 4.4 in my Moto G. Don't remember if it's 4.4.2 or 4.4.3 or 4.4.4 sorry... i tried with your but nothing to do the error is always the same

OUTPUT*: sending programmer
OUTPUT*: OKAY [ -0.000s]
OUTPUT*: flashing singleimage
OUTPUT*: Target LOG: Open multi failed, unknown error
OUTPUT*: Target ERROR: 7 - Open multi failed, unknown error
OUTPUT*: FAILED (sdl-transfer-image:send-image:sdl-open-multi:target error)
[Moto G Original Android Development] Boss442:
Yes, it will output the same error all the tools because, they use the same method internally, on the programfiles/motoflasher/logs will have all the logs, upload in on a zip and send me please :)

P/S: sdl-hello is the error handled by incorrect MBM-CI targetted, so there is another problem here, PM me and talk me about how the phone stopped working, i will help you
[Moto G Original Android Development] :
The problem is a 4.3 mbm-ci!!! I know four people with same problem.

Trust me!
[Moto G Original Android Development] capitanbiglio:
Sorry guys, so what I have to do? Thanks for your help
[Moto G Original Android Development] :
Bring to Motorola's repair. Or we need to get mbm-ci from 4.3 :(

Switch to Q&A ;)
[Moto G Original Android Development] Boss442:
I don't understand you, you said:

Where is really the problem on 4.3 or 4.4.3?

They Are diferent android versions. On my new tool, i gave it a link for my bug tracker, if the four guys that you know can explain what happened and they can give me his REAL android Versions, and send me a log with the real error.

The error on the other post:

It's my fault, a fail in the new tool that i repaired on 1.6.1.1.

But:

Is a Error that never seen before, and if the real problem is on 4.3 or 4.4.3, i can test it because i can't downgrade anymore (im on 4.4.4) i will see if i find a 4.4.3 firmware....

I wait for you explanation about if the problem is on 4.3 or 4.4.3 :silly:
[Moto G Original Android Development] :
Sorry for confusing post problem is

4.4.3 not 4.3
[Moto G Original Android Development] Boss442:
The problem is that there aren't 4.4.3 firmwares, i found four that im downloading but two of them didnt include mbm-ci :crying:
[Moto G Original Android Development] :
Yeah that's true the problem is:

THERE IS NO 4.4.3 because of the short OTA, Motorola upgraded to 4.4.4 immediately:

This guys have 4.4.3 problem: [MENTION=6121934]fenrizxd[/MENTION]

[MENTION=3117611]angelgzg[/MENTION] [MENTION=5239665]suhridkhan[/MENTION] [MENTION=5248423]lazytrunks[/MENTION] [MENTION=4899957]randras83[/MENTION]

Maybe Lollipop mbm-ci can save them...
[Moto G Original Android Development] Boss442:
if 4.4.4 dont save it, i dont think so...

i work on Personal (A telephone Carrier on my country) and i do the service warranty repairment, i don't have acess to the firmwares but i have a JTAG for moto, maybe if someone that had this problem can send me the phone i will se if i can repair it (or find a way to inject a upgraded bootloader), and if suscefully works, i will add it to my tool.

Before i experiment with my own Moto G, but now he is on 4.4.4 and i can downgrade (i upgraded when 4.4.4 firmwares are coming up for testing the 4.4.4 mbm-ci)
[Moto G Original Android Development] :
That's why I tagged the guys ;)

Maybe you could friendly ask Motorola. Otherwise JTAG is a good idea [MENTION=4899957]randras83[/MENTION] already sent for JTAG.
[Moto G Original Android Development] Boss442:
We only contact Moto for replacement parts, and i didn't do it...

And JTAG had a Hardware Key, so i can't extract the firmwares and another things from it, and i need a broken phone with 4.4.3 for do it.

If i use 4.4.4 it will extract 4.4.4 files, so it will dont work....

p/s: there is no Lollipop support from now, and the support comes 1 or 2 months after the OTA
[Moto G Original Android Development] angelgzg:
I am one that I have that problem, my phone stayed in 4.4.3, and although I flash any rom stock smoothly the phone does not pass the warning bootloader actually installing any recovery, nor can I make brick,

And the computer recognizes me as motorola android device
[Moto G Original Android Development] Boss442:
So you aren't stuck on Emergency download? you can enter to fastboot? are you tryed to flash 4.4.4 bootloader?
[Moto G Original Android Development] :
I helped him with all that already :p no luck. Only solution is JTAG or 4.4.3 mbm-ci
[Moto G Original Android Development] angelgzg:
Yes, flashed 4.4.4 and all versions, and does well but does not start
[Moto G Original Android Development] Boss442:
Well try searching 4.4.3 firmware with mbm-ci, and tell me if you found it, i will help you to repair it if you find one
[Moto G Original Android Development] MadL1fe:
Guy! please help! need 5.0 bootloader ! brazilian soak test! My device is broken! :'(

FAILED (blank-flash:greet-device:error reading packet)
[Moto G Original Android Development] :
I told you to don't do stupid things, now you punished yourself...

However, you have to wait for mbm-ci lollipop or we have to create a singleimage with all the bootloader files.
[Moto G Original Android Development] Sandivisi:
i hape you can create a singleimage with all the bootloader files.

btw your phone got Unbricked? i see on your signature
[Moto G Original Android Development] :
Yes I did. I was on 4.4.4, then I created a custom 4.3 bootloader zip, then it became death. There wheren't any mbm-ci's available so I had to wait 2 months for the 4.4.4 mbm-ci. That fixed my phone without paying Motorola $100 for repair.

However, I nearly bricked it again with lollipop. I formated the lollipop system. The only option was installing custom recovery, then pushed a zip with adb to the phone and flashed it (flashable brazillian XT1033 4.4.4). Then flashed the stock recovery, then the Lollipop OTA and it survived.
[Moto G Original Android Development] MadL1fe:
please make utility, i pay if it will work!

i have 5.0 brazilian soak test, and i downgrade to 4.4.2 and update OTA to 4.4.4...and he dead
[Moto G Original Android Development] bharat_goku:
Could you tell me how to get this mbm-ci folder?or where exactly it is?

I've been searching some factory images and haven't been able to find it i'm not sure where to look for it
[Moto G Original Android Development] Sandivisi:
[MENTION=5659583]GI0\/\NNI[/MENTION] [MENTION=4749802]Boss442[/MENTION]

yes it is true, I hope soon there in solving this serious problem. because a lot of people get phone hardbrick because bootloader corrupt.
[Moto G Original Android Development] :
I'm going to take a look with creating a new singleimage!
[Moto G Original Android Development] Sandivisi:
I'm glad to hear it, keep it up bro.
[Moto G Original Android Development] :
[MENTION=4749802]Boss442[/MENTION]
[MENTION=5659583]GI0\/\NNI[/MENTION]

i will donate if the fix for 5.0 bootloader is done! i swear!!

EDIT : Here are the gpt,emmc_boot,tz,sbi,sbl1 and other mbn and bin files from 5.0 Brazilian firmware. I hope someone makes the fix soon! And can u guys share the method to make it? I can try making one if you guys are busy incase.
[Moto G Original Android Development] :
I had those file already. We need to extract a existing single image. We need to know the compression format etc. It's not that easy man...
[Moto G Original Android Development] :
is there anyway we could know that? what will we do now since http://sbf.droid-developers.org/ website is down? where can we find factory images?
[Moto G Original Android Development] Sandivisi:
keep your eyes on http://www.firmware-team.com/forumdisplay.php?f=14
[Moto G Original Android Development] :
Guys we don't need that, I know you are frustrating and you all want to help but Yeah...

There is not much to do...
[Moto G Original Android Development] Sandivisi:
okay sorry bro
[Moto G Original Android Development] :
yeah man itz hell withput ur facourite device working... i dont know from where we could get the factory images now!
[Moto G Original Android Development] :
Off course I know the feeling!

But we need to wait for Motorola's Factory Images. And remember it's your own mistake! I did it too :) I want to help but first you need to accept the current death phone.
[Moto G Original Android Development] bharat_goku:
I'm not sure but would the factory image of moto g2 lollipop help? I have the motoboot.img of it,but I don't have a clue how to decompile it,using regular method is giving me crap literally
[Moto G Original Android Development] :
No. Stop please. You know that Moto G2 is totally not the same device so all of that won't work. You need a blankflasher!
[Moto G Original Android Development] bharat_goku:
Can u tell me how exactly it's made? Or where do I find it?

I pulled the entire dump more or less before I started testing my recovery which messed up my partition
[Moto G Original Android Development] :
I will take a look but please be patient.
[Moto G Original Android Development] :
thanks a ton i believe that g2's files can work since g1's files work on g2's. there is a thread on g2 forum about unbricking corrupted bootloader for 4.4.4. i believe it is processor related and since both are msm8226 u could use the files, we could nevertheless try.

---------- Post added at 07:16 PM ---------- Previous post was at 07:14 PM ----------

could u please share link of g2's factory firmware image so he could look into it?
[Moto G Original Android Development] :
Will not work. You need signed 5.0 singleimage. Otherwise you get preflash validation failed with qboot.
[Moto G Original Android Development] :
we could atleast try. we dont have much to lose since our devices are already bricked
[Moto G Original Android Development] Boss442:
If you try to flash a different bootloader and your battery die, the factory cable maybe dont work, if you don't have warranty try to disasemble the phone and charge the battery directly with a universal battery charguer, or cut a usb cable (prefeer a wall charger) and make contact with the conector for terminal battery, the phone would read the charger like a battery and maybe would let it flash, if it not, let it charge and try in 1-2 Hours.

Motorola device manager drivers don't work with that...

You read the OP? :mad: this is for devices that don't power on
[Moto G Original Android Development] thewerthon:
Bro, my phone says 'permission denied' on every command i try.

In 'flash gpt gpt.bin' it says: preflash validation failed.

What could I do?

;(
[Moto G Original Android Development] Boss442:
dont flash the gpt.. if still same with others files, use mfastboot
[Moto G Original Android Development] thewerthon:
I figured out that is because i was on kitkat, and once i flashed gpt.bin from kitkat, i cant flash gpt.bin from jelly bean
[Moto G Original Android Development] Boss442:
You need to flash the LAST version did you use, so flash the kitkat system, and later downgrade... if you try to downgrade this dont work
[Moto G Original Android Development] surfino:
having some problems,

in device manager i need to update driver for

- Motorola ADB Interface

or

- Portable Device - XT1032

I signed the *.sys file, but when i try installing Qualcoomm_QDLoader_64bit_Driver it says:

The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.

Any clues?

PS: Using Windows 8.1
[Moto G Original Android Development] denzel09:
Buddy, you have imei=0 problem, not bootloader bricked, why you have using this guide? :confused:
[Moto G Original Android Development] surfino:
ma mi insegui :D

Another guy told me in pvt to also try resetting bootloader as last chance as flashboot getvar all gave me correct imei

(tried everythin, also flashing radios)
[Moto G Original Android Development] denzel09:
Ahah no buddy, ma io vivo qui su xda. Tra telefono e pc sto sempre connesso. Amo xda.

Btw try and let me know buddy so we can all stappare lo spumante :D
[Moto G Original Android Development] tschertel:
I can't get bootloader version using getprop. It shows "unknown" in terminal emulator.

Can I use this tool to fix it?
[Moto G Original Android Development] mobilephone01:
My device does not boot now. Just stop the early boot animation(Motorola Logo) and stoped.

and I think USB debugging is off but I can change this because does not bootup.

Device manager can't see my phone.

Please help me. I don't know what should I do.

My device is unlocked bootloader and rooted. I can go in to the recovery mode but when I go in to the recovery mode . Device go in blank black screen.

My device is bricked or have chance to work again.
[Moto G Original Android Development] Boss442:
The driver don't work on the MTP or ADB device. The driver only work when te device is called "qhsusb_bulk", this mode of the device is the "Emergency download mode" and it only show up when you broke the bootloader, if you want to see if brickind and restoring the bootloader will recover the imei just use my script that i added at the bottom of the OP. BTW, try first flashing Motoboot, fsg.mbn, NON-HLOS.bin to see if works...

Really don't know but maybe works, if your phone works great try flashing all MBN partitions(or using the script that i post to the OP), this should break the bootloader and you can recover with this tool

Reflash GPT, Motoboot via fastboot, if this don't work and you want to reflash the bootloader try reflashing all MBN partitions, i will make a script that breaks the bootloader so that allow to recover it, you can download the script at the bottom of the OP
[Moto G Original Android Development] surfino:
Thanks boss for your effort. Tried script to break and your method to recover. Worked flawless. Problem is that imei still shown In fastboot and 0 on Android. Can't seem to solve that imei problem
[Moto G Original Android Development] Boss442:
try flashing this:

if this doesn't work, talk me on google+ or facebook, i will share with you my pds.img, but you will need to see if the IMEI isn't the mine
[Moto G Original Android Development] surfino:
thanks mate, only one thing

persist.img come from 4.3 only, i am running 4.4.2 now, should i downgrade or i can try even if i am on 4.4.2?

nevermind, obviously i have to downgrade. will update later, thanks
[Moto G Original Android Development] bckspc:
Hi all... I have Moto G XT1032 retail.gb.

After several mistakes I've been unable to activate WIFI. On the settings the wifi MAC is "Unavailable".

I've managed to flash stock rom 4.3 then manually OTA to 174.44.9 and then using 3G update to 176.44.1.

Now the phone is working EXCEPT the WIFI. I guess that something is wrong with the WIFI modules or something like that. Will the method explained above work for me? I'm afraid of breaking it and doing worse.

Thankx
[Moto G Original Android Development] Boss442:
No, this metod won't work, search in the forums i think i seen a topic with a solution
[Moto G Original Android Development] bckspc:
Thank you... I finally made it work. See post http://xdaforums.com/showthread.php?t=2582635&highlight=wifi&page=81 for more details.

Thanks
[Moto G Original Android Development] Jerome-X:
can you please share me also your pds.img? Having the same problem as member "surfino"

Could you help me out of this issu IMIEI=0

Thanks, JX!
[Moto G Original Android Development] Boss442:
Reflashing pds.img don't solve the problem... Sorry

Enviado desde mi XT1032 mediante Tapatalk
[Moto G Original Android Development] Boss442:
You want a over-prized rock?

If moto G2 had a blank flasher and you use it on moto G1, you will break worst.

Wait until a 5.0 firmware comes out, and i will update the MotoFlasher App.

If any mod is here, please, close this thread....
[Moto G Original Android Development] :
okay and we gotta wait 2 months for it. thatz a big pain rite?
[Moto G Original Android Development] Boss442:
Maybe more, maybe less.
[Moto G Original Android Development] :
True [MENTION=4749802]Boss442[/MENTION] is right.

You made the mistake so it's also your own mistake.

So, you have to wait, I'll try to make a singleimage but don't expect much.

Indeed please close this thread!
[Moto G Original Android Development] Boss442:
I don't think that there is possible to make singleimage, remember that if you make it, you need to make the programmer too....

I know about Microcontrollers and i know what they do:

Programmer is a mini code that load in the device's ram, this code allows to accept the singleimage content directly on the BL.

Singleimage is a File that content a minimal version of out bootloader, that allows to flash Motoboot to have full bootloader again...

GPT is the General Partition Table, that knows where the partitions reside in memory, so we need to flash after motoboot to know where the phone will flash motoboot.