My Huawei P8 lite doesn't want to accept commandlines because it can't be found. When putting in the line, adb devices, it doesn't list.
But Hisuite founds the phone and list the memory info, pictures etc.
I am trying to root the phone after succesfully unlocking the bootloader. The usb-debugging is on, adbdriver6 is installed and minimal adb fastboot. Have I missed something necessary?
Hisuite didnt recognize it at first. So reinstalled it and it started working. All drivers are installed, device manager shows Android adapter ADB interface and Huawei HDB Interface under Android Phone.
Thankful for any help!
Related
Hello,
First of all, the problem started when Android Kitkat update ota came to my device. After downloading it, my device was not able to verify it, as a result of which, it started downloading the update all over again. It downloaded the update more than 10 times without any success.
So finally I decided to sideload it. I set up everything properly, double checked everything. As I was going to send the update.zip to my tablet through command, the cmd prompt showed me "error: device not found".
I restarted the device, checked the drivers in my computer, even checked whether adb recognized it by commanding "adb devices". It did.
So again I turned it off, entered fastboot mode, But this time before entering recovery, I connected the device (it gave the connecting sound as on Win7). I ran the command "adb devices" and it showed no device at all!
My device is complete stock, unrooted. Usb debugging is turned on and MTP is selected.
Use a toolkit to install\test adb drivers then slide load using it. Some times windows install some crap adb drivers u have to remove them and install the naked drivers.
Toolkit is in development section.
I tested with wugfresh toolkit.
Please ignore my spelling mistakes. English is not my native language.
I've got debugging enabled, have tried literally all the connection options, multiple computers, etc. I just want to back up and root my phone. I'm at the point that I'm willing to try a factory reset and pray that works. Is there anything else I can do before that?
Do you have device drivers installed on your computer? Does adb/installed properly? Is OEM unlocking ticked? If its a driver issue update them. If its adb download the minimal adb from XDA. Otherwise that's it.
Device drivers are installed and OEM unlocking is ticked. I'm working on updating adb/fastboot.
Alright, everything is updated as much as it can be, and still nothing. No recognition whatsoever.
What version of windows are you running?
I had to do this to get mine to work... go into the device manager on Windows, find the Nexus, right-click and choose update driver software. Browse to where the driver is located on your PC and select the folder.
Hi!
So I've just received my Oreo 8.1 update. but before updating, I decided to backup my EFS/persist after some reading in this forum.
Turns out ADB works fine, "adb devices" shows my phone ID but when I reboot to booloader, fastboot doesn't work, it doesn't show my phone ID.
While on ADB mode:
On Windows 10 Device Manager, Moto G5 Plus is listed under Android Devive > Motorola ADB Interface. (Everything ok here, no exclamation mark, working as it should)
-While on fastboot mode:
Phone gets listed under "Other Devices" as "Fastboot Potter S" (exclamation mark inside a triangle)
Tried uninstalling/reinstalling motorola drivers but I always get: Windows found drivers for your device but encountered an error while attempting to install it."
-Moto G5 Plus (XT1683) - Stock, Nougat 7.0 ( NPNS25.137-92-14 )
-Debugging mode is enabled.
-When connected to the PC, If I change from Charging to Transfer Files, my phone doesn't show up as another drive where I can transfer files and also gets listed as MTP (Exclamation mark/Triangle) under "Other Devices"
-Windows 10. Updated.
Anyone has been through that? Any ideas, tips, solutions or workaround would be appreciated.
Use "Fastboot Reboot Bootloader" device will go to bootloader automatically without the need of switching off.
I know I am probably the millionth person to say this, but I can't for the life of me get my device recognized in ADB when it's in Bootloader.
What I have tried so far:
- Activated OEM Unlock, USB debugging and set my computer to always be allowed for usb debugging
- Manually installed latest google usb drivers through device manager
- started up adb in cmd, made sure the device was recognized, rebooted in bootloader to check device list again
- Same thing, but with the drivers from the Mi A1 Tool)
The results:
- in Bootloader: Not recognized in ADB, but windows device manager shows "Android Bootloader Interface" as properly installed with google's driver 11.0.0.0.
- booted up: Recognized in ADB as " d59.... device" and in device manager as "ADB Interface"
This is not my first android rooting experience, but I have never had such problems installing drivers before. Is there anything special about the MI A1 I don't know? Anything I am forgetting maybe? All other Threads I found weren't helpful.
Thank you in advance for just taking the time to read until this point Any pointers even just links will be much appreciated!
Did you type 'su' after opening ADB/command prompt?
No I did not. Will try it out at home, but isn't that just for superuser meaning root access? The command to list devices should be "adb devices" not matter what mode the device is in, no?
Thank you for the tip!
Use "fastboot devices" "fastboot oem unlock".
Hey, I just bought an S7 Edge SM-G950U, the att&t version, SM-G950A. I heard some say that it's not possible to unlock its bootloader, but the OEM unlock option turned out to be available in developer options. However, I'm having a hard time properly installing its drivers, whichever adb driver I use, the driver still shows a yellow warning and the error is that the device can't be started. The device shows up with adb devices when the device is on, but it doesn't neither with fastboot devices nor adb devices when it's in download mode. I'm trying to install TWRP, the hero 2 version. Any help would be appreciated. Thanks in advance
If you in Windows Device Manager find any device with yellow mark right on the device, then the driver installed for it isn't suitable: uninstall it, get Samsung USB Driver and install it.
Samsung devices don't know of a Fastboot mode: there it's called Download mode. You can't run any Fastboot command in this mode.
ADB operates on Android OS, not on device's bootloader, hence it's not working when running the device in Download mode.
Thanks for the prompt reply. I used a different laptop and managed to install the drivers properly, no warnings. However, the result is the same. You mention how I can't run fastboot commands in Download mode, where can I run them? Only Odin is working in that mode now, but I gotta try to unlock the bootloader. A lot of people are saying that this model can't be unlocked, even though the OEM unlock checkbook in the Developer settings is there. Any advice is appreciated
Up
Gearninja said:
Up
Click to expand...
Click to collapse
Down