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

[NotATreoFan]

If I wanted to use the 10.0.31 reserve fix script you did. But wanted to restore 10.0.27, could I just swap the reserve file in your zip and be good?

I would just like having both the reserve fix script and a msm tool for the same version which would be 10.0.27. Since there is no 10.0.31 msm tool available for download.

If you are on .27 now, the .31 file includes a newer kernel, so you would also need to swap out your stock kernel.

 

[tmushtare]

If you are on .27 now, the .31 file includes a newer kernel, so you would also need to swap out your stock kernel.

I hate to keep asking questions, but for the sake of learning. Would you mind explaining how to edit your package to make the .27 reserve file work?

OR would it be easier to make an remake an msm restore tool for .31?

 

[NotATreoFan]

I hate to keep asking questions, but for the sake of learning. Would you mind explaining how to edit your package to make the .27 reserve file work?

OR would it be easier to make an remake an msm restore tool for .31?

The MSM tools come from OnePlus, which they don't share easily.

If you want to modify the package, you need to replace the .31 kernel I have in there, and change the name of the kernel in the script. I would recommend replacing the reserve.img also, although someone said that it is unchanged from 27 to 31.

 

[perrymike15]

10.0.12

Hey guys I got an eBay phone (Tmo HD1925) for cheap and turns out it's a retail demo. Clean imei and it came unlocked, but it's on 10.0.12...someone else on here had that same weird store demo software. Do you think I'm SOL? Or could I use MSM tool for 10.0.13?

 

[jhofseth]

Hey guys I got an eBay phone (Tmo HD1925) for cheap and turns out it's a retail demo. Clean imei and it came unlocked, but it's on 10.0.12...someone else on here had that same weird store demo software. Do you think I'm SOL? Or could I use MSM tool for 10.0.13?

You could use the latest MSM from here: https://forum.xda-developers.com/7t-pro-mclaren/how-to/op7tpro-tmo-5g-unbrick-tool-to-restore-t4043925

 

[perrymike15]

Ok cool, thanks. Just making sure I wouldn't brick it using one of those. Also, does this remove all the T-Mobile bloatware and even bootlogo or nah? Had to ask

 

[frpst9]

10.0.34 is out

Coming from 10.0.31, can anyone provide some guidance on how to make this process work in this scenario?

 

[NotATreoFan]

Coming from 10.0.31, can anyone provide some guidance on how to make this process work in this scenario?

Are you unlocked/rooted? If so, what version were you on when you unlocked?

 

[frpst9]

Are you unlocked/rooted? If so, what version were you on when you unlocked?

I am unlocked and rooted. I think I was on 10.0.19 when I unlocked originally.

 

[NotATreoFan]

I am unlocked and rooted. I think I was on 10.0.19 when I unlocked originally.

And were you able to update to 10.0.31? If so, the only thing you should have to do is have Magisk restore your boot image (no need to uninstall Magisk), then reboot and accept the OTA.

 

[frpst9]

And were you able to update to 10.0.31? If so, the only thing you should have to do is have Magisk restore your boot image (no need to uninstall Magisk), then reboot and accept the OTA.

That did the trick! Thank you!

 

[NotATreoFan]

That did the trick! Thank you!

You're welcome. Just be sure to pull a fresh copy of the kernel for rooting, don't reuse the .31 one.

 

[gaww]

And were you able to update to 10.0.31? If so, the only thing you should have to do is have Magisk restore your boot image (no need to uninstall Magisk), then reboot and accept the OTA.

That worked for me also.

 

[starcms]

New OP7T Pro 5G TM user here. Lots of experience, but with nexus/pixel/essential phones using fastboot to simply flash everything.

While I wait the 7 days for my unlock token, what should I do since I am on the very latest 10.0.34 and there aren't matching msm and reserve.img fixer versions for the most recent versions?

I'm thinking after unlocking the bootloader, I need to run the 10.0.19 msm, then 10.0.19 reserve img fix? Then just take the 10.0.34 ota like normal, root with magisk, and I should have no issues in the future receiving otas as long as I restore stock boot image?

Thanks much!!

---------- Post added at 05:02 ---------- Previous post was at 04:24 ----------

Or different idea, is it possible to pull reserve.img while bootloader locked for 10.0.34? If so, how? Thanks again!

 

[NotATreoFan]

New OP7T Pro 5G TM user here. Lots of experience, but with nexus/pixel/essential phones using fastboot to simply flash everything.

While I wait the 7 days for my unlock token, what should I do since I am on the very latest 10.0.34 and there aren't matching msm and reserve.img fixer versions for the most recent versions?

I'm thinking after unlocking the bootloader, I need to run the 10.0.19 msm, then 10.0.19 reserve img fix? Then just take the 10.0.34 ota like normal, root with magisk, and I should have no issues in the future receiving otas as long as I restore stock boot image?

Thanks much!!

---------- Post added at 05:02 ---------- Previous post was at 04:24 ----------

Or different idea, is it possible to pull reserve.img while bootloader locked for 10.0.34? If so, how? Thanks again!

You can flash the 10.0.27 MSM from here: https://forum.xda-developers.com/7t...7tpro-tmo-5g-unbrick-tool-to-restore-t4043925

Then once you are unlocked, I posted an updated zip with the userdata.img necessary to accept OTAs beyond 10.0.27.

 

[starcms]

You can flash the 10.0.27 MSM from here: https://forum.xda-developers.com/7t...7tpro-tmo-5g-unbrick-tool-to-restore-t4043925

Then once you are unlocked, I posted an updated zip with the userdata.img necessary to accept OTAs beyond 10.0.27.

I had seen your updated zip but thought it was for 10.0.31 only. So it will also work on 10.0.27 but not 10.0.34? Do I need to replace the boot img in zip with the one from 10.0.27 or can I use it exactly as-is?

 

[NotATreoFan]

I had seen your updated zip but thought it was for 10.0.31 only. So it will also work on 10.0.27 but not 10.0.34? Do I need to replace the boot img in zip with the one from 10.0.27 or can I use it exactly as-is?

The zip that I posted is what allowed me to successfully update from .27 to .31. I then posted another zip that had the userdata pulled from my phone after that update, in case someone unlocked for the first time on .31.

 

[starcms]

The zip that I posted is what allowed me to successfully update from .27 to .31. I then posted another zip that had the userdata pulled from my phone after that update, in case someone unlocked for the first time on .31.

Ah I see. I can't seem to find your post for the 10.0.27 zip. Any help?

Much thanks!!

Edit: I found a related post, but the link expired after 30 days. And it's not your zip, just reserve.img from 10.0.27 https://forum.xda-developers.com/showpost.php?p=81983057&postcount=107

Edit2: got it. https://www.androidfilehost.com/?fid=4349826312261760531

Thanks again!!!

 

[t436h05t]

This phone is becoming frustrating, bought the phone when it was on 31, rooted it, then ran the ota fixer. reserve.img is in data. Unroot via magisk, rebooted. Go to apply the OTA, downloads to a little more than half way and fails.... anyone have any ideas? Seems like it is the recovery which i installed the adb recover version,. I tried to restore the old one, doesnt seem to work - anyone have a stock recovery from 31?

FIXED ISSUE BY APPLYING STOCK RECOVERY 2X then it took the update ...

05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553051:ERROR:delta_performer.cc(522)] Unable to open ECC source partition recovery on slot B, file /dev/block/bootdevice/by-name/recovery_b: Invalid argument (22)
05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553106:ERROR:delta_performer.cc(1230)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553148:ERROR:delta_performer.cc(1235)] Expected: sha256|hex = 001B4315FE31C5A4F1C23D1B16A2C64F137950FF2C28CBC7A7BD85F3FCB6C987
05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553187:ERROR:delta_performer.cc(1238)] Calculated: sha256|hex = 9FF662AA7D1616A5CAB2E532839F6D41429D4214CF38012A4996D6228A806AF7
05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553228:ERROR:delta_performer.cc(1249)] Operation source (offset:size) in blocks: 0:1,15252:1
05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553274:ERROR:delta_performer.cc(1530)] source_fd != nullptr failed.
05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553323:ERROR:delta_performer.cc(305)] Failed to perform BROTLI_BSDIFF operation 848, which is the operation 0 in partition "recovery"
05-24 21:16:19.553 1349 1349 E update_engine: [0524/211619.553367:ERROR:download_action.cc(336)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing

 

[starcms]

This phone is becoming frustrating, bought the phone when it was on 31, rooted it, then ran the ota fixer. reserve.img is in data. Unroot via magisk, rebooted. Go to apply the OTA, downloads to a little more than half way and fails.... anyone have any ideas? Seems like it is the recovery which i installed the adb recover version,. I tried to restore the old one, doesnt seem to work - anyone have a stock recovery from 31?

FIXED ISSUE BY APPLYING STOCK RECOVERY 2X then it took the update ...

All of your partitions (except possibly persist and 2 modem efs partitions, but if those are messed up you'd know it lol) must be stock for the OTA to work. This includes recovery.

Just fyi, imo, you shouldn't be writing anything to your recovery (or any other partitions) in fastboot. Use "fastboot boot nameOfTWRPimage.img" or "fastboot boot nameOfStockModrecov.img" and backup/restore partitions using adb commands

I've learned quickly on this phone that fastboot flash causes nothing but bad news. Completely opposite coming from Nexus/pixel/essential phones. I shouldn't blame the phone. It's Android 10 coming stock on the phone. Combined with updates from T-Mobile instead of direct from OnePlus. And no fastboot full restore nor update packages with all the individual .img partitions!!! Only that damn MSM tool that wipes everything. I want to use the Open Beta for Android 11 damnit!

I'd recommend booting into twrp and backing up your persist and 2 efs modem images ASAP (they are called modemst1 and modemst2 I believe, if not, something very similar, no _a or _b). I wish any of the main root threads said that at the very top in huge print (or anywhere). Bad canary version of magisk wiped out my fingerprint reader about a week and a half ago, only a week after I got it...