yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Doubletop12:
Yes I've tried that many times. There could well be a problem with the approach I'm taking but the details of what I should do would be appreciated along with the settings that a working device has e.g. resolution xy axis etc.

I'm convinced a file has been blown away with the reset. The information that lordboo has provided build.prop looks interesting and may provide a clue. Where can I find that?

Pete
[Android Head-Units] lordboo03:
Under internal storage/system folder
[Android Head-Units] Doubletop12:
Screen Shots

I notice a lot of posts of screen shots have been done with a phone.

If you drag down from the top edge of the screen you'll get a menu that includes screen shots (top right). If its not there you may be in the 'Notify' tab. Select 'Switch'.

The screenshots can be found in File Explorer are held in the folder pictures/screenshots. Copy and paste to a USB and then you can post them here

Pete

---------- Post added at 09:17 PM ---------- Previous post was at 09:11 PM ----------

To get more detail on your hardware download CPU-Z from the Play Store

Pete
[Android Head-Units] Doubletop12:
Thanks I'll take a look and compare your content with mine

Pete
[Android Head-Units] Doubletop12:
Config Files

I've found the build.prop file and others. I then started a search for other configuration files to find that .idc files are device specific

https://source.android.com/devices/input/input-device-configuration-files

Particulary for the touch screen. However all my system has are

build.prop

default.prop

mtklog-config.prop

AVRCP.idc

querty.idc

query2.idc

Could somebody please serch their working unit for .prop and .idc files and let me know what they have. Particullarly anything to do with the touch screen?

Thanks

Pete
[Android Head-Units] Doubletop12:
I've just found this

https://xdaforums.com/android/software-hacking/touchscreen-driver-issue-t2966312#post79873816

and this

https://source.android.com/devices/input/touch-devices

The answer to the dead area on my touch screen and non working soft keys is in here somwhere.

Maybe I'm looking for something like an mtk-tpd.idc file that could be missing from my build. Does anybody's working system have one or anything like it?

(if you've got ES File Explorer, or similar, goto "/" and search for ".idc" and ".prop")

Pete
[Android Head-Units] o0timbo0o:
i arrived at this page as i have installed the stero and done something a bit silly . Somehow managed to format the SD card which has deleted all the map files. Tried to root the device as it wont allow me to uninstall the sygic nav app due to it being locked. Does anyone have a sygic sd card i can have an image of. I've tried downloading the sygic app onto the phone then copying the files to the SD card but the app just hangs.
[Android Head-Units] Doubletop12:
Just go to the play store and install HereWeGo then download all the maps you need

Pete
[Android Head-Units] Phant0m3rr0r:
Do u solved the issue?

My solution is clear the launcher data at settings
[Android Head-Units] kavirz:
---------- Post added at 10:42 AM ---------- Previous post was at 10:37 AM ----------

The video shows that something is calling all running apps (Second button on the top right) which is used to stop/clear all active apps. Don't think it is related to the launcher. You could change it with side loading one and see if it does help but I double it. Something is causing issues. I would maybe ask the person you bought it up. Maybe touch screen is faulty. Have a look at developer options to see active touches on the screen. Might show some bug that is hitting that button. The only other thing could be maybe a faulty button setup causing a touch on the screen to call that option.

Update:

Just rewatched the video. I believe it has something to do with canbus/steering controls. Try disconnecting the canbus behind the unit if it has one and test again. Otherwise the issue might be in the steering controls programming but have seen head units do funny things if the canbus is not 100% correct where the car ecu sends something to the head unit and it does something completely incorrect.
[Android Head-Units] bangcak:
how to backup stock firmware before trying those updates?
[Android Head-Units] 00ice00:
Hello guys,

I had root this unit (file XYAUTOUPG) and work correctly but I have two question:

1) The passwords 8888 and 5678 are incorrect, any solution?

2) I try to change boot logo via "Logo Settings" in "Car Setting" app but the .jpg or .png in USB pendrive aren't displayed. Do you know why? Is possible change boot logo somehow?

Thank you
[Android Head-Units] leo06:
Does anyone have the music apk from this units?
[Android Head-Units] kavirz:
Default password is 8888 on the mtk units unless they changed it. Try 126. Remember reading somewhere that this can also sometimes be the password.

I have never tried loading a logo via a pen drive. Just chose from the list available locally on the unit. Also, the format might not be .jpg or .png.

---------- Post added at 07:27 AM ---------- Previous post was at 07:25 AM ----------

I should have it at home. Drop me a PM with your email address and I will upload it for you in the next 8 hours. There is a folder somewhere on the unit where all the original apk's that are installed are saved including music app. You can also just download musicolet as that seems much better then the stock app.
[Android Head-Units] leo06:
Thanks, I have found it. I want the stock music app because I can see the time of the track in car's display, I tried some others music apps and didn't show that info in the display
[Android Head-Units] jefbuan:
I also have this headunit but the problem my steering wheel buttons not working..how can I set this up?
[Android Head-Units] dudyvg99:
Cant You Help me please.

My Head unit display not compitable after upgarde os.

My Head unit Tesla style for toyota camry.

Please help me. Thanks

[IMG="ScreenShot"]https://www.photobox.co.uk/my/photo/full?photo_id=502206043064[/IMG]
[Android Head-Units] ultradj83:
As far as I know there's no valid interface to apply root.

So, the only way is to disassemble and connect to serial port, if available.

Moreover, Su binary is already present, but permissions are set to not to allow read and write to users.
[Android Head-Units] kavirz:
Do you have a picture of what the music app looks like? I will have a look as I have the app at home. PM me with your email address and will send the copy I have.

---------- Post added at 07:54 AM ---------- Previous post was at 07:53 AM ----------

What model? Do you have car settings on your menu? There is normally an option for it in there. Does your vehicle have a canbus box (Small box in line when installing)? If it has a canbus box, then there is an option to change it in factory settings so that the steering controls work. If not, then there must be an program it on the device.
[Android Head-Units] leo06:
I have found the music all and it's working fine, thanks anyway
[Android Head-Units] dougdude10:
ROOT!

Root has to be done through ADB.

Attention! Incorrect actions can lead to a bootloop (endless loading) of the radio. To fix it, you will need a flashing and, as a result, a complete erase of all data; so, proceed at your own risk!

Requirements: P.C. (I prefer my laptop) and your head unit must be able to connect to the same wifi as the PC (I used my mobile phone's hotspot for wifi and connected my laptop and headunit to it)

Download adb (platform-tools-latest-windows.zip) from here

Download SuperSU apk and SuperSU zip files from here

Extract platform-tools-latest-windows.zip to C:\adb

Extract SR5-SuperSU-v2.82-SR5-20171001224502.zip.

Open the armv7 folder

Select all files in the armv7 folder and right click, Copy

Paste the files into the c:\adb directory

In the same folder, create a notepad file and paste in the following text:

service rooting /system/bin/su --daemon
class main
priority 10
user root
oneshot
seclabel u:object_r:system_file:s0

now save this file as "rooting.rc"

Open command prompt on your PC as administrator (in windows 10, in the "type here search" type "cmd")

type in "cd c:\adb"

Move over to the headunit and download "What is my IP address" from the google play store.

open up what is my ip address and write down your headunit's ip address (should be something like 192.168.3.4)

Go back to the play store and download "Terminal Emulator for Android"

open Terminal Emulator for Android

Go back to your pc and in the command prompt window, execute the following code:

(my adb worked without additional commands, immediately after opening the emulator)

(any sentences to the right of // means NOTE; so, don’t copy that part)

adb connect <IP devices>: 5555 // For example adb connect 192.168.3.4/10555
adb shell // Go to Shell
su @#zxcvbnmasdfghjklqwertyuiop1234567890,. // In the shell, we switch to superuser mode using the password
remount // Remount so that all further commands are immediately executed from the superuser
adb shell setenforce 0 // Further on the instruction manual from the articles
adb push su /system/xbin/su
adb push su /system/bin/su
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/xbin/su
adb shell /system/bin/su --install
adb push rooting.rc /system/etc/init/rooting.rc

get back on you headunit,

get the SuperSU apk we downloaded from before and get it installed onto your headunit. (I put mine onto my google drive and downloaded and installed from there)

open it and look for a GRANT command.

Press GRANT to allow superuser access.

NOTE: If you get a request to update the binary file, click reject

go back to your pc. we are going to Reboot your headunit with the reset command

adb shell reboot

The radio will reboot twice, don't panic.

check with root checker

You should be ROOTED!

EDIT: here is a video: https://www.youtube.com/watch?v=4v9s89fYIZ4&feature=youtu.be
[Android Head-Units] kavirz:
Awesome info and guide. Is this only for the PX based devices or will it work on the MTK based devices? Most of us here have the MTK8227L processor so not sure if the guide will work. I will try it out when I get a chance as the logic behind the guide should be the same.
[Android Head-Units] ultradj83:
Sir, what device did you try on?

I remember when I tried ADB by network on my Eonon GA2168K I had no answers.

Moreover, are you able to manage from SuperSU to Magisk?

Tks.
[Android Head-Units] jefbuan:
will this work on my Hu?

View attachment 4846225
[Android Head-Units] dougdude10:
This is for MTK8227L. That is the device I have. I am not sure for PX based

---------- Post added at 05:05 PM ---------- Previous post was at 05:03 PM ----------

Haven't tried moving over to magisk yet, nor have I solved custom recovery. Try following my guide see if it helps. I have a ga2168k as well. I can post my exact specs later.

EONON 10.1 – GA2168K

2Din 10.1"

Android 8.1

4Core

• Model (processor) = Ac-8227L

• Android = 8.1.0

• Kernel version = 3.18.79 (gcc version 6.3.1 20170404 (Linaro GCC 6.3-2017.05)) root@ubuntu #16 Sat Sep 2909:13:10 CST 2018

• Build number = alps-mp-o1.mp5

• Custom Build number = alps-mp-o1.mp5

• Bluetooth address = C0:81:35:13:3E:FA

• Serial number = GU4PUSCQEMUGTCS4

• HMI = KABT.C.O.F.3.01.2019.04.30.15.30

• MCU = TS907.181110(H)

• MEDIA = HC_v1.0.0_190329_1400

• BTV = BT.19.04.29.1530(C0:81:35:13:3E:FA)

---------- Post added at 05:07 PM ---------- Previous post was at 05:05 PM ----------

Your setup looks different. Try using something like spec device and send me your specs.

Jeff, try this thread: it seems similar - https://xdaforums.com/android-auto/...-firmware-chinese-7-head-unit-ac8227-t3931863
[Android Head-Units] marioos88:
After multiple attepts, i give up. I keep receiving this error:

c:\adb>adb connect 192.168.43.75:5555

cannot connect to 192.168.43.75:5555: No connection could be made because the target machine actively refused it. (10061)
[Android Head-Units] dougdude10:
What did you use to get the ip address of you headunit?

is your laptop and headunit connected to the same wifi?

are you using a similar headunit to mine?
[Android Head-Units] alexdr1:
I can't get terminal emulator to open it close right up
[Android Head-Units] dougdude10:
try the app called "termux"
[Android Head-Units] alexdr1:
Im going to try tomorrow but i dont think I can get the command "setprop persist.adb.tcp.port 5555 setprop sys.rkadb.root 1 to work
[Android Head-Units] scheichxda:
Hello

Have a look at:

https://xdaforums.com/android-auto/...-firmware-chinese-7-head-unit-ac8227-t3931863

So I could rescue my unit
[Android Head-Units] yenkai1988:
Does it root method gonna work with my China made head unit?

Android: YT9216B_00002_V004_20190729

Andriod os: Android 8.1 Go XY Auto: 3.0 (8227L)

Can Bus: 3.0 (8227L)

DDR : 1G FLASH: 16G

cpu: A7 1.3GHz x 4

display: 1024*600

MCU: 3.1 (8227L)

Model number: 8227L_demo

Android security patch level: November 5, 2017

Kernel Version: 3.18.22 gangli@zx-PowerEdge-R730 #27 Mon Jul-29 20:35:24 CST 2019

Build number: android-trunk-m0.AC8227L-V1.0

Custom build version: android-trunk-0.AC8227L-V1.0
[Android Head-Units] SchwabSRB:
Dear [MENTION=4565376]kavirz[/MENTION] or anyone who knows ,

is it safe to connect male to male usb with device (pc laptop to 8227L device) , could i damage device or pc doing that ?

CPU:8227L MTK AC8227L

1.5GHz Cortex A7 quad-core

android 9.0 System

Thank you .

Regards

Marko
[Android Head-Units] jmckeejr:
it is ok, i dont think it will work for adb but it is how you would flash updates or recovery (using sp flash tool). It will not damage either just by plugging it in. I have not flashed yet but have tried the plug to see if i could root via adb. Im going to flash recovery tomorrow/today and been researching it all day.
[Android Head-Units] SchwabSRB:
I bought HAMA USB male to male , and on cable is red sticker "Attention: Do not use as USB direct connecting cable between 2 PC/notebooks" ,that bring concerns to me .
[Android Head-Units] jmckeejr:
PC to PC no, PC to radio yes. My radio actually came with this cable but I still can't flash anything nor does adb have root privilege to let me install root unfortunately. Guess I keep looking.

My radio says model yt9217 Android 9, same cpu as you

Edit: I also found out the radio needs to be completely disconnected to flash anything. Only the USB should be attached. I tried to flash while connected but not turned on and almost got brick
[Android Head-Units] vasyl91:
Instruction posted by dougdude10 works fine but under no circumstance update those damn binary files!! Unles you're sure that you can easily hard reset your device or flash su unroot. Orher way you'll end up with bricked head unit.
[Android Head-Units] reednoel4u@yahoo.com:
Hi dougdude10,

I did step by step but have trouble:

C:\adb>adb connect 192.168.1.10:5555

* daemon not running; starting now at tcp:5037

* daemon started successfully

connected to 192.168.1.10:5555

C:\adb>adb shell

root@android:/ # su @#zxcvbnmasdfghjklqwertyuiop1234567890,.

root@android:/ # remount

sh: remount: not found

In this command error, and can't continue, please help.

Thanks

Reed.
[Android Head-Units] Slash6386:
Please h e l p ! :'(

Hi guys, really need you help on my issue. I have a Alps AC8227L_Demo car android head unit. I had recently flashed (using SP Flash tool) a rooted TWRP firmware and it was working fine. Unfortunately, while trying something, I flashed accidentally in "Format All+Download" mode and since then, my device wont boot. It does turn on but only shows black light with no further action. It also gets detected on my laptop through usb male to male cable but then again throws error when I try to flash it again. I suspect format all has wiped the bootloader. I have come across many people with similar problems but with no concrete solution/steps to resolve this. Can anyone please help ?? I'm really desperate. :(
[Android Head-Units] alecxs:
you need to flash complete stock ROM. Ask someone to make a full ROM dump from similar device, or find a download
[Android Head-Units] kavirz:
New AC8227L models now coming with full Android 8.1. Just got a few 9 inch models and confirmed it with CPUZ on Android. Does seem a bit laggy and unrefined but if I disable transitions, it is decent. Screen quality does not seem as nice and menu options everything. Will run proper tests later this week.

---------- Post added at 02:21 PM ---------- Previous post was at 01:58 PM ----------

Two things I noticed since I have been doing these units:

1) XY Auto on the board is the manufacturer of the most common mtk8227l board (currently). This runs Android 6.0 but shows Android 8.1 go and the CPUZ reading for APK level should match Android 6.0.

2) If the board does not say XY Auto, then it might be the new board running a slower version of Android 8.1 but it is really 8.1 with CPUZ reading apk level 27.
[Android Head-Units] alecxs:
so in other words, these products are scams?
[Android Head-Units] jonalowe:
In terms of running Android 9.1, yes. But they seem to run well on Android 6.x. My unit is supposed to have 2gb ram, but CPU-Z shows 1gb. I don't know why the sellers can't be honest. I love the form factor, being ultra thin, and it's fast and smoorh
[Android Head-Units] kavirz:
Not a scam. But really decent device when running Android 6.x. It would be better if sellers were honest as they can show the real settings but they always try make it look better and lying on the spec sheet.

The new version I have running real Android 8.1 is actually decent. After tweeking the transition speeds, it is quite quick. Wish it was Android 8.1 Go instead of full Android 8.1 as it would be quicker on the GO version. Feels a little slower then the Android 6.x version but also the whole chipset is different. Completely different everything so don't think we can port it to XY-Auto's chipset.
[Android Head-Units] marchnz:
So not a scam, but misrepresenting a product, and you're wishing they were honest - that's called a scam!

Suggest not buying from these scammers and make sure to give appropriate feedback to protect others from this scam.
[Android Head-Units] kavirz:
Fair enough. The new version once I have optimized, they will be awesome. Think due to them being still at the beginning of their manufacturing cycle, the OS still needs a lot of work but are really Android 8.1.

The real scammy ones are the ones that say 2gb ram but you get 1gb. Where the actual hardware specifications is incorrect on what they sold you. I agree the Android version should be correct as well but worst when they screw you over on actual hardware. There is a 0.75gb model on the mtk8227l but I would never order that to save money.
[Android Head-Units] BOOMER-USA:
Xtrons psd60unk / ts907 / mtk8227l /

EDIT:

Thanks to the XDA site I was able to recover the HU with an older 8227L bin file but looking for the OEM XTRONS BIN/FIRMWARE.

See here for more info: https://xdaforums.com/android-auto/android-head-units/looking-xtrons-8227l-binary-pic-inside-t4049693

====================

Hi. I have a XTRONS PSD60UNK. Loved the design and UI of the radio...

I followed the instructions on page 10 for gaining root access BUT UNFORTUNATELY FORGOT about the step about NOT letting SuperSU UPDATE the binary. Otherwise it looks like it would have been successful. Now I have a brick.

Can anyone please assist me with resolving my issue so I can get my HU working?

Right now the unit boots with vehicle boot image I initially selected, then a Android logo ( I was able to rename the boot_animation.zip file to boot_animation.old while doing the ADB) so now the Android logo is a still default type Android image but the boot up doesn't go any further. I can't seem to get it into recovery mode but don't know what to do if I did anyway.

Thanks in advance for any replies and assistance.
[Android Head-Units] Frostbourn:
Any chance to get preinstalled NetNavi.apk from this unit?
[Android Head-Units] sn00per77:
Hello guys, i need help with china music...

I have such a radio

ANDROID YT9216B_00002_V004_20190729

SYSTEM : 9.1 XYAUTO: 3,0 (8227L) CAN BUS: 3;0 (8227L)

DDR:4G RASH: 32G cpu: A71.3GHz x 4

DISPLAY 1024*600

MCU1: 3.1 (8227L)

i think this fake.

but i have good prog - AIDA

and that's what she showed

android 8.1 GO

API 23

Android id 343e65327412ca49b

ID assembly YT9216B_00002_V004_20190729

ID MRA58K

version core 3.18.12 (wang@zx-PC1) (gcc version 4.8 (GCC)) #5 SMR PREEMPT Mon Jul 29 11 14:39 2019

manufacturer alps

model 8227L_demo

equipment ac8227l

platform ac8227L

product full_8227L_demo

4xARM Cortex A7 @ 1118Mhz

32bit ARMv7

I can’t find software for updating firmware

what me do?
[Android Head-Units] rockrider81:
Hello to all

I read the whole thread and congratulate everyone.

I inquired about this device and I read dozens of pages that I got a headache :)

Last week I purchased one of these devices and like many others I managed to block it (black screen).

I wanted to do a DUMP of the Rom and change the recovery to change only the RADIOFM.apk as the Chinese original does not have RDS and does not allow you to customize memories etc.

In the end I bought another new 8227L !!

*

The locked device will keep it on standbay.

Unfortunately the dealer (Bangg00 d) for the moment is not responding to my requests for assistance, I asked him if he sent me a flash ROM to restore it, no answer.

Even if you probably already know it, there is a thread on 4PDA on which you can find all the possible files on this device including various DUMPs which may perhaps be useful for recovery.

My ROM Y9213B_00008_V003_20191029 unfortunately is not available but maybe you can find something for your devices as they are all different; I hope you find it useful.

To read, activate the chrome translator.

https://4pda.ru/forum/index.php?showtopic=936535
[Android Head-Units] emta43:
Connection not possible, the device refused connection (10061)

Thank You, good job. It seems that my terminal on the head unit YT8216B is blocked internally. Ive tried adb kill-server, adb connect, every time the same story. USB is locked also (not visible in WIN10) The ping is able to see the device, but every 5th ping is lost.

Any IDEA, tip, trick? :)
[Android Head-Units] georgegreece:
Help me

how did you do root? I have the same system
[Android Head-Units] jerome_062:
Hello every body. I have a yt9218c .now i can root this and active multi windows. But when i use TomTom Go the sound of this notification stop the sound of radio ( or bluetooh musique) alway. Can you help me for this problem ? Thank .sorry for my english [emoji846]

Envoyé de mon SM-N960F en utilisant Tapatalk
[Android Head-Units] jerome_062:
Hello friends,. I have a yt9218b and y try to install rds fmradio but fmradio.apk and GalaPublicResource.zip not compatible. Can you help me please ? Thank you.

Envoyé de mon SM-N960F en utilisant Tapatalk
[Android Head-Units] fabiomdj:
Root successfully

Obrigado pessoal pela ajuda, especialmente a dougdude10.

Caso alguém aí também esteja na dúvida com relação a versão do seu equipamento, vou deixar as especificações do meu para comparação nas imagens abaixo.

Thanks guys for the help, especially dougdude10.

In case anyone there is also in doubt regarding the version of your equipment, I will leave the specifications of mine for comparison in the images below.

[IMG="1"]https://lh3.googleusercontent.com/Avit8gzTC7h6zdiMmy2gkYvQV0jxJMy0MvFJbM5uZ16OT0_IXZ7Dw37u0TbaGLmqbzttYFyqYDFcmhtEeWjWrDya2mCn4upSOsiIvM9Znoa-uSe2Oqfz_2en8Lem0Vi3VFKlR27hUEXZ2R4sMqth5kaCP--8ruaQb9dPos6YlUdwoV4OG48uhkV2kI2PUp3w5uRL96JoN0FYBk1I5UDOueI5mL_sQCMRmyHMJmCCDZbXYHbyqMfQIBFpRe85iOgyQASRIqHcasOiuym-SxpJv2igQs5jscM63K046DUHEgVyBTm-QMn1H1Q5PPcpyvZUTZIFIfT3g4ROodhUKUADj-13SKEkHj1lQwxF89AsnuCQXO0KWPkYl3DSIvHu761Z-RgQKBbr2OnVIly5bTMz09UYYpIfpNEsUbs6hjE9gUTs9QsMI6484fhRvV4EuSYVWAznmH6AjqHOhpk9NP_FVVNjPmDlsMOeLVQL2PRBpaG24o_dUhD50D9QHXHQB2oVK3QInv7j2UxZwK44hU7rsQUR7EUrG_mHpuNgRIsmG0tyk3dmS1WieqYPBkgpC0BAwu-7oeMOKsUgzFWEQ3ybIuNg-ukE9n_N8bTz9y_l2QZ2tJG1PS4ZLmk6N-n3cC97LSGPZ-8ffr9g60CQ1nQ0-wauTbomHwGvV_uBUSDNZ1gvAQRnbWgZRohO3jx76lw=w1723-h970-no[/IMG]
[Android Head-Units] steftours:
password is 12345678
[Android Head-Units] H4MZ4:
I kept getting a buffer error or segmentation fault when switching to superuser mode