Related
Anyone been able to ssh in through the USB connection?
I've done it with other Android phones, but here when I connect the USB cable, it doesn't even bring up the usb0 interface on my GNU/Linux PC, so don't know what's wrong...
Anyone doing it?
You need usb debugging active in settings. You will use adb shell command, not ssh (at least not without an android ssh server app).
Right, it does seem no android ssh server app is available to work over USB.
I was able to do, after redirecting ports from the local PC to the phone via adb, as per http://forum.xda-developers.com/showpost.php?p=20104928&postcount=71
However, interestingly, I cannot ssh in via wifi, as per symptoms in the above posts, i.e. the Galaxy Note will not initiate the connection, although using the same software on a Motorola Droid 3 will connect, so it must be some peculiar setup about the Note. In the thread many other users, notably it seems of Galaxy2 note the same inability to connect.
Anyone been able to connect through ssh via wifi? What am I missing?
any updates on this? I can't connect as well. I'm using sshdroid.
I gave up on SSH via USB, seems it's messed up under android. Just using the wifi method as per above.
There might be some hope with CM9, using the latest kernel, will see...
I tried using the earlier post by 白い熊 (!) which is basically noed's tip and it working beautifully. I think noed made a typo.
This is how it works for me :
1) Installed busybox/droidsshd
2) Connected to the windows pc which had drivers (kies)
3) Issued adb forward tcp:22 tcp:2222 (this is because droidsshd listens at 2222, when i changed that to 22, it worked also)
4) putty to 127.0.0.1 worked (I enabled root and set password in droidsshd prefernces -> Service and Authentication)
Due to busybox, i could run natural linux commands like ps, grep, find. top also worked showing what application bogging cpu - droidsshd for me
Yeah, the problem with this is the adb part... Running it in a Linux box, after a while adb consumes most of the memory, I have to kill it and restart, the connection gets dropped often too. Just a very poor experience, not the solidity you need for sshfs for instance...
Download a cyanogenmod 7 rom and extract dropbear, dropbearkey and dropbearconvert from the /system/xbin/ directory. Dropbear is a lightweight alternative to sshd. Copy them over to the phone, move them to /system/xbin/ and give them the permissions and ownership they had in the archive.
Generate an ssh key for your desktop if you don't have one already: ssh-keygen -t rsa
Copy the public key to the phone: adb push .ssh/id_rsa.pub /sdcard/authorized_keys
Set up your keys on your phone via adb shell:
mkdir /data/dropbear
chmod 755 /data/dropbear
mkdir /data/dropbear/.ssh
chmod 700 /data/dropbear/.ssh
mv /sdcard/authorized_keys /data/dropbear/.ssh/
chown root.root /data/dropbear/.ssh/authorized_keys
chmod 600 /data/dropbear/.ssh/authorized_keys
dropbearkey -t rsa -f /data/dropbear/dropbear_rsa_host_key
dropbearkey -t dss -f /data/dropbear/dropbear_dss_host_key
Run dropbear on your phone in a terminal or using adb shell: dropbear -s -F -v -p 2222
Connect from your desktop: ssh -i .ssh/id_rsa -p 2222 -l root 127.0.0.1
Upfronts: I'm using NottachTrix 1.3.1 with the 2.3.6 Webtop. I'm also a programmer and a network administrator, so I might be a little more comfortable poking around in things that might break my phone than other users. Don't do anything you aren't comfortable with! I'm just reporting my findings. Your phone, your comfort level, your business!
I wanted to get my new lapdock to use the cellular network without jumping through any "enable/disable mobile hotspot" hoops. I finally got all the webtop2sd stuff running, including a working lxterminal and synaptic. I was running synaptic as root from a bash shell ("sudo bash" to give me a root shell, other commands as needed). I noticed that synaptic worked without wifi but firefox didn't. I could also ping various websites with no trouble under the root shell, but the adas user could not. adas COULD ping IP addresses, though, so it seemed like there was a firewall in place that was blocking adas from resolving domain names.
As it turns out, there is a firewall in place that is blocking the adas user from resolving domain names.
Webtop seems to be using iptables to restrict access to the default login user. I typed "iptables -L" to view all the iptables-based firewalling that was going on. Sure enough, three entries existed to block network traffic for the user "adas". After an "iptables -S" to get the commands that were used to turn on the filtering, I was able to reverse the process. (Hint: -A adds a rule, -D deletes one)
From here, I could do a lot of things -- create a script to disable iptables on demand, block the commands from running in the first place, dance a happy little jig... I won't embarrass myself by revealing which I actually did, but hopefully there's enough in this post that will help others resolve their problems in a similar manner!
(By the way, every time the phone is docked, it re-blocks network access, apparently using a file called "syslog-restart".)
If you could fix this would be great, I have the same rom and everything and I use my LapDock in my business and it is always a pain to make it connect and most of the times it fails to connect for me.
Cheers
The following presumes a working lxterminal and synaptic (or apt-get). If you haven't run the webtopscripts to fix the broken dependencies, now's a good time to poke that bear*.
(Type the stuff that's in bold -- comments are in italics)
In lxterminal:
sudo apt-get install nano (Command-line text editor)
iptables -S (generates a list of rules that iptables is currently using)
copy any lines in the "-P OUTPUT ACCEPT" section that start with "-A"
create a new file in nano by typing nano fwdisable.sh
at the top of the new document, type #!/bin/bash and press Enter
paste the copied lines into the resulting screen
insert iptables at the start of each line and change "-A" to "-D" (A for add, D for delete)
once the file looks the way you think it should, exit the program with CTRL-X, saving the file when it asks
at the command prompt, type chmod 755 fwdisable.sh
run your new shell script with sudo ./fwdisable.sh
open up a web browser and enjoy!
* Please don't poke any bears. While they may look fluffy, they react poorly to being poked. There's probably a good metaphor about messing around in the internals of your phone in there somewhere, but for the life of me I just can't find it!
Did you guys can edit a ROM that has it all in a matter of WebTop, I can not make it work on my Atrix in any way.
I do not have the device only the HDMI cable.
Trying to save fwdisable.sh nano give me following error
"Error writing fwdisable.sh Read-only file system"
Please advise
pederb said:
Trying to save fwdisable.sh nano give me following error
"Error writing fwdisable.sh Read-only file system"
Please advise
Click to expand...
Click to collapse
Sounds like you're not root or su
Sent from my MB860 using Tapatalk 2
Ok the drive was write protected, but now I get
" ./fwdisable.sh: line 2: -D: command not found"
" ./fwdisable.sh: line 3: -D: command not found"
I was not able to get it to work with Nano so I used gedit instead but should not make a difference, right?
Any idea?
maybe someone can create a flashable fix so that its easy for some of us noobs lol
studean said:
The following presumes a working lxterminal and synaptic (or apt-get). If you haven't run the webtopscripts to fix the broken dependencies, now's a good time to poke that bear*.
(Type the stuff that's in bold -- comments are in italics)
In lxterminal:
sudo apt-get install nano (Command-line text editor)
iptables -S (generates a list of rules that iptables is currently using)
copy any lines in the "-P OUTPUT ACCEPT" section that start with "-A"
create a new file in nano by typing nano fwdisable.sh
at the top of the new document, type #!/bin/bash and press Enter
paste the copied lines into the resulting screen
insert iptables at the start of each line and change "-A" to "-D" (A for add, D for delete)
once the file looks the way you think it should, exit the program with CTRL-X, saving the file when it asks
at the command prompt, type chmod 755 fwdisable.sh
run your new shell script with sudo ./fwdisable.sh
open up a web browser and enjoy!
* Please don't poke any bears. While they may look fluffy, they react poorly to being poked. There's probably a good metaphor about messing around in the internals of your phone in there somewhere, but for the life of me I just can't find it!
Click to expand...
Click to collapse
Follow this guide guys, it is ridiculously easy, no flashing needed.
I also added a button to the AWN dock with the command:
sudo ./fwdisable.sh
Which will give you one click disabling of the firewall. It will restart the firewall each time you dock/undock it appears, so just dock it, click the firewall disable button and you are good to go.
Norcalz71 said:
Follow this guide guys, it is ridiculously easy, no flashing needed.
I also added a button to the AWN dock with the command:
sudo ./fwdisable.sh
Which will give you one click disabling of the firewall. It will restart the firewall each time you dock/undock it appears, so just dock it, click the firewall disable button and you are good to go.
Click to expand...
Click to collapse
Well I'm still getting my error no matter how many time I try it again
man i cant even get webtop2sd to work. as soon as i run it on my phone it force closes. i havent even got it to open longer then super user request yet.
fingers crossed on a cwm flashable lol.
Thanks for this. I was wondering why apt-get update would work but adas couldn't ping out properly over 3g.
Also, thank you for the walk through in editing iptables there. Interesting that they chose to use that over something more proprietary, or well hidden.
I had this problem at first, too -- I think it was busybox-related. There's a busybox updater or two in the Market (I mean, "Play Store") that will bring you up to speed and let you install webtop2sd.
Sorry it's been so long since my last post! It appears that you didn't insert an "iptables " before the "-D". Check to make sure that each line after the "#!/bin/bash" starts with "iptables -D" instead of just "-D" and see if that takes care of the problem. (Also make sure you execute the script with a "sudo" -- iptables won't work properly as a regular user...)
studean said:
Sorry it's been so long since my last post! It appears that you didn't insert an "iptables " before the "-D". Check to make sure that each line after the "#!/bin/bash" starts with "iptables -D" instead of just "-D" and see if that takes care of the problem. (Also make sure you execute the script with a "sudo" -- iptables won't work properly as a regular user...)
Click to expand...
Click to collapse
should it be,
iptables -D
or
-D iptables
[email protected]:/$ sudo iptables -S
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
FATAL: Could not load /lib/modules/2.6.32.56-MB860-faux123-GB-024/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.32.56-MB860-faux123-GB-024/modules.dep: No such file or directory
-A OUTPUT -d 127.0.0.1/32 -p tcp -m tcp --dport 8086 -m owner ! --uid-owner adas -j REJECT --reject-with icmp-port-unreachable
-A OUTPUT -d 127.0.0.1/32 -p tcp -m tcp --dport 8085 -m owner ! --uid-owner adas -j REJECT --reject-with icmp-port-unreachable
This is how it looks before editing
It should be "iptables -D". Based on the output from your "iptables -S" command, the file should look like this:
Code:
#/bin/bash
iptables -D OUTPUT -d 127.0.0.1/32 -p tcp -m tcp --dport 8086 -m owner ! --uid-owner adas -j REJECT --reject-with icmp-port-unreachable
iptables -D OUTPUT -d 127.0.0.1/32 -p tcp -m tcp --dport 8085 -m owner ! --uid-owner adas -j REJECT --reject-with icmp-port-unreachable
I also had a third line (that escapes me at the moment -- I'm on a different machine) that further blocked access, but apparently there is a bit of variation in the configuration... At any rate, create the file using whatever text editor you feel most comfortable using, then "chmod 755" the file to make it executable. If you call it "fwdisable.sh", then you should type "chmod 755 fwdisable.sh" in lxterminal and run the file with "sudo ./fwdisable.sh" to disable the firewall.
Good luck! If you want to know more about the workings of this stuff, google "bash scripting guide" and (for a general overview) read the wikipedia page for "iptables". It will help you understand what's up with all these seemingly weird commands...
That worked, but now I get these error messages?
[email protected]:/$ sudo ./fwdisable.sh
FATAL: Could not load /lib/modules/2.6.32.56-MB860-faux123-GB-024/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.32.56-MB860-faux123-GB-024/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.32.56-MB860-faux123-GB-024/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.32.56-MB860-faux123-GB-024/modules.dep: No such file or directory
[email protected]:/$
Click to expand...
Click to collapse
Please advice
Cheers
You should be okay with those error messages. I'm not entirely sure WHY it's looking for that file, but it's "normal" output. If you'll remember, it's the same output you got in the "iptables -S" command... Something about accessing iptables causes the system to look for that file. (I just haven't been bothered enough over it to check yet...)
To verify, run "sudo iptables -S" again to see if there is anything left. You should just see three lines:
Code:
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
Anything more than that and you might need to edit your script as you did before. If the output from "iptables -S" looks like the above, though, fire up firefox and give it a whirl!
studean said:
You should be okay with those error messages. I'm not entirely sure WHY it's looking for that file, but it's "normal" output. If you'll remember, it's the same output you got in the "iptables -S" command... Something about accessing iptables causes the system to look for that file. (I just haven't been bothered enough over it to check yet...)
To verify, run "sudo iptables -S" again to see if there is anything left. You should just see three lines:
Code:
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
Anything more than that and you might need to edit your script as you did before. If the output from "iptables -S" looks like the above, though, fire up firefox and give it a whirl!
Click to expand...
Click to collapse
[email protected]:/$ sudo iptables -S
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
FATAL: Could not load /lib/modules/2.6.32.56-MB860-faux123-GB-024/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.32.56-MB860-faux123-GB-024/modules.dep: No such file or directory
-A OUTPUT -o ppp0 -m owner --uid-owner adas -j REJECT --reject-with icmp-port-unreachable
[email protected]:/$
Excellent! This means you're almost there! As before, copy/paste that line into your shell script, change the "-A" to "iptables -D" and that SHOULD be the end of it.
No, really. This time for sure. Just re-run the script when you're done (ignoring the "fatal" stuff) and you'll be browsing in no time!
hi i have read numerous posts and tried many tutorials on here but cant seem to get anywhere with my kindle
fire i believe its a kindle fire 2nd gen as sytem version is 10.2.6
im using win xp on my pc and in device manager i have
kindle fire - android composite ADB interface
MTP has exclamation mark by it and wont load any drivers i have windows media player 11 installed.
it doesnt show up in my computer at all which i think is where the problem may lie
can anyone point me in the right direction on turning my kindle fire into an android device
and not amazon.... thanks in advance
inflicted_1999 said:
hi i have read numerous posts and tried many tutorials on here but cant seem to get anywhere with my kindle
fire i believe its a kindle fire 2nd gen as sytem version is 10.2.6
im using win xp on my pc and in device manager i have
kindle fire - android composite ADB interface
MTP has exclamation mark by it and wont load any drivers i have windows media player 11 installed.
it doesnt show up in my computer at all which i think is where the problem may lie
can anyone point me in the right direction on turning my kindle fire into an android device
and not amazon.... thanks in advance
Click to expand...
Click to collapse
Just got my 2nd gen in the mail today, started reading up on how to root 10.2.4, was feeling good about it, ready to get started and noticed that it was in the middle of upgrading to 10.2.6. guess I'll be following this thread, hope something comes along soon...
How To: Root the Kindle Fire 7" 2 with Windows - Version 10.2.6
inflicted_1999 said:
hi i have read numerous posts and tried many tutorials on here but cant seem to get anywhere with my kindle
fire i believe its a kindle fire 2nd gen as sytem version is 10.2.6
im using win xp on my pc and in device manager i have
kindle fire - android composite ADB interface
MTP has exclamation mark by it and wont load any drivers i have windows media player 11 installed.
it doesnt show up in my computer at all which i think is where the problem may lie
can anyone point me in the right direction on turning my kindle fire into an android device
and not amazon.... thanks in advance
Click to expand...
Click to collapse
inflicted_1999,
I am sorry to hear your frustrations around Rooting the Kindle Fire 2 version 10.2.6, this can be a bugger to Root. I have an idea that may help you. When you have a yellow triangle over MTP, this is a strong sign that the driver is not functional. When you have the combination of, one Android Composite ADB Interface with the yellow triangle over MTP, you have a driver failure. Having said this, none of the utilities will work until you have a functional driver. Just FYI Windows Media Player is not needed to get the Kindle to Root. Once you have successfully installed the driver Android Composite ADB Interface will change to Android ADB Interface and the MTP will change to Portable Devices > Kindle. You will also know the driver install was successful when you get a pop-up asking what to do with the Kindle Drive - like sync it with your MP3 collection.
If you already tried Part A for the driver, here are the key points:
Note: Windows 7 and Vista users, please perform this fix before Rooting: http://forum.xda-developers.com/show...php?p=36373627
A) The first step is to get the ADB Driver installed. If you already performed this step and verified communication to the Kindle.
Please open an Administrative CMD Prompt and enter:
Code:
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Note: We have seen quite a few cases when the driver "fails to install". This message is normally erroneous and can usually be ignored. Plug in your Kindle, then look in the Windows Device Manager to see if the main driver installed.
Our friends at RevTV Created this video which outlines How to install ADB: How to Install ADB Video
The following ADB Driver was provided by Amazon and should install on most platforms (Windows XP, Vista, 7, and 8): Kindle Fire ADB drivers
Note: Due to intermittent issues with the USB Drivers, we offer two versions. First try Kindle Fire ADB drivers.exe if this
does not open ADB Communication try the new updated KindleDrivers.exe
This worked for me
inflicted_1999 said:
hi i have read numerous posts and tried many tutorials on here but cant seem to get anywhere with my kindle
fire i believe its a kindle fire 2nd gen as sytem version is 10.2.6
im using win xp on my pc and in device manager i have
kindle fire - android composite ADB interface
MTP has exclamation mark by it and wont load any drivers i have windows media player 11 installed.
it doesnt show up in my computer at all which i think is where the problem may lie
can anyone point me in the right direction on turning my kindle fire into an android device
and not amazon.... thanks in advance
Click to expand...
Click to collapse
I’m a n00b to this, but this worked for me. I had root than lost it because I didn’t disable auto update. The only way I could get root back is like this.
1. Use Prokennexusa steps to get your comp talking to your kindle, if you run win 7 or Vista make sure you heed the warning. Next find and download “Root_with_Restore_by_Bin4ry_v18” to your desktop and make two copies of it. The name of the folder does not matter you just need two copies of the program, I’ll explain in a minute. I don’t have a download link but it’s on the forum just search for it.
2. Pick one of the two “Root_with_Restore_by_Bin4ry_v18” to modify, you need to modify it to kick the kindle in the head and allow the original to work.open the folder of the one you want to modify and right click on the “RunMe.bat” and click edit. Highlight everything in it and delete. Then copy this in its place.
Code:
@echo off
COLOR 0A
echo ======================================================================
echo = This script will root your Android phone with adb restore function =
echo = Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
echo = Idea for Tablet S from Fi01_IS01 =
echo = (18.12.2012) v17 =
echo ======================================================================
echo.
:CHOICE
set nxt=0
set ric=0
echo Device type:
echo 1) Normal
echo 2) Special (for example: Sony Tablet S, Medion Lifetab)
echo.
echo x) Unroot
echo.
set /p type=Make a choice:
if %type% == 1 GOTO TEST
if %type% == 2 GOTO TABSMENU
if %type% == x GOTO UNROOT
echo.
echo Please Enter a valid number (1 to x)
echo.
GOTO CHOICE
:TEST
echo Checking if i should run in Normal Mode or special Sony Mode
echo Please connect your device with USB-Debugging enabled now
echo Waiting for device to shop up, if nothing happens please check if Windows ADB-drivers are installed correctly!
stuff\adb.exe wait-for-device
stuff\adb.exe pull /system/app/Backup-Restore.apk . > NUL
stuff\adb.exe pull /system/bin/ric . > NUL
if EXIST ric (set ric=1) else (echo .)
if EXIST Backup-Restore.apk (GOTO XPS) else (echo .)
GOTO OTHER
:UNROOT
set /p unr=Really (y/n) ?
IF %unr% == n GOTO CHOICE
stuff\adb.exe push stuff\busybox /sdcard/Documents/busybox
stuff\adb.exe shell "chmod 755 /sdcard/Documents/busybox"
stuff\adb.exe shell "su -c '/sdcard/Documents/busybox mount -o remount,rw /system'"
stuff\adb.exe shell "su -c 'rm /system/xbin/su'"
stuff\adb.exe shell "su -c 'rm /system/app/Superuser.apk'"
GOTO FINISH
:TABSMENU
echo.
echo Special mode:
echo 1) Root
echo 2) Rollback
set /p tabtype=Make a choice:
if %tabtype% == 1 GOTO TABS
if %tabtype% == 2 GOTO TABS_RB
:TABS
echo.
echo Tablet S mode enabled!
echo.
GOTO START
:XPS
echo.
echo Found Sony Backup-Restore.apk
echo LT26,LT22 etc. mode enabled!
echo.
del Backup-Restore.apk
if %ric% == 1 (del ric) else (echo .)
set NXT=1
GOTO START
:TABS_RB
echo.
echo Tablet S Roll Back
echo.
echo Please connect device with ADB-Debugging enabled now....
stuff\adb.exe wait-for-device
FOR /F "tokens=1 delims=" %%A in ('stuff\adb.exe shell "if [ -d /data/app- ]; then echo 1 ; else echo 0 ; fi"') do SET tabs_app=%%A
if %tabs_app% == 1 GOTO TABS_RB_1
if %tabs_app% == 0 GOTO TABS_RB_2
:TABS_RB_1
stuff\adb.exe shell "rm -r /data/data/com.android.settings/a/*"
stuff\adb.exe restore stuff/tabletS.ab
echo Please look at your device and click "Restore my data"
echo.
stuff\adb.exe shell "while [ ! -d /data/data/com.android.settings/a/file99 ] ; do echo 1; done" > NUL
echo 1st RESTORE OK, hit ENTER to continue.
pause
stuff\adb.exe shell "rm -r /data/data/com.android.settings/a"
stuff\adb.exe restore stuff/tabletS.ab
echo Please look at your device and click "Restore my data"
echo.
stuff\adb.exe shell "while : ; do ln -s /data /data/data/com.android.settings/a/file99; [ -f /data/file99 ] && exit; done" > NUL
stuff\adb.exe shell "rm -r /data/file99"
echo Achieved! hit ENTER to continue.
echo.
pause
stuff\adb.exe shell "mv /data/system /data/system3"
stuff\adb.exe shell "mv /data/system- /data/system"
stuff\adb.exe shell "mv /data/app /data/app3"
stuff\adb.exe shell "mv /data/app- /data/app"
echo "Roll back compelted."
GOTO FINISH
:TABS_RB_2
echo.
echo.
echo "Roll back failed. /data/app- not found."
echo.
echo.
GOTO FINISH
:eek:THER
echo.
echo Normal Mode enabled!
if %ric% == 1 (del ric) else (echo .)
echo.
:START
stuff\adb.exe wait-for-device
IF %type% == 2 GOTO TABTRICK
echo Pushing busybox....
stuff\adb.exe push stuff/busybox /sdcard/Documents/.
echo Pushing su binary ....
stuff\adb.exe push stuff/su /sdcard/Documents/.
echo Pushing Superuser app
stuff\adb.exe push stuff/Superuser.apk /sdcard/Documents/.
echo Making busybox runable ...
stuff\adb.exe shell chmod 755 /sdcard/Documents/busybox
if %ric% == 1 (stuff\adb.exe push stuff/ric /sdcard/Documents/ric) else (echo .)
IF %nxt% == 1 GOTO XPSTRICK
stuff\adb.exe restore stuff/fakebackup.ab
echo Please look at your device and click RESTORE!
echo If all is successful i will tell you, if not this shell will run forever.
echo Running ...
stuff\adb.exe shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > NUL
echo Successful, going to reboot your device in 10 seconds!
ping -n 10 127.0.0.1 > NUL
stuff\adb.exe reboot
echo Waiting for device to show up again....
ping -n 10 127.0.0.1 > NUL
stuff\adb.exe wait-for-device
GOTO NORMAL
:TABTRICK
stuff\adb.exe install -s stuff/Term.apk
stuff\adb.exe push stuff/busybox /sdcard/Documents/.
stuff\adb.exe push stuff/su /sdcard/Documents/.
stuff\adb.exe push stuff/Superuser.apk /sdcard/Documents/.
stuff\adb.exe push stuff/rootkittablet.tar.gz /sdcard/Documents/rootkittablet.tar.gz
stuff\adb.exe shell "chmod 755 /sdcard/Documents/busybox"
stuff\adb.exe shell "/sdcard/Documents/busybox tar -C /data/local/tmp -x -v -f /sdcard/Documents/rootkittablet.tar.gz"
stuff\adb.exe shell "chmod 644 /sdcard/Documents/VpnFaker.apk"
stuff\adb.exe shell "touch -t 1346025600 /sdcard/Documents/VpnFaker.apk"
stuff\adb.exe shell "chmod 755 /sdcard/Documents/_su"
stuff\adb.exe shell "chmod 755 /sdcard/Documents/su"
stuff\adb.exe shell "chmod 755 /sdcard/Documents/onload.sh"
stuff\adb.exe shell "chmod 755 /sdcard/Documents/onload2.sh"
stuff\adb.exe shell "rm -r /data/data/com.android.settings/a/*"
stuff\adb.exe restore stuff/tabletS.ab
echo Please look at your device and click "Restore my data"
echo.
stuff\adb.exe shell "while [ ! -d /data/data/com.android.settings/a/file99 ] ; do echo 1; done" > NUL
ping -n 3 127.0.0.1 > NUL
echo 1st RESTORE OK, hit ENTER to continue.
pause
stuff\adb.exe shell "rm -r /data/data/com.android.settings/a"
stuff\adb.exe restore stuff/tabletS.ab
echo Please look at your device and click "Restore my data"
echo.
stuff\adb.exe shell "while : ; do ln -s /data /data/data/com.android.settings/a/file99; [ -f /data/file99 ] && exit; done" > NUL
stuff\adb.exe shell "rm -r /data/file99"
ping -n 3 127.0.0.1 > NUL
echo Achieved! hit ENTER to continue.
echo.
pause
stuff\adb.exe shell "/sdcard/Documents/busybox cp -r /data/system /data/system2"
stuff\adb.exe shell "/sdcard/Documents/busybox find /data/system2 -type f -exec chmod 666 {} \;"
stuff\adb.exe shell "/sdcard/Documents/busybox find /data/system2 -type d -exec chmod 777 {} \;"
stuff\adb.exe shell "mv /data/system /data/system-"
stuff\adb.exe shell "mv /data/system2 /data/system"
stuff\adb.exe shell "mv /data/app /data/app-"
stuff\adb.exe shell "mkdir /data/app"
stuff\adb.exe shell "mv /sdcard/Documents/VpnFaker.apk /data/app"
stuff\adb.exe shell "/sdcard/Documents/busybox sed -f /sdcard/Documents/packages.xml.sed /data/system-/packages.xml > /data/system/packages.xml"
stuff\adb.exe shell "sync; sync; sync"
echo Need to reboot now!
stuff\adb.exe reboot
ping -n 3 127.0.0.1 > NUL
echo Waiting for device to come up again....
stuff\adb.exe wait-for-device
echo Unlock your device, a Terminal will show now, type this 2 lines, after each line press ENTER
echo /sdcard/Documents/onload.sh
echo /sdcard/Documents/onload2.sh
echo after this is done press a key here in this shell to continue!
echo If the shell on your device does not show please re-start the process!
stuff\adb.exe shell "am start -n com.android.vpndialogs/.Term"
pause
GOTO TABTRICK1
:TABTRICK1
stuff\adb.exe push stuff/script1.sh /sdcard/Documents/.
stuff\adb.exe shell "chmod 755 /sdcard/Documents/script1.sh"
stuff\adb.exe shell "/sdcard/Documents/script1.sh"
echo Almost complete! Reboot and cleanup.
stuff\adb.exe reboot
ping -n 3 127.0.0.1 > NUL
echo Waiting for device to come up again....
stuff\adb.exe wait-for-device
stuff\adb.exe shell "su -c 'rm -r /data/app2'"
stuff\adb.exe shell "su -c 'rm -r /data/system2'"
stuff\adb.exe shell "su -c 'rm -r /sdcard/Documents/*'"
GOTO FINISH
:XPSTRICK
set %NXT%=0
echo Pushing fake Backup
stuff\adb.exe push stuff\RootMe.tar /sdcard/Documents/RootMe.tar
stuff\adb.exe shell "mkdir /mnt/sdcard/.semc-fullbackup > /dev/null 2>&1"
echo Extracting fakebackup on device ...
stuff\adb.exe shell "cd /mnt/sdcard/.semc-fullbackup/; /sdcard/Documents/busybox tar xf /sdcard/Documents/RootMe.tar"
echo Watch now your device. Select the backup named RootMe and restore it!
stuff\adb.exe shell "am start com.sonyericsson.vendor.backuprestore/.ui.BackupActivity"
echo If all is successful i will tell you, if not this shell will run forever.
echo Running ......
stuff\adb.exe shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > NUL
echo.
echo Good, it worked! Now we are rebooting soon, please be patient!
ping -n 3 127.0.0.1 > NUL
stuff\adb.exe shell "rm -r /mnt/sdcard/.semc-fullbackup/RootMe"
stuff\adb.exe reboot
ping -n 10 127.0.0.1 > NUL
echo Waiting for device to come up again....
stuff\adb.exe wait-for-device
:NORMAL
IF %ric% == 1 GOTO RICSTUFF
echo Going to copy files to it's place
stuff\adb.exe shell "/sdcard/Documents/busybox mount -o remount,rw /system && /sdcard/Documents/busybox mv /sdcard/Documents/su /system/xbin/su && /sdcard/Documents/busybox mv /sdcard/Documents/Superuser.apk /system/app/Superuser.apk && /sdcard/Documents/busybox cp /sdcard/Documents/busybox /system/xbin/busybox && chown 0.0 /system/xbin/su && chmod 06755 /system/xbin/su && chmod 655 /system/app/Superuser.apk && chmod 755 /system/xbin/busybox && rm /data/local.prop && reboot"
GOTO FINISH
:RICSTUFF
echo Going to copy files to it's place
stuff\adb.exe shell "/sdcard/Documents/busybox mount -o remount,rw /system && /sdcard/Documents/busybox mv /sdcard/Documents/ric /system/bin/ric && chmod 755 /system/bin/ric && /sdcard/Documents/busybox mv /sdcard/Documents/su /system/xbin/su && /sdcard/Documents/busybox mv /sdcard/Documents/Superuser.apk /system/app/Superuser.apk && /sdcard/Documents/busybox cp /sdcard/Documents/busybox /system/xbin/busybox && chown 0.0 /system/xbin/su && chmod 06755 /system/xbin/su && chmod 655 /system/app/Superuser.apk && chmod 755 /system/xbin/busybox && rm /data/local.prop && reboot"
GOTO FINISH
:FINISH
echo You can close all open command-prompts now!
echo After reboot all is done! Have fun!
echo Bin4ry
pause
This is the original code with initial drop locations changed to insure the software gets on the device. close it and save changes.
Double click on “RunMe.bat” to launch on the modified one (it worked for me without using “run as Admin, as a matter of fact, it would not run with elevateded so just double click and follow the on screen instructions).
When it gets done you may see a flash of “kindle fire” on the screen, that’s because its stumbling (good thing) when you have this done run the original “Root_with_Restore_by_Bin4ry_v18” unchanged and follow all instructions.
You should be rooted after that. Load all your google apk’s and enjoy!:good:
I in no way take credit for the code, I just changed the drop location on a hunch and it worked, props to the developer, not me.
As always if you brick it, it’s on you. This worked for me
prokennexusa said:
inflicted_1999,
I am sorry to hear your frustrations around Rooting the Kindle Fire 2 version 10.2.6, this can be a bugger to Root. I have an idea that may help you. When you have a yellow triangle over MTP, this is a strong sign that the driver is not functional. When you have the combination of, one Android Composite ADB Interface with the yellow triangle over MTP, you have a driver failure. Having said this, none of the utilities will work until you have a functional driver. Just FYI Windows Media Player is not needed to get the Kindle to Root. Once you have successfully installed the driver Android Composite ADB Interface will change to Android ADB Interface and the MTP will change to Portable Devices > Kindle. You will also know the driver install was successful when you get a pop-up asking what to do with the Kindle Drive - like sync it with your MP3 collection.
If you already tried Part A for the driver, here are the key points:
Note: Windows 7 and Vista users, please perform this fix before Rooting: http://forum.xda-developers.com/show...php?p=36373627
A) The first step is to get the ADB Driver installed. If you already performed this step and verified communication to the Kindle.
Please open an Administrative CMD Prompt and enter:
Code:
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Note: We have seen quite a few cases when the driver "fails to install". This message is normally erroneous and can usually be ignored. Plug in your Kindle, then look in the Windows Device Manager to see if the main driver installed.
Our friends at RevTV Created this video which outlines How to install ADB: How to Install ADB Video
The following ADB Driver was provided by Amazon and should install on most platforms (Windows XP, Vista, 7, and 8): Kindle Fire ADB drivers
Note: Due to intermittent issues with the USB Drivers, we offer two versions. First try Kindle Fire ADB drivers.exe if this
does not open ADB Communication try the new updated KindleDrivers.exe
Click to expand...
Click to collapse
thanks for your help i have tried all the above options yet i still have a prob with MTP not doing anything and i cant see kindle in
mycomputer adb sees it as an attached device...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pic attached
of my device manager
Kindle Fire 2 7" - How To Install ADB Drivers On Windows
inflicted_1999 said:
thanks for your help i have tried all the above options yet i still have a prob with MTP not doing anything and i cant see kindle in
mycomputer adb sees it as an attached device...
pic attached
of my device manager
Click to expand...
Click to collapse
inflicted_1999,
We know this one. Once you get the driver installed, the following will happen:
MTP will change to Portable Devices > Kindle
Unknown will change to Kindle > Android ADB Interface
Now, how do you accomplish this task? Take these steps:
Take 3 minutes and watch this video, please: How to Install ADB Video
This video will help you to understand the manual installation method for the next driver. Please download: usb_driver
Extract the alternative driver to your desktop and follow the install instructions at the bottom of this response
The alternative driver originates from the Android SDK and is universal for just about any Android device.
The alternative driver instructions are for Windows XP but can be used with Windows 7 and Vista.
Once we get ADB installed then let's plugin the Kindle to your computer USB to see if it initializes properly.
Once this driver has been properly installed you will see "Android Composite ADB Interface" under "Kindle Fire" in the Windows Device Manager which is located by Right Hand Mouse Click Computer, Choose Properties, then Devices or Device Manager. Expand the tree. Expand Kindle. This is where you will see "Android Composite ADB Interface".
Amazon Notes regarding this ADB Driver can be found here: Amazon ADB Notes
ALTERNATIVE DRIVER INSTALL (Vista/XP/Windows7):
Windows XP
To install the Android USB driver on Windows XP for the first time:
1. Connect your Android-powered device to your computer's USB port.
2. Right-click on My Computer from your desktop or Windows Explorer, and select Manage.
3. Select Device Manager in the left pane.
4. Locate and expand Other Devices in the right pane.
5. Right-click Unknown Device and select Update Driver. This will launch the Hardware Update Wizard.
6. Select Install from a list or specific location and click Next.
7. Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
8. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
9. Click Next to upgrade the driver. Sometimes this triggers MTP to update, if this happens stop here and begin the Root procedure as outlined here: http://forum.xda-developers.com/showthread.php?t=2069117 - otherwise proceed to step the next step to update MTP.
10. Locate and expand Other Devices in the right pane.
11. Right-click MTP and select Update Driver. This will launch the Hardware Update Wizard.
12. Select Install from a list or specific location and click Next.
13. Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
14. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
15. Click Next to upgrade the driver.
Once the driver installs correctly, you will see a drive named "Kindle" in My Computer and there will be no more Yellow marks in Windows Device Manager.
prokennexusa said:
inflicted_1999,
We know this one. Once you get the driver installed, the following will happen:
MTP will change to Portable Devices > Kindle
Unknown will change to Kindle > Android ADB Interface
Now, how do you accomplish this task? Take these steps:
Take 3 minutes and watch this video, please: How to Install ADB Video
This video will help you to understand the manual installation method for the next driver. Please download: usb_driver
Extract the alternative driver to your desktop and follow the install instructions at the bottom of this response
The alternative driver originates from the Android SDK and is universal for just about any Android device.
The alternative driver instructions are for Windows XP but can be used with Windows 7 and Vista.
Once we get ADB installed then let's plugin the Kindle to your computer USB to see if it initializes properly.
Once this driver has been properly installed you will see "Android Composite ADB Interface" under "Kindle Fire" in the Windows Device Manager which is located by Right Hand Mouse Click Computer, Choose Properties, then Devices or Device Manager. Expand the tree. Expand Kindle. This is where you will see "Android Composite ADB Interface".
Amazon Notes regarding this ADB Driver can be found here: Amazon ADB Notes
ALTERNATIVE DRIVER INSTALL (Vista/XP/Windows7):
Windows XP
To install the Android USB driver on Windows XP for the first time:
1. Connect your Android-powered device to your computer's USB port.
2. Right-click on My Computer from your desktop or Windows Explorer, and select Manage.
3. Select Device Manager in the left pane.
4. Locate and expand Other Devices in the right pane.
5. Right-click Unknown Device and select Update Driver. This will launch the Hardware Update Wizard.
6. Select Install from a list or specific location and click Next.
7. Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
8. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
9. Click Next to upgrade the driver. Sometimes this triggers MTP to update, if this happens stop here and begin the Root procedure as outlined here: http://forum.xda-developers.com/showthread.php?t=2069117 - otherwise proceed to step the next step to update MTP.
10. Locate and expand Other Devices in the right pane.
11. Right-click MTP and select Update Driver. This will launch the Hardware Update Wizard.
12. Select Install from a list or specific location and click Next.
13. Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
14. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
15. Click Next to upgrade the driver.
Once the driver installs correctly, you will see a drive named "Kindle" in My Computer and there will be no more Yellow marks in Windows Device Manager.
Click to expand...
Click to collapse
sorry to be a complete pain whenever i try to update driver from the \usb_driver\ folder it says this location
doesnt contain information about your device....
Kindle Fire HD and 2 Root Problem - ADB Driver Problem
inflicted_1999 said:
sorry to be a complete pain whenever i try to update driver from the \usb_driver\ folder it says this location
doesnt contain information about your device....
Click to expand...
Click to collapse
inflicted_1999,
You are not being a pain, sometimes it takes several posts - I have seen up to 10 - to resolve a difficult situation. OK, so what is your Operating System?
Please drop to a Command and type the following:
Code:
ping 4.2.2.2
Does this respond with packets? If the response is something like "no internal or external command can be found...", then proceed to patch you computer using this post: http://forum.xda-developers.com/showthread.php?t=2086210 - when you are done please post "completed, moving on to Root" in that thread, not this one.
Finally, do you get an error when you install the original driver or did it install without error? Do you have ADB Enabled under the Device Tab? Do you have any security software installed like Norton Internet Security? Do you have plenty of free disk drive space?
prokennexusa said:
inflicted_1999,
You are not being a pain, sometimes it takes several posts - I have seen up to 10 - to resolve a difficult situation. OK, so what is your Operating System?
Please drop to a Command and type the following:
Code:
ping 4.2.2.2
Does this respond with packets? If the response is something like "no internal or external command can be found...", then proceed to patch you computer using this post: http://forum.xda-developers.com/showthread.php?t=2086210 - when you are done please post "completed, moving on to Root" in that thread, not this one.
Finally, do you get an error when you install the original driver or did it install without error? Do you have ADB Enabled under the Device Tab? Do you have any security software installed like Norton Internet Security? Do you have plenty of free disk drive space?
Click to expand...
Click to collapse
Hi mate thanks for helping... my laptop is running XP pro service pack 3
i get replies from pinging 4.2.2.2
the original drivers installed and said ready to use
i dont have any security software installed at all as its a fresh install, i installed win 7
before this copy of xp and had the same issues...
How To Root Kindle Fire 2 Software Version 10.2.6
inflicted_1999 said:
Hi mate thanks for helping... my laptop is running XP pro service pack 3
i get replies from pinging 4.2.2.2
the original drivers installed and said ready to use
i dont have any security software installed at all as its a fresh install, i installed win 7
before this copy of xp and had the same issues...
Click to expand...
Click to collapse
inflicted_1999,
OK, so we know the variables are OK, now let's dig into ADB, please open a command prompt:
Code:
adb kill-server
adb start-server
adb devices
If the commands work you need to remove the Android SDK prior to using Root MANY ANDROID. Please reply back with the progress.
prokennexusa said:
inflicted_1999,
OK, so we know the variables are OK, now let's dig into ADB, please open a command prompt:
Code:
adb kill-server
adb start-server
adb devices
If the commands work you need to remove the Android SDK prior to using Root MANY ANDROID. Please reply back with the progress.
Click to expand...
Click to collapse
hi mate those commands seem to work as i now have a command prompt with
list of devices attached
D026A024350CJH device
Root the Kindle Fire 2 with Windows - Noob (Simple) Version
inflicted_1999 said:
hi mate those commands seem to work as i now have a command prompt with
list of devices attached
D026A024350CJH device
Click to expand...
Click to collapse
inflicted_1999,
Beautiful, you are ready! First we MUST get rid of Android SDK since Root MANY ANDROID will fail with the SDK installed. So either go to Windows Add/Remove Programs and remove the Android SDK or use Windows Search - find the folder named "platform-tools", one you find it, rename it to "platform-tools-bak".
Once you have renamed or removed the SDK, then we can Root the Kindle Fire 2:
Plug the Kindle back into USB if it is not already plugged into USB.
1. Download Root MANY ANDROID! to your desktop. Extract to your desktop. This package includes updated adb daemons.
NOTE WINDOWS 7 USERS: You need to open a command prompt "as Administrator" when running the above utility batch files RunMe.bat - otherwise Windows will respond with "Permission Denied".
Make sure the Kindle is still plugged into USB.
Root Step 1: Run RunMe.bat from Root MANY ANDROID! through a command window as noted:
Double Mouse Click and Open the Root_with_Restore_by_Bin4ry_v18 folder.
Next Single Left Mouse Click on the Root_with_Restore_by_Bin4ry_v18 folder toolbar.
This highlights the Root_with_Restore_by_Bin4ry_v18 folder.
Note: Make sure none of the files within the Root_with_Restore_by_Bin4ry_v18 are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, finally type
Code:
RunMe.bat
Choose option 1, Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. If you are asked for an 'encryption password', enter the password you use to sign onto Amazon. Click on Restore. When the program has completed, the Kindle will Reboot.
The forum notes can be found here: Root MANY ANDROID! Forum.
Root Step 2: When the Kindle reboots it will have Root.
Root Step 3: Please navigate to the Apps Folder and find Superuser on the Device, click to Launch Superuser, then Reboot.
You are now Rooted, you may move on to How to Install Google Play Store here: http://forum.xda-developers.com/showthread.php?p=35962244
prokennexusa said:
inflicted_1999,
Beautiful, you are ready! First we MUST get rid of Android SDK since Root MANY ANDROID will fail with the SDK installed. So either go to Windows Add/Remove Programs and remove the Android SDK or use Windows Search - find the folder named "platform-tools", one you find it, rename it to "platform-tools-bak".
Once you have renamed or removed the SDK, then we can Root the Kindle Fire 2:
Plug the Kindle back into USB if it is not already plugged into USB.
1. Download Root MANY ANDROID! to your desktop. Extract to your desktop. This package includes updated adb daemons.
NOTE WINDOWS 7 USERS: You need to open a command prompt "as Administrator" when running the above utility batch files RunMe.bat - otherwise Windows will respond with "Permission Denied".
Make sure the Kindle is still plugged into USB.
Root Step 1: Run RunMe.bat from Root MANY ANDROID! through a command window as noted:
Double Mouse Click and Open the Root_with_Restore_by_Bin4ry_v18 folder.
Next Single Left Mouse Click on the Root_with_Restore_by_Bin4ry_v18 folder toolbar.
This highlights the Root_with_Restore_by_Bin4ry_v18 folder.
Note: Make sure none of the files within the Root_with_Restore_by_Bin4ry_v18 are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, finally type
Code:
RunMe.bat
Choose option 1, Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. If you are asked for an 'encryption password', enter the password you use to sign onto Amazon. Click on Restore. When the program has completed, the Kindle will Reboot.
The forum notes can be found here: Root MANY ANDROID! Forum.
Root Step 2: When the Kindle reboots it will have Root.
Root Step 3: Please navigate to the Apps Folder and find Superuser on the Device, click to Launch Superuser, then Reboot.
You are now Rooted, you may move on to How to Install Google Play Store here: http://forum.xda-developers.com/showthread.php?p=35962244
Click to expand...
Click to collapse
that all seemed to work ok and i opened superuser etc... to load google play etc i need to see the kindle on win xp
dont i which i still cant unfortunately ... is there another way other than through my computer
is it worth me reloading with vista win 7 again or win 8 is that easier to connect than xp
How to Access Files Over WiFi - Kies Air - Attached
inflicted_1999 said:
that all seemed to work ok and i opened superuser etc... to load google play etc i need to see the kindle on win xp
dont i which i still cant unfortunately ... is there another way other than through my computer
is it worth me reloading with vista win 7 again or win 8 is that easier to connect than xp
Click to expand...
Click to collapse
inflicted_1999,
Great work inflicted_1999, so you did make it through your rooting problem, good job! OK, I have another idea to accress the Kindle but let's first identify what may be causing the mounting trouble. Can you please go into your windows System by pressing the Windows Key (found between the CTRL and ALT Keys) with the pause/break key - this keyboard shortcut will open the Windows System, next select the Windows Device Manager. What do you see here? You should see:
Kindle > Android ADB Interface
Portable Device > Kindle
If you see a yellow triangle, please reply with the identification of the Yellow Triangle like "Unknown Device".
The other option is to install the attached service Kies Air, it will allow you to access and upload files to your Kindle Fire HD and 2. This is a WiFi file manager.
Kies Air - Attached to this Thread
It’s time to share wirelessly!
Why not manage your mobile device via your Internet browser?
Kies Air is a application that enables you to easily manage contents saved on your device via PC internet or mobile browser using Wi-Fi technology.
Without having to connect any cables, within a browser you can use diverse function such as multimedia transfer, music listening, PIMS management, text message, file search, and so on.
Since Kies Air is an application for accessing mobile content from a PC or browser, the application has to read the content from the mobile device in order to carry out this function. To ensure that your data is secure and not shared without your consent, when you install/update an application, Kies Air will ask you to grant permission.
To access via PC or laptop:
1. Connect the mobile device and the PC or laptop to the same access point (Wi-Fi router)
2. Open Kies Air on the mobile device and tap Start
3. Kies Air on the mobile device will display a URL. Enter the URL in the browser on the PC or laptop
4. Kies Air will display a 4-digit PIN on the mobile device. When prompted, enter the PIN into the browser on the PC or laptop
5. The PC or laptop is now connected and you can access the content of your mobile device.
You can also create a desktop icon to connect to Kies Air more easily
After creating the desktop icon, you can access Kies Air without having to enter the URL into the browser on the PC or laptop
To access via another mobile device (e.g. device B accesses device A):
1. Connect both mobile devices (A and B) to the same access point (Wi-Fi router)
2. Open Kies Air on device A and tap Start
3. Open Kies Air on device B and shake the device twice. This will start a scan for device A
4. Device A will appear on the screen of device B. Tap on device A
5. Kies Air will display a PIN on device A. When prompted, enter the PIN on device B
If Kies Air is not installed on device B, enter the URL displayed by device A into the browser on device B.
If the motion feature is not supported on device B, press the menu key, and then tap Scan.
During installation, Kies Air requests permission to provide you with access to content or other required functions. Your data is only ever accessible within your local network and never sent to the Kies Air team, Samsung, or any other remote server.
prokennexusa said:
inflicted_1999,
Great work inflicted_1999, so you did make it through your rooting problem, good job! OK, I have another idea to accress the Kindle but let's first identify what may be causing the mounting trouble. Can you please go into your windows System by pressing the Windows Key (found between the CTRL and ALT Keys) with the pause/break key - this keyboard shortcut will open the Windows System, next select the Windows Device Manager. What do you see here? You should see:
Kindle > Android ADB Interface
Portable Device > Kindle
If you see a yellow triangle, please reply with the identification of the Yellow Triangle like "Unknown Device".
The other option is to install the attached service Kies Air, it will allow you to access and upload files to your Kindle Fire HD and 2. This is a WiFi file manager.
Kies Air - Attached to this Thread
It’s time to share wirelessly!
Why not manage your mobile device via your Internet browser?
Kies Air is a application that enables you to easily manage contents saved on your device via PC internet or mobile browser using Wi-Fi technology.
Without having to connect any cables, within a browser you can use diverse function such as multimedia transfer, music listening, PIMS management, text message, file search, and so on.
Since Kies Air is an application for accessing mobile content from a PC or browser, the application has to read the content from the mobile device in order to carry out this function. To ensure that your data is secure and not shared without your consent, when you install/update an application, Kies Air will ask you to grant permission.
To access via PC or laptop:
1. Connect the mobile device and the PC or laptop to the same access point (Wi-Fi router)
2. Open Kies Air on the mobile device and tap Start
3. Kies Air on the mobile device will display a URL. Enter the URL in the browser on the PC or laptop
4. Kies Air will display a 4-digit PIN on the mobile device. When prompted, enter the PIN into the browser on the PC or laptop
5. The PC or laptop is now connected and you can access the content of your mobile device.
You can also create a desktop icon to connect to Kies Air more easily
After creating the desktop icon, you can access Kies Air without having to enter the URL into the browser on the PC or laptop
To access via another mobile device (e.g. device B accesses device A):
1. Connect both mobile devices (A and B) to the same access point (Wi-Fi router)
2. Open Kies Air on device A and tap Start
3. Open Kies Air on device B and shake the device twice. This will start a scan for device A
4. Device A will appear on the screen of device B. Tap on device A
5. Kies Air will display a PIN on device A. When prompted, enter the PIN on device B
If Kies Air is not installed on device B, enter the URL displayed by device A into the browser on device B.
If the motion feature is not supported on device B, press the menu key, and then tap Scan.
During installation, Kies Air requests permission to provide you with access to content or other required functions. Your data is only ever accessible within your local network and never sent to the Kies Air team, Samsung, or any other remote server.
Click to expand...
Click to collapse
it still wont connect to the PC but i managed to get kies downloaded and on there and did it all via that..
amazing thanks so much for your help... i managed to do that then golauncher etc from this link http://forum.xda-developers.com/showthread.php?t=2069668 will this stop automatic updates from amazon or will i need to
do that manually
If you need to flash ROM even using fastboot for Smartphone or Tablet in which they use Android OS! Then Ubuntu OS is needed!
This is a guide I made for ubuntu users and included a guide for windows users to setup Android SDK which contains ADB.
Android Debug Bridge (ADB) provides a terminal interface on your PC to interact with your device's file system. This can be useful for many things like installing & uninstalling apps, logcat, backup & restore, and hacking your device just to name a few.
ubuntu 12.04 & 12.10 Guide
1. Go here and download android-sdk (not the adt-bundle)....
https://hotfile.com/dl/241406263/5e6a306/android-sdk_r22.0.5-linux.tgz.html
2. Place the downloaded file in your home folder and then extract it and you should get a folder named android-sdk-linux (do not rename it).
3. If you’re on a 64bit machine run these commands in terminal to make sdk compatible with 64bit (if you’re on 32bit machine then skip this step)....
sudo apt-get update
sudo apt-get install ia32-libs-multiarch
4. Run this command in terminal to install jdk if you don’t have it already....
sudo apt-get install openjdk-6-jdk
5. Navigate to the home folder where you extracted android-sdk-linux and open the folder then open the folder named tools
6. Inside the tools folder there will be a file named android... double click it and select run then android sdk manager will open.
7. In the center pane deselect everything... Now only select the following....
Android SDK Tools
Android SDK Platform-tools
Android Support Library
8. Once selections have been made click on install packages and wait till finished.
9. Upon completion of step 8 in terminal run this command....
sudo gedit ~/.bashrc
When the file opens, go to the very bottom and copy/paste the following 3 lines (make sure they’re each on separate lines)....
# Android tools
export PATH=${PATH}:~/android-sdk-linux/tools
export PATH=${PATH}:~/android-sdk-linux/platform-tools
10. Now reboot your computer.
11. Set your phone to usb debugging then plug it to your pc after pc is done booting
12. Open a terminal on your pc and enter....
adb devices
If all went well, you should see your phone’s serial number and you’ll be ready to go.
~~~~~Important~~~~~
You can use steps 5 & 6 to open Android SDK Manager & update your ADB/SDK installation. Only select your installed packages then update.
Also if you only need the fastboot/adbtools:
sudo add-apt-repository -y ppa: phablet-team/tools
Note: delete the space after"-y ppa:" -xda creates smileys like ppa
sudo apt-get update
sudo apt-get install -y phablet-tools
Sent from my Nexus 4 using xda app-developers app
Thank...
gazhead said:
Also if you only need the fastboot/adbtools:
sudo add-apt-repository -y ppa: phablet-team/tools
Note: delete the space after"-y ppa:" -xda creates smileys like ppa
sudo apt-get update
sudo apt-get install -y phablet-tools
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks man! It's also good way!
Followed this guide (thank you for posting) but couldn't connect. Scratched around and found I needed to create a new file in /etc/udev/rules.d with:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="<4-char_verndorID>", ATTR{idProduct}=="4-char_productID", MODE="0666", OWNER="username"
Followed by:
Code:
sudo restart udev
Then plugged device in and it worked!
qtoon said:
Followed this guide (thank you for posting) but couldn't connect. Scratched around and found I needed to create a new file in /etc/udev/rules.d with:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="<4-char_verndorID>", ATTR{idProduct}=="4-char_productID", MODE="0666", OWNER="username"
Followed by:
Code:
sudo restart udev
Then plugged device in and it worked!
Click to expand...
Click to collapse
What did you name the new file you created? Or did you add this string to another existing file from the rules.d directory? I'm not sure what I've done wrong, but I get
Code:
[email protected]:~$ adb devices
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
Command 'dab' from package 'bsdgames' (universe)
Command 'zdb' from package 'zfs-fuse' (universe)
Command 'kdb' from package 'elektra-bin' (universe)
Command 'tdb' from package 'tads2-dev' (multiverse)
Command 'pdb' from package 'python' (main)
Command 'jdb' from package 'openjdk-6-jdk' (main)
Command 'jdb' from package 'openjdk-7-jdk' (universe)
Command 'ab' from package 'apache2-utils' (main)
Command 'ad' from package 'netatalk' (universe)
adb: command not found
[email protected]:~$
This is after following each step, adding the three lines to the end of .bashrc and rebooting.
atmu5fear said:
What did you name the new file you created? Or did you add this string to another existing file from the rules.d directory? I'm not sure what I've done wrong, but I get
Code:
[email protected]:~$ adb devices
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
Command 'dab' from package 'bsdgames' (universe)
Command 'zdb' from package 'zfs-fuse' (universe)
Command 'kdb' from package 'elektra-bin' (universe)
Command 'tdb' from package 'tads2-dev' (multiverse)
Command 'pdb' from package 'python' (main)
Command 'jdb' from package 'openjdk-6-jdk' (main)
Command 'jdb' from package 'openjdk-7-jdk' (universe)
Command 'ab' from package 'apache2-utils' (main)
Command 'ad' from package 'netatalk' (universe)
adb: command not found
[email protected]:~$
This is after following each step, adding the three lines to the end of .bashrc and rebooting.
Click to expand...
Click to collapse
@atmu5fear, inferring that you're new to Linux (a common background for all), some notes:
Unlike wlth Win-d'oh-s, there is a worldwide development community that's always working toward improvement of every aspect of the system, including echoed messages and documentation. You may have to shake off the tendency to ignore Windudz messages, which are frequently unhelpful. Linux command echoes are much more on-target. Also, look for files such as README in rules.d and read it!
Now before creating a new config file (which may not be necessary on your system), see the top feedback line: "No command 'adb' found." First, see that the adb binary is present and that it has exec permission. (Since it's a small file and functions alone, I prefer to copy it to the folder I'm working from.)
If it then runs but won't connect, read on...
Directory (or "folder") names with a trailing '.d' are special: They configure, control, or provide executables for daemons (programs which run continuously, providing a service).
Within service-config.d folders, if the service steps through the files sequentially (as in this case), then it does so based on each filename. (True except for the special case of rc.d, iIRC, in which order is set by the special program rcorder).
So in this case, for example, since the existing files are named 70-whatever, your newly-created file could be 80-atmu5fears-phone to load after the others.
Should connect.
qtoon said:
@atmu5fear, inferring that you're new to Linux (a common background for all), some notes:
Unlike wlth Win-d'oh-s, there is a worldwide development community that's always working toward improvement of every aspect of the system, including echoed messages and documentation. You may have to shake off the tendency to ignore Windudz messages, which are frequently unhelpful. Linux command echoes are much more on-target. Also, look for files such as README in rules.d and read it!
Now before creating a new config file (which may not be necessary on your system), see the top feedback line: "No command 'adb' found." First, see that the adb binary is present and that it has exec permission. (Since it's a small file and functions alone, I prefer to copy it to the folder I'm working from.)
If it then runs but won't connect, read on...
Directory (or "folder") names with a trailing '.d' are special: They configure, control, or provide executables for daemons (programs which run continuously, providing a service).
Within service-config.d folders, if the service steps through the files sequentially (as in this case), then it does so based on each filename. (True except for the special case of rc.d, iIRC, in which order is set by the special program rcorder).
So in this case, for example, since the existing files are named 70-whatever, your newly-created file could be 80-atmu5fears-phone to load after the others.
Should connect.
Click to expand...
Click to collapse
Thanks @qtoon for the reply. I'm not really new to Ubuntu, albeit, it's been a while. First started using it just prior to the realease of Hardy Heron 8.04 LTS. That being said I am certainly no expert, but am somewhat familiar and comfortable with the command line. I did read the README file before posting, but since I'm not all that familiar with configuration files and the like, I figured maybe I should ask.
As per your suggestion i moved the ADB binary to my home folder, not necessarily my working folder, but to test to see if the adb command would be recognized in terminal.
Code:
mv ~/ADB/android-sdk-linux/platform-tools/adb ~/
Still got same result so I moved it back, then went on to make a new file and add the suggested string
Code:
sudo > /etc/udev/rules.d/80-atmu5fear-adb
sudo gedit /etc/udev/rules.d/80-atmu5fear-adb
After saving and restarting udev I still get the same "adb command not found" error.
I then changed the string to read OWNER"atmu5fear" instead of "username", still nothing
Any more suggestions?
Thanks
atmu5fear
Sorted it out
instead of:
adb devices
i needed to input:
./adb devices
It's listed, and in order to use the adb shell:
./adb shell
once in the shell all adb commands work
I get this error...
[email protected]:~$ sudo > /etc/udev/rules.d/80-sjy-phone
bash: /etc/udev/rules.d/80-sjy-phone: Permission denied
ok....... didn't need to add a file, changed phone usb mode to media device and all is ok.
thanks
atmu5fear said:
Sorted it out
instead of:
adb devices
i needed to input:
./adb devices
It's listed, and in order to use the adb shell:
./adb shell
once in the shell all adb commands work
Click to expand...
Click to collapse
Didn't think to mention that, apologies.
Quick 'why' on the ./ here.
Glad you got it running.
Just tried on 14.4 and worked like a charm.
Note: No need to reboot the computer, just reload the bash config with
Code:
source ~/.bashrc
Thanks
A good step by step guide
i will try it and see if it works
Thanks again
Hello, can someone help me ? - I m having problems connecting my device with adb (I ve connected several other devices before with no problems).
I ve got an Allwinner A20 tv box, it worked fine for a few months then one day, after being on (but idle) for a few hours, I noticed the screen was blank but the light on the front was blue (indicating it was on, red is standby). It would not respond to the remote control or to anything, so I unplugged it and since then it will not boot and the screen is blank, the red light will light up but that is it. I ve eliminated the remote controller not working, but I cant boot the device.
So I ve tried connecting via ADB (with Ubuntu) but I cant get the device to show up after typing "adb devices".
Using this guide:
http://androidonlinux.wordpress.com/2013/05/12/setting-up-adb-on-linux/
I can get the vendor id and device id and I ve added it and the manufacturer to udev/modeswitch devices, but when I type "sudo usb_modeswitch -v 0x1f3a -p 0xefe8 -S -R -W"
I get the following error:
~/Android/sdk/platform-tools$ sudo usb_modeswitch -v 0x1f3a -p 0xefe8 -S -R -W
Take all parameters from the command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 2.1.1 (C) Josua Dietze 2014
* Based on libusb1/libusbx
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x1f3a
DefaultProduct= 0xefe8
SierraMode=1
NeedResponse=0
Look for default devices ...
found USB ID 048d:1336
found USB ID 1d6b:0002
found USB ID 19a8:2036
found USB ID 1f3a:efe8
vendor ID matched
product ID matched
found USB ID 1d6b:0001
found USB ID 062a:0102
found USB ID 1d6b:0001
Found devices in default mode (1)
Access device 004 on bus 003
Current configuration number is 1
Use interface number 0
USB description data (for identification)
-------------------------
Manufacturer: not provided
Product: not provided
Serial No.: not provided
-------------------------
Send Sierra control message
Error: Sierra control message failed (error -7). Abort
I ve searched Google for the error code but I cannot find anything.
The device was rooted and USB debugging was on.
Any help would really be appreciated.
Thanks
I got my OP3 today and my laptop, running ElementaryOS (ubuntu based) didn't recognize the OP3 as MTP,
Here is a guide how to fix this, I based this guide on this guide for the OP2.
steps:
Do NOT connect your OP3 to your pc
run the command "lsusb" from your terminal
Connect your OP3 to your pc with original cable
run the command "lsusb" again
You will see a new device, my OP3 is called " Bus 001 Device 012: ID 05c6:900e Qualcomm, Inc. "
You see that it has an ID, in my case "05c6:900e".
the first value is the vendor-id, the second the product-id, you need those so write them down!
so in my case it's :
vendor id: 05c6
product id: 900e
Install the MTP drivers: "sudo apt-get install libmtp-dev mtpfs"
edit the following file with the command: "sudo gedit /lib/udev/rules.d/69-libmtp.rules"
if you don't have gedit installed use the command: "sudo nano /lib/udev/rules.d/69-libmtp.rules"
Add the following line to the file:
Code:
ATTR{idVendor}=="[COLOR="Blue"]vendor-id[/COLOR]", ATTR{idProduct}=="[COLOR="blue"]product-id[/COLOR]", SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1", TAG+="uaccess"
make sure you change the blue values to your own values found in the step above.
safe the file
restart the service: "sudo service udev restart"
If you did it correct you will see a popup on your OP3, select "File Transfers (MTP)", select that and now you can transfer files between your OP3 and linux
I don't know if the vendor-id and/or product-id are always the same, if some people can confirm that then I will edit the post.
Hey, I got the same vendor id and product id as you did.
However, even after following the procedure step-by-step, I am unable to transfer files between my OP3 and my laptop running Ubuntu 12.04 LTS.
The OnePlus drivers folder gets loaded as a CD(though I'm connecting the phone using USB) when I change the "Use USB for" setting to "File Transfer(MTP)," and the file named "adb_config_Linux_OSX.sh" doesn't do anything when run in terminal either.
Could you help me out with this?
I run Ubuntu 16.04 and needed to install any drivers. simply connect op and I was able to access it.
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
krankyvampire25 said:
Hey, I got the same vendor id and product id as you did.
However, even after following the procedure step-by-step, I am unable to transfer files between my OP3 and my laptop running Ubuntu 12.04 LTS.
The OnePlus drivers folder gets loaded as a CD(though I'm connecting the phone using USB) when I change the "Use USB for" setting to "File Transfer(MTP)," and the file named "adb_config_Linux_OSX.sh" doesn't do anything when run in terminal either.
Could you help me out with this?
Click to expand...
Click to collapse
update: In "设置" -"其他设置" - "内部设备和USB" - "USB计算机连接", select -- "File Transfers (MTP)", everything is ok.
14.04 can't transfer file. a folder cant write anything(not cd image folder).
hi....... i have a other problem with the same OS (Ubuntu 16.04)
MTP works
fastboot works
ADB DON'T !!!
do you know why ?????
ADB and fastboot are working at the same device with Win 10
OK, thanks, forget it, i found a file named "adb_config_Linux_OSX.sh" on the phone and run it...... now it works
ty, it worked after two reboots and a system update. btw, i have the OP3 soft gold with ID 2a70:f003
cheers!
washichi said:
I got my OP3 today and my laptop, running ElementaryOS (ubuntu based) didn't recognize the OP3 as MTP,
Here is a guide how to fix this, I based this guide on this guide for the OP2.
steps:
Do NOT connect your OP3 to your pc
run the command "lsusb" from your terminal
Connect your OP3 to your pc with original cable
run the command "lsusb" again
You will see a new device, my OP3 is called " Bus 001 Device 012: ID 05c6:900e Qualcomm, Inc. "
You see that it has an ID, in my case "05c6:900e".
the first value is the vendor-id, the second the product-id, you need those so write them down!
so in my case it's :
vendor id: 05c6
product id: 900e
Install the MTP drivers: "sudo apt-get install libmtp-dev mtpfs"
edit the following file with the command: "sudo gedit /lib/udev/rules.d/69-libmtp.rules"
if you don't have gedit installed use the command: "sudo nano /lib/udev/rules.d/69-libmtp.rules"
Add the following line to the file:
Code:
ATTR{idVendor}=="[COLOR="Blue"]vendor-id[/COLOR]", ATTR{idProduct}=="[COLOR="blue"]product-id[/COLOR]", SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1", TAG+="uaccess"
make sure you change the blue values to your own values found in the step above.
safe the file
restart the service: "sudo service udev restart"
If you did it correct you will see a popup on your OP3, select "File Transfers (MTP)", select that and now you can transfer files between your OP3 and linux
I don't know if the vendor-id and/or product-id are always the same, if some people can confirm that then I will edit the post.
Click to expand...
Click to collapse
I just now happened upon this forum because my OP3 wasn't connecting for file transfers over USB. This worked like a charm for me; the vendor and product IDs were different (as I'm sure others have commented already), thank you for putting this out there, I definitely hit that 'thanks' button!!!!!!!
It's also possible to use this script (Vendor & Product id can differ).
Code:
#!/bin/sh
# adb configuration script
PATH=$PATH:/bin:/sbin:/usr/sbin
ANDROID_HOME=~/.android
ANDROID_CONFIG=~/.android/adb_usb.ini
CUST_VID="0x2a70"
if [ -e $ANDROID_HOME ] ; then
echo "android home is exist!"
else
echo "creat android home!"
mkdir $ANDROID_HOME
fi
grep $CUST_VID $ANDROID_CONFIG 2>/dev/null
if [ $? -eq 0 ] ; then
echo VID $CUST_VID is already configured..
echo "adb should be OK!"
exit 0
else
echo config adb ...
echo $CUST_VID >> $ANDROID_CONFIG
fi
adb kill-server
if [ $? -eq 0 ] ; then
echo "OK! You can use adb now!"
exit 0
else
echo "try sudo exec adb.."
sudo adb kill-server
if [ $? -eq 0 ] ; then
echo "OK! You can use adb now!"
exit 0
else
echo "Please do command \"adb kill-server\""
fi
fi
exit 0
Useful link: https://wiki.archlinux.org/index.php/android#Android_Debug_Bridge_.28ADB.29
Thanks a lot washichi It worked liked a charm on my OnePlus3T. Thanks a ton