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?
Hello,
I am fighting since yesterday to get the OTA update to install so I wanted to share my current steps and hopefully someone can suggest how to move on.
I have a GT-I9505, initially 'samsung version'. I installed TWRP in order to install the GPe edition. My phone is rooted.
I used to have TWRP 2.6.x
A few days ago, I got like many the OTA update for Lollipop. I let the phone download it and reboot. That´s when things became a bit more complicated.
After reboot, it went to TWRP where no update happened. If I reboot, I get back to be GPe version 4.4.4
I tried upgrading TWRP to a recent version without better results. I tried with TWRP 2.8.1.0
I have read in several places that the issue is that the OTA update expects the stock recovery.
Unfortunately so far I did not find a stock recovery for my S4 that does the trick.
I tried using the "Miustone_stock_recovery-flash-GE4.3". I could install the recovery.
I did save the OTA zip but I don´t know how I can skip the download and use the OTA zip... so so far I do it the 'lazy-lengthy' way and I wait for the download.
After flashing this 4.3 recovery, I get a slightly better result (but nothing better than I got using TWRP): After downloading the OTA, the phone reboots, goes to recovery and it tries to install the OTA update but it fails with the following message:
mmc_test.ko has unexpected content... Status 7
Can anyone suggest a way to easily install this OTA? I guess using a correct recovery could help... if I could find it.
Any hint appreciated.
if your rooted, you cannot OTA update.
justda said:
if your rooted, you cannot OTA update.
Click to expand...
Click to collapse
Are you saying the recovery is NOT the issue and if I unroot (I guess this is possible) it would work ?
As an update, I just tried now using Miustone_Stock_Recovery-flash-XXUBMF8.zip and I get the same result.
I have seen alot of people complain about the 7 error, i even got it when i attempted to update. Everything i read states you cannot update with the OTA .zip if your phone is modified with root and/or a custom recovery.
My advice is use one of the 3 or 4 GPE roms from the 9505 thread. But if you want to totally factory reset your phone have fun, to each his own. :good:
justda said:
I have seen alot of people complain about the 7 error, i even got it when i attempted to update. Everything i read states you cannot update with the OTA .zip if your phone is modified with root and/or a custom recovery.
My advice is use one of the 3 or 4 GPE roms from the 9505 thread. But if you want to totally factory reset your phone have fun, to each his own. :good:
Click to expand...
Click to collapse
Hi Justda,
First of all, thanks for your time and answers. My expectations are fairly low actually I installed the GPe version thinking it would make it simpler.
I was happy to get the OTA thinking I could upgrade in a click...
I realize from your answer that the OTA I am getting on my I9505 is actually meant for the I9505G and thus will not work whatever I do (correct me if I am wrong).
I will follow your advice and pick up one of those ROMs. Do you recommend a specific one?
iBastid or Danvh are my go to guys. Both are active and have a large following of users.
Danvh is straight up no aroma install, you mod it yourself.
Bastid uses aroma to give you more initial choice with his customizations.
But its up to personal preference right now, GPE is still to new for a lot of ROM pimping...
Sent from my GT-I9505G using XDA Premium HD app
I would suggest you to use antaresone's lollipop rom
link here http://forum.xda-developers.com/galaxy-s4/i9505-orig-develop/rom-cyanogenmod-12-t2943934
Questions, it's not here, ask to move this thread in the good section... Q & A
hi all
assuming that i've flashed TWRP + rooted the phone
will i still be able to update the phone via OTA updates?
as this does not work on samsung phones once KNOX is tripped
i was wondering if it would be the same on oneplus devices
your input is appreciated. thanks!
leongzxc said:
hi all
assuming that i've flashed TWRP + rooted the phone
will i still be able to update the phone via OTA updates?
as this does not work on samsung phones once KNOX is tripped
i was wondering if it would be the same on oneplus devices
your input is appreciated. thanks!
Click to expand...
Click to collapse
Short answer: No. Custom recovery can't process the OTA update. There's another thread talking about this topic here: https://forum.xda-developers.com/oneplus-5t/help/root-update-ota-t3712615
If you want the latest updates Funk Wizard usually posts their full zips (not small OTA zips) on XDA (just search in the 5T section) and OnePlus usually has them under the device support page.
I've not tried it myself but I heard once you root and go to software update section oneplus will detect your root and instead will download a full OTA zip which you can then dirty flash in your custom recovery (TWRP) without any issues. of course the flash will remove root and then you will need to flash root zip file to gain root again.
Well, actually I downloaded latest OTA (4.7.4) over wifi and then updated phone while rooted and with custom recovery (oficial 3.2.0 I think). And it worked! I lost root in the process (I rooted again later), but otherwise phone was updated and it was done via custom recovery. So far, I don't have any problems, but not sure if any problems will come later.
shadeau said:
Short answer: No. Custom recovery can't process the OTA update. There's another thread talking about this topic here: https://forum.xda-developers.com/oneplus-5t/help/root-update-ota-t3712615
If you want the latest updates Funk Wizard usually posts their full zips (not small OTA zips) on XDA (just search in the 5T section) and OnePlus usually has them under the device support page.
Click to expand...
Click to collapse
Revin said:
Well, actually I downloaded latest OTA (4.7.4) over wifi and then updated phone while rooted and with custom recovery (oficial 3.2.0 I think). And it worked! I lost root in the process (I rooted again later), but otherwise phone was updated and it was done via custom recovery. So far, I don't have any problems, but not sure if any problems will come later.
Click to expand...
Click to collapse
thanks for the response!
digitalmahdi said:
I've not tried it myself but I heard once you root and go to software update section oneplus will detect your root and instead will download a full OTA zip which you can then dirty flash in your custom recovery (TWRP) without any issues. of course the flash will remove root and then you will need to flash root zip file to gain root again.
Click to expand...
Click to collapse
wow for real?
so if you're rooted. it will not download small zips of OTA but instead the full sized OTA?
then we can choose to flash in TWRP instead?
Hi if someone could please help me as I am bootloader unlocked, rooted, (systemless) using TWRP Recovery, Magisk V.19.3, blu spark r153 oos kernal.....However a couple days ago my phone is indicating a OTA avalible, sorry did some searching just couldnt find the right awnser, I know I need to full OTA becuase I'm rooted, instead of the incremental, just looking for the best way to do this while also updating to the latest blu_spark kernal & latest TWRP, sorry just want to make sure I'm doing all this correct thanks
Do not update via OTA if you've fully rooted and installed custom kernels.
Kindly do the necessary installation steps, and don't do it like a normal OTA update.
dandrake47 said:
Do not update via OTA if you've fully rooted and installed custom kernels.
Kindly do the necessary installation steps, and don't do it like a normal OTA update.
Click to expand...
Click to collapse
much appriciated do you know where I can find the latest full update for download so I can flash it on blu twrp?
thanks again sir:good:
nickfar2000 said:
much appriciated do you know where I can find the latest full update for download so I can flash it on blu twrp?
thanks again sir:good:
Click to expand...
Click to collapse
also when it went to update before I stopped it oneplus recognized that it was rooted and that I would need the full update.....so basiclly just follow those steps?
https://forum.xda-developers.com/oneplus-5t/how-to/official-oxygenos-4-7-2-7-1-1-ota-t3709265
Hi
I have a 2015 Shield (non pro) currently running rooted 5.2.0. I am looking to update it with the latest 8.0.1 dev image to keep root. Is there any precautions or extra steps I need to take over what is in the instructions in the download centre. From what I have read I will need to ADB sideload Magisk to get full root access after installing the dev image.
you'll need to patch the boot.img in magisk canary and then flash it
https://forum.xda-developers.com/shield-tv/general/guide-root-nvidia-shield-experience-t3882254
Do I need to unroot or factory reset the rooted 5.2.0 before flashing 8.0.1. Is there any benefit in flashing the dev image rather than the factory image before flashing the patched boot.img.
You should update the firmware OTA. Because you'll flash the OTA you'll need to patch then flash the dev image or this root boot image: https://forum.xda-developers.com/shield-tv/development/kernel-overclock-kernel-2-22-ghz-t3943079
But do I need to unroot etc to do an OTA.
g1dtf said:
But do I need to unroot etc to do an OTA.
Click to expand...
Click to collapse
yes unroot will happen automatically when you install the OTA. if you know how to use adb and follow my steps it's not a big deal though you can get it back quickly
I have just unfroze system upgrade (com.nvidia.ota) and it offers experience 6.3. I guess I have to incrementally install subsequent OTA's until I get to 8.0.1 then follow your guide to re-root using your guide, I am familiar with using ADB although its been quite a while since I last used it.
g1dtf said:
I have just unfroze system upgrade (com.nvidia.ota) and it offers experience 6.3. I guess I have to incrementally install subsequent OTA's until I get to 8.0.1 then follow your guide to re-root using your guide, I am familiar with using ADB although its been quite a while since I last used it.
Click to expand...
Click to collapse
yes correct you need to do it incrementally--it's totally worth it Nvidia has done some great upgrades!
Got it up to 8.0.0 installing the OTA's. However the next OTA offered is 8.0.2 rather than 8.0.1 which as far as I know has no root options yet as the 8.0.2 images have not been released by NV.
yes but you don't need dev images to root, you can just patch this boot.img and it should give you root (as long as you install the latest Magisk canary and then upgrade through that)
https://forum.xda-developers.com/sh...l-2-22-ghz-t3943079/post81708169#post81708169
False double post please ignore.
Just a little confused as to which boot.img I need to patch. Looked at the XDA link you posted but there are quite a few different ones mentioned in that thread. I am currently running stock 8.0.2 OTA on my 2015 16gb.
g1dtf said:
Just a little confused as to which boot.img I need to patch. Looked at the XDA link you posted but there are quite a few different ones mentioned in that thread. I am currently running stock 8.0.2 OTA on my 2015 16gb.
Click to expand...
Click to collapse
Just boot into twrp using this https://drive.google.com/file/d/1934405D1S0lv52jZMqS-Zny62RIzGWSi/view
Then flash magisk canary in there, and you are done
Thanks! Flashed the latest canary and now rooted on 8.0.2.