I have a Dasaita MAX6 , I flashed Malaysk's ROM and everything was going well. I was setting up GPS volume - the onscreen keyboard obscures the text field, so I plugged in a USB keyboard. As I did that the unit rebooted. I think it rebooted again, but then would only show a black screen.
I reflashed Malaysk, then the stock ROM, DMCU, and just to be sure contacted Dasaita and downloaded the latest versions again.
So I have determined that the SOM is indeed booting up, but the brightness is zero. If I hold a torch to the screen I can just make out a dialogue asking to enable location, but touch isn't working.
I am considering returning the SOM only to Dasaita for exchange. Can someone give me some advice on the best course of action. Thanks.
Is it black screen in recovery too?
marchnz said:
Is it black screen in recovery too?
Click to expand...
Click to collapse
I should have said, recovery is fine - full brightness and touch OK, and flashing MCU and SOM appear to be successful.
mazellan said:
I have a Dasaita MAX6 , I flashed Malaysk's ROM and everything was going well. I was setting up GPS volume - the onscreen keyboard obscures the text field, so I plugged in a USB keyboard. As I did that the unit rebooted. I think it rebooted again, but then would only show a black screen.
I reflashed Malaysk, then the stock ROM, DMCU, and just to be sure contacted Dasaita and downloaded the latest versions again.
So I have determined that the SOM is indeed booting up, but the brightness is zero. If I hold a torch to the screen I can just make out a dialogue asking to enable location, but touch isn't working.
I am considering returning the SOM only to Dasaita for exchange. Can someone give me some advice on the best course of action. Thanks.
Click to expand...
Click to collapse
Plug a mouse if you can accept the dialogue
If not worked...
Reflash again from recovery but first dona full wipe of system
Enviado desde mi SM-G975F mediante Tapatalk
Related
Hello Guys,
I really need some insight on this problem:
I have a KLD (http://www.eonon.com/Car-GPS/Specific-Car-GPS/Mazda/GA5151.html) unit for some time now, but since September it wasn't in my car because I was preparing an audio upgrade. As one of the last steps I've checked out the HU and I wanted to upgrade to the latest MCU&FW, but the unit wouldn't turn on. Since it's on my "workbench" I've checked the cables, fuse, the external PSU, everything i could, but it did not help. The unit worked flawlessly in the car and on the workbench 2 months ago. Nothing changed. Now it won't turn on, not even the fan at the back of the unit. The screen and the button backlights are also off.
The one confusing part is, when I push the power button with reset for a few seconds, the unit comes to life, and goes into recovery! I can flash a ROM, clear the cache, etc., but when I reboot the unit from the menu, it turns off, then the button backlights flash once, but nothing else happens. The unit stays turned off.
So far I've checked:
- Fuse
- External PSU
- Power button
- Replaced the SOM (The unit is RK3066 originally, I'm using it with RK3188)
- Tried different ROMs
- Disconnected the DVD drive
Nothing helped. I can get into recovery, but I can't boot the unit, no matter what SOM (or what ROM) I use. I would really appreciate some help, because I ran out of ideas.
Thanks in advence!
LFMF
Ok, the big conclusion is to use the multimeter first. Magically, ACC was not even close to 12v. Switched to another PSU, everything works.
HeuFei based Headunit, no touch, no buttons.
Everything has been fine, no updates, no changes.
Unit was from Pumpkin, it's a RK3066 based unit with KDL
I get in tonight to drive home form work, and after bootup I noticed none of my SWC worked, buttons on the unit itself don't seem to work, and the touch screen is unresponsive.
The unit boots, I see things happening - just no controls.
Reset button works, Power button works - I can get into recovery mode, but cannot navigate with volume have to use power, tried doing a restore, same thing.
any ideas?
Have you tried disconnecting the battery to remove it from a power source?
grinthock said:
Everything has been fine, no updates, no changes.
Unit was from Pumpkin, it's a RK3066 based unit with KDL
I get in tonight to drive home form work, and after bootup I noticed none of my SWC worked, buttons on the unit itself don't seem to work, and the touch screen is unresponsive.
The unit boots, I see things happening - just no controls.
Reset button works, Power button works - I can get into recovery mode, but cannot navigate with volume have to use power, tried doing a restore, same thing.
any ideas?
Click to expand...
Click to collapse
Hi, i'm experiencing the same problem. I updated my HuiFei unit yesterday to MCU: MCU_KGL_2.78 and ROM: update_4_4_4_800X480_RK3066_29_MAL_27_10_2015. Everything was working fine and did all my personalization. I was able to turn the unit on and off and use all the buttons. Later the day when i used it again all the buttons as well as the screen was unresponsive. The only the power button can turn the screen on and off. I also tried to boot into recovery, but no luck...
I'll try disconnecting the battery and see if it works.
---------- Post added at 12:23 PM ---------- Previous post was at 12:01 PM ----------
BiliTheAxe said:
Have you tried disconnecting the battery to remove it from a power source?
Click to expand...
Click to collapse
I just tried disconnecting the battery, left it for a minute or so and connected it again then turned on the unit. No luck, the screen and buttons are still not responsive...
Hein3G said:
Hi, i'm experiencing the same problem. I updated my HuiFei unit yesterday to MCU: MCU_KGL_2.78 and ROM: update_4_4_4_800X480_RK3066_29_MAL_27_10_2015. Everything was working fine and did all my personalization. I was able to turn the unit on and off and use all the buttons. Later the day when i used it again all the buttons as well as the screen was unresponsive. The only the power button can turn the screen on and off. I also tried to boot into recovery, but no luck...
I'll try disconnecting the battery and see if it works.
---------- Post added at 12:23 PM ---------- Previous post was at 12:01 PM ----------
I just tried disconnecting the battery, left it for a minute or so and connected it again then turned on the unit. No luck, the screen and buttons are still not responsive...
Click to expand...
Click to collapse
You may have updated to the wrong MCU file. They are not interchangeable between manufacturers.
BiliTheAxe said:
You may have updated to the wrong MCU file. They are not interchangeable between manufacturers.
Click to expand...
Click to collapse
Hi have a KGL HU and after the update everything worked fine even restarted the HU a few times without any issues... When i started the unit up again after a few hours, that's when i experienced the no response issue.
I have tried the steps to get into recovery -> Press reset + Power for a few seconds and then release reset... but it just starts up normally
Hein3G said:
Hi have a KGL HU and after the update everything worked fine even restarted the HU a few times without any issues... When i started the unit up again after a few hours, that's when i experienced the no response issue.
I have tried the steps to get into recovery -> Press reset + Power for a few seconds and then release reset... but it just starts up normally
Click to expand...
Click to collapse
I managed to boot into recovery after a few tries and reinstalled the MCU and ROM and the screen and buttons work again. The GPS button is mapped for the "back" function for some reason, but that might be some app changing the assigned function.
So I pulled the power on mine -- no dice.
I want to reflash the MCU, but I can't get into the unit to find out which MCU I have -- catch 22!
ok well, a little progress. I remembered reading elsewhere that someone plugged in a keyboard, so I plugged in a MPC keyboard/trackball combo into the unit -- and now i have a mouse, that's useful.. So I was able to check, it says I have KLD -- but is that what's flashed, or is that what I have....
I tried to assign SWC keys, just to see if it was recognizing them - no dice....
I am also installing fresh firmware and fresh MCU, see what happens.
Well, success.... reloaded KLD mcu.img with latest, and latest firmware... All working..
Keep things simple with your software.. Keep it classy.
Ive tried everything I can think of and it wont work. I have two head units. My older GA5153 was almost too easy. I inserted the SD card into the GPS slot and the unit recognized it and suggested an update. A few minutes late...it was done! My new unit is a Witson that I found on AliExpress. I love the 9 inch screen and the fact that its a quad core, but the UI just isn't doing it. It remembers most things but there's little settings that revert every time you restart the unit. I want the new ROM on there but its just not happening.
The issues Im running in to currently:
Theres no Physical buttons on the unit. I should be able to use the reset as a select button but I haven't got that far yet. The problem there is every time I boot into recovery mode its just the android on his back and it says "No Command".
The unit doesn't do any type of auto update like the GA5153 did.
It almost seems as if the UI was designed to try to prevent people from upgrading. Any and all help is appreciated as Ive been at this for hours and hours with no success. Thanks guys!
Can't you use a USB keyboard?
themissionimpossible said:
Can't you use a USB keyboard?
Click to expand...
Click to collapse
As bad as it sounds, I didn't even think of that. One of the wiring harnesses in the back has a usb port on it. Ill have to see if itll read it when I plug it in.
The unit recognized the keyboard and it was functional while the unit was on, but it wouldn't work in the recovery menu. I'm not sure what to do anymore. All the ROM installer apps Ive tried have failed to recognize the ROM on the SD card. Its very frustrating but I will make this work.
What Witson model do you own?
Are you sure it's a MTCB HU?
Have you tried to contact the manufacturer?
I dont think your Witson unit is an MTCB HU.
I just bought a PX5 unit, which seemed to be working perfectly until I finished installing it into my car and now it has become unresponsive with a black screen and a yellow rhombus with an exclamation point in the middle (unable to upload image as new user).
If I turn off the ignition, it will turn the stereo off and the android screen briefly shows before going into sleep. None of the buttons are allowing me to get past the screen and in to android. The reset button seems to do nothing, android is definitely running in the background, just unsure as to why this screen will not close. Any ideas?
Hi, I think I saw a yellow rhombus with an exclamation point when I was installing my radio and rear view camera was not connected to the radio. I think that it is a warning about missing video signal when radio is displaying live feed from a rear view camera.
So, one explanation for your issue could be that the radio thinks you are reversing, and the rear view camera is not connected to the radio. If I understand it right, radio can switch to rear view camera display mode based on two conditions 1) canbus information 2) +12v trigger signal.
For the condition 2), you could check that nothing is unintentional connected to reverse detect wire. If that does not help, then you could perhaps try to disable reverse view feature in the configuration menu before installing the radio to the car and/or find a working canbus configuration settings.
Please notice that I'm a beginner with Android head units and your problem might well be something totally different!!
Thanks for your reply. Some of your post seems to relate to my issue definitely, I think it is linked to the rear view camera which is currently disconnected. However I am unable to get into any configuration options. None of the buttons/resets I try get me past the exclamation screen, I can only see android once I turn off my ignition when it tells me it is closing down. None of the various reset button combinations seem to do anything with my head unit either, can't seem to reset it properly. Its strange, I will reattach the camera tomorrow and see if that brings any joy. I don't know anything about this stuff myself but I am wondering if I did something to the head unit to brick the non-android side somehow.
Edit: Unfortunately reattaching the camera did not change anything.
Update. I have managed to find a way in to the Android side if I connect my phone via bluetooth to the stereo, it then lets me use the split screen function via the top bar menu to put the warning screen other screen to the side, however whenever I touch the screen or attempt to use the android interface, my stereo goes back to the warning screen, none of my inputs via the stereo buttons or the touch screen seem to be registering with the Android side? Very confused. I have also tried as many button combination resets I can find and I have not been able to successfully get into the recovery menu, or any change except rebooting.
Was your unit professionally installed?
Also, what did the re-seller suggest when you contacted them for support?
No the unit was not professionally installed. I am not sure how I've become stuck with the problem. I made some minor changes in factory settings but nothing I thought would of caused this. The seller is yet to respond and its been a couple of days, but I have requested the hardware reset methods for this unit or any other solutions.
deano35 said:
No the unit was not professionally installed. I am not sure how I've become stuck with the problem. I made some minor changes in factory settings but nothing I thought would of caused this. The seller is yet to respond and its been a couple of days, but I have requested the hardware reset methods for this unit or any other solutions.
Click to expand...
Click to collapse
Check the reverse wire on the back of the unit...if necessary disconnect it to ensure no reverse signal is received.
If your unit can boot into android normally then you will have to figure out why the reverse wire is receiving signal .
Check your connectors to avoid any of them to be loose.
Enviado desde mi SM-G950F mediante Tapatalk
Everything has been disconnected from the unit except the power cable to car and and canbus, from what I can tell nothing is loose. Unit will not boot without the canbus box whatsoever, not sure if that is meant to happen.
deano35 said:
Everything has been disconnected from the unit except the power cable to car and and canbus, from what I can tell nothing is loose. Unit will not boot without the canbus box whatsoever, not sure if that is meant to happen.
Click to expand...
Click to collapse
Yes, canbus decoder need to be connected for power up the HU. If you dont need the decoder box you need rewire the harness.
I think I am going to have to request a refund and return it. Still no reply from the reseller and I am not sure what else I can try, everything that is not needed to power it has now been removed. I can't send links or else I would update the thread with a video of the touch/physical buttons being completely unresponsive even when I manage to get to Android. The unit has definitely developed a fault and I am unable to reset it. Admittedly it could be my fault somehow as it was working for the first few boots, but unless they give me something to try I am just going to have to send it back.
Quick bump. Has anyone got any further ideas? I bought off Aliexpress so contact with the seller is slow and painful, they do not seem to understand the issue and just keep telling me to disconnect all wires and reconnect. Which has been done many times. If anyone wants to post a link to the video for me I would be happy to send them it privately.
deano35 said:
Quick bump. Has anyone got any further ideas? I bought off Aliexpress so contact with the seller is slow and painful, they do not seem to understand the issue and just keep telling me to disconnect all wires and reconnect. Which has been done many times. If anyone wants to post a link to the video for me I would be happy to send them it privately.
Click to expand...
Click to collapse
I would start a dispute with them. I had a device that they sent with similar problems and plenty of issues, which they would not help with or would not understand. Best option is to dispute to get a new device or a full refund. Could you send the video?
xLeviNx said:
I would start a dispute with them. I had a device that they sent with similar problems and plenty of issues, which they would not help with or would not understand. Best option is to dispute to get a new device or a full refund. Could you send the video?
Click to expand...
Click to collapse
Yeh I have a dispute open currently, just was hoping it would inspire the seller to actually offer up a working way of resetting the device. Had to add link below seperately as needed to be ten or most posts.
https://www.youtube.com/watch?v=ujHacKESAT8&feature=youtu.be
The stereo defaults as the warning image black screen and I can only get android up using the multiwindow button with a long press. Then the android side will not register any input and will keep trying to put the black screen to the front.
Update: I have been told by Aliexpress I can have a partial refund and keep the unit, or a full refund if I return to China. Anyone have any ideas how I would go about resetting the unit if I took the partial refund? To be honest I think my only option is to return it and get the full amount back but any ideas would be welcome! Shipping to China and awaiting a refund is going to take weeks, would rather just get it working if possible.
deano35: any progres? I have the same problem as you. This is my post from PX5 MTCD/E Head Unit Discussion Thread
" Hi , I have https://s.click.aliexpress.com/e/DtwdJIt its px5, Mtce_gs_v2.90c. Now I have a little problem with rear camera. I bought reverse camera and tried to connect it into front camera input(I was curious how it would look like) and since then its stuck on camera view. Even after disconnecting camera. Only solution was disable "prohibit reverse" in factory settings menu, but with "prohibit reverse" disabled is obviously not showing reverse camera when I gear the reverse down. Everything is shown in this video. https://photos.app.goo.gl/XbYUHApzT8qTezkq6 Thanks for any advice. "
Take a look on the video, its similar as yours.
Hey y’all
So my phone fell two weeks ago from about 3 feet after a bad hand off as I was showing a pic to someone.
It already had fallen and only suffered a crack along the outer screen from the first fall, but this second drop cracked the inner screen and rendered the lcd useless.
I was still able to turn it off and on, as well as increase/decrease the volume, but screen was showing blue streaks until I just turned it off.
I reset the phone to no avail and eventually got a new replacement screen and frame from witrigs and was able to get the phone into recovery. I wiped the cache and was able to finally get past the boot screen (which displayed fine) but then immediately goes black as it loads up the main OS.
The screen can sense my finger and the touchscreen vibrates when I touch it as if the unlock number pattern screen would appear on the screen but, the screen remains blacked out.
I can turn the volume up and down, power button works fine. I can access twrp and it shows the full screen on the display, but once the OS tries to load the screen blacks out while otherwise functioning as it should.
I checked all of the connections and they’re all good, no loose ends or incorrectly inserted or disjointed pieces, I just can’t get a visual right when the os loads up.
Any ideas if this is hardware/software based? Doesn’t make sense that the screen shows up fine during the initial boot then goes black during the os boot and everything but the screen functions as normal. Thanks
DD
DD83 said:
Hey y’all
So my phone fell two weeks ago
Any ideas folks? Thanks
DD
Click to expand...
Click to collapse
Which rom/kernel you on? You can try another kernel and check
I think I was in resurrection remix 5.8.2. I mostly care about my files but if I can still use the phone that would be ideal.
Just tried flashing the rom I had on before (rr remix n 5.3.5 20180612 release), then dalvik and cache wipe, with the same result. Thanks to anyone that replies and has some insight! Been going on two weeks since my phone was initially dropped to replacing the screen to this! Grrr
DD83 said:
Just tried flashing the rom I had on before (rr remix n 5.3.5 20180612 release), then dalvik and cache wipe, with the same result. Thanks to anyone that replies and has some insight! Been going on two weeks since my phone was initially dropped to replacing the screen to this! Grrr
Click to expand...
Click to collapse
Sometimes there is a drivers issue on replacement of screen. Try OOS and see if it works. Atleast for some people, OOS solved the issue.
tnsmani said:
Sometimes there is a drivers issue on replacement of screen. Try OOS and see if it works. Atleast for some people, OOS solved the issue.
Click to expand...
Click to collapse
Thanks. Should I try a newer more recent oos or one closer to the oos I had installed? Does it matter?
I would ideally like to get back to where my phone was, but if I can’t I’m content with starting over if it means I’ll have a functioning phone.
DD83 said:
Thanks. Should I try a newer more recent oos or one closer to the oos I had installed? Does it matter?
I would ideally like to get back to where my phone was, but if I can’t I’m content with starting over if it means I’ll have a functioning phone.
Click to expand...
Click to collapse
Recent OOS can be tried. There is no link between what OS you had and the OOS you are flashing.
Hope you succeed!
had similiar problems,replaced my screen was using custom roms too i found out cheap screens dont work properly and the only way around this for me was to install caesuim latest kernel cause my screen use to stay black after the screen went to sleep until i installed that kernel works great now
I have a like problem, my oneplus 3 locks the bottom of the screen, already replaced kernel and nothing works, someone has suggested what it can be, the screen has been replaced.
ireaper4592 said:
had similiar problems,replaced my screen was using custom roms too i found out cheap screens dont work properly and the only way around this for me was to install caesuim latest kernel cause my screen use to stay black after the screen went to sleep until i installed that kernel works great now
Click to expand...
Click to collapse
can I install this kernel on OOS latest build?