I know there have been varying posts on the subject, but I thought I would share my experience with the update. I originally started out on a bootloader unlocked, rooted, At&t branded Atrix. I had installed the 2.3.4/4.5.91 fruitcake previously and had been using it for some time. When the update came down I rolled back to stock recovery using fastboot and after the installation of the update, the phone gave me an failed to boot 4. I used rsd to flash the official 2.3.4/4.5.91. I received a failed to boot 1. (After going to launder my, now soiled, trousers) I noticed that when I plugged the phone in, RSD still recognized the phone, even though it did not show the "entering RSD mode" tag. It occured to me to attempt to flash pudding using the 4.2 auto unlock. Immediately after flashing pudding the phone booted up and everything was working fine.
At this point I rooted and installed clockwork on the phone using the same 4.2 tool. I then used Voodoo OTA Rootkeeper to back up my root. Unfortunately the tool installs clockwork in order to root the phone, so I had to flash back to stock recovery using fastboot. . I then booted, downloaded, and then installed the update.
After the update the phone rebooted, and gave me "failed to boot 2, starting RSD mode". At which point I installed pudding again using the tool. Rebooted after having installed pudding, the phone booted beautifully. I used OTA Rootkeeper to restore my root after the boot. Everything is working fine and it is on current version 4.5.141. I hope this helps someone else, or maybe someone to find a more simple, straight-forward way of doing this.
Doogiedoo said:
I know there have been varying posts on the subject, but I thought I would share my experience with the update. I originally started out on a bootloader unlocked, rooted, At&t branded Atrix. I had installed the 2.3.4/4.5.91 fruitcake previously and had been using it for some time. When the update came down I rolled back to stock recovery using fastboot and after the installation of the update, the phone gave me an failed to boot 4. I used rsd to flash the official 2.3.4/4.5.91. I received a failed to boot 1. (After going to launder my, now soiled, trousers) I noticed that when I plugged the phone in, RSD still recognized the phone, even though it did not show the "entering RSD mode" tag. It occured to me to attempt to flash pudding using the 4.2 auto unlock. Immediately after flashing pudding the phone booted up and everything was working fine.
At this point I rooted and installed clockwork on the phone using the same 4.2 tool. I then used Voodoo OTA Rootkeeper to back up my root. Unfortunately the tool installs clockwork in order to root the phone, so I had to flash back to stock recovery using fastboot. . I then booted, downloaded, and then installed the update.
After the update the phone rebooted, and gave me "failed to boot 2, starting RSD mode". At which point I installed pudding again using the tool. Rebooted after having installed pudding, the phone booted beautifully. I used OTA Rootkeeper to restore my root after the boot. Everything is working fine and it is on current version 4.5.141. I hope this helps someone else, or maybe someone to find a more simple, straight-forward way of doing this.
Click to expand...
Click to collapse
Thanks for the info. Do you mind if I re-post in this thread over in the dev forum? I noticed your post count is too low to post over there.
I just got my phone back from Motorola after they fixed a shattered screen. I had sent it in with an unlocked BL, running a CM7 kang. They sent it back running stock .141.
Since I didn't do the update, I had no idea how to proceed re-unlocking it. But it sounds like between you and Nottach, I should be ok with the pudding unlocker(knock on wood).
how did you get rid of superuser on fruitcake?
ghost_og said:
Thanks for the info. Do you mind if I re-post in this thread over in the dev forum? I noticed your post count is too low to post over there.
I just got my phone back from Motorola after they fixed a shattered screen. I had sent it in with an unlocked BL, running a CM7 kang. They sent it back running stock .141.
Since I didn't do the update, I had no idea how to proceed re-unlocking it. But it sounds like between you and Nottach, I should be ok with the pudding unlocker(knock on wood).
Click to expand...
Click to collapse
Not at all, if it's any use to anyone, feel free to repost it. Also, I had a hardware problem (screen banding) on my atrix and sent it back for repairs. When it was returned, it no longer showed unlocked. The bootloader was still unlocked, but I had to reapply the unlock sbf to get it to show again (before using another rom).
ummkiper said:
how did you get rid of superuser on fruitcake?
Click to expand...
Click to collapse
I still had it installed on fruitcake, but lost it (well, rather lost root access, as the app "superuser" is still there but not functional) when I installed the sbf file initially. I'm not sure if flashing pudding or using the automatic unlock on the fruitcake initially would have worked. I didn't think to try it initially.
Cool,thanks for the info.
Sent from my Nexus One using xda premium
Related
So I have Unrevoked3, and want to update OTA, I don't need root anymore.
However, when I update it goes to start the update, then I get a yellow triangle with an exclamation point and an android, it just sits there til I pull the battery.
I want to be sure this is just an issue with needing to unroot, and not something else.
If its just an unrooting issue, how do I unroot from Unrevoked3? All the unrooting topics I've found were for toast or simpleroot.
Sent from my PC36100 using XDA App
Btw, the RA is Clockwork recovery.
Sent from my PC36100 using XDA App
Pretty sure all you need to do is put the update on your SD card, flash it, and then you're done. You'll lose root, but it should work that way. YMMV and all that.
I'll try it when I get home, hopefully it'll work.
Sent from my EVO using the Xda App
any word? I too am having the yellow triangle displayed on my screen when trying to install the OTA after doing Unrevoked 3
Nevermind, Im downloading now.
Im also downloading the 1.47 RUU incase I need to start from scratch, which Ive heard works with revoke.. Im just not sure how to reflash the stock recovery image and get rid of Clockwork Mod and Unrevoked.
I ran flash sdcard:update.zip and so far its updating with no issues, will wait for boot up to see if it took.
I think using the ruu is the only way to reset the recovery, anyway thats what I did and d/ling the OTA now.
Worked fine. Booted up took a bit, but Im used to that with all updates, Im now running Android 2.2
As a side, is the FroYo update supposed to wipe apps/settings? Mine werent.
well mine seemed to work, I didn't care about reseting so my process went like this..
completely stock+unrevoked3 root+clockworkmod
RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459.exe
OTA d/l and installed over 1.47
ota installed successfully
factory defaulted with 2.2 in place
Im running 2.2, but none of my settings were reset and all my apps are still there.
Does running this : RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_rele ase_CL195459.exe erase all of the phone's previous memory?
freditoj said:
Does running this : RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_rele ase_CL195459.exe erase all of the phone's previous memory?
Click to expand...
Click to collapse
Yes.
It does not erase your sd card tho.
So unrevoked 3 users can't use the Froyo OTA update?
I need to sell my atrix, so I wiped using the CWM, now it doesn't show the SU anymore. does this mean i'm not rooted anymore? When I go to settings it says OLYFR_U4_1.5.7. If I'm not rooted anymore, do I just start with the Gladroot process? Or do i have to start all over again? the phone's going to be picked up tomorrow and I said it's rooted =s
Run an app that "requires root" like Titanium Backup. That will tell you if your phone is rooted or not...
Sent from my MB860 using XDA App
nope, it doesn't sideload anymore. i used to do this with my captivate. wipe with CWM and then i'd still be rooted. do i have to flash back to 1.2.6 and start the process all over again?
tepickytoo said:
nope, it doesn't sideload anymore. i used to do this with my captivate. wipe with CWM and then i'd still be rooted. do i have to flash back to 1.2.6 and start the process all over again?
Click to expand...
Click to collapse
Just to let you know, I don't have the AT&T version. (I have the Bell)
With that said, I've been following the Gladroot thread for both phones. Currently I'm rooted with Bell using Gladroot.
My suggestion is to "carefully" follow the checklist in the Gladroot thread to get root again:
http://forum.xda-developers.com/showthread.php?t=1016060
Especially when it says --> "If you are already on 1.57 and do not have root, you MUST flash back to 1.26 for this to work. NO EXCEPTIONS."
^ So with that said it looks like you need to get back to 1.26 before gaining root again.
Most importantly, be slow and take your time. I've soft bricked a phone in the past when I was in a rush and skipped a step.
Best of luck!...
wiping is known to remove root for 4.1.57, so you will need to so the whole process again going back to 4.1.26.
Ahhhh. I see. I've started the process, i'm on the gladroot atm. Thanks for all the help guys!
I'm concerned about rooting or modifying my Atrix a second time. My first Atrix that I had rooted stopped working when I tried to update the OS through the wi-fi download of the update. Mid-way through, the Android mascot and the exclamation sign came up and I had to pull the battery. When I rebooted the phone it said the modem failed to start up. I don't know the reason for it but I went to the store and used my insurance to get a fresh one. Since then, I have only sideloaded apps and now with the Gingerbread update I don't have to use a USB cord to install apps anymore. I'm afraid to try to root or modify my Atrix again.
Bagel Bear said:
I'm concerned about rooting or modifying my Atrix a second time. My first Atrix that I had rooted stopped working when I tried to update the OS through the wi-fi download of the update. Mid-way through, the Android mascot and the exclamation sign came up and I had to pull the battery. When I rebooted the phone it said the modem failed to start up. I don't know the reason for it but I went to the store and used my insurance to get a fresh one. Since then, I have only sideloaded apps and now with the Gingerbread update I don't have to use a USB cord to install apps anymore. I'm afraid to try to root or modify my Atrix again.
Click to expand...
Click to collapse
Rooting should not have given you that problem. I've rooted numerous A4g's on froyo and they are all running GB fine after the ota. I also re-rooted them all now that they have GB. No issues. Also if your atrix didn't give you a boot error right when you turned it on you could have manually flashed a build and wouldn't have had to use you insurance.
Sent from my MB860 using XDA App
Alright, that eases my mind. Perhaps I just had some hardware failure.
How does rooting affect everything? Like you said, you are able to update via OTA when rooted and everything is fine. I also have a question about how to root exactly. I saw the sticky but it only mentioned the leaked release of Gingerblur and not the OTA version. Does the information still apply?
Its a little more involved if don't have your bootloader unlocked. Follow the post mramirezusa has about automatic unlocked bootloader and root.
Sent from my MB860 using XDA App
Be sure to read the instructions twice, then read it again for good measure!
Also check out the [HOWTO] Root after sbf flash thread in the dev section
Sent from my MB860 using XDA App
I had a new phone on 2.3.4. The first thing I tried to do was to unlock it by RSD flashing the unlock sbf from the main pudding thread (http://forum.xda-developers.com/showthread.php?t=1136261).
The initial process seemed to go okay, but I think when the phone was supposed to reboot, it ended up giving me a boot failure message (0x1000, if I remember correctly).
So, I tried the "fastboot oem unlock" command anyway, and it worked.
I tried to RSD flash the full 2.3.4 sbf from brandon15811's thread, but RSD gave an error, something about not being able to find the handle or something.
So, the next thing I did was to see if I could flash RomRacer's CWM via fastboot, and that seemed to work, too.
After that, if I tried to reboot, I would get the motorola startup screen and the word "unlocked", but it just seems to stay there.
I'm about to see if I can use the recovery to flash the full 2.3.4 sbf from here (http://forum.xda-developers.com/showthread.php?t=1138204).
Is that the right way to try to fix this, or is there something else I should try?
Haphim said:
I had a new phone on 2.3.4. The first thing I tried to do was to unlock it by RSD flashing the unlock sbf from the main pudding thread (http://forum.xda-developers.com/showthread.php?t=1136261).
The initial process seemed to go okay, but I think when the phone was supposed to reboot, it ended up giving me a boot failure message (0x1000, if I remember correctly).
So, I tried the "fastboot oem unlock" command anyway, and it worked.
I tried to RSD flash the full 2.3.4 sbf from brandon15811's thread, but RSD gave an error, something about not being able to find the handle or something.
So, the next thing I did was to see if I could flash RomRacer's CWM via fastboot, and that seemed to work, too.
After that, if I tried to reboot, I would get the motorola startup screen and the word "unlocked", but it just seems to stay there.
I'm about to see if I can use the recovery to flash the full 2.3.4 sbf from here (http://forum.xda-developers.com/showthread.php?t=1138204).
Is that the right way to try to fix this, or is there something else I should try?
Click to expand...
Click to collapse
If you have cwm just use samcripp's fruitcakes and see if that works.
Sent from my MB860 using XDA Premium App
msd24200 said:
If you have cwm just use samcripp's fruitcakes and see if that works.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
I haven't confirmed it works yet, but if it does, why those builds instead of brandon15811's?
Haphim said:
I haven't confirmed it works yet, but if it does, why those builds instead of brandon15811's?
Click to expand...
Click to collapse
Sbf flashing is dangerous and not recommended
Sent from my MB860 using XDA Premium App
Unlocking an atrix already on 2.3.4 will give you a soft brick, its been confirmed many times. No way around it. Find the fruit cakes thread as msd24200 stated. Any recovery will work. If you do the full 2.3.4 sbf you can't rds back to an older build our even if you try the 2.3.4, that would give you a hard brick. If your unlocked just go for one of the great roms available.
Sent from my MB860 using XDA App
Dirtburgler said:
Unlocking an atrix already on 2.3.4 will give you a soft brick, its been confirmed many times. No way around it. Find the fruit cakes thread as msd24200 stated. Any recovery will work. If you do the full 2.3.4 sbf you can't rds back to an older build our even if you try the 2.3.4, that would give you a hard brick. If your unlocked just go for one of the great roms available.
Click to expand...
Click to collapse
I did a lot of reading before doing this, and somehow, I never came across that particular fact. Ai! Well, thank you for pointing that out!
So, here's a question then... I have another phone that has 1.83 on it. What's the best way to upgrade that to 2.3.4, unlocked and rooted? Should I follow the same path I did here, do the OTA update, unlock and brick via the unlock sbf, flash a recovery, then apply a fruitcake?
Or is there a better way? I've heard that the 2.3.4 update resizes the partitions, and that seems like a good thing, so I'm not sure I want a path that avoids that.
What do you think?
Haphim said:
I did a lot of reading before doing this, and somehow, I never came across that particular fact. Ai! Well, thank you for pointing that out!
So, here's a question then... I have another phone that has 1.83 on it. What's the best way to upgrade that to 2.3.4, unlocked and rooted? Should I follow the same path I did here, do the OTA update, unlock and brick via the unlock sbf, flash a recovery, then apply a fruitcake?
Or is there a better way? I've heard that the 2.3.4 update resizes the partitions, and that seems like a good thing, so I'm not sure I want a path that avoids that.
What do you think?
Click to expand...
Click to collapse
why bother to update if you're going to downgrade it again?
the unlocker SBF if 1.8.3, and the phone is on 1.8.3, so flash that. then install 2.3.4 via CWM with a fruitcake. done.
dLo GSR said:
why bother to update if you're going to downgrade it again?
the unlocker SBF if 1.8.3, and the phone is on 1.8.3, so flash that. then install 2.3.4 via CWM with a fruitcake. done.
Click to expand...
Click to collapse
Unce I've unlocked the phone on 1.8.3, would it be better to do the OTA update for 2.3.4, and then root? Is this even possible?
One important question, if I apply the CWM fruitcake over 1.83. will it resize the partitions the way the OTA update would?
Haphim said:
Unce I've unlocked the phone on 1.8.3, would it be better to do the OTA update for 2.3.4, and then root? Is this even possible?
One important question, if I apply the CWM fruitcake over 1.83. will it resize the partitions the way the OTA update would?
Click to expand...
Click to collapse
I don't believe so, someone correct me if I'm wrong, but in all honesty there is no reason to use fruitcakes if you don't plan on going back to an older build. Even if you mess something up flashing roms you can go into recovery and restore a backup and your good to go. The only way I've seen a hardbrick is from going back with rsd.
I would unlock then ota to 2.3.4 then install romracers cwm and then your free to flash pre rooted stock roms or cherry (3.14) or alien rom.
Sent from my MB860 using XDA App
Nevermind 10char
I could see flashing back to an older build beneficial to a developer but not your everyday user and rom flasher. Both methods will get you to the same place, fruitcake or ota. I know there are benefita doing the ota like partition size and some other tweaks but I'm not 100% what those benefits are.
I jumped in early and got the leaked ota before we knew of the hard brick issue and like I said I'm still rocking the same atrix I bought back in march.
Sent from my MB860 using XDA App
Dirtburgler said:
I don't believe so, someone correct me if I'm wrong, but in all honesty there is no reason to use fruitcakes if you don't plan on going back to an older build. Even if you mess something up flashing roms you can go into recovery and restore a backup and your good to go. The only way I've seen a hardbrick is from going back with rsd.
I would unlock then ota to 2.3.4 then install romracers cwm and then your free to flash pre rooted stock roms or cherry (3.14) or alien rom.
Click to expand...
Click to collapse
Thanks! If that's an okay route to take, then that's what I'll do.
I have a droid x that is rooted and has the hack so I can wirelessly tether. I used the voodoo ota root keeper to try and keep my root. When I try to install the update it fails. I also have clockworkmod recovery installed. Any suggestions?
rkshack
Rkshack said:
I have a droid x that is rooted and has the hack so I can wirelessly tether. I used the voodoo ota root keeper to try and keep my root. When I try to install the update it fails. I also have clockworkmod recovery installed. Any suggestions?
rkshack
Click to expand...
Click to collapse
If you do take it there is quite a hassle getting it back to be rootable but if you must? You will need the latest version of rsdlite the desired sbf .602 or .605 which will revert it back to stock then you can take the OTA. My guess is somewhere along the way you froze or uninstalled some of the preinstalled bloatware? Which can cause the update to fail this was my case at least I sbfed to. 602 then took 2 OTA'S to .621 unfortunatley I regreted it you may want to look around at method to freeze updater instead your rooted try a different rom or 2 before making the decision
rom question
Thepooch said:
If you do take it there is quite a hassle getting it back to be rootable but if you must? You will need the latest version of rsdlite the desired sbf .602 or .605 which will revert it back to stock then you can take the OTA. My guess is somewhere along the way you froze or uninstalled some of the preinstalled bloatware? Which can cause the update to fail this was my case at least I sbfed to. 602 then took 2 OTA'S to .621 unfortunatley I regreted it you may want to look around at method to freeze updater instead your rooted try a different rom or 2 before making the decision
Click to expand...
Click to collapse
Where are the best areas to look for info on roms. I have clorkwork rom manager but there are not any roms I recognize.
If I were to back up my rom and then use titatanium back up would I be able to restore to my current state.
rkshack
Rkshack said:
Where are the best areas to look for info on roms. I have clorkwork rom manager but there are not any roms I recognize.
If I were to back up my rom and then use titatanium back up would I be able to restore to my current state.
rkshack
Click to expand...
Click to collapse
RootzWiki is the best place to find roms.
You can make complete backups in ClockworkMod Recovery of your entire rom. I would use MyBackup Root to backup things like individual apps, data, SMS, etc.
Sent from my DROIDX using Tapatalk
update failed
Rkshack said:
I have a droid x that is rooted and has the hack so I can wirelessly tether. I used the voodoo ota root keeper to try and keep my root. When I try to install the update it fails. I also have clockworkmod recovery installed. Any suggestions?
rkshack
Click to expand...
Click to collapse
I also had the same failure, it was due to my having removed some of the bloatware. I loaded the 605 SBF file and rooted this installed al the root programs i would need along with voodoo ota and made a root backup, ran all my programs and did the update, all went ell and I was able to renew root with voodoo ota keeper. so far i have had no problems and am on the 621 update and fully rooted. Titanium backup works fine and I have been able to remove the bloatware.
Hope this helps and i am not too late.
From what every been saying, don't upgrade to 621. Just flash a custom rom right now since you are rooted and you can sbf back to 602 or 605 as needed.
I have 2 Droid X and both running CM7 and its awesome. I tried MIUI and Gummy but couldn't get into it.
4.5.621 install failure
Greetings. This looks like the right thread for this issue, but if not, please redirect me.
Some background:
DroidX
Android version 2.3.3
System version 4.5.605.MB810.en.US
currently rooted
Being a laggard, I did not accept the 621 update when first offered through OTA. My 4.5.605 DroidX was rooted and I'd read that I'd have to either unroot or "hide" root in some manner. It seemed like a bit of trouble and I had other life issues at the time.
After things cleared, I contacted VZ and they pushed the upgrade again. After "unrooting", I accepted the OTA upgrade, but each installation attempt failed after a successful download. No other diagnostics, just "the update failed". I tried this multiple times after reboots, battery removal, cache clearing and such. I then did a factory reset and tried again - still the same sequence, successful download, install now, update failed.
So I called VZ and Moto. They suggested accepting the update while attached to a solid WiFi. All the same tricks were turned as with the OTA (another factory reset, clear cache, remove/replace battery) only these attempts used the WiFi (excellent signal). Same failure.
Moto then suggested I ship in the unit and for $110 they would handle it. Right.
So I found Blur_Version.4.5.621.MB810.Verizon.en.US.zip, downloaded it to the SD card and attempted to install using the recovery mode menu. This also fails but at least offers up the message: assert failed apply_patch ("system/app/AccountAndSyncSettings, apk", "-" then some odd number letter sequences followed by "error in /tmp/sideload/package.zip status 7.
I've since rerooted just out of curiosity to see if that would still work.
All this to fix the irritating bug of the phone powering back on by itself.
Any hints or advice?
Thanks.
-Joe
Sending your device in is not necessary at all.
It seems that you have removed one of the systems stock apps. Replace any apps that you may have removed and attempt to take the update again.
Or, you can SBF back to 602 and take the OTA update to .621. Just be sure to back up everything that you need (not including app data).
Sent from my Galaxy Nexus using Tapatalk 2
missteps
Bloatware was renamed but I've been pretty careful not to delete anything... even kept a list of what was renamed and to what. All that has been rolled back but clearly something was missed. The only thing that threw me a curve was the symlink on the Madden Football app, but even that now looks pre-modified.
I take it that changes to ACLs would also glitch the update, but what about file timestamps? How pristine do these stock apps have to be?
I'll check them again since there's little to lose in doing so. If I can't find a discrepancy, the sbf to 602 will be the next step.
Ironically, the reason for embarking on the bloat removal at the outset was to cure the auto-power on bug, which is now supposedly fixed in 621.
But it's all about the learning.
Thanks again.
Help me please 2.3.3 to 2.3.4
I recently tried updating my phone....When I go to system settings and then go to About phone and then system updates.... I get this update 4.5.621.en.us. Then I click download and then when it finishes...I click install and then it shuts off and then it boots up and says " Failed to update software" Click ok... Then that's it... Someone please help me....
DETAILS of FIRMWARE and ETC..
System Version: 4.5.605.MB810.Verizon.en.us
Model number: DroidX
Android Version: 2.3.3 Gingerbread
Someone please help me with this annoying error
Legit-Reflex said:
I recently tried updating my phone....When I go to system settings and then go to About phone and then system updates.... I get this update 4.5.621.en.us. Then I click download and then when it finishes...I click install and then it shuts off and then it boots up and says " Failed to update software" Click ok... Then that's it... Someone please help me....
DETAILS of FIRMWARE and ETC..
System Version: 4.5.605.MB810.Verizon.en.us
Model number: DroidX
Android Version: 2.3.3 Gingerbread
Someone please help me with this annoying error
Click to expand...
Click to collapse
Have you tried downloading the update via wifi? Is the update appoximately 32MB? Have you tried to flash the 621 sbf?
Sent from my MB860 using xda app-developers app
palmbeach05 said:
Have you tried downloading the update via wifi? Is the update appoximately 32MB? Have you tried to flash the 621 sbf?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
I don't know how to flash, and yes i've tried multiple times downloading the update....help
Legit-Reflex said:
I don't know how to flash, and yes i've tried multiple times downloading the update....help
Click to expand...
Click to collapse
Download RSD Lite, i think the latest revision is 5.7. then download the 621 sbf, any necessary drivers, and it also helps to have the fastboot/adb package as well (even though fastboot is useless for us, still something good to have).
backup anything you need backed up or do a nandroid. reboot to bootloader. connect device to computer. start up RSD Lite. click show device. click the button that lets you browse for files. select 621 sbf. click start. sit back and let it do its thing and you'll be back up and running in no time
Links files and instruction on how to flash a sbf, are in my list
sd_shadow's [Collection] of Links for: Droid X (MB810)
Sent from my XT862 using Tapatalk
deboyz1014 said:
From what every been saying, don't upgrade to 621. Just flash a custom rom right now since you are rooted and you can sbf back to 602 or 605 as needed.
I have 2 Droid X and both running CM7 and its awesome. I tried MIUI and Gummy but couldn't get into it.
Click to expand...
Click to collapse
621 isn't all bad. It's easy enough to root it now with an apk called Framaroot and you will then have all the latest security updates from Motorola. If you do go with 621 you are then"stuck" there as it is not possible to go back to any earlier versions. Most of the most recently updated Roms work fine with it.
Sent from my SCH-I535 using Tapatalk