I recently upgraded to the eonon GA6151 and was trying to flash update_RK3188_1024x600.img " booroondook RK3188" , well I renamed the file wrong to dupate.img instead of update.img I started flashing it and it was too late before I realized. Now the unit will not boot up or go to recovery. I can reset it and see the buttons flash like it wants to go to recovery but nothing ever appears on the screen. Is there a way to adb into this unit? Can I put files on a card and have it auto install them? Any help would be appreciated.
I am moving this to the MTCB section sorry for posting in the wrong place.
Hi guys.
I really need help.
Im a rookie, but ready to try installing.
I have a Eonon GA8153 -android 7.1, 2 GB, quad-core processor, 1024x600. in my VW Golf.
It is dead.
I can go into recovery, but from there nothing happens.
I think I need to re-install an androidsystem, not Update one.
I think everything is erased on the unit.
When I reboot, all that happens is the EONON-logo keeps switching on and off.
Is there somewhere I can download a file I can install thru SD-card?
Thanks in advance!
Anyone?
Please help
I think I need to install a ROM, not an update.
Is that possible for android 7.1.1 ?
My unit only goes into recovery. It cannot start.
Have you reached out to Eonon on their support mediums to see if they have a ROM you can flash in recovery?
Yes, I've contacted them, but this is my third eonon-unit that does not work, and Im getting pretty tired of the company.
Sorry to hear. So did they say they didn't have an image you could flash?
What happened too the unit? It just stop working all of a sudden?
No
They sent me an update file but it just destroyed the system.
Hello.
I have a Joying Device with 4GB/32GB and a FYT_6026 SOM.
I installed this root and after that I installed magisk and he patched the boot image. after reboot, now I am stuck here in a bootloop.
bootloop: press power button, wait 2 sec, it displays the car logo for 2 sec, 3 sec black screen, 500ms this no command screen, rebooting ...
How can I recovery / reflash the firmware?
I searched a lot here in the forum now. gtxaspec posted some nice information about the device here: it is pincompatible with FYT_6021 Intel SoFIA SoM.
I tried that! It loads something, but skip the update because its the same firmware or so????
and he wrote this: " *The stock rom has /system/bin/install-recovery which uses a patch file found in the root directory and patches the boot image to create and restore the recovery image on every boot, if it has been modified."
what does that mean? the device should fix his boot image himself, or only the recovery image, on every reboot?
There is no update.img in the joying firmware.zip, so I can't create a microSD card with RockChip SD Card Tools!
The Device have a recessed power and recovery button (on top left).
I do not know the button combo to boot to recovery. tried many combos. no chance.
can somebody help me please? how can I recover the boot image?
packyman said:
How can I recovery / reflash the firmware?
I searched a lot here in the forum now. gtxaspec posted some nice information about the device here: it is pincompatible with FYT_6021 Intel SoFIA SoM.
Click to expand...
Click to collapse
Take a Joying firmware and put it on USB-stick or SD-card.
Put it in your Joying, remove all other mass storage devices (if applicable) and reset it with a needle or so. The moment you see the bootlogo appear, you press reset again. Dot that 3 times. If you have hardware buttons they will now flash pink and then the unit will "force flash" and reflash your unit with the stock joying rom
Hopefully that works.
But do not flash Magisk. It will soft-brick your unit, which is also mentioned in one of gtxaspecs posts.
thanks for your reply. after reading it, I wanted to execute your instructions. I started the device, inserted the microSD card with firmware
and at this moment, the firmware update started immediatelly! a coincidence!
device is now fixed. your instruction maybe I will test later again.
Boa noite
Você conseguiu fazer o ROOT?
Eu tenho um rádio JOYING PX5 com Android 8.1.0 e não sei como root nele
chrisgaio1 said:
Boa noite
Você conseguiu fazer o ROOT?
Eu tenho um rádio JOYING PX5 com Android 8.1.0 e não sei como root nele
Click to expand...
Click to collapse
If you have 8.0.0, see here (or my signature below this post). As fas as I know Joying does not have units with 8.1.0.
Do NOT abuse other topics for your rooting questions
Edit: I do now see that the PX5S models do have 8.1.0, but they are not FYT models. rooting will work, but Xposed and the JET apk not.
surfer63 said:
Take a Joying firmware and put it on USB-stick or SD-card.
Put it in your Joying, remove all other mass storage devices (if applicable) and reset it with a needle or so. The moment you see the bootlogo appear, you press reset again. Dot that 3 times. If you have hardware buttons they will now flash pink and then the unit will "force flash" and reflash your unit with the stock joying rom
Hopefully that works.
But do not flash Magisk. It will soft-brick your unit, which is also mentioned in one of gtxaspecs posts.
Click to expand...
Click to collapse
sir
i have similar issue that my unit is not lunch any more except the logo(JOYING ) for 2 second and the screen become black
i have the firmware which i use before but after when i use custom recovery the unit is not lunching any more
can you help me please
helmi_zr1 said:
sir
i have similar issue that my unit is not lunch any more except the logo(JOYING ) for 2 second and the screen become black
i have the firmware which i use before but after when i use custom recovery the unit is not lunching any more
Click to expand...
Click to collapse
Which custom recovery? There is no custom recovery for this unit.
Please don't tell me you somehow managed to write the Sofia custom recovery to you head unit which is completely different than the Sofia it was meant for?
surfer63 said:
Which custom recovery? There is no custom recovery for this unit.
Please don't tell me you somehow managed to write the Sofia custom recovery to you head unit which is completely different than the Sofia it was meant for?
Click to expand...
Click to collapse
sir
yes that what happend i have been used this APK in my head unit
custom V4_9
https://forum.xda-developers.com/android-auto/android-head-units/rom-gtx-joying-stock-rom-2018-01-29-t3742482
form this link i was think that will help me to install the original firmware but dos not
also i have been trying to recovery the unit using bu usb to usb ( Android Tool ) but that not helping also :crying:
here the video
https://www.youtube.com/watch?v=WzawTy4XmII
helmi_zr1 said:
sir
yes that what happend i have been used this APK in my head unit
custom V4_9
Click to expand...
Click to collapse
I really don't think you can fix this. I have no idea.
You really need to ask Joying. This might mean you need to send the unit to them so they can fix it.
surfer63 said:
I really don't think you can fix this. I have no idea.
You really need to ask Joying. This might mean you need to send the unit to them so they can fix it.
Click to expand...
Click to collapse
actually sir this unit is not from joying company its has same firmware of joying
any how i'll check with KLYDE company since this unit from sister company of them and may they can support
thank you for your time
helmi_zr1 said:
any how i'll check with KLYDE company since this unit from sister company of them and may they can support
Click to expand...
Click to collapse
You might try: https://szklyde.en.alibaba.com/contactinfo.html?spm=a2700.icbuShop.88.89.2bab6556Fug3af
surfer63 said:
You might try: https://szklyde.en.alibaba.com/contactinfo.html?spm=a2700.icbuShop.88.89.2bab6556Fug3af
Click to expand...
Click to collapse
noted , i'll send email to her now , thank you
acutely i am not get any respond from KLYDE yet
should i throw the unit away and get another new one ? or there's solution to fix it
helmi_zr1 said:
acutely i am not get any respond from KLYDE yet
should i throw the unit away and get another new one ? or there's solution to fix it
Click to expand...
Click to collapse
I am afraid you can't fix it yourself.
When first flashing these units, when they are still "empty and clean", they use special methods to connect certain pins on the CPU and/or MCU and/or EMMC and directly "raw write" the complete firmware to the EMMC.
I have no idea which pins to connect or what tools or hardware to use.
And as you can read from my reaction: I know it is "somehow" possible but I have no clue either.
surfer63 said:
I am afraid you can't fix it yourself.
When first flashing these units, when they are still "empty and clean", they use special methods to connect certain pins on the CPU and/or MCU and/or EMMC and directly "raw write" the complete firmware to the EMMC.
I have no idea which pins to connect or what tools or hardware to use.
And as you can read from my reaction: I know it is "somehow" possible but I have no clue either.
Click to expand...
Click to collapse
thank you for your trying to support and i will keep trying till end, i believe may i can fix it by somehow
surfer63 said:
I am afraid you can't fix it yourself.
When first flashing these units, when they are still "empty and clean", they use special methods to connect certain pins on the CPU and/or MCU and/or EMMC and directly "raw write" the complete firmware to the EMMC.
I have no idea which pins to connect or what tools or hardware to use.
And as you can read from my reaction: I know it is "somehow" possible but I have no clue either.
Click to expand...
Click to collapse
Hi surfer63
i would like to add somethings
i have been keep the power on directly to my unit and after 7 minute the logo (joying) appear for 2 second and get the screen black again
so i keep the power continue then i notice that logo appear every 7 minute
is that signs for some things?
helmi_zr1 said:
Hi surfer63
i would like to add somethings
i have been keep the power on directly to my unit and after 7 minute the logo (joying) appear for 2 second and get the screen black again
so i keep the power continue then i notice that logo appear every 7 minute
is that signs for some things?
Click to expand...
Click to collapse
Yes, I assume so. I forgot one thing.
The Joying PX5 units (the FYT units) do have a "self restore" mechanism for recovery. Upon boot the recovery image is always written to the recovery partition if the unit discovers that the recovery partition has been changed. That happens from the /system/bin/install-recovery.sh. I think your unit has that as well. So also if you have written a bad recovery image, it should be overwritten again.
I assume your unit is trying that.
Maybe you could try again with a fresh firmware from an SD-card.
Reset the unit 3 times.
Wait till you see the log, press RST with a pointy thing like a needle or so.
Do that 3 times.
On the 3rd time (or the 4th) the leds might blink purple. If they do that, let it go further and it might flash the firmware again.
surfer63 said:
Yes, I assume so. I forgot one thing.
The Joying PX5 units (the FYT units) do have a "self restore" mechanism for recovery. Upon boot the recovery image is always written to the recovery partition if the unit discovers that the recovery partition has been changed. That happens from the /system/bin/install-recovery.sh. I think your unit has that as well. So also if you have written a bad recovery image, it should be overwritten again.
I assume your unit is trying that.
Maybe you could try again with a fresh firmware from an SD-card.
Reset the unit 3 times.
Wait till you see the log, press RST with a pointy thing like a needle or so.
Do that 3 times.
On the 3rd time (or the 4th) the leds might blink purple. If they do that, let it go further and it might flash the firmware again.
Click to expand...
Click to collapse
thank you i'll try with that way hopefully get my unit a live again
otherwise i'll go for new one since i try to search for FYT_6026 core board but i could not find any suppler how can sale this things
surfer63 said:
Yes, I assume so. I forgot one thing.
The Joying PX5 units (the FYT units) do have a "self restore" mechanism for recovery. Upon boot the recovery image is always written to the recovery partition if the unit discovers that the recovery partition has been changed. That happens from the /system/bin/install-recovery.sh. I think your unit has that as well. So also if you have written a bad recovery image, it should be overwritten again.
I assume your unit is trying that.
Maybe you could try again with a fresh firmware from an SD-card.
Reset the unit 3 times.
Wait till you see the log, press RST with a pointy thing like a needle or so.
Do that 3 times.
On the 3rd time (or the 4th) the leds might blink purple. If they do that, let it go further and it might flash the firmware again.
Click to expand...
Click to collapse
Hello
i have been trying many way but i think my unit is not going to work
i need to ask one quotation what about if i put new FYT 6026 core to my unit is that will help to fix the issue
helmi_zr1 said:
Hello
i have been trying many way but i think my unit is not going to work
i need to ask one quotation what about if i put new FYT 6026 core to my unit is that will help to fix the issue
Click to expand...
Click to collapse
You can ask for a new PX5 motherboard. Most probably you can also go for a new 9853i motherboard (my PX5 unit can). If you want that you have to ask Joying.
Hi. I have a XTRONS PSD60UNK. Loved the design and UI of the radio...
I was wanting to root the unit to replace the default Android boot animation with a vehicle specific boot animation that I obtained elsewhere here on XDA.
I followed the instructions on post #100 of this thread (https://forum.xda-developers.com/showpost.php?p=80550729&postcount=100) for gaining root access BUT UNFORTUNATELY FORGOT about the step about NOT allowing SuperSU UPDATE the binary. Otherwise it looks like it would have been successful. Now I have a brick.
Yes I know --- call me an ID10T!!
Can anyone please assist me with resolving my issue so I can get my HU working again?
I exported a file from the unit to an SD card, which I believe is named TS907.BIN.
Right now the unit boots with vehicle boot image I initially selected, then a default Android logo ( I was able to rename the boot_animation.zip file to boot_animation.old while doing the ADB) but the boot up doesn't go any further.
I can't seem to get it into recovery mode but don't know what to do if I did anyway.
Thanks in advance for any replies and assistance.
Update
I was able to continue looking at threads here and found out how install the 8227L firmware. Different UI than the initial XTRONS UI that was on the HU but I'm working now. I'm going to see if I can get the proper files from XTRONS to get the initial UI back.
XDA is a GREAT forum for info and troubleshooting.
Hello, I have a Dasaita PX6 with hal9k mod installed and it can't start android, only the android name appears and nothing else. I've wiped from recovery but it still doesn't work. I want to know, if I can install the same android rom through the recovery or I have to follow another method to make it work. I am also talking to the manufacturer to send me the original firmware, but they only ask questions and do not give me solutions at the moment. It tells me to access the motherboard and send it a picture.
albertron said:
Hello, I have a Dasaita PX6 with hal9k mod installed and it can't start android, only the android name appears and nothing else. I've wiped from recovery but it still doesn't work. I want to know, if I can install the same android rom through the recovery or I have to follow another method to make it work. I am also talking to the manufacturer to send me the original firmware, but they only ask questions and do not give me solutions at the moment. It tells me to access the motherboard and send it a picture.
Click to expand...
Click to collapse
Refer my recovery posts - OTG, SDCard.
marchnz said:
Refer my recovery posts - OTG, SDCard.
Click to expand...
Click to collapse
thanks for answering. I have seen the tutorial of your signature, but I can't find a tutorial to do it through the SDcard
I have tried to reinstall the rom with an sd card from the recovery and it gives me an error.
I was able to solve it by installing the ROM from a USB. Now it works perfect!!!