Related
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).
Basically is this possible, to go from 4.2 to 4.1.2? Mine is fine but my friend's Nexus 7 keeps shutting down.
Will a factory reset restore 4.1.2? Is there another way? Been googling for an hour, & I'm thinking it mustn't be possible with unrooted devices.
Thanks for any help
Mrs Hedgehog
P.S Please don't yell.
Not that I am aware of--I think you'll need to unlock the boot loader to then push the 4.1.2 image to it, but don't worry, its pretty straightforward with a little reading. Check the stickies for guides.
did the move to 4.2 occur via ota update?
Sent from my Nexus 7 using xda app-developers app
kboya said:
Not that I am aware of--I think you'll need to unlock the boot loader to then push the 4.1.2 image to it, but don't worry, its pretty straightforward with a little reading. Check the stickies for guides.
did the move to 4.2 occur via ota update?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes it was via OTA update. Bottom, she isn't going to want to unlock her device. Is there no way to put it back to how it was when she pulled it out of the box brand new? Even if she loses everything she would prefer that.
P.S Thanks for answering, appreciated.
Maybe she needs to think again. You can relock it as if nothing had happened!
Sent from my Nexus 7 using xda app-developers app
Ok would Google know if she did that. Would it be like it was when she first got it? Say if she had to send it back under the guarantee? I'm shocked actually. I thought a factory reset would take it back to basics. I don't think she'll agree somehow.
Nope, it is like nothing ever happened. No-one shall know (nor care,quite frankly).
Factory reset is more like delete data and settings (and also all your photos etc, if you choose SD card) and return to factory state (I.e. the base OS, which is now 4.2 after the update). It does not roll back to the original OS from the factory, which could be several iterations back.
Sent from my Nexus 7 using xda app-developers app
Wug's Nexus Root Toolkit is what you need.
Unlock, flash back to stock 4.1.2 and then re-lock.
Spannaa said:
Wug's Nexus Root Toolkit is what you need.
Unlock, flash back to stock 4.1.2 and then re-lock.
Click to expand...
Click to collapse
Think I may just do this. But, will it keep trying to force the update on me?
Sent from my Nexus 7 using xda app-developers app
tu3218 said:
Think I may just do this. But, will it keep trying to force the update on me?
Click to expand...
Click to collapse
It's Google that pushes the updates.
I've had no problems with 4.2 but if I do, I'll roll back to 4.1.2 and wait...
Spannaa said:
It's Google that pushes the updates.
I've had no problems with 4.2 but if I do, I'll roll back to 4.1.2 and wait...
Click to expand...
Click to collapse
So I'd still get the notification to update to 4.2 if I reverted back.
But yeah, 4.2 isn't that bad. I do notice some unresponsiveness when clicking icons but other than that, pretty good.
Sent from my SCH-I535 using xda app-developers app
Install the FOTAKill app to stop OTA Notifications
tu3218 said:
Think I may just do this. But, will it keep trying to force the update on me?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I had to roll back to 4.1.2 on my Nexus 7. The tablet would not charge (didn't recognize the high-current charger) under 4.2. To stop the update notifications I installed FOTAKill (tablet must be rooted). .doc file with FOTAKill installation instructions is attached.
Really wish that Google would have an option for "Never" when it asks for permission to install an update.
Spannaa said:
Wug's Nexus Root Toolkit is what you need.
Unlock, flash back to stock 4.1.2 and then re-lock.
Click to expand...
Click to collapse
Hi, I have a question, If I flash back to stock with Wug's toolkit would I receive the 4.1.2 update OTA or would I have to flash it manually?
Sent from my Nexus 7 using XDA Premium HD app
Cee_Pee_Three said:
Hi, I have a question, If I flash back to stock with Wug's toolkit would I receive the 4.1.2 update OTA or would I have to flash it manually?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
If "stock" is before 4.1.2 then yes, you'd get the OTA update notification (which would unroot the tablet. You might as well manually flash 4.1.2.
My Nexus 7 "bricked" when I allowed the update from 4.1.2 to 4.2, requiring a complicated procedure to unbrick it. I suspect that the problem was caused by a "rootkeeper" app.
SMS888 said:
If "stock" is before 4.1.2 then yes, you'd get the OTA update notification (which would unroot the tablet. You might as well manually flash 4.1.2.
My Nexus 7 "bricked" when I allowed the update from 4.1.2 to 4.2, requiring a complicated procedure to unbrick it. I suspect that the problem was caused by a "rootkeeper" app.
Click to expand...
Click to collapse
I wrote that wrong, I meant if I'm on 4.2 and flash back to the 4.1 original that first came with the device, would the 4.1.2 update come up OTA or would I have to flash 4.1.2 manually?
Sent from my Nexus 7 using XDA Premium HD app
I think you have to update manually. OTA will offer 4.2.
telexer said:
I think you have to update manually. OTA will offer 4.2.
Click to expand...
Click to collapse
Correct. The FOTA update would offer only the latest version.
On my new Nexus two separate updates were sent in sequence. First an update to 4.1.2 then another update (declined) to 4.2 a few minutes later. It was not a single update from 4.1.1 to 4.2.
Thank u for sharing this info, this saves me the trouble from updating to 4.1.2 manually.
UPDATE: So I went back to the initial ROM the device came with (JB 4.1.1) and Google quickly prompted to update to 4.1.2 (which is what I wanted) and now it asks me to update to 4.2 but I ignore that
Long story short, my Nexus 7 is back up and working flawlessly again!!
Sent from my Nexus 7 using XDA Premium HD app
SMS888 said:
I had to roll back to 4.1.2 on my Nexus 7. The tablet would not charge (didn't recognize the high-current charger) under 4.2. To stop the update notifications I installed FOTAKill (tablet must be rooted). .doc file with FOTAKill installation instructions is attached.
Really wish that Google would have an option for "Never" when it asks for permission to install an update.
Click to expand...
Click to collapse
What if I want to update my Nexus 7 later, how do I take off the fotakill.apk?
Sent from my Nexus 7 using XDA Premium HD app
4.2..> 4.1.2 Without rooting
Have Nexus 7, stock, has been upgraded OTA to 4.2.1. Have an $80 app (Anywhere Map) which company is working on a fix to operate with 4.2. I use Linux and it appears you can upgrade manually with 'adb reboot recovery' then Power & Vol to get recovery menu. Posts have said simply use 'adb sidload upgrade_img.zip' or 'adb install upgrade_img.zip'. Simple enough. I've only gotten to the menu from which I can choose 'apply update from adb', but have done nothing. Posts have said simply issue the command and select reboot from menu after it installs. This should install new os version without removing apps nor sdcard info. (I have backed up the whole sdcard with 'adb pull' to my computer.)
I have 4.1.2, 4.2, and 4.2.1 images. What I would like to do is put the 4.1.2 on to use until Anywhere Map gets their act together for 4.2. But 4.1.2 seems like a minor update to 4.1 and I can't find that image at Google nor anywhere else.
So the question is as to whether updating with the 4.1.2 image will work or not. I have the material to root the machine manually but would prefer not to do it. This all looks rather straightforward from the many posts I've read, except with my reservations on the 4.1.2 update. Thanks for any comments.
Im getting a Nexus 7 for christmas and im wondering if i decide to root the nexus 7 is it possible to go back to stock as its not amobile phone i cant think it would be to hard because i love the stock jelly bean 4.2 system but im wanting paranoid rom so i can get table ui on the nexus 7 but if i dont like it can i just go back to the stcok jelly bean rom?? (nexus 7 has been bought from offical google website)
Thanks Guys
George
Why would you not like it...its stock plus so many more options.
Sent from my Nexus 7 using xda app-developers app
Yes.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
dparrothead1 said:
Yes.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
Well all im thinking is if the a new OTA update comes out or say for example Vinilla co co pops 5.2 comes out how the hell am i surposed to update to that like at the moment i have a htc oxe x and upateing to jelly bean just not even possible im just worryed that i wont be able to keep updateing when the ota's come out thas all im wanting to know if i root it and put custom roms on it i want to make 100% sure i can update it to the latest firmwere when they officaly come out
Check this thread:
http://forum.xda-developers.com/showthread.php?p=35472344#post35472344
dannymassacre said:
Well all im thinking is if the a new OTA update comes out or say for example Vinilla co co pops 5.2 comes out how the hell am i surposed to update to that like at the moment i have a htc oxe x and upateing to jelly bean just not even possible im just worryed that i wont be able to keep updateing when the ota's come out thas all im wanting to know if i root it and put custom roms on it i want to make 100% sure i can update it to the latest firmwere when they officaly come out
Click to expand...
Click to collapse
This doesn't even matter, all the devs have the official ota update before it comes out due to Google dropping the source before they actually push it out.
Way better to root, you'll have the updates faster that way.
Sent from my Nexus 7
IF you do only one thing, unlock the bootloader before getting lived in on the device. I am rocking stock rooted myself. I am just watching till after cm10.1 hits stable then Ill try some roms out
While I personally prefer stock (with modifications of course) on my N7, it is trivial to revert these devices back to stock, or any other ROM, if you want to. You don't even need to revert and upgrade - you could just download the latest FULL image and flash your device that way, skipping the update step altogether.
But if updates are your only concern, I imagine most of the ROM developers would incorporate the new version into their ROMs very soon after the OTA drops.
BrianDigital said:
IF you do only one thing, unlock the bootloader before getting lived in on the device. I am rocking stock rooted myself. I am just watching till after cm10.1 hits stable then Ill try some roms out
Click to expand...
Click to collapse
This.
Even if you don't run a custom rom initially, if the bootloader is unlocked, you can easily flash a custom recovery and rom later. The problem is that if you unlock all the internal storage gets wiped which is not the end of the world if you backup first but it's still a minor inconvenience.
Sent from my Nexus 7 using Tapatalk 2
paranoid is great, but depends what you like. I love it fit the tablet interface and customization options. stock 4.2 had a lot of the same customization built in, so it's awesome as well.
Sent from my Nexus 7
To me, its custom ROM or bust.
-Sent from Marino's Nexus 7-
Multi ROM
you may want to use Multi ROM.
Root your stock ROM.
Install Custom Recovery to install Multi ROM.
After installing Multi ROM, you may now install other or more ROMs inside.
Also, you have the option to auto-boot from stock ROM or from other ROM.
With that, you may access your stock ROM without removing your custom ROMs and vice versa.
Goodluck!
I unlocked and rooted my nexus 7 so that I could use otg cable---> a flash drive … I have extra storage now. Just download an app called stick mount an your all set...
Rooting should be the first thing you should do. As others said you can keep it stock if you want. Only difference is you get to install apps like titanium backup and file managers like root explorer. You also will have a custom recovery so you can backup your latest STABLE and smooth ROM so you can revert back if you ever run into trouble like the 4.2 OTA debacle.
As far as any maintenance and fixing issues... having root makes it a breeze as factory resets just mean in 10 minutes you are back in businesses, you just need redo your screens.
I took the plunge and after rooting I installed this: [EXPERIMENTAL] MultiROM v3
Now I'm running stock along with a few other ROMS, including Ubuntu.
Hello TPT community,
I Just got this tablet mainly because of the included digitizer and was wondering if anyone could give me a guideline on how to speed things up for this tablet. The tablet came with honeycomb 3.1 included and I am finding it pretty sluggish and unresponsive in general tasks. I went into settings to do a software update but it seems there is no 4.0 update available. There doesn't seem to be a toggle for pen only input in the settings either. Is the normal process for flashing a new Rom to root, then install CWM, and flash Roms?
I'm kind of a n00b here, but that is the right process in general.
For you, there should be a 4.0 update, but you might have to try a few times. After you are running ICS (4.0) you can root and load Koshu's JB rom.
Aren't there problems with rooting ICS?
Sent from my ThinkPad Tablet using xda app-developers app
Absolutely no problms rooting ics
Sent from my Micromax A50
Okay well I went into settings, about tablet, system updates, check for updates. It always says "your system is up to date" even though I know I'm on 3.1
Sent from my ThinkPad Tablet using xda app-developers app
Lets see if we can figure out why it won't update. In settings -> about tablet, what is listed for model number, android version, and kernel version?
Edit:
Found this - http://forums.lenovo.com/t5/ThinkPa...ystem-updates-OTAs-not-installing/ta-p/713571
It might help... I'm also searching for a manual download for ota3 or ota 3.5 from lenovo that you can load in recovery.
Edit 2:
Sorry, I need more coffee...
Is this a wifi only tablet or a 3g tablet? What region is it?
I attached the info in a picture. I dont know how to find out what region or wifi/3g it is though. I don't have a sim to test it. I got it from here: http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=7473177&CatId=6845
It is wifi only, also found this interesting thread - http://forums.lenovo.com/t5/ThinkPad-slate-tablets/thinkpad-1839-update/td-p/975085
Apparently the Tiger Direct refurb is a custom SKU and is SUPPOSEDLY not upgradeable... tho I would think there are ways around that. At least now I know what we are working with here.
da_reeseboy said:
It is wifi only, also found this interesting thread - http://forums.lenovo.com/t5/ThinkPad-slate-tablets/thinkpad-1839-update/td-p/975085
Apparently the Tiger Direct refurb is a custom SKU and is SUPPOSEDLY not upgradeable... tho I would think there are ways around that. At least now I know what we are working with here.
Click to expand...
Click to collapse
So any ideas on how to update to ICS? The ROM in android development section says it requires me to have ICS first.
Unfortunately no... sorry. I'm still a n00b with android devices. Maybe someone with a little more knowledge will chime in now that we know what we are dealing with.
You can root your tablet and go straight to Jelly Bean 4.1.1 or 4.1.2. It's fast and cool! The only little bug is with wifi!
Gesendet von meinem CM10 0.8.1 overclocked Jelly Bean 4.1.1 Thinkpadtablet
troemer said:
You can root your tablet and go straight to Jelly Bean 4.1.1 or 4.1.2. It's fast and cool! The only little bug is with wifi!
Gesendet von meinem CM10 0.8.1 overclocked Jelly Bean 4.1.1 Thinkpadtablet
Click to expand...
Click to collapse
A wifi bug is pretty big. The only connectivity mine has is wifi
I tried to install the adb drivers so I can root it but it says the driver has been tampered with so I can't install. I am on windows 8
Sent from my ThinkPad Tablet using xda app-developers app
@troemer: Not sure if you noticed it or not, but in Koshu's cm10 thread it says:
Requirements
This build uses the Lenovo ICS kernel, you need to upgrade to stock ICS first (Make sure you keep root!)
Click to expand...
Click to collapse
This is why he is trying to get the ICS update.
Daedalus_ said:
A wifi bug is pretty big. The only connectivity mine has is wifi
I tried to install the adb drivers so I can root it but it says the driver has been tampered with so I can't install. I am on windows 8
Sent from my ThinkPad Tablet using xda app-developers app
Click to expand...
Click to collapse
The wifi bug actually isn't that big, just set wifi to always on like suggested. As far as the tampered drivers error, you will probably have to : a) search for a way to install unsigned drivers on win8
or b) use a winxp/win7 pc.
Be careful tho... flashing after having stock ICS is needed for a reason.
Flashing what?
Daedalus_ said:
Flashing what?
Click to expand...
Click to collapse
Based on this:
Daedalus_ said:
A wifi bug is pretty big. The only connectivity mine has is wifi
Click to expand...
Click to collapse
I was worried you were gonna try to just jump straight to JB.
Hey there,
well one way is to try flashing the upgrade directly but like da_reeseboy already mentioned, there is a high possibility that it will fail. Only other way would be to flash the bootloader directly (that most likely the part, that keeps the JB kernel from booting on non ICS kernels) but there is a high bricking chance and eventually the firmware for some of the hardware needs to be updated, too, to work properly.
It looks like there's hope - this guy has the same weird software version as you - http://forum.xda-developers.com/showpost.php?p=37487649&postcount=6. He used the directions in that thread to upgrade to ICS.
Edit -
Full thread: http://forum.xda-developers.com/showthread.php?p=37487649#post37487649
Koshu said:
Hey there,
well one way is to try flashing the upgrade directly but like da_reeseboy already mentioned, there is a high possibility that it will fail. Only other way would be to flash the bootloader directly (that most likely the part, that keeps the JB kernel from booting on non ICS kernels) but there is a high bricking chance and eventually the firmware for some of the hardware needs to be updated, too, to work properly.
Click to expand...
Click to collapse
Just trying to think outside the box (noob style), what if he:
1. Installed CWM
2. Restored a clean 0075 nandroid from someone here on xda
3. Restored stock recovery
4. Checked for OTA to ICS
In my mind the software version is what is holding him back from updates, so I'm thinking that restoring an 0075 nandroid will put him in a position to get the update correctly... but I am still new to this so I could be WAY off.
da_reeseboy said:
Just trying to think outside the box (noob style), what if he:
1. Installed CWM
2. Restored a clean 0075 nandroid from someone here on xda
3. Restored stock recovery
4. Checked for OTA to ICS
In my mind the software version is what is holding him back from updates, so I'm thinking that restoring an 0075 nandroid will put him in a position to get the update correctly... but I am still new to this so I could be WAY off.
Click to expand...
Click to collapse
Thanks for still helping! Do I need a special CWM? I just root and install CWM from the market? Honeycomb is really annoying because some apps I use are only for newer androids such as Hulu plus.
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