Related
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"
Hello,
is there an OTA package which i can flash with a stock recovery (my phone i locked, i don't like to have an unlocked bootloader)?
I am on 4.0.2 right now...
No, you need to be rooted or unlocked to flash the OTA package. Just wait for the official one, it will probably be pushed sometime during easter
I'm still waiting for the OTA aswell
I was pretty sure that the OTA process just downloads a file which will be flashed via the stock recovery. So if someone would have this stock OTA package (update.zip) i can just place in the internal storage and reboot into stock recovery. At least on my HTC Hero at 1.5 -> 1.6 it was working this way...must have remembered something wrong there...
bluefisch200 said:
Hello,
is there an OTA package which i can flash with a stock recovery (my phone i locked, i don't like to have an unlocked bootloader)?
I am on 4.0.2 right now...
Click to expand...
Click to collapse
Haven't tried it myself (since I am rooted and unlocked) but I recon that you can unlock (and loose ALL your data), root, flash the onetime CWM Recovery, flash the 4.0.4 stock image (by which you will loose root), relock (and loose ALL your data again).
At the end you would be completely stock again. That can all be done through the GNEX toolkit by Mskip that can be found here: Link.
You can download the official Google image from here: Link
bluefisch200 said:
I was pretty sure that the OTA process just downloads a file which will be flashed via the stock recovery. So if someone would have this stock OTA package (update.zip) i can just place in the internal storage and reboot into stock recovery. At least on my HTC Hero at 1.5 -> 1.6 it was working this way...must have remembered something wrong there...
Click to expand...
Click to collapse
that was probably right with the htc hero, also on my htc desire..because the ota package was picked by the stock recovery from the sdcard
but the stock recovery on our galaxy nexus with ics, expect the ota to be on the /cache partition..without root u can't write in that partition, only the os itself can write there
bluefisch200 said:
Hello,
is there an OTA package which i can flash with a stock recovery (my phone i locked, i don't like to have an unlocked bootloader)?
I am on 4.0.2 right now...
Click to expand...
Click to collapse
If you are on yakju, root using this method (note you only need temp root, so only do up to step 6), then place the update file from here to /cache and reboot into stock recovery and flash.
efrant said:
If you are on yakju, root using this method (note you only need temp root, so only do up to step 6), then place the update file from here to /cache and reboot into stock recovery and flash.
Click to expand...
Click to collapse
Thank you
Btw. it's easier to just root the OS (go above step 6) instead of only go to 6...for the cp command you will need busybox...i have seen "cat" somewhere but i couldn't figure out how it works...but i seems to be that you can copy files without installing busybox since cat is supported from android at stock...
bluefisch200 said:
Thank you
Btw. it's easier to just root the OS (go above step 6) instead of only go to 6...for the cp command you will need busybox...i have seen "cat" somewhere but i couldn't figure out how it works...but i seems to be that you can copy files without installing busybox since cat is supported from android at stock...
Click to expand...
Click to collapse
Correct, that is why I used cat in my directions instead of cp, as you would not have busybox installed if you are not root...
I'm still on 4.0.1
Is there any way to force an OTA update to 4.0.2 or 4.0.4 without rooting. Or manually install an update with a .zip update through stock recovery rather than CWM. I am unable to get any OTA updates it says my system is up to date which it clearly isnt.
Merio90 said:
Is there any way to force an OTA update to 4.0.2 or 4.0.4 without rooting. Or manually install an update with a .zip update through stock recovery rather than CWM. I am unable to get any OTA updates it says my system is up to date which it clearly isnt.
Click to expand...
Click to collapse
No..................
Sent from my Galaxy Nexus using Tapatalk
Hi guys, each time that I try to upgrade 4.04 by OTA, it stopped and appear the Android with the red exclamation on it.
I've used the 'WugFresh unlocked toolkit' to root/unlock Galaxy Nexus.
For install OTA 4.0.4 from Google, I need to lock the phone again?
If I back to default configs - using WugFresh again - the OTA, and after the root/unlock, work without problems?
Thanks.
That's the stock recovery you're seeing.
What images have you changed?
If you revert to the stock ones (radio/bootloader/etc) you should get the OTA.
Jubakuba said:
That's the stock recovery you're seeing.
What images have you changed?
If you revert to the stock ones (radio/bootloader/etc) you should get the OTA.
Click to expand...
Click to collapse
Why dont you show this guy the light and let him flash google factory image by himself..
OP: there you go http://forum.xda-developers.com/showthread.php?p=23229558
Galaxy Nexus AOKP m5 Franco kernel m3
Thank you, guys.
RaptorHawk said:
Hi guys, each time that I try to upgrade 4.04 by OTA, it stopped and appear the Android with the red exclamation on it.
I've used the 'WugFresh unlocked toolkit' to root/unlock Galaxy Nexus.
For install OTA 4.0.4 from Google, I need to lock the phone again?
If I back to default configs - using WugFresh again - the OTA, and after the root/unlock, work without problems?
Thanks.
Click to expand...
Click to collapse
You are seen that screen because you have something on your device that is not stock. (Unlocked and rooted makes no difference.)
To be 100% sure that an OTA update will install automatically, you need to have all of the following:
1) the radio that came with the ROM that you are using;
2) the stock recovery that came with the ROM that you are using;
3) the stock kernel that came with the ROM that you are using;
4) all of the original files in /system that came with the ROM that you are using.
Have a look at the thread here. It is for manual installation of an update, but the requirements still apply to an automatic update OTA.
So if I uninstalled apps to the system and do the lock/unroot, this will cause problems when I try to upgrade from version 4.0.2 to version 4.0.4?
I uninstalled Google Maps, Youtube and Earth.
RaptorHawk said:
So if I uninstalled apps to the system and do the lock/unroot, this will cause problems when I try to upgrade from version 4.0.2 to version 4.0.4?
I uninstalled Google Maps, Youtube and Earth.
Click to expand...
Click to collapse
You are not reading at all at what efrant says and you havent looked at the link i provided.. Until you do so you wont go farther
Galaxy Nexus AOKP m5 Franco kernel m3
Yes, I read, but maybe I did not quite understand ...
To recap: I used Wug's Toolkit and now I can no longer install the 4.0.4 update official Google OTA. So I would like to know how to undo it, install 4.0.4 and then apply the Wug toolkit again.
According to the links, I need to undo the changes before, but I can not undo the root by Wug's Toolkit, because he can not download a file, appear an error message that could not be found.
What I wonder is, how to get back to what it was prior to applying the 4.0.4 update and then do the root again? Is that possible?
Thanks.
Forget about toolkits, follow this guide please
http://forum.xda-developers.com/showthread.php?p=25477039
Galaxy Nexus AOKP m5 Franco kernel m3
RaptorHawk said:
Yes, I read, but maybe I did not quite understand ...
To recap: I used Wug's Toolkit and now I can no longer install the 4.0.4 update official Google OTA. So I would like to know how to undo it, install 4.0.4 and then apply the Wug toolkit again.
According to the links, I need to undo the changes before, but I can not undo the root by Wug's Toolkit, because he can not download a file, appear an error message that could not be found.
What I wonder is, how to get back to what it was prior to applying the 4.0.4 update and then do the root again? Is that possible?
Thanks.
Click to expand...
Click to collapse
There are two ways to get 4.0.4:
1) Flash a full 4.0.4 ROM, which is what the link msedek posted is.
2) Upgrade 4.0.2 to 4.04, which is the link I posted a couple of posts back.
In the first case, you easily end up with a clean install, but your data is erased (so back up before)
In the second case, you need to make sure that you undo any modifications you made to the /system partition, the kernel, the radio, and the recovery. Then you apply the update, and you will have an upgraded ROM with all your data and settings intact.
RaptorHawk said:
So if I uninstalled apps to the system and do the lock/unroot, this will cause problems when I try to upgrade from version 4.0.2 to version 4.0.4?
I uninstalled Google Maps, Youtube and Earth.
Click to expand...
Click to collapse
Actually, this is true. I was having the same issues. When i rooted, I deleted system apps I did not want. For weeks and weeks I kept receiving the popup message saying that the update to 4.0.4 was available. When attempting to upgrade, it would always fail on reboot.
Just two days ago, I received the upgrade notice again. I immediately went into Recovery mode, and attempted to manually install the update file from the system directory. When I did, I received an error right away saying the update could not find "TabletBooks.apk" (I deleted Google Play Books since I dont use it).
I reinstalled a clean image of 4.0.2 I made with ROM Manager weeks ago, then applied the update to 4.0.4 again, and it ran smoothly with no errors, since all System apps were installed with the clean image I saved.
Hope this helps...
PaisanNYC said:
Actually, this is true. I was having the same issues. When i rooted, I deleted system apps I did not want. For weeks and weeks I kept receiving the popup message saying that the update to 4.0.4 was available. When attempting to upgrade, it would always fail on reboot.
Just two days ago, I received the upgrade notice again. I immediately went into Recovery mode, and attempted to manually install the update file from the system directory. When I did, I received an error right away saying the update could not find "TabletBooks.apk" (I deleted Google Play Books since I dont use it).
I reinstalled a clean image of 4.0.2 I made with ROM Manager weeks ago, then applied the update to 4.0.4 again, and it ran smoothly with no errors, since all System apps were installed with the clean image I saved.
Hope this helps...
Click to expand...
Click to collapse
If you are going to install a clean image anyway, it doesn't make much sense to install 4.0.2 and upgrade to 4.0.4. Just install the 4.0.4 image immediately...
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
If you are going to install a clean image anyway, it doesn't make much sense to install 4.0.2 and upgrade to 4.0.4. Just install the 4.0.4 image immediately...
Click to expand...
Click to collapse
Because you cant just download the full 4.0.4 image and install it via Recovery, can you? I thought you can only install the full image via ADB?
I was able to do all of this while sitting down in the lil boys room, doing my business LOL
PaisanNYC said:
Because you cant just download the full 4.0.4 image and install it via Recovery, can you? I thought you can only install the full image via ADB?
I was able to do all of this while sitting down in the lil boys room, doing my business LOL
Click to expand...
Click to collapse
LOL!
Well, I'm not sure where you got a stock 4.0.2 CWM-flashable file, but FYI, you can flash 4.0.4 the same way if you have a 4.0.4 CWM-flashable file (or just replace the 4.0.2 image with the 4.0.4 image in the same CWM-flashable file.
efrant said:
LOL!
Well, I'm not sure where you got a stock 4.0.2 CWM-flashable file, but FYI, you can flash 4.0.4 the same way if you have a 4.0.4 CWM-flashable file (or just replace the 4.0.2 image with the 4.0.4 image in the same CWM-flashable file.
Click to expand...
Click to collapse
Thanks, that's good to know! I come from HTC phones (G1, Nexus One, etc), so Samsung and modding is kinda new to me.
I had a CWM-flashable 4.0.2 file because ROM Manager created the image for me when I first rooted and wanted a backup of a clean stock ROM. I wouldnt even know where to find a CWM-flashable 4.0.4 file on the web. I only know of the stock source files Google has posted. I read that those files can only be flashed with ADB on a PC.
Thanks again!
PaisanNYC said:
Thanks, that's good to know! I come from HTC phones (G1, Nexus One, etc), so Samsung and modding is kinda new to me.
I had a CWM-flashable 4.0.2 file because ROM Manager created the image for me when I first rooted and wanted a backup of a clean stock ROM. I wouldnt even know where to find a CWM-flashable 4.0.4 file on the web. I only know of the stock source files Google has posted. I read that those files can only be flashed with ADB on a PC.
Thanks again!
Click to expand...
Click to collapse
Oh, you were referring to a CWM backup. I understand now.
But regardless, you can still flash the Google images via CWM, they just have to be packaged up in a CWM-flashable zip.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks for all help. I'm succesfull flash my GNex.
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!
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!