I picked up an Archos G9/80 and immediately came here to root it. Instead I wound up installing SDE and flashing Freezenooks G9 Build8 from tis thread: http://forum.xda-developers.com/showthread.php?t=2171742
I just have one problem. I can't get Dropbear SSH II to install. I tried both from the Play store and adb installing it. I even tried the older version. The apk installs fine but it fails to install the service. They both fail during a step where it says its remounting read-only. This is interesting as I notice that the rootfs is mounted read-write by default. From adb shell I tried to force it read-only with mount -o remount,ro but it fails as the Device is busy. I'm guessing this is the same problem that the installer is encountering and since it can't remount rootfs as read-only it proceeds to remove the binaries it's copied over. I've been trying to find out where it copies them before it deletes them. I assume they would be in /system/bin but I can't ever find them there. I gets to the error step way too fast.
Does anyone have any workarounds? Could / should I "borrow" the binaries from another Android box and copy everything to the correct place?
Related
So this is the formula to take apps from phone to sd and vice versa on an eris.
Copy apps from phone to sdcard
cp data/app/* /sdcard/(folder)
Install apps from sdcard to phone
cd sdcard/(folder)
busybox install *.apk /data/app
Is it the same for the thunderbolt? I would do a test and find out, but I don't want to brick my phone by tampering it as it is mounted.
Edit: start with this of course.
adb shell
su
mount -o rw,remount /dev/block/mtdblock3 /system
cd /system/app
That's kind of the long ended way of installing things, but yes, i dont see why that wont work, it's the same filesystem as any other android phone as long as the rom you are using doesnt do something funny.
You could do it via a file explorer gui app on the phone (there's quite a few free ones in the store), terminal emulator on the phone or via ssh if you have an sshserver set up on the phone as well. adb just seems like a pain to me mostly unless im rooting since it involves hooking things up to usb (unless you do wireless adb).
Also, only system dependant apps go in /system/app (stuff you wouldnt uninstall), anything else goes in /data/app
Ok first things first : If you installed some launcher and your touch screen is not responding and you dont have USB debugging enabled then the only way to fix that is to install the original firmware, dload from here : http://www.androidtablets.net/forum...huawei-ideos-s7-slim-official-firmware-4.html check post 35 for the one i used
If you do have debugging enabled the download Superoneclick from below.
The super one click can aslo root the S7 slim and it has adb installed. Unxip it somewhere and go into the \adb folder. Open command prompt from there and run
Adb devices
If it doesnt show your device the either the debugging is not enabled or the right driver is not loaded. (Menu, Settings, Applications, Development, USB Debugging (Yes))
type adb shell
cd\data\app
rm *launcher*.apk
exit
adb reboot
This will remove the launchers thats faulty and touch screen will work again.
If you guys find a clockworkmod that works then leme know here cause i loaded the wrong one and its messed up.
Use psneuter to root and use the adb in the zip for the above
Cia
How to flash Recovery
Reserved for now
Use other Launchers
ADB remount
adb push c:\bluetooth_power.sh /system/etc/
unzip attached file to c:\
Swapping sdcard and sdcard2 around
adb remount
adb push vold.fstab /system/etc/vold.fstab
if you get permission denied error when doing adb remount then try the following instead :
adb push vold.fstab /sdcard/vold.fstab
adb shell
su
mount -o remount rw /system
cp /sdcard/vold.fstab /system/etc/vold.fstab
mount -o remount ro /system
exit
exit
reboot
Copy attached file into ur adb directory (and unzip it has the modified and original file in the zip) and do the above
Grumps said:
adb remount
adb push vold.fstab /system/etc/vold.fstab
if you get permission denied error when doing adb remount then try the following instead :
adb push vold.fstab /sdcard/vold.fstab
adb shell
su
mount -o remount rw /system
cp /sdcard/vold.fstab /system/etc/vold.fstab
mount -o remount ro /system
exit
exit
reboot
Copy attached file into ur adb directory (and unzip it has the modified and original file in the zip) and do the above
Click to expand...
Click to collapse
this works great - - i had a problem where i have not been able to recover my internal SD card - tried everything - even back to original eclair and all - now i just use the external sd (16gb) for everything. No problems with camera recognizing sd card or programs not downloading, etc, etc....
I'll still try to maybe swap out the internal card, or try to get it functional again somehow, but in the meantime, the S7 if again functional.
Rom
Im currently using this rom an dit works perfectly : http://www.androidtablets.net/forum...ical/15812-rom-tri_zet-ideos_s7-slim-mod.html
Only problem i had was updating google maps so i just loaded the new version via .apk manually
O yes If you load that rom and it comes on the first time the screen might not respond (stuck on lockscreen) but its busy loading software in the background. Mine came up on the lock screen saying connect charger although the battery wasnt low so i plugged the charge cable in. It then rebooted after a while and the touch screen is working perfectly.
http://forum.xda-developers.com/showthread.php?t=942166
Grumps said:
Im currently using this rom an dit works perfectly : http://www.androidtablets.net/forum...ical/15812-rom-tri_zet-ideos_s7-slim-mod.html
Only problem i had was updating google maps so i just loaded the new version via .apk manually
O yes If you load that rom and it comes on the first time the screen might not respond (stuck on lockscreen) but its busy loading software in the background. Mine came up on the lock screen saying connect charger although the battery wasnt low so i plugged the charge cable in. It then rebooted after a while and the touch screen is working perfectly.
http://forum.xda-developers.com/showthread.php?t=942166
Click to expand...
Click to collapse
I just got my Slim S7 yesterday, hated the launcher so I replaced it not thinking it would cause such a problem... long story short I tried installing the rom you linked hoping it would fix it(tried everything else) and the touch screen still is unresponsive and USB debugging is now disabled. Any ideas?
phxtravis said:
I just got my Slim S7 yesterday, hated the launcher so I replaced it not thinking it would cause such a problem... long story short I tried installing the rom you linked hoping it would fix it(tried everything else) and the touch screen still is unresponsive and USB debugging is now disabled. Any ideas?
Click to expand...
Click to collapse
well I finally got it working. I ended up doing multiple battery pulls and installed the geeksu recovery, and that's all I did. I'm up and running on that rom. Only thing is thatbi somehow lost root, but that was no biggy.
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?
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'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.