Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,804,353 Members 40,456 Now Online
XDA Developers Android and Mobile Development Forum

Nexus 5 won't boot, no charging icon, nothing

Tip us?
 
THE_KINGDOM
Old
(Last edited by THE_KINGDOM; 12th September 2014 at 12:40 AM.)
#1  
THE_KINGDOM's Avatar
Senior Member - OP
Thanks Meter 103
Posts: 871
Join Date: Sep 2011
Exclamation Nexus 5 won't boot, no charging icon, nothing

So I was posting about this in the Purity thread already, but this has become a major unresolvable issue so far..

I just updated clean install/flash of Purity ROM to the newest version, with the included stock kernel.
I tried out xposed framework, and only 1 mod (Serajr Blurred System UI)
on dalvik of course.. working fine for over a day.

Suddenly today, phone turned off in the gym randomly and wouldn't boot, then after 30 minutes in the gym after repeatedly trying it eventually boot, then right when I got home, I decided to un-install the mod on xposed framework, and reboot and then boom, off again not turning on for several hours... phone is not detectable by adb or fastboot. when connected to a PC, absolutely nothing, completely dead..

when connected to pc... the only thing that happens when I do vol up + vol down + power is that it cycles through usb device connecting on the PC but (device cannot start).

I've tried charging it, leaving it, I've went through every trouble shooting option that I know of.

There's not even a way I can communicate with the phone from the PC.

any suggestions, any ideas??

I can't believe that a device would be bricked from xposed module??

I could do an RMA, as the device is relatively new,
but If I return this device I'm worried about warranty void due to unlocked bootloader and custom ROM etc??
PHONE: Nexus 5 | White | 32GB
OTHER MEDIA DEVICE: Nexus Q - CM
KERNEL: ---
 
Wakamatsu
Old
#2  
Senior Member
Thanks Meter 216
Posts: 539
Join Date: Jan 2011
I'm leaning towards this being a hardware issue. If you got the phone straight from Google, the unlocked bootloader and custom whatever shouldn't be an issue.
Current phone: something with Android 4.something-something
 
joecool666
Old
(Last edited by joecool666; 12th September 2014 at 01:10 AM.)
#3  
joecool666's Avatar
Senior Member
Thanks Meter 98
Posts: 441
Join Date: Jan 2012
Location: Dublin
Quote:
Originally Posted by THE_KINGDOM View Post
So I was posting about this in the Purity thread already, but this has become a major unresolvable issue so far..

I just updated clean install/flash of Purity ROM to the newest version, with the included stock kernel.
I tried out xposed framework, and only 1 mod (Serajr Blurred System UI)
on dalvik of course.. working fine for over a day.

Suddenly today, phone turned off in the gym randomly and wouldn't boot, then after 30 minutes in the gym after repeatedly trying it eventually boot, then right when I got home, I decided to un-install the mod on xposed framework, and reboot and then boom, off again not turning on for several hours... phone is not detectable by adb or fastboot. when connected to a PC, absolutely nothing, completely dead..

when connected to pc... the only thing that happens when I do vol up + vol down + power is that it cycles through usb device connecting on the PC but (device cannot start).

I've tried charging it, leaving it, I've went through every trouble shooting option that I know of.

There's not even a way I can communicate with the phone from the PC.

any suggestions, any ideas??

I can't believe that a device would be bricked from xposed module??

I could do an RMA, as the device is relatively new,
but If I return this device I'm worried about warranty void due to unlocked bootloader and custom ROM etc??
you could try nexus root toolkit, also you could try with power off hold vol-up insert USB it should install lg flash tool driver's.some time's it take's it time installing driver's so just give it a min or two regard's joe
 
THE_KINGDOM
Old
#4  
THE_KINGDOM's Avatar
Senior Member - OP
Thanks Meter 103
Posts: 871
Join Date: Sep 2011
Quote:
Originally Posted by Wakamatsu View Post
I'm leaning towards this being a hardware issue. If you got the phone straight from Google, the unlocked bootloader and custom whatever shouldn't be an issue.
ok as long as it shouldn't be a problem I'm prob going to do an RMA.

Quote:
Originally Posted by joecool666 View Post
you could try nexus root toolkit, also you could try with power off hold vol-up insert USB it should install lg flash tool driver's.some time's it take's it time installing driver's so just give it a min or two regard's joe
Ok I'm going to try holding vol-up and insert USB, but i assume for nexus root toolkit to work it phone would need to be visible as a "fastboot" device bare minimum, which I'm having problems even getting that right now.
PHONE: Nexus 5 | White | 32GB
OTHER MEDIA DEVICE: Nexus Q - CM
KERNEL: ---
 
joecool666
Old
#5  
joecool666's Avatar
Senior Member
Thanks Meter 98
Posts: 441
Join Date: Jan 2012
Location: Dublin
Quote:
Originally Posted by THE_KINGDOM View Post
ok as long as it shouldn't be a problem I'm prob going to do an RMA.



Ok I'm going to try holding vol-up and insert USB, but i assume for nexus root toolkit to work it phone would need to be visible as a "fastboot" device bare minimum, which I'm having problems even getting that right now.
hi, nexus toolkit has an op for soft-bricked/bootloop. it might detect your device.

---------- Post added at 01:38 AM ---------- Previous post was at 01:22 AM ----------

Quote:
Originally Posted by THE_KINGDOM View Post
ok as long as it shouldn't be a problem I'm prob going to do an RMA.



Ok I'm going to try holding vol-up and insert USB, but i assume for nexus root toolkit to work it phone would need to be visible as a "fastboot" device bare minimum, which I'm having problems even getting that right now.
how's it going any news?
 
THE_KINGDOM
Old
#6  
THE_KINGDOM's Avatar
Senior Member - OP
Thanks Meter 103
Posts: 871
Join Date: Sep 2011
Quote:
Originally Posted by joecool666 View Post
hi, nexus toolkit has an op for soft-bricked/bootloop. it might detect your device.

---------- Post added at 01:38 AM ---------- Previous post was at 01:22 AM ----------



how's it going any news?
vol-up and power while connecting usb didn't do anything so far. I'm going to try nexus toolkit just for the hell of it, but I think this device is literally bricked beyond repair.
PHONE: Nexus 5 | White | 32GB
OTHER MEDIA DEVICE: Nexus Q - CM
KERNEL: ---
 
joecool666
Old
#7  
joecool666's Avatar
Senior Member
Thanks Meter 98
Posts: 441
Join Date: Jan 2012
Location: Dublin
Quote:
Originally Posted by THE_KINGDOM View Post
vol-up and power while connecting usb didn't do anything so far. I'm going to try nexus toolkit just for the hell of it, but I think this device is literally bricked beyond repair.
yeah sound's like it could be hard bricked, hope toolkit work's for you tho.
 
THE_KINGDOM
Old
#8  
THE_KINGDOM's Avatar
Senior Member - OP
Thanks Meter 103
Posts: 871
Join Date: Sep 2011
just doesn't make any sense of why it would be hard-bricked.. randomly just turns off.. so weird
PHONE: Nexus 5 | White | 32GB
OTHER MEDIA DEVICE: Nexus Q - CM
KERNEL: ---
 
joecool666
Old
#9  
joecool666's Avatar
Senior Member
Thanks Meter 98
Posts: 441
Join Date: Jan 2012
Location: Dublin
Quote:
Originally Posted by THE_KINGDOM View Post
just doesn't make any sense of why it would be hard-bricked.. randomly just turns off.. so weird
strange that, not getting detected by p.c, yeah look's like a trip to the service station.sorry i coulden't be of more help. hope you get it back to life.kind regard's joe
The Following User Says Thank You to joecool666 For This Useful Post: [ Click to Expand ]
 
rootSU
Old
#10  
rootSU's Avatar
Senior Member
Thanks Meter 11,277
Posts: 22,338
Join Date: Aug 2010
Location: Oxenhope, West Yorkshire, UK
Quote:
Originally Posted by THE_KINGDOM View Post
just doesn't make any sense of why it would be hard-bricked.. randomly just turns off.. so weird
All bricks are hard bricks. As much as people use the term "soft bricked", believe me - it isn't a thing. A brick is irreparable. If it was repairable, it isn't a brick.

If it is irreparable, its because its been affected beyond the software layer. Messing up the NAND partitions or NAND death are the most common. This can happen during a flash or even seemingly random - its not unusual for bricks to be random. Flash memory in my opinion, is still pretty unstable. Send it for repair /RMA.

Sent from my Nexus 5 using Tapatalk
Want to root/unroot? All important guides and info threads are contained within the "Sticky Roll-up" thread in General. Click the link below to get there!

**Sticky Roll-up: All Guides snd Info Threads linked here**



Philz Touch Recovery with passkey secure lock

I do NOT reply to support queries over PM.

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes