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

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

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

KAZUNA eTalk - App Guide & Discussion

Apps4Flip-Admin

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

fembycat

bruh moment- etalk hosts the firmware [Login to see the link]

yeti

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.
[Login to see the link]

darth

I have a KAZ-F019 and have been trying to flash the firmware that fembycat posted to get it to the KAZ-F119. I have been using QFIL but when I try downloading the firmware to the phone I get the Sahara Fail error. What is causing that? If I wanted to flash it using the Verizon Software Upgrade Assistant which one should I use? (It looks like they have a different one for each manufacturer but I couldnt find one for Kazuna)

xxdeafgirl

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
[Login to see the link]
Also, that archive has a firehose.

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

Apps4Flip-Admin

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

yeti

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.

FATANG

So I snagged one of these from ebay, NIB KAZ-F119

yeti but is not present on the postpaid unit (KAZ-F119) version F119_R024.

This is an eTalk post paid unit but the software version (build number) is F119_R030 and it's never been updated via Takumi nor Verizon. Any thoughts on this?

It lists:
Kernel version: 3.18.71-perf (gcc v4.8)
Hardware Version: F1_MB_1V2
Android Patch Level Dec 5, 2019
Android v 8.1.0

yeti Launch the Engineering Mode app by inputting the dialer code: ##825864##

This isn't working for me with the phone plugged in or not plugged in to my computer, even with a SIM in it (never a Verizon one). Is there another way to do this? I set it up as MTP under the >USB connection menu since the dialer code wouldn't work. Maybe it's build # specific?

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

Can confirm for the F119 T-mobile SIMs work, it also works with a Tello SIM and a Redpocket SIM (CDMA/GMST), they seem to be unlocked from the factory. The only snag I had was a need for an extra reboot after swapping SIMs. It goes a little wonky after recognizing the new SIMis different than the old one, but everything is fine after the 2nd boot.

yeti a cool hidden key shortcut settings menu I found.

It takes a minute to get to this:
Menu>Tools & Settings>Phone Settings>Key shortcuts

yeti I added in a background to the drawer to improve contrast and gave it a fresh coat of paint.

Neat.

Apps4Flip-Admin

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.

yeti

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.

xxdeafgirl

yeti LG didn't license their L125s from anywhere, it's based on a past smartphone platform and it's not an ODM phone like 80% of the other flip phones.

yeti

xxdeafgirl I figured that LG would do their manufacturing in house. I just find the software similarities, button layout and camera position curious when you compare them side by side. Perhaps the eTalk was lisenced from LG then.

I have a feeling at least the software base for both devices were sourced from same company, even if the actual product development happened internally.

Similarly to how both the Kyocera devices and the Schok devices run software derived from the same set of patches (I believe they originated from Borqs).

xxdeafgirl

Actually, most flip phone designs now are all based on each other visually but the internal layouts are gonna be different and will vary wildly from OEM to OEM even if they look similar outside.

The Schok flip looks interesting but $100? That's a lot for me, but if I can obtain one, expect greatness.

yeti

xxdeafgirl Yeah I see what you're saying now. I just compared the main boards and outside of the camera and speaker modules, not a whole lot matches up. :/

yeti

darth

Idk if you use this device with service or not, but you might want to backup your QCN first. It stores your IMEI and MAC addresses as well as a few other things that aren't easily recoverable. While the eTalk is on, plug it in and you should see it in QFIL as HS-USB Diagnostics 9091. Go to Tools -> QCN Backup Restore, choose where to make the backup and click Backup QCN.

1.
that's interesting. Which Sahara Fail error are you seeing?

Make sure that the firmware package is in a path without spaces (ex: D:\Firmware\20190506R024_postpay_user)

If you're using QFIL standalone, you might want to try installing the full QPST Suite. I had problems with the standalone versions.

These are the ones i'm using.
[Login to see the link]
[Login to see the link]

2.
The Verizon Software Upgrade Assistant is actually bundled with the device. If you turn the device off and plug it in, it will expose itself as an installer drive.

follow the steps on the tool, and right before it starts the repair, delete the filed in the firmware folder it unzipped on your drive and replace them with the one fembycat posted.

darth

yeti I used your QFIL from QPST and your drivers. It downloaded successfully but now my phone is in some sort of bootloop/bricked. When I power it up the screen turns white than blinks and goes black and repeats... Now when I plug it in to my computer it shows up as HS-USB Diagnostics 900E (COM24).

Biden2020prez

Oh. Great question, it can be confusing sometimes. If you have the Kaz-F019 model, it won't work. You need download:

yeti
[Login to see the link]
[Login to see the link]
[Login to see the link]

You need to install the Qualcomm Drivers and QPST, then open QFIL (just search qfil from start), plug in your phone, and flash the KAZ-F119 Firmware. You can probably find instructions by searching google for "How to flash new firmware with QFIL". However, if you are having issues, or it's too confusing, I'm happy to help out more.

Note: Doing this will delete all your phones data!

(If you have the KAZ-F119 model, you should be fine already. You can check by going to Settings > About Phone)

yeti

Here's a quick update on what I've been working on.

The launcher felt unfinished to me so I've been trying to improve the overall UX. I added in a background to the drawer to improve contrast and gave it a fresh coat of paint. Icons aren't 100% finished yet but I think they feel more appropriate for a basic phone.

The Verizon menu has been replaced with a Tweaks menu, that includes a shortcut to a little app drawer I'm working on and to a cool hidden key shortcut settings menu I found.

Here's a pic of that:

I'm also working on a simple flash-tool with GUI based on EDL.py that would allow a user to install a custom firmware package safely onto the eTalk without advanced knowledge. More on this later...

Cheers

Biden2020prez

yeti Bump. Does that mean the you have access to the full APK for the launcher (including the classes.dex)? Can anybody with an eTalk post the APK and I'll try to make a version for the LG phones. Thanks!

yeti

darth Well that doesn't sound good.

This is the link to the [Login to see the link]

Install it, reboot your pc and run it. It should be capable of detecting the device and switching it back into flashing mode.

if not, you'll need to either make or procure an EDL deep flashing cable.

darth

yeti If I plug on with holding volume up it goes into downloading mode. It just doesn't boot into any operating system when I try powering it on, even when I tried flashing the firmware again (again said it was successful). I have the ability to download to it just I am having issues with the results of the download...

yeti

darth That's very strange. You didn't alter any of the settings on QFIL did you?

Unless you have a hardware variant we haven't seen yet, the next most likely culprit could be some kind of corruption.

Here's the firmware for the KAZ-F019 prepaid [Login to see the link] you can try flashing that or try your luck with the Verizon Update tool.

darth

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

xxdeafgirl

This is absolutely golden! I don't have any money right now, but I might pick up one of these and if the BL can be force-unlocked, I might build some ROMs for it.