Hi Everyone,
I'm having some difficulties unlocking my Pixel 3a to install a ROM.
I have activated developer options, activated OEM Unlocking, but when I get into the bootloader, there is no option to unlock the bootloader itself...
The only options I have are :
Start
Power off
BarCode
Recovery Mode
Restart Bootloader
I have no idea what's happening and haven't found anything online that would even hint at what is wrong. Does anyone have any idea about what is going on with this ?
Thanks for your help.
when booted to bootloader you need to execute the command
'fastboot flashing unlock'
see here:
How to Unlock the Bootloader on Your Pixel 3a
The first thing you'll always have to do before getting your customization game on with most phones is to unlock the bootloader. Doing so opens the true potential of the device, allowing you to root, install TWRP, Magisk, custom ROMs, and other mods. No matter your wants or needs, there's no way...
android.gadgethacks.com
To Unlock bootloader
- Install adb and fastboot on your PC. https://dl.google.com/android/repository/platform-tools-latest-windows.zip
- Run through the initial setup if you haven't already, if you haven't don't bother logging into your google account.
- Enable dev options(settings>about phone>build number>tap it 7 times).
- Go into settings>system>advanced>dev options>oem unlocking, click the toggle.
- While still in dev options scroll down a little and enable usb debugging.
- Plug your phone into your pc. If or when the phone asks you to trust the computer make sure to check the "always allow this computer" check box.
Open up command prompt type into the cmd window
adb reboot bootloader
The phone will reboot into fastboot mode.
Now type into the cmd window
fastboot devices
See if it lists a device, if not you need to install the drivers I linked to. If you had to install the drivers try the fastboot devices command again after installing them, it should list the device now.
type in:
fastboot flashing unlock
You will then have to use the phone to select yes to the unlock. you use the volume keys to select and the power button to confirm.
Your bootloader is now unlocked and you follow one of the root methods.
reboot your phone
Related
Hi everyone,
Today I decided to root my Mate 9.
I started out with turning 'OEM unlock' on and usb debugging. With ADB installed and the huawei drivers, I began to unlock my bootloader. On the 'EMUI Huawei' homepage I filled out my device details and obtained an unlock code. I opened ADB and checked with 'adb devices' if my device was there. It was. So I continued with typing 'adb reboot bootlader'. After that I typed 'fastboot devices'. My device was still showing up. I typed 'fastboot oem unlock CODE (with the code). On my screen I pressed 'Yes'. Bootloader unlocked.
After this step I tried to flash twrp with the command 'fastboot flash recovery xxxx.img'. I couldn't continue because every adb/fastboot command keeps failing (remote: command not allowed). Now when I boot up my phone it shows 'your device has been unlocked and can't be trusted'. Phone=unlocked, FRP=locked. I can't do anything.
Device: Mate 9 L29C432B198
What did I do wrong or what did I missed? :crying:
I had this issue at first to had to redownload the original rom via the phone recovery this will fix the frp lock then u have to unlock and flash twrp 3.1.01 that is linked in the threads on here
Did it format after it unlocked?
You can try fastboot oem relock UNLOCKCODE
Then go to Settings -> Dev options -> enable OEM Unlocking
Then unlock again.
It probably will fail though if FRP is locked, but worth a shot.
Edit: It's supposed to say
PHONE Unlocked FRP Unlock
I posted this in the appropriate forum but this phone is so old I've not received any response.
So I've decided to root and customize my Z2 Force and want to unlock the bootloader to get TWRP installed. All device side settings are correct (USB Debug, OEM unlock etc.) in developer mode. ADB commands are working fine as I can see my SN when using ADB Devices command. I then reboot to the bootloader through ADB (adb reboot bootloader) and it works fine and my Z2 boots into the bootloader. Then I try to get the unlock code (fastboot oem unlock) and I get a message after trying to run the command: access denied. I started my CMD window using run as admin - no help. Installed ADB all over again with new generic drivers and moto drivers - no help. Even installed everything in the root directory on my hard drive - no help
I don't understand why I'm getting this message. I've unlocked and rooted all my phones over the years but they've all been HTC. Never messed with a moto phone before. Anyone think this is a permalocked bootloader version - MODEL:XT1789-04 TYPE:M29E2
Things I have not tried yet:
Another computer
Tested fastboot command on one of my other phones
Any help is appreciated.
theandies said:
I posted this in the appropriate forum but this phone is so old I've not received any response.
So I've decided to root and customize my Z2 Force and want to unlock the bootloader to get TWRP installed. All device side settings are correct (USB Debug, OEM unlock etc.) in developer mode. ADB commands are working fine as I can see my SN when using ADB Devices command. I then reboot to the bootloader through ADB (adb reboot bootloader) and it works fine and my Z2 boots into the bootloader. Then I try to get the unlock code (fastboot oem unlock) and I get a message after trying to run the command: access denied. I started my CMD window using run as admin - no help. Installed ADB all over again with new generic drivers and moto drivers - no help. Even installed everything in the root directory on my hard drive - no help
I don't understand why I'm getting this message. I've unlocked and rooted all my phones over the years but they've all been HTC. Never messed with a moto phone before. Anyone think this is a permalocked bootloader version - MODEL:XT1789-04 TYPE:M29E2
Things I have not tried yet:
Another computer
Tested fastboot command on one of my other phones
Any help is appreciated.
Click to expand...
Click to collapse
The process to unlock a moto phone is a bit different. OEM commands are as it says, defined by the OEM. They need to be precise and functional. The command:
Code:
fastboot oem unlock
alone will not work.
Step1:
Instead, You should enter:
Code:
fastboot oem get_unlock_data
You will get an unique 131 ID string that looks for example like this:
Code:
(bootloader) 0000000000000000000000000000001
(bootloader) 0000000000000000000000000000002
(bootloader) 0000000000000000000000000000003
(bootloader) 0000000000000000000000000000004
(bootloader) 0000005
Copy the output to a text editor and delete the (bootloader) and the spaces in between, so it's one whole string.
Step2:
Visit the official Moto unlock website. Sign-in with your account, you will be using the E-mail used to create said account to receive the unlock key. Paste the edited 131 ID string and click Can my device be unlocked? button. If it is unlockable, then a conformation page will appear asking for consent and warranty bla bla bla.... Just read it and accept.
Step3:
When you click unlock, you will receive a KEY through your E-mail attached to the moto account used. Save that E-mail somewhere offline, as it can be used to re-unlock the bootloader in the future if you relock it. Connect your device in fastboot again and type:
Code:
fastboot oem unlock KEY
Where KEY is the one you got in the E-mail.
Done!!! Enjoy your freedom , also check the mark near my answer if it solved your question so others don't have to search for long.
Thanks for your reply. Yes I wrote the fastboot command wrong in my post.
The problem I'm having is even when using the fastboot command you posted I still get "access denied" when using fastboot commands. ADB works fine allowing me to reboot into the bootloader through the command prompt/USB as in ADB devices.
theandies said:
Thanks for your reply. Yes I wrote the fastboot command wrong in my post.
The problem I'm having is even when using the fastboot command you posted I still get "access denied" when using fastboot commands. ADB works fine allowing me to reboot into the bootloader through the command prompt/USB as in ADB devices.
Click to expand...
Click to collapse
As long as in Android -> Settings -> Developer options the option "OEM unlock" isn't got enabled - and phone got rebooted afterwards - you receive the reported error.
OEM unlocking is turned on in developer settings
I'll post up some screenshots soon. Right now I'm on day three of work on the 12 hour night shift.
Hi, i am loading booting to bootloader from adb with commnad (adb reboot bootloader) this isnt working, only restart its instantly switch to normal os, any ideas ?
Run
Code:
adb reboot
or
Code:
fastboot reboot
oh sorry man, i am idiot, and i am say it wrong.. I trying boot to fastboot but not working instantly switch to os, any ideas please ?
Unlock bootloader if not done yet.
where i unlock bootloader ? In developer settings ? (i have unlocked)
Enabling OEM Unlock in Developer options doesn't unlock the bootlader, it simply prepares the bootloader to get unlocked via fastboot command.
More info here:
How to Unlock Bootloader via Fastboot on Android
Unlocking the bootloader via Fastboot is the easiest thing to do. But not all Android devices support straightforward bootloader unlocking. Many manufacturers put up a setup on their devices to let…
nerdschalk.com
xXx yYy said:
Enabling OEM Unlock in Developer options doesn't unlock the bootlader, it simply prepares the bootloader to get unlocked via fastboot command.
More info here:
How to Unlock Bootloader via Fastboot on Android
Unlocking the bootloader via Fastboot is the easiest thing to do. But not all Android devices support straightforward bootloader unlocking. Many manufacturers put up a setup on their devices to let…
nerdschalk.com
Click to expand...
Click to collapse
Only I have a small problem I don't unlock my bootloader via fastboot when it doesn't work :/ It immediately jumps to my system when I boot fastboot, even with a command like ,,adb reboot fastboot"
Matyas66055 said:
Only I have a small problem I don't unlock my bootloader via fastboot when it doesn't work :/ It immediately jumps to my system when I boot fastboot, even with a command like ,,adb reboot fastboot"
Click to expand...
Click to collapse
I have new thread, where i am writing all info :/ https://forum.xda-developers.com/t/zte-blade-a7-2019-fastboot-mode-missing.4462035/
I don't know if you are still interested in accessing Fastboot but you can access it using a specific firmware version.
Still, let me tell you that unlocking the bootloader is virtually impossible. Since the well-known generic method doesn't work for the SoC SC9863A, you need to have a special Fastboot's program version and a dedicated private key that only they provide.... and I emphasize the word "dedicated" since apparently ZTE did not use a generic key to sign their ROMS. At least on this device.
Unless they decide to release the key or give support to unlocking the bootloader, all we can do is wait for them to change their minds. Because they don't want to provide it. I know because I tried to order it several times.
I'm trying to install LineageOS 19.1 but I'm having trouble as stated in the title. Every guide I've read mentions that I need to flash TWRP recovery in which case I need to go in fastboot. Problem is once in fastboot I cannot progress any further. I'm not sure what step I missed or what I'm missing. I can detect my device with "adb devices" while the device is on and "adb reboot bootloader" puts it into fastboot (notification light turns blue) but any other commands just result in "waiting for any device" after going into fastboot. Here's some additional info:
- Model is SO-04J Docomo
- Can confirm that bootloader is unlocked (OEM unlocking can be toggled on/off)
actually, you have to unlock your bootloader first (which erases DRM Keys to take photos etc) and you surely haven't done that YET... Just follow the Instructions from Sony and you might wanna consider Backing up DRM Keys first, before you unlock your Bootloader.
1. Type in this number into your Dialer, if it (Bootloader unlocked) says YES, then your Bootloader is already unlocked but if it says, that Bootloader unlock is supported, backup your DRM Keys first and then
2. "Install the device drivers and platform tools" (from Sonys Website) (i just post the link to the driver for you to make it easier)
If you're using Windows for this, I mentioned it before (I had the same Problem as you do) And figured out, that you have to tap on your Device first IN SYSTEM MAINTAINCE (mine was labeled "Android") then Update driver, search on PC, select from List, choose ADB Interface (Samsung Android ADB Interface) and go ahead and unlock bootloader first (which ensures, TWRP CAN be flashed and to install custom ROM)
I just unlocked bootloader on my S7 and was installing magisk and did everything and got the AP patched magisk file etc, and got to Odin and started flashing only for it to fail with this error
Im not sure what to do as this is the correct verison firmware, I unlocked the bootloader, and flashed everything occardinginly
Did you follow the Magisk Installation Instructions?
After unlocking the bootloader, you have to let the device boot and confirm that OEM Unlocking is still available. Vaultkeeper/Knox Guard are still active even after unlocking the bootloader.
V0latyle said:
Did you follow the Magisk Installation Instructions?
After unlocking the bootloader, you have to let the device boot and confirm that OEM Unlocking is still available. Vaultkeeper/Knox Guard are still active even after unlocking the bootloader.
Click to expand...
Click to collapse
Hmm yeah that's what I thought but thought it was already so because...
I unlocked bootloader in dev options but when I boot into download mode it doesn't give me the prompt to fully open up the device it's just normal download mode :/
I tried booting into recovery and "restart to bootloader option" doesn't even exist, so I had to do it via pc
What should I do?
jacobjake7 said:
Hmm yeah that's what I thought but thought it was already so because...
I unlocked bootloader in dev options but when I boot into download mode it doesn't give me the prompt to fully open up the device it's just normal download mode :/
I tried booting into recovery and "restart to bootloader option" doesn't even exist, so I had to do it via pc
What should I do?
Click to expand...
Click to collapse
The OEM Unlocking toggle in Developer Options does not unlock the bootloader on its own. It's simply a "safety" that when enabled allows you to unlock the bootloader.
When you're in download mode, do you see "OEM LOCK" near the top of the screen? Does it say "On"?
To unlock the bootloader, unplug any cables and shut the device down.
Then, hold both VOLUME buttons, and while holding them, insert the USB cable from your PC. The device should start with a prompt - Volume Up for download mode, long press Volume Up for unlock mode, and Volume Down to cancel. Follow the prompts to unlock your device. This will wipe all user data.
Once you've unlocked the bootloader, follow the instructions in the link I posted to ensure Vaultkeeper/Knox Guard are fully disabled.
V0latyle said:
The OEM Unlocking toggle in Developer Options does not unlock the bootloader on its own. It's simply a "safety" that when enabled allows you to unlock the bootloader.
When you're in download mode, do you see "OEM LOCK" near the top of the screen? Does it say "On"?
To unlock the bootloader, unplug any cables and shut the device down.
Then, hold both VOLUME buttons, and while holding them, insert the USB cable from your PC. The device should start with a prompt - Volume Up for download mode, long press Volume Up for unlock mode, and Volume Down to cancel. Follow the prompts to unlock your device. This will wipe all user data.
Once you've unlocked the bootloader, follow the instructions in the link I posted to ensure Vaultkeeper/Knox Guard are fully disabled.
Click to expand...
Click to collapse
When I boot into download mode it just shows a normal download screen with no text in the top left, no nothing, it's just normal download. I don't get the option to unlock the bootloader as I've said in my last post