Database Users

Unable To Unlock Bootloader

Hi,
Have been an owner of an M9+ for a few months now and it's taken me this long to not manage to unlock the bootloader so have caved in and decided to ask nicely for some help / advice.
Firstly, I live in the UK. I bought the handset from Fonis who are located in Dubai (best price, unlocked to any network, etc, etc) so am assuming this handset has got nothing to do with Verizon?
Problems..... the check box for 'allow OEM unlock' is not there. Doesn't exist. There is nothing in Developer Options to do with OEM.
When I boot the phone into Download Mode my pc does not detect it so am unable to proceed in getting the identifier token thingymabob.
Things I have done.... enabled dev options, enabled usb debugging, downloaded all the adb / fastboot stuff, shouted a lot and referred to the handset as a s teaming pile of s**t.
So, am I being extremely thick here and missing something obvious? Have I bought a complete donkey of a handset? (Fonis have good reviews online and that along with the price was a deciding factor in using them).
If anyone can help, great. If any further intel is needed then ask and I shall provide.
Cheers,
Rick

Do you have HTC sync latest installed? That contains the USB driver for the phone for fastboot to work

Yep, latest version of sync is installed. When I open HTC Sync with the phone connected to the PC while in download mode Sync states 'no phone connected'.
Have tried different usb leads and different usb ports but nothing is happening.

p3x982 said:
Yep, latest version of sync is installed. When I open HTC Sync with the phone connected to the PC while in download mode Sync states 'no phone connected'.
Have tried different usb leads and different usb ports but nothing is happening.
Click to expand...
Click to collapse
If you didn't try, maybe try connecting device, remove/uninstall driver of phone device instance in Device manager, reconnect and see if it installs correct driver. Sometimes wrong driver sticks with the phone device, if it was connected before HTC sync installed.

In developer options (in settings) you have to enable the bootloader unlock.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

tbalden said:
Do you have HTC sync latest installed? That contains the USB driver for the phone for fastboot to work
Click to expand...
Click to collapse
Will give thata try at the weekend and report back.

kumita-chan said:
In developer options (in settings) you have to enable the bootloader unlock.
Click to expand...
Click to collapse
Hi, as stated in my original post, that option is not on my phone, it doesn't exist.

USB Debugging can't be used on my Mi A1

Hello people, I've a weird problem on my device.
Yesterday everything was ok. I've enabled USB debugging and I've used "adb" from terminal without issues.
Today, I can't connect with adb anymore.
If I use adb devices I can't see my device. If I try to Enable USB Debugging on my device, for a very short moment (about 2 seconds) I can see my device connected, then it disconnects.
I noticed this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That icon appears for 2 seconds after I disable and re-enable USB debugging, then it disappears (of course the notification for USB connection appears for 2 seconds then disappears).
I've tried everything:
different cables
different PC and Mac
I've removed adb_keys from /data/misc/adb
I've removed adb kesy from .android folder on my PC/Mac
I've revoked USB authorisation
Nothing.
Is there a saint can help me fix this?
I don't want to hard reset device again.
Thanks,
ghale
PS: I don't know if it's important, but in Fastboot mode, I can list device with fastboot devices command.

ghale said:
Hello people, I've a weird problem on my device.
Yesterday everything was ok. I've enabled USB debugging and I've used "adb" from terminal without issues.
Today, I can't connect with adb anymore.
If I use adb devices I can't see my device. If I try to Enable USB Debugging on my device, for a very short moment (about 2 seconds) I can see my device connected, then it disconnects.
I noticed this:
That icon appears for 2 seconds after I disable and re-enable USB debugging, then it disappears (of course the notification for USB connection appears for 2 seconds then disappears).
I've tried everything:
different cables
different PC and Mac
I've removed adb_keys from /data/misc/adb
I've removed adb kesy from .android folder on my PC/Mac
I've revoked USB authorisation
Nothing.
Is there a saint can help me fix this?
I don't want to hard reset device again.
Thanks,
ghale
Click to expand...
Click to collapse
Uninstall adb driver then install latest version
Sent from my [device_name] using XDA-Developers Legacy app

Olystem said:
Uninstall adb driver then install latest version
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I did that already, on both machines.
Nothing.

ghale said:
I did that already, on both machines.
Nothing.
Click to expand...
Click to collapse
Disbale Usb Debugging and OEM Unlocker Then disable Devolopers option Restart Device Then Check

Hello, I've tried that.
Nothing, damn.
I'm stuck.
Btw: thanks.

ghale said:
Hello, I've tried that.
Nothing, damn.
I'm stuck.
Btw: thanks.
Click to expand...
Click to collapse
How you remove or uninstall ADB Driver

Well, on Mac it's very simple, just download new adb and fastboot from Android developer portal and replace old ones.
No drivers needed. On pc is a bit different.

Same problem with Mi6. Did u fix it?

Did you install Cerberus?

Fire hd 8 gen 7th bootloop

i have bootloop fire hd 8 and usb debugging off, how i can fix it?
Try:
1/ Factory reset in recovery => dont work.
2/I go recovery mode -> " apply update from ADB" ->
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it not found my device because USB Debugging is off (?), so i cant sideload Firmware in https://forum.xda-developers.com/showpost.php?p=73033483&postcount=2, plz help

blackerghost said:
i have bootloop fire hd 8 and usb debugging off, how i can fix it?
Try:
1/ Factory reset in recovery => dont work.
2/I go recovery mode -> " apply update from ADB" ->
it not found my device because USB Debugging is off (?), so i cant sideload Firmware in https://forum.xda-developers.com/showpost.php?p=73033483&postcount=2, plz help
Click to expand...
Click to collapse
Enabled USB debugging is not required for sideloading in recovery mode. That would render the whole recovery functionality useless. I just checked it.
Make sure your USB port and cable are okay, maybe use another. Some hubs don't work with ADB.
Also check your drivers. Uninstall and reinstall the official or universal ADB driver. You should notice when the device is detected.
Attention: Only sideload the system version you're on or higher. Downgrading could brick your tablet.

lassemacchiato said:
Enabled USB debugging is not required for sideloading in recovery mode. That would render the whole recovery functionality useless. I just checked it.
Make sure your USB port and cable are okay, maybe use another. Some hubs don't work with ADB.
Also check your drivers. Uninstall and reinstall the official or universal ADB driver. You should notice when the device is detected.
Attention: Only sideload the system version you're on or higher. Downgrading could brick your tablet.
Click to expand...
Click to collapse
Tks u, my sideload is in process.
I change cable but it still not recognize my devices, so i update driver software and pick it from list driver.

OP 6T fastboot device not detected

I had to reinstall Win 10 on my computer and now I'm not able to connect to my 6T in order to root it.
The boot locker is unlocked, I can see it at phone boot. It was unlocked also before last update to OxygenOS 10.3.7.
Debug USB in enabled. When I connect to the phone to the computer it is deceted and I can transfer files.
Whit ADB devices phone is deteted (picture is from all in one tool, using command prompt same result)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
using fastboot devices the phone is not detected.
installed last official usb drivers (google and oneplus)
Any idea, suggestion or further test that can help?
Thanks

Same problem here. Please help.

Finally I found a working solution.
If you have a laptop you have to disable secure boot.
Then you have to disable signature verification on windows 10 ( How to Enable or Disable Driver Signature Enforcement in Windows 10 | Tutorials (tenforums.com) ).
I used option 3.
Download Oneplus usb drivers ( Download Latest OnePlus USB Drivers for Windows and Mac (getdroidtips.com) ).
Then 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.

Thanks man, it worked for me.
Just to complete, after istalling the drivers you can restore signature verification and secure boot on Win 10.
Everything will work fine.

[SOLVED] Unlock BTV-DL09, problem modem

Hello everybody.
I wanted to unlock an BTV-DL09 [ Android 7 EMUI 5.04 EU ], but I'm stuck like the_wing was.
Modem no found !
Phew, got it unlocked! Moments of terror when entering the commands on the cmd...
A few mentions where I got stuck that may help someone else:
Regarding point 3:
In case your model has LTE (i.e. BTV-DL09), you actually should have a dialer application that you have to use instead of the calculator app, which didn't work for me. This is also mentioned in the DC unlocker app. In case you do it with the dialer, you have to enter following code: *#*#2846579#*#*
Regarding point 4:
Inside the "DC unlocker" app, I also got the "device not found" error, and I was wondering why. Two things I noticed:
- To enable USB debugging, it was not sufficient for me to activate the switch in the developer options, as the default USB mode for me is "charging only". I had to change it to i.e. "Device File Manager (MTP)" by tapping on the notification and then re-activate USB debugging in the developer options (which turned off after switching to MTP mode) to get USB debugging working.
- After enabling "manufacturer mode", the mode was turned off as soon as I quit the menu. So I had to stay in the menu to make sure manufacturer mode is on.
- You can check your device manager in Windows to see if the current mode is active: When doing USB debugging, the device "Android Composite ADB Interface" should show up under "Android Phone" list, whereas when you turn on manufacturer mode, some COM ports should show up under "Ports (COM and LPT)"; the one DC unlocker is searching should be named "Android Adapter PCUI". If you got some devices with not properly installed drivers you should consider installing HiSuite software on Windows first.
Regarding point 8
- When I bought the credits for DC unlocker for PayPal, I had to click on a link arrived to the PayPal e-mail for confirming your account. I then still got the "Server login error", but closing and reopening DC unlocker eventually fixed it.
Hope this helps! Happy unlocking to everybody!
Click to expand...
Click to collapse
I have installed Hisuite and Huawei data card driver.
Impossible to activate Device File Manager (MTP) and manufacturer mode, one deactivates the other, I do not know if this is the problem, but according to the tutorials it is a must.
I have a hard time understanding where the problem comes from, I even tested different USB cable, Win 7 and Win 10, I really did everything, but I'm dried.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I finally managed to unlock the bootloader, DC unlocker did not show me information from the tablet, but despite this, I could go to the next step and proceed with the unlocking, it is because of a msie security update according to Valdemaras on cd-unlocker forum, thanks to him.