Database Users

Phone can't read ADB in Fastboot/Bootloader Mode. Recognizes when its on though.

I need help figuring this out. My phone pops up and recognizes my computer when it's on, but not when in bootloader mode. I'm trying to flash the new bootloader/radios, but I can't. I've already uninstalled and reinstalled google drivers via SDK. Any suggestions? Yes it responds properly when on when i type "adb devices" just not when in bootloader mode.

aval1392 said:
I need help figuring this out. My phone pops up and recognizes my computer when it's on, but not when in bootloader mode. I'm trying to flash the new bootloader/radios, but I can't. I've already uninstalled and reinstalled google drivers via SDK. Any suggestions? Yes it responds properly when on when i type "adb devices" just not when in bootloader mode.
Click to expand...
Click to collapse
Can you be a bit more clear on this? Adb doesn't work in bootloader mode, it isn't meant to, so if you're using adb commands while in the bootloader you're doing the wrong thing. What OS are you using? Exactly what command(s) are you issuing?

How about "fastboot devices"?

Heisenberg said:
Can you be a bit more clear on this? Adb doesn't work in bootloader mode, it isn't meant to, so if you're using adb commands while in the bootloader you're doing the wrong thing. What OS are you using? Exactly what command(s) are you issuing?
Click to expand...
Click to collapse
I figured it out. It took me a bit to realize adb doesn't work in bootloader. But I installed the correct drivers using max Lee's radio, bootloader, vendor flashing video if anyone needs in the future. Thanks for all you help with Heisenberg. https://www.youtube.com/watch?v=jwEJJIQEt3Y if anyone needs help like I did

aval1392 said:
I figured it out. It took me a bit to realize adb doesn't work in bootloader. But I installed the correct drivers using max Lee's radio, bootloader, vendor flashing video if anyone needs in the future. Thanks for all you help with Heisenberg. https://www.youtube.com/watch?v=jwEJJIQEt3Y if anyone needs help like I did
Click to expand...
Click to collapse
We already have a detailed guide right here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Problems Reverting to Stock

I briefly took over another thread where this issue didn't belong, but since I am still having issues, I thought I would start my own thread. Okay, so I am on Sprint, sideloaded several of the updates, including most recently the Oreo Beta. I have been very happy with the beta, and was looking forward to the update due this week. However, yesterday evening I dropped the phone on the sidewalk and it cracked very badly, and as I am paying insurance with Sprint I want to bring it to a store and have it fixed. Not only is the screen badly cracked, but the keyboard is acting up a bit also.
Anyway, I was getting advice on the Oreo thread about how to do this, and as I said, I had hijacked the thread, but I was at work and didn't get to try this until tonight when I got home. Anyway, I had originally plan to just find the Ota and sideload it, but it was recommend that I use flashall and the full image file from the Essential site. I tried to do that, but when I restart the phone to get into Bootloader mode, it disappeared from the list of devices visible on my desktop and via adb. It was a bit disturbing to me as I am not used to working in Bootloader, previously did anything like this via recovery, and I wasn't sure how to exit the bootloader, but I chose power off, and saw a weird screen with what looked like a coffee cup, and eventually the phone rebooted and seems unchanged at the moment.
I still want to revert to the sprint nougat before I bring the phone in, but I admit I am a little nervous now about the best way to do this. I could use some suggestions. I hope this post is not too long-winded, but I wanted to explain as much of what has happened as possible.

maltydog said:
I briefly took over another thread where this issue didn't belong, but since I am still having issues, I thought I would start my own thread. Okay, so I am on Sprint, sideloaded several of the updates, including most recently the Oreo Beta. I have been very happy with the beta, and was looking forward to the update due this week. However, yesterday evening I dropped the phone on the sidewalk and it cracked very badly, and as I am paying insurance with Sprint I want to bring it to a store and have it fixed. Not only is the screen badly cracked, but the keyboard is acting up a bit also.
Anyway, I was getting advice on the Oreo thread about how to do this, and as I said, I had hijacked the thread, but I was at work and didn't get to try this until tonight when I got home. Anyway, I had originally plan to just find the Ota and sideload it, but it was recommend that I use flashall and the full image file from the Essential site. I tried to do that, but when I restart the phone to get into Bootloader mode, it disappeared from the list of devices visible on my desktop and via adb. It was a bit disturbing to me as I am not used to working in Bootloader, previously did anything like this via recovery, and I wasn't sure how to exit the bootloader, but I chose power off, and saw a weird screen with what looked like a coffee cup, and eventually the phone rebooted and seems unchanged at the moment.
I still want to revert to the sprint nougat before I bring the phone in, but I admit I am a little nervous now about the best way to do this. I could use some suggestions. I hope this post is not too long-winded, but I wanted to explain as much of what has happened as possible.
Click to expand...
Click to collapse
Just an FYI, I found that putting Oreo on the phone resulted in ADB not working 100% anymore, such as attempting to reboot into recovery/etc. It would just reboot back into the O.S..
Here is what I did to flash the stock firmware.
- download the current release you want to flash. (e.g. NMJ32F), then unzip it into a new folder.
- on your phone, verify that USB debugging and OEM unlocking are turned on in the developers menu.
- reboot your phone into the fastboot mode (power and volume down buttons)
- from your adb command line: type: fastboot flashing unlock
- This will make your phone show a new screen asking if you want to unlock the bootloader. Use the volume down to select YES, and hit the power button. It will now reboot and erase the phone. It will eventually end up booting up too request you setup the phone. (that is what it did for me.)
- reboot the phone back into the fastboot mode (power and volume down buttons)
- you should now see the bootloader listed as unlocked (vs locked)
- from your adb command line: type: fastboot devices (which should show your phones serial number and fastboot next too it.
- on your computer, using the command line, go to the unzipped folder of the NMJ32F build you downloaded
- in the folder there is a batch file you will run called flashall.bat. run it
- your phone will start flashing the NMJ32F build
- when it completes it will reboot a couple of times, erase the phone, and end up at the "lets get started" screen.
- reboot the phone back to the fastboot mode
- from your adb command line: type: fastboot flashing lock
- select the option to lock your bootloader. The phone will reboot/erase I believe, and then end up back to the "lets get started" screen.
- after you setup your phone, you can go back into the developers menu to turn off the oem unlocking
The above steps pretty much follow essentials instructions. (the essential instructions don't give some specifics.)
You are all done. (I recommend you review my instructions and the essential instructions carefully, don't copy paste commands as I may have spelled something wrong, etc.. Just wanted to give you a flow of the process.)

I was following those directions, but what happens is that though the phone appears as a device in adb before rebooting, once I reboot into fastboot mode, it is no longer listed. I also noticed that when tried to reboot the phone into bootloader mode with an adb command, instead, it did a regular reboot, and when it did that reboot, it again was no longer listed as a device, because it went into charging mode. So I'm not sure how to keep this from happening.

maltydog said:
I was following those directions, but what happens is that though the phone appears as a device in adb before rebooting, once I reboot into fastboot mode, it is no longer listed. I also noticed that when tried to reboot the phone into bootloader mode with an adb command, instead, it did a regular reboot, and when it did that reboot, it again was no longer listed as a device, because it went into charging mode. So I'm not sure how to keep this from happening.
Click to expand...
Click to collapse
The reason why the adb command (to go into bootloader mode) didn't work is it is broken when you installed Oreo, that is why you need to do it manually.
When you put your phone into fastboot mode (power button / volume down) plug in your phone into your computer, and from command prompt (make sure you are in the adb folder), type fastboot devices (don't type adb devices) and see if anything replies back.

kbonnel said:
The reason why the adb command (to go into bootloader mode) didn't work is it is broken when you installed Oreo, that is why you need to do it manually.
When you put your phone into fastboot mode (power button / volume down) plug in your phone into your computer, and from command prompt (make sure you are in the adb folder), type fastboot devices (don't type adb devices) and see if anything replies back.
Click to expand...
Click to collapse
Thanks, I understand now. I can't start this tonight, but I will try the again next time I have time at the desktop.

You are probably missing the phone's driver. Download this, Essential device driver for Windows machines. Supports 32/64 bit on Windows 7, 8 and 10., from the essential developer site and install it.

damn it, I read somewhere that there are problems while using adb on the current official beta. There was a command for getting connection again. But I can't find it right now.
Just to be clear. when the phone is on, you enabled USB debugging and plugged in the USB cable and checked the tickbox before you granted debugging access, right? If you don't check the box, there is no access granted after a phone reboot.
take care, I had problems getting through the initial phone setup after I did a factory reset. The Oreo beta still has some hickups. I got it to work after a few reboots. Without finishing the intial phone setup you can't enable USB debugging, you know.

emowing said:
You are probably missing the phone's driver. Download this, Essential device driver for Windows machines. Supports 32/64 bit on Windows 7, 8 and 10., from the essential developer site and install it.
Click to expand...
Click to collapse
Good point on the driver, I wasn't even thinking about that.

Well, my phone was being read when I previously sideloaded updates, so I think I have the right drivers, but I will double check. Can anyone suggest why the phone keeps defaulting to charging mode rather than file transfer every time I reboot it?

maltydog said:
Well, my phone was being read when I previously sideloaded updates, so I think I have the right drivers, but I will double check. Can anyone suggest why the phone keeps defaulting to charging mode rather than file transfer every time I reboot it?
Click to expand...
Click to collapse
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?

iceman#1 said:
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
Click to expand...
Click to collapse
Yes.

iceman#1 said:
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
Click to expand...
Click to collapse
Yes, I did, thanks.

F
iceman#1 said:
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
Click to expand...
Click to collapse
Yes, I did, thanks. Trying to reply and it doesn't appear. Edit: Sorry for the multiple posts,they all appeared at once.

Okay, I am back to this now, I had time today. I installed the windows drivers from the Essential site (I am running Windows 10 64 bit) and the device was recognized in fastboot devices. The phone wiped my data and restarted with a setup screen. So far, so good. So I shut down the phone again, turned it on again in fastboot mode, it was unlocked. I went into a CMD screen and typed fastboot devices, and the phone was still listed there. So I opened windows explorer and got to the folder where I had unpacked the image files and also copied the flashboot file. I right-clicked the flashall.bat file, chose run as administrator. When I did this, I got a bunch of error messages that went by so fast, they were practically impossible to read, though they seem to say something about files not found. I didn't see any log file in the folder, so I guess they are not created. I went back to the Essential site and downloaded the zip file with the correct image files again and tried a second time, with the same results. Anyway I have wiped my phone, but still have not reinstalled the Sprint nougat software I need on this phone. Any other suggestions?

Okay, I tried again, and I was able to read the error message. They all said cannot load "filename" no such file or directory. It sounds like some kind of path error, right? I expanded the file from the Essential download for build Build NMI81C into their own directory, a subdirectory of a library where I have been keeping various android files, and I copied the flashboot file into the same directory from the platform-tools download, but only that file. That seems to be what instructions specify.
Also, I notice on this thread https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681/page3 it mentions also using the command "fastboot flashing unlock_critical" but I do not see that elsewhere.

I was able to get flashall to run using the command prompt instead of Windows Explorer. It seemed to run okay, except a couple of items cause me some concern.
I got a message "FAILED (remote: Flashing is not allowed for Critical Partitions)" for the abl.img file.
And the other command "Did you mean to fashboot format this ext4 partition".
Are either of these a problem?

Try running the commands one at a time. Open the flash-all.sh in a text editor and copy the commands.

As I said in my last message, I was able to get Flashall to work when I ran it in the CMD prompt rather than in windows explorer (which is how it was done in the video posted on Youtube, but didn't work for me). My only concern at this point is whether I should be concerned about the two commands posted in the email.
Interestingly enough, my phone did an update to the build NMJ32F as soon as I started it up.

maltydog said:
As I said in my last message, I was able to get Flashall to work when I ran it in the CMD prompt rather than in windows explorer (which is how it was done in the video posted on Youtube, but didn't work for me). My only concern at this point is whether I should be concerned about the two commands posted in the email.
Interestingly enough, my phone did an update to the build NMJ32F as soon as I started it up.
Click to expand...
Click to collapse
Did u not do the flashing unlock_critical?

Airwolf79 said:
Did u not do the flashing unlock_critical?
Click to expand...
Click to collapse
No I didn't. It was not mentioned by anyone but me in this thread until you did.
So far I have received no error messages since I did the reversion to stock. As I said,
I did get an update almost immediately.

Which Root Method?

Ok, I'm planning on rooting, but seeing the same error from both methods:
https://forum.xda-developers.com/on...t-oneplus-6t-using-oneplus-6t-rooter-t3864238
and
https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3860279
I really don't want to run into the issue of the device not booting, or heat problems etc. So could anyone provide their experiences or opinion on which one works best? I have the regular OP6t, not T-Mobile, live in America.

I used the one click tool.. No heating probs, sot of 10 hours, boots allways, no bootloops, stable root.. Perfect.
Only problems with recovery. Flashed recovery, but somehownit wont stick. Have to flash recovery every time i want to use it. But i guess there is no need for twrp at the moment, so im satisfied with only root and the mods available.

They basically all just do the same thing.
I used fastboot manual commands, takes 5 minutes and at least you know what you're doing.
And your thread is not in the proper section, it should be in Q&A one, ask a Mod to move it

When I tried with command prompt, it said "waiting on devices". My apologies, as it's been about 4 years since I've done this with my Nexus 6

First, you disconnect the device and In command pront write the command + enter, after, when you see "waiting on devices" you have to connect the device and it flash your phone.
I did it like that.
phr0zen said:
When I tried with command prompt, it said "waiting on devices". My apologies, as it's been about 4 years since I've done this with my Nexus 6
Click to expand...
Click to collapse
Enviado desde mi ONEPLUS A6013 mediante Tapatalk

Yup, even tried the one-click method, and it hands on "waiting for device". Followed the directions just as they were innthe link and in the readme file. Phone boots into recovery and does nothing. Computer hangs at the command prompt telling me it's waiting. Installed the rooter setup, and when I open that, it says the phone isn't connected.
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
< waiting for device >
*DISREGARD THIS* did not have usb debugging checked after the reboot... the previous still hold true though

phr0zen said:
Yup, even tried the one-click method, and it hands on "waiting for device". Followed the directions just as they were innthe link and in the readme file. Phone boots into recovery and does nothing. Computer hangs at the command prompt telling me it's waiting. Installed the rooter setup, and when I open that, it says the phone isn't connected.
Click to expand...
Click to collapse
For me, the best option is this:
https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789

alfo!!! said:
For me, the best option is this:
https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789
Click to expand...
Click to collapse
OK, tried that one as well, and it's a no-go either. I installed the OnePlus drivers, and already had ADB binaries/drivers (1.4.3) installed, but decided to run the install again to make sure they were updated.
After this, I booted into fastboot and plugged my phone in the computer. I opened a command prompt and ran "fastboot devices" which returned negative results... it did not recognize my serial number, which indicate the drivers were not installed correctly.
How can they not be installed correctly when I ran it as device administrator?

are you sure that have you doing this step?
"Show File Extensions
Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files."
If it does not work well, I would change PC

alfo!!! said:
are you sure that have you doing this step?
"Show File Extensions
Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files."
If it does not work well, I would change PC
Click to expand...
Click to collapse
Yes, I did that.
Running "fastboot" comes up with all the options, as well as running "adb". Running "fastboot devices" does not show anything though. Unfortunately this is my only computer, which is a windows surface pro. Other laptop got the cord chewed by a hungry dog
I'm open to other options, but it sounds like maybe this computer doesn't play well.

Hi, if you're still looking for solutions.. I followed the first link (one with the rooter application). Peacefully rooted my phone. Didn't check much with recovery and all, but my phone is rooted and I'm able to use root applications and mods.

phr0zen said:
Yes, I did that.
Running "fastboot" comes up with all the options, as well as running "adb". Running "fastboot devices" does not show anything though. Unfortunately this is my only computer, which is a windows surface pro. Other laptop got the cord chewed by a hungry dog
I'm open to other options, but it sounds like maybe this computer doesn't play well.
Click to expand...
Click to collapse
If "fastboot devices" doesn't show a device, your system is not recognizing the device as a fastboot device. Check device manager. You can unplug and re-plug the device with device manager open to see what device your system sees it as and "update driver" that way or simply delete device selecting "delete device software" to completely remove. Re-plug the phone and hopefully it automatically installs with the proper drivers. Otherwise you have to do the "update drive" method to manually select the fastboot driver.
As for ADB, "adb devices" should also show your device listed. Won't show unless debugging is enabled and you can't interact with it unless you authorize the system on the phone. This will happen if you simply run the "adb devices" command while phone is connected with debugging enabled. If still not showing up with debugging enabled, you may have to use same method specified for fastboot above.

I booted into twrp. Enabled adb sideload and then just sideloaded the magisk zip.
Then I booted the phone, installed magisk manager and I was done.
Sent from my ONEPLUS A6013 using Tapatalk

hartleyshc said:
I booted into twrp. Enabled adb sideload and then just sideloaded the magisk zip.
Then I booted the phone, installed magisk manager and I was done.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
This and instead of sideload, you connect a flash drive and install the zips from TWRP.

phr0zen said:
Yup, even tried the one-click method, and it hands on "waiting for device". Followed the directions just as they were innthe link and in the readme file. Phone boots into recovery and does nothing. Computer hangs at the command prompt telling me it's waiting. Installed the rooter setup, and when I open that, it says the phone isn't connected.
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
< waiting for device >
*DISREGARD THIS* did not have usb debugging checked after the reboot... the previous still hold true though
Click to expand...
Click to collapse
is there a way to root the phone and apps like snapchat work?

Popsicle toast said:
is there a way to root the phone and apps like snapchat work?
Click to expand...
Click to collapse
Yes. Use magisk hide to hide root from the Snapchat application

Pain-N-Panic said:
Yes. Use magisk hide to hide root from the Snapchat application
Click to expand...
Click to collapse
im asking cuz i heard magisk hide dosent work on the 6t yet. im using v17.3.

Popsicle toast said:
im asking cuz i heard magisk hide dosent work on the 6t yet. im using v17.3.
Click to expand...
Click to collapse
Ah, I don't have the phone yet so I can't confirm

duvee said:
I used the one click tool.. No heating probs, sot of 10 hours, boots allways, no bootloops, stable root.. Perfect.
Only problems with recovery. Flashed recovery, but somehownit wont stick. Have to flash recovery every time i want to use it. But i guess there is no need for twrp at the moment, so im satisfied with only root and the mods available.
Click to expand...
Click to collapse
What was your screen on time before you rooted? Or did you rooted straight away?
What changes did you make after root to get 10 hours sot? Did you change the kernel?
Sorry for all the questions. I'm looking to root to get better sot but haven't done anything like this since the Nexus 5/6

Popsicle toast said:
im asking cuz i heard magisk hide dosent work on the 6t yet. im using v17.3.
Click to expand...
Click to collapse
All is working as intended, don't listen to 'people'. I have snapshat working without even using specific hiding option in magisk.

Magisk attempt gone horribly wrong on Pixel 3a, haven't found the answer

So I tried to root my Pixel 3a, long story short it went into a boot loop, I got it back into fastboot mode, but now my pc can't see it. when using "adb devices" search comes up with zilch. when plugged into the pc it knows it's plugged in but I can't see it. Has anyone else seen this, or possibly know a way to at least get me to where I can flash the stock image on?

jedivulcan said:
You have to use "fastboot" commands in fastboot mode. Like ... "fastboot reboot bootloader" or "fastboot boot namearecovery.img" ... You might be able to boot into TWRP recovery and flash the Magisk uninstaller.
Click to expand...
Click to collapse
call me noob or insane, but it wasn't working, but then I typed that in and it rebooted into fastboot. Off to try to follow these steps and hopefully get this thing working again.

tcshaddix said:
call me noob or insane, but it wasn't working, but then I typed that in and it rebooted into fastboot. Off to try to follow these steps and hopefully get this thing working again.
Click to expand...
Click to collapse
It wasn't working because you were trying to use adb commands while in fastboot.

tcshaddix said:
So I tried to root my Pixel 3a, long story short it went into a boot loop, I got it back into fastboot mode, but now my pc can't see it. when using "adb devices" search comes up with zilch. when plugged into the pc it knows it's plugged in but I can't see it. Has anyone else seen this, or possibly know a way to at least get me to where I can flash the stock image on?
Click to expand...
Click to collapse
Should've checked connected devices when in bootloader mode:
fastboot devices

trouble with unlocking my bootloader

hey guys,
i just got my 8 pro in the mail, and need to unlock my bootloader. i turned on usb debugging, installed the usb drivers on my pc, and the platform tools.
i pulled up this guide to help: https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-unlocking-bootloader-rooting-t4151823
this is indeed an EU model
im able to run .\ adb devices, and see my device
then, after running .\ adb reboot boatloader, i reach a screen where i am given three language options, and my device shows up under .\fastboot devices
after running .\fastboot unlock oem, i get this message
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
PS C:\Users\FPSReach\Downloads\platform-tools_r30.0.5-windows\platform-tools>
does anyone have any idea what i can do?
sorry if this has been covered before, i did some light searching but really couldnt understand much

FPSReach said:
hey guys,
i just got my 8 pro in the mail, and need to unlock my bootloader. i turned on usb debugging, installed the usb drivers on my pc, and the platform tools.
i pulled up this guide to help: https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-unlocking-bootloader-rooting-t4151823
this is indeed an EU model
im able to run .\ adb devices, and see my device
then, after running .\ adb reboot boatloader, i reach a screen where i am given three language options, and my device shows up under .\fastboot devices
after running .\fastboot unlock oem, i get this message
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
PS C:\Users\FPSReach\Downloads\platform-tools_r30.0.5-windows\platform-tools>
does anyone have any idea what i can do?
sorry if this has been covered before, i did some light searching but really couldnt understand much
Click to expand...
Click to collapse
Shouldn't it be "fastboot oem unlock"?

Yes, that's correct "fastboot oem unlock"

Just follow my guide bud
https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-unlocking-bootloader-rooting-t4151823
Easy step by step

Kollachi said:
Shouldn't it be "fastboot oem unlock"?
Click to expand...
Click to collapse
Yes, my bad, i typed it wrong on here
Just to make sure, i gave it another go right now and got the same " Unable to open fastboot HAL" message

dladz said:
Just follow my guide bud
https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-unlocking-bootloader-rooting-t4151823
Easy step by step
Click to expand...
Click to collapse
Hi sir
You guide is actually the one i found for this
After performing step 3, and reaching the screen with a green START above it, my device no longer responds to fastboot commands, and does not show up after i enter .\fastboot devices (i do still see "fastboot mode" in red text though, weirdly enough)
The only time that my device shows up after entering .\fastboot devices is at the start of step 3, on the language selection screen
What do i do to fix this?

FPSReach said:
Hi sir
You guide is actually the one i found for this
After performing step 3, and reaching the screen with a green START above it, my device no longer responds to fastboot commands, and does not show up after i enter .\fastboot devices (i do still see "fastboot mode" in red text though, weirdly enough)
The only time that my device shows up after entering .\fastboot devices is at the start of step 3, on the language selection screen
What do i do to fix this?
Click to expand...
Click to collapse
? Never had that issue myself. The steps are taken from verified sources and I ran through it myself when I unlocked mine, no one else has said this.
Potentially a driver issue, you using Windows 10 ? Usb 2 or 3? Sometimes people have issues with 3, 2 seems to work for them..
It's been a while since I was on that screen...but the process should be as written.
See if fastboot mode is an option in the start screen (after you've used the ADB reboot bootloader command)

dladz said:
? Never had that issue myself. The steps are taken from verified sources and I ran through it myself when I unlocked mine, no one else has said this.
Potentially a driver issue, you using Windows 10 ? Usb 2 or 3? Sometimes people have issues with 3, 2 seems to work for them..
It's been a while since I was on that screen...but the process should be as written.
See if fastboot mode is an option in the start screen (after you've used the ADB reboot bootloader command)
Click to expand...
Click to collapse
I am on windows 10 and downloaded the usb drivers for the 8 pro beforehand. I just tried again with a usb 2 port, the results are the same.
After using the .\adb reboot bootloader command, my phone screen says "fastboot mode" with the green "start" on top (i just took a pic, to confirm, this is my screen https://imgur.com/tduDZsz ) but at this stage my phone is no longer detected and does not show up under .\fastboot devices or .\adb devices
just for funsies, i downloaded an third party app on my pc called reiboot to get me into fastboot mode
again, it got my phone to this same screen and then said it "failed to enter fastboot" and could no longer detect my phone
this is a brand new model too, a european one, i made this thread within a couple hours of it coming

dladz said:
? Never had that issue myself. The steps are taken from verified sources and I ran through it myself when I unlocked mine, no one else has said this.
Potentially a driver issue, you using Windows 10 ? Usb 2 or 3? Sometimes people have issues with 3, 2 seems to work for them..
It's been a while since I was on that screen...but the process should be as written.
See if fastboot mode is an option in the start screen (after you've used the ADB reboot bootloader command)
Click to expand...
Click to collapse
....oh my god.
I am so sorry, the mistake was on my end.
I followed the instructions meticulously, don't get me wrong.
In a last ditch attempt though, I repeated the process on my old windows 7 laptop with a command prompt
It worked. Im sorry to have disturbed you over this.
If anyone else ever finds this thread while looking for answers, use another computer, i should have tried that earlier.

FPSReach said:
....oh my god.
I am so sorry, the mistake was on my end.
I followed the instructions meticulously, don't get me wrong.
In a last ditch attempt though, I repeated the process on my old windows 7 laptop with a command prompt
It worked. Im sorry to have disturbed you over this.
If anyone else ever finds this thread while looking for answers, use another computer, i should have tried that earlier.
Click to expand...
Click to collapse
So it was a driver issue. Because I did it with Win10 and USB 3.

Kollachi said:
So it was a driver issue. Because I did it with Win10 and USB 3.
Click to expand...
Click to collapse
It probably was, i have no idea what else it could be, honestly

FPSReach said:
....oh my god.
I am so sorry, the mistake was on my end.
I followed the instructions meticulously, don't get me wrong.
In a last ditch attempt though, I repeated the process on my old windows 7 laptop with a command prompt
It worked. Im sorry to have disturbed you over this.
If anyone else ever finds this thread while looking for answers, use another computer, i should have tried that earlier.
Click to expand...
Click to collapse
Yep windows 7 has caused issues in the past, shame really as it's still got it's uses as an OS.
Glad you're sorted.
---------- Post added at 05:46 PM ---------- Previous post was at 05:45 PM ----------
Kollachi said:
So it was a driver issue. Because I did it with Win10 and USB 3.
Click to expand...
Click to collapse
That's correct as 7 chooses the wrong one. Don't think the 10 driver would work.
Haven't looked into it.

dladz said:
Yep windows 7 has caused issues in the past, shame really as it's still got it's uses as an OS.
Glad you're sorted.
---------- Post added at 05:46 PM ---------- Previous post was at 05:45 PM ----------
That's correct as 7 chooses the wrong one. Don't think the 10 driver would work.
Haven't looked into it.
Click to expand...
Click to collapse
Driver issue is sometimes hard to figure out.