Related
Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.
looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.
Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......
Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.
You need the drivers.
albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.
the same issue for me. is there any working solution for that?
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing
Hey guys, I really need some help here, I'm not good at any of this stuff - my OPO just randomly got stuck on a boot loop, I have never played with the USB debugging or any of that or tried to flash anything else, I was using just stock cyanogen.
I've been reading around and I've downloaded all the drivers but still can't detect the device when I do the Shift + Right Click --> Run CMD "fastboot devices" or "adb devices".
I never enabled options such as the USB debugging or anything else, can someone please help me out? I'm really clueless to all of this stuff.
You must first put your phone in fastboot mode.
To put your phone in fastboot mode, turn it off, and then hold power+volume down until you get a screen with only the cyanogenmod logo. If you get to this screen, you're in fastboot mode. If you have installed the proper drivers in your computer, you should be able to connect to the phone from your computer. Connect your usb cable to the phone and the computer, open a dos box and type "fastboot devices". If you get a series of letters and numbers then you're OK.
jchen221 said:
Hey guys, I really need some help here, I'm not good at any of this stuff - my OPO just randomly got stuck on a boot loop, I have never played with the USB debugging or any of that or tried to flash anything else, I was using just stock cyanogen.
I've been reading around and I've downloaded all the drivers but still can't detect the device when I do the Shift + Right Click --> Run CMD "fastboot devices" or "adb devices".
I never enabled options such as the USB debugging or anything else, can someone please help me out? I'm really clueless to all of this stuff.
Click to expand...
Click to collapse
joanquro said:
You must first put your phone in fastboot mode.
To put your phone in fastboot mode, turn it off, and then hold power+volume down until you get a screen with only the cyanogenmod logo. If you get to this screen, you're in fastboot mode. If you have installed the proper drivers in your computer, you should be able to connect to the phone from your computer. Connect your usb cable to the phone and the computer, open a dos box and type "fastboot devices". If you get a series of letters and numbers then you're OK.
Click to expand...
Click to collapse
This, except that's the wrong button combo (power + volume down is for recovery). Use power + volume up to get to fastboot mode and then try the "fastboot devices" command.
Heisenberg said:
This, except that's the wrong button combo (power + volume down is for recovery). Use power + volume up to get to fastboot mode and then try the "fastboot devices" command.
Click to expand...
Click to collapse
I'm sorry for this mistake.
joanquro said:
You must first put your phone in fastboot mode.
To put your phone in fastboot mode, turn it off, and then hold power+volume down until you get a screen with only the cyanogenmod logo. If you get to this screen, you're in fastboot mode. If you have installed the proper drivers in your computer, you should be able to connect to the phone from your computer. Connect your usb cable to the phone and the computer, open a dos box and type "fastboot devices". If you get a series of letters and numbers then you're OK.
Click to expand...
Click to collapse
Thanks for your advice. This is the big problem I'm having, I've downloaded the SDK slim, and the driver manager and the 15 second installer things and installed all of them but still can't manage to detect my phone on fastboot.
jchen221 said:
Thanks for your advice. This is the big problem I'm having, I've downloaded the SDK slim, and the driver manager and the 15 second installer things and installed all of them but still can't manage to detect my phone on fastboot.
Click to expand...
Click to collapse
What command are you using while in fastboot mode?
Heisenberg said:
What command are you using while in fastboot mode?
Click to expand...
Click to collapse
I'm using both
fastboot devices
adb devices
Fastboot devices comes back with nothing in the CMD box, ADB devices gives a message that says 'Devices:' but there are none listed.
jchen221 said:
I'm using both
fastboot devices
adb devices
Fastboot devices comes back with nothing in the CMD box, ADB devices gives a message that says 'Devices:' but there are none listed.
Click to expand...
Click to collapse
There's no point in using adb commands in fastboot because only fastboot commands work. What drivers do you have installed?
XDA Moderator
Transmitted via Bacon
Heisenberg said:
There's no point in using adb commands in fastboot because only fastboot commands work. What drivers do you have installed?
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
I've looked around for all sorts of drivers, I have the universal ADB, android SDK slim or something, is there a specific one I need?
jchen221 said:
I've looked around for all sorts of drivers, I have the universal ADB, android SDK slim or something, is there a specific one I need?
Click to expand...
Click to collapse
Uninstall whatever drivers you have installed, reboot your PC, install these drivers, reboot your PC, connect your phone, test fastboot (fastboot devices).
Heisenberg said:
Uninstall whatever drivers you have installed, reboot your PC, install , reboot your PC, connect your phone, test fastboot (fastboot devices).
Click to expand...
Click to collapse
I tried that, but again no response in CMD when I type fastboot devices.
Although I just tried and am able to boot into recovery mode, would I be able to do some sort of factory reset there? I've already tried to wipe user data but I'm still getting a bootloop there.
jchen221 said:
I tried that, but again no response in CMD when I type fastboot devices.
Although I just tried and am able to boot into recovery mode, would I be able to do some sort of factory reset there? I've already tried to wipe user data but I'm still getting a bootloop there.
Click to expand...
Click to collapse
I can't remember what capabilities the stock recovery has, but if it's there it's worth trying.
jchen221 said:
I tried that, but again no response in CMD when I type fastboot devices.
Although I just tried and am able to boot into recovery mode, would I be able to do some sort of factory reset there? I've already tried to wipe user data but I'm still getting a bootloop there.
Click to expand...
Click to collapse
Heisenberg said:
I can't remember what capabilities the stock recovery has, but if it's there it's worth trying.
Click to expand...
Click to collapse
I managed to get it to work after resetting a bunch of the options, thanks so much for your help with this (even if I didn't get it to fastboot mode)
I have the same problem.
jchen221 said:
I managed to get it to work after resetting a bunch of the options, thanks so much for your help with this (even if I didn't get it to fastboot mode)
Click to expand...
Click to collapse
Hey bro, I have the same problem. Can you please explain me how did you resolve it? This would be of great help. Thanks.
pavanakshay said:
Hey bro, I have the same problem. Can you please explain me how did you resolve it? This would be of great help. Thanks.
Click to expand...
Click to collapse
for me too bro same problem please help me
---------- Post added at 08:28 AM ---------- Previous post was at 08:25 AM ----------
Heisenberg said:
Uninstall whatever drivers you have installed, reboot your PC, install these drivers, reboot your PC, connect your phone, test fastboot (fastboot devices).
Click to expand...
Click to collapse
i too having the same problem bro the driver link is not working please send me the link thankyou in advance
i am also facing the same problem that phone loops into fast boot mode whenever turned on i do totally every kind of drivers softwares and etc like tenorshare but all in vain i guess at last that phone must be enabled usb debuging in order to be detected as a active adb device,i pratically do this stuff by using another phone with enabled debuging and it was an active device andd can be processed further but when i disabled the usb debugging of same phone it was not working with adb interface i hope you understand,,,,but a miracle happenend i removed the battery for about a week and suddenly i pluged and try to turn it on hola it starts from roms boot logo
HELP!!!!! Stuck on bootloop and fastboot not working
i was flashing twrp on infinix s4 withfast boot. after flashing the device is stuck on bootloop. the recovery is not accessible (i press the key combo nothing happens) and fastboot combination is also not working. i tried connecting it with adb cmd and ran the command "adb reboot bootloader" but no device is detected.
ps: the link for drivers is broken
Hello. Im trying to unlock bootloader on my wifes phone. All adb commands works. After I type adb reboot bootloader phone goes to fastboot mode and thats ok. But after I type fastboot devices nothing is happening. How can I fix it?
Gedablo666 said:
Hello. Im trying to unlock bootloader on my wifes phone. All adb commands works. After I type adb reboot bootloader phone goes to fastboot mode and thats ok. But after I type fastboot devices nothing is happening. How can I fix it?
Click to expand...
Click to collapse
it is a problem of s1 boot device driver . i even tried diabling driver signature on my win10 like every post suggested but no luck . i'm also trying to get over it
disable driver signature in win 10 and when windows boots go to device manager and update driver of s1 boot device from the files of given link
https://dl.xda-developers.com/4/0/0....zip?key=oeHhoI_uttjO0gP6y4vAiA&ts=1526629864
usb debugging is enabled on device. running latest version of adb, fastboot. Have tried on both mac and win10 but same issue on both.
Oneplus 7 pro is running 10.3.0GM21AA
>fastboot devices
>adb devices
List of devices attached
966c8016 device
Trying to use fastboot to flash patched magisk img and install magisk.
Do you enter in fastboot in phone?
Sent from my GM1910 using Tapatalk
Yes tried from bootloader as well
fustyler said:
Yes tried from bootloader as well
Click to expand...
Click to collapse
bootloader-fastboot mode is the only time fastboot commands will work. I know you tried this "also". But I feel you are wasting your time trying to run fastboot when phone is booted (instead of focusing on the situation where fastboot should actually be working). adb and fastboot will not work at the same time by definition. Also, debugging does not need to be enabled for fastboot (only for adb).
redpoint73 said:
bootloader-fastboot mode is the only time fastboot commands will work. I know you tried this "also". But I feel you are wasting your time trying to run fastboot when phone is booted (instead of focusing on the situation where fastboot should actually be working). adb and fastboot will not work at the same time by definition. Also, debugging does not need to be enabled for fastboot (only for adb).
Click to expand...
Click to collapse
I have tried it from bootloader and still the same on my pc it just says waiting for device.
What else can I try?
fustyler said:
I have tried it from bootloader and still the same on my pc it just says waiting for device.
What else can I try?
Click to expand...
Click to collapse
Try a different cable, different USB port. Fastboot can be finicky sometimes. You can also go to Windows Device Manager, find the device, and see if you can manually select the drivers. There is a generic Android device driver that sometimes gets fastboot to work properly on some of my past devices. This is on Windows 7, haven't done this on WIn 10 yet, so not sure if it is exactly the same.
redpoint73 said:
Try a different cable, different USB port. Fastboot can be finicky sometimes. You can also go to Windows Device Manager, find the device, and see if you can manually select the drivers. There is a generic Android device driver that sometimes gets fastboot to work properly on some of my past devices. This is on Windows 7, haven't done this on WIn 10 yet, so not sure if it is exactly the same.
Click to expand...
Click to collapse
Have tried different cables and different machines both pc and mac
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Since adb is working, do an adb reboot bootloader and it'll then boot into fastboot. If you can't get a return on fastboot devices at this point, it could be you haven't oem unlocked your phone yet.
mnemesis said:
Since adb is working, do an adb reboot bootloader and it'll then boot into fastboot. If you can't get a return on fastboot devices at this point, it could be you haven't oem unlocked your phone yet.
Click to expand...
Click to collapse
I ran adb reboot bootloader from pc to boot phone into fastboot.
In the bootloader it states device state is unlocked
However fastboot devices ran from pc still shows no device.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
Thanks this fixed it.
Issue fixed by billyt1's comment above. case closed.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
This worked for me as well. Just to make it clear, rephrasing his reply. After disabling signature verification on windows 10, connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device.If it is found, This means Windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.
Giri Prasad said:
This worked for me as well. Just to make it clear, rephrasing his reply. After disabling signature verification on windows 10, connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device.If it is found, This means Windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.
Click to expand...
Click to collapse
ugh. I've tried all of these suggestions and still can't get the device listed in adb while in fastboot.
I even used the TOOL ALL IN ONE without success. Funny thing is, that program recognizes my phone being in fastboot and has it listed. But if I try to flash a recovery from there, it opens a command window and ultimately says there was an error in connecting to the device.
Any help is appreciated.
I have a similar problem. I tried to disable the signature. Installed a new Redmi Note 7 driver. The phone is recognized as an Android phone in the device manager. In Orangefox recovery it is recognized with ADB command. In fastboot it is not recognized. In Orangefox I can't format data. So my ROM is not booting up. So I want to flash fastboot ROM with Fastboot but in Fastboot device is not even recognized.
t
puyow18 said:
ugh. I've tried all of these suggestions and still can't get the device listed in adb while in fastboot.
I even used the TOOL ALL IN ONE without success. Funny thing is, that program recognizes my phone being in fastboot and has it listed. But if I try to flash a recovery from there, it opens a command window and ultimately says there was an error in connecting to the device.
Any help is appreciated.
Click to expand...
Click to collapse
Sorry on the late reply. Pretty sure you can only do fastboot boot boot(recovery).img or\and boot_a or boot_b. Wont let you fastboot flash boot.img.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
Thank you so much!
I also had same issue. my redmi note 6 pro and asus zenfone max pro m1 can be detected in adb but not in fastboot. tried everything. changing driver/disble signature verification. also tried virtual box ubuntu/window 7. but not succeeded. It is actually an issue with usb 3. so I bought usb 2 hub. now everything works fine.
Thank you Thank you Thank you Thank you Thank you Thank you...I have been fooling with this all day
Hi, I already solved this issue (but this only works for xiaomi phone (Redmi Note 7 to be specified), for other brands I think need to download your devices flasher/driver tool)
For Xiaomi user only
1. Download Mi Unlock Tool (https://mi-globe.com/download-xiaomi-mi-unlock-tool-all-versions/) (Version 4.5.813.51)
2. Extract the files anywhere you like
3. Run MiUsbDriver.exe to install the driver
4. Try fastboot devices command
I hope this helps you guys. The Mi Unlock Tool also useful to unlock device locked bootloader.
For other devices maybe can follow this tutorial
Fixed: Fastboot not detecting your Android device
Fix the Fastboot not detecting your device. If your device is not detected by the Fastboot then these tricks will really help you.
www.qasimtricks.com
searching all over the internet on how get my computer to recognize my device in fastboot..
I already had universal adb drivers installed, along with android studio.. so adb worked out of the box. I tried to root, got to where I need to unlock the bootloader but no fastboot..
Tried reinstalling universal adb drivers, also tried a few other downloads from google with no luck on anything..
Searching the forums it seems like fastboot 'just works' for everyone else, so maybe something on my computer is messed up..idk
device manager just shows 'unknown android device'
my phone is oneplus 9 unlocked version, model LE2115
any help is appreciated
cass89 said:
searching all over the internet on how get my computer to recognize my device in fastboot..
I already had universal adb drivers installed, along with android studio.. so adb worked out of the box. I tried to root, got to where I need to unlock the bootloader but no fastboot..
Tried reinstalling universal adb drivers, also tried a few other downloads from google with no luck on anything..
Searching the forums it seems like fastboot 'just works' for everyone else, so maybe something on my computer is messed up..idk
device manager just shows 'unknown android device'
my phone is oneplus 9 unlocked version, model LE2115
any help is appreciated
Click to expand...
Click to collapse
I had the same issue with my op9 unlocking bl.
ADB and Fastboot 29.0.2.zip | by evildog1 for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Use these and open your command window from this . Makes a shortcut on your desktop. I did and unlocking bl worked perfectly.
cass89 said:
searching all over the internet on how get my computer to recognize my device in fastboot..
I already had universal adb drivers installed, along with android studio.. so adb worked out of the box. I tried to root, got to where I need to unlock the bootloader but no fastboot..
Tried reinstalling universal adb drivers, also tried a few other downloads from google with no luck on anything..
Searching the forums it seems like fastboot 'just works' for everyone else, so maybe something on my computer is messed up..idk
device manager just shows 'unknown android device'
my phone is oneplus 9 unlocked version, model LE2115
any help is appreciated
Click to expand...
Click to collapse
Double post
ok now I'm confused.. those drivers didn't work. following the root guide on here it says 'unlock the usual way''boot to bootloader''issue command 'fastboot flashing unlock''
so I decided to try rebooting to fastboot instead, which brought me to fastbootd
fastboot does recognize fastbootd, but the unlock command "flashing unlock" is unrecognized
So do I use bootloader or fastbootd to issue the unlock command?
if the latter, why would fastbootd not recognize the command?
the 'oem unlock' option is ticked on...
cass89 said:
ok now I'm confused.. those drivers didn't work. following the root guide on here it says 'unlock the usual way''boot to bootloader''issue command 'fastboot flashing unlock''
so I decided to try rebooting to fastboot instead, which brought me to fastbootd
fastboot does recognize fastbootd, but the unlock command "flashing unlock" is unrecognized
So do I use bootloader or fastbootd to issue the unlock command?
if the latter, why would fastbootd not recognize the command?
the 'oem unlock' option is ticked on...
Click to expand...
Click to collapse
Make sure you enable oem unlocking in dev options first and reboot.Reboot to bootloader,issue command $fastboot flashing unlock..
cass89 said:
ok now I'm confused.. those drivers didn't work. following the root guide on here it says 'unlock the usual way''boot to bootloader''issue command 'fastboot flashing unlock''
so I decided to try rebooting to fastboot instead, which brought me to fastbootd
fastboot does recognize fastbootd, but the unlock command "flashing unlock" is unrecognized
So do I use bootloader or fastbootd to issue the unlock command?
if the latter, why would fastbootd not recognize the command?
the 'oem unlock' option is ticked on...
Click to expand...
Click to collapse
Are you a carrier variant or global unlocked 9/9pro?
OEM unlocking is enabled, reboot to bootloader, command 'fastboot devices' shows no devices
Still have unknown android device in device manager
It's a global unlocked 9
cass89 said:
OEM unlocking is enabled, reboot to bootloader, command 'fastboot devices' shows no devices
Still have unknown android device in device manager
It's a global unlocked 9
Click to expand...
Click to collapse
Did you create a shortcut to those adb driver's when you installed; on desktop. And open cmd window in that spot. ?
mattie_49 said:
Did you create a shortcut to those adb driver's when you installed; on desktop. And open cmd window in that spot. ?
Click to expand...
Click to collapse
I'm not sure what you mean by shortcut
I unzipped the file to my desktop, then tried installing driver through device manager, but no driver was found.. I then tried installing the driver with the "DPInst_x64.exe" file, but it says install failed with no other explanation
I tried just opening a command prompt in that folder, but with no driver installed, it still isn't recognized
Thanks for helping, I'm lost at this point lol
cass89 said:
I'm not sure what you mean by shortcut
I unzipped the file to my desktop, then tried installing driver through device manager, but no driver was found.. I then tried installing the driver with the "DPInst_x64.exe" file, but it says install failed with no other explanation
I tried just opening a command prompt in that folder, but with no driver installed, it still isn't recognized
Thanks for helping, I'm lost at this point lol
minimal_adb_fastboot_v1.4.3_setup.exe | by shimp208 for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
Try one more thing. Install these and creat shortcut on desktop and try opening cmd in this. We gonna get you unlocked.
One last thing. You have also went into developer options and tic'ed "USB debugging on then ok on device when it asks if you wanna allow phone to communicate.
tried that, still nothing. usb debugging is on.
all I need is a working driver, everything else should be good..
one thing which i'm not sure if it's an issue, I'm using an old usb c to usb 2 cable, I'm not using the cable that came with the phone because my computer doesn't have usb c ports.. but adb and mass storage/file transfers work with no issue
Hate to say it, but it still COULD be your old USB cord even with file transfer and adb functionality preserved. I had a cord that did do file transfer but not adb. You should try another cord...
Here's another driver source to download:
Universal ADB Drivers
2 new cords, and also tried multiple driver downloads, but still nothing... i was really hoping to root this phone and it seemed so easy for everyone else, thats why i bought it.. but I guess I'm stuck with a locked bootloader...
I could try factory resetting windows or the phone, but would that even make a difference?
..rereading the root guide, at the beginning it says "if you're on global and want root, flash the eu boot.img" but I'm not sure if he means do that first or use that for the guide.. I'm assuming I need the bootloader unlocked in order to flash it first, but maybe not..
..also should I have just commented in the root guide post, instead of making a new post?..
I'm sure you've tried another usb port on your computer.
Last thing to try: another PC.
Shouldn't come to that, but that's where you look to be.
Got it!! Someone posted about the op6 not working either and the fix is turning off windows driver signature, not sure why but that worked for me..
Thanks, now on to root lol
I just had some serious fastboot driver issues when setting up my oneplus. Not sure if this helps but can you at least find the driver folder that was installed on your c:drive when you initially installed the drivers. Then check your device manager when your phone is in fastboot and update the device (usually under portable devices) through that path?
If you get a tampering /corrupt error when you do this you can disable driver signing in windows which is what worked for me thanks to this saint.
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Edit: you solved it while I was responding....I had the same issue..congrats...I know the feeling!