Root root access broke cause of busybox??

[nitestalkr]

My root broke all the sudden...
While trying to change busybox version, I lost root access. I've restarted my phone, and still have no root access... any ideas? (Other than the obvious, re-root)

 

[bigsupersquid]

you can still get root through your custom recovery (adb shell) to fix whatever's wrong in /system

 

[nitestalkr]

and how would i go about doing that? im still kinda a noob in some areas..

 

[bigsupersquid]

try root checker from market to verify it's unrooted. maybe busybox installer would help unless that's what messed up.
use gingerbreak app from xda to root again if it's unrooted.

 

[nitestalkr]

Results from root checker:

Root Access is not properly configured or was not granted.

Superuser.apk - com.noshufou.android.su - version 3.0.6 is installed!

System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin

The adb binary is set to default shell user access as root

Standard su binary location: ls -l /system/bin/su:
lrwxrwxrwx 1 0 0 19 Oct 31 12:15 /system/bin/su -> /system/bin/busybox

Standard su binary location: ls -l /system/xbin/su:
-rwsr-sr-x 1 0 0 22236 Aug 1 2008 /system/xbin/su

Alternate su binary location:
ls: /sbin/su: Permission denied

Alternate su type binary location:
ls: /system/xbin/sudo: No such file or directory

SU binary not found or not operating properly

Results provided on your LG-VM670 device by Root Checker version 3.9 from joeykrim in the Android Market - http://goo.gl/GgWae

 

[nitestalkr]

And I tried gingerbreak last night.. it took a while, and I fell asleep, no change, tried superoneclick Monday morning, and took about an hour to get to step 7 (very unusual, whole process shouldn't last longer than 10-15 minutes if not less) so I stopped it cause I was on a strict time schedule. I'm pretty much dumb founded at this point.

 

[bigsupersquid]

get a current copy of su (pull it from an iho zip)
boot into recovery
mounts and storage>mount system
adb push su to the locations you listed in the previous post
adb shell chmod 4755 /path/to/su for each location you pushed to.
reboot.

 

[nitestalkr]

I pushed to all locations listed, and did the chmod, and that still didnt work.
In gingerbreak, i tried the "unroot" feature, and i get an error saying;

GingerBreak
------------
Failed to remount /system as read/write!

and when i try to root, it says:
! Sorry!
-----------
The application GingerBreak (process eu.chainfire.gingerbreak) has stopped unexpectedly. Please Try again.

 

[bigsupersquid]

ok, here's an easy one.
use recovery to restore your last nandroid backup from before the issue happened.
that will fix it.
or, if you didn't have a backup, just reflash the rom.
that will also fix it.

 

[nitestalkr]

well in that case, il just flash the newest build of BACKside. hopefully this will fix it.

 

[bigsupersquid]

it should. since you can adb push to /system in recovery, there shouldn't be any problems.

I don't know why I didn't remember that overwriting the rom should fix your problem.

 

[nitestalkr]

yup, that worked perfectly fine. ha, of course the simplest way to fix it would be the last thing to try xD
thanks for your help!