Database Info

Recover a 4.4.4 downgrade brick! (Temporal solution)

So, i have noted a increased number of threads about people who have soft-bricked their phones downgrading from 4.4.4 GPE after recieving the OTA, since it includes a new partition table and there's no firmware image yet.
Worry not, i have found a solution for your problem. This method only let's you use custom ROMs (sadly), but it's meant to be a temporal solution while we wait for a 4.4.4 GPE image anyways.
So, without further ado, here's my fix:
You will need:
-The good ol' Android SDK
http://developer.android.com/sdk/index.html#download
-Motorola drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
-A custom recovery. I recommend TWRP, since is the only one i have tested.
Official TWRP Images for Moto G: http://techerrata.com/file/twrp2/xt1032/openrecovery-twrp-2.7.1.1-xt1032.img
-The gpt.bin from 4.4.4 (this is the partition table)
I extracted it from the OTA file and uploaded to my Dropbox: https://dl.dropboxusercontent.com/u/82658555/gpt.bin
-A custom ROM of your choice (obligatory) + GApps (optional)
What to do:
Once you have the Android SDK, decompress the folder sdk/platform-tools in a place of your choice.
Inside this folder, put gpt.bin, the custom recovery image and the ROM and GApps zip's.
Start your phone on fastboot. Connect it.
Inside your decompressed platform-tools folder, hold shift and right click inside the folder. Select "Open command window here".
Make sure your phone is properly connected by typing "fastboot devices" (without the quotation marks). The command prompt should show your phone serial number.
Now we start the real deal. Fist of all, flash gpt.bin using this command:
fastboot flash partition gpt.bin
Make sure it ends on "OKAY"
Now, flash the recovery
fastboot flash recovery nameoftherecoveryfile.img
Once this is done, enter recovery using the fastboot menu on your phone (use Vol- to highlight "Recovery", and then press Vol+)
Now your phone should boot on recovery mode. If you recieve an error like "Can't mount /system/", don't worry, this is normal (there's no system partiton yet, after all). Now you can use ADB command with your PC. Once again, to be sure everything is connected properly,tyipe on the console:
adb devices
Once that is done, it's time to give your phone the custom ROM, so you can flash it. Type (or copy/paste)
adb push NameoftheROMfile.zip /sdcard/ NameoftheROMfile.zip
If you have GApps, do the same for those
adb push GApps.zip /sdcard/ GApps.zip
Now you can finally disconnect your phone from the PC! You are almost done, select "Install" in your recovery, and flash your ROM zip, then the GApps if you have them.
Once it's done, you can reboot to system.
And you will have a working Moto G again!!
Enjoy it, and don't brick it again

the guide isw missing some info (like enter flash sideload on recovery)
and that weird command push does not work, i have to use other command
i managed to install another rom after being bricked but still that rom won´t start, i have to try another
still thanks a lot
i did not download android sdk, i have my folder with adb files
also when i am in recovery, i type fastboot devices and nothing happens, but still the recovery could receive the file

maurocds said:
the guide isw missing some info (like enter flash sideload on recovery)
and that weird command push does not work, i have to use other command
i managed to install another rom after being bricked but still that rom won´t start, i have to try another
still thanks a lot
i did not download android sdk, i have my folder with adb files
also when i am in recovery, i type fastboot devices and nothing happens, but still the recovery could receive the file
Click to expand...
Click to collapse
From my experience, you don't have to enter sideload mode in recovery to push a file, sideload mode is for pushing OTAs. And remember, the ADB push command requires you to put the exact name of the file to transfer twice, that could have failed for you.
You can't use fastboot devices on recovery because you can only use ADB commands in recovery, you were supposed to use "adb devices".

Or you can restore 4.4.2 nandroid backup using recovery if you made one. But after that you need to flash correct baseband.

masa86 said:
Or you can restore 4.4.2 nandroid backup using recovery if you made one. But after that you need to flash correct baseband.
Click to expand...
Click to collapse
Not many people do NAND backups these days.
Sad, because they're really useful, and there wouldn't be as many "HALP BRICKED PHONE" threads.

It Doesn't work only say failed xD

Fresroqir said:
It Doesn't work only say failed xD
Click to expand...
Click to collapse
Care to explain what failed?

tatazeuz said:
Care to explain what failed?
Click to expand...
Click to collapse
The install for the custom rom and gapps

Fresroqir said:
The install for the custom rom and gapps
Click to expand...
Click to collapse
What error did you receive? Did you flashed gpt.bin correctly?

tatazeuz said:
What error did you receive? Did you flashed gpt.bin correctly?
Click to expand...
Click to collapse
i just received failed at twrp recovery and how do i flashed gpt.bin right because it say okay.
And what does gpt.bin actually? (i am a noob)

Fresroqir said:
i just received failed at twrp recovery and how do i flashed gpt.bin right because it say okay.
And what does gpt.bin actually? (i am a noob)
Click to expand...
Click to collapse
got.bin is the partition table of the Moto G. Its the file that indicates to the phone the size, name and number of partitions it should have.
So, I know TWRP said in red letters Failed, but I'm interested what is the specific error, what did it said on the command prompt of TWRP.

Error flashing zip sdcard pa falconzip
and then there comes this updating partitution details and do i need to put the rom twice in the cmd?

and do i need a cutom rom with 4.4.4????????

yes, exactly what rom did you use to recover??????????
paranoid did not work, installed fine but stuck at logo loading

Fresroqir said:
and do i need a cutom rom with 4.4.4????????
Click to expand...
Click to collapse
maurocds said:
yes, exactly what rom did you use to recover??????????
paranoid did not work, installed fine but stuck at logo loading
Click to expand...
Click to collapse
I used the latest version of PA + Stock GApps

Thanks!
Edit: Nope... Still same problem. Looks like the gpt file flashed but everything else is the same.

It still doesn't work for me i got th whole time failed and i don't know what i need to do ;(
It says: Z:\New folder\Android>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.025s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.372s]
finished. total time: 0.399s
is that good?
EDIT:it looks that sideload works and not that push command
EDIT: nvm i am stuck at bootanimation
EDIT: this wont work it says failed all the time at twrp

I'm kind of confused. Why couldn't people downgrade and go back to stock by reflashing all of the files from an older stock image, including the motoboot and gpt? I would think this would work...although with people saying that they are unable to downgrade I'm not willing to try upgrading to 4.4.4 myself.
What errors are people seeing if they try to flash gpt and motoboot from, say, 4.4.2 stock or 4.4.2 GPE?
-- Nathan

not work for me..
every recovery stay on black screen and return vibration on touch screen
:/
help > http://forum.xda-developers.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228

i think this fix doesn't work because i can only sideload my roms and gapps xD

Moto G 4.4.4 Bricked! ADB Not working, Please HELP

My MOTO G (XT1032) IS BRICKED
I was running Android 4.4.4 official stock rom. I decided to remove everything and flash android 4.4.2 stock rom.
So I was failing to flash motoboot.img. I tried everything but it dindt work. I then deleted everything, system cache etc through recovery and still the same error: Failed to flash motoboot.img
And when I try other UNBRICK tutorials you need adb working (to place an custom rom via adb to /sdcard. The problem is ADB is not working when I type in adb devices I get: List of devices attached. but I can't see my phone's ID. Its is just empty.
So fastboot is working (when I type in fastboot devices I get the phones ID), But ADB is not working.
How to solve this huge problem??
Thanks in advance.

Jason61 said:
Thanks in advance.
Click to expand...
Click to collapse
Are you using adb while you are in recovery? It won't work in fastboot mode.

No I'm using fastboot, but problem already solved. The problem was with the files gpt.bin and motoboot.img. All the other files from stock rom are flashing correctly.
So I downloaded 4.4.4 Stock Rom (Verizon US version) and copied gpt.bin and motoboot.img from there and pasted in the 4.4.2 Stock Rom folder. Then I flashed all files and it worked !

Maxx stuck boot looping

Hey Guys,
I rooted my device a while ago and everyday had to dismiss the OTA update for the last few months. The other night I accidentally accepted the OTA and know my phone is stuck in a bootloop when connected to power. I'm occasionally able to get into Fastboot mode for RSD to see the phone, ADB will not see the phone. When I attempt to select Recovery or Factory the phone bootloops. I have also tried House of Moto and that didn't work.I have tried flashing all the files located at sbf with no luck. In Fastboot the Device is listed as UNLOCKED with a Status Code: 1.
Any help will be greatly appreciated.
When I flash using House of Moto I get an error for the following:
gpt.bin
motoboot.img
logo.bin
boot.img
recovery.img
system.img
NON-HLOS.bin

uniqueflips said:
Hey Guys,
I rooted my device a while ago and everyday had to dismiss the OTA update for the last few months. The other night I accidentally accepted the OTA and know my phone is stuck in a bootloop when connected to power. I'm occasionally able to get into Fastboot mode for RSD to see the phone, ADB will not see the phone. When I attempt to select Recovery or Factory the phone bootloops. I have also tried House of Moto and that didn't work.I have tried flashing all the files located at sbf with no luck. In Fastboot the Device is listed as UNLOCKED with a Status Code: 1.
Any help will be greatly appreciated.
When I flash using House of Moto I get an error for the following:
gpt.bin
motoboot.img
logo.bin
boot.img
recovery.img
system.img
NON-HLOS.bin
Click to expand...
Click to collapse
Does it ever actually boot up and then just restarts? Or are you never getting to the homescreen?

no home screen
Hi,
It won't even boot loop unless it's connected to power. When it is it just boot loops, tried everything but can't get past the boot loop. Spent countless hours trying to make any progress.

try flashing TWRP from fastboot
Code:
fastboot erase recovery
fastboot flash recovery name.img
if you get into recovery try restoring a nandroid
if that doesnt work, make sure you are flashing the appropriate SBF from the update you were in teh process of taking. My bet is somehow your device got partially updated (bootloader) so you are now unable to flash the SBF you were prevously on. ie. you were on 4.2.2, and took the 4.4 update, you need to flash the SBF for 4.4, not 4.2.2

Once you get back up and running, make sure you disable the Moto OTA app using titanium or the like. That should prevent the phone from trying to take an update again.

Still no luck
Thanks everyone for the suggestions, I'm not sure which firmware it was trying to install so I installed all the firmwares available via House of Moto and still no luck. Tried performing a Full and Keep Data and still the phone will continue to boot loop. One thing I did notice during the install using House of Moto I see the following error multiple times:
(bootloader) Variable not supported!
I got this error on all 5 firmwares.
Any ideas...

uniqueflips said:
Thanks everyone for the suggestions, I'm not sure which firmware it was trying to install so I installed all the firmwares available via House of Moto and still no luck. Tried performing a Full and Keep Data and still the phone will continue to boot loop. One thing I did notice during the install using House of Moto I see the following error multiple times:
(bootloader) Variable not supported!
I got this error on all 5 firmwares.
Any ideas...
Click to expand...
Click to collapse
what version of android were you on prior to this happening. What version was the OTA attempting to update you to?

I think I was on Android 4.4 Blur_Version.19.5.3.obake_verizon.Verizon.en.US, not 100% sure what it was trying to install 4.4.4 or 4.4 19.6.3.
Tried House of Moto again and on the 4.2.2 12.15.15 and 4.4.4 I don't get the (bootloader) Variable not supported! error. The phone still boot loops.

uniqueflips said:
I think I was on Android 4.4 Blur_Version.19.5.3.obake_verizon.Verizon.en.US, not 100% sure what it was trying to install 4.4.4 or 4.4 19.6.3.
Tried House of Moto again and on the 4.2.2 12.15.15 and 4.4.4 I don't get the (bootloader) Variable not supported! error. The phone still boot loops.
Click to expand...
Click to collapse
have you tried with the latest version of RSD lite?
If so make sure you edit the XML file to remove the part about erasing userdata
lets try this too... go to sbf.droid-developers.org and download this file for the maxx "Android 4.4.4
Blur_Version.21.11.21.obake_verizon.Verizon.en.US"
Install the latest moto device manager and RSD lite, then try flashing (might erase userdata)
If that does not work, you can manually flash each file in fastboot, lmk if any of that works
last Q, do you have a motorola factory cable?

Tried with and without removing the getvar file and no luck, still stuck in an endless boot loop when connected to power. ADB still doesn't see the device even in Fastboot mode. Never flashed each file in fastboot individual doesn't that require ADB?

uniqueflips said:
Tried with and without removing the getvar file and no luck, still stuck in an endless boot loop when connected to power. ADB still doesn't see the device even in Fastboot mode. Never flashed each file in fastboot individual doesn't that require ADB?
Click to expand...
Click to collapse
no you dont use adb from fastboot, you use "fastboot"
Lets see if we can get you booted to a recovery. Download this file, save it as recovery.img in your ADB directory.
boot to fastboot and run this command to determine fastboot sees the device
Code:
fastboot devices
If you see your device, then run the next command
Code:
fastboot flash recovery recovery.img
then try to boot to recovery. post result (make sure when you highlight "recovery" in fastboot you use volume up to select it. I just made the mistake of using power and my phone wouldnt boot to recovery)

[Q] Trouble with XT1033 Indian version

So I have XT1033 Indian Version , with 4.4.4 already installed but since I rooted my device and deleted some system apps and tweaked around a bit , it won't update automatically via OTA to 5.0.2 .
Now I am trying to flash 4.4.4 Stock again by following this and after trying everything I could same error pops up again and again .. waiting for device in mfastboot
though at the same time it is connected in fastboot and adb.
Please Help

rhtyhmed said:
So I have XT1033 Indian Version , with 4.4.4 already installed but since I rooted my device and deleted some system apps and tweaked around a bit , it won't update automatically via OTA to 5.0.2 .
Now I am trying to flash 4.4.4 Stock again by following this and after trying everything I could same error pops up again and again .. waiting for device in mfastboot
though at the same time it is connected in fastboot and adb.
Please Help
Click to expand...
Click to collapse
You need to be in boot loader mode when using fastboot.

skyguy126 said:
You need to be in boot loader mode when using fastboot.
Click to expand...
Click to collapse
Yes, I know that.
My phone connects with fastboot but not mfastboot which is needed to flash the stock firmware

try
mfastboot devices
If your device connected ,then cmd will show some device id.Then try flashing.
Did you placed mfastboot.exe in adb folder????xd

rhtyhmed said:
Yes, I know that.
My phone connects with fastboot but not mfastboot which is needed to flash the stock firmware
Click to expand...
Click to collapse
I used fastboot when flashing on my device. They are virtually the same thing.

Unable to flash stock rom on moto g turbo (XT1557).

I'm unable to flash stock rom on my moto g turbo xt1557, with the fastboot method,
the actual problem is when i try to flash gpt.bin in the command getting the error
preflash validation failed remote failure.
since i've flashed this rom earlier it was succesfull at that time then i have installed twrp to try lineage os.
as now i want to revert back to stock , im unable due to the following error.
i'm trying the latest version of the stock rom which is availables\ still getting the error.
Please help.:crying :crying::crying:
Thanks :good::good::good:

vishal4950 said:
I'm unable to flash stock rom on my moto g turbo xt1557, with the fastboot method,
the actual problem is when i try to flash gpt.bin in the command getting the error
preflash validation failed remote failure.
since i've flashed this rom earlier it was succesfull at that time then i have installed twrp to try lineage os.
as now i want to revert back to stock , im unable due to the following error.
i'm trying the latest version of the stock rom which is availables\ still getting the error.
Please help.:crying :crying::crying:
Thanks :good::good::good:
Click to expand...
Click to collapse
Just skip that and do all commands,

Ojas25.8 said:
Just skip that and do all commands,
Click to expand...
Click to collapse
Dude. You mean to skip the flashing of gpt.bin
I have tried that too. Skipping the gpt.bin makes firmware flashing successful.
But after that problem is that phone get stuck on boot logo. Waited untill 30mins still no response.

vishal4950 said:
Dude. You mean to skip the flashing of gpt.bin
I have tried that too. Skipping the gpt.bin makes firmware flashing successful.
But after that problem is that phone get stuck on boot logo. Waited untill 30mins still no response.
Click to expand...
Click to collapse
Did you factory reset in stock recovery first? It's essential...