gnuroot icon indicating copy to clipboard operation
gnuroot copied to clipboard

GNUroot+wheezyx not working w/o real root

Open Rustarurum opened this issue 10 years ago • 2 comments

Hello World,

am using latest GNUroot on a SGN III, with a fully rooted Alliance ROM. I can't get any(!) terminal program to work, no matter how hard I try, or sudo to execute, w/o a real root. The former always complains about permission/access problems with /dev/pts and the later that sudo (which I installed via apt-get) does not have ownership ID '0' (for "root").

I don't understand why I have to make due with all this nonsense, as I have a rooted phone (like so many others). Unfortunately all the other Linux/Android distros depend on loop'ed solutions, which won't work on my kernel. So for now I'm stuck with GNYroot and wheezyx, but what good is that to me if I can't get somethign as simple as an Xterm started (setuid problems). Always its the same old story about lacking permissions.

Please(!) make a GNUroot for those of us who have rooted phones, so that we may finally be able to use true Linux on our thousand $ devices!

PS: Please don't blame this on PRoot, because even if PRoot is to blame, it doesn't do us users any good. If its broke its broke and we root'ed folks shouldn't even have to rely on such crouches.

Rustarurum avatar Aug 27 '14 08:08 Rustarurum

I have never tried GNURoot on a rooted device. I have never rooted a device. I was under the understanding that there was many working ways to run a linux distro on a rooted phone. Is that not true? GNURoot is trying to provide most the same functionality, but without requiring that you root your device. If it is true that there are many users, with rooted devices, that want to run in GNURoot, but as the real root user of the device, I can look into that for the future.

corbinlc avatar Jan 20 '15 22:01 corbinlc

Hi Rustarurum

Have you gotten any farther with this since you wrote in August? If so can you tell us what changed? I find it curious that having root on the device would in any way interfere with the proot solution, more likely it is something about the root you have installed.

I do hear your frustration, but I think it is a misplaced. I have run linux in a chroot on a variety of rooted android devices for several years. I am new to running GNUroot's proot as I am now trying to produce solutions for those times when a rooted device is not a good option. Neither solution is without it's limitations but it really sounds like your problem is that you have a kernel without loop device support. If you are already rooting your device wouldn't it be a better path to install or build a kernel with loop support on it than to focus on this particular solution not working in your particular case. Solving the loop device issue will likely solve your problem with using one of the existing solutions for running linux in a chroot on a rooted device.

I do hope you found or find a way to get your device to do what you want it to do. To that end I encourage you to try a ROM with more of the features you need.

priestdo avatar Feb 18 '15 21:02 priestdo