Database Info

[Q] cannot install ROM coz of CWM status 7

tried to install the "update-oxygen-2.1.4-signed.zip" with CWM 3.1.0.1 today but it didn't work, got stuck at
assert failed: getprop("ro.product.device") == "crespo" || getprop("ro.build.product") =="crespo""
E: Error in /sdcard/update-oxygen-2.1.4-signed.zip
(status 7)
tried to install another ROM but still the same happened...
btw im on stock 2.3.4
anyone encountered this before and know what the problem is? thanks in advance!

jakkix said:
tried to install the "update-oxygen-2.1.4-signed.zip" with CWM 3.1.0.1 today but it didn't work, got stuck at
assert failed: getprop("ro.product.device") == "crespo" || getprop("ro.build.product") =="crespo""
E: Error in /sdcard/update-oxygen-2.1.4-signed.zip
(status 7)
tried to install another ROM but still the same happened...
btw im on stock 2.3.4
anyone encountered this before and know what the problem is? thanks in advance!
Click to expand...
Click to collapse
you wont be able to install through rom manager. i'll explain why : when you install a rom through the rom manager, it automatically reboots to clockwork recovery to install the rom. here's the catch, being on stock, on reboot, you loose the clockwork recovery cause of a script on stock rom.
what you should do is flash the latest clockwork through fastboot , enter recovery immediately, and flash your rom. OR
install recovery through rom manager, download root explorer, navigate to the etc folder. search for a file instal-recovery.sh . you can either rename it to something else or delete it. then reboot into reovery and install your rom.

Verify its MD5 hash? or try another version of Clockwork Recovery (older version or the modded version of CWR)

[Q] roms won't flash. build.prop problem?

so my friend screwed up his optimus v. he said he did a factory reset, but im not sure how exactly he went about it.
anyway, now i can only get into his recovery (cwm 3.2.0.0). ive wiped everything but the sdcard, but no ROM i flash will work. Mirage and IHO both say:
assert failed: getprop("ro.product.device") == "thunderc"
and so on...
the overdrive rom says its installed when i flash it, but rebooting brings me back to recovery.
should i be finding a way to edit the build.prop or what?
any help would be much appreciated.

peopleface said:
so my friend screwed up his optimus v. he said he did a factory reset, but im not sure how exactly he went about it.
anyway, now i can only get into his recovery (cwm 3.2.0.0). ive wiped everything but the sdcard, but no ROM i flash will work. Mirage and IHO both say:
assert failed: getprop("ro.product.device") == "thunderc"
and so on...
the overdrive rom says its installed when i flash it, but rebooting brings me back to recovery.
should i be finding a way to edit the build.prop or what?
any help would be much appreciated.
Click to expand...
Click to collapse
There is a option in the Cwm " toggle assert " or something like that. Just toggle it to turn it off and try flashing again.
Also try to verify the md5 of rom to know whether it is corrupted or not.

[Q] cyanogen mod 10.1.3 RC2 fails install with "status 7"

I am super excited to see an official cyanogenmod for the photon Q 4G LTE. I quickly installed the motorola drivers for the phone, android sdk, unlocked the bootloader with motorola's unlocker, installed ClockworldMod Recovery 6.0.1.3 using fastboot.
Now using cw recovery I am trying to flash cm-10.1.3-RC2-xt897c.zip off my external SD card. The process starts fine buts ends up giving an error.
Code:
Finding update package...
Opening update package...
Installing update...
set_perm: some changes failed
E:Error in /external_sd/cm-10.1.3-RC2-xt897c.zip
(Status 7)
Installation aborted.
I get the same result regardless if I "wipe data/factory reset", "wipe cache partition", and "advanced/wipe dalvik cache".
According to a google search, the status 7 means the rom does not think it is compatible with the phone its being installed to. Well, I checked META-INF/com/google/android/updater-script.txt as described and it contains an entry for
Code:
getprop("ro.product.device") == "xt897c" || getprop("ro.build.product") == "xt897c");
.
It seems like everything checks out. Any ideas why the install is failing?

nezzer said:
I am super excited to see an official cyanogenmod for the photon Q 4G LTE. I quickly installed the motorola drivers for the phone, android sdk, unlocked the bootloader with motorola's unlocker, installed ClockworldMod Recovery 6.0.1.3 using fastboot.
Now using cw recovery I am trying to flash cm-10.1.3-RC2-xt897c.zip off my external SD card. The process starts fine buts ends up giving an error.
Code:
Finding update package...
Opening update package...
Installing update...
set_perm: some changes failed
E:Error in /external_sd/cm-10.1.3-RC2-xt897c.zip
(Status 7)
Installation aborted.
I get the same result regardless if I "wipe data/factory reset", "wipe cache partition", and "advanced/wipe dalvik cache".
According to a google search, the status 7 means the rom does not think it is compatible with the phone its being installed to. Well, I checked META-INF/com/google/android/updater-script.txt as described and it contains an entry for
Code:
getprop("ro.product.device") == "xt897c" || getprop("ro.build.product") == "xt897c");
.
It seems like everything checks out. Any ideas why the install is failing?
Click to expand...
Click to collapse
If it was not compatible, you would get an "assert failed", not "status 7" (I would think?)
If you think it is the assert that is failing, remove that line. Also, that updater-script file shouldn't be a .txt file - it should have no file extension.
In googling that error, everyone does seem to agree tho that status 7 is a mismatch, so I spose try removing that line. I usually would get an 'assert failed' message if these didn't match up - but I use TWRP, maybe that's the difference.

Bad to worse. I had booted the phone multiple times into recovery trying to apply the firmware. No matter what, when I later try to boot the OS, it just stayed stuck at the "boot loader unlocked" warning message, presumably because the firmware was never applied successfully. I left the phone at that screen overnight connected to the computer via USB.
Today I figured I would go ahead and try flashing TWRP to see if that changed anything. Now I am unable to get the phone to power on at all. Pressing the power button has no effect. Same for pressing vol down + pwr. When I plug it into USB the LED turns green but nothing happens on the display. Running adb devices or fastboot devices both say nothing is connected.
The thing appears completely dead. I took the case off and unscrewed the battery terminals for 5 minutes before screwing them back on. Still nothing. The display backlight never powers on.
This is a real bummer. Anyone run across anything like this before?
*Update* It would appear that the phone was not charging when stuck at the bootloader unlocked warning screen despite being connected to my PC. I left my phone on the charger for about 10 minutes and it popped back on to the bootloader unlocked screen. I was able to reboot to the fast boot screen. Since the state is reported as "battery low" I cant flash anything. I will report back once I can flash TWRP.

Mystery solved.
I flashed openrecovery-twrp-2.6.3.0-asanti_c.img and tried installing cm-10.1.3-RC2-xt897c.zip again. No go. Thankfully twrp has some nice features including a great file manager. I tried chmod 777 on the cm zip. No change. I then copied the cm zip from my external sd card to the internal memory. This failed a number of times before it went through successfully. That was my first clue.
I was able to flash cm from the internal sd card no problem. My guess is that my external SD card is experiencing read errors which caused the prior flash attempts to fail. Its working now.

I thought those problems have been solved and/or are nearly not existent.
My SD-Card became defective a few month after using it with my Photon Q. (Got a replacement within warranty.)
I guess that the Photon Q is kind of sensible which mSD's are working and which not.
My current mSD is working flawlessly.
But I flash nearly everytime over the internal storage, just to be sure that I don't get "invisible read errors" during flashing.
You should check your file, a hash may be the way to go.
I had problems with TWRP and CWM with my old mSD. (The flash process was terribly long.)
OpenRecovery was much faster but some flashes were still with issues.

[Q] Stuck on HTC logo

Hello,
Today, I updated to CM11 (the nightly), and got stuck on the white screen. This normally wouldn't be a problem, but my backup ROM (yesterday's nightly) will no longer install on my recovery (CWM 0.6.4.4). It gives an error along the lines of "assert failed: getprop("ro.product.device") == "evita". Whenever I connect it to the computer, it appears as the "One X" under "unknown devices", and won't respond to Fastboot or allow me to see the drive. I have the drivers installed because I have done this before.
What should I do?

The error you're getting when trying to restore your backup is saying that it's for the wrong device. Is it your own backup? Did you create the backup using CWM or TWRP?
Sent from my Evita

Joe Antonetti said:
Hello,
Today, I updated to CM11 (the nightly), and got stuck on the white screen. This normally wouldn't be a problem, but my backup ROM (yesterday's nightly) will no longer install on my recovery (CWM 0.6.4.4). It gives an error along the lines of "assert failed: getprop("ro.product.device") == "evita". Whenever I connect it to the computer, it appears as the "One X" under "unknown devices", and won't respond to Fastboot or allow me to see the drive. I have the drivers installed because I have done this before.
What should I do?
Click to expand...
Click to collapse
can u boot ur device in hboot ? and ur hboot version ?

Problems when flashing custom/official ROM

Hi guys. this is my first post here. I'm brazillian, sorry if I make some language mistake.
Yesterday I tried to install this ROM. My girlfriend asked for it, we have the same phone model (C2104). so I tried to install it in mine, to check if it's good and so on. but I started making mistakes here.
I installed CWM, downloaded the ROM and downloaded gapps. according to the ROM page, I should flash it through fastboot. I didn't pay enough attention and tried to flash it through recovery... my phone got bricked, it wouldn't turn on. it would just keep vibrating if I held the power button. if I connected it to the pc or to the charger, the red led would just keep blinkin.
after a lot of trying & searching I'd found out I should reinstall the stock ROM. so I installed Flashtool and tried to flash a stock ROM with it, but I received the same message every time: "processing of loader.sin finished with errors". then I tried repairing the phone through pc companion and it worked. until 30 minutes ago I was using my phone as if it was brand new. note: when I repaired it through pc companion, my pc started recognizing it as c2105.
earlier this sunday, I tried to flash it through flashtool in fastboot mode (after installing CWM again), but I always received an error message. this time I downloaded adb and fastboot sdk, and I received the same error. then I tried unlocking bootloader, and voila. it worked. but after this my phone got bricked again...
now it shows the SONY logo, but it's frozen on this screen. the only way I can power it off is removing the battery. I can access the recovery (now the cyanogen recovery is installed), but there's nothing I can do there. I tried to install the ROM through the recovery, but it says: "this package is for device: c2105, c2104, c2105, c2104, taoshan. this device is .". I tried pc companion repair again, but it says my phone has a modified firmware and so it can't be repaired through that tool. yesterday I made a stock ROM using this tutorial, but if I try to flash it through flashtool I get the same error I was getting yesterday ("processing of loader.sin finished with errors").
I'm stuck here. I've made a full backup through cwm, but since I can't boot the phone I can't install it again. please help me :crying: I wouldn't mind using stock ROM again, but I've had enough of it, I wanted to use a custom ROM for some time...
EDIT: after some thinking and trying, I've found out that pc companion wasn't working because I had unlocked bootloader. relocked it and could repair my phone. but now I have some doubts:
- is it possible for me to get a TA backup from my girlfriend's phone and restore it to my phone? will it work?
- can you guys help me on installing that ROM?

cJames2 said:
- is it possible for me to get a TA backup from my girlfriend's phone and restore it to my phone? will it work?
Click to expand...
Click to collapse
NO, don't do it will hardbrick your phone.
Edit : for more info about TA go HERE

cJames2 said:
Hi guys. this is my first post here. I'm brazillian, sorry if I make some language mistake.
Yesterday I tried to install this ROM. My girlfriend asked for it, we have the same phone model (C2104). so I tried to install it in mine, to check if it's good and so on. but I started making mistakes here.
I installed CWM, downloaded the ROM and downloaded gapps. according to the ROM page, I should flash it through fastboot. I didn't pay enough attention and tried to flash it through recovery... my phone got bricked, it wouldn't turn on. it would just keep vibrating if I held the power button. if I connected it to the pc or to the charger, the red led would just keep blinkin.
after a lot of trying & searching I'd found out I should reinstall the stock ROM. so I installed Flashtool and tried to flash a stock ROM with it, but I received the same message every time: "processing of loader.sin finished with errors". then I tried repairing the phone through pc companion and it worked. until 30 minutes ago I was using my phone as if it was brand new. note: when I repaired it through pc companion, my pc started recognizing it as c2105.
earlier this sunday, I tried to flash it through flashtool in fastboot mode (after installing CWM again), but I always received an error message. this time I downloaded adb and fastboot sdk, and I received the same error. then I tried unlocking bootloader, and voila. it worked. but after this my phone got bricked again...
now it shows the SONY logo, but it's frozen on this screen. the only way I can power it off is removing the battery. I can access the recovery (now the cyanogen recovery is installed), but there's nothing I can do there. I tried to install the ROM through the recovery, but it says: "this package is for device: c2105, c2104, c2105, c2104, taoshan. this device is .". I tried pc companion repair again, but it says my phone has a modified firmware and so it can't be repaired through that tool. yesterday I made a stock ROM using this tutorial, but if I try to flash it through flashtool I get the same error I was getting yesterday ("processing of loader.sin finished with errors").
I'm stuck here. I've made a full backup through cwm, but since I can't boot the phone I can't install it again. please help me :crying: I wouldn't mind using stock ROM again, but I've had enough of it, I wanted to use a custom ROM for some time...
EDIT: after some thinking and trying, I've found out that pc companion wasn't working because I had unlocked bootloader. relocked it and could repair my phone. but now I have some doubts:
- is it possible for me to get a TA backup from my girlfriend's phone and restore it to my phone? will it work?
- can you guys help me on installing that ROM?
Click to expand...
Click to collapse
Ok you got far x) so now you got cyanogenmodrecovery....
-Download the rom you told (Ressurection) to pc
- Extract Meta-inf/com/google/android/updater-script from it
Open it with word ... Search for lines that looks like that
assert(getprop("ro.product.device") == "C2105" || getprop("ro.build.product") == "c2105" || getprop("ro.product.device") == "taoshan" || getprop("ro.build.product") == "C2104" || abort("This package is for device: taoshan; this device is " + getprop("ro.product.device") + ".");
If you find it delete it...
Then repack it to the zip.... Now you should be able to flash
Sent from my Xperia T using XDA Free mobile app

SdtBarbarossa said:
Ok you got far x) so now you got cyanogenmodrecovery....
-Download the rom you told (Ressurection) to pc
- Extract Meta-inf/com/google/android/updater-script from it
Open it with word ... Search for lines that looks like that
assert(getprop("ro.product.device") == "C2105" || getprop("ro.build.product") == "c2105" || getprop("ro.product.device") == "taoshan" || getprop("ro.build.product") == "C2104" || abort("This package is for device: taoshan; this device is " + getprop("ro.product.device") + ".");
If you find it delete it...
Then repack it to the zip.... Now you should be able to flash
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
tried again right now, following your directions. now I received this error:
"E:failed to verify whole-file signature
E:signature verification failed
Installation aborted."

cJames2 said:
tried again right now, following your directions. now I received this error:
"E:failed to verify whole-file signature
E:signature verification failed
Installation aborted."
Click to expand...
Click to collapse
Oh i see...cyanogen recovery....
Download my fota flasher apk.... Open it as a ZIP ... Look into assets and extract fotatwrp.img ...
Put it on a sdcard and insert it into the phone
Start the phone in recovery and connect it to pc
Download and install " minimal adb and fastboot"
Open it and type:
adb shell
dd if=/storage/sdcard1/fotatwrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
then you got my newest recovery... That one should work
Sent from my Xperia T using XDA Free mobile app