The A100 ships with acer/vg_gen2/vangogh:3.2/HTJ85B/1311401634:user/release-keys . Its copy of /system/bin/vold includes a fix for GingerBreak, so that exploit won't work.
I also tried the iconiaroot-1.3.apk but it did not work either. Logcat says 'E/CMD_SERVER( 102): cmd_server: invalid argument !'. They apparently "fixed" the bug by scanning the input command for semicolons. But you can still use backticks to inject commands!
So until sc2k releases a new iconiaroot-1.4.apk, this should work:
Steps to get root (LINUX VERSION):
0. put your favorite su binary in /mnt/sdcard/su
1. adb shell /system/bin/cmdclient ec_micswitch '\`mount -o remount,rw /system\`'
2. adb shell /system/bin/cmdclient ec_micswitch '\`cat /mnt/sdcard/su >/system/xbin/su\`'
3. adb shell /system/bin/cmdclient ec_micswitch '\`chmod 6755 /system/xbin/su\`'
Steps to get root (WINDOWS VERSION, just the same minus the backslashes):
0. put your favorite su binary in /mnt/sdcard/su
1. adb shell /system/bin/cmdclient ec_micswitch '`mount -o remount,rw /system`'
2. adb shell /system/bin/cmdclient ec_micswitch '`cat /mnt/sdcard/su >/system/xbin/su`'
3. adb shell /system/bin/cmdclient ec_micswitch '`chmod 6755 /system/xbin/su`'
Note that this just gives you a working "su". Installing SuperUser.apk or whatever frontend you like is left as an exercise to the reader.
I will probably release a new version of iconiaroot tonight.
So do you have the A100? I have been looking for some info on it. Mainly on if it comes with a GPS or not. There doesn't seem to be an official spec list anywhere.
Thread Moved.
Yes, it has GPS.
And yes, I have one. Importantly, though some spec sheets list USB charging, I have not gotten it to work yet.
omg, thank you sooo much for the info. I have been hunting everywhere for the answer.
Lightspeed
I can't wait until the Lightspeed ROM is made available for the A100.
Does anyone know if someone is working on that?
Here's hoping that someone ports this devices' 3.2 image/ROM to A500.
tried this. I can see the superuser app installed but root is not working.
adb shell > su yields permission denied.
clubtech said:
tried this. I can see the superuser app installed but root is not working.
adb shell > su yields permission denied.
Click to expand...
Click to collapse
What does "adb shell ls -l /system/xbin/su" say?
It says no such file or directory.
It does not seem to copy su from the sdcard.
Also adb shell /system/bin/cmdclient ec_micswitch '\`mount -o remount,rw /system\`' does not seem to put the system in RW mode.
I really dont know how the superuser app displays under my apps though if it didnt copy su.
Some more info:
When running the commands from your initial post, it fails on:
2. adb shell /system/bin/cmdclient ec_micswitch '\`cat /mnt/sdcard/su >/system/xbin/su\`'
The error is The system cannot find the path specified.
However if i login to a shell session via adb shell first and then run "/system/bin/cmdclient ec_micswitch '\`cat /mnt/sdcard/su >/system/xbin/su\`' " it does not fail, but it also does nothing. i can't find su under /system/xbin
usb host
sorry for such a question in a rooting thread, but it is actually as interresting as the GPS "confusion". Does the A100 have USB host capabilities? And if not, would it be possible to get such functionality working? Maybe an A500 port would help in this matter, as it has a full blown USB?
A100 == A500 + time
jgal said:
Does the A100 have USB host capabilities? And if not, would it be possible to get such functionality working? Maybe an A500 port would help in this matter, as it has a full blown USB?
Click to expand...
Click to collapse
The A100 is a scaled down (physically, not electronically) version of the A500 with a different starting version of the OS (3.2 instead of 3.1). Although the A500 and A100 have both been rooted, the source code for Honeycomb has not been released to the public so we cannot expect fully custom ROMs such as Cyanogen for the A500/A100.
However, what can be done after rooting is the installation of additional kernel modules and configuration files to enable additional functionality. The hardware on the A100 is capable of USB host (as it is on the A500) but needs one of these kernel modules and some configuration changes to get it working.
We should be able to achieve everything that has been accomplished with the A500 (including support for external USB modems!) but we may not be able to directly use the solutions that were developed for the A500 because of the differences in the starting point.
For examples of what has been done with the A500 (and therefore should be doable with the A100 now that root has been achieved) google for "A500 ROM list". Developers have made flashable images with the kernel modules and configuration changes built right in to one handy dandy image. One such all-in-one solution is http://forum.xda-developers.com/archive/index.php/t-1188253.html
((RayDar)) said:
The A100 is a scaled down (physically, not electronically) version of the A500 with a different starting version of the OS (3.2 instead of 3.1). Although the A500 and A100 have both been rooted, the source code for Honeycomb has not been released to the public so we cannot expect fully custom ROMs such as Cyanogen for the A500/A100.
However, what can be done after rooting is the installation of additional kernel modules and configuration files to enable additional functionality. The hardware on the A100 is capable of USB host (as it is on the A500) but needs one of these kernel modules and some configuration changes to get it working.
We should be able to achieve everything that has been accomplished with the A500 (including support for external USB modems!) but we may not be able to directly use the solutions that were developed for the A500 because of the differences in the starting point.
For examples of what has been done with the A500 (and therefore should be doable with the A100 now that root has been achieved) google for "A500 ROM list". Developers have made flashable images with the kernel modules and configuration changes built right in to one handy dandy image. One such all-in-one solution is http://forum.xda-developers.com/archive/index.php/t-1188253.html
Click to expand...
Click to collapse
Maybe i missed this but where do you see the A100 has been rooted? The topic of this specific post is confusing as it does not work. i have tried it and while you do see superuser installed, you don't have root access.
So unless i missed something, i don't think the A100 has been rooted yet.
clubtech said:
Maybe i missed this but where do you see the A100 has been rooted?
Click to expand...
Click to collapse
From the first two posts in this thread:
abliss said:
So until sc2k releases a new iconiaroot-1.4.apk, you can try this:
Steps to get root:
0. put your favorite su binary in /mnt/sdcard/su
1. adb shell /system/bin/cmdclient ec_micswitch '\`mount -o remount,rw /system\`'
2. adb shell /system/bin/cmdclient ec_micswitch '\`cat /mnt/sdcard/su >/system/xbin/su\`'
3. adb shell /system/bin/cmdclient ec_micswitch '\`chmod 6755 /system/xbin/su\`'
Click to expand...
Click to collapse
And:
sc2k said:
I will probably release a new version of iconiaroot tonight.
Click to expand...
Click to collapse
It seemed to me that root on the A100 had been achieved -- especially since "ROOTED" is in the title of this thread.
If not, then my post should say "Although the A500 has been rooted and one day the A100 will be as well, ...".
Yes, sadly the above commands don't really work (at least not for me).
They don't mount the system as RW and su never gets copied over to /system/xbin
Hoping that someone can figure this out.
sc2k said:
I will probably release a new version of iconiaroot tonight.
Click to expand...
Click to collapse
Hello. Have you released a new version of iconia root yet? Il looked on your "how to root hc3.1" and did not see an update supporting the a100.
We all greatly appreciate the effort put forth.
id love to root this as I am unable to mount system as rw too.
clubtech said:
Some more info:
When running the commands from your initial post, it fails on:
2. adb shell /system/bin/cmdclient ec_micswitch '\`cat /mnt/sdcard/su >/system/xbin/su\`'
The error is The system cannot find the path specified.
However if i login to a shell session via adb shell first and then run "/system/bin/cmdclient ec_micswitch '\`cat /mnt/sdcard/su >/system/xbin/su\`' " it does not fail, but it also does nothing. i can't find su under /system/xbin
Click to expand...
Click to collapse
What do these command say?
1. adb shell ls -l /system/bin/cmd*
2. adb shell ls -l /mnt/sdcard/su
3. adb shell getprop ro.build.fingerprint
Related
I do most of my hacking from work. I am uncomfortable installing drivers for adb and such on a PC that i am not admin.
So I tried
su
mount -o remount,rw /dev/block/mtdblock3 /system
cp /sdcard/bootanimation.zip /system/media/
reboot
Did not work....
Anyone know if it this possible?
After reading a little more i can see that this will never work for me and my ROM (I'm a donut)
So yea... anyone know if anything like this is possible in a donut build?
not like the animations from eclair . as far as i have been able to find this is only a eclair thing.
ekeefe41 said:
I do most of my hacking from work. I am uncomfortable installing drivers for adb and such on a PC that i am not admin.
So I tried
su
mount -o remount,rw /dev/block/mtdblock3 /system
cp /sdcard/bootanimation.zip /system/media/
reboot
Did not work....
Anyone know if it this possible?
Click to expand...
Click to collapse
adb push boot1.gif /system/media/bootscreen/
adb push boot2.gif /system/media/bootscreen/
adb push boot_animation.xml /system/media/bootscreen/
adb push boot_bg.gif /system/media/bootscreen/
adb push boot_bg.mp3 /system/media/bootscreen/
unzip the file
xile6 said:
adb push boot1.gif /system/media/bootscreen/
adb push boot2.gif /system/media/bootscreen/
adb push boot_animation.xml /system/media/bootscreen/
adb push boot_bg.gif /system/media/bootscreen/
adb push boot_bg.mp3 /system/media/bootscreen/
unzip the file
Click to expand...
Click to collapse
First of all, if you even read his request, he wants to know how to do it via terminal since he doesn't want to install adb drivers on his computer and I'm pretty sure .gif boots won't work on a cupcake/donut/eclair/ ROM unless they are a HTC SENSE ROM. Please read before posting some BS.
Dude you should just flash via Recovery.
ekeefe41 said:
I do most of my hacking from work. I am uncomfortable installing drivers for adb and such on a PC that i am not admin.
So I tried
su
mount -o remount,rw /dev/block/mtdblock3 /system
cp /sdcard/bootanimation.zip /system/media/
reboot
Did not work....
Anyone know if it this possible?
Click to expand...
Click to collapse
try
cat /sdcard/bootanimation.zip > /system/media/
Macrophage001 said:
try
cat /sdcard/bootanimation.zip > /system/media/
Click to expand...
Click to collapse
Not gonna work, 1) What the hack are you trying to do with that command and 2) He's on Donut, he needs eclair
Damn My eyes are terrible.
note to self:
READ BEFORE WRITE!!!!
on google donut builds, you're stuck with the android-logo-mask and android-logo-shine boot animations. on hero builds, you can use the animated gifs. on eclair builds, you can do the bootanimation zips. if you want to know how to do a standard google build boot animation without using adb, check the link in my signature. i made a full written + video tutorial on how to do it.
the other easy way to do it, is of course, metamorph. making the .thm files takes about 30 seconds and you can flash it without having to use adb, terminal OR recovery.
So how did Cyanogen make a custom boot animation for CyanogenMod?
exactly in the fashion shown in my video tutorial. its not hard.
CM=google build.
your signature
kusotare said:
exactly in the fashion shown in my video tutorial. its not hard.
CM=google build.
Click to expand...
Click to collapse
Dude I love your sig...its tight how you got everything you are running in the form of a link, so people who want the same can easily learn how to do it without asking questions(which they still will do anyway) by simply clicking your links.
thats what I call community contribution.
heh, thanks, i havent updated the links in a LONG damn time though, as you can see. I'm obviously not running CM 4.2.3.1 anymore.
Kudos for the Vibrant!
Gotta love that 4.0 amoled screen dislplay.
and I love how Klyentel has his "G1-BRICKED!"
in his signature, too funny.
ekeefe41 said:
I do most of my hacking from work. I am uncomfortable installing drivers for adb and such on a PC that i am not admin.
So I tried
su
mount -o remount,rw /dev/block/mtdblock3 /system
cp /sdcard/bootanimation.zip /system/media/
reboot
Did not work....
Anyone know if it this possible?
Click to expand...
Click to collapse
yeah it is possible i do it all the time download terminal emulator form the market and enter the following commands
su
# cp /sdcard/bootanimation.zip /data/local/
# reboot
it works for me all the time
Is there something additional I need to do to actually gain "root"? I can't install the clear lock screen from smurf, can't wireless tether.... Don't know what's going on, all of this used to work fine on my Hero - what am I missing?
I don't think you have given enough info for people to even know what the problem is that you are having. Maybe you could be a bit more specific. Do you have superuser installed?
Sorry about that.... basically im on stock 2.2 with supposed "root" using regaws method - problem is, I can't use anything though; adb, wireless tether, I can't flash a lock screen (just sits at boot screen).
Download superuser app from the market place or google it if it is not on your phone already. Install it then launch an app that requires root. You will know real fast if you are rooted.
DomSim said:
Download superuser app from the market place or google it if it is not on your phone already. Install it then launch an app that requires root. You will know real fast if you are rooted.
Click to expand...
Click to collapse
I do have SU... that's the thing but when I try ADB Remount it says device not permitted or something like that, can't remember exactly
You could try full wipe / reflash.
Maybe try a diff ROM too.
You need to flash the engineering bootloader (0.76.2000). Go to Toast's method part 2 and follow the steps to unlock nand. You need the engineering bootloader in order to access /system.
Sent from my PC36100 using XDA App
sombdy said:
You need to flash the engineering bootloader (0.76.2000). Go to Toast's method part 2 and follow the steps to unlock nand. You need the engineering bootloader in order to access /system.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Nand root... I was looking for more info on this, I thought it was the culprit, thanks - ill post results, hopefully good
Edit: Won't work "Permission denied" .... this is really starting to piss me off grrr
DirtyShroomz said:
Nand root... I was looking for more info on this, I thought it was the culprit, thanks - ill post results, hopefully good
Edit: Won't work "Permission denied" .... this is really starting to piss me off grrr
Click to expand...
Click to collapse
Have you run Unrevoked Forever? This will turn off security permissions and should then allow you to flash anything.
Sent from my PC36100 using XDA App
Ok, the reason
Code:
adb remount
doesn't work is because the boot.img isn't patched to allow that, because I forgot to at the time of posting. You still have root (as long as you actually completed the guide successfully), that's just an all time access root through adb
To acheive the same results, type
Code:
adb shell
type
Code:
su
you will then see #. thats root.
Then remount your /system partition using
Code:
mount -o rw,remount / /system
there you go.
regaw_leinad said:
Ok, the reason
Code:
adb remount
doesn't work is because the boot.img isn't patched to allow that, because I forgot to at the time of posting. You still have root (as long as you actually completed the guide successfully), that's just an all time access root through adb
To acheive the same results, type
Code:
adb shell
type
Code:
su
you will then see #. thats root.
Then remount your /system partition using
Code:
mount -o rw,remount / /system
there you go.
Click to expand...
Click to collapse
When I try to type "su" it says "Permission denied"
DirtyShroomz said:
When I try to type "su" it says "Permission denied"
Click to expand...
Click to collapse
Do you have usb debugging on?
Try the new 1 click root in the dev forum. Unrevoked 3.2. See if that doesn't do the trick.
Sent from my PC36100 using XDA App
My guess is you didn't flash the 2.2-root.zip at the end then.. That's the best I can do w/ the info you've given.
one was already asked once but i had two questions
1. Is USB Debugging turned on or off? Settings > Applications > Development
2. you are using a stock rooted rom. are you trying to use sprint's wireless tether app? Sprint's app wont work you need to download wireless tether from the market.
joebags said:
one was already asked once but i had two questions
1. Is USB Debugging turned on or off? Settings > Applications > Development
2. you are using a stock rooted rom. are you trying to use sprint's wireless tether app? Sprint's app wont work you need to download wireless tether from the market.
Click to expand...
Click to collapse
Running stock 2.2. Regaw I did flash 2.2-root at the end and I am trying to use wireless tether not Sprints hotspot
I do have superuser in my apps list and I was able to install SNeoid, Swype, Setcpu, juicedefender and a few others that may require root but it wont let me do anything via adb or install any themes/mods that come in .zips
DirtyShroomz said:
Running stock 2.2. Regaw I did flash 2.2-root at the end and I am trying to use wireless tether not Sprints hotspot
I do have superuser in my apps list and I was able to install SNeoid, Swype, Setcpu, juicedefender and a few others that may require root but it wont let me do anything via adb or install any themes/mods that come in .zips
Click to expand...
Click to collapse
ok do this in command prompt and paste the results in code tags (to save space)
Code:
adb shell ls /system/bin/
regaw_leinad said:
ok do this in command prompt and paste the results in code tags (to save space)
Code:
adb shell ls /system/bin/
Click to expand...
Click to collapse
Code:
setconsole
dumplayer
svc
e2fsck_recvy
chownto
apph
ps
id
chownThp
notify
dhcpcd
pand
renice
bugreport
snd8k
hciattach
iqfd
top
lsmod
setprop
ionice
ifconfig
iptables
kthp_proxy
logwrapper
getevent
htcipcd
su
start
iqd
wipe
ip
smd
sleep
getWiMAXPropDaemond
newfs_msdos
vdc
sync
udhcpd
pppd
rmmod
fsck_msdos
netstat
route
sound8k
rm
radiooptions
pm
logcat
setWiMAXPropDaemond
resize2fs_recvy
htc_inittest
vmstat
dvz
mmcamera_test
keystore
dmesg
system_server
linker
fbtool
reboot
sdptool
busybox
hd
iftop
insmod
bootcomplete
rild
schedtop
debuggerd
wpa_supplicant
schedtest
bluetoothd
ping
btld
ime
omx_tests
tc
sendevent
racoon
toolbox
date
bma150_usr
bootanimation
wimaxDhcpRenew
log
installd
wimax_uart
applypatch
wimaxAddRoute
dexopt
monkey
ln
getprop
album_hdmiexe
stop
surfaceflinger
uevent
akmd
monitorMTD
wimax_mtd
mv
debug_tool
servicemanager
wimaxDumpKmsg
dumpstate
ipd
DmWrapperTest
nandread
kill
gzip
chmod
rmdir
lsc_camera
dbus-daemon
run-as
netcfg
cat
htclogkernel
sh
mount
printenv
mkdir
bmgr
wimaxDhcpRelease
umount
mke2fs_recvy
dnsmasq
input
df
ioctl
am
wimaxDumpLogcat
app_process
chown
htc_timezonetest
service
netd
ls
netsharing
cam_ins_spmo
mm-venc-omx-test
dalvikvm
ser2net
dmagent
shutdown
ndc
dumpsys
mediaserver
vold
sequansd
awb_camera
dd
keypress
cmp
mscompress
wimaxDumpLastKmsg
mtpd
watchprops
ok, so "su" is in there... you should be able to
Code:
adb shell
su
and it give you a #
try opening SuperUser.apk on your phone, THEN doing the above commands. a pop up should come up on your phone saying to allow root to su
regaw_leinad said:
ok, so "su" is in there... you should be able to
Code:
adb shell
su
and it give you a #
try opening SuperUser.apk on your phone, THEN doing the above commands. a pop up should come up on your phone saying to allow root to su
Click to expand...
Click to collapse
that worked, now to get remount do i have to always use that previous command you wrote?
Hi, today i've buy this "awesome" device.
i'm very disappointed for phone calls, beacuse i want to use it like a phone.
I haven't found any way to root this device.
So, i'm very newbie to make this possible because i don't know any programming languages, and i looking for a developer to help me and all A101 users to get root.
Please HELP!!!
Hello, if you want to use your tablet like a phone, download Google voice and groove ip. And the Acer a100 does have a devlopement section and there is a thread on how to root your tablet. Good luck---timothy
Sent from my A100 using Tapatalk
as of right now I don't believe there is a way to root your device the A101 to be exact.
Opps...I just now saw in the title that the op had an A101...sorry for the wrong information...
Sent from my A100 using Tapatalk
Tablets are not phones and can NOT make regular phone calls over the cell network. The SIM is for data connections only.
The best you can do is an IP phone call with app's like Skype.
I'm very sad to read this....
There is no way to see my A101 rooted?
I've follow the guide for root the A100 but problem is when script try to copy the "su" file in /system/xbin.
"su" don't copy for unknown reason.
Currently, no. No known rooting method exists.
Did you activate the USB debbuging on your tablet?
You might also need ADB to be able to do something with it.
Rooting method for Acer Iconia A101 (Russian language).
Code:
4pda.ru/forum/index.php?s=&showtopic=272402&view=findpost&p=11229134
Sorry, i can't translate this in English. My english is bad. Please, help me to translate my instruction and to place at this forum. Thanks.
ZeroNull said:
Rooting method for Acer Iconia A101 (Russian language).
Code:
//4pda.ru/forum/index.php?s=&showtopic=272402&view=findpost&p=11229134//
Sorry, i can't translate this in English. My english is bad.
Click to expand...
Click to collapse
Here it is, How to root the a101. This does work for the a100 also.
from adb or a terminal
Code:
/system/bin/cmdclient ec_micswitch '`echo ro.kernel.qemu=1 > /data/local.prop`'
Reboot adb shell to the a101 and you should have temp root.
su will have to pushed to /system/xbin and SuperUser.apk installed from the market.
That prop seems to stop haptic feedback, on the russian site it also mentions bluetooth also not working.
So remove local.prop after
Code:
rm /data/local.prop
[edit] Sorry, I guess this does not work on the a101 unless an a100 firmware is flashed.
eww245 said:
Here it is, How to root the a101. This does work for the a100 also.
from adb or a terminal
Code:
/system/bin/cmdclient ec_micswitch '`echo ro.kernel.qemu=1 > /data/local.prop`'
Reboot then adb shell to the a101 and you have temp root
Click to expand...
Click to collapse
eww245 said:
[edit] Sorry, I guess this does not work on the a101 unless an a100 firmware is flashed.
Click to expand...
Click to collapse
This is work in A101, if flashing A101 firmware from A100, execute command
Code:
/system/bin/cmdclient ec_micswitch '`echo 'ro.kernel.qemu=1' > /data/local.prop`'
and then flashing firmware A101 back. Then use adb for get root access.
ZeroNull said:
Rooting method for Acer Iconia A101 (Russian language).
Code:
//4pda.ru/forum/index.php?s=&showtopic=272402&view=findpost&p=11229134//
Sorry, i can't translate this in English. My english is bad. Please, help me to translate my instruction and to place at this forum. Thanks.
Click to expand...
Click to collapse
I was sent this link last night in a pm but I haven't been able to try it yet because there's a download in the original thread that seems to be needed and the link to it doesn't work for me. Can someone post that file up here please?
FloatingFatMan said:
I was sent this link last night in a pm but I haven't been able to try it yet because there's a download in the original thread that seems to be needed and the link to it doesn't work for me. Can someone post that file up here please?
Click to expand...
Click to collapse
No one? OK, can someone else please try downloading the A10x_rooting.zip file supposedly found at the following address? It doesn't work for me...
http://4pda.ru/forum/dl/post/1448282/A10x_rooting.zip
This is very interesting it looks it should work. In fact it looks like this little exploit it getting root on ICS(but nost latest version). a quick search revealed the following.
#This will determin if android is running inside an emulator
if ("1".equals(SystemProperties.get("ro.kernel.qemu")) {
// Emulator
}
/data/local.prop is loaded at boot and can set various system parameters.
Some vendor implementations have system parameters that allow root access - so being able to create /data/local.prop allows any user to set those system parameters. It would be more secure if the vendor created an empty /data/local.prop file with access permissions that would only allow write access to root.
So my guess is somehow redirecting the output from ro.kernel.qemu to the local.prop tricks android into granting superuser. Very cool. Too bad it looks like they patched the latest ICS
Were you able to download that file, then? If so, could you please post it up here? I can't get it at all, just get told the file doesn't exist...
Content file
This is file content next:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
su
It tools adb for windows and su file for rooting android arm cpu device.
Plan get "root" for Acer ICONIA TAB A101
Plan get "root" for Acer ICONIA TAB A101
1. Flash firmware A100
2. Touch file "/data/local.prop" and put variable "ro.kernel.qemu=1":
Code:
/system/bin/cmdclient ec_micswitch '`echo 'ro.kernel.qemu=1' > /data/local.prop`'
3. Flash firmware A101
4. Execute "adb tools" for Windows with this command:
Code:
adb remount
adb push su /system/xbin/
adb shell "chmod 06755 /system/xbin/su"
5. Off variable "ro.kernel.qemu=1":
Code:
adb shell "echo '#' >/data/local.prop"
6. Install app
BusyBox
SuperUser APK
Titanium Backup
7. Reboot device
This is work. It is checked up time and again.
Great, thanks! I'll try it later today and presuming I read your instructions correctly, will post up a more native English version of them afterwards, if that's OK with you?
Ok
It would be very good! Thank you!
Root confirmed, awesome! Thanks ZeroNull, you are da MAN!
I want to go a step further and update my A101 to the latest leaked ROM and see if I keep root before I post a more native English set of instructions, but for anyone who wants to try it now, it works!
Hello there!
At first,I would like to say thank you to all users for their supports and their help, thank to your informationI have finally upgraded my Acer Iconia A100 to ICS and I have rooted the device without any problem, and it works like a charm!
But before I made the upgraded to ICS i was using Honey Comb 3.2 which was rooted also and I did manage to install Adhocenabler which worked perfectly with my nokia n97.
So I have upgraded the device to ICS, rooted it, but now I can't get adhocenabler applicatin to work! It always come with "unable to mount system" "are you rooted ?"
All applications have rooted access but it seems that adhocenabler can't have it!
I have tried to Re-root the device, tried to hard reset it, but it still doesn't work...
ANyone is facing the same problem? do you have a solution ?
thank you very much
Hi there, I had a similar problem whilst trying to install chainfire3D.
Try running this (seperate commands) from within terminal emulator (a quick download from the Play Store if you haven't got it installed)
su
mount -o remount, rw /system/
Let me know if this works, did you follow the ZeroNull method?
thank you for your answer!
I've tried your method, but i doesn't work... I'm still stuck with the same error
I have took a screenshot of the application
freefilehosting.net/20120401-145832
freefilehosting.net/20120401-1458361
that sounds weird because it's the only one application that can't get root access
For those who cant get access to adhoc network on ICS,
this method is working perfectly !
download a copy of the wpa_supplicant, here and put it in sdcard/download directory
forum.xda-developers.com/showthread.php?t=1033314
and then open a command shell on windows and type
ADB SHELL
su
mount -o rw,remount /system
cd /system
chmod 775 bin
cd bin
cat wpa_supplicant > wpa_supplicant.old
ls
cat /sdcard/download/wpa_supplicant > /system/bin/wpa_supplicant
ls –a –l
chmod 755 /system/bin/wpa_supplicant
chown system.wifi /system/etc/wifi/wpa_supplicant.conf
mount -o ro,remount /system
press ctrl-c
unplug usb
reboot tablet
restart start phone
Now everything is OK ;=)
I have managed to get CIFS working on stock Nexus 10.
It's quite a bit more problematic on the Nexus 10 than normal.
There are 2 main issues to deal with. Newer versions of the Linux kernel require a UNC variable to be passed to them and the current version of busybox doesn't do this. There is a patch out. I have extracted the patched busybox binary from craigacomez's AOSP Nexus 10 rom.
(Check it out here: http://forum.xda-developers.com/showthread.php?t=1998585 ). Otherwise it should work on the stock mount command if you specify the unc= mount option with the share.
The other issue is the multiuser stuff. If you execute the mount command from inside Terminal Emulator (or a script program) it looks like it mounts ok and you can 'ls' in the directory but it doesn't work for Android apps, they just see an empty directory but if you do it via a 'adb shell' it works fine in Android apps. My theory is ADB is outside of the multiuser stuff. adb actually ships on the device.
1) Unlock bootloader (fastboot oem unlock)
2) Flash recovery adb flash recovery whatever.img
3) Root device (flash CWM-SuperSU-0.98.zip)
4) Install BusyBox (from the market)
5) Copy md4.ko and cifs.ko to device. The files can go anywhere you like. In this example I will just use the root of the sdcard. Some people like them in /system/modules or /system/lib/modules
6) busybox mount -o rw,remount /
7) adb shell
8) Override /system/bin/busybox with the patched version (maybe move it first so it's backed up).
9) insmod /sdcard/md4.ko
10) insmod /sdcard/cifs.ko
11) busybox mount -t cifs -o username=MYUSER,password=MYPASS,unc=\\\\192.168.1.1\\storage //192.168.1.1/storage /data/media/0/cifs/Storage
You will need to manually preform the last 3 commands each time you reboot the device from a adb shell.
NOTE: You can probably get rid of the -o flags completely. In theory the patched version of busybox makes the UNC bit redundant. Possibly you can use the stock busybox with the UNC flag and avoid using the patched one totally. I have just included it to be sure.
Make sure you type 'busybox mount' not 'mount', by default they are different binaries. Otherwise you can remove the /system/bin/mount command and make a new one linking /system/bin/mount to /system/bin/busybox.
Possibly there is some way to get the mount working in the multiuser environment without requiring busybox. If you figure it out please tell ☺
Some threads on the issue:
http://forum.xda-developers.com/showthread.php?p=34397868#post34397868
http://forum.xda-developers.com/showthread.php?t=733490&page=6
http://www.mail-archive.com/[email protected]/msg17650.html
The modules are for 3.4.5-g4e6298b.
EDIT: I added nls_utf8.ko by request
EDIT2: Since adb comes on the device, it is possible to use it to connect to local host:
1) Install cifs modules to /system/lib/modules
2) Install Script Manager from the play store
3) Copy script to device
4) Start SManager
5) Find your script and open it.
6) Tick the su box
7) Hit save
8) Goto home sccreen
9) Add a 'SMShortcuts' widget to your home screen
10) "Add one script shortcut"
11) Choose your script
12) Optionally use this pretty icon ☺
13) Give it a nice name like "Mount Shares"
Here is a shell script...
Code:
#!/system/bin/sh
# Your settings here
USERNAME="USERNAME"
PASSWORD="PASSWORD"
IPADDRESS="192.168.1.1"
SHARE="storage"
MOUNT_POINT="/data/media/0/cifs/Storage"
# If you need to change the mount command edit this
MOUNT_CMD="\
mount -t cifs \
\
-o \
user=$USERNAME,\
password=$PASSWORD,\
unc=\\\\\\\\\\\\\\\\$IPADDRESS\\\\\\\\$SHARE \
\
//$IPADDRESS/$SHARE \
$MOUNT_POINT"
COMMANDS="\
insmod /system/lib/modules/md4.ko; \
insmod /system/lib/modules/nls_utf8.ko; \
insmod /system/lib/modules/cifs.ko; \
$MOUNT_CMD
"
# Starting ADB...
PORT=`getprop service.adb.tcp.port`
setprop service.adb.tcp.port 5555
adb kill-server
adb start-server
stop adbd
start adbd
adb connect localhost
# Make sure we only use the first device (sometimes there is more than one)
SERIAL=`adb devices | head -n2 | tail -n1 | cut -f1`
if [ "$SERIAL" = "" ] ; then
echo "ERROR: Could not find ADB device.";
fi
echo Mounting share via adb...
adb -s $SERIAL shell su root -c "$COMMANDS"
# If you started adb, then stop it here for security:
adb disconnect localhost
stop adbd
setprop service.adb.tcp.port $PORT
start adbd
RESULT=`mount | grep $MOUNT_POINT`
if [ "$RESULT" = "" ] ; then
echo "Mounting failed..."
else
echo "Mounting sucess!"
fi
echo Done... You may close this script window.
EDIT3: Added usbserial.ko, option.ko and usb_wwan.ko
EDIT4: Some users have reported that the need to modify the script to get it working with their version of SU.
EDIT5: I have uploaded modules for 4.2.2, kernel 3.4.5-gaf9c307 but I haven't actually tested them myself (still on 4.2.1). Apparently the adb loophole has also been patched but it is possible to reenable it by putting a RSA key onto the device. Check out this set of instructions here.
EDIT6: I have updated to 4.2.2 on my Nexus 10 and can confirm the new modules work.
You must setup the adbkey or you will get a "device: offline" message. By default adb when adb first runs it tries to create the keys in the $HOME dir which is /data/.android, but the data directory isn't accessible by the 'shell' user.
I got it working simply by setting the HOME variable to /sdcard and restarting the adb server in the script then Android popped up a query (I have update the script above).
IMPORTANT: The Android Media scanner recursively scans folders for media to add the the database so it shows up in programs like Google Music. On large shares this can be a long process and use heaps of battery life. To prevent this add a blank file with the name ".nomedia" to the root of your mount points (or each individual share if you aren't used 1 folder for all your mounts). This will stop music showing up in programs though.
If you find that the device stops responding (the launcher might work but apps fail to load) or you get reboots (often after the previous bug) this is probably due to a bad wifi connection.
Is it posible to make a CWM flash file?
Great
This is great progress, do you know if there is some way I can use the same to mount my usb OTG with ADB shell so that I can read/write to my pen drives from my android apps/file managers?
I have tried using the busybox mount but that didn't work, do I need the modified mount or will none of this help anyway?
alias_neo said:
This is great progress, do you know if there is some way I can use the same to mount my usb OTG with ADB shell so that I can read/write to my pen drives from my android apps/file managers?
I have tried using the busybox mount but that didn't work, do I need the modified mount or will none of this help anyway?
Click to expand...
Click to collapse
Code:
busybox mount -t FSTYPE /dev/block/sda1 MOUNT_LOCATION
Example:
Code:
busybox mount -t vfat /dev/block/sda1 /storage/sdcard0/usbotg
craigacgomez said:
Code:
busybox mount -t FSTYPE /dev/block/sda1 MOUNT_LOCATION
Example:
Code:
busybox mount -t vfat /dev/block/sda1 /storage/sdcard0/usbotg
Click to expand...
Click to collapse
How is this different to what I'm doing already? Mounting this way doesn't work, only the process that mounted it can see the files.
Although I don't have nexus 10, I am having the similar mounting issue on my nexus 7 until I saw this post.
Advise about "adb shell" really helps me resolve the multiuser issue.
Thanks for sharing.
Any chance you could post the nls-utf8.ko for utf8 support?
Thanks!
H3g3m0n said:
1) Unlock bootloader (adb oem unlock)
Click to expand...
Click to collapse
Isn't it fastboot that unlocks the bootloader, and not adb? (unless adb can do it too; I've only heard of fastboot though)
momulah said:
Is it posible to make a CWM flash file?
Click to expand...
Click to collapse
Not a high priority right now as currently you need to do the manual adb shell stuff by hand to get things mounted, a little extra setup work isn't a huge difference.
alias_neo said:
How is this different to what I'm doing already? Mounting this way doesn't work, only the process that mounted it can see the files.
Click to expand...
Click to collapse
Are you mounting in a 'adb shell' or locally in something like terminal emulator? My OTG cable won't be here for a while so I can't really test myself.
weasal said:
Any chance you could post the nls-utf8.ko for utf8 support?
Thanks!
Click to expand...
Click to collapse
Posted, haven't tested it but it seemed to insmod fine.
espionage724 said:
Isn't it fastboot that unlocks the bootloader, and not adb? (unless adb can do it too; I've only heard of fastboot though)
Click to expand...
Click to collapse
Yeh typoed, i'll fix that now.
Currently I'm thinking of ways to hack around the 'adb shell' requirement, as a basic hackish fix would be to make a program that turns on adb wireless, connects to the local device and issues a command. Of course possibly there is a 'proper' way to do mounting. Another lazy way for those with their shares on a Linux system would be a script issue commands to the server via a ssh, getting it to log back into the phone and mount stuff over adb wireless.
alias_neo said:
How is this different to what I'm doing already? Mounting this way doesn't work, only the process that mounted it can see the files.
Click to expand...
Click to collapse
I've been working on getting OTG support natively in my AOSP based custom ROM and I have had some success... check out my ROM for details
H3g3m0n said:
Currently I'm thinking of ways to hack around the 'adb shell' requirement, as a basic hackish fix would be to make a program that turns on adb wireless, connects to the local device and issues a command. Of course possibly there is a 'proper' way to do mounting. Another lazy way for those with their shares on a Linux system would be a script issue commands to the server via a ssh, getting it to log back into the phone and mount stuff over adb wireless.
Click to expand...
Click to collapse
Just wanted to thank H3g3m0n as I was able to successfully mount over adb. Also came up with a workaround to bypass connecting to a PC, grabbed the arm fastboot binary from this thread and installed it on my nexus 7. Used it to connect wireless adb on the 10 and ran the mount commands on the 7.
H3g3m0n said:
Posted, haven't tested it but it seemed to insmod fine.
Click to expand...
Click to collapse
Thanks, I'll give it a try!
You might find my posts #156 and #162 at http://forum.xda-developers.com/showthread.php?t=1781411&page=17 helpful.
Sorry for the noob ? ...
What are the KO's do?
What is the practical use of then.
Sorry I did a little research on then but I could not find an answer in layman terms
Thank you for allowing me to learn.
Sent from my toroplus using xda premium
spdwiz18 said:
Sorry for the noob ? ...
What are the KO's do?
What is the practical use of then.
Sorry I did a little research on then but I could not find an answer in layman terms
Thank you for allowing me to learn.
Sent from my toroplus using xda premium
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Loadable_kernel_module
craigacgomez said:
http://en.wikipedia.org/wiki/Loadable_kernel_module
Click to expand...
Click to collapse
That helps allot.... Now i have an understanding of ko's in general. But what specificly do the modules this thread refers to do and the practical use of then. Thanks foot the help.
Sent from my toroplus using xda premium
spdwiz18 said:
That helps allot.... Now i have an understanding of ko's in general. But what specificly do the modules this thread refers to do and the practical use of then. Thanks foot the help.
Sent from my toroplus using xda premium
Click to expand...
Click to collapse
These modules are needed to enable support for CIFS (Windows share) mounts...
spdwiz18 said:
That helps allot.... Now i have an understanding of ko's in general. But what specificly do the modules this thread refers to do and the practical use of then. Thanks foot the help.
Sent from my toroplus using xda premium
Click to expand...
Click to collapse
Basically you can setup a shared folder from a remote computer. It allows you to have files on another system accessible as if it was part of the internal storage in the device.
Just found out that Android ships with the adb binary on the device itself (after crosscompiling it myself :/, oh well the experience was useful).
It should be possible to setup a script to start the adb server, connect to the localhost and execute the mount without too much difficulty.
Ok, added a script and instructions to the front page for simple on tablet mounting.