mates,
I need your help on installing JB with CW 6.0.0.7. I have a 9023 with ICS 404 stock, rooted, with busy box installed. I tried to instal the jb download from google site (9ZGgDXDi.zip) and I get the following error:
installing update...
verifing current system...
assert failed: apply_patch_check("/system/build.prop", "5a11755c3b67986b1ea8beb466955e9339e3de2c1". "db469a8330031cea064b24c5ff8d7da080a79557")
E:Error in sdcard/applic utili/9ZGgDXDi.zip
(status 7).
Installation aborted.
I had the same problem installing it via ota at the same point.
I tried to change also the CW installing the 5082 but nothing.
Someone can help me to install the JB on my nexus???
thanks
Check out this post: http://forum.xda-developers.com/showpost.php?p=28734976&postcount=970
flobin said:
Check out this post: http://forum.xda-developers.com/showpost.php?p=28734976&postcount=970
Click to expand...
Click to collapse
I restored a backup of my system where busybox was not installed and I got the same problem.
Could you be so kind to link here these three files. To be honest I'm not so expert fo find them alone.
thanks
I went to stock by doing this. http://forum.xda-developers.com/showpost.php?p=29073020&postcount=1
I didn't flash the updates in the second part #1 but you could just flash instead. I logged everything in then did this to get the 4.1.1 http://forum.xda-developers.com/showpost.php?p=29067584&postcount=2817
Go into airplane with a strong wifi signal on for this to work.
I then rerooted (2nd part #2 on)
Hope this helps.
Related
Hi everyone,
After I semi-bricked my TF last time, I followed the "nvflash back to stock" thread to restore to 8.4.4.5. The OTA didn't work (and, as it turns out, neither did Asus's SOP for flashing off the SD card), so I wanted to flash back to Asus's original 8.4.4.5 as downloaded off the Asus website to see if that would help. I went into CWM and tried to flash the Asus's original firmware. I got the following errors:
--Installing: /sdcard/US_epad-user-8.4.4.5.zip
Finding update package...
Opening update package...
Installing update...
assert failed: write_raw_image ("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-8.4.4.5.zip
(Status 7)
Installation aborted.
Any ideas on what I can do?
Thanks!
Update: I can install other roms (i.e. prime v1.6) just fine, it's just the stock rom that I have trouble with. I can live with prime, but I would still like to know the cause of the errors. Thanks!
I had the same problem, the semi-brick, and for return at stock...
I followed this and worked perfectly!
http://tabletroms.com/forums/showthread.php?1071-Asus-Transformer-NVFlash-Stock-3.1-Recovery-Roms
evilmonkey1987 said:
Hi everyone,
After I semi-bricked my TF last time, I followed the "nvflash back to stock" thread to restore to 8.4.4.5. The OTA didn't work (and, as it turns out, neither did Asus's SOP for flashing off the SD card), so I wanted to flash back to Asus's original 8.4.4.5 as downloaded off the Asus website to see if that would help. I went into CWM and tried to flash the Asus's original firmware. I got the following errors:
--Installing: /sdcard/US_epad-user-8.4.4.5.zip
Finding update package...
Opening update package...
Installing update...
assert failed: write_raw_image ("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-8.4.4.5.zip
(Status 7)
Installation aborted.
Any ideas on what I can do?
Thanks!
Click to expand...
Click to collapse
I think you might need the stock recovery to flash the stock 8.4.4.5. If you have a repackaged 8.4.4.5, then you can probably flash that via CWM. Someone would have to convert the stock rom to a flashable format. I thought I saw a thread with repackaged, flashable roms.
gee one said:
I think you might need the stock recovery to flash the stock 8.4.4.5. If you have a repackaged 8.4.4.5, then you can probably flash that via CWM. Someone would have to convert the stock rom to a flashable format. I thought I saw a thread with repackaged, flashable roms.
Click to expand...
Click to collapse
I think that would do it. I will look for that thread because I remember seeing it as well.
DLuke, thanks for your suggestion, but I would prefer not to nvflash (unless it's absolutely necessary) because I'm tired of having to reinstall my apps and losing my saved games on angry birds.
evilmonkey1987 said:
I'm tired of having to reinstall my apps and losing my saved games on angry birds.
Click to expand...
Click to collapse
Why not use Titanium Backup (or similar) to back your apps and saved games up?
Heres a link to a thread with rooted firmware you can flash via CWM. I don't know if this is what your looking for but thought I'd throw it out there
http://forum.xda-developers.com/showthread.php?t=1112527
evilmonkey1987 said:
I think that would do it. I will look for that thread because I remember seeing it as well.
DLuke, thanks for your suggestion, but I would prefer not to nvflash (unless it's absolutely necessary) because I'm tired of having to reinstall my apps and losing my saved games on angry birds.
Click to expand...
Click to collapse
There is a database i n /data/data that you can copy and restore it after flashing to keep your Angry Birds "progress"
I think it's something like data/data/com.rovio.something - your goldens eggs are saved in there.
DilloDroid said:
Heres a link to a thread with rooted firmware you can flash via CWM. I don't know if this is what your looking for but thought I'd throw it out there
http://forum.xda-developers.com/showthread.php?t=1112527
Click to expand...
Click to collapse
I believe this was the thread referred to above. I wish that it would overwrite recovery too though...go all the way back to stock, but without touching my data. The update to 8.4.4.11 doesn't work if CWM is installed.
GeeOne, thanks for the suggestion, I'll check it out!
evilmonkey1987 said:
I believe this was the thread referred to above. I wish that it would overwrite recovery too though...go all the way back to stock, but without touching my data. The update to 8.4.4.11 doesn't work if CWM is installed.
GeeOne, thanks for the suggestion, I'll check it out!
Click to expand...
Click to collapse
There is an update to 8.4.4.11 link available, too.
The issue has been resolved. I used Rom Manager to install a rom found on "Official OTA ICS 4.0.4 for GSM Nexus S (CWM Flashable version)" thread here on XDA.
I'm a noob at Android and this is my first post so please excuse any mistakes.
I am running rooted stock android 4.0.3 on Nexus S
baseband version: I9020XXKI1
kernel version: [email protected] #1
build number: IML74K
I wanted to flash the new update 4.0.4 found on:
Android police "Official Android 4.0.4 (IMM76D) Update Comes To The Nexus S - Here's How To Get It Right Now [Download]"
but when I tried to flash it on stock recovery an error message came up:
"assert failed: apply_patch_check("/system/app/Maps.apk", "f20fe23967bd8b772c595a382de9cb0637be6a60", "940268c3ffbde58b96b58e65c3ba3800ae7e1aa9")
E: Error in tmp/sideload/package.zip
(Status 7)
Installation aborted
a while back, I tried a method I read about to enable Google navigation at any location and I guess this is the cause of the problem.
I tried:
"Factory data reset" from the settings
"wipe data/factory reset" from system recovery
"wipe cache partition" from system recovery
If you have the i9020T then try this:
-Connect to WiFi (Can't be done on data)
-Go to your dial pad.
-type in: *#*#CHECKIN#*#* ---- *#*#2432546#*#*
this will force check for OTA's.
Thanks you Chubby_Skunk for the quick reply.
and I got a notification that said "checkin succeeded" but nothing happened.
Saad.AlDossary.2 said:
Thanks you Chubby_Skunk for the quick reply.
and I got a notification that said "checkin succeeded" but nothing happened.
Click to expand...
Click to collapse
then your phone hasn't revived it yet. I'm having the same issues, but I have a i9020A. So I have to wait even longer....
The ota is going to fail when it comes as well. The update script failed to verify that everything in /system is what it should be. In this case it failed at maps...
albundy2010 said:
The ota is going to fail when it comes as well. The update script failed to verify that everything in /system is what it should be. In this case it failed at maps...
Click to expand...
Click to collapse
Is that the OTA you're talking about?
im on att I9020a and I used this to update http://rootzwiki.com/_/articles/ann...4-imm76d-rom-downloads-for-nexus-devices-r590
there are also links for ns 4g
sean1984 said:
im on att I9020a and I used this to update http://rootzwiki.com/_/articles/ann...4-imm76d-rom-downloads-for-nexus-devices-r590
there are also links for ns 4g
Click to expand...
Click to collapse
It requires unlocked bootloader, root, and CMW???
I'll pass.
Try re-flashing stock 4.0.3 OTA and then flash 4.0.4 update immediately.
kong said:
Try re-flashing stock 4.0.3 OTA and then flash 4.0.4 update immediately.
Click to expand...
Click to collapse
Tried it. Same error 7 when i tried re-flashing stock 4.0.3
I tried to install 4.0.3 with no luck (same error)
I also tried Official OTA ICS 4.0.4 for GSM Nexus S (CWM Flashable version) no luck either.
how can i revert back to stock 4.0.3 (unrooted)?
Saad.AlDossary.2 said:
I tried to install 4.0.3 with no luck (same error)
I also tried Official OTA ICS 4.0.4 for GSM Nexus S (CWM Flashable version) no luck either.
how can i revert back to stock 4.0.3 (unrooted)?
Click to expand...
Click to collapse
You format the data and the cache on the stock recovery and then flash the full ROM of 4.0.3 and you'll be back to stock ROM.
Sent from my GT-P1000 using XDA
sean1984 said:
im on att I9020a and I used this to update
.............................................
there are also links for ns 4g
Click to expand...
Click to collapse
Thanks, the link you posted worked perfectly for me. I upgraded Nexus S (Wind) from CM7.1 and all the data and applications are still on the phone. I did not wipe data/cache/dalvik. Until now everything works well on ICS 4.0.4.
I've got exactly the same phone as you and the same problem with android 4.0.4 update.
I can't find a way to resolve this issue but I don't have exactly the same error message and I'd prefer to update instead of flashing.
Saad.AlDossary.2 said:
"assert failed: apply_patch_check("/system/app/Maps.apk", "f20fe23967bd8b772c595a382de9cb0637be6a60", "940268c3ffbde58b96b58e65c3ba3800ae7e1aa9")
E: Error in tmp/sideload/package.zip
(Status 7)
Installation aborted
a while back, I tried a method I read about to enable Google navigation at any location and I guess this is the cause of the problem.
Click to expand...
Click to collapse
Exact problem for me too. I tried restoring the old Maps.apk through Ti but still no luck. Any other method other than flashing.
I am trying to update my Nexus S i9020a (currently on stock 4.0.4) to stock Jelly Bean, but I'm running into some problems.
First, I got the notification that said there was an OTA update available for 4.1.1, so I started downloading it. After verification, it starting the countdown timer for restarting. When the counter reached 0, my phone did not update, but instead just told me that I was up to date.
I thought that was weird, so I used this thread to download the ota for manual installation. I rebooted into recovery and selected the update. I got the following:
Code:
Verifying current system...
assert failed: apply_patch_space(16570800)
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
I didn't mind losing my data since I have everything backed up, so I went to this page to download the official images. I followed the instructions to flash the stock bootloader, recovery, and 4.0.4 ROM.
The same thing happened. I got the OTA notification, it downloaded and nothing happened. I tried manual install, but got the Status 7 error.
I then downloaded Google's official Gingerbread image and flashed that. I got a notification for the 4.0.4 update. It installed without any problem. Once that was done, I got another notification for the 4.1.1 update. It didn't work, though. The countdown started, but the phone did not reset and it said the phone was up to date. I tried the manual update again and got another Status 7.
Sorry if this is a bit long, but I wanted to say everything I have tried. I have looked through other threads and they mention using CWM, but I would rather not use a custom recovery. I prefer to stay on stock for now.
Gregsaw said:
I am trying to update my Nexus S i9020a (currently on stock 4.0.4) to stock Jelly Bean, but I'm running into some problems.
First, I got the notification that said there was an OTA update available for 4.1.1, so I started downloading it. After verification, it starting the countdown timer for restarting. When the counter reached 0, my phone did not update, but instead just told me that I was up to date.
I thought that was weird, so I used this thread to download the ota for manual installation. I rebooted into recovery and selected the update. I got the following:
Code:
Verifying current system...
assert failed: apply_patch_space(16570800)
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
I didn't mind losing my data since I have everything backed up, so I went to this page to download the official images. I followed the instructions to flash the stock bootloader, recovery, and 4.0.4 ROM.
The same thing happened. I got the OTA notification, it downloaded and nothing happened. I tried manual install, but got the Status 7 error.
I then downloaded Google's official Gingerbread image and flashed that. I got a notification for the 4.0.4 update. It installed without any problem. Once that was done, I got another notification for the 4.1.1 update. It didn't work, though. The countdown started, but the phone did not reset and it said the phone was up to date. I tried the manual update again and got another Status 7.
Sorry if this is a bit long, but I wanted to say everything I have tried. I have looked through other threads and they mention using CWM, but I would rather not use a custom recovery. I prefer to stay on stock for now.
Click to expand...
Click to collapse
First to flash an update u need a custom recovery. if not u will get that error
second dont mind to use a custom recovery bcz after the update your recovery will be back to stock
if this helped dont forget to hit that thanks button
Cascabreu said:
First to flash an update u need a custom recovery. if not u will get that error
second dont mind to use a custom recovery bcz after the update your recovery will be back to stock
Click to expand...
Click to collapse
I didn't realize the update wrote over the recovery. Thanks
Gregsaw said:
I didn't realize the update wrote over the recovery. Thanks
Click to expand...
Click to collapse
on any stock rom, at each boot it will overwrite the recovery
So I could use fastboot/adb to install the custom recovery, then install the zip from sd and the phone would be exactly the same as it would be if I were to receive the update notification directly and installed it that way? Should I wipe cache and dalvik in this scenario?
TheIowaKid said:
So I could use fastboot/adb to install the custom recovery, then install the zip from sd and the phone would be exactly the same as it would be if I were to receive the update notification directly and installed it that way? Should I wipe cache and dalvik in this scenario?
Click to expand...
Click to collapse
yes it's exactly the same, if u want u can wipe cache and dalvik before flashing (that's even recomended from some devs )
I read through the FAQ and tried searching but didn't see a solution.
I have a VZW M8 that is Rooted, S-Off, Clockwork Recovery, Factory ROM, (Installed Standard and Extreme Power Saver Mode, and unlocked VZW WiFi Hotspot.)
I got a notification today that the 1.55.605.2 update is available for the phone but when I attempted to install it the install failed.
Ran it again to get the exact error messages.
On install it takes me to CWM Recovery and asks if I want to install the untrusted zip, (Shows failed to verify whole file signature, then signature verification failed.)
If I tell it to install the untrusted zip I get the following:
file_getprop: Failed to stat "/system/build.prop" : No such file or directory
E: Error in /cache/fumo/OTAPkg.zip (Status 7)
Installation aborted
YELLOW_STL_MACH said:
I read through the FAQ and tried searching but didn't see a solution.
I have a VZW M8 that is Rooted, S-Off, Clockwork Recovery, Factory ROM, (Installed Standard and Extreme Power Saver Mode, and unlocked VZW WiFi Hotspot.)
I got a notification today that the 1.55.605.2 update is available for the phone but when I attempted to install it the install failed.
Click to expand...
Click to collapse
If you have a custom recovery installed it won't update.
Sent from my SCH-I535 using Tapatalk
re install the stock recovery or wait a few hours for the devs to put flashable versions.
YELLOW_STL_MACH said:
I read through the FAQ and tried searching but didn't see a solution.
I have a VZW M8 that is Rooted, S-Off, Clockwork Recovery, Factory ROM, (Installed Standard and Extreme Power Saver Mode, and unlocked VZW WiFi Hotspot.)
I got a notification today that the 1.55.605.2 update is available for the phone but when I attempted to install it the install failed.
Click to expand...
Click to collapse
I would recommend this: http://forum.xda-developers.com/showthread.php?t=2723159
It's always best to wait for someone to release the version(s) of Firmware that will work for S-Off/Rooted/Custom ROMs. Since I'm running ViperOneM8, I flashed the No Boot firmware and have no issues. BTW, my battery life is absolutely AMAZING.
FWIW, here's the patch download on Verizon's own servers: https://pvzwmdmcdn.vzw.motive.com/firmware/HTC6525LVW_1.55.605.2-1.12.605.11_R3.bin
@YELLOW_STL_MACH curious: what did you end up doing? I'm in the same boat (Orig Factory stock ROM, rooted, S-Off, etc.) but never bothered taking the OTA (although it keeps bugging me). just wondering what you did and if it was worth the trouble.
I am running an Asus TF101 B90 tablet. I have just rooted and installed KatKiss 4.4.4_036. I am using ClockworkMod v 3.2.0.1 roach2010-tf101-r1 for recovery. This appears to work fine. I have tried the defined step,s both before and after flashing the 4.4.4 ROM, to flash the 5.1 ROM without success. I have tried this with both a full wipe and without. The results are always the same. After it starts the install the system gives me the following error messages:
Set_metadata_recursive: some changes failed
E:Error in /sdcard/KatKiss-5.1_030.zip
(Status 7)
Installation aborted
I have the same issue with KatKiss-5.1_030c.zip. Yesterday was the first time I rooted an android device. Any recommendations on what and how I need to change things so I can move to Lollipop? Thanks.
John
jdwbmc said:
I am running an Asus TF101 B90 tablet. I have just rooted and installed KatKiss 4.4.4_036. I am using ClockworkMod v 3.2.0.1 roach2010-tf101-r1 for recovery. This appears to work fine. I have tried the defined step,s both before and after flashing the 4.4.4 ROM, to flash the 5.1 ROM without success. I have tried this with both a full wipe and without. The results are always the same. After it starts the install the system gives me the following error messages:
Set_metadata_recursive: some changes failed
E:Error in /sdcard/KatKiss-5.1_030.zip
(Status 7)
Installation aborted
I have the same issue with KatKiss-5.1_030c.zip. Yesterday was the first time I rooted an android device. Any recommendations on what and how I need to change things so I can move to Lollipop? Thanks.
John
Click to expand...
Click to collapse
You need to install a recent recovery
See the link in the 1st post of the rom installation instructions
Thanks!
timduru said:
You need to install a recent recovery
See the link in the 1st post of the rom installation instructions
Click to expand...
Click to collapse
Tim,
First of all thanks so much for your work keeping the ASUS TF101 alive and working! It means a great deal. I did flash the TWRP 2.8.1 recovery system. That worked fine. I was then able to flash the KatKiss-5.1_030c ROM. I am now running Lollipop 5.1.1! Two questions. I ran Root Checker Basic. It can no longer validate that I am rooted, though it could when I ran 4.4.4. Is this to be expected or is there something I need to fix? Secondly, Lollipop seems a bit slower than 4.4.4. Is this to be expected or is there something I need to change to up performance? Thanks.
John