[Q] Updates fail from 4.1.1 to 4.1.2 - Nexus S Q&A, Help & Troubleshooting

Hi,
A while back I rooted and unlocked using clockwork recovery and installed bigxie_magurTA_JRO03C-signed.zip
All was good for a while until the last month where I continually receive notification to update to 4.1.2
when I choose install, it attempts to reboot and on the recovery mode, I attempt to run the /sdcard/update.zip and it fails due to signature verification failure.
When I disable the signature verification, it states it cannot open the update file as if it is corrupt or not there,
I then tried to put on cyanogen mod, and when that loaded, I could not enter in my gmail profile info.
I then installed gapps on the next attempt to install cyanogen mod 10 and although more apps (google play app) was listed, still could not enter my gmail info anywhere
i have gone back to the 4.1.1 install I mentioned earlier, and it is running fine, but I am still prompted to update, which fails every single time.
Any suggestions on how to update this, I would be happy to go with cyanogen mod, but no idea really where to start.
I searched for the same error messages I was getting, and found a few posts but not solutions or recommendations,
Also, is this going to happen for every single update from this point on since rooting and unlocking the phone? i would prefer to give up more app control if going back to stock builds means not having to give up this much time for every update.
Thanks to anyone that can help.

Related

OTA Update failed

Hi,
I've got a magic from TIM but i'm leaving in belgium. I'm running MyHero 2.0.5
By two times, my handset requested me to reboot my phone for a 'system update'. Both attempt failed.
The phone reboots then an icon representing a package update then a a failure sign. The only way to get back the phone was to remove the battery.
My question:
Where can i find the package that android tries to install....is there a log somewhere where the failure is reported ?
Thanks
Ced
If you're running a custom rom and trying to install an OTA it isn't going to work. The OTA is only compatible with the stock OS. If you have root and manage to get an OTA to install then you will lose it. I'd say to just ignore the updates. If your phone is working the way you want it then I would leave it as is. If you want anything different then you'll need to flash something!

Tab 2 10.1 GT-P5113 WIFI OTA Rooted.....

So it look like the JB OTA update is here for the USA. Mine is rooted, and has already download the update, but I haven't applied it yet, as I'm rooted and I don't know if I have to do something special first.....
Any one have any info on this?
Same Boat !!
Me too in same boat with P3113.See the post below yours :crying: Hope experts replies soon.
I went ahead and installed it on my daughters tab. CWM protected itself, and root. I'm still poking around, but thus far no issues beyond it says "update failed" but clearly didn't.
I'm wondering if I should remove CWM and unroot it first...
Run a nandroid real quick, back it up to your computer, and let 'er rip. Like I said, it's working perfectly for me. Then again my daughter is 7, so losing all her data isn't really a problem.
Updated with Root ?
sheepdog elite said:
Run a nandroid real quick, back it up to your computer, and let 'er rip. Like I said, it's working perfectly for me. Then again my daughter is 7, so losing all her data isn't really a problem.
Click to expand...
Click to collapse
So if i understand correctly , you allowed the OTA with root and it wiped data ? I am suprised it installed with Custom recovery !!!
I have over 200 user apps. Will i retain those Apps (dont mind data being wiped)
No, it didn't wipe data. I wasn't worried about it "if" it did, because it's my daughters, and I have TIBU for all her games from like last week.
Just to be perfectly clear. NOTHING went wrong. It installed the new O.S., booted fine, said the update failed, but the update didn't fail. Probably because CWM preserved root, and bootloader, so verification failed.
I ran it..... It updated thru CWM... Once done said update failed, but I had a new agreement to agree too. Sys info says its running 4.1.1.
If I have and issue, ill update here.
Failed for P3113
Based on your experience thought I would try too... Unfortunately failed miserably... I have Cwm 6.0.2.3 and attached is the crash log... Maybe some experts can give their views..
I guess I'll post my successful config just for the sake of comparison.
I'm currently running CWM 6.0.1.1. The tab was rooted with a file called gtab2_jellybean_rooter (think I got it from XDA, but i'm not positive) and had no other modifications/roms/etc.
If you're running any sort of ROM you're definitely boned, gotta wait for a ROM update. Beyond that, I'm not really sure what to say
To do the proper update, you should un-root and then re-root once done. That way you get the full support with your update if needed.
I am rooted, running CWM 6.0.2.3. I accepted the update and hit the install thinking that it would fail just as it does on a rooted SIII. The notification said the install had failed, but as others here have indicated, it appears as though the install was successful. I retained root and all seems to be normal; with one exception: It appears that the Tab no longer "sleeps" but shuts down completely. Regardless of whether I turn it off with the power button (short press) or if the screen simply goes to sleep, I have to long press the power button and it goes through a full boot.
Is anyone else experiencing this? Is there a setting I am missing? I am not a noob at rooting, etc. as I have been doing it since my OG Droid on Verizon, but it surprised me when the update seemed to install (even Google Now is working), and I am stumped about this "shut down" that seems to happen.
I experienced the same thing. I was rooted and had installed CM10, went back to original backup, using latest CWM. I hit system update and it downloaded the update, asked me to continue. CWM asked me if I wanted to install unsigned zip, I accepted, and it went through. At first boot it said update failed, but like everyone else, it went through. I have had no issues at all. My tab goes to sleep correctly.
Have peace in mind.
I finished updating (unfortunately, the battery was 9%, so I had to wait for an hour to charge before doing anything) and I got "failed" error like everybody got, but the system shows 4.1.1 and the performance is improved, and I applied root again.

[Q] [HELP]I accidentally applied an OTA to stock rooted ICS

Hello my name is Unicorn, I did a forum search to see if my particular scenario has been addressed before but did not find anything (perhaps because of my choice of search keywords, I'm not sure.) I made some mistakes and was hoping a more informed member can assist me in remedying my errors. Here is the situation as of currently:
1. I purchased a Verizon SGS3 (SCH-i535) back in December 2012, and was able to root it successfully using the method in this thread: http://forum.xda-developers.com/showthread.php?t=1875914
2. I flashed Synergy ROM (Synergy_d2vzw_02Dec12_2021_r125_s.zip) so my custom binary count is thus far 1.
3. I began having some trouble with Synergy ROM around the time that Verizon deployed their Stock Jellybean OTA update (the "Limit Mobile Data Usage" and "Use Mobile Data" toggle check boxes disappeared from the settings menu which is unusual because I did NOT opt to accept the OTA update.)
4. Rather than trying to manually diagnose why the check box toggles were then missing, I decided merely to Restore my CWMR Recovery Image in order to bring myself back to the modded stock rom (effectively putting me back in the position that I was in after step 1 but before step 2 mentioned above.)
5. Returning to the modded stock rom brought back the toggles as desired, however since the rom was ICS 4.0.4 I was still persistently receiving the nag message asking me download and install the OTA Jellybean update (which I deferred.)
6. This morning the deferment date lapsed, which prompted my phone to restart and boot back in to CWMR 6.0.1.0 where I was asked to confirm whether CWMR should flash the update package.
7. I mistakenly chose to apply the update because I was disoriented due to having just recently awoken, and because I had already hit the home button I allowed the update to proceed (I didn't want to pull the battery part-way through the flash for fear that it would somehow brick my phone.)
8. There were 2 other prompts that appeared during this process, the first one telling me that the update might install stock recovery and the second one informing me that root might be lost (even though I chose the menu options that should have prevented these occurrences from happening it would appear that they in fact still took place because when I attempted to boot back in to CWMR from the EZ-Recovery 2.0 menu I was confronted with the screen telling me that I had unauthorized software and should see a Verizon representative to fix it.
9. After powering down I was able to boot back in to Android after which I found that the "About Phone" section reported an incremental update to Android 4.1.1 so it would appear that the OTA installed partially (even though I'm still getting the notification telling me I need to download the update.)
Basically I just want to return my device to unrooted stock so that I can start fresh then re-root later, but I'm not sure what the best method to use is because I'm not certain if the device is still rooted at this point.

[Q] [SOLVED] 220.27.1 OTA install problems

Hi everyone,
I received the OTA update notification a long time ago but didn't have time to take a deep look into it (baby on the way... now arrived !), but I'm trying to install a lollipop ota update on my moto g.
It's not my first android device, I had about 10 of them and messed around with them, so don't be affraid to use the vernacular directly, but I'm aware that I might be making a rookie mistake too
My phone is a 1st gen 16Gb Moto G. IT's running 4.4.4 (System version 210.12.40.falcon_umts.Retail.en.FR, I'm in France by the way). I did a few things to it :
- unlock bootloader
- install CWM
- root
- install xposed
- install cerberus and moved it to system apps
Before trying to install it I tried to reverse the steps back to stock :
- move cerberus back to user apps, and uninstall it just in case
- remove xposed
- unroot using the option in the SuperSU menu
- go back to kitkat stock revovery, using mototool v2.6 (so this might a 4.4.2 but I didn't find another one so far)
Then I clicked on the OTA notification, anouncing that 220.27.1... was ready to be installed, downloaded it ok, chose to install it.
Everytime I tried the phone rebooted, began the install and after a short while showed a error message and rebooted.
I tried to install it by putting the OTA zip file in /sdcard and install it with the stock recovery, but here's what I found out :
After downloading the OTA on the phone if I go to /cache/ (where the ota zip file is downloaded. To do that I need root access so I got to flash cwm and root it again, fyi) it shows another file, not corresponding to 220.27 but named : Blur_Version.210.12.40.falcon_umts.Retail.en.FR.zip .... which is weird because it's the version that's supposed to be installed already !
I tried something else, found the "Blur_Version.220.27.1.falcon_umts.Retail.en.FR.zip" file on a forum, put it on /sdcard/ and try to install it through recovery... same error.
Does anyone have an idea on how to install it succesfully without having to flash back a stock firmware ?
Thanks a lot to anyone giving a shot, you rock !
Mat
Ps : i tried to find anything similar on the forum but didn't manage to. If i searched with the wrong terms or didn't notice it while browsing trough the different topics, please tell me if you have a clue, and sorry about not having searched well enough.
Found solace here :http://forum.xda-developers.com/mot...osing-apps-t2979971/post57658072#post57658072
Worked perfectly
Sorry for not having searched enough !

[Q] Tmo Samsung S4 (SGH-M919) with Google Play Edition, need help

(this belongs elsewhere but 10 posts...)
I have a rooted S4 and just installed Dandvh's Google Play Edition v.20150919 (http://forum.xda-developers.com/showthread.php?t=2539361) rom. I used TWRP to install, wiping everything but internal storage, then flashed the rom. Installed fine, no errors. Took the usual bit of extra time to boot the first time then up and running clean and stable. The issue is that the OTA Updater app doesn't work, severely limiting my ROM options. It didn't install as part of the rom install, though I'm not sure if it's normal to just get it off the play store. I get an error message about not being compatible with the ROM and can't access it (error message screen cap below). Just in case, I wiped the phone and flashed again just to be sure, same result. The OTA Updater is important as this is where you can change kernals, audioFX stuff, toggle advanced power menus, and quite a bit more. When I used this ROM during the first part of the year OTA Updater worked just fine but I switched off in July to try another ROM so maybe something with the ROM has changed? I tried searching for any comments in the thread to indicate either that something changed with OTA Updater or if anyone else had a similar problem, found nothing. Would appreciate if anyone might know why OTA Updater isn't working or how I might correct it. Thanks.
Edit #1: I haven't changed the model number to SGH-M919 (as seen in the screen cap) in build.prop yet as if I can't get this ROM to work right I'll need to flash something else.
Edit #2: I noted in the patch notes that the ROM was updated for OTA Updater 2.4.2 and I was running 2.5.3 so I uninstalled it and installed 2.4.2. No luck there either.
Version and Build Screenshot
https://imgur.com/SQ6ie5i
Error message
https://imgur.com/TfWN7p2

Categories

Resources