Develop Bugs

[Q] Check what fails a OTA update?

I'm on a Galaxy Nexus takju, and I'm trying to install this update. http://forum.xda-developers.com/showthread.php?t=2144568
But as you can see in that thread, I get an error7.
I guess it might has something to do with my gps.conf that I've edited, and even if I edit it back, there are still some changes done to the date and stuff..
I wonder if there are any way to see why the update fails. Like a log file or something.
Also, what is the easiest way to restor that part then, without wipeing to phone?
EDIT: Also I got the right drivers installed for my win8 computer, but with both Galaxy Nexus toolkit and Nexus Root Toolkit, I can't install the update with adb sideload...
/Söder

you will never be able to update with any method because you modified a system file. you need to completely revert it back to stock (pull it from one of the images).
also, it will tell you in the error 7 message why it failed.

Zepius said:
you will never be able to update with any method because you modified a system file. you need to completely revert it back to stock (pull it from one of the images).
also, it will tell you in the error 7 message why it failed.
Click to expand...
Click to collapse
Do you mean gps.conf or my /system?
And, how do I pull the gps.conf from a image file and push it still intact?
When I get the error I can't see the complete message. But it say something about /system/lib.
If it is my /system, can I then in some way restore just that?
/Söder

AW: [Q] Check what fails a OTA update?
soder said:
Do you mean gps.conf or my /system?
And, how do I pull the gps.conf from a image file and push it still intact?
When I get the error I can't see the complete message. But it say something about /system/lib.
If it is my /system, can I then in some way restore just that?
/Söder
Click to expand...
Click to collapse
The last time it was enough for me to reflash only the system partition. Use fast boot for it and you are on the safe side. The stock Google images are linked in the general and q&a section. The reflash should convert the main and important part back to stock and the ota is possible.
Sent from my Nexus 7

if you are on stock 4.2.1, just flash the rooted 4.2.2 bigxie rom in the dev section and u are ok, no need wipe
u will need to flash also the new radio that u can find in that thread too

Today when I was at schooI I was not able to flash OTA update even with my OTA ROM or Bixgie's OTA ROM so what I did was this:
When I went to home I donwloaded takju 4.2.1 factory images!
I opened CMW and I wiped cache and dalvik cache and then via Fastboot I flashed JB 4.2.1 Takju system and boot and then I flashed old custom recovery 5.#.#... and I was able to update to JDQ39 without losing files from my Nexus..

manumanfred said:
Today when I was at schooI I was not able to flash OTA update even with my OTA ROM or Bixgie's OTA ROM so what I did was this:
When I went to home I donwloaded takju 4.2.1 factory images!
I opened CMW and I wiped cache and dalvik cache and then via Fastboot I flashed JB 4.2.1 Takju system and boot and then I flashed old custom recovery 5.#.#... and I was able to update to JDQ39 without losing files from my Nexus..
Click to expand...
Click to collapse
I extracted the system.img from takju-jop40d-factory-e4d13f14.tar and then did a fastboot flash system system.img
After that I could update. Will boot back and restore my custom system files then, and restore root.
Thanks.
/Söder

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

[Q] 4.2.2 OTA "Error"

My phone prompted me today that an update to 4.2.2 was available.
Its a takju Nexus running with an unlocked bootloader and rooted but otherwise stock rom.
I've tried to get it to do the update, however it reboots to a screen saying "applying system update" then after a few seconds flicks to a screen with an android with an exclamation mark, and the word Error below.
Is this because i'm rooted? or is there something else going on?
Thanks
Kevin

Extra root files shouldn't cancel out the OTA, however, overwriting system files, or modifying system files will. For example installing busybox on system/bin, modifying etc/host etc. Installing mods and replacing apps on /system may also be the culprit.
Just flash the system.img over your current system, also make sure you're running the corresponding recovery, radio, kernel, and bootloader that came with your takju factory image. Do that and and try the OTA again, should work. If the OTA doesn't show up this time, you can download it from the OTA links thread and sideload it via ADB.
Alternatively you can install a custom recovery directly from your phone, back up all of your apps with TB, and flash Bigxie's 'stock' 4.2.2 if you don't have access, or don't want to mess around with a computer. Of course you won't get direct OTA updates from Google that way, but since he usually update his build pretty quick that shouldn't pose much problem.

I'm unable to update to 4.2.2 as it says "couldn't download". Not sure what's going on here.
P.S : I don't mean to hijack this thread.

chelseaeuro said:
I'm unable to update to 4.2.2 as it says "couldn't download". Not sure what's going on here.
P.S : I don't mean to hijack this thread.
Click to expand...
Click to collapse
Try clearing Google Services Framework's data+cache maybe? Or try in a couple hours, the problem could be in the server.

reysonance said:
Try clearing Google Services Framework's data+cache maybe? Or try in a couple hours, the problem could be in the server.
Click to expand...
Click to collapse
I did that and my update is gone lol. Guess I'll have to wait for a few hours.

I had to force stop the frameworks and then try updating, which worked. Thanks!

reysonance said:
Extra root files shouldn't cancel out the OTA, however, overwriting system files, or modifying system files will. For example installing busybox on system/bin, modifying etc/host etc. Installing mods and replacing apps on /system may also be the culprit.
Just flash the system.img over your current system, also make sure you're running the corresponding recovery, radio, kernel, and bootloader that came with your takju factory image. Do that and and try the OTA again, should work. If the OTA doesn't show up this time, you can download it from the OTA links thread and sideload it via ADB.
Alternatively you can install a custom recovery directly from your phone, back up all of your apps with TB, and flash Bigxie's 'stock' 4.2.2 if you don't have access, or don't want to mess around with a computer. Of course you won't get direct OTA updates from Google that way, but since he usually update his build pretty quick that shouldn't pose much problem.
Click to expand...
Click to collapse
Thanks
Just to confirm, if i flash the system.img over my current system, will that delete all my installed apps/data? Which system.img should i be flashing? the one from 4.2.1?
Is there a list somewhere of the version numbers for the various parts (recovery, radio, kernel and bootloader) so i can check they are correct?
Also, is there a way i can flash the OTA update with some error logging or debug output turned on, so i can see what its actually failing at?
Cheers

Yes, the one from 4.2.1, check under Maps > Settings > About, it should gives you the version you're currently running, download it from the factory images page if you haven't already, and no, it should not wipe any apps+data, but back it up anyway if you're worried, better safe than sorry, I'm generally paranoid about data so I always backup, but no it shouldn't wipe anything. You'll lose root and that's it.
And for the bootloader and all that, it all should come all packaged on the factory image, so if you flash 4.2.1 via toolkit, or manually and haven't installed any radio or kernel you should be safe. IIRC, the bootloader version is PRIMELC03, the radio is XXLH1.

reysonance said:
Extra root files shouldn't cancel out the OTA, however, overwriting system files, or modifying system files will. For example installing busybox on system/bin, modifying etc/host etc. Installing mods and replacing apps on /system may also be the culprit.
Just flash the system.img over your current system, also make sure you're running the corresponding recovery, radio, kernel, and bootloader that came with your takju factory image. Do that and and try the OTA again, should work. If the OTA doesn't show up this time, you can download it from the OTA links thread and sideload it via ADB.
Alternatively you can install a custom recovery directly from your phone, back up all of your apps with TB, and flash Bigxie's 'stock' 4.2.2 if you don't have access, or don't want to mess around with a computer. Of course you won't get direct OTA updates from Google that way, but since he usually update his build pretty quick that shouldn't pose much problem.
Click to expand...
Click to collapse
Very thanks for this explanation. It help me a lot and I finally could update via OTA.

Stuck at 4.1.1, Can't update to 4.1.2 or 4.3, please help

Hello
I have Galaxy S3 (ATT), currently i'm stuck at 4.1.1. I can't update to 4.1.2 or 4.3.
I had my phone rooted by the Galaxy tookkit.
What I tried so far is.
1) recovered recovery back to stock (rooted stayed), update failed
2) used the toolkit to remove root, also removed busybox and superuser, toolkit put the clockwork recovery back in., update failed.
How can I update to 4.3?

nekrosoft13 said:
Hello
I have Galaxy S3 (ATT), currently i'm stuck at 4.1.1. I can't update to 4.1.2 or 4.3.
I had my phone rooted by the Galaxy tookkit.
What I tried so far is.
1) recovered recovery back to stock (rooted stayed), update failed
2) used the toolkit to remove root, also removed busybox and superuser, toolkit put the clockwork recovery back in., update failed.
How can I update to 4.3?
Click to expand...
Click to collapse
have you tried using kies to go to 4.1.2 and then manually update to 4.3?

rkant18 said:
have you tried using kies to go to 4.1.2 and then manually update to 4.3?
Click to expand...
Click to collapse
how? Kies is telling me 4.1.1 is the latest.

anyone else?
Tried again yesterday, no root, stock recovery, superuser, busybox all removed. And it downloaded 650mb updated it failed at 31%, this update was interrupted.

nekrosoft13 said:
anyone else?
Tried again yesterday, no root, stock recovery, superuser, busybox all removed. And it downloaded 650mb updated it failed at 31%, this update was interrupted.
Click to expand...
Click to collapse
I used this thread to get back to stock so my flash counter would be reset back to 0 - http://forum.xda-developers.com/showthread.php?t=2363882
Then I used KIES recovery to reflash 4.1.1 just to be sure it was exactly what Samsung intended.
Then when i checked for OTA update (while on 4.1.1) it found one and took a while to download. When it installed the update, it was already to 4.3 - i guess it skipped the 4.1.2 official update.
I then did a master reset from the settings menu and deleted everything so that 4.3 could start fresh. I haven't had any problems with the stock 4.3.

Goofy? Did u try the ota to get to 4.3
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Prometh1216 said:
Goofy? Did u try the ota to get to 4.3
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
yes, it fails at 31% phones reboots and once booted it tells me update was interrupted.

jack man said:
I used this thread to get back to stock so my flash counter would be reset back to 0 - http://forum.xda-developers.com/showthread.php?t=2363882
Then I used KIES recovery to reflash 4.1.1 just to be sure it was exactly what Samsung intended.
Then when i checked for OTA update (while on 4.1.1) it found one and took a while to download. When it installed the update, it was already to 4.3 - i guess it skipped the 4.1.2 official update.
I then did a master reset from the settings menu and deleted everything so that 4.3 could start fresh. I haven't had any problems with the stock 4.3.
Click to expand...
Click to collapse
Thanks will try that, you did a factory reset prior to flashing this?
At work now, so can't download the files, but will try it later.
What did you use to backup your files?

nekrosoft13 said:
Thanks will try that, you did a factory reset prior to flashing this?
At work now, so can't download the files, but will try it later.
What did you use to backup your files?
Click to expand...
Click to collapse
I didn't factory reset before flashing because i knew that when I use KIES to do a recovery it will erase everything on the phone. However, I did wipe cache and dalvic in recovery beforehand... well, come to think of it, i probably did also wipe data before flashing the 4.1.1 that resets the flash counter.
Regarding backing up my files, I have all the files I need on an external sd card so all i have to do is take out the card. Plus, I also use Google Drive to store my pictures as I take them with the camera. no real need to back-up things because things are saved somewhere else, and not directly to the phone. I will probably use the phone storage more now, though since I won't be flashing anything for a while. Taking a break from flashing.
Hope it works out for you.

jack man said:
I didn't factory reset before flashing because i knew that when I use KIES to do a recovery it will erase everything on the phone. However, I did wipe cache and dalvic in recovery beforehand... well, come to think of it, i probably did also wipe data before flashing the 4.1.1 that resets the flash counter.
Regarding backing up my files, I have all the files I need on an external sd card so all i have to do is take out the card. Plus, I also use Google Drive to store my pictures as I take them with the camera. no real need to back-up things because things are saved somewhere else, and not directly to the phone. I will probably use the phone storage more now, though since I won't be flashing anything for a while. Taking a break from flashing.
Hope it works out for you.
Click to expand...
Click to collapse
have you ever tried Helium? I was planning to use that for backup of my apps data.
last time I recovered/flashed phone was with Windows Mobile... so yeah really behind with all of this.
So if I first use helium for backup and then do factory reset, then flash the stock 4.1.1.
I know google account has all my contacts and calendar.
After I have the stock 4.1.1 back I should be able to update to 4.3 and from there restore the backup?

nekrosoft13 said:
have you ever tried Helium? I was planning to use that for backup of my apps data.
last time I recovered/flashed phone was with Windows Mobile... so yeah really behind with all of this.
So if I first use helium for backup and then do factory reset, then flash the stock 4.1.1.
I know google account has all my contacts and calendar.
After I have the stock 4.1.1 back I should be able to update to 4.3 and from there restore the backup?
Click to expand...
Click to collapse
Never used Helium. I have use Titanium Backup before. It's widely used for backing up app data. You can get it in the Play Store. Make sure you don't try to restore system data - it will cause all kinds of trouble. I don't usually restore app data anymore - well, now that I'm on stock I can't, anyway. I always had some kind of issue, whether it be small or big, when I restored data. who knows, maybe I wasn't doing it exactly right.
I'm not sure if restoring apps from 4.1.1 to a 4.3 base would be safe or not. remember, if you try, that means you'll have to root the 4.3 and that will trip your warranty bit count off of zero, so if you're concerned about warranty, you shouldn't root. (if you upgrade to 4.3 stock, you can go to download mode and see that they now have included two flash counts: one to count custom binaries (that can be reset) and the other one called warranty bit, that no one here knows how to reset yet.)

according to Helium, it doesn't require root. I will make a backup just in case, just want my angry birds progress...
still at work, so I can't download the file (yet), so how exactly does this work, since it says you don't need odin?

nekrosoft13 said:
according to Helium, it doesn't require root. I will make a backup just in case, just want my angry birds progress...
still at work, so I can't download the file (yet), so how exactly does this work, since it says you don't need odin?
Click to expand...
Click to collapse
After you download it, make sure it's on your internal sd card in the phone. Boot into ClockWorkMod recovery, wipe data/factory reset, clear cache, clear dalvic from the advanced menu, then flash the zip. that's it. near the end of the flash it will ask you if you want to keep root. i chose no since I knew I was going to be update to the official release. I've heard of people having problems trying to update OTA with root.
Just make sure that updating to 4.3 is what you want because it will limit what you can do with the device after you have the new bootloaders.

Trouble with auto update and twrp

So im on 4.4.2 right now with twrp and timur's kernel FI 2013 installed on the tablet. I keep getting an update message, and it will download 4.4.3 and restart, but it restarts into twrp, which is why, I'm guessing, the update doesn't install. What would be a good solution to updating the tablet to 4.4.3, or.4 if it is available? thanx.

[email protected] said:
So im on 4.4.2 right now with twrp and timur's kernel FI 2013 installed on the tablet. I keep getting an update message, and it will download 4.4.3 and restart, but it restarts into twrp, which is why, I'm guessing, the update doesn't install. What would be a good solution to updating the tablet to 4.4.3, or.4 if it is available? thanx.
Click to expand...
Click to collapse
Assuming you haven't modified any /system files the ota wants to update, the next time the update boots you into twrp, it will not automatically install, you must flash the ota manually, you will find the ota zip in /cache...you will have to flash the stock kernel before doing anything though...and if you get an error about a modified file in /system, you will have to revert the change or dirty flash the stock system.img...wipe dalvik though...after flashing the ota wipe dalvik and cache.

mdamaged said:
Assuming you haven't modified any /system files the ota wants to update, the next time the update boots you into twrp, it will not automatically install, you must flash the ota manually, you will find the ota zip in /cache...you will have to flash the stock kernel before doing anything though...and if you get an error about a modified file in /system, you will have to revert the change or dirty flash the stock system.img...wipe dalvik though...after flashing the ota wipe dalvik and cache.
Click to expand...
Click to collapse
If I flash the stock kernel wouldnt that get rid of timurs that I have now. That kernel is the only reason I have this thing. Just correct me if im wrong but your saying flash back to stock, install updatesthen reflash timurs? Why cant I just try and find a clean 4.4.4 zip which I have looked for but never found, and flash it through twrp instead of relying on the nexus' s self update. I looked in the destination u gave me and it wasnt there. Could this be because /cache is a temporary storage location and I have to do this immediately after the download

[email protected] said:
If I flash the stock kernel wouldnt that get rid of timurs that I have now. That kernel is the only reason I have this thing. Just correct me if im wrong but your saying flash back to stock, install updatesthen reflash timurs? Why cant I just try and find a clean 4.4.4 zip which I have looked for but never found, and flash it through twrp instead of relying on the nexus' s self update. I looked in the destination u gave me and it wasnt there. Could this be because /cache is a temporary storage location and I have to do this immediately after the download
Click to expand...
Click to collapse
There are multiple ways to update, you asked about OTA, in order for OTA to work, the OTA expects the device to have certain files at a certain version, one of the things it checks, besides files in /system, when there is a change to it, is the kernel, so a OTA will fail if it checks the kernel and finds timur's in its place, which is why I suggested you just flash the stock boot and system (yes, you can always go back to timur's afterward assuming it is compatible with the new ROM, you will also have to reroot/redo changes to /system).
The OTA is downloaded into /cache, and if the cache is wiped the OTA file will not be there, so once it is downloaded, use a root filemanager, and copy it to your sdcard, then it won't get wiped.
The other way to update is to just flash the changed images individually from the factory images using fastboot, making sure not to flash the images which would wipe any boot, userdata, or custom recoveries...as long as you do not flash boot.img, you will keep timur's kernel, but you will have to reroot/redo changes to /system.
You can also use the factory image flash-all.bat to do this, BUT you must delete the -w option in the bat file, not doing so will result in your device being wiped, you will still have to reflash timur's kernel using this method as well as reroot/redo changes to /system.
Either way, when you update, wipe dalvik and cache before rebooting.

Just from the way you described that to me i can tell that its going to take some time for me to relearn how to do all of this. Are there really any huge benefits to updating from 4.4.2 to .4 that would really make this worth it? Also if I did decide to put all of this effort into it, is there a way that i can save things like my preferences and my homescreen setup and widgets when i do attempt it? thanks

[email protected] said:
Just from the way you described that to me i can tell that its going to take some time for me to relearn how to do all of this. Are there really any huge benefits to updating from 4.4.2 to .4 that would really make this worth it? Also if I did decide to put all of this effort into it, is there a way that i can save things like my preferences and my homescreen setup and widgets when i do attempt it? thanks
Click to expand...
Click to collapse
Yeah, you can use TiB to backup apps and appdata. I would also advise you do a full nandroid (no need to backup cache though). Save them all to your PC.
As for whether it's worth it, you'll have to read the changelogs for yourself and find out if it is to you or not. Really it's not much work at all to update.
You can always wait around for Android L.

[Q] Can't install Android update on Sprint GS3

Prologue: Sprint GS3. For most of last year I rooted my phone and put Cyanogen mod on it. However I'm planning to go to Ting so I downloaded and flashed back to a stock Sprint GS3 ROM late last year.
Got prompted to install the latest Android system update on my Sprint GS3. It say OK and it reboots into recovery. After about a minute of the install animationion it fails. I tried to link to a screenshot but XDA won't let me post outside links yet.
I can choose to reboot and it reboots like normal without updating.
The error message, in case it's hard to read, says:
Code:
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/priv-app/GoogleServicesFramework.apk" has unexpected contents.
E:Error in /cache/update.zip
(Status 7)
Installation Aborted
Hoping there's a way around it, or am I just stuck without being able to update for the rest of the life of the phone?
PS - Yes I probably shouldn't have messed with it in the first place, I know.

Just flash the latest stock ROM, NJ2

mattzeller said:
Just flash the latest stock ROM, NJ2
Click to expand...
Click to collapse
Won't I then have to re-configure my phone again and re-add all the accounts and apps, etc?
Probably an FAQ, but then where do I find the NJ2?

dtseiler said:
Won't I then have to re-configure my phone again and re-add all the accounts and apps, etc?
Probably an FAQ, but then where do I find the NJ2?
Click to expand...
Click to collapse
Here is the Odin flashable NJ2 thread:
http://forum.xda-developers.com/showthread.php?t=3007847
Just use Titanium Backup to back everything up including texts, flash this then restore everything with Titanium Backup