Hello,
Long story short,
I had some problems with my device, I installed stock from backup, and sent to service... came back with unlocked bootloader.
I installed CM10.1 etc and later wanted to see if I got the OTA.
I got it, tried to install failed.
Recovery to stock -> failed
System reset -> fail
unroot, etc etc etc, only bootloader unlocked -> fail.
Now the point, I got a recovery from Yakju stock image from JRO03C and I had Yakjuwx JRO03C. This should be the problem why my update failed?
If so, where can I download a recovery for my Yakjuwx?
you have a custom rom. thats your problem.
Zepius said:
you have a custom rom. thats your problem.
Click to expand...
Click to collapse
Actually, as I said, everything went to stock before OTA.
So I installed stock radio, stock kernel, stock rom... from backup...
installed stock recovery
got OTA...
asked to install? said yes...
it enetered in stock recovery but failed.
Did you relock your boot loader?
Sent from my Galaxy Nexus using xda premium
Vfan23 said:
Did you relock your boot loader?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
this has nothing to do with it.
OP,
did you have any mods or anything to the stock rom? did you change the radio? did you change anything?
Zepius said:
this has nothing to do with it.
OP,
did you have any mods or anything to the stock rom? did you change the radio? did you change anything?
Click to expand...
Click to collapse
Sorry but I thought having an unlocked boot loader wouldn't allow you to accept ota updates. My bad
Sent from my Galaxy Nexus using xda premium
I sent it back to service and got it back with unlocked bootloader....
Things did:
start phone.
Root
Install recovery
Backup with recovery
Install cm...
Now:
delete data, wipe cache, wipe dalvik
Push back backup
Restore backup
Install stock for JRO03C
Install OTA
Failed.
I have yakjuwx... although possible recovery is for yakju.
Can I flash simply via cwm with install zip from sd card?
Sent from my Galaxy Nexus using Tapatalk 2
mihaly_n said:
I sent it back to service and got it back with unlocked bootloader....
Things did:
start phone.
Root
Install recovery
Backup with recovery
Install cm...
Now:
delete data, wipe cache, wipe dalvik
Push back backup
Restore backup
Install stock for JRO03C
Install OTA
Failed.
I have yakjuwx... although possible recovery is for yakju.
Can I flash simply via cwm with install zip from sd card?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
you still didnt answer my question. The stock rom backup you had, did you do anything to it to change anything about the /system partition? that causes the OTA to fail.
why dont you just do this: http://forum.xda-developers.com/showthread.php?t=1626895
and flash the most recent version of android?
No... made a full backup and stored to my pc... nothing was changed, nothing was modified...
simply I put it back and that's all...
mainly I don't want it because I have YAKJUXW and I don't want YAKJU.
I would full flash a new stock image... but I can't find YAKJUWX only YAKJU.
mihaly_n said:
No... made a full backup and stored to my pc... nothing was changed, nothing was modified...
simply I put it back and that's all...
mainly I don't want it because I have YAKJUXW and I don't want YAKJU.
I would full flash a new stock image... but I can't find YAKJUWX only YAKJU.
Click to expand...
Click to collapse
thats becauce yakjuwx isnt supported by google. samsung supports it. you'd be better off flashing yakju as it is supported by google and you will receive timely updates.
as for the reason the OTA failed, if you try and flash the OTA with a custom recovery (and maybe even stock recovery, not sure tho), it will fail at an assert check. if you read the assert failure or post it here, you can find out what the cause of the failure is.
where can I find the assert? What is that?
I tried installing OTA via stock... but it just said:
checking package,
opening package
installing package
installation aborted...
nothing much more...
mihaly_n said:
where can I find the assert? What is that?
I tried installing OTA via stock... but it just said:
checking package,
opening package
installing package
installation aborted...
nothing much more...
Click to expand...
Click to collapse
Flash CWM or TWRP and try to install the OTA. It will tell you the assert failure
Sent from my Galaxy Nexus using Tapatalk 2
Oh I see...
I'll try it in the next days and I'll report back
Thank you really much for your help
ok runned the backup etc...
now I copied the update and choosed install zip
here itt is
assert failed:
file_getprop("/system/build.prop". "ro.build.fingerprint") == "google/takju/maguro:4.1.1/JRO03C/398337:user/release-keys"... etc
status 7
ideas?
if I install this:
http://forum.xda-developers.com/showthread.php?p=40712528#post40712528
than can I incrementally OTA?
yeah it works
Related
I have root and un-lock my Galaxy Nexus today and flash IMM76D which is download from Google developer page (https://developers.google.com/android/nexus/images)
after finish all the step and updated to Android 4.0.4 Google official rom, I have received Android 4.0.4 System Update by OTA, and ask me reboot the phone !
after rebooting, Build number is updated to IMM76I. and the Baseband version is I9250XXLA2.
But I can not go into CWM anymore after updated by OTA. that's it is normal case......????????????
why un-root after updated by OTA ???????
Sent from my Galaxy Nexus using Tapatalk 2
Your meant to pull the battery out when your flashing the ROM .. geeeez some people don't read instructions anymore!
Remember! Pull your battery out whilst flashing!
Rename the OEM recovery restore file, reflash CWM recovery, and you should be good to go.
Gnex toolkit should help, if you don't have it already.
hki_peter said:
I have root and un-lock my Galaxy Nexus today and flash IMM76D which is download from Google developer page (https://developers.google.com/android/nexus/images)
after finish all the step and updated to Android 4.0.4 Google official rom, I have received Android 4.0.4 System Update by OTA, and ask me reboot the phone !
after rebooting, Build number is updated to IMM76I. and the Baseband version is I9250XXLA2.
But I can not go into CWM anymore after updated by OTA. that's it is normal case......????????????
why un-root after updated by OTA ???????
Click to expand...
Click to collapse
Everything is in the OTA update instruction thread...
efrant said:
Notes:
6) As with all stock updates from Google, these updates will change the permissions on the su binary so, in effect, you will lose root (for those who have it). Install supercurio's OTA Rootkeeper BEFORE you do all this, or, for those with an unlocked bootloader or CWM installed, just re-flash ChainsDD's Superuser zip file found here in CWM, or manually change the permission via ADB (mount the system and chmod 4755 /system/bin/su) while booted in CWM.
Click to expand...
Click to collapse
Recovery gets replaced to stock-version up on updating so cwm will need to be re-flashed after...
Sent from my Galaxy Nexus using xda premium
Tjotte said:
Recovery gets replaced to stock-version up on updating so cwm will need to be re-flashed after...
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yup. That is in there as well...
efrant said:
Notes:
5) For those of you that don't know, there are two files that re-flash the stock recovery on every boot (/system/recovery-from-boot.p and /system/etc/install-recovery.sh). You need to make sure that these files are either deleted or renamed, or else CWM will disappear when you reboot. These files serve no purpose other than re-flashing the stock recovery on every boot. So, if you've recently gotten an OTA and applied it, your CWM is gone...
Click to expand...
Click to collapse
zeekiz said:
Your meant to pull the battery out when your flashing the ROM .. geeeez some people don't read instructions anymore!
Remember! Pull your battery out whilst flashing!
Click to expand...
Click to collapse
What's the intention here? There's no need for this if you're not helping/explaining. What if he did and brick his phone? Would that make you happy?
About a week ago I decided to root my phone. My goal was to get my phone to yakju by flashing 4.1 . After nearly bricking my phone, I eventually got there. What I want to do now is be able to receive OTA updates in the future. I understand that having CWM recovery installed will cancel these updates. Can anyone help me get rid of CWM without losing my data?
Thanks
Sent from my Galaxy Nexus using xda app-developers app
You need to flash the stock recovery back, which can be done via Fastboot. It won't wipe data.
You also need to make sure you have the proper bootloader and radio (which should've updated when you went to 4.1). Both need to be in place to receive and auto-install an OTA.
martonikaj said:
You need to flash the stock recovery back, which can be done via Fastboot. It won't wipe data.
You also need to make sure you have the proper bootloader and radio (which should've updated when you went to 4.1). Both need to be in place to receive and auto-install an OTA.
Click to expand...
Click to collapse
Thanks Marton.
I forget to mention that I'm a real n00b at all of this stuff,
I'm downloading the 4.0.4 "yakju" factory image from here. Is it ok to apply this using the wugfresh root toolkit? Once I flash the stock image I will be prompted to update to 4.1?
My phone details are attached.
your already on 4.1.1 with correct radio.
Just flash the stock recovery using fastboot.
No need to flash 4.04 again.
atifsh said:
your already on 4.1.1 with correct radio.
Just flash the stock recovery using fastboot.
No need to flash 4.04 again.
Click to expand...
Click to collapse
Thank you!
I installed 4.1 using a toolkit and it wiped my data, but I didnt have much on there anyway.
I now have stock android 4.1, yakju, unlocked bootloader and not rooted. How can I root my phone from here?
tomcintosh said:
Thank you!
I installed 4.1 using a toolkit and it wiped my data, but I didnt have much on there anyway.
I now have stock android 4.1, yakju, unlocked bootloader and not rooted. How can I root my phone from here?
Click to expand...
Click to collapse
uhh. You need to follow the same guide to root as always. You flash CWM, flash the su.zip and push the superuser.apk.
But I thought you wanted stock recovery? As I said before, you can just flash it via Fastboot.
If you have adb already setup.
Adb reboot-bootloader. To get boot loader mode.
Fastboot flash recovery recovery.img
Fastboot reboot.
Recovery.img = stock recovery you can rename the file or use the exact name in command.
It will not wipe.
martonikaj said:
uhh. You need to follow the same guide to root as always. You flash CWM, flash the su.zip and push the superuser.apk.
But I thought you wanted stock recovery? As I said before, you can just flash it via Fastboot.
Click to expand...
Click to collapse
Yeh... don't know what I'm saying now
Thanks for the help.
Sent from my Galaxy Nexus using xda app-developers app
Basically I have the preview build of Jelly Bean (JRN84D) but it keeps alerting me to install the OTA version which fails, I know there are lots of threads about this but I can't seem to find the answer in them, I tried flashing the stock recovery but when I try to boot into it I get the Red exclamation mark and can't do anything with the volume or power keys, this is the same exclamation mark I get when trying to install the update.
I think the recovery file may be corrupt, is this the key to getting OTA update? Also my radio is XXLF1 if that helps. Thanks for any help offered, I watched the video and everybody hates noobs but I tried the solutions in other posts and it seems to have got worse.
EDIT: I can access recovery now, but the update still fails.
Sgtpanda said:
Basically I have the preview build of Jelly Bean (JRN84D) but it keeps alerting me to install the OTA version which fails, I know there are lots of threads about this but I can't seem to find the answer in them, I tried flashing the stock recovery but when I try to boot into it I get the Red exclamation mark and can't do anything with the volume or power keys, this is the same exclamation mark I get when trying to install the update.
I think the recovery file may be corrupt, is this the key to getting OTA update? Also my radio is XXLF1 if that helps. Thanks for any help offered, I watched the video and everybody hates noobs but I tried the solutions in other posts and it seems to have got worse.
EDIT: I can access recovery now, but the update still fails.
Click to expand...
Click to collapse
Flash the Stock Recovery/Radio/Bootloader for Takju from the hosted Google Factory Images through Fastboot. It won't erase your data/apps. For the Recovery, you will need to extract it manually from the image while the bootloader and radio should be standalone.
dnlsmy said:
Flash the Stock Recovery/Radio/Bootloader for Takju from the hosted Google Factory Images through Fastboot. It won't erase your data/apps. For the Recovery, you will need to extract it manually from the image while the bootloader and radio should be standalone.
Click to expand...
Click to collapse
When you say the Takju Google Factory Image do you mean the 4.0.4 takju image? as that's the only one I can find on their site.
Thanks.
Sgtpanda said:
When you say the Takju Google Factory Image do you mean the 4.0.4 takju image? as that's the only one I can find on their site.
Thanks.
Click to expand...
Click to collapse
Yes.
Sent from my Galaxy Nexus using xda app-developers app
wilsonlam97 said:
Yes.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Flashed the radio, bootloader and recovery from it and it still doesn't work, if I press up and power button after it fails it gives me a status 7 error, might just flash stock and unroot if there's no other way.
Sgtpanda said:
Flashed the radio, bootloader and recovery from it and it still doesn't work, if I press up and power button after it fails it gives me a status 7 error, might just flash stock and unroot if there's no other way.
Click to expand...
Click to collapse
What is the error?
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
What is the error?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.
Any ideas or am I screwed and should go ahead and try flash stock rom and unroot? Will that even help?
Sgtpanda said:
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
What's the FULL error.
Also, are you using a recovery that is different from CWM 5.5.0.2 or 5.5.0.4? If so, get rid of it, and use one of those.
efrant said:
What's the FULL error.
Also, are you using a recovery that is different from CWM 5.5.0.2 or 5.5.0.4? If so, get rid of it, and use one of those.
Click to expand...
Click to collapse
I'm using stock recovery because everything I've read says to use stock if you want to accept OTA updates, the full error is:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/ApplicationsProvider.apk","08db09578758c61cf5c8ec895b1331a5fa4cc349","512784ba869d55f3cf2d291baaa5f6a0aa90b960")
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.
Sgtpanda said:
I'm using stock recovery because everything I've read says to use stock if you want to accept OTA updates, the full error is:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/ApplicationsProvider.apk","08db09578758c61cf5c8ec895b1331a5fa4cc349","512784ba869d55f3cf2d291baaa5f6a0aa90b960")
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Where did you get the preview build? Based on that error, it would seem to me like you flashed a non-stock version of JB 4.1 like bigxie's ROM. If that is the case, you need to flash a stock ROM before any update can be applied...
efrant said:
Where did you get the preview build? Based on that error, it would seem to me like you flashed a non-stock version of JB 4.1 like bigxie's ROM. If that is the case, you need to flash a stock ROM before any update can be applied...
Click to expand...
Click to collapse
Now that you've mentioned that name, yes that's the ROM I got, I'm gonna go ahead and guess there's no way to return to stock without wiping data is there?
Sgtpanda said:
Now that you've mentioned that name, yes that's the ROM I got, I'm gonna go ahead and guess there's no way to return to stock without wiping data is there?
Click to expand...
Click to collapse
Maybe. You can try this without wiping and see if it works. Then apply the JRO03C-from-JRN84D update form here.
efrant said:
Maybe. You can try this without wiping and see if it works. Then apply the JRO03C-from-JRN84D update form here.
Click to expand...
Click to collapse
And if I do that then will I be able to accept any future OTA updates through android and have it update automatically without having to flash the updates myself?
Sgtpanda said:
And if I do that then will I be able to accept any future OTA updates through android and have it update automatically without having to flash the updates myself?
Click to expand...
Click to collapse
If you follow method 2, then yes, you will be able to automatically accept OTA updates and have it install automatically. BUT, you MAY need to do the first one (i.e., to JRO03C) manually (if you don't get it shortly after you flash JRN84D). After that, you will be all set for the next update.
efrant said:
If you follow method 2, then yes, you will be able to automatically accept OTA updates and have it install automatically. BUT, you MAY need to do the first one (i.e., to JRO03C) manually (if you don't get it shortly after you flash JRN84D). After that, you will be all set for the next update.
Click to expand...
Click to collapse
I'll try it, thanks for the help.
EDIT: It worked! Did it without wiping and it accepted the OTA without needing to do it manually, once again thanks so much for helping!
Hello guys,
Just a quick noob question to which I get different answers: If I flash from yakjuxw to yakju and choose to flash a custom recovery, will I be able to receive OTA updates?
Thanks in advance
You will receive them, but you won't be able to install them if your recover isn't stock.
Sent from my Galaxy Nexus using Tapatalk 2
To add to what Petrovski80 said, you wont be able to install the update over-the-air, but you will be able to install it by downloading it to /sdcard and rebooting into CWM and installing it from there.
EDIT: And in most cases, you will likely see the update here before you get it over-the-air on your device.
And if I have flashed mods/kernels through CWM and i install the update, will the mods be preserved or do I have to flash them again?
tobitronics said:
And if I have flashed mods/kernels through CWM and i install the update, will the mods be preserved or do I have to flash them again?
Click to expand...
Click to collapse
If you flash "mods/kernels", the update will NOT install. If you change any of the original stock files, the update will NOT install.
yestinua let
efrant said:
If you flash "mods/kernels", the update will NOT install. If you change any of the original stock files, the update will NOT install.
Click to expand...
Click to collapse
THIS.
Hi,
I have rooted Stock 4.2.1 Jelly Bean Build number JOP40D, I got software alert 5 days back its successfully download and then after click on restart and install button mobile reboot in TWRP mood and stuck by giving me some error related to partition, image file not found etc etc..
I had tried this 3 to 4 times but same error.
Please help me how to install it on the air.
Just for info i have upgraded my Gnex from 4.1.1 to 4.2.1 using Wug's Nexus Root Toolkit v1.6.2.
Please help me.
You're rooted, which means you edited the system, which means the OTA probably won't install. Always better to go back to 100% stock and re-root
ftrack said:
Hi,
I have rooted Stock 4.2.1 Jelly Bean Build number JOP40D, I got software alert 5 days back its successfully download and then after click on restart and install button mobile reboot in TWRP mood and stuck by giving me some error related to partition, image file not found etc etc..
I had tried this 3 to 4 times but same error.
Please help me how to install it on the air.
Just for info i have upgraded my Gnex from 4.1.1 to 4.2.1 using Wug's Nexus Root Toolkit v1.6.2.
Please help me.
Click to expand...
Click to collapse
You cannot install an OTA update unless you are 100% stock. You have TWRP recovery, thus not 100% stock. That's why it fails. Either flash back stock recovery and retry, or simply apply the update manually using this guide: http://forum.xda-developers.com/showthread.php?t=1419170
Petrovski80 said:
You cannot install an OTA update unless you are 100% stock. You have TWRP recovery, thus not 100% stock. That's why it fails. Either flash back stock recovery and retry, or simply apply the update manually using this guide: http://forum.xda-developers.com/showthread.php?t=1419170
Click to expand...
Click to collapse
Huh.. I've received JDQ39 ota, I forgot to remove TWRP before hand, but it still went through anyway. It installed fine, surprised the hell out of me actually. TWRP 2.4.1.0. Didn't have any other mods though. Not even rooted.
Sent from my Nexus
Petrovski80 said:
You cannot install an OTA update unless you are 100% stock. You have TWRP recovery, thus not 100% stock. That's why it fails. Either flash back stock recovery and retry, or simply apply the update manually using this guide: http://forum.xda-developers.com/showthread.php?t=1419170
Click to expand...
Click to collapse
you can definitely install the OTA with a custom recovery. it however will not install if you modified any /system files, bootloader or radio do not match.
Oh really? That surprises me honestly. Although I never tried it, I always assumed every partition needed to have unmodified stock files (adding extra files does not matter). Apparently the recovery partition is an exception.
Petrovski80 said:
Oh really? That surprises me honestly. Although I never tried it
Click to expand...
Click to collapse
+1
I was really surprised, in a good way! xD