Related
Hey guys just received my n7 yesterday and am very pleased with this, however I have some questions.
Does rooting (only) removes your OTA updates access? I also own a Galaxy S4 (rooted) and I can't get OTA, it says it's modified, but I did flash a custom update on it and kernel. So if I just root my n7, and not flash anything, I will still get OTA's correct? I just want to use some apps which requires root access and not planning to flash a custom rooms or anything. Thanks for any help.
Sent from my Nexus 7 using Tapatalk 4
Mine is always rooted, and I get all OTAs.
Sent from my Nexus 7 using xda app-developers app
You just need to have the stock recovery to receive OTAs.
Username invalid said:
You just need to have the stock recovery to receive OTAs.
Click to expand...
Click to collapse
So if I have twrp installed, i won't receive them?
Sent from my Nexus 7 using Tapatalk 4
Takes 10 seconds to reflash the stock recovery.
UPDATE: SuperSU-v1.55 added the fix for the OTA update issue, so this post is no longer necessary unless you are using an older version of SuperSU
This post also applies to JSS15Q update.
I actually went through and tested JWR66N rooted with SuperSU and the JSS15J OTA update. I expected it to work but it exited with an error.
Ironically the JSS15J OTA actually did patch every single file successfully but near the end while setting permissions, it came up with an error, so after reboot you'll actually be running with all JSS15J rom files, except your build will still say JWR66N, you'll still be running the JWR66N recovery, and you'll still be running the 3.05 bootloader.
I tracked down the issue and put together a fix for it. If you want, it is attached to this post. You just run it after installing SuperSU, so basically:
adb reboot bootloader
fastboot boot twrp.img
within TWRP
install UPDATE-SuperSU-v1.51.zip (SuperSU v1.55 or greater incorporates the OTA fix)
install UPDATE-SuperSU-v1.55.zip
install UPDATE-SuperSU-ota.zip (can be chain installed, just make sure you choose to install it 2nd)
reboot
You'll need to redo these steps (both the installs) after you receive the OTA to preserve root and ability to receive future OTAs.
Also as others have mentioned it is best to be running stock recovery (which the above commands will allow you to do because twrp is never flashed on the tablet) I've attached the stock recovery for JSS15J in case someone needs it.
If you make ANY modifications or delete files from the stock ROM with your new root privileges, then you will greatly increase the chances of the OTA failing. Adding new files is normally fine.
Well shoot - now you have me worried. I did install TWRP, but never considered that would block OTAs. Do they attempt to install and fail?
Sent from my Nexus 7 using xda app-developers app
rmm200 said:
Well shoot - now you have me worried. I did install TWRP, but never considered that would block OTAs. Do they attempt to install and fail?
Click to expand...
Click to collapse
On some platforms, especially when flashing bootloaders and/or radios, the stock recovery pulls some funky maneuvers to get that done. Often custom recoveries are not privy to those maneuvers. Also sometimes custom recoveries will experiment with custom kernels which don't always have the bootloader and/or radio devices mapped the same as the stock kernel. This can lead to problems to.
Thus it is safest to use stock recovery to flash OTAs.
I have flashed the complete JSS15J OTA except for the bootloader part using TWRP and it works ok. All the ROM files are patched.
I just didn't feel like risking my tablet with the bootloader flash portion of JSS15J OTA using twrp. It might work fine. I just know from the past the potential for issues are higher in that section of the OTA flash.
Is it common for nice folk on here to upload a stock zip of say for example, 4.3.1 when it releases so that we can flash it through a custom recovery (e.g., TWRP, CWM etc.), without having to change our custom recoveries?
It was common on other platforms I've used, but I don't know about here.
Root will not prevent an OTA update from coming in and installing, and a custom recovery won't "block" (it just won't be able to complete the install of it automatically). I have been installing OTA updates on rooted Nexus devices with custom recoveries since the Nexus One, and assuming the new Nexus 7 works the same way, the following applies:
If you are running stock ROM, your deivce will receive the notification and download the update, even if rooted
If you are running stock recovery, the update will install automatically as normal
If you are running a custom recovery like CWM or TWRP, it will fail to install automatically but it will still have downloaded to the device and you can use the custom recovery to install it yourself (I've never had this fail)
If you have modified files in /system, the OTA update is pretty much guaranteed to fail regardless of which recovery you use
If you successfully install the OTA update, you will no longer have root, so flash SuperSU using a custom recovery after the OTA update installs
Also:
You can always look for the OTA zip URLs on XDA and just download the update yourself to flash if you don't want to wait for it to come to your device (this is what I always do)
You can flash factory images instead of the update, without losing data (see other threads for how)
If you want to keep stock recovery installed, you can always use fastboot to boot a custom recovery without flashing it, in case you ever need it
The above is accurate and correct as far as I'm aware from my own experience over the years with Nexus devices. I'm sure someone will be happy to correct me if anything is wrong Hope this helps.
phazerorg said:
Root will not prevent an OTA update from coming in and installing, and a custom recovery won't "block" (it just won't be able to complete the install of it automatically).
Click to expand...
Click to collapse
I thought the same about root not blocking the OTA update install from being successful, but that was with years of using superuser.
With SuperSU (I am not sure which version introduced it) they set the immutable flag on a file in almost every OTA. I believe this is to support some OTA survival mode. This causes the OTA to fail in the section where it sets permissions. All the files are patched at that point, but the build.prop hasn't been modified to reflect the new version # and the bootloader and recovery haven't been flash.
You'll essentially be running JSS15J but your software will report it is on JWR66N, your bootloader wouldn't have been patched, and you would be running JWR66N recovery.
TheAltruistic said:
Is it common for nice folk on here to upload a stock zip of say for example, 4.3.1 when it releases so that we can flash it through a custom recovery (e.g., TWRP, CWM etc.), without having to change our custom recoveries?
Click to expand...
Click to collapse
yes the ota update zip always gets posted so you can manually flash with a custom recovery...
just keep in mind you need to keep your files stock otherwise it might not work
Sent from my Nexus 7 2
nolook said:
yes the ota update zip always gets posted so you can manually flash with a custom recovery...
just keep in mind you need to keep your files stock otherwise it might not work
Sent from my Nexus 7 2
Click to expand...
Click to collapse
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Mightym83 said:
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Click to expand...
Click to collapse
Titanium backup is an app, I assume with files he is targeting e. G. Config files.
Sent from my Nexus 7 (2013)
Mightym83 said:
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Click to expand...
Click to collapse
It means don't modify or delete any files in /system
Don't remove a system app that shipped with the tablet. You can install a new version as that just hides the one in /system, but if you remove or modify the original, then the OTA will very likely fail (depending on how complex the OTA is)
Adding files is ok.
Alright, so here's my scenario. Hopefully someone can tell me what should happen:
I am running the stock ROM on my Nexus 7 (2013), but I have ClockWorkMod Recovery installed and I'm using Koush's Superuser app for root permissions. The only system file that I think I have changed is my hosts file because of Adaway. That is easily reverted, though.
So can I just download the OTA, install it manually from the custom recovery (flashing the update.zip file), and then re-flash Koush's superuser app back onto the device?
Will that go smoothly, and will the newer build number be accurately reflected in my About Phone afterward?
(that last part is just my OCD talking)
phazerorg said:
:
[*]If you are running a custom recovery like CWM or TWRP, it will fail to install automatically but it will still have downloaded to the device and you can use the custom recovery to install it yourself (I've never had this fail)
Click to expand...
Click to collapse
This was very helpful, and this is the category i fall in. However, i have installed a kernel. does that change anything?
So basically what you are saying is this, with my current set up:
1 - i will get the update, it will download, but wont install. I should boot into TWRP and install the file that way. Correct? Where is the downloaded file stores?
2 - I can just wait for the download to be posted on here, and just install via twrp.
3 - either way, after installing it, i will lose root. I should then boot into twrp and flash supersu.
Correct?
Theoretically it could work. I believe the flash has worked with twrp.
Personally I always put stock recovery back to flash ota's though especially if there is a bootloader (or radio if you have a mobile version) because on some platforms they involve special procedures that may not be in the custom recovery.
On nexus it looks like it will work with custom recovery but it takes so little effort to put stock recovery back I just do it automatically.
Having said that, I've seen one person post it worked on twrp but haven't read an experience on cwm. Not saying it will or won't work.
If we are running the stock ROM, but have it rooted with the custom recovery, why cant we just use Wegfresh's nexus toolkit to Unroot and image using the updated IMG file?
Then go through and use it to recreate the root\custom recovery again?
is there away to install SuperSU when you have stock recovery? I'm thinking that we have to have either CWM/TWRP to install the zip. or am I having a brain fart on this.....
Thanks for whomever can clear my cobwebs..
You need a custom recovery (TWRP or CWM).
bkeaver said:
is there away to install SuperSU when you have stock recovery? I'm thinking that we have to have either CWM/TWRP to install the zip. or am I having a brain fart on this.....
Thanks for whomever can clear my cobwebs..
Click to expand...
Click to collapse
You can install it if you have the bootloader unlocked.
Use boot command instead of flash to boot into custom recovery and install su.
e.g
Fastboot boot twrp.img
uronfire said:
You can install it if you have the bootloader unlocked.
Use boot command instead of flash to boot into custom recovery and install su.
e.g
Fastboot boot twrp.img
Click to expand...
Click to collapse
Yes, this.
However, why bother keeping stock recovery at all? Stock recovery is effectively neutered once rooted, as you can no longer install an OTA.
uronfire said:
You can install it if you have the bootloader unlocked.
Use boot command instead of flash to boot into custom recovery and install su.
e.g
Fastboot boot twrp.img
Click to expand...
Click to collapse
Thanks this worked :good:
so when I go into recovery now I get a image of a htc one with a red triangle and exclamation mark inside of it?? since I have never went into recovery on this phone before isn't it supposed to look like any other stock recovery??? and if this isn't right I have tried flashing the recovery already and still get the same result... can someone expand on this for me pls
bkeaver said:
so when I go into recovery now I get a image of a htc one with a red triangle and exclamation mark inside of it?? since I have never went into recovery on this phone before isn't it supposed to look like any other stock recovery??? and if this isn't right I have tried flashing the recovery already and still get the same result... can someone expand on this for me pls
Click to expand...
Click to collapse
You have stock recovery.
BenPope said:
You have stock recovery.
Click to expand...
Click to collapse
so it doesn't give you flash update and wipe and all that anymore.. sorry like I said I have never went into recovery on this phone.. just making sure...
bkeaver said:
so it doesn't give you flash update and wipe and all that anymore.. sorry like I said I have never went into recovery on this phone.. just making sure...
Click to expand...
Click to collapse
I think you have to hold volume up and hit power or something.
ok I am good.. thank you... I'm putting everything back to stock because someone bought my phone and I just want to make sure everything is correct on it now.. thanks!!
redpoint73 said:
Yes, this.
However, why bother keeping stock recovery at all? Stock recovery is effectively neutered once rooted, as you can no longer install an OTA.
Click to expand...
Click to collapse
i sold the phone and this is what they requested. I know the OTA wont work and I never keep stock recoveries on my phones but.... I guess they will find out for themselves
and btw thanks everyone for the help. I hit my thanks button but on my browser it it isn't showing it just to let you know....
bkeaver said:
i sold the phone and this is what they requested. I know the OTA wont work and I never keep stock recoveries on my phones but.... I guess they will find out for themselves
Click to expand...
Click to collapse
Sounds like somebody that is a bit ill-informed. They want root, but they probably also want OTA (the 2 don't go together, IMO) and heard that you need stock recovery for OTA. I suppose they can change everything back that they modified with root, and unroot or hide root to install the OTA. But it just seems they are making life more complicated than it needs to be.
Also sounds like its a person that wants root, but not willing to do it themselves. But I suppose that's not really your problem!
Option to root and have ota is very easy :
Stock rom (unmodified but rooted)
Stock recovery
And you can ota. The ota will probably delete superuser but that's about it. The ota will not fail because its rooted as long as the stock rom/apps are unmodified
Mr Hofs said:
Option to root and have ota is very easy :
Stock rom (unmodified but rooted)
Stock recovery
And you can ota. The ota will probably delete superuser but that's about it. The ota will not fail because its rooted as long as the stock rom/apps are unmodified
Click to expand...
Click to collapse
yeah this is what I did for them so who knows.. I've never tried it that way but i guess it would work like that
redpoint73 said:
Yes, this.
However, why bother keeping stock recovery at all? Stock recovery is effectively neutered once rooted, as you can no longer install an OTA.
Click to expand...
Click to collapse
Rooting doesn't affect ota's, at least not in my experience.
ashyx said:
Rooting doesn't affect ota's, at least not in my experience.
Click to expand...
Click to collapse
Only if absolutely nothing was changed with the stock ROM.
Its more my point there is little point to installing OTAs on a rooted device.
redpoint73 said:
Only if absolutely nothing was changed with the stock ROM.
Its more my point there is little point to installing OTAs on a rooted device.
Click to expand...
Click to collapse
I don't understand that statement. I still run stock sense, but with a few additions that don't affect ota's. So I still get updates while having things configured the way I want. I can also run things that require root such as titanium backup and a few others.
ashyx said:
I don't understand that statement. I still run stock sense, but with a few additions that don't affect ota's. So I still get updates while having things configured the way I want. I can also run things that require root such as titanium backup and a few others.
Click to expand...
Click to collapse
Because once you accept an OTA, you will be unrooted. You will have to root again, either by installing custom recovery (than back to stock recovery so you can OTA) or the trick of booting custom recovery via adb to flash SU (as described here). Its just a lot of jumping through hoops with little added value.
On the other hand, if you have custom recovery installed, you can flash any of the array of stock rooted or awesome custom ROMs posted here. This includes stock rooted ROMs taken from OTA updates from lots of versions (often posted within days of the OTA starting to roll out), not just your carrier, so you can possibly get an update much faster than waiting for the OTA to roll out from your carrier (although that depends on what carrier version you have). You also don't have to constantly be worried "well, if I change this I won't get OTAs". You can do whatever the heck you want, and isn't that really the whole point of root?
Its just my opinion. And a lot of this may stem from the fact that I'm on AT&T, who are not only agonizingly slow about rolling out OTAs (sometimes 3-4 months or even later than other carriers on my past HTC device) and have even went to the effort to close exploits and prevent unlocking of bootloaders when rolling out new OTAs (on the One X EVITA). In fact there was even a bug (I assume it was a bug - others may accuse that it was intentional) where installing the Jellybean OTA with SuperCID and S-on bricked the phone.
As I said, its just an opinion. But there are many others on XDA that will agree that OTAs have no place on rooted Android devices.
And to be fair, I did cover myself and stated "there is little point" instead of "there is no point"
One or two days ago I received an ota notification. Every time I try installing the small update, the tablet boots into TWRP, and I don't know what to do next. Why does it not simply install? The nexus 7 is rooted with an unlocked boot loader. Can anyone give me a tip on how to get the update installed?
Snowby123 said:
One or two days ago I received an ota notification. Every time I try installing the small update, the tablet boots into TWRP, and I don't know what to do next. Why does it not simply install? The nexus 7 is rooted with an unlocked boot loader. Can anyone give me a tip on how to get the update installed?
Click to expand...
Click to collapse
With 5.1.1 if the system is altered such as rooting or putting a custom recovery on the device, the update won't install. You have to go back to Pure stock to receive and install updates over the air.
Batfink33 said:
With 5.1.1 if the system is altered such as rooting or putting a custom recovery on the device, the update won't install. You have to go back to Pure stock to receive and install updates over the air.
Click to expand...
Click to collapse
Thank you very much! I am glad that some one had an explanation!
How can I restore to stock recovery for LMY48L? There is no LMY48L factory image, so I can't just extract the recovery out of there. Is there any way I can manually apply the LMY48L OTA's recovery to the recovery image in the LMY47V factory image to get a "stock" LMY48L recovery?b
EDIT: Never mind, it looks very complicated. I ended up just flashing LMY47V recovery and system images, then re-updating to LMY48L, then finally updating to LMY48P. I didn't mean to hijack the OP's thread, but I asked here because it looked like he would run into the same issue as I did.
I have unlocked my bootloader, I have gone through the process of installing TWRP RC1, I have also installed SU 2.79 as guides have shown to do. I have also installed adaway after rooting, as well as titanium backup.
What is left to do now? I have read that if I stay on stock but rooted, when a security update comes out next month and I take it, my device turns into brickmode. I don't intend to stay on stock, I am taking the time to learn all the ins and outs of each rom that exists currently and trying to make a decision which one I like best, and especially what kind of challenging process exists for flashing the rom as well as putting TWRP back on then SU, and the confusing part about doing the vendor image. So yea, still learning. The last time I rooted and flashed anything was LGG3 days, so it's a learning curve again.
Am I supposed to be using a flash drive for anything? Or is that not needed if following the installation process for whatever rom is out there.
Thanks in advance, everyone has been very helpful so far.
There is no need for a flash drive. You can easily disable OTA on stock, and there is no need for a custom rom. In fact, I am rooted on stock. Also, the OTA should not be able to go through while rooted but I have seen myself that it does work surprisingly. My guess is this is because of the dual partitions, but no, you will not get bricked if you accept an OTA. The worst that would happen is that you would lose root. I'm guessing this is due to the dual slots. The OTA overwrites the other slot and swaps it on reboot. You should be able to just get in again but without root.
And if it does fail you can download the full OTA from google and install it with TWRP or adb install it.
Turn off updates in dev options. A couple of people have gotten hit with big data bills from it downloading over and over.
I'm unlocked but not rooted. I installed Franko kernel but need to be rooted to use his app. I'm trying to figure out root yet stay stock for now.
Sent from my Pixel XL using Tapatalk
b4u2 said:
I'm unlocked but not rooted. I installed Franko kernel but need to be rooted to use his app. I'm trying to figure out root yet stay stock for now.
Click to expand...
Click to collapse
So you want to root it now so you can use his app? Second to the last post in the thread below.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242/page2
TonikJDK said:
So you want to root it now so you can use his app? Second to the last post in the thread below.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242/page2
Click to expand...
Click to collapse
Yes and thank you very much!
I'm planning on rooting my Moto Z Play but staying on the stock ROM as it has better battery life (according to XDA members) compared to LineageOS. I also really like Moto Display and all of the other exclusive features to this ROM.
However, I still want to receive OTAs after doing so. I've read that an app called FlashFire can help me with this.
Question 1: Do the OTAs download even if your system is rooted? I've read that some phones do download the OTAs, but fail when the flashing starts as they have a custom recovery, while some phones don't even download at all once it detects that you're rooted.
Question 2: Will it work even if I have TWRP installed?
Thank you.
Hi i dont think you can receive OTAs after unlocking bootloader and iff you do they will fail on installation as you have said. Secondly in my opinion you are right and i have tried almost all the roms on here and by far the stock N is the best rom for fluidity battery life app compatibility etc so i went back to stock but the deodexed N debloated version because im rooted. Iff i were you i would not root at this time because i think Official Oreo is about to be released for our phone and it would be a good idea to hangon a while but that is entirely your choice.
djdelarosa25 said:
However, I still want to receive OTAs after doing so. I've read that an app called FlashFire can help me with this.
Click to expand...
Click to collapse
Never really tested Flashify and FlashFire. If you succeed please write how it works, which steps to do to be on the safe side
djdelarosa25 said:
Question 1: Do the OTAs download even if your system is rooted? I've read that some phones do download the OTAs, but fail when the flashing starts as they have a custom recovery, while some phones don't even download at all once it detects that you're rooted.
Click to expand...
Click to collapse
Download fine. Install fails, yes.
djdelarosa25 said:
Question 2: Will it work even if I have TWRP installed?
Click to expand...
Click to collapse
No. That's why I never install twrp, I just boot it when needed. You need a computer and a cable every time you want to start twrp, but recovery partition stays untouched using fastboot boot.
Idea is:
1. Take a backup of boot partition before rooting
2. Install the kernel you need to avoid f2fs problems, then Magisk. Both modifies the boot partition, nothing else.
When an OTA arrives, you restore your backup of boot partition and everything is stock. OTA is supposed to work fine.
In theory, if I just run TWRP off from the PC and flash SuperSU on my phone without flashing TWRP, I would be rooted, right? And the OTAs would install, but I will lose root access?
djdelarosa25 said:
And the OTAs would install, but I will lose root access?
Click to expand...
Click to collapse
No. SuperSU modifies boot partition. OTA do not install while boot partition is modified.
You need to restore NANDROID backup of original stock boot partition prior to rooting, then you should be fine for install OTA.
---------- Post added at 11:45 ---------- Previous post was at 11:29 ----------
Just an additional hint: Modifying logo also prevents OTA. If you suppress that unlocked bootloader warning with a different logo, of course you need to restore the original logo partition before applying OTA.
tag68 said:
No. SuperSU modifies boot partition. OTA do not install while boot partition is modified.
You need to restore NANDROID backup of original stock boot partition prior to rooting, then you should be fine for install OTA.
Just an additional hint: Modifying logo also prevents OTA. If you suppress that unlocked bootloader warning with a different logo, of course you need to restore the original logo partition before applying OTA.
Click to expand...
Click to collapse
That's a pity. Oh well, I might just have to wait for Oreo.
Thanks a lot!
"'Just an additional hint: Modifying logo also prevents OTA"
Actually...not my experience. I have an unlocked bootloader, flashed a stock rom file by file, except for logo.bin, which is a modded one to get rid of the annoying "untrustworthy" startup screen.
All worked well and recently got the OTA update all installed as normal by the system.
Will wait now to get the official oreo update before i muck around further.
Actually, on the 22-2-8 build on the phone now it runs really well and battery life is great. Getting over 2 days in my usage pattern easy.
Camera good as well. Got some nice photos of the local beach last night.
You can get back to stock, and get ota's
https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190
Note: Lock of Bootloader is not required to get OTA update. It makes sure that you do no action which prevents OTA, but if you take care this does not happen (for instance not rooting which modifies system or boot partition), you eg can take advantage of Nandroid backup only booting TWRP for this purpose.