Related
I am trying to apply to OTA update I got today, but for some reason it crashes half way through un-packaging the installer. Is this because I am rooted? Anyone else having an issue with the update?
codykeith said:
I am trying to apply to OTA update I got today, but for some reason it crashes half way through un-packaging the installer. Is this because I am rooted? Anyone else having an issue with the update?
Click to expand...
Click to collapse
What are you using to try to update? You are going to lose root if this is an OTA update.
Yellowcard8992 said:
What are you using to try to update? You are going to lose root if this is an OTA update.
Click to expand...
Click to collapse
It just came up on my phone and asked if I wanted to download it. I did, and it ask if I wanted to install. I clicked yes. It rebooted, got 1/4 of the way done with unpacking and froze up. I am guessing that its conflicting with the rooting. So I can't install any updates or I will lose root?
I don't think this update does much to anything I use.
codykeith said:
It just came up on my phone and asked if I wanted to download it. I did, and it ask if I wanted to install. I clicked yes. It rebooted, got 1/4 of the way done with unpacking and froze up. I am guessing that its conflicting with the rooting. So I can't install any updates or I will lose root?
I don't think this update does much to anything I use.
Click to expand...
Click to collapse
It was mainly radios and and pri update with new software update. And yes you will lose root. You can just install a rom that is based off this ota if you really want it.
Yellowcard8992 said:
It was mainly radios and and pri update with new software update. And yes you will lose root. You can just install a rom that is based off this ota if you really want it.
Click to expand...
Click to collapse
I want swype, mainly. I tried to install it from their website, but it says it can't install because its available OTA for EVO.
codykeith said:
I want swype, mainly. I tried to install it from their website, but it says it can't install because its available OTA for EVO.
Click to expand...
Click to collapse
Then you can just download a rom that has it included and then pull the apk from the rom.
You NEVER want to take an OTA from Sprint if you are rooted. It will cause complications like that which may cause you to have a corrupted ROM. Always update to a ROOTED OTA. Check my stickied post in Q+A at the top. You will find the link to the stock ROOTED 3.70.651.5 version you can update along with any PRI and Radios.
rooted rom
get this http://forum.xda-developers.com/showthread.php?t=758197
How do you prevent an DInc from updating to gingerbread 2.3.4?
I'm getting a nag to restart and install. This happened once some time ago, and now it's happening again.
Has 2.3.4 been rooted yet? Last time I checked, it hadn't.
Thanks
Anthony
anicotra said:
How do you prevent an DInc from updating to gingerbread 2.3.4?
I'm getting a nag to restart and install. This happened once some time ago, and now it's happening again.
Has 2.3.4 been rooted yet? Last time I checked, it hadn't.
Thanks
Anthony
Click to expand...
Click to collapse
What build version are you getting prompted to update to? If its 4.08.605.2 it's the newest that started today apparently. If I were you I would pull the file from your cache so devs could see what's in it. Also, if you have a custom recovery, it won't update, as it needs stock recovery to update. If you're S-OFF that'd help too.
frostincredible said:
What build version are you getting prompted to update to? If its 4.08.605.2 it's the newest that started today apparently. If I were you I would pull the file from your cache so devs could see what's in it. Also, if you have a custom recovery, it won't update, as it needs stock recovery to update. If you're S-OFF that'd help too.
Click to expand...
Click to collapse
Does that mean I can let it install and it will fail? I am using CWM.
frostincredible said:
What build version are you getting prompted to update to? If its 4.08.605.2 it's the newest that started today apparently. If I were you I would pull the file from your cache so devs could see what's in it. Also, if you have a custom recovery, it won't update, as it needs stock recovery to update. If you're S-OFF that'd help too.
Click to expand...
Click to collapse
I'm rooted with cam and s-off.
So, where does it put the download. I looked everywhere for an 87.8mb file and didn't find one.
anicotra said:
I'm rooted with cam and s-off.
So, where does it put the download. I looked everywhere for an 87.8mb file and didn't find one.
Click to expand...
Click to collapse
If you have root explorer it might be in your cache folder.
frostincredible said:
What build version are you getting prompted to update to? If its 4.08.605.2 it's the newest that started today apparently. If I were you I would pull the file from your cache so devs could see what's in it. Also, if you have a custom recovery, it won't update, as it needs stock recovery to update. If you're S-OFF that'd help too.
Click to expand...
Click to collapse
I found the download in cache and moved it somewhere else. It's version is
4.06.605.3-3.26.605.1_release_210690
anicotra said:
I found the download in cache and moved it somewhere else. It's version is
4.06.605.3-3.26.605.1_release_210690
Click to expand...
Click to collapse
Hm...that's the first GB OTA that was "supposedly" (I didn't get it) pushed I Sept. but yes if you have CWM it will do the countdown to reboot, then never reboot.
Android Central's reporting another OTA being pushed out tonight.
http://www.androidcentral.com/new-gingerbread-ota-droid-incredible-being-pushed-out
mik rom inc HD is getting that update message also
Run your backup and then use root explorer and go to system/etc/security/otacerts.zip and change the name to something else and then you won't have to worry about getting it again. I'm not sure if you can get to it that way with Gingerbread but just look for the security folder and the otacerts.zip.
i just got this now and i am on skyraider.
Renaming ota certs.zip didn't work for me...
I have Skyraider 4.0 installed, with s-off, Clockwork recovery, and I'm still getting this annoying notification...any other ideas?
sccafun said:
I have Skyraider 4.0 installed, with s-off, Clockwork recovery, and I'm still getting this annoying notification...any other ideas?
Click to expand...
Click to collapse
Try flashing this:
http://forum.xda-developers.com/showthread.php?p=19370543
jermaine151 said:
Try flashing this:
http://forum.xda-developers.com/showthread.php?p=19370543
Click to expand...
Click to collapse
What exactly does this do? I opened the apk and didn't see a whole lot.
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.
I have a yakju GNex with stock 4.1 (unrooted). It has the 4.2.0 update on it - it has tried and failed to install this update several times.
I would like to delete this pending 4.2 update, so I'm wondering where I would find the relevant files.
I figure that, once I've deleted them it might automatically download and install 4.2.2 (and hopefully that will install properly), and if that doesn't work then I will try to manually flash 4.2.2. Either way, I'd like to start by deleting the pending update.
Thanks.
Tomaxda said:
I have a yakju GNex with stock 4.1 (unrooted). It has the 4.2.0 update on it - it has tried and failed to install this update several times.
I would like to delete this pending 4.2 update, so I'm wondering where I would find the relevant files.
I figure that, once I've deleted them it might automatically download and install 4.2.2 (and hopefully that will install properly), and if that doesn't work then I will try to manually flash 4.2.2. Either way, I'd like to start by deleting the pending update.
Thanks.
Click to expand...
Click to collapse
4.2.2 requires 4.2.1, which requires 4.2
you modified system files and thats why the OTAs fail to flash. i swear i'm beating a dead horse by saying that.
Zepius said:
4.2.2 requires 4.2.1, which requires 4.2
you modified system files and thats why the OTAs fail to flash. i swear i'm beating a dead horse by saying that.
Click to expand...
Click to collapse
Thank you for clarifying about the OTA being dependent on each other. I take it that applies to the OTA, and not to the published Nexus images so I could still download 4.2.2 and flash it to the phone (bypassing 4.2).
I can see why you suspect that I have modified system files, but I have not. It has stock, unrooted, yakju 4.1 on it.
The only thing non-standard about it is that a Canadian GNex, with an unlocked bootloader, and flashed (via fastboot) to the standard Google firmware. But that is extremely common here, and the problem I'm having is not extremely common, so something must have got mucked up on the phone.
Regardless of how it happened, I would still like to delete the update files if it can be done w/o root.
Zepius said:
4.2.2 requires 4.2.1, which requires 4.2
you modified system files and thats why the OTAs fail to flash. i swear i'm beating a dead horse by saying that.
Click to expand...
Click to collapse
Now I think that is wrong...
I 'reset' the phone - using the option in settings that erases user data.
It appears that this cleared the pending update, as a day later I was prompted with a new OTA install, but now it was for 4.2.2. I confirmed that I was still on 4.1.1 and it was offering me an OTA update to 4.2.2.
Tomaxda said:
Now I think that is wrong...
I 'reset' the phone - using the option in settings that erases user data.
It appears that this cleared the pending update, as a day later I was prompted with a new OTA install, but now it was for 4.2.2. I confirmed that I was still on 4.1.1 and it was offering me an OTA update to 4.2.2.
Click to expand...
Click to collapse
good, did the 4.2.2 update install fine?
thegtfusion said:
good, did the 4.2.2 update install fine?
Click to expand...
Click to collapse
No, it did not. But I believe that the problem that prevented it from installing OK is the same problem which brought me here in the first place. I don't think it would have offered me the 4.2.2 if that update was not suitable for me.
In the end, I downloaded yakju 4.2.2 stock from the Android Nexus Images page, and then followed efrant's instructions in post#1 of this thread:
http://forum.xda-developers.com/showthread.php?t=1626895
I did each of the fastboot flashing steps, including the optional ones, to get the best chance of overwriting whatever was causing the problem. This worked and the phone is now running 4.2.2.
Tomaxda said:
No, it did not. But I believe that the problem that prevented it from installing OK is the same problem which brought me here in the first place. I don't think it would have offered me the 4.2.2 if that update was not suitable for me.
In the end, I downloaded yakju 4.2.2 stock from the Android Nexus Images page, and then followed efrant's instructions in post#1 of this thread:
http://forum.xda-developers.com/showthread.php?t=1626895
I did each of the fastboot flashing steps, including the optional ones, to get the best chance of overwriting whatever was causing the problem. This worked and the phone is now running 4.2.2.
Click to expand...
Click to collapse
Great man!
Enjoy your perfect Galaxy Nexus now
I know that if I uninstall or freeze anything that came in my rooted stock rom, subsequent ota updates may not install correctly. (is that true?)
Will installing Xposed Framework also cause problems when installing an ota system update?
Thanks.
Anderson2 said:
I know that if I uninstall or freeze anything that came in my rooted stock rom, subsequent ota updates may not install correctly. (is that true?)
Will installing Xposed Framework also cause problems when installing an ota system update?
Thanks.
Click to expand...
Click to collapse
if an ota fails and no factory images are available, just flash the previous image with the no wipe option (edit the flash-all.bat with notepad++ and remove the -w paramater iirc) and take the ota
Thanks for the work around.
But does installing Xposed Framework affect the core stock rom in a similar manner?
Anderson2 said:
Thanks for the work around.
But does installing Xposed Framework affect the core stock rom in a similar manner?
Click to expand...
Click to collapse
It depends on the update. If it checks /system/bin/app_process it will fail as that's the file Xposed replaces.
Thank you. I was not clear as to how Xposed worked.