Develop Bugs

[Q] Unable to install CM 7.2 installed due to build.prop error...

Hi guys, need some help here.
Trying to get the CM 7.2 installed on my Verizon R800x. I updated the firmware to .89 (had to relock by bootloader to do so). I then tried to do the fastboot flash boot boot.img and got the kernel to load, but now when I try to install the update.zip from the CWM download I get the following. I unlocked my bootloader again (using the original method from ashergray like fastboot -i oem unlock 0xfce... etc) and tried again. Same result. Any ideas?
CWM-based Recovery v5.0.2.7-nAa-r2
-- Installing: /sdcard/update.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "R800x" || getprop("ro.build.product") == "R800x" || ("ro.product.board") == "R800x" || ("ro.product.device") == "zeusc" || getprop ("ro.build.product") == "zeusc" || getprop(ro.product.board") == "zeusc"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.

Found the answer in
http://forum.xda-developers.com/showpost.php?p=21721347&postcount=147
Just waiting for my Market to start downloading things so I can edit the file

"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] A partially bricked Xperia Arc

So I have a bricked Xperia Arc(LT15i) here. It's not completely bricked as I can enter fastboot mode. So here's my problems.
Only info I could find about installing cwm from fastboot is using recoveryArc.img (CWM 5.x) - It flashs fine, and boots into recovery. The problem is when I try to install a rom zip, the first assert line of script fails. (My phone is not LT15i? But it's written clearly under the battery. Is there a version of Arc not mentioned in the assert line given below?)
Code:
assert(getprop("ro.product.device") == "LT18i" || getprop("ro.build.product") == "LT18i" ||
getprop("ro.product.device") == "LT18a" || getprop("ro.build.product") == "LT18a" ||
getprop("ro.product.device") == "LT15i" || getprop("ro.build.product") == "LT15i" ||
getprop("ro.product.device") == "LT15a" || getprop("ro.build.product") == "LT15a" ||
getprop("ro.product.device") == "anzu" || getprop("ro.build.product") == "anzu");
Well then, I tried also flashing boot.img from FXP147-cm-10-20121118-UNOFFICIAL-anzu.zip and cm-9.1.0-anzu.zip. They also flash fine but does not boot into recovery. I mean not right after installing. I can't get into it manually either. There is no blue led, no luck with spamming back key either.
The third stunt I pulled was to remove assert line from cm-9.1.0-anzu.zip, flash recoveryArc.img, get into recovery, flash cm-9.1.0-anzu.zip (now suceeds), wipe cache/data/dalvik then flash boot.img from cm-9.1.0-anzu.zip via fastboot. This doesn't work either. Boot doesn't get past the flash image.
I'm just wondering if there was someone who have experienced this problem before and how they fixed this.

Read the thread a few below this, the one that uses the actual error message as the thread title.
Sent from myushi

Try to repair the phone with SUS.
http://www.sonymobile.com/global-en/tools/update-service/
Note:
all data on phone will be lost! So make backup from SD with other phone or PC with cardreader if you need some data from SDCard.
I always recommend to use SUS(formerly SEUS) for flashing original firmware, cause PCCompanion often causes problems.
Also remove SIM; When i bought my ArcS i directly updated it from GB to ICS with SUS and i already have inserted SIM when doing this,
after updating all servicenumbers storaged on SIM were lost

[Q] CM 10.1 and 10.2 hboot 1.72 problem

I have an HTC ONE X
I'm trying to put to my X cm10.1 or cm10.2 and the installation is being aborted with error :
assert failed: getprop ("ro.bootloader") == "1.28.0000" || getprop ("ro.bootloader") == "1.31.0000" || getprop ("ro.bootloader") == "1.33.0000" ||
getprop ("ro.bootloader") == "1.36.0000" ||getprop ("ro.bootloader") == "1.39.0000"
E:Error in /sdcard/cm-10.2.20130829-NIGHTLY-endeavour.zip << or /sdcard/cm-10.1.2-endeavour.zip
(Status 7)
Installation aborted.
My hboot is 1.72.000 maybe I must downgrade form this hboot becouse is too new ??

I think you have delete the line that checks for hboot 1.72 from a file somewhere in the meta-inf folder
Edit: found it on an older thread, open the rom zip on your PC before you copy it to phone and Remove the line in /META-INF/com/google/android/updater-script that tells it to look for that hboot. Thanks to @Whoareyou for that info
Put the kettle on

j4ru said:
I have an HTC ONE X
I'm trying to put to my X cm10.1 or cm10.2 and the installation is being aborted with error :
assert failed: getprop ("ro.bootloader") == "1.28.0000" || getprop ("ro.bootloader") == "1.31.0000" || getprop ("ro.bootloader") == "1.33.0000" ||
getprop ("ro.bootloader") == "1.36.0000" ||getprop ("ro.bootloader") == "1.39.0000"
E:Error in /sdcard/cm-10.2.20130829-NIGHTLY-endeavour.zip << or /sdcard/cm-10.1.2-endeavour.zip
(Status 7)
Installation aborted.
My hboot is 1.72.000 maybe I must downgrade form this hboot becouse is too new ??
Click to expand...
Click to collapse
Either remove the lines that check the HBoot version altogether, or edit the 1.28.0000 text to read 1.72.0000 in the update script. It then works.
This has been covered already in the CM thread several times.

Worked ... Thanks.

[Q] Samsung Galaxy S3 (Tmobile) T999 - Root Access Possibly Lost. Fix?

Hi experts!
I'm trying to install CyanogenMod on my Samsung Galaxy S3 Tmobile (T999) for the first time. I just rooted the device and then installed the One Touch Cyanogen App on the phone, completed the steps on the phone and then installed the s/w on PC. After everything's done and CyanogenMod is installed on the phone successfully I get this msg - root access possibly lost. fix?
I've tried all the 3 options I get on this screen - No, Yes & Go Back. But all of these push me back to square 1 and I have to redo everything again. I've tried at least 5 times but I'm still unable to get CM set up on my phone. Please assist.
Another thing I noticed after I rooted and did a factory reset is that I no longer have Google Contacts Sync available. Calender, Mail, Bookmarks etc all there but no Contacts Sync. When I click on "Contacts" app and click on Accounts I dont find Google listed.
This is my first time rooting & installing custom ROM on my Galaxy S3 (Tmobile). Pls help me.

Flash custom recovery, nandroid, full wipe, then flash cm from their site

Root access is missing
serio22 said:
Flash custom recovery, nandroid, full wipe, then flash cm from their site
Click to expand...
Click to collapse
Thanks for your response. What I did was Unrooted and loaded Stock ROM T999UVUENC2 from Sammobile.com
Then tried to follow the steps from their site get.cm and again everything until the end worked fine. The PC installer completed successfully but when the phone rebooted it showed "Root access is missing". When I select "Yes" here I'm back to square 1 again. This is so frustrating.
Pls, pls, pls, help!

I'm a newbie
Also I'm newbie to this. What is meant by -- Flash custom recovery, nandroid, full wipe, then flash cm from their site
I was only trying to follow the easy way by doing it from their website get.cm but apparently I'm unable to do so.
Please tell me how

Retried still failed
serio22 said:
Flash custom recovery, nandroid, full wipe, then flash cm from their site
Click to expand...
Click to collapse
I entered ClockworkMod Recovery v6.0.4.5 and did the following:
1. Wipe data/factory reset
2. Wipe cache partition
3. Mounts and Storage > format /system
4. Mounts and Storage > mount /system
5. Advanced > wipe dalvik cache
5. Install zip: cm-11-20140210-SNAPSHOT-M3-d2tmo.zip
But I get the following error:
assert failed: getprop ("ro.bootlooder") == "T999UVDLJA" || getprop ("ro.bootlooder") == "T999UVDLJC" || getprop ("ro.bootlooder") == "T999UVDMD5" || getprop ("ro.bootlooder") == "T999UVUEMJC" || getprop ("ro.bootlooder") == "T999VVLDLL1" || getprop ("ro.bootlooder") == "T999LUVAMB7" || getprop ("ro.bootlooder") == "T999VVLUEMK5" || getprop ("ro.bootlooder") == "T999LUVUBMK4"
E: Error in /storage/sdcard1/CM-sd/cm-11-20140210-SNAPSHOT-M3-d2tmo.zip (Status 7) Installation aborted.

sandeeppotdar said:
I entered ClockworkMod Recovery v6.0.4.5 and did the following:
1. Wipe data/factory reset
2. Wipe cache partition
3. Mounts and Storage > format /system
4. Mounts and Storage > mount /system
5. Advanced > wipe dalvik cache
5. Install zip: cm-11-20140210-SNAPSHOT-M3-d2tmo.zip
But I get the following error:
assert failed: getprop ("ro.bootlooder") == "T999UVDLJA" || getprop ("ro.bootlooder") == "T999UVDLJC" || getprop ("ro.bootlooder") == "T999UVDMD5" || getprop ("ro.bootlooder") == "T999UVUEMJC" || getprop ("ro.bootlooder") == "T999VVLDLL1" || getprop ("ro.bootlooder") == "T999LUVAMB7" || getprop ("ro.bootlooder") == "T999VVLUEMK5" || getprop ("ro.bootlooder") == "T999LUVUBMK4"
E: Error in /storage/sdcard1/CM-sd/cm-11-20140210-SNAPSHOT-M3-d2tmo.zip (Status 7) Installation aborted.
Click to expand...
Click to collapse
You are on the NC2 bootloader. The zip (which by the way is incredibly old...) will not install because you are on that boot loader (because the boot loader version is not in the allowed list). Get the latest CM that is for d2lte and try that. That should work.
GS³: CarbonROM + NeOcOrE™.hYbR!D edition
Put your Kitsune up!

what a fail ....
Just did the automatic install thinking must be easier but ... all I see is just a big fail ... installed all good until at the end remained at that "root access posibily lost ...." Just a waste of time right now ... pretty disappointed in Cyanogen.
How you want to be successful when this released now for a while not working .... going to sleep worked all night
Edit : Basically just factory reset my phone to the same 4.3 update from Samsung get the last CM from where ....

Its not necessarily cm's fault, it happens, you should just put no though when that message appears, it's caused some problems for some people. Get the latest cm from cm's site under d2lte and flash with custom recovery. You can flash custom recovery with Odin, or if you're rooted with an app like flashify

Hope my guide helps you!
ZeRo-c0ol said:
Just did the automatic install thinking must be easier but ... all I see is just a big fail ... installed all good until at the end remained at that "root access posibily lost ...." Just a waste of time right now ... pretty disappointed in Cyanogen.
How you want to be successful when this released now for a while not working .... going to sleep worked all night
Edit : Basically just factory reset my phone to the same 4.3 update from Samsung get the last CM from where ....
Click to expand...
Click to collapse
I've been through this several times past few weeks. Learnt my lessons the hard way! So I just wrote my own Beginner's Guide to Rooting, Flashing & Unrooting. HTH.
P.S. I tried many ROM's for my S3 including CM11, MIUI etc but nothing beats SlimROM's. SlimKat Stable 9.0 (Android 4.4.4) released on Dec 26 is lean, mean, fast & battery efficient yet offers you all the amazing features you expect from a custom ROM Try it and you can come back to thank me with a beer!!