Develop Bugs

Eonon g2110f bootloop after install a new rom

Hi guys,
I have a problem, my eonon is in bootloop after i have install a new rom but I have no idea what the key combination to enter in recovery mode...
Pls help me!!!
Thanks!

thefaber said:
Hi guys,
I have a problem, my eonon is in bootloop after i have install a new rom but I have no idea what the key combination to enter in recovery mode...
Pls help me!!!
Thanks!
Click to expand...
Click to collapse
Press the reset button.
Press both Power and Home button for about 15 seconds.
Release both and press Power again.
The unit will boot into recovery.

Very very thanks!!!

m00n61 said:
Press the reset button.
Press both Power and Home button for about 15 seconds.
Release both and press Power again.
The unit will boot into recovery.
Click to expand...
Click to collapse
Thanks for the advice, and a little more if you have it. Where could I find the original firmware file for the Eonon G2110F unit? Mine seems to have an issue with one part of the OS, namely the reversing camera which doesn't seem to be working, even after all wiring was installed correctly. Cheers in advance...

djshotty said:
Thanks for the advice, and a little more if you have it. Where could I find the original firmware file for the Eonon G2110F unit? Mine seems to have an issue with one part of the OS, namely the reversing camera which doesn't seem to be working, even after all wiring was installed correctly. Cheers in advance...
Click to expand...
Click to collapse
You can request it from EONON customer support. They are pretty responsive. The only problem is you can never know what will they send you
Alternately, you can either install a firmware suitable for your unit from the huifei server (look in Malaysk's signature for the link) or go with one of the custom ROMs - Booroondook's or Malaysk's. Both are waaaaaay better than any factory firmware.

m00n61 said:
You can request it from EONON customer support. They are pretty responsive. The only problem is you can never know what will they send you
Alternately, you can either install a firmware suitable for your unit from the huifei server (look in Malaysk's signature for the link) or go with one of the custom ROMs - Booroondook's or Malaysk's. Both are waaaaaay better than any factory firmware.
Click to expand...
Click to collapse
I pretty much posted that question without going looking for answers first. All good, my unit is now running the rooted Lollipop ROM that Malaysk cooked. Thanks to all who made such an update possible, I now have a car stereo which pretty closely resembles my Galaxy S6 that's running stock rooted Marshmallow...

Do you have a link to the ROM you used?

asianmulder said:
Do you have a link to the ROM you used?
Click to expand...
Click to collapse
Here:
https://forum.xda-developers.com/showthread.php?t=3246370

Can you help me please?
Does anyone know what is the combination of keys to enter in recovery mode (boot menu) on eonon GA7165S? Thank you
It remains stuck on eonon logo picture after the text "optimizing app xx of xx"

It is not the same h/u
It is other model. Mine is eonon ga7165s and has android 6. And i ve tryied the key combination written above and many other but still not entering in recovery mode.
Ps: someone says that my hu is mtcd not mtcb ( i dont know what that means and which are the differences). Soryy if i said smthing stupid.

hi,
I bought an used Eonon G2110F, MTCB, rk3188 800x480, was came with on board a Malaysk 4.4, I tried to install the update to 5.1 but after few days recognize more bugs.
so decided to install an update to 7.1 do all wipes, but the update no works because I used a wrong rom.
now, my Eonon never stars in recovery, tried more combinations but nothing, I’m unable to create an sdbootable, because the software Sd software update 1.4 stopped during the process, I dowloaded others suite and tried on other pc, but always the same result.
anyone have a solution for me?
sorry for my english,
maurizio

mzampa said:
hi,
I bought an used Eonon G2110F, MTCB, rk3188 800x480, was came with on board a Malaysk 4.4, I tried to install the update to 5.1 but after few days recognize more bugs.
so decided to install an update to 7.1 do all wipes, but the update no works because I used a wrong rom.
now, my Eonon never stars in recovery, tried more combinations but nothing, I’m unable to create an sdbootable, because the software Sd software update 1.4 stopped during the process, I dowloaded others suite and tried on other pc, but always the same result.
anyone have a solution for me?
sorry for my english,
maurizio
Click to expand...
Click to collapse
You cant install Android 7.1 roms on MTCB head units, you can use any MTCB Android 4.4 or at maximum 5.1.1 roms

mzampa said:
I decided to install an update to 7.1 do all wipes, but the update no works because I used a wrong rom. Now, my Eonon never stars in recovery, tried more combinations but nothing.
Anyone have a solution for me?
maurizio
Click to expand...
Click to collapse
Well, have you tried installing a Quick Start app. on the device? Because the stock ROM you currently have going is pre-rooted, you can put onto the head unit an app. which gives you choice of restart, either normal restart, restart into Recovery or restart into Download mode. All you need do is give the app. Superuser permissions. Here is one of the best restart apps on Google Play Store...
Code:
[URL="https://play.google.com/store/apps/details?id=com.antaresone.quickreboot&hl=en"]https://play.google.com/store/apps/details?id=com.antaresone.quickreboot&hl=en[/URL]
Oh, and 99.9% of the time an install of a Nougat ROM on your device will fail, because
iRcKenny said:
You can't install Android 7.1 ROMs on MTCB head units, you can use any MTCB Android 4.4 or at maximum 5.1.1 ROMs
Click to expand...
Click to collapse

hi,
thanks for yours replies, now termine to check the system, all it’s ok, but the HU doesn’t turn on.
I think to have bricked the HU, the current, directly and under key are ok, tried various mode to restart,
also connect to pc, but don’ t recognize the HU. are dead!
solution?
regards
maurizio

mzampa said:
hi,
thanks for yours replies, now termine to check the system, all it’s ok, but the HU doesn’t turn on.
I think to have bricked the HU, the current, directly and under key are ok, tried various mode to restart,
also connect to pc, but don’ t recognize the HU. are dead!
solution?
regards
maurizio
Click to expand...
Click to collapse
Maybe this post can help you

pumpkin nd0294b
i brick my pumpkin nd0294b ( px5 with oreo 8.0 mcu like in attached photo)and i can't enter in recovery mode just freeze . any idea? thanks

Please rom greek

treliarhs7 said:
Please rom greek
Click to expand...
Click to collapse
Eonon G2110f

Need Help Modding ROM

Hello,
I am new to modding/creating ROM's but have ok experience with android and linux themselves. I recently bought a Pumpkin android 4.4.4 head unit that has a RK3188-T SOM with 32GB nand and 2GB RAM at 1024x600. I thought it would work with malaysk's rom because it's a RK3188, but it gets stuck in a bootloop with the google stock android boot animation (the silver ANDROID with a shimmer going across). I've been trying to self teach/google how to mod the rom to make it work with my device but haven't been able to yet. I have the update.img's for both malaysk and pumpkin unpacked as well as their recovery and boot img's. I've also been trying to learn what it takes to pre-root the stock rom so I can at least get xposed up and running, but there's not really any good tutorials on that either. If anyone could help me out learning how to pre-root or how to/what to mod to get malaysk's rom working I'd be extremely grateful!!!!
Oh, also, with the unit at the boot animation, is that still the boot.img, or has boot.img passed control off to system.img at that point? Trying to narrow down where the problem is.
Thank you in advanced,
-Kyle

Your head unit unfortunately (or fortunately) is not an MTCB model, so Malaysk's MTCB ROM would never work on it.
Therefore the appropriate forum section for your question is this:
Android Head Units
or this other one should your HU's MCU version start with MTCD:
MTCD Discussion, Questions, Development

themissionimpossible said:
Your head unit unfortunately (or fortunately) is not an MTCB model, so Malaysk's MTCB ROM would never work on it.
Therefore the appropriate forum section for your question is this:
Android Head Units
or this other one should your HU's MCU version start with MTCD:
MTCD Discussion, Questions, Development
Click to expand...
Click to collapse
That might explain why even once I get the malaysk recovery up and reinstall a second time, the unit seems to boot up, but both the recovery and system are almost comletely off the left side of the screen, only about 10% is visible on the left edge of the screen. I don't even know what the options are in that recovery screen, I know there's 7 options and I've found that option one boots into system, option 3 installs the update.img, option 2 does something but not sure what, and options 4-7 bounce right back to that recovery screen. Sadly, even with adb on by default I can't get this thing to connect to my pc. So, since those roms won't work, can you tell me how to pre-root the stock rom please? I've tried all the root apk's I could find, KingRoot would work, but with it I couldn't get SuperSU binaries installed properly so it's not the right kind of root I guess. And I'd love to know how to pre-root a rom anyways! Thx a ton!
-Kyle

kjcsg said:
That might explain why even once I get the malaysk recovery up and reinstall a second time, the unit seems to boot up, but both the recovery and system are almost comletely off the left side of the screen, only about 10% is visible on the left edge of the screen. I don't even know what the options are in that recovery screen, I know there's 7 options and I've found that option one boots into system, option 3 installs the update.img, option 2 does something but not sure what, and options 4-7 bounce right back to that recovery screen. Sadly, even with adb on by default I can't get this thing to connect to my pc. So, since those roms won't work, can you tell me how to pre-root the stock rom please? I've tried all the root apk's I could find, KingRoot would work, but with it I couldn't get SuperSU binaries installed properly so it's not the right kind of root I guess. And I'd love to know how to pre-root a rom anyways! Thx a ton!
-Kyle
Click to expand...
Click to collapse
Not sure if it's the same for your unit but with MTCB head units go to settings/factory settings and when asked for the password type *#hct#root#
If you want to turn adb on go back to settings/factory settings and for the password type adbon

Goose247 said:
Not sure if it's the same for your unit but with MTCB head units go to settings/factory settings and when asked for the password type *#hct#root#
If you want to turn adb on go back to settings/factory settings and for the password type adbon
Click to expand...
Click to collapse
Unfortunately, my factory settings password entry only allows for numbers. I can't get the on screen kb to come up or the usb kb to type letters in the box.

Update: I got malaysk's rom up and running...However the touch screen is messed up (it receives input about an inch above where I tap). Then when I tried to reinstall the rom from settings with wiping it went back to the display off the left side of the screen. How I did it:
1) Install malaysk's rom from stock recovery (with "Check parameter..., E:Check failed at 0x4, Update Parameter..., Check parameter after update..." the first install part, and "E:1 parse errors" and "handle script error! ignore..." the second part)
2) Boot loop - USB kb hit ALT PRTSCR I until I get the recovery sliver on the left hand side of the screeen
3) This time I tried using the second option instead of third installing the pumpkin stock update.img and it boot looped the pumpkin boot animation
4) Reinstalled malaysk's rom using the pumpkin recovery again
5) Malaysk's rom booted up! Touch screen messed up but it booted up!
Now I'm redoing that and going to try to install the kld mcu.img's to get the touch screen working right along with the buttons and volume knob. Still no usb recognition on my pc tho sadly.

I'm trying to install the mcu img from recovery but even with the rom positioned correctly on screen the recovery is still a sliver on the left of my screen. Can someone tell me the options in recovery so I know what I'm selecting please and thank you.
Sent from my VS990 using XDA-Developers mobile app

Nvm, I found a picture online. Next question, does anyone know how to copy the mcu partition or modify mcu data? The pumpkin mcu is in bin format n the converter I have won't convert it to img because it's too big.
Sent from my VS990 using XDA-Developers mobile app

If you get it to work, please let us know here.

Well, from what I can tell, it won't work because the custom roms have different kernels causing the display to be off the screen, at least for the fused roms. I tried a non fused malaysk rom and it wasn't off the screen, but I couldn't get the mcu to work. To get the mcu to work you could try to copy the stock settings mcu update, I tried but it's over my head once I got it decompiled and tried following the code to see what it actually does when you click mcu update in the pumpkin settings. Because of kernels and reverse engineering the pumpkin mcu update are over my head for my current knowledge and understanding, I'm trying to get a refund for this unit and going to buy a joying unit since joying actively works with us, the modding community, giving us stock firmware and root and kernels and help and thus we get a much better unit and rom in the end! Joying understands the meaning of android and how it's supposed to be open source and collaborative for the community to work together to make the best goodies possible. I mean, for crying out loud, Google has gotten many of their features that they've put into their kk, lp, mm releases from us, from modders creating what they want and tuning android to it's best!!! Pumpkin, and as a related note, Verizon sucks!!! Alright, rant complete, any questions, let me know!
-kjcsg

Tcl p66 50" - oreo 8 problem

Hello,
I have a problem after the official update to OREO 8: the instant switching-on of the TV no longer works.
the option is regularly activated in the android menu.
With the previous operating system I never had this problem.
I also reset the TV to factory data with no results.
Can anyone help me?
Many thanks in advance,
Michele

hey,
have the exact same problem over here... tv always boots up completely from scratch

realmastah said:
hey,
have the exact same problem over here... tv always boots up completely from scratch
Click to expand...
Click to collapse
they answered me from TCL ITALIA assistance, telling me that it is a known problem and that it will be solved (we hope) with an update ... update that they don't know when it will be released ...
Today I wrote to TCL EUROPE pointing out that this problem is not acceptable and that they give me solutions.
I will keep you updated on this.

Bafoth said:
Hello,
I have a problem after the official update to OREO 8: the instant switching-on of the TV no longer works.
the option is regularly activated in the android menu.
With the previous operating system I never had this problem.
I also reset the TV to factory data with no results.
Can anyone help me?
Many thanks in advance,
Michele
Click to expand...
Click to collapse
What version is your Oreo?
Try downloading V534.
Go to.
https://support.tclelectronics.com.au/software-updates/
It's official TCL Australia Software Download Page.
V534 is stable and has no issue with Instant Power On feature.

MirrorNeuz said:
What version is your Oreo?
Try downloading V534.
Go to.
(...)
It's official TCL Australia Software Download Page.
V534 is stable and has no issue with Instant Power On feature.
Click to expand...
Click to collapse
Does this firmware update work for European TVs as well? Has anybody tested it?
I have the exact same problem on my TCL 50DP660, bought in Germany.
I don't recommend this TV to anyone because of this particular bug. So annoying. Terrible user experience.

Okay, I tried to install Australian v534 on my TV and it didn't work, failed on validation, probably the signature doesn't match

49 inseries Thomson / TCL Percee TV instant start
I have the exact same issue with a 49 inch 6 series Thomson / TCL Percee TV bought in Spain. I am in contact with the manufactures. So far they have advised me to download and install the latest software version and completely reset the tv. This did nothing and the problem persists so I am awaiting their next response. I will update the thread if I receive a working solution. They also told me that it is not possible to roll back to the previous android version.

Same problem here with an TCL U55X9006 QLED. With the OREO.

Any news..?!

MirrorNeuz said:
What version is your Oreo?
Try downloading V534.
Go to.
https://support.tclelectronics.com.au/software-updates/
It's official TCL Australia Software Download Page.
V534 is stable and has no issue with Instant Power On feature.
Click to expand...
Click to collapse
Webpage does not exist, any idea what's happened to the software downloads?

https://drive.google.com/folderview?id=1vXfF1A3WtxTTU3CDRWraWyA7xd_dTGgr
Wysłane z mojego TA-1033 przy użyciu Tapatalka

49 inseries Thomson / TCL Percee TV instant start
The link has an error in it. Try replacing the first full stop with @ e.g. [email protected]
This is for Aussie customers though. Someone else on this thread tried it and the download mismatched with their tv. I have not had any success with the latest European version that tcl/Thomson recommended I download and install. I have not heard back from them since. At the moment I cannot pursue as I am in the UK and the tv is in Spain. I intend to chase up again in new year when next over there.

Any news please ?

I fixed mine! Tried a bunch of stuff, almost bricked my TV (seriously) but now Instant Power On is working! I'll explain exactly what worked for me and how to do it:
DO IT AT YOUR OWN RISK, I take no responsibility for any damages:
Download the file Update.pkg from https://drive.google.com/drive/folders/16RcAprPvyJuiXiEpEbIgvGlIW493kKtQ (folder v528)
Add it to the root of USB Pen Drive
Turn off your TV and take the energy cable out
Insert the Pen Drive
Connect the energy cable while pressing and holding the Power button (the TV button, not the remote control)
Keep it pressed until the screen flicks
You will see a Update in Progress screen (a small gray square in the center of the screen), do not turn off your TV until it's finished
Wait for it to restart. In my case after the update it also wiped all data, if yours does not, try doing it manually before testing Instant Power On
Remember to disable auto updates
Notes:
My TV is a TCL 50DP660 (Percee TV)
Before starting the process it was updated to the latest version (v543)
I chose v528 randomly, I have no idea if it only works on this version
I believe the Update.pkg contains the full image, while the zip is meant for OTA upgrades, but I'm not sure
Maybe the fix came from doing a full installation and is not related to specific version. If you're feeling adventurous feel free to try another version, I'm fine
The reason why I almost bricked my TV is because I tried other stuff before doing this.Just for documenting, this is the complete step by step I did (not recommended):
I was trying random stuff to make Instant Power On work, first I enabled developer mode, ticked some options including "Stay Awake", "Show Taps" and "Pointer Location". Of of them caused my TV to restart and enter a bootloop. At this point I was only trying to make my TV work again. I couldn't find a way to factory reset, so I tried installing the .zip update again with no success, tried to install v528 zip with also no success. Then I tried to downgrade it to Android 7 installing the Update.pkg from version v373. At this point not only my TV would boot, it would also present a lot of image issues, flickering and trying to install the v543 zip started to fail in the middle of the process. At this point I was convinced it was bricked and I lost the guarantee. Then I tried to install the Update.pkg from version v528. I had to remove the pen drive right after the installation was finished otherwise it would go on a update loop. I really don't recommend trying any of those things, I only did because I was already in a boot loop and still I think I was quite lucky. I wasn't even expecting Instant Power On to work in the end of the process.
Good luck! Please send a feedback if you try these steps!

Well done Lucasl! Thanks for posting this excellent write up. I shall be giving this method a try in March when I have access to the tv again and will feed back.?

Lucasls, where did you manage to download the various versions from? Do you have a link? In case v528 does not work on my tv.
Thanks

A4Android said:
Lucasls, where did you manage to download the various versions from? Do you have a link? In case v528 does not work on my tv.
Thanks
Click to expand...
Click to collapse
The link I posted you can navigate through folders, but this is the link to root of the repository https://drive.google.com/drive/folders/1vXfF1A3WtxTTU3CDRWraWyA7xd_dTGgr

Where do you find the upgrade.pgk files? It Is "original" or find on internet?!
I have fear of brick my TV Also... :crying:

franchini.luca said:
Where do you find the upgrade.pgk files? It Is "original" or find on internet?!
I have fear of brick my TV Also... :crying:
Click to expand...
Click to collapse
I found on internet, but I have no reason to believe they are tweaked. In fact I believe they are all signed (has a cryptographic signature that can only be made by the original vendor), because I think to install custom non signed by TCL firmware you first would need to unlock the bootloader. This is my experience with Android phones, I don't expect Android TVs to be any different.
If you Google for this Google Drive folder's link (https://drive.google.com/drive/folders/1vXfF1A3WtxTTU3CDRWraWyA7xd_dTGgr) you'll see it shows in many different forums with many different languages, but I can't know for sure who uploaded it in the first place... See: http://bit.ly/35KpebC
In my case I was desperate because my TV was already bootlooping when I tried to flash this image, so it's of course a harder decision when you have a fully functional TV.

I Ask you this becouse there Is a Little probability that that firmware are not for 55dp660 TV but for a similar model.
So the TV install the upgrade.pkg but TV gira in bootloop... :crying:

[tech support] Pumpkin PX3 MTCE HU, started bootlooping, need help recovering

Hello all,
I've run into an issue with my new head unit. I was just trying it out before installing it, got it powered up from my bench supply to test, and as soon as I installed a couple of apps (Plex and Google Play Music) it started bootlooping on me.
I figured I would go ahead and install a CFW since I do that for all my android devices anyway, but I've gotten myself into a pickle now. I can prompt the unit to attempt a firmware update, but all of the firmware releases I've found are in nupdate.img format, and the recovery is looking for a "kupdate.zip" format. I did try using the SD_Firmware_Tool to build an sdcard for this, but it seems to just be getting ignored.
The current behavior is that I get the "Pumpkin" bootloader logo, then it reboots. It no longer even shows the "android" loading screen as It did before I tried using the SD_Firmware_Tool.
For reference, I was trying to use the Hal9k rom from here
Getting to the onboard update menu works by holding the power button (pushing down the volume wheel) and hitting the reset button. I haven't been able to get it to boot into any other recovery modes yet, but if anyone happens to know of another button combo that should be working, please let me know.
I've put in an email to pumpkin support but I have a feeling they'll take a while to get back to me with the firmware, so hoping someone else might have something I can use in the meantime.

Well apparently I was mistaken about what CPU is under the hood of this thing (was going by a user review on the amazon page where I purchased it.)
According to the recovery it's loading into, this has an RK3368 rather than the RK3188 I expected

Little Update:
I'm trying out this unbrick for the PX5 to see if I can get it to use a more robust recovery. The current one keeps trying to mount a nonexistant drive location to run the kupdate.zip, and most of the pictures I've found of people's recoveries floating around on here have had the option to choose update files from different locations, so I think the recovery on this needs an update.
It's so far booting to a black (backlight on) screen and not progressing, so I hope the firmware update is going in the background and I just need to wait it out. Anyone know how long that firmware update process should take?

well I think my unit may just be new or different somehow, as none of the unbrick metbods seem to be working at the moment.
I've attached some pics of the unit's internals to see if that can help find a solution

How have you ascertained it to be an MTC(D/E) - it isnt

marchnz said:
How have you ascertained it to be an MTC(D/E) - it isnt
Click to expand...
Click to collapse
I suppose there were some assumptions made based on what's already available on the market.
If it's not an MCT(#) then what is it?

Pyr0ball said:
I suppose there were some assumptions made based on what's already available on the market.
If it's not an MCT(#) then what is it?
Click to expand...
Click to collapse
An XDA search for [kupdate] yeilds the information.

Made some progress on figuring this module out

px6 max6 android 10 Version unmatch

after upgrading MCU V3.71D and PX6 HA3_rk3399_10.0_ota(20210111) from dasaita.com
factory settings. bluetooth/canbus all settings are wrong and version unmatch -1 are in the bottom of me screen.
tried MCU unmacth unlock but it keep crashing when i start it.
could really need some advise here.

little update. all my settings are back. but cant remove "version unmatch -1 "
i tried using mcu Unmatch Unlock form this tread :https://forum.xda-developers.com/t/solution-for-version-unmatch-i-hope-final.3805092/
but it keep crashing on android 10. will downgrading to 9 work ?

problem solved.
i downgraded to 8,1 and installed GS mcu. then i could use McuUnmatchUnlock.
then upgraded to 10 and latest HA mcu.

Did you figure this out? I can't downgrade to 8.1 "Can't install this package over newer...etc" error.
I have a VANKU PX6 android 10 unit that bricked itself after changing some settings in the factory menu. The seller convinced me the board was toast but I knew the MCU probably corrupted. I finally found an MCU that allowed me to even boot the unit and I installed the sellers "update.zip" file however,
The bottom says "version mismatch -01"
Any ideas?

encryptedslayer said:
Did you figure this out? I can't downgrade to 8.1 "Can't install this package over newer...etc" error.
I have a VANKU PX6 android 10 unit that bricked itself after changing some settings in the factory menu. The seller convinced me the board was toast but I knew the MCU probably corrupted. I finally found an MCU that allowed me to even boot the unit and I installed the sellers "update.zip" file however,
The bottom says "version mismatch -01"
Any ideas?
Click to expand...
Click to collapse
Read the post above your question for solution
Even better modify apk to install on A10.
FYI - MCU is not Android and does not affect booting.