Apps4Flip-AdminLevel 5 - Gold Elite Member
This is massive, Just ordered one and going to try to create some custom firmware mods for this group.
KAZUNA eTalk - App Guide & Discussion
yetiLevel 3 - Gold Member- Edited
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.
- Apps4Flip-AdminLevel 5 - Gold Elite Member
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.
- yetiLevel 3 - Gold Member
- Edited
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.
XxxdeafgirlLevel 4 - Platinum Member
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.
- yetiLevel 3 - Gold Member
- Edited
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).
XxxdeafgirlLevel 4 - Platinum Member
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.
- yetiLevel 3 - Gold Member
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. :/
darthLevel 6 - Platinum Elite Member
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)
- yetiLevel 3 - Gold Member
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.
- yetiLevel 3 - Gold Member
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
- darthLevel 6 - Platinum Elite Member
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).
- yetiLevel 3 - Gold Member
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.
- darthLevel 6 - Platinum Elite Member
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...
- yetiLevel 3 - Gold Member
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.
XxxdeafgirlLevel 4 - Platinum Member
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.
2 months later
- Edited
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.
- yetiLevel 3 - Gold Member
Oh good there is still some interest in this device.
FATANG 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?
I don't have this version in my archive, if possible I'd like to snag a backup of it from you.
The only build known to have working ADB access is the postpaid's F119_R024, but you can try dialing *#*#2016#*#* and clicking on the button that says 打开开发者选项 this enable developer options which you can access from the notifications while the device is plugged into a PC.
FATANG 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.
It's cool to know that at least the postpaid units are factory unlocked.
FATANG It takes a minute to get to this:
Menu>Tools & Settings>Phone Settings>Key shortcuts
Wow now I just feel stupid.
FATANG Neat.
I was working on a custom firmware but lost interest, but I still have the decompiled F1Launcher source if someone wanted it.
I gave up on getting the kernel source from TAKUMI and my Japanese isn't nearly good enough for me to write a GPL compliance letter.
I have been looking at the kernel source for the LG classic flip, and they are the same version and CAF release tag so I think I can get it to boot on the eTalk with a bit of tinkering, just not sure how many of the important bits will work without patches.
- Edited
yeti I don't have this version in my archive, if possible I'd like to snag a backup of it from you.
Sure, as soon as I figure out what I'm doing 
yeti but you can try dialing ##2016## and clicking on the button that says 打开开发者选项 this enable developer options which you can access from the notifications while the device is plugged into a PC.
This absolutely worked, what it does is auto-enables USB debugging. When you go to the notifications menu (Menu>Notifications) it allows you to "click to disable USB debugging" When you click it, it disables USB debugging and then automatically puts you into the developer options menu which is far more kino than most developer option menus.
It includes: Bluetooth HCI Snoop log and packet capture, a 3/6/12/24 hour memory log, Double password, Stay awake while charging (which includes while plugged into a PC based upon your USB settings), Bootloader unlock, Color Modes, Web View Impl, Automatic updates, Bluetooth and WiFi/WLAN options, and the standard Developer options of Running Services, Hardware, Drawing, and Debugging,
The only running services when OEM are:
Tools & settings, SimContacts, com.qti.diagservices, Kika keyboard, Kazuna Home, CellBroadcastReceiver, and com.qualcom.qcrilmsgtunnel service. There is no background processes even if you load a memory card and media and no bloatware that I can find running but it will not let you disable MyVerizon or Verizon Cloud except through "No background processes" under the Developer options.
There is an option for "Force allow apps on external" to "Make any app eligible to be written to external storage regardless of manifest values" which is going to be fun...
yeti I have been looking at the kernel source for the LG classic flip, and they are the same version and CAF release tag so I think I can get it to boot on the eTalk with a bit of tinkering, just not sure how many of the important bits will work without patches.
Honestly if there is a way to pull off the verizon software that would be all that is needed aside from visual tweaks per each users needs and an FM radio. The camera on this thing isn't even that bad.
I didn't have any 32 gb memory cards laying around so I ordered one so I can test what kinds of media I can get it to play and also another F119 so I can brick or fry one of these while tweaking it and not feel so bad.
yeti I was working on a custom firmware but lost interest
Legacy OS might be a valid option but I dunno if it's needed, this thing only used 20% of it's battery idling uncharged for 5 days.
yeti I gave up on getting the kernel source from TAKUMI and my Japanese isn't nearly good enough for me to write a GPL compliance letter.
So I dunno how you were doing this, but under Menu>Tools&Settings>About Phone>Kernel version it lists the following info that might help:
3.18.71-perf (gcc version 4.8 (GCC) )
kazuna1@ubuntu5 #1