edl VS mtkclient

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.

I went through a lot of trouble unlocking an old Xiaomi. mtkclient bypass methods do not work as a for all Xiaomi (or at least did not for my device). Thread: https://github.com/bkerler/mtkclient/issues/110

Have you tried mtkclient?

You're probably not going to be able to unlock the bootloader through official channels with that being a carrier phone. On the Motorola developer site you'll probably be told that your device doesn't qualify. If that's the case you can still unlock the bootloader using mtkclient. Check it out at https://github.com/bkerler/mtkclient There's easy enough installation instructions and and a step by step on how to unlock and root your mtk phone.

You could use emulators if they cover your needs. But you have mtkclient, however no warrants it will work.

I bet you have a mediatek chip (because Infinix, to my knowledge, never ever ever puts snapdragon SoCs). You could use mtkclient to root it, and I am pretty sure it already has the files necessary to obtain access to the phone.

That being said... try mtkclient. Can it work? Yes, I don't know of changes to the Oppo kernel regarding root perms. Will it work? No warrants.

Try mtkclient, should cover it. Watch out for your data.

Look - you're lucky to have a Mediatek chip. Use mtkclient - its' readme tells you on how to read memory. And actually has a rooting guide in the readme.md.

Should be at the root of the work directory