Hi,
I recently updated my rk3188 MTCB-YM from 4.4.4 to dsa’s 5.1.1 ROM. All went well with the update. After a couple of weeks, I found the ROM was starting to run quite slow and was almost unusable - except if you kept the unit on for a long time. It was like it was loading a lot of things for a long time and once that was done, it became responsive immediately instead of being delayed to button presses etc.
So I decided to boot into recovery and do a wipe all/factory reset. My unit does not have physical buttons or a gps sd card slot. None of the usual boot into recovery options work so I use an app to reboot into recovery. I started this app and chose the correct option. At the time I did this, the radio was playing. The screen went black and the stayed like that with the radio still playing. The lights on the unit are still on but nothing works - no response at all. I have turned the car off and left it off overnight. When I turn the car back on, the radio starts playing again immediately. (This would normally take a little time while it boots up, so the unit is obviously stuck). As I cannot do any of the reset/recovery options - is there anything I can do? I haven’t removed the unit to see if it is possible to short the pins as I don’t have access to a bench power supply and have limited skills. But I will try this if there are no other options. I also haven’t removed the battery terminal to cut power yet. That was going to be my next test. But wanted to see if there was any advice before I do this.
EDIT: I took the plunge and disconnected the battery, and the unit started back up again.
Related
Hi folks, I've lurked here for quite a while and gotten some invaluable info; so first off thanks for all of the contributions from the gurus here!
Now, I have a pretty strange issue that I haven't been able to find an answer on anywhere. I'm hoping that someone can help me sort this.
The background story:
My wife has a MyTouch 3G Slide that I bought for her back in July. Last week she managed to drop it in some water. It DID NOT get fully submerged since the water was very shallow. However, it did get a slight amount of intrusion. She pulled the battery in a relatively quick amount of time and we let it sit in a bowl of rice to dry out for a couple days.
The current deal:
When I felt the phone was sufficiently dried after a few days, I fired it up. It took a very long time to get out of the MyTouch splash screen and loaded noticeably slower than normal. Once in, the phone functioned perfectly normal. Absolutely no issues at all with any functionality once you get past the security pattern.
However, whenever you put the phone to sleep, it does some funky stuff. The screen goes black for a second and then comes back on, ready for you to swipe down and then enter the security pattern again. Then it will go black again. Then it comes back on. It just continues to do this, never stopping. Sometimes it will go to the security pattern screen too.
So I figured this may have been some hardware issue since it was acting like someone was just repeatedly pressing the power button. First I wanted to try a simple reboot though. Upon rebooting, the phone would not get past the splash screen. It just froze there.
I pulled the phone apart to see if maybe there was some corrosion on the PCB from the water intrusion. Everything looked fine, but while I was in I did a little wipe-down with some alcohol, then I put it back together. After multiple attempts, I was able to get it to boot again. But the boot process was still VERY slow. Occasionally, it would boot into safe mode as well. But when it booted normally, everything would always function great once logged into the phone. This convinced me that it wasn't a hardware problem since the phone would not cut into sleep mode or anything when logged in. It worked perfectly fine. So I figured that maybe there was some sort of corruption that occurred in the software.
So I tried a hard reset. Didn't fix it.
Then I figured that maybe I needed to do a reflash. So I rooted the phone since the water plunge voided the warranty anyways. Once rooted, I flashed TeamFenix 1.7.1 successfully.
But the phone still only fully boots intermittently, and the boot process is still slow. It also has the same problem in sleep mode which is killing the battery fast since the screen is pretty much constantly on. But once in, the flashed ROM works perfectly just like the stock ROM.
Video of the condition:
Since I'm new, I'm not allowed to put any links in my post. But if you type in the string below after the YouTube url, you'll see a quick video I posted of the condition.
watch?v=dX55URtaRHo
So it seems that there is some crazy issue only upon bootup and when the phone is put to sleep. Can anything be done to fix this? Is there a way to locate and fix corrupted software? Any and all help is appreciated!
Sorry for the self bump. Any devs out there have any suggestions? I gotta get this thing sorted.
If its happening on both stock and teamfenix, I'm pretty sure it's a hardware issue. Flashing a rom completely replaces the software, so it doesn't sound like its that.
Sent from my T-Mobile myTouch 3G Slide using XDA App
It actually seems like a problem in the power button. Did you check the contacts for the power button? Repeatedly pressing the power button will first lock it initially and dim the screen. Press again, then it gives you the chance to unlock. Press again and it goes back to sleep. Wash rinse repeat...
Yes, I understand. But if it were an issue with the power button, when you logged into the phone, it would randomly put itself to sleep. It doesn't do that, it functions perfectly normal with no errors whatsoever when you are logged into the phone. This problem is only exhibited in sleep mode which would rule out a hardware issue with the power button.
Two days ago, my T-Mobile Samsung Galaxy S3 dropped out of my coat pocket as i was running for the bus. I picked it up and saw the screen was cracked along the top left and bottom left hand side. Everything was working for the past two days and i figured i'll just wait till Christmas to get a new phone. This morning i took my phone off the charger and turned it on. The Samsung logo flashed, and then the boot animation for Slimrom (the custom rom i'm currently running on) flashed for about a second but then the screen went black. I did a battery pull but the weird thing is whenever i put my battery back in, even without touching the power button, it boots up by itself but then the screen goes black again. I can access TWRP and download mode but they both go black after a few seconds as well. I was able to successfully turn on my phone and have it fully function for about 15 minutes after putting it back on the charger, but it quickly blacked out again. It also keeps randomly booting up by itself which is weird. Im guessing this is a problem with the screen itself, but could it be a software issue because the device keeps booting up by itself? If it is the screen, will i have to buy a new one or is it not worth it? I've also tried using a different battery and i have the same issue so it can't be that. Any help is appreciated!
Sounds like an issue with the power button, it probably got stuck somehow either when you dropped it, or after you dropped it. Do a simple search for power button and you will find ways to fix it!
Holy crap i didn't even think of that! It makes total sense since every time i even tap my power button, even for just a second, it turns on. I've read around that clearing the cache or a factory reset could work. Is this true?
Unlikely, unless it's a software issue but it's always a possibility. Slam the phone against something to try to get the power button back into place, or open it up and try to see if you can fix it yourself, or replace it
The problem seems to be gone. I haven't had any issues for two days now. All i did was press the power button really hard multiple times. Thanks for you help man!
My C1905 has been acting very strange lately. I have noticed the volume up key failed without warning. This was confirmed with CWM key test. Today, my phone was locked, on a table with nothing that could have pressed any buttons. It randomly rebooted and went into recovery mode. I rebooted it, and then to adjusted volume. The phone crashed and rebooted. When it loaded back up, it crashed when I tried to unlock (insecure lockscreen) first time after boot. I noticed some processor heat, so I removed the back to allow for cooling. The crash lead to yet another reboot. This time, the phone crashed again about 4 seconds into the boot animation. Every one of these crashes involves 2 seconds or so of screen frozen and then automatic processor reset. After this crash, the phone decided to boot to CWM recovery. I went to key test again, and noticed that it said key 766. I can't find any key that causes this code, and Googling this code makes me no wiser. I did a backup of the phone just to be sure against data loss. I left the phone powered off for 5 mins, then turned back on. After about a 3 mins boot, phone seems to be "back to normal."
The phone is "usable" now, but for how long? I'm running latest CM11 build with mounts2SD.
Can anyone shed any light on possible causes? Or even key code 766, or why volume up key failed? I use volume down more than volume up.
I've had the phone for 1yr10mnth now.
The only cause I can think of is the 68C processor temp on 30/06/15, due to warm temperature outside, roughly 34C. Possible PCB warping causing bad processor connection?
theperson333 said:
Hi,
My C1905 has been acting very strange lately. I have noticed the volume up key failed without warning. This was confirmed with CWM key test. Today, my phone was locked, on a table with nothing that could have pressed any buttons. It randomly rebooted and went into recovery mode. I rebooted it, and then to adjusted volume. The phone crashed and rebooted. When it loaded back up, it crashed when I tried to unlock (insecure lockscreen) first time after boot. I noticed some processor heat, so I removed the back to allow for cooling. The crash lead to yet another reboot. This time, the phone crashed again about 4 seconds into the boot animation. Every one of these crashes involves 2 seconds or so of screen frozen and then automatic processor reset. After this crash, the phone decided to boot to CWM recovery. I went to key test again, and noticed that it said key 766. I can't find any key that causes this code, and Googling this code makes me no wiser. I did a backup of the phone just to be sure against data loss. I left the phone powered off for 5 mins, then turned back on. After about a 3 mins boot, phone seems to be "back to normal."
The phone is "usable" now, but for how long? I'm running latest CM11 build with mounts2SD.
Can anyone shed any light on possible causes? Or even key code 766, or why volume up key failed? I use volume down more than volume up.
I've had the phone for 1yr10mnth now.
The only cause I can think of is the 68C processor temp on 30/06/15, due to warm temperature outside, roughly 34C. Possible PCB warping causing bad processor connection?
Click to expand...
Click to collapse
The problem occurred yesterday, so I tried to flash back to stock when the phone "seems to fix itself" again. I got flashtool ready, pulled the battery, inserted again, held the vol_down and connected the USB cable. The phone entered the qualcomm USB HS download mode. I remembered seeing that VOL_UP and VOL_DOWN would cause this mode to be entered aswell as missing kernel. I knew the kernel asn't missing since the phone sometimes boots fine. To further confirm this, I took the battery out, put it back in and connected the usb cable. As expected, the phone entered fastboot, as if the VOL_UP key was being held.
I tried drying the phone out, using silica desiccant, in a moisture shield bag, in case water was shorting the VOL_UP traces. No success. To my knowledge, the phone should be dry anyway. The volume switch feels fine, when pressing it, suggesting the problem is after the switch.
Could the VOL_UP button cause the crashing at the various stages outlined in the OP? I've made them bold in the quote. I also noticed that phone entered CWM whilst in my pocket and enabled, disabled and enabled again rainbow mode. I didn't even know that existed. When the phone boots normally, the VOL_UP key acts like it doesn't exist. When the phone crashes during boot, the main board seems to heat up.
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.
Device is a PX5 fitted for an MB SLK (with extra hardware Buttons, CAN-BUS, etc), Android 9.
I think someone posted something similar before, I'm also in contact with the producer (Witson):
First the tl;dr - Touchscreen didnt work temporarily, then permanently, now not in some areas.
Now the details:
~2 Weeks ago: Touchscreen suddenly didn't respond, I rebooted the device, worked fine again
~1 Week ago: Touchscreen was acting "on its own" sometimes making presses I didnt make, so songs switched etc. maybe was also only dirt, but didn't seem like it, only reboot helped
~2 days ago: Drive to supermarket, everything works fine, come back, screen doesn't react anymore. AT ALL. Tried to reboot, still doesn't work. Tried to boot into recovery, even there the screen doesn't work(tapping gestures, long press).
So I wrote Witson and simultaneously googled for issues like that with Android Head Units, read sth about calibrating the screen or holding reset+power button... last thing didnt work.
Smarta** that I am, I connected a mouse to the device, system was working fine with that, so I could still somehow use everything, so definatley sth with the touchpanel
Then came the answer from Witson, they sent a video on how the recalibrate, so I did:
Go into Factory Settings > Enter 126 > Touch Panel Calibration (or sth like that) .... 2 crosses in the corners of the screen, no reaction .. i think i also tried to use "Reset Touch" but also didn't work.. BUT I didn't reboot afterwards.
Now the fun begins: After work, go to the car, Head Unit starts, I dont even try touching until after 3 minutes and as I try suddenly the screen reacts! But after some time of driving, it stopped working again.
Back home, reboot, touch works for ~1min then stops again.
Boot into recovery, Wipe/Factory reset, Screen reacts PARTLY after that, like around the middle it doesn't seem to react... Factory Settings for Calibration again, want to enter the 126, but that row on the keyboard doesn't react. All the others do (even though sometimes laggy), Mouse again, enter code, go to calibration, touch works this time! Calibrate, apply, reboot. But still sometimes the Settings itself don't react all the time, when I wnat to enter WiFi Password, again, upper row of the keyboard doesn't react, rest of the keyboard does.
WHAT is going on!? Faulty Hardware? Software? "Driver"?
I also have a video of me trying to enter stuff on the keyboard, if someone needs it.
Suggest to send it back or demand warranty replacement for these poor lack of Quality Control knock off head units.
All you will get posting here are guesses.