Used ADB to unlock bootloader but now ADB can't "see" the phone in download mode
I have a Windows 7 PC and I used that with Android SDK to unlock the bootloader and that worked. Now (trying to install recovery) I can put the phone (5.1.1) in download mode and the PC registers the phone in Device Manager but ADB doesn't see it. I've changed nothing with the PC since unlocking the bootloader and I've confirmed USB debugging is enabled on the phone but the command 'adb devices' lists nothing below 'List of Devices Attached'. Has anyone heard of this? Any troubleshooting suggestions?
Try go to device manage and look for a device with a strange name using the Android ADB device driver, choose update and look for a driver for LGE ADB device instead.
I did t think think adb works in download mode, and it sure won't work in bootloader
If you are on lollipop then use fastboot to flash TWRP
fastboot flash recovery nameofrecovery.img
Sent from my LG-H901 using XDA-Developers mobile app
I am trying to root my J7 NEO but i cannot boot into download mode.
I have tried the conventional methods such home+vol d+power) and adb commands.
Nothing will work.
It is factory unlocked .
I can boot into recovery and tried reboot to bootloader option and that does not work
Can anyone help?
Hi , to use adb command enable USB Debugging to do that go to settings /about phone /Software information and click 7-8 time on Build number , now go back and click on Developler Option and enable usb debugging . Now connect your phone wait for adb driver to be installed, once is installed open adb command line type adb devices to see if your device is recognized next write adb reboot download . Good luck
I cannot get adb to recognize my device in download mode. I have installed all the necessary drivers, got usb debugging enabled and even switched out cables. If anybody has a solution to this it would be greatly appreciated. I'm trying to falsh a boot img with magisk to root my device, but download mode is not recognized.
ADB doesn't work in Fastboot ( AKA Download and/or Bootloader ) mode: you have to use
Code:
fastboot devices
fastboot <FASTBOOT-SUBCOMMAND-HERE>
jwoegerbauer said:
ADB doesn't work in Fastboot ( AKA Download and/or Bootloader ) mode: you have to use
Code:
fastboot devices
fastboot <FASTBOOT-SUBCOMMAND-HERE>
Click to expand...
Click to collapse
unfortunately the fastboot command ain't working either. everything works fine when the phone is on it's just when I enter download mode it ain't recognized
Cat_tails said:
unfortunately the fastboot command ain't working either. everything works fine when the phone is on it's just when I enter download mode it ain't recognized
Click to expand...
Click to collapse
Why you enter the download mode - that is LAF mode - at all?
Normally there is no adb nor fastboot in that mode...
I have not been able to get how to activate diag port on this nokia 7.1, it has unlocked the bootloader and made root but I can not activate diag port.
any idea how to activate the diag port?
What commands did you enter? Which rom do you use?
Code:
adb devices
adb shell
su
setprop sys.usb.config diag.adb
Hello.
Today I updated from the Nord 5G to the Nord 2 5G.
DN2103_11_A.14
I have enabled developer mode, oem unlock and adb debug.
I can't access fastboot properly. And recovery is different from the previous Nord. There is no option to reboot to fastboot.
I use adb reboot-fastboot and I enter a sort of fastboot. It says:
fastboot_unlock_verify ok
The device is in fastboot mode which is only for debug Android devices. if you want to exit fastboot mode, please long press volume up nad power buttons simultaneously.
Phone is recognized in windows when in adb-mode (normal booted), but does not recognize it when in this new fastboot mode. Just an Android with an exclamation mark on.
Halp?
krugm0f0 said:
Hello.
Today I updated from the Nord 5G to the Nord 2 5G.
DN2103_11_A.14
I have enabled developer mode, oem unlock and adb debug.
I can't access fastboot properly. And recovery is different from the previous Nord. There is no option to reboot to fastboot.
I use adb reboot-fastboot and I enter a sort of fastboot. It says:
fastboot_unlock_verify ok
The device is in fastboot mode which is only for debug Android devices. if you want to exit fastboot mode, please long press volume up nad power buttons simultaneously.
Phone is recognized in windows when in adb-mode (normal booted), but does not recognize it when in this new fastboot mode. Just an Android with an exclamation mark on.
Halp?
Click to expand...
Click to collapse
Don't own this device but try: "adb reboot bootloader" instead and test fastboot commands from there (don't navigate to Fasboot from bootloader).
krugm0f0 said:
Phone is recognized in windows when in adb-mode (normal booted), but does not recognize it when in this new fastboot mode. Just an Android with an exclamation mark on.
Click to expand...
Click to collapse
This is normal behaviour with the OPN2 afaik. Your PC can access the USERDATA folder whilst in ADB mode (aka booted normally) and whilst in the recovery bios. Your pc CANNOT access the USERDATA folder when your phone is in fastboot, or at least I've never been able to on my Nord 2.
Your op didn't include what exactly you need help with. Everything you described is exactly intended behaviour. From my understanding your seem to have booted into fastboot mode, then noticed your PC can't access userdata. That's normal, you can still use fastboot commands and your PC is still connected to the phone. Your "My Computer" folder on PC not showing the phone shouldn't be any cause for alarm.
Now I'm starting to guess, because you might have failed to mention; Are you unable to send fastboot commands to your phone when its in fastboot mode?
Are you trying to flash a file?
What's the issue?
Zombnombs said:
This is normal behaviour with the OPN2 afaik. Your PC can access the USERDATA folder whilst in ADB mode (aka booted normally) and whilst in the recovery bios. Your pc CANNOT access the USERDATA folder when your phone is in fastboot, or at least I've never been able to on my Nord 2.
Your op didn't include what exactly you need help with. Everything you described is exactly intended behaviour. From my understanding your seem to have booted into fastboot mode, then noticed your PC can't access userdata. That's normal, you can still use fastboot commands and your PC is still connected to the phone. Your "My Computer" folder on PC not showing the phone shouldn't be any cause for alarm.
Now I'm starting to guess, because you might have failed to mention; Are you unable to send fastboot commands to your phone when its in fastboot mode?
Are you trying to flash a file?
What's the issue?
Click to expand...
Click to collapse
I am unable to send fastboot commands. Is not recognized by "fastboot devices". And this fastboot mode looks nothing like my previous phones. 2, X, 5T and Nord 5G. <waiting for device>
I want to do my "usual routine" with my new phones. Unlock, flash twrp or other recovery, and flash magisk for root.
After a "full wipe" of ADB and fastboot drivers, I reinstalled and got it working!
nothing. only recovery mode
vol down+ power =recovery mode
vol up + power = normal boot
I finaly boot into fastboot mode with adb command only (adb reboot bootloader)
With buttons wont work.
But i can't enable Volte/Vowifi (thats why i wanted to boot there).
Can you send adb commands when in recovery mode ?
I'm trying to enable VoLTE too, but adb only detect phone when powered normaly, not when in recovery mode.
i don't know about adb but in fastboot you can.
I can't enable volte/vowifi in fastboot with this commands.
https://androplus.org/wp/wp-content/uploads/2021/08/onr12.jpg
Fastboot commands start with fastboot, those are adb commands.
krugm0f0 said:
After a "full wipe" of ADB and fastboot drivers, I reinstalled and got it working!
Click to expand...
Click to collapse
krugm0f0 said:
Hello.
Today I updated from the Nord 5G to the Nord 2 5G.
DN2103_11_A.14
I have enabled developer mode, oem unlock and adb debug.
I can't access fastboot properly. And recovery is different from the previous Nord. There is no option to reboot to fastboot.
I use adb reboot-fastboot and I enter a sort of fastboot. It says:
fastboot_unlock_verify ok
The device is in fastboot mode which is only for debug Android devices. if you want to exit fastboot mode, please long press volume up nad power buttons simultaneously.
Phone is recognized in windows when in adb-mode (normal booted), but does not recognize it when in this new fastboot mode. Just an Android with an exclamation mark on.
Halp?
Click to expand...
Click to collapse
i am having the same issue can any one help
krugm0f0 said:
After a "full wipe" of ADB and fastboot drivers, I reinstalled and got it working!
Click to expand...
Click to collapse
pls contact me in 9650930525 in this number and help me how u did it
drkanurag said:
i am having the same issue can any one help
Click to expand...
Click to collapse
pankspoo said:
On Android 12 OnePlus removed fastbootmode so no unlocking nothing.
But how did u booted in fastbootmode on oos 12 i can't understand
Click to expand...
Click to collapse
roldev said:
Downgrade to latest A11. Unlock via fastboot. Do what you want, then. All explained here or/and telegram group. Sorry, don't have time to do step by step guide now. Cheers.
Click to expand...
Click to collapse
Follow this guide to downgrade to A11 https://community.oneplus.com/thread/1596759
Then you should be able to access fastboot.
krugm0f0 said:
After a "full wipe" of ADB and fastboot drivers, I reinstalled and got it working!
Click to expand...
Click to collapse
Could you go into more detail on what you did in the entire process exactly? Did you use the drivers and adb install from the 15 sec installer? Did you simply uninstall them in the Windows Device Manager and click on "update drivers" to find the local drivers from the 15 sec installer? Which ones did you choose? Sorry, these might be dumb questions, but I'm admittedly very stupid when it comes to Windows and drivers in particular.
I did the exact thing I described above but I'm still just getting that message. Additionally, "fastboot devices" won't list anything and "fastboot oem unlock" will wait for the device for eternaty. "adb devices" on the other hand will list my device while not in Fastboot.