I just extracted the Gentoo Stage3 package for ARM7A and I am playing around trying to get the binaries to run either through terminal emulator or adb shell on my Galaxy Tab running Gingerbread.
I am FULLY aware of how PATH works and all of the normal reasons you would get a "not found" error when trying to run a command, but this one has me stumped.
I tried setting my path to include a subdirectory of /system/bin as follows:
PATH=/system/bin/gentoo:$PATH and gentoo is where I put my gentoo binaries.
When I do which (command) it says:
/system/bin/gentoo/(command)
When I try to run it, it runs the same command from one of the other directories such as /system/xbin (from busybox) instead.
I tried renaming one of the binaries so it has a unique name mv ps wtf I can still do which wtf and get /system/bin/gentoo/wtf
THEN when I try to run it I get wtf: not found.
Obviously the file is there. Even if I go directly to /system/bin/gentoo and do ./wtf I get wtf: not found. If I copy one of the Android system binaries to /system/bin/gentoo/wtf it will run just fine.
Why would I get a not found error for a binary that is obviously there??
I would expect a different error if it wasn't an acceptable binary, so I am lost.
Any ideas?
rustyshack3 said:
I just extracted the Gentoo Stage3 package for ARM7A and I am playing around trying to get the binaries to run either through terminal emulator or adb shell on my Galaxy Tab running Gingerbread.
I am FULLY aware of how PATH works and all of the normal reasons you would get a "not found" error when trying to run a command, but this one has me stumped.
I tried setting my path to include a subdirectory of /system/bin as follows:
PATH=/system/bin/gentoo:$PATH and gentoo is where I put my gentoo binaries.
When I do which (command) it says:
/system/bin/gentoo/(command)
When I try to run it, it runs the same command from one of the other directories such as /system/xbin (from busybox) instead.
I tried renaming one of the binaries so it has a unique name mv ps wtf I can still do which wtf and get /system/bin/gentoo/wtf
THEN when I try to run it I get wtf: not found.
Obviously the file is there. Even if I go directly to /system/bin/gentoo and do ./wtf I get wtf: not found. If I copy one of the Android system binaries to /system/bin/gentoo/wtf it will run just fine.
Why would I get a not found error for a binary that is obviously there??
I would expect a different error if it wasn't an acceptable binary, so I am lost.
Any ideas?
Click to expand...
Click to collapse
Just a guess, but I'd bet that the linker path for the binary is having trouble finding a library.
Related
Hello.
I'm trying to install adb on my tablet so that I might issue adb/fastboot commands to my Android phone.I downloaded this file which is a zip of the platform-tools directory. I put it on my internal memory' but I also tried it from /data/. The problem is that when I enter that directory and enter "adb" I get a permission denied error. OK, so I enter a root shell and try again, only to get a not found error. "./adb" also returns a permission error even from a root shell.
Anyone have any ideas?
You are trying to run an Intel binary on an ARM processor.
Hello,
Veteran SW guy here; but newbie at Android.
I have three tablets. All of them are Ematic Model EGS004. All three were bought for the sole purpose of being used by children to watch educational videos (in mp4 and flv formats) and read PDF documents. Absolutely nothing else. No games. No internet access whatsoever. Etc.
Two of the tablets are still in the box and have not been touched. I'm hoping that they may be useful for making/restoring an original image of the tablets.
To implement the requirements of this project, I did the following to one of the tablets:
1) Used the instructions at http://forum.xda-developers.com/showthread.php?t=2495069 to get root access with Cydia Impactor and Chainfire SuperSU.
2) Installed Titanium Backup (root). Using this, I uninstalled most of the Google applications (excluding Google Play), messager, YouTube, games, etc.
3) Installed File Manager (Explorer) by Rhythm Software.
4) Installed Shell Terminal Emulator by MobilDev. Using the shell, I went to the /system/lib directory and renamed libwifidisplay.so
and libwpa_client.so to libwifidisplay.disabled and libwpa_client.disabled.
Unfortunately, upon reboot, the tablet gets stuck in the bootup screen (with the ematic logo). Obviously, something about Android causes a hang if an expected kernel module is missing...
I tried using the shell in Cydia Impactor. But, the file system was read only. I tried:
mount -o rw,remount /system
But, I get an "Operation not permitted" since I am not root.
I downloaded the ADB bundle for windows at http://developer.android.com/sdk/index.html#download and successfully installed adb on my PC. I could get into a shell with the "adb shell" command. But, the /system/lib directory still is read only and I can't seem to remount it since I am not root.
I tried "adb remount". "Operation not permitted" was the result, again.
Cydia Impactor installs its "su" binary in /system/xbin. I tried running it from there using various invocations like "su -c mount -o rw,remount /system" Each time, the shell hung and I never got a shell prompt afterwards.
Questions:
1) Surely there's a way that I can get back in to rename these files now... I can "ls" them from the adb shell. I can pull them to my PC with adb pull. (adb put doesn't work either since the file system is read only.) Ideas?
2) Once I get this solved, what is the best way to get rid of the wireless capability so that children can never use it? I would like to move videos and PDF's between it and a PC strictly via USB.
3) Is there a way to image/restore one of the untouched tablets - or, for that matter, this one once its up and running like it needs to be?
Thanks everyone!
Jim
Let's try a simpler question since there have been no responses:
Once I get into a shell (non-root) using ADB or Cythia Impactor, I believe I can rename the files if I can only get SuperSU to work. However, when I invoke su, the shell hangs:
su -c ls
su
etc. All of these hang. I assume that SuperSU is waiting for a confirmation from the android display. But, since I'm stuck at the startup screen, there's never an opportunity. How can I get the shell to interact with me as root so that I can remount the file system as RW and rename files?
Thanks,
Jim
rivkah613 said:
Hello,
Veteran SW guy here; but newbie at Android.
I have three tablets. All of them are Ematic Model EGS004. All three were bought for the sole purpose of being used by children to watch educational videos (in mp4 and flv formats) and read PDF documents. Absolutely nothing else. No games. No internet access whatsoever. Etc.
Two of the tablets are still in the box and have not been touched. I'm hoping that they may be useful for making/restoring an original image of the tablets.
To implement the requirements of this project, I did the following to one of the tablets:
1) Used the instructions at http://forum.xda-developers.com/showthread.php?t=2495069 to get root access with Cydia Impactor and Chainfire SuperSU.
2) Installed Titanium Backup (root). Using this, I uninstalled most of the Google applications (excluding Google Play), messager, YouTube, games, etc.
3) Installed File Manager (Explorer) by Rhythm Software.
4) Installed Shell Terminal Emulator by MobilDev. Using the shell, I went to the /system/lib directory and renamed libwifidisplay.so
and libwpa_client.so to libwifidisplay.disabled and libwpa_client.disabled.
Unfortunately, upon reboot, the tablet gets stuck in the bootup screen (with the ematic logo). Obviously, something about Android causes a hang if an expected kernel module is missing...
I tried using the shell in Cydia Impactor. But, the file system was read only. I tried:
mount -o rw,remount /system
But, I get an "Operation not permitted" since I am not root.
I downloaded the ADB bundle for windows at http://developer.android.com/sdk/index.html#download and successfully installed adb on my PC. I could get into a shell with the "adb shell" command. But, the /system/lib directory still is read only and I can't seem to remount it since I am not root.
I tried "adb remount". "Operation not permitted" was the result, again.
Cydia Impactor installs its "su" binary in /system/xbin. I tried running it from there using various invocations like "su -c mount -o rw,remount /system" Each time, the shell hung and I never got a shell prompt afterwards.
Questions:
1) Surely there's a way that I can get back in to rename these files now... I can "ls" them from the adb shell. I can pull them to my PC with adb pull. (adb put doesn't work either since the file system is read only.) Ideas?
2) Once I get this solved, what is the best way to get rid of the wireless capability so that children can never use it? I would like to move videos and PDF's between it and a PC strictly via USB.
3) Is there a way to image/restore one of the untouched tablets - or, for that matter, this one once its up and running like it needs to be?
Thanks everyone!
Jim
Click to expand...
Click to collapse
Erratic Ematic
rivkah613 said:
Let's try a simpler question since there have been no responses:
Once I get into a shell (non-root) using ADB or Cythia Impactor, I believe I can rename the files if I can only get SuperSU to work. However, when I invoke su, the shell hangs:
su -c ls
su
etc. All of these hang. I assume that SuperSU is waiting for a confirmation from the android display. But, since I'm stuck at the startup screen, there's never an opportunity. How can I get the shell to interact with me as root so that I can remount the file system as RW and rename files?
Thanks,
Jim
Click to expand...
Click to collapse
I rooted my son's EGS004, installed busybox, and played around with it without any apparent problem. When I rebooted it, I was prompted to set up the device then and every subsequent time I rebooted it. I could not install any apps and could not redo the Cydia Impactor rooting procedure. The reason was that /data was reporting itself as 0.00B in size. Factory reset didn't change anything. Ematic wants me to return it.
Your issue sounds different, but it could be something as simple as the device being very unforgiving. There's a pinhole with a reset button (never worked for me but tech support suggested it) which may help.
I have been recently messing with a Verizon ellipsis 7, it is rooted and I was trying to install some android 5.0 apps, boot animation, and fonts. Well I got a bootloop so I adb'd in and undid my modifications by pushing my backup of /system. Well that is where I went wrong Im guessing, I know have no access to adb shell, everytime I give that command I get this error
Code:
C:\android-sdk\platform-tools>adb shell
soinfo_link_image(linker.cpp:1635): could not load library "libc.so" needed by "
/system/bin/sh"; caused by load_library(linker.cpp:757): too small to be an ELF
executable: libc.soCANNOT LINK EXECUTABLE
Next I did adb pull /system/lib/libc.so and it is 0k in size. Now here comes the interesting part I did not modify my tablet yet to allow me to run adb in root mode so I cannot push the correct libc.so file to regain access to the adb shell. I am now stuck on the android screen (it is just stuck there not looping) can not run adb logcat because I have no access to shell and cannot push anything to the /system folder because I cannot run adb as root. So what do yall think, am I screwed?
Anyone have any idea?
im in the same mess, i messed with my system directory, got stuck on the verizon screen adb'd a backup but no go. wish i could help.
any idea of how to get root inside factory mode? my backup wasnt rooted
I'm really enjoying remix OS, So much so, I seldom use my windows partition at all any more except for one thing. Bootloader updates and firmware installations on my various android devices. (Most Nexus Player android TV boxes)
Remix shipped with adb support and I have been using it to push bulk installs onto my own and customer devices, I would like to perform the firmware updates as well and found remix does not ship with fastboot installed in system/bin. There is a fastboot file but it is for the Intel 915 graphics support libs.
Is there a way I can add it? been looking at a few pre compiled bin packages for linux but can't seem to get any of them to work correctly. can't seem to get the fastboot.bin to be executable.. even with root.
Any help would be appreciated. Asked the remix folks as I am on the beta program but have not gotten an answer.
Thanks!
MrJinx123 said:
I'm really enjoying remix OS, So much so, I seldom use my windows partition at all any more except for one thing. Bootloader updates and firmware installations on my various android devices. (Most Nexus Player android TV boxes)
Remix shipped with adb support and I have been using it to push bulk installs onto my own and customer devices, I would like to perform the firmware updates as well and found remix does not ship with fastboot installed in system/bin. There is a fastboot file but it is for the Intel 915 graphics support libs.
Is there a way I can add it? been looking at a few pre compiled bin packages for linux but can't seem to get any of them to work correctly. can't seem to get the fastboot.bin to be executable.. even with root.
Any help would be appreciated. Asked the remix folks as I am on the beta program but have not gotten an answer.
Thanks!
Click to expand...
Click to collapse
Try the one here: it's seems to show the help page fine. Haven't checked any of the command though;
alternatively you could compile a version from source
Thanks for the lead
Looking around thru XDA , I found a few fastboot packages that should have worked. My device filesystem is RW and root is obviously present. I copy the file and chmod it as executable but still get access denied trying to execute it as root, Most the versions I found expect you to adb copy it into the device, With remix OS, I'm not sure how to to do that since there is no OTG port. If the filesystem is RW, Should I need to use adb to copy the file in? Looking at compiling a copy since the remix install I'm using is x64 on intel and maybe the fastboot executable needs to be for this specific target?
MrJinx123 said:
Looking around thru XDA , I found a few fastboot packages that should have worked. My device filesystem is RW and root is obviously present. I copy the file and chmod it as executable but still get access denied trying to execute it as root, Most the versions I found expect you to adb copy it into the device, With remix OS, I'm not sure how to to do that since there is no OTG port. If the filesystem is RW, Should I need to use adb to copy the file in? Looking at compiling a copy since the remix install I'm using is x64 on intel and maybe the fastboot executable needs to be for this specific target?
Click to expand...
Click to collapse
Definately at least executes for me; will check tomorrow if it can detect a fastboot device. One from @osm0sis : http://forum.xda-developers.com/showthread.php?t=2239421 also seems to run fine and I think its a different one; some of the others posted are a copy of that first one I posted without giving credit.
Looks like you did point me to the right one.
Since remix OS on a laptop doesn't support an OTG adb transfer... I manually copied adb, adb.bin and fast boot to the system/xbin directory as root.
Then used
chown 0:0 on all 3 files, As found in the included install script (adb shell script)
then chmod +755 (all 3 files) also tried chmod +777
No errors or complaints from the command line..
attempt to execute as user or root, Get permission denied..
"ls" the file shows -rwxrwxrwx root root ?
When I compare against other files in xbin, they all have lrwxrwxrwx. I'm assuming the "l" is a symbolic link pointing to the busybox install.
Am I missing something? that is preventing fastboot from being executable? I don't claim to be a linux expert in any way...
MrJinx123 said:
Since remix OS on a laptop doesn't support an OTG adb transfer... I manually copied adb, adb.bin and fast boot to the system/xbin directory as root.
Then used
chown 0:0 on all 3 files, As found in the included install script (adb shell script)
then chmod +755 (all 3 files) also tried chmod +777
No errors or complaints from the command line..
attempt to execute as user or root, Get permission denied..
"ls" the file shows -rwxrwxrwx root root ?
When I compare against other files in xbin, they all have lrwxrwxrwx. I'm assuming the "l" is a symbolic link pointing to the busybox install.
Am I missing something? that is preventing fastboot from being executable? I don't claim to be a linux expert in any way...
Click to expand...
Click to collapse
adb is already installed (/system/bin/adb); other than that I have it as 777 root:root as well, any chance you have forgotten to execute fastboot as root [su]?
Screenshot attached; and just checked if device detected in fastboot and it is.
NB with adb you might have to use adb -s 0123456789ABCDEF reboot bootloader for example as theres an emulator device running on RemixOS.
Hello,
I own a phone(Model Number ZTE BLADE L5 PLUS) with Android 5.1 lollipop. I am trying to push install a normal apk file which doesn't need any special access. Also, my phone has way more storage space than the size of the apk. When I am trying to install the apk, it looks like it works at first with the message
"1 file pushed" with the speed of pushing the apk.
The real problem happens after a split second. It suddenly says "Error: Unknown command 'install'" and a huge list of commands which all starts with "pm" comes out. I have tried multiple times, from rebooting adb and typing in the path of the apk instead of inserting the name, but it all failed, with exactly the same issue every time. I also searched about the "adb install" command missing, but ended up wasting time only(only solutions for "adb" command not found came out)
I installed adb via Android Studio(Android SDK Platform-Tools), along with the platform suitable for Android 5.1. I didn't download the android emulator though. I hope I could get some help.
Thank You