Related
Hello,
i need an update.zip or an update.img of stock firmware for T-R42 B351 V1.0 or V1.1
to be put into the external sd card to recover the system
I have recovery version 4.2.01, that prompts for this options:
update from external storage: needs update.zip
update rkimage from external storage: needs update.img
I have no other options because my pc is no more able to recognize my T-R42 B351 V1.1
Where can i found such files?
Thanks
T-R42 B351 V1.0 stock firmware
Vicolodo said:
Hello,
i need an update.zip or an update.img of stock firmware for T-R42 B351 V1.0 or V1.1
to be put into the external sd card to recover the system
I have recovery version 4.2.01, that prompts for this options:
update from external storage: needs update.zip
update rkimage from external storage: needs update.img
I have no other options because my pc is no more able to recognize my T-R42 B351 V1.1
Where can i found such files?
Thanks
Click to expand...
Click to collapse
All the stock firmware for are here: T-R42 B351 V1.0 or V1
http://pan.baidu.com/share/home?uk=2134144741#category/type=0
el_easy said:
All the stock firmware for are here: T-R42 B351 V1.0 or V1
http://pan.baidu.com/share/home?uk=2134144741#category/type=0
Click to expand...
Click to collapse
thank you,
i am a newbie,
do you think that with stock rom it is possible to update the device
putting the rom in the sdcard and choosing `update rkimage` option?
thanks!
Vicolodo said:
thank you,
i am a newbie,do you think that with stock rom it is possible to update the device
putting the rom in the sdcard and choosing `update rkimage` option?
thanks!
Click to expand...
Click to collapse
stock firmware you update using your computer with Rockchipbatch tool
- Download firmware from T-R42 B351 V1.0 and extract the file save it to your desktop.
- Press the recover button of T-R42 and don’t loose it. Then you can connect T-R42 and computer by using micro USB cable (OTG port of T-R42 to USB port of computer.
- You can now launch the Batch Tool by double clicking on the file named RKBatchTool in the folder where you extracted the Batch Tool 1.7 to. You should see the following:
el_easy said:
stock firmware you update using your computer with Rockchipbatch tool
- Download firmware from T-R42 B351 V1.0 and extract the file save it to your desktop.
- Press the recover button of T-R42 and don’t loose it. Then you can connect T-R42 and computer by using micro USB cable (OTG port of T-R42 to USB port of computer.
- You can now launch the Batch Tool by double clicking on the file named RKBatchTool in the folder where you extracted the Batch Tool 1.7 to. You should see the following:
Click to expand...
Click to collapse
thank you,
but the problem is that my pc cannot see the t-r42
Vicolodo said:
thank you,
but the problem is that my pc cannot see the t-r42
Click to expand...
Click to collapse
You may be bricked. If so you can jump pins 8&9 on the nand chip to get it into MaskRom mode.
1.Load RKBatchTool with your ROM.
2.Connect only OTG cable - power is not required.
3.Hold power button down.
4.Short pins 8 and 9 with needle or pin until Batch tool display blue icon that is MaskRom mode.
5.Remove needle and load firmware into program.
6.Click restore and wait for success.
Hope this helps
BRICK0044 said:
You may be bricked. If so you can jump pins 8&9 on the nand chip to get it into MaskRom mode.
1.Load RKBatchTool with your ROM.
2.Connect only OTG cable - power is not required.
3.Hold power button down.
4.Short pins 8 and 9 with needle or pin until Batch tool display blue icon that is MaskRom mode.
5.Remove needle and load firmware into program.
6.Click restore and wait for success.
Hope this helps
Click to expand...
Click to collapse
THANK YOU!!
but HOW CAN I FIND THE NAND CHIP on my T-R42 board?
i already asked in other threads and other forums but i have not get answers yet
In attachment i link the snapshot of the board... can you help me?
THANKS!
Vicolodo said:
THANK YOU!!
but HOW CAN I FIND THE NAND CHIP on my T-R42 board?
i already asked in other threads and other forums but i have not get answers yet
In attachment i link the snapshot of the board... can you help me?
THANKS!
Click to expand...
Click to collapse
what does it say on the big rectangular chip above the heatsink? I think it might be on the other side of the board though, can you take a pic of the other side?
BRICK0044 said:
what does it say on the big rectangular chip above the heatsink? I think it might be on the other side of the board though, can you take a pic of the other side?
Click to expand...
Click to collapse
Yes,
here is the link to all the snapshots i did (there are also snapshots of the power adapter, you can skip them)
https://www.dropbox.com/sh/fnz01w8ylpxuzxi/oc5gJHjO5g
Vicolodo said:
Yes,
here is the link to all the snapshots i did (there are also snapshots of the power adapter, you can skip them)
https://www.dropbox.com/sh/fnz01w8ylpxuzxi/oc5gJHjO5g
Click to expand...
Click to collapse
I don't see any of the other side of the board, but I need to know the numbers and letters on the Toshiba chip. I can't make them out in the pics
BRICK0044 said:
I don't see any of the other side of the board, but I need to know the numbers and letters on the Toshiba chip. I can't make them out in the pics
Click to expand...
Click to collapse
Ok thank you, i understand,
i am not at home now
When this evening i go back to home i will send to you the numbers and letters of the Toshiba chip,
and higher resolution snapshots of all the chips
I will try also to take some snapshots of the other side of the board (not yet done this because i had fear to break some connector to take it out)
Thank you a lot!
Vicolodo said:
Ok thank you, i understand,
i am not at home now
When this evening i go back to home i will send to you the numbers and letters of the Toshiba chip,
and higher resolution snapshots of all the chips
I will try also to take some snapshots of the other side of the board (not yet done this because i had fear to break some connector to take it out)
Thank you a lot!
Click to expand...
Click to collapse
Almost sure it is the Toshiba chip above the heatsink but need the number, may not get right back to you because Im going on vacation but will try.
---------- Post added at 12:51 PM ---------- Previous post was at 12:29 PM ----------
BRICK0044 said:
Almost sure it is the Toshiba chip above the heatsink but need the number, may not get right back to you because Im going on vacation but will try.
Click to expand...
Click to collapse
I magnified the Toshiba chip and it is your nand chip. I use the end of a needle with the eye in it and be patient it might not work the first time just keep trying with the directions I gave you. As soon as you see the blue light in rkbatchtool come on remove the needle and restore. Good luck let me know . By the way the number one pin is the one by the dot on the chip and count down from there.
BRICK0044 said:
Almost sure it is the Toshiba chip above the heatsink but need the number, may not get right back to you because Im going on vacation but will try.
---------- Post added at 12:51 PM ---------- Previous post was at 12:29 PM ----------
I magnified the Toshiba chip and it is your nand chip. I use the end of a needle with the eye in it and be patient it might not work the first time just keep trying with the directions I gave you. As soon as you see the blue light in rkbatchtool come on remove the needle and restore. Good luck let me know . By the way the number one pin is the one by the dot on the chip and count down from there.
Click to expand...
Click to collapse
hello, thank you!!
the numbers and letters are:
TOSHIBA SW2857
TAIWAN 13359AE
TC58TEG6DCJTA00
here the snapshots:
https://www.dropbox.com/sh/vmkcl05ha541j11/_orwLkI82h
NAND CHIP FROM OTHER T-R42 board
These are examples from other boards that are bricked, look at it ,are similar like your...
Try 8 and 9 pins with a needle..
I have read that the NAND chip like the pin 5 ,6 , 6 and 7, 7 and 8 or 8 and 9. as work too.. , But 8 and 9 work for many people... . Don't hurry up it may take many attempts ...
More Information here:Unbrick or fix NAND on the MK808
el_easy said:
These are examples from other boards that are bricked, look at it ,are similar like your...
Try 8 and 9 pins with a needle..
I have read that the NAND chip like the pin 5 ,6 , 6 and 7, 7 and 8 or 8 and 9. as work too.. , But 8 and 9 work for many people... . Don't hurry up it may take many attempts ...
More Information here:Unbrick or fix NAND on the MK808
Click to expand...
Click to collapse
Hello,
thank you
counting starting from the pin no 1 (i suppose it is the pin on the corner near the dot on the chip, can you confirm?),
i tried with 6,7 and 7,8 and 8,9
but with no results
instead, shortening the 9,10 i get on the pc the message: 'unknown usb device' (like when i press the reset button) but RkBatchTool (v 1.7) does not go to Mask Rom Mode.
and i get this message only when the power adapter is connected
But seems that the NAND flash is not resetted:
turning off / on the device, i see that is loaded the same firmware (boot animation starts as before...and so on)
I supposed that this operation should reset the NAND flash, or i am wrong?
Thanks!
Vicolodo said:
Hello,
thank you
counting starting from the pin no 1 (i suppose it is the pin on the corner near the dot on the chip, can you confirm?),
i tried with 6,7 and 7,8 and 8,9
but with no results
instead, shortening the 9,10 i get on the pc the message: 'unknown usb device' (like when i press the reset button) but RkBatchTool (v 1.7) does not go to Mask Rom Mode.
and i get this message only when the power adapter is connected
But seems that the NAND flash is not resetted:
turning off / on the device, i see that is loaded the same firmware (boot animation starts as before...and so on)
I supposed that this operation should reset the NAND flash, or i am wrong?
Thanks!
Click to expand...
Click to collapse
8,9 pins should be around here
el_easy said:
8,9 pins should be around here
Click to expand...
Click to collapse
ah...thanks!
so i have not to count the pins starting from the dot that i see on the corner of the chip?
Tc58teg6dcjta00
hello,
i am searching for the pdf datasheet related to the chip TC58TEG6DCJTA00
I searched it on many websites, but i am not able to find it...
el_easy said:
8,9 pins should be around here
Click to expand...
Click to collapse
I don't think you are right, the dot is on the other side. So pin 8,9 should be on the other side.
buhohitr said:
I don't think you are right, the dot is on the other side. So pin 8,9 should be on the other side.
Click to expand...
Click to collapse
thanks,
i asked the datasheet to toshiba,
but they answered me they can not send informations to private persons ...
by the way... i tried with all pins 1,2 2,3 3,4 4,5 etc but there is no way to get the Mask Rom Mode...
the only message i get on my pc shortening some couple of pins (es.: 9,10, but also some others) is 'unknown USB device'... (and this happen only when i connect the power plug... when it is not connected i have no messages...)
(like when i press the reset button)
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)
ROM / Firmware/ Brick Recovery for 7" Android Head Unit AC8227l YT9217 YT9218 1/16GB
Thanks everyone who contributed in my effort to fix my bricked device. Here is all that I have found useful in successfully reviving my device.
The files shared here are the ones that worked on my unit (see specs and pictures below) If your device is different, it may or may not work.
If the device has dedicated radio chip inside, the Firmware number will show as YT9218, if no radio chip, then it will show as YT9217
Note: if your device is not bricked, Make a full backup before trying another firmware.
I hope it helps. (donations are always welcome )
Memory dump:
firmware 20181222 HiFi: (Link) (thanks mazepa2000) (May 2019 update below)
Rooted TWRP firmware 20190523 HiFi: (Link)
Preloader (Boot_1) from other Similar Firmwares: (Link) <- Click again if it doesn't lead to the relevant post.
Download the one similar to your device's version.
Firmware via flash tool: Rooted TWRP 20190523 (Link) Thanks Maxkir
(You may need to remap side touch buttons in Factory settings (code 8888) -> Touch settings -> Click start -> Name of the button -> The button itself ->Repeat for all the buttons -> close -> ok).
Firmware for YT9213 Device: (Link) (Thanks pajurpl)
Update / Upgrade Files USB flash drive:
Firmware 20190522 HiFi: (Link) (Thanks foxgiggle , iSevenAuto)
Firmware 20190906: (Link)
MCU 3.1 (Link)(Thanks foxgiggle )
MCU 2.8 (Link) (Thanks lemmon and foxgiggle)
I hope it helps. (donations are always welcome )
Memory Dump Procedure via flashtool:
(Memory dump is only needed if you need full recovery from a backup. Otherwise you may only need to do the next part.)
Download and install MTK drivers. (Link)
Load scatter file and preloader (Link) in spflashtool. Press Ctrl Alt V , then go to Window and select "write memory". In file path select "user", in begin address put 0x0, In Region select the partition named "EMMC_USER". Hit Write memory. After that plug in the usb cable (connected to usb1 port). If the device is not detected, you need to power it on. If still not detected then you might need to short the two test points (see picture) (without power this time) and then plug in the usb cable. Remove the short when write process starts. Check if the issue is fixed. If its not fixed, then do the same to write boot2 and boot1 partitions as well. You may need to download Boot_1 specific to your original firmware from the link above.
Uploading Firmware (full or parts) via flashtool:
If you are uploading the firmware available in parts, you only need to upload "BOOTIMG" and "ANDROID" (SYSTEM).
You may also need to flash "RECOVERY". Remember to uncheck the preloader. Here is a nice instructions file. (Link) (thanks Maxkir)
There is more info and firmwares to chose from at 4pda forum.
Update / Upgrade Procedure via USB flash drive:
Copy the zip file (do not extract) to usb drive or microSD card, (formatted by SD Card Formatter). Connect to usb port 1 or 2. Go to Car Settings, System info. Click Android Upgrade.
--OR--
Extract the zip into a folder named XYAUTOUPG into the flash drive or microSD card, connect to usb port 1 or 2 and then reboot. Upgrade should start automatically. You might need to try with different USB drives or sd cards. For some reason this only works with certain usb and cards.
I hope it helps. (donations are always welcome )
MCU Upgrade Procedure via USB flash drive:
Extract the mcu file into flash drive or microSD card. Connect to usb port 1 or 2. Go into system info and update mcu.
Make a Full Backup/Memory Dump:
Open SPFlashtool, Select Memory Test Tab, Select only RAM Test (uncheck the rest), push start, and connect the unit. Save the information appeared, in a text file for later. (Read above "Memory dump procedure" for the usb connection setup).
Now go to ReadBack Tab, Double click on empty space next to tick mark, Select a folder where you want to store the dump file, and Type a name for the dump file you are going to creat, (ie. Boot_1, Boot_2, USER). Click Save. In next window "Readback block start address", select the region you want to make backup of (ie. EMMC_BOOT_1, EMMC_BOOT_2, EMMC_USER).
Start address is 0x0000000000000000
Length copy and paste from the text file you created earlier.
typically for Boot_1 and 2 the length is 0x0000000000400000
and for USER (16GB models) the length is 0x00000003a8000000
Click OK.
Now click on Readback and then connect the unit via usb cable. and Read process will start.
Do the same to make backup of all three partions. USER will take long time because its the largest partition.
RDS FM Radio:
Radio app with fixed RDS, channel names on buttons and HiFi: (Link) (thanks sjguk)
Copy to FMRadio directory /system/priv-app/FMRadio, rename to FMRadio.apk and change permission 764. (or 755 ?).
Channel name Editor: (Link) (thanks mclaught)
install as normal. You may need to install GalaPublicResources. Click top right dots.
I hope it helps. (donations are always welcome )
Multi Window Mode:
Go to root folder, look for build.prop. Open in text editor. Change the line ro.build.type=user to ro.build.type=userdebug.
If no such line is there, then simply add the line at the end. Save and exit. Go to Android settings, Developer options, look for multi window mode and enable it. Swipe down from the top of the window, Click on recent apps tile. You'll see the new multi window option there.
Subwoofer output Pin:
The default AUX_out pins are for mid range audio and is controlled by Mid slider in the mixer. The subwoofer output is on another pin (See Picture).
it is easy to remove one of the AUX_out pin and install it at the Sub output. this pin is controlled by Subw slider in the audio mixer.
Launchers UI1, UI2, UI4, UI5 (Link) (Thanks Maxkir)
Boot animation: (Resolution is 1024x600)
eg. (Link)
The animation preview didn't work for me, but I installed it anyway and it worked fine.
OBD Dongle Bluetooth Setting:
Open Bluetooth app, Click on settings, tap on the pin code "0000" and type in "1234" instead. Save settings.
Now search and connect the OBD dongle normally.
I hope it helps. (donations are always welcome )
Unit Specs:
motherboard marking YT9217 VER1.5 XY AUTO also 9218 VER2.4 XY AUTO near the antenna
Model no 8227L_demo android 8.1
Android YT9217C_00005_V003_20191402_HIFI
Kernel 3.18.22
DDR 1GB FLASH 16GB
CPU A7 1.3GHzx4
Amplifier AC7315 mos bile duct 45Wx4
AutoChip ARM AC8227L
Mediatek MT6323LGA
Kingston EMMC 16G
Im looking for the same ROM. Let me know if you find some info. Also Im looking for the AirRadio App. so I can use a Launcher.
Thanks
viktorsaari said:
the link takes me to the main page. and then its like finding needle in a haystack.
Click to expand...
Click to collapse
All relevant info about ROMs and flashing you can find in top header of this russian forum.
Look at the spoilers in the gray header layer and use Google translate to understand what is written there.
There are 3 ROM versions for the 8227L based head units. I downloaded and installed the oldest of the 3 (rooted and TWRP IMG included). Copy all files from the RAR to a flashdrive in root folder.
Turn off the head unit.
Connect the flashdrive to USB 1 slot of the head unit.
Turn on the the head unit.
The install process starts immediately after turning on.
It takes about 10 minutes.
When install process is ready, turn off the head unit.
Detach the flashdrive.
Turn on the head unit and it will boot with factory settings like a new device....
Note that there are also ROMs for flashing wit MTC flash tool downloadable.
But the versions for installing from USB sticks ( po russki - dla flashky) are more comfortable to install and I don't own a Windows pc. So this variant was my favorite method...
Regards and good luck...
Edit: if your unRAR program asks for a password for unpacking the RAR file, then use Eazy unRAR app from Playstore on your Android device - it ignores password lock in RAR file ...
Edit2: the 5th gray spoiler in the top header of the Russian forum hosts the links to the ROM RAR files...
The USB flash drive method didn't work for me, Device doesn't detect USB while booting up. I tried everything, connecting the test points, pushing reset button etc. to no avail.
SP flash tool does seem to work, I have tried uploading several available roms, only these three uploaded successfully,
full_8227L_demo-userdebug 6.0 MRA58K 1534513814 test-keys
Заводская прошивка под флештул от 09.11.2018 UI1 с переводом
20181224 TWRP ROOT перевод и эквалайзер от ноябрьской
but didn't turn on the device. Device turns on but I get a black (backlit) screen. What else is there to try?
bitstra said:
All relevant info about ROMs and flashing you can find in top header of this russian forum.
Look at the spoilers in the gray header layer and use Google translate to understand what is written there.
There are 3 ROM versions for the 8227L based head units. I downloaded and installed the oldest of the 3 (rooted and TWRP IMG included). Copy all files from the RAR to a flashdrive in root folder.
Turn off the head unit.
Connect the flashdrive to USB 1 slot of the head unit.
Turn on the the head unit.
The install process starts immediately after turning on.
It takes about 10 minutes.
When install process is ready, turn off the head unit.
Detach the flashdrive.
Turn on the head unit and it will boot with factory settings like a new device....
Note that there are also ROMs for flashing wit MTC flash tool downloadable.
But the versions for installing from USB sticks ( po russki - dla flashky) are more comfortable to install and I don't own a Windows pc. So this variant was my favorite method...
Regards and good luck...
Edit: if your unRAR program asks for a password for unpacking the RAR file, then use Eazy unRAR app from Playstore on your Android device - it ignores password lock in RAR file ...
Edit2: the 5th gray spoiler in the top header of the Russian forum hosts the links to the ROM RAR files...
Click to expand...
Click to collapse
No idea, what else you can try
If you can connect a PC to headunit and flashed a ROM with TWRP, may be you can use adb reboot recovery and clear data and cache via TWRP?
Hope you find a solution to boot your HU...
viktorsaari said:
The USB flash drive method didn't work for me, Device doesn't detect USB while booting up. I tried everything, connecting the test points, pushing reset button etc. to no avail.
SP flash tool does seem to work, I have tried uploading several available roms, only these three uploaded successfully,
full_8227L_demo-userdebug 6.0 MRA58K 1534513814 test-keys
Заводская прошивка под флештул от 09.11.2018 UI1 с переводом
20181224 TWRP ROOT перевод и эквалайзер от ноябрьской
but didn't turn on the device. Device turns on but I get a black (backlit) screen. What else is there to try?
Click to expand...
Click to collapse
No luck with adb either.
seems like my only option is if I could get the exact ROM for this device and flash it. The seller was less than helpful, so Aliexpress refunded me in full.
bitstra said:
No idea, what else you can try
If you can connect a PC to headunit and flashed a ROM with TWRP, may be you can use adb reboot recovery and clear data and cache via TWRP?
Hope you find a solution to boot your HU...
Click to expand...
Click to collapse
Received firmware files from seller, but its probably the update files, not the complete firmware. Unable to flash it via sp flash tool. (copy and paste the whole link until the .zip part)
http://download.seicane.com/doc/80/H5 Android 8.1 updated file.zip
Any ideas ???? my device is a brick at the moment, and doesn't recognise usb flash drive for updating.
Fixed.:victory:
Check the first post for detail.
So you flashed via sd card or flashtool?
viktorsaari said:
Fixed.:victory:
Click to expand...
Click to collapse
Hi How did you manage to fix it I have the same problem?
---------- Post added at 03:47 PM ---------- Previous post was at 03:46 PM ----------
viktorsaari said:
Received firmware files from seller, but its probably the update files, not the complete firmware.
http://download.seicane.com/doc/80/H5 Android 8.1 updated file.zip
Any ideas ???? my device is a brick at the moment, and doesn't recognise usb flash drive for updating.
Click to expand...
Click to collapse
The link is dead!
SP Flash tool.
ric69 said:
So you flashed via sd card or flashtool?
Click to expand...
Click to collapse
Thanks but flashtool is impossible to me as I don't have any USB recognition on my pc
Please see the original post, I added the things I did to fix it.
the link is not dead, copy and paste complete until the .zip part
anyway this zip file didn't help.
Check the first post for helpful material.
coffer said:
Hi How did you manage to fix it I have the same problem?
---------- Post added at 03:47 PM ---------- Previous post was at 03:46 PM ----------
The link is dead!
Click to expand...
Click to collapse
ric69 said:
Thanks but flashtool is impossible to me as I don't have any USB recognition on my pc
Click to expand...
Click to collapse
Did you get your connection to the PC yet?
---------- Post added at 03:28 PM ---------- Previous post was at 03:25 PM ----------
viktorsaari said:
Please see the original post, I added the things I did to fix it.
the link is not dead, copy and paste complete until the .zip part
anyway this zip file didn't help.
Check the first post for helpful material.
Click to expand...
Click to collapse
Thanks for that, wow the memory dump is massive more than 4Gb! Did you use format and download or just download in the Flash tool? Do you know the files the scatter file took from the memory dump? So, you didn't use any files from the first download where you took the scatter file from? I'm still having a problem connecting to my PC may have to use the hardware forced (testpoint) method!
You need usb male to male cable, attach it to usb1 on the device. but not yet connect to pc. Run the sp flash tool. and select the correct scatter file. Then run which ever function you need. after that connect the usb cable to pc while connecting these two test points (picture) with a small piece of wire to each other. After it is recognised and operation starts, you can release the jumper wire.
ric69 said:
Thanks but flashtool is impossible to me as I don't have any USB recognition on my pc
Click to expand...
Click to collapse
viktorsaari said:
You need usb male to male cable, attach it to usb1 on the device. but not yet connect to pc. Run the sp flash tool. and select the correct scatter file. Then run which ever function you need. after that connect the usb cable to pc while connecting these two test points (picture) with a small piece of wire to each other. After it is recognised and operation starts, you can release the jumper wire.
View attachment 4769616
Click to expand...
Click to collapse
Thanks, when I use the scatter file from the first download and put it with the files in the second download it only picks up the preloader file nothing else?
Hi, Scatter file is only needed to make sp flash tool recognise the partition table on the device. no need to download anything via scatter file. press Ctrl Alt V , then go to Window and select "write memory". Set start address to 0x00 Use this to write Boot_1 , Boot_2 and User, to EMMC_Boot_1, EMMC_Boot_2 and EMMC_User respectivly. thats it.
I hope it helps.
Thanks for that, wow the memory dump is massive more than 4Gb! Did you use format and download or just download in the Flash tool? Do you know the files the scatter file took from the memory dump? So, you didn't use any files from the first download where you took the scatter file from? I'm still having a problem connecting to my PC may have to use the hardware forced (testpoint) method!
Click to expand...
Click to collapse
Hi, yes, I fixed it. Check the first post for details.
NicoApple said:
Im looking for the same ROM. Let me know if you find some info. Also Im looking for the AirRadio App. so I can use a Launcher.
Thanks
Click to expand...
Click to collapse
Thanks but for most of us , we don't have any USB recognition to pc (or android devices) there is any sounds when plug
ric69 said:
Thanks but for most of us , we don't have any USB recognition to pc (or android devices) there is any sounds when plug
Click to expand...
Click to collapse
have you tried the test point method yet, I will try it tomorrow or Monday?
looking to root
ANDROID: F9212B_00020_V001
VERSION 9.1 CAR Edition
XYAUTO: F6.7 (X2)
CAN Pro: 3.7
DDR 1GB
FLASH 16 GB
MCU: 4.0 (X2)
Darthdub79 said:
looking to root
ANDROID: F9212B_00020_V001
VERSION 9.1 CAR Edition
XYAUTO: F6.7 (X2)
CAN Pro: 3.7
DDR 1GB
FLASH 16 GB
MCU: 4.0 (X2)
Click to expand...
Click to collapse
Have you had any luck with rooting this? I have the same unit and want to root it as well.
Search results for query: F9212B
forum.xda-developers.com
brody6104 said:
Have you had any luck with rooting this? I have the same unit and want to root it as well.
Click to expand...
Click to collapse
No
No
I have this unit also and am trying to get the touch screen to respond. has anyone verified the manufacturer? I'd like to just reload the system. I've done computer repair since the mid-90s but avoided android and IOS devices until now so I am now looking for open-source tool recommendations preferably tools that can be run off of a pc or laptop. any help or tips would be appreciated. Thanks!
I was able to get root on this, extract attached zip to root of flash drive (fat32 format is required) and attach it to the 4pin USB. Then short the F1 pin (next to the wifi antenna - see attached image to ground. You can also check the pin maps on the device for F1. Once you have it grounded, just reboot the device and it should flash twrp to the unit. Once you have twrp flashed, install terminal emulator and type "reboot recovery" and it should start twrp after which you can install magisk for root.
This files were tested on 1gb/16gb version from 4PDA.
I managed to kill all the gapps on my device and now android auto doesn't work with the ZLink app. If anyone can share the twrp back up of system apps folder.
Thanks for the guide, will try soon.
Did anyone share the system folder with you?
WW3 said:
I was able to get root on this, extract attached zip to root of flash drive (fat32 format is required) and attach it to the 4pin USB. Then short the F1 pin (next to the wifi antenna - see attached image to ground. You can also check the pin maps on the device for F1. Once you have it grounded, just reboot the device and it should flash twrp to the unit. Once you have twrp flashed, install terminal emulator and type "reboot recovery" and it should start twrp after which you can install magisk for root.
This files were tested on 1gb/16gb version from 4PDA.
I managed to kill all the gapps on my device and now android auto doesn't work with the ZLink app. If anyone can share the twrp back up of system apps folder.
Click to expand...
Click to collapse
Thanks a lot! It worked, had a different setup of the rear connectors but found the one that was the same.
hockeystar53 said:
Thanks a lot! It worked, had a different setup of the rear connectors but found the one that was the same.
Click to expand...
Click to collapse
hockeystar53 said:
Thanks a lot! It worked, had a different setup of the rear connectors but found the one that was the same.
Click to expand...
Click to collapse
Do you have the layout of what you used to root your headunit?
Yes, here's my layout.
There is only one male connector that corresponds to the picture by WW3.
hockeystar53 said:
Yes, here's my layout.
There is only one male connector that corresponds to the picture by WW3.
Click to expand...
Click to collapse
Thanks I'll try to do this myself
hockeystar53 said:
Yes, here's my layout.
There is only one male connector that corresponds to the picture by WW3.
Click to expand...
Click to collapse
Ok so I unplugged everything had the tweezers on the 2 pins plugged the power and USB plug back in and where do I go after that?
For 10 seconds? It didn't work the first time for me? Is the Flashdrive Fat32? Did you transfer the files to the flash drive? It should start automatically, follow the instructions to the letter.
hockeystar53 said:
For 10 seconds? It didn't work the first time for me? Is the Flashdrive Fat32? Did you transfer the files to the flash drive? It should start automatically, follow the instructions to the letter.
Click to expand...
Click to collapse
Did you unplug anything? Yes the flash drive is formatted
Yes, everything unplugged.
Then connect the two pins with the tweezer, then insert the USB cable with your flash drive in it, then insert the power cable while still holding the tweezer in place and continue to hold it for atleast 10 seconds after you have inserted the power cable. Hope that helps.
Ok...I must be connecting the wrong 2 pins
hockeystar53 said:
Yes, everything unplugged.
Then connect the two pins with the tweezer, then insert the USB cable with your flash drive in it, then insert the power cable while still holding the tweezer in place and continue to hold it for atleast 10 seconds after you have inserted the power cable. Hope that helps.
Click to expand...
Click to collapse
Which connector you put the tweezers on cause my setup is similar to yours
Sorry for the bump, why do you want to root it in first place?