Considering the fact that my device is rooted, and I have installed Android 4.1 (Jelly Bean) by my own when it was still an unofficial version of this OS, can my device be updated to OTA update or I must get the 4.1.1 version manually by myself?. In the case I can't get the OTA update, would it be possible to stop getting notifications about a new update which is available. The constant notifications are driving me crazy. Thanks for your attention.
1 no you can't do ota updates 2 you should just flash one of many outstanding ROMs on this great website and then you will no longer get ota messages
Sent from my Galaxy Nexus using xda premium
If all you have done is flashed the 4.1 image from Google I/O, and rooted, then yes you can take the OTA. If you have a custom recovery, edited system files, non-stock bootloader and radio, you can't OTA.
tatelucas said:
Considering the fact that my device is rooted, and I have installed Android 4.1 (Jelly Bean) by my own when it was still an unofficial version of this OS, can my device be updated to OTA update or I must get the 4.1.1 version manually by myself?. In the case I can't get the OTA update, would it be possible to stop getting notifications about a new update which is available. The constant notifications are driving me crazy. Thanks for your attention.
Click to expand...
Click to collapse
As martonikaj mentioned, if you installed the stock 4.1 ROM (along with the XXLF1 radio), then you can accept the update to 4.1.1. If you installed some other 4.1 ROM that is not stock (like bigxie's ROM or something else), then no, you cannot install the update. Updates are only for stock ROMs.
If you don't want to update but want to get rid of the notification, have a look here.
Related
Hi,
I have rooted my GN using Wug's Galaxy Nexus Root Toolkit
I had ICS 4.0.3, and now I have 4.0.2 :S I searched for OTA update, but there is nothing. Whats going on? Am I still able to recieve OTA updates? Why cant I update to 4.0.3? I got the Jakyu version
Technically speaking, yes. If you are worried, just unroot, update then root again. Anyway, OTAs will revoke your root access if it's successful.
But if you are rooted and running a custom ROM, then it's a different story.
I won't worry about it because worse come to worst, you can just download the rooted OTAs online and flash it yourself. There will be so many floating around online when an official one drops.
4.0.2 is the latest OTA update available.
There isn't a 4.0.3 OTA. The latest is 4.0.2.
sorry i got my phone today and i updated it via wifi. now it's running ics 4.0.2 build icl53f. and it doesn't do anything when i tap update again. i thought it would upgrade to 4.0.4.
can i flash the latest aokp now or do i have to flash 4.0.4 via odin first?
does it make a difference?
No difference at all.
Use my guide (linked in sig...post #2) to install a rom the correct way (bug free).
I personally just updated.
Solid build.
Just in case you wanted to know why you didn't get the update for 4.0.4, Google doesn't control the release cycle for non-yakju phones (phones that are running ROMs from carriers/vendors). It has to go through their process before it gets sent to you. If you really want IMM76I without needing to go the custom route, just flash the yakju (stock Google) images here. Instructions are here.
I have YAKJU build still no Jellybean OTA on my GNexus
I am now on IMM76I & i have not received OTA update to Jellybean 4.1.
Is per your instructions I have updated to the Google version of ICS (YAKJU).
Should I wait for the OTA? or is there any other way to get Jellybean? (Dont want to root)
Unlawful said:
Just in case you wanted to know why you didn't get the update for 4.0.4, Google doesn't control the release cycle for non-yakju phones (phones that are running ROMs from carriers/vendors). It has to go through their process before it gets sent to you. If you really want IMM76I without needing to go the custom route, just flash the yakju (stock Google) images here. Instructions are here.
Click to expand...
Click to collapse
Faadiz said:
I am now on IMM76I & i have not received OTA update to Jellybean 4.1.
Is per your instructions I have updated to the Google version of ICS (YAKJU).
Should I wait for the OTA? or is there any other way to get Jellybean? (Dont want to root)
Click to expand...
Click to collapse
You can try to "force it" with the Google Services Framework trick. That's about it.
I currently have a Telus GSM GNex 4.0.4 flashed to the yakju builds so I can receive the OTA updates directly from Google. If I install the stock Jelly Bean 4.1 ROM, will I be able to receive subsequent OTA updates from Google?
Thanks.
pupsin said:
I currently have a Telus GSM GNex 4.0.4 flashed to the yakju builds so I can receive the OTA updates directly from Google. If I install the stock Jelly Bean 4.1 ROM, will I be able to receive subsequent OTA updates from Google?
Thanks.
Click to expand...
Click to collapse
yes
AFAIK, for flashing 4.1, u need CWM. if u have CWM, u cant get OTA.
spearhead121 said:
AFAIK, for flashing 4.1, u need CWM. if u have CWM, u cant get OTA.
Click to expand...
Click to collapse
We need to be a bit clearer than that in order to not cause confusion:
1) CWM is needed to flash JRN84D in current form, but that doesn't mean that CWM needs to be installed on your device. Booting CWM is fine.
2) All stock ROMs (including JRN84D) which have been updated from a previous build via an OTA update have two files in /system which re-flash the stock recovery on EVERY reboot. So, even if you did have CWM flashed, it would be gone unless you modified the ROM.
3) Even if you do keep CWM, you will still receive the notification that there is an OTA update, and you can install it -- it just won't install automatically. You need to manually download it, re-boot into CWM and flash it. But it will work fine.
My nexus use stock Google rom with Franco kernel, and I am already in 4.1.1, after a whole week of waiting and checking, I still didn't receive ota update to 4.1.2, is it because I am using Franco?
Because you're on a custom ROM.
AFAIK only stock unrooted devices receive ota
http://forum.xda-developers.com/showthread.php?t=1419170
Sent from my i9250
I'm on 4.3 but I just got an update saying "Android 4.3 update now available"?
So I'm on stock 4.3 rooted build JSS15Q but I just got an OTA message.
Naturally this wont work since I'm rooted, but does anyone know what gives? And if there's some sort of update is there a way I can do it while keeping root?
Check About tablet in settings. If you are not on build JSS15R then it is an update.
stevemw said:
Check About tablet in settings. If you are not on build JSS15R then it is an update.
Click to expand...
Click to collapse
Yes, although I'm rooted with a custom recovery so the OTA fails.
Macmee said:
So I'm on stock 4.3 rooted build JSS15Q but I just got an OTA message.
Naturally this wont work since I'm rooted, but does anyone know what gives? And if there's some sort of update is there a way I can do it while keeping root?
Click to expand...
Click to collapse
I think it will always say there's an android 4.3 update for now since these are only updates of 4.3. I'm sure when we get kit-kat (android 4.4) it'll change to "android 4.4 update now available" and will stay like that for future updates until the next android version (5.0?).
As for keeping root, installing supersu 1.65 is supposed to prevent losing root after the OTA update but I don't believe it's guaranteed to work but it's always a very quick process to gain root again. You should check out sfhub's discussion thread for this update.
bolo808 said:
I think it will always say there's an android 4.3 update for now since these are only updates of 4.3. I'm sure when we get kit-kat (android 4.4) it'll change to "android 4.4 update now available" and will stay like that for future updates until the next android version (5.0?).
As for keeping root, installing supersu 1.65 is supposed to prevent losing root after the OTA update but I don't believe it's guaranteed to work but it's always a very quick process to gain root again. You should check out sfhub's discussion thread for this update.
Click to expand...
Click to collapse
Thanks for the info, in the end I went with this:
http://forum.xda-developers.com/showthread.php?t=2447876
I'm trying it now so hopefully it goes smoothly. The only problem I foresee is that in the future I wont be aware of when further updates are available (this method disables OTA notifications).
Macmee said:
Thanks for the info, in the end I went with this:
http://forum.xda-developers.com/showthread.php?t=2447876
I'm trying it now so hopefully it goes smoothly. The only problem I foresee is that in the future I wont be aware of when further updates are available (this method disables OTA notifications).
Click to expand...
Click to collapse
Best of luck to you :fingers-crossed: On the bright side even though it disables OTA notifications, I guarantee you any sign of a new update in the future, you'll see it here on xda and at least from there you'll know there's an OTA on the way.
My JSS15R just installed OTA. I was running TWRP and SuperSU, and had no problems. Still rooted.
Sent from my Nexus 7 using xda app-developers app
Does anybody know what the changelog for this update is? 8mb seems to make it a minor fix for something I'm guessing
Sent from my Nexus 7 using XDA Premium 4 mobile app
rmm200 said:
My JSS15R just installed OTA. I was running TWRP and SuperSU, and had no problems. Still rooted.
Click to expand...
Click to collapse
I DID have problems. I had TWRP 2.6.3.0 and SuperSU 1.65. Update bombed while in TWRP. Rebooted so fast that I couldn't read any error messages.
I was a minor problem as I just downloaded the odex version of the update from the same thread that Macmee linked above. No biggie, but would have been nice it if it happened automatically.
BTW, I WAS automatically notified of the OTA update even though I was running the Odex version of 15Q (due to problems with OTA update while rooted on the previous version -- been to this rodeo before). If I can ask, what leads you to believe that this odex/deodex version will break OTA notifications?
PJ Clifford said:
I DID have problems. I had TWRP 2.6.3.0 and SuperSU 1.65. Update bombed while in TWRP. Rebooted so fast that I couldn't read any error messages.
I was a minor problem as I just downloaded the odex version of the update from the same thread that Macmee linked above. No biggie, but would have been nice it if it happened automatically.
BTW, I WAS automatically notified of the OTA update even though I was running the Odex version of 15Q (due to problems with OTA update while rooted on the previous version -- been to this rodeo before). If I can ask, what leads you to believe that this odex/deodex version will break OTA notifications?
Click to expand...
Click to collapse
If you are running the odex version from development, OTA notification will still be there, but the OTA update will fail. At the minimum, the kernel-rootfs included in that build, while only having very minimal functionality changes, will fail the SHA1 check in the OTA update because even a 1-byte change will fail.
I started looking to see why I had no problems with the OTA. Turns out I did lose the superSU binary and TWRP after the update. I am back to stock recovery. So I have a bit of fixing to do.
Sent from my Nexus 7 using xda app-developers app
sfhub said:
If you are running the odex version from development, OTA notification will still be there, but the OTA update will fail. At the minimum, the kernel-rootfs included in that build, while only having very minimal functionality changes, will fail the SHA1 check in the OTA update because even a 1-byte change will fail.
Click to expand...
Click to collapse
Ahhh.... That explains everything! After I got the N7, the first thing I did was root it. Of course that was with the older versions of TWRP and SuperSU. I got the notice for the 15q update and, of course, it failed due to the old SuperSU (didn't know that at the time, just that it failed). I ended up downloading the rooted odex version from here and flashed that through TWRP. Worked perfectly. In the mean time, I upgraded TWRP and SuperSU to their latest versions when I discovered that the reason the original OTA failed was due to older versions of those utilities. So, having no clue that the odex version would kill the update, when I got the notification for 15r, I tried the OTA update and, of course in retrospect, THAT failed too. I immediately did the odex version again -- again with no problem. BUT, I have been scratching my head trying to figure out why it didn't work when I had the latest TWRP/SuperSU. Now I know! Next OTA, I will either just reflash to stock or just wait a day or two for the odex/deodex versions to come out.
Whew. That is a load off. Thanks for filling me in on what is going on. I don't mind problems, but I hate a mystery!