Related
I have Flashed Warm 2.2 and wanted to flash the new one Warm Z but having some issues.
Everytime i try to flash it stops and states bad
done this as well with MikFroyo 4.5 as well
both will not flash
I had some problems going into recovery earlier but i reflashed Clockworld then RA and i am now good with recovery. but can not flash any roms any help would be nice
what ra version?
what error message do you get?
Heading out to get some nom noms, but try toggling off signature verification, or re-download the rom.
NewZJ said:
what ra version?
what error message do you get?
Click to expand...
Click to collapse
RA ver.2.3
Error
E:Can't open /sdcard/mikfroyo-v4.5-signed.zip
(bad)
and yes i disabled sig. verify and enabled it and same error also tried mounting /sdcard
Also wanna add that i can open the zip files fine from my PC, I just also tried a kernal and got the same message i guess its any zip file so far,
I also had this problem with Clockworld 3.0.0.5
Thanks
Try re-downloading it. Seems something is wrong with the file
i tried redownloading two different pc's formatting memory cards you name it i keep getting a problem same saying img is bad no matter what i try to flash
I don't know why its not working, but that error is related tot he actual file itself. Do you have a crappy internet connection?
teh roxxorz said:
I don't know why its not working, but that error is related tot he actual file itself. Do you have a crappy internet connection?
Click to expand...
Click to collapse
Ditto... Make sure you are getting the full file. Also make sure you are not just doing a quick wipe of your SD card. Do a full wipe and repair, it's worth the time, trust me.
my internet connection is good, what software should i use to do a full wipe/repair
Hi guys. I have a huge problem. Few minutes ago I tried to install CyanogenMod 7.2-GIO-KANG by use CWM v5.0.2.7. Everything appeared to be ok, but when phone reboot I just can see white word ANDROID on a black background and nothing more. Phone just stop on this screen. Is there any resolution for my problem? I modded lot of phones, this is my first crash. Thx for every advice. Bye
Same issue. Is there a way to restore to stock firmware without odin? Such as from the recovery console?
If before you had an official rom, you must use the ext4 formatter. I think you'll find it in the thread! Hope to be useful
Sent from CM9 Gio with the XDA app v.v
i've noticed sometimes is does take a minute or two to get past that screen.
tooviral
Now I have a new problem, it no longer allows me to boot the device, it displays an image of a phone connected to a pc. Does this mean I have to flash in odin?
gruntlord6 said:
Now I have a new problem, it no longer allows me to boot the device, it displays an image of a phone connected to a pc. Does this mean I have to flash in odin?
Click to expand...
Click to collapse
Happened to me once, I just found a stock rom and flashed with odin. Since I've put cwm recovery I've backed up and haven't had a prob since
tooviral
tooviral said:
Happened to me once, I just found a stock rom and flashed with odin. Since I've put cwm recovery I've backed up and haven't had a prob since
tooviral
Click to expand...
Click to collapse
Well as you can tell I am new to android, I tried using odin with a stock rom I found on this site, but I keep getting the error:"an unnamed file was not found"
gruntlord6 said:
Well as you can tell I am new to android, I tried using odin with a stock rom I found on this site, but I keep getting the error:"an unnamed file was not found"
Click to expand...
Click to collapse
Have you downloaded gio_v1.0.ops?
That may cause the "an unnamed file was not found" problem
all you need to do is "wipe data/factory reset" ... i didn't use any ext4-formatter and it works well..
matt_galaxygio said:
Have you downloaded gio_v1.0.ops?
That may cause the "an unnamed file was not found" problem
Click to expand...
Click to collapse
That helps, but now it tells me "cannot open the usb serial port. code: 2"
Edit: Never mind, found out it was kies conflicting. Thanks for the help!
Ok, I used odin and newest stock rom. Now the phone is working fine, like new Thx for all advices guys, that was really helpful. Cya
I have this issue too.
Im new to android but I followed the thread, I:
Root
install CWM, then nandroid backup
flash CM7 in CWM
I downloaded the CM7 KANG file and tried several times, thinking file might be corrupt. Same problem.
Unfortunately my backup didn't work, so I'm ordering a Jig to fix my phone.
But I'd like to know what went wrong.
I didnt reformat my SD card with 4ext though, should I have?
Thanks
tioammar said:
all you need to do is "wipe data/factory reset" ... i didn't use any ext4-formatter and it works well..
Click to expand...
Click to collapse
I tried this and it didnt work for me
im not a noob and never had thid problem in years. i installed twrp through goo mananger. The weird thing is it installs kernels just fine, but not a rom, any ideas? please help
Luthien1 said:
im not a noob and never had thid problem in years. i installed twrp through goo mananger. The weird thing is it installs kernels just fine, but not a rom, any ideas? please help
Click to expand...
Click to collapse
What error does it give when it fails to flash a ROM? What ROM are you trying to flash?
lordcheeto03 said:
What error does it give when it fails to flash a ROM? What ROM are you trying to flash?
Click to expand...
Click to collapse
it says e error, its very strange, i tried installing cwm and that recovery wont even let me make a backup, this is terrible uhhh... sorry it just says E: error and doesnt say anything else
Luthien1 said:
it says e error, its very strange, i tried installing cwm and that recovery wont even let me make a backup, this is terrible uhhh... sorry it just says E: error and doesnt say anything else
Click to expand...
Click to collapse
It says E: error when you try to make a backup as well?
lordcheeto03 said:
It says E: error when you try to make a backup as well?
Click to expand...
Click to collapse
ok i had twrp through goo manager, and i was able to make backups and install kernels just finel but when i tried a rom such as infamous it gave me the error, so i tried to install through micro sd card, no luck same error something about it not being mounted. So, i installed cwm and tried to make a backup but then i ran out of space, so the backup failed, so i had to delete some stuff, now im trying to back up again, then i will try to install a rom with cwm
this is so strange, i didnt do anytihng out of the ordinary, i got root by chainfire, then installed goo manager, and then a custom kernel...the most viewed one right now, so i thought it was legit which im sure it is, then a rom..... to end the madness, then i keep getting errors, its so frustrating
Luthien1 said:
ok i had twrp through goo manager, and i was able to make backups and install kernels just finel but when i tried a rom such as infamous it gave me the error, so i tried to install through micro sd card, no luck same error something about it not being mounted. So, i installed cwm and tried to make a backup but then i ran out of space, so the backup failed, so i had to delete some stuff, now im trying to back up again, then i will try to install a rom with cwm
Click to expand...
Click to collapse
Ok, see, now that is getting to the meat. Try flashing another ROM... I understand you might just want Infamous, but try flashing another one just for testing purposes. I'm thinking you're one to add to the list of having a bad Infamous d/l.
lordcheeto03 said:
Ok, see, now that is getting to the meat. Try flashing another ROM... I understand you might just want Infamous, but try flashing another one just for testing purposes. I'm thinking you're one to add to the list of having a bad Infamous d/l.
Click to expand...
Click to collapse
i did i tried flashing jedi rom and that failed too, soo this is just weird
i got frusturated and said if i cant have a custom rom, ill debloat now im getting errors, im on my way to a bricked device
Luthien1 said:
i got frusturated and said if i cant have a custom rom, ill debloat now im getting errors, im on my way to a bricked device
Click to expand...
Click to collapse
I may be overboard with my suggestion, but it wouldn't hurt to Odin back to 100% stock and restart your journey.
now it says E cant open/sdcard/o/download/jedi(bad)
Luthien1 said:
now it says E cant open/sdcard/o/download/jedi(bad)
Click to expand...
Click to collapse
Before you Odin back; are you still able to successfully flash any of the kernels you've downloaded? Also, if you downloaded any of the ROMs onto your computer, try browsing through the zips real quick on your computer.
lordcheeto03 said:
Before you Odin back; are you still able to successfully flash any of the kernels you've downloaded? Also, if you downloaded any of the ROMs onto your computer, try browsing through the zips real quick on your computer.
Click to expand...
Click to collapse
yes i can install kernels just fine, just not roms... it says it cant open the zip file, so weird.....i think i need to odin completely back too
Luthien1 said:
yes i can install kernels just fine, just not roms... it says it cant open the zip file, so weird.....i think i need to odin completely back too
Click to expand...
Click to collapse
Slow down, re-group, you are NOT going to brick...
First off, lets try some things, my first would be try a different recovery, copy a rom you want to the internal sdcard, then try. Bet it works.
I had a issue like this also, day 2 of my g4, pull the battery for 5-10 min, it seems the recovery gets confused and it will error.
another item to try...check to make sure the md5 file size is correct. common mistake, people for get to do a check.
try these, if you have the same issues, odin back to stock and start over.
Good luck. Your welcome.
lordcheeto03 said:
I may be overboard with my suggestion, but it wouldn't hurt to Odin back to 100% stock and restart your journey.
Click to expand...
Click to collapse
Probably this...and a formatting of the internal storage couldn't hurt either to make sure everything is cleared out.
Hey I had same problem. Download through Firefox not reg browser. And for infamous use the last download link
Goomanger gave me 3 bad downloads. To test this theory try and open the zip through a file manager, it probably won't let you because of bad download.. Happened to me 4 times but stopped using stock browser to download those files and has been working ever since
Sent from my SGH-M919 using XDA Premium HD app
---------- Post added at 10:54 AM ---------- Previous post was at 10:50 AM ----------
Also if you can't flash most things from more than 1 recovery still(happened to me when first got my gs4) I did Odin again but used 2.5.0.2 twrp and everything fixed as well. I recently was having the problem you have now and my first suggestion fixed it
Sent from my SGH-M919 using XDA Premium HD app
so, thank you everyone for your replys in this matter. I did odin back to stock and guess what, i got stuck at the splash screen for t mobile. This never happened before with odin, it always worked 100 percent, this is the first time i odined back to stock and it broke my phone, so weird. So, im going to try again. I wil def use firefox next time, and twrp you said the latest is having problems?
Luthien1 said:
so, thank you everyone for your replys in this matter. I did odin back to stock and guess what, i got stuck at the splash screen for t mobile. This never happened before with odin, it always worked 100 percent, this is the first time i odined back to stock and it broke my phone, so weird. So, im going to try again. I wil def use firefox next time, and twrp you said the latest is having problems?
Click to expand...
Click to collapse
Might want to thank people for the effort...there is a thanks button
get into recovery now, and do a factory reset, flash the correct kernel for your device, it will boot.
Hey guys, I have a serious problem and need my phone for work...
I downloaded multi rom update, was already running it... i was going to do a clean install and wiped everything... now when I try and flash it, it says failed... I still had the previous version of the rom and and tried to flash that and it failed as well, now I am stuck in TWRP and I scared to try and reboot.
Please help and fast
Also I didn't realize that i had an old version of jelly bomb but it failed as well
Try rebooting recovery. Then your normal wipe and flash process.
Sent from my SPH-L900 using Tapatalk 2
mike.too.cool said:
Hey guys, I have a serious problem and need my phone for work...
I downloaded multi rom update, was already running it... i was going to do a clean install and wiped everything... now when I try and flash it, it says failed... I still had the previous version of the rom and and tried to flash that and it failed as well, now I am stuck in TWRP and I scared to try and reboot.
Please help and fast
Also I didn't realize that i had an old version of jelly bomb but it failed as well
Click to expand...
Click to collapse
Pull battery and start over.
I pulled out the battery and tried it again but it is still not working. Is there any way to connect my phone to a computer with no ROM so that I can attempt another ROM? I have tried but cant figure out how to access the files
mike.too.cool said:
I pulled out the battery and tried it again but it is still not working. Is there any way to connect my phone to a computer with no ROM so that I can attempt another ROM? I have tried but cant figure out how to access the files
Click to expand...
Click to collapse
you use twrp? make sure you havent clicked a box that asked for a signature that can make it fail if i remember right.take a look around in recovery for a bit and see what you can find
mike.too.cool said:
I pulled out the battery and tried it again but it is still not working. Is there any way to connect my phone to a computer with no ROM so that I can attempt another ROM? I have tried but cant figure out how to access the files
Click to expand...
Click to collapse
you might want to try using one of the "one-click" ODIN files to get back to rooted stock, if anyone elses advice fail you.
patrao_n said:
Try rebooting recovery. Then your normal wipe and flash process.
Click to expand...
Click to collapse
for future ref, always remember this step. srsly.
evolving said:
you use twrp? make sure you havent clicked a box that asked for a signature that can make it fail if i remember right.take a look around in recovery for a bit and see what you can find
Click to expand...
Click to collapse
go into settings tab and make sure nothing is checked
Evolving thanks, you are a pro! the first option was checked, I think it had to do with a signature, anyways thanks I am no longer stressed!:good:
mike.too.cool said:
Evolving thanks, you are a pro! the first option was checked, I think it had to do with a signature, anyways thanks I am no longer stressed!:good:
Click to expand...
Click to collapse
far from a pro my man just spend to much time on xda.glad i could help.
T989 without any SD card in it, the one I had died apparently new one on order. Went to flash the latest PA rom but kept getting error 7 using CWM. I updated my recovery to the latest TWRP and still will not flash. I tried updating to the newest radio UVMC6, but that wont flash. I am currently on CM10.1 nightly. My process for flashing is recovery, superwipe, flash, which is when the flash errors out and I re wipe and then I can flash my CM10 back on. So I can flash CM10 all day long but nothing else. I searched on here and found that the ATT version of this phone has this problem and you have to flash an AOKP and then flash whatever you want, other phones with similar problems say use ODIN and flash stock and then go from there. I am just looking for any advice on this situation. I could not find anything specific enough in my search to help me and I am hoping someone here can. Thanks in advance.
Note: I have also tried flashing CM10.1 RC5 and has the same problems.
moebawlz said:
T989 without any SD card in it, the one I had died apparently new one on order. Went to flash the latest PA rom but kept getting error 7 using CWM. I updated my recovery to the latest TWRP and still will not flash. I tried updating to the newest radio UVMC6, but that wont flash. I am currently on CM10.1 nightly. My process for flashing is recovery, superwipe, flash, which is when the flash errors out and I re wipe and then I can flash my CM10 back on. So I can flash CM10 all day long but nothing else. I searched on here and found that the ATT version of this phone has this problem and you have to flash an AOKP and then flash whatever you want, other phones with similar problems say use ODIN and flash stock and then go from there. I am just looking for any advice on this situation. I could not find anything specific enough in my search to help me and I am hoping someone here can. Thanks in advance.
Note: I have also tried flashing CM10.1 RC5 and has the same problems.
Click to expand...
Click to collapse
For onw those superwipe scripts are not needed with twrp, u might be getting the error from that, are u trying to flash from internal SD card since ur external died? That might cause it but I don't think so, I would suggest trying a manual wipe of all partitions, data, system, cache, dalvik, 2x , then flash, if that doesn't work try using Odin, go back to stock and start over, that should fix it definetly
Sent from my SGH-T989 using xda premium
soupysoup said:
For onw those superwipe scripts are not needed with twrp, u might be getting the error from that, are u trying to flash from internal SD card since ur external died? That might cause it but I don't think so, I would suggest trying a manual wipe of all partitions, data, system, cache, dalvik, 2x , then flash, if that doesn't work try using Odin, go back to stock and start over, that should fix it definetly
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Thank you... I wasnt sure about superwipe on TWRP since I just put it on and came from CWM. I am trying to flash from the internal card and the new external card will be at my doorstep tomorrow so I will drop that in as well. I will drop back in once I get all this done and hopefully all goes well.
Again thanks.
moebawlz said:
Thank you... I wasnt sure about superwipe on TWRP since I just put it on and came from CWM. I am trying to flash from the internal card and the new external card will be at my doorstep tomorrow so I will drop that in as well. I will drop back in once I get all this done and hopefully all goes well.
Again thanks.
Click to expand...
Click to collapse
Good glad I can help, let me know how it all goes, now I'm interested lol
Sent from my SAMSUNG-SGH-T989 using xda premium
Ok so I got my new SD card. Tossed that in, just figured I would try flashing from the external, no luck there. Same issues.
Odin back to stock using this tutorial http://forum.xda-developers.com/showthread.php?t=1513359&page=3
Used http://forum.xda-developers.com/showthread.php?t=2195283 this to regain root.
Got CWM back on but now I cannot flash SuperUser
When I go to flash Superuser it says
Mounting System
Deleting System:bin/su...
Deleting System:xbin/su
Extracting files to SYSTEM
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
E: Error in /emmc/Superuser-3.0.7-efghi-signed.zip
(Status 0)
Installation aborted
So on the plus side I didn't brick the phone... downside now I am back to Gingerbread and currently stuck here...
Possibly a bad zip file?
Any ideas on this?
Quick update... I am a moron... Did not realize that root is kept with this restore... Got Superuser from market and am good to go.
Installing TWRP now and will have an update on the flash soon.
OK... the fun seems to have just begun
I cannot install TWRP from GooManager. No clue why, looking on here and I found //techerrata.com/browse/twrp2/hercules (cant link too new of a member)
So as it seems I can download the .img and GooManager should see it and if that doesnt happen I can install it through the terminal with these commands
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
OR flash it with ODIN... Which I would assume I get the .tar file and follow the same process as putting the recovery files in?
Aside from TWRP being an issue, I tried installing the PA rom with CWM and I got this:
Installing update
set_perm:some changes failed
E:Error in /sdcard/pa_hercule...zip
(Status 7)
Installation aborted
The same error I had in the first place
moebawlz said:
OK... the fun seems to have just begun
I cannot install TWRP from GooManager. No clue why, looking on here and I found //techerrata.com/browse/twrp2/hercules (cant link too new of a member)
So as it seems I can download the .img and GooManager should see it and if that doesnt happen I can install it through the terminal with these commands
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
OR flash it with ODIN... Which I would assume I get the .tar file and follow the same process as putting the recovery files in?
Aside from TWRP being an issue, I tried installing the PA rom with CWM and I got this:
Installing update
set_perm:some changes failed
E:Error in /sdcard/pa_hercule...zip
(Status 7)
Installation aborted
The same error I had in the first place
Click to expand...
Click to collapse
I'm not sure what your overall problem is, but if you are going to install TWRP do not use Goo Manager or the img file. They have been messing up peoples phones. Odin the tar or try the zip from the TWRP thread.
meekrawb said:
I'm not sure what your overall problem is, but if you are going to install TWRP do not use Goo Manager or the img file. They have been messing up peoples phones. Odin the tar or try the zip from the TWRP thread.
Click to expand...
Click to collapse
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Along with that after I got TWRP working through Goo Manager again I tried flashing PA again and I had the same error as I did in the first place.
Maybe my phone just hates anything but the nightly I had before...
moebawlz said:
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Click to expand...
Click to collapse
If you can boot into TWRP, then they must have fixed the Goo problem.
It seems like you have tried most everything. Maybe you should Odin back to stock. If you are comfortable doing it, that is.
i went to flash with goo last night and it bricked the phone kind of, i had to ODIN and reflash the CWM again and bam the phone rebooted no problem
meekrawb said:
If you can boot into TWRP, then they must have fixed the Goo problem.
It seems like you have tried most everything. Maybe you should Odin back to stock. If you are comfortable doing it, that is.
Click to expand...
Click to collapse
I did Odin back to stock before. I am still on stock gingerbread right now with root access and am getting the errors I have been. I followed the tutorials in the sticky thread that I posted before that got me back to stock.
Within TWRP I tried installing the newest Cyanogen Mod and got
E:Error executing updater binary in zip
Error flashing zip
When I try installing the PA rom I get the same error
Any thoughts? Would going back to stock through Odin and doing this again potentially fix it? or is that a shot in the dark?
Lucky for me I kept a backup saved on my PC from before I did anything here. So I am back to the CM 10.1 Nightly I started on for the time being.
Is there any other method of flashing a rom that I might be able to try?
moebawlz said:
I did Odin back to stock before. I am still on stock gingerbread right now with root access and am getting the errors I have been. I followed the tutorials in the sticky thread that I posted before that got me back to stock.
Within TWRP I tried installing the newest Cyanogen Mod and got
E:Error executing updater binary in zip
Error flashing zip
When I try installing the PA rom I get the same error
Any thoughts? Would going back to stock through Odin and doing this again potentially fix it? or is that a shot in the dark?
Click to expand...
Click to collapse
It would be a shot in the dark. I did a Google search for your error and a couple of people said they were able to fix it by using TWRP 2.3. That was for different phones though. Maybe try that before going stock.
I am by no means a pro at this and am still learning as I go. Just to make sure of what I am doing, can I Odin TWRP 2.3? I also found this
http://forum.xda-developers.com/showthread.php?t=1639673
or
http://forum.xda-developers.com/showthread.php?t=1658418
Just a thought here... I keep gettin emmc errors... I was reading about upgrading and downgrading TWRP through the Terminal Emulator and it said use emmc or sdcard depending on what the phone reads it as.
When I first got the phone i recall seeing emmc when i would go into any file browser. Now it just says sdcard0 (internal) & sdcard1 (external)
So how can I get recovery to stop looking for emmc and start looking for sdcard0?
Unless I am way off in left field here with this.
moebawlz said:
I am by no means a pro at this and am still learning as I go. Just to make sure of what I am doing, can I Odin TWRP 2.3?
Click to expand...
Click to collapse
Yes, use Odin and the 2.3.3.0 tar from the techerrata website. I like using the Odin method because I have never had a problem upgrading recovery that way. I don't know about the emmc errors because I have only used the dd method like twice.
Edit: Maybe your internal memory is corrupted? I'm not sure how to test for that though.
moebawlz said:
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Along with that after I got TWRP working through Goo Manager again I tried flashing PA again and I had the same error as I did in the first place.
Maybe my phone just hates anything but the nightly I had before...
Click to expand...
Click to collapse
I think u must be getting bad DL then because none of that sounds right lol, if u got twrp to load into your device and all is working fine then the only other option is a bad DL, try checking the DL with a root browser or something to see the size of the file, status 7 errors are from the zip, usually bad install script in the ROM, which could be caused by a bad DL, check the DL size and let me know
Sent from my SGH-T989 using xda premium
went back to 2.3.3 and still having the same error.
Is there a way to correct any possible errors in my internal memory?
moebawlz said:
went back to 2.3.3 and still having the same error.
Is there a way to correct any possible errors in my internal memory?
Click to expand...
Click to collapse
If the DL is good, I don't know what else to tell u that is very strange indeed, but interesting too, I've never not been able to install at all, I'm curious..
Sent from my SGH-T989 using xda premium