I think my phone may be bricked when I turn it on all I get is the samsung title and it does nothing else. I had just recently updated it with the voodoo with lag fix from rom manager and then this morning flashed it with one of the super fast kernals and that is when it rebooted and never advanced past the samsung logo.
I tried to get the stock .tar form drop box but keep getting a 404 error and I am unable to get that or follow the link to remove the voodoo, that link just goes to just a jumble of symbols with nothing to download. Again sorry if this is covered somewhere else in here but I have looked and tried to fix this but not even the cw recovery works. Oh in case you can't tell I am a newb .
You can't flash non voodoo over voodoo. I'm sure someone will chime in shortly. I don't know how to fix it. Sorry
Sent from my SCH-I500 using XDA App
Odin to stock. You aren't bricked. Keep trying to download the tar file
Sent from my sch-i500 using dl09 supah clean
I believe you will have to completely reset your phone to stock with stock kernel/rom etc and you will lose all your data. It will essentially be a new phone again. It will work though.
You can flash non voodoo over voodoo as voodoo uses a different filesystem that is not 'seeable' by non voodoo kernels.
Cali3350 said:
You can flash non voodoo over voodoo as voodoo uses a different filesystem that is not 'seeable' by non voodoo kernels.
Click to expand...
Click to collapse
Note: Cali3350 meant to write shouldn't instead of can.
I would start here:
http://forum.xda-developers.com/showthread.php?t=804784
Ok I click on the first link and the page just brings up gibberish, like I said I am a newb so don't flame me too bad please, what am I supposed to do with that first link?
Don't click the link. Right-click, save as.
I am unfortunately unclear on the finer points of recovering from a voodoo misadventure, but that first link is intended for voodoo4 and perhaps catastrophic circumstance. I believe you would have voodoo5 if you installed recently via RM, but someone should correct me if I am wrong.
I haven't ever needed voodoo, so I have yet to go down any of these roads. However, if I were in your situation, I would try to clear the lagfix with red cwm first and leave my MBR alone until I was convinced I had to overwrite it. Once you are back to an RFS file system, put on a nonvoodoo file system that matches your base band and/or odin to stock as needed.
In any case, you are embarking on quite a crash course.
You should just be able to flash another voodoo kernel, then all will be fine. If you decide to flash a non voodoo kernel after that, disable the voodoo within red CWM, reboot to let the file system revert, then flash your new kernel
Thanks Kevin that worked just fine, I had to use a different sd card because somehow I write protected the one that came with the phone. It now boots up fine but I need to download everything again . But now I cannot access the market, press the icon and if flashes and then nothing.
Related
i need help...my vibrant is sitting at a blk screen after odining the stock jfd.tar . i had had voodoo lagfix and a market lagfix on there earlier and i dnt think i took it off correctly bcuz i was late to class but shouldnt odin take care of thatif i selected repartition and the stock jfd.tar file?...could it be that its still setup as EXT4 and not rfs like it should be when its stock? now i JUST noticed that it will only boot completely if i load a custom rom despite using odin to revert to stock. what happens is that it boots to the tmobile pink square but no sound, when the galaxy S screen comes on, then the tmo sound comes on (late), then the screen goes blk w/ the touch buttons lit. in order for it to boot i have to flash the root update in clockwork, reboot, then flash a ROM, reboot....have i done somethin wrong? why wont it boot when i odin it?
you need to disable the voodoo fix before you do anything, because its like you said, it still assumes its ext4. In odin its trying to flash its looking for rfs partition. If its too late to disable voodoo, you may want to try flashing one of the 2.2 ROMs through Odin, those seem to fix all bricks (non JTAG bricks that is), and brings phones back to life. If you use a 2.2 i recommend Eugenes very first one where you don't have to mess with kernels and such
boimarc89 said:
i need help...my vibrant is sitting at a blk screen after odining the stock jfd.tar . i had had voodoo lagfix and a market lagfix on there earlier and i dnt think i took it off correctly bcuz i was late to class but shouldnt odin take care of thatif i selected repartition and the stock jfd.tar file?...could it be that its still setup as EXT4 and not rfs like it should be when its stock? now i JUST noticed that it will only boot completely if i load a custom rom despite using odin to revert to stock. what happens is that it boots to the tmobile pink square but no sound, when the galaxy S screen comes on, then the tmo sound comes on (late), then the screen goes blk w/ the touch buttons lit. in order for it to boot i have to flash the root update in clockwork, reboot, then flash a ROM, reboot....have i done somethin wrong? why wont it boot when i odin it?
Click to expand...
Click to collapse
I had the same issues. Here's what I understand. Voodoo changes the filesystem to ext4, as you know. But RFS can't read that. For some reason, the kernel doesn't flash properly because it still sees the ext4 partition.
So here's what I did to fix. Pain in the arse, but it works.
In ODIN, Flash Eugene's Froyo that does not brick ROM in the bible
When that is complete the recovery will come up and there will be some errors. That's ok. We don't want this one.
THEN flash RFS (you should already have it) from the bible.
SHOULD be good to go. Like I said, it's dumb that you have to go through that, but it is what it is. I did it 4 times in 5 hours using trial and error. I know this method works.
Good luck!
in adb, i ran "adb shell", "mount" and i checked the "/dev/block/" and it said "/dev/block/mmcblk0p3 /data_tmo rfs rw,nosuid,nodev,vflat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0". so i think its rfs..i think lol is there a command in adb that can disable the lagfix?
is the RFS file ur talkin about, "s1_odin_20100512.pit" ?? or is it somethin else?
I agree, flash to froyo that does not brick, then flash back to the original firmware, not leaked updates. I have had great luck with checking repartition when flashing froyo, keep it checked when flashing back to stock. Then uncheck it and flash the stock rom a second time.
Sent from my SGH-T959 using XDA App
boimarc89 said:
in adb, i ran "adb shell", "mount" and i checked the "/dev/block/" and it said "/dev/block/mmcblk0p3 /data_tmo rfs rw,nosuid,nodev,vflat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0". so i think its rfs..i think lol is there a command in adb that can disable the lagfix?
Click to expand...
Click to collapse
No, the problem is probably mmcblk0p4 a.k.a /data being and ext4 filesystem, but if you flashed the stock kernel the phone won't be able to mount /data since it won't understand the ext4 filesystem... and THAT's the problem.
boimarc89 said:
is the RFS file ur talkin about, "s1_odin_20100512.pit" ?? or is it somethin else?
Click to expand...
Click to collapse
Is that sarcasm? I hope it is
boimarc89 said:
is the RFS file ur talkin about, "s1_odin_20100512.pit" ?? or is it somethin else?
Click to expand...
Click to collapse
that pit file just tells Odin how to setup the partition tables... its the actual .tar file that contains the .rfs install files... if you can get into Clockwork and install a custom ROM, then you can disable the voodoo lag fix, and reflash the stock kernel so you can go back to stock
or
like everyone else has mentioned go to froyo, then go to stock
If you can get into clockwork, just flash the flashable zip version of the froyo Rom. Accidentally forgot to disable voodoo when I flashed it earlier. What do ya know, the ROM booted all the way up. That will work without odin. Given that it wasn't a fluke and u have access to clockwork still. If not odin is your only option. Point blank.
http://dl.dropbox.com/u/9742964/Vibrant_Frankin_Twiz_Update3.zip
thats eugene373's Frankin-Twiz3 custom ROM preloaded with JACs Voodoo kernel, just flash through Clockwork and it'll install the voodoo fix again so you can disable it
If it doesn't help you, it may help others in a similar situation.
i got it now..im running the ji2 firmware trying to get to build.prop so i can fix the missing market apps..idk how to get to it...can i extract it by adb?
boimarc89 said:
i got it now..im running the ji2 firmware trying to get to build.prop so i can fix the missing market apps..idk how to get to it...can i extract it by adb?
Click to expand...
Click to collapse
Use a root explorer app and edit it directly from your phone.
boimarc89 said:
i need help...my vibrant is sitting at a blk screen after odining the stock jfd.tar . i had had voodoo lagfix and a market lagfix on there earlier and i dnt think i took it off correctly bcuz i was late to class but shouldnt odin take care of thatif i selected repartition and the stock jfd.tar file?...could it be that its still setup as EXT4 and not rfs like it should be when its stock? now i JUST noticed that it will only boot completely if i load a custom rom despite using odin to revert to stock. what happens is that it boots to the tmobile pink square but no sound, when the galaxy S screen comes on, then the tmo sound comes on (late), then the screen goes blk w/ the touch buttons lit. in order for it to boot i have to flash the root update in clockwork, reboot, then flash a ROM, reboot....have i done somethin wrong? why wont it boot when i odin it?
Click to expand...
Click to collapse
I'm probably asking for it, but ...
How is this thread "in the rom bible"? You messed up in some manner, didn't quite understand exactly what you were doing, you don't fully understand what a fstab is or how partitions really matter, sure, I understand that. But why does this warrant a thread: yeah, that's a bit beyond me ...
After reading several other threads promoting self-policing, why oughtn't it be sought here.?! If the only reason that this thread is offered a place in dev is because there is a mention of ext4, then we are all in trouble.
I've been flamed and chastised before for my views, but if no one polices, then who will? Is your question really geared toward the development of something Android related? Then perhaps you have a valid thread. But if it's not genuinely development related, why are you posting here?!
disable-lagfix in an update.zip
This article has a link to install the disable-lagfix with an update.zip file. If you have access to recovery I suggest you use that.
http://androidspin.com/2010/09/23/overclock-add-some-voodoo-to-your-samsung-vibrant/
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
So I broke my market like a week ago and can't fix it. The only thing I haven't tried is recovering to a few weeks ago BUT I am unsure if it's safe to do because I am currently running on DJ05 with Nemesis's test 6 sv1100 voodoo kernel.
If I revert back to a time (using the red recovery screen) with dl01 and NO lagfix installed (without a broken market too) will I be okay? If it's okay to do, will DJ05 still end up being installed?
I am fairly new to this but I always try to figure things out myself before asking. However, I was unable to find difinitive answers and I am just unsure.
Any clear help in layman's terms would be greatly appreciated!!
Sent from my SCH-I500 using XDA App
If you are flashing a non voodoo kernel over a voodoo one you must first disable voodoo. Do this by creating a folder or file named disable_lagfix and putting it in the voodoo folder of your sd card.
Just to be safe, reboot fully before flashing anything. It should do the voodoo female robot voice. When you get back onto your home screen run quadrant to ensure your scores are somewhere around 800. If they are still over 1000 voodoo didn't disable properly. If it's disabled you should be all clear to flash a non voodoo kernel. Just make sure if you have a dj05 modem and kernel the rom needs to be dj05 etc. good luck
Edit: just in case I didn't read your post correctly: if you are restoring an old backup of di01 you will also need to flash the stock di01 modem through odin and a di01 kernel through cwm. Hope this helps.
Sent from my sch-i500
I'm a relative newbie and not very tech-oriented, and I appear to have screwed up big time. I'd appreciate any help that can be offered. To cut to the chase, when I attempt to boot up my Fascinate, it gets stuck indefinitely on the Samsung logo.
Here's what I did to screw it up. I rooted my phone when I first got it last year and did a lagfix. It unrooted with the update to JD05. Yesterday I attempted to root it again using two different 1-click methods, neither of which worked. I then followed the instructions in the "Modified CWMrecovery for Odin" thread, not having it work until finally succeeding in getting root using CWM Red. The phone rebooted and was rooted, and everything seemed fine, so I used Rom Manager to Boot to Recovery. This did something strange--it took 15 minutes to get to the recovery screen, with a digital voice periodically telling me how much longer it would take. When I got to the recovery screen the first thing I did was to perform a backup. I think this effort to be safe did me in, because the phone must have already been screwed up then and I think I backed up the screw-up.
I then attempted to reboot and since then all efforts get me stuck on the Samsung logo. I've tried almost all options from the Recovery screen: reboot system now, apply sdcard update.zip, wipe date/factory reset, wipe cache partition, install zip from ascard, and restore. All bring the same locked up phone.
I'd appreciate any ideas to bring my Fascinate back to life!
First off the only way to get to red CWM is to install a voodoo 5 kernel. I'm thinking the voodoo kernel and the one click lag fix don't play well together. I'm sure someone else will step in with more info however I would start by looking for a thred called how to completely remove voodoo. Then try odin to restore. Good luck.
Edit. I read your post again and not sure if u did one click lag fix or just an older voodoo kernel. Either way same result u have to disable voodoo 4 and one click to install voodoo 5. Odin it. The voice u hear was the voodoo kernel converting your system to ext4 if this was the first time you've heard this I think your first lag fix may have been the one click.
Sent from my SCH-I500 using XDA App
Yes this happed to me too. If i take it to the Verizon store will they know my phone is rooted and moded? i need help ASAP
Search the forums on how to properly removed the voodoo lag fix. Then you need to reflash dj05. Voodoo doesn't really do much except for show you a higher quadrant score and limit to what roms/themes you can install. Same thing happened to me. Just do a quick search, I think its in the development section. The easiest way to remove it is with and. Hope this is somewhat helpful.
so fresh and so superclean.
Don't bring it to verizon because you would be defrauding them for your mistake. see if you can access your sd card through the computer and put either a file or folder in the voodoo folder called disable_lagfix and try booting again. If that doesn't help (it is probably too late for that) then you need to flash back to stock through odin. find the thread in development on how to do that. Good luck. Your phone is not broken. Breathe.
Sent from my sch-i500 using dl09 supah clean
Here is the ODIN back to stock if you don't want to bother with removing Voodoo. That should fix your phone with or without Voodoo. It's always worked for me.
THANKS SO MUCH its back to normal i cant thank you enough
Many thanks for all of the help.
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