Develop Bugs

[Q] Phone not being recognized by computer in bootloader?

So I've been trying to root/unlock my CDMA nexus and I'm having a very frustrating problem that's preventing me from doing it with any of the toolkits available OR the manual method. I have the android SDK installed, samsung's USB drivers, and everything else I've been told to get. I can detect my phone when it's connected (and USB debugging is on) using adb commands but ONLY when the phone is booted as normal. If I reboot into the bootloader, my computer no longer detects it, and I can no longer act upon it via adb. This, of course, is preventing me from getting anywhere on the unlocking/root front. Anyone have any ideas? I'm fresh out.

ADB doesn't work in boot loader/fastboot. Adb only works in recovery or when Android is fully running.
You need to use fastboot commands in bootloader/fastboot.
"Fastboot devices" to see if it's detected.
Sent from my Galaxy Nexus

have you installed the hboot drivers?

As above, you have to use fastboot commands when the phone is in bootloader. Try "Fastboot devices" to see if your computer sees the phone.

Fastboot commands don't detect the phone either. Fastboot is installed, as I can get it via command prompt to show available commands and whatnot, it just does not detect a device to work on.

I am also having this exact problem when i try to install the new touch cwm beta that was just released. Its not detecting the device while in the bootloader, and when i try to fastboot flash recovery it just says <waiting for device> and does nothing.

I know this is a little late, but I figured I’d post here to help anyone else out that is having this problem. I was trying to update my Galaxy Nexus from 4.0.2 to 4.0.4 using fastboot when I ran into the problem you’re having. I did this from a Windows 7 machine, and the fix for me was as follows:
1. After booting into the bootloader and having your phone plugged into your computer, open Computer Management.
2. Under Device Manager, in Computer Management, you should see a listing for a device called “Android 1.0” and it’ll have the little yellow triangle with the exclamation point on it.
3. Right click on the Android 1.0 device and select “Update Driver Software…”
4. Click “Browse my computer for driver software”
5. Click “Let me pick from a list of device drivers on my computer”
6. If you installed the Samsung drivers for the phone, scroll down until you see a device listed as “SAMSUNG Android Phone”
7. Select it and click next
8. It should auto populate the driver information. Click next and it will install the device
9. Go back to your CMD prompt and fastboot devices should now list the phone.
Hope this helps!

Quicks man your the best!

...or use Linux #trolling
Sent from my Galaxy Nexus using xda app-developers app

[Q] adb devices: unauthorized

Hi All,
I flashed TWRP to my sm-t320 with Odin in Windows. `adb devices' (in both Windows & Linux) can recognize my device but it always show unauthorized. Does anybody know how to fix that? but it's ok when I'm in twrp (turn off the tablet, then power+volume up to go to twrp: I didn't know this before, so this is for people like me), adb devices works fine.

dxxvi said:
Hi All,
I flashed TWRP to my sm-t320 with Odin in Windows. `adb devices' (in both Windows & Linux) can recognize my device but it always show unauthorized. Does anybody know how to fix that? but it's ok when I'm in twrp (turn off the tablet, then power+volume up to go to twrp: I didn't know this before, so this is for people like me), adb devices works fine.
Click to expand...
Click to collapse
Make sure you have USB Debugging enabled on your phone if you do turn it off connect your phone to your PC turn USB Debugging on and see if you get a message to allow your PC to connect to your Tab if you do then allow it.
Also check you have the correct drivers installed when connected to your PC
If you are on windows 7 right click my computer then properties and click Device Manager, look for Samsung Android Phones in the list and expand it, this should then say Samsung Android ADB Interface.
If you don’t see Samsung Android Phones your have the incorrect drivers assigned to you TAB, the one windows installs by default is generally the wrong one.
If you see Samsung Android Phones but when expanded it doesn't say Samsung Android ADB Interface then again the wrong driver is installed.
To correct it right click and select properties, then update driver, then click browse computer, then click let me select from a list Select Samsung Android ADB Interface.
When its installed you may get messages about devices not working properly just click OK to it, unplug you Tab then plug it back in again and wait for it to connect.
Open a CMD and type ADB Devices hit return and you device should be recognised,
If you are using TWRP then when you connect to your device in Recovery mode to your PC you need different drivers for that to work properly again the ones installed by windows as default are not the proper ones, it will work with the default ones but not correctly you probably will not be able to Push or Pull files or apk's.

Trouble with Fastboot

I just can't seem to get fastboot to see the phone...
I have a Z00AD2 with 2.19.40.22 software. USB Debugging is turned on. ADB sees the phone, both from my Ubuntu host system, and from a Windows 8.1 virtual machine. When I use "fastboot device" I just get "<waiting for device>" and when I run scripts/batch files (such as the one-click root) it hangs as well.
I'm assuming there's something very simple, and probably obvious, that I'm missing - but after 8hrs of messing with it yesterday, I'm a little fried.
Appreciate any thoughts!

This morning I installed a new Windows8.1 VM, installed the Intel drivers and adb/fastboot from the sticky page in the general forum. During adb/fastboot install, should I use the drivers provided if I've already installed the Intel version? I think I've tried both ways at this point... Plug the phone in, and it is recognized in adb. Fastboot displays "waiting for device".
I tried the one-click root batch file, and when running CheckBeforeAction.bat my phone restarts into fastboot mode, with the android opened-up on its back, and the batch file continues to "make sure 'asus android bootloader interface' installed on your computer successfully" (I'm not sure it is? I don't see any reference to it anywhere...).
If I proceed further I get the "if you see '123456789 ... fastboot' then you are ready to root" message - where is that supposed to display? On the phone's screen? Finally I hit a key and the batch file says it's rebooting my phone, and it gets stuck on <waiting for device>
Again, I'm sure I'm missing something simple; but I just can't figure what step(s) I'm missing.

Solved the problem, at least in terms of running fastboot on my virtual machine... I had only set up one device filter in VirtualBox, for the phone when it was in it's normal state. When in fastboot mode it uses a different driver, and thus needed a second device filter set up - once I did that, everything went smoothly as far as adb and fastboot functionality go. Having trouble now with flashing twrp...

Can't root Oneplus5T

So I want to root my new phone but my phone won't be recognized with my windows 10 laptop when doing the adb 'partnership' with phone plugged in via usb. I unlocked oem on phone as well as allow usb debugging. I'm following instructions from
a google search of rooting oneplus5t on oreo I believe its from the***********dotcom.I've never rooted a phone successfully as the last time I tried was a galaxy s7 edge in which I found out it was a clone from someone on here lol.
I looked around but can't seem to get past the part of simply entering "adb devices" in the command after installing android sdk tools. Any help,tips,pointers, advice would be much appreciated! Thanks and have a great day!

Make sure that the drivers are installed properly from the SDK. Installing the SDK is not enough. Look in device manager and look for a yellow symbol with exclamation mark next to any Android device. Right click and get to select driver and point to "Google usb driver" that you extracted from the SDK then select either bootloader or ADB driver depending on what mode your phone is in when doing the above. It should then work. Sorry if that is not clear I am doing it from memory and I am not at my computer. Good luck!

smartway4me said:
So I want to root my new phone but my phone won't be recognized with my windows 10 laptop when doing the adb 'partnership' with phone plugged in via usb. I unlocked oem on phone as well as allow usb debugging. I'm following instructions from
a google search of rooting oneplus5t on oreo I believe its from the***********dotcom.I've never rooted a phone successfully as the last time I tried was a galaxy s7 edge in which I found out it was a clone from someone on here lol.
I looked around but can't seem to get past the part of simply entering "adb devices" in the command after installing android sdk tools. Any help,tips,pointers, advice would be much appreciated! Thanks and have a great day!
Click to expand...
Click to collapse
Try "fastboot devices" instead that will tell you of it's correct or not too

smartway4me said:
So I want to root my new phone but my phone won't be recognized with my windows 10 laptop when doing the adb 'partnership' with phone plugged in via usb. I unlocked oem on phone as well as allow usb debugging. I'm following instructions from
a google search of rooting oneplus5t on oreo I believe its from the***********dotcom.I've never rooted a phone successfully as the last time I tried was a galaxy s7 edge in which I found out it was a clone from someone on here lol.
I looked around but can't seem to get past the part of simply entering "adb devices" in the command after installing android sdk tools. Any help,tips,pointers, advice would be much appreciated! Thanks and have a great day!
Click to expand...
Click to collapse
Did you enable ADB debugging in Developer Options yet?
That must be done when plugging phone into your computer while the phone is booted up.

Obtained Sprint Nexus S 4G, Stuck on ICS

So my buddy gave me this Nexus S 4G, since I like to collect phones. Unfortunately, it appears to be stuck on 4.0 ICS. I tried to check for an update to 4.1 ICS, but for some reason, it reports that my phone is up to date??? Wtf. So I tried doing it manually, I can't flash this random OTA which may or may not (probably is) Jelly Bean in stock recovery, but it fails. I tried doing it even more manually using fastboot, but for some reason, I can't get the USB drivers to work. My next step is to use a Macintosh, as they seem to work better with Android, but I don't have access to it yet. In the mean time, is there any other way to get this phone updated or, at the very least, rooted and ROM'd?

@Dr. Hax
I'm assuming you are using windows? If so burn a Linux iso, Mint or Ubuntu are both great. You can make a bootable iso using a thumb drive or CD. Then set up your pc for dual boot. You'll never have a driver issue on Linux.
I'm sure you probably know this but how I have gotten windows to work and see my device is install the fastboot and adb 15 second installer from here: https://forum.xda-developers.com/showthread.php?t=2588979
Then reboot of course. And when I plug my device in have developer options enabled and usb debugging enabled and be watching phone for the little box pop up that you just checkmark really quick so your pc can communicate with the device... Also if you scroll down on the phone in developer options to "default usb configuration" and change that to "file transfer", that will usually bring the little box up on my devices to check mark so they can communicate..It only shows for a second then it's gone. But if it hasn't popped up yet then open terminal and type sudo adb devices (hit enter) and again be watching your phone because that little box should then come up that you must quickly check mark on phone so pc and phone can communicate.
I always uninstall and reinstall drivers on windows and reboot afterwards. Also make sure check device manager and see what's there. But that 15 second fastboot adb installer for windows is a life saver and makes it all super easy!! On Linux none of this happens. Ever! ? You just plug in your phone and the model of your device shows up on the computer screen. IDK if this makes sense much but I tried to word it where it did best I could. Hopefully this helps or you already got it going.