Another noob question: Will the rooted vibrant phones get the official 2.2 ota update automatically? If not, how can we get it? Do we have to unroot to stock 2.1 and manually flash official 2.2? If the answer to my first question is yes; what will happen? Do we get unrooted automatically n loose data?
Thanks.
*** Sent from my Samsing Vibrant using xda app
sLiKK said:
Another noob question: Will the rooted vibrant phones get the official 2.2 ota update automatically? If not, how can we get it? Do we have to unroot to stock 2.1 and manually flash official 2.2? If the answer to my first question is yes; what will happen? Do we get unrooted automatically n loose data?
Thanks.
*** Sent from my Samsing Vibrant using xda app
Click to expand...
Click to collapse
Although this isn't definitive, just expect that *IF* you have taken responsibility for modifying your phone (and rooting is modifying), you will have to take responsibility for updating it yourself. Merely rooting may not leave you with a brick post OTA, but we've also heard plenty of tales of unmodified or only-rooted phones being bricked with the last OTA, so be advised. And this is not just a Samsung issue. HTC, Motorola, LG...etc ad nauseum...
OTA's are made for those who do not modify their Android phones (i.e. the overwhelming majority of users). The only upgrade scenarios an OTA can reliably count on being workable are those where a phone's OS is in a known state. Samsung & T-Mobile cannot take into consideration modified devices when developing an OTA, because such modifications run the gamut and are impossible to predict.
Furthermore OTA's are pushed out in batches. In other words, all of the million-plus Vibrants will not be updated all at once, but in stages. This makes several things likely. First, it's likely that it could take many weeks for you to get any official OTA pushed to your phone. Second, it's equally likely that you will be able to get the OTA packaged as an Odin or CWM update long before you'd ever see the OTA officially.
So here's the gist...
If you want to rely on an OTA, don't modify your phone in any way whatsoever. If you want to modify your phone an OTA is irrelavent, as an update will be available to you as a modder long before it's available to the majority.
If you have a rooted stock 2.1 you will recieve the ota, but you will loose root.
Edit: id just listen to that guy up there
Fear the beard...
Related
I am running stock samsung firmware on the T-Mobile Vibrant.
I had been holding off on rooting/rom-ming it because i was afraid of bricking.
I think i want to root now for 2.2, and have been going over the forums.
However, I need a method of rooting which will also support my upgrading to a 2.3 rom later on when it is released. Because according to what i have read, the safest way to get to 2.3 would be to to go back to a stock 2.1 and then repeat whatever steps are given.
TL;DR: I need an easy point which gets me to Froyo right now which will aslo get me to Honeycomb later without too much brickage chances and complications. Thanks
You can root keeping the stock rom and still receive the OTA updates
Sent from my Galaxy S using Tapatalk
There is a ton of info on this site to assist IF you want to install a custom ROM. There is a great video that shows you a lot of what you need to do to be able to install the ROM. Take a look around and read read read. It is a fairly simple task and I have tried to brick my phone and ODIN has always come to the rescue!http://forum.xda-developers.com/showthread.php?t=821468
I've been searching and searching and can't find anything where this question is really touched on, at least not from Google.
Basically the thing I'm looking at is this. I come from a Droid X which had and still has a locked bootloader. I was always under the impression that this means two things:
1) MUST use signed updates
2) Cannot use custom kernels
And based on those two things my understanding was that you can theme and modify some small framework and /system stuff, but could never truly update the phone like you could with an unlocked bootloader.
This is where I'm confused. So we have unlocked bootloaders on our Thunderbolts which allows us to flash unsigned zips. Cool. But how does this affect future versions of Android? Like our current Gingerbread roms, aren't they based off of a leaked RUU? What would happen if let's say, Gingerbread is the final OS Upgrade we get from Verizon. How will the next major update to Android be loaded to us?
Do the developers have the ability to port new versions of Android without these leaked OTA's? Or do we rely on the OTA's that include new Android OS versions to progress? Thanks
When Verizon sends out updates our Devs can take them and edit them to work with rooted users. Thats why you will see things come from (I think his name is football) who gives us the updates from Verizon and then our Devs modify them to keep our root privileges. If you are rooted on a custom ROM tho you wont receive OTA.
Thank you for the response. I understand that part, but really what I'm trying to find out is:
Thunderbolt is on Froyo -> Verizon WILL update us to Gingerbread via OTA
Had Verizon NOT updated us to Gingerbread, would devs be able to take us there thanks to an unlocked bootloader? Or would the phone forever be doomed to use Froyo?
Take that principle and apply it to whatever comes after Gingerbread, because I'm pretty sure 2.3 will be the last major OS update this phone gets officially.
i cant give you a sure answer but BAMF has made sense 3.0 work on our phones and that is never releasing as an OTA i would assume if the next version of android comes to any 1ghz phones or well any htc phones someone will find a way just allot more work and more time.
Well thats basically all I needed to know. As long as we have an unlocked bootloader and a dev community willing to work on it, people can basically port any new versions of the OS even from other phone updates.
I just fear the idea of EOL and no more future OS updates.
Good way to answer your question is to take a look at the d1 and even the eris. They are both eol yet i know for sure the d1 has gingerbread, and i believe the eris does also.
sent from my bolt
I have never had the need but I am considering rooting. One item I am concerned about is the ability to get firmware updates after rooting. Do they still prompt/download? If not what do you guys do about this?
NEVER take a firmware update when you're rooted; thats never a good idea. Devs usually get the updates, cook them in the roms, then you would flash the updated rom over your current (if its same) or flash the newly rooted rom. Alot easier than it sounds, you'll get the hang of it. 9 out of 10 times accepting firmware updates will remove root. Just ask the retards that accepted the 2.3 GB update on their Evo 4G lol. Had to wait abt 3 months for root ...
On my note 2 I accepted the OTA update and some how I rooted it with the OTA Root keeper. Evertything works fine but I cannot install custom recovery. What woould be the best way to unlock the bootloader and install custom recovery now.
I also have galaxy s3 and droid bionic both are rooted and custom roms installed and working great.
I have been with Verizon 16 years and it's abuot time to change but I think there all the same anymore $$$
If you took the ota then you can not unlock your bootloader as of this time.
why on earth are folks so hell bent on ota's???? fyi when you buy a device that came locked but was unlocked by devs at xda, YOU NEVER EXCEPT ANY OTA! It has been posted all over this forum...please research before you do anything!!
Totally agree! I won't even update an app until I know what the changes are, and even then I usually wait to see if any issues arise with the update.
Doesn't matter how many times you warn people no to install an OTA because it has a bootloader, someone won't listen.
I would never consider taking a ota until after our devs have a chance to check it out. Besides if you run a custom rom your developer will most likely be updating to the new build and you know you can safely flash it.
Besides I know verizon is more worried about blocking crap than they are on their real updates.
Forget the security update and give us official 4.1.2 screw verizon! Verizon ota usually means bad things.
Travisdroidx2 said:
I would never consider taking a ota until after our devs have a chance to check it out. Besides if you run a custom rom your developer will most likely be updating to the new build and you know you can safely flash it.
Besides I know verizon is more worried about blocking crap than they are on their real updates.
Forget the security update and give us official 4.1.2 screw verizon! Verizon ota usually means bad things.
Click to expand...
Click to collapse
4.1.2 has very little to offer us.
adrynalyne said:
4.1.2 has very little to offer us.
Click to expand...
Click to collapse
I agree with that. However my point was instead of Verizon spending their time improving their devices they would rather spend their money and time trying to figure out how to screw us. I know 4.1.2 brings little to the table but maybe if they were not working on locking the bootloader they could improve on the builds instead. I would still rather have 4.1.1 over 4.2.1 any day.
I'm just your average Android enthusiast, not nearly as talented and skilled as you devs, but I know my way around my phone. I am currently rocking the Galaxy S4 SCH-I545 NC5 (Rooted with Towelroot and Safestrap 3.72 installed). I never thought highly of Samsung's user interface and have wanted to upgrade to CM forever, but as each new update comes I really, really want it, so I carelessly take the OTA. I've done this far too many times so I decided to disable the system update app so I wouldn't be bothered by the new updates that come around.
Anyway, I think it's time to upgrade to Lollipop now that it's available, but I really want to keep root access, and since you guys are the professionals, I want to know the best way to flash the new update instead of take the OTA, which, if I'm not mistaken, will let me keep root and the small possibility that I can get Cyanogen some day. Is it best for me to just go ahead and take the risk-free OTA update, or should I flash? If so, can someone guide me through the process? I'm sorry if this sounds like child's play to you but I don't want to brick my phone in any situation, so it'd be great if someone could help me with this. Thanks in advance!
Screenshots for more information:
http://imgur.com/CIBx5qY,KHATxkV,fKyJcoB#2
Update: I followed a tutorial to update to OC1, but was not successful (Wouldn't boot). I used Odin to reflash the NC5 and now I'm back where I started. Anyone have an idea?
Here's the link to the tutorial:
http://zidroid.com/how-to-update-keep-root-verizon-galaxy-s4-on-lollipop-oc1/#comment-6589
Edit: Tried this twice, both didn't work. I'm considering just taking the OTA and not getting root. What should I do?