Database Users

ASUS cancelled 2.19.40.18 OTA

guys
http://www.asus.com/zentalk/forum.php?mod=redirect&goto=findpost&ptid=14836&pid=107979
asus said they cancelled this update due to unstable update...
1st i dont know what is unstable in this version[same as previous and new bug of call screen animation
2nd lol which update came without new bugs?
3rd they removed after they heard about unlocking bootloader..something fishy right :laugh:

they will probably patch the unlock method with the next update, gonna unlock the bootloader before updating to next update.
Sent from my ASUS_Z008D using Tapatalk

luisoman2000 said:
they will probably patch the unlock method with the next update, gonna unlock the bootloader before updating to next update.
Sent from my ASUS_Z008D using Tapatalk
Click to expand...
Click to collapse
ya same here..but what they will do to unlocked phones/??

ansebovi said:
ya same here..but what they will do to unlocked phones/??
Click to expand...
Click to collapse
Maybe there just will be a check and it will abort if the BL is unlocked
But it should be easy to adapt these OTA updates to unlocked devices

ansebovi said:
ya same here..but what they will do to unlocked phones/??
Click to expand...
Click to collapse
Nothing they can do. As long as you don't flash an OTA or full stock build. They may have a way to patch it in their droidboot.

ansebovi said:
guys
3rd they removed after they heard about unlocking bootloader..something fishy right :laugh:
Click to expand...
Click to collapse
That was my first guess as well

TheSSJ said:
Maybe there just will be a check and it will abort if the BL is unlocked
But it should be easy to adapt these OTA updates to unlocked devices
Click to expand...
Click to collapse
no i am asking about bootloader[can they lock it somehow if we flash next ota]
Harfainx said:
Nothing they can do. As long as you don't flash an OTA or full stock build. They may have a way to patch it in their droidboot.
Click to expand...
Click to collapse
so how can we update from here after ??? need to modified by someone for flashing ???
jaysus145 said:
That was my first guess as well
Click to expand...
Click to collapse
ya my 1st thought too,, haha

ansebovi said:
so how can we update from here after ??? need to modified by someone for flashing ???
Click to expand...
Click to collapse
That's how it works with all custom work. Once you're off stock, you're going to have to wait for someone to post a safe update/install.
Rushing in and taking an OTA is a very common way of breaking your build. Like what we see with running an OTA while rooted. Any number of problems can come up.
They could patch any number of things that would give you a very bad day.
With the support we have here though, we'll probably have flashable, safe OTA zips within a few hours of an OTA being captured/downloaded.

Harfainx said:
That's how it works with all custom work. Once you're off stock, you're going to have to wait for someone to post a safe update/install.
Rushing in and taking an OTA is a very common way of breaking your build. Like what we see with running an OTA while rooted. Any number of problems can come up.
They could patch any number of things that would give you a very bad day.
With the support we have here though, we'll probably have flashable, safe OTA zips within a few hours of an OTA being captured/downloaded.
Click to expand...
Click to collapse
well i am from sony device..they release main update of android..and 1 bug fix,thats all...so we dont care..and no need to worry about relocking issues..
this is the first asus device...man they releasing update for every 10days..i thought we could apply just like that..but since they didnt gave unlocked bootloader tool ,i got these doubt..
and thanks for info..
so i must wait for zips which is modified for unlocked bootloader[if they trying to relock]

I honestly doubt they're going to find a way to relock it with an update, but who knows what voodoo they may come up with.
Either way, we'll grab the updates and get them ready to be flashed quickly. It's a simple process.

I highly doubt he will do anything regarding unlocking/locking bootloader. because:
1. last year they released their official tool to unlock zenfone 4,5,6 bootloader after 3-4 months of release.
2. This year when they launched the zf2 in US they hold contest and developer events via xda. Now xda is a place where no one keeps their bootloader locked. so they knew exactly where they are releasing and advertising the product.
So I dont think they would even bother about this bootloader . Maybe it is an unstable build in terms of their quality test.

Dang, and my 551 (2/16GB) is still in transit.
Was browsing the forum and this thread - has 2.19 been captured and saved somewhere else, or was everyone just downloading off ASUS servers for this OTA (when forced)?
I don't know if I would want 2.19 yet. Maybe to keep on my PC until the right time. That is, if 2.20 comes out and the BL hole is plugged, and those who were on 2.19 (and took advantage of the bootloader unlocking) still got the update successfully - if either of those two outcomes are false, I wouldn't use it.

joel.maxuel said:
Dang, and my 551 (2/16GB) is still in transit.
Was browsing the forum and this thread - has 2.19 been captured and saved somewhere else, or was everyone just downloading off ASUS servers for this OTA (when forced)?
I don't know if I would want 2.19 yet. Maybe to keep on my PC until the right time. That is, if 2.20 comes out and the BL hole is plugged, and those who were on 2.19 (and took advantage of the bootloader unlocking) still got the update successfully - if either of those two outcomes are false, I wouldn't use it.
Click to expand...
Click to collapse
Everthings here http://forum.xda-developers.com/zenfone2/general/ota-links-stock-rom-t3093999

android is open source. and roms are not illegal. so why bother? i don't think asus is interested on ours bootloader plus, other zenfone's are already unlocked

joel.maxuel said:
Dang, and my 551 (2/16GB) is still in transit.
Was browsing the forum and this thread - has 2.19 been captured and saved somewhere else, or was everyone just downloading off ASUS servers for this OTA (when forced)?
I don't know if I would want 2.19 yet. Maybe to keep on my PC until the right time. That is, if 2.20 comes out and the BL hole is plugged, and those who were on 2.19 (and took advantage of the bootloader unlocking) still got the update successfully - if either of those two outcomes are false, I wouldn't use it.
Click to expand...
Click to collapse
Even if your phone gets here on a newer version (it won't), you could always downgrade everything and unlock from there. =)
Shakalaka has backups of everything going back to like version 2.12 or 2.13.

MatteXperiaU said:
android is open source. and roms are not illegal. so why bother? i don't think asus is interested on ours bootloader plus, other zenfone's are already unlocked
Click to expand...
Click to collapse
Problem is they can't support any ROM that isn't official on the zenfone. They'll pass you off. Like most manufacturers.

These are just official update links from Asus. Not backups. Asus can shut those down at any point. Not saying they will.
See here for pre-rooted ROM backups:
http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590

one more doubt..
i think 2.17 is stable build from asus without the android os drinking the battery
now i have unlocked the bootloader ,can i reflash the 2.17[asking since it doesnt have the things which enabled to unlock bootloader] ...or once unlocked,we can do anything like other brands phone?

damian5000 said:
These are just official update links from Asus. Not backups. Asus can shut those down at any point. Not saying they will.
See here for pre-rooted ROM backups:
http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
Click to expand...
Click to collapse
I downloaded the appropriate OTA the other night, so if ASUS pulls the file, I still have it and can share it on Dropbox and/or Copy.
I get the phone today! So hopefully tonight I get the OTA up to 2.18 and then wait to see what upcoming 2.20 has to offer. If we can still unlock the BL with 2.20, I will let that OTA happen. Similarly if we find out that those who unlocked their bootloaders can't take the update (at that point I will cry a little, if there is no official way to unlock BL released with the update ).
If both scenarios above are false, then I will apply my downloaded 2.19, unlock the bootloader, then accept 2.20.
Best one could do eh?
---------- Post added at 07:24 ---------- Previous post was at 07:19 ----------
ansebovi said:
one more doubt..
i think 2.17 is stable build from asus without the android os drinking the battery
now i have unlocked the bootloader ,can i reflash the 2.17[asking since it doesnt have the things which enabled to unlock bootloader] ...or once unlocked,we can do anything like other brands phone?
Click to expand...
Click to collapse
I cannot imagine it would re-lock the bootloader. Should be able to downgrade, as long as you use the whole image and not just the OTA zip.
Now you got me wondering....

joel.maxuel said:
I cannot imagine it would re-lock the bootloader. Should be able to downgrade, as long as you use the whole image and not just the OTA zip.
Now you got me wondering....
Click to expand...
Click to collapse
no i didnt mean it will relock,..
but the unlocked needed some file right..it modifies something right? ...and it is not present in old things..so can old fw run on unlocked bootloader? [or would it get bootloop or damage bootloader]

Axon 7 Software Update - MR2

According to a Mod on Z-Community there should be an update being pushed out shortly. If anyone gets the update can provide the change log that would be appreciated. And if you do the update please let us know if the UI has changed. Still waiting on my axon 7, hopefully it ships tomorrow.

We need someone to capture this update before it's installed.
Always thank those who are helpful...and just ignore those who aren't.

I'll be curious if anyone with an unlocked bootloader can get this ota.

xxBrun0xx said:
I'll be curious if anyone with an unlocked bootloader can get this ota.
Click to expand...
Click to collapse
well if in case that is not possible if someone can capture the OTA i bet we can find a way how to apply the OTA with an unlock bootloader.

that would be great if someone can do that!!

DrakenFX said:
well if in case that is not possible if someone can capture the OTA i bet we can find a way how to apply the OTA with an unlock bootloader.
Click to expand...
Click to collapse
Yea, just create a flashable zip.
Sent from my ZTE A2017U using Tapatalk

shoman94 said:
Yea, just create a flashable zip.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
from b20_boot i when back to B20 Stock, so i may be able to capture that OTA wuhahaha , and if i can make a flashable zip i'll do it for everyone else.

DrakenFX said:
well if in case that is not possible if someone can capture the OTA i bet we can find a way how to apply the OTA with an unlock bootloader.
Click to expand...
Click to collapse
It should be possible to patch most everything -- however, if any of the partition hashes don't match, those partitions couldn't be patched. That would make minemeat out of the partition if you forced it, since they are updating blocks, and not direct files.

DrakenFX said:
from b20_boot i when back to B20 Stock, so i may be able to capture that OTA wuhahaha , and if i can make a flashable zip i'll do it for everyone else.
Click to expand...
Click to collapse
How did you go back? Can you please link me to the thread because I am stumped

bkores said:
How did you go back? Can you please link me to the thread because I am stumped
Click to expand...
Click to collapse
There's no thread , it was just me trying new things base on a user who started the idea a little while ago,

xxBrun0xx said:
I'll be curious if anyone with an unlocked bootloader can get this ota.
Click to expand...
Click to collapse
You will get the OTA. You just can't install it if your recovery is modified or is TWRP.
Sent from my ZTE A2017U using XDA-Developers mobile app

max1001 said:
You will get the OTA. You just can't install it if your recovery is modified or is TWRP.
Sent from my ZTE A2017U using XDA-Developers mobile app
Click to expand...
Click to collapse
No, the bootloader unlocking process changes more than just the recovery. It changes boot, system, and fastboot as well. So even if you reflash a stock recovery, if the OTA tries to patch any of those other partitions, it'll fail. This is why people have been clamouring ZTE to post full system images, so people who unlocked their BL can roll back to full stock in order to get OTAs.
Plus, we don't know if ZTE will use the IMEIs of people who officially submitted a bootloader unlock as exceptions to the OTA rollout.

xtermmin said:
Plus, we don't know if ZTE will use the IMEIs of people who officially submitted a bootloader unlock as exceptions to the OTA rollout.
Click to expand...
Click to collapse
They have to be using a list like that. Otherwise they wouldn't be able to roll out the bootloader unlock OTA to the right phones.
Which of course, is still silly -- they should have used the method others use where it's just baked into the OS and you have to request the appropriate code to provide during unlock. Then everyone would be on the same software load.

I am on my new stock phone I just picked up from Best Buy yesterday. I check the updates screen and it shows MiFavor 4.0 and my current version of B20. I haven't hit next yet but how would I capture the OTA?
I am t work with super slow wifi so I don't want to download anything here.

imp3r10 said:
I am on my new stock phone I just picked up from Best Buy yesterday. I check the updates screen and it shows MiFavor 4.0 and my current version of B20. I haven't hit next yet but how would I capture the OTA?
I am t work with super slow wifi so I don't want to download anything here.
Click to expand...
Click to collapse
B20 is the latest as of today. There's an update coming soon per ZTE. They didn't give us a date.
Sent from my ZTE A2017U using XDA-Developers mobile app

I guess by soon they didn't mean within a few days...Usually when companies say soon it's within 24 hrs.

According to the official forums, the MR2 update has been pushed back to next week.
Update:
Due to a few last minute software optimizations, the update will be pushed until mid to late next week.
Give your fingers a rest. We will update the community when the update goes live.
Click to expand...
Click to collapse
https://community.zteusa.com/thread/12287?start=210&tstart=0

I'm still on stock. How would I go about capturing the OTA when it's released next week?
Also, it looks like the bootloader unlock request form on the ZTE site is no longer available, but instead says: "The form AXON 7/Pro Bootloader Unlock Request is no longer accepting responses. Try contacting the owner of the form if you think this is a mistake."
That could mean something significant (free bootloader unlocks for everyone with no voiding of warranty!) or it could mean that they borked something on the backend (I think it was a Google form, so any number of things could have changed that caused the form to disappear).

rczrider said:
I'm still on stock. How would I go about capturing the OTA when it's released next week?
Also, it looks like the bootloader unlock request form on the ZTE site is no longer available, but instead says: "The form AXON 7/Pro Bootloader Unlock Request is no longer accepting responses. Try contacting the owner of the form if you think this is a mistake."
That could mean something significant (free bootloader unlocks for everyone with no voiding of warranty!) or it could mean that they borked something on the backend (I think it was a Google form, so any number of things could have changed that caused the form to disappear).
Click to expand...
Click to collapse
If you are running and adb logcat on your computer (or your phone) when you check for and/or download the OTA, the full link for the OTA should be in there somewhere. Or, to just save the file, after you download it but before you apply it, you can copy it off of the internal sd card partition. Getting the download location is better though, then people can download it directly for themselves.

rczrider said:
I'm still on stock. How would I go about capturing the OTA when it's released next week?
Also, it looks like the bootloader unlock request form on the ZTE site is no longer available, but instead says: "The form AXON 7/Pro Bootloader Unlock Request is no longer accepting responses. Try contacting the owner of the form if you think this is a mistake."
That could mean something significant (free bootloader unlocks for everyone with no voiding of warranty!) or it could mean that they borked something on the backend (I think it was a Google form, so any number of things could have changed that caused the form to disappear).
Click to expand...
Click to collapse
This is Coming from a ZTE-Employee which many of us know him from ZTE-Community
sshasan Employee 13 minutes ago
ZTE has not changed their opinion on unlocking the bootloader. The bootloader will still be unlockable.
I have temporarily stopped the form from accepting new requests for good reason.
1.) The process for unlocking the bootloader will be changing if all goes well with testing. (This includes stock image)
2.) There is a software update coming next week - Since stock images have not yet been released, instead of adding more customers to the mix of those who will not be able to update, I've decided to not let this happen.
Click to expand...
Click to collapse
so that is GREAT news and something else meaning Unlock Bootloader Request or process will be different

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

Help me, I'm special

Does anyone have a reasonable explanation as to why one isnt getting certain updates?
The only available update I have is the December 2017 one, but afaik that one is riddled with bugs, and I don't rly feel like risking it. The January never popped up, yet alone february and march one. I've tried all those possible "tricks" with Google Services, from data clean up, signing up for the beta program, factory reset; nothing worked.
I've been told by the support to wait for the batches to arrive; 3 times now.. On the Mi Forums I've been told to sacrifice goats to Chthulu.
My disappointment is immeasurable, and my day is ruined.

Download and flash the fastboot ROM by Mi Flash Tool.

Zoldannah said:
On the Mi Forums I've been told to sacrifice goats to Chthulu.
My disappointment is immeasurable, and my day is ruined.
Click to expand...
Click to collapse
LOL! Well, did you do it?
You can try the miflashtool method.

LouisMuruu said:
LOL! Well, did you do it?
You can try the miflashtool method.
Click to expand...
Click to collapse
An entire stock. Did not work ??*
I've never done flashing before, I'm nutorious for ****ing things up. Why can't I just get the OTA the way it's mean to be received ffs

Zoldannah said:
An entire stock. Did not work ??*
I've never done flashing before, I'm nutorious for ****ing things up. Why can't I just get the OTA the way it's mean to be received ffs
Click to expand...
Click to collapse
You are probably on nougat. You need to update to the december Version (oreo preparation) and then you can update to march from there.

The OTA updates are incremental updates from a specific firmware version so you have to go through the sequence of all the updates. You can't just jump over several in one go.

t-bon3 said:
The OTA updates are incremental updates from a specific firmware version so you have to go through the sequence of all the updates. You can't just jump over several in one go.
Click to expand...
Click to collapse
I've seen ppl saying they've got both dec + jan simultaneously.. But I guess this explains it; Thanks babes!

Well, can I ask why are you so special ??

shubham8 said:
Well, can I ask why are you so special ??
Click to expand...
Click to collapse
Special in a sense of being mentally challenged; self degradation. Don't worry, I'm not being condescending ?

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.