How to Voodoo ***Updated 27 Mar 2011***KERNEL BUILT FROM SOURCE/SOUND/UNDERVOLTED

Download Quadrant from the market and run it. If you get like !1400+, then you're on voodoo. If it's under 1000, then you most likely don't have voodoo enabled.
 
Yeah, I am only getting 970 on quadrant. Doesn't look like it worked.

Sent from my Froyo Fascinate using Tapatalk.
 
hhhmmmmm might be time for me to move on up to Voodoo, got nothing to flash and I'm bored. maybe this weekend, thanks for the write-up mike
 
Ok so im not sure if this is the right place to post this but ill give it a shot. I was running sc 2.6, has the patch installed as well. I was running midnight blue theme, then flashed the gingerbread theme. I then decided i wanted something else so i flashed the VA green theme. Before flashing all of these i did cache wipes and dalvic cache wipes. I did a nandroid backup of my gingerbread theme and wanted to flash back to that. I did that and got the force close loop of hell. I went back into recover did a data wipe factory reset this time, wiped all the caches, and tried running any flashing any theme i could but i am not getting past the boot animations now. I am running voodoo 2.4. Any help would be much appreciated.

Ok so i fixed the problem, read back a couple of threads and realized what i needed to do. Thanks. :)
 
Last edited:
I finally took the plunge and meet the VooDoo android, sexy voice for sure;) Thanks for the directions. Running SFC2.6v w/ EB16v kernel. I am re-installing all my apps and data now. Hopefully all will go well.
 
Gunnermike, you've been one of my primary inspirations in these forums, for I know I can probably never top the shenanigans you get into with your phone. For that, I thank you haha
Secondly I'm currently running the non vodoo sc 2.6. Can I flash the vodoo version right over, as it's not a nonvoodoo trying to cover vodoo?
Sent from my SCH-I500 using Tapatalk
 
I need a little help

Flashed (oden) back to stock DL01 - everything fine
Rooted the phone via mac 1 click- everything fine
Flashed (oden) red cwm-all - everything fine
Booted into recovery (vol/up/dnw/pwr) - everything fine

Wipe data/factory reset, wipe cache, wipe dalvik cache

Choose update zip fro sd card and selected the new sc 2.8 Voodoo and all appeared fine.

selected voodoo in red CWD and enabled lag fix

selected reboot and the samsung comes up and after a min takes me back to red CWD. I have pulled the batt and reboot and the same thing occurs.

any ideas?

CC
 
well i tried it with sc 2.6V and it seems to be working. That voice almost made me crud myself :eek:
 
I need a little help

Flashed (oden) back to stock DL01 - everything fine
Rooted the phone via mac 1 click- everything fine
Flashed (oden) red cwm-all - everything fine
Booted into recovery (vol/up/dnw/pwr) - everything fine

Wipe data/factory reset, wipe cache, wipe dalvik cache

Choose update zip fro sd card and selected the new sc 2.8 Voodoo and all appeared fine.

selected voodoo in red CWD and enabled lag fix

selected reboot and the samsung comes up and after a min takes me back to red CWD. I have pulled the batt and reboot and the same thing occurs.

any ideas?

CC

I got stuck in this as well. Eventually even Odin quit working for me. Got it flashed back to non-voodoo eventually. :confused: I am backing off of Voodoo for now. Too scary for me! :-[
 
2.6V ended up working. I then wiped cache and dalvik and updated to 2.8V. I also flashed the EB01 radio via ODEN. Setting up the phone again now, but all seems well.

CC
 
I updated sc2.5nv to 2.8v today. I had problems activating the lag fix in cwm. After reading a little further it looked like there was a known issue about 2.8v taking voodoo. I flashed the EBO1 voodoo kernel and got the lag fix to take, heard the lady and got a 1461 in quadrant. Thanks to this thread and GM for making it mostly worry free.

I have a question about the two options for voodoo kernels in adryn's SC 2.8 sticky. What is the difference between the EB01v kernel vs the EB16v kernel? It is my understanding that after SC 2.4 that it was a hybrid of EBO1 & EB16, so does it matter which kernel I flash? When I look at about phone>build number: it shows sch-I5000.EB01. So would I be ill advised to use the EB16 kernel should there be any type of benefit to one kernel vs the other?

Thanks for any insight.
 
I updated sc2.5nv to 2.8v today. I had problems activating the lag fix in cwm. After reading a little further it looked like there was a known issue about 2.8v taking voodoo. I flashed the EBO1 voodoo kernel and got the lag fix to take, heard the lady and got a 1461 in quadrant. Thanks to this thread and GM for making it mostly worry free.

I have a question about the two options for voodoo kernels in adryn's SC 2.8 sticky. What is the difference between the EB01v kernel vs the EB16v kernel? It is my understanding that after SC 2.4 that it was a hybrid of EBO1 & EB16, so does it matter which kernel I flash? When I look at about phone>build number: it shows sch-I5000.EB01. So would I be ill advised to use the EB16 kernel should there be any type of benefit to one kernel vs the other?

Thanks for any insight.

I dont really notice a difference between the two other than EB16 having the dummy tethering capability, for now im sticking with it.
 
I updated sc2.5nv to 2.8v today. I had problems activating the lag fix in cwm. After reading a little further it looked like there was a known issue about 2.8v taking voodoo. I flashed the EBO1 voodoo kernel and got the lag fix to take, heard the lady and got a 1461 in quadrant. Thanks to this thread and GM for making it mostly worry free.

I have a question about the two options for voodoo kernels in adryn's SC 2.8 sticky. What is the difference between the EB01v kernel vs the EB16v kernel? It is my understanding that after SC 2.4 that it was a hybrid of EBO1 & EB16, so does it matter which kernel I flash? When I look at about phone>build number: it shows sch-I5000.EB01. So would I be ill advised to use the EB16 kernel should there be any type of benefit to one kernel vs the other?

Thanks for any insight.

the malware protection and the dumby teather in the eb16 version.
 
  • Like
Reactions: living the dream
Can't get lagfix to take. What the heck?

I've never had issues with voodoo before, but I flashed the full stock dl01 odin from 2.6v, then flashed full 2.8nv in odin. Went in and installed the voodoo kernel, and then tried to enable lagfix before rebooting. No lady android. I even tried downloading the full 2.8v and installing it. I can't get lagfix to take.

It shows enabled when I go back in to check the settings, but quadrant scores are sub 1000's. So disappointing. Any thoughts?
 
Can't get lagfix to take. What the heck?

I've never had issues with voodoo before, but I flashed the full stock dl01 odin from 2.6v, then flashed full 2.8nv in odin. Went in and installed the voodoo kernel, and then tried to enable lagfix before rebooting. No lady android. I even tried downloading the full 2.8v and installing it. I can't get lagfix to take.

It shows enabled when I go back in to check the settings, but quadrant scores are sub 1000's. So disappointing. Any thoughts?

you are using the clockwork that says
e:missing blahblah blah
when you boot into it?
 
Can't get lagfix to take. What the heck?

I've never had issues with voodoo before, but I flashed the full stock dl01 odin from 2.6v, then flashed full 2.8nv in odin. Went in and installed the voodoo kernel, and then tried to enable lagfix before rebooting. No lady android. I even tried downloading the full 2.8v and installing it. I can't get lagfix to take.

It shows enabled when I go back in to check the settings, but quadrant scores are sub 1000's. So disappointing. Any thoughts?

you are using the clockwork that says
e:missing blahblah blah
when you boot into it?

Also, I was doing some reading here and at XDA, and it seems some people have had problems enabling lag fix and voodoo with the EB16 kernel included in sc 2.8, so Adrynalyne put links for EB01 kernels in his superclean thread. Not sure if that is the problem here.
 
I was using the E: error blah blah blah one, and thought that may have been it, so I flashed the cw all from xda - it's the one that doesn't give those errors (new red, I believe) in odin.

Anyway - I hope that's all it is - just a kernel issue. Landshark - does the EB01 that Adryn put up, have the built in dummy wifi tether. If so, are kernels ok to just flash over top of each other without a removal process?

Thanks, guys. Yeah - I know how lagfix works - I'm just frustrated not having it do what it's supposed to.
 
Last edited:
Problem:

Applying new themes caused phone to “hang” during boot animation. Installing Voodoo per instructions caused same behavior. At boot animation you would feel the phone vibrate once then after a 5 to 10 sec pause it would vibrate again twice in succession. This loops and continues to happen until you pull battery or use three button method to boot to recovery.

Cause:

Issue with format of SD Card and or possibly data on SD card. Even after formatting SD card I had same issue after copying data to SD card from computer. Restoring apps via Titanium would Force Close (FC) after a reboot and system settings were not sticking after reboot.

Resolution:

Backup required data only off of your SD Card. Music and VCard for my contacts was all I kept.

1. Reboot to recovery and clear the following:

a. Main Menu
i. wipe data/factory reset
ii. wipe cache partition

b. Advanced Menu
i. Wipe Dalvik Cache

c. Mounts and storage Menu
i. Format boot
ii. Format system
iii. Format data
iv. Format dbdata
v. Format sdcard
vi. Format sd-ext

2. Power down your phone

3. Install your preferred Kernel / ROM. (NON VOODOO) Get them HERE

a. Use DroidXcons easy one step found HERE or

b. Remove SD Card and use a card reader to copy Non Voodoo Kernel / ROM to it

4. Once NON Voodoo Kernel / ROM is installed boot phone

5. I have noticed after a Kernel / ROM is applied settings don’t “stick”. Before you setup your google account etc reboot phone.

6. Run through the setup wizard. Make sure you have Root installed and working.

7. Remember to turn on “Debug Mode” in options

8. If you don’t want VooDoo you are done. If you want VooDoo continue

9. Download your Voodoo Kernel / ROM and put on your SD Card

10. Reboot into RED CWM Recovery. If you boot into anything other than RED you will need to flash via Odin CWM-Recovery-ALL found HERE first

11. Choose the following:

a. Install zip from sd card
b. Choose zip from sd card
c. Browse to and select your Voodoo Kernel / ROM you downloaded and execute it
d. When this completes if you are not at the main CWM page hit the left soft menu key until you are back at main menu
e. Choose the following:
i. Voodoo Menu
1. enable lagfix
2. /system lagfix on
f. From here hit your left soft menu key to return to main menu again and choose reboot.

If you do not hear a woman’s voice and your phone boots up the lag fix did not take. In my experience it seems RED CWM does not appear to be able to handle multiple different options being selected in one session.

I had to reboot to RED Recovery and here I applied my selected kernel again. I then went back to main menu > voodoo > and enabled the lag fix again. I only choose the Second lag fix option not the first.

If this does not work go back to RED Recovery and apply your kernel yet again and then in the main menu > voodoo > options select the first lag fix option again. From here I heard the woman’s voice letting me know it was converting from RFS to EXT4 and my phone did not hang at boot animation any longer.

*NOTES* (Taken from GizmoDroid) at XDA Developers site

just a couple notes to the first timers:

1. Most ROM's currently are bundled with a kernel. For example, SuperClean installs CWM, kernel, and system image all in one flash, so no need to flash a separate kernel or CWM after flashing the ROM.
2. Currently, in the newest RED CWM, there are two enable options in the voodoo menu:
• "enable lagfix" - this converts all rfs partitions to ext4 except your "system" partition
• "/system lagfix" - this converts your "system" rfs partition to ext4
You will need to hit both of them for full optimization.

After selecting "enable lagfix", the text at the bottom will change to:



Voodoo lagfix is actually: disabled
next boot: enabled

Options:

/system lagfix conversion: yes
debug mode: no



Unfortunately, the current CWM has a little glitch that can be confusing. After rebooting, "Voodoo lagfix is actually:" is supposed to change to "enabled" but it will always say "disabled". Rest assured though, it is enabled.

A big thanks goes out to gunnermike53 for helping me diagnose / troubleshoot this issue.
 
  • Like
Reactions: gunnermike53
Thank you Mr. Killyourself for the detailed explination. I know you are glad to finally have it fixed. It only took what, 3 days.:D