Guys, i have a Diamond, but, yesterday the diamond turn off, and don´t turn on, i tried to do a soft and hard reset and nothing, i tried to enter in bootmode and nothing, when i put the battery the screen turn on, and the diamond vibre, but nothing else, what i can do??
rmorera84 said:
Guys, i have a Diamond, but, yesterday the diamond turn off, and don´t turn on, i tried to do a soft and hard reset and nothing, i tried to enter in bootmode and nothing, when i put the battery the screen turn on, and the diamond vibre, but nothing else, what i can do??
Click to expand...
Click to collapse
what did you do *before* your diamond stopped turning on?? unless you had a completely unpredicted system meltdown of your diamond for injecting it with super high voltage. it is rare for it to not power off unless you did something ... so please elaborate so we can assist better.
Ok, yesterday i use the phone like anothe normal day, in the night i turn off the phone, and in the morning, when i tried to turn on, i have this problem, for example, when a tried to do a soft, hard reset, the screen is in black, when a conect the phone to the usb the screen is black, is, i left the phone alone, in 3 minutes the black screen again, i don´t know why.
any LED activity when plugged into USB?
I think it is a major manufacture problem
I had the same problem, taking out the battery waiting a while and inserting it back, will solve the problem for some time but it will happen again.
Finally I sent it to the HTC support center.
I don't understand why HTC didn't recall.
If you'll search this forum you'll see the same problem in different stages, some times it's a blank screen but the phone will ring and some are just freeze.
Hi, I've had my Diamond for about a month soon and it started earlier this week by not wanting to come on at all. Been taking out the battery for a few days but eventually got fed up and did a hardware reset tonight. Not long after that it just suddenly turned itself off and I couldn't get it back on again. I thought I'd pack it back into the box it came in and send it back tomorrow and took out the sim card. After that it came to life again.
Happened to get a call after that and that call was suddenly disconnected without any reason.
So I am not very happy with this phone at the moment. Would appreciate any advice or if you know for sure it can't be sorted maybe I should send it back and ask for another one?
Blazeitup123 said:
any LED activity when plugged into USB?
Click to expand...
Click to collapse
Nothing, but one time the pc detect the phone, but later nothing.
No Led activity either on mine when it went dead.
When the Phone goes dead, try cooling the phone down as much as possible, and try starting it up again.....
There is a problem with the HTC Diamond in that it can cook itself (excessive heat), due to the auto over temp function crashing and not switching off the phone..... (That's what I have been told at least...)
I know over around 5 Diamonds so far that have had this issue, where the symptoms slowly get worse...
Have a look at this thread....
http://forum.xda-developers.com/showthread.php?p=2905775#post2905775
PLEASE P.M. me if you have any of the symptoms described in the thread...
I have been TRYING to get my Diamond fixed under warranty now for 2 months with little success... And I kinda need to know how wide spread this problem is to proceed any further.
could not turn on after blank screen ...
Hello,
I've had the same issue as rmorera, and after I hard reseted the phone all went o.k.. BUT after I reinstalled part of the small apps I use, the phone started to go off again. So, the problem seems to be in the software ...
I believe the cause might be the SRS WOW which I use. I installed the .cab, then the .reg file provided (ufortunatelly I don't remember from which thread I got the files ...). And shortly after, the phone stopped working. I uninstalled the software, and now it works! Could it be that the SRS WoW did this?
I tried to reinstall the SRS WoW and I found that if enabled for "Internal (Stereo)" instead of "Headphones" it gets my phone shut when the WM blanks the screen. If I select the "Headphones" options the issue seems to disappear.
Still, the SRS WoW damages the volume buttons action, but I think this issue is on another thread ...
Hi guys,
The following problem has taken me litterally DAYS of reading XDA, trying everything I could, but still no solution. Googling and searching this forum didn't help either, and it's totally weird.
It's a Samsung Galaxy S GT-I9000, on which were installed, almost two years ago, the ClockWorkMod recovery, Darky's ROM, Froyo, and everything was fine for months. Then, one day, out of nowhere, it switched off, without notice. Impossible to switch it on again! I remembered having seen some strange battery behavior few days before, like falling from 80% to 30% with no reason, so I thought of a battery issue. I plugged it for a full night. In the morning, I was able to boot it, but not easily, and all apps were crashing: during boot, or when launched manually. Yes, all I tried were crashing! Then, the phone became fully not bootable: press the power button, the screen shows "Samsung GT-I9000", then switches off...
I ordered a new battery: same result.
A guy from a phone repair store told me to plug the phone, and keep the power button down for 2 minutes: after this, I could reboot the phone, and thus, wipe data (factory reset). But it didn't help.
After "playing" a bit with it, I realized that the problem is:
the phone won't boot if an external source of power is not connected (as said above, white text shows, then the phone "dies")
if started with power cord/usb, the phone will work fine, all the time
if started with power cord/usb, and the external power source removed once the phone is booted, the phone will work fine, UNTIL the screen goes black for power saving mode or by pressing pwoer button, after which, within seconds, you can't open the phone anymore. I mean: if you press the start/power button immediately after the screen goes black, the screen goes on again, and the phone is ok. If you wait for few seconds, it's over, you can't do anything, and have to reboot the phone. This said, the phone doesn't vibrate, so I suppose it's not really off. But then... what is this state??
I really tried my best: updated to GB2.3.6, bricked my phone trying to re-install the CWM and having a bootloop, installed and used Odin and Heimdall, reverted to stock kernel, etc, etc, etc.
I feel sorry to bother you guys, I was really convinced that with the incredibly huge amount of data, how-tos, explanations, etc. I would manage to get rid of this, but this problem, though I don't really think it's hardware (but maybe it is?) stayed across so many kernels, roms, etc. that it's killing me!
For the record:
Model number: GT-I9000
Micro-software (?): 2.3.6
Baseband: I9000XXJW4
Kernel: 2.6.35.7-I9000XWJW7-CL1125830 [email protected] #2 (problem was the same with [email protected] #2)
Version number: GINGERBREAD.XXJW4
Any help would be greatly appreciated, considering that a wireless phone that needs to be wired is a little bit of an issue... :laugh:
Thanks in advance !
Marc_B_ said:
Hi guys,
The following problem has taken me litterally DAYS of reading XDA, trying everything I could, but still no solution. Googling and searching this forum didn't help either, and it's totally weird.
It's a Samsung Galaxy S GT-I9000, on which were installed, almost two years ago, the ClockWorkMod recovery, Darky's ROM, Froyo, and everything was fine for months. Then, one day, out of nowhere, it switched off, without notice. Impossible to switch it on again! I remembered having seen some strange battery behavior few days before, like falling from 80% to 30% with no reason, so I thought of a battery issue. I plugged it for a full night. In the morning, I was able to boot it, but not easily, and all apps were crashing: during boot, or when launched manually. Yes, all I tried were crashing! Then, the phone became fully not bootable: press the power button, the screen shows "Samsung GT-I9000", then switches off...
I ordered a new battery: same result.
A guy from a phone repair store told me to plug the phone, and keep the power button down for 2 minutes: after this, I could reboot the phone, and thus, wipe data (factory reset). But it didn't help.
After "playing" a bit with it, I realized that the problem is:
the phone won't boot if an external source of power is not connected (as said above, white text shows, then the phone "dies")
if started with power cord/usb, the phone will work fine, all the time
if started with power cord/usb, and the external power source removed once the phone is booted, the phone will work fine, UNTIL the screen goes black for power saving mode or by pressing pwoer button, after which, within seconds, you can't open the phone anymore. I mean: if you press the start/power button immediately after the screen goes black, the screen goes on again, and the phone is ok. If you wait for few seconds, it's over, you can't do anything, and have to reboot the phone. This said, the phone doesn't vibrate, so I suppose it's not really off. But then... what is this state??
I really tried my best: updated to GB2.3.6, bricked my phone trying to re-install the CWM and having a bootloop, installed and used Odin and Heimdall, reverted to stock kernel, etc, etc, etc.
I feel sorry to bother you guys, I was really convinced that with the incredibly huge amount of data, how-tos, explanations, etc. I would manage to get rid of this, but this problem, though I don't really think it's hardware (but maybe it is?) stayed across so many kernels, roms, etc. that it's killing me!
For the record:
Model number: GT-I9000
Micro-software (?): 2.3.6
Baseband: I9000XXJW4
Kernel: 2.6.35.7-I9000XWJW7-CL1125830 [email protected] #2 (problem was the same with [email protected] #2)
Version number: GINGERBREAD.XXJW4
Any help would be greatly appreciated, considering that a wireless phone that needs to be wired is a little bit of an issue... :laugh:
Thanks in advance !
Click to expand...
Click to collapse
That's a very strange problem... let's try something, remove the battery, sim card and sd card and hold the power button for 1-2 minutes, btw when the screen is off, is really the phone off or just the screen? did you try to make a call to your phone when the screen is off?
timberman4444 said:
That's a very strange problem... let's try something, remove the battery, sim card and sd card and hold the power button for 1-2 minutes, btw when the screen is off, is really the phone off or just the screen? did you try to make a call to your phone when the screen is off?
Click to expand...
Click to collapse
Hi timberman thanks for the answer!
You're very right: I totally forgot to say that what initially allowed me to restart my phone "regularly" was this procedure of pressing the power button for 2 minutes (hint given by a man from a repair shop). Before this, I couldn't (kind of a bootloop).
It's a very good question! I don't think the phone is really off in fact, because there isn't this vibration saying the phone turned off... Let me try to call it!
F..k! I was redirected right away to the voicemail... so... phone was off
I'm starting to think it's an harware issue... I reinstalled lots of ROMs, kernel, etc. Same ****...
Any idea?
Marc_B_ said:
Hi timberman thanks for the answer!
You're very right: I totally forgot to say that what initially allowed me to restart my phone "regularly" was this procedure of pressing the power button for 2 minutes (hint given by a man from a repair shop). Before this, I couldn't (kind of a bootloop).
It's a very good question! I don't think the phone is really off in fact, because there isn't this vibration saying the phone turned off... Let me try to call it!
F..k! I was redirected right away to the voicemail... so... phone was off
I'm starting to think it's an harware issue... I reinstalled lots of ROMs, kernel, etc. Same ****...
Any idea?
Click to expand...
Click to collapse
Hi mark, i'm totally out of ideas for your problem... anyway, maybe you read mi answer wrong, in your post you say that the guy in the repair shop tell yo to press the power button with THE PHONE PLUGGED IN, but what i say is press the power button 2 minutes WITHOUT BATTERY, btw i keep thinking about this.. if any idea comes to my mind i tell you.
Hi again, try to play a song and turn the screen off to see what happens.
Sent from my GT-I9000 using xda app-developers app
timberman4444 said:
Hi mark, i'm totally out of ideas for your problem... anyway, maybe you read mi answer wrong, in your post you say that the guy in the repair shop tell yo to press the power button with THE PHONE PLUGGED IN, but what i say is press the power button 2 minutes WITHOUT BATTERY, btw i keep thinking about this.. if any idea comes to my mind i tell you.
Click to expand...
Click to collapse
Hi! Answering is already nice
I tried the button pressed for 2 minutes without battery: didn't change anything.
I tried playing a sound: MAN, YOU'RE A GENIUS!!! Launching the music, then forcing the screen off with power button lets the music play, and OF COURSE, I can reactivate the screen by pressing the home button. The screen goes off normally again after few seconds, but the music is still playing, etc. So, as long as the music goes, the bug doesn't happen!
Other hints:
For some time already, when I was removing the phone from my ear after a call, quite often, the screen was staying off, and I had to press a lot of buttons to have it on again, and be able to close the call
The moment where it crashes when booting without power is the very INSTANT where the initial white text (Samsung Galaxy S) goes brighter. So, if you unplug the power cord just after this, the boot ends normally. In summary, something happens at boot just after screen brightness changes which is the same thing happening when the screen goes off for power saving. All this, only when no external power is plugged.
Hehe, we (you) are making progress
Marc_B_ said:
Hi! Answering is already nice
I tried the button pressed for 2 minutes without battery: didn't change anything.
I tried playing a sound: MAN, YOU'RE A GENIUS!!! Launching the music, then forcing the screen off with power button lets the music play, and OF COURSE, I can reactivate the screen by pressing the home button. The screen goes off normally again after few seconds, but the music is still playing, etc. So, as long as the music goes, the bug doesn't happen!
Other hints:
For some time already, when I was removing the phone from my ear after a call, quite often, the screen was staying off, and I had to press a lot of buttons to have it on again, and be able to close the call
The moment where it crashes when booting without power is the very INSTANT where the initial white text (Samsung Galaxy S) goes brighter. So, if you unplug the power cord just after this, the boot ends normally. In summary, something happens at boot just after screen brightness changes which is the same thing happening when the screen goes off for power saving. All this, only when no external power is plugged.
Hehe, we (you) are making progress
Click to expand...
Click to collapse
Hi again, it seems like your phone is unable to exit the deep sleep mode or something like that so, let`s try another thing, in ICS or JB there´s an option in the developer option settings that unfortunately is not present in gingerbread roms, so, you can try to switch to a ICS/JB rom and go to settings-developer options and disable the "PM sleep mode" let`s see what happens then
timberman4444 said:
Hi again, it seems like your phone is unable to exit the deep sleep mode or something like that so, let`s try another thing, in ICS or JB there´s an option in the developer option settings that unfortunately is not present in gingerbread roms, so, you can try to switch to a ICS/JB rom and go to settings-developer options and disable the "PM sleep mode" let`s see what happens then
Click to expand...
Click to collapse
I tried to install ICS, with a GREAT tutorial found here: http://forum.xda-developers.com/showthread.php?t=1494493 Sadly, the phone reboots after installing the ICS kernel, and then doesn't work anymore, I had to reinstall the Gingerbread (I tried twice).
Last news: I let the phone play music (sound muted!!) for about 12 or 18h: all was fine! So I decided to pause the music, and see what happens. Boom ((c) Steve Jobs)!! The screen went black, and phone was "dead". I was expecting this, so no panick, I put back my SIM card, my SD card, and tried to reboot, with power cord plugged: it boots until the screen shows the small loader animation, then the empty battery image, but then goes black again, instead of showing the charging battery!! Download mode is still available, so I'll try to reflash the kernel, say.
It's like if each time screen was put black, phone was dying.
I can't stress enough how I appreciate your help: even if we can't save my phone, it's very pleasant to be able to TRY things. Thanks man!! :good:
Update: I reinstalled all... and it's not, even with power cord in, going further than the "Samsung Galaxy S" white text. The moment this picture disappears from screen, phone is dead. For good this time ?
Marc_B_ said:
I tried to install ICS, with a GREAT tutorial found here: http://forum.xda-developers.com/showthread.php?t=1494493 Sadly, the phone reboots after installing the ICS kernel, and then doesn't work anymore, I had to reinstall the Gingerbread (I tried twice).
Last news: I let the phone play music (sound muted!!) for about 12 or 18h: all was fine! So I decided to pause the music, and see what happens. Boom ((c) Steve Jobs)!! The screen went black, and phone was "dead". I was expecting this, so no panick, I put back my SIM card, my SD card, and tried to reboot, with power cord plugged: it boots until the screen shows the small loader animation, then the empty battery image, but then goes black again, instead of showing the charging battery!! Download mode is still available, so I'll try to reflash the kernel, say.
It's like if each time screen was put black, phone was dying.
I can't stress enough how I appreciate your help: even if we can't save my phone, it's very pleasant to be able to TRY things. Thanks man!! :good:
Update: I reinstalled all... and it's not, even with power cord in, going further than the "Samsung Galaxy S" white text. The moment this picture disappears from screen, phone is dead. For good this time ?
Click to expand...
Click to collapse
you tried to install the rom on the recovery instead of odin?
timberman4444 said:
you tried to install the rom on the recovery instead of odin?
Click to expand...
Click to collapse
Hi! No, I didn't, I used Odin. But now, I can't try anything anymore The only "results" I can get from this phone are:
- enter download mode and update from Odin (maybe from Heimdall, too, but I didn't check)
- reboot until the first moment the screen goes black, after which, the phone becomes fully unresponsive
Marc_B_ said:
Hi! No, I didn't, I used Odin. But now, I can't try anything anymore The only "results" I can get from this phone are:
- enter download mode and update from Odin (maybe from Heimdall, too, but I didn't check)
- reboot until the first moment the screen goes black, after which, the phone becomes fully unresponsive
Click to expand...
Click to collapse
so, you can`t install any rom at the moment?
timberman4444 said:
so, you can`t install any rom at the moment?
Click to expand...
Click to collapse
I can! I can install any kernel, or ROM, trhough Odin, but I can't boot at all... Except if someone has a magical trick, I would say it smells like coffin...
Marc_B_ said:
I can! I can install any kernel, or ROM, trhough Odin, but I can't boot at all... Except if someone has a magical trick, I would say it smells like coffin...
Click to expand...
Click to collapse
Pretty bad signals there.. i think you should go to a repair shop or buy another device
timberman4444 said:
Pretty bad signals there.. i think you should go to a repair shop or buy another device
Click to expand...
Click to collapse
Sadly, yes... thanks for helping however !
Hey guys,
I left my HTC One to charge and when I tried to unlock it, it wouldn't respond. Right now it's a blank screen, the red LED is on even when I unplug the phone, and the hardware buttons are lit. I've tried to restart the phone by holding the power, holding power + volume down, but nothing is working. Device isn't showing up under adb or fastboot devices. What is going on? How can I fix this?
Help me out. Thanks!
-Coby
Edit: Recently this has been happening to my phone frequently, but I am usually able to get it to restart doing the methods said above. This is the first time I can't get it to do anything.
Put it under a stronger light and longpress power + vol-
Try this
I was actually searching through old threads and found that same answer and tried it. I can't believe it worked! Thanks! Why does this happen though? And will this hopefully prevent it from happening later on?
Are you rooted with a custom rom?
However, idk why it happened
Guich said:
Are you rooted with a custom rom?
However, idk why it happened
Click to expand...
Click to collapse
I have 4.3 Google Edition on my phone with TWRP.
I'll remember this trick next time though. Thanks again!
COBYATCH said:
I have 4.3 Google Edition on my phone with TWRP.
I'll remember this trick next time though. Thanks again!
Click to expand...
Click to collapse
:good:
Strange that you had this issue, but :good:
Guich said:
Put it under a stronger light and longpress power + vol-
Try this
Click to expand...
Click to collapse
Why the stronger light? Im confused! :cyclops:
This has worked for me a ton of times too, I guess it must just trigger something with the light sensor the phone has and wakes it up.
TwinAdk said:
Why the stronger light? Im confused! :cyclops:
Click to expand...
Click to collapse
It's a tips
Maybe the light sensor is always on...
Sent from One with Tapa4
It happened to me when i was rooted and used CWM.
It happened everytime i let the battery run down completely.
I havent rooted my replacement yet and when i let it run down, charged it for ten minutes and it booted straight up.
Seems to be an issue with the phone reading the charge state of the safety circuit in the phone. Mere speculation but i havent heard of it happening to anyone who wasnt rooted with custom recovery....
kungfudavie said:
It happened to me when i was rooted and used CWM.
It happened everytime i let the battery run down completely.
I havent rooted my replacement yet and when i let it run down, charged it for ten minutes and it booted straight up.
Seems to be an issue with the phone reading the charge state of the safety circuit in the phone. Mere speculation but i havent heard of it happening to anyone who wasnt rooted with custom recovery....
Click to expand...
Click to collapse
Can you please give me a little bit more details?
I have exact the same issue: The battery ran out completely, then I can't charge it or turn it on.
I have tried
1. with charger connect to outlet, power + vol-
2. with charger connect to PC, power + vol-
3. under desk light, without charger connected, power + vol-
Nothing worked for me.
Some questions:
- Should I connect the cable when I attempt to turn on the phone?
- Is normal desk fluorescent light "bright enough"?
- Should I move the phone under the light first then press the button, or the other way around?
Thank you for your help!
i have the same problem in my htc eye. i tried your solution. but it won't worked for me. phone still on blank screen and red light is on. how can i fix it?????
my note 4 running poprocks and xposed wants to boot up but it never does. it vibrates, gives the jingle, then nothing but a pulsing blue light that goes from blue to almost cyan color. if i pull the battery and connect it to the pc, it vibrates and does a connect/disconnect sound over and over until i hear the jingle but then the light starts again. bad battery? for extra info, the battery on lollipop would give me false reports. it would say like 30% to dead instantly. i was reading it was a lollipop issue cuz others had this same problem. it wasnt that bad tho i would at least get the low battery notification before turning off but recently it never even makes it to that level. so around 20% before it died. also saw in the poprocks thread xposed was killing batteries on samsung devices. i didnt really have any issues before tho until lollipop so thought it was like others had said a lollipop issue on samsung.
How would Xposed kill a battery?
Try this...shut down, pull the battery out, plug the device into the wall, turn it on. Does it work now?
Sent from my SM-N910T using Tapatalk
Pick_A_Name said:
How would Xposed kill a battery?
Try this...shut down, pull the battery out, plug the device into the wall, turn it on. Does it work now?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
if i plug it in without a battery it does nothing. i tried holding all the buttons for 20secs and it just vibrates then plays the bootup sound then blue pulsing light. also since i tried this last night i would see the screen extremely brief show a line of light when it would either try to start or when i would force a reboot. i would not have noticed it if i wasnt in pitch black.
D200P13 said:
if i plug it in without a battery it does nothing. i tried holding all the buttons for 20secs and it just vibrates then plays the bootup sound then blue pulsing light. also since i tried this last night i would see the screen extremely brief show a line of light when it would either try to start or when i would force a reboot. i would not have noticed it if i wasnt in pitch black.
Click to expand...
Click to collapse
It should not without a battery if it's plugged in. Sounds like hardware to me.
Sent from my SM-N910T using Tapatalk
D200P13 said:
if i plug it in without a battery it does nothing. i tried holding all the buttons for 20secs and it just vibrates then plays the bootup sound then blue pulsing light. also since i tried this last night i would see the screen extremely brief show a line of light when it would either try to start or when i would force a reboot. i would not have noticed it if i wasnt in pitch black.
Click to expand...
Click to collapse
Have you tried to flash Xposed disabler? Or to flash your whole rom again? Because to me that simply sounds like a broken OS.
Regarding the battery issue, you need to calibrate it after you've flashed a new rom. Use "Battery Calibration' from Google Play.
Xelasarg said:
Have you tried to flash Xposed disabler? Or to flash your whole rom again? Because to me that simply sounds like a broken OS.
Regarding the battery issue, you need to calibrate it after you've flashed a new rom. Use "Battery Calibration' from Google Play.
Click to expand...
Click to collapse
no i cant access my phone at all the screen is totally black. i was able to odin flash stock rom but after the successful flash via odin i cannot hear a bootup jingle anymore and the blue led is gone. odin is still accessible tho. i was wondering if i should try a mhl but at this point i am not sure if the phone will detect it since IF it is working its still waiting for a setup.
btw who is the developer for the calibration app? there are a few but i would like to have it for future reference.
D200P13 said:
no i cant access my phone at all the screen is totally black. i was able to odin flash stock rom but after the successful flash via odin i cannot hear a bootup jingle anymore and the blue led is gone. odin is still accessible tho. i was wondering if i should try a mhl but at this point i am not sure if the phone will detect it since IF it is working its still waiting for a setup.
btw who is the developer for the calibration app? there are a few but i would like to have it for future reference.
Click to expand...
Click to collapse
Strange, so you were able to flash a rom even though your screen was black? Did you enter download mode blindly, or how did you do it?
The dev calls himself NeMa, the app is named Battery Calibration.
Xelasarg said:
Strange, so you were able to flash a rom even though your screen was black? Did you enter download mode blindly, or how did you do it?
The dev calls himself NeMa, the app is named Battery Calibration.
Click to expand...
Click to collapse
blind. i just counted the bootup sequence pressing the keys at the right time. so not sure. gotta buy a heat gun and see if its the screen. also wanted to try mhl but dont know which to try.
I think my battery start failing and phone randomly shuts down in 14 - 25 % battery level, tries reboot itself and usually stuck with blue to cyan pulsating led. Battery pull and connecting to charger always solves the problem.
Sent from my SM-N910T using XDA Free mobile app
D200P13 said:
blind. i just counted the bootup sequence pressing the keys at the right time. so not sure. gotta buy a heat gun and see if its the screen. also wanted to try mhl but dont know which to try.
Click to expand...
Click to collapse
Damn, I'm sorry. That does really sound like hardware failure.
Hardware same thing just happened to me been on cmremix all year on kit kat bootloader updated 2 weeks ago to 5.0.1 bootloader using the Odin method flashing back to stock than re rooting... Initially phone seemed sluggish but was fine than the phone randomly started turning off would vibrate as to reboot than nothing would appear on the screen but the blue led light would be light up... Went on till last Friday where the phone just died at 60 % phone wouldn't do anything hooked it up to my comp couldn't do anything other than the phone coming up as USB mass storage. Took it T-Mobile they tried everything and it wouldn't do anything I hear lollipop is causing a lot of problems for the 910t anyways got me new phone yesterday its a 910c odd I know and running 5.0.1 thing runs amazing on cmremix 14.2.....I would take it T-Mobile see if its under warranty goodluck
i ordered a heat gun and lifted the display. just as soon as i could peek in, i saw the flex was disconnected. connected the flex and display was back on! luckily it only cost me a heat gun.