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.
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
Hello, I need some help/advice.
TLDR;
Verizon Motorola G7 power (Build PDOS29.114-134-12)
{
that i want to use on straight talk verizon towers is sim locked and verizon cant help me.
I tried rooting but the device isnt elligble to unlock the bootloader from motorola, attempted root anyway and it was unsuccessful running the console commands with the patched boot.img file.
}
I purchased a Verizon G7 Power on ebay and typically I just throw a sim card in and it works, sometimes I root the phone if i wanted to do things like teathering or run other apps.
I put my Straight talk ( verizon tower ) sim card that I use into the new phone and the phone simply says "change carrier, sorry your device can't be activated on another carriers network right now" and lists the verizon support numbers.
I went to the store and asked for assistance but they referred me again to tech support and gave me a more direct number.
Of course I called and the they were very good at helping me except the outcome all came down to, the device isnt blacklisted/stolen based off the meid and i should "wait 90 days" to be able to use the phone
Its been 90 days also since i purchased it.
So then I went to root it thinking maybe if I have a different build it would be alright.
Went through the steps with the tools, patched the boot img and transferred it back to my pc and ran the command line
"PS C:\Android\platform-tools> ./fastboot flash boot C:\Users\D*****\Desktop\magisk_patched.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (18137 KB) OKAY [ 0.740s]
Writing 'boot_a' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
PS C:\Android\platform-tools>"
I was able to check the box in the settings to 'allow bootloader to be unlocked"
So then I realized maybe I need the bootloader unlock code from Motorola, so i went through those steps and when pasting my string motorola says my device isnt eligible to be unlocked.
What do i do now ?
Thank you in advanced for your advices.
EvanWilliam said:
Hello, I need some help/advice.
TLDR;
Verizon Motorola G7 power (Build PDOS29.114-134-12)
{
that i want to use on straight talk verizon towers is sim locked and verizon cant help me.
I tried rooting but the device isnt elligble to unlock the bootloader from motorola, attempted root anyway and it was unsuccessful running the console commands with the patched boot.img file.
}
I purchased a Verizon G7 Power on ebay and typically I just throw a sim card in and it works, sometimes I root the phone if i wanted to do things like teathering or run other apps.
I put my Straight talk ( verizon tower ) sim card that I use into the new phone and the phone simply says "change carrier, sorry your device can't be activated on another carriers network right now" and lists the verizon support numbers.
I went to the store and asked for assistance but they referred me again to tech support and gave me a more direct number.
Of course I called and the they were very good at helping me except the outcome all came down to, the device isnt blacklisted/stolen based off the meid and i should "wait 90 days" to be able to use the phone
Its been 90 days also since i purchased it.
So then I went to root it thinking maybe if I have a different build it would be alright.
Went through the steps with the tools, patched the boot img and transferred it back to my pc and ran the command line
"PS C:\Android\platform-tools> ./fastboot flash boot C:\Users\D*****\Desktop\magisk_patched.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (18137 KB) OKAY [ 0.740s]
Writing 'boot_a' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
PS C:\Android\platform-tools>"
I was able to check the box in the settings to 'allow bootloader to be unlocked"
So then I realized maybe I need the bootloader unlock code from Motorola, so i went through those steps and when pasting my string motorola says my device isnt eligible to be unlocked.
What do i do now ?
Thank you in advanced for your advices.
Click to expand...
Click to collapse
Perty much out of luck on Verizon but some one has rooted a Verizon one but not saying how just keep looking or sell it and get one from cosumer cellular
roadkill42 said:
Perty much out of luck on Verizon but some one has rooted a Verizon one but not saying how just keep looking or sell it and get one from cosumer cellular
Click to expand...
Click to collapse
dang i guess i have to sell it.
its in good condition so i guess no big deal, i wonder what i will get next. I just liked it because it was cheap and had a 5000mah battery.
Thanks!
EvanWilliam said:
dang i guess i have to sell it.
its in good condition so i guess no big deal, i wonder what i will get next. I just liked it because it was cheap and had a 5000mah battery.
Thanks!
Click to expand...
Click to collapse
There is another way maby by using the q loader flasher u might be able to flash retus firm ware on to the phone .I'm not responsible for anything going wrong just for u to look at try at your own risk I hope it will work
roadkill42 said:
There is another way maby by using the q loader flasher u might be able to flash retus firm ware on to the phone .I'm not responsible for anything going wrong just for u to look at try at your own risk I hope it will work
Click to expand...
Click to collapse
Thanks but i was able to sell the phone to my friend he wrecked his to the point where his wasnt usable so i sold him this one and it has been good and he likes the battery life :shrug:
I feel like doing that i definitely would've bricked it
it was weird the first time we tested his verizon sim in the phone it shut off after starting the first phone call, no issues since then lol.
Update : Bought a "Moto G Power " from Straight Talk, love it.
EvanWilliam said:
Update : Bought a "Moto G Power " from Straight Talk, love it.
Click to expand...
Click to collapse
But I can't root it
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!
so first i want to apologize for posting in the wrong place but this phone doesn't seem to exist anywhere and I'm having trouble with getting the bootloader unlocked and installing Magisk (if someone could tell me where this should have been posted I would appreciate it allot)
I followed everything on the Sony open devices page checked if it was allowed got my unlock code for both IMEI (dual sim device) just in case that would be a problem now getting into fastboot was more difficult than I was expecting (Sony devices their screen stay black on fastboot which I haven't seen before) but I forced a driver update through device manager and now its being recognized by fastboot but it just gives me the error:
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
now after looking around online (some people suggested that it might be unlocked already but I'm not allowed to flash Magisk so I don't think so and i cant check the screen during fastboot as everyone suggests because it stays black)some more trying to find anything I found a post about allowing OEM unlocking through developer options and that's where I got stuck because my device keeps doing this
currently i rather bin it because this has already taken days from my life but I refuse to turn this into another €200 paperweight (I really hate e-waste) so i hope someone can help me get in the right direction again
sorry for my horrible posting (and grammar) I never do this and thanks to anyone who takes the time to read this
A friend wanted to root this phone... I guess he won't.
This is the only post I found about it, thanks for your feedback and sorry for your loss haha!