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

Root How to fix permissions on files with Busybox (Without using ROM Manager)

droidzone

droidzone

Android Enthusiast
After trying and trying, I finally got Busybox successfully installed in the /system/bin of my rooted (Unrevoked 3) Desire running Clockworkmod and Neophyte TSense.

The reason I installed Busybox was because ROM Manager could use it to fix permissions on files so that less "Andoid.process.acore has stopped unexpectedly" errors would pop up.

But ROM Manager still gives me the stock "An error occured while trying to run privileged commands!" error.

Does anyone know how to fix this, or alternately if there is a script which can use Busybox to fix permissions on my files without using RomManager?
 
danfrance said:
have you tried clearing data and cache on superuser permissions app?
Click to expand...

Yup. Tried it just now. I tried deleting data rom Settings>Applications. (Cache was zero). It didnt work.

So rebooted to recovery, wiped the whole cache partition, tried again. Still no deal.. :(
 
I read of a batch script which Cyanogen has incorporated into one his ROMS. Tried it but even that didnt help. But Cynogen's .sh which he originally had posted had a bad link so probably I wasn't using the right one.

I've tried ROM Manager>Fix Permissions in a Cyanogen ROM, and it's always done the job. A series of command line operations are executed, which fixes permissions. In this case however on a Neophyte, ROM Manager just says "An error occured while trying to run privileged commands!", which implies that somehow permissions aren't correct for it, or that its batch script runs into trouble while running (which may be because of lack of busybox/problem with busybox).

I've verified that busybox is indeed properly installed into /system/bin. The path too is correct, since invoking busybox from any command line brings up its options.

So what else could be the problem.
Superuser app has granted ROM Manager root privs, since it does seem to be able to boot to recovery rom direct from App. But I've previously had problems with the "Download ROM" option, while it automatically installs. It fails at the signature prompt, though I've toggled signature verification off.
 
It would be easier to find out the problem if the batch script used by ROM Manager itself could be downloaded and applied at a command prompt, since I could see which line the problem starts at.

But I cant find that script anywhere.
 
Cache partition isn't related to app caches. Wiping the cache partition is usually a waste of time.

Busybox shouldn't be in /system/bin for one thing...
 
I'd initially tried installing it in /system/xbin. It didn't seem to work, so I put it here. I found it odd that the app cache of superuser was 0. That's why I erased cache partn.

Do u think having busybox where it is now, might create a problem?
 
Busybox should be in /system/xbin.

I'm not certain why you're having to install it. Every custom ROM comes with it.
 
You shouldn't ever have to install busybox on a rooted phone (unless you're building your own ROM). It's essential for too many things that require root.
 
teppic74 said:
You shouldn't ever have to install busybox on a rooted phone (unless you're building your own ROM). It's essential for too many things that require root.
Click to expand...

I agree, and installation of Busybox wasnt exactly a No-Brainer. But now that it is installed, I want to fix permissions using it, and cannot since ROM Manager is sulking. I can't manually issue thousands of busybox commands and fix permissions.

I guess I'll have to wait till someone who has a similiar problem comes up/finds a solution.
 
If there's no Busybox scripts around, is there at least an alternative to ROM Manager that allows me to fix permissions?
 
You must log in or register to reply here.
Back
Top Bottom