Related
okay guys so this is the dilemma...
i was rooted on 7.1.1 dp1 with the flashable pixel zip. I received the DP2 OTA somehow, tried to install but it just restarted the phone.. nothing changed.
I eventually got bored of it and tried flashing the resurrection ROM. however, i got stuck on the boot screen. so i unrooted and flashed the factory image off googles devs site. Now i want to go update to DP2, i have enrolled in the beta but still nothing comes up. i have unenrolled and enrolled heaps of times and nothing is happening.
thanks for any help
It's not immediate. Enroll in the beta again. Wait a couple of hours. Eventually it'll pop up. Reboot after a few hours if you still don't have it.
If all else fails, the DP2 image is available online at developer.android.com/preview/download.html if you don't get the OTA. Just download from the developer site, extract, put phone into fastboot mode, and then run the flashall.bat. This will flash your phone back to stock on developer preview 2. The DP2 build number is NPF26F (You said you had an image from the dev site, check the build number).
RoyJ said:
It's not immediate. Enroll in the beta again. Wait a couple of hours. Eventually it'll pop up. Reboot after a few hours if you still don't have it.
Click to expand...
Click to collapse
I was enrolled in the beta for a couple of days and I still haven't gotten anything
Sent from my Nexus 6P using XDA-Developers mobile app
krisyarno said:
If all else fails, the DP2 image is available online at developer.android.com/preview/download.html if you don't get the OTA. Just download from the developer site, extract, put phone into fastboot mode, and then run the flashall.bat. This will flash your phone back to stock on developer preview 2. The DP2 build number is NPF26F (You said you had an image from the dev site, check the build number).
Click to expand...
Click to collapse
Silly questions but do I need to be rooted to flash the dp2 image ? And no, my apologies. I've got 7.0 NBD91K from Google, not the dev site. My bad!
Sent from my Nexus 6P using XDA-Developers mobile app
agerciaffaa said:
Silly questions but do I need to be rooted to flash the dp2 image ? And no, my apologies. I've got 7.0 NBD91K from Google, not the dev site. My bad!
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Nope! There's no need to be rooted! You do, however, need to have an unlocked bootloader. But I'd imagine you'd have that if you're flashing roms :laugh:
And ah! I'm on the same page as you now about the google developers factory images site. With the android developers site I posted, just scroll down on that page and find the nexus 6P link and download that! This will wipe your data though.
Your problem originally that caused the DP2 update to not work was the pixel mod. If you have that flashed, the ota update doesn't work. I had the same problem. But the good news is, you can get pixel mods for DP2 too! I'm using one too.
krisyarno said:
Nope! There's no need to be rooted! You do, however, need to have an unlocked bootloader. But I'd imagine you'd have that if you're flashing roms :laugh:
And ah! I'm on the same page as you now about the google developers factory images site. With the android developers site I posted, just scroll down on that page and find the nexus 6P link and download that! This will wipe your data though.
Your problem originally that caused the DP2 update to not work was the pixel mod. If you have that flashed, the ota update doesn't work. I had the same problem. But the good news is, you can get pixel mods for DP2 too! I'm using one too.
Click to expand...
Click to collapse
i will know flash dp2 hahaha
and yes i just figured id try to install it only because i received it. i mean, i was able to receive it and it noticed that it was a 6p depsite having flashed the pixel mod
agerciaffaa said:
i will know flash dp2 hahaha
and yes i just figured id try to install it only because i received it. i mean, i was able to receive it and it noticed that it was a 6p depsite having flashed the pixel mod
Click to expand...
Click to collapse
Yeah, it doesn't hurt to try (unless it does). I did the same thing because I was curious about that. I figured it would update and wipe the pixel mod, but nope! :laugh: I hope everything goes smoothly :good:
Mayor news, Nougat Preview is open now, check this thread for more information.
https://community.zteusa.com/message/73727
Go there and register and have some Nougat fun.
EDIT : this is an important information mentioned in the main thread back in Z-Community, so KEEP THAT IN MIND or ask question before proceeding and i mean don't ask them here
Important disclaimer: There is a likelihood that personal data on your device may be lost during the software upgrade process, so a complete backup is highly recommended prior to this upgrade. Furthermore, the ability to roll back from Nougat to Marshmallow will not be supported.
Click to expand...
Click to collapse
UPDATE 12-12-2016
Re: Axon 7 (A2017U) US Nougat Preview
aerospaceman aerospaceman Employee Dec 12, 2016 1:28 PM (in response to aerospaceman)
Hello Community Members. We have received an overwhelming response to our Nougat preview. At this time new applications are closed. If you have been chosen to participate you will be receiving an e-mail with further instructions within the next few days. Thank you to everyone who submitted their application!!
Your Z-Community Team
Click to expand...
Click to collapse
They say there's an NDA, but the actual agreement can't be seen while signing up...? Anyway good luck to people who signs up!
kgptzac said:
They say there's an NDA, but the actual agreement can't be seen while signing up...? Anyway good luck to people who signs up!
Click to expand...
Click to collapse
So that means that anyone who signs up isn't gonna be able to tell us if MiFavor is gone or not with Nougat? That's all I want to hear.
I also want to know if the t-mobile wifi calling and other memory/power management optimization situation has improved. Hopefully the NDA allows that (likely not, lol)
Who knows what the NDA will and will not allow - all you are doing right now is signing up to be a part of the experiment. Not everyone who signs up will be accepted (I hope I am accepted)
Signed up. We will see what happens.
I applied but probably won't get update. I am already rooted with unlocked bootloader.
i think we need a stock rom tool via fastboot or qfil. actually zte said that they would give but there is no news about it.
so i have to wait. i think @DrakenFX or @Unjustified Dev will make it which can be flash via TWRP
Signed up, we'll see.
It won't void warranty for anyone asking.
I signed up. I love beta testing new OS's.
Sent from my ZTE A2017U using Tapatalk
kgptzac said:
I also want to know if the t-mobile wifi calling and other memory/power management optimization situation has improved. Hopefully the NDA allows that (likely not, lol)
Click to expand...
Click to collapse
Power management needs to be fixed, encryption would be nice, and this weird issue where you can't use your photos from google photos as wallpapers.
kgptzac said:
They say there's an NDA, but the actual agreement can't be seen while signing up...? Anyway good luck to people who signs up!
Click to expand...
Click to collapse
After you apply, they will pick who they accept. After you get accepted, then you get the NDA to sign or not sign. If you choose to sign it, then your IMEI gets added to the list and they push out all the extra updates. You can basically refuse at any point up to when you get updates (since apparently you can't go back to Mashmallow).
I unlocked my bootloader... can i still get in on this?
spacemanvt said:
I unlocked my bootloader... can i still get in on this?
Click to expand...
Click to collapse
You should ask that question at the zte community. but probably not.
spacemanvt said:
I unlocked my bootloader... can i still get in on this?
Click to expand...
Click to collapse
Apparently the previous OTAs haven't checked for unlocked bootloader, so unless they changed that for this OTA, you should be able to get it.
http://forum.xda-developers.com/showpost.php?p=70006569&postcount=16
abdi7451 said:
Apparently the previous OTAs haven't checked for unlocked bootloader, so unless they changed that for this OTA, you should be able to get it.
http://forum.xda-developers.com/showpost.php?p=70006569&postcount=16
Click to expand...
Click to collapse
But how do we get back to stock recovery so we can flash the updates?
Signed up. Hoping the beta starts soon. Can't wait to see if they moved from MiFlavor or not.
borijess said:
But how do we get back to stock recovery so we can flash the updates?
Click to expand...
Click to collapse
1- boot to TWRP
2- Tap Mount
3- Check SYSTEM-READ-ONLY
4- Wipe Dalvik, Cache, Data and System
5- Flash my B29.StockSystem
6- Reboot (there's probably going to be a message about NO OS , just ignore and slide to reboot.
Once full boot, reboot back to Recovery to check if stock recovery is in place and reboot if it is..
Signed up.
However I have a question. I own A2017U model but if i reside outside of U.S. does it disqualify me to participate?
Hello, I have been talking with this guy from atnt s7 forum. This is what he said...
- Omar04
-Can't remember where they are but I remember I did this> dial *#8736364# a Screen will come up Software update there I tap on check for update then tap on Results if any you will see a long URL with many numbers on it use that URL to get the bin file containing the OTA link and use the ota link on a download manager for it to download if you don't have that version yet. But for the newest ota you need to decipher by yourself Q=2017 A=January and numbers after month =day of build if you lucky and find the correct build it will show up to download that's how we AT&T users find the Nougat ahead of time.
- If a long link didn't show then you need someone else with older build to do same for link to show on results then every one will be able to use that link and search for OTA hidden in servers.
If anyone is still on the old firmware , there is hope that through using this way, we can get an early final nougat!!!
Unable to process the request.
You have to have an older version of android MM.
That just brings it to the check for update menus with 2 more options. Tmobile is still adding their bloat and testing it before release according to their update status for s7
Sent from my SM-G930T using XDA-Developers Legacy app
afwolfpacked said:
That just brings it to the check for update menus with 2 more options. Tmobile is still adding their bloat and testing it before release according to their update status for s7
Sent from my SM-G930T using XDA-Developers Legacy app
Click to expand...
Click to collapse
T-Mobile website still has it listed as I'm manufacture development stage. Gonna take a while before we see it
Deadlysin9 posted this...
That could be it. I got the server URL for the guy that did the S7 one by just going into /data/data/com.ws.dm (the data folder for our system update app, you'll have to find the package name of yours) and looking through all the files. From there it seems he looked at the desc.bin that it downloads to get the URL of the actual update package, but I don't know what he did after that to find the other files.
I believe this is an alternative possibility of getting the same result. Also it IS possible. Atnt got their software early by using this exact same method.
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.
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.