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

FliphoneBochur

lgexalter1 I installed it, but I didn't restart my computer. I just restarted my computer and I didn't get that whole long megillah, but after cmd said Device detected :) it just went to the next command input, and nothing showed up in my output folder. [Login to see the link] any suggestions?

aapost

FliphoneBochur what is the full output after running edl rl your_dump_folder_name --genxml --loader=path/to/prog_emmc_firehose_8909.mbn?

make sure your current working directory has a folder you want the files to go in to and that you replace your_dump_folder_name with the name of the folder, and make sure the path after = on loader points to the location where you saved the firehose file prog_emmc_firehose_8909.mbn.

aapost

FliphoneBochur Hmm yes, it appears to be a driver issue with windows... On linux you can change some udev rules, but someone else with experience in getting phones/drivers working together on windows will have to assist with that one (I assume that would probably need to occur regardless of what program you used to interact with the phone in edl mode)

FliphoneBochur

So would anybody who knows how to work with that be able to help me with:

FliphoneBochur Zadig says it reinstalled the driver, but it keeps disconnecting the device during installation, and when I manually reboot it into edl and plug it back in the driver is still listed as libusb0, not libusb-win32.

? [Login to see the link] any ideas?

Biden2020prez

aapost

aapost if they have an f019 hardware model, a firmware for an f019 would be preferable regardless of version.

He already tried doing the one on Kazuna's site, and is still within his brick.

aapost Running the edl rl command would pull the images without altering the phone, so there is no need to update or alter a phone that is working.

true. I was saying that I've had many experiences with many of these devices and I think the issues happen when flashing newer devices with the older firmware's on Kazuna's site. By the way, there is also a benefit of flashing the f119 firmware (1. Its factory Unlocked 2. its working with adb). but i guess its worth a try for me to pull my firmware, but its also worth a try for yours. lets both upload it.

FliphoneBochur

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

FliphoneBochur

aapost

C:\Users\Admin\Desktop\edl-master>py edl rl "C:\Users\tzvib\Desktop\Yoni Test" --genxml --loader=prog_emmc_firehose_8909.mbn
No module named 'Crypto'
Qualcomm Sahara / Firehose Client V3.60 (c) B.Kerler 2018-2022.
main - Using loader prog_emmc_firehose_8909.mbn ...
main - Waiting for the device
main - Device detected :)

C:\Users\Admin\Desktop\edl-master>

(I put the loader in the edl folder, just clarifying, and if I try pip install crypto, it outputs this:

Requirement already satisfied: crypto in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (1.4.1)
Requirement already satisfied: Naked in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from crypto) (0.1.32)
Requirement already satisfied: shellescape in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from crypto) (3.8.1)
Requirement already satisfied: requests in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from Naked->crypto) (2.28.2)
Requirement already satisfied: pyyaml in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from Naked->crypto) (6.0)
Requirement already satisfied: charset-normalizer<4,>=2 in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from requests->Naked->crypto) (3.0.1)
Requirement already satisfied: idna<4,>=2.5 in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from requests->Naked->crypto) (3.4)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from requests->Naked->crypto) (1.26.14)
Requirement already satisfied: certifi>=2017.4.17 in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from requests->Naked->crypto) (2022.12.7)

Biden2020prez That's what I've been using the whole time.

Biden2020prez

FliphoneBochur Use Bkerler's the one that lgexalter1 linked to. thats the source and its the best try.

Biden2020prez

FliphoneBochur you can also probably just use qfil if this is too hard, but this is better

aapost

FliphoneBochur try pip install pycryptodome, and for good measure pip install the rest of those listed in the requirements.txt

FliphoneBochur

Biden2020prez How do I backup in qfil? And what do you mean by better?

Biden2020prez

FliphoneBochur

Open QFIL and connect your device to your computer
Select "Rawprogram0.xml" and "Patch0.xml" under "Programmer Path"
Click on "Load XML" button
Click on "Rawprogram0.xml" and then click on "Edit" button
Locate the files that you want to exclude from the backup and delete them from the "Rawprogram0.xml" file
Repeat step 5 for "Patch0.xml" file
Click on "Save" button
Click on "Download" button to start the firmware backup process

FliphoneBochur

Biden2020prez Heh. Ironically, I feel like edl is simpler.

aapost

aapost excluding the >=numbers stuff, just the package names to the left

FliphoneBochur

aapost I tried pip install pylzma and I got a this megillah:

C:\Users\Admin\Desktop\edl-master>pip install pylzma
Collecting pylzma
  Using cached pylzma-0.5.0.tar.gz (4.2 MB)
  Preparing metadata (setup.py) ... done
Building wheels for collected packages: pylzma
  Building wheel for pylzma (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py bdist_wheel did not run successfully.
  │ exit code: 1
  ╰─> [10 lines of output]
      running bdist_wheel
      running build
      running build_py
      creating build
      creating build\lib.win-amd64-cpython-311
      copying py7zlib.py -> build\lib.win-amd64-cpython-311
      running build_ext
      adding support for multithreaded compression
      building 'pylzma' extension
      error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for pylzma
  Running setup.py clean for pylzma
Failed to build pylzma
Installing collected packages: pylzma
  Running setup.py install for pylzma ... error
  error: subprocess-exited-with-error

  × Running setup.py install for pylzma did not run successfully.
  │ exit code: 1
  ╰─> [12 lines of output]
      running install
      C:\Users\Admin\AppData\Local\Programs\Python\Python311\Lib\site-packages\setuptools\command\install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
        warnings.warn(
      running build
      running build_py
      creating build
      creating build\lib.win-amd64-cpython-311
      copying py7zlib.py -> build\lib.win-amd64-cpython-311
      running build_ext
      adding support for multithreaded compression
      building 'pylzma' extension
      error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure

× Encountered error while trying to install package.
╰─> pylzma

note: This is an issue with the package mentioned above, not pip.
hint: See above for output from the failure.

I tried running the backup command again and I got the exact same output as before:

No module named 'Crypto' Qualcomm Sahara / Firehose Client V3.60 (c) B.Kerler 2018-2022. main - Using loader prog_emmc_firehose_8909.mbn ... main - Waiting for the device main - Device detected :)

aapost

FliphoneBochur Yeah.. looks like some OS specific needs again, trying to compile something and it needs some tools for building installed. Try to see if you can find what it is asking for and then run the command again after installing it.

The deprecation warning part should be ignore-able.

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.

« Previous Page Next Page »