KAZUNA eTalk - App Guide & Discussion

It kept giving me a sahara fail error, so I used the verizon software upgrade assistant, and now my phone is bricked

ZTEGuy I had similar issues darth I didnt look into it much but if you resolve the issue please let me know

It seems to be turning on and functioning, just the screen keeps looping white except for a small strip which changes as the phone turns on. I have tried flashing it with both the prepaid and postpaid softwares. the Verizon software upgrade assistant tool fails to recognize the software version of the phone.

ZTEGuy Are you using a standalone version of QFIL, or the QPST one that Yeti posted?

I am using QPST

Did you install the Qualcomm Drivers?

(If you have another computer to try it on, that may be helpful. It took me 3 computers until I got it working - But I had a different error)

Yes I did install the drivers

ZTEGuy

Hey ZTE guy, before plugging in your phone to the USB cable try running QFIL as an administrator on your computer and then connect up the phone.

Biden2020prez
What are the benefits of flashing to the F119 firmware for an F019 phone? I'm currently using an F019 as a backup phone while I wait for a new Pixel Pro and i've become rather smitten with the classic flip phone design. I would love to be able to at the very least install slack and/or sync to google for my contacts so I can read messages sent to me by work colleagues.

drbeast The benefit is that the F119 has allowed adb

ZTEGuy

Yeah that's a pretty big benefit :xD

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.