Computer does not see the device in bootloader- nexus 5x - Nexus 5X Q&A, Help & Troubleshooting

Hi everyone !
I am pretty new here, therefore please forgive me if I have chosen wrong subject.
I have got a problem with Nexus 5x with Android8 OPR6 (Oreo), BHZ21d, the USB debugging is enabled, OEM lockdown. Moreover, I have ADB drivers installed. When connected to a PC, the phone is detected and when it enters the bootloader mode, the computer does not see it.
What I want to do is unlock it and go to Android 7.1
Maybe someone has such a case and knows how to solve this problem?
I would appreciate any help
PS. I tried the Nexus Tool and CMD and unfortunately can not get it.

If you boot regularly, connect phone with pc and enter fastboot devices: is your device listed?

Related

[UNLOCK] [H815] Fastboot won't recognize my LG G4 in fastboot mode...

First I must say, I searched all over the internet for answer to this problem. None of the topics I read had matched my problem.
I want to unlock my bootloader so I can flash custom recovery and get root access.
When I want to access the bootloader ("adb reboot bootloader"), in my phone all goes fine (I see on my phone the Fastboot instructions, etc). The problem is in my computer that fastboot won't recognise my phone anymore. When I want to get the device-id, fastboot is stuck on "waiting for all devices". When I want to see the list of devices, ("fastboot devices"), I get nothing, wether my phone is on bootloader mode or not.
I installed all the LG drivers, including the ADB one. I am in USB debugging mode, and I disabled OEM protection.
Android version is Lollipop.
I need help on this matter, thanks in advance.
notrium dweller said:
First I must say, I searched all over the internet for answer to this problem. None of the topics I read had matched my problem.
I want to unlock my bootloader so I can flash custom recovery and get root access.
When I want to access the bootloader ("adb reboot bootloader"), in my phone all goes fine (I see on my phone the Fastboot instructions, etc). The problem is in my computer that fastboot won't recognise my phone anymore. When I want to get the device-id, fastboot is stuck on "waiting for all devices". When I want to see the list of devices, ("fastboot devices"), I get nothing, wether my phone is on bootloader mode or not.
I installed all the LG drivers, including the ADB one. I am in USB debugging mode, and I disabled OEM protection.
Android version is Lollipop.
I need help on this matter, thanks in advance.
Click to expand...
Click to collapse
not all phones can be unlocked.. search for g4 list of bootloader unlock youll see the list if yours isnt there you cant . only root 5.1 no twrp.
raptorddd said:
not all phones can be unlocked.. search for g4 list of bootloader unlock youll see the list if yours isnt there you cant . only root 5.1 no twrp.
Click to expand...
Click to collapse
I know mine can be unlocked. I actually can get to the bootloader via ADB. The problem is that fastboot won't recognise my phone afterwards. (I believe it's the european version of the H815 model, and according to one-click-root app, my phone can be safely rooted. Also my Lollipop version is 5.1.)
There are other few issues also:
Fastboot won't recognise my phone, even if the phone is not in bootloader mode.
Windows will recognise all of the LG related drivers including the ADB related driver, while the phone is powered on normally.
However, it fails to do so, in bootloader mode. I see non working driver in Windows 7 Device Manager, under "Other Devices" by the name "Android" with yellow exclamation mark. Nothing else.
Still looking for advice...
notrium dweller said:
I know mine can be unlocked. I actually can get to the bootloader via ADB. The problem is that fastboot won't recognise my phone afterwards. (I believe it's the european version of the H815 model, and according to one-click-root app, my phone can be safely rooted. Also my Lollipop version is 5.1.)
There are other few issues also:
Fastboot won't recognise my phone, even if the phone is not in bootloader mode.
Windows will recognise all of the LG related drivers including the ADB related driver, while the phone is powered on normally.
However, it fails to do so, in bootloader mode. I see non working driver in Windows 7 Device Manager, under "Other Devices" by the name "Android" with yellow exclamation mark. Nothing else.
Still looking for advice...
Click to expand...
Click to collapse
am sorry i cant help ive nver unlocked mine..
Still looking for suggestions, people...
I have the same problem, adb detects my phone but fastboot does not. Same Phone btw
Still no solution until now ? I have the same problems
My device is H815
Hi !
I have had this problem too...solved with strong battle to understand myself...
My solution : when you have installed driver ,when your phone go to fastboot mode and the pc don't want to reconize the phone : on the pc on windows go to harware manager (config panel) and you can see in theory "android" with a "?" ==> you have to install manually the driver by searching somewhere on the harware list "android adb interface " (i don't remember where it is) ==> your phone wil be reconized ! And you will have the 2 lines of ID on the adb comand interface....and follow the tutorial...
I have read hundreds of issues with driver problems when it comes to windows.
Please try Linux instead. There are live distributions like Ubuntu available. Install it on USB stick and start from there.
No driver issues anymore. Just works.
.
@steadfasterX it need some knowledge for to use Linux OS for adb thingsv (unlock bootloader ,instal TWRP,rom,apps...etc...) ? maybe you can do a small tutorial for to help ?
For windows i have found these pictures for an eventual help (see ZIP on attach file)
@Loulou-13 , now i can see my device-id - solved -
but now have another problems, my imei is not match with my device-id ...
my device is H815
yes...i know i have sent an answer too late ... but my solution is one of this problem and eventualy can be useful for other people.
for your new problem ,what happen ? .......have you enter the corect number ,without space or other ?
Loulou-13 said:
@steadfasterX it need some knowledge for to use Linux OS for adb thingsv (unlock bootloader ,instal TWRP,rom,apps...etc...) ? maybe you can do a small tutorial for to help ?
For windows i have found these pictures for an eventual help (see ZIP on attach file)
Click to expand...
Click to collapse
Well there are hundreds of guides out there just use google...
adb and fastboot working the same way under Linux so there is no need to have a specific guide for linux.
I haven't tested that guide here but it looks very good as a starting point:
http://forum.xda-developers.com/showpost.php?p=44739402&postcount=1
As said there are other maybe better guides but Google will tell you.
.
@steadfasterX thank for your link ,it's useful for people who have problem and read this thread
It's not for me .... i have my bootliader unlocked ,twrp...( and this fabulous Imperium MM rom !!!! )

Can't get windows 10 to detect my Fastboot device

hey guys, I just got my OP3, I want to open the bootloader before I store some data that will be erased anyway when unlocking, I enabled USB Debugging & OEM unlocking & Advanced reboot and then I accepted the RSA Fingerprint popup. (Then, when running adb devices, I got the id of my device).
Now, I am in bootloader mode, and when running fastboot devices, I get nothing. I already installed Oneplus drivers when first connected the device.
In Device Manager under Other Devices I can see a device named "Android". When trying to install the drivers manually by browsing devices I have on my computer, I can only see "Samsung ADB Interface" and I am afraid installing this will not work when trying to unlock the bootloader. What can I do? I also have a Kali Linux Laptop if that's helping. Thanks.
Put in fastboot mode, connect to computer and manually select fastboot interface from the device manager "install device/update driver manually" box. That worked for me.
JusTeN_ said:
hey guys, I just got my OP3, I want to open the bootloader before I store some data that will be erased anyway when unlocking, I enabled USB Debugging & OEM unlocking & Advanced reboot and then I accepted the RSA Fingerprint popup. (Then, when running adb devices, I got the id of my device).
Now, I am in bootloader mode, and when running fastboot devices, I get nothing. I already installed Oneplus drivers when first connected the device.
In Device Manager under Other Devices I can see a device named "Android". When trying to install the drivers manually by browsing devices I have on my computer, I can only see "Samsung ADB Interface" and I am afraid installing this will not work when trying to unlock the bootloader. What can I do? I also have a Kali Linux Laptop if that's helping. Thanks.
Click to expand...
Click to collapse
Its fine just search for fastboot devices and see if your device comes up. Mine was showing the same thing and i continued and it worked

adb devices: no device found, why ?

Just a quick question.
Im unable to access fastboot or bootloader mode through adb command line.
I turned on usb debugging, connected phone to usb cable with my pc, run command line in platform-tools - adb devices and nothing happens.
I think i know the answer, but i want to be sure. Is it because i dont have unlocked bootloaded (OEM Unlock, still 6 days to wait)
Do you have the proper drivers? Try downloading the universal ADB drivers.
Sent from my Lenovo P2a42 using Tapatalk
Switch USB mode to PTP instead of MTP. I don't know why, but it works like that after Android KitKat/Lollipop release. Used this trick on LG G2 mini and now on my P2
I dont know if i have correct drivers, but i think so
https://dl.google.com/android/installer_r24.4.1-windows.exe
http://download.oracle.com/otn-pub/...m=1498221676_80503fd7b283f64cfa8ae7825b0021e2
My Xiaomi Redmi phopne is detected correctly, but its rooted and OEM unlocked
edit:
It's fine now. Its unbelivable what a mess is with adb files/usb drivers and similar. There is so much that can go wrong.
I wiped everything and installed minimal adb and fastboot + lenovo usb/mtp drivers
Now pc detects my phone.

Motorola Moto G Fast (2020) - Rooting and Custom ROM Suggestions

Hey All,
I just got my first Android phone to have a bit of a project for my first root/custom ROM of a phone. I chose the Moto G Fast because it seems relatively easy to unlock the Motorola bootloader and such, but I am still new to this so I wanted to see if anybody here had any suggestions insofar as rooting goes and what custom ROM to use for the phone. Ideally I would like to use Lineage OS but Lineage 17 (current) does not support the Moto G Fast and the release date of Lineage 18 is yet to be announced. So does anybody here have any recommendations for a custom android ROM and maybe some tips/tricks when it comes to rooting/unlocking the bootloader?
Thank you in advance. Any and all advice is greatly appreciated.
Just a quick bump for this thread. I could use some suggestions/guidance.
To unlock your bootloader, follow the steps from this link: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Rooting is as easy as intalling recovery and flashing magisk.
Beetle84 said:
To unlock your bootloader, follow the steps from this link: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Rooting is as easy as intalling recovery and flashing magisk.
Click to expand...
Click to collapse
Thank you very much for the helpful info. I am looking through this now. I am curious as to whether or not there is a Linux equivalent to the Motorola USB drivers. I only see Windows/MacOSX.
Another issue that I've just come across is that the Android SDK cannot seem to find my phone when it is connected to my computer. When I run the command "fastboot oem get_unlock_data" I am met with a perpetual <waiting for any device> prompt. My phone does not show up in the file explorer or device manager either despite having downloaded the motorola drivers. Also, I have OEM unlock and usb debugging enabled. Does anyone have any ideas as to what the issue could be?
Just a quick bump for the day.
PrettyDumbITGuy said:
Another issue that I've just come across is that the Android SDK cannot seem to find my phone when it is connected to my computer. When I run the command "fastboot oem get_unlock_data" I am met with a perpetual <waiting for any device> prompt. My phone does not show up in the file explorer or device manager either despite having downloaded the motorola drivers. Also, I have OEM unlock and usb debugging enabled. Does anyone have any ideas as to what the issue could be?
Click to expand...
Click to collapse
I hate to ask the stupid question, but you did reboot to the bootloader before the unlock command right?
Otherwise, Linux issues aren't my thing, hopefully someone else can give you a hand there
Beetle84 said:
I hate to ask the stupid question, but you did reboot to the bootloader before the unlock command right?
Otherwise, Linux issues aren't my thing, hopefully someone else can give you a hand there
Click to expand...
Click to collapse
Not a stupid question at all. I am very new to phone rooting/android phones in general so the inquiry is warranted.
To answer your question, I did boot to the bootloader after enabling OEM unlock. When in fastboot mode I receive a green prompt that shows a connection and that the phone is in transfer mode. However, when I execute the commands in Android SDK to unlock the boot loader my computer is unable to locate the device. This problem occurs on both Windows and Manjaro Linux.
On windows 10 you have to disable driver verification I'm pretty sure for the fastboot drivers to work correctly. It's been awhile since I've done it so best bet is to google this.
Beetle84 said:
On windows 10 you have to disable driver verification I'm pretty sure for the fastboot drivers to work correctly. It's been awhile since I've done it so best bet is to google this.
Click to expand...
Click to collapse
I disabled driver verification with the following command "bcdedit /set testsigning off" and then connection my phone. The Win10 machine still does not detect the phone as a usable device. I receive a warning box with the following error "USB device not recognized. The last USB device you connected to this computer malfunctioned and Windows does not recognize it. "
PrettyDumbITGuy said:
.
Click to expand...
Click to collapse
PrettyDumbITGuy said:
Not a stupid question at all. I am very new to phone rooting/android phones in general so the inquiry is warranted.
To answer your question, I did boot to the bootloader after enabling OEM unlock. When in fastboot mode I receive a green prompt that shows a connection and that the phone is in transfer mode. However, when I execute the commands in Android SDK to unlock the boot loader my computer is unable to locate the device. This problem occurs on both Windows and Manjaro Linux.
Click to expand...
Click to collapse
Did you install android tools and android udev on Manjaro
BTK19 said:
Did you install android tools and android udev on Manjaro
Click to expand...
Click to collapse
Yes, I did. The problem I run into on Linux is much the same as the problem that I run into on WIndows. The computer simply does not recognize the phone as a device and the Android SDK tools do not detect the phone. I almost wonder if maybe something is wrong with the phone? Perhaps I purchased a defective device? I know that normally when you plug in your phone to a machine you receive a prompt on the phone asking you whether or not this is a "trusted device" but I receive no such prompt on my Moto G Fast. I'm almost wondering if I should just return the phone and get something else. Perhaps a Moto G8 power or maybe one of the new Nord line of One+ phones.
This may be redundant. But I suggest you try another cord. More often than not I find myself weeding through charge only cords till I find a data cord. Also try using a USB 2.0 port, preferably attached (rear of the computer) as opposed to any front ports or hub.
PrettyDumbITGuy said:
Hey All,
I just got my first Android phone to have a bit of a project for my first root/custom ROM of a phone. I chose the Moto G Fast because it seems relatively easy to unlock the Motorola bootloader and such, but I am still new to this so I wanted to see if anybody here had any suggestions insofar as rooting goes and what custom ROM to use for the phone. Ideally I would like to use Lineage OS but Lineage 17 (current) does not support the Moto G Fast and the release date of Lineage 18 is yet to be announced. So does anybody here have any recommendations for a custom android ROM and maybe some tips/tricks when it comes to rooting/unlocking the bootloader?
Thank you in advance. Any and all advice is greatly appreciated.
Click to expand...
Click to collapse
Unlocking my G Fast was Sooo easy, i asked Boost to unlock phone, no charge! then i 5apped UICC UNLOCK btn under About Phone, done & done.

Bootloader un-detected.

I am trying for the first time to root my 7t pro McLaren, and I ran into a problem. When the boot loader is turned on, and I use fastboot devices, nothing happens. When I do adb devices with it powered on, it shows that its connected. I tried to use the oneplus usb driver update, and nothing happened. does anyone have any solutions? I have OEM unlocking turned on and SIM permantly unlocked. If it helps I'm running on windows 10.
KH-Squisshy said:
I am trying for the first time to root my 7t pro McLaren, and I ran into a problem. When the boot loader is turned on, and I use fastboot devices, nothing happens. When I do adb devices with it powered on, it shows that its connected. I tried to use the oneplus usb driver update, and nothing happened. does anyone have any solutions? I have OEM unlocking turned on and SIM permantly unlocked. If it helps I'm running on windows 10.
Click to expand...
Click to collapse
Hi.
What you want to do exactly?
To Root open bootloader as first.
Developer options /Default usb configuration/ file transfer. Then check if pc "see" your device. fastboot fastboot devices. If visible then u are at home let's say
Make sure your USB port on the phone is clean using compressed air. Though if it works with ADB it should also work in bootloader
Riski3Run said:
Hi.
What you want to do exactly?
To Root open bootloader as first.
Developer options /Default usb configuration/ file transfer. Then check if pc "see" your device. fastboot fastboot devices. If visible then u are at home let's say
Click to expand...
Click to collapse
I was trying to just root it, but I found out what it was. someone sent me the drivers to update my device in manage devices.

Categories

Resources