[HD1925] [OP7TPROTMO] reserve.img dumps OTA fixer.

[starcms]

SOOOOOO, you're saying I just download one of these script things, for the version I am currently on, then itll un root me??? and I can OTA, then root again???


How do you unroot.....
"is that what this script is for"?

I'm just making sure I don't mess up my device and for some reason, everything on XDA feels like it's not fully explained / i'm hella stupid, forgive me. I need THIS much clarification on some things.

It's pretty clear. This is what is needed to be able to receive OTAs after unlocking your bootloader. It only needs to be applied once (unless you run the msm tool and also unlock your bootloader again) and needs to match the version you are currently on.

It has absolutely nothing to do with root/Magisk

 

[AUriasg]

Hope this helps! This has been tested to work on a device unlocked on 10.0.13,
and there is little reason to believe it won't work on others. Also, if you use the
msm tool for these devices, and wish to unlock and continue to get OTA updates,
you must use this package, as MSM relocks you, and will destroy reserve.img again.


Those of you who have used this, please keep an eye out for updates from TMO
and report back whether you were able to update.
Confirmed that it works with brand new OTAs. Several members of the TG group
took the update from 10.0.16 and 10.0.19 without issue after restoring reserve with
these packages.

Hello, I've just bought an 7TPM used, I was looking to f
Change to a global rom but I read about that issue here in this forum, that lead me to notice that I'm stuck in 10.0.12, could I use this tool too?

Thanks

Edit: I found out in this forum that this is a retail demo unit so it came with this build. So does any one managed to get fixed?

Thanks

 

[NotATreoFan]

For anyone that unlocks their bootloader after the OTA to 10.0.36, here's an updated package to fix future OTAs.

https://www.androidfilehost.com/?fid=8889791610682891398

 

[NotATreoFan]

Successfully updated to 10.0.37 OTA this morning, then pulled the updated reserve.img. You only need this if your bootloader unlock was done after the update.

https://www.androidfilehost.com/?fid=8889791610682923540

 

[SaxManDan]

Had to completely unroot to install OTA... is this normal?

So around the end of July, I rooted my phone then used this script to install the fixed reverse.img. Fast forward to today, OOS 10.0.37 comes out, and I tried to install it, but my phone says "Installation Problem". I had to uninstall Magisk completely, and now the update is downloading. Is this normal? From what I knew, you could install OTAs while rooted. Is this not the case with this phone/script?

 

[NotATreoFan]

So around the end of July, I rooted my phone then used this script to install the fixed reverse.img. Fast forward to today, OOS 10.0.37 comes out, and I tried to install it, but my phone says "Installation Problem". I had to uninstall Magisk completely, and now the update is downloading. Is this normal? From what I knew, you could install OTAs while rooted. Is this not the case with this phone/script?

You don't have to completely uninstall Magisk. I choose the Restore Images option, which leaves all Magisk configuration intact. Then after the update, just pull/patch/flash the updated kernel.

 

[SaxManDan]

You don't have to completely uninstall Magisk. I choose the Restore Images option, which leaves all Magisk configuration intact. Then after the update, just pull/patch/flash the updated kernel.

Darn, I wish I found out about this sooner. So either way, before updating Magisk has to be removed/disabled before the OTA update?

 

[NotATreoFan]

Darn, I wish I found out about this sooner. So either way, before updating Magisk has to be removed/disabled before the OTA update?

Yes, but it's only about 10-15 minutes to root again, depending on how fast you can run through the steps.

 

[gaww]

Yes, but it's only about 10-15 minutes to root again, depending on how fast you can run through the steps.

Just saying hello from 8 's after having dumped my TMO 1925. Much more going on without all the hassles with a carrier phone.

You were a major help when I was there - looks like you still are.

 

[starcms]

It literally takes 30 seconds to install/accept/download OTA and keep root.

A) Use Magisk Manager app to uninstall (click uninstall and click restore images -- don't do a complete uninstall). Don't reboot yet.
B) Accept, download, and install OTA -- do NOT reboot yet!
C) After OTA update is successfully completed and it's asking to reboot, open Magisk Manager, and choose to "install via inactive slot (after OTA)"
D) Reboot, and you'll be upgraded and rooted.

 

[NotATreoFan]

It literally takes 30 seconds to install/accept/download OTA and keep root.

A) Use Magisk Manager app to uninstall (click uninstall and click restore images -- don't do a complete uninstall). Don't reboot yet.
B) Accept, download, and install OTA -- do NOT reboot yet!
C) After OTA update is successfully completed and it's asking to reboot, open Magisk Manager, and choose to "install via inactive slot (after OTA)"
D) Reboot, and you'll be upgraded and rooted.

My phone auto reboots after each OTA.

 

[starcms]

My phone auto reboots after each OTA.

No it doesn't. It puts a little box saying to click to restart now in the bottom right corner of the update screen or it'll automatically restart by X day and Y time if you don't do it yourself before then.

Make sure you watch the update progress so you can manually reboot (update) when you choose.

Edit: In Developer Options, near the very top, there is an option you can uncheck to disable "Automatic System Updates -- Apply update when device restarts". However, I've never had to disable that option. I'm pretty sure it just keeps it from restarting at Y time on X day to complete the update process. You could try unchecking it b4 the next OTA though.

I'm sure tho that if you just stay on the update/OTA screen while it downloads and updates, it won't automatically restart. Even if you click away from that screen, it won't auto restart. Not till after the given day and time anyway. They'll just be an option in the bottom corner to restart now.

 

[NotATreoFan]

No it doesn't. It puts a little box saying to click to restart now in the bottom right corner of the update screen or it'll automatically restart by X day and Y time if you don't do it yourself before then.

Make sure you watch the update progress so you can manually reboot (update) when you choose.

Hmm, maybe I just tap it and don't pay attention. Definitely possible. I'll be sure to keep an eye on for the next update.

 

[luigi90210]

It literally takes 30 seconds to install/accept/download OTA and keep root.

A) Use Magisk Manager app to uninstall (click uninstall and click restore images -- don't do a complete uninstall). Don't reboot yet.
B) Accept, download, and install OTA -- do NOT reboot yet!
C) After OTA update is successfully completed and it's asking to reboot, open Magisk Manager, and choose to "install via inactive slot (after OTA)"
D) Reboot, and you'll be upgraded and rooted.

I have never had this work for me, I always get installation failed and I have to redownload and root manually

These instructions worked well for my pixel 3a xl so I don't know what I'm doing wrong here

 

[starcms]

I have never had this work for me, I always get installation failed and I have to redownload and root manually

These instructions worked well for my pixel 3a xl so I don't know what I'm doing wrong here

You need to ensure you have the stock recovery partition flashed back on beforehand if you flashed the modified recovery or twrp. My advice is don't use fastboot flash on this phone. Or as little as possible anyway. Don't flash twrp. Just boot it using "fastboot boot nameOfTwrp.img"

All the partitions (well, technically not every single one, like persist) are checked by the OTA update tool to ensure their checksums match the expected values to ensure they have never been modified. Boot, recovery, system, odm, vendor, and product are most definitely all in that list.

It's also possible that when you first installed Magisk, you didn't install it properly, on an original unmodified boot image. Then Magisk Manager has no way to properly restore your boot image because it has no proper backup of an original, unmodified one.

 

[luigi90210]

You need to ensure you have the stock recovery partition flashed back on beforehand if you flashed the modified recovery or twrp. My advice is don't use fastboot flash on this phone. Or as little as possible anyway. Don't flash twrp. Just boot it using "fastboot boot nameOfTwrp.img"

All the partitions (well, technically not every single one, like persist) are checked by the OTA update tool to ensure their checksums match the expected values to ensure they have never been modified. Boot, recovery, system, odm, vendor, and product are most definitely all in that list.

It's also possible that when you first installed Magisk, you didn't install it properly, on an original unmodified boot image. Then Magisk Manager has no way to properly restore your boot image because it has no proper backup of an original, unmodified one.

I never flash modified recoveries and won't until twrp is 100% functional

I also follow the root guide instructions by booting twrp, pulling the boot.img patching it with magisk and booting the modified boot.img and installing magisk using the app

I can restore my unmodified boot.img with magisk perfectly fine and I do all the steps as shown but I always get installation failed when I reboot

 

[jbfountain]

Hello. I'm on the latest T-Mobile .37, and would like to pull the reserve.img. It may have been addressed already, but it's a long thread and I read for hours, and didn't find anything on how to pull the reserve.img without root. Can you explain the process to pull it, so I can save it, and share with the rest of the people in this thread? Then I will feel more comfortable with unlocking the bootloader and rooting. I've been on XDA for years and have a good deal of knowledge with HTC, and Samsung, but not Oneplus. Thank you.

 

[NotATreoFan]

Hello. I'm on the latest T-Mobile .37, and would like to pull the reserve.img. It may have been addressed already, but it's a long thread and I read for hours, and didn't find anything on how to pull the reserve.img without root. Can you explain the process to pull it, so I can save it, and share with the rest of the people in this thread? Then I will feel more comfortable with unlocking the bootloader and rooting. I've been on XDA for years and have a good deal of knowledge with HTC, and Samsung, but not Oneplus. Thank you.

I've only pulled it with root, and I always do it immediately after updating. I actually posted it here a week ago, 14 posts back.

 

[jbfountain]

I thought once you unlock the bootloader everything gets erased, so I don't understand how you back it up if it was erased.
Is it located in the stock recovery or somewhere else?

 

[starcms]

I thought once you unlock the bootloader everything gets erased, so I don't understand how you back it up if it was erased.
Is it located in the stock recovery or somewhere else?

He restored reserve if it hadn't been done once after first unlocking bootloader, took the OTA, rooted, and pulled the latest/updated reserve.img