[General Questions and Answers] rrm.:
Not a new ROM, but a step forward. (TWRP & SuperSU)

(Edited: Removed all external links due to my newcomer status)

To be brief:

I have not found the stock ROM for the DOOGEE T5S, nor tried any new custom ROM to replace it.

I have managed to install a TWRP with SuperSU powers.

These instructions might help you clean up your current system.

Bonus: the recovery menu (TWRP) is multilingual.

Caveat emptor:

My stock ROM came with a nasty couple of Trojans(a) and other potential malware(b) embedded. The Trojans subscribed me to "premium" phone services, costing me some money. I went through the whole hassle in order to get rid of them.

If you have a DOOGEE T5S, your phone is probably infected too. Owners of other DOOGEE phones should beware. (c,d,e)

DISCLAIMER: The following instructions could seriously harm or brick your phone. I make no guarantees of any type, shape or form as to the end results. These operations WILL VOID YOUR WARRANTY.

What I did:

Last warning: during these operations I had to do a factory reset of my phone. I strongly recommend you BACKUP ALL YOUR DATA before you continue.

1] Install TWRP & root the phone (f)

* Download the required files:

- The TWRP image file here:

[Search the NEEROM dot COM website]

- The SuperSU patch file here:

[Search the NEEROM dot COM website]

* Unrar the TWRP image. Leave the SuperSU patch zipped.

* Enter fastboot mode.

Using ADB in terminal:

adb reboot bootloader

* Flash the TWRP image in the recovery partition.

fastboot flash recovery /path/to/twrp/image/recovery.img

(in my case fastboot requires root privileges, so sudo it.

* Reboot and enter in recovery mode.

In fasboot send the reboot system, but press Volume UP during reboot.

* Enter into TWRP and Install the patch "SuperSU 2.78-SR1"

Once in TWRP, ADB is again functional.

Load SuperSU patch to your sdcard:

adb push /path/to/your/patch/SuperSU_Pro_v2.78-SR1.zip /sdcard/

In the TWRP menu, go to "Install". Browse to the "sdcard" directory. Select the SuperSU patch and Install.

* Reboot to the system.

Beware: system will not start if you haven't installed the SuperSU patch. It will loop at startup, and won't progress beyond the startup logo.

2] Initial setup.

From factory reset, the phone will go through the first installation procedures. Follow the setup until your system logs on, and you can connect again to your phone via ADB.

3] Get rid of the malware.

* Disable the apps:

Without need of supercow powers:

- Enter an adb shell:

adb start-server

adb shell

Disable the apps:

In a normal ADB shell:

pm disable your.package.name.here

If you don't know the name of the packages, you can always get the full list with:

In your normal terminal (not adb):

adb shell 'pm list packages -f'

In an ADB shell:

pm list packages -f

* Remove the apps:

First try a normal removal. If they are system apps this will fail, but try anyways.

pm uninstall your.package.name.here

* Escalation to remove apps:

Now that the first try has failed, get supercow powers:

In the ADB shell:

su

(You should get a message on your phone telling you that ADB is requiring root privileges. Say OK)

Now your ADB console should read something like "root@xxxxx.whatever"

And we try again:

pm uninstall your.package.name.here

But we have a super hardcore app that fails to be removed with the normal supercow powers. So we step it up. (g)

pm uninstall -k --user 0 your.package.name.here

... SUCCESS!

But wait, the app is still there. Yes, you only removed it for root. So... lets do some overkilling:

Meanwhile:

Let's check the ID of the system user:

id system

In my phone "system" is 1000

So, here we go:

pm uninstall -k --user 1000 your.package.name.here

Your mileage may vary. Sometimes the first command does the trick, sometimes the app is still there.

Is it gone? Not always.

Can it creep out from the netherworld? Maybe. So, let's beat the dead horse.

* Silence the dead (h)

Just in case the app is still lurking, let's make it harder for it to creep up on us.

pm hide your.package.name.here

Great. Silent in its coffin.

But is the app still there? Sadly, yes. I looked around and the apps were still there, in a privilege data folder.

* Root it out (i)

This is an extreme measure. You can really harm yourself doing this, so... you have been warned.

At this stage, you should be using supercow powers. If you are not, brief recap:

adb shell
su

Now, the systems partition is read only, so you cannot remove the content there. So, to remove the files there, you have to remount it in read-write mode. Here we go:

mount -o rw,remount /system

Now, find the app directories you want to remove. In my case, the apps were in "/system/priv-app". So:

rm -rf /system/priv-app/YourAppFolder/

And, eventually, erase the associated data:

rm -rf /data/data/your.package.name.here

A read-write /system/ partition is not a good idea, so we reset as read-only:

mount -o ro,remount /system

[You might need this]

I don't remember if this is required. Maybe to be able to write to the recovery partition via fastboot...

adb shell setprop ro.secure 0

This voids the GUARANTEE. You have been warned (AGAIN).

----

(a) Found Trojan.Hiddad & Adware.Retsanvie. Probable carrier app: com.gangyun.beautysnap (aka com.android.snap).

(b) Antivirus programs tag the OTA program as potentially dangerous: com.fota.wirelessupdate

(c) [Some articles on DOOGEE and LEAGOO shipped with Trojans]

(d) [Some articles on DOOGEE and LEAGOO shipped with Trojans]

(e) [Some articles on DOOGEE and LEAGOO shipped with Trojans]

(f) [NEEDROM dot COM website]

(g) [ROMPROVIDER dot COM website]

(h) [Reddit Post]

(i) [ANDROID dot STACKEXCHANGE dot COM Post]