WARNING: This should not be done lightly. This could brick your phone if not done properly. I take no responsibility for anyone's actions or phones. I'm just relaying my findings and the process I used to unlock my Google Store bought Pixel 2. This process will not work with a Verizon bought Pixel 2. (see note at end)
WARNING: This process will erase all content on your Pixel 2. Essentially do a factory reset.
1. Backup your Pixel 2 first. Before doing anything just make sure you have up to date backup for your device data as well your files such as images, pictures, videos or documents.
2. Have already installed ADB and Fastboot Setup on your PC.
3. Make sure your device is charged.
4. Enabled USB debug and OEM Unlock option from the device settings under the "Developer Mode" menu.
You will have to enable Developer Mode. Do this by tapping the Build Number under "System", "About Phone" 7 times.
You can now unlock you Google Pixel 2 Bootloader.
1. Connect your Pixel 2 phone to your PC and wait for drivers to be installed.
2. Now go to ADB and Fastboot Folder then do Shift + Right Click to select Open Command Prompt Here.
3. Boot your Pixel 2 or Pixel 2 XL to bootloader mode using this: adb reboot bootloader
4. Now to unlock your phone enter this command in terminal: fastboot flashing unlock
5. On your phone allow the device to be unlocked by selecting Yes using power keys and power button to confirm.
6. Your phone will not reboot with a warning that your bootloader is unlocked and can't be verified (this is normal). Your device with erase all content and reboot a second time.
7. Your phone will now be at the same state it was as a new phone to set up.
I have not seen of a method to root the Pixel 2 yet. If the procedure is similar to the Pixel this should put you into a position to root your phone without having to erase all your data to unlock your bootloader first.
NOTE ON VERIZON BOUGHT PIXELS:
I don't know if this process will work with the Pixel 2 or not. This is how I unlocked the bootloader on my Verizon bought Pixel. I bought mine very early on. It was right after they patched the work around we had to unlock the Verizon bootloaders. I did not let Verizon turn on the phone when I purchased it. I removed the micro-sim when I got it home before turning the phone on. I then went through the above process to unlock my bootloader. With the Pixel the blocking of the "OEM Unlock" seemed to happen after it connected to the Verizon network. With the Pixel 2 it won't let you "OEM Unlock" the phone unless you are connected to to the internet at a minimum. So this may not work for the Pixel 2.
Anyone who doesn't know this already should never unlock their bootloader.
Agreed. I just posted this for those wondering if there were differences in the process between the Pixel and Pixel 2. At least Google kept it the same. Now we just need a TWRP for the Pixel 2 to finish the root.
Sent from my Pixel 2 using Tapatalk
Unlocking will break safetynet right?
Can I expect that to be resolved after someone develops a method to root?
bjgood said:
Unlocking will break safetynet right?
Can I expect that to be resolved after someone develops a method to root?
Click to expand...
Click to collapse
That is correct. For the Pixel they had a kernel that would disable the safetynet check and return a pass whenever an app would check. We'll have to wait and see what happens for the Pixel 2.
psu90 said:
Agreed. I just posted this for those wondering if there were differences in the process between the Pixel and Pixel 2. At least Google kept it the same. Now we just need a TWRP for the Pixel 2 to finish the root.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
I think at this point the best thing to do is flip the switch to allow bl unlock and leave it at that. I mean if you are going to root in the future. Until they release sources unlocking will break AP and security check apps. If you don't care about that then unlock the bl now since it will wipe the device in the process. That's the beauty of having a Verizon model. You can't do that so the pressure is off.
Has anyone tried this on a Verizon bought Pixel 2?
I would be interested to see if you put a non verizon sim in first, whether it would lock the oem unlock option
need proper thread
morgenman42 said:
I would be interested to see if you put a non verizon sim in first, whether it would lock the oem unlock option
Click to expand...
Click to collapse
can you please provide me some good thread to solve this unlocking
Pixel2 bought from Google store; I had booted up with my VZW Sim card before reading this thread, but OEM unlock was not greyed out . Unlocked B/L with no issues.
Thanks for confidence to move ahead. Looking forward to root w/o a reset.
neuron617 said:
Pixel2 bought from Google store; I had booted up with my VZW Sim card before reading this thread, but OEM unlock was not greyed out . Unlocked B/L with no issues.
Thanks for confidence to move ahead. Looking forward to root w/o a reset.
Click to expand...
Click to collapse
Can you specify which Pixel2 you bought? Was it specifically for VZW, or did you buy the GOOGLE version and drop your VZW SIM into it at home?
b00ster23 said:
Can you specify which Pixel2 you bought? Was it specifically for VZW, or did you buy the GOOGLE version and drop your VZW SIM into it at home?
Click to expand...
Click to collapse
Bought from Google Store fearing anything from Verizon or Best Buy would be compromised. Had a VZW nano SIM from my Moto XPE, which I popped in, yes.
No there are actually two different models sold at the google store. one has a verizon sim and one doesn't.
morgenman42 said:
No there are actually two different models sold at the google store. one has a verizon sim and one doesn't.
Click to expand...
Click to collapse
I bought the Google (non-Verizon) version from the Google store. I didn't want to take any chances even though Google says all phones purchased from them can have their bootloader unlocked. That was the way it was with the Pixel. I just popped my nano-sim from my old Pixel in my new Google version Pixel 2 and everything worked fine.
Sent from my Pixel 2 using Tapatalk
Verizon model direct from Google cannot be bootloader unlocked.
See https://forum.xda-developers.com/showpost.php?p=74271638&postcount=86
Sent from my PH-1 using XDA Labs
Guys is there any way to do it when OEM unlock is grey?
froniu said:
Guys is there any way to do it when OEM unlock is grey?
Click to expand...
Click to collapse
No, there is not.
Sent from my PH-1 using Tapatalk
No, thats a sign of it being a verizon version
Send it back, get a non Verizon model
Sent from my PH-1 using Tapatalk
mine arrives tomorrow.. can't send it back though because has to be bought through best buy
Related
The new Device Protection features of Android 5.1 on the Nexus 9 and Nexus 6 can, in certain cases, cause you to have a bootloader which can not be unlocked.
Please have a read of the following links:
https://support.google.com/nexus/answer/6172890?hl=en
http://forum.xda-developers.com/nexus-6/help/update-to-5-1-lock-bootloader-t3058480
http://forum.xda-developers.com/nexus-6/general/relock-bootloader-time-updating-to-5-1-t3053497
What a pita
Sent from my Nexus 5 using XDA Free mobile app
i would never relock my bootloader
people unlock there bootloader for a reason
but to relock it after thats just wrong...
thats one of the things i hate about CM
they recommend you to relock your bootloader...
Agreed, why would you lock your bootloader unless sending in for repairs maybe?
But Google is really messing up the flow. The nexus 6 5.1 OTA is a mess right now but I will leave that for another thread.
Android 5.1 for Nexus 9? You must be joking.
So, I just purchased a Nexus 9 via the 4-hour online-only sale at Best Buy. It was $100 off, couldn't pass it up. My question is: is this likely going to be shipped in such a condition as to prevent me from permanently unlocking the bootloader? Or is a permanent lock something one must deliberately do?
disturbd1 said:
So, I just purchased a Nexus 9 via the 4-hour online-only sale at Best Buy. It was $100 off, couldn't pass it up. My question is: is this likely going to be shipped in such a condition as to prevent me from permanently unlocking the bootloader? Or is a permanent lock something one must deliberately do?
Click to expand...
Click to collapse
No no you can still unlock it
But if you relock it that's the problem
disturbd1 said:
So, I just purchased a Nexus 9 via the 4-hour online-only sale at Best Buy. It was $100 off, couldn't pass it up. My question is: is this likely going to be shipped in such a condition as to prevent me from permanently unlocking the bootloader? Or is a permanent lock something one must deliberately do?
Click to expand...
Click to collapse
As USBhost said, you'll be able to unlock it. However, when you are first setting it up and are running through the set-up wizard, there will be an option to "Protect Device" or something like that. If you enable it, and re-lock the bootloader, it will put you in a situation where you can only unlock the booloader in certain situations -- and if you happen to have a bootloop with a locked bootloader, that's when you are in trouble.
EDIT: On Nexus devices, I personally unlock the bootloader as soon as I take it out of the box, without first booting into Android, and then leave it unlocked. But of course, you give up some security by doing that.
efrant said:
As USBhost said, you'll be able to unlock it. However, when you are first setting it up and are running through the set-up wizard, there will be an option to "Protect Device" or something like that. If you enable it, and re-lock the bootloader, it will put you in a situation where you can only unlock the booloader in certain situations -- and if you happen to have a bootloop with a locked bootloader, that's when you are in trouble.
EDIT: On Nexus devices, I personally unlock the bootloader as soon as I take it out of the box, without first booting into Android, and then leave it unlocked. But of course, you give up some security by doing that.
Click to expand...
Click to collapse
Considering this is a tablet, hopefully I won't lose or misplace it
Thanks, guys! Glad I stumbled across this thread before the thing arrived.
Locking the bootloader doesn't protect you from anything. If the device leaves your physical control in a potentially hostile environment, whatever is on the system or boot partition becomes suspect, regardless of whether the bootloader is locked or unlocked.
doitright said:
Locking the bootloader doesn't protect you from anything. If the device leaves your physical control in a potentially hostile environment, whatever is on the system or boot partition becomes suspect, regardless of whether the bootloader is locked or unlocked.
Click to expand...
Click to collapse
Example: I have a device running a stock ROM with no encryption, the stock recovery and a lock screen password. I happen to lose my phone. What happens to the photos of me dancing to Old Time Rock & Roll in my underwear that are stored on the device? If the bootloader is unlocked, someone just plugs it into a PC, boots TWRP and pulls them off. If the bootloader is locked, there is no easy way to see or get the photos off the device.
That is all I was saying about security. Nothing to do with you leaving your device somewhere or losing it, and then finding it again. Strictly about the personal content on the device.
efrant said:
EDIT: On Nexus devices, I personally unlock the bootloader as soon as I take it out of the box, without first booting into Android, and then leave it unlocked. But of course, you give up some security by doing that.
Click to expand...
Click to collapse
I thought Lollipop always requires you to go in and check the Enable OEM Unlock box? Or is that not true if you never booted into Android even once?
bailyc said:
I thought Lollipop always requires you to go in and check the Enable OEM Unlock box? Or is that not true if you never booted into Android even once?
Click to expand...
Click to collapse
If you have never booted into Android, then you don't need to check that setting. As I said, that's the way I did it on my N6: take out of box -> charge -> boot directly into bootloader -> "fastboot oem unlock". No other steps required if you don't boot into Android first.
can i use this guide for safely relock my Bl on Nexus 9 ..... Relocking coz of RMA and warranty purpose as bought from amazon India instead of Play Store
http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
lilliput222 said:
can i use this guide for safely relock my Bl on Nexus 9 ..... Relocking coz of RMA and warranty purpose as bought from amazon India instead of Play Store
http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Click to expand...
Click to collapse
Yes, that should work for the N9 as well.
The bootloader on my Nexus 9 Android 5.1.1 is locked forever due to my mistake
Short backstory:
- I wanted to install the Android M developer Preview for the Nexus 9 but I forgot to check "Enable OEM unlock" in developer options (worst mistake).
- I used adb command to flash the new image but failed somehow
- I carelessly type # fastboot oem lock
- I tried to factory reset from bootloader to bring it back to Stock. Now it couldn't factory reset and my Nexus 9 hangs in a nice boot loop.
- I try # fastboot oem unlock but failed with permission denied error
I tried some ways to save my device but no hopes
- I used Nexus Root Tookit to unlock bootloader or restore image with force mode but failed,
- I follow instruction in HTC dev forum to get identifier token in order to receive your unlock code binary file but failed
- Unluckily, I don't installed any custom recovery.
Please help if you know a way unlock the bootloader or flash the factory ROM to save the nexus 9
quekl84 said:
Please help if you know a way unlock the bootloader or flash the factory ROM to save the nexus 9
Click to expand...
Click to collapse
Not possible. You will have to return it to HTC for repair or replacement.
quekl84 said:
Short backstory:
- I wanted to install the Android M developer Preview for the Nexus 9 but I forgot to uncheck "Enable OEM unlock" in developer options (worst mistake).
- I used adb command to flash the new image but failed somehow
- I carelessly type # fastboot oem lock
- I tried to factory reset from bootloader to bring it back to Stock. Now it couldn't factory reset and my Nexus 9 hangs in a nice boot loop.
- I try # fastboot oem unlock but failed with permission denied error
I tried some ways to save my device but no hopes
- I used Nexus Root Tookit to unlock bootloader or restore image with force mode but failed,
- I follow instruction in HTC dev forum to get identifier token in order to receive your unlock code binary file but failed
- Unluckily, I don't installed any custom recovery.
Please help if you know a way unlock the bootloader or flash the factory ROM to save the nexus 9
Click to expand...
Click to collapse
u mean u forgot to CHECK to box to allow oem UNLOCK? im confused lol
cobyman7035 said:
u mean u forgot to CHECK to box to allow oem UNLOCK? im confused lol
Click to expand...
Click to collapse
Yes, I forgot to check the box to allow oem UNLOCK. And now my device is locked forever.
A quick question: A lot of N9 ROMs require flashing an updated bootloader from the factory image. Aren't these bootloaders locked by default? Can we flash a factory bootloader over a custom ROM?
It seems that we might bork our Nexus 9s if we flash a locked bootloader in.
Me and this guy was talking about unlocking the bootloader by modifiying the .bin in an ota file and to my surprise he apparently was able to unlock the Pixel 2. Maybe this will work for those in on a Verizon Pixel 1 so give this a shot!
From all I can tell your just unlocking the critical partition with the command "Fastboot flashing lock_critical" then it allows for you to unlock. Refer to this thread and good luck!
https://forum.xda-developers.com/pixel-2/help/maybe-stupid-question-verizon-pixel-2s-t3726294
Couldn't be this easy, so many devs have looked into this.
Sent from my Pixel XL using Tapatalk
FUZER384 said:
Couldn't be this easy, so many devs have looked into this.
Click to expand...
Click to collapse
I too think this is too easy but if it works it works.
I don't see how you can modify an OTA and still pass the the cert signing check and update checker.
TonikJDK said:
I don't see how you can modify an OTA and still pass the the cert signing check and update checker.
Click to expand...
Click to collapse
That is what is interesting me but it seems another person has done the same and it worked.
I don't even have Verizon or the Verizon pixel, but I'm curious if this works too lmao.
Didn't for me on my pixel. Says cannot be unlocked
abranson said:
Didn't for me on my pixel. Says cannot be unlocked
Click to expand...
Click to collapse
I see is this on the Pixel XL or just the Pixel ?
5 inch. I wouldn't think it would matter
abranson said:
5 inch. I wouldn't think it would matter
Click to expand...
Click to collapse
It just seems that all the success stories of the Pixel 2 are of the smaller verison and not the Pixel 2 XL so I didn't know if one or the other would work better. Also what error did it give you?
Edit: the critical part is an XL command only so try
Fastboot lock
Or
Fastboot flashing lock
The flashing lock-critical said it wasnt a valid command, so tried the lock_critical. Already locked and did nothing else. Also if changed to unlock_critical, fails and says unlocking is not allowed ,
abranson said:
The flashing lock-critical said it wasnt a valid command, so tried the lock_critical. Already locked and did nothing else. Also if changed to unlock_critical, fails and says unlocking is not allowed ,
Click to expand...
Click to collapse
How about fastboot flashing lock or flashing unlock
Did those too. The oem unlocking not allowed came up. Can't toggle oem unlocking switch, so idk
abranson said:
Did those too. The oem unlocking not allowed came up. Can't toggle oem unlocking switch, so idk
Click to expand...
Click to collapse
I don't understand this comment maybe a typo?
Oem unlocking toggle under developer options is greyed out. When you input those commands, it says failed, and says unlocking is not allowed. I'm not at a PCat the moment, but I can do again tomorrow, and take a pic
---------- Post added at 02:22 AM ---------- Previous post was at 02:15 AM ----------
And I was under the impression the critical command was only for pixel 2 and 2xl, so Idk. I have latest adb and fastboot
abranson said:
Oem unlocking toggle under developer options is greyed out. When you input those commands, it says failed, and says unlocking is not allowed. I'm not at a PCat the moment, but I can do again tomorrow, and take a pic
---------- Post added at 02:22 AM ---------- Previous post was at 02:15 AM ----------
And I was under the impression the critical command was only for pixel 2 and 2xl, so Idk. I have latest adb and fastboot
Click to expand...
Click to collapse
I thought the critical command was just a Android Oreo thing not specific to the Pixel 2's
EstiR86 said:
I thought the critical command was just a Android Oreo thing not specific to the Pixel 2's
Click to expand...
Click to collapse
For Pixel 2: To flash the bootloader, Pixel 2's boot loader must be updated to at least Oreo MR1's version first. This may be done by applying an over-the-air (OTA) update, or sideloading a full OTA with the instructions on that page.
For Pixel 2 XL only: the critical partitions may also need to be unlocked before flashing. The unlock can be performed with this command, and should NOT be done on other devices:
fastboot flashing unlock_critical
Looks like this exploit does not work for the original Pixel. Bummer waste or a thread, good luck to those still trying to unlock.
try this, take Sim out and scratch out gold plating square closest to cut in one corner. reinsert Sim, reboot phone and adb/fastboot first then try activate oem unlock.sean
petiolarissean said:
try this, take Sim out and scratch out gold plating square closest to cut in one corner. reinsert Sim, reboot phone and adb/fastboot first then try activate oem unlock.sean
Click to expand...
Click to collapse
I'm confused what this would do, would you like to elaborate more.
Please dd and pm me your frp, ftm, and if you are willing to, factory reset and then enable oem unlock, and send your userdata partition, all with the oem unlock allowed.
Thanks!
bump?
What is this needed for? I've upgraded to the 4XL but still have my 2XL for right now.
wgrant said:
What is this needed for? I've upgraded to the 4XL but still have my 2XL for right now.
Click to expand...
Click to collapse
The request is probably for this thread. People are trying to use the recently rediscovered exploit to finally be able to bootloader unlock Verizon Pixel 2 XL phones.
wgrant said:
What is this needed for? I've upgraded to the 4XL but still have my 2XL for right now.
Click to expand...
Click to collapse
On the LG V40 if the frp partition from a phone with the OEM lock flag triggered is dd'd to another device, the bootloader will allow unlocking, additionally, the ftm partition on the v40 seems to carry the imei so I assume the same is true for the Pixel, I'd understand if you didnt want to share that partition but I think if the phones imei registers as a Google store one, that could help trick it into working.
Is there any way an exchange can be done here for the Verizon software that enables WiFi calling, volte, voicemail, and video calling? Is that Verizon software out there somewhere? If you guys are trying to root and unlock vzw phones you'll be wiping and starting with a fresh phone anyway. Is that a good time to extract these files and provide them?
I have a Verizon Pixel 2 XL on Android 9 [last security patch]. Bootloader unlocked :good:
IcyAgitator said:
I have a Verizon Pixel 2 XL on Android 9 [last security patch]. Bootloader unlocked :good:
Click to expand...
Click to collapse
Could you follow this guide: https://forum.xda-developers.com/showthread.php?t=2450045 to get frp and ftm partitions? Then PM them to @Whoareyou
Thanks again!
Unfortunately I already was able to get these from someone with a Google Store unlocked one, the dd'd partitions didnt stick through a reboot, and it wasnt able to oem unlock, ive been messing with the oemlock-bridge-client, so far chaning the device_lock status from 1 to 0 does nothing :/
shwise said:
Could you follow this guide: https://forum.xda-developers.com/showthread.php?t=2450045 to get frp and ftm partitions? Then PM them to @Whoareyou
Thanks again!
Click to expand...
Click to collapse
I updated to Android 10 Security Patch October 6 2019. But I will do what I can.
Whoareyou said:
Unfortunately I already was able to get these from someone with a Google Store unlocked one, the dd'd partitions didnt stick through a reboot, and it wasnt able to oem unlock, ive been messing with the oemlock-bridge-client, so far chaning the device_lock status from 1 to 0 does nothing :/
Click to expand...
Click to collapse
Could you try flashing those from temp root, hard powering off (holding button) and then booting to BL?
shwise said:
Could you try flashing those from temp root, hard powering off (holding button) and then booting to BL?
Click to expand...
Click to collapse
I'll try when I get home, but I don't know if it'll be any different than using the "reboot bootloader" command.
No offence but,why are people still trying to unlock/root the "unlockable/unrootable" variants of this phone? Its like what 3-4 years old? Like i get trying to root/unlock them when they 1st come out even though like come on you should've known by now. But now there are way better phones. Everyone is offering good deals for trade in's. I think its time to give up.
I would not have even rooted android 10 if Google music had a dark mode. (literally the only thing i use root for now) Oh and to fix the things google ****ed up like the lock and unlock sound and battery sound.
krolla03 said:
No offence but,why are people still trying to unlock/root the "unlockable/unrootable" variants of this phone? Its like what 3-4 years old? Like i get trying to root/unlock them when they 1st come out even though like come on you should've known by now. But now there are way better phones. Everyone is offering good deals for trade in's. I think its time to give up.
I would not have even rooted android 10 if Google music had a dark mode. (literally the only thing i use root for now) Oh and to fix the things google ****ed up like the lock and unlock sound and battery sound.
Click to expand...
Click to collapse
I expect to get two more years out of this phone.... It'd be nice to have root options.
krolla03 said:
No offence but,why are people still trying to unlock/root the "unlockable/unrootable" variants of this phone? Its like what 3-4 years old? Like i get trying to root/unlock them when they 1st come out even though like come on you should've known by now. But now there are way better phones. Everyone is offering good deals for trade in's. I think its time to give up.
I would not have even rooted android 10 if Google music had a dark mode. (literally the only thing i use root for now) Oh and to fix the things google ****ed up like the lock and unlock sound and battery sound.
Click to expand...
Click to collapse
It's 2 years old
I am trying to unlock my bootloader and root my phone but I am unable to turn on the OEM unlocking feature in developers options. Several months ago I returned/restored the phone's stock image. I previously rooted my phone but decided to unroot it. Now I am attempting to root it again but I cannot unlock the bootloader by switching on OEM unlocking.
The OEM Unlocking option is greyed out and appears to be locked or inaccessible. I have attached a screen shot.
Can someone tell me what I must do to fix this.
LeoG360 said:
I am trying to unlock my bootloader and root my phone but I am unable to turn on the OEM unlocking feature in developers options. Several months ago I returned/restored the phone's stock image. I previously rooted my phone but decided to unroot it. Now I am attempting to root it again but I cannot unlock the bootloader by switching on OEM unlocking.
The OEM Unlocking option is greyed out and appears to be locked or inaccessible. I have attached a screen shot.
Can someone tell me what I must do to fix this.
Click to expand...
Click to collapse
Are you sure the BL is locked now? If not boot into BL and check it. In any case Google is your friend:
https://www.theandroidsoul.com/how-to-fix-oem-unlock-greyed-out-or-oem-unlock-disabled-problem/
That's why I don't see any sense in relocking, I can't find any advantage in it.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
That's why I don't see any sense in relocking, I can't find any advantage in it.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
I hear you Wolfcity. And it is something that seems to come up on every device I have owned starting with the Moto G2 (G3, G4, G5+, & G5s+). I have had users flat out tell me I am wrong and that you need to relock the device in order to go back to stock or remove root. :silly:
Quick and simple bc after sifting through this website I accidently figured it out. First use the script from this post - https://forum.xda-developers.com/t/oneplus-pure-debloat.4157691/ then check dev options and OEM unlocking should be ungreyed out. Grab your oneplus unlock by running this command - "fastboot oem get_unlock_code" Then go to - https://www.oneplus.com/unlock_token submit your token and serial number and wait exactly one week to the day. Download this tool https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3358711/ and you can unlock the bootload with your unlock.bin file. After that whats next is up too you!
I don't know about SIM unlocking, however I did figure out which package specifically enables the toggle for OEM unlocking in the Developer Options.
So I took a look at the debloat thread linked above and I went through the list of packages and I was uninstalling them on my phone one by one until I found the one that enabled the toggle for OEM unlocking in the Developer Options.
When I uninstalled the package com.qualcomm.qti.uim, the toggle for OEM unlocking was no longer greyed out.
That's a great find. Is it enough to simply force-stop the package or does it need to be disabled/uninstalled?
Might try this on the OP9 or OP10 if I get one.
LLStarks said:
That's a great find. Is it enough to simply force-stop the package or does it need to be disabled/uninstalled?
Might try this on the OP9 or OP10 if I get one.
Click to expand...
Click to collapse
I didn't see if force stopping it worked or not so I wouldn't be able to answer that. I just uninstalled it with adb.
Title of tread said sim-unlocking, after reading through, it only mentions bootloader unlocking via the OnePlus website and all in one flashing tool. Yes it may bypassed the carrier restriction for bootloader unlocking, but is the phone actually sim unlocked? As you can use it with another carrier?
But I agree, finding out com.qualcomm.qti.uim being the toggle for bootloader unlock is great find.
I disabled com.qualcomm.qti.uim via ADB myself and while 'OEM Unlocking" is no longer grey and you can enable the option the bootloader for me is still locked. My OnePlus 8T model is through T-Mobile
kevinco1 said:
I disabled com.qualcomm.qti.uim via ADB myself and while 'OEM Unlocking" is no longer grey and you can enable the option the bootloader for me is still locked. My OnePlus 8T model is through T-Mobile
Click to expand...
Click to collapse
gotta complete the whole process homie.. AFTER doing the uninstall or disable of com.qualcomm.qti.uim, then you gotta flip the toggle and then reboot to bootloader. after that you need to run the fastboot command, "fastboot oem get_unlock_code"... copy that code to your clipboard, then go to the Oneplus website, fill out the form and paste that code in the proper field.
After that it does take exactly one week... (to the minute) and you will need to go back to this site and you will see it change to download. Download that file and flash it via fastboot, then confirm you want to unlock and its done!
Now after that you have to remember to NEVER flash a stock firmware via fastboot again, otherwise you will re-lock your bootloader. I cannot confirm whether or not you will be able to, or even need to flash the unlock token again, but in the case of Samsung phones, when you flash the bootloader unlock token, you DO NOT get a second chance. If you unlock it once, and then accidently re-lock via flashing stock, you will be stuck with a locked bl. (EDIT: you CAN flash stock with samsung, as long as the bootloader version isnt changed. If you upgrade the BL then you are stuck!)
(Now theres a simpler way around all this but you must do your research, and look into converting your TMO-US fw to TMO-EU ... this can be done without unlocking the bootloader. And after the conversion, if you disable the OP mentioned file, you can simply toggle, and run the "fastboot oem unlock" command and thats it... no token file needed! And i am in Texas, so i can confirm 100% that ALL of the bands are active and available, and i get 5g with absolutely no problem... In fact my phone runs quicker and gets better battery life on the EU fw. )
Then when your phone is fully paid off, simply flash back to the US fw and you can have them Sim unlock you and you can either go thru the normal unlocking process, or you can go back to the EU... but either way no foul, no harm!
So to get T-Mobile to do it on their end do this.
Go on their site and facebook, keep telling them this. "I'm a developer who can't develop app's on my device, can you please allow my phone to be unlocked." Most will tell you it needs to be paid off, but you quite possibly will get that disgruntled worker or guy who just doesn't care. Took me 5 tries, then the guy I got was like, "okay I'll do it for you!" #boomdone
Social engineering at its finest.
kyanox said:
So to get T-Mobile to do it on their end do this.
Go on their site and facebook, keep telling them this. "I'm a developer who can't develop app's on my device, can you please allow my phone to be unlocked." Most will tell you it needs to be paid off, but you quite possibly will get that disgruntled worker or guy who just doesn't care. Took me 5 tries, then the guy I got was like, "okay I'll do it for you!" #boomdone
Social engineering at its finest.
Click to expand...
Click to collapse
I have had this same issue. I bought the 8T+5G from OnePlus online store TMobile version (because the unlocked versions were sold out). Been back and forth betwee TMobile and OnePlus for 4 days, and OnePlus finally says they nor Tmobile can unlock the device until it has been used on Tmobile's service for 45 days (part of the unlock policy). I knew this, but thought surely someone can help me. OnePlus assured me that the IMEI number does not enter into the system as an unlockable phone until after the 45 days, and that NOBODY can unlock the phone until then... Am I screwed for 40 more days???? This in my opinion is a scam to force people to use a service they may not want.
i am shop in istanbul come to me oneplus 8t 5g t-mobile i ask whole world for simlock no one can and one of customer tell me i can unlock he take device for 3 hour he come back and device unlocked and he tell me i can do anything in oneplus phones i got crazy how he did this ? anyone know how ?
jabe78 said:
I have had this same issue. I bought the 8T+5G from OnePlus online store TMobile version (because the unlocked versions were sold out). Been back and forth betwee TMobile and OnePlus for 4 days, and OnePlus finally says they nor Tmobile can unlock the device until it has been used on Tmobile's service for 45 days (part of the unlock policy). I knew this, but thought surely someone can help me. OnePlus assured me that the IMEI number does not enter into the system as an unlockable phone until after the 45 days, and that NOBODY can unlock the phone until then... Am I screwed for 40 more days???? This in my opinion is a scam to force people to use a service they may not want.
Click to expand...
Click to collapse
Does this still work on the recent 8T phones? Please do keep us updated on your situation. I'm thinking about buying this phone unlock the boot-loader, Sim unlock and get Lineage on it. I don't mind 45 days if they actually unlock it
TommyQuid said:
Does this still work on the recent 8T phones? Please do keep us updated on your situation. I'm thinking about buying this phone unlock the boot-loader, Sim unlock and get Lineage on it. I don't mind 45 days if they actually unlock it
Click to expand...
Click to collapse
Yeah. I'm going to wait it out. Counting down the days I'm chained to T-Mobile (38 left). I actually wanted their service so it isn't an inconvenience, but I hate being forced to do anything, much less wait to do what I wanted to do from day one, which is Flash Roms. I'm looking at Lineage too. So I will update this post once I get to that point. Here's hoping they keep their word, because my 15 day return policy on the phone runs out in two days.
Alright folks I've been with Samsung over a decade and just got my first Oneplus (8T+5G KB2007) so don't start yelling at me just yet. Got this thing on Amazon and appears to be new. I'm sim/network unlocked through TMO. My OEM Unlock was never greyed out. I can toggle no problem. However, I went through the debloat described above because of the following problem: Sticks on "waiting for any device" after running "fastboot oem get_unlock_code" Please tell me this is an easy fix. I already reinstalled the google driver through SDK Manager bla bla bla.... Am I missing something simple? Any help would be appreciated. THX
jabe78 said:
Yeah. I'm going to wait it out. Counting down the days I'm chained to T-Mobile (38 left). I actually wanted their service so it isn't an inconvenience, but I hate being forced to do anything, much less wait to do what I wanted to do from day one, which is Flash Roms. I'm looking at Lineage too. So I will update this post once I get to that point. Here's hoping they keep their word, because my 15 day return policy on the phone runs out in two days.
Click to expand...
Click to collapse
I should've done more research myself. Galaxy was about to quit on me so I grabbed this one specifically because it was rated as one of the very top phones for development. If it wasn't such a rush I would've spent more time.
jtford said:
Alright folks I've been with Samsung over a decade and just got my first Oneplus (8T+5G KB2007) so don't start yelling at me just yet. Got this thing on Amazon and appears to be new. I'm sim/network unlocked through TMO. My OEM Unlock was never greyed out. I can toggle no problem. However, I went through the debloat described above because of the following problem: Sticks on "waiting for any device" after running "fastboot oem get_unlock_code" Please tell me this is an easy fix. I already reinstalled the google driver through SDK Manager bla bla bla.... Am I missing something simple? Any help would be appreciated. THX
Click to expand...
Click to collapse
Have you checked if your phone is properly connected to your computer? Check using "fastboot devices" to see if your device is detected, and if it is not, then go within the Windows Device Manager and install the appropriate driver from Google, which can be found by searching "Google Fastboot Driver".
Xryphon said:
Have you checked if your phone is properly connected to your computer? Check using "fastboot devices" to see if your device is detected, and if it is not, then go within the Windows Device Manager and install the appropriate driver from Google, which can be found by searching "Google Fastboot Driver".
Click to expand...
Click to collapse
It doesn't show it shows under adb devices but not fastboot devices. Let me find the fastboot driver real quick and try. Thanks
jtford said:
It doesn't show it shows under adb devices but not fastboot devices. Let me find the fastboot driver real quick and try. Thanks
Click to expand...
Click to collapse
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Rootk1t said:
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Click to expand...
Click to collapse
Holy ****.... finally! I just needed the OnePlus_usb_driver_setup.exe in order to install the right driver from said directory. Big thanks man. Really!
TommyQuid said:
Does this still work on the recent 8T phones? Please do keep us updated on your situation. I'm thinking about buying this phone unlock the boot-loader, Sim unlock and get Lineage on it. I don't mind 45 days if they actually unlock it
Click to expand...
Click to collapse
So it was actually 40 days, I don't know why I said 45. Anyway, even after (48 days), it took me calling TMOBILE and having someone talk to their (OEM team) and start a conversation with them. 3 days later I was able to SIM unlock the phone. I was able to toggle OEM unlocking. Did the Fastboot command to get the Unlock Code, and sent it to OnePlus for "7 days". What the crap is all of this hassle? I left Android and went to Apple for 7 years. When I left, you could unlock a bootloader in minutes. For being so keen on allowing us to unlock our phones, it seems they give you a Circus of Hoops to jump thru "on Their timeline". Anyway, I actually think I may have screwed up the code because it was displayed on two lines from Fastboot. I sent it as one line. Hoping they sort it out and I don't have to reapply and wait another 7 days. What a mess!
jabe78 said:
So it was actually 40 days, I don't know why I said 45...
Click to expand...
Click to collapse
Thanks for the update