OLD CWMrecovery.tar - Fascinate Android Development

This is the .tar file I used for CWM. Did a Factory data reset then flashed the package via ODIN (PDA). I had to reactivate my phone to get access to App Market to download Rom Manager. I Flashed ClockworkMod Recovery via Rom Manager and used the Reboot into Recovery to install the DL30.zip.
http://www.multiupload.com/C0HFVLSI22
I followed the steps outlined in several other threads and got nothing but errors. This is the only way that worked correctly.
I did not install the new CWM until AFTER I flashed the DL30.zip!
Loving Froyo and hope everyone else gets it running soon!

Related

[Q] HELP: I cannot get vibrant to boot into CWM

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!

[Q] Clockworkmod install problems

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!

[Q] Issues with CWR

I am new to modding my vibrant (phone is rooted but that's all) but looking to flash a new ROM. I dl'd rom manager and installed cwr. When I reboot into recovery mode via rommanager or manually doing it,I do not get the prompt to backup. Only options I get are to reboot system, reinstall packages, delete all user data, delete cache data, and format internal sd-card. Anyone know how to fix this? I just updated to 2.2 froyo UVKB5 kernel 2.6.32.9 if that helps.
looks like you have stock recovery.
try reinstall packages, might take a couple times..
or install CWM via replacing update.zip
What he said, yeah.
So just delete the current update.zip file on my phone and replace it with a new one? Any links to download the update.zip file?
Sometimes you have to Reinstall Packages twice for it to go from regular recovery to CWR. If you flash a custom ROM though, most have a custom recovery built in.
If you have to replace the update.zip (which I don't think that you do), this worked for me the first time I rooted.
http://forum.xda-developers.com/showthread.php?t=849028
How to Root.
I am rooted, but I want to back everything up so that way if I do not like the new custom rom I can go back. I tried reinstalling the update.zip file from the link but s till have the same issue. Any other solutions besides going back to stock and going from there? And if I did go back to stock, would I lose everything?
I backed up using Titanium Backup, is that the same as going into recovery mode and backing up?
Re-download recovery using ROM Manager, then repeat. Worked when I had a similar issue.
Tried that several times. I also reuploaded the update file and reinstalled the package several times. Still no luck so I think I might go back to stock using Odin.
Then DL Eugenes froyo don't brick ROM with the 2e recovery update in it, then re-install packages, maybe twice and you'll have the green recovery menu your seeking
Googled Eugene's DL and I do not feel to confident with it. Is it supposed to fix the issue with getting into recovery mode?
So I went back to stock last night using Odin, upgraded to 2.2, and rooted using Superoneclick. Phone's back up and running but faster than the first time I upgraded to 2.2. I still have the issue getting into the proper recover to install the zip file. I've read that deleting Slacker helped some people, assuming it freed up space on the System ROM. My system ROM was full until I started to delete some apps. I now have 20.7 MB free. Could not enough System ROM space be the issue?
I am now also getting a "Fail" attempt when I try and update su saying that it failed to find currently installed su binary. Any advice on fixing this?
TIA!!!
it would probably be easier to just odin back to stock jfd and then flash a deodexed kb5 build thats rooted with SU already in it from here in the forums.
http://forum.xda-developers.com/showthread.php?t=1036193&highlight=deodexed
If you flashed kb5 from kies or odin and don't want to reinstall the rom then you will need to flash a modified 3e recovery because you probably are not quite rooted and won't be able to use CWM until you flash the modified 3e recovery...
http://forum.xda-developers.com/showthread.php?t=833423
You might want to check out the AIO vibrant toolbox (pinned topic in the development thread) it will give you big easy buttons and instructions to flash back to jfd and root and flash a new rom if you need to... It comes with Odin so you can wander into the install folder and fire up Odin to flash the modified 3e recovery if you decide to go that route too.
If I flash a deodexed kb5 will i still be able to flash a custom rom?

GT 10.1 LTE - EH04 - Unable to install CWM Recovery

I have a rooted GT 10.1 LTE with the EH04 update. I have tried flashing via CWM which results in the obvious breakage. I have also tried installing via Recovery and Odin with the attached files and in various combinations with no luck.
Any suggestions or ideas on what I am mucking up to not be able to get CWM only my tablet?
To note: It was working prior to the EH04 update.
Bump.
Any ideas?
try the cwm here:
http://forum.xda-developers.com/showthread.php?t=1090289
to a certain degree it is a lot of trial and error as to what parts of the various 10.1 models are common and which are distinct -- at this juncture what is to loose from flashing a different cwm?
Try this recovery ( flash zip)
http://www.mediafire.com/?w45j8i0fcj0wck0
Then try this rom
http://forum.xda-developers.com/showthread.php?t=1277045
Its been working very well for me.
Mr.Jester said:
I have a rooted GT 10.1 LTE with the EH04 update. I have tried flashing via CWM which results in the obvious breakage. I have also tried installing via Recovery and Odin with the attached files and in various combinations with no luck.
Any suggestions or ideas on what I am mucking up to not be able to get CWM only my tablet?
To note: It was working prior to the EH04 update.
Click to expand...
Click to collapse
I unrooted to get the EH04 updated using this: http://rootzwiki.com/topic/7718-romleakodineg01-factory-stock-odin-image-vzw-lte-tab-101/ , waited for the EH04 update, then re-rooted using this (which I used to root initially): http://rootzwiki.com/topic/2242-root-recovery-galaxy-tab-101-lte/ .
Perhaps you should unroot per the above, take the update, then re-root as above--worked for me.
i ota'd EH04, lost root. downloaded kernel.zip, applied it, got root back, installed cwmod, clicked to reboot into recovery and it's looping since, i can't do anything but get into ODIN but the PC wont recognize it, although i get a pop up saying android.. installed, adb devices doesn't pick up either. can't get into recovery.
---
update
http://forum.xda-developers.com/showpost.php?p=18121666&postcount=53
someone warned in the forums and i didn't read it before i did it, used odin to put recovery.zip, now i'm back in action.
The recovery you provided is the same that I attached. What I discovered however is that if I booted into recovery right after installing the CWM recovery, CWM would load. If I booted into stock EH04 then back into recovery, the stock recovery would load. It seems as if the ROM was restoring stock recovery when it loaded. After installing Lightspeed, CWM recovery stayed in place.
Either way, thank you for the assistance. I hope this thread ends up helping someone else.
My steps to install Lightspeed from Stock ROM EH04:
1. reboot recovery, install either recovery.zips above.
2. When the system automatically reboots, hold volume up to boot into recovery again. This time it should be CWM.
3. Wipe cache and factory reset
4. Install Lightspeed ROM
I
Mr.Jester said:
The recovery you provided is the same that I attached. What I discovered however is that if I booted into recovery right after installing the CWM recovery, CWM would load. If I booted into stock EH04 then back into recovery, the stock recovery would load. It seems as if the ROM was restoring stock recovery when it loaded. After installing Lightspeed, CWM recovery stayed in place.
Either way, thank you for the assistance. I hope this thread ends up helping someone else.
My steps to install Lightspeed from Stock ROM EH04:
1. reboot recovery, install either recovery.zips above.
2. When the system automatically reboots, hold volume up to boot into recovery again. This time it should be CWM.
3. Wipe cache and factory reset
4. Install Lightspeed ROM
Click to expand...
Click to collapse
Thank you. Everytime I tried flashing cwm recovery, I would always end up back at stock recovery. Your fix worked perfect.

[Q] Phone stuck in recovery boot SGS2

Hi, I'm pretty new to rooting and whathaveyou, and followed a guide to installing Siyah-s2-v6.0b5, and everything was working fine, until I came across Cyanogen, which I'd saw a while back and looked quite interesting. I tried to install Cyanogen once the phone was rooting, but the installer on my PC said that my device was unavailable for the installation, for which I appointed to the fact that it was rooted.
I downloaded the Cyanogen install zip for my SGS2, and in the recovery menu used "install zip from sdcard" from which I selected the Cyanogen zip. The installation failed, and any attempt at starting the phone would lead me to the CWM-based Recovery v6.0.1.2.-Siyah, and no further. I'm able to access the download mode.
I attempted using Odin3 v3.07 to install a stock kernel onto the phone, but I was left with the boot, maybe I was doing it wrong?
I'd really appreciate some help, thanks.
- Brad

Categories

Resources