yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] lsmsc:
Yes, this is the one i'm using. But it didn't work. Wiping the Phone wasn't a concern, as it was a fresh one anyway. :)

This! This is exactly what was wrong. Entering recovery directly after installing it via flash tool worked perfectly. Thanks!

So, I now have SuperSU installed. :)

What about TWRP? Do I have to flash it again every time i need it, or is there a way to keep it?
[Android Q&A, Help & Troubleshooting] moriel5:
Shouldn't it still be there?

I remember when I used to be on the stock firmware (around R9-R12), it had remained.
[Android Q&A, Help & Troubleshooting] Tzul:
I can't imagine that it wipes the system partition, otherwise Android would be gone. ;)

It should wipe userdata and maybe cache. Does it really wipe the SD card, too?

About TWRP remaining:

If you start TWRP for the first time, it should ask you whether or not you want to allow changes to the system partition. If you do allow changes at least, TWRP should remain.

Android has a simple mechanism that updates/restores the stock recovery, here's how it works:

When Android boots, the script /system/bin/install-recovery.sh gets executed at one point (used to be /system/etc/install-recovery.sh in older versions).

The default content of this script does the following:

Check if the current recovery partition matches the expected checksum.

If not, then use the "applypatch" command to flash the recovery partition with a new image, built on-the-fly from three components:

The current boot partition. Both boot and recovery have an individual copy of the Linux kernel, which is the biggest chunk of data in both files, so it makes sense to take the boot image and tweak a few things in order to "convert" it to the stock recovery.

A patch file, /system/recovery-from-boot.p, which will fix the main differences between boot and recovery.

A "bonus file", /system/etc/recovery-resource.dat, basically a zip file containing some data that would be inefficient to store in the patch file. Mostly png graphics used by the recovery.

The script checks the SHA1 checksums of both input and output (boot partition and the constructed recovery image). If there's a mismatch, or if any of the required files are missing, then the recovery cannot and will not be changed.

Now, if you install SuperSU to the system partition (the traditional way), it "hijacks" the install-recovery.sh script file to launch its own daemon (background service). SuperSU saves a copy of the original script as "install-recovery_original.sh", but does not run it. If you do a new "systemless" install for Android 6 and higher, SuperSU modifies the boot partition instead. So, either way, having SuperSU installed means no automatic overwrite of the recovery.

Even if you don't have SuperSU installed, every time you leave TWRP, it renders the install-recovery.sh script ineffective. It does so by renaming the patch file /system/recovery-from-boot.p to recovery-from-boot.bak! A simple solution that does not clash with what SuperSU does.
[Android Q&A, Help & Troubleshooting] moriel5:
Thanks, I did not research how this works out, since I generally modify /system in any case, so this helped me understand the predicament that others might be in.

And about fastboot oem-unlock wiping /system as well, I have checked this myself (the partition was completely empty afterwards when viewed from ADB), and had to reflash via SP Flashtool as a result.
[Android Q&A, Help & Troubleshooting] lsmsc:
Thanks for the explanation. :)
[Android Q&A, Help & Troubleshooting] gkotr:
I just download and run the official android 6 rom from doogee.cc

doogee.cc/download.php?ProId=53

just klik the dowload (the date on the site is not correct). and install with flash tool.

i do not try to root it yet.
[Android Q&A, Help & Troubleshooting] crazytiti:
Hey thank for the link.

I'm downloading it.

It's strange that the OTA update did not alert me about this new version ?

Does anyone else tried it ?
[Android Q&A, Help & Troubleshooting] Tzul:
I'm not surprised that this isn't distributed via OTA. Major updates like this rarely are for cheap Chinese phones.

I installed this Android 6 firmware yesterday and it appears to work flawlessly so far. The bugs that annoyed me in the Android 5.1 firmware are gone, at least.

I used TWRP to flash the latest SuperSU zip, and it automatically installed in systemless mode, just like it should. That means it modifies the boot image, and also disables verity, which allows further changes to the system partition. I could then install Xposed in the traditional system mode and it works just fine.

Here's a patched version of the bootloader that I made. It allows the use of "fastboot flash" and "fastboot boot" without having to go through the unlocking procedure (unlock could wipe your data, as [MENTION=5358804]moriel5[/MENTION] wrote).
[Android Q&A, Help & Troubleshooting] moriel5:
Actually, others before me have pointed the bootloader issue (I think perhaps [MENTION=7125933]Sam Nakamura[/MENTION]?).
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
No, it wasn't me :) happy to see that doogee kept its promise, sort of..

Even I don't use this phone anymore

Good luck guys:fingers-crossed:
[Android Q&A, Help & Troubleshooting] moriel5:
I am moving over to a Nexus 4, since I need a phone that I could call from (I would like to somehow repair the cellular antennae that I had broken by accident, though).

However, as a miniature tablet, my X5 Pro is still usable.
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
No, mine was perfectly fine.. :) I just had the opportunity to buy a used oneplus2 but in very good shape for only 135€ for the 64gb variant... Even I was really satisfied with the x5pro back in the days I thought it was a good future investment on a longer term & as I really have no use for 2 phones I sold it for a decent price..

I really enjoyed my start here at xda in this thread, so it's also a wonderful opportunity to say peace to you, especially [MENTION=5358804]moriel5[/MENTION]

See you guys hopefully elsewhere again :good:

Sry for being off topic!
[Android Q&A, Help & Troubleshooting] lucaviend:
the official 6.0 finally...lol

so, i want to try flashing the repack version by snowcat

http://www.needrom.com/download/official-android-6-0-x32/

but i still confused with the step

after flashing it we should wipe phone... its mean in twrp?
[Android Q&A, Help & Troubleshooting] zulfib:
Guys. I have purchased a new x5 Pro and it comes out the box with android 6. How do I get custom recovery on this? Looks from previous posts that adb commands does not work for twrp recovery. Don't want to end up with a brick.

I can post the new rom if I can change the recovery and backup if anyone is interested?
[Android Q&A, Help & Troubleshooting] crazytiti:
So i have flashed the snowcat repack 6, so far so good except 2 things :

- battery stats doesn't work (it's like the last 5.1 update which mess up some xml files) does it work for you ?

- i try to install the superSu from last page http://download.chainfire.eu/supersu-stable

it made it unable to boot : freeze on the android 6 doogee animation. I have to reflash the system to make it work again.

edit : the Bluetooth H-163 audio module that was disconnecting every 3seconds in 5.1 now work correctly ;)
[Android Q&A, Help & Troubleshooting] crazytiti:
Maybe flash the TWRP recovery.img from SP Flash Tool ?

Then at first boot press the vol+ button to go in recovery, because if it boot system it will erase recovery.

Edit : i juste check the build number and the snowcat repack android 6 is 20161122 but same kernel.
[Android Q&A, Help & Troubleshooting] zulfib:
My concern is the scatter file for this phone. Will it be the same as that published in first post? How do I verify it?
[Android Q&A, Help & Troubleshooting] moriel5:
Why shouldn't it? It's not like Doogee had suddenly changed the partition layout.

Just check the the text files' contents and MD5 hashes, they should be the same.
[Android Q&A, Help & Troubleshooting] zulfib:
Thanks for the reply. What I meant was how do I verify the Partition sizes on my phone. I only know of droidtools that could generate a scatter file, but this is not supported.
[Android Q&A, Help & Troubleshooting] moriel5:
You'll need the terminal for that, however I forget the command.

I'll search for it, but it may take time, since I don't always have that pleasure myself.
[Android Q&A, Help & Troubleshooting] zulfib:
Does the terminal imply that I'll need su? That is my ultimate goal after recovery.
[Android Q&A, Help & Troubleshooting] crazytiti:
I have checked the scatter file from sp flash tool from 5.1 R15 and the scatter file from the 6 repack : same

You can check partitions on unrooted phone with this app :

https://play.google.com/store/apps/details?id=com.cls.partition

After launch go to option / all partitions
[Android Q&A, Help & Troubleshooting] zulfib:
Update: TWRP installed on stock Android 6 using the most recent one from needrom and the accompamying SuperSu linked within the same post. Note ; the uploader has stated that it only works on Stock rom - which is what I am using.

Thanks guys for your help!
[Android Q&A, Help & Troubleshooting] Tzul:
I can confirm the battery stats issue.

Are you sure your phone froze after installing SuperSU? Maybe it just appeared to be frozen while still updating the apps in the background. When it freezes, it normally freezes before the boot animation even starts. And after the installation of SuperSU, the first boot can take 10 or more minutes.

I used the original Doogee ROM, not Snowcat's repack. Perhaps SuperSU clashed with some of the modifications he made...

The SP Flash Tool will actually do the verification for you. If you try to use it with a mismatched scatter file, it should complain and refuse to flash.
[Android Q&A, Help & Troubleshooting] crazytiti:
Ok I certainly not wait 10 minutes... maybe 5 maximum.

I will retry.
[Android Q&A, Help & Troubleshooting] lucaviend:
im a little bit confuse with the repack...

so...there is still no compatible superSu for this repack?
[Android Q&A, Help & Troubleshooting] crazytiti:
So i try 2 things :

- wait >25 minutes with the repack and Update super su 2.78 : frozen on doogee android 6 logo

- flash only boot and system from official android 6 rom : stuck at bootloader logo (so can't try the super su)

So i get back to boot and system from repack without SU
[Android Q&A, Help & Troubleshooting] moriel5:
I know that it would be essentially a system root, however did you try to install it manually to /system?

I realize that this could possibly soft-brick the device or do nothing at all, since it's not the intended behaviour, however, how about we attempt it?
[Android Q&A, Help & Troubleshooting] Tzul:
[MENTION=6023942]crazytiti[/MENTION] That is weird. Must be a conflict with Snowcat's repack then.

As I wrote before, flashing the official Doogee release (all partitions, not just boot and system), and then installing the SuperSU zip with TWRP definitely works.

Since the repack disabled verity according to the description, you should be able to install SuperSU in the traditional system mode. To do that, boot TWRP, go to Advanced, Terminal, and type this, followed by enter:

echo SYSTEMLESS=false>/cache/.supersu

Then, install the SuperSU zip via the Install menu.

The SuperSU installer will find the "/cache/.supersu" file you just created, read the line "SYSTEMLESS=false" from it. The installer defaults to SYSTEMLESS=true on Android 6, but this way you can override that behavior, and make SuperSU install to the system partition like in older Android versions.
[Android Q&A, Help & Troubleshooting] crazytiti:
I just try it : didn't work...
[Android Q&A, Help & Troubleshooting] moriel5:
Hmm, that is really odd.

What we need is a log in order to see where the problem may lie.
[Android Q&A, Help & Troubleshooting] crazytiti:
Yep !

but i don't know how to get the log when the phone isn't booting and the adb interface seems to not work at that time.
[Android Q&A, Help & Troubleshooting] moriel5:
For ADB to work, you need to first connect the phone to the PC and select "Always allow this PC" (or something like that, I forget the exact wording), and afterwards it should work.

Alternatively, there is a method via logcat, in which you can collect the log from the recovery, however I did not check how to do so.
[Android Q&A, Help & Troubleshooting] moriel5:
I can't really tell (as I am not, unfortunately, fluent enough in the inner workings of the system), however it seems, based upon your log, to be something related to the network (no idea what exactly).

I'm glad that things are working out for you, however it would seem that in the end you are not using the repack.

In other news, the whole spyware fiasco that has hit BLU, it would seem that Doogee uses the same OTA update system, so I recommend to uninstall, or at least do disable any packages that relate to the aforementioned system.

When I saw the images of the OTA app on BLU phones, I could tell that it was identical to the OTA app on Doogee phones.

I had forgotten to post this earlier, sorry about that.
[Android Q&A, Help & Troubleshooting] crazytiti:
working battery stats

Hello all,

i did the same thing as for R17 : i take the power_profile.xml file from Tzul (fix for R17) and put it into the framework-res.apk from android6 (using apk multi tool)

And now the battery stats are working.

Here is the modded framework-res.apk (don't forget to unzip it)

use TWRP file manager to put in place (in /system/framework)

Maybe Tzul could do an update.zip ? (i could do it if someone give me a simple how-to ^^)
[Android Q&A, Help & Troubleshooting] moriel5:
Once I have time, I'll upgrade my Doogee X5 Pro from SnowCat4PDA's old AOSP MM ROM, however I had already downloaded the modded framework-res.

About the update.zip, I'm not too fluent in the workings, however I think that you can take an existing update.zip, clean it, and place the modded framewor-res inside, according to the file hierarchy (meaning that you also create the folder that it goes in).

For good measure, perhaps you should take a look at the update-binary inside META-INF>google>android.
[Android Q&A, Help & Troubleshooting] lipippo:
Hello,

could some kind soul check if android auto is supported fully by this phone?

I mean, if it has the necessary hw encoder profile to connect to the head-unit in the car.

You don't need a head-unit compatible with android auto, it's enough to install the app and, if the phone is not compatible, it will tell you that the app works but it won't be able to connect to the car's screen.

The reason I ask is I have an homtom ht7 pro, same chipset, same memory, same resolution, in fact same everything as the x5 pro, it should work but it doesn't. Why? Because, even if it supports h264 hardware encoding, it's missing profile 4, which is the one android auto needs.

I'm asking if somebody could test it with the x5 pro because homtom simply says the phone is "not compatible" (duh!) but I think they're lying (e.g. they also say the ht7 pro is not compatible with android 6, while there's an official android 6 for the x5 pro), the mali t720 should be capable of supporting profile 4 and it's just a matter of providing a suitable kernel.

I originally asked the same question here and [MENTION=5358804]moriel5[/MENTION] suggested to ask also in this thread.
[Android Q&A, Help & Troubleshooting] crazytiti:
Hello,

i just install android auto from

https://play.google.com/store/apps/details?id=com.google.android.projection.gearhead&hl=fr

it has updated some others apps (gmaps music ...)

Seems to be working fine on latest official android 6 X5pro
[Android Q&A, Help & Troubleshooting] moriel5:
Another option is AutoMate, which is freemium (some features cost money.

I personally really like it, and it looks nearly identical to Android Auto (albeit, a slightly older version of it).
[Android Q&A, Help & Troubleshooting] lipippo:
But did it show the warning that it wouldn't connect to the car's screen or not?
[Android Q&A, Help & Troubleshooting] crazytiti:
I did not have any warning

See the recording.

[YOUTUBE]https://youtu.be/Kn_mz-5-wgg[/YOUTUBE]
[Android Q&A, Help & Troubleshooting] lipippo:
Would you be so kind to install hardware info and, in the codecs section, check the profiles supported by OMX.MTK.VIDEO.ENCODER.AVC?
[Android Q&A, Help & Troubleshooting] crazytiti:
Hardware info say ok
[Android Q&A, Help & Troubleshooting] lipippo:
OK, it's missing profile 4, hence it cannot connect to the in-dash display :(
[Android Q&A, Help & Troubleshooting] spitaleti:
Hello.

I am from Brazil, i have a doogee X5 (8Gb, not PRO) and need help.

I updated the rom to stock (it was with a custom), but now the phone no longer works, the backlight lights up, and the touch sound as well, but it has no image in android, recovery mode, or CWM.

I utilized the mt6580 flashtool, try a lot of diferents roms, try erase the bootloader, format, etc.

All roms has the same problem, only sound..

Can someone help me?
[Android Q&A, Help & Troubleshooting] moriel5:
When did the issues start?
[Android Q&A, Help & Troubleshooting] spitaleti:
After the installation of the stock rom.
[Android Q&A, Help & Troubleshooting] moriel5:
Are you sure that you had installed the Doogee X5 stock ROM?

Since the X5 Pro may have a different screen (I hadn't checked).

And just to verify, did your model come with 4 or 8 GB of storage, and with either 512MB or 1GB of RAM?

Since there were two models of the X5.
[Android Q&A, Help & Troubleshooting] spitaleti:
I downloaded three roms, one x5 v17, one x5 v13 and one custom ...

My specifications are:

"General

Brand	DOOGEE

Model	X5

Quantity	1Piece

Material	Plastic

Form Color	Black

Type	Brand New

Power Adapter	EU Plug

Housing Case Material	Plastic

Network

Network Type	2G , 3G

Band Details	2G: GSM 850/900/1800/1900MHz; 3G: WCDMA 850/1900/2100MHz

Data Transfer	GPRS , HSPA , EDGE

Network Conversation	One-Party Conversation Only

WLAN	Wi-Fi 802.11 b,g,n

SIM Card Type	Micro SIM

SIM Card Quantity	2

Network Standby	Dual Network Standby

GPS	Yes

Bluetooth Version	Bluetooth v4.0

System Operating Android 5.1

CPU Processor	MTK6580

CPU Core Quantity	Quad-Core

Storage

RAM	1GB

ROM	8GB

Available Memory	4.7GB

Memory Card	Yes

Max. Expansion Supported	32GB

Display

Touch Screen Type	IPS

Screen Resolution	1280*720

Screen Size ( inches)	5.0

Camera

Camera Pixel	5.0MP (SW 8.0MP)

Front Camera Pixels	2.0MP / SW 5.0MP

Flash	Yes

Auto Focus	Yes

Touch Focus	Yes

Power

Talk Time	680minutes

Standby Time	72Hour

Battery Capacity	2400mAh

Battery Type	Replacement

Other Features

features	Wi-Fi , GPS , FM , Bluetooth

Sensor	Light sensor , G-sensor , Proximity , Gesture

Waterproof Level	IPX0 (Not Protected)

I/O Interface	TF card slot , Micro USB , 3.5mm , SIM Slot

Radio Tuner	FM

Other Features	5.0" IPS HD + Dual Network Standby + Android 5.1 + 1GB RAM + 8GB ROM + Wi-Fi + GPS + OTA + 8.0MP camera + 5.0MP secondary camera + Gesture control + Wake Gesture + Xender + Quad-Core

Reference Websites	== Will this mobile phone work with a certain mobile carrier of yours? ==

Dimensions & Weight

Dimensions	5.63 in x 2.84 in x 0.35 in (14.3 cm x 7.22 cm x 0.88 cm)

Weight	4.38 oz (124.2 g)

"

(from the order history)

But even CWM has the same problem :\
[Android Q&A, Help & Troubleshooting] moriel5:
Did you download them from NeedROM?

Since I can't tell what is the source of the issue.
[Android Q&A, Help & Troubleshooting] spitaleti:
yes, i download form needrom
[Android Q&A, Help & Troubleshooting] moriel5:
Hmm, strange.

What is this MT6580 Flashtool?
[Android Q&A, Help & Troubleshooting] moriel5:
News: SnowCat4PDA has built version 7.1.1 for the Doogee X5 Pro, and will release it soon.

In other news, he is releasing the stable verion of version 7.0 soon.

And there is a noGAPPS version of 6.0 now, with the same bugs as a cleaned GAPPS version.

I am trying to convince him to create noGAPPS versions of his ROMs, and I hope that there are others that will join me.

If required, I am willing to provide him a box (that he can use via SSH) to build them.

If others chime in, we may be able to provide something better than my i3-540 buildserver.
[Android Q&A, Help & Troubleshooting] lucaviend:
i tested snowcat 7.1.1 its flawless

still buggy with the hotspot, except that everything is perfect..

anyway anyone have a miravision for stockrom 6.0??
[Android Q&A, Help & Troubleshooting] XeNitro:
Has anyone managed to root the Doogee X5 Pro running Android 6.0

I've tried several times, non of the one-click roots work and installing TWRP just resulted in 'invalid command' or won't boot into recovery and will reboot into normal

Thanks XeNitro
[Android Q&A, Help & Troubleshooting] crazytiti:
i have success with official 6 rom and TWRP & super su 2.78 r1 from this link

https://www.needrom.com/download/twrp-recovery/
[Android Q&A, Help & Troubleshooting] moriel5:
You do realize that the official 6.0 has preinstalled malware and spyware?

SnowCat4PDA's AOSP 7.1.1 also supports (I think, I had not yet verified this) the double tap to wake gesture (perhaps SnowCat4PDA's new app, or Kernel Adiutor is required to use it, though).

And recently, I had not yet posted this, as I still need to succesfully flash it myself, on 4PDA, several LOS14.1 (on 7.1.1) ROMs have been released.
[Android Q&A, Help & Troubleshooting] crazytiti:
Can you be more specific about which apps are malware/spyware ?

I've try at first the snowcat 6 but at that time it wasn't very stable and couldn't boot on my phone.
[Android Q&A, Help & Troubleshooting] moriel5:
Some of the preinstalled apps, such as "Xender", however I forget the precise list.

Also, the updater is the same one the BLU used to use, that caused the fiasco a few months back.
[Android Q&A, Help & Troubleshooting] crazytiti:
Ok, xender is one of the first apps that i remove ;)

Concerning the updater i have understand that it's more a leak of personal data than something that will annoye the user directly (like unwanted advertising pop up)

Am i right ?
[Android Q&A, Help & Troubleshooting] moriel5:
Yes, since the updater is spyware (adups)..

This post is a bit old, however it contains some of the information regarding this:

http://www.androidpolice.com/2016/1...-phones-including-blu-devices-sold-in-the-us/

Ever since, BLU had moved over to Google's official updater.
[Android Q&A, Help & Troubleshooting] crazytiti:
i remember having search on my device for the two spy package :

com.adups.fota, com.adups.fota.sysoper

I cannot find them so i believe my rom is not contaminated.

(i search in /data/data)
[Android Q&A, Help & Troubleshooting] moriel5:
I thought that Adups did not put their name in the package name, perhaps I was mistaken.
[Android Q&A, Help & Troubleshooting] divisha:
gretel

friends i have a query, i want to buy a big battery phone in good price for my daughter so suggest me which is best Doogee BL7000 or Gretel GT6000, i like gretel because this phone price only $95 and come with 6000mAh battery
[Android Q&A, Help & Troubleshooting] zef1skull:
just use kingroot 4.6.2 if u use doogee x5pro original stockrom if u using custom its kidda hard to take it so i try go find which one can root it after flash custom rom android nougat
[Android Q&A, Help & Troubleshooting] Cr4z33:
Can these files (root & TWRP) be applied also to other Doogee phones like i.e the X10?

I ask because at today I could find no solution yet.
[Android Q&A, Help & Troubleshooting] crazytiti:
certainly not

these are very specific files for one model of phone.
[Android Q&A, Help & Troubleshooting] Cr4z33:
OK thanks.
[Android Q&A, Help & Troubleshooting] xe7um:
Can somebody recommend me a custom ROM good enough for daily usage that I could use instead of 6.0 (R16) stock ROM?. I've had no success with SnowcatPDA 7.1.1 (bootloop)
[Android Q&A, Help & Troubleshooting] xe7um:
I suspect there are X5 pro devices incompatible with SnowcatPDA 7.1.1 (hence the bootloop). Can somebody confirm this?