Hello Oneplus friends!
My goal has been to get myself on the LineageOS ROM on these forums...and I miss the olden days just a bit =).
I got T-Mo to do the SIM unlock thing for me. OnePlus gave me the unlock_code.bin earlier this morning. It was like Christmas all over again! I ran "flash cust-unlock unlock_code.bin
I followed the instructions as best as I could to copy/paste all the commands from the main post, but doing "flash system system.img" turned into a bit of a mess, as it apparently didn't see the system partition to wipe. Naturally the phone wouldn't boot after this, so a bit more googling found me this page: https://www.oneplus.com/support/softwareupgrade/details?code=PM1605596915581. And, it did the wipe-and-reload thing that I expected it to, and I'm back to stock ROM...but, with a locked bootloader.
"No problem, the hard parts are all taken care of already!"
I go to the network settings, and the phone is showing as SIM unlocked. I enable USB debugging and OEM unlocking, reboot to make sure it takes effect, and then I reboot into the bootloader.
I then do "fastboot flash cust-unlock unlock_code.bin", like last time. I then get the following:
PS C:\platform-tools> fastboot flash cust-unlock unlock_code.bin
target reported max download size of 805306368 bytes
sending 'cust-unlock' (0 KB)...
OKAY [ 0.013s]
writing 'cust-unlock'...
(bootloader) Device is unlocked.
OKAY [ 0.010s]
finished. total time: 0.029s
That should mean the bootloader gets unlocked, right? I get the "are you sure" prompt, affirm it, and then I have an unlocked bootloader? That's what I'd expect...but the phone camps out in fastboot with the device state saying "locked", no matter how many times I reboot and redo this - same behavior. My computer says the phone has been unlocked, but the phone doesn't actually unlock.
Thank you for your consideration of this issue, and I hope this thread helps someone else in the future.
(edit: clarification - though the 'sending cust-unlock' command says 0KB, the file is 288 bytes so it is likely a rounding error. The file does have actual data in it)
Edit 2: aaaaand I'm a moron. Once that flash is done, THEN the "fastboot oem unlock" command works. Issue that, the confirmation prompt comes up, you've got an unlocked bootloader.
I'm leaving the thread here in case it helps someone else with lapsed memory; if the mods want to delete it, no harm, no foul.
Haha, I was about to suggest running the actual command, until I got to your edit.
Glad you solved this error.
I wish T-Mobile would let me unlock my phone!
Related
My carrier (C Spire) has found a problem with the device on their network that makes the device lose it's signal all the time. They claim it is a device problem anyway. I have unlocked the bootloader on the phone, but have not flashed any roms or made any other changes to the phone. Just the unlocked bootloader. They have said that since they know it is a problem with the device, they will let owners come in and exchange the phone for a Galaxy SIII free and clear. The only stipulation is it has to be in like new condition. My phone is perfect except for the unlocked bootloader. They'd probably never notice if it wasn't for that notification screen when the phone reboots that would tell them. I need to relock the bootloader to make that screen go away.
So, my question is, how do I do that? I've tried doing 'fastboot oem lock' but that doesn't work.
This is what I get when I try:
Code:
C:\Users\adear\AppData\Local\Android\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.014s]
finished. total time: 0.016s
If I run the command as it suggests I get:
Code:
C:\Users\adear\AppData\Local\Android\android-sdk\platform-tools>fastboot oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 0.246s]
finished. total time: 0.248s
I'm not sure what to do to get it to lock again.
Can anyone please help?
The problem is, you've unlocked it 'officially' from Moto... so it's registered in the database as unlocked.
You can try to change the boot logo, I haven't tried yet... Supposedly you can to get rid of that annoying screen.
Maybe you will just have to take it in and hope they don't reboot it. Kinda sucks that we have official unlocks now, because they can now easily track who has unlocked their phones and who hasn't :/
According to Moto, you can relock the bootloader, although the warranty remains voided. I know Moto knows about it, but I doubt very much that the carrier is going to go so far as to check it.
I just need to know why the 'fastboot oem lock' command didn't work. And what I can do to relock it.
adear11 said:
According to Moto, you can relock the bootloader, although the warranty remains voided. I know Moto knows about it, but I doubt very much that the carrier is going to go so far as to check it.
I just need to know why the 'fastboot oem lock' command didn't work. And what I can do to relock it.
Click to expand...
Click to collapse
Did you try using the same key to unlock to relock?
I've never bothered relocking...
arrrghhh said:
Did you try using the same key to unlock to relock?
I've never bothered relocking...
Click to expand...
Click to collapse
Is the key required to relock? I had not tried using it.
adear11 said:
Is the key required to relock? I had not tried using it.
Click to expand...
Click to collapse
I said I've never tried to relock.
It makes sense tho. Same process to relock as it was to unlock. Give it a shot, what do you have to lose.
arrrghhh said:
I said I've never tried to relock.
It makes sense tho. Same process to relock as it was to unlock. Give it a shot, what do you have to lose.
Click to expand...
Click to collapse
Just gave it a try, got the same result. "Fail: Please run fastboot oem lock begin first!"
adear11 said:
Just gave it a try, got the same result. "Fail: Please run fastboot oem lock begin first!"
Click to expand...
Click to collapse
You entered fastboot oem lock begin <key>?
arrrghhh said:
You entered fastboot oem lock begin <key>?
Click to expand...
Click to collapse
When I do 'fastboot oem lock begin [key]' I get "(bootloader) Ready to flash signed images".
From here, if I do 'fastboot oem lock' again, I get "Re-Lock Failure. See display." On the phone's display, I get:
Code:
No valid PIV block in SP for system
piv validation failed (system)
Re-lock failure
Hrm. I was poking around Moto's FAQ's and community site, and they talk about relocking - but not in detail unfortunately. They cryptically state that they will not release any stock recoveries at this time - so perhaps if you don't have the stock recovery, you can't relock...?
I would post up on Moto's forums or call their support... Not sure how much help they will be, but their website leaves much to be desired about the relocking process...
oh dear some anonymous person had pasted motorola's flashing script, perhaps you can use it to figure out how to fix your device
http://pastebin.com/Ca8wcGAv windows
http://pastebin.com/SnxrbdaW linux/mac
im just really glad i happened to be browsing around pastebin and found that in it.
shabbypenguin said:
oh dear some anonymous person had pasted motorola's flashing script, perhaps you can use it to figure out how to fix your device
http://pastebin.com/Ca8wcGAv windows
http://pastebin.com/SnxrbdaW linux/mac
im just really glad i happened to be browsing around pastebin and found that in it.
Click to expand...
Click to collapse
so, if one were interested in using this anonymous persons script, how would one proceed?
adear11 said:
so, if one were interested in using this anonymous persons script, how would one proceed?
Click to expand...
Click to collapse
i would imagine gathering all the files and putting them in the proper spots/folders would assemble a replica of this script. i was just mentioning you should look thru to see if there is anything taht helps you tho
In short, in order to relock the bootloader, you have to flash signed software in the process.
Ugh why did I try this lol.. Still having problems. I restarted my computer and that fixed the problem "waiting for device" now in cmd it will at least recognize the phone BUT, I get this trying to figure out some information
getvar:cid FAILED (command write failed (unknown error))
It says it's unlockable, but fails.
Code:
platform-tools_r29.0.0-windows\platform-tools>fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 1
OKAY [ 0.003s]
Finished. Total time: 0.009s
So then:
Code:
platform-tools_r29.0.0-windows\platform-tools>fastboot flashing unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
platform-tools_r29.0.0-windows\platform-tools>fastboot flashing unlock_critical
FAILED (remote: 'unknown command')
fastboot: error: Command failed
If I factory reset, then oem unlock is allowed, but when I simply reboot to the bootloader, and start the phone after, it is greyed out. I feel like I am getting a false positive, except for the command above literally says it should be unlockable. fastboot oem unlock also does not work. I am skipping all options during setup and using Wifi as well only.
Any ideas?
There's already a thread about it. More than likely your rma is a Verizon phone and they can't be unlocked. Search and you shall find
I highly suspect Verizon model. A quick way to solve this is contact Google Pixel Support and give them the IMEI of the phone and ask for them to confirm if it is the VZW or Google Edition. I've done this a couple times to find a used Google Edition phones cause I've had a few duds. Phone support is the quickest, chat support has protocol that might make it hard for them to disclose that information.
AgentSoul said:
I highly suspect Verizon model. A quick way to solve this is contact Google Pixel Support and give them the IMEI of the phone and ask for them to confirm if it is the VZW or Google Edition. I've done this a couple times to find a used Google Edition phones cause I've had a few duds. Phone support is the quickest, chat support has protocol that might make it hard for them to disclose that information.
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-2/help/oem-unlocking-grayed-vzw-pixel-2-t3776763
Disclaimer : I don't know Nokia fixed this or not and will this work for you guys but it worked for me and i want the developers to provide mass support for our Nokia 8.1 coz this is highly capable devices made stupid by HMD and fed up of lack of support by nokia
IMPORTANT: Do not verify your device on hmd unlocker app or it won't work for sure
step 1: go to website https://www.nokia.com/phones/en_int/bootloader sign in via Google(i did but don't think so it matters)
Step 2: Fill in required details asked and proceed directly on website and the website alone...do not verify ur imei on the nokia bootloader unlock app or this will not work 100%
Step 3: Agree all the terms and validate...u will get the unlock key from hmd global on email by which u signed in on Step 1
I am attaching the pics of the key i got...also it says it is the key for Nokia 8 but that's typo I guess but I assure u it works coz I unlocked my device also I relocked the bootloader and all the widevine works perfect after relocking the bootloader so no worries if you want to go back to stock also
I REQUEST ALL THE DEVELOPERS IF THIS WORKS FOR U GUYS PLEASE PLEASE SHOW CUSTOM ROMS AND RECOVERY SUPPORT FOR OUR NOKIA 8.1
THANKS IN ADVANCE
Is there any advice that ROM cannot be upgraded ? My condition is : I followed your steps to do but I couldn't flash unlock key. I returned system and found the "OEM unlock" cannot be enabled. That's why I cannot flash my unlock key.
not working
Code:
# fastboot flash unlock unlock.key
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.003s]
writing 'unlock'...
FAILED (remote failure)
finished. total time: 0.007s
Kris Chen said:
Is there any advice that ROM cannot be upgraded ? My condition is : I followed your steps to do but I couldn't flash unlock key. I returned system and found the "OEM unlock" cannot be enabled. That's why I cannot flash my unlock key.
Click to expand...
Click to collapse
Maybe its a possibility but low...although just found out yesterday that it depends on which production batch ur phone is made in....Nokia 8.1 manufactured in old batches have unlockable bootloader coz there imei is properly written
So its upon luck....which batch ur phone belongs to
dantemason said:
not working
Code:
# fastboot flash unlock unlock.key
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.003s]
writing 'unlock'...
FAILED (remote failure)
finished. total time: 0.007s
Click to expand...
Click to collapse
Yea mate then its end for you...unfortunately but did u have the option to turn OEM unlock on developer options...
Sanket Kalore said:
Yea mate then its end for you...unfortunately but did u have the option to turn OEM unlock on developer options...
Click to expand...
Click to collapse
Yes I have the OEM unlock on developer options, but it grayed out and not able to switch on.
And I watched the video in the telegram group you posted, executed the same command, but just didn't work.
Like you said, maybe it's end for me :crying:
Code:
$ fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
finished. total time: 0.001s
dantemason said:
Yes I have the OEM unlock on developer options, but it grayed out and not able to switch on.
And I watched the video in the telegram group you posted, executed the same command, but just didn't work.
Like you said, maybe it's end for me :crying:
Code:
$ fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
finished. total time: 0.001s
Click to expand...
Click to collapse
Well mine is also greyed out but I had enabled it in last update so it stayed on but grey
Sanket Kalore said:
Disclaimer : I don't know Nokia fixed this or not and will this work for you guys but it worked for me and i want the developers to provide mass support for our Nokia 8.1 coz this is highly capable devices made stupid by HMD and fed up of lack of support by nokia
IMPORTANT: Do not verify your device on hmd unlocker app or it won't work for sure
step 1: go to website https://www.nokia.com/phones/en_int/bootloader sign in via Google(i did but don't think so it matters)
Step 2: Fill in required details asked and proceed directly on website and the website alone...do not verify ur imei on the nokia bootloader unlock app or this will not work 100%
Step 3: Agree all the terms and validate...u will get the unlock key from hmd global on email by which u signed in on Step 1
I am attaching the pics of the key i got...also it says it is the key for Nokia 8 but that's typo I guess but I assure u it works coz I unlocked my device also I relocked the bootloader and all the widevine works perfect after relocking the bootloader so no worries if you want to go back to stock also
I REQUEST ALL THE DEVELOPERS IF THIS WORKS FOR U GUYS PLEASE PLEASE SHOW CUSTOM ROMS AND RECOVERY SUPPORT FOR OUR NOKIA 8.1
THANKS IN ADVANCE
Click to expand...
Click to collapse
UPDATE: 5 guys successful unlocked with this method no need of enabling OEM unlock option just go ahead and follow the instructions of nokia gives after sending key.
I have an error:
fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.000s]
writing 'unlock'...
FAILED (remote failure)
finished. total time: 0.015s
Any solution?
Thanks
i reached out to nokia care and below was the response
Nokia mobile care
I would like to inform you that unlocking the bootloader is not available at this moment
***********
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.000s]
writing 'unlock'...
FAILED (remote failure)
finished. total time: 0.016s
thx it did work on my phone.
Hmmm, looks like site isn't working anymore.
I check the checkbox, but the log in to continue button stays greyed out, tried 3 different browsers.
Sadly, Looks like I have to pay for unlock. Am looking in lineageos development for this device. Too much free time after loosing job
Sanket Kalore said:
Disclaimer : I don't know Nokia fixed this or not and will this work for you guys but it worked for me and i want the developers to provide mass support for our Nokia 8.1 coz this is highly capable devices made stupid by HMD and fed up of lack of support by nokia
IMPORTANT: Do not verify your device on hmd unlocker app or it won't work for sure
step 1: go to website https://www.nokia.com/phones/en_int/bootloader sign in via Google(i did but don't think so it matters)
Step 2: Fill in required details asked and proceed directly on website and the website alone...do not verify ur imei on the nokia bootloader unlock app or this will not work 100%
Step 3: Agree all the terms and validate...u will get the unlock key from hmd global on email by which u signed in on Step 1
I am attaching the pics of the key i got...also it says it is the key for Nokia 8 but that's typo I guess but I assure u it works coz I unlocked my device also I relocked the bootloader and all the widevine works perfect after relocking the bootloader so no worries if you want to go back to stock also
I REQUEST ALL THE DEVELOPERS IF THIS WORKS FOR U GUYS PLEASE PLEASE SHOW CUSTOM ROMS AND RECOVERY SUPPORT FOR OUR NOKIA 8.1
THANKS IN ADVANCE
Click to expand...
Click to collapse
It doesn't work with 8.3 (invalid IMEI)
mingkee said:
It doesn't work with 8.3 (invalid IMEI)
Click to expand...
Click to collapse
Maybe try Nokia 8.3 forums this is tested for Nokia 8 and 8.1 only but thanks for informing
simboy1234 said:
i reached out to nokia care and below was the response
Nokia mobile care
I would like to inform you that unlocking the bootloader is not available at this moment
***********
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.000s]
writing 'unlock'...
FAILED (remote failure)
finished. total time: 0.016s
Click to expand...
Click to collapse
Check 4th post
Moderator Announcement: Thread has been cleaned from advertisement of paid unlock services, which is not accepted on XDA!
Hi! Does anyone know how to lock the bootloader?
Previously, I experimented with installing GSI (PixelExperience, Havok OS, etc.). But as it turned out, the original system is much more stable than the GSI (although I may not have found the correct GSI
I want to return the phone to the state it was before unlocking the bootloader. That is, now I have the bootloader in the "unlocked" state. And I want it to be "blocked". Thus, the phone will be almost in its original form.
So ive been trying to get my OP 8t Tmobile variant bootloader unlocked, sim unlocked it , requested the unlock token from one plus , finally got it, been trying to flash the token but i keep getting a error, any help would really appreciate it a lot.
Detailed error code:
target reported max download size of 805306368 bytes
sending 'cust-unlock' (0 KB)...
OKAY [ 0.008s]
writing 'cust-unlock'...
FAILED (remote: Error - Verify Failed ! (-1))
finished. total time: 0.015s
Richy0s said:
So ive been trying to get my OP 8t Tmobile variant bootloader unlocked, sim unlocked it , requested the unlock token from one plus , finally got it, been trying to flash the token but i keep getting a error, any help would really appreciate it a lot.
Detailed error code:
target reported max download size of 805306368 bytes
sending 'cust-unlock' (0 KB)...
OKAY [ 0.008s]
writing 'cust-unlock'...
FAILED (remote: Error - Verify Failed ! (-1))
finished. total time: 0.015s
Click to expand...
Click to collapse
hey, im on this exact thing. ive got the sim unlocked, but i need to get the unlock token. can you tell me how to request it from one plus? and did you get your bootloader unlocked?
Oneplus's website is screwed up and you can't download the token (it's corrupt) currently.
Use my msm conversion to unlock bootloader w/o token
Did you ever get your oneplus 8t unlocked? If not, I was going to suggest the msm tool to convert it to a EU version. I'll edit this post with a link. https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180981/
I've hardricked my oneplus 8t li ten times because I'm learning on my own. But I bring that sucker back every time. There are different msm tools, but ALL OF THEM that I've tried have worked every time. The only difference is what they convert it to. You can either "adb reoot edl" from home screen with adb enabled in the developers options or you can turn the phone off, let it sit for a minute, start the msm tool, then hold both volume buttons down for a few seconds and plug the phone into the usb while still pressing the volume buttons. The screen stays black, but you can see activity on the msm tool dashbord. I'm about to use it now, since my phone is currently hard bricked...lol. I've flashed shape shift os, lineage, icecold os, and some others. I have screenshots of all of them. Like shape shift, because it has a grip of hidden stuff on it, like easter eggs. It's hilarious. Just let me know if you need help.
I never find a need to ask a question to a forum. it's long overdue though. For ages, I have just been mooching off of the great minds at XDA.
This one is a bit difficult.
Meat_________________________________________________________________________
Anyone reading this threat is probably looking for instructions on "How to unlock Bootloader to Nord N10 (MetroPCS) or BE2025 as the model suggests. If you have a BE20XX, you are in the wrong place. This is only meant for the BE2025 since it's the toughest cookie I found out of the three models I know of.
I successfully obtained an unlock_code.bin file from OnePlus's awesome support team. After much back and forth. This is for the BE2025.
I started an application to obtain a bootloader unlock token from OnePlus's website. What I didn't realize is that there was a model difference between T-Mobile versions of the N10 and the MetroPCS version. I left the application up after realizing this, and contacted OnePlus support.
To make a long story short, they told me to, "consult the carrier" (Metro).
The carrier told me "consult the manufacturer we can't do that".
The manufacturer said, "give me some time".
Moments later after the chat had ended and I was on a 24-48 hour wait for an email with more information. My application (for the unlock token) magically got approved after receiving my chat transcript.
Potatoes________________________________________________________________________________________________
I copied the unlock_code.bin to the platform-tools folder.
Fired up CMD, and entered the following commands.
Code:
cd C:/platform-tools
adb reboot bootloader
fastboot oem flash unlocktoken unlock_code.bin
I get this...unfortunately.
Code:
C:\platform-tools>fastboot flash unlocktoken unlock_code.bin
Sending 'unlocktoken' (0 KB) OKAY [ 0.014s]
Writing 'unlocktoken' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
So, it seems to be a catch 22. I feel pretty dumb right now, and I'm hoping someone has better knowledge to chart this territory. I could be using the wrong fastboot commands, definitely a possibility. So many are out there though. I just feel like I am doing something wrong right here, or it's definitely a catch 22.
Let's go over some basic Q&A so y'all don't have to troubleshoot the little things.
Q: Did you enable debugging and OEM in developer options?
A: Yes
Q: Are all your drivers up to date, fastboot, adb, etc etc?
A: Yes
Q: Did you copy unlock_code.bin to your android root directory?
A: Android 11 won't allow me to place it in the root. I'm thinking this is the major hurdle.
I looked around a bit online, and most instructions insist you can just enter two commands, and "bam" you did it. That's not the case for the BE2025. At least not on android 11. I am sure there are other users struggling with this too. Or I just can't find the right thread buried in a mountain of easy instructions that don't really need to be reposted so much.
Setup:
Windows 10 Pro /w dev insider activated.
Android Debug Bridge version 1.0.41
Version 31.0.3-7562133
Android version: 11
Build: 11.0.1.BE88CF
Model: BE2025
Build Number: BE2025_17_210803
I need someone to come pour some gravy on this subject.
TLDR: How do I get this unlock_code.bin to take on the Nord N10 BE2025?
Thank you for your time in advance. If there was information I left that may be of use, ask away.
Sorry for the long read.