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?
Noticed a new build was released for OTA. Doing a little research I discovered it won't work while rooted.
Question being, what's the easiest way to update? Temporarily run custom recovery and flash it? I don't want to loss root access or any data. If needed I'll re-root again, but rather not.
Sent from my Nexus 7 using xda app-developers app
datallboy said:
Noticed a new build was released for OTA. Doing a little research I discovered it won't work while rooted.
Question being, what's the easiest way to update? Temporarily run custom recovery and flash it? I don't want to loss root access or any data. If needed I'll re-root again, but rather not.
Click to expand...
Click to collapse
There are many ways to accomplish the same end goal.
You can actually install the OTA while rooted. Just need to run the small fix in this post:
http://forum.xda-developers.com/showthread.php?p=44597339#post44597339
Rerooting on this device is super simple.
There are also other options like flashing the factory images or one of the pre-rooted odexed/deodexed repackaged mostly stock ROMs. You can find them described here:
http://forum.xda-developers.com/showthread.php?t=2415497
So just temporarily run custom recovery then flash the update? but where can I download the latest OTA update?
Sent from my Nexus 7 using xda app-developers app
datallboy said:
So just temporarily run custom recovery then flash the update? but where can I download the latest OTA update?
Click to expand...
Click to collapse
You need to run the fix I mentioned above OR unroot BEFORE installing the OTA or the OTA will fail near the end.
You can find the OTA here:
http://forum.xda-developers.com/showthread.php?t=2415497
Don't quite understand the post, so better to just hold off on an attempt.. Would using the unroot option in SuperSU, allowing the OTA update to go through, then rerooting work fine without deleting data?
I'm know more about Nook Tablet than Nexus 7, didn't care what I did to my Nook because I could fix it. I'm more cautious with this.
Sent from my Nexus 7 using xda app-developers app
Super-Su unroot never help you if you delete something in the /system directory
1)you must flash fix after root
2)do not flash permanent custom recovery and relock bootloader (if your bricked you devices you can send to Warranty Service)
3)replace backup of /system directory before update
and after update clean Dalvik Cache before flash Root again (if superuser privilegies still anavalable for you)
Understand the fix now. Noticed the update went through, but got an error when it finished. Flash ota update in temporary recovery. Correct?
Sent from my Nexus 7 using xda app-developers app
I just downloaded the OTA to the device, unrooted, installed the OTA in TWRP, and then the latest superSU zip (still in recovery). Reboot and voila.
datallboy said:
I'm know more about Nook Tablet than Nexus 7, didn't care what I did to my Nook because I could fix it. I'm more cautious with this.
Click to expand...
Click to collapse
This is a Nexus device. There's almost no way to hard-brick it. Worst case, reboot into bootloader, and fastboot push the stock images.
The fix worked, and I'm still rooted. with all data. Temporarily booted into TWRP, flashed the fix and forced OTA update. Thank you!
ripelli part
Don't fear the ota update. There were no negative effects on my rom or kernel.
-cleanROM1.3
- 3.4.0 ElementalX1.1+
sfreemanoh said:
This is a Nexus device. There's almost no way to hard-brick it. Worst case, reboot into bootloader, and fastboot push the stock images.
Click to expand...
Click to collapse
LOL if you flash STOCK and then bootloader - you will get bootloop hardbrick without FASTBOOT and ADB !!! (only APX)
(my nexus 7 1 gen in this situation)
------------------------------------------------------
why you try new customs rom, when in few weeks would be android 5.0 ?
sambistt said:
LOL if you flash STOCK and then bootloader - you will get bootloop hardbrick without FASTBOOT and ADB !!! (only APX)
(my nexus 7 1 gen in this situation)
------------------------------------------------------
why you try new customs rom, when in few weeks would be android 5.0 ?
Click to expand...
Click to collapse
I'm not sure what you're saying in reference to my earlier comment...are you saying something I said was incorrect?
Hello
I've rooted my Nexus 5X and i left the recovery to stock recovery because i wanted to have the OTA updates normally without using a PC.
With ytsemless root I was hoping that this is no problem. But the febuary security OTA fails when I try to install.
Can someone explain to me why this could fail?
I have not much root apps installed. Just adaway, busybox, sd maid and supersu. No costum kernel.
So from my point of view I touched nothing that should have an impact to OTA.
So my question is: Why is there always an error when I try to update with OTA?
ChenZ86 said:
Hello
I've rooted my Nexus 5X and i left the recovery to stock recovery because i wanted to have the OTA updates normally without using a PC.
With ytsemless root I was hoping that this is no problem. But the febuary security OTA fails when I try to install.
Can someone explain to me why this could fail?
I have not much root apps installed. Just adaway, busybox, sd maid and supersu. No costum kernel.
So from my point of view I touched nothing that should have an impact to OTA.
So my question is: Why is there always an error when I try to update with OTA?
Click to expand...
Click to collapse
Because you have applied systemless root. Anything, ANYTHING different from completely stock will cause the normal OTA process to fail. These posts keep asking the same question and the answer never changes. It is what it is. There are a ton of posts here which will explain alternate flashing processes to update, then re-root your device.
Try using flashfire from Chainfire. It detects downloaded ota and ask you if you want to try and flash it. Also there is an option to re-root after updating. If the ota doesn't install then download the factory image for February and flash the whole thing. Make sure data is uncheked so that it doesn't wipe your data. It's a bigger download than ota but it will definitely work.
I had stock + root + xposed + layers. Managed to update to latest build with automatic re-root. Then I just flashed twrp-recovery using flashify and installed xposed through twrp. Took me 5 mins to flash everything (excluding time to download the factory image). All without using a PC!
Skickat från min Nexus 5X via Tapatalk
this all seems like a hassle compared to using a near-stock custom rom and updating it yourself.
2x4 said:
this all seems like a hassle compared to using a near-stock custom rom and updating it yourself.
Click to expand...
Click to collapse
[emoji106] Or even stock rom.
Sent from my Nexus 9 using Tapatalk
I downloaded Chainfire's Flashfire app now that it is live on the Play Store. I had been updating firmware as separate files (system.img, vendor.img, boot.img all separately) using fastboot and may continue to do so at the monthly updates, but I wanted to check and see if anyone reported any problems or successes using the app.
My N5X is unlocked and rooted, running stock firmware with the exception of a custom recovery (TWRP) and custom kernel (ElementalX).
Here is my question: Would the process of updating via FlashFire be to let it install the new firmware once binaries are released, keep root, and just flash the kernel and other zips (like AdAway, Viper4Android) once it's done?
Just trying to get some advice on whether FlashFire is that much more convenient than just using fastboot and flashing firmware manually. Any experiential responses would be appreciated.
When an update comes out just sideload the ota in recovery. Twrp works as well as stock. You'll get the latest firmware and you don't lose data. Download the ota from the same site as the factory image are, https://developers.google.com/android/nexus/images
Sent from my Nexus 9 using XDA Free mobile app
Flashfire is safe to use. But it is advised to update the bootloader via fastboot since it is much more secure, but I have updated it with Flashfire once and had no issues. As long you know what you are flashing, you won't have any problem. I've not used FF to flash OTA since I was always on a custom ROM, but what you describe sounds like something Flashfire was meant to do. You'll find more information in Chainfire's thread.
roofrider said:
Flashfire is safe to use. But it is advised to update the bootloader via fastboot since it is much more secure, but I have updated it with Flashfire once and had no issues. As long you know what you are flashing, you won't have any problem. I've not used FF to flash OTA since I was always on a custom ROM, but what you describe sounds like something Flashfire was meant to do. You'll find more information in Chainfire's thread.
Click to expand...
Click to collapse
I see that you've flashed the bootloader with FlashFire on your Nexus 5X and had no issues. Did you use bootloader IMG file from Bullhead Official Images? Could you elaborate a little more about what specifically did you do to flash the bootloader with FlashFire?
I've a 5X with a dead USB port, so I'm highly interested on knowing the details
mishamosher said:
I see that you've flashed the bootloader with FlashFire on your Nexus 5X and had no issues. Did you use bootloader IMG file from Bullhead Official Images? Could you elaborate a little more about what specifically did you do to flash the bootloader with FlashFire?
I've a 5X with a dead USB port, so I'm highly interested on knowing the details
Click to expand...
Click to collapse
I've not used FlashFire lately, but it was pretty straightforward. Yes I used the bootloader IMG file, but probably downloaded from Flash's or Bean's file host. Just enable Bootloader flashing in FF's settings, add the Firmware package (bootloader image), select the partition, and Flash. Though it works, it's not the safest way to flash bootloaders. I would suggest checking FF's thread just to make sure the app supports the latest bootloader update and whatnot. It being Chainfire's app there should be no reason to worry, but always a good idea to read/search the official thread in such cases.
I'm about to purchase a Nexus 5X, and currently using LG G2.
I use some root apps such as Titanium Backup, AdAway, and some Xposed models for tweaking.
Is it worth to root the Nexus 5X as well? Will it affect OTA updates? And if so, is it easy to update the device manually without losing important data?
I'm pretty sure that if you use systemless root you can still OTA. Either way, if you wouldn't use Android Pay, then i'd see why you wouldn't root.
Rekan_ said:
I'm pretty sure that if you use systemless root you can still OTA. Either way, if you wouldn't use Android Pay, then i'd see why you wouldn't root.
Click to expand...
Click to collapse
You can't install the differential OTA you get over the air directly because boot.img will fail integrity check.
It is relatively easy to replay boot.img though and run the OTA, then reinstall root.
Alternatively, flash the full OTA from the factory image page using adb sideload or TWRP.
Alternatively, flash the appropriate images using fastboot.
There are other ways like with flashfire also.
If you have to ask if you should root, you shouldn't.
Sent from my Nexus 5X using Tapatalk
Why would you use stock image anyway? There are plenty of roms that get updated monthly, albeit with a little delay