Database Users

Device is altered

I didn't unlock my bootloader and I'm not rooted. My bootloader is locked. But Google Pay seems to think my device is modified. I did install Android 10 on my TMobile variant but it was working fine when I had the Android 9 open beta. Disney + and Netflix aren't in the app store so Google Play thinks I'm altered too. Help?

bigmikey307 said:
I didn't unlock my bootloader and I'm not rooted. My bootloader is locked. But Google Pay seems to think my device is modified. I did install Android 10 on my TMobile variant but it was working fine when I had the Android 9 open beta. Disney + and Netflix aren't in the app store so Google Play thinks I'm altered too. Help?
Click to expand...
Click to collapse
Seems to be working just like everyone else's T-Mobile Android 10 OP6T. This is a known issues on our devices.

bigmikey307 said:
I didn't unlock my bootloader and I'm not rooted. My bootloader is locked. But Google Pay seems to think my device is modified. I did install Android 10 on my TMobile variant but it was working fine when I had the Android 9 open beta. Disney + and Netflix aren't in the app store so Google Play thinks I'm altered too. Help?
Click to expand...
Click to collapse
It's a bug, you're going to have to wait until it's patched, no ETA from OnePlus yet.
Sent from my ONEPLUS A6013 using Tapatalk

I converted my T-Mobile phone using the MSM tool (no root) a while ago and never had trouble with Google Pay. It stopped working only after the latest update (Android 10.0). I hope OP will fix this in their next update.

Yeah, we all do. I have not been able to get around it. Tried the magisk module "setprops" but that didin't work. Anyone find a way around it yet?

Scott said:
Yeah, we all do. I have not been able to get around it. Tried the magisk module "setprops" but that didin't work. Anyone find a way around it yet?
Click to expand...
Click to collapse
You mean magiskhide props ?...
Ans set 6T pie fingerprint?...

cultofluna said:
You mean magiskhide props ?...
Ans set 6T pie fingerprint?...
Click to expand...
Click to collapse
The latest magiskhide props module has a valid 6T A10 fingerprint, I'm using it and my device is certified.

Open Beta 2 T-Mobile

Has anyone tried to flash the new Beta update to the OnePlus 6T TMobile version? Does it still give the same error "Build Version does not match Hardware version"?

bigmikey307 said:
Has anyone tried to flash the new Beta update to the OnePlus 6T TMobile version? Does it still give the same error "Build Version does not match Hardware version"?
Click to expand...
Click to collapse
I just downloaded and installed the open beta 2 and it's great! I'm going to give it a week and "test the engine and tires." I still have my Pie firmware, just in case.
NOTE: I installed using the local update method. I was rooted also with pie.

Main OP question was if you flash android 10 via zip and tried flashing beta on top to see if it works like it did on android 9. Please let me know if anyone tried this as well. Thank you in advance.

bigmikey307 said:
Has anyone tried to flash the new Beta update to the OnePlus 6T TMobile version? Does it still give the same error "Build Version does not match Hardware version"?
Click to expand...
Click to collapse
No 'build version does not match hardware version' error when flashing the new beta to TMO converted one plus 6t. I used TWRP 3.3.1.28 and all is good.

We still don't have the "reserve" partition though. OnePlus fonts will be missing and show up as italic fonts. A few apps are also gone but can be installed from play store. You wont pass Safety net so you will miss out on Netflix, etc.
No F/C's. Not sure on battery yet.
Everything else does seem good! I am enjoying it!

Scott said:
We still don't have the "reserve" partition though. OnePlus fonts will be missing and show up as italic fonts. A few apps are also gone but can be installed from play store. You wont pass Safety net so you will miss out on Netflix, etc.
No F/C's. Not sure on battery yet.
Everything else does seem good! I am enjoying it!
Click to expand...
Click to collapse
You can use the reserve partition magisk module...

justforgot said:
Main OP question was if you flash android 10 via zip and tried flashing beta on top to see if it works like it did on android 9. Please let me know if anyone tried this as well. Thank you in advance.
Click to expand...
Click to collapse
I used patched MSM tool to get TMobile variant to international ROM without unlocking bootloader and then I local upgraded to Android 10 stable, then local upgraded to OB 2 and all is well!

So I'm on Android 10 Stable with bootloader unlocked. What happens if I relock bootloader? Will I go into bootloop on restart, and will it get rid of the warning on restart, or do I need to do what @bigmikey307 did?
Update : I did the above but didn't go to beta 2

PapaMag said:
So I'm on Android 10 Stable with bootloader unlocked. What happens if I relock bootloader? Will I go into bootloop on restart, and will it get rid of the warning on restart, or do I need to do what @bigmikey307 did?
Update : I did the above but didn't go to beta 2
Click to expand...
Click to collapse
didn't understood what you meant about "didn't go to beta 2"...
for beta you need to flash via local update since you're on the official update yet. link is on the beta thread or on the Oxygen Updater app from playstore

TJSteveMX said:
didn't understood what you meant about "didn't go to beta 2"...
for beta you need to flash via local update since you're on the official update yet. link is on the beta thread or on the Oxygen Updater app from playstore
Click to expand...
Click to collapse
I just meant I stopped at 10.0 and didn't local upgrade to beta yet

Any word on the Play Protect Certification issue on T-Mo devices? I've been getting by without it on the Stable release, but I'll definitely go Beta of this update resolves the issue.

taylor85345 said:
Any word on the Play Protect Certification issue on T-Mo devices? I've been getting by without it on the Stable release, but I'll definitely go Beta of this update resolves the issue.
Click to expand...
Click to collapse
Nope, not certified. Someone posted some links in the Official Stable thread with instructions on how to do it using root and some magisk modules.

taylor85345 said:
Any word on the Play Protect Certification issue on T-Mo devices? I've been getting by without it on the Stable release, but I'll definitely go Beta of this update resolves the issue.
Click to expand...
Click to collapse
So like @Scott Mentioned, it requires root to pass at the moment. The Magisk mod is called Magiskhide props config and it works perfectly well as a workaround. Good luck!
Sent from my OnePlus6T using XDA Labs

I'm probably overlooking something obvious but I have no idea what it is.
Here's the story; I have a T-Mobile OP6t converted to International.
Flashed the update to OB31 (Open Beta 2).
I have Magisk and Titanium Backup installed, both with root access allowed.
However, I'm unable to get TB to actually uninstall some of the system apps I don't want.
Also, I can't copy and paste (via Solid Explorer) my edited HOSTS file to block ads.
What am I missing?

Scott said:
We still don't have the "reserve" partition though. OnePlus fonts will be missing and show up as italic fonts. A few apps are also gone but can be installed from play store. You wont pass Safety net so you will miss out on Netflix, etc.
No F/C's. Not sure on battery yet.
Everything else does seem good! I am enjoying it!
Click to expand...
Click to collapse
What is the reserve partition? And do I need it/want it?

cultofluna said:
You can use the reserve partition magisk module...
Click to expand...
Click to collapse
Do you have a link?

Scott said:
Do you have a link?
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=1899786940962618515

Scott said:
We still don't have the "reserve" partition though. OnePlus fonts will be missing and show up as italic fonts. A few apps are also gone but can be installed from play store. You wont pass Safety net so you will miss out on Netflix, etc.
No F/C's. Not sure on battery yet.
Everything else does seem good! I am enjoying it![/QUOTE @Scott , which apps are you referring to?
Sent from my ONEPLUS 6T using Tapatalk Pro.
If I've helped you out, please tap the thanks button.
Click to expand...
Click to collapse

xRogerxC said:
@Scott , which apps are you referring to?
Sent from my ONEPLUS 6T using Tapatalk Pro.
If I've helped you out, please tap the thanks button.
Click to expand...
Click to collapse
The OP Weather app for instance, the OP square and round icon packs, e few more that I dont recall. All of them could be downloaded from the play store. You only need the font fox magisk module referenced earlier in this thread. You wont notice these missing apps on a dirty install but you will see it on a clean install or factory reset.

Reinstalling the ROM ZIP via in-built updater fixes the issue. Done it multiple times.

OnePlus 6t T-Mobile unlocked converted oxygen 10.3

Hi, I have a T-Mobile version of OnePlus 6t and it is unlocked. I converted to global room but Can I update to oxyen os 10.3?
I saw posts that T-Mobile version needs to wait T-Mobiles OTA but I am not sure this applied to post-unlocked one.

Ruin2580 said:
Hi, I have a T-Mobile version of OnePlus 6t and it is unlocked. I converted to global room but Can I update to oxyen os 10.3?
I saw posts that T-Mobile version needs to wait T-Mobiles OTA but I am not sure this applied to post-unlocked one.
Click to expand...
Click to collapse
I have a converted TMobile op6t and upgraded to 10.1 then just local upgraded to 10.3 without issues but just last night I flashed the open beta 3. Your fine to upgrade.

Ruin2580 said:
Hi, I have a T-Mobile version of OnePlus 6t and it is unlocked. I converted to global room but Can I update to oxyen os 10.3?
I saw posts that T-Mobile version needs to wait T-Mobiles OTA but I am not sure this applied to post-unlocked one.
Click to expand...
Click to collapse
I went from 9.0.17 to 10.3 with a local upgrade - all seems to work fine. Except for Google certification that will not be available till TMobile release A10 and certify the device. So some applications will not show in Play Store (Like Netflix) and GPay will not work.

polzovotel said:
I went from 9.0.17 to 10.3 with a local upgrade - all seems to work fine. Except for Google certification that will not be available till TMobile release A10 and certify the device. So some applications will not show in Play Store (Like Netflix) and GPay will not work.
Click to expand...
Click to collapse
Question, I have the apk saved and I install say Netflix apk onto android 10, would I be able to use the app or would it be unable to install/work?

ozzmanj1 said:
Question, I have the apk saved and I install say Netflix apk onto android 10, would I be able to use the app or would it be unable to install/work?
Click to expand...
Click to collapse
Yes, you can. You better install Netflix BEFORE upgrading. The reason is Netflix deployment is not one APK - you will need to use 3d party to deploy Netflix apk.

polzovotel said:
I went from 9.0.17 to 10.3 with a local upgrade - all seems to work fine. Except for Google certification that will not be available till TMobile release A10 and certify the device. So some applications will not show in Play Store (Like Netflix) and GPay will not work.
Click to expand...
Click to collapse
Did you install safety net on magisk? My playstore is certified on 6t, 10.3, rooted etc

bigjailerman said:
Did you install safety net on magisk? My playstore is certified on 6t, 10.3, rooted etc
Click to expand...
Click to collapse
I do not have root
Sent from my [device_name] using XDA-Developers Legacy app

beany23 said:
I have a converted TMobile op6t and upgraded to 10.1 then just local upgraded to 10.3 without issues but just last night I flashed the open beta 3. Your fine to upgrade.
Click to expand...
Click to collapse
Did you use the incremental or full package? The incremental fails as soon as you click it. I am giving the full pkg a try.

vibraniumdroid said:
Did you use the incremental or full package? The incremental fails as soon as you click it. I am giving the full pkg a try.
Click to expand...
Click to collapse
For those of us on converted TMO devices, you can only use full packages. The incremental will fail Everytime.

What steps did you use to root? Did you do it after installing A10?
---------- Post added at 03:34 PM ---------- Previous post was at 03:33 PM ----------
bigjailerman said:
Did you install safety net on magisk? My playstore is certified on 6t, 10.3, rooted etc
Click to expand...
Click to collapse

polzovotel said:
Yes, you can. You better install Netflix BEFORE upgrading. The reason is Netflix deployment is not one APK - you will need to use 3d party to deploy Netflix apk.
Click to expand...
Click to collapse
May I ask, when you went from 9.0.17 to 10.3, did you use Oxygen updater? I have converted twice now from A9 to A10 and both times had to msmtool back to A9.17 due to various issues. I would like to update to A10, but don't want to have an issue and have to re-wipe everything and go through the ordeal of unlocking bootloader again as well as copying all my files back to my phone and setting things back up.
Did you have any issues with your upgrade or was it a seemless experience? I realize there is Netflix and google play (I do use Netflix but no Gpay).
If it worked good for you I may consider going to 10.0.3 from 9.0.17 in the next day or so. I realize the upgrading is all subjective, just curious

ozzmanj1 said:
May I ask, when you went from 9.0.17 to 10.3, did you use Oxygen updater? I have converted twice now from A9 to A10 and both times had to msmtool back to A9.17 due to various issues. I would like to update to A10, but don't want to have an issue and have to re-wipe everything and go through the ordeal of unlocking bootloader again as well as copying all my files back to my phone and setting things back up.
Did you have any issues with your upgrade or was it a seemless experience? I realize there is Netflix and google play (I do use Netflix but no Gpay).
If it worked good for you I may consider going to 10.0.3 from 9.0.17 in the next day or so. I realize the upgrading is all subjective, just curious
Click to expand...
Click to collapse
Worked well for me using oxygen updater and local upgrade option. No wipe or data loss for me. I am not root and my bootloader is locked. I did not see any issues with a10 apart Google certification that will be fixed when TMobile release a10 for this device
Sent from my [device_name] using XDA-Developers Legacy app

polzovotel said:
Worked well for me using oxygen updater and local upgrade option. No wipe or data loss for me. I am not root and my bootloader is locked. I did not see any issues with a10 apart Google certification that will be fixed when TMobile release a10 for this device
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Gotcha, perhaps I will wait then. I am unlocked bootloader with magisk and twrp. Thanks for the reply.

ozzmanj1 said:
May I ask, when you went from 9.0.17 to 10.3, did you use Oxygen updater? I have converted twice now from A9 to A10 and both times had to msmtool back to A9.17 due to various issues. I would like to update to A10, but don't want to have an issue and have to re-wipe everything and go through the ordeal of unlocking bootloader again as well as copying all my files back to my phone and setting things back up.
Did you have any issues with your upgrade or was it a seemless experience? I realize there is Netflix and google play (I do use Netflix but no Gpay).
If it worked good for you I may consider going to 10.0.3 from 9.0.17 in the next day or so. I realize the upgrading is all subjective, just curious
Click to expand...
Click to collapse
I just updated to the latest 10.0.3 last night. There were no major hiccups and I followed the ultimate guide method 2. There were some Magisk modules that were incompatible such as (OOS Doze) and my sms/MMS with Google messenger stopped working. The messagenr actually resolved itself and is now working and my Netflix works along with Disney plus. I am using the module safetypass to pass safetnet

LuCkyCn said:
I just updated to the latest 10.0.3 last night. There were no major hiccups and I followed the ultimate guide method 2. There were some Magisk modules that were incompatible such as (OOS Doze) and my sms/MMS with Google messenger stopped working. The messagenr actually resolved itself and is now working and my Netflix works along with Disney plus. I am using the module safetypass to pass safetnet
Click to expand...
Click to collapse
Oh, good to know. Thank you. I will look into that ultimate guide method 2. I appreciate the feedback.
Edit: Did you do local upgrade or upgrade from the oxygen update app directly?

ozzmanj1 said:
Oh, good to know. Thank you. I will look into that ultimate guide method 2. I appreciate the feedback.
Edit: Did you do local upgrade or upgrade from the oxygen update app directly?
Click to expand...
Click to collapse
Local update. I didn't lose any data or files. The process was pretty straight forward and i went straight to 10.0.3 too.

Did you root before installing 10.3?

jestyr8 said:
For those of us on converted TMO devices, you can only use full packages. The incremental will fail Everytime.
Click to expand...
Click to collapse
Not true I went from 9. 17 to 10.01 and Incremental to 10.3. With no issues. Your mileage may vary.

I'm on 9.0.17 converted TMobile to international, can I take the 10.3.0 update , I'm understanding I'll most likely lose Google pay which I don't use anything else?

I went from 9.17 converted to International to 10.3, then rooted.
Yes you will lose Google Pay and Play Store Certification.

Stock at&t device certified fingerprint

I'm on an lg-v350, originally from at&t but it is currently unlocked, rooted with magisk and running Android 9. My device has been "ctsprofile:failed" for a awhile now. Not the biggest deal but if anyone has a certified device fingerprint I'd be very appreciative.

You can get it to pass by installing a couple modules in Magisk. The first one is busybox as a requirement. The second on is MagiskHideProps; it does the work. Use it to change the fingerprint to a Pixel 3 on Pie. I do not know the drawbacks of doing this, but you will pass the ctsprofile check and be able to use GPay.
Meatmassuse said:
I'm on an lg-v350, originally from at&t but it is currently unlocked, rooted with magisk and running Android 9. My device has been "ctsprofile:failed" for a awhile now. Not the biggest deal but if anyone has a certified device fingerprint I'd be very appreciative.
Click to expand...
Click to collapse

cmrntnnr said:
You can get it to pass by installing a couple modules in Magisk. The first one is busybox as a requirement. The second on is MagiskHideProps; it does the work. Use it to change the fingerprint to a Pixel 3 on Pie. I do not know the drawbacks of doing this, but you will pass the ctsprofile check and be able to use GPay.
Click to expand...
Click to collapse
Yea, that's the eventual option I came too as well. Haven't noticed any ill effects yet but who knows if it'll work forever. One amusing side effect was a free 100gbs on google drive when I opened the app. Some pixel promo ot said, haha.

Meatmassuse said:
I'm on an lg-v350, originally from at&t but it is currently unlocked, rooted with magisk and running Android 9. My device has been "ctsprofile:failed" for a awhile now. Not the biggest deal but if anyone has a certified device fingerprint I'd be very appreciative.
Click to expand...
Click to collapse
From stock AT&T V35 with latest PIE and security update. These should work with the Magisk props module to pass CTSProfie. I haven't cross-flashed, unlocked or rooted mine due to concerns with widevine L1 and the lack of an AT&T stock backup ROM.
[ro.build.fingerprint]: [lge/judyp_lao_com/judyp:9/PKQ1.181105.001/200341345c8c9.FGN:user/release-keys]
[ro.build.version.security_patch]: [2020-02-01]
Config attached (remove txt extension and place in sdcard directory, then choose custom fingerprint in props module).

rlw6534 said:
From stock AT&T V35 with latest PIE and security update. These should work with the Magisk props module to pass CTSProfie. I haven't cross-flashed, unlocked or rooted mine due to concerns with widevine L1 and the lack of an AT&T stock backup ROM.
[ro.build.fingerprint]: [lge/judyp_lao_com/judyp:9/PKQ1.181105.001/200341345c8c9.FGN:user/release-keys]
[ro.build.version.security_patch]: [2020-02-01]
Config attached (remove txt extension and place in sdcard directory, then choose custom fingerprint in props module).
Click to expand...
Click to collapse
I want you too know that I'd divorce my wife for you sir haha. For real though, thanks bruv.

Meatmassuse said:
I want you too know that I'd divorce my wife for you sir haha. For real though, thanks bruv.
Click to expand...
Click to collapse
Glad to help. I learned a while back to back up my props before hacking on my android devices...

Does anyone have the Oreo fingerprint for AT&T V35? I would very, very much appreciate it. I have cross-flashed to Oreo ULM and can't get CTSprofile to pass using the Pie version.
Edit:
Nevermind. Fixed it by upgrading to ULM Pie and flashing FTM, modemst1 and modemst2 from AT&T.

10.0.35 update

https://www.t-mobile.com/support/de...-7t-pro-5g/software-updates-oneplus-7t-pro-5g
I cannot find the download link from oneplus so I can get the system and boot images to update my rooted phone. I hate Oneplus....they do not list these links anyplace. Can someone please post. Thank you.

I think this update brings the 5G band n41 to our device if the new band specs on T-Mobile's listing for our phone is anything to go by.

dstryrwiz said:
I think this update brings the 5G band n41 to our device if the new band specs on T-Mobile's listing for our phone is anything to go by.
Click to expand...
Click to collapse
N41 has been enabled on this phone since .31. This update might bring the N66/N2 which we had pass through the FCC a few months ago.

Has anyone got it yet ? Mine still not pulling it up

LT1UltraZ said:
Has anyone got it yet ? Mine still not pulling it up
Click to expand...
Click to collapse
Mines haven't either

I added the reserve.img back as directed but mine is not pulling it up either. This is why I hate oneplus. With a pixel, you got the link, downloaded it, and flashed it. They are never posting anything on their website. Matter of fact, our model does not even show up on the support page.

photolarry said:
I added the reserve.img back as directed but mine is not pulling it up either. This is why I hate oneplus. With a pixel, you got the link, downloaded it, and flashed it. They are never posting anything on their website. Matter of fact, our model does not even show up on the support page.
Click to expand...
Click to collapse
Your device (T-Mo variant) lacks local update feature in Settings->System->System Updates like 6T, 7 Pro and 7T, 8 T-Mobile and 8 Verizon editions, hence why it isn't listed on support website since you can't officially flash builds by yourself.

Some_Random_Username said:
Your device (T-Mo variant) lacks local update feature in Settings->System->System Updates like 6T, 7 Pro and 7T, 8 T-Mobile and 8 Verizon editions, hence why it isn't listed on support website since you can't officially flash builds by yourself.
Click to expand...
Click to collapse
Ummmm I have a rooted device and can flash it manually as I have done on many other oneplus phones. The OOS files are just not published with links sadly.
These links are listed for the non 5G phone : https://forum.xda-developers.com/7t-pro/how-to/oneplus-7t-pro-repo-oxygen-os-builds-t4003455
Sadly we do not have a dev that lists them for our phone. I am trying to get more info.

photolarry said:
Ummmm I have a rooted device and can flash it manually as I have done on many other oneplus phones.
Click to expand...
Click to collapse
No you can't? There is no such local update screen with devices bought from T-Mobile.
photolarry said:
The OOS files are just not published with links sadly.
These links are listed for the non 5G phone : https://forum.xda-developers.com/7t-pro/how-to/oneplus-7t-pro-repo-oxygen-os-builds-t4003455
Sadly we do not have a dev that lists them for our phone. I am trying to get more info.
Click to expand...
Click to collapse
Full zips are just not provided by OnePlus even by OTA for carrier devices (exception being Android major updates eg when Android 11 will be released), only incremental ones are provided. More info at https://www.xda-developers.com/dont...s-7t-pro-mclaren-bootloader-oxygenos-updates/
As a sidenote I'm the OP of the thread you just linked.

Some_Random_Username said:
No you can't? There is no such local update screen with devices bought from T-Mobile.
Full zips are just not provided by OnePlus even by OTA for carrier devices (exception being Android major updates eg when Android 11 will be released), only incremental ones are provided. More info at https://www.xda-developers.com/dont...s-7t-pro-mclaren-bootloader-oxygenos-updates/
As a sidenote I'm the OP of the thread you just linked.
Click to expand...
Click to collapse
I have a rooted phone and want to get this update file. It is not that complex. If I was on any other oneplus phone that was not specialized for 5G, I could get the info needed. I dont know why you think this is hard to do? I gave you a few examples from the other forum

photolarry said:
I have a rooted phone and want to get this update file. It is not that complex. If I was on any other oneplus phone that was not specialized for 5G, I could get the info needed. I dont know why you think this is hard to do? I gave you a few examples from the other forum
Click to expand...
Click to collapse
Are you even reading his responses? Those examples came from him.
Even if you had the OTA URL and file captured, you can't flash it. It'll brick your phone unless it goes through the update menu. They are incremental updates that check file integrity. They are not full updates. You cannot flash updates on this phone. Period.
If you have an MSM, that's different. But we don't have that either. Right now, all we can do is wait.

I am rooted
Some_Random_Username said:
Your device (T-Mo variant) lacks local update feature in Settings->System->System Updates like 6T, 7 Pro and 7T, 8 T-Mobile and 8 Verizon editions, hence why it isn't listed on support website since you can't officially flash builds by yourself.
Click to expand...
Click to collapse
I can apply it via fastboot. And I have done so many times. For the 7 pro for example. This whole wrinkle with 5G and reserve.img really sucks. I am sorry but this is very frustrating. I want simply to be rooted for many reasons and without even flashing custom ROM....and now it looks like being rooted is causing more harm than good. I guess I get nothing from being rooted. I am contemplating just using MSM to go backwards and unroot.

photolarry said:
I have a rooted phone and want to get this update file. It is not that complex. If I was on any other oneplus phone that was not specialized for 5G, I could get the info needed. I dont know why you think this is hard to do? I gave you a few examples from the other forum
Click to expand...
Click to collapse
From the very own article written by XDA Portal I linked to:
So what’s the problem here? The T-Mobile OnePlus 7T Pro McLaren Edition, unlike most other OnePlus devices, does not have full firmware ZIPs available from OnePlus’s website. So with an unlocked bootloader barring you from taking incremental updates and no full ZIPs to take, you will be stuck on whatever OxygenOS build your phone is running if you decide to pull ahead and unlock your bootloader. The regular OnePlus 7T Pro does have full ZIPs available for downloading, but you can’t take those on this device since it’s carrier-branded and it’s T-Mobile – not OnePlus – who is responsible for the device’s OxygenOS firmware.
Click to expand...
Click to collapse
Thanks for your understanding.

Actually we do.
LLStarks said:
Are you even reading his responses? Those examples came from him.
Even if you had the OTA URL and file captured, you can't flash it. It'll brick your phone unless it goes through the update menu. They are incremental updates that check file integrity. They are not full updates. You cannot flash updates on this phone. Period.
If you have an MSM, that's different. But we don't have that either. Right now, all we can do is wait.
Click to expand...
Click to collapse
There is MSM that works for most oneplus phones. And the Hydrogen image for .34 so I might just do that and unroot.

photolarry said:
There is MSM that works for most oneplus phones. And the Hydrogen image for .34 so I might just do that and unroot.
Click to expand...
Click to collapse
Stop. Just stop. You cannot flash the Hydrogen image. That's for the Chinese non-5G model.

I can use this!
LLStarks said:
Stop. Just stop. You cannot flash the Hydrogen image. That's for the Chinese non-5G model.
Click to expand...
Click to collapse
https://forum.xda-developers.com/7t...7tpro-tmo-5g-unbrick-tool-to-restore-t4043925
and there is an ops file for 34. So Not sure why you do not think I can use MSM. I most certainly can.

photolarry said:
https://forum.xda-developers.com/7t...7tpro-tmo-5g-unbrick-tool-to-restore-t4043925
and there is an ops file for 34. So Not sure why you do not think I can use MSM. I most certainly can.
Click to expand...
Click to collapse
LL Starks is right. MSM has been locked into specific devices starting with this device and going forward. With the 7 Pro, it was different because MSM was still universal for it. It won't work if you try using a Hydrogen MSM tool for a T-Mobile 5G variant. I know it's easy to get frustrated, but you're gonna brick your phone if you don't listen to reason or people who know what they're talking about. Not trying to sound harsh, but that's the simple truth.

photolarry said:
https://forum.xda-developers.com/7t...7tpro-tmo-5g-unbrick-tool-to-restore-t4043925
and there is an ops file for 34. So Not sure why you do not think I can use MSM. I most certainly can.
Click to expand...
Click to collapse
You're confusing several different topics.
No, you cannot manually install OTAs on OnePlus devices from TMO. It worked on the 6T at first, but then the Local Update option was removed in an update. You might be able to sideload through a modified stock recovery, if someone with root can grab the OTA after it downloads, but before it installs, since it will be deleted after.
Yes, there is a HydrogenOS MSM image. No, you cannot flash it on the HD1925 (hotdogg) TMO variant.
Yes, there are several MSM images for our TMO variant. Running any of them will lock your bootloader and restore to stock. When you unlock again after, you will once again be missing the reserve.img needed to accept OTAs.
There are downloadable zips that replace the missing reserve.img needed to accept an OTA. I didn't create the first couple, but I did make ones for .27 -> .31 and .31 -> .34.
Regardless of what build you are on now, a missing reserve.img will not prevent you from seeing an update. Your phone will download it even if you are rooted. However, it will fail to install once it gets to the part where it updates reserve.img.

Ok so what do you recommend?
NotATreoFan said:
You're confusing several different topics.
No, you cannot manually install OTAs on OnePlus devices from TMO. It worked on the 6T at first, but then the Local Update option was removed in an update. You might be able to sideload through a modified stock recovery, if someone with root can grab the OTA after it downloads, but before it installs, since it will be deleted after.
Yes, there is a HydrogenOS MSM image. No, you cannot flash it on the HD1925 (hotdogg) TMO variant.
Yes, there are several MSM images for our TMO variant. Running any of them will lock your bootloader and restore to stock. When you unlock again after, you will once again be missing the reserve.img needed to accept OTAs.
There are downloadable zips that replace the missing reserve.img needed to accept an OTA. I didn't create the first couple, but I did make ones for .27 -> .31 and .31 -> .34.
Regardless of what build you are on now, a missing reserve.img will not prevent you from seeing an update. Your phone will download it even if you are rooted. However, it will fail to install once it gets to the part where it updates reserve.img.
Click to expand...
Click to collapse
Do I restore the reserve.img with the script and tools in that other thread? I did that actually. You are saying I should be able to get the update, and it will unroot me afterwards? I could use magisk to say install to inactive slot after OTA before rebooting though right? I still am not getting the update OTA...I clicked check a bunch of times. Maybe I am not in the queue for this round.

photolarry said:
Do I restore the reserve.img with the script and tools in that other thread? I did that actually. You are saying I should be able to get the update, and it will unroot me afterwards? I could use magisk to say install to inactive slot after OTA before rebooting though right?
Click to expand...
Click to collapse
If you already restored your reserve.img, then the OTA should install once your phone gets it. Some people have been able to update without unrooting, but I do it to be safe. I go into Magisk and choose to restore boot images, but not uninstall. This allows any downloaded modules to remain and not have to be configured again when you root after update.
Once you restore boot images and reboot, the OTA should install and then reboot again. I then repeat the original root steps by pulling an updated boot.img through TWRP, and am back up and running in less than 15 minutes.