I flashed back to stock AT&T, rooted, added Superuser, installed CWM, downloaded the CM9 stable zip from their site, put it on SD (tried internal and external, not that it should make any difference...), and keep getting this:
Installing: /sdcard/cm-9.0.0-quincyatt.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "SGH-I717" || getprop("ro.build.product") == "SGH-I717" || getprop("ro.product.device") == "quincyatt" || getprop("ro.build.product") == "quincyatt"
E:Error in /sdcard/cm-9.0.0-quincyatt.zip
(Status 7)
Installation aborted.
Was it a bad download, perhaps? Seems unlikely, but you never know I suppose.... The only thing I can come up with is that I'm on kernel 2.whatever and the screenshots I see with 4.0+ have 3.0.8. If this is the problem, how can I get that kernel on my Note before flashing CM9 again?
Please let me know if I'm missing any other important information needed to help solve this awful stock phone problem
You need to update ROM manager.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
kinghorsey said:
You need to update ROM manager.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
No, he needs to update his recovery which can be done via ROM manager if he wants to keep cwm. Twrp 2.2.1.1 also works.
CWM 5.8.4.8 is what ROM manager should install for you. If you give them money ROM manager can install the touch CWM 5.8.4.3. All of these versions work to flash cm9, cm10, or any other ROM.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
yollasho said:
No, he needs to update his recovery which can be done via ROM manager if he wants to keep cwm. Twrp 2.2.1.1 also works.
CWM 5.8.4.8 is what ROM manager should install for you. If you give them money ROM manager can install the touch CWM 5.8.4.3. All of these versions work to flash cm9, cm10, or any other ROM.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
I just got 5.5.0.4 which I assumed was the latest, and when I installed it again through ROM manager it gave me 5.0.2.7. Odd.
I'll look for 5.8 and update...
gauchotodd said:
I just got 5.5.0.4 which I assumed was the latest, and when I installed it again through ROM manager it gave me 5.0.2.7. Odd.
I'll look for 5.8 and update...
Click to expand...
Click to collapse
For the life of me I can't get CWM to update. I got 5.8.4.8 from their site, which is just a recovery img, put it on the SD card as is, didn't do anything, made it a zip to try to run it as update.zip, won't do it. I deleted the existing CWM folders, put the new one on there, and it still loads 5.5.0.4. Tried formatting everything, didn't work. ROM manager won't do anything for me either.
gauchotodd said:
For the life of me I can't get CWM to update. I got 5.8.4.8 from their site, which is just a recovery img, put it on the SD card as is, didn't do anything, made it a zip to try to run it as update.zip, won't do it. I deleted the existing CWM folders, put the new one on there, and it still loads 5.5.0.4. Tried formatting everything, didn't work. ROM manager won't do anything for me either.
Click to expand...
Click to collapse
Yeah if you're going to use the .img you have to use adb. The instructions are around.
ROM manager has the option at the top to "flash ClockworkMod recovery" that should install the latest non touch CWM. Did you try that?
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
yollasho said:
No, he needs to update his recovery which can be done via ROM manager if he wants to keep cwm. Twrp 2.2.1.1 also works.
CWM 5.8.4.8 is what ROM manager should install for you. If you give them money ROM manager can install the touch CWM 5.8.4.3. All of these versions work to flash cm9, cm10, or any other ROM.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
That's what I meant.
Accidentally omitted "via."
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
yollasho said:
Yeah if you're going to use the .img you have to use adb. The instructions are around.
ROM manager has the option at the top to "flash ClockworkMod recovery" that should install the latest non touch CWM. Did you try that?
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
I got an error in the command prompt when I tried adb, and I tried to Flash ClockworkMod Recovery in ROM manager but it installed 5.0 (wtf); since I can't get CWM to update to 5.8 I gave up and reflashed to stock, rerooted, reinstalled Superuser, put the TWRP 2.2.1.1 zip on my SD (openrecovery-twrp-2.2.1.1-sgh-i717-signed.zip), but when I try to install it gets a quarter of the way through and I get this:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
install_package = (2)
Installation aborted.
So I got GooManager from the market, and when I try to Install OpenRecoveryScript I get "No recoveries were found for your device."
I just can't catch a break here. What am I missing??
gauchotodd said:
I got an error in the command prompt when I tried adb, and I tried to Flash ClockworkMod Recovery in ROM manager but it installed 5.0 (wtf); since I can't get CWM to update to 5.8 I gave up and reflashed to stock, rerooted, reinstalled Superuser, put the TWRP 2.2.1.1 zip on my SD (openrecovery-twrp-2.2.1.1-sgh-i717-signed.zip), but when I try to install it gets a quarter of the way through and I get this:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
install_package = (2)
Installation aborted.
So I got GooManager from the market, and when I try to Install OpenRecoveryScript I get "No recoveries were found for your device."
I just can't catch a break here. What am I missing??
Click to expand...
Click to collapse
you got this installation aborted error in cwm when flashing twrp?
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
yollasho said:
you got this installation aborted error in cwm when flashing twrp?
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Sorry no, I reflashed to stock because it was the only way I could get rid of CWM completely. So that was in the stock recovery mode while trying to flash TWRP.
gauchotodd said:
Sorry no, I reflashed to stock because it was the only way I could get rid of CWM completely. So that was in the stock recovery mode while trying to flash TWRP.
Click to expand...
Click to collapse
Haha, ok. So you are Odin'd back to stock and stock recovery. I would use Odin to install the cwm from braways thread in dev section. Then you will have cwm and can flash stuff (like twrp). Once you flash latest twrp you will be set to flash any Rom. Hope that helps.
You can't flash this stuff from stock 3e recovery.
Good luck.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
yollasho said:
Haha, ok. So you are Odin'd back to stock and stock recovery. I would use Odin to install the cwm from braways thread in dev section. Then you will have cwm and can flash stuff (like twrp). Once you flash latest twrp you will be set to flash any Rom. Hope that helps.
You can't flash this stuff from stock 3e recovery.
Good luck.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
That's exactly what I used last time, the download for CWM there gave me 5.5 which caused the rest of my (initial) problems. After reflashing stock, I tried to put 5.8 on the SD and install the zip, and it wouldn't do that either. I'll give that another shot since TWRP isn't working either....
Finally got it: had to reinstall CWM 5.5 so I could install TWRP 2.2.1.1 and then it let me flash CM9. I swear I tried that already; I guess it just needed to be rubbed the right way. Thanks for the help!
gauchotodd said:
Finally got it: had to reinstall CWM 5.5 so I could install TWRP 2.2.1.1 and then it let me flash CM9. I swear I tried that already; I guess it just needed to be rubbed the right way. Thanks for the help!
Click to expand...
Click to collapse
Glad you got it figured out. You should be set now.
Sorry I wasn't more helpful, I was afk a bit.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
I am stuck at the boot page and when I go to the recovery it said MD5 error. I did a system clear to install a new ROM.. Please what should I do now? Thanks.
Search.
meiyi2 said:
I am stuck at the boot page and when I go to the recovery it said MD5 error. I did a system clear to install a new ROM.. Please what should I do now? Thanks.
Click to expand...
Click to collapse
Re-download again the rom. Flash again. Md5 means file is corrupted
Sent from my GT-i9300 using Tapatalk 4
You will need to re-download the rom and flash it again in recovery.
Yeah redownload and see if there is no problem with md5 flashing if so if it is corrupt try without md5 to flash.
Sent from my GT-I9100 using Tapatalk
I have samsung galaxy player 5 and i am getting error while installing slimkat 4.4.2 by Meticulus via CWM. Does anybody have the same problem............:crying:
mac1996 said:
I have samsung galaxy player 5 and i am getting error while installing slimkat 4.4.2 by Meticulus via CWM. Does anybody have the same problem............:crying:
Click to expand...
Click to collapse
According to the installation instructions, you WILL get an assert error:
Comming from a Pre "Slim-venturi-4.4.2.beta.1.7-UNOFFICIAL-20131221-1839" ROM
Do a back up!
Do factory reset/ wipe (incl. /system)
In recovery: flash ROM zip file. (You WILL get an assert error!)
Read the warning on the screen.
Flash the ROM again!
If you have and international device flash the INT Kernel from the OP.
Flash Gapps
Reboot.
yes i got the assesst error and then again when I tries to flash rom it gave me error
mac1996 said:
yes i got the assesst error and then again when I tries to flash rom it gave me error
Click to expand...
Click to collapse
try to back cm9 first then instal it again to cm10.2 and go to slimkat..in the op you get assert from first flash and flash it again..
Sent from my YP-G70 using XDA Premium 4 mobile app
Wen I turn the phone on it fails to load anything and then goes into recovery. This all came from when I attempted an OTA for a rom I was on before.
I 'm getting this error.
E:failed to verify whole-file signature
E:signature verification failed
Installation Aborted
I re flashed the CF Root using odin but still no luck.
Flash full stock firmware with odin then factory reset.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Flash full stock firmware with odin then factory reset.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
I'm sorry but i'm not sure what you mean by this. I have Odin but how do you flash a zip file?
Ok scratch what I said earlier its a .MD5 I just thought it was a .zip when it was downloading. I've managed to restore the stock firmware using odin. I gather that this has removed my root?
Bump
Recently i got a softwre update(43.68 Mb) on my stock rooted Galaxy S Duos s7562. after I have downloaded the update it asked to update now or later.. when accepted to install now, It swittched off and opened in cwm recovery and said failed to verify signature of file.. istallation aborted.
-in which I disabled signature verification.. but after a few sec "signature check disabled" msg pops up..
does it mean I can flash the update file manually after moving it from ( /cache/ ) to my sdcard?? or it will cause any problem???
help guys!
The ota wont install because you have a custom recovery. Try to flash a stock recovery back and take the ota again.
Sent from my Nexus 4 using XDA Free mobile app
lolcakes203 said:
The ota wont install because you have a custom recovery. Try to flash a stock recovery back and take the ota again.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
That I can figure but signature check is disabled then why not installing.. and Can I just take the downloaded OTA update from /cache/ and install it in recovery?
I think you can, but if you can download the ota from xda and then move the zip over to the sd card that would be best. Also, I think the zip verification has to do with md5 hashes, and not with whether or not the ota will install. It may also be failing because of your modified system.
Sent from my Nexus 4 using XDA Free mobile app
You could always stick the OTA on your hard drive from /cache/ and use adb sideload <file>