Database Users

BOSION ANDROID 4.4.2 head unit

i edited this since the unit is identified and i see that a lot of this units are being sold right now. the goal is to people post firmwares for the unit, root methods, mcus...etc.
my unit in the seller description is described as a dual core. altough, when i received, the system is the same, as you can see in the pictures below, but hardware shows a quadcore cortex A7.
many people achived root with kingoroot.
my unit, per example, wont gain root. ive tried every root app i can remember. with kingoroot, it reaches 90% and it freezes and reboot. also, sometimes when it boots, radio and music app have force close erros and i have to reboot the unit.
people that have root, can you access the mcu.bin and post it here?
EDIT
____________________________________________________
this unit is being sold both in dual core allwinner t2 and quadcore allwinner t3
in the dual core the root can be achived with kingroot or kingoroot apk.
in the quadcore, my case, no root method has been found. i cant connect the unit to the pc so can only try the android versions.
below are firmwares for the dual core and quadcore.
MCU update guide for both models - put the mcu.bin in the root of micro sd card, insert in the unit. a pop up will appear asking for update the mcu, just click ok and let it finish.
updating the full fw. all firmwares come with phoenixcard. open phoenixcard, slect your microsd drive letter, select format to normal, press ok, select image and press burn. after that, turn off unit insert micro sd and turn on unit. it will upgrade. when it finish, black screen will appear, turn off unit, remove card and turn on.
NOTE - everytime i tried to burn the img with phoenixcard in the internalcard reader, i got errors. both in deskptop and laptop. had to use external card reader.
Dual Core FW and MCU
fw may 2016 - https://yadi.sk/d/Eo2U4zfFtXFh6
mcu - https://yadi.sk/d/C5AQ1mOHtWSxu
QuadCore FW and MCU from 09/09/2016
FW - https://mega.nz/#!X50HQS7Q!V6fYDvRY1g_l8epyyxy4GH2mITGRS_1BRCBbc4-IyKI
MCU - https://mega.nz/#!H01jzAIY!GQJzSudDi632ThLsIb5H-IGU1-6sHkyUPzjg7Rwbcu0
video instructions included
________________________________________________________________________________________________________________
Secret Menu tested on quadcore instructions.
go to settings, about device and tap kernel, tap os version, tap kernel, tap os version, tap kernel, tap os version. factory settings menu will apeear. three times each, intercaleted. this have to be accessed because some people after flashing fw, the radio fm app doesnt work so you have to go here and select radio model 7786

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

that launcher looks kind of cool.
I have no idea what it is, but there seems to be a lot of questions like this recently. Where do you all get these head units that you have no idea what they are?

looks like a bosion. i have the same one. root is available. i rooted with kingo root universal method. I'm hoping to find out how to upgade to 5.1 or install a custom rom. If you want to change the look, nova launcher works without crash, dont install apex
---------- Post added at 03:08 PM ---------- Previous post was at 02:59 PM ----------
pnonu23 said:
looks like a bosion. i have the same one. root is available. i rooted with kingo root universal method. I'm hoping to find out how to upgade to 5.1 or install a custom rom. If you want to change the look, nova launcher works without crash, dont install apex
Click to expand...
Click to collapse
also for some reason gmaps works on this 4.4 device with voice recognition so I deleted IGO cause it rearely boots if my flash drive is in. FM radio on my unit doesnt cut off. also freezes when i plug my 2tb hd up to usb. runs kodi and youtube flawlass tho. just wish small makers like this quit locking down their android products and open up support pages. I too was trying to get usb debugg to work but they locked the developers option

pnonu23 said:
looks like a bosion. i have the same one. root is available. i rooted with kingo root universal method. I'm hoping to find out how to upgade to 5.1 or install a custom rom. If you want to change the look, nova launcher works without crash, dont install apex
---------- Post added at 03:08 PM ---------- Previous post was at 02:59 PM ----------
also for some reason gmaps works on this 4.4 device with voice recognition so I deleted IGO cause it rearely boots if my flash drive is in. FM radio on my unit doesnt cut off. also freezes when i plug my 2tb hd up to usb. runs kodi and youtube flawlass tho. just wish small makers like this quit locking down their android products and open up support pages. I too was trying to get usb debugg to work but they locked the developers option
Click to expand...
Click to collapse
mine sometimes when it boots, i have to flash the mcu i found on the web. this because the radio app and the music app force close. can anyone provide MCUS for this unit?
kingo root doenst work on mine. its reaches 90%, the unit freezes and reboot

people that have root, can you access the mcu.bin and post it here?

nosidefcp said:
people that have root, can you access the mcu.bin and post it here?
Click to expand...
Click to collapse
dont know what you want done, but i can help if you tell me how to do it. Dont know how to access a mcu.bin.
In the meantime i have a 1.15 update file with instructions on how to update, that the seller sent me, if anyone is interested. I'm a noob to these mcu boxes.

pnonu23 said:
dont know what you want done, but i can help if you tell me how to do it. Dont know how to access a mcu.bin.
In the meantime i have a 1.15 update file with instructions on how to update, that the seller sent me, if anyone is interested. I'm a noob to these mcu boxes.
Click to expand...
Click to collapse
hi. thank you for being available. I don't know if the mcu.bin file is stored somewhere but I know for sure that without rot, I cant find it. my hope is that if you have root access, with root explorer you can find the file. so please download root explorer and then, with the search option just type mcu and/or mcu.bin and see if root explorer find that file. if yes, please upload it here. let me know

nosidefcp said:
hi. thank you for being available. I don't know if the mcu.bin file is stored somewhere but I know for sure that without rot, I cant find it. my hope is that if you have root access, with root explorer you can find the file. so please download root explorer and then, with the search option just type mcu and/or mcu.bin and see if root explorer find that file. if yes, please upload it here. let me know
Click to expand...
Click to collapse
hello ,
i have the same head unit and had problems with it .
so i got an update from the seller . mcu.bin.
extract the mcu , put it on a sdcard
and insert the card in the unit.

so anyone found a root method for the quadcore model? i have a new fw and new mcu from 09/09 all working fine but i wanna remove the radio app and install another, but tat just with root...kingo and kingroot doesnt work

nosidefcp said:
so anyone found a root method for the quadcore model? i have a new fw and new mcu from 09/09 all working fine but i wanna remove the radio app and install another, but tat just with root...kingo and kingroot doesnt work
Click to expand...
Click to collapse
can you post your MCU ?

Not sure if this is the place but I'm having issues getting the head unit to pair with the OBDII . When I scan it can be found , it says tap to pair and it does nothing. Also, A Bluetooth scan shows something there in Chinese characters. I remove it and it keeps coming back. there IS NOT A LOT I WOULD REALLY CHANGE ABOUT THE HEAD UNIT BUT I WANT TO USE MY obdii

Hi,
Do you know if the firmware you attached supports this?
m.es.aliexpress.com/item/32669808886.html

antonio2k said:
Hi,
Do you know if the firmware you attached supports this?
m.es.aliexpress.com/item/32669808886.html
Click to expand...
Click to collapse
yes it does. just check when the unit arrives if its the quad or dual core and choose the fw

Hi,
i have a quad core. But no root.
can you tell me how i can root?
This is my Head Unit
ww w.aliexpress.com/item/Quad-Core-Android-4-4-car-dvd-player-gps-2Din-7-Inch-For-Volkswagen-VW-Skoda/32321954979.html?spm=2114.13010608.0.0.0RlJVJ
With Android 4.4.2

shatch said:
Not sure if this is the place but I'm having issues getting the head unit to pair with the OBDII . When I scan it can be found , it says tap to pair and it does nothing. Also, A Bluetooth scan shows something there in Chinese characters. I remove it and it keeps coming back. there IS NOT A LOT I WOULD REALLY CHANGE ABOUT THE HEAD UNIT BUT I WANT TO USE MY obdii
Click to expand...
Click to collapse
Hi there, I've bought a wifi odb2 scanner from eBay which seems to work, I also had an issue with my Bluetooth scanner not working.
Apart from that the player is actually ok, I would like to root, though. For instance, I'd like to change the default music player to poweramp or something similar so that when I press the hardware buttons on the side poweramp comes on instead of the pre-installed garbage.

some unit same problems
hello i have the exact same unit but app versio 2.1 mcu 1.12 some was talkin about the 1.15
and wath about root ?? any news?? also have the same bluethoot problem only pairs with phones
tanks every one
also ...
found this on rooting allwiner
this is a copy from theregister site
This is what a root debug backdoor in a Linux kernel looks like
Allwinner's all-loser code makes it into shipped firmware
reddit Twitter Facebook linkedin 159
9 May 2016 at 23:20, Richard Chirgwin
A root backdoor for debugging ARM-powered Android gadgets managed to end up in shipped firmware – and we're surprised this sort of colossal blunder doesn't happen more often.
The howler is the work of Chinese ARM SoC-maker Allwinner, which wrote its own kernel code underneath a custom Android build for its devices.
Its Linux 3.4-based kernel code, on Github here, contains what looks to The Register like a debug mode the authors forgot to kill. Although it doesn't appear to have made it into the mainstream kernel source, it was picked up by firmware builders for various gadgets using Allwinner's chips.
It's triggered by writing rootmydevice to the special file /proc/sunxi_debug/sunxi_debug. That gives the current running process root privileges. If that file is present on your device or single-board computer, then you need to get rid of it. This is the code that checks for the magic write:
if(!strncmp("rootmydevice",(char*)buf,12)){
cred = (struct cred *)__task_cred(current);
cred->uid = 0;
cred->gid = 0;
cred->suid = 0;
cred->euid = 0;
cred->euid = 0;
cred->egid = 0;
cred->fsuid = 0;
cred->fsgid = 0;
printk("now you are root\n");
}
Tkaiser, a moderator over at the forums of the Armbian operating system (a Linux distro for ARM-based development boards) notes there's a number of vulnerable systems in the field.
As tkaiser writes, echo "rootmydevice" > /proc/sunxi_debug/sunxi_debug "from any process with any UID will get root, and it's probably remotely exploitable if combined with networked services that might allow access to /proc."
He adds: “This security flaw is currently present in every OS image for H3, A83T or H8 devices that rely on kernel 3.4.”
As well as all Orange Pi images except for Armbian's freshly patched 5.10, these vulnerable gadgets include ARM dev boards from FriendlyARM, SinoVoip (its M2+ and M3 Banana Pi boards), Cubietruck, and LinkSprite's pcDuino8 Uno.
There are probably other products out there using the Allwinner
any one knows if its possible it works for us ??

Hello,
Do you have any news about the root of the Bx-411 t3?
Thanks!

Similar problems
I have the quad core model. No access to root as of yet. The seller sent me an upgrade file which doesn't boot. I can't seem to find anyway to make my i-bus work for the steering controls.
Anyone considered windows 7 ?

[ROOT][FLASH][TWRP] Josmile / Xonrich MTK 8227L VW Head unit Android 10

Hi, i'v bought this unit and share all information i can find here.
The unit is very good, runs android 10 but i like to customize further.
Updates:
- Added Magisk install instructions (prefere)
- Just created a TWRP to this unit! Links bellow.
- Added links to last firmware from Josmile.
Looking for:
- Full flashes backup or updated versions from vendor. See down on the page instructions how to do it so you are safe from bricking in future. And share or PM me the link for the dump.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bought from Josmile Store : https://www.aliexpress.com/item/4000088935841.html?spm=a2g0s.9042311.0.0.7d724c4dfvbhO5
Similar to this on Xonrich store: https://www.aliexpress.com/item/4000059343717.html?spm=a2g0o.productlist.0.0.375177ecx7Q4Ro
Not sure who is the original manufacturer.
Specs:
Model 8227L
CPU Autochips AC8227L QuadCore 1,2 GHz MTK 8227L
RAM 2Gb (RS512M32 16 GBits x 32, 1.8/1.2/1.2V, -25~85℃, FBGA178)
ROM 16GB
IPS 1024x600
GPS MT6625L
Radio 7708S (with RDS)
DAC TDA7851L 4x45W
Wi-Fi MT6625L 802.11n
Bluetooth MT6625L 4.0
Kernel 3.18.79 (gcc version 6.3.1 20170404 (Linaro GCC 6.3-2017.05)) [email protected] #28 Mon Oct 28 14:39:22 CST 2019
full_8227L_demo-userdebug 10 O11019 1571038753 userdebug
Build alps-mp-01.mp5
Includes:
CanBus module for steering buttons control and AC head unit visualization, lights, reverse detection and ACC.
Compatible with (at least):
- Volkswagen Golf, Polo, Passat, Eos, Jetta, Tiguan
- Skoda Octavia
Supports:
- GPS
- Video in Front and Rear
- DVR in
- Video Out
- Line In/Out
- USB
- Wifi
- BT
Optional :
- TPMS - Tire Pressure measurement
- DAB radio
- OBD2 ELM327 BT dongle for car diagnostics
- 4G via usb dongle
Original Firmware:
HMI: XRCH.D.Q.F.2.01.2019.11.11.16.00
MCU: TS907.190518(H)
MEDIA: HC_v.2.0.0_190923_1100_e(v1.40)
BTV: BT.19.11.08.1500
New Firmware:
HMI: TSKJ.D.Q.F.2.C02.2020.05.20.10.30
MCU: TS907.190518(H)
MEDIA: HC_v.2.0.0_200416_0930(v1.40)
BTV: BT.20.05.07.1130
Firmware: https://mega.nz/file/ZhklkRpa#8g4I61welZ-F6WYcQFFWLv8wfqngxjreTh3wYwBSjkQ
Instructions: https://mega.nz/file/VwsHmZqL#9qVuMZ-F_v6WYWngSLVLDNLxu9VuME53qmh4YX6rIJE
Codes:
- Change boot Logo: 5678
- Advanced configurations: 8888
Install TWRP
Method 1 (no root, with flash tool):
- Follow instructions of "Unbrick with flash tool" below
- When Downloading, choose the twrp recovery file from this link that i prepared to support this unit. The stock image is also supplied on the flash tool instructions.
- Note: TWRP crashes the UI if the screen times out for 1 minute, so go to settings and disable screen timeout.
Method 2 (with root):
Start a remote adb shell and replace recover partition with the twrp file.
adb push RECOVERY.IMG /tmp/recovery.bin
adb shell
dd if=/tmp/recovery.bin of=/dev/block/platform/soc/by-name/RECOVERY
Root
Method 1 - Magisk via TWRP
Copy Magisk install (tested with v20.4) and Magisk App to an USB drive.
Plug drive reboot to TWRP and choose to install the Magisk install file.
Clean dalvik cache.
Copy the APK to the device /system/app folder for a system application (you could also have the apk manualy instaled before).
Reboot and its done!
Method 2 - With no Root yet
https://forum.xda-developers.com/showpost.php?p=80550729&postcount=100
Warning: never let SuperSu update the su binary or it will not boot anymore and need to fix via TWRP or flash recovery / update.
USB OTA update:
- Plug in a FAT32 formated USB pen with the firmware files "8227L-8.bin" and "8227L-8.upd" saved to the root folder (ask your seller for the updated firmware files and share with us).
- Unit should detect in 30s and update automatically.
Enter Upgrade Mode :
- Plug in a FAT32 formated USB pen with the firmware files "8227L-8.bin" and "8227L-8.upd" saved to the root folder (ask your seller for the updated firmware files).
- Press reset.
- Keep touching the screen with one finger quickly until "detected" appears in green, recovery now starts.
Recovery / Factory Reset:
- Press reset.
- Keep touching the screen quickly with 5 fingers at the same time until "detected, entering recovery" appears.
- Will enter TWRP or do a factory reset if using the stock recovery and reboot after.
Unbrick with flash tool:
- Connect to computer by USB cable (use the 4 pins usb cable not the 6 pin on the back of the unit)
- Flashtool available here : https://mega.nz/#!LAl1FI6D!CJa2AHokZ...2FJ6js2xY/view
- Install drivers
- Launch flash tool
- Use "MTK_AllInOne_DA.bin" Download-Agent (DA).
- Choose "MT3367_Android_scatter.txt" and select the images/partitions you want to replace (files here or can be obtained with full flash backup method)
- Select Download Only
- Choose partitions
- Press Download
- Press reset on the unit
- Process should start and go smooth until 100%.
Full Flash Backup: - (This applies to all MTK chipsets)
- Connect to computer by USB cable (use the 4 pins usb cable not the 6 pin on the back of the unit)
- Flashtool available here : https://mega.nz/#!LAl1FI6D!CJa2AHokZ...2FJ6js2xY/view
- Install drivers
- Launch flash tool
Instructions on how to make a full DUMP device, bypassing the 5-minute limit of the application:
- See this instructions as the basis.
- We do everything as it is written, Save EMMC_BOOT_1 and EMMC_BOOT_2 and other partitions.
- For EMMC_USER, reaching point 3.3, the principle remains the same, only we will have to merge the EMMC_USER region in various parts, depending on the size discovered.
Here are the addresses and lengths of the pieces:
Addresses and Length
-------------- address ---------------- length
1: 0x0000000000000000 0x5C800000
2: 0x000000005C800000 0x5C800000
3: 0x00000000B9000000 0x5C800000
4: 0x0000000115800000 0x5C800000
5: 0x0000000172000000 0x5C800000
6: 0x00000001CE800000 0x5C800000
7: 0x000000022B000000 0x5C800000
8: 0x0000000287800000 0x5C800000
9: 0x00000002E4000000 0x5C800000
10: 0x0000000340800000 0x5C800000
11: 0x000000039D000000 0x08200000 <- adapt to reach the total size you got from the memory test (eg. 0x00000003a5200000).
Get 11 pieces, they need to be combined into 1 file. We use the DOS copy program:
- Open a cmd shell, change to the path where the files are and type:
copy /b file1+file2+file3+filex dump.bin
Next use the WwR program:
- Select File - select the ROM file in autopilot. First specify the merged dump.bin, and then EMMC_BOOT_1.
WwR will check the integrity and if everything is correctly reported that you have full firmware.
- Click "Cut the ROM, trim zeros, ext2/ext3/ext4 in sparse".
- Share you dump on the thread!

@chaveiro thank you for taking the time to detail all the steps in plain English. I could have used it this past weekend when I managed to brick my unit
Certainly helps a lot more than getting Google translate to talk about "drain the dump" and "sew the files" plus my favorite "add the sausages in" - you know it's talking about translating 4pda.ru
One question for you though: I was able to dump the user partition in one go (and my unit has 32GB...so the user partition is twice as big as yours)...what is the "5 minute limit of the application"? Is that WwR related? I never installed it, but then again, I recovered by flashing just recovery and the system image, I never touched the user partition (luckily, intact).

Ipse_Tase said:
@chaveiro thank you for taking the time to detail all the steps in plain English. I could have used it this past weekend when I managed to brick my unit
Certainly helps a lot more than getting Google translate to talk about "drain the dump" and "sew the files" plus my favorite "add the sausages in" - you know it's talking about translating 4pda.ru
One question for you though: I was able to dump the user partition in one go (and my unit has 32GB...so the user partition is twice as big as yours)...what is the "5 minute limit of the application"? Is that WwR related? I never installed it, but then again, I recovered by flashing just recovery and the system image, I never touched the user partition (luckily, intact).
Click to expand...
Click to collapse
Yeah, most of the information come from russian sites and common sense, but for TRWP to work correctly i lost a few hours messing with source code.
The SP Flash tool, gives a flash error after some time (~5 mins) reading, it's not a fixed time, so by reading the flash partially, it's easy to repeat reading just that chunk than the full flash with the risk of it failing to read again. it worked for you, to read in one go, it's nine.
Is your unit like this one or different, can you share your dump or (even better) the firmware update file from the seller?

chaveiro said:
Yeah, most of the information come from russian sites and common sense, but for TRWP to work correctly i lost a few hours messing with source code.
The SP Flash tool, gives a flash error after some time (~5 mins) reading, it's not a fixed time, so by reading the flash partially, it's easy to repeat reading just that chunk than the full flash with the risk of it failing to read again. it worked for you, to read in one go, it's nine.
Is your unit like this one or different, can you share your dump or (even better) the firmware update file from the seller?
Click to expand...
Click to collapse
I used https://forum.xda-developers.com/android-auto/android-head-units/everything-yt9216b-t4007063 to flash my unit as I needed root to fix the bloody radio.
The seller was never replying to my messages so I gave up getting any software from him.
My unit is NOT this one, it's a 9" generic (Carlaoer) 8227L one (YT9216C).
I have to test your suggestion regarding TWRP screen timeout as this is EXACTLY the problem I'm having with mine...it craps out after a while. Didn't time it, but now 1 min sounds about right.
So happy to be able to talk to someone who has actually gone through all this pain :laugh:
As you can see most folks here are just either fishing for software thinking that newer is better or have never looked at flashing and are asking for a guide - which you and others have provided.
---------- Post added at 17:36 ---------- Previous post was at 17:30 ----------
Oh...from the document you linked, the guy is using SP_Flash_Tool_v5.1352.01 and says <<does not work with blocks larger than 4GB>>
I used v5.1924 - maybe they lifted that limitation (FAT32).
---------- Post added at 18:32 ---------- Previous post was at 17:36 ----------
One last thing: you mentioned <<Note: TWRP crashes the UI if the screen times out for 1 minute, so go to settings and disable screen timeout.>>
I thought that would solve my TWRP backup but it didn't
It goes to around 500MB and crashes in a weird way: screen flickers like an old CRT TV that loses H sync - horizontal lines and bit blurry. I was counting on TWRP backup rather than system dump, as even starting the unsigned drivers is a problem on a Win10 machine that will NOT run in safe mode unless I put in the 56 BitLocker key...what a pain.

I thought that would solve my TWRP backup but it didn't
It goes to around 500MB and crashes in a weird way: screen flickers like an old CRT TV that loses H sync - horizontal lines and bit blurry. I was counting on TWRP backup rather than system dump, as even starting the unsigned drivers is a problem on a Win10 machine that will NOT run in safe mode unless I put in the 56 BitLocker key...what a pain.
Click to expand...
Click to collapse
It crashes writing or reading and in what partitions?
Its nice to have more people interested here also., the Russian foruns apart from being in Russian, have too much information, missing links and threads with 1000+ pages. Really difficult to get anywere fast, but useful anyway.
Now i'm on getting the best user experience, do you recommend any Launcher in particular?
BTW: Just updated Root with Magisk instructions (much more clean and stable).

chaveiro said:
It crashes writing or reading and in what partitions?
Its nice to have more people interested here also., the Russian foruns apart from being in Russian, have too much information, missing links and threads with 1000+ pages. Really difficult to get anywere fast, but useful anyway.
Now i'm on getting the best user experience, do you recommend any Launcher in particular?
BTW: Just updated Root with Magisk instructions (much more clean and stable).
Click to expand...
Click to collapse
It crashed after 500-600MB of WRITING the boot partition...USB stick or Internal flah, makes no diff. I REALLY hate SPFlash tools and would have preferred TWRP backup and restore.
BTW: I tried your suggestion to RST and touch the screen with 5 fingers...it did NOT bring me into TWRP. Still don't know how to get there other than from Terminal (reboot recovery) or Magisk Manager.
I use AGAMA for my launcher as after I changed the color it matched perfectly my red interior dashboard and info screen colors...looks like factory (to me )
Try Viper4Android for everything audio EXCEPT radio...it does make a difference. Got it with the ROM I flashed (see last post for the XDA link), but you can install it from Magisk Manager.

8227L-8.bin Upgrade
Hello,
I have tried to update my unit with 8227L-8 files, however nothing happens.
I have tried both USB sockets, unplugged the power for a long time, rebooted through Terminal and pushed the reset button for 20 seconds.
I have also tried your instructions to the letter.
I can see the files in the File Explorer.
I have also tried to format the USB stick with SD Card Formatter.
Tried atleast 4 different versions of the 8227L-8 files.
My unit is not rooted.
Anything else I can do to make it work?

Takip

grvdggr said:
Hello,
I have tried to update my unit with 8227L-8 files, however nothing happens.
I have tried both USB sockets, unplugged the power for a long time, rebooted through Terminal and pushed the reset button for 20 seconds.
I have also tried your instructions to the letter.
I can see the files in the File Explorer.
I have also tried to format the USB stick with SD Card Formatter.
Tried atleast 4 different versions of the 8227L-8 files.
My unit is not rooted.
Anything else I can do to make it work?
Click to expand...
Click to collapse
Tray tapping the center of the screen continuously and intermittently after pressing reset button, if not works try the same but with the finger constantly in the screen (one long taping). The screen should say "detected" or something similar and the upgrade procedure should start.
Regards

Ipse_Tase said:
I used https://forum.xda-developers.com/android-auto/android-head-units/everything-yt9216b-t4007063 to flash my unit as I needed root to fix the bloody radio.
The seller was never replying to my messages so I gave up getting any software from him.
My unit is NOT this one, it's a 9" generic (Carlaoer) 8227L one (YT9216C).
I have to test your suggestion regarding TWRP screen timeout as this is EXACTLY the problem I'm having with mine...it craps out after a while. Didn't time it, but now 1 min sounds about right.
So happy to be able to talk to someone who has actually gone through all this pain :laugh:
As you can see most folks here are just either fishing for software thinking that newer is better or have never looked at flashing and are asking for a guide - which you and others have provided.
---------- Post added at 17:36 ---------- Previous post was at 17:30 ----------
Oh...from the document you linked, the guy is using SP_Flash_Tool_v5.1352.01 and says <<does not work with blocks larger than 4GB>>
I used v5.1924 - maybe they lifted that limitation (FAT32).
---------- Post added at 18:32 ---------- Previous post was at 17:36 ----------
One last thing: you mentioned <<Note: TWRP crashes the UI if the screen times out for 1 minute, so go to settings and disable screen timeout.>>
I thought that would solve my TWRP backup but it didn't
It goes to around 500MB and crashes in a weird way: screen flickers like an old CRT TV that loses H sync - horizontal lines and bit blurry. I was counting on TWRP backup rather than system dump, as even starting the unsigned drivers is a problem on a Win10 machine that will NOT run in safe mode unless I put in the 56 BitLocker key...what a pain.
Click to expand...
Click to collapse
I have Carlaoer. I want RDS radio and android auto. Which firmware should you use?

@bicer79 you quoted my whole post and the link to what I used is in the first line. What else is unclear.... ?
---------- Post added at 13:43 ---------- Previous post was at 13:41 ----------
grvdggr said:
Hello,
I have tried to update my unit with 8227L-8 files, however nothing happens.
I have tried both USB sockets, unplugged the power for a long time, rebooted through Terminal and pushed the reset button for 20 seconds.
I have also tried your instructions to the letter.
I can see the files in the File Explorer.
I have also tried to format the USB stick with SD Card Formatter.
Tried atleast 4 different versions of the 8227L-8 files.
My unit is not rooted.
Anything else I can do to make it work?
Click to expand...
Click to collapse
You might have to go the SPFlash tools route, that's what I ended up doing. Read the post where I got my software to restore the unit.

Ipse_Tase said:
@bicer79 you quoted my whole post and the link to what I used is in the first line. What else is unclear....
---------- Post added at 13:43 ---------- Previous post was at 13:41 ----------
You might have to go the SPFlash tools route, that's what I ended up doing. Read the post where I got my software to restore the unit.
Click to expand...
Click to collapse
Do you mean this thread?
https://forum.xda-developers.com/an...ng-yt9216b-t4007063/post83077925#post83077925
I tried to put in 8227L-8.bin as download agent in SP Flash Tool but I get an error message.
Also I don't have a scatter file for it, just the 8227L-8.upg file.
I have googled SP Flash Tool along with 8227L-8.bin but can't find any relevant information. @zaborrilla
Tried the various tapping and holding techniques but no luck. =/
---------- Post added at 12:43 AM ---------- Previous post was at 12:10 AM ----------
Okay, I think I'm starting to get it.
So in SP Flash Tool:
Download Agent needs to be MTK All in One
Scatterloading file, I use the one from the link I thought you meant.
However, 8227L-8.bin and 8227L-8.upg needs to be in the same folder as the Scatterfile, correct?
So I get these files:
Preloader
LK
ARM2
BOOTIMG
SEC_RO
LOGO
METAZONE
TEE1
TEE2
ANDROID
CACHE
USRDATA
I have selected all except for Preloader, should I uncheck anything else?
Thanks a lot, there is HOPE!

Hi,
Seller Josmile just sent me this:
Firmware: mega.nz/file/ZhklkRpa#8g4I61welZ-F6WYcQFFWLv8wfqngxjreTh3wYwBSjkQ
Instructions: mega.nz/file/VwsHmZqL#9qVuMZ-F_v6WYWngSLVLDNLxu9VuME53qmh4YX6rIJE
Use at your own risk, not tested yet
Regards

zaborrilla said:
Hi,
Seller Josmile just sent me this:
Firmware: mega.nz/file/ZhklkRpa#8g4I61welZ-F6WYcQFFWLv8wfqngxjreTh3wYwBSjkQ
Instructions: mega.nz/file/VwsHmZqL#9qVuMZ-F_v6WYWngSLVLDNLxu9VuME53qmh4YX6rIJE
Use at your own risk, not tested yet
Regards
Click to expand...
Click to collapse
Is that with Android 8 or higher?
Those instructions are a little bit different than others, I shall try with my bin and upg file. =)
Thank you.

They are for the model of the first post, the one that I have. Its android 10, I dont know if its really 10 or fake, I have to check it.
Regards

So I tried the new method in the description but it didn't work.
My unit won't recognise the tapping, so that method is out.
When I connected the unit USB male to PC USB male, nothing happened.
Might be the USB cable so I have soldered it.
Question: Should the unit be able to show in the PC when turned off?

grvdggr said:
So I tried the new method in the description but it didn't work.
My unit won't recognise the tapping, so that method is out.
When I connected the unit USB male to PC USB male, nothing happened.
Might be the USB cable so I have soldered it.
Question: Should the unit be able to show in the PC when turned off?
Click to expand...
Click to collapse
I read somewhere, at least for my unit, that the usb Drive used for updating should be connected to the usb cable that has 4 wires( in my unit, one cable has 6 wires).
Regards

zaborrilla said:
I read somewhere, at least for my unit, that the usb Drive used for updating should be connected to the usb cable that has 4 wires( in my unit, one cable has 6 wires).
Regards
Click to expand...
Click to collapse
Thanks, I'm using the 4 wire USB cable, tried the 6 wired one too.
Pictures of my unit:
https://drive.google.com/file/d/12DS9sHgtWj68V9LZc2AdVHZ1ATnwuvrh/view?usp=sharing
https://drive.google.com/file/d/1JAtAzFfHVo4aOhlowu2dZ8JTlzjfhJV2/view?usp=sharing

grvdggr said:
Hello,
I have tried to update my unit with 8227L-8 files, however nothing happens.
I have tried both USB sockets, unplugged the power for a long time, rebooted through Terminal and pushed the reset button for 20 seconds.
I have also tried your instructions to the letter.
I can see the files in the File Explorer.
I have also tried to format the USB stick with SD Card Formatter.
Tried atleast 4 different versions of the 8227L-8 files.
My unit is not rooted.
Anything else I can do to make it work?
Click to expand...
Click to collapse
grvdggr said:
Thanks, I'm using the 4 wire USB cable, tried the 6 wired one too.
Click to expand...
Click to collapse
You will NOT get any notification from PC when connected.
The scatter file IS included in the software I linked to if this is what you want to flash. Methinks however that we're talking different units here. The topic was for the VW unit, the software nomenclature looks nothing like mine. So make sure you are looking at software for YOUR unit.
Use the 4 pin USB connector, remove power, and test doing a readback : only when you start the process plug in the USB cross cable and you will see the PC detecting the unit (red bar at the bottom, changing colors of read is successful).
Worst-case scenario, you might need to look for thev2 test points to short, but I only needed that because I screwed up the preloader one time...never needed after restoring it.

zaborrilla said:
Hi,
Seller Josmile just sent me this:
Firmware: mega.nz/file/ZhklkRpa#8g4I61welZ-F6WYcQFFWLv8wfqngxjreTh3wYwBSjkQ
Instructions: mega.nz/file/VwsHmZqL#9qVuMZ-F_v6WYWngSLVLDNLxu9VuME53qmh4YX6rIJE
Use at your own risk, not tested yet
Regards
Click to expand...
Click to collapse
Just updated my unit. All went OK. I post pictures of before versión, after version, different launcher after install, cpu-z (how can I see if is really android 10?), etc...
Summary: All works ok, launcher is different.

[GUIDE] Mediatek Android Head Units - How to fully backup or restore backup with SP Flash Tool (beginner-friendly tutorial)

Hi all,
I decided to make 3, very beginner-friendly guides on how to fully backup your Android Head Units and how to restore those backups. These guides are made primarily for the SuperMOD packages in my signature but will generally apply to any Mediatek-based device.
Video Guide - How to full backup your Android Head Unit
This guide will help you:
Backup your whole flash drive with SP Flash Tool
Create your own Scatter and Preloader file
Create your own shareable firmware
PDF Guide - How to restore your backup with SP Flash Tool
This guide will help you restore your backup on a working Android head unit, type MediaTek YT921xxx, with available flash dump
Video Guide - Test Point recovery of a bricked head unit
This guide will help you restore your non-working Android head unit, type MediaTek YT921xxx, with available backup
If you encounter errors during these procedures, like DRAM failures etc, here are the main reasons as to why this might be happening:
Your Preloader and/or Scatter file is incompatible - extract your native scatter and preloader from your backup file
Incompatible SP Flash Tool version
Try to insert the USB cable within 2 seconds of pushing 'WRITE' or 'DOWNLOAD'
Use USB 2.0 ports if available rather than USB 3.0
Make sure your USB port does not go into sleep mode
Your Mediatek drivers are not properly installed on your PC
Faulty or incompatible USB cable - make sure it's shorter than 1m.
Refer to this guide on information about all the errors
------------------------------------------
Thanks! And if this post is helpful to you please don't forget to "like" it.
Enjoy!​

iceblue1980 said:
I wanted to share a guide that I translated from Russian forums and adjusted for the English speaking folks on how to successfully import a memory dump into you chinese unbranded Android car stereo head unit, normally a 8227L_demo device with Android type YT9213, YT9216, YT9217, YT9218 and similar.
The guide is made for beginners and is with pictures. You can view the PDF file here and I suggest you download it for better viewing quality and picture detail.
If you encounter errors during the procedure, like DRAM failures etc, here are the main reason for why this is happening:
1. Your Mediatek drivers are not properly installed on your PC
2. Try another Flashtool version (for me only version 5.1824 worked thus far) - this should solve the issue 90% of the time.
3. Ensure your USB cable is shorter than 1m and is fully working.
I am also going to make a separate post on how to perform a full backup of the same unit types, using the same tools. As you know it is always recommended to backup your original ROM before starting experimenting. Thank you and I hope this is helpful to you folks out there.
Click to expand...
Click to collapse
You know it. We know it. That you are the best!!! Thanks a lot!

Flashtool version is VERY critical, as I found out the hard way. Please remember to follow each author's instructions to the point.

iceblue1980 said:
I wanted to share a guide that I translated from Russian forums and adjusted for the English speaking folks on how to successfully import a memory dump into you chinese unbranded Android car stereo head unit, normally a 8227L_demo device with Android type YT9213, YT9216, YT9217, YT9218 and similar.
The guide is made for beginners and is with pictures. You can view the PDF file here and I suggest you download it for better viewing quality and picture detail.
If you encounter errors during the procedure, like DRAM failures etc, here are the main reason for why this is happening:
1. Your Mediatek drivers are not properly installed on your PC
2. Try another Flashtool version (for me only version 5.1824 worked thus far) - this should solve the issue 90% of the time.
3. Ensure your USB cable is shorter than 1m and is fully working.
I am also going to make a separate post on how to perform a full backup of the same unit types, using the same tools. As you know it is always recommended to backup your original ROM before starting experimenting. Thank you and I hope this is helpful to you folks out there.
**ONLY UPLOAD 'BOOT1' IF YOUR UNIT IS BRICKED, OTHERWISE JUST UPLOAD THE 'ROM_USER" FILE.
Click to expand...
Click to collapse
Hello. Pdf file is not available for download.

raionshinzo said:
Hello. Pdf file is not available for download.
Click to expand...
Click to collapse
Thanks, please try again. The link has been updated.

iceblue1980 said:
Thanks, please try again. The link has been updated.
Click to expand...
Click to collapse
Thanks for the reply and for updating the file.
Can You please help me with this issue?
I have two HU 9216bj with 1 GB ram and 16GB storage. The problem is that one is XY auto 1.1 and is running without any issues. Another one I bought came with XY auto 6.5. However, after some time this one started to cause problems such as when I start the car half of the screen started to splash like rain. The seller changed my unit but this problem did not go away. So I contacted him again and he updated my unit to XY auto 6.8 but even after the update, the problem is there. He told me that these 6.5 and 6.8 updates are causing problems and asked me not to update my XY auto 1.1 HU which is still working fine.
So I made a dump file of 9216bj XY auto 1.1 and rewrite it on the XY auto 6.8 but the unit goes black screen and I have to use the original emmc_user file of 6.8 to restore it. These units are not 10.1 andriod. The droid info showed 8.1 and CPU Z showed 9.1. Frankly speaking, I don't know which android it is.
I have attached the images of both the 9216bj 1GB 16GB below. Kindly guide me in this regard.
Thanks again.

raionshinzo said:
Thanks for the reply and for updating the file.
Can You please help me with this issue?
I have two HU 9216bj with 1 GB ram and 16GB storage. The problem is that one is XY auto 1.1 and is running without any issues. Another one I bought came with XY auto 6.5. However, after some time this one started to cause problems such as when I start the car half of the screen started to splash like rain. The seller changed my unit but this problem did not go away. So I contacted him again and he updated my unit to XY auto 6.8 but even after the update, the problem is there. He told me that these 6.5 and 6.8 updates are causing problems and asked me not to update my XY auto 1.1 HU which is still working fine.
So I made a dump file of 9216bj XY auto 1.1 and rewrite it on the XY auto 6.8 but the unit goes black screen and I have to use the original emmc_user file of 6.8 to restore it. These units are not 10.1 andriod. The droid info showed 8.1 and CPU Z showed 9.1. Frankly speaking, I don't know which android it is.
I have attached the images of both the 9216bj 1GB 16GB below. Kindly guide me in this regard.
Thanks again.
Click to expand...
Click to collapse
Unfortunately the Android 10 units are very poorly built and there are no custom firmware available afaik. The 8.1 and 9.1 units are doable but 10s should be avoided.

iceblue1980 said:
Unfortunately the Android 10 units are very poorly built and there are no custom firmware available afaik. The 8.1 and 9.1 units are doable but 10s should be avoided.
Click to expand...
Click to collapse
Hello.
The android version is 9.1. I have attached the images below. I would appreciate if you can guide to an older or stable firmware or its dump for YT 9216BJ mipi 1280×720.
I have tried many roms from XYgala but the screen goes black even after reset it remains black.
I created a dump by making an scatter file with MT8127 processor and emmc memory and then did a read back of boot 1 boot 2 and user.
Thanks.

raionshinzo said:
Hello.
The android version is 9.1. I have attached the images below. I would appreciate if you can guide to an older or stable firmware or its dump for YT 9216BJ mipi 1280×720.
I have tried many roms from XYgala but the screen goes black even after reset it remains black.
I created a dump by making an scatter file with MT8127 processor and emmc memory and then did a read back of boot 1 boot 2 and user.
Thanks.
Click to expand...
Click to collapse
Try this guide.

iceblue1980 said:
I am also going to make a separate post on how to perform a full backup of the same unit types, using the same tools.
Click to expand...
Click to collapse
That could be very helpful.
Is it available ?

oferyuval said:
That could be very helpful.
Is it available ?
Click to expand...
Click to collapse

iceblue1980 said:
oferyuval said:
That could be very helpful.
Is it available ?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
The linked clip is from 2014.
An updated guide from 2019 from the same guy can be found here: https://forum.hovatek.com/thread-21970.html

oferyuval said:
The linked clip is from 2014.
An updated guide from 2019 from the same guy can be found here: https://forum.hovatek.com/thread-21970.html
Click to expand...
Click to collapse
Isn't this a guide for WwR tool rather than Flash Tool?

iceblue1980 said:
Isn't this a guide for WwR tool rather than Flash Tool?
Click to expand...
Click to collapse
It uses WwR to make a scatter file and than SP Flash Tool

Okay, I updated the OP. Now there is a guide both for making full backup and restoring it. Hopefully, this will help you guys out there.

iceblue1980 said:
Okay, I updated the OP. Now there is a guide both for making full backup and restoring it. Hopefully, this will help you guys out there.
Click to expand...
Click to collapse
Great, many thanks !!! I'll try to follow it.

The new backup guide looks very clear and comprehensive.
I'll use it to make my first backup attempt. Thank you for taking the time to make it.
Two questions:
1. It seems that the values from the scatter file downloaded at 8. are used only for downloading preloader.Xxx.bin. Is that correct ?
2. Should we disconnect the usb cable from the pc at 17. before reconnecting it in 23. ?

oferyuval said:
The new backup guide looks very clear and comprehensive.
I'll use it to make my first backup attempt. Thank you for taking the time to make it.
Two questions:
1. It seems that the values from the scatter file downloaded at 8. are used only for downloading preloader.Xxx.bin. Is that correct ?
2. Should we disconnect the usb cable from the pc at 17. before reconnecting it in 23. ?
Click to expand...
Click to collapse
Happy to hear that.
As for your questions:
The scatter file included in the software package downloads is applicable to the respective head unit type, that the software package is made for. This means you can use it to backup your head unit, without the need of creating your own scatter file. And the best part is - if the scatter file isn't compatible with your head unit, it's a good indication that the software package is not compatible with your device.
No, as you are instructed to disconnect the USB cable in step 15.

iceblue1980 said:
Happy to hear that.
As for your questions:
The scatter file included in the software package downloads is applicable to the respective head unit type, that the software package is made for. This means you can use it to backup your head unit, without the need of creating your own scatter file. And the best part is - if the scatter file isn't compatible with your head unit, it's a good indication that the software package is not compatible with your device.
Click to expand...
Click to collapse
This makes perfect sense if I had a verified firmware or at least verified scatter file.
I don't know how to get one for my device.
I would like to backup the original firmware before loading a new firmware, so I can restore the original incase the new one is not compatible. In this case I am not sure that using a scatter file from the new untested firmware is a good idea.
iceblue1980 said:
2. No, as you are instructed to disconnect the USB cable in step 15.
Click to expand...
Click to collapse
Sorry, I missed this one

oferyuval said:
This makes perfect sense if I had a verified firmware or at least verified scatter file.
I don't know how to get one for my device.
I would like to backup the original firmware before loading a new firmware, so I can restore the original incase the new one is not compatible. In this case I am not sure that using a scatter file from the new untested firmware is a good idea.
Sorry, I missed this one
Click to expand...
Click to collapse
You can make your own scatter file using a tool like WwR MTK.
Having said that, I'd be very surprised if the scatter file in the software package didn't work for your device, providing your head unit is compatible.

[GUIDE] Android 8 API27 SUPERMOD for YT9216BF YT9216CFJ YT9216BJ YT9216BFJ YT9216CJ - root, Viper4Android, TWRP, Custom UI, brick recovery and more

Hi all,
If you want to greatly improve the way your head unit works, sounds and looks like - you've come to the right place!
Why install this?
With this package you will greatly improve:
Stability
Speed
User Interface
Sound tweaking options
Customisation options
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ON PHYSICAL BUTTONS: this software has only been tested on head units with no physical buttons (like volume) | Before making any changes, access the CAR SETTINGS -> FACTORY SETTINGS -> ENCODER SETTINGS on your head unit and take a screenshot of the current settings (see example below). After installing the package, go back to these settings and adjust them if needed. If that doesn't help and if you can't successfully re-calibrate the buttons after installing the firmware, restore your backup
Disclaimer
I do not create the software itself but rather use research and put together different mods and hacks into one package that includes very user-friendly step-by-step instructions on how to install it all. You will find the links to original posts in the instructions pdf's if credit is due. The software might include smaller changes made by me and has been fully tested in real units.
This firmware works on the following 1Gb RAM and 2 Gb RAM units with fake Android 8.1, 9.0, 9.1, 10 and Android 11 installed, with screen resolution of 1024x600 px. It will not work on Tesla-style units:
- YT9216BF | YT9216CFJ | YT9216BJ | YT9216BFJ | YT9216CJ
!! TAKE A PICTURE OF YOUR SYSTEM INFO AND KERNEL VERSION BEFORE DOING ANYTHING TO YOUR HEAD UNIT !!​
The zip file package contains:
Modified firmware - courtesy of Stranger21UFA @ 4PDA (link to the original post)
TWRP (separate folders for 1GB and 2GB RAM units)
Root via Magisk
Viper4Android
Car Launcher
Boot Animation
SEPARATE INSTRUCTIONS ARE INCLUDED IN EVERY FOLDER
​>>>> ALWAYS BACKUP YOUR UNIT BEFORE MAKING ANY CHANGES TO IT <<<<​​!! IMPORTANT !!​This is a fairly advanced installation process and will require you to follow the individual guides included in the software package - to the letter. Failing to do so, will (in "best" case) result in a slow and buggy head unit and in the worse case - brick it altogether.​
DOWNLOAD
YT9216BF * YT9216CFJ * YT9216BJ * YT9216BFJ * YT9216CJ - supermod software package & drivers
STEP-BY-STEP GUIDE (upgrading from working stock firmware):
DO NOT SKIP ANY STEPS, AND INSTALL EVERYTHING IN THE CORRECT ORDER. STEPS 5 AND 6 ARE MOST CRITICAL.
Proceed to download the software package for your unit and the drivers package in the same folder
It's highly recommended to do these upgrades with your unit connected on your desktop, rather than in the car. Video Guide
Install the Mediatek & ADB drivers on your Windows computer. Video Guide - use the same principle for ADB drivers.
Backup your current system by exporting a full memory dump. Video Guide
Import back your memory dump from step-5 to ensure it fully works. This is how.
Install the package. Separate instructions are included in every folder of the downloaded zip file. Follow them by the order.
IF THIS SOFTWARE PACKAGE HAS BRICKED YOUR HEAD UNIT AND YOU HAVE YOUR BACKUP AVAILABLE, follow the steps below:
DO NOT SKIP ANY STEPS, AND INSTALL EVERYTHING IN THE CORRECT ORDER.
It's highly recommended to do these upgrades with your unit connected on your desktop, rather than in the car. Video Guide
Install the Mediatek & ADB drivers on your Windows computer. Video Guide - use the same principle for ADB drivers - (download link is in the video description)
Watch this video on Test Point recovery
Import back your memory dump. This is how.
If successful - try to install the software package again or stay with your original one
IF THIS SOFTWARE PACKAGE HAS BRICKED YOUR HEAD UNIT AND YOU HAVE NO BACKUP AVAILABLE, follow the steps below:
Share the pictures of your System Info and Kernel in this thread and we'll try to help you
------------------------------------------
This post is being frequently updated and you'll find more guides and mods in our signature​------------------------------------------
** IF YOU ARE UNABLE TO RESTORE YOUR UNIT, PLEASE CONSIDER DONATING IT TO US @ ExtremeMOD, SO WE CAN BUILD MORE MODS AND TUTORIALS​
Thanks! And if this post is helpful to you please don't forget to "like" it.
Enjoy!​
[V4A][VIPER4ANDROID][ViperFX][ROOT][TWRP][8227L][YT9216BF] [YT9216CFJ] [YT9216BJ] [YT9216BFJ] [YT9216CJ]

I flashed this on my YT9216BJ and everything flashed 100%, but when I went to reboot I got nothing. It looks like the unit isn't turning on at all. There is a blue LED on the board that is lit up when I connect power. Any ideas as to what went wrong?

dustindavidson900 said:
I flashed this on my YT9216BJ and everything flashed 100%, but when I went to reboot I got nothing. It looks like the unit isn't turning on at all. There is a blue LED on the board that is lit up when I connect power. Any ideas as to what went wrong?
Click to expand...
Click to collapse
Sorry to hear that. Please try the following steps:
1. Completely disconnect your head unit from power, start Flash Tool as Administrator and execute the command: Format+ALL including deleting the bootloader
2. Run the steps from "Brick Recovery" starting with Step-6.
If the above doesn't work - revert back to your original firmware by restoring your backup. Share your System Info screen found in Car Settings as well as your build.prop file and we'll have a look.
Make sure the USB cable is properly attached. The firmware update should not take more than 20 min. If it does, it indicates a bad cable/connection.

My PC will not detect the head unit at all. I'll try the test point recovery tomorrow and report back.

dustindavidson900 said:
My PC will not detect the head unit at all. I'll try the test point recovery tomorrow and report back.
Click to expand...
Click to collapse
In that case, follow the full brick recovery guide in the OP but use your backup to restore it. Once completed, share the info mentioned in my previous reply.
PS try step 1 in my previous reply. Because the unit is only detected once you push "Download" in Flashtool and then connect the USB cable to your computer. Before that nothing will be shown in your Device Manager. If nothing happens in Flashtool then do test point method.

dustindavidson900 said:
My PC will not detect the head unit at all. I'll try the test point recovery tomorrow and report back.
Click to expand...
Click to collapse
you need test point method now to make that alive again , after shorting them for some 2,3 times,run flash tool ,select scatter and press download, then connect headhunt with a usb a cable...

Why would I need to short them for 3 minutes? Isn't shorting them while I connect the usb enough. That's what the test point instructions say.
Edit: I was able to recover using the Android 6 version of the mod. Could not get the Android 8 mod to work. Thank you for the guide

dustindavidson900 said:
Why would I need to short them for 3 minutes? Isn't shorting them while I connect the usb enough. That's what the test point instructions say.
Edit: I was able to recover using the Android 6 version of the mod. Could not get the Android 8 mod to work. Thank you for the guide
Click to expand...
Click to collapse
Glad to hear it! Android 6 is the recommended option, hands down. I made Android 8 for those that can't successfully rollback to 6.
The unit you see in the pictures in the Android 6 post is a project of mine where rollback caused physical buttons to no longer work and I couldn't remap them either. So had to put together Android 8 package.

vijay_joon said:
you need test point method now to make that alive again , after shorting them for some 2,3 minutes,run flash tool ,select scatter and press download, then connect headhunt with a usb a cable...
Click to expand...
Click to collapse
Please avoid flooding this thread with bad or misleading instructions. Thank you

Hi, can I update my yt9216bj without disconnect it from my car?

matteo2 said:
Hi, can I update my yt9216bj without disconnect it from my car?
Click to expand...
Click to collapse
You absolutely can. However you need to disconnect it from car battery.

dustindavidson900 said:
Why would I need to short them for 3 minutes? Isn't shorting them while I connect the usb enough. That's what the test point instructions say.
Edit: I was able to recover using the Android 6 version of the mod. Could not get the Android 8 mod to work. Thank you for the guide
Click to expand...
Click to collapse
i meant to say 2,3 times , my mistake , i amended, shorting them removes the previous preloader stuff , i may be noob here but this is what worked for me

The method I had to use slightly differs from everything I have read.
1.) I wired a toggle switch to my positive lead. Left it in the off position (no power to head unit)
2.) I connected my radio to my PC (most instructions said do this after)
3.) Pressed the download button in flash_tool.
4.) Shorted the test points and turned on the toggle switch. As soon as I flipped the switch the radio connected and flashed %100.
I actually soldered a button to the test points to make it easier and in case I have to do it again. Took me a minute but then I realized it's just the volume up button and the procedure is essentially the same as putting a phone into download mode.

dustindavidson900 said:
The method I had to use slightly differs from everything I have read.
1.) I wired a toggle switch to my positive lead. Left it in the off position (no power to head unit)
2.) I connected my radio to my PC (most instructions said do this after)
3.) Pressed the download button in flash_tool.
4.) Shorted the test points and turned on the toggle switch. As soon as I flipped the switch the radio connected and flashed %100.
I actually soldered a button to the test points to make it easier and in case I have to do it again. Took me a minute but then I realized it's just the volume up button and the procedure is essentially the same as putting a phone into download mode.
Click to expand...
Click to collapse
Soldering a button switch is indeed by far the best approach. However since the majority of folks here are very new to these types of units, the guide makers here aim to keep it as simple as possible.
You're correct about the buttons and their functionality but since the majority of these devices come without physical buttons, you need to force download mode this way.
Finally, test point method is only required if you mess up your preloader. This should rarely happen. The only times you need to write a new preloader is when changing Android API, i.e upgrading or downgrading. And of course if you modify some of the hardware inside.
The majority of times users accidentally delete the preloader from their units in FlashTool.

I thing i found the picture for the test points but i am a little confuses 2 and three are on the same pad but 1 and 4 are different. Do i short them all together?

ian1mm989 said:
I thing i found the picture for the test points but i am a little confuses 2 and three are on the same pad but 1 and 4 are different. Do i short them all together?
View attachment 5389427
Click to expand...
Click to collapse
Also my board looks a little different.

ian1mm989 said:
Also my board looks a little different.
View attachment 5389429
Click to expand...
Click to collapse
Please read the instructions carefully. The link is in the main post.

I have problem with my Unit (Ebilaen YT9216BF 2GB/32GB).
I installed your firmware, and try reboot to twrp (using command: reboot recovery).
After that my unit doesn't boot (black screen).
After that i want to install TWRP (by SPFlashTools as says Tutorial), but Unit was bricked.
My problem is i didn't make backup firmware.
Right now when i try to unbrick my Unit (using a lot of firmware versions) in SP Flash Tools has error: s_ft_enable_dram_fail (4032) (olso when using TestPoint in motherboard).
I think this error means that i have wrong preloader.bin
Any chance to unbrick Unit without having original firmware?
Information about Unit from motherboard:
B9216BF v0.5/C 32G
A005-B9216BF011(9.0)
20210220
Problem solved. I find correcr preloader.bin

ian1mm989 said:
Also my board looks a little different.
View attachment 5389429
Click to expand...
Click to collapse
Doesn't look that different to me. Here are your 2 test points.

dustindavidson900 said:
The method I had to use slightly differs from everything I have read.
1.) I wired a toggle switch to my positive lead. Left it in the off position (no power to head unit)
Click to expand...
Click to collapse
You could share a picture of your soldered button. Some folks here might find it helpful
I'm thinking of making a guide going for a permanent mod, where the soldered tactile SMD button will be accessible through a small hole in the back of the head unit (similar to how you access the RESET button). That way you can use a 'needle' to short the test points, rather than picking the unit apart every time.

PX6 Android 11 head unit (MTCH MCU firmware) and Peugeot RCZ JBL Amplifier issue

Hi,
I have the same well-known issue that exists with most Android head units and Peugeot JBL amplifiers.
The amplifier only works until volume knob is adjusted, the issue is technically the same as in this video for example:
Of course, "Amplifier" is enabled in factory settings menu.
MY head unit looks the same as in the video but with PX6 and Android 11.
MCU ver: MTCH_MX_V3.81_1
When I ordered this unit, I asked 3 times the distributor if the head unit is complatible with JBL amplifier and he assured about compatibility.
Till then I discussed with the distributor many times but it seems they are lost and I afraid they won't provide any working solution...
Since all ingoing and outgoing CAN communication works otherwise (ie. remote control buttons, car menu controlling, parking radar, car diagnostics reading, VOLUME ADJUSTMENT, etc.) I'm quite sure this issue is realted to firmware not to hardware (CAN decoder). I read some posts on the internet where MCU update solved this issue.
So I'm looking for any suggestions or perhaps a newer MCU file to test with, or any older MCU files to downgrade (if downgrading is possible).
Thank you in advance,
best regards
Adrian
ps.: my car's model code is: 12372UY, Peugeot RCZ 1.6THP with factory JBL amplifier

nhadrian said:
Hi,
I have the same well-known issue that exists with most Android head units and Peugeot JBL amplifiers.
The amplifier only works until volume knob is adjusted, the issue is technically the same as in this video for example:
Of course, "Amplifier" is enabled in factory settings menu.
MY head unit looks the same as in the video but with PX6 and Android 11.
MCU ver: MTCH_MX_V3.81_1
When I ordered this unit, I asked 3 times the distributor if the head unit is complatible with JBL amplifier and he assured about compatibility.
Till then I discussed with the distributor many times but it seems they are lost and I afraid they won't provide any working solution...
Since all ingoing and outgoing CAN communication works otherwise (ie. remote control buttons, car menu controlling, parking radar, car diagnostics reading, VOLUME ADJUSTMENT, etc.) I'm quite sure this issue is realted to firmware not to hardware (CAN decoder). I read some posts on the internet where MCU update solved this issue.
So I'm looking for any suggestions or perhaps a newer MCU file to test with, or any older MCU files to downgrade (if downgrading is possible).
Thank you in advance,
best regards
Adrian
ps.: my car's model code is: 12372UY, Peugeot RCZ 1.6THP with factory JBL amplifier
Click to expand...
Click to collapse
Hi...
Try with CHS based software for your device, it is android 10, do a backup of your software first just in case, then update from USB, test and see if works
SOFTWARE : https://drive.google.com/file/d/1Ta2vL7Fc8tWmzmRxaJ-JMYGmlYYnRmud/view?usp=sharing
If not working, try with EXTRON softwares. Find it on this forum , there is a link for it somewhere in posts.

If issue is not with firmware (if it is the same problem) try leveling audio input (hidden/factory menu/admin menu - asks pin code) to a correct one in menu other or audio or what else is in admin menu.

Anton TNT said:
If issue is not with firmware (if it is the same problem) try leveling audio input (hidden/factory menu/admin menu - asks pin code) to a correct one in menu other or audio or what else is in admin menu.
Click to expand...
Click to collapse
I tried this first but didn't help.

Anton TNT said:
Hi...
Try with CHS based software for your device, it is android 10, do a backup of your software first just in case, then update from USB, test and see if works
SOFTWARE : https://drive.google.com/file/d/1Ta2vL7Fc8tWmzmRxaJ-JMYGmlYYnRmud/view?usp=sharing
If not working, try with EXTRON softwares. Find it on this forum , there is a link for it somewhere in posts.
Click to expand...
Click to collapse
Can you please tell me in a few words what is the easiest way of backing up my compete system fw? I only found how to upgrade, but not a complete system backup. Thank you in advance.

nhadrian said:
Can you please tell me in a few words what is the easiest way of backing up my compete system fw? I only found how to upgrade, but not a complete system backup. Thank you in advance.
Click to expand...
Click to collapse
There is a backup option in admin/hidden menu (pin 8888 or 0000 or what ever it is). Just plug nUSB and transfer all files, including system image (xxxx.img etc.).
If not there I do not no where it is. Every device is different. If not found, prior to update, ask seller to give you original software if need to install again. (NOTE: softwqare is as is, and seller or other like myself that are giving you this update are not responsible for any misconduct or defected softwares after updates, so watch what you are doing)

Thank you for your kind reply. I made a short video about the model and build details as well as the Factory menu. Unfortunatelly there aren't any backup option. I was asking the supplier for the factory firmware, I hope they'll send it to have a backup.
Otherwise it looks like this is a PX6 "A-Media Auto" head unit. Does the fw you sent just fit for this taking into account the details in my video?

Refer MTCD forums, unit is a MTCD variant.
You will also find Yandisk based MCU and Android firmware. Stay with same MCU type (MX).

marchnz said:
Refer MTCD forums, unit is a MTCD variant.
You will also find Yandisk based MCU and Android firmware. Stay with same MCU type (MX).
Click to expand...
Click to collapse
Thank you for the information. Do you know what is the safest way of downgrading to A10? Most of the firmwares are A10 or earlier, and it is noted that only for up to A10.

nhadrian said:
Thank you for your kind reply. I made a short video about the model and build details as well as the Factory menu. Unfortunatelly there aren't any backup option. I was asking the supplier for the factory firmware, I hope they'll send it to have a backup.
Otherwise it looks like this is a PX6 "A-Media Auto" head unit. Does the fw you sent just fit for this taking into account the details in my video?
Click to expand...
Click to collapse
What kind of Peugeot is it ? What model ?
If 301-308 version use different PSA canbus settings untill all commands and apps work.
Will look for my psa settings f canbus and took picture of it.

Anton TNT said:
What kind of Peugeot is it ? What model ?
If 301-308 version use different PSA canbus settings untill all commands and apps work.
Will look for my psa settings f canbus and took picture of it.
Click to expand...
Click to collapse
It is a 2010 Peugeot RCZ with factory JBL amp.
My current canbus adapter is a Simple Soft PSA one (PA-SS-05) and canbus setting is Nr.61 - as shown on the video. I have everything working like reverse radar, steering wheel remote buttons, A/C feedback, etc. The only thing is the JBL that do not remain on.

UPDATE: I got an update.zip from the seller. It was a downgrade to Android 10. After installing the update, device stuck at boot logo (peugeot animation). Sometimes reset itself, like in 10 minutes or so. Can it be recovered somehow?

nhadrian said:
UPDATE: I got an update.zip from the seller. It was a downgrade to Android 10. After installing the update, device stuck at boot logo (peugeot animation). Sometimes reset itself, like in 10 minutes or so. Can it be recovered somehow?
Click to expand...
Click to collapse
You must update again a let it finish update till inside android system, then remove usb or sdcard wich contains image for system and reboot with pin code, enter 4 or justbtake off ignirion key. As soon as gets inside android system, purge memory from factory menu, with pin 8888 or what is yours to get in. Go to setting for memory if you have it and it must not write to any sd card or usb attached in system. As soon system is recognozed it will take settings from internal memory not from usb or cards.

Hi, did you manage to update successfuly?

Anton TNT said:
Hi, did you manage to update successfuly?
Click to expand...
Click to collapse
Unfortunatelly not. Still waiting for the seller to provide me a firmware in img. Or a flash tool.
I can't install the update.zip by RKTools, not recognized file format.
But at least I know how to enter recovery mode and drivers are installed on my PC, RKTools recognize it.
I tried to flash the firmware you posted here earlier but the tool quitsas soon as I try to load it.

nhadrian said:
Unfortunatelly not. Still waiting for the seller to provide me a firmware in img. Or a flash tool.
I can't install the update.zip by RKTools, not recognized file format.
But at least I know how to enter recovery mode and drivers are installed on my PC, RKTools recognize it.
I tried to flash the firmware you posted here earlier but the tool quitsas soon as I try to load it.
Click to expand...
Click to collapse
Your device is an MTCD variant. Refer mtcd forums and my recovery threads. If SDCARD recovery does not work, use OTG recovery per my posts

Here is the OTA update.zip I got from that idiot chinese seller:
1.01 GB file on MEGA
mega.nz
He said it is a complete firmware, this is the folder content (zip is 1 Gig):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can anybody help me converting to an .img for OTG flashing, or an SD-card image (which I can write to an SD-card with balena etcher)? I'd be really thankful (donate on paypal if succeed), I'd still remain on "official" firmware for my device, for a possible warrantee dispute...
Thank you guys in advance!!!

I still don't know how to install any firmwares in .zip container (either my factory one, hal9k or malysik).
My device has black screen during recovery boot, so the only chance is using the rockchip tools or SD card method. I was trying to find topics on how to convert the .zip package to img but can't find any information.
Please someone help!

nhadrian said:
I still don't know how to install any firmwares in .zip container (either my factory one, hal9k or malysik).
My device has black screen during recovery boot, so the only chance is using the rockchip tools or SD card method. I was trying to find topics on how to convert the .zip package to img but can't find any information.
Please someone help!
Click to expand...
Click to collapse
Use .zip file in usb, if not readable prior to startup of unit, press and hold Reset button - a litlle hole on device - and keep holding while usb with update is in port. Release reset button and system will boot up and read usb files and update device. If not read, unzip files inside .zip and place them in usb , just two files .img and .upd and try again same procedure with reset button.

Anton TNT said:
Use .zip file in usb, if not readable prior to startup of unit, press and hold Reset button - a litlle hole on device - and keep holding while usb with update is in port. Release reset button and system will boot up and read usb files and update device. If not read, unzip files inside .zip and place them in usb , just two files .img and .upd and try again same procedure with reset button.
Click to expand...
Click to collapse
Neither of this method works. Every time it boots into the main system (and the infinite Peugeot logo).