yashsingh1/xdaforums huggingface dataset:
[Oukitel (All phone models)] djmikxy:
Long micro usb on Oukitel k3

Please help.

This phone has a long micro usb cable. Why??!! There is no other cable plugged. Where are buy other cable, to be right? Or reduction from short micro usb to long micro usb? But to fit it and work on the phone. Something like this https://www.ebay.com/itm/Micro-USB-...hash=item361c255ca3:m:mcwdhFfvS9U665lFpdO-chA

But micro usb (short) to micro usb (long)

Thanks

Sorry for my english.
[Oukitel (All phone models)] h4m5t3r:
Here you cant get an complete (1m) micro-USB charging cable with a long micro-USB connector (9mm) that fits to the Oukitel K3: :cool:

https://www.aliexpress.com/item/Lon...32828940770.html?spm=a2g0s.9042311.0.0.yzrJWp
[Oukitel (All phone models)] h4m5t3r:
It looks like Oukitel is working on an OTA to firmware version V3.12!

On 4PDA user makc-best has posted the attached screenshot.

...it seems that the user has only received an FOTA-test, but it seems too that Oukitel is working on solving the problem with the malware.
[Oukitel (All phone models)] FennoManiac:
My phone did some updating, and so did the trojan :D

Two different trojans, on internal storage and on the sdcard :p

HOPEFULLY the V3.12 doesn't have this problem :rolleyes:
[Oukitel (All phone models)] jiwliwah:
i have long usb can connect OTG flash drive but can't connect usb to lan.

i have long usb can connect OTG flash drive.

but can't connect usb to lan.

i have fectory USB To Go. and i can connect flash drive.

Why i can't connect usb to lan.
[Oukitel (All phone models)] Alberto96:
It means that the kernel doesn't support USB LAN or you need to root the device in order to handle it. As far as i remember, Android doesn't support Wired LAN connections natively.
[Oukitel (All phone models)] zibibo:
Greetings to the whole forum, do you have any news for twrp??I tried to insert the twrp in the rom but nothing to do ?
[Oukitel (All phone models)] jackdam88:
Installation of TWRP (custom recovery) via FT (it is necessary to unlock the loader-depriving the warranty)

Custom recovery is a mode that allows not to boot into the system to backup (backup data) firmware, format various partitions, install custom firmware and patches.

1. Unlock the boot loader. As a result of unlocking you will get a completely clean phone: all user data and programs will be erased! In the "Settings" menu of the smartphone, activate the "For Developers" menu (usually by repeatedly clicking on the assembly number in the "About phone" tab) and select "Enable Factory Unlock" in the menu. Switch off the machine.

2. Put the device in the "fastboot" mode by pressing the key combination up and power from the switched off state, selecting the option "fastboot" from the appeared text menu of the bootloader.

3. Connect the smartphone cable to the USB port of the computer (in the Device Manager, the Android ADB Interface device should be displayed), install the necessary drivers, copy the necessary utilities to the computer: Attached file ADB.rar (1.44 MB)

, unzip them in a separate folder and open it on the command line.

4. At the command prompt, type:

fastboot devices

In this case, if everything is installed and properly connected, as a result of the command you will have to get the output of your smartphone's line:

fastboot 0123456789ABCDEF

5. Enter the command to unlock:

fastboot oem unlock

while the smartphone screen will prompt you to confirm the intention by pressing the volume up. Press the volume up.

At the command line, if the command is successful, you will see the following:

#

C: \ ADB> fastboot oem unlock

...

(bootloader) Start unlock flow

OKAY [43.920s]

finished. total time: 43.921s

IMPORTANT!! Do not miss this item! -> 6. Restart the smartphone with the command

fastboot reboot

Wait for the system to boot, then turn off the smartphone and again call the "fastboot" mode.

7. TWRP firmware. Copy the TWRP recovery.img image to the ADB utility folder. At the command prompt, type:

fastboot flash recovery.img

In this case, the recovery will be stitched into the memory of the smartphone.

8. Turn off the power of the smartphone while holding down the power button for a long time (~ 6 seconds). Call up the bootloader menu, select Recovery option and enter TWRP. Install the SuperSU patch and reboot into the system.

TWRP Recovery 3.1.1 by: jemmini

Thanks for the assembly jemmini

I ran it. I have the boot file to flash, but I do not know how to attach it
[Oukitel (All phone models)] zibibo:
Unfortunately I tried in all ways, unlocked the boot, used adb, but it does not work. Waiting for someone to implement the working twrp for this phone.
[Oukitel (All phone models)] jackdam88:
drive.google.com/open?id=11qLb_WVrS7aVZJkeLcbMD1B_lLKWpKEU[/url]

this twrp I used it and it works 100%
[Oukitel (All phone models)] zibibo:
I tried the file you suggested, but it does not work ...

"No command."

I had to rewrite the whole firmware.

I'll get a working and tested twrp, or maybe a good custom rom :(
[Oukitel (All phone models)] jackdam88:
Have you unlocked the boot?
[Oukitel (All phone models)] zibibo:
Yes Man.☹️??
[Oukitel (All phone models)] jackdam88:
strange, it worked for me
[Oukitel (All phone models)] zibibo:
It does not work, then unlocking the bootloader the imei disappears. ?
[Oukitel (All phone models)] jackdam88:
io ho seguito la guida da qui:

https://translate.googleusercontent...Jrhgefr56E8U50R5RFjzFRo0Kpcw8YQ#entry64353776
[Oukitel (All phone models)] zibibo:
Installed the twrp,installed supersu,result? without imei,the phone does not detect the sim. I had to re-lock the boot loader, and reinstall the rom because I could not rewrite the imei code .... This method does not work.

Mi dispiace, ma ho provato di tutto, e non va....... :rolleyes: :(:crying:
[Oukitel (All phone models)] Alberto96:
Guys, this is a known issue (boot unlock = imei gone), there isn't any real working solution available yet.
[Oukitel (All phone models)] zibibo:
Thanks Albe hopefully find a solution soon. It's a good phone but without root I do not need it, I do not know whether to wait, or send it back ... ?
[Oukitel (All phone models)] Alberto96:
Already tested lots of ways, no luck. The same issue is present on the DOOGEE BL7000 since they share the same software manufacturer.
[Oukitel (All phone models)] jackdam88:
Sorry, but following the guide what is the problem imei?
[Oukitel (All phone models)] zibibo:
Once you unlock the bootloader the imei code is no longer displayed ... and if you re-lock the phone, it will not start again, and wants to put the rom away
[Oukitel (All phone models)] jackdam88:
I do not know what to recommend, because I followed the guide I was successful installing the recovery jemini 3.1.1 is no problem of imei
[Oukitel (All phone models)] vyhulenahlavicka:
Jackdam88 your version of update is 3.11?
[Oukitel (All phone models)] FennoManiac:
Hey you phone rooting wizards! :o

Could you get the soundrecorder.apk file from the phone? I want to submit it to all antivirus companies I know. Maybe someone will take a closer look at it and be able to tell us what that damn trojan is doing, and what those other files it downloads do. :confused:
[Oukitel (All phone models)] jackdam88:
Yes

---------- Post added at 08:12 PM ---------- Previous post was at 08:11 PM ----------

I unfortunately deleted it ..
[Oukitel (All phone models)] John31415:
Please find link to file - .dropbox.com/s/m7ghyawg0drqoag/SoundRecorder.zip?dl=0

VirusTotal reports 18/61 engines find malware. I sent it to Comodo but received no reply. I also wrote to Oukitel and received nothing from them.

I've not found any sign of unusual activity nor have I seen any other files in the SoundRecorder folder which somebody reported.

Because I was aware of the malware reports I made sure that I did not run SoundRecorder. Could it be that it hasn't activated for this reason?

But for this problem, which has cost me a lot of time researching, and still not being confident to use it for anything needing security I'm really pleased with the phone, especially at it's low price.
[Oukitel (All phone models)] FennoManiac:
Thank you!

Just to confirm, from which firmware version this file is from? I'm assuming V3.11, since it is the latest?
[Oukitel (All phone models)] John31415:
That's correct, 3.11.
[Oukitel (All phone models)] FennoManiac:
Ps. I have not been able to get the file. I get this error. Could you try using some other service, like google drive or something like that :)

Error (429)

This link is temporarily disabled. The person who shared it hit their daily limit of traffic or downloads. Learn about traffic limits.

​
[Oukitel (All phone models)] jackdam88:
here is the procedure to install twrp on oukitel k3 ..

1 enable USB debugging on your phone, enable installation of unconsidered sources in settings and the USB malicious sources option from the developer options menu.

2 download the folder attached to the link and copy in the spflashtool folder the 2 files scatter and preload "https://drive.google.com/open?id=1yegxx6mrqztKKZ2JMTQOpMAJnWKyJ8gN"

3 open spflashtool and in the download screen in "scatter loading file" insert the file you just copied into the folder

connect the phone on to the PC

4 now several entries will have appeared, let the first 2 selected and make downloads, now with the phone connected turn it off and the download will concede in a short time

5 now unlock the boot from the fastboot using an adb terminal from the pc with the phone connected with the command "fastboot oem unlock" and give the date, give ok from the phone with the vol + and reboot with "fastboot reboot"

6 copy the recovery.img file into the directory of the android fastboot teminal program on the pc

7 come back in fastboot mode on the phone always connected to the PC, from terminal adb copy the recovery with the command "fastboot flash recovery recovery.img"

8 sending the phone in recovery you will have the twrp
[Oukitel (All phone models)] Alberto96:
Unlocking the bootloader will cause the baseband to die, and as a result the IMEI won't be detected.
[Oukitel (All phone models)] John31415:
It seems to be because I don't have enough posts here yet.

Below is part of a Google Drive link. Maybe you know how to complete the first part?

1Y7dpE5eyhv2b0ihVcPzr6j8bOC3frBe7

---------- Post added at 08:21 PM ---------- Previous post was at 07:59 PM ----------

It was a Dropbox problem after all. In case you can't find it from the above I'll try with the full link to see what happens.

https://drive.google.com/file/d/1Y7dpE5eyhv2b0ihVcPzr6j8bOC3frBe7/view
[Oukitel (All phone models)] cstuarty:
still looking for root on this cheap bus, but there might be light light at the end of the tunnel! theres talk of the phone getting android 8 , if this is the case they might get rid of the prize bootloader
[Oukitel (All phone models)] zibibo:
Guys maybe solve for the root...

https://www.movilesdualsim.com/tema/mds-twrp-3-1-1-0-koolnee-k1.189301/

---------- Post added at 03:09 AM ---------- Previous post was at 02:37 AM ----------

Guys maybe solve for the root...

https://www.movilesdualsim.com/tema/mds-twrp-3-1-1-0-koolnee-k1.189301/
[Oukitel (All phone models)] Y300-0100:
V3.12 avaliable here for download:

https://www.oukitel.com/latest-software-rom-for-all-oukitel-devices-48.html

[MENTION=2386505]Alberto96[/MENTION]

Is there any way to flash new firmware without loosing data? I hate to customize my phone again.

Thanks
[Oukitel (All phone models)] FennoManiac:
I just updated.

Unfortunately the Sound Recorder trojan is still there. First scan with the Malwarebytes, it found that sound recorder of course and two other pieces of malware, on internal storage and SD-card, in the cache folder of the sound recorder. :(
[Oukitel (All phone models)] krtx1:
Update

Pls. let me (us) know how to update - step by step instruction. On my K3 flashing the rom 3.12 is impossible at all.

Thanks a lot in advance
[Oukitel (All phone models)] Levered:
Does K3 will get Android Oreo soon, many device using MT6750T get android oreo now like Leagoo S9 and Cubot X18 Plus.?
[Oukitel (All phone models)] Alberto96:
You are confusing devices released with Oreo out of the box with those that require an update. Please wait for an official announcement from OUKITEL.
[Oukitel (All phone models)] Levered:
That's what i mean..:D:fingers-crossed:
[Oukitel (All phone models)] xtremegamer87:
So you are sure this recovery is right for Oukitel k3? Because it's written for the koolnee k1. And it is safe to unlock the bootloader? Or risk of losing imei as [MENTION=2386505]Alberto96[/MENTION] told? Thanks in advance :)
[Oukitel (All phone models)] firehell:
and the Malware in SoundRecorder?

What about the supposedly active malware that is reported to be in the Soundrecorder? Is this a serious issue? Or?
[Oukitel (All phone models)] FennoManiac:
It seems that uninstalling that app for current user disables that malware. But resetting the phone brings it back!

I am not 100% certain if this uninstalling trick works. So I'm also running F-secure Safe on my phone, and I haven't seen those pieces of malware on my phone in a good while. When it is uninstalled scanners can't see it either.

Link to a how to guide:

How to Uninstall Carrier/OEM Bloatware Without Root Access
[Oukitel (All phone models)] ilmervanhattem:
Why do you think so?
[Oukitel (All phone models)] zibibo:
I have seen that they are working on it, they have the same problem as our root ... ☹️ anyway, the rootless phone is not good, it consumes a lot of battery, it can be disconnected, it would take a custom rom, like the cdroid I had in the oukitel k6000 pro, it was perfect. ?
[Oukitel (All phone models)] firehell:
I need some urgent help from people who really know about security issues

My new Oukitel K3 is infected with the Trojan that others are reporting.

In fact Malwarebytes found 5x

Android/Trojan.Dropper.Agent.BLV

Android/Trojan.Clicker.DDL

Android/Trojan. Dropper.Agent.BLV (in other folder/place)

Android/Trojan.Clicker.DDL (in other folder/place)

Malwarebytes can remove these four Trojans

However, it also found:

Android/Trojan.Agent.AED

Which it CANNOT REMOVE because it is part of the system and in Sound Recorder

I first found this in Firmware version K3.V11 - but after just updating Firmware to K3.V12

I find all 5x Trojans once again!

(although I don’t understand why only Malwarebytes found these and Bitdefender and Kaspersky have not????)

So my help request:

Is it security sufficient to just:

Force Stop/Clear data/switch off “Draw over other apps”/switch off “Modify system settings” the inbuilt Sound Recorder (and download another from Play store)

OR:

Because Trojan still remains on phone (even if not using this Sound Recorder) it is still a security risk/threat ?

I still have just a couple of days to send this back to amazon, so really appreciate/need a fast answer to this.

Thanks a lot

(I fail to understand why some people find this Trojan on K3 and others don’t – but I have it – so really need to know if it is a risk/threat)

(Perhaps some have this K3 phone a while and can say if it is better to return it, or really worth keeping even with this problem?)

(Stubborn Trojan Killer - from Cheetah Mobile found nothing !?!)

Update: have decided to send it back - not interested in root - and otherwise security would seem to be a big risk

Users can comment on Doctor Web news items

Android/Trojan.Agent - Malwarebytes Labs

Remove Trojan.Agent
[Oukitel (All phone models)] zibibo:
Even I was undecided whether to keep it, or return it, but being a good phone, and using the phone as a spare and especially having paid only € 99 I think I will keep it.
[Oukitel (All phone models)] firehell:
Thanks Zibibo

I paid the same for mine, that is why I have even bothered considering keeping it - anymore and it would have gone back for sure - but with a low income there is not a whole lot of choice for me out there.

I returned it to factory state, but haven't really made up my mind what to do about it. Send it back - keep it?

It seems all these China phones have some Trojan Virus of one kind or another.

I haven't really tested it (K3) yet so can't say much about it - it just appears to be good, but?

just that damned Trojan? and how great is the risk?

so my mind asks: Is it worth the risk (when you don't have a whole lot of money for something else)?:confused:
[Oukitel (All phone models)] zibibo:
In the end we are all under control ... Then it depends on you, how worried you ... Then I'm confident, at least I hope that soon will come out the root for our k3 so you can install a custom firmware, and finally solve the various problems and bugs. ?
[Oukitel (All phone models)] firehell:
Update:

For a while now I have been in contact with Oukitel. It is a slow tedious contact, and a lot of language difficulty, but it is there. The latest news is that they have said they will try to remove this Trojan and leave Sound Recorder intact.

I will stay in contact and keep the pressure on and hope they will actually do this (which I guess means another Firmware update is the only possible way - but they are not fast - so?)

have to wait and see!

Update2:

They have said they will remove the Trojan infection but it will take time because they have to apply to Google for certification when they make changes (Sound Recorder) = wait and see
[Oukitel (All phone models)] zibibo:
Good news ... We wait, and see what happens, maybe in time comes out even the root ...
[Oukitel (All phone models)] roseibt:
No more trojans

So, here is my solution, that works for every phone btw...

As you said in principle chinese phones are not to be trusted, so first thing after malwarebytes antimalware to be installed is "no root firewall" by grey shirts. You can allow or deny any app using data transfer. Monitor the servers and check, if strange chinese adresses are used! Allow only sites you trust. Don´t let something like Sound Recorder use the net!!! What for anyway??? This is just to see, that indeed this app loads viruses in its cache.

Now the interesting part: I use the App "package disabler" from KunKunSoft to clean all the garbage Apps from my chinese devices. If I don´t need it, it drains only battery and I get rid of it. Normally the phone has to be rootet to remove system apps, but there is a workaroud which worked on my K3.

First, as I tried to root my K3, all the problems in this thread came up and I temporarily bricked the thing. At the start I had V3.03 on it. Trojan was there, but didn´t load others. Now I use V3.12. Trojan was there and tried loading others from the net (was stopped by the firewall ;) ))

BUT!!!:

If you have installed "Mini ADB and Fastboot" on your PC, you can give package disabler the rights to disable the Sound Recorder App. Not de-install, but disable it. Only drawback is, you have to temporarily remove all accounts from the phone.

When you install packet disabler, you get a web link exactly how to use the App without root.

Worked perfect for me. I disabled Sound Recorder and some bloating Google stuff. Malwarebytes Antimalware finds nothing now (after two weeks), and nothing is loaded in the sound recorder cache.

Enjoy!!!
[Oukitel (All phone models)] CA|\|ALLA:
Initial build Oukitel K3 (Coosea). Lineageos-15.1 Unofficial.

Full backup of partitions and efs before installing.

Initial build may 15 19:14:21 CEST 2018.

UNSTABLE.

Start boot = unknown // Currently I do not have the device

Working = unknown // to check the rom.

Not working = unknown // Report any bugs.

WARNING: I am not responsible for any damage you cause to your device with this rom/kernel.

search "Coosea" on androidfilehost to find and download the rom.
[Oukitel (All phone models)] zibibo:
How do you install this rom? ?Why if you use the Twrp you lose the imei, so from the internal memory I think it is not possible, or must be installed directly with the flash tool? I would like clarification on this.

Thank you!!!
[Oukitel (All phone models)] CA|\|ALLA:
Hello, this rom is installed from the twrp. The desirable thing is to install it from microSD, in case you have to format Data and Cache to perform the installation. I'm not sure that the imei is lost, one thing is that the phone radio does not work well and can not read the imei and another is that the imei is damaged. If it is the second case it is because the version of the twrp that is being used is not for that device and flashes the partitions of the rom in other partitions different from those that should.

I enclose installation script so you can see that it does not flash any of the partitions related to the radio.

assert(getprop("ro.product.device") == "k3" || getprop("ro.build.product") == "k3" ||

getprop("ro.product.device") == "K3" || getprop("ro.build.product") == "K3" || abort("E3004: This package is for device: k3,K3; this device is " + getprop("ro.product.device") + "."););

ui_print("Target: Oukitel/full_k3/k3:8.1.0/OPM2.171019.029.B1/unknow05151914:userdebug/test-keys");

ifelse(is_mounted("/system"), unmount("/system"));

package_extract_dir("install", "/tmp/install");

set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);

set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);

show_progress(0.750000, 0);

ui_print("Patching system image unconditionally...");

block_image_update("/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||

abort("E1001: Failed to update system image.");

show_progress(0.050000, 5);

package_extract_file("boot.img", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot");

show_progress(0.200000, 10);

set_progress(1.000000);
[Oukitel (All phone models)] zibibo:
I imagined it was via Twrp as with other custom rom ....

However, the fact remains that all those who tried to root the phone via the Twrp by Gemini after the boot loader was unlocked, the phone code disappeared in the phone.E if you rebooted the boot the phone came into bootloop, and you have to rewrite the rom.☹️
[Oukitel (All phone models)] CA|\|ALLA:
The bootloop occurs when the bootloader is unlocked or when the twrp is installed or when the root is installed? And the same question, when the imei is damaged? I ask because I do not have the device to do tests with it.
[Oukitel (All phone models)] zibibo:
If you read in the previous posts, you can see that the phone once run the root works, but no longer displays the imei code, so the network does not work, and there is not even the possibility to rewrite the imei tried with various tools .if then you go back to block the boot loader to restore my code, the phone enters boot loop.e and you have to rewrite the firmware via flash tool. I think it's the fault of the Twrp not suitable, or a block that they put in device.Second me it would take a new Twrp. I hope I was clear
[Oukitel (All phone models)] CA|\|ALLA:
Since yesterday I have built a recovery twrp from the sources. It is not a port of another. I do not know if it worked and it is done with ramdisk files of the original device and compiled kernel. I'm going to upload the version in case someone wants to try them. I will also make a version 2 modifying this version with the original kernel of the device recovery and upload it. I hope that one of the two works well.

To test them without installing:

$ fastboot boot recovery.img

To install:

$ fastboot flash recovery recovery.img

twrp V-1 >> androidfilehost.com/?w=files&flid=271829
[Oukitel (All phone models)] zibibo:
Unfortunately I will be out all week for work, so I do not have the chance to try it, but I hope that some forum user will do it ...

Thank you for your work :good: ;)