5,595,428 Members 48,350 Now Online
XDA Developers Android and Mobile Development Forum

[Q] Bricked device?

Tip us?
 
Potetsjokolade
Old
(Last edited by Potetsjokolade; 11th February 2014 at 06:52 PM.)
#1  
Senior Member - OP
Thanks Meter 5
Posts: 115
Join Date: Jan 2012
Default [Q] Bricked device?

Hello, I think I've bricked my device...

I had Google Play issues, error 403, 920, 923, so I tried a fullwipe which I had used without any problems on my Desire HD. But I've encountered big issues on my Nexus 5...

It's stuck in bootloop, but I can get it to fastboot and recovery. I can't get it to mount USB-OTG (think that's wiped)

It won't show up in ADB (I am in fastboot), worked BEOFORE I flashed Custom Recovery (it broke after I installed), and did not work before I got all the errors. I can sideload CM11, but flashing wont help.

Any thoughts?

I'll try to get adb to work in fastboot, reinstalling drivers etc....

Thanks!

EDIT: Here is the zip i flashed do a full wipe. So you scriptheads know what messed things up
 
Aerowinder
Old
#2  
Recognized Contributor
Thanks Meter 1028
Posts: 2,750
Join Date: Aug 2012
Quote:
Originally Posted by Potetsjokolade View Post
Hello, I think I've bricked my device...

I had Google Play issues, error 403, 920, 923, so I tried a fullwipe which I had used without any problems on my Desire HD. But I've encountered big issues on my Nexus 5...

It's stuck in bootloop, but I can get it to fastboot and recovery. I can't get it to mount USB-OTG (think that's wiped)

It won't show up in ADB (I am in fastboot), worked BEOFORE I flashed Custom Recovery (it broke after I installed), and did not work before I got all the errors. I can sideload CM11, but flashing wont help.

Any thoughts?

I'll try to get adb to work in fastboot, reinstalling drivers etc....

Thanks!
Make sure you are using a recovery designed for the Nexus 5, and not the one you used on your old phone. Link is in my signature.

Flash factory images (return to stock). Link in signature.
 

Hammerhead Firmware: Google
USB Drivers: Google
ADB+ADB Drivers: 19.0.1 (API 19) + Koush's Universal ADB Drivers v6
Recovery: TWRP | Stock KOT49H zip
Superuser: Chainfire | Mirror
 
jd1639
Old
(Last edited by jd1639; 11th February 2014 at 07:14 PM.)
#3  
jd1639's Avatar
Recognized Contributor
Thanks Meter 2231
Posts: 7,304
Join Date: Sep 2012
Location: Minnetonka, MN
Quote:
Originally Posted by Potetsjokolade View Post
Hello, I think I've bricked my device...

I had Google Play issues, error 403, 920, 923, so I tried a fullwipe which I had used without any problems on my Desire HD. But I've encountered big issues on my Nexus 5...

It's stuck in bootloop, but I can get it to fastboot and recovery. I can't get it to mount USB-OTG (think that's wiped)

It won't show up in ADB (I am in fastboot), worked BEOFORE I flashed Custom Recovery (it broke after I installed), and did not work before I got all the errors. I can sideload CM11, but flashing wont help.

Any thoughts?

I'll try to get adb to work in fastboot, reinstalling drivers etc....

Thanks!

EDIT: Here is the zip i flashed do a full wipe. So you scriptheads know what messed things up
You wiped your os. You either need to side load a zip with adb. Or return to stock with the factory image

Edit, what did you use a script to wipe your device for? That's crazy, especially since it's not for the n5. You may be hosed because that script messes with a whole bunch of partitions which I'm sure don't align with the n5
 
Potetsjokolade
Old
#4  
Senior Member - OP
Thanks Meter 5
Posts: 115
Join Date: Jan 2012
Quote:
Originally Posted by jd1639 View Post
You wiped your os. You either need to side load a zip with adb. Or return to stock with the factory image

Edit, what did you use a script to wipe your device for? That's crazy, especially since it's not for the n5. You may be hosed because that script messes with a whole bunch of partitions which I'm sure don't align with the n5
haha, I know, I wanted to wipe the device (get it?). I was affraid I had wiped the adb drivers on my n5 (lol), I got adb in fastboot to work, and I flashed stock image. Everything works now.
 
jd1639
Old
#5  
jd1639's Avatar
Recognized Contributor
Thanks Meter 2231
Posts: 7,304
Join Date: Sep 2012
Location: Minnetonka, MN
Quote:
Originally Posted by Potetsjokolade View Post
haha, I know, I wanted to wipe the device (get it?). I was affraid I had wiped the adb drivers on my n5 (lol), I got adb in fastboot to work, and I flashed stock image. Everything works now.
Glad it's working. You dodged a bullet. I'm sure you won't do that again.
 
P.Mobile
Old
#6  
P.Mobile's Avatar
Senior Member
Thanks Meter 934
Posts: 4,332
Join Date: Nov 2011
Location: RhOdE IsLAnD... 401
that zip is not made for the N5... u cant flash wipe zips made for other phones
The Following User Says Thank You to P.Mobile For This Useful Post: [ Click to Expand ]
 
El Daddy
Old
#7  
El Daddy's Avatar
Forum Moderator
Thanks Meter 2602
Posts: 3,104
Join Date: May 2008
Location: Roseville, MN
Quote:
Originally Posted by Potetsjokolade View Post
(snip) I got adb in fastboot to work, and I flashed stock image. Everything works now.
You mean you got FASTBOOT to work in the BOOTLOADER.

Sent from my Nexus 5
 
ldubs
Old
#8  
ldubs's Avatar
Senior Member
Thanks Meter 20
Posts: 294
Join Date: Dec 2012
Location: Brooklyn, NY
BTW these Google play issues were happening all day today. It wasn't your device.

sent from my hammerhead


Insert witty, pithy, androidy statement here

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


XDA PORTAL POSTS

Add Swipe Utilities to Your App with SimpleFingerGestures Library

Gestures have become an increasingly important element in smartphone UI … more

Android App Review: Lock it Down with Lockdown Pro – XDA Developer TV

Our smartphones are our lives. They store our contacts, emails, … more

Get the AOSP Lock Screen on Your ICS-Powered Samsung Device

Android is the only popular mobile operating system that allows users, … more

Motorola Droid RAZR HD and M to Receive KitKat in a “Few More Weeks”

Verizon and Motorola shocked us all back in November when … more