I've rooted and unlocked my N1 and flashed it several times with custom Roms. I recently went from CM7 RC1 to a rooted stock 2.3.3, for which I had installed HBOOT. Now I am only able to perform a nandroid restore to change the roms and am unable to install CM7 RC2 or even to reinstall CM7 RC1 with which I was previously running. The error I see is:
Installing update . . . .
assert failed: getprop("ro.product.device") =="
one" || getprop("ro.buiE:unknown command [ld.product")]
E: Error in /sdcard/update.zio
(Status 7)
Installation aborted.
I've looked through Cyanogen and XDA forums but I haven't seen a direct response to this particular issue. I've tried Wiping and wiping the davlik cache, and I've flashed Clockwork recovery and RA recovery via rom manager. I've tried 4 separate roms and get the same error, and these are roms I was able to use previously.
Any help or even a push in the right direction would be very much appreciated, as I've essentially hit a wall. Please excuse the noobish picture of my N1 screen , I don't know how to take screen shots.
status 7 error
i have the same problem. solution plz
So this happened only after flashing the hboot right?
Did you try wipe/data factory from the recovery menu?
Looks like a problem in build.prop of the ROM currently on device.
Solution: check build.prop for the line that the installation scripts fails at, see what it's expecting and what's there, and change accordingly. You can do all that by ADB shell in recovery.
fakey97 said:
I've rooted and unlocked my N1 and flashed it several times with custom Roms. I recently went from CM7 RC1 to a rooted stock 2.3.3, for which I had installed HBOOT. Now I am only able to perform a nandroid restore to change the roms and am unable to install CM7 RC2 or even to reinstall CM7 RC1 with which I was previously running. The error I see is:
Installing update . . . .
assert failed: getprop("ro.product.device") =="
one" || getprop("ro.buiE:unknown command [ld.product")]
E: Error in /sdcard/update.zio
(Status 7)
Installation aborted.
I've looked through Cyanogen and XDA forums but I haven't seen a direct response to this particular issue. I've tried Wiping and wiping the davlik cache, and I've flashed Clockwork recovery and RA recovery via rom manager. I've tried 4 separate roms and get the same error, and these are roms I was able to use previously.
Any help or even a push in the right direction would be very much appreciated, as I've essentially hit a wall. Please excuse the noobish picture of my N1 screen , I don't know how to take screen shots.
Click to expand...
Click to collapse
From the screen shot, i think you are trying to flash an NS ROM!! That's the reason it fails
Sent from my icy cool nexus
Hello friends.
I have an original VZW droid.
I rooted with EasyRoot many moons ago, then manually updated the stock 2.1 image to 2.2 FRG01B.
Ever since then, when i try to flash a new rom (or even the OTA update.zip to FRG02), i always get the Fail triangle with the exclamation point.
My latest go-round has been with Clockword Mod recovery.
i can successfully flash the recovery image, but when i try install a CM7 signed rom, i get the same fail triangle with a 'Status 7' message..
I have wiped data/cache/facory reset all several times.
in fact, as we speak, i just tried to apply to OTA update, and the error is ->
e:error in /cache/688e.....signed-voles-FRG22D-from-FRG01B.zip.
(status 7)
Installation aborted.
i've just resigned myself to be stuck for months now, but i have the flash bug again since i was able to successfully get CM7 on my nook color and do netflix.
is there any advice ?
thanks!
I've been trying to flash aokp_vibrantmtd_build-25 and\or AOKP_build23_i9000_beta2.1-signed with no success I boot into CWM and select the zip it starts then I get the Asset failed: ro.product.device == GT-I9000M ect and it ends with (Status 7)... Am I using the wrong CWM v2.5.1.0? To be sure I flashed the latest Kernel speedmod-kernel-k16-11 via Odin and still not working. The old ROM I had wont launch any longer and its not hosted so I'd be nice to get the AOKP rom running. Any help would be much appreciated!
A: Wiped everything and formatted everything then flashed another ISC ROM and updated kernel to Semaphore_ICS_0.8.1 CWM updated to v5.5.0.4 re-flashed beta 3 and it works flawlessly now!
Btw for future reference if you know what device you have and know the rom is compatible (hard right?). You can edit out assert statement in install script.
Sent from my SGH-T959 using XDA App
I tried installing AOKP 27 but when flashing this comes up.
-- Installing: /sdcard/aokp_galaxysmtd_build-27.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "galaxys" || getprop("ro.build.product") == "galaxys" || ...........
............
..... (many such things) (with galaxys replaced by galaxysmtd, & in other places, GT-I9000)
(then):
E;Error in /sdcard/aokp_galaxysmtd_build-27.zip
(Status 7)
Installation aborted.
or the phone will just reboot and try again etc.
How do I either go back or flash the rom without it failing?
Just try to flash any BaseRom trough Odin and then try again to flash AOKP Build 27
trough recovery...!
Just do a battery pull and reboot into recovery and re-flash the rom
Had the same problem! Tried a few times , allways stuck on bootloop, and no more CWM!
For me it worked this way:
Flashed stock JVU with repartition, CM9 throw CWM, got bootloop reboot into recovery flashed CM9 again, them flashed AOKP. Reboot, and no problem
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!