Can't unlock bootloader OnePlus 8 - OnePlus 8 Questions & Answers

I'm having trouble unlocking the bootloader, I've tried 3 times and can't figure it out, when I input (Fastboot oem unlock) it just says "waiting for device" and does nothing, what should I do??

It's a driver issue, fastboot doesn't even see your device. Get fastboot drivers installed, theres a trillion tutorials on XDA and other places for how to do that if you're not sure how.

Related

Bootloader unlock issue.

Hello all. I'm new to the forum but not so new to rooting and such. I am in the process of rooting my Nexus 5 via Ubuntu and keep getting stuck at the bootloader command "./fastboot oem unlock" I've tried about 30 different ways and searched and searched. The bootloader will not show the next screen where it says Yes or No. Fastboot and adb both recognize the device in Terminal when connected. I type in the correct commands, get three dots, then it just sits. Nothing happens. Ive re traced my steps and started over at least 20 times. LMY48l Android 5.1.1 Kernal 3.4.0. Any help would be greatly appreciated. Thanks!

Fastboot oem unlock freezes phone

It's my first post on this forum, so I'm saying hello.
I've recently bought Nexus S which after turning on is stuck on Google logo, but I could enter fastboot and recovery. But it has locked bootloader. I tried unlocking it by "fastboot oem unlock" but it asks me if I'm sure and then i click yes it freezes (phone not fastboot). I tried it using different drivers, machines, operating systems, cables, but still nothing. Unbrick tool by AdamOutler says that "device not found". When trying to flash stock image by Odin on the phone there is message if I'm sure that I want to unlock bootloader but with nothing to choose, and after while it shows by red characters that system image was verified.
I don't know past of this phone. (I have no idea, which version of android was it running)
I'd be extremely helpful for any kind of advice.

OEM unlock Unknown command

I am about to lose my mind if I cant figure this out.
I have an LG Stylo 2 Plus model LG-K530F, and i have been trying to root it for several hours
I have certainly clicked the "Enable OEM Unlock" option, but no matter how many times I try the command on ABD, it will not work
I have made sure that my computer recognizes the device, and from the command prompt can successfully boot it into fast boot with "adb reboot bootloader"
I've poured through all sorts of threads and forum posts about other lg stylo 2's with different model numbers, I've factory reset the phone preemptively from suggestions, yet no matter what I try, I cannot get past "fastboot oem unlock"
And just to be sure, I have done a "fastboot flashing get_unlock_ability" just to make absolutely sure I allowed to unlock it.
It just *won't* for some reason
"fastboot getvar unlocked" tells me that it is not unlocked already
"fastboot oem lock" works and says its already locked
Does anyone have any help for me? Any suggestions? A thread or post I haven't seen yet?
The phone itself seems to imply that i need a code from LG to unlock it, there is a part on the fastboot menu that says "2) Write Unlock Key - fastboot flash unlock unlock.bin" but the LG developer website does not support this phone, so i wont be able to get one from them
lol yes you need the unlock bin from LG...
good luck

T-Mobile OP8 5g (IN2017); I have my unlock token from T-mobile, but I'm unable to flash it.

Just as the title says; I have the unlock token and I've tried everything I can think of to flash it and nothing's worked. I have OEM unlocking enabled, the phone is permanently carrier unlocked, USB debugging is enabled, I've made sure to download a new version of Platform Tools, I've moved the .bin file to the same directory as Platform Tools, the phone comes up in ADB and fastboot when I check, it just won't write and I can't figure out why... usually it just hangs at sending 'cust-unlock' etc. but never progresses past that. Can anyone help me figure this out?
EDIT: Resolved! Me being dumb, not realized I'd only tried USB 2.0 ports; using a 3.2 port did the trick instantly.
Have you tried other fastboot commands like - "fasboot reboot bootloader" to ensure your fastboot is working properly and the correct drivers are installed?
FoxyDrew said:
Have you tried other fastboot commands like - "fasboot reboot bootloader" to ensure your fastboot is working properly and the correct drivers are installed?
Click to expand...
Click to collapse
Yea, that's what's baffling; I can jump back and forth between adb and bootloader/fastboot pretty easily but I just can't send the unlock token. I have seen a couple weird errors though, like if I'm in bootloader and do 'fastboot OEM unlock' and it fails (since I can't get the token to flash) and afterward I try 'fastboot devices' sometimes fastboot crashes to the 'press any key to reboot' screen.
Could this just be an outdated driver issue? I thought they were up to date...
Have u try using other cable or even try on different PC?
hendavi said:
Have u try using other cable or even try on different PC?
Click to expand...
Click to collapse
I've tried multiple USB ports and the original cable as well as others; I've confirmed commands like 'ADB reboot bootloader' and 'fastboot reboot bootloader' work and I've even updated the ADB/fastboot drivers just in case... still nothing. I haven't tried a different PC yet but I suppose that's next
No matter what I try, this is what I get every time I try it from the bootloader. I've tried from bootloaderd/recovery, but it fails there too saying something like 'writing not allowed' or something... I have OEM unlock turned on and it's carrier unlocked, so I have no clue what's stopping this from working.
What's really weird is I actually got this to work once before on this same device, but had to reset the phone back to stock T-Mobile branded software using the MSM tool; the first time around, I was able to enter the unlock token and just unlock it like normal (fastboot OEM unlock). Now that I've reset the phone and I'm trying again, it just won't work... really perplexed on this one.
UPDATE
I had to pull up an image of my mobo's io panel because I couldn't remember and couldn't see which ports were which; once I moved the cable to a USB 3.2 port, it worked... I guess I'd only been trying it on USB 2.0s before so it didn't work.
Thanks for your help!
I had same issue on my OnePlus 8 TMobile. Have to disable driver signatures. This shows you how. Yes, the link is for a diff phone, but just follow the disable driver signatures part of it and it will then show up in fastboot
https://forum.xda-developers.com/t/...owing-up-in-fastboot-mode-windows-10.4194491/
EDIT: False alarm. I was sent an unlock code for an older device I have instead of the one I just bought. Should've double checked it first.

What Am I Doing Wrong? (Rooting/Bootloader Unlocking)

Hopefully someone here can help me through my problem,
Device Details: BLU G60/BLU VIVO X6
Android 9/Pie
OEM Unlocking: Allowed
USB Debugging: Enabled
Hey, I'm pretty new to this way of customizing my phone (adb, root, roms etc), and I'm trying to root my phone with Magisk. I have a patched boot.img, my bootloader is allowed to be unlocked and I'm doing exactly what the root guide says (https://www.mobilewithdrivers.com/magisk-root/blu-g60-64gb-3gb-ram) but it wont work, I keep getting different errors and I see all my fellow droid users so happy with their rooted devices, I want to root mine too. So what I'm asking is; Can someone with an actual brain (Mine wont work) to try and help me out or walk me through step-by-step?
Thanks for reading!
Some of the issues I have:
"adb reboot booter" and "fastboot reboot bootloader" both reboot the device but in the top left corner it says "fastboot mode" and just freezes, when I do any command it just says "device null" but when I reconnect the USB cable, it just powers off.
"fastboot flashing unlock" results in "FAILED (remote: Not implemet.)" Yes, spelt like that.
"fastboot oem unlock" says, unkown cmd...
Wrong driver in use. Use the one provided by BLU suitable to your phone.
i couldnt find any drivers for the exact device, only google ones...
any ideas?
If you have a mac, you could try that. They usually don't require drivers.

Categories

Resources