Develop Bugs

Issue with CWM and Flashing ROMs

Ok, I can successfully get into CWM, but I can't flash either the OMGB or OMFGB ROMS. I always wipe data/dalvik. It doesn't even try to install, like it can't find the .zip file or something. The funny thing is, I successfully flashed a ROM using the ROM Manager application by downloading CM7 and installing from ROM Manager.
I have tried placing the .zip on the root of the SD card and also in the "CWM download" folder without luck.
Basically, I can flash a ROM with ROM Manager, but not manually using CWM?

you are supposed to find the zip yourself through CWM it will not find it for you
reboot recovery(CWM), wipe data, install zip from sdcard, find .zip in contained folder
if you cannot find it is not .zip format

I am doing exactly as you say. Wipe data/dalvik/cache partition. Flash zip and this is the error I get:
Assert failed: getprop("ro.product.device") == "inc" || getprop("ro.build.product") == "inc"
|| getprop("ro.product.board") == "inc"
E: Error in /sdcard/OMFGB_inc-1.3.1_nightly-08-25.zip
(status7)
Installation aborted.
Anyone ever seen this?

i've had the exact same issue using amon ra style recovery I installed the newest cwm and it flashed no problem. not sure what the problem wad
Sent from my ADR6350 using xda premium

Rossco_Pee said:
I am doing exactly as you say. Wipe data/dalvik/cache partition. Flash zip and this is the error I get:
Assert failed: getprop("ro.product.device") == "inc" || getprop("ro.build.product") == "inc"
|| getprop("ro.product.board") == "inc"
E: Error in /sdcard/OMFGB_inc-1.3.1_nightly-08-25.zip
(status7)
Installation aborted.
Anyone ever seen this?
Click to expand...
Click to collapse
It looks like you are trying to a Droid Incredible Rom on your Droid Incredible 2. ro.build.product = inc is the Droid Incredible
ro.build.product = vivow is the Incredible 2

That makes sense. But I did get those downloads from this forum. I guess it must be the download because I just successfully flashed GAPPS.

Rossco_Pee said:
That makes sense. But I did get those downloads from this forum. I guess it must be the download because I just successfully flashed GAPPS.
Click to expand...
Click to collapse
Are you flashing these files for the inc2?
OMGB_vivow-1.2.2.zip
or
OMFGB_vivow-1.3.1
Also are you checking the md5 to make sure you don't have a corrupt download?

I had the same exact issue same exact ROM. switching recoveries solved it for me
Sent from my ADR6350 using xda premium

As the other post said you're trying to install OM(F)GB for the original Droid Incredible. The code name for the Inc2 is Vivow. That's why the asserts in the updater-script are failing.
Sent from my Incredible 2 using XDA App

check the version of CWM. I read somewhere that one of the 5.0.something did not work well. Sorry I can't remember which one it was.

Can't install zips in recovery

I've got a nasty problem on my Sprint Gnex. Every time I boot into recovery and tell it to flash a .zip file, it returns this:
Code:
-- Installing (whatever).zip
Finding update Package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "toroplus" || getprop("ro.build.product") == "toroplus"
E:Error in (whatever).zip
I have this problem in CWM and CWM Touch as flashed by ROM Manager. I've tried to edit my build.prop file to say either toroplus or torospr, but neither setting works. It doesn't matter what zip I use, they all die here.
I can back up and restore using nandroid, so what's broken and how do I fix it?

Try flashing the toroplus CWM image via fastboot: http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.3.1-toroplus.img

That did it! Thanks!

"Status 7" error in CWM while installing ROM

Hey everyone,
I'm currently trying to install the latest CM10 FXP131 ROM on my Arc S Lt18i. I flashed my phone to the first ICS Stock ROM by Sony and rooted it to install CWM Recovery.
Now, the next step was to flash the ROM. So I downloaded the Anzu version of the ROM, copied it to my SD and changed into Recovery mode. I picked "install zip from sdcard" and chose the ZIP I've just downloaded.
But instead of installing the ROM I got a error every time. It says
E:Error in /sdcard/cm-10-20120731-UNOFFICIAL-anzu.zip
(Status 7)
Installing aborted
Can someone help me to finally install the ROM?
Thank you so much,
Max

You also need to install the kernel.

Something like this a few lines above?
assert failed: getprop("ro.product.device") == "LT18i" || getprop("ro.build.product") == "LT18I" || getprop("ro.product.board") == "LT18i"

T-119a said:
Something like this a few lines above?
assert failed: getprop("ro.product.device") == "LT18i" || getprop("ro.build.product") == "LT18I" || getprop("ro.product.board") == "LT18i"
Click to expand...
Click to collapse
Nope, this is the full protocol:
Finding update package...
Opening update package...
Installing update...
set_perm: some changes failed
E:Error in /sdcard/cm-10-20120731-UNOFFICIAL-anzu.zip
(Status 7)
Installation aborted.
Just for information. The first thing I've done after installing CWN was straight installing the .zip . I did not flashed the kernel or wipe. Maybe that has something to say?
EDIT: Oh, and after every try to install the ROM my phones hangs up at the "SONY" logo and won't boot. I always have to flash the original sony .ftf to make it run again :/
Thank you,
Max

Open the cm-10-20120731-UNOFFICIAL-anzu.zip with a zip viewer, extract the boot.img and flash it via fastboot. Then perform a Full Wipe and try to flash the ROM again.

T-119a said:
Open the cm-10-20120731-UNOFFICIAL-anzu.zip with a zip viewer, extract the boot.img and flash it via fastboot. Then perform a Full Wipe and try to flash the ROM again.
Click to expand...
Click to collapse
I will try that, but I need a unlocked bootloader for that all, right? Or isn't that necassary at all?

maexjen said:
I did not flashed the kernel or wipe. Maybe that has something to say?
Click to expand...
Click to collapse
Yep.

maexjen said:
I will try that, but I need a unlocked bootloader for that all, right? Or isn't that necassary at all?
Click to expand...
Click to collapse
If you want to flash cyanogen you have to unlock your bootloader. An unlocked bootloader is recommend for flashing custom Roms and kernels.

Thank you for your clarification! It's working now! =)

T-119a said:
Something like this a few lines above?
assert failed: getprop("ro.product.device") == "LT18i" || getprop("ro.build.product") == "LT18I" || getprop("ro.product.board") == "LT18i"
Click to expand...
Click to collapse
Hello... I'm flashing new ROM and facing Status 7 error with what you said at the front... Here's the error message:
assert failed: getprop ("ro.product.device") == "c8812" | | gerprop ("ro.build.product") == "c8812" | | getprop ("ro.product.device") == C8812 "| | getprop (" ro.build.product ") ==" C8812 "
E: Error in / sdcard/C8812_20120822005.zip
(Status 7)
Installation aborted.
Can I know the cause of this and how to overcome that? Please & Thanks!

I'm getting this exact same problem on my Arc S except with cm10 Fxp138. My bootloader is unlocked, im rooted, i flashed the kernel first and STILL i get Status 7 error installation aborted. If someone could help, that'd be great

I am also getting the same error but on Sony LWW with Pacman JB ROM.

I also got this status 7 error with the code "Status 7 - symlink: some symlinks failed".
After deleting the first line (before the ; sign) I could get the rom to install.
I would like to know, why / how this can happen... Maybe flashing a false kernel or other things?

I think maybe binary and script don't match each other; or maybe there's error in text of script
(sorry for my bad english)

try to flash the kernel lupus

Firstly, give us recovery log. Secondly, I had such an issue with CM7.1 quite long time ago. I've fixed it by changing phone's ID from LT18i to LT15i via fastboot. There's a proper command for it.
1. Go to CWM
2. Plug phone
3. "adb pull tmp/recovery"

WHAT ?
Try a full wipe ( data , cache )

CM10 on my ARC
I have the same, install new baseband upper then 70 or official ics 4.0.4 then use flashtools to install kernel and flash rom
You have unlocked bootloader ??

i have "Status 7 - symlink: some symlinks failed" when i try install Jelly-v4.zip. anyone help me, i have downloaded that rom 3 times but it can't help

meinmain said:
Hello... I'm flashing new ROM and facing Status 7 error with what you said at the front... Here's the error message:
assert failed: getprop ("ro.product.device") == "c8812" | | gerprop ("ro.build.product") == "c8812" | | getprop ("ro.product.device") == C8812 "| | getprop (" ro.build.product ") ==" C8812 "
E: Error in / sdcard/C8812_20120822005.zip
(Status 7)
Installation aborted.
Can I know the cause of this and how to overcome that? Please & Thanks!
Click to expand...
Click to collapse
I had a lot of frustration with this. Had many attempts. The only thing that seemed to work for me was to flash the doomlord kernel. Then it worked perfectly.

[Q] HTC Desire aborts when installing ROMS

I'm running Clockworkmod Recovery v5.0.2.0, everything is wiped. I'm trying to install a ROM but I get this error message:
assert failed: getprop("ro.product.device") == "bravo" ||
getprop("ro.build.product") == "bravo"
E:Error in /sdcard/Elk759_0.26.zip
(status 7)
Installation aborted.
I used 4 different ROMs and I get the same message. What should I do?

Siousat said:
I'm running Clockworkmod Recovery v5.0.2.0, everything is wiped. I'm trying to install a ROM but I get this error message:
assert failed: getprop("ro.product.device") == "bravo" ||
getprop("ro.build.product") == "bravo"
E:Error in /sdcard/Elk759_0.26.zip
(status 7)
Installation aborted.
I used 4 different ROMs and I get the same message. What should I do?
Click to expand...
Click to collapse
Change your recovery ASAP to a newer CWM version or much better : 4ext touch recovery and see if it works.
________________________________
Please press thanks if I helped you in any way.
Sent from my HTC Desire using the xda app.

Check the hboot requirement of the roms and the md5 of the zips. If all is okay then it's time to upgrade the recovery. Flash 4ext as it is the best of'em all.

Siousat said:
I'm running Clockworkmod Recovery v5.0.2.0, everything is wiped. I'm trying to install a ROM but I get this error message:
assert failed: getprop("ro.product.device") == "bravo" ||
getprop("ro.build.product") == "bravo"
E:Error in /sdcard/Elk759_0.26.zip
(status 7)
Installation aborted.
I used 4 different ROMs and I get the same message. What should I do?
Click to expand...
Click to collapse
Hm, also make sure you are using htc desire compatible rom.
________________________________
Please press thanks if I helped you in any way.
Sent from my HTC Desire using the xda app.

Siousat said:
getprop("ro.product.device") "bravo"
Elk759_0.26.zip
Click to expand...
Click to collapse
I think reading before answering a question is a good place to start
Sent from my HTC Desire

Stuck in Recovery Mode....!!

Hi Xda This is owais khatri here,,
I haved watch whole xda but still not found help...
I have download all bin total.... 9 bins from xda and 2 from Amazon web site...
i have Adb and fastboot whole correct and recognze device,
bin download most of them is Cant read bin and 2 are running but at end they show (( assert failed: getprop ("ro.product.device") == "kodiak" || getprop ("ro.build.device") e:error in /tmp/update.zip (status 7) installation aborted ))
HURTINGGG..
plz help meeee,,,,

owais khatri said:
(( assert failed: getprop ("ro.product.device") == "kodiak" || getprop ("ro.build.device") e:error in /tmp/update.zip (status 7) installation aborted ))
Click to expand...
Click to collapse
Put the BIN file in the same folder where your ADB files are.
Use the exact name of the BIN file in the command line or rename it to a short & simple name, like your example above (e.g. "update.bin")
(Don't use ZIP files if you work with the official Amazon recovery, it can only process BIN files.)
Did you modify the build.prop on your device? What was the last OS version you had installed?

stuck at fire system recovery
Bingo Bronson said:
Put the BIN file in the same folder where your ADB files are.
Use the exact name of the BIN file in the command line or rename it to a short & simple name, like your example above (e.g. "update.bin")
(Don't use ZIP files if you work with the official Amazon recovery, it can only process BIN files.)
Did you modify the build.prop on your device? What was the last OS version you had installed?
Click to expand...
Click to collapse
i had same problem please someone who help me

owais khatri said:
Hi Xda This is owais khatri here,,
I haved watch whole xda but still not found help...
I have download all bin total.... 9 bins from xda and 2 from Amazon web site...
i have Adb and fastboot whole correct and recognze device,
bin download most of them is Cant read bin and 2 are running but at end they show (( assert failed: getprop ("ro.product.device") == "kodiak" || getprop ("ro.build.device") e:error in /tmp/update.zip (status 7) installation aborted ))
HURTINGGG..
plz help meeee,,,,
Click to expand...
Click to collapse
Do you still have Safestrap installed? What happens when you try to reboot?

owais khatri said:
Hi Xda This is owais khatri here,,
I haved watch whole xda but still not found help...
I have download all bin total.... 9 bins from xda and 2 from Amazon web site...
i have Adb and fastboot whole correct and recognze device,
bin download most of them is Cant read bin and 2 are running but at end they show (( assert failed: getprop ("ro.product.device") == "kodiak" || getprop ("ro.build.device") e:error in /tmp/update.zip (status 7) installation aborted ))
HURTINGGG..
plz help meeee,,,,
Click to expand...
Click to collapse
How are you connecting to the device? In Safestrap or Amazon Recovery? You should be able to sideload the Amazon official update via the Amazon Recovery no matter what condition your build.prop is in.
Download the official Amazon update bin for your device
Boot into Amazon Recovery by holding down Volume Down+Power
Select "Sideload update from ADB"
Run adb sideload <name of update file>.bin
Recommend you do a factory reset afterwards to be safe
Assuming all is well you can reroot now and go back to whatever custom image you desire

I have Amazon fire phone but it continuesly going on recovery mode after update and resetting