Okay, where do I begin? The PSfreedom was released for droid and a friend said I can use one of her old droids which was 2.1update1. So in my haste to flash this thing I used EasyRoot, got it rooted (of course made a nandroid backup at least), installed cyanogen 6 (made a backup of this using clockwork recovery), installed the wrong kernel, then was stuck at a loop screen. Well I kept trying and trying to boot it to Clockworkmod Recovery and nothing was working until about the time I gave up and set it down...and WHAM! Clockworkmod Reovery! So I went to nandroid, restore and clicked on my clockwork cyanogen backup. And thus I was stuck on an endless loop of the Droid eye and the Droid logo. I assumed something went wrong and tried booting into clockwork recovery to no avail. Then it finally let me into the normal recovery and I decided I should find a way to start from scratch. Now I wiped EVERYTHING and still I have the endless loop, PLUS it wont let me update to another official firmware via update.zip.
This is the error it gives me:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/Phone.odex", "e619ca7905cd905cd9eeb429c96601b728667b30b94b7", "5d22b967c190356983966fa1f7901aeebdffaaaf")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Can anyone help me figure out what the bejeezus is wrong?
i would suggest u check to see if there is an option to "allow install of update.zip" and click on it before you do the update. i know sprecovery has it
if all else fails, flash the 2.1 sbf file and start over, its really easy
I just got my replacement phone thru HTC and I was returning my current N1 to stock. I had CM6 installed and I rooted my phone without Unlocking it. My plan was to reinstall the stock recovery and go back to a stock unrooted Froyo.
A bunch of stuff happened and where I'm stuck at now is that I have a stock recovery. And my phone has an incomplete OS. (When it loads it just Force Closes everything.)
The last thing i flashed before the OS stopped working was: Update-Passion-Full-FRF91.zip
I tried flashing in fastboot. idk what else to do?
I'd like to either have this go back to stock like i wanted or at least get back to having RA Recovery so i can recover my nand
Please get back to me as soon as possible.
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_%26_Tutorials#Unroot_.2F_Restore_your_Nexus
I got mine to stock and successfully returned it to HTC for a swap without any problem using fastboot from the link above. I didn't flash it to stock 2.2 I only flashed the room that it came with from factory (really old one ERD79) and HTC didn't care.
yeah i tried doing that first. but i kept getting failed verification errors
just flash RA recovery via fastboot ( if you can, I dont't know if it will let you since you don't have bootloader unlocked)
Or try using the PASSIMG.ZIP method
Please help soon. i have to send this phone back to HTC
IMGPASS.zip did not work. Main version is older! error
it wont let me go into stock recovery and flash any signed ROMS. It starts to open them up and then i get an error.
Verifying update package...
Installing update...
assert failed: !less_than_int (1277421628), getprop(ro.build.date.utc"))
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Phone Fixed itself??
THe phone fixed itself. It finally rebooted and no force closes.
No idea what i did that fixed it.
but i just accept that it happened.
Now to mess with my new phone :/
Hello!
I have a Samsung Galaxy S Captivate previously rooted over a year ago. I was mostly using CyanogenMod for a while, and some time ago, I decided to try out some random ROM (can't remember the name, but it was an unofficial port of ICS).
It had some issues and bugs, so I decided to switch back to CyanogenMod. I've tried installing CyanogenMod 7.2, 9.0 and 10.0
Everytime, I get the following error message:
Code:
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "captivate" ||
getprop.("ro.build.product") || ... (and so on)
E:Error in /sdcard/#whateverpackage#.zip
Status 7
Installation aborted.
*Where "whateverpackage" is the zip/ROM I am trying to install.
Things I attempted to no avail:
1. Toggling asserts. I get the same error.
2. Reflashing recovery-clockwork-2.5.1.2, but I get the same type of error.
3. Installed USB Drivers for Samsung, and attempted to run Odin3 One-Click Downloader (I897UCJF6-final-OCD-REV0.exe), but it isn't responding it seems.
I'm thinking of trying to install ADB and see if I can get the device to properly go into "download mode" and see if Odin responds.
This may be important: When I boot in recovery, the top of my screen shows "CWM-based Recovery v5.5.0.2"
So if anyone knows a straightforward fix to this, or can at least give me rough steps to try/follow, I would greatly appreciate your help.
Thanks for taking the time to read this!
You could have quickly found an answer if you searched "status 7" or "assert failed." It simply means your phone is identifying as a different device because of the ROM you flashed. You can get around this by flashing a kernel appropriate for whatever you're trying to install, so Devil or Semaphore will do. From there, reboot recovery and install the ROM.
korockinout13 said:
You could have quickly found an answer if you searched "status 7" or "assert failed." It simply means your phone is identifying as a different device because of the ROM you flashed. You can get around this by flashing a kernel appropriate for whatever you're trying to install, so Devil or Semaphore will do. From there, reboot recovery and install the ROM.
Click to expand...
Click to collapse
I did look up assert failed, but I couldn't get a clear answer.
I didn't occur to me to look up "status 7"; just seemed like a very cryptic error code.
Thank you for your advice nonetheless. I'll update if the error persists.
Semaphore & CyanogenMod
So, I flashed Semaphore 2.8.0 and then attempted to install CyanogenMod 10 (Android 4.1.2, I think).
Got Status 0.
Tried reflashing Semaphore 2.8.0, and 1.2.6. No progress.
Any recommendations?
I tried to flash CyanogenMod 9 on Semaphore 1.2.6 and got Status 7.
Thanks.
Headless_One said:
So, I flashed Semaphore 2.8.0 and then attempted to install CyanogenMod 10 (Android 4.1.2, I think).
Got Status 0.
Tried reflashing Semaphore 2.8.0, and 1.2.6. No progress.
Any recommendations?
I tried to flash CyanogenMod 9 on Semaphore 1.2.6 and got Status 7.
Thanks.
Click to expand...
Click to collapse
If you would read a bit before doing the flashing you would know that status 0 is from rebuilding the partition. You simply need to flash CM10.1 twice. So it goes like this: Flash CM10.1, reboot recovery, flash CM10.1.
BWolf56 said:
If you would read a bit before doing the flashing you would know that status 0 is from rebuilding the partition. You simply need to flash CM10.1 twice. So it goes like this: Flash CM10.1, reboot recovery, flash CM10.1.
Click to expand...
Click to collapse
I do look up the error. Just no one actually mentioning that until your post.
Thank you for your advice.
I flashed it 3 times (rebooting each time) and I always get Status 0.
More explicitly:
Code:
-- Installing: /sdcard/cm-10.0.0-captivatemtd.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/cm-10.0.0-captivatemtd.zip
(Status 0)
Installation aborted.
Side note: I'm on Semaphore 2.8.0 and I used Heimdell to flash it (through Ubuntu).
Any additional thoughts?
Headless_One said:
I do look up the error. Just no one actually mentioning that until your post.
Thank you for your advice.
I flashed it 3 times (rebooting each time) and I always get Status 0.
More explicitly:
Code:
-- Installing: /sdcard/cm-10.0.0-captivatemtd.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/cm-10.0.0-captivatemtd.zip
(Status 0)
Installation aborted.
Side note: I'm on Semaphore 2.8.0 and I used Heimdell to flash it (through Ubuntu).
Any additional thoughts?
Click to expand...
Click to collapse
Tried simply booting up?
If that doesn't work, reflash without rebooting recovery.
BWolf56 said:
Tried simply booting up?
If that doesn't work, reflash without rebooting recovery.
Click to expand...
Click to collapse
I tried rebooting the device, but, after shortly showing "At&t", it goes straight to the Recovery screen.
I tried installing CM10 again, but same error.
Just reflashed Semaphore. It always gets stuck on At&t after flashing (for several minutes). Is that normal?
So I've been removing the battery, and putting it back in. Then it goes straight to 'Semaphore CWM Recovery v6.0.2.0'.
My steps from there:
Attempted to install CM10. Status 0 error. Turned phone off.
Rebooted straight to CWM-Based Recovery v6.0.1.5.
Tried installing CM10 from there. Status 0 error.
Rebooted. Right back to Recovery v6.0.1.5.
Tried installing CM10 again. Status 0 error
Tried installing CM9. Phone rebooted midway and got stuck on 'At&t' screen.
Rebooted using 3-key button combo (to get to recovery screen).
Went to Recovery v6.0.1.1. (What the hell is going on?)
Tried installing CM9. SUCCESSFUL. Also installed gapps for ICS while at it.
Booted to CM9 correctly.
Rebooted to Recovery and it was still Recovery v6.0.1.1.
Rebooted back to CM9 properly.
Edit:
Rebooted to Recovery. Updated to CM10.
Noticed that Recovery version changed back to v6.0.1.5.
CM10 seems to be working properly.
Anyone knows why I am getting 3 different Recovery versions?
Note: Sorry for the somewhat long post. I just figured I should tell you everything I am doing step-by-step.
Headless_One said:
I tried rebooting the device, but, after shortly showing "At&t", it goes straight to the Recovery screen.
I tried installing CM10 again, but same error.
Just reflashed Semaphore. It always gets stuck on At&t after flashing (for several minutes). Is that normal?
So I've been removing the battery, and putting it back in. Then it goes straight to 'Semaphore CWM Recovery v6.0.2.0'.
My steps from there:
Attempted to install CM10. Status 0 error. Turned phone off.
Rebooted straight to CWM-Based Recovery v6.0.1.5.
Tried installing CM10 from there. Status 0 error.
Rebooted. Right back to Recovery v6.0.1.5.
Tried installing CM10 again. Status 0 error
Tried installing CM9. Phone rebooted midway and got stuck on 'At&t' screen.
Rebooted using 3-key button combo (to get to recovery screen).
Went to Recovery v6.0.1.1. (What the hell is going on?)
Tried installing CM9. SUCCESSFUL. Also installed gapps for ICS while at it.
Booted to CM9 correctly.
Rebooted to Recovery and it was still Recovery v6.0.1.1.
Rebooted back to CM9 properly.
Anyone knows why I am getting 3 different Recovery versions?
Note: Sorry for the somewhat long post. I just figured I should tell you everything I am doing step-by-step.
Click to expand...
Click to collapse
Actually that's great details, thanks!
Have you tried flashing CM10 from CM9? It will still have to rebuild the partition so 2 flashes will be needed.
BWolf56 said:
Actually that's great details, thanks!
Have you tried flashing CM10 from CM9? It will still have to rebuild the partition so 2 flashes will be needed.
Click to expand...
Click to collapse
Yes sir, I just did that. It works
Thanks for your help.
Just wanted to thank you both for this thread. Totally helped me upgrade my Cappy to CM10.1 today. Thanks!
hey guys,
I am noob to rooting. Recently rooted my nexus s GT-I9020 and installed clockworkmod recovery version 5. I tried installing CM10.1 Rom for nexus s. Installed rom manager from store and tried flashing recovery there I got this error stating 'An error occured while flashing your recovery'. Tried many times, replaced version 3 to version 5 of clockworkmod recovery. Dont have any idea what to do. Kindly help me to sort this out please!!!!.
use this recovery image
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.2.5-crespo.img
and get the latest cm nightly from here
http://download.cyanogenmod.com/?device=crespo
these are both from the official sources, so you know they will flash as they should
Hi Guys,
Scene:
Last week I had a rooted phone that could install any custom ROM, Then all of a sudden I could no longer install a custom ROM, I would get a boot loop. So today I un- rooted my phone, then re-rootes however, o now get an status 7 error on any custom ROM. I can however backup my old rooted ROM.
Any idea what has gone wrong that I cannot install a custom ROM, or how I can install a custom ROM?
Any help would be greatly appreciated.
Here is the full error log when installing any ROM:
Finding update package
Opening update package
Installing package
Symlink: some symlinks failed
E:error in /external_sd/ (the ROM name)
(Status 7)
Installation aborted
????:crying:
Try this http://highonandroid.com/android-roms/how-to-fix-status-7-error-with-cwm-recovery-on-rooted-android/
totex71 said:
Try this http://highonandroid.com/android-roms/how-to-fix-status-7-error-with-cwm-recovery-on-rooted-android/
Click to expand...
Click to collapse
Thanks I have tried this but it doesnt work. I get a status 6 error.
OK so i have tried installing with TWRP which works however, I get a bootloop with any ROM I install. I guess its my phone. I will stick to the stock retail en GB rom