My phone have been rooted recently to RC29. I got a popup saying do I want to update. Of course I said update later. I was wondering what would happen if I updated instead of modding cupcake through SD card?
Yellowelectronic said:
My phone have been rooted recently to RC29. I got a popup saying do I want to update. Of course I said update later. I was wondering what would happen if I updated instead of modding cupcake through SD card?
Click to expand...
Click to collapse
You'd probably lose root.
You will lose root. No probably involved
Related
First of all let me say sorry for posting this without searching first, but I'm at a bar with no WiFi.
I rooted my buddies g1 using the onetouch method. He later accepted the 1.6 update after I gave it back. Now I can't access recovry to get to the nandroid backup i made. What are my options?
It seems he lost root becuase in terminal I can't get Su access
You lost root. downgrade down to 1.5 again and do a one click root. then flash a rooted donut rom so it doesn't bring up the option to update.
Thanks for the quick reply. I figured id have to do it again so no big deal. I will just have to beat him up if he does again lol
he shouldnt be getting OTA's from a rooted ROM
B-man007 said:
he shouldnt be getting OTA's from a rooted ROM
Click to expand...
Click to collapse
it happened to me when I had the stock spl. I flashed over the engineers, and it went away.
well I did the OTA.... and ive rooted it following toasts tut... i got it to boot in recover mode... and im doing a NAND backup... oh just finished actually... i swear im not lying lol..
i finished the NAND backup and did a system reebot within the recovery... now let me get this straight tho... within the recovery is where I would flash a new rom yes? if I were to power off the Evo, root is gone right, this is only like a softspl ?
crap...EDIT:
um crap... nvm apparently i didnt update...
i swear I downloaded, installed, restarted the phone to allow install... but it shows software number 1.32.651.1.
maybe because I did a factory reset? then that would mean that this update is rather a patch (ie like a cab fix)??
or did the update not apply?
Ya, I had to download and install the update twice. There is no way root is worth the SD card bug, so until there is root for the patched ROM, no root for me.
The thing is right now we have ghetto root. The other devs have specifically said the update conflicted with root. Best not to install it if you care about it.
Aridon said:
The thing is right now we have ghetto root. The other devs have specifically said the update conflicted with root. Best not to install it if you care about it.
Click to expand...
Click to collapse
I don't. Not gonna bother rooting until after the official 2.2 ROM releases in August or so.
Allow me to explain my vague topic.
My son and I both have a droid pro, and are both running update 3.8.7
However, both of our phones were rooted before the update came and simply let it update.
After it got updated I noticed I was not rooted anymore. And z4root would not unroot my phone, or root it anymore.
Basically it was in sort of an in-between state, between rooted and unrooted.
The way I had to fix mine was by running the 2.2.6 (or whatever it was )sbf I had found on TBH, and from there going through the update progress.
Problem with that was that I had to set it back to factory settings.
So, my son's phone is still in that in-between state. Does anyone here know if it will pose a problem when this new gingerbread update hits his phone?
Will I be forced to do a factory reset with a previous sbf in order to be able to do it without it bricking?
I can't speak from personal experience, but others here have strongly suggested unrooting before update to prevent problems like what you described. As for the latest update, there are not really any reports yet on how it has gone for rooted users yet.
Before the last 3.8.7 updated, my phone was rooted with z4root and I had some unimportant apps frozen, nothing that is really crucial. I went ahead with the update (using the update.zip) which worked just fine. Yes, z4root is a bit confused of what is going on but I would not worry about it - I guess it is just logging events and thinks that because u havent unrooted it thru the program, it must still be rooted. The update removes the root anyways .. but I went ahead to unroot it with aroot again which worked like a charm on 3.8.7. At the moment, I am going to updating to Gingerbread also using an update.zip and I can give you a detailed report on how things went in a little bit ...
tnt118 said:
I can't speak from personal experience, but others here have strongly suggested unrooting before update to prevent problems like what you described. As for the latest update, there are not really any reports yet on how it has gone for rooted users yet.
Click to expand...
Click to collapse
This.
You might be able to go through just fine without flashing the SBF, but it's always a good idea to unroot/unfreeze apps and be stock for an update. Always.
Not always.
After the update from 2.26 to 2.63 (cant remember?) I had rooted my phone with z4root and froze some unimportant bloat ware, I didnt touch any programs that I deemed important for the system. I then proceeded to update to 3.8.7 without unrooting or unfreezing apps! It worked fine. After this, the system was unrooted again, I rooted again with aRoot without any problems.Now, I upgraded to Gingerbread, also coming from being rooted. The individual updates remove the rooting and you are back at point zero and, as long as you dont have any important system utilities frozen, it will work absolutely fine.
vivid22 said:
Before the last 3.8.7 updated, my phone was rooted with z4root and I had some unimportant apps frozen, nothing that is really crucial. I went ahead with the update (using the update.zip) which worked just fine. Yes, z4root is a bit confused of what is going on but I would not worry about it - I guess it is just logging events and thinks that because u havent unrooted it thru the program, it must still be rooted. The update removes the root anyways .. but I went ahead to unroot it with aroot again which worked like a charm on 3.8.7. At the moment, I am going to updating to Gingerbread also using an update.zip and I can give you a detailed report on how things went in a little bit ...
Click to expand...
Click to collapse
Interesting. Well if the root has been removed then there is no problem.
My son has a lot less problems then I do so I never had to freeze any apps. Meaning I basically never had to root his phone to begin with. So I may just get away with doing nothing then.
I mean I had rooted his phone on the previous system, on 3.8.7 it never worked with z4root so I'm guessing it's not rooted at this point.
I'll try to double check
As for my own phone, I will need to keep an eye on how to after the new update. I have serious battery problems that I blame on useless background processes.
I'll just tell him to go ahead and run it, if it ever comes to us that is.
Thanks guys
That is true, but z4root is just mistaken in a sense that it is confused and thinks its still rooted while its actually not ... Unless you click unroot in z4root, it will always assume its still rooted. z4root will not work in the 3.8.7 version as its not compatible. You need to use aRoot for that. And I can confirm that all updates work, even when the phone is left rooted before the update! Every update automatically unroots (locks) the phone again anyways.
Ok.
I just found the update on droidforums and went ahead and installed on my phone because I couldn't wait for Verizon
Later on ill do my sons phone as well. Im sure it will go well so ill report back to help ease the mind of others.
yeah so it wasnt a problem. I ran the same update.zip file i found and my sons phone is running nicely.
vivid22 said:
Not always.
After the update from 2.26 to 2.63 (cant remember?) I had rooted my phone with z4root and froze some unimportant bloat ware, I didnt touch any programs that I deemed important for the system. I then proceeded to update to 3.8.7 without unrooting or unfreezing apps! It worked fine. After this, the system was unrooted again, I rooted again with aRoot without any problems.Now, I upgraded to Gingerbread, also coming from being rooted. The individual updates remove the rooting and you are back at point zero and, as long as you dont have any important system utilities frozen, it will work absolutely fine.
Click to expand...
Click to collapse
It may work just fine, and it may even work fine most of the time, but it's still a good idea to unroot before installing a stock update. A lot of issues can potentially come up. Unrooting doesn't hurt anything since the updates break root anyway. It's just a good precaution. A lot of people had major issues with the last 2.2 update when they installed it without unrooting first.
It looks like all is well on updating with the Gingerbread release. But better than safe than sorry I say.
Hello everyone. I was wondering if this would work:
Root, remove all bloatware, and then unroot and get OTA update. Will my phone, after OTA, remain without Bloatware?
The short answer is - no.
The longer answer is - you won't get the update unless you flash it manually as PD15IMG (which wipes and reformats everything anyway).
Jack_R1 said:
The short answer is - no.
The longer answer is - you won't get the update unless you flash it manually as PD15IMG (which wipes and reformats everything anyway).
Click to expand...
Click to collapse
what I mean is to root the phone, remove the apps like Asphalt, friend streem, etc. Then unroot it and wait till I get stock OTA
I think friend stream is removable but I may be wrong
No. Once you get the official OTA you will be subject to all the T-mobile bloatware. If you really want the stock gingerbread ROM, there is a rooted version with and without the new radio in the development forums.
You can get rid of the bloatware or you can have the gb update, but you cant do both until an exploit to root the update comes out.
AntonJart said:
what I mean is to root the phone, remove the apps like Asphalt, friend streem, etc. Then unroot it and wait till I get stock OTA
Click to expand...
Click to collapse
I understood what you've meant, and the answer doesn't change - no, you can't do it, the OTA will bring EVERYTHING on the system back to stock or won't work at all.
Jack_R1 said:
I understood what you've meant, and the answer doesn't change - no, you can't do it, the OTA will bring EVERYTHING on the system back to stock or won't work at all.
Click to expand...
Click to collapse
thats bad
I have my phone rooted, but I was wondering if Verizon can send anything down to unroot it.
If yes, what can I freeze to prevent OTA updates? Also, if we are unable to load custom ROMs ever, for whatever reasons, would that mean we would be stuck with this build of 4.3 because Verizon could take away root with an update? Thanks.
cooch said:
I have my phone rooted, but I was wondering if Verizon can send anything down to unroot it.
If yes, what can I freeze to prevent OTA updates? Also, if we are unable to load custom ROMs ever, for whatever reasons, would that mean we would be stuck with this build of 4.3 because Verizon could take away root with an update? Thanks.
Click to expand...
Click to collapse
From what I've read freezing SDM 1.0 should block OTA updates.
cooch said:
I have my phone rooted, but I was wondering if Verizon can send anything down to unroot it.
If yes, what can I freeze to prevent OTA updates? Also, if we are unable to load custom ROMs ever, for whatever reasons, would that mean we would be stuck with this build of 4.3 because Verizon could take away root with an update? Thanks.
Click to expand...
Click to collapse
Yes, more likely than not a OTA would take away root. However.. Verizon can't push a OTA onto your phone. yes it downloads it, and notifies you but dow not install unless you accept it to install.
You can freeze SDM to prevent this notifcation from showing up and from phone for checking on updates.
I say again though, Verizon does not force your phone to flash the OTA's, you must always accept the OTA.
+1
and go ahead and freeze sdm1.0...and more then likely Verizon will have the next update patch root.
droidstyle said:
+1
and go ahead and freeze sdm1.0...and more then likely Verizon will have the next update patch root.
Click to expand...
Click to collapse
I'm sure they will, I just hope we have a recovery by then