Database Info

Nexus 5 touchscreen stopped working.

Hello,
My Xperia Z broke and I sold it. Last week I bought a Nexus 5 (white) and yesterday the touchscreen suddenly stopped working while browsing twitter. I rebooted and the touchscreen worked for 1 sec and then it stopped working again. It keeps working for 1 - 5 sec and then stops.
Is there a way I can fix this? The phone is rooted because I wanted to copy WhatsApp over from another phone because I lost my sim bound to whatsapp.
I can go to the shop I bought it and get it fixed under warranty because I did not do anything weird with the phone nor dropped it. but first I want to see if it can be fixed from home or if it is a software problem because the shop is a hour drive and I don't want to do without my phone for another 2 weeks.
Here is a video how it looks: youtube(dot)com/watch?v=EsSyC50Dksw
Thanks in advance!

Have you tried flashing the factory image?
Sent from my Nexus 5 using Tapatalk

tangosierra_ said:
Have you tried flashing the factory image?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Can you send me a link to a tutorial?
Thanks!

http://forum.xda-developers.com/showthread.php?t=2513701

mistahseller said:
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
Thanks! Will try now

tangosierra_ said:
Have you tried flashing the factory image?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Done. The touchscreen is still doing the same thing.

teunnk said:
Done. The touchscreen is still doing the same thing.
Click to expand...
Click to collapse
I guess it's just broken then, I'll get it fixed.
Thanks for the help!

teunnk said:
I guess it's just broken then, I'll get it fixed.
Thanks for the help!
Click to expand...
Click to collapse
Make sure you lock boot loader unroot etc reset tamper flag
Sent from The Deathstar

mistahseller said:
Make sure you lock boot loader unroot etc reset tamper flag
Sent from The Deathstar
Click to expand...
Click to collapse
I tried to lock the bootloader whilst in fastboot mode but cmd doesn't recognize the command?

teunnk said:
I tried to lock the bootloader whilst in fastboot mode but cmd doesn't recognize the command?
Click to expand...
Click to collapse
Ah, went to the directory in cmd and then did the command, locked now. thanks again!
almost forgot to lock it ;3

[Q] Nexus 5 most likely hardbricked what do I do? Please help

I think my nexus 5 is hardbricked doing a paanodandroid ota update
This happened on latest paranoid android + latest franco kernel + TWRP
I wanted to update pa gapps (first 2 downloads md5 checksum failed, third time it worked) and when the phone booted afterwards, systemui failed and I couldn't do anything. I Thought this wasn't a big problem since the phone managed to boot. I long pressed the power button to shut it down so I could boot into recovery to restore my backup I had recently made. When I tried to boot into recovery it wouldn't do anything. Not boot into recovery and not into fastboot. How is this even possible by simply flashing gapps?
What should I do?
I've tried all the button combinations for more than 15 seconds.

michaelsplus said:
I think my nexus 5 is hardbricked doing a paanodandroid ota update
This happened on latest paranoid android + latest franco kernel + TWRP
I wanted to update pa gapps (first 2 downloads md5 checksum failed, third time it worked) and when the phone booted afterwards, systemui failed and I couldn't do anything. I Thought this wasn't a big problem since the phone managed to boot. I long pressed the power button to shut it down so I could boot into recovery to restore my backup I had recently made. When I tried to boot into recovery it wouldn't do anything. Not boot into recovery and not into fastboot. How is this even possible by simply flashing gapps?
What should I do?
I've tried all the button combinations for more than 15 seconds.
Click to expand...
Click to collapse
Have you tried powering it on again mine sometimes won't bit straight away after long pressing power button but works after 5-10 mins
Sent from my Nexus 5 using Tapatalk

kevtrysmoddin said:
Have you tried powering it on again mine sometimes won't bit straight away after long pressing power button but works after 5-10 mins
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes I've tried it a few times already the last 45 minutes

michaelsplus said:
Yes I've tried it a few times already the last 45 minutes
Click to expand...
Click to collapse
I take it that it doesn't respond in any way to the charger or p.c.
Sent from my Nexus 5 using Tapatalk

kevtrysmoddin said:
I take it that it doesn't respond in any way to the charger or p.c.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Indeed it doesn't . The pc only recognizes it's an unknown usb device

michaelsplus said:
Indeed it doesn't . The pc only recognizes it's an unknown usb device
Click to expand...
Click to collapse
You could have a faulty memory issue
Sent from my Nexus 5 using Tapatalk

So, at this point it doesn't boot at all? Do you have a link to the gapps you flashed?
Sent from my Nexus 5 using XDA Free mobile app

michaelsplus said:
Indeed it doesn't . The pc only recognizes it's an unknown usb device
Click to expand...
Click to collapse
If you plug the N5 when he's off, do you see any led?

jd1639 said:
So, at this point it doesn't boot at all? Do you have a link to the gapps you flashed?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
It doesn't boot at all no.
It was downloaded through the paranoid android OTA app. It was the 20140531 version: http://goo.im/devs/paranoidandroid/roms/gapps
OverSpeed301 said:
If you plug the N5 when he's off, do you see any led?
Click to expand...
Click to collapse
No. No activity whatsoever.

michaelsplus said:
It doesn't boot at all no.
It was downloaded through the paranoid android OTA app. It was the 20140531 version: http://goo.im/devs/paranoidandroid/roms/gapps
No. No activity whatsoever.
Click to expand...
Click to collapse
I think it was just a coincidence that it failed after flashing gapps. I'd RMA it. Sounds like the emmc went bad. It's happened on a few n5's.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
I think it was just a coincidence that it failed after flashing gapps. I'd RMA it. Sounds like the emmc went bad. It's happened on a few n5's.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Will they help me out when the bootloader was unlocked and a custom rom and kernel installed?

michaelsplus said:
Will they help me out when the bootloader was unlocked and a custom rom and kernel installed?
Click to expand...
Click to collapse
If it doesn't boot who will know? Google's pretty cool about RMA's
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
If it doesn't boot who will know? Google's pretty cool about RMA's
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
That's a bit good news . Thank you
As i mentioned I managed to boot once into the (not working) rom after the (corrupted I think) gapps package had been installed, does that mean that the gapps file cannot have messed up the bootloader since I already managed to boot once after installing the package?

michaelsplus said:
That's a bit good news . Thank you
As i mentioned I managed to boot once into the (not working) rom after the (corrupted I think) gapps package had been installed, does that mean that the gapps file cannot have messed up the bootloader since I already managed to boot once after installing the package?
Click to expand...
Click to collapse
I just think it was a coincidence that your memory went bad after you flashed. Out would have happened even of you didn't flash the gapps. That's my theory anyway
Sent from my Nexus 5 using XDA Free mobile app

michaelsplus said:
I think my nexus 5 is hardbricked doing a paanodandroid ota update
This happened on latest paranoid android + latest franco kernel + TWRP
I wanted to update pa gapps (first 2 downloads md5 checksum failed, third time it worked) and when the phone booted afterwards, systemui failed and I couldn't do anything. I Thought this wasn't a big problem since the phone managed to boot. I long pressed the power button to shut it down so I could boot into recovery to restore my backup I had recently made. When I tried to boot into recovery it wouldn't do anything. Not boot into recovery and not into fastboot. How is this even possible by simply flashing gapps?
What should I do?
I've tried all the button combinations for more than 15 seconds.
Click to expand...
Click to collapse
Don't send it to an RMA follow this guide. BSOD/NoBootloader
This is a guide I created following the exact same issue you had. If THIS doesn't work then send it in to RMA

wolfirotisha said:
Don't send it to an RMA follow this guide. BSOD/NoBootloader
This is a guide I created following the exact same issue you had. If THIS doesn't work then send it in to RMA
Click to expand...
Click to collapse
Saw your guide, and thanks for it. But if the device doesn't boot it won't get into the alternate bootloader
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Saw your guide, and thanks for it. But if the device doesn't boot it won't get into the alternate bootloader
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Does the PC detect it when plugged in? If so then its not hardbricked.
If you have hangouts I can try to help better.
---------- Post added at 02:14 AM ---------- Previous post was at 02:02 AM ----------
And should my guide fail there is always this one. LG FlashTool

wolfirotisha said:
Does the PC detect it when plugged in? If so then its not hardbricked.
If you have hangouts I can try to help better.
---------- Post added at 02:14 AM ---------- Previous post was at 02:02 AM ----------
And should my guide fail there is always this one. LG FlashTool
Click to expand...
Click to collapse
Thank you. I tried both these guides but none of them worked. I can't get any life in the device.
The PC ony recognizes it as 'unknown usb device'

[Q] Lollipop Error Message

Hello xda forum
I had got my nexus 5 off contract from California, USA and am using it in Delhi, India. I dont know if this fact is causing the problem or not, so thought i'd mention it..
So ..my device wasnt receiving the lollipop ota update so i did the clear google framework app data trick and got the update..
When the system reboots to install the lollipop it shows "error" like after 10-15℅ of completion. This was yesterday. So now i got the ota update without the clearing the data of google framework and the same problem persists. It just shows 'error' and i have to restart the phone by pressing lock and volume up key..
Help. Please.
Thanks in advance

Also it was earloer rooted with towelroot. But i did unroot it with superSu a couple of weeks before ..

What error is it giving you?

_MetalHead_ said:
What error is it giving you?
Click to expand...
Click to collapse
It just says error. But after a little digging i came to find that this is probably because i tweaked a few system files when i was rooted. Like the mixer_path... Now i cant seem to remember the changes i made neither can i find the oroginal file for nexus 5 stock on the net.. Could you or anyone please help.. Any advise

rahul9five said:
It just says error. But after a little digging i came to find that this is probably because i tweaked a few system files when i was rooted. Like the mixer_path... Now i cant seem to remember the changes i made neither can i find the oroginal file for nexus 5 stock on the net.. Could you or anyone please help.. Any advise
Click to expand...
Click to collapse
Google nexus factory images. Just to be sure flash the recovery, system, and boot images in fastboot from 4.4.4
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Google nexus factory images. Just to be sure flash the recovery, system, and boot images in fastboot from 4.4.4
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Will i have to unlock my bootloader for all this? As i rooted my phone with towelroot i didnt have to unlock it earlier

rahul9five said:
Will i have to unlock my bootloader for all this? As i rooted my phone with towelroot i didnt have to unlock it earlier
Click to expand...
Click to collapse
You do need an unlocked bootloader. Get bootunlocker from the play store it'll unlock without wiping the device.
Sent from my Nexus 9 using XDA Free mobile app

Major problem

So i got my nexus 5 for like a year now and when i got it i flashed twrp recovery and kernel franco cause....I dont really know.
So i wanted to reset my phone so I did a factory reset and turns out i didnt turn off my freedom app...
So now i cant connect to google services and i cant turn off freedom cause u need a google account to enter the app.
Dont know what to do I need help......

FapMaster784 said:
So i got my nexus 5 for like a year now and when i got it i flashed twrp recovery and kernel franco cause....I dont really know.
So i wanted to reset my phone so I did a factory reset and turns out i didnt turn off my freedom app...
So now i cant connect to google services and i cant turn off freedom cause u need a google account to enter the app.
Dont know what to do I need help......
Click to expand...
Click to collapse
Worst case, just flash the factory image. Stay on stock if you don't know why you flashed twrp and a custom kernel.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Worst case, just flash the factory image. Stay on stock if you don't know why you flashed twrp and a custom kernel.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Im not sure either why i did that...
I tried to flash factory image but the fastboot.exe just crashed after something like 10 seconds

FapMaster784 said:
Im not sure either why i did that...
I tried to flash factory image but the fastboot.exe just crashed after something like 10 seconds
Click to expand...
Click to collapse
Exact fastboot error output, please.

nvm i solved it

Please update thread title to let other devs know your issue is solved.
Sent from my Nexus 5

FapMaster784 said:
nvm i solved it
Click to expand...
Click to collapse
How did you solve it?
Sent from my iPhone using Tapatalk

The simle way would be to use the file manager in TWRP to wipe the offending file....
SENT BY ENTANGLEMENT

HELP!!!!!! Locked bootloader after flashing a kernel and it doesn't want to boot

Hi guys
As you probably know by reading the title, i completely messed up. I was on the stock google factory image and decided to flash a custom kernel. I enabled usb debuging and oem unlock. after having unlocked the bootloader, I installed the twrp boot img and then flashed the kernel. All was well when i stupidly decided to lock my bootloader. Things crashed and now when i try to boot into my phone, the google logo appears and 1 seconds later crashes keeps doing it until i turn my phone off. My bootloader is locked and i think usb debuging and oem unlock are also disabled.
The same thing happens when i try to go to the recovery, it just crashes.
Any help would be greatly appreciated guys. thank you !!

Colday96 said:
Hi guys
As you probably know by reading the title, i completely messed up. I was on the stock google factory image and decided to flash a custom kernel. I enabled usb debuging and oem unlock. after having unlocked the bootloader, I installed the twrp boot img and then flashed the kernel. All was well when i stupidly decided to lock my bootloader. Things crashed and now when i try to boot into my phone, the google logo appears and 1 seconds later crashes keeps doing it until i turn my phone off. My bootloader is locked and i think usb debuging and oem unlock are also disabled.
The same thing happens when i try to go to the recovery, it just crashes.
Any help would be greatly appreciated guys. thank you !!
Click to expand...
Click to collapse
I feel bad for you. However, you bricked your Pixel.
As I mentioned yesterday, contact Google for an RMA replacement.

phaino00 said:
I feel bad for you. However, you bricked your Pixel.
As I mentioned yesterday, contact Google for an RMA replacement.
Click to expand...
Click to collapse
I bought the phone on ebay. Could i still get a RMA replacement ?

Colday96 said:
I bought the phone on ebay. Could i still get a RMA replacement ?
Click to expand...
Click to collapse
I don't believe so since you're not the original owner. However, it doesn't hurt to try.

If you bl locked the phone w modified software ur boned. I believe that RMA availability is transferrable from owner to owner, however, I also believe that they will refuse to RMA a phone which technically broke because AVB is doing its job properly. You can try but I'd say your chances are slim. Sorry mate. Also future reference: if you don't have any reason in particular to relock your phone, just don't. You'll save yourself the hassle of having to do it again and it wiping the phone everytime any software thing goes wrong or anytime u want to upgrade custom ROM or kernel or anything of the sort. This goes for any phone not just those with android verified boot.

phaino00 said:
I don't believe so since you're not the original owner. However, it doesn't hurt to try.
Click to expand...
Click to collapse
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?

Colday96 said:
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?
Click to expand...
Click to collapse
Assume they will.

Colday96 said:
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?
Click to expand...
Click to collapse
Yes they will know but they have proprietary software to forcefully unlock/reformat the phone properly if they so choose to actually accept the phone

This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400 ?

Nandolkz said:
This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400 ?
Click to expand...
Click to collapse
You can still sell it for around 150 for parts on ebay

Nandolkz said:
This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400
Click to expand...
Click to collapse
Can't you restore using the stock zips from google?

Poebat said:
Can't you restore using the stock zips from google?
Click to expand...
Click to collapse
I already tried, using both 8.1 and the first Nougat... It says oem can't unlock. I even download the skipsoft app to tryout but fail

Nandolkz said:
I already tried, using both 8.1 and the first Nougat... It says oem can't unlock. I even download the skipsoft app to tryout but fail
Click to expand...
Click to collapse
If you are flashing the latest version of Oreo you don't need to oem unlock. What version of Android were you running before you bricked it?

Poebat said:
If you are flashing the latest version of Oreo you don't need to oem unlock. What version of Android were you running before you bricked it?
Click to expand...
Click to collapse
8.0, well I already tried the dic 8.1 and it didn't work... Let me try the nov build.. or im going to try both let me see what happen.. I'll share the cmd log...

Nandolkz said:
8.0, well I already tried the dic 8.1 and it didn't work... Let me try the nov build.. or im going to try both let me see what happen.. I'll share the cmd log...
Click to expand...
Click to collapse
Okay. If that doesn't work try the 7.1.2 build with the flash-all.bat

Poebat said:
Okay. If that doesn't work try the 7.1.2 build with the flash-all.bat
Click to expand...
Click to collapse
It won't work because his bootloader is locked. I also tried the OTA file and that didn't work either. Do to have usb debugging on ?

Colday96 said:
It won't work because his bootloader is locked. I also tried the OTA file and that didn't work either. Do to have usb debugging on ?
Click to expand...
Click to collapse
He doesn't have a working OS so I doubt it

Here is what is happening to me... Any ideason how to fix it? ?

Nandolkz said:
Here is what is happening to me... Any ideason how to fix it? ?
Click to expand...
Click to collapse
Try flashing the stock rom with fastboot

Poebat said:
Try flashing the stock rom with fastboot
Click to expand...
Click to collapse
Here