What is it about OTA updates that allows them to be applied without losing apps/data/settings, but a "ROM" or downloaded update can't?
Hasn't anyone figured out how to apply an update equivalent to an OTA (but "root" safe) without losing settings?
You can flash a ROM and keep your apps and whatnot. Just don't format the /data directory.
Sent from my ADR6400L using Tapatalk
Also some ROMs provide OTA updates through ROM Manager.
No, thats not a storm. Its just my Thunderbolt layin down this post.
But I'd expect issues when changing roms from different devs for sure
Sent from my ADR6400L using XDA App
mike.s said:
What is it about OTA updates that allows them to be applied without losing apps/data/settings, but a "ROM" or downloaded update can't?
Hasn't anyone figured out how to apply an update equivalent to an OTA (but "root" safe) without losing settings?
Click to expand...
Click to collapse
If you are rooted & want the stock rom, you can go here, http://forum.xda-developers.com/showthread.php?t=1042004 you can flash the update without losing anything. I did it. All I had to do was delete the bloatware again...
Also there is a seperate file to flash the new radio. all works well for me... The version numbers were changed to show the original stock info, but that was to protect the leaker..
mike.s said:
What is it about OTA updates that allows them to be applied without losing apps/data/settings, but a "ROM" or downloaded update can't?
Hasn't anyone figured out how to apply an update equivalent to an OTA (but "root" safe) without losing settings?
Click to expand...
Click to collapse
OTA updates don't wipe DATA or Cache.
You can do the same on any ROM (basicly) as long as it is JUST a update.
___
Sent from my HTC ThunderBolt 4G LTE on XDA Premium.
mike.s said:
What is it about OTA updates that allows them to be applied without losing apps/data/settings, but a "ROM" or downloaded update can't?
Hasn't anyone figured out how to apply an update equivalent to an OTA (but "root" safe) without losing settings?
Click to expand...
Click to collapse
Also some of the dev's add in a script that wipes prior to the install. If your flashing a new version of the same rom just remove the script before you flash the rom and don't wipe. But it's done to reduce errors/force close issues.
OTA updates can be a multiple of things.. It can be applying a patch, it could be a radio update, it can be a firmware update aka OS. There can be an OTA that will require a data wipe. Usually you would see something like that let's say for example not that this is happening right now but let's just say we were on the Thunderbolt 2.2.1 Froyo and they updated us to Thunderbolt 2.3.1 Gingerbread then most likely it's going to be a full data wipe because it's more then a minor patch it's a whole OS and the file system would be changed example libs etc.. So you can't have old data mesh with new data that calls for certain things in the phone differently then Froyo did opposed to the way Gingerbread would.. Hope this helps!! On custom ROM's every ROM is different or unique in it's own way... Some have things that others don't, the DEV adds stuff or removes stuff and that will play a role in how the ROM itself will run or react... I'm trying to make this sound as simple as possible.. lol Anyways again hope this helped..
OTA updates are patches, and do an inplace update.
RUU Rums do a complete reinstall.
Think of it as an update to windows 7 v/s a new install
DroidVicious said:
OTA updates can be a multiple of things.. It can be applying a patch, it could be a radio update, it can be a firmware update aka OS. There can be an OTA that will require a data wipe. Usually you would see something like that let's say for example not that this is happening right now but let's just say we were on the Thunderbolt 2.2.1 Froyo and they updated us to Thunderbolt 2.3.1 Gingerbread then most likely it's going to be a full data wipe because it's more then a minor patch it's a whole OS and the file system would be changed example libs etc.. So you can't have old data mesh with new data that calls for certain things in the phone differently then Froyo did opposed to the way Gingerbread would.. Hope this helps!! On custom ROM's every ROM is different or unique in it's own way... Some have things that others don't, the DEV adds stuff or removes stuff and that will play a role in how the ROM itself will run or react... I'm trying to make this sound as simple as possible.. lol Anyways again hope this helped..
Click to expand...
Click to collapse
That's not necessarily true. My Mom's Epic went from 2.1 to 2.2.1 without wiping anything.
On top of that, these updates are coming from manufacturers that know every single thing (I hope!) about the software they worked with/designed. It's easier for them to ensure minimal to no complications without wiping.
06ms6 said:
That's not necessarily true. My Mom's Epic went from 2.1 to 2.2.1 without wiping anything.
On top of that, these updates are coming from manufacturers that know every single thing (I hope!) about the software they worked with/designed. It's easier for them to ensure minimal to no complications without wiping.
Click to expand...
Click to collapse
Droid Eris went from 1.5 to 2.1 and wiped everything...... At least mine did.. if you follow a RUU read some instructions for some older devices that are on the Verizon Wireless site they talk about backing info up... I guess it comes down to how you update or upgrade..
You can also use Titanium Backup or if you don't want to wipe modify the install script. Most devs have people wipe with new roms just to prevent issues from older versions of software. Really, no custom apps should be installed in the data folder but some devs put them in there. Just something to expect with custom roms unless the dev spends a lot of time and effort into it like CM7.
No, thats not a storm. Its just my Thunderbolt layin down this post.
Yeah, with an RUU I can see that happening. Never have with an OTA though.
The short answer to the OP's question is that they spend many thousands of dollars pay teams of developers for many hours to make the upgrade as seamless as possible for users. Our devs just don't care enough, and rightfully so. Would you rather avoid a wipe or get 5x's as many features?
Sent from my ADR6400L using XDA App
Jaxidian said:
The short answer to the OP's question is that they spend many thousands of dollars pay teams of developers for many hours to make the upgrade as seamless as possible for users. Our devs just don't care enough, and rightfully so. Would you rather avoid a wipe or get 5x's as many features?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
We care, but people do other mods beyond custom roms. This makes it unpredictable.
jcase said:
OTA updates are patches, and do an inplace update.
RUU Rums do a complete reinstall.
Think of it as an update to windows 7 v/s a new install
Click to expand...
Click to collapse
So, the file you posted at http://forum.xda-developers.com/showthread.php?t=1041514 isn't really the same as the OTA, since it installs as an RUU and wipes everything?
Do we have to wait for someone to grab the actual OTA file before we can have a "root safe" upgrade which doesn't wipe data?
jcase said:
OTA updates are patches, and do an inplace update.
RUU Rums do a complete reinstall.
Think of it as an update to windows 7 v/s a new install
Click to expand...
Click to collapse
Well said; think of it as an upgrade to Service Pack 1 instead of re-installing Windows from scratch. Excellent analogy
mike.s said:
So, the file you posted at http://forum.xda-developers.com/showthread.php?t=1041514 isn't really the same as the OTA, since it installs as an RUU and wipes everything?
Do we have to wait for someone to grab the actual OTA file before we can have a "root safe" upgrade which doesn't wipe data?
Click to expand...
Click to collapse
Dude its an ruu, its been said over and over, it says it in the title of that thread, so of course it installs as an ruu.
You do not want to install the OTA over a rooted device. At best it will disable root (if it flashes, which it shouldn't) at worst it will brick.
jcase said:
Dude its an ruu, its been said over and over, it says it in the title of that thread, so of course it installs as an ruu.
Click to expand...
Click to collapse
Yes, I understand that.
You do not want to install the OTA over a rooted device. At best it will disable root (if it flashes, which it shouldn't) at worst it will brick.
Click to expand...
Click to collapse
The RUU you posted wipes data, but keeps root. The OTA doesn't wipe data, but would loose root. What does it take to have an upgrade file that keeps root and doesn't wipe data?
This goes to my original question - what is it about an OTA that allows it to keep data? Why can't there be an update file with the new release, which keeps data and root?
Does an RUU format a partition before copying files? Or does it simply have a partition image which is flashed in bulk? How does an OTA-type update differ? I'm not asking for a simple "Win install vs. SP1" answer (which answers "what it does," not "how it does it"), but is there a flag in the upgrade file which is set, or what - how is this actually controlled?
Ota is done with recovery and a n update.zip, it applies patches to the system to bring it current. With non rooted devices you know what the firm ware is and can safely do this. Rooted devices, you don't know with certainty what the firmware is, and patching can cause problems.
While I could make one for rooted user, I don't have time to deal with the complaints and requests for help that will come with it.
Sent from LG Revolution HD Pro
Related
For anyone who's NOT on a LEAKED version of 2.1, you can still Root.
We have verified that the PB00IMG.zip goes through its checking process, and asks to update. It looks very much like the Root PB00IMG.zip IS able to be flashed over any phones that went from 1.5 to OTA 2.1.
So anyone who's holding back on going from 1.5 to OTA 2.1, for fear that they wont' be able to root, let your fears disappear.
Special thanks to ssgtob1 from AndroidForums.com who bravely tested booting up in HBOOT with the Root PB00IMG.zip on his SD card.
Thank you for your help, and anyone who DIDN'T leak, we STILL have you covered for Root. Go ahead and follow any set of normal directions for 1.5 to root, and you should be all set to Root your phone.
FOR LEAKERS: Some exploits are still being explored. I hope something comes to fruition. You will know as soon as anyone knows. I promise.
Thanks,
Paul
Peed on yet again leaking sucks. All I know is patience is a virtue I will forever remember to have after this phone. Guess im going to update to v3 leak from v1 since cannot update.
edgeupgx said:
Peed on yet again leaking sucks. All I know is patience is a virtue I will forever remember to have after this phone. Guess im going to update to v3 leak from v1 since cannot update.
Click to expand...
Click to collapse
Maybe you should continue to be patient with v1?.....
So, Ive updated to the OTA and did not have root on my 1.5 when I updated. Are you saying that even though I have done this that I can still root? If so, which tutorial/directions should I follow?
Don't worry, two things have been confirmed.
First the OTA will not work with the leaked ROMs installed.
Second, the OTA is exactly the same as the 2.1 leak v3.
This was confirmed on Android-forum by someone that took the time to compare every single file and CRC the binaries. The only difference was that the leaked ROMs use a different bootloader to install as they did and the actual OS and apps are exactly the same so if you got leak v3 you got the OTA.
The OTA won't install because you are already running it. The only down side is you still cannot root, but otherwise you have as good or better than the OTA.
.
So far, I have not come across a cooked ROM for root that does not have bugs or that functions as well as the OTA (which also has a few bugs). I'm hoping that the development will continue or even increase so we will have better ROMs soon.
xtremeskier97 said:
So, Ive updated to the OTA and did not have root on my 1.5 when I updated. Are you saying that even though I have done this that I can still root? If so, which tutorial/directions should I follow?
Click to expand...
Click to collapse
The exact directions, as if you were 1.5. You have a few options. If you have Windows, an easy way to go about it is this:\
http://forum.xda-developers.com/showthread.php?t=661413
The manual method does, literally, the EXACT same thing, it's just a teeny bit more technical, but you learn a lot about your phone in the process (that you wouldn't have learned using the Eris Master Application). If you're pretty technical (or using Mac OSX or Unix or Linux) then I would use the following tutorial (except, if you have Unix/Linux, you don't have to worry about drivers, and it's "./adb" instead of "adb" when you're running commands).
http://forum.xda-developers.com/showthread.php?t=647707
Good luck!
DigitalMD said:
So far, I have not come across a cooked ROM for root that does not have bugs or that functions as well as the OTA (which also has a few bugs). I'm hoping that the development will continue or even increase so we will have better ROMs soon.
Click to expand...
Click to collapse
I must vouch for Ivan's Eris_Official 1.0 being as bugless as the OTA, in my experience. This guy's been cooking ROMs for all kinds of phones for YEARS, and knows what he's doing. 100% clean, looks like stock, and is a lot faster.
http://forum.xda-developers.com/showthread.php?t=652044
Root after 2.1 OTA upgrade from 1.5
OK,
Let me get this straight and understand it crystal clear. Are you saying that an Eris with 1.5 without root can get the 2.1 OTA upgrade and later get root? Has anyone done this? Hoping it's true as I just got the OTA and installed it based on this thread. BTW, 2.1 .......NICE!
Bill
bczygan said:
OK,
Let me get this straight and understand it crystal clear. Are you saying that an Eris with 1.5 without root can get the 2.1 OTA upgrade and later get root? Has anyone done this?
Click to expand...
Click to collapse
Yes it is possible, and yes it has been done. I believe if you got the 2.1 OTA from a stock 1.5, the documented root method will work fine.
If you got 2.1 from any of the three leaks, you are stuck without root.
(Someone correct me if I'm wrong though! )
Add on question about rooting the OTA 2.1
I amn in the process of trying to root from the 2.1 OTA. Am I correct in thinking that following the walkthrough, that I will be replacing the OTA with another ROM which is functionally the same, but not the same exact one? Can I later redo the OTA from a file? Will this eliminate root?
Bill
bczygan said:
I amn in the process of trying to root from the 2.1 OTA. Am I correct in thinking that following the walkthrough, that I will be replacing the OTA with another ROM which is functionally the same, but not the same exact one? Can I later redo the OTA from a file? Will this eliminate root?
Bill
Click to expand...
Click to collapse
Following the walkthrough OR using the Eris Master Application (if you have Windows) will work JUST fine. (even though those things say you NEED 1.5, that's not exactly true, because OTA 2.1 works as well).
Once you Root, put a Recovery on there, then flash a nice ROM from Recovery, you will flash a ROM (like Ivan's Eris_Official_1.0) that has AT LEAST the exact same functionality as the OTA.
Later, if you want, you can follow the method documented on http://www.androidforums.com/htc-droid-eris/ in the All Things Root section, and click on AcidBath's thread, stickied at the top (then scroll about one page down) for DOWNGRADING from Root 2.1 back to Stock 1.5 (yes it is possible), then follow the tutorial for applying the MANUAL OTA update.
This will take you back from Rooted 2.1 back to OTA 2.1, if you should so choose (though I can't think of a good reason why you'd do that).
Once you have root, and you're using things like WiFi tether and so on, I'm guessing you won't go back. But the option IS available. And yes, if you go back to 1.5 then manual OTA, you will lose root, but you can GET IT BACK the same way you're getting it right now.
pkopalek - Very good info.
I'd just like to add that I manual upgraded from 1.5 to OTA 2.1 and hated it,
and found it possible to go from OTA 2.1 back down to 1.5..and I found the
process to be much easier than the manual OTA install.
I'd like to root now but after reading your instructions, (android forums site is
down right now), I'm still confused.
Root after 2.1 OTA upgrade from 1.5
I did the root last night. Took a while, but everything worked good. I now have recovery and can try other ROMS. Not quite sure yet how to access root or use su. But I love the wireless tethering. Using it right now. Used to use a wired tether program but this is better. I did lose all my apps and settings, but will rebuild it all. I don't think I'll use the OTA again. Love having root. Thanks to all who make this possible.
Bill
BlazeD OnE said:
pkopalek - Very good info.
I'd just like to add that I manual upgraded from 1.5 to OTA 2.1 and hated it,
and found it possible to go from OTA 2.1 back down to 1.5..and I found the
process to be much easier than the manual OTA install.
I'd like to root now but after reading your instructions, (android forums site is
down right now), I'm still confused.
Click to expand...
Click to collapse
Rooting, you just follow the directions for Rooting a 1.5 phone. If you're on the OTA, that's fine, if you're on 1.5, that's fine. The directions are 100% exactly the same.
The link I posted above was for DOWNGRADING from Root 2.1 to normal 1.5. Ignore that. Here's where you want to be:
The Eris Master App works GREAT if you have Windows:
http://forum.xda-developers.com/showthread.php?t=661413
Or do the normal manual Rooting method (it's exactly the same thing, just the App does the commands for you, or you do it yourself -- this is the method that I use, every time):
http://forum.xda-developers.com/showthread.php?t=647707
I suggest Ivan's Eris_Official 1.0 for a ROM, instead of 0.8t2 or whatever is suggested in that thread (that thread is kind of old).
http://forum.xda-developers.com/showthread.php?t=652044
bczygan said:
I did the root last night. Took a while, but everything worked good. I now have recovery and can try other ROMS. Not quite sure yet how to access root or use su. But I love the wireless tethering. Using it right now. Used to use a wired tether program but this is better. I did lose all my apps and settings, but will rebuild it all. I don't think I'll use the OTA again. Love having root. Thanks to all who make this possible.
Bill
Click to expand...
Click to collapse
I recommend Ivan's Eris_Official 1.0 for you too. Download and put it on your SD card.
http://forum.xda-developers.com/showthread.php?t=652044
Boot your phone into recovery, do Backup/Restore > nand backup (to back up your phone) then go back to main menu (volume down), Wipe > Wipe factory/data reset, wipe Dalvik Cache (both), back to main menu (volume down), Flash Zip from SD Card, flash Ivan's Eris_Official.
You'll be doing great.
ALSO:
anyone who's rooting and flashing these ROMs should also be flashing the latest Radio that comes with the OTA:
http://forum.xda-developers.com/showpost.php?p=6469408&postcount=113
yeah i rooted from the OTA and it worked fine it just took a bit longer than it should've because i had some trouble doing it on a mac but i figured it out eventually.
just follow the instructions and you should be fine *only if you are the 2.1 OTA or 1.5*
Hi! I'm on 2.1 OTA, and my droid Eris has never been modified in any way at a software or hardware level. I am running HBOOT 1.47.0000. Whenever I use the PB00IMG.ZIP (of which I have checked the MD5 sums) and reboot into the bootloader screen (The one with "HBOOT" and searches for images) I always get "No Image or wrong image!" and am never presented with the option of "push activate" as a result. Any tips? Yes, the PB00IMG.ZIP is in the root of the SD card. I can't really think that I'm doing anything wrong, as I've read the instructions a billion times, and checked every site with instructions, to see if there was any variation in methods.
Any input or tips (other than "don't root your phone" ) would be greatly appreciated!
It Works!!!
I gave up root for the OTA...never again. I'll 2nd (3rd, 4th, etc) if you are on the OTA you can get root. Thank God...so glad to be back. ;-)
Ok so I have what might be a very elementary question. And I apologize in advance if this is not the right thread or just generally a dumb question.
Is there any advantage or disadvantage to rooting from 2.1 OTA vs. 1.5? Also is there any real difference between my phone rooted from 1.5 and my wife's phone rooted from 2.1?
-------------------------------------
Sent via the XDA Tapatalk App
Monkeypuppet said:
Ok so I have what might be a very elementary question. And I apologize in advance if this is not the right thread or just generally a dumb question.
Is there any advantage or disadvantage to rooting from 2.1 OTA vs. 1.5? Also is there any real difference between my phone rooted from 1.5 and my wife's phone rooted from 2.1?
Click to expand...
Click to collapse
As far as I understand it, after rooting, you will have both of the phones on 2.1 rooted.
I am ready to install the latest update to my x2, but i am currently rooted and have the pulldown toggle zip and crt animation on my device, as well as the supercharger script, i know its very easy to remove the supercharger script,but would the crt or pulldown effect the install? Anyone encountered this issue yet?
thanks for the help.
amancini92292 said:
I am ready to install the latest update to my x2, but i am currently rooted and have the pulldown toggle zip and crt animation on my device, as well as the supercharger script, i know its very easy to remove the supercharger script,but would the crt or pulldown effect the install? Anyone encountered this issue yet?
thanks for the help.
Click to expand...
Click to collapse
In order for you to update your gonna have to sbf back to 2.3.3 if that's what your on. If not, then the update will fail because of the root. You will be able to update once you sbf & wipe data in stock recovery as well just to be safe. Hope that helps
Edit: this is for if you are trying to get the ota...sorry I should clarified that first
thanks for the help that basically clears it all up, seeing as im fairly happy with it right now im going to leave well enough alone, when they roll out a bigger update i will consider it, thats what i figured i was going to have to do.
amancini92292 said:
thanks for the help that basically clears it all up, seeing as im fairly happy with it right now im going to leave well enough alone, when they roll out a bigger update i will consider it, thats what i figured i was going to have to do.
Click to expand...
Click to collapse
Just use titanium backup then and back to stock, do the update and reload ur apps. Takes all of about an hour, tops.
Droid X2 - Eclipse v1.0
yeah i have all of that done already, i might give it a try, thanks
Rp...I don't think it will fail just due to root. U WILLA lose ur root.
It most likely WILL fail due to the mods/or rom u run due to missing files that are necessary.
if u are stock rooted I think it would work...but either way good idea to go back bone stock just to avoid any issues altogether
im running the completely stock rom, removing the script i have isnt an issue what so ever, is there any way to remove installed zips that were installed in the recovery?
ashclepdia said:
Rp...I don't think it will fail just due to root. U WILLA lose ur root.
It most likely WILL fail due to the mods/or rom u run due to missing files that are necessary.
if u are stock rooted I think it would work...but either way good idea to go back bone stock just to avoid any issues altogether
Click to expand...
Click to collapse
True always better to be safe than sorry
if your on stock and you want to return your animations to stock you could possibly extract framework-res.apk from /system/framework/ of the stock gingerbread and push it via adb to your phone or you could use root explorer to do so as well. that should erase your mods to animations. and you'll most likely have to reboot after. but animations should retrun to stock after, than unroot and take the ota. but its never a bad idea just to go to bone stock via sbf as rp076 suggested
For taking off the toggles u can just flash the stock notification zip from one of those threads I think it is there somewhere. Or ask the creator of the toggle zip u flashed for the stock one...
But ur safest bet is sbf and data wipe. It's not hard to do at all and is just a good thing to know how to do
I recovered my stock rooted backup from eclipse .8 and took the OTA no problem. You will lose root but Pete's one click will work to root again. You won't lose any apps.
Sent from my eclipsed DROID X2 using xda premium
rp076 said:
In order for you to update your gonna have to sbf back to 2.3.3 if that's what your on. If not, then the update will fail because of the root. You will be able to update once you sbf & wipe data in stock recovery as well just to be safe. Hope that helps
Edit: this is for if you are trying to get the ota...sorry I should clarified that first
Click to expand...
Click to collapse
Steve125 said:
I recovered my stock rooted backup from eclipse .8 and took the OTA no problem. You will lose root but Pete's one click will work to root again. You won't lose any apps.
Click to expand...
Click to collapse
Why do people keep thinking that just because you have root you have to SBF.. Root has nothing to do with the OTA update..
If you try and it fails it's not due to root, it would have to do with something frozen, or you have OTA Blocked with Rom Manager, or something else changed...
Of all the phones out there I can't think of any (ever) that have blocked OTA updates just because of root access.. In fact OTA Blocking had been added in to Rom Manger a few years back to prevent the OTA updates so people wouldn't update and lose root on updates that were not rooted yet.
On a side note, why would you SBF to 2.3.3 instead of just going to 2.3.4? You're just adding an extra step there. That would be like flashing back to Froyo SBF (what's the point?) if you want 2.3.4 GB..
masters said:
Why do people keep thinking that just because you have root you have to SBF.. Root has nothing to do with the OTA update..
If you try and it fails it's not due to root, it would have to do with something frozen, or you have OTA Blocked with Rom Manager, or something else changed...
Of all the phones out there I can't think of any (ever) that have blocked OTA updates just because of root access.. In fact OTA Blocking had been added in to Rom Manger a few years back to prevent the OTA updates so people wouldn't update and lose root on updates that were not rooted yet.
On a side note, why would you SBF to 2.3.3 instead of just going to 2.3.4? You're just adding an extra step there. That would be like flashing back to Froyo SBF (what's the point?) if you want 2.3.4 GB..
Click to expand...
Click to collapse
Calm down killa...just stating what I know thru past experiences & I'm not the only one who's had the problem before. When the 2.3.3 update first came out I couldn't update because my phone still was rooted, NOTHING FROZEN OR REMOVED. I read in other threads at the time that sbf'ing was the way to fix the problem. Once i did that, i was able to get the update installed successfully. Its not a wrong procedure, but a way to be sure to get a clean install. And as for flashing back, I was saying to do that if he wanted the ota
Side note...rom manager isn't or hasn't even been available yet for this phone ...surely you knew that
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 have an Incredible 4g on Verizon that I acquired during the first week of release. I was fortunate enough to get it unlocked during the time when HTC allowed it from their site. I unlocked the phone, installed TWRP, and rooted my device (I'm not entirely sure how I did this).
It's been over a year now, and my phone is kind of sluggish. How can I go about updating this phone to the latest software? I'd settle for the latest OTA from Verizon, as long as I can keep it rooted.
I'm also willing to flash one of the other kernels, but I dont really have any experience flashing CM or Viper.
So what's the best way to go about doing this? How do you update an already rooted phone? Ideally I'd like to keep all apps/data during the update. Any information or links for how to update appreciated!
My phones details:
Android 4.0.3
HTC Sense 4.0
Software: 1.43.605.3.710RD
HTC SDK API: 4.11
it probably won't even install unless you return to stock recovery.
another poster already confirmed losing root after installing the update.
imo - the update is not worth it anyway. they other thread lists the changes... nothing significant.
if your phone is sluggish either find out what is causing it (app, etc), tweak performance using your root, or wipe it and start clean. i would not give up an unlocked, rooted device for this update.
j13smiley said:
it probably won't even install unless you return to stock recovery.
another poster already confirmed losing root after installing the update.
imo - the update is not worth it anyway. they other thread lists the changes... nothing significant.
if your phone is sluggish either find out what is causing it (app, etc), tweak performance using your root, or wipe it and start clean. i would not give up an unlocked, rooted device for this update.
Click to expand...
Click to collapse
Is this just for stock updates, or for Viper/VM mods as well? I'm willing to step up to 4.3 or 4.4 with one of these custom ROMs, assuming I can keep root.
Is this a complicated process to install one of these custom ROMs (anything special since my phone is so "old")?
Will I have to wipe and install from scratch as well?
You can always clear your cache and davek cache to help improve speeds.
zackiv31 said:
Is this just for stock updates, or for Viper/VM mods as well? I'm willing to step up to 4.3 or 4.4 with one of these custom ROMs, assuming I can keep root.
Is this a complicated process to install one of these custom ROMs (anything special since my phone is so "old")?
Will I have to wipe and install from scratch as well?
Click to expand...
Click to collapse
Installing a fresh/new ROM is very easy, and it will indeed require reinstalling apps. However, Look at getting Titanium Backup Root - I highly recommend the Pro version - you can back up all of your apps and data. Once performing a full TiB backup to your external SD card, you can wipe and install a fresh ROM, then restore any/all apps and data backed up with TiB. The app will pick up right where you backed it up, settings and all. You may need to re-set up a few apps (such as email settings).
If you like sense, I recommend ViperLTE. It's very close to stock Sense, but offers several great tweaks you can choose to use (or not). Installing it is easy if you have TWRP recovery installed. If you don't have TRWP installed, look at mdmower's thread for that recovery. I also highly recommend performing a full Nandroid backup to your external SD card before doing anything.
j13smiley said:
it probably won't even install unless you return to stock recovery.
another poster already confirmed losing root after installing the update.
imo - the update is not worth it anyway. they other thread lists the changes... nothing significant.
if your phone is sluggish either find out what is causing it (app, etc), tweak performance using your root, or wipe it and start clean. i would not give up an unlocked, rooted device for this update.
Click to expand...
Click to collapse
Very true... I, too, lost root after OTA update. I've tried every method I could find to attempt to unlock bootloader now with update... even tried wipe and flash of stock RUU 2.17.605.2: unable to go back to older version due to updated bootloader (wouldn't let me load it).
It'd be nice if HTCdev simply updated for a .bin that'll work... I tried flashing unlock_code.bin from previous experiences... but wouldn't work either. Any rumors of a new method to unlock the new bootloader?
So I have read multiple articles on how to unroot and have tried 2 of them with no avail. Can anyone explain to me or point me in the right direction on to a "How to unroot for dummies" or something!? I tried getting a nandroid backup and putting in in TWRP/backups/ but for some reason when I boot into recovery and select "Internal Storage" it doesnt show anything! Then I tried to flash the stock recovery from the toolkit and I get an error. Any help would be appreciated.
CavyS said:
So I have read multiple articles on how to unroot and have tried 2 of them with no avail. Can anyone explain to me or point me in the right direction on to a "How to unroot for dummies" or something!? I tried getting a nandroid backup and putting in in TWRP/backups/ but for some reason when I boot into recovery and select "Internal Storage" it doesnt show anything! Then I tried to flash the stock recovery from the toolkit and I get an error. Any help would be appreciated.
Click to expand...
Click to collapse
There is a step by step guide to do this under the General section of this forum.
Here is a link...
http://forum.xda-developers.com/showthread.php?t=2751011
I would ask why you want to unroot? Unless you are selling/trading the device, its my opinion that once you are rooted, there are few other valid reasons to go back.
scott500 said:
There is a step by step guide to do this under the General section of this forum.
Here is a link...
http://forum.xda-developers.com/showthread.php?t=2751011
Click to expand...
Click to collapse
Yeah that might as well have been written in Arabic. I think that might be one of the methods I tried though?.. Except when I put the Nandroid backup in TWRP/backups then rebooted my phone into recovery the backup wasnt showing in there no matter what I did, and the other way just got an error.
redpoint73 said:
I would ask why you want to unroot? Unless you are selling/trading the device, its my opinion that once you are rooted, there are few other valid reasons to go back.
Click to expand...
Click to collapse
I want to unroot to get the OTA update. And I'm sure I could probably flash the new update or whatever, but I would rather just get the OTA. Just my OCD I guess?..
CavyS said:
I want to unroot to get the OTA update. And I'm sure I could probably flash the new update or whatever, but I would rather just get the OTA. Just my OCD I guess?..
Click to expand...
Click to collapse
I can never ever understand folks that root, than want OTA. As you suggested, the ROM is already available (stock rooted) in a custom recovery-flashable form, supplied graciously just days after the OTA started rolling out. And if you are referring to an upcoming OTA, the same will probably be true; or it will be available earlier for the international version (and isn't that one of the reasons we root?).
If you want the firmware package that came with the OTA, that is available to flash on modded phones, as well.
redpoint73 said:
I can never ever understand folks that root, than want OTA. As you suggested, the ROM is already available (stock rooted) in a custom recovery-flashable form, supplied graciously just days after the OTA started rolling out. And if you are referring to an upcoming OTA, the same will probably be true; or it will be available earlier for the international version (and isn't that one of the reasons we root?).
If you want the firmware package that came with the OTA, that is available to flash on modded phones, as well.
Click to expand...
Click to collapse
Lol I know, idk why I have to have to OTA either. Its just an OCD thing. I think its because I know that what I'm getting from OTA is clean and is a 100% working squeaky clean release by Android. Opposed to a ROM that someones put together themselves. I'm sure there is nothing wrong with the ROM or that there is any kind of malware or viruses in it. But its just an OCD thing were I would never stop thinking about it. And first thing my phone crashes or runs into a bug regardless of the problem I would blame it on the ROM. Lol now I sound like a sociopath
CavyS said:
now I sound like a sociopath
Click to expand...
Click to collapse
Haha, not really.
If a clean, bugfree OS is what you crave, than I would actually strongly disagree with the notion that an OTA is the way to do that. OTA is often a mess, as it only updates some things, and not other (not a complete image) and also keeps user data; which if you will see from any forum thread (here or other places) about bugs after OTAs, keeping user data is often the cause of many issues.
Factory reset plus OTA is one way around this. But if you really are OCD about a "clean" stock install, I would run the RUU. Either get S-off, or relock bootloader beforehand; and backup user data as this will be wiped. RUU is a complete factory released image.
redpoint73 said:
Haha, not really.
If a clean, bugfree OS is what you crave, than I would actually strongly disagree with the notion that an OTA is the way to do that. OTA is often a mess, as it only updates some things, and not other (not a complete image) and also keeps user data; which if you will see from any forum thread (here or other places) about bugs after OTAs, keeping user data is often the cause of many issues.
Factory reset plus OTA is one way around this. But if you really are OCD about a "clean" stock install, I would run the RUU. Either get S-off, or relock bootloader beforehand; and backup user data as this will be wiped. RUU is a complete factory released image.
Click to expand...
Click to collapse
Quick question. I put the Nandroid backup in the TWRP/backups/ folder. It doesnt show up in "Restore" but it shows up in "Install" in TWRP Recovery. When I click on it in "Install" it asks me "Swipe to Confirm Flash" Is it okay to flash Nandroid backup from the "Install" location or does it have to be done through "Restore"?
redpoint73 said:
I would ask why you want to unroot? Unless you are selling/trading the device, its my opinion that once you are rooted, there are few other valid reasons to go back.
Click to expand...
Click to collapse
I unrooted ?. Main reason for me was to use ISIS and be able to play a game me and some buddies play. I had root and ISIS didn't like it, so grabbed rootcloak but game disliked xposed
Sent from my HTC One_M8 using Tapatalk
twiggums said:
I unrooted ?. Main reason for me was to use ISIS and be able to play a game me and some buddies play. I had root and ISIS didn't like it, so grabbed rootcloak but game disliked xposed
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yeah I just updated with RUU, I'll re-root again once 4.4.4 gets pushed out.