yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Franzferdinan51:
I did twice actually how can I go thru and maybe find out what the issue is I will say that the problem only started after rooting but in its defense it was only 20 minuets or so before I rooted i believe I used king root

Edit so I noticed under high CPU load it seems to happen more frequently and my CPU won't go past 1608 chopped it down to 1.2ghz took it longer but still happened currently testing 1ghz I'm testing by unzipping a a 2GB Debian .IMG I'm thinking kernel issue?
[Miscellaneous Android Development] mikele2016:
Personally I would start to install a clean system... In this way if the system come unstable or freeze you can be sure its hardware problem.

For now it is may be the root, may be malware ? ... may be your power dealer ! you do not know.
[Miscellaneous Android Development] Franzferdinan51:
Well malwarebytes says it's clean as for everything else Idk but I'll try it and see what happens I guess
[Miscellaneous Android Development] mikele2016:
We are supposed to root with this simple command did you ever tried it ? :

echo "rootmydevice" > /proc/sunxi_debug/sunxi_debug

http://forum.armbian.com/index.php/topic/1108-security-alert-for-allwinner-sun8i-h3a83th8/
[Miscellaneous Android Development] Franzferdinan51:
Actually no I didn't do it that way but that's good to know I just ran king root aginst my better judgement but i did message the customer support about Android 6/7 the response was this

I will probably restore today but I want to see what they do with 6.0 if they release it then I'll be using that instead of 5.1
[Miscellaneous Android Development] mikele2016:
I think the kernel they have removed from their web site was rootable with this command line. I just bought my tablet and it come with 5.1.1 lollipop kernel 3.4.39 and not 3.4 and I can NOT root as is.

Personnaly I would try to reinstall the original firmware because It will take many time to build any 6 or 7 android version for this tablet specifically... good luck !
[Miscellaneous Android Development] mikele2016:
"you can keep close an eye to our web site"...(TabletExpress team)

Yes ... Every days ?

So now please make my day tell us that Marshmallow or Nougat is ready to download for this dragon fire ! !"/$%?&*()²¦¬¤¢£@

8-)
[Miscellaneous Android Development] MSF Jarvis:
Your day was successfully destroyed. Nothing for you here.
[Miscellaneous Android Development] mikele2016:
wait.. its only 10am here, we will see... 8-)
[Miscellaneous Android Development] NepoRood:
I wouldn't hold my breath (girl?, lol) I don't think it's going to happen this year...

That's just my opinion, anyway. I'm still working on a custom ROM though (don't hold your breath on that either), maybe I'll get it worked out before long.
[Miscellaneous Android Development] mikele2016:
Interesting. what customisation will you build exactly ?

[MENTION=2830750]Lodotux[/MENTION] For VLC I did the tweak for hardware decoding but its not convincing ...
[Miscellaneous Android Development] NepoRood:
I'm working with BlissRoms, I'm the most familiar with it. I can build it, but it bootloops :confused:

I'll be working on it again this weekend, to see what I can come up with. Also, I've been at this for a couple months now, so as I said: don't hold your breath, I wouldn't want you to pass out due to lack of oxygen! :p
[Miscellaneous Android Development] mikele2016:
blissroms w0000000 dude !

I hope that you have a good funeral arrangement ! lol

Praise the lord ! lol

Amen
[Miscellaneous Android Development] Paxster:
[MENTION=7237874]NepoRood[/MENTION] Thank You ..

Recovery Twrp 2.8.0 + V3.0.2 with SDcard Plus Usb device mmc Version. Not Nan version.

If you unsure which version is yours, Please check the Forum for Instructions.

I have Included the Option to Backup to Sdcard or Usb device Plus redone the KitKat Android V4 to Work with mmc version.

Files In Zip

X10_twrpV2.8.7.0_mmc Android V4.4 Version.

x10_TwrpV3.0.2_mmc Android V5 version

RashR.apk

1.- Root With KingoRoot.

2.- Install RashR + update it when starting.

3- Copy Recovery File to Sdcard or Internal.

4.- Start RashR and Select The Recovery.img

5.- Start Flash When Asked.

6.- Reboot To recovery.

Done.

I am sorry I cannot do the Nann version due to not having that one. I am sure NepoRood will inc the changes from these;)

Download Here

Regards

Paxster;)
[Miscellaneous Android Development] NepoRood:
The original TWRP I made for nand devices already backs up to external sd :good:

Also, I fixed the USB OTG a while back, but never uploaded it. Sorry all, but no one was complaining about it not working, lol. So I figured folks were content with just using external sd, and so am I...

Regards,

Nepo
[Miscellaneous Android Development] mikele2016:
Hi people ! If I compare the HDMI output (supposed 720p/ 1080p) between Dragon Touch 10X 5.1.1 Lollipop and my GK525 RK3188 Dongle device KitKat 4.4.2, Dragon Touch is NOT TRUE 1080p but something like 480/720p ... some artifacts on movies and icons are big ...
[Miscellaneous Android Development] jakobim:
Hello everyone,

I'm experiencing the same trouble regarding rooting as mikele2016 does: I just received my Dragon Touch X10 with Anroid 5.1.1 and kernel version 3.4.39 and was unsuccessful rooting with KingoRoot. I can't even find out the partition scheme as the command ls -al /dev/block/by-name fails with "permission denied".

Is there any known method to root this kernel version? Does anybody have the previous TabletExpress firmware versions which are rootable? Is it even possible to downgrade an Android kernel?

Any help would be really appreciated!

jakobim
[Miscellaneous Android Development] NepoRood:
Are you sure that you are in shell?

Your terminal should say "root@X10" before typing the above command.

After you confirm your version, using TWRP is the preferred method for root
[Miscellaneous Android Development] jakobim:
I probably should first cover in more detail how I did what and describe my environment:

•	Computer: Windows 7 x64 (inside a virtual machine, vmware)

•	Tablet: Dragon Touch X10, Android Version 5.1.1, Kernel Version 3.4.39, Firmware Version 2.1rc3

•	Driver: Universal ADB Driver ("ADBDriverInstaller") as USB driver, ADB.exe used from the Kingo installation directory

As mentioned above tried to root multiple times with Kingo without any success. In order to uncover the partition scheme I ran cmd.exe as Adminitrator, it gave me:

C:\Program Files (x86)\Kingo ROOT\tools>adb devices
List of devices attached
00000000000000000000 device

C:\Program Files (x86)\Kingo ROOT\tools>adb shell
shell@X10A:/ $ ls -al /dev/block/by-name
ls -al /dev/block/by-name
/dev/block/by-name: Permission denied
1|shell@X10A:/ $

[MENTION=7237874]NepoRood[/MENTION]: As you can see for me it says shell@X10A. How can I make the shell say root@X10? Was yours rooted by default?
[Miscellaneous Android Development] NepoRood:
What's running outside the virtual machine?

When you get to "shell@X10", type: su

That should put you to root.

Otherwise, use adb to flash one of the TWRP recoveries (I'd start with NAND version), then: adb reboot recovery

From there, you should be able to flash the SuperSu zip, unless you need the MMC version :p

After a reboot, you may need to flash TWRP again, but after you're rooted, it'll stay in place :good:
[Miscellaneous Android Development] jakobim:
My main system is Windows 7 x64 running -> VMWare Player running -> Windows 7 x64 (I like to keep dirty try-and-error inside a sandbox ;))

This it what gave me was:

C:\Program Files (x86)\Kingo ROOT\tools>adb shell
shell@X10A:/ $ su
su
/system/bin/sh: su: not found
127|shell@X10A:/ $

This is probably also the or at least one of the reasons why Kingo fails to root the device.

Wait, is it really that simple? Then why do we have to find out beforehand what the partition scheme is? Won't it break your device if you flash the NAND onto a MMC version and vice versa? Is it really safe?
[Miscellaneous Android Development] NepoRood:
Yes, it's safe. You can't brick Allwinner devices :cool:

Only problem you'll run into is TWRP not being able to find your partitions if you flash the wrong version. The reason for finding out your partition scheme, is to save that step.

You can also try: cat /proc/partitions

See what that gives you...
[Miscellaneous Android Development] jakobim:
OK, so if worse comes to worst I can always reflash the original firmware from the TabletExpress homepage and it will behave as if nothing happened?

What also bugs me is for me it says X10

A

while you talk about X10, is that just a typo?

shell@X10A:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name

253 0 131072 zram0
179 0 15155200 mmcblk0
179 1 12546048 mmcblk0p1
179 2 16384 mmcblk0p2
179 3 1 mmcblk0p3
179 5 16384 mmcblk0p5
179 6 16384 mmcblk0p6
179 7 1572864 mmcblk0p7
259 0 16384 mmcblk0p8
259 1 32768 mmcblk0p9
259 2 786432 mmcblk0p10
259 3 16384 mmcblk0p11
259 4 16384 mmcblk0p12
259 5 81920 mmcblk0p13
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
shell@X10A:/ $

:cool: Well, now it's pretty obvious which path to take … if I get green light from you for the question above I will try to root my Dragon tomorrow and report back.
[Miscellaneous Android Development] NepoRood:
There you go, lol (I should've thought of that earlier). And yes, if anything goes wrong, just reflash the factory firmware. I've probably flashed it 50+ times since I've got it :good:
[Miscellaneous Android Development] jakobim:
I have done quite a lot of experimenting and want to report back my findings:

Rooting the shipped firmware does not seem to be possible. What did the trick for me was to flash the firmware from the TabletExpress homepage. With that the shell also changed from shell@X10A to root@X10, and from there it was a walk in the park just like described in the first post.

There is still a major issue bugging me though: I like 5.1 Lollipop far more than 4.4 KitKat because of is usability, interface, features, etc., however there are quite a few Apps I need that do not work properly on Lollipop while working flawlessly on KitKat. So although I would much prefer to stay on Lollipop I am forced to use KitKat. However I do not want to loose the custom recovery and I don't want to root with Kingo as it forces all its virus-like Apps upon you.

NepoRood, is there any change you implement TWRP for Android 4.4.4 with MMC partition scheme? I would so very much appreciate it!

Anyways, thanks a bunch for all your help, NepoRood, keep up the good work!

---------- Post added at 04:36 PM ---------- Previous post was at 04:31 PM ----------

For those who have the same problems as me rooting their Dragon Touch X10, here is how I managed to root mine:

1) First connect your tablet via USB to the PC, then use the Universal ADB driver installer ("ADBDriverInstaller.exe") to install the correct ADB interface driver.

2) Install ADB (Android Debug Brigde), for example via the ADB SDK, ADB-tools or KingoRoot also comes with ADB in its install directory

3) Launch cmd.exe as Administrator and change the directory to where the adb.exe lies (example cd c:\tools\)

4) Now type adb.exe devices and at least one "device" should be listed for your Dragon Touch X10

5) Now type adb.exe shell. If your shell is called root@X10, your firmware is rootable and you can skip to step 7. If your shell is called shell@X10A (probably the firmware your tablet was shipped with) it is not rootable.

6) If your firmware is not rootable, follow NepoRood's instructions in the second post on how to flash a firmware from the Tablet Express via PhoenixUSBPro (or look it up on YouTube)

7) If still in the ADB shell leave it with exit, then as described in the first post you can install the TWRP custom recovery via adb.exe push …

8) I needed to copy the SuperSU.zip to the internal storage as I can not access the usbhost from TWRP
[Miscellaneous Android Development] mikele2016:
hey you all people what do you think about stock screenguard that the tablet come with from factory ? For me it seem very scrappy, and the contact between my finger skin and screen is not very good... What do you think ? if I replace it with another one brand new, is that the contact will be best or this come from screen itself (cheap plastic) ?
[Miscellaneous Android Development] ArtisLee:
Stuck on start up "Dragon Touch" screen, please help

Hello, first off thanks for all the work you have done making it possible to do all of this. I am green to this, just to warn you but I'm a quick study.

Okay my X10 is a nand device(found this using your method, thanks) that i rooted using your suggested method and I thought I had followed your directions exactly but apparently I missed something somewhere because after the final command to push TWRP my device froze on the "Dragon Touch" start up logo screen and cmd says it's waiting on my device. I did get my SDK from the new android studio (if that matters) but had no problems installing and used snoop05's adb and fastboot load(thanks to snoop05, I wouldn't have made it this far). I verified my device was connected to ADB exactly as you described and saw exactly what you posted we should see. Everything was exactly as you described until i entered the last command. I have not done anything to my tablet since this happened simply because I have no idea what will happen when I do, so it is still on the start up logo screen plugged into my PC(its only been a little under 2 hours). Any advice you can offer will be greatly appreciated Thank you very much.

Oh yes, I haven't figured out how to add "thanks" to this post but will be soon. Thanks again
[Miscellaneous Android Development] NepoRood:
Well, that's weird. Are you sure you downloaded the proper TWRP? Sorry, gotta ask, lol. Worst case, you can flash the factory firmware and bring your tab back to life (I "bricked" mine 25-30 times building TWRP) using LiveSuit or PhoenixUSB. Have you tried booting into recovery? If it's stuck at the DT logo, you can press and hold the power button until it shuts down. Then use the HW keys to try and boot recovery...

Regards,

Nepo

PS: "Thanks" is a button on the left side, bottom, of a post. It has a ":good:" on it
[Miscellaneous Android Development] ArtisLee:
No, I hadn't touched it lol. Wanted to see what you said first but I tried booting into recovery and all is well now. I have never gone this deep into it before and I didn't want to brick it permanently. Thanks so much for the speedy response and advice, I am going to give it another shot. I actually think I entered the last command slightly wrong leaving out a letter.
[Miscellaneous Android Development] NepoRood:
No worries, I'm always happy to help, especially on one of my projects/devices :good:

I'm in and out of XDA all day, lol, I only got lucky to see your post ;)
[Miscellaneous Android Development] ArtisLee:
Right on! Well, I have tried 4 more times all with the same outcome and I believe that it is not rebooting to the bootloader for some reason. I even tried booting to recovery and selecting boot to bootloader from there and it did the same thing. Do you have any thought as to what could cause this or if you think I'm even on the right track?
[Miscellaneous Android Development] NepoRood:
This tab doesn't support fastboot (ie: bootloader flashing) Maybe you're doing something wrong on your end? ADB works and the sunxi tools work, but fastboot is a no go. Where are you at on the tab right now?
[Miscellaneous Android Development] ArtisLee:
Yep that would probably be my problem then lol. I am going to start at the beginning of your instructions here in a little bit and see if I can't figure it out. I am really just playing trying to teach myself as I go but I really do appreciate all of your help so far. I will let you know how it goes when I can get back to it later. Thanks again
[Miscellaneous Android Development] ArtisLee:
This may be a dumb question but does that fact that I am using windows OS make a difference? If not then could you dumb down the process of pushing the image via adb. I have the twrp.img file along with the .sh file n the same folder as adb but the sideload command didn't work saying it can't read the img file. I also have both the TWRP.img and .sh files saved in the root directory of my sd card and tried to do it this way and even found the twrp/ when it told me to choose a package except when I hit select it just opens an empty folder and still wants me to select a package to update. If I am way off course here jus let me know so i can take a few steps back and do a lot more reading lol.
[Miscellaneous Android Development] NepoRood:
Using Windows shouldn't be a problem, as long as you have ADB setup correctly (and sounds like you do). I do believe that you are going about this wrong though, lol. The tablet should be On and Android running (like for normal everyday use) when pushing TWRP, it' not done through sideload.

After pushing, then you reboot to recovery and it should be TWRP :good:
[Miscellaneous Android Development] kuj0:
permission denied error

howdy folks. This is not my first time rooting, I've rooted HTC's before, but I am having an issue with this tablet. below is what I have done, and the returns.

C:\WINDOWS\system32>adb shell

shell@X10A:/ $ ls -al /dev/block/by-name

/dev/block/by-name: Permission denied

1|shell@X10A:/ $ ls -al /dev/block/

/dev/block/: Permission denied

1|shell@X10A:/ $ ls -al /dev/block

/dev/block: Permission denied

1|shell@X10A:/ $

any idea what's going on? If the ls -al command is denied then I won't be able to load TWRP.

Android 5.1.1

A83T_N106_N1061L2BC_1508208.20160412

performed factory reset and wiped cache partition

tried to reboot to bootloader, and I think the system froze on splashscreen...not sure though as this is the freaking slowest tablet I have ever had

Any help will be greatly appreciated
[Miscellaneous Android Development] MSF Jarvis:
Did you try issuing the su command and then trying again? Or maybe just start with adb root
[Miscellaneous Android Development] kuj0:
it's been awhile, but this is what I've done

Microsoft Windows [Version 10.0.14393]

(c) 2016 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>adb devices

List of devices attached

00000000000000000000 device

C:\WINDOWS\system32>ls -al /dev/block/by-name

'ls' is not recognized as an internal or external command,

operable program or batch file.

C:\WINDOWS\system32>adb shell

shell@X10A:/ $ ls-al /dev/block/by-name

/system/bin/sh: ls-al: not found

127|shell@X10A:/ $ ls -al /dev/block/by-name

/dev/block/by-name: Permission denied

1|shell@X10A:/ $ su

/system/bin/sh: su: not found

127|shell@X10A:/ $ adb root

* daemon not running. starting it now on port 5038 *

* daemon started successfully *

error: device not found

1|shell@X10A:/ $

tried running adb root again before entering the shell since I know it's been awhile, I think I should have done that

Microsoft Windows [Version 10.0.14393]

(c) 2016 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>adb root

adbd cannot run as root in production builds

C:\WINDOWS\system32>

I'm running command as admin too.

Going to bed, but if you have more ideas, or see something I screwed up, I'll check it first thing in the am
[Miscellaneous Android Development] NepoRood:
Are you using an "I" (eye) or "l" (el), should be a "L". Also, this has been discussed a few post back, solution:

cat /proc/partitions[/CODE

This too will tell you what type of blocks you have
[Miscellaneous Android Development] NepoRood:
You don't have to be in shell to push
[Miscellaneous Android Development] kuj0:
If you look at the last line in shell, it says "exit" because I had exited the shell.

The line I pushed on says C:\WINDOWS\system32 because I was out of the shell
[Miscellaneous Android Development] Flukester69:
Hey NepoRood,

2 questions for ya. I am experienced Android user however:

1. I never used Kingoroot, in fact I have many android devices and the process has always been twrp or cwr to flash root/rom's. Is Kingoroot just as good in the case of this tablet as twrp and flashing root?

2. Are you or have you looked into making a rom for this tablet?

Cheers!
[Miscellaneous Android Development] NepoRood:
Preferred method is using TWRP to flash SuperSu for root, and I haven't had much luck in ROM building, everything bootloops so far (AOSP, CM and OMNI)

Kingoroot is more or less and option for those that, for some reason, don't want a custom recovery.

Regards,

Nepo
[Miscellaneous Android Development] Flukester69:
Hey thanks! Kingoroot did not work for me, both thru windows and apk. When I hooked up with the usb Win10 said something wrong with my device... Maybe the cable they included with the tablet is ****? I didn't see any drivers for this device.. I'll have to look at this again on the weekend.

In regards to building a ROM did these tablet express guys release the source for their ROM?
[Miscellaneous Android Development] NepoRood:
No sources, I've had to put everything together from scratch, which is also part of the problem, lol

For drivers, mine installed automatically, I think, I haven't used Win10 in quite a while. Just make sure you have the Universal ADB Driver (from Google) installed. On Linux, the driver is: AWUSB
[Miscellaneous Android Development] Flukester69:
Ya my son infected my Win10 PC with trojans and stuff so I did a major cleanup and removed lots of old drivers... I'll grab the adb stuff again and re-install. Let you know.

EDIT: I figured out that my cable that came with the tablet was crap. I changed it and it solved the detection issues I was having. Uninstalled old adb drivers. Then I used USBDeview to clean things up further and installed naked driver. Poof I got a X10
[Miscellaneous Android Development] Flukester69:
Interesting. I try to check if i am mmcblk0p1 or nand but I get permission denied?? So I thought, ok, try su in shell but didn't work. USB debugging is on, Windows finds my device as a X10. Everything seems fine. Can't do jack with this permission denied.

KingoRoot doesn't work either... gets to 56% sits there for a while and then 73% and then failed. Thought this would be a piece of cake, lol.

Update: Sorry spent all nite on this... Ridiculous... Ok, can I not use this PhoenixUSBPro thing and flash your mmc twrp using your little guide? And what about that extended stuff you have.. the image with twrp on it.. what about flashing that??? I didn't want to go ahead yet and F up my tablet.

---------- Post added at 10:47 PM ---------- Previous post was at 09:52 PM ----------

Hey man, did you figure this out? I am having exactly same issues as you. WTF, did they lock the tablet or something? Please let us/me know.
[Miscellaneous Android Development] NepoRood:
Unlike other flashing tools, LiveSuite or Phoenix flash the entire firmware, not individual partitions. You're not going to mess up your tablet, worse case, you'll have to reflash factory firmware and setup your tablet again.

You can try the modified firmware, but that didn't work for me, I left it in OP because it might work for others.
[Miscellaneous Android Development] Flukester69:
Ya only issue I was seeing with flashing this firmware is it said Nand for twrp. Thanks for your help thus far.
[Miscellaneous Android Development] NepoRood:
Have you tried pushing anything else to the tablet? A text file for example. Or pushing the recovery to a different directory, like: /data/local/tmp

If not, let's try to simplify things, using the following steps:

1) move the recovery to the same directory as your adb, that way you don't have to type out the path to the recovery, then see if you can push it to the recovery partition (mmcblk0p9)

2) try pushing to a different directory:

adb push x10_twrp_mmc.img /data/local/tmp

3) is step #2 works, do this, one at a time:

adb shell

dd if=/data/local/tmp/x10_twrp_mmc.img of=/dev/block/mmcblk0p9

reboot recovery