Hi everyone,
I'm coming to you because you're the last chance for my HU to survive... and also because I'm a dumb with Android or softwares...
I got a few months ago a chinese HU with no name and Android 7.1 to install in my 2007 grand vitara.
Everything was ok for a while, and then one morning I start the unit and it stuck on the screen below.
I can let it like this for hours, nothing move. Since, I'm just able to turn off/on the screen.
I tried all reset/buttons combination I have been able to find on the net to get in Recovery Mode, nothing. I unplugged it from power, nothing. I put a new rom on the sd card (thinking maybe it would run from the SD) nothing.
So any idea is welcome.
Otherwise, I think this will go straight to trash...
Many thanks for your help
Related
Beers for anyone who can help!
I have Pumpkin ND0294B-A08, was trying for hours to get root for it, at one point an APK loader was supposed to root and reboot to recovery mode, it looked like root was successful but never booted to recovery, now I am stuck at either straight PUMPKIN load screen, or if I use RST button along with POWER button I can get it to "Starting update..." screen with android logo.
I have been working for hours and keep hitting dead ends and broken links and files that are missing from download sites and am now just stuck.
Unit is Android 8 PX5 MCU CSN2. I thought it was the same as my last head unit but I overlooked the MCU CSN2 and I think that's why it's dead.
Beers for anyone who can help me bring this back to life, extra for those who can help me bring it back to life rooted.
Thank you.
From what i remember from other posts is you can flash the standard (CSN2) firmware without booting into android. If you can get it into "starting upgrade" mode, try having an sd card in there with the stock firmware. Easily downloadable from the csn2 thread. I hope you have success!
I actually tried that once or twice just to get it back from being bricked, and it wasn't working. EDIT: found many extra links for firmware. I will try again.
EDIT 2: tried UPDATE2.BIN and KUPDATE.ZIP in a fat32 SD card that worked earlier on this same unit, tried several versions of the factory firmware from the thread and it isn't working for me. If I just power the unit with the SD card inserted, it sits at PUMPKIN large letter screen. Not in a loop, just sits at that screen. THEN, when I boot while holding power button it shows a display with a green Android character with the words "Starting update..." but I let it sit that way for an hour and it does nothing else.
Anyone else have ideas that can help possibly? My unit is bricked unless I get this fixed.
Thank you,
Hey guys am in desperate need of some help have a eonon GA-9263B android 8.0 unit. Wrong rom was attempted to be loaded and now i get no real signs of life. Have tried making countless sd scards etc etc with no luck. If i hold down the power button for 15 seconds its does flash 3 times but thats it. Any help at this stage is appreciated
Hi everyone! It's a great pleasure to be the part of that big community. Please forgive me for any language mistakes since my English is not so good.
I'm the owner car radio, head unit is produced <probably> by Joying, but I can't tell the exact model, I bought it one year ago as used. Everything was fine, but few days ago it just stop working. It was in something like bootloop. Showing all the time "Android" sign. Now I found some time to see what happened. I've downloaded few firmwares and tried install them in recovery mode. After first installation my recovery menu looked something different, and lollipop logo has appeard. I thougth that's all. But it was only booting to the recovery mode. So I've tried another update.zip file. At last installation I probably screw something up. The only thing that head unit is doing now is blinking "Robot Android", after five seconds it start showing text "Have not get into systemUI many times!" It blinks for few seconds and thet everything is turning off. Now I even couldn't get into recovery mode, beacuse I probably deleted it with last version of update.zip.
I would really appreciate Your help.
Best regards,
Bartek
Hey guys,
I bought a Navigation System M779 (androidautoplayer.com) for Suzuki Grand Vitara from AliExpress one month ago.
At first, everything was fine and I was very happy about it. Nothing to conplain about.
Then I went on Holidays for about 14 days, in which the car wasn't used in any way.
Yesterday I started the car for the first time after Holiday, the battery still was fine but the radio did not boot. The screen stayed black and the Buttons did not light up.
After checking the Plugs on the back, the screen showed a Bootlogo, but got stuck.
I did not modify anything and everything was fine until Holiday.
Can you please help me?
Pressing reset did not change anything. Sometimes, selecting reverse does activate the rear cam. That's it.
I don't know how to enter Recovery or how to install the Firmware.
It is an Android 9 PX5 System. This is everything I know.
Kind regards
Robin
May be able to reflash firmware using this method - https://forum.xda-developers.com/showpost.php?p=79144579&postcount=2 assuming that the manufacturer posts firmwares on their site, or can provide it to you via download, email, etc.
Thank you for your reply.
I tried some Firmware-files, just to see If the head unit enters Recovery. This failed.
The manufacturer also replied to a Mail, telling me that they will hand me out a possible solution next week.
I will wait eagerly.
Hallo again,
unfortunately the manufacturer did not provide a solution to recovery my Head Unit.
I managed to get into the Recovery Menu and tried to wipe data, but this had no effect at all. Still stucking in bootloop.
The information given in Rcovery Mode are:
rockchip/rk3368/rk3368
9/PQ2A.190305.002/hct204281503
userdebug/test-keys
Recovery V9.0.5.
Supported API: 3
Can anyone please help me restore the Head Unit?
Kind regards
Fisatec
Fisatec said:
Can anyone please help me restore the Head Unit?
Fisatec
Click to expand...
Click to collapse
Did you try to disconnect the main connector from the unit and leave it that way for a few minutes ?
And then reconnect it again.
Thanks for your reply... But I think I did very stupid today and bricked the device.
Reagrding to this topic "forum.xda-developers.com/android-auto/android-head-units/head-units-rockchip-px5-mcu-csn2-t3912413" I flashed my device with "Fake Android 10 - July 6th 202007061156".
The flash ran smooth without any errors. But the screen seems dead now.
The buttonlights still turn on and do blink if I press the powerbutton for about 10s, but there is no bootlogo or anything at all.
I cannot enter recovery anymore.
**** happens?!?
Kind regards
Fisatec
Hope someone can help. I have an Android 8.1 head unit (Chinese) which has been working fine. I removed it from my car and powered it up in the house with a PC PSU, this enabled me to sit for a few hours and set all my apps and home screen up just as I want it. Once all was done, it was running great. I installed back in the car and on powering up, everything was good. A couple of days later, I got in the car and the android displayed “Erasing" and took about 10 minutes to boot. On boot it has gone back to factory defaults and deleted everything. Even worse, the original launcher screen will not come on and it just says “Starting android" but does not progress any further and I cannot get into any settings.
Does anyone know -
1) How to access recovery mode, either by the reset button combination or taking the motherboard out and shorting?
2) or How to Install the original or another Android that will work with my unit?
Or any other ideas? I'm fairly confident when it comes to fixing stuff, just need a walkthrough to get me up and running again.
I had the same issue after installing a new firmware in my Junsun V1 Pro with Mtk8257 CPU. Unfortunately you're just writing that you have a Chinese head unit but all Android head units are from China...
This happened only once and after configuring everything again I have no further problems. The "Starting Android" screen appeared several minutes. So still stay patient and wait.
I thought the erasing happened because I remounted the vendor partition for write access in a wrong way. Maybe you installed a software component or performed some special actions which may be the reason for the erasing?