Related
I've now had two OTA update notifications but both have failed.
The update downloads and then when the phone restarts it shows the robot with a red triangle, I have to pull the battery and once the phone restarts the update hasn't been applied.
Is this because I'm rooted or is there something else going wrong?
kekni said:
I've now had two OTA update notifications but both have failed.
The update downloads and then when the phone restarts it shows the robot with a red triangle, I have to pull the battery and once the phone restarts the update hasn't been applied.
Is this because I'm rooted or is there something else going wrong?
Click to expand...
Click to collapse
Do you have the stock recovery installed? If not, that is what is causing the problem. Have a read of this thread for more info.
Yeah that must be it. I've tried using the method in the post but I get an assert error. I think it's because I've updated system apps. Am I right in thinking I need to modify the build.prop in the update?
kekni said:
Yeah that must be it. I've tried using the method in the post but I get an assert error. I think it's because I've updated system apps. Am I right in thinking I need to modify the build.prop in the update?
Click to expand...
Click to collapse
No. You need to replace the files you updated with the stock ones.
Ah. Okay. Can you point me in the direction of the best way to do that? Or is it just a case of finding all the apks and replacing the updated ones
kekni said:
Ah. Okay. Can you point me in the direction of the best way to do that? Or is it just a case of finding all the apks and replacing the updated ones
Click to expand...
Click to collapse
What build version are you currently on, and how many files are you looking for? If it's not too many, I'll extract them for you.
efrant said:
What build version are you currently on, and how many files are you looking for? If it's not too many, I'll extract them for you.
Click to expand...
Click to collapse
Currently I'm on ICL53F. The one that stops the update is Books but then there could be more... Would disabling CWM be an option as I've just got an OTA notification.
kekni said:
Currently I'm on ICL53F. The one that stops the update is Books but then there could be more... Would disabling CWM be an option as I've just got an OTA notification.
Click to expand...
Click to collapse
No, that wouldn't be an option. The update will still fail. For any update to work, all the original files need to be present in /system. You will have to do this in an iterative process. Replace one file, try the update again, replace the next file giving you an error, try the update again, ...
It may be easier to just flash a fresh full image. (You may even be able to keep your data if you do not flash the userdata.img file -- only flash the boot.img and the system.img files from the IMM76I factory image.
I've attached the BooksTablet .apk and .odex files for you.
Lesson to be learned: back up the stock files to your computer if you plan on changing them.
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.
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
Currently trying to update my Nexus 7 to JSS15R (8MB OTA that may have helped multitouch issue?)
I am running rooted stock ROM, unlocked bootloader etc. Current build number is JSS15Q.
I've heard the newer versions of SuperSU have the OTA fix built in. I haven't been able to update though. I noticed there was an update and I went to update my Nexus 7. It went to update like it should, but I got an error and it never changed.
Flashed the OTA fix thinking it would help. No.
Forced OTA update by stopping Google Framework. No.
Flashed SuperSU 1.65 and tried to update again. No.
Any suggestions on what I should do? Manually flash the update without loosing root or an data?
Did you reflash the ota after you flashed supersu?
What was the error message?
sfhub said:
Did you reflash the ota after you flashed supersu?
What was the error message?
Click to expand...
Click to collapse
I read the new SuperSU versions have the OTA fix built in which allows OTA update.
When I initially went to update before everything, it rebooted then just came up with the "open android guy" with an error. Not sure what it exactly said, but I ran into the problem when I updated to JSS15Q.
I updated to JSS15Q by flashing the SuperSU OTA update fix with temporary TWRP. It then went through no problem. I followed that same method this time, but it didn't work.
When I did the j to q update while rooted the ota had an error as well. I had to install the full q rom from google. (I'm stock with root and I changed the system font) But this time around when I got the r ota I double checked what version supersu was runing and its at 1.65. I applied the r ota with no errors.
church said:
When I did the j to q update while rooted the ota had an error as well. I had to install the full q rom from google. (I'm stock with root and I changed the system font) But this time around when I got the r ota I double checked what version supersu was runing and its at 1.65. I applied the r ota with no errors.
Click to expand...
Click to collapse
Yeah I'm running 1.65 currently, but the update won't show up anymore. Check for updates and there's nothing.
datallboy said:
Yeah I'm running 1.65 currently, but the update won't show up anymore. Check for updates and there's nothing.
Click to expand...
Click to collapse
If its like the last issue with J to Q. You are updated but it doesn't show the name change in system. I could be wrong. It should have already been downloaded to your tablet. Check with a root explorer to find the ota zip or download the R ota found somewhere on this forum and manually flash it. I'm glad I didn't have to mess with anything this time around.
church said:
If its like the last issue with J to Q. You are updated but it doesn't show the name change in system. I could be wrong. It should have already been downloaded to your tablet. Check with a root explorer to find the ota zip or download the R ota found somewhere on this forum and manually flash it. I'm glad I didn't have to mess with anything this time around.
Click to expand...
Click to collapse
I found a zip for the ota update, don't remember where, but should I be able just to flash it with TWRP without loosing anything?
It will lose the option to blend milkshakes
church said:
It will lose the option to blend milkshakes
Click to expand...
Click to collapse
Not asking for sarcasm, just solutions. Will I lose root or any data? Or is it just like OTA update if I do it manually.
Oh you're using twrp? Disregard what I said. I'm coming from stock with stock recovery and rooted.
church said:
Oh you're using twrp? Disregard what I said. I'm coming from stock with stock recovery and rooted.
Click to expand...
Click to collapse
Stock recovery is on my device. I'm temporarily booting TWRP with the Nexus Toolkit so I can flash things.
datallboy said:
I read the new SuperSU versions have the OTA fix built in which allows OTA update.
When I initially went to update before everything, it rebooted then just came up with the "open android guy" with an error. Not sure what it exactly said, but I ran into the problem when I updated to JSS15Q.
I updated to JSS15Q by flashing the SuperSU OTA update fix with temporary TWRP. It then went through no problem. I followed that same method this time, but it didn't work.
Click to expand...
Click to collapse
Next time you have an error with stock recovery (android fallen down) press/hold power, then press/release VolUp, then release Power.
This will show you the error log.
As to your current problem, if your unit won't download and notify you about JSS15R download it by hand and place in your virtual sdcard, then temporary boot into tarp and choose install, selecting the ota zip.
---------- Post added at 08:58 PM ---------- Previous post was at 08:55 PM ----------
datallboy said:
Not asking for sarcasm, just solutions. Will I lose root or any data? Or is it just like OTA update if I do it manually.
Click to expand...
Click to collapse
Install the ota update.zip, then before reboot, immediately install supersu.
Do it that way and you won't lose root.
Forced OTA and it failed. I had already flashed the superSU.zip before
If you can't read this is the log...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check ("/system/build.prop" [numbers and letters]
E: Error in /cache/(update file.zip)
(Status 7)
Installation aborted.
Any way to manually flash the update? Because SuperSU OTA isn't working.
So, you modified the build.prop, restore your backup of the original and it will work. Or flash the full factory image.
Guhrasoh said:
So, you modified the build.prop, restore your backup of the original and it will work. Or flash the full factory image.
Click to expand...
Click to collapse
Now that you mention it I tweaked it with PimpMyRom. I'll take that off and try to update.
I am a bit late, but I tried fixed my build.prop to its original state and I still can't OTA update...
I noticed on stock recovery there's an option to update with ADB. Is there an update file I can use to just manually install the update? I know the JSS15R update didn't do much, but I would like to know for future reference and when Android 4.4 is released.
datallboy said:
I am a bit late, but I tried fixed my build.prop to its original state and I still can't OTA update...
I noticed on stock recovery there's an option to update with ADB. Is there an update file I can use to just manually install the update? I know the JSS15R update didn't do much, but I would like to know for future reference and when Android 4.4 is released.
Click to expand...
Click to collapse
The same OTA update.zip you used before is used to do sideload in adb as well.
You'll also get the same errors if you have modified files.
If you post the errors, they can be diagnosed.
If you modified a lot of files, sometimes it is easier using the factory images.
sfhub said:
The same OTA update.zip you used before is used to do sideload in adb as well.
You'll also get the same errors if you have modified files.
If you post the errors, they can be diagnosed.
If you modified a lot of files, sometimes it is easier using the factory images.
Click to expand...
Click to collapse
Status 7 error, the log is posted in one of the above posts. I use "PimpMyROM" for a short while, which modifies the file. I deleted all the tweaks that went into the build.prop.
datallboy said:
Status 7 error, the log is posted in one of the above posts. I use "PimpMyROM" for a short while, which modifies the file. I deleted all the tweaks that went into the build.prop.
Click to expand...
Click to collapse
Unless you are very careful with your edit or made a backup, you need to get the real file. When you edit, even if you have an extra space left over, the sha1 checksum check will fail.
sfhub said:
Unless you are very careful with your edit or made a backup, you need to get the real file. When you edit, even if you have an extra space left over, the sha1 checksum check will fail.
Click to expand...
Click to collapse
I'll probably just backup apps + data and use JSS15R factory image. Made the mistake of not making a backup of my build.prop.
Good thing it's a Nexus Device!
I got the OTA update notification today, but I couldn't install because of CWM.
I modified the zip to remove the recovery check, but it's the first one I've ever done, so I'm not sure if it will work. Either way, you'll probably have to reflash CWM if it does work.
As always, I'm not responsible for anything that goes wrong with your phone. Whether it blows up, catches fire, or just bricks....not my fault.
Anways, here are both the OG and the modified versions of the OTA update.
UPDATE: I just flashed the modified zip and it installed fine. Got rid of that annoying notification and I still kept root by choosing to fix root after flashing it.
Modified
Original
SoCmodder said:
I got the OTA update notification today, but I couldn't install because of CWM.
I modified the zip to remove the recovery check, but it's the first one I've ever done, so I'm not sure if it will work. Either way, you'll probably have to reflash CWM if it does work.
As always, I'm not responsible for anything that goes wrong with your phone. Whether it blows up, catches fire, or just bricks....not my fault.
Anways, here are both the OG and the modified versions of the OTA update.
UPDATE: I just flashed the modified zip and it installed fine. Got rid of that annoying notification and I still kept root by choosing to fix root after flashing it.
Modified
Original
Click to expand...
Click to collapse
tried to flash the modified but failed
jiggajaydroid said:
tried to flash the modified but failed
Click to expand...
Click to collapse
Are you on the stock rom? I'm not sure it will work if you're on the deodexed one.
tried flashing the modified one on a stock rooted rom. Firmware portion gave failure notice.. Seems like build.prop has new version but i'm still getting update nag
I'll be posting a full OTA zip for rooted users that contains the full updated files in a bit (not just the patch.p files)
CNexus said:
I'll be posting a full OTA zip for rooted users that contains the full updated files in a bit (not just the patch.p files)
Click to expand...
Click to collapse
Thank you, Sir!!
CNexus said:
I'll be posting a full OTA zip for rooted users that contains the full updated files in a bit (not just the patch.p files)
Click to expand...
Click to collapse
Thanks!
will this wipe the phone ? will i loose root ? i am s-on . can i flash over bone stock rom ?
thanks
andybones said:
Thank you, Sir!!
Click to expand...
Click to collapse
Are you planning on updating your bonestock rom with this OTA Andy, or is it not worth it since it's a relatively small one?
Sent from my HTC6500LVW using xda app-developers app
red rage said:
will this wipe the phone ? will i loose root ? i am s-on . can i flash over bone stock rom ?
thanks
Click to expand...
Click to collapse
Would like to know this too as i am bootloader unlocked with s-on and rooted. if this will patch my bootloader, what service do i freeze to avoid getting the nagging OTA notification?
Thanks
I am s-on, but unlocked and rooted. I'm still unlocked and I'm still rooted after applying this update. I wouldn't recommend doing it on another Rom though. It would probably fail.
Sent from my HTC6500LVW using Tapatalk 2
I am s-off with rumrunner can i just flash the modified OTA?
thewagdy said:
I am s-off with rumrunner can i just flash the modified OTA?
Click to expand...
Click to collapse
If you still have stock recovery yes. Then flash custom recovery and su. Choose the nonmodified one.
Sent from my Nexus 7 using Tapatalk 4
dottat said:
If you still have stock recovery yes. Then flash custom recovery and su. Choose the nonmodified one.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I already have custom recovery
thewagdy said:
I already have custom recovery
Click to expand...
Click to collapse
Check this then.. http://forum.xda-developers.com/showthread.php?t=2469057
Sent from my Nexus 7 using Tapatalk 4
SoCmodder said:
I got the OTA update notification today, but I couldn't install because of CWM.
I modified the zip to remove the recovery check, but it's the first one I've ever done, so I'm not sure if it will work. Either way, you'll probably have to reflash CWM if it does work.
As always, I'm not responsible for anything that goes wrong with your phone. Whether it blows up, catches fire, or just bricks....not my fault.
Anways, here are both the OG and the modified versions of the OTA update.
UPDATE: I just flashed the modified zip and it installed fine. Got rid of that annoying notification and I still kept root by choosing to fix root after flashing it.
Modified
Original
Click to expand...
Click to collapse
The original is unrooted and signed? I need to be able to flash it via stock recovery or in RUU. Need to get someone back to .10 for rumrunner.
BreakingVZW said:
The original is unrooted and signed? I need to be able to flash it via stock recovery or in RUU. Need to get someone back to .10 for rumrunner.
Click to expand...
Click to collapse
This is just the update files from .08 to .10. They aren't full roms. There is another thread with stock roms, but I'm not sure about stock recovery. You may have to pull it from the RUU.