Hi everyone !
I'm having troubles in rooting my phone, let me explain:
When i enter "adb devices" in cmd, no problem i can see my phone,
So i enter "adb reboot bootloader", but here, Windows displays a "Unknown device"
I thinked it was about the drivers, so i tried to install them in the device manager but it's impossible to find Google or Huawei or even Android in the Manufacturer list,
I have Android SDK installed, and when i plug my phone it's showed as "Android adapter ADB interface" in the device manager
Thanks for the help !
Okay, try to re-enable USB Debugging from the Developer options.
If that doesn't works, then Revoke USB debugging authorizations in Developer options and reconnect your device, and allow the PC again.
This might solve the problem.
Hope this helps you.
DigiGoon said:
Okay, try to re-enable USB Debugging from the Developer options.
If that doesn't works, then Revoke USB debugging authorizations in Developer options and reconnect your device, and allow the PC again.
This might solve the problem.
Hope this helps you.
Click to expand...
Click to collapse
I tried but it didnt solve thé problem.
Thé phone is displayed as "unknown device" in fastboot mode
gignagent said:
I tried but it didnt solve thé problem.
Thé phone is displayed as "unknown device" in fastboot mode
Click to expand...
Click to collapse
Try to install honor 5x driver then try again
Did you tried connecting after doing a factory reset? Maybe it can help.
Related
Hi, I have already had my USB debugging enabled and from my device manager I can see my device there showing "ASUS Android Devices" > "Asus Android Composite ADB Interface".
But when I reboot my tablet as USB mode and from my laptop I run cmd as Administrator, and run "adb devices" command, it just show me "List of devices attached" and then the command prompt.
I have already unlock and rooted my tablet.
Why I can't see my device id ? Please help
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
Yeah this process is correct. Even I've experienced this.
What I did is:
Removed the USB cable connection and reconnect.
Kill adb.exe
Restart adb.
Then device was shown to be connected.
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
Yes, I did that but still the same. Any other suggestions?
If on windows make sure your driver's are installed.
Type in cmd
adb kill-server
adb start-server
If that doesn't work try a different usb slot. You could also try moving adb and it's dependencies to your system32 folder. It's where all your commands are stored for cmd. You won't have to navigate to the android sdk tools.
Sent from my SPH-L710 using Tapatalk 2
Have you enabled Debugging on in your phones Developer settings?
ngaisteve1 said:
Yes, I did that but still the same. Any other suggestions?
Click to expand...
Click to collapse
it's so easy, just turn off your android device, then hold down both "Volume Down" key and "Power" at the same time, wait a few seconds till it start in recovery mode, done.
now type adb devices, and you'll see your device.
no need for that.
close any adb process either from task manager or by typing: "adb kill-server" in adb console
close everything and use this customized adb file I attached, it'll show your device.
it also has instructions and necessary files for rooting your device.
Problem
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
I have LG Optimus G (E975) i wipped all from the device and now i can't put cm11 on it, adb sideload do not work, and list of devices attached is empty. what must i do to put CM11 on my phone?:crying:
I'm having the same issue but I have a ! triangle on my Nexus 5 under Other Devices. Any suggestions???
I have the same issue on my nexus 4. Yesterday it showed up with adb devices, now it's an empty list. I have USB debugging enabled and tried restarting the server. Nothing works. Any ideas?
ldemon360 said:
I'm having the same issue but I have a ! triangle on my Nexus 5 under Other Devices. Any suggestions???
Click to expand...
Click to collapse
unplug the device and adb kill-server then replug the device and try
turn debugging off and then on again
I had the same problem. In my case, i had forgot to enable usb debugging after new rom.
ngaisteve1 said:
Hi, I have already had my USB debugging enabled and from my device manager I can see my device there showing "ASUS Android Devices" > "Asus Android Composite ADB Interface".
Click to expand...
Click to collapse
In your case just disable USB debugging and then enable again.
fix the driver
I had this issue.
In my case when I went to device manager I could see the Device and wasn't installed correctly and could not load the drivers even after having installed them on the PC.
SO I clicked update drivers.
Select that will chose the drivers to install and select the Android Devices - ADB driver.
You will get a warning, but just ignore it and load the ADB driver for the phone.
Ensure you are in the sideload option of the recovery
Now
adb devices
it should show up as Sideload
Now sideload
Cheers
Dirk
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
Thanks, this worked for me.
Just add ur device id in adb.ini
Same issue was faced by me on my micromax Q334 and xolo era, I search lot for that and finally just adding hardware id the device are detected under adb.The steps are clearly shown in my video below..
It will definitely going to sort this problem..
For that just right click on adb driver ,navigate to detail tab and search for hardware id then add to adb.INI
I have also uploaded video on that YouTube: Fix adb connection issue(Adb driver installed, but device not listed)
device listed as "? recovery"
hey,
am trying to connect honor 6(h60-L04) but am not able to see the proper name for my device is just showing "? recovery" and am trying to update the android version coz of the device is in reboot-loop so help me out here
if there is any other option to recover device give me link.
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
not work my friend, the list of devices is empty
Put your phone in PTP mode... just found this. When it was on charge or MTP nothing would connect, but when it was in PTP adb.exe said "error: device offline", but on phone it asked if I wanted to trust the computer!!! Ohhhkay, now we're getting somewhere. Clicked trust and ran adb devices and there it is
See below... I found there are two versions of adb.exe I was using. PTP is not the problem, but adb.exe has to be the right one or it just says offline.
vern.zimm said:
Put your phone in PTP mode... just found this. When it was on charge or MTP nothing would connect, but when it was in PTP adb.exe said "error: device offline", but on phone it asked if I wanted to trust the computer!!! Ohhhkay, now we're getting somewhere. Clicked trust and ran adb devices and there it is
Click to expand...
Click to collapse
ALSO!! Get the newest driver pack from LG "LGMobileDriver_WHQL_Ver_4.1.1". The driver packs in the roots that I downloaded aren't new enough. After Windows got the right drivers I was able to see the COM ports properly.
I'm not sure if I have the root working currently. The "Newest root method V03" where you click on root.bat seems to pick the wrong COM port. When I try to do it manually with Send_command.exe using the other COM port it seems like the root process doesn't work properly. It eventually completes, but no info about what it did etc.
I'm using an LG Transpyre VS810PP with Android 5.1.1 currently, and a Windows 10 64-bit machine.
My end goal is stock lolipop rooted.
I botched a flash and now I cant get developer mode / ADB working.
When I started, my tablet was stock ROM, towelroot. I connect tablet in developer mode, flashed dual recovery and everything was great. I copied the pre-rooted lolipop ROM to my SD card and flashed it. HOWEVER instead of turning off the device, I selected reboot from recovery. This resulted in boot loop.
SOOOO, I figured no worries, just flash old ROM and try again. So did this:installed Androxyde Flashtool
opened XperiFirm
downloaded 1276-8392 and 1274-8801 (I've tried the rest using both ROMs btw)
Tools>Bundler>Create>Selected folder>selected SGP312 for device
For branding I entered the above ie 1276-8392
For version I entered the ver ie 10.5.A.230
Flashmode>checked boxes to wipe everything
The flash goes through without a hitch. Under about tablet, I see
Model : SGP312
Android Ver : 4.4.2
Kernel : 3.4.0-perf-g32ce454, [email protected]#1
Build Number : 10.5.A.0.230
I activate USB debugging and unknown sources, connect to USB and Flashtool returns: Device connected with USB debugging turned off
I went into device manager and found the MTP driver. Also of note, the device ID is: USB\VID_0FCE&PID_5194&REV_0228
I downloaded Sony's ADB drivers, tried to manually update device driver and windows7x64 kicked back driver is not for your device.
I edited the INF to include the hardware ID exactly as it appears in device manager and tried again. This time windows let me load the driver. It shows up in device manager as 'Sony sa0107 ADB Interface Driver'
HOWEVER, Flashtool is still giving me the same MTP message and if I cmd prompt "adb devices" I get nada.
Is there a way to verify developer mode on the tablet? What else can I try? The tablet gives me a notification when I connect 'usb debugging mode connected, ready to install software'
Thanks!
_sadpanda said:
I went into device manager and found the MTP driver. Also of note, the device ID is: USB\VID_0FCE&PID_5194&REV_0228
HOWEVER, Flashtool is still giving me the same MTP message and if I cmd prompt "adb devices" I get nada.
Thanks!
Click to expand...
Click to collapse
I had a very similar problem in 2014. I do not want to discourage you, but at the end I send it back to sony for a repair. They gave me a new tablet and said that the mainboard was broken.
Nevertheless, there is a thread in Sony cross device general, where people like you end up: http://forum.xda-developers.com/showthread.php?t=1849170
You can try and search for help there, maybe you have more luck then me.
Its odd... ADB was working and stopped after flash. Is this what you had or just no connection from the start?
Sorry, I misread your post. I thought your tablet would not start and you could not get flashmode working. Sorry for that.
What you could try:
1. Be sure you actually activated USB debugging in developer options
2. When you connect the device, you should get a prompt on the tablet to allow usb debugging from that computer
Maybe try "revoke USB debugging authorisations" in developer options and reconnect
3. Install the drivers from flashtool/drivers/ or install sony pc companion. Delete your old driver from device manager.
4. try switching between MTP and MSC mode in usb connectivity menu
Since ADB worked before it was probably no driver problem. Now you cannot be sure. Most probably you tapped away the said prompt of allowing usb debugging when connecting.
If none of this helps I don't know of anything more. Maybe try different usb ports or even computers.... Or try to flash again
bernddi said:
4. try switching between MTP and MSC mode in usb connectivity menu
Click to expand...
Click to collapse
UGH!!! I'm a jacka$$. I totally forgot about that menu/setting. fixed instantly.
I've been having issues with adb on pie. It just doesn't recognise my phone. I've tried uninstalling and reinstalling the drivers but it doesnt work for me. Although, the pc can recognise my phone but not in adb. Whenever i run a adb command i don't get a prompt on my phone asking to allow the pc which is weird. I need help here.
Just had the same issue. On Windows. Reinstalled the adb drivers, didn't help. This, I think, is what resolved it for me, YMMV:
While the phone is plugged to PC,
disabled USB Debugging in Developer Options,
observed a toaster notification on Windows about updating/installing drivers for my phone,
enabled USB Debugging again, clicked Allow on the dialog that popped up,
and I was back in business.
nameanyone said:
Just had the same issue. On Windows. Reinstalled the adb drivers, didn't help. This, I think, is what resolved it for me, YMMV:
While the phone is plugged to PC,
disabled USB Debugging in Developer Options,
observed a toaster notification on Windows about updating/installing drivers for my phone,
enabled USB Debugging again, clicked Allow on the dialog that popped up,
and I was back in business.
Click to expand...
Click to collapse
Thanks. I'll try this once i get back home.
Me too
mayankjet said:
Thanks. I'll try this once i get back home.
Click to expand...
Click to collapse
I have the same problem, and it waas not fixed disabling and enabling USB debugging. Did you found the solution? Or someone found? Or God if you are there listening? Or the devil, i am ready to sell my soul for this.
marcebil said:
I have the same problem, and it waas not fixed disabling and enabling USB debugging. Did you found the solution? Or someone found? Or God if you are there listening? Or the devil, i am ready to sell my soul for this.
Click to expand...
Click to collapse
I think i had to update the adb to its latest version.
Sent from my Nokia 7.1 using XDA Labs
I've waited 17 days after linking my Mi account to my Mi8L. I've unlocked more than half a dozen Xiaomi phones, so it's not new to me. However, it stops at 99% and spits out an error message in Chinese. Does anyone know what it means? https://drive.google.com/open?id=1dl6tPZdx7HfFwxQWel3hhjl9doFE5s8S
It means you haven't been using the phone for the necessary amount of time, so unlock isn't possible.
You're probably on a shop or chinese variant that need you to wait 30 days until unlocking.
Sorry for my bad english
Also, check this thread:
http://en.miui.com/thread-4456547-1-1.html
Snowdine said:
It means you haven't been using the phone for the necessary amount of time, so unlock isn't possible. You're probably on a shop or chinese variant that need you to wait 30 days until unlocking.
Click to expand...
Click to collapse
It's strange because when I tried previously, it told me I had to wait 15 days, and I waited longer than that (I took note of the date and time).
Same with me.
Use Mi Unlock 2.3.803.10 (old version).
Works perfectly.
I do not know if you can help me, I was unlocking the Mi 8 Lite requested 15 days to wait after this period I was unlocking and to my surprise the fastboot mode when I connect the USB cable it erases and I can not unlock.
Developer options enabled, usb debugging enabled and oem unlocking also recognizes more when I log in to fastboot it shuts off
rinampa said:
I do not know if you can help me, I was unlocking the Mi 8 Lite requested 15 days to wait after this period I was unlocking and to my surprise the fastboot mode when I connect the USB cable it erases and I can not unlock.
Developer options enabled, usb debugging enabled and oem unlocking also recognizes more when I log in to fastboot it shuts off
Click to expand...
Click to collapse
Try starting the process from adb, don´t use hardware buttons and see what happens.
With device on connect to pc and pay attention that pops up a message "Allow USB debugging" then tap on "always allow" and "ok".
Now type
Code:
adb devices
to see if pc is recognicing and if it is ok type
Code:
adb reboot bootloader
.
Open normally MiFlash Unlock and sign in to your account and follow the scrren on instructions. Provide some screenshots if something fails.
SubwayChamp said:
Try starting the process from adb, don´t use hardware buttons and see what happens.
With device on connect to pc and pay attention that pops up a message "Allow USB debugging" then tap on "always allow" and "ok".
Now type
Code:
adb devices
to see if pc is recognicing and if it is ok type
Code:
adb reboot bootloader
.
Open normally MiFlash Unlock and sign in to your account and follow the scrren on instructions. Provide some screenshots if something fails.
Click to expand...
Click to collapse
Do you have adb and drives for my 8 lite?
rinampa said:
Do you have adb and drives for my 8 lite?
Click to expand...
Click to collapse
Download from here SDK Platform Tools and unzip it preferably in your main drive, you can do all the adb/fastboot processes inside this folder for easier task: https://developer.android.com/studio/releases/platform-tools
And here they´re the USB drivers for our device, choose from Mi 8, it´s the same https://www.xiaomigeek.com/download-xiaomi-usb-driver-windows.html
SubwayChamp said:
Download from here SDK Platform Tools and unzip it preferably in your main drive, you can do all the adb/fastboot processes inside this folder for easier task: https://developer.android.com/studio/releases/platform-tools
And here they´re the USB drivers for our device, choose from Mi 8, it´s the same https://www.xiaomigeek.com/download-xiaomi-usb-driver-windows.html
Click to expand...
Click to collapse
Unfortunately I do not know what happens adb fastboot does not work, I did all the procedure I rebooted in option 7 I installed adb drive the curious one and that the pc recognizes the device opens the internal storage is difficult, I have always unlocked my devices.
rinampa said:
Unfortunately I do not know what happens adb fastboot does not work, I did all the procedure I rebooted in option 7 I installed adb drive the curious one and that the pc recognizes the device opens the internal storage is difficult, I have always unlocked my devices.
Click to expand...
Click to collapse
I'm not sure if you're doing it rightly. Adb works when device is on and fastboot when device is in bootloader/fastboot mode.
When you type for first time adb devices with device power on then you have to see a message from your android screen asking if you want to allow USB debugging, you have to tap on always allow and then in ok.
Provide some screenshot from your pc to see the fail.
SubwayChamp said:
I'm not sure if you're doing it rightly. Adb works when device is on and fastboot when device is in bootloader/fastboot mode.
When you type for first time adb devices with device power on then you have to see a message from your android screen asking if you want to allow USB debugging, you have to tap on always allow and then in ok.
Provide some screenshot from your pc to see the fail.
Click to expand...
Click to collapse
Yes I am aware I have experience always unlocked my gadgets something strange here on my pc or on the device I will try on another pc thank you attention you are correct, thank you.
SubwayChamp said:
Try starting the process from adb, don´t use hardware buttons and see what happens.
With device on connect to pc and pay attention that pops up a message "Allow USB debugging" then tap on "always allow" and "ok".
Now type
Code:
adb devices
to see if pc is recognicing and if it is ok type
Code:
adb reboot bootloader
.
Open normally MiFlash Unlock and sign in to your account and follow the scrren on instructions. Provide some screenshots if something fails.
Click to expand...
Click to collapse
I did as I wrote I entered the fastboot mode with adb and fastboot and the black screen with something written on top of the mini-screen that can not read appeared again, I open the unlock box and this occurs.
rinampa said:
I did as I wrote I entered the fastboot mode with adb and fastboot and the black screen with something written on top of the mini-screen that can not read appeared again, I open the unlock box and this occurs.
Click to expand...
Click to collapse
Plz provide some screenshot from your pc to see what happens on fastboot windows and on MiUnlock Tool; it could happen that you were missing something.
SubwayChamp said:
Plz provide some screenshot from your pc to see what happens on fastboot windows and on MiUnlock Tool; it could happen that you were missing something.
Click to expand...
Click to collapse
This is so after connecting fastboot mode with MiFlash Unlock
rinampa said:
This is so after connecting fastboot mode with MiFlash Unlock
Click to expand...
Click to collapse
Ok, your pc is not detecting your device connected in fastboot mode.
Try uninstalling all the drivers; those that you don´t use and those related with Xiaomi devices and install Mi PC Suite just to get installed the drivers https://mipcsuite.com open it for first time and connect it with your device on just to update drivers between both but when you´ll go to use MiFlash Unlock close it.
The USB cable used for your device is not to be shared with other devices so any of them creates a kind of data map on data wires and pc can have a sort of mistake trying to detect your device rightly.
Then to make all these steps start the process from adb as mentioned before sending with adb command to your device to bootloader/fastboot mode, this is just to confirm that pc is detecting it at both levels; adb and fastboot.
SubwayChamp said:
Ok, your pc is not detecting your device connected in fastboot mode.
Try uninstalling all the drivers; those that you don´t use and those related with Xiaomi devices and install Mi PC Suite just to get installed the drivers https://mipcsuite.com open it for first time and connect it with your device on just to update drivers between both but when you´ll go to use MiFlash Unlock close it.
The USB cable used for your device is not to be shared with other devices so any of them creates a kind of data map on data wires and pc can have a sort of mistake trying to detect your device rightly.
Then to make all these steps start the process from adb as mentioned before sending with adb command to your device to bootloader/fastboot mode, this is just to confirm that pc is detecting it at both levels; adb and fastboot.
Click to expand...
Click to collapse
É Ask me to update my device use Miui beta 10 9.4.25
rinampa said:
É Ask me to update my device use Miui beta 10 9.4.25
Click to expand...
Click to collapse
Uodate it, maybe this corrects some issues
I discovered what is written on the upper left side of the screen, press Key to shutdow. According to research I did not advance anything is USB input problem try on another Pc or a USB Hub cable.
rinampa said:
I discovered what is written on the upper left side of the screen, press Key to shutdow. According to research I did not advance anything is USB input problem try on another Pc or a USB Hub cable.
Click to expand...
Click to collapse
Of course, this is what´s written.
When PC detects device connected on fastboot or download mode then it holds it to avoid that it reboots while some data is transferring from and to each other.
If you put device on fastboot mode without connecting it to any PC then it will shutdown in 4 seconds aprox.
But like your case when PC detects that a device is connected but not in any transferring mode then it prompts to shutdown device.
For this I said that your PC is not recognicing it at fastboot mode, and installing again the drivers could solve the issue.
alxsduarte said:
Same with me.
Use Mi Unlock 2.3.803.10 (old version).
Works perfectly.
Click to expand...
Click to collapse
You right work ?
Hi,
My Nord 2 have latest update DN2103_11_A.17, and I wanted to enable VoLTE.
My computer can't detect my phone in ADB when in recovery mode, it detects only when just powered on normaly and connected.
I have latest Android plateform tools installed on computer.
Any Idea of what's wrong ?
Thanks
Adb drivers and permissions.
Try in Linux, easier
I have exactly the same problem on my OneNeplus Nord 2. I installed the MediaTek_Preloader_USB_VCOM_Drivers drivers in auto mode and even in manual mode under Windows 10. When I type adb reboot recovery the smartphone reboots in recovery mode even if it tells me seems strange see photo (sorry very small text...) but then no other orders are accepted. Same problem in bootloader mode. So I can't unlock the bootloader. Any help is welcome...
Hey I had the same issue with fastboot device not showing up. Fastboot with other devices on my PC had never been an issue.
This Fixed it for me:
Open "Device Manager" from the Windows start menu.
Your device should be listed there as "Android Device" (with a yellow indication for missing driver)
Right click the device and select "Update Driver".
Click Browse my computer for drivers.
Click Let me pick from a list of available drivers on my computer.
From the list select "Android Bootloader Interface". It is possible that you need to deselect the "Show compatible hardware" button.
Good luck.
cukierkas said:
Adb drivers and permissions.
Try in Linux, easier
Click to expand...
Click to collapse
Hi, thanks I'll try. Any specific driver for Linux?
I've read that adb in recovery mode doesn't work since A.14 update, and I'm on A.17. Anyone Can confirm that?