My superuser app force closed and I had to wipe. Again.

[Daniel Mack]

Lets get get the pleasantries out of the way: Samsung Droid Charge SCH-I510, rooted, running the latest Altered Beast Custom Rom. With the peanutbutter jelly time 0615_charge_overclock kernel. CWM 3.1.0.1

Now its not that big a deal because I finally got titanium backup. (GET IT). Also Launcher Pro is great because it allows you to save your home screen shortcuts and dock. But for the 4th time I was doing the usual messing around with a rooted phone, overclocking, undervolting, trying out root only app killers, and some combination of rooted apps cause my Superuser.apk to force close. This time I was undervolting with voltage control, its the only one that works with my kernel, and had been stress testing it with SetCPU and it stopped working. I know its going to happen again, but everytime I have to factory reset my phone. Now I dont lose root because my cmd ADB shell i have the # symbol. Here's the list of what I've done, probably from most recent to first:

flashed with this guys superuser zip. xda-developers - View Single Post - [APP] Superuser 2.3.6.1 - Now on the Market [2010-09-05]

Followed this guys command lines give or take a chmod: HowTo Get Superuser.apk working VIDEO - Android Forums

I have gone int setting > application > Managing > all > superuser.apk clear data.

I tried wipe cache and dalvik and reboot. Ditto, then reflash my rom and update. and kernel.
I wiped the voltage data since this time that was the last thing I was playing with.

I can't use the terminal emulator because I can't get SU to work. So I didn't play with busybox much.
I dont have any linux experience so I kind of bumble around in cmd.

I redid my original method of rooting minus the gingerbreak upload: Root Samsung Droid Charge of Verizon [Guide] | Android Total

I probably left a method or two out but feel free to point out anything obvious I missed. I would just like to restore the Superuser.apk without having to reset factory data. I foremost directories using the the linux cmds I know best. ls to get a list then cd to go into the directory. I figure theres a directory with some left over data that comes back up. But i figured that xda-developers - View Single Post - [APP] Superuser 2.3.6.1 - Now on the Market [2010-09-05] would of taken care of that. It deleted files before installing itself.

 

[srkmagnus]

Are you backing up the system via recovery before messing with the phone. It doesn't seem like it because it would prevent a factory reset. In recovery, make a backup (called nandroid). Do this at some point before getting too deep in modding the phone so you can just revert back to that time if something goes wrong. It would prevent a wipe and everything will be just as it was when the backup was preformed. Saves a great deal of time.

 

[Daniel Mack]

Are you backing up the system via recovery before messing with the phone. It doesn't seem like it because it would prevent a factory reset. In recovery, make a backup (called nandroid). Do this at some point before getting too deep in modding the phone so you can just revert back to that time if something goes wrong. It would prevent a wipe and everything will be just as it was when the backup was preformed. Saves a great deal of time.

I cant do that because of the CWM + voodoo i'm using. I cant flash a different CWM because its made to work with my kernel.

Since I'm already rooted could I just use ES file manager to copy and move the system file? Think ill try that.

 

[Daniel Mack]

Turns out I was able to make a flash with ROM manager. I clicked create back up of current rom. It shut off, then when it turned back the screen had the android figure holding a warning sign. I had to pull the battery. Then when I turned it on it made the backup. So problem solved perhaps? ill have to wait till the superuser app fails again.

EDIT: I was reading through my kernel forum and it says this just makes a soft brick.