Will not launch on android 5.1

[priestdo]

I was happily running gnuroot with a wheezy instance on an android 5.0.4 nexus 5. Yesterday the device upgraded to android 5.1 and now I am unable to launch a rootfs. I have removed and re-installed gnuroot and wheezy, also tried gentoo to see if it was a wheezy issue, it is not. I have removed and cleared all cache and then re-installed gnuroot as well, same results.

I can create a new rootfs. At least it seems to do it and then the option to launch that rootfs is there. But if I try to launch it, with or without fake root, the terminal comes up for a second and then I am back at the home screen. There is no usable output on that terminal when it comes up.

Outside of gnuroot Jackpal terminal still runs fine.

I have also tried moving around the system both in an adb shell and in jackpal, but that is of limited usefulness as the device is not rooted.

Is there anything I should try or capture on this non-rooted device that would help debug the problem?

[priestdo]

I now have a userdebug 5.1 device as well. So, while it does not have a working way to become root while on the device, I can get a root adb shell.

So, I can confirm that /data/data/champion.gnuroot/app_install/support/wheezy/proot is there, and that /data/data/champion.gnuroot/app_install/rootfs/wheezy was created and populated. But on this device as well, I cannot launch it.

However, with this device I can look at or examine logs and the filesystem, so if there is something you would like me to check, try or capture, let me know.

[corbinlc]

What devices do you have? Are you using a custom ROM? I have these known android version or device specific issues:

1. newer builds of cyanogenmod are not working. Known solution in next release
2. newer android versions don't work for xperia devices. Known solution in next release.
3. newer android versions don't work on Nexus 4 (other nexus devices fine). Unknown cause. Some experimenting done.

[priestdo]

The devices I have that stopped working are a nexus5 running stock android 5.1 build LMY47D and a 2013 nexus7 running android 5.1, a userdebug build so I could become root in an adb shell and look around. They are both running versions of the 3.4.0 kernel from google.

I didn't mean to post twice, sorry. On Mar 5, 2015 3:42 PM, "corbinlc" [email protected] wrote:

What devices do you have? Are you using a custom ROM? I have these known android version or device specific issues:

1. newer builds of cyanogenmod are not working. Known solution in next release
2. newer android versions don't work for xperia devices. Known solution in next release.
3. newer android versions don't work on Nexus 4 (other nexus devices fine). Unknown cause. Some experimenting done.

— Reply to this email directly or view it on GitHub https://github.com/corbinlc/gnuroot/issues/51#issuecomment-77476914.

[corbinlc]

Can you check if my octave app (https://play.google.com/store/apps/details?id=com.octave) works for you? If so, then the next changes to GNURoot will probably solve this.

[priestdo]

I just tried installing octave. It installed successfully but on launch it also opens the terminal and before I can see what is on the terminal display, it dies and I am back at the android home screen. So, that is not working.

If a logcat or bugreport would be usefull, let me know. On Mar 6, 2015 17:04, "corbinlc" [email protected] wrote:

Can you check if my octave app ( https://play.google.com/store/apps/details?id=com.octave) works for you? If so, then the next changes to GNURoot will probably solve this.

— Reply to this email directly or view it on GitHub https://github.com/corbinlc/gnuroot/issues/51#issuecomment-77663173.

[tapirbait]

Hi,

I have the same issue since upgrading to 5.1 on an ARM Nexus 7. I just tried to run proot 'by hand' from /data/data/champion.gnuroot/app_install/support/wheezy/proot but it did not work. I can't even enter the directory. On the other hand, I can run binaries from Burrows Busybox app fine, though they reside in the corresponding app data directory as well.
So I thought this may be a permission issue?

 $ ls /data/data/burrows.apps.busybox/app_busybox
<lists directory..., contained busybox binaries are runnable as well>
 $ ls /data/data/champion.gnuroot/app_install
opendir failed, Permission denied
 $ ls /data/data/champion.gnuroot/app_install/support/wheezy/proot
/data/data/champion.gnuroot/app_install/support/wheezy/proot: Permission denied
 $ /data/data/champion.gnuroot/app_install/support/wheezy/proot
/system/bin/sh: /data/data/champion.gnuroot/app_install/support/wheezy/proot: not found
 $

[priestdo]

I have found that wheezy and fedora will not launch but gentoo will still launch on those same devices. Nexus 10 continues to work fine, nexus 5 will not run wheezy. On May 1, 2015 5:38 AM, "tapirbait" [email protected] wrote:

Hi,

I have the same issue since upgrading to 5.1 on an ARM Nexus 7. I just tried to run proot 'by hand' from /data/data/champion.gnuroot/app_install/support/wheezy/proot but it did not work. I can't even enter the directory. On the other hand, I can run binaries from Burrows Busybox app fine, though they reside in the corresponding app data directory as well.

So I thought this may be a permission issue?

$ ls /data/data/burrows.apps.busybox/app_busybox <lists directory..., contained busybox binaries are runnable as well> $ ls /data/data/champion.gnuroot/app_install opendir failed, Permission denied $ ls /data/data/champion.gnuroot/app_install/support/wheezy/proot /data/data/champion.gnuroot/app_install/support/wheezy/proot: Permission denied $ /data/data/champion.gnuroot/app_install/support/wheezy/proot /system/bin/sh: /data/data/champion.gnuroot/app_install/support/wheezy/proot: not found $

— Reply to this email directly or view it on GitHub https://github.com/corbinlc/gnuroot/issues/51#issuecomment-98124553.

[tapirbait]

True story! I just installed gentoo and it works.
Still wheezy and arch don't work. In aboriginal, I get a >-prompt and whatever I enter on that prompt, it quits immediately after hitting return.

[davidmegginson]

I can confirm — Wheezy terminal crashes and disappears immediately on 5.1.1 (32GB 2013 Nexus 7, rooted but stock). Was working fine with 5.0.2 on the same device.

[cb125]

I have tried Wheezy on a Nexus 5, a Nexus 7, and a Nexus 10, all running 5.1.1, and a Tab S running Cyanogenmod 12.1, and it crashes instantly every time. In addition, Gnuroot Debian also doesn't work on any of these machines--the installer never finishes untarring.

[python-b5]

Hey I want GNURoot Debian but it gets stuck on Installing tar file for GNURoot debian Any help???

[ckuethe]

Me too. Also on running rooted stock 5.1.1 on 32GB 2013 N7

[tifabio]

Me too. Running non rooted stock 5.1.1 on 16GB Nexus 5 (Version LMY48B). Wheezy terminal crashes and disappears immediately. Was working fine with 5.0.2 on the same device.

[RuddeK]

I dunno what is the problem for you as my Xiaomi mi3 running stock android 5.1.1-r2 works fine with gnuroot. I haven't rooted my phone and I use Debian Wheezy (although with Jessie repos nowdays).

[cb125]

Yeah, the bug is super dependent on the specific hardware platform. Nexus 10 works fine, but the nexus 7 2013 doesn't work even with 5.1.1r6 (build LMY48G).

[corbinlc]

Hey everyone. Thanks for chiming in. I have been seeing your comments, but haven't had anything to add. I have been trying to get through some other GNURoot work, before tackling this. That release looks like it is close to being ready and then this will be my #1 priority for GNURoot, as it is obviously awful that it doesn't work on 5.1 for many devices. One really good point of news, is I now have a device that shows this issue so, hopefully, I will be able to progress quickly when I get started on this.

I don't know the cause of the problem. This is what I know so far... It primarily effects devices running 5.1, but not all devices running 5.1. The Nexus 4 shows a similar issue, but it showed up on 5.0. It is effected by how PRoot is built and how the programs running in the PRooted environment are built.

When I first saw this issue, I thought it might be related to the planned restriction to only allow PIE executables on 5.1, but that restriction got nixed. Is there some piece of it that remains? Not sure.

I will be working with GNURoot Debian to solve this. GNURoot Debian is fully open sourced, so maybe some of you can work on this too. I will post progress when I get going on this.

If anyone wants, they can start googling for similar issues with other apps. That often helps with these device or android version specific issues.

Thanks, Corbin

[corbinlc]

Can you all try GNURoot Debian ( https://play.google.com/store/apps/details?id=com.gnuroot.debian )? GNURoot Debian is taking the place of GNURoot Wheezy very soon and GNURoot WheezyX shortly after. It should now work on devices running 5.1. File issues against GNURoot Debian here: https://github.com/corbinlc/GNURootDebian/issues

[cb125]

Looks good on nexus 5 and on nexus 7 2013, both running 5.1+.

Thanks!

[priestdo]

YES! GNURoot Debian does launch on my Nexus 5. I have not yet gone through the entire setup I was doing before to get emacspeak working. I hope to try that tonight. Thanks! Greg

On Wed, Jul 22, 2015 at 12:17 PM, cb125 [email protected] wrote:

Looks good on nexus 5 and on nexus 7 2013, both running 5.1+.

Thanks!

— Reply to this email directly or view it on GitHub https://github.com/corbinlc/gnuroot/issues/51#issuecomment-123831755.

[tifabio]

Works for me too. Thanks!

[ckuethe]

LGTM

[kurokirasama]

hi, i'm having this issue with gnu root debian on android 5.1... any fix?

[priestdo]

Have you tried the version at the site listed a message from corbinic date July 22 2015 That is what solved it for us. Greg

On May 25, 2017 21:01, "kurokirasama" [email protected] wrote:

hi, i'm having this issue with gnu root debian on android 5.1... any fix?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/corbinlc/gnuroot/issues/51#issuecomment-304185308, or mute the thread https://github.com/notifications/unsubscribe-auth/AKUZvlHNWBgu1DquLbAtpEg0TfO2PFgBks5r9k6VgaJpZM4Dpjrl .

[kurokirasama]

that's the one i tried... heading to the corresponding page to ask now. Thanks!

[vuahackervn]

I also run GNUroot Debian. But it can not open ip address for minecraft server pe. Who is the Deity of Debian? Then show me how to open ip address sever. Best regards