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

[ntzrmtthihu777]

Ok. I've put together some packages to help people who unlocked their bootloaders
and got stuck on version 10.0.13, 10.0.14, or 10.0.16, or who unlocked
(or will unlock) on version 10.0.19 and wish to get whatever the next OTA version is.

reserve.10.0.*.HD61CB.7z has all the files needed to re-insert your reserve.img where
it should be and correct its permissions. It should allow you to OTA ifyou don't root
after this (this uses a temporary root), or if you unroot before trying to take it. Pick
the version that matches whatever version you are currently on.

Files:
reserve.10.0.13.HD61CB.7z
SHA256: 047c18bc7cf29aef556ed023a061276ff940201d5184355da977a911ccb43931
reserve.10.0.16.HD61CB.7z
SHA256: 0b180e338e889aee149672ba026fb02c16f56d1dfad9351dd9e9f3fabee7d310
reserve.10.0.19.HD61CB.7z
SHA256: 34f92a7f114d3bb4dd8e7cf5aee47ad3909f79fa8ccc97fdaa417ef422dc21ed
reserve.10.0.25.HD61CB.7z
SHA256: 85157f6f9f386c2d87235762862fbd5c6f844ab9f750fc5637b87a2fc0c25815


Instructions:

0. This script starts at the normal system screen.
1. Unzip.
2. If you're on windows, extract the contents of platform-tools_r29.0.5-windows.zip
into the root of the same folder. If you're on linux, adjust your $PATH variable in shell.
3. Run fix-reserve.sh or fix-reserve.bat for linux or windows respectively.
4. Follow the instructions in the prompt. (when it says 'when you're booted' that
means booted and unlocked (pin, pattern, whatever. userdata needs to be decrypted
at this point)).
5. It will reboot you. Magisk manager will still be installed but you will otherwise
not be rooted. The magisk_patched.img in this folder will root you permanently
if you would like.

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.

 

[js042507]

Thanks for this. So just to be clear, I should be able to run the second part (fix reserve) only and this should put back the .img file so I could theoretically receive the OTA? Is the first part necessary at all? I am on 10.0.16 and would just like to receive the OTA directly. Of course, I would unroot first.

 

[LLStarks]

No, you need to do the whole thing.

 

[ntzrmtthihu777]

Thanks for this. So just to be clear, I should be able to run the second part (fix reserve) only and this should put back the .img file so I could theoretically receive the OTA? Is the first part necessary at all? I am on 10.0.16 and would just like to receive the OTA directly. Of course, I would unroot first.

The first part is necessary if you are on any other version than 10.0.19. You would need a reserve.img dumped from 10.0.16
to ota to 10.0.19, and since most people unlocked before 10.0.19 came out, we're not likely to get ahold of reserve.img for
those versions.

 

[dstryrwiz]

Does the first part perform a clean wipe or just force the OTA to apply even with the file mismatch?

 

[ntzrmtthihu777]

Does the first part perform a clean wipe or just force the OTA to apply even with the file mismatch?

First part does not wipe at all, just an overwrite. It fastboot flashes all the non-device-specific partitions as dumped
from a phone which was updated from 10.0.13 to 10.0.19, so after the first bit, and then restoring the reserve.img, your
phone should in theory be exactly how it would be if you hadn't unlocked, except its unlocked. Confused yet?

 

[dstryrwiz]

First part does not wipe at all, just an overwrite. It fastboot flashes all the non-device-specific partitions as dumped
from a phone which was updated from 10.0.13 to 10.0.19, so after the first bit, and then restoring the reserve.img, your
phone should in theory be exactly how it would be if you hadn't unlocked, except its unlocked. Confused yet?

Understood. Just to be clear though, this overwrite doesn't result in a replacement of the data partition with a blank partition, correct?

I understand that it's technically not a wipe, but I just want to be certain by doing this process that I won't end up losing all my files and need to restore all my apps again. If I need to, it's fine, just want to know that will happen before I do this process if it will.

 

[ntzrmtthihu777]

Understood. Just to be clear though, this overwrite doesn't result in a replacement of the data partition with a blank partition, correct?

I understand that it's technically not a wipe, but I just want to be certain by doing this process that I won't end up losing all my files and need to restore all my apps again. If I need to, it's fine, just want to know that will happen before I do this process if it will.

Well, standard disclaimers apply for any sort of flash operation on your phone, but no, it should
not delete anything in userdata. The first script pack should not touch it at all, and the second one
doesn't do anything other than push a file and correct permissions and selinux context.

 

[La_anvil]

excellent. thanks

 

[nickmc01]

Everything worked for me. Also looks like the Magisk patch works as well. So far no issues. Hopefully this will work with the next OTA update.

 

[NotATreoFan]

Very nice! I will probably take a shot of rooting my phone next weekend. Just got done setting my replacement phone up, and not in a rush during the week to do it again.

 

[dstryrwiz]

Update worked perfectly for me. Thanks for this!

 

[Keepinitgreen]

directions are very unclear in batch for update part, says it was finished with the Super (after parsing all 12 parts) and then nothing and now when i closed out to try to do the reserve to the boot loader im getting into qualcoms crashdump mode and its saying corrupted force dump kernel_restart. Please advise.

 

[ntzrmtthihu777]

directions are very unclear in batch for update part, says it was finished with the Super (after parsing all 12 parts) and then nothing and now when i closed out to try to do the reserve to the boot loader im getting into qualcoms crashdump mode and its saying corrupted force dump kernel_restart. Please advise.

No, it was 'finished' with super. there are more images after that.
Can you get into either fastboot or fastbootd mode?

 

[Keepinitgreen]

No, it was 'finished' with super. there are more images after that.
Can you get into either fastboot or fastbootd mode?

My apologies brother, did not realized there were more to flash. Just completed part one now to do the reserve.

 

[ntzrmtthihu777]

My apologies brother, did not realized there were more to flash. Just completed part one now to do the reserve.

It happens. I amended the first post to say it would reboot on its own, I thought I had,
but it was only on the second part.

 

[Keepinitgreen]

It happens. I amended the first post to say it would reboot on its own, I thought I had,
but it was only on the second part.

All good man! Appreciate this dope workaround. I have intermediate experience with terminal so it's a lot of guess work haha

 

[Gamesoul Master]

The first part is necessary if you are on any other version than 10.0.19. You would need a reserve.img dumped from 10.0.16
to ota to 10.0.19, and since most people unlocked before 10.0.19 came out, we're not likely to get ahold of reserve.img for
those versions.

Is this still the case? And if so, would it be useful to have access to somebody with a locked HD1925 running 10.0.16?

 

[jhofseth]

@ntzrmtthihu777 , I wonder how hard it would be to modify all future snatched OTAs to completely ignore reserve.img? I did see one line in the last one mentioning a specific reserve size.

 

[NotATreoFan]

@ntzrmtthihu777 , I wonder how hard it would be to modify all future snatched OTAs to completely ignore reserve.img? I did see one line in the last one mentioning a specific reserve size.

You would need root at a minimum, and likely a functional TWRP as well. Once you modify the OTA, it will fail the signature check.