Hi,
I have an odd problem. I have rooted my nexus S and am on 2.3.2, and have clockwork recovery. however in order to apply the update to 2.3.3, it doesnt not work with clockwork recovery, and so I was trying to flash stock recovery using a recovery.img file from one of the stock nandroids on the site.
when I am in bootloader, and i try fastboot flash recovery recovery.img where this is the stock recovery image, it gives me a "remote: Write Fail" error.
However I have no problem in using the same command to flash clockwork recovery image.
Does anyone know why this is happening? and does anyone know how i can flash the stock recovery image back to my phone so I can apply the update to 2.3.3?
Thanks,
brownmonkey said:
Hi,
I have an odd problem. I have rooted my nexus S and am on 2.3.2, and have clockwork recovery. however in order to apply the update to 2.3.3, it doesnt not work with clockwork recovery, and so I was trying to flash stock recovery using a recovery.img file from one of the stock nandroids on the site.
when I am in bootloader, and i try fastboot flash recovery recovery.img where this is the stock recovery image, it gives me a "remote: Write Fail" error.
However I have no problem in using the same command to flash clockwork recovery image.
Does anyone know why this is happening? and does anyone know how i can flash the stock recovery image back to my phone so I can apply the update to 2.3.3?
Thanks,
Click to expand...
Click to collapse
CWM will apply the signed 2.3.3 update without a problem - what issue are you having where you can't apply through CWM?
krohnjw said:
CWM will apply the signed 2.3.3 update without a problem - what issue are you having where you can't apply through CWM?
Click to expand...
Click to collapse
so I downloaded the update and changed the filename to update.zip and put it in the root of /sdcard/
then when I boot into clockwork mod recovery, and click "apply update from sdcard" it starts running and after getting to verifying current system i get the following error
assert failed: apply_patch_check("/system/build.prop",...)
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted
and idea what is causing the problem? im a complete noob when it comes to this stuff
brownmonkey said:
so I downloaded the update and changed the filename to update.zip and put it in the root of /sdcard/
then when I boot into clockwork mod recovery, and click "apply update from sdcard" it starts running and after getting to verifying current system i get the following error
assert failed: apply_patch_check("/system/build.prop",...)
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted
and idea what is causing the problem? im a complete noob when it comes to this stuff
Click to expand...
Click to collapse
Yeah - it's checking build.prop and it's either been modified or you are not running a stock rom.
It's going to check quite a few files in the system partition and verify they match what it's expecting (as it is patching them) before it performs the update. If they don't match it will not proceed and you will get an assert failed error. This is not a boot loader problem, rather a file problem.
Did you apply anything that would have updated build.prop?
krohnjw said:
Yeah - it's checking build.prop and it's either been modified or you are not running a stock rom.
It's going to check quite a few files in the system partition and verify they match what it's expecting (as it is patching them) before it performs the update. If they don't match it will not proceed and you will get an assert failed error. This is not a boot loader problem, rather a file problem.
Did you apply anything that would have updated build.prop?
Click to expand...
Click to collapse
Yes i did, I added in a few lines to increase my download speeds, and set it so that it always locks to hspa... if i remove the lines and resave build.prop file should that fix the issue and allow me to update?
brownmonkey said:
Yes i did, I added in a few lines to increase my download speeds, and set it so that it always locks to hspa... if i remove the lines and resave build.prop file should that fix the issue and allow me to update?
Click to expand...
Click to collapse
So i tried the above... i removed the two extra lines I had added to build.prop and tried the update but it still gives the same error? Do you know of any way I can get around this error or is the only way to do a titanium backup and flash the stock 2.3.3 version that has been posted in another link?
Thanks for your quick replies.
You may be able to flash the full update. Or get a build.prop from a 2.3.2 build if someone can pull it.
Sent from my Nexus S using XDA Premium App
Related
IMPORTANT: The process described in this post breaks WiMAX, so I have removed the download links, and I recommend that no one attempt it. Please see this thread for a way to get from the original stock everything all the way up to the latest rooted OTA with the latest radio+WiMAX firmwares without even needing adb.
~~~ remainder of this post retained for historical interest only ~~~
Background: I didn't want to flash a full /system partition to upgrade my EVO 4G from Flipz's rooted stock 1.32.651.6 ROM to the latest 1.47.651.1, and I feel better using a barely modified "official" update from Sprint/HTC, so here's what I did:
Allowed the phone to download the update from Sprint/HTC. (It downloads into /cache.)
Copied the update to my computer and unzipped it.
Edited the META_INF/com/google/android/updater-script. (See below for a diff.)
Removed the recovery.img from the firmware.zip. (I don't want to go back to a stock recovery.)
Deleted the patch files for Sprint_Qik.apk and Sprint_TV.apk, since I've deleted those apps from my phone.
Edited the /system/build.prop file on the phone to remove the line that Flipz added at the bottom, thus restoring it to its stock condition (sha1=ee40d5143cf1089af2575045a9db9061f0d0dca9).
Zipped the update back up and signed it.
Download the update here:
OTA_Supersonic_1.47.651.1-1.32.651.6_rootsafe.zip
(md5=913c7594ca8ca94594a2c8e1ec9b5564)
Download the original build.prop file here:
build.prop-1.32.651.6
(md5=a29ab0ec25ad976bd12bc8bad5a97063)
Alternate: If you kept Sprint TV and Sprint Qik, use this update zip instead:
OTA_Supersonic_1.47.651.1-1.32.651.6_rootsafe-Sprint.zip
(md5=410f57feeaebcf89c5497cd6e599a807)
Before you begin: You MUST be using a rooted stock 1.32.651.6 ROM, such as this one released by Flipz. Because this update is an incremental update, it cannot apply to any other ROM, even custom ROMs having the same base system version.
How to install this update:
Caution: There has been a report that updating using this method breaks the WiMAX. If that's true, it can only be because HTC must have added some new function to their recovery program that the custom recoveries don't have. It is recommended that you run a Nandroid backup in case you need to revert.
Download the two files linked above.
adb push OTA_Supersonic_1.47.651.1-1.32.651.6_rootsafe.zip /sdcard/ (Or copy the update zip to your SD card by some other means.)
adb remount
adb push build.prop-1.32.651.6 /system/build.prop (See below for what to do if this step fails.)
adb reboot recovery
Run a Nandroid backup just in case.
Flash from the update zip and reboot.
The radio+WiMAX updates will install. This takes a while. Don't touch it. When it's finished, it will reboot on its own.
You'll find yourself in recovery one last time. Reboot.
It'll sit on the "4G" splash for a long time. Don't panic.
Once the home screen appears, go to Settings, About Phone, and verify that your "Software number" is 1.47.651.1 and your "Baseband version" is 2.05.00.06.10.
You may need to remove and re-add some home screen widgets.
If you're still using su and Superuser.apk from Flipz's stock rooted ROM, you will need to install the su-2.1-e-unsecure-signed.zip from this thread. It's a much, much newer version than the one Flipz included. It's an update zip, so install it via recovery.
Enjoy!
What to do if pushing build.prop fails:
This probably means you haven't unlocked NAND by flashing the engineering SPL. That's okay. Your custom recovery program probably supports adb while in recovery mode. If so, you can simply reboot the phone into recovery, perform step #4 from above, skip step #5, and continue from step #6.
For the curious, here's the diff of the updater-script from the stock update to mine: updater-script-1.47.651.1.diff
Troubleshooting
If you're getting an error that says assert failed: apply_patch_check, it means something about your system is different from a totally stock 1.32.651.6 system. Most likely you're running a custom ROM, not a rooted stock ROM, you've already applied the update, or you've installed some kind of hack like QuickBoot. Because this update is an incremental update, it can only be applied to a rooted (but otherwise unaltered) stock 1.32.651.6 ROM. Try flashing Flipz's stock rooted 1.32.651.6 ROM and then proceeding with the steps above under "How to install this update."
If Wireless Tether gets stuck when starting tethering, it probably means you still have the old and crusty su and Superuser.apk. Install the su-2.1-e-unsecure-signed.zip update mentioned above to get the latest set of superuser tools. Then Wi-Fi Tether should work fine.
Thank you. Will see if this fixes my broken 4G.
wsantiagow said:
Links Please?
Click to expand...
Click to collapse
The forum wouldn't let me post links. Apparently it's an anti-spam policy. As soon as a moderator is nice enough to bless my account, I'll turn those URLs into links.
please add back in Qik and TV... let users delete that after? many people use those programs.
either way, nice work
Does this include all of the contents of the original update, including the change to the Bit Rate of the Camera?
blehzz said:
please add back in Qik and TV... let users delete that after? many people use those programs.
either way, nice work
Click to expand...
Click to collapse
Get the rootsafe-Sprint.zip instead. The only differences between it and the stock update are that it doesn't include the recovery image and it preserves setuid+setgid root for /system/xbin/su.
wsantiagow said:
Thank you. Will see if this fixes my broken 4G.
Click to expand...
Click to collapse
I'm assuming broken as in you ran the unrevoked update?
Any luck?
Also, OP:
Does 4G work for you after this? I remember reading in some other threads that 4G wasn't working for images flashed without the default recovery. Not sure if I'm taking it out of context or if this is an issue.
wphend00 said:
Does this include all of the contents of the original update, including the change to the Bit Rate of the Camera?
Click to expand...
Click to collapse
It's exactly the update package furnished from Sprint over-the-air (the 30.2 MiB one), but with one line added to the updater script so that the update doesn't kill the setuid permissions on /system/xbin/su.
That means it changes everything Sprint changed in the latest update, including kernel, radio, WiMAX, and anything else.
So can I use this over a rooted Fresh .53 without breaking the root? Is this what you are running?
whitslack said:
The forum wouldn't let me post links. Apparently it's an anti-spam policy. As soon as a moderator is nice enough to bless my account, I'll turn those URLs into links.
Click to expand...
Click to collapse
..........
ViViDboarder said:
Also, OP:
Does 4G work for you after this? I remember reading in some other threads that 4G wasn't working for images flashed without the default recovery. Not sure if I'm taking it out of context or if this is an issue.
Click to expand...
Click to collapse
There's no 4G coverage in my area, so I can't know whether it works for sure. I can turn on 4G, though, and it says "Scanning." Also, the ip link command shows the wimax0 network interface is present, so I would assume that means the kernel module loaded successfully.
FWIW, I flashed the update using toast's recovery (md5=0ba574fe3a8d82e4e796cc306efa63a7). It definitely goes through the extra reboot cycle for flashing the firmwares. I see no reason why it wouldn't flash the WiMAX firmware, given that it's essentially the stock update process.
bjrmd said:
So can I use this over a rooted Fresh .53 without breaking the root? Is this what you are running?
Click to expand...
Click to collapse
I can't guarantee the patches will apply cleanly against anything other than the stock 1.32.651.6. It won't hurt to try it. The updater script has checks to be sure everything will apply cleanly before it touches anything, so the worst that can happen to you is that it will politely refuse to apply.
whitslack said:
I can't guarantee the patches will apply cleanly against anything other than the stock 1.32.651.6. It won't hurt to try it. The updater script has checks to be sure everything will apply cleanly before it touches anything, so the worst that can happen to you is that it will politely refuse to apply.
Click to expand...
Click to collapse
Only a stock 1.32.651.6? What if I'm running a stock ROOTED 1.32.651.6?
Also, can I just drop it in my SD card and flash it from there using Clockwork Recovery, or does it have to go through via the commands?
Thanks, btw!
whitslack said:
There's no 4G coverage in my area, so I can't know whether it works for sure. I can turn on 4G, though, and it says "Scanning." Also, the ip link command shows the wimax0 network interface is present, so I would assume that means the kernel module loaded successfully.
FWIW, I flashed the update using toast's recovery (md5=0ba574fe3a8d82e4e796cc306efa63a7). It definitely goes through the extra reboot cycle for flashing the firmwares. I see no reason why it wouldn't flash the WiMAX firmware, given that it's essentially the stock update process.
Click to expand...
Click to collapse
Right... Well, here it scans and then turns off wimax and then turns it back on and keeps doing that. Working with joshua_ last night I got it to keep scanning... It never did get an IP though but the interface was definitely present. I could see it with netcfg from the adb shell.
I pointed joshua_ to this thread to see what he things of these patches. I had been trying to help him use my phone to debug this issue so I don't want to mess things up too much for him.
I get an install aborted when trying to run the update zip. Starts the install then just stops and give an install aborted.
BTW I am now using a Fresh and not DC on my phone. And I am fully rooted(NAND unlocked) and have been able to run several other updates.zip without issue, currently using Clockwork MOD for recovery and not RA
rugedraw said:
Only a stock 1.32.651.6? What if I'm running a stock ROOTED 1.32.651.6?
Also, can I just drop it in my SD card and flash it from there using Clockwork Recovery, or does it have to go through via the commands?
Thanks, btw!
Click to expand...
Click to collapse
It will probably fail if you don't have a file at /system/xbin/su, which only rooted ROMs have. If you're running totally stock, you should just use the automatic OTA update from Sprint. If you're running rooted stock, you should use this. (I was using Flipz's rooted stock initially, so that's what I tested against.)
Badious said:
I get an install aborted when trying to run the update zip. Starts the install then just stops and give an install aborted.
Click to expand...
Click to collapse
What recovery are you using? Amon RA 1.7.0.1 wouldn't work for me. It kept complaining about no signatures, even though I had signed the update. I used toast's recovery successfully.
If that's not the problem, then it can only be that some file on your phone is not identical to the version from the stock 1.32.651.6. Did you replace the /system/build.prop file with the stock one linked in the OP? In particular, this update will not apply against Flipz's stock rooted ROM unless you replace that file with the really stock one.
Yep downloaded the buildprop in the OP and copied that over via ADB successfully(checked softwar version and it shows stock buildprop info)
Let me try it one more time and see exactly what it is bawking about.
Ok. Error Reads as Such:
Verifying Current System....assert failed: apply_patch_check ("system/app/AccountandSyncSettings.apk" . TWO LONG SETS OF HEX NUMBERS[if you need them I can provide them])
E: Error in /sdcard/OTA..(name of full file)
(status 7)
Installation Aborted.
ERROR:
Verifying current system...
assert failed: apply_patch_check ("/system/app/AccountAndSyncSettings.apE:unknown command [k",]
E:unknown command [56479c22c")]
E:Error in /sdcard/OTA_Supersonic_1.47.651.1-1.32.651.6_rootsafe-Sprint.zip
(Status 7)
Installation aborted.
Can someone assist please, would like to get this new Radio OTA flashed....
Edit: Running DC 3.2.1 with Aloyisus Theme
whitslack said:
It will probably fail if you don't have a file at /system/xbin/su, which only rooted ROMs have. If you're running totally stock, you should just use the automatic OTA update from Sprint. If you're running rooted stock, you should use this. (I was using Flipz's rooted stock initially, so that's what I tested against.)
Click to expand...
Click to collapse
Thanks for the quick response! I am running a rooted version of 1.32.651.6 and I've been waiting for something like this. So I should be OK using clockwork recovery to run this?
rugedraw said:
Also, can I just drop it in my SD card and flash it from there using Clockwork Recovery, or does it have to go through via the commands?
Click to expand...
Click to collapse
You can put it on your SD card by any means available to you. The only requirement is that your recovery program does not care that it's signed by someone other than HTC.
TheMike1 said:
ERROR:
Verifying current system...
assert failed: apply_patch_check ("/system/app/AccountAndSyncSettings.apE:unknown command [k",]
E:unknown command [56479c22c")]
E:Error in /sdcard/OTA_Supersonic_1.47.651.1-1.32.651.6_rootsafe-Sprint.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
That can only mean that you're not using the stock ROM (w/ root added). This is an incremental update straight from the official sources with one slight tweak to preserve root access, so you must be using a stock system in order for it to apply.
Users of custom ROMs should be flashing new versions of those custom ROMs. The incremental upgrade path here will not work on custom ROMs.
I am trying to install ota 1.84 from 1.53 stock backup I made when I 1st rooted-after I flashed the stock rom to my device I was prompted for the ota update which I downloaded I fastboot flash stock recovery used ota rootkeeper to protect root when I went to install the update it went about 25% then this message appeared,epic fail I rechecked my rom to make sure there wasn't any rooted apps on it just plain stock I know it something I have missed along the way but I stuck atm -went ahead and reflashed cwm and restored backup -Can anyone help point me in the right direction on this one??I apoligized in advance if its been posted somewhere on here I have failed to locate and answer
jmcdonald58 said:
I am trying to install ota 1.84 from 1.53 stock backup I made when I 1st rooted-after I flashed the stock rom to my device I was prompted for the ota update which I downloaded I fastboot flash stock recovery used ota rootkeeper to protect root when I went to install the update it went about 25% then this message appeared,epic fail I rechecked my rom to make sure there wasn't any rooted apps on it just plain stock I know it something I have missed along the way but I stuck atm -went ahead and reflashed cwm and restored backup -Can anyone help point me in the right direction on this one??I apoligized in advance if its been posted somewhere on here I have failed to locate and answer
Click to expand...
Click to collapse
hopefully better image
Geeze best image i have
I never apply ota update but hope this help you out.
http://www.jbhale.com/2012/06/09/dev-how-to-apply-ota-htc-tested-on-one-s/
Sent from my HTC One S using Tapatalk 2
It says Error in file, have you tried redownloading it? Did you manually download the OTA file or did you get it the usual way (search for updates in phone).
x1tyme said:
I never apply ota update but hope this help you out.
http://www.jbhale.com/2012/06/09/dev-how-to-apply-ota-htc-tested-on-one-s/
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Thanks will give it a look
frdd said:
It says Error in file, have you tried redownloading it? Did you manually download the OTA file or did you get it the usual way (search for updates in phone).
Click to expand...
Click to collapse
I downloaded it directly from device
It says:
Code:
Verifying current system...
assert failed: blablabla
To me, this means:
It checks the system on your device to see if it can take this OTA, but the hash of your build.prop file does not match what it expects.
Maybe this OTA is not for your device or you're not on truly stock 1.53.
-Jobo
touch of jobo said:
It says:
Code:
Verifying current system...
assert failed: blablabla
To me, this means:
It checks the system on your device to see if it can take this OTA, but the hash of your build.prop file does not match what it expects.
Maybe this OTA is not for your device or you're not on truly stock 1.53.
-Jobo
Click to expand...
Click to collapse
Yeah going take a look at it later that's kinda what I was thinking anyhow I appreciate the help
Hello,
I wanted to upgrade from 4.4 to 4.4.2 through recovery.
The thing is that I took the wrong file and got a "failed to verify whole file signature" error when I "adb sideloaded".
I finally succeeded installing the 4.4.2 but I am wondering if I should clean somehow the phone as some files (from the wrong update file) were sent to the device and the upgrade was aborted.
Thanks
rarat said:
Hello,
I wanted to upgrade from 4.4 to 4.4.2 through recovery.
The thing is that I took the wrong file and got a "failed to verify whole file signature" error when I "adb sideloaded".
I finally succeeded installing the 4.4.2 but I am wondering if I should clean somehow the phone as some files (from the wrong update file) were sent to the device and the upgrade was aborted.
Thanks
Click to expand...
Click to collapse
If the upgrade was aborted, there is nothing to clean up. It validates the file first before it attempts to flash. So, the flash hasn't started by then.
You should be good
jj14 said:
If the upgrade was aborted, there is nothing to clean up. It validates the file first before it attempts to flash. So, the flash hasn't started by then.
You should be good
Click to expand...
Click to collapse
Thanks for the reply. I thought some files would have to be uploaded solewhere before it can verify the signature.
Will I continue to get OTA software updates if I root and unlock the boot loader (to install TWRP)?
Thanks,
Hish747
Yes, make sure to untick to update the recovery in the debug options
Send from OnePlus One using Tapatalk
Yes.Of course.But it happened to me that the update script showed some errors. I had to fix them by downloading the original files and replacing my system files.
want to love this device but it seems like its always something.
---------- Post added at 04:35 PM ---------- Previous post was at 04:33 PM ----------
Sorry wrong thread...
Satras said:
Yes, make sure to untick to update the recovery in the debug options
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
Can I dirty flash the nightlies from CM11S if I have just unlocked the bootlader and rooted?
There is no nightly for CM11s just for CM11.
I recommend to do a clean install including factory reset.
Keep in mind that after flashing something, you need to flash root at the end too
Send from OnePlus One using Tapatalk
So we will still get OTA's great! Great phone for costumizations.
ZTube said:
Yes.Of course.But it happened to me that the update script showed some errors. I had to fix them by downloading the original files and replacing my system files.
Click to expand...
Click to collapse
That does not happen if you just unlock, root and install a custom recovery.
Also a custom kernel would be fine
Send from OnePlus One using Tapatalk
Sorry if this is a bit of a n00b question (I know people are sensitive about that!) but I have searched around a bit and not found a solution to this issue. Here's the situation...
So what i've done so far is unlocked the bootloader, installed TWRP, and SuperSU (so I have root). I also unchecked the update recovery box in dev options. When told I need to update I downloaded the update, hit install, the phone reboots and takes me to TWRP. When in TWRP I hit install, navigate to the cache and try to install the update /cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip
When I do that, I get the following:
"
E:Error installing zip file '/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Done processing script file
Installing '/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Can't install this package on top of incompatible data. Please try another package or run a factory reset
E: Error executing updater binary in zip ''/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Error flashing zip ''/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Updating partition details...
"
Anybody got any ideas?
Seems TWRP expects a MD5 file.
I use CWM as recovery and can install the update OTA. Maybe try CWM recovery
Send from OnePlus One using Tapatalk
Satras said:
Seems TWRP expects a MD5 file.
I use CWM as recovery and can install the update OTA. Maybe try CWM recovery
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
Most people that ive read about are using twrp and had no problem updating.
aamir.m.ali said:
Sorry if this is a bit of a n00b question (I know people are sensitive about that!) but I have searched around a bit and not found a solution to this issue. Here's the situation...
So what i've done so far is unlocked the bootloader, installed TWRP, and SuperSU (so I have root). I also unchecked the update recovery box in dev options. When told I need to update I downloaded the update, hit install, the phone reboots and takes me to TWRP. When in TWRP I hit install, navigate to the cache and try to install the update /cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip
When I do that, I get the following:
"
E:Error installing zip file '/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Done processing script file
Installing '/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Can't install this package on top of incompatible data. Please try another package or run a factory reset
E: Error executing updater binary in zip ''/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Error flashing zip ''/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Updating partition details...
"
Anybody got any ideas?
Click to expand...
Click to collapse
Yeah, you gotta open the zip on your pc, modify META-INF/com/google/android/updater-script and remove the code (its in the top part) that mentions the incompatible data error. Then try flashing again.
aamir.m.ali said:
Most people that ive read about are using twrp and had no problem updating.
Click to expand...
Click to collapse
Yeah, I don't like TWRP and got CWM installed, so I can only give support about that [emoji213]
Send from OnePlus One using Tapatalk
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!