Hey guys
My car head unit is from royal for hyundai elantra and it's stuck on the starting Android logo and can't get past it so can you please help me fix it? Thank you
No one has any idea on how to fix it?
Yasser_Atyah said:
No one has any idea on how to fix it?
Click to expand...
Click to collapse
It is probably in a boot loop. What did you install or do to get it in that boot loop?
If you didn't do anything, you might try to rest the unit or disconnect if from 12V and wait at least 2 hours.
And edit your first post to change the title. I assume it is "resetting" and not "resting"
surfer63 said:
It is probably in a boot loop. What did you install or do to get it in that boot loop?
If you didn't do anything, you might try to rest the unit or disconnect if from 12V and wait at least 2 hours.
And edit your first post to change the title. I assume it is "resetting" and not "resting"
Click to expand...
Click to collapse
1- no I didn't do anything to it. It was working perfectly and I had to switch the car off and then turned it on the boot loop issue started.
2- how do I disconnect it from 12v? Sorry but I am have zero experience when it comes to cars.
3- and you are right it's resetting but I have no idea how to edit the title of thread.
Yasser_Atyah said:
1- no I didn't do anything to it. It was working perfectly and I had to switch the car off and then turned it on the boot loop issue started.
2- how do I disconnect it from 12v? Sorry but I am have zero experience when it comes to cars.
3- and you are right it's resetting but I have no idea how to edit the title of thread.
Click to expand...
Click to collapse
2- Get it out of the dashboard and disconnect the harness or the power plug or take the fuse out.
3- like I said. Edit the first post. It will also make the title editable.
Do you have a small reset hole in the front of your unit? If so, try to reset it with a "pointy" thing like a needle or something else.
Try what surfer63 says, because he has way more experience than most of the people about Android Head Units on this board. If all else fails try what I did after having a bootlooping HU for nearly 4 months :S
Had the same issue. The HU (with 2 USB ports) was some unknown brand called Funrover loosely based on Joying firmware. What worked for me was
- Download the suitable Joying firmware : joyingauto.com/blog/post/joying-intel-sofia-android-car-stereo-software-update
- Extract it on the PC and then copy the firmware files on to a freshly (FAT32) formatted USB drive
- Plug in the USB drive to your HU USB port (1?)
- Since your HU is already bootlooping, plug in a keyboard and use the following key combination> Alt + Print Scr + tapping i (or e, both worked for me) to get in to recover
- Ideally the recovery option will detect the plugged in USB and start reflashing the firmware so that you will be able to use the HU again.
First of all, thank you so much all for any help!! It's my first time posting in the forum which I think speaks to my desperation state right now:crying:, so anything is greatly appreciated!
I bought an Android 10 unit with the PX6 Rk3399 processor, but it had some bloatware that I wanted to get rid of (mainly a knock-off android auto that started when I plugged my phone in even after disabling the app and it got pretty annoying). I decided to root the unit, but it wouldn't stay rooted after restart. I then decided to let SuperSU update the SU binaries despite knowing that something could go wrong, and of course the unit went straight into bootloop!
I then accessed Recovery mode by long pressing the power button (waiting for the unit to flash 5 times) then releasing and pressing again (don't ask me how I found this out). It had an option to flash updates, so I tried flashing the Kal9k Android 9 ROM, with no luck (kept getting error 1001). Then I found a firmware in update.zip form for a similar radio, with my processor and ram and etc from sygav, so I decided to flash that one using the update option on recovery. No luck though, as it was still stuck on boolook with a ford logo (as if the original system partition wasn't flashed and was still there). I couldn't access adb from recovery to see if I could delete the SU folder (if I plugged a USB cable on recovery, the computer didn't seem to see anything), so I booted into bootloader from recovery. Which by the way, was a black screen but did get picked up through USB by windows.
After tinkering with drivers for hours, I don't know how, but my unit got connected and recognized by fastboot. But in trying to erase the system partition, there was no way for system to be found. Every other partition (i.e. cache) could be erased but not system. I also couldn't flash the firmware I found because it being an update.zip, it didn't have a system.img (but it did have an image for everything else, such as boot, recovery, etc).
So I decided to flash a firmware from a guy on the internet that had a soft brick, and I flashall'd it. Now I'm starting to think this guy's firmware was for another completely different system (oh and by the way, System.img failed to flash as it couldn't find the partition, but it really was the only firmware I could find that had a system.img, so since I was completely desperate I stupidly went for it).
Now I can no longer boot into recovery, and I might be booting straight into bootloader mode, but I am not that sure. After I do the trick with the lights flashing and all, the device gets picked up by my computer, but as an unknown device:
{
"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"
}
I manually update it's drivers with the downloaded bootloader drivers from the android sdk (google USB drivers) and it gets detected as a Kedacom USB device, not an Android Device, so no fastboot:
Then if I disconnect it and connect it again, it shows up as an unrecognizable USB device or something like that.
It seems like the same problem I had when I first connected to bootloader, but I don't even know what I did to fix that . I think I might have rebooted into recovery, and then from there booted into bootloader, and somehow my computer then had Android drivers available for install and I manually installed them and it worked? Maybe? I really have no idea, but I can't try that because I can't get to recovery.
I have an update.zip with what I think is the closest firmware to what my radio had originally, an Android 10 PX6 firmware, from which I was planning to install the boot, bootloader and recovery if I had access to fastboot (which I really don't know how to make windows see that it might be a bootloader device), however, since I don't have a system.img to flash and bootloader doesn't even find the system partition, I don't even know where I would go from there.
What do you guys think I should do? What are my options? Did I just hard brick my unit? I wouldn't think so because windows detects "something" even if it can't assign it the driver. But if it is hard bricked, I am not scared to open it up and to do whatever I have to do, if just am really unsure on what to do and how to do it!
Again, any help is highly appreciated! And thank you so much in advance!:fingers-crossed:
SOLUTION:
Alright, this was a ride! It took me about two weeks to find the solution. No matter what I flashed from the recovery, the unit would still be on bootloop, but the last thing I flashed was an update.zip I found on the internet from some guy, and that made my unit completely hard bricked and irrecoverable (no access to recovery). So here's what I did.
Apparently, reading around Rocketchips (PX3,PX5,PX6) have like a "if everything else fails" kind of mode, for stupid people like me, called MASKROM Mode. It's the last resort mode that lets you flash something on the unit when everything fails. That mode is not flashable (you can't mess it up). It's kind of like if a computer had an integrated last resort in case you mess up and break the BIOS.
To get to it though, it is kind of complicated. You need to get to the PX6/5/3 board, which is basically the heart of your radio. So start unscrewing!
The board will look something like this one:
https://sc01.alicdn.com/kf/HTB1f6tCE.R1BeNjy0Fmq6z0wVXaC.jpg
Where the top part is a heatsink that you might also have to remove. PX5s and PX3s may not look exactly like so, but look for something of more or less the same characteristics and form factor, you'll know when you see it.
Go ahead and remove the board from the unit VERY CAREFULLY (the female pin sockets break VERY VERY EASILY from what I've heard, so be very careful).
Next, we will need to connect the PX6/5/3 to the computer through USB. For that, we will have to make a custom cable. Here's the link to the forum where they explain how to make that cable in detail: https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
Shoutout to @marchnz , he's a genius and without his help I certainly would have wasted my $400 I spent on the headunit.
So long story short, take a USB to something cable (the ones for your phone, for instance), strip it, and solder some resistances to it in the EXACT SAME WAY as in the pictures in the first post of the forum.
Now, connect the cable in the same way as the pictures if you have a PX5 or PX3.
IF YOU HAVE A PX6 find out which pins to connect in PAGE 2 of https://forum.xda-developers.com/an...s-development/px6-maskrom-mode-t3989407/page2 , in the pictures of a post by @oton .
Now download Androidtool here: https://github.com/rockchip-linux/tools/blob/rk3399/windows/AndroidTool_Release_v2.52.zip . This is the software that is going to let us access the mode I was talking about earlier.
Once you have it install, restart and plug in your USB end of the cable. Open the device manager on windows. If you see an Unrecognized device pop up, or a malfunctioning USB, you will need to install the drivers. Here's the link to where you can find an autoinstaller: https://github.com/rockchip-linux/tools .
If, after all, you still are having issues with the drivers, you'll need to install them manually. So right-click on the unrecognized device, update driver, browse my computer, let me pick, Have Disk, and then you find the drivers that we just downloaded (unzip them, of course). Choose the driver, and close and re-open Androidtool.
If you see Maskrom device detected on the bottom, you're all set! If you see recovery device detected, you'll have to put it on Maskrom, for good measure. It might work on recovery, but I'd put it in maskrom mode anyway. To do that, you'll have to disconnect the usb from the computer (while the other end with the cables is still hooked to the board), short two pins on the other side of the board (where the heatsink was) (for a PX6, you can find out which ones here https://forum.xda-developers.com/showpost.php?p=80641439&postcount=435) (for a PX5, I belive it will be on the thumbnails of the first post here: https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892) (if you can't figure out which ones, google search for pins to put your unit in maskrom). While you are shorting those pins (maybe with some metallic tweezers), plug in the usb, stop shorting the pins, and the unit should show up in maskrom.
Now dowload an update.img from the following repository: https://yadi.sk/d/umCvHqCDzHccr/RockChip PX5 Android 9/YB . If it tells you to download something, just click on the file until you get to the .rar screen and click on the download arrow on the top right of the screen.
Important: FOR MY UNIT, I HAD TO DOWNLOAD MANY UPDATE.IMG BEFORE 1 WORKED. ONLY ANDROID 8.1 WORKED FOR ME, SO KEEP TRYING! YOU'RE ALMOST THERE!
ALSO, DO NOT DOWNLOAD ANY OTGs (update.zip), ONLY DOWNLOAD IMAGES (update.img).
Now go to upgrade firmware on Androidtool, click on firmware, choose the update.img you downloaded, and start flashing it!
You'll get a progress readout on the right side, and you'll know when its done. Now it's time to put everything back together and hook up the unit and see if it worked. If it didn't or if it's in bootlooop, download another image from the repository and try again. The only one that worked for me was android 8.1.
Okay, so now everything worked and you got your Head Unit back! But what if you had to downgrade android for it?
Here's how to bring it back to its former glory:
From where I stood (android 8.1), the android 8.1 recovery wouldn't allow for android 9 or android 10 flashing. And I found some info on how to flash PX5s recoveries, but nothing on PX6, so I went to Hal9k's website and purchased his modinstaller 2 and followed instructions. Through there, you'll have the chance to update to android 9 or 10 (up to you), by running his apk that will install a new recovery on your machine, and then flashing any update.zip you want. In my case, I decided to also go for his ROM, because of the features it offered. The whole process was 10 bucks but I think it was completely worth it (honest opinion, not sponsored). You can also opt for installing and Android 10 ROM, as I had at the beginning, but I've heard they're pretty unstable.
So that's all! Not an easy project, but at the end you'll have your unit back and running!
I'm guessing you've seen this rom thread? There's a link to the stock stm firmware in the thread, if that's what you have.
https://forum.xda-developers.com/an...rom-malaysk-rom-px6-mcu-stm32-rk3399-t4111653
When mine was stuck on the black screen, I had to short 2 pins out on the board which entered recovery mode. I then managed to get it working from there. I can post a photo of which pins if it's any use to you?
skipraider said:
I'm guessing you've seen this rom thread? There's a link to the stock stm firmware in the thread, if that's what you have.
https://forum.xda-developers.com/an...rom-malaysk-rom-px6-mcu-stm32-rk3399-t4111653
When mine was stuck on the black screen, I had to short 2 pins out on the board which entered recovery mode. I then managed to get it working from there. I can post a photo of which pins if it's any use to you?
Click to expand...
Click to collapse
Hi! I saw that ROM, but when I went to download it it still gives me an update.zip file with all the recovery.img, boot.img bootloader.img but no system.img. I guess I could boot it to recovery and apply the update there, but I think my recovery is also gone :/
Regarding what you said though, are you talking about the maskrom mode? or something like that? Or do those pins just take you into recovery? I could try it but I don't know if Recovery will even work :/
And if they put the radio in maskrom, where do you go from there?? And sure! A picture would be more than greatly appreciated!!
Thank you so much for all your help!!!
To be honest with I'm not sure if it is the maskrom mode, I'm no expert with these things.
All I was getting out of mine was a black screen, but shorting these pins out and powering it up entered a recovery mode each time. Might be worth a try.
skipraider said:
To be honest with I'm not sure if it is the maskrom mode, I'm no expert with these things.
All I was getting out of mine was a black screen, but shorting these pins out and powering it up entered a recovery mode each time. Might be worth a try.
Click to expand...
Click to collapse
My board looks different from that one and I can't seem to find any pins that look like could be shorted :/
I'm at the point where I can flash update.img into the board with my computer (through connecting pins to some USB cable), but I cannot find any full OTG flash for my PX6!
Any ideas? This might be too much to ask but is there any chance you could provide me with a full otg backup of yours to flash on mine maybe?
alfondehesa said:
My board looks different from that one and I can't seem to find any pins that look like could be shorted :/
I'm at the point where I can flash update.img into the board with my computer (through connecting pins to some USB cable), but I cannot find any full OTG flash for my PX6!
Any ideas? This might be too much to ask but is there any chance you could provide me with a full otg backup of yours to flash on mine maybe?
Click to expand...
Click to collapse
Hi,
I have no idea how to do that, and the unit is back in the car now. I ended up keeping the stock rom to be on the safe side! Sorry.
I'm stuck in bootloop on Android 10 PX6 MTCE, headset has no HW buttons only a reset button, can't seem to access recovery.
What step should I try first? I am a total noob and don't own a soldering iron.
Paperclip and recovery?
Update.zip won't flash before rom boot will it.
If all else fails can someone post me a USB OTG?
I only started messing as Malaysk rom had no software volume change for me. Xposed install then reboot looks like a bootloop. Was my Christmas present as well
Hello My Threecar device crashed.
I could not connect to the port in the picture.
The computer does not see the device at all. Does not detect.
Red square. I shorted the feet and the computer never detected it
How can I do PC device detection
Hi, What kind of connector are you using ? can you send a link for that connector or give the connector name ?
radskin said:
Hi, What kind of connector are you using ? can you send a link for that connector or give the connector name ?
Click to expand...
Click to collapse
Hi.
JST-SH 1.0 mm 4 pin Connector
bicer79 said:
Hi.
JST-SH 1.0 mm 4 pin Connector
Click to expand...
Click to collapse
I have bought the JST-SH 1.0 mm 4 pin connector and the connector is to small.
Sorry mate.
I confused it with another device
jst 1.25 connector 4p female
if you want i can pay you
radskin said:
I have bought the JST-SH 1.0 mm 4 pin connector and the connector is to small.
Click to expand...
Click to collapse
radskin said:
I have bought the JST-SH 1.0 mm 4 pin connector and the connector is to small.
Click to expand...
Click to collapse
bicer79 said:
if you want i can pay you
Click to expand...
Click to collapse
Tanks for the offer, but I work at a company that sells this type of material. I ill look for the right type of connector.
radskin said:
Tanks for the offer, but I work at a company that sells this type of material. I ill look for the right type of connector.
Click to expand...
Click to collapse
This is the correct connector
JST 1.25 mm connector 4 pin female
Hi,
I have same board like skipraider, when I short these two pins there is no results. Should I connect board to PC by USB cable. My radio is freezing on black screen after car logo. It happend after updating software and it was take very long time on erasing part so then I restarted radio and it never woke up If I should connect to PC by USB using 4 pin connector has someone pinout description of this connector. Where is Ground, 5V+ , DP+ and DP-?
welcome
Sorry, I don't know English, but I translate from Google. I have a problem. I updated the screen and an error occurred. And because a black screen appears after the logo appears. I can not enter the recovery recovery. The computer refuses to recognize the screen. There is someone who said it must be a 6pin. How do I get the cable that holds the 6 pin. Or is there a way to revive?
[ROM][PX6][STM32][9.0] Malaysk ROM for PX6 MCU STM32 RK3399 with Android 9
Only for devices processor Rockchip PX6, MCU - STM32. Mod Pie 9.0 Android PX6 STM32 RK3399 Not suitable for those who have a real 10 android installed. Install the Device Info HW application in Google Market and look at the API level. 28 API - 9...
forum.xda-developers.com
Examine this topic. Here is how to recover bricked device.
jst 1.25 connector 4p required
Hi all, a need help. After an unsuccessful update, I received a bootloop. There are no physical buttons on the device. Found instructions for recovery through ANDROID TOOL. I connected it to the computer in maskrom mode, but I can’t find the firmware that needs to be uploaded in order for the device to work. Share a dump that suits me or give instructions on how I can restore the device.
They're all there in the MTCD forums.
Thanks for the answer, but all I found is different ota update.zip. And my device is loaded only in maskrom mode.
That's why I'm looking for a full recovery version.
Hi, you have to use the IMG file that contains the recovery and then update normally via OTA. For example, the IMG is:
CHS2_RK3399_10.0_IMG(20200424)
HCT7_rk3399_10.0_IMG(20200415)
OLS_rk3399_10.0_IMG(20201012)
Яндекс
Найдётся всё
disk.yandex.ru
I recommend reading this thread, you will find answers to your questions here:
[MTCD/E] Android 10 upgrade using official Free tools
To upgrade a MTCD/E PX3, PX5, PX6 from Android 6+ on using official Rockchip free tools - a reminder, bringing together multiple threads. First note - if coming from Android 6 - early versions of Realtek dual BT/WIFI (type 2) are not supported...
forum.xda-developers.com
I downloaded the firmware, I start to flash it and every time it breaks off by 50-60%. I used different firmware from the attached ones and different versions of AndroidTool. And different driver versions. Log attached.
s.danyliak said:
I downloaded the firmware, I start to flash it and every time it breaks off by 50-60%. I used different firmware from the attached ones and different versions of AndroidTool. And different driver versions. Log attached.
Click to expand...
Click to collapse
Erase first
I did, first cleared, reboot and firmware. The result is the same I read a lot of documentation, they wrote that there may not be enough power, but the power supply is 5A.
I noticed that the device turns itself off after a couple of minutes of operation. Possible overheating! I will check it.
s.danyliak said:
I noticed that the device turns itself off after a couple of minutes of operation. Possible overheating! I will check it.
Click to expand...
Click to collapse
I had the same problem I bricked my headunit (rk3399 PX6 Android 10) trying to recover root after updating magisk to 25.1 went into maskrom mode but device lost connection to my PC and flash fails at different percentage.
Cause ended up being the adapter i was using to power the device I used 12v 2A adapter
After switching to 12v 10A adapter it finished flashing. BUT make sure the chip has cooling like a heatsink or it will overheat during flash.
I changed the power supply to 10A. Installed cooling. The result is the same. The device reboots even if nothing is done.
Have you tested another USB cable? @s.danyliak
I have tried two different cables. But I connect via usb which is from the device kit and also the usb a - usb a cable is possible in this problem. There are also only 4 contacts, and for otg you need 5. I did not find information on the board I attached the photo.
Does anyone have any ideas ?
Ask seller for schematic and share here for feedback
So I was able to achieve some result and broke everything even worse. In maskrom mode, I flashed boot. And was able to see the device as fastboot. But my joy did not last long. After rash actions, I flashed the wrong boot and now I can’t enter maskrom as I did before by closing the contacts on the keyboard. Approximately as in the photo below. The question is, how can I force him to enter maskrom mode?
s.danyliak said:
So I was able to achieve some result and broke everything even worse. In maskrom mode, I flashed boot. And was able to see the device as fastboot. But my joy did not last long. After rash actions, I flashed the wrong boot and now I can’t enter maskrom as I did before by closing the contacts on the keyboard. Approximately as in the photo below. The question is, how can I force him to enter maskrom mode?
Click to expand...
Click to collapse
Short the two pads while powering on. Lift short after powering on
I tried, I can no longer enter maskrom with this method