Database Users

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

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.

So if the hardware is the same as the other 4.4.2 units then can we update our old units to 6.0?

Can you share me the content of /sbin directory?

sambacha said:
So if the hardware is the same as the other 4.4.2 units then can we update our old units to 6.0?
Click to expand...
Click to collapse
If the hardware matches then I do not see why not. In addition to dd-ing the system and boot partitions of my dump (which you are welcome to try) please see my last edits of the first post for possible flashable firmware being available.
Just make sure that you have a (tested) way to get back if things do not work...

mrtnb said:
Can you share me the content of /sbin directory?
Click to expand...
Click to collapse
See attached.

Found a thread in the russian site about updating the older units that came with 4.4.2 to 6.0. I will give that a try later today and report back. I'm mostly concerned about it's native support to USB DAC's so I can finally stop change audio sources in my DSP every time I want to use any app other than UAPP.
EDIT: spoke too soon before reading the updates to the original post!

Alternative to the stock radio -- help needed
I found this alternative radio app (reference, source code). It works well but I am unable to set preferences as the app force closes on selecting the setting menu item.
I would ask the developer, except that I do not speak Russian. I was wondering if any Russian speaker around here could inquire about the issue. I have also downloaded the sources and I am poking around but I am not holding my breath until I find a solution (I am a coder but not an Android developer). Many thanks in advance!

sambacha said:
Found a thread in the russian site about updating the older units that came with 4.4.2 to 6.0. I will give that a try later today and report back. I'm mostly concerned about it's native support to USB DAC's so I can finally stop change audio sources in my DSP every time I want to use any app other than UAPP.
EDIT: spoke too soon before reading the updates to the original post!
Click to expand...
Click to collapse
Can you share your experience and the russian thread's link?

sambacha said:
Found a thread in the russian site about updating the older units that came with 4.4.2 to 6.0. I will give that a try later today and report back. I'm mostly concerned about it's native support to USB DAC's so I can finally stop change audio sources in my DSP every time I want to use any app other than UAPP.
EDIT: spoke too soon before reading the updates to the original post!
Click to expand...
Click to collapse
Can you give us a link?
---------- Post added at 07:40 AM ---------- Previous post was at 07:21 AM ----------
can I flash this over Android 4.4?
This is my unit:
Android 4.4.2 Operation System
CPU Processor: Allwinner R16 Cortex A9 Quad-core 1.6GHz
RAM Memory: Samsung DDR3 1GB/16GB

I just installed an EONON GA2162. Link
Which appears to be a clone of the same..
MCU version: 5.3.19-108-10-943101-170114
System version: V7.3.1_20170114.111256_KBT2
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 20170112 test-keys
Build Fingerprint: Allwinner/astar_d7/astar-d7:6.0.1/MOB30R/20170112: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: 836 MB
Java Heap: 80 MB
STORAGE
Internal: 12 GB
EXTERNAL: Not Detected
I can dump the rom if anyone desires.

sbruda said:
[*]It would be great if long press events (SWC and/or front panel buttons) can be used. Some hints in various threads suggest that this is possible with these units but I found no way to do it. Advice is once more much appreciated.
Click to expand...
Click to collapse
Hi, I recently bought one of these for a Ford Mondeo and I somehow have figured about using keypress events.
The problem doesn't lie in the unit itself, but the damn apps it has.
I have been two entire days staring at Extreme Logcat screen and button event but no go, but, suddently, key event started registering next, prev and play/pause.
GREAT, I thought, and I started configuring Xposed Additions to start some audio visualizers in some buttons but when I started the music app, it stopped registering the events. It closed that app and those events where working again. Tried powerAmp and everything works like a charm. Menu and back keystrokes can also be mapped while the on-screen button still do the default action, so:
- It seems like the built-in apps capture those events and prevent anyone (tasker, Xposed Additions) to use them.
- MP3 and video player can be replaced pretty easyly but radio and specially bluetooth manager (Which has a whooping 12 keys that can be customized (0-9, # and *)) cannot be replaced.
- Decompiling the app, and disabling those captures could be the solution to use all those keystrokes OR finding some way to block those apps from capturing those events.
If I get something new I'll post asap.
Hope this helps.

pir8man said:
I just installed an EONON GA2162. Link
Which appears to be a clone of the same..
MCU version: 5.3.19-108-10-943101-170114
System version: V7.3.1_20170114.111256_KBT2
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 20170112 test-keys
Build Fingerprint: Allwinner/astar_d7/astar-d7:6.0.1/MOB30R/20170112: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: 836 MB
Java Heap: 80 MB
STORAGE
Internal: 12 GB
EXTERNAL: Not Detected
I can dump the rom if anyone desires.
Click to expand...
Click to collapse
could you please upload this rom for us
thanks man

me sumo al pedido
Saludos !
no se si alguien puede pero estaría bueno que puedan subir los packs de actualización. para R16 en la resolucion 1024*600
por ejemplo estos son los Nombres de los archivos que hacen falta...
tambien especificar el android si es 4.4 o 5.1 o 6.0
bd07a5ee-fbb0-11e4-ae78-000c29ba27c0
90436790-1e25-11e5-9b35-000c29ba27c0
91973a18-1e25-11e5-b937-000c29ba27c0
92e82e86-1e25-11e5-bffa-000c29ba27c0

khalwd said:
could you please upload this rom for us
thanks man
Click to expand...
Click to collapse
Hi,
(my first post):laugh:
I would also like to have a copy of this ROM.
I have the same Droid report.
Being someone that cant leave things alone i have somehow corrupted my unit.
I rooted with Kingoroot and all worked well. Uploaded a recovery to the cloud, all good.
Decided to down load back to the unit. Wife moves car and interrupts download.
Now when i boot up all i get is the car logo and the android screen, this is where it stops.
Tried installing various updates, They seem to install. Progress bar for abut 5 min shows update end
then boots to the car logo Android screen and stops.
Cheers

Hi,
pirulazul said:
Hi, I recently bought one of these for a Ford Mondeo and I somehow have figured about using keypress events.
The problem doesn't lie in the unit itself, but the damn apps it has.
I have been two entire days staring at Extreme Logcat screen and button event but no go, but, suddently, key event started registering next, prev and play/pause.
GREAT, I thought, and I started configuring Xposed Additions to start some audio visualizers in some buttons but when I started the music app, it stopped registering the events. It closed that app and those events where working again. Tried powerAmp and everything works like a charm. Menu and back keystrokes can also be mapped while the on-screen button still do the default action, so:
Click to expand...
Click to collapse
Thank you for the report. I tried the same (stop all system apps) but even so KeyTest does not register any event. This was done for the panel buttons since I do not have yet any SWC (the unit is on the bench), which may or may not be the cause of my failure.
pirulazul said:
- It seems like the built-in apps capture those events and prevent anyone (tasker, Xposed Additions) to use them.
- MP3 and video player can be replaced pretty easyly but radio and specially bluetooth manager (Which has a whooping 12 keys that can be customized (0-9, # and *)) cannot be replaced.
Click to expand...
Click to collapse
Have you found any way to replace the default association for these apps? By default the "Mode" action cycles through the default apps, did you find any way to convince this action to cycle through some other (custom) rotation?
pirulazul said:
- Decompiling the app, and disabling those captures could be the solution to use all those keystrokes OR finding some way to block those apps from capturing those events.
Click to expand...
Click to collapse
I'll try to look into this, but at this time I cannot promise any timeline.
Cheers!

would one of my units be similar to yours?
i received a newer firmware from the chinese (build 29.12) as a ZIP which contains the 4 files as above, but i can't update it since i get a signature error (seen below). In the meantime i managed to **** up the screen by accidentally switching to 800x480 and now i can't see anything useful on the display...

zerozoneice said:
would one of my units be similar to yours?
Click to expand...
Click to collapse
Looks pretty much the same as mine (with a slightly newer firmware though).
zerozoneice said:
i received a newer firmware from the chinese (build 29.12) as a ZIP which contains the 4 files as above, but i can't update it since i get a signature error (seen below). In the meantime i managed to **** up the screen by accidentally switching to 800x480 and now i can't see anything useful on the display...
Click to expand...
Click to collapse
Most (all?) Chinese vendors know absolutely nothing about the units they sell so it is quite possible to have the wrong firmware. This, or the file got corrupted during transfer somehow. Have you tried my firmware blob or the others that float around? The probability that it will work look decent and what have you gotta loose?
You can also try to restore the resolution by trial and error (touching the screen where things should be). A couple of success stories have been posted in this thread though the process looks painful...

there are couple of FWs around, i saw them on 4PDA as well. The latest is february, something. The problem is that the ZIP file has the 4 files you listed above, instead of an IMG file. Shouldn't IMG be the default ROM update? I mean even PowerSuit recognizes only IMGs, that is if i manage to connect to the damn box somehow.
I tried TV out, hoping the signal is ****ed only from the mainboard to the screen and it would manage to display it on another external screen, but....there is no TV out. Didn't work with the cables provided.
Trial & error...i would need to see another menu next to me in order to see where the hell i'm pressing on my screen
Resolution change is the first menu, but is hidden in the extra settings, behind a password which i'd also need to enter....blindly.
Did you manage to install any of the 4PDA firmwares properly on yours? Try the December 29th one, this is the one that Infidini sent me....
LE: LOL, i just read the following passage from the thread you posted above:
"What is the Extra Settings password?
Resolved: 123456
Note: Do NOT change the resolution of the head unit. You will destroy your unit. However it is reversible."
Post 807: another quickfinger like me, changed the res. the other way around, from 800 to 1200, but he still sees something....
https://forum.xda-developers.com/showpost.php?p=70762889&postcount=807
Post 747: same problem as me.
https://forum.xda-developers.com/showpost.php?p=70047172&postcount=747
How can i flash this damn unit? How can we connect to it?
@sbruda: i have an idea. Can you please post screenshots of the menu, from the main menu screen all the way to the extra settings, where u enter the password and then the "change resolution" menu option? It can help me to figure my fingers around the screen blindly... THX!
---------- Post added at 04:43 PM ---------- Previous post was at 04:15 PM ----------
HERE is the link to the FW that infidini support provided me.

zerozoneice said:
there are couple of FWs around, i saw them on 4PDA as well. The latest is february, something. The problem is that the ZIP file has the 4 files you listed above, instead of an IMG file. Shouldn't IMG be the default ROM update? I mean even PowerSuit recognizes only IMGs, that is if i manage to connect to the damn box somehow.
Click to expand...
Click to collapse
I believe that the four files can be used directly to upgrade, at least this is what people have reported (I have never tried to upgrade myself). This also makes sense given that a restore to factory from the (Android) menu will presumably use the partition with those files.
zerozoneice said:
I tried TV out, hoping the signal is ****ed only from the mainboard to the screen and it would manage to display it on another external screen, but....there is no TV out. Didn't work with the cables provided.
Click to expand...
Click to collapse
It would appear that TV out only works for the DVD.
zerozoneice said:
Did you manage to install any of the 4PDA firmwares properly on yours? Try the December 29th one, this is the one that Infidini sent me....
Click to expand...
Click to collapse
No, I meant to but I am really pressed for time nowadays so I have no idea when will I get to it.
zerozoneice said:
@sbruda: i have an idea. Can you please post screenshots of the menu, from the main menu screen all the way to the extra settings, where u enter the password and then the "change resolution" menu option? It can help me to figure my fingers around the screen blindly...
Click to expand...
Click to collapse
Here they are. Sorry for the crappy photos but I have no idea how to take screenshots on this unit (please advise):
1-main.jpg - main screen
2-notif.jpg - notifications pulled down (two times)
3-settings-scrolled.jpg - the settings app scrolled all the way down
4-car-settings-scrolled.jpg - the Car settings screen scrolled all the way down
5-settings-pass.jpg - the password entry box and keyboard (I would advise the use of a USB keyboard instead though)
6-extra-settings.jpg - the Extra setting screen
7-resolution.jpg - the resolution dialogue
I hope this helps. If somebody can advise on how to take screenshots I will come back with better quality photos.

sbruda said:
1-main.jpg - main screen
2-notif.jpg - notifications pulled down (two times)
3-settings-scrolled.jpg - the settings app scrolled all the way down
4-car-settings-scrolled.jpg - the Car settings screen scrolled all the way down
5-settings-pass.jpg - the password entry box and keyboard (I would advise the use of a USB keyboard instead though)
6-extra-settings.jpg - the Extra setting screen
7-resolution.jpg - the resolution dialogue
I hope this helps. If somebody can advise on how to take screenshots I will come back with better quality photos.
Click to expand...
Click to collapse
thx, they're good enough. using phone is fine. afaik password for that extras in my case is 123456 and restore to factory settings 7890
i will try tomorrow.
---------- Post added at 07:32 PM ---------- Previous post was at 07:01 PM ----------
How do you power on the thing when not connected in the car???

Samsung galaxy core 2 duos SM-G355H storage problem

Hello,
I have a problem with Samsung SM-G355h.
When I enter in settings/storage or in any application details, system can't calculate how much storage that application occupies or any oder memory space beside available space (there's just calculate... where space amount should be). Besides that I can install apps but can't uninstall them (uninstalling is working but never finishes), there is no error massages. After a while phone just restarts.
I tried following things:
- wipe data and cash, reset to factory settings;
- I used Odin to install newer and older firmware (official);
but it is always the same.
Phone isn't rooted and has no custom rom in it.
If someone has idea what I can do more, his suggestion will be most welcome.
Phone software specifications:
Android version: 4.4.2
Baseband version: G355HXXU0AOB3
Kernel version: 3.10.17-5115844 [email protected] #2 Thu Jan 5 21:10:36 KST 2017
Build number: KOT49H.G355HXXS0AQA4
Security software version: ASKS v1.2_161011
Thank you for your attention

mladja27 said:
Hello,
I have a problem with Samsung SM-G355h.
When I enter in settings/storage or in any application details, system can't calculate how much storage that application occupies or any oder memory space beside available space (there's just calculate... where space amount should be). Besides that I can install apps but can't uninstall them (uninstalling is working but never finishes), there is no error massages. After a while phone just restarts.
I tried following things:
- wipe data and cash, reset to factory settings;
- I used Odin to install newer and older firmware (official);
but it is always the same.
Phone isn't rooted and has no custom rom in it.
If someone has idea what I can do more, his suggestion will be most welcome.
Phone software specifications:
Android version: 4.4.2
Baseband version: G355HXXU0AOB3
Kernel version: 3.10.17-5115844 [email protected] #2 Thu Jan 5 21:10:36 KST 2017
Build number: KOT49H.G355HXXS0AQA4
Security software version: ASKS v1.2_161011
Thank you for your attention
Click to expand...
Click to collapse
Go to recovery and try to clear cache

Expert needed to root Android Headunit with Allwinner A50 SoC

Hi Experts,
In possession of a Pioneer Headnit which consists of a amplifier and seperate tablet SDA-8TAB.
Seems to run on a Allwinner A50 Soc and on Android 9. Would like to get root access but well known Rooting Apps do not work. Somebody can help? I captured some info from the tablet and by looking in the logs which were created when you re-install the tablet:
Manufacturer: worldchip
Model: SDA-8TAB
Brand: Pioneer
Board: exdroid
Device: SDA_8TAB
Hardware: sun8iw15p1
Platform: venus
Product: SDA_8TAB_XEEU5_EEA
Installed RAM: 2 GB
<<< CPU >>>
Core Architecture: 4x ARM Cortex-A7 @ 1800 MHz
Instruction Set: 32-bit ARMv7
CPU Revision: r0p5
CPU Cores: 4
Supported ABIs: armeabi-v7a, armeabi
Supported 32-bit ABIs: armeabi-v7a, armeabi
AES: Not Supported
NEON: Supported
PMULL: Not Supported
SHA1: Not Supported
SHA2: Not Supported
<<< Android >>>
Android Version: 9 (Pie)
API Level: 28
Android Security Patch Level: 2019-11-05
Codename: REL
Java Runtime Version: Android Runtime 0.9
Java VM Version: ART 2.1.0
Java VM Heap Size: 256 MB
Kernel Architecture: armv7l
Kernel Version: 4.9.118
Tags: release-keys
Type: user
Google Play Services Version: 20.21.15 (100300-313409149)

hjdevries said:
Would like to get root access but well known Rooting Apps do not work.
Click to expand...
Click to collapse
It would be very helpful if you mentioned wich rooting apps you already tried. How would you otherwise get advice about other apps/options.

surfer63 said:
It would be very helpful if you mentioned wich rooting apps you already tried. How would you otherwise get advice about other apps/options.
Click to expand...
Click to collapse
Sure, thanks for the question, apps I tried:
Kingroot
Kingoroot
dr. Foneroot
RootGenius
P.S I don't want to install custom rom, only would like root access

hjdevries said:
Sure, thanks for the question, apps I tried:
Kingroot
Kingoroot
dr. Foneroot
RootGenius
P.S I don't want to install custom rom, only would like root access
Click to expand...
Click to collapse
Try Magisk. It is the universal rooting method.
You do need to know though how to flash a boot image, or how to dd write a boot image.

surfer63 said:
Try Magisk. It is the universal rooting method.
You do need to know though how to flash a boot image, or how to dd write a boot image.
Click to expand...
Click to collapse
Goedemiddag,
Yes I have read tutorials and I need TWRP with a custom file designed for my device, which I cannot find.
So Magisk is one step too far for the moment.
Any suggestion? Dank, HJ

hjdevries said:
Goedemiddag,
Yes I have read tutorials and I need TWRP with a custom file designed for my device, which I cannot find.
So Magisk is one step too far for the moment.
Any suggestion? Dank, HJ
Click to expand...
Click to collapse
Depending on the head unit you do not need TWRP, but I have no idea how your boot/recovery works.
Other tools are Superuser and SuperSU.

surfer63 said:
Depending on the head unit you do not need TWRP, but I have no idea how your boot/recovery works.
Other tools are Superuser and SuperSU.
Click to expand...
Click to collapse
What I did just now:
1. In developer settings Android allow to boot custom image
2. Downloaded MagiskManagere to tablet and chose the option to install ZIP automatically
3. Booted in Android recovery mode by holding down the power button and volume up button
4. I expected to get booted in a different screen than the stock Android one, see attachment.
Bootloader option just shows the Android puppet....with belly open
Am I doing something wrong?

I also surfed the web and found out that it's helpfull to have the stock factory rom from the device so that later on it can be flashed with root access.
But to get the stock rom you need root, which I am actually after. Or use TWRP but hey, they don't have rom for my device.
So basically stuck. Should I give up or is there a way, or perhaps I am doing something wrong?

hjdevries said:
I also surfed the web and found out that it's helpfull to have the stock factory rom from the device so that later on it can be flashed with root access.
But to get the stock rom you need root, which I am actually after. Or use TWRP but hey, they don't have rom for my device.
So basically stuck. Should I give up or is there a way, or perhaps I am doing something wrong?
Click to expand...
Click to collapse
Most units here are Chinese units. Actually there are only 4~5 Android/MCU manufaturers. All the brands you see are resellers of the hardware of these 4~5 resellers. You have a Pioneer. It might be identical to one of those manufacturers, but maybe also a pure Pioneer in-house development. That makes that it difficult for those Chinese head unut owners to help you.
But did you try this link? : http://howtoandroitroot.com/download/pioneer-sda-8tab
(I didn't follow it through)

surfer63 said:
Most units here are Chinese units. Actually there are only 4~5 Android/MCU manufaturers. All the brands you see are resellers of the hardware of these 4~5 resellers. You have a Pioneer. It might be identical to one of those manufacturers, but maybe also a pure Pioneer in-house development. That makes that it difficult for those Chinese head unut owners to help you.
But did you try this link? : http://howtoandroitroot.com/download/pioneer-sda-8tab
(I didn't follow it through)
Click to expand...
Click to collapse
Note to self for good tutorial, method 2. https://www.the***********.com/install-magisk-root-android-devices/
Need Stock root image.
The website you gave doesn't asllow me anything, however it shows options for all ANdroid which is strange, This tablet just came out.
Do you have somebody in your network who could help find that stock boot image looking at my first post with ingo, or contact me how to get it myself from the device perhaps?
Willing to donate of course.

I think I have almost the same unit as you .. I've been looking everywhere for the info about rooting and any available alternative roms ... Mine is a Xomax XM 2VA 757 ... pure allwinner but now you've answered a lot of my puzzles. Thanks
We have almost identical architectures .... and I have asked my vendor if they can find me an OTA type upgrade ROM for it .. I don't hold out much hope but I am trying.
Manufacturer: Allwinner
Model: QUAD-CORE
Brand: Allwinner
Board: exdroid
Device: venus-a3
Hardware: sun8iw15p1
Platform: venus
Product: venus_a3
Core Architecture: 4x ARM Cortex-A7 @ 1512 MHz
Instruction Set: 32-bit ARMv7
CPU Revision: r0p5
CPU Cores: 4 Cores
CPU Clock Range: 480 - 1512 MHz
Core 1 Clock: 1512 MHz
Core 2 Clock: 1512 MHz
Core 3 Clock: 1512 MHz
Core 4 Clock: 1512 MHz
Supported ABIs: armeabi-v7a, armeabi
Supported 32-bit ABIs: armeabi-v7a, armeabi
AES: Not Supported
NEON: Supported
PMULL: Not Supported
SHA1: Not Supported
SHA2: Not Supported
Screen Resolution: 1024 * 600
Screen Size: 155 mm × 86 mm
Screen Diagonal: 6.98 inches
Pixel Density: 170 dpi (mdpi)
xdpi / ydpi: 168 / 177 dpi
GPU Vendor: ARM
GPU Renderer: Mali-400 MP
Refresh Rate: 59 Hz
Default Orientation: Landscape
OpenGL ES Version: 2.0
GPU Version: OpenGL ES 2.0 8c81e1f
Android Version: 9 (Pie)
API Level: 28
Android Security Patch Level: 2019-01-05
Rooted Device: No
Build ID: MCX.UI6_3.USER.BUILD.20201117-095320
Codename: REL
Fingerprint: Allwinner/venus_a3/venus-a3:9/PPR1.181005.003/20201117-095320:user/test-keys
Java Runtime Version: Android Runtime 0.9
Java VM Version: ART 2.1.0
Java VM Heap Size: 192 MB
Kernel Architecture: armv7l
Kernel Version: 4.9.118
Tags: test-keys
Type: user
Google Play Services Version: 21.09.15 (110302-361652764)

And we both live in the Netherlands !! I'm in Den Haag .. where are you ?

I just found anA50 firmware .. don't recognise the device though ...
Here ...

Heya. I have the same device. After a few weeks of research I managed to boot it into a firmware from another device (MultiLaser M7S Lite Oreo) using PhoenixCard. This means that I should be able to use IMGRePacker to extract it, then patch boot.fex with Magisk, flash that back onto the SD Card and from there on out, I should be able to backup the stock img from the internal nand, patch that and then flash it to the nand. I will keep y'all up to date with success/failures.
UPDATE 1: Boot.fex from MultiLaser Stock Firmware is patched and repacked into Firmware IMG. Flashing to SD Card right now.
UPDATE 2: Flashed SD Card with new boot.fex. Wouldn't boot. Will try flashing it with the option "Preserve force encryption" checked.
UPDATE 3: Just found out there are two bootloaders. One on the nand, and one on the SD. Obviously to boot the sd card with a patched img, I will need to unlock the bootloader. Edit: It won't boot to bl with button combo, I am assuming I will need to execute "adb reboot bootloader", so will be trying that.
UPDATE 4: The M7S ROM is booted and rooted baby!

snowlily said:
Heya. I have the same device. After a few weeks of research I managed to boot it into a firmware from another device (MultiLaser M7S Lite Oreo) using PhoenixCard. This means that I should be able to use IMGRePacker to extract it, then patch boot.fex with Magisk, flash that back onto the SD Card and from there on out, I should be able to backup the stock img from the internal nand, patch that and then flash it to the nand. I will keep y'all up to date with success/failures.
UPDATE 1: Boot.fex from MultiLaser Stock Firmware is patched and repacked into Firmware IMG. Flashing to SD Card right now.
UPDATE 2: Flashed SD Card with new boot.fex. Wouldn't boot. Will try flashing it with the option "Preserve force encryption" checked.
UPDATE 3: Just found out there are two bootloaders. One on the nand, and one on the SD. Obviously to boot the sd card with a patched img, I will need to unlock the bootloader. Edit: It won't boot to bl with button combo, I am assuming I will need to execute "adb reboot bootloader", so will be trying that.
UPDATE 4: The M7S ROM is booted and rooted baby!
Click to expand...
Click to collapse
hi,can you send the boot file?i have thepioneer and trying to root it

Lefteris Fragiadakis (Frago) said:
hi,can you send the boot file?i have thepioneer and trying to root it
Click to expand...
Click to collapse
Unfortunately I messed it up and accidentally flashed the internal boot partition with a magisk patched boot from the multilaser and now I have no way to obtain the original boot image. Though you can always check if the multilaser firmware is anywhere near stable on your device using phoenixcard. I'll see if I can find back where I got the flashfile in a bit and post here. Just make sure to use phoenixcard before actually flashing the tablet. This way you can know if it even boots and works in the first place, without risking a brick.

The download quota is exceeded. Imma find a way to download it and reupload it to Mega

i can read system if i take of emmc using ufi box but i dont want to lose guarentee,i also tried to find a boot to patch it with magisk but i didnt,i only want to root this pioneer

snowlily said:
Unfortunately I messed it up and accidentally flashed the internal boot partition with a magisk patched boot from the multilaser and now I have no way to obtain the original boot image. Though you can always check if the multilaser firmware is anywhere near stable on your device using phoenixcard. I'll see if I can find back where I got the flashfile in a bit and post here. Just make sure to use phoenixcard before actually flashing the tablet. This way you can know if it even boots and works in the first place, without risking a brick.
Click to expand...
Click to collapse
also maybe the pathced boot you have i can try to boot it on pioneer to see if this work

Please Help, T3L Allwinner A23 1.60 Mhz 1gb Ram 16gb Rom Update Fail

Hello, thank you very much to anyone who can help me, I tell you about my situation, I do the whole procedure the 5 files in the root in a Fat32 USB memory, I mark the box to format the internal flash, the stereo takes a long time and indicates that it does not It turns off, then it restarts, everything gives the impression that it is going to perform the procedure but the only thing that happens is that the vehicle logo and the android letters are reset, when it starts after a long time in the Android letters it turns out that a factory settings reset, nothing else .... !! it never reaches the screen where you see how the installation and update bar progresses as in the video, and the information continues to show the same number and date of compilation, mcu, system and the same failures of course .. I'm doing wrong .? I have manually reset to factory, I have changed memory, I have tried 2 different compilations: (20210803 and 20210825) with the name THEME1, I have downloaded from different places ..! Nothing, always the same behavior and result.
Supposedly this is the correct firmware for my Stereo.
My device is a T3L with 1GB Ram and 16GB of Internal memory,
MCU version:
T3L.3.19.-296-10-A49311-210105 (MM030)
System:
V8.1.1_20210430.162039_THEME1
Android Version: 10 (Fake) - 8.1 API Level 29
VW:
(T3L.3.19, PT2313, QN8035, MM030,296)
CPU-Z:
AllWinner A23 1.60 GHZ
Model: QUAD-CORE T3 p1 (t3_p1)
Board: exdroid
Hardware: sun8iw11p1
Build ID: t3_p1-eng 8.1.0 OPM1.171019.026.20210430 test-keys
Resolution: 1027x600 Pixels
Screen Size: 7.42 inches (but I bought it as a 9-inch)
Thank you in advance for the light and the help ..!
Greetings from the Middle of the World

Samsung galaxy S4 GT-i9506 network , service mode problems, etc

hi all,
I decided to do my first post as i am stuck with something i am not sure how to rectify as a newbie in the android world but not newbie in the computer world.
I bought a samsung s4 GT-i9506 secondhand phone with damaged usb port thinking to repair it and try my skills for interest above all.
So got the port replaced and mobile charges ok now, i see the device working. battery is OK.
I think the device is Samsung Galaxy S4, and UNLOCKED possibly 2013 model GT-i9506 Black.
I found on the web some other codes like VDS or Shv-e330s-510 but not sure if these mean GTi9506 or are similar.
I found how to wipe - reset to factory, did that and did all updates to the phone. I dont know what OS was previously on the phone.
I then found the IMEI and paid via ebay to do a device or carrier check and got the following results including some other i add by myself.
I give all the info further down.
So, i tried to put a sim card and got error with SIM network unlock PIN window.
I added sim card, local card without subscription Lyca or comviq for above issue.
I dont know the pin and i click dismiss instead of unlock.
So, i need to unlock the networ i understand.
The paid check said unlocked so not sure what is going on with the phone at this stage.
After searching online I went in networks and did a search. I got results as below:
Telenor SE
Telenor SE
Tele2
3 SE
Telia S
So no Lyca or Comviq listed or not sure if ie Telia handles Lyca (I think Estonian company)
as i see Telia signal on the mobile from time to time, using the Lyca sim card.
I then found a video how to enter the service menu to do unlock of the network for free.
It works when i do the 0011 dial with star and hash keys combination, but does not accept
entering key values ie 1 etc to bring the next menu up etc. So it stays in the first service mode screen
which says (some items change values while this mode is on)
RRC:idle band8
mcc-mnc 240-02
rx 2398 RI -76, CID 780353
tx 2713 PSC 476
eclo -5 RSCP -81
speechver FR FR FR
L1 PCH_sleep
drx cycle 64
sib19 is received
therm 0 LNA 0
service Limited
PA state 0 APT, HDET 0
imei certi NA
-----
So i abandoned this operation and tried to follow other videos ie to root device
and run an app, i forgot its name, found in XDA as apk file that does this unlocking as well (may work)
as could not find it in google play store.
I downloaded a root checker app and checked device. It said may not be rooted or need to grant SU permissions.
I got another root checker and said that device may not be rooted ok, but i guess could be same issue as above.
I also read that samsung disable the service mode and maybe my update is not allowing this mode to work and needs root
or flashing earlier OS versions which i have no clue how to find and apply - i have no instructions at all.
Then i tried to find free root apps but no luck as not sure what you do after that and where. So i stopped here and thought to
ask in the forums.
So, which is the best way to free fix my network problem on this oldie phone...
How can i downgrade and or flash to an older android version that will allow me to run the service mode OK etc. what do i need for that.
Platforms and software pc or mac.
I have a soldering iron and screwdrivers and may do some soldering if is possible to my skills.
Mobile info from about device menu included below.
-----
basedand i9506xxudpL1
kernel version 3.4.0-6069869
[email protected]#1
thu dec 1 13:43:16 KST 2016
build no. LRXX22c.I9506xxSDPL2
SE for android status
enforcing
SEPF_GT-i9506_5.0.1-1_0039
thu dec 1 13:45:59 KST 2016
KNOX version 2.3
standard sdk 5.3.0
premium sdk 2.3.0
customisation sdk 2.0.0
container 2.3.0
cep 2.0.1
enterprise billing 1.0.0
SE for android 2.3.0
sso 2.1.1
TIMA 2.0
VPN 2.2.0
-------------some other info i added not from about device menu----
Android v5.0.1, SD card.
STORAGE hdd: 16GB total. about 10GB free with latest OS installed updated
STORAGE microSD card max: 64GB
SIM CARD type: Micro (not nano) Medium size type
SN= RF8DC05A6AE
SSN= -i9506GSMH
FCC ID= A3LGTi9506
from the paid check i got
Model Info: MOBILE GT-i9506 BLACK VDS

Serial Number: RF8DC05A6AE
DO (different from SN above has extra two letters at the end)
Number: 8202869406(C4F0-05)

Model Number: GT-I9506ZKAVDS
Model Name: GT-I9506
Model Desc: Galaxy S4
Warranty Status: Warranty Expired

Production Date: 01-12-2013
Warranty Until: 10-12-2014
Manufacturer: Samsung Electronics Vietnam (SEV), Bac Ninh City

Carrier: Sweden Unlocked

Sold By: Sweden / 11 December 2013
Blacklist status: Clean
----finaly the end....
I use english language menus for operating the phone
thanks for reading