Ok, after successfully rooting and putting EB01 on my phone, I discovered that when I tried to install zip files from my sd card that I was taken into Samsung recovery (blue). I found out that my CWM was dated, and needed a new one. In looking for the most current version, I installed CWM 3.0.0.8. Now when I attempt to install from SD, I am rebooted into red CWM, but it doesn't like the script, so it aborts installation of whatever ROM I try to install. Update.zip kicks me into CWM 3.0.0.8, and when I try to install from there I get a similar message. I have tried to flash a different CWM through Odin, but nothing changes. I have also tried to use the "All ClockworkMod Recoveries" option, but it tells me "An error occurred while downloading your recovery" regardless of which version I select.
I am running Superclean 2.2 and have Rom Manager v3.0.1.0
I did see a similar thread to this for an HTC Hero phone, and it seemed to indicate the CWM I installed is for Gingerbread. Hoping there might be an easy fix to this I am overlooking so that I don't have to start from scratch. TIA!
It's not JUST for Gingerbread. The scripting language that the newest cwm uses is edify. And the latest cwm doesnt support the older scripting languages that the zip scripts used to be written in. so all the scripts need to be updated to use edify. And they'll work fine. Even on froyo.
Sent from my SCH-I500 using XDA App
Also, the newest version of Superclean (2.7) uses edify, so you should be able to flash that in CWM 3.x
times_infinity said:
It's not JUST for Gingerbread. The scripting language that the newest cwm uses is edify. And the latest cwm doesnt support the older scripting languages that the zip scripts used to be written in. so all the scripts need to be updated to use edify. And they'll work fine. Even on froyo.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Ok, that makes sense. Is there anything I can do to update the scripts?
I am trying to do the same thing. I want to have a Rom Manager version on my phone that allows me to use the 'install zip from sd card' function in the program and run the scripts correctly.
I have replace the update.zip and update-recovery.zip with th red jt1134 CWM zip, but the latest version of CWM seems to write scripts entirely differently, so it'll get me into recovery and then recovery can't run the scripts. Any idea of how I can go back to a prior version of Rom Manager?
spenceuiuc said:
I am trying to do the same thing. I want to have a Rom Manager version on my phone that allows me to use the 'install zip from sd card' function in the program and run the scripts correctly.
I have replace the update.zip and update-recovery.zip with th red jt1134 CWM zip, but the latest version of CWM seems to write scripts entirely differently, so it'll get me into recovery and then recovery can't run the scripts. Any idea of how I can go back to a prior version of Rom Manager?
Click to expand...
Click to collapse
Odin. Here's the page. http://forum.xda-developers.com/showthread.php?t=942021
Just use manual cwm for now. The ROM Manager is going to fudge it for the time being. I don't trust RM to do a proper wipe before install either. It would be nice to use the RM gui, but its better to just spend a few extra minutes to make sure things get done right.
How do you get into CWM
How do you get into CWM without Rom Manager????
derond1 said:
How do you get into CWM without Rom Manager????
Click to expand...
Click to collapse
If you already have a super clean rom, just hold your power button to pop up the power down screen. Then select the option for "Recovery".
OR
Turn off phone. While turning it on, hold the power button+up volume+down volume. The Samsung logo will turn on, then turn off. Release the buttons and it will come on again then boot to recovery. Then select the option "update.zip" to launch into CWR.
So far what are the problems with the new CWR recovery 3.0? I want to flash to the newest SCv2.9 but Im reading some iffy comments on it. What are the possible drawbacks and is the only way to get back to CWR 2.5 through Odin? because since I own a mac this is a ***** and a half to do! Can you also run CWR 2.5 on SCv2.9?
Thanks in advance.
tumness420 said:
So far what are the problems with the new CWR recovery 3.0? I want to flash to the newest SCv2.9 but Im reading some iffy comments on it. What are the possible drawbacks and is the only way to get back to CWR 2.5 through Odin? because since I own a mac this is a ***** and a half to do! Can you also run CWR 2.5 on SCv2.9?
Thanks in advance.
Click to expand...
Click to collapse
I was able to follow the thread by jt that has a simple zip and install with my cwm 3.0.x.
sent from Froyo'd Fascinate!
I have successfully been able to root and install everything on my Mytouch4G just fine, however, when I tried to install my wife's Vibrant, I am stuck. Here is what I have done:
1) I rooted successfully using superoneclickv1.9.1
2) I installed ROM Manager and also downloaded the Auxora ROM to get ready to install
3) When I flash CWM recovery, it says current and latest recover is 2.5.1.2 (concern here that my mytouch says 3.0.2.4 - do different phones install differently with CWM?). When I look at all CWM recoveries I also notice there is two seemingly more current versions available 2.5.1.3 and 2.5.1.4. I have left it at .2 but wondering why all the versions.
4) When I reboot into recovery, I always get the stock recovery and have not been able to get CWM recovery so I am unable to flash my Auxora ROM. I ran update packages numerous times, and get a signature verification error. I have tried a recovery 3e patch that does not work either. I also gave a try at downloading and SDK, but received temp root errors (phone is already rooted).
After reading many posts, I cannot seem to get a direct answer on what I should do to get CWM to actually boot properly, so I can flash a ROM. Someone said to flash the stock JDK rom, but if I can't boot into recovery, how can I flash anything.
Any help would be greatly appreciated.
You need to get a program for your pc called odin to get back to stock. you can find that and instructions on how to use it if you search for the daily updated vibrant bible its GREAT
http://forum.xda-developers.com/showthread.php?t=849028
going to stock eclair heres a a great guide
So going back to stock eclair will then allow me to install CWM recovery then load roms?
Every once n a while I haft do the install packages thing twice before it gives me clockwork green
. Hope this helps.. o n btw u should look at some of the other roms in the bible before u try auxora
yes u should go back to stock eclair for every rom, in my opinion. Then after that do the 3 button combo and install packages and u will have to do it twice and then the green screen will kick in and ready to rock a new rom.
i hope this helps
What is your current firmware?
I see you posted over in the "NOOB GUIDE" thread, you should really try to root using the method posted there and not any one click root apps.
This should be the root method everyone uses:http://forum.xda-developers.com/showthread.php?t=723479
After root your phone recovery should be blue. Choose "reinstall packages" gives you green recovery(this may need to be repeated multiple times to work possibly including flashing CwMRecovery with ROM manager. I recently did it 5 times b4 i got green recovery)Once you access green recovery chose "apply sdcard:update.zip" go into advanced and choose "reboot recovery" This should give you red recovery. Do a nandroid backup and flash away. Good luck!
Another option you could do is to download SGS kernel flasher from the market and flash a voodoo injected kernel with that app. Then when you boot into recovery you will have red voodoo recovery and you can flash away.
Odin to stock the best way to flash a new rom
Sent from my SGH-T959 using XDA Premium App
jman531 said:
So going back to stock eclair will then allow me to install CWM recovery then load roms?
Click to expand...
Click to collapse
The stock 2.2 that Samsung distributed with their Kies tool has a recovery that checks signatures. Everything earlier does not check signatures. So either use something earlier to get CWM running, or use a ROM that doesn't have the stock 2.2 recovery in the first place, or mod your recovery using the method described in http://forum.xda-developers.com/showthread.php?t=833423
Using Odin to go back to stock Eclair between your flashes of modded roms has the benefit of taking care of this, and also can clear up left over bits and pieces that may interfere with the proper function of your new ROM.
ok, i followed the instructions and am back to eclair, however, whenever I install packages, it just reboots the phone, not even back into stock recovery. I use the 3 key method and get into recovery, run install packages, and the phone just boots back up...its like it isn't running the update.zip file...
UPD: When i load rom manager and try to reboot into recovery, it says the application superuser permissions has stopped unexpectedly and keeps force closing now....titanium backup wont run now either, my root permissions seem whacked after going back to eclair?
UPD2: I followed instructions to unroot and reroot here: http://forum.xda-developers.com/showthread.php?t=739300
It removed superuser, then added it back again, but I still get the unexpected error and it appears my root is not in place. I am back to eclair, and now need a certain way to get my root fixed, so I can try and flash CWM recovery. Without root working, it is not letting me. My wife hates me now for doing this to her phone, so those of you that are married, I would appreciate your assistance to get back on her good side...before Mother's day...please? =)
Ok, thanks for all the help, however, I am really back where I started. I can only get stock recovery, and for the life of me, cannot get CW recovery to load. I used ODIN to go back to eclair on the vibrant, have a good root on the phone now, and no matter how many times i reinstall packages i cannot get clockworkmod recovery to load, ever. Any more thoughts out there?
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
starkiller86 said:
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
Click to expand...
Click to collapse
thanks...It is rooted, but not sure about busybox...the stock recovery is 2e now since I went back to eclair, so not sure i should follow that link as it talks about modifying 3e and making it backwards compatable. I did use that process before I went back to eclair, and it didn't work for me. I have uninstalled rom manager, and reinstalled...and it is different in that it shows a flashed recovery 2.5.1.2, and never asks me for my phone type anymore...it used to ask me and i had to select vibrant....is the recovery supposed to be 2.5.1.2? when I show all recoveries it lists .1, .2, .3, .4 so wondering if I should use .3 or .4...why does it stay at .2?
starkiller86 said:
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
Click to expand...
Click to collapse
OK>>> I GOT IT... Thanks to everyone who helped...Here is what was needed:
1) Install ODIN, install back to eclair
2) uninstall ROM Manager, reinstall
3) I needed to select the 2.5.1.2 recovery from the list again (this was important as it somehow knew of the previous load, but files were missing, or something was just wrong.) It finally loaded properly, and asked for phone type again, so selected vibrant
4) I rebooted into recovery, and instead of install packages, i rebooted once, as starkiller suggested
5) After reboot, went back into recovery from rom manager, and this time installed updates, and it showed that it replaced the recovery with CWM.
6) It rebooted into stock recovery however, so I once again selected install updates, and it went right into CWM recovery, and now I am flashing happy!!!
Thanks again everyone...this was soooooo different than my mytouch4g!
If you have the Kies update of Froyo, the 3e mod will sometimes not work. I've gotten to CWM though , but its best to downgrade then flash a ROM from there.
I just wanted to bump this thread because it really helped me.
I've messed around with numerous android phones, and I've never had thie issues I've had with this phone getting into recovery to flash ROMs
Thank you!
Ok, so I have been running a Honeycomb rom but wasnt happy with it so I decided to try a different one. In the Roms directions, it said to be on a stock 1.2 rom. So I downloaded the one from its instructions and flashed. All went well, it booted into the stock rom with no problem. So I put the new HC rom on my sd and renamed to update.zip. I booted into recovery and noticed that the recovery was reverted back to the stock recovery. I thought, no big deal, Ill just flash the rom from that recovery. Well it kept aborting the install for some reason. Doesnt give an error, just says installation aborted. So I figured it was the recovery that was the problem. I downloaded CWM 0.8 and followed instructions, put the recovery folder and the update.zip on the sd card, I booted into recovery and the installation bar came up like it was installing, then switched back to the stock recovery. I assumed all went well and rebooted the device then powered off again and tried to boot into CWM, shows the three birds and the recovery key detected but doesnt go any further. I can power the device off and boot it back up into the stock rom but every time I try to boot into recovery, it does the same thing and gets stuck. Any help would be great.
CWM v8 isn't compatible with 1.2 branch.
My website here.
Hi all.
Hope everyone is having a good day!
Lets start: in simple words, it appears I've got two CWM installed. Know it sounds crazy but this is how it looks.
I run Villain 2.4.2 with nynmphetamine 2.1.3 kernel and "some" CWMs
Previously I had also Villain but on CFRoot kernel that preloads a custom CWM
What I've done:
I tried to install CM7 "easy" way so installed ROM manager and when it asked me if I wanted to flash CWM with the newest one I pressed "yes" and stupidly overwrote it. Then downloaded CM7 and when ROM manager attempted to boot into CWM android logo with an expression mark appeared and the phone hung. I rebooted into recovery and it showed me I run CWM 4.0.0.2 (i think that's the custom from CFroot) but the ROM manager says I've got 4.0.1.5.
When I tried to install CM7 via 4.0.0.2 the installation itself went fine but the phone stucked on Samsung logo during post-instalation booting.
Could you give me an advice on how to sort this out? I mean to get properly set up kernel and CWM after some serious messing up
I'd be grateful for any help.
Cheers.
chalger
I dont know if its possible to have 2 CWMs (maybe app version is different), but this happens with CM7. You should wipe dalvik, factory reset, flash cm7 and boot. Phone will get stuck, shut down long pressing power, reboot in cwm and reflash (no wipe needed). CM7 should boot now.
Trying to install clockworkmod but I have 3e recovery. I did it through rom manager which was a nub mistake but I didn't know 3e was going to troll me. So it says:
e:failed to verify whole file signature
e:signature verification failed samsung "3e"
I then followed this thread: http://forum.xda-developers.com/showpost.php?p=16909269&postcount=12
and tried the Speedmod kernel to get rid of 3e like the person said but that rom is for the international version and now I can't connect to verizon.
So at the point I am thinking using Odin is my only option but all roms are .zip and not .tar. I am clueless as what I can do. Please help me.
So I tried the Odin method in this thread http://forum.xda-developers.com/showthread.php?t=1026746 and flashed the pit and stock 2.1 files. It passed with green in odin but when I put the battery back in it boots into 2e but says # Manual Mode # at the bottom. I am not sure if that means the flash didn't actually work or what. I am lost now.
Thought I'd update this thread since I finally fixed the problem and sucessfully put Cyanogenmod7 without using the stupid Rom Manager after about 8 hours of work. So just in case someone wants to know what I did. For some reason Odin was not working so I used Heimdall v1.83 and the EB01 Heimdall package and sucessfully flashed to froyo 2.2. I mounted the sdcard and put Cyanogenmod7 and gapps on it.
Now I used Odin to flash the CM7 capable CWM (I think its version 4). Booted the phone into download mode and then used jt1134's ClockworkMod Recovery found in the CM7 fascinate wiki. The wiki says use Heimdall but I used Odin and it worked. The CWM is now blue instead of Red. Next I did a wipe data/factory reset along with wipe cache partition. I selected install zip from scard and choose the CM 7.1 package. Everything went well and it boots into CM7. NOW TO INSTALL THE GAPPS. I thought I just boot into CMW using the volume buttons and power button BUT NO that is NOT correct. In CM7 you have to hold the power button and press reboot and then select recovery AND THEN IN THAT CWM select install zip from sdcard (choose gapps). THIS IS IMPORTANT OR ELSE GAPPS WONT INSTALL. I was bummed for like another hour.
So there it is how to install CM7 just when you think you have been to hell and back with the fascinate. Never again am I volunteering myself to help root and install CM7 on a friend's fascinate. The droid incredible was soo easy!