Develop Bugs

Can't Flash Cyanogen 9 RC2

Trying to flash Cyanogen 9 RC2 on my Verizon Galaxy Nexus. Rooted, unlocked and running the latest ClockworkMod. Most recent GAPPS flashed as well.
This is the error I get when trying to flash...ANY HELP would be GREATLY APPRECIATED!!!!
Installing: /sdcard/Flashables/cm-9.0.0-RC2-toro.zip
Finding update package…
Opening update package…
Installing update…
Assert failed: getprop(“ro.product.device”) == “toro” || getprop(“ro.build.product”) == “toro”
E:Error in /sdcard/Flashables/cm9.0.0-RC2-toro.zip
(Status 7)
Installation Aborted

It's failing to verify that your phone is in fact a toro. Which means the ROM you're currently using has modified something g to show you as not being a toro.
Suggestion: flash factory image and begin the whole process again.
Sent from my Galaxy Nexus using Tapatalk 2

[Q] Stuck on recovery, data/cache wiped, no rom to flash

I just bought a SGS3 today, and I used this guide to root and install recovery
theunlockr[DOT]com/2012/07/19/how-to-root-and-install-clockworkmod-recovery-on-att-galaxy-s3/
I'm thinking now that this was a big no-no.
I downloaded the latest CM10 nightly and the respective gapps.zip, however when I boot into recovery and try to install it, it tells me this:
Code:
-- Installing: /sdcard/cm-10-20121014-NIGHTLY-d2att.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att"
E:Error in /sdcard/cm-10-20121014-NIGHTLY-d2att.zip
(Status 7)
Installation aborted.
I have already (stupidly) factory reset/wiped and formatted cache. What can I do?
Thanks in advance for any help.

The error status 7 is most likely an outdated recovery, get a newer version after you get your phone going. Most likely you will have to Odin back to stock or stock rooted and start over. Here are some pretty clear instructions, read the whole first post at least http://forum.xda-developers.com/showthread.php?t=1739426
[HOWTO] [ROOT] No Tripping Flash Counter - [ATT / Bell / Telus / Rogers / Sasktel]
Good luck and remember xda should always be your first stop lol

HTC one X failed. error Status 7

sorry if i posted wrong .but first time here.
i tried this : Unofficially Update HTC One X to Android 4.1 Jelly Bean With Domination ROM Based on CM10 it all went smoothly. UNTILL. when i reached the 16'th step. i got this error:
-- Installing: /sdcard/endeavoru-domination-5.zip
Finging Update package...
Opening Update package...
Installing Update...
assert failed: Getprop("ro.product.device") == "endeavoru" || getprop("ro.build.product") =="endeavoru" E:Error in /sdcard/endeavoru-domination-5.zip (status7) Installation aborted
is there anything to do to save my phone ? i cant get it to mount in the usb so that i can replace files on the SD card or anything. so i quess my phone is ruined ?

fastboot flash the latest recovery http://forum.xda-developers.com/showthread.php?t=1594819
then try again. If still the same error, at least with new recovery, you can mount usb storage then you can put in other rom.zip

you sure you have the international one x and not the evita?

tomascus said:
you sure you have the international one x and not the evita?
Click to expand...
Click to collapse
ok to be honorst. i have/had no clue what im doing. a friend reffered me to the page where i could do it because he did it on hes phone.
so i tried.
but if i have to place other files on my SD card or anything i could just aswell throw my phone away, as i cant use it for anything as it is right now and i cant enter the SD card on my pc

ckpv5 said:
fastboot flash the latest recovery http://forum.xda-developers.com/showthread.php?t=1594819
then try again. If still the same error, at least with new recovery, you can mount usb storage then you can put in other rom.zip
Click to expand...
Click to collapse
nice. ill give it a try. thanks. ill update to let you know if it solevd it

Rasmus8934 said:
nice. ill give it a try. thanks. ill update to let you know if it solevd it
Click to expand...
Click to collapse
Frist STOP FLASHING, put the phone in bootloader and see whats on top
Does it say ENDEAVORU
or
Does it say EVITA
if it says evita , stop flashing stuff from here because you might brick the phone !!!

the problem was solved. thanks for the quick and helpfull support

Rasmus8934 said:
the problem was solved. thanks for the quick and helpfull support
Click to expand...
Click to collapse
What was the problem ? Post it please it might help others at some point

Rasmus8934 said:
ok to be honorst. i have/had no clue what im doing...
Click to expand...
Click to collapse
And there's your issue...

ckpv5 said:
fastboot flash the latest recovery http://forum.xda-developers.com/showthread.php?t=1594819
then try again. If still the same error, at least with new recovery, you can mount usb storage then you can put in other rom.zip
Click to expand...
Click to collapse
this solved it.

And for the problem of google apps stopping to work that you mentioned before, you need to flash gapps for that rom. Not familiar with a CM10 ROM but that usually the case.

[Q] Stuck in ICS and Google won't sync. Please Help?!?

G-nex verizon
rooted
Currently running CM9
I was running CM10 when I attempted to use the experimental update CM sent me. It installed fine, but google account was missing. Took the option to go back to CM10 and got stuck on the bootloader screen with the circle. Went into recovery mode in a panic and attempted to load one of my backups. The only one that worked was a CM9 backup from September. Now My google account won't sync, I can'tget onto the market. Recovery mode fails to install the nightly I put on the sdcard. At this point I've wiped the cashe, and done a factory reset. my sdcard was partitioned into that 0 folder by the update.At wit's end here. Any help would be greatly appreciated.

Don't panic, you got this.
Update your recovery to the latest version. If you're using twrp go to goo manager and update from the menu (install open recovery script). The most recent version of twrp is 2.4.1.0
Grab the CM version and gapps that you want to use and place them on your "sdcard"
Boot into recovery and flash CM and gapps.
Reboot.

Beezer80 said:
Don't panic, you got this.
Update your recovery to the latest version. If you're using twrp go to goo manager and update from the menu (install open recovery script). The most recent version of twrp is 2.4.1.0
Grab the CM version and gapps that you want to use and place them on your "sdcard"
Boot into recovery and flash CM and gapps.
Reboot.
Click to expand...
Click to collapse
I'm sorry, I'm a bit confused. I'm using clockwork mod. I've put a nightly on my sdcard and recovery recognizes it, but the install keeps failing. I'm really in a bad way. I can't restore my ROM Manager premium to download a rom and nothing I put on the sdcard is working. I think I need step by step help here.

your download from rom manager was bad. you have a couple options
1) go back to stock, download the rom, fastboot flash cwm, then flash the rom.
2) download the rom to your computer, then adb push it to your recovery.
3) download the rom on your phone directly from cm, and then flash it.

...
Again I tried to install cm10.1 - 20130212 nightly. This is what cw mod is saying
assert failed: getprop("ro.product.device") == "maguro: | | getprop("ro.build.product") == "maguro"
E:Error in /sdcard/0/cm-10.1 - 20130212 - NIGHTLY - maguro.zip
(Status 7)
Installation aborted.
What am I doing wrong?

wahrenjie said:
Again I tried to install cm10.1 - 20130212 nightly. This is what cw mod is saying
assert failed: getprop("ro.product.device") == "maguro: | | getprop("ro.build.product") == "maguro"
E:Error in /sdcard/0/cm-10.1 - 20130212 - NIGHTLY - maguro.zip
(Status 7)
Installation aborted.
What am I doing wrong?
Click to expand...
Click to collapse
you downloaded a GSM rom, not a verizon one. (maguro = GSM, Toro = verizon, Toroplus = Sprint.)
thats your problem.

that was great but now.
wahrenjie said:
Again I tried to install cm10.1 - 20130212 nightly. This is what cw mod is saying
assert failed: getprop("ro.product.device") == "maguro: | | getprop("ro.build.product") == "maguro"
E:Error in /sdcard/0/cm-10.1 - 20130212 - NIGHTLY - maguro.zip
(Status 7)
Installation aborted.
What am I doing wrong?
Click to expand...
Click to collapse
Zepius said:
you downloaded a GSM rom, not a verizon one. (maguro = GSM, Toro = verizon, Toroplus = Sprint.)
thats your problem.
Click to expand...
Click to collapse
Zep, thank you so much. I flashed the correct ROM. The issue I'm having now is the one I was having before. My phone wouldn't do the customary set up even after I did the factory reset. I can't seem to set up my google account so that I can load my calender and contacts and access the play store. It's not giving me that option.

did you flash gapps that go with the rom?

Zepius said:
did you flash gapps that go with the rom?
Click to expand...
Click to collapse
You're going to find this hilarious. I went and flashed the gapps right after the last reply. I have the play store, but know for some reason, my keyboard has stopped working. Is there a link for a better working set of gapps?

go on cm's site and find the most recent one.

...
Zepius said:
go on cm's site and find the most recent one.
Click to expand...
Click to collapse
Zep, Thanks alot for your help and patience. I got it working again. Sorry for all the noobitity.

Stuck in Recovery

Ok.. So going over the past events today... This morning I flashed color os 2.0, I liked it, but it was missing xposed mods lol.
So I then flashed Vanir, and customized it from there. However, I dont like the aosp cameras. They dont seem as clear or good with flash.
I tried flashing the LG camera port. Then the Lenovo Super camera port(Really wanted to get it working.. :/)
But I couldnt get those working, and then the google camera kept FCing, so I had to reflash Vanir. When I did that, It still fced.. So I flashed again, and ever since I've been trying to at least get a rom to boot.
Every time the phone boots up, it goes straight into Philz touch. No matter what rom i try, or what I do.
Idk if there is a fastboot mode, because I havent been able to find anything on there being one, so I'm really stumped.. :/
Also, in CMD My device says "Unauthorized" next to the name :/
Any help would be appreciated
Ask me anything
Sincerely Josh
P.S. Sorry for bad grammar.
EDIT: I FIXED IT:
So after looking around for a bit, I found this
And then after i flashed TWRP, every time I tried to flash something I got the error telling me my device was a "geefhd_att_us" instead of a geef, e980, or e986 so on so on.
I then searched google, and found a comment on this Here is the comment :
"I believe i found a fix: thanks to @veenab
extract the .zip open the extracted files and open META-INF > com > google > android > updater-script
next change
(getprop("ro.product.device") == "e986" || getprop("ro.build.product") == "e986" ||
getprop("ro.product.device") == "e980" || getprop("ro.build.product") == "e980" ||
getprop("ro.product.device") == "geefhd" || getprop("ro.build.product") == "geefhd" ||
getprop("ro.product.device") == "e988" || getprop("ro.build.product") == "e988" ||
getprop("ro.product.device") == "gkatt" || getprop("ro.build.product") == "gkatt" || abort("This package is for \"e986,e980,geefhd,e988,gkatt\" devices; this is a \"" + getprop("ro.product.device") + "\".")
Click to expand...
Click to collapse
to
(getprop("ro.product.device") == "e986" || getprop("ro.build.product") == "e986" ||
getprop("ro.product.device") == "e980" || getprop("ro.build.product") == "e980" ||
getprop("ro.product.device") == "geefhd" || getprop("ro.build.product") == "geefhd" ||
getprop("ro.product.device") == "geefhd_att_us" || getprop("ro.build.product") == "geefhd_att_us" ||
getprop("ro.product.device") == "e988" || getprop("ro.build.product") == "e988" ||
getprop("ro.product.device") == "gkatt" || getprop("ro.build.product") == "gkatt" || abort("This package is for \"e986,e980,geefhd,e988,gkatt\" devices; this is a \"" + getprop("ro.product.device") + "\".")
Click to expand...
Click to collapse
repackage the zip and flash."
As soon as I edited the code shown in that post it let me flash anything I wanted
Hope this Help anyone else who was in my predicament.

capeorigins said:
Ok.. So going over the past events today... This morning I flashed color os 2.0, I liked it, but it was missing xposed mods lol.
So I then flashed Vanir, and customized it from there. However, I dont like the aosp cameras. They dont seem as clear or good with flash.
I tried flashing the LG camera port. Then the Lenovo Super camera port(Really wanted to get it working.. :/)
But I couldnt get those working, and then the google camera kept FCing, so I had to reflash Vanir. When I did that, It still fced.. So I flashed again, and ever since I've been trying to at least get a rom to boot.
Every time the phone boots up, it goes straight into Philz touch. No matter what rom i try, or what I do.
Idk if there is a fastboot mode, because I havent been able to find anything on there being one, so I'm really stumped.. :/
Also, in CMD My device says "Unauthorized" next to the name :/
Any help would be appreciated
Ask me anything
Sincerely Josh
P.S. Sorry for bad grammar.
Click to expand...
Click to collapse
Same thing happened to me last night when flashing the M7 update to Cyanogen. ADB won't register the device in download mode, tried doing the hard reset (vol + power), doing a clean and dirty flash in recovery, even tried flashing a new recovery (which failed) but it just keeps rebooting to Philz recovery.

Mustang350 said:
Same thing happened to me last night when flashing the M7 update to Cyanogen. ADB won't register the device in download mode, tried doing the hard reset (vol + power), doing a clean and dirty flash in recovery, even tried flashing a new recovery (which failed) but it just keeps rebooting to Philz recovery.
Click to expand...
Click to collapse
hmm, yeah well im gonna try this. but if you have any luck let me know xD
Good luck, Lets hope we can fix this for both our phones

capeorigins said:
hmm, yeah well im gonna try this. but if you have any luck let me know xD
Good luck, Lets hope we can fix this for both our phones
Click to expand...
Click to collapse
Which recoveries did you try?

capeorigins said:
Which recoveries did you try?
Click to expand...
Click to collapse
CWM, TWRP and even tried reflashing Philz. All give me an installation error then reboot into recovery.

Mustang350 said:
CWM, TWRP and even tried reflashing Philz. All give me an installation error then reboot into recovery.
Click to expand...
Click to collapse
Hmm, Did my findings help?

capeorigins said:
Hmm, Did my findings help?
Click to expand...
Click to collapse
Attempting now

Mustang350 said:
Attempting now
Click to expand...
Click to collapse
/WIN meter is full! All systems green my friend!

Glad to help? hope this help others too!
Sent from my Optimus G Pro using Tapatalk

*sigh*
I wish I could have found this thread last night. I too got the bootloop in PhilZ and I found a solution through Google, where you flash a particular file and it magically fixed the problem. Well, I thought the file was universal, but nope. It was for a particular, unrelated phone. This bricked my entire phone (and I don't mean soft brick! I couldn't charge, enter recovery, enter download mode, nor even cold boot mode!!!). I just got back from ATT after replacing it under warranty.

spexwood said:
*sigh*
I wish I could have found this thread last night. I too got the bootloop in PhilZ and I found a solution through Google, where you flash a particular file and it magically fixed the problem. Well, I thought the file was universal, but nope. It was for a particular, unrelated phone. This bricked my entire phone (and I don't mean soft brick! I couldn't charge, enter recovery, enter download mode, nor even cold boot mode!!!). I just got back from ATT after replacing it under warranty.
Click to expand...
Click to collapse
Oh wow, that really sucks.. Sorry to hear that :/
I know I was scared to death when I was confronted with this problem, but the communities on the internet are awesome
Also, Did you lose any important data, or were they able to recover anything?
Sent from my LG-E980 using Tapatalk