Database Develop

Adb not recognising OT3

Hey guys, I have a problem here. I unlocked the phone, flashed with twrp 3.01 and supersu. Then I installed Resurrection remix, flashed twrp 4.0.1 and supersu again. My phone works, but always had the initial screen "dm-verity". So I searched about it, and I figured out I have to go to bootloader and enter 2 commands. Now, when I enter in cmd and type "adb devices" while op3t in bootloader, my phone is not recognized. (0 devices found). Instead, when in twrp -> advanced-> adb sideload, my phone is listed with serial number. How can I make my phone recognisible by Windows while in bootloader mode, so that I can enter the 2 commands and get rid of dm-verity message? Everything inside the phone and the rom itself work perfect.! Also, when I go to settings/developer, I'm not able to change "oem unlock", it stays forced on OFF... Is that normal? Thank you very much in advance.

Magic Tmac1 said:
Hey guys, I have a problem here. I unlocked the phone, flashed with twrp 3.01 and supersu. Then I installed Resurrection remix, flashed twrp 4.0.1 and supersu again. My phone works, but always had the initial screen "dm-verity". So I searched about it, and I figured out I have to go to bootloader and enter 2 commands. Now, when I enter in cmd and type "adb devices" while op3t in bootloader, my phone is not recognized. (0 devices found). Instead, when in twrp -> advanced-> adb sideload, my phone is listed with serial number. How can I make my phone recognisible by Windows while in bootloader mode, so that I can enter the 2 commands and get rid of dm-verity message? Everything inside the phone and the rom itself work perfect.! Also, when I go to settings/developer, I'm not able to change "oem unlock", it stays forced on OFF... Is that normal? Thank you very much in advance.
Click to expand...
Click to collapse
Did you installed the drivers? I had the same issue and I installed the OP3T USB drivers afterward it shows me the device.

Yes I did. But I can also reinstall them, can you please provide me the driver's link which fixed the same problem? Thanks

Nokia 7 Plus Bootloader unlock on OREO & ADB Fastboot Problem

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

Question Can't get into fastboot to unlock bootloader

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

Question Stuck on the fastboot screen

Hey,
So, basically, I'm having this issue where my phone fails to enter fastboot mode. It just gets stuck on the screen. I can restart normally if that happens by just holding down the power and volume down button, but I really don't get why it isn't booting into fastboot properly. Anything I can do to fix it? I'm on 12.5.9, Redmi 9T Global version. I need to boot into fastboot in order to install TWRP, and I can't do that due to this issue. Also, as a side question, how can I downgrade MIUI?
Thanks in advance.

Bump.

Bump.

Bump.

Xenomorphs said:
Hey,
So, basically, I'm having this issue where my phone fails to enter fastboot mode. It just gets stuck on the screen. I can restart normally if that happens by just holding down the power and volume down button, but I really don't get why it isn't booting into fastboot properly. Anything I can do to fix it? I'm on 12.5.9, Redmi 9T Global version. I need to boot into fastboot in order to install TWRP, and I can't do that due to this issue. Also, as a side question, how can I downgrade MIUI?
Thanks in advance.
Click to expand...
Click to collapse
Have you tried using adb and fastboot method. Try using adb to force boot it into fastboot

qwertz512 said:
Have you tried using adb and fastboot method. Try using adb to force boot it into fastboot
Click to expand...
Click to collapse
Any detailed steps for that? Right now, I'm facing another issue, too, where I apparently have an update (MIUI 13), but it can't verify it, hence, not installing it.

Xenomorphs said:
Any detailed steps for that? Right now, I'm facing another issue, too, where I apparently have an update (MIUI 13), but it can't verify it, hence, not installing it.
Click to expand...
Click to collapse
Enable developer options and enable usb debugging after that download android adb tools and adb drivers for your phone. After that you have installed everything go to the directory where you have adb installed and from that open a elevated command prompt and type in "adb devices". It should say a random string followed by device (if your device is plugged in) After that type adb reboot bootloader and it should reboot into fastboot. For the update issue I've had that too its when the download was interrupted mid-way and it got corrupted somehow and the md5 doesn't match. Make sure to download it on the screen without turning off the screen or switching off to others apps.

hakudayo said:
Enable developer options and enable usb debugging after that download android adb tools and adb drivers for your phone. After that you have installed everything go to the directory where you have adb installed and from that open a elevated command prompt and type in "adb devices". It should say a random string followed by device (if your device is plugged in) After that type adb reboot bootloader and it should reboot into fastboot. For the update issue I've had that too its when the download was interrupted mid-way and it got corrupted somehow and the md5 doesn't match. Make sure to download it on the screen without turning off the screen or switching off to others apps.
Click to expand...
Click to collapse
Thank you so much. I'm going to try.

Xenomorphs said:
Thank you so much. I'm going to try.
Click to expand...
Click to collapse
No problem if you have any questions just ask me

Now I'm stuck with this same issue.,
Got into this while trying to boot TWRP OrangeFox-R12.1_3_A12_FBEv2-Unofficial-lime.zip on xiaomi A12 ROM

Question [Resolved] No connection with pc in fastboot mode.

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!