Related
Anyone care to explain what all this cwm commotion is about and which one to use?
red works for all eb01 and dl30 roms, orange (the newest one), does not. if you use orange, it will frustrate you at best, and leave you without a working phone at worst (though I doubt it will actually brick it). the easy solution is to just download red, and don't update it until someone proves it works reliably.
m91-30 said:
red works for all eb01 and dl30 roms, orange (the newest one), does not. if you use orange, it will frustrate you at best, and leave you without a working phone at worst (though I doubt it will actually brick it). the easy solution is to just download red, and don't update it until someone proves it works reliably.
Click to expand...
Click to collapse
That is actually completely false. Ive had zero problems with CWM 3.x.
But to answer the OP's question, I would stick with CWM 2.1.x until a lot of the flashable zips are rewritten with edify scripting, as cwm 3.x works with edify and edify only.
Sent from my SCH-I500 using XDA App
The orange CWM (3.0) uses a new scripting method, Edify, for update files (zip files). The red and green CWM (2.5) supports the Amend scripting method for update files.
Most of the existing files that can be flashed on this site were made with the Amend script, which isn't compatible with CWM 3.0. There are some Edify updates becoming available now, however.
While some people are saying that CWM 2.5 doesn't support Edify, I know people over in the Super Clean thread are saying they flashed adrynalyne's sc2.7 (which used an Edify script) using jt's red CWM (2.5.1.x).
I'm personally sticking with CWM 2.5.1.x until there is a need for me to update to something else.
Yes, I've tried using the orange version... Didn't work really well for me. The red one is amazing.
I keep seeing cwm 3.0 mention. Where can I find it? I have 2.5.1 now
Sent from my SCH-I500 using Tapatalk
The orange one doesn't work as designed. The red one does everything we need plus one.
I meant to include that it was because of scripting incompatibility, but it will frustrate you, at least it did me. clockwork is such an amazing program, but orange will just run you in circles trying to write the amend scripted ROMs. trying to write an amend ROM with orange and not being able to after wiping my cache and data also messed up my apps (as I would expect it to), meaning I wasted time just trying to get rom manager working again (it fought me, and took 5 times of reinstalling, uninstalling, then reinstalling to get t to work), then installing red.
this was only an inconvenience for me, but it still made a 10 minute process take a lot longer. do yourself a favour and download red BEFORE trying to flash your ROM.
you can update to the latest version of it through rom manager, but remember, it isn't compatible with our ROMs
I don't even use rom manager so maybe that's a good thing Thanks guys.
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.
ive been doing some reading and have some questions
1. is clockwork mandatory? id prefer to flash via odin.
2. can you recommend a touchwiz rom thats cleaned and based on the new ed01 source?
Well, Clockwork isn't absolutely mandatory, but the vast majority of ROMS/Kernels/Themes/etc. come packaged in .zip files which are meant to be flashed via CWM.
Odin uses .tar/.md5 files and is usually relegated to a more disaster recovery tool, or flashing items like a new radio. You CAN use Odin to flash ROMS, but you options can me more limited.
Here's a list of the most popular ROMS/Kernels/etc for the Fascinate:
http://forum.xda-developers.com/showthread.php?t=1013312
For Odin flashable ROMS, there's a great post at androidcentral.com:
http://forum.androidcentral.com/ver...tom-roms-w-root-clockwork-updated-3-25-a.html
Hope this helps.
its the the red/green/orange cw that im not crazy over 9i may be reading something wrong
You definately want to use RED cwm for the fascinate. Orange does not play nice at all, since support for amend scripting was removed. (Almost all fascinate ROMS use this type for flashing) If you accidentally flashed Orange through ROM Manager, you can use this post to help you get back to red:
http://forum.xda-developers.com/showthread.php?t=942021
Use either Odin (.tar file) or CWM (.zip file) to flash and you'll be back to red after manually booting into clockwork.
CWM really is much easier to flash, if for no other reason than not having to pull the case and battery off
havent flashed yet, just rooted, but i figured if vzw is dropping 2.2, i might as well do a custom.
just gotta decide
as i said im thinking clean, nonvoodoo. but i dont see an ed01, just an ec01
Pretty sure everybody will tell you ed01 and ec01 are the same, but I'm just going by the the general post on the matter.
Sent from my SCH-I500 using XDA Premium App
hhhmm then i guess what im waiting for now are restore files for ec01/ed01
or would older ones be ok?
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.
I flashed my vibrant from bionix 1.3.1 with touchwiz to the CM7 just to see what was on CM7, the problem i'm running into now is that i'm trying to flash it back to bionix until CM7 becomes stable. It now states the following:
Amend scripting (update-script)is no longer supported
Amend scripting was deprecated by Google in Android 1.5
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Installation aborted.
As far as i know, i researched the problem and the problem i believe has to concern with the way CM7 and the recovery work with scripting.
I just want to know how to get back to bionix, i'm relatively new to this flashing and stuff so i would like a detailed description, even maybe a step by step answer but at this point any answer would work.
Additional Information:
I have a forward facing camera installed on my vibrant this is NOT the sgh-t959v, this is the sgh-t959 with a camera mod.
lfrenkel said:
I flashed my vibrant from bionix 1.3.1 with touchwiz to the CM7 just to see what was on CM7, the problem i'm running into now is that i'm trying to flash it back to bionix until CM7 becomes stable. It now states the following:
Amend scripting (update-script)is no longer supported
Amend scripting was deprecated by Google in Android 1.5
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Installation aborted.
As far as i know, i researched the problem and the problem i believe has to concern with the way CM7 and the recovery work with scripting.
I just want to know how to get back to bionix, i'm relatively new to this flashing and stuff so i would like a detailed description, even maybe a step by step answer but at this point any answer would work.
Additional Information:
I have a forward facing camera installed on my vibrant this is NOT the sgh-t959v, this is the sgh-t959 with a camera mod.
Click to expand...
Click to collapse
You MUST Odin back to stock JFD with repartition first, before going back to a Froyo ROM, including Bionix 1.3.1
Mr. Apocalypse said:
You MUST Odin back to stock JFD with repartition first, before going back to a Froyo ROM, including Bionix 1.3.1
Click to expand...
Click to collapse
How can I do that ??
Use the toolbox stickied in the Dev section. Has pit and tar files, drivers,...
He's right. You have to flash back to stock. You can try Heimdall One-Click, which will do all, he work for you.
Sent from my SGH-T959 using XDA App
odin back
I went through the same issues this past Friday. I had upgraded to ICS v13 and could not for the life of me get GPS to work.
I crashed my phone trying to load bionix v1.3.1 from cwm 5.x. had to Odin back and install cwm, and then update to bionix's rom.
Should be easy once you get all the files and get your drivers installed and your phone into download mode.