My T-Mobile Vibrant (launch unit) was flashed to Bionix 1.3 w/ Voodoo. No problems there. I saw some large blue text on a black background that was too big to fit on the screen so I couldn't read it before it quickly rebooted. I hope it wasn't important. I've not applied any lag fixes before now.
Whether I try the Bionix 1.3 with voodoo or Bionix 1.3 w/ stock kernel and try to flash Voodoo separately doesn't seem to matter. The voodoo folder is present and contains logs only. Voodoo is not disabled.
The voodoo update never looks like it takes long enough to perform the file system conversion. When issuing the "mount" command, I see RFS for system, data, etc.
Why won't it convert the RFS to EXT4?
Any ideas?
Can I send these logs somewhere?
epakrat75 said:
My T-Mobile Vibrant (launch unit) was flashed to Bionix 1.3 w/ Voodoo. No problems there. I saw some large blue text on a black background that was too big to fit on the screen so I couldn't read it before it quickly rebooted. I hope it wasn't important. I've not applied any lag fixes before now.
Whether I try the Bionix 1.3 with voodoo or Bionix 1.3 w/ stock kernel and try to flash Voodoo separately doesn't seem to matter. The voodoo folder is present and contains logs only. Voodoo is not disabled.
The voodoo update never looks like it takes long enough to perform the file system conversion. When issuing the "mount" command, I see RFS for system, data, etc.
Why won't it convert the RFS to EXT4?
Any ideas?
Can I send these logs somewhere?
Click to expand...
Click to collapse
Unfortunately it seems like a lot of people are having a problem getting voodoo to install. Personally I've enabled and disabled it plenty of times without any issues. From what I've heard, some people have flashed back to the vibrant stock using odin, then flash a rom with voodoo. Its worth a shot.
Thanks so much for the reply!
However, I recently saw a tweet from justanotherdev that said (as I understand it) that there is a hardware compatibility issue for some TMO Vibrants having a larger NAND chip preventing install due to the config being unsupported. Beta 5 is supposed to fix this and finally allow install.
If I can't get it to work after one more try, I may just wait for Beta 5 and try that with the Bionix 1.3 w/ stock kernel or Bionix v1.4 w/ Beta 5.
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
When I installed Bionix Fusion I tried also to install the Voodoo lagfix. When I did I ran Quadrant and my performance didn't improve.
I figured that I did not install it right, I then went right into performing the lagfix found on the Bionix Fusion thread which worked great.
Now, I'm wondering if I still have Voodoo running or installed. I have a Voodoo folder on my internal card and it contains log files and txt files but nothing else. The txt files contain messages like "This model is not supported".
The reason for my question is because I want to flash a new Kernel that requires that you are not running Voodoo. How can I be absolutely sure I am not running it?
Thanks.
Check the website...project voodoo there is flashable "dissablelagfix"zip and instructions do you can be certain thats its off, hope this helps
****'ll buff out
Thanks. Worked great!
You have a Vibrant with a special type of NAND memory that Voodoo is not compatible with, so Voodoo automatically disabled itself on your phone. You're fine to flash anything.
Sent from my SGH-T959 using XDA App
If your a noob, stay with OCLF
but overall i say VOODO is THE best lagfix.
The latest stock kernels collection with the latest Voodoo from supercurio are the best there are, since the latest Voodoo lag fix concerts not only /data into EXT4 but /system, /cache and /dbdata as well.
Another benefit of Voodoo over the OCLF is the filesystem used, OCLF is EXT2 based, it is faster than EXT4 but less reliable and there are reports that the lag comes back up in a few weeks or even days after the install.
I just Voodoo fixed my Nero V1 install with JL4+latest Voodoo, and the thing flies off the charts. My experience was always good with the Samsung stock RFS, good but not great, and with Voodoo it is great!
P.S. Do not forget to RTFM or you will be a sad panda one day.
lqaddict said:
The latest stock kernels collection with the latest Voodoo from supercurio are the best there are, since the latest Voodoo lag fix concerts not only /data into EXT4 but /system, /cache and /dbdata as well.
Another benefit of Voodoo over the OCLF is the filesystem used, OCLF is EXT2 based, it is faster than EXT4 but less reliable and there are reports that the lag comes back up in a few weeks or even days after the install.
I just Voodoo fixed my Nero V1 install with JL4+latest Voodoo, and the thing flies off the charts. My experience was always good with the Samsung stock RFS, good but not great, and with Voodoo it is great!
P.S. Do not forget to RTFM or you will be a sad panda one day.
Click to expand...
Click to collapse
whats RTFM?
xriderx66 said:
whats RTFM?
Click to expand...
Click to collapse
read the effin manual; basically, just ensure you do your hw with any lagfix and backup with nandroid first
also: get comfortable with odin before embarking on any crazy adventures
Lol especially if u like to flash a new rom every other day like me.
Same here i only used OCLF with my roms, i never used Voodoo. I see some people dont like to use Voodoo, and it can be dangerous if you dont uninstall it. Im assuming to just disable Voodoo you make that folder in the voodoo folder and thats it right?
I also say Voodoo. I used to use OCLF but I like voodoo a lot better. And voodoo is as easy as pie to install these days. Just flash a voodoo enabled Kernel.
mystycs said:
Same here i only used OCLF with my roms, i never used Voodoo. I see some people dont like to use Voodoo, and it can be dangerous if you dont uninstall it. Im assuming to just disable Voodoo you make that folder in the voodoo folder and thats it right?
Click to expand...
Click to collapse
Very close, it is a file rather than a folder. Basically that is it though. There is even a flashable version you can do from Clockwork Recovery.
It is just absolutely imperative that you disable it before doing anything that will change these file systems (/system, /data, /dbdata, or /cache) outside of the running OS. Things that might do this will include: flash a new ROM, flash a mod that will write to any of those file systems, or clear the dalvik cache.
Just wondering what is voodoo exactly? I flashed to nero v3, but not sure about enabling voodoo because I'm more concerned about battery life. However, besides the notes on that page, what else does voodoo do?
Your current system type is RTF or something.
Voodoo makes it ext4,.which is faster, more stable, and currently the latest thing.
I don't understand why every rom doesn't have voodoo built in
Enable it. You'll enjoy the benefits & your battery life will be fine.
Just remember to disable voodoo via recovery before flashing back to a previous backup or flashing a new kernel.
You're battery Will be fine. I've been running nero since day one and the battery is fantastic with voodoo enabled. Also tried it disabled, and haven't noticed any difference.
Sent from my SGH-T959 using XDA App
Voodoo DOES effect battery but by so low that you can barely notice
xriderx66 said:
Your current system type is RTF or something.
Voodoo makes it ext4,.which is faster, more stable, and currently the latest thing.
Click to expand...
Click to collapse
To add a little more to the mostly correct explanation above: This is the file system used by your phone -- how it keeps track of file and folder names and sizes and contents and permissions and so on. The Windows equivalent would be file systems like FAT32 and NTFS. That's why there is a conversion when you enable voodoo -- it's changing the Samsung RFS system to ext4.
(RFS stands for Robust File System, which is Samsung's spin on a FAT file system from the old days of DOS... so you can see why people don't have much respect for it. Android by default from Google uses YAFF.)
It's probably safe to say that in the full-size computer world, most Linux systems run some sort of ext-based file system.
It's a Very Good Thing.
I'm running Nero V3. How do I know if I have voodoo enabled?
Never mind. Figured it out.
Thanks for the explanations, just out of curiousity can you also install nero updates on top of each other without any concerns?
dekka83 said:
Thanks for the explanations, just out of curiousity can you also install nero updates on top of each other without any concerns?
Click to expand...
Click to collapse
The first day I flashed Nero I messed up something with Titanium backup and decided to just wipe and flash again. I had already enabled voodoo and I did not do anything to it before I flashed and everything worked out fine.
I've spent a lot of time on here the last 2 weeks reading as much as possible about flashing. I finally took the plunge and flashed Axura 2.2.6 onto my Vibrant, and I love it.
Now, I am intrigued by the new Bionix-V ROM out, but I am not sure I understand everything I need to do if I want to change ROMs. Also, I have a few questions I can't seem to get a grasp on.
1. Before flashing or anything, I rooted with Ryan's OCLF. When I flashed with Axura, did that install and enable voodoo on my phone? Did it override OCLF? I know you are not supposed to be running both.
2. I cannot figure out this kernel thing. Do I just let the ROMs handle them, or am I supposed to be updating on my own?
3. I don't do anything with the modem (e.g., KA7), correct? As I understand it, the ROMs are based off of this.
4. I have read some stuff recently about how Titanium Backup has caused some issues. Should it not be used when going from ROM to ROM?
5. I have read some stuff recently about the battery and cycling it. Should this be done if I want to change ROMs?
Thanks in advance.
cccheel said:
I've spent a lot of time on here the last 2 weeks reading as much as possible about flashing. I finally took the plunge and flashed Axura 2.2.6 onto my Vibrant, and I love it.
Now, I am intrigued by the new Bionix-V ROM out, but I am not sure I understand everything I need to do if I want to change ROMs. Also, I have a few questions I can't seem to get a grasp on.
1. Before flashing or anything, I rooted with Ryan's OCLF. When I flashed with Axura, did that install and enable voodoo on my phone? Did it override OCLF? I know you are not supposed to be running both.
2. I cannot figure out this kernel thing. Do I just let the ROMs handle them, or am I supposed to be updating on my own?
3. I don't do anything with the modem (e.g., KA7), correct? As I understand it, the ROMs are based off of this.
4. I have read some stuff recently about how Titanium Backup has caused some issues. Should it not be used when going from ROM to ROM?
5. I have read some stuff recently about the battery and cycling it. Should this be done if I want to change ROMs?
Thanks in advance.
Click to expand...
Click to collapse
ok..
1. I dont know if Axura had Voodoo....but if you flash a custom ROM (weather its Axura, Bionix-V..etc..) it'll always be rooted
2. Some folks (like me) prefer going back to stock 2.1 with Odin...then flashing their new custom ROM...so they dont run into ghost files and kernel issues...but its not needed....some times you can go from ROM to ROM
3. the KA7 is the newest leak from Samsung for our phones....when a custom ROM is made...it is made from the newest leak...which now is KA7..this way the ROMs stay up to date
4. Titanium Backup is a great tool...almost a must use tool if you're going from ROM to ROM....Titanium Backup Pro is a lot more speedier and has more features that the free version...but the free one is also good
5. I personally make sure my batt is fully charged and is plugged in while i'm flashing so it reduces the time i have to re-condition...you should read a little bit more on that
1. Before flashing or anything, I rooted with Ryan's OCLF. When I flashed with Axura, did that install and enable voodoo on my phone? Did it override OCLF? I know you are not supposed to be running both.
It sounds like you just rooted with OCLF, no issue there. OCLF lag fix converts your file system to EXT2, voodoo is EXT4. If you heard Linda (lady's voice) at first bootup, your system is EXT4 via voodoo. You can download voodoo toggle from the market to verify it is working, and to disable (which you would do if you flash something that is NOT voodoo). Also, it is not possible to run both.... file system is one or the other. EXT4 is better (even though EXT2 will show a higher quad score).
2. I cannot figure out this kernel thing. Do I just let the ROMs handle them, or am I supposed to be updating on my own?
The ROM will handle this. You only need to flash another one if you really want to..
3. I don't do anything with the modem (e.g., KA7), correct? As I understand it, the ROMs are based off of this.
The ROM will handle this. You only need to flash another one if you really want to, ie, you have better signal with one vs the one included in your rom.
4. I have read some stuff recently about how Titanium Backup has caused some issues. Should it not be used when going from ROM to ROM?
Ignorance causes issues, not Titanium Backup. Check the noob guide in my signature to learn how to use it properly.
5. I have read some stuff recently about the battery and cycling it. Should this be done if I want to change ROMs?
Always. Also in the noob guide.
Thanks
Thanks. You guys rock.
Quick question/comment. When I used OCLF, I know that I rooted and I also ran the lagfix, because my quadrant score went up drastically. Not sure if this matters.
I went into Astro, and I have a folder for voodoo with log files in it, so this means I must have voodoo, right?
I downloaded the voodoo toggle, but I don't see it anywhere on my phone. Does it only show as a setting somewhere?
Voodoo toggle = Reboot Button (no clue why the dev did this). App works great though.