[Q] Fastboot oem unlock not working - General Questions and Answers

Hello,
I'm on TWRP 2.8.0.1 on an OPPO Find 7a. I want to reflash TWRP, but can't succeed since the device is not unlocked (played around with http://forum.xda-developers.com/find-7/development/rom-makulayos-rom-t2863295 and couldn't get rid of XPosed and its modules so I wanted to set up all from scratch). 'Fastboot oem unlock' says OKAY [0.000s]. But the device is still locked. How can I reflash TWRP?!
Thank you

Related

Can not unlock bootloader

I can't unlock bootloader on my OPO. I tried command: fastboot oem unlock, and fastboot mode is responded with restart to TWRP.
Also I tried a lot of things that i found forums but they did not work. I can't flash anything.
I read somewhere that I can't unlock bootloader without OS installed, but I flash Cyanogenmod 11 (not 11s, and I don't know how), and then I got this problem: https://www.youtube.com/watch?v=jlhBVj89oxU , and my bootloader is still locked.
Does anyone have solution?

[Q] "Fastboot oem unlock" Does nothing.

I have owned this phone for about 5-6 months now and have never unlocked the bootloader. I know I probably should of done that when I got it but for some reason I have been able to flash TWRP, Root the phone, and install custom roms without wiping the phone no problem. I am currently on Paranoid Android 4.6 Beta 6 and TWRP 2.8 but I wanted to go back to CM11S, and I thought maybe it's time that I unlock the bootloader. I have installed the correct drivers and when I type "fastboot oem unlock", the Command Prompt said "finished in 0.06 seconds", I then rebooted and nothing happens. I also tried a Toolkit to unlock it but that didn't do anything either. Can anyone help? I don't want to Hard Brick my phone.
Thanks
It sounds like your bootloader is already unlocked.
Try running
fastboot oem device-info
to see what it says. Post your results here and somebody should be able to help you.
The right command is:
Code:
fastboot oem device-info
Transmitted via Bacon
check this
Matt7262 said:
I have owned this phone for about 5-6 months now and have never unlocked the bootloader. I know I probably should of done that when I got it but for some reason I have been able to flash TWRP, Root the phone, and install custom roms without wiping the phone no problem. I am currently on Paranoid Android 4.6 Beta 6 and TWRP 2.8 but I wanted to go back to CM11S, and I thought maybe it's time that I unlock the bootloader. I have installed the correct drivers and when I type "fastboot oem unlock", the Command Prompt said "finished in 0.06 seconds", I then rebooted and nothing happens. I also tried a Toolkit to unlock it but that didn't do anything either. Can anyone help? I don't want to Hard Brick my phone.
Thanks
Click to expand...
Click to collapse
hello ..
i have oneplus 64 that the Tampered was true and unlock false.
i have original recovery . that i cant run not signed zip
i tried everything even install coloros ( and its failed)
finaly after alot of hours the soultion very simple
1.install throw adb sideload the signed rom ... https://www.androidfilehost.com/?fid=95747613655046106
2. its take you to factory rom
3. after that u can unlock your oneplus with fastboot oem unlock
thanks
timmaaa said:
The right command is:
Code:
fastboot oem device-info
Click to expand...
Click to collapse
Thanks, edited to fix.

Stuck after unlocking bootloader?

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

Unable to Unlock Bootloader (help!)

I've tried online guides to unlock bootloader, but messed up in some point and now I'm stuck.
1st. Download indepth test and reboot to bootloader within the app.
2nd. Tried adb devices successfully
3rd. Fastboot oem unlock nor Fastboot flashing unlock run (output: fastboot oem unlock failed "remote unknown command")
4th. Decided to make a factory reset (just becase I had to make an stupid desition)
Now I can reboot into fastboot again, because in depth test app won't install anymore. Installer says "Installation failed -An app with the same signature has already been installed"
I've unsuccessfully tried to flash stock rom from recovery but thein depth test seems to be "installed" without front user interface, also fasboot reboot bootloader get stuck in waiting for any device.
Can someone have a solution I already tried anything that comes to my mind.
Thanks.
I was able to solve the problem installing extractly the same apk.
The "fastboot oem unlock" dont work for me
What work on me 5pro is "fastboot flashing unlock"
Then flash twrp and vbmeta
To relock bootloader "fastboot flashing lock"
Source https://forum.xda-developers.com/realme-5-pro/how-to/bootloader-unlock-tutorial-t3985003
Other, might helpful source:
https://forum.xda-developers.com/realme-5-pro/development/rom-pixel-experience-t4053357

[SOLVED] Lenovo VIBE K5 A6020a41 Bootloader refuses to unlock

EDIT:
fastboot boot and fastboot flash WORK even though
fastboot oem device-info shows thebootloader is NOT UNLOCKED.
If that still doesn't work try to flash some other compatible stock rom for your model with qfil and try the fastboot boot and fastboot flash commands again, don't care about unlock status, it worked for me successfully flashed twrp and a custom rom.
Hello!
My Lenovo VIBE K5 A6020a41 refuses to unlock its bootloader.
Output of fastboot oem unlock:
FAILED (remote: 'oem unlock is not allowed')
I have enabled developer settings, usb debugging and Unlock OEM setting.
I found some posts of people with the same issue and smartphone model and they said they fixed it by flashing another stock rom (they didn't specify which).
I have flashed two or three other stock ROMs with QFIL, one was for A6020a40 model and the other two were for my A6020a41 model.
Again, I enabled all the necessary settings and still couldn't unlock my bootloader, showed the same error.
Then I tried flashing TWRP through QFIL, but when I rebooted into it, Lenovo logo showed for a second and then a black screen forever, I also tried to see if adb was able to detect it as a device in recovery, but it didn't.
Then I managed to root it with KingoRoot(I know it is not secure and it is bad and all, but I just want to flash a custom rom anyway), so I installed the official TWRP app and an app called Flashify, both flashed TWRP successfully, but I couldn't boot into the TWRP again, Lenovo logo for a second and a black screen.
Do You have any suggestions please?
Thank You.
Try
Code:
fastboot flashing unlock
what is the appropriate command on newer devices.
jwoegerbauer said:
Try
Code:
fastboot flashing unlock
what is the appropriate command on newer devices.
Click to expand...
Click to collapse
Already did. This device supports the older one only. (Should support)
Hint: Add " Lenovo VIBE K5 A6020a41 " to front of this thread's title.

Categories

Resources