Related
I recently bought a generic android head unit from Ali Express. It actually works well but I really need to connect it to a CAN bus and write some additional software (background: I want to replace the factory unit in a Nissan Leaf, so it needs to display some vehicle info, show the heater settings and set up the charge timer). I have experience in Android app development and embedded Linux, but I'm still a 'noob' when it comes to Android hacking (root access etc).
I'm pretty sure I will need root access to do what I want. It has 'CAN tx / rx' pins on the back, and I am pretty sure they are wired to one of the serial interfaces internally (I will need an adapter to convert UART to CAN as well). I played around with an app to access the serial ports (i.e. ttyxxx) but I didn't have permission to use many of them - probably the ones I wanted!
I don't want to re-write the existing music player, amp control and radio; I just want to add a new app to carry out my vehicle-specific functions.
I tried the root process given here but it didn't work.
Here are the device details:
Model: S07
MCU Version: MTCB-HA-V2.60
Android Version: 4.4.4_01062015
Kernel Version: 3.0.36+ [email protected] #278
CPU: ARM7 1.6G x 2
CPU/SOC is an RK3066 on a modular board. Pictures attached.
It doesn't have any physical buttons except reset - there are touch sensitive buttons for power, back and volume. It has one SD card slot for map data and no USB on the front (several on the back).
I haven't figured out how to get to the recovery console, or connect it to a PC via USB.
Any suggestions for how to root? Or get to recovery console?
Anyone else with a similar device?
Check out the Huefi thread above. It has everything you need. first page covers root. basically, download the rom you want, put it on the GPS SD card, insert it, and wait for it to ask you to update. Once you do that, it will be rooted. there is no other way to root it if it has 4.4.4. DO NOT INSTALL A MCU file for it unless it is for HA devices. HA is the manufacture of the unit, and if you use an MCU file for a different device, you run the risk of loosing the physical buttons on the unit. This can be repaired by going into recovery and flashing the HA MCU, but that is a lot of extra work
Hi! Thanks for your reply.
I was wary about installing a new image because I don't want to lose the existing radio app and amplifier controls (which are specific to the device rather than the RK3066 SOC module, if I have understood the structure correctly).
* Would a new image replace these apps, or are they actually in the MCU firmware anyway?
* Can I back up my current image first? I looked at some backup tools, but they all needed root access... =Catch 22.
Sorry for noob questions... I'm getting the hang of Linux but still new to messing with Android at a low level. I'd love to play around with a stripped Ubuntu or similar on the device, but I don't want to have to write my own software for the radio parts - at least not yet.
BTW do you know how the bootloader system works? Is it possible to boot from SD card or USB (therefore allowing some other OS to be booted without replacing the onboard image)?
MayfairDROID said:
Check out the Huefi thread above. It has everything you need. first page covers root. basically, download the rom you want, put it on the GPS SD card, insert it, and wait for it to ask you to update. Once you do that, it will be rooted. there is no other way to root it if it has 4.4.4. DO NOT INSTALL A MCU file for it unless it is for HA devices. HA is the manufacture of the unit, and if you use an MCU file for a different device, you run the risk of loosing the physical buttons on the unit. This can be repaired by going into recovery and flashing the HA MCU, but that is a lot of extra work
Click to expand...
Click to collapse
jcolebaker said:
Hi! Thanks for your reply.
I was wary about installing a new image because I don't want to lose the existing radio app and amplifier controls (which are specific to the device rather than the RK3066 SOC module, if I have understood the structure correctly).
* Would a new image replace these apps, or are they actually in the MCU firmware anyway?
* Can I back up my current image first? I looked at some backup tools, but they all needed root access... =Catch 22.
Sorry for noob questions... I'm getting the hang of Linux but still new to messing with Android at a low level. I'd love to play around with a stripped Ubuntu or similar on the device, but I don't want to have to write my own software for the radio parts - at least not yet.
BTW do you know how the bootloader system works? Is it possible to boot from SD card or USB (therefore allowing some other OS to be booted without replacing the onboard image)?
Click to expand...
Click to collapse
I cant help with the bootloader issues, but I can with some of the others:
-Radio and Amplifier apps are the same on all units, or should I say is compatible across all units. If you were to go into the settings, then factory settings and enter 126 as the password, you can see all the settings you need to make sure your unit functions after upgrading your rom image.
-You can not back up your factory image. its not possible. You can always reach out to your seller and ask them if they will send you a copy of the factory firmware.
MayfairDROID said:
I cant help with the bootloader issues, but I can with some of the others:
-Radio and Amplifier apps are the same on all units, or should I say is compatible across all units. If you were to go into the settings, then factory settings and enter 126 as the password, you can see all the settings you need to make sure your unit functions after upgrading your rom image.
-You can not back up your factory image. its not possible. You can always reach out to your seller and ask them if they will send you a copy of the factory firmware.
Click to expand...
Click to collapse
SUCCESS! I just downloaded and installed the latest image from Malaysk (I think?) and it looks like it is working well! Radio, music player and amplifier work, and I have root access. Woo! So far so good... Thanks!
Hello Friends, I read your post. Like anything happens
I want to update my Car Stereo Radio Head Unit
Here are the device details:
Model; S07
MTCB-JY-v2.44
MAR 24 2015 9:46:14
ANDROID VERSION 4.4.4_25032015
kernel version
3.0.36+
ROOT @ UBUNTU # 766
Build number
rk3066.eng4.4.4 25032015.13: 08: 43
CPU
arm7 1.6 GHz (x2)
But that is not the screen resolusion 880 // 1024
Knowing that I have to Huifei / KGL, Klyde, or RoadMaster
Thank
aribetty7811 said:
Hello Friends, I read your post. Like anything happens
I want to update my Car Stereo Radio Head Unit
Here are the device details:
Model; S07
MTCB-JY-v2.44
MAR 24 2015 9:46:14
ANDROID VERSION 4.4.4_25032015
kernel version
3.0.36+
ROOT @ UBUNTU # 766
Build number
rk3066.eng4.4.4 25032015.13: 08: 43
CPU
arm7 1.6 GHz (x2)
But that is not the screen resolusion 880 // 1024
Knowing that I have to Huifei / KGL, Klyde, or RoadMaster
Thank
Click to expand...
Click to collapse
Hi, I also didn't know the screen resolution, and it is not mentioned on the "About" screen.
In the settings menus, I found some options for recording a video of the display (I don't know why!) and the maximum resolution there was 1024 x 600. I figured that you wouldn't bother to record at higher res than the screen had, so the resolution must be 1024x600. This seemed to work!
My stereo has absolutely NO branding on it anywhere so I don't know whether it's a clone of Huifei or something else, but it worked with the "Malaysk" firmware, which I downloaded from the Huifie file repository (linked from here), under firmware->Malaysk ROM->Malaysk DualCore RK3066).
I picked the bottom one (12th Jun 15, 1024x600 with different launcher).
jcolebaker said:
Anyone else with a similar device?
Click to expand...
Click to collapse
I just installed the same unit. Only complaints are streaming music via Bluetooth only works if you open up the Bluetooth app (probably because android doesn't act as a Bluetooth sink). The other issue is, I cannot seem to change the brightness of the screen...its a touch too dim for daylight (I have a convertible) and a bit too bright for nighttime.
Glad to see you got a custom rom working.
Hey jcolebaker, do you think you could post what the LCD model number is? Is it a Hannstar HSD070IFW1-A?
Sent from my Nexus 6 using Tapatalk
vdubskey said:
Hey jcolebaker, do you think you could post what the LCD model number is? Is it a Hannstar HSD070IFW1-A?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Sorry not sure what the LCD is - I don't want to pull it apart. It has a board on the back which has the following on it:
BL-TFT-V2.2(HCT)
That's soldered to another board that says:
P/N:BL-7inch-7000-KB-V00 20150311
Update question
Do I burn the update.img file to the sd card or do I simply copy it? And does it have to be my gps sd card or can it be a spare blank one?
Thanks
---------- Post added at 11:06 PM ---------- Previous post was at 10:42 PM ----------
dovoto said:
Do I burn the update.img file to the sd card or do I simply copy it? And does it have to be my gps sd card or can it be a spare blank one?
Thanks
Click to expand...
Click to collapse
Doesn't appear to be an img file in the context of "burn it" so I think that answers that question (just copy it) The head unit doesn't seem to do anything when I drop it in though (either with it on when I insert it or with it already inserted during a reset). Any thoughts?
dovoto said:
Doesn't appear to be an img file in the context of "burn it" so I think that answers that question (just copy it) The head unit doesn't seem to do anything when I drop it in though (either with it on when I insert it or with it already inserted during a reset). Any thoughts?
Click to expand...
Click to collapse
The file should be "update.zip". I used a new SD card - try formatting one with FAT32.
You just copy it to the card and insert it - I think the stock Android image automatically checks for update files that look like this, and loads them. This process worked OK for me - if not then hopefully someone here knows more about the update process than me.
HI !
I also try to root my 2din android without success... I have the same as your and I fail to get recovery and the android can't detect the update.img (or update.zip)
I have tried many tips, my sd card is in fat32, well detected by android ...
Do you have the tip to access to the recovery ?
Thanks
Logicsystem360 said:
HI !
I also try to root my 2din android without success... I have the same as your and I fail to get recovery and the android can't detect the update.img (or update.zip)
I have tried many tips, my sd card is in fat32, well detected by android ...
Do you have the tip to access to the recovery ?
Thanks
Click to expand...
Click to collapse
I think the file is "update.img" not "update.zip". Anyway I have not figured out how to get to the boot loader on mine, and I never got any recovery console. Sorry I am too much of a beginner myself to suggest anything.
HI !
I also try to root my 2din android without success... I have the same as your and I fail to get recovery and the android can't detect the update.img (or update.zip)
I have tried many tips, my sd card is in fat32, well detected by android ...
Do you have the tip to access to the recovery ?
Thanks
Click to expand...
Click to collapse
Instead of flashing a new image, go to the factory settings and type in *#hct#root#
This should give you root, no need to flash a new image
Logicsystem360 said:
HI !
I also try to root my 2din android without success... I have the same as your and I fail to get recovery and the android can't detect the update.img (or update.zip)
I have tried many tips, my sd card is in fat32, well detected by android ...
Do you have the tip to access to the recovery ?
Thanks
Click to expand...
Click to collapse
Bonjour.
If you would like more than root and you're still having trouble getting into recovery with your Hot Audio RK3066 1024x600 2 DIN Head Unit, the steps below have worked for me when the system does not automatically detect the mcu or update.img.
*** Prior to flashing any OEM or Custom ROM firmware, I recommend using a backup app like Titanium to save all your existing apps and data to your external micro sd card or usb memory stick.
1) Install Quick Boot or a similar apk from the play store.
2) Attach a wireless usb or usb keyboard and confirm it is working as intended. I use a Lenovo N5902 but most usb or wireless usb keyboards should work for this task.
3) Make sure you have the update and or mcu image file on your gps micro sd card or an attached usb memory stick (not the zip file).
4) Open Quick Boot, select recovery, and the system will shut down and boot into recovery.
5) Use your usb keyboard to scroll or arrow down to the update option with correct img file location, then press enter to execute the mcu or android firmware update or both.
6) After you update the android firmware, it is highly recommended that you go into the Settings > Backup & Reset, and select reset to factory and check the box to delete all data from the internal sd card. This reset to factory and internal sd card wipe should give your updated android system a clean start and help avoid system issues due to left over data from the previous firmware.
7) Delete the mcu and or update image from your external micro sd card. Done.
Hope this helps...
Best to all,
R
wrong thread. sorry
Android dvd s07 update
Hi,
I want update my android car dvd mercedes w203 2006
MCU version: MTCB-KGL-V2.80
Android version:
4.4.4._07012016
3.0.36+
[email protected] #2321
I need files to update, please help
Has anybody managed to root android caska 4.4.2?
Thanks
Anyone?
It says:
mcu: v3.00h7_ca712_f7e1430
kernel: 3.0.36+
android 4.4.2
Thanks
Also looking for a way to root this HU too.
Why don't you just flash Malaysk's ROM? It's easier and the ROM is much smoother than stock.
War-Rasta said:
Why don't you just flash Malaysk's ROM? It's easier and the ROM is much smoother than stock.
Click to expand...
Click to collapse
I've never used Android, I'm a iOS user and very afraid to brick my unit. I just download ROM for 4.4.2 and boot it according to the instructions?
My unit shows:
MCU Version: V3.00F8_CA380_E55B_ECI1455
Build number: D200 Ver2.01 20141228.2309
TCON Version: V6.00_HSD80_EC28e
Many thanks for your help!
War-Rasta said:
Why don't you just flash Malaysk's ROM? It's easier and the ROM is much smoother than stock.
Click to expand...
Click to collapse
I actually tried a Malaysk's rom and It gave me error in the middle of installation. I had to return the original rom. Not quite sure if I used the correct malaysk's rom. I have a rk3066 android. 4.4.2
Hi Guys,
I also have a similar unit. Did you manage to make a backup of current image? I want to upgrade because I have two issue: sometimes the unit doesn't complete the startup and I can't use sygic navigator.
Build number: D200-20150713.2225-S1
Kernel version:3.0.36+
[email protected] #883
Tue Jul 7 10:43:52 CST 2015
MCU Version:V3.00H7_CA712_F7E1430
TCON Version:V6.00_HSD70_F77Hi
Media Version:89J_0025_000000
SN Number:UNKNOWN
Bluetooth Version:I50E_ADK.HBS.0.20150521.1
Hardware Version:TFT:EC2_EBT
MB:EC2_D1S
MD: DE5GM_R82_TE6K
Best regards,
lmcoelho said:
Hi Guys,
I also have a similar unit. Did you manage to make a backup of current image? I want to upgrade because I have two issue: sometimes the unit doesn't complete the startup and I can't use sygic navigator.
Build number: D200-20150713.2225-S1
Kernel version:3.0.36+
[email protected] #883
Tue Jul 7 10:43:52 CST 2015
MCU Version:V3.00H7_CA712_F7E1430
TCON Version:V6.00_HSD70_F77Hi
Media Version:89J_0025_000000
SN Number:UNKNOWN
Bluetooth Version:I50E_ADK.HBS.0.20150521.1
Hardware Version:TFT:EC2_EBT
MB:EC2_D1S
MD: DE5GM_R82_TE6K
Best regards,
Click to expand...
Click to collapse
By your username I assume you're brazilian, right?
Where did you buy your unit?
This night I've managed to talk to a Caska sales director for LATAM and he said that they cannot give the stock ROM for security reasons. I still have problems with the clock and the startup also (blank screen). They say their engineering team is working on fixing that issue, but China has a holiday that starts today (Oct 1st.) and only ends Oct 7th. So I'll only have an answer after that day.
Maybe you can talk to your seller and see if he gives any support (I bought mine at www.rcmultimidias.com.br).
Sure I am, you are right.
I bought mine from aliexpress. I found a update.img file in some folder, but I'm not sure if it is the full image. I opened that image in a linux box and looks like we have everything, there some ext4 images, boot image and a lot of other files, but I'm not 100% sure about it. May be somebody with experience could verify that.
Another annoying thing is the music and video apps not reading files from sdcard, they only read USB and inand. I've modified the Music app to point it to the correct path, but I couldn't install it back to the unit (It fails to install without any error). At least if I could reassign music and video buttons to another app, that would be ok (VLC is working fine, just need to adjust volume).
purchio said:
By your username I assume you're brazilian, right?
Where did you buy your unit?
This night I've managed to talk to a Caska sales director for LATAM and he said that they cannot give the stock ROM for security reasons. I still have problems with the clock and the startup also (blank screen). They say their engineering team is working on fixing that issue, but China has a holiday that starts today (Oct 1st.) and only ends Oct 7th. So I'll only have an answer after that day.
Maybe you can talk to your seller and see if he gives any sup.
Click to expand...
Click to collapse
Guys. I am also brazilian and I bricked my unit. They sent my the original update.img and sad to put a update.txt file on sdcard and boot. But I can not boot. Any idea?
Thanks
danylam said:
Guys. I am also brazilian and I bricked my unit. They sent my the original update.img and sad to put a update.txt file on sdcard and boot. But I can not boot. Any idea?
Thanks
Click to expand...
Click to collapse
Normally you have to boot in recovery mode, something that I still don't know how to do for this unit, and then use that update.img to restore. See this thread http://forum.xda-developers.com/showthread.php?t=2660662, there some possible procedures there and may be one of them work for the caska.
How big is the update.img file they sent to you?
lmcoelho said:
Normally you have to boot in recovery mode, something that I still don't know how to do for this unit, and then use that update.img to restore. See this thread http://forum.xda-developers.com/showthread.php?t=2660662, there some possible procedures there and may be one of them work for the caska.
How big is the update.img file they sent to you?
Click to expand...
Click to collapse
Yeah. I have tried everything but could not boot. It is just a blank screen.
Here you go with the update.img.
https://www.sendspace.com/file/mjkgfj
Here I posted a video with all the problems I'm experiencing with this unit. The main problem is that I cannot setup the right time, so all Android apps are useless (they require a secure connection to their servers and this is only allowed with a valid certificate [that needs the correct date]).
I was trying to root my unit so that I could use ClockSync to fix the time every 30 seconds (it resets after 1 minute), but had no success on that.
https://www.youtube.com/watch?v=tWWCP9tAYm4
danylam said:
Guys. I am also brazilian and I bricked my unit. They sent my the original update.img and sad to put a update.txt file on sdcard and boot. But I can not boot. Any idea?
Thanks
Click to expand...
Click to collapse
Hi!
So, where did you managed to talk to Caska? I've tried contact with Caska Brasil with no success (they say they do not offer support for Android units), and Caska Global didn't give any answer ([email protected]).
I've downloaded your update.img, but it's for CA712 and my unit is a CA380-XLA, I'm afraid to brick it. Have you tried entering recovery mode pressing reset and power buttons the same time?
lmcoelho said:
Sure I am, you are right.
I bought mine from aliexpress. I found a update.img file in some folder, but I'm not sure if it is the full image. I opened that image in a linux box and looks like we have everything, there some ext4 images, boot image and a lot of other files, but I'm not 100% sure about it. May be somebody with experience could verify that.
Another annoying thing is the music and video apps not reading files from sdcard, they only read USB and inand. I've modified the Music app to point it to the correct path, but I couldn't install it back to the unit (It fails to install without any error). At least if I could reassign music and video buttons to another app, that would be ok (VLC is working fine, just need to adjust volume).
Click to expand...
Click to collapse
I can reassign the screen buttons in my unit. In the settings, go to the last menu: "Shortcuts". Not sure if there's a way to reassign the physical buttons without modifying the original ROM.
danylam said:
Yeah. I have tried everything but could not boot. It is just a blank screen.
Here you go with the update.img.
Click to expand...
Click to collapse
I'm newbie as well, but I know that you must need possible clue, since you brick your unit. I'm afraid to point you to the wrong direction, but I believe it deserves to try. I saw some threads discussing about the bootloader and connect via USB. Looks like to have to install the usb driver for the rock chip (RK3066, since it is dual core and there is a file RK3066Loader_uboot_upgrade2_4_16gok.bin in the update.img file). I don't have more details on that, but may dig deeper.
lmcoelho said:
I'm newbie as well, but I know that you must need possible clue, since you brick your unit. I'm afraid to point you to the wrong direction, but I believe it deserves to try. I saw some threads discussing about the bootloader and connect via USB. Looks like to have to install the usb driver for the rock chip (RK3066, since it is dual core and there is a file RK3066Loader_uboot_upgrade2_4_16gok.bin in the update.img file). I don't have more details on that, but may dig deeper.
Click to expand...
Click to collapse
I've tried pluggin a USB to the unit and connecting it to my PC with no success, no devices are recognized. I have developer mode active but no options to enable USB Debugging.
So, I was able to extract all APKs from the file danylam hosted, and it's quite different from my unit: I have only one "Settings" menu, and in my unit some essential apps weren't installed (like HBS_Carkit_ChangeLogoUtil.apk and HBS_Carkit_SyncGPSTime.apk). I've installed them and solved one of my problems: car starting with a GMC logo. But the SyncGPSTime.apk isn't being called by any applications, so it's not starting (and I cannot start from itself).
Then I tried installing the Settings.apk that came with the ROM and ended up with a non functional setup menu, unfortunately. Since in that version most settings are changed from the "Android Settings", and I couldn't install that apk (it shows me an unknown error), I've lost some essential menus.
danylam said:
Guys. I am also brazilian and I bricked my unit. They sent my the original update.img and sad to put a update.txt file on sdcard and boot. But I can not boot. Any idea?
Thanks
Click to expand...
Click to collapse
purchio said:
So, I was able to extract all APKs from the file danylam hosted, and it's quite different from my unit: I have only one "Settings" menu, and in my unit some essential apps weren't installed (like HBS_Carkit_ChangeLogoUtil.apk and HBS_Carkit_SyncGPSTime.apk). I've installed them and solved one of my problems: car starting with a GMC logo. But the SyncGPSTime.apk isn't being called by any applications, so it's not starting (and I cannot start from itself).
Then I tried installing the Settings.apk that came with the ROM and ended up with a non functional setup menu, unfortunately. Since in that version most settings are changed from the "Android Settings", and I couldn't install that apk (it shows me an unknown error), I've lost some essential menus.
Click to expand...
Click to collapse
Hi,
The only way to talk to caska global is using skype (coagent,service). Normally they are online at 9pm (Sao Paulo time).
lmcoelho said:
I'm newbie as well, but I know that you must need possible clue, since you brick your unit. I'm afraid to point you to the wrong direction, but I believe it deserves to try. I saw some threads discussing about the bootloader and connect via USB. Looks like to have to install the usb driver for the rock chip (RK3066, since it is dual core and there is a file RK3066Loader_uboot_upgrade2_4_16gok.bin in the update.img file). I don't have more details on that, but may dig deeper.
Click to expand...
Click to collapse
Can you tell me how to extract this bin file from the image?
Thanks
purchio said:
I've downloaded your update.img, but it's for CA712 and my unit is a CA380-XLA, I'm afraid to brick it. Have you tried entering recovery mode pressing reset and power buttons the same time?
Click to expand...
Click to collapse
I found the update.img in my CA712 with a simple search for update.img. I used the file browser and and did the search from / device.
---------- Post added at 10:59 AM ---------- Previous post was at 10:40 AM ----------
danylam said:
Can you tell me how to extract this bin file from the image?
Thanks
Click to expand...
Click to collapse
This is the linux tool to open the image http://forum.xda-developers.com/showthread.php?t=2257331
command:
Code:
./imgrepackerrk update.img
It creates a update.img.dump folder and the bin file should be in the update.img.dump/Image
Boot.img is compressed and if you want to see content do this:
Code:
mkdir boot
cd boot
gzip -cd ../boot.img | cpio -i -
lmcoelho said:
I found the update.img in my CA712 with a simple search for update.img. I used the file browser and and did the search from / device.
Click to expand...
Click to collapse
Tried searching mine but couldn't find any *.img files. But at least I've managed to uninstall the CA712 settings from my unit and revert to the original one.
Looks like your unit is a little bit different from mine.
Hello I need help, by mistake I flashed SP_Flash_Tool a version that in the end was incompatible with my AC8227 YT9216B with what remained brick.
I am trying to recover it with versions that download YT9217 and YT9218 but it is known that they are very different from the version that I had the YT9216B_00002_v004_20190530 and by means of USB bridging the test point close to negative but even though the program SP_Flash_Tool- 5.1916 always ends with failure 4032 or 5054 both related to the DMRAM.
There would be someone in the forum that could help me indicating where to find the link to download my ROM? I have already reviewed the month of 400 pages of the 4PDA forum and I did not find it.
I believe this (Link) is the version you are looking for. Its a memory dump. If you need help flashing it, follow the instruction here. Error 4032 means you are not using correct scatter file. and 5054 means there is not correct preloader file to go with the scatter. You can try the one I have shared, or copy the 2 files from other similar firmwares offered at 4pda
I hope it helps.
lmmerono said:
Hello I need help, by mistake I flashed SP_Flash_Tool a version that in the end was incompatible with my AC8227 YT9216B with what remained brick.
I am trying to recover it with versions that download YT9217 and YT9218 but it is known that they are very different from the version that I had the YT9216B_00002_v004_20190530 and by means of USB bridging the test point close to negative but even though the program SP_Flash_Tool- 5.1916 always ends with failure 4032 or 5054 both related to the DMRAM.
There would be someone in the forum that could help me indicating where to find the link to download my ROM? I have already reviewed the month of 400 pages of the 4PDA forum and I did not find it.
Click to expand...
Click to collapse
viktorsaari said:
I believe this (Link) is the version you are looking for. Its a memory dump. If you need help flashing it, follow the instruction here. Error 4032 means you are not using correct scatter file. and 5054 means there is not correct preloader file to go with the scatter. You can try the one I have shared, or copy the 2 files from other similar firmwares offered at 4pda
I hope it helps.
Click to expand...
Click to collapse
Thank you very much for your help, I will try it immediately to see if with a little luck and your copy of the firmware convinces my computer and starts once and for all, although I do not have too much hope, but anyway, we will try achieve.:good
Nothing, still the same, error 4032 put it as you put it.
Connected to a 12V source the screen starts in a blue color and there is no change unless the reset button is pressed, I don't know if that can indicate any other fault such as that the MCU memory had been erased or corrupted and that is why he does not stop doing anything but the question is that following the procedure for the use of the "test point" step by step always cindependently of using a flash tool or another, of using different scatter files or firm YT9216 / 17/18, B, Whatever the question is, always, always the blissful error 4032 above all.
I don't know what to do, any suggestion is accepted even if it is to use a hammer as a tool.
did you try the scatter and preloader from my post?
viktorsaari said:
did you try the scatter and preloader from my post?
Click to expand...
Click to collapse
yes both and in different ports of the PC (windows10)
the error you have described is only the wrong scatter and preloader file. its only a matter of finding the correct one. I also found the scatter that worked from a different firmware(the firmware didnt work but only the scatter did) , and installed different firmware. It might be possible for you to extract original scatter from the device using MTK droid tools.
lmmerono said:
yes both and in different ports of the PC (windows10)
Click to expand...
Click to collapse
viktorsaari said:
the error you have described is only the wrong scatter and preloader file. its only a matter of finding the correct one. I also found the scatter that worked from a different firmware(the firmware didnt work but only the scatter did) , and installed different firmware. It might be possible for you to extract original scatter from the device using MTK droid tools.
Click to expand...
Click to collapse
Thanks, I found about 20 scatter files between AC8227_Android_scatter and MT3367_Android_scatter, I have about 10 preloader_8227l_demo_ (Preloader) and another 15 different SP_Flash_Too.
I will have to arm myself with patience and try different combinations (so far I have tried more than 50 with the same result, the always present ERROR (4032).
We'll see if I get it or give up before, the ideal is that somewhere the files were found together and that they were already successfully tested but that would be daydreaming.:crying:
Another possible solution would be to enter the way that I would recognize a USB Flash drive with an XYAUTOUPG file or whatever I had tried with it but since this brick after pressing the reset it still does not know.
wow, I'm impressed by your patience
I also downloaded many files from the Russian forum. One of the problems I faced is if the folder name contains some Russian characters, the flashtool gives similar errors. Also some suggested, removing first 4 lines from the scatter file helps in some cases.
I remember I also had disappointments first. Many times I packed everything up and put in storage, but then brought it back for further testing. and one day I got lucky. Hopefully you too will fix it soon.
lmmerono said:
Thanks, I found about 20 scatter files between AC8227_Android_scatter and MT3367_Android_scatter, I have about 10 preloader_8227l_demo_ (Preloader) and another 15 different SP_Flash_Too.
I will have to arm myself with patience and try different combinations (so far I have tried more than 50 with the same result, the always present ERROR (4032).
We'll see if I get it or give up before, the ideal is that somewhere the files were found together and that they were already successfully tested but that would be daydreaming.:crying:
Another possible solution would be to enter the way that I would recognize a USB Flash drive with an XYAUTOUPG file or whatever I had tried with it but since this brick after pressing the reset it still does not know.
Click to expand...
Click to collapse
viktorsaari said:
wow, I'm impressed by your patience
I also downloaded many files from the Russian forum. One of the problems I faced is if the folder name contains some Russian characters, the flashtool gives similar errors. Also some suggested, removing first 4 lines from the scatter file helps in some cases.
I remember I also had disappointments first. Many times I packed everything up and put in storage, but then brought it back for further testing. and one day I got lucky. Hopefully you too will fix it soon.
Click to expand...
Click to collapse
Thanks for your help but I don't get results on the other hand, the test point disappeared from using it so much, it was deleted and since the processor does not have the pins in the air it can no longer even be tried.
I do not know if there is another test point or one that could help for the purpose that is sought and is: to start this brick.
On the main board, from where there would be a SIM socket, there is a connector that could appear to be a USB socket to be used by the Technical Service in the commissioning of the newly assembled ones.
Anyway, I just want to be able to recover my radio.
Thanks for your help.
Hello my friend I hope you upload the file again, YT9216B_00002_v004_20190530 * Thank
viktorsaari said:
I believe this (Link) is the version you are looking for. Its a memory dump. If you need help flashing it, follow the instruction here. Error 4032 means you are not using correct scatter file. and 5054 means there is not correct preloader file to go with the scatter. You can try the one I have shared, or copy the 2 files from other similar firmwares offered at 4pda
I hope it helps.
Click to expand...
Click to collapse
Hello my friend
I hope you upload the file again,
YT9216B_00002_v004_20190530
* Thank you
imr088888 said:
Hello my friend
I hope you upload the file again,
YT9216B_00002_v004_20190530
* Thank you
Click to expand...
Click to collapse
Not exactly the same date but this will work. Just a newer update with root and TWRP
Firmware YT9216B_00002_V004_20190826 (UI1) ROOT, TWRP, translation. (1/16)
https://drive.google.com/file/d/132kkj5neExIr9UufZIgAqeEu67JSVtu3/view
Hi my friend, I could not update, I put the update in usb and the update did not show me, is there a certain way to install?
Hi there I exausted the whole xda and russian forum for something that can work..
exausted different forums.... and tryd a lot of firmware and methods...
I did about the same I am afraid.... no backup and now black screen on startup and no connection to usb no more......
yesterday it still connected to my laptop....you could hear it connect in windows but i couldnt get anything to load on it... all sorts of errors in Flash tool....
eventually i I Did manage to download the preloader onto ny headunit from firmware I found in this post....
I found out that I had to use this order: I would connect my usb... click download in Flashtool then it starts... and I switch on the power of my head unit.... and it completed the upload of the preloader..... So i finally thought Yessssss now install the rest of the firmware.... but after this I had no connection with my head unit... it doesnt find it anymore trough USB.....
but after that I installed that preloader file... I can no longer get any connection no more to my hu....
please help me out.... I also did read some stuff that you need to connect or push 3 spots togheter on youre pcb...?? does anyone got more information or a clear foto of wich and how I connect these 3 spots?
Or maybe now a way I can unbrick my device or have correct software for me??
Ive been trying to fix it 4 3 days in a row now... but I am about to go insane
System information I found in factory settings when the unit was still stock and untouched:
YT9216B_00002_V004_20190708
kenel: 3.18.22
Flash:16G
CPU:A7 1.3 GHz x 4
Display 1024 * 600
MCU1: HW8227L-3.3-SW0-3.1
Inide when i open it op the sticker on the connectors on the pcb tells me:
YT9216B Vo.1 16C
A.005-YT9216B004
20200214
And here is the information of the store i bought it from in the original advertisement:
Specifications on website:
● System:Andriod 8.1
● Model:SU 9701
● Radio Chip:QN8035
● Software:8227L
● Type:Android navigation MP5
● Size:7 Inch
● Bluetooth:Bluetooth 4.0
● Resolution:1024*600
● Audio Amplifier:TDA7388
● Voltage:12V
● Power Output:60W
● Memory:1G+16G
● Audio format:MP3/WMA/WA/OGG/FLAC/APE
● Video format:RM/RMVB/MP4/FLV/MKV/3GP/AVIASF/SWFMP1
● Image foramt:JPG
● FM Range:FM 87.5~108MHz
● Operating temperature:-10℃ ~ +60℃
● USB Interface:USB 2.0
● Product Size:188mm*58mm*165mm
● Weight:1922g
● Button: Physical button/Reset button
● Factory password:1111
My apologies for my bad English (not my native language).
Hope you guys can help me unroot it...
martinique78 said:
Not exactly the same date but this will work. Just a newer update with root and TWRP
Firmware YT9216B_00002_V004_20190826 (UI1) ROOT, TWRP, translation. (1/16)
https://drive.google.com/file/d/132kkj5neExIr9UufZIgAqeEu67JSVtu3/view
Click to expand...
Click to collapse
I have this radio version and I can't update it. I tried USB update with a flash pen USB and gave me an error. I tried with SP flash and gave me error 4032 with the test points method... I don't know what can I do more.
DFC said:
I have this radio version and I can't update it. I tried USB update with a flash pen USB and gave me an error. I tried with SP flash and gave me error 4032 with the test points method... I don't know what can I do more.
Click to expand...
Click to collapse
I gave up on this junk radio a while ago...worked for a few days then it just went blank and got really hot so i pulled it out. Now it sits in a box in pieces.
My radio looks like a PODOFO, It's a YT9216B_00002_v004_20190826 firmware but aida64 show yt9218B.
I tried some methods, nothing worked. I tried to update via Android update, flash with USB with SP flash, flash with USB pen and sd card, without success .I decided to try again. Can someone help me, and on first place tell me what is the correct firmware for this device? And a full tutorial step by step (without shortcuts)? or some tip that can help me?
yt9216b
hello can you help me please me send new rom
thank you
YT9216B?
morio005 said:
hello can you help me please me send new rom
thank you
Click to expand...
Click to collapse
Hi, I wanted to know if this version of the radio was updated? Thank you
Renstaman said:
Hi there I exausted the whole xda and russian forum for something that can work..
exausted different forums.... and tryd a lot of firmware and methods...
I did about the same I am afraid.... no backup and now black screen on startup and no connection to usb no more......
yesterday it still connected to my laptop....you could hear it connect in windows but i couldnt get anything to load on it... all sorts of errors in Flash tool....
eventually i I Did manage to download the preloader onto ny headunit from firmware I found in this post....
I found out that I had to use this order: I would connect my usb... click download in Flashtool then it starts... and I switch on the power of my head unit.... and it completed the upload of the preloader..... So i finally thought Yessssss now install the rest of the firmware.... but after this I had no connection with my head unit... it doesnt find it anymore trough USB.....
but after that I installed that preloader file... I can no longer get any connection no more to my hu....
please help me out.... I also did read some stuff that you need to connect or push 3 spots togheter on youre pcb...?? does anyone got more information or a clear foto of wich and how I connect these 3 spots?
Or maybe now a way I can unbrick my device or have correct software for me??
Ive been trying to fix it 4 3 days in a row now... but I am about to go insane
System information I found in factory settings when the unit was still stock and untouched:
YT9216B_00002_V004_20190708
kenel: 3.18.22
Flash:16G
CPU:A7 1.3 GHz x 4
Display 1024 * 600
MCU1: HW8227L-3.3-SW0-3.1
Inide when i open it op the sticker on the connectors on the pcb tells me:
YT9216B Vo.1 16C
A.005-YT9216B004
20200214
And here is the information of the store i bought it from in the original advertisement:
Specifications on website:
● System:Andriod 8.1
● Model:SU 9701
● Radio Chip:QN8035
● Software:8227L
● Type:Android navigation MP5
● Size:7 Inch
● Bluetooth:Bluetooth 4.0
● Resolution:1024*600
● Audio Amplifier:TDA7388
● Voltage:12V
● Power Output:60W
● Memory:1G+16G
● Audio format:MP3/WMA/WA/OGG/FLAC/APE
● Video format:RM/RMVB/MP4/FLV/MKV/3GP/AVIASF/SWFMP1
● Image foramt:JPG
● FM Range:FM 87.5~108MHz
● Operating temperature:-10℃ ~ +60℃
● USB Interface:USB 2.0
● Product Size:188mm*58mm*165mm
● Weight:1922g
● Button: Physical button/Reset button
● Factory password:1111
My apologies for my bad English (not my native language).
Hope you guys can help me unroot it...
Click to expand...
Click to collapse
Hello, Did you solve issue?
I'm facing same issue. My android radio is the same of yours.
Hello all, i have tryied to update my headunit to android 8 using PhoenixSuit, the upgrade process had gone right, but the headunit locks on the android start screen. And i am struggling with it for some months now.
I am unable to make it be recognized by phoenix suit again, nor make it boot to an USB or Mem card made by phoenixcard.
the only thing i could get was it to start in recovery mode, so it read files like:
51eb6df0-cad7-11e8-bf31-afdca4ac0826
52c7b3fa-cad7-11e8-8188-57adc8d05072.0
52c7b3fa-cad7-11e8-8188-57adc8d05072.1
etc.. the name of the files vary according to the "uboot" file i load on the headunit.
I have tryied lots of files gotten from russian foruns, etc to no sucess, even the original files that i got from the maker fails to start the unit.
If i had to guess the problem that make me unable to restore the original android 7.1 i got from the makers, it would be the partitions number and size, i think phoenixsuit had recreated the partitions in the upgrade process and that recovery mode does not change it... so any android that is not the version 8 (that seens to not work on my unit) does not get even to the start screen.
If someone can give me some tips on how to solve this, i had alread tried anything i could understand from the russian foruns and from here to no sucess
Thanks in advance.
So nobody knows how i can get into a "command prompt" mod where i can remake the system partitions or how i can get the headunit to boot from a phoenixcard created USB?
Hi, i need mcu for my android 1din car player, can someone help, i ask many peoples and they dont have it, if someone can help. My car audio player is cyclon 7101a
Hi all,
I decided to make 3, very beginner-friendly guides on how to fully backup your Android Head Units and how to restore those backups. These guides are made primarily for the SuperMOD packages in my signature but will generally apply to any Mediatek-based device.
Video Guide - How to full backup your Android Head Unit
This guide will help you:
Backup your whole flash drive with SP Flash Tool
Create your own Scatter and Preloader file
Create your own shareable firmware
PDF Guide - How to restore your backup with SP Flash Tool
This guide will help you restore your backup on a working Android head unit, type MediaTek YT921xxx, with available flash dump
Video Guide - Test Point recovery of a bricked head unit
This guide will help you restore your non-working Android head unit, type MediaTek YT921xxx, with available backup
If you encounter errors during these procedures, like DRAM failures etc, here are the main reasons as to why this might be happening:
Your Preloader and/or Scatter file is incompatible - extract your native scatter and preloader from your backup file
Incompatible SP Flash Tool version
Try to insert the USB cable within 2 seconds of pushing 'WRITE' or 'DOWNLOAD'
Use USB 2.0 ports if available rather than USB 3.0
Make sure your USB port does not go into sleep mode
Your Mediatek drivers are not properly installed on your PC
Faulty or incompatible USB cable - make sure it's shorter than 1m.
Refer to this guide on information about all the errors
------------------------------------------
Thanks! And if this post is helpful to you please don't forget to "like" it.
Enjoy!
iceblue1980 said:
I wanted to share a guide that I translated from Russian forums and adjusted for the English speaking folks on how to successfully import a memory dump into you chinese unbranded Android car stereo head unit, normally a 8227L_demo device with Android type YT9213, YT9216, YT9217, YT9218 and similar.
The guide is made for beginners and is with pictures. You can view the PDF file here and I suggest you download it for better viewing quality and picture detail.
If you encounter errors during the procedure, like DRAM failures etc, here are the main reason for why this is happening:
1. Your Mediatek drivers are not properly installed on your PC
2. Try another Flashtool version (for me only version 5.1824 worked thus far) - this should solve the issue 90% of the time.
3. Ensure your USB cable is shorter than 1m and is fully working.
I am also going to make a separate post on how to perform a full backup of the same unit types, using the same tools. As you know it is always recommended to backup your original ROM before starting experimenting. Thank you and I hope this is helpful to you folks out there.
Click to expand...
Click to collapse
You know it. We know it. That you are the best!!! Thanks a lot!
Flashtool version is VERY critical, as I found out the hard way. Please remember to follow each author's instructions to the point.
iceblue1980 said:
I wanted to share a guide that I translated from Russian forums and adjusted for the English speaking folks on how to successfully import a memory dump into you chinese unbranded Android car stereo head unit, normally a 8227L_demo device with Android type YT9213, YT9216, YT9217, YT9218 and similar.
The guide is made for beginners and is with pictures. You can view the PDF file here and I suggest you download it for better viewing quality and picture detail.
If you encounter errors during the procedure, like DRAM failures etc, here are the main reason for why this is happening:
1. Your Mediatek drivers are not properly installed on your PC
2. Try another Flashtool version (for me only version 5.1824 worked thus far) - this should solve the issue 90% of the time.
3. Ensure your USB cable is shorter than 1m and is fully working.
I am also going to make a separate post on how to perform a full backup of the same unit types, using the same tools. As you know it is always recommended to backup your original ROM before starting experimenting. Thank you and I hope this is helpful to you folks out there.
**ONLY UPLOAD 'BOOT1' IF YOUR UNIT IS BRICKED, OTHERWISE JUST UPLOAD THE 'ROM_USER" FILE.
Click to expand...
Click to collapse
Hello. Pdf file is not available for download.
raionshinzo said:
Hello. Pdf file is not available for download.
Click to expand...
Click to collapse
Thanks, please try again. The link has been updated.
iceblue1980 said:
Thanks, please try again. The link has been updated.
Click to expand...
Click to collapse
Thanks for the reply and for updating the file.
Can You please help me with this issue?
I have two HU 9216bj with 1 GB ram and 16GB storage. The problem is that one is XY auto 1.1 and is running without any issues. Another one I bought came with XY auto 6.5. However, after some time this one started to cause problems such as when I start the car half of the screen started to splash like rain. The seller changed my unit but this problem did not go away. So I contacted him again and he updated my unit to XY auto 6.8 but even after the update, the problem is there. He told me that these 6.5 and 6.8 updates are causing problems and asked me not to update my XY auto 1.1 HU which is still working fine.
So I made a dump file of 9216bj XY auto 1.1 and rewrite it on the XY auto 6.8 but the unit goes black screen and I have to use the original emmc_user file of 6.8 to restore it. These units are not 10.1 andriod. The droid info showed 8.1 and CPU Z showed 9.1. Frankly speaking, I don't know which android it is.
I have attached the images of both the 9216bj 1GB 16GB below. Kindly guide me in this regard.
Thanks again.
raionshinzo said:
Thanks for the reply and for updating the file.
Can You please help me with this issue?
I have two HU 9216bj with 1 GB ram and 16GB storage. The problem is that one is XY auto 1.1 and is running without any issues. Another one I bought came with XY auto 6.5. However, after some time this one started to cause problems such as when I start the car half of the screen started to splash like rain. The seller changed my unit but this problem did not go away. So I contacted him again and he updated my unit to XY auto 6.8 but even after the update, the problem is there. He told me that these 6.5 and 6.8 updates are causing problems and asked me not to update my XY auto 1.1 HU which is still working fine.
So I made a dump file of 9216bj XY auto 1.1 and rewrite it on the XY auto 6.8 but the unit goes black screen and I have to use the original emmc_user file of 6.8 to restore it. These units are not 10.1 andriod. The droid info showed 8.1 and CPU Z showed 9.1. Frankly speaking, I don't know which android it is.
I have attached the images of both the 9216bj 1GB 16GB below. Kindly guide me in this regard.
Thanks again.
Click to expand...
Click to collapse
Unfortunately the Android 10 units are very poorly built and there are no custom firmware available afaik. The 8.1 and 9.1 units are doable but 10s should be avoided.
iceblue1980 said:
Unfortunately the Android 10 units are very poorly built and there are no custom firmware available afaik. The 8.1 and 9.1 units are doable but 10s should be avoided.
Click to expand...
Click to collapse
Hello.
The android version is 9.1. I have attached the images below. I would appreciate if you can guide to an older or stable firmware or its dump for YT 9216BJ mipi 1280×720.
I have tried many roms from XYgala but the screen goes black even after reset it remains black.
I created a dump by making an scatter file with MT8127 processor and emmc memory and then did a read back of boot 1 boot 2 and user.
Thanks.
raionshinzo said:
Hello.
The android version is 9.1. I have attached the images below. I would appreciate if you can guide to an older or stable firmware or its dump for YT 9216BJ mipi 1280×720.
I have tried many roms from XYgala but the screen goes black even after reset it remains black.
I created a dump by making an scatter file with MT8127 processor and emmc memory and then did a read back of boot 1 boot 2 and user.
Thanks.
Click to expand...
Click to collapse
Try this guide.
iceblue1980 said:
I am also going to make a separate post on how to perform a full backup of the same unit types, using the same tools.
Click to expand...
Click to collapse
That could be very helpful.
Is it available ?
oferyuval said:
That could be very helpful.
Is it available ?
Click to expand...
Click to collapse
iceblue1980 said:
oferyuval said:
That could be very helpful.
Is it available ?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
The linked clip is from 2014.
An updated guide from 2019 from the same guy can be found here: https://forum.hovatek.com/thread-21970.html
oferyuval said:
The linked clip is from 2014.
An updated guide from 2019 from the same guy can be found here: https://forum.hovatek.com/thread-21970.html
Click to expand...
Click to collapse
Isn't this a guide for WwR tool rather than Flash Tool?
iceblue1980 said:
Isn't this a guide for WwR tool rather than Flash Tool?
Click to expand...
Click to collapse
It uses WwR to make a scatter file and than SP Flash Tool
Okay, I updated the OP. Now there is a guide both for making full backup and restoring it. Hopefully, this will help you guys out there.
iceblue1980 said:
Okay, I updated the OP. Now there is a guide both for making full backup and restoring it. Hopefully, this will help you guys out there.
Click to expand...
Click to collapse
Great, many thanks !!! I'll try to follow it.
The new backup guide looks very clear and comprehensive.
I'll use it to make my first backup attempt. Thank you for taking the time to make it.
Two questions:
1. It seems that the values from the scatter file downloaded at 8. are used only for downloading preloader.Xxx.bin. Is that correct ?
2. Should we disconnect the usb cable from the pc at 17. before reconnecting it in 23. ?
oferyuval said:
The new backup guide looks very clear and comprehensive.
I'll use it to make my first backup attempt. Thank you for taking the time to make it.
Two questions:
1. It seems that the values from the scatter file downloaded at 8. are used only for downloading preloader.Xxx.bin. Is that correct ?
2. Should we disconnect the usb cable from the pc at 17. before reconnecting it in 23. ?
Click to expand...
Click to collapse
Happy to hear that.
As for your questions:
The scatter file included in the software package downloads is applicable to the respective head unit type, that the software package is made for. This means you can use it to backup your head unit, without the need of creating your own scatter file. And the best part is - if the scatter file isn't compatible with your head unit, it's a good indication that the software package is not compatible with your device.
No, as you are instructed to disconnect the USB cable in step 15.
iceblue1980 said:
Happy to hear that.
As for your questions:
The scatter file included in the software package downloads is applicable to the respective head unit type, that the software package is made for. This means you can use it to backup your head unit, without the need of creating your own scatter file. And the best part is - if the scatter file isn't compatible with your head unit, it's a good indication that the software package is not compatible with your device.
Click to expand...
Click to collapse
This makes perfect sense if I had a verified firmware or at least verified scatter file.
I don't know how to get one for my device.
I would like to backup the original firmware before loading a new firmware, so I can restore the original incase the new one is not compatible. In this case I am not sure that using a scatter file from the new untested firmware is a good idea.
iceblue1980 said:
2. No, as you are instructed to disconnect the USB cable in step 15.
Click to expand...
Click to collapse
Sorry, I missed this one
oferyuval said:
This makes perfect sense if I had a verified firmware or at least verified scatter file.
I don't know how to get one for my device.
I would like to backup the original firmware before loading a new firmware, so I can restore the original incase the new one is not compatible. In this case I am not sure that using a scatter file from the new untested firmware is a good idea.
Sorry, I missed this one
Click to expand...
Click to collapse
You can make your own scatter file using a tool like WwR MTK.
Having said that, I'd be very surprised if the scatter file in the software package didn't work for your device, providing your head unit is compatible.