Database Develop

White screen issue

I've been running the same radio, ROM, and SPL on my Tilt for months. A few days ago it started having a white screen issue. Whenever the screen turns off, it is solid white when it comes on (either by me turning it on or receiving a call or text). If I turn it off and on again everything is normal. I've soft reset my phone a couple of times. Is there anything I can try short of a hard reset or flashing another rom/radio/SPL? Thanks!

Also, I can no longer uncheck check boxes with the stylus. I have to use the hardware buttons.

wow crazy i just had this happen to mine phone today, luckily i found a tilt 2 on craigslist for 150 so i just went and got that. as soon as i backup all my stuff i am going to try and get the tilt back up and running. ill let you know if i get anywhere.

Yeah. I'm about go upgrade with AT&T and am going to get an Aria or an iPhone 4.

feanor512 said:
Also, I can no longer uncheck check boxes with the stylus. I have to use the hardware buttons.
Click to expand...
Click to collapse
pdtp said:
wow crazy i just had this happen to mine phone today, luckily i found a tilt 2 on craigslist for 150 so i just went and got that. as soon as i backup all my stuff i am going to try and get the tilt back up and running. ill let you know if i get anywhere.
Click to expand...
Click to collapse
Have you even tried a hard reset to see if that solved the problem?

I just flashed back to the stock ROM and it still happens. I guess it's a hardware issue.

I've never had an issue that I wasn't able to remedy by simply leafing through the forums here. However, this problem has put an end to all of that. I have the same exact issue as described by the OP and have absolutely no idea what to do. If anyone has any insight on the matter, please do help.

Qhusb_dload?

Today while using my one that is rooted with trickdroid 8.0.0 turned off at around 40% randomly, The screen froze at the lockscreen and I when put it to charge the orange light did not appear. I cannot reboot into recovery from the phone nor from adb. When plugged in the computer it is read as QHUSB_DLOAD. Any advice on how to fix this?

dlnas said:
Today while using my one that is rooted with trickdroid 8.0.0 turned off at around 40% randomly, The screen froze at the lockscreen and I when put it to charge the orange light did not appear. I cannot reboot into recovery from the phone nor from adb. When plugged in the computer it is read as QHUSB_DLOAD. Any advice on how to fix this?
Click to expand...
Click to collapse
QHUSB_DLOAD usually means a hard-brick. Does it power on at all? You might try leaving it plugged in overnight, but I suspect your phone just died.

iElvis said:
QHUSB_DLOAD usually means a hard-brick. Does it power on at all? You might try leaving it plugged in overnight, but I suspect your phone just died.
Click to expand...
Click to collapse
It does not power on at all. My battery was at ~40%. Is it possible for the phone to just turn off like that at that percent?

dlnas said:
It does not power on at all. My battery was at ~40%. Is it possible for the phone to just turn off like that at that percent?
Click to expand...
Click to collapse
I haven't seen it on the One, but it was a real problem with the One XL. Phones would just drop to 0% charge and die for no apparent reason. Not pleased to this happening on the One.

iElvis said:
I haven't seen it on the One, but it was a real problem with the One XL. Phones would just drop to 0% charge and die for no apparent reason. Not pleased to this happening on the One.
Click to expand...
Click to collapse
Before it died. I unlocked the phone and the only thing I could do was pull the notification drawer down. It would not let me open any app or even the app drawer.

dude this sounds frightening

Read the HTC Unbricking Project thread, the problem is HTC phone wide so I see no reason why the fix wouldn't also be. At the very least give that thread a read, you've got nothing to lose.

postfatal said:
Read the HTC Unbricking Project thread, the problem is HTC phone wide so I see no reason why the fix wouldn't also be. At the very least give that thread a read, you've got nothing to lose.
Click to expand...
Click to collapse
That fix is only for a couple of specific issues:
Note: This will fix only devices which were bricked by turning S ON. And bricks caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device. Any devices bricked with other ways are currently *not* supported. We are working on it
Click to expand...
Click to collapse
People tried it on the One XL/Evita when this happened, and it didn't work, unfortunately. Note that the method requires the battery to be removed.

tousary shall
iElvis said:
That fix is only for a couple of specific issues:
People tried it on the One XL/Evita when this happened, and it didn't work, unfortunately. Note that the method requires the battery to be removed.
Click to expand...
Click to collapse
I've only had the phone for 2 months and it already bricked. It shouldn't be a problem explaining it to AT&T and getting a replacement right? I mean if I can't turn it on they can't turn it on.

Had the same problem after flashing the wrong recovery..
THis means it is hardbricked and unrecoverable..
You could ask here: http://forum.xda-developers.com/showthread.php?p=43750389#post43750389
Else send it in for repairs

dlnas said:
I've only had the phone for 2 months and it already bricked. It shouldn't be a problem explaining it to AT&T and getting a replacement right? I mean if I can't turn it on they can't turn it on.
Click to expand...
Click to collapse
It's a hardware fault, from everything I've seen, and HTC or AT&T should replace it. AT&T tends to be very easy about this. If the phone won't power on at all, they shouldn't give you a hard time.

[Q] nexus 6 after new 5.1.1 update BIG PROBLEM(Keeps turning off

Hi , ive done all i can before coming here for help but this is my last resort as im stumped. About a month ago i updated my phone to the latest Android version on my Nexus 6. Literally straight after the update my phone began to play up. It started turning itself off at random times , not when i did a specific thing it could be anything and at any time. Spoke to Motorola and they were no use , so cleared my phone did a reset and still the same occurrence, as it was still on the newest version. But what i found was when the phone was plugged into the mains it didn't go off at all, but then again this problem happened right after the update. SO the next thing i have done is custom ROM but again the device will turn off randomly .I really need help as ive only had this phone since January and ive not been able to use it.
Thanks in advance

Sounds like battery defect. Has same issue on my n4 with regards to being ok when plugged in
Sent from my Nexus 6 using Tapatalk

benthebratt said:
Hi , ive done all i can before coming here for help but this is my last resort as im stumped. About a month ago i updated my phone to the latest Android version on my Nexus 6. Literally straight after the update my phone began to play up. It started turning itself off at random times , not when i did a specific thing it could be anything and at any time. Spoke to Motorola and they were no use , so cleared my phone did a reset and still the same occurrence, as it was still on the newest version. But what i found was when the phone was plugged into the mains it didn't go off at all, but then again this problem happened right after the update. SO the next thing i have done is custom ROM but again the device will turn off randomly .I really need help as ive only had this phone since January and ive not been able to use it.
Thanks in advance
Click to expand...
Click to collapse
Yes, absolutely sounds like the battery issue that is somewhat common. Best to RMA at this point because the next step is that the battery starts to expand.
You can, in the meantime, boot into bootloader, and select bootloader logs. Press power to select and then reboot. This clears and calibrates the battery stats. Most likely, the issue will return.

Evolution_Tech said:
Yes, absolutely sounds like the battery issue that is somewhat common. Best to RMA at this point because the next step is that the battery starts to expand.
You can, in the meantime, boot into bootloader, and select bootloader logs. Press power to select and then reboot. This clears and calibrates the battery stats. Most likely, the issue will return.
Click to expand...
Click to collapse
Thanks for the reply, what does RMA mean ? ive done that calibrating but didnt turn on . Also i spoke to Motorola and they said as i have a cracked screen they will have to replace that before reparining costing £120

benthebratt said:
Thanks for the reply, what does RMA mean ? ive done that calibrating but didnt turn on . Also i spoke to Motorola and they said as i have a cracked screen they will have to replace that before reparining costing £120
Click to expand...
Click to collapse
Return merchandise authorization.

Bricked phone?

Hi there!
I was wondering if anyone around here had some ideas on what to do.
My LG G4 had been working fine until today. I unlocked the screen to check my e-mail and it completely froze. It was plugged in at the time, so I unplugged it to see if I could restart it. The charging light was still blinking, the power button didn't respond, absolutely nothing.
I took the battery out, left it for a minute or so and rebooted. It loaded, unlocked, but I could only get to the app menu before it completely froze again. Afterwards, screen went black.
On the third try, it booted up to the LG logo and that's it. It popped up about 3 times and screen went black. No other response whatsoever. I can only try to reboot again only after taking out the battery, but it does the same thing.
I switched the battery with another one of the same model, nothing changed. Computer doesn't recognize it either.
I've looked around for a bit and I can't find anything like my case. The closest thing described is the boot loop. I'm not exactly sure that's my case, but it seems similar to a certain degree.
I got it to boot to recovery mode, but it doesn't do anything. It asks me if I'm sure I want to run it, and in the second 'yes' it freezes up completely again. Screen goes black and does absolutely nothing else.
Added note, phone upgraded to 6.0 yesterday morning. I had no issues with it until now. No app updates were running at freezing time.
I'm considering taking it to the store before I try anything myself, just in case there is still some warranty active.... But any ideas would be greatly appreciated.

sinajei said:
Hi there!
I was wondering if anyone around here had some ideas on what to do.
My LG G4 had been working fine until today. I unlocked the screen to check my e-mail and it completely froze. It was plugged in at the time, so I unplugged it to see if I could restart it. The charging light was still blinking, the power button didn't respond, absolutely nothing.
I took the battery out, left it for a minute or so and rebooted. It loaded, unlocked, but I could only get to the app menu before it completely froze again. Afterwards, screen went black.
On the third try, it booted up to the LG logo and that's it. It popped up about 3 times and screen went black. No other response whatsoever. I can only try to reboot again only after taking out the battery, but it does the same thing.
I switched the battery with another one of the same model, nothing changed. Computer doesn't recognize it either.
I've looked around for a bit and I can't find anything like my case. The closest thing described is the boot loop. I'm not exactly sure that's my case, but it seems similar to a certain degree.
I got it to boot to recovery mode, but it doesn't do anything. It asks me if I'm sure I want to run it, and in the second 'yes' it freezes up completely again. Screen goes black and does absolutely nothing else.
Added note, phone upgraded to 6.0 yesterday morning. I had no issues with it until now. No app updates were running at freezing time.
I'm considering taking it to the store before I try anything myself, just in case there is still some warranty active.... But any ideas would be greatly appreciated.
Click to expand...
Click to collapse
seems like infamous bootloop... harware issue. send it to tmobile or LG.

raptorddd said:
seems like infamous bootloop... harware issue. send it to tmobile or LG.
Click to expand...
Click to collapse
I was afraid so... Went directly to the T-Mobile store where I bought it and, since the warranty was still active, they exchanged it on the spot.
I just hope this one lasts longer than the other one did...
Thanks!

sinajei said:
I was afraid so... Went directly to the T-Mobile store where I bought it and, since the warranty was still active, they exchanged it on the spot.
I just hope this one lasts longer than the other one did...
Thanks!
Click to expand...
Click to collapse
yeah.. did you know manufacture date on the one affected by bootloop or first 3 serial number.?

raptorddd said:
yeah.. did you know manufacture date on the one affected by bootloop or first 3 serial number.?
Click to expand...
Click to collapse
Yup. Actually still have the box.... the date was 05/2015.
New one's date is 03/2016.

sinajei said:
Yup. Actually still have the box.... the date was 05/2015.
New one's date is 03/2016.
Click to expand...
Click to collapse
it was a 505.. most will bootloop... new one is. 603. theres hw 1,0 and 1.1.. this you look at software info ... in hidden menu.. in dialer..

raptorddd said:
it was a 505.. most will bootloop... new one is. 603. theres hw 1,0 and 1.1.. this you look at software info ... in hidden menu.. in dialer..
Click to expand...
Click to collapse
This one (603) is a HW Version 1.0 ...

sinajei said:
This one (603) is a HW Version 1.0 ...
Click to expand...
Click to collapse
mines its 601 and same HW 1.0 if they knew they revised 1.0 to 1.1 why not use the 1.1 if they knew this back in october 2015.. theres older phone from 2015 with HW 1.1

raptorddd said:
mines its 601 and same HW 1.0 if they knew they revised 1.0 to 1.1 why not use the 1.1 if they knew this back in october 2015.. theres older phone from 2015 with HW 1.1
Click to expand...
Click to collapse
That is an excellent question...
Btw, does your screen freeze up sometimes? 'Cause mine sometimes goes unresponsive right after I unlock it... I just lock and unlock it again and keeps working just fine, but it's kind of annoying... old one did it and it, now this one does it sometimes too...

sinajei said:
That is an excellent question...
Btw, does your screen freeze up sometimes? 'Cause mine sometimes goes unresponsive right after I unlock it... I just lock and unlock it again and keeps working just fine, but it's kind of annoying... old one did it and it, now this one does it sometimes too...
Click to expand...
Click to collapse
yes it does.. but very rare... not to often... but mines does using phone and it freezes then turn off screen and when back it all works... i used power button.. not sure why but it does..but liek i said not to often. its once in a while..

raptorddd said:
yes it does.. but very rare... not to often... but mines does using phone and it freezes then turn off screen and when back it all works... i used power button.. not sure why but it does..but liek i said not to often. its once in a while..
Click to expand...
Click to collapse
Good to know it's not just me then. Guess it's a common screen glitch then.
Thank you for the info!

Well another 505 g4 bites the dust. Playing a game, backed out of it, phone froze, pulled battery, turned on to endless bootloop, pulled battery again, now nothing and I mean nothing, no boot loop, no nothing
Definitely a brick. Computer doesn't recognize or even try to charge it. Hopefully still under warranty.
Sent from my LG-VS980 using Tapatalk

[Poll] Has your phone randomly powered off?

Has your 7 Pro randomly shut down since you have had it?
Seems like it's been happening for a fair few people on multiple carriers and versions of the phone, including myself. You can see complaints in the below thread.
https://forums.oneplus.com/threads/one-out-of-2-oneplus-7-pro-is-now-dead.1043492/
You can get your phone back on by holding power+vol up for a few seconds! This is super annoying as I use my phone as an alarm and now can't trust it to work.

Yes I have.

Nope

Twice...now I'm rooted we'll see if it continues
Sent from my GM1915 using Tapatalk

exxpired said:
Has your 7 Pro randomly shut down since you have had it?
Seems like it's been happening for a fair few people on multiple carriers and versions of the phone, including myself. You can see complaints in the below thread.
https://forums.oneplus.com/threads/one-out-of-2-oneplus-7-pro-is-now-dead.1043492/
You can get your phone back on by holding power+vol up for a few seconds! This is super annoying as I use my phone as an alarm and now can't trust it to work.
Click to expand...
Click to collapse
Could be Hardware/Software issue. But if you were able to revive it with the said shortcut, then I think it's a software issue.
Btw never faced this issue.

I have had this happen as well a few times but it was due to a certain kernel I was using.

Yup, was rather scared as even long pressing power didn't do anything. Thought it was completely game over. Luckily mentioned power-on button combo brought it back to life.
Has happened twice now. So far this and the worthless A/B partition shizzle has left a bad taste for now.

You could always check to see if this is ticked to make sure you don't miss an alarm.

I have this since day one no reboots at all

I have the T-Mobile version and converted to International running stock OS w/ elemental kernel. No issues since I bought it..

none so far. I have had my phone since last thursday and has a build date of 6.4.2019 everything works great no issues.

Not experiencing anything of that nature on my end luckily.

Happened to me the other day. I just assumed I drained the battery although I knew there was no way I used it that much since taking it off the charger. I just left it off for a while and then turned it on by attempting to go into the BL.

luckylui said:
I have the T-Mobile version and converted to International running stock OS w/ elemental kernel. No issues since I bought it..
Click to expand...
Click to collapse
Same here.
Sent from my GM1915 using Tapatalk

Happened to me 3 times already when I go to bed. So I miss my alarm to wake up. Since I have turned off that sleep optimization crap it hasn't happened. Not sure if that did anything to be honest.

mac796 said:
Happened to me 3 times already when I go to bed. So I miss my alarm to wake up. Since I have turned off that sleep optimization crap it hasn't happened. Not sure if that did anything to be honest.
Click to expand...
Click to collapse
Clock>Settings>Power off alarm

Nope. Only once got recory bl but was my own fault and was easilly fixable

No Issues since my possession at product launch.

B3311 said:
Clock>Settings>Power off alarm
Click to expand...
Click to collapse
Does that still power the device on in the powered off state?

exxpired said:
Does that still power the device on in the powered off state?
Click to expand...
Click to collapse
Yes. If that's turned on and your phone is off, it'll basically turn the phone on like you normally would using the power button. It does this a minute or two before your alarm is supposed to go off.