Is there a way to unlock bootloader yet? [TA-1021 variant] - Nokia 6 Questions & Answers

I've come across this blog: "unlockbootloader .org/tutorial/nokia-6"
It's looked okay but I still very doubt it. This kind of question doesn't received an answer on Nokia phone sub-website, runs by HMD, so I'm posting here.
Also, are there any work around with this phone or you and me will have to wait HMD move first?
Thanks.

I might have misunderstood something, but isn't the bootloader unlockable directly from developer options?
Clicking it gives an usual warning why you shouldn't do it, and asks confirmation. I haven't actually proceeded further because I have no need to unlock it currently..

Zuikkis said:
I might have misunderstood something, but isn't the bootloader unlockable directly from developer options?
Clicking it gives an usual warning why you shouldn't do it, and asks confirmation. I haven't actually proceeded further because I have no need to unlock it currently..
Click to expand...
Click to collapse
Yes, you're misunderstood this thing. The unlock bootloader option is there in developer options and there that's too in fastboot, it'll give you a FAIL error message if you choose it.
If you weren't interested in unlock Nokia 6, why are you comment on this topic?

Related

[WARNING] Do NOT lock your bootloader when on Android 5.1

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.

How to unlock bootloader (tutorial)

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?

Any chance of a recover program yet?

I'm on QAA and just rooted it. I'm guessing that the boot loader is still locked and nothing works. I've heard people say that the OEM unlock would unlock the boot loader but I don't believe that is the case.
Anybody??
Septaric said:
Anybody??
Click to expand...
Click to collapse
Recover program? This phones bootloader is unfortunately still locked and will probably never get unlocked. Only root is achievable right now...
That's what I thought. I had read a thread here somewhere that they thought the OEM unlock unlocked the bootloader.
Septaric said:
That's what I thought. I had read a thread here somewhere that they thought the OEM unlock unlocked the bootloader.
Click to expand...
Click to collapse
where?found it and share to us。
I called Sprint tech and they told me it was for security to keep someone else from returning your phone to stock settings. When I went to the boot loader the highlighted area seemed to bounce around between the options. Here's the link to the conversation.
https://forum.xda-developers.com/tmobile-s7-edge/help/oem-unlock-developer-options-t3328414

BTV-W09 EMUI 4.1 unlock bootloader

I'm not having any luck unlocking the boatloader. I've read the instructions, apparently I need a code from Huawei to do it, but they stopped giving out codes... am I completely screwed? is there some other process?
davidmoore said:
I'm not having any luck unlocking the boatloader. I've read the instructions, apparently I need a code from Huawei to do it, but they stopped giving out codes... am I completely screwed? is there some other process?
Click to expand...
Click to collapse
Usually you should search a bit before asking about help .... because the answer to your request may be already here
If you haven't found anything in the meantime, assuming you've already searched, you can take a look here as well.
I messaged the post owner about their credits. not sure how it'll work because DC unlocker doesn't specify the mediapad m3 on their website, but I'll see what they say.
surdu_petru said:
Usually you should search a bit before asking about help .... because the answer to your request may be already here
If you haven't found anything in the meantime, assuming you've already searched, you can take a look here as well.
Click to expand...
Click to collapse
alright, so I think I'm unlocked now. I'm able to adb reboot bootloader and I get a white screen that says phone unlocked/frp unlocked. when I attempt to flash recovery though it says "FAILED (remote: Command not allowed)"

T-Mobile Oneplus 8t 5g Sim unlock? and legit bootloader unlock

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

Categories

Resources