Hi,
Trying to install Lineage on my old pixel 2.
The phone was bought directly from Google. When in Fastboot mode, it says on the screen that the boot loader is locked. When I run "fastboot flashing unlock" in a shell from a connected Mac, is says:
FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
So I went into the settings on the phone and the OEM unlocking option is greyed out and says "Connect to the internet or contact your carrier". It is connected to the internet, however.
Thanks for any help,
A
Same problem here. Does anyone have a solution?
Same problem too. Hard reset is supposed to solve this.... but not for me. oem unlocking option is ungreyed then , but unlocking bootloader is still impossible.
Have you connected to the Internet with the device?
Try dialing this: *#*#CHECKIN#*#* (*#*#2432546#*#*), you should get a notification that says "checkin successful" or something like that. If OEM unlocking is still greyed out, reboot the phone and check again.
V0latyle said:
Have you connected to the Internet with the device?
Try dialing this: *#*#CHECKIN#*#* (*#*#2432546#*#*), you should get a notification that says "checkin successful" or something like that. If OEM unlocking is still greyed out, reboot the phone and check again.
Click to expand...
Click to collapse
Still having problems even after doing this.
Goe11 said:
Still having problems even after doing this.
Click to expand...
Click to collapse
I don't have any other suggestions, then.
When the device connects to the internet, it's supposed to check the IMEI against a whitelist to determine whether OEM unlocking is allowed. If it doesn't do this, it's possible that the device is either defective, or is actually a carrier branded device. The latter is more likely with older phones like the Pixel 2 that have been out of production for quite some time.
Related
It was late and I was cleaning up my old OP5T, getting it ready to sell. I thought I had plugged in my OP5T, but I still had my OP6 plugged in when I ran "fastboot oem lock". Now it won't boot and I can't unlock it (I'm assuming because I can't get into the OS and "enable OEM unlocking" anymore).
Is there anything I can do?
try using search next time because its already been talked abput here https://forum.xda-developers.com/oneplus-6/help/relock-bootloader-t3798135
Actually, I DID read that. I didn't just roll off the cabbage truck. If you have time to post snippy replies (I also searched YOUR post history), then maybe you can point out where in that thread the answer to my question is. I could see if there was a thread where this specifically happened, or if it had been talked about over and over, but I couldn't find one. You do know this is a fairly new device, right? TBH, you're just being rude. To count on someone to hit the right search terms for a single thread where the info exists is just asinine.
1) I have not seen anyone with this situation on the OP6 yet
2) The OP5T had an unbrick tool
3) Most phones have a way to restore the OS to factory
If it can't be restored without calling OnePlus, then why not just say so? I'll answer for you, it's because you actually enjoy replying in such a manner. Grow up.
Have you tried the mega unbrick guide?
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Flapjack said:
It was late and I was cleaning up my old OP5T, getting it ready to sell. I thought I had plugged in my OP5T, but I still had my OP6 plugged in when I ran "fastboot oem lock". Now it won't boot and I can't unlock it (I'm assuming because I can't get into the OS and "enable OEM unlocking" anymore).
Is there anything I can do?
Click to expand...
Click to collapse
I don't think relocking your bootloader will disable the "enable OEM unlock" toggle in the OS. You may just be able to unlock your bootloader as normal again. You should be able to use the fastboot recovery method to restore your OS.
[email protected] said:
Have you tried the mega unbrick guide?
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Click to expand...
Click to collapse
I did, but I got the "software image does not exist" error. Does it matter whether I downloaded the 5.13 or 5.15 vesion?
mikex8593 said:
I don't think relocking your bootloader will disable the "enable OEM unlock" toggle in the OS. You may just be able to unlock your bootloader as normal again. You should be able to use the fastboot recovery method to restore your OS.
Click to expand...
Click to collapse
I tried several times. It throws the following error, which when searched for, always seemed to be someone forgetting to enable OEM unlocking in settings:
Code:
FAILED (remote: oem unlock is not allowed)
Success! I was able to get it to work with the drivers from this post. No other drivers worked. I also forced the COM port to the first available (in my case, COM1) vs the one it popped up on. Until I did that, I would just get a huge list of ports that had no device attached. Once I had it on COM1, it was the only device that showed up in the list. The first time after that, I got a "Sahara Communication Failed" error, but it went away after rebooting the phone back into EDL mode again.
Thanks for the help!
Flapjack said:
Success! I was able to get it to work with the drivers from this post. No other drivers worked. I also forced the COM port to the first available (in my case, COM1) vs the one it popped up on. Until I did that, I would just get a huge list of ports that had no device attached. Once I had it on COM1, it was the only device that showed up in the list. The first time after that, I got a "Sahara Communication Failed" error, but it went away after rebooting the phone back into EDL mode again.
Thanks for the help!
Click to expand...
Click to collapse
Hi buddy,
I tired to relock the bootloader and success in that but the phone stuck at fastboot mode, neither restarting to system nor to anything. Kindly help me if i can flash the stock rom in locked bootloader is so how.
THanks in adv
Did you try msm download tool ?
My OnePlus was bricked and it's bootloader is locked too, I have tried most of the steps like msm and those Bat files etc. But error is coming
"Remote : Flashing is not allowed in locked state"
Even tried that all in one tool that also can't unlock my bootloader
Now plz someone show me steps it will be a great help
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
I was using my phone normally yesterday (Saturday) 12/06, I left it charging and when I looked at it again, it was restarting non-stop. It's a Redmi Note 8, I held the power button, but it wouldn't turn on, it just went back to the bootloader screen, I didn't try to format it as I'm trying to recover my files. So I thought about unlocking the bootloader to have access to my files, I used Mi Unlock Tool, but it doesn't work because it asks me to add my account to the device (It was already added before this happened). I still have access to my account phone number, and email. But I couldn't unlock by this fastboot method, so I tried using the "fastboot oem unlock" command, which didn't work either, it showed these two messages.
'Fastboot boot command is not available in locked device'
FAILED (remote: 'Token Verify Failed, Reboot the device')
fastboot: error: Command failed
The versions of MiFlash Unlock I used were
"miflash_unlock-en-5.5.224.55" and "miflash_unlock-en-5.5.224.24".
The device is not recognized by the "Mi PC Suite".
The device still appears in fastboot devices, but not in adb devices
bump
When unlocking phone's bootloader automatically all user-data get lost.
Hint: Add Redmi Note 8 to this thread's title thus mainly owners of such phone get addressed.
jwoegerbauer said:
When unlocking phone's bootloader automatically all user-data get lost.
Click to expand...
Click to collapse
I was trying this and this [GUIDE]
jwoegerbauer said:
Hint: Add Redmi Note 8 to this thread's title thus mainly owners of such phone get addressed.
Click to expand...
Click to collapse
Ok!
When using "MiFlash Pro", I managed to reach 100% (?), but the device resets, gets stuck in the MIUI screen for 2 minutes and then resets again to the bootloader screen. I was flashing the same ROM i was using, the "V12.0.4.0.QCOMIXM".
Video flashing the ROM
It's an old phone, I wanna root it, but no matter what I do "OEM Unlock" never shows up in the settings. I've reset the thing multiple times, changed the date, messed with auto updates a lot, but nope never shows up.
Some info that's probably useful. I got this phone from straight talk (a Walmart carrier, don't ask why it's a long story yes I know it was a terrible idea, Walmart was lying to us saying we needed to buy a phone from them and I didn't want to fight), and when trying to root it a friend who knows a lot more than I do told me to enter odin mode, and instead of that, in big red text (slightly covered by the camera) it says "entering fastboot mode...", (shown below) and doing "fastboot devices" spits out "R9AN90BYY5J" as the fastboot device, so I don't know.
I tried doing it via pc but when I do "fastboot oem unlock" (because apparently its not a real samsung phone so i should use fastboot) it says "
FAILED <remote: 'unknown command'>
Fastboot: error: Command failed"
from what I've heard (from a source I don't remember, and the same friend) apparently you just can't root us model phones, I tried all of this on my Galaxy A50 as well (I got it from inland cellular and apparently it's a verizon model phone, might have something to do with me going through verizon I don't know, but it is a real samsung phone) and oem unlock still never shows up. So am I just screwed?
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.