I rooted my One and installed the latest version of TWRP on it last night and tried to flash CM 10.2 Stable on it. I kept getting the "Failed" message so I went ahead and made a stupid move and wiped EVERYTHING including internal storage. I ADB pushed Gummy ROM and a couple different versions of CM 10.2 but I keep getting "E:Unable to open zip file. Error flashing zip '/sdcard/ROM.zip'" Can someone tell me what I'm doing wrong? It's nearly 11am and I've gotten no sleep trying to find out how to fix this.
EDIT: PROBLEM SOLVED! All of the files I downloaded were corrupted. After redownloading them on a different computer the ROM flashed fine.
Related
I tried to do a search for this problem but search isn't working on XDA right now... So my problem is that I was trying to update my Hellybean ROM and when I wiped I must have wiped something I shouldn't have. The newest ROM was saved to my internal SD and after wiping it wouldn't reboot into TWRP so I tried CWM, which it did boot into but wouldn't load the old version of Hellybean on my ext sd. I tried to load a .tar file through ODIN to get the phone going again but it keeps failing when trying to load the MTP USB drives, so I am stuck! Anyone know what the problem might be?
I should add, when loading a tar file through ODIN, the phone reboots through the initial Samsung logo then goes to another and gets stuck there. I am thinking that it is not loading all of the files because of the USB drive not being installed?
You might try grabbing the modified CWM file from BlownFuze's AOKP thread and flashing it from your ext sd card. It will flash the newest roms. If all else fails you could try the emergency firmware recovery in Kies.
ovennon sus
Really now said:
You might try grabbing the modified CWM file from BlownFuze's AOKP thread and flashing it from your ext sd card. It will flash the newest roms. If all else fails you could try the emergency firmware recovery in Kies.
Click to expand...
Click to collapse
Through CWM it will see a couple of rom's on the ext sd but I get an error when it starts to flash. I tried Kies but when I plug in the USB it doesn't see the phone. I don't think it's bricked as I can get into download mode and cwm??
After getting some sleep I thought about what I did yesterday when flashing the rom. I had a longggg day at work and was tired and after wiping the phone I think I rebooted it before flashing the rom, I am almost positive I did that. It will be the last time I flash after a long, tiring day! Anyone ever reboot the phone after a wipe without flashing a rom first?
I don't know what tar file you were flashing thru odin but I do know when you flash back to stock it always hangs up on the first boot. Then you have to go into recovery and do a factory reset and boot up again. BlownFuze posted a handy guide on flashing the stock rom back in June. You might have a look at that and see if it's any help. http://forum.xda-developers.com/showpost.php?p=42806745&postcount=360
I got it figured out and fixed... the version of CWM was an old one, uploaded the newest one and got everything reloaded!!
Glad to hear that. Seems like the 4.3 roms are a bit more finicky about the recovery version you're on.
Really now said:
Glad to hear that. Seems like the 4.3 roms are a bit more finicky about the recovery version you're on.
Click to expand...
Click to collapse
I pulled a LOT of hairs out yesterday trying to figure it out, and it was such a simple fix! Thanks for your help!!!!
I'm glad I could give a little help. Happy flashing! :laugh:
Some months ago I was flashing nightly and non stable zip. If you loose AOSP keyboard, Ok. At some point, after IOKP 4.3.1. flash, not beanstalk or even hellkat which I could not install, ALL ROM FAILED, all gapps idem.I only had a backup of IOKP and it isntall. TWRP 2.6.4.0 .img flashed by Odin 1.85 saved me once.
This time I felt unstability over several processes and only gave one order, reboot recovery. It all blaked, samsung in an out
Tried .tar of phielz touch, CMW. TWRP above refered showed itself but whem I thought the backup was over, it seems the OS was missing...
Now after flashing The new version of TWRP for t0lte I got nothing.
I know nothing of programming, code or whatsoever.
If somebody could give some suggestions that can help...:crying:
I have an MDK S4 and have been flashing custom roms all along.
It had been like a whole week since my last flash so I downloaded Chaos rom and wiped my data and went to install it just like I've done 100 times before with other roms. When I swipped on install it came up with a red "Failed" message. I thought this was odd, but I've had it happen before with corrupt/incomplete/errored downloads.
Since I had already wiped I went to go do a fresh install of the basic NG2 rom I was on prior to wiping and got another "Failed" message.
Flashed my recovery image (which thankfully worked.) I repeated the whole wiping/attempting to flash/restoring my recovery image cycle again hoping it would work the second time around... which it left me back on my recovery image.
Not sure what went wrong. Tried to update TWRP to a newer version through goo manager, but that doesn't seem to be working either.
Thoughts?
Worked perfectly. Thanks!
Hello, so I was running CM10 on my Fascinate for a couple months, but I decided to boot into recovery one day and I say got the error messages unable to mount to cache, etc. So I decided to start from scratch with the stock rom. Then I decided to flash CM7, but I kept on getting into a bootloop where it loops "waiting for sd to mount (20s), (19s), etc. So I decided to try out CM10 again or CM11, but then I kept on getting the warning: No file_contexts in CWM 6.0.3.3 when you try to flash CM10 and it doesn't even flash CM11. So I'm wondering what am I doing wrong. I currently have the files:
I tried the method with teamhacksung which works, but CWM brings back the errors that I had to begin with and I'm unable to update to CM11 through teamhacksung
atlas_v2.2.pit
CI500_VZW_EH03_BM_CM.tar.md5
CM-7.2.0-fascinatemtd.zip
cm-10.1-20130723_Nightly-fascinatemtd.zip
cm-11-2014-221_UNOFFICIAL-fascinatemtd.zip
cwm4_fixed_for_cm7_ODIN.tar
teamhacksung_fascinatemtd-ota-eng.BUILD1.zip
Any help would be greatly appreciated.
Hi there, i'm writing this in hopes of someone reading it who give me some pointers.
i was running for the last years on CM 10.2.1 but i thought it was time for an update. update to CM 11.2 worked but my installed apps were making some weird troubles so i decided to do a factory reset and there my trouble started.
i flashed to boot.img in fastboot, cleared cache with fastboot cmd
format \system, \data, \cache and of course dalvik
flashed rom CM 11.2 (from official cyanogenmod site) via recovery sideload
rebooted and as my thread title says was stuck on CM boot sequence
i tried different CM roms, but always the same result. system wont end the bootup.
i even suspected a problem with CMW v6.0.4.8 and flashed TWRP from the CM 12.1 thread here in the forum.
so in short i can flash boot.img, recovery, different roms but in the end can't get it to work.
i would really appreciate some hints what i could do differently or maybe were i go wrong.
if you need more info i'm happy to supply them to you.
Thanks in advance.
solved by installing a TWRP backup and boot.img what i found on a german android site.
i was also able after that to install CM 12.1 unofficial and its running now. but i'm totally stumped what caused this weird problem to begin with. doesn't really matter now, i'm relieved it worked in the end.