Its my understandig that if you root your phone but don't flash a rom you will still be alerted when your carrier pushes out ota updates. Now my question is if I install a different kernel such as chevy's or something to allow me to overclock my dx will I still be alerted for carrier ota updates?
Sent from my DROIDX using XDA App
crxin said:
Its my understandig that if you root your phone but don't flash a rom you will still be alerted when your carrier pushes out ota updates. Now my question is if I install a different kernel such as chevy's or something to allow me to overclock my dx will I still be alerted for carrier ota updates?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
You mean ROM not Kernel. (Kernel opens up a great deal of wounds, )
But the answer is no, you will not be able to update ota unless you flash back to stock ota sbf.
Just to add to what Steven58 said,
While it is true that loading a custom ROM will prevent you from receiving OTA updates, that's not necessarily a bad thing.
The dev's for those ROMs generally do a great job of keeping up with the latest /system files and updating their builds as necessary. Most likely any given custom ROM will have better functionality and stability than the stock Moto one anyway.
There are always some caveats and variables based on your own desires, but if the Stock Moto was done right, we wouldn't see so many popular ROM alternatives.
There will be cases when a new kernel (such as is the case with the most recent OTA .340) is released that you will need to either get the OTA, or hope some one releases an SBF. In those rare cases, you should be able to flash back to stock (with whatever the current system release is), do the update (which would update kernel, and possible radio, etc) and then proceed back to using your favorite ROM (assuming it's been updated to that version).
Clear as Mud?
Yup I understand it now. Thanks for the help and all the replies
Sent from my DROIDX using XDA App
Related
We have all these methods to downgrade and apply the OTA.
But can't we just flash ROMs that devs from the OTA?
What's the point of accepting the OTA?
Sent from my Incredible using XDA App
Well
1) Devs will need time to cook the OTA into a custom ROM, the OTA is ready on impact
2) The OTA does not require reinstalling your apps
3) Some have no problem with Verizon's stock ROMs and wouldn't want it cooked
4) Cooked roms tend to break things when adding and removing and mixing and matching (which is why cooked ROM threads are 99.9999999% bug reports) and some people would rather not have to deal with the extra bugs
5) Cooked roms are really to the taste of the cooker. If they don't like the facebook app, then I guess you won't have the facebook app; and if they like swype, well then you have swype. 1 person cooks, everyone else settles. That is not to everyones taste.
Ruggerxpunk said:
We have all these methods to downgrade and apply the OTA.
But can't we just flash ROMs that devs from the OTA?
What's the point of accepting the OTA?
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
The OTA may contain various fixes as the leaked versions may or may not be the final release - they may be test builds that were leaked to testers.
You are right, there isn't any point in doing it other than to be one if the firsts to have the official up update. I'm sure it week be available by download here a day or two after the official is out, but the anticipation is killing me (us).
I am really anxious to see of the battery life is improved, also it would be nice to have all streaming audio problems fixed for good.
@jdmba - exactly!
Sent from my HTC Incredible «•» Rooted/S-off/Skyraider v2.5.2 Vanilla «•» http://www.unrevoked.com/forever
jdmba said:
1) Devs will need time to cook the OTA into a custom ROM, the OTA is ready on impact
2) The OTA does not require reinstalling your apps
3) Some have no problem with Verizon's stock ROMs and wouldn't want it cooked
4) Cooked roms tend to break things when adding and removing and mixing and matching (which is why cooked ROM threads are 99.9999999% bug reports) and some people would rather not have to deal with the extra bugs
5) Cooked roms are really to the taste of the cooker. If they don't like the facebook app, then I guess you won't have the facebook app; and if they like swype, well then you have swype. 1 person cooks, everyone else settles. That is not to everyones taste.
Click to expand...
Click to collapse
they may cook a new version from it, but i can guarantee unrevoked is gonna patch it with root and release it stock, no changes made. just like the leaks, they always released it unmodified besides root. also, if youre rooted and updated on a leak, whether or not the official ota saves all your apps etc. doesnt matter because you have to downgrade, requiring a complete wipe of everything, so theres nothing to save anyway. thats only beneficial if youre still on stock 2.1.
The only real benefit of official ota, is you dont have to wait. hopefully, rooting the official release wont prove to be difficult, then waiting would only be something like a day.
If I root my samsung fascinate... am I able to continuously update to the newer version of Android? Or does it require additional assistance from the good people of XDA? thank you in advance
Most likely will either not accept update or will lose root upon update.
That's what happened last time.
Sent from my SCH-I500 using XDA App
so if new updates from google android comes out, even if I root the phone i can't just go and download the new version?
If all you do is install apparently that require root access, you should be fine. You'll just lose root access, and have to re-root afterward. If, however, you remove factory apps like Bing, or do any other OS modifications like the lag fix, there's a much bigger chance that the official updates will either fail, or cause problems. In that case, you either need to revert to stock before updating, or rely on xda developers to roll out customized versions of the updates that you can apply with your modifications in place.
Sent from my SCH-I500 using XDA App
So, the "official update" from say verizon will not work as well if I remove all the bloat ware... however, a rooted phone will be able to take in updates from Google ANdroid...like 2.3 or 3.3 etc... with no issues?
Perhaps to clarify a little further, I wish to purchase the Fascinate and root it. In the future, as new Android versions come out, I would rather take the official Android versions by Google instead of the updates by Verizon. Much like the Tmobile G1, is this possible once rooted?
I understand this is rather a long post so I appreciate all the help. Thank you.
There are no Google updates vs. OEM updates released through the carriers. All updates are carrier-released, regardless of the source (OEM OR Google), and are model-specific, largely due to OEM OS customizations and differing hardware. The only phones that get pure Google updates OTA (somebody correct me if I'm wrong) are the ones that are released with a 100% stock Android ROM from the factory.
The only OTA updates you will get for the Fascinate will be from Verizon, and will require a stock ROM, and most likely will need all original apps in place. If you want the pure Google updates, you will need to install a custom ROM with those updates.
Sent from my SCH-I500 using XDA App
Oh, and just to clarify, if you install a custom ROM that gives you pure stock Android, you will have to rely on the developer of that ROM to release updated versions that include the latest updates from Google. There are no OTA updates for custom ROMs, as they are not supported by Google, your carrier, or the phone manufacturer.
Sent from my SCH-I500 using XDA App
The only phone that truly gets untouched virgin updates would be the Nexus One, and even then the drivers are added by HTC.
The Moto Droid I guess would be the next one to also, but its been so long since I used a purely stock version that I remember if Moto adds apps at Verizon's request.
All carriers request what features/bloatware to install/not install. They send said requests to OEM, which turns around and incorporates the requests, and adds their custom branding/widgets/etc to send back to the carrier for testing. The carrier then has its own internal testing to verify requests and make sure no new prevalent bugs pop up. No one at Verizon (or any carrier really) actually does any coding of any kind.
What the OEM's receive from Google may be what you consider a "pure ROM" with "hooks" built in so that the various OEM's can add their custom homescreen, bloatware, brand specific widgets, etc. But, with the source being released most likely what happens is that this job now falls upon the OEM's themselves to write in their own "hooks", as Google just pumps out strictly OS generic builds into the ASOP.
In which case, either Sammy or Moto or whoever pulls that and fixes whatever issues, or they have internal builds going (which is more likely) that they tinker with to fix issues.
I believe Moto does this as evidenced by the lettering of the builds. Seems like they go through builds nightly when they are working on an update for a phone. I wouldn't be surprised if Sammy was the same way.
Sorry to make this post so long. Hope this helps.
So, a phone has to be "rooted" to allow full control over the phone. In this mode, I am allowed to make changes to the phone such as downloading ROMS that imitates the basic stock version of say the Froyo 2.2 In the future if a new version arrives, I can expect the upgrade from either Verizon (which I will have to unroot) or hope that the good people of XDA find ways to put new version of the Android in to my already rooted phone.
So, if I have a android phone and if the hardware is popular enough, people will continue finding ways to put new Android versions on the rooted phones through ROM. I hope I am understanding this matter correctly...
If that is the case, I now will go search in the threads for a way to root the Fascinate and find a ROM that lets me have the stock version of Android. I am very satisfied with the great people on this thread and I am very thankful for your responses and patience. Thank you very much.
Yes. You've got it down for the most part. If you root there are methods to unroot that will allow you to download the ota update. But with any luck the devs will get the froyo build long before it gets officially released and will be properly rooted by then.
Sent from my SCH-I500 using XDA App
I am rooting this and it will be my first time. Will I be able to dl official updates with cwm recovery installed as they become available. I'm really only interested in rooting I'm not flashing any roms or anything. If it makes any difference the one I have is for Bell mobility.
Sent from my HTC One S using xda app-developers app
I'm sure it differs from device to device but, so long as you're running the stock ROM, you should get OTA updates but you'll probably have to root again.
Sent from the heart...of darkness!
Sleef said:
I'm sure it differs from device to device but, so long as you're running the stock ROM, you should get OTA updates but you'll probably have to root again.
Sent from the heart...of darkness!
Click to expand...
Click to collapse
Yeah this is correct should some time in the future your ab deodexed rom mods tweaks etc etc and a ota update is rolling simply flash a stock rom and you should have no problems updating if you have problems error screens or force closes then you gotta factory reset
According to this IBT Blog, restoring to stock ROM is mandatory for receiving the upcoming OTA update to 4.2.
Does any one know if this is true, as the last OTA update to 4.1.2 automatically launched and completed just fine on my N7 in its rooted state?
digixmax said:
According to this IBT Blog, restoring to stock ROM is mandatory for receiving the upcoming OTA update to 4.2.
Does any one know if this is true, as the last OTA update to 4.1.2 automatically launched and completed just fine on my N7 in its rooted state?
Click to expand...
Click to collapse
I think you're confusing running the stock rom and being rooted. One can be rooted while still running the stock rom. If this is the case, you should have no problem receiving the OTA update. On the other hand, if you loaded a custom rom (e.g., CyanogenMOD), you won't get the OTA update.
nyijedi said:
I think you're confusing running the stock rom and being rooted. One can be rooted while still running the stock rom. If this is the case, you should have no problem receiving the OTA update. On the other hand, if you loaded a custom rom (e.g., CyanogenMOD), you won't get the OTA update.
Click to expand...
Click to collapse
Am I still able to get the OTA update, if I'm on Stock rooted, but modify the system to have tablet UI?
If not, what will be my option, to update the tablet? I guess manually pushing the Rom might work, but a reassuring would be good
Sent from my Nexus 7 using xda app-developers app
Bcroc said:
Am I still able to get the OTA update, if I'm on Stock rooted, but modify the system to have tablet UI?
If not, what will be my option, to update the tablet? I guess manually pushing the Rom might work, but a reassuring would be good
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I haven't messed around with modifying the UI, but I have replaced and disabled system apps in the past, and that stops the OTA from installing (it will download the OTA, but the install will fail). I suspect it's possible that the same thing will happen with a modified UI, but I'm not 100% sure. What is the process for modifying the UI? Did you replace certain files? If so, hopefully you saved the original versions and can revert back to the originals.
Bcroc said:
Am I still able to get the OTA update, if I'm on Stock rooted, but modify the system to have tablet UI?
If not, what will be my option, to update the tablet? I guess manually pushing the Rom might work, but a reassuring would be good
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Can you keep us updated here if you decide to try and install the OTA update while in tablet UI? i would be interested as well if it will update
Bcroc said:
Am I still able to get the OTA update, if I'm on Stock rooted, but modify the system to have tablet UI?
If not, what will be my option, to update the tablet? I guess manually pushing the Rom might work, but a reassuring would be good
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
If all you did was change the dpi then yes it wont matter your build.prop is going to be overwritten anyways
ontoptherock said:
Can you keep us updated here if you decide to try and install the OTA update while in tablet UI? i would be interested as well if it will update
Click to expand...
Click to collapse
Of course, but I think I will wait the update before doing anything, that's just more convenient
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 07:16 AM ---------- Previous post was at 07:15 AM ----------
nyijedi said:
I haven't messed around with modifying the UI, but I have replaced and disabled system apps in the past, and that stops the OTA from installing (it will download the OTA, but the install will fail). I suspect it's possible that the same thing will happen with a modified UI, but I'm not 100% sure. What is the process for modifying the UI? Did you replace certain files? If so, hopefully you saved the original versions and can revert back to the originals.
Click to expand...
Click to collapse
No, I don't wan to replace anything, only modify the build.prop to have a different density setting.
Sent from my Nexus 7 using xda app-developers app
nyijedi said:
I think you're confusing running the stock rom and being rooted. One can be rooted while still running the stock rom. If this is the case, you should have no problem receiving the OTA update. On the other hand, if you loaded a custom rom (e.g., CyanogenMOD), you won't get the OTA update.
Click to expand...
Click to collapse
I do know the difference between Stock ROM vs. Stock ROM + Rooted -- but I had just read the IBT blog too fast and plus I implicitly assume that folks who use custom ROM would just wait until their particular custom ROM rolls onto 4.2 base, to realize that folks with custom ROM is the target audience of the IBT blog.
So its safe to update via ota if your on stock rooted? Ive seen people saying its fine but on my old atrix I was warned it would brick my device.
jefferson9 said:
So its safe to update via ota if your on stock rooted? Ive seen people saying its fine but on my old atrix I was warned it would brick my device.
Click to expand...
Click to collapse
My N7 went through the last update just fine (other than getting un-rooted).
Hey,
I have a question regarding rooting and upgrading.
Before i root, I would like to know if I do root, how will I upgrade to KLP when it is released for nexus 10?
Do i have to restore?
It depends on the situation. If you root, using a backup app like carbon or titanium backup will ensure anytime you update or change a rom you keep all your goodies. If your root only and don't change your rom you will get the OTA and it will lose root (easy to fix) and your stuff will stay.
Changing your rom is a different story though
Sent from my Nexus 10 using Tapatalk HD
So on stock...
altimax98 said:
It depends on the situation. If you root, using a backup app like carbon or titanium backup will ensure anytime you update or change a rom you keep all your goodies. If your root only and don't change your rom you will get the OTA and it will lose root (easy to fix) and your stuff will stay.
Changing your rom is a different story though
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
I'm on stock, but when klp releases, can i just update ? Would jb> klp be too big of a change that a lot of bugs may arise?
For example, I used to have a rooted nook color, it updated and I got unrooted... There ended up being bugs even after I rerooted it...
I am just wondering is updating then rerooting the correct method...
add12364 said:
I'm on stock, but when klp releases, can i just update ? Would jb> klp be too big of a change that a lot of bugs may arise?
For example, I used to have a rooted nook color, it updated and I got unrooted... There ended up being bugs even after I rerooted it...
I am just wondering is updating then rerooting the correct method...
Click to expand...
Click to collapse
It's stock Google software. I had a Nook Color as well and they tried to block root on it anyway they could. There is no knowing if the upgrade to KLP will be easy (history tells us it will be) and root should be on board almost immediately after release, at the very worst you would have to reroot but that is nothing.
Sent from my Nexus 10 using Tapatalk HD
altimax98 said:
It's stock Google software. I had a Nook Color as well and they tried to block root on it anyway they could. There is no knowing if the upgrade to KLP will be easy (history tells us it will be) and root should be on board almost immediately after release, at the very worst you would have to reroot but that is nothing.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Thanks!
Other question in the same vein:
I have a rooted n10, but I changed the kernel. Will I have to revert to update?
Probably yes, but worth a shot first, atthe kernel question. I'm just going to wait utnil a AOKP KLP comes out, myself.
About Key Lime Pie I read somewhere that KLP will ne only available on quad core devices..
Sent from my GT-I9100 using xda premium
When you are rooted there is no point to updating to a new Android version via OTA. You simply go from the ROM you are on, to installing a new version of the same ROM based on the new Android version. Developers like to keep their ROM updated, so usually you will see all the most popular ROMs updated to the latest and greatest version of Android within a day.
If you try to do OTA then you usually lose root, you often have to re-lock your bootloader, you have ton verify you are on the stock rom AND kernel, and then still hope you are "stock enough" to have the update be successful. That is just way too much work and not worth it at all when the alternative is to just flash a new version of a ROM and be done with it.
EniGmA1987 said:
When you are rooted there is no point to updating to a new Android version via OTA. You simply go from the ROM you are on, to installing a new version of the same ROM based on the new Android version. Developers like to keep their ROM updated, so usually you will see all the most popular ROMs updated to the latest and greatest version of Android within a day.
If you try to do OTA then you usually lose root, you often have to re-lock your bootloader, you have ton verify you are on the stock rom AND kernel, and then still hope you are "stock enough" to have the update be successful. That is just way too much work and not worth it at all when the alternative is to just flash a new version of a ROM and be done with it.
Click to expand...
Click to collapse
It depends if you are stock rooted or on a custom rom...
If you are stock rooted but have Twrp you could do the OTA reboot to recovery and root checker will install super SU for you
If you don't have Twrp... Nexus devices are easy to root anyways
Or use an OTA root keeper app