Database Info

tmobile version twrp & rooted

Hello fellas, I bought my TMobile Oneplus 7 pro on a payment plan yesterday. I already have it bootloader unlocked, rooted and twrp installed, volte works, Netflix works(480p). Running an international version OOS 9.5.11. My question is..... Since i already did all that, can I sim unlock it in the future, after 40 days, without having to revert back to stock tmobile?

As far as I know, you only have to wait 3 days to request a permanent sim unlock. @mobbdeep can do it for you with just the account holders last name and the phone number the OP7 Pro is currently on. You will need the T-Mobile "unlock" app so you can select "Permanent Unlock" in the app though, so you *may* need to temporarily reflash stock for that, but if you ask around, someone might be able to pull the apk from theirs for you to try on international.
Also out of curiosity, how well does T-Mobile service work on the international ROM? I've been thinking of converting mine and buying a dual sim tray since mine is unlocked.

agentfusion said:
As far as I know, you only have to wait 3 days to request a permanent sim unlock. @mobbdeep can do it for you with just the account holders last name and the phone number the OP7 Pro is currently on. You will need the T-Mobile "unlock" app so you can select "Permanent Unlock" in the app though, so you *may* need to temporarily reflash stock for that, but if you ask around, someone might be able to pull the apk from theirs for you to try on international.
Also out of curiosity, how well does T-Mobile service work on the international ROM? I've been thinking of converting mine and buying a dual sim tray since mine is unlocked.
Click to expand...
Click to collapse
If you're already on the international firmware and have stuff flashed, you will need to revert back to the stock T-Mobile firmware in order to truly unlock your SIM. If you try downloading the Device Unlock app via Play Store or APK, it will give an invalid network unlock reading. If you have a T-Mobile OnePlus 7 Pro, PM me your phone number and the last name of the account holder of your T-Mobile account and I can unlock your phone in seconds. You can then use the Device Unlock app to unlock your SIM then flash the international firmware if you'd like.. that is what I did myself.
Anyway, the international version firmware is good but there's no significant difference except it's used to unlock your device but not your SIM. I have SmurfKernel and xXx NoLimits ROM module installed and my device performance has increased greatly.

mobbdeep said:
If you have a T-Mobile OnePlus 7 Pro, PM me your phone number and the last name of the account holder of your T-Mobile account and I can unlock your phone in seconds.
Click to expand...
Click to collapse
PM sent man! ?

king3opobn said:
PM sent man! ?
Click to expand...
Click to collapse
I'll be doing the rest tomorrow. I'm busy the rest of today.

mobbdeep said:
I'll be doing the rest tomorrow. I'm busy the rest of today.
Click to expand...
Click to collapse
Ok, thanks

Working root instructions for Verizon Pixel 4 XL

VERIZON PIXEL 4 XL Root Instructions
NOTE: You must do this PRIOR to activating the phone with Verizon. On my phone once I activated it the OEM bootloader unlock switch became greyed out. (Edit - after rebooting once activated the OEM lock is available again).
Steps I took:
1. Turn on the phone, do not activate the SIM with the carrier.
2. Update to the latest firmware version.
3. Reboot.
4. Enable developer settings, turn on OEM unlock
5. Boot in fastboot mode, run fastboot flash unlock in a shell, reboot.
6. Set up and activate (mine required a chat with Verizon to activate, it wouldn’t activate through the app).
7. Reboot into fastboot, flash a boot.img that has been patched (magisk_patched.img). You can find instructions on this elsewhere.
8. Reboot.
9. Install magisk manager (canary builds). It will say it needs to download a zip to fully install. Allow.
10. Reboot. You’re now rooted.
11. Magisk manager and magisk install may want to upgrade, feel free.
Enjoy!
NOTE: There are several who this has worked for, and some who haven't been able to get it to work. Suggest reading the thread and providing info on phones that do and don't unlock for whatever reason.

Any idea if this would work with the Pixel 4? Thanks
Sent from my [device_name] using XDA-Developers Legacy app

Menardo said:
Any idea if this would work with the Pixel 4? Thanks
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I can't say for certain, but I think it would just the same. I don't know of any reason it wouldn't.

Im......just going to wait patiently for TWRP to be released for Pixel 4/XL then I will flash Magisk. Suck for now because I so use to adaway, and build.prop tether. The struggle is real.

mr.marcus said:
Im......just going to wait patiently for TWRP to be released for Pixel 4/XL then I will flash Magisk. Suck for now because I so use to adaway, and build.prop tether. The struggle is real.
Click to expand...
Click to collapse
Did they ever get TWRP working correctly on the 3xl??

mr.marcus said:
Im......just going to wait patiently for TWRP to be released for Pixel 4/XL then I will flash Magisk. Suck for now because I so use to adaway, and build.prop tether. The struggle is real.
Click to expand...
Click to collapse
TWRP isn't working on Android 10 currently. It'll need a lot of time to develop, as Google moved a lot of things related to recovery to new sections.
If you really want to root you should definitely patch the appropriate boot image (found here: https://developers.google.com/android/images) and follow the above mentioned steps.
Regarding AdAway: I'm using DNS66 since years. You can download an active the AdAway DNS serting to this app as well an AdBlock will work like a charm. No root needed.
Sent from my HTC U12+ using XDA Labs

Man I wish I saw this first. Well I hope another method comes along for those of us who activated already.

billydroid said:
Man I wish I saw this first. Well I hope another method comes along for those of us who activated already.
Click to expand...
Click to collapse
Well don't feel bad I tried it today before activating and it didn't work. It may wind up being a random occurrence with units that didn't have the IMEI's registered. That's probably why he had to contact Verizon to get the phone to work on their network.

CyberpodS2 said:
Did they ever get TWRP working correctly on the 3xl??
Click to expand...
Click to collapse
Not that I know of. I have been patching boot files for my 3 xl.

wolfu11 said:
Well don't feel bad I tried it today before activating and it didn't work. It may wind up being a random occurrence with units that didn't have the IMEI's registered. That's probably why he had to contact Verizon to get the phone to work on their network.
Click to expand...
Click to collapse
Perhaps. It knew it was a Verizon phone, it had a Verizon activation app. I was very careful to skip activation of any type at the store or when taking it home, so it might be that you need to tell Verizon that you'll activate it later to have the chance to unlock it.
Also, the OEM bootloader unlock has remained available after reboot. I think if it's unlocked in the way I describe it stays unlocked.

mr.marcus said:
Im......just going to wait patiently for TWRP to be released for Pixel 4/XL then I will flash Magisk. Suck for now because I so use to adaway, and build.prop tether. The struggle is real.
Click to expand...
Click to collapse
You might be waiting awhile.
https://www.androidpolice.com/2019/10/24/android-10-twrp-pixel-3-4/?amp

Nice!
madscribblerz said:
VERIZON PIXEL 4 XL Root Instructions
NOTE: You must do this PRIOR to activating the phone with Verizon. On my phone once I activated it the OEM bootloader unlock switch became greyed out. (Edit - after rebooting once activated the OEM lock is available again).
Steps I took:
1. Turn on the phone, do not activate the SIM with the carrier.
2. Update to the latest firmware version.
3. Reboot.
4. Enable developer settings, turn on OEM unlock
5. Boot in fastboot mode, run fastboot flash unlock in a shell, reboot.
6. Set up and activate (mine required a chat with Verizon to activate, it wouldn’t activate through the app).
7. Reboot into fastboot, flash a boot.img that has been patched (magisk_patched.img). You can find instructions on this elsewhere.
8. Reboot.
9. Install magisk manager (canary builds). It will say it needs to download a zip to fully install. Allow.
10. Reboot. You’re now rooted.
11. Magisk manager and magisk install may want to upgrade, feel free.
Enjoy!
Click to expand...
Click to collapse
I was able to do this a couple days ago. I have heard conflicting reports regarding whether this is possible or not but it certainly worked for me. I don't really have any interest in root access on pixel devices so I will just flash the Google store variant factory image (which I think is the one without the C4 in it's build number) and relock it. Maybe I'll play around with it later

Just did the patched boot image method using Magisk to root my 4XL.
Works perfectly with Magisk Canary, exactly the same process I used to do with my Pixel 3

Just an FYI - while Magisk canary builds were required when Android 10 was first released, the Magisk stable version 20 works on Android 10. So while you may use beta or canary builds if you want to, it is no longer a requirement. You can use the latest stable build and be fine.

madscribblerz said:
Perhaps. It knew it was a Verizon phone, it had a Verizon activation app. I was very careful to skip activation of any type at the store or when taking it home, so it might be that you need to tell Verizon that you'll activate it later to have the chance to unlock it.
Also, the OEM bootloader unlock has remained available after reboot. I think if it's unlocked in the way I describe it stays unlocked.
Click to expand...
Click to collapse
I brought it home sealed in the box .
Removed the sim card and powered into bootloader. From there went to recovery mode and did a factory reset. Set it up without signing into my Google account or WiFi and then went to developer options it was grayed out stating"locked carrier device". Did a factory reset as normal and set it up without signing in then took the updates from WiFi. Rebooted and checked developer options still grayed out with same message. I have yet to put a Verizon sim it but did try a different carrier but still no luck. I did have luck with this procedure with one of my Verizon 2xl so I'm pretty sure I did it right. But anyway I didn't see the app you speak of. Where is it located? I only bought this phone because of the discount Verizon gave. I'll be selling it but was curious if it could be unlocked.
Did you unlock your bootloader or just flip the toggle?

wolfu11 said:
I brought it home sealed in the box .
Removed the sim card and powered into bootloader. From there went to recovery mode and did a factory reset. Set it up without signing into my Google account or WiFi and then went to developer options it was grayed out stating"locked carrier device". Did a factory reset as normal and set it up without signing in then took the updates from WiFi. Rebooted and checked developer options still grayed out with same message. I have yet to put a Verizon sim it but did try a different carrier but still no luck. I did have luck with this procedure with one of my Verizon 2xl so I'm pretty sure I did it right. But anyway I didn't see the app you speak of. Where is it located? I only bought this phone because of the discount Verizon gave. I'll be selling it but was curious if it could be unlocked.
Did you unlock your bootloader or just flip the toggle?
Click to expand...
Click to collapse
Both. I'm rooted using a patched magisk boot image, which I couldn't have flashed otherwise.
There does seem to be some mystery sauce here though. I didn't do anything with my SIM, I left it as it was. The app was carrier setup (in notifications prompting to activate) which I didn't launch until after having turned on the toggle, and having run fastboot flashing unlock, then fastboot flash boot magisk_patched.img. I did update to the .C4 release beforehand though, but didn't think that in any way related.
Maybe it was something to do with misconfiguration on the Verizon side - but that seems pretty unlikely given that they didn't even try to activate it and said when I got home to do so - so like you, I came home with it sealed in the box.
Maybe someone else can shed some light - as it seems we're about 50/50 on the unlocks. I bought mine retail at a verizon store. I essentially got it free, as I traded in a Galaxy 5 for $450, which pays out $18.50 a month, and cancelled Fi, which covers the phone's monthly with money coming in.

Damn my device didn't unlock

I wonder if this will work with Spectrum/Charter Wireless since they use Verizon's towers....If anyone knows or has any thoughts I would appreciate it.

wolfu11 said:
I brought it home sealed in the box .
Removed the sim card and powered into bootloader. From there went to recovery mode and did a factory reset. Set it up without signing into my Google account or WiFi and then went to developer options it was grayed out stating"locked carrier device". Did a factory reset as normal and set it up without signing in then took the updates from WiFi. Rebooted and checked developer options still grayed out with same message. I have yet to put a Verizon sim it but did try a different carrier but still no luck. I did have luck with this procedure with one of my Verizon 2xl so I'm pretty sure I did it right. But anyway I didn't see the app you speak of. Where is it located? I only bought this phone because of the discount Verizon gave. I'll be selling it but was curious if it could be unlocked.
Did you unlock your bootloader or just flip the toggle?
Click to expand...
Click to collapse
Did almost the same procedure with my dad's 64 GB black XL. I didn't go into bootloader but I took out the sim, set it up without signing in, and it gave me a greyed out message to turn on WiFi before I could do anything. Tried a factory reset, got the same message. Did another factory reset, set it up without any account but signed into my Wifi network, and it gave me the greyed out message that I can't OEM unlock on carrier locked devices.
When I get my phone I'm thinking about trying a quick WiFi toggle going back to developer settings and trying to unlock before it can communicate with Verizon. I doubt it'll work, but it's worth a shot.
madscribblerz said:
Both. I'm rooted using a patched magisk boot image, which I couldn't have flashed otherwise.
There does seem to be some mystery sauce here though. I didn't do anything with my SIM, I left it as it was. The app was carrier setup (in notifications prompting to activate) which I didn't launch until after having turned on the toggle, and having run fastboot flashing unlock, then fastboot flash boot magisk_patched.img. I did update to the .C4 release beforehand though, but didn't think that in any way related.
Maybe it was something to do with misconfiguration on the Verizon side - but that seems pretty unlikely given that they didn't even try to activate it and said when I got home to do so - so like you, I came home with it sealed in the box.
Maybe someone else can shed some light - as it seems we're about 50/50 on the unlocks. I bought mine retail at a verizon store. I essentially got it free, as I traded in a Galaxy 5 for $450, which pays out $18.50 a month, and cancelled Fi, which covers the phone's monthly with money coming in.
Click to expand...
Click to collapse
I'm a bit confused by the last part, so are you on a Verizon monthly payment plan?

bosox284 said:
Did almost the same procedure with my dad's 64 GB black XL. I didn't go into bootloader but I took out the sim, set it up without signing in, and it gave me a greyed out message to turn on WiFi before I could do anything. Tried a factory reset, got the same message. Did another factory reset, set it up without any account but signed into my Wifi network, and it gave me the greyed out message that I can't OEM unlock on carrier locked devices.
When I get my phone I'm thinking about trying a quick WiFi toggle going back to developer settings and trying to unlock before it can communicate with Verizon. I doubt it'll work, but it's worth a shot.
I'm a bit confused by the last part, so are you on a Verizon monthly payment plan?
Click to expand...
Click to collapse
I am on a 24 month payment plan, but those payments are negated by the trade in and extra money I save having only verizon without Fi.

Converted TMobile to International Firmware Question

If I have a oneplus 7 pro (tmobile, flashed to international stock 9) am I able to use the latest international firmware flasher to wipe the phone and go straight to 10.3?
this link https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I'm on 9.5.11 GM21AA and I've had the upgrade nag screen showing for what feels like forever now and I guess im ready to update, but I really like clean upgrades instead of just flashing ontop of whats already there to update.

HaiKaiDo said:
If I have a oneplus 7 pro (tmobile, flashed to international stock 9) am I able to use the latest international firmware flasher to wipe the phone and go straight to 10.3?
this link https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I'm on 9.5.11 GM21AA and I've had the upgrade nag screen showing for what feels like forever now and I guess im ready to update, but I really like clean upgrades instead of just flashing ontop of whats already there to update.
Click to expand...
Click to collapse
I think you have to use beta 3 to unlock the phone (oem unlock), unless that doesn't matter to you

preference said:
I think you have to use beta 3 to unlock the phone (oem unlock), unless that doesn't matter to you
Click to expand...
Click to collapse
Dumb question. Whats beta 3? and does it matter that I already have the device OEM unlocked? ...or wait..that gets re-locked when you use these tools doesnt it?

HaiKaiDo said:
Dumb question. Whats beta 3? and does it matter that I already have the device OEM unlocked? ...or wait..that gets re-locked when you use these tools doesnt it?
Click to expand...
Click to collapse
Read this article
https://www.xda-developers.com/t-mobile-oneplus-7-pro-root-tutorial/amp/

Need to sim unlock it. Bootloader unlock it. Flash international firmware via fastboot. I have the same phone and the 7t. Same process when it's T-Mobile.

travis82 said:
Need to sim unlock it. Bootloader unlock it. Flash international firmware via fastboot. I have the same phone and the 7t. Same process when it's T-Mobile.
Click to expand...
Click to collapse
When you changed from T-Mobile to international varient, did it Relock the Sim again or it still remained unlocked
Thanks in advance

[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/

No SIM Card Detected after installing LineageOS and rooting

Howdy all,
I'll try to keep things brief but informative.
Yesterday I got the unlock bin for my T-Mobile Oneplus 7 Pro. I unlocked it, flashed LineageOS (latest 17.1), Magisk (19.04 but then updated to latest after install), DM-Verity, and TWRP (unified Q version).
I have installed Nethunter, F-Droid, and some other basic apps.
I just got a new SIM Card from T-Mobile and activated it last night, however it shows the same as the empty SIM slot (which my phone doesn't have a physical second slot) and on the lock screen at the top left rotates between saying: "No SIM card" "No SIM card - T-Mobile" "No SIM card - No service". In the phone the top right does not show any bars, x'ed out or otherwise, however one time after taking it out, googling, then putting it back in it sis appear x'ed out until reboot.
I cannot send texts as it says no preferred SIM card selected, and I cannot make calls due to a lack of service; however, I can receive texts and calls and even answer calls and speak to the calling party just fine.
I was getting nothing, then I saw where someone received a text and it fixed it for them, so I texted myself, got a backlog of texts, but nothing else came of that.
I have no idea what to do from here and only vauge idea of why it may be like this but no understanding of it.
I found this reddit post seeming to detail the issue, but I do not know if it applies to me (presumably does) and I do not understand any of the information in the post, nor do I know what to do with this information:
reddit.com/r /oneplus /comments /gb5jlk /factory_reset_no_sim_card_detected_oneplus_7_pro /
(sorry for the spaces, can't post outside links until after I've posted 10 posts)
and with that I'm all out of idea and knowledge. My background is in Offensive Security, but I know very little about SIM Cards and smart phones so all help is greatly appreciated!

Is the device sim unlocked?

wired57 said:
Is the device sim unlocked?
Click to expand...
Click to collapse
I didn't do it so I'm going to assume it is not. I've only unlocked the bootloader (obviously). How would I go about unlocking the SIM?
Also, the original carrier was T-Mobile and the SIM is also T-Mobile, I assumed this would be ok but is there an issue since I didn't unlock it yet I installed custom stuffs - or what would be causing an issue by not unlocking it? (just trying to learn more )

MagicCooki3 said:
I didn't do it so I'm going to assume it is not. I've only unlocked the bootloader (obviously). How would I go about unlocking the SIM?
Also, the original carrier was T-Mobile and the SIM is also T-Mobile, I assumed this would be ok but is there an issue since I didn't unlock it yet I installed custom stuffs - or what would be causing an issue by not unlocking it? (just trying to learn more )
Click to expand...
Click to collapse
How did you root?
Did you grab a patched boot image or did you boot with the TWRP image and install Magisk yourself?
Grabbing the wrong image is the number one thing that causes WiFi and SIM issues.

tech_head said:
How did you root?
Did you grab a patched boot image or did you boot with the TWRP image and install Magisk yourself?
Grabbing the wrong image is the number one thing that causes WiFi and SIM issues.
Click to expand...
Click to collapse
I used this method (copied from irsa mintTM in a YouTube comment)
"REBOOT TWRP
FORMAT DATA (If you are encryted) your internal memory will be lost!!!
REBOOT TWRP
WIPE DATA & CACHE
Flash Rom
Flash TWRP Installer
REBOOT TWRP
WIPE DATA & CACHE
Flash Rom again
Flash TWRP again
REBOOT TWRP
Flash Magisk 19.4!!!! <----This version
Flash DM Verity zip file <--- Always last file before system reboot
REBOOT SYSTEM AND ENJOY"

Gotta unlock for custom ROMs. Flash back to TMobile firmware do a sim unlock, then you can flash back.

wired57 said:
Gotta unlock for custom ROMs. Flash back to TMobile firmware do a sim unlock, then you can flash back.
Click to expand...
Click to collapse
Oh ok, gotcha! I'll give that a go using this video and method and I'll update you if that fixed everything.
youtube .com/ watch?v=4CeCM88ecv4
Thank you so much!!

wired57 said:
Gotta unlock for custom ROMs. Flash back to TMobile firmware do a sim unlock, then you can flash back.
Click to expand...
Click to collapse
I got the T-Mobile stock everything back and everything locked back down, but my SIM card is showing now service now - the same no sim message as was on LineageOS, not even receiving texts now.
I'll re-seat and mess with it when I get some more time.

wired57 said:
Gotta unlock for custom ROMs. Flash back to TMobile firmware do a sim unlock, then you can flash back.
Click to expand...
Click to collapse
Also, I went to the unlock app and it says it's fully unlocked already and can be used with any carrier...

If you didn't use the msm tool to get you back to the T-Mobile firmware, then you probably aren't on T-Mobile firmware. I had the same issue trying to get lineage to work, and was able to get back to stock and have data.
Since you probably don't have the bootloader unlock code, you need to convert to international firmware, and fully update to at least 10.3.2 before you flash lineage. If you don't, you won't have service.
Sent from my GM1915 using Tapatalk

mjdavis871 said:
If you didn't use the msm tool to get you back to the T-Mobile firmware, then you probably aren't on T-Mobile firmware. I had the same issue trying to get lineage to work, and was able to get back to stock and have data.
Since you probably don't have the bootloader unlock code, you need to convert to international firmware, and fully update to at least 10.3.2 before you flash lineage. If you don't, you won't have service.
Sent from my GM1915 using Tapatalk
Click to expand...
Click to collapse
I did use the MSM tool, it's locked, has the T-Mobile boot animation and everything.
I do have the unlock file & code, I had to wait a week to get it.