Hi All
i have a problem on Ubuntu 12.04 with the adb .
My device is simply not detected by adb. ( there are no devices in the device list.
I have updated the udev rules many times , and it seems to me that the device itself is detected by the system.
I wiould need any help with that problem , which makes me slowly really mad.
Thank you for your help
BR
sz_gergo
Hi,
The problem got solved for me when I started adb server as root process.
Open a terminal and go to android-sdk-linux_x86/platform-tools or wherever adb resides, and type
Code:
adb kill-server
sudo ./adb start-server
Now hopefully when you type adb-devices, adb-server will recognize your device provided the udev-rules are correct.
All the best !
craterib said:
Hi,
The problem got solved for me when I started adb server as root process.
Open a terminal and go to android-sdk-linux_x86/platform-tools or wherever adb resides, and type
Code:
adb kill-server
sudo ./adb start-server
Now hopefully when you type adb-devices, adb-server will recognize your device provided the udev-rules are correct.
All the best !
Click to expand...
Click to collapse
Hi craterib !!
Firstly thanks for your answere.
I will try your sollution when i arrive at home, today.
I will provide you the results. Could you paste your udev rules ??
Just for the case that mine are not the best ones
THX
Gergo
sz_gergo said:
Hi craterib !!
Firstly thanks for your answere.
I will try your sollution when i arrive at home, today.
I will provide you the results. Could you paste your udev rules ??
Just for the case that mine are not the best ones
THX
Gergo
Click to expand...
Click to collapse
Code:
[email protected]:/etc/udev/rules.d$ more 51-android.rules
# Sony Ericsson Mobile Communications AB
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", ATTR{idProduct}=="6168", MODE="0600", OWNER="kuisma"
Using this, you don't have to run the adb server as root. Use the "lsusb" to get Vendor and Product id for your device.
Also, change "kuisma" to your user, of course, unless toy happen to be me.
Restart udev (/etc/init.d/udev restart) once you've edited this.
sz_gergo said:
Hi All
i have a problem on Ubuntu 12.04 with the adb .
My device is simply not detected by adb. ( there are no devices in the device list.
I have updated the udev rules many times , and it seems to me that the device itself is detected by the system.
I wiould need any help with that problem , which makes me slowly really mad.
Thank you for your help
BR
sz_gergo
Click to expand...
Click to collapse
To get your newly build Apps down to your device you have to use the ADB (Android Debug Bridge). The common way to make your device ready for playing is to download the USB driver package which is included in the SDK Manager.
But these drivers are only for a couple of common mobile devices, so what if you have an ARCHOS 8 like me…. You will still get stuck with a nice…. device not found ….
The first part is easy, Archos in my case, offers his own usb drivers .
After downloading the USB driver I got a shiny “Archos 7 ADB” item under “Android Phone” in my windows device manager. But what is this,…. after restarting the ADB daemon,…. “ADB devices” was only showing an annoying message… “device not found….” Gees.
Hmm, Google is your best friend …… The solution is that the ADB daemon needs also your USB device vendor ID (VID)
If you cannot get it from your device vendor you may look under device manager -> device details -> hardware ID -> USB\VID_xxxx.
The VID for the adb should be placed in a file under {user home}/.android/adb_usb.ini.
Insert the VID in HEX notation {0x0e79}
If this file does not exist, just create it!
bronzext said:
To get your newly build Apps down to your device you have to use the ADB (Android Debug Bridge). The common way to make your device ready for playing is to download the USB driver package which is included in the SDK Manager.
But these drivers are only for a couple of common mobile devices, so what if you have an ARCHOS 8 like me…. You will still get stuck with a nice…. device not found ….
The first part is easy, Archos in my case, offers his own usb drivers .
After downloading the USB driver I got a shiny “Archos 7 ADB” item under “Android Phone” in my windows device manager. But what is this,…. after restarting the ADB daemon,…. “ADB devices” was only showing an annoying message… “device not found….” Gees.
Hmm, Google is your best friend …… The solution is that the ADB daemon needs also your USB device vendor ID (VID)
If you cannot get it from your device vendor you may look under device manager -> device details -> hardware ID -> USB\VID_xxxx.
The VID for the adb should be placed in a file under {user home}/.android/adb_usb.ini.
Insert the VID in HEX notation {0x0e79}
If this file does not exist, just create it!
Click to expand...
Click to collapse
Dear all suddenly it is solved !!!!!!
Well the sollution was for me to insert the Vendor Id of my box into the $HOME/.android/abd_usb.ini in the hex notation.
After that i have killed the server and restarted it as a normal user.
It is working fine now and the device is shown by the adb devices
Thank you for your help
BR
Gergo
I did not see anybody here mention Knives-And-Forks Tools which is easiest way to Install adb and Fastboot on multiplatform computer. I did it and works like a charm
sz_gergo said:
Dear all suddenly it is solved !!!!!!
Well the sollution was for me to insert the Vendor Id of my box into the $HOME/.android/abd_usb.ini in the hex notation.
After that i have killed the server and restarted it as a normal user.
It is working fine now and the device is shown by the adb devices
Thank you for your help
BR
Gergo
Click to expand...
Click to collapse
hello i have question how to insert vid in hex notation...
digitized007 said:
hello i have question how to insert vid in hex notation...
Click to expand...
Click to collapse
Well therefor you will need an editor. I have used vi , but it is possible to use any editor.
2. step open the file in the editor
3. in a terminal window type " lsusb -v " that will give you the information of all the usb devices
look for the line beginning with idVendor of your device
for me it looks like: " idVendor 0x12d1 Huawei Technologies Co., Ltd."
4. copy the hexcode: 0x12d1 (yours may be another number) into the file
5. save the file
6. restart the server
only that number is needed nothing else
for every device you will get such a code , and each device code should came into a separate line
Hope that helps
br
sz_gergo
Related
*****To all newebies(as quite a few new people are at this forum because they got their first device! (TFP)) any anyone who wants to learn, let’s get educated about our devices!*****
ADB (Android Debug Bridge) is an extremely useful tool that WILL help you in all of your customizing needs! You may see the need to use ADB commands to help root your device, change ROMS, or send your device a fix. Without the knowledge here, you could easily be left in the dark.
ADB is a necessity for developers and general consumers alike. Knowing this tool is a great advantage to you to help your device at the best quality possible.
Installation
Download Google SDK
Choose the correct operating system and install!
The installation REQUIRES Java JDK which can be downloaded from Here
If during installation it asks for JDK (and you have installed it) Press the back button and next again, sometimes that will fix the error.
**Note** The SDK installs to C:\Program Files (x86)\Android\android-sdk standard, chose any directory for you
Start the SDK and immediately, you will notice a few checkboxes. For the standard user, just make sure Android SDK Platform-tools (under Tools) and Google USB Driver package (under Extras) – the drivers are always good to have, latest ADB drviers.
Click install 2 packages and wait. Once installed go to your installation directory and find the platform-tools folder. This directory is your ADB and will be your lifeline!
**Do you want ADB accessible through any command prompt directory?**
You are in luck. (For Windows 7)
Right click on My Computer > Properties > Advanced System Settings >Advanced (Tab) > Environment Variables > Under System Variables scroll and dbl click on Path
TO THE END of the Variable value line add
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools
Or whatever the directory you installed to + platform-tools
Open CMD and type ADB, if you did it right, you will see proper ADB jargon regardless if you are in the correct directory or not!
Congratulations! ADB is installed!
**Make sure your device is using the latest drivers (that you just downloaded) or other ADB drivers provided by ASUS to access ADB. When connected in Debugging mode, device manager will have: ASUS Android Composite ADB Interface**
ADB Usage
**I will be talking mainly about commands/arguments that the general end-user may use or come across**
**Make sure your tablet is in USB Debugging Mode to be able to connect to ADB (Settings > Applications)**
ADB Devices : This command shows all connected android devices that will respond to an ADB command. It is useful for making sure your device is connected.
ADB Connect [IPORT] : This command will connect to your device over personal WIFI connection if your device is setup for ADB over WIFI (Requires root and NOT recommended)
ADB Push [local_file] [remote_file] : This command will push any local file to the device (only if the device is Read/Writable. Stock /system/ folders are only Readable.
ADB Pull [Remote_file or Directory] [Save file or Directory] : This command take files or an entire directory and save it to your desired location. This command only works when directory is read/Writable.
ADB Shell [command] : This command will perform most UNIX commands on the device. Without a command, you can enter several shell commands before you ‘exit’. Most will not work unless SU is applied (# instead of $). Must be rooted for SU. Only play with these commands if they are known by you or exactly copied from instructions.
ADB Logcat [ > file.txt ] : This command will display (or save per > file.txt) a log of what’s happening on the device. If you are receiving errors, turn on logcat, reproduce error, turn off, and send logcat to the developer.
ADB Install [-r][-s] [local_apk] : This command force installs (or reinstalls –r or –s installs on SD-Card) any APK provided.
ADB Uninstall [-k] [APK_Name] : This command uninstalls any APK Name provided (app.apk) and will even keep cache and other data with the –k tag.
ADB start-server : This command will start the server if the server is off or killed. (Normally server will auto-start when ADB command is used)
ADB kill-server : This command will close ADB server. Useful if ADB server is acting up or not connecting to any devices.
ADB remount : This command will mounts the /system/ partition Read/Writable pending the device is allow to. Stock TFP will NOT.
ADB root : This command will restart ADB with root permissions if the build allows for it. Stock TFP will NOT.
ADB usb : This command will restart ADB on device to use USB connection for ADB communication.
ADB tcpip [port] : This command will restart ADB on device to use TCPIP connection for ADB. Standard port is 5555. Again, this connect not recommended for file transfers.
ADB reboot [recovery/bootloader] : This command will restart your device. If either of the two options are given, the device will boot into that mode (sadly TFP does not support the two options.. yet)
ADB Tips/Tricks
When following ADB instructions, follow them WORD-BY-WORD in the EXACT ORDER GIVEN. If copy and pasting their commands (one line at a time) makes it easier, then do so.
If you have root access, do not mess around in ADB shell unless you know what you are doing
Connecting over IP can be beneficial for you for quick ADB access, but for file transfers, speed is slow and you ALWAYS risk corruption (check the md5!) One bad file and you have boot-loops!
ADB Logcat is an amazing command. If anything is wrong with your device, 9/10 you can see it in logcat. If you can find the exact problem, fixes can happen much easier. USE LOGCAT TO YOUR ADVANTAGE!
ADB reboot can be a quick reboot, sometimes you don’t feel like waiting!
Use the environmental variables! It helps exponentially, and keeps from having multiple instances of ADB running.
When multiple instances of ADB are running (different directories) ADB can get messed up! (ADB not up-to-date restarts, and connect problems). ASUS Sync service has and ADB setup. Turn it off if you are not using it. Try to stick to only ONE instance of ADB
Eventually, we may have root access in our recovery kernel. Then and only then can our devices be truly customizable!
The GUIDE is not finite. Please post anything you feel should be added/corrected to the guide. Please take notice from this, as the understanding of these simple commands could help save your device(s)!
Thanks and 5 star would make me feel good inside too!
Wow... Nice post. Lots of time went into this lol. Thanks can't give the five stars in the app though:-(
Sent from my Transformer Prime TF201 using xda premium
The link in step #1 is whack - I think you want tis? http://developer.android.com/sdk/index.html
Lock-N-Load said:
The link in step #1 is whack - I think you want tis? http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
hmm thats what was in there, i re-saved and it works now ... maybe xda error
thanks tho!
biggem001 said:
hmm thats what was in there, i re-saved and it works now ... maybe xda error
thanks tho!
Click to expand...
Click to collapse
before you fixed it, it was trying to use this http://http://developer.android.com/sdk/index.html"
note the extra parens at the end and the double http call
i noticed that too, all i did was re-save and it worked. how weird.
Thanks! I've seen a few tutorials on this but this one was by far the easiest to follow and best organized. Short and sweet. Worked on my desktop great, I've never managed to install it right D:
Re posting to give 5 stars. Thanks again OP
Quick question: Is it normal for PTP mode to be required for adb to work? Because as soon as I switch to MTP I can no longer use adb.
cmat1120 said:
Quick question: Is it normal for PTP mode to be required for adb to work? Because as soon as I switch to MTP I can no longer use adb.
Click to expand...
Click to collapse
i can do either at once.. thats weird
GPS, Wifi and BT Testing
Could someone write some basic tutorials on how to verify/test GPS, wifi and BT funtions? For those of us who are new to Android it would helpful in verifying which problems are truly present. Also perhaps show how to find the serial number - for example: some don't know you have to click status - because there are a some erroneous posts out there. There may be users who assume something works or doesn't work, based on limited knowledge and these inaccurate findings only serve to muddy up the works.
There's a lot of animosity about the influx of newbies (and trust me, as a newbie it doesn't feel good). I think the first step is to educate. If some of these troubleshooting steps are laid out, more people can contribute in an intelligent way.
I thought this would be a good thread for the Guides thread, but it is closed and I cannot send PMs.
Thanks - Great Info
One thing you can add for all us amateurs is how to use ADB to install off market apps, stuff like that. Things the non-power user can benefit from. Some simple command line structure would be great.
theandies said:
One thing you can add for all us amateurs is how to use ADB to install off market apps, stuff like that. Things the non-power user can benefit from. Some simple command line structure would be great.
Click to expand...
Click to collapse
i wont add it to the guide, because adb install is pretty self explanatory but this
make sure you can install non-market apps
Code:
adb install app.apk
jonalisa said:
Could someone write some basic tutorials on how to verify/test GPS, wifi and BT funtions? For those of us who are new to Android it would helpful in verifying which problems are truly present. Also perhaps show how to find the serial number - for example: some don't know you have to click status - because there are a some erroneous posts out there. There may be users who assume something works or doesn't work, based on limited knowledge and these inaccurate findings only serve to muddy up the works.
There's a lot of animosity about the influx of newbies (and trust me, as a newbie it doesn't feel good). I think the first step is to educate. If some of these troubleshooting steps are laid out, more people can contribute in an intelligent way.
I thought this would be a good thread for the Guides thread, but it is closed and I cannot send PMs.
Click to expand...
Click to collapse
for GPS, use GPS Test app on the market
for BT and wifi testing, i'll just connect my device via BT or adhoc wifi and do the testing on my PC itself, more accurate and better programs
Excellent howto, thanks
I have trouble connecting to my prime with adb. In the Win7 Device Manager the correct device shows up, no exclamation mark at all, but adb just won't see the Prime.
USB debugging mode is on, no Asus Sync software on the PC. I have no clue why ADB won't see my device.
Now many of us can really shoot ourself in the foot.
by far the best and quickest adb install/setup ever. thanks OP!
neo1738 said:
by far the best and quickest adb install/setup ever. thanks OP!
Click to expand...
Click to collapse
aw shucks!
THANKS!
biggem001 said:
ADB Devices : This command shows all connected android devices that will respond to an ADB command. It is useful for making sure your device is connected.
ADB Connect [IPORT] : This command will connect to your device over personal WIFI connection if your device is setup for ADB over WIFI (Requires root and NOT recommended)
ADB Push [local_file] [remote_file] : This command will push any local file to the device (only if the device is Read/Writable. Stock /system/ folders are only Readable.
ADB Pull [Remote_file or Directory] [Save file or Directory] : This command take files or an entire directory and save it to your desired location. This command only works when directory is read/Writable.
ADB Shell [command] : This command will perform most UNIX commands on the device. Without a command, you can enter several shell commands before you ‘exit’. Most will not work unless SU is applied (# instead of $). Must be rooted for SU. Only play with these commands if they are known by you or exactly copied from instructions.
ADB Logcat [ > file.txt ] : This command will display (or save per > file.txt) a log of what’s happening on the device. If you are receiving errors, turn on logcat, reproduce error, turn off, and send logcat to the developer.
ADB Install [-r][-s] [local_apk] : This command force installs (or reinstalls –r or –s installs on SD-Card) any APK provided.
ADB Uninstall [-k] [APK_Name] : This command uninstalls any APK Name provided (app.apk) and will even keep cache and other data with the –k tag.
Click to expand...
Click to collapse
Just a small suggestion, adb won't accept commands if they are capitalized.
For example "ADB devices" will work perfectly, but "ADB Devices" won't.
So, in order to help the newest of newbies, you might want to put the commands in lowercase in the first post.
Ok, I'm just going to ask it...
How do I set up SDK and ADB on my 3rd generation HDX 8.9. I find quite a few sets of instructions from 2011 but nothing seems up to date. And android studio is installing the driver in amazon.com which seems weird.
This is the latest I tried--here
I've searched and searched--I've tried several of these with no luck getting the pc to recognize the kindle.
Please no hateful replies--I've been at this for 2 days and I or really wouldn't ask.
Links would be really useful.
Thank you
Unless you are developing, you do not need android studio, jdk, or anything else. All you need to to do is download the sdk.
From here I am going to assume you are on Windows. Probably win 8 or 8.1?
Extract the sdk to a folder where you have write access.
Now find the folder called platform-tools in the sdk folder.
Now, in the Windows explorer bar, select all the text and type cmd
If you do this right, it will open a command window in the platform- tools folder.
If that is confusing, you can go to the sdk folder and then open the command prompt from the start window. Then type cd and drag the platform-tools folder to the command window.
Right now, all the devs are crying, because these are lazy shortcuts, but they work and save you from adding this folder to your path which is better programmatically, but a bit more involved.
Anyway, now you are where you need to be so, type
Code:
adb devices
And you should see your device, but, you probably won't. Stay tuned...
Sent from my KFTHWI using Tapatalk
You don't need to install the whole Android Studio suite — just the SDK Tools will suffice.
As for the Kindle Fire drivers...
https://developer.amazon.com/appsan...ing-up-the-ADB-Driver-for-Kindle-Fire-Devices
So, hopefully you got either a printout of your device, or you got a blank line like...
Code:
List of devices attached...
This is because you do not have the driver installed. If you get another error, either you are in the wrong folder, or you did not enable and on your device.
Code:
To enable adb on your device, click on the serial number in settings>device options 5 times and it will give you the developer options. Enable adb is a toggle there.
Alright, now we need the driver. Go to device manager in your computer and delete anything that looks android or kindle in nature. Unhook your tablet and reboot.
Download the HDX toolkit from the developers error forum and try the install drivers tool in it.
Reboot.
Now, making sure you have enabled adb on your device, open up a command prompt in platform-tools, and try the command again.
Code:
Adb devices
You should see your serial number.
If you have any issues, report back. I may have skipped a step or two as I am giving these directions from memory.
Good luck.
~Leko
Whew! Thank you! Doing this now.
Will update
Did I say thank you?!!!!
Update...After extracting the sdk zip file, platform tools is not showing up.
Downloading the installer file now...
Update2...found platform tools
Oh, my bad, I'm on windows 7...
Update--
The kindle died..thanks for all the input! Greatly appreciated:good:
lekofraggle said:
So, hopefully you got either a printout of your device, or you got a blank line like...
Code:
List of devices attached...
This is because you do not have the driver installed. If you get another error, either you are in the wrong folder, or you did not enable and on your device.
Code:
To enable adb on your device, click on the serial number in settings>device options 5 times and it will give you the developer options. Enable adb is a toggle there.
Alright, now we need the driver. Go to device manager in your computer and delete anything that looks android or kindle in nature. Unhook your tablet and reboot.
Download the HDX toolkit from the developers error forum and try the install drivers tool in it.
Reboot.
Now, making sure you have enabled adb on your device, open up a command prompt in platform-tools, and try the command again.
Code:
Adb devices
You should see your serial number.
If you have any issues, report back. I may have skipped a step or two as I am giving these directions from memory.
Good luck.
~Leko
Click to expand...
Click to collapse
So I am stuck adb devices--the line is blank
--ADB is enabled
--USB debugging is checked
--kindle driver installed
--portable device deleted in device manager
--SDK is set up C:\Program Files (x86)\Android\android-sdk\platform-tools
The driver installed in a separate file in program files as amazon.com which looks odd to me.
Maybe my path is wrong?
Update I've tried the method found here but after 2 tries with reboots, I'm still getting MTP device and portable device->fire. Each time i see the last one I delete it, reboot plug in again and portable device appears.
I've also tried Amazon instructions here
Anyone have any ideas?
Thanks in advance!
It sounds like you are on the right track.
Unplug your kindle, delete the devices again, and try this file.
http://forum.xda-developers.com/showthread.php?t=2665683
Use it just to install the drivers. (That is all it can do for you).
Then open a command prompt.
And plug your device in.
.
If the drivers are installed correctly, the path only matters to get adb to work (which the blank line tells you it is).
Also, there is a chance the devices will show up the same after the correct drivers are used. Mtp is able to run aside adb, but on Win 8 anyway, not fastboot (don't worry about fastboot).
Hi People !!!
I had my OP2 showing in fastboot but not being able to show in adb devices though other devices were showing correctly there.So,drivers were perfect.Also,I was able to use adb over wifi on my OnePlus 2 but not adb through cable.So,I set up on my mission to get it show.And after 10 hrs of a lot hassle,I am successful.
So,here is the guide.
Open windows command prompt (Windows Key + R)
Ènter: %HOMEPATH%\.android
and then press OK
This will open the hidden .android folder within Home Folder of the current user.
There you will see a file called: adb_usb.ini
Edit the file using Notepad or Editplus/Notepad+
Just add the text: 0x2A70
without pressing any additional enter key/new line characters, save the file
now go to command prompt and restart adb:
adb kill-server
adb devices
Now the device will start showing up!
If you don't see any adb_usb.ini file (This happened for me.) , do this :-
Click the Start menu. ...
Type "folder options" (without the quotes). ...
A dialog box with the title "Folder Options" will appear. ...
Click to uncheck the box for "Hide extensions for known file types".
Click the "OK" button at the bottom of the dialog box.
In the .android folder ,create a notepad file with name adb_usb.ini (Make sure .ini is not in the name but in the extension.)
In the notepad file , enter this :-
Code:
# add your vendor IDs, one per line
0x1949
0x18D1
0x2A70
8.) Save the file and close it...ANd follow the remaining steps.
I will be thankful to you a lot..
i have tried all the possible methods to connect via adb if this works..
ssly it will be awesome
Sent from my ONE A2003 using Tapatalk
Zeuscluts said:
I will be thankful to you a lot..
i have tried all the possible methods to connect via adb if this works..
ssly it will be awesome
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Welcome. If you still have any issues connecting to adb, grant me Teamviewer access and I will help you out.
Sent from my ONE A2003 using Tapatalk
Naman Bhalla said:
Welcome. If you still have any issues connecting to adb, grant me Teamviewer access and I will help you out.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
yes sure,
can we chat on hangouts
you can contact me on
[email protected]
Sent from my OP5.
I had the same problem! Will surely try! Thanks
Keep up the great work Naman..!!
Did somebody got this to work on Linux? Probably you need to adjust udev rules there to get it to work. Will try out today and let you know how it goes.
dansou901 said:
Did somebody got this to work on Linux? Probably you need to adjust udev rules there to get it to work. Will try out today and let you know how it goes.
Click to expand...
Click to collapse
You need to add a udev*rules file that contains a USB configuration. In the rules file, each device manufacturer is identified by a unique vendor ID, as specified by the ATTR{idVendor} property. To set up OP2 detection on Ubuntu Linux:
Log in as root and create this file:/etc/udev/rules.d/51-android.rules.
Use this format to add OP2 vendor to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="2a70", MODE="0666", GROUP="plugdev"
Now execute:
chmod a+r /etc/udev/rules.d/51-android.rules
Done
I am 99.99 percent sure it will work.. But you should try and tell me.
Thanks.
Sent from my ONE A2003 using Tapatalk
Naman Bhalla said:
You need to add a udev*rules file that contains a USB configuration. In the rules file, each device manufacturer is identified by a unique vendor ID, as specified by the ATTR{idVendor} property. To set up OP2 detection on Ubuntu Linux:
Log in as root and create this file:/etc/udev/rules.d/51-android.rules.
Use this format to add OP2 vendor to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="2a70", MODE="0666", GROUP="plugdev"
Now execute:
chmod a+r /etc/udev/rules.d/51-android.rules
Done
I am 99.99 percent sure it will work.. But you should try and tell me.
Click to expand...
Click to collapse
Didn't fix it for me, until I found out, that there also exists a ˝/.android/adb_usb.ini file . Has the same format as the Windows file.
/M
marlow925 said:
Didn't fix it for me, until I found out, that there also exists a ˝/.android/adb_usb.ini file . Has the same format as the Windows file.
/M
Click to expand...
Click to collapse
Sorry for asking, but does this whole issue affect Oneplus two devices with original stock ROM (Oxygen OS 2.1.0), too?
Or does it just affect devices with custom firmware?
coala-lumpur said:
Sorry for asking, but does this whole issue affect Oneplus two devices with original stock ROM (Oxygen OS 2.1.0), too?
Or does it just affect devices with custom firmware?
Click to expand...
Click to collapse
Probably both. I haven't tested stock Rom though.
/M
I have the opposite problem, adb works after using your guide but fastboot just doesnt :S
alankstiyo said:
I have the opposite problem, adb works after using your guide but fastboot just doesnt :S
Click to expand...
Click to collapse
Fastboot should not be affected by CM at all, as it's in the bootloader. Did it work before you made the changes ?
Maybe worth reinstalling the fastboot packages.
/M
marlow925 said:
Fastboot should not be affected by CM at all, as it's in the bootloader. Did it work before you made the changes ?
/M
Click to expand...
Click to collapse
I had a wrong driver, cant root for the moment but havent unlocked the bootloader so think that is the problem
Well. Without unlocking the bootloader you won't get anywhere. Fastboot is a bootloader feature. You don't need root for fastboot.
/M
Sent from my SM-P905 using Tapatalk
Didn't work for me.
So found mine in my install folder
c:\android\.android\adb_usb.ini
After each change below I ran adb kill-server then adb devices.
I already have the line 0x2a70, I first changed it to 0x2A70 (just in case)
tried renaming it to adb_usb.ini.bak, to see if it would recreate, nope.
renamed the folder .android to .android.bak and it created the adbkey and adbkey.pub but not the .ini.
So looking at the .android folder, I think I learned something new tonight, I assume this is the public/private key pair store for adb to do it's work? So it truly is just a usb connection issue then if it works over network and not with the usb cable connected yes?
So I even tried re-running the '15 seconds ADB Installer' version 1.3 by Snoop05 that I used originally and still no change. Any advice appreciated.
My ADB is working but the fastboot isn't working! Thank you for your help!
Still not detecting
I tried doing your steps but its not helping. My phone enters the fastboot mode but the pc never detects it.
Can u please help me out.
---------- Post added at 07:08 PM ---------- Previous post was at 07:05 PM ----------
williamt31 said:
So found mine in my install folder
c:\android\.android\adb_usb.ini
After each change below I ran adb kill-server then adb devices.
I already have the line 0x2a70, I first changed it to 0x2A70 (just in case)
tried renaming it to adb_usb.ini.bak, to see if it would recreate, nope.
renamed the folder .android to .android.bak and it created the adbkey and adbkey.pub but not the .ini.
So looking at the .android folder, I think I learned something new tonight, I assume this is the public/private key pair store for adb to do it's work? So it truly is just a usb connection issue then if it works over network and not with the usb cable connected yes?
So I even tried re-running the '15 seconds ADB Installer' version 1.3 by Snoop05 that I used originally and still no change. Any advice appreciated.
Click to expand...
Click to collapse
Same here!!!!!
any help would be appreciated
My fix was:
turn on adb over TCP on phone in developer options.
At cmd type:
adb connect <ip.address>
adb devices (now shows device)
adb reboot bootloader
Open another cmd if you don't get your prompt back and continue
still not working
i tried all the steps and my op2 only shows when connected via wifi but that is too slow for an adb backup, it still doesnt show up when connected over usb
any ideas? or is any info needed?
Hi, I hope I am posting in the right section? I found the site really difficult to navigate having never used the site before. If its in the wrong place please can a mod move it.
Ok so I have an Android Set Top Box (STB) and I am trying to extract all the data from it. It is an mxp pro 4k. I don't want a backup of the data I want to extract full images of the device for analysing with forensic tools. The problem is I can't seem to communicate with it. I have the full SDK that is up to date, once navigated to the platform tools folder I opened a command line and typed
Code:
adb devices
after plugging in a USB cable to the OTG port. No prompts appeared on the screen to trust any connections like my iPhone does when I connect it. Adb devices returns no results. So I tried wireless adb, I typed
Code:
adb connect 192.168.x.x
and it said connected. Then when running the devices command I had the ip and port then the word device. I then get a shell by using
Code:
adb shell
Which i then elevate to root by using
Code:
su
. Then when i try an adb pull or adb backup I get a message saying error device offline.
Im new to Android so not even sure I am doing it right. I have done a lot of reading and research but seem to be stuck with the basics. To confirm USB debugging is turned on.
Hi!
I have recently bought an F1 and I can't connect it to PC (Windows or Linux). I turned Developer options on and enabled USB debugging. I tried every option in "Select USB configuration". The adb devices command always give empty list. The PCs are OK because they work with every other phones. On Windows I even tried to install USB drivers but didn't help. Could you help?
Did u give administrator rights when opening your adb programm?
Ziegenjupp said:
Did u give administrator rights when opening your adb programm?
Click to expand...
Click to collapse
I tried "sudo apt kill-server", "sudo apt start-server" and "sudo apt devices" but didn't help.
bartatamas said:
Hi!
I have recently bought an F1 and I can't connect it to PC (Windows or Linux). I turned Developer options on and enabled USB debugging. I tried every option in "Select USB configuration". The adb devices command always give empty list. The PCs are OK because they work with every other phones. On Windows I even tried to install USB drivers but didn't help. Could you help?
Click to expand...
Click to collapse
Once you enable Usb debugging in phone. Restart the phone and connect to pc. A pop up appears to Authorize the pc. Once done you can check the ADB list. It will be displayed only after you add the pc to the trusted device in the pop up.
Hope this helps. Thanks
sssyraj
sssyraj said:
Once you enable Usb debugging in phone. Restart the phone and connect to pc. A pop up appears to Authorize the pc. Once done you can check the ADB list. It will be displayed only after you add the pc to the trusted device in the pop up.
Hope this helps. Thanks
sssyraj
Click to expand...
Click to collapse
I hardly believe but it worked! thanks
sssyraj said:
Once you enable Usb debugging in phone. Restart the phone and connect to pc. A pop up appears to Authorize the pc. Once done you can check the ADB list. It will be displayed only after you add the pc to the trusted device in the pop up.
Hope this helps. Thanks
sssyraj
Click to expand...
Click to collapse
I can now see my device and transfer files, but for some reason, I `sudo adb devices` still doesn't see my phone.
bartatamas said:
Hi!
I have recently bought an F1 and I can't connect it to PC (Windows or Linux). I turned Developer options on and enabled USB debugging. I tried every option in "Select USB configuration". The adb devices command always give empty list. The PCs are OK because they work with every other phones. On Windows I even tried to install USB drivers but didn't help. Could you help?
Click to expand...
Click to collapse
If u r running on windows 10, try this method to fix "adb issue" :-
Before fixing ADB not recognized error, you should confirm that Android SDK has been saved on your computer and you know its location.
Step 1: Right-click "Computer" and choose "Properties" on pop-up menu.
Step 2: Click "Advanced system settings" on the left panel in new window.
Step 3: In System Properties window, under "Advanced" tab, click "Environment Variables".
Step 4: Environment Variables is open now. You can edit or delete existing variables in list, or create new environment variables.
Under "User variables for isunshare", click "New" button to create a new variable for running ADB on computer.
Step 5: Type Variable name and Variable value. Click OK.
Variable name: Path
Variable value: C:\Users\isunshare\Downloads\android-sdk_r24.4.1-windows\android-sdk-windows\platform-tools
Step 6: You would see the new variable you just created in "User variables for isunshare". Click OK at the bottom.
Step 7: Open Command Prompt and type "adb", you would see ADB detailed information.
Now you have successfully fixed error "adb" not recognized as an internal or external program or batch file.
I've the same probelm during debloating my poco f1. Solved that by using this method.
who_i_am said:
If u r running on windows 10, try this method to fix "adb issue" :-
Before fixing ADB not recognized error, you should confirm that Android SDK has been saved on your computer and you know its location.
Step 1: Right-click "Computer" and choose "Properties" on pop-up menu.
Step 2: Click "Advanced system settings" on the left panel in new window.
Step 3: In System Properties window, under "Advanced" tab, click "Environment Variables".
Step 4: Environment Variables is open now. You can edit or delete existing variables in list, or create new environment variables.
Under "User variables for isunshare", click "New" button to create a new variable for running ADB on computer.
Step 5: Type Variable name and Variable value. Click OK.
Variable name: Path
Variable value: C:\Users\isunshare\Downloads\android-sdk_r24.4.1-windows\android-sdk-windows\platform-tools
Step 6: You would see the new variable you just created in "User variables for isunshare". Click OK at the bottom.
Step 7: Open Command Prompt and type "adb", you would see ADB detailed information.
Now you have successfully fixed error "adb" not recognized as an internal or external program or batch file.
I've the same probelm during debloating my poco f1. Solved that by using this method.
Click to expand...
Click to collapse
These instructions are for systemwide installation of adb. The OP's issue is not that. The correct advice has already been given and it has worked.
sssyraj said:
Once you enable Usb debugging in phone. Restart the phone and connect to pc. A pop up appears to Authorize the pc. Once done you can check the ADB list. It will be displayed only after you add the pc to the trusted device in the pop up.
Hope this helps. Thanks
sssyraj
Click to expand...
Click to collapse
In my case I am unable to do so as my phone is completely wiped clean. Tried updating the adb interface manually everytime I try to boot fastboot boot twrp.img I get a blank slightly lit-up screen.
Also adb devices shows nothing
C:\Users\shal1018\AppData\Local\Android\Sdk\platform-tools>adb devices
List of devices attached
C:\Users\shal1018\AppData\Local\Android\Sdk\platform-tools>adb shell
adb.exe: no devices/emulators found
sssyraj said:
Once you enable Usb debugging in phone. Restart the phone and connect to pc. A pop up appears to Authorize the pc. Once done you can check the ADB list. It will be displayed only after you add the pc to the trusted device in the pop up.
Hope this helps. Thanks
sssyraj
Click to expand...
Click to collapse
In my case My Phone is not accessible as its wiped clean..what do I do?
noahshines said:
In my case I am unable to do so as my phone is completely wiped clean. Tried updating the adb interface manually everytime I try to boot fastboot boot twrp.img I get a blank slightly lit-up screen.
Also adb devices shows nothing
C:\Users\shal1018\AppData\Local\Android\Sdk\platform-tools>adb devices
List of devices attached
C:\Users\shal1018\AppData\Local\Android\Sdk\platform-tools>adb shell
adb.exe: no devices/emulators found
Click to expand...
Click to collapse
This happened to me too. Recently with 12.0.2.0 modem, I did the wipe of system and data partition along with it I tried to update the twrp to latest using old twrp. With this, even fastboot can't be reachable ie. Lighting up but no image in fastboot and phone won't respond in even miflash. I had took it to Xiaomi service center and they put the software for a nominal price of 2.5 USD in India. There after we can change to whatever firmware we like.
So, try reaching the Xiaomi service center. Thanks
sssyraj said:
This happened to me too. Recently with 12.0.2.0 modem, I did the wipe of system and data partition along with it I tried to update the twrp to latest using old twrp. With this, even fastboot can't be reachable ie. Lighting up but no image in fastboot and phone won't respond in even miflash. I had took it to Xiaomi service center and they put the software for a nominal price of 2.5 USD in India. There after we can change to whatever firmware we like.
So, try reaching the Xiaomi service center. Thanks
Click to expand...
Click to collapse
Thanks for the respose..I was thinking of doing the same!
sssyraj said:
This happened to me too. Recently with 12.0.2.0 modem, I did the wipe of system and data partition along with it I tried to update the twrp to latest using old twrp. With this, even fastboot can't be reachable ie. Lighting up but no image in fastboot and phone won't respond in even miflash. I had took it to Xiaomi service center and they put the software for a nominal price of 2.5 USD in India. There after we can change to whatever firmware we like.
So, try reaching the Xiaomi service center. Thanks
Click to expand...
Click to collapse
Xiaomi service centre said the couldn't... would you mind telling me which state in India.. did you take it to?
noahshines said:
Xiaomi service centre said the couldn't... would you mind telling me which state in India.. did you take it to?
Click to expand...
Click to collapse
I got it serviced at Chennai, Tamil Nadu. My phone shown boot logo and loops due there isn't system as I wiped it. So they took it as Software issue and have done the software update for Rs 180. Sometimes we might need to pretend as novice to leave something to Professionals. Thanks.
Cheers
sssyraj.
Same with my POCO M3. Mi PC Suite device not detected, I can't unlock it too because can't be detected. I'm tired to follow multiple methods online, reinstalling, uninstalling vise versa even disabling antivirus, and reinstalling again and again with adminisrator rights. Thank you for any help will rise in soon to easily fix these issues.