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

[NotATreoFan]

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?

There is a way to pull the reserve.img without root, and I did do it one time was back in the beginning. But honestly, I don't remember the exact steps I took in ADB shell to get it.

Once I had it restored the first time, I just pull it again using a root file explorer on the phone.

 

[jbfountain]

So when the first time I unlock the bootloader I can root and the stock reserve.img will still be there for me to extract and save? Sorry if I'm being a pain in the butt. Like I said this is my first Oneplus, and never had to worry about the reserve.img in order to be able to get updates. I've always been able to boot into TWRP and back up the device, and then when an update was out just return to stock with the backup, and take the update and re-root. Somehow I got the impression that once you unlocked the bootloader it wiped the reserve.img. Thanks for the help. I'll unlock the bootloader tomorrow, as it's really hot where I am, and I'm so drained I have to get some rest.

 

[NotATreoFan]

So when the first time I unlock the bootloader I can root and the stock reserve.img will still be there for me to extract and save? Sorry if I'm being a pain in the butt. Like I said this is my first Oneplus, and never had to worry about the reserve.img in order to be able to get updates. I've always been able to boot into TWRP and back up the device, and then when an update was out just return to stock with the backup, and take the update and re-root. Somehow I got the impression that once you unlocked the bootloader it wiped the reserve.img. Thanks for the help. I'll unlock the bootloader tomorrow, as it's really hot where I am, and I'm so drained I have to get some rest.

No. Unlocking will format the data partition, which is where reserve.img resides (\data\reserve\reserve.img).

But once you are unlocked and rooted, you can use the file I posted last week to restore it, and allow OTAs to work again.

 

[jbfountain]

Thank you for clarifying that. How were you able to get the reserve.img the first time? I'm sorry for being so anal about this. It's been 116 degrees here, and I just had a severe concussion, and want to understand how this was accomplished. Thank you again for your time and help. I'm just starting to recover from the spinal cord surgery and the concussion. I just read back a couple of posts and asw that you didn't remember how you pulled it in adb shell.

 

[gaww]

Thank you for clarifying that. How were you able to get the reserve.img the first time? I'm sorry for being so anal about this. It's been 116 degrees here, and I just had a severe concussion, and want to understand how this was accomplished. Thank you again for your time and help. I'm just starting to recover from the spinal cord surgery and the concussion. I just read back a couple of posts and asw that you didn't remember how you pulled it in adb shell.

I have had similar injuries and you should be taking it easy - stress can actually cause problems.

 

[Tech0verlord]

So my phone is currently on 10.0.37, if I were to unlock my bootloader, which one of these files should I use to restore my reserve.img? Should I use 10.0.25?

 

[RypeDub]

So my phone is currently on 10.0.37, if I were to unlock my bootloader, which one of these files should I use to restore my reserve.img? Should I use 10.0.25?

You would use the OTA fixer for 10.0.37

But actually, I think we don't need to do that anymore.

If you are on 10.0.37, unlock bootloader, root, you're good to go

Unlocking your bootloader and a portion of the rooting process (so at multiple times) will format/erase all data on your phone, so make sure you have backups.

 

[Tech0verlord]

You would use the OTA fixer for 10.0.37

But actually, I think we don't need to do that anymore.

If you are on 10.0.37, unlock bootloader, root, you're good to go

Unlocking your bootloader and a portion of the rooting process (so at multiple times) will format/erase all data on your phone, so make sure you have backups.

Aside from photos/videos which I'll backup manually, would the built in backup system (to g-drive) on the phone be enough?

Edit: found the 10.0.37 fix after reading through the thread a bit

 

[RypeDub]

Aside from photos/videos which I'll backup manually, would the built in backup system (to g-drive) on the phone be enough?

I also personally don't know what is sufficient enough.

This is the first time I've have a fully unlocked bootloader w/root in over a decade.

I just made sure to not use my phone for anything important until it was rootable.

But now that I am rooted, and switched to a newer OnePlus phone, how do I backup like that. All my root customizations, prefs, etc.

Plus, you're non root, so how do you backup the most complete way with that limit ?

I hope we both find out ??

 

[Tech0verlord]

Well, just rooted and it downgraded me to 10.0.36, used the .36 fix package and i cant install the .37 ota. Should I install the .37 fix package?

EDIT: Now, I did go into Magisk and used the uninstall -> restore image option, but even then I still get the error

 

[starcms]

Well, just rooted and it downgraded me to 10.0.36, used the .36 fix package and i cant install the .37 ota. Should I install the .37 fix package?

EDIT: Now, I did go into Magisk and used the uninstall -> restore image option, but even then I still get the error

It "downgraded" you to 10.0.36 because you didn't root correctly and it switched slots. All you needed to do was switch back.

 

[NotATreoFan]

Just received the 10.0.39 5G SA update, so here's the latest reserve.img repair script, should anyone need it.

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

 

[Appreciative]

I don't understand what mistake I've made along the way.

I received the phone and took the OTA to 10.0.37
Then I used the long method of unlocking bootloader. Unlock device via support chat, submit stub to OnePlus and get the cust unlock bin back.
Followed the guide here for rooting:
Unlock bootloader, fastboot twrp to pull, inject magisk and replace. Magisk root has been working fine. Many modules.

I followed the post a few posts back:
Uninstall via magisk manager and chose restore image. Download and install OTA 10.0.39 fails with "couldn't update. Installation problem. Retry"

I would like the ability to quickly flash OTAs as outlined above. If anyone could tell me what part went wrong so I can reconfigure my entire phone (if necessary) to be able to easily take OTAs and retain root.

Thanks for any help

 

[NotATreoFan]

I don't understand what mistake I've made along the way.

I received the phone and took the OTA to 10.0.37
Then I used the long method of unlocking bootloader. Unlock device via support chat, submit stub to OnePlus and get the cust unlock bin back.
Followed the guide here for rooting:
Unlock bootloader, fastboot twrp to pull, inject magisk and replace. Magisk root has been working fine. Many modules.

I followed the post a few posts back:
Uninstall via magisk manager and chose restore image. Download and install OTA 10.0.39 fails with "couldn't update. Installation problem. Retry"

I would like the ability to quickly flash OTAs as outlined above. If anyone could tell me what part went wrong so I can reconfigure my entire phone (if necessary) to be able to easily take OTAs and retain root.

Thanks for any help

Did you run the reserve.img fix? If not, then OTAs will fail until you do. You need to download the package I uploaded that matches the current build you have. After running it, the OTA should run as expected.

 

[Appreciative]

Did you run the reserve.img fix? If not, then OTAs will fail until you do. You need to download the package I uploaded that matches the current build you have. After running it, the OTA should run as expected.

Oh, no I sure didn't. I think I misunderstood and thought that it was not needed for builds after 10.0.25. I see that's the last build in the OP. I'm not sure how I conflated that. Assuming I can find the 10.0.37.7z package somewhere in this thread, I'll follow-up with my results.

Thanks for the help. Please let me buy you a coffee for your efforts. PM me a btc address or leave one here as I'll be in this thread for a few days lol. Thanks again for your efforts and reply

 

[NotATreoFan]

Oh, no I sure didn't. I think I misunderstood and thought that it was not needed for builds after 10.0.25. I see that's the last build in your post. I'm not sure how I conflated that. Assuming I can find the 10.0.37.7z package somewhere in this thread, I'll follow-up with my results.

Thanks for the help. Please let me buy you a coffee for your efforts. PM me a btc address or leave one here as I'll be in this thread for a few days lol. Thanks again for your efforts and reply

Here is the link to the post with 10.0.37 fixer: https://forum.xda-developers.com/showpost.php?p=83366663&postcount=204

Once you repair the reserve.img, future OTAs only require unrooting and restoring images, since the reserve.img will be present and updated as needed by the OTA.

Thank you for the coffee offer, but that is not necessary. I'm here to help however I can.

 

[Jbo914]

Soooooooooo I'm looking for ideas. I bootloader unlocked via the ”bootloader unlock without sim/unlock token” instructions, Rooted via the rest of the root thread instructions, then ran ota fixer for 10.0.0.36 via these instructions. Sadly OTA install returns "Installation Problem". I made sure I did not have root via root checker. Magisk is installed. Etc. Can anyone think of something I overlooked?

 

[derget1212]

Soooooooooo I'm looking for ideas. I bootloader unlocked via the ”bootloader unlock without sim/unlock token” instructions, Rooted via the rest of the root thread instructions, then ran ota fixer for 10.0.0.36 via these instructions. Sadly OTA install returns "Installation Problem". I made sure I did not have root via root checker. Magisk is installed. Etc. Can anyone think of something I overlooked?

https://forum.xda-developers.com/showpost.php?p=83396271&postcount=210

 

[Appreciative]

Here is the link to the post with 10.0.37 fixer: https://forum.xda-developers.com/showpost.php?p=83366663&postcount=204

Once you repair the reserve.img, future OTAs only require unrooting and restoring images, since the reserve.img will be present and updated as needed by the OTA.

Thank you for the coffee offer, but that is not necessary. I'm here to help however I can.

Thanks again for your help. I was able to get it all taken care of. One big problem I'm having that I didn't ever have on my 5T, is the adb driver. I have to revoke authorization, toggle debugging and accept the authorization between every move I make. Between the script I had to do it.

I have the issue on Linux too but it doesn't ever recognize over abd so I use windows. I had this issue for unlocking the bootloader as well as flashing and anything else where I need to connect over USB. I know I'm not the only one as I've seen similar issues mentioned somewhere throughout these sections. If anyone knows the right answer to get that working easily / properly, please reply here as I'll be checking this thread a few more times in the future.

Thanks again for everyone's efforts. Scripts, flash packages, post links and guidance. It's very appreciated

 

[RypeDub]

Just received the 10.0.39 5G SA update, so here's the latest reserve.img repair script, should anyone need it.

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

I ran this and now my lockscreen is crashing so fast, I can't even tap my PIN in to unlock the screen and finish this process.

I'm not sure what's going on, but sometimes I can manage to tap in my PIN fast enough to get fully unlocked and on the home screen, but then what?

I decided to obtain the latest Magisk Manager from https://github.com/topjohnwu/Magisk/releases, and then rename it MagiskManager-v7.5.1.apk so I didn't have to mess with your script.

Running your script allows me unlock my phone and get to the home screen, ONLY using the latest Magisk Manager. I get the lockscreen crashing loop if I use the older version.

My magisk manager is 8.0.1 and my magisk is stuck at 20.4 for some reason.

Fastbooting straight from your boot_10.0.39_magisk.img gives me the lockscreen crashing loop.