Related
Hello all, I have just signed up because this seems to be a good place for me to ask questions. I purchased an Eincar Octo-core, 32GB ROM, 2GB RAM running Android 7.1.2. I know very little about Android Headunit but require some help if anyone is able to.
For some reason it won't recognise .MP4 files so I am unable to watch any films in this format. It plays AVI, MKV and other file formats without any problems.
The internal mic is terrible so I purchased an external mic from Wish, which is a big improvement.
I read somewhere that the unit can be flashed with something like Pumpkin/Joying firmware which will allow me to root but not sure how or if it's definitely possible? I would like to install apps like Viper4Android but need root access. I've tried KingoRoot and it fails every time.
MCU version: 5.3.19-7-20-656201-170225
System version: V9.2.2_20171226.101304_TW2
Processor: UltraOcta-T8
Hi,
Like you might have seen in "my" other thread "[Review] Joying PX5 2GB+32GB on Android version 8.0.0", I worked on rooting the Joying Android version 8.0.0 PX5-A53 Rockchip units. (Do not confuse this with rooting the Sofia 3GR Intel units)
I have now released my scripts for Linux/Unix like and for Windows. You can find these scripts on my github releases section.
It comes with an instruction. Read it carefully and if unclear let me know.
I also updated the rooting page of my website.
My signature under my posts also reflects the "new status".
Note that the current rooting method uses the "setenforce 0" method to root your unit. That is deprecated since Android 4.2 as it is less safe. Until now I (and many others) did not find a way to root our Chinese head units in the "safe way" (using setenforce 1). I will do my best to get the safe method working on our units (some day)!
Note: I do have a FYT unit, but the scripts should actually work on any PX5 Android 8.0.0 unit. The scripts "might" work on PX5 Android version 6.0.1 units, but you better use the official rooting methods in those cases. (Besides: Android 6.0.1 on the PX5 units is a "dead end").
========
I'm also working on Xposed on the PX5. The first attempts resulted in a not working Xposed. Upon uninstall I boot-looped my unit needing a fresh flash. At least I could test my root script one more time . I will continue on that.
I'm also working hard on my JET apk: A complete rewrite (multiple screens, tab based approach) and making it suitable for the PX5 as well. Some images are already showing up on my website
reserved
Hey Surfer,
When I run the Extra Tools app it tells me my unit is not a sofia or px5 unit. What information does it check?
If this helps any:
CPU: ARM Cortex-A53 eight-core 2+32 GB PX5; CPU: PowerVR G6110
Build: PX5-userdebug 8.0.0 OPR5.170623.007 eng.bsp.20180605.100502 test-keys
MCU: 2018-04-16 17:04:06 ZHAN_(NOR)__90_C9RD6686_CAN(A)PX5D1804160
System: APP2018-06-05 03:04:18
--Tully
Tried this script on Joying 2GB 32GB Android 6.01 unit. ADBoverwifi enabled. Script cannot connect to unit. Laptop and HU on same 2.4GHz network. After reboot no Superuser app apears appearantly. Joying Extra apps still says semi-rooted then. Too bad Joying has no 8.0 rom for this unit for now
Code:
C:\Users\Deniz\Desktop\SuperSU-PX5-ARM\SuperSU-PX5-ARM>copy_install.bat 192.168.8.104
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
unable to connect to 192.168.8.104:5555
error: device '(null)' not found
unable to connect to 192.168.8.104:5555
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
Reboot your Head Unit NOW!
C:\Users\Deniz\Desktop\SuperSU-PX5-ARM\SuperSU-PX5-ARM>
walkin123 said:
Hey Surfer,
When I run the Extra Tools app it tells me my unit is not a sofia or px5 unit. What information does it check?
If this helps any:
CPU: ARM Cortex-A53 eight-core 2+32 GB PX5; CPU: PowerVR G6110
Build: PX5-userdebug 8.0.0 OPR5.170623.007 eng.bsp.20180605.100502 test-keys
MCU: 2018-04-16 17:04:06 ZHAN_(NOR)__90_C9RD6686_CAN(A)PX5D1804160
Click to expand...
Click to collapse
That version 50 was theoretically configured for PX5 as at that time I did not have a PX5 yet. I based it on the way how the Sofias were configured. The check is now correct in the version I'm working on.
It still contains some bugs due to the massive rewrite and the new PX5 parts. You have to wait till that one is ready.
Just let me know and Ill happily test it for you.
steef84 said:
Tried this script on Joying 2GB 32GB Android 6.01 unit. ADBoverwifi enabled. Script cannot connect to unit. Laptop and HU on same 2.4GHz network. After reboot no Superuser app apears appearantly. Joying Extra apps still says semi-rooted then. Too bad Joying has no 8.0 rom for this unit for now
Code:
C:\Users\Deniz\Desktop\SuperSU-PX5-ARM\SuperSU-PX5-ARM>copy_install.bat 192.168.8.104
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
unable to connect to 192.168.8.104:5555
error: device '(null)' not found
unable to connect to 192.168.8.104:5555
error: device '(null)' not found
<... snip ...>
error: device '(null)' not found
Reboot your Head Unit NOW!
C:\Users\Deniz\Desktop\SuperSU-PX5-ARM\SuperSU-PX5-ARM>
Click to expand...
Click to collapse
Did you reboot your unit in advance?
And how often did you try? Sometimes you need multiple tries.
And how did you enable the adb over tcpip? Do you have a terminal app? If so could you give the command "getprop persist.adb.tcp.port". It should return 5555.
Furthermore: I am already in discussion with Joying as I think the PX5 wifi is not good.
As I was not certain whether it was my unit only or also on other units, I did not extensively communicate about it in this forum. I think quality control is not so good at Joying. Both users of Sofias and PX5s are complaining about terrible WiFi reception. The WiFi antenna needs to be soldered onto the board and I think the "assembling teams" have good and bad solderers.
Anyway: It only works for me when I take my phone and laptop into the car and use my phones hotspot. Downloading of apps over my home WiFi does work, but is extremely slow, much slower than my previous Sofia.
(Installation of apps from the Play Store is much faster though than on the Sofia).
walkin123 said:
Just let me know and Ill happily test it for you.
Click to expand...
Click to collapse
Give me a couple of more days. Almost there, but I have again a busy week in front of me.
Sorry to say, but at this time it takes perhaps more time to react on test reports than it takes me to test myself.
steef84 said:
Tried this script on Joying 2GB 32GB Android 6.01 unit. ADBoverwifi enabled. Script cannot connect to unit. Laptop and HU on same 2.4GHz network. After reboot no Superuser app apears appearantly. Joying Extra apps still says semi-rooted then. Too bad Joying has no 8.0 rom for this unit for now
Code:
C:\Users\Deniz\Desktop\SuperSU-PX5-ARM\SuperSU-PX5-ARM>copy_install.bat 192.168.8.104
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
unable to connect to 192.168.8.104:5555
error: device '(null)' not found
unable to connect to 192.168.8.104:5555
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
error: device '(null)' not found
Reboot your Head Unit NOW!
C:\Users\Deniz\Desktop\SuperSU-PX5-ARM\SuperSU-PX5-ARM>
Click to expand...
Click to collapse
I tried this on my PX5 4x32 Oreo. The unit rooted just fine, then I was notified to update the SU Binary, so I did. Now I'm stuck on the Android Boot screen. Tried resetting 3 times, no joy. I tried re-running the root script and I get the exact same as above, it's not completing the boot to where adb will work.
Please Help! I have a very long trip on Wednesday, would be nice to have a stereo and maps...
wanb1i said:
I tried this on my PX5 4x32 Oreo. The unit rooted just fine, then I was notified to update the SU Binary, so I did. Now I'm stuck on the Android Boot screen. Tried resetting 3 times, no joy. I tried re-running the root script and I get the exact same as above, it's not completing the boot to where adb will work.
Please Help! I have a very long trip on Wednesday, would be nice to have a stereo and maps...
Click to expand...
Click to collapse
Sorry. That is something I do have to add. Do NOT try to update the su binary. It was the same in all previous methods so I really forgot to mention that now. The only thing you can currently do is reflash the unit with a fresh firmware. I will immediately update the pages and the instruction.
surfer63 said:
Sorry. That is something I do have to add. Do NOT try to update the su binary. It was the same in all previous methods so I really forgot to mention that now. The only thing you can currently do is reflash the unit with a fresh firmware. I will immediately update the pages and the instruction.
Click to expand...
Click to collapse
Ok, I'm downloading the 6/5/18 firmware. I really didn't want to upgrade this unit because everything was working with the stock FW it came with. oh well, the joys of modding android!
I'm going to wait until you have this done before I mess with it again.
Do I have to update the OEM & MCU as well? Never done that before SCARY!!
UPDATE:
I have it working again, now I need to set it back up.
PX5 Android Version 8.0.0 incompatible
Believe a user above expressed a similar issue where apk gives an incorrect analysis of system saying "This is NOT a Joying Sofia 3GR Intel-" which is true "-or a Joying PX5 unit!". Either they sent me the wrong unit (joking, I got the right unit) or the apk needs a little bit of tweaking
I'd just like to know when your newer script arrives as your last release was over two months ago. I just want to remove Launcher3 since Joying firmware apparently doesn't allow a persistent default launcher; it changes back to Launcher3.
Have a JY-UO135N4
Orphlo said:
Believe a user above expressed a similar issue where apk gives an incorrect analysis of system saying "This is NOT a Joying Sofia 3GR Intel-" which is true "-or a Joying PX5 unit!". Either they sent me the wrong unit (joking, I got the right unit) or the apk needs a little bit of tweaking
I'd just like to know when your newer script arrives as your last release was over two months ago. I just want to remove Launcher3 since Joying firmware apparently doesn't allow a persistent default launcher; it changes back to Launcher3.
Click to expand...
Click to collapse
There are great running apps more than 2 years old . It doesn't mean a project is dead. Besides: I have a very interesting, busy life outside Joying.
Switching a launcher has nothing to do with my JET apk. If you want to switch the launcher you should do that from the Settings from the Apps part, where you define the standard apps. It is mentioned as "boot screen" app or something like that.
So not the Joying launcher changer as that only gives you the option for the Joying launchers.
Re:
surfer63 said:
There are great running apps more than 2 years old . It doesn't mean a project is dead. Besides: I have a very interesting, busy life outside Joying.
Switching a launcher has nothing to do with my JET apk. If you want to switch the launcher you should do that from the Settings from the Apps part, where you define the standard apps. It is mentioned as "boot screen" app or something like that.
So not the Joying launcher changer as that only gives you the option for the Joying launchers.
Click to expand...
Click to collapse
Yup good to hear, and I'd certainly hope there wasn't someone who lived their life in a car. Anyway, yes what you're talking about is the 'Default Apps' section in settings. Normally the default home launcher option will allow you to change the default launcher, however the Joying unit will reset your choice each time it is rebooted. I don't know why it is, and the limited ability of Joying's "Launcher3" home screen is unfortunate, so it seems the only way to fix this is to remove Launcher3 completely and disable it which can only be done with root access, something I can't seem to get.
So ultimately It'd be great to see an update so I can get it done through your method, otherwise if there are any other methods feel free to let me know :good:
Orphlo said:
Yup good to hear, and I'd certainly hope there wasn't someone who lived their life in a car. Anyway, yes what you're talking about is the 'Default Apps' section in settings. Normally the default home launcher option will allow you to change the default launcher, however the Joying unit will reset your choice each time it is rebooted. I don't know why it is, and the limited ability of Joying's "Launcher3" home screen is unfortunate, so it seems the only way to fix this is to remove Launcher3 completely and disable it which can only be done with root access, something I can't seem to get.
So ultimately It'd be great to see an update so I can get it done through your method, otherwise if there are any other methods feel free to let me know :good:
Click to expand...
Click to collapse
I said "you should do that from the Settings from the Apps part", NOT from Joyings launcher settings.
Re:
surfer63 said:
I said "you should do that from the Settings from the Apps part", NOT from Joyings launcher settings.
Click to expand...
Click to collapse
No I got what you said, it's just that the Launcher app actually redirects you there. The Launcher app I'm using is Nova, and in Nova settings the option to set as default home app opens up settings to that location
I was able to root my Joying JY-UOS01P4 unit (32GB+4GB PX5) OREO (NOT MTCD/E!) by modding some files and running your root package. I did the following manually because im not able to inject the mod to the main file yet:
1. downloaded the latest firmware update from joying website
2. extracted its contents and i put "service.adb.tcp.port=5555" on last line of the config.txt file
3. flashed this slightly modified firmware
4. Installed ADB over WIFI enabler "AoW_v1.1.apk" ( https://forum.xda-developers.com/showpost.php?p=71616884&postcount=273 ) and made it happen
5. Connected to the router and followed your instructions. ROOTED !
Altough i was not able to use your great Joying Tools app (says my unit is not a Joying product) and was not able to use Viper4Android. By using root explorers seems some folders and files are write-protected even with root rights acquired by your method.
Thanks for your job !
Horus
horuscurcino said:
I was able to root my Joying JY-UOS01P4 unit (32GB+4GB PX5) OREO (NOT MTCD/E!) by modding some files and running your root package. I did the following manually because im not able to inject the mod to the main file yet:
Altough i was not able to use your great Joying Tools app (says my unit is not a Joying product) and was not able to use Viper4Android. By using root explorers seems some folders and files are write-protected even with root rights acquired by your method.
Click to expand...
Click to collapse
Nice your rooted it. JET version 50 was a "theoretical" approach to the PX5. The to be released version 51 will support the PX5.
surfer63 said:
Nice your rooted it. JET version 50 was a "theoretical" approach to the PX5. The to be released version 51 will support the PX5.
Click to expand...
Click to collapse
Great. I will wait for this release!
Thank you, Horus
surfer63 said:
Nice your rooted it. JET version 50 was a "theoretical" approach to the PX5. The to be released version 51 will support the PX5.
Click to expand...
Click to collapse
I downloaded JET 51, and was able to root fairly easily. My only hiccups running the scripts were because I was using a work laptop that seems to stop once in a while, which caused timeouts on adb But I re ran the scripts a few times and was ultimately successful.
Edit: I also had a few issues because the Joying WiFi MAC address changed. This used up all of the DHCP Leases/ IP Addresses from my hotspot, so I had to restart the hotspot after a few reboots.
I bought one of these Chinese Android boxes that integrate with your existing head unit and I'm trying to find any information about it, and which forum I should be posting questions to. FWIW I have a VW Touareg with an RNS850 system that is basically the same thing as the Audi MMI 3g+ system, but with a touch screen.
Here is some model and version info:
Model: ZQ8002
MCU: TUREG-ZQAND-1.1
APP: MTK-8002_C37_GA1_DZSJ_DaZhong_EN_2019-05-27
Android: 6.0
CPU: 4 core 32-bit CPU Coetex-A7 @1.3G
RAM: 2GB
Flash: 16GB
Baseband Version: MOLY.WR8.W1449.MD.WG.MP.V61.P3
Kernel: 3.18.19 [email protected] #2
Hostname: fise8321_tb_m (seen via ADB shell)
It has a "Factory Settings" menu similar to other Android head units I've seen mentioned here. That presents a numeric keypad. I figured out a few codes for it:
0000: Bunch of debugging toggles, also toggle for ZLink CarPlay
5555: Just says "ok" when you enter it. I think this turns on ADB over TCP. I was able to ADB to it after this, but I had also use a terminal emulator to enable it.
9999: Single item to allow installation of "APP", which I assume is the firmware?
The box on Amazon: https://www.amazon.com/gp/product/B07PJGLD41/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
Main issues I'm trying to solve right now is that my skip track buttons on my steering wheel aren't doing anything, even though I can see the CAN bus events in the logs when I press the buttons. I'm hoping there's a Factory Setting code I haven't found that might let me change the CAN Bus settings. It has carCanBus and FactorySettings apks that I was able to decompile, but didn't find anything useful.
mondo1287 said:
I bought one of these Chinese Android boxes that integrate with your existing head unit and I'm trying to find any information about it, and which forum I should be posting questions to. FWIW I have a VW Touareg with an RNS850 system that is basically the same thing as the Audi MMI 3g+ system, but with a touch screen.
Here is some model and version info:
Model: ZQ8002
MCU: TUREG-ZQAND-1.1
APP: MTK-8002_C37_GA1_DZSJ_DaZhong_EN_2019-05-27
Android: 6.0
CPU: 4 core 32-bit CPU Coetex-A7 @1.3G
RAM: 2GB
Flash: 16GB
Baseband Version: MOLY.WR8.W1449.MD.WG.MP.V61.P3
Kernel: 3.18.19 [email protected] #2
Hostname: fise8321_tb_m (seen via ADB shell)
It has a "Factory Settings" menu similar to other Android head units I've seen mentioned here. That presents a numeric keypad. I figured out a few codes for it:
0000: Bunch of debugging toggles, also toggle for ZLink CarPlay
5555: Just says "ok" when you enter it. I think this turns on ADB over TCP. I was able to ADB to it after this, but I had also use a terminal emulator to enable it.
9999: Single item to allow installation of "APP", which I assume is the firmware?
The box on Amazon: https://www.amazon.com/gp/product/B07PJGLD41/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
Main issues I'm trying to solve right now is that my skip track buttons on my steering wheel aren't doing anything, even though I can see the CAN bus events in the logs when I press the buttons. I'm hoping there's a Factory Setting code I haven't found that might let me change the CAN Bus settings. It has carCanBus and FactorySettings apks that I was able to decompile, but didn't find anything useful.
Click to expand...
Click to collapse
Hi Mondo! How are you?, I've updated my interface like ypurs with a wrong MCU. Could you send my your? I need the file MCU TUREG-ZQAND-1.1. Thanks a lot. My email is [email protected]
Albe Vala said:
Hi Mondo! How are you?, I've updated my interface like ypurs with a wrong MCU. Could you send my your? I need the file MCU TUREG-ZQAND-1.1. Thanks a lot. My email is [email protected]
Click to expand...
Click to collapse
Hi Albe, is this something I could copy off of the unit? I have not had mine installed for a couple of years, but I am interested in trying to get this thing updated to possibly fix some of the issues I had with it. It may be a long time before I work on it, but if you could provide the file system path to copy the MCU file, I will provide it for you. If it's more involved than just copying a file, just let me know what I need to do or link me to a guide. Thanks!
mondo1287 said:
Hi Albe, is this something I could copy off of the unit? I have not had mine installed for a couple of years, but I am interested in trying to get this thing updated to possibly fix some of the issues I had with it. It may be a long time before I work on it, but if you could provide the file system path to copy the MCU file, I will provide it for you. If it's more involved than just copying a file, just let me know what I need to do or link me to a guide. Thanks!
Click to expand...
Click to collapse
I don't know how is it possible to exctract the MCU file (.bin) by the interface. I could try to find online anything to do it. i try to find softwars and so on, if i'will try i tell you something. I send many mails to producer of the unit, but everytime i do it, he tell me to waiting for response of the engineering department......and i wait. My MCU was TUREG-ZQAND-1.3 but i think your version 1.1 coluld going rigt for mine.
Not (android-auto) requested moderator move to Android head units forum.
mondo1287 said:
Hi Albe, is this something I could copy off of the unit? I have not had mine installed for a couple of years, but I am interested in trying to get this thing updated to possibly fix some of the issues I had with it. It may be a long time before I work on it, but if you could provide the file system path to copy the MCU file, I will provide it for you. If it's more involved than just copying a file, just let me know what I need to do or link me to a guide. Thanks!
Click to expand...
Click to collapse
Hi Mondo. I've find how could you extract the MCU file from your ZQ android interface. read the thread that i link you now! I wiat for your reply. https://www.androidiani.com/forum/autoradio-android/546699-f-q-px5-autoradio-android.html. At the end of Point "2" you can read how to export your mcu file! Thanks a lot and best regards.
https://m.youtube.com/watch?v=FLe7yx3XJP8https://m.youtube.com/watch?v=FLe7yx3XJP8
click video link and comment. im not a developer i just listened to the amazon sellers directions and then searched 8227l in google and found a bunch of files, then tested them and now i want to pass the info on.
tp the guys asking if itll work?
i dont know you gotta test it like i did. they worked on my unit. and the files i donloaded came from other style stereos with android.
i just generally think they are all same firmware if it look similar to actual stereo design and ui .
This is what I have.
Android : YT9216b_00002_V004_20190728
8227L
MCU 3.1
MODEL NUMBER 8227L_DEMO
Can i install the 9.0? Is is real 9.0 or fake?( you know right now it has 6.0 but says it is 8.1GO)
its the fake 8.1 like always but it works so cant complain.
ighostsgunnaz said:
its the fake 8.1 like always but it works so cant complain.
Click to expand...
Click to collapse
Is this the 8.1go or just 8.1?
Also the android 9.0 has multi screen working?
Can i safely flash my head unit with the firmware listed?
Yes u can ( always do at your own risk like me); but use one of the touch only files. I can't upload pictures yet but i tried to post a screenshot of each firmware look. If its 8227l firmware it should update/flash.
ighostsgunnaz said:
Yes u can ( always do at your own risk like me); but use one of the touch only files. I can't upload pictures yet but i tried to post a screenshot of each firmware look. If its 8227l firmware it should update/flash.
Click to expand...
Click to collapse
Ok i may try to flash it this few days. Btw the 8.1 is the go ver or just 8.1? What is your recommendation to install 8.1go or 9.0 which is smoother and better?
slayer369 said:
Ok i may try to flash it this few days. Btw the 8.1 is the go ver or just 8.1? What is your recommendation to install 8.1go or 9.0 which is smoother and better?
Click to expand...
Click to collapse
They both looked very smooth even when running on my stereo. And i have a touch & button stereo it worked flawlessly no lag no glitch.
Only error was for the firmware being for touch screen only
Hello, I would like to know if this type of software has in some menu the option of autosleep to program that it turns off completely and does not remain in standby, in other Android it exists but here I do not see it. Can this Android 9.0 image be flashed even if it now has 8.1? Is it official or is it rooted?
thanks
i have the following head unit in the link attached will android 9 rom support this head unit ? It has touch button such as back,home,volume up/down.
and how does UI2 look like?
https://drive.google.com/open?id=0B-DeZ2cJS-h6UFVKSkswdExXX2NMNnc2akoydS1jcVQxd1hN
Hi guys! I ask for your help, a few days ago I bought an android radio unit on aliexpress, specifically the Junsun brand, with these characteristics:
Model: 8227L
Android version: 8.1.0
Kernel version: 3.18.79 (gcc version 6.3.1 20170404 (Linaro GCC 6.3.2017.05) [email protected] #57
Comp. Number: alps.mp.o1.mp5
2GB Ram
32Gb Rom
7 inch
With Canbus (ford mondeo 2007)
Its my first time with an android radio unit and I am very lost, I would like to know if I can change the firmware or update it, the one that it brings is very limited and does not let me change the brightness of the device or bluetooth functions.
Thank you for support!
Hi guys!
Is it suitable for me?
'Android 9'
ac960e2134.jpeg[/IMG]
I tryed to update using 8.1 archives, the unit detect the USB files, ask for update with a countdown, but when autorestart and start to update, the unit say fail, check USB and files...
Any solution?
i have 8227L with DSP will it work with this
ighostsgunnaz said:
Above are 2 android 7.1 & 8.1 example. Below is Android 9 example.
This is for those who have a ( 8227l ) android stereo and are looking for the update file zip. Also the mcu in the about phone menu should begin with ts . I have 5 files from jby tech, they are the Amazon seller of my hizpo android 8.1 stereo unit. From lots of research and emails to the company, i found that these Android stereos come in many brand names but run the same 8227l system. Another company with the same unit is joying but the device name is different along with the entire UI. Please do be sure you have a 8227l unit before proceeding. Other updates for other brands can be found on google and xda forum. I will try to remember to put link for xda forum. Below I have listed 2 groups of files. One is for touch screen only android stereo and the other is for touch screen with volume knob. Please choose according to your type of stereo. And follow the steps below exactly.
1. Download proper zip for your device.
2. Extract the 2 files from within the zip folder.
3. Copy & paste the ( .bin ) & other file on to a blank sd card or usb flash drive. Make sure these are the only 2 files on the sd card or flash drive.
4. With stereo unit powered off insert the sd card or usb flash drive and power on stereo. (Note some units will recognize the file immediately during boot, and others will prompt you after loading main screen. If unit does not recognize it, power off for 40sec and when u power on tap the screen in middle repeatedly with finger until the word "detected" shows in green. If it gives a message in red saying failed please check you have good download copy and have followed the instructions exactly. Will answer questions as i am able to.
All links to files and sites mentioned must be copy pasted. Im not able to attach external link yet.
The files below this line are for android6os,7os,8.1os 8227l units with a volume knob
Stock Android 7.1 firmware:
drive.google.com/folderview?id=1_D0IOyzUDNwo83Y4cVv054HPmaYs2JO7
Stock android 8.1 firmware:
drive.google.com/folderview?id=1LJ-FVgn73hxqJ-x7-pSJZuJDkfEV-c-7
Here is another version for this unit that is stock Android 6,7os but felt like it had a low resolution not for certain, but is safe to install in case base version still isnt a match for your unit:
Android7.1 V63
7drive.google.com/file/d/14UTC12nlWutwEqfsfux8spPY6qApw8Nt/view?usp=drivesdk
Android 7.1 v67
drive.google.com/file/d/1QQkQnxYZuO8rZ19KqVKPtVRIIE81sJ5b/view?usp=drivesdk
____________________________________
The files below are for the "TOUCH" only Android 9os 8227l units with touch back, home, vol -/+ buttons.
*** I have installed them on the non-touch unit and it will work but not allow volume knob to work, and will display " Activation code does not match " ***
Stock android 9 touch firmware version 1:
drive.google.com/file/d/19Yn_v6hXMJBObvgS7eqPN2nVgHhoisyX/view?usp=drivesdk
Stock android 9 touch firmware version 2:
drive.google.com/file/d/14gSJXCNqYPpUkgg7M_sd3jim6JvF1R3M/view?usp=drivesdk
Click to expand...
Click to collapse
I have a 8277L with Dsp, will it work with this one.
Hy guys,
I have this android radio with fake android 9.1
Android: YT9216C_AHD_00005_V004_20191017_HIFI
System: Android 9.1 XY AUTO:3.1 (8227L)
CAN pro: 3.0 (8227L)
DDR: 2G FLASH:32G
CPU: A7 1.3 GHz x4
MCU1: 3.1
Kernel Version: [email protected]#5
Build number: android-trunk-m0.AC8227L-V1.0
The unit have hardware buttons for volume up and down.
Can i install android 9 touch or android 8.1 ?
Thanks for the reply and sorry for my bad english.
rohan_agashe said:
I have a 8277L with Dsp, will it work with this one.
Click to expand...
Click to collapse
I have it too... Are there Any New firmware? I changed launcher to agama and each time i start the unit, usb doesnt detect it.
The 8.1 versión is horrible
code
ighostsgunnaz said:
Above are 2 android 7.1 & 8.1 example. Below is Android 9 example.
This is for those who have a ( 8227l ) android stereo and are looking for the update file zip. Also the mcu in the about phone menu should begin with ts . I have 5 files from jby tech, they are the Amazon seller of my hizpo android 8.1 stereo unit. From lots of research and emails to the company, i found that these Android stereos come in many brand names but run the same 8227l system. Another company with the same unit is joying but the device name is different along with the entire UI. Please do be sure you have a 8227l unit before proceeding. Other updates for other brands can be found on google and xda forum. I will try to remember to put link for xda forum. Below I have listed 2 groups of files. One is for touch screen only android stereo and the other is for touch screen with volume knob. Please choose according to your type of stereo. And follow the steps below exactly.
1. Download proper zip for your device.
2. Extract the 2 files from within the zip folder.
3. Copy & paste the ( .bin ) & other file on to a blank sd card or usb flash drive. Make sure these are the only 2 files on the sd card or flash drive.
4. With stereo unit powered off insert the sd card or usb flash drive and power on stereo. (Note some units will recognize the file immediately during boot, and others will prompt you after loading main screen. If unit does not recognize it, power off for 40sec and when u power on tap the screen in middle repeatedly with finger until the word "detected" shows in green. If it gives a message in red saying failed please check you have good download copy and have followed the instructions exactly. Will answer questions as i am able to.
All links to files and sites mentioned must be copy pasted. Im not able to attach external link yet.
The files below this line are for android6os,7os,8.1os 8227l units with a volume knob
Stock Android 7.1 firmware:
drive.google.com/folderview?id=1_D0IOyzUDNwo83Y4cVv054HPmaYs2JO7
Stock android 8.1 firmware:
drive.google.com/folderview?id=1LJ-FVgn73hxqJ-x7-pSJZuJDkfEV-c-7
Here is another version for this unit that is stock Android 6,7os but felt like it had a low resolution not for certain, but is safe to install in case base version still isnt a match for your unit:
Android7.1 V63
7drive.google.com/file/d/14UTC12nlWutwEqfsfux8spPY6qApw8Nt/view?usp=drivesdk
Android 7.1 v67
drive.google.com/file/d/1QQkQnxYZuO8rZ19KqVKPtVRIIE81sJ5b/view?usp=drivesdk
____________________________________
The files below are for the "TOUCH" only Android 9os 8227l units with touch back, home, vol -/+ buttons.
*** I have installed them on the non-touch unit and it will work but not allow volume knob to work, and will display " Activation code does not match " ***
Stock android 9 touch firmware version 1:
drive.google.com/file/d/19Yn_v6hXMJBObvgS7eqPN2nVgHhoisyX/view?usp=drivesdk
Stock android 9 touch firmware version 2:
drive.google.com/file/d/14gSJXCNqYPpUkgg7M_sd3jim6JvF1R3M/view?usp=drivesdk
Click to expand...
Click to collapse
When I give the code 12345678 in the menu, I come in a separate menu in Chinese on my ac8227L Someone confesses to this.
how to upgrad my drive to android 9
noomkhup said:
how to upgrad my drive to android 9
Click to expand...
Click to collapse
I cant choose Android upgrade too, like the previous post shows: it is grayed out...
Soldiaz said:
I cant choose Android upgrade too, like the previous post shows: it is grayed out...
Click to expand...
Click to collapse
i think sell this device and buy new device android9 hahaha
Sorry My English is stupid - -"
i think i have the same unit as yours.how was your after flash result?
slayer369 said:
Ok i may try to flash it this few days. Btw the 8.1 is the go ver or just 8.1? What is your recommendation to install 8.1go or 9.0 which is smoother and better?
Click to expand...
Click to collapse
Hi guys, I'd love to know why my Radio app for this head unit can no longer open. I tried force stopping the app, I tried hard reset via factory settings, I tried pulling it out and putting it back in for a power reset (doesn't seem to do anything), tried cleaning cache and data, tried clean up apps, but the stock radio app just keeps saying "Could not open Radio"
I've looked for other fm radio app APKs to install with no luck, they are either incompatible or just streaming online radio apps which doesn't help, nor can I find the replacement radio apk in order to uninstall and reinstall to see if that helps solve the problem.
Anyone else run into this issue? Can I somehow pull the APK of the existing radio app to save, and then uninstall and reinstall it? Any and all help is appreciated - googling is not providing me with anything for this unit thus far which means I'm stuck with a very decent deck for the price, that no longer has a functioning radio (which was working great before it suddenly stopped opening after I was showing off and literally saying how great the radio works!).
Head unit details, for reference, are:
Android: YT9213AJ_00011_V001_20200613
Android OS: Android 9.1 XY AUTO: 3.4 (8227L)
CAN Pro: 3.1 (8227L)
DDR: 1G FLASH: 16G
CPU: A7 1.3GHz x 4
display: 1024x600
MCU: 3.1 (8227L)
Kernel Version: 3.18.22
Build number: android-trunk-m0.AC8227L-V1.0
Custom build version: android-trunk-m0.AC8227L-V1.0
Ok, so took a shot after posting this, and funny enough it worked to just do a factory reset via the android settings, and Radio app worked finally! Had to reinstall apps and accounts, but who cares, radio works again!
Now, anyone have any useful info on how to upgrade this unit now? The Android Upgrade and MCU Upgrade buttons are greyed out on this unit, and the various mods and updates I've found here won't do anything (zip files say unrecognized in the file folder and the system is not recognizing an upgrade file was loaded like I've seen others very easily be able to accomplish.
Not Android Auto, requested moderator move to Android head units forum