KAZUNA eTalk - App Guide & Discussion

aapost Thank you so much for answering!
Model #: KAZ-F019
I don't know which thing on the back is the version, so here's a picture of the thing:[Login to see the link]

FliphoneBochur I wish I had a good answer for you. But this happened to a bunch of guys from this forum, and Tag used to filter the phone, but stopped because this was happening. I am not sure what to try, but here is my suggestion. Plug in the powered off phone and it should show Verizon Software Upgrade Assistant. See if it can upgrade or repair your phone. That would be best.

Here is what I have gathered: It seems that phones already on newer versions are having issues with this. It might help if we can get a hold of a newer one and dump the firmware, but not sure. I am hoping in the near future to work on a way of kashering this phone without playing around too much with the firmware.

Maybe I'll try to update my phone to newest update then give you the firmware.

Thank you so much! I'll try the Software Upgrade Assistant & tell you what happens.

Biden2020prez And it doesn't seem like it will work... but try booting into recovery (either pwr+volume up or pwr+volume down). It would get to a screen that says no command. but it will probably just continue to boot loop.

FliphoneBochur Hmmm, I guess maybe the 019's don't list version... I only have the f119 r035 which would risk breaking yours even more... I didn't have any luck with the firmwares from the manufacture site, but backing up and restoring with edl was working good.. I would suggest trying to find a working f019 or someone with one who can do a full backup of theirs using edl. And at the same time, do a full edl backup of your broken phone so you can restore it to it's current state (in fact, practice backing up and restoring with EDL with the broken phone, it wont fix anything, but better to know the process at least works).

The result of each backup should be a file lists like this:
abootbak.bin cmnlibbak.bin devinfo.bin keymasterbak.bin modemst1.bin rawprogram0.xml sbl1.bin tzbak.bin
aboot.bin cmnlib.bin fsc.bin keymaster.bin modemst2.bin recovery.bin sec.bin tz.bin
apdp.bin config.bin fsg.bin keystore.bin oem.bin rpmbak.bin splash.bin userdata.bin
boot.bin DDR.bin gpt_backup0.bin misc.bin pad.bin rpm.bin ssd.bin vendor.bin
cache.bin devcfg.bin gpt_main0.bin modem.bin persist.bin sbl1bak.bin system.bin

If the file lists are different from the above, YMMV as far as results.. and I would only proceed if the list matches between the phones.

You would then take all the files from the working phone, EXCEPT, leave out:
cache.bin
modemst1.bin
modemst2.bin
persist.bin
userdata.bin

as these have the phone specific information (like imei) and you don't want to overwrite that on your phone.

You would then try to restore the working phones files (minus those above) to the broken phone and see what happens. If it doesn't work, you can then restore back to your current broken state.

Biden2020prez Software Upgrade Assistant doesn't work (like you said). Recovery mode isn't looping, but the screen is blank. Before I flashed the firmware (the 1st time) it said no command

aapost Thank you so much! Biden2020prez said he'll try to edl backup his working phone. Where does edl backup to?

aapost Also, edl as in [Login to see the link] ?

I forgot to mention, DO use the firehose from the manufacturers firmware files, that was the one good thing in there.

I would recommend the official edl from bkerler (the fork you listed was last updated 2019...)

backup command:
edl rl your_dump_folder_name --genxml --loader=path/to/prog_emmc_firehose_8909.mbn

restore command:
edl wl your_dump_folder_name --loader=path/to/prog_emmc_firehose_8909.mbn

aapost Thanks! I'll try to practice while I anxiously wait for [Login to see the link] 's firmware.

Biden2020prez The whole problem was caused by uploading a rom from the F119. Are you really sure it’ll work?

aapost When I run the backup command, I get this:
Traceback (most recent call last):
File "C:\Users\Admin\Desktop\edl-master\edl", line 130, in <module>
from docopt import docopt
ModuleNotFoundError: No module named 'docopt'

lgexalter1 thats assuming he has pip... otherwize download this script [Login to see the link] and run it, then run lgexalter1's command.

FliphoneBochur I am very much unsure it would work, but... you flashed the f019 and are still in a brick. I think you need to be flashing a newer firmware version, which can possibly be a f119. You are bricked already, so doesn't hurt to try. if that doesnt work, I will software update my f019 and give you that rom (even though id prefer not).

FliphoneBochur requirements.txt for edl lists:
wheel
pyusb>=1.1.0
pyserial>=3.4
docopt>=0.6.2
pylzma>=0.5.0
pycryptodome
lxml>=4.6.1
colorama
usb
capstone
keystone-engine

you might need to do a pip install for a few of those, and any others that pop up until the No module messages go away.

lgexalter1 Thanks! Now after connecting to edl, my computer spat all this back (sorry for posting the whole thing, I just don't know what's important):

Traceback (most recent call last):
  File "C:\Users\Admin\Desktop\edl-master\edl", line 391, in <module>
    base.run()
  File "C:\Users\Admin\Desktop\edl-master\edl", line 299, in run
    conninfo = self.doconnect(loop)
               ^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Admin\Desktop\edl-master\edl", line 193, in doconnect
    self.cdc.connected = self.cdc.connect(portname=self.portname)
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Admin\Desktop\edl-master\edlclient\Library\Connection\usblib.py", line 226, in connect
    self.configuration = self.device.get_active_configuration()
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Admin\AppData\Local\Programs\Python\Python311\Lib\site-packages\usb\core.py", line 921, in get_active_configuration
    return self._ctx.get_active_configuration(self)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Admin\AppData\Local\Programs\Python\Python311\Lib\site-packages\usb\core.py", line 113, in wrapper
    return f(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Admin\AppData\Local\Programs\Python\Python311\Lib\site-packages\usb\core.py", line 249, in get_active_configuration
    self.managed_open()
  File "C:\Users\Admin\AppData\Local\Programs\Python\Python311\Lib\site-packages\usb\core.py", line 113, in wrapper
    return f(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Admin\AppData\Local\Programs\Python\Python311\Lib\site-packages\usb\core.py", line 131, in managed_open
    self.handle = self.backend.open_device(self.dev)
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Admin\AppData\Local\Programs\Python\Python311\Lib\site-packages\usb\backend\libusb1.py", line 804, in open_device
    return _DeviceHandle(dev)
           ^^^^^^^^^^^^^^^^^^
  File "C:\Users\Admin\AppData\Local\Programs\Python\Python311\Lib\site-packages\usb\backend\libusb1.py", line 652, in __init__
    _check(_lib.libusb_open(self.devid, byref(self.handle)))
  File "C:\Users\Admin\AppData\Local\Programs\Python\Python311\Lib\site-packages\usb\backend\libusb1.py", line 600, in _check
    raise NotImplementedError(_strerror(ret))
NotImplementedError: Operation not supported or unimplemented on this platform

I don't know if this has anything to do with this long nonsense (to me), but 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.
What do I do about both of these?

aapost Thanks! That's exactly what I did

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

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.

I would recommend that the images you use be pulled using edl to assure compatibility with a push back using edl.

of course remembering to exclude those 5 files mentioned.

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?