I've been at this for like 3-4 hours and have gotten NOWHERE.
Okay, so I wasn't always rooted, I waited and waited and waited for Froyo, thinking it was going to be awesome - then it OTA'ed to me, and I've had NOTHING but problems. Battery life went down like 1/2 as much (if not more) on a good day, problems with the vibrations, ring volumes, some parts are laggier, the largest problem is that the new radio image SUCKS and the newest thing, there's some texts and calls that it never gets. I've never seen such a failed update in my entire life. /rant
Anyway, I've been searching and searching and searching so pleeeeeeeeeeeease don't tell me to search anymore.
I'm interested in putting the Ultimate KangBang 2.1 on my phone (end result). So that requires 2.0 as it's a patch - fine.
So first, yes, my phone is rooted, I can run su and get a root shell on my phone (if that's proof I guess?).
The clockwork mod is KILLING me, though.
The problem is I have version 3e of the recovery mode thing which is stopping unsigned files. I've been trying to get clockwork mod 3.X installed for easily the last 2 hours and had nothing but dead links or nothing happened.
I thought I found the answer a little while ago, using this write-up on installing the clockwork mod, I downloaded cwm-recovery-ALL.tar, and pushed it to the phone with Odin, unplugged it upon successful flash, restarted it, held vol down and power, nothing. Eventually holding up (I think it was up) and power got me to standard samsung recovery mode (ie. it did jack ****). Never-the-less, I went in and used the ROM manager to install clockwork mod 3.X, it said it worked..but it didn't.
I can't install things via update of root because I have 3E of the recovery, and I can't get clockwork mod to work for the life of me. I've been googling the **** out of everything I can think of to get the clockwork mod to work, but have come up with outdated forums, or broken ass links.
NOTHING WORKS!
The only think that worked (once) was when I used "reboot into recovery mode" from ROM manager, it rebooted into clockwork recovery..but upon reboot again it booted into the standard recovery mode.
How the HELL do I get the clockwork mod on my phone because believe me when I tell you I've searched and I have a plethora of useless ass tabs cluttering my browser all being completely useless.
Please help
Yes, I'm sure this has been covered "many times" before, but I can't find a single one that works.
TIA :'(
Do you have gtalk ?
All you have to do is download (google) odin http://download1422.mediafire.com/ii...din3+v1.83.exe (its a program made by samsung) and a odinable recovery.tar from this site http://dl.dropbox.com/u/36791/CWM3_Voodoo.tar.md5
Then in odin you place the recovery.tar in the pda section dont click any other things NEVER EVER CLICK PHONE then hit start once it says pass on odin you unplug your phone from the usb and exit odin then put the battery back in and boot directly into recovery ( press/hold the buttons volume up+down and power at the same time) then wipe data/factory reset in recovery then flash either a kernel or rom to make the recovery stick.
Make sure you already have a rom or kernel on your sdcard.
I'm not the best at explaining things but i know exactly what you need to do.
abrixxxx said:
Do you have gtalk ?
All you have to do is download (google) odin (its a program made by samsung) and a odinable recovery.tar from this site.
Then in odin you place the recovery.tar in the pda section dont click any other things NEVER EVER CLICK PHONE then hit start once it says pass on odin you unplug your phone from the usb and exit odin then put the battery back in and boot directly into recovery ( press/hold the buttons volume up/down and power at the same time) then flash either a kernel or rom to make the recovery stick.
I'm not the best at explaining things but i know exactly what you need to do.
Click to expand...
Click to collapse
I'm not trying to be a douche, I know you're trying to help, but can you re-read (or initially read) the 8th paragraph in my post? I know the post is a bit long, but I tried slimming the post down a bit :-\.
EDIT:
gtalk as in the voice program? No, it's not installed on my desktop nor my phone - I use Skype for voice/vid and AIM/gmail for chat.
You're liable to get help more quickly (and with less flaming) if you post questions in the correction section -- please see this stickied thread: http://forum.xda-developers.com/showthread.php?t=1038478
As far as your issue goes, your first problem is that you don't actually want to use ROM Manager. Koush's recoveries no longer work with this phone. The working CWMs for the Fascinate are all modded and have to be downloaded and flashed via ODIN (or another modded CWM).
jt's recovery is closer, but that's still an old version. The most functional pre-packaged one right now is at the top of this post: http://forum.xda-developers.com/showthread.php?t=1046905
Just follow the instructions in that post, and you should be good.
Oh, one other thing -- it doesn't sound like you were using the correct key combination for CWM, so that's probably why jt's wouldn't boot. It's all three keys: power+vol up+vol down, not just power+up or down.
Completely forgot to include the phone specs, my mistake:
Recovery Version: 3e
HW Version: I500.05
Model #: SCH-I500
Firmware Version: 2.2.1
Baseband Version: S:i500.05 V.ED04
Kernel Version: 2.6.32.9
Build Number: SCH-I500.ED04
Just a note on that build number, one of the clockwork mod posts had a whole list of CWM's which were like JYX, JYZ, stuff like that, and they were like "pick whichever cwm matches your phone's build #, blah blah" My phone's build # has no J's in it, and I didn't want to brick it.
Did you boot directly into recovery after putting your battery back in ? You can't boot into the OS before going straight to recovery from odin or else it overwrites the custom recovery with the samsung one.
Falcyn said:
You're liable to get help more quickly (and with less flaming) if you post questions in the correction section -- please see this stickied thread: http://forum.xda-developers.com/showthread.php?t=1038478
Click to expand...
Click to collapse
My mistake, I read that when I initially joined, but forgot about it when I posted .
Falcyn said:
As far as your issue goes, your first problem is that you don't actually want to use ROM Manager. Koush's recoveries no longer work with this phone. The working CWMs for the Fascinate are all modded and have to be downloaded and flashed via ODIN (or another modded CWM).
Click to expand...
Click to collapse
So ROM Manager is completely useless now?
Falcyn said:
jt's recovery is closer, but that's still an old version. The most functional pre-packaged one right now is at the top of this post: http://forum.xda-developers.com/showthread.php?t=1046905
Just follow the instructions in that post, and you should be good.
Click to expand...
Click to collapse
I'll take a look at that now.
Falcyn said:
Oh, one other thing -- it doesn't sound like you were using the correct key combination for CWM, so that's probably why jt's wouldn't boot. It's all three keys: power+vol up+vol down, not just power+up or down.
Click to expand...
Click to collapse
Confirmed 3x, holding down power + vol-up + vol-down starts the OEM Android recovery mode (ie. Android system recovery <3e>). From what I understand about the CWM, once it's installed and working, I should never see this screen again, it should always be the CWM boot screen, no?
abrixxxx said:
Did you boot directly into recovery after putting your battery back in ? You can't boot into the OS before going straight to recovery from odin or else it overwrites the custom recovery with the samsung one.
Click to expand...
Click to collapse
I don't recall, actually, I'll try that now before I check out JT's recovery.
Same as above. But also hold all three buttons and wait for samsung logo to turn on off and back on then let go.
Sent from my SCH-I500 using Tapatalk
Most likely you booted into the OS then powered down then did the 3 button method which would make the samsung recovery overwrite the one you odin'd.
Do this odin the recovery.tar I linked then when you put the battery back in hold volume up+volume down then press power as well make sure you're holding all three at the same time no just two of them. If you go to the custom recovery good job if it boots into the OS try again there is no way it should boot into the 3e recovery if the recovery is being flashed via odin and says pass.
Yes ROM Manager is 100% useless for us fascinate users.
Okay, I did that after flashing it with Odin (without letting it boot the OS) and "CwM Lagfix 2.5.X" came up. I then tried rebooting the phone and didn't hold it down and then it went into the OS. I then shut it down, pulled the battery, and held all three buttons again, but it brought up the standard Android recovery system .
From what I understood the clockwork mod was permanent, but everything I've seen on my phone makes it only temporary. Am I doing something wrong?
2.5? That's an even older version. What link did you use? The one I gave you: http://forum.xda-developers.com/showthread.php?t=1046905 is a 3.x.
And yes, ROM Manager is essentially useless for our phone.
EDIT: You could always just ODIN the whole UKB 2.0 package, too, which will get you jump-started with CWM, a new kernel, and obviously the ROM itself:
http://www.mediafire.com/?a63v435opsaq3g3
Falcyn said:
2.5? That's an even older version. What link did you use? The one I gave you: http://forum.xda-developers.com/showthread.php?t=1046905 is a 3.x.
And yes, ROM Manager is essentially useless for our phone.
EDIT: You could always just ODIN the whole UKB 2.0 package, too, which will get you jump-started with CWM, a new kernel, and obviously the ROM itself:
http://www.mediafire.com/?a63v435opsaq3g3
Click to expand...
Click to collapse
Yeah, I first tried it with the package I was working with from the thread I linked to in the OP from here.
Doesn't matter, though, same thing happened. I used the package in the link you gave me, flashed it to the phone, rebooted into recovery, worked fine with 3.X, then rebooted it and let the OS load, then powered it off, then tried to reboot into recovery and I got the standard Android system recovery.
Unless I'm missing something this "Android recovery system <3e>" should never be seen again, but it seems like the CWM flashes I'm doing are volatile on OS loads.
I'll check out that link now.
FINALLY!
I installed UKB 2.0 and CWB worked at first...so then I hit "Reboot" and loaded the OS. The OS loaded (UKB) and then I held the power button, and hit "recovery mode." This restarted it, but it loaded into "Android recovery system" - I was about to kill somebody, but then I noticed it was 2e, not 3e. So I took the CWM 3.0 and flashed it back, and now, whether I hold all three buttons or hit "recovery mode" from the hold power menu in the OS, it boots into CWM 3.0.
I'd like to say I think I've seen the last of the Android recovery system - but I know I haven't .
The only thing I can't figure out is why it has ARS 2e AND CWM on it. Seems like they're direct replacements for one another...I would say the UKB 2.0 ROM shipped with just ARS 2e and that was that - but it showed the CWM 3.0 before I loaded the UKB OS.
Is the ARS sitting "under" the clock work mod? Or are they direct replacements for one another?
EDIT:
Also, which 2.0 ROM was that? I've been using this page as reference. That seems like the official page for that ROM. None of the 2.0 ROMs there are the link you gave me, though. I'm just curious if I should update the kernel or not, as the ROM either A) Didn't update it, or B) Included the same version. While I'm asking a question a second here, what is the PBJ setting and the OTB? I'm assuming OTB means out of the box, but I could be wrong, and I believe PBJ has something to do with power or under/overclocking, but I'm not quite sure..and even with the word android, google turns up lots of results for sandwiches under the query..
I do know that for a time we had to boot into the stock recovery, hit "update.zip," and then we'd reboot into CWM so at least at one time they did run side-by-side... but I honestly don't know if stock recovery is completely replaced now or if it just gets ignored.
Anyways, that was the official UKB/CR 2.0 ROM, but the ODIN file wasn't put together by TSM as it contains all the other components too. landshark68 packaged that up and his packages are all reliable.
As far as the kernel goes, the one included in what you flashed is a non-Voodoo PeanutButta Jelly Time kernel with a -50mv voltage reduction to help with battery life. That's a regular speed (1ghz) kernel.
Only The Brave (at first I thought it stood for Out of The Box too, go figure) is a more customizable kernel that can be both overclocked and voltage-reduced but starts out with neither.
I would recommend sticking with the PBJ kernels, personally, as they're actually good out of the box without having to play around with voltage controls manually.
The only reason you'd really want to switch kernels now is if you want to go to Voodoo... the PBJ kernel that ODIN file set you up with isn't.
The key to making cwm permanent is replacing the stock kernel. You can odin anything you want but if you leave the stock kernel it will overwrite your recovery every time it boots. Any of these custom kernels that are packaged in ukb roms should have the proper cwm included, but it may not hurt to update the recovery as new ones become available.
Sent from my SCH-I500 using XDA App
Syndacate said:
While I'm asking a question a second here, what is the PBJ setting and the OTB? I'm assuming OTB means out of the box, but I could be wrong, and I believe PBJ has something to do with power or under/overclocking, but I'm not quite sure..and even with the word android, google turns up lots of results for sandwiches under the query..
Click to expand...
Click to collapse
^^That's hysterical! Haha, I LOL'D when I saw that. I promise I'm not being an ass. PBJ stands for imnut's peanut butter jelly time kernel, and OTB stands for nemesis2all's Only The Brave kernel. If the package you flashed did not come with either one of those 2 custom kernels, you need to flash one. Either OTB 1.6 for Touchwiz based roms, or one of imnuts' PBJ kernels. Since I usually always use OTB, I'm more familiar with it and I know that it will permanently install CWM 3 for you upon installation and then you should no longer have any problems with stock recovery replacing your custom recovery. I'm pretty sure that PBJ does the same thing, but I dont know for sure as I havent used it. If you want full overclocking/undervolting abilities, you should probably flash OTB.. PBJ is not overclockable, I dont think, but again I could be wrong.. OTB gives you full control of voltage used for each frequency step available using the app "voltage control."
Oh, and voodoo, too. OTB kernels are all voodoo-enabled. Now you can run OTB kernels with voodoo disabled manually in recovery under the voodoo options, but with hiw good and reliable voodoo has become, and considering how much it speeds up your phone, im not really sure why anyone would use a galaxy s phone without voodoo or ext4 formatted partitions at least. But thats just me, as I realize some people prefer standard non-voodoo kernels.
To sum it up, I know for fact that using OTB kernels will replace stock recovery with CWM3 voodoo-enabled recovery, and you wont have it reflashing stock recovery like stock kernels do (which is the reason for the problems you were having).. PBJ might do the same thing, but im not sure because they're not voodoo kernels so I don't know if the PBJ kernels actually replace/update your recovery partition like OTB does. Either way, PBJ will not reflash stock recovery once you have a custom CWM kernel flashed, so as long as you do that you should be good to go.
Anyway, I hope you got it working right by now. I just thought that was utterly hysterical when I read that part about whenever you google for PBJ kernel that it comes up with a lot of results about sandwiches. Hahaha, that's classic.
Tbh this guy if he can't handle this stuff he will eventually brick his phone and cry bloody murder. Their is an all in one which I don't know why you didn't flash that.......
Sent from my SCH-I500 using Tapatalk
abrixxxx said:
Did you boot directly into recovery after putting your battery back in ? You can't boot into the OS before going straight to recovery from odin or else it overwrites the custom recovery with the samsung one.
Click to expand...
Click to collapse
I bet this is the source of much of your frustration.
You need to go straight to recovery and flash a kernel - the stocker is putting the samsung recovery in place before you get to cwm...
Swyped...
Falcyn said:
I do know that for a time we had to boot into the stock recovery, hit "update.zip," and then we'd reboot into CWM so at least at one time they did run side-by-side... but I honestly don't know if stock recovery is completely replaced now or if it just gets ignored.
Anyways, that was the official UKB/CR 2.0 ROM, but the ODIN file wasn't put together by TSM as it contains all the other components too. landshark68 packaged that up and his packages are all reliable.
As far as the kernel goes, the one included in what you flashed is a non-Voodoo PeanutButta Jelly Time kernel with a -50mv voltage reduction to help with battery life. That's a regular speed (1ghz) kernel.
Only The Brave (at first I thought it stood for Out of The Box too, go figure) is a more customizable kernel that can be both overclocked and voltage-reduced but starts out with neither.
I would recommend sticking with the PBJ kernels, personally, as they're actually good out of the box without having to play around with voltage controls manually.
The only reason you'd really want to switch kernels now is if you want to go to Voodoo... the PBJ kernel that ODIN file set you up with isn't.
Click to expand...
Click to collapse
Gotcha, now a Voodoo kernel just has the lagfix and other Voodoo project items bundled into the kernel?
garywojdan81 said:
The key to making cwm permanent is replacing the stock kernel. You can odin anything you want but if you leave the stock kernel it will overwrite your recovery every time it boots. Any of these custom kernels that are packaged in ukb roms should have the proper cwm included, but it may not hurt to update the recovery as new ones become available.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Gotcha, so now it's permanent (yay)
wilshyre said:
^^That's hysterical! Haha, I LOL'D when I saw that. I promise I'm not being an ass. PBJ stands for imnut's peanut butter jelly time kernel, and OTB stands for nemesis2all's Only The Brave kernel. If the package you flashed did not come with either one of those 2 custom kernels, you need to flash one. Either OTB 1.6 for Touchwiz based roms, or one of imnuts' PBJ kernels. Since I usually always use OTB, I'm more familiar with it and I know that it will permanently install CWM 3 for you upon installation and then you should no longer have any problems with stock recovery replacing your custom recovery. I'm pretty sure that PBJ does the same thing, but I dont know for sure as I havent used it. If you want full overclocking/undervolting abilities, you should probably flash OTB.. PBJ is not overclockable, I dont think, but again I could be wrong.. OTB gives you full control of voltage used for each frequency step available using the app "voltage control."
Oh, and voodoo, too. OTB kernels are all voodoo-enabled. Now you can run OTB kernels with voodoo disabled manually in recovery under the voodoo options, but with hiw good and reliable voodoo has become, and considering how much it speeds up your phone, im not really sure why anyone would use a galaxy s phone without voodoo or ext4 formatted partitions at least. But thats just me, as I realize some people prefer standard non-voodoo kernels.
To sum it up, I know for fact that using OTB kernels will replace stock recovery with CWM3 voodoo-enabled recovery, and you wont have it reflashing stock recovery like stock kernels do (which is the reason for the problems you were having).. PBJ might do the same thing, but im not sure because they're not voodoo kernels so I don't know if the PBJ kernels actually replace/update your recovery partition like OTB does. Either way, PBJ will not reflash stock recovery once you have a custom CWM kernel flashed, so as long as you do that you should be good to go.
Anyway, I hope you got it working right by now. I just thought that was utterly hysterical when I read that part about whenever you google for PBJ kernel that it comes up with a lot of results about sandwiches. Hahaha, that's classic.
Click to expand...
Click to collapse
Yeah, I think in PBJ it's set in stone, because there's different PBJ UKB ROM's with +/- voltages, so I'm guessing it's a packaged thing that's compiled into the ROM.
I believe I saw Voodoo in CWM on this Kernel. Guess it's just the OEM version with whatever PBJ fixes, and Voodoo packed into it.
Maybe at some point I'll try OTB, it definitely seems like a nice touch to be able to adjust your clock on the fly. Though I wonder if there was a particular reason why UKB only offered PBJ kernels and no OTB ones :-\.
tonu42 said:
Tbh this guy if he can't handle this stuff he will eventually brick his phone and cry bloody murder. Their is an all in one which I don't know why you didn't flash that.......
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Bite me.
I was "into the rooting game" for like 4 hours before making that post.
It's hard to just "pick up" random tid-bits of information from forum threads - because everybody uses TLA's and if you're new to it, you don't know what all those TLA's mean.
So while it's possible that I brick my phone at some point, that's a risk I'm taking, so in other words I should PM your ass in like a year when my contract is up and I get a new phone and tell it to stick it up your ass sideways.
AND, if you read (which you didn't), you'll see I already flashed the all in one and am running 2.1 perfectly stable now. Why did I not flash the all in one? I didn't know about the all in one. If I had, I probably would have done that a long time ago.
If you're not the one doing the hacking on the ROMs then 80% of the battle of "rooting/hacking android phones" is simply the act of knowing what's out there, different patches, compilations, images made by different people, issues, successes, etc. between different packages. So if you're like me, and busy, and can't always afford to read the latest and greatest, it puts you as a disadvantage.
So in short, shove it.
M00NEY said:
I bet this is the source of much of your frustration.
You need to go straight to recovery and flash a kernel - the stocker is putting the samsung recovery in place before you get to cwm...
Swyped...
Click to expand...
Click to collapse
Yeah, go figure . Didn't think the OS booting re-wrote the recovery partition/sector on boot, from an OS perspective, that's just weird.
Related
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.
Girlfriend got a Fascinate yesterday and deemed me worthy enough to root it so she can kill all the bloatware (yay for me!). I've got root on the phone, and I understand that if I don't flash a custom kernel for the phone, it'll just break the recovery (using "cwm-recovery-all.tar") as soon as the phone boots up. She likes the overall touchwiz experience and all that, so I'm not sure of any rom's that are pretty stock cept for bloat, and any kernels I should use so recovery doesn't break.
I'm just concerned about getting recovery to stick so that I can perform a backup in case anything should happen.
I have a OG Droid, so all this bending over backwards for root and recovery is new to me and threads seem either too full of info or not enough for me, so here's me asking for help!
Either way, thanks!
Dustin
seraph_harim said:
Girlfriend got a Fascinate yesterday and deemed me worthy enough to root it so she can kill all the bloatware (yay for me!). I've got root on the phone, and I understand that if I don't flash a custom kernel for the phone, it'll just break the recovery (using "cwm-recovery-all.tar") as soon as the phone boots up. She likes the overall touchwiz experience and all that, so I'm not sure of any rom's that are pretty stock cept for bloat, and any kernels I should use so recovery doesn't break.
I'm just concerned about getting recovery to stick so that I can perform a backup in case anything should happen.
I have a OG Droid, so all this bending over backwards for root and recovery is new to me and threads seem either too full of info or not enough for me, so here's me asking for help!
Either way, thanks!
Dustin
Click to expand...
Click to collapse
You're just a few steps away.
First download this stock ed01 debloated/debinged stock ROM from link below and place in root directory of SD card:
http://www.multiupload.com/BKHF5DKJ18
also, choose a kernel and place on sd card. I recommend imnuts' PB&J variety-you might want to stick with stock voltage or -50uv for now. Be mindful to get non-voodoo if you aren't planning on getting into this. found here (try the 3rd or 5th option):
https://sites.google.com/a/imnuts.net/android/kernels
Next, use Odin to install your CWM again. When you boot up this time, boot directly into CWM by turning phone off, and holding volume down, volume up, and power (all 3) until CWM appears. flash your rom, and kernel. If you don't boot into cwm directly by this method, the stock kernel will overwrite CWM, which is what was happening to you, i believe.
after rom/kernel is installed, choose reboot system now from cwm.
Yeah, I just wasn't sure about what kernel would be good for her phone, so I just was kinda "stuck" at that point. ^^;;
But I will give it a go and she how it works out! thanks much!
Everything was a success, and there was much rejoicing!
They only thing I noticed was after the Samsung bootloop animation, it goes to the default "android" one instead of Verizon's... I'm sure there's a way to get that back, but its not in the system dump I have. I'm currently searching for it on the net ^^;;
Thanks again!
Edit: I was able to find a boot animation that had the first part of the Galaxy S bit without the Verizon part. When it booted it just repeated the "Galaxy S" animation. I thought by adding, renaming, and reversing the shutdown animation would at least give that back, but now I just get a black screen for that segment...Still working on it....I think it has to do with the txt file inside, but i'm not sure.
The PowerOn.wav is still present on the phone, but it doesn't play either.... >_<
Are you certain you put poweron.wav in /system/etc folder?
Yup, its there and plays fine in the media player, but I just noticed that there's also a PowerOn.snd file right above. Could that be interfering?
Make a backup elsewhere of that file, then delete it and see if that works.
Sent from mah Fascinate using XDA Premium App
The sound won't work with most kernels that are not stock because the boot sounds aren't actually turned on in the kernel
Swyped from my CM7 fascinate
Oh okay, any chance to get the default boot animation from any of you guys? She doesn't mind the sound "missing," but she would like the boot animation at least.
Eitiher way, thanks much for the info!
since it seems like you're using a stock Rom just debloated and rooted, you may want to think about just using the stock Kernel with the recovery wipe removed, it has two options one that sticks with the stock boot animation and may still have sound and one that allows custom boot animations. This kernel was created by imnuts and can be found here:
http://forum.xda-developers.com/showthread.php?t=1060457
Awesome, thanks! I'll give that a try and see how it turns out!
And it worked! Thanks again!
So I just rooted my wife's phone and froze as many apps as I could without glitching the system out with TB. The phone was super laggy from the box but now it seems better but she said today that it froze on her a couple times. I come from a Droid X with GB 2.3 rooted and it's pretty fast for me. Even when it was stock it was quick. I'm not sure what else to do. Since it's my wife's I would rather leave it as close to stock as possible. Any suggestions.
Also is there a list of apps that can be froze in TB without causing other issues. It may be possible I froze one to many.
Thanks for your time.
Terry
Divey1130 said:
So I just rooted my wife's phone and froze as many apps as I could without glitching the system out with TB. The phone was super laggy from the box but now it seems better but she said today that it froze on her a couple times. I come from a Droid X with GB 2.3 rooted and it's pretty fast for me. Even when it was stock it was quick. I'm not sure what else to do. Since it's my wife's I would rather leave it as close to stock as possible. Any suggestions.
Also is there a list of apps that can be froze in TB without causing other issues. It may be possible I froze one to many.
Thanks for your time.
Terry
Click to expand...
Click to collapse
I would suggest you follow this link here
http://forum.xda-developers.com/showthread.php?t=1048380
Download and flash one of the "DEBLOATED/DEODEXED"
These types of ROM's are completely stock just with all of the crap removed (bing and the VZW bloatware)
Shark has the thread updated to the 12th of June so they should be up-to-date.
Cheers
gkirby11 said:
I would suggest you follow this link here
http://forum.xda-developers.com/showthread.php?t=1048380
Download and flash one of the "DEBLOATED/DEODEXED"
These types of ROM's are completely stock just with all of the crap removed (bing and the VZW bloatware)
Shark has the thread updated to the 12th of June so they should be up-to-date.
Cheers
Click to expand...
Click to collapse
I read over it all and my wife's phone is ED04 which is not in his list. I think this is exactly what I am looking for. I understand most of it except the modem stuff. There are so many numbers and versions to use. This is so different than my droid x. If I would have started with her phone first, I probably would have never attempted to mod it. Anyways what should I do now? Would it be better to flash a rom that's not stco but stable and fast. Just for giggles I did a quadrant test on hers and mine. She barely broke 900 while mine is over 1900. Seems like a huge difference being both are 1g processors.
Thanks for the help.
Terry
Barely breaking 900 is normal if you are not using a voodoo enabled kernel. The rfs partition is what is the biggest bottleneck. If you truly want a snappy rom, jump to comrom or evil fascinate. I use both equally and both will give you the speed you are wishing to match from your dx. As for modems, your wife's modem is compatible with either rom I mentioned.
For now I would suggest keeping her phone froyo based as gb is still being worked on by our awesome devs, but isn't for the faint at heart just yet IMHO
Dalamar1320 said:
Barely breaking 900 is normal if you are not using a voodoo enabled kernel. The rfs partition is what is the biggest bottleneck. If you truly want a snappy rom, jump to comrom or evil fascinate. I use both equally and both will give you the speed you are wishing to match from your dx. As for modems, your wife's modem is compatible with either rom I mentioned.
For now I would suggest keeping her phone froyo based as gb is still being worked on by our awesome devs, but isn't for the faint at heart just yet IMHO
Click to expand...
Click to collapse
Perfect, exactly what's needed. So do I follow these steps even tho is says from ED01.
Install Instructions:
If you are coming from a stock ED01 non rooted build follow these instructions:
Download Evil Fascination and place it on your SD card
Download Odin: http://www.mediafire.com/?msnc375idu7xhqt
Download Recovery: http://www.mediafire.com/?pfuhk4ibn9uore3
Install Samsung Drivers for your pc: http://forum.xda-developers.com/showthread.php?t=779238
Remove battery from the phone
Connect the phone up through USB and hold volume down during the connection
Your phone will be in download mode
Open up Odin and click on the pda button and select the recovery file
Click Start on Odin - phone will reset when flashed
Hold volume up and down and insert battery back into the phone and boot it up. Hold volume up and down while it boots up and it will boot into CWM recovery. If it has boot up to the startup animation you will need to start over and reflash recovery through odin
When you are in CWM recovery continue with the instructions below.
If so I'm ready to flash it.
Thanks
Terry
Yeah that looks good. Just use Odin (pda button) to flash your recovery. (Ensure you are using the PDA button. Cannot emphasize that enough)
Then follow the steps outlines. You're good to go.
Dalamar1320 said:
Yeah that looks good. Just use Odin (pda button) to flash your recovery. (Ensure you are using the PDA button. Cannot emphasize that enough)
Then follow the steps outlines. You're good to go.
Click to expand...
Click to collapse
Thanks a million. Will update after flash.
Terry
Just to make sure since there are a million different downloads is this the right one to download. (highlighted in red is the one)
CR 2.0
These versions will wipe your data, so make sure you back it up
This version contains the EC01 modem/radio and imnut's 05/31 PBJ -50mv nonvoodoo kernel
This version contains no modem/radio and imnuts' 05/31 PBJ -50mv nonvoodoo kernel
So this one would be without the kernel which is the modem/radio.
Then I do this patch for 2.1
Com Rom (froyo) 2.1 (patch, must flash on top of 2.0, no need to wipe):
md5: 725f94fa1cad7e562a767cd61ecd590b
And then this theme.
[THEME] Crysis Revolution v4.0 *Community ROM 2.1!* *6.20.11*
Is this all correct and in the right order. I want to 100% sure before I do this. Man is it so much different than flashing my DX.
Thanks
Terry
Divey1130 said:
Just to make sure since there are a million different downloads is this the right one to download. (highlighted in red is the one)
CR 2.0
These versions will wipe your data, so make sure you back it up
This version contains the EC01 modem/radio and imnut's 05/31 PBJ -50mv nonvoodoo kernel
This version contains no modem/radio and imnuts' 05/31 PBJ -50mv nonvoodoo kernel
So this one would be without the kernel which is the modem/radio.
Then I do this patch for 2.1
Com Rom (froyo) 2.1 (patch, must flash on top of 2.0, no need to wipe):
md5: 725f94fa1cad7e562a767cd61ecd590b
And then this theme.
[THEME] Crysis Revolution v4.0 *Community ROM 2.1!* *6.20.11*
Is this all correct and in the right order. I want to 100% sure before I do this. Man is it so much different than flashing my DX.
Thanks
Terry
Click to expand...
Click to collapse
this looks fine, no need to worry about the radio I believe it will use the one from whatever baseband you're at before you flash (ED04 I believe you said) or you can flash the one with ED01 radio... yes ComRom with imnuts' PBJ kernel is good, I would suggest the voodoo kernel one but its up to you, patch on top of that then theme after and you should be set
tapatalked from my GINGERBANGED Fascinate
As anoninja said. You should be good to go. Thing to keep in mind is that it is very difficult to brick your fascinate. Not impassible. But difficult. As long as you stay with fascinate files, never try captivate, vibrant, i9000, etc, stuff, then worse case scenario, you may have to odin back to stock and try again, but even that's unlikely. Good luck. Keep us posted with your progress
Sent from my SCH-I500 using XDA App
Hey thanks guys, feels better knowing it's not so easy to screw my phone up. I read a little about voodoo before work and yes, I do want to have it. So the majic question is, which one.
Thanks
Terry
Well if you choose evil fascination with the kernel, I think out will automatically convert you to voodoo so no extra steps other then to wait for the conversion after it boots.
Sent from my SCH-I500 using XDA App
After doing some more research I have decided to go with Com Rom 2.0 then patched to 2.1.
I am going to go with this one:
*Fixed* UKB 2.0 with -50 PBJ Voodoo Kernel ***6.4.11 (script fixed)
md5: 1092A4F02F668521D633670A80BA127C
My wife doesn't like the all black theme on the evil rom. Now I am still a little confused on the kernel thing. I have been reading for awhile now and will continue to do so. I'm not understanding if I have to flash the kernel first or rom first. I have been through the fascinate development thread over and over and while most put "how to's" in them, I still don't understand in which order things should go. There is so much to do just to flash a rom on this phone. But I know I will get it done even if I have to start over from fresh. So many roms, kernels, updates, 2.2.3.4.6._______, etc, etc...... What exactly is a kernel? I come from the droid x back ground where we root, cwr, then flash. That's it. Also to me Odin seems to be a 3rd party app that's needed to flash CWR. Other than that is there any other use for it. Sorry for all the ?'s but I like to do my homework before I do something like this. I am a pretty good self learner but the way things are worded for the phone is a little confusing at times. Maybe a step by step list if starting fresh.
EX- 1-root
2-odin
3-cwr
4-kernel or rom or both
Something like that would be easier to understand. Anyways I always appreciate any help I get.
Thanks
Terry
Divey1130 said:
After doing some more research I have decided to go with Com Rom 2.0 then patched to 2.1.
I am going to go with this one:
*Fixed* UKB 2.0 with -50 PBJ Voodoo Kernel ***6.4.11 (script fixed)
md5: 1092A4F02F668521D633670A80BA127C
My wife doesn't like the all black theme on the evil rom. Now I am still a little confused on the kernel thing. I have been reading for awhile now and will continue to do so. I'm not understanding if I have to flash the kernel first or rom first. I have been through the fascinate development thread over and over and while most put "how to's" in them, I still don't understand in which order things should go. There is so much to do just to flash a rom on this phone. But I know I will get it done even if I have to start over from fresh. So many roms, kernels, updates, 2.2.3.4.6._______, etc, etc...... What exactly is a kernel? I come from the droid x back ground where we root, cwr, then flash. That's it. Also to me Odin seems to be a 3rd party app that's needed to flash CWR. Other than that is there any other use for it. Sorry for all the ?'s but I like to do my homework before I do something like this. I am a pretty good self learner but the way things are worded for the phone is a little confusing at times. Maybe a step by step list if starting fresh.
EX- 1-root
2-odin
3-cwr
4-kernel or rom or both
Something like that would be easier to understand. Anyways I always appreciate any help I get.
Thanks
Terry
Click to expand...
Click to collapse
yes odin is a 3rd party program used to push installs, and most roms nowadays will root you and install kernel (most come with it built in unless otherwise specified) when you flash them so no worries about rooting or kernels... a little about voodoo here:
http://forum.xda-developers.com/showthread.php?t=1043673&highlight=voodoo
http://forum.xda-developers.com/showthread.php?t=1039897&highlight=voodoo
and you can read about what all these 'roms', 'radios' and 'kernels' are here (i wouldn't get any downloads from here as this is old):
https://docs.google.com/document/d/...XcM268FoIzk/edit?hl=en&authkey=CKqWypcP&pli=1
I'll try and make it simple, this is how I did it and had no problems:
1. obvious step, have all the driver, programs and packages you need ready to go: samsung drivers and odin on your pc, both ComRom 2.0 and 2.1 patch on sd card
2. assuming you're already on EB01 froyo baseband or higher, you wanna use odin to install CWR
3. from CWR make any backups you want then wipe data/cache/dalvik
4. flash .zip of rom you want (ComRom 2.0), select reboot phone once to ensure it took. Since you're flashing a voodoo kernel on first boot you should hear a robot lady saying she's formatting partitions, this may take a while but its normal
5. once it started up power phone off and boot again into CWR (or use power button menu to boot straight there with 'recovery' option)
6. flash .zip of ComRom patch, no wiping needed and select reboot phone
7. congrats you're rooted, voodoo'd and running ComRom 2.1
tapatalked from my GINGERBANGED Fascinate
anoninja118 said:
yes odin is a 3rd party program used to push installs, and most roms nowadays will root you and install kernel (most come with it built in unless otherwise specified) when you flash them so no worries about rooting or kernels... a little about voodoo here:
http://forum.xda-developers.com/showthread.php?t=1043673&highlight=voodoo
http://forum.xda-developers.com/showthread.php?t=1039897&highlight=voodoo
and you can read about what all these 'roms', 'radios' and 'kernels' are here (i wouldn't get any downloads from here as this is old):
https://docs.google.com/document/d/...XcM268FoIzk/edit?hl=en&authkey=CKqWypcP&pli=1
I'll try and make it simple, this is how I did it and had no problems:
1. obvious step, have all the driver, programs and packages you need ready to go: samsung drivers and odin on your pc, both ComRom 2.0 and 2.1 patch on sd card
2. assuming you're already on EB01 froyo baseband or higher, you wanna use odin to install CWR
3. from CWR make any backups you want then wipe data/cache/dalvik
4. flash .zip of rom you want (ComRom 2.0), select reboot phone once to ensure it took. Since you're flashing a voodoo kernel on first boot you should hear a robot lady saying she's formatting partitions, this may take a while but its normal
5. once it started up power phone off and boot again into CWR (or use power button menu to boot straight there with 'recovery' option)
6. flash .zip of ComRom patch, no wiping needed and select reboot phone
7. congrats you're rooted, voodoo'd and running ComRom 2.1
tapatalked from my GINGERBANGED Fascinate
Click to expand...
Click to collapse
You are the shiz nik. Perfectly worded and the timing couldn't have been better. Phone has both files ready to go. I found some more literature on kernels and now understand what it does. Pretty much controls performance of the phone. And I see roms with and without kernels. For my first time with this phone I will go with a kernel/rom. The radio is stock ED04 which I will leave stock. Will update after I finish all of this. My wife will be stoked now that her phone will run smoothly. Thanks for the detailed explanation for me.
Terry
Divey1130 said:
You are the shiz nik. Perfectly worded and the timing couldn't have been better. Phone has both files ready to go. I found some more literature on kernels and now understand what it does. Pretty much controls performance of the phone. And I see roms with and without kernels. For my first time with this phone I will go with a kernel/rom. The radio is stock ED04 which I will leave stock. Will update after I finish all of this. My wife will be stoked now that her phone will run smoothly. Thanks for the detailed explanation for me.
Terry
Click to expand...
Click to collapse
no problem, good luck
tapatalked from my GINGERBANGED Fascinate
I just wanted to thank all of you that helped me here. Running Com Rom 2.0 w/2.1 patch. It's nite and day compared to how the phone was. So much smoother and no lags as of yet. My wife couldn't be happier now with the phone working like it should be. I did encounter one issue tho. I could not create a backup. It would read an error message. (forgot what it said) Anyways thanks a million for the help. The crt animation is awesome and I love the functions when powering off. Rebooting instead of powering off then on and especially booting into recovery without pushing the volume rocker. Well I am going to add a theme for her so richen it up and go from there.
Just got it to backup as I was typing this. After reading thread after thread it seemed like you either had to flash a kernel other than stock or flash a rom before it would back up. I even tried red, blue, and purple with no luck. Oh well at least now it's backed up.
Terry
Divey1130 said:
I just wanted to thank all of you that helped me here. Running Com Rom 2.0 w/2.1 patch. It's nite and day compared to how the phone was. So much smoother and no lags as of yet. My wife couldn't be happier now with the phone working like it should be. I did encounter one issue tho. I could not create a backup. It would read an error message. (forgot what it said) Anyways thanks a million for the help. The crt animation is awesome and I love the functions when powering off. Rebooting instead of powering off then on and especially booting into recovery without pushing the volume rocker. Well I am going to add a theme for her so richen it up and go from there.
Just got it to backup as I was typing this. After reading thread after thread it seemed like you either had to flash a kernel other than stock or flash a rom before it would back up. I even tried red, blue, and purple with no luck. Oh well at least now it's backed up.
Terry
Click to expand...
Click to collapse
sucks about the backup, the voodoo lagfix CWR versions are known to have problems with this and unfortunately I forgot to mention this, I tend to not do nandroid backups since I don't keep much on my phone in terms of data and apps, being the flashaholic that I am lol anyway good that you got it up and running, its good stuff and a million times better than stock
tapatalked from my GINGERBANGED Fascinate
I am currently running comrom 2.1 with OTB 1.6 kernel. Looking to go with the flow on updates lol. Wanting to get everyones opinion. Should I switch? If so, how about should I do that? Don't want to mess anything up on my phone
powerstroke said:
I am currently running comrom 2.1 with OTB 1.6 kernel. Looking to go with the flow on updates lol. Wanting to get everyones opinion. Should I switch? If so, how about should I do that? Don't want to mess anything up on my phone
Click to expand...
Click to collapse
Well the first thing you should do is read, read, and read again on the CM7 test build thread along with the waiting room in the general thread. For every handful of success stories there are even more horrible failures.
Another question you should ask yourself is why are you considering switching? Because you know, understand, and like CM7 features? Or because you have seen endless posts on here about how it is now working?
Believe me I love CM7. I ran it for my daily driver for a few months back when 60% of it didn't function. Now that it is in TEST build 10 (still not full release like Ultimate Kang bang 2.1 that you are running) people are flashing it like it is a full RC. They are also having terribly problems and soft bricked phones more than an Touchwiz based ROM at the moment.
If you really like CM7 features, understand the process for flashing an MTD/BML ROM, and feel prepared for the worst then go for it. If it is successful for you it will change your whole perception of the Fascinate. Add on the new Glitch V11.1 kernel and you will never run anything else!!
...If you are just flashing it because it is the flavor of the week... I'd wait till it is in nightlies before flashing. Just reduces the chances of an oh-s#%t-moment happening.
powerstroke said:
I am currently running comrom 2.1 with OTB 1.6 kernel. Looking to go with the flow on updates lol. Wanting to get everyones opinion. Should I switch? If so, how about should I do that? Don't want to mess anything up on my phone
Click to expand...
Click to collapse
I was exactly where you are 24 hours ago myself. I took the plunge and I'm glad I did. CM7 is the best thing that has ever been on my phone. I had zero installation problems. I haven't even tried the new 1.7ghz kernel yet. Got nems 1.6 though doing nicely. While I echo the precautions of the prior post I whole heartedly endorse the switch
Sent from my SCH-I500 using XDA Premium App
gkirby11 said:
Well the first thing you should do is read, read, and read again on the CM7 test build thread along with the waiting room in the general thread. For every handful of success stories there are even more horrible failures.
Another question you should ask yourself is why are you considering switching? Because you know, understand, and like CM7 features? Or because you have seen endless posts on here about how it is now working?
Believe me I love CM7. I ran it for my daily driver for a few months back when 60% of it didn't function. Now that it is in TEST build 10 (still not full release like Ultimate Kang bang 2.1 that you are running) people are flashing it like it is a full RC. They are also having terribly problems and soft bricked phones more than an Touchwiz based ROM at the moment.
If you really like CM7 features, understand the process for flashing an MTD/BML ROM, and feel prepared for the worst then go for it. If it is successful for you it will change your whole perception of the Fascinate. Add on the new Glitch V11.1 kernel and you will never run anything else!!
...If you are just flashing it because it is the flavor of the week... I'd wait till it is in nightlies before flashing. Just reduces the chances of an oh-s#%t-moment happening.
Click to expand...
Click to collapse
Great answer!
powerstroke, like he said; read, read, and read some more. that's what i did. and i ended up going for it, and so far i am not looking back. Just prepare yourself with backup plans in case something goes wrong.
From my point of view, I'm enjoying CM7 as least as much more than CommRom as I enjoyed CommRom more than Stock. I'd say that it's CM7 from here on out for me, except that's what I said about CommRom not too long ago. Who knows what the Devs will come up with next?
I liked CM7 but the low in call volume and the sucky AOSP camera made me go back to CommRom 2.1 with EC09 radio.
i agree, just read up like crazy so you don't mess anything up but take the plunge if your prepared. i went from just stock, debloated ed01 to the latest cm7 and i've had no problems. look up omfgb though because i'm waiting for that one to be more functional and i'm probably gonna switch to it
Give miui a shot to. It's pretty.
Fascinatemtd MIUI 1.7.15 - Glitch v11.1
Ok awesome guys appreciate all the info. I think I'm going to give it a whirl. Main question I have now is, what is the easiest and safest way to switch over to that rom from where I am now? Just do the factory reset, wipe cache, and wipe dalvik cache? Then flash the CM7 rom through recovery? or something else? Just want to make sure I do it right lol
^^^
That's why everyone said read.....
Ha...No **** lol. I understood that part but for people that might have already switched between those roms might have other suggestions. No need to be a smartass
Well since your being a smartass, lol, want to find me a forum that specifically shows how to switch from a froyo rom to cm7????
powerstroke said:
Well since your being a smartass, lol, want to find me a forum that specifically shows how to switch from a froyo rom to cm7????
Click to expand...
Click to collapse
Easy, try the thread for the CM7 ROM in the development section. jt covers it in the op, and there are several more specific walkthroughs in the the thread.
provided by Land Shark:
(coming from stock DL09)
1. Power down phone, pull battery
2. ODIN EC09 modem, pull usb cord, close ODIN
3. Reopen ODIN, connect USB, flash fixed CWM 4 from OP of CWM7 thread (here: http://forum.xda-developers.com/showpost.php?p=14554015&postcount=1)
3. Close ODIN, pull usb cord, put battery back in phone, hold volume up, volume down, and power buttons but release all three as soon as you see samsung logo flash for the second time
4. Flash CM7 07/13 build and GAPPs (Google Apps) from OP
5. Reboot phone, wait for ROM to fully boot and load, finish setting up phone with contacts, apps, etc., profit.
ok..followed your instructions. now im in a loop when its trying to flash. "waiting for sd card to mount" over and over. counting down in seconds? what should i do?
If you are serious about diving into cm7 read all u can I red for 3 days. Nearly 2500 posts and its knowledge I'll need should anything not go smooth you may have one glitch that u try and fix mess that up and its steam rolls into a long process but if u follow word for word and know exact orders of Odin and flashes and how to get to the proper cwm its beautiful just make sure ur beyond prepared before the first click that's about the best advice I can give 2cents are now in the pot
JOrtenzi said:
provided by Land Shark:
(coming from stock DL09)
1. Power down phone, pull battery
2. ODIN EC09 modem, pull usb cord, close ODIN
3. Reopen ODIN, connect USB, flash fixed CWM 4 from OP of CWM7 thread (here: http://forum.xda-developers.com/showpost.php?p=14554015&postcount=1)
3. Close ODIN, pull usb cord, put battery back in phone, hold volume up, volume down, and power buttons but release all three as soon as you see samsung logo flash for the second time
4. Flash CM7 07/13 build and GAPPs (Google Apps) from OP
5. Reboot phone, wait for ROM to fully boot and load, finish setting up phone with contacts, apps, etc., profit.
Click to expand...
Click to collapse
well this is what i did and still have problem!!!!!!!!! T.T
1) odin ebo1 with atlas pit 2.2
2) cwr blue on CM7(jt site)
3) installed cm7 latest one 7/17
4) now stuck on cm7 logo and just stuck there... nothing happens ........... any HELP????????!!!!!!
izzjkjoe said:
well this is what i did and still have problem!!!!!!!!! T.T
1) odin ebo1 with atlas pit 2.2
2) cwr blue on CM7(jt site)
3) installed cm7 latest one 7/17
4) now stuck on cm7 logo and just stuck there... nothing happens ........... any HELP????????!!!!!!
Click to expand...
Click to collapse
This works for me, but in step 2. I odin cwr 3-30 fix all. immediately Boot into it and wipe everything, then flash the 7/4 build, from there use cm7 recovery from power button to flash newest build w/o wiping...worked multiple times for me.
Sent from my SCH-I500 using XDA App
I was on com rom with ed04 radio, i just did the 3 wipes and install miui zip, takes less than 5mins.
Sent from my I500 using XDA Premium App
Hello all,
I have a question that has not been answered after many hours of searching. Hopefully I'm just dumb, and my buddy's stock firmware and data isn't hosed. I'm trying to get his stock firmware running again so I can back it up safely.
What I've done:
Tried to flash CWM's update.zip via stock recovery (signature verification failed on the three different zip's I could find in the forums and various links)
Used Heimdall to push "cmenard-T959-CWM" zImage (this worked, and I get a different screen at boot)
The phone boots to the point of the T-Mobile splash screen with the annoying shriek sound, but goes to a black screen after. If i touch any of the soft buttons, they light up and remain lit. It'll stay like that for at least 20 minutes.
Is it possible to re-flash the system partition and not the data partitions using ODIN? Is that even feasible? Like I mentioned above, I'd like to get the stock firmware running such that I can make a good backup of it with all the user data intact. I haven't been able to because the CWM+root wouldn't flash.
Any suggestions or insight would be greatly appreciated.
thanks in advance!
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Toast6977 said:
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Click to expand...
Click to collapse
Thanks for the suggestion, Toast. I don't believe the internal SD has been messed with, and I don't plan to mess with it either. The thread you linked is not quite related to my issue, as far as I can tell.
I am able to get into Download Mode, and the Stock Recovery mode as well. However every time I try to flash an 'update.zip' with the Stock Recovery, I get an error about Signature Verification Failure.
After stepping back from it for a day, I think I've gained some clarity. Since all I've done is flash a different Kernel with Heimdall, I'm going to try to flash a stock kernel then see what happens.
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Toast6977 said:
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
Click to expand...
Click to collapse
Woodrube said:
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Click to expand...
Click to collapse
hahaha poltergeist!
Wow, so I'm glad I asked. I wouldn't have known about this issue, as I do not have any history with this device.
I know that the ROM is currently 2.2, and the Android System Recovery is showing "3e".
If I understand correctly, once I'm ready to flash up to ICS, I'll need to ODIN back to 2.1 to get Android System Recovery "2e", which will let me flash 'update.zip' packages freely. Then I flash an 'update.zip' to get CWM, then flash CM7, then CM9 (and CM9 is my intended destination).
The things mentioned in the thread you linked do appear to apply to my situation.
However I still want to get the stock OS booted and working, then do a Nandroid backup of it. (it's the computer tech/security pro in me. Since I'm new to this device, I -tried- to read up on everything first, and didn't want to make a change without being sure it would work.)
Does anyone happen to know if flashing a stock kernel over the 'cmenard' kernel will harm anything, and hopefully get a successful boot? Again, I'm trying to get the stock ROM booting again in order to verify I have everything I need off of it, then do a nandroid backup. Flashing to CM9 will come afterwards.
Ok, here are some things for you.
Here is a kernel pack that you can use. Read the OP because there are Froyo AND Gingerbread kernels in there.
[KERNELS] Moped_Ryder SGS Kernel Pack v2 [20+ Froyo/GB Kernels]
I really suggest using something like BaliX 1.2 or BaliUV kernels to make your back up. They are smooth, fast and OC/UV-able. To flash just Wipe /cache, /dalvik -> flash kernel -> Wipe /cache, /dalvik (I also fix permissions too bc that is the way that I learned and I just do it that way all the time). Reboot and Bam!! you should be able to get to the point that you can make a backup.
Look in my signature, there are downloads and flashables that are direct download linked. There is also an ICS install guide that can help your journey. Once you have your backup, then use Odin from the Toolbox in my signature and flash back to stock JFD. From there you will be able to follow my guide.
If you need any files, just let me know and I will upload them when I get home (won't be until late though, i have plans right after work).
Using HB, can I choose any theme? I am not so acquainted with the Theme chooser and boot animation of my phone. I flashed a boot animation zip yesterday and it was stuck in "ANDROID" screen. So I have to flash again. I never used any boot animation and themes in my phone yet. I want to know about them.
Sent from my SGH-T959 using xda app-developers app
Wrong thread. Put that question in the Jelly Bean Banter thread. No need to hijack this thread until we get OP up and running.
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
maxpeet said:
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
Click to expand...
Click to collapse
Wrong they are not the same. cwm can do the work without a PC beside you can erase, back up , restore and flash, which make our life easier, heimdall or Odin ," I prefer odin "are the last option when you can't fix it with cwm
To fix your phone use Odin or heimdall and go back to stock don't worry all your files, photo, music, will be safe. Then
1 get root on you , if you don't how ask
2 get cWm
3 do a nandroid back up
4 have fun flashing all roms you want lol
Sent from my SGH-T989 using xda app-developers app
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Toast6977 said:
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Click to expand...
Click to collapse
do no check de re-partition button and use a .pit file follow this tutorial and you will be fine
http://forum.xda-developers.com/showthread.php?t=848737