Search results

Same thing I said to the other guy. You've provided the to and from versions, but I need a logcat during an update attempt to tell you why this is failing. A 16->25 update should theoretically work, as they produced a 13->19 update later on.

Three things: 1. version you're on. 2. version its trying to update to. 3. logcat taken while trying to update. Otherwise we can't help figure out why its not working.

Don't know and won't know without a logcat during an update attempt.

[02-21 00:14:18.750 1300:1300 E/update_engine] [0221/001418.750800:ERROR:delta_performer.cc(522)] Unable to open ECC source partition abl on slot B, file /dev/block/bootdevice/by-name/abl_b: Invalid argument (22) [02-21 00:14:18.750 1300:1300 E/update_engine]...

Yeah but none of this info helps us solve your issue. This only shows that you're following directions. Something else is killing the ability for you to update, and a logcat during said update will tell us what it is. Also, what version are you on, and what version are you trying to update to?

You can't mount android 10's system,odm,vendor,product partitions as rw at all. They use a subset of the ext4 filesystem which lacks all write support, so its simply impossible technoligically.

Try to update while pulling a logcat of the phone. It will explain what is causing the update failure.

Even if you don't, you can more than likely just use the msm in this thread to just redo it from the start.

I may have a fix for this issue. Shot you a pm with a tg invite link. A similar issue occurs on the OnePlus 7t Pro 5g McLaren from T-Mobile (HD1925), in that unlocking kills OTA updates. We may be able to fix this issue on this phone in the same way.

Not as long as you unroot prior to taking it, and have not done any thing other than root. You can re-root after taking the ota.

There's a button that has them all listed. There's three versions. More or less, but there simply is no global firmware for us to convert to for this device (they could create one, I suppose). This tool will fix just about any sort of brick we may encounter during normal experimentation.

https://forum.xda-developers.com/7t-pro/how-to/op7tpro-tmo-5g-unbrick-tool-to-restore-t4043925 I'll send ya a pm.

Updates with new reserve.img.

Huh, can you do me a favor then. Can you run this command on your phone after relocking: adb shell stat /data/reserve/reserve.img adb shell stat du -h /data/reserve/reserve.img Basically I want to see if the relock-wipe kills the image as well. because if it does, apparently the only way to get...

Uh.... you may not have the right phone for this. Its for the t-mobile oneplus 7t pro mclaren 5g. We never had a 10.0.2 version on our phone. it came with 10.0.13 and had updates to 10.0.14 and 10.0.16 and 10.0.19.

There is no flash-all.bat.exe file. The flash-all.bat, what you mean, is inside the update.10.0.19.HD61CB.7z file, not the platform tools. You just use platform tools I provide if you don't have a newish set of adb/fastboot installed yourself.

Honestly no idea. I just tested that installation worked on my (soon to be returned at the time, now returned) OTA bricked 10.0.16 phone and had user LLStarks test on his. Other than the temp root used in order to replace the reserve.img I didn't do any root messing about, and my replacement is...

Honestly unsure about the relock. I know unlocking will nuke the userdata partition, but I don't know about the reverse. Someone else may have to give you the answer on this one.

Bit of a clarification. If you call lpunpack without any flags, it will extract {odm,product,system,vendor}_a.img properly without issue, but will create 'empty' 0 byte images for {odm,product,system,vendor}_b.img. In order to get the b-sides, you must call it again like so: ./lpunpack --slot=1...

Hehe. Anywho, why you askin? you got a 10.0.16?

Very. That, and beign willing to sacrifice their current setup (reserve.img can only be snatched just after a factory reset) Honestly, once you do this, and we're sure it works, you can just reroot and backup your own reserve.img after each update. Yep.

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.

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

Sweet, hopefully this gets up fairly quick. I have my old 7tpro I'd like to do the OTA test with if this is an old version.

Cool stuff man. On the assumption it is the exact right one for our device, what version does it restore the phone to? As far as I've read and can tell using an MSM tool on a device re-locks the bootloader, so unlocking would still OTA kill you. If its sufficiently early on in the OTA train I...

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.

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...

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.

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...

Already am, lol. We ended up getting 3-4 'android news sites' to the top of google search results on this, and I've been doing the tweets and the chats and the blogs. Not going to let up until we have a resolution to this problem.

False alarm guys. 10.0.12 guy apparently was given a frikken retail demo phone. Not our situation.

Hey, you. We have may, and emphasis on may, have a fix. Would you be willing to pop into our telegram chat and help us troubleshoot?

The file is reserve.img, not recovery.img ;)

You may want to put a warning/disclaimer on the first post that unlocking bl will prevent all further OTA updates from the phone for the moment.

If you rooted, you unlocked the bootloader. If you unlock the bootloader a file required for updates is erased, and you can't ever go back to full stock and get updates, until either tmo or oneplus step up and give us a full stock rom.

Well, it didn't kill a dummy reserve.img I put there. Perhaps it would kill a real one, but I'd rather not have anyone deliberately try that as that may cause some severe pain down the line. We know for a fact that unlocking will.

It does not. I believed it did due to prior postings elsewhere and the fact that before this device I never heard of any android device which has any file in /data survive a factory reset. I knew that unlocking the bootloader wiped /data, and that that killed the image needed for OTA updates, so...

Hey, before someone gets entirely too upset. Some of my original statements in this post were mistaken. I've since edited both the title and the contents (maintaining the original contents for the sake of not hiding said mistakes as if they've never happened) to be accurate with what I factually...

<Mod edit: Quoted post deleted> Rather vitriolic aren't you? Look, the factory/master reset figure-out was by someone else. I reposted it, along with the known fact that unlocking the bootloader does in fact kill this file (it even does so on non-tmobile oneplus 7t pro, but OnePlus is smart...

Yeah, and I'm talking about the T-Mobile variant as well, HD1925

The heck? I've never seen that ever before. 10.0.13HD61CB, 10.0.16HD61CB and 10.0.19HD61CB.

Nah. its a bit of both. OnePlus was stupid for putting 'reserve.img' inside userdata, but T-Mobile is even stupider for not implementing the fix non-TMO OnePlus devices use, which is to switch to full OTA updates.

Android Police picked up the story: https://twitter.com/AndroidPolice/status/1218982470822924289 https://www.androidpolice.com/2020/01/19/unlocking-the-bootloader-on-the-t-mobile-oneplus-7t-pro-5g-mclaren-breaks-your-ability-to-install-updates/

Hope so. honestly its just a case of bad design on OnePlus's part. What's the first thing the help desk going to tell you to do if your phone isn't working? Exactly, wipe /data. And now no updates for you.

No idea personally. Someone has mentioned something to that effect in the telegram chat.

No, I think you're good on those, as there is a full software package on the oneplus site you can use to restore. the HD1925 models do not, so we're screwed until something gets fixed/figured out.

TL;DR: don't unlock or erase userdata on this image, or you'll never get another update until OnePlus fixes this. https://forums.oneplus.com/threads/t-mobile-7t-pro-5g-usa-ota-10-0-19hd61cb.1172725/ https://www.reddit.com/r/tmobile/comments/eq4or6/security_disclosure_master_reset_procedure_on/

Note that these hashes may be deep dm-verity hashes not plain sha256 and so on.

Yeah. My understanding is that 19 installs over 13. I'm not one hindered percent sure though.

Think it won't work anyway. It checks hashes of the other side before applying, and if they don't match it can't apply the update (brotli diff format, not a full update.zip style update which just replaces everything).