Database Info

Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016

Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016​
I was surprised to not find this information in any of the forums.
This is why I'm posting this thread to prevent further confusion and future xda-enthusiastic "Phone Buyers" from Oppo's decision.
Oppo has of this year decided to "lock the access to its Bootloader".
By "access" i mean no way to access it with "adb reboot fastboot" and "adb reboot bootloader" and any "Bootup Button combination".
Its not only hitting new phones but also old phones.
All the latest ColorOS Firmwares will prevent you from accessing the Bootloader.
All Project Spectrum alpha/beta's for OLD and NEW phones will prevent you from accessing the Bootloader.
If you are using a custom rom and want to try out any of the above stock roms. Be !WARNED! you will lose access to the Bootloader!
They not only removed the access to the Bootloader but also removed the "fastboot binarys" itself.
If by chance you are able to access the Bootloader and want to use fastboot commands. All commands will result in "FAILED (remote: unknown command)"
I noticed this and raised questions in the official Oppo forum:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is the official reply:
I hope this helps enthusiastic users in their "phone choice".
For me access to the Bootloader and having fastboot commands are on top of the list when it comes to choosing a new phone.
Update:
It seems like that Oppo decided to bring back fastboot and the possibility to unlock the bootloader in their "Project Spectrum" ROM.
But apparently not in all devices!
ColorOS (The Stock ROM) is unaffected and remains with a defunct fastboot. Confirmed by Oppo R9 Plus users. Which is Oppo's latest Qualcomm based phone.

Thank God i didn't upgrade !

You can unlock the bootloader and access the fastboot by downloading the old version of the ColorOS.
Thanks.

Mulham82 said:
You can unlock the bootloader and access the fastboot by downloading the old version of the ColorOS.
Thanks.
Click to expand...
Click to collapse
this is only true for devices which had firmware releases in 2015. my Oppo R7S (European Version) for example was already shipped with a firmware that is hit by their new strategy. no old firmware to unlock the bootloader or access fastboot.

celoxocis said:
Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016​
I was surprised to not find this information in any of the forums.
This is why I'm posting this thread to prevent further confusion and future xda-enthusiastic "Phone Buyers" from Oppo's decision.
Oppo has of this year decided to "lock the access to its Bootloader".
By "access" i mean no way to access it with "adb reboot fastboot" and "adb reboot bootloader" and any "Bootup Button combination".
Its not only hitting new phones but also old phones.
All the latest ColorOS Firmwares will prevent you from accessing the Bootloader.
All Project Spectrum alpha/beta's for OLD and NEW phones will prevent you from accessing the Bootloader.
If you are using a custom rom and want to try out any of the above stock roms. Be !WARNED! you will lose access to the Bootloader!
They not only removed the access to the Bootloader but also removed the "fastboot binarys" itself.
If by chance you are able to access the Bootloader and want to use fastboot commands. All commands will result in "FAILED (remote: unknown command)"
I noticed this and raised questions in the official Oppo forum:
this is the official reply:
I hope this helps enthusiastic users in their "phone choice".
For me access to the Bootloader and having fastboot commands are on top of the list when it comes to choosing a new phone.
Click to expand...
Click to collapse
Thanks for the info, it´s something to keep in mind certainly.

Thank you for your effort in this. Any process on the r7s front?
Website signature

Yes , I got caught out by this
I purchased my R7s due to Oppo's previously root friendly attitude only to find I could not root when I had updated my phone to the latest version
I have expressed my displeasure to Oppo

this is exactly what happened to me when I purchased the R7S. I did my research before purchase and saw that all previous Oppo phones were unlockable using fastboot. when I bought the phone. fastboot binarys were removed in LK.
there has been alot of effort by xda-dev's to find a way to unlock the affected phones.
I can only say this much. a way has been found. which was used to put pressure on Oppo including all the incoming complains.
Im a project Spectrum beta tester and the good news is. that the project Spectrum beta roms have fully working fastboot binarys. which will allow an bootloader unlock.
if you look in the Oppo forum. you will see that I provided an official TWRP and am currently working on a CyanogenMod.
no need to give up or to pass on this mid-ranger at all. just patients

is there really no way to root the phone? i don't understand Chinese and in the original way i can't use the OPPO R9 Phone

If anyone can point me towards where to find older R7 PlusF firmware that would be great. Doesn't seem to be listed on oppo website anymore.
"R7plusfEX_11_OTA_005_all_201508180100"
Is available by host server aborts download at 100mb/1.3gb

Looks like I missed out this thread... Only recently I discovered such situation at Oppo forum. Very disappointed by this...

is there any way for unlocking fastboot for oppo a37 which only has coloros3.0.0 rom?

hamzachaudhry36 said:
is there any way for unlocking fastboot for oppo a37 which only has coloros3.0.0 rom?
Click to expand...
Click to collapse
Have you checked if you have fastboot access at all? Install minimal adb & fastboot enable debugging mode in developer options and issue the command "adb reboot fastboot".
If the phone simply reboots then Oppo has not included fastboot binarys for your device.

celoxocis said:
Have you checked if you have fastboot access at all? Install minimal adb & fastboot enable debugging mode in developer options and issue the command "adb reboot fastboot".
If the phone simply reboots then Oppo has not included fastboot binarys for your device.
Click to expand...
Click to collapse
Yeah phone simply reboots but is there any solution for flashing new fastboot bunarys on my device

hamzachaudhry36 said:
Yeah phone simply reboots but is there any solution for flashing new fastboot bunarys on my device
Click to expand...
Click to collapse
No unless an older ROM version had it and it was removed with an upgrade.
Try reverting to the oldest ROM version you can find and try again.

celoxocis said:
No unless an older ROM version had it and it was removed with an upgrade.
Try reverting to the oldest ROM version you can find and try again.
Click to expand...
Click to collapse
The problem is my phone got out with latest rom version .....
Is there any way to port fastboot binarys from some other rom to mine ....?????
There is a phone named Xaomi 2 Prime which has same specs(GPU, CPU and RAM) is there a way to port those files ....??

hamzachaudhry36 said:
The problem is my phone got out with latest rom version .....
Is there any way to port fastboot binarys from some other rom to mine ....?????
There is a phone named Xaomi 2 Prime which has same specs(GPU, CPU and RAM) is there a way to port those files ....??
Click to expand...
Click to collapse
NO!!! You will brick your phone!
Different manufacturer totally different signature's!
There is no way! Because Oppo locked it down!
You should have done research before buying a phone. If you wanted root, Xposed, custom ROM, etc

celoxocis said:
NO!!! You will brick your phone!
Different manufacturer totally different signature's!
There is no way! Because Oppo locked it down!
You should have done research before buying a phone. If you wanted root, Xposed, custom ROM, etc
Click to expand...
Click to collapse
Yeah i just bought it cuz people said it is the best phone in medium budget... and it is popular....
but if anything happens to my phone i won't be able to install even stock rom in it with PC....
can i atleast port twrp for my device to get root and randroid backup functions which i really want...?????

hamzachaudhry36 said:
Yeah i just bought it cuz people said it is the best phone in medium budget... and it is popular....
but if anything happens to my phone i won't be able to install even stock rom in it with PC....
can i atleast port twrp for my device to get root and randroid backup functions which i really want...?????
Click to expand...
Click to collapse
NO! Again! for TWRP to work you need an unlocked bootloader which you don't have and can't have because of Oppo removing fastboot!
Return your phone and get a different phone.
Avoid Oppo at all costs!
I suggest Asus Zenfone 2 it has all you want and even official CyanogenMod support!
It's close to the specifications of the a37f.
https://wiki.cyanogenmod.org/w/Z00L_Info
And stop using so many questions marks!
It only makes you look stupid.

celoxocis said:
NO! Again! for TWRP to work you need an unlocked bootloader which you don't have and can't have because of Oppo removing fastboot!
Return your phone and get a different phone.
Avoid Oppo at all costs!
I suggest Asus Zenfone 2 it has all you want and even official CyanogenMod support!
It's close to the specifications of the a37f.
https://wiki.cyanogenmod.org/w/Z00L_Info
And stop using so many questions marks!
It only makes you look stupid.
Click to expand...
Click to collapse
Thanks but it won't be refunded in my country. So i am stuck. I can get Samsung J5 2015 which is rooted and has many functions which i like from my brother in exchange of it but Oppo provides many functions which samsung does not like Oppo has almost no bloatwares, Built-in app locker, more ram, 4G, built-in customizations, and a camera that is the best.
Thanks for all the help. I just wanted to confirm, my friend said that we can make a port of twrp so i asked.
and i am an idiot and a noob so i use many question marks sometimes

Slot Unbootable: Load Error, Device State: Locked

Hi guys, right now I cannot boot my phone up, it is giving me "ERROR: Slot Unbootable: Load Error"
-When I Click start it brings me back to the same screen
-Restarting bootloader brings me to back to the same screen
-Download mode errors in "ERROR: Operation Denied
-Cannot boot into recovery mode, same error (Unbootable: Load Error)
-Cannot run fastboot flashing unlock:
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.003s
-Cannot flash img :
FAILED (remote: Flashing is not allowed in Lock State)
-Cannot enable OEM Unlock in developer's option since I cannot boot the phone up.
-flash-all.bat gives me "Operation is not allowed in Lock State"
The device is used when I bought it so I cannot RMA it or get a refund.
Am I out of luck? See below for screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Look into this:
https://skipsoft.net/skipsoft-unified-android-toolkit/
Sent from my [device_name] using XDA-Developers Legacy app

jasonbiggs said:
Look into this:
https://skipsoft.net/skipsoft-unified-android-toolkit/
Click to expand...
Click to collapse
That only works with OEM switch ticked, won't do anything for him now
This exact scenario happened to me as well, phone randomly vibrated and turned off and I got this.
Why not just call them and explain the issue but don't mention it being used? I'm sure they'll still RMA it.

crixley said:
That only works with OEM switch ticked, won't do anything for him now
This exact scenario happened to me as well, phone randomly vibrated and turned off and I got this.
Why not just call them and explain the issue but don't mention it being used? I'm sure they'll still RMA it.
Click to expand...
Click to collapse
To Google? Wouldn't they think it would be shady if you got the phone brand new from somewhere (like craigslist) and it wasn't working? I guess calling them wouldn't hurt.

Zilchary said:
To Google? Wouldn't they think it would be shady if you got the phone brand new from somewhere (like craigslist) and it wasn't working? I guess calling them wouldn't hurt.
Click to expand...
Click to collapse
I'm not advising anything here, but I'm not sure how they'd know. If you mention it straight off the bat I'm sure they aren't going to do anything for you.

Have you tried switching slots to see if the other one would boot by typing fastboot --set-active=b
I had a similar issue and that was able to fix it, but then again my device was unlocked, so not sure if that will help

bbacon said:
Have you tried switching slots to see if the other one would boot by typing fastboot --set-active=b
I had a similar issue and that was able to fix it, but then again my device was unlocked, so not sure if that will help
Click to expand...
Click to collapse
You can't switch slots with a locked bootloader.
I feel like we should be able to fastboot flash stock images even if bootloader locked, or at least separate the recovery from the boot image. Seems like a dumb idea how they have it currently, since if anything happens to the boot image you're stuck with a paperweight.

Not sure if you were able to get a fix, but you could always try to download the factory image and remove the "-w" from the .bat file. Of course, if there's nothing on the phone, keep the "-w" and do a full wipe.
https://developers.google.com/android/images

b00ster23 said:
Not sure if you were able to get a fix, but you could always try to download the factory image and remove the "-w" from the .bat file. Of course, if there's nothing on the phone, keep the "-w" and do a full wipe.
https://developers.google.com/android/images
Click to expand...
Click to collapse
Can't flash with a locked bootloader. They don't even allow you to flash their own signed images.

crixley said:
Can't flash with a locked bootloader. They don't even allow you to flash their own signed images.
Click to expand...
Click to collapse
I thought you could flash the image, but not sideload OTA's? Couldn't remember as I've had my VZW Pix2 unlocked.... It's possible that it's the other way around, OTA's but not images.
**EDIT**
Yep, OTA's not full images. Sounds like this PIX was botched, then the BL was locked.
https://developers.google.com/android/ota

b00ster23 said:
I thought you could flash the image, but not sideload OTA's? Couldn't remember as I've had my VZW Pix2 unlocked.... It's possible that it's the other way around, OTA's but not images.
**EDIT**
Yep, OTA's not full images. Sounds like this PIX was botched, then the BL was locked.
https://developers.google.com/android/ota
Click to expand...
Click to collapse
Yep it is a ridiculous concept, I have no idea what they were thinking. I had this exact same thing happen and needed to RMA, when if I had an unlocked bootloader I could have easily fixed it. Then I received a refurb, and with refurbs you cannot unlock the bootloader lol
I think I'm probably done with pixels after this one. The quality control is terrible.

crixley said:
Yep it is a ridiculous concept, I have no idea what they were thinking. I had this exact same thing happen and needed to RMA, when if I had an unlocked bootloader I could have easily fixed it. Then I received a refurb, and with refurbs you cannot unlock the bootloader lol
I think I'm probably done with pixels after this one. The quality control is terrible.
Click to expand...
Click to collapse
If you received a refurbished Google phone (not Verizon) that had the inability to unlock the BL, I would send that puppy back until I got one. I mean, why spend the big $$ into a phone and have a warranty, and then have features removed after using the warranty. No way in my book.

b00ster23 said:
If you received a refurbished Google phone (not Verizon) that had the inability to unlock the BL, I would send that puppy back until I got one. I mean, why spend the big $$ into a phone and have a warranty, and then have features removed after using the warranty. No way in my book.
Click to expand...
Click to collapse
Several people have sent back 3 or 4 and had the same thing happen every time. Unfortunately I can't go a week per time without a phone since I use mine for work, and they refuse to send me a new one.

crixley said:
Yep it is a ridiculous concept, I have no idea what they were thinking. I had this exact same thing happen and needed to RMA, when if I had an unlocked bootloader I could have easily fixed it. Then I received a refurb, and with refurbs you cannot unlock the bootloader lol
I think I'm probably done with pixels after this one. The quality control is terrible.
Click to expand...
Click to collapse
I have the same problem. My bootloader is unlocked. Can you please help me?

Zilchary said:
To Google? Wouldn't they think it would be shady if you got the phone brand new from somewhere (like craigslist) and it wasn't working? I guess calling them wouldn't hurt.
Click to expand...
Click to collapse
Hi @Zilchary .
So, finally what have you did?
My Pixel 2 gets that same error after December 2018 Security Patch applied.
I bought my Pixel 2 directly from Google Store USA.
So I enter the CHAT for PIXEL SUPPORT (from Google REPAIR , then Contact US), And Explain I got stuck in Bootloader locked with Error: Slot Unbootable
They immediately understand the problem and tell me I need to RMA (Return merchandise authorization) the phone,
so the Information they ASK ME was :
1) My Phone IMEI, with that info they tell me That I had purchased the Phone in Google Store
2) So they ASK for the "ORDER ID" in my account in Google Store, And with that info they ask me to choose between two options:
3) a) Me to Send first my phone, wait for delivered to them (they need to check the phone) and then send me a REFURBISHED PHONE. or b) PRE-Charge my Credit Card with the price of a Pixel 2,
so They send right now a REFURBISHED phone and IF they don't get my Pixel 2 in "X" day they will actually apply the Charge to my Credit Card.
So the way I see the matters, PIXEL 2 phones has 24 months of warranty in countrys where Google sell it, but you will have problems if YOU DON`T HAVE the "ORDER ID" of the Google Store.
If you actually have this "ORDER ID" because the seller gave you that info when you Purchase, YOU can just tell the PIXEL SUPPORT to send you the FEDEX information (the FEDEX LABEL TO SEND THE PHONE) to your NEW EMAIL (your actual email)
But If you don't have the "ORDER ID" you will have to try to contact the seller to get that "ORDER ID" or you should explain to COSTUMER SERVICES that you don't have it but that will be messy.
and don`t even imagine if the PHONE has BAD IMEI report.
Let me know what happens with your phone
and Have you try this link to github ? (read section: "ERRORS" between sections "iYTBP" (Youtube) and "CameraNX")

Hi @sabrosolatino
The phone was actually my sister's, I asked her what she did and this was her response :
I called 866 246 6453 to the google support line.
The Android reboot system came up and I couldn't reboot or get out of the same screen. The first time I called they told me to click a combination of keys to try to reboot the system. Nothing worked. He told me he needs the order ID # to process the warranty to get a replacement phone. I didn't have the order ID # and told me to call back when I have it. He also said because I don't have the order ID #, I can call their partner repair centers and bring it in to get it fixed or have someone come to the house to fix it in real time. I called the 2nd time and spoke to a different rep, he told me I have a 2-year warranty if there are no physical damages to the phone (until 4/23/20) and the next step is to ship out my phone and get a replacement. They confirmed my email address and sent me the shipping labels. He didn't need an order ID # to process the replacement.
So yes, there was nothing we could do since we couldn't boot it into recovery, ended up shipping out the phone without an order ID #.
Hope everything goes well for you!

I was also told that after she got her phone RMA'd, the phone she got was a refurbished phone at the agent said "It's basically brand new".

This isn't a new issue, it typically happens with something doesn't flash right. Using this tool and applying the monthly update helps me out of this bind every time.

that did it, select reboot bootloader then fastboot --set-active=a in command prompt window, then use the flash-all.bat with "-w" removed in the extracted factory image. Profit!

Zilchary said:
Hi guys, right now I cannot boot my phone up, it is giving me "ERROR: Slot Unbootable: Load Error"
-When I Click start it brings me back to the same screen
-Restarting bootloader brings me to back to the same screen
-Download mode errors in "ERROR: Operation Denied
-Cannot boot into recovery mode, same error (Unbootable: Load Error)
-Cannot run fastboot flashing unlock:
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.003s
-Cannot flash img :
FAILED (remote: Flashing is not allowed in Lock State)
-Cannot enable OEM Unlock in developer's option since I cannot boot the phone up.
-flash-all.bat gives me "Operation is not allowed in Lock State"
The device is used when I bought it so I cannot RMA it or get a refund.
Am I out of luck? See below for screenshot.
Click to expand...
Click to collapse
Oh, man. This is exactly what happened to my Pixel 2. I bought mine stock, new, from VZW in August 2018. November OTA came in and the phone didn't install the update properly and I landed on this screen. There was absolutely nothing I could do. A few fastboot commands would return some data but because of the locked bootloader I was SOL.
I RMA'd mine. Google didn't even ask questions. They just asked me to turn the phone in.
I'm sorry you can't RMA yours.
I don't know, friend. You might be looking at a paperweight.

How to root your Pixel 3a/3a XL WITHOUT TWRP

**Your Bootloader MUST be unlocked**
**does not work on Android Q**
1) Download Magisk APK from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 and install the APK
2) download your system image from https://developers.google.com/android/images Make sure you check settings-->about phone to get your current software version to your PC
3) extract the boot.img and copy it to your Pixel
4) open Magisk and select install then write to a file. Select boot.img
5) wait for it to finish then copy the patched boot image back to your PC
6) open a powershell window from the folder you copied the patched boot image to and either ADB reboot bootloader or turn off your phone and hold the volume down and power key until your in fastboot mode, plug it in and run "fastboot getvar current-slot"
7) take note which boot letter pops up either A or B
8) run "fastboot flash boot_<Letter> <patched_image_name>.img
9)"fastboot reboot"
PROFIT
This also appears to break Google Pay even though Magisk Hide is enabled. If anyone has a work around please share!
Link to the newest Google USB drivers:
https://developer.android.com/studio/run/win-usb

Nice post. As I posted in another thread. I would test the patched image with the following command.
"fastboot boot <patch_image_name>.img"
If it works then flash it permanently.

In case anyone wants to put the old style nav bar on their new phone this still works
How to disable Android Pie gestures on the Google Pixel 3
1. Install any 3rd-party launcher of your choice. This is a must because otherwise, you won’t have a launcher app left once we’re done with this tutorial!
2. Set up ADB on your PC. Here’s a tutorial we previously wrote that you should you through the process.
3. Connect your Pixel 3 to your PC and open up a command prompt/terminal in the directory where you downloaded the ADB binary. Enter the following command depending on your OS:
Windows Command Prompt
adb shell
Windows Power Shell
.\adb shell
macOS/Linux Terminal
./adb shell
4. Now, enter the following command to uninstall the Pixel Launcher from the current user.
pm uninstall -k --user 0 com.google.android.apps.nexuslauncher
5. Now, enter this command to re-enable the stock navigation bar after reboot. This is the setting you’ll be changing by issuing the below command.
settings put secure system_navigation_keys_enabled 1
6. Reboot your Pixel 3.
7. Once you’re booted back up, you should see the original 3 button navigation bar layout and the original vertical stacked card recent apps overview.

Does not work for me on my Pixel 3a XL with Android Q Beta 3.
All the steps appear to succeed but when the phone is rebooted and Magisk Manager run it says "Magisk is not installed."
I also notice that the Magisk patched boot.img is _much_ smaller than the original. 31 MB vs. 64 MB. Doesn't seem to have kept the phone from booting though so I don't know if this is normal.
Code:
[[email protected] bonito-qpp3.190404.015]$ fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.022s
[[email protected] bonito-qpp3.190404.015]$ fastboot flash boot_b magisk_patched.img
Sending 'boot_b' (30756 KB) OKAY [ 1.160s]
Writing 'boot_b' OKAY [ 0.496s]
Finished. Total time: 1.734s
[[email protected] bonito-qpp3.190404.015]$ fastboot reboot
Rebooting
Finished. Total time: 0.068s
[[email protected] bonito-qpp3.190404.015]$ ls -lh boot.img boot_magisk_patched.img
-rw-r--r-- 1 carl users 64M Jan 1 2009 boot.img
-rw-r--r-- 1 root root 31M May 10 10:48 magisk_patched.img

clipcarl said:
Does not work for me on my Pixel 3a XL with Android Q Beta 3.
All the steps appear to succeed but when the phone is rebooted and Magisk Manager run it says "Magisk is not installed."
I also notice that the Magisk patched boot.img is _much_ smaller than the original. 31 MB vs. 64 MB. Doesn't seem to have kept the phone from booting though so I don't know if this is normal.
Click to expand...
Click to collapse
Doesn't work on Q Beta 3

Anyone here about the progress on the Q magisk? Haven't wandered over to pixel land in a while; seems like I recall him saying he was onto something last time I did.

Last I heard Magisk works for the Pixel 1 and 2 running Android Q but due to different software on the Pixel 3 it still isnt working but the dev has said he is working on it. I am sure with time he will get it fixed since he has a Pixel 3.
krabman said:
Anyone here about the progress on the Q magisk? Haven't wandered over to pixel land in a while; seems like I recall him saying he was onto something last time I did.
Click to expand...
Click to collapse

Worked fine after downgrading my 3aXL to Pie.
Thanks for the instructions!

Worked great. As stated, Google Pay didn't work, but Chase and Mario Run worked (which they didn't on my last rooted device). Thanks!

It's totally wrong but I flash both A and B and call it a day. Makes it easier to remember the commands. As a point of interest for those on Fi using the eSim remember to go through the setup using it again after you unlock or you're going to get a toast asking you to connect to Fi every ten minutes. I had assumed it would just remember the sim information, not a good assumption, I had to factory reset and go through the setup again.

echoarcade28 said:
Worked great. As stated, Google Pay didn't work, but Chase and Mario Run worked (which they didn't on my last rooted device). Thanks!
Click to expand...
Click to collapse
How is that possible? With my very very old Nexus 5, a custom ROM and Magisk, Google Pay perfecty works... (I'm waiting for the 3a)

Thanks for this thread! I just want to inform folks who just bought their Pixel 3a/Pixel 3a XL from T-Mobile, that root is not possible as of now since the bootloader is locked. I was misinformed thinking the bootloader would be unlocked. However, the bootloader came locked and is dependent upon factory unlocking your device. In which, T-Mobile only offers after 45 days being on their service and paying the device off in full

xFierce said:
Thanks for this thread! I just want to inform folks who just bought their Pixel 3a/Pixel 3a XL from T-Mobile, that root is not possible as of now since the bootloader is locked. I was misinformed thinking the bootloader would be unlocked. However, the bootloader came locked and is dependent upon factory unlocking your device. In which, T-Mobile only offers after 45 days being on their service and paying the device off in full
Click to expand...
Click to collapse
You sure not confusing their carrier unlock policy with unlocking bootloader. The phone's all have locked bootloaders they are just easily unlocked using fastboot.
Sent from my [device_name] using XDA-Developers Legacy app

shadyshadow said:
You sure not confusing their carrier unlock policy with unlocking bootloader. The phone's all have locked bootloaders they are just easily unlocked using fastboot.
Click to expand...
Click to collapse
I tried to unlock the bootloader through fastboot but received an error. On tmobile pixel 3a devices the bootloader is linked to OEM unlocking of the device unfortunately. OEM unlocking is grayed out on tmobile sim locked devices until they're permanently unlocked by tmobile.

xFierce said:
I tried to unlock the bootloader through fastboot but received an error. On tmobile pixel 3a devices the bootloader is linked to OEM unlocking of the device unfortunately. OEM unlocking is grayed out on tmobile sim locked devices until they're permanently unlocked by tmobile.
Click to expand...
Click to collapse
Wow..ok 45 days long time to be adding data, installing apps etc. be good to play safe and buy from Google store
Sent from my [device_name] using XDA-Developers Legacy app

shadyshadow said:
Wow..ok 45 days long time to be adding data, installing apps etc. be good to play safe and buy from Google store
Click to expand...
Click to collapse
Nah, just a few days. All they need to do is hop on Twitter and ask for SIM unlock. They'll generally do it without too much hassle so long as it's not a brand-new account and it's in good standing.
Got my 6T unlocked by them long before it was paid off, and my 3aXL SIM unlocked by them before the first payment was even made.

Not exactly a root question,
But I rooted and then tried to install the Magisk viper. I keep getting prompted to install drivers and then after a wait, a confirmation to reboot
Then all over again.
Any body found a way to get viper working without TWRP?

jcrompton said:
Not exactly a root question,
But I rooted and then tried to install the Magisk viper. I keep getting prompted to install drivers and then after a wait, a confirmation to reboot
Then all over again.
Any body found a way to get viper working without TWRP?
Click to expand...
Click to collapse
I just installed it Working great.
Download from here.

poncespr said:
I just installed it Working great.
Download from here.
Click to expand...
Click to collapse
Thanks
Did install successfully.
But I'm not familiar with that build .... Is there a way to load old saved profiles? I can't find that in the some what different UI

ok, so maybe someone here can help me out, I don't get it, why I cant unlock the bootloader on my 3a xl.
I could enable OEM unlock and USB debugging in developer settings.
"adb reboot bootloader" sets it into fastboot mode. But the command "fastboot flashing unlock" does in fact nothing.
I dont even get an error message?!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I exit out with "fastboot reboot". That does work. Could it be that Google has blocked it somehow until the 15 days return window? (Bought the 3a xl in the german google online store)

[Guide] Unlocking the bootloader

The Nokia 7.2, surprisingly, comes with an unlockable bootloader. The information is shared by TechMesto and I am just re-using it to create this guide.
Notes:
Unlocking the bootloader may void the device's warranty.
All existing data on the device will be erased.
To unlock:
Update: Nokia has disabled the unlock ability with the December MR. You can only unlock if you downgrade your phone to an old release first. You can get it at Nokia Care or by buying remote flashing services.
Before you start: Make sure that you have platform-tools downloaded on your PC. You need to open a CMD or Terminal window in the folder where you have saved the platform-tools, unless you have installed them system-wide.
• First of all, enable Developer Options by tapping 7 times on BuildID in "About phone".
• Then go to developer options and enable OEM Unlocking option.
• Now reboot the phone into bootloader/fastboot mode. You can use the adb command:
Code:
adb reboot-bootloader
or else use hardware keys to reboot to bootloader mode.
• Make sure the phone is detected in fastboot mode. Then send the OEM unlocking command:
Code:
fastboot flashing unlock
• Confirm the unlock on the phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
• That's it!
You can also do the unlock_critical if you plan to flash the bootloader.

Reserved for future use.

I am on a Nokia 7.2, a dual-sim variant with 6GB RAM and 128 GB ROM. The model name is TA-1196.
I am currently having issues with this method, whenever I try to flash unlock, prior to the V1.160 update, the fastboot will report back saying "Write to device failed (unknown error)".
If anyone would enlighten me I would be happy to hear.
Edit: Currently on build number 00WW_1_060
Edit 2.0: Works after updating to build 00WW_1_160. Seems Nokia enabled this method by mistake. Who knows?

KohGeek said:
I am on a Nokia 7.2, a dual-sim variant with 6GB RAM and 128 GB ROM. The model name is TA-1196.
I am currently having issues with this method, whenever I try to flash unlock, prior to the V1.160 update, the fastboot will report back saying "Write to device failed (unknown error)".
If anyone would enlighten me I would be happy to hear.
Edit: Currently on build number 00WW_1_060
Edit 2.0: Works after updating to build 00WW_1_160. Seems Nokia enabled this method by mistake. Who knows?
Click to expand...
Click to collapse
Hi, looks like you were initially doing flash unlock instead of flashing unlock? And since there was nothing to flash, it failed.

singhnsk said:
Hi, looks like you were initially doing flash unlock instead of flashing unlock? And since there was nothing to flash, it failed.
Click to expand...
Click to collapse
I was using flashing, and as my edit has said, it seems the option to unlock the bootloader was only enabled after version 160.

KohGeek said:
I was using flashing, and as my edit has said, it seems the option to unlock the bootloader was only enabled after version 160.
Click to expand...
Click to collapse
That's okay, but the output you got wasn't appropriate for that command. If the unlock support isn't allowed it will say "flashing unlock is not allowed". Or in case the bootloader isn't including that command at all, it will say "Unknown command".
I might be wrong too, but your output isn't something i've seen on any of the phones i've owned, whether unlockable or non-unlockable. That output is what I usually get when the command is not proper, or the drivers aren't properly installed or the fastboot device isn't properly responding. Rebooting to bootloader should usually fix it. At least it does on other Nokia and Sharp phones.

singhnsk said:
That's okay, but the output you got wasn't appropriate for that command. If the unlock support isn't allowed it will say "flashing unlock is not allowed". Or in case the bootloader isn't including that command at all, it will say "Unknown command".
I might be wrong too, but your output isn't something i've seen on any of the phones i've owned, whether unlockable or non-unlockable. That output is what I usually get when the command is not proper, or the drivers aren't properly installed or the fastboot device isn't properly responding. Rebooting to bootloader should usually fix it. At least it does on other Nokia and Sharp phones.
Click to expand...
Click to collapse
I was curious too, it kicked me off the bootloader screen when I was doing that on version 060, but it seems all is well now

https://nokiamob.net/2019/11/02/off...nlock-the-nokia-7-2-and-nokia-6-2-bootloader/

I unlocked bootloader now how to root this phone they didn't released kernel source for preparing twrp should i root the phone with magisk patched boot.img??

Coolboy996 said:
I unlocked bootloader now how to root this phone they didn't released kernel source for preparing twrp should i root the phone with magisk patched boot.img??
Click to expand...
Click to collapse
You can use TWRP or patched image to root the 7.2

Can confirm that it is still unlockable. Got 2 of them today from Argos in the UK (Scotland). They are on 00WW_1_130 with security batch from 2019/08/05.
Only thing I had to do was enable internet and reboot to get the option to stop being greyed out.

Just got mine today and it forced a system update upon activation. I was unable to unlock the bootloader.

allc0re said:
Just got mine today and it forced a system update upon activation. I was unable to unlock the bootloader.
Click to expand...
Click to collapse
Are you sure? Has Horrendously Menacing Dicks actually started blocking people having reasonable control of their 7.2 devices after letting them have it for so long?

allc0re said:
Just got mine today and it forced a system update upon activation. I was unable to unlock the bootloader.
Click to expand...
Click to collapse
Yep. They blocked the ability with the most recent December MR.

singhnsk said:
Yep. They blocked the ability with the most recent December MR.
Click to expand...
Click to collapse
Ah that sucks. Did you try connecting to the internet and rebooting? That enabled the option to enable OEM Unlocking in developer settings for me.

CGarz said:
Ah that sucks. Did you try connecting to the internet and rebooting? That enabled the option to enable OEM Unlocking in developer settings for me.
Click to expand...
Click to collapse
I was able to turn on OEM Unlocking in Developer Options, but running the command in fastboot failed.

That really sucks. Now no devs will buy it =(.

allc0re said:
I was able to turn on OEM Unlocking in Developer Options, but running the command in fastboot failed.
Click to expand...
Click to collapse
I know they planned to lock it down ; however were you using the most recent fastboot (platform-tools). I know I had issues with not having most current versions.

bkttk2 said:
I know they planned to lock it down ; however were you using the most recent fastboot (platform-tools). I know I had issues with not having most current versions.
Click to expand...
Click to collapse
I also can not unlock the bootloader after update security 05/12/2019...MB no longer unlockable bootloader any more.

Lamtanloc512 said:
I also can not unlock the bootloader after update security 05/12/2019...MB no longer unlockable bootloader any more.
Click to expand...
Click to collapse
Think we may be out of luck then, but one last suggestion. I noticed when reading through the thread on user indicated they were using "flash" instead of "flashing" when trying to unlock the bootloader.
I know I personally did the same thing at first. Did anyone confirm that "flashing" was used?
I know the older methods used flash. Just asking.

[PayPal Reward] GM1915 Converted International; Root/TWRP Questions [SOLVED]

I posted a thread on this, commented on a couple other threads, posted on Reddit, and I simply cannot get straight answers across the board. All the feedback I'm getting is different. I am willing to PayPal friends and family $5 to the first person that can answer my questions with links to sources just so I can ensure the information I'm getting is correct. I haven't rooted a phone since my 1st Gen Moto X so I'm out of the loop, but have a understanding of everything.
I have a GM1915 OnePlus 7 Pro that is T-Mobile SIM unlocked. I followed the tutorials HERE and HERE to flash the global firmware and all went well. Only issue I had was my SIM was being detected but no service, so I did an OTA update to 10.0.3 and my service is working fine now. Here are where my questions begin:
1. Now that I have installed the international firmware I don't need to get a bootloader unlock from T-Mobile/OnePlus, correct? I can just use the OEM unlock option and unlock via fastboot?
I have had people tell me I am good to enable OEM unlocking and use fastboot oem unlock, others have told me I still need to request a unlock, others tell me to downgrade to SP3. I just need a straightforward answer: Can I use OEM unlocking or do I need to request an unlock from OnePlus?
2. I know bootloader/root can sometimes cause certain applications to not function, but I've also read Magisk has a setting to correct this. I'm mainly just concerned with Google Pay, is there a method for it to still function with root?
Again, I've had some people tell me I can't use Google Pay, Netflix, or anything like that at all, others tell me Magisk Hide and SafetyNet will fix this issue. I also had an individual state "However, recent changes coming might thwart this.". Again, can I use Google Pay or can't I?
3. Part of me would actually like to use the phone stock for a week or so to see if I even feel like I need root access. I am currently on OS 10.0.3, if I update to the newest OS (looks like 10.3.1 is the newest) will I still be able to root with Magisk and flash TWRP? I would assume yes since you can do an OTA update and keep Magisk, but I just wanted to verify.
So if I update to 10.3.1 can I still follow the same tutorial listed under question 1 and it will work? Doesn't the most recent version of TWRP/Magisk support 10.3.1? Or will I need to use MSM and go back to 9.5.X (can't remember the exact version, but it's the OS it puts you on when you follow the steps for international firmware flashing)? Can I even go back to 9.5.X after updating to 10.3.1? I see release notes for TWRP that state is now have Android Q support but I just want to ensure it's compatibile with 10.3.1 or whatever the newest OS is.
Code:
mauronofrio matarrese
2019-08-18T15:04:57Z
Upload New Blobs for Android Q
I know regardless my phone is going to get wiped, I just want to be prepared on what I need to do if I decide to root.
I don't need links to tutorials, there are plenty of them and I understand how flashing TWRP and Magisk works, I just need my above questions answered with sources. I have searched around for a couple days and cannot get straight forward answers for any of these. First to answer every question with sources I'll send $5 PayPal.

ThisIsCheez said:
I posted a thread on this, commented on a couple other threads, posted on Reddit, and I simply cannot get straight answers across the board. All the feedback I'm getting is different. I am willing to PayPal friends and family $5 to the first person that can answer my questions with links to sources just so I can ensure the information I'm getting is correct. I haven't rooted a phone since my 1st Gen Moto X so I'm out of the loop, but have a understanding of everything.
I have a GM1915 OnePlus 7 Pro that is T-Mobile SIM unlocked. I followed the tutorials HERE and HERE to flash the global firmware and all went well. Only issue I had was my SIM was being detected but no service, so I did an OTA update to 10.0.3 and my service is working fine now. Here are where my questions begin:
1. Now that I have installed the international firmware I don't need to get a bootloader unlock from T-Mobile/OnePlus, correct? I can just use the OEM unlock option and unlock via fastboot?
I have had people tell me I am good to enable OEM unlocking and use fastboot oem unlock, others have told me I still need to request a unlock, others tell me to downgrade to SP3. I just need a straightforward answer: Can I use OEM unlocking or do I need to request an unlock from OnePlus?
2. I know bootloader/root can sometimes cause certain applications to not function, but I've also read Magisk has a setting to correct this. I'm mainly just concerned with Google Pay, is there a method for it to still function with root?
Again, I've had some people tell me I can't use Google Pay, Netflix, or anything like that at all, others tell me Magisk Hide and SafetyNet will fix this issue. I also had an individual state "However, recent changes coming might thwart this.". Again, can I use Google Pay or can't I?
3. Part of me would actually like to use the phone stock for a week or so to see if I even feel like I need root access. I am currently on OS 10.0.3, if I update to the newest OS (looks like 10.3.1 is the newest) will I still be able to root with Magisk and flash TWRP? I would assume yes since you can do an OTA update and keep Magisk, but I just wanted to verify.
So if I update to 10.3.1 can I still follow the same tutorial listed under question 1 and it will work? Doesn't the most recent version of TWRP/Magisk support 10.3.1? Or will I need to use MSM and go back to 9.5.X (can't remember the exact version, but it's the OS it puts you on when you follow the steps for international firmware flashing)? Can I even go back to 9.5.X after updating to 10.3.1? I see release notes for TWRP that state is now have Android Q support but I just want to ensure it's compatibile with 10.3.1 or whatever the newest OS is.
Code:
mauronofrio matarrese
2019-08-18T15:04:57Z
Upload New Blobs for Android Q
I know regardless my phone is going to get wiped, I just want to be prepared on what I need to do if I decide to root.
I don't need links to tutorials, there are plenty of them and I understand how flashing TWRP and Magisk works, I just need my above questions answered with sources. I have searched around for a couple days and cannot get straight forward answers for any of these. First to answer every question with sources I'll send $5 PayPal.
Click to expand...
Click to collapse
Firstly I can't give you a reputable source, and I don't want any money. I actually recently bought a Renewed Oneplus 7 Pro from amazon when it was 420, its the Black 8GB 256GB T-Mobile GM1915 model. So here is what I found out , and currently running Ill post some pics to show you
1. If you followed the guides above exactly and everything went smoothly your pefectly fine to use OEM Unlock, it basically installs a version of the firmware that doesn't check for a boot loader unlock token. I had originally requested one as well than found this nifty guide and it worked amazingly.
2. Yes it will work perfectly fine with Magisk, just use the Hide Magisk , it will resintall under a new name. Than you can even go further and use magisk hide to hide it from each app independently. As for google pay I have mine setup and it worked fine. I haven't actually been able to go into store and use it as we are very closed off in home now, but It allowed me to add my card fine, verify with my bank and all that good stuff. As for netflix yes it will work but since you unlocked bootloader you lose the Widevine DRM L1 certification and thus can't watch in HDR anymore. It still works fine though and honestly looks alright to me.
3. I had updated my T-Mobile OS all the way to latest version forget what it was at the moment, and than I did the tutorial to unlock the bootloader and flash twrp/magisk/rom. It worked out perfectly fine so you should be fine as well. What I would do is use the tutorial above unlock bootloader, because that version of the OS doesn't check for unlock token, than flash a stock Global rom 10.3.2 is avaliable now. and enjoy it for awhile and when your ready install a custom rom and magisk.
I'll add some pictures of things you asked about. Sadly I can't show my model number in system due to rom but i showed it connected to my pc.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Kireyev said:
Firstly I can't give you a reputable source, and I don't want any money. I actually recently bought a Renewed Oneplus 7 Pro from amazon when it was 420, its the Black 8GB 256GB T-Mobile GM1915 model. So here is what I found out , and currently running Ill post some pics to show you.
[/HIDE]
Click to expand...
Click to collapse
This was more than helpful, and a first hand account. I know you said that you didn't want any money but I am prepared to send it, if you don't want it I will donate to a charity of your choice.
3. I had updated my T-Mobile OS all the way to latest version forget what it was at the moment
Click to expand...
Click to collapse
When you say this, did you update your firmware OTA on the T-Mobile firmware, or the Global/International firmware using OTA? I don't want to skip any incremental updates and cause issues so I might update using OTA to the newest it provides than use Oxygen Updater to get to 10.3.2. As long as I can be on the newest firmware and still unlock my bootloader and flash TWRP I'm fine. I mainly got this phone because it ticks every feature box I want and it can be rooted, but I'm up for using it stock for a while to see if I even want root.
Edit: I reread you post and think I looked over something about unlocking the bootloader. So the specific version of the firmware you flash to to swap to the international firmware doesn't require an unlock token, so if I wanted to use the OEM unlock I'd need to be back on that version, but if I wanted to unlock after I update to 10.3.2 I'd need to request a token. Am I understanding that correctly?

ThisIsCheez said:
This was more than helpful, and a first hand account. I know you said that you didn't want any money but I am prepared to send it, if you don't want it I will donate to a charity of your choice.
When you say this, did you update your firmware OTA on the T-Mobile firmware, or the Global/International firmware using OTA? I don't want to skip any incremental updates and cause issues so I might update using OTA to the newest it provides than use Oxygen Updater to get to 10.3.2. As long as I can be on the newest firmware and still unlock my bootloader and flash TWRP I'm fine. I mainly got this phone because it ticks every feature box I want and it can be rooted, but I'm up for using it stock for a while to see if I even want root.
Click to expand...
Click to collapse
It was the T-Mobile firmware. 10.0.3 version. I had done it before I was even thinking about unlocking bootloader and flashing. Than when I saw the custom ROMS + Kernels where you can gain massive performance gains or optimize battery like mad I was sold on it. Plus the ugly t-mobile boot screens annoyed me. It is an amazing phone and prices can be had at its a steal. Also their is a TWRP that lets you dual boot and use shared data partition. So you could have one boot as a custom ROM, and another as stock and have the data shared in a common partition. Get a little of both ^_^
Like I have two profiles and one is more performance / battery Optimized
This other was more for fun on seeing how far I can push scores I am bored during this lockdown lol

Kireyev said:
It was the T-Mobile firmware. 10.0.3 version. I had done it before I was even thinking about unlocking bootloader and flashing. Than when I saw the custom ROMS + Kernels where you can gain massive performance gains or optimize battery like mad I was sold on it. Plus the ugly t-mobile boot screens annoyed me. It is an amazing phone and prices can be had at its a steal. Also their is a TWRP that lets you dual boot and use shared data partition. So you could have one boot as a custom ROM, and another as stock and have the data shared in a common partition. Get a little of both ^_^
Like I have two profiles and one is more performance / battery Optimized
This other was more for fun on seeing how far I can push scores I am bored during this lockdown lol
Click to expand...
Click to collapse
Thanks for all the replies. Would you care to answer this question below? And if you do not want the cash what charity would you like it donated to?
Edit: I reread you post and think I looked over something about unlocking the bootloader. So the specific version of the firmware you flash to to swap to the international firmware doesn't require an unlock token, so if I wanted to use the OEM unlock I'd need to be back on that version, but if I wanted to unlock after I update to 10.3.2 I'd need to request a token. Am I understanding that correctly?

ThisIsCheez said:
Thanks for all the replies. Would you care to answer this question below? And if you do not want the cash what charity would you like it donated to?
Edit: I reread you post and think I looked over something about unlocking the bootloader. So the specific version of the firmware you flash to to swap to the international firmware doesn't require an unlock token, so if I wanted to use the OEM unlock I'd need to be back on that version, but if I wanted to unlock after I update to 10.3.2 I'd need to request a token. Am I understanding that correctly?
Click to expand...
Click to collapse
You know I am honestly not sure on this part, I did the bootloader unlock right after I followed that tutorial with the MSM tool. I am pretty sure its just the t-mobile firmware that blocks you from doing OEM unlock with out token. Not the global. But one way to find out be enable OEM unlock in developer settings, and run the fastboot oem unlock cmd. See if it works. If not you have your answere and will have to go back to other version. If you want you can always relock bootloader. I would test this but as I've already unlocked , re-locking and unlocking probably not give proper answer. But if you want I can install 10.3.3 lock bootloader and try to unlock it again lol.
EDIT: a test in sues.

Kireyev said:
You know I am honestly not sure on this part, I did the bootloader unlock right after I followed that tutorial with the MSM tool. I am pretty sure its just the t-mobile firmware that blocks you from doing OEM unlock with out token. Not the global. But one way to find out be enable OEM unlock in developer settings, and run the fastboot oem unlock cmd. See if it works. If not you have your answere and will have to go back to other version. If you want you can always relock bootloader. I would test this but as I've already unlocked , re-locking and unlocking probably not give proper answer. But if you want I can install 10.3.3 lock bootloader and try to unlock it again lol.
EDIT: a test in sues.
Click to expand...
Click to collapse
So I tried fastboot oem unlock after updating to 10.3.1 and it asked me if I wanted to unlock without prompting for an unlock token. I didn't choose the option to unlock, I kept it locked, but I think if I can get that far I should be able to unlock without a token on 10.3.1

ThisIsCheez said:
So I tried fastboot oem unlock after updating to 10.3.1 and it asked me if I wanted to unlock without prompting for an unlock token. I didn't choose the option to unlock, I kept it locked, but I think if I can get that far I should be able to unlock without a token on 10.3.1
Click to expand...
Click to collapse
I can confirm now officially. After locking my bootloader, using MSM tool to go back to T-Mobile updating to 10.0.3 and trying to unlock bootloader it wouldn't work as I thought.
When using the MSM tool to go to international version and updating all the way to 10.3.2, it worked perfectly fine. So you can be on global rom and not worry about being able to unlock bootloader later due to updates Very awesome can get on global rom and not compromise bootloader so can have all security in place

Kireyev said:
I can confirm now officially. After locking my bootloader, using MSM tool to go back to T-Mobile updating to 10.0.3 and trying to unlock bootloader it wouldn't work as I thought.
When using the MSM tool to go to international version and updating all the way to 10.3.2, it worked perfectly fine. So you can be on global rom and not worry about being able to unlock bootloader later due to updates Very awesome can get on global rom and not compromise bootloader so can have all security in place
Click to expand...
Click to collapse
You are the GOAT. Not only does this help me but hopefully some other members of the community that wish to update and try stock before unlocking the bootloader.

Kireyev said:
I can confirm now officially. After locking my bootloader, using MSM tool to go back to T-Mobile updating to 10.0.3 and trying to unlock bootloader it wouldn't work as I thought.
When using the MSM tool to go to international version and updating all the way to 10.3.2, it worked perfectly fine. So you can be on global rom and not worry about being able to unlock bootloader later due to updates Very awesome can get on global rom and not compromise bootloader so can have all security in place
Click to expand...
Click to collapse
Just as verification that I wasn't using the PayPal reward as a ploy to get someone to respond and bail, Kireyev declined payment so I made a donation to ExtraLife in his name. Thanks again for your help to me and the community.
https://www.extra-life.org/index.cfm?fuseaction=donorDrive.participant&participantID=408732

Kireyev said:
I can confirm now officially. After locking my bootloader, using MSM tool to go back to T-Mobile updating to 10.0.3 and trying to unlock bootloader it wouldn't work as I thought.
When using the MSM tool to go to international version and updating all the way to 10.3.2, it worked perfectly fine. So you can be on global rom and not worry about being able to unlock bootloader later due to updates Very awesome can get on global rom and not compromise bootloader so can have all security in place
Click to expand...
Click to collapse
hey thank you both for this thread but admittedly i am a little lost and i really do not want to brick this device, ive rooted devices in the pas, some even requiring hardware modifications to do so. but i just want to make sure i do everything right
im on a sim unlocked t-mobile 10.0.3.gm31cb right now
what are the exact steps i need to follow to unlock bootloader, and get on the latest rom ?

Outta said:
hey thank you both for this thread but admittedly i am a little lost and i really do not want to brick this device, ive rooted devices in the pas, some even requiring hardware modifications to do so. but i just want to make sure i do everything right
im on a sim unlock
Click to expand...
Click to collapse
If you follow the main guide on xda exactly you're going be fine. Once on global your essentially done because than you can flash a twrp through fastboot and install any rom, kernel you want. As well as magisk. The most important part is that msm guide. Now if you want to be more official get an unlock token and do it the regular way through fastboot with the unlock token. It took about a week in a half to get mine. But the msm guide works perfectly. Also I've gotten my device stuck in multiple fastboot loops and stuff their is always a way back.

Kireyev said:
If you follow the main guide on xda exactly you're going be fine. Once on global your essentially done because than you can flash a twrp through fastboot and install any rom, kernel you want. As well as magisk. The most important part is that msm guide. Now if you want to be more official get an unlock token and do it the regular way through fastboot with the unlock token. It took about a week in a half to get mine. But the msm guide works perfectly. Also I've gotten my device stuck in multiple fastboot loops and stuff their is always a way back.
Click to expand...
Click to collapse
Exactly which guide, at least 5 have been discussed lol what are the exact steps to take to go from stock be tmo to bootloader unlocked and rooted on latest stock rom.
I also don't mind sending you a monetary gift for your help. Thanks in advanced.

Outta said:
Exactly which guide, at least 5 have been discussed lol what are the exact steps to take to go from stock be tmo to bootloader unlocked and rooted on latest stock rom.
I also don't mind sending you a monetary gift for your help. Thanks in advanced.
Click to expand...
Click to collapse
This guide
https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947
Once you follow this you will be off TMobile stock and on global stock. Here you can choose to unlock bootloader or not. You don't need to root and install twrp to be on global rom. Just basically do the msm guide than. Update through the oxygen updater app to latest.

Kireyev said:
This guide
https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947
Once you follow this you will be off TMobile stock and on global stock. Here you can choose to unlock bootloader or not. You don't need to root and install twrp to be on global rom. Just basically do the msm guide than. Update through the oxygen updater app to latest.
Click to expand...
Click to collapse
just bricked my phone at this part:
3) Hold both volume buttons for 5 seconds then plug in the USB cable. OR In ADB type "adb reboot edl".
phone turned off and wont turn back on, any idea what tro do now?

Outta said:
just bricked my phone at this part:
3) Hold both volume buttons for 5 seconds then plug in the USB cable. OR In ADB type "adb reboot edl".
phone turned off and wont turn back on, any idea what tro do now?
Click to expand...
Click to collapse
Yep your in download mode, its not bricked no worries. just hold volume up and power button for awhile you well feel a vibrate and than it will reboot

Kireyev said:
If you follow the main guide on xda exactly you're going be fine. Once on global your essentially done because than you can flash a twrp through fastboot and install any rom, kernel you want. As well as magisk. The most important part is that msm guide. Now if you want to be more official get an unlock token and do it the regular way through fastboot with the unlock token. It took about a week in a half to get mine. But the msm guide works perfectly. Also I've gotten my device stuck in multiple fastboot loops and stuff their is always a way back.
Click to expand...
Click to collapse
Kireyev said:
Yep your in download mode, its not bricked no worries. just hold volume up and power button for awhile you well feel a vibrate and than it will reboot
Click to expand...
Click to collapse
Thanks again, saved, do you have any idea what my issue is, why isn't msm seeing my device? Adb does..

Outta said:
Thanks again, saved, do you have any idea what my issue is, why isn't msm seeing my device? Adb does..
Click to expand...
Click to collapse
strange all you really need do is hook it up to pc, enable usb debugging which u've done. type adb reboot edl, wait for it and have msm open and it should connect. My only thing to suggest would be try another cable or another port on the pc. sometimes i've also noticed fastboot can be odd for me and I have to reboot the computer for it to notice my phone . I'd suggest try those things. Did you check your system model and see if it was the 1915 model with the GM31CB?

dont know if you got it or not but heres link to the commands https://droidfeats.com/unlock-bootloader-oneplus-7-pro-t-mobile/