Help recovering a "bricked" MTCE, PX6 (Xtrons) unit - MTCD Android Head Units General

Hi all,
first post in this section, so be nice I have a very recent build Xtrons TQ700L unit that i have managed to soft(?) brick after rooting and removing a factory app ("Easy Connect"). On boot I get the initial logo, then after a long time a black screen that goes nowhere. I'm looking for advice on the best strategy to recover/rebuild it.
Hardware details...
build number:
rk3399-userdebug 10 QQ2A.200305.004.A1 eng.hct2.20200521.120545 test-keys
MCU version:
MTCE_GS_V3.53_3
As i understand it i have an "MTCE, GS" MCU and can ONLY flash MCU updates from the GS manufacturer. The MCU is probably not the problem here though.
I have a PX6, Android 10 build date of 20200521. Am I correct in saying i can flash any android 10 ROM designed for the PX6 that is newer than this date? Are the only differences between manufacturers cosmetic, like the nice launcher Xtrons supplies?
When i look on Yandex (https://yadi.sk/d/umCvHqCDzHccr), there is no PX6/Android 10 firmware at all from "GS", but there is from "HCT". Should i be looking at flashing the HCT/PX6/Android 10 firmware date 20200612 from the recovery menu? I can get to recovery easily enough by holding, then double clicking the reset button - i just dont know whether i should be flashing part of or the whole of the above package to fix my brick.
thanks.

So in case this helps anyone else, it was an easy fix. Baby steps below.
- grab the latest "Android 10", "PX6/RK3399" factory ROM either from threads here, or from Yandex. I found HA3_RK3399_10.0_ota(20200706).zip here on XDA.
- unzip the outer layer ZIP file and copy the inner "update.zip" to a micro SD card. The stock recovery systems dont allow any selection of ROM file names, so it must be update.zip.
- put the SD card in the "GPS" SD slot.
- with the unit on, reboot to recovery. My way was using a nail to hold the reset button in until the touch button lights began the flash, then quickly release and double click the reset again.
- in recovery, menu items can be scrolled through by either clicking the reset button, or (in my case) touching anywhere on the screen (easier).
- push and hold the rest button (or screen) to select the item.
- do a "wipe data/factory reset" (i guess) to be sure of cleaning out the old mess.
- then do "Apply update from SD card". it should automatically find the update.zip and apply it to all partitions.
- select reboot. Done.
The ROM i used was a "HA" branded generic ROM, so it didnt have the same launcher as my original "GS" (Xtrons) branded ROM. Xtrons wouldn't supply me with their stock ROM when i asked. The generic one was a little better anyway, since it has a stack of boot animations to choose from, whereas the Xtrons one only had the Xtrons logo. It also doesnt have the Easy Connect app, which is what I was trying to remove in the first place!
Additionally, i was able to obtain root easily by using the wifi ADB method here.

I did the same thing. Stupid app kept opening.
I don't have a micro sd card slot, hope it works with usb stick. Don't have one at the moment to try.
Same as yours.
Also, entering recovery mode you..
Hold reset button for 10 sec, release and immediately press it once.
I have a dicola px6 mtce
I'll update if i get it working.

Related

Official Diamond ROM 2.03 update - HELP

Hey guys,
I have no idea what's going on. I appreciate your suggestions. I flashed my Diamond many times (and other phones as well) with most of the ROM available. Unit a month ago or so I've been using the official 1.93 ROM with previously installed hard SPL 1.40. When I attempted to install a new 2.03 ROM I went through the whole procedure same way as always with a little exception. Right after completion - 100% the unit reboots, shows the rainbow screen with a message "Upgrade ROM code error" - try again. What is the world is this? I also have a message on my desktop "Error 270-update error" - The image file is corrupted. My unit is european and I downloaded the ROM from both US and Euro sites. From this point I managed to downgrade again to version 1.93. Then I ran again the hard SPL 1.40 and reattempted to upgrade to 2.03 - SAME THING!
I don't know what to do next. Why I cannot flush it with the latest ROM? Any ideas or similar situations? Please see picture.
Thanks
Same Thing happened to me :S wtf??
xevier69 said:
Hey guys,
I have no idea what's going on. I appreciate your suggestions. I flashed my Diamond many times (and other phones as well) with most of the ROM available. Unit a month ago or so I've been using the official 1.93 ROM with previously installed hard SPL 1.40. When I attempted to install a new 2.03 ROM I went through the whole procedure same way as always with a little exception. Right after completion - 100% the unit reboots, shows the rainbow screen with a message "Upgrade ROM code error" - try again. What is the world is this? I also have a message on my desktop "Error 270-update error" - The image file is corrupted. My unit is european and I downloaded the ROM from both US and Euro sites. From this point I managed to downgrade again to version 1.93. Then I ran again the hard SPL 1.40 and reattempted to upgrade to 2.03 - SAME THING!
I don't know what to do next. Why I cannot flush it with the latest ROM? Any ideas or similar situations? Please see picture.
Thanks
Click to expand...
Click to collapse
Hi have you tried to flash from the internal storage?
Have you tried flashing with internal storage method?
Exactly the same problem here, so I tried to flash to a really old original HTC ROM after the failure and it flashed fine
So I thought I would try upgrading over the top of an original ROM, had the same error , bloody HTC
So, any ideas how to resolve this issue? Are we stuck with the old ROM? I'm glad that I'm not the only one experiencing the same problem.
No, I have never tried to flash from internal storage. How can this be done? do I copy the whole .exe file to storage and run from there? Any pre-cautions?
Thanks
Though I bricked my phone when it happened, never seen that error before despite many ROM flashes
I have now tried tommytaos ROM which is supposed to be very close to the original but some with some tweaks.
http://forum.xda-developers.com/showthread.php?t=479049
It installed just fine on my phone. Seems HTC have broken their ROM
xevier69 said:
So, any ideas how to resolve this issue? Are we stuck with the old ROM? I'm glad that I'm not the only one experiencing the same problem.
No, I have never tried to flash from internal storage. How can this be done? do I copy the whole .exe file to storage and run from there? Any pre-cautions?
Thanks
Click to expand...
Click to collapse
it's the best way to flash the rom and the safest...
From Suiller thread:
the standard procedure to cook a ROM is made trough activesync program, I mean that the .nbh file is pushed into the phone trough activesync, across the usb cable, but this procedure can give some troubles:
1. it takes long time, about 10 minutes
2. it's a bit unsafe (even if the procedure can be always restored safely)
3. it's possible only with Windows OS (NO Linux nor *BSD, et cetera...)
I don't know why this is not well known but ALL producers (like HTC) give the possibility to upgrade the rom/firmware without having MS windows (thanks GOD someone knows that there aren't only windows users).
This faster procedure can be done also with *nix variants (or whatever you use) because the ROM update is made directly by the phone.
The procedure is very simple, it will take just 2 minutes, can be done everywhere & is good for cooking radios too (very fast in this case)
-= COOKING ROMs & Radios from phone =-
1. open from your PC the rar or zip archive and extract only the BIG .nbh file
2. rename as DIAMIMG.NBH
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!)
4. reset your device and within 3 seconds push together the Vol_Down + Back button (the one on the right above the hangup button) and keep pressed until the boot loader appears (the one with the color stripes)
5. soon as you see the bootloader stop to press those poor buttons
6. a very simple gray menu will appear asking you what to do, simple press the power button to perform the ROM/Radio upgrade
7. while the upgrade runs be patient and don't press again the power button, reset the device or play with it until it finishes, when finished a message "UPDATE SUCCESS" will appear, now you can safely reset your device
8. who prefer can perform a hard reset after the fresh cook (soon after reset simply press Vol_Down + Circle button, then when you see another simple gray menu choose Vol_Up to confirm format), even if this has no-sense because internal memory is pre-formatted during flash, but... there is always a but... for some unknown "scientific" reason sometimes an hard-reset can save time & headache
notes:
* be sure to have at least 10/20% of charge, anyway the whole procedure will take about 2 minutes, so you must be ensure that your mobile will stay turned on for at least those 2 dirty minutes (just in case you can attach the power AC/DC too), don't panic if something goes wrong... read few lines below
* like told you above the same procedure is good for cooking Radio too, of course Radio are smaller and it will be really fast (about one minute!)
* you don't need windows anymore or activesync, is enough just to copy the file into the storage card (transfers WITHOUT activesync are faster)
* it's possible to make a reset simply by getting off the stylus and pressing the small red button under the stylus carrier
* don't worry if something goes wrong... any cook failure can be always restored, the important thing is that you don't fail hardspl flash... but you have to do it just one time in your life
special note about hard-spl:
if you have signed-only hard-spl I strongly suggest to upgrade to an un-signed one, personally I tested many & I can confirm that the "good ones", at least in my experience, are the Olinex 1.37 or 1.93, you can find a copy here
remember also that you can NOT brick your device if you have a good hard-spl (like the ones I mentioned above) & flashing directly from phone is really faster (also good for flashing radio)
so the only one thing you should take care is when you change/upgrade the hard-spl, but you have to do this step just once, I'm using this hard-spl from about 6 months & I was able to flash everything (plus dozen recovers for failed flash)
for rom/radio upgrades you can safely also reboot/remove cable/turn off your phone while flashing ...every lost flash can be always restored safely, it's enough to restart your device in boot mode & restart flashing, also with cable trough the classic RUU (to put device in boot mode simply reset & keep pressed Vol_Down button)
In the hope this procedure can be useful at least to save time
if you have the official rom which is a exe file you can extract the rom file using winrar.
EUREKA!!! Done Deal!!!
Flashed from Internal Storage as per following directions:
-= COOKING ROMs & Radios from phone =-
1. open from your PC the rar or zip archive and extract only the BIG .nbh file
2. rename as DIAMIMG.NBH
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!)
4. reset your device and within 3 seconds push together the Vol_Down + Back button (the one on the right above the hangup button) and keep pressed until the boot loader appears (the one with the color stripes)
5. soon as you see the bootloader stop to press those poor buttons
6. a very simple gray menu will appear asking you what to do, simple press the power button to perform the ROM/Radio upgrade
7. while the upgrade runs be patient and don't press again the power button, reset the device or play with it until it finishes, when finished a message "UPDATE SUCCESS" will appear, now you can safely reset your device
8. who prefer can perform a hard reset after the fresh cook (soon after reset simply press Vol_Down + Circle button, then when you see another simple gray menu choose Vol_Up to confirm format), even if this has no-sense because internal memory is pre-formatted during flash, but... there is always a but... for some unknown "scientific" reason sometimes an hard-reset can save time & headache
THANKS! THANKS! THANKS!
Flashing using the Internal Method is the safest and most convenient way to flash. Spread the word.......
xevier69, Thanks for your thread
Having just purchased Oli's security unlocker... I was annoyed about this problem with a HTC official rom!
But your method has solved this issue!
Thanks again
Thanks guys it works perfect!
This just happened to me too and the only roms i have ever flashed:
1.37 official spanish: came with the phone
1.37 official WWE
1.93 official WWE
and now 2.03 official WWE fails.
WTF... One would expect the upgrade not to fail, right?
I wonder if they are checking for HardSPL to be original too!?
Anyway thanks for the workaround
This worked for me to
Cheers
xevier69 said:
EUREKA!!! Done Deal!!!
Flashed from Internal Storage as per following directions:
-= COOKING ROMs & Radios from phone =-
1. open from your PC the rar or zip archive and extract only the BIG .nbh file
2. rename as DIAMIMG.NBH
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!)
4. reset your device and within 3 seconds push together the Vol_Down + Back button (the one on the right above the hangup button) and keep pressed until the boot loader appears (the one with the color stripes)
5. soon as you see the bootloader stop to press those poor buttons
6. a very simple gray menu will appear asking you what to do, simple press the power button to perform the ROM/Radio upgrade
7. while the upgrade runs be patient and don't press again the power button, reset the device or play with it until it finishes, when finished a message "UPDATE SUCCESS" will appear, now you can safely reset your device
8. who prefer can perform a hard reset after the fresh cook (soon after reset simply press Vol_Down + Circle button, then when you see another simple gray menu choose Vol_Up to confirm format), even if this has no-sense because internal memory is pre-formatted during flash, but... there is always a but... for some unknown "scientific" reason sometimes an hard-reset can save time & headache
THANKS! THANKS! THANKS!
Click to expand...
Click to collapse
Thers some other option
Install twice from activesync 1st time = error, run for the second time the same version and OK it updates.
At least with my Diamond had worked
Cheers
Hi!
The same thing happend to me too... I think it's because of the serial number we have entered when we have downloaded that 100 MB ROM Update file from the HTC support site... well i think it doesn't match with the serial and IMEI of the phone that the upgraded rom checks at the end of the update process... so i think it's kind of a protection against piracy developed by htc... taiwanese idiots!
Hi!
pls anyone send any information about an rom update file that works and doesn't report errors after it installed 100%. pls specify it's rom version too! 2.03 would be great
thanks in advance
miriamscorob said:
pls anyone send any information about an rom update file that works and doesn't report errors after it installed 100%. pls specify it's rom version too! 2.03 would be great
thanks in advance
Click to expand...
Click to collapse
read all posts please
works like a charm folks! thank you!
g0x said:
Thers some other option
Install twice from activesync 1st time = error, run for the second time the same version and OK it updates.
At least with my Diamond had worked
Click to expand...
Click to collapse
I made this too for testing First flash: Error, Second time: Ok

Eonon GA6164F - Recovering from no Boot/Brick - MTCD - RK3188 - MTCD_KLD

Here are my notes regarding the Eonon GA6164F and recovering from a black screen, cant boot, cant get into recovery.
Thanks to all the members and information on this site who i was able to piece together to come up with this solution.
I still dont know if my assumptions are totally correct, (please comment if i need to learn more) .
--
Back Story : My device was shipped with a Dec 2016 Android 5.1.1 build, and my steering wheel keys on my Camry were not all working.
Skip track and Back track were doing the same action, I tried re-learning/mapping in "WheelKeys Study" but nothing fixed it.
I resorted to using Vol - + for volume, Skip forward = skip track, MODE button (underneth) as = skip back.
I contacted Eonon about this, and they gave me a new Android build to try, update.img.
I wasnt able to update using the Settings - About - Software Update. (Error finding file).
I wasnt able to update using the standard recovery options (RES button, power etc.)
I did notice it was looking for dupdate.img.
I renamed my update.img file to dupdate.img and it was able to install via the Settings - About - Software Update.
The device rebooted , installed, then nothing... just a black screen.
I couldnt get any display up no matter what i tried.
After 24 hours or so of testing/trailing etc. I did manage to get it back working.
Im certain it was a bad update file because once i had it working again, i re-applied the update file i was supplied and sure enough, it broke it again.
These are my notes on how i recovered it.
--
Reboot into recovery on a healthy device
----------------
Hold RES
Press Power
Release RES (while still holding power)
Let go of power 1-2 secs after
Should reboot into recovery
---
Boot into recovery and restoring on a un-healthy device
----------------------
If cant boot into recovery
Download a Malaysk android build file (you may need to sign up to the hosting server site, and then add to downloads, then you can download to your computer from there)
Create bootable SD card using 'rockchip create upgrade disk tool v1.4'
(Run .exe as admin, dont check 'SD Boot', just leave 'Upgrade Firmware'
(If you cant see your USB drive, check that you have right clicked-Run as Admin in windows on the .exe)
Select Malaysk MTCD dupdate.img file
First post has download links
https://forum.xda-developers.com/android-auto/mtcd-discussion-questions-development/rom-malaysk-roms-mtcd-device-t3385309
Fully power off device (unplug from the back/or remove neg battery from car).
Insert new-bootable SD card into GPS slot
Plug device back in (or reconnect neg. battery cable to car)
- Device will boot into recovery and complain about no update file (thats fine) the Bootable SD card is just to get you into recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once in recovery, remove the GPS slot SD card and plug in a USB stick with an update.img
(my machine was looking for dupdate.img so i had to rename it).
Press power button to skip down the settings
Hold power button to select an option
Select 'Update system/mcu image from usb and clear all'
<processing>
Device reboots
Toyota logo shows (never progresses)
Press RES
Device reboots
Toyota logo shows
Android is starting (optimizing app XX of XX)
Malaysk recomends once the build is installed, to reboot into recovery once again using the normal method of buttons (RES + Power etc.) and 'wipe all data/factory and cache reset'
--
Now i am running a 10.8 build, because i was having trouble with the Google services on the latest, and i need to learn more about the 11.4 build and the MicroG stuff that replaces the Google services.
I am still suffering from the steering wheel controls issue, but at this point... i dont care...
I found i am getting a lot of "unable to read file" from the m4a files i have on my SD or USB card/stick and i need to learn more about how to get the steering wheel controls to action "other" music apps, i believe this is to do with the MTCD-Keys stuff, but going from what seemed like a dead device to this point, i want to wait a while before i start playing with it again.
I have added pictures in the thread, but they are linked to a photobucket, so i have also added them as attachments in case that photobucket account ever goes down.
Eonon Issue HELP!!!!
I have a Eonon Radio similar to this unit except it originally had 4.2.2 on it I recently tried to update it to 4.4.4 and mcu 2.81 which worked perfectly until restarting the car overnight. Radio booted into cannot find e:\
I then reverted back to 4.2.2 but I can get to the 4.2.2 recovery mode but every update.img I try to use only puts me into a reboot mode of the KiKat screen Maylay Mod Splash. Anyone out there can help suggest something?
I seem to have a half baked system that I can get into the recovery mode for 4.2.2. but the update.img says it cannot find it in the GPS sd card.
rogerradio said:
I have a Eonon Radio similar to this unit except it originally had 4.2.2 on it I recently tried to update it to 4.4.4 and mcu 2.81 which worked perfectly until restarting the car overnight. Radio booted into cannot find e:\
I then reverted back to 4.2.2 but I can get to the 4.2.2 recovery mode but every update.img I try to use only puts me into a reboot mode of the KiKat screen Maylay Mod Splash. Anyone out there can help suggest something?
I seem to have a half baked system that I can get into the recovery mode for 4.2.2. but the update.img says it cannot find it in the GPS sd card.
Click to expand...
Click to collapse
There are no Eonon radios, Eonon sell radios from several different manufacturers, the one in this thread is a Klyde - KLD.
If yours was 4.2.2./4.4.2 and MCU 2.85 then you have an MTCB unit and you need to try in the MTCB forums.
I've downloaded the rockchip create upgrade disk tool v1.4 and ran through your instructions. The HU won't boot off the SD card. Just sits there. If I remove the SD card, it immediately boots into the installed ROM. (I want to downgrade)
Hi
I tried reinstall the malaysk firmware but i rename dupdate.img as update.img and after reinstall now my device do not turn on, only show black screen like off and appear turn on nothing, i tried apply different methods of reset but nothing worked.
Help please!
Rodrizio said:
Hi
I tried reinstall the malaysk firmware but i rename dupdate.img as update.img and after reinstall now my device do not turn on, only show black screen like off and appear turn on nothing, i tried apply different methods of reset but nothing worked.
Help please!
Click to expand...
Click to collapse
Can you put it in recovery ?
typos1 said:
Can you put it in recovery ?
Click to expand...
Click to collapse
I don't know how exactly. I push the reset and power button in the sequence of first post but nothing happens. Only every time pushed the reset button the device light flashes but it's look like off
Rodrizio said:
I don't know how exactly. I push the reset and power button in the sequence of first post but nothing happens. Only every time pushed the reset button the device light flashes but it's look like off
Click to expand...
Click to collapse
Try making a bootable sdcard.
Guys your help pls! My head unit is stuck to the initial logo (Navigation System) and there seems to be nothing I can do to get into recovery to re-install the software. I have tried everything described above, no way to get into recovery with buttons, so I made and SD bootable card with various firmwares but the HU does not seem to read the card (I tried also with a USB stick, with no luck).
Is there anything else I can try to get it to work again?
My HU is a Px3 MTCE KGL 2 GB.
Thanks a lot for your help!!
Bobek82 said:
Guys your help pls! My head unit is stuck to the initial logo (Navigation System) and there seems to be nothing I can do to get into recovery to re-install the software. I have tried everything described above, no way to get into recovery with buttons, so I made and SD bootable card with various firmwares but the HU does not seem to read the card (I tried also with a USB stick, with no luck).
Is there anything else I can try to get it to work again?
My HU is a Px3 MTCE KGL 2 GB.
Thanks a lot for your help!!
Click to expand...
Click to collapse
Try @marchnz's recovery method.
typos1 said:
Try making a bootable sdcard.
Click to expand...
Click to collapse
I tried boot with a Sdcard bootable created with rockchip create upgrade disk tool (my sdcard is a 8gb size. I don´t know if the size make a issue) with the Malaysk dupdate.img file but nothing happend.
I follow the next steps.
I unplug from the back my device and insert the SD card bootable into GPS slot.
I plug again the device from the back and nothig, only the same screen black like off, I try differents combination of keys (press RES+Power ) and nothing....:crying:
It´s my device really dead? :crying:
Rodrizio said:
I tried boot with a Sdcard bootable created with rockchip create upgrade disk tool (my sdcard is a 8gb size. I don´t know if the size make a issue) with the Malaysk dupdate.img file but nothing happend.
I follow the next steps.
I unplug from the back my device and insert the SD card bootable into GPS slot.
I plug again the device from the back and nothig, only the same screen black like off, I try differents combination of keys (press RES+Power ) and nothing....:crying:
It´s my device really dead? :crying:
Click to expand...
Click to collapse
You shouldnt need to press anything, it should boot from the sdcard as soon as you turn it on. I would read @marchnz's unbricking threads if nothing its working.
Just want to know were I can find an "original" Rom for my Klyde PX5 MTCD unit.
I install Hal9k and it work like a charm but what if I have to send it back to Shenzhen?
Maybe I have to do this so before that I want to get it in original state.
Seelenwinter said:
Just want to know were I can find an "original" Rom for my Klyde PX5 MTCD unit.
I install Hal9k and it work like a charm but what if I have to send it back to Shenzhen?
Maybe I have to do this so before that I want to get it in original state.
Click to expand...
Click to collapse
Lol, no one send their unit back to China because it costs too much, its far easier and cheaper to repair it yourself, but there are factory ROMs around if you look, but I wouldnt bother looking unless you need to, cross that bridge (if and) when you come to it as they say.
Now it's a situation I really need that klyde mtcd px5 firmware.
Are there any hints or links?
Thanks ✌?
Yeah loads all over the forums.

Recovery Help Please

Just had an Eonon GA2160 head unit installed in my wife's car - unit was becoming unresponsive, and after contacting Eonon tech support they advised that i flash an updated firmware which they provided- this unit has all touch buttons plus the reset hole FYI - after flashing using the normal, non-recovery System Update in settings, firmware flashed but upon restart the unit is stuck on the lock screen and won't move on to full boot - I've hit reset using the pin hole on the front, and have tried to initiate a re-flash of firmware using the method provided by Eonon tech support (turning key to ACC, reset hole, turn key off, then back on again) - that method doesn't work - is there another way to get into recovery mode with these units? The only physical button is the pin hole reset -
I have an older Eonon unit with physical buttons and it's so easy to get into recovery mode if I run into any problems - I've googled and searched forums but can't really find any definitive method with the touch only units - thanks to anyone who can help -
Hey Bro,
Did you got any succes? I am stuck in this also. The screen is black only the touch buttons lights are ON. If i press the reset button the light is flashong on the button every 10 seconds and thats it...
How do i go to recovery mode?
Thanks!
georged84 said:
Hey Bro,
Did you got any succes? I am stuck in this also. The screen is black only the touch buttons lights are ON. If i press the reset button the light is flashong on the button every 10 seconds and thats it...
How do i go to recovery mode?
Thanks!
Click to expand...
Click to collapse
I was sent instruction by the manufacturer to get into upgrade mode - they sent me a link to the appropriate firmware for my unit, and had me unzip the files on a FAT32 formatted micro sd card - here is a link to a video they sent me to show how to get it going, but my unit just sat on the boot logo screen no matter what I did - manufacturer told me that the unit is bad, so I packed it up this morning and am sending back for replacement - keep in mind this method is get you into upgrade/flash mode - doesn't look like it gets you into recovery mode which was so easy on older models with actual buttons -
https://www.youtube.com/watch?v=mBtzL_iiA8Q&feature=youtu.be
If anyone else has any info about getting these touch control only units into Recovery Mode that would be awesome

How do I enter recovery on an Eonon GA6154F (MTCD KDL)

I have an Eonon GA6154F. From looking in the System Info I believe that it is an MTCD based KDL device.
It has become increasingly slower over time. I would like to try resetting and installing a different ROM on it to see if it helps speed things up at all. But no matter what I try I cannot seem to enter the recovery system.
I have tried holding in the reset button whilst also holding the power button, then releasing the reset button and then releasing the power button 1 - 2 seconds later but it still just boots up as normal.
I have also tried following the instructions in this thread: https://forum.xda-developers.com/an...al/eonon-ga6164f-mtcd-rk3188-mtcdkld-t3594368 but when I try the write the firmware file to an SD Card an error message comes up on screen saying something about failing to write the MBR. The SD Card application also records error 87 in it's log file.
I am currently running a stock ROM from around November 2016. I would like to either reinstall a stock ROM or one of the available customised ROMs, I'm not fussed which. My ultimate goal is to effectively factory reset my Android Head Unit in the hope that it speeds it back up.
Hopefully someone can help me out with this
push and hold the power knob untul you see the units buttons flash 3 times, let go and push the power knob again you will see the recovery screen come up.
jim1985 said:
I have an Eonon GA6154F. From looking in the System Info I believe that it is an MTCD based KDL device.
It has become increasingly slower over time. I would like to try resetting and installing a different ROM on it to see if it helps speed things up at all. But no matter what I try I cannot seem to enter the recovery system.
I have tried holding in the reset button whilst also holding the power button, then releasing the reset button and then releasing the power button 1 - 2 seconds later but it still just boots up as normal.
I have also tried following the instructions in this thread: https://forum.xda-developers.com/an...al/eonon-ga6164f-mtcd-rk3188-mtcdkld-t3594368 but when I try the write the firmware file to an SD Card an error message comes up on screen saying something about failing to write the MBR. The SD Card application also records error 87 in it's log file.
I am currently running a stock ROM from around November 2016. I would like to either reinstall a stock ROM or one of the available customised ROMs, I'm not fussed which. My ultimate goal is to effectively factory reset my Android Head Unit in the hope that it speeds it back up.
Hopefully someone can help me out with this
Click to expand...
Click to collapse

Px5 unknown boot screen? Error flashing

Good evening all
I’ve tried flashing my px5 8.0 to hal9k. I had read that first you must flash to 3.x to then Android 9. I put the boot card img on an 8gb card and put the unit into recovery. The flash worked and brought up the first screen. Then went to update from sd and now I’m left with the second screen. See pic.
Now i am unable to get back into recovery.
Any help would be great. Thanks
So I am unable to post outside links.
The first screen boots up black with navigation system upgrade card.
The second screen that comes up is black with red green and blue squares at the top with a load of Chinese writing it says at the very top in small writing - px5 v1.1
forgot to mention I have the unit that is unable to get into recovery by pressing the power / reset buttons. I believe it had mod installer app that put the unit into recovery.
Did you ever figure this out? Im having the same problem with my px5 head unit (same screen)
Use OTG method per my thread/signature

Categories

Resources