I'm currently rooted, have titanium backup, deleted a bunch of bloatware, but that's about it. Will this screw up my phone when I update to Froyo via OTA update? OR can I just safely update when T-Mo rolls out froyo?
Thanks in advanced!
EDIT: Oh, and lets say I called T-Mo and got an unlock code, and unlocked my phone RIGHT NOW with the current FW, JID, will I lose the unlock?
Bump, anybody have a solution to my question?
draikz said:
I'm currently rooted, have titanium backup, deleted a bunch of bloatware, but that's about it. Will this screw up my phone when I update to Froyo via OTA update? OR can I just safely update when T-Mo rolls out froyo?
Thanks in advanced!
EDIT: Oh, and lets say I called T-Mo and got an unlock code, and unlocked my phone RIGHT NOW with the current FW, JID, will I lose the unlock?
Click to expand...
Click to collapse
Your YMMV. Last time Tmo rolled out JI6, many people with removed bloatware complained about issues. Stuck at Boot up. Not sure, if you would have any issues. only time will tell. If you have a backup of your stock, you can restore and manually force a update request once its rolled out. hope this helps.
=/ I don't have a backup of my stock
What do I do then?
My understanding is the update.zip file from rooting was causing the brick issues. If an ota comes all you have to do is unroot your phone before you install. You can be on a custom rom. I recieved an ota notification while on Bionix and after unrooting I accepted, installed and had no issues. Hopefully that answers your question.
regardless, if an OTA comes I would not accept it. Chances are that if YOU got an OTA update, it was on XDA days/weeks before you got it... and they should have a stock version with Root enabled that you could just flash.
If you do not have a backup, make one now! It's too easy to not have one. It's in the sticky if you do not know how.
Related
Hey guys, sorry to bother everyone with another question about the update but there are a few things I could really use clarification on if it's not too much trouble.'
I'm currently on 1.57, gingerbreak rooted, gladi ROM and sbf flashed the hsupa radio. I can't really find anything about what's done in the update so i can't even tell if it'd be worth it for me to update. Will anything happen if I don't update? I didn't have any problems with my iphone when I skipped over 3 or 4 updates...just want to make sure nothing bad will happen.
Next, if I do want to update (which I don't think I will because I'm reading that a lot of people have been having problems with some things) if there a program I can use to save all of my rooted features and re-apply them after I've updated? I read about beforeupdate and afterupdate but I can't find any information about what they do and if they'll do what I'm looking for.
I'm thinking that with this update being buggy, moto will have to roll out another update pretty soon and maybe I should just wait for that one.
Here you go: Release Notes from Motorola
I accepted the update like 30 hours ago, retained root - No problems or issues here! Everything seems to be working fine.
You can use Titanium Backup to backup your user apps, I would recommend NEVER BACKUP/RESTORE SYSTEM APPS because you can get a lot of force closes and stuff.. Thats happened to me in the past.
http://goo.gl/EyexL
If you have the time and the patience, go back to 1.26 and OTA update to 1.83. The majority of the problems your reading about are from phones that are modded and have been altered and then updated. I had similar issues with my phone after the update, much like the others your reading about. Not staying up to date on official updates could leave you in the dark if a new update comes out and you find yourself stuck with a phone that cant be updated (easily). The 1.87 radio works but made my Atrix hot and chewed up battery. Im not saying its going to make a difference for you, With titanium backup and gingerbreak available now, its easy peasy to root and bring your phone back to your liking very quickly.
Beforeupdate and Afterupdate are used to retain root across upgrades. Gingerbreak is easier(click click, launch= rooted)
WiredPirate said:
I accepted the update like 30 hours ago, retained root - No problems or issues here! Everything seems to be working fine.
You can use Titanium Backup to backup your user apps, I would recommend NEVER BACKUP/RESTORE SYSTEM APPS because you can get a lot of force closes and stuff.. Thats happened to me in the past.
http://goo.gl/EyexL
Click to expand...
Click to collapse
so you're saying you updated without flashing back or anything (without changing ANY settings) and you retained everything?
spitefulcheerio said:
so you're saying you updated without flashing back or anything (without changing ANY settings) and you retained everything?
Click to expand...
Click to collapse
That is correct. I was on 1.57 rooted w/ GladRoot, NO MODS. I accepted the update, ran "afterupdate" from the GladRoot .zip. Now I'm on rooted and on 1.83.
EDIT: You cannot use this method btw since you have modded. You have to sbf first.
Dirtburgler said:
If you have the time and the patience, go back to 1.26 and OTA update to 1.83. The majority of the problems your reading about are from phones that are modded and have been altered and then updated. I had similar issues with my phone after the update, much like the others your reading about. Not staying up to date on official updates could leave you in the dark if a new update comes out and you find yourself stuck with a phone that cant be updated (easily). The 1.87 radio works but made my Atrix hot and chewed up battery. Im not saying its going to make a difference for you, With titanium backup and gingerbreak available now, its easy peasy to root and bring your phone back to your liking very quickly.
Beforeupdate and Afterupdate are used to retain root across upgrades. Gingerbreak is easier(click click, launch= rooted)
Click to expand...
Click to collapse
Yeah i know I once I'm updated, I can root again but I've downloaded tons of apps and changed so many settings to get this phone to run exactly how I want. I've spent a good amount of time changing little things here and there and I don't want to lose all of it!
Is there away to retain all of this information through some kind of backup or something? I have all my apps and user data backed up with TiBackup. If I go back to 1.26 and then update to 1.83, can i restore using TiBackup?
im not too keen on titanium backup other than how to use it for the most part lol. The static phone settings will be defaulted to shipping state if you go back to 1.26. there may be a way to do what you are trying but that's out of my league. These is a setting in Titanium to transfer phone settings across Rom's but i've never tried nor have i seen it on the Atrix Forum. (I never really looked for it, didnt need it, so there may be a thread on it.)
The fact that you have Gladiatrix Rom throws a wrench into the whole easy update thing. Check This if you havent already----- http://forum.xda-developers.com/showthread.php?t=1063618
same here i have no problem
WiredPirate said:
That is correct. I was on 1.57 rooted w/ GladRoot, NO MODS. I accepted the update, ran "afterupdate" from the GladRoot .zip. Now I'm on rooted and on 1.83.
Click to expand...
Click to collapse
Exactly what I did and everything is working fine. Ran afterupdate after the 1.83 OTA and things are working great~! everything retained
So I was reading on Droid-Life that there might be an OTA to ICS on 5/9. My question is if I rooted now, installing Amon Ra, backed up, and removed some bloat.
How would the OTA effect me? If I didn't want to bother with roms atm but just wanted to remove bloat. Would accepting the OTA mess anything up?
Be patient. Once the RUU hits the streets. One of the device will post a rooted, deodexed, deflated version. That's what I'm waiting on.
Masx said:
So I was reading on Droid-Life that there might be an OTA to ICS on 5/9. My question is if I rooted now, installing Amon Ra, backed up, and removed some bloat.
How would the OTA effect me? If I didn't want to bother with roms atm but just wanted to remove bloat. Would accepting the OTA mess anything up?
Click to expand...
Click to collapse
I doubt it they said an update was coming for the Xoom LTE too and so far like all android devices.... nothing. Go Google Go..
leoingle said:
Be patient. Once the RUU hits the streets. One of the device will post a rooted, deodexed, deflated version. That's what I'm waiting on.
Click to expand...
Click to collapse
So I shouldn't bother rooting for now?
Root and remove your bloat. If an OTA is released I say within a day you will see someone post a zip version you can place on your SD card and place right on your phone. Have some fun and let yourself go.
Jimi Mack said:
Root and remove your bloat. If an OTA is released I say within a day you will see someone post a zip version you can place on your SD card and place right on your phone. Have some fun and let yourself go.
Click to expand...
Click to collapse
I just didn't know if there was some crazy unrooting process or error that would happen if the OTA popped up on me or was forced to install it.
Considering I don't plan on installing a rom for a little bit till I'm more comfortable with using the phone.
Hello all,
Just had a quick question. I didn't know what search terms to use to get an accurate answer, since the search seems to pick up any and everything related to any of your search terms. I was wondering what exactly prevents an OTA update from taking. Is it the recovery that is installed? Is it having root? It's been a while since I have accepted an OTA for a device, outside of the Nexus on launch day. I have my Razr Maxx rooted, no custom rom. I tried a few of the ICS leaks but they were in safestrap, my non safe partition remains only rooted. When the OTA actually hits should I be able to accept it fine or will I need to go back to completely stock unrooted?
Things that prevent an OTA: ROMS, Bloatware frozen/uninstalled, custom recoveries (safestrap, bootstrap) so yes, when you want the OTA you'll need to fastboot back to complete stock for it to work. Root won't stop an OTA but OTA's generally break root.
You can try just uninstalling safestrap but I've read cases where just uninstalling it doesn't work and you need to fastboot back to stock.
everything wrong with motorola and Android has to do with idiot upper middle management execs having endless powerpoint presentations babbling corporate gibberish so they can make the next payment on their overpriced overlarge joke of a house and BMW. we are left to sort out the steaming pile of ****. i pray google has the sense to fire every last one of them and give their salaries and bonuses to the engineers!
Freezing bloatware has never prevented me from getting and OTA. Custom ROM and bloatware removal has/will.
tech_head said:
Freezing bloatware has never prevented me from getting and OTA. Custom ROM and bloatware removal has/will.
Click to expand...
Click to collapse
What is the difference between freezing and removal, from a technical standpoint? I rooted my Razr using CASUAL and then installed Titanium Backup Pro and have been zapping the Verizon bloatware. I do want the stock ICS when it comes out. I guess I could reinstall the bloatware from backup and then freeze it rather than uninstalling. I don't care so much if the OTA doesn't install, I can troubleshoot that, but I don't want the OTA to brick my phone, that's the main concern.
The main reason I don't want the bloatware on there is that I don't want there to be any danger of clicking on anything that will make my monthly bill go up. Sometimes I let my girlfriend or other people use my Razr and if they manage to get a $10 monthly charge on my bill because they just had to see NFL Mobile or something similar, I'm gonna be pissed
I'm fairly sure it just changes the extension to .apk.bak, but I could be wrong
So, I have bloatware frozen, but none uninstalled. If ICS /is/ released on the 12th for the Verizon RAZR, I should be able to get it OTA?
Rooted, stock 2.3.6
bpingry said:
So, I have bloatware frozen, but none uninstalled. If ICS /is/ released on the 12th for the Verizon RAZR, I should be able to get it OTA?
Click to expand...
Click to collapse
Yes, at worst case scenario: You might have to unfreeze everything, Install OTA RootKeeper, use OTA RootKeeper to a> Backup your root and B> Temporarily unroot your device.
On the last OTA that I received, I was not able to install the OTA until I ran the Temp Unroot from OTA RootKeeper, then the OTA went smoothly after that.
quarky42 said:
Yes, at worst case scenario: You might have to unfreeze everything, Install OTA RootKeeper, use OTA RootKeeper to a> Backup your root and B> Temporarily unroot your device.
On the last OTA that I received, I was not able to install the OTA until I ran the Temp Unroot from OTA RootKeeper, then the OTA went smoothly after that.
Click to expand...
Click to collapse
Apps in preinstall folder are required by OTAs those are the real bloats. Any other system modification will be verified too, like build.prop, init.d CWM and so on..
Remember an OTA update is an incremental update wich will check any required system piece, especially those I've mentioned.
Cheers
OK. So I have the pull down button mod. Will this get in the way? I've not removed any bloat or yet (was waiting for updates). All I have is pull down mod and root.
MarkyG82 said:
OK. So I have the pull down button mod. Will this get in the way? I've not removed any bloat or yet (was waiting for updates). All I have is pull down mod and root.
Click to expand...
Click to collapse
Yes, it's a system modification. You'll need to flash stock rom to flash an OTA update.
When installing an OTA you can press both volume buttons at the same time to to see dialog, and if anything fails you will have filename and directory of failed checks. And it won't auto reboot until you tell it too. I found the problem files for the ics leak from early April leak and was able to install without wiping.
Sent from my DROID RAZR using xda premium
See I'm not fussed about wiping. Id quite happily have stock ICS and mod it from there. Looks like I'll be hacking some way or other to get the official anyhow as I'm on linux. Unless someone can point me to a UK suitable stock rom I can fast boot or add flash from linux. I have add setup if that helps. My system version is 167.26.
Sent from my XT910 using xda premium
cause they arent bronies, duh.
ExtraDan said:
cause they arent bronies, duh.
Click to expand...
Click to collapse
Sorry, I don't understand.
Sent from my XT910 using xda premium
and you wont...
MarkyG82 said:
Sorry, I don't understand.
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
I don't understand them either, just don't make a big deal about it
Thanks for all the replies. I don't have any bloatware frozen and no system mods done so I guess once the OTA hits, as long as safestrap uninstalled smoothly, I should be good to go. Ill check out ota root keeper here shortly.
Sent from my DROID RAZR using xda premium
i just bought the droid razr maxx. there is supposed to be an OTA update to ICS soon. my question is, will i be able to switch back and forth from new rom and current rom? just wondering incase i dont like it. will it prompt me when the update is available, or will it do it automatically? also will it keep my current apps and settings after the update?
Once you upgrade thats IT, your stuck with the new, your apps should be fine if your stock and unrooted. The phone will inform you when an update is available, or you can check for updates to try to grab it sooner depending on the rollout schedule.
Could have done a search, there's approximately 1 billion ICS OTA threads already.......
Sent from my DROID RAZR using XDA
brons2 said:
Could have done a search, there's approximately 1 billion ICS OTA threads already.......
Click to expand...
Click to collapse
This was legit questions... this wasn't another "When is it" threads. Don't be too quick to jump.
BTW, Daniel, you mentioned that if you were stock, unrooted it would be fine. What if I'm rooted (still stock)?
RedRamage said:
This was legit questions... this wasn't another "When is it" threads. Don't be too quick to jump.
BTW, Daniel, you mentioned that if you were stock, unrooted it would be fine. What if I'm rooted (still stock)?
Click to expand...
Click to collapse
You will want to get the VooDoo OTA Root Keeper for free in the market.
Install, back up root.
When your update hits, go back into the app and select "temp un-root".
After the update, go back to the app and restore root.
Its been hit and miss for some ppl on the last OTA, has worked for me everytime tho.
stupidchicken03 said:
You will want to get the VooDoo OTA Root Keeper for free in the market.
Install, back up root.
When your update hits, go back into the app and select "temp un-root".
After the update, go back to the app and restore root.
Its been hit and miss for some ppl on the last OTA, has worked for me everytime tho.
Click to expand...
Click to collapse
Also don't freeze or delete any "bloat" as that can mess up your ability to update.
I appreciate the info guys!
Now, if we could just get the update...
daniel644 said:
Also don't freeze or delete any "bloat" as that can mess up your ability to update.
Click to expand...
Click to collapse
What about safestrap. If we are running sick rooted GB, OTA comes out, unfreeze all the boat, do I need to uninstall safestrap as well?
Many people have had trouble installing the leaks if they have SafeStrap and friends installed.
That doesn't mean an OTA update will fail though.
johnmagoo said:
What about safestrap. If we are running sick rooted GB, OTA comes out, unfreeze all the boat, do I need to uninstall safestrap as well?
Click to expand...
Click to collapse
When I restore the backup I made during the Safestrap install, it wipes out both root and Safestrap. But I made the backup as soon as possible before making modifications.
Simple question and hopefully different from all the other "It's here!", "Where are our ROM" threads..
I upgraded (if you can call it that) to the Galaxy Nexus literally like a week ago and deactivated my TB but it remains rooted.
Anyone know if there are dangers trying to activate it rooted with the intent to unroot, wait for the OTA, just in the hopes it will sell for more.
Or would you recommend unrooting then activating and then waiting for the OTA?
Hopefully you understand the question. I had the impression from a friend that if I tried to re-activate with root, it would red flag me for modified software. Thanks in advance.
DNak206 said:
Simple question and hopefully different from all the other "It's here!", "Where are our ROM" threads..
I upgraded (if you can call it that) to the Galaxy Nexus literally like a week ago and deactivated my TB but it remains rooted.
Anyone know if there are dangers trying to activate it rooted with the intent to unroot, wait for the OTA, just in the hopes it will sell for more.
Or would you recommend unrooting then activating and then waiting for the OTA?
Hopefully you understand the question. I had the impression from a friend that if I tried to re-activate with root, it would red flag me for modified software. Thanks in advance.
Click to expand...
Click to collapse
The stock rooted roms are posted on the Infected forums if you just want to flash the stock rooted ICS.
OR, you could unroot and flash the OTA, but doing so I believe will upgrade your hboot, so you'll have to wait a bit until get the s-off on the new hboot.
Either way, I'm sure it'll be all squared away in the next couple of weeks.
Personally, if it were me, I would unroot and go OTA. Fly around completely stock for a while on your phone. I did that when 605.19 came out and I was actually surprised how well it performed being completely stock (battery life aside). But that didn't last long for me--I rooted it pretty shortly after.
Also, I'm not sure if you'd be red-flagged for trying to update OTA from root. I mean the worst that could happen is the update won't go through, and more likely, the update will go through, but will completely remove root and s-off.
Don't take the OTA expecting to reroot!
wazup7 said:
The stock rooted roms are posted on the Infected forums if you just want to flash the stock rooted ICS.
OR, you could unroot and flash the OTA, but doing so I believe will upgrade your hboot, so you'll have to wait a bit until get the s-off on the new hboot.
Either way, I'm sure it'll be all squared away in the next couple of weeks.
Personally, if it were me, I would unroot and go OTA. Fly around completely stock for a while on your phone. I did that when 605.19 came out and I was actually surprised how well it performed being completely stock (battery life aside). But that didn't last long for me--I rooted it pretty shortly after.
Also, I'm not sure if you'd be red-flagged for trying to update OTA from root. I mean the worst that could happen is the update won't go through, and more likely, the update will go through, but will completely remove root and s-off.
Click to expand...
Click to collapse
There may not be a "re-root" after you take the new hboot!!!!
YOU HAVE BEEN WARNED!!!
I've been saying this and not enough people are listening and stuck not being able to root again.
I know one person even trying to work on the hboot right now and his device will no longer boot, so think again before taking the OTA.
It's up to you and doesn't effect me either way, just a few words of advice if you will.
Maybe this will change and another miracle as big as this release will happen and an exploit will be found on a 2 year old device with less then a handful of devs even looking at it.
This could change, but right now I would not count on it.
I took the update unrooted but still had revolutionary's hboot. I can confirm that the hboot was not overwritten by the new one.
Edit
Didn't realize there was a thread about this already lol. My bad.
Sent from my HTC6435LVW using xda app-developers app
Seems there is a LOT of revert to stock and unroot threads, is there a consolidated place or simple means of doing this? I think I'm going to undo everything I did and just her activate it stock. If she *****es down the road about not having root (unlikely), I'll worry about it then.
Thanks guys.