Related
I tried to uninstall Voodoo and now when I restart my phone it shows the galaxy
s and verizon animations, then loads up to a black screen and lit up capacitive icons. I can reboot into recovery, but I can't seem to mount the sd card and i keep getting errors when I try to mount any extensions. Please tell me there is something that I can do to fix this.
try wiping?
try instructions from "how to remove voodoo completely" thread. i cwm flashed the file from there when i had the same problem as u.
Take a deep breath. If you can see any thing at all on your screen, it's not bricked.
Just follow the instructions here;
How to remove voodoo
And your phone will be like new.
I would specifically follow the instructions that i give on page three, as adrynalyne's auto removal script still doesn't work 100%.
http://forum.xda-developers.com/showthread.php?t=804784&page=3
i had a similar problem when i tried to remove the old lag fix.
screen turned black on bootup and lights would come on but nothing else...
i had to use odin to restore everything and i had to wipe the cache and data from recovery.
Sometimes pixie dust works...or just listen to them
Sent from my sharks with fricking lazers on their backs
Thank you for the replies. I was able to finally mount the phone after doing a nandroid. It was force closing like crazy, but I kept with it until I was able to mount the phone from the os. Then I put in the voodoo lagfix uninstall folder and wiped and rebooted. Then I was able to nandroid to another backup and wiped, then did a odin restore, wipe and nandroid data restore. Now it's running like new and voodoo is uninstalled. This is an interesting experience coming from the hero and droid. I am a champ at those phones and I have never bricked a phone and I bricked this one twice. Kind of reminds me of the first time I started playing with my hero. It's a way to get the blood pumping.
emplox said:
I would specifically follow the instructions that i give on page three, as adrynalyne's auto removal script still doesn't work 100%.
http://forum.xda-developers.com/showthread.php?t=804784&page=3
Click to expand...
Click to collapse
This. My removal utility is a pain in my ass
I found it works, but then you gotta battery pull and nandroid back. A clean wipe wont cut it.
I disabled voodoo lagfix and the phone would not boot. I tried to use Odin and now all I get is force close when the phone boots up and it will not let me mount the card. any ideas?
Since I initially wrote this thread, I tried Voodoo one more time and when I removed it, this time with an app to see if it was user error, it once again made my phone non-responsive, it seems that it just is a bit unstable when being removed. With that said, I was where you are now and I was able to restore it. I did a factory wipe of my phone and cache through clockwork and then replaced my kernel and put the full stock image on the phone through Odin. Then I went into clockwork and went to my last backup and restored data. The phone loaded up, but it was as if I did a factory reset. I skipped everything, mounted my phone to my cpu and deleted voodoo files manually (the file needed to remove vodoo was just sitting there too). I went back into clockwork and just restored data under the advanced settings and I was back in business. Hopefully this can help you too. It may be overkill, but it worked.
You did NOT brick your phone. Will people please stop saying they bricked their phone when they haven't? Bricked means YOU CAN NOT RECOVER!!!! Stop scaring and confusing people! pretty please.
I'm not sure who that was directed to, but when this first happened,for a while it seemed that no matter what I did, the phone would not become operable. So for all intents and purposes, it is bricked. It doesn't matter if it can be restored, if you can't fix it, then it is bricked. I don't understand why people are so stuck on semantics. If that is the case, then no phone can be truly bricked, because once you send it to Samsung, they can restore it with their proprietary software. If your phone is nonresponsive and you can't fix it, it's bricked. I kept at it and was able to restore my phone, but I've read that there are people on here who couldn't figure it out and gave their phone in for another one. Because restoring the phone is above their skill level, they bricked their phone.
Kamar234 said:
I'm not sure who that was directed to, but when this first happened,for a while it seemed that no matter what I did, the phone would not become operable. So for all intents and purposes, it is bricked. It doesn't matter if it can be restored, if you can't fix it, then it is bricked. I don't understand why people are so stuck on semantics. If that is the case, then no phone can be truly bricked, because once you send it to Samsung, they can restore it with their proprietary software. If your phone is nonresponsive and you can't fix it, it's bricked. I kept at it and was able to restore my phone, but I've read that there are people on here who couldn't figure it out and gave their phone in for another one. Because restoring the phone is above their skill level, they bricked their phone.
Click to expand...
Click to collapse
I believe the preferred term is "soft-bricked"...LOL
Just do a wipe. I used adrenalines uninstaller. Worked like a charm. Voodoo is a pain in my butt
Sent from my SCH-I500-Fascinate using XDA App
Haha, yes, I've seen people use the term soft bricked here. Voodoo's instability is interesting though. I haven't felt this way since I started using smart phones in 03'. Just something I can't seem to get to work. Good thing the payoff isn't that great. To the person who is having trouble with their phone, I hope I, or someone else here, was able to help.
I just removed lagfix and it worked perfectly. Lol my phone never had lag until I installed lag fix. But I do love the kernal And boot animation provided.
Wanted to say I removed voodoo tonight by adding the remove file via adb. Everything worked as planned. Took about 10 minutes to get off step 2 but everything completed and booted up.
Sent from my SCH-I500 using XDA App
I can only offer <3 support... When I tried to remove Voodoo the first time, ugh I went through hell. I was stuck on my loading screen with Samsung just staring me in the face. Followed the complete remove by Adrynalyne, and everything was ok in the end.
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.
This has happened to me twice now, I've had to replace my D2 because it keeps bricking for some reason. I don't know why, but now whenever I try to download something from my SD card (a rom or a theme) It just bricks. I go to mounts/storage, click on that then I go to download from SD, I select my rom and it doesn't work. It'll go to the boot logo, show Matt's logo (I used Matts Epic2.5) and won't stop repeating it over and over again.
Sometimes it'll show the whole logo, then after maybe 5 times it'll show half the logo then stop and keep repeating this process. I don't know why, but it used to always work in the past. What am I doing wrong? Do I need to wipe my data and cache every time now? I never had to before.
I really miss my Droid 1 (root wise lol)
BTW, I don't know if this means anything, but do I need to deodex my phone or however you say it :S, sorry I'm really new to droid 2. I don't even know what deodex means lol. Anyone help me on explaining what that means?
Deodexing or de-odex-ing is how it makes more sense to me just means that all of the apk's or applications on your phone are together and don't have stray .odex files in the /system/app folder (or wherever they're located). Phone dev's will leave these .odex files out of the .apk's so that load times are supposedly faster but the file called services.jar which needs to be edited for detailed themes has to be de-odexed before it can be edited and if one file is de-odexed then the others should all be.
I'm not sure what specifically the problem is and please don't be offended if I'm going too far but in order to mount /system the entry in mounts/storage has to read "unmount /system". Make sure the you've got the entire ROM, but wiping cache and data is worth a shot too.
Also if you have a major problem with your droid 2 you just need to flash the .sbf there are two different ways to do it (and two versions of the sbf). One in windows and the other in linux and (thanks to me lol) the linux version is available to anybody with a windows computer too.
Yeah I fixed my phone today using the windows sbf. Do you think it's worth it to deodex my phone? And I don't know what the problem seems to be I have the full rom and I never had to wipe before :/ I guess I'll just wipe every time now.
Most of the ROM's now are de-odexed so you shouldn't have to the only reason you would need to is to theme. To check and see if it's deodexed just use Terminal emulator and enter
Code:
$ cd /system/app
$ ls
This means change directory to /system/app then list the files in there.(it's a lower case L)
If there are files that end in .odex then it's not de-odexed.
UPDATE: I sbf my phone and got it "unbricked". So I just got root access and then I tried to instal the 2.5 Epic Rom. These are the steps I went through.
1. Went to Titanium Backup and restored my Droid Bootstrapper app.
2. Opened the app and did the Flash Recovery, is said success then I went into recovery mode.
4. I went to Mounts and Storage, pressed OK on Mount/system
5. Went to Install from SD Card.
6. Went to EUnleashed2.5 (however it is)
7. It installed only halfway and said install is complete and the screen would just sit there when it was only less than halfway full.
9. Now my phone is bricked again and I am currently unbricking it.
What am I doing wrong?
EDIT: By the way, if those things that I clicked on aren't exactly right, it was because I was typing it from memory because my phone was bricked and I couldn't actually see them.
First, you have not been bricked - you've had bootloops, which means some files are corrupted, missing, or incompatible. You can cure a bootloop, but you can't cure a brick.
My guess is you're trying to install Epic 2.5, which has 2.2.20 baseband/kernel dependencies, over your new 2.3.20 baseband/kernel from the sbf. In other words, Epic 2.5 can't and won't install on your phone anymore. You'll have to wait for Epic 3.0 or use another ROM that has been built off 2.3.20.
karnovaran said:
First, you have not been bricked - you've had bootloops, which means some files are corrupted, missing, or incompatible. You can cure a bootloop, but you can't cure a brick.
My guess is you're trying to install Epic 2.5, which has 2.2.20 baseband/kernel dependencies, over your new 2.3.20 baseband/kernel from the sbf. In other words, Epic 2.5 can't and won't install on your phone anymore. You'll have to wait for Epic 3.0 or use another ROM that has been built off 2.3.20.
Click to expand...
Click to collapse
Lol thanks, that makes a lot more sense to me now. I just saw his post about 3.0, I can't wait till it comes out. Thanks for the help!
So, I'm pretty new w/ Android. Just flashed with voodoo lag fix D02-Kernel-LV-1250 using Dirrk's instructions. This means that I did the following:
- Rooted (was already done)
- Installed CWM (from instructions here)
- Downloaded D02-Kernel-LV-1250 and put on SD card
- Rebooted to CWM and did a backup
- Booted into recovery and flashed kernel
- Rebooted
Now, I see that DJ05 is released. (I even see stuff about voodoo lag fix for it...didn't know that was available.) So, now I wished I hadn't installed voodoo lag fix, because I hear it is difficult to uninstall.
I've tried to do my own research here, but I really don't want to change messing up my phone, so I'm asking for help here. Here are the threads I have sifted through:
- http://forum.xda-developers.com/showthread.php?t=805052
- http://forum.xda-developers.com/showthread.php?t=804784
- http://forum.androidcentral.com/fascinate-roms-hacks/34819-how-go-back-stock.html
- http://www.fascinateforums.com/foru...oms/685-instruction-remove-voodoo-kernel.html
- http://www.fascinateforums.com/foru...everything-you-wanted-know-about-kernels.html
Questions
What is the trade-off b/w D02 and DJ05?
If DJ05 really has the lag fix, is there any benefit of staying on D02?
For future reference, how do I know what kernel version I am using (Voodoo4 vs Voodoo5)?
Understanding what I've done above, what do I need to do to get to DJ05?
Do I really need to flash to stock and lose everything to get there?
And if so, can I use the backup I made in CWM?
If not, and I have Titanium Backup installed and all apps/data backed up, does it matter if I have to go back to stock?
Sorry for the newbie questions for help, but I really want to make sure I do it right. Any help is greatly appreciated.
FYI, this is what I've looked through for the new stuff available (should I go with the last link?):
- http://forum.xda-developers.com/showthread.php?t=869990
- http://forum.xda-developers.com/showthread.php?t=872378
- http://forum.xda-developers.com/showthread.php?t=874809&highlight=voodoo+lag+fix+vs+dj05
Thanks for any help you can give!
1. D02 is just the kernel version and DJ05 is a firmware update so there is really no comparison here.
2. updating to dj05 is worth it because it fixes several issues with the phone.
3. the only way to tell between voodoo 4 and 5 is to read which one you are downloading
4. it's a good idea to do a full wipe of the phone before updating to dj05 and your nand backup before the update will not work properly because the new kernel doesn't work with the old firmware.
5. if using ti-backup then yes wipe
to remove voodoo go to the voodoo folder on you sd and make a TEXT file called disable_lagfox.txt and reboot then LET IT FINISH COULD TAKE UP TO 20 MIN IN SOME CASES so wait it out don't pull battery no matter what.
when you update use the stupidfast kernels if your afraid of messing up your phone don't use voodoo it really is more of a power user option. didn't answer everything on order I know lol but think I coveted most of it
Sent from my SCH-I500 using XDA App
I'd like to add that in some cases the disable_lagfix method might not work. (It's supposed to be disable_lagfix, not .txt and not lagfox lol). In my case, it ran for nearly two hours without doing anything. Don't worry, if it takes that long just pull the battery and use ODIN to return to stock (from Adrynalyn's thread). But obviously make backups before you try to disable voodoo.
lol yea disable_lagfix sry swype error haha and the .txt will be added guess I just was thinking about doing it pc side I'm use to putting my own extension sometimes.
Sent from my SCH-I500 using XDA App
Thanks for the info! I've run out of time to do it before I leave for Christmas, but I'm going to do this first thing when I get back!
DJ05 fixed my GPS to the point of locking nearly instantly.
That's the kicker for me
everything else is gravy
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.