yashsingh1/xdaforums huggingface dataset:
[Android] Protocol 9:
UPDATED: Added warning regarding UBIFS system installer for TWRP. If you are not aware, the DL701Q Tablet utilizes the UBIFS file system. You must use the the correct version of the installer, (MTK Devices w/UBIFS).
[Android] Protocol 9:
You can flash the stock recovery image from my post, but you may need to factory reset in the actual Chinese stock recovery.
[Android] Meyrinn:
I can't get booted up. I know a little about android and it's like the system is hosed somehow. I'm trying to find the stock Rom update.zip which I'm not exactly sure exists. I never had twrp recovery on it. It's got factory recovery.
[Android] Protocol 9:
Try booting into recovery (power/volume down buttons), and attempt to factory reset from there.
[Android] SockRamen:
After a break, i picked this back up again today.

I was able to initiate the correct selections to do a factory wipe via TWRP

and started over. I re-ran Iroot, and it verified i already/still had root.

I then ran MTK-TWRP in auto and then in manual.

(i do get a verification that i have UBIFS)

This time i did get a screen that asked me if i had touch problems

and then asked me to select the orientation. :good:

I thought got the orientation incorrect though, it was flipped opposite diagonally, but

at least i knew where to press to activate the intended button.

I rebooted it and re-ran TWRP in manual again to see if i had selected the incorrect orientation.

screenshot (no outside links for noobs evidently) httpee://i.imgur.com/sqQE3NL.jpg (remove the ee)

But the buttons were still flipped diagonally (Mount = Wipe, Install = Reboot and vice-versa)

I will still consider it a success, atleast i know where to press and will play around with selecting

different orientation options later and update you if i find a combo that works. Thanks again for all your help!
[Android] Meyrinn:
I've factory reset in recovery already. No luck booting.
[Android] Protocol 9:
I'm not aware of an update.zip available yet. You may want to check the SPF and MTK tools threads to find a tutorial related to the boot image and firmware. I will see if I can generate a scatter file for you.
[Android] IamNWar:
I was running into the same issue as you, I tried a few different options and found that going with the Flipped Screen Swap XY Flip Y worked for me. TWRP is running in landscape mode vs vertical but the buttons you touch are the correct ones.

Getting TWRP to load was a challenge due to a few other issues but Proto was awesome in answering questions I had
[Android] Protocol 9:
Good Job sticking with it! It is a bit of a challenge, I will add the orientation that worked for you up in the guide, as it is the same as what I got, except Normal Screen, it may be that not all units are mapped the same, and just for an FYI, this recovery does not work in portrait mode at all, so don't waste time trying to get the manual settings to force portrait...

Thanks,

Proto
[Android] mcwups1:
Great guide. I just got one, and was hoping for some development on this.

I haven't tried the process yet, because it appears some are having issues still, but any progress is welcomed.

Plus, the update I have, shows 4.4.0/A86V_004_1.

Do you think it will still work?

Thank you.
[Android] Protocol 9:
I haven't taken any updates past .004 and I don't believe I will, unless it reverses write permissions to the external SD card. Having said that, I haven't tested it. Hopefully someone who has taken the update and completed the process will chime in. I'm going to update the guide with some more specific items that people may be having issues with. I know the orientation of the recovery is the biggest thing right now, people are getting it to work different ways, so I will update the manual process to more specific actions people can do to get it right.
[Android] mcwups1:
It appears that the link provided for iRoot is broken.
[Android] mcwups1:
I tried to download iRoot, but it disappears. I save it to a specific place as an .exe file, and when I go to the folder to open it, it isn't there, even after it says it's done downloading.

When I go to the downloads page, it says the file must have been moved or deleted??

Very odd.
[Android] Protocol 9:
Update: It appears that the executable may have been updated and now may be mistakenly identified by your antivirus program as a virus.
[Android] @Numnizzle:
First time I've ever used iRoot. I keep running into a "Fail and Retry" message any ideas what's the cause?
[Android] Protocol 9:
The iRoot Database seems to have been updated to include this device now, it recognizes it as a supported device, which it didn't when I started using it. Having said that, some things to verify:

iRoot installed to your Desktop (doesn't seem critical though), I've used it right from extracting it in Downloads.....

ADB Drivers installed? (Remove all old or incorrect drivers from previous installs, if applicable)

ADB Debugging enabled on the Tablet?

Factory Reset to remove previous root attempts/installs, (if applicable).
[Android] mcwups1:
I simply cannot get this to download to my computer.

I thought I'd be smart, and download to my phone, which works, but when I try to transfer to my computer, it shows up on the desktop for 1 second, then disappears!
[Android] Shaun_vip:
Disable your anti-virus before transferring.
[Android] mcwups1:
Okay. Got Root!

Now, installing TWRP is a completely different monster.

I DL'd the Easy Magic TWRP Install Tool

I ran it. Chose Auto

Says ADB Shell is not working.

Asks then if I want to DL MTK Auto Installer?

They appear to be USB drivers, but I don't know what to do with them after?

I've used my Android folder to install recoveries and some other things, but this is obviously above my head.
[Android] Protocol 9:
[Guide]How to Root and Install TWRP Touch Recovery for Tianshi-Digiland DL701...

Edit: You can remove all the previous drivers, I think in your case, try to find any recent installs for MT65XX and HTC Dream. Reconnect your tablet to reinstall device drivers and hopefully the TWRP install tool will get shell. it should run automatic aside from the exceptions noted.

Please also verify:

1. UBIFS compatible version of installer is being used., Installed to DESKTOP, and run as administrator.

2. USB Debugging is still enabled on tablet.
[Android] Shaun_vip:
Sorry for being off topic a bit but does anyone know how to get a custom recovery on the dl1010q? I tried protos method but won't work for the 10 inch version. I'm trying to get the stock recovery for the 10 or information on a successful custom recovery if anyone can help. Again, sorry for asking about a different model. Thanks.
[Android] Protocol 9:
How did you root the 10 inch? Interesting that the recovery installer won't work, I believe it is the same architecture. I'm assuming you already tried booting into stock recovery using the power/vol down method?
[Android] Shaun_vip:
I bricked my first one rooted with root genius via pc after attempting the wireless firmware update while rooted. I have my replacement rooted with kinguser as the su app after doing the wireless update first. Supersu will not work and I have read it has issues with other mtk devices as well. I get the "no command" screen when trying to boot directly into recovery, but while on the no command screen I can vol+ or vol- and it brings up android 4 recovery (in English) I haven't found the recovery in Chinese on this tablet.

---------- Post added at 06:19 PM ---------- Previous post was at 06:13 PM ----------

Sorry proto I did find the Chinese recovery on the 10.1 as well... But still haven't been able to find a way to do a custom recovery. When I attempted following the steps for the 701 I get an error in the twrp installer. Maybe because I'm putting the stock recovery you listed for the 7 in the folder when running the twrp installer.? I'm pretty decent with Android but not sure how to extract my stock recovery from my tablet

---------- Post added at 06:33 PM ---------- Previous post was at 06:19 PM ----------

I didn't run the process in automatic first but it did ask all the prompts manually. I will attempt this again in a few hours when I get home from work and if I have the same problem I will list exactly what the error message says. I really wish there was a stock recovery and rom image for this device somewhere. It would make trial and error much safer feeling lol.
[Android] Protocol 9:
[Guide]How to Root and Install TWRP Touch Recovery for Tianshi-Digiland DL701...

If you have either the android sdk or a linux machine, you should be able to use a terminal to pull the recovery image. You might be able to restore your first tablet if you can do a nand backup on your second one in the english recovery.
[Android] Shaun_vip:
Okay after several hours of reading and trying to correct things I have found a issue on my end. I really screwed up when I attempted to root this tablet with an app called ROMaster. I did that when I first got it but shouldn't have. It has changed something I hope I can fix. It installs ROMaster ADB interface driver even when putting tablet in fast mode and connecting to pc. So I guess it pushes that driver from my device to pc? Either way I can't even manually install any other driver even uninstalling through device manager and checking "delete driver software" when uninstalling. I "added legacy hardware" through device manager and installed the driver anyway and rebooted thinking it may associate with the tablet after reboot but no such luck. I am trying to figure this out if anyone has advise? I'm thinking I may need to attempt to make a USB.uni file through sdk tools on my pc and see if that can help get this ROMaster ADB interface issue solved. Everything I have read says the ROMaster adb can't communicate properly with the device. So that would explain the error on TWRP installer. Any help appreciated I think your recovery method may work but I need to sort out the adb issues.
[Android] Protocol 9:
Ok, just so I understand, you do have root, correct? If so do you also have SuperSU installed with permissions as well? If you do you can run any number of root apps and either delete or freeze the Romaster after SuperSU takes over permissions. Check for any other Chinese apps that you may not understand the function of and do the same with them. If you don't have this: usbdeview, I recommend you install it on your pc and use it to identify all of the MT65xx, adb, HTC Dream drivers that may be installed and remove them.... once your tablet and pc are clean, try the process again. You may want to connect once in normal mode and again in recovery mode to install both drivers. You can then use a terminal to verify shell. You can get past the Romaster, I had it for awhile and didn't know. Note: The Chinese version of SuperUser has an icon that looks like a blue shield with a white horse on it, that is the one that is compatible, has english prompts and will grant SuperSU persmissions....hope this helps...
[Android] mcwups1:
Well, my computer is a virus infected pile of rubble now.

Not exactly sure what caused it, but one of the "driver downloads" popped out one trojan after another.
[Android] Protocol 9:
Well, my computer is a virus infected pile of rubble now.

Not exactly sure what caused it, but one of the "driver downloads" popped out one trojan after another.

Drivers should install automatically through your connection to the tablet. As of the posting of this guide, none of the programs cited in the process are associated with actual viruses, I have personally done this process at least a dozen times on two different tablets without incurring an actual virus. I will run through the process again to verify. If you downloaded a virus somehow, try to find the offending program and uninstall it. If it's using your browser then uninstall your browser, uninstall the program, then reinstall your browser. Just be sure that it isn't your antivirus mistaking an executable for a virus. If you can figure out what had the virus please share so others don't do the same.
[Android] Kalisie:
Hi so I just got the Digiland DL701Q tablet, and Ive been trying for a few hours to get TWRP to install properly. No matter what I do, I can not get it to ask me for the orientation setup, it gets to where it asks if my screen is flipped, I say yes, and it just installs everything from there without any more questions. Ive already tried reinstalling ADB drivers, made sure debugging is on, redownloaded the recovery, ect ect. So far nothing is working. Am I missing an important step?
[Android] mcwups1:
It was NOT one of your files. It was something that popped up from the TWRP steps.
[Android] Protocol 9:
Try this version: 2.82 TWRP, remember to run auto mode first time, then manual mode for options.
[Android] Protocol 9:
Try this version (after you get your system cleaned up). 2.8.2.TWRP. If you figure out what happened, you should report it on the install thread.
[Android] Kalisie:
Yeah I tried that one, it keeps telling me that I dont have the ADB drivers installed or USB debugging on. But USB debugging is on, and Ive tried reinstalling the drivers and couple times, its still saying they are not there.
[Android] Protocol 9:
In that case I would make sure that it is NOT an EXE file, they will trip antivirus and will be reported as Trojans, just verify before you go ballistic on your cleaning!:eek:
[Android] Protocol 9:
try installing usbdeview, look for any adb, MT65, HTC Dream etc, drivers, especially for "unknown device", get rid of them and reinstall. Have you run terminal in android sdk or linux? can you get a response to : adb devices command? or adb shell?
[Android] Kalisie:
Yeah I can access all of the ADB stuff, and I do have a response from adb devices command and adb shell. The previous version of the TWRP works fine up until the recovery loads and its all upside down and sideways. It just wont give me the option to change the orientation, the new installer wont do anything since it cant find the ADB drivers, but I know they are there and work fine for everything else.
[Android] Protocol 9:
Are you certain you are running it in manual? When it asks if you want to run auto you have to select no to run in manual mode.....
[Android] Kalisie:
Yup, running it manual. I can select what resolution to set it to (1024x600) then it asks if its flipped, so I hit yes, and it goes on its own from there with no further questions.
[Android] Protocol 9:
That is a new one... not sure what to say about that....:confused:
[Android] Protocol 9:
Does the recovery function properly upside down? if so, just leave it, you're as good as you're gonna get.....sorry, weird bug in the device...
[Android] Kalisie:
Its pretty much upside down and flipped, basically everything is in the spots that the person on the second page of this topic explained. So its usable for the most part, its just figuring out where everything is in the other sections past the main menu of the recovery that is difficult. Im sure I'll eventually figure it out though.
[Android] Protocol 9:
Ok, well either the soft buttons work or they don't, you shouldn't have to figure anything out.....I guess the menus could be more intuitive regarding the file system...:silly:
[Android] Kalisie:
I think the problem might just be that the UI is in landscape layout but the actual buttons are in portrait. I dont know how to make it so they line up, but I am starting to learn where everything is at, I just have to visualize where the buttons would be when I hold it vertical instead of horizontal. (If that makes sense.)
[Android] Meyrinn:
Is there a way to push twrp recovery on the dl701 through fastboot??
[Android] MAGICMAN516:
Aborted install

I tried automatic and manual and I keep getting a message like

Aborted, cannot repack recovery.img

Or something like that. I follow all the instructions. I have it rooted. I did that as soon as I bought the device about a month ago

the end of the log looks like this

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

20150116170828 recovery-from-boot.p exists

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

20150116170837 ubifs filesystem

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

20150116170842 Flipped Screen

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

20150116170846 MTK screen res : 1024x600

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

20150116170855 Normal Screen-SwapXY-FlipY Touch

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

20150116170855 KitKat ROM

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

20150116170858 recovery.fstab :

--------------
[Android] mcwups1:
New update.
[Android] Protocol 9:
I attempted to take the update today, however being rooted with TWRP recovery installed, it would not take. If you want the update you most likely will need to un-root and re-install the stock recovery. After downloading and attempting to install, I made a second attempt. I don't believe you will be able to update firmware OTA after root and you'd need to revert to stock first. If anyone else has been successful at installing updates without reverting or losing root, please provide details.

Thanks,

Proto
[Android] MAGICMAN516:
Mine was rooted and I installed the update fine. I did loose root.
[Android] mcwups1:
http://xdaforums.com/showthread.php?t=2816435

Digiland Android Tablet Root Anyone?

He may have.

---------- Post added at 10:57 PM ---------- Previous post was at 10:54 PM ----------

You know. I'm not sure my tablet automatically downloaded or uploaded the appropriate drivers, or any drivers, when I connected it to my Windows 8 machine.
[Android] Shaun_vip:
I suggest anyone who downloaded the update to go to wireless update in app manager and delete data(this deletes the update file). Then freeze the wireless update app in titanium backup. I did this and verified the update file is deleted. I don't want to lose root.

This will work if you have NOT ran the update only if you downloaded without installing.
[Android] Protocol 9:
New version of the wireless update available. Version V004.002 out.
[Android] kancer:
attempted ota while rooted, soft bricked stuck at no command.

stock img avail anywhere yet? yea im dumb didnt make a backup.
[Android] Protocol 9:
There is a stock recovery image in the guide.....Did you attempt to flash this from stock recovery? If so you will get a checksum error. If "no command" shows up on your screen, simply push the power button to get the recovery menu back.

I could not take the update, even after reverting to stock recovery, un-rooting and factory resetting.......I kept getting a "zip file error"
[Android] kancer:
I took ota, rebooted to no command. I cant get os to boot now. Reboot either loops digiland screen or right back to no command and recovery screen.

Sorry for my ignorance but, I'm under the impression stock recovery is the screen with the options of reboot, flash from adb, flash from sd, factory reset, ect.

You mean flash the stock recovery img from that screen? I thought they were one in the same? I think i meant to ask, is there a stock firmware img around?

Thanks for reply and any info that clears up my confusions, my lack of knowledge is embarrassing lol.
[Android] Protocol 9:
The same folks who run the TWRP thread also have a tutorial on using SPF and MTK Droid Tools for creating and flashing scatter files, you'll need this to get your firmware back. ( I meant did you attempt to flash the Wireless update through your recovery in my question. )
[Android] khadafeeee:
Does anybody know if there is a jellybean rom for this,or if not know about a way to transfer app and data to sd card...ran out of room on internal,and hopefully the DL701Q gets a section on XDA for itself .Get tutorial by the way
[Android] Kalisie:
Also, is there a stock ROM yet? I think I deleted a few important things with titanium backup, and the wireless update wont work. I keep getting a "System is damaged, wireless update is disabled!" message. Ive tried to do a factory reset several times, but it appears that even the reset isnt bringing back the few files I uninstalled..
[Android] Protocol 9:
I started to get that same message. I did finally get the update to take, without loosing root. It finally updated when I attempted to flash an experimental build of CM that I am working on porting, when the flash failed, I wiped everything and restored a V_003 (rooted) backup. After that I went ( by chance), to the wireless update and it worked, weird actually. I'm not saying that wiping your system and restoring will work, (most likely it won't), because I have also edited my build properties so that my stock rom is an now an engineering build. I can't really attribute a single cause for it to have worked....otherwise I would put the steps in here for updating, sorry. I just wanted to let people know it is possible....

screenshot

screenshot

screenshot

You can pull the update file with a root file browser and install all the updated APK's if you want to from the patch, you may also see all of the files (scatter/logo/boot), if you know how to work with them.
[Android] miketucky350:
Thats alot sir for your time. This has worked perfect for me.
[Android] Protocol 9:
Congratz-Thanks :cool:
[Android] miketucky350:
Xposed working like a champ too. If anyone is curious which download to get its the one with the numbers. Which is the 2nd one listed
[Android] Protocol 9:
Yeah, although the screenshot shows version 2.7, version 2.6 is the stable release for the Framework....
[Android] SYN1ST3R:
I have a rooted DL701Q and was not able to do the wireless update because I receive the message "Your system was damaged. wireless update is disabled!" So now I'm interested in trying to apply the updated APKs manually from the patch. I copied the "update.zip" from the wireless update to my computer. This is the folder structure:

[ ] - folder

[update]

[META-INF]

[patch]

[recovery]

[system]

build.prop

logo.img

scatter.txt

SEC_VER.txt

type.txt

uboot.img

What & where do I apply the updated APK files to update my device? I see under [update] - [patch] - [system] - [app] & [priv-app] there are APK files with a "p" at the end (example: "ApplicationsProvider.apk.p" ) should I just remove the "p" after each APK file?

Thank you for your help!
[Android] Protocol 9:
I just installed the new ones in ->System->App with a file browser... I didn't mess with the apps/odex files in the Patch folder....
[Android] miketucky350:
I updated mine while rooted. Also I deleted some system apps and stuff. I wonder if Theres some authentication that can be removed. So we can just manually flash in recovery. Wether it be stock or twrp
[Android] vampirefo:
Has anyone successfully built a working recover? If anyone has why not upload it for other users? no need for everyone to have to build their own. All that is needed is for one person to build a working recovery and upload it for others.
[Android] vampirefo:
Can you upload the update.zip?
[Android] vampirefo:
Yes you can if you have the update.zip

My tablet is newer and is already upgraded so no way for me to get the update.zip. I need the update.zip to be available to make a flashable stock ROM.

This is my version.
[Android] vampirefo:
The easiest way to root is to flash custom recovery then download and install SuperSU v2.46

I ported carliv ubifs recovery, cause twrp is well lame, lol.

Then just boot into fastboot and install custom recovery, then reboot download SuperSu place on micro sdcard boot into recovery and install SuperSu.

http://xdaforums.com/showpost.php?p=23427715&postcount=1
[Android] Protocol 9:
Update.zip

Sorry folks, I haven't been on for awhile, link to the update zip as requested.... contains boot, logo img's, system/build.prop and patch files....

Thanks,

Proto
[Android] kn333:
Chicken soup for the soul

Thx for that proto. My problem is that I bought mine already @ 4.4.3, have not been able to root. Ran

fastboot getvar all

and it spit out a bunch a mumbo jumbo (pronounced moombo hoombo) including calling it's self "mid713l-lp-lvds-20141226". So I used TFSE and found THIS: ALL the image and scatter files etc in a zip called "mid713l-lp-lvds-20141226.zip - 251.48 MB" found it on a Chinese website. I CAN'T POST LIVE LINKS SO......eichteeteepee://www(dot)multiupfile(dot)com/f/ff1c4c48