Hey All, I'm trying to downgrade (rogers) from 4.4.2 to 4.2.2 in order to successfully obtain root on 4.4.2, but each time I use RSD to try and downgrade I get the error message "failed flashing process 2/16 partition "gpt.bin" moto x" and on boatloader it says "downgraded security version update gpt_main version failed preflash validation failed for GPT"
Anyone ever have this issue?
endiz said:
Hey All, I'm trying to downgrade (rogers) from 4.4.2 to 4.2.2 in order to successfully obtain root on 4.4.2, but each time I use RSD to try and downgrade I get the error message "failed flashing process 2/16 partition "gpt.bin" moto x" and on boatloader it says "downgraded security version update gpt_main version failed preflash validation failed for GPT"
Anyone ever have this issue?
Click to expand...
Click to collapse
There's actually several posts here, including a sticky with bootloader information about this. Moto upgraded the bootloader in 4.4.2 and it cannot be downgraded. Sorry, you're stuck on 4.4.2 and stuck without root until someone finds an exploit.
endiz said:
Hey All, I'm trying to downgrade (rogers) from 4.4.2 to 4.2.2 in order to successfully obtain root on 4.4.2, but each time I use RSD to try and downgrade I get the error message "failed flashing process 2/16 partition "gpt.bin" moto x" and on boatloader it says "downgraded security version update gpt_main version failed preflash validation failed for GPT"
Anyone ever have this issue?
Click to expand...
Click to collapse
Forget slapmymoto, if you want root you have only 1 choice, unlock your bootloader which you can do on a Rogers moto x , I did it the day I got my moto from robbers way back in sept. No that's not a typo Rogers the robber
Sent on my Gummy running Lenoto X
flashallthetime said:
Forget slapmymoto, if you want root you have only 1 choice, unlock your bootloader which you can do on a Rogers moto x , I did it the day I got my moto from robbers way back in sept. No that's not a typo Rogers the robber
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Yep, unlock that sucker, and you guys don't actually use Rogers do you? ewwwww
I didn't realize the Rogers version could be bootloader unlocked. You will of course void your warranty. But if you unlock it, it as simple as fastboot flash recovery twrp-recovery.img
Steve-x said:
Yep, unlock that sucker, and you guys don't actually use Rogers do you? ewwwww
Click to expand...
Click to collapse
Yah I know rogers the robber, they're as bad as Verizon, or like my x wife, just can't get rid if either
Sent on my Gummy running Lenoto X
flashallthetime said:
Yah I know rogers the robber, they're as bad as Verizon, or like my x wife, just can't get rid if either
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Unlocked, flashed twrp, rooted. Ah, that feels much better.
endiz said:
Unlocked, flashed twrp, rooted. Ah, that feels much better.
Click to expand...
Click to collapse
Easy breezy
Now what firmware are you running?
Sent on my Gummy running Lenoto X
I think I'll stick with stock rogers + xposed. Until CM11 is stable at least...
I'm pretty happy with the stock firmware myself now that I have the carrier name removed and the battery percent in black added.
Related
can I install the 4.4.2 upgrade on 4.4 without flashing the bootloader??
opinions?
No.
Sent from my Moto X cellular telephone...
sekelink said:
can I install the 4.4.2 upgrade on 4.4 without flashing the bootloader??
opinions?
Click to expand...
Click to collapse
The sbf firmware no don't even try, your best bet is to wait for either eclipse or kangakat ROMs to be updated, you need to have a unlocked bootloader with a custom recovery. Please people do not take short cuts with your bootloader
Sent on my Gummy running Lenoto X
flashallthetime said:
The sbf firmware no don't even try, your best bet is to wait for either eclipse or kangakat ROMs to be updated, you need to have a unlocked bootloader with a custom recovery. Please people do not take short cuts with your bootloader
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Yes i have bootloader unlocked and rooted xt1058 latin america phone. I would like to test the 4.4.2 update without flash the gpt and motoboot. This is because i want my phone with the bootloader not stuck in 4.4.2
sekelink said:
Yes i have bootloader unlocked and rooted xt1058 latin america phone. I would like to test the 4.4.2 update without flash the gpt and motoboot. This is because i want my phone with the bootloader not stuck in 4.4.2
Click to expand...
Click to collapse
No no no, if you have problems please don't open a thread if your phone gets borked, theres minor differences between 4,4 and 4.4.2 you want even know what they changed
Sent on my Lenoto A2109 tablet
My Moto X won't boot, and it's 4.4.2 so the stock 4.4 image from Motorola won't flash. I get some type of gpt downgrade warning.
What can I do? I don't care about preserving data.
Thanks
fbiryujin said:
My Moto X won't boot, and it's 4.4.2 so the stock 4.4 image from Motorola won't flash. I get some type of gpt downgrade warning.
What can I do? I don't care about preserving data.
Thanks
Click to expand...
Click to collapse
flash this 4.4.2 SBF file for verizon
http://sbf.droid-developers.org/download.php?device=0&file=841
enjoy
dray_jr said:
flash this 4.4.2 SBF file for verizon
http://sbf.droid-developers.org/download.php?device=0&file=841
enjoy
Click to expand...
Click to collapse
Thanks. I will give that a shot tonight.
I don't understand why you believe you can't flash 4.4 over 4.4.2 with dev edition with an unlocked bootloader. That only applies to locked bootloaders.
nhizzat said:
I don't understand why you believe you can't flash 4.4 over 4.4.2 with dev edition with an unlocked bootloader. That only applies to locked bootloaders.
Click to expand...
Click to collapse
sorry you are wrong there that applies to all Moto X's
you can not flash 4.4 before the bootloader will not downgrade you will get a error when it tries.
the only upside to having a unlocked bootloader is that you can root any version of android by just installed a custom recovery then installing the SuperSU flashable zip file.
Today
07:10 PM
by poda13
Replies: 1
Views: 76
Go to first new post
hope that helps
dray_jr said:
sorry you are wrong there that applies to all Moto X's
you can not flash 4.4 before the bootloader will not downgrade you will get a error when it tries.
the only upside to having a unlocked bootloader is that you can root any version of android by just installed a custom recovery then installing the SuperSU flashable zip file.
Click to expand...
Click to collapse
You're right. The 4.4.2 bootloader can't be downgraded regardless of model.
nhizzat said:
You're right. The 4.4.2 bootloader can't be downgraded regardless of model.
Click to expand...
Click to collapse
The 4.4.2 bootloader can't be downgraded; but I think the 4.4 system image and kernel could flashed just fine on an unlocked unit even if the bootloader has been upgraded for 4.4.2. You would need to flash the 4.4 manually so that it doesn't try and flash the 4.4 bootloader though.
jasoraso said:
The 4.4.2 bootloader can't be downgraded; but I think the 4.4 system image and kernel could flashed just fine on an unlocked unit even if the bootloader has been upgraded for 4.4.2. You would need to flash the 4.4 manually so that it doesn't try and flash the 4.4 bootloader though.
Click to expand...
Click to collapse
This is what I had to wind up doing as the other image I had wouldn't flash. I edited the xml to skip the gpt and bootloader, and it flashed 4.4 back. Updated again and I'm all good
fbiryujin said:
This is what I had to wind up doing as the other image I had wouldn't flash. I edited the xml to skip the gpt and bootloader, and it flashed 4.4 back. Updated again and I'm all good
Click to expand...
Click to collapse
please dont do that if you need to flash the 4.4.2 for verizon. please grab it from SBF they have added the 4.4.2 SBF package for verizon on the website. i do not recommend editing the XML file for the chance or bricking your phone.
Hi, is been over a week from the ATT 4.4.2 release and i wanted just to ask if someone is working at the full firmware because i really need to flash that after i bad flash an european version without thinking that i had the bootloader locked and an AT&T phone, help! 10 days without and andorid phone!
ATT just started pushing the OTA... it could be a few weeks until we see a full SBF available. Until then, with a locked bootloader there is nothing you can do, because you can't flash files not signed by motorola.
I'm sure as soon as its available it will be posted here -> http://sbf.droid-developers.org/phone.php?device=0
hem, why the firmware isn't out? someone is working at it? i really need the upload because my phone always boot on fastboot for a bad flash, please
Albi.ema23 said:
hem, why the firmware isn't out? someone is working at it? i really need the upload because my phone always boot on fastboot for a bad flash, please
Click to expand...
Click to collapse
Its not out because Moto doesn't release it... we rely on people to gain access and leak the files.. So there is no set time table for them being available.
I'm sure the people who maintain that site are continually trying to grab the latest SBF files. So as soon as they get access to it, it will be posted.
KidJoe said:
Its not out because Moto doesn't release it... we rely on people to gain access and leak the files.. So there is no set time table for them being available.
I'm sure the people who maintain that site are continually trying to grab the latest SBF files. So as soon as they get access to it, it will be posted.
Click to expand...
Click to collapse
ah, so... what i should do? the phone "think" that the last ATT firmware is a downgrade because i tryed to flash the 4.4.2 EU, there is a way or i MUST wait for ATT 4.4.2 firmware?
Albi.ema23 said:
ah, so... what i should do? the phone "think" that the last ATT firmware is a downgrade because i tryed to flash the 4.4.2 EU, there is a way or i MUST wait for ATT 4.4.2 firmware?
Click to expand...
Click to collapse
I would say wait.
Others might suggest flashing say the T-Mobile/GSM DEV XT1053 rom... but I'm not sure how safe that is.
KidJoe said:
I would say wait.
Others might suggest flashing say the T-Mobile/GSM DEV XT1053 rom... but I'm not sure how safe that is.
Click to expand...
Click to collapse
can that be flashed on a XT1058 ATT bootloader locked?
KidJoe said:
I would say wait.
Others might suggest flashing say the T-Mobile/GSM DEV XT1053 rom... but I'm not sure how safe that is.
Click to expand...
Click to collapse
do you think that an motorola service center can do something?
Albi.ema23 said:
can that be flashed on a XT1058 ATT bootloader locked?
Click to expand...
Click to collapse
Locked bootloader? Not sure. And I really hesitate to suggest flashing roms for other models.
Albi.ema23 said:
do you think that an motorola service center can do something?
Click to expand...
Click to collapse
They will likely try and do warranty. But if you flashed with wrong rom, they may not cover it as "under warranty"
Btw, you never really said what rom you tried flashing, and exactly what issues you are having now.
KidJoe said:
They will likely try and do warranty. But if you flashed with wrong rom, they may not cover it as "under warranty"
Btw, you never really said what rom you tried flashing, and exactly what issues you are having now.
Click to expand...
Click to collapse
i tried to flash "Blur_Version.161.44.16.ghost_row.Retail.en.EU" with RDS Lite but the flash has stop at the boot "failed sflashing process. 6/17 flash boot "boot.img" then i tried the same with the adb&fastboot after that i turn on the phone and on the screen there was "Failed to hab check for boot: 0x56 preflash validation failed for boot", Failed to hab check for recovery : 0x56 preflash validation failed for recovery , Failed to hab check for boot: 0x56 PIV block validation for system failed Invalid PIV image: system
then i re flashed the original ATT 4.4 and at the boot in the screen was writen Partition (boot) Security Version Downgraded
Albi.ema23 said:
i tried to flash "Blur_Version.161.44.16.ghost_row.Retail.en.EU" with RDS Lite but the flash has stop at the boot "failed sflashing process. 6/17 flash boot "boot.img" then i tried the same with the adb&fastboot after that i turn on the phone and on the screen there was "Failed to hab check for boot: 0x56 preflash validation failed for boot", Failed to hab check for recovery : 0x56 preflash validation failed for recovery , Failed to hab check for boot: 0x56 PIV block validation for system failed Invalid PIV image: system
then i re flashed the original ATT 4.4 and at the boot in the screen was writen Partition (boot) Security Version Downgraded
Click to expand...
Click to collapse
Yeah, once you get 4.4.2 on there you do NOT want to downgrade.
At this point, you can try reading -> http://forum.xda-developers.com/moto-x/general/tut-resurrecting-bricked-moto-x-corrupt-t2629057 but post #120 implies you need the ATT 4.4.2 SBF to really fix it.
KidJoe said:
Yeah, once you get 4.4.2 on there you do NOT want to downgrade.
At this point, you can try reading -> http://forum.xda-developers.com/moto-x/general/tut-resurrecting-bricked-moto-x-corrupt-t2629057 but post #120 implies you need the ATT 4.4.2 SBF to really fix it.
Click to expand...
Click to collapse
sorry but what does SBF means?
Albi.ema23 said:
sorry but what does SBF means?
Click to expand...
Click to collapse
Its an acronym. I'm not sure what each of the letters stand for exactly...
Basically an SBF file is a completely stock system image. You flash it through the RSDlite tool. It will completely revert your phone back to stock. FXZ was also used at one point when referring to such an image.
For the X, the SBF is actually a packed zip file which contains all the parts, and an XML file which tells RSDLite what to flash, in what order, and some stuff. You could also unzip it and use mFastboot to flash the individual parts instead of using RSDLite.
KidJoe said:
Its an acronym. I'm not sure what each of the letters stand for exactly...
Basically an SBF file is a completely stock system image. You flash it through the RSDlite tool. It will completely revert your phone back to stock. FXZ was also used at one point when referring to such an image.
For the X, the SBF is actually a packed zip file which contains all the parts, and an XML file which tells RSDLite what to flash, in what order, and some stuff. You could also unzip it and use mFastboot to flash the individual parts instead of using RSDLite.
Click to expand...
Click to collapse
so..that mean i must wait for the 4.4.2 ATT anyway? and that motorola center can't do nothing about it?
Albi.ema23 said:
so..that mean i must wait for the 4.4.2 ATT anyway? and that motorola center can't do nothing about it?
Click to expand...
Click to collapse
to fix it yourself, you need to wait. Or you could do more harm than good.
A moto service center may fix it or send you a refurbished phone. And if they do, they might not cover it under warranty since you have a non-developer edition that you tried to flash the wrong rom too which put you in this situation. i.e. the warranty terms cover defects in materials and workmanship, not drops, getting wet, or other damage from improper operation or use. (flashing the rom for another model or carrier would be considered improper operation or use)... So it might cost $$$
If this is your only phone, and you need it working now, then you have no choice but to call Moto (if Moto Maker) or ATT (if retail non-customized) to see about "warranty" and see what happens. Otherwise use another phone temporarily and just wait for the ATT 4.4.2 SBF to leak, as you should be able to fix your phone by flashing it.
I need to block BOOTLOADER my moto x on Android 4.4.3. After the update the error. In Android 4.4.2 worked. Now there's more
Christian Correia said:
I need to block BOOTLOADER my moto x on Android 4.4.3. After the update the error. In Android 4.4.2 worked. Now there's more
Click to expand...
Click to collapse
If you want to lock it:
fastboot oem lock
But there is absolutely no reason to do that. You don't gain any functionality by re-locking (you actually LOSE functionality), and Moto still knows you previously unlocked.
You can NEVER change your status back to "Locked". Once you unlock, status changes to "Unlocked", and if you subsequently re-lock the status changes to "Re-Locked".
I'm really curious why you would want to to re-lock. Your post really doesn't make any sense....
Good Luck
Thank you friend. I get more p following error: No valid block in SP PIV system is
piv validation failed (system)
Re-lock failure
Christian Correia said:
Thank you friend. I get more p following error: No valid block in SP PIV system is
piv validation failed (system)
Re-lock failure
Click to expand...
Click to collapse
What did you do?
This didn't happen by itself. Give us some background info - what are you trying to accomplish, and at what point did your phone get in the state it is in now?
Also, re-locking bootloader will not help with whatever it is you are trying to accomplish.....which I still don't understand.
Okay, thanks I'll leave it the way it is. Since Motorola deebloqueei I know him. Answer me one thing, BOOTLOADER unlocked Smartphone affects the performance or something.?
Christian Correia said:
Okay, thanks I'll leave it the way it is. Since Motorola deebloqueei I know him. Answer me one thing, BOOTLOADER unlocked Smartphone affects the performance or something.?
Click to expand...
Click to collapse
No, it does not affect performance. It allows you to root your device easily, and (optionally) flash custom roms and custom recovery.
Are you trying to upgrade or downgrade? I still don't understand your problem...
I wanted to downgrade to 4.4.2. And I did and I upgraded to 4.4.3 via OTA. Most wanted the complete 4.4.3 firmware update because I think it detracted. And so I thought it was because of the BOOTLOADER. I'm a bit newbie in this regard
Christian Correia said:
I wanted to downgrade to 4.4.2. And I did and I upgraded to 4.4.3 via OTA. Most wanted the complete 4.4.3 firmware update because I think it detracted. And so I thought it was because of the BOOTLOADER. I'm a bit newbie in this regard
Click to expand...
Click to collapse
NEVER NEVER attempt to downgrade. It is well documented that you can permanently brick your phone if you try.
If you want to flash the entire 4.4.3 STOCK IMAGE, you can do that!!!
Follow the instructions here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
You can find the STOCK IMAGES here: http://sbf.droid-developers.org/phone.php?device=0
MAKE SURE you use the correct image for YOUR carrier and version.
EDIT: The only 4.4.3 image that has been released is for T-Mobile. If you are not on T-Mobile, DO NOT attempt the process I outlined above. Just wait until the image for YOUR CARRIER becomes available.
Again, whatever you do, do NOT attempt to downgrade.
Friend could not find version 4.4.3 for my Moto X XT1058. As I do now.?
Christian Correia said:
Friend could not find version 4.4.3 for my Moto X XT1058. As I do now.?
Click to expand...
Click to collapse
The only 4.4.3 complete stock image that has been released is for T-Mobile XT1053. If you are not on T-Mobile, DO NOT attempt the process I outlined above. Just wait until the image for YOUR CARRIER becomes available.
Again, whatever you do, do NOT attempt to downgrade.
It looks like you will have to wait until the new 4.4.3 image for your XT1058 becomes available.
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?