edl VS nvidia-vaapi-driver

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.

For anyone wondering, I got hardware acceleration working (NVIDIA 1660 Super: h264, vp8, vp9, don't know why I can't get HEVC support currently) using the nvidia-driver-545 using the steps from nvidia-vaapi-driver to build from source (version: 0.0.11)

I don't think it's your fault and I don't think you're using the wrong browser.

> I should be working out the dependency story and compiling some driver from Github myself.

no, nvidia _should_ make it easier for people using the 3rd most popular desktop OS to use their hardware. It would make them more competitive against AMD and Intel, which both support hardware video decoding.

That's probably not going to happen, so the next best option is to install a package from the package manager [0]. There might be some kind of compilation needed, but in my experience that's rarely an issue (aside from time), especially if it's coming out of the package manager for a popular distribution.

> It's just not a real option for maybe 99% of PC users.

well, 99% of PC users with Nvidia hardware. It's an important distinction since this problem is specific to Nvidia. If the solution is to installing a package from the package manager, it's only as difficult as installing the browser in the first place.

I do agree there's some extra questions that may make things difficult, or unfamiliar for the vast majority of people, though. Like how is someone supposed to know they need the nvidia-vaapi-driver package anyway?

[0] - https://github.com/elFarto/nvidia-vaapi-driver#package-manag...

to be honest, pop os solved most of my problems except the hardware acceleration problem which seems like an issue with Nvidia. I am planning to try this soon. https://github.com/elFarto/nvidia-vaapi-driver/ as mentioned in the comments

RpmFusion only has v0.0.9 of nvidia-vaapi-driver although release v0.0.10 adds support for Nvidia drivers v535. https://github.com/elFarto/nvidia-vaapi-driver/releases/tag/v0.0.10

I do have one machine with the Firefox PPA rather than the snap, and that's because I've got an NVIDIA card in it and want to use an experimental library.

Note that as an nvidia gpu owner you need to do some extra backflips to make firefox use hardware decoding such as installing a custom vaapi-to-nvdec translation driver: https://github.com/elFarto/nvidia-vaapi-driver

General VDPAU vs VA-API video acceleration pains. Needing a community driver for imperfect VA-API support, that nvidia updates have broken multiple times.

Don't use VDPAU, this driver is much better: https://github.com/elFarto/nvidia-vaapi-driver