• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [1-21-13][ROM] CM10.1 for the evoLTE!!

I just downloaded an update for cm10 and made a backup. Tried installing and FAILURE TO INSTALL. tried dling again and moving to sd2. Same results. Tried using slightly older updates then the latest one, FAILURE TO INSTALL. tried wiping dalvik+cache. Still can't update. Does anyone know the problem?
 
I just downloaded an update for cm10 and made a backup. Tried installing and FAILURE TO INSTALL. tried dling again and moving to sd2. Same results. Tried using slightly older updates then the latest one, FAILURE TO INSTALL. tried wiping dalvik+cache. Still can't update. Does anyone know the problem?
Either it's bad downloads, as Early said, or you accidentally enabled zip signature verification in your TWRP settings. Disabling that should get it working (provided your downloads are good).
 
Could it be a kernel thing? Where the stock kernel can't run CM10?

I had that problem installing CM10 and was stuck at the splash screen, but found that answer in the forums, and I changed the kernel using the directions found here:

http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html

I ended up going back to stock ROM just because I was pretty ill with all the "XXX stopped working" messages. I had to manually change back to the stock kernel before my TWRP backup of the stock ROM would work again.

DUH!!!! OK, after reading the OP's post again, I realize that they're not even getting that far. Yes, I think that taking the check mark out of "verify zips" will help you. But you might run into the problem I reference above if you don't manually flash the kernel.
 
Probably a bad/intermittent connection. You're downloading from your phone right? I remember you mentioning before that's your main internet source.
 
Come on guys....give me some credit? I know I've only been at it 2 maybe 3 years.
I'm not using a custom kernel and zip verify was off. All ROMs are doing this.
 
Come on guys....give me some credit? I know I've only been at it 2 maybe 3 years.
I'm not using a custom kernel and zip verify was off. All ROMs are doing this.

You have a rom flash image on your internal sd card and the md5 checks out correctly, and it doesn't install?
 
Actually I turned on md5 for fun and it said something to the tune of no md5. Internal external.
 
Actually I turned on md5 for fun and it said something to the tune of no md5. Internal external.

Ok, we're miscommunicating.

On your phone, go to the flash zip image with EStrongs File Explorer. Long press the file, choose properties. In the dialog that comes up, choose Show checksum. Check md5 and then calculate the checksum.

Compare to the value shown on the dev's download server where you got the rom.

This is what folks have meant when asking if the md5 of the download is correct.
 
If the md5 sum fails its a bad download. If md5 checks out then the problem lies either with your recovery, SD card, or the transfer to the SD card
 
Cm10 says md5 is 56a30246aba670952748bc314444c5e3

Phone says its b1c8b7e8b9b8bbb288808a6ff8023332

Correct me if I'm wrong, but those don't match.
 
Back
Top Bottom