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 so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Are you in the bootloader? (Phone off -> Vol. Up + Power -> fastboot oem lock).
Also, does the command "fastboot devices" show your device?
The USB connector socket at the phone might not make a proper contact with the USB plug. Make sure they connect properly. You may try another cable, or have a look at your USB socket and compare it to another. Check out particularly the little horizontal part in the USB socket.
Make sure you're in bootloader/fastboot mode before attempting to connect in fastboot. Fastboot cannot detect your phone, make sure your udev related settings are appropriate. Check on a Linux PC: https://source.android.com/source/initializing.html Configuring USB Access section.
If after this your phone will not be recognized by fastboot, please post the output of the following command (as root), after seconds after connecting the phone in fastboot mode:
Code:
tail /var/log/messages
Harbb said:
Are you in the bootloader? (Phone off -> Vol. Up + Power -> fastboot oem lock).
Also, does the command "fastboot devices" show your device?
Click to expand...
Click to collapse
fastboot does not show my device. I go into bootloader using adb reboot bootloader because my stupid power button wont work, thats why i want to sent it in to get fixed.
If drivers are properly installed this might not be working because the power button is stuck in or something. Not sure what to try to sort it out if that's the case.
mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
1 - Boot your phone into fastboot mode.
2 - open cmd in your pc.
3 - write: cd \"name of the file where your fastboot is in your pc", and then press enter.
4 - write: fastboot oem lock
5 - press enter and it's done!
bjuderas said:
1 - Boot your phone into fastboot mode.
2 - open cmd in your pc.
3 - write: cd \"name of the file where your fastboot is in your pc", and then press enter.
4 - write: fastboot oem lock
5 - press enter and it's done!
Click to expand...
Click to collapse
if you read the first post it says that fastboot doesnt work
mikeydubbs said:
if you read the first post it says that fastboot doesnt work
Click to expand...
Click to collapse
Sorry, didn't read it right!
And I'm sorry, but I don't know the solution for your problem!
have you tried using a different usb port on your pc?
sent from my dark iced, skanky, t11 infused ns4g
p1gp3n said:
have you tried using a different usb port on your pc?
sent from my dark iced, skanky, t11 infused ns4g
Click to expand...
Click to collapse
yeah i have and i tried using my laptop, and ubuntu 11.10
this sucks so much
i sent my phone in for a broken power button as well. I couldn't even get into the bootloader to relock it so i sent it with an unlocked bootloader. they still fixed it.
shahravi94 said:
i sent my phone in for a broken power button as well. I couldn't even get into the bootloader to relock it so i sent it with an unlocked bootloader. they still fixed it.
Click to expand...
Click to collapse
so do you think as long as its not rooted they wont care?
yup! i flashed a stock image so it was unrooted and sent it in. they fixed it up for me
If you are using Linux you might need su permissions!
Try:
sudo fastboot oem lock
mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
Hi, I know this thread is old but I was having the same problem relocking my nexus 4 after installing stock Android 4.4.3 KitKat.
I'm using Nexus Root Toolkit, I don't know what tools you're using to lock your nexus S boblem ut this very easy to use it downloads the drivers and what ever you need to lock, unlock or flash stock and custom roms for any Nexus device.
So my problem was that I would launch OEM Lock on Nexus Root Toolkit and it would detect the device, reboot in Fastboot mode and it would proceed just fine but after saying "Launching TWRP.... something" it would reboot the phone and say to me "Waiting for device" untill it would time out.
I found out that when the program(NEXUS ROOT TOOLKIT) asked me to download a TWRP IMG files, I said no everytime because I didn't think I'd need it. So after trying 5 times, I allowed it to download it and i retryed to OEM Lock it and MAGIC!
Somewhere in the process of Locking the rom it is going to need the TWRP File so allowing the program to download it solved it for me.
I don't know if this will help you or if you still have the same phone, but if you do have use Nexus Root Toolkit and download all it asks and you'll be fine.
Good Luck.
"waiting for device" forever when "fastboot oem unlock:
mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
I have the same exact problem.
ADB works fine when the phone is up & running, so I am suspecting a driver compatibility problem when the phone is in "FASTBOOT MODE".
I tried to install the "Universal Naked Driver 0.73 (Compatible with Nexus 5, 4, 7, 10 and S)" but Windows 7 64-bit refuses to pick it up. I use the Device Manager method which shows (when the phone is in "FASTBOOT MODE"):
Code:
"Other Devices
> Android 1.0"
When the phone is up & running, Device Manager shows it as:
Code:
"Android USB Devices
> SAMSUNG Android Composite ADB Interface"
Any idea how to proceed from here?
-----
Update: After a day went by, I searched Google some more and found a thread that describes exactly my problem:
http://forum.xda-developers.com/nexus-s/help/nexus-s-root-windows-requests-android-1-t878579
Which led me to:
http://forum.xda-developers.com/nex...oader-nexus-s-t875580/post9861928#post9861928
Which led me to:
http://pdanet.co/a/
I am rushing to try this now...
-------
Success!
~> fastboot oem unlock
...
OKAY [ 18.734s]
finished. total time: 18.734s
Click to expand...
Click to collapse
nunojpg said:
If you are using Linux you might need su permissions!
Try:
sudo fastboot oem lock
Click to expand...
Click to collapse
It helped. Thanks!
mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
Well before trying to Relock the device see whether its connected or not. Type this command fastboot devices and hit enter see whether it shows some no. As in a reply if not that means the deivce isnt connected. If the device is connected type this command to relock your device fastboot oem lock and hit enter. Check on your device screen The Lock status will be changed to LOCKED.
If Helped Click Thanks
---------- Post added at 03:30 PM ---------- Previous post was at 03:27 PM ----------
mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
Well before trying to Relock the device see whether its connected or not. Type this command fastboot devices and hit enter see whether it shows some no. As in a reply if not that means the deivce isnt connected. If the device is connected type this command to relock your device fastboot oem lock and hit enter. Check on your device screen The Lock status will be changed to LOCKED.
If Helped Click Thanks
Two days ago, I unlocked my bootloader and it wiped everything. After that, I installed TWR and rooted the device with a toolkit.
Now I don’t know what went wrong, but I would like to flash CWM recovery instead of TWR, but...
it’s now showing that my bootloader is LOCKED.
And I cannot unlock after I’ve tried using adb, cmd, or the toolkit.
I will hold Vol Up+power to enter fastboot and as soon as I hit “unlock bootloader” or enter “fastboot oem unlock” in command, the phone immediately starts into TWR.
Without an unlocked bootloader, I cannot flash anything via the bootloader.
Any help would be appreciated. Thank you!
Turn the phone completely off. Hold volume up + power, plug the phone in via USB (ensure that you have the drivers installed for the phone)
fastboot oem unlock
fastboot reboot
then go back into volume up + power (fastboot mode)..... fastboot flash recovery <recovery-name>.img while the recovery file is in the fastboot.exe folder. then boot into recovery.
zephiK said:
Turn the phone completely off. Hold volume up + power, plug the phone in via USB (ensure that you have the drivers installed for the phone)
fastboot oem unlock
fastboot reboot
Click to expand...
Click to collapse
You see, I cannot even get to the part where I reboot the phone myself because the phone automically does it for me and jumps itself into TWR recovery and does not unlock the bootloader for me.
It takes less than a second from when i run the command "fastboot oem unlock" to when the phone reboots. Then it take about 15 seconds to get to the TWR recovery.
The only drivers I've installed on my Win8 (tried Win 7 as well) are these:
http://forum.xda-developers.com/showthread.php?t=2588979
Any other drivers I'm missing? I do not want to do download the full SDK.
lemonspeakers said:
You see, I cannot even get to the part where I reboot the phone myself because the phone automically does it for me and jumps itself into TWR recovery and does not unlock the bootloader for me.
It takes less than a second from when i run the command "fastboot oem unlock" to when the phone reboots. Then it take about 15 seconds to get to the TWR recovery.
The only drivers I've installed on my Win8 (tried Win 7 as well) are these:
http://forum.xda-developers.com/showthread.php?t=2588979
Any other drivers I'm missing? I do not want to do download the full SDK.
Click to expand...
Click to collapse
I actually had that happen to me too. When I typed fastboot oem unlock, my phone just instantly rebooted. But the bootloader was still unlocked. Use http://forum.xda-developers.com/showthread.php?t=2788632 and start from scratch. Use Universal Naked Drivers 0.73, they work amazing. I had these drivers installed before so I didn't even need to install drivers.
zephiK said:
I actually had that happen to me too. When I typed fastboot oem unlock, my phone just instantly rebooted. But the bootloader was still unlocked. Use http://forum.xda-developers.com/showthread.php?t=2788632 and start from scratch. Use Universal Naked Drivers 0.73, they work amazing. I had these drivers installed before so I didn't even need to install drivers.
Click to expand...
Click to collapse
I tried your method but I keep restarting to the twrp recovery.
and specific thing that made the device unlock the bootloader. Fastboot OEM unlock just restarts my device
I have the correct drivers the win 7 pc does recognize the device in fastboot mode.
thank you
tkdsl said:
I tried your method but I keep restarting to the twrp recovery.
and specific thing that made the device unlock the bootloader. Fastboot OEM unlock just restarts my device
I have the correct drivers the win 7 pc does recognize the device in fastboot mode.
thank you
Click to expand...
Click to collapse
Silly to ask, but you unchecked the cm update in dev settings and enabled debugging?
Personally, my second lappy didn't even list the device in fastboot, but the commands still worked.
I would just boot into fastboot and run the all the commands in series.
teh roxxorz said:
Silly to ask, but you unchecked the cm update in dev settings and enabled debugging?
Personally, my second lappy didn't even list the device in fastboot, but the commands still worked.
I would just boot into fastboot and run the all the commands in series.
Click to expand...
Click to collapse
I've already tried this on 3 different computers.
I don't see how having dev mode would affect bootloader if I never boot into the OS.
Someone had the same issue and had found a fix. I will give this tampering fix a try:
http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-totally-locked-t2817735
lemonspeakers said:
Two days ago, I unlocked my bootloader and it wiped everything. After that, I installed TWR and rooted the device with a toolkit.
Now I don’t know what went wrong, but I would like to flash CWM recovery instead of TWR, but...
it’s now showing that my bootloader is LOCKED.
And I cannot unlock after I’ve tried using adb, cmd, or the toolkit.
I will hold Vol Up+power to enter fastboot and as soon as I hit “unlock bootloader” or enter “fastboot oem unlock” in command, the phone immediately starts into TWR.
Without an unlocked bootloader, I cannot flash anything via the bootloader.
Any help would be appreciated. Thank you!
Click to expand...
Click to collapse
Hi lemonspeakers,
sadly I don't have a solution, but the same problem.
Current state:
Bootloader locked
TWRP installed
no root
Sending "fastboot oem unlock" causes reboot to recovery.
Besides that the phone is fully working. (My friends thing I'm crazy because I'm sad about a fully working, "normal" phone
I hope somebody have suggestions to fix the issue.
Update:
I've just seen the tamering fix thread and I'm going to try that, too,
Did it work for you?
Dr.Linde said:
Hi lemonspeakers,
sadly I don't have a solution, but the same problem.
Current state:
Bootloader locked
TWRP installed
no root
Sending "fastboot oem unlock" causes reboot to recovery.
Besides that the phone is fully working. (My friends thing I'm crazy because I'm sad about a fully working, "normal" phone
I hope somebody have suggestions to fix the issue.
Update:
I've just seen the tamering fix thread and I'm going to try that, too,
Did it work for you?
Click to expand...
Click to collapse
I haven't tried it because i'm out on vacation for a few days. I didn't want to bring my new oneplus with me.
If you tried that fix, let me know how it went. thanks!
lemonspeakers said:
I haven't tried it because i'm out on vacation for a few days. I didn't want to bring my new oneplus with me.
If you tried that fix, let me know how it went. thanks!
Click to expand...
Click to collapse
Actually, I tried it and... It works!
I flashed the script, than used this guide (again):
http://forum.xda-developers.com/showthread.php?t=2788632
Than it looked like the only improvement is, that the bootloader is now unlocked. Root didn't work.
I could fix that by going to Recovery, factory reset, reinstall SuperSU an reboot. My phone now is finally rooted.
I think the factory reset part is strange, but I'm so glad I now have a rooted OPO.
When you try it, please let me know if you also have to do a factory reset.
Dr.Linde said:
Actually, I tried it and... It works!
I flashed the script, than used this guide (again):
http://forum.xda-developers.com/showthread.php?t=2788632
Than it looked like the only improvement is, that the bootloader is now unlocked. Root didn't work.
I could fix that by going to Recovery, factory reset, reinstall SuperSU an reboot. My phone now is finally rooted.
I think the factory reset part is strange, but I'm so glad I now have a rooted OPO.
When you try it, please let me know if you also have to do a factory reset.
Click to expand...
Click to collapse
That is sooo SCHWEET! I can't wait to try it on my phone when I get home! Woot!
Pretty sure I've done everything correctly so far, trying to unlock my bootloader.
For some reason it doesn't recognise my phone in fastboot mode, the blue led is on but Flashtool just says "wait for fastboot mode"
Please help a noob
Obviously you don't have the driver installed. If u did u wouldn't be getting that error
twelveways1 said:
Pretty sure I've done everything correctly so far, trying to unlock my bootloader.
For some reason it doesn't recognise my phone in fastboot mode, the blue led is on but Flashtool just says "wait for fastboot mode"
Please help a noob
Click to expand...
Click to collapse
Why are you using flashtool? Or who Said U should use that? Use Minimal Fastboot and Adb, NewFlasher/XperiFirm together with the Drivers from Google (Google Hosts all OEM Drivers on a List). That will be the most latest and official way (Sony Guide)
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!