• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root The I borked my SF support group thread

Yeah I know I've been seeing the trend with Voodoo. I just don't have a Windows box handy for the inevitable date with Odin. So I'm delaying :D
 
It's not so bad, never had a prob with the ol' Dirrk lv1200

yeah if ur running a kernel ur happy with then :D

but when you do make the eventual jump from pre november voodoo to mid november nonvoodoo i think you ll notice what we're all talking about :cool:
 
anyone have a solution if you didn't have a voodoo kernel, and even after the odin restore, can't boot into recovery or get to the setup page because of processes force closing? :(
 
yeah if ur running a kernel ur happy with then :D

but when you do make the eventual jump from pre november voodoo to mid november nonvoodoo i think you ll notice what we're all talking about :cool:
Could not have said it better myself jt's11/15uv and now geeknik's own uv are stellar

You guys try jt's 11/15 Voodoo to see if its faster?
Nope squidy you are the last of a dying breed, the voodoo'ers ;)

anyone have a solution if you didn't have a voodoo kernel, and even after the odin restore, can't boot into recovery or get to the setup page because of processes force closing? :(
Im not sure I under the issue but I think this might help. After odin restore, go ahead and re flash recovery tar and after thats do a data wipe and fix permissions that should get to working properly/get rid of FC's
 
Im not sure I under the issue but I think this might help. After odin restore, go ahead and re flash recovery tar and after thats do a data wipe and fix permissions that should get to working properly/get rid of FC's

I tried those things, they didn't do jack squat for it :(
Basically, it boots up to the lockscreen, and when I unlock, it starts displaying FC windows and that's it. I can't get past them, and can't get to the settings to enable debugging to try and re-root it.

EDIT: link for video http://www.youtube.com/watch?v=VaIeDMofp5w
 
I've been there before with the FC thing. You sure you didn't sneak in and record my Fascinate when it was doing that a few weeks ago??? :D

Try making sure the following is in order:

1. Make sure you have a file OR a folder named "disable_lagfix" in your "voodoo" folder on your SD card if you've recently had voodoo on there before, just to be safe. Maybe going through the additional steps many deem necessary for a complete voodoo uninstall might not be a bad idea. I haven't had to go that far yet. Doing the "disable_lagfix" in the voodoo has let me reflash new kernels without very many problems so far.

2. You've probably already done this, but with FC's coming out your phone's nose, it can't hurt to try one more time!! Download a fresh copy of the 300+ meg stock restore file for Odin (along with the other two restore files on this post.)

3. Reinstall the CWM using Odin, again, preferably from a freshly and newly downloaded file just to be on the safe side.

4. Then go in and wipe all the caches, do a factory wipe/reset, and give it another go. Try doing it all in this order and see if it helps at all. I had the endless force close loop for some time, and this process got me out of it. I haven't seen the FC loop happen again since, and that's with several kernel flashes while experimenting with my phone for the best balance between performance and battery life.

5. An additional step that helps some (including myself) that experience Google account and market issues after an Odin restore, is doing a factory wipe in the settings of the phone after it's booted up. For some reason, this got my google account back to working, and I was able to re-root and hit the ground running once again with my phone.

The Fascinate is incredibly resilient, and 90% (or perhaps more) of its horrendously annoying problems and also its incredible potential can either made completely wonderful or completely terrible just by software alone.
 
I've been there before with the FC thing. You sure you didn't sneak in and record my Fascinate when it was doing that a few weeks ago??? :D

Try making sure the following is in order:

1. Make sure you have a file OR a folder named "disable_lagfix" in your "voodoo" folder on your SD card if you've recently had voodoo on there before, just to be safe. Maybe going through the additional steps many deem necessary for a complete voodoo uninstall might not be a bad idea. I haven't had to go that far yet. Doing the "disable_lagfix" in the voodoo has let me reflash new kernels without very many problems so far.

2. You've probably already done this, but with FC's coming out your phone's nose, it can't hurt to try one more time!! Download a fresh copy of the 300+ meg stock restore file for Odin (along with the other two restore files on this post.)

3. Reinstall the CWM using Odin, again, preferably from a freshly and newly downloaded file just to be on the safe side.

4. Then go in and wipe all the caches, do a factory wipe/reset, and give it another go. Try doing it all in this order and see if it helps at all. I had the endless force close loop for some time, and this process got me out of it. I haven't seen the FC loop happen again since, and that's with several kernel flashes while experimenting with my phone for the best balance between performance and battery life.

5. An additional step that helps some (including myself) that experience Google account and market issues after an Odin restore, is doing a factory wipe in the settings of the phone after it's booted up. For some reason, this got my google account back to working, and I was able to re-root and hit the ground running once again with my phone.

The Fascinate is incredibly resilient, and 90% (or perhaps more) of its horrendously annoying problems and also its incredible potential can either made completely wonderful or completely terrible just by software alone.

excellent post SK :)

we've all been down the fc hell before and recovered (well most of us) you defininetly need to completely get rid of everything on the phone. FC hell is a pain but recoverable.

you will need to odin pit/system, kernel, and cwr. make sure you arent pushing standard recovery in odin as well (didnt think you were, but ya never know)

you will need to wipe data and cache in recovery, clockwork recovery as well.

if you have done all these things and still having issues let us know. someone is usually lurking the boards.
 
someone is usually lurking the boards.
owl-orly.jpg


perfect advice between SK and nitsuj17 nothing to add but a pic here
 
Thanks everybody for all of the tips, I genuinely appreciate the input!

Unfortunately for myself and the phone, it never decided to work right, and eventually just stopped responding to anything other than charging. I couldn't get it to power on, nor could I get it into download mode :eek:

Anyhow, went to Verizon last night and got it replaced, which is nothing new to me since technology dies around me (even when I don't mess with the system).
I think I'll just hold off the rooting again until we get Froyo ROMs, but ya never know, I might take the plunge again ;)
 
With the recent release of voodoo5 I suppose I should get housekeeping in here. jt promises no uninstall issues but as we all know ;)
 
With the recent release of voodoo5 I suppose I should get housekeeping in here. jt promises no uninstall issues but as we all know ;)

yes....but........


supercurio seemed to indicate that what was released last night was based on a slightly older version of code which is what is causing cwr issues.

hopefully it gets updated.
 
yes....but........


supercurio seemed to indicate that what was released last night was based on a slightly older version of code which is what is causing cwr issues.

hopefully it gets updated.
saw that :confused: I cant believe jt didnt have the latest and greatest source. he can sc do interact daily, I feel bad for the early bandwagon jumpers, then again it is only cwm which is not working otherwise people did say the phone was flying, someone even said faster than stupidfast
 
saw that :confused: I cant believe jt didnt have the latest and greatest source. he can sc do interact daily, I feel bad for the early bandwagon jumpers, then again it is only cwm which is not working otherwise people did say the phone was flying, someone even said faster than stupidfast

yeah i would have to think voodoo5 is the next evolutionary leap past what we have atm, and i saw it was really fast for others.

the lack of cwr in that version scares even me a bit :o so ill hold off til jt is up later
 
I saw the news about voodoo5 and cwm issues. What was the consensus on resolving it?

i have yet to go looking into the test 1 or test 2 revisions from last night that adryn posted, but the modified test one he did of jts yesterday afternoon solved the cwr issues as apparently previously you needed a 2nd flash to get cwr. adryns threw it all together, so no issues for me...so far
 
I had a little scare this morning attempting to disable voodoo but odin fixed it for me. Already have voodoo installed again.
 
Back
Top Bottom