Related
This has been updated to be deodexed+root+busybox only (though it still supports JAC kernel out of the box). At this point there are so many different lag fixes that it's hard to keep up with them all.
What it does have:
ROOT
No .odex files (deodexed)
Newest Busybox
ext manipulation files and libs, so it makes it easier to e2fsck or tune2fsck if you want ext4.
Also thanks to eugene373 for his work in establishing a baseline update.zip without which this would have taken a great deal more work.
Should work in clockwork, doesn't seem to need a wipe. If you have problems, use regular recovery, just rename it to "update.zip" on the root of your sdcard and it should flash just fine.
WARNING:
This should be completely safe. Nonetheless, should loss of job/loss of fertility/nuclear war ensue, I am not responsible.
Instructions:
1. Load the .zip file onto the root of your internal SD card (/sdcard)
2. Using Clockwork recovery, do "Install zip from SD card", then "Choose zip from sdcard", choose the VibrantDeodexed.zip, and choose "Yes"
2b.(ONLY If you don't have Clockwork) rename the download to "update.zip" and place it on the root of your sdcard. Then reboot into recovery and choose "Update packages".
3. (Optional) Flash JAC's kernel with ODIN using the directions specified HERE It is more stable and gets better benchmarks but there do seem to be some issues with the screen taking a while to wake up.
http://www.getyourboneon.com/VibrantDeodexed1_2.zip
NOTE: The first boot takes a long time because it has to dexopt stuff.
Version 1.0:
Just stock and rooted w/busybox
Version 1.1:
Uses the latest version of busybox and comes with support for JAC kernel out of the box (no need to flash the init.d update.zip and supersedes my method if his kernel is flashed.)
Version 1.2:
Updated busybox, added ext tools. Removed all lag fixes, though it will still work with the JAC kernels.
There are so many lag fixes out there at the moment that I didn't want to "lock in" people to a particular one.
Part of the high quadrant score is the 90 million triangles/sec. The data script boosts the data score.
Sent from my SGH-T959 using XDA App
what is the ext hack? and how does it make the phone faster?
the ext hack puts the data and dalvik cache on the sdcard on an ext2/3 partition...
it brought my quadrant score from 850-950 up to 1400-1500
its like apps2sd but the apps part is still on the phones internal memory...
original link is here for the hack--http://forum.xda-developers.com/showthread.php?t=739647
anomalous, thanks for all your hard work...
so if we get a good deodexed rom, someone could compile JIT for our 2.1 right?
junkdruggler said:
the ext hack puts the data and dalvik cache on the sdcard on an ext2/3 partition...
it brought my quadrant score from 850-950 up to 1400-1500
its like apps2sd but the apps part is still on the phones internal memory...
Click to expand...
Click to collapse
why does the phone run faster with the data stored externaly? or is it because of the partition type?
im not quite sure, I would have figured our internal mem had a faster transfer rate than an sdcard, but Im on a class 2 and still getting better results... so it cant be a faster transfer rate...
@freedom: put simply, EXT formats run way faster than Fat32, which is what the rest of the storage is.
wiki: EXT3 (common format) and ext4 (latest)
edit: better explanation here
However, I'd most love to see either one of the internal storage (app storage or the other internal) finding a way to be put into EXT3, as that would probably run better than any sdcard.
Just so everyone Knows, the Format via the update script don't work, still trying to find the correct command for it....
But, in clockworkmod, just format the system / data / cache partition's before flashing.
designerfx said:
@freedom: put simply, EXT formats run way faster than Fat32, which is what the rest of the storage is.
wiki: EXT3 (common format) and ext4 (latest)
edit: better explanation here
However, I'd most love to see either one of the internal storage (app storage or the other internal) finding a way to be put into EXT3, as that would probably run better than any sdcard.
Click to expand...
Click to collapse
Er, the internal storage is "rfs", samsung's proprietary fs. (And the read/write speed of fat32 tends to be a little faster than ext2, and TONS faster than ext3/4 - journals slow it down in exchange for stability after crashes)
The increase in speed is just that - faster underlying hardware. The onboard "sd card" (same "disk" that /data is partitioned out of) is heartbreakingly slow.
Disconn3ct said:
The increase in speed is just that - faster underlying hardware. The onboard "sd card" (same "disk" that /data is partitioned out of) is heartbreakingly slow.
Click to expand...
Click to collapse
Is there an app to test thr transfer speed on the phone? I ask because I have moved my data/dalvik to ext3 on a class 6 sd card. When I benchmark reads from Linux the speed and seek time between internal and my sd are not that great yet the actual performance of the phone is as different as night and day.
I wonder if this is more an issue with the rfs implementation than a hardware speed issue. My other thought is that maybe the benefit comes from having a separate I/O lane for loading data/dalvik. Not sure the hardware actually supports multiple/parallel I/O but it's a theory.
Sent from my SGH-T959 using XDA App
How did you de-odex the the core.jar? I've unodexed the whole thing myself as well, as well as optimize the heck out of every jpeg, png and gif inside the apks (excluding 9.png's of course) but I'm having an issue deodexing core.jar. Did you just replace it with the one from the deodex'd SGS ROM?
FastKatt said:
Is there an app to test thr transfer speed on the phone? I ask because I have moved my data/dalvik to ext3 on a class 6 sd card. When I benchmark reads from Linux the speed and seek time between internal and my sd are not that great yet the actual performance of the phone is as different as night and day.
I wonder if this is more an issue with the rfs implementation than a hardware speed issue. My other thought is that maybe the benefit comes from having a separate I/O lane for loading data/dalvik. Not sure the hardware actually supports multiple/parallel I/O but it's a theory.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I'll see what I can do to test it out this afternoon. (If you want to jump the gun, what I'm figuring is finding a static-linked arm version of bonnie++ or similar. Booting recovery, mount data or sdcard - not both - and test. Reboot recovery, test the other one. Maybe test dbdata and external sd as well, but the interesting numbers will be the first two - onboard-with-rfs and onboard-with-vfat..)
ivanmmj said:
How did you de-odex the the core.jar? I've unodexed the whole thing myself as well, as well as optimize the heck out of every jpeg, png and gif inside the apks (excluding 9.png's of course) but I'm having an issue deodexing core.jar. Did you just replace it with the one from the deodex'd SGS ROM?
Click to expand...
Click to collapse
Honestly, used the ROM kitchen for most of it; it uses a brute-force approach to sort out dependencies. Only one I had to do manually was TouchWizCalendar.apk (because it needed both twframework.jar and com.google.android.maps.jar). I'll work on getting the update script working during work later today.
anomalous3 said:
Honestly, used the ROM kitchen for most of it; it uses a brute-force approach to sort out dependencies. Only one I had to do manually was TouchWizCalendar.apk (because it needed both twframework.jar and com.google.android.maps.jar). I'll work on getting the update script working during work later today.
Click to expand...
Click to collapse
Which ROM kitchen? I used my own script. Does the ROM boot up and run doing it that way? Should be interesting to play with.
Hmm, got the update script working almost perfect, but now it causes crashes. Seems to be missing dbus.conf.
OP updated - it works.
I did something very noobish.
I formatted the cache, system and data and forgot to throw the update.zip file onto the internal sd card prior to doing this. I can get into the stock recovery but as far as rebooting the phone to put the update on the internal storage I can't do that. I am able to take out the 2g memory (avatar) and load the update.zip on there but, of course, the stock recovery won't recognize that.
Is there a way to put the update.zip onto the internal memory in the position that I am in? Is there anything I can do?
I think I just made a HUGE no-no.
Any help would be greatly appreciated.
theMAGNUM said:
I did something very noobish.
I formatted the cache, system and data and forgot to throw the update.zip file onto the internal sd card prior to doing this. I can get into the stock recovery but as far as rebooting the phone to put the update on the internal storage I can't do that. I am able to take out the 2g memory (avatar) and load the update.zip on there but, of course, the stock recovery won't recognize that.
Is there a way to put the update.zip onto the internal memory in the position that I am in? Is there anything I can do?
I think I just made a HUGE no-no.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried connecting your phone to your computer while at the recovery, and see if you can access it via ADB?
ArbitrageMan said:
Have you tried connecting your phone to your computer while at the recovery, and see if you can access it via ADB?
Click to expand...
Click to collapse
No adb shell doesn't find my device
Hey guys, I just need to know how far up **** creek without a paddle I am and how I got here. I had a stock JF6, a friend told me to root with unleash the beast so I did. Been running great and aside from using metamorph to install a few swype themes and nav bar themes, it was stock. I had managed to learn a bit and heard clockwork mod was a great thing, and was making backups regularly.
Well since everything was going so well, I decided to dig deeper and install cognition 2.1. Things went fine, until I got to first boot, then I realized all my stuff was gone, should have known and me being changed my mind. So I went and booted into recovery, and tried to restore my most recent backup, well of course it failed when it came to data because cognition had formatted it.
Well after a lot of formatting data/cache, I tried to install the cognition 2.1.zip, got an error message.. Failed to install. After rebooting I was stuck in the att white screen boot loop. So once again formatted data, and this time I ran update.zip(unleash the beast).
HERES my question, now I seem to have some kind of hybrid, on first boot of cognition I got the custom boot sounds and wallpaper. Nothing now, however my baseband is now JH7, and it says something about voodoo lag fix. But still says 'beast .... Teaser' for system info.
I'm so confused, what's the best way for me to get a stable version of cognition running? Ill just install all my data, I just wabt to know exactly what my phone is running.
Sent from my SAMSUNG-SGH-I897 using XDA App
Best bet is to flash back to JF6, root, install ROM Manager, and load Cognition from that.
Also, that question its better suited for q&a, not the dev forum
Sent from my SAMSUNG-SGH-I897 using XDA App
sdotbrucato said:
Best bet is to flash back to JF6, root, install ROM Manager, and load Cognition from that.
Also, that question its better suited for q&a, not the dev forum
Don't forget to disable lagfix before you Odin.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA App
Sorry, I just mainly check here and the themes and apps section.. Completely forgot about the other ones.
So if I wanted to flash back to jf6.. Would I just get one of these stock dumps floating around and flash it? Or is there a better way?
Sent from my SAMSUNG-SGH-I897 using XDA App
Use the Odin One Click that's posted at the top of this forum. It will flash you back to stock in a matter of seconds.
Sportsguy15 said:
Use the Odin One Click that's posted at the top of this forum. It will flash you back to stock in a matter of seconds.
Click to expand...
Click to collapse
THANK YOU.
this is what I needed to know. So basically, odin one click, use any method to root (probably just use a one-click this time), and then download rom manager and install cognition from clockworkmod? and thats all it would take?
Much easier then what I had in mind.
bamathrasher said:
THANK YOU.
this is what I needed to know. So basically, odin one click, use any method to root (probably just use a one-click this time), and then download rom manager and install cognition from clockworkmod? and thats all it would take?
Much easier then what I had in mind.
Click to expand...
Click to collapse
Yep, that's all you need to do. I've started doing that any time I flash a new rom, ie, One-click to stock, root, rom manager, flash new rom.
I have had similar issues when I try to flash over an existing rom, plus it is nice to start with a fresh rom, no bugs.
bobbylx said:
Yep, that's all you need to do. I've started doing that any time I flash a new rom, ie, One-click to stock, root, rom manager, flash new rom.
I have had similar issues when I try to flash over an existing rom, plus it is nice to start with a fresh rom, no bugs.
Click to expand...
Click to collapse
Data on ext4 survives an Odin flash, so if you are on voodoo, it's a bit more involved than just flashing.
rajendra82 said:
Data on ext4 survives an Odin flash, so if you are on voodoo, it's a bit more involved than just flashing.
Click to expand...
Click to collapse
I saw something like this in the Cognition thread, about creating a file called "disable-lagfix" or something and placing it on the root of the sd. Is that the extra step you are referring too, and if so, I definitely need to do this?
bamathrasher said:
I saw something like this in the Cognition thread, about creating a file called "disable-lagfix" or something and placing it on the root of the sd. Is that the extra step you are referring too, and if so, I definitely need to do this?
Click to expand...
Click to collapse
Yes. That's the correct method to put /data back on RFS. Once you have created the file and rebooted, a robotic lady will inform you that the /data is being converted. Once this boot finishes, you are at a point where Odin or Clockwork will be able to help you. When /data is in ext4 format, the other programs don't recognize it, and don't work properly.
just for future reference, what type of data are you talking about here? I have no data I'd like to keep at this point, after I bricked my phone last night, I basically tried everything in clockworkmod until I got it back to a workable state so I'd have a phone to use today at work. How am I supposed to make it through a work day without being able to text? its impossible. haha.
So if I have no data I desire to keep, is this necessary or is this a different type of data, important data for the system?
bamathrasher said:
just for future reference, what type of data are you talking about here? I have no data I'd like to keep at this point, after I bricked my phone last night, I basically tried everything in clockworkmod until I got it back to a workable state so I'd have a phone to use today at work. How am I supposed to make it through a work day without being able to text? its impossible. haha.
So if I have no data I desire to keep, is this necessary or is this a different type of data, important data for the system?
Click to expand...
Click to collapse
If you noticed in my post I did not say data but /data. There is a difference.
On your Captivate there is a total of 16 GB of internal memory. The memory is partitioned into several block devices. One of these partitions is mmblk0p4, which once booted, is mounted to /data. This directory stores your apps installed from market, your user information, your call log, your text messages, and so on. It has to be working for your phone to boot up properly. Although /data looks like a directory, since it is a link to an actual device, it can be on its own file system which is different than other devices mounted to other directories. On a default Captivate (i.e., before you install Cognition, which includes a choice of two voodoo lagfix kernels) the block device mmblk0p4, mounted as /data is formatted in a proprietary Samsung RFS file system, which is too slow. When you install the voodoo kernel, on first boot, it formats the device in a much faster ext4 file system if there is no file or folder called disable-lagfix in /sdcard/voodoo, thus severely reducing the lag. The problem is that the default kernel, the recovery mode kernel, and the Odin flasher program understand how to deal with this device formatted in RFS. If your block device is in ext4 and you restore the system through Odin, you will end up with Odin not wiping off the contents of /data, which is what you actually wanted. I am not sure if you end up with a working /data device in RFS and a chunk of unused ext4 information, or a kernel not understanding /data in ext4 and hanging. If you are in this state, your best bet is to flash on a voodoo kernel through Odin, which will then understand the ext4 /data. Once the voodoo kernel boots, you then create the disable-lagfix file and reboot, to get /data back in RFS. Then you go into download mode, and wipe the /data on RFS with Odin.
rajendra82 said:
If you noticed in my post I did not say data but /data. There is a difference.
On your Captivate there is a total of 16 GB of internal memory. The memory is partitioned into several block devices. One of these partitions is mmblk0p4, which once booted, is mounted to /data. This directory stores your apps installed from market, your user information, your call log, your text messages, and so on. It has to be working for your phone to boot up properly. Although /data looks like a directory, since it is a link to an actual device, it can be on its own file system which is different than other devices mounted to other directories. On a default Captivate (i.e., before you install Cognition, which includes a choice of two voodoo lagfix kernels) the block device mmblk0p4, mounted as /data is formatted in a proprietary Samsung RFS file system, which is too slow. When you install the voodoo kernel, on first boot, it formats the device in a much faster ext4 file system if there is no file or folder called disable-lagfix in /sdcard/voodoo, thus severely reducing the lag. The problem is that the default kernel, the recovery mode kernel, and the Odin flasher program understand how to deal with this device formatted in RFS. If your block device is in ext4 and you restore the system through Odin, you will end up with Odin not wiping off the contents of /data, which is what you actually wanted. I am not sure if you end up with a working /data device in RFS and a chunk of unused ext4 information, or a kernel not understanding /data in ext4 and hanging. If you are in this state, your best bet is to flash on a voodoo kernel through Odin, which will then understand the ext4 /data. Once the voodoo kernel boots, you then create the disable-lagfix file and reboot, to get /data back in RFS. Then you go into download mode, and wipe the /data on RFS with Odin.
Click to expand...
Click to collapse
thank you for taking your time to write this up for me. Very helpful.
"You do not have enough free space in /data to use this fix. Please free up space before using this fix"
?????????????????
I checked my /data folder -- it's empty except for a few small .txt files
I have a 32 GB external SD card
My internal SD card is 50% free
WHAT GIVES ??????????
Is there any other lag-fix's ?
I have OneClickLagFix V1+ (1.0 with extra's)
Please help
Use voodoo lag fix
same thing happens to me after flashing JPK..
Sent from my GT-I9000 using Tapatalk
Its your internal built in 2gb phone memory which doesnt have enough space.
OCLF requires 1.2gb of space on it to work.
You can do what I did which was to titanium backup everything, reset to factory (frees up your phone memory), do OCLF/voodoo and then restore your backup.
Voodoo works better than OCLF but there's no permanent way of uninstalling it other than reflashing it. Got sick of waiting for Froyo and did it anyway.
KaliKot said:
Its your internal built in 2gb phone memory which doesnt have enough space.
OCLF requires 1.2gb of space on it to work.
You can do what I did which was to titanium backup everything, reset to factory (frees up your phone memory), do OCLF/voodoo and then restore your backup.
Voodoo works better than OCLF but there's no permanent way of uninstalling it other than reflashing it. Got sick of waiting for Froyo and did it anyway.
Click to expand...
Click to collapse
So in order to do Voodoo i HAVE to reset factory ?
I don't have ODIN do I have to reflash ?
jaju123 said:
Use voodoo lag fix
Click to expand...
Click to collapse
I don't have or know how to use ODIN yet -- im still kinda new
Also, I don't have the 3 button recover/download mode -- (i can't get KIES to upgrade my firmware for the life of me) -- so flashing/reflashing isn't the best option for me
I was hoping for like an App like Ryan's was out there
I guess not. So there's only Ryan's and Voodoo ?
Funkadelick said:
So in order to do Voodoo i HAVE to reset factory ?
I don't have ODIN do I have to reflash ?
Click to expand...
Click to collapse
You dont have to reflash. You need to have 3 button recovery mode though and it will apply the lagfix on boot.
You'll only have to reflash if you want to completely remove voodoo from your phone instead of just disabling it.
A word of warning though. I had the same encounter earlier when OCLF couldnt lagfix my phone because of the disk space. I did voodoo and it worked but then my phone only had like 20mb left.
Its best to reset to factory, apply either lagfix and then restore your apps with Titanium Backup
I had the same issue on JPK initially because OCLF 2.1.0 wasnt able to write to the system folder. It had prepared the files to move but failed at that point.
I assume yours is the same.
I did this to fix it:
open terminal emulator on phone and type:
su
busybox mount -o remount,rw /system
I manually deleted the file "linux.ex2" in folder /data/ext2 to free up the space...
After that rerun the lag fix, works fine
And you couldnt post this problem in one click lag fix topic why? Just wondering what compels everyone to make a dump out of this forum.
This is ridiculous...
You guys really need to calm down with this "new topic" button"
Funkadelick,
This thread has nothing to do with development and does not belong in that section. This topic has also been covered in other threads as mentioned above, and therefore really should not have been posted in the first place.
Before posting any more threads, go read the "please read before posting" thread at the top of the forum section as all of these subjects are addressed there along with other important ones as well.
Thread closed.
So now that I lured you in with my snazzy thread title I will hit you with the boring stuff. Im just lost on all the ROM Flash OCLF Kernel Lingo. I want to go to Froyo and currently have 2.1 with Voodoo. There doesnt seem to be any SOLID thread that gives you simple instructions on what it does, how to do it, etc.
I read somewhere that if you have the Voodoo on the phone currently you have to flash back to the stock ROM. Other thread dont really touch on if you have to flash back or if you just do the upgrade.
Second, what is going to be lost in the process. Again I see some thread that say you have to do a Master Delete that will erase everything on the phone then some are not clear if you have to erase everything. If you do have to wipe it clean what are you guys using the back up all your apps? I did a backup with ROM Manager last night as well as a App Backup with Astro. But where do the backed up files go? Is it smart enough to drop them on the external SD card?
I hate to post such a general question but I am just getting overwhelmed reading 6 million different threads about different versions that do different things.
Disable voodoo by creating a folder in the voodoo directory "disable-lagfix" (without quotes), reboot (this will take a while). When that is fine download Titanium Backup and use that to backup all your apps + data. Copy the Titanium Backup folder to your external sd card. Backup all the data you want on your internal sd card. Flash back to stock and do a master clear (enable usb debugging first), root and install RM/CWM, copy over the rom you want to flash to the internal sd card (DO NOT RENAME). Power off the phone remove your sim card and sd card. Boot into CWM and flash your rom.
ps. Make sure your battery is fully charged.
Let me know if I missed anything. Swyping this before bio class.
Edit: Do NOT restore system data
Sent from my Captivate
curti.nogg said:
Disable voodoo by creating a folder in the voodoo directory "disable-lagfix" (without quotes), reboot (this will take a while). When that is fine download Titanium Backup and use that to backup all your apps + data. Copy the Titanium Backup folder to your external sd card. Backup all the data you want on your internal sd card. Flash back to stock and do a master clear (enable usb debugging first), root and install RM/CWM, copy over the rom you want to flash to the internal sd card (DO NOT RENAME). Power off the phone remove your sim card and sd card. Boot into CWM and flash your rom.
ps. Make sure your battery is fully charged.
Let me know if I missed anything. Swyping this before bio class.
Edit: Do NOT restore system data
Sent from my Captivate
Click to expand...
Click to collapse
Thanks a ton! Thats exactly what I needed to get it all straight.
curti.nogg said:
Disable voodoo by creating a folder in the voodoo directory "disable-lagfix" (without quotes), reboot (this will take a while). When that is fine download Titanium Backup and use that to backup all your apps + data. Copy the Titanium Backup folder to your external sd card. Backup all the data you want on your internal sd card. Flash back to stock and do a master clear (enable usb debugging first), root and install RM/CWM, copy over the rom you want to flash to the internal sd card (DO NOT RENAME). Power off the phone remove your sim card and sd card. Boot into CWM and flash your rom.
ps. Make sure your battery is fully charged.
Let me know if I missed anything. Swyping this before bio class.
Edit: Do NOT restore system data
Sent from my Captivate
Click to expand...
Click to collapse
What he said. Also if you are new to flashing I would advise looking into the cognition thread. It is definitely the easiest and most user friendly rom. And actually if you are coming from 2.1 all you should need to do is disable the lagfix by above named method, and one click to stock using odin. Also can be found in cognition thread somewhere. Then flash. I have never had to do a master clear. And have never had even a minor problem with either odin flashes or CWM. This just would save a little time but by all means if you wanna stay safe as can be do a master clear.
Thanks. I got the Cognition rom loaded up and is working well. Although It is missing swype which I miss.
sstrawsb said:
Thanks. I got the Cognition rom loaded up and is working well. Although It is missing swype which I miss.
Click to expand...
Click to collapse
Huh? All my Cognition versions had swype.
Swyping....read at your own risk
I second that, I have always had swype as well. I know this sounds obvious and I am sure you have already tried this but cog sets the default as android keyboard try switching the input by long pressing the input box.
Sent from my GT-I9000 using XDA App
Might have to go into settings, locale and text and enable it. Not sure, never used it, but I have to do that for smart keyboard. It's a thought.
Ok, I have Eclair and VooDoo on it. Now I want to make my phone as new, as from the box. I dont mind to have VooDoo just disabled but I want to format my mass memory. How do I do that because it will probably delete "disable lagfix" folder ? I dont want to flash with Odin or anything else since I dont have a clue how to work with that. Can I flash fresh Eclair trough Kies so VooDoo is deleted and I have phone just like when I bought it ? Or I can do right click and Format in windows, VooDoo does not have any connection with it ?
So, basically, I want to bring my phone in "out of the box" state, Im on Eclair and I have VooDoo lagfix installed and disabled with "disable lagfix" folder, thats it.
Tnx a lot !
No one ??? Am I the only one that wants to do this sometime ?
damirbusic said:
Ok, I have Eclair and VooDoo on it. Now I want to make my phone as new, as from the box. I dont mind to have VooDoo just disabled but I want to format my mass memory. How do I do that because it will probably delete "disable lagfix" folder ? I dont want to flash with Odin or anything else since I dont have a clue how to work with that. Can I flash fresh Eclair trough Kies so VooDoo is deleted and I have phone just like when I bought it ? Or I can do right click and Format in windows, VooDoo does not have any connection with it ?
So, basically, I want to bring my phone in "out of the box" state, Im on Eclair and I have VooDoo lagfix installed and disabled with "disable lagfix" folder, thats it.
Tnx a lot !
Click to expand...
Click to collapse
when you format the internal mass storage, yes, "voodoo" folder will disappear too.
but when you reboot the phone, the kernel will detect that voodoo folder is missing, and it will once again, implement voodoo, and your phone will still have voodoo, and you will see the voodoo folder after the reboot.
Because Voodoo implemented at the kernel level, if you want to remove voodoo totally, the only way is to flash new kernel after disable lagfix.
on top of that, i believe voodoo didn't touch internal storage (except creating voodoo folder as a indicator or flag, and allow you to disable voodoo by adding a disable lagfix folder).
so it's safe to do format of your internal storage even if with voodoo installed.
hope the info helps.
most of the owner moved to froyo, which makes eclair related thread has lesser response
Tnx a lot, that helps, I have formatted mass memory and then Ive made Voodoo/disable lagfix folder and now it is ok, I can flash Froyo when it finally arrives in Croatia.
Thanks !