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!!!
Related
Hi there,
I am searching for hours for a solution to my Problem and could not find the trick. Hopefully someone can help me here...
I am trying to get root on my Car Navi which uses Omnirom (4.4.2) issued by its manufacturer. I've read that one simply should flash supersu.zip in recovery mode. The problem is that there is no documentation on how to enter the recovery mode on the device. When flashing new firmware/android, one simply insert a sd card with the new firmware and the flashing process starts automatically on reboot.
Is there another way to get root access for Omnirom kitkat? I've tried Framaroot without luck.
Thanks for any help.
Greets.
tobias.s said:
Hi there,
I am searching for hours for a solution to my Problem and could not find the trick. Hopefully someone can help me here...
I am trying to get root on my Car Navi which uses Omnirom (4.4.2) issued by its manufacturer. I've read that one simply should flash supersu.zip in recovery mode. The problem is that there is no documentation on how to enter the recovery mode on the device. When flashing new firmware/android, one simply insert a sd card with the new firmware and the flashing process starts automatically on reboot.
Is there another way to get root access for Omnirom kitkat? I've tried Framaroot without luck.
Thanks for any help.
Greets.
Click to expand...
Click to collapse
Um, Omni does not currently ship preinstalled on any device, and as a result, it's impossible to be running Omni without access to a custom recovery, since you need a custom recovery to install Omni in the first place.
Whatever your navigation system is running, it is NOT Omni, and as a result, this is not the correct place to be posting about issues with your device.
Sorry if this is the wrong forum, I just went to omnirom.org and there was a link to this forum.
This is a little bit weird: Omni was not preinstalled but the update(Omni) came directly from the manurfacturer (sntron.com).
In my case no recovery mode is accessible. As I've written in the 1st post, I copied the update on a sd-card and booted from it so that the updated installs automatically.
Attached is a picture of what is installed.
Thanks for any info.
wtf...
This is weird. That would make this device an unofficial kang that not a single member of the Omni team was aware of until now...
LOOL
Sent from my N1 using Tapatalk
I installed an Eonon GA5153F the other day and I can't seem to figure out what MCU it is compatible with. From Eonon it comes with MCU: MTCB-ZD v2.68. I know the GA5153 is compatible with KLD but this one has that F at the end of the model number. Can I just install a pre rooted rom without messing with the MCU (flash only the rom and not the MCU)? I really want to install Malaysk's rom and have all that rooted goodness.
has anyone successfully installed Malaysk's rom on the GA5153F yet?
Hi I have a eonon I used this thread and its all ok its running KitKat 4.4.4
http://forum.xda-developers.com/showthread.php?t=2660662
Sent from my GT-P5210 using XDA Free mobile app
pcmender2005 said:
Hi I have a eonon I used this thread and its all ok its running KitKat 4.4.4
http://forum.xda-developers.com/showthread.php?t=2660662
Sent from my GT-P5210 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the reply. Is your a GA5153F? Im starting to think it is a JY unit now because it has the JY apps installed.
hippie131 said:
Thanks for the reply. Is your a GA5153F? Im starting to think it is a JY unit now because it has the JY apps installed.
Click to expand...
Click to collapse
No mine is a eonon GA5162 no trouble rooting it and updating it mate
Try this mate its jy rom
http://huifei.fs-fileserver.de/content/firmware/KK 4.4.4 Dualcore (Factory & DSA Rooted)/JY 4.4.4/
Sent from my GT-P5210 using XDA Free mobile app
Any update on this?
Have the same HU (Eonon GA5153F) and want to install a custom ROM and TWRP recovery, but can't find anything relevant to 'ZD' MCU.
I too have just installed the GA5153F in my car and while it's a good unit, I'd love root to be able to do a little more with it. Like yours, mine says ZD 2.68 and having only had it installed for a few hours, I'm nervous about flashing something that could brick it immediately!
Looking forward to hopefully getting some more information on this one soon
Just found the thread that tells you the access code you use in Factory Settings that gives you root - *#hct#root#
Think I'm gonna start there and see how it progresses..
You get root with that code, then you can install SuperSU from Play store and update su binaries (before restarting). Then you have fulltime root (tested).
Waiting for TWRP to do a nandroid backup before messing more with the system...
hi there, did you flashed any rom yet? i would love to have 2gb space for app...Malaysk's (mmm )i do have the same unit, ive rooted, installed xposed and a few modules, everything is ok till now!...
Upd - i did flashed Malaysk's ROM And all went fine much much better now!
You flashed the ROM from here http://huifei.fs-fileserver.de/cont...k/Malaysk Quadcore RK3188/800x480/09.09.2015/ without messing with MCU?
Did you change CAN-BUS settings or did they work out of the box (the default is VW simple if I remember correctly)?
no, was update_4_4_4_800X480_8_RK3188_MAL_19_10_2015 found here
http://forum.xda-developers.com/showthread.php?t=3246370
go down and you will found it!
maybe you have to change the bt(bluethooth), from 6 to 5 on factory settings
well i can tell you it worth flash this rom.....from 10 to 100% better
pedromaiaz said:
no, was update_4_4_4_800X480_8_RK3188_MAL_19_10_2015 found here
http://forum.xda-developers.com/showthread.php?t=3246370
go down and you will found it!
maybe you have to change the bt(bluethooth), from 6 to 5 on factory settings
well i can tell you it worth flash this rom.....from 10 to 100% better
Click to expand...
Click to collapse
Yeah, eventually I found the thread after some digging, and found there is this updated ROM version which is not on the server.
Now I have to find the time to try it
i have a MTCB-ZD-V2.81 what could it be? is a Eonon GA5163F
Maybe...its for mazda?....same specs i think!
yeah mines for mazda
I've got a GA5163F (for Mazda) as well and I have the MTCB-ZD-V2.81 MCU. How did you guys go about flashing Malaysk's ROM? I'm trying to follow the thread but I'm a little confused.
mokflurry said:
I've got a GA5163F (for Mazda) as well and I have the MTCB-ZD-V2.81 MCU. How did you guys go about flashing Malaysk's ROM? I'm trying to follow the thread but I'm a little confused.
Click to expand...
Click to collapse
i got it to install on mine. you can go to http://forum.xda-developers.com/showthread.php?t=3246370 for the latest firmware.
then RK3188 800x480
download the latest and extract it. from there it should have instructions on what to do.
if not put the "update.img" on the root of sd or usb (fat32), plug it in and enter recovery,
-To get into the Recovery Menu:
-Use a paper-clip and press and hold the RES button by the eject button for 3 seconds.
-Keep the RES button pressed and hold the power button for 3 seconds.
-Release the RES button, keep power button pressed
-Release the power button once the lights turn on.
Flashing the rom:
Malaysk Rom Only:
1. Wipe all the data/factory and cache reset.
Note: This will erase the flash memory and give 2 gb of instead of the 1 gb of factory application installation memory using the Malaysk Rom.
It will also delete the factory rom. No going back.
2. Update system/mcu image from usb.
Credit to this thread for instrutions:
http://forum.xda-developers.com/and...non-ga5151f-mazda-3-android-headunit-t3240475
kuraijay said:
i got it to install on mine. you can go to http://forum.xda-developers.com/showthread.php?t=3246370 for the latest firmware.
then RK3188 800x480
download the latest and extract it. from there it should have instructions on what to do.
if not put the "update.img" on the root of sd or usb (fat32), plug it in and enter recovery,
-To get into the Recovery Menu:
-Use a paper-clip and press and hold the RES button by the eject button for 3 seconds.
-Keep the RES button pressed and hold the power button for 3 seconds.
-Release the RES button, keep power button pressed
-Release the power button once the lights turn on.
Flashing the rom:
Malaysk Rom Only:
1. Wipe all the data/factory and cache reset.
Note: This will erase the flash memory and give 2 gb of instead of the 1 gb of factory application installation memory using the Malaysk Rom.
It will also delete the factory rom. No going back.
2. Update system/mcu image from usb.
Credit to this thread for instrutions:
http://forum.xda-developers.com/and...non-ga5151f-mazda-3-android-headunit-t3240475
Click to expand...
Click to collapse
Thank you so much! That's quite extensive and helpful. So I'm downloading (update_4_4_4_800X480_RK3188_10_MAL_11_12_2015.rar) and I see there's a READ ME.doc and update.img in it. I'm assuming the read me will have the instructions and the update.img is essentially the ROM? I'm familiar with flashing roms on my phones but I'm used to seeing ROMs in .ZIP formats.
Did you do a back up of any sort? Just want to make sure I'm not missing anything.. thanks!
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 am new to the forum and have never done any of this. I bought a Chinese Android radio, and because it lacks several options in the menu, I would like to change the start icon, and I see that to modify the Bootlogo I need to root. I have already done the OEM unlocking, I have tried with Kingoroot, it has not worked, and I am unable to access the recovery menu when starting the system, I cannot find the combination of keys to start it even by pressing the small "reset" button, Its a Fiat 500 radio type. I cant post the link. Thank you very much in advance.
Not Android auto, request moved to Android head units forum.
Javierlopcast said:
Hi, I am new to the forum and have never done any of this. I bought a Chinese Android radio, and because it lacks several options in the menu, I would like to change the start icon, and I see that to modify the Bootlogo I need to root. I have already done the OEM unlocking, I have tried with Kingoroot, it has not worked, and I am unable to access the recovery menu when starting the system, I cannot find the combination of keys to start it even by pressing the small "reset" button, Its a Fiat 500 radio type. I cant post the link. Thank you very much in advance.
Click to expand...
Click to collapse
I used Magisk when I was on Android 10 and it worked. Had to get a image from the stock firmware and patch it within the magisk app etc.
H4MZ4 said:
I used Magisk when I was on Android 10 and it worked. Had to get a image from the stock firmware and patch it within the magisk app etc.
Click to expand...
Click to collapse
Could you help me, can you tell me what steps to follow to get the image and then patch it? thank you very much friend