yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] moriel5:
To say the the truth, this has been discussed a few times already, I forget how many times, and in which threads (there are 3 threads here at XDA devoted to the Doogie X5 Pro, I'll post them in a few moments if it's possible from XDA Labs).

The chipset itself is MT6735P, you can open up (as in, expose the motherboard) the phone and see, and Doogie themselves say this.

---------- Post added at 10:11 PM ---------- Previous post was at 10:07 PM ----------

Here they are:

http://xdaforums.com/general/device...on/review-doogee-x5-pro-85-best-buy-t3230576/

http://xdaforums.com/general/general/doogee-x5-pro-volume-boost-headphone-t3245887

And the current one.
[Android Q&A, Help & Troubleshooting] ImJamIN:
Hi moriel5,

Can you post the commands to flash via fastboot?

Thank you

And what's about install viper atmos from TWRP? Is it ok for x5 pro?
[Android Q&A, Help & Troubleshooting] moriel5:
You can use the official Google USB Drivers for this, you just have to install them manually.

fastboot flash recovery (replace with name of file).img

From TWRP just flash SuperSU.

That's it.

I'm not sure since:

1. I don't remember which one I tried which failed.

2. I'm not using the stock rom anymore, I'm using SnowCatPDA's vanilla AOSP marshmallow, at version 6.0.
[Android Q&A, Help & Troubleshooting] ImJamIN:
Hi,

I have this error :

Unknown partition 'recovery.img'

Error : cannot determine image filename for' recovery.img '

I'm on r14 and I'm try to install TWRP 2.8.7.3
[Android Q&A, Help & Troubleshooting] moriel5:
And the name of the file is recovery.img?

---------- Post added at 09:47 AM ---------- Previous post was at 09:44 AM ----------

If the name of the file is TWRP.img and it's in C:\ADB, then the command goes like this:

fastboot flash recovery C:\ADB\TWRP.img

Just clarifying.
[Android Q&A, Help & Troubleshooting] ImJamIN:
Thank you... I'm successful install it with flash tool, but when I'm going to recovery I have the android logo with red triangle... Why?

I've tried all recovery version (2.8.7. 3 3.0.2.0 and x5s version)

Edit : now with fastboot I've a new error : remote download for partition recovery is not allowed :what:
[Android Q&A, Help & Troubleshooting] moriel5:
I think the red triangle issue means that you don't have a recovery installed.

About fastboot... it's odd, I'll try recreating that issue at home.

Are sure you're using the X5 Pro?

If you're using the X5, then you need TWRP compiled for the X5, it has a different CPU, so it's incompatible.
[Android Q&A, Help & Troubleshooting] ImJamIN:
Yes, I'm on x5pro
[Android Q&A, Help & Troubleshooting] moriel5:
Hmm.

And you havn't rooted it yet, right?
[Android Q&A, Help & Troubleshooting] ImJamIN:
No... I've found the problem; it was the bootloader locked.

I've unlock it from developer option and from fastboot and after I've flashed the recovery.

But now I've a new problem : every recovery that I've tried make x5 pro bootlooping.

Now I've successful boot my x5 pro with the original recovery.

Why have I all these problems?
[Android Q&A, Help & Troubleshooting] moriel5:
About fastboot, sorry, I forgot about fastboot oemunlock.

It's generally the first thing I do, so I almost take it for granted that the device in question is bootloader unlocked.

About the bootloop, it's definitely odd, did you try the r14 twrp from needrom?

At least I think that it's there.

Perhaps Doogee changed something in the roms system libraries that neccessaciates rebuilding TWRP in accordance, and that's the reason there are multiple versions of TWRP in accordance to the system revisions.
[Android Q&A, Help & Troubleshooting] ImJamIN:
Yes, I've tried also r14 without success.

I think that doogee have changed something... :(

Now remain only oneclickroot sw...that I don't want to use... :banghead:
[Android Q&A, Help & Troubleshooting] lucaviend:
u use 6.0 snowcat? is it good?

i want o try it but dont know the bugs there
[Android Q&A, Help & Troubleshooting] moriel5:
It's pretty good, however (and this is a common bug among AOSP roms) reception is horrible, I'm on a network which generally has full reception underground, and now I barely have reception outside buildings.

On 4G, I cannot make or recieve calls, nor send or recieve texts, however data works fine, but due to this issue, I'm mainly on 3G (My carrier doesn't exactly use 2G, but I'm fine with that, their 3G has better reception than the other carriers' 2G).

To get data working, you have to crash com.android.phone, and wait a few seconds.

Sometimes you need to crash com.android.phone a second time to get data working.

Occasionaly data stops working, and you have to crash com.android.phone again.

I cannot use ADB from the PC, due to the authentication prompt never appearing (and you couldn't revoke them from the settings either, since that option is just not there).

The device does appear in "adb devices", as an unauthorized device.

To be honest, I also had the adb bug on Doogee's official 5.1 rom.

There is a battery drain, however it's not very severe, especially with Greenify.

Marshmallow permission prompts don't appear, and the permission settings are not in the settings, however with

AppOpsXposed they are there, and you can set them properly, just the prompts never appear and the system always grants the permissions.

OTG doesn't work at all.

The screen flickers at times, not too major, though.

Beyond that I do not remember any other bugs, however Xposed works fine.

---------- Post added at 09:27 AM ---------- Previous post was at 09:00 AM ----------

In addition, there is a (very) noticeable UI freeze when opening the mini-WiFi interface in the quicksettings.

All in all, though, I personally can live with it.
[Android Q&A, Help & Troubleshooting] ImJamIN:
Why if I use a microSD it is recognized as sdcard0 and internal memory as sdcard1?
[Android Q&A, Help & Troubleshooting] moriel5:
Opposite.

Internal = sdcard0

External = sdcard1

And you can adapt the microSD as internal storage, this is Marshmallow, after all.

And another bug I had forgotten to mention, is a momentary lack of responsiveness when unlocking device.
[Android Q&A, Help & Troubleshooting] ImJamIN:
I know that should be opposite, but with mine (r14 and TWRP 3.0.2.0, yes finally I have installed it) if I insert microSD it show me that internal is become sdcard1 and external is become sdcard0. :what:
[Android Q&A, Help & Troubleshooting] moriel5:
Interesting, perhaps Doogee changed something with their configuration.

And I thought that you're on 6.0, however R14 is 5.1

By the way, from where is the 3.0.2 TWRP that you have?

I couldn't find an arm variant of that version, only arm64.
[Android Q&A, Help & Troubleshooting] ImJamIN:
I'm using TWRP 3.0.2.0 from needrom for x5s
[Android Q&A, Help & Troubleshooting] moriel5:
The X5S and the X5 Pro are not the same, although they are similar.

X5S: 1GB RAM, 8GB ROM

X5 Pro: 2GB RAM, 16GB ROM

They do have the same chipset, though: MT6735P.

I'm not sure if it will work, but I'll try it out, it may work.
[Android Q&A, Help & Troubleshooting] ImJamIN:
If you look at needrom, the creator of TWRP has written that is fully compatible with x5pro ;) and I can confirm it because I've installed it on my x5pro :thumbup:
[Android Q&A, Help & Troubleshooting] moriel5:
Alright, then I'm definitely flashing it.

Even if anything goes wrong, I have backups.
[Android Q&A, Help & Troubleshooting] moriel5:
In the end I flashed a different one that I had found in the comments for SnowCatPDA's 6.0 rom on needrom.

The storage bug is nowhere to be found and it's 3.0.2.
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
This isn't a bug.. Just put your backups in folder TWRP / x5s instead of x5pro...

---------- Post added at 12:34 PM ---------- Previous post was at 12:27 PM ----------

Same here, that is irritating... 0 = ext. SD
[Android Q&A, Help & Troubleshooting] moriel5:
I wasn't talking about backups, I was talking about sdcard0/sdcard1.
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
Of course, a made a mistake with that chatting function... I meant the other guy with the back up.. Sry
[Android Q&A, Help & Troubleshooting] moriel5:
It's fine, don't worry.

This TWRP though, will also make backups easier since it was built for the X5 Pro, it's not just compatible with it.
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
Twrp 3.0.2

I flashed successfully twrp 2.8.7 and 2.8.7.3 but with the version 3.0.2 I have difficulties.. I downloaded the port from needrom, pandi1673 and tried flashify, rashr and sp flash tool v5 but nothing worked for me.. With and without locked bootloader. Has someone flashed twrp 3.0.2 successfully? And I don't mean the x5s version..

Edit: I flashed the version witch I mentioned here before (link in a comment on needrom, android 6) with flashify and boom it worked... This version just couldn't find my previous backups... Need to look at this issue later.. Thanks for this hint!

PS: doogee announced yesterday via Facebook that they roll out android 6.0 for x5 pro soon..
[Android Q&A, Help & Troubleshooting] moriel5:
I flashed 3.0.2 via TWRP, it's working fine, I also added the light materialized theme.

And about 6.0, no wonder I didn't find the announcement, I don't use Facebook, ever since I deleted my account since Facebook is evil.
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
​

OK, you flashed the version from the comment of android 6.0? Cause if I do a backup with this version it creates me a folder on my sd card called x5s.. Even when it is written x5 pro in the main window of twrp 3.0.2... Strange thing
[Android Q&A, Help & Troubleshooting] moriel5:
Yes, I did.

That is quite interesting.

However, I don't really use the backup feature, preferring to make a clean install, so it makes sense that I didn't see that.
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
Hm, maybe you could check it out with a tiny partition..
[Android Q&A, Help & Troubleshooting] moriel5:
I'll keep it in mind, for now I just backup my personal files and apk's of my installed apps manually to the SD.
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
Yup, the problem then is that this version again doesn't find backup files created under a twrp version originally made for x5 pro cause 2 different folders are created x5s and x5pro in the twrp backup folder... Same problem like twrp 3.0.2 version for x5s...
[Android Q&A, Help & Troubleshooting] moriel5:
At least it's not a major issue, although it is an issue that should be worked upon.
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
No, I had no other issues with backup or flashing zip.... Didn't try to restore something yet.. But I guess it works - and at least this version is flashable cause I couldn't get the "official" pandi1673 needrom version Installed, neither with flashify, rashr nor with sp flash tool..
[Android Q&A, Help & Troubleshooting] moriel5:
According to the comments there, the last update to the file there was corrupted.
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
No, unfortunately it's still not working.. First the file couldn't be opened properly and when that was fixed the file is still unflashable...

The file from the android 6 comments is the only working one I found regarding twrp 3.0.2
[Android Q&A, Help & Troubleshooting] lucaviend:
i want to ask...what is the best ROM so far guys?

i still use r08 and to change ROM but dont know what the best
[Android Q&A, Help & Troubleshooting] moriel5:
Depends on your tastes.

I use SnowCatPDA's 6.0 rom.

There is the stock r14, and once XDA lets me send PM's, there will be work on cm12.1, and hopefully also cm13.
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
Needrom r14 (flick air mod) to install via twrp ist most stable... But there will be an official update to android 6.0 soon..
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
By the way, I saw there's version 2 of SnowCatPDA's android 6 available with many fixed bugs, almost all fixed.. Did you already tried this Rom, any experience with it?
[Android Q&A, Help & Troubleshooting] moriel5:
I also saw it, and I think that is the version I have, however I'm not sure, and I'll check in more detail when I'll have time.
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
Today I flashed successfully the x32 android 6 SnowCatPDA's edition, then twrp and after flashing super su zip it ended in bootloop?!? Did I made a mistake? How did you gain root privileges on this Rom? Thx
[Android Q&A, Help & Troubleshooting] moriel5:
I had first flashed SnowCatPDA's rom, the I booted into into it, then flashed TWRP, then SuperSU, then I cleared cache & dalvik cache, and finally booted into the system again.
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
OK, did the same without cleaning dalvik & cache... I'll give it another try.. Thx
[Android Q&A, Help & Troubleshooting] moriel5:
No problem.

General rule of thumb, always clean dalvik & cache.

Unless of course you're using TWRP to reboot into fastboot or download mode, or to turn off your device (no idea why someone would use TWRP especially for that, though).
[Android Q&A, Help & Troubleshooting] GiannisSma:
Any experience from you have install the Android 6 rom about the dev's note for sound quality?

Στάλθηκε από το X5pro μου χρησιμοποιώντας Tapatalk
[Android Q&A, Help & Troubleshooting] moriel5:
I'm not an audiophile, nor do I usually notice too many changes in audio quality , but I think it's a bit louder?
[Android Q&A, Help & Troubleshooting] GiannisSma:
I didn't have time to install it yet and I asking to know more details about this note for the rom. Maybe isn't so bad the quality and that's why you can't understand the difference before and now with this rom! Thank you for the answer. And if you or anyone else have more details and notice something changed to better or worse about the rom for example battery life, speed, signal, wifi etc let as inform! [emoji4]

Στάλθηκε από το X5pro μου χρησιμοποιώντας Tapatalk
[Android Q&A, Help & Troubleshooting] moriel5:
Audio was pretty quiet at maximum, according to my friends.

I personally set it to below minimum (don't want to destroy my hearing), so no one but me generally hear anything at my levels.

About the updated rom, I'm going to check if it's the same one I have or newer.
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
Installed the 64bit version 2 of SnowCatPDA's android 6.. Runs almost perfectly and the nasty speaker issue can be fixed by settings, sound and notification, uncheck every option in sound enhancement... Voila
[Android Q&A, Help & Troubleshooting] moriel5:
4G calls work for you?

What about OTG, and ADB?

And tge proximity sensor?
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
I only use 3g so hard to say... Otg should work as SnowCatPDA states in his description at least on the 64bit version, I don't use adb but twrp3 64bit runs smoothly in combination with flashify - no sensor bugs so fare.. Till now it works just perfectly, no issues at all.. Even to install super su zip worked on first try, couldn't get it done with the 32bit version...
[Android Q&A, Help & Troubleshooting] moriel5:
I'm on the 32-bit as it and some of the apps I use are a lot lighter that way.

SuperSU flashed perfectly right from the start, systemless-root.

4G calls though don't work, adb and otg don't either (although theywork from TWRP), and I'm not sure if I'm on the first or second version of the rom.

Update: I just checked, I'm on the first version, definitely going to update.
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
VTS for Android finds 0 publicly known vulnerabilities on SnowCatPDA's android 6 x64... Pretty cool, I never had such a good result before...
[Android Q&A, Help & Troubleshooting] moriel5:
I've had it on SnowCatPDA's rom, as well as Phicomm's Clue C230W (512mb/quad-core (at least until they updated the app).
[Android Q&A, Help & Troubleshooting] GiannisSma:
How can i install the x64 bit twrp that included it the x64 bit rom's folder? This twrp doesn't have any scatter file and that i do is chosing the one scatter i find in the rom's folder and then i click on the recovery path and change the file from recovery.img with the recovery-TWRP-x64.img but i try to boot into twrp and the phone boots normal! Is it neccesary to install first the x32 bit and after install rashr and install the x64 bit recovery and then the x64 bit rom?
[Android Q&A, Help & Troubleshooting] moriel5:
No, switch names and flash.

Or flash the way it is, and then flash TWRP.

From Fastboot.

fastboot oemunlock

Reboot to bootloader

fastboot flash recovery *.img (replace * with name of TWRP image file)
[Android Q&A, Help & Troubleshooting] GiannisSma:
I change the recovery.img to recovery_old.img and the recovery-TWRP-x64.img to recovery.img, i choose the scatter exists and now i flash and i come back if all was ok for feedback.
[Android Q&A, Help & Troubleshooting] moriel5:
No problem, awaiting feedback.
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
I kicked the stock recovery out of the folder and pointed the flash tool (the recovery section) directly to the twrp 64 image... You can choose the path by clicking on the green or white bar in sp flash tool v5... Then i flashed the whole rom at once.. Good luck..
[Android Q&A, Help & Troubleshooting] crazytiti:
Hello all.

i just received my X5 pro

No root and bootloader lock.

It come with android 5.1 R15-2016.03.16

I want to upload this R15 version to needrom.com

But I'am not able to backup partitions with adb shell and

dd if=/dev/block/mmcblk0pxx of=/storage/sdcard0/dump/mmcblk0pxx

(xx from 1 to 23 and also mmcblk0rpmb mmcblk0boot0 mmcblk0boot1 to make a whole save of the phone before messing with it :)

i get permission denied even wheen under recovery.

Under bootloader i d'ont have ADB access

Do i have to root it first ?

edit : i manage to flash recovery with TWRP3.0.2-0 (for R14 ?) from needrom http://www.needrom.com/download/twrp_3-0-2-0_recovery-for-x5-pro/

But this broke my stock rom ! (strange boot loop one time only reboot after doogee logo, one time TWRP try to do something but struggle and then reboot)

TWRP partially work i have backup all partitions. Fastboot still work

I will post later the system backup (maybe corrupted ?)
[Android Q&A, Help & Troubleshooting] crazytiti:
So here is the system backup R15

dl.free.fr/oNIG3W0Rj

I notice that TWRP only use /dev/block/mmcblk0p0 to p22

but when the phone was working ihave seen /dev/block/mmcblk0p23
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
Thanks for your work, the download link seems not to work...

Is the r15 still lollipop 5.1? .. cause there's an official update to 6.0 expected...
[Android Q&A, Help & Troubleshooting] crazytiti:
Yes it's android 5.1

http://dl.free.fr/oNIG3W0Rj should work from any country but if you want i can upload it elsewhere.

Also i try to flash the android 6 x32 v2 from snowPDA via flashtool but it make bootloop too.

I'm glad if you have any idea to make it work again :-/ it seems doogee change something in this R15

Edit : with Flash tool i successfully revive my phone :)))

I reflash stock boot stock system and TWRP recovery (because i lost the original R15 recovery)

but this time i use the file system_image.emmc.win instead of system.ext4.win

So now i have R15 and TWRP (although i'm not sure TWRP is fully functional)
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
Download couldn't work because of adaway... Now it's working..

I had issues with SnowCatPDA's x32 but x64 work damn well for me, I use it since a week now..

I tried lots of different twrp versions on this phone and they all did the job 100%.. Except the twrp 3.0.2 from pandi1673 on needrom.com. Now I use twrp x64 at the moment also working just great..

SnowCatPDA writes that the new phone versions have another kind of display but he compiled a new boot.img for this problem but I'm sure you read this on needrom... Maybe they changed it another time- you could write him as he invites users to give feedback..
[Android Q&A, Help & Troubleshooting] crazytiti:
Ok i may test x64 version at one time (or maybe wait the official)

Indeed with the TWRP recovery working i was able to install superSU so my phone is rooted ;)

I will upload the system partition on needrom but i will upload the system_image.emmc.win because the other one is broken.
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
Jup, I had a hard bricked phone after flashing twrp 3.0.2 from pandi1673 on needrom.com... But I had a nandroid and a working flash tool so no problem.. I'm really happy with this android 6 x64 but you can never know, may one day I'll give r15 a try..
[Android Q&A, Help & Troubleshooting] crazytiti:
Ok so boot + system R15 are uploaded to needrom

http://www.needrom.com/download/official-r15-system-boot-backup/
[Android Q&A, Help & Troubleshooting] moriel5:
I'm staying on x32 for testing, my provider has the best coverage in my country, so even though my reception is horrible (1-2 bars in my room instead of full) with x32, I still have reception nearly everywhere with 3G, and in some places (not many) I even have a nearly full signal).

I can confirm that the display bug in v.1 has been fixed.

---------- Post added at 10:11 PM ---------- Previous post was at 10:10 PM ----------

I'll download them in order have a backup.

My host has been taken down (again) already a long time ago, though.

By the way.
[Android Q&A, Help & Troubleshooting] moriel5:
Another bug/limitation in v2 of SnowCatPDA's x32 6.0.

ScreenRecord cannot record in HD, in V1 it was possible, all this with the stock binary.

With GB binary, unable to record at all both in v1 and v2.
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
And I can't get viper4android to work on x64... Tried almost every possible workaround / solution but drivers won't install properly...

I can confirm that it's not possible to ScreenRecord in other quality than the device standard..
[Android Q&A, Help & Troubleshooting] moriel5:
All same on x32, and device default for screen recording is below 720p.
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
Also with viper4android?
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
Om

OK, got it working.. Changed selinux to permissive and used the universal init. d app..
[Android Q&A, Help & Troubleshooting] moriel5:
I'm on permissive most of the time (manually changing after boot, but Viper4Android does not recognize driver.

I use compatible mode.
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
I thought that is the reason why universal Inint. d from app store is needed so the system remembers the selinux setting after reboot, at least it works for me.. No more issues

Do you use the new version 2.0.4.1?

---------- Post added at 05:32 PM ---------- Previous post was at 04:42 PM ----------
[Android Q&A, Help & Troubleshooting] moriel5:
About Viper4Android, yes, downloaded it straight from the site, so I'm on 2.0.4.1.

About Engineer mode, I didn't see anything anything that could help us, and I'm the kind who plays even with those kinds of settings.

Calibrating the proximity sensor doesn't help either.
[Android Q&A, Help & Troubleshooting] Sam Nakamura:
OK, I don't know much about engineer mode but I tried some apps which promise to enhance the signal but that's not working.. And I don't mind so much as I actually have never lost the signal... It's low but sufficient
[Android Q&A, Help & Troubleshooting] crazytiti:
Maybe it's just a calibration problem.

the reception is as good as the stock firmware but it display lower indicator ?
[Android Q&A, Help & Troubleshooting] moriel5:
About proximity sensor, recalibration did not help.

About reception, no, it's actually worse.

I'm underground pretty often, so I can verify this, my cellular provider usually provides full reception, even underground, but I have no reception at all down here, where I used to have full coverage.

I have a second phone on the same network, different number, though, and there I have full coverage.