Database Develop

Downgrade from 4.4.2 to 4.4

So I used the 4.4 root tutorial without any problems and then flashed the 4.4.2 update via sdcard.
The deal is that my supersu seems to be damaged, thought I still have root, the xposed framework can´t seem to receive supersu permission.
So I want to downgrade to the 4.4.
How should I do this?

alemonte said:
So I used the 4.4 root tutorial without any problems and then flashed the 4.4.2 update via sdcard.
The deal is that my supersu seems to be damaged, thought I still have root, the xposed framework can´t seem to receive supersu permission.
So I want to downgrade to the 4.4.
How should I do this?
Click to expand...
Click to collapse
Term "Downgrade" refers to "lowering" you version, in this case from 4.4 to 4.2.2. Now you just need to go back to 4.4
I am not sure whether your bootloader unlocked or not and what you version is, but I think this one will help http://forum.xda-developers.com/showthread.php?t=2603358 or this one http://forum.xda-developers.com/showthread.php?t=2538896

okaban said:
Term "Downgrade" refers to "lowering" you version, in this case from 4.4 to 4.2.2. Now you just need to go back to 4.4
I am not sure whether your bootloader unlocked or not and what you version is, but I think this one will help http://forum.xda-developers.com/showthread.php?t=2603358 or this one http://forum.xda-developers.com/showthread.php?t=2538896
Click to expand...
Click to collapse
Ok, so I have a locked bootloader. My guess is that I have the last version since I made the update to 4.4.2.
By having a locked bootloader I think I can´t downgrade to 4.2.2, right?
So I wanted to go back to 4.4 by following the commands below:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
But right on the first fastboot, I get this error:
downgraded security version
Update gpt_main version failed
preflash validation for GPT

alemonte said:
Ok, so I have a locked bootloader. My guess is that I have the last version since I made the update to 4.4.2.
By having a locked bootloader I think I can´t downgrade to 4.2.2, right?
So I wanted to go back to 4.4 by following the commands below:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
But right on the first fastboot, I get this error:
downgraded security version
Update gpt_main version failed
preflash validation for GPT
Click to expand...
Click to collapse
you can't go back to the complete 4.4 package and honestly im not even going to tell you how to get 4.4 running because i wont be responsible for you hardbricking your phone.
4.4.2 has a new bootloader and 4.4 has a diffrent bootloader you cant downgrade the 4.4.2 bootloader at all. it is a one way street sorry

dray_jr said:
you can't go back to the complete 4.4 package and honestly im not even going to tell you how to get 4.4 running because i wont be responsible for you hardbricking your phone.
4.4.2 has a new bootloader and 4.4 has a diffrent bootloader you cant downgrade the 4.4.2 bootloader at all. it is a one way street sorry
Click to expand...
Click to collapse
OK! I know I messed up updating to 4.4.2 rooted. Should've stayed on 4.4 but my X was having issues after disconnecting from Wifi to connect to LTE. Anyways..I´ll be returning the phone and getting a new one today! Tnks a lot for the help!

alemonte said:
Ok, so I have a locked bootloader. My guess is that I have the last version since I made the update to 4.4.2.
By having a locked bootloader I think I can´t downgrade to 4.2.2, right?
So I wanted to go back to 4.4 by following the commands below:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
But right on the first fastboot, I get this error:
downgraded security version
Update gpt_main version failed
preflash validation for GPT
Click to expand...
Click to collapse
Most likely you tried to downgrade to the very first 4.2.2 (.31 in case of XT1058). It's not possible. You need the one after, with camera update (.54 for XT1058, for example, http://sbf.droid-developers.org/phone.php?device=0)

okaban said:
Most likely you tried to downgrade to the very first 4.2.2 (.31 in case of XT1058). It's not possible. You need the one after, with camera update (.54 for XT1058, for example, http://sbf.droid-developers.org/phone.php?device=0)
Click to expand...
Click to collapse
please dont downgrade to 4.2.2 camera update downgrade to 4.4 you just have to not flash the gpt file but flash everything else.
if you flash 4.2.2 Camera update and then take the OTA for 4.4 you will brick your phone.

dray_jr said:
please dont downgrade to 4.2.2 camera update downgrade to 4.4 you just have to not flash the gpt file but flash everything else.
if you flash 4.2.2 Camera update and then take the OTA for 4.4 you will brick your phone.
Click to expand...
Click to collapse
So, is it possible to go from 4.4.2 to 4.4 without bricking or not? Just asking for clarification because of
4.4.2 has a new bootloader and 4.4 has a diffrent bootloader you cant downgrade the 4.4.2 bootloader at all. it is a one way street sorry
Click to expand...
Click to collapse

okaban said:
Term "Downgrade" refers to "lowering" you version, in this case from 4.4 to 4.2.2. Now you just need to go back to 4.4
I am not sure whether your bootloader unlocked or not and what you version is, but I think this one will help http://forum.xda-developers.com/showthread.php?t=2603358 or this one http://forum.xda-developers.com/showthread.php?t=2538896
Click to expand...
Click to collapse
Please do not advise any users to downgrade!
It is well documented that if you downgrade to ANY version, once on 4.4.2, you will brick your phone! It is literally all over the Moto X forums.
Wouldn't you feel awful if the OP followed your advice and bricked their phone???
---------- Post added at 09:03 PM ---------- Previous post was at 09:00 PM ----------
EchoHelix said:
So, is it possible to go from 4.4.2 to 4.4 without bricking or not? Just asking for clarification because of
Click to expand...
Click to collapse
NO! I have no idea why anyone would advise you to do that.....
Whatever exploit you had used to root on 4.4 does not work on 4.4.2
The only way to root (and achieve write-protect-disable), now that you are on 4.4.2 is to unlock the bootloader. Even with unlocked bootloader, you still can't downgrade without bricking.

I'll just add my two cents as well....as perfectly said already above....I'll just add....
NO. Do not ever try to downgrade to any version if you are on 4.4.2 or higher already. Unless you don't care at all if you brick and have the cash for a new phone or an old phone you'd be happy using again.
No. Some will debate this, and they should keep it to themselves.....unless they are offering to replace your phone if their advice bricks you. ?
---------- Post added at 03:21 PM ---------- Previous post was at 03:17 PM ----------
@okaban , please do not advice people to downgrade, or lead them to believe its safe.
If you want to try it, go ahead....but keep it to yourself. Too many aren't confident with this stuff and will end up with a paperweight because you led them to believe they could do it.
So please, do not suggest downgrading. Its irresponsible and hazardous advice.
Thanks! ?

samwathegreat said:
Please do not advise any users to downgrade!
It is well documented that if you downgrade to ANY version, once on 4.4.2, you will brick your phone! It is literally all over the Moto X forums.
[cut]
The only way to root (and achieve write-protect-disable), now that you are on 4.4.2 is to unlock the bootloader. Even with unlocked bootloader, you still can't downgrade without bricking.
Click to expand...
Click to collapse
KJ said:
I'll just add my two cents as well....as perfectly said already above....I'll just add....
NO. Do not ever try to downgrade to any version if you are on 4.4.2 or higher already. Unless you don't care at all if you brick and have the cash for a new phone or an old phone you'd be happy using again.
No. Some will debate this, and they should keep it to themselves.....unless they are offering to replace your phone if their advice bricks you. ?
Click to expand...
Click to collapse
Sorry, quoted because I wanted to try and emphasize this advice... and add...
The GPT.BIN in 4.4.3 has been updated as well.. so Once you have either 4.4.2 or 4.4.3 on your phone, DO NOT ATTEMPT TO DOWNGRADE!!!
If you try and downgrade only "parts" things wont work properly... example: Those who had 4.4.2 and downgraded only system.img and boot.img found issues going settings -> security... (it kicked them out). And other flakey things happened. When they attempted to update, things got worse.
4.4.4 will likely see updates to motoboot.img(bootloader) and GPT.BIN(partition table)... So the same warnings will apply.
It does NOT matter if your bootloader is unlocked or not. These same warnings and caveats apply!!

KidJoe said:
Sorry, quoted because I wanted to try and emphasize this advice... and add...
The GPT.BIN in 4.4.3 has been updated as well.. so Once you have either 4.4.2 or 4.4.3 on your phone, DO NOT ATTEMPT TO DOWNGRADE!!!
If you try and downgrade only "parts" things wont work properly... example: Those who had 4.4.2 and downgraded only system.img and boot.img found issues going settings -> security... (it kicked them out). And other flakey things happened. When they attempted to update, things got worse.
4.4.4 will likely see updates to motoboot.img(bootloader) and GPT.BIN(partition table)... So the same warnings will apply.
It does NOT matter if your bootloader is unlocked or not. These same warnings and caveats apply!!
Click to expand...
Click to collapse
Good point at the end. After 4.4.2....some thought their unlocked phone was immune to these warnings.....or their dev edition....which every one should know now is no different than any other unlocked phone. Aside from intact warranty.
Great addition KidJoe! Doesn't matter the phone, locked, unlocked or dev edition......none can safely downgrade.
The moto x is nothing like a Nexus in this regard.

[Q] Sprint 4.4.4 recovery

I'm returning my phone to stock and wish to flash the stock 4.4.4 recovery back over TWRP. As 4.4.4 firmware has not been officially posted anywhere, is there any way someone can provide a means of flashing it back? And if that isn't possible, is it safe to flash 4.4.2 stock recovery only?
Thanks for the help.

DJMaj07 said:
I'm returning my phone to stock and wish to flash the stock 4.4.4 recovery back over TWRP. As 4.4.4 firmware has not been officially posted anywhere, is there any way someone can provide a means of flashing it back? And if that isn't possible, is it safe to flash 4.4.2 stock recovery only?
Thanks for the help.
Click to expand...
Click to collapse
This makes no sense.
To get back to where you were you can,
1) restore your last twrp backup. That is what twrp is for. If you never made one, Someone could post one, system & boot only.
Recovery has nothing to do with it. The full fxz/XML 444 is what you need.
If you Rsd the 442 XML in order to "reOTA" you risk a brick.

aviwdoowks said:
This makes no sense.
To get back to where you were you can,
1) restore your last twrp backup. That is what twrp is for. If you never made one, Someone could post one, system & boot only.
Recovery has nothing to do with it. The full fxz/XML 444 is what you need.
If you Rsd the 442 XML in order to "reOTA" you risk a brick.
Click to expand...
Click to collapse
Let me explain. I unlocked my bootloader and flashed TWRP. I am currently running stock unrooted 4.4.4 with TWRP. I want to return to the stock recovery, and then relock the bootloader. Obviously a TWRP backup won't help here.

Philz has a built in custom ROM creation feature to do this very thing. You can flash Philz from twrp then reboot recovery. Be sure to wipe cache & dalvik but not data. Then flash the custom ROM that some kind reader may post. Or twrp restore the system & boot, same thing.

DJMaj07 said:
Let me explain. I unlocked my bootloader and flashed TWRP. I am currently running stock unrooted 4.4.4 with TWRP. I want to return to the stock recovery, and then relock the bootloader. Obviously a TWRP backup won't help here.
Click to expand...
Click to collapse
Why would you re-lock the bootloader? Ever?
You realize that you can NEVER get rid of the "Warning: Unlocked Bootloader" message, right? Re-locked BLs **STILL** display that message. There is no way to EVER get back to "Locked" status. No way to ever get rid of the Unlocked boot message (other than flashing a new logo.bin, but you can only do that if UNlocked).
We just don't understand why you would want to do that...? If you are selling it, why not just sell it as unlocked? Your buyer will still see the "warning" message regardless....

DJMaj07 said:
Let me explain. I unlocked my bootloader and flashed TWRP. I am currently running stock unrooted 4.4.4 with TWRP. I want to return to the stock recovery, and then relock the bootloader. Obviously a TWRP backup won't help here.
Click to expand...
Click to collapse
Sorry
The 442 stock recovery should work, pull it from the XML. Use Rashr tools to flash. Then superSU to hide root/unroot
Then you have as close to a locked phone as possible. The bootloader screen will still show your unlock status though.

samwathegreat said:
Why would you re-lock the bootloader? Ever?
You realize that you can NEVER get rid of the "Warning: Unlocked Bootloader" message, right? Re-locked BLs **STILL** display that message. There is no way to EVER get back to "Locked" status. No way to ever get rid of the Unlocked boot message (other than flashing a new logo.bin, but you can only do that if UNlocked).
We just don't understand why you would want to do that...? If you are selling it, why not just sell it as unlocked? Your buyer will still see the "warning" message regardless....
Click to expand...
Click to collapse
The relocking of the bootloader isn't really the priority, I mainly just want to get the stock recovery back to prevent issues with accepting OTAs in the future. This was never about making that message go away. That's why I focused on the "getting back to stock recovery" part in the OP

aviwdoowks said:
Sorry
The 442 stock recovery should work, pull it from the XML. Use Rashr tools to flash. Then superSU to hide root/unroot
Then you have as close to a locked phone as possible. The bootloader screen will still show your unlock status though.
Click to expand...
Click to collapse
That would be great if 4.4.2 recovery was safe. Could I just use fastboot to flash the recovery and relock the bootloader?

DJMaj07 said:
The relocking of the bootloader isn't really the priority, I mainly just want to get the stock recovery back to prevent issues with accepting OTAs in the future. This was never about making that message go away. That's why I focused on the "getting back to stock recovery" part in the OP
Click to expand...
Click to collapse
I see,
To make sure your system is ota ready you will need to pull the STK recovery from the 444 XML when it comes but the 442 one may have the same md5 anyway
---------- Post added at 08:05 PM ---------- Previous post was at 07:58 PM ----------
DJMaj07 said:
That would be great if 4.4.2 recovery was safe. Could I just use fastboot to flash the recovery and relock the bootloader?
Click to expand...
Click to collapse
When you do get ready to flash the 442 recovery post the md5 & also ask others to post there md5 for their 444 recovery. Maybe someone saved their recovery from 444.

DJMaj07 said:
The relocking of the bootloader isn't really the priority, I mainly just want to get the stock recovery back to prevent issues with accepting OTAs in the future. This was never about making that message go away. That's why I focused on the "getting back to stock recovery" part in the OP
Click to expand...
Click to collapse
Bootloader status has no effect on OTAs whatsoever. Why relock the bootloader at all?

So does anyone know where to find this stock recovery?

moto x not-so-dev edition, what is RSDlite trick?

I simply want to allow my phone to accept any gpt.bin.
i honestly do not care about what it thinks about "downgraded security version".
Is there anyway to do that with a plain fastboot client/interface?
what does RSD does for work around that?
thank you!

sigh... it does not F*** allow it, but DO screw up something.
now regular boot just gives me a black screen. while 'factory' and 'bp tools' boot just fine to my fully working system rom (stock 4.4.3)

What exactly have you had in your device, flashed, etc...And what you are trying to accomplish.
Need some more details.
And the reason security is set up like that is cause downgrading the Moto X can easily brick your device. Many members have bricked trying to downgrade, or after managing to downgrade...have bricked later.
Without the errors, this section would be overflowing with brick threads. ?

KJ said:
What exactly have you had in your device, flashed, etc...And what you are trying to accomplish.
Need some more details.
And the reason security is set up like that is cause downgrading the Moto X can easily brick your device. Many members have bricked trying to downgrade, or after managing to downgrade...have bricked later.
Without the errors, this section would be overflowing with brick threads. ?
Click to expand...
Click to collapse
fair point. Though i'm still amazed how phone manufacturers manage to get a device bricked by installing software... oh well.
so, my phone history is:
bought moto x dev.
received 4.4.3 OTA update over the 4.4.2 that shipped with it.
flashed twrp because i like image backups and to be able to do minimally required things like ssh tunels and firewall.
and that is pretty much it. i think at some point i used gravitybox when i had 4.4.2 to see what it was about and then reflashed the factory image on top.
So now i wanted to do 2 things.
1. flash the 4.4.4 OTA to see what it is like.
2. if 4.4.4 stock was not decent, i will probably flash a 4.4.2 or whatever the latest CM is for that phone.
edit: ok, forgot to be specific. i'm at step 1 of option 1 still. which is flash 4.4.2 (latest version on the lame motorola stock image repo) and then acept the 4.4.4 OTA. but the stock 4.4.2 gpt.bin triggers that warning.

You can't flash back to 4.4.2. That could/will brick you. And definitely would brick you if you did manage to flash 4.4.2 and then took an ota.
Again, the most talked about subject , next to bootloader unlocking, in the X section.

KJ said:
You can't flash back to 4.4.2. That could/will brick you. And definitely would brick you if you did manage to flash 4.4.2 and then took an ota.
Click to expand...
Click to collapse
You can return to a 4.4.2 nandroid after taking the 4.4.4 OTA if your bootloader is unlocked. I just did it last night.
My story:
1) Unlocked bootloader and rooted with TWRP/SuperSU on 4.4.2;
2) Made a 4.4.2 nandroid and saved it to my PC;
3) Returned to stock 4.4.2 and took the 4.4.4 OTA;
4) Made a 4.4.4 nandroid and saved it to my PC;
5) Inadvertently wiped System partition and Internal Storage;
6) Flashed 4.4.4 system.img from the SBF using mfastboot while in bootloader mode to return to 4.4.4 system;
7) Restored phone to 4.4.2 using TWRP and my 4.4.2 nandroid.
---------- Post added at 04:34 PM ---------- Previous post was at 03:43 PM ----------
gcbxda said:
sigh... it does not F*** allow it, but DO screw up something.
now regular boot just gives me a black screen. while 'factory' and 'bp tools' boot just fine to my fully working system rom (stock 4.4.3)
Click to expand...
Click to collapse
I am unclear on what you did to get to this point.

Wansanta said:
You can return to a 4.4.2 nandroid after taking the 4.4.4 OTA if your bootloader is unlocked. I just did it last night.
My story:
1) Unlocked bootloader and rooted with TWRP/SuperSU on 4.4.2;
2) Made a 4.4.2 nandroid and saved it to my PC;
3) Returned to stock 4.4.2 and took the 4.4.4 OTA;
4) Made a 4.4.4 nandroid and saved it to my PC;
5) Inadvertently wiped System partition and Internal Storage;
6) Flashed 4.4.4 system.img from the SBF using mfastboot while in bootloader mode to return to 4.4.4 system;
7) Restored phone to 4.4.2 using TWRP and my 4.4.2 nandroid.
---------- Post added at 04:34 PM ---------- Previous post was at 03:43 PM ----------
I am unclear on what you did to get to this point.
Click to expand...
Click to collapse
Ok, but one problem. If you take an ota to a new version now it WILL brick. So you are now stuck on 4.4.2. That is the problem with downgrading.
Sent from my XT1058 using Tapatalk

AGISCI said:
Ok, but one problem. If you take an ota to a new version now it WILL brick. So you are now stuck on 4.4.2. That is the problem with downgrading.
Click to expand...
Click to collapse
Not true - I can restore back to my 4.4.4 nandroid. I have done it 3 times so far trying to debug the problem with my text messages being restored. I can go back and forth b/t my 4.4.2 nandroid and my 4.4.4 nandroid with no problems.

Wansanta said:
Not true - I can restore back to my 4.4.4 nandroid. I have done it 3 times so far trying to debug the problem with my text messages being restored. I can go back and forth b/t my 4.4.2 nandroid and my 4.4.4 nandroid with no problems.
Click to expand...
Click to collapse
NOT THE SAME AS FIRMWARE!!
Firmware contains the bootloader, not so with a nandroid
---------- Post added at 04:35 PM ---------- Previous post was at 04:22 PM ----------
A nandroid can be flashed down NO PROBLEMO.

aviwdoowks said:
NOT THE SAME AS FIRMWARE!!
Firmware contains the bootloader, not so with a nandroid
Click to expand...
Click to collapse
First, he said I was stuck on 4.4.2, and that is what I was responding to. I am not stuck on 4.4.2 - I can go back and forth b/t 4.4.2 and 4.4.4 using my nandroids.
Second, for the record after I took the OTA I had to flash the 4.4.4 system.img from the 4.4.4 sbf b/c I inadvertently wiped my system partition. I tried using RSDLite but it would not recognize my device. When I was in bootloader mode, adb would not recognize my device either. But I was able to use mfastboot to flash the 4.4.4 system.img. After flashing the 4.4.4 system.img from the sbf, I was able to restore back to 4.4.2 system using my nandroid.
So you can selectively flash the sbf files to return to a previous version of android - you don't have to flash the bootloader. My bootloader is 30:B7 and you CAN run 4.4.2 system after you have upgraded to the 4.4.4 bootloader IF you are unlocked and rooted. I don't know what happens if you are not.

if when you flash an image you pretty much re-partition the whole flash memory (gpt), install the bootloader and system... what exactly 'bricks' the phone with downgrade/upgrade?

gcbxda said:
if when you flash an image you pretty much re-partition the whole flash memory (gpt), install the bootloader and system... what exactly 'bricks' the phone with downgrade/upgrade?
Click to expand...
Click to collapse
See links in my next post.

gcbxda said:
if when you flash an image you pretty much re-partition the whole flash memory (gpt), install the bootloader and system... what exactly 'bricks' the phone with downgrade/upgrade?
Click to expand...
Click to collapse
These links explain it better than I did:
http://forum.xda-developers.com/showpost.php?p=50734236&postcount=29
Q9Nap said:
gpt is the partition table that contains, among other things, the security versions for all other partitions. motoboot contains the various bootloader parts and also contains the security version for gpt that is checked on every boot.
they really only affect locked devices in that they prevent a locked device from being able to downgrade.
although they are not revertible once upgraded, they really don't affect unlocked devices because having the bootloader unlocked allows flashing whatever you want.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=49990727&postcount=33
Q9Nap said:
Gpt is the partition table. It contains security version for the other partitions and prevents downgrading on locked devices. It has a security version itself which is checked at boot. Once it is upgraded, it can't be reverted, but isn't really necessary on unlocked devices since the boot loader will allow flashing anything.
Click to expand...
Click to collapse
I believe in this link where Q9Nap says partition, he means partition table:
http://forum.xda-developers.com/showpost.php?p=50734615&postcount=31
Q9Nap said:
yes security version is usually updated with newer builds, but not always. i don't know what moto uses for criteria to determine whether to increase it or not, i don't work for moto.
attempting to flash a lower security version partition will not brick, it will fail to flash, giving the "failed preflash validation" error message.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=50721154&postcount=21
Q9Nap said:
it is almost impossible to permanently brick an unlocked device. pretty much the only way you could would be to flash an erroneous file to the bootloader partition, preventing the ability to access the bootloader menu.
Click to expand...
Click to collapse

If you want to go back to 4.4.2, just flash the 4.4.2 boot.img and system.img from the 4.4.2 fxz; it will work fine with the updated bootloader and radio.

Q9Nap said:
If you want to go back to 4.4.2, just flash the 4.4.2 boot.img and system.img from the 4.4.2 fxz; it will work fine with the updated bootloader and radio.
Click to expand...
Click to collapse
The op in this thread wants to be able to flash any gpt.bin he wants to. He is being told by others if he does that he will brick. I was quoting you b/c he asked why it would brick and I was showing him that it won't brick, it will just fail and also some of your quotes explain why it will fail. You said it better than I could so I quoted you. Sorry if it was confusing for me to quote you from other threads in this thread.
---------- Post added at 02:08 AM ---------- Previous post was at 02:07 AM ----------
gcbxda said:
sigh... it does not F*** allow it, but DO screw up something.
now regular boot just gives me a black screen. while 'factory' and 'bp tools' boot just fine to my fully working system rom (stock 4.4.3)
Click to expand...
Click to collapse
This is another one of @Q9Nap quotes:
with the system booted to a blank screen, press and hold the power button until you see the screen flicker, about 10 seconds.
as soon as it does, quickly release power button, press and hold volume down and then press and hold power.
hold both volume down and power for a few seconds, then release.
you should be in bootloader menu.
it might take a few tries, but you will get it.

Wansanta said:
The op in this thread wants to be able to flash any gpt.bin he wants to. He is being told by others if he does that he will brick. I was quoting you b/c he asked why it would brick and I was showing him that it won't brick, it will just fail and also some of your quotes explain why it will fail. You said it better than I could so I quoted you. Sorry if it was confusing for me to quote you from other threads in this thread.
Click to expand...
Click to collapse
yeah it won't brick, it will just fail to flash.
as long as you can access fastboot mode, you're not totally bricked.

Q9Nap said:
yeah it won't brick, it will just fail to flash.
as long as you can access fastboot mode, you're not totally bricked.
Click to expand...
Click to collapse
It did mess something up for him b/c now a regular boot gives him a blank screen. So I just posted your instructions on how to get from the blank screen to bootloader mode.

Wansanta said:
It did mess something up for him b/c now a regular boot gives him a blank screen. So I just posted your instructions on how to get from the blank screen to bootloader mode.
Click to expand...
Click to collapse
you have to flash boot.img and system.img from the same version.
in addition, you should wipe cache and dalvik-cache.
if there are still issues, you should wipe data also.

THanks a lot for all the info! much apreciated. I think i'm still confused by the horrible reuse of terms all around android history.
When you say boot nowadays, do you mean the fastboot firmware? i wasn't able to flash it some time ago... granted, i'm a fossil on android knowledge nowadays.
Q9Nap said:
you have to flash boot.img and system.img from the same version.
in addition, you should wipe cache and dalvik-cache.
if there are still issues, you should wipe data also.
Click to expand...
Click to collapse
THis is my problem. "from the same version".
phone is on 4.4.3.
lousy motorola only provides dev phone images to 4.4.2 (and 4.2.2). even though they distributed 4.4.3 for ages and now are roling out 4.4.4
There is nothing from the same version i can flash. specially if i want to try the OTA 4.4.4

gcbxda said:
THanks a lot for all the info! much apreciated. I think i'm still confused by the horrible reuse of terms all around android history.
When you say boot nowadays, do you mean the fastboot firmware? i wasn't able to flash it some time ago... granted, i'm a fossil on android knowledge nowadays.
THis is my problem. "from the same version".
phone is on 4.4.3.
lousy motorola only provides dev phone images to 4.4.2 (and 4.2.2). even though they distributed 4.4.3 for ages and now are roling out 4.4.4
There is nothing from the same version i can flash. specially if i want to try the OTA 4.4.4
Click to expand...
Click to collapse
I don't think you mentioned what carrier you're using.
Moto sux at updating their fxz files, that's why there is firmware team:
http://sbf.droid-developers.org/phone.php?device=0
WARNING! shameless plug forthcoming....
Also feel free to try my Google Play edition fxz:
http://forum.xda-developers.com/moto-x/development/fxz-xt1053-xt1060-google-play-edition-4-t2715488

Expert opinion needed in going back to Stock

Hi Guys,
I am in a bit of a problem. My Moto X has unlocked bootloader and rooted with custom recovery (twrp). So i can't update to 4.4.4 from OTA so i want to unroot and lock my bootloader (going back to everything stock).
I tried this method but it failed at first two steps.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot oem lock
i recommend wiping your device also but that is up to you if you dont want
to then skip the next two commands and just type the reboot command
fastboot erase userdata
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
The firmware which i am trying to install is:
"Android 4.4.2 Blur_Version.161.44.32.ghost_sprint.Sprint.en.US ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml"
My fastboot/bootloader with the error i am getting along with My phone information is attached below.
Need your help what should i do now.

Usama Ahmed said:
Hi Guys,
I am in a bit of a problem. My Moto X has unlocked bootloader and rooted with custom recovery (twrp). So i can't update to 4.4.4 from OTA so i want to unroot and lock my bootloader (going back to everything stock).
I tried this method but it failed at first two steps.
The firmware which i am trying to install is:
"Android 4.4.2 Blur_Version.161.44.32.ghost_sprint.Sprint.en.US ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml"
My fastboot/bootloader with the error i am getting along with My phone information is attached below.
Need your help what should i do now.
Click to expand...
Click to collapse
You should NOT re-lock the bootloader. Leave it unlocked. The phone will update just fine with unlocked BL. Just flash back to stock (what ever version you have on the phone now), then take the new OTA update.
Afterwards you can re-root if you want to.
Once again: You do NOT need to lock the BL - for any reason.
EDIT: Just looked at your pictures. Your phone is in BAD shape -- you should have never attempted to downgrade. This will be difficult to recover. I suggest asking for help in the "debricking" thread in the General sub-forum.
Good Luck.
It looks to me like you WERE on the 4.4.4 or above bootloader, and you flashed just the 4.4.2 system and boot.img at some point. Now, going back to full 4.4.2, you have downgraded the Bootloader and partition table. That is a no-no.

samwathegreat said:
You should NOT re-lock the bootloader. Leave it unlocked. The phone will update just fine with unlocked BL. Just flash back to stock (what ever version you have on the phone now), then take the new OTA update.
Afterwards you can re-root if you want to.
Once again: You do NOT need to lock the BL - for any reason.
EDIT: Just looked at your pictures. Your phone is in BAD shape -- you should have never attempted to downgrade. This will be difficult to recover. I suggest asking for help in the "debricking" thread in the General sub-forum.
Good Luck.
It looks to me like you WERE on the 4.4.4 or above bootloader, and you flashed just the 4.4.2 system and boot.img at some point. Now, going back to full 4.4.2, you have downgraded the Bootloader and partition table. That is a no-no.
Click to expand...
Click to collapse
I have bought the phone in this shape so i don't know what the previous owner did to it. What if i use donot touch bootloader but just use Super SU (Full Unroot) option to unroot and flash stock recovery img from "ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml" file, then will i be able to install OTA update of 4.4.4?

Usama Ahmed said:
I have bought the phone in this shape so i don't know what the previous owner did to it. What if i use donot touch bootloader but just use Super SU (Full Unroot) option to unroot and flash stock recovery img from "ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml" file, then will i be able to install OTA update of 4.4.4?
Click to expand...
Click to collapse
Don't take the OTA. Just try to flash the full 4.4.4 SBF!
You can find the full 4.4.4 Sprint SBF at one of the links here: http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347

samwathegreat said:
Don't take the OTA. Just try to flash the full 4.4.4 SBF!
You can find the full 4.4.4 Sprint SBF at one of the links here: http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
Click to expand...
Click to collapse
Ok i am getting a little scared right now. I don't want to brick my device. I have found one firmware which i think should be okay to go with.
ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip
Do you think i should go with it? Is their any chance of getting bricked? I have posted my system information picture above so you can see if it will be compatible with it.

Usama Ahmed said:
Ok i am getting a little scared right now. I don't want to brick my device. I have found one firmware which i think should be okay to go with.
ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip
Do you think i should go with it? Is their any chance of getting bricked? I have posted my system information picture above so you can see if it will be compatible with it.
Click to expand...
Click to collapse
The previous owner has left you with mismatched partitions. This state is known to be at risk of bricking....
Your safest option is to attempt to flash the 4.4.4 SBF (yes you linked the right file), but even this is not without risk. It might work perfectly fine, and you might end up having to de-brick it.
Wish I could give you a more definite answer, but anything other than flashing the full 4.4.4 SBF is very dangerous. Even flashing the entire 4.4.4 SBF has some risk.
Good Luck.

samwathegreat said:
The previous owner has left you with mismatched partitions. This state is known to be at risk of bricking....
Your safest option is to attempt to flash the 4.4.4 SBF (yes you linked the right file), but even this is not without risk. It might work perfectly fine, and you might end up having to de-brick it.
Wish I could give you a more definite answer, but anything other than flashing the full 4.4.4 SBF is very dangerous. Even flashing the entire 4.4.4 SBF has some risk.
Good Luck.
Click to expand...
Click to collapse
Thanks alot for your help. If you think there is even a slight chance of hard brick than i will stay with the current rom i have.
One last question, I you were in my position, would you go for flashing 4.4.4 SBF or would you just leave it as it is?

Usama Ahmed said:
Ok i am getting a little scared right now. I don't want to brick my device. I have found one firmware which i think should be okay to go with.
ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip
Do you think i should go with it? Is their any chance of getting bricked? I have posted my system information picture above so you can see if it will be compatible with it.
Click to expand...
Click to collapse
@samwathegreat is correct. You are trying to downgrade, hence the errors and problems. The key here is the screen shot of AP Fastboot, where the second line shows 30.B7 which is the bootloader for 4.4.4. So at this point, you only want to flash a 4.4.4 SBF, and never flash anything lower.
That does appear to be the correct 4.4.4 if you have a 2013 or First Gen... Sprint X.
I suggest you flash using mFastboot with the extra steps as listed in Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html However, if you are unsuccessful doing that, then you're going to need to visit the Unbricking thread and see if that can help you get fixed up.

KidJoe said:
@samwathegreat is correct. You are trying to downgrade, hence the errors and problems. The key here is the screen shot of AP Fastboot, where the second line shows 30.B7 which is the bootloader for 4.4.4. So at this point, you only want to flash a 4.4.4 SBF, and never flash anything lower.
That does appear to be the correct 4.4.4 if you have a 2013 or First Gen... Sprint X.
I suggest you flash using mFastboot with the extra steps as listed in Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html However, if you are unsuccessful doing that, then you're going to need to visit the Unbricking thread and see if that can help you get fixed up.
Click to expand...
Click to collapse
Hi KidJoe! Thanks for your reply. What can i post to confirm if i have chosen the right SBF for my phone (Yes it is Moto X First-Gen).
This is the file i am downloading right now. "ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip"
And if i flash it with what you mentioned, is their a chance of bricking my device?
BTW i try to flash "ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml" with the same method you posted which resulted in error due to the problem you mentioned above.

Usama Ahmed said:
Hi KidJoe! Thanks for your reply. What can i post to confirm if i have chosen the right SBF for my phone (Yes it is Moto X First-Gen).
This is the file i am downloading right now. "ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip"
And if i flash it with what you mentioned, is their a chance of bricking my device?
Click to expand...
Click to collapse
Your first screen shot in Post 1 shows your phone has 161.44.32.ghost_sprint.Sprint.en.US. In other words, Sprint rom. So you should be able to flash the Sprint 4.4.4 you found.
Ideally you want to look at the FINE PRINT on the bottom of the back of the phone. It will have a model, like XT1056, XT1060, XTT1049, XT1053, etc. The other option, if you have the original box, check the label on the end of it. If the IMEI number printed on the label, matches what phone shows in its menus, then that label on the box should also tell you the model (the box for my Verizon X has MOTXT1060DEV on the bar code label.), Since you got yours used, its VERY important you confirm that is the original box when trying to use the box to confirm the model number!
As for risks of bricking... well, that is an unknown. There have been MANY bricks caused when users got them selves into the situation your phone is in. There is no 100% risk free process to try and recover. And that is why there are so many warnings telling people to NOT DOWN GRADE!!!
What I'm suggesting has worked, but you are correct, there is still a chance to brick. Taking an OTA in the state your phone is in also has a risk of bricking. Anything you try and do at this point also have a risk of bricking.
Usama Ahmed said:
BTW i try to flash "ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml" with the same method you posted which resulted in error due to the problem you mentioned above.
Click to expand...
Click to collapse
Yes. The phone will ERROR if you try to flash an older GPT.BIN which is what you are encountering. (bootloader version indicates you had 4.4.4 on your phone, including its GPT.BIN and Bootloader).
The problem is this...
The Phone's previous owner had a FULL 4.4.4 ROM flashed to the phone. They attempted to downgrade. Since GPT.BIN and MOTOBOOT.IMG can not be downgraded, they did only PARTS!! Now the phone has mismatched bootloader, partition table and other parts compared to the older "System" and such which are installed.

KidJoe said:
Your first screen shot in Post 1 shows your phone has 161.44.32.ghost_sprint.Sprint.en.US. In other words, Sprint rom. So you should be able to flash the Sprint 4.4.4 you found.
Ideally you want to look at the FINE PRINT on the bottom of the back of the phone. It will have a model, like XT1056, XT1060, XTT1049, XT1053, etc. The other option, if you have the original box, check the label on the end of it. If the IMEI number printed on the label, matches what phone shows in its menus, then that label on the box should also tell you the model (the box for my Verizon X has MOTXT1060DEV on the bar code label.), Since you got yours used, its VERY important you confirm that is the original box when trying to use the box to confirm the model number!
As for risks of bricking... well, that is an unknown. There have been MANY bricks caused when users got them selves into the situation your phone is in. There is no 100% risk free process to try and recover. And that is why there are so many warnings telling people to NOT DOWN GRADE!!!
What I'm suggesting has worked, but you are correct, there is still a chance to brick. Taking an OTA in the state your phone is in also has a risk of bricking. Anything you try and do at this point also have a risk of bricking.
Yes. The phone will ERROR if you try to flash an older GPT.BIN which is what you are encountering. (bootloader version indicates you had 4.4.4 on your phone, including its GPT.BIN and Bootloader).
The problem is this...
The Phone's previous owner had a FULL 4.4.4 ROM flashed to the phone. They attempted to downgrade. Since GPT.BIN and MOTOBOOT.IMG can not be downgraded, they did only PARTS!! Now the phone has mismatched bootloader, partition table and other parts compared to the older "System" and such which are installed.
Click to expand...
Click to collapse
The model no written on back is XT1056. Just to be sure i have also attached the picture below. I am currently downloading "ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip".
Should i go for all these cmds?
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot reboot
Click to expand...
Click to collapse
Also in this process, is their chance of my phone dead?
Will these cmds also lock my bootloader or should i just leave it unlocked? As currently my phone has unlocked bootloader and is rooted.
A step by step (maximum safe steps) for flashing would be greatly appreciated.

Usama Ahmed said:
The model no written on back is XT1056. Just to be sure i have also attached the picture below. I am currently downloading "ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip".
Should i go for all these cmds?
Also in this process, is their chance of my phone dead?
Will these cmds also lock my bootloader or should i just leave it unlocked? As currently my phone has unlocked bootloader and is rooted.
A step by step (maximum safe steps) for flashing would be greatly appreciated.
Click to expand...
Click to collapse
XT1056 is Sprint. So ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip is the right ROM to use.
use EVERY COMMAND AS STATED in the link. If successful, all parts will be back in line, and consistent.
As I said, yes there is a chance you can brick your phone. Many other things can brick your phone while you are in this state too. There is no 100% "Safe" and "guaranteed to not brick your phone" process when you are in this state.
This process will NOT lock your bootloader. And samwathegreat already told you there is no need to re-lock it.

KidJoe said:
XT1056 is Sprint. So ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip is the right ROM to use.
use EVERY COMMAND AS STATED in the link. If successful, all parts will be back in line, and consistent.
As I said, yes there is a chance you can brick your phone. Many other things can brick your phone while you are in this state too. There is no 100% "Safe" and "guaranteed to not brick your phone" process when you are in this state.
This process will NOT lock your bootloader. And samwathegreat already told you there is no need to re-lock it.
Click to expand...
Click to collapse
Ok then i will be trying it right now and see what happens.

Thanks alot to @samwathegreat and @KidJoe. I have successfully updated my Moto X to 4.4.4 KitKat. I hope it had solved mismatched bootloader, partition table and other parts as mentioned by @KidJoe.
Attachment of process is below.

Usama Ahmed said:
Thanks alot to @samwathegreat and @KidJoe. I have successfully updated my Moto X to 4.4.4 KitKat. I hope it had solved mismatched bootloader, partition table and other parts as mentioned by @KidJoe.
Attachment of process is below.
Click to expand...
Click to collapse
Screen shot starts when system.img is flashing, so as long as the commands above that were also done and didn't error out, you are good!

Excellent support here! @samwathegreat and @KidJoe are GREAT!

KidJoe said:
Screen shot starts when system.img is flashing, so as long as the commands above that were also done and didn't error out, you are good!
Click to expand...
Click to collapse
Sorry i didn't realize that. Yes everything part was flashed without error otherwise i wouldn't go further.

But i am in a new problem now. My sim card is not working now. It says "Your SIM card does not allow a connection to this network". If anyone can help regarding that or if i can flash something to make it work.

Usama Ahmed said:
But i am in a new problem now. My sim card is not working now. It says "Your SIM card does not allow a connection to this network". If anyone can help regarding that or if i can flash something to make it work.
Click to expand...
Click to collapse
it appears you're not using sprint as your carrier... So You may now have to run this process to SIM unlock -> http://forum.xda-developers.com/moto-x/general/guide-success-sim-unlock-sprint-xt1056-t2825155

KidJoe said:
it appears you're not using sprint as your carrier... So You may now have to run this process to SIM unlock -> http://forum.xda-developers.com/moto-x/general/guide-success-sim-unlock-sprint-xt1056-t2825155
Click to expand...
Click to collapse
Yes i am not using sprint as my carrier. Thanks alot for the help again. I will try this now and post the result.

[Q] Unlocking error Bootloader

Is there any method to unlock the bootloader without activating the system developer option? I'm stuck on the boot screen and I can't unlock. ANDROID 5.1

Christian Correia said:
Is there any method to unlock the bootloader without activating the system developer option? I'm stuck on the boot screen and I can't unlock. ANDROID 5.1
Click to expand...
Click to collapse
Can you get into bootloader mode? And if not, what have you tried to get into bootloader mode?

JulesJam said:
Can you get into bootloader mode? And if not, what have you tried to get into bootloader mode?
Click to expand...
Click to collapse
Yes. Enter the RECOVERY and FASTBOOT normally. Actually I don't know what is bootloader mode, more goes into recovery and fastboot

Christian Correia said:
Yes. Enter the RECOVERY and FASTBOOT normally. Actually I don't know what is bootloader mode, more goes into recovery and fastboot
Click to expand...
Click to collapse
bootloader mode = fastboot
If a full system.img of 5.1 is not available for your device, I would get into bootloader mode and try to flash the 5.0 stock system using fastboot or mfastboot. Then see if you can unlock the bootloader. It may not work if you have upgraded your bootloader to 5.1 and please note - you cannot safely downgrade either the bootloader or partition table so don't even try.
What model device do you have? I am assuming that there is no 5.1 system.img available.

JulesJam said:
bootloader mode = fastboot
If a full system.img of 5.1 is not available for your device, I would get into bootloader mode and try to flash the 5.0 stock system using fastboot or mfastboot. Then see if you can unlock the bootloader. It may not work if you have upgraded your bootloader to 5.1 and please note - you cannot safely downgrade either the bootloader or partition table so don't even try.
What model device do you have? I am assuming that there is no 5.1 system.img available.
Click to expand...
Click to collapse
Unfortunately I can't downgrade. And the BOOTLOADER has been updated to version 60.16. The way it's going to be wait the full image (XT1097 5.1 23.11.14 current)

Christian Correia said:
Unfortunately I can't downgrade.
Click to expand...
Click to collapse
Why can't you downgrade just the system partition? If you get the official copy or the fxz, it is a signed image and so you can flash it using fastboot or mfastboot even with a locked bootloader. You may need to flash the 5.0 boot.img too.
What model do you have?

JulesJam said:
Why can't you downgrade just the system partition? If you get the official copy or the fxz, it is a signed image and so you can flash it using fastboot or mfastboot even with a locked bootloader. You may need to flash the 5.0 boot.img too.
What model do you have?
Click to expand...
Click to collapse
I tried to pass the 5.0 system image, plus the error. I do not know what to do. Precise image 5.1 23.32-14 which is what I was before the brick

Christian Correia said:
I tried to pass the 5.0 system image, plus the error. I do not know what to do. Precise image 5.1 23.32-14 which is what I was before the brick
Click to expand...
Click to collapse
What model phone do you have? Brazilian XT1097?

JulesJam said:
What model phone do you have? Brazilian XT1097?
Click to expand...
Click to collapse
Yes

Christian Correia said:
Yes
Click to expand...
Click to collapse
I think this is the official 5.0 firmware for it.
http://forum.xda-developers.com/moto-x-2014/development/rom-retail-br-firmware-t2995818
I would download it, then extract the system file(s). I don't know if they will be in sparsechunks or a single file, but if they are in sparsechunks, you can use regular fastboot to flash them. If the system is a single file system.img, you will have to use mfastboot version 2 to flash it.
I would try just flashing the system partition and then see if it boots. If not, then I would flash the 5.0 boot.img.
You also could try downgrading to 4.4.4 system, I know others have done it successfully.
Just do NOT take any OTAs - people are bricking when they downgrade and then take an OTA. You must wait for the 5.1 firmware to be released to flash it. Don't take an OTA.

JulesJam said:
I think this is the official 5.0 firmware for it.
http://forum.xda-developers.com/moto-x-2014/development/rom-retail-br-firmware-t2995818
I would download it, then extract the system file(s). I don't know if they will be in sparsechunks or a single file, but if they are in sparsechunks, you can use regular fastboot to flash them. If the system is a single file system.img, you will have to use mfastboot version 2 to flash it.
I would try just flashing the system partition and then see if it boots. If not, then I would flash the 5.0 boot.img.
You also could try downgrading to 4.4.4 system, I know others have done it successfully.
Just do NOT take any OTAs - people are bricking when they downgrade and then take an OTA. You must wait for the 5.1 firmware to be released to flash it. Don't take an OTA.
Click to expand...
Click to collapse
Friend didn't work. Gave Error DOWNGRADED VERSION SYSTEM

Christian Correia said:
Friend didn't work. Gave Error DOWNGRADED VERSION SYSTEM
Click to expand...
Click to collapse
The only other thing you could do and I don't know if the dev would agree to this, is use a software tool we have called MoFo - it allows you to flash unsigned files as long as they are in the ext4 format.
The developer is @maiko1 and I will ask on the MoFo thread if he would consider opening up the tool for this purpose. It costs $20 USD for the software. It would allow you bypass the bootloader signature check and force flash any unsigned file you want to the system partition.
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404

JulesJam said:
The only other thing you could do and I don't know if the dev would agree to this, is use a software tool we have called MoFo - it allows you to flash unsigned files as long as they are in the ext4 format.
The developer is @maiko1 and I will ask on the MoFo thread if he would consider opening up the tool for this purpose. It costs $20 USD for the software. It would allow you bypass the bootloader signature check and force flash any unsigned file you want to the system partition.
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
Click to expand...
Click to collapse
Works even with the locked bootloader? I am not spending money for nothing? Sure it works? Where can I get these images ext4?

Christian Correia said:
Works even with the locked bootloader? I am not spending money for nothing? Sure it works? Where can I get these images ext4?
Click to expand...
Click to collapse
Let me download the 5.0 image for your device and see if I can flash it to my XT1096 first using mofo.exe. I have a locked bootloader.
Since your bootloaders are unlockable, there is the possibility that maiko1 would discount it for you, idk, but you could ask since really it would just be a one time repair tool.
Also, do you know if someone who is still on the 5.1 soak can pull the 5.1 image from their device and make it flashable by mfastboot? Or would it fail the signature check? I don't know enough about that to know.
The other potential issue is that your boot.img is now 5.1 and maybe that would not boot with the 5.0 system.img. It should but you would need someone with an unlocked bootloader to try it and see if the 5.1 boot.img can run with the 5.0 system.

JulesJam said:
Let me download the 5.0 image for your device and see if I can flash it to my XT1096 first using mofo.exe. I have a locked bootloader.
Since your bootloaders are unlockable, there is the possibility that maiko1 would discount it for you, idk, but you could ask since really it would just be a one time repair tool.
Also, do you know if someone who is still on the 5.1 soak can pull the 5.1 image from their device and make it flashable by mfastboot? Or would it fail the signature check? I don't know enough about that to know.
Click to expand...
Click to collapse
I'm going to be standing by then. If it works I will buy

Christian Correia said:
I'm going to be standing by then. If it works I will buy
Click to expand...
Click to collapse
The dev has to agree to open it up for your model and I added this to my last post:
The other potential issue is that your boot.img is now 5.1 and maybe that would not boot with the 5.0 system.img. It should but you would need someone with an unlocked bootloader to try it and see if the 5.1 boot.img can run with the 5.0 system.
You would need to get someone with an unlocked bootloader XT1097 to see if the 5.1 boot.img will boot the 5.0 system.img. I think it should but it would be better to have someone test it.

JulesJam said:
The dev has to agree to open it up for your model and I added this to my last post:
The other potential issue is that your boot.img is now 5.1 and maybe that would not boot with the 5.0 system.img. It should but you would need someone with an unlocked bootloader to try it and see if the 5.1 boot.img can run with the 5.0 system.
You would need to get someone with an unlocked bootloader XT1097 to see if the 5.1 boot.img will boot the 5.0 system.img. I think it should but it would be better to have someone test it.
Click to expand...
Click to collapse
Thank you. I'm awaiting any news

Christian Correia said:
Thank you. I'm awaiting any news
Click to expand...
Click to collapse
And I guess the other potential issue is whether the 5.1 bootloader will unlock when running the 5.0 system.img - it may not. But at least your phone would work until the 5.1 firmware is released.
I am downloading the Brazilian XT1097 5.0 firmware file now and will flash it if it is flashable by mofo.exe - it will take me about an hour or so if everything goes smoothly.
---------- Post added at 04:42 AM ---------- Previous post was at 03:55 AM ----------
Christian Correia said:
Thank you. I'm awaiting any news
Click to expand...
Click to collapse
Ok, the image is broken down into sparse chunks like the AT&T XT1097. I will enlist the help of someone who was able to make the AT&T image into a single file ext4 file that could be flashed by mofo.exe but it is late my time so it won't be until tomorrow. It takes linux to do that and I don't use linux.
Also, there is the possibility that the exploit that mofo.exe relies on is patched in the 5.1 bootloader. I doubt it since 5.1 was out before mofo.exe was released. Maybe maiko1 would let you test it for free since we only know for sure that it works on the 5.0 and 5.0.2 bootloaders.

Christian Correia said:
Thank you. I'm awaiting any news
Click to expand...
Click to collapse
I have made the single file image but now I need another poster here to remove the footer and the header using a hex editor. Once that is done I can flash it to my device using mofo.exe to see if it flashes.

JulesJam said:
I have made the single file image but now I need another poster here to remove the footer and the header using a hex editor. Once that is done I can flash it to my device using mofo.exe to see if it flashes.
Click to expand...
Click to collapse
I'm waiting eagerly. Because it's been more than 1 week without my dear appliance. And I've tried everything to resuscitate him. And from what I've seen, the only way is to have a system image :fingers-crossed: