Related
I found many having difficulty in getting adb working especially in linux so created this seperate fullproof thread as tried,tested & working method to get adb working.
This method can also be used for other Android phones which are not supported by google drivers (so called third party usb vendors).
Replace 0x1d91 in this tutorial with your device vendor id.If u don't know vendor id then ask here I will guide u how to know vendor id.
If u don't have usb drivers for your device then also ask me I will guide how u can modify google usb drivers to use with your device.
Now let's talk of Micromax A70:
WINDOWS 7:
Drivers for Micromax A70- Micromax A70 USB Driver.rar
Install JDK and Android SDK and update SDK.(google if u want to know how)
Turn on USB Debugging in phone in Settings>Applications>Development
Connect phone to PC & install drivers
Your pc may not find the drivers so go to Device Manager n Update Driver n choose location of the downloaded drivers.
Now Most important part.
Create adb_usb.ini file in C:\Users\YOUR USERNAME\.android folder and add following to the file.
0x1d91
(filename is adb_usb.ini, if u already have that file then delete it & create new one OR u can add 0x1d91 to next line without deleting anything in file.)
Save the file and exit.
OR
Download this adb_usb.ini file n place it in C:\Users\YOUR USERNAME\.android
Now open command prompt and navigate to platform-tools directory of android sdk.
Type "adb devices" without quote and hit enter.
Your Micromax A70 will show up in connected devices for sure.
No need to install 91pc suite anymore.
WINDOWS 7 64bit:
Same steps of above 32bit system but I added this to avoid Driver not signed problem at boot which forced to use F8 option to disable driver signing check.
Driver Signature Enforecement Overrider
This software will take care of this issue.How-to is also on the download page.U can download it here-
http://www.softpedia.com/get/Tweak/Video-Tweak/Driver-Signature-Enforcement-Overrider.shtml
LINUX (Ubuntu):
Install JDK and SDK. (i will provide link to install jdk 7 which i used)
JDK- How To Install Oracle Java 7 (JDK) In Ubuntu ~ Web Upd8: Ubuntu / Linux blog
SDK-Follow below steps or go to this link ADB
Credits to Bytecode for that.
Download tar.gz package & extract it.
In terminal
cd /home/user/extracted_folder/android-sdk-linux_x86/tools
./android
Download all necessary packages by clicking on "Available packages" and checking "Android Repository". Then click on "install selected" button and another window will pop up. Check "accept all" and click on "install" button. Wait and you will have all SDK packages installed,adb too.
sudo gedit /etc/udev/rules.d/99-android.rules
Then paste following in it.(I am writing code for Micromax only,there is a list of all manufactures,if u want I can give it.U can also get it using link above by Bytecode from xda)
Now, use following instead so u will also get fastboot working alongwith adb.
Code:
#ADB on Micromax A70
SUBSYSTEM=="usb", SYSFS{idVendor}=="1d91", MODE="0666"
#fastboot on Micromax A70
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
Save & Exit.
For ubuntu 11.04,paste this.(i m not sure of this but found in more then 2 guides)
Code:
#ADB on Micromax A70
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1d91" TEST=="/var/run/ConsoleKit/database", RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"
#fastboot on Micromax A70
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1" TEST=="/var/run/ConsoleKit/database", RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"
Save & exit.
Code:
sudo chmod a+rx /etc/udev/rules.d/99-android.rules
sudo service udev restart
sudo gedit .bashrc
At the end paste this-
Code:
export PATH=${PATH}:/home/YOUR-USERNAME/android-sdk-linux_x86/platform-tools
(this may change according to your android-sdk directory)
Code:
source ~/.bashrc
Now the most important part, again at Terminal,
Code:
mkdir -p ~/.android && echo 0x1d91 > ~/.android/adb_usb.ini && adb kill-server && adb devices
Viola!!!
Trust me,if you follow all steps properly adb will work for sure.
HIT THANKS IF I HELPED...
Micromax A78
ADB recognised my phone, but cannot start in fastboot. I switch off the phone, press camera buttton, an plugin usb, but the phone cannot load into fastboot its showing chargin sign no matter how long i pressed the camera button. Please help
Definition:
ADB is the android debugging bridge that allows you to control your phone from your PC and is a bridge allowing you transfer stuff from it
Fastboot is usually used in bootloader and used a lot in unlocking your bootloader and commands in it
Setting up ADB:
1.Download the ZIP file from the attachments and extract it in C:\SDK\platform-tools (You will need to create these folders)
2. Go to command prompt by typing this word in menu search
3.Start writing
Code:
cd C:\SDK\platform-tools
adb.exe
You will see
Code:
Android Debug Bridge version 1.0.29
-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. Overrides ANDROID_SERI
AL
environment variable.
-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
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
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
(-l means list but don't copy)
(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 forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
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 backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
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 reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP 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.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
Don't freak out everything will be explained
4.Connect device and make sure that USB Debugging is enabled from Settings:Applicationsevelopment(on GB)
Settingseveloper Options(on ICS and HC)
5.Write
Code:
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Device name
6.There are common commands used on ADB:
Code:
adb reboot
adb reboot recovery
adb reboot bootloader
adb push C:\<directory>\file /sdcard/
adb pull /sdcard/file C:\<directory>\
adb install C:\<directory>/file.apk
or /sdcard/<directory>/file.apk
adb remount
Push and Pull means copy form directory to another
ADB Shell for in device commands
Code:
adb shell
#mv /sdcard/file /system/app
#cp /sdcard/file /system/app
#rm /sdcard/file
#mkdir /sdcard/yourfoldernamehere
#ls /sdcard/<directory>
Setting up fastboot: Your phone must be on bootloader
Code:
cd C:\SDK\platform-tools
Commands List:
Code:
fastboot devices – lists which devices in fastboot mode are currently attached to your computer
fastboot boot <filename> – boots a rom stored on your pc specified by the filename
fastboot flash <partition> <filename> – flashes a rom stored on your pc, partition can be one of {boot, recovery, system, userdata}
Example: fastboot flash recovery C:\<directory>\recovery.img
PS: When i wrote <directory> it means like C:\Users\Desktop\Desktop\file
Or you can put the file in the the platform-tools folder you created so
write Ex:
Code:
adb push file.apk /sdcard/
Got stuck with htc logo after the LeeDroid flash on my HTC
Hi All,
Good morning. I am very new with Android, I did the flash rom using Leedroid 4.3.0 I can flash it ok, but it said I use s-off so I need to extract the boot.img from rom.zip and flash it.
I have no idea how to flash it. Can anyone guide me step by step.
I tried the ADB.exe with CMD but no luck, although it say (sending boot <3853 kb> ... okay, writing boot... OKAY, I still cannot get it to work, after reboot, I still got stuck with htc logo.
I am using HTC flyer, HBOOT 6.10.1002
Thank you in advance for your help
you need to flash it when you are in bootloader using fastboot command:
fastboot flash boot boot.img
You are my first teacher......enjoyed it....Thanks a lot...
Incredible s stuck on loading
Hey All,
Here is my story -
Never felt the need of rooting my phone, until one of my relatives, done that for me. If I ever knew, that i will have so many problems, I would have never let him do that.
Moving on, I couldn't find a rom fitting myself, always had bugs, used too much of my battery, or so on. Got tired losing everything, everytime i had to change the rom, after finding a bug i couldn't stand. So, I came back to original rom 2.3.5. Thought i will just update and will have S-off phone with original software.
Somehow it didn't let me update, I stayed with that for few months, then one day i decided i can't stand the old soft, and started working on getting my phone back to s-on and original rom. Used Android flasher to flash this file engHBOOToverARX . The next step was to flash the original rom, via
Android flasher. But i couldn't find it on internet. Therefore i thought it's just gonna be easier and faster that i'll just go and scan for the update.
It found and finally was updating when I was happy i'll get back to normal phone. Unfortunately, It wouldn't load the software anymore, only the white screen with the HTC logo.
Bootloader still says
Revolutionary
Vivo PVT SHIP S-OFF RL
HBOOT - 6.13.1002
RADIO - 3822.10.08.28_M
eMMC - boot
Apr 1 2011, 18:34:39
I tried to follow the steps, on the cmd.
But it looks like it can not find the device.
My phone is connected to the computer via usb cable and on the bootloader menu.
PLEASE HELP ASAP.
I am using my old Nokia 6310i as the backup plan at the moment, and believe me it is not fun at all, uxcept the fact that I make everyone laugh
when I take it from my pocket
Titas
Where to start:
This is not a general help thread
This is not even in the Q&A forum
You have a VIVO which is an incredible s not SAGA (codename for desire s so you're in the wrong forum)
Sywepd form my DsereiS
explanation
"Setting up fastboot: Your phone must be on bootloader "
1st... what do you mean by "Your phone must be on bootloader" & how to do ??
2nd... I accessed this thread from another one concerning nabi II tablet rooting .... but I can't figure out the DIRECT importance to know that ...in regard to rooting the nabi II
.... is it essential ??
3rd.. can u please write the prompt commands in full manner ... as sometimes u use "\" or "/" eg:
"adb install C:\<directory>/file.apk
or /sdcard/<directory>/file.apk "
that's a little bit difficult ..thanks
ayanah said:
"Setting up fastboot: Your phone must be on bootloader "
1st... what do you mean by "Your phone must be on bootloader" & how to do ??
Click to expand...
Click to collapse
If you don't know that then you need to do A LOT of reading before attempting to play around with your device
ayanah said:
2nd... I accessed this thread from another one concerning nabi II tablet rooting .... but I can't figure out the DIRECT importance to know that ...in regard to rooting the nabi II
.... is it essential ??
Click to expand...
Click to collapse
I have no idea how you got here from the Nabi II forum - unless someone there felt that this was a decent guide to also use on the Nabi II
ayanah said:
3rd.. can u please write the prompt commands in full manner ... as sometimes u use "\" or "/" eg:
"adb install C:\<directory>/file.apk
or /sdcard/<directory>/file.apk "
that's a little bit difficult ..thanks
Click to expand...
Click to collapse
The OP is NOT going to rewrite his guide just for you after 6 months. Also, the difference between using '\' and '/' depends on whether you are using Windows or Linux - if you can't work that out then I would also suggest that you leave your device alone before you destroy it.
a reply
SimonTS said:
If you don't know that then you need to do A LOT of reading before attempting to play around with your device
I have no idea how you got here from the Nabi II forum - unless someone there felt that this was a decent guide to also use on the Nabi II
The OP is NOT going to rewrite his guide just for you after 6 months. Also, the difference between using '\' and '/' depends on whether you are using Windows or Linux - if you can't work that out then I would also suggest that you leave your device alone before you destroy it.
Click to expand...
Click to collapse
by the way .. in less than 1 hrs I used his guide to install programs from my PC (& I had no previous knowledge even where to start command prompt) on my old galaxy i5700 (use it for trials) ... I installed the programs using "adb install ....." & every thing is OK ... & I had successfully rooted my galaxy s6102 using another thread (not the one click programs) also every thing is OK ... I'd like to tell you I know about (rooting) less than 2 days ago ... so I think this is a good start for me ..... SO .. it would be appreciated to anyone who could answer me in short just showing little pit details & the pitfalls to avoid ...
also I thought"\" is where I copy from &"/" where I copy to i.e. concerning the direction of the path ... but I wasn't sure so I needed to get that explained
thanks for help but let OP take the decision HIMSELF.
referral thread :http://forum.xda-developers.com/showthread.php?t=1905674
I have been trying to do a factory reset of the Nabi 2, and since I can't seem to access the "Mommy Mode", I thought I could do it from the recovery menu. So far I have yet to find any factor reset option available. Is there such a beast or am I out of luck?
kcallis said:
I have been trying to do a factory reset of the Nabi 2, and since I can't seem to access the "Mommy Mode", I thought I could do it from the recovery menu. So far I have yet to find any factor reset option available. Is there such a beast or am I out of luck?
Click to expand...
Click to collapse
This is not the Nabi 2 forum...
And don't even know what the hell the "Mommy Mode" is, but with the command <adb reboot recovery> should bring you to the recovery.
Sent from my Nexus 7 using xda app-developers app
c.m.b said:
This is not the Nabi 2 forum...
And don't even know what the hell the "Mommy Mode" is, but with the command <adb reboot recovery> should bring you to the recovery.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Actually, was able to get it sorted... I am not sure how I ended up posting on this thread, because I was replying on the Rooting Nabi thread... Weird!
If my USB debugging was off occurred when the soft brick, is there any way to get access via ADB?
My softbrick was caused by a bad file (framework-res.apk).
Is there any way to replace this file?
Nice work mOh19973 :good:
Your guide came in really handy for rooting the Nabi 2 that we got my son for Christmas. He'll be really excited once he sees that the Google play store is now available
Thanks,
Bodie
HELP!!!
mOh19973 said:
Definition:
ADB is the android debugging bridge that allows you to control your phone from your PC and is a bridge allowing you transfer stuff from it
Fastboot is usually used in bootloader and used a lot in unlocking your bootloader and commands in it
Setting up ADB:
1.Download the ZIP file from the attachments and extract it in C:\SDK\platform-tools (You will need to create these folders)
2. Go to command prompt by typing this word in menu search
3.Start writing
Code:
cd C:\SDK\platform-tools
adb.exe
You will see
Code:
Android Debug Bridge version 1.0.29
-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. Overrides ANDROID_SERI
AL
environment variable.
-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
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
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
(-l means list but don't copy)
(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 forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
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 backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
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 reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP 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.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
Don't freak out everything will be explained
4.Connect device and make sure that USB Debugging is enabled from Settings:Applicationsevelopment(on GB)
Settingseveloper Options(on ICS and HC)
5.Write
Code:
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Device name
6.There are common commands used on ADB:
Code:
adb reboot
adb reboot recovery
adb reboot bootloader
adb push C:\<directory>\file /sdcard/
adb pull /sdcard/file C:\<directory>\
adb install C:\<directory>/file.apk
or /sdcard/<directory>/file.apk
adb remount
Push and Pull means copy form directory to another
ADB Shell for in device commands
Code:
adb shell
#mv /sdcard/file /system/app
#cp /sdcard/file /system/app
#rm /sdcard/file
#mkdir /sdcard/yourfoldernamehere
#ls /sdcard/<directory>
Setting up fastboot: Your phone must be on bootloader
Code:
cd C:\SDK\platform-tools
Commands List:
Code:
fastboot devices – lists which devices in fastboot mode are currently attached to your computer
fastboot boot <filename> – boots a rom stored on your pc specified by the filename
fastboot flash <partition> <filename> – flashes a rom stored on your pc, partition can be one of {boot, recovery, system, userdata}
Example: fastboot flash recovery C:\<directory>\recovery.img
PS: When i wrote <directory> it means like C:\Users\Desktop\Desktop\file
Or you can put the file in the the platform-tools folder you created so
write Ex:
Code:
adb push file.apk /sdcard/
Click to expand...
Click to collapse
When I go to command and type in adb.exe i get an error. Also when I try to download the file it doesn't let me have the option of saving the file to platform-tools. I have to move it there myself and then I extract the files. I've done this several different times and still keep coming up with same results on the command prompt! Please help!!!! Been working on this for 4 hours!!!
Once in directory you do not type adb.exe. just type
Adb devices
If your Android device is hooked into the USB it should be listed
Flyer
I am having major troubles trying to root my nabi 2 tablet. I tried replying on the actual thread but it wouldnt let me. If anyone can help me out please do. I've tried 2 ways which are pretty much the exact same.
1. download pdanet - install (whilst tablet is plugged in) and chose samsung and it shows up in devices as working fine
2. downloaded platform-tools and made SDK and platform-tools folder. I have the install files as well
3. Run cmd type cd C:\SDK\platform-tools. type adb.exe and it loads in.
4. Run install and chose option 1.
It goes to the option where I choose reboot kernal then it restarts and I get the green android icon with the red triangle with esclamation mark in it.
What am I doing wrong its been doing my head in for 3 days now if anyone can help it would be great. thanks
sweetpea8852 said:
When I go
Click to expand...
Click to collapse
In future, please don't quote the entire OP lie that when there is no need. It makes threads much more difficult to follow.
Klarkus said:
I am having major troubles trying to root my nabi 2 tablet. I tried replying on the actual thread but it wouldnt let me. If anyone can help me out please do. I've tried 2 ways which are pretty much the exact same.
1. download pdanet - install (whilst tablet is plugged in) and chose samsung and it shows up in devices as working fine
2. downloaded platform-tools and made SDK and platform-tools folder. I have the install files as well
3. Run cmd type cd C:\SDK\platform-tools. type adb.exe and it loads in.
4. Run install and chose option 1.
It goes to the option where I choose reboot kernal then it restarts and I get the green android icon with the red triangle with esclamation mark in it.
What am I doing wrong its been doing my head in for 3 days now if anyone can help it would be great. thanks
Click to expand...
Click to collapse
This is the Desire S forum. You may have been directed here, but we don't use Nabi tablets I'm afraid.
Nabi 2
Klarkus said:
I am having major troubles trying to root my nabi 2 tablet. I tried replying on the actual thread but it wouldnt let me. If anyone can help me out please do. I've tried 2 ways which are pretty much the exact same.
1. download pdanet - install (whilst tablet is plugged in) and chose samsung and it shows up in devices as working fine
2. downloaded platform-tools and made SDK and platform-tools folder. I have the install files as well
3. Run cmd type cd C:\SDK\platform-tools. type adb.exe and it loads in.
4. Run install and chose option 1.
It goes to the option where I choose reboot kernal then it restarts and I get the green android icon with the red triangle with esclamation mark in it.
What am I doing wrong its been doing my head in for 3 days now if anyone can help it would be great. thanks
Click to expand...
Click to collapse
Try this link
http://forum.xda-developers.com/showthread.php?t=1905674
i need some help in cammand propt for adb devices please. my problem is when i push enter on putting in adb devices it says emulator-5554 device and then my device underneath, i need to some how turn off the emulator because it will only finish process with one adb device. has anyone asked you about this before? can you help me?
This post is adapted from a post in the android hacking general thread by user jackattack79.
I just changed the udev rules to work with our tf700's. Perhaps it can be helpful here. Thanks again to jackattack79 for the original post.
Anyone wanting to use adb with your ASUS Infinity through Ubuntu/Linux... follow these steps (these steps will make accessing adb much easier and allow abd to recognize your phone)[Please note - modifying the .bashrc in step 1 is not required; it will just make using Android SDK much easier for beginners]:
1. Modifying the PATH Environment Variable will help out immensely when it comes down to making use of SDK tools like ADB. Doing this will also allow you to execute certain protocols like ADB from ANY location. So if you're operating from the Desktop, you don't have to redirect to the SDK's platform-tools folder to make use of ADB if you need to make use of it.
To modify the PATH variable of your system, you need to edit your .bashrc file. To do so, in a terminal, execute the following command:
$ nano ~/.bashrc
You will now have the Nano text editor enabled on the terminal. Now, at the very top of the file(yes, that means go to the top and hit enter to create some space at the top. Then just copy and paste - a caveman really could do it!), enter the following:
#AndroidDev PATH
export PATH=${PATH}:~/android-sdk-linux/tools
export PATH=${PATH}:~/android-sdk-linux/platform-tools
Once you're finished, press CTRL + X, Y, and then hit Enter to save your changes and exit the Nano text editor.
2. Now that we have our PATH variable set up, we need to make sure our hardware will be detected once we initialize ADB. However, Ubuntu won't allow ADB access to the Android phone via USB unless the appropriate udev rule is set. This is Bug #316215. In order to get around this rule, you need to create a rule file as root.
In a terminal, execute the following command that will create the rule file. This will utilize the graphical sudo command, so that we can still have control over the file if we're not a root user.
Now, you create a file:
sudo nano /etc/udev/rules.d/51-android.rules
Copy and paste the following udev rule in the text editor that opened up which contains the new rule file we created:
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4c91", MODE="0666" #Normal tf700
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4daf", MODE="0666" #Fastboot tf700
Once you've copied and pasted the udev rule in the text editor which contains your newly created rule file, save your changes and quit (Control+X, Y, Enter). Now that you've set your udev rule you have to reboot (shut down terminal and reopen; I also recommend unplugging your phone from usb and plugging it back in) so that ADB will be in your path.
To test your changes, open up a terminal and execute the following:
$ adb devices
You should now see:
List of devices attached
C61DAXXXXXXX device
If you see:
List of devices attached
???????????? no permissions
Reread this post and try again.
more helpful udev info here http://wiki.cyanogenmod.com/wiki/Udev
Can't get this to work.
I'm on Ubuntu 12.10 64 bit version.
I have installed Android SDK, i have put in the paths in bashrc, i have created the file in /etc/udev/rules.d/51-android.rules
When i iisue the command abd devices:
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
My tab don't show up...
I have tried lsusb and there it lists it as vendor 0b05 and product 4c90
I have tried with putting that in to 51-android.rules but to no avail.
Any hint on how i can get this to work?
I have even rebooted the laptop and tried restarting the adb deamon with: adb kill-server
Best regards Mackis
Mackis said:
Can't get this to work.
I'm on Ubuntu 12.10 64 bit version.
I have installed Android SDK, i have put in the paths in bashrc, i have created the file in /etc/udev/rules.d/51-android.rules
When i iisue the command abd devices:
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
My tab don't show up...
I have tried lsusb and there it lists it as vendor 0b05 and product 4c90
I have tried with putting that in to 51-android.rules but to no avail.
Any hint on how i can get this to work?
I have even rebooted the laptop and tried restarting the adb deamon with: adb kill-server
Best regards Mackis
Click to expand...
Click to collapse
Yes, use the values you got with lsusb.
Did you set the permissions on the rules file to 0644 so all can read?
Yepp
ls -al /etc/udev/rules.d/51-android.rules
-rw-r--r-- 1 root root 194 okt 22 14:34 /etc/udev/rules.d/51-android.rules
And i even reloaded the udev rules by:
udevadm control --reload-rules
That way i don't have to reboot. But i tried rebooting to.....
Hmmmm in some mysteroius way USB debugging was disabled, i'm 100% confident i enabled it.......
Now i find my device puhhhhhhhhhh Was so near of reinstalling linux and going back to ubuntu 12.04 as a last resort.
Thanks for the help!!
Best regards Mackis
Mackis said:
Can't get this to work.
I'm on Ubuntu 12.10 64 bit version.
I have installed Android SDK, i have put in the paths in bashrc, i have created the file in /etc/udev/rules.d/51-android.rules
When i iisue the command abd devices:
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
My tab don't show up...
I have tried lsusb and there it lists it as vendor 0b05 and product 4c90
I have tried with putting that in to 51-android.rules but to no avail.
Any hint on how i can get this to work?
I have even rebooted the laptop and tried restarting the adb deamon with: adb kill-server
Best regards Mackis
Click to expand...
Click to collapse
Are you using a US tf700 ASUS Infinity?
Just wondering why the product code was different for you.
Thanks
lowreeds said:
Are you using a US tf700 ASUS Infinity?
Just wondering why the product code was different for you.
Click to expand...
Click to collapse
lsusb with USB debugging disabled:
Bus 002 Device 070: ID 0b05:4c90 ASUSTek Computer, Inc.
lsusb with USB debugging enabled:
Bus 002 Device 071: ID 0b05:4c91 ASUSTek Computer, Inc.
64 bit used to require certain 32 bit libs to be installed once upon a time. Not sure if it's still the case, but you could try:
sudo apt-get install ia32-libs
_that said:
lsusb with USB debugging disabled:
Bus 002 Device 070: ID 0b05:4c90 ASUSTek Computer, Inc.
lsusb with USB debugging enabled:
Bus 002 Device 071: ID 0b05:4c91 ASUSTek Computer, Inc.[/QUOTE
Ahhh.
i see.
Click to expand...
Click to collapse
Yeah you are right, for some reason debugging was unchecked and im 100%sure i checked it. I have it up and running now. Thanks!!
//Mackis
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
lowreeds said:
List of devices attached
C70KASXXXXXX device
Click to expand...
Click to collapse
Just a heads up. I'm not sure it's such a good idea to out your serial number like that (I censored it in my quote for you)...
This guide was created using information taken from:
http://bernaerts.dyndns.org/linux/247-ubuntu-automount-nexus7-mtp
http://www.webupd8.org/2012/12/how-to-mount-android-40-ubuntu-go-mtpfs.html
http://blog.itsbilal.com/index.php/...d-4-0-phonetablet-to-ubuntu-the-reliable-way/
and others. They show you how to determoine all the id information required to set up mtp mounting. This guide will just focus in on what you need to get your Asus TF700 connected.
Background:
Latest Android devices are using 2 different USB connexion modes : PTP and MTP.
With PTP mode, the tablet is seen as a digital camera. This is working Out Of The Box under Ubuntu 12.04. But, you can only access DCIM directory of your device.
With MTP mode, the tablet is seen as a multimedia device where you can access the complete exported filesystem. But it doesn't work Out Of The Box under Ubuntu. It needs some setup and configuration to work.
Note: Gvfs has been updated in Ubuntu 13.04 Raring Ringtail, bringing a new MTP backend which allows users to access Android 4.0 devices which do not support the USB Mass Storage. So this should work out of the box with Raring.
Even if you can access easily a MTP device thru a program called gmtp, it is not as convenient as a conventional USB mass storage, accessible directly from Nautilus.
This guide explains how to configure your Ubuntu computer to directly access your Asus TF700, exported filesystem in MTP mode as soon as you plug it to a USB port.
Thanks to some udev rules, your tablet will automatically mount when device is plugged in & unmount when device is unplugged.
This guide has been done for Asus TF700, but it should work with any other MTP device (Android phone or tablet, MP4 player, ...) if you adapt the Udev rules according to your device.
The Basic steps are:
1) Allow non root users to access root mounted filesystems
2) Install go_mtpfs
3) Configure udev rules to mount and unmount Android filesystems
Configuring FUSE:
Ubuntu doens't allow normal users to access fuse configuration file. This is a bug, which is quite easy to correct by giving read attribute to /etc/fuse.conf.
By default, fuse does not allow mounted filesystems to be accessed by anybody else that the user who has mounted it. As MTP filesystem will be mounted by root to be used by any user, we need to modify fuse default behaviour to allow it. This is configured by uncommenting the user_allow_other key in /etc/fuse.conf.
Code:
# sudo chmod a+r /etc/fuse.conf
# sudo gedit /etc/fuse.conf
Code:
/etc/fuse.conf
...
# Allow non-root users to specify the 'allow_other' or 'allow_root' mount options.
user_allow_other
Install go-mtpfs:
There are various programs to add support for mtp to Ubuntu. After trying a number of them I have found go-mtpfs works best for me. You certainly could install a different program and just adjust the guide to suit. Go-mtpfs is available in the WebUpd8 Unstable PPA, for Ubuntu 13.04, 12.10 and 12.04. Add the PPA and install it using the following commands:
Code:
# sudo add-apt-repository ppa:webupd8team/unstable
# sudo apt-get update
# sudo apt-get install go-mtpfs
If you are not happy with installing prebuild binaries from repositories, you can easily get the source from github and build it yourself.
Once that is done you need to create a mount point for your Android filesystems. I have chosen TF700 under /media. This mount point should be accessible by anybody as you will later mount the device using your user account.
Code:
# sudo mkdir /media/TF700
# sudo chmod 777 /media/TF700
Add the udev rules:
This is the core of making the auto mounting work. The first link I reference has all the information on how you discover the Vendor and Product ids. While it is interesting reading, I have just skipped over all that and supplied the TF700 specific values. If you are trying to setup another device you WILL NEED TO read it and get the appropriate values, as they are device specific.
Code:
# sudo gedit /etc/udev/rules.d/51-android.rules
Code:
# Asus TF700
SUBSYSTEM=="usb", SYSFS{idVendor}=="0b05", ATTR{idProduct}=="4c91", MODE="0666" #MTP media, USB debug on
# Asus TF700 MTP mode under JB 4.2+ : automatic mount & umount when plugged (USB debug on & off)
ENV{ID_MODEL}=="ASUS_Transformer_Pad_TF700T", ENV{ID_MODEL_ID}=="4c91", ACTION=="add", RUN+="/usr/bin/sudo -b -u YOUR_LOGIN /usr/bin/go-mtpfs -allow-other=true /media/TF700"
ENV{ID_MODEL}=="ASUS_Transformer_Pad_TF700T", ENV{ID_MODEL_ID}=="4c91", ACTION=="remove", RUN+="/bin/umount /media/TF700"
You need to change "YOUR_LOGIN" to your username.
Last thing is to restart udev for the new rules to become operationnal.
Code:
# sudo service udev restart
Declaration in /etc/fstab:
At this stage, you are able to automatically mount and unmount your TF700. Your device should appear after few seconds in Nautilus computer section.
You can now browse your device straight from Nautilus. You can copy files from and to your TF700, you can rename files, ...
You have to know that you will face some limitations as MTP is not a real filesystem protocol :
* you can not copy files bigger than 2 Gb,
* you can not create empty files,
* you can not move file within the phone with drag & drop
* you cannot open files in write mode directly from TF700
Another problem is that you can not unmount your TF700 straight from Nautilus. If you click on the Eject button, you will get an error message saying :
umount: /media/TF700 is not in the fstab (and you are not root)
To solve that, it has to be declared in /etc/fstab with its fuse caracteristics.
As /etc/fstab is using SPACE as a separator and as our TF700 fuse caracteristics include SPACE caracter, we have to convert them to its octal escape code \040.
Code:
# sudo gedit /etc/fstab
Code:
/etc/fstab
...
DeviceFs(ASUS\040Transf) /media/TF700 fuse.DeviceFs(ASUS\040Transf) allow_other,rw,user,noauto 0 0
When you will remount it in MTP mode, your TF700 will be seen as a device. In Nautilus, it appears in the device section and you are now able to Eject it ...
Thanks wery good info
ʞןɐʇɐdɐʇ on tf300t
with 13.04, i hear where now have native support. i installed 13.04 last night, but did not test it out. i will try it tonight.
timrock said:
with 13.04, i hear where now have native support. i installed 13.04 last night, but did not test it out. i will try it tonight.
Click to expand...
Click to collapse
Didn't work for me on my Droid Razr HD but the OPs tutorial was pretty useful.
Few questions though:
1. you can not create empty files,
2. you can not move file within the phone with drag & drop
Click to expand...
Click to collapse
1. Does this apply to folders as well?
2. What about cut and paste? I swear it worked for me.
Xplorer4x4 said:
Didn't work for me on my Droid Razr HD but the OPs tutorial was pretty useful.
Few questions though:
1. Does this apply to folders as well?
2. What about cut and paste? I swear it worked for me.
Click to expand...
Click to collapse
worked fine with my tf700, galaxy nexus, nexus 7 and my daughter samsung galaxy tab 2
As some extra help. I hate to see the device always present in Nautilus even if it's not mounted, because of fstab. So as a workaround (which is not the best way I imagine) I modified the udev rules file and the fstab file.
bjtheone said:
Code:
# sudo gedit /etc/udev/rules.d/51-android.rules
Code:
# Asus TF700 MTP mode under JB 4.2+ : automatic mount & umount when plugged (USB debug on & off)
ENV{ID_MODEL}=="ASUS_Transformer_Pad_TF700T", ENV{ID_MODEL_ID}=="4c91", ACTION=="add", RUN+="/usr/bin/sudo -b -u YOUR_LOGIN /usr/bin/go-mtpfs -allow-other=true /media/TF700"
ENV{ID_MODEL}=="ASUS_Transformer_Pad_TF700T", ENV{ID_MODEL_ID}=="4c91", ACTION=="remove", RUN+="/bin/umount /media/TF700"
Click to expand...
Click to collapse
I changed it as follows:
Code:
# Asus TF700 MTP mode under JB 4.2+ : automatic mount & umount when plugged (USB debug on & off)
ENV{ID_MODEL}=="ASUS_Transformer_Pad_TF700T", ENV{ID_MODEL_ID}=="4c91", ACTION=="add", RUN+="/path/to/mount_script.sh"
ENV{ID_MODEL}=="ASUS_Transformer_Pad_TF700T", ENV{ID_MODEL_ID}=="4c91", ACTION=="remove", RUN+="/path/to/unmount_script.sh"
The mount_script.sh contains:
Code:
#!/bin/sh
/bin/sed -i 's|#DeviceFs(ASUS\040Transf)|DeviceFs(ASUS\040Transf)|' /etc/fstab
/usr/bin/sudo -b -u YOUR_LOGIN /usr/bin/go-mtpfs -allow-other=true /media/TF700
and the unmount_script.sh:
Code:
#!/bin/sh
/bin/sed -i 's|DeviceFs(ASUS\040Transf)|#DeviceFs(ASUS\040Transf)|' /etc/fstab
/bin/umount /media/TF700
Now to make sense of the previous scripts, the fstab file has to change just a little. The extra line previously added has to be commented. That way the mount script will uncomment that line, making your device unmountable by the user and showing under the devices section, and when removed the unmount script will comment the same line so it won't show in that section any more.
Just to be sure, here's how the fstab looks (note the #[/B in front of the line)]:
Code:
/etc/fstab
...
#DeviceFs(ASUS\040Transf) /media/TF700 fuse.DeviceFs(ASUS\040Transf) allow_other,rw,user,noauto 0 0
Make sure you restart your udev so the new scripts can work, using with
Code:
# sudo service udev restart
Great tutorial but go-mtpfs is buggy
How come there are files that don't show up when I mount the go-mtpfs directory? For instance, when I navigate to SD Card/DCIM/Camera over the go-mtpfs mount,there is nothing there. if I connect to a shell over adb, I can see the files are clearly there. I thought it may be filesystem corruption however issuing adb pull of the Camera directory does indeed retrieve the correct files.
Hi guys, First post here, really looking forward to learn more about android .
I'm trying to root a generic tablet (titan pc008) using linux and ADB.
The thing is when i connect the tablet and run adb devices it doesn't get listed.
So i guess i need to install some sort of generic driver or something but i've very superficial knowledge about rooting and android tinkering in general.
I've already tried killing and restarting the adb server
The lsusb output for my device:
Code:
Bus 002 Device 004: ID 2207:0000
Added this line to the file "/etc/udev/rules.d/99-android.rules":
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="2207", ATTR{idProduct}=="0000", MODE="0666", OWNER="user"
Hi guys.
I kept on googling and finally found a was to set up adb for this device on stackoverflow by Mateus Sousa Mello
I had same problem as you, what i done: Added vendor id to ~/.android/adb_usb.ini
echo "0x2207" >>~/.android/adb_usb.ini
Added the following lines to /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="207/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="207", MODE="0666"
Now my chinese tablet Archos c906 is recognize on ./adb device as:
List of devices attached
0123456789ABCDEF device
Click to expand...
Click to collapse
I hope this might help someone in the future.