I'm not sure what I'm legally allowed to share while under an agreement with TAKUMI JAPAN 株式会社. Additionally I am not responsible for ANYTHING you choose to do with your device. If you choose to modify your device, you risk permanent damage, and most likely void your warranty. Working USB Debugging through ADB is in fact possible, under specific conditions. There is some limitation placed on the USB debugging authorization prompt on some firmwares. this limitation is present on the prepaid version's (KAZ-F019) software version F019_R031 but is not present on the postpaid unit (KAZ-F119) version F119_R024. It is possible to flash a prepaid KAZ-F019 to a postpaid KAZ-F119 if you can locate the firmware package this can be done using either the Qualcomm Flash Image Loader (QFIL) or through Verizon Software Upgrade Assistant and a bit of quick thinking during the download phase right before the device is "repaired". I can not guarantee that everything will work as expected after flashing your eTalk as the postpaid variant. They dont seem to have any meaningful differences between the two save for software version but you can never be too cautious. If you do decide to go this route, backup your IMEI, because recovering it is a real pain. My particular unit was purchased as "unlocked" and still detects my SIM correctly but your mileage my vary. Enabling Developer options and USB Debugging: Launch the Engineering Mode app by inputting the dialer code: *#*#825864#*#* Click on Developer Options, and toggle the category to make changes. Scroll down to USB Debugging and toggle it. If you have and ADB server running you should see your computers RSA fingerprint. You can select "Always allow..." and click OK. You now have working ADB access and can install any supported application. Note on application support: The eTalk seems to share common DNA with the LG Classic Flip so anything that runs on it should run on the eTalk as well. if you choose to install the Apps4Flip launcher choose the one for "LG Classic Flip" There is no restriction on the application's namespace or signature and I was able to load a wide variety of apps, though I was limited by the devices general hardware. The accessibility enabler app xxdeafgirl shared works like a charm, as does list launcher. Misc findings: QDLoader 9008 Mode - Hold Volume Up while plugging it into your PC. EDL Deep Flashing Cables work too. Recovery - Volume Up while booting (not much to see here) Fastboot - Volume Down while booting (or here for that matter) Treble Compatible Still working on getting a custom recovery working (hopeful), or unlocking the bootloader (less hopeful) but once we do, it should be possible to completely replace the version of Android with a custom one. Maybe even KaiOS... FM Radio I believe the FM Radio to be enabled across all eTalk models, we just need an app to utilize it. Factory Test Utility There is another factory test utility, this one baked into the boot image itself. It's accessible by holding both volume buttons while turning the device on. Nothing particularly interesting here. You might not even be able to reboot out of it. 2/10 would not recommend Wrap up: Hope you found this helpful or at least interesting. Let me know if any other mysteries pop up. Cheers, Dan

Super Impressive work, keep it up and thanks for contributing this!

bruh moment- etalk hosts the firmware https://kazuna.co.jp/dl_files/KAZ-F119/20190506R024_postpay_user_fuse.zip

And I bought a Cricket Debut Flip. I wanna get an ETalk and see what I can do, I bet this is another S-OFF device that can be flashed with EDL.PY EDL.PY download Also, that archive has a firehose.

now that the cat's out the bag, lets have some fun. fembycat they left the url for their firmware directory in a plaintext file. Almost feels like they wanted people to find it lol. xxdeafgirl yep EDL.py works great. System isn't ODEXed and the java isnt obfuscated so I've making some small quality of life tweaks, repacking the image and flashing it. Maybe we should make a Discord to pool our efforts? Edit: Here's a Magisk patched boot image to save everyone some trouble. Google Drive link

This is massive, Just ordered one and going to try to create some custom firmware mods for this group.

I've been in contact with TAKUMI for a bit, and am trying to secure the kernel sources (hence why I wasn't allowed to specify the firmware location). Once those are on lock, this might be the most open smart flip-phone to date. Also kinda hard to say outright but it's happened to me, The device has decent support on GSM carriers, and may already be networked unlocked. I bought a second eTalk off ebay, a postpaid model and when I popped my metro by t-mobile sim in and ran the Search networks tool, I was able to associate the device on Metro and have been using it as my daily driver for the last few days. Not sure if this applies to the prepaid as well, or maybe since this one was paid off It unlocked on it's own when I put in my sim.

Kernel sources are protected under the GPL, you should not have a hard time getting them. So far it is looking like the E-Talk is the most open modern flip phone on the market, I would love to dig deep and debloat it a bit to speed things up, that would be a huge improvement, but alas I can't find the time yet. Hopefully will have time soon.

[unknown] would all this be true for the eTalk from other brands (e.g. tcl freetel)?

lgexalter1 As far as I know, they are all the same device. If you're referring to the network unlock status, again take what I said with a grain of salt. It may have been a fluke or something specific to the postpaid variant (KAZ-F119). I frequently see the eTalk listed as being made by Freetel but I really think this is a mistake of some kind. Freetel does make flip phones for their home market (ex: the Musashi, and the Mode1 Retro), but I haven't found a significant link between the two. I've yet to see one turn up as a TCL though. I suppose it's possible that TCL manufactured the device for TAKUMI株式会社, but I don't think that's the case as the Alcatel GO FLIP V on verizon runs a very different fork of Android. Something much more inline with ZTE's latest offerings. The eTalk was definitely ODM'd by a Chinese company but outside of references to Wy, China Mobile and Borqs I have no idea who made this device. If we figure that out, we probably also solve who LG licensed their devices from.

KAZUNA eTalk - App Guide & Discussion

ZTEGuy

Yes I did install the drivers

drbeast

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.

ZTEGuy

drbeast The benefit is that the F119 has allowed adb

drbeast

ZTEGuy

Yeah that's a pretty big benefit :xD

drbeast

Hi friends,
I've been able to get my F019 connected via QPST to show the QDLoader 9008. I can even get the build type ready to go as well, but I'm not able to get the QCN backup to work.

I can see in the status it's saying, "Invalid SPC Code, ignored".

Curiously, 00000 is not working. Does anyone have any advice? I bought this over ebay awhile ago and it works well with my verizon sim on a prepaid account. Could it be the last 4 digits of my IMEI ?

Edit: are you guys using windows 10 or 11 for this? I'm wondering if there's some sort of driver conflict going on.

Biden2020prez

drbeast are you in the qfil app?

jake24

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

Biden2020prez

Has anyone mounted system as rw? How?

Biden2020prez

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.

snipsnip

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.

Biden2020prez

You must flash the firmware fembycat posted

snipsnip

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

Biden2020prez

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

aapost

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

FliphoneBochur

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

FliphoneBochur

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.

aapost

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

FliphoneBochur

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]

Biden2020prez

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.

aapost

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

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

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

FliphoneBochur

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

« Previous Page Next Page »