yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] moriel5:
Perhaps, but I do not think thus.

From my experience, if you clean flash SnowCat4PDA's ROM (including the bootloader), there are no issues.

However, you also need the recovery to be compatible with his ROM, otherwise it WILL bootloop (this is not a bug, you'll find this with all ROMs that you try to flash a recovery that does not support their boot image).
[Android Q&A, Help & Troubleshooting] xe7um:
What I've done following recommendations of maria.aiva:

- In device enable USB debug and OEM unlock

- in Linux terminal:

$ adb reboot-bootloader

$ fastboot devices

(device is detected)

$ fastboot getvar all

...

warranty: yes

unlocked: no

$ fastboot oem unlock

...

void warranty message, clear ALL data

(like a factory reset)

$ fastboot getvar all

...

warranty: no

unlocked: yes

- Shut down phone and get out battery

- Flash phone with flash_tools and MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt

(I've flashed SnowcatPDA 7.1.1x32 BETA4 from getbest_ru, in needrom there is only BETA3)

(this does full wipe)

- Without starting phone, Flash compatible TWRP

(this one is a bit involved. Interestingly TWRP 3.1.1 x32 Android 7.1.1 from getbest_ru doesn't work.

I had to use TWRP 3.2 img from LineageOS 14.1 but then I didn't have a scatter file, and used the

3.1.1 one changing recovery image name accordingly.

I'm confident that TWRP 3.2 works because right now I've it installed with Android stock 6.0 kernel R16

and rooted with SuperSU)

- Put battery in and start in TWRP recovery

(no luck, I get a bootloop showing SnowcatPDA image continuously)
[Android Q&A, Help & Troubleshooting] moriel5:
The stock 6.0 ROM has a whole different layout from the stock 5.x ROMs, while SnowCat4PDA's ROMs share a similar bootloader to the stock 5.x ROMs, so the 3.2 TWRP will not work for you.

Try flashing the 3.1.1 TWRP via fastboot (fastboot flash recovery **.img).
[Android Q&A, Help & Troubleshooting] xe7um:
If I remember well I flashed TWRP 3.1.1 first with flash_tools and didn't work either. I understand that I've to flash rom 7.1.1 first and then power on and boot to bootloader, select fastboot and then flash 3.1.1 via fastboot, right? Once I enter TWRP, some options before booting system?
[Android Q&A, Help & Troubleshooting] moriel5:
I'd recommend you to reboot to TWRP twice more, and then reboot to system (perhaps also flash cache, dalvik cache, and data, to be on the same side).

It's been quite some time since I had last used my X5 Pro, seeing as I had accidentally broken the cellular antaenne connector on my X5 Pro's motherboard (while fixing the USB port), and getting a Nexus 4 since then (I only miss the battery life, ease of disassembly, newer kernel version (though PostMarketOS development may help change that situation), and screen size (though I'd rather have a ~5.7-5.8" 1080p screen).
[Android Q&A, Help & Troubleshooting] xe7um:
Prior doing what you suggest, some interesting points:

Posted comments regarding Snowcat 7.1.1 BETA3 in needrom website:

-------------------------------------------------------------

itabori user:

" No luck with this ROM —maybe I need help?

Tried installing x32, then x64 version using FlashTool v5.1636. Gets stuck in boot loop, showing the SnowCat logo only.

Installed TWRP later from getbest.ru as linked, that did not work either —boot loop.

Any ideas, please let me know –I would like to get rid of the stock Android 6.0 ROM as it has cooked-in ads in the factory ROM.

Cheers,

István"

-------------------------------------------------------------

noizeboy user:

"Getting a boot loop on install with this rom. There's 2 scatter files in the rom, one –wipe clean install –and another just normal. Normal one is corrupt and the –wipe clean install –just leaves a loop d loop."

-------------------------------------------------------------

CoMiKe user:

"v7.1.1 BETA 4 (from the author's webpage) bootloops. I'm not even able to enter the recovery, and people reported the same on previous posts, so DON'T INSTALL!!"

-------------------------------------------------------------

CoMiKe user:

"Tested with BETA 3 and it bootloops as well, so this ROM is a no-go for me."

-------------------------------------------------------------

valentino67 user:

"hello i have two x5 pro phone

the first was under android 5.1

I have installed nougat 7.1.1 x64 beta4

without problem, everything nickel walking

the second is under android 6.0,

impossible to put nougat 7.1.1

after the logo nougat it reboot permanently yet

they have all the same processor: mt 6735v"

-------------------------------------------------------------

Just my two cents: Perhaps 7.1.1 works only when upgrading from 5.1, otherwise when upgrading from MM 6.0 it bootloops.

Will investigate tomorrow

---------- Post added at 10:23 PM ---------- Previous post was at 10:12 PM ----------

Another question, when flashing 7.1.1 from stock 6.0 should I use Download or Firmware update in flash_tools?
[Android Q&A, Help & Troubleshooting] moriel5:
I'll answer both questions at once, since, and I am sorry that I hadn't been clear enough before: Do NOT flash any of SnowCat4PDA's ROMs upon the stock 6.0 ROM.

You need to first flash the latest 5.1 ROM, before doing anything else.

This is due to the partition layout being different (at least, I think that is the reason, I hadn't had the time to properly check).

And as to what choice to choose with SP Flash Tools, I'd recommend you not to touch those options at all, just to leace it the way it is.

I do want to check what the difference (when I'll have the time to do so), however for the time being, I know that playing with it will simply hardbrick your phone (my friend's old tablet is still hardbricked due to that, and I had not been able to resurrect it, even via the soldering emergency mode).
[Android Q&A, Help & Troubleshooting] xe7um:
When flashing 5.1 R17 from needrom device doesn't turn on. I've to reflash to 6.0 to recover. Frankly I don't fully understand... thera are 5 ROMs:

ROM 1 - Doogee X5 Pro

ROM 1 - Doogee X5 Pro - Update R12

ROM 1 - Doogee X5 Pro - Update R17 (the one that I've tried)

ROM 2 - Doogee X5 Pro

Flash SPMDT

Needrom installation comments follow:

-------------------------------------------------------------------------------------------------------

DESCRIPTION

ROM Mobile Doogee X5 Pro –ROM Android 5.1

ONLY MT6735M

ROM 1 –Update OfficialROM Doogee X5 Pro version: DOOGEE-X5pro-Android5.1-R17-2016.07.01 –t93bm-dg-a37-33pgu-hd-128g16g-fdd137820-bom68 –full_hct6735m_35gu_l-user 5.1 LMY47D

ATTENTION this ROM is not compatible with ROM 2

————————————————————————————————————————————————————————————————

ROM 1 –Update Official ROM Doogee X5 Pro version: DOOGEE-X5pro-Android5.1-R12-2016.01.15 –t93bm-dg-a37-33pgu-hd-128g16g-fdd137820-bom68 –full_hct6735m_35gu_l-user 5.1 LMY47D

ATTENTION this ROM is not compatible with ROM 2

————————————————————————————————————————————————————————————————

ROM 2 –Official ROM Doogee X5 Pro version: DOOGEE-X5pro-64+8-Android5.1-2015.12.21 –t93bm-dg-a37f–33pgu-hd-64g8g-fdd137820-dg- full_hct6735m_35gu_l-user 5.1 LMY47D

ATTENTION this ROM is not compatible with ROM 1

————————————————————————————————————————————————————————————————

ROM 1 –Official ROM Doogee X5 Pro version: DOOGEE-X5pro-Android5.1-R09-2015.12.01 –t93bm-dg-a37-33pgu-hd-128g16g-fdd137820-bom68 –full_hct6735m_35gu_l-user 5.1 LMY47D

Gapps include –No Rooted

Language support: Multilang

Install ROM:

Install with SP MDT:

1). Turn off the smartphone. Cable is not connected to the computer.

2). Remove the battery and insert it again

3). Connect your phone to a computer cable. The operating system detects a new device

4). Disconnect the cable from the computer.

5). Run SPMultiPortFlashDownloadProject.exe

6). Choose File>Open File Agent download and specify the file MTK_AllInOneDA.bin (it is in the folder SP_MDT).

7). Click Scatter File and select the MT6735M_Android_scatter.txt file (it's in the folder with the rom).

8). Click "Start all".

9). Connect your phone to a computer cable. The program should see and blink. If the phone is not detected, then unplug it from the computer,

remove and insert the battery (if the battery is removable) and reconnect it to the computer.

10). After (OK) click Stop and disable any phone.

11). Completed.
[Android Q&A, Help & Troubleshooting] moriel5:
The first three are for the X5 Pro (which has 2GB of RAM, and 16GB of ROM).

1: ROM 1 - Doogee X5 Pro

R09

2: ROM 1 - Doogee X5 Pro - Update R12

3: ROM 1 - Doogee X5 Pro - Update R17

The last one is for the X5S, which is precisely the same, but for the RAM (1GB instead of 2) and the storage (8GB instead of 16).

Think of it as a refreshed X5.

4: ROM 2: - Doogee X5 Pro X5S ("R01")

Try R09 in that case, and then just update it to R17 (But not directly, try flashing R12 in between, if possible, via stock recovery).

---------- Post added at 01:28 PM ---------- Previous post was at 01:16 PM ----------

For anyone curious, I had finally found the website I had downloaded the MT6735/MT6735M/MT6735P's Schematics.

Enjoy: http://www.datasheet4u.com/datasheet-pdf/MediaTek/MT6735/pdf.php?id=925384
[Android Q&A, Help & Troubleshooting] xe7um:
Once R09 is flashed, I can't even turn it on. Neither can I reflash 6.0 R16 with flash_tool. Device is dead. Help! (I suspect that device is hard bricked)
[Android Q&A, Help & Troubleshooting] moriel5:
Don't worry, what you need to to do is take out the battery, connect the phone via USB, and start flashing as soon as you return the battery.

I'll try researching this, all this sounds very weird.
[Android Q&A, Help & Troubleshooting] xe7um:
What do you mean exactly? I execute flash_tool, press Download button, connect device without battery (nothing happens -before it began flashing-) and then connect the battery? nothing happens

Before, with battery in, when powering on, there was a noticeable little click after a few seconds. Now nothing
[Android Q&A, Help & Troubleshooting] moriel5:
Are you sure that SP Flash Tools does not recognize the phone at all?

If so, I'm going to try finding a solution as soon as I finish cleaning up the kitchen at my house.
[Android Q&A, Help & Troubleshooting] moriel5:
Alright then, I may have found a solution.

Someone had encounted a similar situation nearly a year ago, and managed to unbrick their device.

Here is the link: https://xdaforums.com/general/xda-assist/doogee-x5-pro-bricked-t3555418

And here the page that they had made use of:

https://www.engineerthink.com/blog/2016/07/how-to-unbrick-hard-bricked-mediatekmtk-android-phone/

Now I must sleep, since I had last slept nearly 48 hours ago, and I have work in the late morning.

I am not leaving this situation, though, until it gets resolved.
[Android Q&A, Help & Troubleshooting] xe7um:
Success! You saved my day (and my phone :)

I use flash_tool on Linux. Very convenient..., just plug the phone without battery and starts flashing. No physical buttons to press to get the phone recognized.

Problem was the phone was hardbricked and Linux flash_tool didn't recognize it in any way. I got an old WinXP box, entered metamode with VolUp+Power and could flash preloader. Then I flashed whole stock 6.0 R16 ROM in Linux.

Now the question is: how come flashing needrom's stock 5.1 R09 ROM hardbricks the phone?

Thanks! Now would be interesting to find a reliable way to install SnowcatPDA 7.1.1 from stock 6.0

Have a nice year!
[Android Q&A, Help & Troubleshooting] moriel5:
I'm glad that at the very least, the phone works now, although it is odd that it required Windows XP (I use Solus OS, my favorite Linux distro, so I don't have that kind of oddity).

It is very strange, are you sure you have the X5 Pro and not the X5S?

Until we find a way, perhaps you'll want to try SnowCat4PDA's debloated 6.0 stock ROM?
[Android Q&A, Help & Troubleshooting] xe7um:
sure, 2Gb RAM, 16GB flash

But, as you commented before, flashing should be over a 5.1 kernel, not the 6.0

Another question, if I use MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt no need to wipe Dalvik/cache, right?
[Android Q&A, Help & Troubleshooting] moriel5:
Hmm...

This is a seperate ROM from SnowCat4PDA's ROMs, it is the stock 6.0 ROM, just debloated.

It is not a true custom ROM.

Correct.
[Android Q&A, Help & Troubleshooting] xe7um:
I understand then that I've to flash CUSTOM Android 6.0 v3.1 x64 x32 fix from Needrom. Flash with flash_tool/MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt and boot directly to system. Just to be sure.

Another question. Can these ROMs be directly downloaded from xda-developers?
[Android Q&A, Help & Troubleshooting] moriel5:
I don't think that is it.

Try checking getbest.ru, SnowCat4PDA's blog.

Not unless someone uploads them to here.
[Android Q&A, Help & Troubleshooting] xe7um:
My testings so far...

Attempt to install SnowcatPDA 7.1.1 BETA4:

There is a new custom ROM 5.1 in getbest.ru dated 20-06-2017 that seems to be for new X5 pro models, as far as I can understand from the russian translation. When installing I get a bootloop when selecting recovery, out of three options (normal, fastboot, recovery)

Attemt to install SnowcatPDA DOOGEE X5PRO Marshmallow 6.0 - v4.0 + AOSP, dated 06-01-2017 in getbest.ru:

As before, bootloop when selecting recovery.

I try all this from stock MM 6.0 R16 ROM

Definitely I find all this very picky!
[Android Q&A, Help & Troubleshooting] moriel5:
You tried the AOSP build, not the repacked stock 6.0 build.

I'll try finding the link for it, and once I do, I'll send it to you.

In the meantime, I'll try finding out why the AOSP builds are not working.

By the way, there are CM/LOS 14.1 (7.1.1) builds on 4PDA if you wish to try them, and there is an Oreo (8.0) build over at VKontakte.

I personally havn't tested them, since either, with the CM/LOS builds, I was running the AOSP builds, which had a newer bootloader, or, with the Oreo build, I am waiting for XPosed framework to be available before jumping.

In addition, I do not understand Russian, something which heavily hampers me on 4PDA and VKontakte.
[Android Q&A, Help & Troubleshooting] xe7um:
I've found in getbest.ru: Oficial Androiod 6.0 for DOOGEE X5PROx32. File is repack-stock-x5pro-6.0-R16-x32.zip.

I understand this is like official stock only debloated and without adware. Am I right? I've flashed it and seems to work well
[Android Q&A, Help & Troubleshooting] moriel5:
You are correct.

I still need to find out why the other firmwares did nit work for you, though.
[Android Q&A, Help & Troubleshooting] xe7um:
how to root debloated SnowCat official marshmallow rom

Now the problem is that I can't root the phone. I can install TWRP:

fastboot flash recovery recovery-twrp-3.2.0-git-20171204.imp

which is from LineageOS 14.1 (Android 7.1.2 Nougat) but works well.

When installing SuperSU-v.2.79-201612051815.zip device bootloops. This SuperSU worked well with official DOOGEE R16 6.0 ROM

---------- Post added at 07:32 PM ---------- Previous post was at 06:58 PM ----------

I've finally rooted with a newer SuperSU version. Forget about it. Thanks
[Android Q&A, Help & Troubleshooting] moriel5:
I'm glad it worked out for you.

I'm guessing that the old version did not patch the boot image, that is why it caused the phone to bootloop.
[Android Q&A, Help & Troubleshooting] moriel5:
Good news everyone!

While this does not yet guarantee anything for the X5 Pro, the MT6735P has work being made towards an opensource bootloader!

https://www.postmarketos.org/blog/2018/04/14/lowlevel/
[Android Q&A, Help & Troubleshooting] ilsaggio73:
hi, i installed x5pro-6.0-x32-v3.1.ip by snowcat, but i can't get into recovery to install magisk ... do you have any ideas? (the snowcat pda edition logo starts up when switched on)
[Android Q&A, Help & Troubleshooting] xdaluser0:
Needrom usually has everything:

Flash tool for windows and linux:

http://www.needrom.com/download/sp-flash-tool-v5-1424-00/

Alternative flash tools shops use that sometimes works better:

http://www.needrom.com/download/smart-phone-multiport-download/

Driver package*:

http://www.needrom.com/download/mtk-driver-auto-installer-v5-1453-03/

Scatter files usually come with roms since they're device specific. So, for instance, the twrp off needrom for the doogee x5 pro has two bundled in TWRP-X5-Pro-R11-Rom.rar:

http://www.needrom.com/download/twrp-2-8-7-3-megthebest-5/

One for the TWRP recovery and one for the stock R11 recovery. You can compare the two and see they come with specific instruction for the device and usually name the rom files. For the purpose of unofficial recoveries, and roms in general, the file names are stripped from the scatter file or are deselected in the GUI. In this case, there are two customized scatters for two different roms.

*Typically, the driver and flash tool that matches it work fine. Sometimes, you need to mess around with versions so it's hard to know what to use. For instance, under windows 10 32bit, I used:

Driver: MediaTek Driver Package version 5.14.53.00

Flash Tool: MediaTek SP Flash Tool 5.15.32.00

Usually it's best to try the latest version and work your way backwards from there.
[Android Q&A, Help & Troubleshooting] awakekiwi:
I am happy to report that Kingroot apk now successfully roots X5 Pro with latest updates. Works a treat! No tricks needed.

Just install Kingroot and run it, phone will reboot, and bingo done!
[Android Q&A, Help & Troubleshooting] niknah:
Doogee X3?

I couldn't get kingroot to work with Doogee X3.

sp flash tools wouldn't detect the X3 either, when I click "Download" it does nothing.

Tried mtkdroidroot too, the adb there wouldn't detect the device and if I upgraded the adb so that it detects the device, mtkdroidroot says adb failed.

There doesn't look like much different between the X3 and X5 except that the screen is smaller.

I have enabled oem unlock and debugging in the developer section. "fastboot oem unlock" seemed to have worked.

Does anyone have any ideas?

Thank you.
[Android Q&A, Help & Troubleshooting] awakekiwi:
Nope sorry, this thread is for x5 pro, its 64bit ans different chipset so quite different to x3. Even the x5 and x5 pro require different process to root.
[Android Q&A, Help & Troubleshooting] devrieshh:
the x3 is 32bit
[Android Q&A, Help & Troubleshooting] Aidriz:
Can make a root for Doogee X5 Pro ~

Please help me.. I need the root.. Can everybody help me?
[Android Q&A, Help & Troubleshooting] awakekiwi:
go here, install kingroot apk to your phone (click the link from your phone browser) then simply open the app and click and phone will restart and then your done! easy.. PS: you need to have allowed in your phone settings third party apps (google allowing third party apps)

http://www.appsandroidapk.com/tools/kingroot/
[Android Q&A, Help & Troubleshooting] Romeohotel:
So I finally got root with Kingroot, and swapped it out for SuperSU. But I haven't been able to flash TWRP at all. I'm guessing it's because the TWRP images available go up to R12, and I'm on R14. Is there an Image available for R14? Or should I roll back to R12 and then use the megathebest TWRP? And if I have root, can I flash the recovery image with Rashr or Flashify? or do I have to carry on my fight to the death to get Flashtool working? :o Cheers all.
[Android Q&A, Help & Troubleshooting] Romeohotel:
UPDATE: Well I went ahead and tried to flash a different version of the stock rom using SP Flash tool....and I'm bricked. I've tried multiple roms and multiple versions of flashtool, all with the same result: The download completes fine, the phone is recognised by the pc and I can browse all the folders on the phone, but when I try and boot it, the screen lights up...and that's it. No boot logo, and no recovery (tried flashing that independently as well, and the preloader). Any ideas anyone?
[Android Q&A, Help & Troubleshooting] zanderman1985:
can the guys who rooted with king root post what version you had when you did it? i have r08 and i've tried absolutely EVERYTHING, kingoroot, rootgenius, kingroot i could go on but nothings worked

regards alex
[Android Q&A, Help & Troubleshooting] moriel5:
I uploaded them, however if that SnowCat guy from 4PDA is making 6.0 (which I'm using currently) there must be 6.0 kernel sources, so off I go searching for them.

---------- Post added at 10:44 PM ---------- Previous post was at 10:41 PM ----------

My recommendation is to just flash TWRP from bootloader via fastboot and install SuperSU from there, makes things a lot easier since you can use the official Google USB drivers for that.
[Android Q&A, Help & Troubleshooting] Romeohotel:
I used kingroot version 4.80 and it worked like a charm.
[Android Q&A, Help & Troubleshooting] moriel5:
I'm not telling anyone what to do, however KingRoot is known to be spyware.

It does it's job, however it sends personal data back to the KingRoot's developers' servers.

So I recommend not to use it if possible.

Search here on XDA for more information about the problematic nature of KingRoot.
[Android Q&A, Help & Troubleshooting] Romeohotel:
Agreed. I used it as a last resort on an out-of-the-box phone with zero data on it, and then immediately swapped it out for superSU. I wouldn't advise anyone to leave kingroot on their system.
[Android Q&A, Help & Troubleshooting] Romeohotel:
Can anyone point me to a R14 stock rom?
[Android Q&A, Help & Troubleshooting] moriel5:
Alright, I have asked for Exodus ROM to be ported over to the Doogee X5 Pro.

No guarantees, however let's hope for the best.

Exodus ROM is supposed to be extremely stable.
[Android Q&A, Help & Troubleshooting] bighun:
i am trying to root my x5 pro and having no joy i have tried everything and no joy could someone who has flashed there x5 pro please set out how they did it starting with which file goes where and what recovery img do i use i have used sp flash tool and tried to download the files with scatter files installed and MTK_AllInOne_DA.bin but i am not sure what recovery image to use the flash tool works good but i just get red then yellow no purple in between any help would be good
[Android Q&A, Help & Troubleshooting] kirito9:
I can try to port CM12.1 for your device. I already ported to another MT6735M device.
[Android Q&A, Help & Troubleshooting] moriel5:
The Doogie X5 Pro is a MT6735P device.

However, there is an odd story with it and the MT6735M chipset, so you have my support.

Could you also try CM13?

There are 6.0 kernel sources over at 4PDA, again with this l odd MT6735M story, so you could try it out, I still haven't downloaded it yet, probably I'll download it this week or next week, however I'm currently using AOSP 6.0 on my phone, courtesy of SnowCatPDA.
[Android Q&A, Help & Troubleshooting] kirito9:
MT6735P, MT6735M or just MT6735 are just different variations of the chipset. The ROM should boot even though you still have an MT6735P ported from MT6735M. If you have stock ROM then I can tell you which files to upload and I will port. PM me for further instructions.
[Android Q&A, Help & Troubleshooting] moriel5:
I'll PM you when I'll be on my laptop, XDA Labs isn't letting me send PM's at the moment.

It may take a few days, Realtek's Windows drivers for my internal WiFi adapter are horrible, I wish that all of my tools were available on Linux.
[Android Q&A, Help & Troubleshooting] GiannisSma:
Great news! Hope to see your work and try it to leave feedback and help you to improve your port!

Look at the screenshots below, my device info is MT6735 and at the sp flash tool I get MT6735M which is the right? Maybe some devices have different cpu model?

Στάλθηκε από το X5pro μου χρησιμοποιώντας Tapatalk