yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] amw2320:
After throwing that earlier log up, I realized that I was getting a successful kernel boot with a transition to system startup via zygote. So I don't think we need to dig to deeply into that kernel dmesg anymore. The current dmesg output looks pretty good (aside from the camera which I think is unplugged from when I had the tablet disassembled.

Most recent logs:

dmesg

logcat

There are a few errors in there, but the only fatal one you'll find is this:

F/MediaProfiles( 494): frameworks/av/media/libmedia/MediaProfiles.cpp:970 CHECK((fp = fopen(xml, "r"))) failed.
F/libc ( 494): Fatal signal 6 (SIGABRT), code -6 in tid 494 (main)
I/libc ( 494): Suppressing debuggerd output because prctl(PR_GET_DUMPABLE)==0

**EDIT** - For future sunxi builders -- I fixed this error by including system/etc/camer_cfg folder in vendor files. MediaProfiles is looking at camera configuration files as well.

I believe that MediaProfiles.cpp is a build file for libmedia.so.

I tried replacing the built libmedia.so with the original from the stock image, but then had issues with libmedia_jni.so.

Then, I tried to replace libmedia_jni.so as well, which gave me a bunch of errors, then failed at installd.

I then replaced installd and the failure is at:

E/AndroidRuntime( 1139): *** FATAL EXCEPTION IN SYSTEM PROCESS: MountService#onDaemonConnected
E/AndroidRuntime( 1139): java.lang.IllegalArgumentException: Failed to find storage device at /storage/emulated/0
E/AndroidRuntime( 1139): at android.os.Environment.isExternalStorageEmulated(Environment.java:862)
E/AndroidRuntime( 1139): at android.os.Environment.isExternalStorageEmulated(Environment.java:846)
E/AndroidRuntime( 1139): at com.android.server.pm.PackageManagerService.isExternalMediaAvailable(PackageManagerService.java:9096)
E/AndroidRuntime( 1139): at com.android.server.pm.PackageManagerService.startCleaningPackages(PackageManagerService.java:9136)
E/AndroidRuntime( 1139): at com.android.server.pm.PackageManagerService.updateExternalMediaStatusInner(PackageManagerService.java:14178)
E/AndroidRuntime( 1139): at com.android.server.pm.PackageManagerService.scanAvailableAsecs(PackageManagerService.java:14073)
E/AndroidRuntime( 1139): at com.android.server.MountService$3.run(MountService.java:889)

**EDIT** - fixed this error by adding symlink /mnt/shell/emulated/0 /storage/emulated/0 to init.sun8i.rc and adding overlay to /frameworks/base/core/res/res/xml/storage_list.xml from the allwinnner SKD (i used the octopus-ibt overlay)

Maybe I need to hunt further up the chain, or maybe that is not the issues that is stopping boot in the first place.
[Miscellaneous Android Development] techjunkie2099:
no vpn on Dragon X10 5.1

one last effort no replies, and after multiple wipes all parts on factory 5.1 and 5.1 off website , now using the custom X10-V2-5.1-amw-TWRP_SuperSU.img (Created by: [MENTION=2678971]amw2320[/MENTION], has TWRP (nand) and SuperSu already installed)

results = failed , it connected to the vpn server and authenticated ok gets ip, but no routing, no data transferred , my tests show all the 5.1 tablet express roms and do not have a working support for open vpn clients apps.

Bit vpn works in 4.4 just fine? but way to to sluggish so I will stick with 5.1 custom and just use tor orbot, man I tell ya what a waste if time this was.

seems like there are openvpn routing errors bugs on android HTC builds in the past 2012 that sound very similar to this.

I will have to take the rom apart myself and research this further

QUOTE=techjunkie2099;69514252]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[/QUOTE]
[Miscellaneous Android Development] JBVGAMER:
Downgrade

Is it possible to downgrade from 5.1.1 on this tablet to 4.4.x? Thanks
[Miscellaneous Android Development] NepoRood:
Yes, just flash whichever firmware you want. Firmware is available at Tablet Exress website, there's a link on the first page of this thread.
[Miscellaneous Android Development] amw2320:
I haven't gotten any further, but if anyone wants to debug as well I wanted to post the image which was hacked to output UART over the microSD slot. This gives you the kernel log and logcat even if ADB does not load.

This image is flashable with LiveSuit or PhoenixSuite:

image

Note: this works with NAND, not sure about MMC

I am using this uSD breakout board linked here.
[Miscellaneous Android Development] mikele2016:
supposed to update to marshmallow end december... but its an another lie
[Miscellaneous Android Development] amw2320:
Some progress

So I made some progress over the holidays to the point where I can now boot into CyanogenMod 12.1 startup (asking me to select a language). Horray! That being said bluetooth errors take over the screen immediately and the screen is nonresponsive. I can't tell if the touchscreen isn't working or if everything has just been taken over by the fast repeating bluetooth errors.

I have not updated the device and vendor files on github as I am using a modified version of allwinners already heavily modified SDK. If I can get it to the point where I can boot and have some interaction (I'm currently compiling a build that should be bluetoothless), I'll try and figure out a way to get all of the changes into the device directory.
[Miscellaneous Android Development] amw2320:
The link below is what I have so far:

CyanogenMod 12.1 X10

When you install CM will boot to the Select Region screen.

The touchscreen is not working, and I don't know why. The module is loaded, and I don't see any big errors anywhere in the log.

In addition there is a bluetooth error that is repeating. If you want to get rid of this while troubleshooting, delete (or rename) /system/lib/hw/bluetooth.default.so

You can force going to the homescreen with

adb shell monkey -p com.cyanogenmod.trebuchet 1

Below is the only issue I see with the touchscreen, however it appears to recover on its own finding the correct size.

I/InputReader( 490): Device added: id=-1, name='Virtual', sources=0x00000301
I/InputReader( 490): Device added: id=6, name='sunxi-keyboard', sources=0x00000101
I/InputReader( 490): Device added: id=5, name='headset', sources=0x00000101
I/InputReader( 490): Device added: id=3, name='axp81x-supplyer', sources=0x00000101
I/InputReader( 490): Touch device 'gslX680' could not query the properties of its associated display. The device will be inoperable until the display size becomes available.
I/InputReader( 490): Device added: id=1, name='gslX680', sources=0x00001103
I/InputReader( 490): Reconfiguring input devices. changes=0x00000004
I/InputReader( 490): Device reconfigured: id=1, name='gslX680', size 1366x768, orientation 0, mode 1, display id 0
I/ActivityManager( 490): Config changes=8 {1.0 ?mcc?mnc en_US ?layoutDir sw548dp w933dp h523dp 224dpi lrg long land ?uimode ?night finger -keyb/v/h -nav/h s.4 themeResource=null}

It may be half working. If you keep taping the screen, it will not turn off. And if you touch the screen when it is dimmed, it will occasionally lighten again.

It may sense the touch, but does not know the correct position?

Any ideas Nepo?

Well it looks like the touchscreen is somewhat alive. If you adb in and type:

cat /dev/input/event5

any touch on the screen is recorded with gibberish. Looks like the module is loaded, but android doesn't know how to read it????

The only difference I see from a stock logcat is that the stock shows

I/ActivityManager( 480): Config changes=8 {1.0 ?mcc?mnc en_US ?layoutDir sw768dp w1366dp h695dp 160dpi xlrg long land ?uimode ?night finger -keyb/v/h -nav/h s.4}

The display size being incorrect does make sense for the pointer not working, but everything looks good, and I cannot see where ActivityManager is reading these values.
[Miscellaneous Android Development] NepoRood:
Drew, upload your changes to git, so I can see what you've done and compare it to mine. Also, I've been flashing all my builds with TWRP, I haven't got as far as you though, as I'm still stuck at CM logo...

~Nepo

PS, Also, been a few days since I've done anything, I have a active device to maintain for AOKP :D
[Miscellaneous Android Development] amw2320:
I've uploaded changes, but I'm not working off a normal CM tree. You'll need to add a few more things from the allwinner SDK. I used the one here (Yes that is an 18GB zip file).

There are a few directories you need:

device/softwinner/octopus

device/softwinner/octopus-common

hardware/aw/

These may be able to be forked from https://github.com/pine64-android/device-softwinner and https://github.com/pine64-android/hardware-aw, however I don't know which SDK these came from and if there are differences between the trees.

After adding these directories I have disabled multiple Android.mk files due to build errors I could not fix:

hardware/aw/audio/octopus/Android.mk.disabled

hardware/aw/hwc/octopus/Android.mk.disabled

device/softwinner/common/hardware/camera/Android.mk.disabled

device/softwinner/common/hardware/libhardware/libsensors/Android.mk.disabled

This is why I still have files like system/lib/hw/audio.primary.octupus.so in my vendor branch. But I think it is also why audio is failing.

--- off topic of how to set this up, but dlopen failed: cannot locate symbol "pcm_get_node_number" referenced by "libcodec_audio.so"...

Finally in I commented out a few lines:

device/softwinner/octopus-common/sepolicy/genfs_contexts - I commented out the line genfscon fuseblk / u:object_r:sdcard_external:s0

device/softwinner/common/common.mk - I commented out #DEVICE_PACKAGE_OVERLAYS := \

Again my GIT knowledge is poor, so this isn't the pretty way to do this. It should get you to the same place I'm sitting right now though.
[Miscellaneous Android Development] NepoRood:
Thanks, I'm going to fork, then re-sync my repos. I appreciate all the effort you are putting into this :good:
[Miscellaneous Android Development] amw2320:
touchscreen issues

I posted to a dev forum for more help on the touchscreen here.

It goes into significantly more detail.

Everything looks good to the point where I almost wonder if the touchscreen is working that the screen is just constantly frozen. Maybe if someone has a mouse they can plugin we can see if that is the case. Who knows.
[Miscellaneous Android Development] nickhere:
Thank you all for doing the work. I wanted to learn how to right my own firmware. We need updating and tweaking. Maybe even marshmallow. Another thing to consider turning this into a Ubuntu tablet. Also does this tablet have gps but not enable.? Some of the diag apps says it does.
[Miscellaneous Android Development] amw2320:
Looks like it is a touchscreen issue. A mouse works fine.

Nepo, I updated my build again. Having recovery.fstab in root/etc/ forces the /etc folder to be created by the ramdisk. This directory should just be a symlink to /system/etc. When init.rc tries to create the symlink it can't as the directory already exists, so mulitple config files are not being detected. This fixed a bunch of errors. The system is now pretty stable after you disable the bluetooth module. Still no touchscreen however.

Wifi is not being up yet, but I am able to insert the module without errors. After that there seem to be some wpa_supplicant issues that I haven't looked into. Seems like were getting there though.
[Miscellaneous Android Development] NepoRood:
Awesome work man, You'll probably figure it out before I do, I'm not gonna have much time this weekend to work on it.
[Miscellaneous Android Development] amw2320:
If anyone is following along. Progress is going to halt for awhile. I am heading out of the country for the next month, and just got a new tablet for that trip. I'll respond to questions, but not going to be working on this.
[Miscellaneous Android Development] nezlek:
Partition Info ?

Verify Partition Scheme

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

# Now type:

adb shell

# followed by:

ls -al /dev/block/by-name

# First Line should be 1 of the 2:

# This is a "mmcblk" device
lrwxrwxrwx root root 2016-07-20 00:08 UDISK -> /dev/block/mmcblk0p1

# This is a "nand" device
lrwxrwxrwx root root 2016-07-20 00:36 UDISK -> /dev/block/nandk

First, thanks for an extremely useful post. Very well written and informative IMHO.

For those seeking to apply this wisdom to other cheap Chinese tablets with Allwinner CPUs .....

Have an Allwinner 83T tablet - an AstroTab A10 - running Android 5.1.1. The method you offered for determining the Partitioning Scheme doesn't work with it. I've seen some convoluted configurations, but this one is a contender for a prize. The adb shell rejects the request, presumably because the device is not yet rooted.

HOWEVER, an alternative approach (apparently) is to examine the details in the file systems. Using adb, PULL-ed what I could, and beginning at the sys folder, followed the path to fs, to ext4, where I found folders for mmcblk0p1, mmcblk0p7, mmcblk0p10 and mmcblk0p13 . PRESUMABLY this means it is an "mmcblk" rather than a "nand" device. Guess it is time to cross my fingers and spin the prayer wheel. :cyclops:
[Miscellaneous Android Development] swishanon:
WOw. Gave up on it for a while and checked back today to see if anything has changed and stunned. It may not be working but grateful you guys are trying. Thanks again for previous help. Tablet slow now cause almost out of space since could never transfer to SD was going to write and start over but glad I checked in.
[Miscellaneous Android Development] nezlek:
Identifying the recovery partition

For those trying to apply this approach to Allwinner A83T devices other than the Dragon Touch, parsing through the various partition schemes - and let's face it - no two devices would EVER be the same :( - is really annoying (to put it very politely). It might be useful for folks who have identified which blocks / segments / partitions / whatever might actually be the one we want to try and flash a recovery to - to share their experience & results with their particular tablet(s). Typically, a stock recovery partition seems to run around 8 to 10 MB in size, plus or minus a few, so on one such device (an Astro Tab A10), executing the command (from an adb shell)

cat /proc/partitions

returns the following info about partition sizes (# blocks):

zram0 13,1072

mmcblk0 15,155,200

mmcblk0p1 12,808,192

mmcblk0p2 16,384

mmcblk0p3 1

mmcblk0p5 16,384

mmcblk0p6 16.384

mmcblk0p7 1,048,576

mmcblk0p8 16,384

mmcblk0p9 32,768

mmcblk0p10 1,048,576

mmcblk0p11 16,384

mmcblk0p12 16,384

mmcblk0p13 81,920

mmcblkboot1 4,096

mmcblkboot0 4,096

mmcblk1 31,276,032

mmcblkp1 31,271,936

On some of these Allwinner tablets, there are dozens of partitions, and Lord only knows why, other than to make for an arbitrarily convoluted configuration that is more difficult to root or flash a custom recovery to. In THIS case, if we assume a (typical) block size of 512 bytes, we can at least eliminate some unlikely places. Some are too small and others too large. Perhaps simplistic reasoning but at least a starting point. :confused:
[Miscellaneous Android Development] NepoRood:
Did you try:

ls -al /dev/block/by-name
[Miscellaneous Android Development] nezlek:
I did indeed. Permission denied. I obviously need to get the thing rooted first. It has stubbornly refused my efforts to date but if all else fails I'll threaten it :laugh: At this point it is still more of an intellectual challenge than a necessity, but I like a challenge.
[Miscellaneous Android Development] nezlek:
any chance?

Any of you nice folks working on this project aware of an image un- / re- packing tool that will work on the Allwinner ROM image(s)? My arsenal is geared toward MTK and Snapdragon devices. The folks at Allwinner clearly seem to want to make this as convoluted as humanly possible. :confused:

Also having quite a "bother" trying to root this thing. It has a slightly newer build than the Dragon and clearly the folks at Allwinner closed off the exploits used by Kingoroot, which will get to 90% on the .apk version and 37% on the PC version, then hang and die.

Suggestions welcomed and actively sought
[Miscellaneous Android Development] blakegriplingph:
From what I can attest, ROM repacking on Allwinner devices is indeed convoluted. You'll need a donor ROM from a similar device and a special tool to cook a backup for it to be read by PhoenixSuit. I know a friend from a suburb near Indianapolis who used to do this stuff on A31s and so on, but he's retired afaik.
[Miscellaneous Android Development] NepoRood:
Try this: Link

I've had success with it :good:
[Miscellaneous Android Development] nezlek:
Still no joy .......

Thanks, but I already tried that one - no success. It might be because I am stuck with a Windows 10 system at the moment (Geez, but that really SUCKS) and the tool(s) would be happier on a Linux-based desktop, but for whatever reason I am stranded for now. :(
[Miscellaneous Android Development] allaidback:
can't you just root by flashing supersu in recovery?
[Miscellaneous Android Development] nezlek:
If only .....

That would presume you could flash a non-stock recovery to the thing to begin with. It would require an unlocked bootloader, which most Allwinner CPU tablet makers seem to equate with giving the Nuclear Launch Codes to WikiLeaks. I've pretty much given up on (Astro-Tab) the vendor. They seem to have ZERO interest in anything beyond the stock box, and won't even help to work around the fact that their older version of the very same tablet won't accept their own Marshmallow update. There are LOTS of inexpensive Android tablets out there. No need to be stuck with one that won't do what you need it to. ;)
[Miscellaneous Android Development] peonpete:
First off i want to thank NepoRood and others who worked on rooting this device and putting a recovery on it. This is what makes Android phones/tablets of all varieties so interesting!!

With that said, I am having a issue though but its really nothing to do with the root or TWRP. The issue I am having is that in the battery tab, i notice that "Cell Standby" is using up a huge chunk of my battery life. At worst it is around 30% usage and at best 21%, so clearly something is going on there. I also checked the IMEI tab in settings, and i believe in this tablet it should say "nothing or none available", but my status says "unknown".

I downloaded "System app remover (ROOT)" and removed the Phone.APK and MMS.apk [i believe thats the name] and the problem still persists. Anyone else have this issue, or know how to fix it?

---------- Post added at 05:39 PM ---------- Previous post was at 05:14 PM ----------

I know this is a old post that i am replying to, but i had the exact same problem as you. If you flash the custom firmware on the first page, its nearly a 900mb download, you will be rooted and have TWRP already installed. Thats what i ended up having to do because i had permission denied even when trying to flash the recovery.
[Miscellaneous Android Development] NepoRood:
lol, I'd almost forgot about this device :o

I got it for the sole purpose of "learning Android", just like the RCA devices I had before it. I've came a long way since then :cool:
[Miscellaneous Android Development] peonpete:
Any idea about the "cell standby" using up some of the battery?
[Miscellaneous Android Development] NepoRood:
More proof that it's a "bloated" and "fictitious" number. You're using a tablet, how can you have cell standby? The CSB bug has been present since Lollipop, I hear they fixed it with Oreo...
[Miscellaneous Android Development] peonpete:
I installed Titanium Backup and removed the "Cellular Data Apk" app, and the Cell Standby has went away. Its still using the same battery percent though, so it was as you said a display bug. :)