I'm attempting to get webtop from HDMI to work and attempted the install.bat thing but still nothing so I went to
http://forum.xda-developers.com/showpost.php?p=12580345&postcount=634
I can push those files but can not SU in adb shell
I am able to SU in terminal on my phone but not the adb shell
What can I do to get this working? I'm not sure what info you need from my phone to better assist but ask.
I'm running 2.2.2 rooted with gingerbreak I tried to reroot but no go don't think i need too and superuser app is there and works since i use TB and bloat freeze
I just get permission denied thanks for any help. I have googled this but can't find anything.
could you maybe have a problem with ADB itself? Maybe try reinstalling your SDK and setting up ADB again? You said you already tried to re-root and that didnt fix the issue. Maybe someone with more knowledge of ADB could provide more assistance...
I managed to get it working. I noticed when I had my screen set to not turn off i received a message to all access and I granted SU now it works fine.
I have a Motorola Droid X on Android 2.3.3.
Motorola One Click Root goes all the way through and says that the phone should be rooted, but it never is. Here is the alternate method I attempted:
First I used SuperOneClick 2.2 in "Shell Root" mode to get the superuser (#) prompt in adb shell. From there I was able to mount the /system folder for read/write access.
I then copied, "chmodded" and --installed busybox to /system/xbin/.
Next I copied su to /system/bin and changed its permissions to 0755.
Finally, I installed a Superuser.apk
I still get no superuser prompts when I run a root app or type "su" in adb.
What am I missing?
U need to reset your phone and try all over again
Try to wipe/erase the application data of your root app and/or Superuser app, and try again to see if Superuser prompt will popup.
Several days ago, I upgrade ROM of my phone, and restored data and applications, then rooted, but when I type 'su' in Terminal Emulator application, it will wait for a few seconds and failed with "permission denied" error. I use strace to try to figure out why, I noticed that the real UID (10083) of Terminal Emulator application is not as same as the one (10069) send to Superuser. So I wiped the application data and Superuser application data (in fact, I also reinstalled them), then Superuser will prompt when executing 'su' command.
So I don't use adb push/install all that often but since I deleted mobile hotspot on my phone (I thought I had it frozen but apparently I didn't) I cannot upgrade my system.
I am rooted, and have tried installing from an emulator on the phone (and shell) as well as installing from and adb on the PC.
When I try to adb remount I get the following error:
remount failed: Operation not permitted
I have re-rooted thinking that an early version of root wasn't rooted for adb and also hoping that would let me install via shell. How can I get Mobile Hotspot back on?
Ok, so I was able to run a mount from terminal and copy the files and get the upgrade to go through.
So does anyone know why adb remount doesn't work? Is it because of the Moto Blur?
I have searched through lot of posts on xda; able rooted device copied su binary and make root work by sdb shell.
Able to get #prompt on adb shell. But when i install superuser.apk; try to run from UI, i see an error.
"There was an error installing superuser"
What am i missing here. Sorry if a repost. quick help would be appreciated
TIA
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.