Develop Bugs

[Q] Status 7 Error Cyanogenmod 7 Nightly Build 14

Dear Forum Members,
I have a problem with my Desire HD.
My phone is rooted and has the 3.0.0.5 ClockworkMod Recovery installed.
I wanted to install Cyanogenmod 7 Nightly Build 14 for HTC Desire HD.
Iv'e downloaded the .zip file and put it on my SD-Card.
I went to ROM Manger and tried both ways (Install ROM from SD-Card ore Reboot in recovery mode and install it there).
Both ways I ended up getting this strange message:
Installing update…
assert failed: getprop("ro.product.device") == "bravo" || getprop("ro.build.product") == "bravo" || getprop("ro.product.board") == "bravo"
E:Error in /sdcard/cm_bravo_full-14.zip
(Status 7)
Installation aborted.
Is any one seen this error before? and if so can you please help me.
Kind Regards,
Whiteness.

Whiteness said:
Dear Forum Members,
I have a problem with my Desire HD.
My phone is rooted and has the 3.0.0.5 ClockworkMod Recovery installed.
I wanted to install Cyanogenmod 7 Nightly Build 14 for HTC Desire HD.
Iv'e downloaded the .zip file and put it on my SD-Card.
I went to ROM Manger and tried both ways (Install ROM from SD-Card ore Reboot in recovery mode and install it there).
Both ways I ended up getting this strange message:
Installing update…
assert failed: getprop("ro.product.device") == "bravo" || getprop("ro.build.product") == "bravo" || getprop("ro.product.board") == "bravo"
E:Error in /sdcard/cm_bravo_full-14.zip
(Status 7)
Installation aborted.
Is any one seen this error before? and if so can you please help me.
Kind Regards,
Whiteness.
Click to expand...
Click to collapse
The error messages suggest your trying to install the ROM for Bravo or the original Desire, I think you may have the wrong ROM?

Good be now downloading the ace version
Let you know!

[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] 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

[Q] TWRP installation on T999 Galaxy S3 - which file?

Hello - I have just downloaded TWRP Manager and am preparing to install the custom recovery on a Canadian Wind Galaxy S3 (model number SGH-T999V). I would appreciate it if someone could confirm which file I should use for this purpose. Is it the d2can file?
Thanks,
Mvt926

You can use d2can, d2tmo or d2lte.
I recommend d2tmo if you plan on flashing any if the roms we have. Ensures better chances of successful flashing.

DocHoliday77 said:
You can use d2can, d2tmo or d2lte.
I recommend d2tmo if you plan on flashing any if the roms we have. Ensures better chances of successful flashing.
Click to expand...
Click to collapse
Thanks. I used d2tmo and it seems to have worked.
Mvt926

mvt926 said:
Thanks. I used d2tmo and it seems to have worked.
Mvt926
Click to expand...
Click to collapse
I've just completed my first system backup under TWRP and,owing to space limitations, excluded the data option. How useful is the backup with this exclusion? If I need to re do the backup with data included, is there a way to delete the first backup before completing the second?
Thanks,
Mvt926

Data includes your apps/data and settings. It should be under the TWRP folder on your sd card.

DocHoliday77 said:
Data includes your apps/data and settings. It should be under the TWRP folder on your sd card.
Click to expand...
Click to collapse
Thanks - as I have already run a titanium backup on all apps and data, would it be safe to assume that I can exclude the data option under TWRP backup?
Another thing I have found is that choosing the restore option under TWRP (to see whether the backup I have made is available for restore) causes an immediate crash (of TWRP).
Thanks,
Mvt926

That is up to you. Backing up system and boot partitions is basically just backing up the rom, just so you know. I make a clean nandroid before doing anything, and keep it on my computer. Then I generally just backup the data partition and keep the rom handy. At least I used to. I don't do it much anymore because I use titanium and it kinda seemed a little redundant to me. I still keep an initial backup on my computer though....just in case.
Everyone is different. Its boils down to what you are most comfortable having as your backup.

DocHoliday77 said:
That is up to you. Backing up system and boot partitions is basically just backing up the rom, just so you know. I make a clean nandroid before doing anything, and keep it on my computer. Then I generally just backup the data partition and keep the rom handy. At least I used to. I don't do it much anymore because I use titanium and it kinda seemed a little redundant to me. I still keep an initial backup on my computer though....just in case.
Everyone is different. Its boils down to what you are most comfortable having as your backup.
Click to expand...
Click to collapse
Thanks. I have realized that TWRP permits backups to the external SD card so will use that for a full backup, including data, and then make a duplicate on my computer for additional security.
Mvt926

I need some help please
This might not be the best place to post this but I am stuck.
I have been forced to update after my GS3 took a dump. The power control chip went bad. I have now taken over my wife's old GS3. I had not rooted and installed a custom rom in so long it took me a while to figure it out. I have rooted it. I have superuser. I installed CWM. However, I cannot get CM 10.2.1 to install. I have 4.3.1 on my device and wanted to stick with that os. I did not want to go to kit kat. I try to install through cwm and keep getting installation aborted. I uninstalled KNOX as I thought that might be the issue but I am guessing from reading this that it is a bootloader issue. I don't know how to fix/change any of that and very much need someones help. I am on a TMO SGH T999 build number JSS15J.T999UVUENC2. Kernel 3.0.31. I would very much like someone to help me figure out how to get CM 10.2.1 to install on my device. Please if you or if you know someone who can help me.
Thanks,
TIDE
[email protected]

Flash the rom again and when it fails go back and copy log to sd. The info you'll want will be towards the bottom. Let us know what it says is the reason for failure.

follow up
DocHoliday77 said:
Flash the rom again and when it fails go back and copy log to sd. The info you'll want will be towards the bottom. Let us know what it says is the reason for failure.
Click to expand...
Click to collapse
Please excuse my ignorance, how do I create the log to copy. Is that done with a specific app?
I think I figured out how to create a log. Please see my follow up post.

I think I found the log
DocHoliday77 said:
Flash the rom again and when it fails go back and copy log to sd. The info you'll want will be towards the bottom. Let us know what it says is the reason for failure.
Click to expand...
Click to collapse
I think this is what you wanted. I know I am flashing the correct version for my phone sgh t999 which from what I understand a status 7 error could mean that I was not. I was thinking it had something to do with the boot loader and knox on this version 4.3.1.
-- Installing: /sdcard/0/0/cm-10.2.1-d2tmo.zip
Finding update package...
I:Update location: /sdcard/0/0/cm-10.2.1-d2tmo.zip
I:using /data/media for /sdcard/0/0/cm-10.2.1-d2tmo.zip.
Opening update package...
Installing update...
Warning: No file_contexts
script aborted: assert failed: getprop("ro.bootloader") == "T999UVDLJA" ||
getprop("ro.bootloader") == "T999UVDLJC" ||
getprop("ro.bootloader") == "T999UVDMD5" ||
getprop("ro.bootloader") == "T999UVUEMJC" ||
getprop("ro.bootloader") == "T999VVLDLL1" ||
getprop("ro.bootloader") == "T999LUVAMB7" ||
getprop("ro.bootloader") == "T999VVLDMF2" ||
getprop("ro.bootloader") == "T999VVLUEMK5"
assert failed: getprop("ro.bootloader") == "T999UVDLJA" || getprop("ro.bootloader") == "T999UVDLJC" || getprop("ro.bootloader") == "T999UVDMD5" || getprop("ro.bootloader") == "T999UVUEMJC" || getprop("ro.bootloader") == "T999VVLDLL1" || getprop("ro.bootloader") == "T999LUVAMB7" || getprop("ro.bootloader") == "T999VVLDMF2" || getprop("ro.bootloader") == "T999VVLUEMK5"
E:Error in /sdcard/0/0/cm-10.2.1-d2tmo.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/0/0/cm-10.2.1-d2tmo.zip")
I:using /data/media for /sdcard.

Yup. Thsts what I thought we'd see. Open the rom and find the updater script. Using Notepad++, edit it by replacing any of those builds with T999UVUENC2. If the one you choose to replace is listed more than once, replace it in all instances.
Delete the 3 signature files in the meta-inf folder, rezip and flash.

additional question
DocHoliday77 said:
Yup. Thsts what I thought we'd see. Open the rom and find the updater script. Using Notepad++, edit it by replacing any of those builds with T999UVUENC2. If the one you choose to replace is listed more than once, replace it in all instances.
Delete the 3 signature files in the meta-inf folder, rezip and flash.
Click to expand...
Click to collapse
Please excuse my ignorance, but I have never modified a script. I figured out how to pull out just the updater script file but I want to make sure I modify it correctly. Here is what the top bunch of lines look like in my script. If I understand correctly I am just going to replace any one of the "T999….." with "T999UVUENC2" It should make no difference which one? Also What are the signature files? I have three files in the META-INF folder, CERT.RSA, CERT.SF, and MANIFEST.MF. I presume you are talking about those three files? Please confirm that I am correct. If I need to modify anything else in the script below please let me know.
Thank you once again.
assert(getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product") == "d2tmo");
assert(getprop("ro.bootloader") == "T999UVDLJA" ||
getprop("ro.bootloader") == "T999UVDLJC" ||
getprop("ro.bootloader") == "T999UVDMD5" ||
getprop("ro.bootloader") == "T999UVUEMJC" ||
getprop("ro.bootloader") == "T999VVLDLL1" ||
getprop("ro.bootloader") == "T999LUVAMB7" ||
getprop("ro.bootloader") == "T999VVLDMF2" ||
getprop("ro.bootloader") == "T999VVLUEMK5");

You are correct on both. To make it even easier, replace the build ending in MJC. All you'd have to do is change MJC to NC2.
And don't worry too much about any of this. If you happen to do something wrong it would most likely fail w/o flashing anything.

DocHoliday77 said:
You are correct on both. To make it even easier, replace the build ending in MJC. All you'd have to do is change MJC to NC2.
And don't worry too much about any of this. If you happen to do something wrong it would most likely fail w/o flashing anything.
Click to expand...
Click to collapse
I got through that and now I get a status 4 error. I know I have more than enough internal memory. I did store the CM file on the internal memory to flash it. Would that have anything to do with it? Do I have to install it from an external sd?
Here is the log file. I think also for some reason my changes are not getting saved to the name when I change EMJC to ENC2 based upon what I'm seeing below. The signature files also don't seem to delete and when I remove the .txt at the end of the file name to save it back to the zip file I also think it stays there regardless.
-- Installing: /sdcard/0/0/cm-10.2.1-d2tmo.zip
Finding update package...
I:Update location: /sdcard/0/0/cm-10.2.1-d2tmo.zip
I:using /data/media for /sdcard/0/0/cm-10.2.1-d2tmo.zip.
Opening update package...
Installing update...
Warning: No file_contexts
script aborted: assert failed: getprop("ro.bootloader") == "T999UVDLJA" ||
getprop("ro.bootloader") == "T999UVDLJC" ||
getprop("ro.bootloader") == "T999UVDMD5" ||
getprop("ro.bootloader") == "T999UVUEMJC" ||
getprop("ro.bootloader") == "T999VVLDLL1" ||
getprop("ro.bootloader") == "T999LUVAMB7" ||
getprop("ro.bootloader") == "T999VVLDMF2" ||
getprop("ro.bootloader") == "T999VVLUEMK5"
assert failed: getprop("ro.bootloader") == "T999UVDLJA" || getprop("ro.bootloader") == "T999UVDLJC" || getprop("ro.bootloader") == "T999UVDMD5" || getprop("ro.bootloader") == "T999UVUEMJC" || getprop("ro.bootloader") == "T999VVLDLL1" || getprop("ro.bootloader") == "T999LUVAMB7" || getprop("ro.bootloader") == "T999VVLDMF2" || getprop("ro.bootloader") == "T999VVLUEMK5"
E:Error in /sdcard/0/0/cm-10.2.1-d2tmo.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/0/0/cm-10.2.1-d2tmo.zip")
I:using /data/media for /sdcard.

Can you get the log and paste the error here again? Not familiar with status 4 right off hand.
It shouldn't matter if its on internal or external sd. But you can try flashing from external.

DocHoliday77 said:
Can you get the log and paste the error here again? Not familiar with status 4 right off hand.
It shouldn't matter if its on internal or external sd. But you can try flashing from external.
Click to expand...
Click to collapse
I did , see above message. I am definitely not doing something right. I am on a Mac and using text editor to modify the file. That was my second try, the first time I did get a status 4 and I remodified and tried again and now I got a status 7 again.

It looks like the edit you made didnt take. Did you unzip the rom, make the edit and then rezip into a new file?
I don't know what text editor you should use on a mac. Go to Notepad++ website to see if they support it. If not you will have to find an editor that preserves the EOL formatting (End of Line) as Unix style. Not sure if a mac is able to do that with a built in editor.
You could make the edits on device I suppose, but its just a little more time consuming and easier to make mistakes.

DocHoliday77 said:
It looks like the edit you made didnt take. Did you unzip the rom, make the edit and then rezip into a new file?
I don't know what text editor you should use on a mac. Go to Notepad++ website to see if they support it. If not you will have to find an editor that preserves the EOL formatting (End of Line) as Unix style. Not sure if a mac is able to do that with a built in editor.
You could make the edits on device I suppose, but its just a little more time consuming and easier to make mistakes.
Click to expand...
Click to collapse
I found a way to edit the file and I know it is taking the edit. I have tried again and it still fails. However, when I view the log and it says saved in the CWM folder and I go to retrieve it, it is not there. There is no saved log that I can upload. Any thoughts?
Can I install kitkat on the SGH T999, it is the older model, not the LTE. And have you tried CM for KitKat? How is it, reasonably stable? Would that resolve my issues?