i really could use some help friends im having problems with adb on windows when my device is on adb can see it of course
C:\adb>adb devices
List of devices attached
ZY22236P94 device
the problem is when its in bootloader mode adb cant seem to see it i have all drivers installed and i cant understand why im getting this error i want to install a recovery and i cant i currently have know recovery installed and i really need to rest my phone cause of a lot of software issus this is the message that get when bootloader mode
C:\adb>adb devices
List of devices attached
it shows nothing attached on windows devices manager it shows motorola adb interface connectad and running fine so i cant understand what im doing wrong please i really need some help here mates
You need to use fastboot commands in the bootloader, not adb.
Sent from my MotoG3 using Tapatalk
Related
installed adb and fastboot inorder to mod a HTC Dream,
adb devices gives a response when I use it,
when I power into the fastboot and connect the phone
fastboot devices gives nothing, just returns to prompt, no error messages, but no devices listed
running fastboot gives the command list
can I assume fastboot is running correctly even though it doesn't give me a device list?
hmmm, no replies, maybe I'm the only one who doesn't know this,
but, how can I check that fastboot is actually connecting to the phone, and if it should show devices and doesn't how can I check whats wrong?
Hi,
I'm kind of a noob at this rooting stuff. I've looked ariund, done my research and everything but it never seems to go smoothly??..
I think the main problem is with the drivers. After following instructions the android drivers still said 'Android 1.0'. So I installed Pda net and then I got 'Android ADB Interface' drivers. Soo the thing is, after searching for 'adb devices' in cmd prompt, It says 'list of devices' but there's nothing in the list....?
For some reason it won't do any commands like 'adb reboot bootloader' or 'fastboot oem lock'. It says not found. I have installed all the sdk and packages...
Would really appreciate some help from you guys. I didn't think rooting would be so complex??...
Thanks
can you post screenshot??
Ok for some reason, after starting the cmd again today and typing adb devices, it has listed my device. But when I type 'fastboot oem lock' (because my bootloader is already unlocked) it says not found as shown in the screenshot.
Am I doing something stupid??...
70 views?... cant anyone help ... please..
soulja786 said:
70 views?... cant anyone help ... please..
Click to expand...
Click to collapse
If adb devices lists your device you're not in the boot loader, the ONLY place fastboot will recognize your device and function or you have a driver issue. You're either in recovery or booted up. Reboot into the boot loader to use fastboot.
If you get into the boot loader and fastboot still doesn't show your device it's a driver issue. Update the driver manually and point it to the SDK USB driver provided with the SDK.
For reference....
Booted into boot loader:
Fastboot OK
ADB NO
Recovery / Fully booted
Fastboot NO
ADB OK
Hi guys,
I really do think this is a driver issue... any idea on how to solve it? I do have PDA Net installed... ?
@krohnjw ... could you please clarify.. Im a bit lost.
Thanks!
Did you try something like oneclickroot?
http://forum.xda-developers.com/showthread.php?t=1138755
Well I also had a lot of issues trying to root my i9020t so let me try to help..
Phone will be recognized with ADB when u select enable debug on developer options. You ll see "Android ADB Interface" on SYS DRV.
On other hand , when U start phone on fasboot mode, it should install something like "Android Bootloader Interface " , if U keep seeing "Android ADB Interface" , its wrong, but took some time to realize that.
That happened to me when I was using WinXP x32 to root my phone, ironically thinking it would be more compatible an less prone to bugs... When done it on W7 x64 , my fastboot driver was discovered correctly (Android bootloader Interface) using x64 PDA drivers, and all went good then!
Hope this may help!
hello,
I'm hoping someone here can help me sort out my current problem.
I've been trying to root so I can install the latest ICS port, but having problems at the Fastboot screen.
I apologize in advance if some of the references/names I'm using are incorrect.
So, I had originally unlocked my Nexus S sometime early this year. When I restart the phone, the "unlocked" lock picture shows up under the "Google" words, and when I go into fastboot mode, the Lock State is Unlocked.
I'm running 2.3.6 right now on the Tmobile version of the phone.
When the phone is on (not in fastboot mode), I can execute ADB commands and the device is recognized. As soon as I go into fastboot it isn't.
I'm running 64bit Win 7, and I have gone through the various threads that have listed this issue, and installed PDA Net drivers and still there is no solution.
In Fastboot mode, while connected to computer under device manager, it shows up under Universal Serial Bus Controllers as an Unknown Device... I'm unable to update any drivers for it, and even when I try to manually update the drivers by going to the PDANet drivers it does not allow it.
When the phone is on in regular mode in device manager it shows up as Android Phone and within that it has a listing called Android Composite ADB Interface.
As mentioned above, when phone on in regular mode everything is detected.
I installed clockwork app from market, assuming that the phone was "rooted" based on the "unlock state" in fastboot mode, but it immediately says that phone needs to be rooted because it was unable to find SuperUser file etc etc.
I've spent the better part of a few days trying to figure this out by checking all sorts of links, but I haven't found a solution. The main issue is that the phone is not being recognized when in fastboot mode when connected by USB. And I'm unable to install the proper drivers for fastboot mode.
Hopefully this makes sense, and someone can provide some insight.
Thanks in advance!
I'm not positive about this but couldn't you adb push the su binary and apk? I don't own the Nexus but I would think since its unlocked you could just push the files. If this would work I would think it's just a temporary solution to allow superuser permission. As I understand it, fastboot is the preferred method for the Nexus.
Sent from my PG06100 using Tapatalk
Did you try a fastboot command like fastboot devices?
Don't know if this applies to you but I had a similar sounding problem when trying to root my Nexus S where everytime I booted into fastboot mode I had an error message at the bottom of the screen saying something like 'fastboot status-fail Invalid command' and so I couldn't use any fastboot functions.
To get around it I used this one-click root . For some reason I got an error message halfway through for whatever reason and it wouldn't complete the root for me but it booted me into fastboot without receiving the error message and then once I was in I went and rooted manually.
The CWM is out of date on that site though (possibly the super-user zip too) so I replaced them with the latest versions and popped it in my dropbox for you, if you wanna try it out.
http://dl.dropbox.com/u/47770734/One-Click-Nexus-S.zip
Edit: just had a little look through the bat script and the initial commands that got me into fastboot properly is (with your phone in debugging mode):
adb start-server
adb reboot bootloader
Click to expand...
Click to collapse
So you could try that first if you wanna go through manually.
Know that you can't run adb command while in fastboot mode. Boot into your CWM and then you can start an adb shell and you'll be able to push all the files you want and execute all the commands you need.
Fastboot mode is for running fastboot indeed. Try 'fastboot devices' while you're in the bootloader and see if devices pop up. If not, you really have to figure out your drivers issue. Maybe remove the device completely from your PC (including driver files) and reinstall it using the PDAnet drivers.
Greetz
I've unlocked the bootloader through the official HTC Dev website, and attempted to follow the procedure here: http://forum.xda-developers.com/showthread.php?t=1341127, however, ADB doesn't work very well.
I attempted to run "adb devices", and it recognises the phone, but says it's offline. When I tried to run zurgRush, it starts up the ADB daemon, and just sits there. Device manager doesn't show anything ADB related, I have unknown sources and USB Debugging enabled too... I have no idea how to get it working. My HD2 is much more well behaved... any suggestions would be welcome!
Hi
Noob alert here.
I'm trying to flash a custom recovery (twrp) on a very old phone which has its bootloader unlocked. (the phone currently runs android 6.0, yes, that old...)
I read on the forums here that I need to use ADB from windows (Win10 here) in order to flash twrp onto the phone (to replace the stock recovery).
I DLed the neccessary files (platform tools), but it's just a bunch of files with nothing to actually install AFAICT...
MAny tutorials mention that I should just launch a CLI from within the folder containing the tools and then run ADB to flash twrp.
However, I get stuck at < waiting for any device > which, according to other tutorials, isa sign that drivers are not installed for my device in windows.
Some tutorial mention that I should INSTALL ADB (rather than just run it from CLI), so I'm starting to wonder what I am missing here.
- Should I INSTALL ADB? how?
- Should I install drivers for my device? It seems like my device is properly detected by Win10 and I couldn't find any driver to install anywhere.
I'm confused about what's going on.
Could you please help me out here?
Thanks a lot for your advice.
Best,
-a-
OK, I made a little progress I think. I'm not sure my issue is actually related to windows drivers but maybe I'm wrong.
Here's the deal:
When my phone is booted and connected to my PC,
adb device
spits up something : the phone is detected. Now after running
adb reboot bootloader
the phones reboots into bootloader mode (and displays the info that the bootloader is unlocked. But from now on,
adb device
in windows CLI outputs nothing : the phone is no longer detected.
Plus now the phone shows up as an unnknown device (fastboot2.0) in windows device manager. So? Missing driver I guess?
Running windows update found a driver for
Google Android Bootloader Interface
So I guess now it should work
I'll post the results
Thanks a lot
-a-
nope...
No luck
ADB still cannot see my device when in bootloader mode
asheenlevrai said:
nope...
No luck
ADB still cannot see my device when in bootloader mode
Click to expand...
Click to collapse
Actually it works!
Even though
adb devices
would not list anything when the phone wwas in bootloader mode, I was able to flash twrp
problem solved!
In the future some commands in Bootloader Mode require fastboot oppose to ADB.