Related
Hey all, so I was on a business conference call this morning and immediately after the call I went to check my Call History, which had plenty of records in it last night, and there was no history. Furthermore, I lost the ability to make calls. I figured "oh it's just another stupid M$ bug... why don't I reboot." Well, bad idea. After rebooting, the phone now states it has No Service; however, Media Net is miraculously still connected. To test this anomaly, I loaded up IE and navigated to google.com. To my surprise, the page loaded! Nonetheless, I cannot load the phone app either manually or even by pressing the send button. I'm not receiving any texts or phone calls.
Is this a common problem? Could something have shorted out? Is my radio rom simply busted? Luckily, I'm a good boy and I synchronize my phone with my Nix box frequently so I have everything backed up. I just need to get my phone back to normal!
I'm running the newest ROM available from HTC America for AT&T. Here's what the screen says at boot time:
M 05 R 1.40.30.00
S 04 G 32.73.7020.16H
B 06 D 2.15
When the phone is booting, the screen that lists the roms looks like it always has. It doesn't say "No GSM" like some people have had on this forum.
I've rebooted the damn thing so many times that I learned something new today. WM5 has a Safe Mode... I'll be damned!!! It asked me if I wanted to reboot in Safe Mode at one point and I figured "why not? it has helped me fix so many Windows problems on PCs, surely it will be the answer to my problems on this phone right?!" Guess again, nothing different other than no Today plug-ins or autorun programs. I'm at a loss of ideas with this.
One thing you all should know is that I've taken the phone apart multiple times to replace my cracked screens (yes my screen has cracked more than once... I swear it's a design flaw in the phone). I even took it apart and assembled it perfectly this morning after I started experiencing the problems . That didn't help... but the good news is everything is intact hardware wise with the phone
I GREATLY appreciate any help. I've used this forum frequently to get tips and tricks on tricking my AT&T 8525 out. You guys are great. Thanks in advance!
So I just noticed something new. If my number is being dialed, the phone actually comes out of sleep mode and lights up but never rings or even shows a call is coming in. Of course I cannot pickup the call. This is VERY weird behavior. I'm getting quite desperate and there have been no posts so I'm getting ready to just reflash this phone. Any ideas, suggestions, comments, etc?!?!?!
Well, ended up just loading up a new rom (WM6) from AT&T/HTC and lost all of my customizations but the phone works well now. Thanks to all those who viewed this thread and THOUGHT about helping
I saw on few websites people complained about this issue. Well some of them at least.
Does anyone has a slightest idea if this is a hardware or software issue?
I tried hard restarting the phone - nothing happens.
When i insert the headphones, nothinghappens. I installed that toggleheadset program, and all it does it enables me to hear sound through headset, but when i try skipping the song from the headset button, it does nothing.
Also, trackball backlight and button lights are out.
Its a 2 days old phone, i dont like the facts that i will give them a 2 days old phone to repair and then get it back. I bought the new phone...
Anyone has an idea? Is there any chance that this new software patch will fix this?
thanks in advance
well, first of all, report the problem to HTC....most people seem to complain on forums, but not to HTC, so it leaves an impression of a problem affecting only a few people, when it's not :/
second, i can only quote what they answered me:
We have received very, very few queries regarding the issue you are facing, so I thank you for taking the time in reporting it to us.
For the above reason, I can not confirm if a software fix is on its way, and indeed if HTC will play a part in this release. I have taken the liberty of passing this issue on to our developers for their consideration.
Thanks for your answer.
Actually i did contact HTC, out of the same reason you stated here. and here is what ive got:
Dear valued HTC customer,
Thank you for contacting our Customer Support Center. We are dedicated to providing you with the best quality service and answering all of your questions and concerns.
We would recommend you to hard reset your device. If this does not help please contact us in order to book your phone into repair .
If the above steps do not resolve your issue, we invite you to visit the support area on our Web site. Please go to: http://www.htc.com/www/support.aspx
i would just like to know if its a software or hardware issue.. but seems to me that its hardware.. not sure though..
i think it's software, otherwise that Toggle wouldn't do anything, what i don't get is why hard resets don't help....thought maybe there was something on the original SD card and formatting/changing it maybe lost us something important, but that seems unlikely :/
Mine got sent back to HTC over a week ago apparently they are INVESTIGATING!
why this stops T Mobile from giving me a replacement is a *&^&**^%$ mystery to me !
will bell them this week ....................ON MY OLD VIEWTY .......to get an update
I did sent mine back to the reseller here in Netherlands. Within two days I got a brand new one.
Everything seems to be working allright but the issue appeared three days after I turned it on so now is my second day. Fingers crossed tomorrow.......
Good luck. I think HTC received a lot complaints about this issue last week. I heard my reseller said they had three broken Hero's last week.
Its a hardware fault with a board that connects to the main PCB. Send it back for a refund/replacement. You shouldnt have to go the waranty route since it was obviously faulty when you got it. Even if it happened after 2 days, 2 weeks, 2 months or 6 months, it should not fail that quickly. The law is on your side.
I'm pretty sure HTC know about this problem since its all over the net now!
Hello guys,
I have a very strange but really bad problem: my omnia7 can't stay in standby.
When I press the power button, to turn off the screen and go in standby (so not the full turn off), my Omni7 wakes up alone, going on the unlock screen. In the same time, the phone rings with the ring that is played when you connect the phone for charging.
I've tried reboot, reset, hardreset, removing the sim-card, turning on/off "battery saver options" ... still that issue :crying:
Anyone has an idea?
I've flashed with a cooked rom (xda-devs Omnia7 Tango V4.0)
my current config :
OS version : 7.10.8779.8
hard version : 3.1.0.4
soft radio version : 2424.11.7.2
hard radio version : 0.0.0.800
loader version : 4.10.1.9
SOC version : 0.36.2.0
Thanks to any ideas, because that problem is killing me
my phone started doing this late last night too! i thorght it was because rain had gone into the power socket but if others are having same problem at the same time maybe not?
has your phone been exposed to water at all recently? is your phone jailbroken? cant realy think of other reasons
the problem stops when the phone is plugged in. is there anything that can trick the phone to thinking it is on charge? I have wphtweaks installed but the options there are not able to stop it
Hi,
I can't remember if my phone has been wet :/ I take care, so my phone never received water. But when I'm outside, under the rain, it's possible.
Today it was better, just a few times my phone wakes up alone.
I'll give you feedback in the next days. Let me know about yours
I managed to trick my phone into silence a few times earlier but it was difficult and then only lasted 5-10 minutes.
if yours didnt get wet it seems unlikely to do with water but I left mine ontop of the aga after removing the battery and over a relativly cool part. A few hours later and it seems to be working fine now.
I will report back if the issue arises again.
EDIT: Ahhhh!! STOP THE RINGING!!! started again this morning
Mine too !
This morning ... the ringing awakening problem !!!!!
But it was better this afternoon.
Really I don't know what happens.
Are we only two persons in the xda world with this problem????
this is realy weird now! mine was doing it in the morning but since about 12pm - 1pm it has been fine! I feel like its something to do with an installed homebrew app maybe.
I also have a custom rom but mine was flashed a long time ago and much older than yours. not sure which version
EDIT (1:10pm GMT): no problems since yesterday
EDIT2 (1:30pm GMT): again i spoke too soon!
Did you guys get this problem sorted out? Had the same problem recently and tried all the suggestions in other threads (bend USB pin, Reset/Restore Device etc) but nothing fixed it, so after being woken at 3am by constant charging tone, took to T-Mobile shop. They said it was a software problem. I said I'd tried all that and the most likely cause I'd seen on the internet was a duff USB port.
Anyway, T-Mobile sent it off for repair and 7 days later - returned and fixed. The repair sheet said software upgrade, but the phone had been reset to bog standard Phone 7, so unlikely. The T-Mobile repair tracking site (excellent) which shows blow-by-blow trace of what and where, showed initial software upgrade/no fix but I used their "contact us" facility to suggest a USB problem and by magic the repair tracking log showed a replacement USB port.
BTW - had to resort to an iphone and HTC android while Omnia was off for repair. Now I know why I like Phone 7 and can't wait for 8. The iphone GUI is so last decade and Android GUI is really just a copy of Windows 6.5 with XDA developers' tweaks isn't it.
Hi Wuzzok,
what do you mean by "bend USB pin" ?
Anyway, it seems like it's finished for me. I didn't get tht strange bug (soft/hard bug???) for a very long time. I just hope it's really over !
Same problem
Hi Folks,
I have the same problem, too. Yesterday afternoon on my way home the phone started ringing with the USB plug sound and always started up itself from standby mode.
As I have a custom ROM (mi7ROM) I first thought it could be a problem with the ROM - although I could not really believe it since it was running stable for months now. I flashed it again and nothing changed - still ringing and starting up itself
I managed to get rid of the sound by deleting the entry in the registry key "Local Machine\Current User\ControlPanel\Sounds\BatteryCharging\Sound" but that does not solve the real problem.
After reading here and in some other WP7 blogs I am sure that this is a hardware problem with the USB plug unit. As my phone is just 11 months old I opened an online ticket at "SAMSUNG online repair service" who promise to answer in the next 24 hours. So I just have to wait and see...
actual state
neutom said:
Hi Folks,
I have the same problem, too. Yesterday afternoon on my way home the phone started ringing with the USB plug sound and always started up itself from standby mode.
As I have a custom ROM (mi7ROM) I first thought it could be a problem with the ROM - although I could not really believe it since it was running stable for months now. I flashed it again and nothing changed - still ringing and starting up itself
I managed to get rid of the sound by deleting the entry in the registry key "Local Machine\Current User\ControlPanel\Sounds\BatteryCharging\Sound" but that does not solve the real problem.
After reading here and in some other WP7 blogs I am sure that this is a hardware problem with the USB plug unit. As my phone is just 11 months old I opened an online ticket at "SAMSUNG online repair service" who promise to answer in the next 24 hours. So I just have to wait and see...
Click to expand...
Click to collapse
Samsung sent me an offer to send the phone in for repair - but what should I say, the problem solved itself. For two days now the phone works normal again. So I had to cancel the service call .
mine hasnt done it in a long time either. looks like its just a temporary thing. I wonder what caused it! For me it started after I was using my phone in the rain and the usb slide was open so thats my suspect.
You may be right. Mine is "quiet" now, since a long time. Water may be the cause.
Update
Hi folks,
mine is mostly quiet again, too. Only few incidents "happen" but they do not last very long - only a few minutes. It's somehow spooky but I do not want to send it in to Samsung now when the error it not constantly reproducible.
I agree with you that there might be a correlation with humidity although I am sure that it did never get wet and I almost always keep the USB-shutter closed. Who knows ...
Sent it in
Finally I sent it in for repair today. It started ringing permananently two days ago...
Now I have to wait and see.
Final state
Okay, I received it back... and it works.
First they did nod find and could not reproduce the failure and wanted to send it back - only with a new flashed image - but fortunately the technician called me and I could describe the problem again. After waiting a few hours, the fault appeared again and they decided to change the mainboard.
I hope, that's all :laugh:
Hello,
Me too it makes me after my omnia 7 is dropped in water, but problem solved.
Me too
WuzzoUK said:
Did you guys get this problem sorted out? Had the same problem recently and tried all the suggestions in other threads (bend USB pin, Reset/Restore Device etc) but nothing fixed it, so after being woken at 3am by constant charging tone, took to T-Mobile shop. They said it was a software problem. I said I'd tried all that and the most likely cause I'd seen on the internet was a duff USB port.
Anyway, T-Mobile sent it off for repair and 7 days later - returned and fixed. The repair sheet said software upgrade, but the phone had been reset to bog standard Phone 7, so unlikely. The T-Mobile repair tracking site (excellent) which shows blow-by-blow trace of what and where, showed initial software upgrade/no fix but I used their "contact us" facility to suggest a USB problem and by magic the repair tracking log showed a replacement USB port.
BTW - had to resort to an iphone and HTC android while Omnia was off for repair. Now I know why I like Phone 7 and can't wait for 8. The iphone GUI is so last decade and Android GUI is really just a copy of Windows 6.5 with XDA developers' tweaks isn't it.
Click to expand...
Click to collapse
Are you really sure that the problem is USB port.. Mine too behave like this. I've tried to remove battery, factory reseting, reflashing ROM. But nothing works. Mine is Samsung focus
post to remove
My newly purchased ZenWatch is set to have Always-On Screen but after 5 seconds it fades a little, then, shows the dimmed version for a second, then goes completely black so I can't see anything until I wake it again.
Wear version 5.0.1
Connecting to Android 4.4.4
This happens the same with any watch face I select: pre-installed or new custom ones. I have tried uninstalling Wear and ZenWatch Manager, resetting the watch and starting over again, same thing happens.
Could an app or watchface I have installed be interfering with the Always-On option somehow??
I don't know if this is related but I had to return my first watch as it didn't charge, so this is the second one connected to my phone (after 'forgetting' the first then pairing the new one).
When I click on the Always-On tick box on my phone, it immediately updates this option showing on the Watch so it's definitely sending the command to it. It shows as Always-On selected on the watch.
Has anyone else had this bug and know how to fix it? Thanks.
Is cinema mode on?
annik1s said:
Is cinema mode on?
Click to expand...
Click to collapse
Thanks, no, cinema mode isn't on.
It's really curious, the screen fades slightly in brightness after five seconds, then goes to the dim version of the watch face, then goes completely black a second later. One tap brings it back so I'm it's like the regular off screen mode.
TheGreatWaldopepper said:
My newly purchased ZenWatch is set to have Always-On Screen but after 5 seconds it fades a little, then, shows the dimmed version for a second, then goes completely black so I can't see anything until I wake it again.
Wear version 5.0.1
Connecting to Android 4.4.4
This happens the same with any watch face I select: pre-installed or new custom ones. I have tried uninstalling Wear and ZenWatch Manager, resetting the watch and starting over again, same thing happens.
Could an app or watchface I have installed be interfering with the Always-On option somehow??
I don't know if this is related but I had to return my first watch as it didn't charge, so this is the second one connected to my phone (after 'forgetting' the first then pairing the new one).
When I click on the Always-On tick box on my phone, it immediately updates this option showing on the Watch so it's definitely sending the command to it. It shows as Always-On selected on the watch.
Has anyone else had this bug and know how to fix it? Thanks.
Click to expand...
Click to collapse
Hi,
I'm very curious to know if you have found a solution to this problem as my new ZenWatch is doing the exact same thing. Asus support has told me it's a firmware issue but that seem odd to me as the feature seems to work for others.
Chewie01 said:
Hi,
I'm very curious to know if you have found a solution to this problem as my new ZenWatch is doing the exact same thing. Asus support has told me it's a firmware issue but that seem odd to me as the feature seems to work for others.
Click to expand...
Click to collapse
Oh thank you for telling me I'm not at least alone! No I haven't found a solution - I have reset the device, removed all the Wear apps one by one from the phone (in case a setting is interfering) and nothing makes it work as it should.
So... firmwear meaning the version of Wear that's installed on the watch? I was considering seeing what options are on the debug? menu but following online instructions I couldn't get this to work (you have to swipe from top left etc). I'm on 5.0.1 build LWX48S bought in the UK, how about you?
Have you had another watch that you replaced? I have and thought maybe settings got confused between watches. On my previous one, the always-on screen worked fine on it. When I booted it up for the first time, it did a software update. It however had a power problem (didn't charge after 2 days), so I replaced it.
The replacement didn't update when booted up, and doesn't update when I reset, so I assumed it shipped with newer firmwear - maybe the always-on problem is caused by this?
One weird problem with the replacement watch is that it notified me that it was almost out of power, despite having about 75% batter left, then it switched off and didn't turn on until charged over night. Only happened once.
I was planning on swapping it for another at the shop but someone else having the issue makes me think it's software. Might wait for an update, but if not solved long term then I'm not happy - I want it to look like a watch rather than a blank screen.
TheGreatWaldopepper said:
My newly purchased ZenWatch is set to have Always-On Screen but after 5 seconds it fades a little, then, shows the dimmed version for a second, then goes completely black so I can't see anything until I wake it again.
Wear version 5.0.1
Connecting to Android 4.4.4
This happens the same with any watch face I select: pre-installed or new custom ones. I have tried uninstalling Wear and ZenWatch Manager, resetting the watch and starting over again, same thing happens.
Could an app or watchface I have installed be interfering with the Always-On option somehow??
I don't know if this is related but I had to return my first watch as it didn't charge, so this is the second one connected to my phone (after 'forgetting' the first then pairing the new one).
When I click on the Always-On tick box on my phone, it immediately updates this option showing on the Watch so it's definitely sending the command to it. It shows as Always-On selected on the watch.
Has anyone else had this bug and know how to fix it? Thanks.
Click to expand...
Click to collapse
Just got my Zenwatch and I am having the same problem... Resetting the watch helped. But, I am still not getting the watch to vibrate on notifications. It vibrates when I set an alarm (on the watch) to it's not the vibrating device itself...
TheGreatWaldopepper said:
Oh thank you for telling me I'm not at least alone! No I haven't found a solution - I have reset the device, removed all the Wear apps one by one from the phone (in case a setting is interfering) and nothing makes it work as it should.
So... firmwear meaning the version of Wear that's installed on the watch? I was considering seeing what options are on the debug? menu but following online instructions I couldn't get this to work (you have to swipe from top left etc). I'm on 5.0.1 build LWX48S bought in the UK, how about you?
Have you had another watch that you replaced? I have and thought maybe settings got confused between watches. On my previous one, the always-on screen worked fine on it. When I booted it up for the first time, it did a software update. It however had a power problem (didn't charge after 2 days), so I replaced it.
The replacement didn't update when booted up, and doesn't update when I reset, so I assumed it shipped with newer firmwear - maybe the always-on problem is caused by this?
One weird problem with the replacement watch is that it notified me that it was almost out of power, despite having about 75% batter left, then it switched off and didn't turn on until charged over night. Only happened once.
I was planning on swapping it for another at the shop but someone else having the issue makes me think it's software. Might wait for an update, but if not solved long term then I'm not happy - I want it to look like a watch rather than a blank screen.
Click to expand...
Click to collapse
I have the same version of Wear with the same build number and I am also in the UK (which may be the common factor here as it is looking quite likely to be a manufacturing batch issue). When I first got the my watch from Heathrow terminal 2 it had an older version of Wear pre installed and the always on mode was not working then either. This would suggest the Wear version is not the issue here but the ASUS firmware which links Wear to the hardware is at fault.
I have also done the uninstall all apps from my Nexus 6 and factory reset the watch thing but ultimately it made no difference.
This the response I received from ASUS BTW,
Thank you for contacting ASUS. We are sorry to hear about this problem. I believe this is due to a firmware bug, it is not a setting that you can choose.
Please be advised that I will forward your feedback to our HQ development department to see if our engineers can resolve this problem in the next firmware update.
We are sorry for the inconvenience caused.
I also share your sentiment that a watch that doesn't tell the time is not much use to me so I will be rolling the dice and returning it for a replacement unit in the hope for a device that works as advertised.
Chewie01 said:
I have the same version of Wear with the same build number and I am also in the UK (which may be the common factor here as it is looking quite likely to be a manufacturing batch issue). When I first got the my watch from Heathrow terminal 2 it had an older version of Wear pre installed and the always on mode was not working then either. This would suggest the Wear version is not the issue here but the ASUS firmware which links Wear to the hardware is at fault.
I have also done the uninstall all apps from my Nexus 6 and factory reset the watch thing but ultimately it made no difference.
This the response I received from ASUS BTW,
Thank you for contacting ASUS. We are sorry to hear about this problem. I believe this is due to a firmware bug, it is not a setting that you can choose.
Please be advised that I will forward your feedback to our HQ development department to see if our engineers can resolve this problem in the next firmware update.
We are sorry for the inconvenience caused.
I also share your sentiment that a watch that doesn't tell the time is not much use to me so I will be rolling the dice and returning it for a replacement unit in the hope for a device that works as advertised.
Click to expand...
Click to collapse
Did you return it in the end?
After several frustrating emails with ASUS support in which they replied with general info on how the Always on-screen setting can be set, then asked me what build number I had even though I told them this in the first place, they concluded it must be a hardware problem.
"Taking in consideration that you have both the settings enabled on your watch as on your connected device and you are using the latest firmware, I also believe this is being cause by a hardware fault. Please return the ZenWatch back to your reseller."
So I took the plunge and exchanged it for the second time with suspicious staff at the shop (it was past their 21 day return policy cut-off, so I had to order another, then swap the new one for mine, on their system they refunded the new one). Hey presto, the new one works fine!
This one shipped with: 4.4w.2, KNX01W, updated to: 5.0.1, LWX48S.
So overall sounds like perhaps just a hardware issue. I know it's a new product but it's lucky I like the look of the watch so much that I'm tolerating quite a few teething problems. The one I have now has a very slight ridge on the right hand side of the screen where it meets the metal frame, which you can feel when swiping right. Hopefully I'm just being overly-fussy now and I won't notice after a while, but it's not as smooth as my previous two watches. On the left of the screen it's completely flush.
TheGreatWaldopepper said:
Did you return it in the end?
After several frustrating emails with ASUS support in which they replied with general info on how the Always on-screen setting can be set, then asked me what build number I had even though I told them this in the first place, they concluded it must be a hardware problem.
"Taking in consideration that you have both the settings enabled on your watch as on your connected device and you are using the latest firmware, I also believe this is being cause by a hardware fault. Please return the ZenWatch back to your reseller."
So I took the plunge and exchanged it for the second time with suspicious staff at the shop (it was past their 21 day return policy cut-off, so I had to order another, then swap the new one for mine, on their system they refunded the new one). Hey presto, the new one works fine!
This one shipped with: 4.4w.2, KNX01W, updated to: 5.0.1, LWX48S.
So overall sounds like perhaps just a hardware issue. I know it's a new product but it's lucky I like the look of the watch so much that I'm tolerating quite a few teething problems. The one I have now has a very slight ridge on the right hand side of the screen where it meets the metal frame, which you can feel when swiping right. Hopefully I'm just being overly-fussy now and I won't notice after a while, but it's not as smooth as my previous two watches. On the left of the screen it's completely flush.
Click to expand...
Click to collapse
I went to take mine back last week only to be told by PC World that this product can only be bought on-line and I would have to buy another one and then return the first for a refund. Which is a bit of a scam to me as the replacement was at a higher price than the first one I bought from Heathrow Duty Free.
I am due to collect the replacement and have an argument about the price difference tomorrow so finger crossed I get a working one as well.
Chewie01 said:
I went to take mine back last week only to be told by PC World that this product can only be bought on-line and I would have to buy another one and then return the first for a refund. Which is a bit of a scam to me as the replacement was at a higher price than the first one I bought from Heathrow Duty Free.
I am due to collect the replacement and have an argument about the price difference tomorrow so finger crossed I get a working one as well.
Click to expand...
Click to collapse
Ha, mine was from PC World too. I guess it's not their fault that your original one was bought duty free & therefore cheaper, but really if it's faulty they should treat it as such. They did offer me the option of booking it in as faulty, then it would have been sent off to ASUS and in all probability replaced with a new one anyways, but he didn't know how long this would take. So I just took the other option of buying another, having it delivered to the store the next day then swapping & refunding the latest transaction.
TheGreatWaldopepper said:
Ha, mine was from PC World too. I guess it's not their fault that your original one was bought duty free & therefore cheaper, but really if it's faulty they should treat it as such. They did offer me the option of booking it in as faulty, then it would have been sent off to ASUS and in all probability replaced with a new one anyways, but he didn't know how long this would take. So I just took the other option of buying another, having it delivered to the store the next day then swapping & refunding the latest transaction.
Click to expand...
Click to collapse
Well the good news is I now have the replacement watch and it works as advertised. I did have to complain a lot to get the difference in price resolved. I ended up complaining so much that the store manager gave me the money out of his own pocket just to get rid of me .
Hi, I have a LG K20 Plus. I currently can't turn the phone on, so I don't have much software information to give you. The phone was bought at T-Mobile (Metro by T-Mobile) and I had a SafeLink sim card and a 16 gb micro sd card inserted when the issue started. I have since removed both. It says Qualcomm snapdragon on the screen when it starts. It was also rooted and the bootloader is unlocked.
I broke the screen on my phone and I decided to do the repair myself. I have done about 7 or 8 screen replacements and I actually did this phone a year ago with no issues, so I felt I could manage this one as well. I bought an entire display (from ebay) and switched it out with no problems. Initially it worked great! I used it for a few days before realizing that I had no sound. I opened it back up and noticed the loud speaker had fallen out. I found it, put it back in, reassembled it as I normally do and turned it on.
NOTE: when I was reassembling it the second time, I actually tried to put a screw in a hole that wasn't a screw hole. I used a light to normal amount of pressure but I didn't force it. I think it's the hole where the moisture detector is. Picture #1
I turned it on and right after the logo screen I got a message that said "High temperature detected Powering off for your safety" and it immediately shut off. The phone does appear to charge normally but it won't stay on. I did a factory reset (I'm not sure if it's still rooted but the bootloader is still unlocked). I also switched back to the old (broken) display just to check if that would work. I couldn't see any difference in the shielding but I switched them just to be sure. I bought a new battery and installed it. I took a q-tip and 95% Isopropyl Alcohol and cleaned pretty much the entire motherboard, paying special attention to the battery connections. After each one of these things, I tried to start it with the same error message immediately upon start up.
NOTE: At no point has the phone every physically felt hot or even warm. I don't think it's on long enough for it to get hot. But something is wrong and I have no idea what it is. I, literally, took the phone apart, put in the speaker and put it back together in less than 5 minutes. Could it be I just bumped something and knocked it loose?
I searched for any information I could find both here and with google but there is next to no information on the LG K20 Plus. I did find some information on the LG V20 that had overheating issues, and that has been all the luck I've had. I watched several videos and it seems the solution is to apply thermal paste. But my phone doesn't have any evidence that thermal paste was ever on it. I went and bought some but I have no idea where exactly to put it or even if it's needed. Most videos showed people using some kind of aluminum foil but I'm not sure if that is safe. I have several old phone laying around and I managed to get some of the silver tape and a copper square thing but, again, my phone did not have these things to begin with. I don't want to start adding things only to make it worse.
There is a slight difference of the tape that is on my phone now (the display I just bought) as compared to the old one (broken display). Picture #2 Again, I have no idea if that means anything but I thought it worth mentioning. Picture #3 is how it looks now as if I were going to put it back together. Picture #4 is the part (don't know name) where the videos show to apply the thermal paste and the shielding.
I'm really at a loss as to what to do next and I can't really afford to take it in to have it repaired before next month. If anybody has any insight or answers as to what happened, I'd be very grateful for your help. I'm sorry for the long post. I just wanted to tell you everything I have done in detail. Thank you
If you're using Kernel Auditor or any other kernel adjustment simply reset to default and use only ondemand or interactive. There's also options for the thermal portion of the kernel, don't mess with those. If VCC or another thermal option was checked off turn it back on. Putting the GPS to the moderate setting (the one below high accuracy) will keep the temps down as well. Are you using a custom ROM? If you're on Discord you can feel free to message me SCOPE★ BRΞΛD #8460 . I am only offering that so we can get this resolved quickly for you, just copy and paste since I use special characters.
Omgosh, thank you so much for taking the time to respond! Although I'm sure everything you are saying is very smart, I have absolutely no idea what you're saying. I'll do my best to try and answer you. I don't know what SCOPE is or how to send a message there. I don't think I'm using any thing for the "kernal". Also, I don't know what VCC or Discord is. As far as turning off setting for GPS or any other app, the phone will not stay on. I get about 1 sec after the logo when it boots up, then the error message about overheating and it immediately shuts off. I did a factory reset so everything should be good to go as far as apps. I don't think I'm using a custom ROM. The only thing I did was install TWRP, unlocked the bootloader and rooted the phone a year ago but nothing since then. As I stated earlier, this happened right after I did a display repair. Is there something on the MOBO that can get bumped that will make your phone get hot or send a overheating error. My phone doesn't show any sign that there was ever thermal paste on it prior but should I add some now. Will that help?
Update... Now the phone does not power on at all. When I plug it in to charge it I get an error that says "Device temperature is too high or low. Please move to another place to charge. I wonder where you went. I googled SCOPE so I could sign up to message you like you asked me to but nothing but definitions came up. I know I'm out of my league here. You guys all talk so technical. I didn't understand one thing the person asked me for. I know it's rare to get a response as quickly as I did and I was so happy to see someone had responded. Now, I just feel stupid and defeated. I thought this site was inexperienced with cell phones friendly. I'm just trying to get help so I don't have to go out and buy another phone again. Can someone refer me to a site that is more directed toward people who don't know much about the technical side of cell phones... please! Again, thank you for your time.
HelpNeededPlz said:
Update... Now the phone does not power on at all. When I plug it in to charge it I get an error that says "Device temperature is too high or low. Please move to another place to charge. I wonder where you went. I googled SCOPE so I could sign up to message you like you asked me to but nothing but definitions came up. I know I'm out of my league here. You guys all talk so technical. I didn't understand one thing the person asked me for. I know it's rare to get a response as quickly as I did and I was so happy to see someone had responded. Now, I just feel stupid and defeated. I thought this site was inexperienced with cell phones friendly. I'm just trying to get help so I don't have to go out and buy another phone again. Can someone refer me to a site that is more directed toward people who don't know much about the technical side of cell phones... please! Again, thank you for your time.
Click to expand...
Click to collapse
Hey, I just wanted to say sorry this happened to you. The same thing happened to me. My LG K20 Plus, no matter what button combinations I push and for how long I hold them, will not turn on or go into download mode. Plugging it in to a charger or PC does nothing either. Before it got to this state, I got the infamous green screen of death/Demigod crash handler (google this--it's a known issue with some models of LG phones and it happens when they overheat). It's definitely a hardware/build issue, and especially since this issue keeps the phone from turning on or connecting to a computer, I don't see a workable fix short of buying a new phone, unfortunately. Again, I'm in the same boat so I'm not happy about it either. I would say XDA is by far the best site to find a fix to this sort of problem, so if no one here has any suggestions on how to fix it, I think you (we) may be out of luck.
Thank you for letting me know. I'm not sure of some of what you said but I did catch the bottom line. Basically, just hold onto the phone until someone here comes up with a fix or workaround? I have a question for you. Did your problem start after you did some kind of repair? I'm wondering if I bumped something on the mobo to make it give a false overheating error. Do you happen to know where that sensor might be located? Sorry you are having problems to. It really stinks when your phone breaks and no matter how much time and energy you put it to figuring out the problem to fix it, there just isn't any good answers out there. I wish you lots of luck and if you figure anything out, please update here so I can try it too.
You need a whole new phone.
That or you're gonna have to replace the hardware