• KAZUNA eTalk - App Guide & Discussion

FliphoneBochur

Open QFIL and connect your device to your computer
Select "Rawprogram0.xml" and "Patch0.xml" under "Programmer Path"
Click on "Load XML" button
Click on "Rawprogram0.xml" and then click on "Edit" button
Locate the files that you want to exclude from the backup and delete them from the "Rawprogram0.xml" file
Repeat step 5 for "Patch0.xml" file
Click on "Save" button
Click on "Download" button to start the firmware backup process

      FliphoneBochur try pip install pycryptodome, and for good measure pip install the rest of those listed in the requirements.txt

          aapost I tried pip install pylzma and I got a this megillah:

          C:\Users\Admin\Desktop\edl-master>pip install pylzma
Collecting pylzma
  Using cached pylzma-0.5.0.tar.gz (4.2 MB)
  Preparing metadata (setup.py) ... done
Building wheels for collected packages: pylzma
  Building wheel for pylzma (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py bdist_wheel did not run successfully.
  │ exit code: 1
  ╰─> [10 lines of output]
      running bdist_wheel
      running build
      running build_py
      creating build
      creating build\lib.win-amd64-cpython-311
      copying py7zlib.py -> build\lib.win-amd64-cpython-311
      running build_ext
      adding support for multithreaded compression
      building 'pylzma' extension
      error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for pylzma
  Running setup.py clean for pylzma
Failed to build pylzma
Installing collected packages: pylzma
  Running setup.py install for pylzma ... error
  error: subprocess-exited-with-error

  × Running setup.py install for pylzma did not run successfully.
  │ exit code: 1
  ╰─> [12 lines of output]
      running install
      C:\Users\Admin\AppData\Local\Programs\Python\Python311\Lib\site-packages\setuptools\command\install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
        warnings.warn(
      running build
      running build_py
      creating build
      creating build\lib.win-amd64-cpython-311
      copying py7zlib.py -> build\lib.win-amd64-cpython-311
      running build_ext
      adding support for multithreaded compression
      building 'pylzma' extension
      error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure

× Encountered error while trying to install package.
╰─> pylzma

note: This is an issue with the package mentioned above, not pip.
hint: See above for output from the failure.

          I tried running the backup command again and I got the exact same output as before:

          No module named 'Crypto'
          Qualcomm Sahara / Firehose Client V3.60 (c) B.Kerler 2018-2022.
          main - Using loader prog_emmc_firehose_8909.mbn ...
          main - Waiting for the device
          main - Device detected :)

              FliphoneBochur Yeah.. looks like some OS specific needs again, trying to compile something and it needs some tools for building installed. Try to see if you can find what it is asking for and then run the command again after installing it.

              The deprecation warning part should be ignore-able.

                FliphoneBochur you can also try running pip install pycryptodome first just to try to get that module message out of the way. You will likely still need you to go back and install the rest of them though.

                  FliphoneBochur error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": [Login to see the link]

                  if you install Microsoft Visual C++ 14.0 or greater, seems u wont have an issue, according to the error message.

                    lgexalter1 just to break that down,
                    the pip install -r requirements.txt does the same thing as installing them 1 by 1, but all at once. Sometimes it is clearer what module is having issues when you go 1 by 1.

                    The other command you can give a go, couldn't hurt, but I think it only loads the Loaders repository, and you already have the firehose set up and it seems to see it, so i think you are likely already good there.

                    git submodule update --init --recursive
                    Submodule 'Loaders' (https://github.com/bkerler/Loaders) registered for path 'Loaders'
                    Cloning into '/edl/Loaders'...
                    Submodule path 'Loaders': checked out 'b39741a9b96160755b963819d52dfe589f7a3a62'

                      I'm at the same stage [Login to see the link] is, except I own a F119 variant, and just tried reflashing it with kazuna's fw from their update endpoint.

                      The phone "is there" aka, if you manage to skip setup wizard and all that fuss, the underlying is working, it looks like they might have botched something in the file they are serving (or QFIL is doing some kind of damage) kernel wise, because to me, it just looks like a bad display driver.

                      If anyone has a F119 dump, even just boot.img only, I'd be grateful

                      I'm just waiting for someone to send anything. Anything that could get the phone to work. If it remains a brick it won't be the worst thing ever because I backed up his files and I have a spare phone, but I'd rather unbrick it.
                      If [Login to see the link], [Login to see the link], or anybody else who has the firmware would be able to send it, I'd really appreciate it. Thanks!

                      Meh, managed to restore F119 from a QFIL backup from the same device.
                      I've started messing with it because I manage to get the debugging opts, but not the authorization dialog, so it remains unauthorized.

                      Build no. F119_R035

                        pollofifo Many people had this issue, so if you can give an unbricking guide it would be amazing