post no longer relevant
If you want to update this, My modified cwm thread has the RED clockwork odin package.
adrynalyne said:
If you want to update this, My modified cwm thread has the RED clockwork odin package.
Click to expand...
Click to collapse
i think omj is going to change his op on af...ill copy that over when he does
When I get in Odin and select CWMRecovery_DJ05_DL09.tar.md5, it fails.
I did not touch any settings in Odin, just clicked PDA and selected that file.
Edit: Redownloaded that file and got it to work. I am now having an issue when applying update.zip... it starts but then comes up with an exclamation point inside of a triangle and the little Android guy... phone reboots fine.
Did you get this solved? Check out the thread at AF I had the same problem
worked like a charm..thanks!
SoCalSpecialist said:
worked like a charm..thanks!
Click to expand...
Click to collapse
ok so i havent been able to find a full answer..but does this leave the device in DI01 or 05 or 09?
just by looking at the files it seems as if it goes from 05 to 09 but once in about phone>build number it reads : DI01
so im just looking for a little clarification here..just rooted my Facinate minutes ago so im still stuck in the whole mindset of the Incredible.
I tried this. Have EA28. Not sure how. Didn't install. Saw install screen on phone last night and hit cancel.
Anyway, Ran Odin, CWMRecovery_DJ05_DL09.tar.md5, reboot, blue text, apply sdcard:update.zip, switched to red text, install zip from sd card, choose zip from sd card, su-2.3.6.1+busybox1.19.zip, choose zip from sd card, DJ05_DL09_kernel.zip (plain kernel due to dl09), ran titanium backup, could not acquire root priv.
Startup screen has sound, but not animation anymore. Installed superuser and it shows titanium backup under "allow". When I run TB, I get the error screen and below in another small screen says, "Titanium Backup has been granted superuser permissions". But can't get anywhere to backup apps. Says Root Access: Failed.
ideas?
Another thing that confused me was the red cwm says voodoo lagfix recovery v2.5.1.x. I thought you weren't supposed to use any voodoo for DL30? Not that I've made it that far due to titanium backup issue, but....
Can anyone confirm whether or not this to sure does or doesn't work with ea28? My wife updated he phone and now she wants it rooted.
Edit this does work for EA28. Everything went smoothly. Thanks nitsuj.
Sent from my SCH-I500 using XDA App
mdisaac said:
When I get in Odin and select CWMRecovery_DJ05_DL09.tar.md5, it fails.
I did not touch any settings in Odin, just clicked PDA and selected that file.
Edit: Redownloaded that file and got it to work. I am now having an issue when applying update.zip... it starts but then comes up with an exclamation point inside of a triangle and the little Android guy... phone reboots fine.
Click to expand...
Click to collapse
I also got stuck at the same screen. what did you do to resolve it????
Here is the link to my guide for rooting with a MAC. I do not have a PC and used these steps to successfully root my phone. After completing last step in guide and getting blue cwm on your phone, DL new red cwm and install
http://forum.xda-developers.com/showthread.php?t=967641
Sent from my SCH-I500 using XDA Premium App
EA28 going to DL09?
Hello..
I am just getting around to rooting my fascinate now. I have EA28. From the instructions, it appears you are going back to DL09. Is that correct? What is the significance of that? Should I care?
Thanks in advance!
This thread is old and should be deprecated. The directions still work, but you need to use the Odin package of ClockworkMod in this thread (it's the very first item linked) instead of the md5 file (DL05_DJ09) above.
However, if you're going custom the thing you should *really* do is Odin in one of the full-Froyo packages. This will include both root and recovery.
s44 said:
This thread is old and should be deprecated. The directions still work, but you need to use the Odin package of ClockworkMod in this thread (it's the very first item linked) instead of the md5 file (DL05_DJ09) above.
However, if you're going custom the thing you should *really* do is Odin in one of the full-Froyo packages. This will include both root and recovery.
Click to expand...
Click to collapse
Thanks S44. My goal is to go froyo, but I need to be rooted first in order to do that.
I have been reading all the threads but many of them are very long. The DL30 thread is over 50 pages long.
So should I:
1) follow the instructions in this thread but use the new ClockworkMod then
2) update to froyo.
What is the most current thread for updating to froyo on the fascinate while after I am rooted?
Appreciate it.
TheTinRam said:
Thanks S44. My goal is to go froyo, but I need to be rooted first in order to do that.
Click to expand...
Click to collapse
Actually, no you don't. Download mode is magic. You *do* need to be rooted to back up apps with Titanium, if you want to do that. In that case, follow the directions above (with the new recovery). Then back up your user apps + app data.
Whether or not you do this, you should move to Froyo with a full-Odin package. Download the ROM you want (either Nameless, Super Clean, or whatever) in zip form to your SD card. Follow the directions here (under "Most Thorough Method of Fixing Every Problem You Might Have") using the first two files here and the recovery I mentioned in my previous post. Yes, this is sort of overkill, but better to avoid stuff like corrupted dbdata from the beginning and not have to fix it later.
You might want to wait a day or so because it looks like jt is finally fixing up Clockwork.
EDIT: I read almost all of the 52 pages of the DL30 thread to realize that DL30 is out of date . I guess Its going to be EB01 or Superclean. Do you know if Superclean has the audio out via USB working for the docks?
I have some questions in regards to picking ROMs:
I am a little confused in where to find the latest versions. For example in the "most thorough me..." thread, there is a link to super clean version form 3/30/2011 yet wiki has super clean from last year. Where can I look at all the ROMs and descriptions?
Which froyo ROM would you recommend? I love Google's stock froyo, but I also want to use the fascinate's USB audio out on the car and desktop dock. I also would like to wifi tether.
Thanks again!
This post had a link to download ODIN but it was removed. Could you please provide that link again. It also had a link to "Samsung Drivers", don't I need that too?
I am going to take a shot at following the ""Most Thorough Method..." steps tomorrow morning and install superclean on my Facinate. Quick Q: In step one, it simply says to ODIN EB01. I can just do this without being rooted?
Also, you said jt is fixing up clockwork. What do you mean by this, what exactly does not work?
I know these are noob questions, but I am just starting out with this.
Thanks
Driver links are here. Odin is here.
Yes, download mode lets you Odin in complete firmware packages without root.
Most people are using Super Clean, so that has the most support (and themes), but there are some odd issues floating around with it. My guess is that a lot of those issues have to do with not cleaning up in the super-thorough way I'm suggesting, and with the permissions bug after flashing a theme (below). There's also navendrob's EC10-based "Nameless" ROM, and ahmgsk's DL30-based "TrulyFascinating" ROM. Nameless is good but he's about to drop a version 4 with a lot of fixes, so you might wait a day or so for that. TrulyFascinating seemed to be pretty good (heavily stability-tested), but he hasn't updated it in a while (busy with more recent Epic leaks, I guess). You might try running it with one of the state-of-the-art EC10 Voodoo kernels.
There are a couple of Clockwork bugs, but the one causing the most current problems is that the old one couldn't fix permissions properly. This causes issues after making a change to the /system after the initial ROM flash, generally when you flash a theme on top of it. The new one I linked above *can* fix permissions, but still requires you to manually mount /dbdata beforehand (actually, go to the "mounts and storage" submenu and make sure /system /dbdata and /data are all mounted -- that is, the option referring to them says "unmount", which will happen when they're mounted -- before you go to the "advanced" submenu and run the fix permissions script). The new new one coming soon will just fix it without a problem, and do other stuff too.
Once again thanks. I have everything I need....or so I thought.
I restored my phone to factory, loaded the drivers, fired up ODIN and added the PDA and PIT. I hit start.... nothing happens. "All threads complete, succeed 0 / failed 0"
Looks like I am missing something. Do I need to somehow tell ODIN where the phone is? I don't see a way to do that.
PS in step 4 its states "ODIN the CWM Recovery package ROM from this post". Does CWM bin file go into PDA or phone in ODIN?
I one again apologize for my noobiness.
The Clockwork step comes after you do the full package and boot with that.
Make sure you have Odin open *before* you connect the phone in download mode.
Related
I seem to be at a bit of a cross road here, hopefully posting this story can give me some direction, as I see people with similar problems elsewhere, but not on XDA.
After getting the JI6 upgrade on stock, it took out OCLF, when i did it update, none of the setting where available. So when I redid OCLF, i could not up to the new OCLF and could not undo the old one. However voodoo5 was available, and seeing the reports on that voodoo5 was the bees knees. So I ran it (stupidly. It went though the motions, heard the voice prompts saying the steps, and said it was Completed. I knew the first boot up took some- what I would get is
Stuck on Black Vibrant screen, would hear T-Mo boot up sound, but would never progress after 20 - 30 minutes
Reading the Forum, (Use that search button) using the steps specifically in this post: [TUTORIAL][ROM] How to fix your phone and apply the update --- to achieve what i heard that had success stories with using Odin to restore to restore JI6 update after this kind of error. Well here is where I am at:
I can get into recover mode and boot loader
I get Vibrant, Tmobile screen, hear the tmobile tone, and then see the galaxy S screen
I then get an all black screen where the buttons on the bottom (home, back etc) light up, and will turn off when i touch them and then come back on
And that's it. I get nothing, a big blank screen. And I am unsure where to go... any advice would be helpful on how to get a full recovery. No longer worried about my data, just want to get my phone back up and running by any means.
buggzero said:
I seem to be at a bit of a cross road here, hopefully posting this story can give me some direction, as I see people with similar problems elsewhere, but not on XDA.
After getting the JI6 upgrade on stock, it took out OCLF, when i did it update, none of the setting where available. So when I redid OCLF, i could not up to the new OCLF and could not undo the old one. However voodoo5 was available, and seeing the reports on that voodoo5 was the bees knees. So I ran it (stupidly. It went though the motions, heard the voice prompts saying the steps, and said it was Completed. I knew the first boot up took some- what I would get is
Stuck on Black Vibrant screen, would hear T-Mo boot up sound, but would never progress after 20 - 30 minutes
Reading the Forum, (Use that search button) using the steps specifically in this post: [TUTORIAL][ROM] How to fix your phone and apply the update --- to achieve what i heard that had success stories with using Odin to restore to restore JI6 update after this kind of error. Well here is where I am at:
I can get into recover mode and boot loader
I get Vibrant, Tmobile screen, hear the tmobile tone, and then see the galaxy S screen
I then get an all black screen where the buttons on the bottom (home, back etc) light up, and will turn off when i touch them and then come back on
And that's it. I get nothing, a big blank screen. And I am unsure where to go... any advice would be helpful on how to get a full recovery. No longer worried about my data, just want to get my phone back up and running by any means.
Click to expand...
Click to collapse
Did You Flash Something Before Disabling Voodoo? 2 Fixes to Help You Out.
So you forgot to disable the voodoo lagfix before you flashed a new rom and now you're getting an error, similar to the one posted below. Even Odin won't allow you to flash back to stock. Well, pay close attention and with some luck, you'll be good as rain...or something like that.
Fix 1:
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine! BAM!
Fix 2: (use only if you know how to use adb commands)
1. Place the 'disable-lagfix' file in your sdk>tools directory
2. Get into clockwork recovery like you normally would
3. Follow these adb commands to push the 'disable-lagfix' file to you sdcard>voodoo
adb push disable-lagfix /sdcard/voodoo
4. File should now be on your sdcard in your voodoo folder.
5. Reboot phone and with luck, you should hear Linda the robot telling you your file system is being converted back to rfs.
6. Because your system directory has already been wiped, you'll still get a black screen when you reboot, but your file system is back to rfs. Just pull the battery, and reflash whatever rom you want. Then reboot again.
ANNNDD THE TRUUUUTHHH SHALL SET YOU FREEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE
Thank you AMD. Following "Fix 1" Method, worked flawlessly!
Now, just to clarify, this put the phone completely back to stock? It has undone the ext2, voodoo and hoodoo nonsence? I just want to know where I stand, becuase now that I am wiped clean, there is obvious no worry of loosing data now lol. Might as well put a nice custom rom, rather than fiddiling with fixes to the stock right now.
Also, I am not yet familiar with ADB, but will read the sticky Bible thread, do you recomend that method over the 1st one? I did not install clockwork recovery, is that a perferred pre-loader to prevent these kind of issues?
buggzero said:
ANNNDD THE TRUUUUTHHH SHALL SET YOU FREEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE
Thank you AMD. Following "Fix 1" Method, worked flawlessly!
Now, just to clarify, this put the phone completely back to stock? It has undone the ext2, voodoo and hoodoo nonsence? I just want to know where I stand, becuase now that I am wiped clean, there is obvious no worry of loosing data now lol. Might as well put a nice custom rom, rather than fiddiling with fixes to the stock right now.
Also, I am not yet familiar with ADB, but will read the sticky Bible thread, do you recomend that method over the 1st one? I did not install clockwork recovery, is that a perferred pre-loader to prevent these kind of issues?
Click to expand...
Click to collapse
Your welcome and yes, you're completely back to stock and everything is gone. So you should be set. No, both methods work well and do the same. I know adb but still prefer the first method, works all the time is something goes wrong with voodoo or any lagfix.
I wouldn't say it's preferred to prevent those issues because you may still have them either way but its nice to have. You can make a backup with it so if anything goes wrong you have something to fall back on. Just makes things simpler.
Sent from my SGH-T959 using XDA App
Seeing some of your other posts in the bionix fusion rom, which is what I ended up flashing to, it seems that the issue you had mentioned is that even if your moving between voodoo compatible roms, voodoo needs to be removed before.
This can be done within the handset with rom manager, using the voodoodisable.zip?
Cause ya, didn't quite understand that part till it happened. Feel pretty dumb when there is post after post of "PPL DUN FKN READ"
Sent from my SGH-T959 using XDA App
buggzero said:
Seeing some of your other posts in the bionix fusion rom, which is what I ended up flashing to, it seems that the issue you had mentioned is that even if your moving between voodoo compatible roms, voodoo needs to be removed before.
This can be done within the handset with rom manager, using the voodoodisable.zip?
Cause ya, didn't quite understand that part till it happened. Feel pretty dumb when there is post after post of "PPL DUN FKN READ"
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
It's simple to disable voodoo. When you have voodoo installed you should have a voodoo folder in your internal SD card, if you don't them make one. Put a file called disable-lagfix in there with no extensions. A blank file with that name. Reboot and you'll hear the.process going through of removing voodoo. Then you can flash what ever you like without any problems. If you want voodoo back delete the disable-lagfix file or rename it to enable-lagfix. Simple.
Sent from my SGH-T959 using XDA App
thx for ur sharing...
i hv the same problem, it's fixed now...
On my last 3 androids I usually got updates early and just flashed the zips in recovery on my stock androids. I've had a tough time figuring out the process on my vibrant though. Is it the same process with the vibrant? Because when I searched it seemed like Odin and kies were mentioned often but I haven't used either and I'm not sure where to start. Is there a simple zip of froyo I can flash on my stock vibrant? I really planned on waiting for the ota but at this point my nexus will have gingerbread first and then ill go back to using it daily again so I'd like to have some time with a more smooth and snappy, flash and tether enabled vibrant..
Check out the stickies
Chalup said:
Check out the stickies
Click to expand...
Click to collapse
Thanks, can you give me another hint?
Actually I did read the stickies thoroughly before i posted this thread, the closest thing i found were instructions for installing the 2.2 version of the market which was in the really long sticky so i maybe missed what youre referring to, that sticky said the first post was about root issues but i still looked through the entire thing, both posts. i also checked the sticky in the development section. I went back to double check just now but i still dont see information about flashing froyo on a stock vibrant if its even possible. and fyi here is what i found before posting my question, these are just a few of the threads i checked. There are some "stock froyo roms" but im pretty sure they are still mods requiring root. There are many "froyo" type threads in development section. Im still trying to figure out if its even possible to flash froyo if im not rooted
http://forum.xda-developers.com/showthread.php?t=836222
http://forum.xda-developers.com/showthread.php?t=837763
http://forum.xda-developers.com/showthread.php?t=833563
Download your desired rom and save it to internal or external sd card, back up everything u don't want to lose. Flash clock work recovery , reboot into clock
Work, go to install zip from sd card, choose yours, install then reboot, enjoy.
Sent from my SGH-T959 using XDA App
ronjeremy11 said:
Thanks, can you give me another hint?
Actually I did read the stickies thoroughly before i posted this thread, the closest thing i found were instructions for installing the 2.2 version of the market which was in the really long sticky so i maybe missed what youre referring to, that sticky said the first post was about root issues but i still looked through the entire thing, both posts. i also checked the sticky in the development section. I went back to double check just now but i still dont see information about flashing froyo on a stock vibrant if its even possible. and fyi here is what i found before posting my question, these are just a few of the threads i checked. There are some "stock froyo roms" but im pretty sure they are still mods requiring root. There are many "froyo" type threads in development section. Im still trying to figure out if its even possible to flash froyo if im not rooted
http://forum.xda-developers.com/showthread.php?t=836222
http://forum.xda-developers.com/showthread.php?t=837763
http://forum.xda-developers.com/showthread.php?t=833563
Click to expand...
Click to collapse
Honestly rooting isn't even that big of a deal, what I would suggest is to go download the one click root (or use One Click Lag Fix from the market), it really is simple.
I'm not sure how to use Kies (haven't used it myself), but odin is simple, this is the video that helped me when I first flashed it. I think ODIN is only used to go back to the stock firmware which you can find on the forum.
http://www.youtube.com/watch?v=AnY7P14JSWQ
To do the one click root, you turn on USB debugging and plug in your usb cable into your computer (don't mount the drives).
Open one click root and click root, it will copy over the files and do it's thing, then your phone will reboot into recovery mode and all you do is scroll down to "re-install packages" using the volume key and use the power key to select, then your phone will reboot once again and when it starts up you should be rooted (you'll have a super user app in your app drawer).
Then when you're rooted, you install Rom Manager from the market. After installing rom manager, flash the Clockwork Recovery (the very first option) and go download a froyo rom of your choosing from the development section. Right now, choose the option to backup your rom (just a safety net in case something goes wrong, you'll be able to come back to where you are now). When this is done, mount your phone on your computer and copy the back up to your computer. Then copy the downloaded rom to your internal sd.
Once you are flashed with clockwork recovery, all you have to do in rom manager is pick the option "Install ROM from SD Card" (assuming that you have already copied the rom to your internal sd card (not the microsd)). After this the phone should reboot and start the installation process. The advice given is to leave the phone alone for the first 15 minutes after it boots up, restart the phone, and wait another 5 minutes before messing with it.
Thank you. And just to be completely clear, i take ifrom the rooting instructions and affirmations that flashing a froyo image on an unrooted vibrant is not an option...In the past I have rooted my nexus and g1 so clockworkmod/flashing in recovery, this is all familiar, I'm guessing 1 click root is similar to the nexus version in that 1 click can unroot as welll? This all sounds good so I guess ill just try to sift through all the custom Froyo Rome in dev section and try to locate a stable and as stock as possible version. I'm going to wait until later on Monday, between now and then will be my last expressed hope of hearing an update about the existence of an official froyo ota update for the vibrant. But I've read a lot about Samsung and their odd software update complex so I wont be holding my breath. But come hell or high water I will soon have full adobe flash, tethering, a smooth UI , etc., e tc., etc.
I have rooted my Vibrant using ROM Manager/Flash CWM Recovery. (I'm running 2.2, Kernel 2.6.32.9, Build FROYO.UVKA6.) I used this method because no matter what folder on the external or internal sd card I could not use the 'reinstall packages' option on the reboot screen. Now, I'm trying to place the Bionx or Nero ROMs on my phone, but can't get anything to install no matter what I do.
I don't think I anything wrong with the root because I kept getting the same 'E:signature verification failed Installation aborted' message everyone else seems to be getting. I'm wondering if Samsung/T-Mo didn't put anything in to prevent rooting and adding new ROMs.
I have rebooted my phone multiple times and have not gotten any results. Along with ROM Manager, I have Busybox installed.
Please feel free to ask questions for more details. I'm a noob to rooting, so I definitely allow for the fact that I might have screwed something up and will need to start over.
PN
PrimeNemesis said:
I have rooted my Vibrant using ROM Manager/Flash CWM Recovery. (I'm running 2.2, Kernel 2.6.32.9, Build FROYO.UVKA6.) I used this method because no matter what folder on the external or internal sd card I could not use the 'reinstall packages' option on the reboot screen. Now, I'm trying to place the Bionx or Nero ROMs on my phone, but can't get anything to install no matter what I do.
I don't think I anything wrong with the root because I kept getting the same 'E:signature verification failed Installation aborted' message everyone else seems to be getting. I'm wondering if Samsung/T-Mo didn't put anything in to prevent rooting and adding new ROMs.
I have rebooted my phone multiple times and have not gotten any results. Along with ROM Manager, I have Busybox installed.
Please feel free to ask questions for more details. I'm a noob to rooting, so I definitely allow for the fact that I might have screwed something up and will need to start over.
PN
Click to expand...
Click to collapse
This is because you are now on 2.2. Samsung patched the exploit from 2.1 that allowed cwm recovery to be flashed. The best thing I can tell you to do since you have root would be to either
A) ODIN down to 2.1 ROM then root again, then install rom manager and from there you can install cwm recovery OR
B) Use this method I posted based on Supercurios voodoo kernels found here:
http://forums.t-mobile.com/t5/Samsung-Vibrant/on-steps-to-flash-Bionix-V-1-2/m-p/720803#M5807 (look for the answer marked solution - and because you have root skip ONLY that part and download the proper supercurio's zip not the tar).
Supercurio's vibrant kernels found here:
http://forum.xda-developers.com/showthread.php?t=870480
Do this before you try anything else, this is your quickest and least painful solution:
http://forum.xda-developers.com/showthread.php?t=833423
Then:
When you boot into recovery and hit Reinstall Packages, the phone might reboot back into recovery, Reinstall Packages again and it will take you to the mod recovery, no more sig. verification.
Congrats!
Thanks.....
roumenjr and mavsfan.
I was able to get the root done. I took roumenjr's suggestion and it worked once I figured out that I was placing the ROMs in the wrong folder.
Now running Bionix Obsidian v2.
oooops..............
EDIT [4-26-11]: Sorry guys for the delay on updating this thread. I currently have no free time, so defer to other threads for up-to-date information. I will probably be back in a couple weeks.
EDIT [4-8-11]: jt1134 has put a lot of work into fixing the mounting/filesystem/permissions issues over the last couple days. I will update this post as soon as he makes his latest compile available.
Original Post:
Because of the confusion over the different versions of ClockworkMod Recovery, I will try to address the major questions in this thread.
This all started out when some people started asking questions about why themed nandroid backups always had problems when they were restored (very informative thread detailing the process). After figuring out that something was broken in CWM, I decided to try to find it. Thankfully, it was an easy fix that me and jt discovered whilst chatting in the IRC. While I was poking around, I fixed a few other small problems too. Since then, jt has worked on making sure the mounting/permissions work right. I think we finally have a winner.
[SIZE=+1]Changelog[/SIZE]
Bug: The old CWM did not have root shell access because of a typo in the old initramfs, so this caused lots of issues when ROMs and themes did not set the correct permissions in their scripts. This is where most of the "Force Close" problems and boot loops came from when flashing roms and also when restoring Nandroids backups. Fix: corrected the init script typo from "ro.secure=01" to "ro.secure=0"
Bug: "Voodoo lagfix is actually: disabled" even when it is enabled. Fix: working (probably as a result of the root fix)
Bug: "Fix Permissions" script is broken. Fix: updated to new version and then modified to auto-mount the correct partitions and use correct files
Bug: Mounting menu typo "umount /dbdata". Fix: corrected to "unmount /dbdata"
Bug: Battery Stats wiping returns immediately to menu. Fix: added a print out to confirm to the user that battery stats wipe was ran
Bug: "Format Boot" option does not work. Fix: not compatible with the Fascinate, removed from menu
Bug: "Enable/Disable Puzzle LockScreen" does not work. Fix: no longer compatible, removed from menu
Bug: Miscellaneous quirks and issues. Fix: mounting and permissions code improved throughout, and making it more robust in handling ext4 and RFS configurations.
[SIZE=+1]Frequently Asked Questions[/SIZE]
Q: After I enter CWM, it says I am at version 2.5.1.x. Does that mean I'm on the correct version?
Unfortunately, the last several updates have been minor bugfixes, and the version number has stayed at 2.5.1.x. Hopefully this will be remedied soon. An easy way to check is to go to "Advanced" menu. If you don't see "Enable Puzzle LockScreen", then you are on the newest version (this menu option was removed because it has not been functional for a long time).Q: Does battery stats wipe work yet?
It was working on the on the old CWM, it just didn't give you a confirmation after wiping. If for some reason it wasn't working on the old CWM recovery (because of the ro.secure bug that was fixed), then I can definitely confirm that it is working now.
In the newest fix, I added a notification before returning to the menu that tells the user that the battery stats had been wiped.Q: Does Fix Permissions work yet?
If you select "Fix Permissions" you should see it doing a lot of work (should take 1-2 minutes). If it returns to the menu immediately, it means one of two things:
You just wiped /data or /dbdata, in which case, there is nothing to fix permissions for (completely normal)
Your /data or /dbdata partition is unable to mount, which means you may have had a bad voodoo conversion, or something that will probably require Odining back to stock to repair (not normal)
Q: I have the new CWM and the feature you said was fixed doesn't work!
Maybe, but I'm guessing you have an old copy, or you have flashed a file that has overwritten your recovery partition to an old version. That's why I have included the SuperClean ROM's with the updated CWM, because most people don't know about this. If you prefer to not re-download the whole SuperClean file, you can take the zImage2 file from the CWM ZIP file and drag and drop it into the /kernel_update/ directory in your current SuperClean file.
[SIZE=+1]Most Thorough Method of Fixing Every Problem You Might Have[/SIZE]
If you have an issue with applications force closing or a continual boot loop, a lot of times you can fix this issue by running the Fix Permissions option.
However, if you would like to see your phone be able to have fully functioning Nandroids, and less problems with permission related errors when flashing different ROM's, I encourage you to do the following (this will make your phone as clean and healthy as possible):
Download to PC
CWM-Recovery Odin Package
MD5 Checksum:
CI500_VZW_EB01_FROYO_REL.tar.md5
MD5 Checksum: d04733ce540ab1af291cfa44d42c768e
atlas_v2.2.pit
MD5 Checksum: a0eaf496375cf72b90f7ceef4f0a4538
Place on /sdcard
ROM of your choice
MD5 Checksum:
Now that's done, on to the fun part....
ODIN the full stock EB01 package in PDA, the atlas_v2.2.pit in PIT, and "Re-Partition" checked
Let your phone fully boot into the OS and verify everything is working correctly
Remove your battery
ODIN the CWM Recovery package
Unplug USB Cable, THEN reinsert your battery
Hold both the volume keys and the power button down until a second after you see the Samsung boot logo, then let go
It should now boot into red CWM recovery
Wipe Cache/Dalvik Cache only. Flash the ROM of your choice
Reboot. Since you have installed the Voodoo ROM, then you should hear a Sexy Robot lady telling you that she is converting your partitions. This process will take 10 minutes or so. If you pull the battery, you will have to start all over again.
Let your phone fully boot into the OS and verify everything is working correctly
If you need to install a theme, reboot; enter CWM; wipe Cache/Dalvik Cache only; enter CWM; flash theme
If you need to install a kernel, reboot; enter CWM; flash kernel
Make a fresh nandroid backup. If you try to restore a Nandroid made with the old CWM, you will probably have problems.
I haven't gone into the specifics of how to do all the above, because there are several tutorials with pictures and well-written guides already in existence.
[SIZE=+1]A couple of things about ClockworkMod Recovery that a lot of people don't know[/SIZE]
The CWM package in this post is the ONLY CWM file you ever need, for any Samsung Fascinate ROM. Even Eclair ROMs. Even Non-Voodoo Roms. Doesn't matter. Delete all your old copies.
When you flash a CWM Recovery, you are writing an entire kernel into the recovery partition of your phone (bml8). This does not affect your current kernel because it is stored on your kernel partition (bml7).
When you download a ROM, it is up to the ROM author to decide if they want to include a kernel and/or CWM. For example, SuperClean bundles the ROM/Kernel/CWM all into one flash file. When you flash SuperClean, it will overwrite your kernel partition (bml7), your recovery partition (bml8), and your system partition (stl9).
[SIZE=+1]A few other questions that might get asked[/SIZE]
Q: What is that MD5 gibberish under the download links?
A: MD5 (and other checksums/hashes) can be used to verify the integrity of a downloaded file. Basically, you download the file, then use an MD5 tool to calculate the checksum. You then compare the file's checksum to the checksum I have posted under the link. If it matches, then you know that your download is not corrupt.
The whole process is much easier/quicker then it sounds, even if you've never done it before. Also, there are many free MD5 calculators (I use HashCheck).Q: Is this CWM 3? Why isn't my menu orange?
While this is the newest fully compatible CWM for the Fascinate, it has NOT had any of the CWM 3.0 code base ported into it. As of CWM 3.0, Koush ripped Amend scripting support for flashing. Most of the rest of the world has already moved to Edify scripts, but in Samsung Fascinate land, we still cling to Amend scripts in a lot of our ROM/patch flash files because of some of the issues that Edify has had with the way Samsung laid out the partitions and devices. This is why we have stuck with CWM 2.5 for so long, because so many ROMs, themes, and patches are still using Amend scripts.
Really though, its time to merge the CWM 3.0 base, port the voodoo options, cut ties with amend, and get the Samsung Fascinate's funky mounting/partitions/layout fully compatible with CWM. Someone just has to do the work, because Koush doesn't seem to be that interested in it any more.
There are a lot of improvements in the back end of CWM 3.0 that make it more reliable. Also, if someone were to be slightly ambitious, there are quite a lot of previously unseen (on the Fascinate) features that could be ported from other people's CWM mods. One easy one would be backup and restore of the kernel, which would allow for a more complete Nandroid. It's actually already half-way implemented in the code, so it wouldn't take much more work to get it done, even on the current version.
Then there is the EFS partition... which is a subject avoided by most people but is an important aspect of the phone that no one currently is backing up. There has been a lot of work done for the other SGS variants, but no one has really spoken up about it in the Fascinate world.Q: Will this overwrite my kernel/custom kernel files on my system partition/knock up my daughter?
The CWM ZIP package has been cleaned of the system files, and the ODIN package has been correctly configured to flash to the recovery partition only. SuperClean will behave like normal, which involves flashing your kernel/CWM/system/daughter.
Until Adrynalyne and jt1134 adopt these files (or make their own), then this applies to files that are downloaded from the links provided in THIS THREAD ONLY.
Q: Why did you start a new thread for this?
Because in the main threads, I answer the same questions every 20 posts. This is more visible. If this information is merged into Adrynalyne's SuperClean thread and JT1134's CWM thread, I will ask for a mod to close this thread.
Good job
I‘m done with the 2.3 ROM!
How foooooolish I am
So..... I'm currently running sc 2.9.2 with voodoo ..... Do I need to just flash the sc + voodoo update in cwm? Wipe data/cache/dalvik?
Sent from my SCH-I500 using XDA App
Nice write up. This should help a lot of people have a better understanding (assuming they actually read it).
chefthomas99 said:
So..... I'm currently running sc 2.9.2 with voodoo ..... Do I need to just flash the sc + voodoo update in cwm? Wipe data/cache/dalvik?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
well if you want to do it the way he spells out in the op, you need to do alot more. flashback to eb01 is the first step. just follow the steps.
thanks for this. a new thread was very needed aswell.
Is the recovery-all zip dated 3-30 in this post any different from the modified one for custom kernels that you posted in jt's thread a couple days ago?
garywojdan81 said:
Is the recovery-all zip dated 3-30 in this post any different from the modified one for custom kernels that you posted in jt's thread a couple days ago?
Click to expand...
Click to collapse
Let's just go ahead and assume that there are no files outside of this thread that are identical to the files in this thread.
Even though that may not be exactly true, most people do not know what version of the file they have, since they all have the same file names. This is another reason why I provided the MD5 checksums, since that is a unique identifying mark.
If you ran the MD5 checksums on all the files, you maaay just find that the ODIN file in this thread is identical to the ODIN file in JT's thread. Since he first posted a very naughty ODIN that overwrote your kernel instead of recovery, I'd like people to just assume that they should trash every CWM file they currently have and download it fresh.
This isn't a april fool's joke is it? I would be sad.
RacerXFD said:
This isn't a april fool's joke is it? I would be sad.
Click to expand...
Click to collapse
lol. where as i dont think he would ruin a good joke, i dont think would go this far to make a joke. gizmo is a pretty straight forward and generally helpful guy.
Not that there is anything wrong with using recovery stand alone...
The post I am waiting for is the one that tells me how to setup Rom Manager to work with _any_ froyo+ rom kernel combo, be it via red cwr our blue cwr or a well placed recovery-update.zip. I thought I had this working once but it is gone.
soba49 said:
Not that there is anything wrong with using recovery stand alone...
The post I am waiting for is the one that tells me how to setup Rom Manager to work with _any_ froyo+ rom kernel combo, be it via red cwr our blue cwr or a well placed recovery-update.zip. I thought I had this working once but it is gone.
Click to expand...
Click to collapse
If somebody can make recovery-update.zip from this recovery and paste it over rom
manager, it might just work.
uslacson1 said:
If somebody can make recovery-update.zip from this recovery and paste it over rom
manager, it might just work.
Click to expand...
Click to collapse
"Might" is the key word there.
ROM Manager sends commands to CWM on reboot. If you try to mix a new ROM Manager with any CWM before 3.0, it might use different syntax in the commands. Sure, it will probably work most of the time, but why take that chance?
The only real solution is for someone to port the CWM 3 stuff. Project voodoo already has quite a bit done on it, it just needs to be adapted to the Fascinate.
After that, Koush would probably be more helpful at helping us get the code successfully pushed into the CWM that ROM manager downloads.
gunnermike said:
lol. where as i dont think he would ruin a good joke, i dont think would go this far to make a joke. gizmo is a pretty straight forward and generally helpful guy.
Click to expand...
Click to collapse
Haha, pretty much. I'm a jokester in real life, but interwebz is serious business.
I think a more important point is that I wouldn't spend 4 hours typing this post if it were a joke xD
Thanks for posting this to clarify the why fors and the what nots. So its more than edify and amend scripting that's holding us back from an official CW recovery we need to have project voodoo updated as well for 3.x compatibility? Reminds me of the slcd Incredible issues we had. That has only been sorted out for a month or two. (amoled/slcd) Anyway thanks for this post it really does clear up some questions/concerns.
Sent from my SCH-I500 using Tapatalk
thanks for this thread. helps alot.
GizmoDroid said:
Haha, pretty much. I'm a jokester in real life, but interwebz is serious business.
I think a more important point is that I wouldn't spend 4 hours typing this post if it were a joke xD
Click to expand...
Click to collapse
Gizmo,
As much as I would love to trust your new CWM... I can't trust anyone today. In fact, I'm running to the basement as we speak with my aluminum foil hat. Please understand that no words that come out of anyone's mouth can be taken with any seriousness.
On that note, your CWM recovery works fantastic.
I appreciate it! Thanks.
ODIN the full stock EB01 package in PDA, the atlas_v2.2.pit in PIT
Where might these be found?
So, I tried step 1. I flashed, via Odin, the stock EB01 tar from adyn's stock post. Also pulled the atlas_v2.2.pit from his "how to fix brick after 2.7" post. I believe I'm bricked. I selected repartition, pit in pit section, eb01 tar in pda section. My phone now boots directly into the samsung stock recovery. I don't get a samsung boot logo either. I can get into download mode via holding down vol-down, but no matter what I flash now to try to bring my phone back to life, I'm still stuck. Has anyone run into this? I'm not a noob when it comes to Odin, so I don't believe I've made any mistakes.
EDIT: Ugh, I flashed what I thought was the full EB01 stock rom. It was the pre-rooted version I found a while ago. When flashed with the atlas v2.2 pit, it soft bricked the phone. So, just a suggestion for the OP that you can get the needed EB01 tar and atlas files from adryn's post on fixing your phone after it's borked with SC 2.7: http://forum.xda-developers.com/showthread.php?t=977493
I'll shut up now.
Needing some help with 3eRecovery. I understand every thread I've read on how to do these things, but it doesn't work the way everyone says. Explanation below.
____________________________________________
I'm definitely rooted... have superuser and test with Terminal Emulator. su works fine. Even tested root with Titanium Backup. It works.
Trying to install 3e recovery, to get CWM3, to get KA6+voodoo kernel. 3e recovery installer fails root check every time.
From what I've read, if you're already permanently rooted, the modified 3e recovery installer would stop checking for temporary root. This is clearly not the case here. I've even tried running SuperOneClick to shell-root the device, which it succeeds at, but this does not change any results from the 3e recovery installer.
I have even used Odin3 to start from scratch on the machine, taking it all one step at a time, back from the original Eclair ROM+KRNL, Kies upgrade to KA6, SuperOneClick.
oh, and yes, I've tried installing the KA6 stock+voodoo kernel through Odin. Odin says it succeeds, the phone reboots, but there is no difference. I've installed the Voodoo Control app, but it shows that there's no Ext4 conversion. Am I doing something wrong? Is my phone doing something weird?
I really wanna get rid of the rfs system. absolutely hating it. There are two images attached proving root and showing results of 3eRecovery
I'm obviously studying the XDA Vibrant Bible, but here's some other links I'm using:
http://forum.xda-developers.com/showthread.php?t=833423
http://forum.xda-developers.com/showthread.php?t=870480
Did you try reboooting into recovery to see if you have it properly installed?
definitely have... plus it fails at the temp root check, would it do that if the 3eRecovery were installed properly? I'd think it'd fail later.
and yes, I've tried installing CWM3 through Rom Manager a couple of times after attempting the 3eRecovery, and the "install package" choice repeats and repeats and repeats, I never see the CWM Recovery.
Is it telling you there's no more room in /system? Remove a bloat app like Slacker Radio to free up some space if you haven't already. Good luck!
Sent from my rough sketch of a Vibrant on a brick.
no... I saw that message once a while back, before I restored to original krnl and rom, the jfd one I think. but since I did that and started from scratch, this is the first problem I've run into.
Q: if I use the 512 pit file with the KA6+voodoo krnl tar found here (http://forum.xda-developers.com/showthread.php?t=870480) in Odin v.1.7, shouldn't that accomplish the same thing as cracking the recovery and using CWM to load up the zip version? when I try to use the Odin version, nothing changes? is that what you mean when you ask if my /system is full?
I'll remove some apps (i use Slacker) like Ads to Home, T-Mobile TV, etc. I'll let you know if Odin works any better. but I don't anticipate anything changing.
She issue here. CWM won't install, even after a supposed 3e flash.
-bZj
XDAapp
down8 said:
She issue here. CWM won't install, even after a supposed 3e flash.
-bZj
XDAapp
Click to expand...
Click to collapse
except mine won't even let me flash the 3e.
fail.
Did you enable usb debugging?
Sent from my SGH-T959 using XDA App
yep. absolutely.
Lol. I tried replying with just "yes," but there's a ten character minimum to posts. Ha (easily amused here)
Repartition choice in Odin
For others suffering this and other seemingly unfathomable problems with a Galaxy S phone... reset phone to official/full/original ROM+KRNL (JFD in my case) and use the re-partition choice in Odin. after I did that, I rerooted with SuperOneClick, installed a Terminal Emulator, and manually removed some of the bloatware that came with it.
Don't know which one of these fixed it, but the 3eRecovery installer worked after that... I downloaded the ROM Manager again, did the CWM that is included with that, had to click "reinstall packages" twice, but then it worked.
Thanks for the tip Droidificator. Don't know for sure if it's it, but I'm sure it didn't hurt.
___________________________________________________
lol... great irony in all of this is that Kies updated my phone to KB5 instead of KA6, so now I'm looking at using OCLF for the ext2 tools for now.
any advice on where to go from here to have the most efficiency out of this phone from the KB5?
make sure that a current version of busybox is installed. i had an issue with this when i ODIN'd back to stock and re-rooted. good luck with everything!