Related
I noticed on an unlocked bootloader, I can't downgrade the bootloader or gpt.bin (these are the only ones i checked once i read in another post about this). Can anyone explain why or how to do this? What is gpt.bin???
Kind of related - if the AT&T and Verizon locked BL 4.4 versions can downgrade, why can't I with an unlocked BL? It makes me feel cheated.. unless I'm not understanding something correctly...
mohlsen8 said:
I noticed on an unlocked bootloader, I can't downgrade the bootloader or gpt.bin (these are the only ones i checked once i read in another post about this). Can anyone explain why or how to do this? What is gpt.bin???
Kind of related - if the AT&T and Verizon locked BL 4.4 versions can downgrade, why can't I with an unlocked BL? It makes me feel cheated.. unless I'm not understanding something correctly...
Click to expand...
Click to collapse
actually, after playing with it for a while now, i was able to downgrade from 4.4 to 4.2 (camera update) using RSD Lite and the leaked firmware. using fastboot commands themselves doesn't work. it's weird.
i'd still love to know why we can't downgrade the bootloader and some other files on unlocked dev editions.
mohlsen8 said:
actually, after playing with it for a while now, i was able to downgrade from 4.4 to 4.2 (camera update) using RSD Lite and the leaked firmware. using fastboot commands themselves doesn't work. it's weird.
i'd still love to know why we can't downgrade the bootloader and some other files on unlocked dev editions.
Click to expand...
Click to collapse
you can. end of story. don't know what you read or what you are personally doing wrong that isn't allowing you to downgrade your device. but you most definitely can do this. there is nothing that you can't do with an unlocked bootloader.
jayboyyyy said:
you can. end of story. don't know what you read or what you are personally doing wrong that isn't allowing you to downgrade your device. but you most definitely can do this. there is nothing that you can't do with an unlocked bootloader.
Click to expand...
Click to collapse
This is absolutely correct!
jayboyyyy said:
you can. end of story. don't know what you read or what you are personally doing wrong that isn't allowing you to downgrade your device. but you most definitely can do this. there is nothing that you can't do with an unlocked bootloader.
Click to expand...
Click to collapse
there's a couple places i've seen this. and my bootloader is unlocked, and i can't downgrade, for instance, to the bootloader from the original t-mobile software (4.2.2 pre-camera) - this file, just to clarify (from sbf droid developers): TMO_XT1053_4.2.2-13.9.0Q2.X-116-X-17-6_CFC.xml.zip. i take the motoboot.img out and use "fastboot flash motoboot motoboot.img". i get:
(bootloader) Preflash validation failed
phone display says:
Failed to hab check for tz: 0x4e
?
while we're discussing, motorola says these can be relocked. in all of my screwing around this morning i was trying this too. i followed all directions and still cannot lock the phone. i use "fastboot oem lock" and it tells me:
(bootloader) FAIL: Please run fastboot oem lock begin first!
ok, so i use "fastboot oem lock begin". now it gives me:
(bootloader) Ready to flash signed images
ok, try "fastboot oem lock" again and then it gives me:
(bootloader) Re-Lock Failure. See Display
display says "No valid PIV block in SP for system piv validation failed (system) Re-lock failure".
i've tried many times to flash all stock files back to the phone using fastboot, as well as RDS Lite, and it's been successful each time, but it won't re-lock. i've also tried "fastboot oem lock begin" then flashing all the stock files, then "fastboot oem lock". still, no dice. what's up with this?
The updated bootloader isn't let you flash older files. If you flash a full package it will downgrade the bootloader first and then you can flash the other older files. If you use a program such as rsdlite it will handle it all for you.
Steve-x said:
The updated bootloader isn't let you flash older files. If you flash a full package it will downgrade the bootloader first and then you can flash the other older files. If you use a program such as rsdlite it will handle it all for you.
Click to expand...
Click to collapse
so if i flashed the entire 4.2.2 pre-camera file through RSD Lite, it would downgrade the bootloader as part of that? why am i not allowed to do this in fastboot manually?
mohlsen8 said:
so if i flashed the entire 4.2.2 pre-camera file through RSD Lite, it would downgrade the bootloader as part of that? why am i not allowed to do this in fastboot manually?
Click to expand...
Click to collapse
Yes, it would downgrade the bootloader.
You can do it with fastboot manually but you need to do it in the proper sequence is all.
Steve-x said:
Yes, it would downgrade the bootloader.
You can do it with fastboot manually but you need to do it in the proper sequence is all.
Click to expand...
Click to collapse
really? i had no idea that sequence mattered. why would that matter if i have an unlocked bootloader and want to flash an older one onto the device?
i just tried running the 4.2.2 pre-camera file through rsd lite (after removing the getvar line as usual) and it fails on 2/16 (flashing gpt.bin). screen says "downgraded security version. update gpt_main version failed. preflash validation failed for GPT".
i don't understand why it won't work for me and i really would love to understand all of this.
mohlsen8 said:
really? i had no idea that sequence mattered.
i just tried running the 4.2.2 pre-camera file through rsd lite (after removing the getvar line as usual) and it fails on 2/16 (flashing gpt.bin). screen says "downgraded security version. update gpt_main version failed. preflash validation failed for GPT".
i don't understand why it won't work for me and i really would love to understand all of this.
Click to expand...
Click to collapse
to me happens the same, shouls we first downgrade bootloader and recovery before using GPT, maybe our version of RSD lite is not the same?
beelzebu said:
to me happens the same, shouls we first downgrade bootloader and recovery before using GPT, maybe our version of RSD lite is not the same?
Click to expand...
Click to collapse
i have 6.14. going to install 6.15 now and try.
edit: 6.15 does the same thing. won't flash 4.2.2 pre-camera through RSD Lite because of the downgraded security error on GPT.bin.
mohlsen8 said:
i have 6.14. going to install 6.15 now and try.
edit: 6.15 does the same thing. won't flash 4.2.2 pre-camera through RSD Lite because of the downgraded security error on GPT.bin.
Click to expand...
Click to collapse
Had the same issue with downgrading from the camera ota to the pre camera sbf file, rsdlite wouldn't flash got.bin failed, I think it possibly the ota that prevents downgrading, but if you flash from one sbf file and downgrade you're OK, I haven't tried it, just a thought
Sent on my Moto X
flashallthetime said:
Had the same issue with downgrading from the camera ota to the pre camera sbf file, rsdlite wouldn't flash got.bin failed, I think it possibly the ota that prevents downgrading, but if you flash from one sbf file and downgrade you're OK, I haven't tried it, just a thought
Sent on my Moto X
Click to expand...
Click to collapse
Are you saying you were able to flash the pre-camera sbf? edit: sorry - didn't read you right at first. i have tried it through rsd lite and no go.
I don't actually want to go back to that.. just want to know what the deal is with my "unlocked" bootloader. what i think is that the bootloader cannot be downgraded (and then gpt.bin and stuff subsequently cannot be). Someone pulled an oopsie with the 4.4 update because even the AT&T/Verizon versions can downgrade, so we can downgrade that but not to the pre-camera one.
I'm just used to nexuses where i can fastboot flash whatever i want whenever i want. i would just love clarification just to know what the deal is.
mohlsen8 said:
Are you saying you were able to flash the pre-camera sbf? edit: sorry - see you said you didn't try this. i have tried it through rsd lite and no go.
I don't actually want to go back to that.. just want to know what the deal is with my "unlocked" bootloader. what i think is that the bootloader cannot be downgraded (and then gpt.bin and stuff subsequently cannot be). Someone pulled an oopsie with the 4.4 update because even the AT&T/Verizon versions can downgrade, so we can downgrade that but not to the pre-camera one.
I'm just used to nexuses where i can fastboot flash whatever i want whenever i want. i would just love clarification just to know what the deal is.
Click to expand...
Click to collapse
No I couldn't flash the pre camera sbf firmware after accepting the camera fix through ota, I believe flashing the ota flashes something that's prevents you from downgrading. You could try inserting the camera fix gpt.bin file into the pre camera sbf file and see if it flashes ?don't know if it will work
Sent on my Moto X
flashallthetime said:
No I couldn't flash the pre camera sbf firmware after accepting the camera fix through ota, I believe flashing the ota flashes something that's prevents you from downgrading. You could try inserting the camera fix gpt.bin file into the pre camera sbf file and see if it flashes ?don't know if it will work
Sent on my Moto X
Click to expand...
Click to collapse
at that point i could easily just flash everything other than gpt.bin and motoboot. i was hopping around on some of them today just to check it out. it's those two that are the issue.
mohlsen8 said:
at that point i could easily just flash everything other than gpt.bin and motoboot. i was hopping around on some of them today just to check it out. it's those two that are the issue.
Click to expand...
Click to collapse
now that's interesting. figured i'd try it anyway, so in the pre-camera SBF file i replaced gpt.bin with the post-camera gpt.bin and it flashes fine through rsd lite, motoboot and all. what the hell.
I think you can downgrade to any version. Check out the xml file for the order of operations. You will see some of them flash a few parts, then reboot the phone, and then continue with the flashing process. Others flash everything one partition after the other. I believe that reboot is vital for certain downgrades.
Steve-x said:
I think you can downgrade to any version. Check out the xml file for the order of operations. You will see some of them flash a few parts, then reboot the phone, and then continue with the flashing process. Others flash everything one partition after the other. I believe that reboot is vital for certain downgrades.
Click to expand...
Click to collapse
i thought that as well and compared the two 4.2.2 xml's and did not find any real differences like that. not to mention gpt.bin is the first thing flashed and it fails when it tries to flash it. i'd like to know if anyone is or was able to directly flash 4.2.2 pre-camera without replacing the gpt.bin or motoboot.
mohlsen8 said:
i thought that as well and compared the two 4.2.2 xml's and did not find any real differences like that. not to mention gpt.bin is the first thing flashed and it fails when it tries to flash it. i'd like to know if anyone is or was able to directly flash 4.2.2 pre-camera without replacing the gpt.bin or motoboot.
Click to expand...
Click to collapse
i would assume that your issue is coming from flashing OTAs that are not specific for dev phones (don't even know if dev phone OTAs are available). Im not certain of all of this, but when you flash the same OTA that a non-dev phone uses, it will still impliment the security checks to not let you downgrade even though your bootlader is unlocked. Perhaps you may need to unlock the bootloader again (even though it says it is unlocked). Again, i don't actually know this to be true, but I would assume that there is an error somewhere in some code that is relocking (or something like that) a dev phone that flashes the OTAs that are coming out. A nexus wouldn't ahve this problem because none of their OTAs are ever locked anyway (i believe). So the problem is probably with Verizon not releasing a different OTA for unlocked dev phones as opposed to consumer editions.
Im just speculating. Im sure you can find the answer on google if you read up about what unlocking the bootloader actually means.
jayboyyyy said:
i would assume that your issue is coming from flashing OTAs that are not specific for dev phones (don't even know if dev phone OTAs are available). Im not certain of all of this, but when you flash the same OTA that a non-dev phone uses, it will still impliment the security checks to not let you downgrade even though your bootlader is unlocked. Perhaps you may need to unlock the bootloader again (even though it says it is unlocked). Again, i don't actually know this to be true, but I would assume that there is an error somewhere in some code that is relocking (or something like that) a dev phone that flashes the OTAs that are coming out. A nexus wouldn't ahve this problem because none of their OTAs are ever locked anyway (i believe). So the problem is probably with Verizon not releasing a different OTA for unlocked dev phones as opposed to consumer editions.
Im just speculating. Im sure you can find the answer on google if you read up about what unlocking the bootloader actually means.
Click to expand...
Click to collapse
is that a dig? you don't have to be a jerk. i'm not some idiot pressing buttons over here. just asking if anyone knows why this is.
this is for t-mobile. but i have a gsm dev edition, same model as t-mobile etc. even the official firmware files for the GSM Developer Edition, that i downloaded directly from Motorola themselves, are labeled "T-MOBILE RETAIL..". i don't think the dev edition ever had the pre-camera version (it shipped with the update applied). so maybe you're right about that. i dunno. i'm not the only one who's reporting this. i was just really curious to know why this is.
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.
Hello,
It had the original rom 4.4 on my XT1058 with root and unlocked bootloader, but was not getting running with 4.4.2 update for the original recovery. So I was going to be able to update and run fasthall.bat back to 4.2.2, but I opened the file and rebooted the machine to backup and forgot that it was open. Result: ****ed me.
I believe I have lost my bootloader, but following the tutorial of Gundabolu SC, unable to enter fastboot again, however, I can not run the sbf or RSD by flashall.bat.
I noticed that my phone with this LOCKED status, though I unlocked it.
To start the fastboot I run the code the tutorial I mentioned above, then it displays the following screen
Code:
[COLOR="Red"]Failed to hab check for gpt_main: 0x4e
CID Read Failure
Invalid CID Status 0x69
CustomerID error. Contact Dealer: 0xdead
No SP Partition found[/COLOR]
[COLOR="DarkOrange"]Fastboot Reason: Invalid CID[/COLOR]
For both methods to recovery, it becomes part of gpt.bin and when arrives at motoboot, of the following error message:
Code:
[COLOR="DarkOrange"]getvar max-download-size
downloading 32768 bytes
done
getvar max-download-size
downloading 1643008 bytes[/COLOR]
[COLOR="Red"]downgraded security version
update aboot version failed[/COLOR]
Can anyone help me?
------------
Problem solved thanks to XDA's amazing users!
feelknOck said:
Hello,
It had the original rom 4.4 on my XT1058 with root and unlocked bootloader, but was not getting running with 4.4.2 update for the original recovery. So I was going to be able to update and run fasthall.bat back to 4.2.2, but I opened the file and rebooted the machine to backup and forgot that it was open. Result: ****ed me.
I believe I have lost my bootloader, but following the tutorial of Gundabolu SC, unable to enter fastboot again, however, I can not run the sbf or RSD by flashall.bat.
For both methods, it becomes part of gpt.bin and when arrives at motoboot, of the following error message:
Code:
downgraded security version
aboot version update failed
Can anyone help me?
Click to expand...
Click to collapse
You can try go to this link Hope it helps
http://forums.androidcentral.com/mo...7371-unroot-unbrick-your-phone-using-sbf.html
---------- Post added at 04:31 PM ---------- Previous post was at 04:18 PM ----------
Did it worked??S i am too not quite sure about this??
manav113 said:
You can try go to this link Hope it helps
http://forums.androidcentral.com/mo...7371-unroot-unbrick-your-phone-using-sbf.html
Click to expand...
Click to collapse
I tried to recover via RSD several times, both with 4.4, as 4.2.2, but both have the same error.
In the RSD panel the following error message:
Code:
Failed flash process. 2/13 flash mootboot "motoboot.img" -> Phone returned FAIL.
quite a different error.NEVER heard of it>Wait let me ask my friends about it..
manav113 said:
quite a different error.NEVER heard of it>Wait let me ask my friends about it..
Click to expand...
Click to collapse
the issue is the bootloader you are trying to install dose not match the one installed so it will fail everytime we have to find the right one to get everything installed correct
so we need to grab the 100% correct firmware package for your phone.
the model you gave me is for the AT&T version
here is the 4.4 AT&T firmware try installing this one
http://sbf.droid-developers.org/download.php?device=0&file=4
let me know the outcome.
dray_jr said:
the issue is the bootloader you are trying to install dose not match the one installed so it will fail everytime we have to find the right one to get everything installed correct
so we need to grab the 100% correct firmware package for your phone.
the model you gave me is for the AT&T version
here is the 4.4 AT&T firmware try installing this one
http://sbf.droid-developers.org/download.php?device=0&file=4
let me know the outcome.
Click to expand...
Click to collapse
I'm downloading and post the result. 202 KB/s
Thank you!
-
dray_jr said:
the issue is the bootloader you are trying to install dose not match the one installed so it will fail everytime we have to find the right one to get everything installed correct
so we need to grab the 100% correct firmware package for your phone.
the model you gave me is for the AT&T version
here is the 4.4 AT&T firmware try installing this one
http://sbf.droid-developers.org/download.php?device=0&file=4
let me know the outcome.
Click to expand...
Click to collapse
Sorry for double post there.
I remember that my device is the XT1058, but Brazil.
I downloaded the sbf, removed the max-download-size and run the RSD, but he brought me the same errors.
Sounds like you need to wait for the full 4.4.2 Brazil image to be posted for download to recover the phone.
Steve-x said:
Sounds like you need to wait for the full 4.4.2 Brazil image to be posted for download to recover the phone.
Click to expand...
Click to collapse
Excuse me, but why do you think?
I did not get to install 4.4.2, I started to run the script flashall.bat 4.2.2 and thinking it would give time, it ended up damaging the bootloader.
Tried the firm indicated that dray_jr and 2 BR's, but it did not work.
I am very worried.
Did you try this, sounds like your trying to flash 4.2.2 firmware over 4.4.2 which won't work http://forum.xda-developers.com/showthread.php?t=2628940
Sent on my Gummy running Lenoto X
Do you get the "downgraded security version" error when trying to flash 4.2.2 and 4.4 ?
flashallthetime said:
Did you try this, sounds like your trying to flash 4.2.2 firmware over 4.4.2 which won't work http://forum.xda-developers.com/showthread.php?t=2628940
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I was going to try and probably would work (I've done this several times and has no secret), but it was not to start. I opened flashall.bat script but forgot to close it, because it was going back up yet, but the script detected the fastboot and started the process.
With seconds I removed the cable, barely gave it to start the first stage (before I left without turning back) and corrupted my bootloader.
I had the Original ROM 4.4 installed with root and unlocked bootloader, but even trying the 4.4 firmware I get the errors I described above.
Would have something to do with the tutorial I follow to start the fastboot?
I am Brazilian and even translating and reading what little I understand, I can not identify a problem as well. I'm scouring all here and trying something, but like I said, I am a layman and do not understand how the bootloader and related work.
Steve-x said:
Do you get the "downgraded security version" error when trying to flash 4.2.2 and 4.4 ?
Click to expand...
Click to collapse
With 2 firmwares I get the same error.
everytime i post here i reread the first thread and i am still not sure what you did.
so im going to ask some questions and see if we can't get some more info on this issue
1. Your device was 4.4 unlocked bootloader and rooted
2. did you try and install the 4.4.2 firmware
3. your device is the AT&T model but from Brazil
because if you are getting the gpt error on both 4.2.2 and 4.4 and it would lead me to think that the 4.4.2 bootloader is installed on your device.
dray_jr said:
everytime i post here i reread the first thread and i am still not sure what you did.
so im going to ask some questions and see if we can't get some more info on this issue
1. Your device was 4.4 unlocked bootloader and rooted
2. did you try and install the 4.4.2 firmware
3. your device is the AT&T model but from Brazil
because if you are getting the gpt error on both 4.2.2 and 4.4 and it would lead me to think that the 4.4.2 bootloader is installed on your device.
Click to expand...
Click to collapse
He removed the cable as it was flashing, can you get to the fastboot screen?
Sent on my Gummy running Lenoto X
dray_jr said:
everytime i post here i reread the first thread and i am still not sure what you did.
so im going to ask some questions and see if we can't get some more info on this issue
1. Your device was 4.4 unlocked bootloader and rooted
2. did you try and install the 4.4.2 firmware
3. your device is the AT&T model but from Brazil
because if you are getting the gpt error on both 4.2.2 and 4.4 and it would lead me to think that the 4.4.2 bootloader is installed on your device.
Click to expand...
Click to collapse
1. Yes, I was running 4.4 with unlocked bootloader and rooted
2. I installed the original recovery to try the OTA update for version 4.4.2, but he returned me error halfway through the update, because my ROM was modified. That's when I thought of going back to 4.2.2 without changes and run the 4.4.2.
3. My device is the XT1058 Retail Brazil.
flashallthetime said:
He removed the cable as it was flashing, can you get to the fastboot screen?
Click to expand...
Click to collapse
Yes, I can start the fastboot via script "qflash.exe with (PORT NUMBER)-ramload MPRG8960.hex-mbn 33 MSM8960_bootloader_singleimage.bin-v-o" with a blank bootloader.
feelknOck said:
1. Yes, I was running 4.4 and unlocked bootloader routed.
2. I installed the original recovery to try the OTA update for version 4.4.2, but he returned me error halfway through the update, because my ROM was modified. That's when I thought of going back to 4.2.2 without changes and run the 4.4.2.
3. My device is the XT1058 Retail Brazil.
Yes, I can start the fastboot via script "qflash.exe with (PORT NUMBER)-ramload MPRG8960.hex-mbn 33 MSM8960_bootloader_singleimage.bin-v-o" with a blank bootloader.
Click to expand...
Click to collapse
ok if i remember well first flash recovery from 4.4 firmware
mfastboot flash recovery recovery.img
after then u ll be able to flash entire image of 4.4.2
could it be that even thou the 4.4.2 update failed that it still installed the new bootloader and that is why nothing else will install.
but either way he could flash the 4.4 firmware without the gpt file and then take the OTA and everything should be fine.
danger2u said:
ok if i remember well first flash recovery from 4.4 firmware
mfastboot flash recovery recovery.img
after then u ll be able to flash entire image of 4.4.2
Click to expand...
Click to collapse
Before having this problem I tried all that.
I installed the original recovery and tried to upgrade to 4.4.2 but it gave error in the middle of the update and restarted the phone saying that the software update was not completed.
dray_jr said:
could it be that even thou the 4.4.2 update failed that it still installed the new bootloader and that is why nothing else will install.
but either way he could flash the 4.4 firmware without the gpt file and then take the OTA and everything should be fine.
Click to expand...
Click to collapse
I will remove the line from gpt and try again.
Earlier I was testing at work and now I'm home. The 4.4 firmware download this lingering: (
you really can't cause anymore problems so this is what i would try because from what i have read if you try to install 4.2.2 or 4.4 you the a gpt.bin verification error. which means that neither 4.2.2 or 4.4 are the right bootloader.
That leaves us with some how the 4.4.2 bootloader got installed because it is the only bootloader that can't go to 4.4 so with that being said.
I would download the correct 4.4 firmware for your phone.
extract it
and use the below adb commands to install it but leave out the gpt.bin flash command
Code:
*leave this one out*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
i think everything should install fine and your phone should boot up and from what i have read you should still be able to take the 4.4.2 OTA without bricking your phone
I tried to downgrade from 4.4.3 (really bad battery life being the reason) to 4.4.2 and couldn't do it. The bootloader is unlocked. Used the manual method and then used the RSD Lite method and got the same "preflash validation failed for GPT" error. Don't know how to get around it. Thankfully, in the fastboot, scrolled down to "factory" and upon clicking it was able to get back into my original 4.4.3 stock ROM. So does anyone know how to downgrade? I'd appreciate the help.
If you're getting an error on GPT.BIN, that means the partition table has changed in 4.4.3 and you can't downgrade to 4.4.2.
I didn't think this was the case.. i.e. there were posts saying that the versions hadn't changed.
You can always try option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html but I expect it will error.
KidJoe said:
If you're getting an error on GPT.BIN, that means the bootloader and partition table has changed in 4.4.3 and you can't downgrade to 4.4.2.
I didn't think this was the case.. i.e. there were posts saying that the versions hadn't changed.
You can always try option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html but I expect it will error.
Click to expand...
Click to collapse
I just extracted the official 4.4.3 update.zip: it DOES contain a new GPT.BIN
I was also under the impression that people reported success downgrading 4.4.3 > 4.4.2 because the bootloader itself did not change.
OP: Could you verify that you are using the correct 4.4.2 SBF for the XT1053? This one: http://sbf.droid-developers.org/download.php?device=0&file=840
samwathegreat said:
I just extracted the official 4.4.3 update.zip: it DOES contain a new GPT.BIN
Click to expand...
Click to collapse
I can't find my 4.4.2 T-Mo sbf, so I'm having to download it again. I was going to compare the two, as well as motoboot.img...
download is taking forever
If GPT.BIN is different between 4.4.3 and 4.4.2, then downgrading wont be possible unless mfastboot is used, and the person is willing to have miss matched versions on their phone (which wont be a good/safe state for taking possible future updates)
samwathegreat said:
I just extracted the official 4.4.3 update.zip: it DOES contain a new GPT.BIN
I was also under the impression that people reported success downgrading 4.4.3 > 4.4.2 because the bootloader itself did not change.
OP: Could you verify that you are using the correct 4.4.2 SBF for the XT1053? This one: http://sbf.droid-developers.org/download.php?device=0&file=840
Click to expand...
Click to collapse
Yep that is the version that I downloaded and attempted to downgrade to. No joy.
KidJoe said:
I can't find my 4.4.2 T-Mo sbf, so I'm having to download it again. I was going to compare the two, as well as motoboot.img...
download is taking forever
If GPT.BIN is different between 4.4.3 and 4.4.2, then downgrading wont be possible unless mfastboot is used, and the person is willing to have miss matched versions on their phone (which wont be a good/safe state for taking possible future updates)
Click to expand...
Click to collapse
No, I don't think I'm going to do that if that's the case. The thing that's draining my battery is the kernel. Can I just flash a different kernel to combat the problem?
mufakir said:
No, I don't think I'm going to do that if that's the case. The thing that's draining my battery is the kernel. Can I just flash a different kernel to combat the problem?
Click to expand...
Click to collapse
Do you guys think this method will work? :
http://translate.google.com/transla...ngrade+4.4.3+moto+x&es_sm=93&biw=1366&bih=643
mufakir said:
Do you guys think this method will work? :
http://translate.google.com/transla...ngrade+4.4.3+moto+x&es_sm=93&biw=1366&bih=643
Click to expand...
Click to collapse
that is basically like using mfastboot to flash everything but GPT.BIN... so you'll have a missmatched GPT.BIN on there. While it may work, it might be a little flakey, and definitely not safe to take future updates.
KidJoe said:
I can't find my 4.4.2 T-Mo sbf, so I'm having to download it again. I was going to compare the two, as well as motoboot.img...
download is taking forever
If GPT.BIN is different between 4.4.3 and 4.4.2, then downgrading wont be possible unless mfastboot is used, and the person is willing to have miss matched versions on their phone (which wont be a good/safe state for taking possible future updates)
Click to expand...
Click to collapse
@mufakir,
Download completed and I was able to compare.
@samwathegreat is completely correct. GPT.BIN in 4.4.3 is different than 4.4.2.
Unlike with 4.4.2, motoboot.img (the bootloader) did NOT change. Never the less, the upgraded GPT.BIN in 4.4.3 is enough to prevent successful downgrade to 4.4.2.
4.4.3 has not yet been released for Verizon so I can't do any testing.
The only possible way to downgrade would be *IF* the following works to downgrade GPT.BIN.....
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
(followed by flashing the rest of the rom)
If that still fails, then you can't downgrade 4.4.3's GPT.BIN, and therefore can not successfully or fully downgrade to 4.4.2.
Hi all. I'm an idiot. I updated to the 5.0 rom, and tried to downgrade to 4.4.3. It went well, until my device tried to update to 4.4.4. Now I'm stuck with a bootloader (xt1053 30.B7) that says it's locked, says it can't be unlocked, and says
Code:
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup:0x35
CID read failure
Invalid CID status 0x69
CustomerID error. Contact dealer: 0xdead
no SP partition found
Please, is there any way to bring my device back to life? I've tried flashing pretty much anything I can get my hands on, but it always fails because the bootloader is locked. I tried unlocking it with the code I got from motorola a while back, but that's not working either. Again, please help if possible.
I'm a jackass. I'm trying the RSD with the newest SBF now.
Hopefully the 4.4.4 will fix you up.
thehanutedtubby said:
Hi all. I'm an idiot. I updated to the 5.0 rom, and tried to downgrade to 4.4.3. It went well, until my device tried to update to 4.4.4. Now I'm stuck with a bootloader (xt1053 30.B7) that says it's locked, says it can't be unlocked, and says
Code:
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup:0x35
CID read failure
Invalid CID status 0x69
CustomerID error. Contact dealer: 0xdead
no SP partition found
Please, is there any way to bring my device back to life? I've tried flashing pretty much anything I can get my hands on, but it always fails because the bootloader is locked. I tried unlocking it with the code I got from motorola a while back, but that's not working either. Again, please help if possible.
Click to expand...
Click to collapse
I am not very familiar with how Moto's phone's do their stuff. But, have you tried flashing the stock image for your device? One thing though, if you used the leaked soak test to upgrade your device, your screwed until the official lollipop image for your device comes up.
thehanutedtubby said:
Hi all. I'm an idiot. I updated to the 5.0 rom, and tried to downgrade to 4.4.3. It went well, until my device tried to update to 4.4.4. Now I'm stuck with a bootloader (xt1053 30.B7) that says it's locked, says it can't be unlocked, and says
Code:
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup:0x35
CID read failure
Invalid CID status 0x69
CustomerID error. Contact dealer: 0xdead
no SP partition found
Please, is there any way to bring my device back to life? I've tried flashing pretty much anything I can get my hands on, but it always fails because the bootloader is locked. I tried unlocking it with the code I got from motorola a while back, but that's not working either. Again, please help if possible.
Click to expand...
Click to collapse
IF you updated to one of the 5.02 leaks (or soaks as they were called), and got this message when trying to downgrade by flashing an OLDER Moto SBF (like 4.4.4), then you will likely be stuck until a 5.02 SBF leaks.
GPT.BIN doesn't like being downgraded, or attempted to be downgraded.
However, if your bootloader still says 30.B7, I would try flashing the stock Moto Xt1053 4.4.4 SBF using mfastboot by following option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html
So the bootloader does say it's 30.b7, but it also says it's locked. And when I try to unlock it, it says fastboot oem unlock disabled. I have tried flashing back to 4.4.4, but I think the updated gpt from 5.0.2 is messing it up.
As a few of us have tried to warn people, and just like the mad rush to flash kit Kat when it came out.... You will likely need to wait for the SBF of 5.0.2 for your device. Not much else you can do at this point.
Sorry for your unfortunate situation.
I managed to get it running again by flashing the gpt of the lollipop files. I'm doing my best to go to the 1053 lollipop build to avert another brick. Thanks all for the help!
And I'm successfully on the XT1053 lollipop build. Let it be known that I'm only on lollipop to avoid incompatibilities due to the new GPT I had to flash. Sorry Motorola. Trust me, I wish I had waited.
thehanutedtubby said:
And I'm successfully on the XT1053 lollipop build. Let it be known that I'm only on lollipop to avoid incompatibilities due to the new GPT I had to flash. Sorry Motorola. Trust me, I wish I had waited.
Click to expand...
Click to collapse
I did the same thing with my moto x and now I dont know what to do with it, can you help me?
Does yours say exactly what mine does? If so, flash the gpt.bin from the 5.0.2 zip's root directory, and reflash 4.4.4 completely. Then update using the zip from the other thread.
thehanutedtubby said:
Does yours say exactly what mine does? If so, flash the gpt.bin from the 5.0.2 zip's root directory, and reflash 4.4.4 completely. Then update using the zip from the other thread.
Click to expand...
Click to collapse
Can you explain what you did after flashing 4.4.4 with the gpt.bin from 5.0.2. I'm about to do that but am not sure what update in another thread you are referencing.
thanks.
thank you bro, i was really desperate! this must be stickie!
A sticky on how to possibly brick your device with one false move?