Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

Recover a 4.4.4 downgrade brick! (Temporal solution)

OP tatazeuz

2nd July 2014, 02:14 AM   |  #1  
tatazeuz's Avatar
OP Senior Member
Flag Santiago
Thanks Meter: 84
 
299 posts
Join Date:Joined: Dec 2012
More
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.custh...ail/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/xt1...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
Last edited by tatazeuz; 2nd July 2014 at 02:38 AM.
The Following 10 Users Say Thank You to tatazeuz For This Useful Post: [ View ]
2nd July 2014, 01:21 PM   |  #2  
Senior Member
Thanks Meter: 118
 
390 posts
Join Date:Joined: Jan 2013
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
2nd July 2014, 01:40 PM   |  #3  
tatazeuz's Avatar
OP Senior Member
Flag Santiago
Thanks Meter: 84
 
299 posts
Join Date:Joined: Dec 2012
More
Quote:
Originally Posted by maurocds

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

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".
2nd July 2014, 02:21 PM   |  #4  
Member
Thanks Meter: 23
 
60 posts
Join Date:Joined: Dec 2007
Or you can restore 4.4.2 nandroid backup using recovery if you made one. But after that you need to flash correct baseband.
2nd July 2014, 04:11 PM   |  #5  
tatazeuz's Avatar
OP Senior Member
Flag Santiago
Thanks Meter: 84
 
299 posts
Join Date:Joined: Dec 2012
More
Quote:
Originally Posted by masa86

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

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.
2nd July 2014, 05:33 PM   |  #6  
Junior Member
Thanks Meter: 2
 
18 posts
Join Date:Joined: Feb 2014
It Doesn't work only say failed xD
Last edited by Fresroqir; 2nd July 2014 at 05:55 PM.
2nd July 2014, 06:04 PM   |  #7  
tatazeuz's Avatar
OP Senior Member
Flag Santiago
Thanks Meter: 84
 
299 posts
Join Date:Joined: Dec 2012
More
Quote:
Originally Posted by Fresroqir

It Doesn't work only say failed xD

Care to explain what failed?
2nd July 2014, 06:09 PM   |  #8  
Junior Member
Thanks Meter: 2
 
18 posts
Join Date:Joined: Feb 2014
Quote:
Originally Posted by tatazeuz

Care to explain what failed?




The install for the custom rom and gapps
2nd July 2014, 06:17 PM   |  #9  
tatazeuz's Avatar
OP Senior Member
Flag Santiago
Thanks Meter: 84
 
299 posts
Join Date:Joined: Dec 2012
More
Quote:
Originally Posted by Fresroqir

The install for the custom rom and gapps

What error did you receive? Did you flashed gpt.bin correctly?
2nd July 2014, 06:31 PM   |  #10  
Junior Member
Thanks Meter: 2
 
18 posts
Join Date:Joined: Feb 2014
Quote:
Originally Posted by tatazeuz

What error did you receive? Did you flashed gpt.bin correctly?



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)
Last edited by Fresroqir; 2nd July 2014 at 06:39 PM.

Post Reply Subscribe to Thread

Tags
4.4.4, brick, downgrade, soft, softbrick
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes