Related
Hey guys,
I recently bought a Joying headunit (JY-UM138P2) and I am wondering if there is a way to root my device.
I tried Kongoroot and it failed. Joying Extra Tools won't work beacuse it is not a Sofia Model. And as far as I can tell there is no custom firmware for this model availabile.
Android Version: 6.0.1
CPU: ARM Cortex A53 eight-core 2+32GB PX5, GPU: PowerVR G6110
Info on System: APP 1024*600 2017-01-11 19:13:52
MCU Version: 2017-11-06 17:57:54 JY_(R68)__26_C26_6026_CAN(All)
Which is the main problem as I cannot tell from this if it is an MTCC, MTCD or MTCE unit.
In general I actually do only want to have read and write acceess to the system/media folder to be able to switchout the bootanimation.zip for a custom one that I created.
Thank you!
MrAbstoss said:
Hey guys,
I recently bought a Joying headunit (JY-UM138P2) and I am wondering if there is a way to root my device.
I tried Kongoroot and it failed. Joying Extra Tools won't work beacuse it is not a Sofia Model. And as far as I can tell there is no custom firmware for this model availabile.
Android Version: 6.0.1
CPU: ARM Cortex A53 eight-core 2+32GB PX5, GPU: PowerVR G6110
Info on System: APP 1024*600 2017-01-11 19:13:52
MCU Version: 2017-11-06 17:57:54 JY_(R68)__26_C26_6026_CAN(All)
Which is the main problem as I cannot tell from this if it is an MTCC, MTCD or MTCE unit.
In general I actually do only want to have read and write acceess to the system/media folder to be able to switchout the bootanimation.zip for a custom one that I created.
Thank you!
Click to expand...
Click to collapse
That's an fyt SoM... Solutions soon? Standby
MrAbstoss said:
In general I actually do only want to have read and write acceess to the system/media folder to be able to switchout the bootanimation.zip for a custom one that I created.
Click to expand...
Click to collapse
So far the Joying units were rooted on linux/adb level.
So if you can make an adb connection over WiFi to your unit, you already have root terminal access via adb.
That is enough for doing what you want.
Well, so far I managed to establish an ADB via wifi connection (without using an usb cable, as I dont have a male to male usb cable).
But it lists my headunit as an unauthorized device.
MrAbstoss said:
Well, so far I managed to establish an ADB via wifi connection (without using an usb cable, as I dont have a male to male usb cable).
But it lists my headunit as an unauthorized device.
Click to expand...
Click to collapse
Try this
MrAbstoss said:
Well, so far I managed to establish an ADB via wifi connection (without using an usb cable, as I dont have a male to male usb cable).
But it lists my headunit as an unauthorized device.
Click to expand...
Click to collapse
Hello, I just got my new HU (same as yours) I was able to root with kingoroot over usb adb. Go to Developer options (pw 3368), In the top right corner, underneath the back button is a menu icon. Tap and then tap "USB computer connection." Then select the bottom option. I believe only the left side USB will work (when facing front of HU) and you may need to toggle the USB debugging switch. Windows, adb based kingoroot will work.
Only problem, root will not stick after reboot...I was able to install xposed framework, and install xposed Additions. Additions still works after loss of root, so not so bad. I use a RcJoyCon to HW keyboard for my SWC I am still experimenting with other apps.
Does loss of root mean a locked bootloader?
I also had no male to male USB, just made my own. Just twisting the wires together worked fine.
Please share if you learn of any ways to retain root.
Will monitor this thread, as Im looking for root for JY-UM135P2 too. Will try the usb method soon.
EDIT: tried to make custom male to male usb. Connected the 5 wires. Laptop and hu doesnt recognise the cable.
steef84 said:
Will monitor this thread, as Im looking for root for JY-UM135P2 too. Will try the usb method soon.
EDIT: tried to make custom male to male usb. Connected the 5 wires. Laptop and hu doesnt recognise the cable.
Click to expand...
Click to collapse
My usb mod only involved 4 wires. Not sure whats going on with the extra wire, that may be the issue. Double check your connections.
Was able to re-root today using my X98 tablet, Good news for the future, when needed after car install. Its rare that you would need to reboot anyways, after all the software mods have been done . Deep sleep retains root, and the device is only drawing 0.01Amps(limit of measure)
I'll have more to share for these non MTCD/E, PX5 units in the future. Have found a way to keep user apps in memory, after deep sleep by using xposed modules. Tasker now stays active.
Oke today tried again. Bought male to male usb. Still the cable js not recognised in both usb ports. Enabled usb debugging and tried lower and upper option in the chinese menu from developer options. So no clue for now
Experimental and untested
As some of you might know I created a windows and linux script to install seSuperuser onto the Joying Sofia3GR Intel units.
I just compiled su and the Superuser.apk for the PX5 models. I do not have a PX5 and therefore this is completely untested!
Prerequisites:
- You need to have adb over tcpip working.
- (Linux) You need to have adb installed (but you have otherwise the line above would not be possible)
- Have a Joying PX5 ROM available so you can reflash if necessary.
On your pc:
Download the attached Superuser-JoyingPX5-Arm.zip onto your pc/laptop.
Unzip it somewhere on your pc/laptop.
On Windows: Run CMD.exe as Administrator.
On Linux like OSes: Open a terminal.
Change to the folder where you unzipped the files and change to the folder where the install.sh and install.bat are located.
On Windows: Run the install.bat script with the IP address of your Head Unit as a parameter: install.bat 192.168.178.50 (for example)
On linux: Run the install.sh script with the IP address of your Head Unit as a parameter: ./install.sh 192.168.178.50 (for example)
Wait until the script finishes.
Reboot your Head Unit.
gtxaspec said:
That's an fyt SoM... Solutions soon? Standby
Click to expand...
Click to collapse
Hi gtxaspec,
Are you planning to make an custom rom for these Rockchip PX5, FYT 6026 bases headunits?
I have your GTX joying ROM V9a3an on a Joying FYT6021 intel SoFIA and it works so much better than the stock rom.
Keep up the good work!
surfer63 said:
Try this
Click to expand...
Click to collapse
i finally got my device connected and also got the unauthorized message:
"This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device."
I tried everything i could find on the net and in your link but still had no luck...
Does anybody have an idea what else I could try?
The thing with my device is - in order to be able to connect to it with adb I had to change something in the developer options menu: in the top right corner there are 3 dots (even above the On/off switch) and there you can only choose "USB computer connection" - if you click on that a popup menu appears "USB MODE" and 2 chinese options to choose from. It was set on the first option but only works if set on the second option (it's chinese so i can not read it)
This thread relates to MCU: CSN2_xxxxx, CSN2_D_xxxxx and CSN2_8600_D_xxxxx for PX4, PX5 and PX6 platforms
This thread is a mirror of russian 4pda to cover more users/developers.
All units are made by Klyde, but are sold under different brands.
I've been looking for a simple way to donate me if this thread is useful for you, all the ways are collected in one post there
The thread requires a new mainteiner. Details are there.
Hardware specifications:
CPU: Octa-core PX5 1.5GHz Cortex A53 64 bits CPU
ROM: 16/32/64G
RAM: 2/4G
Resolution: 1024*600
Out Power: 4*45Watt
Operating System: Android 8/9
Radio Tuner/Audio Chip: NXP6686 / TDA7851
Built-In WiFi Module /Support External 3G Dongle
Features: Radio Tuner,Built-in GPS,MP3 Player,Bluetooth,Touch Screen,TV,Mirror link,Built-In Microphone,Support Steering Wheel Control,Support Can-Bus
Useful tips
Tag [Android 8] means that it applicable to Android 8 , the same for [Android 9]. If there is no tag, it suits both versions.
Factory Settings password: 126
If you type 888 while opening Factory Settings, the Logo changing menu appears instead of Factory Settings. Logo1 replaces "Navigation system" picture, Logo2 replaces "android" picture. Logo2 is animated.
Developers mode password is 237
Password 927 opens menu, that helps to adjust screen brightens by changing VCOM value. You can set it between 1 and 100. Be careful with that!
[Android 8] How to get root: Use a rooting app, alternative link
[Android 9] How to root
Warning! You should be careful with that as it can brick your device once you tried to update SuperSu. Do not update SuperSu binary or the SuperSU app!!! You will get bootloop if that is updated!!! Also you have to wait until the tool completes its job, otherwise you can get no sound. If you face the mentioned problems, just re-flash your device. BE CAREFUL!.
Starting from android 8 January firmware there is an option "OFF" for "Power off delay if ACC OFF". it allows to keep android in a sleep mode forever. Please note that it consumes around ~9-10mA in this mode. Powered off device uses 4.8mA only (twice less than sleeping mode).
How to get enter stock recovery: hold reset(power) button, wait until sensor buttons start blinking, release and immediately press the button again. See video
To adjust the back camera brightness, just tap the screen when the camera is active.
Set custom logo
Detailed device schema
Known issues/limitations and fix/workaround for that
Lost wheel key settings and radio stations in case full power loss (yellow wire). Make sure that yellow wire is not disconnected when the car is stopped/locked.
Sound level is 10 (12) after reboot/sleep if you was listening louder; if it was less than 10 (12) stays the same. 12 appeared in Dec 11th firmware, it was 10 before that. Not topical starting from Dec 27th firmware, now you can define default sound between 12 10 and 20 in Car Settings-->Personal Settings. 10-20 is in Jan 17th firmware .
buzz in speakers caused by 433MHz alarm system and USB stick remounting.
small buzz caused by WIFI, observed in complete silence only. Not an issue if there are no connected devices.
There are lots of cases when wheel keys does not work at all. The reason is in wiring. Please study the head unit manual + car wiring scheme and put the needed wire to the correct connection shoe.
if you have canbus adapter and wheel buttons duplicate actions (i.e you pressed next track, but 2-3 tracks were switched, the same for sound level), just flash Jan 17 or newer firmware. Also it is possible to change wiring, but the firmware is much easier.
if you have canbus adapter and track switching is reversed (incorrect), just go to Factory Settings --> canbus and set keys_previous_next to change.
Bluetooth ODBII and hands-free (calls) does not work simultaneously. At the same time ODBII and BT Music works well simultaneously. Hardware limitation, no idea for now if that can be solved.
Voice dialing, voice search do not work on some devices. Fixed in May 8th firmware.
1.PX5 Firmware.
You can combine different firmware and MCU (I.e. take the pumpkin MCU + April firmware or vice versa). MCU from Android 8 is compatible with Android 9. Mind DSP only while updating MCU.
The factory does not provide me with a changelog! Do not ask about it.
Android 10.
Mar 31st 2021 202103310921
Mar 23rd 2021 202103231402 with Erisin launcher
Jan 4th 2021 202101041604 + MCU CSN2_D_1152020_114303
Fake Android 10.
It is the same android 9 firmware, but with the changed launcher, radio and Bluetooth app.
July 6th 202007061156
Android 9.
The link for the most recent firmware and MCU: with DSP and without DSP. _D_ in the MCU version means that it is for units with DSP.
All available versions of MCU are on my Google drive.
Firmware history and links:
Sep 1st 2020 202009011014
June 1st 202006010933
Android 8.
The link for the most recent firmware and MCU: with DSP and without DSP. _D_ in the MCU version means that it is for units with DSP.
All available versions of MCU are on my Google drive.
Firmware history and links:
June 18th 201906180853 + MCU CSN2_06102019_114308
2. PX6 Firmware
Android 10.
Aug 27th 2021 202108271854
Mar 31st 2021 202103311813
Oct 27th 2020 202010270905
Android 9.
July 1st 202007011143
3. PX5 Android 9 for 1 DIN units with MCU CSN2_8600_D
The differences between this unit are on Russian 4pda
Firmware 201911301053 + MCU CSN2_8600_D_11202019_162651 is located on Google Drive
4. PX4 Firmware
Android 10.
Oct 23rd 2020 202010231137
The instruction how to upgrade is there
The list of purchased devices
KLYDE for Subaru Forester
OTOJETA for Nissan and 3 more for Sportage IV
KANOR 2pcs for Oulander and 2DIN 2Din and 2pcs for Mazda, and for cee'd
SKYSHADOW for hyundai i40, and for Prado, also 2Din with 32Gb and 64Gb
HaiSunny for StantaFe
Eonon GA9180A for Chevrolet/GMC
Autostereo for Mazda 5
Tested and compatible 3G/4G modems
ZTE MF622
ZTE MF825
Huawei e173
Huawei E352
Huawei E3272
Alcatel 410D
How to update firmware on the device (without changing android version)
I know at least 3 methods how to do that Use USB Stick or SD card with FAT32 filesystem for android 8 or USB Stick ONLY for android 9.
1.
- put the firmware (kupdate.zip + update2.bin if you want to upgrade MCU) directly to USB stick or SD card,
- insert it while the unit is running,
- click OK once suggestion to update appears.
2. The same as 1, but the last point is to start update from system settings
3. Use it, if you have a brick (bootloop)
- put the firmware (kupdate.zip + update2.bin if you want to upgrade MCU) directly to USB stick or SD card with FAT32 filesystem for android 8 or ONLY USB Stick for android 9.
- power off the device, insert USB stick or SD card for android 8 or ONLY USB Stick for android 9.
- press and hold power button and power on unit by switching on ACC in your car or enable power +12V on both red and yellow wire in case you doing that on the table. On some units use reset button instead.
- once the update is started, release the button.
WARNING! Firmware update will remove all your personal data and settings on the device!
If you observe the error like "header and footer of kupdate.zip does not correspond signature", just try to upgrade form another USB stick/SD card.
Upgrade from Android 8 to Andriod 9 (Using disassembling method)
For now it is needed to DISASSEMBLE the unit for upgrade! These actions are on your own responsibility!!!
0. You will need Windows PC/Laptop/Tablet for this procedure, please refer to guide from Chinese engineers here.
1. Install drivers from this archive
2. Short circuit the resistor to ground (there is a picture in guide)
3. Power on the unit
4. Connect USB (use Type-A male to Type-A male cable).
5. Flash the Android 9 data from this archive
6. Disconnect USB and power. Then power on the unit.
7. Enjoy
After these steps you'll be able to install any android 9 from this thread. It is needed to disassemble the unit only once.
A few videos for the reference are there and there.
Upgrade from Android 8 to 9 WITHOUT disassembling.
ALL YOUR ACTIONS ARE YOUR OWN RESPONSIBILITY!!! Nobody will send you a new core board in case of the failure! At least will not do that free of charge!
0. All needed files are there.
1. To perform the upgrade we need:
- Strong desire to do that and be ready to purchase a new core board in case of total failure (~100$);
- micro SD card slot in your unit. If the unit vendor gives details regarding the units without SD cards, I'll update this post;
- USB stick (up to 16GB, to avoid possible problems) formatted in fat32;
- micro SD card (again, please use not so big);
2. Put the following things on USB stick:
- MCU firmware that suits your device. I.e. update2.bin from the first message in thread with DSP or not depending on your unit)
- Android 9 firmware from the first message. kupdate.zip, Again: Andriod 9!!!
3. Do NOT plug USB stick to the unit for now, let`s make bootable SD card;
4. On Windows PC run SDDiskTool and create bootable SD card. The manual inside of the archive, with the details, so I see to reasons to repeat it there. update.img from the archive is used there ~350Mb;
5. Install "Android 8 upgrade 9.apk" into the unit, run it, click only the button in this application. The unit becomes a brick (temporary, till a success on step 9) - You will see only a black screen and lights on the buttons;
6. Put SD card into a units slot, disconnect battery terminal of your car or power off the unit in some other way. Both red and yellow wires of unit should not have +12V on them !!!
7. connect battery terminal.
8. The unit is upgraded for the first time. Take a video of the process!!! Just in case if you fail and it will be needed to troubleshoot that. On this step you should see TWO errors of formatting metadata. YES, there should be TWO errors!! and formatting error for system.
Video of attempt.
The final screenshot.
9. Disconnect and connect battery terminal one more time. The unit upgrades from SD card one more time Take a video of the process,just in case. this time there should be no errors with metadata and system!!! The last string should be "Doing Actions succeeded".
Video of 2nd attempt.
The final screenshot.
10. Disconnect battery terminal, REMOVE SD card from unit, plug USB stick prepared on step 2.
11. Connect battery terminal and the unit will complete the upgrade to Android 9.
12. Once the upgrade from USB stick is done, the unit start running Android 9. All further upgrades will be done from USB stick without any additional actions
Video of installing the firmware from USB Stick.
13. FORMAT SD card on your PC, do not use it in unit until it is formatted, just to be safe.
Upgrade to real android 10
There are 2 known ways how to upgrade to android 10.
1. Disassemble your unit and do the same as described there using the files for PX5 or PX6 depending on your platform. Also there is an instruction with pictures in each archive.
2. Without disassembling, but using windows laptop or tablet. Quite simple, but requires lots of checks and preparations. And in worth case scenario you will have to solder to the needed pins of coreboard.
!!! The upgrade is possible on motherboards rev 1.4, 1.5.2 and 1.6 (quite possible that other revisions too, but we have not enough information for now). The mainboards of rev 1.2 require disassembling and soldering additional usb cable!!!
In order to complete the upgrade we need:
- strong desire to do that and be ready to disassemble unit in case of the failure or even purchase a new one.
- USB type A male to type A male cable
- Windows laptop or tablet
Steps to do.
1. Preparation
- check the Bluetooth module that is configured in your unit: System Settings-->Factory Settings-->FUNC-->BT Mode. Note its model somewhere. That will be needed to restore the settings after the upgrade.
- check if you can do an upgrade:
-- install terminal emulator on your unit and run
Code:
dmesg | grep "USB device" | grep using
and note the last time stamp
-- plug USB stick to the first USB (on the panel or into an extender cable)
-- run again
Code:
dmesg | grep "USB device" | grep using
-- if you see something like
Code:
[ 4781.749803] usb 3-1: new high-speed USB device number 16 using usb20_otg
you can use this USB and plug the head unit to your laptop via it using USB male type A to male type A cable. usb20_otg is vital
-- if you see something like
Code:
1-1.3: new high-speed USB device number 5 using ehci-platform
This USB can not be used!
-- repeat the action for the second unit`s USB
-- IF BOTH PORTS DOES NOT HAVE OTG YOU CAN NOT GO FURTHER UNTIL YOU SOLDER THE 3RD CABLE! The instruction is at the end of this post.
- download PX5 or PX6 depending on your platform.
- if you have a display with resolution 1280*720 , download a custom oem.img, it is suitable for both PX5 and PX6;
- extract archive to root directore of drive C: You should have C:\px6_10.0_burntools\ or C:\px5_10.0_burntools\ folder;
- install drivers from DriverAssitant folder;
- in case of PX6 go to C:\px6_10.0_burntools\AndroidTool_Release_v2.71, for PX5 go to C:\px5_10.0_burntools\AndroidTool_Release_v2.71, edit config.ini, replace Selected=1 with Selected=2. That will enable English language for the program;
- if you have 1280*720 display, put the custom file to rockdev\image folder and replace the old one;
- backup all vital data on your head unit;
2. Upgrade
- run AndroidTool.exe
- download and install this APK
- run it and click "Go to Android10", the device will be rebooted and BRICKED. APK kills loader and boot partition!!!
- connect your laptop and head unit via the discovered OTG USB
- AndroidTool should reprt "Found one MASKROM device"
- hit run button;
- wait until the competition.
The unit will be rebooted, data partition will be formated and the unit will be running andriod 10.
3. Post upgrade
- download the most recent firmware
- put it on USB stick
- do an upgrade using this USB stick
Known issues and fixes
1. Bluetooth KD6 does not work on android 10. Replace the module with IVT140 or RF210, maybe it will be fixed in new firmware. Fixed starting from 202011261850
2. In some unique cases the rear camera does not work on android 10 (we suspect that it appears on old mainboard revisions without DSP). Fix is to revert to android 9 or maybe it will be fixed in new firmware. Fixed starting from 202010141730
TIPs.
Mainboards Rev 1.2 do not have USB OTG, so you have to solder the 3d USB cable. Just solder the USB wire to connector A if the mainboard. Pins 63 and 64. 63rd stands for D+, 64th corresponds D-. Do not forget about GND. +5V is not mandatory for upgrade, you can take it from rear connector H (check pin 5 or 10 there) and make fully working USB port.
{
"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"
}
Now we need TWRP and some proper custom ROM support.
February 20th 201902201912 + MCU CSN2_0192019_154914 from Pumpkin ND0294 suitable for us said:
I couldnt download the file, it comes corrupt.
---------- Post added at 01:51 PM ---------- Previous post was at 01:48 PM ----------
In my unit, buzz comes when the radio is off, and the noise seems like the radio was turned on, but in very low volume... Does it happen with you too, guys?
Click to expand...
Click to collapse
aecioms said:
I couldnt download the file, it comes corrupt.
Click to expand...
Click to collapse
Fixing my google drive.
aecioms said:
I couldnt download the file, it comes corrupt.
Click to expand...
Click to collapse
Fixed.
Does this unit permit firmware downgrade?
aecioms said:
Does this unit permit firmware downgrade?
Click to expand...
Click to collapse
If you are talking about downgrade from, let's say, Feb firmware to Dec firmware - it works. If you are looking some exotic android like 6.0, there is no firmware with old android for these units.
Head units RockChip PX5 with MCU CSN2 (Android 8.0.0): discussion, firmware, tips etc
_yuzo_ also add these skyshadow products. I own the 1st one with 64gb upgraded version
1. Adjustable 10.1" IPS Android 8.0 4GB +32GB + 8 Core Car DVD Player GPS Glonass map RDS Radio wifi Bluetooth 2 Din for universal
https://s.click.aliexpress.com/e/bSVJ1e80
Particularly the 64gb free upgraded versions were csn2
2. New IPS 10.1" Android 8.0 4GB +64GB + Octa Core Car DVD Player GPS Glonass map RDS Radio wifi Bluetooth 4.0 2 Din for universal
https://s.click.aliexpress.com/e/cncQMDNQ
Sent from my iPhone using Tapatalk
sambhasanbiswas said:
_yuzo_ also add these skyshadow products. I own the 1st one with 64gb upgraded version
Click to expand...
Click to collapse
Done.
Hi Yuzo. Do you know if there is a way to pull a copy of my existing OS and MCU that came shipped with the unit? I want to try flashing to the latest pumpkin MCU, but would like to restore to stock if needed. My unit is an Eonon GA9180a. Thanks!
Build Number: 201811021951
Kernel: 4.4.103
MCU: CSN2_1122018_153527
Guys, I can't transfer files with ES File explorer by WLAN. It says "sender disconnected"... Does it happen with someone else? How to solve this?
Now I need to use pendrive everytime I want to transfer files to headunit...
rblloyd83 said:
Hi Yuzo. Do you know if there is a way to pull a copy of my existing OS and MCU that came shipped with the unit? I want to try flashing to the latest pumpkin MCU, but would like to restore to stock if needed. My unit is an Eonon GA9180a. Thanks!
Build Number: 201811021951
Kernel: 4.4.103
MCU: CSN2_1122018_153527
Click to expand...
Click to collapse
Hi! Rooting app contains tools for backup, but that is rather alfa version and noone tried to flash that dump back.
Your MCU is present in very first firmware available there. I, as well as xda and 4pda users, do not have 201811021951 firmware. But I can assure that Jan 17th and Pumpkin firmwares are stable. The only noticeable difference between them is in a launcher, application appearance. Also Pumpkin does not have the option that allows to set the brightness according to the clock.
Please also share the link where you bought your device.
_yuzo_ said:
Hi! Rooting app contains tools for backup, but that is rather alfa version and noone tried to flash that dump back.
Your MCU is present in very first firmware available there. I, as well as xda and 4pda users, do not have 201811021951 firmware. But I can assure that Jan 17th and Pumpkin firmwares are stable. The only noticeable difference between them is in a launcher, application appearance. Also Pumpkin does not have the option that allows to set the brightness according to the clock.
Please also share the link where you bought your device.
Click to expand...
Click to collapse
Thanks, sure appreciate the feedback. I purchased this system:
"eonon.com/Android-Car-GPS/Vehicle-Specific-GPS/Chevrolet-GMC-Buick-Newest-Android-8-0-Car-GPS-Navigation-System-7-Inch-Auto-Stereo-Upgrade-RAM-4GB-Factory-Auto-Radio.html"
I just wanted to list my csn2 device that I ordered at aliexpress from seller autostereo for my Mazda 5: https://de.aliexpress.com/item/-/32913733250.html
I did not do any modification so far. But steeringwheel keys do double clicks, so maybe I will try some update later.
rblloyd83 said:
Thanks, sure appreciate the feedback. I purchased this system:
"eonon.com/Android-Car-GPS/Vehicle-Specific-GPS/Chevrolet-GMC-Buick-Newest-Android-8-0-Car-GPS-Navigation-System-7-Inch-Auto-Stereo-Upgrade-RAM-4GB-Factory-Auto-Radio.html"
Click to expand...
Click to collapse
Thanks. Added.
donny02 said:
I just wanted to list my csn2 device that I ordered at aliexpress from seller autostereo for my Mazda 5: https://de.aliexpress.com/item/-/32913733250.html
I did not do any modification so far. But steeringwheel keys do double clicks, so maybe I will try some update later.
Click to expand...
Click to collapse
Added to the list of devices. The case is connected with canbus adapter and fixed in Jan 17th firmware (also it is possible to fix that by changing wires, but firmware update is much easier). If you want to keep the original launcher - use Jan 17th firmware, otherwise you can try Pumpkin.
Eonon GA9180A For Chevy/GM Trucks is running CSN2. Im pretty sure its a klyde as well.
As for the static when D/L U/L over wifi. It because the wifi antenna is taped directly to the top of the am/fm receiver and not properly shielded.
I did buy a new antenna with a longer cable. One of these days i will pull it out of the truck and add the new one in and reroute the wiring to see if it helps any.(not in a rush since it doesn't bother me to much)
Flyaudio in Russia sells head units for a variety of cars that are also based on the Intel Airmont CPU, similar, but not equal to Joying latest Intel Airmont head units (see https://forum.xda-developers.com/an...ying-android-8-1-intel-airmont-eight-t3897206 and https://forum.xda-developers.com/an...ing-finally-head-unit-digital-output-t3891087 )
I purchased a G4909R unit, a 10 inch (=no knobs) unit for Volkswagen Passat B7 (https://flyaudio-shop.ru/products/g4909r-magnitola-android-volkswagen-passat-b7-2010-2015)
Youtube video https://www.youtube.com/watch?v=HZhE30W5ej8
Similarities to Joying’s units:
- Android 8.1.0 “user” build with its limitations for rooting, adb, debugging, etc.
- DSP with quite a lot of equalizer settings, but it seems to be a slightly different DSP
- FYT/SYU system apps (oh dear…)
Differences to Joying:
- No SPDIF audio output
- No 3G/4G modem
- Different BT chip
- Completely different form-factor (see video linked above at timestamp 6:06 https://youtu.be/HZhE30W5ej8?t=366 )
Passwords
Factory Settings: 3368
Developer Settings: 3368
Backlight current adjustment: 5768
Door lock interference: 0000
I was able to root it with the same approach (but not using the ready-made files!) as documented for the Joying units https://forum.xda-developers.com/an.../howto-root-joying-sc9853i-head-unit-t3915530
I noticed that some apps that I used on Intel Sofia and Rockchip PX5 units without problems now run into crashes on this unit, actually ANRs (Application Not Responding).
Actually, the Android 8.1 version on this unit is quite different compared to a “stock” Android 8.1, both from its UI and also “internally”.
SYU has created a monster of a Settings app. Car related settings and standard Android settings are all mixed without any structure. Not very clever at all!
Another Android modification: The steering wheel controls for PREV and NEXT only work when used in the SYU system apps (e.g. FM radio and Music player). No other standard app works, also not my DAB-Z app. Reason is that the FYT middleware is circumventing the Android framework MediaSession handling completely and thus the MediaControl interfaces in apps don’t work.
The SYU Bluetooth app still kills Google contacts, a bug that existed already 3 years ago in the Intel Sofia units with Android 6.01. They have not done anything about it!
My conclusion after some days with the unit on my desk, and now in the car for about a week:
Nice hardware, but the software is crippled more than ever…
realzoulou said:
Similarities to Joying’s units:
- Android 8.1.0 “user” build with its limitations for rooting, adb, debugging, etc.
I was able to root it with the same approach (but not using the ready-made files!) as documented for the Joying units https://forum.xda-developers.com/an.../howto-root-joying-sc9853i-head-unit-t3915530
Click to expand...
Click to collapse
Now that you have it rooted, you can make the /system read-writable from a rooted terminal.
Code:
su
mount -o remount,rw /system
Can you change the build.prop?
Code:
ro.build.type=user
to
Code:
ro.build.type=userdebug
and add:
Code:
persist.adb.tcp.port=5555
ro.debuggable=1
ro.adb.debuggable=1
And reboot?
Maybe you can then adb over tcpip?
I'm not sure whether this will work, but you can try.
On a normal user build adbd is not enabled/started. So it also might require the addition of "start adbd" in the "/system/bin/install-recovery.sh".
(But maybe when you set the debuggable properties, it is started automatically. I should take a look at the rc files in the boot image)
I enabled adb over WiFi persistently. However, it was a bit tricky.
1. Enable USB device mode in Developer Menu (very well hidden: First click on "..." on uper right corner, then the second option in the Chinese dialog)
2. Connect head unit to PC via USB (not all USB ports of the device allow adb, so try out all of them)
3. Use "adb shell" to execute
Code:
su
setprop persist.adb.tcp.port 5555
After a reboot you can connect via adb over WiFi.
The property ro.build.type is set usually by the kernel. You cannot set it via build.prop.
realzoulou said:
I enabled adb over WiFi persistently. However, it was a bit tricky.
1. Enable USB device mode in Developer Menu (very well hidden: First click on "..." on uper right corner, then the second option in the Chinese dialog)
2. Connect head unit to PC via USB (not all USB ports of the device allow adb, so try out all of them)
3. Use "adb shell" to execute
Code:
su
setprop persist.adb.tcp.port 5555
After a reboot you can connect via adb over WiFi.
The property ro.build.type is set usually by the kernel. You cannot set it via build.prop.
Click to expand...
Click to collapse
i know this is old, but...
I have adb over wifi enabled... when i connect to ADB i get device unauthorized. I shouldn't need usb drivers since its wifi, right? I am 99% sure its device related and not my laptop or software, because I have an 8227 headunit that connects fine. Is there anyway to authorize my TS9 Topway unit through terminal without root?
Hello,
I'm new with the Head Unit based on Android and If someone could help me answer some questions it could help me a lot.
I have this unit
In short:
Allwinner T8 board
MCU: T8.3.19-167-10-A43101-190504
System: V9.3.1_20181106.155925_CLC1-FD
Android 8.1
I'm trying to modify the ROM... and I don't care If I loose all the pre-installed crap inside.
So far, this is what I can do with this rom:
- Install APKs...
- Remove APKs...
- Connect via ADB over network
if beforehand inside the device I type "setprop service.adb.tcp.port 5555" in a terminal, then turn off and on the debug option in the developper menu. Thanks to serious manufacturers, all passwords seem to be shared between various if not all unit buyable over internet. The command and developper option trick must be done after EACH reboot, wich is fantastic behavior.
- Reboot to bootloader or recovery using adb
- In recovery, I can do nothing since there is no hardware key appart "reset"..., USB keyboard seem to not work either (I cry when I see the non reachable "mount /system" option ...).
- Use a hand made USB A-A cable to communicate with the device, when in bootloader. If "in rom" or recovery, adb or fastboot don't see the device.
So basically I can do nothing.
- I searched for firmwares, but I only find direct links to various site that provide update.zip or update.img or similar, but no flashable firmware from fastboot.
- If I found update firmware for T8 based board, my manufacturer version code (CLC1-FD) match none of those available here or on russian forums (AKW1-FD, JP1, TW2-FD,....).
- I can not use su (not allowed, setgid failed), to make boot and system image backup that I can eventually modify
- I tried KingRoot, Magisk (but I have no boot image ...) none work
- I tried "fastboot oem unlock[or whatever]", which just freeze fastboot and make it unusable until another reboot
So in the end, if someone know something about this hardware, if the another firmwares (AKW1-FD, JP1, etc) are compatible between devices, or if you know where I could ask for original firmware (oem image), or if it is possible to unpack the updates files to extract something exploitable (already tried for hours using basically all tools available like kitchen simg2img etc), please help me.
I have another device that will come to me, the ownice C800, but I think it will be the same problem. Unmodifiable over locked device.
I am working in a business where we need this kind of hardware inside a car, and we wanted to use one of the unit to make a proof of concept so we cannot afford custom hardware right now.
Thanks you if you had the patience to read this. Hope you can help.
Update and file recovery for Allwinner T8
Hello,
Do you find or have rom, firmware for Allwinner T8 and any app radio for testing?
Do you know? How make file *.img rom from my Unit?
Tomek
Hi there,
I got myself the following unit on aliexpress: https://de.aliexpress.com/item/4000805871840.html?spm=a2g0s.9042311.0.0.52ef4c4dBTvhGh. It has a CHS MTCE.
When I look at factory settings, it says "A-Media Auto" as device name.
It came with zlink Carplay PCB mounted on the PCB and worked with stock rom. When I changed to mod firmwares (e.g. HAL9k or Malysk) I actually lost the CarPlay functionality. zLink just stays at "waiting", however my phone identifies the unit as CarPlay available and connects over bluetooth using the carplay connection dialog. However the "use carplay now" dialog doesn't pop up. Manufacturer says, the unit would need to be returned to factory to reprogramme. Not sure this entirely the only option.
They said they don't offer the stock rom, just updates.
A friend of mine has bought exactly the same unit, so I was wondering if I could extract the OEM stock software from there and flash onto my unit. I am not an Android expert, however already changed a couple of iPhones/Tablets OEM software e.g. to LineageOS. So, with some turoials I normally find my way around. I am ok experienced on admin level on WIN and Linux.
Not sure the OEM Android is fully rooted, but I can find out, when I have the OEM unit in my hands.
Is there a (relatively safe) process to extract the stock rom and update the modded rom HU?
See my OTG thread, extract partition by partition from your friends unit, which you mention is the same, then flash your SOM.
Thanks for replying.
My SOM has an USB port soldered to it. (See photo). Chances are, I do not even use the "wire" method to connect, but just use this port?
wupperi said:
Thanks for replying.
My SOM has an USB port soldered to it. (See photo). Chances are, I do not even use the "wire" method to connect, but just use this port?
Click to expand...
Click to collapse
PX6 board has a HDMI connector on it - do you mean that?
I am also interested in a PX6 stock Android 9 partition export image, as I recently bought a PX6 board which has Android 10 preinstalled and therefore I am currently limited to it and can´t "downgrade" to my preferred ROM Hal9k v4 beeing Android 9 based...