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.
Related
Okay, my Atrix is rooted and USB Debugging is on, but when I try to remount adb, it says "remount failed: Operation not permitted". Since I can't get adb shell to the # to come up, I type "adb shell su" and I get a Permission denied. I originally rooted with SuperOneClick and enabled sideloading with it and today I rerooted, unrooted, then used DesignGears' new root script to reroot and clean up SuperOneClick's root. Still no adb root access. I have TitaniumBackup, Superuser, and RootExplorer installed and even downloaded Root Checker to check if i really had root. I've spent almost all day looking this up and the closest I've found is the thread that talks about adb showing the device offline with the fix of copying over another adbd to the sbin folder(which I also tried) and adb still doesn't seem to recognize my root. The only time I can get the # prompt is when I do a shell root with SuperOneClick, but that is just a temporary root. Is anyone else experiencing this?
Edit: forgot to mention that adb works fine when I connect my NexusOne, so it's probably not the computer.
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've got a droid razr; rooted, stock rom
I broke the screen accidentally and now the screen isn't showing anything and touch isn't working.
I'd like to recover all the data off my device, but since it's locked, it won't budge. Drives won't mount when I plug it into my PC.
I've got a previous backup which is a little older, but i'm interested in backing up the actual databases (texts, call logs, etc) and system data too, along with my images and personal data.
Is there any way I can perform a whole backup while the system is locked like this?
I've already searched the forum for previous threads with similar issues, but I couldn't find one with a viable solution.
Any help is appreciated, thanks in advance.
Partial Update
Hey all-
I've partially solved my problem.
I was able to get ADB working miraculously. I downloaded the Motorola Device Manager and installed it, also downloaded the Android SDK/Java SDK;
Using the sdk manager i installed the google usb drivers (im not sure it helped any way, but just in case)
after that I ran through the process of adb
Code:
adb kill-server
adb start-server
**plug in device**
adb wait-for-device
adb get-serialno
From there I was able to use "adb shell" and navigate around the file system; used su, went to /data/system/ and did "mv gesture.key gesture.key.bak"
I then restarted my phone and did a repeat of wait-for-device, and get-serialno just to verify the phone was connecting properly.
I then browsed to my computer and amazingly, the drives mounted, my sdcard, and sdcard-ext as removable drives and I was able to view the contents.
-------
So now, I'm stuck here with a device that's NOT locked, I can view my files, and I can navigate the file system.
My end goal is to be able to copy everything from /data/ to /etc/ /system/ /root/ /sdcard*/ /vendor/ /xbin/ and any other system file that's not available through the mounted drives.
I'll keep this thread updated, and if anybody has any help or clue on how I'd do this, it'd be greatly appreciated.
So far I've tried variations on "adb pull" using / as a root dir; trying to find a way to use the shell to invoke scp, ssh, or some other file transfer, but I get no network connection. While in the adb shell and doing any file operations, I get an error stating that it's a read-only file system as well.
Fixed
I just wanted to let you all know that I've resolved my problem.
Let me state the issue again.
- Screen and touch broke.
- Device locked with pattern
- Rooted
- ICS - Stock Verizon ROM
- USB Mode was UMC, not PTP/MTP
- USB Debugging enabled
I used ADB to delete /data/system/gesture.key and rebooted, effectively removing the device lock, and allowing drives & data on my SD cards to show up in explorer after a reboot of the phone.
After futzing around for a bit, I realized the phone was tied to my Google account, and I remotely installed "Droid VNC Server" (app name org.onaips.vnc)
From there I found a way to activate the VNC server through the ADB command line
Source: android.stackexchange.com/a/31957
Code:
Application located in
/data/data/org.onaips.vnc/files
With a root shell, run this
chmod 766 /data/data/org.onaips.vnc/files/androidvncserver
Then you can execute the vnc server from the command line
/data/data/org.onaips.vnc/files/androidvncserver
Run this to forward the port
adb.exe forward tcp:5901 tcp:5901
On your VNC client, connect to localhost:5901
From there I was able to get access to my home screen and pulled the notification drop down and changed from USB Mass Storage to Camera/Media Mode
Rebooted the phone, started the vnc server again, connected to it and moved some files around to my SD Card
In another adb shell as root, I was able to copy files from /data/data/ (or anywhere else I wanted) and write them to anywhere on /sdcard-ext/
From there in another command shell, I ran adb pull /sdcard-ext/datafolderfile
=========================================================================
I believe this to be the overall gist of things, though I ran into hiccups along the way, while I was messing around, I changed some permissions which caused my su executable to break and only be allowed to run shortly after booting the phone; and also because of the broken screen, something would cause the phone to reboot every so often, breaking my connections, backups, file transfers, and etc
There's also a cool option in adb
Run
"adb backup" and it'll give you all the switches, you'll have to confirm the backup on your phone, so be sure to be running VNC and confirm it, but adb backup should be able to grab everything you need. Like I said it didn't work for me because my phone would reboot;
I hope everybody that sees this can benefit from it
Annafunny said:
So did you extract your data from your Razr with adb finally?
Click to expand...
Click to collapse
This thread is really old (4 years)... and the answer was provided.
To avoid further issues, closed.
I bricked my Kindle hdx 7" and am looking for help. i JUST COULDN'T LEAVE IT ALONE. rooted wth towelroot, rolled back to 13.2.2.8, Safestrap, Nexus 1.02 for safestrap on rom slot 1. Could not get instant video, so attempted update to 13.4.5.2 to see if that would work. Realized I forgot to backup like I am supposed to do and stopped update. After no boot it went to stock recovery and I did a factory reset, just like everyone says not to do, and now I am in bootloop. Gray Kindle Fire logo for about 45 seconds, then black screen for about 45 seconds. I can communicate throught abd, but I don't know what to enter. I have found TUT from r3pwn which seems really helpful, I just cannot use keyboard fast enough to get it in,(nerve damage from brain tumor). I have seen at some point that I should get into fastboot mode, I can do that, I just don't have Windows drivers. I have been all around XDA and cannot remember where I saw things. can someone point me in the right direction? Thank you.
It took a while, but, accomplished it with help from @Davey126, reading posts from @draxie, @ONYXis, @EncryptedCurse and others. Too many to list.
Fastboot mode is useless to you anyways, as you haven't unlocked the bootloader.
The important thing is that you still have ADB access. If you can't enter the commands in time, just make a batch script to do it for you.
Code:
adb wait-for-device
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
chmod 0777 /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /cache/kindleupdate.bin
adb reboot recovery
As far as I know, you only need to add adb wait-for-device before it tries to run any of the other commands.
Save the above code as .bat in your text editor of choice (i.e. Notepad). Remember to change the local path (in the second to last line) to wherever the .bin is on your computer.
EncryptedCurse said:
Fastboot mode is useless to you anyways, as you haven't unlocked the bootloader.
The important thing is that you still have ADB access. If you can't enter the commands in time, just make a batch script to do it for you.
Code:
adb wait-for-device
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
chmod 0777 /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /cache/kindleupdate.bin
adb reboot recovery
As far as I know, you only need to add adb wait-for-device before it tries to run any of the other commands.
Save the above code as .bat in your text editor of choice (i.e. Notepad). Remember to change the local path (in the second to last line) to wherever the .bin is on your computer.
Click to expand...
Click to collapse
Thank you for your help, I will do this after work.
I couldn't connect with adb on laptop, connected today and batch file stops.
adb wait-for-device
adb shell
[email protected]:/ $
Then when kindle powers off for boot loop, cmd window exits.
Any ideas?
my new batch file and logcat. is it hopeless, or more to come on learning adb?
notjoken958 said:
It took a while, but, accomplished it with help from @Davey126, reading posts from @draxie, @ONYXis, @EncryptedCurse and others. Too many to list.
Click to expand...
Click to collapse
Glad you got it working. Like most complex device recovery efforts it take a lot of reading/filtering and trial/error/retries before being rewarded with meaningful successes. As you probably learned each journey is a little different; almost impossible to develop step-by-step recovery guide that wouldn't eventually have dozens of amendments covering 'special circumstances'. Enjoy your revived HDX!