Hi everyone, first I sincerely apologise if I'm posting this in the wrong forum (and if so please direct me to the proper place). If it's okay, here goes:
I would greatly appreciate your help. I have this Chinese made car Headunit in my car (running android jellybean 4.2.2). I've had it for about a year and a half or so. A couple of months ago, the screen began to be unresponsive - after boot up. It is quite frustrating, as the unit itself is actually working.. but the screen just does not respond. This happens randomly! Sometimes you have to restart it several times before it works normally. And it does work normally sometimes, though there is no apparent order. It seems to just be quite random. I tried using one of the screen calibration apps from the appstore. It seemed to make a very minor difference (or perhaps not!). The problem is still very much there.
Sometimes, while it's unresponsive, if you touch an app icon and leave the unit alone, after some time the app would eventually open - though the time it takes to do that greatly varies. At this point, the screen may then work - sometimes normally, but in many cases, abnormally or unpredictably. In some cases it will not work at all.
Please does anyone know what is responsible for this and if/how it can possibly be fixed?
One more thing I should add is that I suspect this started to happen as a result of an unsuccessful attempt to root the device. Could that be the reason... and/or is there any hope... i.e. can it possibly be fixed?
I have also done a factory restore.. but it still does this! Please help
Listner said:
Hi everyone, first I sincerely apologise if I'm posting this in the wrong forum (and if so please direct me to the proper place). If it's okay, here goes:
I would greatly appreciate your help. I have this Chinese made car Headunit in my car (running android jellybean 4.2.2). I've had it for about a year and a half or so. A couple of months ago, the screen began to be unresponsive - after boot up. It is quite frustrating, as the unit itself is actually working.. but the screen just does not respond. This happens randomly! Sometimes you have to restart it several times before it works normally. And it does work normally sometimes, though there is no apparent order. It seems to just be quite random. I tried using one of the screen calibration apps from the appstore. It seemed to make a very minor difference (or perhaps not!). The problem is still very much there.
Sometimes, while it's unresponsive, if you touch an app icon and leave the unit alone, after some time the app would eventually open - though the time it takes to do that greatly varies. At this point, the screen may then work - sometimes normally, but in many cases, abnormally or unpredictably. In some cases it will not work at all.
Please does anyone know what is responsible for this and if/how it can possibly be fixed?
One more thing I should add is that I suspect this started to happen as a result of an unsuccessful attempt to root the device. Could that be the reason... and/or is there any hope... i.e. can it possibly be fixed?
I have also done a factory restore.. but it still does this! Please help
Click to expand...
Click to collapse
Greetings and welcome to assist. Unfortunately any modifications made to the system by the attempted root won't be undone by a factory reset. If you try asking here and give the full details of your model
https://forum.xda-developers.com/android-auto/android-head-units
hopefully the experts there can help you
Good Luck
Sawdoctor
Thank you very much Sawdoctor! I have now posted this at the link you kindly provided. Have a great night
Related
I am sorry to say, but I am not happy with my new phone !
Some serious problems with it.
1. sometimes when I push the powerbutton nothing hapens, and actualy I can see the phone is fuctioning (round button is flashing for new mail). After a few seconds I get the "famous" grey screen. Reboot is the only option.
2. sometimes I wake up and the phone has boot (I guess) somewhere in the night, because I have to give my accescode for the sim.
3. the "broken glass" isue is a problem and happens twice now
Think these are not small problems for a "Pro" phone.
Right now I don't have a riable and solid phone, and I think a pro phone should be that way .
Hope this things are fixed soon.
I wonder if this is a difference in roms or if you should return your touch pro. I've beating the hell out of my phone software wise to see how it will run and i haven't had a single problem yet. I haven't been charging it via the wall charger so maybe that has something to do with it but i doubt it.
Send it back! At least try that once, if you get the same problem again then either you are very unlucky, or there is a problem with all batches. I haven't had either of those problems once and got the phone the day it came out.
I only see one or two people complaining about these issues.
Steve
steveoidm said:
Send it back! At least try that once, if you get the same problem again then either you are very unlucky, or there is a problem with all batches. I haven't had either of those problems once and got the phone the day it came out.
I only see one or two people complaining about these issues.
Steve
Click to expand...
Click to collapse
I am thinking about it, to send it back. But I still hope it is a rom problem, like Bxsteeze said. Flashing another rom could help. Soon that is possible I will try.
If it doesn't help I send it back.(forgive my my English )
TBH i would do it the other way around. If flashing the ROM doesn't help because of a hardware fault and you have flashed another ROM, chances are you may not get the replacement you want.
especially as Olinex haven't finished the SPL Downgrader yet.....
DONT send it back ffs!!
We have just got HardSPL for the thing so you can actually try any ROM you wish, surely its worth the little hassle trying that first?!
I had the same "broken glass" like screen issue only once also when sitting overnight, but it wasn´t charging at all.
I have several other issue´s but it think it´s ROM related, and if it´s not i´m gonna send mine back aswel.
I've had issues 2 and 3 happen to me.
A couple of times now when trying to wake the device from an overnight charge in the morning I get no response, device locked. Soft reset and all is well.
Regarding the broken glass thing, that's definitely a software issue. Its TF3D having a spaz. If you disable it and then re-enable it, all is well.
Check out the issues thread here:
http://forum.xda-developers.com/showthread.php?t=418150
and here:
http://forum.xda-developers.com/showthread.php?t=420700
Hey if anyone doesn't want their Raphael. You could give it to me.
hardSPL ? Let the party begin
Problems
Hi,
Four problems i found so far.
First the broken glass effect. When the phone is ringing and i turn it on his screen the ringing stops and the 3dflo breaks. Or the screen turns grey.
Problem 2 After it restarts i get an device.exe issue.
Problem 3 volume of normal calling is very low. In a noisy room it is hard to understand the caller.
Problem 4 During a call several hick-ups. Also when the signal strength is max.
For know. It is a nice smartphone but some things need improvement.
Can I remind people there is an issues thread here:
http://forum.xda-developers.com/showthread.php?t=418150
I know a couple of pages got a bit OT about touch sensitive buttons etc but its back on track now. Log your issues in there guys so we can try and help each other better.
Syphon Filter said:
Can I remind people there is an issues thread here:
http://forum.xda-developers.com/showthread.php?t=418150
I know a couple of pages got a bit OT about touch sensitive buttons etc but its back on track now. Log your issues in there guys so we can try and help each other better.
Click to expand...
Click to collapse
And dont forget to add the info to the wiki.
My Touch Pro has had the 'wake up' problem (either refuses to without soft reset or shows me frizzed up screen), has frozen on me during basic setup (following a hard reset) and has given me several spontaneous resets.
It also keeps forgetting my wi-fi network exists.
I feel safe in saying that I have a faulty one, so I'm asking for a replacement.
EDIT: Fixed. For some reason it was a power issue. I used two different chargers (not cheap ones, but professional ones) and for some reason it wouldn't work well. However, I changed to simple USB chargers and it worked without a problem. Sorry for wasting your time. I will keep this thread here in case others come across my same problem!
Hi all,
I tried searching the forums over and over with no luck.
I purchased this stick very recently and found it to be a fake.
The problem I have encountered is that it randomly turns off whenever I open an app. It started with the browser-- every time I open the browser, it shuts off. I restored to factory settings and the browser was working, however every time I click into the play store it shuts down.
This happened from the first day I got the device-- I have never used it for more than ~2-3 minutes (the only thing which does not make it shut off is the settings!).
Maybe I am missing something. If you could kindly help me work through it it would be extremely appreciated.
Hey guys,
I need help. Badly. My trusty SCH-I535 has pretty much gone to pot over the last three days. It started with the lockscreen/power button becoming so loose and sensitive, that the screen was perpetually turning on and off. However, my warranty expired last Thursday. Aside from that, the software was functioning beautiful (Carbon ROM, unknown August 4.3 nightly). Today however, the phone decided to freak out. Suddenly, it began displaying the incorrect time, wouldn't show me new messages, and applications were incredibly unstable. In an attempt to fix the issue, I decided to re-flash the ROM. This however, made no change. Therefore, I made the decision to finally update to the most recent stable version. After doing this, the phone wouldn't boot past the carbon boot animation. I rolled back to an older build, and had the same issue.
Here's where it gets sucky. After rolling back didn't do anything, I was in the process of re-flashing 1.8. During install process, TWRP crashed. This left me without a bootable system partition. As the night has worn on, it's become worse and worse. Now, TWRP is crashing often before the splash screen, at the "Samsung Galaxy SIII" screen. Occasionally it will load, but always locks up and crashes before finishing the install process. Same deal with CWM. I have tried several versions of both recoveries and none have made a single bit of difference. I've scoured the forums, and can't seem to find an identical problem/working fix. I've tried everything I can find, and so far, nothing productive has happened. It's 3:25AM over here, and I'm exhausted. I'm at my wits end. Any input would be fantastic.
Thanks so much,
The_Unofficial
Did you try to flash via ODIN? Maybe it will help you to boot it to normal.
The_Unofficial said:
Hey guys,
I need help. Badly. My trusty SCH-I535 has pretty much gone to pot over the last three days. It started with the lockscreen/power button becoming so loose and sensitive, that the screen was perpetually turning on and off. However, my warranty expired last Thursday. Aside from that, the software was functioning beautiful (Carbon ROM, unknown August 4.3 nightly). Today however, the phone decided to freak out. Suddenly, it began displaying the incorrect time, wouldn't show me new messages, and applications were incredibly unstable. In an attempt to fix the issue, I decided to re-flash the ROM. This however, made no change. Therefore, I made the decision to finally update to the most recent stable version. After doing this, the phone wouldn't boot past the carbon boot animation. I rolled back to an older build, and had the same issue.
Here's where it gets sucky. After rolling back didn't do anything, I was in the process of re-flashing 1.8. During install process, TWRP crashed. This left me without a bootable system partition. As the night has worn on, it's become worse and worse. Now, TWRP is crashing often before the splash screen, at the "Samsung Galaxy SIII" screen. Occasionally it will load, but always locks up and crashes before finishing the install process. Same deal with CWM. I have tried several versions of both recoveries and none have made a single bit of difference. I've scoured the forums, and can't seem to find an identical problem/working fix. I've tried everything I can find, and so far, nothing productive has happened. It's 3:25AM over here, and I'm exhausted. I'm at my wits end. Any input would be fantastic.
Thanks so much,
The_Unofficial
Click to expand...
Click to collapse
Your broken power button is probably the issue. The reason your recoveries are crashing is likely because the power button is triggered and it's making the phone turn off in the middle of the process.
It's unfortunate your warranty just expired, but you can get it fixed through a website, then you should be good from there. Also I would try to call up Samsung and tell them what you think the problem is, they might give you a break and fix your phone anyway since it's only a week after warranty.
Sent from my SCH-I535 using Tapatalk 2
Details...
Alright guys. More details. Sorry it took so long to reply. Apparently I had Gmail set to send XDA emails to spam. Silly me.
The more times I attempt to boot to recovery, the earlier TWRP will freeze.
TWRP rarely makes it beyond the "Installing System" process
TWRP NEVER makes it beyond the "Creating Symlinks" phase
I'm using TWRP 2.6.3.0
If I let the phone sit, it gets farther in the installation process before hanging
Bad Username, I tried contacting Samsung and Verizon. Neither one of them would replace , or fix it for me. Have any specific resources for repairing the button? That would be excellent. I just ordered a cheap $3 case on Amazon to see if that would help fix the problem. I don't, however believe this is causing the problem. TWRP has a lockscreen. It never goes to the lockscreen, it just hangs, then eventually force reboots. Almost as if some temporary RAM storage is being filled up. It's quite strange.
skyss07 I would REALLY prefer not to flash to stalk. Like, REALLY. This would mean losing all my files and pictures. I'm not too keen on that. I'm saving that as a final resort only.
The_Unofficial said:
Alright guys. More details. Sorry it took so long to reply. Apparently I had Gmail set to send XDA emails to spam. Silly me.
The more times I attempt to boot to recovery, the earlier TWRP will freeze.
TWRP rarely makes it beyond the "Installing System" process
TWRP NEVER makes it beyond the "Creating Symlinks" phase
I'm using TWRP 2.6.3.0
If I let the phone sit, it gets farther in the installation process before hanging
Bad Username, I tried contacting Samsung and Verizon. Neither one of them would replace , or fix it for me. Have any specific resources for repairing the button? That would be excellent. I just ordered a cheap $3 case on Amazon to see if that would help fix the problem. I don't, however believe this is causing the problem. TWRP has a lockscreen. It never goes to the lockscreen, it just hangs, then eventually force reboots. Almost as if some temporary RAM storage is being filled up. It's quite strange.
skyss07 I would REALLY prefer not to flash to stalk. Like, REALLY. This would mean losing all my files and pictures. I'm not too keen on that. I'm saving that as a final resort only.
Click to expand...
Click to collapse
Mobile tech videos would do it, not sure what the cost would be, I'd try contacting them.
Sent from my SCH-I535 using Tapatalk 2
Hi,
I realize many of you will state this has been asked before but I really can't find a fix for the phone so I thought maybe it's best to ask my own question and describe the issue.
So I work in a small company dealing with recycled mobile phones. I've been there about a year and a half, I had no training as it was just me and another guy, so it was just google and a lot of help from this site, so thanks guys for all the great help as I've got most of my answers from previously asked questions. I'm not a complete noob, but still have lots to learn.
This question I will keep related to the Moto G. So in my company we managed to pick up around 20 Moto G XT-1032. However around 6 of them seem to have software issues, after a factory reset (after testing) 6 got stuck on a boot loop. So I searched around and found 'http://forum.xda-developers.com/showthread.php?t=2542219' which I followed and managed to flash the software back to 4.3, I had issues on an XP computer but after trying with a windows 7 it seemed to work and the phone booted up. The 6 which got stuck in a boot loop had previously been factory reset as I could see it was at the factory set-up when I turned them on. So I was quite confused why 6 would get stuck.
So today I actually finally figured out to move to a windows 7 laptop which allowed me to actually flash the phones. After flashing the phone back to 4.3 I tested the phone and all seemed fine, so as these are to be sold I had to factory reset them again (resetting through the standard settings, no special code). So once again they all seemed to get stuck in a bootloop, but instead of an actual bootloop it shows the Motorola logo and then the screen goes black but I can see the backlight is still on, then it just sits there as long as I leave it, over 4 hours so far.
I have attempted a second flash on one of the phones and it's done the same. I'm downloading UK firmware for the xt1032 not the dual sim version. I've held the power button for 120 seconds as someone mentioned that on some random thread. Managed to get to restart and got into the android bios thingy (not sure what it's actually called, hopefully you'll understand what I mean) and attempted a factory reset but it just gets stuck on the black screen (still can see the backlight is on).
I'm now out of ideas, I really don't know what else to try. I'd really appreciate if someone could shine some light on this and what could possibly be causing the issues. The phones look brand new and are known as '14 day returns' meaning someone has returned it from new after 14 days, they are then fully tested by the manufacturer before being sold to companies like ourselves. If it was one phone I'd suspect maybe a hardware issue but because it's 6 I'm just thinking this would be a strange coincidence.
I'd be interested to hear from anyone who could give me advice on, unlocking, flashing and anything else which could help me at my place of work. I work with Sony's, HTC's, Lumia's, Samsung's and Motorola's, and also every now and again ZTE and Huawei's. So feel free to contact me if you think you could offer me any advice, all is welcome.
Thanks for reading, and thanks in advance to any advice.
Chris
kimber015 said:
Hi,
I realize many of you will state this has been asked before but I really can't find a fix for the phone so I thought maybe it's best to ask my own question and describe the issue.
So I work in a small company dealing with recycled mobile phones. I've been there about a year and a half, I had no training as it was just me and another guy, so it was just google and a lot of help from this site, so thanks guys for all the great help as I've got most of my answers from previously asked questions. I'm not a complete noob, but still have lots to learn.
This question I will keep related to the Moto G. So in my company we managed to pick up around 20 Moto G XT-1032. However around 6 of them seem to have software issues, after a factory reset (after testing) 6 got stuck on a boot loop. So I searched around and found 'http://forum.xda-developers.com/showthread.php?t=2542219' which I followed and managed to flash the software back to 4.3, I had issues on an XP computer but after trying with a windows 7 it seemed to work and the phone booted up. The 6 which got stuck in a boot loop had previously been factory reset as I could see it was at the factory set-up when I turned them on. So I was quite confused why 6 would get stuck.
So today I actually finally figured out to move to a windows 7 laptop which allowed me to actually flash the phones. After flashing the phone back to 4.3 I tested the phone and all seemed fine, so as these are to be sold I had to factory reset them again (resetting through the standard settings, no special code). So once again they all seemed to get stuck in a bootloop, but instead of an actual bootloop it shows the Motorola logo and then the screen goes black but I can see the backlight is still on, then it just sits there as long as I leave it, over 4 hours so far.
I have attempted a second flash on one of the phones and it's done the same. I'm downloading UK firmware for the xt1032 not the dual sim version. I've held the power button for 120 seconds as someone mentioned that on some random thread. Managed to get to restart and got into the android bios thingy (not sure what it's actually called, hopefully you'll understand what I mean) and attempted a factory reset but it just gets stuck on the black screen (still can see the backlight is on).
I'm now out of ideas, I really don't know what else to try. I'd really appreciate if someone could shine some light on this and what could possibly be causing the issues. The phones look brand new and are known as '14 day returns' meaning someone has returned it from new after 14 days, they are then fully tested by the manufacturer before being sold to companies like ourselves. If it was one phone I'd suspect maybe a hardware issue but because it's 6 I'm just thinking this would be a strange coincidence.
I'd be interested to hear from anyone who could give me advice on, unlocking, flashing and anything else which could help me at my place of work. I work with Sony's, HTC's, Lumia's, Samsung's and Motorola's, and also every now and again ZTE and Huawei's. So feel free to contact me if you think you could offer me any advice, all is welcome.
Thanks for reading, and thanks in advance to any advice.
Chris
Click to expand...
Click to collapse
Before I start: DISCLAIMER: I DO NOT TAKE ANY RESPONSIBILITY FOR YOUR ACTIONS BY FOLLOWING MY INSTRUCTIONS. YOU ARE FULLY RESPONSIBLE FOR YOUR ACTIONS.
Now we got that out of the way...
Try upgrading to 4.4.2: http://sbf.droid-developers.org/phone.php?device=14 (Get the firmware here)
Use the thread you mentioned: http://forum.xda-developers.com/showthread.php?t=2542219
Hello guys,**
Well few days ago I accidentally dropped my Nexus 5 in a glass of water for just 1 sec. So I immediately switched it off and wait a bit to let dry then restarted it, and all seemed to work fine. But just some days later and up to now the phone boots up all fine as usual to the lock screen, and from there I can pull down the notification bar (and navigate through it, activate/deactivate wifi, etc..) but when I unlock it to get to the home screen it becomes all back and nothing appears on the screen even though the phone is still on.*
It's really confusing and weird. When I call the phone it rings (so no signal or sound problem) but I can't still access the screen to take the call as it's all back and unresponsive.
Following some suggestions I disassembled the phone and cleaned it dry but same results again! So now I think the problem is somehow related to the motherboard, coz as you might notice on some of the pictures attached, it seems that some plastic parts have melt down to cover other smaller parts. Anyway guys,*I'm just wondering if some of you guys had experienced something like that and if you were luckier*to find a solution or any directives that could help. Or you even think that's a motherboard problem like, do you know any ways to fix that o buy a new one somewhere??
PLEASE!!
Sorry apparently, I can't publish links until I get like 10 posts or plus..
But anyway guys, I'd really appreciate your help.
Why did you power it on and short circuit it on purpose for??
Bump
@SekouCheikh
Maybe it's a coincidence that you dropped it in water and this happened a few days later. Once in a blue moon mine does something similar to this (although not usually as start up only after lots of use), but I think it's related to an app or xposed. I only notice it after installing a bunch of crap again. Maybe try a factory reset (do it though the computer) just to see if it is somehow not hardware related? That's what I would try first.
Help please
Ttt
Wait... Are you seriously posting from 2 different accounts??
<...>
First, simply try to factory reset or flash a new rom. There is not enough evidence to be sure it's a hardware problem, it could just as well be a coincidence that it started happening just now.
-SmOgER said:
Wait... Are you seriously posting from 2 different accounts??
<...>
First, simply try to factory reset or flash a new rom. There is not enough evidence to be sure it's a hardware problem, it could just as well be a coincidence that it started happening just now.
Click to expand...
Click to collapse
No, I just like to help
Help Op solve the problem please
Ttt