• KAZUNA eTalk - App Guide & Discussion

Biden2020prez Hmm, I hadn't considered downgrading to a previous firmware. I guess I can give it a shot and hope for the best.

    I just remembered that a while back someone from tag told me they stopped doing etalk because some phones wouldn't turn on after.

    2 months later

    *#*#825864#*#* was moved to *#*#7465382019#*#* on the R035 version

    2 months later

    Somebody just gave me their phone to try to work with. I successfully installed the firmware, but now the phone screen just flashes when I turn it on. Does anybody know where I could get the Kaz-F019 firmware to try flashing that instead of the Kaz-F119? [Login to see the link] Where did you find the firmware?

    yeti they left the url for their firmware directory in a plaintext file.
    Almost feels like they wanted people to find it lol.

    I can't find the firmware anywhere. Could anybody help me? I really hope there's a way to fix this phone...

      UPDATE: I'm pretty sure I found the right one. The original link posted here was [Login to see the link], so I just changed /F119/ to /F019/ and in that link I found [Login to see the link]. So Baruch Hashem for that! Now I flashed that firmware, and the phone turns on, shows a white screen for about 2 seconds, turns off, and repeats. I HAVE NO CLUE HOW TO FIX THIS! Somebody please help me because this isn't my phone & I don't want to break it. If anybody has any way to revert the phone to the way it was before, please tell me. If anything involves factory resetting, it's no problem because Baruch Hashem I updated everything beforehand, but now I'm stuck in a loop of a flashing white screen. PLEASE HELP!

      P.S. What I learned from this is that if you're ever dealing with boot.img files / firmware flashing / edl / BE CAREFUL! If you're fiddling around with somebody else's phone, make sure they agree that you're not responsible if you break it.

        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

                      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

                        FliphoneBochur My phones are using lower firmware versions and I'd rather not update it. I think aapost should try sending his rom, as you already tried getting the f019 firmware from Kazuna's site, and couldn't boot. The f119 often works with the f019 as seen in the OP (I've done it myself).

                              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).