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

Search This thread
By:
Advanced…
P

pir8man

Senior Member
Nov 25, 2007
328
89
Samsung Galaxy S21
Samsung Galaxy S22
lodewj said:
I can't seem to get this unit rooted.
So far I've tried kingroot who said it failed after a while. I have done a request for this device. It was the 4th request.
Then I've tried kingoroot. Also following the suggestions on 4pda. Everytime after 90% my unit reboots (doesn't give an errorscreen).
I've tried to install supersu and chainfire's su. but so far no succes.

Does anyone have more suggestions?
Click to expand...
Click to collapse

The only time i had repeated failures with Kingoroot is because the app needs a good internet connection. A weak signal causes too long of timeouts for the script to run properly.

As for your MCU related issues have you gone through the 'Extra Settings' and 'Devloper Options' menus thoroughly? Aside from the updates and resets you have done, i don't know what else you could do. Aside from wait for a working update to arrive.
 
P

PittBrad

Member
Sep 26, 2010
31
0
I have a Allwinner R16 astar_y3 with Android 5.1.1
My HW_ID is 34. Unfortunately i don't know which manufacturer it is.
I have rooted it with kingoroot.
Can i flash 6.0.1? Somewhere i have read that a downgrade to Android 4 should be the first step.
Don't know if this is true. Maybe somebody can help....Thank you!
Br, Martin
 
Raiderman

Raiderman

Senior Member
May 27, 2010
771
619
Nampa, ID USA
I was able to root my AHU, and decided to start customizing.

I can't get the stock launcher to go to the 12hr clock.

.
 

Attachments

  • tmp_19938-20170422_135709868773811.jpg
    tmp_19938-20170422_135709868773811.jpg
    254.3 KB · Views: 584
A

alikro

Member
Sep 22, 2013
28
5
lodewj said:
it seems like bd07a5ee-fbb0-11e4-ae78-000c29ba27c0 is the mcu (16MB in size) .
I've got a mcu update from my seller and the filename has exactly that name and has no file extension.

The instructions I've got from the seller:
Click to expand...
Click to collapse


How did you the update ?
I also got a file like this, but i have no idea what to do
 
L

lodewj

Senior Member
Aug 27, 2008
73
4
Aarschot
Copy it on a fat32 USB stick.
Choose update system from the extra settings.
After the update, go tot the extra settings an choose tour car from the mcu list.
 
A

alikro

Member
Sep 22, 2013
28
5
Last edited:
  • Like
Reactions: sbruda
R

RyanFleming

Member
Oct 7, 2013
8
3
50
Northwest Indiana
www.RYEInc.biz
Successful Root Eonon GA2162

Here is my experience of rooting an Android 6.0.1 Head Unit.
My best guess is all the Eonon Head Units they are selling are the same hardware, just different shaped Plastic, but of course I don't know for sure.
Rooting can be dangerous so if my steps below mess something up I feel your pain, but take no responsibility for it.

Eonon GA2162
Processor Type: QuadCore-R16
Android Version: 6.0.1
MCU Version: 5.3.19-108-10-943101-170313
System Version: V7.3.1_20170317.110558_KBT2

I don't have stock images to go back and try this again, so I can't be %100 sure of the exact way to do it. But here is what I did.

1. I installed KingOroot.apk and ran it many times (and reboots), it failed each time. When you install it you get a warning, if you cancel the warning, another prompt comes up, allowing you to still install it, even without enabling unknown sources. I think this is an Android 6+ feature.
2. I installed Chainfire SuperSU, tried installing it normally several times (and reboots), failed each time.
3. I figured out the password to gain Developer Options, (plus other passwords see towards end of post) : 7890
4. I went to settings, pressed developers options and typed the code.
5. Unknown sources was already checked, I turned on the Unlock Bootloader Option and accepted the "scary" warning.
6. I ran KingOroot.apk again, it got %90 complete and failed.
7. I rebooted and tried again, same thing happened.
8. I rebooted and noticed another supersu was installed next to the Chainfire one.
9. I removed the SuperSU from KingOroot.
10. I ran the install for ChainFire and it succeeded.
11. I removed KingOroot.

I have successfully powered the unit a few times and root is sticking.
****************************************************************************************************************************************

Most likely the proper way to do it is below:
1. Go into developer options, turn on Unknown Souces and Unlock Bootloader.
2a. Either Run KingOroot and either select install software (to use the SuperSU that is installed by the app)
2b. Or Run KingOroot without the install software, Then Use ChainFire SuperSU to install normally.
3. Reboot the Head Unit and it should be rooted.

****************************************************************************************************************************************

Passwords given by request from Eonon:
Extra settings code: 123456
Developer options code: 7890

Password I used from this thread to enable USB debugging: john@tw-desktop

****************************************************************************************************************************************

If I can get my hands on a copy of the recovery image, I will try and flash TWRP onto this in the near future. But I need a way to get
back in case it does not work, and I am unsure how to make a backup of the recovery image. I will try and figure it out on my own in the next day or so, and report back what I find.

Happy Rooting...

Ryan
 
Last edited:
  • Like
Reactions: Jleeblanch
P

pirulazul

Senior Member
Jan 10, 2015
131
35
Samsung Galaxy Tab 4
Xiaomi Poco X3 NFC
Well, after tons of trial and error with the keys issue, it seems like key functionality is not controlled by Android itself. No file refers to it, no file is modified when I change the settings, so it seems like the mcu is being modified and this makes things harder to modify the apps that each button brings. Right now i think I hit a wall. I only managed to change boot logo manually, boot animation a remap some keys like play pause, and some others.
 
P

pir8man

Senior Member
Nov 25, 2007
328
89
Samsung Galaxy S21
Samsung Galaxy S22
RyanFleming said:
Here is my experience of rooting an Android 6.0.1 Head Unit.
My best guess is all the Eonon Head Units they are selling are the same hardware, just different shaped Plastic, but of course I don't know for sure.
Rooting can be dangerous so if my steps below mess something up I feel your pain, but take no responsibility for it.

Eonon GA2162
Processor Type: QuadCore-R16
Android Version: 6.0.1
MCU Version: 5.3.19-108-10-943101-170313
System Version: V7.3.1_20170317.110558_KBT2

Ryan
Click to expand...
Click to collapse

Ryan: Can we get a ROM dump of your unit? You have newer System & MCU than i do for my same EONON based unit. I am running the update posted by VelvetPig in this thread, dated 20170309. I would like to see if yours dated 20170317 might solve some minor glitches I have been working around.
 
P

pir8man

Senior Member
Nov 25, 2007
328
89
Samsung Galaxy S21
Samsung Galaxy S22
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 "john@tw-desktop". 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
 
Last edited:
  • Like
Reactions: ZUNGNN, FernandoPradelli, sbruda and 1 other person
L

lodewj

Senior Member
Aug 27, 2008
73
4
Aarschot
pir8man said:
There seems to be some confusion about which specific models this thread references. This thread references the mainboard 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 the second layer of hardware that interfaces with the external hardware modules. 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
Click to expand...
Click to collapse

To make things more clear:

This is the inside of my unit:

Inside there is the "motherboard", wich incorporates the amplifier, radio tuner, bluetooth module and mcu.
Soldered on top of the motherboard is another module (red). The Topway CR105-V5 in my case. This module holds the cpu (allwinner r16, ddr3 memory, emmc for storage and gps).

The mcu is soldered seperatly on the motherboard. In my case an STM8S207:

21j6oag.jpg
 
S

sinkee

Member
May 10, 2017
8
1
Screen flickering

Heya guys,

First of all thanks everyone for the assist.

I have bought similar multimedia device (ibb.co/mf8XGQ) however screen on my unit simply after some time starts to lose colour, screen flickers and so on. After some time it comes back to normal and then again some artifacts are occuring. This is happening sometimes when I start the car, then in middle of driving, really there isnt any real pattern.

Here is how it looks like:

Videos:
drive.google.com/file/d/0B9Bcgfj_3SdaQUN5R01DemhUdEU/view?usp=sharing
drive.google.com/file/d/0B9Bcgfj_3SdaXzJWS3dkakVna1k/view?usp=sharing

Screenshots:
s15.postimg.org/ruv0hbd0b/IMG_20170421_164741.jpg
s15.postimg.org/6mhbzvyjf/IMG_20170421_170831.jpg
s15.postimg.org/a7d7j432z/IMG_20170421_170921.jpg

Tried factory reset (via settings menu) but it didn't help.
And there is no way I can boot the device into recovery mode.
 
C

coyote320

Member
Apr 14, 2016
34
3
TH6 launcher

Hi guys, I will be very great full if any of you can provied the launcher of TH6 Firmware image. i donwloaded the whole firmware and I know how to extract APK from iso but here the rar file contain 4 files that I don't know what to do with :)

I navigated on 4pda but the link to donwload only the launcher is dead

10125187.jpg


Thanks
 
P

pir8man

Senior Member
Nov 25, 2007
328
89
Samsung Galaxy S21
Samsung Galaxy S22
sinkee said:
Heya guys,

First of all thanks everyone for the assist.

I have bought similar multimedia device (ibb.co/mf8XGQ) however screen on my unit simply after some time starts to lose colour, screen flickers and so on. After some time it comes back to normal and then again some artifacts are occuring. This is happening sometimes when I start the car, then in middle of driving, really there isnt any real pattern.

Here is how it looks like:

Videos:
drive.google.com/file/d/0B9Bcgfj_3SdaQUN5R01DemhUdEU/view?usp=sharing
drive.google.com/file/d/0B9Bcgfj_3SdaXzJWS3dkakVna1k/view?usp=sharing

Screenshots:
s15.postimg.org/ruv0hbd0b/IMG_20170421_164741.jpg
s15.postimg.org/6mhbzvyjf/IMG_20170421_170831.jpg
s15.postimg.org/a7d7j432z/IMG_20170421_170921.jpg

Tried factory reset (via settings menu) but it didn't help.
And there is no way I can boot the device into recovery mode.
Click to expand...
Click to collapse

That sounds like a faulty wiring internally. I would contact reseller for an exchange.
 
P

pirulazul

Senior Member
Jan 10, 2015
131
35
Samsung Galaxy Tab 4
Xiaomi Poco X3 NFC
sinkee said:
Heya guys,

First of all thanks everyone for the assist.

I have bought similar multimedia device (ibb.co/mf8XGQ) however screen on my unit simply after some time starts to lose colour, screen flickers and so on. After some time it comes back to normal and then again some artifacts are occuring. This is happening sometimes when I start the car, then in middle of driving, really there isnt any real pattern.

Here is how it looks like:

Videos:
drive.google.com/file/d/0B9Bcgfj_3SdaQUN5R01DemhUdEU/view?usp=sharing
drive.google.com/file/d/0B9Bcgfj_3SdaXzJWS3dkakVna1k/view?usp=sharing

Screenshots:
s15.postimg.org/ruv0hbd0b/IMG_20170421_164741.jpg
s15.postimg.org/6mhbzvyjf/IMG_20170421_170831.jpg
s15.postimg.org/a7d7j432z/IMG_20170421_170921.jpg

Tried factory reset (via settings menu) but it didn't help.
And there is no way I can boot the device into recovery mode.
Click to expand...
Click to collapse
It could be also bad car wiring, or battery is worn off or bad grounding. Try to get better grounding wiring the black cable to a bolt behind the dashboard
 
You must log in or register to reply here.

Similar threads

K
"AN-21 U" - Unbranded 6.2" 2 DIN Pure Android 4.1 Car Stereo Radio Head Unit [ROOTED]
Replies
9K
Views
2M
kandymanthadon
kandymanthadon
S
OUKU - Unbranded 6.2" 2 DIN Android Car Stereo Radio Head Unit
Replies
3K
Views
978K
K
katerini1
B
S150 - Android head unit
Replies
5K
Views
813K
K
Keramax
LwannaCM
Firmware for Carplay AI Boxes (Qualcomm/Rockchip/Allwinner) Android 7/9
Replies
1K
Views
381K
D
deepske
B
Bonroad C1067106A3 Allwinner QUAD CORE T3 P3 2GB RAM 16GB ROM 6.0.1
Replies
272
Views
220K
K
KURECT

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 10
    S
    sbruda
    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 "john@tw-desktop" (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.
    View
    6
    P
    pir8man
    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: "john@tw-desktop"
    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.
    View
    5
    dick-jones
    dick-jones
    rizu3544 said:
    would you please share your launcher apk and your launch screenshot... ?
    Click to expand...
    Click to collapse

    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.
    View
    5
    dick-jones
    dick-jones
    petro_ionut said:
    There is a modded rom on 4pda with autorun that works and is a good rom: V7.3.1_20170610.110122_KED1
    Click to expand...
    Click to collapse

    mrchrister said:
    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.
    Click to expand...
    Click to collapse

    Hi, guys!
    I made a new modded rom V7.3.2_20170801.182935_KED1.
    See changes here
    Thx.
    View
    4
    P
    pir8man
    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 "john@tw-desktop". 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
    View

New posts