Related
Hello all,
Is it possible to put any ROMs on an SD, make it bootable, and boot from the SD?
thank for your answers.
Does anyone knows the solution?
gandhars said:
Hello all,
Is it possible to put any ROMs on an SD, make it bootable, and boot from the SD?
thank for your answers.
Click to expand...
Click to collapse
Hi all.
I am interesting too. Its possible?
dvc said:
Hi all.
I am interesting too. Its possible?
Click to expand...
Click to collapse
Hi,
Please someone help, I am interested TOOOOOOOOOOOOOOOOO.
I mistakenly installed a G4 Rom in my G3 device, now its only showing Three color screen & not accepting any ROM.
Please help....................
flash with the NoVendor-ID Dopod Rom from the FTP...
To boot from a program, create a folder entitled "MCSTART" which contain a programme call "AUTORUN.EXE". When you insert card, windows will copy executable and launch it with parameter "install" (and when you remove it, windows relaunch app with "unsinstall parameter")
So maybe you can create an executable that launch ROM update
rodigezstyle said:
flash with the NoVendor-ID Dopod Rom from the FTP...
Click to expand...
Click to collapse
Tried but not helping.......
Hi ,
i tried to update the mcu LY with usb stick but i forgot to cancel the dmcu.img of previously GS radio that was in the sd in GPS slot. So the mcu system updated the GS file and not the LY. The system restarted correctly but i had the alert on android "wrong update" in red. So i updated the mcu to the correct LY dmcu.img file , but now the volume knob give me no response and i don't have the original dmcu.cfg to restore.
What i can do? Thanks
Factory settings.
marchnz said:
Factory settings.
Click to expand...
Click to collapse
which menu of factory settings? thanks
bluemask69 said:
which menu of factory settings? thanks
Click to expand...
Click to collapse
Knob from memory.
marchnz said:
Knob from memory.
Click to expand...
Click to collapse
in "other" menu? i found only a "knob mode" with some parameters to select
SOLVED with this post
https://forum.xda-developers.com/showpost.php?p=79758323&postcount=2
Hey Guys
Ive got a really big Problem at my PX5 Device Android 8.
After i Update the mcu File with the correct Suffix (HLA), my Volume Control Drives crazy. The whole time it trys to lvl Up the Volume, and i cant Touch anything, because ItS Always Displays.
Pls Help me.
Find the proper mcu file(s) [img and cfg]. Copy to USB stick.
Reboot to recovery. Choose "Apply update mcu". Keep the fingers cross !
Good luck !
Ive already done this with different mcu Files, but IT doesnt Help
And i only found IMG Data Not the correct cfg File? Where i can get this?
Schimanski91 said:
Hey Guys
Ive got a really big Problem at my PX5 Device Android 8.
After i Update the mcu File with the correct Suffix (HLA), my Volume Control Drives crazy. The whole time it trys to lvl Up the Volume, and i cant Touch anything, because ItS Always Displays.
Pls Help me.
Click to expand...
Click to collapse
Factory settings....
And Then?
In Factory settings click "Export" (if you can do it...). Copy the resulted cfg file to stick, near to img.
Okay cfg and mcu IMG? Both?
Yes, both.
Does it Matter that i only have an mtcd 2.56 hla With a cfg from 2.47? Or not?
It doesn't matter !
It doesnt Work, what can I do now?
Factory settings; knob
I cant Access it, because of the permanent Volume Control :/
1.What mcu.img did you used to upgrade ?
2.Erase mcu.img from stick, leave just mcu.cfg. Reboot to recovery, update mcu, choose mcu.cfg.
3.If your PC device it's connected through CAN-BUS adapter to your car, try to disconnect this adapter...
1. MTCD HLA 2.56
2. It doesnt Work :/
3. I will try
Did you tried with your old (original version) mcu.img ?? Or, at least, an different , lower, version, not 2.56 ?!?
I Cant find my Old Version in the Internet so i cant try it.
But Ive tried 2.41 and 2.45 for example but the Problem was'nt solved
Check your mail for 2.56.
Ive tried the Same, but the Problem wasnt Solved.
Hi All,
I wanted to find the file that I need to use to update my Head Unit, had an issue and it displays an error saying "Canbus Serial port:/dev/ttyS1 was used! !" and unabled my steering buttons.
Does anybody knows which file or where can I look for it?
Thanks in advance!
MCU Version: 2021.03.16 18:42:45 NOR_812_F2N_G23P32f32_Ver: 1.0(FYT)
Device: sp7731e_1h10
And what did your reseller say?
I would not simply write another MCU firmware over my head unit.
And how did this happen? Did you already flash it with another firmware?
I chated with the reseller and indeed told me that I had reload the can Box files, for such thing, unfortunately after many atempts asking for such file the reseller simply would not provide such file, thats why I try to research for an alternative download.
being completly new to this I was playing around with the configurations and tried to upload a new firmware without having selected any , so I guess the configurations messed up afterwards.
I have seen many different firmwares for the head unit , but the head unit works fine excepting the steering controls , so I am not sure if I have to update the firmware of the entire headunit, or the MCU or the CAB Box configurations.
Is there any known library or repository for many known versions of such firmwares so I can take the closest one to it? and hope to not trash the entire head unit?
Thanks in advance!
Your s7731 is less wide spread than the uis7862 or uis8514. There are not so many and not so many in this forum. In this case you might take a look on 4pda.
did you find any solution ?
i think have same radio as you
Where did you get your ?
Any luck finding a newer MCU update ?
royo210 said:
I chated with the reseller and indeed told me that I had reload the can Box files, for such thing, unfortunately after many atempts asking for such file the reseller simply would not provide such file, thats why I try to research for an alternative download.
being completly new to this I was playing around with the configurations and tried to upload a new firmware without having selected any , so I guess the configurations messed up afterwards.
I have seen many different firmwares for the head unit , but the head unit works fine excepting the steering controls , so I am not sure if I have to update the firmware of the entire headunit, or the MCU or the CAB Box configurations.
Is there any known library or repository for many known versions of such firmwares so I can take the closest one to it? and hope to not trash the entire head unit?
Thanks in advance!
Click to expand...
Click to collapse
Have u found mcu file ?
ghannaiem said:
Have u found mcu file ?
Click to expand...
Click to collapse
I got this file from the seller after asking a lot, but unfortunately I haven't been able to execute the file, if anyone can execute this correctly can u give advice on how to proceed?
royo210 said:
I got this file from the seller after asking a lot, but unfortunately I haven't been able to execute the file, if anyone can execute this correctly can u give advice on how to proceed?
Click to expand...
Click to collapse
Thanks for sharing .
File is old and does not contain MCU.
MCU unlikely to be issue
marchnz said:
Thanks for sharing .
File is old and does not contain MCU.
MCU unlikely to be issue
Click to expand...
Click to collapse
Then what does that File contains?
How can you tell?
royo210 said:
I got this file from the seller after asking a lot, but unfortunately I haven't been able to execute the file, if anyone can execute this correctly can u give advice on how to proceed?
Click to expand...
Click to collapse
Mcu file should be named as "mcuall.bin "
Unfortunately they do not provide it with firmware update . any way thanks so much for the link and i'll use the firmware you provide hoping it will fix the problem
ghannaiem said:
Mcu file should be named as "mcuall.bin "
Unfortunately they do not provide it with firmware update . any way thanks so much for the link and i'll use the firmware you provide hoping it will fix the problem
Click to expand...
Click to collapse
What Issue you have and are trying to solve with this firmware?
royo210 said:
What Issue you have and are trying to solve with this firmware?
Click to expand...
Click to collapse
If car is parcked for more than 48 hours headunit goes to deep sleep then when start using and ignition is on it stuck on boot logo and it wont boot until i force restart it with reset button
ghannaiem said:
Mcu file should be named as "mcuall.bin "
Click to expand...
Click to collapse
Are you sure?
I believe the OP's device uses an MCU file named stm32ud.bin, just like other FYT devices.
Hi me also with this device is there any update or can the android be changed thanks
j0hn83 said:
Are you sure?
I believe the OP's device uses an MCU file named stm32ud.bin, just like other FYT devices.
Click to expand...
Click to collapse
Stm32ud is for Gd32f-------- mcu types like in teyes cc2l/plus
While my device and also @royo210 's device use another type mcu chip here below is a picture for
And it is named in the system info as
NOR_812_F2N_G23P32f32_Ver: 1.0(FYT)
royo210 said:
Canbus Serial port:/dev/ttyS1 was used!
Click to expand...
Click to collapse
this is caused by BSP Serial Debug option in Developers Settings. Disable it and never enable again
do not try to flash any mcu firmware just for fun, you might not be able to revert this back and i think 100% this won't help you with steering wheel buttons
Does someone who can help me to find the firmware and the MCU for this one?
Intel Sofia3gr Rockchip RK30SDK
MCU: FY_90_C9_7703_18EM_JY2009B
Security patch level: 01-06-2016
As my joying head unit only allows certain devices to connect due to Joying Bluetooth crippling, would adding a Bluetooth dongle allow other devices, or will the limitations still apply to the USB input?
looking for the same answer. Apparently older models could use Bluetooth dongle so long as it was the same exact Bluetooth chipset found inside the android head unit. Secondly, the Bluetooth config has to be altered to use the external dongle instead of the internal chipset. This was ~2017 era. So far nobody has fixed the Bluetooth exclusivity limitations. The only other way is if you have the FYT 7862 headunits and use custom firmware and rom to bring back bluetooth control thru the custom FYT mamager.
Tricky13 said:
As my joying head unit only allows certain devices to connect due to Joying Bluetooth crippling, would adding a Bluetooth dongle allow other devices, or will the limitations still apply to the USB input?
Click to expand...
Click to collapse
Does Bluetooth only reconnect to the last device used?
My unit allowed me to pair multiple phones (my wife and daughter also drive) but the Bluetooth system would only reconnect to the last phone used. So if I drove the car last, and then my wife drives, it won't connect to her phone without manually...
forum.xda-developers.com
Follow that thread, it might turn out useful
this is the best thing to happen to android HUs. You need YFT models for this firmware to work. https://forum.xda-developers.com/t/...dition-with-fmc.4542673/page-30#post-88513899
Unfortunately, nothing that would help my head unit in that thread.
Onkypig said:
looking for the same answer. Apparently older models could use Bluetooth dongle so long as it was the same exact Bluetooth chipset found inside the android head unit. Secondly, the Bluetooth config has to be altered to use the external dongle instead of the internal chipset. This was ~2017 era. So far nobody has fixed the Bluetooth exclusivity limitations. The only other way is if you have the FYT 7862 headunits and use custom firmware and rom to bring back bluetooth control thru the custom FYT mamager.
Click to expand...
Click to collapse
Thank you for that must be the first understandable and helpful comment I have had so far.
On a side note, I tried a Bluetooth mouse and that worked with its own dongle.
Tricky13 said:
On a side note, I tried a Bluetooth mouse and that worked with its own dongle.
Click to expand...
Click to collapse
So does a BT keyboard. I use that when I need to type a lot on my unit, for example when using the linux terminal.
But a Bluetooth dongle will not help at all.
But you are asking the same question again and again and do it by cross-posting in several threads. I already pointed you to the same thread as @louforgiveno did in post #3.
It DOES contain relevant information for your unit and it DOES contain the info you need to be able to pair more devices. I think it is because you only look at the title or because you don't understand it or did not read it completely, but it exactly gives the information you need.
It doesn't help to ignore that.
I do not understand either why you mention that the reply from @Onkypig is understandable. It leads to one of my posts explaining a flashing issue due to a corrupt USB-stick. There is no relevance at all to this question.
As I said before I am a newbie to doing anything to tweak Android head units or anything Android for that matter, and so far all I get is pointed to threads that apparently are supposed to be of some help but most of which I don't understand, but the end result is I just get criticised for not posting in the right place (this forum is bloody confusing to a newbie!) and not being able to understand the jargon instead of being offered help, so pardon me for being uneducated in Android.
Being new to "something" is OK. We all started that way. But you were saying that that thread that was mentioned by both @louforgiveno and myself was not (relevant) for your unit. By saying that you give a totally different impression to us.
Check what value your sys.fyt.bluetooth_type is.
- If you have your original firmware, check the config.txt
- If you don't have that, then check it yourself
- If you don't know how to do that, then download, install and run my HWGetInfo (from my signature below my posts). It will show you.
If the value is 1, create a config.txt containing sys.fyt.bluetooth_type=0
If the value is 0, create a config.txt containing sys.fyt.bluetooth_type=1
Save that text file onto a clean usb-stick and copy the lsec6315update from your Joying firmware also on that usb-stick, and nothing more than those two files.
Flash your unit with this and try again.
If it doesn't work, replace the value in your config.txt and put the original value back in. Flash that again.
surfer63 said:
Being new to "something" is OK. We all started that way. But you were saying that that thread that was mentioned by both @louforgiveno and myself was not (relevant) for your unit. By saying that you give a totally different impression to us.
Check what value your sys.fyt.bluetooth_type is.
- If you have your original firmware, check the config.txt
- If you don't have that, then check it yourself
- If you don't know how to do that, then download, install and run my HWGetInfo (from my signature below my posts). It will show you.
If the value is 1, create a config.txt containing sys.fyt.bluetooth_type=0
If the value is 0, create a config.txt containing sys.fyt.bluetooth_type=1
Save that text file onto a clean usb-stick and copy the lsec6315update from your Joying firmware also on that usb-stick, and nothing more than those two files.
Flash your unit with this and try again.
If it doesn't work, replace the value in your config.txt and put the original value back in. Flash that again.
Click to expand...
Click to collapse
Tricky13, for real this is the answer and it was in that thread. One thing you'll learn if you hang out here long enough, is that @surfer63 usually has the answer and there aren't many, if any, who know these units better than him.
surfer63 said:
Being new to "something" is OK. We all started that way. But you were saying that that thread that was mentioned by both @louforgiveno and myself was not (relevant) for your unit. By saying that you give a totally different impression to us.
Check what value your sys.fyt.bluetooth_type is.
- If you have your original firmware, check the config.txt
- If you don't have that, then check it yourself
- If you don't know how to do that, then download, install and run my HWGetInfo (from my signature below my posts). It will show you.
If the value is 1, create a config.txt containing sys.fyt.bluetooth_type=0
If the value is 0, create a config.txt containing sys.fyt.bluetooth_type=1
Save that text file onto a clean usb-stick and copy the lsec6315update from your Joying firmware also on that usb-stick, and nothing more than those two files.
Flash your unit with this and try again.
If it doesn't work, replace the value in your config.txt and put the original value back in. Flash that again.
Click to expand...
Click to collapse
Thank you for explaining, I have used the HWGetinfo and found the sys.fyt.bluetooth_type=1 however not sure what/where the lsec6315update is, and how do you flash this to the unit?
Does the USB stick need to be formatted to anything in particular?
Tricky13 said:
Thank you for explaining, I have used the HWGetinfo and found the sys.fyt.bluetooth_type=1 however not sure what/where the lsec6315update is, and how do you flash this to the unit?
Does the USB stick need to be formatted to anything in particular?
Click to expand...
Click to collapse
The USB-stick must be formatted as FAT32.
Unzip below zip onto it.
Put it in your unit and it will flash automatically.
After reboot test your BT devices.
If it did not help, change the value in the config.txt back to 1 and flash again to "restore" to original state.
dishe2 said:
Tricky13, for real this is the answer and it was in that thread. One thing you'll learn if you hang out here long enough, is that @surfer63 usually has the answer and there aren't many, if any, who know these units better than him.
Click to expand...
Click to collapse
Must admit that I wish I understood coding, but I admire those that can write and understand it.
surfer63 said:
The USB-stick must be formatted as FAT32.
Unzip below zip onto it.
Put it in your unit and it will flash automatically.
After reboot test your BT devices.
If it did not help, change the value in the config.txt back to 1 and flash again to "restore" to original state.
Click to expand...
Click to collapse
Many thanks for your help and patience, I will give it a try and report back.
Tricky13 said:
On a side note, I tried a Bluetooth mouse and that worked with its own dongle.
Click to expand...
Click to collapse
Any "Bluetooth mouse" with its own USB adapter is probably not actually Bluetooth.
It's simply a wireless mouse using the 2.4 GHz ISM band for communication.
To see if this is the case just plug the USB adapter into a desktop and look at the USB configuration descriptor.
That's lsusb -v in Linux or the usbview.exe utility in Windows.
What you'll see is what looks like a wired USB mouse, not a Bluetooth adapter.
surfer63 said:
The USB-stick must be formatted as FAT32.
Unzip below zip onto it.
Put it in your unit and it will flash automatically.
After reboot test your BT devices.
If it did not help, change the value in the config.txt back to 1 and flash again to "restore" to original state.
Click to expand...
Click to collapse
Just before I go ahead, I am using the latest update firmware ...
Here is the firmware for 10.1" 1920*1200:
Updated files please click Here.
Applicable Radio Models: UQS10N4G-H, UQS10N6G-H, UQD10N4G-H, UQD10N6G-H
Just wanted to check this is OK ?
Tricky13 said:
Just before I go ahead, I am using the latest update firmware ...
Here is the firmware for 10.1" 1920*1200:
Updated files please click Here.
Applicable Radio Models: UQS10N4G-H, UQS10N6G-H, UQD10N4G-H, UQD10N6G-H
Click to expand...
Click to collapse
I don't understand. Do you mean to use this as backup?
Or do you want to use it to flash? This you should not do. Only the files I put in that zip. The only thing is that if it doesn't flash, you take the lsec6315update out of the firmware and copy that onto the usb-stick.
surfer63 said:
I don't understand. Do you mean to use this as backup?
Or do you want to use it to flash? This you should not do. Only the files I put in that zip. The only thing is that if it doesn't flash, you take the lsec6315update out of the firmware and copy that onto the usb-stick.
Click to expand...
Click to collapse
No I mean that is the firmware I am currently using, I updated late last year, and I just wanted to check that it was OK to go ahead with using the one you provided as I know Joying use different for each display resolution.
Tricky13 said:
No I mean that is the firmware I am currently using, I updated late last year, and I just wanted to check that it was OK to go ahead with using the one you provided as I know Joying use different for each display resolution.
Click to expand...
Click to collapse
In the zip file surfer63 gave you is 2 files, not a firmware. An lsecupdate file that doesn't actually do anything other than tell the unit it is to be flashed. There's also a config.txt file with a single line, making only 1 change.
If it doesn't have the desired effect, change the 0 to a 1 in the config.txt, flash it again and everything will revert back to how it was.
It matters not what device you have or what firmware you are running.
j0hn83 said:
In the zip file surfer63 gave you is 2 files, not a firmware. An lsecupdate file that doesn't actually do anything other than tell the unit it is to be flashed. There's also a config.txt file with a single line, making only 1 change.
If it doesn't have the desired effect, change the 0 to a 1 in the config.txt, flash it again and everything will revert back to how it was.
It matters not what device you have or what firmware you are running.
Click to expand...
Click to collapse
Thank you! It always pays to double-check when you don't know exactly what you're doing.
Well, Bluetooth is still not connecting to the devices I want, but I now have an inverted screen!! Any ideas how to change this back?
I am going to revert the Bluetooth config back to as before, but no idea why the screen is now inverted?
At least being Joying, I can just spin it around on the mounts, but it's still very odd that It's become inverted?