So far I am unable to get voodoo going on the Com ROM. Everything else is working great. I installed it over ED01 Debloated with cache and dalvik wipe. In CWR under voodoo, it says lagfix enabled is default. The log at the bottom says disabled. When I select "enable lagfix" nothing changes. Scored 992 on quadrant.
Went back and did a complete data wipe, re-flashed the ROM, nothing changed.
Sent from my SCH-I500 using Tapatalk
Check the voodoo folder on your on your sdcard and make sure there is not a disable-lagfix file. If there is delete it and reboot.
good day.
Did the trick!
Thanks
Sent from my SCH-I500 using Tapatalk
Must be working....quadrant 1524.
Sent from my SCH-I500 using Tapatalk
Related
Sorry if this has been answered (I know its frowned upon), but I'm a bit pressed for time. I installed Voodoo V3 a little while back on JFD, but disabled it for JI6 using the 'disable lagfix' file in Voodoo folder method.
Last night, I flashed Obsidian v3 with VooDoo, but the new version will not install (I'm assuming that Voodoo was not completely uninstalled), and I can't use any of the OCLF methods pre-installed with the ROM (says: You already appear to have another lag fix intalled! (/system/bin/playlogos1 less than 5kb).
I am still running Obsidian v3.
I'd appreciate the help and a walkthrough if possible!
Thanks in advance and sorry for the trouble.
Try to flash sombionix voodoo disable.zip file into clockwork recovery. You should hear voice now converting to rfs. Once done, and it boots up. Go back to clockworkmod, flash another rom without voodoo. Than you should be okay from there on.
Sent from my SGH-T959 using XDA App
Flashing the disable_lagfix.zip simply places a disable lagfix file in the voodoo directory (i think). I had that done before I flashed JI6 and obsidian...and the issue never went away.
Look in files folder, you see anything labeled voodoo?
Sent from my SGH-T959 using XDA App
Create disable-voodoo empty text file but save as disable-voodoo file and place it in your voodoo folder and reboot. See what happens.
Sent from my SGH-T959 using XDA App
at the root of my internal SD is the Voodoo folder. Within it is a folder labeled logs, and also the disable_lagfix file i put in there to disable it. However, if i delete this folder, Voodoo will reinstall itself automatically when i reboot.
when i place the disable_lagfix file within that directory...it disables Voodoo, but does not completely rid the system of it. When I installed Obsidian v3 with Voodoo, it did not install the new version of VooDoo because the old one still existed. Also, OCLF also will not install and i think its also because of this.
Try pushing the disable voodoo via adb.
Sent from my SGH-T959 using XDA App
Or try to to do a factory restore first from clockwork. See what hapoens. I had that same issue too while back.
Sent from my SGH-T959 using XDA App
Swing by the project-voodoo dot org site and go to documentation (i would give you a link if i could post one but...). Follow the first set of instructions on there and you'll get voodoo out in no time. Now, I'm not entirely sure if the vibrant devs accept this as the proper method of removal for our phones but I just tried this a couple of nights ago to get Soniqu3's theme on Onyx R4. Hope this helps.
Use terminal emulator and type mount. If it says data/ rfs in there, voodoo is disabled. Are you using the oclf included in the rom? Sombionix said the one in the market will not work.
Last option for you. Do this...
http://www.teamwhiskey.com/installation-guide/rfs-lag-fix-and-you
Its the same thing oclf does, just not one click.
Sent from my SGH-T959 using XDA App
Sent from my SCH-I500 using XDA App
Even after i run "fix permissions " in CWM I am getting some FC'S in the same programs. Anyone have a fix for the fix?
Running jt's ec10 4/7
SC 2.9.2
NITRODARK V.4
Sent from my SCH-I500 using XDA App
Have you tried booting into recovery, wiping cache and dalvik. restart?
T.M.M.L said:
Have you tried booting into recovery, wiping cache and dalvik. restart?
Click to expand...
Click to collapse
Been there and done that. Even performed un-install and re-install a few times.
Sent from my SCH-I500 using XDA App
Some of the Developers have said it helps to completely wipe everything as in odin back to something like EB01 with the pit files so it repartitions your internal storage. Essentially it's reformatting your phone to new again, then of course rooting unless you odin in CWR your then drop in your favorite rom. it helped me the few times i had a ton of FC issues and the one time i had SOD. just my suggestion though.
First though, do you have GizmoDroids fixed CWR? Ihttp://forum.xda-developers.com/showthread.php?t=1017817f not you might want to start here before you do anything else.
DaleV said:
Some of the Developers have said it helps to completely wipe everything as in odin back to something like EB01 with the pit files so it repartitions your internal storage. Essentially it's reformatting your phone to new again, then of course rooting unless you odin in CWR your then drop in your favorite rom. it helped me the few times i had a ton of FC issues and the one time i had SOD. just my suggestion though.
First though, do you have GizmoDroids fixed CWR? Ihttp://forum.xda-developers.com/showthread.php?t=1017817f not you might want to start here before you do anything else.
Click to expand...
Click to collapse
I've done a full wipe with Odin just the other day. Didn't do the pit file though. Maybe I'll give that a try since I'm probably going back to try the dl09 modem on froyo to see if signal issues stabilize. Thanks for the input!
Any other suggestions?
Sent from my SCH-I500 using XDA App
I have had sporadic results running the fix permissions from inside CWM. With the different versions/fixes/patches to it I am never sure which one I am on so I don't use that method at this time. Try running the fxpms from a terminal emulator with root access after boot up, or with adb. That should run correctly.
I have also had tons of force closes lately and found that the problem was that the database was getting corrupted after trying to restore apps + app data in Titanium Backup. Only way I could get that fixed was to wipe and reload a rom and manually install the apps. After that I haven't been having issues with FCs.
deadcaper said:
I have had sporadic results running the fix permissions from inside CWM. With the different versions/fixes/patches to it I am never sure which one I am on so I don't use that method at this time. Try running the fxpms from a terminal emulator with root access after boot up, or with adb. That should run correctly.
I have also had tons of force closes lately and found that the problem was that the database was getting corrupted after trying to restore apps + app data in Titanium Backup. Only way I could get that fixed was to wipe and reload a rom and manually install the apps. After that I haven't been having issues with FCs.
Click to expand...
Click to collapse
I'll give it a run through on terminal emulator. I was using tb for awhile and stopped using it for some reason. I hope jt's updated fix comes out soon.
Any suggestions on modem kernel to use?
sent from my fascinated phone EC10 4/8 SC 2.9.2 NITRODARK V.4
Ok, this being my girlfriend's phone, I dont get to mess around with it often and am pretty new to it. I flashed CI500_VZW_EB01_FROYO_REL.tar.md5 via Odin 1.3 and also flashed the red cwm. I booted up and restarted to the cwm and installed the superuser that was with the busy box. when I installed titanium backup, it kept on force closing so I tried to go to cwm and factory reset, it would not mount the sd. Tried going into the mount/ unmount and mount there but with no luck. so I thought it was the sd card but when i go to install zip menu, I can access the sd card. what can be wrong?
is the phone a verizon fascinate?
Yea its verizon. Also superuser works... But titanium cant get access.
Sent from my SCH-I500 using XDA App
Its probably the permissions. .. Check super user to see if titanium is on allow. Can always reinstall
Sent from my SCH-I500 using XDA App
If you have problems with Titanium Backup its recommended to select Problems on the main screen and have it download a reliable busybox for TB.
If your wanting to be rooted you should Odin an EB01 package that comes rooted + recovery. I've never had to install superuser because its ready to go after you Odin.
If you want to start from scratch go here and follow instructions:
http://forum.xda-developers.com/showthread.php?t=1017817
for the pit file:
http://dl.dropbox.com/u/2056318/atlas_v2.2.pit
hmm reading that guide kinda points to the bad voodoo conversion. Not only is titanium being force closed, all installed apps do it after a restart. What else can i do?
I had this same problem with Ti yesterday, all I had to do was go into sup and forget Ti, then go to appear manager and CFC clear data whatever, just make it forget you used it yet. Then I just ran Ti again, it asked for sup permission, everything worked fine then.
Sent from my SCH-I500 using XDA Premium App
well its not just titanium back up. when i restart the phone, everything that i had downloaded from the market force closes.
Sounds like your dbdata is messed up, reodin with the atlas PIT file
http://adbdev.com/danknub/atlas_v2.2.pit
Sent from my SCH-I500 using XDA App
micellis said:
Sounds like your dbdata is messed up, reodin with the atlas PIT file
http://adbdev.com/danknub/atlas_v2.2.pit
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
yea i already tried that.... but the weird part is when i odin the atlas file, supposedly there should be a lady saying something about the phone being repartitioned? I never got it to say that. I odined atlas with the image file from the guide that was posted above. what am i doing wrong? i clicked the repartition box
syn87 said:
yea i already tried that.... but the weird part is when i odin the atlas file, supposedly there should be a lady saying something about the phone being repartitioned? I never got it to say that. I odined atlas with the image file from the guide that was posted above. what am i doing wrong? i clicked the repartition box
Click to expand...
Click to collapse
I clicked on the repartition and it never worked. I left it unchecked and it seemed to work until I tried to flash the radio. I changed computers and for some reason odin ran everything fine. Now I am running EC01.
Running Das BAMF Remix v1.6.3 and the kernel that comes with it (bamf 4.4.7).
I was interested in "upgrading" my kernel to Adrynalyne's Control Freak 2.0. I've never flashed just a kernel, only a ROM.
Questions:
1. What is the advantage of upgrading to CF 2.0?
2. Do I flash it in Clockwork Recovery just like a ROM, but without wiping data/cache?
3. I control my frequency/governor through the Das BAMF Toolkit under CPU Settings, so I uninstalled the SetCPU app (no reason to have two). Can I control CF 2.0 with my current Das BAMF Toolkit or do I need the SetCPU app?
4. I read.... "***WARNING*** These are advanced kernels and you CAN end up not booting if you do not know what you are doing. If In doubt, use a bamf kernel, or DO NOT modify this kernel's advanced options." How can I screw this up if I flash it like a regular ROM?
It sounds like you don't know enough about goofing with the cf kernels advanced commands so as long as you stay away from the command line and/or keep a backup kernel you should be fine.
In order to flash a kernel boot into recovery, don't use Rom manager or kernel manager.
Once in recovery wipe the cache partition, go to advanced and wipe David cache, ignore the SD-ext error.
Go back and select choose zip to install.
Navigate to the kernel you downloaded and flash it.
Reboot and enjoy.
Make sure to create a backup prior to flashing encase you do goof something up.
Sent from my ADR6400L using XDA Premium App
ibsk8 said:
It sounds like you don't know enough about goofing with the cf kernels advanced commands so as long as you stay away from the command line and/or keep a backup kernel you should be fine.
In order to flash a kernel boot into recovery, don't use Rom manager or kernel manager.
Once in recovery wipe the cache partition, go to advanced and wipe David cache, ignore the SD-ext error.
Go back and select choose zip to install.
Navigate to the kernel you downloaded and flash it.
Reboot and enjoy.
Make sure to create a backup prior to flashing encase you do goof something up.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Thanks.
I'm guessing the command line is something not easy to access?
How do I keep a backup kernel?
Sent from my ADR6400L using XDA Premium App
Its easy to access.
For a backup kernel download a froyo kernel from any of the available ones out there. Adrynalyne or imoseyon is what I use.
sent from a sweet paper weight.
ibsk8 said:
Its easy to access.
For a backup kernel download a froyo kernel from any of the available ones out there. Adrynalyne or imoseyon is what I use.
sent from a sweet paper weight.
Click to expand...
Click to collapse
Do I just put the backup kernel on the root of my SD card?
I'm running the CF 2.0 kernel right now with no problems so far.
Sent from my ADR6400L using XDA Premium App
I have a Thunderbolt running das bamf 2.0-5 and I tried to restore to my backup but it aborts during the system reformat? Any ideas. Thx
Sent from my ADR6400L using XDA App
elliott35 said:
I have a Thunderbolt running das bamf 2.0-5 and I tried to restore to my backup but it aborts during the system reformat? Any ideas. Thx
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Open rom manager, hit the menu button choose clear download cache. Hit menu again, choose settings, tick the erase recovery box. Go back to the main screen in rom manager, reflash clockwork mod recovery.
Choose fix permissions. Reboot system. Reboot to recovery and try to restore a backup.
Let us know if it works.
sent from a sweet paper weight.