Thank you for your reply. I will look into it and let know how it went.1.73.8 changed partition table and require PC to flash firmware. Will erase everything include IMEI and zlink/360 activation. All can be recovered.
If you want to try, info here. It is quite a bit more complex than standard upgrades via System Info menu button. But not too difficult depending on computer skill level.
YT5760B_AC8259 - Brick Recovery
Firmware Format and Installation Diagrams Here is a general overview diagram providing an understanding of ota, firmware, and TWRP flashing. And flashing upgrade to 64bit on <= 4GB HUs. https://mega.nz/folder/hDEhFAqZ#A0JuPIKhW83X5NZgL2NSWg/folder/QTllgKwAsites.google.com
AC8257 CPU Based unit's problems & questions - Couldn't find any info about it
- Thread starter EagleXDR
- Start date
Just an update: I performed an update to 64bit firmware, it went well. HU is definitely faster.
One more question: I tried to change mic sensitivity in factory settings, but in my case I can't open drop-down menu (see attachement). Is there any fix?
And one more thing: whenever somebody call me, a ringer in BT app is incredibly loud (much louder that music). After the call, music is as loud as the ringer for a second, and then goes back to normal? Any way to lower ringer sound level?
Attachments
Glad to hear firmware flashing went well. Let me know if anything in my directions is unclear. Which IMEI recovery tool did you use?
Also Is your HU 2-4GB unit? which would have followed my custom directions to run 64b on 2-4GB systems. Posting a System Info screen is usually the clearest.
The Settings Menu has Volume settings for music and call volume and the mix ratio. Tried any of those?
Your screen pic shows hotspot is on so I presume you are on either Apple CarPlay or Anrdroid Auto. There is generally a huge problem for call volume/gain with these. Read here
YT5760B_AC8259 - Sound
Musc & Call Volumes There are 3 possible ways to make/receive calls BT calls to linked phones without CarPlay/AndroidAuto (CP/AA) Use Settings->Volume to set call volume and music volume independently. Usually call volumes are set much louder than music due to the narrow frequency range of calls
Last edited:
First, thank you for the reply and guidance. I used Maui META, worked fine (I had problems during first try, it worked well after that).
My HU is 4GB unit.
I don't know of any clear comparison 64bit is better. I am running a 64b firmware on my 2G horizontal HU. If you've already done firmware flashing before, then its easy to go back and forth as you like. Here are the directions
YT5760B_AC8259 - Brick Recovery (google.com)
Do note you have a vertical unit and recent vertical unit 1.73.7 installation revealed the wrong orientation display driver is in that firmware. See vertical unit installation info here
YT5760B_AC8259 - HW FW
Currently Installed Firmware Settings->System Info will show currently installed firmware YT5760B_AC8259 - Settings (google.com) 1.XX.Y is the currently installed release CANBUS shows the installed CANBUS version MCU shows installed MCU version Factory installed firmware seems to have J preceding
XYAuto seems to be not reachable...I don't know of any clear comparison 64bit is better. I am running a 64b firmware on my 2G horizontal HU. If you've already done firmware flashing before, then its easy to go back and forth as you like. Here are the directions
YT5760B_AC8259 - Brick Recovery (google.com)
Do note you have a vertical unit and recent vertical unit 1.73.7 installation revealed the wrong orientation display driver is in that firmware. See vertical unit installation info here
YT5760B_AC8259 - HW FW
Currently Installed Firmware Settings->System Info will show currently installed firmware YT5760B_AC8259 - Settings (google.com) 1.XX.Y is the currently installed release CANBUS shows the installed CANBUS version MCU shows installed MCU version Factory installed firmware seems to have J preceding
But can i use the OTA version or should I totally reflash the Flash memory and then the new firmware?
Computer flash firmware method is necessary. Last page of overview diagram illustrate this
YT5760B_AC8259 - Brick Recovery
Firmware Format and Installation Diagrams Here is a general overview diagram providing an understanding of ota, firmware, and TWRP flashing. And flashing upgrade to 64bit on <= 4GB HUs. https://mega.nz/folder/hDEhFAqZ#A0JuPIKhW83X5NZgL2NSWg/folder/QTllgKwA
Hi,
I have a vertical unit :
YT5760B , AC8259, 8G and 128G, Display 1280x800 (lvds) (8Bit).
after updating from 1.73.7 to 1.73.8 using PC flashing and update outline by Howardc64 the unit bricked to black screen, only backlight is on. Wrong display driver? so after many reboots and waiting.. it started but just like you the colors were wrong - 6bit instead of 8bit- and the touch is wrong. pressing on top of the screen result in clicking the bottom of the screen.
How did you resolve the issue please?
Try to get into system settings and then you can go to factory settings. then in touch settings you can change the X-Y swap settings. It takes a lot of trying out where to touch the screen to get to the right button. But keep in mind that the X-coordinates are swapped.
I tried that already, it did not resolve the issue, it made worse, instead of reverse x-axis the y-axis got reversed as well!
What about the colors? How did you fix that? at the moment under SYSTEM INFO it shows the display as 6bits instead of 8bit.
Thanks for the help.
Under config set screen to the right settings and not adaptive.
For the colors, scroll down and at the bottom there are two check boxes. Set the one on the right to on! I do not remember what its called
In the same screen where you can set x-y swap, there is also a config.
I will give it a shot. It's hard to read when colors are saturated. Thanks a lot, Will post the results later.
The colors are OK now. The tiny box on the right was for 6/8 selection. Awesome, big relief .
The config box when selected a message pops up saying "No upgrade file found".
Seems xyauto vertical unit computer upgrade firmware has 6/8bit and touch coordinate inversion problems. I’ll update the install guide with a warning.
Can you show a pic of the tiny button for 6/8bit for future firmware flashing upgrade efforts?
Hi, Sure thing. Thanks for all the good work you put into this.
@ekvdc , Are you sure it was under "config" box? I clicked the "touch screen resolution" and there was a setting of "adaptive" and there I changed it to my screen res 1280*800 , saved it and rebooted. That did not fix the wrong X coordinate inversion.
Sorry was indeed Touch screen resolution. Mine is 1024X768. Changed that and then did a reset and after that it was ok. Previous flash it took about three or four resets and then it was good..
For the color depth it is under "color setting"
Attachments
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
@2:15 in the video, his thumb is over the 2x DDR memory. Its under the shield in your HU.
I recently researched a dead eMMC for HiSense Android TV. eMMC is not simple flash chip. It has many features
- Handles NAND Flash wear leveling
- Provide multiple partitions (boot/user)
- Access security to boot
- Has CPU inside
eMMC4.5 (jedec.org)
I'm not certain of the following but after studying HiSense TV Android eMMC, I think the following is boot process for all Android with boot code stored in eMMC
- main SOC request code from specific eMMC location (boot1?)
- boot1 code (maybe also boot2? I don't know) start running basic system (not yet HU firmware)
- basic system has more sophisticated communication capabilities to/from USB/PC to flash remainder of the firmware
- I think boot1 code can be secured
Where did you get the boot1? And does it match your HW?
Since YT5760B has so many variations. Maybe there is slightly different boot1 for slightly different HW versions. Its probably desirable to get boot1 from matching HW version #s on your board.
In HiSense TV, writing boot1 required security access and need to contact SOC manufacturer (MSTAR who is also acquired by MTK just like AutoChips). I guess this is not necessary for AutoChips from the youtube video. But it is still necessary to get correct boot1 and the flash location. I don't know any details here.
I don't have any experience here. Just sharing some basic knowledge of Android boot process.1
You have different HU firmware than this thread. See Boison B200 under "Other AC8259HUs" tab
I'm not sure how robust is the B200 forums on firmware upgrades. Its easy to brick these HUs so make sure you read and confirm clear robust B200 upgrade procedure before attempting. This forum's HU (YT5670B) has firmware released on file server by firmware developer. However, many HUs owners post firmware they received from vendor in forums.
On 360 app on our HU, you buy HU version with this feature, then the vendor preinstall 360 app (roundadas) license. Yous says not activated so maybe you didn't purchase this feature?1
I installed latest version of UI20 in xyauto site(June 1). After 2 day of testing, It seems the problem of 360 was solved.
So I need not to test the 3 split screen base package. -
4i did it !!! i did it !!! my radio works!! to much people with this problem and i found the solution trying bored files from xygala, i was bored, i downloaded all the files in that drive 1 by 1.. seems it’s a driver for lg screens, i will edit this to make a tutorial, but i need help to do it, my english is not so good3Late Feb release of an xyauto UI is pretty good. Has maps (I use with google maps app with offline maps), radio, HU music player, a fixed app launch icon pane (left vertical) and a user changeable app launch icon pane (lower bottom) all on one screen.
Generally quite nice. google maps has voice input search, auto dark mode at night while navigating (none navigation mode unfortunately stays in day mode) map will be always north up while driving without navigation route.
patch file link Note this seems to be for 1024x600 screen only. Didn't see it in other resolution folders.
Mode switching is a bit mysterious (I have a steering wheel button programmed to switch modes). In the old default UI, mode switch with switch between currently running apps. Seems to do nothing on this UI while being displayed.
This launcher provide everything I use so no need to fiddle with the HU much. Just power on the car and drive. The useful features are
- FM radio (wife listens to this and its her car)
- Maps always displayed and track your position smoothly (Seen other launchers with map. Position only update every second or so, very jerky display). Google maps fixed to north up unless navigating. Voice input destination via mic icon on google maps search bar. Maps always in bright color mode (quite bright at night but area is not entire screen) Navigation will auto change to dark mode at night.
- BT works if setup to auto pair. Incoming calls pops up on screen. Can voice command out going calls with iPhone easily. Just say "siri call xxx" with iPhone mic able to hear you. iPhone looks up your contact and dials while connecting to HU's BT for speaker/mic sound.
- Music player will play all music files in the system/USB stick.
- Color choices are nice. Colorful but background is dim for night time use. Only issue is google maps none navigation mode display stays bright. Other nav software might handle this better.
- Google maps generally likes portrait displays like a phone. This horizontal smaller window sometimes hide the next driving intersection change behind the green direction box on top. Not too big of a problem.
- Left column icons are not changeable. Bottom row is user changeable.3I have recorder a video with the YT5760B system upgrade. It takes about 5 minutes to complete. In the attached ZIP file you can find the video.3
I managed to extract all the apks from 1.73.7.
Strangely. I couldn't find zlink.apk.
There is ZlinkActivationCode.apk, which is the only apk related to zlink.
-------------------------------------------------------------
Update!
Finally found the zlink apk. it was inside the vendor.new.dat.br.
I have uploaded zlink apk here, just in case someone needs it.
I believe this is the zlink ver 3.9.27 comes from the 1.73.7 firmware.
I haven't got chance to test it on my HU (now is midnight here in Australia), will do it tomorrow.3
Just installed 1.73.6 on 5760B 1024*600, didn't wipe user data.
Actually, I forgot and left 1.73.3 (don't recall if it was 5/24 or 7/25 version) on the USB stick w/1.73.6 and 1.73.3 got installed which wiped my user data. But then I installed 1.73.6 over this without wiping user data.
Biggest change I notice is just the 2x boot up pop sound is gone. So maybe xyauto have more orderly sound hardware initialization now
