Timeline for Reason for chroot failure: tmp-mksh: chroot: not found
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 8, 2016 at 19:01 | history | edited | goulashsoup | CC BY-SA 3.0 |
deleted 1 character in body
|
| Jul 8, 2016 at 9:02 | vote | accept | goulashsoup | ||
| Jul 6, 2016 at 12:44 | answer | added | goulashsoup | timeline score: 2 | |
| Jul 5, 2016 at 8:38 | comment | added | Grimoire | It appears that we're going outside the scope of your question, which concerned only chroot. | |
| Jul 5, 2016 at 8:31 | comment | added | goulashsoup |
type sh refers sh is tracked alias for /system/bin/sh, but like I stated before it says No such file or directory
|
|
| Jul 5, 2016 at 8:25 | comment | added | Grimoire |
As before, issue type sh: this will tell you the location of the shell binary, which you'll need to replace any instance of /bin/bash with.
|
|
| Jul 5, 2016 at 8:04 | comment | added | goulashsoup |
Thanks. I am a step forward. Now type chroot refers chroot is /system/xbin/chroot. But now I get the error chroot: cant execute '/bin/bash': No such file or directory or for /system/bin/sh chroot: cant execute '/system/bin/sh': No such file or directory. Well I checked the /system/bin/sh file. Like it is stated in this post it is exisiting
|
|
| Jul 5, 2016 at 7:33 | comment | added | Grimoire |
First and foremost, I said type, with one and only argument for it, which was chroot. Aside from that, you may need to install BusyBox, in order to be able to use chroot, since your device lacks it.
|
|
| Jul 5, 2016 at 7:20 | comment | added | goulashsoup |
So I tried type chroot /data/local/mnt /bin/bash. Result (error): 1. chroot not found, 2. /data/local/mnt not found (but it exists), 3. /bin/bash not found. I tried type chroot /data/local/mnt /system/bin/sh. Result (error): 1. same, 2. same, 3. /system/bin/sh is /system/bin/sh.... The results for whence -v chroot are equivalent.
|
|
| Jul 5, 2016 at 6:56 | comment | added | Grimoire |
Try issuing type chroot or whence -v chroot, and tell us the result.
|
|
| Jul 4, 2016 at 20:53 | history | asked | goulashsoup | CC BY-SA 3.0 |