Related
Here is a tutorial to unlock the bootloader on our Moto X Play: http://www.gammerson.com/2015/08/steps-how-to-unlock-bootloader-of-moto-x-play.html
The warranty is not there after this, is there any way to lock it again without Motorola being able to see that it was unlocked?
Gesendet von meinem XT1562 mit Tapatalk
I guess every moto phones have the same process
http://forum.xda-developers.com/showthread.php?t=2753110
Sent from my Moto E using XDA Free mobile app
The unlocked bootloader warning message can easily be removed too: http://www.droidviews.com/remove-bootloader-unlocked-warning-on-moto-x-and-moto-x-2014/ I tested it and it work on our Moto X Play.
Oops.....completely forgot that this will wipe the phone (as all devices do when unlocking the bootloader).
Nico3d3 said:
We may not have CWM recovery and root yet, but here is a tutorial to unlock the bootloader on our Moto X Play: http://www.gammerson.com/2015/08/steps-how-to-unlock-bootloader-of-moto-x-play.html
Click to expand...
Click to collapse
We have TWRP recovery now, lets root it .
[Steps] How to Root Moto X Play by Flashing TWRP Recovery
Nico3d3 said:
The unlocked bootloader warning message can easily be removed too: http://www.droidviews.com/remove-bootloader-unlocked-warning-on-moto-x-and-moto-x-2014/ I tested it and it work on our Moto X Play.
Click to expand...
Click to collapse
This will work even if it's a Moto X 2014 logo? I'm a little uneasy in doing this.
karendar said:
This will work even if it's a Moto X 2014 logo? I'm a little uneasy in doing this.
Click to expand...
Click to collapse
So far, hasn't caused any issues for me.
Worked for me too
If I just remove the message, won't the technical assistance be aware that I unlocked the bootloader?
LuizHenrique91 said:
If I just remove the message, won't the technical assistance be aware that I unlocked the bootloader?
Click to expand...
Click to collapse
They already know since you requested the bootloader unlock code. From the terms and conditions:
THE FOLLOWING APPLIES TO ALL UNLOCKED DEVICES EXCEPT FOR DEVELOPER EDITION DEVICES. BY OBTAINING THE UNLOCK CODE FOR THIS DEVICE, IRRESPECTIVE OF WHETHER THE DEVICE'S BOOTLOADER IS SUBSEQUENTLY UNLOCKED OR ITS SOFTWARE OR OPERATING SYSTEM IS MODIFIED, USER AGREES TO WAIVE AND VOID ALL WARRANTIES
Click to expand...
Click to collapse
Removing the message is more for us, so we don't need to keep seeing it.
... disregard.... This is not the post you're looking for, move along.
Is unlocking for your device not dangerouse?
blackmaffia said:
Is unlocking for your device not dangerouse?
Click to expand...
Click to collapse
nope not dangerous, rather you can have more control over your device than Motorola gives you.
blackmaffia said:
Is unlocking for your device not dangerouse?
Click to expand...
Click to collapse
You just loose your warranty.
Sent from my XT1562 using Tapatalk
Failed to unlock Bootloader. Check "Allow OEM unlock" in Developer Options.
Anyone please help me.
I tried to install the official OTA and something went wrong. The device got stuck into bootloops. I entered into bootloader and decided to unlock it. As adviced by the xda thread i followed the instructions, but after getting the Unique key via Email, when i enter "fastboot unlock OEM UNLOCKKEY", it gives an error saying Failed to unlock Bootloader. Check "Allow OEM unlock" in Developer Options.
I cannot boot my phone.
Please help me.
Hamzasr said:
Anyone please help me.
I tried to install the official OTA and something went wrong. The device got stuck into bootloops. I entered into bootloader and decided to unlock it. As adviced by the xda thread i followed the instructions, but after getting the Unique key via Email, when i enter "fastboot unlock OEM UNLOCKKEY", it gives an error saying Failed to unlock Bootloader. Check "Allow OEM unlock" in Developer Options.
I cannot boot my phone.
Please help me.
Click to expand...
Click to collapse
i recall this problem happening to someone earlier, he solved it by clearing cache and factory wipe from recovery
bootloader>>recovery>>factory reset and clear cache
http://forum.xda-developers.com/mot...-how-to-downgrade-6-0-to-5-1-1-t3267253/page5
Hamzasr said:
Anyone please help me.
I tried to install the official OTA and something went wrong. The device got stuck into bootloops. I entered into bootloader and decided to unlock it. As adviced by the xda thread i followed the instructions, but after getting the Unique key via Email, when i enter "fastboot unlock OEM UNLOCKKEY", it gives an error saying Failed to unlock Bootloader. Check "Allow OEM unlock" in Developer Options.
I cannot boot my phone.
Please help me.
Click to expand...
Click to collapse
There is a thread I created for the first timers.
You have to check the option "allow oem unlock" in developer options.
Please check the whole forum for details before doing anything like this.
Sent from my XT1562 using Tapatalk
blackmaffia said:
Is unlocking for your device not dangerouse?
Click to expand...
Click to collapse
If you leave it unlocked after rooting then it can make your phone more susceptible to localised threats like someone stealing your phone and re-purposing it or stealing your data from it directly.
But for many the reward outweighs the risks and there are ways to mitigate.
Trying to unlock Moto X Play on Linux by using "fastboot oem get_unlock_data", but it just says waiting for device. I ran "adb devices" and also enable "Allow unlocking device" in the Developer menu. Am I missing something?
I have found the previous thread for the other G4 models, but I can't seem to get the flashing to work. I'm assuming we need a different variation of the OEM.img file.
Here is the previous thread for other models
http://forum.xda-developers.com/moto-g4/development/moto-g-4th-gen-how-to-remove-amazon-t3416587
Has anyone been successful at removing ads on the just released G4 Play from Amazon? XT1607
umrdyldo said:
I have found the previous thread for the other G4 models, but I can't seem to get the flashing to work. I'm assuming we need a different variation of the OEM.img file.
Here is the previous thread for other models
http://forum.xda-developers.com/moto-g4/development/moto-g-4th-gen-how-to-remove-amazon-t3416587
Has anyone been successful at removing ads on the just released G4 Play from Amazon? XT1607
Click to expand...
Click to collapse
try this strange trick, I'm not sure it will work, it might boot loop, but you can always just reflash the rom
download the STOCK oem.img from STOCK amazon firnware from https://www.filefactory.com/folder/c6cdedc45a775d27 (harpia amazon)
And then prepare to flash it (enter fastboot mode, put oem.img in mfastboot folder, open cmd)
type "mfastboot flash oem oem.img" but DO NOT press enter
then, start holding down the power button on your phone
about 2 seconds later, press enter on PC.
If all goes well, right after computer says "writing oem..." phone will reboot and there will be totally blank oem partition!
parrotgeek1 said:
try this strange trick, I'm not sure it will work, it might boot loop, but you can always just reflash the rom
download the STOCK oem.img from STOCK amazon firnware from https://www.filefactory.com/folder/c6cdedc45a775d27 (harpia amazon)
And then prepare to flash it (enter fastboot mode, put oem.img in mfastboot folder, open cmd)
type "mfastboot flash oem oem.img" but DO NOT press enter
then, start holding down the power button on your phone
about 2 seconds later, press enter on PC.
If all goes well, right after computer says "writing oem..." phone will reboot and there will be totally blank oem partition!
Click to expand...
Click to collapse
So the OEM.img is what contains the ads?
So we are just trying to find a way to write a stock XT1607 OEM.img
umrdyldo said:
So the OEM.img is what contains the ads?
So we are just trying to find a way to write a stock XT1607 OEM.img
Click to expand...
Click to collapse
Yes, OEM contains ads
But you can not flash another model OEM.img without unlocked bootloader
So I am trying to trick the bootloader into ERASING the OEM partition, so the ads files can't be read
parrotgeek1 said:
Yes, OEM contains ads
But you can not flash another model OEM.img without unlocked bootloader
So I am trying to trick the bootloader into ERASING the OEM partition, so the ads files can't be read
Click to expand...
Click to collapse
So are we looking for the OEM.img from the same model number but different carrier?
https://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=8
There are 3 listed on that page.
Let me know with a mention or quote or pm or something if you guys are successful. All of the other methods like using adb to hide com.amazon.phoenix failed for me as well as unlocking the bootloader. I made the mistake of assuming that a XT1607 is a XT1607 is a XT1607 and it didn't matter who you bought it from, so I went with the $99 option figuring if it had a locked bootloader, it would have a different model number (as is the case with LG and HTC phones) so if this method doesn't work, I'm going to contact Amazon to do an exchange for the version without ads and pay the difference.
Sent from my Moto G Play using XDA Labs
agentfusion said:
Let me know with a mention or quote or pm or something if you guys are successful. All of the other methods like using adb to hide com.amazon.phoenix failed for me as well as unlocking the bootloader. I made the mistake of assuming that a XT1607 is a XT1607 is a XT1607 and it didn't matter who you bought it from, so I went with the $99 option figuring if it had a locked bootloader, it would have a different model number (as is the case with LG and HTC phones) so if this method doesn't work, I'm going to contact Amazon to do an exchange for the version without ads and pay the difference.
Sent from my Moto G Play using XDA Labs
Click to expand...
Click to collapse
I'm thinking all we really need is the OEM.img from the non ad version amazon XT1607 and then run the flash as stated in the RSD Lite thread.
But I haven't found the zip for that phone. Unless it's an entirely different model number.
umrdyldo said:
So are we looking for the OEM.img from the same model number but different carrier?
https://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=8
There are 3 listed on that page.
Click to expand...
Click to collapse
No, we are not, you can not flash any OEM IMG that does not have software channel "amz" (look in about phone to see that). So you have to trick it into erasing it
umrdyldo said:
I'm thinking all we really need is the OEM.img from the non ad version amazon XT1607 and then run the flash as stated in the RSD Lite thread.
But I haven't found the zip for that phone. Unless it's an entirely different model number.
Click to expand...
Click to collapse
Random question: do you have an option to enable battery percentage, in the battery settings? The moto z droid does.
parrotgeek1 said:
Random question: do you have an option to enable battery percentage, in the battery settings? The moto z droid does.
Click to expand...
Click to collapse
No, mine doesn't have that option.
Sent from my SM-T550 using Tapatalk
parrotgeek1 said:
Random question: do you have an option to enable battery percentage, in the battery settings? The moto z droid does.
Click to expand...
Click to collapse
GravityBox will allow this.
How to enable embedded battery percentage on Moto G4 Play
parrotgeek1 said:
Random question: do you have an option to enable battery percentage, in the battery settings? The moto z droid does.
Click to expand...
Click to collapse
secfincorp said:
No, mine doesn't have that option.
Sent from my SM-T550 using Tapatalk
Click to expand...
Click to collapse
mx597turbo said:
GravityBox will allow this.
Click to expand...
Click to collapse
Yes, we have an option to enable battery percentage.
No, it does not require GravityBox.
Steps:
Enable System UI Tuner by long pressing and releasing Settings icon(gear icon)
Open System UI Tuner in Settings menu
Toggle embedded battery percentage to on
See images for help: https://imgur.com/a/HR8dr
Wow thanks!!
Sent from my Moto G Play using Tapatalk
secfincorp said:
Wow thanks!!
Click to expand...
Click to collapse
Please do not talk about this more in this thread, it's about ad removal
umrdyldo said:
I'm thinking all we really need is the OEM.img from the non ad version amazon XT1607 and then run the flash as stated in the RSD Lite thread.
But I haven't found the zip for that phone. Unless it's an entirely different model number.
Click to expand...
Click to collapse
It's not. And that's what burns me up. Every other manufacturer will at least increment the model number to differentiate between one that can unlock the bootloader and one that cannot. With the XT1607, it's the model *name* rather than the model number. The moto g4 play and the moto g4 play prime exclusive edition (that's ours).
I'm using that as my basis for an attempt to talk my way into an unlock code for my bootloader because I bought the Amazon prime version under the assumption that I'd be able to unlock the bootloader and root the device, since the model number is the same. Now I have to return my phone, be without a phone while it's shipped back, wait for the refund to clear, buy the same damn phone for $50 more, wait for it to be shipped out, and deal with Sprint to get the new one activated. All because it's the only carrier unlocked cdma phone that isn't like $400.
Sent from my Moto G Play using XDA Labs
no de bloat
So is there no way for de bloat and ad removal for the amazon moto g4 play XT1607?!?!?
I got two other stock files
XT1607_HARPIA_RETUS_MPI24.241-2.35-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
XT1607_HARPIA_CCAWS_MPI24.241-2.35_cid50_subsidy-CCAWS_regulatory-DEFAULT_CFC.xml.zip
The problem I'm having is when I try to flash an oem.img from one of the other phones I get a validation check error and the phone fails.
If this actually works, I just need to know how to bypass the validation check. Maybe I'm on the wrong path and will end up bricking my phone.
But looking at the other G4 ad removal thread, this is basically what they did. They flash a stock Moto G4 oem.img file and that file doesn't contain the bloat.
umrdyldo said:
I got two other stock files
XT1607_HARPIA_RETUS_MPI24.241-2.35-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
XT1607_HARPIA_CCAWS_MPI24.241-2.35_cid50_subsidy-CCAWS_regulatory-DEFAULT_CFC.xml.zip
The problem I'm having is when I try to flash an oem.img from one of the other phones I get a validation check error and the phone fails.
If this actually works, I just need to know how to bypass the validation check. Maybe I'm on the wrong path and will end up bricking my phone.
But looking at the other G4 ad removal thread, this is basically what they did. They flash a stock Moto G4 oem.img file and that file doesn't contain the bloat.
Click to expand...
Click to collapse
Right on. Maybe try and upload those files so people can try them out? or link them here.
Thomaslm800 said:
Right on. Maybe try and upload those files so people can try them out? or link them here.
Click to expand...
Click to collapse
https://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=8
They are ordered by name or date.
I am still not having any luck.
I'm wondering if the XT1602 is the same phone and if we can flash that OEM image.
I'm missing a step or two here I think. Very frustrating.
Hi,
So I recently got my hands on this new phone, and the blimming phone won't unlock. I'm using the XT1700!!! Not E3 Power!. It's on TESCO UK, and the System Version is "23.0.XT1700_S303_160829_UK". Yes, in developer options, OEM Unlocking is ticked! Tried two PCs, different drivers, different cables... idk.
I get the output on my phone to unlock with both "flashing unlock_critical" and "oem unlock"; both say "Unlock failed, returning to fastboot in 3s..."
This is the output in CMD:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 7.803s
Any suggestions? I'm really not sure.
jcolongo said:
Hi,
So I recently got my hands on this new phone, and the blimming phone won't unlock. I'm using the XT1700!!! Not E3 Power!. It's on TESCO UK, and the System Version is "23.0.XT1700_S303_160829_UK". Yes, in developer options, OEM Unlocking is ticked! Tried two PCs, different drivers, different cables... idk.
I get the output on my phone to unlock with both "flashing unlock_critical" and "oem unlock"; both say "Unlock failed, returning to fastboot in 3s..."
This is the output in CMD:
Any suggestions? I'm really not sure.
Click to expand...
Click to collapse
Yeah.
My E3 XT1700 was purchased from Tesco but its sim free, not locked to tesco.
I'm pretty sure if you read elsewhere in the unlock bootloader thread, the S303 firmware DOES NOT allow the bootloader to be unlocked.
My E3 is S124 firmware, although I have been running Lineage OS 14.1 (android 7.1.2) on it for some time.
Sorry but there's no way you can unlock this model
bubba1601 said:
Yeah.
My E3 XT1700 was purchased from Tesco but its sim free, not locked to tesco.
I'm pretty sure if you read elsewhere in the unlock bootloader thread, the S303 firmware DOES NOT allow the bootloader to be unlocked.
My E3 is S124 firmware, although I have been running Lineage OS 14.1 (android 7.1.2) on it for some time.
Sorry but there's no way you can unlock this model
Click to expand...
Click to collapse
Is there not anyway I can flash S124? Its MTK so I could surely use a flashtool?
bubba1601 said:
Yeah.
My E3 XT1700 was purchased from Tesco but its sim free, not locked to tesco.
I'm pretty sure you need to unlock the bootloader to do that.
Its really not worth the hastle.
S124 isn't available anywhere to download unless you pay for it, but you got to unlock the bootloader before you can flash it, as its only available as a TWRP back up.
I lost my IMEI number doing that and had to flash an S131 E3 power firmware and reflash my IMEI which wasn't easy at all.
I've just checked and S303 and S512 are indeed bootloader locked.
Click to expand...
Click to collapse
bubba1601 said:
bubba1601 said:
Yeah.
My E3 XT1700 was purchased from Tesco but its sim free, not locked to tesco.
I'm pretty sure you need to unlock the bootloader to do that.
Its really not worth the hastle.
S124 isn't available anywhere to download unless you pay for it, but you got to unlock the bootloader before you can flash it, as its only available as a TWRP back up.
I lost my IMEI number doing that and had to flash an S131 E3 power firmware and reflash my IMEI which wasn't easy at all.
I've just checked and S303 and S512 are indeed bootloader locked.
Click to expand...
Click to collapse
Damn man. Is there anyway I can root at least?
Click to expand...
Click to collapse
jcolongo said:
bubba1601 said:
Damn man. Is there anyway I can root at least?
Click to expand...
Click to collapse
Not unless you find one if these "one click root" apps via PC that supposedly magically root.
Its a shame these bootloaders cannot be advertised as not unlocking compatible, it would have saved you a lot of trouble.
Do try everything although to be fair, I've not seen anyone post about unlocking those two firmwares.
I'm only sorry I can't help more
Click to expand...
Click to collapse
bubba1601 said:
jcolongo said:
Not unless you find one if these "one click root" apps via PC that supposedly magically root.
Its a shame these bootloaders cannot be advertised as not unlocking compatible, it would have saved you a lot of trouble.
Do try everything although to be fair, I've not seen anyone post about unlocking those two firmwares.
I'm only sorry I can't help more
Click to expand...
Click to collapse
It's all good. I'm making progress however; managed to find a S124 SP flash firmware, but I'm scared to flash it, as I'll be out of a phone for 3 months which is a problem, as I need it for collage. I'll continue to look around.
Click to expand...
Click to collapse
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.
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