• KAZUNA eTalk - App Guide & Discussion

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

          2 months later

          Sorry for bringing up a sore topic, but has anybody had any success unbricking this phone or backing up the firmware?

            I think Kazuna may have something to do with the Punkt MP02. I see hints in the files

            2 months later

            FliphoneBochur i bricked one as well, but turns out it is not actually bricked. i tried swapping the mother board with a functional one of an older firmware and it did the same. i suspect the new hardware is not compatible with the older firmware. but the motherboard itself is not bricked.

              12 days later

              I've successfully filtered this device with my new android MDM. Unless I missed something, this phone could be one of the few flip phones that can be securely locked down without requiring any reflashing, if you go the MDM route.

              a month later

              Baruch Hashem, after 5 months of this phone bricked, with the help of [Login to see the link], we have managed to unbrick this phone! We did this by flashing the stock aboot, boot, system, and vendor partitions. You can download those [Login to see the link]. Here's how to do that in QFIL:

              I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE. PROCEED AT YOUR OWN RISK!

              If you bricked your Kazuna eTalk KAZ-F019 by flashing the stock partitions of the F119, you can attempt to unbrick your phone by following the steps below.

              1. Download and extract the partitions linked above.
              2. In QFIL, select Flat Build
              3. By programmer path, click Browse and select this phone's firehose (in the original firmware which you can find in earlier posts).
              4. Go to Tools > Partition Manager > OK
              5. Once you're in, select the aboot partition, right-click it, and select Manage Partition Data. MAKE SURE TO LEFT-CLICK (select) THE PARTITION YOU WANT TO EDIT BEFORE RIGHT-CLICKING IT! I have bricked a phone by not making sure the thing I was right-clicking was selected. (You can further make sure you're flashing to the right partition by checking in the Raw Data Manager popup and the file you are flashing.)
              6. I would recommend at this point that you backup these partitions from the phone before flashing the new ones. Just in case this doesn't work, you could get the phone back to its original bricked state (though I hope it does work). Go to the partition you want to backup, and press "Read Data" and wait until it finishes reading. Now, in file explorer, go to "%appdata%\Qualcomm\QFIL\". Go to the COMPORT folder with the number of the port you are currently using. QFIL will tell you which port you are using when you plug in the phone (it will say (COM_)). Within the folder, you will find a file that says readdata...bin. Rename it to the partition you're backing up (i.e. aboot.bin), so it's not confusing. I would recommend that you backup each partition one at a time. You can see a detailed explanation of backing up partitions with QFIL [Login to see the link]
              7. Now go back to the aboot's Raw Data Manager, click on Load Image, and select aboot.bin (from the partitions linked above)
              8. Repeat steps 5 & 6 for boot, system, and vendor

              Your phone should now be unbricked!

              pollofifo Hey, there! I am working with a bricked F119, and I would definitely appreciate the full QFIL backup you mentioned, if it's not too much trouble. Thanks!