Related
Hi,
What are experiences of current owners of Nexus phones ? My Desire Z is rooted ( only rooted, don't have a custom ROM), and I never got Gingerbread update so I'd hate the same thing happening to G Nexus.
Thanks.
zljk said:
Hi,
What are experiences of current owners of Nexus phones ? My Desire Z is rooted ( only rooted, don't have a custom ROM), and I never got Gingerbread update so I'd hate the same thing happening to G Nexus.
Thanks.
Click to expand...
Click to collapse
That will never happen with the GN. When you own this phone you're first in line for the updates until the next is coming out then you're second but still faster than the others.
Sent from my HTC Desire using XDA App
When you're rooted you can't get the OTA updates. You have to unroot to apply them. That's true for all Android phones.
You cant get them at all?
Not even: get update and apply it, loose root because of the update, reroot?
Sent from my A500 using Tapatalk
TulpiX said:
You cant get them at all?
Not even: get update and apply it, loose root because of the update, reroot?
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
you could do that, but chances are someone will get the OTA before you and pre root it for everyones pleasure and you can just flash that via recovery
TulpiX said:
You cant get them at all?
Not even: get update and apply it, loose root because of the update, reroot?
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
If my experiences with my OG Droid match up with the Nexus line, if you've only rooted and haven't actually installed another ROM, you should be able to apply the OTA update and lose root because of it. Then just root again.
martonikaj said:
When you're rooted you can't get the OTA updates. You have to unroot to apply them. That's true for all Android phones.
Click to expand...
Click to collapse
I've seen some threads claiming that root itself doesn't affect updates, but changing of data on system partition.... Was kind of hoping there is a way to have my cake and eat it too - don't mind having to root the phone all over again after the OTA....
Anyhow - as an alternative, is there a way to get official Nexus updates ( stock ) using other channels except OTA ? What was happening with old Nexus phones ?
zljk said:
I've seen some threads claiming that root itself doesn't affect updates, but changing of data on system partition.... Was kind of hoping there is a way to have my cake and eat it too - don't mind having to root the phone all over again after the OTA....
Anyhow - as an alternative, is there a way to get official Nexus updates ( stock ) using other channels except OTA ? What was happening with old Nexus phones ?
Click to expand...
Click to collapse
The alternate way to get official Nexus updates is to download the update zip file once someone copies it off their device and uploads it, and install it in whatever fashion works.
I rooted my Nexus One without unlocking the bootloader or using custom recovery. I definitely still got OTA updates and they worked fine, but would unroot the phone.
The solution is to use a custom recovery and apply the update .zip manually, then reflash superuser before rebooting. Whenever an OTA update comes out, someone eventually uses logcat to get the URL to the zip and posts it so anyone can download it.
I was rooted on Froyo and got the OTA update to Gingerbread no problem, but I lost root. I eventually got root again (Gingerbreak) and when the 2.3.4 update came out, I did it manually in custom recovery to keep root.
Now I run CM7.1 so I definitely don't get OTA updates from Google
TulpiX said:
You cant get them at all?
Not even: get update and apply it, loose root because of the update, reroot?
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
It will often download and you can try but it will either fail, unroot you, or cause troubles.
You're best off applying the pre-rooted update, or unrooting and taking the OTA.
martonikaj said:
When you're rooted you can't get the OTA updates. You have to unroot to apply them. That's true for all Android phones.
Click to expand...
Click to collapse
True. However it's trivial to repackage an OTA update to a rooted update and since it's very compatible with the source in AOSP and you get working drivers very early you can start messing around with it straight away.
blunden said:
True. However it's trivial to repackage an OTA update to a rooted update and since it's very compatible with the source in AOSP and you get working drivers very early you can start messing around with it straight away.
Click to expand...
Click to collapse
Of course, as is often the case for most phones supported here on XDA. the rooted OTA comes in the form of a .zip soon after it comes out.
slowz3r said:
you could do that, but chances are someone will get the OTA before you and pre root it for everyones pleasure and you can just flash that via recovery
Click to expand...
Click to collapse
When flashing the rooted OTA via recovery, does it wipe the phone (apps and all)?
Also for the other method, when unrooting >> applying OTA >> rooting again, does it wipe the phone at any point during this process?
Help would be appreciated and rewarded!
I just received my OTA update notification and found the update zip itself in the cache of my phone. I can post that update zip here if a mod can come along and tell me where to put it. I am going to wait till I'm home so I can have my rooting facilities handy before starting.
phazerorg said:
I rooted my Nexus One without unlocking the bootloader or using custom recovery. I definitely still got OTA updates and they worked fine, but would unroot the phone.
The solution is to use a custom recovery and apply the update .zip manually, then reflash superuser before rebooting. Whenever an OTA update comes out, someone eventually uses logcat to get the URL to the zip and posts it so anyone can download it.
I was rooted on Froyo and got the OTA update to Gingerbread no problem, but I lost root. I eventually got root again (Gingerbreak) and when the 2.3.4 update came out, I did it manually in custom recovery to keep root.
Now I run CM7.1 so I definitely don't get OTA updates from Google
Click to expand...
Click to collapse
+1. Exactly.
There is a lot of wrong (or slightly incorrect) information in this thread.
Have root has no impact whatsoever in your ability to receive or apply the OTA update. This has been the case on every Android device. However, if you have a custom recovery flashed, you will not be able to automatically apply the update - you will have to find the zip file in the cache and use your custom recovery to apply it.
On a slightly separate note, once you apply the update either automatically or manually via custom recovery, you will lose root. However, if you do have a custom recovery, as long as you flash ChainsDD's superuser package immediately after applying the update, but before rebooting, you will retain root.
On another separate not, if you flash the update as is from Google, it includes a file (/system/recovery-from-boot.p) that re-flashes the stock recovery on every boot, so you will lose your custom recovery. Either remove the file before flashing the update, or just re-flash your custom recovery.
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?
After some vigorous searching I've found out that if you don't modify the boot loader then you should be okay receiving OTA updates. I'd like to root my nexus 7 so I can run some apps that require root access. I've looked at many methods on how to root the nexus 7, but from my noob understanding, the majority of these methods require unlocking the boot loader and getting TWRP recovery. Won't that mess up the OTA? I've searched a couple threads but I don't necessarily understand the difference between an unlocked boot loader and a rooted device. The reason I still want to have OTA updates is so that I can still update android and so on.
Thanks for taking the time to read this and help guys!
Pickle_Jr;4f86 said:
After some vigorous searching I've found out that if you don't modify the boot loader then you should be okay receiving OTA updates. I'd like to root my nexus 7 so I can run some apps that require root access. I've looked at many methods on how to root the nexus 7, but from my noob understanding, the majority of these methods require unlocking the boot loader and getting TWRP recovery. Won't that mess up the OTA? I've searched a couple threads but I don't necessarily understand the difference between an unlocked boot loader and a rooted device. The reason I still want to have OTA updates is so that I can still update android and so on.
Thanks for taking the time to read this and help guys!
Click to expand...
Click to collapse
On this platform, at this time, you need to unlock the bootloader to install root.
You don't need to flash/install twrp if you don't want to, but you need to boot into twrp temporarily to install the root files.
Even if you install twrp rather than boot into it temporarily, it won't cause your ota to fail.
The things that cause the ota to fail are
1) modifying or deleting any files with your root permissions
This includes root apps which do things you might not realize
2) installing custom kernel
3) installing earlier version of supersu
sfhub said:
On this platform, at this time, you need to unlock the bootloader to install root.
You don't need to flash/install twrp if you don't want to, but you need to boot into twrp temporarily to install the root files.
Even if you install twrp rather than boot into it temporarily, it won't cause your ota to fail.
The things that cause the ota to fail are
1) modifying or deleting any files with your root permissions
This includes root apps which do things you might not realize
2) installing custom kernel
3) installing earlier version of supersu
Click to expand...
Click to collapse
Awesome! Thanks! So if I understand correctly, as long as I be careful about what root apps I have as well as have a newer (newest) version of SuperSU installed I'll be okay? I'm assuming I'll lose root when I get an OTA update but hopefully when the time comes, there'll be a way to root android 4.4 when the n7 get's it as well. And if something goes wrong I guess I could just unroot, factory reset, and update OTA that way too. Thanks for the help!
Pickle_Jr said:
Awesome! Thanks! So if I understand correctly, as long as I be careful about what root apps I have as well as have a newer (newest) version of SuperSU installed I'll be okay?
Click to expand...
Click to collapse
Yes.
For example, if you freeze a stock app in titanium, that is ok, but if you remove a stock app, then an OTA will likely fail.
If you use stickmount, it modifies a system file and backs it up, then restores it when it is done, but sometimes that gets out of sync, in which case the OTA fails.
There are other examples.
Pickle_Jr said:
I'm assuming I'll lose root when I get an OTA update but hopefully when the time comes, there'll be a way to root android 4.4 when the n7 get's it as well. And if something goes wrong I guess I could just unroot, factory reset, and update OTA that way too. Thanks for the help!
Click to expand...
Click to collapse
If you install root through the stock recovery, you'll lose root permissions (but the files will still be there). Just re-root using the existing procedure.
If you want to save a step, boot into TWRP to install the OTA (which you download manually) and then "chain" install the OTA, then the root install files.
This way, you lose root for half a second until the 2nd install file in the chain runs. Essentially you won't lose root (or won't notice losing root) because the first time you boot into 4.4, you'll have root.
Hello everyone,
I have purchased my OnePlus 5T, and I absolutely love it! I was just wondering whether I could root while retaining the stock ROM and recovery and still get the OTA updates in the usual way? I don't mind staying with OxygenOS and stock recovery I would just really like root access while keeping updates!
Would appreciate a quick answer,
Thankyou in advance,
Nathan.
I would unlock the bootloader and backup the default recovery. Then flash twrp and boot in to it and flash Magisk for root. Then flash the default recovery back.
Why? If you root your phone, then incremental OTA updates will more than likely get broken. That means, once you root, you will just need to apply the full update for each OTA. If you have TWRP installed, then you just download the fill update.zip file, and flash the update.zip and root.zip packages and be on your way.
when an update comes out just dirty flash the full zip once released, i thought u could still install OTA even with TWRP, u just can't with root and a modified system, can't u just uninstall magisk, then do the update then reinstall magisk?
Exactly. As soon as you modify the system (whole point of root), incremental OTAs will not work. Just dirty flash the full OTA via TWRP and profit.
This question has been asked before. You can read through all the answers here: https://forum.xda-developers.com/oneplus-5t/help/root-update-ota-t3712615
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?