Database Users

New OTA Zip If Devs need

Here is what I pulled off my phone
http://www.multiupload.com/OFWXQJCXBZ
This is the logcat as well
http://www.multiupload.com/JKGT5YYAVH

Here are the radio hashes contained in the OTA:
radio.img -> aa5ab6837c5ef4fe602ea8b5ee6ae544
mdm9k.img -> 373745d310240a57b8e360a40e648178
They match exactly to the leaked 1.13.605.7 radios.

So radio version, 1.16.00.0402w_1, in this OTA update and the leaked release is the same?

Here:
http://twitter.com/#!/TeamAndIRC/status/68719544964882433
And here:
http://twitter.com/#!/TeamAndIRC/status/68717365759709184
List of differences

just because the numbers are same.. it may not mean they are the same. Remember one was never officially released. Unless they are taken apart.. one can't really say if they are the same.
Either way a flashable zip with the officially released OTA should be put out to flash over.

Another update:
http://twitter.com/#!/TeamAndIRC/status/68729302467883008
http://twitter.com/#!/TeamAndIRC/status/68729389340295168
If you're too lazy to click the links then here:
@TeamAndIRC ✔ jcase
Root version of the OTA will not come from us, as we released it two weeks ago already
@TeamAndIRC ✔ jcase
OTA == our leak ... LAME #Thunderbolt

Tekk I can't see your links since Twitter's blocked here at work but I got this from another site:
Recent TeamAndIRC tweets:
Root version of the OTA will not come from us, as we released it two weeks ago already
Posted on May 12, 2011
OTA == our leak ... LAME #Thunderbolt
Posted on May 12, 2011

kriskmk said:
just because the numbers are same.. it may not mean they are the same. Remember one was never officially released. Unless they are taken apart.. one can't really say if they are the same.
Either way a flashable zip with the officially released OTA should be put out to flash over.
Click to expand...
Click to collapse
I'm sorry, but are you serious? Do you know what an MD5 sum is?

Ha thanks Tekk!

Well, that's disappointing.

I would agree since I run rooted RUU leak and I got random reboots. So if VZW pushes the leak as official OTA, then I don't see how they won't get ton of support calls on this from non-rooted customers.

Funny...after looking at the thunderbolt_instructions.pdf from Verizon's Support site, it shows the size of the update at 22.277 MB, but the other screenshots from droid-life are showing it at 35.649 MB...wonder what the difference could be?

wraithdu said:
I'm sorry, but are you serious? Do you know what an MD5 sum is?
Click to expand...
Click to collapse
My comment was to the guy who referenced the radio numbers..I didn't even see your post. Still curious why the OTA is about 10 MB larger.

kriskmk said:
Still curious why the OTA is about 10 MB larger.
Click to expand...
Click to collapse
They supposedly did some updating to Backup Assistant and a few other software peices but it looked like mostly bloat (at least from the pdf description.)

From the PDF:
SOFTWARE UPDATE
GET THE MOST OUT OF YOUR THUNDERBOLT BY HTC.
Verizon Wireless is pleased to announce a new software update,
Build Number: 1.13.605.7 Baseband: 1.16.00.0402w_1,
for your ThunderBolt™ by HTC.
Verizon Wireless and HTC encourage you to download this update.
Web Browsing and Data Access
+ Enhanced data connectivity when accessing the Verizon 3G network.
Email and Messaging
+ SMS and MMS messages are stored properly in the Messaging
Application (Inbox, Sent, etc.).
Additional Device Features
+ Timing for device activation has been improved.
+ “Backup Assistant” is correctly displayed in the Application menu.
+ Stability improvements for data centric applications such as
Facebook, KAYAK, Yahoo! Mail, My Verizon and more.
+ Accurate location is displayed when accessing the Weather Widget.
+ Quickly load GPS updates for Google Maps and VZ Navigator

100% byte for byte the same as our last leak.

Thanks j for verifying this.

I for one am excited for the OTA. Now everyone elses phone can reboot randomly just like ours.

kriskmk said:
My comment was to the guy who referenced the radio numbers..I didn't even see your post. Still curious why the OTA is about 10 MB larger.
Click to expand...
Click to collapse
Ah, understood.
@jcase
Good to hear!

jcase said:
100% byte for byte the same as our last leak.
Click to expand...
Click to collapse
Good to know. Thanks J!

OJ6 update now available

Battery optimization and security updates.

I see no difference at all between this new update and the previous one. Can somebody state the differences if there is any please?

Probably part of the new "monthly" update schedule for security fixes. It's only 150.55 MB. Looks like it fixed the most recent Stagefright vulnerabilities.

poit said:
Probably part of the new "monthly" update schedule for security fixes. It's only 150.55 MB. Looks like it fixed the most recent Stagefright vulnerabilities.
Click to expand...
Click to collapse
I believe they sent another update to handle the stagefright. This one claimed Battery improvements so we will test and see

al3azim said:
I believe they sent another update to handle the stagefright. This one claimed Battery improvements so we will test and see
Click to expand...
Click to collapse
I think OG5 was supposed to fix the stagefright vulnerabilities but it didn't, there were new vulnerabilities discovered which you can test for using stagefright detector. OJ6 takes care of the new vulnerabilities.

poit said:
Probably part of the new "monthly" update schedule for security fixes. It's only 150.55 MB. Looks like it fixed the most recent Stagefright vulnerabilities.
Click to expand...
Click to collapse
poit said:
I think OG5 was supposed to fix the stagefright vulnerabilities but it didn't, there were new vulnerabilities discovered which you can test for using stagefright detector. OJ6 takes care of the new vulnerabilities.
Click to expand...
Click to collapse
Ok, thank you. Hopefully they got it this time around

Anyone rip out the update to add to current roms.
Sent from my 0x1 Note 4...... I love tep

kaos420 said:
Anyone rip out the update to add to current roms.
Sent from my 0x1 Note 4...... I love tep
Click to expand...
Click to collapse
If this update is the same type of update the N5 got then no you can't "add" this ota to current roms. It is a very complex patch that envolves actually patching all of the system files in the rom. I would need somebody to pull the ota zip from their phone and upload it and i will be able to give you a definite answer. But I can almost guarantee this ota is in fact a patch and therefore will be impossible to use for dev purposes. Speaking from my experience with the N5 ota which i quickly learned upon extracting and looking at the ota zip for it.

tx_dbs_tx said:
If this update is the same type of update the N5 got then no you can't "add" this ota to current roms. It is a very complex patch that envolves actually patching all of the system files in the rom. I would need somebody to pull the ota zip from their phone and upload it and i will be able to give you a definite answer. But I can almost guarantee this ota is in fact a patch and therefore will be impossible to use for dev purposes. Speaking from my experience with the N5 ota which i quickly learned upon extracting and looking at the ota zip for it.
Click to expand...
Click to collapse
Where is the file located?

tx_dbs_tx said:
If this update is the same type of update the N5 got then no you can't "add" this ota to current roms. It is a very complex patch that envolves actually patching all of the system files in the rom. I would need somebody to pull the ota zip from their phone and upload it and i will be able to give you a definite answer. But I can almost guarantee this ota is in fact a patch and therefore will be impossible to use for dev purposes. Speaking from my experience with the N5 ota which i quickly learned upon extracting and looking at the ota zip for it.
Click to expand...
Click to collapse
only reasaon i asked is came from note 3. we had a small update that was able to be flashed over current setup. but im sure someone will grab it.

After update i can't flash recovery via odin . Stuck on stock until i figure this one out

Anyone else having horrible speeds like this? Before I could get at least 13 down and sometimes even over 20 but this is horrible. We got a new prl version with this update too so I don't know if that's why. Well for some reason I can't post a pic but I only got 4 down and not even 1 full Meg up.
Sent from my SM-N910P using XDA Free mobile app

My wifi was slow downloading even after a fresh restart so i odin back to og and all good again

No wifi problems here. Speedtest reports the usual 35 down and 3 up. I'll check LTE when I get in a decent signal area. I'm on OJ6 with the 030 prl
Sent from my SM-N910P using Tapatalk

1midniterider said:
Where is the file located?
Click to expand...
Click to collapse
Cache folder

bonebeatz1234 said:
After update i can't flash recovery via odin . Stuck on stock until i figure this one out
Click to expand...
Click to collapse
Any update on rooting and recovery after updating?

poit said:
No wifi problems here. Speedtest reports the usual 35 down and 3 up. I'll check LTE when I get in a decent signal area. I'm on OJ6 with the 030 prl
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Same here. Wifi is the same and same prl. The weird thing was my signal didn't seem to really change simply driving around where normally it would be better.
Sent from my SM-N910P using XDA Free mobile app

To get the update zip do this. First you MUST be on the stock odexed OG5 rom. Next go to Settings | System update and check for updates or it may prompt you that an update is available automatically. simply download the update but DO NOT install it. Last, root your phone if you aren't already by odin'ing the latest TWRP recovery then flash a pre-rooted OG5 kernel in recovery and reboot. You will also need to flash the latest SuperSu binaries or download SuperSU from google Play and install it and then use that to install the binaries. Once you have proper root, use a root file browser (I recommend root explorer) and look in the root directory for a folder named "fota". The ota will be a zip file with a file name that is a mix of numbers and letters or it will be named "update.zip". It will be over 100mb in size. Copy that zip to your phone's internal storage or sd card and then upload that zip file and pm me the link. I will check it out. I'm pretty sure the update contains security updates that require "patching" the system files. This means the update.zip will be impossible to use for updating custom roms. We will have to wait for the tar ball.

Patch7 said:
Any update on rooting and recovery after updating?
Click to expand...
Click to collapse
I couldn't flash twrp recovery because it wouldn't work. I used cwm to get going again . The thing is i couldn't find it for sprint note 4 so i used a different model tar file not recommended unless you know what you doing . My touchscreen was not accurate after i flashed that recovery but i already knew it. I had to use dialer code *#2663# then i was rooted and back on custom rom.

Does this fix the damn crash to lock screen?

November security update is up

OTA's and factory images have been posted for November security updare.
https://developers.google.com/android/ota
Three versions:
NDE63U Europe
NDE63V US, except Verizon
NDE63X Verizon

With the BIG warning on the page about be sure to backup all your Photos and Personal data before applying the Update, does this means that it will delete all your data for just applying an OTA update? I understand that for applying the Full Factory images but does it really wipes the data applying just the OTA updates?
Sorry, but this being my first Nexus/Google phone what I know for OTA updates was just a simple process that doesn't delete anything on the phone, and I just want to be sure how it is here before I proceed, thanks in advance.

erasat said:
With the BIG warning on the page about be sure to backup all your Photos and Personal data before applying the Update, does this means that it will delete all your data for just applying an OTA update? I understand that for applying the Full Factory images but does it really wipes the data applying just the OTA updates?
Sorry, but this being my first Nexus/Google phone what I know for OTA updates was just a simple process that doesn't delete anything on the phone, and I just want to be sure how it is here before I proceed, thanks in advance.
Click to expand...
Click to collapse
Best to back up your data, just to be safe. But I personally sideloaded "U" without any issue. Nothing lost.

cam30era said:
Best to back up your data, just to be safe. But I personally sideloaded "U" without any issue. Nothing lost.
Click to expand...
Click to collapse
Yeah, I understand the risks when updating anything so I always do a backup of the most important stuff just in case, but as you know it's not the same to have to do a Full backup/restore. I needed to be sure but if you did it and you are fine then with what I already have backed up I should be fine too, thanks.

I just restored to stock my L and then checked for updates before rooting.
It said I'm already up to date.
I'll try again in a little while before rooting.
But simply being "unlocked" might be what is preventing me from grabbing an update. Not sure.

CZ Eddie said:
I just restored to stock my L and then checked for updates before rooting.
It said I'm already up to date.
I'll try again in a little while before rooting.
But simply being "unlocked" might be what is preventing me from grabbing an update. Not sure.
Click to expand...
Click to collapse
You can download the update(s) from the Google dev site and adb sideload of fastboot flash the factory image (if your bootloader is unlocked). No need to wait for the OTA, if you don't want to...

Whats the difference between builds NDE63U, NDE63V and NDE63X?

Got a vzw pixel that BL unlocked. Safe to flash the 63X? I saw @jcase said vzw would not do an OTA that relocked your BL. Just wondering if anyone else flashed the 63X build.

armandocorti said:
Whats the difference between builds NDE63U, NDE63V and NDE63X?
Click to expand...
Click to collapse
U-> 11/1 sec patch
V-> 11/5 sec patch
X-> 11/6 sec patch

cam30era said:
U-> 11/1 sec patch
V-> 11/5 sec patch
X-> 11/6 sec patch
Click to expand...
Click to collapse
Not arguing, but how do you know this.
The previous three builds were all the for different phones.
It's natural to expect the new three builds (all dropped on the same day) are for three different phones, USA, Verizon and *something else*.

CZ Eddie said:
Not arguing, but how do you know this.
The previous three builds were all the for different phones.
It's natural to expect the new three builds (all dropped on the same day) are for three different phones, USA, Verizon and *something else*.
Click to expand...
Click to collapse
http://source.android.com/security/bulletin/2016-11-01.html

Was going to flash the factory image system but it looks like the process has changed.... More files and slot a and b.
Anyone know the proper way to manually flash the system.img?

cam30era said:
You can download the update(s) from the Google dev site and adb sideload of fastboot flash the factory image (if your bootloader is unlocked). No need to wait for the OTA, if you don't want to...
Click to expand...
Click to collapse
Yes, I realize I can typically install my own updates.
But as of right now, nobody truthfully knows which phone should have which build. P is so far looking Verizon Only.
Nobody I know of on Verizon has the H or L images.
So I'd rather be safe than sorry and let my phone CHOOSE it's update, and it did not so I mentioned that here to prevent others from restoring to stock and trying for an OTA
Anyways, it's just a payload.bin file. Not the same android image as the older files. I'm actually not sure how to install a payload.bin.
---------- Post added at 12:48 PM ---------- Previous post was at 12:46 PM ----------
cam30era said:
http://source.android.com/security/bulletin/2016-11-01.html
Click to expand...
Click to collapse
Yeah, I get that there are security patches.
But what I'm asking you is to tell us how you know those security patches correspond with the different builds.
I skimmed the page but didn't notice anything saying one way or the other.

CZ Eddie said:
Yes, I realize I can typically install my own updates.
But as of right now, nobody truthfully knows which phone should have which build. P is so far looking Verizon Only.
Nobody I know of on Verizon has the H or L images.
So I'd rather be safe than sorry and let my phone CHOOSE it's update, and it did not so I mentioned that here to prevent others from restoring to stock and trying for an OTA
Anyways, it's just a payload.bin file. Not the same android image as the older files. I'm actually not sure how to install a payload.bin.
Click to expand...
Click to collapse
My vzw pixel shipped with 63H.

jaxenroth said:
My vzw pixel shipped with 63H.
Click to expand...
Click to collapse
Then you're the only person on the board so far who has an H build on Verizon:
http://forum.xda-developers.com/pixel-xl/help/build-pixel-t3489990/page2
Could you please post in that thread to let others know?
I wonder if you got a non-Verizon phone.

CZ Eddie said:
[/COLOR]
Yeah, I get that there are security patches.
But what I'm asking you is to tell us how you know those security patches correspond with the different builds.
I skimmed the page but didn't notice anything saying one way or the other.
Click to expand...
Click to collapse
Valid question. @jcase has clearly stated that "X" would prevent VZW bootloader unlock. Regarding U and V, and which is 11/1 and which is 11/5, I don't know for sure. But it's clear from the Google dev link that each of the 3 builds include an incremental increase in patches.

"clearly stated that "X" would prevent VZW bootloader unlock."
Those durty basturds.
And that's why I didn't get a VZW phone.
<<----- VZW hater gets to hate on VZW yet again. :laugh:

JustusIV said:
Was going to flash the factory image system but it looks like the process has changed.... More files and slot a and b.
Anyone know the proper way to manually flash the system.img?
Click to expand...
Click to collapse
I guess i will do an adb sideload of the OTA.
I have never done it this way, but it looks like others have done this, and the boot-to-root still works.

with the newest radio being in the v .. i would speculate that its u world v north america and x verizon
corrected radio
Sent from my marlin using XDA Labs

CZ Eddie said:
Not arguing, but how do you know this.
The previous three builds were all the for different phones.
It's natural to expect the new three builds (all dropped on the same day) are for three different phones, USA, Verizon and *something else*.
Click to expand...
Click to collapse
"The previous U and V versions were a few days older and are simply there for legacy reasons."
Source > http://www.androidcentral.com/google-posts-latest-pixel-images-november-security-patch

VS995

Can Someone make a Stock Rom for the VS995 for TWRP
or point to a guide that allows you to update to the latest system files and security patches.
Verizon started rolling out Vs99519A recently and for what ever reason I cant update my system past (15a) and keep root using kdz writer

Still waiting on the kdz for 19a. AlphaRom is close to stock and it's built off 18a

i95swervin said:
As far as I know there is no public kdz file for vs995 19a. If you see one let me know, I'll build it.
You can update to my rom its based off of stock vs995 18a.
Click to expand...
Click to collapse
Thanks I have used Alpha but it doesnt include the hd recorder and I haven't been able to install manually.
Just force closes. I appreciate the feedback.

i95swervin said:
should of submitted a bug report. I have a flashable zip of the debloated files that you could add back in.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=75141428&postcount=276
TheLgHifi Recorder is not included in alpha-app-add-on-rev2

i95swervin said:
my bad I must of forgot to add it in. I will redo the installer and add that in. Also I have succesfully pulled the system from the 19a ota update. A update for alpha rom will be releasing soon.
Click to expand...
Click to collapse
Thanks again

i95swervin said:
my bad I must of forgot to add it in. I will redo the installer and add that in. Also I have succesfully pulled the system from the 19a ota update. A update for alpha rom will be releasing soon.
Click to expand...
Click to collapse
Thanks for doing that. I know that is probably a pain considering the 19A KDZ isn't out yet. Looking forward to it!

Has anyone updated to The latest update VS9951AA
Dated 02012018

Vernox701 said:
Has anyone updated to The latest update VS9951AA
Dated 02012018
Click to expand...
Click to collapse
Yes, last night, Happy Valentine's Day to me and my phone!
So far the update appears as "Mostly Harmless" it's billed as security fixes.
After installing the phone didn't melt, brick, explode, rip, snort, farkle nor fall apart so, again, "Mostly Harmless."

I updated yesterday also, and can not find anything new or different? Other than my phone is really slow for about 10 minutes after the update/reboot, then it runs fine.
Not much info on the internet other than security update.

Still no antirollback on this latest update (VS9951AA)???

Just received an update tonight from Verizon.
Running Alpha 1aa....I blocked the update just passing the info along.

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.