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.
Ok, so I was playing around with the new Root Tools app and made a few, what I thought were safe, tweeks to the system and rebooted the phone. It gets past the M screen, runs the boot animation and then starts the boot animation again. No way out except to pull the battery.
How can I get it out of this endless bootloop? If I have to factory reset and start again from scratch, so be it. I would just like to know how.
I've tried holding down different button combinations on boot but haven't come up with the right sequence I guess.
I've also tried pulling the battery as the animation starts, then putting it back in and rebooting which is supposed to call up the recovery mode, but it doesn't. I'm not sure what to try next? I wish these things had a reset button
It's a Droid 2 Rooted with the stock rom running Froyo 2.2. I have the Bootstrap recovery loaded and did a backup with the clockwork recovery. I also have, and use, Titanium Backup Pro for Root.
After bootlooping pull the battery and put it back in. Then plug the droid 2 in with the cable either wall or USB will work. Then turn it on and it should get you recovery. The phone has to be completely off when you plug it in though.
Sent from my DROID2 using XDA App
EDIT: I tested it and USB won't work (at least for me) better off just using the wall plug.
Thanks, but that not working either. When I plug in the cable after the battery pull it starts up automatically and goes to the battery charge screen. I then shut it off and start it back up with no battery but plugged in and it goes right back into the boot loop after the M screen.
The batter charge screen is what you want. Just press the power button after you get the charge screen and you'll be booted into clockwork.
But in order to factory reset from a bootloop you have to flash an .sbf theres a few different tutorials. One in Windows, Another in linux/mac, and another in linux but for windows machines through an Ubuntu livecd(that I made).
Oh, OK I thought it was going to go right into recovery mode. Good to know.
I finally figured out how to get into the stock recovery and bootloader, so I tried to run the stock restore but after it wiped the data, it couldn't find the recovery file! So then I read in another post about using RSDlight 4.9 to do an sdf restore so I used that method. Of course while it was flashing I did come across your Ubuntu method and that does look like it would be a simpler process. I'm going make one of those CD's to have for next time.
Anyway, I was able to get it back to stock. It looks like most of my stuff is still on the SD card, so that's a bonus! I'll have to re-root before I can restore everything via Titanium, but that's going to be tomorrow's project. As for now just happy to to have my phone back. Especially before the wife (who has been telling me for weeks to stop F'in with it) found out .
I really appreciate that you took the time to help, thanks again!
No problem.
Could you change your Thread title to include [SOLVED]. Thanks
Can you please explain to me how you fixed this problem? I am currently having this problem now.
Please do not open/post in multiple threads for the same issue. This is a waste of time as we can see you have an open thread. Please reply to my response in your original thread for further assistance. (http://forum.xda-developers.com/showthread.php?t=824254)
newk8600 said:
Could you change your Thread title to include [SOLVED]. Thanks
Click to expand...
Click to collapse
Ok, your wish is my command! ;-)
Sent from my DROID2 using XDA App
Can I close this?
Yes. This issue has been resolved.
theecho said:
Yes. This issue has been resolved.
Click to expand...
Click to collapse
Ok, thanks
Hey guys i know "Help!" threads get annoying (at least in the Fascinate forum they do.) but i could really use some help.
Rooted my friends phone today (root,clockwork,rom manager), and was going to install regular JAC kernal /voodoo w/o color fix.. I made sure the phone had the smaller NAND chip. Installation went fine (phone booted, voice told me it was switching to ext. 4.) and the voice said voodoo was complete. The phone was stuck at the S logo for about an hour and it was then i decided voodoo was botched. From there i rebooted to clockwork and went to restore the nandroid i made when i rooted. The nandroid got stock at one of the Data files for about 30 minutes. (i have a feeling this is around where i messed things up myself) Decided screw it and was going to flash JI6(T959UVJI6) and the stock kernal with ODIN. Now the phone boots past the S logo but the screen stays black and only the backlight menu buttons light up. It wont go past there. Any quick help is appreciated.
You didn't disable the lagfix I'm assuming.
Odin Eugene's Froyo that doesn't brick, then Odin JFD, install ROM of you're choosing.
Did you even try to search for a fix before posting???
~SB
problem0atique said:
Hey guys i know "Help!" threads get annoying (at least in the Fascinate forum they do.) but i could really use some help.
Rooted my friends phone today (root,clockwork,rom manager), and was going to install regular JAC kernal /voodoo w/o color fix.. I made sure the phone had the smaller NAND chip. Installation went fine (phone booted, voice told me it was switching to ext. 4.) and the voice said voodoo was complete. The phone was stuck at the S logo for about an hour and it was then i decided voodoo was botched. From there i rebooted to clockwork and went to restore the nandroid i made when i rooted. The nandroid got stock at one of the Data files for about 30 minutes. (i have a feeling this is around where i messed things up myself) Decided screw it and was going to flash JI6(T959UVJI6) and the stock kernal with ODIN. Now the phone boots past the S logo but the screen stays black and only the backlight menu buttons light up. It wont go past there. Any quick help is appreciated.
Click to expand...
Click to collapse
If you can still boot into clockwork recov. you can save it by pushing the undo voodoo zip file that was mentioned about. Assuming that u have adb access. If not odin froyo that doesnt brick tepartition checked. Turn off. Boot back in download. Odin stock jdf. Ji6 isnt a standalone rom. Its more like a no wipe update. Lucky his vibrant wasnt hardware locked lol. He will have a 90% chance of losing EVERYTHING
Had to odin flash froyo that doesnt brick then jfd and yep he lost all his data but he didnt have much to begin with. Now happily running Fusion. Thanks for the help guys!
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.
it was a rutine day as usual, running the GPS with CoPilot and playing music stream via BT to the car
and all of the sudden BAMN! the scary grey Google screen with the unlocked lock shows up
I was like *** BEEP ***, in my head i though oh, it might just be that reboot bug that is plaguing everybody but me, and now it's finally catching up
but noooooo... after i got to work i tried to reboot the phone (pulling battery out), nada, nothing, zero, zip... still the same dead google screen
then the worse case scenarios flashes through me head (knowing samsung past issues ) so i'm blazing for the worse...
currently i confirmed it can go into CW recovery screen and also go into the Odin Download Mode screen
so i'll try a nandroid backup first
if that is a no go, Odin is next...
Good luck, man. I feel your pain.
Hope you don't have to resort to odin, but if you do, that safety net will have proved its utility.
Again good luck!
Sent from my Nexus S using XDA Premium App
I can almost guarantee that ODIN will work. I resurrected a Fascinate that was locked out from itself using ODIN as well as a Captivate that had this same problem you are describing. ODIN dont **** around.
AllGamer said:
it was a rutine day as usual, running the GPS with CoPilot and playing music stream via BT to the car
and all of the sudden BAMN! the scary grey Google screen with the unlocked lock shows up
I was like *** BEEP ***, in my head i though oh, it might just be that reboot bug that is plaguing everybody but me, and now it's finally catching up
but noooooo... after i got to work i tried to reboot the phone (pulling battery out), nada, nothing, zero, zip... still the same dead google screen
then the worse case scenarios flashes through me head (knowing samsung past issues ) so i'm blazing for the worse...
currently i confirmed it can go into CW recovery screen and also go into the Odin Download Mode screen
so i'll try a nandroid backup first
if that is a no go, Odin is next...
Click to expand...
Click to collapse
hey what is your "flashing" history? (i.e. roms, kernels, etc.)
serialtoon said:
I can almost guarantee that ODIN will work. I resurrected a Fascinate that was locked out from itself using ODIN as well as a Captivate that had this same problem you are describing. ODIN dont **** around.
Click to expand...
Click to collapse
Well, that's if Odin is used right, otherwise it can ruin the phone. I've used it to bring back my Vibrant a bunch. It's good knowing that these Galaxy S phones are nearly brick proof.
All is not lost, honest...
AllGamer said:
it was a rutine day as usual, running the GPS with CoPilot and playing music stream via BT to the car
and all of the sudden BAMN! the scary grey Google screen with the unlocked lock shows up
I was like *** BEEP ***, in my head i though oh, it might just be that reboot bug that is plaguing everybody but me, and now it's finally catching up
but noooooo... after i got to work i tried to reboot the phone (pulling battery out), nada, nothing, zero, zip... still the same dead google screen
then the worse case scenarios flashes through me head (knowing samsung past issues ) so i'm blazing for the worse...
currently i confirmed it can go into CW recovery screen and also go into the Odin Download Mode screen
so i'll try a nandroid backup first
if that is a no go, Odin is next...
Click to expand...
Click to collapse
Hi AllGamer.
I had a similar disaster with the black google screen, and I had the unlocked bootloader as well, first I relocked bootloader, then used odin to reflash (http://forum.xda-developers.com/showthread.php?t=947950 ) then used the e0b546c442bf.signed-soju-GRI40-from-GRH78.e0b546c4 update (http://android.clients.google.com/p...2bf.signed-soju-GRI40-from-GRH78.e0b546c4.zip) renamed it to update.zip, put it on root of memory, and ran it via the built in recovery mode after..phew.
Odin saved my life to!!
Good luck...
i guess i should have updated the post before heading out to lunch
not too long after i posted the original message, i was able to reflash any ROM, and got it to boot back to normal.
it was weird for some odd reason the ROM just got corrupted? i don't see how's that possible
I was on Bionix 1.3 beta for the longest time, and i've been on Bionix pretty much ever since December 2010/Jan 2011
I'm now back to Stock 2.3.3, but i replaced the stock recovery with CW recovery
I simply booted into the CW recovery mode, and then loaded a new ROM from zip
Yipee
AllGamer said:
i guess i should have updated the post before heading out to lunch
not too long after i posted the original message, i was able to reflash any ROM, and got it to boot back to normal.
it was weird for some odd reason the ROM just got corrupted? i don't see how's that possible
I was on Bionix 1.3 beta for the longest time, and i've been on Bionix pretty much ever since December 2010/Jan 2011
I'm now back to Stock 2.3.3, but i replaced the stock recovery with CW recovery
I simply booted into the CW recovery mode, and then loaded a new ROM from zip
Click to expand...
Click to collapse
Glad your sorted....