edl VS archwiki

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.

Create the technical documentation of your project You can use any of the following options: * A wiki, like the ArchWiki that uses MediaWiki * Read the Docs, used by projects like Setuptools. Check Awesome Read the Docs for more examples. * Create a website * Create a blog, like the documentation of Blowfish, a theme for Hugo.

What would you expect to find in that repo? The underlying software for wiki.archlinux.org is mediawiki and that is not based on git.

Bookmark https://wiki.archlinux.org

https://wiki.archlinux.org/ please go and see here, this might help u

Usually i recommend linux mint for beginners but hyprland may be a little bit hard to install there. So maybe in your case the best option is an arch based system with a graphical installer. A lot of people here recommend endeavourOS. Download the iso, install it to a VM and take your first steps. Once you are a little bit familiar with it, you may try to set up dual boot and run it on bare metal. Take small steps, backup your data and read the arch wiki.

For reference: Arch Linux is at https://www.archlinux.org, wiki at https://wiki.archlinux.org, and the ISO at https://archlinux.org/download/. Supported install methods are here and here only. This subreddit supports archlinux.org exclusively. Join us!

-------------------------------------------- Hyprland Crash Report -------------------------------------------- I tried so hard, and got so far... Hyprland received signal 11 (Segmentation fault) Version: 0a78f6031c8fcc6773f136fccde3d560aaac239d Tag: v0.29.0 System info: System name: Linux Node name: nah Release: 6.4.12-arch1-1 Version: #1 SMP PREEMPT_DYNAMIC Thu, 24 Aug 2023 00:38:14 +0000 GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) os-release: NAME="Arch Linux" PRETTY_NAME="Arch Linux" ID=arch BUILD_ID=rolling ANSI_COLOR="38;2;23;147;209" HOME_URL="https://archlinux.org/" DOCUMENTATION_URL="https://wiki.archlinux.org/" SUPPORT_URL="https://bbs.archlinux.org/" BUG_REPORT_URL="https://bugs.archlinux.org/" PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/" LOGO=archlinux-logo Backtrace: #0 | Hyprland(_Z12getBacktracev+0x62) [0x55644d617522] ?? ??:0 #1 | Hyprland(_ZN13CrashReporter18createAndSaveCrashEi+0x42c) [0x55644d5f203c] ?? ??:0 #2 | Hyprland(_Z25handleUnrecoverableSignali+0x47) [0x55644d5893d7] ?? ??:0 #3 | /usr/lib/libc.so.6(+0x3e710) [0x7f350243e710] ?? ??:0 #4 | /usr/lib/libwlroots.so.12032(+0x516a2) [0x7f35030676a2] ?? ??:0 #5 | /usr/lib/libwlroots.so.12032(+0x4f659) [0x7f3503065659] ?? ??:0 #6 | /usr/lib/libwlroots.so.12032(+0x54d55) [0x7f350306ad55] ?? ??:0 #7 | /usr/lib/libwlroots.so.12032(+0x5689e) [0x7f350306c89e] ?? ??:0 #8 | /usr/lib/libwayland-server.so.0(wl_signal_emit_mutable+0x7e) [0x7f3502fcd01e] ?? ??:0 #9 | /usr/lib/libseat.so.1(+0x30ca) [0x7f3502a870ca] ?? ??:0 #10 | /usr/lib/libsystemd.so.0(+0x2a675) [0x7f350315c675] ?? ??:0 #11 | /usr/lib/libsystemd.so.0(+0x2a59b) [0x7f350315c59b] ?? ??:0 #12 | /usr/lib/libsystemd.so.0(+0x2a56d) [0x7f350315c56d] ?? ??:0 #13 | /usr/lib/libsystemd.so.0(+0x2a59b) [0x7f350315c59b] ?? ??:0 #14 | /usr/lib/libsystemd.so.0(+0x2a56d) [0x7f350315c56d] ?? ??:0 #15 | /usr/lib/libsystemd.so.0(+0x2a59b) [0x7f350315c59b] ?? ??:0 #16 | /usr/lib/libsystemd.so.0(+0x2a56d) [0x7f350315c56d] ?? ??:0 #17 | /usr/lib/libsystemd.so.0(+0x2a59b) [0x7f350315c59b] ?? ??:0 #18 | /usr/lib/libsystemd.so.0(+0x2a56d) [0x7f350315c56d] ?? ??:0 #19 | /usr/lib/libsystemd.so.0(+0x2a59b) [0x7f350315c59b] ?? ??:0 #20 | /usr/lib/libsystemd.so.0(+0x2a50b) [0x7f350315c50b] ?? ??:0 #21 | /usr/lib/libsystemd.so.0(+0x2a70f) [0x7f350315c70f] ?? ??:0 #22 | /usr/lib/libsystemd.so.0(+0x48268) [0x7f350317a268] ?? ??:0 #23 | /usr/lib/libsystemd.so.0(+0x4fce7) [0x7f3503181ce7] ?? ??:0 #24 | /usr/lib/libseat.so.1(+0x36de) [0x7f3502a876de] ?? ??:0 #25 | /usr/lib/libwlroots.so.12032(+0x4d127) [0x7f3503063127] ?? ??:0 #26 | /usr/lib/libwayland-server.so.0(wl_event_loop_dispatch+0xa2) [0x7f3502fceae2] ?? ??:0 #27 | /usr/lib/libwayland-server.so.0(wl_display_run+0x27) [0x7f3502fcf2d7] ?? ??:0 #28 | Hyprland(main+0x8d9) [0x55644d577dd9] ?? ??:0 #29 | /usr/lib/libc.so.6(+0x27cd0) [0x7f3502427cd0] ?? ??:0 #30 | /usr/lib/libc.so.6(__libc_start_main+0x8a) [0x7f3502427d8a] ?? ??:0 #31 | Hyprland(_start+0x25) [0x55644d586735] ?? ??:0 Log tail: [LOG] Callback 5564501935d0 -> 5564501935c8, Keyboard removed. [LOG] Destroyed keyboard 5564501934d0 [LOG] Callback 55644fd2f938 -> 55644fd2f930, Keyboard removed. [LOG] Callback 55644fd2f800 -> 55644fd2f7f8, Keyboard removed. [LOG] Callback 55644fd2f868 -> 55644fd2f860, Keyboard removed. [LOG] Callback 55644fd2f8d0 -> 55644fd2f8c8, Keyboard removed. [LOG] Destroyed keyboard 55644fd2f7d0 [LOG] Callback 556450074a38 -> 556450074a30, Keyboard removed. [LOG] Callback 556450074900 -> 5564500748f8, Keyboard removed. [LOG] Callback 556450074968 -> 556450074960, Keyboard removed. [LOG] Callback 5564500749d0 -> 5564500749c8, Keyboard removed. [LOG] Destroyed keyboard 5564500748d0 [LOG] Callback 5564500874f8 -> 5564500874f0, Mouse removed. [LOG] Callback 5564501cc9d8 -> 5564501cc9d0, Keyboard removed. [LOG] Callback 5564501cc8a0 -> 5564501cc898, Keyboard removed. [LOG] Callback 5564501cc908 -> 5564501cc900, Keyboard removed. [LOG] Callback 5564501cc970 -> 5564501cc968, Keyboard removed. [LOG] Destroyed keyboard 5564501cc870 [LOG] Callback 55644fcf59e8 -> 55644fcf59e0, Mouse removed. [LOG] Callback 5564500bf3f8 -> 5564500bf3f0, Keyboard removed. [LOG] Callback 5564500bf2c0 -> 5564500bf2b8, Keyboard removed. [LOG] Callback 5564500bf328 -> 5564500bf320, Keyboard removed. [LOG] Callback 5564500bf390 -> 5564500bf388, Keyboard removed. [LOG] Destroyed keyboard 5564500bf290 [LOG] Callback 55644f3bc2b8 -> 55644f3bc2b0, Mouse removed. [LOG] Callback 55645003b3a8 -> 55645003b3a0, Keyboard removed. [LOG] Callback 55645003b270 -> 55645003b268, Keyboard removed. [LOG] Callback 55645003b2d8 -> 55645003b2d0, Keyboard removed. [LOG] Callback 55645003b340 -> 55645003b338, Keyboard removed. [LOG] Destroyed keyboard 55645003b240 [LOG] Callback 55644ff5f058 -> 55644ff5f050, Mouse removed. [LOG] Callback 5564500e9108 -> 5564500e9100, Keyboard removed. [LOG] Callback 5564500e8fd0 -> 5564500e8fc8, Keyboard removed. [LOG] Callback 5564500e9038 -> 5564500e9030, Keyboard removed. [LOG] Callback 5564500e90a0 -> 5564500e9098, Keyboard removed. [LOG] Destroyed keyboard 5564500e8fa0 [LOG] Callback 556450206068 -> 556450206060, Keyboard removed. [LOG] Callback 556450205f30 -> 556450205f28, Keyboard removed. [LOG] Callback 556450205f98 -> 556450205f90, Keyboard removed. [LOG] Callback 556450206000 -> 556450205ff8, Keyboard removed. [LOG] Destroyed keyboard 556450205f00 [LOG] Callback 556450067b70 -> 556450067b68, SwitchDevice removed. [LOG] Callback 556450067b08 -> 556450067b00, SwitchDevice removed. [LOG] Callback 55644fe495e8 -> 55644fe495e0, Tablet removed. [LOG] Callback 55644fe49580 -> 55644fe49578, Tablet removed. [LOG] Callback 55644fe49518 -> 55644fe49510, Tablet removed. [LOG] Callback 55644fe494b0 -> 55644fe494a8, Tablet removed. [LOG] Callback 55644fe49448 -> 55644fe49440, Tablet removed. [LOG] Removed a tablet [LOG] Session got activated!

> spend hours on google to fix some crap

That's the Windows way. It's a bad fit for Linux, because there is no one true obsessively-backwards-compatible Linux.

The good news is we don't need it: Linux isn't a black box, so we don't need to guess or study its behavior. We can look it up instead. The goal here is to construct understanding from documentation, as opposed to deconstructing behavior from testing.

Some great starting points to get your bearings are:

- https://wiki.archlinux.org/

- https://wiki.gentoo.org/wiki/Main_Page

- man pages

Since this no support forum, r/linuxquestions would be better suited for your question (rule #1). The reddit situation is indeed sad. But there are other sources of information: Have a look at the Arch wiki, especially the pages regarding the Arch build system. If you need further guidance, ask at the EndeavourOS forum, the folks over there are always willing to help.