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
Related
Im running Amon Ra 1.6.2. I am successfully running cyan stable and also was able to run Modaco Custom rom r13. Ive tried to run all three new versions of r21 including md5. All installation aborted (bad). PLEASE HELP ME. DESIRE ROM IS THE REASON I ROOTED, but still use cyan for dailey use..
Try wiping?
wiped everything in the recovery manager. data/factory cache sd ext batter and rotate. all three still abort (bad) Am i using wrong recovery version? Do i need to use earlier alpha? Ive been trying to figure this out for 3 days!
Corrupt file..? dl a new or again.!
thnx keldaug your exactly right. i swear i downloaded them like 5 times. UGH FINNALY! THANKS!!
I was on Darkys ROM for some months without any flashing problems. Now i wanted to change from Darkys ROM 10.1 (Gingerbread 2.3.4) to Galnet MIUI. I had to downgrade to Froyo and then install the CWM zip in CWM. This was NOT succesful. It always says "Installation aborted (Status 7)". Then i tried to install CyanogenMod 7.1. Upgraded to Gingerbread Stock with CWM 3 and when i first flashed it via ODIN the phone first booted in the standart Android CWM display (dont know the name sry). The phone automatically formated cache etc. but then it showed me 2 times "/efs is not mounted". I was able to boot and to open CWM but ALWAYS when i want to install ANY CWM ROM it shows me the message with Status 7 ...
EDIT: The message when i try to install a zip via CWM:
--INSTALLING: SDCARD: update-cm-7.1.0-GalaxyS-signed.zip
Finding update package
Opening update package
Installing update
Checking state of BML/MTD
assert failed: run_program("tmp/updater.sh) == 0
E:Error in /mnt/sdcard/update-cm-7.1.0-GalaxyS-signed.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
How can i mount /efs again and make CWM ROM Flashing able again?
Thank you.
I am not a dev, but I suggest you do a fresh ODIN flash to stock rom or this SIMPLY HONEY ( its got odin version & hence very easy to install ) rom.
I already flashed several (stock) roms... still not working
The first thing you every do before flashing a rom is a nandroid backup.... use this to recover...
I hope to hear oh thanks i didn't remember about that, lol. But i do not expect it...
Do you have any backups, of the /efs maybe? If you do then find out how to put that back on..
An option would be to use adb to try fix it, first try the obvious and try mount the ef, if that doesn't work then tell me what files you have in the efs... and we'll try help you from there.
If you don't know hoe to use adb there is a pinned thread in the general forum, and I have made a there is a basic tutorial in a number of places either search here or google
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
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!
So I posted a help thing about EFS a while back and didnt get to much help with that but i managed to figure things out. Now however
ive got myself into another predicament i cant seem to get out of.
So, from the start, i have a galaxy s3 (GT i-9305T) it was rooted, i still had the stock rom, but was running the beoffla kernal.
The idea was to download and install "JustArchi I9300XXUGML2 stock, deodexed and all the rest" then start finding
some nice themes. Ive got philz_touch_6.07.9-i9305.tar installed for my recovery.
This is where the trouble starts...
So first off i wipe the cache and the davik cache, go to install the rom then i get this: (ill go from installing update)
assert failed: write_raw_image (" /tmp/boot.img" , " /dev/block/mmcblk0p5" )
E: Error in /storage/sdcard1/Just archi........zip
(Status 7)
Installation aborted
Now i looked up a whole heap of pages to see if i could sort it out myself and i tried a few different things,
none of which have prevailed. First i tried to reflash an insecure boot image then try again, nup. I tried to
flash back to stock recovery and re format (No errors) then back to custom. Mounted /data and /system
and re formatted which worked with no error, still same error when flashing rom though. Also tried flashing
with different custom recovery, no luck there either.
There were a few other things i tried but i cant really remember what i did because
this has been a problem for a while now. Some of the pages i looked over for
information were:
http://www.droidforums.net/forum/android-hacks-help/26658-assert-failed-write_raw_image-tmp-boot-img.html
http://forum.xda-developers.com/showthread.php?t=1045887
And this is the one im on at the moment, im currently downloading a stock rom from sammobile to try flash.
http://forum.xda-developers.com/galaxy-s3/help-i9305/i9305t-10-2-upgrade-boot-stops-unable-t2406422
"UPDATE"
Finished downloading the stock rom, tried to install with philz recovery and got this:
Installing: /storage/sdcard1/I9305TDVBME2_I9305TTELBME1_TEL (STOCK).zip
Finding update package...
Opening update package....
Installing update...
Installation aborted.
And thats it, no kind of specific error codes or anything.
Thanks in advance to anyone who can help me out,
really stuck on this one.
IIEsoticoII said:
So I posted a help thing about EFS a while back and didnt get to much help with that but i managed to figure things out. Now however
ive got myself into another predicament i cant seem to get out of.
So, from the start, i have a galaxy s3 (GT i-9305T) it was rooted, i still had the stock rom, but was running the beoffla kernal.
The idea was to download and install "JustArchi I9300XXUGML2 stock, deodexed and all the rest" then start finding
some nice themes. Ive got philz_touch_6.07.9-i9305.tar installed for my recovery.
This is where the trouble starts...
So first off i wipe the cache and the davik cache, go to install the rom then i get this: (ill go from installing update)
assert failed: write_raw_image (" /tmp/boot.img" , " /dev/block/mmcblk0p5" )
E: Error in /storage/sdcard1/Just archi........zip
(Status 7)
Installation aborted
Now i looked up a whole heap of pages to see if i could sort it out myself and i tried a few different things,
none of which have prevailed. First i tried to reflash an insecure boot image then try again, nup. I tried to
flash back to stock recovery and re format (No errors) then back to custom. Mounted /data and /system
and re formatted which worked with no error, still same error when flashing rom though. Also tried flashing
with different custom recovery, no luck there either.
There were a few other things i tried but i cant really remember what i did because
this has been a problem for a while now. Some of the pages i looked over for
information were:
http://www.droidforums.net/forum/android-hacks-help/26658-assert-failed-write_raw_image-tmp-boot-img.html
http://forum.xda-developers.com/showthread.php?t=1045887
And this is the one im on at the moment, im currently downloading a stock rom from sammobile to try flash.
http://forum.xda-developers.com/galaxy-s3/help-i9305/i9305t-10-2-upgrade-boot-stops-unable-t2406422
"UPDATE"
Finished downloading the stock rom, tried to install with philz recovery and got this:
Installing: /storage/sdcard1/I9305TDVBME2_I9305TTELBME1_TEL (STOCK).zip
Finding update package...
Opening update package....
Installing update...
Installation aborted.
And thats it, no kind of specific error codes or anything.
Thanks in advance to anyone who can help me out,
really stuck on this one.
Click to expand...
Click to collapse
Can anybody at all shed some light on my situation,
or at least a place for me to start learning myself...
Hi.
If you downloaded the stock ROM from sammy mobile are these not meant to be installed via Odin?
There are a few post if you search for some of the pre rooted stock ROMs that you can flash with odin.
I would start from there.
Sent from my GT-I9305 using xda app-developers app
johnnyblaze1977 said:
Hi.
If you downloaded the stock ROM from sammy mobile are these not meant to be installed via Odin?
There are a few post if you search for some of the pre rooted stock ROMs that you can flash with odin.
I would start from there.
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
The roms i downloaded from samsmobile were in .zip files, which im pretty
sure has to be flashed with one of the custom recoveries.
Thanks though
at first seems you tried to flash rom designed for i9300
then, you downloaded an ODIN image and you have to flash it by ODIN, no way you'd flash it over any recovery
to be more specific:
unzip the file I9305TDVBME2_I9305TTELBME1_TEL (STOCK).zip you downloaded, you should get a huge file with extension of .md5 or .tar
read in the forums how to use ODIN to flash firmware
adamuadamu said:
at first seems you tried to flash rom designed for i9300
then, you downloaded an ODIN image and you have to flash it by ODIN, no way you'd flash it over any recovery
to be more specific:
unzip the file I9305TDVBME2_I9305TTELBME1_TEL (STOCK).zip you downloaded, you should get a huge file with extension of .md5 or .tar
read in the forums how to use ODIN to flash firmware
Click to expand...
Click to collapse
Yes ive just done this now and flashed the stock rom with odin
and i think everything has gone well (im not sure as my screen is
water damaged but i did here boot audio only once) so im
letting my phone sit in a bag of rice in pieces for the night
and am going to check things out tommorrow.