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

davgros

yeti Thanks for all the info i installed the launcher but can't see it, how do i bring it up?
Thanks

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

Biden2020prez correct. porting the launcher might be a bigger headache then it's worth though.

here's the decompiled source for the launcher with a bit of makeup applied to it and the non-Verizon sim message nulled out. reassemble with your favorite apk compiler if you're into that

[Login to see the link]

Biden2020prez

yeti Thanks! I'm very excited to check it out. (Is it your version or the stock?)

Biden2020prez

Biden2020prez I really need the apk b/c the apk app I use on android doesn't open decompiled projects. (The apk compiler on pc had errors compiling, usually android works fine in those scenarios)

Biden2020prez

~~And More Importantly, did you ever backup /system or /system/priv-app or wherever the apps are saved on this phone. If so, please send it.~~
I had an eTalk without a battery, and with much heavenly assistance I flashed it to Kaz-f119! (I am ordering a battery)
can you send me any email: [Login to see the link] or post your email so we can communicate quicker?

ekjr

yeti not working for me

Biden2020prez

ekjr Welcome to Apps4Flip Forums!
I don't know what you mean by

ekjr not working for me

If you can explain your issue in more detail it will be a lot easier to help. Thanks!

ekjr

how do you get that pop up that says allow usb debuging

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)

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

QFIL says "no port available" when I try flashing the firmware on my phone

Biden2020prez

ZTEGuy Try powering off the phone and holding volume up when you plug in the USB. Let me know if it works.

ZTEGuy

It still says no port available, and does not let me press the download button

ZTEGuy

never mind, was just a bad cord. works fine now,

ZTEGuy

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

darth

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

ZTEGuy

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.

Biden2020prez

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

ZTEGuy

I am using QPST

Biden2020prez

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)

« Previous Page Next Page »