Database Develop

[Q] Can't get adb working on my One

Hello
I have done all many researches in forum, and made sure all of below are done but just can't get adb working on my device in fastboot mode...
- Installed USB driver
- Debugging mode is on
- Not using 3.0 USB port
- Using Win 7 64 bits
Fastboot is working fine but adb can't find my device at all. It shows blank list after I typed "adb devices"
Funny thing is when I boot into TWRP recovery and use the adb sideload function, adb can find my device correctly!
Anyone got a clue what's happening on my One? I really want to make adb works so I can make it s-off.
Thanks.

adb doesn't work in fastboot mode.

BenPope said:
adb doesn't work in fastboot mode.
Click to expand...
Click to collapse
Thanks and sorry for my noobiness.
I always think I need to boot into fastboot mode for adb.
:fingers-crossed:

try an custom recovery witch support adb like teawin

I use TWRP for ADB. TWRP > Advanced > ADB Sideload.

windows 10 and adb problem

OK, just got my nexus 6 yesterday, and said goodbye to Samsung..
first, plugged my phone into my windows 10 machine, and it instantly showed up in windows explorer, and was able to see all the directories on my phone, so that was good.
I then followed the instructions for installing the ADB/Fastboot installation stuff from here,
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Opened the command prompt, typed in these commands, cd Desktop/android-sdk-windows/platform-tools
adb version, and adb version showed up just fine.
Turned off my phone, held down volume and power and entered fastboot mode, but after typing the proper commands, my phone serial number doesnt show up..
I have enabled developer mode, turned on USB debugging, enabled OEM unlock, but still no serial number shows up.
I'm not a rookie, and understand how to use ADB, but I am afraid that windows 10 is the issue..
Anyone have any suggestions?
Thanks for your input:good:
Mod Edit:
Solution found and thread closed at OPs request

You can't use adb in fastboot mode. You can only use fastboot in fastboot mode. Adb only works in android or recovery

thanks, I got it sorted out by installing this..
http://forum.xda-developers.com/showthread.php?t=2588979

ADB won't see my BLU R1 HD

Hi. I've been trying for hours to get Helium backup to work with my R1 and it won't work. My G4 works fine with the same USB port and cable. When my G4 is plugged in, if I type adb devices, it shows up. The BLU phone does not show up. I've tried uninstalling and installing Helium in my computer and in the phone. I did a hard reset on the phone. I downloaded and installed the drivers Helium recommends and nothing. I simply can't make the R1 work. I've noticed a few people having the same problem in other forums but I haven't found a fix for it.
Anyone can give me some ideas? Thanks.

Did you enable usb debugging. Not calling you an android dummy but we have all forgot to enable usb debugging one time or uhnutha.

Yeah, I enabled it.

Another day trying to get adb to see my phone and nothing. I installed mtk drivers, etc and I'm still getting a blank when typing "adb devices"...

Are you using the cable from Blu? I noticed that my other devices work fine with any cable, but the R1 only seems to respond with the Blu provided USB cable.

Yeah, I started using the BLU cable just in case and it didn't make a difference.
Sent from my VS986 using Tapatalk

My phone recognizes ADB perfectly in TWRP but I cannot get adb to work with the system up.
Not a cable or adb drivers.

king200 said:
My phone recognizes ADB perfectly in TWRP but I cannot get adb to work with the system up.
Not a cable or adb drivers.
Click to expand...
Click to collapse
Don't be so sure it's not driver, because while in recovery and while in system the phone reports different mode to PC, so could be using different driver

Try going into device manager in Windows and updating the driver. Select choose from available drivers, and if there's one that's different than what is currently loaded, try that one.
Sent from my BLU R1 HD using Tapatalk

Vendor ID issue, you need to update the adb_usb.ini to include it.

I got adb to see my R1 under Windows. When you plug it in, change from MTP mode to PTP mode and unplug it, then plug back in. It works in PTP mode but not MTP mode for some odd reason.

Synir said:
Vendor ID issue, you need to update the adb_usb.ini to include it.
Click to expand...
Click to collapse
What is the proper vendor entry. What is your entries. Currently I have:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
0x12D1

king200 said:
What is the proper vendor entry. What is your entries. Currently I have:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
0x12D1
Click to expand...
Click to collapse
did it work?

Has anyone solved this issue yet?

i cant seem to figure out how to get adb to work with this phone. need help im on 6.6 and no step by step instructions on how to either roll back or just install a new rom.

pookeye said:
i cant seem to figure out how to get adb to work with this phone. need help im on 6.6 and no step by step instructions on how to either roll back or just install a new rom.
Click to expand...
Click to collapse
ADB just "works" for so many users, It leaves the dumb question . Did you enable developer options and turn adb debugging?
Also what abd are you using?
Easiest thing to do would be reinstall adb + fastboot with 15 second install.
link to that is in the unlock tool thread. Which will also answer your question what is needed to install new / other rom.
(tool unlocks bootloader, flash twrp, can install superSU,)

HELP with adb and fastboot (fixed)

man, i am losing my mind over this now. i have no idea why my phone seems like it isn't recognized in adb fastboot. however, when i am not in fastboot it shows just fine.
before i go into fastboot mode on the phone i can use command prompt and it shows
>adb devices
List of devices attached
d858f4c6 device
i can even command the phone to go into fastboot
adb reboot bootloader - and my phone goes into fastboot
then when in fastboot:
i type fastboot devices - nothing listed
adb devices - nothing listed
what am i doing wrong here? everything seems to be fine before going into fastboot but once i am in fastboot none of the same commands work the device isn't recognized
yes, of course i have usb debugging turned on.
any ideas? i've been messing with this going on two hours now uninstalling my files and reinstalling them.
EDIT - ok it took me like 3 hours but the device needs different drivers when in fastboot but you can only fix it while its in fastboot on my machine for some reason

You can't use adb commands when in fastboot mode and vice versa.

knives of ice said:
man, i am losing my mind over this now. i have no idea why my phone seems like it isn't recognized in adb fastboot. however, when i am not in fastboot it shows just fine.
before i go into fastboot mode on the phone i can use command prompt and it shows
>adb devices
List of devices attached
d858f4c6 device
i can even command the phone to go into fastboot
adb reboot bootloader - and my phone goes into fastboot
then when in fastboot:
i type fastboot devices - nothing listed
adb devices - nothing listed
what am i doing wrong here? everything seems to be fine before going into fastboot but once i am in fastboot none of the same commands work the device isn't recognized
yes, of course i have usb debugging turned on.
any ideas? i've been messing with this going on two hours now uninstalling my files and reinstalling them.
EDIT - ok it took me like 3 hours but the device needs different drivers when in fastboot but you can only fix it while its in fastboot on my machine for some reason
Click to expand...
Click to collapse
I have same problems. Please explain how you have solved. Which drivers the Mi Mix needs in fast boot mode?

basically, you have to watch your device manager for the ANDROID to pop up and it should have a yellow exclamation. you have to fix the drivers, but the problem is at least in my case you have to complete and fix the drivers before the mix puts itselt out of fastboot and into charging (which it does quite quickly when not connected)
install this:
http://forum.xda-developers.com/showthread.php?t=2588979
and follow the guide that he posts in the pictures on what you need to change
here
http://forum.xda-developers.com/attachment.php?attachmentid=2480396&d=1388281089
as soon as you have the drivers fixed windows will tell you and the mix will stay connected

OnePlus3t bricked can only boot into fastboot, however my ADB driver no longer works

I have ran into a bit of an odd problem due to me messing up a root and then messing my phone up even more while trying to fix it.
my phone is fully bricked and only boots into fastboot mode. i tried to fix it with the one-plus fixer (idk its official name) but i got an error 7. I now need to re flash an older version of TWRP and try a diffrent method but i cant as my phone no longer is recognized in fastboot using the ADB tool. I have the USB driver installed on Windows. On Linux i ran the .sh script as root and it still doesn't work.
I have both Ubuntu and Windows installed on my PC so i can do whatever you suggest me to do regardless of the os.
Thank you to anyone that can help in advanced
Malte

This is not a hardbrick; a hard one wouldn't boot at all and give no sign of life (except when plugged to PC).
Try an unbrick tool to revert to official OOS. On Windows 7+ remember to disable signed driver enforcement.

You mention fastboot and adb. Which one are you using?
Just to make sure: While in the bootloader (fastboot mode), adb does not work. You have to use the fastboot commands. Installing TWRP would be:
Code:
fastboot flash recovery <name-of-img-file>
If that's what you're already trying, just ignore this post.

I want to be able to do that but if i do adb devices it no longer finds my phone
Didgeridoohan said:
You mention fastboot and adb. Which one are you using?
Just to make sure: While in the bootloader (fastboot mode), adb does not work. You have to use the fastboot commands. Installing TWRP would be:
Code:
fastboot flash recovery <name-of-img-file>
If that's what you're already trying, just ignore this post.
Click to expand...
Click to collapse
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command

Ive done this but it didnt fix my phone.
przemcio510 said:
This is not a hardbrick; a hard one wouldn't boot at all and give no sign of life (except when plugged to PC).
Try an unbrick tool to revert to official OOS. On Windows 7+ remember to disable signed driver enforcement.
Click to expand...
Click to collapse
I did this last night but it never fixed my phone. it boots and then says "md5 checksum error" so im needing to try a diffrent approach but i cant because i cant flash anything onto it due to adb not finding my device now

Bandella said:
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command
Click to expand...
Click to collapse
Like I said, the adb commands won't work while in the booloader (that's why it's called fastboot mode). You need to use fastboot commands... The equivalent command would be:
Code:
fastboot devices

Bandella said:
I did this last night but it never fixed my phone. it boots and then says "md5 checksum error" so im needing to try a diffrent approach but i cant because i cant flash anything onto it due to adb not finding my device now
Click to expand...
Click to collapse
I had the same issues with md5, all you have to do is try a different USB port. I suggest the ones on your motherboard if you're on a PC. Then run the tool as administrator. I hope this helps, good luck!
P.S if it still doesn't work, try a different PC, I'm 100% sure it'll work

Bandella said:
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command
Click to expand...
Click to collapse
As Didgeridoohan touched upon, adb and fastboot (while related) are different. They have different requirements and applications.
adb won't work while the device is in fastboot mode. Conversely, when the device is able to use adb, fastboot commands won't work.
adb: only works booted to OS or alternately in TWRP. Debugging must be enabled
fastboot: only works in bootloader-fastboot mode. Debugging is not required to be enabled.
For flashing TWRP, it's fastboot that you need. Well, there is a way to do it with adb, but fastboot is by far the more common way.
When in fastboot mode, adb command won't work, and there fore it is completely expected that "adb devices" yields not response. Try "fastboot devices" (no quotes) and if you get the phone's ID in response, you are in business.

Bandella said:
...
my phone ... only boots into fastboot mode...
Click to expand...
Click to collapse
I've had this happen to me when I've triggered dm-verity. Instead of getting the dm-verity warning display the phone would simply boot straight back to fastboot.
My solution was to:
- flash the latest TWRP using
Code:
fastboot flash recovery <recovery file. img>
- reboot into recovery (use the volume keys on the phone to select recovery and then press the power key)
-flash the full stock image I was using before the problem started
This would clean up any changes made to the boot and system images and allow me to boot the system normally.
Note: because this leaves you with a stock kernel you'll end up with the stock recovery after you boot the system.
Sent from my OnePlus3T using XDA Labs

boot your PC into Ubuntu and install adb/fastboot (tons of guides available off the 'net). then boot your 3t to dl mode and connect it to your PC. as mentioned already "fastboot devices" should list your 3t and you should now be able to flash to your heart's content. no need for drivers, unlike under Windows. i have a bootable linux usb drive primarily for this reason. curious what script you're trying to run though..