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
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
I am trying to download AOKP's nightly aokp_maguro_kitkat_nightly_2014-01-04 but whenever I try to flash it the bot shows up with a error exclamation point and with the message at the bottom:
"set_metadata_recursive: some changes failed
E: Error in/sdcard/0/aokp_maguro_kitkat_nightly_2014-01-04 .zip
(Status 7)
Installation aborted"
I tried to flash older nightlys of the kitkat update but I get the same error. I have tried to wipe data/factory reset but that deosnt work. I can flash the AOKP mod I had before I tried this so there isn't a major problem if I can't update, but I would like to update to kitkat to improve my phone.
Anyone know why I keep getting this message and how to fix it?
Percurnicus said:
I am trying to download AOKP's nightly aokp_maguro_kitkat_nightly_2014-01-04 but whenever I try to flash it the bot shows up with a error exclamation point and with the message at the bottom:
"set_metadata_recursive: some changes failed
E: Error in/sdcard/0/aokp_maguro_kitkat_nightly_2014-01-04 .zip
(Status 7)
Installation aborted"
I tried to flash older nightlys of the kitkat update but I get the same error. I have tried to wipe data/factory reset but that deosnt work. I can flash the AOKP mod I had before I tried this so there isn't a major problem if I can't update, but I would like to update to kitkat to improve my phone.
Anyone know why I keep getting this message and how to fix it?
Click to expand...
Click to collapse
I think you have to update your recovery. Older versions are not compatible with kitkat. I'm using Philz touch recovery, here's a link to his thread: http://forum.xda-developers.com/showthread.php?t=2201860
You'll find different files for different types of tuna (galaxy nexus), choose the correct one according to your actual model, install it, and you're hopefully ready to flash.
Hope I could help!
Sent from my Nexus 7 using Tapatalk 4
Percurnicus said:
I am trying to download AOKP's nightly aokp_maguro_kitkat_nightly_2014-01-04 but whenever I try to flash it the bot shows up with a error exclamation point and with the message at the bottom:
"set_metadata_recursive: some changes failed
E: Error in/sdcard/0/aokp_maguro_kitkat_nightly_2014-01-04 .zip
(Status 7)
Installation aborted"
I tried to flash older nightlys of the kitkat update but I get the same error. I have tried to wipe data/factory reset but that deosnt work. I can flash the AOKP mod I had before I tried this so there isn't a major problem if I can't update, but I would like to update to kitkat to improve my phone.
Anyone know why I keep getting this message and how to fix it?
Click to expand...
Click to collapse
Yes, you need to update your recovery. I had same problem with an other kk ROM.
I suggest you to download last cwm from the official site and install that.
After that you can install the AOKP 4.4! :thumbup:
Inviato dal mio Galaxy Nexus utilizzando Tapatalk
ottoemezzo said:
I think you have to update your recovery. Older versions are not compatible with kitkat. I'm using Philz touch recovery, here's a link to his thread: http://forum.xda-developers.com/showthread.php?t=2201860
You'll find different files for different types of tuna (galaxy nexus), choose the correct one according to your actual model, install it, and you're hopefully ready to flash.
Hope I could help!
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This worked perfectly! thank you!
Just to provide all the information I have on hand, I have the
T-Mobile SGH-M919
android version 4.3
baseband version M919UVUEMK2
Current Recovery: ClockworkMod 6.0.4.7
My issue is that regardless of what rom I attempt to download i get the error below. Specifically, I've tried to download virginROM 2.3, which seems to be compatible with my device. From what I understand status 7 is in place to keep you from flashing an incompatible rom and so I'm not too sure how to proceed from here. Any and all help would be appreciated.
flash flash flashin things
format() expects 5 args, got 4
E: Error in /data/media/0/virginROM_v2.4.1.zip
(status 7)
Installation aborted.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log.
Please open ROM manager to report the issue.
Try using TWRP
My S4 Is Insane
Deviant Team Member
could be the signature veridicatrion, try disabling in recovery
aisarang said:
Just to provide all the information I have on hand, I have the
T-Mobile SGH-M919
android version 4.3
baseband version M919UVUEMK2
Current Recovery: ClockworkMod 6.0.4.7
My issue is that regardless of what rom I attempt to download i get the error below. Specifically, I've tried to download virginROM 2.3, which seems to be compatible with my device. From what I understand status 7 is in place to keep you from flashing an incompatible rom and so I'm not too sure how to proceed from here. Any and all help would be appreciated.
flash flash flashin things
format() expects 5 args, got 4
E: Error in /data/media/0/virginROM_v2.4.1.zip
(status 7)
Installation aborted.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log.
Please open ROM manager to report the issue.
Click to expand...
Click to collapse
I just ran into this a few minutes ago using Philz Touch. The solution I found was under the install zip menu, you should see "Don't Allow Old update-binary. It should have a check-mark; simply untick that option and try again.
lordcheeto03 said:
I just ran into this a few minutes ago using Philz Touch. The solution I found was under the install zip menu, you should see "Don't Allow Old update-binary. It should have a check-mark; simply untick that option and try again.
Click to expand...
Click to collapse
I'm using CWM and I don't see the option to check "donm't allow old update-binary." When I turn toggle signature verification off I get
E:footer is wrong
E: signature verification failed
Installation aborted.
and then get prompted to ask if i want to install an untrusted package. I attempted to download and apply the new 4.4.2 Google Edition by Davnh, haven't tried TWCP yet but i feel like it should still be doable via CWM.
I have the WiFi version of the Nexus 7 (2013). It is on KTU84P (Android 4.4.4). Bootloader is unlocked, TWRP 2.7.1.1 is installed for recovery and it is rooted.
I downloaded the OTA zip and have tried to install it in 2 different ways:
In TWRP, going to Advanced->ADB Sideload. Then from the connected PC, running "adb sideload <downloaded zip file>"
From TWRP on the device, going to Install, and selecting the downloaded zip.
In both cases, I get the same error:
Package expects build fingerprint of google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys or google/razor/flo:5.0/LRX21P/1570855:user/release-keys; this device has google/razor/flo:4.3/JSS15Q/779366:user/release-keys.
Click to expand...
Click to collapse
I'm not real sure what that error means, or how to go about addressing it. Any suggestions?
Thanks
You can't flash the OTA in TWRP, at least I don't think so, but I do know that 5.0 requires the latest version of TWRP, think it's 2.8.1.0
Sent from my 2013 Nexus 7
"Until death, I will remain a Dirty Unicorn.."
Tried updating to TWRP 2.8.1.0, I couldn't even get adb to recognize the tablet when in sideload. Just gave me device not found.
But, based on your other comment, I grabbed Wug's Nexus Root Toolkit and reflashed the stock recovery. Sideload is now in progress, I think I'm good to go (I probably just jinxed it!)
Thanks a lot for the help. I had thought it would just replace the recovery - I didn't realize that actually prevented it from running.
Update TWRP in bootloader. Fasboot flash recovery recovery.img
cabadam said:
I have the WiFi version of the Nexus 7 (2013). It is on KTU84P (Android 4.4.4). Bootloader is unlocked, TWRP 2.7.1.1 is installed for recovery and it is rooted.
I downloaded the OTA zip and have tried to install it in 2 different ways:
In TWRP, going to Advanced->ADB Sideload. Then from the connected PC, running "adb sideload <downloaded zip file>"
From TWRP on the device, going to Install, and selecting the downloaded zip.
In both cases, I get the same error:
I'm not real sure what that error means, or how to go about addressing it. Any suggestions?
Thanks
Click to expand...
Click to collapse
The error message is simply saying that the file you are trying to flash is to update from 4.4.4 to 5.0. But your device is at 4.3, and so, you cannot flash this file.
You will need to first upgrade to 4.4.4 and then flash from 4.4.4 to 5.0
jj14 said:
The error message is simply saying that the file you are trying to flash is to update from 4.4.4 to 5.0. But your device is at 4.3, and so, you cannot flash this file.
You will need to first upgrade to 4.4.4 and then flash from 4.4.4 to 5.0
Click to expand...
Click to collapse
No, it was at 4.4.4. For some reason it just didn't like TWRP. When I went back to stock recovery, it sideloaded just fine. I'm up and running now on 5.0.
cabadam said:
No, it was at 4.4.4. For some reason it just didn't like TWRP. When I went back to stock recovery, it sideloaded just fine. I'm up and running now on 5.0.
Click to expand...
Click to collapse
Weird - did you modify your build.prop for any reason?
jj14 said:
Weird - did you modify your build.prop for any reason?
Click to expand...
Click to collapse
Nope. When I got the tablet, I rooted it, flashed TWRP, but didn't modify anything else. And basically the root was just so I could do full backups.
I tried twrp amd cwm and both wont work. Twrp shows jelly bean and cwm shows previous version of kitkat. Both are not showing ktu84p
Build fingerprint error when flashing 5.0 OTA via stock recovery
ImjuzCY said:
I tried twrp amd cwm and both wont work. Twrp shows jelly bean and cwm shows previous version of kitkat. Both are not showing ktu84p
Click to expand...
Click to collapse
Hello!
Really want to flash the OTA without a total wipe.
First flashed it from TWRP 2.8.1.0 and got the wrong build finger print says I have Flo:4.3/JSS15Q/779366 and it expects KTU84P/1227136
Then using WugFresh 1.9.4 flashed stock recovery so I could sideload then encountered the whole adb disappearing in recovery - eventually solved that and finally managed to adb sideload saw my screen saying it was installing the update using the stock recovery - YAY! It was short lived as the stock recovery screen told me the exact same thing that TWRP had told me.
I looked at my build.prop and it says my ro.build.fingerprint=google/razor/flo:4.4.4/KTU84P/1227136. user/release-keys
Can someone enlighten me? I've wasted so much time on this I would love some keen insight - PLEASE!!
Thanks for any and all help!
Edbogue
Same problem
Hey guys!
I have the exact same problem as OP.
tried installing the zip using the latest version of TWRP and got the same error as OP.
I reverted back to stock recovery and tried to install the OTA update and I got a similar error (image attached).
I'm stuck, could someone help?
Rooted Nexus 7 2013 running 4.4.4 with TWRP 2.8.1.0
Same here. Build.prop has the desired release keys but cwm is giving me the exact same error. Anyone have any suggestions?
open the zip file,
edit META-INF/com/google/android/updater-script
just comment the following three lines:
#getprop("ro.build.fingerprint") == "google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys" ||
# getprop("ro.build.fingerprint") == "google/razor/flo:5.0/LRX21P/1570855:user/release-keys" ||
# abort("Package expects build fingerprint of google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys or google/razor/flo:5.0/LRX21P/1570855:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
then the update will go through.
you will take this workaround at your own risk.
make sure the version is 4.4.4/KTU84P already.
You need to be in kk stock with all apps from Google. !
I used NRT with sideload and no problem to flash 5.0 !
ahmao said:
open the zip file,
edit META-INF/com/google/android/updater-script
just comment the following three lines:
#getprop("ro.build.fingerprint") == "google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys" ||
# getprop("ro.build.fingerprint") == "google/razor/flo:5.0/LRX21P/1570855:user/release-keys" ||
# abort("Package expects build fingerprint of google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys or google/razor/flo:5.0/LRX21P/1570855:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
then the update will go through.
you will take this workaround at your own risk.
make sure the version is 4.4.4/KTU84P already.
Click to expand...
Click to collapse
ahmao, when you say comment you mean this
Code:
/*comment goes here*/
as they do with CSS?
open the zip file,
edit META-INF/com/google/android/updater-script
just comment the following three lines:
#getprop("ro.build.fingerprint") == "google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys" ||
# getprop("ro.build.fingerprint") == "google/razor/flo:5.0/LRX21P/1570855:user/release-keys" ||
# abort("Package expects build fingerprint of google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys or google/razor/flo:5.0/LRX21P/1570855:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
then the update will go through.
you will take this workaround at your own risk.
make sure the version is 4.4.4/KTU84P already.
Click to expand...
Click to collapse
As suggested, I tried that. Commented out the lines. Now when trying to flash it just says "Installing Update" then "Installation Aborted" gives no further details. Thanks for the suggestion though.
I had same problems on n4.
I tried flashing stock recovery. Doesn't work. So, I flashed the whole stock 4.4.4 rom, and then apply the Ota. And it worked.
But I had to wipe my user data. (maybe not necessary)
Envoyé de ma Nexus 7.2 depuis tapatalk
I finally waved the white flag and used WugFresh's toolkit 1.9.8. Cool thing though. I was planning on using it to restore to stock 4.4.4. When chose the option to Flash Stock it actually downloaded and flashed the lollipop factory image instead of the latest kitkat. Did wipe data as expected with a factory image but still saved a step. Even though the bootloader was updated, it remained unlocked so I was able to immediately root. I am normally not a fan of toolkits and am more inclined to do things myself (with lots of help from forums of course) for educational purposes but I spent 2 days working on it the other way and got it done this way in under an hour.
comment means add a hash "#" in front of the script line.
if further check fails, just find the line and comment out the app_check line.
bwat1009 said:
I finally waved the white flag and used WugFresh's toolkit 1.9.8. Cool thing though. I was planning on using it to restore to stock 4.4.4. When chose the option to Flash Stock it actually downloaded and flashed the lollipop factory image instead of the latest kitkat. Did wipe data as expected with a factory image but still saved a step. Even though the bootloader was updated, it remained unlocked so I was able to immediately root. I am normally not a fan of toolkits and am more inclined to do things myself (with lots of help from forums of course) for educational purposes but I spent 2 days working on it the other way and got it done this way in under an hour.
Click to expand...
Click to collapse
Thanks man!
That worked perfectly!
I lost all my data (which is fine) plus I really needed to start from scratch at some point.
I'm trying to install TWRP custom recovery, but it seems to be crashing all the time.
Does TWRP support Android 5.0 yet?