Related
This will most definitely wipe all previous remnants of data, including any unlock codes that you may have on your phone!​
Update 10/11/10: This is now a confirmed fix for phones with larger NAND chips;
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. Once done and phone has rebooted, root your phone & install Rom Manager.
14. Download & Install Bionix 1.7 with OCUV Voodoo
Click to expand...
Click to collapse
NOTE: The bootup sound HAS changed.. But if you hear Linda go through the process of changing the format then you can now run voodoo..
(Or if you don't know & you arent for sure, just download Quadrant & if your score is 1500+ voodoo is enabled.)
If you would like to know if you have a larger NAND chip, please follow This guide.
Credits: sombionix | SkOrPn | Masterâ„¢ | JAC
If I forgot anyone in that list, I apologize. Please just PM me so I can add you to the list.
i think my vibrant has the larger nand chip, any way to make sure before i go through the steps above? using terminal on the phone would be best, it's just mount right? not sure what to look for after that
Supercurio has already supplied JAC with the fix for the larger NANDS (I asked him). JAC just has to make a new kernel with it included.
BUT, JI6 is so fast that I don't think that it even needs a lag fix. I've been running it for a couple days with not one hiccup. Don't know what Samsung did but it worked.
kangxi said:
Supercurio has already supplied JAC with the fix for the larger NANDS (I asked him). JAC just has to make a new kernel with it included.
BUT, JI6 is so fast that I don't think that it even needs a lag fix. I've been running it for a couple days with not one hiccup. Don't know what Samsung did but it worked.
Click to expand...
Click to collapse
Yeah I know, But until he makes it we can test this for a temp fix
Ok well, I DO have a larger NAND which is why I've been trying to follow the Beta5 development. Can you explain what doing all of this actually does and why it works?
kangxi said:
Ok well, I DOCan you explain what doing all of this actually does and why it works?
Click to expand...
Click to collapse
We have no clue.. But we both have done this & for some reason voodoo works on both of our devices now
kangxi said:
Ok well, I DO have a larger NAND which is why I've been trying to follow the Beta5 development. Can you explain what doing all of this actually does and why it works?
Click to expand...
Click to collapse
I have been using voodoo for several weeks now. I kept getting the dreaded "this model is not supported" error when trying to apply voodoo kernels. I tried literally dozens of times if not more, I was on the verge of quiting but sombionix told me to try flashing to the froyo rom that does not brick, and then to the stock rom. I immediately rooted, installed Rom Manager and Clockwork recovery, and then flashed bionix 1.4 rom (might have been bionix 1.3 at first, but 1.4, 1.6 and 1.7 have all worked since) containing JAC's v1.1 OC/UV/Voodoo kernel with Voodoo beta4.
Voodoo has worked flawlessly ever since... My NAND is the larger 416MB NAND. Go figure....
All we are asking of you guys is to have a little faith and try this procedure. If it works, then you get voodoo bliss, and if it don't then we are back where we started. You have nothing to lose but a hour or less of your time. Give it a try and report back here please. Good luck...
SkOrPn said:
I have been using voodoo for several weeks now. I kept getting the dreaded "this model is not supported" error when trying to apply voodoo kernels. I tried literally dozens of times if not more, I was on the verge of quiting but sombionix told me to try flashing to the froyo rom that does not brick, and then to the stock rom. I immediately rooted, installed Rom Manager and Clockwork recovery, and then flashed bionix 1.4 rom (might have been bionix 1.3 at first, but 1.4, 1.6 and 1.7 have all worked since) containing JAC's v1.1 OC/UV/Voodoo kernel with Voodoo beta4.
Voodoo has worked flawlessly ever since... My NAND is the larger 416MB NAND. Go figure....
All we are asking of you guys is to have a little faith and try this procedure. If it works, then you get voodoo bliss, and if it don't then we are back where we started. You have nothing to lose but a hour or less of your time. Give it a try and report back here please. Good luck...
Click to expand...
Click to collapse
+1
He didn't even tell me, lol
It'd be nice to see Bionix v1.8 come with Voodoo Beta5 since they're both so close at hand so we don't have to go through this crazy business. Good work and great find, though!
I followed this method and it allowed me to use the Voodoo Lag Fix. I was never able to get it to work before, would never hear the boot up sequence telling me my file system was being converted etc. After flashing Eugenes Froyo rom and flashing back due to stability issues I tried Bionix 1.5 and was able to flash the voodoo kernel. I checked before when it wouldn't work for me and found that I too also have the larger NAND chip. I upgraded to Bionox 1.6 just fine, not sure why it worked but Its been wonderful these past 2 weeks.
I second ji6 is impressive.
Sent from my SGH-T959 using XDA App
vdubgti08 said:
I followed this method and it allowed me to use the Voodoo Lag Fix. I was never able to get it to work before, would never hear the boot up sequence telling me my file system was being converted etc. After flashing Eugenes Froyo rom and flashing back due to stability issues I tried Bionix 1.5 and was able to flash the voodoo kernel. I checked before when it wouldn't work for me and found that I too also have the larger NAND chip. I upgraded to Bionox 1.6 just fine, not sure why it worked but Its been wonderful these past 2 weeks.
Click to expand...
Click to collapse
Yeah Voodoo beta5 was never needed, so a whole lot of people waited for nothing. LOL
So i searched the forums and didnt find a definate answer, maybe i didnt search the correct terms or something, idk. My question is, if you have a larger nand and voodoo DOESNT install, do you still need to run "disable-lagfix" when flashing a backup or another rom?
2sh0rt said:
So i searched the forums and didnt find a definate answer, maybe i didnt search the correct terms or something, idk. My question is, if you have a larger nand and voodoo DOESNT install, do you still need to run "disable-lagfix" when flashing a backup or another rom?
Click to expand...
Click to collapse
No i do not believe so, BUT, I would still put that file into the voodoo folder anyway. There is no harm in doing so. When you get the other rom installed and setup how you like, then you can remove it. Voodoo can be enabled and disabled at will simply by removing/replacing the "disable-lagfix" file into the voodoo folder. Its just as easy as that really...
Hope that helps.
I Really think you don't need to since your file system is still rfs,
how do you totally remove voodoo? if i flash back to the last backup i have BEFORE installing bio1.7 voodoo will voodoo still be there or will it be gone?
I think you would need to put the disable-lagfix file/folder in the voodoo folder. Then reboot wait until it's done, then flash a kernal that isn't voodoo.After that then restore your back up. For some reason, I thought my back up was fine, but when I take the disable-lagfix file out, it would reinstall voodoo again when I boot. It might just be me, but I don't think nandroid back-ups restore the kernal. I could be wrong...
Daddy_617 said:
I think you would need to put the disable-lagfix file/folder in the voodoo folder. Then reboot wait until it's done then flash a kernal that isn't voodoo then restore your back up. For some reason before I thought my back up was fine and when I take the disable-lagfix file out it would reinstall it again when I boot. It might just be me but I don't think nandroi back ups restore the kernal. I could be wrong...
Click to expand...
Click to collapse
+1
Yes you need to put that disable-lagfix file into the voodoo folder on the sdcard. Reboot, it will tell you voodoo is being disabled/transformed back into rfs, once finished you can then proceed with your normal flashing routine.
Linda's beautiful voice!!!
I'm a long time lurker, but I've never had anything constructive to say so I've silently read, and slowly learned how to make my phone more awesome. I'm happy to say that I followed these directions exactly and voodoo finally enabled. What a great find! Thanks!
Orwell83 said:
I'm a long time lurker, but I've never had anything constructive to say so I've silently read, and slowly learned how to make my phone more awesome. I'm happy to say that I followed these directions exactly and voodoo finally enabled. What a great find! Thanks!
Click to expand...
Click to collapse
Glad to hear another happy voodoo user, and yet more proof that beta4 works on all vibrants including larger nand variants.
Your welcome Orwell
After hearing terrible horror stories of people following the proper instructions on how to remove the lagfix, I thought I'd ask some questions that might help many [inquiring] people as well as myself.
1.) If you have Voodoo installed, I assume that it's okay to install the current ROMs on xda (i.e. jt's superclean, frost's, blue breeze) because those ROMs flash /system and voodoo affects /data, correct?
2.) When flashing a ROM, it is recommended that you wipe data / cache to prevent any issues from occurring. The only issue with this is that you can't wipe data (from CWM) with Voodoo installed, correct?
3.) If the above answer is correct, then is there a more efficient way of wiping data WITHOUT having to disable lagfix (which seems to be causing problems for those who are even following the appropriate directions). For example, would clearing the delvik cache be a sufficient replacement for wiping data/cache to satisfy the recommendation when flashing a current ROM?
Thanks in advance.
Hey there, I saw you had a bunch of views but no responses yet, so I thought I'd chime in, I'm not new to android or flashing roms, but this voodoo kinda freaked me out as well hearing all the horror stories. I still do not completely understand voodoo myself, but I can tell you from my expereinces, I have flashed a few themes and roms with Dirrks kernel with voodoo, and aside from the usual of taking your time and following the directions...
I use Root Explorer and create a "disable_lagfix" file inside the voodoo folder, and let everything run its course...i.e. when installing the kernel, it takes a long time and the screen does go black for part of it, but let it all play out and don't touch the phone, pull the battery, ect. and it does even take longer to remove voodoo once you put the "remove_lagfix" file and reboot.
I'd say it was a good 10 min. on the samsung screen before anything came back up and running, but I resisted freaking out and let everything boot up properly, and I have had zero problems with it.
It does take twice as long to load roms or themes becasue I always have preferred wiping all data and cache when installing new roms and creating a nandroid, just have had better luck in the past by doing that, so by disabling voodoo, leting it boot back up, doing the clockwork thing, then having to re-enable voodoo is a pita, but in my experiences its been no issue and i've never run into any issues so far. (fingers crossed now becasue of that statement)
Hope it helps you a little bit.
Nice post. Solid advice. Patience is key as is doing it the right way
Sent from my 1.2Ghz voodoo fascinate
starscream84 said:
Hey there, I saw you had a bunch of views but no responses yet, so I thought I'd chime in, I'm not new to android or flashing roms, but this voodoo kinda freaked me out as well hearing all the horror stories. I still do not completely understand voodoo myself, but I can tell you from my expereinces, I have flashed a few themes and roms with Dirrks kernel with voodoo, and aside from the usual of taking your time and following the directions...
I use Root Explorer and create a "disable_lagfix" file inside the voodoo folder, and let everything run its course...i.e. when installing the kernel, it takes a long time and the screen does go black for part of it, but let it all play out and don't touch the phone, pull the battery, ect. and it does even take longer to remove voodoo once you put the "remove_lagfix" file and reboot.
I'd say it was a good 10 min. on the samsung screen before anything came back up and running, but I resisted freaking out and let everything boot up properly, and I have had zero problems with it.
It does take twice as long to load roms or themes becasue I always have preferred wiping all data and cache when installing new roms and creating a nandroid, just have had better luck in the past by doing that, so by disabling voodoo, leting it boot back up, doing the clockwork thing, then having to re-enable voodoo is a pita, but in my experiences its been no issue and i've never run into any issues so far. (fingers crossed now becasue of that statement)
Hope it helps you a little bit.
Click to expand...
Click to collapse
Thanks for the advice, I'll keep it in mind. Now that theres a Voodoo Toggle things should be a bit easier
This is more of a general response to the idea of voodoo "horror stories" than your specific questions but I have installed/disabled voodoo many times to try different kernel variations/install new roms and I have never run into a problem. I'd have to think 90% of the horror stories can be traced to user error.
I'm not trying to be a **** or anything, this stuff can be confusing and I've made mistakes in the past as I'm sure everyone has.
All I'm saying is that if you're careful, patient and always follow instructions (and for me, I ALWAYS wipe data/cache before installing anything) I think voodoo and you (or any kernel/rom, for that matter) can have a wonderful relationship.
Sent from my 1.2ghz VooDoo Fascinate
It will also only take one good f-up, followed by seven hours of fixing it to learn what not to do if you don't feel like reading first.
Sent from my SCH-I500 using XDA App
throwing the phone into downloading will still wipe everything right?
starscream84 said:
Hey there, I saw you had a bunch of views but no responses yet, so I thought I'd chime in, I'm not new to android or flashing roms, but this voodoo kinda freaked me out as well hearing all the horror stories. I still do not completely understand voodoo myself, but I can tell you from my expereinces, I have flashed a few themes and roms with Dirrks kernel with voodoo, and aside from the usual of taking your time and following the directions...
I use Root Explorer and create a "disable_lagfix" file inside the voodoo folder, and let everything run its course...i.e. when installing the kernel, it takes a long time and the screen does go black for part of it, but let it all play out and don't touch the phone, pull the battery, ect. and it does even take longer to remove voodoo once you put the "remove_lagfix" file and reboot.
I'd say it was a good 10 min. on the samsung screen before anything came back up and running, but I resisted freaking out and let everything boot up properly, and I have had zero problems with it.
It does take twice as long to load roms or themes becasue I always have preferred wiping all data and cache when installing new roms and creating a nandroid, just have had better luck in the past by doing that, so by disabling voodoo, leting it boot back up, doing the clockwork thing, then having to re-enable voodoo is a pita, but in my experiences its been no issue and i've never run into any issues so far. (fingers crossed now becasue of that statement)
Hope it helps you a little bit.
Click to expand...
Click to collapse
just so im clear on this, based on what you're saying:
if i have voodoo (using jt's kernel) and want to install a rom I would disable_voodoo, let that take its course, install rom, reinstall voodoo?
dopepope said:
just so im clear on this, based on what you're saying:
if i have voodoo (using jt's kernel) and want to install a rom I would disable_voodoo, let that take its course, install rom, reinstall voodoo?
Click to expand...
Click to collapse
If all you were doing was installing the rom, you wouldn't have to disable voodoo first UNLESS the rom you were installing included a kernel and it was non-voodoo. If you wanted to make a backup, then you may need to disable voodoo first. If you're upgrading the kernel from voodoo to another voodoo kernel, you also wouldn't have to disable it before hand.
My accelerometer just stopped working. It was fine and when I went to youtube, I realized that it would not switch back to portrait from landscape, and now it's not working at all! Not in apps, not at home screen, no where... My image gallery doesn't even do the tilt animations.
The situation
-Rooted
-1200 OC Voodoo lagfix with bootanimation
-LauncherPro
I have checked to make sure orientation change was enabled in both settings and preferences... Ugh, yet something else I've seem to have broken.
I have also tried flashing other variations of Voodoo. ARG!!!
I've noticed the exact same issue. Is that Dirrk's OC kernel? If so, I have the same setup you have listed. I'm also having calendar issues with both jt's clean rom and bubby's magic rom. I'm trying a restore from a couple of days ago but I'll probably end up going back to complete stock and starting over. Isn't experimentation fun?
kupdegrove said:
I've noticed the exact same issue. Is that Dirrk's OC kernel? If so, I have the same setup you have listed. I'm also having calendar issues with both jt's clean rom and bubby's magic rom. I'm trying a restore from a couple of days ago but I'll probably end up going back to complete stock and starting over. Isn't experimentation fun?
Click to expand...
Click to collapse
I was thinking that too, but I don't want too! Experimentation for the win!
I did a restore from like 2 days ago and still my accelerometer was not working. I read in one of the Vibrant threads about other people with this problem, and they said only a stock restore fixed their problems... sigh.
What files do I have to flash with Odin to be completely Stock? I read several threads that said I needed only one and others that said 3.
OK, for anyone having the same problems I was having, I managed to fix mine and hopefully it will work for you.
All I did was remove Voodoo via the Uninstaller. I did not do it manually and I did lose all my data and root, but getting root back is cake. You do not have to go back to stock entirely, but yeah, you kinda do. CWM was still there I was able to just flash Voodoo right back on LOL!
****, I forgot to backup with Nandroid, again!!! Oh well.
Any "known good" fixes or causes yet?
Hey guys, new to rooting and mods on phones. i have a samsung fascinate that i rooted on saturday. installed rom manager, root explorer, clockwork and ti backup. the problem i am having is that when i attempt to flash the super clean rom from jt1134, by using the rom manager. it keeps giving me a few different error messages. on is E: failed to verify whole-file signature and E:Signature verification Failed. Through my research i tried dl'ing the zip form to the sd card, and similar messages came up. please help. Thanks
Can I make a recommendation? Dont instal any roms as of now. None are true custom roms. All still have the touchwiz running. None of the roms run bug free and all see Force Close errors!!
Your better off...just rooting, Install lagfix from market, and use launcherpro.
Ive tried the custom roms and honestly not worth it till froyo comes.
stupid question but what exactly does lagfix do?
Ok ive noticed it fixes how slow the market reacts when opened, also speeds up when page loads somewhat.....if you use the LagFix in the market it has a option in the app to remove it if you dont like it , but im sure you will. Stay away from Voodoo LagFix it can be tricky.
Download oclf from market
give it root access
choose to install EXT2 Tools
Then go back and install Lag Fix V1+
This is the only lag fix i know of that be removed by the app itself no outside programs.
Trust me the roms that are out you wont notice anything special from them. all they do is remove apps!!! Wait till cyanogen releases his rom for Fascinate. He makes the best Roms period!!! And he just made a beta for the galaxy lineup....but the fascinate will not see any true roms untill froyo is released!!!
whats the eta on froyo? seems like it keeps getting pushed back.
the cyanogen rom was the entire reason i wanted to test it on the fascinate(i didn't know it wasn't available yet). i had a buddy with it and it seemed to be a super powerful rom.
thanks for all the info martyotaku
From the looks of it.... not till January! Was supposed to be this month. Who knows might still happen.
Honestly if I'm you if your in your 30 days return it and wait for something else. Samsung is known for horrible support.
It sounds like you haven't actually installed CWM... Did you just try to flash it via ROM Manager? Because that won't work. You actually have to flash it using Odin. Once you have CWM successfully installed, you can flash ROMS, kernals, etc...
And I would stay away from the OCLF. A lot of people have been having problems with it, just like VooDoo. Once I uninstalled it, I noticed significant battery life increase. All the lag fix really does is artificially inflate quadrant scores, which don't really count for much anyways.
I've been running JT's Super Clean ROM and I can easily go 48 hours without a charge... No where near that on the stock ROM
just bought cwm from the market and installed.
which i didnt do before. i assumed when i dl rom manager and did that recovery it was already installed.
went to see how super clean acted and tried to redo the flash. still gave me the same two error messages.
Again, you have to flash CWM through Odin, you can't just install it and it magically work
gotcha. ill research how to use the odin ect.... thanks kevin
No problem!
Here's the thread on how to do it
And I cannot stress this enough...
NEVER, EVER, EVER USE THE "PHONE" BUTTON IN ODIN!!!
ALWAYS, ALWAYS, ALWAYS USE THE "PDA" BUTTON.
You will have an expensive paper weight if you use the "phone" button.
Don't do it.
Well if that happens... I'm going straight to verizon and opsse sorry I dropped it in a lake... Haha
Sent from my SCH-I500 using XDA App
figured odin out... got it installed and did a back up... completely different process.. looks like it has worked. phone is rebooting right now. and ... its stuck on vz symbol for a few min... bammm...very nice!! recommendations from here... sweet themes maybe???
Cant wait to see how it goes from here on out... Thanks so MUCH Kevin. is there any way to give props on this website?
Not that I know of, other than the way you just did!
Glad you got it working.
I'm using JT's Super Clean ROM from ROM Manager with the Dark Gloss theme
i so far like the set up of revolutions v3 w/ circle battery. here in a few i am going to switch to dark gloss mod w/ slide animations...
So I am running the latest voodoo infused Superclean 2.1 and I found out something that saves a ton of time.
Say you downloaded a .zip file you need to flash in cwr. Before you had to create the disable folder/file, reboot, wait for it to convert back, reboot, flash zip file, remove disable file, reboot..wait for it to enable...
Now I find I can reboot, choose disable voodoo in the new cwr menu, go to zip file and flash it, then immediately toggle voovoo back to enabled, then reboot. No reboots in-between .....
I thought maybe it was a placebo and that voodoo wasn't actually reenabled, but after it booted I ran Linpack and Quadrant and my scores were obviously voodoo enabled scores....
So is it too good to be true?
you are referring to the original voodoo....... I believe the new voodoo source is voodoo 5.
jamesnmandy said:
So I am running the latest voodoo infused Superclean 2.1 and I found out something that saves a ton of time.
Say you downloaded a .zip file you need to flash in cwr. Before you had to create the disable folder/file, reboot, wait for it to convert back, reboot, flash zip file, remove disable file, reboot..wait for it to enable...
Now I find I can reboot, choose disable voodoo in the new cwr menu, go to zip file and flash it, then immediately toggle voovoo back to enabled, then reboot. No reboots in-between .....
I thought maybe it was a placebo and that voodoo wasn't actually reenabled, but after it booted I ran Linpack and Quadrant and my scores were obviously voodoo enabled scores....
So is it too good to be true?
Click to expand...
Click to collapse
Yes this had been around for some time now to make it easyer so yeah
First, you don't need to disable voodoo to flash 99% of stuff.
Second, disabling voodoo in the menu just creates the disable_voodoo file for you. you'd still have to reboot for it to disable (and wait through the conversion process) for it to be actually disabled. it's even on the screen. "voodoo actually: enabled"
so when you toggle it off, flash, and back on without rebooting, you aren't disabling it at all.
Really? You didn't know that? Voodoo 5 has been out for MONTHS now. This thread should be moved.
There hasnt been the need to disable voodoo to flash most things for months....since we have had voodoo recovery around Thanksgiving....not exactly a new revelation
You guys might be missing a couple points. This is the voodoo that comes packaged in Superclean2.1 EB01 that Adrenalyne just recently released. So no its not the old voodoo.
Another point someone made was 99% of things don't need voodoo disabled. A couple nights ago after installing SC2.1 I tried to install two different zip files. Both times I got an error. Error at Line 2 or Erie at line 4. IRC member said disable voodoo. So I did and all of a sudden they install fine. Ok. But then I see the voodoo toggle in CWR and I try it without revolting in-between and it works.
Maybe I'm not explaining this well.
jamesnmandy said:
You guys might be missing a couple points. This is the voodoo that comes packaged in Superclean2.1 EB01 that Adrenalyne just recently released. So no its not the old voodoo.
Another point someone made was 99% of things don't need voodoo disabled. A couple nights ago after installing SC2.1 I tried to install two different zip files. Both times I got an error. Error at Line 2 or Erie at line 4. IRC member said disable voodoo. So I did and all of a sudden they install fine. Ok. But then I see the voodoo toggle in CWR and I try it without revolting in-between and it works.
Maybe I'm not explaining this well.
Click to expand...
Click to collapse
voodoo5 is voodoo5...theres nothing new in terms of what we can do in recovery with the voodoo options that we couldnt do 2 months ago
ive flashed a ton of stuff in the last few days with voodoo enabled and had no issue or reason to disable/renable in cwr
Well voodoo 5 is new to me. I went from DH12 stock to EB01 Voodoo. Guess its just me learnin'
When jt first released voodoo for eb01 he didn't have cwm fixed yet. About 30 minutes later he released another eb01-voodoo.zip that was 5mb bigger (13mb) because it included a working cwm. Since then I have flashed and restored many times without error or disabling. SC2.1 voodoo includes voodoo5 and working cwm in the zip. If you're still getting an error in red cwm then maybe something is borked and you should start over. Hope this helps.
And all questions should be posted in general. You'll likely get plenty of responses there as well.
Sent from my SCH-I500 using XDA App
Just to clarify, the ONLY time you ever need to disable the lag fix after enabling it is if you intend to flash a non-Voodoo kernel of any kind. That's because a non-Voodoo kernel is incapable of reading the ext4 filesystem and will freak out when trying to boot. As long as you use the red CWM (which is compatible with ext4; green CWM, like non-Voodoo kernels is not), then you can do nandroid backups/restores and flash roms, themes, and other Voodoo kernels as much as you want without having to worry about disabling the lag fix.
Oh, and disabling and then enabling the lag fix from the CWM menus without rebooting does absolutely nothing, because it has to reboot in between to run the scripts that actually enable or disable the lag fix (this is when you hear the female robotic voice).
Posted from my EB01 SuperClean Fascinate with Voodoo
I've just switched to superclean 2.2 with voodoo, and it's my first time using it. I'm enjoying it so far, but I've already made the noob mistake of using rom manager to boot into recovery. Luckily it was only a boot animation, so the flash failed and no damage was done. Just have to get used to manually booting into red cwr.
But it's really good to know I can flash roms without disabling as long as I use red cwr. Didn't see a clear answer to that before. And I can flash other voodoo kernels as well without disabling? Say, for example, kaosinate rom and kernel? Been wanting to try that and jt's vanilla
Sent from my SCH-I500 using XDA App
Not sure about jt's, but kaos's kernel is a Voodoo kernel, so yes, you wouldn't need to disable the lag fix before flashing it.
Posted from my EB01 SuperClean Fascinate with Voodoo
ivorycruncher said:
Not sure about jt's, but kaos's kernel is a Voodoo kernel, so yes, you wouldn't need to disable the lag fix before flashing it.
Posted from my EB01 SuperClean Fascinate with Voodoo
Click to expand...
Click to collapse
Yeah, jt has a voodoo kernel for his vanilla froyo. Great to know, ivory, thanks
Sent from my SCH-I500 using XDA App
jamesnmandy said:
You guys might be missing a couple points. This is the voodoo that comes packaged in Superclean2.1 EB01 that Adrenalyne just recently released. So no its not the old voodoo.
Another point someone made was 99% of things don't need voodoo disabled. A couple nights ago after installing SC2.1 I tried to install two different zip files. Both times I got an error. Error at Line 2 or Erie at line 4. IRC member said disable voodoo. So I did and all of a sudden they install fine. Ok. But then I see the voodoo toggle in CWR and I try it without revolting in-between and it works.
Maybe I'm not explaining this well.
Click to expand...
Click to collapse
I suggest you stop using voodoo since you clearly know nothing about how it works. As started by someone else, the only time you need to disable voodoo is when flashing a non voodoo kernel. The errors that you got are clearly install script errors. NOT because you're voodoo'd. So you and the person you got advice from know nothing about how voodoo works so I suggest you save yourself the trouble and stop using it.
Sent from my SCH-I500 using XDA App
I am not sure what is ment by"other" voodoo kernels. I thought voodoo 5 itself was the kernel. Now from reading these posts I have lost some understanding of voodoo. If there are other voodoo kernels, are those others voodoo 5 based? What normal kernel is the stock voodoo 5 based on?
Rocking dj05 and jt's voodoo 5