Database Users

Power button not working (unlocked device, 2nd owner?)Update!

So the power button on my nexus one completely stopped working. I shut off the device and could not turn it back on. After popping battery in an out a few times I finally somehow, got it to turn on. Now i'm going to need to make sure it stays on all the time.
Now my question. To me this looks like a manufacturers hardware defect, so would the unlocked bootloader and me being the second owner of the device make any sort of difference here?
Any other way to turn the device on when its completely shut off?
Update #1: 7/30/10
Called HTC, then i got transferred to Nexus one department then back to HTC. Described my problem to everyone. They were nice to say they will get that taken care of. Told him i got the phone as a gift, updated my info, and I'm doing the swap option. He also said that any "physical" damage to the device might be charged, aka broken screen or w.e, regular wear and tear is fine. Mentioned nothing at all about software. I'm flashing back to stock either way. Will update as time goes

Same power button problem. Haven't checked into warranty with bootloader being unlocked, but if you plug up the usb cord, wait for the little led light to come on, take out the battery and put it back in as soon as the light goes off, then it will power the phone back on.

Ah i guess that's how i got lucky with turning it on then.
Hmm, i might give them a call tomorrow and see what they say.

Let us know what they say if you don't mind.

No worries with HTC. I was a second owner of my first N1. I traded my Iphone 3GS for it. Unlocked the bootloader first 10 minutes i had the thing. Few weeks later. I saw dust under the screen. Called up HTC. Gave them IMEI. Told them my girl got it for me for my birthday. They gave me an address.(original owners). I said nope and gave them mine. Went through the process. I had them put a hold on my credit card for $525. They sent a replacement phone next day. I packed mine up and sent it back. I had to do this twice because the replacement after 3 weeks started getting dust again and i could tell the power button wasnt really working well also.
Now im a second owner of another N1. I traded my tmobile N1 for a ATT N1. woot.

You can also root the phone and put trackball wake on it....also, when the phone is off completely, the trackball WILL boot it - tested this myself today.

MaximReapage said:
You can also root the phone and put trackball wake on it....also, when the phone is off completely, the trackball WILL boot it - tested this myself today.
Click to expand...
Click to collapse
Honestly when my phone was off I tried booting by pressing trackball and holding, just pressing and nothing. How did you do it? is there a specific process? I already have trackball wake selected thankfully before this even happened.
Another question is, how in the hell would i get into recovery or any of those functions now?

Coderedpl said:
Honestly when my phone was off I tried booting by pressing trackball and holding, just pressing and nothing. How did you do it? is there a specific process? I already have trackball wake selected thankfully before this even happened.
Another question is, how in the hell would i get into recovery or any of those functions now?
Click to expand...
Click to collapse
You download quick boot and user that to get into recovery or bootloader.

I ended up receiving the new nexus one, but i sold it already so yea

Hi,
I've a nexus one with a broken on-off button, so now I can't boot my phone at all.
there is a rom to boot with trackball or any hardware button ?
thx

Read the thread
thebluest said:
Hi,
I've a nexus one with a broken on-off button, so now I can't boot my phone at all.
there is a rom to boot with trackball or any hardware button ?
thx
Click to expand...
Click to collapse
Read the Thread and there is a suggestion on how to turn it on

Hard bricked nexus 4 help please?

So last night I hard bricked my nexus 4. its rooted, with cyanogenmod 10.1 ROM, and ive never had any issues with this phone. I have no idea what happened, but I sent a text message to someone, and it powered itself down. it was fully charged when this happened, so I know its not the battery. ive done some research, and its a true hard brick. no bootloader, no recovery, I just get a red/orange flashing light if I hold down the power button. google said im still under warranty, and they will still replace it even with it being rooted. My question is, is it possible to fix without having to get a replacement, or JTAG? If anyone has had any success, please help.
And like I said, I was only sending a text. I have no idea why it bricked, it restarts itself once in a while randomly, but this time it didn't turn back on.

Try plugging it into the wall for about 5 minutes then try turning it on again. If it doesn't work, RMA it. Why would you risk your warranty and JTAG it?

exb0 said:
Try plugging it into the wall for about 5 minutes then try turning it on again. If it doesn't work, RMA it. Why would you risk your warranty and JTAG it?
Click to expand...
Click to collapse
No, I DONT want to JTAG it. im looking for alternatives. if its possible to fix a hard brick without JTAG or using my warranty. If at all possible, I want to fix it, because I have a lot of pictures and everything on there that I would like to get out of it. I don't want to lose them. JTAG is my last resort if I cant get it replaced, but they said they would. I want my stuff off it though.

sinndissension said:
No, I DONT want to JTAG it. im looking for alternatives. if its possible to fix a hard brick without JTAG or using my warranty. If at all possible, I want to fix it, because I have a lot of pictures and everything on there that I would like to get out of it. I don't want to lose them. JTAG is my last resort if I cant get it replaced, but they said they would. I want my stuff off it though.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2347060
This is your last hope. If it doesn't work, RMA it and request for your data to be saved. Not sure if they can do it, but just ask.

exb0 said:
http://forum.xda-developers.com/showthread.php?t=2347060
This is your last hope. If it doesn't work, RMA it and request for your data to be saved. Not sure if they can do it, but just ask.
Click to expand...
Click to collapse
thank you I really appreciate it. im gonna try it out and see if it works.
This might be a noob question, but ive never heard of download mode. is it the same as recovery mode on the nexus 4?

sinndissension said:
thank you I really appreciate it. im gonna try it out and see if it works.
This might be a noob question, but ive never heard of download mode. is it the same as recovery mode on the nexus 4?
Click to expand...
Click to collapse
Nope. It's different.

sinndissension said:
thank you I really appreciate it. im gonna try it out and see if it works.
This might be a noob question, but ive never heard of download mode. is it the same as recovery mode on the nexus 4?
Click to expand...
Click to collapse
You can compare it too fastboot mode.

gee2012 said:
You can compare it too fastboot mode.
Click to expand...
Click to collapse
ok so if the nexus 4 wont go into download mode, or fastboot, or anything else, I have no choice but to RMA it right? cuz the ONLY response im getting from it is a red/orange flashing light when I hold down the power button. other than that, nothing happens.

sinndissension said:
ok so if the nexus 4 wont go into download mode, or fastboot, or anything else, I have no choice but to RMA it right? cuz the ONLY response im getting from it is a red/orange flashing light when I hold down the power button. other than that, nothing happens.
Click to expand...
Click to collapse
Did you press volume down first and then the power button both for a few seconds to get into fastboot mode?

Nope. The ONLY time it has any sign of life is if the charger is connected to it and I hold down the power button. If it's NOT connected to the charger, pressing the power button does absolutely nothing. I can't go into recovery mode, download mode, or the bootloader. I've tried charging it overnight, (and part of the next day) left it off the charger for over a week, it shows up as "Qualcomm-something" when I plug it into a computer, but I can't do ANYTHING with it connected to a computer either, and after I got my replacement, I tried taking out the battery and putting it back in. There was still no change......I've literally done EVERYTHING short of JTAG. Trust me, I searched all over google, and XDA, and tried everything. As far as I know, hard bricking is rare, but it happens. And it just happened, to happen to me. So unless there's a solution someone knows of that I didn't just list, my last option is JTAG.

sinndissension said:
yep. ive done EVERY combination of holding down the buttons, no response. when I plug it in to a laptop, the laptop beeps, like the USB connection sound, but the nexus doesn't show up on the computer. I know the computer recognized what kind of phone it was, cuz the first time I plugged it in, I got a pop up message saying "installing qualcom drivers", or along the lines of that. other than that, NOTHING has worked. If theres ANY fix for this, id like to give it a try, cuz ALL my stuff is on there.
Click to expand...
Click to collapse
Try charging it for a while and try again in a few hours or better yet tomorrow. Sometimes that helps bro. If that doesn`t help you`ll have to take it in for repair an maybe they can salvage your data if they are wiiling to do that. Good luck.

I think it's just your battery(RLOD) instead of a brick.
See this:
http://forum.xda-developers.com/showthread.php?t=2250454
I wouldn't be worried about your files stored on your phone because I think Google has more work to do than search in peoples pictures. What I would worry about is your warranty since you have a custom rom, unlocked bootloader and root...
Sent from my Nexus 4 using xda app-developers app

Well, found out it WAS a hard brick. Google replaced it with my warranty. For some reason they returned my money before I even got the chance to send the broken nexus 4 back. Didn't even mail it. So I'm assuming I don't have to send it back. So I'm gonna JTAG the hard bricked nexus, and hopefully it'll work again.
Thanks everyone for your help.

sinndissension said:
ok so if the nexus 4 wont go into download mode, or fastboot, or anything else, I have no choice but to RMA it right? cuz the ONLY response im getting from it is a red/orange flashing light when I hold down the power button. other than that, nothing happens.
Click to expand...
Click to collapse
You may not be doing it right. When I get the flashing light on mine it means I forgot to let go of the power button fast enough. When it vibrates, let go of power button immediately but keep pressing the volume. Does your phone vibrate a few seconds prior to the flashing light?
Sent from my GT-P7510 using xda app-developers app

Nope. The ONLY time it has any sign of life is if the charger is connected to it and I hold down the power button. If it's NOT connected to the charger, pressing the power button does absolutely nothing. I can't go into recovery mode, download mode, on the bootloader. I've tried charging it overnight, (and part of the next day) left it off the charger for over a week, it shows up as "Qualcomm-something" when I plug it into a computer, but I can't do ANYTHING with it connected to a computer either, and after I got my replacement, I tried taking out the battery and putting it back in. There was still no change......I've literally done EVERYTHING short of JTAG. Trust me, I searched all over google, and XDA, and tried everything. As far as I know, hard bricking is rare, but it happens. And it just happened, to happen to me. So unless there's a solution someone know of that I didn't just list, my last option is JTAG.

sinndissension said:
Nope. The ONLY time it has any sign of life is if the charger is connected to it and I hold down the power button. If it's NOT connected to the charger, pressing the power button does absolutely nothing. I can't go into recovery mode, download mode, on the bootloader. I've tried charging it overnight, (and part of the next day) left it off the charger for over a week, it shows up as "Qualcomm-something" when I plug it into a computer, but I can't do ANYTHING with it connected to a computer either, and after I got my replacement, I tried taking out the battery and putting it back in. There was still no change......I've literally done EVERYTHING short of JTAG. Trust me, I searched all over google, and XDA, and tried everything. As far as I know, hard bricking is rare, but it happens. And it just happened, to happen to me. So unless there's a solution someone know of that I didn't just list, my last option is JTAG.
Click to expand...
Click to collapse
so i have the same problem. was about to tweet with full battery so my question is what did you end up doing? Did you fix it or abandon it?

Weird. I've had the "red light of death" 2 hours ago because i didn't put the phone on the charger and it had like 4%. Pressing Volume down + power got it to enter fastboot and i was able to start the phone normally so it's charging booted

Mashed_Potatoes said:
Weird. I've had the "red light of death" 2 hours ago because i didn't put the phone on the charger and it had like 4%. Pressing Volume down + power got it to enter fastboot and i was able to start the phone normally so it's charging booted
Click to expand...
Click to collapse
ok...that has nothing to do with a hard brick. That just means your phone was dying.

dominiqueovalle said:
so i have the same problem. was about to tweet with full battery so my question is what did you end up doing? Did you fix it or abandon it?
Click to expand...
Click to collapse
Ok, I got mine replaced because it was still under warranty, and normally, the manufacturer cant tell its rooted or unlocked if its a true hard brick, (rooting and unlocking voids your warranty.) So i got mine replaced.
If your NOT under warranty still, your ONLY option if you want to fix it is JTAG. Google it, it costs about 50 bucks on average, but its cheaper than a Nexus 4. Research JTAG before you try it though. Or you have to buy a new one. I still have my only one, and i basically use it for parts for my newer N4.
Is it a true HARD brick, or just a soft brick?

sinndissension said:
Ok, I got mine replaced because it was still under warranty, and normally, the manufacturer cant tell its rooted or unlocked if its a true hard brick, (rooting and unlocking voids your warranty.) So i got mine replaced.
If your NOT under warranty still, your ONLY option if you want to fix it is JTAG. Google it, it costs about 50 bucks on average, but its cheaper than a Nexus 4. Research JTAG before you try it though. Or you have to buy a new one. I still have my only one, and i basically use it for parts for my newer N4.
Is it a true HARD brick, or just a soft brick?
Click to expand...
Click to collapse
its a hard brick. ive tried it all bought a new battery installed it etc. ive looked up jtag and i have the money but idk if i should do it. do you recomend it? i have no experience doing anything like it and im planning on getting the iphone 6 in the fall but i cant stand not having a phone till then especially since high school starts soon.
But the reason im sure its a hard brick is cuz when it shut down the battery was like 50 and charging and it froze for 25 seconds or so then shut down and refuses to boot or show any signs of life now except a blinking or solid red light but its not the red light of death because i replaced the battery therefore i came to the conclusion that it is hard bricked.
i know ive said alot of unecessary information but my question is do you think i should buy the jtag thing? do you reckon its easy to do? or maybe i could pay an experienced professional to do it?
thanks for the reply btw

Phone finally booted after 3 day boot loop..

I decided to start a thread because I noticed there were multiples about this issue. So 3 days ago I was on Facebook when my phone randomly froze. I pushed the power button, and that's when it began bootlooping. I instantly tried booting into recovery with no success. I was hopeful, however, because I could still access the bootloader. I got on my computer and began researching the issue and steps I could take to fix it. I tried every method out there and was unsuccessful. I ended up buying a Pixel today off Craigslist and am loving it so far. So anyway since my Pixel came with the OEM charger, and I had been using a non-oem ever since I had my 6P, I decided to plug in the OEM and see what happens. Within the first hour my 6P began to get very hot, almost to the point where I couldn't even hold it in my hand. Keep in mind the phone was still consistently boot looping the whole time. So I decided to unplug it. Well I left it sitting and went about my business and when I came back to my bed I noticed it was doing the Google boot animation!!!! I started freaking out! After it booted up I finished the tutorial stuff and just let it sit on the home screen for a second. I noticed the battery was low so I figured I would plug the charger back up and let it charge. Well in the time it has taken me to write this post, it just started boot looping again... Lol. So I just unplugged the charger AGAIN, to see if it will boot up again. To me, it seems like there might be a hardware issue with my battery. Anyway, my 6P was rooted and running nitrogen OS (wasn't running the latest build but was 7.1.)

what are the exact symptoms? and does it boot into bootloader and recovery if not what is it physically doing?

dontbeweakvato said:
what are the exact symptoms? and does it boot into bootloader and recovery if not what is it physically doing?
Click to expand...
Click to collapse
As of now it is still boot looping and no it doesn't boot into recovery. Only symptoms I've noticed is the phone starts to get extremely hot when I plug in the OEM charger that came with my Pixel. I figured they were the same so that's why I decided to use it since it was OEM.

I had a 6p that bootlooped eternally couldnt access boot or recovery, I sent it in and they sent a new one. Board was damaged.
I also had a nexus 5 that bootlooped and it turned out to be a bad power botton. the internal connection was broken so it would get power and lose power all in the same second, off and on but too fast to see other than seeing a bootlooping device. that was fixed with a new power button which had to be soldered on.
if not on warranty you could take to a cell phone repair shop maybe they might be able to fix the issue.

dontbeweakvato said:
I had a 6p that bootlooped eternally couldnt access boot or recovery, I sent it in and they sent a new one. Board was damaged.
I also had a nexus 5 that bootlooped and it turned out to be a bad power botton. the internal connection was broken so it would get power and lose power all in the same second, off and on but too fast to see other than seeing a bootlooping device. that was fixed with a new power button which had to be soldered on.
if not on warranty you could take to a cell phone repair shop maybe they might be able to fix the issue.
Click to expand...
Click to collapse
It is under warranty, but the sad part is that I no longer have the receipt for it. I got the phone off Craigslist and the guy gave me the original box and receipt but I managed to lose it. I haven't been able to get it to fully boot back up again since last night. I'm not that worried about it anymore because I already have a new phone, but I wouldn't mind if it were to some how fix itself lol.

e1ement08 said:
It is under warranty, but the sad part is that I no longer have the receipt for it. I got the phone off Craigslist and the guy gave me the original box and receipt but I managed to lose it. I haven't been able to get it to fully boot back up again since last night. I'm not that worried about it anymore because I already have a new phone, but I wouldn't mind if it were to some how fix itself lol.
Click to expand...
Click to collapse
my first bootloop years ago i thought the same.
it wont fix itself. its not a software isssue because youd be able to at least boot into bootloader. it sucks to hear the truth but thats the truth.
its a hardware issue and you could take it to a repair shop because they will inspect and fix. small drops that dont harm the device can ultimately cause small breaks in the solder joints so who knows what is wrong without inspection

Bricked Le Pro 3 727 (Blue Screen of Death)

Hello friends,
My LeEco Le Pro3 (727) bricked two days ago and I haven't had any luck turning it back on. It was running LineageOS 8.1 latest official build with an unlocked bootloader, Magisk 16.0, TWRP 3.2.1, and OpenGapps ARM64 8.1 nano. Immediately prior to bricking I was setting it up for bluetooth with my car and was trying to run Google Maps through voice command. As I directed Google Maps to take me to a location, the phone froze, the screen got all "fuzzy" and I got the dreaded blue screen of death.
From that point on I have not been able to turn the phone back on. When I press the power button it will vibrate every 5-10 seconds as though it will turn on but it never does. Ive tried everything I can think of to get to work again including:
- Pressing power button for 2 min, 5 mins, 10 mins
- Pressing power button + vol up (recovery) for 2 min, 5 mins, 10 mins
- Pressing power button + vol down (fastboot) for 2 min, 5 mins, 10 mins
- Pressing power button + vol up + vol down (QFIL MODE) -> Installing Qualcomm driver, downloading "FlashOne2.0", flashing all versions of "qfil files" that I could find but still unable to boot up
- Pressing all different button combinations while plugged in to computer/charger
- Using different cords/chargers/usb ports
- Leaving it to charge overnight/full day then trying to boot up
- Leaving it sitting not charging for a full day then trying to boot up
At this point I'm starting to think it might be a hardware issue but who knows..
Any advice/suggestions would be greatly appreciated.
Thank you.

Where did you buy it from.
I don't have much to add here it seems like you have done everything that you could
Let's clear this up no fashboot right.
Only one thing to try hold power down then plug in USB.
Sent from my LEX727 using xda premium

My one did the same, the issue was motherboard. You should send it back to repair.

mchlbenner said:
Where did you buy it from.
I don't have much to add here it seems like you have done everything that you could
Let's clear this up no fashboot right.
Only one thing to try hold power down then plug in USB.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Thank you for the reply.
It was purchased from a local retailer here in the United States through Google Express. Fortunately I should still be able to return it for a full refund but I would rather have a working phone than my money back.
No flashboot either. It's like the phone just decided to quit working one day. Tried holding power while plugging in USB as well and no change.
marik1 said:
My one did the same, the issue was motherboard. You should send it back to repair.
Click to expand...
Click to collapse
The conclusion I'm reaching at this point too. I'll see what the return policy.

Well if it will not turn on it is hardware issue you should be able to return it.
Sent from my LEX727 using xda premium

That is so strange. The screen going fuzzy like that is indicative of a hardware issue, IMO. I saw that on my laptop once, but that was because I hit the screen too hard. Never seen a BSOD on an Android device before. TIL.
I assume you've already tried an adb logcat. Were you using the original LeEco cable? I heard it has issues since it's not up to spec. 99% hardware failure, but I can't help but think it has something to do with driver communication confusing the device and causing hardware failure (?) if that's even possible.

Just a final update for those curious.
After leaving the phone alone for two days I plugged it into the charger and low and behold it started vibrating and booted up by itself. It was running a Chinese developers editions 720 rom due to the QFIL File I had flashed in my earlier in my attempt to fix it. Battery was drained so I let it charge for a while and everything was fine until I attempted to restart the phone. As the boot animation was loading, I got the blue screen of death for a second time.
I took a quick picture, the phone shut off itself off, and same as before it wouldn't boot again. As other users have suggested it appears to be a hardware issue, likely with the motherboard. Fortunately I was still able to return the phone (purchased through Google Express via a local retailer) and received a full refund. I've since bought another Le Pro3 (727) and hopefully when that one comes in, it won't have any issues.
Thanks to all the users who left suggestions/tips.

shyboi122 said:
Just a final update for those curious.
I've since bought another Le Pro3 (727) and hopefully when that one comes in, it won't have any issues.
Thanks to all the users who left suggestions/tips.
Click to expand...
Click to collapse
You bought the same phone again? :good: You're courageous, lol.

i been experiencing the exact problem like your on my x720, as i boot up the system or enterting the recovery mode the screen go fuzzy on loading screen and shut itself off completly, i can still able access fastboot. As i left it for a while the phone will be able to almost finish the boot then ending it all with a blue screen.
Have anyone found a way to fix this DIY since my phone has past the guarantee plan ?

oneplus 2 not working after screen replacement

My screen broke 6 months ago, so it wasn't used/charged for 6 months. Now I've replaced the screen, but it won't start up anymore. First thing I saw was the warning "low battery", so I charged it for a while. Still, nothing. Charged it for several days, nothing. Checked the battery voltage, 3.80 volts, exactly what it should be I think?
The phone does do something though. When I hold the "on" button, after 5 seconds it buzzes and the screen shows the oneplus logo and android. Just for two seconds, then nothing. Same thing with "on" and volume down, the start-up screen for 2 seconds...
When I use "on" and volume up, I get the screen saying "fastboot mode". And that doesn't go away untill I press "on" for a while.
I can connect it to my laptop, but cant see it. But when I take the battery out while connected to the laptop, the phone will show the "low battery" warning. Connect the battery again, and the logo and android message come on for two seconds...nothing more.
So the screen works, the battery is charged, but no way to turn it on. Tried holding the "on" button for 15 seconds, same result. Just a 2 seconds oneplus logo visible...
I have no clue what this could be, I hope its not completely fubar...
Thanks in advance, Fred Doe

Hey Fred Doe,
I wouldn't like to hijack your post, but I seem to have run into the exact same issue here.
A friend of mine got his screen replaced, and the phone acts exactly the same as yours.
I have disassembled the phone and checked all connections, but everything seems to be correct on the inside.
The phone does seem to boot, and it does boot into recovery mode (it responds to the button presses by vibrating) but the screen just doesn't show anything.
Only when doing fastboot the screen stays on.
Hopefully someone here can point us in the right direction.

there's not much to hijack here...sure sounds like the same problem. At this moment I gave up, guess its a lost cause..

Guys, the exactly same thing here. I've tried to unbrick it but failed.... So far what I know is that bootloader is locked.
I would like to know what steps should us do in order unlock bootloader, get screen functioning while getting access back to bootloder (TWRP) so after that we can install a new ROM!
Any clue from the community of OnePlus 2? This phone is still a good phone! Thnx

Have you guys tried running the msm tool. It'll restore everything to stock if you can it to work. If either of you have magisk installed it can cause issues with charging while the phone is off I believe.
I mean honestly sounds more like hardware issue that a msm wouldn't fix, but it's weird that your screen works in fastboot.
If you do the msm tool though be aware it will wipe everything on your device, and relock the bootloader if it is unlocked.
Like I said doubt it will help, but just a thought.
Edit: Also make sure you use the correct one for your device.
Edit sorry guys wrong forum ignore everything I said. Apparently xda labs thought my OP6T was a OP2.
Sent from my ONEPLUS A6013 using XDA Labs

@TheLogicalGamer
no problem. Thnx anyway. I'm still locked with my OP2.

dajosova said:
@TheLogicalGamer
no problem. Thnx anyway. I'm still locked with my OP2.
Click to expand...
Click to collapse
But the screen does show up & stays on in fastboot?
I'm no expert but any stretch. I just jumped ship from lg my 6t is the 1st OP phone I've owned. But if the screen does work normally in fastboot then it wouldn't be illogical to entertain the idea that it was a software issue. So I mean this is a bit of a chin scratcher.
Sent from my ONEPLUS A6013 using XDA Labs

Thanks for replying.
IWhen I press Power + Vol. Up it shoes Fast Boot screen. Then I connect cable and sometimes I can use command line but can't unlock bootloader with command line. All methods found indicate to use Recovery but since my screen doesn't work on Recovery I'm stuck.
When I press Power + Vol. Down (for entering Recovery) screen it goes all black but the capacitive buttons and Volume button give back a vibration response, as if it have entered Recovery Mode but since I can't see nothing on screen I can do anything either.
My bootloader is locked because I see that info via command line.
Thanks anyway
PS: I think something is corrupted. My OP2 was unlocked much time ago. I frquently change ROM's and have also updated TWRP. The only thing I did was disassembling the phone in order to change a shattered screen glass.
I've also tried different methods and installed in my pc different Qualcomm drivers, ADB, etc.
I'm getting close to the point of testing with broken touch, buying a new touch screen but with frame or giving up completely and buy a new phone :|
The last option get me in doubt because I would like a phone wich is good and fast and decent battery but not with a premium price... and popular so I can unlock it without hassle in order to install root apk's.