Is it safe to update to the newest ota i had unlocked my phone and ran the early copy of of 2.3 but didn't like it so i flashed back to 1.83. My phone no longer shows its unlocked sence i flashed the 1.83 back on it will it brick if i try to run the offical ota ?
Related
Just curious if the 1.83 OTA update enacts the journaling where it won't allow you to flash back to 1.26 or 1.57. Has it been confirmed whether 1.83 OTA allows or restricts reverting to previous firmwares?
cerps said:
Just curious if the 1.83 OTA update enacts the journaling where it won't allow you to flash back to 1.26 or 1.57. Has it been confirmed whether 1.83 OTA allows or restricts reverting to previous firmwares?
Click to expand...
Click to collapse
I have successfully gone from 1.83 SBF ginger 3.0 gingerbroke, back to 1.2.6 then OTA to 1.57 and OTA 1.83, I have done this 3 times already with no consequences or issues. Currently on 1.83, Gingerbreak, Tether etc. All is well. I have used both the RSD method using provided links before official release of 1.83, as well as the current OTA. I just can stop playing with this phone lol.
This is exactly what I was wondering. I remember reading, pre-1.83 release that you would not be able to flash back to stock once the 1.83 update had been applied due to the firmware journaling that the 1.83 put in place. I've been reluctant to upgrade to 1.83 for that very reason. Are there others out there who have successfully 1.26 sbf flashed a 1.83 version phone?
jimbush3 said:
This is exactly what I was wondering. I remember reading, pre-1.83 release that you would not be able to flash back to stock once the 1.83 update had been applied due to the firmware journaling that the 1.83 put in place. I've been reluctant to upgrade to 1.83 for that very reason. Are there others out there who have successfully 1.26 sbf flashed a 1.83 version phone?
Click to expand...
Click to collapse
Im not sure If anyone has had any issues, but i scour this forum daily while at work lol, and im pretty sure if it was an issue it would be on the top of every Atrix thread. I have flashed back to 1.26 from 1.83 3 times. I wanted to see if the official OTA ran any different from the SBF that went live on the 29th because i couldn't find an answer so i took the risk and tried it. First try worked perfectly. I then went back to SBF 1.83 to test again to see if anything was different. Far as i could tell the OTA official release seems to scroll menus better and just seems to be a little more fluid. I STRESS!!! I DO NOT have technical data to back this up, Just my opinion. I dont want start a snowball effect of people flashing there device back to stock thinking OTA 1.83 is better lol.
jimbush3 said:
This is exactly what I was wondering. I remember reading, pre-1.83 release that you would not be able to flash back to stock once the 1.83 update had been applied due to the firmware journaling that the 1.83 put in place. I've been reluctant to upgrade to 1.83 for that very reason. Are there others out there who have successfully 1.26 sbf flashed a 1.83 version phone?
Click to expand...
Click to collapse
I flashed back to 1.26 from 1.83 successfully last night. I then OTA'd my way back to 1.83. (One thing, however, after my phone installed the 1.57 OTA, it wouldn't boot back up. It just said failed to boot and went to RSD mode. I then flashed the 1.57 sbf and that went well. I then OTA'd to 1.83 and all is well)
sent from my Atrix
Hello Atrix users! I recently just received this phone about a week ago and have rooted, unlocked the bootloader and also flashed the cwm. Now, whenever I try to update via OTA or sd card I get an error stating that the update has failed. I'm very new to Android phones and I was wondering what the procedure for updating would be? BTW I'm on 1.8.3
Thanks a lot
first of all i dont think your suppose to rsd or ota after you have unlocked the BL you have to flash GB through moto-fastboot or fastboot when u have GB on your external SD and run the commands through a command window, GOOGLE IS YOUR FRIEND and so is XDA just a do a search and you should find wat your looking for,
wat i have done is i was already on 1.8.3 and unlocked the BL, but i forgot to root the phone, and i couldnt root idk why, so i had to use the aroot method(do quick search on it) which had me rsd back to 1.2.6 then reboot, after that the words UNLOCKED where gone, so i think rsd back to 1.2.6 either took the unlock away or just got rid of the words and BL was still unlocked idk, but any way did a wi-fi ota update to 1.5.7 than ran afterupdate.bat and it retained the root, then just ran the unlock again with rsd rebooted and the words unlocked were back, but im not on 1.8.3, idk if i should try to ota to it, or rsd back to the beginning which is 1.2.6 and just ota all the way to the offical newest update of gingerbread then unlock the bl again and do the preinstall root method, thats where im stuck at,
That seems like a ton of work just for the OTA. I unlocked my boot loader and flash the cherry blur rom (v.1.4) this was the easiest way I have found to get 2.3.3 on my phone and without blur over taking the interface.
Sent from my MB860 using XDA Premium App
from wat i have read you should be good with wat ever u do with rsd or flashing back to a stock rom AS LONG AS YOU HAVENT UPDATED TO THE NEWEST OTA UPDATE SENT TO YOU OTA BUT IF YOU HAVE ACCEPTED THE OTA UPDATE YOU WILL HARD BRICK YOUR PHONE IF U TRY FLASHING BACK TO A STOCK LIKE 1.2.6 i think that is how it goes from wat i have read
I rooted and flashed GladiAtrix and VividLime theme. How.exactly can I go about flashing my phone to the GB OTA update? I do not want to unlock and end up getting a hardbrick.
Sent from my Vivid Lime GladiAtrix of doooooooooom.
Unlock or do it ota. Only choices.
I voided my warranty.
FluffyCow said:
I rooted and flashed GladiAtrix and VividLime theme. How.exactly can I go about flashing my phone to the GB OTA update? I do not want to unlock and end up getting a hardbrick.
Sent from my Vivid Lime GladiAtrix of doooooooooom.
Click to expand...
Click to collapse
The retail OTA .SBF can be obtained here---> http://www.filesonic.com/file/1507329091/1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
You will only get a hardbrick if you try to flash back to an older build using RSD after you have used the OTA 2.3.4. sbf
Not a big deal, im on the OTA with unlocked bootloader and I have flashed every rom that has come out. Once you RSD to 2.3.4 you might as well delete RSD. No reason you should need it. I recommend unlocking your bootloader before you take the leap to the OTA. Its way easier before the OTA update. If your already on the OTA 2.3.4 you can still use RSD to unlock your bootloader but thats it. It will give you a softbrick but its easily recovered.
(SOLVED)
Im in stock 4.1.2 whit S-OFF, unlocked bootloader (1.55) and then RELOCKED.
¿Can i take the last OTA?
Im not rooted, and i dont have custom recoverys (i recently flashed a RUU.zip to return to stock, but i could not remove the S-OFF and RELOCKED status because the hboot 1.55).
I have economic (health) problems and I'll really need to sell my phone, but I'm afraid that the new owner will come out error when trying to update.
conquesoextra said:
Im in stock 4.1.2 whit S-OFF, unlocked bootloader (1.55) and then RELOCKED.
¿Can i take the last OTA?
Im not rooted, and i dont have custom recoverys (i recently flashed a RUU.zip to return to stock, but i could not remove the S-OFF and RELOCKED status because the hboot 1.55).
I have economic (health) problems and I'll really need to sell my phone, but I'm afraid that the new owner will come out error when trying to update.
Click to expand...
Click to collapse
Yes. You can get OTAs while S-OFF. And assuming you haven't unlocked the bootloader since flashing the RUU, all the system files it verifies should be in place to accept OTAs. However, considering you are currently on 4.1.2, you'll need to run through a progression of OTAs to get up to the latest version, 4.4.2 w/ Sense 6. Might be better to just run the latest RUU to bring it up to 4.4.2 w/ Sense 5.5 then OTA to Sense 6. Be aware that you'll need to be on the AT&T network in order to get the updates OTA. If you're not on AT&T, you'll need to flash the updates manually, in which case you'll need to be S_OFF.
Also, once the phone is S-OFF there is no good reason to change that back to S-ON. There's the potential of bricking the phone by doing so. And even if it doesn't brick, the updates in firmware may make it more difficult to obtain S-OFF again.
Thank you very much.
At the begining i did this:
1- Unlocked bootloader and flashed TWRP.
2- Root
3- Gained S-Off
When i decide to sell it i did this:
1- Removed xposed and root.
2 - Relocked bootloader.
3 - Flashed RUU.zip (4.1.2)
¿What do you mean whit AT&T network? I unlocked the phone vía imei (using it in mexico whit Telcel) and still have the update appearing.
Sorry for my terrible english
conquesoextra said:
Thank you very much.
At the begining i did this:
1- Unlocked bootloader and flashed TWRP.
2- Root
3- Gained S-Off
When i decide to sell it i did this:
1- Removed xposed and root.
2 - Relocked bootloader.
3 - Flashed RUU.zip (4.1.2)
¿What do you mean whit AT&T network? I unlocked the phone vía imei (using it in mexico whit Telcel) and still have the update appearing.
Sorry for my terrible english
Click to expand...
Click to collapse
First off, since you are S-OFF there is no need to relock the bootloader in order to flash an RUU. It will run just fine with an unlocked bootloader. Also when you flash an RUU, all the partitions get wiped so there is no need to do anything within the ROM such as remove xposed & root prior to flashing. The RUU will set the device essentially in a factory state.
As far as I understand it, the OTAs for carrier specific devices are served up by the carrier. So if the phone has been SIM unlocked and is being used on another network, if you go into Settings>AT&T software update, it will not receive any available OTA update. You will need to flash the update file manually using the information in this thread, http://forum.xda-developers.com/showthread.php?t=2659374.
Since you are still on 4.1.2, you will need to run one of the recent RUUs in order to manually flash the OTA updates in that thread. The latest RUU available for AT&T devices is KK4.4.2 w/Sense 5.5.
http://androidruu.com/getdownload.p...09_10.26.1718.01L_release_356565_signed_2.exe
Flash that then you can manually flash the OTA update to get Sense 6.
You are the man.
THANK YOU SO MUCH!
My phone is currently Rooted with TWRP installed, and im running gpe 4.4.4 stock rooted rom from the android development forums. Now, considering im s-on and have no computer at home at the moment, I was trying to figure out a way to update my firmware so that i can test out and flash one of these new lollipop roms. If I flash using twrp an at&t stock rom such as "Stock AT&T 1.58 Deodexed" from the AT&T forum,
1. Will I receive an OTA from at&T
2. Is it safe to accept the OTA
3. Will it update the firmware properly, so that i may flash a lollipop firmware.
My guess is that the answer to #2 will probably be a no. My phone is originally an at&t device btw.
Thanks for any help.
Most OTA's will fail simply cause you have a custom recovery.
If you can afford $25 just gain S-OFF using "Sunshine"
You need to be on stock ROM and stock recovery to install an OTA. Root is okay, and bootloader unlocked is okay ("okay" meaning the OTA will install, but you will lose root).
The stock ROM is normally odexed, so I don't think the deodexed will qualify as "stock" enough to allow the OTA to install (I'm thinking NO). The fastest way to return to stock ROM and recovery is probably by RUU (relock bootloader required for RUU).
Not sure what you mean by "safe" but as long as you meet the above conditions you will be able to receive and install OTAs. You will lose root as mentioned (but can easily just re-install custom recovery and root again). And your data should remain intact; although you should always backup important personal data, anyway.
But be aware there is currently no AT&T OTA that will update you to the current (3.x) firmware required for LP custom ROMs. The OTA for 4.4.4 is rumored for Dec. 29, but its already been delayed twice.
If you don't want to s-off, you will have to wait until 4.4.4 rolls out (to update the firmware). Or just s-off by sunshine and be done with it.