I am unrooted and on stock 4.4.
I have tried installing the 4.4.2 OTA 3 times, failing every time on 20-30%.
Then I tried to go to recovery mode and wiping cache partition, and after that I immediately got another OTA 4.4.2, but that also failed.
I have no idea why this is happening, and what my options are.
Do anyone know about this problem, if it is with my phone or a general problem, and how to fix it, or get 4.4.2 some other way.
did you install any mods, kernels, change any files? if so its been documented all over the forums.
No, the only thing I've done that might be causing a problem (I've just now learned), is that I had Google Keep deactivated, which apparently is a no-no since it's a system app.
I've re-activated it now and waiting until I get another OTA, then trying again.
danielvago said:
No, the only thing I've done that might be causing a problem (I've just now learned), is that I had Google Keep deactivated, which apparently is a no-no since it's a system app.
I've re-activated it now and waiting until I get another OTA, then trying again.
Click to expand...
Click to collapse
It didn't work. I have no idea what to do, can I sideload the APK?
Something similar happened to me to my wife's Nexus 5. Not even manually down loading the OTA file and flashing it using CWM worked properly (it flashed all right, but the phone became unstable after). So in the end, I downloaded the factory image for 4.4.2 and did a flash-all. Detailed instructions for doing that are available here: http://forum.xda-developers.com/showthread.php?t=2513701. It seems to run fine now. If you would like to preserve your data, unzip all of the factory image file and flash one component at a time, skipping userdata.img (as doing so wipes your data).
danielvago said:
It didn't work. I have no idea what to do, can I sideload the APK?
Click to expand...
Click to collapse
I've never had a problem flashing an update because system apps were disabled. Deleted yes, disabled no. If you were at one time rooted and deleted Keep from system/app sideloading it will not install it in the system, it will be installed as a user app. Also, if you put Keep back in system/app it needs to be both the apk and the odex files or it will fail again anyway. If you delete anything from the system you need to save those files somewhere because that will affect being able to do updates. Instead of deleting a file I would just rename it by adding the number 1 at the end of the name (Keep.apk1). At this point you would need to be rooted to replace anything in the system. Or you could use adb to flash the system image. Anyway... all this is conjecture on my part because it's not very clear if you have EVER been rooted or not and what exactly you mean by "deactivated," then asking if sideloading would work. If you "Disabled" Keep you don't need to sideload it because it's still there inside system/app. The update does not care if you have system app updates installed or not as long as the original is in system/app.
---------- Post added at 04:33 AM ---------- Previous post was at 04:24 AM ----------
Theory said:
Something similar happened to me to my wife's Nexus 5. Not even manually down loading the OTA file and flashing it using CWM worked properly (it flashed all right, but the phone became unstable after). So in the end, I downloaded the factory image for 4.4.2 and did a flash-all. Detailed instructions for doing that are available here: http://forum.xda-developers.com/showthread.php?t=2513701. It seems to run fine now. If you would like to preserve your data, unzip all of the factory image file and flash one component at a time, skipping userdata.img (as doing so wipes your data).
Click to expand...
Click to collapse
I believe you can open the flash-all script and delete the -w part and it will not flash the userdata image. I have a new original version of the 2012 N7 I'm going to try that with here in a minute to update to 4.4.2 but like you mention doing each image separately works great.
wantabe said:
I've never had a problem flashing an update because system apps were disabled. Deleted yes, disabled no. If you were at one time rooted and deleted Keep from system/app sideloading it will not install it in the system, it will be installed as a user app. Also, if you put Keep back in system/app it needs to be both the apk and the odex files or it will fail again anyway. If you delete anything from the system you need to save those files somewhere because that will affect being able to do updates. Instead of deleting a file I would just rename it by adding the number 1 at the end of the name (Keep.apk1). At this point you would need to be rooted to replace anything in the system. Or you could use adb to flash the system image. Anyway... all this is conjecture on my part because it's not very clear if you have EVER been rooted or not and what exactly you mean by "deactivated," then asking if sideloading would work. If you "Disabled" Keep you don't need to sideload it because it's still there inside system/app. The update does not care if you have system app updates installed or not as long as the original is in system/app.
---------- Post added at 04:33 AM ---------- Previous post was at 04:24 AM ----------
I believe you can open the flash-all script and delete the -w part and it will not flash the userdata image. I have a new original version of the 2012 N7 I'm going to try that with here in a minute to update to 4.4.2 but like you mention doing each image separately works great.
Click to expand...
Click to collapse
Sorry for not being clear, I have never rooted, un-locked, flashed anything, etc. I am using the phone very stock-y, not messing with anything.
It boggles me, that I can have such a problem, when I am going completely stock.
The most "extreme" things I've done is install an adblock apk and flashplayer 11.1 apk, that Dolphin browser suggested.
I don't know if the only solution is to do a factory reset, which I hate doing, since it took so very long to set everything up the way I wanted it.
I've read of other people having this problem, and no solution, and some have tried a factory reset but that didn't fix it.
danielvago said:
Sorry for not being clear, I have never rooted, un-locked, flashed anything, etc. I am using the phone very stock-y, not messing with anything.
It boggles me, that I can have such a problem, when I am going completely stock.
The most "extreme" things I've done is install an adblock apk and flashplayer 11.1 apk, that Dolphin browser suggested.
I don't know if the only solution is to do a factory reset, which I hate doing, since it took so very long to set everything up the way I wanted it.
I've read of other people having this problem, and no solution, and some have tried a factory reset but that didn't fix it.
Click to expand...
Click to collapse
What is the error when the OTA fails?
Adblockers usually require root, which in turn edits the hosts file, so that could be the culprit. I'd go the factory image way and edit the flash-all.bat using Notepad++ before running it to remove the -w flag so you don't lose your data
try incremental install
danielvago said:
I am unrooted and on stock 4.4.
I have tried installing the 4.4.2 OTA 3 times, failing every time on 20-30%.
Then I tried to go to recovery mode and wiping cache partition, and after that I immediately got another OTA 4.4.2, but that also failed.
I have no idea why this is happening, and what my options are.
Do anyone know about this problem, if it is with my phone or a general problem, and how to fix it, or get 4.4.2 some other way.
Click to expand...
Click to collapse
try sideloading 4.4.1 first. .and then sideload 4.4.2 after that. see if that works.
EddyOS said:
Adblockers usually require root, which in turn edits the hosts file, so that could be the culprit. I'd go the factory image way and edit the flash-all.bat using Notepad++ before running it to remove the -w flag so you don't lose your data
Click to expand...
Click to collapse
I just updated a new 2012 N7 from 4.1 to 4.4.2 and I couldn't get removing the -w flag to work. I think the script needs more editing than just removing the -w part. Something new I had never tried before which I actually don't personally have much use for because it still flashes the stock recovery over a custom recovery if you are using one. Anyway.. flashing the bootloader and radio separately and then flashing the update zip with "fastboot update image-hammerhead-kot49h.zip" would be a little bit of a shortcut versus flashing ALL of the images and you don't lose data.
Never had an issue myself, but I always prefer to flash each image manually one at a time
EddyOS said:
Never had an issue myself, but I always prefer to flash each image manually one at a time
Click to expand...
Click to collapse
I've always flashed each image separately also, I was just being lazy and experimenting. Removing the -w from the .bat and/or the .sh wouldn't work for me.
---------- Post added at 10:33 AM ---------- Previous post was at 10:27 AM ----------
danielvago said:
Sorry for not being clear, I have never rooted, un-locked, flashed anything, etc. I am using the phone very stock-y, not messing with anything.
It boggles me, that I can have such a problem, when I am going completely stock.
The most "extreme" things I've done is install an adblock apk and flashplayer 11.1 apk, that Dolphin browser suggested.
I don't know if the only solution is to do a factory reset, which I hate doing, since it took so very long to set everything up the way I wanted it.
I've read of other people having this problem, and no solution, and some have tried a factory reset but that didn't fix it.
Click to expand...
Click to collapse
If you don't want to try a factory reset (can't blame you) you're probably going to need to use adb. If you don't have it setup this is a good video showing how to setup adb.
wantabe said:
If you don't want to try a factory reset (can't blame you) you're probably going to need to use adb. If you don't have it setup this is a good video showing how to setup adb.
Click to expand...
Click to collapse
Thanks a lot.
I followed his steps and got it to show me the phones serial number when I wrote "adb devices" in cmd, in SDK -> platform-tools but... now what?
The guide just stops, and I don't know what to do.
I've done everything in this other guide ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ), but when I get to "adb sideload kk.zip" it just says "adb is not recognized as an internal or external command, operable command or batch file" and I'm stuck again.
What to do?
danielvago said:
Thanks a lot.
I followed his steps and got it to show me the phones serial number when I wrote "adb devices" in cmd, in SDK -> platform-tools but... now what?
The guide just stops, and I don't know what to do.
I've done everything in this other guide ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ), but when I get to "adb sideload kk.zip" it just says "adb is not recognized as an internal or external command, operable command or batch file" and I'm stuck again.
What to do?
Click to expand...
Click to collapse
Your path to adb isn't correct. Put the zip file in the same folder as adb
jd1639 said:
Your path to adb isn't correct. Put the zip file in the same folder as adb
Click to expand...
Click to collapse
Thanks, that was it, got it to begin.
Unfortunately it didn't work, it gave me an error about 30-35% through (like the normal OTA).
It says:
"/system/framework/framework-res.apk" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
From this link ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ) I chose:
"Nexus 5
Android 4.4 to 4.4.2 OTA update"
as I am on 4.4.
danielvago said:
Thanks, that was it, got it to begin.
Unfortunately it didn't work, it gave me an error about 30-35% through (like the normal OTA).
It says:
"/system/framework/framework-res.apk" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
From this link ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ) I chose:
"Nexus 5
Android 4.4 to 4.4.2 OTA update"
as I am on 4.4.
Click to expand...
Click to collapse
You're going to have to flash the system and boot image in fastboot in order for the update to work. You modified something
jd1639 said:
You're going to have to flash the system and boot image in fastboot in order for the update to work. You modified something
Click to expand...
Click to collapse
I am unrooted and locked, I have no idea how I modified something, or what, or how, I have kept it really stock.
What does it mean to flash the system and boot image? Can I do it without rooting, unlocking and/or factory resetting?
danielvago said:
I am unrooted and locked, I have no idea how I modified something, or what, or how, I have kept it really stock.
What does it mean to flash the system and boot image? Can I do it without rooting, unlocking and/or factory resetting?
Click to expand...
Click to collapse
Ok, so you're doing an adb sideload while in recovery?
jd1639 said:
Ok, so you're doing an adb sideload while in recovery?
Click to expand...
Click to collapse
Yes.
Related
Good morning,
I have the ICS 404 stock, rooted with CW 6.0.0.7. I downlaoded via ota the JB but the system was not able to install the new JB. How can solve this problem?? Do I have to install manually? Where is the file downloaded?? Someone can help me on the procedure to follow??
thanks
coluichepensa said:
Good morning,
I have the ICS 404 stock, rooted with CW 6.0.0.7. I downlaoded via ota the JB but the system was not able to install the new JB. How can solve this problem?? Do I have to install manually? Where is the file downloaded?? Someone can help me on the procedure to follow??
thanks
Click to expand...
Click to collapse
I have the same exact problem, however it also occurs when I try to install the zip directly from CWM...perusing the other threads it seems as though it's an issue with BusyBox overwriting some files in /system/bin. For the life of me I cannot find how to correct this issue even though the it is repeatedly mentioned in the threads that is has been covered already. Seeing as I'm nearing my wits' end, I'd appreciate someone pointing me in the right direction. Thanks in advance.:crying:
---------- Post added at 10:02 PM ---------- Previous post was at 09:42 PM ----------
Just to clarify this is what I get when I try to install 4.1.1:
Verifying current system...
assert failed: apply_patch_check
('/system/bin/gzip", "afdda757b27b444f525a0f41726d2c1a83012869", "5ba3b3ecd509cf6dcee37b2f27110310a1f55045")
E:Error in /cache/9ZGgDXDi.zip
(Status 7)
Installation aborted.
Even flashing 4.0.4 vias CWM doesn't overwrite the problematic /system/bin files. I got as far as trying to flash a factory image of 4.0.4 but got too frustrated with the fastboot commands in Terminal on OSX.
Again, while not a total neophyte, I could really use some hand holding regarding this mess. Thanks in advance.
Bumping in hope that some kind soul can walk me through replacing the /system/bin files that were overwritten by busybox. Tried factory reset and reflashing the 4.0.4 OTA to no avail. I think that flashing a factory image of 4.0.4 would work but I can't figure that out. I'm on OS X for what it's worth.
I appreciate your time.
Flashing through fastboot is rather simple. Can't remember the exact Mac commands of top of my head. But they are basically the same just fastboot-mac or whatnot.
Anyways if that is really a issue/ don't wanna bother with it. Look for the full stock ROM for your device and flash that with cwm. Make sure you wipe the old rom off first.
albundy2010 said:
Flashing through fastboot is rather simple. Can't remember the exact Mac commands of top of my head. But they are basically the same just fastboot-mac or whatnot.
Anyways if that is really a issue/ don't wanna bother with it. Look for the full stock ROM for your device and flash that with cwm. Make sure you wipe the old rom off first.
Click to expand...
Click to collapse
Thanks for the prompt reply. I dl'ed the factory image for my device (I9020T) from the developers/google site but couldn't get the ./flash-all.sh script to run. I then took the image.zip file from the factory tgz file and tried to flash it via CWM but got installation aborted/ Error 7 as well. Seems to be the only way to overwrite the system/bin filed that BusyBox replaced is to flash a factory image via fastboot.
Is there a way in which I can replace the problematic system/bin files that are preventing me from installing JB without flashing a stock factory image? And if there isn't, could I get some help with the Terminal commands for getting the /.flash-all.sh script to run on Mac?
Thanks again for your help and patience.
Those images are not mean to flashed through any recovery.
You can ignore that script. Extract what you have downloaded until you are left with ALL .img files. You should have system.img boot loader, radio, and userdata.img
Flash them one at a time with fastboot. Can't remember the exact Mac command but its fastboot flash system system.img etc for windows. Just look it for Mac. Think its fastboot-mac then the command but not sure. I hate Macs.
This has Mac fastboot info in it. I hate Macs also
http://forum.xda-developers.com/showthread.php?t=1789216
Edit: this has some info to help you also, I just change to Mac fastboot
http://forum.xda-developers.com/showthread.php?t=1785672
Sent from my Nexus S using xda premium
jayjay3333 said:
This has Mac fastboot info in it. I hate Macs also
http://forum.xda-developers.com/showthread.php?t=1789216
Edit: this has some info to help you also, I just change to Mac fastboot
http://forum.xda-developers.com/showthread.php?t=1785672
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Those two links were extremely helpful, thanks for that. I got as far as having all the requisite factory image files ready to be flashed in the same folder, but when I issue the command to flash the bootloader.img I get
Code:
-bash: ./fastboot-mac: Permission denied
.
Think I may have gotten a little over my head with this whole rooting business
For the record I am rooted and have an unlocked bootloader.
coluichepensa said:
Good morning,
I have the ICS 404 stock, rooted with CW 6.0.0.7. I downlaoded via ota the JB but the system was not able to install the new JB. How can solve this problem?? Do I have to install manually? Where is the file downloaded?? Someone can help me on the procedure to follow??
thanks
Click to expand...
Click to collapse
try latest touch version here http://bit.ly/QHLhXs when the update go to install in cmw there one dailoge box come choose yes and choose reboot and its appear again dailoge box choose yes disable recovery flash.
I solved the problem flashing this stock rom. http://forum.xda-developers.com/showthread.php?t=1784497
Finally sussed it out as well! Thanks to all for the help. Flashing the stock ICS image allowed me to install the JB OTA - will never install the BusyBox from the market again.
Cheers again to all.
I am trying to install the 5.1 OTA. I am stock & non-rooted. I recently booted into TWRP but I didn't flash it. When the OTA starts to install I get the Android with the exclamation mark. The only word is Error. I press the power button and volume-up and the error is...
"/system/bin/install-recovery.sh" has unexpected contents.
E:Error in /cache/update.zip
(Status 7)
Apparently even doing a fastboot boot into TWRP mucked up something. Anyway to correct that file to take the OTA again? I really don't wanto to do a factory reset.
xda6969 said:
I am trying to install the 5.1 OTA. I am stock & non-rooted. I recently booted into TWRP but I didn't flash it. When the OTA starts to install I get the Android with the exclamation mark. The only word is Error. I press the power button and volume-up and the error is...
"/system/bin/install-recovery.sh" has unexpected contents.
E:Error in /cache/update.zip
(Status 7)
Apparently even doing a fastboot boot into TWRP mucked up something. Anyway to correct that file to take the OTA again? I really don't wanto to do a factory reset.
Click to expand...
Click to collapse
You don't need to do a factory reset. Just remove -w from flash-all.bat and flash factory image without loosing data.
P:S: Also there are a lot OTA update threads yet.
zagorteney said:
You don't need to do a factory reset. Just remove -w from flash-all.bat and flash factory image without loosing data.
P:S: Also there are a lot OTA update threads yet.
Click to expand...
Click to collapse
Will this method correct the install-recovery.sh file so future OTA updates will apply?
xda6969 said:
I am trying to install the 5.1 OTA. I am stock & non-rooted. I recently booted into TWRP but I didn't flash it. When the OTA starts to install I get the Android with the exclamation mark. The only word is Error. I press the power button and volume-up and the error is...
"/system/bin/install-recovery.sh" has unexpected contents.
E:Error in /cache/update.zip
(Status 7)
Apparently even doing a fastboot boot into TWRP mucked up something. Anyway to correct that file to take the OTA again? I really don't wanto to do a factory reset.
Click to expand...
Click to collapse
zagorteney said:
You don't need to do a factory reset. Just remove -w from flash-all.bat and flash factory image without loosing data.
Click to expand...
Click to collapse
Flash-all can be used to automate the process of flashing a factory image, but OP is having issues with OTA.
xda6969 said:
Will this method correct the install-recovery.sh file so future OTA updates will apply?
Click to expand...
Click to collapse
Read this thread's first post to know how you can upgrade to 5.1.
I think you can flash the ota update file (once it downloaded, it should be somewhere in your device - EDIT: zagorteney posted the exact location below, /cache) with TWRP, like you would a normal custom rom, and TWRP will output more information about why the OTA isn't applying.
@beekay201
You are wright. I've thought that OP just want to update to 5.1 anyway. Update.zip is located in /cache.
I had the same issue, then when I made the decision to use the flash-all script, I got another error about missing the system.img when it was in the same folder as everything else. I ended flashing all the files manually.
Ki77erB said:
I had the same issue, then when I made the decision to use the flash-all script, I got another error about missing the system.img when it was in the same folder as everything else. I ended flashing all the files manually.
Click to expand...
Click to collapse
It's common problem with flashing 5.1.
zagorteney said:
It's common problem with flashing 5.1.
Click to expand...
Click to collapse
I think I'm going to do the flash-all.bat. I've done that before and since I can save my app data by omitting -w then this method should be fine. I am going to make sure I have the latest adb and fastboot first so hopefully I don't get the common missing system.img error. Once I do this, will it correct the install-recovery.sh file so I can take future OTAs again? Also, the -w retains all app settings and data right?....it just doesn't preserve the internal SD card data?
xda6969 said:
I think I'm going to do the flash-all.bat. I've done that before and since I can save my app data by omitting -w then this method should be fine. I am going to make sure I have the latest adb and fastboot first so hopefully I don't get the common missing system.img error. Once I do this, will it correct the install-recovery.sh file so I can take future OTAs again?
Click to expand...
Click to collapse
As I know, you shouldn't be rooted or make any other modifications with system to get OTA.
zagorteney said:
As I know, you shouldn't be rooted or make any other modifications with system to get OTA.
Click to expand...
Click to collapse
That's correct. I am no longer rooted and I haven't modified any system files intentally. Somehow, just booting into TWRP made a change to that file. I never had this issue when I was using CR.
zagorteney said:
As I know, you shouldn't be rooted or make any other modifications with system to get OTA.
Click to expand...
Click to collapse
Yep; SuperSU for example modifies /system/etc/install-recovery.sh (or /system/bin/install-recovery.sh) and a couple more files.
xda6969 said:
That's correct. I am no longer rooted and I haven't modified any system files intentally. Somehow, just booting into TWRP made a change to that file. I never had this issue when I was using CR.
Click to expand...
Click to collapse
Never heard of TWRP modifying /system on its own.
beekay201 said:
Yep; SuperSU for example modifies /system/etc/install-recovery.sh (or /system/bin/install-recovery.sh) and a couple more files.
Never heard of TWRP modifying /system on its own.
Click to expand...
Click to collapse
Ahh...I did install SuperSU to unroot. But I also installed it on a N10 to unroot it and it took the OTA without a hitch.
I did the flash-all.bat after removing the -w. Everything went fine. I hope the install-recovery.sh file was corrected. Thanks all for the help!
my sister in-law has the nexus 5 and i have been trying to help her get it updated. it is still on 4.4.3 it downloads the 4.4.4 patch but refuses to install. i tried to use ADB and side load the 4.4.4 and it fails. both times it says /system/app/hangouts.apk has unexpected contents
so i wiped the phone to the factory image of 4.4.3 because that was the restore image on the phone. Build number KTU84M
now when i try to do it the error changed to a cache file of hangouts. i didn't write it down so i don't have that one verbatim. can someone please help me figure this out.... the only thing i can think of at this point is to unlock the boot loader and force a factory image, but its not my phone so i was trying to avoid that. any help is grateful thanks.
clevenger23 said:
my sister in-law has the nexus 5 and i have been trying to help her get it updated. it is still on 4.4.3 it downloads the 4.4.4 patch but refuses to install. i tried to use ADB and side load the 4.4.4 and it fails. both times it says /system/app/hangouts.apk has unexpected contents
so i wiped the phone to the factory image of 4.4.3 because that was the restore image on the phone. Build number KTU84M
now when i try to do it the error changed to a cache file of hangouts. i didn't write it down so i don't have that one verbatim. can someone please help me figure this out.... the only thing i can think of at this point is to unlock the boot loader and force a factory image, but its not my phone so i was trying to avoid that. any help is grateful thanks.
Click to expand...
Click to collapse
Have you tried using this tool kit? This tool kit is great. Just one click everything but make sure you have unlocked bootloader (which this tool can do as well)
All you need to do is enable usb debugging in your phone and install drivers (use the toolkit again)
http://www.wugfresh.com/nrt/
Quote if you expect a response
Hnk1 said:
Have you tried using this tool kit? This tool kit is great. Just one click everything but make sure you have unlocked bootloader (which this tool can do as well)
All you need to do is enable usb debugging in your phone and install drivers (use the toolkit again)
http://www.wugfresh.com/nrt/
Quote if you expect a response
Click to expand...
Click to collapse
He says at the end of his post that he would rather keep bootloader locked.
---------- Post added at 11:48 AM ---------- Previous post was at 11:35 AM ----------
clevenger23 said:
my sister in-law has the nexus 5 and i have been trying to help her get it updated. it is still on 4.4.3 it downloads the 4.4.4 patch but refuses to install. i tried to use ADB and side load the 4.4.4 and it fails. both times it says /system/app/hangouts.apk has unexpected contents
so i wiped the phone to the factory image of 4.4.3 because that was the restore image on the phone. Build number KTU84M
now when i try to do it the error changed to a cache file of hangouts. i didn't write it down so i don't have that one verbatim. can someone please help me figure this out.... the only thing i can think of at this point is to unlock the boot loader and force a factory image, but its not my phone so i was trying to avoid that. any help is grateful thanks.
Click to expand...
Click to collapse
Basically, something happened to hangouts.apk and now the ota update doesn't run.
Sideloading won't help here, it will just error just the same, like you've found for yourself.
Mhm. This will take some tinkering.
First steps, unpack system.img from factory image KTU84M and use towelroot to get root on the device.
Enable USB debugging on the device, get an adb root prompt on the PC ('adb root'), remount /system rw, push KTU84M hangouts.apk to overwrite existing file, remount /system ro, reboot.
Run the ota again.
PS if it then complains about root... He he let me know
Thank you for the help.
beekay201 said:
He says at the end of his post that he would rather keep bootloader locked.
---------- Post added at 11:48 AM ---------- Previous post was at 11:35 AM ----------
Basically, something happened to hangouts.apk and now the ota update doesn't run.
Sideloading won't help here, it will just error just the same, like you've found for yourself.
Mhm. This will take some tinkering.
First steps, unpack system.img from factory image KTU84M and use towelroot to get root on the device.
Enable USB debugging on the device, get an adb root prompt on the PC ('adb root'), remount /system rw, push KTU84M hangouts.apk to overwrite existing file, remount /system ro, reboot.
Run the ota again.
PS if it then complains about root... He he let me know
Click to expand...
Click to collapse
Thanks for all the advice. I ended up getting very upset. I copied all of her pictures and backed up all her contacts, told her opps... so just to go deeper into this rabbit hole. I recovered the phone to the factory 4.4.3 image. Still refused to update. Tried again to use adb to side load. Nothing. Flashed again including cache, still no dice. So then I went and got the 5.0.1 update from Google. Since I had already erased the phone, I unlocked the boot loader, and tried to flash the phone. That failed as well. Over and over. So I had to do it one partition at a time. Then it took the 5.0.1 image. Now to add another thing that makes no sense to me. Her wall paper that was a picture of her and her daughter stayed on the phone as the background. Also every app was in its place, but grayed out. They where not in the phone, but the phone remembered they where there. Had to redownload then but how in the world did that stay, when I factory restored the phone twice, and then flashed a factory ROM to make it update. Also I know it was a good update because in the middle of updating apps, it downloaded 5.1 OTA and that installed fine. Just to give some insight as to what I had to do.
"system partition has unexpected contents" March 2016 OTA or Sideload Failed Error 7
Hi,
My N5 is rooted and on factory images (6.0.1). I have reverted to stock recovery from twrp 3.0.0.0 because my system wouldn't accept Feb security updates.
After reverting to stock recovery, Feb updates worked fine.
March updates however continually fail with Error 7 (modified system partition?), either by system OTA or sideloading over adb / stock recovery.
I think, the last thing that I did was installed Wake Lock Detector, converted to a system app, this broke and couldn't be removed or converted back to a user app, so I had to force remove it via a convoluted system of Ti and other Root Uninstaller apps. Got rid of it in the end.
Anyway, this is the only thing I can think of that may be causing this Error 7, and I'm out of options. That's why I'm here.
The CM team seem to have some solutions to this issue. Anyone have any ideas for stock peeps?
Do I really need to unroot and reflash stock etc etc etc? I'd rather not.
Thanks, as ever, for the great support on XDA!
1. Check if the bootloader is hhz12k
2. Try use twrp 2.8.7.1 instead
3. Check adb version installed in your pc
I've gone back to pure stock...huge pain. Before I did this I reset to full stock, rooted and tested again...root broke the OTA and side load with error 7. Hence why I'm back unrooted and fully stock again. I want updates.
tedrogers61 said:
I've gone back to pure stock...huge pain. Before I did this I reset to full stock, rooted and tested again...root broke the OTA and side load with error 7. Hence why I'm back unrooted and fully stock again. I want updates.
Click to expand...
Click to collapse
Not many people replied to you as it has been said over and over and over. On marshmallow any change to system partition breaks the ability to apply OTAs. If you want the updates so bad, just download the new factory image and fastboot flash system.img. Then re-root. You wont lose data this way.
Thanks very much. I didn't know this and I swear I searched high and low...obviously not in the right areas. I ask a question on XDA when I feel I've googled the topic to death with no satisfactory outcome. So I can reflash a new system image over the top and all data remains intact? Good to know. Thank you.
tedrogers61 said:
Thanks very much. I didn't know this and I swear I searched high and low...obviously not in the right areas. I ask a question on XDA when I feel I've googled the topic to death with no satisfactory outcome. So I can reflash a new system image over the top and all data remains intact? Good to know. Thank you.
Click to expand...
Click to collapse
@tedrogers61: Make sure you only flash the system.img part - you have to do that manualy, dont use the .bat in the package.
Otherwise you WILL lose your data 100%, because the .bat file is flashing anything AND erase userdata+cache partition by default !
What you need to do :
1. Download factory image at https://developers.google.com/android/nexus/images#hammerhead
2. Use 7zip to unpack the .tgz, then again unzip the .tar, then unzip the image-hammerhead-mmb29v.zip (if you are using windows)
3. copy the system.img to a easy to find location (optional, just helps to find the system.img)
4. if you have USB Debug activated+USB cable + ADB installed (which i guess you have), connect your phone to USB, Phone runing normally and open a command prompt.
Enter these commands:
Code:
adb reboot bootloader
fastboot flash system <path-to-your-system.img>
On first command, the phone should reboot and display should show an android laying on his back
Next command should give you feedback in command prompt like "Erasing system"..."sending system"..."writing system".
The phone display should show similiar informations.
Thats it - you need to apply root after this.
You need to restart the phone manualy but as long as the command prompt shows OKAY and "finished. total time xyz seconds", everything worked fine.
Thank you @Warlord711, I worked out it was fastboot flash system system.img.
Testing this on my N5 right not which won't receive April OTA.
Might give this a go on my N5X later, which won't go past Feb OTA.
Is there a pattern here? Is there something wrong with my account which is preventing OTA's perhaps?
wangdaning said:
Not many people replied to you as it has been said over and over and over. On marshmallow any change to system partition breaks the ability to apply OTAs. If you want the updates so bad, just download the new factory image and fastboot flash system.img. Then re-root. You wont lose data this way.
Click to expand...
Click to collapse
Thank you very much.
tedrogers61 said:
Thank you @Warlord711, I worked out it was fastboot flash system system.img.
Testing this on my N5 right not which won't receive April OTA.
Might give this a go on my N5X later, which won't go past Feb OTA.
Is there a pattern here? Is there something wrong with my account which is preventing OTA's perhaps?
Click to expand...
Click to collapse
As mentioned, if anything is modified (root, custom recovery, etc) you will not be able to use OTA. Another problem, for people like me, cannot access google servers. Your google account is not linked to OTA, so it is not that. Doesn't really matter anyway, like you found, easy enough to just do it yourself. I live in China so have no choice anyway, haha, but it is simple. Personally, I do not use stock roms anyway, so don't really care.
Hope by performance fixes they mean memory leak fix.
I have not seen os ram usage this low after boot in many months.
Did you have round corner?
yaral said:
Did you have round corner?
Click to expand...
Click to collapse
It squared it when I screenshot.
Anybody figure out how to turn off the rounded corners?
Anyone know what the modem sucurity patch is about? Kinda don't want to take it cuz of the sim lock issues awhile back.
enigma2446 said:
Anyone know what the modem sucurity patch is about? Kinda don't want to take it cuz of the sim lock issues awhile back.
Click to expand...
Click to collapse
no clue but i fastboot flashed the images because the OTA refused to work, but flashing the images worked. i'm still able to connect to ATT towers from my sprint sim unlocked PH-1.
TomTheGeek3 said:
no clue but i fastboot flashed the images because the OTA refused to work, but flashing the images worked. i'm still able to connect to ATT towers from my sprint sim unlocked PH-1.
Click to expand...
Click to collapse
Noob question here: When using fastboot to flash the update image, do you have to worry about the "slot A" vs "slot B" thing?? Can you provide a little more insight? I've been reading around the forum, and I'm a little worried about bricking my phone! (The bootloader on my phone is unlocked and I've rooted the phone, but I haven't flashed a third-party ROM. The OTA update feature gives me a "couldn't update" message.)
adiejg said:
Noob question here: When using fastboot to flash the update image, do you have to worry about the "slot A" vs "slot B" thing?? Can you provide a little more insight? I've been reading around the forum, and I'm a little worried about bricking my phone! (The bootloader on my phone is unlocked and I've rooted the phone, but I haven't flashed a third-party ROM. The OTA update feature gives me a "couldn't update" message.)
Click to expand...
Click to collapse
No you don't have to worry about it. The flash all file in the zip will do all the work for you. It wont take update via ota because you have to be on the stock boot.img. the stock boot img has the recovery built into the ramdisk there for if your rooted then there is no stock recovery to use for ota. Be cautious because flashing via fastboot will wipe the phone.
enigma2446 said:
No you don't have to worry about it. The flash all file in the zip will do all the work for you. It wont take update via ota because you have to be on the stock boot.img. the stock boot img has the recovery built into the ramdisk there for if your rooted then there is no stock recovery to use for ota. Be cautious because flashing via fastboot will wipe the phone.
Click to expand...
Click to collapse
If I edit the .bat file and remove "format userdata", that will prevent the wipe?
njsges said:
If I edit the .bat file and remove "format userdata", that will prevent the wipe?
Click to expand...
Click to collapse
It should without issues but always prepare for hickups.
Anyone else having issues when trying to update to the February release? I tried to sideload the OTA update and that kept giving me the error "adb sideload failed to read command: no error" and then I decided to follow Morphius's suggestion here to just unroot my device by flashing to stock bootloader in order to try to take the OTA update and that OTA keeps failing as well. Anyone else having this issue?
hssxda said:
Anyone else having issues when trying to update to the February release? I tried to sideload the OTA update and that kept giving me the error "adb sideload failed to read command: no error" and then I decided to follow Morphius's suggestion here to just unroot my device by flashing to stock bootloader in order to try to take the OTA update and that OTA keeps failing as well. Anyone else having this issue?
Click to expand...
Click to collapse
Are you rooted?
After three days running, memory Leak not fixed.. Bummer
enigma2446 said:
No you don't have to worry about it. The flash all file in the zip will do all the work for you. It wont take update via ota because you have to be on the stock boot.img. the stock boot img has the recovery built into the ramdisk there for if your rooted then there is no stock recovery to use for ota. Be cautious because flashing via fastboot will wipe the phone.
Click to expand...
Click to collapse
Again, a very noob question, (and I do apologize) but can I use something like Titanium Backup to make sure I can restore all my apps the way they were after I flash the update via fastboot? Reinstalling everything seems like a gigantic pain in the backside.
adiejg said:
Again, a very noob question, (and I do apologize) but can I use something like Titanium Backup to make sure I can restore all my apps the way they were after I flash the update via fastboot? Reinstalling everything seems like a gigantic pain in the backside.
Click to expand...
Click to collapse
Titanium Backup used to require root access. You probably need to be rooted before you update via fastboot and run the backup through Titanium Backup. Then you will need to copy your backup files to a computer because fastboot flashing will erase your phone data. Next apply the fastboot update, root again, copy your backup back to the phone and restore your backup.
enigma2446 said:
Are you rooted?
Click to expand...
Click to collapse
I was but I followed all the proper steps but for some reason this morning my computer wouldn't real the OTA zip file. I tried it tonight using a different USB port on my laptop and it is worked first time... so weird...
d14r1 said:
After three days running, memory Leak not fixed.. Bummer
Click to expand...
Click to collapse
I don't have memory leak anymore..
1.5gb ram not in usage.
The last time I restarted my phone was after the update.
I'm using my Essential 'phone in the UK having recently purchased it used. On the 7th I had a notice to say that an update was available. When I tried to install it it downloaded, but refused to install saying: Couldn't update... installation problem. As far as I know the 'phone is running the stock software but I noticed that no updates had been installed since October 2018. I unchecked 'allow bootloader unlocking' in case that was the issue, but still couldn't perform the update.
I went onto the Essential website and downloaded the OTA image to my iMac, then, following the guide, sideloaded the update on to the 'phone. This worked well and I now have an updated PH-1. I'll have to see if March's update now installs correctly or not.
so.... am i reading this right... and here is my thinking...
to keep root and still take the OTAs
- go to Essentials site and download the image zip
- (to keep root) copy boot.img to your device, patch it through magisk, then copy it back to your ota folder.
- open flashall.bat, comment the format userdata (to keep your data), change the boot.img line to patched_boot.img
- run flashall.bat
- profit