hi fellows im fascing a problem,
Im unable to get my phone in adb or fastboot mode
when i plug my phone in and hit ADB Devices after allowing "Using USB to transfer files" it shows no device,
but if i dont allow it shows my devices.
again if i hit "Adb reboot-bootloader"
i restarts in bootloader but again here fastboot shows nothing.
any knid guy also let me know how to unlock bootloader on august patch after resolving this issue.
reinstalling windows solved my problem
Ibtisaam said:
hi fellows im fascing a problem,
Im unable to get my phone in adb or fastboot mode
when i plug my phone in and hit ADB Devices after allowing "Using USB to transfer files" it shows no device,
but if i dont allow it shows my devices.
again if i hit "Adb reboot-bootloader"
i restarts in bootloader but again here fastboot shows nothing.
any knid guy also let me know how to unlock bootloader on august patch after resolving this issue.
Click to expand...
Click to collapse
reinstalling windows solved my problem
Related
Hello, my HTC ONE is 2.24.401.8 and I have a problem with ADB devices..
I downloaded Sync Manager and let it recognize my deivce, and then uninstalled it.
It reacts to adb devices when its on , and even reboots to bootloader by "adb reboot bootlaoder"
but , the moment it goes into bootloader , it doesnt response to "adb devices" . it shows nothing. I can reboot it by "fastboot reboot" , but I cant do anything besides that
Any Ideas?
***I installed&Uninstalled Sync Manager 100 times..
From my understanding is when you are in the bootloader screen, you have to use fastboot commands and when you are in any other screen(twrp/booted into the OS) you use ADB commands.
I've never used ADB commands when in bootloader, I've always used fastboot commands.
What exactly are you trying to do?
Halloa said:
Hello, my HTC ONE is 2.24.401.8 and I have a problem with ADB devices..
I downloaded Sync Manager and let it recognize my deivce, and then uninstalled it.
It reacts to adb devices when its on , and even reboots to bootloader by "adb reboot bootlaoder"
but , the moment it goes into bootloader , it doesnt response to "adb devices" . it shows nothing. I can reboot it by "fastboot reboot" , but I cant do anything besides that
Any Ideas?
***I installed&Uninstalled Sync Manager 100 times..
Click to expand...
Click to collapse
As Nest said above, you need to use fastboot commands in bootloader, adb will only work into os or recovery.
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
KlamKhowder said:
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
Click to expand...
Click to collapse
unlock it using flash tool, just press unlock wait and enter the code.. done
KlamKhowder said:
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
Click to expand...
Click to collapse
try using different usb cable/ different port.
Had same problem....some driver was missing
Sent from my C5503 using xda app-developers app
I've finally gotten flash tool to work, however now it gives me an error saying that my device cannot be officially unlocked,
EDIT: i'm pretty sure i've unlocked the bootloader now, as flashtool had me enter an unlock code and my device has had all of its data reset.
however my issues continue as now flashtool utterly refuses to pick up my device. I have re-installed all drivers, flashtool, etc but still nothing.
sometimes it may have conflicts when flashtool and other tools use their own instance of adb or fastboot. I think the best thing to do now is reinstalling regular drivers normally. don't forget to enable usb debugging...
this may be useful :
Code:
[I]ADB_PATH[/I]\adb kill-server
exit
create a text file, paste this code then save it as ADB - Kill.cmd
Phone info
OPPO A74 5G
Model number - CPH2197
Build number - CPH2197_11_A.12
Android 11
Developer Mode enabled
OEM Unlock enabled
USB Debugging enabled
Below are screenshots of all of the above
[Screenshots](https://imgur.com/a/qw0fUAw)
Phone is recognised by ADB but not Fastboot and as such I cannot unlock the Bootloader. Is there something I've done wrong or something else I can try?
When entering "Fastboot devices" in CMD nothing comes up.
When entering command "ADB reboot Bootloader" in CMD the phone restarts instead of loading into Bootloader.
I have tried turning phone off and the pushing power button + vol up - this just keeps restarting phone.
Any help would be much appreciated as I'd really like to root this phone all extra info in images on Imgur. Link above.
DeeSkye said:
Phone info
OPPO A74 5G
Model number - CPH2197
Build number - CPH2197_11_A.12
Android 11
Developer Mode enabled
OEM Unlock enabled
USB Debugging enabled
Below are screenshots of all of the above
[Screenshots](https://imgur.com/a/qw0fUAw)
Phone is recognised by ADB but not Fastboot and as such I cannot unlock the Bootloader. Is there something I've done wrong or something else I can try?
When entering "Fastboot devices" in CMD nothing comes up.
When entering command "ADB reboot Bootloader" in CMD the phone restarts instead of loading into Bootloader.
I have tried turning phone off and the pushing power button + vol up - this just keeps restarting phone.
Any help would be much appreciated as I'd really like to root this phone all extra info in images on Imgur. Link above.
Click to expand...
Click to collapse
Did you find a way? I tried everything but I couldn't get into fastboot
No way to enter fastboot mode for oppo phones. Now I use Oppo A74 4G version. Cannot enter fastboot mode. It's locked by Oppo. And they don't give bootloader code for unlock BL. Only way is to change phone
I've been trying run fastboot too. 4 hours later I find this thread. That explains it
Last Oppo phone I buy I guess.
Did you manage to find a workaround for this by chance?
Has anyone tried rebooting from recovery to then enter fastboor or?
Im gonna look into myself soon...
Ive seen this issue before on a different phone but cant remember how they bypassed it
Perhaps yall can try to find a post where they did so.. maybe it'll work on this phone too.
I was able too get to fastboot mode. The phone labels it "recoveryd mode", however, fastboot commands work.
1st. Connect phone and confirm ADB is connected by using "ADB devices" command.
2nd. Enter "adb reboot fastboot bootloader"
Phone will reboot into "recoveryd mode". It looks exactly like the normal recovery mode except the title displayed after you select the language and fastboot commands will work.
However, I still have not found out how to unlock the bootloader, so it does me no good.
try doing adb reboot fastboot or adb reboot bootloader
fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
guys ,, fails
when trying to boot to fastboot and not fastbootd
Hello all, I'm trying to install a new ROM but one of the first steps consists in getting access to adb and fastboot mode.
Unfortunately, I can easily access to adb mode, and adb commands respond well, but when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
I've tried to install adb drivers, uninstall/reinstall the drivers (but it's always the windows drivers that installs first). I even tried to install google usb drivers using SDK manager, but didn't succeed this step.
I've tried to change the usb cable, but with another one, it was worse: even the adb commands would not work. So I guess the one I'm using is ok.
I'd be very happy if someone could help me fixing this frustrating bug!
Model:M1903F11A
kernel:4.14.117-perf-g0f2347b
MIUI Global 12.0.6
Android version : 10 QKQ1.190825.002
Cyjam said:
.. new ROM but one of the first steps consists in getting access to adb and fastboot mode.
...
Click to expand...
Click to collapse
The first step is to unlock the bootloader.
Cyjam said:
... when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
....
Click to expand...
Click to collapse
For fastboot try:
adb devices
........... (here you must see a number)
adb reboot bootloader
fastboot devices
........... (here you must see that number again)
Hi, thanks for trying to help me:
you're right , first is the unlock, but it's done. it's even in "grey" on the screen and written: bootloader is already unlocked. I've tested my phone with "root checker" and test is ok.
you're right about the command, this is the one I've used to go to fastmode and actually this command works: as I said, when in adb mode, it's all good: my phone is connected to pc and accepts the adb commands. But once I switch to fastboot, this is when it's going wrong: my phone's not answering to any commands.
To be more precise: when prompting: adb devices: i get a number. When prompting, in fastbood mode, fastboot devices: i get nothing.
Alleluia!!
Finally found out how to fix it!
After going in fasboot mode with the command: adb reboot bootloader, i opened the windows device manager: There I found a android XXx interface, or something like this: anyway, something barely identified by windows. Right clik, update drivers, manually update, pointing to the folder I store the google usb drivers and : Bingo! It works like a treat.
I now can step further in the process... Hope I won't need to come back with another question in the next minutes!
Hi I've a pixel5, it was reset to V11 software for compatibility with my son's medical device. Now with added security the app wont work because the bootlaoder is open. When I boot it say sits unlocked and to visit g.co/ABH
I've tried but cannot get it closed
When I go to fastboot I get the 'no command'.. on tring to flash it allows me to see the device and reboot the bootloader BUT then it will not respond to the cmd fastboot devices. when I try fastboot flashing lock it just says <waiting for device>
Any help? !
Billy
Try installing the usb driver https://developer.android.com/studio/run/win-usb
billyedit said:
Hi I've a pixel5, it was reset to V11 software for compatibility with my son's medical device. Now with added security the app wont work because the bootlaoder is open. When I boot it say sits unlocked and to visit g.co/ABH
I've tried but cannot get it closed
When I go to fastboot I get the 'no command'.. on tring to flash it allows me to see the device and reboot the bootloader BUT then it will not respond to the cmd fastboot devices. when I try fastboot flashing lock it just says <waiting for device>
Any help? !
Billy
Click to expand...
Click to collapse
I'm confused about "sits unlocked" and if this means you're stuck on the unlocked bootloader warning screen. If the phone hangs you're better off keeping the bootloader unlocked until that problem is sorted out. If it's starting, on the other hand...
Waiting for device means fastboot isn't communicating with the phone. Could be USB drivers. But if you flashed Android 11 from the same computer, drivers were working then, right?
In Developer options make sure USB debugging is enabled. While there, and while the bootloader is still unlocked, make sure OEM unlock is in the On position; it will flip back to Off when the bootloader is locked again.
Use Platform Tools 33.0.3 when trouble shooting USB to avoid trouble shooting Platform Tools 34.x.x.
As long as you get serial number output from commands adb devices and fastboot devices, fastboot flashing lock should work to re-lock the bootloader. Remember to finalize locking with the phone buttons.
Thank you both is was indeed the USB driver that needed the google update... All is well! thanks