yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] tvladan:
The problem with the reboots (as far as i could undrestand) comes from the factory recovery witch checks and restores some data at root level, this is the reason why mtk droid tools can not root the phone and this is the reason why those partitions might not work. Anyway, thanks for the replay, your effort is much apreciatted(by me anyway:p)...so there is no reason for me to try and flah those new partitions ...since there is no way to make a true nandroid backup i might loose all the installed apps.. If there will not be a custom recovery for our phone anytime soon..i might get bored one evening and flash kit kat to it....

Also ... the reason for the Encryption unsuccessful error might be that the data partition is invalid, or that the phone searches still for the old partition ... you should of tried to reboot the phone a couple of times before pressing the factory reset, might got lucky and made it work as some posts around the internet suggest. Anyway ... without a custom recovery for this phone ... every other thing regarding custom roms, flashing tools and stuff is very hard to accomplish.
[General Questions and Answers] Nudeldampf:
I'd love to flash kit kat and try this, but the only image I have is the R14 build provided by Doogee on their website. Which causes instant flickering on my display, I've just tried it again a minute ago. Only this new build R21 you gave us solves this flickering problem afterwards. Do you have a contact at Doogee since they send you their build? I have written a mail months ago and funny thing is, yesterday they replied. Not much text, essentially they said that there will be the latest version R21 soll which will solve the vertical lines problem. So you got the version earlier, which was awesome for me :D

But I wonder, what makes my DG700 different from yours or others that I cannot flash the R14 build with Kit Kat? I know that the Rom page with the EBR files said on another page to change the display drivers when flashing - but the dropdownmenus are empty those version of SPMDT and there is no button for specifying the database like told in that howto?
[General Questions and Answers] NaturalBornCamper:
Yeah, that's the same thing that happened on my DG700, as I posted on my big reply on page 2. Repartitioned always worked until the first restart. And I tried so many different combinations with always the same result. So I was hoping these files from Needrom were maybe somehow different than the ones I created myself.

I do appreciate you trying it, A LOT! I would have been so angry if I had tried it once again to reach the exact same result as I had 30 times before. I would have had to reinstall and personalize everything again. Especially since I cannot make a Nandroid restore without the custom recovery and that Titanium backup seems not to be able to restore app data on Lollipop.

It's weird however that some people on needrom managed to make the repartition work. What's the deal with the DG700??? Why are they all different? It's really annoying!

-Some can repartition

-Some have the flickering problem like you

-Some are not water resistant like mine.

What the hell Doogee?
[General Questions and Answers] tvladan:
@ Nudeldampf: How about this KitKat release form needroom? it says "official" but the code ends with 16. Is this the same one as the one from Doogee? http://www.needrom.com/download/doogee-dg700/

@ NaturalBornCamper: this are the risk involved buying from an obscure china company. If we had a Nexus I am sure we would of found other problems but also a greater area of support here on xda. To add to your list of weird stuff that DG700 does mine does the following:

- from time to time it looses root privileges, with no obvious reason ... i plug it in the PC use Iroot and root it again ... works fine for a while. Once i dropped it on the concrete coming out of the car, and also lost root privileges.

- it lost both IMEI's when i installed ALL the official DOOGEE firmware

- all the dpi changers I tried so far keep reverting to 200dpi after 2 or 3 reboots ... whatever other dpi I set, I always find myself back to 200

So yea ... if any of you have the patience and time to try this: try rooting with MTK Droid tools (search the latest version on google). at some step in the process the program instructs you to create a custom recovery and gives you a link as how to do it ... I had it at some point but not seem to find it right now. (here it is afterall: http://xdaforums.com/showthread.php?t=2379412)
[General Questions and Answers] NaturalBornCamper:
Didn't you read the disclaimer on iRoot? It says: "Dropping your phone will result in losing root provileges, take that biatches!" :p

I know what you mean about all the randome problems na! However I had China phones before and never had weird stuff like that :) It seems like mine is not too bad compared to the weird problems you have, all this is happening with R21 of Android 5.0? Maybe it's all because of this.

Anyways, thanks for that link. I thought I recalled trying something similar to this, making my own recovery, but it failed or something like that, and I can't recall if it was the same procedure I tried. I definitely remember trying to create my own with a tool like this one, as well as TWRP.

[MENTION=6718315]Nudeldampf[/MENTION] This looks like an experiment for you and your second DG700 once again :p
[General Questions and Answers] tvladan:
the tool and the procedure are prior to android 5.0. I tried but also failed creating my own recovery. All I managed to do was to soft brick the phone :)) It seems that MTK droid tools developer abandoned the project for some reason so ... no updates for 5.0. For me it's the first china phone, but so far, short of being unable to install xposed and some modules I am pretty satisfied with my dg700. haven't tested it for water proof or nail hammering yet ... :p

anyway ... as I manage to remember a sort of nandorid backup can be done using sptool or mtkdroid ... since it downloads all the phone's data to pc, including user data and so on ... but I am in the same situation as NaturalBornCamper, my son was born 2 months ago, not a lot of time to loose on experimenting with the phone ... maybe in the winter when he'll be a little bit bigger and sleep more than 2 hours at a time :P
[General Questions and Answers] Nudeldampf:
Sadly no, the build number of the folder inside the packed file is the same, R14. I've tried installing this one as well yesterday, with the same flickering result :(

Besides I wonder why they have cut the possibility to manually change display drivers in all the new versions of SPMDT? The version provided in your link is the only one I could find where you can alter these settings (saw a video on Youtube with an even older release, but can't find this one on the internet). Not that it helped at all, since the dropdown fields are always empty when I tried it, no matter what scatter file I gave it.. And I simply hate it when newer versions of programs have less features than before!

The latest I could find is 2.5.3, but like you said the project seems abandoned :( But I'll give it a try, just can't tell if I get the time today - a lot of work just came in (on friday.. damnit :D ).

[MENTION=5074219]NaturalBornCamper[/MENTION]: DG700 2nd Unit to the rescue, Sir :D
[General Questions and Answers] NaturalBornCamper:
Awesome Nudeldampf hahaha! Thanks a lot friend!

I know you guys are so tired of no custom recovery and no repartitioning that you want to revert to Android 4.4.. But After I had the sweet taste of Lollipop, I don't want to go back to 4.4! I love too much the animated gallery, battery features, general looks, etc. Can't wait to see all the tweaks there must be with Gravity Box!!!
[General Questions and Answers] Nudeldampf:
Okay.. now I've tried it on several of my PCs (Windows 7 and XP likewise) here at work and - no connection via ADB.

This is annoying as hell, all drivers work normally, but ADB simply won't. I can root the phone with vRoot, but can't get access via ADB shell. It just lists no device. And no device in ADB means no testing with MTK Droid. Can one of you guys confirm working ADB drivers and a successful device listing in the ADB shell?
[General Questions and Answers] tvladan:
yes I can. On win7 64, after installing several drivers, including the universal adb one, i finally got it to connect. unfortunately i had a clean win install several days ago on my system and i have no way to tell you which drivers i had working back than, but as and if i remember correctly the universal USB drivers for adb did the trick. also I remember that the phone should be in download mode for the correct drivers to activate. (instal quick boot apk - needs root - and restart it in download mode)
[General Questions and Answers] Nudeldampf:
Thanks! I've looked a little more and found this post, one of those (folder "All MTK Drivers"-"New inst. win7") had a working Google ADB driver, now I can see my phone in the ADB shell. Onwards! :)
[General Questions and Answers] Nudeldampf:
An update

Nope, I haven't managed it to flash a custom bootloader, but with small steps I'm pretty sure I'm marching towards it ;)

This is just a quick update of where I am at the moment. I've read a lot on different sites and tried a lot from different people and came to the conclusion that Easy Magic PhilZ Touch Installer could be our way. If I got it right it is not supported anymore by its developer Phil3759 and yuweng because too many people copied it on other sites without giving proper credit :(

But it also works for Lollipop devices and after several (soft) bricks (much thanks for your R21 build from Doogee tvladan! :) ) I'm trying to get this to work. After unlocking the bootloader I'm at the point where I need to understand how the recovery.fstab is working because this is the point where the tool hangs according to its log file. But that is not so uncommon and for that reason they have explained the process a bit in his thread. Now I just have to understand what I need to do and try it out :D

Just so you know I'm still working on it. This might take some more time for various reasons but at least I'm having fun doing this and I'm learning a lot :)
[General Questions and Answers] javlada:
[MENTION=6718315]Nudeldampf[/MENTION]

I hope you will succeed. I would really like to update to Lollipop. But I need root and a big partition for applications (6GB).
[General Questions and Answers] NaturalBornCamper:
Good work on finding these drivers! I just reinstalled Windows too and have no idea which drivers I previously had.. And Also, I tried "Easy magic philz touch installer" a few months ago when I reflashed 30 times, but I never got it to work. It would be awesome if I did something wrong however and that you managed to make it work :)

By, the way, did you see guys? R21 is now "officially" out on Doogee's servers. I just got the notification
[General Questions and Answers] Nudeldampf:
Okay guys, time for a new update!

I'm working together with Cleopatra on Chinaphonearena and got this Cyanogen 12 Mod installed and working with a custom recovery :)

So yes, this is indeed working. But to get to this point, you'll have to flash the R14 Kitkat build first (like described there) to get the PhilZ recovery installed from which you're basically upgrading to the CM12 Lollipop Android (which is still in Alpha stage with for example GPS and video recording missing).

BUT, and now comes the strange part, I could only do this on my second phone, the one which I bought from a different vendor after I thought the first one was crippled with the white lines everywhere. My guess is that Doogee has produced a new batch of DG700 on which you can't flash the old Kitkat builds without getting the white lines gibberish on screen - so maybe thats why they delivered the R21 build so fast. This "new" line has a different backplate - not this crocodile thingy, but a nice and smooth backplate. The old one (which I got working with CM12) has this crocodile plate.

So the mission is to get this custom recovery working on both version of the phone, old and new production batch. And then, better internal storage allocation (and of course Xposed Framework - which should already work with the CM12 build, will try next week).

So now I'm off into the weekend and will keep trying to break stuff next week! :)
[General Questions and Answers] NaturalBornCamper:
Wow, thanks for all that good work! I will be patient and wait for CM12 to be 100% functional or just have stock rom with a custom recovery for Lollipop, whichever comes out first.

You theory with the 2 different versions of the DG700 makes sense, I have the crocodile skin and I hope this version's better hehe.

[MENTION=6718315]Nudeldampf[/MENTION], [MENTION=4913970]tvladan[/MENTION], [MENTION=2165918]javlada[/MENTION], have you tried to make your own custom CWM Recovery as per this link? It's been so long so I forgot if I tried this one a few months back.

http://www.theandroidhow.com/2014/05/how-to-make-flash-cwm-recovery-without.html

I posted on the pages to ask if it the MTKDroidTools version posted works with Lollipop and if people tried it. But now that Doogee Released R21 of the ROM, I feel like it might be worth trying that thing out and take the opportunity to reinstall everything. So if none of you guys tried it and I get positive feedback from the users on the page, it might be our door to paradise and I'll give it a try :)
[General Questions and Answers] mikaelbrostrom:
R24 released

R24 for DG700 released in patchform:

H_T_T_P:_/_/_95._211._210_.86/ota/root_data02/hct/hct6582_L/d28a-dg-a28-qhd-wg-w850-w1900-w2100-emmc-64g8g-android5.0/en/other/DOOGEE-Titans2_DG700-Android5.0-R24-2015_08_13/DOOGEE-Titans2_DG700-Android5.0-R21-2015_07_02-DOOGEE-Titans2_DG700-Android5.0-R24-2015_08_131439778360057.zip

in that file a scatter.txt is located, maby that file and system/bin/recovery make the phone hang at Doogee 2.... after first reboot when EBR1 and EBR2 are manipulated :)

/Mikael
[General Questions and Answers] NaturalBornCamper:
Cool, where did you get this file? It doesn't seem very official :p
[General Questions and Answers] Nudeldampf:
I've tried a method like this before, but it didn't work because all I got from MTK Droid was the two errors "ERROR: No find KernelGZ" and "ERROR: no split boot image". But I don't know exactly what they mean, there are different opinions out there and no real solution it seems. And as MTK Droid is abandoned I doubt we'll ever find out :-/

But I'll try this again today with my crocodile phone. on which I haven't tested this yet.

---------- Post added at 07:22 AM ---------- Previous post was at 07:21 AM ----------

Nice, but where the heck did you get this? But I'll try it anyway I think :D
[General Questions and Answers] NaturalBornCamper:
[MENTION=6718315]Nudeldampf[/MENTION]

Maybe I tried it too and don't remember, it seems unlikely I would not have seen this before :P Still a slim chance you might succeed hehe
[General Questions and Answers] mikaelbrostrom:
Tcpdump :) when checking for FOTA, in settings->about phone->wireless update :D o got the url i cleartext, so i downloaded it..

---------- Post added at 10:42 AM ---------- Previous post was at 10:20 AM ----------

also from tcpdump :)

Version.number.

DOOGEE-Titans2_DG700-Android5.0-R24-2015_08_13

Version.size.

18.57 MB

Release.date

2015-08-15

Release.note

Improved input method: Myanmar

Fox some bugs
[General Questions and Answers] Nudeldampf:
This is great work, thanks! :)

I just came back from a meeting and had a look into the update.zip - and then it hit me that I have no idea how to install this o_O Normally I would put it onto the SD card and install it through the recovery. But with the stock rom R21 there still is no recovery, I've only achieved this through the previous Kitkat build R14 from which then one can for example flash the Alpha Cyanogen12 mod available here. Hmm.. or do I have an error in my thinking?

The content of the scatter file itself is not enough to put it into SP Flash Tool as it will reject it.

Any ideas as my brain seems to be malfunctioning? I need some food :D
[General Questions and Answers] NaturalBornCamper:
Perhaps he meant to just make a complete reflash via sp flash tools, but replacing allthe r21 files with the ones in r24, including the scatter file, then take the EBR1 and EBR2 files repartitioned.

So it would be:

1-merge r21 and r24(update.zip)

2-replace the scatter with r24

3-replace the stock EBRs with the repartitioned one

4-reflash all

It would mean it would be like flashing r21 but with the changes from update.zip, the EBRs and the scatter.

Is that what you meant friend?
[General Questions and Answers] mikaelbrostrom:
it' s a binary patch/diff between 21 and 24, and only between those.
[General Questions and Answers] Nudeldampf:
Hmm, as it is a binary diff between R21 and R24 like mikaelbrostrom said, I think there is no real way to merge these two at binary level (at least of my technical understanding with this because I don't have the knowledge and/or right tools).

Replacing the scatter won't help either because the scatter is invalid as I said, it only has 20 lines whereas the scatter in R21 contains 332 lines of code.

I suppose we won't get a complete R24 build from Doogee like the R21 estranged luckily got from them? :)

I've searched for some tutorials/explanations about signed recovery files, EBR and custom recoverys in general for Mediatek devices because my knowledge is too limited and I want to understand more of whats going on when one builds a custom rom for example. I intend to read this today and play around a bit because I hate it when I don't understand things like this I'm working with :D

Meanwhile I've been testing some custom roms Cleopatra provided me with, but all of those (except the Cyanogen12 Alpha) hat Android 4.4.2 and required the R14 build and then a modified recovery.img (based on Android 4.4) to install the custom recovery. A good step would be to get this modified recovery.img working with a stock Lollipop like the R21 :)

I need more knowledge and a master to learn from, fun I already have :D
[General Questions and Answers] mikaelbrostrom:
all the filename.ext.p has a header IMGDIFF2

IMGDIFF2 is a android format for patching images, a sampe code is here, maby some newer somewhere...:

ht_t_ps_:_/_/_code.csdn.net/u012096567/android_bootable_recovery_cn_scue/tree/anzhi/applypatch/imgpatch.c
[General Questions and Answers] Nudeldampf:
So this is a Script written in C which merges two versions of a firmware? To be honest I've never programmed in C; years ago I used to program and script a little in Basic, HTML, PHP and the like, so I'm a bit rusty on that :D

Hmm.. I think I need a compiler, but the includes in there are some more files which I need from this project. Lets see, but this is something I can't do right now, I've got to read into it some more to get more self assurance with this
[General Questions and Answers] tvladan:
I posted a request for custom TWRP here http://xdaforums.com/showthread.php?t=2798257&page=38#post62807881 ... please support me with the request ... the more the merrier :D

Hopefully somebody with the proper knowledge will help us!
[General Questions and Answers] Nudeldampf:
Wow thanks, awesome work! :)

I've tried nearly the same things as you did, unlocked the bootloader as well and all overall with the same outcome. I think the problem with PhilZ and TWRP are that they are build for Kitkat. I've got PhilZ working with a custom recovery.img as described here and it worked. But only if you flash the Kitkat R14 build first. It never worked for me with the R21 Lollipop build :( Had no success with Carliv so far either..

Flashing the R24 via ADB... well... why didn't I come up with that idea? Sometimes I'm thinking to complicated I think :D Will try it today!

As for the request at TWRP, it seems we're getting a an unlocked boot.img today as bovirus wrote following to your post :) This makes me very excited because I'm pretty sure the NO KERNELGZ, NO SPLIT BOOT errors we got from MTK Droid relate to this.

Before I went into weekend last friday (I let my phones lying at work, because there I have more time to experiment with this :P ) I tried a different approach. Since there seems to be no way to yet to get a working custom recovery installed on a stock Lollipop build like the R21 and the only available custom ROM with Lollipop is the Cyanogen12 which is still in Alpha I thought of trying building my own custom Lollipop rom based on the R21 build.

Found this Kitchen which seems pretty nice so far and is still in development. However I could not build the zip on friday because the 7zip version seems to have a bug so I wanted to replace it with an older version today and try again.

The plan in my head is flashing the R14 Kitkat build to be able to flash the PhilZ recovery. Then flash the Lollipop custom rom to hopefully finally get a Lollipop Android with a custom recovery under the hood without the recovery-from-boot.p - good to see we came to the same conclusions about that file :) At least thats what I hope to achieve :)

But still, this doesn't solve the "problem" with those two known versions of the DG700. The old crocodile backplate version which can be flashed with every Kitkat from Doogee without any problem and the new one with the smooth backplate - on which you can ONLY install the R21 build without the flickering problem. I could install the PhilZ recovery (with the custom recovery.img from the Cyanogen12 mod) on the flashed R21 smooth version though and it worked on the second try.. but it was flickering like mad again. I tried flashing something inside the recovery but gave up because it was pure luck hitting the right menu items - too much flickering :D

Hopefully we can get a solution which works with both phones, so a custom recovery based on Lollipop would be best.

Hehe, I'm still using my old phone with its crushed display because I want this custom Lollipop first before moving all my stuff over to the DG700. My colleague is laughing at me for still using the broken old phone while these two DG700 are laying on my table but I don't care - he's using an iphone for years and don't understands why it is fun to tinker with your phone like this ;)
[General Questions and Answers] Pepo1980:
On 4pda.ru is many information and patched R21 with root and big partition, custom recovery for DG700.
[General Questions and Answers] Nudeldampf:
That would be great, could you provide a direct link? I'm no native russian speaker and have trouble surfing the site with Google translating to english simultaniously :)
[General Questions and Answers] tvladan:
Thank you for this info! Please provide link to direct thread or link to direct download! Thanks !!!

---------- Post added at 11:06 AM ---------- Previous post was at 10:48 AM ----------

[MENTION=6718315]Nudeldampf[/MENTION] i understand you perfectly regarding setting up a proper system for our doogees .. so you are saying that on R21 Philz worked and you could boot into recovery after flashing, but with flickering screen? I am asking because I have a crocodile backcover type phone but no issues with the flickering system ...

Also

The recovery-from-boot.p file can be deleted once you have root access via iRoot. Just install root explorer, give permissions and delete it! Also thre is another file that might have to do with restoring stock recovery (as I found out just now, reading this:http://www.stevenhale.co.uk/main/2012/03/can-i-flash-cwm-recovery-permanently/) The file is: /system/etc/install-recovery.sh I renamed this one to /system/etc/install-recovery.sh-back. This is a script, I have no ideea if it is executed by the first file or by another ... just rename both files and you should be ok.