Hey there,
just tried to flash this ROM to my Ace.
I updated CWM to the required 6.0.5.3_1, wiped data/factory reset and formatted /system.
Everytime I try to install the .zip, I get the "installation aborted" message. No error code, no more information.
Would be awesome to get some help, cause i cant find this problem in the forum, only some with error codes.
I used an earlier version of CM on this device before trying to flash it now.
Greetings
Installed a non-modded version of CM now, which worked fine.
Getting the status 0 error now when installing the original CM gapps. Any solutions?
lolmachine said:
Installed a non-modded version of CM now, which worked fine.
Getting the status 0 error now when installing the original CM gapps. Any solutions?
Click to expand...
Click to collapse
1. Are you using a CM11 compatible recovery?
2. Are you the complete files downloaded? or have you an unstabe internet connection?
Try to donwload the files again
Related
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!
Hello, I was on the latest stable,
I tried installing the latest nightly - 19 using the cm updater. It said something about data has another partion please try to install again to confirm wiping /data
so i selected the zip again, it seem to install just fine but I cant get past the cyanogenmod logo.
I wiped both cache and installed it again but same problem. Any tips what to do next?
I think you mean Nightly of CM 10.2 ...
Use the newest nightly ,in one Nightly there was an error about installation.
The warning is because with the nightly beginning from 20130816 the partitioning layout have to be changed because of Out of space on /system...so the massage is only that you know it and you have to confirm it a second time ...
So test a newer nightly an it should work!!!
Here is the link to the thread of CM 10.2 ....http://forum.xda-developers.com/showthread.php?t=2385178 there are some additional infos ...
Let me no if it works ...
unrealbe said:
Hello, I was on the latest stable,
I tried installing the latest nightly - 19 using the cm updater. It said something about data has another partion please try to install again to confirm wiping /data
so i selected the zip again, it seem to install just fine but I cant get past the cyanogenmod logo.
I wiped both cache and installed it again but same problem. Any tips what to do next?
Click to expand...
Click to collapse
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
Hi,
I get error when trying to install nightly cm 11 on my i9000.
I currently have cm 10.2 with CWM on it.
I enter recovery
Installing the ZIP of the nightly rom.
And I get error:
error can't open /sdcard/******* (bad)
Any idea?
shakta said:
Hi,
I get error when trying to install nightly cm 11 on my i9000.
I currently have cm 10.2 with CWM on it.
I enter recovery
Installing the ZIP of the nightly rom.
And I get error:
error can't open /sdcard/******* (bad)
Any idea?
Click to expand...
Click to collapse
Mate, I never had any problem with installation of cm11 on my i9000.
Make sure that you dont have the corrupted zip and try redownloading and reflashing it on 10.2 after wipe.
Have goodluck
shakta said:
Hi,
I get error when trying to install nightly cm 11 on my i9000.
I currently have cm 10.2 with CWM on it.
I enter recovery
Installing the ZIP of the nightly rom.
And I get error:
error can't open /sdcard/******* (bad)
Any idea?
Click to expand...
Click to collapse
If it says 'Status 7' underneath, it means the current version of clockwork is incompatible. Try flashing a kitkat kernel first, reboot recovery, then flash cm11. I had an error that I seem to remember looked similar
Try to do a clean install.
Delete everting (data, datadata, system,etc) and them make the 3 wipe's.
It's work for me.
Hello
today before I install CM 12.1 on my XT1072 I clicked on wipe in TWRP then advanced wipe then I selected
* Dalvik cache
* Data
* Cashe
* System
I tried to install CM 12.1 after that but it gave me Error
now I don't have any os installed on my phone
So please if any one know a full rom link or any way to install the os again please help me with it
thank you very much
Hassan Qandil said:
Hello
today before I install CM 12.1 on my XT1072 I clicked on wipe in TWRP then advanced wipe then I selected
* Dalvik cache
* Data
* Cashe
* System
I tried to install CM 12.1 after that but it gave me Error
now I don't have any os installed on my phone
So please if any one know a full rom link or any way to install the os again please help me with it
thank you very much
Click to expand...
Click to collapse
Download from Cyanogenmod site the last nightly of CM for THEA (http://download.cyanogenmod.org/?device=thea)
Put it in the micro SD card of your phone (using another phone or the card reader of your PC if it has one)
In TWRP install the ROM from the external SD (and Gapps if you want to use them)
In this situation I think that the above method is the only one, but wait for other answers, it could be that someone can show you better ways.
when I tried to install CM 12.1 the same way you said .. the phone gave me a failure message
Hassan Qandil said:
when I tried to install CM 12.1 the same way you said .. the phone gave me a failure message
Click to expand...
Click to collapse
Can you report that message?
The first time you install a ROM after a system wipe (as you described), TWRP gives an error message, but, after system reboot (by TWRP function), the phone starts normally and CM starts the standard update procedure
I am not sure what do you mean exactly but the installation of cm 12.1 didn't even start
gave me error message .. I think that cm rom need stock rom to install over it
now I just want to install the official firmware .. but I didn't found any rom img files yet
I thank every one can help me ... it's my only phone :crying:
Hassan Qandil said:
I am not sure what do you mean exactly but the installation of cm 12.1 didn't even start
gave me error message .. I think that cm rom need stock rom to install over it
now I just want to install the official firmware .. but I didn't found any rom img files yet
I thank every one can help me ... it's my only phone :crying:
Click to expand...
Click to collapse
Mmh, it's a strange situation. I wiped system memory about three/four time on my phone (and also on my friend's phone) and the procedure I described to you worked for me every time. But the error message, in my case, was after CM installation and not before, as in your case.
Did you check the MD5Sum (or SHA) of the downloaded file to make sure it was not corrupted? The error you received can be related to a corrupted file...
Lastly take a look at this tool:
http://forum.xda-developers.com/mot...dows-tool-moto-g-2015-xt1072-restore-t3124915
I've never tried it but it seems to be suited to your case.