yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Flukester69:
Ya I tried pushing things and got permission denied but I'll try /data/local/tmp

---------- Post added at 09:01 AM ---------- Previous post was at 08:33 AM ----------

I had no problem pushing the .img to local/tmp however the dd command failed Permission denied.

C:\Users\Tom\Downloads>adb shell

shell@X10A:/ $ dd if=/data/local/tmp/x10_twrp_mmc.img of=/dev/block/mmcblk0p9

dd: /dev/block/mmcblk0p9: Permission denied

OMG I think the problem is Win10. When I press the button 8 times etc and I hear a bing from PC but nothing happens on tablet. So I look in Device Manager and there is an unknown device there. When I try and install driver from the phoenix usb flash tool it says the driver is no good. WTH. I think I'm F'd. Has anyone tried flashing the rom from the recovery on the tablet? I guess I'll try that.... I don't know.
[Miscellaneous Android Development] Flukester69:
Holy crap got it working! Works now!

So the problem for me was when you press volume button and plug it in and then power button 8 times, Windows bings, well Device Manager showed a failed device. I just "ass"umed the driver installed before. Drilling through the device tabs, it was corrupt or not installed. So I went to Properties of that device, Update driver and pointed it to the Program Files x86\USB driver folder. (By the way, there is a 4.0.0 of the Phoenix USB Pro when I checked for updates). So anyway, I tried the process over again phoenix usb pro 4.0.0 and selected the twrp image supplied in the first couple posts and pressed start. Did the funky vol button and power and 8 presses of power and Poof I now have SuperUser on 5.1.1.

Exploring to make sure everything works. SU binary needs update no biggie...

Now I am happy! Many thanks NepoRood
[Miscellaneous Android Development] Flukester69:
Well looks like i will have to reflash the ROM as TWRP included is/must be nand version not for mm block structure. When you load twrp, you can't reboot back to system because it can't read partitions. So I would assume after flashing the rom, you should manually flash twrp mmc after.

UPDATE: This was the case. So after reflashing with the phoenix program, I then pushed and flashed recovery using the mmc image.
[Miscellaneous Android Development] NepoRood:
Glad you got it going! :good:
[Miscellaneous Android Development] Flukester69:
Thanks! I have permission to port a ROM to this tablet if I choose so, I will look into it, though if you install Xposed/Gravity on this tablet, you can make up for some missing things.
[Miscellaneous Android Development] mikele2016:
stay close... this wil be out soon...... told me DragonTouch 10X Team about Marshmallow/Nougat update since two months...

I'm not sure they understand the meaning of words "soon" and "close" ...
[Miscellaneous Android Development] NepoRood:
I don't think they do either, lol. I'm putting them down for July 2017 to release MM, if ever...
[Miscellaneous Android Development] mikele2016:
death team

lol ! :laugh:
[Miscellaneous Android Development] Flukester69:
That would be very cool that they release an update. In the meantime I am looking to see if there is any way I can make a ROM.
[Miscellaneous Android Development] pensive:
I am trying to recover media files Dragon Touch X10

I used to be able to extract boot.img from a ROM and boot an Android phone using fastboot. I have been looking around the net for a solution to boot my Dragon Touch X10 using either stock recovery or bootloader so that I can access the file system. The tablet stopped booting since yesterday and I have lots of documents and videos in it. I don't want to wipe it until I explored my options to recover the file system.

Is there any ROM or update that I can use that does NOT automatically wipe out all data? Is there any other way to get into the tablet to copy my media off to a PC?

Thanks.
[Miscellaneous Android Development] NepoRood:
The X10 doesn't support fastboot :(

Do you have any ADB access? Can you boot stock recovery?

If you're a Linux user (they may have a Windows version, I don't remember), you may have another option. Use the sunxi live suite tool to reflash the factory firmware. If you tell it "NOT" to format, your data should still be there (it'll basically flash: uboot, boot and system). That was the case for me, YMMV though.

NOTE: I said "sunxi live suite" not Phoenix USB pro...
[Miscellaneous Android Development] pensive:
Trying to recover Dragon Touch X10 fs

I am able to boot into the stock recovery which came with the tablet, or bootloader (one of the options) within the stock recovery. The recovery option has an adb update option which supposedly would allow me to update the tablet with a fresh os. The concern is that it would automatically wipe all the data. I watched a youtube video about the process, and it says to backup data first before the update for this reason. My problem at the moment is that I can't backup anything because I cannot get into the tablet OS. I can only get to the recovery.

I was hoping to find something that would allow me to boot the tablet, (not burn any partitions, just boot from a PC) copy the media files off, wipe, reinstall the OS, reinstall all the media.

So, any ideas and/or links would be most appreciated. No fastboot? Damn.

Thanks.
[Miscellaneous Android Development] NepoRood:
Boot recovery, attach a cable and try to "pull" your info with ADB, it should work.

Or, try to push one of the TWRP recoveries and see if you can get that to work.

Sorry, but I've never had any issues like you're experiencing, so I'm just throwing out ideas, lol
[Miscellaneous Android Development] allaidback:
I just tested it for you...just install phoenixsuit to flash the image file and follow the prompts and make sure to select do NOT format and proceed...it does not wipe any user data or int/ext sd.
[Miscellaneous Android Development] NepoRood:
I, personally, appreciate that (I hate Windows), and couldn't remember if Phoenix did that or not, but I know for a fact sunxi live suite does :good:
[Miscellaneous Android Development] pensive:
Ok, this looks promising :) I can either boot my laptop into Ubuntu or attach the tablet to an Ubuntu server. WRT. Phoenixsuit, can you confirm the version that has "no format" option. Windows or Linux, older or the most recent one which looks different? And this is in reference to Dragon Touch X10 or another device?

Thanks.
[Miscellaneous Android Development] pensive:
Ok, got back to normal, more or less.

Just to follow up how it went in case anyone down the line might be interested. Although the tablet would not boot I was able to get into it with "adb shell" Using "adb pull /sdcard/Download" ran into a problem because some video file names had "?" or "??" in them and Windows was not able to create copies.

I had to first install busybox in /data/local/busybox, and then try to create an archive, but then I ran into space problem, since I had about 9gig to archive.

I ended up breaking up the file list into smaller pieces and did it in parts. Some file names I managed to change to not include "?" That was a lot of work to mess with file names, and it was not trivial to refer to the original names with "mv".

Eventually I "adb pull"ed the majority of stuff off as archives or smaller folders.

Using PhoenixSuit I flashed all the partitions with the stock ROM. It did absolutely nothing for the booting problem.

Then I flashed the custom recovery from this thread, the rooted ROM using the custom recovery. Although the new recovery was there, flashing the different ROM did nothing.

At which point in time I just wiped the tablet. Wiping the tablet did in fact restore it functionality. Google restored most of the apps I had there before, but NOT. Not sure why.

I am back to more or less where I was with one really annoying exception. I had like 5 different browsers with many tabs in each open, which previously persisted through even reboots. When I was running "wipe" through the custom recovery it would have been nice if the process tried to preserve the tabs.

Maybe down the line if it is not too much work, it would be nice for the recovery to attempt to preserve the tabs, i.e. copy the tab info from various browser folders into some archive on /sdcard and then restore them after the factory reset is done.

Otherwise, thank you very much to the guys who helped with advice. :D
[Miscellaneous Android Development] techjunkie2099:
Rooted X10 5.1.1 firmware v2.1rc3 build 60412 kernal 3.4.39 + Twrp recovery

X10 5.1.1 V2.1rc3_20150826 build 60412

build A83T_N106_N1061L2BC1508208.20160412

kernal 3.4.39

just got this tablet Dragon X10 UltraOcta-A83 from amazon today, replacing my old rooted nexus 7 2012 5.1.1.

history:

tried rooting with adb using pc following instructions listed in this thread that failed access denied.

tried kingo Root on pc failed access denied

tried kingo root on android first attempt locked up rebooted, then 2nd attempt rooted completed it says.

got access to dev system files with adb shell now

Can see its is a "mmcblk" device.

re rooted with kingoroot again passed.

getting a access denied when I tried push the twrp image. adb push x10_twrp_mmc.img /dev/block/mmcblk0p9 or dest /dev/block/by-name/recovery.

adb shell

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

also access denied.

I can push the image to /data/local/tmp as a test that works.

will try the Phoenix usb method next to see if I can twrp on.

so I thinking its not full root? bad kingoroot

super su and busybox installed, but fails to update supersu now?

so I am thinking thats my issue, trying to sort this out.

ok this worked for me to get twrp recovery

adb shell su

root@X10A:/ # dd if=/data/local/tmp/x10_twrp_mmc.img of=/dev/block/mmcblk0p9

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

33660+0 records in

33660+0 records out

17233920 bytes transferred in 2.172 secs (7934585 bytes/sec)

root@X10A:/ #

copied over UPDATE-SuperSU-v2.78-20160905010000.zip /data/local/tmp

booted into TWRP installed UPDATE-SuperSU-v2.78-20160905010000.zip

rebooted

now all checks out good.

100% rooted and TWRP recovery installed flashfire.

now time for a full nandroid or flashfire backup

hopefully this is helpful and clear enough for anyone else with same firmware and mmc

cheers techjunkie
[Miscellaneous Android Development] swishanon:
Hello,

Seems like something is wrong with my new X10. I type in 'adb devices', daemon starts, but List of devices attached is blank line? adb shell returns 'device not found'

HELP.

Over the past few months, it seems some devices have different names for the partition scheme, either "nand" or "mmcblk". So, the first step will be to check which type you have before installing TWRP and rooting the device. Here's how you check:

1) Connect the device to your PC, and open a terminal

2) Type the following:

# to make sure the device is recognized:

adb devices

# result should be:

List of devices attached
00000000000000000000	device
[Miscellaneous Android Development] swishanon:
nope. nothing at all. plus new development. Finally had it successfully rooted by Kingo Root after about a dozen attempts. Power ran low last night and after recharging, tablet stuck in dragon boot screen. Can access recovry and tried factory reset multiple times but still stuck on dragon boot screen. What to do now?
[Miscellaneous Android Development] NepoRood:
You need to install the Google universal adb driver, at least. If your tab is semi-bricked, your only option is to reflash factory firmware using PhoenixUSB or LiveSuit
[Miscellaneous Android Development] swishanon:
Have them installed but Phoenix USB not seeming to do anything. Is there any specific place I'm supposed to be when I plug into Phoenix? The only place I can access is recovery. If i try to reboot to bootloader, i'm on a screen that only shows dragon "touch" along with the logo. computer recognizes usd developer as device plugged in but Phoenix doesn't seem to be doing anything.

[IMG="Driver fail"]http://imgur.com/YPnmsow[/IMG]

[IMG="driver fail 2"]http://imgur.com/1nYmAFg[/IMG]

[IMG="phoenix debug vieww="]http://imgur.com/aFD6IPG[/IMG]

[IMG="phoenix debug view 2"]http://imgur.com/fM13r8f[/IMG]

---------- Post added at 10:56 PM ---------- Previous post was at 10:36 PM ----------

just tried to use adb sideload to push X10-HT-PW-V1-AL-5.1-A83T_N106_N1061L2BC_20151126.img

Got following on tablet:

Finding update package...

Opening update package....

Verifying update package...

E:footer is wrong

E:signature verification failed

Installation aborted.
[Miscellaneous Android Development] NepoRood:
Tab should be off when flashing, if you go back to the OP (first page of this thread), I posted a short "Guide" for using the flash tool...
[Miscellaneous Android Development] swishanon:
Thanks for the continued help. It was off but didn't know about the eight press thing so everytime i plugged it in, it went to stuck dragon screen. All is well now! I have the stock firmware from Tablet Express.

QUESTION. Could I use the same process for the customized rom with the TWRP and SU?
[Miscellaneous Android Development] ListlessSpectre:
THANK YOUUUU!!!!! http://forum-lw-1.xda-cdn.com/images/smilies/redface.gif

:o

This saved me about another 3 hours of trying to get root back on my X10. I had Kingo for a while and it started getting buggy, although I DID have root. I re-flashed the stock ROM back with PheonixUSBPro thinking I could just re-root it with Kingoroot's pc adb tool and it would soft brick me on a rebbot, although I was able to update everything through Google Play with no problem before hand. I tried wiping the cache first thru stock recovery...no luck. Did a complete wipe...nothing. Found this and I'm good to go. Thank you very much!! :highfive:
[Miscellaneous Android Development] swishanon:
Okay. I still can't move things to my sdcard. Thanks to you I have root. I actually used your custom rom. Problem is in Settings->Apps, there is still no 'move to sdcard' button. I have tried third party apps but they all take me back to that screen. My tablet does recognize and sdcard is mounted but I can't move anything to it!

link2sd failed to move, suggested linking but LINK TO SD CARD greyed out. says second partition not found.
[Miscellaneous Android Development] NepoRood:
Have you tried the apps2sd app? Or using the xposed module?
[Miscellaneous Android Development] swishanon:
Yes, that's one of the apps I tried. Not familiar with the module?
[Miscellaneous Android Development] NepoRood:
Me either, but, I'm sure they have one. I have Xposed on my X10, so I know their framework works. Give it a shot
[Miscellaneous Android Development] G247:
Great Thread
[Miscellaneous Android Development] NepoRood:
Glad you like it :D
[Miscellaneous Android Development] bandit97:
So back in the day I really enjoyed developing and mix mashing. Maybe a kang or two lol (Didnt know at the time).

I've always had One or neXus devices, the gold old easy days. Recently picked up Dragon Touch for a car droid, getting the itch again, and seeing how development is non existent for our device Id love to get involved.

Having an average intelligent brain I have very little room for info so Ive forgot 99% of my tricks and most of what I knew.

So Ive managed to get the factory image extracted with RickyKitchen

Ive added root, initd, busybox, zip aligned, deodexed, and some initd scripts.

Im stuck trying to rebuild it to encrypted image Any Ideas? Ive attached images of where Im at.

I see OP was trying to build a tree?

Im willing to get involved.

Heres what Im most proud of, the number 1 rom at one point lol

http://xdaforums.com/showthread.php?t=2338146

And probably my pinnacle, but contained some code that wasn't allowed I guess I kanged but made what was I imagine the better One V roms.

http://xdaforums.com/showthread.php?t=2429500
[Miscellaneous Android Development] NepoRood:
I have built trees (device and vendor), most likely not complete since the ROMs I've built won't boot...

All on my Github

The big problem, I think, is the way Allwinner goes about building and setting up their devices (it's still secret :()

You may want to look into changing your image files into fex files...
[Miscellaneous Android Development] bandit97:
Im needing to convert back to img from files. Stuck lol

Could it maybe not boot due to NAND MMC conflict? My device is MMC.

I used to be able to port roms. One thing I remember is a few folders and files were all that was needed to be replaced for a boot.

Where Im at now is finding a CM for a device with our CPU and trying to port in the libs, devices, filesystem, etc from our device. Cut and paste port lol
[Miscellaneous Android Development] NepoRood:
Last custom for an Allwinner device was 4.4.4 (KitKat) as far as I could tell...

Maybe someday we'll get something new, right now we have to settle for Xposed
[Miscellaneous Android Development] bandit97:
Would you know where that rom is? maybe I could port cm 12 into it?

So I have

Extracted factory image to FEX

Converted FEX to IMG

Extracted Image

Did my customization

And I am stuck on converting the system folder to IMG then back to FEX

Any Ideas?
[Miscellaneous Android Development] NepoRood:
There's tools for that...

I'm currently on my windows boot, tools are on linux, lol

I can check after work
[Miscellaneous Android Development] amw2320:
If I remember the system.fex image is just a .img file with a renamed extension. You should just be able to take the original system.fex, rename it to system.img, mount the image, and then make any edits as necessary. When your done, unmount, rename back to .fex, and repack into firmware.

Also, I've been trying to dive at this from a hardware standpoint and get UART working so we can have a console while trying to boot any new ROMs. So far I haven't had any luck. I've taken the device apart and tested pretty much every pad that looked reasonable while flooding the serial ports without any output. My fear is UART is disabled in the current kernel. If anyone wants to take a look or test further, I've made a page and uploaded some images on linux-sunxi.
[Miscellaneous Android Development] bandit97:
I extracted system.fex to an img then extracted the img so Im trying to get a folder back to system.fex

And Im not able to make an img out of my folder
[Miscellaneous Android Development] amw2320:
Sorry, you're correct. I haven't worked on this in a few months. I outlined how to do it in this thread awhile back and dug up the link.

The relevant part is:

system.fex -- The system image. This is a sparse ext4 partiton format. Unpack it with simg2img in android_img_repack_tools (e.g. simg2img system.fex system.img). The image can then be mounted and edited. When you are ready to repack it use ext2simg (e.g. ext2simg system.img system.fex). make_ext4fs and mkuserimg.sh did not seem to work for me.

Good luck!
[Miscellaneous Android Development] NepoRood:
[MENTION=2678971]amw2320[/MENTION]

Not sure which branch you're trying to use, but I updated the AOSP and BlissPop branches. Added busybox as you suggested, also updated BoardConfig to boot selinux permissive. Changed fstab back to nand as well in AOSP tree, left Bliss alone, so I can experiment after work.

If you're using a different branch let me know, and I can merge the above commits into that branch.

Regards,

Nepo

EDIT:

I'm in the process of adding the missing files to the vendor tree, I'm going to have to go to work before I finish though.

EDIT 2:

Found time to finish updating vendor tree :good:
[Miscellaneous Android Development] amw2320:
Awesome. At this point I am using you're modified device tree, but sadly I have never bothered learning to upload to github. I'll look into it so I can push updates of where I have gotten.

---------- Post added at 07:01 AM ---------- Previous post was at 06:50 AM ----------

Mounting now, but failing and I can't see how. Any ideas?? Log is on pastebin due to length here.
[Miscellaneous Android Development] NepoRood:
I've made a cm branch, and will try a build on my end. In the meantime, I'm going to ask a couple more "knowledgeable" friends to look at the log on Pastebin. Looks like some init errors around line 333, but could be more to it. I'll let you know what I find out.

Here's to Making Progress :good:
[Miscellaneous Android Development] amw2320:
This is getting pretty tough. It looks to me like Zygote is not starting correctly which is why I keep seeing the wake lines. I think it init.zygote32.rc is trying to start Zygote, failing and restarting.

Trying to start it manually I get:

$root@X10:/ # /system/bin/app_process -Xzygote /system/bin --zygote --start-system-server
CANNOT LINK EXECUTABLE: cannot locate symbol "_ZN7android14AndroidRuntime5startEPKcRKNS_6VectorINS_7String8EEEb" referenced by "/system/bin/app_process"...

If I replace the app_process32 build by CM with the vendor app_process32, it does a bit better but still fails:

$root@X10:/ # /system/bin/app_process -Xzygote /system/bin --zygote --start-system-server
Aborted

Its also really annoying that logcat doesn't work:

root@X10:/ # logcat
CANNOT LINK EXECUTABLE: cannot locate symbol "android_log_setColoredOutput" referenced by "logcat"...

I'm pretty sure the reason for this is CM logcat is compiled to use colored output while ASOP is not. So I am trying to use an ASOP liblog.so built for this kernel within a CM system that doesn't support it.

I wonder if some of these library incompatibilities are too much to overcome without the kernel source to recompile.
[Miscellaneous Android Development] NepoRood:
I've asked an experienced dev to take a look at the log you put on pastebin, he lives in Brasil, and it may take him a bit to look at it. Also, he don't have the device, but he's been very helpful to me in the past. Maybe he'll have some insight...
[Miscellaneous Android Development] amw2320:
ahhhhhhhh.....

I think I see what is happening. It is the libraries -- they aren't kernel dependent, but they are build dependent. Neporood, since you included all of them in the vendor files, they are being skipped from being recompiled for each build (e.g. that is why this CM build was trying to use the existing ASOP library). When I deleted liblog.so from the vendor directory it was compiled during the build and logcat is now working.

The good news is I think if we remove all the vendor libraries, so they are rebuild during a compile. Then add in only the ones that aren't being built, we may get a bootable system.

That may take a bit though.....
[Miscellaneous Android Development] NepoRood:
Let me know what you need, I think I can figure out how to add you to one of my git repos, lol...

Although, we should know already that we need the ones I added the other day, yes?
[Miscellaneous Android Development] amw2320:
I've gotten a bit farther, graphics are now working and it is booting the CM logo. However failing after that and I am having trouble tracking down the source.

Despite it not booting it sits in a loop with ADB and logcat enabled, so anyone should be able to flash this and start playing around to see if they can get further. I'm probably going to take a break for awhile.

My device and vendor trees are here. These are based off CM 12.1.

Nepo, the differences between yours and mine right now that I think matter:

Paired down vendor libs to only those not built

Original fstab working again

Missing libpvr2d.so in your /system/vendor/lib -- this is why graphics were failing

I have disabled libsoftwinner-ril in device.mk -- I don't think this matters yet, I'm failing before I get to this.
[Miscellaneous Android Development] NepoRood:
A dev friend told me that, from looking at the logs, init is a bit borked. Its trying to load density/display and can't find it. Said we should add it to system.prop, or, add the following to META inf script

package_extract_dir("system", "/system");

# after this line

run_program("/sbin/busybox", "mount", "/system");

Might do the trick without having to run a new build. I'll clone your trees and run a build in the morning after work, also will try to fix the system.prop before building.

Appreciate the extra effort you're putting into this. Maybe we'll have a working ROM soon :fingers-crossed: