Allwinner R16 (astar_d7) Android 6.0.1 Marshmallow - Partition Dump & Information

Search This thread

Trasnoastur

Member
Jul 2, 2021
13
1
Eonon GA2160 Marshmallow 6.0.1

I need help, tried everything, but I can't fix it, can you give me a solution, the steps to follow
There is a corrupt or misconfigured file, I want to reinstall the stock ROM again
Another possible solution would be to overwrite the touchscreen configuration files (what are they and in which folder are they located?)

The problems
The bottom ¼ down of the touchscreen does not work
, (touching it does nothing)
The touch io key and touch area key buttons are misconfigured, when clearing them trying to reset them (there is no assigned button, and it does not leave me, the start is in the lower touchscreen zone that it does not detect).

It is assumed that the files sent by the technical service include the entire system included
I have the files sent by the technical service:
80e9638e-9b57-11e6-ae60-17eb46db23b3
81cb828c-9b57-11e6-ad2a-df6786178d62
827ba428-9b57-11e6-8dfb-37398ea70e52.0
827ba428-9b57-11e6-8dfb-37398ea70e52.1
827ba428-9b57-11e6-8dfb-37398ea70e52.2

Correspond to the MCU:
80e9638e-9b57-11e6-ae60-17eb46db23b3
And in img format:
dmcu.img
hmcu.img

And the official installation instructions
Update steps:
1. Please download the software.
2. Unzip the file you downloaded, copy the 5 files into a formatted SD card (FAT32 format).
3. Insert the SD card into GPS card slot.
4. Enter Settings->Car settings-->system update.
5. The car stereo will start to update after selecting “extSD”.
6. The car stereo will automatically reboot after finishing update. Then reset the factory settings as following steps: Settings--->Car settings--->Reset factory (password: 7890)
7. The car stereo will automatically reboot after finishing “Reset factory settings”. Then entering Settings--->Car settings--->Extra settings(password:123456)--->Model choose--->Select
VW(5.3.19,CONFIG,BC6,NODVD,Rohm37XXX,TEF668X

Before when installing it, let me choose model, now select is blank (there is no option)

Also the MCU firmware, although when trying to install it following the instructions, it does nothing.
MCU firmware
Here is the link of MCU software:
https://drive.google.com/file/d/1mgsP9QmuZdCp_uDkz0pXFXziJH6nyYym/view?usp=sharing
And here is the video for your reference:

I have the phone rooted with Kingoroot
Wifi without internet (the message, although it connects for Google account, Kingoroot ...)
 

fawsto

Member
Apr 3, 2018
8
0
Hello @****-jones
i updated recently my HU with the links you posted V7.3.2_20200305.162050_KED1-i145-mod.rar and V7.3.2_20200305.162050_KED1-i140-mod.rar on both of them the rear camera doesn't work anymore and the bluethooth either
any way to fix them ???
 

Trasnoastur

Member
Jul 2, 2021
13
1
Eonon GA2160 Marshmallow 6.0.1

I need help, tried everything, but I can't fix it, can you give me a solution, the steps to follow
There is a corrupt or misconfigured file, I want to reinstall the stock ROM again
Another possible solution would be to overwrite the touchscreen configuration files (what are they and in which folder are they located?)

The problems
The bottom ¼ down of the touchscreen does not work
, (touching it does nothing)
The touch io key and touch area key buttons are misconfigured, when clearing them trying to reset them (there is no assigned button, and it does not leave me, the start is in the lower touchscreen zone that it does not detect).

It is assumed that the files sent by the technical service include the entire system included
I have the files sent by the technical service:
80e9638e-9b57-11e6-ae60-17eb46db23b3
81cb828c-9b57-11e6-ad2a-df6786178d62
827ba428-9b57-11e6-8dfb-37398ea70e52.0
827ba428-9b57-11e6-8dfb-37398ea70e52.1
827ba428-9b57-11e6-8dfb-37398ea70e52.2

Correspond to the MCU:
80e9638e-9b57-11e6-ae60-17eb46db23b3
And in img format:
dmcu.img
hmcu.img

And the official installation instructions
Update steps:
1. Please download the software.
2. Unzip the file you downloaded, copy the 5 files into a formatted SD card (FAT32 format).
3. Insert the SD card into GPS card slot.
4. Enter Settings->Car settings-->system update.
5. The car stereo will start to update after selecting “extSD”.
6. The car stereo will automatically reboot after finishing update. Then reset the factory settings as following steps: Settings--->Car settings--->Reset factory (password: 7890)
7. The car stereo will automatically reboot after finishing “Reset factory settings”. Then entering Settings--->Car settings--->Extra settings(password:123456)--->Model choose--->Select
VW(5.3.19,CONFIG,BC6,NODVD,Rohm37XXX,TEF668X

Before when installing it, let me choose model, now select is blank (there is no option)

Also the MCU firmware, although when trying to install it following the instructions, it does nothing.
MCU firmware
Here is the link of MCU software:
https://drive.google.com/file/d/1mgsP9QmuZdCp_uDkz0pXFXziJH6nyYym/view?usp=sharing
And here is the video for your reference:

I have the phone rooted with Kingoroot
Wifi without internet (the message, although it connects for Google account, Kingoroot ...)
Suddenly Kingoroot lost the root; and now "it is locked", although reinstalled it does not root I've tried installing Kingroot but it doesn't root either
any suggestions ...
 

pir8man

Senior Member
Nov 25, 2007
308
78
Suddenly Kingoroot lost the root; and now "it is locked", although reinstalled it does not root I've tried installing Kingroot but it doesn't root either
any suggestions ...
Try again at different times. I forget if one or both of those call on server. Trying at different times will overcome interner/server-load issues.
 

UM yes

New member
Oct 12, 2021
2
0
he guys , i have the same unit as mentioned in this thread , and i wonder if there is a way to backup frimware and MCU
 
  • Angry
Reactions: pir8man

Trasnoastur

Member
Jul 2, 2021
13
1
Figured out the main problem. Eonon sent me the 5/9/2017 firmware.
Its 6 files...
they archive is here: https://drive.google.com/file/d/0BzzboUgP8pRtTG9oMnJTMnhXRDQ/view?usp=sharing
I have de Eonon GA2160, with configure problems, the link you have don´t work. Technical service sent me 5 files
80e9638e-9b57-11e6-ae60-17eb46db23b3
81cb828c-9b57-11e6-ad2a-df6786178d62
827ba428-9b57-11e6-8dfb-37398ea70e52.0
827ba428-9b57-11e6-8dfb-37398ea70e52.1
827ba428-9b57-11e6-8dfb-37398ea70e52.2

Can you sent me the 6th file?
Thank you
 

mick_big_15

Member
Jan 12, 2008
8
0
Toowoomba
ONLY FOR PROCESSOR ALLWINNER T3!







ONLY FOR PROCESSOR ALLWINNER T3!


V8.2.3_20170902.134531_KED1-mod
https://yadi.sk/d/rsB7L-EA3MqVkQ

+ root (SuperSU v.2.79);
+ com.tw.fcam.apk (DVR);
+ removed red message "UI unauthorized, please contact the supplier";
+ other Launcher2.apk

Requires Factory reset after installation, reboot after first boot.
Hey mate, just wanted to say thanks for this post in particular from 5yrs ago haha. I have an Eonon GA2164 unit with the allwinner T3 that I really needed root access on to change the captive portal from whatever random .cn website it was set to over to google. I took a bit of a gamble but this did the trick for me, works a treat.
 

soulaimania

New member
Jun 25, 2008
2
0
I disabled BC6 and enabled BC8, restarted and now it works! The Bluetooth application shows iTopway as the device name and 1234 as the PIN. I was able to pair with it and place and receive calls.

Wifi is still weird, at one point it wants to connect to the iPhone hotspot, after a reboot it won't connect no matter what. I'll keep monitoring the logs and see if there's something interesting there.

Thanks a lot @****-jones, your support in this thread has been amazing!
Hi Clawoo,
Could tell me if you did find the solution for your rebooting after wifi issue ?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    Please note that I gave up on this unit (MTCD PX5 units are so much nicer...). I will try to update this post (however infrequently) with information that may appear in this thread or come my way by other means, but I will not seek information actively and updates will no longer be from my own experience or experiments.

    At the time of writing this head unit is available here and (probably) here. These are both custom fit for Kia Sorento, but other versions do exist; in particular several EONON units feature the same hardware configuration (model numbers GA2160, GA7153 GA7163, and I am sure others).

    Hardware-wise this seems to be the same unit as described in this thread so many tricks therein will work for this unit. In particular the USB debugging password continues to be "[email protected]" (without quotes); the extra settings password is most likely either 123456 or 668811; the factory reset and developer options passwords appear to be both 7890.

    In all the unit is an Allwinner quad core R16, with the MCU version 5.3.19-16-10-650101-161115 and System version V7.3.1-2016-11-12.100233_TW2. Here is the Droid Info report:

    Code:
    DEVICE
    Model: QuadCore-R16 (astar_d7)
    Manufacturer: Allwinner
    Baseband Version: Not Available
    RIL Version: sw-dataonly-ril-for-6.0_v1.0
    Build Number: astar_d7-eng 6.0.1 MOB30R 20161112 test-keys
    Build Fingerprint: Allwinner/astar_d7/astar-d7:6.0.1/MOB30R/20161112:eng/test-keys
    Bootloader: unknown
    Java VM: ART 2.1.0
    OS Version: Marshmallow (6.0.1)
    SDK: 23
    
    DISPLAY
    Resolution: 1024x600 pixels
    Software Density: 160 dpi (mdpi)
    Refresh Rate: 60 Hz
    
    PROCESSOR
    CPU Architecture: ARMv7 Processor rev 5 (v7l)
    Board: exdroid
    Chipset: sun8i
    Cores: 4
    Clock Speed: 480 MHz - 1200 MHz
    Instruction Sets: armeabi-v7a, armeabi
    CPU Features: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt
    CPU Governor: Not Available
    Kernel Version: 3.4.39
    Kernel Architecture: armv7l
    
    GRAPHICS
    Renderer: Mali-400 MP
    Vendor: ARM
    OpenGL Version: OpenGL ES 2.0
    
    RAM
    Total: 986 MB
    Java Heap: 80 MB
    
    STORAGE
    Internal: 12 GB
    EXTERNAL: Not Detected

    Software-wise the unit comes with a fairly stock version of Marshmallow, though as usual the operating system is a bit locked down (but to my surprise not too locked down) compared to stock.

    The purpose of this thread is to gather information about the software and possible customization for these units. I have added the information I gathered from my experience and I will update this post with any new information I manage to obtain.

    1. Partition dump

    For reference I dumped all the partitions of my device. The dump is available here. The dump was done by name (for those partitions that have a name) and symlinks point to the device name from /dev/block. Feel free to share (credit appreciated but not necessary) and please share any information that you gather from it (which will be included in this section as it becomes available).

    2. Flashing firmware

    There are multiple ways of flashing new firmware, depending on the actual unit and also its state (working, bootloop, etc.). All methods require that the all the files (three to six) that contain said firmware (see next section) be placed in the root of a SD card formatted FAT32 and inserted in the GPS slot of the unit. Some reports of the firmware being flashed from a USB stick rather than the SD card also exist; they also mention that choosing one USB port over another might make the difference between success and failure.

    On a working system inserting the card and/or USB stick and choosing "update system" from preferences will likely do the trick.

    On a system that is not working the following methods have been reported:

    • Hold Home, press Reset, and keep holding Home until the update starts (thanks).
    • A hardware solution is to short Key 1 (steering wheel controls) to ground, then press and hold Reset for 10 seconds; release Reset and disconnect Key 1 when "update" is displayed (thanks).
    • Yet another procedure might be needed for some units (thanks): Using a USB stick prepared as above and inserted in the unit, turn ignition to ACC, press Reset, turn ignition off, then after 5 seconds turn it again to ACC. A video is also available.

    3. Flashable firmware

    All the reports I have seen indicate that all the firmware versions are interchangeable. However, a factory reset will be needed most of the time for full functionality, especially so when installing firmware from a different vendor. It is VERY important however to note that the file bd07a5ee-fbb0-11e4-ae78-000c29ba27c0 contains the MCU firmware and so SHOULD NOT be flashed on incompatible devices as doing so will brick the unit (thanks).

    Partition 11 of the above dump in particular stores a flashable image. It contains the following files:

    81cb828c-9b57-11e6-ad2a-df6786178d62
    827ba428-9b57-11e6-8dfb-37398ea70e52.0
    827ba428-9b57-11e6-8dfb-37398ea70e52.1
    bd07a5ee-fbb0-11e4-ae78-000c29ba27c0

    The files 827ba428-9b57-11e6-8dfb-37398ea70e52.* in particular when cat-ed together form an ext4 file system that appear to be a copy of the system partition. This 4pda forum thread contain more information (thanks @Ahfish22); I do not speak Russian at all but Google Translate does a good job most of the time.

    Since I started this thread many people have posted many firmware versions. Here is a hopefully complete list. There might be duplicates and misses and I apologize for both in advance.

    The following set of firmware (in particular V7.3.1_20170610.110122_KED1 therein) come recommended by several users (thanks).

    EONON firmware:
    GA2162_KBT2_20170309 (thanks)
    V7.3.1_20170114.111256_KBT2 (thanks)
    EONON-R16-20170509 (thanks)
    EONON-R16-KLD20170515
    V7.3.1_20170427.104257_KBT2 (thanks)
    EONON-R16-KLD20170515 (thanks)

    KED1 (MEDEKE?) firmware (thanks):
    V7.3.1_20170216.180104_KED1
    V7.3.1_20170720.152039_KED1

    TW2 (TopWinner?) firmware (thanks):
    V7.3.1_20170111.114952_TW2-IVT+ROOT+RADIO
    V7.3.1_20161229.175327_TW2
    V7.3.1_20161201.154419_TW2

    TH6 firmware (thanks): V7.3.1_20161129.194710_TH6

    JYZC1 (Joying?) firmware (thanks):V7.3.1_20170317.114203_JYZC1

    Kaier firmware (thanks)

    Rooted KLD (Klyde) firmware (thanks):V7.3.1_20170512.203736_KLD1-0-1-mod

    4. Recovery

    Mot units do have a working recovery partition, though some are reported not to have such. The command "reboot recovery" at a root prompt (terminal emulator or ADB) will enter recovery (if available).

    Alternatively recovery can be reached with an external USB keyboard as follows: While holding Alt and Print Screen keep tapping i; the system will eventually restart in recovery (thanks pir8man) .

    It should be noted that despite the on-screen instructions the stock recovery does not react to any buttons on the head unit, but works well with an external USB keyboard.

    5. Customization

    There are useful tweaks that come with the stock operating system including speed-dependent volume and (apparently, I have not tested exhaustively) the elimination of the full-screen keyboard.

    I found this alternative to the stock radio app (context, source code) which is pretty nice except that the app force closes upon attempting to enter settings. If you speak Russian it may be worth discussing this with the developer.

    Root: Kingoroot works, though several attempts (reboot and try again) may be needed. Note that a reliable Internet connection is needed during the whole process. I do not like the extra apps and intrusive ads that come with Kingoroot. I therefore recommend once rooted to install Chainfire's SUperSU, let it update the su binary, and then uninstall Kingoroot. Note however that the current Play Store SuperSU (namely, version 2.82) may not be able to overwrite Kingoroot's su (saying instead that "the su binary is occupied"). If this is the case you may want to try version 2.79 (downloadable from here) which is known to work. Once the Kingoroot's su binary is overwritten you can upgrade to the latest (Play Store) SuperSU.

    Busybox: Installed without incidents using the usual installer from the Play Store.

    Xposed: Installed using the Xposed installer v. 3.1.1 and works well. I tried Gravity Box and Xprivacy.

    6. Outstanding issues

    It should be possible to redefine the default apps for music, video, and radio but I did not find any way to do it.

    Mapping SWC and front button panel events works to some degree (for testing purposes I mapped the "Band" button to the app drawer), but this seems to be exclusively at the mercy of the MCU, which only allows mapping to predefined actions. I could find no way to map these events to custom actions on the OS side. It was reported that button events are communicated to the OS as long as no MCU app is running. However, I was unable to reproduce this; for me no event is ever seen by the OS no matter how many (or how few) apps are running. I stopped all the MCU apps but even so KeyTest does not register any event.

    Needless to say, no custom recovery (such as TWRP) exist for these units.
    6
    I spent my day getting educated about my head unit today. From reading up on the 4pda threads HERE and HERE and finally a look at the previous model's thread HERE.

    With a fresh partition dump on a USB drive, I was set to go testing. My particular version is EONON's GA2162 Model. I loaded several versions of the OS found on 4PDA. I am currently running the latest that I found, dated 20170224. Each version worked well with the onboard MCU. At one point, I had to factory reset because my hardware buttons stopped responding. This only occurred once, but I wanted to mention it in case anyone gets stuck with this situation.

    It appears that the MCU is what really makes the hardware work with the Android system. the ROM is pretty much interchangeable between the various models based on this board. I found the included apps and icon colors were the difference between releases. Functionality was flawless on each of the 5 versions I tested today.

    I could not get PhoenixSuit or LiveSuit to operate with my unit. I believe it is because I do not have the correct cable type. Because of that I was stuck with the boot downloader to update the system partition. This went painlessly. I loaded the four flash files to the root folder of my USB stick and connected it to the head unit. Then booted to download mode.

    From the previous model thread, i found all the access I needed with:
    USB Debugging password: "[email protected]"
    Extra Settings password: 123456
    Developer Options password: 7890

    I have a DD dump of my original ROM. It is 370MB in size. I saw the requests for a post of it. Any suggestions on where to post such a large file?

    Boot Modes:
    Download Method 1: Hold "HOME" hardware button and press 'Reset" button. Release "HOME" button at update mode screen.
    Download Method 2: Short "Key1" wire to ground will force download mode.

    Recovery Method 1: Enter "reboot recovery" command from a command line (terminal or adb).
    Recovery Method 2: Attach a USB keyboard. Hold "Alt" key AND "Print Screen". While holding, keep tapping "i". When the system restarts, it should trigger a restart in recovery mode.
    5
    would you please share your launcher apk and your launch screenshot... ?

    View attachment Launcher2-mlt1.apk
    Launcher2-mlt1.jpg
    View attachment Launcher2-kld.apk
    Launcher2-kld.jpg
    View attachment Launcher2-ked.apk
    Launcher2-ked.jpg
    View attachment Launcher2-eonon.apk
    Launcher2-eonon.jpg
    View attachment Launcher2-TH6.apk
    Launcher2-TH6.jpg
    View attachment Launcher2-jyzc.apk
    Launcher2-jyzc.png
    View attachment Launcher2-tw2.apk
    Launcher2-tw2.jpg

    You should rename the file to Launcher2.apk, replace it in the folder system/priv-app/Launcher2/ and set permissions to 0644. Need root.

    Attention! Before you do that, install any other launcher. Need it, whatever your head unit is not locked, if something you did wrong.
    4
    Info & Findings

    There seems to be some confusion about which specific models this thread references. This thread references the mainboard&CPU(SOC) that is re-branded by each manufacturer for any specific head unit model. I find it easiest to think of the mainboard as the starting point. and the MCU as a secondary layer that turns on and off all the various hardware modules as we switch from them via apps. The Mainboard is generic and interchangeable. The Android OS is not generic, but IS interchangeable. Worst case is the MCU is not configured for the new OS and a factory reset is needed to get the two working together again. The MCU firmware itself is NOT generic NOR interchangeable.

    These mainboards may be attached to different screen sizes and/or button layouts. My understanding is that the MCU interfaces between the various hardware features (bluetooth, wifi, gps, radio, cameras, buttons, etc) and the Android OS. This means the MCU is specific each manufacturer that takes this mainboard and attached their own hardware modules and interface (screen, buttons). Detailed MCU information: HERE

    In my case, I have an EONON GA2162 head unit. Which is Allwinner R16 based motherboard with EONON Specific hardware modules. The MCU is programmed with KBT2 firmware to accommodate EONON's specific changes. I can change to any other released System firmware and may need to factory reset for full functionality. I can only update the MCU to newer KBT2 MCU Firmwares.

    It appears the Allwinner R16 based motherboard is the same board used in the android 4.4.4 units linked: HERE The main hardware difference between those units and ours is the SOC/CPU. Ours is AllWinner R16 (Cortex A9) based where the other units are RockChip PX3(Cortex A9) based. Our units come with Android 6.x standard simply because by the time AllWinner SOC hit the market, development had already turned to 6.x and 7.x System OS.
    w OS.

    Hardware Details:
    Hardware: Resolution: 1024 * 600
    Output power: 4 * 45W
    Cores: 4
    ROM 16 GB
    Display: LCD TFT, 6,2 / 7/8/9 / 10.1 inch capacitive 5 points
    Operating System: Android 6.0.1
    RAM 1 GB
    Main CPU: Allwinner R16 Cortex A9 Quad Core (upto) 1.6GHz
    Radio: analog 6686 with RDS
    Navigation: GPS / GLONASS

    Sytem Versions:
    This units Android system is 6.0.1, however the software versions for this unit vary
    KBT2 (EONON):
    @Pir8man V7.3.1_20170112_KBT2
    @VelvetPig V7.3.1_20170309 GA2162_KBT2

    KED1 (MEDEKE?):
    V7.3.1_20170216.180104_KED1
    V7.3.1_20170224.153853_KED1
    V7.3.1_20170103.140506_KED1

    TW2 (TopWinner?):
    V7.3.1_20170111.114952_TW2
    V7.3.1_20161229.175327_TW2
    V7.3.1_20161201.154419_TW2

    TH6:
    V7.3.1_20161129.194710_TH6

    JYZC1 (Joying?):
    V7.3.1_20170317.114203_JYZC1

    Other Downloads:
    PhoenixSuit Software: http://www.mediafire.com/file/oz5digccn3t52ee/115_cz0084d9kx1a5dm5f_4.3---4.4+刷机.rar
    KingoRoot Appliction

    Additonal Information:
    USB Debugging is password protected.
    Resolved: The password is "[email protected]". Credit to @nikko82

    Factory Reset / Developer Options password: 7890
    Extra Settings password: 123456
    Alternate password: 668811
    Note: Do NOT change the resolution of the head unit. You will destroy your unit. However it is reversible.


    Backup (ROM DUMP) Procedure:
    Code:
    Thanks to @iceglue
    1. Start TERMINAL EMULATOR2. Execute Superuser: su
    3. Go to partition directory: cd /dev/block/by-name
    4. Copy to SD Card:
    dd if=boot of=/extsd0/boot.img bs=4096
    dd if=bootloader of=/extsd0/bootloader.img bs=4096
    dd if=env of=/extsd0/env.img bs=4096
    dd if=data of=/extsd0/data.img bs=4096
    dd if=misc of=/extsd0/misc.img bs=4096
    dd if=recovery of=/extsd0/recovery.img bs=4096
    dd if=system of=/extsd0/system.img bs=4096
    dd if=private of=/extsd0/private.img bs=4096

    RECOVERY:
    No Custom (CWM/TWRP) recovery available yet for the R16 based units running Android 6.x. Also some units are being shipped without the basic android recovery. Terminal and using unix 'dd' command (with root access) to read/write partitions is the current solution for ROM recovery.

    Boot Modes:
    Download Method 1: Hold "HOME" hardware button and press 'Reset" button. Release "HOME" button at update mode screen.
    Download Method 2: Short "Key1" wire to ground will force download mode.

    Recovery Method 1: Enter "reboot recovery" command from a command line (terminal or adb).
    Recovery Method 2: Attach a USB keyboard. Hold "Alt" key AND "Print Screen". While holding, keep tapping "i". When the system restarts, it should trigger a restart in recovery mode.



    EDIT: Fixed GDrive link to Eonon Backup file
    4
    There is a modded rom on 4pda with autorun that works and is a good rom: V7.3.1_20170610.110122_KED1

    Totally agree with Petro, this tomorrow works very well and has root already.

    If you want to change the boot animation, enter 'Topway' into the external SD dialogue.

    Hi, guys!
    I made a new modded rom V7.3.2_20170801.182935_KED1.
    See changes here
    Thx.