Was originally typing this in the Nero thread but didnt wana add clutter..
Ok, so I've been running Nero with voodoo enabled for a little over a week with no issue. ROM was smooth and battery life was solid. Then yesterday for the sake of a little more battery life I disabled voodoo and flashed the Super IO kernel to see how it would be in this ROM. Everything was fine for a while but then they phone would freeze everytime I ran GPS Test Plus. Only thing it would respond to was hitting the power button to put it to sleep and from that it would not wake (sleep of death). I proceeded to pull the battery. Immediately after the phone fully booted I began getting endless force closes from what seemed like every single all on the phone. Pretty sure this was kernel panic yes?
So I reflashed the JL5 Voodoo kernel (posted in the Nero OP) thinking that would fix it. the force close storm stopped but the phone was still acting up freezing and still wouldnt wake from sleep. I decided then backup, factory reset, wipe cach and dalvik cache, and reflash Nero. I thought all was well but to my surprise after being on the charger all night I arrive to work to find that my battery was at 74% O_O. This is shocking due to the fact that the phone had only been off the charger for about 45 minutes and had not been used AT ALL during that time.
So my question is... Did I just have a bad flash or did flashing the Super IO kernel do some unseen damage? Checked the battery info in Spare Parts and nothing looked out of order.
I would recommend, going back to stock and reflashing nero 3 and retrying the Super IO kernel. Hope that fixes the problem.
Will do when I get home. I assume this will unroot me, right?
I remember a post from Eugene on his site that the super io kernel works best when it is flashed with a rom before that rom is booted for the first time. If you're going back to the super io kernel, you should flash your rom, then flash the kernel before your first boot. It was something about how the kernel syncs with the rom, flashing it as an after thought can cause issues.
Ginger Clone's of the World Unite! Via the XDA App
Thats weird because I flashed super io over R14 when he first released it and had no problem -_-
Same thing happens to me when i touch Eugenes work. Thought I was the only one
Sent from my SGH-T959 using XDA App
Br1cK'd said:
I remember a post from Eugene on his site that the super io kernel works best when it is flashed with a rom before that rom is booted for the first time. If you're going back to the super io kernel, you should flash your rom, then flash the kernel before your first boot. It was something about how the kernel syncs with the rom, flashing it as an after thought can cause issues.
Ginger Clone's of the World Unite! Via the XDA App
Click to expand...
Click to collapse
regP said:
Thats weird because I flashed super io over R14 when he first released it and had no problem -_-
Click to expand...
Click to collapse
I was only successful with Super IO when I flashed it after a clean rom install. It sucks, but........
This is interesting, I experienced the same type of battery loss upon flashing Nero V3 for the first time. But, I did not flash eugenes super io kernel. I just stuck with the JL5. Although, Once I did a good recondition on my battery, Things seem to be much better. I'm a stickler when it comes to battery life though lol. Whens the last time you reconditioned the battery and wiped the stats via recovery?
I wipe the stats after every flash. I don't recondition unless the battery meter is trippin because I use 3 different batteries. 2 of which are knockoffs but they last about the same as the original. I factory reset, wiped caches again and then flashed the latest Axura. To my surprise after flashes and restoring data I booted into recovery to find the jl5 voodoo kernel was still there.. so I flashed Eugene's eb-productions stock kernel and everything seems to be fine.
What happened with the fc storm WAS kernel panic right?
I spoke too soon. Battery is still draining like a mofo and now I know why. Checked spare parts battery history and it reports that the phone wont go to sleep. Ill have to try to Odin back to stock when I get home
I have a few questions though because I've never done this before.
1. I downloaded Eugene_E2_JK2 from the Bible. Is that one fine or should I flash back to a stock 2.1 ROM
?
2. Will this process unroot my phone?
3. How is flashing the stock rom with odin any different than doing a factory reset and flashing with clockwork? I'm just worried that since flashing in clockwork didn't work odin wont either.
Vibrant via XDA App
So I odin back to JK2 then flashed a fresh installation of the latest Axura. Everything went fine as far as the flashing but after first boot I went back into recovery and i think the voodoo kernel from nero was active because I had the red letters and an option to enable voodoo O_O. WTF? I disabled voodoo before i did odin. I'm pretty sure Axura doesnt come with the voodoo kernel so how it was there after i came from stock is beyond me. So I flashed the EB-Productions stock kernel which i have used on Macnut and Axura and gotten great battery life before going to Nero. The battery still seems to be draining faster. Spare Parts reports that the "time spend without sleep" is about 10 minutes less than the phones boot time. I havent touched the phone since it booted so i dont see how thats possible.
I have no idea whats going on... Any help would be greatly appreciated. Im about ready to pull my hair out..
Just ODIN back to shipping rom (remember to use pit file and check repartition) It is better to do that everytime you are changing roms with kernel......
What difference would odin to stock 2.1 make over stock 2.2..?
regP said:
What difference would odin to stock 2.1 make over stock 2.2..?
Click to expand...
Click to collapse
The stock 2.1 is the official t-mobile software as it came from the factory. Any 2.2 we have is leaked, there is no official 2.2 for us yet. Although the 2.2 you said you flashed is as close as we got to a stock froyo rom. Flashing one of the two should get you back to stock, but the 2.1 is accepted the official base by many to start from, square one so to speak. After flashing stock, before any other roms are applied, you shouldn't have the red voodoo cwm anymore.
If you do still have voodoo after flashing stock, search for Eugene's Froyo that doesn't Brick. Flash through odin with the 512 pit file, you will reboot to a recovery that doesn't work, pull your battery, set up odin with either stock 2.1 or leaked 2.2 and the pit file, boot back to download mode, and flash the stock rom, being sure this time to select the repartition check box in odin. This will remove voodoo, and is the fix for times when voodoo goes bad. After this you will be as stock as you can get, and if you need a link to the froyo that doesn't brick, let me know I'll post it.
Ginger Clone's of the World Unite! Via the XDA App
What's the difference between reconditioning and just wipeing the stats. I've wiped it through clockwork before however what's reconditioning?
Sent from my SGH-T959 using XDA App
Reconditioning is charging your battery fully then letting it run down until the phone turns off then charging it back up again. The purpose is to make the battery reading more accurate if it seems to be inaccurate.
In other news... I odin back to stock 2.2 AGAIN then reloaded Axura. All is well now. Still bugs me though that voodoo was still there after the first odin. Just dont see how that was even possible.
Thanks for all the help!
The latest axura rom comes with the voodoo kernel, so if you flashed it, you will have, or should have, voodoo recovery. That was my point about checking recovery after flashing stock to verify it was removed, if that was what you were trying to do.
Ginger Clone's of the World Unite! Via the XDA App
Soo Im running SC 2.9.2 with Sense Theme and I try to flash Jt's new EC kernel but it never changes. Im still on kernel 2.6.32.9 and its pissing me off! I first boot into red recovery and disable lagfix through voodoo, then reboot. Then boot back into recovery and flash the kernel of choice, then go renable lagfix in voodoo and reboot! The lady talks and everything BOTH times.. but once my phone is completely rebooted its exactly the same! What am I doing wrong? at first I didnt think that lagfix was a huge part of it but after reading posts and talking to friends it made it seeem like it was.... so IDK HELP!!!
Thanks in advance
The 2.6.32.9 kernel is the right one. The only thing that should change from kernel to kernel is the date and the email address/username right after the kernel version.
On JT's kernel you should see Something like Mar 27 in the date area. I don't know what the email address says since I'm no longer on it though.
Edit: Also note, you don't have to disable voodoo lagfix if you're already using a voodoo kernel and you're flashing another voodoo kernel
Voodoo --> Voodoo (Don't need to disable lagfix)
Voodoo --> NonVoodoo (DO need to disable lagfix)
NonVoodoo --> NonVoodoo (Lagfix should always be disabled, shouldn't even have the option to turn it on really)
NonVoodoo --> Voodoo (Lagfix should be disabled by default when flashing a voodoo kernel)
Thanks for the help. but to be exact, where does this date show up so I know if it worked?? My system looks exactly the same as before when I look under "About Phone".... so im just skeptical that it flashed cuz my batt hasnt gotten better and it doesnt seem much faster. should i wipe batt stats? will that make a difference?
Thanks!
go into terminal (or download one from market)
type:
su
{Press enter}
cat /proc/version
{press Enter}
You will see:
Linux Version 2.6.32.9 (kernel author@virtualbox) (gcc version 4.4.1 (yada yada yada) COMPILE DATE
If that compile date is the date the the author released the kernel you are running it.
it says version not found!? and it doesn't say anything in terms of a kernel number or anything!
HELP!!!!
Thanks!
i get the same thing..... on a side note i thought superclean 2.9.2 came with ec10 kernel
@tumness420 i had the same problem when you do the su in terminal than you do cat /proc/version make sure you have a space between cat and / i tried it and it works
running "uname -a" can give you the build date/time as well.
Great! Thanks for the help! @mrtonee
Now the only question is, if the kernel didnt flash through CWM recovery how else am i to do it? considering I have a mac instead of PC.
or are there any other trick tips or shortcuts into flashing kernels?
cus it says installation complete when I run it, but I swear the kernel didnt flash
Does having a theme have anything to possibly do with why kernels dont flash properly?
Thanks in advance!
tumness420 said:
Soo Im running SC 2.9.2 with Sense Theme and I try to flash Jt's new EC kernel but it never changes. Im still on kernel 2.6.32.9 and its pissing me off! I first boot into red recovery and disable lagfix through voodoo, then reboot. Then boot back into recovery and flash the kernel of choice, then go renable lagfix in voodoo and reboot! The lady talks and everything BOTH times.. but once my phone is completely rebooted its exactly the same! What am I doing wrong? at first I didnt think that lagfix was a huge part of it but after reading posts and talking to friends it made it seeem like it was.... so IDK HELP!!!
Thanks in advance
Click to expand...
Click to collapse
Just so you know...the kernel doesn't bring any visual changes. Its changes are "under the hood" so you can't see them. Like was stated if you are going from one voodoo kernel to another, you don't need to disable lagfix. Also, the easiest way to tell if you are running a voodoo kernel is to download Quadrant Standard and run the full benchmark. A voodoo phone scores 1400+ whereas a nonvoodoo phone scores around 900.
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.