Every single one of the roms I've tried to install have failed during installation and have all said Zip corrupt. Any idea why this keeps happening? Is there another way to install these roms other than twrp and cwm. Could the transfer method of the Rom files have anything to do with the corrupt zips? I would greatly appreciate any helpful input from anyone.
@twistedshellz: before flash, check md5sum of downloaded zip and compare it with the one on downloadsite. If they differ, try another modem /pc /smartphone for downloading
Related
Hello, I am having a slight issue with TWRP while trying to install a rom. I have been able to successfully flash a kernel and make a back up using the recovery but when I tried to flash MDOB version 1.6, I received the error- Cant open zip file. I thought maybe I had a bad download so I downloaded version 1.7 and tried again with the same failure of being unable to open the zip. I've seen the error mentioned when i searched for a fix but never found a clear solution. Is there a setting I'm missing or a post i should read that i haven't stumbled upon yet? Thanks for any advice or guidance on how to correct this failure. I have attempted to mount the system as well prior to flash and moving the file to my micro-sd to attempt from there.
Droidmissionary said:
Hello, I am having a slight issue with TWRP while trying to install a rom. I have been able to successfully flash a kernel and make a back up using the recovery but when I tried to flash MDOB version 1.6, I received the error- Cant open zip file. I thought maybe I had a bad download so I downloaded version 1.7 and tried again with the same failure of being unable to open the zip. I've seen the error mentioned when i searched for a fix but never found a clear solution. Is there a setting I'm missing or a post i should read that i haven't stumbled upon yet? Thanks for any advice or guidance on how to correct this failure. I have attempted to mount the system as well prior to flash and moving the file to my micro-sd to attempt from there.
Click to expand...
Click to collapse
What version of TWRP are you running? If it's current, have you tried reinstalling the recovery itself?
I apologize for the Noob question(s), but does anyone know if the **.zip.md5sum** file as listed below needs to be flashed in conjunction with the actual Rom? If so, do they need to be flashed in a particular order? I haven't been doing so since it appears to be a blank file based on the size. I only ask because ever since switching to OmniRom from GummyRom, my phone seems to get stuck at the Samsung logo screen. About half the time it requires a battery pull because my phone seems to just be stuck at boot. I'm using the latest version of CWM and have read in the Omni thread that switching to the latest version of TWRP resolved the problem. I am just curious if others are or have experienced this problem and what they did to resolve it?
Lastly, I know this is more like a three part question and if I have to post it in another thread I will. But I did try to install TWRP from the Goo Manager app and when the download page loads it doesn't install anything. The page just says it's preparing my download, but doesn't download anything. Any thoughts or suggestions would be greatly appreciated...
I am using a Verizon Galaxy S4
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip 2013-12-08 18:40 193587 KB
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum 2013-12-08 18:40 0 KB
droidzen10 said:
I apologize for the Noob question(s), but does anyone know if the **.zip.md5sum** file as listed below needs to be flashed in conjunction with the actual Rom? If so, do they need to be flashed in a particular order? I haven't been doing so since it appears to be a blank file based on the size. I only ask because ever since switching to OmniRom from GummyRom, my phone seems to get stuck at the Samsung logo screen. About half the time it requires a battery pull because my phone seems to just be stuck at boot. I'm using the latest version of CWM and have read in the Omni thread that switching to the latest version of TWRP resolved the problem. I am just curious if others are or have experienced this problem and what they did to resolve it?
Lastly, I know this is more like a three part question and if I have to post it in another thread I will. But I did try to install TWRP from the Goo Manager app and when the download page loads it doesn't install anything. The page just says it's preparing my download, but doesn't download anything. Any thoughts or suggestions would be greatly appreciated...
I am using a Verizon Galaxy S4
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip 2013-12-08 18:40 193587 KB
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum 2013-12-08 18:40 0 KB
Click to expand...
Click to collapse
First things first, the MD5sum is the checksum of the ROM at buildtime, all you need to do is have this in the same folder as the ROM when flashing and TWRP will verify the checksum of the ROM before installing, so if it is a mismatch it stops you right there.
It should not be flashed.
Its been a while since I used the twrp check-sum someone correct me if wrong.....I verify the MD5 before i put the rom on phone to ensure its a good download.
GooManager has always been flaky on my Skyrocket and on my buddies S3, but that is just me talking, nothing against goomanager. That being said I have always preferred to flash recoveries from the recovery, or odin this ensures (me) that the flash went well.
You can almost always find a zip of the latest recovery for your phone in one of the development threads or you can ask on the S4 Q&A thread if someone has one or if they can get you one. I haven't been to your forum but i'm sure there is a TWRP thread to follow.
OmniRom flashing question
Tweakecho said:
First things first, the MD5sum is the checksum of the ROM at buildtime, all you need to do is have this in the same folder as the ROM when flashing and TWRP will verify the checksum of the ROM before installing, so if it is a mismatch it stops you right there.
It should not be flashed.
Its been a while since I used the twrp check-sum someone correct me if wrong.....I verify the MD5 before i put the rom on phone to ensure its a good download.
GooManager has always been flaky on my Skyrocket and on my buddies S3, but that is just me talking, nothing against goomanager. That being said I have always preferred to flash recoveries from the recovery, or odin this ensures (me) that the flash went well.
You can almost always find a zip of the latest recovery for your phone in one of the development threads or you can ask on the S4 Q&A thread if someone has one or if they can get you one. I haven't been to your forum but i'm sure there is a TWRP thread to follow.
Click to expand...
Click to collapse
Thanks for your answer and suggestion regarding flashing a recovery. I've been doing a lot of reading here on XDA and quite a few have suggested using Flashify to flash recoveries....
Tweakecho said:
First things first, the MD5sum is the checksum of the ROM at buildtime, all you need to do is have this in the same folder as the ROM when flashing and TWRP will verify the checksum of the ROM before installing, so if it is a mismatch it stops you right there.
Click to expand...
Click to collapse
It doesn't work that way for me. I always put the files in the same folder but TWRP 2.6.3.3 always says that there is no md5 file to be found.
Riiquiem said:
It doesn't work that way for me. I always put the files in the same folder but TWRP 2.6.3.3 always says that there is no md5 file to be found.
Click to expand...
Click to collapse
It's because the file extension is wrong.
Zip md5 Verification (looks for file with zipname.zip.md5)
So, if you downloaded these files :
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum
You need to rename "omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum" to "omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5".
AngryHapposai said:
It's because the file extension is wrong.
Zip md5 Verification (looks for file with zipname.zip.md5)
So, if you downloaded these files :
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum
You need to rename "omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum" to "omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5".
Click to expand...
Click to collapse
That explains why mine always reports an error as well. *fixes all future build md5's
Having the same problem MD5 not found while flashing ROM. lemme try renaming. Will say again, if its work
Ok so before I start I did try to put this on the developers page but I haven't made enough posts yet so it didn't let me .... I am having lots of problems with my Canadian Samsung galaxy s4 sgh 1337m .... I don't even know where to start .. first off im rooted so I have that covered I know that for a fact I also have team win recovery project ... now I want to rom buy my phone will NOT allow me to do it ... I will go online I will download the rom and the Gapps directly to my internal storage ... il go into it il do the whole wipe cache and Delvik and then factory reset .. then ill flash the rom and the Gapps and it says failed to flash the rom but the Gapps are successful .. I then flash my backup and proceed with my day .... YES I am downloading them for the correct device .... why is this happening ?? in my last post someone replied my Twrp may be out dated so I went onto my new computer and tried to install Odin again so I could flash the new Twrp to my device and my computer wont let me open Odin its a new windows 8 and it WILL NOT open it it gives me some Chinese letters and closes ... Why is this happening to me ?? why cant I open Odin or download Roms to my phone ... I've watched numerous instruction videos and it works perfectly for everyone accept for me .. someone please help me .... if my issue is resolved I will be donating to XDA .... this issue has been ongoing for weeks .
have you verified the md5 sum of your downloads?
also what backup method did you use?
muskratt said:
have you verified the md5 sum of your downloads?
also what backup method did you use?[/QUOTE
What is the whole verify thing your telling me about ive never had to do it before on other devices its just been simple .... also I use team win recovery project to create my backups
Click to expand...
Click to collapse
Lets start with what rom are you trying to flash? I noticed you are trying to flash gapps.....so I take it you are trying to flash a aosp rom.
Timtim1234321 said:
muskratt said:
have you verified the md5 sum of your downloads?
also what backup method did you use?[/QUOTE
What is the whole verify thing your telling me about ive never had to do it before on other devices its just been simple .... also I use team win recovery project to create my backups
Click to expand...
Click to collapse
Most roms provide an md5 number to verify a good download. It is a checksum that tells you the download is good. Get a file explorer like FX Explorer. Long press on rom you downloaded and then open details. It will have selection to do a checksum. The number should match the one from the rom site where you downloaded it from. Very common to get a bad download from time to time. You can also use terminal on pc, if you familiar with that and have adb on your pc. I prefer that method. I do it as soon as download to rom to pc.
Also, what version twrp are you on. Most prefer 2.5.0.2. This is a flashable zip for it.
https://www.dropbox.com/sh/yhrq0tia8512rj9/FCjN8C9RMT/TWRP_Flashable-2.5.0.2.zip
Flash thru your current twrp recovery. Unless you already have 2.5.0.2 or the very latest twrp seems ok. On 2.5.0.2 don't ever do a format where you have to type "yes" to comfirm format.
I always wipe thru the Advanced menu manually. I wipe System/Data/Caches 3x. Always do that flashing new roms on new versions to a rom, unless dev says otherwise. Or, on CM Nightlies. Even then it doesn't hurt to do a full wipe on occasion. Crap can build up over time dirty flashing and cause issues.
As Ax said, unless you are flashing a CM roms, no need for gapps. Also, depending on rom you are flashing you may need to flash your carriers kernel after rom.
So, more info may be needed to help you--:good:
Click to expand...
Click to collapse
Hi XDA,
Before I decided to open this topic I've read through several topics, but I can't seem to find out what I am doing wrong. I hope that opening this thread will help me solving my problem.
I have a Dutch Samsung Galaxy S4 (i9505) running Android 5.0.1 Lollipop using the Nova launcher, but I'd like to install a ROM for new features and better battery life. After looking around in the development forum I found two interesting ROMs which I wanted to try out. These are the following:
http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-imperium-ll-v1-0-t3046889
Or
http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-albe95-s6-port-1-0-t3092479
I downloaded the zip file from the first ROM listed and copied it to my SD-card
Both seemed like decent ROMs. I looked up how to root my phone and found out that by using Odin this was pretty easy. After rooting my phone I used QuickBoot to enter Recovery mode. After wiping the DATA I chose update through SD Card > selected the zip file and thought it would install from that moment.
After waiting several minutes the ROM seemed to be installed, the phone rebooted itself and after seeing the swingy SAMSUNG logo it said SYSTEM-UI has stopped. I was able to use all functions, aside from the taskbar, homebutton and backbutton. Also, it seemed like nothing changed? My phone was exactly the same, aside from the fact that my background was black.
I am confused where I am making a mistake by installing either ROM. Can anyone point me out where I make the mistake and tell me how to solve my problem.
Thank you.
If there's any other info neccesary please don't hesitate to ask, i'm happy to provide!
Did you actually install any custom recovery?
You need a custom recovery to install any custom roms. It won't work with the stock recovery.
I'd recommend TWRP recovery. It can also be installed via Odin.
I did, but maybe something went wrong. I am back on the normal ROM now, just rooted the device using http://forum.xda-developers.com/showthread.php?t=2219803 this thread.
I Will try installing twrp again. Can I use one of the following despite not being in the USA? How do I know for sure?
Samsung Galaxy S4 AT&T (jflteatt)
Samsung Galaxy S4 Canada (jfltecan)
Samsung Galaxy S4 Cricket (jfltecri)
Samsung Galaxy S4 C-Spire (jfltespi)
Samsung Galaxy S4 Google Edition (jgedlte)
Samsung Galaxy S4 International Exynos (i9500)
Ok, installed TWRP and copied the zip files to both my SD card as well as the internal hd, going to install, finding the zip files, swipe to install. Following happens:
Installing '/external_sd/imperium_ll_blabla.zip
Checking for MD5 file
Skipping MD5 chekc: no MD5 file found
Verifying zip signature
E: Zip signature verification failed: 1
FAILEd.
I'm confused.
mess89 said:
Ok, installed TWRP and copied the zip files to both my SD card as well as the internal hd, going to install, finding the zip files, swipe to install. Following happens:
Installing '/external_sd/imperium_ll_blabla.zip
Checking for MD5 file
Skipping MD5 chekc: no MD5 file found
Verifying zip signature
E: Zip signature verification failed: 1
FAILEd.
I'm confused.
Click to expand...
Click to collapse
Disable zip signature verification and try again.
Make sure you use the latest TWRP recovery. CWM and Philz are highly outdated.
Thanks for the tips guys. I will try on sunday, don't want to mess with my phone during birthday parties
I will let you know about the results.
Please do a clean flash when you're installing a new ROM.
Clean as in delete cache, dalvik, system, and if needed, internal storage.
krasCGQ said:
Disable zip signature verification and try again.
Click to expand...
Click to collapse
That's where I went wrong, thanks guys!
So I am trying to install a new rom (On The Edge) as this week I have been installing and trying all the different roms for fun to see which one I like the most and to learn.
When I go to install version 6 beta 2 of (https://forum.xda-developers.com/s7-edge/development/fastupdates-ontheedgelite-ux-v1-t3401348) the 2gb zip fails to flash "could not extract 'META-INF/com/google/android/update-binary'" Error installing the zip file. I have not seen this before even after installing all the different roms I have this week.
I tried installing 5.6 and that one seemed to flash install correctly and the wizard showed so I am at a loss. Others are reporting they can install version 6 without issues. Is there something I am missing on how to flash this thing?
the files might be corrupt...
That was my first thought so I re-downloaded and transferred it to my phone again but got the same issue. Others have said they are able to flash it which is why I assumed maybe there is something special I need to do that is not obvious.