Root Messed up

sounds like you hit the force close hell a lot of us have had. Did this happen the with the auto-reboot by the root program, or the next time you manually rebooted?

 

give me the step by step on when it first happened. it sounds like it was a voodoo issue not root

 

well i gotta go, hope you get it worked out or someone else here can help you!

 

Yes you can restore to stock if you need to. A more detailed account of exactly what you did and where you are right now is vital for diagnosing your problems. Restoring a voodoo bork might not even be needed in your case, cannot tell based on above info and certainly we dont wanna guide you thru a process you may not need

 

the uninstall voodoo.zip is like a 50/50 success rate. To really insure you remove voodoo before odin back to stock you need to do the full uninstall using adb.

[How to] Completely Remove Voodoo Lagfix - xda-developers

 

Given what appeared wrong with ur phone it didn't seem neccesary to exchange it...,.it wasnt a total brick by any means. Did u at least remove all traces of cwr and odin back to stock before exchanging?

If not there exists the chance (however small) that they pick up that it was a modded device. Its best to never try and return something that can be recovered.

Returning devices only lends support to companies wanting to lockdown their devices more to stop bricking.

I'm glad u have a working phone now but u might be better off taking a step back and relaxing before trying to voodoo again

 

Hi,
I don't mean to take over this thread but I find myself in a similar situation
except I arrived here after trying to mod the framework_res.apk in order to get the circle battery percentage indicator.

I mistakenly renamed and moved the original framework_res.apk with the hopes to just replace it with the new framework... well as soon as I moved the original, it froze and I couldn't replace it with the new .apk so I rebooted

For a while I couldn't past the boot up screen so I tried the
"wipe data/factory reset, wipe cache partition" options, of course with no luck. THEN I used Odin to

1. flash the Clockworkmod
2. installed a new framework_res.apk from a .zip found on a thread the battery indicator mod for the SF
http://androidforums.com/fascinate-all-things-root/192271-battery-percentage.html

Now I can get past boot screen, up the lock screen it's fine. However once unlocked its going into the multiple Fore close screens "com.android phone has stopped....TwLauncher(process.com.sec.android.apptwlauncher) has stopped...etc. etc.

I'm trying to figure out how I should proceed from here. ANY ideas...

THanks!

UPDATE: I tried all the fixes in this link
Odin Restore files to get you to stock - xda-developers
was still getting forced closes. Then I wiped the stock recovery cache. (Thanks to GoBruins for that one)
After that it was still giving me FCs but to a lesser degree and I was able to make it into the "Settings menu" and do a factory reset.

 

Keep the updates coming. Hard to tell if you are golden again yet or not. Sounds like you're getting the hang of it

 

so after the factory reset are you good to go then?

 

Update 2:

Ok so I've had time to play around with my SF post "Force Close" hell and reflashing back to stock. All day today at work it's been pretty solid.

No real issues except I noticed my GPS took Extremely long to acquire position. Now I know many people have complained about this issue, including myself to some extent but NOT this long. It was taking like 5mins, so i finally gave up and d/l GPS STATUS from the market. Ran it (it took <1min) and then re-ran Navigator, and didn't seem to have any new issues.

Otherwise I got off work early so I was able to
1. RE-Root via one click root.
2. Reflashed CWM
3. Backed up Nandroid this time
4. Changed battery indicator to Circle battery indicator (worked this time!)
5. Flashed Dirrk's Voodo LV1200 kernal.
6 Installed Set CPU and have been running at 1200 (conservative)

I had a brief issue right after installing SET CPU where my phone wouldn't wake up from sleep (all i got was a black screen). Did battery pull and haven't been bothered by that since.

All afternoon its been pretty solid. I notice that my battery has discharged somewhat earlier than usual (which is counter to what I'd expect)...BUT i chalked this up to keeping my screen on for much longer than usual. to re-download apps, mess with settings, etc. and making several more phone calls than I usually do. [BTW: I really can't believe just how much making calls drains the batt...is there a "fix" for this? I thought the complaints were that our antennas were actually underpowered?]

So far I think things are looking like they're back to normal with my phone. I'll post anything unusual that might come up.

 

Good stuff Konos. Whenever someones shares their problems and solutions its a great benefit to us all. Also realize for every registered member who may have already gone thru this same thing there is someone unregistered and lurking who found your post on a google search.
Phone calls should drain the battery about 1% every 3-4 minutes. So yeah a 20 minute call should drain you 5-7%. If you are on BT it will be slightly higher. Phone is rated for 7 hours of talk time but as always YMMV

 

Hella, i am a COMPLETE droid noob and the same thing happened to me after trying to install 2.2.1 and now i cant access my phone at all just force close force close.. I have the new epic and it means sooo much to me to have it working... Will anyone help me?

 

ya might want to head over the samsung epic forums...as we dont have that phone

 

(Samsung Galaxy Y) I'm having the same problem. My phone is rooted as well (Withh ChainsDD's version). I was installing a font using root font installer and when it ask me to reboot the system, i did. After rebooted the phone, the twlauncher started giving me the same problems. Can anyone help please?