yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] looxonline:
Finally got around to donating too :) Efforts appreciated.
[FYT Android Head Units] wanb1i:
Me too!:cool:
[FYT Android Head Units] looxonline:
Finally managed to pull the contents of fyt.prop. Planning on investigating the SOM in a little more detail tomorrow to see if I can understand the hardware a little better.

px5:/system/app $ cat fyt.prop
#客户标识：fytmanufacturer
# fyt,mt,sh,zyc....
#
#字体大小：fytfontzise
# 0.8, 1.0, 1.15, 1.3
#
#动态壁纸：fytlivewallpaper
#com.bizhi.mogudongtai/com.zte.mobile.MushroomDay.WallpaperServiceMushroom
#
#输入法：inputMethod
#注音输入法:com.google.android.apps.inputmethod.zhuyin/.ZhuyinInputMethodService
#讯飞：com.iflytek.inputmethod.pad/.FlyIME
#
#未知来源开关：ro.rk.install_non_market_apps
#
sys_graphic.cam_dvp.deinterlace=false
ro.rk.install_non_market_apps=true
ro.build.fytmanufacturer=53
ro.build.fytfontsize=1
ro.build.fytlivewallpaper=
ro.fyt.uiid=2
ro.build.fytinputmethod=com.google.android.inputmethod.pinyin/.PinyinIME

ro.fyt.def.sb.radio=8
ro.fyt.def.sb.aux=4
ro.fyt.def.sb.player=4
ro.fyt.def.sb.tv=8
ro.fyt.usb_enable=1
persist.fyt.fy_radartofront=1

# 空	= 0;
#调试	= 1;
#深青联	= 2;
#青联同创= 3;
#悦歌	= 4;
#名途	= 5;
#众易畅	= 6;
#睿林	= 7;
#凯易德	= 8;
#普诚博安= 9;
#车行建	= 10;
#州信	= 11;
#莹隆	= 12;
#思百德	= 13;
#东琛	= 14;
#柯权	= 15;
#车美利	= 16;
#福帆达	= 17;
#卓奥通	= 18;
#博悦纵横= 19;
#格铭	= 20;
#佳艺田	= 21;
#卡百特	= 22;
#航韵	= 23;
#瑞宝	= 24;
#三一众合= 25;
#北箭	= 26;
#兴嘉林	= 27;
#欧华	= 28;
#康盛	= 29;
#方向通	= 30;
#爱影	= 31;
#派实达	= 32;
#凯振	= 33;
#飞音	= 34;
[FYT Android Head Units] kikan:
donating too...

thanks

by

kikan
[FYT Android Head Units] Squirley709:
So, since it is paused I am assuming no download is available?
[FYT Android Head Units] surfer63:
No, there is not yet a ROM available at all, AFAIK
[FYT Android Head Units] Zaagfluit:
Any news on the px5 FYT ROM? Will it include selectable canbus presets for multiple cars?
[FYT Android Head Units] looxonline:
LOL, I was about to ask the same thing. [MENTION=520205]gtxaspec[/MENTION] mentioned that it would not overwrite the MCU so provided the Joying ROM uses the same communication protocol between SOM and MCU for decoded CAN messages then CAN should work. [MENTION=520205]gtxaspec[/MENTION] to confirm though.
[FYT Android Head Units] Zeze21:
I am very sorry if that is a stupid question, but would this Rom run on one of the following devices:

jy-um128p2 or jy-um135p2?

Or let me rephrase that question: Is there a way for me to find out if the rom will run on the devices before flashing the rom?

Thank you :)
[FYT Android Head Units] looxonline:
They are both FYT 6026 and the comments on the Joying blog made by Joying themselves suggest that they can be upgraded to Android 8. On that basis this ROM should work with them.
[FYT Android Head Units] Zeze21:
Thank you so much for that Info. I do however have 2 more questions:

1.) Where have you found any comment on the jy-um128p2 about the oreo update or is there anywhere an oreo update? (I myself have not found one)

2.) Please don't let me die stupid :) How do you know that they are FTY 6026? Where can I see that?
[FYT Android Head Units] looxonline:
1.) Read the comments at the bottom of this page... https://www.joyingauto.com/blog/pos...-core-cpu-android-car-stereo-latest-update-2/

2.) Joying units ending with P2 are FYT based... see https://xdaforums.com/showpost.php?p=76662264&postcount=4
[FYT Android Head Units] Zeze21:
Thank you again. I don't want to bloat this thread but - I can not find anything about the jy-um128p2 only about the jy-uo128p2 or does this include the jy-um128p2

Again I am sorry for my stupid questions - i just want to be able to understand and be sure (as much as possible)
[FYT Android Head Units] looxonline:
The UM is listed right there on the same page that I referenced. That page is referring to firmware that is compatible with PX5 units. The UM is therefore a PX5 unit...
[FYT Android Head Units] Zeze21:
True - but it does not say anything about it being an oreo update :confused:
[FYT Android Head Units] surfer63:
Joying is very unclear about that.

They have FYT PX5 firmware updates from 6.0.1 to 6.0.1

AND they have FYT PX5 firmware upgrades from 8.0.0 to 8.0.0

They do not mention an upgrade from 6.0.1 to 8.0.0

Either a 6->8 upgrade is not supported. Or maybe the upgrade is a little tricky and maybe that's why they do not officially announce it. I don't know.

So everyone on a PX5 6.0.1: email to carjoying@gmail.com for an official statement and an official upgrade route from 6.0.1 to 8.0.0
[FYT Android Head Units] Zaagfluit:
Doest that mean that for example, If my parking sensor sound doest’n work now, it still won’t work after the update?
[FYT Android Head Units] wanb1i:
Just curious if there is any movement on your new PX5SoM and therefore the ROM? I know several of us have donated and we all love your work! I have your ROM on my wife's Sofia unit and can't wait to get it on my 6021 upgraded to 6026! ;):cool:
[FYT Android Head Units] shanetrainST:
Is it possibly we will see a AOSP 8.0 build for the PX5? Something more stock and less joying.

I see they have completely messed up the Bluetooth with the PX5, apps cannot turn on or scan the BT like they can on the Sofia.

The PX5 is using a Realtek RTL8723DS wifi/bt 4.1 combo, seems connected to the CPU.

Why cant the Chinese just learn to use standard build practices and not try route all their stuff through their FYT software.
[FYT Android Head Units] wanb1i:
Curious, I'm not having any of those issues on my PX5 Core upgrade.
[FYT Android Head Units] looxonline:
From what I understand intel included BT on the SoC which meant that there would have been native Android drivers providing the HAL. This means that apps using the standard Android calls would have been able to access the BT.

With the PX5 the BT was not included on the SoC. While it may still have been possible to use native Android drivers to interface with the RTL it seems as if the Chinese chose not to and instead wrote their own. Because of this when an app tries to access BT functionality it can't. The FYT stuff on the other hand knows how to interface with the driver that they wrote...
[FYT Android Head Units] shanetrainST:
I have been looking into this a lot, seems the Bluetooth drivers/libs and apps are all standard.

The BT is included on the SOM just like the Sofia so it should work fine, I have the PX5 SOM that replace the Intel Sofia board upgrade

Problem is joying have modified 2 files in the ramdisk (boot.img) init.syu.rc & init.connectivity.rc to get all BT to the Joying app by removing a heap of stuff and adding a heap. I have found a clean source online that I have been able to make new init.connectivity and modified init.syu.rc, it will probably break all Joying Bluetooth functionality but it should allow other apps to turn it on, that all I am interested in.

My biggest problem now is i have modified the two .rc file and made a new Boot.img and placed it into the 6026_8.zip but I get signature verification error when I try load my modified ROM.
[FYT Android Head Units] looxonline:
Strange given that the bootloader will pretty much load anything. No need for signatures. See post #5 in this thread.
[FYT Android Head Units] shanetrainST:
I have tried a few time to mod the rom, each time it fails then reboot right before the android logo should appear (install status bar), it only flashes up very very quick an error that I think mentions signature..

As for post 5, I am on the latest firmware so they may have changed something since that post
[FYT Android Head Units] looxonline:
I have not worked with this SoM much but to the best of my understanding the bootloader should not be alterable with an update. Once a bootloader is unlocked it should always be unlocked. The only way to change that would be with a manual write of a new image to the flash. That's why having a bootloader exploit or an unlocked bootloader is such a bonus. Did you change the sql6026update8 binary by any chance?

Otherwise message gtxaspec directly and I am sure that he will be able to assist.
[FYT Android Head Units] Néocray:
Any news from gtxaspec about availability?
[FYT Android Head Units] packyman:
Any news?
[FYT Android Head Units] TT_Vert:
[MENTION=520205]gtxaspec[/MENTION], where are you located? I can probably get you what you need. If outside of US perhaps we can crowdfund for shipping. I'm glad to provide the SOM though.

Dave
[FYT Android Head Units] rowdy15:
Getting a SOM

Hi All,

I have just purchased and installed this head unit in my VW Jetta MK5. The existing software is pretty good, except for a few things.

I like how it talks to the canbus.

- Radio stations show up on dash screen with channel number and frequency

- the music and video apps show up on the dash screen also as "1/5" e.g. song 1 of 5.

I like how it can play flac and mp3 files and any of videos I have tried to play so far, so I don't need to install any other music or video apps.

The radio IC (TEF6686) seems to work really well. Soooo much better than my old KGL RK3066 unit.

I do however have some issues:

- I believe the Bluetooth, makes you lose you contact on your iPhone when downloading contacts to head unit. (just a guess but I think that's what's happened)

- micro SD slot only accepts 32 GB (I need to do more testing on this though...maybe I need to format the microSD card to NTFS or maybe EXT2 or EXT3 or EXT4).

- the head unit doesn't have any way to set the apn settings so that you can have a usb dongle in it. You can enable 4G in the settings and an icon does come up in the pull down status bar, but it doesn't work. I haven't tested with an apn settings app yet.

Someone please get the original poster a new SOM. Here is a link to one. or is this the intel sofia unit.

https://www.joyingauto.com/joying-fyt-android-8-0-oreo-update-4gb-32gb-core-board.html
[FYT Android Head Units] looxonline:
Most on this thread have donated. Why not chip in a bit and make it happen faster?
[FYT Android Head Units] TT_Vert:
I have a PX5 SOM i'd donate and offered to two posts above but he never responded. I'll just keep it as a spare.

Dave
[FYT Android Head Units] rowdy15:
OK. How do I do it. Paypal? edit: nevermind worked it out now. Sorry didn't see the donate button initially.

gtxaspec can you please send your postage details to dave, so he can send a SoM to you. happy to help pay for postage.

update on likes/dislikes.

likes:

the bluetooth quality is excellent and google assistant works great too. You guys may already have had a good quality microphone and google assistant, but this was a massive issue in the earlier models (e.g. KGL RK3066 models).

dislikes:

the music widget doesn't update the picture (from file metadata).

The widgets aren't that rich. It would be awesome to have the one widget like in malaysks rom. that shows the details of the different media programs.

The likes far outweigh the dislikes though.

Also worked out that a micro SD larger than 32 Gb works if formatted to NTFS.
[FYT Android Head Units] surfer63:
This is not correct.

I created a custom ROM Yesterday, but it failed on an incorrect signed 6026_8.zip. Not signed, with testkeys signed, with my own signature: Always a "whole file verification error".

So the recovery binary does check signatures.
[FYT Android Head Units] gtxaspec:
You can't use the joying recovery to install the zip, the joying recovery DOES require the zip to be signed. Use twrp. In my notes I was referring to the hardware itself, not the joying recovery
[FYT Android Head Units] surfer63:
OK. clear. It put me on the wrong foot thinking it was like the "old days" when making custom ROMs for rockchips.

Good you're back.

Can I use the same TWRP image as for the Sofia?
[FYT Android Head Units] gtxaspec:
Nope, you have to use one targeted towards the arm platform. Been traveling the past few months for work, I'll see if I can dig up my twrp image.
[FYT Android Head Units] surfer63:
Some time ago I looked at the twrp.me site but there are so many versions and I can't find the most suitable for our units.

(I can't find the x86 one for the Sofia either)

Edit: or did you compile it yourself?

Edit 2: Or from here? https://twrpbuilder.github.io/downloads/twrp/ (search for px5)
[FYT Android Head Units] Aaaron16:
Is it possible to get a version of this ROM without Xposed? Or have you found a way of packing the system.new/system.patch/system.transfer files in the 6026_8.zip?
[FYT Android Head Units] surfer63:
It is not a problem to package a new system.new.dat and system.transfer.list (and also another allapp.pkg with some mods like a split-screen enabled apps and a BT-app that can only read contacts, so it won't screw(=remove all) your Google contacts). That is what I did and mentioned on 28th October (post #49).

The point is that the 6026_8.zip needs to be signed with the FYT/Joying signature, OR you need to replace the Joying recovery with a TWRP recovery as gtxaspec explained in post #50. With TWRP in place you also put everything (the things you want) from Allap.pkg also in system.new.dat and system.transfer.list.

This I had not understood from his post #5 where he mentioned "FYT_6026 does not require signed images...of anything, even the bootloader.". He meant there: In case you have the TWRP recovery, then the FYT_6026 does not ......

(It would have been so nice if it worked with unsigned images/files with the Joying recovery binary: Simply create a new 6026_8.zip and allapp.pkg and create a new file_contexts(.bin) for the SELinux extra file attributes, and simply flash that combo using Joyings update binary.)
[FYT Android Head Units] packyman:
any chance for happy news of a custom rom?
[FYT Android Head Units] surfer63:
Continuation of https://xdaforums.com/showpost.php?p=78317447&postcount=2084

You need to know the several partitions. For that you issue a command from a rooted adb access or a rooted shell on the unit, and do like:

ls -l /dev/block/platform/ff0f0000.dwmmc/by-name/

Among a lot of other partitions it will mention:

recovery -> /dev/block/mmcblk2p7

When making a backup of the stock PX5 recovery image you need rooted adb access or a rooted shell on the unit, and do like:

dd if=/dev/block/mmcblk2p7 of=/sdcard/stock-px5-recovery.img

Then verify it:

sha1sum /sdcard/stock-px5-recovery.img

This should give you some sha1sum. Then do the dd and verify again and see if you get the same sha1sum.

When writing a recovery image, you first verify its sha1sum like:

sha1sum /sdcard/my_custom_recovery.img

And to write the recovery to its recovery partition you do something like:

dd if=/sdcard/my_custom_recovery.img of=/dev/block/mmcblk2p7

Followed by a verify:

dd if=/dev/block/mmcblk2p7 of=/sdcard/check-my_custom_recovery.img
sha1sum /sdcard/check-my_custom_recovery.img

And of course both sha1sums should be equal. Then you can remove the /sdcard/check-my_custom_recovery.img

Then the proof of the pudding: try to reboot to the TWRP recovery.

etc. etc. And that is only to find the correct recovery image. Then the start for the "quest" of the custom ROM starts with multiple flashes, errors, probably soft-bricks. etc.

BE VERY CAREFUL!! And check my commands for yourself. I looked very carefuly at it, but everyone can make mistakes.

I will not do this myself.
[FYT Android Head Units] wanb1i:
Sorry for double posting, I didn't realize it had been moved.

Isn't it possible to to temporarily "boot" the twrp recovery, instead of flashing to accomplish whatever task, then reboot and have stock recovery again? I know I did this on other Android devices.
[FYT Android Head Units] surfer63:
Yes, it is. It is the same as what Malaysk is doing with his Android 8 custom rom for MTCD/E units. He uses an SD-card as boot/recovery to flash his image.

You can also follow the steps and try for yourself via this post: https://xdaforums.com/android/help/how-to-boot-sd-card-qmobile-z8-bricked-t3712171

There are more posts/articles describing likewise approaches.

(And now that I think of it: This might even fix gtxaspecs hard-bricked px5. Or maybe he already tried)
[FYT Android Head Units] Kyle M.:
OK, I think this second method of using temporary images might be the safer way around this. Then once i'm 100% happy it works for my unit, I'll try to write it on the recovery partition. Right after lunch, i'm gonna head out to my car with a spare battery and spend the evening with it. Let me know if anyone's interested so i'll take pics.
[FYT Android Head Units] wanb1i:
Thanks Surfer, but this is WAY over my head! ?
[FYT Android Head Units] Kyle M.:
Ok so i tried doing that and the checksums are not the same. I can't understand why.

Update: I've tried to write directly both recoveries that you linked me to, but what it's boiling down to is that the checksums for the recovery images before and after they're written onto mmcblk2p7 are different. I also decided to bite the bullet and attempted reboot recovery for each one. The first (03/2018) simply failed to boot into recovery, and it rebooted the normal way back. The second one I tried (08/2018) caused it to get stuck onto the very first boot logo without doing anything else. Power button did not change anything either. Thankfully the reset button worked and it rebooted back to normal.

The only time the checksums worked was when i wrote the stock recovery back to the recovery partition.
[FYT Android Head Units] surfer63:
The recovery might indeed not work as it is not for the Joying.

I downloaded twrpbuilder from google play to backup and upload the recovery and necessary files to the trwpbuilder site, so that a recovery image can be created, but the queue is constantly too full.
[FYT Android Head Units] Kyle M.:
I've tried sending a request from the app. Not sure if it worked.

On a different note, how well did android 6 work on those head units? I suppose being around for longer, it's become more refined. I never had time to check it out cause my unit shipped with android 8 right away. My phone's still got a 6 on it and it works great for what I need.
[FYT Android Head Units] Kyle M.:
Hi [MENTION=520205]gtxaspec[/MENTION],

Where can I find your latest ROM for this unit please? Also do you have an unlocked bootloader I can try to flash please?

If there's anything that needs testing, feel free to send it over and I'll try it out on my unit as well.

Thanks.
[FYT Android Head Units] ojuniour:
i need your help. i was so stupid. I flashed a twrp recovery and then after I installed an xposed module which made the system get stuck at "android" boot logo. so i tried to flash back the system's original firmware from joying website but now it's possible since the original recovery isn't there anymore. it just shows the car logo for like 2 seconds and then blank screen. What do you suggest? do you think bootable sd is the way to go?
[FYT Android Head Units] surfer63:
I do indeed think that a bootable SD is now the only option, but I never ceated one (for an Android system that is).

When/If you have a workable bootable SD, you have 2 options: either write the recovery image back or flash the system image directly from a system image/zip you created from system.new.dat and system.transfer.list.

I would choose for the "easy" recovery image write-back.

This will require unix/linux knowledge and partition/block/sector knowledge as to where to write to recovery image.

Did you make a listing of your partitions and blocks/sectors of those partitions?
[FYT Android Head Units] ojuniour:
Nope.. Obviously not. :/
[FYT Android Head Units] surfer63:
Been 2 days on business trip.

See attached the files I have.
[FYT Android Head Units] ojuniour:
I'll keep that as future reference. They've already shipped for a replacement.
[FYT Android Head Units] wanb1i:
Bluetooth Headset

Has anyone been successful getting a BT headset to work on this unit?

I've tried 3 different ones multiple times with no joy. The last one said it paired & there was a pop-up indicating it was connected, but no audio.

Any help would be appreciated.

Sorry, I posted this in the wrong forum, but can't delete it.
[FYT Android Head Units] XsQuallenX:
Is this a dead project?

Been checking this for weeks hoping to see download links
[FYT Android Head Units] Junior_1967:
Have you posted this somewhere else? Could not find it..

I also tried and the best I can do now is only have audio by using this gadget:

Using a UClear motorcycle headset and since I pair my phone directly to it all I need is audio out for music and GPS direction.

https://www.bestbuy.ca/en-ca/produc...ter-tv-audio-to-headset-speaker/12928794.aspx

I word of caution: If you decide to use the above BT transmitter, you will have to provide USB power with an external source, not the radio, as it is recognized as a keyboard and creates a bunch of problems...

Sorry if the reply is in the wrong spot.

Cheers!
[FYT Android Head Units] wanb1i:
Thanks for the info!
[FYT Android Head Units] surfer63:
I'm afraid it is. I haven't "seen" gtxaspec for months now.

Maybe he will make a glorious return some day.
[FYT Android Head Units] XsQuallenX:
Well that's no good.

Did any of you fine people reading this, that had the chance to download the files while they were available, save them...and more importantly, wanna share said files? That would be some kind of fantastic. ;)
[FYT Android Head Units] tankgod82:
Has anybody had any luck flashing a dead board. I have one on my hands. I do have the stock ROM from the factory now. They are telling me to put it on a USB drive and just plug it in. My USB slot is working but its not doing anything on the head unit. Any help would be great.
[Xiaomi Redmi Note 5 / 5 Plus Questions & Answers] dromaczek:
Hi, I have question. I want buy note 5 636sd.

I read a lot about anti downgrade.

One question, it is possible after unlock bootloader downgrade via fastboot rom?
[Xiaomi Redmi Note 5 / 5 Plus Questions & Answers] Fataldose:
I think they will fix that soon, for now you can unlock your bootloader flash twrp and then use miuipro, masik, xiaomi eu miui10 roms those all better than stock miuis. So you will not hang to anti rollback ;)

Don't forget to ask seller if device is miui 9 or 10.
[LG V30 Questions & Answers] GinsMada:
Hi

I updated my LG V30+

But I check my "App scaling" app list,

Have a lot app is not available in this function list (Old version has available for these lost apps)

Have any config wrong for mobile?

The software version is V20d-TWN-XX

( I tried to do the factory reset, cache clean.. but...:crying:)

Thank yours.
[ZenFone 2 Q&A, Help & Troubleshooting] mahzix:
Hello!

I'm having some issues with my Zenfone 2.

A few days ago, I brick hard him. and yesterday it has been restored. but I put an old version, so I decide make again the process and put the current version. :rolleyes:

The problem is... I put the wrong WW on my ZE551ML. accidentally I put the XZE551ML :( and now my phone ir haaaaard bricked.

It does not start any more, when I press the power button he vibrates, still in black screen and restart. without bootloader :crying:

I already tried using iSoc,xFSTK,AsusFLashTool... all this programs, but the cellphone does not connect with my pc and programs.

is there any other way to reverse this?

(when my phone it's off and I plug the usb with pc, battery emblem appears as "0%" and not charge)
[Samsung Galaxy S9+ Guides, News, & Discussion] hbstun:
Hi

SM-g960w FRP combination file needed .

Thank u for help
[Samsung Galaxy S9+ Guides, News, & Discussion] hbstun:
at back of the phone

sm-g960w fcc id :A3LSMG960U

Can i use g960u combination for reseting FRP ??
[Samsung Galaxy S9+ Guides, News, & Discussion] Scott:
No, I believe the W is the Exynos and the U is Snapdragon. You need to find FRP for Exy.
[Samsung Galaxy S9+ Guides, News, & Discussion] FalsAlarm:
quit giving out false information! b a s t er
[Samsung Galaxy S9+ Guides, News, & Discussion] elliwigy:
lol calm down.. hes a great guy and a good dev.. im sure he didnt intentionally give wrong info...

to answer ops question, yes, you can flash g960w onto g960u/u1 and vice versa.. any other variants is a no go..
[Samsung Galaxy S9+ Guides, News, & Discussion] FalsAlarm:
lol, sorry, just seems like everyone hoarding the secrets and wanting cash, ya know.

sorry for saying that but I guess they have every reason to do so since life's all about money it seems :good: