• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

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

Search This thread

eqroiueq

Member
Aug 27, 2017
30
4
You have an extremely old version of fastboot and adb installed. That's why it says command unknown. The version you have installed should not be used with this phone. Download the latest from here and simply unzip and replace files in your current adb/fastboot directory:

Done. Fastboot now will not even find the device.
Is that log file of the phone simply entering and then exiting EDL mode without issuing any commands from MSM tool? Or is that an actual log file after attempting a backup? To me, it really looks like the former.
That was the actual log file from the failed backup.
I now have a log file of a supposedly successful backup of persist (32 MB) and reserve1 (8 MB), reserve2 (16 MB), reserve3 (16 MB), reserve4 (16 MB). It follows:
ToolLog.txt said:
IA V1.0
FCL V1.0

========================================================
MetadataVersion=2,CryptVersion=1,m_bIsPackImage=1
Project Name: 19861
Image Version: hotdogg_13_A.01_210114
Skip SHA256 Check: No
HW CHK: No
RF CHK: No
PRJ CHK: No
MDL CHK: Yes
Tool version verified! (V5.0.17)
project 19861 not support boot mode feature
project 19861 enable fuse
MVL V1.2
[1] dwMajorVersion=6,dwMinorVersion=2,is_win7_system=0
Device Arrival: \\?\USB#VID_05C6&PID_9008#5&86f85b3&0&10#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
[1] Set device as UFS
[1] [CSerialCommHelper] No data in buffer to be sent 0
[1] [SP][193] Check cmd done status failed. 1
[1] [SP][206] Reset Sahara
[1] UFS Inquiry Command Output: SAMSUNG KLUEG8UHDB-C2D1 0400
[1] UFS info Vendor = samsung, TotalLogicalBlocks = 499892224
[1] EmmcSizeInGB = 238.367188, TotalLogicalBlocks = 499892224
[1] Memory size:
[1] HANDSET_TYPE_256G:
Device Remove: \\?\USB#VID_05C6&PID_9008#5&86f85b3&0&10#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
[1] [CSerialCommHelper] Buf: 0 (1002/1000)
[1] [CSerialCommHelper] Buf: 0 (1015/1000)
[1] [CSerialCommHelper] Buf: 0 (1015/1000)
Do I need all four reserve partitions?
If it's from after attempting a backup, looks like you have the wrong drivers installed for EDL mode. Search for instructions and proper EDL drivers for OnePlus devices.
The drivers I have I don't know how to identify, except by the file name, which I think might be the Windows Update ID? ( fe241eb3-d71f-4f86-9143-c6935c203e12_fba473728483260906ba044af3c063e309e6259d.cab ) I don't know how to tell whether there are any newer ones since I've only once seen any kind version number: 2.1.2.2, which is associated with the ones I have.

Unfortunately, I'm not allowed to completely uninstall ESET on this computer to test whether that helps.
I'm pretty fed up with this, and I'm probably just going to give up. I'll just unlock the bootloader and restore the persist.img that I got without knowing whether it's any good. If that doesn't fix the fingerprint sensor, I'll live without it. The one on my current/old phone has been broken in hardware for months anyway, so I'm used to it.
Sorry for the trouble and thanks for your help.
 

starcms

Senior Member
Done. Fastboot now will not even find the device.

Disconnect device, reboot PC, and try again. If no go, see below about getting proper drivers.

That was the actual log file from the failed backup.
I now have a log file of a supposedly successful backup of persist (32 MB) and reserve1 (8 MB), reserve2 (16 MB), reserve3 (16 MB), reserve4 (16 MB). It follows:

Do I need all four reserve partitions?

Okay, so you got a successful backup of persist.img? Okay, that's what you needed. Save it in at least 3 different places.

As for the 4 reserve partitions, I'm not sure why the MSM tool backs it up in 4 parts, but those are worthless as they can't be restored. If you still need a backup of reserve.img for OOS11 11.0.1.2, let me know and I'll post it for you.

The drivers I have I don't know how to identify, except by the file name, which I think might be the Windows Update ID? ( fe241eb3-d71f-4f86-9143-c6935c203e12_fba473728483260906ba044af3c063e309e6259d.cab ) I don't know how to tell whether there are any newer ones since I've only once seen any kind version number: 2.1.2.2, which is associated with the ones I have.

You can get the latest drivers from OnePlus's website. Just search. Don't get them from windows update!

Unfortunately, I'm not allowed to completely uninstall ESET on this computer to test whether that helps.
I'm pretty fed up with this, and I'm probably just going to give up. I'll just unlock the bootloader and restore the persist.img that I got without knowing whether it's any good. If that doesn't fix the fingerprint sensor, I'll live without it. The one on my current/old phone has been broken in hardware for months anyway, so I'm used to it.
Sorry for the trouble and thanks for your help.

Wait, I'm confused now, was your persist already corrupted before you just now recently backed it up using MSM Tool? Or is your FP sensor working fine now?

Is your FP sensor working now? If yes, then you're good, and if or when your FP stops working after unlocking bootloader, you can simply flash your backup of persist to fix it. No need to flash it immediately after unlocking bootloader, only when you get issues with FP sensor (or other sensors) not working.

As far as error 31, are you sure you have enough free space on C:\ ? When you chose only persist and reserve to backup, it most likely worked because you weren't trying to back up every single partition and had enough space. And before when u tried to backup all partitions, you probably had just enough room except for the 3 that failed.
 
Last edited:

eqroiueq

Member
Aug 27, 2017
30
4
Okay, so you got a successful backup of persist.img? Okay, that's what you needed. Save it in at least 3 different places.

As for the 4 reserve partitions, I'm not sure why the MSM tool backs it up in 4 parts, but those are worthless as they can't be restored. If you still need a backup of reserve.img for OOS11 11.0.1.2, let me know and I'll post it for you.
Yes, please post the reserve image for 11.0.1.2.
You can get the latest drivers from OnePlus's website. Just search. Don't get them from windows update!
Thanks. I was able to find them finally.
Wait, I'm confused now, was your persist already corrupted before you just now recently backed it up using MSM Tool? Or is your FP sensor working fine now?

Is your FP sensor working now? If yes, then you're good, and if or when your FP stops working after unlocking bootloader, you can simply flash your backup of persist to fix it. No need to flash it immediately after unlocking bootloader, only when you get issues with FP sensor (or other sensors) not working.
Sorry for the confusion. My FP sensor was working when I made the backup.
 

TI028

Member
Apr 29, 2021
16
1
Hello :)

I rolled back to Android 10 (42), turned off "Automatic System Update" via the developer menu, but at night the smartphone was updated to Android 11.

Tell me, how can I disable automatic system updates ?
 

ArvhFiend

New member
Sep 14, 2016
3
0
I need to ask if this OTA update issue also exists with the indian variant (HD101)? If so then can this tool fix it for HD1901 too? I'm currently on LineageOS right now and need to go back to stock because of the widevine L1 certification. Please reply!
 

starcms

Senior Member
I need to ask if this OTA update issue also exists with the indian variant (HD101)? If so then can this tool fix it for HD1901 too? I'm currently on LineageOS right now and need to go back to stock because of the widevine L1 certification. Please reply!

No, not at all. You are in the wrong forums. These are only for HD1925, the T-Mobile 7T Pro 5G McLaren. For your variant, view the regular OP7T Pro subforums (even if you have the international McLaren edition) for the questions, software and tools you need.
 

Machine318

Senior Member
Sep 30, 2015
127
46
Burlington
Have you applied the reserve.img before? If so use the uninstall in Magisk to completely remove root, reboot. Take the OTA. Reboot. See the other thread for the Magisk patched boot image, fastboot that and then direct install Magisk to your now stock image.
 
Have you applied the reserve.img before? If so use the uninstall in Magisk to completely remove root, reboot. Take the OTA. Reboot. See the other thread for the Magisk patched boot image, fastboot that and then direct install Magisk to your now stock image.
No, i haven't applied the reserve.img, I missed that before root and before the update to OOS 11.

Is there any other way to update ?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 22
    ntzrmtthihu777 said:
    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.
    8
    I've posted these in some other threads, but I guess I should post them here as well.

    Each ZIP is named according to the build your phone is currently one. For example, if you are on 10.0.31 and want to update to 10.0.35, download the 10.0.31 archive, after which time you should be able to accept the OTA. If you are currently on 10.0.34, download that archive.

    10.0.31 - https://www.androidfilehost.com/?fid=4349826312261762168
    10.0.34 - https://www.androidfilehost.com/?fid=4349826312261814735
    10.0.35 - https://www.androidfilehost.com/?fid=4349826312261819229
    5
    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
    3
    There's another update out today, 10.0.25, claiming big 5G improvements.
    3
    Hehe. Anywho, why you askin? you got a 10.0.16?
    Oh yeah, for sure. Don't know why I waited on unlocking and/or updating. Maybe I just never quite found the time? Only thing I got around to doing was getting SIM unlocked.

    I'm at work for the next 9 hours, but after that... Well, after that I'm willing to do whatever needs to be done to help out.