I'm very confused as to what happened, and feel like I'm only making things worse so decided to come here. I've been rooted for about 2 months now after using Unrevoked Forever, and until last week everything was fine.
Using Rom Manager I attempted to flash Salvage Mod coming from Cyanogen 6.1.2. After wiping Data/Cache, when going to open the Zip Clockwork told me that the Rom did not exist in my SD card?
I redownloaded and tried again several times with no luck. I tried downloading other ROMS through my computer and putting them directly on my card and now I'm getting an error saying the Zip files are "(bad)"
Flashed RA Recovery through Rom Manager, the same errors, and now flashing back to Clockwork won't work. Any ideas what the problem maybe? Any solutions would be greatly appreciated
Have you tried booting to recovery directly and flashing a rom? I personally use CWM 2.6 and prefer to do all the work myself through recovery instead of hoping RomManager gets it right.
Yes I've tried booting into Recovery myself, keep getting the error that the zip. is bad
Related
Okay so i had CM6.1.1 flashed onto my evo and everything was working fine. i installed the new version of clockwork mod on my phone and i found something else i wanted to flash. i tried to reboot my phone and now everything force closes. and i mean EVERYTHING! i tried to restore all of my backups and none are working. can anyone help?
dude what i just did was go to rom manager and scroll all the way down flash alternate recovery and after its installed go and tap om clockworkmod recoveries and install the 2.5.0.1 and your good to go !!
JJS714 said:
Okay so i had CM6.1.1 flashed onto my evo and everything was working fine. i installed the new version of clockwork mod on my phone and i found something else i wanted to flash. i tried to reboot my phone and now everything force closes. and i mean EVERYTHING! i tried to restore all of my backups and none are working. can anyone help?
Click to expand...
Click to collapse
I doubt *flashing* clockwork would cause force closes. But you can always revert back to 2.5.0.1 or AmonRa and restore a backup. Check the "Legacy" area of ROM Manager.
I also had this problem as ROM manager kept informing me that a new version of clockwork mod was available. after "updgrading" I couldn't flash any new ROMs and got a truncated message that during the process that 3.0 series clockwork mod needed to have some files deleted due to changes with Gingerbread and something about google.... (sorry about the lack of good definition on this, but the text was truncated and I was freaking out at the time since I started getting stuck at the white HTC boot screen.) Eventually I was able to perform a recovery and finally flash back to clockwork 2.5 and everything is OK now.
Strangely, after doing this ROM Manager indicated that 2.5 CW was the current version... However, after a few hours I started getting the message to "upgrade" to 3.0 again. I'll just ignore that for now.
Does anyone know why 3.0 is not working for everyone?
I got this also, but i wasnt using CM...i was on a sense mod and was able to restore a different rom and went to the new amon-RA instead.
Maybe its something with CM specifically
It has to do with the scripts used in the update.zips. Most people are still using the olds version used in 1.5... Net said that he had to change it to the new scripts used in gingerbread which makes it not work with any updates or backups made prior. There is a topic on it in here where he explains it. He says to flash the 2.5 if it's not letting you update something.
snappydave said:
I also had this problem as ROM manager kept informing me that a new version of clockwork mod was available. after "updgrading" I couldn't flash any new ROMs and got a truncated message that during the process that 3.0 series clockwork mod needed to have some files deleted due to changes with Gingerbread and something about google.... (sorry about the lack of good definition on this, but the text was truncated and I was freaking out at the time since I started getting stuck at the white HTC boot screen.) Eventually I was able to perform a recovery and finally flash back to clockwork 2.5 and everything is OK now.
Strangely, after doing this ROM Manager indicated that 2.5 CW was the current version... However, after a few hours I started getting the message to "upgrade" to 3.0 again. I'll just ignore that for now.
Does anyone know why 3.0 is not working for everyone?
Click to expand...
Click to collapse
Sent from my PC36100 using Tapatalk
They put up a new version of Clockworkmod recovery 2.6.0.1. This will work for all that had problems with the 3.0.XXX versions of the recovery. All the goodies of the 3.0XXX but with amend support so it will work with all roms.
All I can say is that Amon has never let me down. May want to check it out if you haven't already. Even their recent update was smooth as silk. No problems for me.
I had this happen to me too with a flash resulting in the white evo screen loop. I was able to flash to the amon ra 1.8 but I couldn't flash anything. So I upgarded to the new version of RA but am still not able to flash anything. I go into the white evo screen loop and then I have to pull the battery and nand a restore. Not sure what I need to do now. Any help would be greatly appreciated.
I have the Amon Ra recovery and tried to upgrade to Starburst ROM from Modaco R8. After a couple of false starts (ROM loaded OK but had various runtime problems) I noticed my SD card went "read only".
After doing a full wipe and reloading the Starburst zip, I tried to flash it from recovery, but the process stopped immediately and I was back in the Amon Ra menu. No error messages, just a complete failure to read the zip containing the ROM.
I've replaced the SD card and even tried installing a different ROM (good ole R8). Same issue.
Is it a good idea to reflash the recovery with Unrevoked or should I try something else first? Is there another way to flash a ROM than via recovery?
Flash ClockworkMod recovery via fastboot then try flashing the rom again.
Thanks, good suggestion, will give that a try, after making gold card just to soothe my nerves...
Do I need S-OFF for this?
And if so, can I still get S-OFF on the phone given I have no ROM installed?
Hi,
I flashed my phone with the HTC 2.3 dev release. Whilst it had some of the new features I wanted, it broke bluetooth to my car which was a deal breaker. I read plenty guides, got revolutionary, s-off'd and installed clockworkmod. That all worked well (seemingly).
I decided to try for the first time a custom rom rather than try and put back the original htc one. I tried leedriod. Used the install from zip method with cwm to install. It installed but just get stuck in a reboot loop. I tried CM7. That installed fine. Whilst the phone is now running with CM7, there are a lot of problems I think related to the boot loader.
If I try to install anything from the sdcard .zip via cwm, it always fails with cannot install zipfile (BAD). Tried hundreds of times! I obviously managed it the first time to get leedroid and cm7 installed.
Cannot establish a connection with the PC to the sdcard when the phone is running and copy anything for more than a few seconds.
usring rom manager, it always says cwm is not installed when it is and trying to re-install hangs near the end.
In cm7, reboot from power button just hangs.
I tried revolutionary again to re-flash cwm. That worked, but no difference. I've a feeling all the above are connected.
I've tried using cwm to do a full wipe, reformat sdcard etc.
Anyone any suggestions? Phone is a bravo with hboot 1.06
First off, rom manager's is pants, don't use it.
Bad zip file is usually a broken download, check the files md5 sum against the original, or just download it again.
Then clear all userdata and try the update.zip again.
I have 3 nandroids using cwm. Stock Rom, AEmod Rom and Starburst Rom. They are all on internal sd. Today I tried flashing a theme over starburst that I didn't realize wasn't compatible so I ended up in boot loops. When I booted into recovery to nandroid back to starburst, cwm was not recognizing any files despite the fact I can see them on the SD card. It's telling me "no files found".
Anyone else encounter this?
P.S. I ended up reflashing the ROM itself, but the weird part is that it downloaded and had all my previous settings. It wasn't like I installed a new rom from scratch. It was very odd. I cleared everything before I flashed the zip too, so I'm sort of puzzled.
So you are up and running now just have some settings left over from before? The reason some of this didn't get erased is likely because you didn't format system. This step wasn't included in the original instructions for flashing the Starburst rom. If you look at the Starburst thread in the Dev forum it will now show this additional step. Hope it helps, this is one additional step you need to do when flashing a rom or restoring a nandroid.
Sent from my SPH-D710 using XDA App
t91180 said:
I have 3 nandroids using cwm. Stock Rom, AEmod Rom and Starburst Rom. They are all on internal sd. Today I tried flashing a theme over starburst that I didn't realize wasn't compatible so I ended up in boot loops. When I booted into recovery to nandroid back to starburst, cwm was not recognizing any files despite the fact I can see them on the SD card. It's telling me "no files found".
Anyone else encounter this?
P.S. I ended up reflashing the ROM itself, but the weird part is that it downloaded and had all my previous settings. It wasn't like I installed a new rom from scratch. It was very odd. I cleared everything before I flashed the zip too, so I'm sort of puzzled.
Click to expand...
Click to collapse
T, you are one step ahead of me. I can't even get CWM to make a nandroid. I get "Can't mount /sdcard". I've pretty much tried everything, but giving up for now. Samsung is crazy obstinate and complicated compared to HTC. But this rig is worth it
I was rocking an old S.E.A.L. ROM for a couple years until it started becoming unbearable due to apps crashing and random reboots. So I downloaded a couple new ROMs to try, along with a new kernal, and put them on the sdcard storage.
I did a factory reset wipe, and tried flashing with TWRP. Couldn't seem to run the install properly and kept getting corrupt file errors.
So I used ODIN to update TWRP to 3.0.0. I tried all kinds of flashing again with the same errors. So I re-downloaded the zips and moved them to ExternalSD. The flashing process now seems to go smoother, but the problem is that it doesn't seem to actually write anything to the device. However, I did flash the latest SuperSU zip and that seemed to create a folder, etc..
I tried using ODIN again to re-flash the recovery (to try TWRP 2.8.7) and that seems to fail now. So it appears I'm stuck with TWRP 3.0.0. I can boot into Recovery and Download modes no problem.
I've tried just about every approach to ressurect this tablet with a fresh ROM and nothing is working. My head is approaching the explosion point.
I'd appreciate any advice!
Thanks!