Hi guys,
I bought an Erisin android 7.1 car head unit 2 months ago, except the Bluetooth connection issue, it worked good. Today I got the boot loop problem, and searched by google, but still cannot goto recovery mode. My unit only has a rest hole in front and no physical button.
Anyone could help me to fix it?
Thanks so much
Related
A few months back I flashed the MCU on one of my KLD MTCB units, I had done it many times before and never had a problem, but this time, the unit went into recovery, started to flash the MCU, then the screen went blank and everything shut off and since then its been totally dead.
I put the SoM in my other MCTB/C machine and it booted (to recovery) and after rebooting it ran fine, but it will not boot in the machine and the SoM from the working machine wont boot in the non working machine either.
The front of the unit including the screen and SoM (Klyde units have the SoM mounted on the back of the screen) WILL boot if its removed and put on the working machine, so the problem is with the motherboard somewhere.
I think that maybe the mcu.img I was trying to update to (MTCB KLD v2,78) was corrupt.
It was suggested that I try the method to use when the buttonless units wont go into recovery - shorting pin 8 on the MCU etc, that doesnt work.
I m stumped.
I did have to solder a resistor back 6 months before the unit died, but it worked fine for 6 months before it died, I thought maybe the solder had cracked or something and re-soldered it, but it still wont boot.
I d be grateful for any suggestions.
I know who can repair it...
departe said:
I know who can repair it...
Click to expand...
Click to collapse
Really ? Who ? I was literally just thinking about how I can sort it out !!
I just sent mine to this guy...send me a PM message..couse I don't know if I can post it here...
Hi All,
Well I bit the bullet and bought a Seicane Android 6.0 head unit ( model no. DAFT 2732RV) which I custom installed into my Range Rover Sport. The unit 8s actually for a Toyo Rav 4. ..
Initially everything that I had installed worked, however after installing Automate Car Dash and rebooting the HU the touch screen froze and I can't do anything...:crying:
So I removed the HU checked all wires for shots etc and then searched for a hard reset button to no avail....
Can anyone give me some pointers on how to resolve this?
Thanks in advance.
Guy
did you ever figure this out?
yeah, continual pressing of the 'captive' home button allowed me to get into the settings, deselect Automate and then the system sorted itself out eventually as the OEM launcher seems very sensitive...
Hi all
I have recently purchased an Eonon branded PX3 model number GA8162 (Android 7.1 / 2GB ram)
Sometimes when turning the car off the stereo will not wake the next time you start the car. It is completely unresponsive including the reset button. There is nothing you can do to wake the stereo until about 12 hours (or so) passes and then it will boot up fine.
When it happens, all the rest button does is make the backlighted buttons light up, and they turn off as soon as the reset button is released. You can make this happen to the headunit when the ignition is off also.
It doesn't always do this, only occasionally and I don't know what it causing it. I have installed Malyusk's custom rom which I would hope solve it, and even installed a new MCU that the seller provided to me.. Neither have worked.
I do not think it is a problem with my car as my old Kit-Kat based headunit never had any problems.
Has any one had any experience of anything like this? Is it a hardware issue, or does anyone have a workaround? I dont really want to send it back due to the cost and how long it will take to get a replacement!
Many thanks
GA8162
Hello, I'm very new to this and while I don't currently have problems I'd be interested to know which MCU you updated to, the MTCE_WWW search doesn't really bring up any results. I have the same unit as yourself and would love to update it. Cheers
I install on www mcu for eonon Ga8161 7.1 a kld mcu file
They told me that www is 99.9% kld .. For now it works fine for me
Hi guys,
I have a strange behavior and I hope you can help me
I recently dropped my Mi5 into the water. :crying: The display didn't work anymore, I found out, that the contact for the display was damaged on the mainboard and ordered a new one.
After installation, the display works again
The only problem: As soon as I connect the main camera unit, the device doesn't boot any longer, but lands in the boot loop. I also have a 2nd camera unit and here the same happens. That means the camera unit shouldn´t be the problem.
Did you have an idea, what could be the issue here and how I can solve it?
Like said before it is strange because without a connected camera unit everything boots without a problem into the system.
Thanks in advance for your awesome help
Just wanted to let you know, that this issue was a hardware defect of the new mainboard yesterday I got another one delivered and everything works without any problems \o/
Hi all, I hope someone can help.
I recently encountered a Bluetooth issue, where the signal strength was very weak when using multiple pairs of headphones. I downloaded a BT signal strength app and using this, I found the strength hovered around 30-40%. Having had my screen replaced previously by a local repair shop, I suspected there was a loose antenna, so I opened the phone to find damage to the motherboard, whereby a small piece of the board was completely missing.
I then purchased a used motherboard from eBay which I then fitted. However on powering up the phone, all I got was the Huawei logo on black start up screen then it turned off. With charger connected it would continuosly bootloop. I then done factory reset and restarted the phone and after a few failed boot ups,it eventually powered up. It was locked with the screen lock from previous owner, which they were happy enough to supply. With the phone unlocked I then set about setting the phone up using my own Google account and all seemed fine. Every aspect of the software/hardware appeared to working perfectly.
I then updated to emui12 which appeared to download and install, however the phone went back into the previous state,whereby it turns off after the Huawei logo appears.
I have no file available in eRecovery. If I put my old damaged motherboard back in the phone boots up first time. I would at this point have given up and reverted back to my old motherboard, however when taking it out,the upper microphone has broken clean off the board.
Any advice out there?
Thanks in advance
Update, which may help anyone in the same position.
It appears the motherboard is paired to the battery and the boot loop issue was resolved when I used the battery from the donor phone I took the motherboard from. I assume buying a new battery would have been another solution had I no access to the battery which was paired to the motherboard I used.