Develop Bugs

Help! Bootloader not recognised. Forgot to toggle Enable OEM unlocking :(

I unlocked my bootloader without toggling Enable OEM unlock in the developer options. Now my devices shows unlocked in bootloader but fastboot doesn't recognises it After unlocking everything got erased and now the toggle button in developer options is disabled! What to do? Can't even install recovery without fastboot. :'( Now after Is there anyway get fastboot working again so that I can go to stock and do the process once again? I just want my fastboot to work as it used to Reply ASAP. Thank you in advance

cbhhargava said:
I unlocked my bootloader without toggling Enable OEM unlock in the developer options. Now my devices shows unlocked in bootloader but fastboot doesn't recognises it After unlocking everything got erased and now the toggle button in developer options is disabled! What to do? Can't even install recovery without fastboot. :'( Now after Is there anyway get fastboot working again so that I can go to stock and do the process once again? I just want my fastboot to work as it used to Reply ASAP. Thank you in advance
Click to expand...
Click to collapse
It's disabled, but turned on right? That's normal behavior for the OEM Unlock menu setting on Nougat. Enable USB debugging then try using fastboot.
Sent from my Nexus 5X using Tapatalk

That's most like a driver\cable issue. You can't unlock the bootloader without toggling OEM unlocking. Actually it seems there is a posibility found by Bitdomo but for security reasons he didn't shared it.

You're safe if you're unable to change the OEM Unlocking status in Developer Options because that's how it behaves. That's totally fine.
Make sure your download the Factory Image from the Factory Images Website and execute the flash.bat file when you're in fastboot mode.
Let the processes complete and your device will return to 100% stock. Cheers!

I'm sure my cable works. Because it worked first time when I unlocked it(without toggling the oem unlock option) with same cable and laptop. And I'm also sure that there is no driver issue because my device manager shows my device when I connect it in fastboot mode. But "fastboot devices" gives me nothing. I'm tensed and using my phone on stock android without updating any ota updates. I don't know what to do and I'm totally freaking out.

After your phone is in fastboot mode and connected to the computer, try going into control panel - device and printers - right click on your nexus 5x - properties - hardware - properties - change settings - driver - update driver - select manually - select from existing drivers. Now try the drivers one by one and see which one works

how to check if bootlader is locked

Hi Folks
I just got the Media Pad M2 8.0 and I want to check if the bootloader is locked or not
because there is no dialer installed I can't use the code I found in other forums
is there another way to find out?

hingerl said:
Hi Folks
I just got the Media Pad M2 8.0 and I want to check if the bootloader is locked or not
because there is no dialer installed I can't use the code I found in other forums
is there another way to find out?
Click to expand...
Click to collapse
Yes, there should be. You need to enter fastboot mode on the phone - i.e you need to get into the bootloader screen. The bootloader screen (usually called fastboot mode) will tell you if the bootloader and FRP are locked or unlocked - If it is locked, you should see "PHONE Locked" and "FRP Lock" in green, otherwise it should say "PHONE Unlocked" and "FRP Unlock" in red if the phone has been properly unlocked.
You can enter fastboot mode by either using ADB ("adb reboot bootloader", first make sure to enable developer options first as detailed in the Rooting guide, and then enabled USB debugging), or by first shutting down the phone and then powering it up while holding down the VOLDN (Volume Down) key. Of the two methods, I'd recommend the ADB method because the hardware keys method is usually hit-or-miss for me - sometimes it takes me to the bootloader, sometimes it boots normally into the ROM.
If you're on Windows and need the ADB and fastboot binaries, you can install the "15-second ADB installer" found in this thread.

Thanks, that worked, took me a while to figure everything out...
and it appears that my device is unlocked...

Touch Screen Not Responding

Update #2: I've been able to connect the A2 to my PC and can detect it when in fastboot mode with the "adb/fastboot" tools and with the MiFlash utility. I attempted to flash an earlier version of a ROM but I can't. MiFlash gives:
"Erase boot_a error"
I then attempted to unlock the device with the "Mi Unlock" tool but get "Sorry, your MI ID is not associated with a phone number"
Any suggestions on how to unlock the bootloader?
Update: After waiting a few minutes the touch screen started responding for a few inputs, and then stops. Toggling the lock screen a few times allows additional inputs for a few presses.
A couple of months ago the phone started displaying issues with touch input. Locking and unlocking the screen would correct the issue for a while. However, as time progressed the issue got worse.
Today I did a factory reset and since then I have been unable to input any operations. The phone is stuck on the "Hi there" welcome screen and I cannot press "Start". Power and volume buttons work fine, so I attempted to use "adb" to flash a new ROM, or a stock ROM from before July/August.
My PC won't detect the phone when in "fastboot"
What options are left?
Can I dump the stock ROM to an SD-Card and attempt to flash that from the bootloader?
Or do I need to unlock the phone prior to any ROM manipulation?
thanks for any advice

Update #2: I've been able to connect the A2 to my PC and can detect it when in fastboot mode with the "adb/fastboot" tools and with the MiFlash utility. I attempted to flash an earlier version of a ROM but I can't. MiFlash gives:
"Erase boot_a error"
I then attempted to unlock the device with the "Mi Unlock" tool but get "Sorry, your MI ID is not associated with a phone number"
Any suggestions on how to unlock the bootloader?

mindstorms911 said:
Update #2: I've been able to connect the A2 to my PC and can detect it when in fastboot mode with the "adb/fastboot" tools and with the MiFlash utility. I attempted to flash an earlier version of a ROM but I can't. MiFlash gives:
"Erase boot_a error"
I then attempted to unlock the device with the "Mi Unlock" tool but get "Sorry, your MI ID is not associated with a phone number"
Any suggestions on how to unlock the bootloader?
Click to expand...
Click to collapse
Boot your phone in system (normally).
Find build number in settings, about phone. Tap 7 times or until you've unlock developer options.
Turn on OEM Unlock and USB Debugging.
Turn off phone and boot fastboot mode.
Type 'fastboot oem unlock' and wait until it finish wipe phone.
And it's done.

RFD80M-75679 said:
Boot your phone in system (normally).
Find build number in settings, about phone. Tap 7 times or until you've unlock developer options.
Turn on OEM Unlock and USB Debugging.
Turn off phone and boot fastboot mode.
Type 'fastboot oem unlock' and wait until it finish wipe phone.
And it's done.
Click to expand...
Click to collapse
Thanks, that worked. I am now able to flash an earlier ROM, will see if that fixes the screen input issue.

Flashed an earlier version of the ROM and still had issues, so I finally managed to flash an alternative ROM - HavocOS - and that experienced the issue as well. Looks like the phone has a hardware issue somewhere.

help me.

hello.
Trying to run bootloader on htc 10.
First of all I enabled developer mode in settings app and turned on USB Debugging but I can't turn on oem unlock.
What should I do?

Bootloader is already unlocked.
If you want to lock, then log on to https://www.htcdev.com/bootloader/ select your phone and go to the following pages. Maybe there is information about re-locking there.
Probably it is the fastboot oem lock command

Bootloading Kyocera DuraXV Extreme

Hello, I'm having some serious trouble bootloading my Kyocera DuraXV Extreme (AOSP)
I've went into developer options and activated USB debugging and allowed OEM unlocking.
But I get stuck on rebooting into bootloader mode. I've tried different approaches:
1. Starting up phone while holding volume up and down buttons. Then select "reboot to bootloader".
2. adb reboot bootloader command
Both options reboot the phone without going into bootloader mode.
Seems Kyocera decided to somehow lock the bootloader mode. Anyone know of a workaround here?

jonas.sj said:
Hello, I'm having some serious trouble bootloading my Kyocera DuraXV Extreme (AOSP)
I've went into developer options and activated USB debugging and allowed OEM unlocking.
But I get stuck on rebooting into bootloader mode. I've tried different approaches:
1. Starting up phone while holding volume up and down buttons. Then select "reboot to bootloader".
2. adb reboot bootloader command
Both options reboot the phone without going into bootloader mode.
Seems Kyocera decided to somehow lock the bootloader mode. Anyone know of a workaround here?
Click to expand...
Click to collapse
My comments below are based on the belief that you are trying to unlock the bootloader.
I am not familiar with this phone but generally the two steps mentioned by you are not enough to unlock the bootloader. After those steps, you'll have to issue a command via adb to unlock the bootloader and if successful, then you can boot into it for further operations. The command will vary between devices, so search and profit.

Thanks, this cleared it up a bit, you are right, I'm trying to unlock it.
I'm trying the command fastboot flashing unlock but only getting the message < waiting for any device >. I read somewhere that I might need some USB drivers but I don't know where to find them. I have the latest version of the standard USB drivers for the phone, but as I understand it I need special drivers for this?

I'm trying to follow the steps here: https://www.ifixit.com/Guide/How+to+unlock+the+bootloader+of+an+Android+Phone/152629#s317298
I get stuck on the step:
Enter the command adb reboot bootloader
Wait a couple seconds until your device rebooted into the bootloader, then enter the command fastboot flashing unlock
My phone isn't "rebooted into the bootloader", it just reboots. It gives the message "< waiting for any device >" when I write fastboot flashing unlock

jonas.sj said:
I'm trying to follow the steps here: https://www.ifixit.com/Guide/How+to+unlock+the+bootloader+of+an+Android+Phone/152629#s317298
I get stuck on the step:
Enter the command adb reboot bootloader
Wait a couple seconds until your device rebooted into the bootloader, then enter the command fastboot flashing unlock
My phone isn't "rebooted into the bootloader", it just reboots. It gives the message "< waiting for any device >" when I write fastboot flashing unlock
Click to expand...
Click to collapse
It should be a driver issue. When the phone is on and you connect it to the PC/laptop and send the command 'adb devices', does it show an alphanumeric value? Likewise, when you are booted into the bootloader by key combination and send the command, 'fastboot devices', does it show the same alphanumeric response? If so, the drivers are installed properly. If not, either you don't have the correct drivers or they are not installed properly. Try installing the drivers again after disabling driver signing in Windows on your PC (search for it on Google).

Hello, can you clarify what you mean by "booted into the bootloader by key combination"?
My problem is I cannot boot into bootloader at all.
Any attempt at doing so results in a normal boot of the device.

jonas.sj said:
Hello, can you clarify what you mean by "booted into the bootloader by key combination"?
My problem is I cannot boot into bootloader at all.
Any attempt at doing so results in a normal boot of the device.
Click to expand...
Click to collapse
Are you sure that the key combination for booting into bootloader is what you described in the first post?
1. Starting up phone while holding volume up and down buttons. Then select "reboot to bootloader".
Click to expand...
Click to collapse
I see Power plus Volume Up as the suggested one from a Google search. Try that.
If you can't even boot into the bootloader with the correct key combination, I don't know how to help you further since we are starting to go in circles. I am sorry.

Hello, thank you so much for trying to help me. It seems I can't boot into bootloader. Volume up + power gives the same result as what I did before.: It opens a "Recovery" menu where I can choose reboot to bootloader, but this option just reboots the phone.
I've been in contact with Kyocera and they say:
Thanks for contacting the Kyocera Customer Support. We will be more than happy to assist you with your concern
In this case allow us to inform you that since this device is a basic phone , it doesn't have the option to activate fastboot mode. By installing something that will change the way the phone works , that will void the warranty that came with the phone. We as manufacture can not help you to modify the software that came with the phone.
So the phone's fastboot mode has been deactivated. But since it's an android I guess it should still be possible with some workaround. I just don't know whee to start, I've been researching for a week with no result.

Something interesting ehre, maybe someone with more coding knowledge can tell what's going on.
I found the source code for the phone and located a file called recovery.c which I guess handles the menu I see when I press volume up + power button. Maybe some clue to why the phone isn't going into fastboot mode?