Of my galaxy nexus, the build number of recent firmware is JWR66V of Takju updated one month or longer ago. The phone showed twice of notice of updating to JWR66Y, so then pressed button to reboot and install. I did not watch the whole installing. After booting, the build number I checked was still JWR66V. I tried pressing the "Check now" button in "System updates", but no response and still showed "Last checked for updates on Jul 31."
Anyone can give help with that? Thanks a lot.
You are probably rooted and with custom recovery.... That's why the update failed.
The update package is at /cache.
From SuperSu do a full unroot, re-apply stock recovery and try update again.
Sent from my Galaxy Nexus using xda app-developers app
wisefreakz said:
You are probably rooted and with custom recovery.... That's why the update failed.
The update package is at /cache.
From SuperSu do a full unroot, re-apply stock recovery and try update again.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Thank you very much!
Surely I did not (never) get it rooted and no custom recovery. I only use it as the second (spare) phone, so I keep the system entirely original and installed some common software. I checked the /cache directory with estrong explorer, but it showed empty.
Is that could be because Yakju model using Takju firmware?
Weird. Keep waiting for answer.
pursuefun said:
Thank you very much!
Surely I did not (never) get it rooted and no custom recovery. I only use it as the second (spare) phone, so I keep the system entirely original and installed some common software. I checked the /cache directory with estrong explorer, but it showed empty.
Is that could be because Yakju model using Takju firmware?
Weird. Keep waiting for answer.
Click to expand...
Click to collapse
Weird...! There is no yakju or takju hw.... They are sw bundled to different countries... I dunno if being unrooted you can see what's in the cache folder...
Sent from my Galaxy Nexus using xda app-developers app
wisefreakz said:
Weird...! There is no yakju or takju hw.... They are sw bundled to different countries... I dunno if being unrooted you can see what's in the cache folder...
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I was wondering if I can see files in /cache without rooted, too. But, I don't want to root it for that. Maybe I will flash the whole firmware of JWR66Y, if the problem can't be solved.
Thank you very much.
Related
So I updated to 4.1.2 recently and decided I'd simply root my phone. Now today I have the AT&T updater telling me I have an update pending. I'm already on 4.1.2 and the only possible reason I could conceive as to why this is popping up is because during rooting something must have changed and that flagged the updater as me having an obsolete firmware. Anyone else getting this?
mrmcpowned said:
So I updated to 4.1.2 recently and decided I'd simply root my phone. Now today I have the AT&T updater telling me I have an update pending. I'm already on 4.1.2 and the only possible reason I could conceive as to why this is popping up is because during rooting something must have changed and that flagged the updater as me having an obsolete firmware. Anyone else getting this?
Click to expand...
Click to collapse
What is your current firmware
Sent from my GT-N7105 using xda premium
4.1.2 Baseband I317UCALK7 Build Number JZO54K.I317UCALK7
mrmcpowned said:
4.1.2 Baseband I317UCALK7 Build Number JZO54K.I317UCALK7
Click to expand...
Click to collapse
The latest is actually I317UCAMA4; the ALK7 is the one right before that
Thanks, I have TWRP installed so do I have to reinstall the stock recovery and then continue the update and whatnot?
Don't waste your time with the ATT update; just flash almost any custom ROM, and you will have all the benefits plus much more...
wase4711 said:
Don't waste your time with the ATT update; just flash almost any custom ROM, and you will have all the benefits plus much more...
Click to expand...
Click to collapse
I agree, but if you want to upgrade, use cf auto root to reinstall stock recovery, use full unroot in super su, then run update
Sent from my GT-N7105 using xda premium
Android The Greek said:
I agree, but if you want to upgrade, use cf auto root to reinstall stock recovery, use full unroot in super su, then run update
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
I've tried this, but the update still fails. Could it be my modified system files from setting up Google wallet?
Sent from my Nexus 7 using xda app-developers app
bookem11 said:
I've tried this, but the update still fails. Could it be my modified system files from setting up Google wallet?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Could be, I always keep a stock backup jsut incase. You can always dirty flash a stock rom and see if that works
Sent from my GT-N7105 using xda premium
If you are going to stick with stock, you may want to use autoruns to disable the check for updates. That way at least the notification will go away.
Android The Greek said:
I agree, but if you want to upgrade, use cf auto root to reinstall stock recovery, use full unroot in super su, then run update
Click to expand...
Click to collapse
I did all of the above. Update was downloaded successfully, Phone reboot itself and started installing update. And than "updated was interrupted" message popped out. I've tried it several times with the same result.
Any ideas what I'm doing wrong?
I received an update notification through OTA, and I've start the upgrade process, the device restarted to do the upgrade, but while upgrading it gave an error and hanged, I've removed the battery and start the phone, but I'm still on 4.2.2, and whenever I try to check for update it gave that there's no update.
???????
Sent from my Galaxy Nexus using xda app-developers app
Forget to tell that my device is yakju
Sent from my Galaxy Nexus using xda app-developers app
Is your phone stock? If you're rooted and made any modifications to system files (mods, build.prop edits, etc) your phone will fail during the OTA. You need to be completely stock on the latest 4.2.2 radios for your model. Basically you have to be more or less on the 4.2.2 OTA to get 4.3.... always been like that for every android version though.
Can't you fasboot flash the factory images?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
RoyJ said:
Is your phone stock? If you're rooted and made any modifications to system files (mods, build.prop edits, etc) your phone will fail during the OTA. You need to be completely stock on the latest 4.2.2 radios for your model. Basically you have to be more or less on the 4.2.2 OTA to get 4.3.... always been like that for every android version though.
Can't you fasboot flash the factory images?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Exactly what happened to me. So, I flashed factory images, received OTA for 4.2.2, cleared Google Services Framework several times, 4.3 showed up. In process of installing. Good to go.
I think flashing the image it's the easiest way, any one had the link for yakju?
Sent from my Galaxy Nexus using xda app-developers app
Also happened to me. Cleared "Google Services Framework" and tried to re-install 4.3 when it came down.
Still got an error
Any ideas?
ronsher said:
Also happened to me. Cleared "Google Services Framework" and tried to re-install 4.3 when it came down.
Still got an error
Any ideas?
Click to expand...
Click to collapse
are you on a completely stock rom? if not, it will always fail.
My friend has problem too
I rooted and install custom reovery and costume kernel for him
He got 4.3 OTA update but he get error in installing
would somebody tell me what can I do for him?
hes_luckey said:
My friend has problem too
I rooted and install custom reovery and costume kernel for him
He got 4.3 OTA update but he get error in installing
would somebody tell me what can I do for him?
Click to expand...
Click to collapse
wow.... does no one read anything? there's a thread exactly like this in Q/A, and i even said the reason it will fail not 1 post above yours... my mind is blown at the pure laziness that you have shown.
hi huy
I have a galaxy nexus which is running 4.3 JWR66V and recently I tried to update to JWR66Y but it's weird that I cannot OTA or sideload the update. It never happen to me before. and when I installed it, a message said that error status 7. assert fial: Apply_update_patch or whatever it is. Can anybody help me out here? I don't want to lose all my data.
duchung95 said:
hi huy
I have a galaxy nexus which is running 4.3 JWR66V and recently I tried to update to JWR66Y but it's weird that I cannot OTA or sideload the update. It never happen to me before. and when I installed it, a message said that error status 7. assert fial: Apply_update_patch or whatever it is. Can anybody help me out here? I don't want to lose all my data.
Click to expand...
Click to collapse
Flash the factory image and use this: http://forum.xda-developers.com/showthread.php?t=2377307
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex
My gnex is rooted so can i still do your method?
duchung95 said:
hi huy
I have a galaxy nexus which is running 4.3 JWR66V and recently I tried to update to JWR66Y but it's weird that I cannot OTA or sideload the update. It never happen to me before. and when I installed it, a message said that error status 7. assert fial: Apply_update_patch or whatever it is. Can anybody help me out here? I don't want to lose all my data.
Click to expand...
Click to collapse
the update failed because YOU changed some system file on your phone. the assert check tells you why the update failed.
I had an update problem aswell. I assume it's because I updated Google Play Services by sideloading the app when it leaked. Ideas? I'm too lazy to start from scratch.
Sent from my Galaxy Nexus using xda app-developers app
It is great
mrgnex said:
Flash the factory image and use this: http://forum.xda-developers.com/showthread.php?t=2377307
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Thank for helping me and it worked for me great but I had to adjust something in the flash-all.sh and flashing it normally
So, does anyone have a JWR66V Google Play Services apk?
I have a i9250 gsm Galaxy Nexus, maguro. JWR66V. It used to be Yajuux but I changed this to Yakju with Wug Fresh's Nexus Tool kit. I manually updated my phone to 4.3. However, about once a week, I get a notice that my phone would like to update to 4.3. The download is only 1.7mb. Once I allow the update, the phone reset, boots up and says "installing system update" with the android mascot on the screen and a swirly atom-thing at his stomach. After about a minute a message comes up that says "error!" with the android mascot now on his back. I have to remove the battery and restart my phone, otherwise it hangs. The update notice won't come back for another week, unless I stop the google service framework app and clear the data. I'm assuming these system updates are to upgrade to JWR66Y, but I don't know why I keep having these errors. Any help/advice would be appreciated.
Figured it out
Solved. I managed to sideload the update through the Nexus toolkit. Even after updating though, it didn't show the correct version. I had to unroot by uninstalling supersu (survival mode didn't work), then doing the OTA update, then reinstalling the binaries for Supersu.
Can anyone recommend a good site/feed that keeps track of these security updates/other major updates?
And the toolkit gets the credits, even when the user still has no idea what just happened.
beekay201 said:
And the toolkit gets the credits, even when the user still has no idea what just happened.
Click to expand...
Click to collapse
braindead users win again!
No Clue..
Can someone, Experienced.. Tell me what exactly to do here.. I am on Stock Rom, Rooted, with TWRP Recovery. Exact same problem when I try to install the Update. Same 1.7 MB Update. Any Help would be much appreciated.
dipenv said:
Can someone, Experienced.. Tell me what exactly to do here.. I am on Stock Rom, Rooted, with TWRP Recovery. Exact same problem when I try to install the Update. Same 1.7 MB Update. Any Help would be much appreciated.
Click to expand...
Click to collapse
The reason the update doesn't install is because you are using a third party recovery.img (twrp) and Android cannot update your phone with twrp, only with it's own recovery. You can download the update posted in one of the threads and install from twrp.
Sent from my Nexus 7 using Tapatalk 4
chrisinsocalif said:
The reason the update doesn't install is because you are using a third party recovery.img (twrp) and Android cannot update your phone with twrp, only with it's own recovery. You can download the update posted in one of the threads and install from twrp.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Thank you for this explanation. Very helpful to braindead user like myself, and will help me know what to do for future updates.
chrisinsocalif said:
The reason the update doesn't install is because you are using a third party recovery.img (twrp) and Android cannot update your phone with twrp, only with it's own recovery. You can download the update posted in one of the threads and install from twrp.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Does doing this wipe the phone?
Not if you only install the update. You will have to reinstall supersu after the update because you will lose root.
Sent from my Galaxy Nexus using Tapatalk 2
chrisinsocalif said:
The reason the update doesn't install is because you are using a third party recovery.img (twrp) and Android cannot update your phone with twrp, only with it's own recovery. You can download the update posted in one of the threads and install from twrp.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
thats not correct. ive updated with OTAs through TWRP.
the update is failing because something isnt stock.
Zepius said:
thats not correct. ive updated with OTAs through TWRP.
the update is failing because something isnt stock.
Click to expand...
Click to collapse
Update through twrp by downloading the update not through ota since you have third party software.
Sent from my Nexus 7 using Tapatalk 4
chrisinsocalif said:
Update through twrp by downloading the update not through ota since you have third party software.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Requesting the download link if possible. Searched the forum but couldn't found one. Tx in Advance.
Solved. Got it! HERE
Help !!!
I just updated my NEXUS 7 2013 from 4.4 to 4.4.2 but after restarting, the Android version in settings still says 4.4.
I checked for updates again in System Updates menu but my device says the system is up to date.
My device is Nexus 7 2013 32G rooted under TWRP 2.6.3.1 recovery on Super SU root.
I also tried updating manually using TWRP zip update but it failed.
here's the part of the prompt during TWRP update:
Verifying current system...
"/system/bin/debuggerd" has unexpected contents.
E: Error executing updater binary in zip '/sdcard/Dow...
Hope someone can help me find a solution for this. Thanks!
I auto updated my nexus 7 2013 wifi 32gb with 4.2.2 and there were no problems. I put the device back to stock 4.4 first and unrooted the tablet as well. My suggestion is to get the toolkit and select any version for device then select flash stock and unroot box. I did this and received the ota update the next day. After updating successfully you can root and install custom recovery again if that is what you want. Do not OEM lock the device because every time you unlock it again you will erase all content.
Best of luck
Sent from my Nexus 7 using xda app-developers app
OP: Uninstall stickmount (easiest) or flash the debuggerd in this thread.
Yea it won't update if your rooted.
-sent from my LG G2 using XDA Premium 4
player911 said:
Yea it won't update if your rooted.
-sent from my LG G2 using XDA Premium 4
Click to expand...
Click to collapse
Being rooted is fine. I was rooted just had to uninstall stickmount, and it updated from 4.3 to 4.4.2, I did lose root, but that was easily rectified.
mdamaged said:
Being rooted is fine. I was rooted just had to uninstall stickmount, and it updated from 4.3 to 4.4.2, I did lose root, but that was easily rectified.
Click to expand...
Click to collapse
How did you update? Side-load?
I'm guessing the Stickmount issue is only present on 4.4 because I was on 4.4.1 (Stock Rooted ROM by Scroler) and flashed the OTA I received on device in TWRP and it successfully updated to 4.4.2...and I never lost root ?
Sent from my Nexus 7 using Tapatalk 4
Richieboy67 said:
How did you update? Side-load?
Click to expand...
Click to collapse
Nope, OTA.
thanks
Jleeblanch said:
I'm guessing the Stickmount issue is only present on 4.4 because I was on 4.4.1 (Stock Rooted ROM by Scroler) and flashed the OTA I received on device in TWRP and it successfully updated to 4.4.2...and I never lost root ?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Can you give us the link to the stock rooted rom by scroler?? i can't seem to find it anywhere. thnks alot!
mdamaged said:
Nope, OTA.
Click to expand...
Click to collapse
Cool, I just ran the update myself with no issues. I just changed back to the stock recovery first and ran the ota to 4.4 no problem. I was worried about it though because I had issues when doing my Nexus 4 but it was my fault. At the end in the recovery when it asked if I wanted it to fix root I clicked yes. I should have clicked no and just rerooted using wug or something.
Now I am going to grab the 4.4.2 update. I do not have ota yet for 4.1 or 4.2 on my Nex 7. My Nex 4 though is all set at 4.4.2 and it seems like they really fixed tons of stuff! I can't wait to get that on the 7!!
Thanks:good:
mdamaged said:
OP: Uninstall stickmount (easiest) or flash the debuggerd in this thread.
Click to expand...
Click to collapse
I used to have OTA problems with Stickmount and that damn debuggered file on my 2012 Nexus 7. Never installed it on my flo as a result.
Are you saying that simply uninstalling Stickmount will be sufficient for an OTA to take successfully? Does uninstalling reinstate the previous debuggered file, or must we replace it manually?
mlj11 said:
I used to have OTA problems with Stickmount and that damn debuggered file on my 2012 Nexus 7. Never installed it on my flo as a result.
Are you saying that simply uninstalling Stickmount will be sufficient for an OTA to take successfully? Does uninstalling reinstate the previous debuggered file, or must we replace it manually?
Click to expand...
Click to collapse
Yes. Upon installation, Stickmount makes a backup of debuggerd in the same directory with a bak extension, when uninstalled it renames it to debuggerd, restoring the stock debuggerd, I did not have to put it back manually.
player911 said:
Yea it won't update if your rooted.
-sent from my LG G2 using XDA Premium 4
Click to expand...
Click to collapse
I flashed 4.4.1-> 4.4.2 successfully with twrp on a rooted device but it was just rooted with a modified host file, no other mods.
godutch said:
I flashed 4.4.1-> 4.4.2 successfully with twrp on a rooted device but it was just rooted with a modified host file, no other mods.
Click to expand...
Click to collapse
I thought the issue was to do with OTA updates and and not flashing updates from recovery as this is defeating the purpose of OTA udates.
Sent from my Nexus 7 using xda app-developers app
I am on 4.3, unlocked and rooted with TWRP recovery.
The 4.42 update notification had been there for a while and I finally decided to take the plunge.....
I ran the update through the notification and my device rebooted into the TWRP custom recovery. Not knowing what to do, I rebooted again and checked the version. Nothing had changed and I am still at 4.3.
However the System Update notification had disappeared. I checked for System Update and it says my device is up-to-date....
How do I get the OTA update again?
What do I have to do to get the update installed on my device?
I have since also uninstalled StickMount.
vivre said:
I am on 4.3, unlocked and rooted with TWRP recovery.
The 4.42 update notification had been there for a while and I finally decided to take the plunge.....
I ran the update through the notification and my device rebooted into the TWRP custom recovery. Not knowing what to do, I rebooted again and checked the version. Nothing had changed and I am still at 4.3.
However the System Update notification had disappeared. I checked for System Update and it says my device is up-to-date....
How do I get the OTA update again?
What do I have to do to get the update installed on my device?
I have since also uninstalled StickMount.
Click to expand...
Click to collapse
You could always just do a full wipe and restore it to factory defaults. That'll do it for sure.
Sent from my Nexus 7 using Tapatalk
dmginc said:
You could always just do a full wipe and restore it to factory defaults. That'll do it for sure.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Anyway to do it without wiping data? :crying:
vivre said:
Anyway to do it without wiping data? :crying:
Click to expand...
Click to collapse
Sorta yeah. But it hurts more than it helps. Wiping is really the best way to go. Or just wait a day or two and see if it comes.
Sent from my Nexus 7 using Tapatalk
vivre said:
I am on 4.3, unlocked and rooted with TWRP recovery.
The 4.42 update notification had been there for a while and I finally decided to take the plunge.....
I ran the update through the notification and my device rebooted into the TWRP custom recovery. Not knowing what to do, I rebooted again and checked the version. Nothing had changed and I am still at 4.3.
However the System Update notification had disappeared. I checked for System Update and it says my device is up-to-date....
How do I get the OTA update again?
What do I have to do to get the update installed on my device?
I have since also uninstalled StickMount.
Click to expand...
Click to collapse
The over the air will not work if you have a custom recovery. You have to flash the update zip with TWRP or whatever custom recovery you are using. You could move the update from "cache" to "storage" if you still had it or just download it to storage and then flash (Install) it with TWRP..
wantabe said:
The over the air will not work if you have a custom recovery. You have to flash the update zip with TWRP or whatever custom recovery you are using. You could move the update from "cache" to "storage" if you still had it or just download it to storage and then flash (Install) it with TWRP..
Click to expand...
Click to collapse
Thanks.
Your method worked.... but only after I uninstalled Xposed Framework ! :good: