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

aapost

FliphoneBochur you can also try running pip install pycryptodome first just to try to get that module message out of the way. You will likely still need you to go back and install the rest of them though.

MXRJR

FliphoneBochur error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": [Login to see the link]

if you install Microsoft Visual C++ 14.0 or greater, seems u wont have an issue, according to the error message.

aapost

lgexalter1 just to break that down,
the pip install -r requirements.txt does the same thing as installing them 1 by 1, but all at once. Sometimes it is clearer what module is having issues when you go 1 by 1.

The other command you can give a go, couldn't hurt, but I think it only loads the Loaders repository, and you already have the firehose set up and it seems to see it, so i think you are likely already good there.

git submodule update --init --recursive Submodule 'Loaders' (https://github.com/bkerler/Loaders) registered for path 'Loaders' Cloning into '/edl/Loaders'... Submodule path 'Loaders': checked out 'b39741a9b96160755b963819d52dfe589f7a3a62'

FliphoneBochur

[Login to see the link] [Login to see the link] I got edl working now. Could one of you please send a firmware, so I could try it out? Thanks!

Biden2020prez

FliphoneBochur Okay Soon.

pollofifo

I'm at the same stage [Login to see the link] is, except I own a F119 variant, and just tried reflashing it with kazuna's fw from their update endpoint.

The phone "is there" aka, if you manage to skip setup wizard and all that fuss, the underlying is working, it looks like they might have botched something in the file they are serving (or QFIL is doing some kind of damage) kernel wise, because to me, it just looks like a bad display driver.

If anyone has a F119 dump, even just boot.img only, I'd be grateful

FliphoneBochur

I'm just waiting for someone to send anything. Anything that could get the phone to work. If it remains a brick it won't be the worst thing ever because I backed up his files and I have a spare phone, but I'd rather unbrick it.
If [Login to see the link], [Login to see the link], or anybody else who has the firmware would be able to send it, I'd really appreciate it. Thanks!

pollofifo

Meh, managed to restore F119 from a QFIL backup from the same device.
I've started messing with it because I manage to get the debugging opts, but not the authorization dialog, so it remains unauthorized.

Build no. F119_R035

FliphoneBochur

pollofifo Could you please send the firmware? Thanks!

Biden2020prez

pollofifo Many people had this issue, so if you can give an unbricking guide it would be amazing

Biden2020prez

FliphoneBochur sorry I'm being very slow.

FliphoneBochur

Biden2020prez No problem! Thank you for willing to help!

pollofifo

Biden2020prez I can just send a QFIL full backup, but it's from F119

FliphoneBochur

pollofifo Please do. It might work. Biden2020prez
Like he said, whoever sends something, I'll try. Thank you so much!

hube

pollofifo Hey, there! I am working with a bricked F119, and I would definitely appreciate the full QFIL backup you mentioned, if it's not too much trouble. Thanks!

Biden2020prez

FliphoneBochur Okay i will too sson, but maybe only after shabbos

FliphoneBochur

Sorry for bringing up a sore topic, but has anybody had any success unbricking this phone or backing up the firmware?

Biden2020prez

FliphoneBochur Hmm... Maybe I'll try again

keej123

FliphoneBochur i bricked one as well, but turns out it is not actually bricked. i tried swapping the mother board with a functional one of an older firmware and it did the same. i suspect the new hardware is not compatible with the older firmware. but the motherboard itself is not bricked.

Biden2020prez

I think Kazuna may have something to do with the Punkt MP02. I see hints in the files

nortforreal

I've successfully filtered this device with my new android MDM. Unless I missed something, this phone could be one of the few flip phones that can be securely locked down without requiring any reflashing, if you go the MDM route.

« Previous Page