I did an OTA update, and SMS stopped working and also my screen wouldn't shut off automatically (nor when I hit the button).
So I tried flashing back to the 4.4.2 version from sbf.droid-developers but I got an error.
No valid PIV block in SP for system
piv validation failed (system)
Fastboot Reason: Boot Failure
Now I'm stuck in AP Fastboot. It says Battery Low, but I can get it to say Battery OK by plugging it into the wall and then rebooting it or something weird like that. It's hard to get it to do it but it's possible.
Anyway, it doesn't matter what version I try to flash now, boot and system give me errors when trying to flash.
Partition (boot) Security Version Downgraded
It seems like I need to be unlocked in order to downgrade, but to unlock I have to get out of fastboot. Am I perma bricked?
Not sure how I fixed it to be honest, but I'll try to recall some things that might help others.
At the end of a long road of reinstalling drivers, fighting with the low battery, trying various versions of the firmwares, and trying multiple scripts/tools, I got it to work.
I ended up using (not sure how much of this is relevant);
Motorola Drivers from the Motorola Device Manager
RSD lite, v6.1.4
The newest 4.4.2 firmware
eulogy1337 said:
Not sure how I fixed it to be honest, but I'll try to recall some things that might help others.
At the end of a long road of reinstalling drivers, fighting with the low battery, trying various versions of the firmwares, and trying multiple scripts/tools, I got it to work.
I ended up using (not sure how much of this is relevant);
Motorola Drivers from the Motorola Device Manager
RSD lite, v6.1.4
The newest 4.4.2 firmware
Click to expand...
Click to collapse
The only part of that which would be relevant is if you did in fact use the newest 4.4.2 firmware. This would be 18X.46.15. The reasons that is relevant is because (1) you titled your original post that you were attempting to un-do the most recent update (which you have now successfully installed again) and (2) If you are on the .15 firmware and not .10, you will not be able to unlock your bootloader now. You may or may not be aware of that already. Otherwise, you did exactly what was needed to make your phone operable. :good:
netizenmt said:
The only part of that which would be relevant is if you did in fact use the newest 4.4.2 firmware. This would be 18X.46.15. The reasons that is relevant is because (1) you titled your original post that you were attempting to un-do the most recent update (which you have now successfully installed again) and (2) If you are on the .15 firmware and not .10, you will not be able to unlock your bootloader now. You may or may not be aware of that already. Otherwise, you did exactly what was needed to make your phone operable. :good:
Click to expand...
Click to collapse
I used the newest 4.4.2 on that site (which is .10). I was getting errors before and the only glaring difference is the version of RSD lite. I dunno why it worked then and not before.
eulogy1337 said:
I used the newest 4.4.2 on that site (which is .10). I was getting errors before and the only glaring difference is the version of RSD lite. I dunno why it worked then and not before.
Click to expand...
Click to collapse
Well, now that you mention is, I suppose an older version of RSD Lite might generate that error. .10 is the money version of 4.4.2 - if you have .10, you can still unlock your BL by following the tutorials for KitKat to do so. .15 is the -newest- version, but primarily, it's an update to fix the exploits that allow .10 to be unlocked and rooted, so don't do it before you unlock. Once you are unlocked, .15 is fine - you will still be able to install a custom recovery, root, etc. I would install the recovery before you update as well, personally. Good luck!
netizenmt said:
Well, now that you mention is, I suppose an older version of RSD Lite might generate that error. .10 is the money version of 4.4.2 - if you have .10, you can still unlock your BL by following the tutorials for KitKat to do so. .15 is the -newest- version, but primarily, it's an update to fix the exploits that allow .10 to be unlocked and rooted, so don't do it before you unlock. Once you are unlocked, .15 is fine - you will still be able to install a custom recovery, root, etc. I would install the recovery before you update as well, personally. Good luck!
Click to expand...
Click to collapse
I'm still having most of the issues that made me try to un-do the update anyway.
Texts take ~20 mins to send out. Phone calls seem okay. Google Play Store freezes non-stop (downloading/installing new apps takes forever, usually gets stuck downloading around 75% regardless of the size of the app). If I go to Developer Options, the Settings app locks up until I close it (I wanted to see if I could switch to/from ART). Battery might be draining faster too.
I'm afraid to get stuck back at the fastboot. What should I do?
What can I do with this? I installed the update and I wasn't able to root my xt907.
As stupid as I could be, I went inmediately to RSD with the same ROM I flashed just a couple of hours ago (want don't have the most recent update, I think).
Stuck at Fastboot. Fastboot Reason: Flash Failure
When I try to re-flah, it says:
usb connected
downgraded security version
update gpt_main version failed
preflash validation failed from GPT
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to fix the Brick of RSD (at least this worked for me)
A collab I want to do... This solved me right now my problem
In the xml file (assuming you removed any lines which contains “GetVar”, “var” or “oem”), delete the following lines:
<step operation="flash" partition="partition" filename="gpt.bin" MD5="5B3FD782141145E4BD1C9270D954AFF1" />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="8514ED883150B7A0579F9431CD872B39" />
Click to expand...
Click to collapse
I don't know what are these files, but my phone came back from death :fingers-crossed: :laugh:
If this helps anyone, just... Yay!
Attatched, how it goes the XML file
I had a similar issue, and now i believe i need the 46.15 firmware to get back up and running. But it doesn't seem to be something i can find online.
There is a thread with the .15 FW in the general section.
Sent from my HTC6525LVW using Tapatalk
Related
if you are still on 1.8.3 stock, you can get a copy of 4.5.91.sbf file by using Motorola Software Update, handy if you need to flash a clean version of 4.5.91 on 4.5.40 or 4.5.91(OTA upgraded).
by default, the sbf file is saved to:
C:\Program Files (x86)\Motorola\Software Update\firmwares\1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
copy it to somewhere else before Motorola Software Update finishes flashing or it will get deleted automatically.
erasen1 said:
if you are still on 1.8.3 stock, you can get a copy of 4.5.91.sbf file by using Motorola Software Update, handy if you need to flash a clean version of 4.5.91 on 4.5.40 or 4.5.91(OTA upgraded).
by default, the sbf file is saved to:
C:\Program Files (x86)\Motorola\Software Update\firmwares\1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
copy it to somewhere else before Motorola Software Update finishes flashing or it will get deleted automatically.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Have you flashed it yet? I sent Kennithpenn a pm about this and he asked me not to release it. He also told me it is not safe to flash via rsd!!
flashing ...
erasen1 said:
flashing ...
Click to expand...
Click to collapse
Are you using Motorola Software Update tool or RSD 5.3.1 to flash it? Also was you bl already unlocked before or after you did it?
NYG-SBXLII said:
Are you using Motorola Software Update tool or RSD 5.3.1 to flash it? Also was you bl already unlocked before or after you did it?
Click to expand...
Click to collapse
at first, I used Motorola Software Update tool to flash, it flashed successfully - as expected
then I tried to flash it using RSD Lite v5.0, also flashed successfully, it actually did not erase user & data partition, retaining all apps & settings.
NYG-SBXLII said:
Are you using Motorola Software Update tool or RSD 5.3.1 to flash it? Also was you bl already unlocked before or after you did it?
Click to expand...
Click to collapse
the phone was BL unlocked before, I flashed from 4.5.40 back to 1.8.3 sbf, then " fastboot oem lock" ( not sure if it locks the phone back), then Motorola Software Update tool & RSD.
erasen1 said:
at first, I used Motorola Software Update tool to flash, it flashed successfully - as expected
then I tried to flash it using RSD Lite v5.0, also flashed successfully, it actually did not erase user & data partition, retaining all apps & settings.
Click to expand...
Click to collapse
Ok, well 4.5.40 was never released so thats probably why you where able to downgrade to 1.83. Im not sure if it is a good idea to flash this after 4.5.91 though. probably not a good idea to release unless someone has the ball's to flash it from 4.5.91 bl unlock.
edit: well you flashed it via rsd after you used Motorola Software Update. So it might be all good..
edit: **** it, i've got insurance, im going to give a go... I was bl unlocked and flashed leaked ota
edit: confirmed, 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf is safe via rsd 5.3.1 after ota bl unlocked 4.5.91!
edit: this seems to be a service sbf as it does not wipe data!
NYG-SBXLII said:
I sent Kennithpenn a pm about this and he asked me not to release it.
Click to expand...
Click to collapse
What do you mean he told you not to release it. The upgrade file is freely available from Motorola now. You can download direct to your PC from the software updater.
Would this work for me if after pulling the OTA I am stuck at the Motorola M with Dual Core? Could I flash this SBF and get my phone back up and running? I tried using the Motorola Software Update software but not sure what mode to connect my phone for it to recognize it.. Connected via Fastboot the software says:
"Motorola Software Update is unable to identify you device at this time. Please Try again"
Thank you in advance
NYG-SBXLII said:
Ok, well 4.5.40 was never released so thats probably why you where able to downgrade to 1.83. Im not sure if it is a good idea to flash this after 4.5.91 though. probably not a good idea to release unless someone has the ball's to flash it from 4.5.91 bl unlock.
edit: well you flashed it via rsd after you used Motorola Software Update. So it might be all good..
edit: **** it, i've got insurance, im going to give a go... I was bl unlocked and flashed leaked ota
edit: confirmed, 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf is safe via rsd 5.3.1 after ota bl unlocked 4.5.91!
edit: this seems to be a service sbf as it does not wipe data!
Click to expand...
Click to collapse
NYG, Thanks for experimenting..
Question: So if I do the OTA update, then I MOD the hell out of it. I can use this SBF file and RSD to go back to stock and my phone will be like nothing ever changed...???
you shouldn't install this directly, but it is very handy to have (in order to extract images)
my method is to download it through the program but disconnect the phone as soon as it starts to download. when it finishes, you should have the file there, copy/move it whatever and exit the program.
b30sam said:
NYG, Thanks for experimenting..
Question: So if I do the OTA update, then I MOD the hell out of it. I can use this SBF file and RSD to go back to stock and my phone will be like nothing ever changed...???
Click to expand...
Click to collapse
Yes, but just like the ota, after you flash this, you can never flash firmware lower than 4.5.91 again or you will get a hard brick. Also depending on what ROM you are on before you flash this you may have to manually wipe data because this sbf does not.
franciscojavierleon said:
you shouldn't install this directly, but it is very handy to have (in order to extract images)
my method is to download it through the program but disconnect the phone as soon as it starts to download. when it finishes, you should have the file there, copy/move it whatever and exit the program.
Click to expand...
Click to collapse
This file can now be downloaded from the dev section. http://forum.xda-developers.com/showthread.php?t=1181932
Well i was needing revert my custom firmware and bootloader to stock (also relock bootloader)
but i was very afraid about you can revert uncloked bootloader if you do it with Pudding
http://forum.xda-developers.com/showthread.php?t=1136261
My atrix 4G (MB860) comes with the latest v4.5.145 (AT&T)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And I was running CF SuperLite_CM10_V8, with TWRP 2.6.3 Recovery
I decided to flash de SBF file running the risk of a brick, but i was reading this post
http://www.grupoandroid.com/topic/76554-downgrade-de-45145-a-141-y-unlock-bootloader/
If i get a soft-brick....
I use RSDLite 6.1.5 + MTK PATCH to flash
And 1ff-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-att-us-gas_na_olpsgbattspe_p012.sbf.gz as my flash file
And if you are reading this post it's because you allready have installed your MotoDrivers rigth?
(I do it from my Win 8 Computer, x64 system)
My Result? a MB860 Stock 2.3.6-4.5.141 with Locked Bootloader
Later i perform an upgrade from my phone to 2.3.6-4.5.145 (Moto Blur ID rerquired)
To end one more time in my first same version.
If you decided to do this IT'S ALL UNDER YOUR OWN RESPONSABILITY!!!
I'm just sharing my own experience!!!
Conclusion: It's posible Restock & Relock from Pudding Without Brick your MB860 Atrix 4G :good:
Saludos desde Tijuana B.C MX :laugh:
Any Gramatical Correction are welcome!, English it's not my natal Language!
klonic0 said:
Well i was needing revert my custom firmware and bootloader to stock (also relock bootloader)
but i was very afraid about you can revert uncloked bootloader if you do it with Pudding
http://forum.xda-developers.com/showthread.php?t=1136261
My atrix 4G (MB860) comes with the latest v4.5.145 (AT&T)
And I was running CF SuperLite_CM10_V8, with TWRP 2.6.3 Recovery
I decided to flash de SBF file running the risk of a brick, but i was reading this post
http://www.grupoandroid.com/topic/76554-downgrade-de-45145-a-141-y-unlock-bootloader/
If i get a soft-brick....
I use RSDLite 6.1.5 + MTK PATCH to flash
And 1ff-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-att-us-gas_na_olpsgbattspe_p012.sbf.gz as my flash file
And if you are reading this post it's because you allready have installed your MotoDrivers rigth?
(I do it from my Win 8 Computer, x64 system)
My Result? a MB860 Stock 2.3.6-4.5.141 with Locked Bootloader
Later i perform an upgrade from my phone to 2.3.6-4.5.145 (Moto Blur ID rerquired)
To end one more time in my first same version.
If you decided to do this IT'S ALL UNDER YOUR OWN RESPONSABILITY!!!
I'm just sharing my own experience!!!
Conclusion: It's posible Restock & Relock from Pudding Without Brick your MB860 Atrix 4G :good:
Saludos desde Tijuana B.C MX :laugh:
Any Gramatical Correction are welcome!, English it's not my natal Language!
Click to expand...
Click to collapse
Way late on this. Everybody knows how to return to stock.
palmbeach05 said:
Way late on this. Everybody knows how to return to stock.
Click to expand...
Click to collapse
Well... hehe :silly:
Stuck in the same boat! Please advise...
Many thanks klonic0 for your post, it has given me hope!
I am stuck in a similar situation with an AT&T Atrix 4G that has the v4.5.145 unlocked bootloader and absolutely refuses to flash back to the stock 1ff-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-att-us-gas_na_olpsgbattspe_p012.sbf image.
The phone experiences frequent SODs and drains its battery extremely quickly.
The Motorola RSD lite (with the MTK patch) keeps failing at "switching to BP Pass through mode".
(I have tried about 7 variations from windows xp through to Windows 8.1 on 32 and 64 bit machines.
After which I am back to square one, i.e. a "Failed to boot 1" error message on the top left corner of the phones screen, I then have to flash anyone of the following three sbf files to get the phone working again:
pudding.sbf or 4547-fix-try2.sbf or trololol-unlock234.sbf
Is there any hope to flash back this phone back to the stock image with a locked bootloader?
bevilz said:
Many thanks klonic0 for your post, it has given me hope!
I am stuck in a similar situation with an AT&T Atrix 4G that has the v4.5.145 unlocked bootloader and absolutely refuses to flash back to the stock 1ff-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-att-us-gas_na_olpsgbattspe_p012.sbf image.
The phone experiences frequent SODs and drains its battery extremely quickly.
The Motorola RSD lite (with the MTK patch) keeps failing at "switching to BP Pass through mode".
(I have tried about 7 variations from windows xp through to Windows 8.1 on 32 and 64 bit machines.
After which I am back to square one, i.e. a "Failed to boot 1" error message on the top left corner of the phones screen, I then have to flash anyone of the following three sbf files to get the phone working again:
pudding.sbf or 4547-fix-try2.sbf or trololol-unlock234.sbf
Is there any hope to flash back this phone back to the stock image with a locked bootloader?
Click to expand...
Click to collapse
Yes, it should be working. Did you factory reset? Did you look into what failed to boot 1 means?
Sent from my ATRIX HD using XDA Free mobile app
Update: No results yet...
palmbeach05 said:
Yes, it should be working. Did you factory reset? Did you look into what failed to boot 1 means?
Sent from my ATRIX HD using XDA Free mobile app
Click to expand...
Click to collapse
Hi Palmbeach05! Thank you for replying so quickly.
Yes I have factory reset the device before every attempt to flash the sbf using RSD Lite, and I have looked into the "failed to boot 1" error as well, it follows the information from this "quote" on the Atrix 4G GSMarena.com page 5:
"to all those people out there who own a motorola atrix 4g and have unlocked their bootloader 4.5.145 and are having sleep of death issues aka SOD where the phone does not wake up after a period of inactivity download moto software updater from motorola website and follow the on screen instructions moto software updater will download the stock 4.5.145 and automatically flash it and finally u will get rid of sleep of death issues and remember u will have to be in stock firmware the moto software update wont recognize your phone if u are on cyanogenmod word of advice if u are already on 4.5.145 never unlock the bootloader because there is no unlockable bootloader for 4.5.145 all the unlocked boootloaders are from previous versions so even though they unlock the phone there will be consequences like sod and random reboots on high temperatures so bottom line is u have to go back to stock many people will tell u to flash via rsd lite but trust me rsd lite is of no help as it wont be able to flash successfully because 4.5.145 sbf is not available and rsd cant downgrade so it will give an error message error switching phone to BP pass through mode but the moto software updater will be able to download the 4.5.145 sbf from motorola website and flash it automatically"
Unfortunately I have had absolutely no luck with the Motorola software update software package either.
I realize this is an old thread, but I'm very interested in this and I couldn't find the right information.
Motorola has given me the run around because none of their links ever work anymore (like this one: https://forums.motorola.com/posts/9bae279371).
Is there any sort of official md5 checksum for this file? How do you know you're downloading something legit from 4shared?
Thanks so much.
(The method I tried it myself and it works perfectly and does not cause any problems, however I am not responsible of damage to your phone)
* REQUIREMENTS:
-Unlocked Bootloader
-Firmware T-Mobile 4.4.4 download
-RSD Lite
-ADB & Fastboot drivers
-Notepad++
*INSTRUCTIONS:
1. Download firmware T-Mobile 4.4.4 and extract all zip files.
2. Open the file RETAIL-US_4.4.4_KXA21.12-L1.29.1_2_cid9_CFC_1FF.xml with Notepad++ (preferably) or editor text.
3. Delete lines:
Code:
<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="76e5f85606012c083d46f37425c441b1" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="2b664024c8a421245b814e3b7c4c5077" />
4. Save the file and open RSD Lite and upload the edited file in RSD Lite.
5. Turn off the phone and put it into fastboot mode and connect to PC. When RSD Lite recognizes the device and indicate that you are connected press START to realize the downgrade.
6. Wait until the phone reboots and have Android 4.4.4 KitKat back. :good:
attached the modified xml file, just change the extension .txt to .xml
IMPORTANT: Do not try to reinstall soak test lollipop, otherwise it may cause brick your phone.
Isn't this dangerous to do so?
You're skipping the gpt.bin and motoboot which may cause issues with KitKat and skipping these and later upgrading by any OTA has resulted in some bricked devices.
I don't think this is a good idea.
Sent from my Moto X using XDA Free mobile app
I believe there are enough warnings about this. This procedure is just ok if for whatever reason somebody wants to have all 4.4.4 but gpt and motoboot.
For any other upgrade or downgrade, anybody interested need to look really hard into it before flashing any isht.
So all good.
hbenz2008 said:
I believe there are enough warnings about this. This procedure is just ok if for whatever reason somebody wants to have all 4.4.4 but gpt and motoboot.
For any other upgrade or downgrade, anybody interested need to look really hard into it before flashing any isht.
Click to expand...
Click to collapse
Since people STILL do it, even though it has the very real potential to BRICK phones, and/or cause other issues, I would say we STILL don't have enough warnings...
And we still have threads popping up like this -> http://forum.xda-developers.com/moto-x/moto-x-qa/screwed-t3059954
In my opinion, EVERY post/thread advising people its "OK" or "Safe" to downgrade, should at least include warnings that bricking is possible, before any instructions are presented.
And we have seen threads suggesting to downgrade get locked/deleted
tazlooney89 said:
(The method I tried it myself and it works perfectly and does not cause any problems, however I am not responsible of damage to your phone)
* REQUIREMENTS:
-Unlocked Bootloader
-Firmware T-Mobile 4.4.4 download
-RSD Lite
-ADB & Fastboot drivers
-Notepad++
*INSTRUCTIONS:
1. Download firmware T-Mobile 4.4.4 and extract all zip files.
2. Open the file RETAIL-US_4.4.4_KXA21.12-L1.29.1_2_cid9_CFC_1FF.xml with Notepad++ (preferably) or editor text.
3. Delete lines:
Code:
<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="76e5f85606012c083d46f37425c441b1" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="2b664024c8a421245b814e3b7c4c5077" />
4. Save the file and open RSD Lite and upload the edited file in RSD Lite.
5. Turn off the phone and put it into fastboot mode and connect to PC. When RSD Lite recognizes the device and indicate that you are connected press START to realize the downgrade.
6. Wait until the phone reboots and have Android 4.4.4 KitKat back. :good:
attached the modified xml file, just change the extension .txt to .xml
IMPORTANT: Do not try to reinstall soak test lollipop, otherwise it may cause brick your phone.
Click to expand...
Click to collapse
OP, please don't color your text. this is what your post looks like to me:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
also, this is what it looks like when i quote your text:
If you downgrade back to 4.4.4, will it be safe to upgrade once the official 5.0.2 comes out?
640k said:
OP, please don't color your text. this is what your post looks like to me:
also, this is what it looks like when i quote your text:
Click to expand...
Click to collapse
Errr, I'm not sure that everyone is going to re-style their posts to work optimally with your browser themes and modifications. It works fine with the standard browsers I checked... Problems on your end.
Kinda misleading to say this "causes no problems" when it will most likely brick any phone that gets an OTA after its done?
I get pretty annoyed how much we refuse to discuss downgrading and associated issues out of fear that people will be educated JUST enough to be dangerous... I'd still rather not rely on safety through ignorance and abstinence... But man it seems like your little red disclaimer should at least mention they have a good chance to ruin their phone if they take an OTA. (Still don't get why everyone here with unlocked bootloaders is so obsessed with OTAs, I have never had a modded phone where people would even consider taking OTAs... Always just wait for a safe flashable version, but apparently the moto x community is different *shrug*)
athulele said:
Isn't this dangerous to do so?
You're skipping the gpt.bin and motoboot which may cause issues with KitKat and skipping these and later upgrading by any OTA has resulted in some bricked devices.
I don't think this is a good idea.
Sent from my Moto X using XDA Free mobile app
Click to expand...
Click to collapse
I tried flashing with the gpt.bin and motoboot still in the XML file but get a "downgrade security detected" and it stops due to trying to downgrade. Is there a better way to flash back to 4.4.4 from 5.0.2?
Getting this when trying to flash gpt.bin: http://i.imgur.com/zkes3kJ.png
edit: I tried only removing the gpt.bin and getvar line and leaving the motoboot line in. Seems to be flashing and working.
I had a strange bug that the battery was stuck at 1% when I removed the motoboot command.
edit2: still having the 1% battery problem. Can't do anything
edit3: Trying a bold strategy... I replaced the gpt.bin file with the 5.0.2 version of it and flashed the rest of the 4.4.4 files. We'll see what that does. I'm perfectly fine with bricking my phone.
edit4: still getting 1% battery issue. Going to try making it die then fully charging.. Hopefully that will fix it..
Edit5: worked! Killing the battery made it figure out the %and now I'm back on soak test ghost .38. The OTA seemed to work fine both times it updated to 5.0.2 then to the updated soak test.
ken1645 said:
I tried flashing with the gpt.bin and motoboot still in the XML file but get a "downgrade security detected" and it stops due to trying to downgrade. Is there a better way to flash back to 4.4.4 from 5.0.2?
Getting this when trying to flash gpt.bin: http://i.imgur.com/zkes3kJ.png
edit: I tried only removing the gpt.bin and getvar line and leaving the motoboot line in. Seems to be flashing and working.
I had a strange bug that the battery was stuck at 1% when I removed the motoboot command.
edit2: still having the 1% battery problem. Can't do anything
edit3: Trying a bold strategy... I replaced the gpt.bin file with the 5.0.2 version of it and flashed the rest of the 4.4.4 files. We'll see what that does. I'm perfectly fine with bricking my phone.
edit4: still getting 1% battery issue. Going to try making it die then fully charging.. Hopefully that will fix it..
Click to expand...
Click to collapse
In this case, if you take an OTA, you'll most likely brick. But if you're fine with it,no problem. Although I don't advise you to do that.
Sent from my Moto X using XDA Free mobile app
if I have the soak test 5.0.2 retail US, I can do downgrade directly to retail brazil 4.4.4?
you can downgrade by skipping gpt and motoboot, but DONT EVER take OTA, you will need to wait for full lolipop sbf to update manually.
shavo21 said:
if I have the soak test 5.0.2 retail US, I can do downgrade directly to retail brazil 4.4.4?
Click to expand...
Click to collapse
So what would happen if u followed this guide but made a TWRP backup of 5.0.2 and then tried to restore to 5.0.2 through TWRP?
I tried the searches, i tried the restore to stock, i tried windroid, i tried everything.
i have a moto x pure with originally 6.0.1 but it was with a unlocked bootloader. now i want to restore it back. i tried everything i could find to relock it and now i am trying the system images from motorola but i keep getting this ******* response
tail_XT1575_MPH24.49-18_18\CLARK_RETUS_MPH24.49-18_18_retus_US>fastboot flash
rtition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.003s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.354s
can someone please help me. the bat all files are not working and now manually isnt working either. step by step instructions would be appriciated. ive been trying at this for 5 hours now
You cannot lock the bootloader again. Once it's unlocked it's a done deal. Warranty wise
Sent from my XT1575 using Tapatalk
You can relock... But there is no reason to. If it is not locking you are not 100% stock. I think there was discussion on this in the firmware thread.
Problem with 'gpt.bin' not flashing is you are trying to downgrade, regardless of an unlocked bootloader or not, you cannot downgrade the partition table (gpt.bin is the partition table). If you want to relock you need to factory default in recovery, flash the stock ROM that is the same or newer version than you have installed (you cannot downgrade), and you must use the 'fastboot oem lock begin" commands to start and 'fastboot oem lock' to end the flashing sequence.
Although this process works, it isn't really relavent and means nothing because Moto will always know it was unlocked (the generation of the unlock token voided your warranty, whether unlocked or not), your bootloader status will never return to 0 and your software status will always show modified.
Be aware that we have seen a few Moto G 2015 devices get bricked by this, if somehow the bootloader version doesn't match the ROM (can happen... we have seen it more than once) due to flashing multiple stock images or failed/improper OTA flash, and the bootloader gets locked it becomes insta-brick and won't go past the bootloader and won't unlock again. It seems the only way out is to flash a newer official stock image if/when one becomes available.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my 0PJA2 using Tapatalk
So you either haven't flashed anything, or you returned to stock and took an OTA and it went official again (lucky you, it's inconsistent).
Bootloader status can never be returned to 0.
Sent from my Motorola XT1575 using XDA Labs
Jessooca said:
I have the latest July update (minor sec update) my phone is stock and I have the latest firmware, spoke to Tom (rootjunky) and he was stumped as well. I have the same issue and I'm not downgrading anything, nor flashing an older firmware, yet still have your same issue. Unlocked the bootloader and that didn't help either.
Probably have rootjunky remotely look at my XT1575 and see if he can figure it out..... I will let you know the issue when we know.
Curious.... Does your phone always startup and go into that bootloader/fastboot screen??
Click to expand...
Click to collapse
It did for a bit not but anymore. It was doing bootloops but when I put back twrp and reflashed a ROM on XDA it stopped doing it
Sent from my 0PJA2 using Tapatalk
ok an update.
so i downloaded from here http://www.gammerson.com/2015/09/restore-stock-firmware-rom-in-moto-x-style-pure-2015.html which is the same as a link from XDA and already had the download.
so i flashed it three times to assure it was flash entirely.
1) first time it just flashed the software
2)second time the radios started to work
3) third time was just to make sure it worked properly
it started to change the bootloader date and returned the unlocked bootloader message. after i did that, everything worked the way it was supposed to minus the bootloader lock.
it gave me a notification that there is an update available for marshmallow, downloaded and flashed automatically so i think im in good hands so far. i guess everything is ok now and after nougat, ill just root it back again.
Jonathanlc2005 said:
ok an update.
so i downloaded from here http://www.gammerson.com/2015/09/restore-stock-firmware-rom-in-moto-x-style-pure-2015.html which is the same as a link from XDA and already had the download.
so i flashed it three times to assure it was flash entirely.
1) first time it just flashed the software
2)second time the radios started to work
3) third time was just to make sure it worked properly
it started to change the bootloader date and returned the unlocked bootloader message. after i did that, everything worked the way it was supposed to minus the bootloader lock.
it gave me a notification that there is an update available for marshmallow, downloaded and flashed automatically so i think im in good hands so far. i guess everything is ok now and after nougat, ill just root it back again.
Click to expand...
Click to collapse
Try windroid tool kit it works except for root but it does have a bootloader relock to it.
Hello hello,
First time poster as I don't know crap to help folks since I'm just learning *ahem*, and I've come across an issue that has me completely stumped with a recently purchased refurbished Moto G4...
([Edit/Update]: So apparently new users can't embed links, and so it appears that my Imgur photos are also not posting...?)
TLDR: OTA to Nougat refuses to install on XT1625...because Consumer Celluar?
So here's the long version... Bought a refurbished Moto G4 XT1625 (not amazon) with the intention of using it as a learning aid for unlocking, rooting, etc.
Unlocked the bootloader, flashed TWRP, backed up, rooted via Magisk, backed up. After a couple days, up pops the OTA notification. "Yay" I thought. Then "Oh wait, I heard root + OTA can be difficult". So I read. A lot.
Fast forward and of course the OTA failed when I just accepted it. However, I captured the file, pulled up the stock ROM download from the official Moto website after checking that the build numbers matched, and proceeded to unroot and reflash that stock ROM (except for bootloader and gpt files). I booted back up, got the notification again, and hit OK. Fail. So I booted into recovery and tried to sideload OTA (using "Blur_Version.24.31.65.athene.retail.en.US.zip" pulled from "com.motorola.ccc.ota-20171028-062630.tar.gz"). Fail.
Maybe somehow I misread the multiple how-tos out there, and I'm screwing something up in the process here?
After numerous rinse and repeats of the above steps, I cannot for the life of me get past this damn error which (assuming my inexperienced eyes are reading it properly) seems to say that the current CCMyConsumer.apk on my phone is somehow wrong (corrupted/incorrect/missing?), and so the OTA's response to me is a big FU.
Verifying current system...
E3005: "/oem/app/CCMyConsumer/CCMyConsumer.apk" has unexpected contents.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This seems.......weird to me? If I have both the stock ROM and am using the actual OTA, why would a random provider's app be screwed up, much less screwing up the update.
Also, if it matters at all, here's that particular directory tree in a file manager...an apk file doesn't appear to even be there?
Could a lack of existence be the "unexpected contents?"
So, the question as in the TLDR, any ideas on what the cause or solution to this error or overall OTA issue could be? I'm at a loss.
The only other item I noticed is that my "Settings" now crashes if I attempt to navigate into "Apps" within its menu. However, if I navigate directly into an App's info page via the app drawer, I can access those. Not saying this is related, I have no idea, but being the only other oddity, and since it persists through flashes, I figured I'd mention it (even if unrelated, I am still curious what could be going on there too...).
Thanks in advance for any help, education, or peace of mind. =P
NobodyByChoice said:
Hello hello,
First time poster as I don't know crap to help folks since I'm just learning *ahem*, and I've come across an issue that has me completely stumped with a recently purchased refurbished Moto G4...
([Edit/Update]: So apparently new users can't embed links, and so it appears that my Imgur photos are also not posting...?)
Unlocked the bootloader, flashed TWRP, backed up, rooted via Magisk, backed up. After a couple days, up pops the OTA notification. "Yay" I thought. Then "Oh wait, I heard root + OTA can be difficult". So I read. A lot.
Fast forward and of course the OTA failed when I just accepted it.
Click to expand...
Click to collapse
Do you still have TWRP installed? You cannot flash an OTA update with TWRP installed. You'll have to find and flash the original Nougat ROM which will remove TWRP. Then accept the OTA update and let it install. Then, if you need TWRP, flash it again. I know because I was in the same boat when I accidentally accepted the OTA update with the Sept security patch and it screwed up my phone (XT1625) royally. Check out this thread which describes my process.
https://forum.xda-developers.com/mo...boots-twrp-t3701768/post74463378#post74463378
Link to XT1625 firmware: https://androidfilehost.com/?fid=673368273298984458
lmacmil said:
Do you still have TWRP installed? You cannot flash an OTA update with TWRP installed. You'll have to find and flash the original Nougat ROM which will remove TWRP. Then accept the OTA update and let it install. Then, if you need TWRP, flash it again. I know because I was in the same boat when I accidentally accepted the OTA update with the Sept security patch and it screwed up my phone (XT1625) royally. Check out this thread which describes my process.
https://forum.xda-developers.com/mo...boots-twrp-t3701768/post74463378#post74463378
Link to XT1625 firmware: https://androidfilehost.com/?fid=673368273298984458
Click to expand...
Click to collapse
Thanks for the advice, sorry for the late reply as I was out of the country. I do understand the need to get rid of TWRP first, but I'll read through your recommended threads and see what happens!