GUIDE: connect OP3 with MTP on Linux (ubuntu) - OnePlus 3 Guides, News, & Discussion

GUIDE: connect OP3 with MTP on Linux (ubuntu) - OnePlus 3 Guides, News, & Discussion

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

Related

[Q] How to install adb on linux??? (ubuntu)

Hey guys im pretty good with adb, not many problems at all but ive recently ditched windows for a real os Ubuntu but im not super familiar with the commands and how to do this and that. Can someone hep me with setting up adb in Linux the guide posted is really rough for noobs to linux.

well if you using linux then you will be using terminal to type out the adb commands. once you installed adb into linux you can type adb /? and it will give you the list of commands. In most cases you have to use sudo when running adb commands, at least using sudo when starting the adb server.

no i have no problem using adb at all, i was asking how to install it i cant get it to run in the first place ?

you have to follow the steps for linux, they are mostly meant for ubuntu afaik. Download the special linux SDK, Eclipse etc. One thing you should do to make adb work is add your sdk/tools directory to linux's $PATH.
It should go something like this...
$ echo $PATH (should return the directories associated with $PATH)
$ export PATH=$PATH:/home/user/sdk/tools (replace with path to your tools directory, you may need to add 'sudo' to the beginning of this cmd)
$ echo $PATH (you should now see your tools directory added to the end of the $PATH variable)
$ adb devices (now adb should do something, if nothing else at least error, no devices)
Is this what you were looking for? or some other issue..

sonikamd said:
you have to follow the steps for linux, they are mostly meant for ubuntu afaik. Download the special linux SDK, Eclipse etc. One thing you should do to make adb work is add your sdk/tools directory to linux's $PATH.
It should go something like this...
$ echo $PATH (should return the directories associated with $PATH)
$ export PATH=$PATH:/home/user/sdk/tools (replace with path to your tools directory, you may need to add 'sudo' to the beginning of this cmd)
$ echo $PATH (you should now see your tools directory added to the end of the $PATH variable)
$ adb devices (now adb should do something, if nothing else at least error, no devices)
Is this what you were looking for? or some other issue..
Click to expand...
Click to collapse
thank you you are officially great

jamizzal said:
thank you you are officially great
Click to expand...
Click to collapse
Just to expand on that a little, when you adb start-server you will need to sudo, IIRC on ubuntu root is only enable to connect to USB.
Eg
Code:
sudo adb start-server
adb devices
adb logcat

NPerry said:
Just to expand on that a little, when you adb start-server you will need to sudo, IIRC on ubuntu root is only enable to connect to USB.
Eg
Code:
sudo adb start-server
adb devices
adb logcat
Click to expand...
Click to collapse
thank you i was wondering why i could not find my device

sonikamd said:
you have to follow the steps for linux, they are mostly meant for ubuntu afaik. Download the special linux SDK, Eclipse etc. One thing you should do to make adb work is add your sdk/tools directory to linux's $PATH.
It should go something like this...
$ echo $PATH (should return the directories associated with $PATH)
$ export PATH=$PATH:/home/user/sdk/tools (replace with path to your tools directory, you may need to add 'sudo' to the beginning of this cmd)
$ echo $PATH (you should now see your tools directory added to the end of the $PATH variable)
$ adb devices (now adb should do something, if nothing else at least error, no devices)
Is this what you were looking for? or some other issue..
Click to expand...
Click to collapse
Thank youu a lot! It's working with this but everytime I am rebooting Ubunutu 9.04 I have to type in these commands again to get adb...
what can I do?

you have to put this command in your .bashrc file
$ sudo gedit ~/.bashrc
then you need to enter your password
in the file you just need to add that command at the end :
PATH=$PATH:/SDK_PATH/tools/
export PATH
SDK_PATH.. you need to put your path .. something like ~/android-sdk-linux/
then you need to reboot to see if it works ;-)
enjoy !

how do you
install apps on the virtual device?????????

This is how I did it on my machine:
1. Download this zip file
2. Extract the file and copy both files to /usr/bin/
3. In the terminal type lsusb and copy first 4 ID symbols for High Tech Computer Corp
4. In the terminal type sudo gedit /etc/udev/rules.d/51-android.rules and paste the following SUBSYSTEM=="usb",ATTRS(idVendor)=="0bb4",SYMLINK+="android_adb",MODE="0666" where the bold symbols are taken from step #3.
5. Save and close everything. Unplug your device and plug it back again. ADB should now work as supposed.

Thanks for this easy instruction and for the files Karolis. Everything works fine on Ubuntu 10.10 x64

Karolis said:
4. In the terminal type sudo gedit /etc/udev/rules.d/51-android.rules and paste the following SUBSYSTEM=="usb",ATTRS(idVendor)=="0bb4",SYMLINK+="android_adb",MODE="0666" where the bold symbols are taken from step #3.
Click to expand...
Click to collapse
Just in case anyone else runs across this, in Suse 11.3 I needed to replace the brackets around idVendor with curly braces.
Code:
SUBSYSTEM=="usb",ATTRS{idVendor}=="04e8",SYMLINK+="android_adb",MODE="0666"
Even after that, I don't seem to get any devices in adb
Code:
# adb devices
List of devices attached
Here is /var/log/messages when plugging the device in
Code:
Apr 8 16:40:38 vaio kernel: [362518.911578] usb 2-1.1: new high speed USB device using ehci_hcd and address 9
Apr 8 16:40:38 vaio kernel: [362518.997898] usb 2-1.1: New USB device found, idVendor=04e8, idProduct=681c
Apr 8 16:40:38 vaio kernel: [362518.997905] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 8 16:40:38 vaio kernel: [362518.997910] usb 2-1.1: Product: SAMSUNG_Android
Apr 8 16:40:38 vaio kernel: [362518.997914] usb 2-1.1: Manufacturer: SAMSUNG
Apr 8 16:40:38 vaio kernel: [362518.997918] usb 2-1.1: SerialNumber: 3030610AA1A700EC
Apr 8 16:40:38 vaio kernel: [362519.007324] cdc_acm 2-1.1:1.0: This device cannot do calls on its own. It is not a modem.
Apr 8 16:40:38 vaio kernel: [362519.007426] cdc_acm 2-1.1:1.0: ttyACM0: USB ACM device
Apr 8 16:40:38 vaio kernel: [362519.016244] scsi11 : usb-storage 2-1.1:1.2
Apr 8 16:40:38 vaio modem-manager: (ttyACM0) opening serial device...
Apr 8 16:40:38 vaio modem-manager: (ttyACM0): probe requested by plugin 'Generic'
Apr 8 16:40:39 vaio kernel: [362520.016848] scsi 11:0:0:0: Direct-Access Android UMS Composite 0001 PQ: 0 ANSI: 2
Apr 8 16:40:39 vaio kernel: [362520.017149] sd 11:0:0:0: Attached scsi generic sg2 type 0
Apr 8 16:40:39 vaio kernel: [362520.021880] scsi 11:0:0:1: Direct-Access Android UMS Composite 0001 PQ: 0 ANSI: 2
Apr 8 16:40:39 vaio kernel: [362520.022034] sd 11:0:0:1: Attached scsi generic sg3 type 0
Apr 8 16:40:39 vaio kernel: [362520.026214] sd 11:0:0:0: [sdc] Attached SCSI removable disk
Apr 8 16:40:39 vaio kernel: [362520.027091] sd 11:0:0:1: [sdd] Attached SCSI removable disk
Apr 8 16:40:42 vaio modem-manager: (ttyACM0) closing serial device...
Apr 8 16:40:42 vaio modem-manager: (Generic): GSM modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1 claimed port ttyACM0
Apr 8 16:40:42 vaio modem-manager: Added modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1
Apr 8 16:40:42 vaio modem-manager: Exported modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1 as /org/freedesktop/ModemManager/Modems/5
ls -al /dev/android_adb before plugging phone in
Code:
# ls -al /dev/android_adb
ls: cannot access /dev/android_adb: No such file or directory
and after
Code:
ls -al /dev/android_adb
lrwxrwxrwx 1 root root 15 2011-04-08 16:35 /dev/android_adb -> bus/usb/002/008
Am I doing something wrong?

i did all thing but it stiil dont show this first in terminal
Code:
$ echo $PATH (should return the directories associated with $PATH)
$ export PATH=$PATH:/home/user/sdk/tools (replace with path to your tools directory, you may need to add 'sudo' to the beginning of this cmd)
$ echo $PATH (you should now see your tools directory added to the end of the $PATH variable)
thanks.

koala996 said:
you have to put this command in your .bashrc file
$ sudo gedit ~/.bashrc
then you need to enter your password
in the file you just need to add that command at the end :
PATH=$PATH:/SDK_PATH/tools/
export PATH
SDK_PATH.. you need to put your path .. something like ~/android-sdk-linux/
then you need to reboot to see if it works ;-)
enjoy !
Click to expand...
Click to collapse
Thanks bud, this helped me out.. Recently installed Ubuntu back on my machine and could not remember for the life of me how to do this lol. So, thanks again.

Hi My name is abbas, I followed the procedure to set the path in ubuntu for adb, however after setting the path: when I typed
$adb
the response was:
$ error while loading shared libraries: libncurses.so.5: wrong ELF class: CLASS64

Can someone help me, i'm using both Windows and Linux Ubuntu 11.10 OS, and i did manage to get adb to work on Windows, but now i prefer Linux and i can't manage adb to work. Downloaded sdk, proprietary platform etc. . . Exported path, installed lsusb-1.0.8, edited rules and inserted rules for Sony Ericsson etc. But when i type $ sudo adb start-server (then i type my password) it says that command is unknown. " sudo: adb: command not found " so my question is what the f**k i'm doing wrong?
EDIT: Changed location of sdk folder, eclipse. . . And it worked, tnx anyway. . .

sonikamd said:
you have to follow the steps for linux, they are mostly meant for ubuntu afaik. Download the special linux SDK, Eclipse etc. One thing you should do to make adb work is add your sdk/tools directory to linux's $PATH.
It should go something like this...
$ echo $PATH (should return the directories associated with $PATH)
$ export PATH=$PATH:/home/user/sdk/tools (replace with path to your tools directory, you may need to add 'sudo' to the beginning of this cmd)
$ echo $PATH (you should now see your tools directory added to the end of the $PATH variable)
$ adb devices (now adb should do something, if nothing else at least error, no devices)
Is this what you were looking for? or some other issue..
Click to expand...
Click to collapse
Thanks alot!

[GUIDE] ADB For Beginners (Setup, Use, and More!)

Hello All!
After much frustration with setting up ADB i finally got it working. Everyone said its simple and takes minimal knowledge but when things dont work, nothing really worked. Anyways after 2 hours of research trying to get ADB to work i finally got it all working and wanted to share my knowledge to anyone else that needed help.
This Guide is for windows only. If you are using Mac OS X please go here: ADB For Dummies
If you are using Linux please go here: [HOW-TO]Set up Android SDK/ADB/Fastboot on Ubuntu Linux
Like My Guide(s)? Donate
--------------------------------------------------------------------------
Things you need:
Android SDK - Download
Winrar - Download (32bit) Download (64bit)
Windows PC
USB Cable
A Rooted HTC Dream (Google G1)
--------------------------------------------------------------------------
Setting up the Android SDK
Download the file from above
Unzip to your desktop
Take the "android-sdk-windows" folder and move it to the root of your hard drive (C:\)
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista/Windows 7)
Select Environment Variables...
Press New
For Variable Name type: adb
For Variable Value type: C:\android-sdk-windows\tools
Now, [Get new sdk (1.5r3) to work]
1. Run SDK Setup.exe
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Preparing your phone for ADB
Go to Settings on your phone
Select Applications
Select Development
Make sure 'USB Debugging' is checked
--------------------------------------------------------------------------
Installing Drivers
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
For Android SDK 1.5r3+
1. Run SDK Setup.exe
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in
Code:
cd C:\android-sdk-windows\tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next line
Now you are all set to run adb commands
Note: for a list of commands type in 'adb' in cmd
CONGRATS YOU NOW HAVE ADB FULLY RUNNING!
--------------------------------------------------------------------------
Droid Explorer by Camalot
Droid Explorer is a Windows software that will download, install, and setup the android SDK for you all in under a minute so you are ready to go. I use this on a daily basis. This amazing piece of software has tons of plugins and a built in file explorer for all your files on your phone! All you gotta do is download, install, and go!
Download Droid Explorer - Here
Install the program, and let it setup the SDK files for you
Connect your phone
Enjoy!
--------------------------------------------------------------------------
"Im not getting a notification of Android ADB when i plug in my USB"
Why: Your computer has detected your phone but as a protable device and as a storage device.
Fix: This took me a lot of research and time to figure out so this is what your are going to do.
First download USBDeview - Here
Unzip it
Run USBDeview.exe as Administrator
You will see all drivers being used on your computer
Highlight and Uninstall all drivers with the description have HTC Android (Should be 3 of them)
Right Click on the driver and press uninstall
Once done, Unplug your phone and plug it back in
You should now get the notification of the ADB device
Follow the steps above to install the drivers
--------------------------------------------------------------------------
When Typing just adb in cmd you will get whats called a "usage doc" which gives you a lits of commands that you can use:
Code:
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] <file> - push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb root - restarts adb with root permissions
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PDP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
--------------------------------------------------------------------------
Commands that you should know
adb push - Insert file to phone such as Stock.apk to /data/app_s
Code:
adb push <pathtofile.apk> <file system location> - Example: adb push c:\app.apk /data/app
adb pull - Remove file from phone such as Stock.apk from /data/app_s
Code:
adb pull <pathtofile.apk> - Example: adb pull /data/app_s/Stock.apk
adb install - Install app to phone
Code:
adb install <path to file> - Example: adb install c:/apps/apps2sd.apk
adb uninstall - Uninstall app from phone
Code:
adb uninstall <name of application> - Example: adb uninstall linda.apk
For more ADB Commands go - Here
--------------------------------------------------------------------------
Thats it for ADB! Congrats and if you have any questions please ask me or if anything is missing or not correct please tell me. I got all of this from research and personal experience.

-------bump------

Good guide, pretty simple... Ill bookmark this, so I can send people that needs help here.

i have attached a zip that has the files i use to get basic use like for doing root to stock to upgrading 2.1-2.2 and other small things.
extract to C:\fastboot
in C:\fastboot you will find a "cmd" batch file. just run it and it should be ready for you to type in adb commands or fastboot. just make sure your in debug mode by doing all in the first post for installing drivers and all that.

U seriously bumped this thread? Lmfao

help?
i was trying adb and i got!
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
K:\>adb devices
List of devices attached
HT07YHL02294 offline
HT07YHL02294 device
K:\>adb remount
error: more than one device and emulator
Click to expand...
Click to collapse

ADB
i have this message Permission Denied what should i do?

thank you D200P13 soo much. i got it working thanks to your files

X10 adb issues
Can't get it to work for my X10.
ADB does not see my X10 when connected, have tried all mentioned above several times, no luck.
USB drivers seem not to install.
Do i need something special for my X10 to connect via ADB ?

p2dewit said:
Can't get it to work for my X10.
ADB does not see my X10 when connected, have tried all mentioned above several times, no luck.
USB drivers seem not to install.
Do i need something special for my X10 to connect via ADB ?
Click to expand...
Click to collapse
Turn telephone i debug mode.

when i type adb it says that it's an unrecognized command.

That's because you haven't navigated to the folder where the adb file is located...
Sent from my Nexus One using XDA App

danger-rat said:
That's because you haven't navigated to the folder where the adb file is located...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Isn't it in the android-sdk-windows folder?
EDIT
nvm found it. it's in another folder....thanks

when i run adb shell, it doesn't give me a # it gives me $. what do i do?

What are you trying to do?
Sent from my Nexus One using XDA App

Trying to flash a rom on my phone (x10) and was making sure adb is working properly before i do anything. When flashing the new rom there's some bugs that require adb to fix. From my understanding "$" means i don't have su access. Thanks for the help btw. Sorry for bothering you. Just taking proper precautions.
EDIT
Sorry again. Found my answer. I forgot to unlock my device to accept superuser permissions. Thanks for your help

to check ur phone is detected by adb....
i type "adb shell" in cmd,and according 2 u i should show #.....but it shows $ to me......why?

To check connection, type "adb devices"
"adb shell" will allow you to work remotely on your device. If the $ doesn't change to #, then you don't have root access.
Sent from my Nexus One using XDA App

If your just trying to set up adb to riot your device, I put this together to make things much easier...
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA App

Where is the Mac Specific version. Everything you posted is for windows mate!

How to install ubuntu on the Droid 4

How to install ubuntu on the Droid 4
Note to mods: this thread is a branch off of this thread
Huge thanks to zacthespack for creating the ubuntu installer app and original boot script and to zeroktal for modifying the script to work on the D4 and helping me get it working on my device.
I decided to take my experience in setting this up and put it into a how-to so that others could enjoy the experience of having ubuntu on the Droid 4. If zackthespac or zeroktal have any problems with me making and putting this guide up, please let me know and I will remove it.
Knowledge Required:
working knowledge of command line
working knowledge of vi
OR the ability to learn how to use both
Tools Required:
A rooted Motorola Droid 4
BusyBox (Android Market)
Terminal Emulator (Android Market)
Android VNC Viewer (Android Market)
Ubuntu Installer App (Android Market)
zeroktal's ubuntud4.zip file (attached to this post and mediafire)
Vi Cheat Sheet (lagmonster.org)
Step by Step:
Install BusyBox, Terminal, and Android VNC Viewer
Install and run Ubunutu Installer App
Follow the on-screen instructions and click next
Download either the Small or Large image to your phone, (use zeroktal's ubuntud4.zip file instead of the boot script provided in the guide) after the image downloads (will take a while because the file is HUGE) click next
For this screen, the instructions differ from the app.
1. With your D4 plugged into your PC in USB Mass Storage, create a directory (folder) called ubuntu in the EXTERNAL sdcard's root*
2. Extract the image you downloaded to that directory
3. Download and extract the attached .sh (ununtud4.zip) to that directory
4. Disconnect your phone from your PC
5. Open terminal and run the following commands:
su [ENTER]
mount -o remount,rw,exec,suid /dev/block/vold/179:1 /mnt/sdcard-ext [ENTER]
cd /mnt/sdcard-ext/ubuntu [ENTER]
sh ubuntud4.sh [ENTER]
960x540 [ENTER]**If you get an error message: ubuntud4.sh: 45: syntax error: end of file unexpected (expecting "then") see troubleshooting section below.killall -TERM Xtightvnc [ENTER]
vncserver :1 -geometry 960x540 [ENTER]**6. Open androidVNC app and enter the following settings:
Nickname: Anything you want
Password: ubuntu
Address: localhost
Port: 5901
Color Format: 24-bit color (4 bpp)
7. Hit connect
8. Hit your menu soft button and then set input mode to touchpad
9. You have ubuntu on your Droid 4!
To "shut down" ubuntu:
press the menu button, select disconnect in VNC
In terminal type this command 3 times (terminal will close itself when you are done):
exit [ENTER]
To "start up" ubuntu again:
Follow steps 5-8 above
Troubleshooting:
If you get the error message: ubuntud4.sh: 45: syntax error: end of file unexpected (expecting "then") you are about to have fun with vi at the command line.
Do the following from inside terminal:
su [ENTER]
cd /mnt/sdcard-ext/ubuntu [ENTER]
vi ubuntud4.sh [ENTER]If you see ^M or ^ at the end of any line (remember to scroll all the way to the right to see the end of long lines) remove it. once you do that, everything should work just fine. (See the Vi Cheat Sheet above for help with Vi)
Note: Vol Up + E is [ESC] by default in this terminal emulator
Notes:
* It does not have to be on the external SD, but if you put it on the internal SD you will have to modify things as needed-- if you dont know what needs to be changed, just put it on the external SD.
** Screen size can be whatever you want it to be, but 960x540 is the size of the D4 screen.
*** This is a fairly involved process... especially when it comes to editing the .sh file in vi things can get very frustrating and hard, but just take your time and you will get it. As always, doing anything with root access on your phone, especially on the command line has risks. I am not responsible if anything goes wrong with your phone... proceed at your own risk!

greekchampion04 said:
Notes:
* It does not have to be on the external SD, but if you put it on the internal SD you will have to modify things as needed-- if you dont know what needs to be changed, just put it on the external SD.
** Screen size can be whatever you want it to be, but 960x540 is the size of the D4 screen.
*** This is a fairly involved process... especially when it comes to editing the .sh file in vi things can get very frustrating and hard, but just take your time and you will get it. As always, doing anything with root access on your phone, especially on the command line has risks. I am not responsible if anything goes wrong with your phone... proceed at your own risk!
Click to expand...
Click to collapse
I actually got it up and running on my internal sdcard partition. Pretty much just have to modify the Mount remount command, and a few lines in the script.
Here's the original command
Code:
mount -o remount,rw,exec,suid /dev/block/vold/179:1 /mnt/sdcard-ext
And the modified one
Code:
mount -o remount,rw,exec,suid /dev/block/vold/179:57 /mnt/sdcard
Only things you have to change are the device location(179:57) and mount location(drop the -ext after sdcard)
Now, after that you also have to modify the script a bit. Just go through it, and anywhere that you see sdcard-ext, drop the -ext off the end.

thanks for putting that up for everybody! like i said, if you know what you are doing its not a hard swap to make.

Is anyone else getting just a gray screen when they remote in? What could be causing this?

i had that same problem at first... did you use zeroktal's ubuntud4.zip file? or did you use the ubuntu.sh file included in the app?

I used the sh file included. I did however fix the problem, when mounting at the start i confused vold with void. I did not get the file system mounted properly. This method does work!! however I am currently trying to get bash on my droid to replace sh as the shell. I've checked the forums but have not found anything yet about someone installing bash on the droid 4. With no way for nandroids I feel i should wait before I kill sh.
Sent from my DROID4 using XDA App

If you mod your init.sh in your root directory to the following, your vnc will work on startup without issue. It will also shutdown vnc on exit.
#!/bin/bash
#############################################
# Asks User to screen size and saves as REZ #
#############################################
#echo "Now enter the screen size you want in pixels (e.g. 800x480), followed by [ENTER]:"
#read REZ
##############################################
# Pick which desktop environment to use, this#
# is done by having a xstartup file for each #
# desktop, then renaming the one you want to #
# use to 'xstartup' before boot #
##############################################
echo "Please select which Desktop environment you want to use, type the number to select it then press [ENTER]"
echo "1 - LXDE"
echo "2 - Gnome"
echo "Make your Selection:"
read DESKTOP
if [ $DESKTOP == 1 ]
then
mv /root/.vnc/lxstartup /root/.vnc/xstartup
fi
if [ $DESKTOP == 2 ]
then
mv /root/.vnc/gxstartup /root/.vnc/xstartup
fi
###########################################
# Tidy up previous LXDE and DBUS sessions #
###########################################
rm /tmp/.X* > /dev/null 2>&1
rm /tmp/.X11-unix/X* > /dev/null 2>&1
rm /root/.vnc/localhost* > /dev/null 2>&1
rm /var/run/dbus/pid > /dev/null 2>&1
############################################################
# enable workaround for upstart dependent installs #
# in chroot'd environment. this allows certain packages #
# that use upstart start/stop to not fail on install. #
# this means they will have to be launched manually though #
############################################################
dpkg-divert --local --rename --add /sbin/initctl > /dev/null 2>&1
ln -s /bin/true /sbin/initctl > /dev/null 2>&1
###############################################
# start vnc server with given resolution and #
# DBUS server, (and optionally an SSH server) #
###############################################
dbus-daemon --system --fork > /dev/null 2>&1
/etc/init.d/ssh start
vncserver :1 -geometry 960x540
echo
echo "If you see the message 'New 'X' Desktop is localhost:1' then you are ready to VNC into your ubuntu OS.."
echo
echo "If VNC'ing from a different machine on the same network as the android device use the 1st address below:"
##########################################
# Output IP address of android device #
##########################################
ifconfig | grep "inet addr"
echo
echo "If using androidVNC, change the 'Color Format' setting to 24-bit colour, and once you've VNC'd in, change the 'input mode' to touchpad (in settings)"
echo
echo "To shut down the VNC server and exit the ubuntu environment, just enter 'exit' at this terminal - and WAIT for all shutdown routines to finish!"
echo
###############################################################
# Spawn and interactive shell - this effectively halts script #
# execution until the spawning shell is exited (i.e. you want #
# to shut down vncserver and exit the ubuntu environment) #
###############################################################
/bin/bash -i
#########################################
# Disable upstart workaround and #
# kill VNC server (and optionally SSH) #
# Rename used xstartup to its first file#
#########################################
killall -TERM Xtightvnc
/etc/init.d/ssh stop

Also save the follow lines between ### as remount.sh on your system partition. Then chmod 755 /system/remount.sh. Now you can just run run from a terminal /system/remount.sh and voila it remounts correctly and starts ubuntu(with the above fixes). Im still working on the unmounts.
####### for the internal sd card
mount -o remount,rw,exec,suid /dev/block/vold/179:57 /mnt/sdcard
/mnt/sdcard/ubuntu/ubuntu.sh
######
OR
####### for the external sd card
mount -o remount,rw,exec,suid /dev/block/vold/179:1 /mnt/sdcard-ext
/mnt/sdcard-ext/ubuntu/ubuntu.sh
#######

great stuff!

feel free
Feel free and take, modify, repost or edit anything I touch.

QUESTION:
After I delete all the ^M and ^ what do i do next? I try to hit the command ":x" to exit and save changes but it just creates another line. Also when I press VOL UP + E to escape nothing happens.

PhanTuhC said:
QUESTION:
After I delete all the ^M and ^ what do i do next? I try to hit the command ":x" to exit and save changes but it just creates another line. Also when I press VOL UP + E to escape nothing happens.
Click to expand...
Click to collapse
In vi, the command to save and exit is :wq (probably short for write and quit).

remember, read up on the vi quick-reference guide: http://www.lagmonster.org/docs/vi.html

OK I fixed it but now its not letting me connect with androidVNC. All the settings entered is correct but when I try to connect it says:
"VNC connection failed!" localhost/127.0.0.1:5901 - Connection refused"

ok, i've gone thru this a few times (slowly and deliberately) and must be missing something...the directions seem pretty straightforward! here's what i know...
busy/terminal/vnc are all installed
small 2.5gb image is unzipped in /sdcard-ext/ubuntu directory
the attached .sh file from page 1 is in the same directory
i removed all ^M using vi
but when I try sh ubuntud4.sh i get an error...
"mkdir failed for /data/local/mnt/ubun, No such file or directory"
(plus a few other errors)
should the directory be "ubun" or "ubuntu"? am I typing something incorrectly?

copy and paste new script
Copy and paste the new scripts I posted. They will fix your problem. Remember to use the remount script from /system/ the rest will work perfectly if you are root. I'll check back later on your progress.

Ok, well I started from scratch (deleted both .img and .sh files) and it's still not working.
I have all the apps installed (and yes rooted, SU works just fine)
I used Ubuntu Installer app to download the image zip (tried both the large and small img)
I downloaded the .sh file from the first post
The /sdcard-ext/ubuntu/ folder now has two files: "ubuntu.img" and "ubuntud4.sh"
All ^M characters have been removed from .sh file
Still no joy...
Ideas? What am I missing?
In terminal, I can set SU permissions and the mount/cd commands work just fine...it's the last sh command that spits out a bunch of errors about not being able to create/find the directories.
I'm going to format the sdcard and try again...any help is appreciated.
Update: Even after re-formatting the SD and following the steps exactly, no luck!

Did you remember to remount the sdcard with exec and suid permissions?

Andbuntu will work much better than this method. It works on every single phone with modification to the "environmental variables".
http://code.google.com/p/andbuntu/
Follow the directions in the script to make the process much easier than the first post.
instructions:
generate an image with rootstock on an ubuntu computer.
put it on /sdcard/ubuntu/ubuntu.img
run the script on your phone with "sh /path/to/script"
Here is the script. http://andbuntu.googlecode.com/svn/trunk/uboot
Also, run "firstRun" to make things like terminals work properly.

Adamoutler: That didnt work for me. The permissions were incorrect on the mounted partitions.
Sent from my DROID4 using XDA App

[Q] trouble rooting kindle 2 (ver 10.2.6)

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

Install ADB on Windows & ubuntu 12.04 or 12.10

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

Database Develop

welcome