edl VS Team-Win-Recovery-Project

Open up QFIL (which should have been installed as part of the QPST tool). Click "Configuration" -> "FireHose Configuration" and in the window which pops up change the "Device Type" to UFS as informed by the article here "https://www.ereaderpro.co.uk/en/blogs/news/e-ink-product-follow-up-boox-tab-mini-c-and-page-versus-previous-generation". The article indicates that the device uses UFS2.1 as it's storage protocol. It also indicates that the device uses a Qualcomm® Snapdragon™ 662. In order to properly program the chip we need an appropriate programmer which is `prog_firehose_life_ddr_patched.zip`. The driver to communicate with the Qualcomm chip was originally found in a git thread (https://github.com/bkerler/edl/issues/200) attached to a comment as `prog_firehose_life_ddr_patched.zip` here: https://github.com/bkerler/edl/files/7991604/prog_firehose_life_ddr_patched.zip. To use this change the "Select Build Type" to be "Flat Build" and then click "Browse" for the "Programmer Path" and point it to `prog_firehose_life_ddr_patched.zip`.

YMMV, but in my experience it works flawlessly.

If that fails there are chip specific tools you can use to read/write to the right partitions, such as the fantastic EDL tool for Qualcomm devices:

https://github.com/bkerler/edl

EDL is the offical protocol used by support to debug and reset your phone. Issuing the following command should reboot you into fastboot.

Sierrakeygen HOW-TO on Windows 1. Original information from https://github.com/bkerler/edl

As for tracking down the issue on your side, it would be a matter of setting up this and then creating a memory dump while in EDL mode. The "how to get logs out of this" part we'll have to figure out afterwards.

After flashed wrong abl from LG G7 to abl_a partition and reboot, my phone was bricked. No Flash mode nor fastboot, I was use paper clip and short to testpoint in mainboard, its recogized as QUSB_BULK_CID:0402_SN:XXXXXXXX. I can send hello packet to sahara (edl mode) and got these information when using EDL tools (https://github.com/bkerler/edl). Seem like Sony sake authencation and Secure boot prevented me load different loader to sahara, Is there anyway or who can find the correct firehose loader programmer file for this XZ2? :

I had this problem too, I find it simpler to use something like hirensboot CD (a windows live image) or an edl tool to directly flash the image from Linux, like this, first you'll need to decompress the image with this.

You might be able to use bkerlers edl to unbrick the phone. https://github.com/bkerler/edl

I did. Kinda funny that all the links in those search results are marked as linked. I tried every possible solution that I could find. Even this https://github.com/bkerler/edl but still no luck. Thanks for your reply though.

B is super important to me, so my phone right now is a OnePlus 7 Pro. It was one of the last models ever made that can still pass SafetyNet while rooted (due to being whitelisted for "basic" / non-hardware-backed attestation). Unfortunately now it's several versions out of date and will stay that way for the foreseeable future, on top of the fact that nobody's figured out how to lock the bootloader on a custom ROM, despite the fact that it'll get you back Widevine L1 keys (the 7 Pro doesn't erase them on bootloader unlock like most phones do).

This stopped mattering to me when something accidentally activated a "feature"[0] of TWRP that erased my device and the maintainers have so far been completely hostile to the notion of adding an option to disable that functionality.

Now I just use my phone because OxygenOS is great, the hardware mute switch is great, lack of camera cutout is great (fuck rounded corners though), and it has some serious flagship specs. Not an advertisement or anything, but this was $300 refurbished from Back Market.

[0]: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/...

If ya do care about it: your only hope will be using an tool like TWRP Recovery to backup that partition. And decrypt it using your pin/password during that process.

make sure your downloading stuff from the offical github page... ANYTHING ELSE IS FAKE MAGISK get twrp files at twrp.me and make sure your using a legit version of odin!!!

Was downloading TWRP images from official site https://twrp.me/, but non passed checksum and GPG verification. Tried for several devices.

Older builds of TWRP? https://twrp.me/

Link to the wrong TWRP. Looks like a backup/restore Android thing that is open source.

Find a way to unlock the phone so that you can install a custom recovery, like TWRP. LineageOS team will recommend their own LineageOS Recovery, but don't even bother with it. TWRP has a lot more useful features, and is more widely supported by XDA Developers, and most people in general know it. If your phone is already vendor unlocked, then that makes the next steps much easier. If I recall correctly, since your device is a Samsung, you might have to use Odin Launcher to get to the bootloader to unlock it and install TWRP. I'm not sure though, so don't quote me on it.

I would finish the work of relocking bootloader on rooted OOS 11 with working AVB but I lost interest after TWRP wiped all my data. The issue is still open and nobody is treating it seriously, so I'm 100% done messing with root.

Their official site is https://twrp.me/