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.
Hi guys I was just wondering if I unlock and root my stock GSM Nexus, not installing CWM or any custom roms at all just keeping it stock (aside from Superuser, root). Does that stop or affect the OTA updates from google at all.
I did a search but its all basically about putting on CWM and flashing roms and pretty much all rooting help apps I found seem to want to install cwm as well so I'm curious if once I root it is my only way of updating is manually flashing roms myself
http://forum.xda-developers.com/showthread.php?t=1441478
Ahh damn my search skills must suck but I still have to say that the answer was a little vague too
Rooting will not affect OTA updates. If you make any changes to anything outside /sdcard/ it'll cause problems. Manual update will not wipe the device.
Click to expand...
Click to collapse
I guess it means your fine and update will work as long as you don't go modding the original files ?
The thing is that i asked this question several times, and every time i get different answer..
I have also rooted my phone and unlocked bootloader, without any custom cWM or custom rom.. I have changed bootanimation (its in system, so its outside sdcard).
Will i be able to get OTA update, to see it and to install it ?
Thanks in advance
Laynee1 said:
The thing is that i asked this question several times, and every time i get different answer..
I have also rooted my phone and unlocked bootloader, without any custom cWM or custom rom.. I have changed bootanimation (its in system, so its outside sdcard).
Will i be able to get OTA update, to see it and to install it ?
Thanks in advance
Click to expand...
Click to collapse
You should still get your OTA updates. They may break the root on your phone though but thats not really a big deal.
Sent from my XT860 using XDA App
Laynee1 said:
The thing is that i asked this question several times, and every time i get different answer..
I have also rooted my phone and unlocked bootloader, without any custom cWM or custom rom.. I have changed bootanimation (its in system, so its outside sdcard).
Will i be able to get OTA update, to see it and to install it ?
Thanks in advance
Click to expand...
Click to collapse
You get a different answer because there are a lot of people who have no clue what they are talking about, passing on wrong information.
First of all, there is a difference between "getting" an OTA update notification, and having it install. Those are two separate things. You will get the OTA update notification. Whether or not it will install depends on many things, and it changes with every update. The update has a series of "asserts" or verifications that it runs through to make sure all the files it is going to update are there. You wanna know which files it checks? Don't be lazy - open up an OTA zip file and look at the updater-script file and go through it. There you will see yourself what files need to be stock. Doing it yourself is the only way to learn. Trusting a bunch of xda members who don't know what they are talking about is not the way to learn...
Having said all that, having an unlocked bootloader or having root will in no way impact your ability to receive OR install an OTA update.
Sent from my Galaxy Nexus using Tapatalk
Thanks to both of you... The thing is that i really look forward to get 4.0.3 .. I dont want to flash custom roms, i want it all stock .. Im not asking about ETAs or smt.. Im just wishing for 4.0.3 . I heard that a lot of things are settled into 4.0.3.. Lags are gone, bugs are fixed..
Laynee1 said:
Thanks to both of you... The thing is that i really look forward to get 4.0.3 .. I dont want to flash custom roms, i want it all stock .. Im not asking about ETAs or smt.. Im just wishing for 4.0.3 . I heard that a lot of things are settled into 4.0.3.. Lags are gone, bugs are fixed..
Click to expand...
Click to collapse
Unlocking or rooting does not mean you are going to flash custom ROMs...
Sent from my Galaxy Nexus using Tapatalk
The only thing that will affect OTA is when you load a custom recovery onto the phone. THAT'S THE ANSWER!
Edit - These things also can affect OTA
Modifying or removing a file that is checked/patched.
Having a different radio installed.
Having a different bootloader installed (possibly).
Having a different kernel installed.
Have modified your build.prop to show a different version.
efrant said:
Unlocking or rooting does not mean you are going to flash custom ROMs...
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Ye i know .. I have unlocked bootloader and rooted phone.. But i dont want to flash any custom rom.. I wanna keep it stock.. Just , im saying i cant wait for OTA 4.0.3
jd1001 said:
I have seen this questions posted a number of times from the same user. The only thing that will affect OTA is when you load a custom recovery onto the phone. THAT'S THE ANSWER!
Click to expand...
Click to collapse
..and an incorrect one at that. That is not the only thing.
Having a custom recovery will:
Prevent being able to install the OTA
Not stop the ota notification or being able to download it.
Other things that will break your ability to install an OTA, even if you do not have a custom recovery loaded (you can still get notified and download):
Modifying or removing a file that is checked/patched.
Having a different radio installed.
Having a different bootloader installed (possibly).
Having a different kernel installed.
Have modified your build.prop to show a different version.
You can install an ota if you modify the udapter-script if you know what you are doing even in the above scenarios (using a custom recovery).
adrynalyne said:
..and an incorrect one at that. That is not the only thing.
Having a custom recovery will:
Prevent being able to install the OTA
Not stop the ota notification or being able to download it.
Other things that will break your ability to install an OTA, even if you do not have a custom recovery loaded (you can still get notified and download):
Modifying or removing a file that is checked/patched.
Having a different radio installed.
Having a different bootloader installed (possibly).
Having a different kernel installed.
Have modified your build.prop to show a different version.
You can install an ota if you modify the udapter-script if you know what you are doing even in the above scenarios (using a custom recovery).
Click to expand...
Click to collapse
Well thanks for correcting me eventhough I wasn't actually wrong in what I said.
Thanks for adding those bits too I had no idea that other mods could affect OTA although I have read here a few times that the bootloader won't affect OTA. There should be an actual topic on this because with all the information floating around it is confusing.
Just a nuance in your choice of words...
Having a custom recovery will not prevent you from installing an OTA, but it will prevent the OTA from installing automatically on its own - you can still manually flash it through your custom recovery...
The second list should be items that "may" affect OTA, rather than "will", since it is dependent on the individual updater-script...
I think we're on the same page though...
danger-rat said:
Just a nuance in your choice of words...
Having a custom recovery will not prevent you from installing an OTA, but it will prevent the OTA from installing automatically on its own - you can still manually flash it through your custom recovery...
The second list should be items that "may" affect OTA, rather than "will", since it is dependent on the individual updater-script...
I think we're on the same page though...
Click to expand...
Click to collapse
Totally agree! Sometimes it's just frustrating becaus eeveryone thinks they know the right answer when in actual fact people post rubbish that is incorrect. I am guilty of it too but I always go back and edit when I make a false statement.
danger-rat said:
Just a nuance in your choice of words...
Having a custom recovery will not prevent you from installing an OTA, but it will prevent the OTA from installing automatically on its own - you can still manually flash it through your custom recovery...
The second list should be items that "may" affect OTA, rather than "will", since it is dependent on the individual updater-script...
I think we're on the same page though...
Click to expand...
Click to collapse
No. Any signed ota package...the above will affect it. Going by what JBQ said, where every ota should include radios...I'd say I worded it ok.
Also, there is a darn good chance that the custom recovery will stop the install even manually...if it checks the recovery version for an update. That is fairly common. That said, if you remove asserts and know what you are doing, then sure you can flash manually.
This is the sort of uncertainty I am talking about. We should create a new topic and nail it down finally!
Here is a way to nail it down:
If you have modified your system in any way aside from rooting, then your chances of being able to install an ota update are greatly diminished.
adrynalyne said:
Here is a way to nail it down:
If you have modified your system in any way aside from rooting, then your chances of being able to ota are greatly diminished.
Click to expand...
Click to collapse
Ha ha ha sorted!
adrynalyne said:
No. Any signed ota package...the above will affect it. Going by what JBQ said, where every ota should include radios...I'd say I worded it ok.
Also, there is a darn good chance that the custom recovery will stop the install even manually...if it checks the recovery version for an update. That is fairly common. That said, if you remove asserts and know what you are doing, then sure you can flash manually.
Click to expand...
Click to collapse
No OTA update to date has checked the recovery. In fact, every OTA update to date has forced a flash of the stock recovery.
Sent from my Galaxy Nexus using Tapatalk
Here we go again!
I'm running the JB 4.1 version that was released with the dev units during Google I/O -- Now it's constantly telling me to update, and when I update, it fails.
Now, I want to "upgrade" to a CM 10 nightly.
Do I have to wipe and install or can I just install?
If you want to go to CM10, you need to 100% wipe that device before installing.
If you want to try and diagnose the issue you're having taking the OTA to 4.1.1, we can work through that too.
Alright. What do you need to know?
iFargle said:
Alright. What do you need to know?
Click to expand...
Click to collapse
To try and accept the OTA?
How did you install this 4.1? Did you flash the proper radio with it? Do you have a custom recovery? Are you rooted? Have you changed or uninstalled any system apps? What error do you get (what happens) when you try to accept the OTA?
We need to know what you flashed... Did you just flash the ROM or flashed radio, bootloader and recovery for that variant? If you didn't flash them, you gotta do it. If not, you can't update.
However, if you did flash everything, just flash them one more time just to make sure. Sometimes, people get confused and flash wrong version of radio and stuff...
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I am rooted and unlocked, yes. I installed this 4.1 image using clockworkmod recovery. I don't even know what a custom recovery is, so I assume I do not have one of those.
Ah, I did disable one system app -- Google Play Magazines. As soon as the update popup comes back I will try again... Since now when I go and click on the check updates button it tells me I'm up to date, even though it's still 4.1.
iFargle said:
I am rooted and unlocked, yes. I installed this 4.1 image using clockworkmod recovery. I don't even know what a custom recovery is, so I assume I do not have one of those.
Ah, I did disable one system app -- Google Play Magazines. As soon as the update popup comes back I will try again... Since now when I go and click on the check updates button it tells me I'm up to date, even though it's still 4.1.
Click to expand...
Click to collapse
Disabling any apps wouldn't matter. However, you just said that you have Clockworkmod, right? If it's, there's your problem. Flash stock recovery and you should be good to go
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
I am sorry if this question is answered already, but is there any way one can get the OTA again once the device is rooted? I mean by unroofing and factory reset or whatever means....
After rooting, OTA is still working but you'll probably lose root after it, excepted if your Superuser has an " OTA Survival " feature. In this case, you'll have to flash a stock ROM, and root it.
Sent from my Nexus 7
azvlean said:
After rooting, OTA is still working but you'll probably lose root after it, excepted if your Superuser has an " OTA Survival " feature. In this case, you'll have to flash a stock ROM, and root it.
Sent from my Nexus 7
Click to expand...
Click to collapse
be careful if you have a custom recovery, accepting an OTA might screw your device up.
sk8trix said:
be careful if you have a custom recovery, accepting an OTA might screw your device up.
Click to expand...
Click to collapse
Thanks for replying.
Will the custom recovery be overridden by the stock one? Or is there any chance of bricking the device?
sriram18981 said:
Thanks for replying.
Will the custom recovery be overridden by the stock one? Or is there any chance of bricking the device?
Click to expand...
Click to collapse
no sometimes what happens is the files dont install and you either get a reboot screen or some sort of black screen and then you might need to fix things with a toolkit through the pc or some hard kind of fix, t happened to me on a motorola Atrix a while back.
sriram18981 said:
I am sorry if this question is answered already, but is there any way one can get the OTA again once the device is rooted? I mean by unroofing and factory reset or whatever means....
Click to expand...
Click to collapse
If your phone or tablet is rooted but with Stock Recovery the OTA should work just fine as long as you haven't modified any system files that get updated through the OTA. The bigger the update is the more likely it is you will lose root and that the OTA will find modified files. On Nexus devices I've personally never seen more than an error message if the OTA fails. At most I've only ever seen "unexpected contents in" error with whatever (modified) file is the problem. The OTA will always fail if you have a custom recovery but it's not really a big deal, you can always flash the OTA update zip in your custom recovery (TWRP?), more often than not before the OTA even rolls out to your device you can find the OTA zip here or on another website.
Just got it on my htc one... for use on stock rom/stock recovery....
https://www.androidfilehost.com/?fid=23622183712466856
RUU coming too
http://forum.xda-developers.com/showthread.php?t=2867643
Can I use the zip u provided to update? I'm totally stock. S-on. On 4.4.2. And how to do it it's been years for me. Thought I needed a .pmg file?
rickyjohn said:
Can I use the zip u provided to update? I'm totally stock. S-on. On 4.4.2. And how to do it it's been years for me. Thought I needed a .pmg file?
Click to expand...
Click to collapse
If you are s-on, you can't flash anything custom or stock. You will need to root and s-off first. Or you could take the ota if all you want is the update. If you want to get some customization on there...you should do some reading through the threads. Things are a bit different since a few years ago and this phone doesn't have an external sd card...
Sent from my Lunar Ecliptic One.
rickyjohn said:
Can I use the zip u provided to update? I'm totally stock. S-on. On 4.4.2. And how to do it it's been years for me. Thought I needed a .pmg file?
Click to expand...
Click to collapse
First link is 100% stock and will work on stock recovery. Just place it on the phone storage or SD and boot to stock recovery. Choose the appropriate "apply update from" and then point to that file.
brymaster5000 said:
If you are s-on, you can't flash anything custom or stock. You will need to root and s-off first. Or you could take the ota if all you want is the update. If you want to get some customization on there...you should do some reading through the threads. Things are a bit different since a few years ago and this phone doesn't have an external sd card...
Sent from my Lunar Ecliptic One.
Click to expand...
Click to collapse
every time i try to get into the recovery menu i just get a picture of the phone with a red triangle and exclamation point.
Any idea if towelroot works with this update? I noticed that the update notes on the vzw website says "Device root vulnerability issue has been resolved"
Sent from my HTC6500LVW using Tapatalk
rickyjohn said:
every time i try to get into the recovery menu i just get a picture of the phone with a red triangle and exclamation point.
Click to expand...
Click to collapse
That is your stock recovery. Stock recovery is not meant to go into like custom ones. It's used for ota's, factory resets, and that's about it.
Sent from my Lunar Ecliptic One.
got "invalid operation" when trying to update with the zip file, it is on device storage, any ideas? does the zip need to be renamed?
rickyjohn said:
got "invalid operation" when trying to update with the zip file, it is on device storage, any ideas? does the zip need to be renamed?
Click to expand...
Click to collapse
When flashing an OTA everything has to be bone stock. If you have stock tethering enabled, Xposed Framework installed, or files missing from /system/apps, it will fail.
That's a bummer. I'm totally stock. Just changed fonts, that's it. Guess it just won't go. thanks
I restored stock recovery and stock hotspot and the OTA still won't install properly -- I'm not sure what I'm missing. Is there any way to flash the OTA when rooted without wiping my phone?
Ovy13 said:
I restored stock recovery and stock hotspot and the OTA still won't install properly -- I'm not sure what I'm missing. Is there any way to flash the OTA when rooted without wiping my phone?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2485319
Flash in trwp the full odex ROM. I don't know if updating via ota while rooted will work. I know unlock and s-off doesn't matter from personal experience.
Sent from my One using XDA Free mobile app
Uzephi said:
http://forum.xda-developers.com/showthread.php?t=2485319
Flash in trwp the full odex ROM. I don't know if updating via ota while rooted will work. I know unlock and s-off doesn't matter from personal experience.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
In the past, simply restoring stock recovery, updating normally, and then flashing a custom recovery was enough. Doesn't seem to work this time, or there's simply some customization I've forgotten about.
If I'm not mistaken, just the presence of the su binary can be enough to abort an official ota. If you have the official OTA zip and attempt flashing through the stock recovery and it fails, the error message should give some indication of the problem. The script runs a check on the contents of /system and if anything is off it will fail.
pastorbennett said:
If I'm not mistaken, just the presence of the su binary can be enough to abort an official ota. If you have the official OTA zip and attempt flashing through the stock recovery and it fails, the error message should give some indication of the problem. The script runs a check on the contents of /system and if anything is off it will fail.
Click to expand...
Click to collapse
Su is fine. It simply won't work afterwords. Any other system changes will cause it to fail though.
dottat said:
Su is fine. It simply won't work afterwords. Any other system changes will cause it to fail though.
Click to expand...
Click to collapse
So I have TWRP, root, s-off, and XPosed installed. Verizon sent me the OTA update, but I need to return everything to stock before I do anything with the update? I'm a little dense here...
PiperCub49 said:
So I have TWRP, root, s-off, and XPosed installed. Verizon sent me the OTA update, but I need to return everything to stock before I do anything with the update? I'm a little dense here...
Click to expand...
Click to collapse
Disable xposed. Flash stock recovery and take the ota. Then flash custom recovery via Fastboot and flash su.zip in Twrp.
Assuming of course you made no other /system mods other than root and xposed.