• KAZUNA eTalk - App Guide & Discussion

lgexalter1 I installed it, but I didn't restart my computer. I just restarted my computer and I didn't get that whole long megillah, but after cmd said Device detected :) it just went to the next command input, and nothing showed up in my output folder. [Login to see the link] any suggestions?

    FliphoneBochur Hmm yes, it appears to be a driver issue with windows... On linux you can change some udev rules, but someone else with experience in getting phones/drivers working together on windows will have to assist with that one (I assume that would probably need to occur regardless of what program you used to interact with the phone in edl mode)

    So would anybody who knows how to work with that be able to help me with:

    FliphoneBochur Zadig says it reinstalled the driver, but it keeps disconnecting the device during installation, and when I manually reboot it into edl and plug it back in the driver is still listed as libusb0, not libusb-win32.

    ? [Login to see the link] any ideas?

    aapost

    aapost if they have an f019 hardware model, a firmware for an f019 would be preferable regardless of version.

    He already tried doing the one on Kazuna's site, and is still within his brick.

    aapost Running the edl rl command would pull the images without altering the phone, so there is no need to update or alter a phone that is working.

    true. I was saying that I've had many experiences with many of these devices and I think the issues happen when flashing newer devices with the older firmware's on Kazuna's site. By the way, there is also a benefit of flashing the f119 firmware (1. Its factory Unlocked 2. its working with adb). but i guess its worth a try for me to pull my firmware, but its also worth a try for yours. lets both upload it.

      FliphoneBochur what is the full output after running edl rl your_dump_folder_name --genxml --loader=path/to/prog_emmc_firehose_8909.mbn?

      make sure your current working directory has a folder you want the files to go in to and that you replace your_dump_folder_name with the name of the folder, and make sure the path after = on loader points to the location where you saved the firehose file prog_emmc_firehose_8909.mbn.

        aapost

        C:\Users\Admin\Desktop\edl-master>py edl rl "C:\Users\tzvib\Desktop\Yoni Test" --genxml --loader=prog_emmc_firehose_8909.mbn
        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 :)
        
        C:\Users\Admin\Desktop\edl-master>

        (I put the loader in the edl folder, just clarifying, and if I try pip install crypto, it outputs this:

        Requirement already satisfied: crypto in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (1.4.1)
        Requirement already satisfied: Naked in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from crypto) (0.1.32)
        Requirement already satisfied: shellescape in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from crypto) (3.8.1)
        Requirement already satisfied: requests in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from Naked->crypto) (2.28.2)
        Requirement already satisfied: pyyaml in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from Naked->crypto) (6.0)
        Requirement already satisfied: charset-normalizer<4,>=2 in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from requests->Naked->crypto) (3.0.1)
        Requirement already satisfied: idna<4,>=2.5 in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from requests->Naked->crypto) (3.4)
        Requirement already satisfied: urllib3<1.27,>=1.21.1 in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from requests->Naked->crypto) (1.26.14)
        Requirement already satisfied: certifi>=2017.4.17 in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from requests->Naked->crypto) (2022.12.7)

        Biden2020prez That's what I've been using the whole time.

          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'