Related
Hey guys, first off sorry if this is in the wrong section, but i REALLY need help and apparently im more booby than i thought.
So i flashed the bionix 1.3 rom back when i first saw it, and i flashed the voodoo version, so now i want to upgrade to 1.5 voodoo. The thing is, i cant disable the lagfix!
What i do is place the folder called ONLY " disable lagfix " and reboot, and i hear the robot lady SAY that it successfully converted back to rfs! so it WORKS.
But then when i boot into recovery to flash bionix 1.5, EVERYTIME, it says converting back to ext4 -_-
PLEASE HELP ME!
place the folder...?
it's supposed to be "disable-lagfix" in /sdcard/Voodoo and reboot.
zephiK said:
place the folder...?
it's supposed to be "disable-lagfix" in /sdcard/Voodoo and reboot.
Click to expand...
Click to collapse
JAC himself said for it to be "disable lagfix" and ya i put in in /sdcard/Voodoo
but ill try the dash in disable-lagfix
Weird.. I remembered it said "disable-lagfix" in the past. Guess he must of changed it, but I did name it disable-lagfix yesterday prior to flashing Frankin-Twiz Update4 and it has never done me wrong with uninstalling Voodoo.
I just took a blank text file named Disable lagfix (taking out the .txt of course) and dumped it in the Voodoo folder, worked just fine for me.
Could it possibly be a Bionix bug?
zephiK said:
Weird.. I remembered it said "disable-lagfix" in the past. Guess he must of changed it, but I did name it disable-lagfix yesterday prior to flashing Frankin-Twiz Update4 and it has never done me wrong with uninstalling Voodoo.
Click to expand...
Click to collapse
I tried the dash in disable lagfix and it said succeffully reverted back to rfs like it dos without the dash. now, do i DELETE the folder called voodoo b4 booting into recovery to flash bionix 1.5 or do i leave it there?
holysmokesbatty said:
I just took a blank text file named Disable lagfix (taking out the .txt of course) and dumped it in the Voodoo folder, worked just fine for me.
Could it possibly be a Bionix bug?
Click to expand...
Click to collapse
im not sure, but i just did a folder and the robot lady SAID it was converting to rfs... but it said it last time too and once i boot into recovery it says going back to ext4. so do i DELETE anything b4 going to recovery? do i leave the voodoo folder there?
skateral271 said:
I tried the dash in disable lagfix and it said succeffully reverted back to rfs like it dos without the dash. now, do i DELETE the folder called voodoo b4 booting into recovery to flash bionix 1.5 or do i leave it there?
Click to expand...
Click to collapse
No it doesnt matter.. you can leave the folder there, if you leave the file "disable-lagfix" (or "disable lagfix").. it will still work. Just Voodoo won't be activated. I don't use Bionix so I don't know if he included a version with VOODOO pre-installed. But if voodoo is pre-installed and disable-lagfix or disable lagfix is present then the lagfix wont be activated until you remove that file.
skateral271 said:
But then when i boot into recovery to flash bionix 1.5, EVERYTIME, it says converting back to ext4 -_-
PLEASE HELP ME!
Click to expand...
Click to collapse
If you are flashing bionix 1.5 voodoo, then it will continue to convert to ext4 no matter if you have the disable-lagfix in the Voodoo folder.
You need to flash bionix 1.5 that doesn't have the voodoo kernel.
Lakers3408 said:
If you are flashing bionix 1.5 voodoo, then it will continue to convert to ext4 no matter if you have the disable-lagfix in the Voodoo folder.
You need to flash bionix 1.5 that doesn't have the voodoo kernel.
Click to expand...
Click to collapse
so i should disable the lagfix, flash the original version of 1.3, then upgrade to the voodoo version of 1.5?
You need to Download: Bionix 1.5 w/JACs OC/UV Kernel
Then disable lagfix
Then flash Bionix 1.5 w/JACs OC/UV Kernel
Do not flash Bionix 1.5 w/JACs OC/UV VOODOO Kernel, if you flash this it will continue to convert it to ext4
Lakers3408 said:
You need to Download: Bionix 1.5 w/JACs OC/UV Kernel
Then disable lagfix
Then flash Bionix 1.5 w/JACs OC/UV Kernel
Do not flash Bionix 1.5 w/JACs OC/UV VOODOO Kernel, if you flash this it will continue to convert it to ext4
Click to expand...
Click to collapse
wait but then i CANT use voodoo anymore?
skateral271 said:
so i should disable the lagfix, flash the original version of 1.3, then upgrade to the voodoo version of 1.5?
Click to expand...
Click to collapse
You must be joking!... Voodoo is a kernel that converts rfs to ext4 which = "lagfix" ... So if you continue to flash Bionix 1.5 w/JACs OC/UV VOODOO it will continue to convert to
ext4.
Again you must Download and Flash Bionix 1.5 w/JACs OC/UV Kernel
You are causing a constant loop
skateral271 said:
wait but then i CANT use voodoo anymore?
Click to expand...
Click to collapse
if you disable the lag fix, then you are not using voodoo
This is what you do....
Flash Bionix 1.5 w/JACs OC/UV VOODOO
Disable lagfix
Reboot
That's it! DO NOT flash it again!!... Every time you flash it you are installing the "lagfix" again which converts to ext4
This has been moved to the Q&A sub-forum. Please post any future questions there and not in the development sub-forum.
As far as your problem goes: When you create the "disable lagfix" file in the Voodoo folder within your SDCard and reboot, after it's finish disabling the lagfix, DO NOT DELETE the "disable lagfix" file until AFTER you have finished flashing the new ROM. After you have done this, THEN you can remove the file and the process will convert the new ROM's /data partition to ext4 (if you flashed another voodoo kernel, that is.)
The file not only converts the EXT4 back to RFS but also PREVENTS the conversion of RFS to EXT4.
Complete newb here... So i just did the disable voodoo thing exactly as it says here and now my screen is stuck on the vibrant screen not doing anything. Should i pull the battery or??? yeah i got nothin.
davemw2 said:
Complete newb here... So i just did the disable voodoo thing exactly as it says here and now my screen is stuck on the vibrant screen not doing anything. Should i pull the battery or??? yeah i got nothin.
Click to expand...
Click to collapse
Did you hear Linda say anything? It stays on the Vibrant screen while converting but you should hear a voice letting you know the progress and an ETA
My girlfriend has a Vibrant which is not hardware locked. I rooted and installed Bionix w/voodoo on Sept 28. I can't tell in her 'about phone' which version of Bionix she's running, but I believe it's 1.3, as the zip file I downloaded has 1_3 in the filename.
The first big problem I have is that nandroid does not work. If I try to restore to her stock backup I made, it gets an error when trying to mount data. Same error if I try to make a backup of the Bionix ROM. What am I doing wrong? Until I have her phone properly hacked I was just going to keep a backup of her phone and let her use that in the meantime, but can't do that now.
I am familiar with Android and clockwork as I've owned a Droid for half a year and flash new ROMs frequently but I've never encountered that error before. I want to install the new Bionix but without being able to make a backup I don't want to. I don't think it will install properly without being able to mount data anyway. Can someone tell me what I'm doing wrong?
You have to remove voodoo in order to use clockwork.
Ok, I think I can handle that. Can someone explain to me why data can't be mounted with voodoo? Can I just delete the folder and flash the new ROM that includes voodoo?
Yeah in the bionix thread it says nandroid doesn't work with voodoo and shows how to disable it.
Sent from my SGH-T959 using XDA App
velocity92c said:
Ok, I think I can handle that. Can someone explain to me why data can't be mounted with voodoo? Can I just delete the folder and flash the new ROM that includes voodoo?
Click to expand...
Click to collapse
It takes the data, and moves it to a virtual ext4 that it creates, so when nandroid is trying to backup or restore it is looking for the data folders in the wrong place, so it does not work.
You need to follow the voodoo thread, you need to place the file in the voodoo folder, if you delete the folder it may cause you allot more issues, you must install it the way they say in the thread or you can softbrick the phone. And you cannot flash a new ROM with it installed or you again will mess up the phone. The only thing you can do is create the file, put it in your folder and restart the phone, let it do its thing, once it reboots then nandroid will work again.
Thread moved to Q&A.
Noob and hacker in the same sentence...interesting
Sent from my SGH-T959 using XDA App
Pasted in from the Bionix thread:
How-to Disable the Voodoo Lagfix:
1. Once again, you MUST disable the Voodoo lag fix in order to flash any other rom, kernel, or perform a nandroid backup. If you don't...well....lets just say I warned you.
2. Its simple. Create a folder on the root of your sdcard called 'Voodoo'.
3. Now, open notepad or something similar and save the blank file. Name it 'disable-lagfix'. This file cannot have any file extension, so remove it if it does.
4. Place your blank file into the 'Voodoo' folder you made on your sdcard.
5. In order to disable, simply power down your phone and power it back up.
6. FINISHED! You can now flash anything you'd like!
How-to Confirm Voodoo Lagfix is Disabled:
1. In adb shell or terminal type 'mount'
2. If it is disabled is should read '/dev/block/mmcblk0p2'.
3. If it is not disabled, it will read '/dev/block/mmcblk0p4'.
There is also a flashable .zip file that does this for you, if you care to search around and find it. Otherwise, the above will work fine. Once you disable Voodoo and confirm that it's disabled, you'll be able to backup/restore nandroid backups again.
Ok...I know this can be a complicated process if you run into issues...so here is a detailed how to...Make sure and READ thru the WHOLE post!!!!!
INSTALLATION INSTRUCTIONS:
1. ROOT, Flash CWM Recovery
2. Create a FULL nandroid backup
3. Download a kernel of choice - links below
4. Put the kernel on root of sd, or you can leave it in download folder, but DON'T rename the file
5. Boot into Clockwork MOD recovery (either from ROM Manager or manually- hold volume up and down at same time and press power button, then select "apply sdcard: update.zip"
6. In recovery select "Install zip from sd card"
7. Select "Choose zip from sd card"
8. Navigate to the kernel file and select it
9. Let it install, it will take a few minutes...screen will go weird (black with big blue letters) then take you back to recovery.
10. Reboot phone
IMPORTANT: THIS BOOT WILL TAKE A LONG TIME...MAY BE 5-25 MINUTES...WAIT IT OUT. DO NOT PULL BATTERY. EVEN IF IT IS AT A BLACK SCREEN WITH SOFT KEYS LIT UP, DO NOT TOUCH IT. YOU WILL HEAR FEMALE VOICE. THIS IS NORMAL.
11. Once phone boots, download SetCPU from market and set the slider to desired Max. Do not select "Set on boot" and use Conservative mode.
ENJOY!!!!!
KERNEL LINKS:
- jt1134 - [RELEASE] Voodoo (v0.2) ext4 lagfix for Fascinate! Now with AOSP boot animations!
- Dirrk - [KERNEL] Dirrk v01 Voodoo lagfix OC/UV - For Dirrk OC kernels, use the D012 kernels, not D01: D012 - Dirrk > Open the link>select my folder>the samsung and you will see the D012 kernels...
***If you are using jt1134 kernels with boot animation ability, here is how to add it. Find the boot animation you like, download it to your phone. Do not unzip it. Use Root Explorer or Astro File Manager and copy the bootanimation.zip file into either system/media or data/local. Reboot phone to test out.
HOW TO DISABLE VOODOO LAGFIX
1. Use Astro File Manager or Root Explorer app...open the app
2. Navigate to sdcard/Voodoo folder
3. Create a new blank FILE named disable_lagfix....NOT A FOLDER
4. Reboot phone
IMPROTANT: THIS BOOT WILL TAKE EVEN LONGER THAN THE INSTALLATION OF VOODOO KERNEL BOOT...AGAIN, WAIT IT OUT!!!!! DO NOT PULL BATTERY.
NOTE: IF YOU ARE RUNNING ANY OF VOODOO KERNELS, VERSION 0.2+, YOU CAN FLASH ANY OF THE VOODOO OC KERNELS OVER...INCLUDING JT'S OVER DIRRK'S AND VICE VERSA...IF YOU WANT TO GO BACK TO A REGULAR KERNEL, YOU MUST DISABLE VOODOO FIRST...ALSO IF YOU WANT TO CREATE A FULL NANDROID BACKUP AS WELL, YOU MUST DISABLE VOODOO LAGFIX. IF YOU BACKUP WITH VOODOO ENABLED, YOUR DATA WILL NOT BACKUP. IF YOU RESTORE YOUR NANDROID BACKUP, THE KERNELS ARE NOT RESTORED.
If you ran into trouble, start HERE:
- Adrynalyne - How to completely remove Voodoo Lagfix
- Odin Files to get you back to stock
VERY IMPORTANT:
-Battery issue can be because your phone is too hot...pull battery and let it cool down for 5-10 minutes...then boot up and see if its there.
-IF uninstalling v0.1, create a FILE in sdcard/voodoo and NOT a folder...
-Once uninstalled v0.1, DELETE the disable_lagfix file, before flashing v0.2...
-Boots take may FOREVER in between changes, especially after uninstalling.....WAIT it out. It may be 5 minutes, may be 15. Don't start pulling batteries and using Odin just yet.
-READ all instructions carefully and FULLY....
-And lastly, ALWAYS do a nandroid backup.
Wow. Great write up. Thanks a ton for this
Sent from my SCH-I500 using XDA App
I really hope this eliminates 99% of issues that people run into.
Nicely done. Concise and accurate
awwww man, if only this was posted this morning I wouldn't have called for a doa swap.. lol i thought my phone was fubar-ed earlier b/c of the oc kernel.. i finally got everything fixed the hard way by wiping and loading stock kernels.. that didn't work too well either.. long story short i got everything working but after i called for a swap and before this posted lol.. great post!
wish this was in place before i started flashing. lol. i had to learn the hard way. many flashes later i have learned what to do but this definately deserves a sticky so others dont have to go thru what luckly only took me a day to figure out but could have taken longer.
I've been running the 1200 kernal for a few days with no problems. I do have setcpu set to load on boot.....just curious if I should change it? And why? All seems OK.
Nice post, tats.
Kudos for a great, concise write up!
suzook said:
I've been running the 1200 kernal for a few days with no problems. I do have setcpu set to load on boot.....just curious if I should change it? And why? All seems OK.
Click to expand...
Click to collapse
Once you confirm that its completely stable even Dirrks says its OK to set on boot. You just wanna be 100% sure it is before you get caught in an endless boot loop. But yeah a couple days is long enough to ensure stability; go ahead and lock it in if you want
Is this rom and kernel really that much better than stock?
I guess I'm asking is battery life better and is the speed of the phone better with the lag fix??
I have Voodoo .2, and I set the bootanimation in both folders, both in system/media, and data/local, and the standard animation keeps playing anyway.
Anyone have any ideas ????
Bull174
Yes this kernel with voodoo is that much better. Voodoo isn't that BS one click lag fix. Its a real permanent solution." Basically" the same filesystem all other phones come with.quadrant can do 17-1800 which isn't inflated. Its what the galaxy can actiually do. And that just with eclair(2.1) battery life is the same. The phone will likely never lag on u again. And actually with a normal filesystem its prolly the fastest smoothest running phone out there. Would easily put the second generation snapdragons to Shame. If u try it u will be hooked. It is *VERY IMPORTANT* that before u flash any other kernels that u disable ur lagfix first. This can also be done easily with the app "voodoo toggle" in the market. If you like your phone now you will love it now. Take the plunge. You wont regret it. Just do your reading and follow instructions on how to install and remove voodoo to a T and you will be fine.
Sent from my SCH-I500 using XDA App
Wound up having to restore an old voodoo, the v. 0.2 standard clocking one, from a jt's 1.2 OC kernel. The restore worked fine, but I'm currently trying to disable in order to flash stock kernel and a clean ROM and then get voodoo back. The boot up has been going on for about an hour, heard to voice at the beginning and about 20 minutes in. How much longer will it take? I'm getting kinda nervous as I really don't want to have a bricked phone on my hands.
EDIT: It was about 2 hours and I pulled and went to go do an odin restore. The phone flashed PIT, system, kernel and recovery all successfully, I wiped everything from both clockwork and the blue 2e recovery screen, but now I can't access clockwork nor does the phone boot, however it does appear in adb. Does anybody know what I should do?
EDIT2: Reflashed all the files from Odin, got it to boot both into clockwork and pure stock. Gonna go flash a nandroid and get my setup back.
You can use the disable_lagfix as a folder, I have tried it and it works. Voodoo is looking for anything disable*lagfix so it works even with a dash, space, numbers...
I followed each and every direction to the last word, however I can't seem to overclock my phone. I installed the jt1334 kernel, but the max i can go is 1ghz (1000000mhz). help?
EDIT: In addition, I did both a linpack and Quadrant Standard test. my linpack score was "MFLOPS:8.142" and my Quadrant
Standard score is "950".... i don't understand what I did wrong as I see others have QS scores of 1600+ at least 1200+...
xsalientx said:
I followed each and every direction to the last word, however I can't seem to overclock my phone. I installed the jt1334 kernel, but the max i can go is 1ghz (1000000mhz). help?
EDIT: In addition, I did both a linpack and Quadrant Standard test. my linpack score was "MFLOPS:8.142" and my Quadrant
Standard score is "950".... i don't understand what I did wrong as I see others have QS scores of 1600+ at least 1200+...
Click to expand...
Click to collapse
Have you downloaded SetCPU? What are you using to overclock?
mexiken said:
I have Voodoo .2, and I set the bootanimation in both folders, both in system/media, and data/local, and the standard animation keeps playing anyway.
Anyone have any ideas ????
Click to expand...
Click to collapse
I have the same issue. I thought it was originally because I extracted the bootanimation.zip out of the downloaded file but renaming the original file didn't work either.
kupdegrove said:
I have the same issue. I thought it was originally because I extracted the bootanimation.zip out of the downloaded file but renaming the original file didn't work either.
Click to expand...
Click to collapse
If its just the voodoo 0.2 file, then boot animation wont work. It has to be the 1000_bootabimation kernel or the 1200_bootanimation one.
I actually fixed it somehow... I don't necessarily know what I did though. But thank you for your help!
Sent from my SCH-I500 using XDA App
been searching last 2 hours to no avail..
I appreciate any feedback cause I cant seen to get this.
Started with stock rom, un-rooted.
Installed rom manager per bionix instructions..
Downloaded bionix191_stock.zip
Saved to root sd card.
Selected "Install rom from sd card"
Informed me to unroot.
installed ryanZA's oclf from the market to root.
Re-ran rom manager.
Selected again "Install rom from sd card"
Selected wipe data and cache
Reboot process begins.
stops at "update.zip (bad) error.
What am I doing wrong?
try redownloading it.
Thanks for the reply...
I already tried downloading the zip again.
The zip file matches the proper size from
The link as stated on the install info...
I have the copy on my sd card in the root folder
as well as my download folder.
do I have to do something in the OCLF app?
try rooting withouth OCLF, using a normal update.zip
also, did you rename the bionix file?
I didn't know I had to rename the zip.
What do I rename it to?
The rom manager wouldn't run without a root,
so I had to use oclf first...
do I have to odin back to stock to install bionix?
no, dont rename it. this is what I did.
1. Odin to stock http://forum.xda-developers.com/showthread.php?t=734475
2. install the update.zip from stock recovery
3. use market to download ROM manager
4. use ROM manager to reboot into recovery (do not use install rom from SD card)
5. you may need to use stock recovery to reinstall packages
6. in clockwork, install zip from sdcard
7. choose zip from sdcard
8. choose your bionix version
9. install
10. reboot twice
thx Brian, worked perfectly. You are a friend an a scholar!
I installed Bionix 1.9.1 Voodoo (OC/UV/Voodoo Kernel)
Benchmarked at 1878
installed OCLF right after..but the 2.1 & 2.2 lagfixes are unavailable...
Trying to fig out how to install OCLF on top of voodoo?
You don't use both the OCLF and Voodoo at the same. Voodoo requires a bit more reading comprehension and user ability than OCLF. For people that want a LagFix without the hassle of Disabling/Enabling Voodoo every time you reflash; OCLF is for you.
I'm on Bionix 1.9.1 with JACs OC/UV Kernel and no Voodoo (don't really feel the need) and I used OCLF to root way back when I had stock TWiz.
Glad you got it working and from here on out if you flash any of the prominent ROMs available you don't have to revert to stock as most of them wipe clean as part of their script. Just boot into ClockWork recovery, install zip from SD and find whichever ROM you want.
Oh and always nandroid before flashing a new ROM and use Titanium Backup to back up your apps and such.
I actually do not use the voodoo lagfix, because you have to disable it every time you want to flash something. I have had to repartition my phone so many times because of it I finally just stopped using it. Bionix is so fast I don't really see a need for the lagfix anyway.
Sent from my SGH-T959 using XDA App
briankao1992 said:
I actually do not use the voodoo lagfix, because you have to disable it every time you want to flash something. I have had to repartition my phone so many times because of it I finally just stopped using it. Bionix is so fast I don't really see a need for the lagfix anyway.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I second this post. Bionix is fast enough comming from Stock. I do not think I need the lag fix.
Fusion is even better now!!!
I had simplyhoney 2.8 rom and when i tried to upgrade to 5.1 got a voice telling me to convert data partitions and not enough room. Doing a search lead me to voodoo being the cause, maybe. I have unbricked my phone with odin flashed stock rom, flashed simplyhoney 5.1 same error. Reflashed back to stock cleared cache and data, wipe data and factory reset still 5.1 wont load, still i have voodoo files.
From what i have been reading there are different ways to uninstall voodoo based on your voodoo version. I dont remember installing it so i dont know what version i am on. I do have a voodoo folder and in my base directory and i have like 4 voodoo files some really big.
I have tried the disable_voodoo file trick but i want voodoo gone! I dont understand how to do this? When i flash back to stock guides say to clear your files i thought i selected that but my voodoo folders and files remain. Does anyone have any idea how to remove voodoo.
Can they tell me what needs to be selected in CWM???? Which options the exact wording?
I am pulling my hair out!!!
Just get into recovery and disable voodoo. Reboot the phone and it will boot right up. Then if you want, let it sit for few minutes and get back into recovery and enable voodoo and reboot. This time it should convert your partition properly.
You have red recovery right? Disable voodoo option should be in o lagfix options. You can also make a blank file named disable-lagfix and put it in voodoo folder on your sdcard and reboot. That would also disable voodoo. File should have no extension of course.
red recovery right? Whats that?
I looked in CWM in there boot menu and i see the Voodoo section, it is set to disable and not to turn on at next boot. If its disabled then it wont effect flashing ROMs right?
dpelletier said:
red recovery right? Whats that?
I looked in CWM in there boot menu and i see the Voodoo section, it is set to disable and not to turn on at next boot. If its disabled then it wont effect flashing ROMs right?
Click to expand...
Click to collapse
Red Recovery is Voodoo
Blue is Stock
Green is CWR
Turquoise is CM7/ICS flavors
Also the large files on your SD card that are something like .tar.lzo or whatever they are named, you can delete those. That is a backup created when the lag fix was initiated. They take up unneccessary space on your SD card and aren't needed for anything.