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.
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.
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!
borked up the fascinate whilst trying to update to the devs 2.2.
i know exactly what i did wrong. i was running voodoo5, and i clicked to disable lag fix, but i forgot to restart to let it *actually* disable before trying to load the new stuff. STUPID!
when that happened, it hung on samsung screen, then after battery pull all the phone will do is boot loop.. samsung screen, then goes to robot and screen says says "wiping cache, data, ect.." and then back to samsung screen to reboot and reboot.
i have literally 30 tabs open with articles from here and other forums, nothing seems to be working. here is what i have tried.
1. tried booting back to red cwm and playing with the lagfix (enable and disable again) to see if it would work, no go. i ended up losing red cwm - had to ODIN red back.. i cant get green to flash.
2. tried flashing DL09 both the full package and each individual part via ODIN
3. tried flashing the stocki500system.md5 (from the board) and kernel via ODIN, and nothing.. same boot loop. everything i have flashed via ODIN still gives me a boot loop..
4. tried to connect via ADB but it wont let me access the phone.. NOTE: i just downloaded ADB as a last resort and know nothing about it..
the only thing i can seem to do is get to red cwm. i have several backups in the restore section, but none of them seem to work - either i get a "no file found" even though i can see the file(s), or i get an error after it does load that says ".android_secure.img not found. skipping restore of /sdcard/.android_secure"
any ideas?
Okay follow these steps. Make sure you follow them step by step. Even though you have the lagfix installed this removed it for me.
http://forum.xda-developers.com/showthread.php?t=782204
Place the PIT file where it belongs. Then ODIN the system, kernel, and recovery in that order. Don't restart the process every time. Just ODIN them one after another.
thank you very much for taking a moment to answer. i did follow that thread, however
i managed to get the stocki500 recovery but the other files (recovery, PIT) are all 404 not found errors.
ive tried that stock md5 and it still boot loops. i actually have that tab open from when i tried that route..
any other ideas and thanks again
Thats why its not working. Try this restore by adrynalyne. The file is there and everything is in one. Just ODIN in the PDA section. This should work.
http://forum.xda-developers.com/showthread.php?t=867648
I got myself into a bit of pickle too. Kept getting errors on the new_cwm file. After numerous attempts. I figured out the file hadn't downloaded correctly and the archive was damaged. Folks who havent installed Froyo yet, do yourself a favor and check the files before you save it to your sd card.
BSayre18 said:
Thats why its not working. Try this restore by adrynalyne. The file is there and everything is in one. Just ODIN in the PDA section. This should work.
http://forum.xda-developers.com/showthread.php?t=867648
Click to expand...
Click to collapse
downloading now.. thanks for the point to this file.. i hadnt found that one yet
no problem. it should work out good.
mailaliasgar said:
I got myself into a bit of pickle too. Kept getting errors on the new_cwm file. After numerous attempts. I figured out the file hadn't downloaded correctly and the archive was damaged. Folks who havent installed Froyo yet, do yourself a favor and check the files before you save it to your sd card.
Click to expand...
Click to collapse
i soft bricked doing that with a corrupt file before.. however that time i was able to restore using my backup.
this time, every time i try a method, it kicks me back to boot loop. if the file that im downloading now doesnt work, i will have to try and figure out ADB as a last resort..
thanks much for the help!
BSayre18 said:
no problem. it should work out good.
Click to expand...
Click to collapse
problem
thank you for all your help
mrjake1970 said:
problem
thank you for all your help
Click to expand...
Click to collapse
So this worked for you? You just re-rooted as normal?
def
Thank you all for your help. i applied all the info i got here, and one of them worked it finally took the ODIN flash to stock and i recovered into FROYO from there.
seriously thank you all.. its great that the community is so supportive
I did the exact same thing a couple of days ago, and recovered a similar way, odin back to D101, flashed DL09 & superclean, then restored a backup, then disabled voodoo and finally flashed DL30. I've got a couple of questions.
1: Is voodoo completely off my phone or is it just disabled (is there a difference)? When I apply update.zip from the blue recovery I get green cwm.
2: Each time I backup, restore, flash a different rom I apply update.zip, then from green recovery I flash "new_cwm.zip". Is this necessary?
Joe T said:
I did the exact same thing a couple of days ago, and recovered a similar way, odin back to D101, flashed DL09 & superclean, then restored a backup, then disabled voodoo and finally flashed DL30. I've got a couple of questions.
1: Is voodoo completely off my phone or is it just disabled (is there a difference)? When I apply update.zip from the blue recovery I get green cwm.
2: Each time I backup, restore, flash a different rom I apply update.zip, then from green recovery I flash "new_cwm.zip". Is this necessary?
Click to expand...
Click to collapse
i followed all the hints i got, and i think that the one i got about formatting helped me get out of the boot loop from hell.. it finally took my flash from ODIN, it wouldn't until i did the format(s)..
mind you i am NOT an expert, however from what i read and talked about offline, voodoo is still resident on your phone but disabled (check to see if you have the voodoo file still on your card).. if DL30 is running fine, you are ok..
from what i have read, yes.. the new cwm is required in order to get it to mesh properly with 2.2 leak.. i havent had any issues and i loaded that as well.. from one of the posts i read, if you are a serial flasher, then you need to make sure that not only you download the new cwm zip, but also should have deleted the entire clockworkmod folder from your card for best results..
I love this threadd.... I did the same damn thingg...
Sent from my SCH-I500 using XDA App
You guys are not alone. I'm just glad the peeps that know what's going on have the patience to put up with us.
Sent from my SCH-I500 using XDA App
adrynalyne's di01 odin package covers a multitude of sins.
upsidedownaaron said:
adrynalyne's di01 odin package covers a multitude of sins.
Click to expand...
Click to collapse
It will literally bring any phone back from the dead as long as its a software issue. I recommend keeping the di01 package, samsung drivers and Odin 1.3 on your computer at all times...
Sent from my SCH-I500 using XDA App
godihatework said:
It will literally bring any phone back from the dead as long as its a software issue. I recommend keeping the di01 package, samsung drivers and Odin 1.3 on your computer at all times...
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
ABSOLUTELY!! I have those on my computer at all times, adrynalynes d101 brought me back a few times.
Sent from my stock 2.1
unrooted, fully bloated (for now) Fascinate
Hello all,
Been rambling around the forums in ninja mode trying to gain enough knowledge to not mess up my phone before trying to mod it but alas best laid plans....
Anyhoo I was working to put the Froyo leak on my phone and everything was good till I did a cwm wipe of the phone and wammo it had problems. I managed to use Odin to get it back to barebones stock, lost my high score in Angry Birds too dang it.
Now that I am back to this point I tried to run the Verizin updates and it downloads and goes into install mode on reboot and it dies at Updating Modem section. At that point I saw I was rooted so I removed that and tried again, no dice amigo. Did a factory wipe, nothing. Cleared the cache, fail again.
If it helps its trying to do a dh12 to di01 update. Got any ideas?
When you went to stock did you flash the stock kernel and stock recovery as well? I had to do this when I updated to dl09
Good question and yes I believe I did, I followed this: http://forum.xda-developers.com/showthread.php?t=782204&highlight=return+stock thread to get the job done. Let me try it one more time.
Also I load the PIT file with each md5 correct?
Looks like I fixed it on the second time around. Not sure what I missed but the update went through. No worries. Might pay someone to hand hold my through getting DL30 on my phone cause even as an IT guy I'm missing something every time.
Strong thing is, once the DI01 update happens it actually doesn't find any other updates...wifi is off.
VZW pulled the DL09 update due to the e911 bug until it is fixed
Makes good sense. Sooo anyone wanna tutorialize me on how to de-crappify my phone? Its worth a donation from me.
You're on di01 right?
I would odin the dl09 package, then use cwm to flash super clean 2.2. Clean, debloated froyo goodness
Sent from my SCH-I500 using XDA App
Sounds good. The problem lies in me somehow fudging up the process at some point and having to set my phone back to stock again.
Where did you see this?
"VZW pulled the DL09 update due to the e911 bug until it is fixed"
Have any sources on this one? I really would like to see them.
Not doubting you, I have just been rebooting and *228 for 3 days trying to get this update only to see this quote...
VZW sent a message to all Fascinate owners the other night acknowledging the bug and a fix being in the works. Why would they continue to push it out after that?
Sent from my SCH-I500 using XDA App
Well...
0123456789
New EA update is being pushed out.
Verizon told me to go to a store as some phones will not accept OTA updates. Seems stupid and like a lie, but whatever...
Atst44 said:
"VZW pulled the DL09 update due to the e911 bug until it is fixed"
Have any sources on this one? I really would like to see them.
Not doubting you, I have just been rebooting and *228 for 3 days trying to get this update only to see this quote...
Click to expand...
Click to collapse
He's right. Google the source if you need it. Please don't take this response as me being snarky, I don't mean it that way.
I think the biggest issue people are having is not being careful and following the directions perfectly.
I was new two days ago and did this with only one hiccup.
1. I followed the Beginner's thread in this forum to get me rooted. First pass with Odin failed as the one click code didn't recognize the phone. 2nd pas worked. Trick was to just turn on USB debugging and plug in phone, do not then click the mount notification. Leave that off as USB debugging was all that was needed.
2. I installed Mod Manager and Titanium backup right after. This was part of the main directions and Titanium (though not mentioned) allowed me to save all my specific apps that had important data, like my 100% completed Angry Birds.
3. I then followed the directions in the developer forum for the How To.. install DL30 for Froyo. This scared me at first because the CW recovery stalled when wiping data. I waited over 30 minutes before getting the courage to pull the battery and start over. Figured its only deleting user data, should be ok. It was and then it worked the 2nd time without fail. I did reboot in normal recovery, but running the update.zip put it back into CW.
4. After that, I rebooted numerous times, checked all stock apps, upgraded firmware in camera, and used Titanium to add back my apps I bought or downloaded as well as restored my bookmarks and memo notes.
In the end I've had no bugs/issues as others have reported. Only functionality not tested is bluetooth as I don't use it for anything.
I hope this helps and if you are walking through it all again, I would be glad to help specific questions based on my experience.
I was DL09 stock OTA at first. I'd recommend getting rooted and using Odin to get the stock DL09 from these forums flashed before you try to put DL30 on. As a developer myself, it just makes sense to always put on builds that are in order of each other. So DI01, then DL09, then DL30.
0123456789
superchunkwii, thanks for the feedback. When I booted into cwm recovery mode it hung too. I think my fatal mistake was I booted in regular recovery mode and did my wipe....sad. I should have just rebooted and went back in cwm like you did.
As far as freezing apps I did not know freezing angry birds would save its data. Boy was my wife is mad (she plays it the most).
I did everything else on cue so I will try again and see how she goes. IT CAN BE TAUGHT! As the genie says.
On another note I did download the EA28 update today, can I install the DL30 Rom or do I need to "downgrade" to DL09 to get this done? Anyone try?
dlmcclou said:
superchunkwii, thanks for the feedback. When I booted into cwm recovery mode it hung too. I think my fatal mistake was I booted in regular recovery mode and did my wipe....sad. I should have just rebooted and went back in cwm like you did.
As far as freezing apps I did not know freezing angry birds would save its data. Boy was my wife is mad (she plays it the most).
I did everything else on cue so I will try again and see how she goes. IT CAN BE TAUGHT! As the genie says.
On another note I did download the EA28 update today, can I install the DL30 Rom or do I need to "downgrade" to DL09 to get this done? Anyone try?
Click to expand...
Click to collapse
1. Not freeze.. that makes it so app won't run. Backup with Titanium Backup is what you need I think.
2. What is EA28? I don't think the fascinate has had that build.
Just got an update EA28 any ideas what it does
Sent from my SCH-I500 using XDA App
EA28 build is the update to fix the emrgency dialing bug in DL09. As I understand, it is otherwise the same as DL09. I am by no means an expert though.
EA28 build is the update to fix the emrgency dialing bug in DL09. As I understand, it is otherwise the same as DL09. I am by no means an expert though.
Click to expand...
Click to collapse
Cool. Can anyone confirm this?
My brother and I both have a Vibrant. He broke his so I loaned him mine for a week. While he had mine (which I've upgraded to 2.2), he installed Android 2.1 Voodoo 4 on it. Little to say, after rebooting, the phone wasn't booting past the boot screen.
I've now followed some instructions from the forum, and have reflashed my phone with Eugene's non-bricking ROM through Odin. The phone boots up just fine now. However, I am trying to install ROM Manager on the phone, so I can reflash my recovery ROM (non Voodoo) - and the Android market tells me it can't install the app due to not having enough free space - though I have over 1GB.
I am guessing this is because the internal disk is still setup in the Voodoo file system, and just enough space was repartitioned for the OS to go back on.
Can anyone help me restore my phone?
EDIT: I've also tried flashing a different recovery ROM through ODIN (with repartition), which also wouldn't let me get past the bootup screen.
I'm taking a wild guess here, I seriously don't know, but did you click repartition in Odin? I think that's would work, but like I said, I'm not completely sure.
I didn't repartition for the Eugene rom fix (as per the instruction I read), but did when I tried to load another version ontop of that.
I was in the Voodoo chatroom, and was able to get some help. It sounds like I need to download a stock ROM and then reset my file partition to get rid of the EXT4 partition, and reset it all to the default.
I have Eugene's "non bricking" rom, but I don't think that's what I need. Can anyone point me in the right direction of what I need and how to do this?
Just search for the stock Odin images and flash back. They should be in a sticky. I would repartition as well.
I am trying to find a stock version I can ODIN flash. Do you know where I can get one?
http://forum.xda-developers.com/showthread.php?t=848737
I've gone through ODIN, done a reflash to the stock firmware, and repartitioned the phone as well.
Now, when I boot the phone up, I get the T-Mobile screen and the Galaxy S screen, and then the phone goes black (with no lights on) and doesn't go any further. My phone has been sitting on the desk like this for 20 minutes now.
I am wondering if this is like when moving to Voodoo, it takes a while to change the format to EXT4, is the phone having to go back to the default?
I 1am into the same problem with the old voodoo. What you'll need to do is flash back to stock via odin. Ur apps memory will be real low. Flash an old 2.1 voodoo. Let it do its thing once booted put a disable voodoo file into the folder and reboot. It will be ok after that. Hope that makes sense.
Sent from my SGH-T959 using XDA App
this thread might help
http://forum.xda-developers.com/showthread.php?t=848737
fatboy547 said:
I 1am into the same problem with the old voodoo. What you'll need to do is flash back to stock via odin. Ur apps memory will be real low. Flash an old 2.1 voodoo. Let it do its thing once booted put a disable voodoo file into the folder and reboot. It will be ok after that. Hope that makes sense.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Thanks fatboy, but I can't even flash back to stock. The phone won't boot up.