Related
Hi all,
I recently picked up a new Pixel and was wanting to flash it. I ended up enabling USB debugging and set OEM unlock within Android settings.
Yet when I use fastboot flashing unlock, it keeps telling me that OEM unlock isn't set. In my haste, I ran flash-all with a new Google build and this overwrote the existing ROM, but left the bootloader intact it seems. Now when I boot, it says I have a damaged OS and I should use recovery. The problem is that even recovery is damaged and it keeps rebooting to the bootloader. So adb won't work either. The only thing that works is fastboot.
Is there anything I can do to fix this or is it completely bricked? I can't seem to use fastboot to flash any ROM to the device - keeps erroring. I tried to match a ROM with the bootloader but that didn't work either.
Any ideas?
I used Nexus Root Toolkit when I got semi-bricked.
Use erase Command on flashboot for data and system then do flash_all again
As was mentioned, if you have fastboot you are ok. You can flash as mentioned above or use this -
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
NRT is good for people like me who barely know what they're doing, enough to get bricked in the first place like I did. What i like is that it takes away a little of the uncertainty about whether I'm using the right files.
I hadn't rooted and unlocked and done all the setup in about a year so I forgot everything.
Save yourself some trouble and look at the "TWRP bootloops" thread. It's easy to avoid if you follow some specific steps, frustrating otherwise.
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...
hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!
d j a said:
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!
Click to expand...
Click to collapse
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.
cam30era said:
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...
Click to expand...
Click to collapse
Yeah didn't think NRT would work because of the locked bootloader! Fastboot continue just gets out of fastboot - what is that gonna solve? I have a damaged set of partitions it seems - going from bootloader -> recovery boots back to the bootloader so it's clear that partition is damaged.
Is there any way I can just push some build to rebuild the partitions or can I do absolutely nothing until the bootloader is unlocked. And if so, how on earth can i unlock it if the only thing that works is fastboot?
hamazoza said:
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.
Click to expand...
Click to collapse
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
I'll try that tonight. FWIW, I know I copied the line from flash-all to just flash recovery.img and even the system image, and both failed.
The only difference I see between that and yours is you have '-w update'. Maybe that's the trick.
d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"
hamazoza said:
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"
Click to expand...
Click to collapse
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106
d j a said:
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106
Click to expand...
Click to collapse
I don't think that'll work. OEM unlock wasn't set in developer settings.
hamazoza said:
I don't think that'll work. OEM unlock wasn't set in developer settings.
Click to expand...
Click to collapse
You don't need that. I actually unlocked mine without it. The tool also has a unlock feature. Its worth a try.
Look for this forum post: flashing to stock android npd90g twrp t3424863
This helped me too. Only difference is I had TWRP installed.
Try unlocking bootloader via termjnal, then use the fastboot command via terminal (pc) fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable fastboot, then erase the partitions manually as mentioned in the tutorial and reflash them either manually or together using skipsoft / nrt or manual commands and a factory image.
Normally there should not be anything wrong with your bootloader image since modifying it is disabled for bootloader locked devices. Let us know about your progress.
Oh, also never flash an older system image than your current one.
Hi,
Apparently, I'm misunderstanding something. I'm trying to root my 2XL. I have unlocked the phone successfully, I believe. I have the notification screen at bootup. When I get to the task of flashing a factory image, I get the Failed notification, "FAILED (remote: Flashing is not allowed for Critical Partitions)". This occurs after ... writing 'bootloader_b'.
I was able to get Magisk installed but only 14.0 and I don't have root.
I haven't rooted anything in over 5 years so most of this stuff is pretty foreign.
Any advice would be welcome.
fastboot flashing unlock
then
fastboot flashing unlock_critical
uicnren said:
fastboot flashing unlock
then
fastboot flashing unlock_critical
Click to expand...
Click to collapse
Lord, you were fast.
Do I need to redo fastboot flashing unlock again before I flash the critical?
Also, my phone was on the latest 8.0.0. Would you recommend that I flash the new 8.1?
slingblade01 said:
Lord, you were fast.
Do I need to redo fastboot flashing unlock again before I flash the critical?
Also, my phone was on the latest 8.0.0. Would you recommend that I flash the new 8.1?
Click to expand...
Click to collapse
Unlock critical first then flash 8.1. Make a backup because this will wipe user data.
I am already unlocked and flashed 8.0 manually. I went to flash 8.1 today and got the OPs error. Are you saying that fastboot flashing unlock_critical will also wipe data? Damn that sucks if true.
SirVilhelm said:
I am already unlocked and flashed 8.0 manually. I went to flash 8.1 today and got the OPs error. Are you saying that fastboot flashing unlock_critical will also wipe data? Damn that sucks if true.
Click to expand...
Click to collapse
Oh yeah! It's definitely true. Unfortunately
uicnren said:
fastboot flashing unlock
then
fastboot flashing unlock_critical
Click to expand...
Click to collapse
Thx you saved my life <3
uicnren said:
fastboot flashing unlock
then
fastboot flashing unlock_critical
Click to expand...
Click to collapse
I get an error saying "device already unlocked" but it still won't let me flash my bootloader... (Hope you're still active here...)
clarkcant said:
I get an error saying "device already unlocked" but it still won't let me flash my bootloader... (Hope you're still active here...)
Click to expand...
Click to collapse
Are you on Pie or Oreo? Is your platform-tools up to date? Have you tried different USB A to USB C cables and ports?
uicnren said:
fastboot flashing unlock
then
fastboot flashing unlock_critical
Click to expand...
Click to collapse
Thanks man u saved my life. btw im not using a pixel, im in a xiaomi a3 but it worked!!
It doesnt work ....Help me to unlock critical
sadatkabir55 said:
It doesnt work ....Help me to unlock critical
Click to expand...
Click to collapse
Without details from you, we can't help you. For example, are you on the latest update? What else did you try? What worked for you and what didn't? Seriously, we can't read your mind. We can't see your phone. We can't perform miracles. It's a bit tiresome to have to ask you for things you should have already provided so we CAN help you.
Since you haven't given any details for anyone to go on, all I can tell you is that depending on the version of Android you are running, the "unlock critical" command may no longer be required, in which case you will get a message when executing the command.
I did not notice this was the forum dedicated to Pixel devices, sorry. I re-did my message in the Oneplus Nord dedicated forum regarding my issue that, however, seems to be the same as the one people encountered here.
Here is the link if anyone feels like helping me : https://forum.xda-developers.com/t/...itions-need-assistance-details-below.4274551/
slingblade01 said:
Lord, you were fast.
Do I need to redo fastboot flashing unlock again before I flash the critical?
Also, my phone was on the latest 8.0.0. Would you recommend that I flash the new 8.1?
Click to expand...
Click to collapse
yeah he was like in 1 min
I have oneplus 8 5g IN2017. I was flashing the global rom.I unlocked the bootloader. but fastboot flashing unlock is taking too long. It just keep running and did'nt finish. Please guide. I am so tired of this.
Also Device is stuck in bootloader.
Khateeb2110 said:
I have oneplus 8 5g IN2017. I was flashing the global rom.I unlocked the bootloader. but fastboot flashing unlock is taking too long. It just keep running and did'nt finish. Please guide. I am so tired of this.
Click to expand...
Click to collapse
You'll need to read about your own phone. This thread is about the Pixel 2 XL. Different manufacturers tend to have different ways to unlock the bootloader.
Also, people who follow this thread are unlikely to know about OnePlus. Find a OnePlus-thread to ask for help.
(WTF...!) LG V30/V30+/V30S Bootloader Unlock & Root Method (With Clear Instructions)
WTF...! LG V30,V30+,V30S (MOST VARIANTS)
BOOTLOADER UNLOCK, TWRP, ROOT INSTRUCTIONS HERE
>>>CLICK HERE TO POST #193<<<
_______________________________________________
ChazzMatt said:
Due to the July 2018 LG security patch blocking the WTF bootloader unlock exploit, I've added instructions in post #1 of US998, H930 and India H930DS Oreo KDZ threads to use dev patched LGUP to downgrade to earlier versions of KDZ in order to use this WTF bootloader unlock exploit. You can always update to newer firmware AFTER bootloader unlock.
I've also updated the instructions in this thread to include references to the July 2018 security patch situation.
Click to expand...
Click to collapse
_______________________________________________
My Bootloader Unlock Crazy Method (video) - here - https://youtu.be/NtrGYqAW5OU
that is 1's test unlock bin file http://www.mediafire.com/file/e6c9zcvcfolyfcf/test.bin/file
that is new unlock bin http://www.mediafire.com/file/xnwcck1wr5w4qz2/new_unlock.bin/file
Thank you for supported
Sorry for my English
EDIT: ignore these next few pages of posts. We were all trying to figure this all out. It was crazy stuff, and initially @TxanMoe did brick his phone. But he recovered, and we figured out what worked and what didn't.
Skip to post #56 for the first success story replicating this method. After that, it was off to the races!
Everything after post #56 on is relevant, while everything between here and there is not really worth reading, as there was lots of false speculation proved wrong.
We figured out LG Oreo has a great bootloader unlock flaw that can be exploited so we can install TWRP and root. Also since the initial post @TxanMoe perfected the "fake" bootloader unlock.bin code. (Originally he used a Huawai M8 unlock code -- from an LG G4 thread. Crazy stuff.)
Post #193 has the full instructions, as does the op above.
POST #56
JWnSC said:
Your the man! Followed your exact steps. It worked. I now have twrp and unlocked bootloader on my ls998(converted to us998). Thanks for this
Click to expand...
Click to collapse
____________________________
(back to original post #2)
TxanMoe said:
so, i search on google lg unlock.bin
i found lg g4 unlock.bin in this link https://forum.xda-developers.com/g4/general/unlock-bin-t3158596
Click to expand...
Click to collapse
I actually don't see an LG G4 unlock.bin in that thread. I see someone asking for one. Somebody supplied one from an M8, but I don't see one from an LG G4. OR if they did, they edited off, back in 2015. So, where did you find it? Which post?
But good luck to you, if this is true. You definitely have everyone's attention!
Sorry
From M8 unlock.bin
TxanMoe said:
Sorry
From M8 unlock.bin
Click to expand...
Click to collapse
Wait. You flashed an Huawei M8 unlock.bin code onto an AT&T LG V30 H931 and UNLOCKED the bootloader? After of course crossflashing H930 Oreo KDZ and basically bricking your phone.
The only reason I halfway believe this is because the guy with the rooted H932 in China is running Galaxy 8 TWRP with parts of H930 flashed over the phone.
And because you were one of the first to crossflash your phone in this forum. So, you know what you are doing.
___________
So, how does your phone identify now in About Phone? H930 or H931? Or Canadian H933 (which you had cross flashed to earlier.)
In LGUP, in download mode, how does it identify? Even after I flashed US998 over LS998 (Frankenstein thread), in download mode with LGUP, the phone still showed as LS-998.
I upload screen record video wait a few minutes
That is check my imei no
Now my sim is not working
ChazzMatt said:
Wait. You flashed an Huawei M8 unlock.bin code onto an AT&T LG V30 H931 and UNLOCKED the bootloader? After of course crossflashing H930 Oreo KDZ and basically bricking your phone.
The only reason I halfway believe this is because the guy with the rooted H932 in China is running Galaxy 8 TWRP with parts of H930 flashed over the phone.
And because you were one of the first to crossflash your phone in this forum. So, you know what you are doing.
___________
So, how does your phone identify now in About Phone? H930 or H931? Or Canadian H933 (which you had cross flashed to earlier.)
In LGUP, in download mode, how does it identify? Even after I flashed US998 over LS998 (Frankenstein thread), in download mode with LGUP, the phone still showed as LS-998.
Click to expand...
Click to collapse
My original phone is At & t (h931)
I flashed to h933 kdz on my phone (no error)
And yesterday i flash to h930
After My phone is bricked
Can't enter anything mode
But Qualcomm driver install & remove my simcard
Connect to usb when my phone is fastboot mode
My download m8 unlock.bin flashed
Show some error massage
But succeed unlock and normal boot
Sorry very weak My english
TxanMoe said:
But Qualcomm driver install & remove my simcard
Connect to usb when my phone is fastboot mode
My download m8 unlock.bin flashed
Show some error massage
But succeed unlock and normal boot
Sorry very weak My english
Click to expand...
Click to collapse
The Qualcomm driver part interests us. Others have talked about possibly using that vs the LG drivers.
The M8 unlock.bin file being used is crazy.
Yes, I linked to your earlier post where you cross flashed your H931 to a Canadian H933. You were very expert at doing it.
Here it is again, for those who missed it.
https://forum.xda-developers.com/showpost.php?p=76459829&postcount=4
I wonder if I can try this method, but I am already on Oreo h930. Would I have to flash the Oreo h930 or h933 over my h931? Then flash m8 unlock bin?
H930 and m8 unlock.bin
After you get this error massage
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.003s]
writing 'unlock'...
FAILED (remote: Error!! Wrong unlock key size)
finished. total time: 0.006s
But device is unlock
I see you tried fastboot oem unlock as your last command before you were able to successfully flash recovery.
Addiso said:
I see you tried fastboot oem unlock as your last command before you were able to successfully flash recovery.
Click to expand...
Click to collapse
i write some test command because i get error massage
but after reboot my device is already unlocked
and then reflash twrp
success
TxanMoe said:
H930 and m8 unlock.bin
After you get this error massage
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.003s]
writing 'unlock'...
FAILED (remote: Error!! Wrong unlock key size)
finished. total time: 0.006s
But device is unlock
Click to expand...
Click to collapse
Thanks, I'll prepare to try this out. I'll get the files ready and try to get to it tomorrow. I tried downloading the unlock bin from your post but it says the user removed the file.
Who-Lep said:
Thanks, I'll prepare to try this out. I'll get the files ready and try to get to it tomorrow. I tried downloading the unlock bin from your post but it says the user removed the file.
Click to expand...
Click to collapse
working link https://drive.google.com/file/d/0BzC0lkkywIrLN08tNTJyNmpKTEFzSEZGeDJOMWdzWE9lMFZN/edit
but you can't download
i upload attachment zip
TxanMoe said:
working link https://drive.google.com/file/d/0BzC0lkkywIrLN08tNTJyNmpKTEFzSEZGeDJOMWdzWE9lMFZN/edit
but you can't download
i attachment zip
Click to expand...
Click to collapse
Thanks! Downloading now. I have the unlock.bin, lgup+30ll, & downloading the h93020d_00_open_EU_op_0326.kdz. I believe that is the right kdz?
Who-Lep said:
Thanks! Downloading now. I have the unlock.bin, lgup+30ll, & downloading the h93020d_00_open_EU_op_0326.kdz. I believe that is the right kdz?
Click to expand...
Click to collapse
yes
H93020d_00_OPEN_EU_OP_0326.kdz
after you flashed
your devices is bricked
but you can enter fastboot (connect usb, Hold Power+Vol Down, Show LG LOgo RE-press Power , but keep Vol Down )
TxanMoe said:
yes
H93020d_00_OPEN_EU_OP_0326.kdz
after you flashed
your devices is bricked
but you can enter fastboot (connect usb, Hold Power+Vol Down, Show LG LOgo RE-press Power , but keep Vol Down )
Click to expand...
Click to collapse
Okay, let write out the steps so I am clear.
1. Use lgup and update to h930.kdz and brick
2. Boot into fastboot and flash unlock.bin
3. Reboot?
Who-Lep said:
Okay, let write out the steps so I am clear.
1. Use lgup and update to h930.kdz and brick
2. Boot into fastboot and flash unlock.bin
3. Reboot?
Click to expand...
Click to collapse
yes
TxanMoe said:
yes
Click to expand...
Click to collapse
Would I select upgrade or partition dl?
wow... That really sounds crazy and weird, and tbh like it wouldnt work at all ?
But if this seriously works...
More devices being bootloader unlocked is nice
Does everything work now though? Like the modem, your imei and so on?
This is my first OnePlus device so I'm a little confused. I've followed a bootloader unlock guide found here; however, it says my device will be wiped once it is unlocked. Problem is, the device isn't wiping so I can only assume it hasn't unlocked. Can someone point me to a guide that works?
I've already got my unlock_code.bin file from OnePlus and I flashed it before trying the unlock commands. Every command claimed to be successful; yet, there seem to be no changes whatsoever.
Try "fastboot oem device-info" without quotes, to get bootloader info. Should tell you if it's unlocked or not
Allen77777 said:
Try "fastboot oem device-info" without quotes, to get bootloader info. Should tell you if it's unlocked or not
Click to expand...
Click to collapse
I'll give this a go tomorrow when I get back to my computer. Thanks
noxarcana said:
This is my first OnePlus device so I'm a little confused. I've followed a bootloader unlock guide found here; however, it says my device will be wiped once it is unlocked. Problem is, the device isn't wiping so I can only assume it hasn't unlocked. Can someone point me to a guide that works?
I've already got my unlock_code.bin file from OnePlus and I flashed it before trying the unlock commands. Every command claimed to be successful; yet, there seem to be no changes whatsoever.
Click to expand...
Click to collapse
unlock_code.bin
I remember my old HTC´s have unlock_code.bin but not OnePlus!
You are sure you flash unlock_code.bin???
Read here:
https://forum.xda-developers.com/showpost.php?p=79741564&postcount=2
Matija Gubec said:
unlock_code.bin
I remember my old HTC´s have unlock_code.bin but not OnePlus!
You are sure you flash unlock_code.bin???
Read here:
https://forum.xda-developers.com/showpost.php?p=79741564&postcount=2
Click to expand...
Click to collapse
I'll have a look at it after I get off work; but, yea, many of the guides I looked at previously said I had to get an unlock token file from OnePlus to unlock the bootloader. I used as to get the code and then used the site down below to get the unlock_code.bin file from OnePlus.
https://www.oneplus.com/unlock_token
Regardless, flashing that file not the "fastboot OEM unlock," or whatever the command is, worked and I'm certain my device is still locked.
First thing I did after work was to try and unlock it again. I'm not sure what happened or what I did differently, but it worked. Bootloader is unlocked and now I'm trying to figure out my next step.
Hi, I have a oneplus 7T that belongs to T-MOBILE, I decided to make it global, after doing the process I made the mistake of blocking the bootloader after that the terminal does not pass the error "Your device is corrupt. It can't be trusted and will not boot ", I can only enter the fastboot mode, I have tried to enter the EDL mode to do the process again through the MSM through the adb commands and through a deep flash cable and np I have been lucky.
I have also tried to unlock the bootloader but it does not allow me, because it gives me an error related to that I have to enable unlocking through the android developer.
The pc only recognizes the terminal as "Android Bootloader Interface".
So if you can acces the fastboot mode have you tried flashing a oos10/11 fastboot rom ?
saintjimmy1984 said:
So if you can acces the fastboot mode have you tried flashing a oos10/11 fastboot rom
Click to expand...
Click to collapse
saintjimmy1984 said:
So if you can acces the fastboot mode have you tried flashing a oos10/11 fastboot rom ?
Click to expand...
Click to collapse
Yes, I tried, but it gives me an error in the transfer of the files.
Never relock bootloader as easy to hard brick. Try to set up msmtool on another pc and good usb-C cable. Also u should move this post to Q-A
Hi
I had is same problem, and is very easy to solve.
You only have use the method for which to use for covert the device in global versión, but only
you must do the steps until the equipment is unlocked, and then instead of continuing with the procedure, what you must do is flash a stock firmware that corresponds to the region of your mobile.
It's all a matter of taking the procedure to the point where it allows it to be flashed through fastboot
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com
HueyT said:
Never relock bootloader as easy to hard brick. Try to set up msmtool on another pc and good usb-C cable. Also u should move this post to Q-A
Click to expand...
Click to collapse
alright I will keep it in mind.
Stronger1101 said:
Hi
I had is same problem, and is very easy to solve.
You only have use the method for which to use for covert the device in global versión, but only
you must do the steps until the equipment is unlocked, and then instead of continuing with the procedure, what you must do is flash a stock firmware that corresponds to the region of your mobile.
It's all a matter of taking the procedure to the point where it allows it to be flashed through fastboot
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com
Click to expand...
Click to collapse
mmm, I will try this method, although as I understand I have to use the T-Mobile ROM in this case, I have a good time looking for it and I did not find it, I will continue at it.
wade99.3 said:
mmm, I will try this method, although as I understand I have to use the T-Mobile ROM in this case, I have a good time looking for it and I did not find it, I will continue at it.
Click to expand...
Click to collapse
It is not necessary to use the TMobile rom, you just have to get to the point where the phone is unlocked with the command "fastboot flashing unlock_critical" and then jump to steps 7 and 8 of the guide referenced in the link I shared.
Stronger1101 said:
It is not necessary to use the TMobile rom, you just have to get to the point where the phone is unlocked with the command "fastboot flashing unlock_critical" and then jump to steps 7 and 8 of the guide referenced in the link I shared.
Click to expand...
Click to collapse
ok I'll try
Stronger1101 said:
Hi
I had is same problem, and is very easy to solve.
You only have use the method for which to use for covert the device in global versión, but only
you must do the steps until the equipment is unlocked, and then instead of continuing with the procedure, what you must do is flash a stock firmware that corresponds to the region of your mobile.
It's all a matter of taking the procedure to the point where it allows it to be flashed through fastboot
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you very much, the problem was solved, I changed the phone cable and tried it with windows 7 and finally I was able to unlock the bootloader.