Develop Bugs

Help! - Can't upgrade radio

I am trying to install 2.2 but i can't get past the radio update.
First i rooted my incredible with unrevoked3 then realized i needed to update the radio. So i followed the directions from this forum to upgrade the radio to 2.X from a rooted phone. I installed the stock BP31IMG, downloaded the dinc_ota to my SD, renamed it to update.zip and booted to recovery. Upon running the update it gives the following messages.
Finding update package
Opening update package
Installing update
Verifying current system
assert failed: apply_patch_check("/system/lib/modules/bcm4329.ko . "f6c9098e3fd8e6caef864f35090043561987e9f8")
E:Error in /sdcard/update.zip
(Status 7)
Installation Aborted
I formatted my SD and downloaded the dinc_ota from a few different sources but i still get the same message.
Anyone have any ideas?

okrk said:
I am trying to install 2.2 but i can't get past the radio update.
First i rooted my incredible with unrevoked3 then realized i needed to update the radio. So i followed the directions from this forum to upgrade the radio to 2.X from a rooted phone. I installed the stock BP31IMG, downloaded the dinc_ota to my SD, renamed it to update.zip and booted to recovery. Upon running the update it gives the following messages.
Finding update package
Opening update package
Installing update
Verifying current system
assert failed: apply_patch_check("/system/lib/modules/bcm4329.ko . "f6c9098e3fd8e6caef864f35090043561987e9f8")
E:Error in /sdcard/update.zip
(Status 7)
Installation Aborted
I formatted my SD and downloaded the dinc_ota from a few different sources but i still get the same message.
Anyone have any ideas?
Click to expand...
Click to collapse
Download it again
Sent from my ADR6300 using XDA App

jdkoreclipse said:
Download it again
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Like i said I downloaded it from 2 or 3 different sources all giving the same error.

On your phone or pc
Sent from my ADR6300 using XDA App

Register your phone with Google (sign into your Google account on your phone)
HTC Incredible, rooted w/ modified Sense 2.1

jdkoreclipse said:
On your phone or pc
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Downloaded on my pc and transferred to phone. Are you saying i must download it using the phone?

If you cant do it through your PC try using your phone... Go through the Google Account Setup then download Astro File Manager.. Download the OTA update through your phone from whatever source, then use Astro to rename it to update.zip ; then just go into recovery and apply it.

I think you have to apply the first OTA that everyone received shortly after launch that fixed exchange issues prior to applying the radio update.

ilinfinityil said:
Register your phone with Google (sign into your Google account on your phone)
HTC Incredible, rooted w/ modified Sense 2.1
Click to expand...
Click to collapse
I am already registered - Why should i sign in to google? What are you saying? What next?

Reddog80p said:
I think you have to apply the first OTA that everyone received shortly after launch that fixed exchange issues prior to applying the radio update.
Click to expand...
Click to collapse
Yep thats what fixed my issue with it
basically the order should be:
if rooted run PB31IMG.zip
complete the setup process on first boot and run Verizon's first (and only right now) official OTA update that you will receive
rename dinc_ota.zip to update.zip and from the stock recovery update the radio
from there reboot and you should have the new baseband
Note: apparently don't run dinc_ota.zip more then once or you can brick the phone, so be careful, however the failed updates you have been doing i dont think count cause i must have done that at least 4 times lol
follow the official instructions here:
forum.xda-developers. com/showthread.php?t=737400
Good luck!

mechinn said:
Yep thats what fixed my issue with it
basically the order should be:
if rooted run PB31IMG.zip
complete the setup process on first boot and run Verizon's first (and only right now) official OTA update that you will receive
rename dinc_ota.zip to update.zip and from the stock recovery update the radio
from there reboot and you should have the new baseband
Note: apparently don't run dinc_ota.zip more then once or you can brick the phone, so be careful, however the failed updates you have been doing i dont think count cause i must have done that at least 4 times lol
follow the official instructions here:
forum.xda-developers. com/showthread.php?t=737400
Good luck!
Click to expand...
Click to collapse
Great - Thanks
Now where can i find this OTA from verizon?

okrk said:
Great - Thanks
Now where can i find this OTA from verizon?
Click to expand...
Click to collapse
Try going to about phone>system updates and manually checking.

Reddog80p said:
Try going to about phone>system updates and manually checking.
Click to expand...
Click to collapse
It says my phone is up to date- nothing is available to install
Any other suggestions?

I just flashed back to stock for $hits and giggles and I'm in the same boat as you lol.

Reddog80p said:
I just flashed back to stock for $hits and giggles and I'm in the same boat as you lol.
Click to expand...
Click to collapse
I guess that proves i'm not crazy.

okrk said:
I am already registered - Why should i sign in to google? What are you saying? What next?
Click to expand...
Click to collapse
Heh, idk bro. I installed the official OTA update for 2.1 and then signed into my Google account and it worked for me.
HTC Incredible, rooted w/ modified Sense 2.1

ilinfinityil said:
Heh, idk bro. I installed the official OTA update for 2.1 and then signed into my Google account and it worked for me.
HTC Incredible, rooted w/ modified Sense 2.1
Click to expand...
Click to collapse
How did you do that - Where in google do you find the ota.

ilinfinityil said:
Heh, idk bro. I installed the official OTA update for 2.1 and then signed into my Google account and it worked for me.
HTC Incredible, rooted w/ modified Sense 2.1
Click to expand...
Click to collapse
Did you go back to stock then apply the radio update zip or did you already have the first OTA from about 2 months ago then flash the new radio OTA?

Come on PPL - Hasn't anyone encountered this and figured it out?

I'm applying the radio update now. It seems to be working. I did not get any error and it's going through the green arrow over the phone screen now. I just went to stock then ran the update.zip from recovery.
Make sure that you rename "dinc_ota" to update. Then boot into recovery and then select "apply update.zip"

OTA Update failed

Woke up this morning and saw the system update message. It started to update but then I got a picture of the android with a red triangle. That stayed for a few minutes and the phone rebooted. Now I am still on 4.0.1 and there is no system update available.
Any thoughts as to what caused this or how to get the update to process?

For me the same problem.
I think something went wrong during the update. The installation of the update was already 30 minutes ongoing and nothing happened. After resetten the phone it started up with still 4.0.1 and no system update availiable.
Anyone an idee what went wrong?
---------- Post added at 11:53 AM ---------- Previous post was at 11:13 AM ----------
chrisjaffe said:
Woke up this morning and saw the system update message. It started to update but then I got a picture of the android with a red triangle. That stayed for a few minutes and the phone rebooted. Now I am still on 4.0.1 and there is no system update available.
Any thoughts as to what caused this or how to get the update to process?
Click to expand...
Click to collapse
See following guide : http://forum.xda-developers.com/showthread.php?p=20843237
Worked for me. The problem is that I have CWM recovery installed.

People use this phone on stock?
Sent from my Galaxy Nexus using Tapatalk

I'm having the same problem. I think it's because CWM borks the update. Any ideas anyone? I was hoping to only do OTA updates until/if I start installing custom roms.

chrisjaffe said:
Woke up this morning and saw the system update message. It started to update but then I got a picture of the android with a red triangle. That stayed for a few minutes and the phone rebooted. Now I am still on 4.0.1 and there is no system update available.
Any thoughts as to what caused this or how to get the update to process?
Click to expand...
Click to collapse
You cannot install OTA the updates if you are rooted and have Clockwork Recovery installed. The only way you can update to 4.0.2 is to either install one of the many custom roms available or revert back to the stock recovery.

dr9722 said:
You cannot install OTA the updates if you are rooted and have Clockwork Recovery installed. The only way you can update to 4.0.2 is to either install one of the many custom roms available or revert back to the stock recovery.
Click to expand...
Click to collapse
Not true:
http://forum.xda-developers.com/showthread.php?p=20843237

Laintsurge said:
I'm having the same problem. I think it's because CWM borks the update. Any ideas anyone? I was hoping to only do OTA updates until/if I start installing custom roms.
Click to expand...
Click to collapse
Yeah, I had the same problem, but see link from above: http://forum.xda-developers.com/showthread.php?p=20843237

dr9722 said:
You cannot install OTA the updates if you are rooted and have Clockwork Recovery installed. The only way you can update to 4.0.2 is to either install one of the many custom roms available or revert back to the stock recovery.
Click to expand...
Click to collapse
True.
EddyOS said:
Not true:
http://forum.xda-developers.com/showthread.php?p=20843237
Click to expand...
Click to collapse
Your link contradicts your reply.

Thanks for the replies all.
The problem is that I do not have CWM installed, and my GN is not rooted. I am very happy with stock ICS so this is the first phone I have had in over 10 years that I have not installed a custom ROM on.
One thing to note is that I did force the install of 4.0.1. I was experiencing the volume bug and had to leave on a road trip so i could not wait for the first OTA to roll out to me. But to do that I did fastboot boot not fastboot flash for CWM so after a reset I am back on the stock recovery.
So any other ideas how to get the update to restart? The bootloader is obviously unlocked if that makes any difference.
Thanks,
cj

sstang2006 said:
True.
Your link contradicts your reply.
Click to expand...
Click to collapse
I'm not sure what you are reading, but here it is:
1) Whether you have root or not, it makes no difference.
2) Having CWM vs. stock recovery does make a difference, but only somewhat. In both cases, you CAN install the OTA update. It's just that the procedure is a little different. With the stock recovery, the OTA will install automatically. With a custom recovery (like CWM) it will install, but you have to install it manually.

efrant said:
I'm not sure what you are reading, but here it is:
1) Whether you have root or not, it makes no difference.
2) Having CWM vs. stock recovery does make a difference, but only somewhat. In both cases, you CAN install the OTA update. It's just that the procedure is a little different. With the stock recovery, the OTA will install automatically. With a custom recovery (like CWM) it will install, but you have to install it manually.
Click to expand...
Click to collapse
1- No one said root will make a difference.
2- This thread is regarding a user who receives an OTA update. If he does not have the factory recovery it will fail.

chrisjaffe said:
Woke up this morning and saw the system update message. It started to update but then I got a picture of the android with a red triangle. That stayed for a few minutes and the phone rebooted. Now I am still on 4.0.1 and there is no system update available.
Any thoughts as to what caused this or how to get the update to process?
Click to expand...
Click to collapse
sstang2006 said:
1- No one said root will make a difference.
2- This thread is regarding a user who receives an OTA update. If he does not have the factory recovery it will fail.
Click to expand...
Click to collapse
Unless I'm reading the original post incorrectly, the thread is about a user who received the OTA update and it didn't install. His questions were: 1) What caused this? and 2) How to get the update to process?
Saying that the OTA will fail if he doesn't have the stock recovery, I suppose, addresses his questions but, instead of just saying that, would it not be more helpful to tell him that the OTA doesn't install automatically with CWM, it just needs a different install process, which EddyOS pointed him to), instead of just saying it will fail. In any case, you are correct -- lets just tell all users to flash back the stock recovery to install OTA updates.

I have the same problem. I flashed google Yakju images over my bell yakjuxx images. Boot loader is unlocked obviously but not rooted and no cwm.
I did however flash a different radio, not sure if that was my issue. Now the update has disappeared so I can't retry.

Quidlor said:
I have the same problem. I flashed google Yakju images over my bell yakjuxx images. Boot loader is unlocked obviously but not rooted and no cwm.
I did however flash a different radio, not sure if that was my issue. Now the update has disappeared so I can't retry.
Click to expand...
Click to collapse
Again, see the thread that EddyOS and davomgz linked to above. Instructions are there. Make sure your read the thread, and not just the first post.

efrant said:
Unless I'm reading the original post incorrectly, the thread is about a user who received the OTA update and it didn't install. His questions were: 1) What caused this? and 2) How to get the update to process?
Saying that the OTA will fail if he doesn't have the stock recovery, I suppose, addresses his questions but, instead of just saying that, would it not be more helpful to tell him that the OTA doesn't install automatically with CWM, it just needs a different install process, which EddyOS pointed him to), instead of just saying it will fail. In any case, you are correct -- lets just tell all users to flash back the stock recovery to install OTA updates.
Click to expand...
Click to collapse
In his first post he did not specify which recovery he had.
chrisjaffe said:
Thanks for the replies all.
The problem is that I do not have CWM installed, and my GN is not rooted. I am very happy with stock ICS so this is the first phone I have had in over 10 years that I have not installed a custom ROM on.
One thing to note is that I did force the install of 4.0.1. I was experiencing the volume bug and had to leave on a road trip so i could not wait for the first OTA to roll out to me. But to do that I did fastboot boot not fastboot flash for CWM so after a reset I am back on the stock recovery.
So any other ideas how to get the update to restart? The bootloader is obviously unlocked if that makes any difference.
Thanks,
cj
Click to expand...
Click to collapse
(I suppose you have the GSM version because of your ATT logo)
As you are describing right now, you are not rooted and in stock recovery.
Try flashing manually the OTA 4.0.2 which you can find here: http://download.peteralfonso.com/maguro
If it fails, then the original OTA 4.0.1 you forced was not the real OTA from google, so reflash the 4.0.1 from the above link and then flash 4.0.2.
If you have he CDMA version then find the OTA for that.

efrant said:
Again, see the thread that EddyOS and davomgz linked to above. Instructions are there. Make sure your read the thread, and not just the first post.
Click to expand...
Click to collapse
Thanks efrant! Those instructions worked.
I DID however discover something that I have not seen posted anywhere.
It would appear (for obvious reasons) that the OTA updates checks for version integrity. Due to me installing a different radio (Bell GN radio) the OTA update aborted itself and I saw the abort again when trying to manually update. This time I could see that the "radio" was mentioned and aborted. I re-installed the original Yakju radio from ITL41F and did the manual OTA update and it worked!
Now I just have to re-install the Bell GN radio image.

Quidlor said:
Thanks efrant! Those instructions worked.
I DID however discover something that I have not seen posted anywhere.
It would appear (for obvious reasons) that the OTA updates checks for version integrity. Due to me installing a different radio (Bell GN radio) the OTA update aborted itself and I saw the abort again when trying to manually update. This time I could see that the "radio" was mentioned and aborted. I re-installed the original Yakju radio from ITL41F and did the manual OTA update and it worked!
Now I just have to re-install the Bell GN radio image.
Click to expand...
Click to collapse
Yeah, I should mention that in the first post. (You could have also removed the assert in the updater-script file, and it would have installed.)

efrant said:
Yeah, I should mention that in the first post. (You could have also removed the assert in the updater-script file, and it would have installed.)
Click to expand...
Click to collapse
Can I prevent this problem for future OTA updates? Say 4.0.3 is pushed out, should I remove the assert in the update-script file now? or wait until it says "there's an update available"?
I don't want to have to manually update every time because I used a different radio.

Thank you very much for the answers. I did not mean to cause such a fuss. I am aware of how to flash the image manually, as I did that to force the 4.0.1 update.
I guess what (as it turns out) I was really asking was, What caused this to stop? And how to I retry/restart the automatic update?
The only other info that I can think that is relevant here is that I am sure that I forced the actual OTA. I wonder if something happened during the flash, or since, that corrupted something that the update is checking.
Oh and it is an unlocked GSM Nexus though I am currently in the UK for about 6 months so I have given up my ATT contract for a Pay-as-you-go Lebara SIM while here.
Thanks again for the answers, next time I'll try to be more clear the first time.
cj

Quidlor said:
Can I prevent this problem for future OTA updates? Say 4.0.3 is pushed out, should I remove the assert in the update-script file now? or wait until it says "there's an update available"?
I don't want to have to manually update every time because I used a different radio.
Click to expand...
Click to collapse
When the next update comes out, you can either either flash back the original radio before updating, or remove the assert in the update-script file in the new update.

[Q] Trouble with updating OTA to JB

I'm currently using the stock rom from Google (4.0.4) after updating it from 4.0.1 which originally shipped with my device (manually, not OTA). Just yesterday I decided to update my phone to JB through the OTA update. It downloads perfectly fine but when it reboots into the installation, I get the error with the android mascot and red exclamation mark.
-- Install /cache ...
Finding update package ...
Opening update package ...
Verifying update package ...
Installing update ...
Verifying current system ...
assert failed: apply_patch_check("EMMC:/dev/block/platform/omap/omap_hsmmc.0/by-name/radio:12583168:8b7209e8c3a6d73254ad92069aabe693beffd6bd:12583168:47b1799049e32ef2c0746ca716f5277a83768b96")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
I'm pretty sure it manages to download perfectly fine since the file is still in my cache (filename is f946a4120eb1.signed-yakju-JR003C-from-IMM761.f946a412.zip) Anyone able to help me with this?

spaceinvad3rs said:
I'm currently using the stock rom from Google (4.0.4) after updating it from 4.0.1 which originally shipped with my device (manually, not OTA). Just yesterday I decided to update my phone to JB through the OTA update. It downloads perfectly fine but when it reboots into the installation, I get the error with the android mascot and red exclamation mark.
I'm pretty sure it manages to download perfectly fine since the file is still in my cache (filename is f946a4120eb1.signed-yakju-JR003C-from-IMM761.f946a412.zip) Anyone able to help me with this?
Click to expand...
Click to collapse
You do not have the XXLA2 radio flashed. You need to flash that before applying the update.

Thanks for that. I've also got another question. I currently can't access clockwork mod through the recovery menu, after updating it to 4.0.4 I wasn't able to access it anymore. I've tried the rom manager from the play store but it says something that I don't have permission. I think I forgot to install the super user when I initially installed the update to 4.0.4.

I agree, you have to be careful with each rom's compatibility. 4.0.4 brought with it new radios which I believe most if not all jb roms are based on. You can flash the new radios after rooting and unlocking the device. If you manually root the phone, you'll know if you successfully pushed su to your sd card.
Sent from my Galaxy Nexus using xda app-developers app

spaceinvad3rs said:
Thanks for that. I've also got another question. I currently can't access clockwork mod through the recovery menu, after updating it to 4.0.4 I wasn't able to access it anymore. I've tried the rom manager from the play store but it says something that I don't have permission. I think I forgot to install the super user when I initially installed the update to 4.0.4.
Click to expand...
Click to collapse
1) every ota update disables root access.
2) every ota update places two files on your device that re-flash the stock recovery every time you boot your phone.
3) the android laying on its back with the exclamation point IS the stock recovery.
4) you need to flash cwm, flash the su package, then rename/delete this file: /system/etc/install-recovery.sh and you are all set.
Sent from my Galaxy Nexus using Tapatalk 2

[Q]OTA failed with stock recovery

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

[Q] OTA JSS15R While Rooted

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!