KAZUNA eTalk - App Guide & Discussion

Can anyone help me disable the browser on the f119 version?

drbeast are you in the qfil app?

Has anyone mounted system as rw? How?

FATANG i think i know why they removed it in the newer software versions.
An exploit came out once to get A root shell from within that app.

Hi all, I recently received one of these from Verizon as part of their wave of replacements for old 3G phones. It's has a F119_R035 build number. I'm having a bit of trouble trying to get WebADB to connect to it. I used the ##2016## code to enable developer options, and in notifications "USB debugging connected. click to disable USB debugging" appears when the phone is connected via USB, but WebADB just gives the "Please authorize the connection on your device". I was able to bring up the Developer Options Menu once or twice after going to "click to disable USB debugging", but now I can't even get back into that. I just get a message saying "please enable developer options first", even though I already did that. I'm hoping I didn't mess something up and will need a factory reset to get it to work.

On a side note, there's something I noticed. While looking around the phone for a flashlight in the tools, I was disappointed that there wasn't one. Seems kind of weird that a standard feature like a flashlight isn't available on a phone with a working flash. However, there technically is a flashlight mode for it. After entering ##2016## , the menu that comes up has a manual test option where you test all of the phones features. One of those is a flashlight, and if you tap it and and don't select "Test Pass" or "Test Fail", it will probably stay on as long as you want.

Please excuse the low image quality.
I'm not sure why they didn't just make it easily accessible from the tools menu. Maybe they just didn't want the LED to burn out.

You must flash the firmware fembycat posted

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.

FliphoneBochur what model number and what version does the sticker have on it?

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?