Nexus 5 probably briked (adb/fastboot not work) - Nexus 5 Q&A, Help & Troubleshooting

I have problem starting my nexus 5 (Stock, android 6.0)
Boot stopping on Google logo. However adb unavailable (adb devices shows nothing, but USB debugging enabled in Dev settings)
Ok, when I go to fastboot menu fastboot devices shows nothing too
hxxp://i.imgur.com/gH9G7SS.jpg
I tried this under Windows 8.1 and Xubuntu
On Windows phone displayed as "Unknown USB device", but Windows decline offer to update driver for this device (aka "My system driver up to date")
I also tried to wipe data through recovery, but it returned error - couldn't mount /cache, /data and /system
Please help.

Have you tried under Windows 7? I don't know or use Linux and I also have problems with Windows 8 so I downgraded my machine to Windows 7 and stays on 7.

uninstall and reinstall the drivers in Windows.

Use Wugfresh's Nexus Root Toolkit button "Install & test drivers" - it guides you through the setup of your Windows drivers. I also had problems with Windows 8, though I think that 8.1 was ok, and on Windows 10 I have no driver problems.

blanco2701 said:
uninstall and reinstall the drivers in Windows.
Click to expand...
Click to collapse
ok, HOW?

audit13 said:
Have you tried under Windows 7? I don't know or use Linux and I also have problems with Windows 8 so I downgraded my machine to Windows 7 and stays on 7.
Click to expand...
Click to collapse
On Windows 7 the same behaviour

Not sure what to suggest but you need to get it recognized so you can unlock the bootloader and flash a stock ROM.

io_zhik said:
ok, HOW?
Click to expand...
Click to collapse
Start the device in bootloader mode... Look for DEVICE MANAGER in Windows, connect the phone and look for it on the list. Right click and UNINSTALL (probably Unknown USB device).
Disconnect the phone and reconnect it, it should install by itself and start working. If it works you might have to do the same while the phone is in bootloader mode.
If this doesn't work, try installing Wugfresh's nexus root toolkit, it guides you through everything, including installing/updating windows drivers. A lot of experienced users don't like the toolkit since you don't actually learn much by using it. The way I see it is as a tool (as it's name says) that does all the work for you while you sit back and relax, and so far it has worked well most of the time, specially when doing what you want to do, do a fresh install of Android.

You could also try updating the Windows drivers using the drivers from here: http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339

"If this doesn't work, try installing Wugfresh's nexus root toolkit"
Is there an echo in here...?
Does anyone actually bother to read previous posts? There were only 7...

dahawthorne said:
"If this doesn't work, try installing Wugfresh's nexus root toolkit"
Is there an echo in here...?
Does anyone actually bother to read previous posts? There were only 7...
Click to expand...
Click to collapse
Is there a problem with agreeing with you?

Not if you have the courtesy to add "as suggested earlier by..."

dahawthorne said:
Not if you have the courtesy to add "as suggested earlier by..."
Click to expand...
Click to collapse
I didn't know you where the first one to ever suggest the toolkit. By your logic, you too should have quoted whoever suggested the app before you, even if it was in another forum.
Anyways, since you actually took your time to complain about it, and to make you feel better, I'll say sorry. wtf lol
---------- Post added at 10:27 AM ---------- Previous post was at 10:26 AM ----------
io_zhik said:
ok, HOW?
Click to expand...
Click to collapse
Back to the topic, did you find your solution?

Related

Help Rooting [Desperate]

Hey guys, I'm a total noob (please don't hate). I've tried rooting my Nexus S running 4.1 for a long time now, but I just can't
seem to figure it out. I was wondering if someone could walk me though it step by step via some sort of
communication like MSN Messenger. I don't know whether I'm messing up the drivers or what it is, but my
I can't ever unlock my bootloader.
Thanks ahead of time.
Nexus S 4 life but you joined this month hmm lol
Which part are you stuck at?
I tried before I joined. I can't seem to make it say ULOCKED in the bootloader, but I think I'm screwing up the whole thing. Could you please guide me through it? You don't know how happy I'd be.
Sent from my Nexus S using xda app-developers app
NexusS4Life said:
I tried before I joined. I can't seem to make it say ULOCKED in the bootloader, but I think I'm screwing up the whole thing. Could you please guide me through it? You don't know how happy I'd be.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Do you mean you can't get the Yes/No dialog to show up? Looks like driver problems. Make sure you installed all of the Nexus S drivers needed. While you're in bootloader you should see Android 1.0 under Device Manager on your computer. Installing pdanet usually fixes this..Good luck
i tried pdanet but it comes up with this error message that keeps getting stuck between 2 windows
NexusS4Life said:
i tried pdanet but it comes up with this error message that keeps getting stuck between 2 windows
Click to expand...
Click to collapse
Not sure what you mean by that...but it looks like you lack fastboot drivers. Refer to this thread http://forum.xda-developers.com/showthread.php?t=878786 and let me know how it turns out.
qccoles said:
Not sure what you mean by that...but it looks like you lack fastboot drivers. Refer to this thread http://forum.xda-developers.com/showthread.php?t=878786 and let me know how it turns out.
Click to expand...
Click to collapse
Dont understand what any of this means
How to install ADB and Fastboot:
1. download and place in the root of your C:\ drive
2. extract here (not into a sub folder)
3. now open up control panel
4. find system
5. goto advanced settings
6. goto environmental variables
7. in the box that says "system variables" scroll down to find a variable "Path"
8. highlight it
9. click edit
10. add this to the end
Quote:
;C:\android\tools
yes the ; is needed
11. click ok
i think i know why PDAnet wont work for me...i have windows 8 not 7
NexusS4Life said:
i think i know why PDAnet wont work for me...i have windows 8 not 7
Click to expand...
Click to collapse
Hey NexusS4Life, if you still haven't rooted, I'd be glad to help you. I'm no expert, but I'm pretty familiar with the whole process now, seeings as how I've rooted a Nexus One and Nexus S.
Private message me, as soon as I see it we could set up a time to chat on MSN or whatever so this goes quicker.
Well, I was helping him in PM but he hasn't said anything else so A. He's rooted and having the post-root jitters, B. Pissed and sleep
qccoles said:
Well, I was helping him in PM but he hasn't said anything else so A. He's rooted and having the post-root jitters, B. Pissed and sleep
Click to expand...
Click to collapse
I just need the fastboot drivers...if someone could help me with that...i have windows 8 so pdanet doesnt work
Can anyone help me now? Ill be on at 12pm central time if anyone wants to help me out tonight. You can post on here
so i can private message you when im online. Thank you.
maybe this will help: http://forum.xda-developers.com/showthread.php?t=1583801

Bricked my device

Hey guys, I have a problem with my Nexus 5, it's that I cannot boot ANY Android (No android at all, just shows Google logo)
I can get into Recovery mode, but the phone is EMPTY (no rom on it).
Adb (How to push files using ADB without Android SDK The Easy Way - Team Nocturnal <-- go to youtube and paste that, i followed that tutorial) doesn't work unfortunately.
Any suggestions guys ?
Just wrote a thread about adb. Click link in signature then look for section 1
Sent from my Nexus 5 using Tapatalk
spluxor said:
Hey guys, I have a problem with my Nexus 5, it's that I cannot boot ANY Android (No android at all, just shows Google logo)
I can get into Recovery mode, but the phone is EMPTY (no rom on it).
Adb (How to push files using ADB without Android SDK The Easy Way - Team Nocturnal <-- go to youtube and paste that, i followed that tutorial) doesn't work unfortunately.
Any suggestions guys ?
Click to expand...
Click to collapse
Google 15 second adb drivers xda. It's probably in rootSu's guide. That'll set up the adb you need
Sent from my Nexus 5 using XDA Free mobile app
It is indeed
Sent from my Nexus 5 using Tapatalk
I unfortunately cannot pass the 'unwanted things' in How to test adb and fastboot work, since I cannot install the driver.
It shows like AOSP on HammerHead and I cannot install a single driver.
Thanks!
spluxor said:
I unfortunately cannot pass the 'unwanted things' in How to test adb and fastboot work, since I cannot install the driver.
It shows like AOSP on HammerHead and I cannot install a single driver.
Thanks!
Click to expand...
Click to collapse
You need these drivers http://forum.xda-developers.com/showthread.php?t=2386956
If you are using windows 8 or 8.1 then you have to turn off driver signature enforcement
bitdomo said:
You need these drivers http://forum.xda-developers.com/showthread.php?t=2386956
If you are using windows 8 or 8.1 then you have to turn off driver signature enforcement
Click to expand...
Click to collapse
That was already told in my thread.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 06:56 AM ---------- Previous post was at 06:55 AM ----------
spluxor said:
I unfortunately cannot pass the 'unwanted things' in How to test adb and fastboot work, since I cannot install the driver.
It shows like AOSP on HammerHead and I cannot install a single driver.
Thanks!
Click to expand...
Click to collapse
Well, you need to fix that.
If you want help please explain in detail your issue
Sent from my Nexus 5 using Tapatalk
Well the good thing is that I unbricked it, by following How to Unbrick or Unroot the Nexus 5 (incl. Tamper Flag Reset) on YouTube by C4ETech, the bad thing is that I have to install everything again, but okay my fault
Anyways guys thanks for help !
If you can see the Google logo when you turn on your device and can go into recovery, it's not bricked. Bricked means it will not turn on at all. It's essentially just a "brick" with no possible way to recover.
vanessaem said:
If you can see the Google logo when you turn on your device and can go into recovery, it's not bricked. Bricked means it will not turn on at all. It's essentially just a "brick" with no possible way to recover.
Click to expand...
Click to collapse
Completely agree. And by this rule, there is not really such a thing as a software brick either.
That said, I do sometimes use the term "Radio Brick" when a Rdio flash has gone wrong and it cannot be fixed without being sent to the Vendor. Can't think of a better term.
rootSU said:
Completely agree. And by this rule, there is not really such a thing as a software brick either.
That said, I do sometimes use the term "Radio Brick" when a Rdio flash has gone wrong and it cannot be fixed without being sent to the Vendor. Can't think of a better term.
Click to expand...
Click to collapse
By that term, anything nonrecoverable can be considered a brick which is still more accurate than a device being bricked or software bricking a device yet it can still be turned on and/or charged.
Anyway, I say all that to say to the OP and all who think they are bricked, all is not lost if your device functions at all.

[Q] OPO Root problem. Device not found

Hello everyone,
I've been a member since the I had my Sony Xperia X10 and Samsung Galaxy S3 and both phones were rooted using xda forums. I greatly appreciate this community and should contribute more but I'm not that advanced as most users here. I do have a little some experience tinkering around with the computer but I'm mainly a hardware type of guy and know only a little on software.
But here is my problem. I tried a few methods of trying to root my One Plus One and had little success. I came to a conclusion that it's a driver issue. When i use the command adb devices, it wouldnt show any devices. When I look in the device manager with my OPO plugged in, the drivers are missing. I tried to manually download android sdk and install from there but still no luck. I tried using the GUI toolboxes which has the adb and drivers to install. But still came out with no luck.
Can anyone assist me with my situation? When I turn on Developer Options and checked Android Debugging and USB Debugging Notify, I would not get the message to confirm and give access to the computer. I can open all folders in Windows 7 of my OPO and I use the original data cable supplied with my phone.
Thanks in advance!
Try manually installing the correct driver in device manager. Chances are that Windows is picking a matching but incompatible driver from your old device or tries to be smart.
d4fseeker said:
Try manually installing the correct driver in device manager. Chances are that Windows is picking a matching but incompatible driver from your old device or tries to be smart.
Click to expand...
Click to collapse
Sorry for the noob question, but where would I find the drivers?
archanphel said:
Sorry for the noob question, but where would I find the drivers?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2386956
I know OPO isn't listed but the driver works for OPO.
is that for windows 8.1? I'm running windows 7
archanphel said:
is that for windows 8.1? I'm running windows 7
Click to expand...
Click to collapse
Works on Windows 7 as well, thats why its called "Universal"
and read more carefully the thread says,
2 & 64 Bit Windows 8 / 7 / Vista / XP - Attached to this post!
MD5: 5B9EA9C73066E8F655D14BBA8318C176
Click to expand...
Click to collapse
zephiK said:
Works on Windows 7 as well, thats why its called "Universal"
and read more carefully the thread says,
Click to expand...
Click to collapse
Yup, sorry about that. I figured it out by the step by step tutorial. Thanks
I have successfully rooted my phone. Thanks again for all the help!

[Q] MTP, File transfer issues.

Hi guys,
Well ive searched and ive searched... It seems many people have this issue after flashing and many people have solved it by many different methods, none work for me
When i plug my phone into my PC running windows 7,
The phone is recognized under Other Devices named "MTP" but no drivers seem to be able to let me access the files.
Any suggestions ill try ANYTHING!
Thanks in advance.
craig14 said:
Hi guys,
Well ive searched and ive searched... It seems many people have this issue after flashing and many people have solved it by many different methods, none work for me
When i plug my phone into my PC running windows 7,
The phone is recognized under Other Devices named "MTP" but no drivers seem to be able to let me access the files.
Any suggestions ill try ANYTHING!
Thanks in advance.
Click to expand...
Click to collapse
Start > Search > Device Manager (or devmgmt.msc). Right click the Nexus 5 and uninstall driver, then unplug and replug it in.
Tried this but no luck!
Any ideas?
Lethargy said:
Start > Search > Device Manager (or devmgmt.msc). Right click the Nexus 5 and uninstall driver, then unplug and replug it in.
Click to expand...
Click to collapse
It installs drivers but just goes back to the same state.
craig14 said:
It installs drivers but just goes back to the same state.
Click to expand...
Click to collapse
Try these;
From **Sticky Roll-Up: All Guides and Info Threads Linked Here**:
rootSU said:
ADB, Fastboot and Drivers - 15 seconds ADB Installer - Really quick and easy way to install adb and fastboot (by @Snoop05) - INSTALL THIS BEFORE ROOT
[ADB/FB/APX Driver] Universal Naked Driver - A "bare" driver required for connecting your device(by @1wayjonny) - INSTALL THIS BEFORE ROOT if above fails
Diagnosing USB Driver and ADB issues in Windows - Ensure ADB and fastboot WORK before you root (by @MaxRabbit ) - READ FOR INFORMATION, DO NOT FOLLOW unless both above fail
Click to expand...
Click to collapse
Lethargy said:
Try these;
From **Sticky Roll-Up: All Guides and Info Threads Linked Here**:
[/LIST]
Click to expand...
Click to collapse
no luck
craig14 said:
Hi guys,
Well ive searched and ive searched... It seems many people have this issue after flashing and many people have solved it by many different methods, none work for me
When i plug my phone into my PC running windows 7,
The phone is recognized under Other Devices named "MTP" but no drivers seem to be able to let me access the files.
Any suggestions ill try ANYTHING!
Thanks in advance.
Click to expand...
Click to collapse
Same for me, can't transfer any files via PC, I use Airdroid. Phone doesn't show up in device manager regardless of what I try -- also this is my 3rd Nexus and the second one to do this.
craig14 said:
Hi guys,
Well ive searched and ive searched... It seems many people have this issue after flashing and many people have solved it by many different methods, none work for me
When i plug my phone into my PC running windows 7,
The phone is recognized under Other Devices named "MTP" but no drivers seem to be able to let me access the files.
Any suggestions ill try ANYTHING!
Thanks in advance.
Click to expand...
Click to collapse
Have you ever installed the ADB drivers? Sometimes they conflict if you install those first. What I mean is that if you use fastboot on your phone before using MTP, this can happen.
Aerowinder said:
Have you ever installed the ADB drivers? Sometimes they conflict if you install those first. What I mean is that if you use fastboot on your phone before using MTP, this can happen.
Click to expand...
Click to collapse
That'll be my problem then! :good:
---------- Post added at 08:47 PM ---------- Previous post was at 08:31 PM ----------
THIS fixed my device issues, for some random reason my Nexus was showing up as an ACER ADB Interface.
Aerowinder said:
Have you ever installed the ADB drivers? Sometimes they conflict if you install those first. What I mean is that if you use fastboot on your phone before using MTP, this can happen.
Click to expand...
Click to collapse
hmmmm, ive only ever installed the ADB drivers whilst trying to solve this issue but have completely unistalled and used naked drivers still to no avail
If anyone knows a fix for this id be forever in your debt!!
craig14 said:
hmmmm, ive only ever installed the ADB drivers whilst trying to solve this issue but have completely unistalled and used naked drivers still to no avail
If anyone knows a fix for this id be forever in your debt!!
Click to expand...
Click to collapse
radicalisto said:
That'll be my problem then! :good:
---------- Post added at 08:47 PM ---------- Previous post was at 08:31 PM ----------
THIS fixed my device issues, for some random reason my Nexus was showing up as an ACER ADB Interface.
Click to expand...
Click to collapse
I posted the fix in my post above yours... I've quoted it for you.
You truly are my hero!!
Thank you so much, i have no idea why i couldnt find the answer anywhere whenit was so simple...
Thanks again dude

Unable to unlock bootloader

As the title says, i cant manage to unlock the bootloader. My device is GM1910, i am running 9.5.10 GM21AA. i went to OB2 but then rolled back and decided i wanted to unlock and root, but for some reason i cannot. followed all the proper guides, tried the adb method, but when i type fastboot oem unlock, it just says waiting for device. I also tried the all-in-one tool and same problem, the moment i check for bootloader status, the application hangs. has anyone faced this issue before? could use some help. Thanks
Using the OP cable and tried on both USB 3 and 2
linx1287 said:
As the title says, i cant manage to unlock the bootloader. My device is GM1910, i am running 9.5.10 GM21AA. i went to OB2 but then rolled back and decided i wanted to unlock and root, but for some reason i cannot. followed all the proper guides, tried the adb method, but when i type fastboot oem unlock, it just says waiting for device. I also tried the all-in-one tool and same problem, the moment i check for bootloader status, the application hangs. has anyone faced this issue before? could use some help. Thanks
Using the OP cable and tried on both USB 3 and 2
Click to expand...
Click to collapse
If your on sprint you cant unless you pay off the phone or have it active for 50days. Not sure about t-mobile. heres a helpful link tho.
https://forum.xda-developers.com/oneplus-7-pro/how-to/discussion-sprint-oneplus-7-pro-5g-t3963319
lonewolf2k2 said:
If your on sprint you cant unless you pay off the phone or have it active for 50days. Not sure about t-mobile. heres a helpful link tho.
https://forum.xda-developers.com/oneplus-7-pro/how-to/discussion-sprint-oneplus-7-pro-5g-t3963319
Click to expand...
Click to collapse
Sorry but mine isnt any carrier phone GM1910 is the chinese international running GM21AA
Sounds more like a USB connectivity issue, than a problem with the device. Try the command: fastboot devices
And if it just hangs, then you don't have USB fastboot connectivity.
To be clear, the phone is booted to bootloader-fastboot mode (which is required for fastboot commands)?
You need the latest windows 10 drivers, adb & fastboot. And off course Open Beta it's still young... meanning sh.. could happen.
redpoint73 said:
Sounds more like a USB connectivity issue, than a problem with the device. Try the command: fastboot devices
And if it just hangs, then you don't have USB fastboot connectivity.
To be clear, the phone is booted to bootloader-fastboot mode (which is required for fastboot commands)?
Click to expand...
Click to collapse
null0seven said:
You need the latest windows 10 drivers, adb & fastboot. And off course Open Beta it's still young... meanning sh.. could happen.
Click to expand...
Click to collapse
Yes adb devices does register and adb reboot bootloader command does take me to the bootloader, but when i tried the fastboot devices it didnt register, so i think you are on to something. I will check again once i get home today. Thanks
I was on open beta, i reverted to 9.5.10 Pie in order to unlock bootloader and root.
If its not too much trouble, could you link me to the drivers (i would ask adb too but seeing as it works when i do adb devices command, i think thats working fine)? Thanks
Platform tool 2.9.0.4 (adb-fastboot), latest
https://android.gadgethacks.com/how...stall-adb-fastboot-mac-linux-windows-0164225/
null0seven said:
Platform tool 2.9.0.4 (adb-fastboot), latest
https://android.gadgethacks.com/how...stall-adb-fastboot-mac-linux-windows-0164225/
Click to expand...
Click to collapse
Thanks. This was the version i was working with yesterday. Could you link me to the usb drivers i might need? Since response stops at fastboot i am assuming the drivers are to blame
One thing you can try, on Windows go to Device Manager, find the phone, and pick the option to update the drivers. Select the drivers manually (don't let Windows find the drivers automatically). Then the one called Generic Android Device (or something like that).
I sometimes have to do this, to get Windows to work with adb/fastboot.
This is all on my old Windows 7 machine. So if you have Win 10, it might be a bit different.
redpoint73 said:
One thing you can try, on Windows go to Device Manager, find the phone, and pick the option to update the drivers. Select the drivers manually (don't let Windows find the drivers automatically). Then the one called Generic Android Device (or something like that).
I sometimes have to do this, to get Windows to work with adb/fastboot.
This is all on my old Windows 7 machine. So if you have Win 10, it might be a bit different.
Click to expand...
Click to collapse
Thank you. You were right about the driver issue....going through the device manager yielded the driver situation. Had to enable debugging to finally let the driver install. I completely forgot about this. I had to do this same thing when i had to unlock bootloader and twrp for my HTC 10.
Now that i am done with this, a few final things i would like to clear out....doing the local update on root to restore stock system is still valid right? and if i want to go full stock from say custom roms like los and so on, a flash through MSM tool? Will doing that also relock the bootloader? Sorry for all the noob questions and thanks in advance.
Local upgrade works with/without root or twrp.
MSM tool revert youre phone like it's out of the factory. Bootloader locked, no root, no twrp.
If you come back to Oos from custom roms you need to Format Data (this will wipe ALL in youre phone. everything).

Categories

Resources