This -> View attachment adhoc-switcher.zip <- archive includes the modified wpa_supplicant file that supports ADHOC mode, along with scripts to switch back and forth between the ADHOC mode wpa_supplicant and the stock (Infrastructure only) wpa_supplicant on your NC.
The included file adhoc-switcher.sh is will do all of the work for you.
From the included README file:
Unzip the archive View attachment adhoc-switcher.zip into the same directory as your adb binary.
Execute ./adhoc-switcher.sh in your adb binary directory.
# md5sum adhoc-switcher.zip
e682e1578df1a253f1e4c42fd89f37d5 adhoc-switcher.zip
When you run adhoc-switcher.sh, you will see the following output telling you what it is doing:
Code:
$ ./adhoc-switcher.sh
(1) Remounting /system as read-write...
(2) Making backup of original wpa_supplicant at:
/system/bin/wpa_supplicant.original...
(3) Making local backup of /system/bin/wpa_supplicant.original...
2070 KB/s (226036 bytes in 0.106s)
(4) Pushing up new files to /system/bin/...
wpa_supplicant.adhoc: 1662 KB/s (226028 bytes in 0.132s)
wpa_supplicant.infrastructure: 1711 KB/s (226036 bytes in 0.128s)
ap: 6 KB/s (271 bytes in 0.042s)
adhoc: 6 KB/s (253 bytes in 0.040s)
(5) Setting permissions on new files in /system/bin/...
(6) Setting Wifi mode to Infrastructure (ap)...
(7) Remounting /system as read-only...
All done!
To switch between Access Point (AP) [Infrastructure] mode and ADHOC mode,
execute the following commands on your NC:
# su
# ap
To switch to Access Point [Infrastructure] mode, execute the following
commands on your NC:
# su
# adhoc
You should turn off wifi before executing these commands.
Hope you find this useful.
John - your friendly neighborhood e-thug.
Thank you. Will give this a try.
Any chance of anyone creating a toggle widget that can toggle between both with a simple tap.
Sent from my SGH-T959 using XDA App
Very nice John. Good quick fix for the adhoc switching. Appreciate the effort.
Sent from the totally awesome Rooted Nook Color
rxr said:
Thank you. Will give this a try.
Any chance of anyone creating a toggle widget that can toggle between both with a simple tap.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I'd love to do that but, my netbook just isn't up to the task of running a full-on android dev environment. Over Christmas, I'll try to remember to bring the "big" laptop back with me.
If someone else beats me to it, that would be great too.
Maybe we could get the SoftKeys app to allow a new button to appear to toggle the wifi setting?
johnopsec said:
This -> View attachment 464007 <- archive includes the modified wpa_supplicant file that supports ADHOC mode, along with scripts to switch back and forth between the ADHOC mode wpa_supplicant and the stock (Infrastructure only) wpa_supplicant on your NC.
Click to expand...
Click to collapse
Hey there, Mr. eThug. Thanks for the update. But I didn't it was necessary. After installing the original fixed wpa_supplicant, I can connect to adhoc and infrastructure networks. Or is there something else I'm missing?
edison said:
Hey there, Mr. eThug. Thanks for the update. But I didn't it was necessary. After installing the original fixed wpa_supplicant, I can connect to adhoc and infrastructure networks. Or is there something else I'm missing?
Click to expand...
Click to collapse
The ADHOC capable wpa_supplicant has a bug that requires you restart wifi any time the NC sleeps. The original does not. Since my personal use is with standard Infrastructure (AP) connections primarily and ADHOC only on occasion, I decided that it would be handy to be able to switch between them easily.
You have a typo in the script, line 28 I think, should be "adb shell" and you have "db" shell.
Messes with permissions.
KitF said:
You have a typo in the script, line 28 I think, should be "adb shell" and you have "db" shell.
Messes with permissions.
Click to expand...
Click to collapse
I just verified from my local copy and also downloaded the archive I uploaded to the site. They're identical and in every instance, it is "./adb shell" just as it should be.
Any possibility you opened adhoc-switcher.sh in an editor and accidently deleted a character? Other than that, the MD5SUM of the original archive is:
# md5sum adhoc-switcher.zip
e682e1578df1a253f1e4c42fd89f37d5 adhoc-switcher.zip
Make sure that the MD5SUM matches for what you downloaded.
Oh that's right, I must have messed it up somehow converting it into a windows Batch file.
Any way we can get some sort of GUI app or a widget toggle for this? Seems like it would be handy for when I need to tether to my phone when there's no wifi around.
KitF said:
Oh that's right, I must have messed it up somehow converting it into a windows Batch file.
Any way we can get some sort of GUI app or a widget toggle for this? Seems like it would be handy for when I need to tether to my phone when there's no wifi around.
Click to expand...
Click to collapse
Cool. Glad we tracked that down!
I'd love a widget or app to switch between them. Two things though... This is a temporary "fix" for an issue. Once they get the bugs worked out of wpa_supplicant so it can support Infrastructure and ADHOC and not have the sleep issue, we won't need to switch back and forth between them. Second: I don't have a full-blown android dev platform to do an app or widget myself so, someone else would need to do it.
Maybe using gscript lite as was done here : http://www.chinadigitalcomm.com/android-a81/a81e-connect-to-ad-hoc-wifi-t1413-10.html
I suppose running sh scripts doesn't work on Windows?
nikescar said:
I suppose running sh scripts doesn't work on Windows?
Click to expand...
Click to collapse
Nope. But if you're up to the task, it should be easy for you to convert the script to winblowz .bat format for the most part.
I tried to modify the scripts to run through gscript and I thought it worked initially. Then when I went to switch it waste my wifi. Had to restore from the backup.
Gscripts would be nice I'm just not smart enough to do it.
Did you switch Wifi off before switching?
Also here's my converted .bat that I used:
Code:
echo
echo "(1) Remounting /system as read-write..."
adb shell "mount -o remount rw /system"
echo
echo "(2) Making backup of original wpa_supplicant at:"
echo "/system/bin/wpa_supplicant.original..."
adb shell "mv /system/bin/wpa_supplicant /system/bin/wpa_supplicant.original"
echo
echo "(3) Making local backup of /system/bin/wpa_supplicant.original..."
echo
adb pull /system/bin/wpa_supplicant.original
echo
echo "(4) Pushing up new files to /system/bin/..."
echo
echo -n "wpa_supplicant.adhoc: "
adb push wpa_supplicant.adhoc /system/bin/
echo -n "wpa_supplicant.infrastructure: "
adb push wpa_supplicant.infrastructure /system/bin/
echo -n "ap: "
adb push ap /system/bin/
echo -n "adhoc: "
adb push adhoc /system/bin/
echo
echo "(5) Setting permissions on new files in /system/bin/..."
adb shell "chmod 755 /system/bin/wpa_supplicant.*"
adb shell "chmod 755 /system/bin/ap"
adb shell "chmod 755 /system/bin/adhoc"
echo
echo "(6) Setting Wifi mode to Infrastructure (ap)..."
adb shell "ln -s /system/bin/wpa_supplicant.infrastructure /system/bin/wpa_supplicant"
echo
echo "(7) Remounting /system as read-only..."
adb shell "mount -o remount,ro /dev/block/mmcblk0p5 /system"
echo
echo "All done!"
echo
A bit messy but it works.
KitF said:
Did you switch Wifi off before switching?
Click to expand...
Click to collapse
Thanks for the bat.
What I was trying to do is modify the scripts to run through the gscripts app for Android. That way we could switch on the go a bit easier. Sure I could use a console emulator but one click (actually two) is what I was looking for.
I might give it a try later, the .sh files available here http://www.chinadigitalcomm.com/android-a81/a81e-connect-to-ad-hoc-wifi-t1413-10.html can be opened with a text editor and it looks like the command just "crushes" the file.
I can see the ad-hoc network created by my phone and I connect. But none of the web-based apps are working. Says I am connected but no data comes through. Any ideas?
The .bat file is a good idea.
I factory reset my Nook again (tried to return it for one that flickers less). I had to go through this again. I was distracted when going through the commands and had mucked something up - Wifi wouldn't start back up at all after I tried to switch back and forth. But I knew it worked because I had it working yesterday.
Poked my head in and checked security (ls -l /system/bin) , I could tell the security of the files didn't match. Looks like I missed one or two of the chmod commands (kids were probably distracting me). Fixed 'em up and it's working fine now.
At least with a .bat file or the like, there's less chance for a typo.
Related
All credit goes to the orig guy who made the d2 exploit
If you feel the need to donate money then he deserves it [email protected]
I made an easier to follow tutorial over here with pics. Sorry but I am tired of going back and forth so just go there if you are having problems. If you can follow simple adb commands just follow the directions below
Download and Install Samsung Drivers
64bit:
http://www.wikifilez.com/root files/epic4g/usb_drivers_GalaxyS_x64.zip
32bit:
http://www.wikifilez.com/root files/epic4g/SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe
1 Click Root Method
http://forum.androidcentral.com/fascinate-roms-hacks/33899-how-root.html
Manual Method
cd C:\android-sdk\tools
adb push C:\fascinate\su /sdcard/su
adb push C:\fascinate\rage.bin /data/local/tmp/rage.bin
adb push C:\fascinate\busybox /sdcard/busybox
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
./rage.bin
wait....
when it brings you back to your original shell in windows then follow these commands
adb shell (you should see # this time instead of $ this is exactly what we want)
mount -t rfs -o remount,rw /dev/block/stl9 /system
cd /system/xbin
cat /sdcard/su > su
cat /sdcard/busybox > busybox
chmod 4755 su
chmod 4755 busybox
exit
adb install C:\fascinate\Superuser.apk
This is permanent.
I just updated the files here with the latest su / superuser.apk / busybox
Also check out my tutorial to fix the memory/lag issues for this phone
http://forum.xda-developers.com/showthread.php?p=8086738#post8086738
Dirrk said:
All credit goes to the orig guy who made the d2 exploit
I feel naked without my droid lol this phone is so light
adb push su /sdcard/su
adb push rage.bin /data/local/tmp/rage.bin
adb push busybox /sdcard/busybox
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
./rage.bin
wait....
when it brings you back to your original shell or windows cmd promt
adb shell
mount -t rfs -o remount,rw /dev/block/stl9 /system
cd /system/xbin
cat /sdcard/su > .
cat /scard/busybox > .
chmod 4755 su
chmod 4755 busybox
exit
adb install Superuser.apk
Please let me know if I posted something wrong.
Click to expand...
Click to collapse
does it stick after reboot?
Its supposed to be a temporary root so i doubt it will.
This works on any android phone up to 2.2. I have confirmed this works on my epic, so th same sould work here.
Sent from my SPH-D700 using XDA App
see below.
confirmed root.
Had to use Superuser.apk 2.3.6.1 and the su binary in the package, but the rest worked.. except for that cat command? Why would you cat binary files instead of copying them? (not complaining, just curious). I just adb pushed them to /system/xbin, and adb shell chmod'd them.
You also have a typo near the end "scard" instead of "sdcard".
You can also use mv or cp. I just happen to use cat because I used it the other day rooting my friends stock 2.2 droid. Which required me to use cat.
And yes this is permanent
Cool, i tried using rm -rf to get rid of a directory I created accidentally, and was getting some syntax errors, so I wasn't sure how compatibile the command line on android was to linux.
Glad it's pretty close. Being very familiar with linux makes this pretty easy to understand. Day 1 with an android device was pretty darn fun. I think I'm glad I went this direction.
I just followed this and used the same files I had from my Droid 2 (just updated the Superuser.apk from this sites thread for it) and works perfectly. Rebooted phone did "adb shell" and "su" and still have root, so it is permanent
side note: steps say "/system/xbin" and assume you meant "/system/bin" like Droid 2 was. That's where I put them and it worked.
cliffr39 said:
I just followed this and used the same files I had from my Droid 2 (just updated the Superuser.apk from this sites thread for it) and works perfectly. Rebooted phone did "adb shell" and "su" and still have root, so it is permanent
side note: steps say "/system/xbin" and assume you meant "/system/bin" like Droid 2 was. That's where I put them and it worked.
Click to expand...
Click to collapse
It works either way, both are executable system folders. Glad you it worked for you, hopefully we can get some roms cooking soon and play catch up to the other galaxy s phones
doesnt work for me, i get an error device not found
ive type adb devices - device not found. usb debugging on, usb conneced on port 5037
xirnibor said:
doesnt work for me, i get an error device not found
ive type adb devices - device not found. usb debugging on, usb conneced on port 5037
Click to expand...
Click to collapse
Your USB mode might be set wrong. Flip it to whatever it's not at, and try again.
i forgot this laptop didnt have the updated usb drivers from android sdk, downloading then will try again. i have tried so far with the sdcard mounted and unmounted, while in usb debugging mode. will post after updates
How long do you actually have to wait after the execting the rage.bin file?
itznfb said:
How long do you actually have to wait after the execting the rage.bin file?
Click to expand...
Click to collapse
I dunno, ~20-30 seconds? Assuming sound is enabled you should hear the same USB device connected/disconnected sounds.
If you want to be 100% sure just wait like 90 seconds. I'm pretty sure it killed my shell though, so if it does that, you're good to go.
ok, adb recognizes the device *see below, however when i type adb push su /sdcard/su i get cannot stat 'su': no such file or directory. ?
C:\downloads\android\android\tools>adb devices
List of devices attached
I500a2d0087a device
namebrandon said:
I dunno, ~20-30 seconds? Assuming sound is enabled you should hear the same USB device connected/disconnected sounds.
If you want to be 100% sure just wait like 90 seconds. I'm pretty sure it killed my shell though, so if it does that, you're good to go.
Click to expand...
Click to collapse
ok... running the rage.bin locked up my device twice but on the third try it worked. another fascinate rooted
xirnibor said:
ok, adb recognizes the device *see below, however when i type adb push su /sdcard/su i get cannot stat 'su': no such file or directory. ?
C:\downloads\android\android\tools>adb devices
List of devices attached
I500a2d0087a device
Click to expand...
Click to collapse
su is a file (for our purposes right here, anyway). Unless you explicity specify its path, it needs to be in the same directory you're running the adb command from.
If you installed the Android SDK per guidelines, adb should be in your PATH environment variable, and you should be able to execute it from any directory. If you didn't do that, then for the sake of simplicity, copy all the files referenced in the original steps to your working directory. From your post above, it appears that is c:\downloads\android\android\tools\
I got stuck at cat /sdcard/su > . Is that supposed to be > .? It won't let me enter that...There's not something else that's supposed to be there?
EDIT: I get the same error faspalma
I'm stuck at that point too. cat /sdcard/su > . returns "cannot create .: is a directory"
From this thread:
http://forum.xda-developers.com/showthread.php?t=874871
Attached is a working sqlite3 binary.
Copy it to /system/bin
(I transfered it to my SD, then used rootexplorer (mount R/W) to copy into /system/bin))
you will now be able to edit sqlite databases on the nook itself.
--------------------------------------------------------------------------------
Attached Files sqlite3.7z (11.9 KB, 56 views)
--------------------------------------------------------------------------------
In your terminal:
$ adb pull /data/data/com.bn.devicemanager/databases/devicemanager.db devicemanager.db
$ sqlite3 devicemanager.db
sqlite> update registry set value='manual' where name='com.bn.device.fota.mode';
sqlite> .q
$ adb push devicemanager.db /data/data/com.bn.devicemanager/databases/devicemanager.db
$ adb reboot
Congrats Your NC is now permanently blocked from any future BN OTA auto updates.
No more build.prop spoof hacks for each release (sideload only),,,,,, yada yada
sleep like a baby.........with yur wifi on.
Nook got pissed and reset itself. Good thing I have backups.
bonzer2u, thanks! Just did it on my rooted (1.0.1 version) nook and so far no issues.
That reminds me that the prereqs are you need to be rooted with SU and ADB working.....DOH
Jeeeez and of course credit where credit is due...
JoshMiers - for providing the sqlite3 binary post.
and
ixampl - for providing the clues that lead me to find the appropriate db and setting to hack.
Finally, disclaimer: Apply and/or feel free to incorporate into your projects at your own risk, if your NC self distructs, yur on yur own......NOT
Instructions don't use sqlite3 binary on device
Your instructions work fine assuming that the computer connected to the NC has the sqlite3 binary installed. The sqlite3 binary you link to could be used to make the changes inside adb shell but it's not documented as such. Just wanted to give that note to help clear up anyone's confusion if they run into issues with the given instructions. Other than that, thanks for the tip!
The sqlite3 binary I posted is for use on the Nook itself. If you want to do that instead of doing adb pull/push just do this in an adb shell:
Code:
# sqlite3 /data/data/com.bn.devicemanager/databases/devicemanager.db
sqlite> update registry set value='manual' where name='com.bn.device.fota.mode';
sqlite> .q
# reboot
JoshMiers said:
The sqlite3 binary I posted is for use on the Nook itself. If you want to do that instead of doing adb pull/push just do this in an adb shell:
Code:
# sqlite3 /data/data/com.bn.devicemanager/databases/devicemanager.db
sqlite> update registry set value='manual' where name='com.bn.device.fota.mode';
sqlite> .q
# reboot
Click to expand...
Click to collapse
Easier then I thought, thanks again Josh....
hoban_eris said:
Your instructions work fine assuming that the computer connected to the NC has the sqlite3 binary installed. The sqlite3 binary you link to could be used to make the changes inside adb shell but it's not documented as such. Just wanted to give that note to help clear up anyone's confusion if they run into issues with the given instructions. Other than that, thanks for the tip!
Click to expand...
Click to collapse
If I understand you correctly, my PC is a dell win7-32 laptop and it doesn't have any sqlite3 installed binary on it? I did however use it to download and transfer the sqlite3 binary Josh posted to my nook??
Yes Josh mentioned the adb shell version above.
I did initially forget to mention you need to be rooted and have SU and ADB functioning as a prereq, my bad, but it is pretty obvious.....
If you have adb working on your PC, the chances are that you have sqlite binary on your PC since it seems to come with the android sdk in the tools folder (for example, android-sdk_r07-windows\android-sdk-windows\tools). When I did it on mine, I used the commands from the OP, and did it on the PC with nook connected, but didn't use the linked sqlite3 binary for nook).
droidseban said:
If you have adb working on your PC, the chances are that you have sqllite binary on your PC since it comes with the android sdk in the tools folder (for example, android-sdk_r07-windows\android-sdk-windows\tools). When I did it on mine, I followed your directions, and did it on the PC with nook connected, but didn't use the linked sqllite3 binary for nook).
Click to expand...
Click to collapse
Ahh I see now and didnt know that... I understand what you guys are referring to now.
Thanks for clearing that up, like my post title suggests, still just a rookie with the nook that is.....
We are all here to learn from each other.
Looking through the rest of the entries in the registry table, there is this entry: "com.bn.device.fota.next_connect_default_interval" which is set to the value 604800000. Assuming this is in milliseconds as usual, it translates to 7 days. So, nook is set to check for updates once every week. I guess you can try upping this number also to avoid the updates.
Adding a command to raise the udate check interval to a year to the steps from OP (NOTE: no space in "...default_interval". Not sure why the forum software is inserting it):
$ adb pull /data/data/com.bn.devicemanager/databases/devicemanager.db devicemanager.db
$ sqlite3 devicemanager.db
sqlite> update registry set value='manual' where name='com.bn.device.fota.mode';
sqlite> update registry set value='31557600000' where name='com.bn.device.fota.next_connect_default_interval';
sqlite> .q
$ adb push devicemanager.db /data/data/com.bn.devicemanager/databases/devicemanager.db
$ adb reboot
excellent, did you notice the download URL in the table as well?????
Someone suggested another way to perma-stop OTA would be to add the url
https://csqaint.barnesandnoble.com/bncloud/serviceG 127.0.0.1
to our hosts file?
Do you think this would work as well?
I would think so, but it might crash the process that checks for the updates.
bonzer2u said:
Someone suggested another way to perma-stop OTA would be to add the url
https://csqaint.barnesandnoble.com/bncloud/serviceG 127.0.0.1
to our hosts file? Do you think this would work as well?
Click to expand...
Click to collapse
No -- the hostname csqaint does not resolve outside BN.
I don't think it is directly going to https://csqaint.barnesandnoble.com/bncloud/serviceG. My guess is Nook goes to https://bncs.barnesandnoble.com/bncloud/oauthpage/BnOAuthMgmt.jsp to authorize the connection, establishes a VPN, and then move on to https://csqaint.barnesandnoble.com/bncloud/serviceG.
bonzer2u said:
From this thread:
http://forum.xda-developers.com/showthread.php?t=874871
Attached is a working sqlite3 binary.
Copy it to /system/bin
(I transfered it to my SD, then used rootexplorer (mount R/W) to copy into /system/bin))
you will now be able to edit sqlite databases on the nook itself.
--------------------------------------------------------------------------------
Attached Files sqlite3.7z (11.9 KB, 56 views)
--------------------------------------------------------------------------------
In your terminal:
$ adb pull /data/data/com.bn.devicemanager/databases/devicemanager.db devicemanager.db
$ sqlite3 devicemanager.db
sqlite> update registry set value='manual' where name='com.bn.device.fota.mode';
sqlite> .q
$ adb push devicemanager.db /data/data/com.bn.devicemanager/databases/devicemanager.db
$ adb reboot
Congrats Your NC is now permanently blocked from any future BN OTA auto updates.
No more build.prop spoof hacks for each release (sideload only),,,,,, yada yada
sleep like a baby.........with yur wifi on.
Click to expand...
Click to collapse
I like your method better than spoofing the build.prop of 1.1.
Would it be okay with you if I make this into a Clockwork update.zip ?
thecubed said:
I like your method better than spoofing the build.prop of 1.1.
Would it be okay with you if I make this into a Clockwork update.zip ?
Click to expand...
Click to collapse
Absolutely and goes for anyone it might be useful for......
I dont get sqlite 2
Hi All,
Noob quiestion,
I go in adb shell promt "#" by typing "adb shell" in command line.
when I type sqlite3 I get "sqlite3 : not found"
Am I missing anything?
So I have been reading quite a few threads here on XDA, and the one thing I noticed for noobs to linux/unix world is that they are struggling with some basic command once adb shell is gained. I decided to whip out this quick tutorial to help those noobs out to become more of an expert...like me...lol j/k
Here we go:
Prerequisites:
You must know how to invoke a adb shell command already to drop into your phone.
ALL commands in Unix/Linux are case sensitive
For more details, go to this ADB tutorial (very good one): http://forum.xda-developers.com/showthread.php?t=517874
Let's get going:
Once a shell is gained via adb, let's look at some of the basic commands you can do to navigate around the filesystem. Note: you must remove the double-quotes (") for the actual command.
Code:
"cd" = is change directory
to change to any directory, you type: cd dir_name (where dir_name is a full path)
Example: I want to go to /data/local/tmp in my phone, I would do
cd /data/local/tmp <hit ENTER>
You can also use the ".." to go UP one directory.
Example: I'm in /data/local/tmp and I want to go up to /data folder, a command would be: cd ../.. alternatively, if I do cd .. then i'll drop into /data/local folder instead.
Code:
"ls" = list files/directories
to list files/directories within a folder, the command should be:
ls <hit enter> => this will list all NON-HIDDEN file/directories within your CURRENT directory.
ls /data/local/tmp => this will list all NON-HIDDEN file/directories within /data/local/tmp directory.
ls -l => this will list all NON-HIDDEN file/directories within your CURRENT directory, plus additional details. Consider this is like a "Details" view in Windows Explorer.
ls -a => this will list all files/directories (including hidden files) within your CURRENT directory.
ls -la => this will list all files/directories (including hidden files) within your CURRENT directory, plus details.
Code:
"chmod" = change mode
Goes to wikipedia for more details: https://secure.wikimedia.org/wikipedia/en/wiki/Chmod
Most commonly used modes on android phones are:
"755" or "777".
So if you have a root.sh shell script that you downloaded from XDA, and uploaded to your phone and try to execute it with ./root.sh and it said "Permission denied". That means your script does not have the execute permission. You need to do:
chmod 755 root.sh <hit enter>
[B]IMPORTANT: There is *NO* negative sign (-) in front of the mode bit. So it is NOT chmod -755 root.sh[/B]
If you get a "File or directory not found" error, which means you are chmod-ing a file that doesn't exist in your current directory. To execute a chmod on root.sh in /data/local/tmp you do:
chmod 755 /data/local/tmp/root.sh
If you want to chmod an ENTIRE DIRECTORY and ALL files underneath it you do:
chmod -R 755 /data/local/tmp => this will set /data/local/tmp and ALL files/folders underneath it to be 755.
Code:
"chown" = change ownership
Go to wikipedia for details: https://secure.wikimedia.org/wikipedia/en/wiki/Chown
Most common used chown for android is: "root:root" or "root:shell"
Example: if you want to change ownership of root.sh to root:shell then you do:
chown root:shell root.sh
NOTE: the -R (recursive) option is also available for chown.
chown -R root:shell /data/local/tmp
Code:
"pwd" = print working directory
so when you are within a directory and you want to know which directory you are in, then you issue the command:
pwd <hit enter>
The system will reply back with the currently directory you are in.
I'll try to add more if I think of anything else useful, or if you have suggestions, please feel free to add.
so what does it mean to add adb to your path? thats holding me back from temp rooting on my mac. Im a total adb noob clearly.
hockey4life0099 said:
so what does it mean to add adb to your path? thats holding me back from temp rooting on my mac. Im a total adb noob clearly.
Click to expand...
Click to collapse
The easiest way to explain it is that you can run ADB from anywhere...do a search and you can find a more detailed (and more proper) explanation and directions on how to set it up.
hockey4life0099 said:
so what does it mean to add adb to your path? thats holding me back from temp rooting on my mac. Im a total adb noob clearly.
Click to expand...
Click to collapse
What OS are you using?
vboyz103 said:
What OS are you using?
Click to expand...
Click to collapse
mac
______________
hockey4life0099 said:
mac
______________
Click to expand...
Click to collapse
Like I said, do a search on XDA...there's a great guide on how to set up ADB properly. I'll link to it tomorrow when I get on the computer.
-- Sent from my 3VO Shooter --
hockey4life0099 said:
mac
______________
Click to expand...
Click to collapse
If you use mac, open a Terminal, and you should be at your home directory and type:
nano ~/.profile
if the .profile doesn't exist yet, then you'll see an empty.
Put this into the file
PATH=$PATH:/path/to/your/android/platform-tools
export PATH
save and exit out of Nano, and type:
source ~/.profile
then after this type adb and if adb is in your PATH then you see adb help.
Overview Of Permissions via ADB SHELL
Example = drwxrwxrwx
To Check Permission at anytime in ADB just Type:
ls -l
The First character defines the Directory, Link, Binary.
Below are some examples
Example = d---------
d = Directory
l = Link
b = Binary
The next 9 characters define the file permissions. These permissions are
given in groups of 3 each.
The first 3 characters are the permissions for the owner of the file or directory.
Example = -rwx------
The next 3 are permissions for the group that the file is owned by.
Example = ----rwx---
The final 3 characters define the access permissions for everyone not part of the group.
Example = -------rwx
There are 3 possible attributes that make up file access permissions.
r - Read permission. Whether the file may be read. In the case of a
directory, this would mean the ability to list the contents of the
directory.
w - Write permission. Whether the file may be written to or modified. For
a directory, this defines whether you can make any changes to the contents
of the directory. If write permission is not set then you will not be able
to delete, rename or create a file.
x - Execute permission. Whether the file may be executed. In the case of a
directory, this attribute decides whether you have permission to enter,
run a search through that directory or execute some program from that
directory
In addition to the file permission, you can also modify the owner and
group of the file. The chown program is used here and its syntax is very
simple. You need to be the owner of a file or root to do this.
Understanding Owner Permissions:
The first command is for owner ID, the Second Command is for Group ID.
exp. root.root ( First Root is owner, Second Root is Group ).
Chmod 644 some file, Like Build.prop For testing & then Veiw the Resulted Changes!
Refer to the table below as a quick reference.
Command Line for Both would look like this
chmod 644 build.prop = -rw-r--r--
\/
Chmod Guide
0 - ---
1 - --x
2 - -w-
3 - -wx
4 - r--
5 - r-x
6 - rw-
7 - rwx
SH Chown Guide
\/
chown root.root build.prop
root.root = Root
root.shell = Shell
Busybox SH Chown Guide
\/
chown 0.0 build.prop
0.0 = Root
0.2000 = Shell
I'll update the chmod with more with More Complex Commands Later
Side Note:Always set owner ( chown ) before Setting Permissions ( Chmod )!
Hope this Clears up things & is Helpful to everyone
~Eugene373​
Add adb to your path in Windows.
As has been explained above all it does is allowing your adb to be called out from any location.
To set it in windows you will need to add path to your adb.exe file to your PATH in widows XP or CLASSPATH in windows7.
You can find it in start->contro panel->system->advanced.
There is a tab called "Inviromental Variables".
Click on that tab and new window will pop up. New window has 2 field in it. We are interested in bottom field called "System variables".
Windows XP user should look for line with variable "Path".
Click that line and choose edit below. New pop up will apear and you can edit path line in there. You should add path to your adb.exe to that line.
Example.
I did install windows sdk in c:\android\android-sdx-windows so my adb.exe file is in that folder. I did add path to that folder in "Paht" line of system variables. Add path to your adb.exe after semicolon.
;c:\Location\of folder\where you have\adb exe file\
Save changes, apply them. Now you can use call for adb commands from any location.
Widows 7 users.
Same changed need to be appied as for Windows XP.
There is only one difference that that path in Inviromental variables in windows7 is called "CLASSPATH".
Rest is same. Just add the path to folder containing your adb.exe file to CLASSPATH line and you would be able to use adb in any location.
Hope this make sense and will help.
My mac keeps sayin no device but I can access adb from anywhere basically its in my path but won't pick up my phone
Sent from my PG86100 using XDA Premium App
snoopy1e11 said:
My mac keeps sayin no device but I can access adb from anywhere basically its in my path but won't pick up my phone
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
Make sure your phone is in debugging mode.
ADB won't see phone if debugging is not enabled.
It is on
Sent from my PG86100 using XDA Premium App
I'm a windows user.
Can't think of anything else.
Sorry.
agat63 said:
Make sure your phone is in debugging mode.
ADB won't see phone if debugging is not enabled.
Click to expand...
Click to collapse
If you have USB debugging turned on, you should see a triangle with exclamation mark on task bar. Secondly, try to do this:
adb kill-server => kill off current server first
then
sudo adb devices => u need to enter password
Basically, you are running adb with escalated privilege, sometimes it needs root access.
This is Wat I got
Sent from my PG86100 using XDA Premium App
snoopy1e11 said:
This is Wat I got
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
hmmm interesting...just wondering if you have your device turned on to be disk usage instead of just Charge Only?
Check on your desktop to see if you SD card had mounted, not sure if it makes a difference but worth a try. Another thought is that maybe your USB port doesn't work?? Did you check your phone to see if you have a triangle with exclamation mark in it on the task bar? (to the left)
Also, try it on a different computer if u can, and if it still doesn't work, afraid urs is defective.
I really appreciate ur help I re did the sudo command and hit "adb devices connect" and my device popped up
Sent from my PG86100 using XDA Premium App
snoopy1e11 said:
I really appreciate ur help I re did the sudo command and hit "adb devices connect" and my device popped up
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
Ha, interesting cuz I never have to issue that command. Good to know you got it to work.
I just rooted my x2, and installed eclipse. I cant get adb to push, I get permisson denied. I cant do adb remount cuz I get operation not permitted. I had it working once, but now It wont let me do it. Im trying to theme and I need adb push to work. I also tried putting an app on the sdcard and using root explorer to change the apk, all i did was make 1 png edit and the apk wasnt working. Im not sure whats going on and any help would be nice.
TheMuffStuff said:
I just rooted my x2, and installed eclipse. I cant get adb to push, I get permisson denied. I cant do adb remount cuz I get operation not permitted. I had it working once, but now It wont let me do it. Im trying to theme and I need adb push to work. I also tried putting an app on the sdcard and using root explorer to change the apk, all i did was make 1 png edit and the apk wasnt working. Im not sure whats going on and any help would be nice.
Click to expand...
Click to collapse
My Thoughts Are,
PC Mode
Updated Drivers
Correct Path Pointing To ADB Folder Inside Android SDK
Some Computers Need The USB Cable To Be Plugged In The Back Not The Front Due To Front Ports Aren't Supported
Make Sure You're Using The Right Commands ie. adb push <Local> <Remote> -Copy File/Dir To Device
Im gunna try some more today, also when I just make 1 png edit in an apk, and use my sdcard, then root explorer to swap the apks, the new apk gets an error, even tho I only made 1 edit. Its being weird.
Edit: Ive tried PC Mode, updated all drivers. My paths are fine, as im on the same computer that ive done all my theming on for my fascinate/charge. I am using USB's in the back, same one ive always used. Im using the right commands. My phone is rooted using the 1 click script. Im not really sure what else it could be. Im just getting permission errors, I have a feeling its a root problem. I dont know.
Edit:: The only thing I can think of is trying to sbf back to stock, update to pre-rooted gingerbread, and try that?
Honestly it sounds like you are not rooted. I had troubles running the script as well after it came out. I had already rooted earlier in the day using the actual researchers blog instructions.
http://vulnfactory.org/blog/2011/08/25/rooting-the-droid-3/
Those steps are all you need then you can push the su and Superuser.apk files. I wrote a vb script file to install the drives and push the files but I need to do more testing before I put that out for people to try. Using the one click is nice but with everything flying by so fast its easy to miss an error. If you have the one click extracted open a command prompt and navigate to that folder. Then run the commands as follows:
adb shell
mv /data/local/12m /data/local/12m.bak
ln -s /data /data/local/12m
(POWER OFF DEVICE IT WILL REBOOT ON ITS OWN)
adb shell
rm /data/local/12m
mv /data/local/12m.bak /data/local/12m
mv /data/local.prop /data/local.prop.bak
echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop
echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop
echo "ro.sys.atvc_allow_res_core=0" >> /data/local.prop
echo "ro.sys.atvc_allow_res_panic=0" >> /data/local.prop
echo "ro.sys.atvc_allow_all_adb=1" >> /data/local.prop
echo "ro.sys.atvc_allow_all_core=0" >> /data/local.prop
echo "ro.sys.atvc_allow_efem=0" >> /data/local.prop
echo "ro.sys.atvc_allow_bp_log=0" >> /data/local.prop
echo "ro.sys.atvc_allow_ap_mot_log=0" >> /data/local.prop
echo "ro.sys.atvc_allow_gki_log=0" >> /data/local.prop
(POWER CYCLE)
adb shell
(# WILL BE LISTED)
exit
adb remount
adb push busybox /system/xbin/busybox
adb push su /system/xbin/su
adb push Superuser.apk /system/app/Superuser.apk
adb shell chmod 4755 /system/xbin/su
adb shell chmod 755 /system/xbin/busybox
Anything that is in () is not to be typed but informative. The steps above have worked for me on 2 X2's so far and a friends DROID3.
Just in case someone is
This page details how to root the Fujitsu Arrows TAB F-01D.
http://arrowstab-f01d.blogspot.com/2012/03/easy-rooting-toolkit-for-arrows-tab-f.html
it works.
Now if only somebody can post the firmware updates..
English instructions
Well, with some help from Google Translate and some creative interpretations, I managed to do this and thought I'd provide some English instructions for others (with some added comments)
DISCLAIMER: AS USUAL, YOU SHOULD KNOW THAT FOLLOWING THESE ACTIONS (AND ESPECIALLY FOLLOWING THEM INCORRECTLY) CAN BRICK YOUR DEVICE (I.E. YOUR DEVICE WILL STOP WORKING, POSSIBLY PERMANENTLY). I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY ARISE FROM YOU FOLLOWING THESE INSTRUCTIONS, YOU DO SO AT YOUR OWN RISK.
Downloads
1. Windows -- the Arrows TAB USB driver Download.
2. Easy rooting toolkit (ERT) for Arrows Tab F-01D (ver 1.0) Download
3. goroh_kun's lsm_disabler.ko Download
Info
4. A su binary, such as the one found in DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
5. Android SDK platform tools. adb(.exe) (and in Windows, specifically: AdbWinApi.dll, AdbWinUsbApi.dll)
Preparation
1. Unzip ert4F01D.zip, and in the subdirectory 'files' place:
* adb.exe (Windows only, from step 4 above)
* AdbWinApi.dll (Windows only, from step 4 above)
* AdbWinUsbApi.dll (Windows only, from step 4 above)
* lsm_disabler.ko (from step 3 above)
* su (from step 5 above)
2. Before connecting the USB, in Settings -> Applications -> Development:
* Check (tick) USB debugging ("Debug mode when USB is connected")
* Check (tick) Stay awake ("Screen will never sleep while charging")
3. Set up the USB drivers and Android Development stuff if you haven't already. I don't use Windows so can't help with this.
The Dirty Work
At this stage, you can run the batch file. Since I don't use Windows, I did the steps by hand, so you'll have to correlate your actions appropriately (I can't read Japanese either, so your guess is as good as mine ).
1. On your PC:
adb shell "mv /data/local/calib.dat /data/local/calib.dat_"
adb shell "ln -s /data/local.prop /data/local/calib.dat"
2. On the tablet, go into Google Maps, touch the GPS icon ("locate me" icon) on the top right hand corner, and then touch the BACK key to exit.
3. On your PC:
adb shell "echo ro.kernel.qemu=1 > /data/local.prop"
adb shell "rm /data/local/calib.dat"
adb shell "mv /data/local/calib.dat_ /data/local/calib.dat"
adb reboot
5. Once the device has fully rebooted, on your PC:
adb shell "mkdir /data/local/lib"
adb push files\lsm_disabler.ko /data/local/lib/
adb shell "insmod /data/local/lib/lsm_disabler.ko"
adb shell "mkdir /data/local/bin"
adb shell "echo '#!/system/bin/sh' > /data/local/bin/autoexec.sh"
adb shell "echo '/system/xbin/soff' >> /data/local/bin/autoexec.sh"
adb shell "chmod 755 /data/local/bin/autoexec.sh"
adb shell "mount -o rw,remount /system /system"
adb shell "ln -s /data/local/bin/autoexec.sh /system/etc/install-recovery.sh"
adb push files\su /system/xbin/
adb shell "chown root.root /system/xbin/su"
adb shell "chmod 06755 /system/xbin/su"
adb shell "echo insmod /data/local/lib/lsm_disabler.ko > /system/xbin/soff"
adb shell "chmod 755 /system/xbin/soff"
adb shell "mount -o ro,remount /system /system"
adb shell "echo > /data/local.prop"
6. I think at this point I was just meant to exit the lock screen.
7. adb reboot
8. Congratulations. You're now rooted. Go to the Play Store and download "Superuser" (by ChainsDD) and "BusyBox" (by Stericson). If you decide to buy BusyBox Pro, do not check the "symlinks" option in version 8.0, otherwise it's game over (no wifi, no adb shell, no root, no remount). It's a pain, but not impossible to repair this situation, see http://forum.xda-developers.com/showthread.php?p=26964465. I've emailed the author and I hope future versions won't trash the system so easily.
After all this, I'd suggest download Titanium Backup for Root users, backing everything up, and uninstall the all the bloatware that came with the device. Read up elsewhere about Titanium Backup.
Let me know if this helped you! Not sure how many other English speakers are using this device
Thank you for this wonderful post! A few questions:
1.) I use the F-01D but I don't live in Japan. One of the gripes I've been having about this tablet is that there doesn't seem to be anyway for me to get firmware updates unless I go there. Once rooted am I able to use Market Enabler to fake a carrier and update my tablet?
2.) This is slightly off on a tangent but since I can't find much English material about this tablet anway I might as well ask here. Another one of my gripes about the tablet is it doesn't seem to handle video very well. even 720p video doesn't play smoothly on it. On most of the software I download, it seems hardware acceleration is not enabled? Is this a hardware issue, or is it blocked by the software. And if the latter would rooting the tablet help resolve this issue; or is there any other solution? From what I've read the OMAP processor in this thing should easily be able to handle 1080p video right?
Many thanks! :good:
Kinslayer81 said:
Well, with some help from Google Translate and some creative interpretations, I managed to do this and thought I'd provide some English instructions for others (with some added comments)
DISCLAIMER: AS USUAL, YOU SHOULD KNOW THAT FOLLOWING THESE ACTIONS (AND ESPECIALLY FOLLOWING THEM INCORRECTLY) CAN BRICK YOUR DEVICE (I.E. YOUR DEVICE WILL STOP WORKING, POSSIBLY PERMANENTLY). I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY ARISE FROM YOU FOLLOWING THESE INSTRUCTIONS, YOU DO SO AT YOUR OWN RISK.
Downloads
1. Windows -- the Arrows TAB USB driver Download.
2. Easy rooting toolkit (ERT) for Arrows Tab F-01D (ver 1.0) Download
3. goroh_kun's lsm_disabler.ko Download
Info
4. A su binary, such as the one found in DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
5. Android SDK platform tools. adb(.exe) (and in Windows, specifically: AdbWinApi.dll, AdbWinUsbApi.dll)
Preparation
1. Unzip ert4F01D.zip, and in the subdirectory 'files' place:
* adb.exe (Windows only, from step 4 above)
* AdbWinApi.dll (Windows only, from step 4 above)
* AdbWinUsbApi.dll (Windows only, from step 4 above)
* lsm_disabler.ko (from step 3 above)
* su (from step 5 above)
2. Before connecting the USB, in Settings -> Applications -> Development:
* Check (tick) USB debugging ("Debug mode when USB is connected")
* Check (tick) Stay awake ("Screen will never sleep while charging")
3. Set up the USB drivers and Android Development stuff if you haven't already. I don't use Windows so can't help with this.
The Dirty Work
At this stage, you can run the batch file. Since I don't use Windows, I did the steps by hand, so you'll have to correlate your actions appropriately (I can't read Japanese either, so your guess is as good as mine ).
1. On your PC:
adb shell "mv /data/local/calib.dat /data/local/calib.dat_"
adb shell "ln -s /data/local.prop /data/local/calib.dat"
2. On the tablet, go into Google Maps, touch the GPS icon ("locate me" icon) on the top right hand corner, and then touch the BACK key to exit.
3. On your PC:
adb shell "echo ro.kernel.qemu=1 > /data/local.prop"
adb shell "rm /data/local/calib.dat"
adb shell "mv /data/local/calib.dat_ /data/local/calib.dat"
adb reboot
5. Once the device has fully rebooted, on your PC:
adb shell "mkdir /data/local/lib"
adb push files\lsm_disabler.ko /data/local/lib/
adb shell "insmod /data/local/lib/lsm_disabler.ko"
adb shell "mkdir /data/local/bin"
adb shell "echo '#!/system/bin/sh' > /data/local/bin/autoexec.sh"
adb shell "echo '/system/xbin/soff' >> /data/local/bin/autoexec.sh"
adb shell "chmod 755 /data/local/bin/autoexec.sh"
adb shell "mount -o rw,remount /system /system"
adb shell "ln -s /data/local/bin/autoexec.sh /system/etc/install-recovery.sh"
adb push files\su /system/xbin/
adb shell "chown root.root /system/xbin/su"
adb shell "chmod 06755 /system/xbin/su"
adb shell "echo insmod /data/local/lib/lsm_disabler.ko > /system/xbin/soff"
adb shell "chmod 755 /system/xbin/soff"
adb shell "mount -o ro,remount /system /system"
adb shell "echo > /data/local.prop"
6. I think at this point I was just meant to exit the lock screen.
7. adb reboot
8. Congratulations. You're now rooted. Go to the Play Store and download "Superuser" (by ChainsDD) and "BusyBox" (by Stericson). If you decide to buy BusyBox Pro, do not check the "symlinks" option in version 8.0, otherwise it's game over (no wifi, no adb shell, no root, no remount). It's a pain, but not impossible to repair this situation, see http://forum.xda-developers.com/showthread.php?p=26964465. I've emailed the author and I hope future versions won't trash the system so easily.
After all this, I'd suggest download Titanium Backup for Root users, backing everything up, and uninstall the all the bloatware that came with the device. Read up elsewhere about Titanium Backup.
Let me know if this helped you! Not sure how many other English speakers are using this device
Click to expand...
Click to collapse
Just wanted to say thank you again. The rooting worked perfectly, though it took me a while to manually type in all the commands. For people who want to try this, you do need to install busybox before any other programs such as rootchecker will properly verify that your device is actually rooted.
And just for anyone wondering - rooting and using MarketEnabler has NOT been able to resolve the issue of not being able to update the software overseas...
Hey, sorry for the late reply, busy times :>
Glad the post helped you! I know I was super amped to finally get rood and get rid of all the bloatware I couldn't even understand. Things have definitely been a lot smoother since then (but far from perfect, also dying for an ICS upgrade). As for your questions:
simzhewei said:
1.) I use the F-01D but I don't live in Japan. One of the gripes I've been having about this tablet is that there doesn't seem to be anyway for me to get firmware updates unless I go there. Once rooted am I able to use Market Enabler to fake a carrier and update my tablet?
Click to expand...
Click to collapse
From playing around, the requirements seem to imply that you *have to* upgrade via cellular data from a Docomo SIM card, and it can't be done via roaming, so yeah, it seems like you have to physically go to Japan to upgrade Your market enabler idea was a good one, but since you tried that (I'm assuming using the Docomo info), I guess the upgrade app is using a different source to check where you're at. Ultimately we need to somehow get hold of an update.zip (or other file) that can be run through the Recovery system (which does exist!).
2.) This is slightly off on a tangent but since I can't find much English material about this tablet anway I might as well ask here. Another one of my gripes about the tablet is it doesn't seem to handle video very well. even 720p video doesn't play smoothly on it. On most of the software I download, it seems hardware acceleration is not enabled? Is this a hardware issue, or is it blocked by the software. And if the latter would rooting the tablet help resolve this issue; or is there any other solution? From what I've read the OMAP processor in this thing should easily be able to handle 1080p video right?
Click to expand...
Click to collapse
Haven't tried 1080p, but after some tinkering I did get 720p playing. I use MX Player, and although they said it would download needed hardware decoders automatically, it didn't, and things improved a lot after I downloaded the MX Player ARMv7 codec. Video plays great, but to get sound, I had to run the sound through the software decoder (just tap the music note icon, and choose "Track #1 (S/W decoder)".
On the other hand, I found the hardware decoding often gets stuck (relaunching MX player just gives you a waiting indicator forever)... and the only way to fix it is a reboot. Since this happens quite often, it's incredibly annoying, and I'm hoping an upgrade will fix it. Let me know if this doesn't happen to you. Also have some very intermittent wifi issues, some things work fine (speedtest, etc) but apps like streaming radio, some work fine (spotify) and others don't work at all (di radio). Some things work fine for a while after a reboot.
---------- Post added at 10:02 AM ---------- Previous post was at 10:00 AM ----------
Incidentally, here's what happens if I try update via recovery (with no update files). Maybe it will help someone. Googling most of the stuff came up with nothing. The ** in the middle somewhere is stuff I couldn't read, guess I should go back and do it again but this is from quite a while ago.
Code:
C_L1_043
2.6.35.7
V19R36D
=======================
SD Downloader
=======================
Device SW Downloading...
Don't remove
the SD Card & the Battery.
checking battery
eMMC SD mount complete.
microSD mount complete.
Firm name :
Firm name :
Target:
Check eMMC(SD).
Firm name :
Update GANG file not found
File open error!
**ddl Touch Firm Write start
Firm name :
/external_sd/I2C_HSSP_Bridge_Parallel.cyacd file not found
firm name :
/sdcard/I2C_HSSP_Bridge_Parallel.cyacd file not found
#sddl touch firm not found ret: 1
SKIP sddl launch firm write end ret: 1
SD : SdFgldfirmwrite -------
firm name :
BAC_H_19.enc =
firm name :
BAC_H_1.9.enc =
error
SKIP sddl fgic firm write end ret: 1
end
****************************
****************************
****
All firmware not found!
****
Interesting situation...
First off...Kinslayer81, thanks for posting this. I found the original in Japanese, and was not eager to try to translate it. Thanks for putting in the work.
For everyone (especially if you got this to work) - when I went through the step, I keep getting a "permissions denied" message. Whether it's the ERT4F01D batch file, or typing the commands in... I get "permissions denied".
Did you guys encounter this?
Glad it helped you On which step are you getting the error? Any strange output on any of the preceding steps?
Every step is important, to be done in the exact same order, e.g. loading google maps and pressing the 'my location' icon, etc.
Dakedo_Baby said:
First off...Kinslayer81, thanks for posting this. I found the original in Japanese, and was not eager to try to translate it. Thanks for putting in the work.
For everyone (especially if you got this to work) - when I went through the step, I keep getting a "permissions denied" message. Whether it's the ERT4F01D batch file, or typing the commands in... I get "permissions denied".
Did you guys encounter this?
Click to expand...
Click to collapse
Permission denied
Oh I know... I'm not new to the game. I've stalked these boards for a while now... This is my first tablet though.
I've tried running both the ERT4F01D batch... and the manual input.
I get it from the batch file, as soon as I tell it to "RUN"... "Permissions Denied"
From manual input - LINE 2: adb shell "ln -s /data/local.prop /data/local/calib.dat" = "Permissions Denied"
Like there's some additional admin privilege I don't have. Hmmmmm....
And here's an additional kicker... the tablet auto-reboots each and every time. I've tried it a number of times (started over from the top), same result each time.
Kinslayer81 said:
Glad it helped you On which step are you getting the error? Any strange output on any of the preceding steps?
Every step is important, to be done in the exact same order, e.g. loading google maps and pressing the 'my location' icon, etc.
Click to expand...
Click to collapse
I must admit, I don't have any great ideas.
So you can move the file in the first step no problem, and just the attempt to symlink gives you the error?
What is the output of "adb shell ls -la /data/local/".
When does the auto reboot occur?
Dakedo_Baby said:
Oh I know... I'm not new to the game. I've stalked these boards for a while now... This is my first tablet though.
I've tried running both the ERT4F01D batch... and the manual input.
I get it from the batch file, as soon as I tell it to "RUN"... "Permissions Denied"
From manual input - LINE 2: adb shell "ln -s /data/local.prop /data/local/calib.dat" = "Permissions Denied"
Like there's some additional admin privilege I don't have. Hmmmmm....
And here's an additional kicker... the tablet auto-reboots each and every time. I've tried it a number of times (started over from the top), same result each time.
Click to expand...
Click to collapse
I'm stumped too...
Well... this is getting a little interesting...
LS command - no problem (included image)
Decided to have another shot at it... and I was able to get a little further. Still encountered a problem
Now, the INSMOD command failed... "Operation not permitted"
Kinslayer81 said:
I must admit, I don't have any great ideas.
So you can move the file in the first step no problem, and just the attempt to symlink gives you the error?
What is the output of "adb shell ls -la /data/local/".
When does the auto reboot occur?
Click to expand...
Click to collapse
file system set to READ-only...
My file systems are set to Read-only... that explains quite a bit....
Dakedo_Baby said:
Well... this is getting a little interesting...
LS command - no problem (included image)
Decided to have another shot at it... and I was able to get a little further. Still encountered a problem
Now, the INSMOD command failed... "Operation not permitted"
Click to expand...
Click to collapse
Dakedo_Baby said:
My file systems are set to Read-only... that explains quite a bit....
Click to expand...
Click to collapse
Do you mind me asking, how did you set your file system to read-write? I have the same error as you were seeing but it's not allowing me to remount as read-write...
Can you confirm what command you used please?
thanks
Sorry again for late reply
Dakedo_Baby, I've looked at your stuff a few times and it's not obvious to me where things are going wrong. I again need some more info to try get a better idea of what's going on:
1) Before the first reboot, let me know the output of: adb shell "cat /data/local.prop"
2) After the reboot, let me know the output of: adb shell id
As for the file systems, well, /data should be already mounted rw, and /system should be mounted ro until you remount it. You can see how each is mounted with just "adb mount".
histrix said:
Do you mind me asking, how did you set your file system to read-write? I have the same error as you were seeing but it's not allowing me to remount as read-write...
Can you confirm what command you used please?
thanks
Click to expand...
Click to collapse
The command to remount the /system partition as read-write is: adb shell "mount -o rw,remount /system /system"
Of course, you should only be executing that step as part of the given sequence and in the correct order. You won't be able to execute the command until after your first reboot in the instructions, after which adb should still be running as root.
Any good Custom ICS roms you guys recommend after rooting the Arrows Tab?
ICS..Hurray!!!
Just found this out in Fujitsu site:
http://spf.fmworld.net/fujitsu/c/update/nttdocomo/f-01d/update1/top/index.html
There is a 4.0.3 download available. Click the 3rd Button (Green) downloads the zip package.
The 2nd link has howto from PC.
Still not sure if this will work, but trying out.
Also may lose root..and whatever else..So keeping my fingers crossed.
Google translation link
http://translate.google.com/transla...update/nttdocomo/f-01d/update1/top/index.html
Will post how it goes.
I made a new thread for this, since it's a different topic and you'll lose root too
http://forum.xda-developers.com/showthread.php?p=32200671
insmod lsm-disabler.so to remount /system rw
Back to the original topic... what I maybe didn't notice before is that the stock kernel blocks even root users from remounting /system as rw. So in case you ever need rw access to /system again, obviously you'll first have to be root, and afterwards you'll need to "insmod lsm-disabler.so" (as per the original instructions) before you can "busybox mount -o remount,rw /system" (or run any root app that remounts the system partition).
locked F-01d
Kinslayer81 said:
Well, with some help from Google Translate and some creative interpretations, I managed to do this and thought I'd provide some English instructions for others (with some added comments)
DISCLAIMER: AS USUAL, YOU SHOULD KNOW THAT FOLLOWING THESE ACTIONS (AND ESPECIALLY FOLLOWING THEM INCORRECTLY) CAN BRICK YOUR DEVICE (I.E. YOUR DEVICE WILL STOP WORKING, POSSIBLY PERMANENTLY). I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY ARISE FROM YOU FOLLOWING THESE INSTRUCTIONS, YOU DO SO AT YOUR OWN RISK.
Downloads
1. Windows -- the Arrows TAB USB driver Download.
2. Easy rooting toolkit (ERT) for Arrows Tab F-01D (ver 1.0) Download
3. goroh_kun's lsm_disabler.ko Download
Info
4. A su binary, such as the one found in DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
5. Android SDK platform tools. adb(.exe) (and in Windows, specifically: AdbWinApi.dll, AdbWinUsbApi.dll)
Preparation
1. Unzip ert4F01D.zip, and in the subdirectory 'files' place:
* adb.exe (Windows only, from step 4 above)
* AdbWinApi.dll (Windows only, from step 4 above)
* AdbWinUsbApi.dll (Windows only, from step 4 above)
* lsm_disabler.ko (from step 3 above)
* su (from step 5 above)
2. Before connecting the USB, in Settings -> Applications -> Development:
* Check (tick) USB debugging ("Debug mode when USB is connected")
* Check (tick) Stay awake ("Screen will never sleep while charging")
3. Set up the USB drivers and Android Development stuff if you haven't already. I don't use Windows so can't help with this.
The Dirty Work
At this stage, you can run the batch file. Since I don't use Windows, I did the steps by hand, so you'll have to correlate your actions appropriately (I can't read Japanese either, so your guess is as good as mine ).
1. On your PC:
adb shell "mv /data/local/calib.dat /data/local/calib.dat_"
adb shell "ln -s /data/local.prop /data/local/calib.dat"
2. On the tablet, go into Google Maps, touch the GPS icon ("locate me" icon) on the top right hand corner, and then touch the BACK key to exit.
3. On your PC:
adb shell "echo ro.kernel.qemu=1 > /data/local.prop"
adb shell "rm /data/local/calib.dat"
adb shell "mv /data/local/calib.dat_ /data/local/calib.dat"
adb reboot
5. Once the device has fully rebooted, on your PC:
adb shell "mkdir /data/local/lib"
adb push files\lsm_disabler.ko /data/local/lib/
adb shell "insmod /data/local/lib/lsm_disabler.ko"
adb shell "mkdir /data/local/bin"
adb shell "echo '#!/system/bin/sh' > /data/local/bin/autoexec.sh"
adb shell "echo '/system/xbin/soff' >> /data/local/bin/autoexec.sh"
adb shell "chmod 755 /data/local/bin/autoexec.sh"
adb shell "mount -o rw,remount /system /system"
adb shell "ln -s /data/local/bin/autoexec.sh /system/etc/install-recovery.sh"
adb push files\su /system/xbin/
adb shell "chown root.root /system/xbin/su"
adb shell "chmod 06755 /system/xbin/su"
adb shell "echo insmod /data/local/lib/lsm_disabler.ko > /system/xbin/soff"
adb shell "chmod 755 /system/xbin/soff"
adb shell "mount -o ro,remount /system /system"
adb shell "echo > /data/local.prop"
6. I think at this point I was just meant to exit the lock screen.
7. adb reboot
8. Congratulations. You're now rooted. Go to the Play Store and download "Superuser" (by ChainsDD) and "BusyBox" (by Stericson). If you decide to buy BusyBox Pro, do not check the "symlinks" option in version 8.0, otherwise it's game over (no wifi, no adb shell, no root, no remount). It's a pain, but not impossible to repair this situation, see http://forum.xda-developers.com/showthread.php?p=26964465. I've emailed the author and I hope future versions won't trash the system so easily.
After all this, I'd suggest download Titanium Backup for Root users, backing everything up, and uninstall the all the bloatware that came with the device. Read up elsewhere about Titanium Backup.
Let me know if this helped you! Not sure how many other English speakers are using this device
Click to expand...
Click to collapse
thanks for the rooting tutorial but mine is also locked to ntt DOCOMO,,,ANY WAY TO UNLOCK IT
how to unlock the network
please help me how to unlock this tablet i got this tablet from my japan friend but it is network locked please help me to unlock this