Title pretty much asks it all.
In developer options, OEM unlocking is greyed out. Is there a way to unlock and if so how?
TimmyP said:
Title pretty much asks it all.
In developer options, OEM unlocking is greyed out. Is there a way to unlock and if so how?
Click to expand...
Click to collapse
Have you connected to internet? What version of oxygen os are you on? And does it say "connect to the internet or contact your carrier" by the OEM unlocking toggle?
Yes Internet. Oos 11. I tried the T-Mobile app for permanent unlock it failed. Doesn't say anything but "allows the bl to be unlocked" but it's greyed.
TimmyP said:
Yes Internet. Oos 11. I tried the T-Mobile app for permanent unlock it failed. Doesn't say anything but "allows the bl to be unlocked" but it's greyed.
Click to expand...
Click to collapse
Permanent unlock is sim unlocking, has nothing to do with OEM unlocking
Thats great thanks
I got it. Set to midi connection so ADB detects phone.
adb shell
pm disable-user com.qualcomm.qti.uim
Now OEM unlocking is ungreyed
Its a no go. It reveals the option, but fastboot commands ask for a token.
Going to the Oneplus token generator with the correct info (because get oem info worked in fastboot) results in a window that says
"api router invoker request error"
It seems these phones are no longer rootable. Maybe when its paid off tmobile will give me a token.
Any ideas?
"fastboot flashing unlock" asks for token.
TimmyP said:
Its a no go. It reveals the option, but fastboot commands ask for a token.
Going to the Oneplus token generator with the correct info (because get oem info worked in fastboot) results in a window that says
"api router invoker request error"
It seems these phones are no longer rootable. Maybe when its paid off tmobile will give me a token.
Any ideas?
"fastboot flashing unlock" asks for token.
Click to expand...
Click to collapse
Maybe the site down, probably wait a bit, got the same error too
Thanks Ill get all prudent info in a text file. What a pita. I loathe having a new phone and not knowing whether I can root it. So much setting up already.
I tried it again for the heck of it, and now it says "IMEI number has been applied" ...so I guess I wait for the email?
Never got a confirmation or anything, but searches tell me I should get it in a few days to weeks.
TimmyP said:
I tried it again for the heck of it, and now it says "IMEI number has been applied" ...so I guess I wait for the email?
Never got a confirmation or anything, but searches tell me I should get it in a few days to weeks.
Click to expand...
Click to collapse
i got mine around an hour later after applying mine, maybe check hourly to see if you gotten it or not?
Nothing. Tbh I think Im gonna return this. Its only 128gb version and I was much happier with rooted A32 5G.
Sucks cant even use tasker for fun stuff.
Look through the OP9 forums for the OnePlus Tool..... it helps you get the number you write down to request the unlock code from OnePlus, also it can ungrey the OEM switch
Thanks but I already got that stuff requested. Still no token :-( Been talking to support tho they said they are on it!
underworld737 said:
Have you connected to internet? What version of oxygen os are you on? And does it say "connect to the internet or contact your carrier" by the OEM unlocking toggle?
Click to expand...
Click to collapse
OMG !
I have spent 7 hours attempting to unlock my Boot-Loader, and in the desire to prevent any unintended updates, I did not connect my OP9 to the network.
I Think That This Advice Should be Stickied to the front page:
"Unable to toggle OEM unlocking in <Developer Settings> ?"
"Connect to Internet first to see if it's already done !!"
HOWEVER, I still cannot :
Code:
flashboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
barguybrady said:
OMG !
I have spent 7 hours attempting to unlock my Boot-Loader, and in the desire to prevent any unintended updates, I did not connect my OP9 to the network.
I Think That This Advice Should be Stickied to the front page:
"Unable to toggle OEM unlocking in <Developer Settings> ?"
"Connect to Internet first to see if it's already done !!"
HOWEVER, I still cannot :
Code:
flashboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
Click to expand...
Click to collapse
Try ,,,,,,fastboot oem unlock,,,,
Its fastboot flashing unlock and I wouldnt recommend anything but using a token, because the rooting information here is fragmented and outdated.
Request one from oneplus and check back on that page you requested it on. Mine took about 3 days.
TimmyP said:
Its fastboot flashing unlock and I wouldnt recommend anything but using a token, because the rooting information here is fragmented and outdated.
Request one from oneplus and check back on that page you requested it on. Mine took about 3 days.
Click to expand...
Click to collapse
I already have that... Hence my confusion.
I'm thinking that there's Just One Little Thing I'm doing wrong here... Can't figure it out..!
Aha. I had been doing it in the wrong order.
Bash:
fastboot devices
fastboot flash cust-unlock unlock_code.bin
fastboot oem unlock
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))
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170
depii said:
Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170
Click to expand...
Click to collapse
Once it boots into fastboot, I enter "fastboot flashing unlock"
I have that same version of fastboot.
Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?
depii said:
Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?
Click to expand...
Click to collapse
Device state is locked
There's nothing under OEM unlocking saying that the bootloader is already unlocked.
Yes, I have enabled unlocking before booting into fastboot. I've done it five times now.
What's odd is if I use the unlock_critical command, I get "FAILED (remote: Device already : unlocked!)"
geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?
rohanhole said:
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?
Click to expand...
Click to collapse
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.
geicogecko said:
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.
Click to expand...
Click to collapse
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.
rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
I first updated to 8.1 OTA, then unlocked.
rohanhole said:
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.
Click to expand...
Click to collapse
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
Read the other threads or check the xda news portal. This command actually unlocks the pixel 2 not XL variant.
geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
I really don't have any clue why it worked ! After reading latest post I executed the above command in leap of faith and it really worked ! Finally unlocked bootloader on pixel 2 128 Gb. But its strange as I don't have Verizon model , as I purchased the device from official google store in India ( flipkart.com )
Here is the XDA post : https://www.xda-developers.com/verizon-google-pixel-2-bootloader-unlock/
geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
SkipSoft Download Page | SkipSoft.net
skipsoft.net
The issue that I'm having is that I am unable to unlock the bootloader even though I should be able to. Here are the steps i'm taking and where the issue happens.
Factory/Wipe reset
Tap about Pixel 2 7 times to get developer options
Go to developer options and enable USB Debugging and OEM Unlocking.
(I Can see that OEM unlocking is enabled).
Then I do "adb reboot bootloader"
and once in the bootloader, I do "fastboot flashing unlock"
Then it tellsme that Flashing Unlock is not allowed and when I go back to the developer options, the OEM Unlocking is greyed out and in the off position and I cannot re enable it no matter what. I have not being able to find anyone with this problem or a solution, any help would be appreciated.
I have tried the above steps many times with no luck, and every time the results are the same. It gives me the OEM Unlock option right after the factory reset, but one I do the "fastboot flashing unlock" it doesn't unlock the bootloader and then it locks the option in developer options.
I updated both ADB and fastboot to the latest version.
Edit #2: running the "fastboot flashing get-unlock-ability" command, returns a (1), which means that it should be able to be unlocked.
Edit #3: Tried to sideload OTA update using ADB and it does not solve the issue.
After factory image, did you reinstall the update? Maybe make sure the update has been completed in total (takes 2 reboots sometimes).
Try: fastboot oem unlock
Definitely a weird issue. Are you on Verizon’s network?
Edit: were you connected to the internet when you did the oem unlock in the developers options?
Edit 2: you have usb debugging enabled yeah?
Jomama22 said:
After factory image, did you reinstall the update? Maybe make sure the update has been completed in total (takes 2 reboots sometimes).
Try: fastboot oem unlock
Definitely a weird issue. Are you on Verizon’s network?
Edit: were you connected to the internet when you did the oem unlock in the developers options?
Edit 2: you have usb debugging enabled yeah?
Click to expand...
Click to collapse
After factory image, did you reinstall the update? Maybe make sure the update has been completed in total (takes 2 reboots sometimes).
I did not, I assumed that since it is the latest factory image, I did not needed to update, will try this ASAP.
USB Debugging is enabled.
I was connected to the internet when I did the OEM Unlock under developer options, I tried both connected and not connected to the internet. I tried to change the boot partition using fastboot and it does not allow to do so when in "locked" mode.
oem unlock returns that it is unable to be unlocked. (Sorry, not home now, but will post the actual error when I get back)
I am experiencing this issue also. I'm on my 2nd RMA device. The specific error I get after typing
Code:
fastboot flashing unlock
is
Code:
FAILED (remote: Flashing Unlock is not allowed)
Any help is appreciated.
keanon said:
I am experiencing this issue also. I'm on my 2nd RMA device. The specific error I get after typing
Code:
fastboot flashing unlock
is
Code:
FAILED (remote: Flashing Unlock is not allowed)
Any help is appreciated.
Click to expand...
Click to collapse
That is in fact the error I'm getting. I had the OG Pixel and the Pixel 2 rooted since the day they came out and never had a problem, and now with this RMA replacement, I'm having problems, but IDK what could be the cause because with a fresh factory reset, I can at least see the "OEM Unlock" under developer options, so I'm so confused.
plgonzalezrx8 said:
That is in fact the error I'm getting. I had the OG Pixel and the Pixel 2 rooted since the day they came out and never had a problem, and now with this RMA replacement, I'm having problems, but IDK what could be the cause because with a fresh factory reset, I can at least see the "OEM Unlock" under developer options, so I'm so confused.
Click to expand...
Click to collapse
My OEM Unlock option will "take" when I click it, but it's disabled again when I reboot.
If they're RMA replacements, there's a possibility you got a Verizon Pixel 2 instead of a Google. This happened to me as well, I just traded for my wife's Pixel 2, because she has no interest in BL Unlocking and all that goes with it. There have been others who kept returning phones until they got one that allowed BL Unlocking. If you purchased from Google originally, just tell them the problem and they should send you another RMA replacement, from what I've seen elsewhere.
Edit for clarification: Supposedly, they've been getting Verizon and Google Pixel 2s mixed up when they get refurbished.
lightningdude said:
If they're RMA replacements, there's a possibility you got a Verizon Pixel 2 instead of a Google. This happened to me as well, I just traded for my wife's Pixel 2, because she has no interest in BL Unlocking and all that goes with it. There have been others who kept returning phones until they got one that allowed BL Unlocking. If you purchased from Google originally, just tell them the problem and they should send you another RMA replacement, from what I've seen elsewhere.
Edit for clarification: Supposedly, they've been getting Verizon and Google Pixel 2s mixed up when they get refurbished.
Click to expand...
Click to collapse
I ordered a new open OEM Pixel 2 XL 64gb in Just Black arriving from eBay in 48hrs. I am now concerned.
MrKillroy said:
I ordered a new open OEM Pixel 2 XL 64gb in Just Black arriving from eBay in 48hrs. I am now concerned.
Click to expand...
Click to collapse
I am too. I'm still paying mine off and I've been without a well-functioning phone since June 15.
So op, is this the first time you have tried unlocking this rma? If so, sounds like you know the problem and probably have to rma again
Jomama22 said:
So op, is this the first time you have tried unlocking this rma? If so, sounds like you know the problem and probably have to rma again
Click to expand...
Click to collapse
Yes. This is the first time I tried to unlock this RMA, just got it a couple days ago. I have rooted all my android phones for the past 4-5 years and never had a problem similar to this show up before. The thing is that I really want to know what is happening at at deeper level, why is this happening, it doesn't make any sense at all because why would that option change if the fasboot flashing command is returning an error, also when I use "fastboot flashing get_unlock_ability" it returns a (1) and not a (0), which means that it can be unlocked.
We'll see, I started the RMA process lets see what they say.
plgonzalezrx8 said:
Yes. This is the first time I tried to unlock this RMA, just got it a couple days ago. I have rooted all my android phones for the past 4-5 years and never had a problem similar to this show up before. The thing is that I really want to know what is happening at at deeper level, why is this happening, it doesn't make any sense at all because why would that option change if the fasboot flashing command is returning an error, also when I use "fastboot flashing get_unlock_ability" it returns a (1) and not a (0), which means that it can be unlocked.
We'll see, I started the RMA process lets see what they say.
Click to expand...
Click to collapse
I don't remember where exactly I saw it, but in one of the commands, it tells you whether it's allowed to be unlocked. That's a firm 0 in that spot. Like I said, you likely ended up with a refurbished Verizon version. The only difference, to my knowledge, is that Verizon doesn't want you to unlock your bootloader.
There's already a whole thread about this. Please post there
https://forum.xda-developers.com/pixel-2/help/oem-unlocking-grayed-vzw-pixel-2-t3776763/page5
Bottom line. Google pixel 2s refurbished RMAs are botched for OEM unlocking. There's a problem with their refurbishment procedures that makes it behave exactly like show here
Only solution is trying to convince them to send you a new RMA, but good luck with that.
plgonzalezrx8 said:
The issue that I'm having is that I am unable to unlock the bootloader even though I should be able to. Here are the steps i'm taking and where the issue happens.
Factory/Wipe reset
Tap about Pixel 2 7 times to get developer options
Go to developer options and enable USB Debugging and OEM Unlocking.
(I Can see that OEM unlocking is enabled).
Then I do "adb reboot bootloader"
and once in the bootloader, I do "fastboot flashing unlock"
Then it tellsme that Flashing Unlock is not allowed and when I go back to the developer options, the OEM Unlocking is greyed out and in the off position and I cannot re enable it no matter what. I have not being able to find anyone with this problem or a solution, any help would be appreciated.
I have tried the above steps many times with no luck, and every time the results are the same. It gives me the OEM Unlock option right after the factory reset, but one I do the "fastboot flashing unlock" it doesn't unlock the bootloader and then it locks the option in developer options.
I updated both ADB and fastboot to the latest version.
Edit #2: running the "fastboot flashing get-unlock-ability" command, returns a (1), which means that it should be able to be unlocked.
Edit #3: Tried to sideload OTA update using ADB and it does not solve the issue.
Click to expand...
Click to collapse
Please visit this thread for more info. Though I need to mention there is no actual fix as of yet.
I've been trying at this for a couple days now,no success but no brick either Every phone I've owned up to this one I've been able to root and flash recoveries and custom roms as I pleased but this phone been tricky for me so I need someone here maybe to tell me my next move... So I called TMobile and I got the rep to give me a permanent unlock for my phone and I checked the Tmobile unlock app and its says permanently unlocked ...So my question now is since I cant seem to get the adb to "fastboot oem unlock" to change the device state to unlocked in the bootloader without asking me for my unlock code ,how to I get this to work? Is the next step requesting the unlock code from Oneplus because I have all the info for the form for Oneplus but don't know how to find unlock code for the form.... Help me out guys ... Thanks
bfreshdadon said:
I've been trying at this for a couple days now,no success but no brick either Every phone I've owned up to this one I've been able to root and flash recoveries and custom roms as I pleased but this phone been tricky for me so I need someone here maybe to tell me my next move... So I called TMobile and I got the rep to give me a permanent unlock for my phone and I checked the Tmobile unlock app and its says permanently unlocked ...So my question now is since I cant seem to get the adb to "fastboot oem unlock" to change the device state to unlocked in the bootloader without asking me for my unlock code ,how to I get this to work? Is the next step requesting the unlock code from Oneplus because I have all the info for the form for Oneplus but don't know how to find unlock code for the form.... Help me out guys ... Thanks
Click to expand...
Click to collapse
You now need to convert to Int. version, you can't "fastboot oem unlock" on T-Mo version without a stupid unlock token! Follow these instructions ===> https://forum.xda-developers.com/oneplus-7-pro/how-to/how-to-convert-tmobile-op7-to-t3935947
So I called TMobile and I got the rep to give me a permanent unlock for my phone and I checked the Tmobile unlock app and its says permanently unlocked
After this, you need to enable OEM unlock. See here.
Once you have enabled OEM Unlock under developer options, the fastboot oem unlock will work.
DanDroidOS said:
You now need to convert to Int. version, you can't "fastboot oem unlock" on T-Mo version without a stupid unlock token! Follow these instructions ===> https://forum.xda-developers.com/oneplus-7-pro/how-to/how-to-convert-tmobile-op7-to-t3935947
Click to expand...
Click to collapse
Thanks man,,gonna try that...
itskapil said:
So I called TMobile and I got the rep to give me a permanent unlock for my phone and I checked the Tmobile unlock app and its says permanently unlocked
After this, you need to enable OEM unlock. See here.
Once you have enabled OEM Unlock under developer options, the fastboot oem unlock will work.
Click to expand...
Click to collapse
Thanks man...Gonna check it out ..
Hello, hope this finds everyone well. I have been looking at the related topics and saw a post by @mobbdeep which had helpful information but I was unable to get ahold. If anyone knows a way or someome that can help I would highly appreciate that.
Thanks!
Update: Just spoke with T-Mobile and they said we don't have anything called "Unlock code" that it would be something you get from OnePlus. Does anyone have a clue?
Thanks.
Faibawa said:
Update: Just spoke with T-Mobile and they said we don't have anything called "Unlock code" that it would be something you get from OnePlus. Does anyone have a clue?
Thanks.
Click to expand...
Click to collapse
Make sure you have adb and fastboot installed and OEM unlocking selected in Android, then boot into fastboot by using "adb reboot bootloader". Once in fastboot, use "fastboot oem get_unlock_code". Copy the code, remove all of the weird formatting so it is one consistent string, and paste that into the unlock code box at oneplus' site.
If you are wanting to unlock without paying off the phone, you will need to wait for mobbdeep to get back or try your luck with T-Mobile's Twitter. There was a well-documented bug in later firmwares on the original OP8 which caused people to lose signal, with the only way to fix to use MSM to roll back. I was able to request an unlock with this.
stompysan said:
Make sure you have adb and fastboot installed and OEM unlocking selected in Android, then boot into fastboot by using "adb reboot bootloader". Once in fastboot, use "fastboot oem get_unlock_code". Copy the code, remove all of the weird formatting so it is one consistent string, and paste that into the unlock code box at oneplus' site.
If you are wanting to unlock without paying off the phone, you will need to wait for mobbdeep to get back or try your luck with T-Mobile's Twitter. There was a well-documented bug in later firmwares on the original OP8 which caused people to lose signal, with the only way to fix to use MSM to roll back. I was able to request an unlock with this.
Click to expand...
Click to collapse
Thanks for your reply! I am familiar with everything you mentioned in regards to fastboot commands. However, the OEM unlocking option is grayed out meaning i cannot toggle it.
I will attempt the fastboot get unlock code command and hopefully see some magic.
Yea i'm in on waiting for mobbdeep. Hopefully he'd be able to give some insight. His topic post is the most relevant to my issue. I'm now going in on 3rd day with carrier sim in the phone.
What's MSM you mentioned? I read it in a few places here but what is that tool used for?
Thanks again! Have a great day.
Faibawa said:
Thanks for your reply! I am familiar with everything you mentioned in regards to fastboot commands. However, the OEM unlocking option is grayed out meaning i cannot toggle it.
I will attempt the fastboot get unlock code command and hopefully see some magic.
Yea i'm in on waiting for mobbdeep. Hopefully he'd be able to give some insight. His topic post is the most relevant to my issue. I'm now going in on 3rd day with carrier sim in the phone.
What's MSM you mentioned? I read it in a few places here but what is that tool used for?
Thanks again! Have a great day.
Click to expand...
Click to collapse
You will not be able to issue the fastboot commands with the OEM unlocking option greyed out. The only way, currently, to get that option, is to have a permanent SIM unlock on the device. There are talks in the Verizon thread about a working workaround for bootloader unlock, but I am unsure if that particular method is working on T-Mobile devices. As for MSM, it is the unbricking tool for our devices. There is a special download mode that can be triggered in Qualcomm devices by holding volume up and volume down with the device off, and inserting a USB cable. Should something happen catastrophic to your software, and recovery through fastboot isn't possible, MSM allows your device to be returned to stock software. It will automatically relock your bootloader, and does not touch certain partitions like persist (individual fingerprint calibration files are in this partition), but it does completely recover your device in extreme cases. I actually misspoke in my post, as MSM is available on all devices. I meant the fastboot ROM restores, as that does require a bootloader unlock.
Faibawa said:
Hello, hope this finds everyone well. I have been looking at the related topics and saw a post by @mobbdeep which had helpful information but I was unable to get ahold. If anyone knows a way or someome that can help I would highly appreciate that.
Thanks!
Click to expand...
Click to collapse
Hi there!
Are you looking to sim unlock your phone (i.e. network unlock) your phone? If so, PM me. I have a lead. Yes, really. :good: