Database Users

[Q] Stuck in Fastboot and not being able to connect to PC

Alright, I am having some trouble with the Nexus and hopefully someone can help me with this. Then Nexus was unlocked and rooted but I was still rocking the stock rom on there. The tablet used to be recognized by the computer and everything was fine. I used a car charger today to charge the tablet, came home, and the tablet would no longer show MTP when connected to the computer but rather would only charge.
I thought it was an issue with the rom so I downloaded a new rom, made a backup and went to flash it. Something happened when I was flashing the rom which forced the tablet to reboot and all it would get to is the Google screen. It won't go past that. I can get into the bootloader but can't boot into recovery or the system. Its not being recognized in fastboot mode either so I have no way to flash a recovery onto it...
Any suggestions?

have you tried force rebooting it a few times to try to get it ti boot up?

simms22 said:
have you tried force rebooting it a few times to try to get it ti boot up?
Click to expand...
Click to collapse
Multiple times. I have also used several different USB cables and ports on the computer. Still nothing

Any other thoughts?? I'm really in a bind

rmerchant786 said:
Any other thoughts?? I'm really in a bind
Click to expand...
Click to collapse
Can I take a look at it for you? Send me a PM and we will chat on google talk. I have some ideas though, we can connect remotely with teamviewer and I'll see if I can tell what's going on.

Any luck? I'm having the same problem.
The device is not recognized by the computer at all and the bootloader freezes then I connect it to the computer or the charger.

Engstrom said:
Any luck? I'm having the same problem.
The device is not recognized by the computer at all and the bootloader freezes then I connect it to the computer or the charger.
Click to expand...
Click to collapse
change your wire it maybe faulty or try it again on another pc

ngoralph said:
change your wire it maybe faulty or try it again on another pc
Click to expand...
Click to collapse
I've tried three usb cables on three computers (with W7, W8, Ubuntu and OS X). Makes no difference.
It does however indicate charging then it's off.

Engstrom said:
I've tried three usb cables on three computers (with W7, W8, Ubuntu and OS X). Makes no difference.
It does however indicate charging then it's off.
Click to expand...
Click to collapse
out of ideas but i used the wire given on the box and it worked but when i used different plug it didn't work

I have the same problem too after i meet flashing error in TWRP ~
I'm trying to flash Paranoid ROM update in TWRP, somehow the recovery show error when flashing so i decided to reboot system.
After that it stuck at Google logo and when I try to plug in the usb to computer, the fastboot freeze...
What to do man? Please help me

Please anyone help help ???

Are you two able to get an adb connection? If so, and you can get into fastboot, you can download and flash the Google factory ROM.
If you are not familiar with adb, try the Nexus 7 Toolkit from Skipsoft.net to flash the OEM ROM.
I'm not the lowest of the low, but I am the slowest of the slow.

I had similar issue
When I first unlocked and rooted my N7 .... and then tried to flash AOKP, I had a very similar issue as it would not boot into OS or CWM! SO i left it for some time and then crossed my fingers and tried to boot into bootloader 1 day later and then CWM ..... and it worked!
I think this is quite good advice for u to try out!
exglynco said:
Are you two able to get an adb connection? If so, and you can get into fastboot, you can download and flash the Google factory ROM.
If you are not familiar with adb, try the Nexus 7 Toolkit from Skipsoft.net to flash the OEM ROM.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse

exglynco said:
Are you two able to get an adb connection? If so, and you can get into fastboot, you can download and flash the Google factory ROM.
If you are not familiar with adb, try the Nexus 7 Toolkit from Skipsoft.net to flash the OEM ROM.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse
Thanks for the reply mate
I can get into fastboot but once I connect the usb, it freeze and the toolkit I used (GNEX TOOLKIT) couldn't get my device :crying:
And sorry to ask, what is adb connection?
I only know fastboot, now my N7 only can boot in fastboot without usb plug in :silly:
But I will try to use the toolkit you recommend me, hope it works :fingers-crossed:
Thanks a lot
---------- Post added at 12:48 AM ---------- Previous post was at 12:45 AM ----------
exglynco said:
Are you two able to get an adb connection? If so, and you can get into fastboot, you can download and flash the Google factory ROM.
If you are not familiar with adb, try the Nexus 7 Toolkit from Skipsoft.net to flash the OEM ROM.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse
wtgserpant said:
When I first unlocked and rooted my N7 .... and then tried to flash AOKP, I had a very similar issue as it would not boot into OS or CWM! SO i left it for some time and then crossed my fingers and tried to boot into bootloader 1 day later and then CWM ..... and it worked!
I think this is quite good advice for u to try out!
Click to expand...
Click to collapse
Haha...so what I have to do is wait for a few day and try again
Thanks for the advice

Google Fasfboot and ADB. Between the two of them, you can flash recovery, push & flash ROMs, etc. The Nexus 7 Toolkit makes Fasfboot & ADB commands pushbutton choices.
I'm not the lowest of the low, but I am the slowest of the slow.

Nexus 4 - bricked? - TWRP - no OS installed

Hi All,
I bought a Nexus 4 on eBay thinking I could fix it but I am really struggling.
The nexus 4 has TWRP 2.8.6.0 but that is all.
I cannot enable USB debugging as I don't have any rom installed.
I have tried a USB OTG cable with power, but have learned that the phone still cannot output the right power? The light on my usb stick comes on but TWRP does not list any USB OTG.
This phone does not have an SD card slot, so I cannot load anthing this way.
Is it impossible to get this phone working?
Kind Regards,
breaktheblock

Try fastboot from the bootloader, and reflash

ReneX10 said:
Try fastboot from the bootloader, and reflash
Click to expand...
Click to collapse
Hi ReneX10,
Thankyou for the reply, can you tell me the next step after I get to the fastboot screen?

breaktheblock said:
Hi ReneX10,
Thankyou for the reply, can you tell me the next step after I get to the fastboot screen?
Click to expand...
Click to collapse
tbh, going back to stock is a good idea and then the door is open
https://developers.google.com/android/nexus/images?hl=en
there ya go, basically follow the instructions...

ReneX10 said:
tbh, going back to stock is a good idea and then the door is open
there ya go, basically follow the instructions...
Click to expand...
Click to collapse
Will I need adb drivers to be working in windows for me to be able to do this? because so far I have been unable to successfully install any even using NRT to help.

breaktheblock said:
Will I need adb drivers to be working in windows for me to be able to do this? because so far I have been unable to successfully install any even using NRT to help.
Click to expand...
Click to collapse
Afraid I am a Linux baby, can't help you with Windows :/
fastboot etc already on there

my windows computer wont recognize the phone when I plug phone into the PC, driver installation always fails?
how can i connect a phone with just TWPR to my PC, could this be using MTP?

breaktheblock said:
my windows computer wont recognize the phone when I plug phone into the PC, driver installation always fails?
how can i connect a phone with just TWPR to my PC, could this be using MTP?
Click to expand...
Click to collapse
Have a look at this thread ..
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
(Read the thread thoroughly, and take notes, its real easy to get lost in the middle of the procedure and mess it up, and having to start again).
Flashing the stock rom is done entirely via fastboot, so you shouldnt need to worry about adb.
If you can boot into bootloader you should be able to flash stock image, once you get the windows drivers sorted. Luckily I'm on a Mac, so drivers haven't been an issue. I had a similar scenario sometime ago, and after flashing stock, all was good in the world again. I may be wrong, but you'll probably need the latest platform-tools (which contains fastboot) if you're flashing the latest stock images. (Someone correct me if I'm wrong on that one).
Sent from my LG-V500 using Tapatalk

dsbnz said:
Have a look at this thread ..
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
(Read the thread thoroughly, and take notes, its real easy to get lost in the middle of the procedure and mess it up, and having to start again).
Flashing the stock rom is done entirely via fastboot, so you shouldnt need to worry about adb.
If you can boot into bootloader you should be able to flash stock image, once you get the windows drivers sorted. Luckily I'm on a Mac, so drivers haven't been an issue. I had a similar scenario sometime ago, and after flashing stock, all was good in the world again. I may be wrong, but you'll probably need the latest platform-tools (which contains fastboot) if you're flashing the latest stock images. (Someone correct me if I'm wrong on that one).
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
This is good information, but I cannot get any further that plugging the phone into the PC, I have tried 4 different usb cables and with them all windows 7 and XP says "unknown device".
I wasn't sent the original cable from the owner which I am asking to do if they have it, but it may be a long shot for them to still have it.
Looks like I need the original usb cable?

breaktheblock said:
This is good information, but I cannot get any further that plugging the phone into the PC, I have tried 4 different usb cables and with them all windows 7 and XP says "unknown device".
I wasn't sent the original cable from the owner which I am asking to do if they have it, but it may be a long shot for them to still have it.
Looks like I need the original usb cable?
Click to expand...
Click to collapse
I don't think the cable needs to be original, I've used a Motorola cable on my N4 to flash stock, with no problems.
Is the phone in fastboot mode when you connect to pc?
Have you tried these drivers?
http://developer.android.com/sdk/win-usb.html
Sent from my LG-V500 using Tapatalk

dsbnz said:
I don't think the cable needs to be original, I've used a Motorola cable on my N4 to flash stock, with no problems.
Is the phone in fastboot mode when you connect to pc?
Have you tried these drivers?
http://developer.android.com/sdk/win-usb.html
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
For information I am using a cable from a usb cable that came from a Nexus 5.
When the phone is connected to the PC it had an android lying down with an open chest.
When pointing to the android developer sdk drivers as above it does it's usual thing of saying it is already up to date below that still saying unknown device. I'm so frustrated right now.

breaktheblock said:
For information I am using a cable from a usb cable that came from a Nexus 5.
When the phone is connected to the PC it had an android lying down with an open chest.
When pointing to the android developer sdk drivers as above it does it's usual thing of saying it is already up to date below that still saying unknown device. I'm so frustrated right now.
Click to expand...
Click to collapse
Can you reboot to the main bootloader screen?
The reason i ask is .. When you see the android lying down is there a list below showing the phone stats? If not, possibly this is why windows is reporting an unknown device.
You should try to get back into fastboot
This has the info to get to bootloader if youre not sure how..
http://www.androidcentral.com/how-unlock-nexus-4-bootloader
When you're in fastboot, try to connect to pc again.
Sent from my LG-V500 using Tapatalk

dsbnz said:
Can you reboot to the main bootloader screen?
The reason i ask is .. When you see the android lying down is there a list below showing the phone stats? If not, possibly this is why windows is reporting an unknown device.
You should try to get back into fastboot
This has the info to get to bootloader if youre not sure how..
http://www.androidcentral.com/how-unlock-nexus-4-bootloader
When you're in fastboot, try to connect to pc again.
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Underneath the android lying down it has:
FASTBOOT MODE (in red text)
PRODUCT_NAME
HW VERSION
BOOTLOADER VERSION
BASEBAND VERSION
CARRIER INFO
SERIAL NUMBER
SIGNING
SECUREBOOT (in green text - enabled)
LOCK STATE (in red text - unlocked)
Above the android lying down I can use the hardware buttons to toggle between "Start | Restart bootloader | Recovery mode | Power off"
Am I in fastboot?

breaktheblock said:
Underneath the android lying down it has:
FASTBOOT MODE (in red text)
PRODUCT_NAME
HW VERSION
BOOTLOADER VERSION
BASEBAND VERSION
CARRIER INFO
SERIAL NUMBER
SIGNING
SECUREBOOT (in green text - enabled)
LOCK STATE (in red text - unlocked)
Above the android lying down I can use the hardware buttons to toggle between "Start | Restart bootloader | Recovery mode | Power off"
Am I in fastboot?
Click to expand...
Click to collapse
Sounds like youre in the right mode. The problem would likely be on the pc/driver side.
P.S. in fastboot mode, you only need to use fastboot on pc .
Sent from my LG-V500 using Tapatalk

dsbnz said:
Sounds like youre in the right mode. The problem would likely be on the pc/driver side.
P.S. in fastboot mode, you only need to use fastboot on pc .
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
The driver issue is a massive stumbling block.
I'm still not sure if the cable will work.
I understand I can use fastboot after the PC recognises the nexus 4.
I have a Lubuntu PC this may help me but I have no idea where to start in terms of the drivers.

breaktheblock said:
The driver issue is a massive stumbling block.
I'm still not sure if the cable will work.
I understand I can use fastboot after the PC recognises the nexus 4.
I have a Lubuntu PC this may help me but I have no idea where to start in terms of the drivers.
Click to expand...
Click to collapse
I use a mac, so im no use when it comes to linux variants etc.
Depending on the power of your pc, you could try using a virtual machine (i.e. virtualbox running windows xp if you have xp disk, or even windows 7). Ive done this before on the mac (xp virtual machine) and it works. This way you can install the correct drivers on a fresh install of windows, without messing with the host OS.
Otherwise, best bet is to uninstall any drivers in your current windows, and install divers from google link i posted earlier.
Sent from my LG-V500 using Tapatalk

breaktheblock said:
The driver issue is a massive stumbling block.
I'm still not sure if the cable will work.
I understand I can use fastboot after the PC recognises the nexus 4.
I have a Lubuntu PC this may help me but I have no idea where to start in terms of the drivers.
Click to expand...
Click to collapse
just outta curiosity, when you plug the phone in (in bootloader mode) change dir to the one with fastboot.exe in and type (in command prompt):
fastboot devices
what output do you get?

ReneX10 said:
just outta curiosity, when you plug the phone in (in bootloader mode) change dir to the one with fastboot.exe in and type (in command prompt):
fastboot devices
what output do you get?
Click to expand...
Click to collapse
nothing happens at all.
I think I have something similar to this http://forum.xda-developers.com/nexus-4/help/twrp-os-installed-connect-to-pc-t2538794
as in i'm stuffed. :crying:

As in "no devices detected" ...what is the output? Pfffft I tried!

ReneX10 said:
As in "no devices detected" ...what is the output? Pfffft I tried!
Click to expand...
Click to collapse
Just to check I am doing it correctly, I launch cmd in windows, change the directory to the location where fastboot is and type "fastboot devices". The result of this is it just gives the directory name again waiting for another command.
I hope I'm not coming across as ungrateful, I assure you this is not the case.

Nexus 4 bricked, no OS, no recovery.

Hello
I tried a Nougat rom for the Nexus 4 which was available as a full update package (including system bootloader rom etc) and installed it with the update command from adb instead of from custom rom.
now my phone is bricked and I cant seem to get it fixed.
It either gets stuck in a bootloop, or i can force switch it to bootloader mode. From there I can go to recovery but the stock recovery is useless.
Problem is when i connect this to my windows 10 pc, it shows no sign of being detected. I installed drivers over and over including the universal ADB and fastboot drivers available here on XDA. it doesnt show up under adb devices command and even the Nexus 4 rootkit doesnt detect it as a phone.
I wanna make this phone working again. I'm guessing the way is to go back to stock image and then re-root and re-flash custom recovery and ROM. but even for this, it should be detected by the PC and adb command and rootkit right? Is there something I'm overlooking here?
This is the ROM I tried
https://forum.xda-developers.com/nexus-4/development/fake-nexus-rom-nexus-4-t3230268
The way to install it is also mentioned there and that is exactly what I did.

Did you try this adb installer: https://forum.xda-developers.com/showthread.php?t=2588979
In that thread, I read the people are able to use adb on Windows 10. If that doesn't work, find a Windows 7 PC or boot to ubuntu using bootable pendrive and flash the factory images using fastboot.
Nitin

nitin.chobhe said:
Did you try this adb installer: https://forum.xda-developers.com/showthread.php?t=2588979
In that thread, I read the people are able to use adb on Windows 10. If that doesn't work, find a Windows 7 PC or boot to ubuntu using bootable pendrive and flash the factory images using fastboot.
Nitin
Click to expand...
Click to collapse
So are you saying this is definitely a problem of Windows 10? I hadnt even considered that...

BluTheCool said:
So are you saying this is definitely a problem of Windows 10? I hadnt even considered that...
Click to expand...
Click to collapse
I read many users complaining about that. You can try that installer; as I mentioned - users have reported that they were able to use adb on Windows 10 after installing adb using that installer. If that doesn't work try the second suggestion (Ubuntu/ Linux)
Nitin

nitin.chobhe said:
I read many users complaining about that. You can try that installer; as I mentioned - users have reported that they were able to use abd on Windows 10 after installing adb using that installer. If that doesn't work try the second suggestion (Ubuntu/ Linux)
Nitin
Click to expand...
Click to collapse
i tried the installer but it made no difference. i tried it my win 7 partition as well but it didnt show up in the device manager.. i think usb debugging must have been disabled with my new rom flash. but even then i dont get why it wont show up as anything in devman...
any command i try ends with waiting for device and since i cant find the device in devman I cant even update the driver manually. I guess I could give linux a shot

Hey I finally figured out the problem. Its unbelievable. The usb port of the device was slightly bent in such a way that every cable I tried never really connected with the phone. I twisted it up a little and now its being detected as fastboot. The drivers you provided work like a charm now. Thanks for all the help !

BluTheCool said:
Hey I finally figured out the problem. Its unbelievable. The usb port of the device was slightly bent in such a way that every cable I tried never really connected with the phone. I twisted it up a little and now its being detected as fastboot. The drivers you provided work like a charm now. Thanks for all the help !
Click to expand...
Click to collapse
Glad that it helped, hope you get it revived soon :fingers-crossed:
Nitin

BluTheCool said:
Hey I finally figured out the problem. It's unbelievable. The USB port of the device was slightly bent in such a way that every cable I tried never really connected with the phone. I twisted it up a little and now it's being detected as fast boot. The drivers you provided work like a charm now. Thanks for all the help!
Click to expand...
Click to collapse
It seems I have the same prob, as my N4 too doesn't get detected. But my ph can charge with USB when I connect to PC.
How you twisted USB port? I mean it has very less room to insert any tool.

sandy7874 said:
It seems I have the same prob, as my N4 too doesn't get detected. But my ph can charge with USB when I connect to PC.
How you twisted USB port? I mean it has very less room to insert any tool.
Click to expand...
Click to collapse
Tell me one thing - can you boot to fastboot mode?
Nitin

nitin.chobhe said:
Tell me one thing - can you boot to fastboot mode?
Nitin
Click to expand...
Click to collapse
Yes I m able to boot to Fastboot mode.

sandy7874 said:
Yes I m able to boot to Fastboot mode.
Click to expand...
Click to collapse
Ping me on hangouts. My email ID is in my signature.
Nitin

can't connect to ADB

For some reason I cannot for the life of me connect the phone to ADB. It, ADB nor Fastboot can ever recognize that my XZP is there. I've done this many times with other phones. I'm positive I have the correct drivers. I'm on a PC with Windows 10. Any suggestions?

You should not be that positive regarding Windows 10 drivers???
Try manually delete the drivers then try again.

droidnew said:
For some reason I cannot for the life of me connect the phone to ADB. It, ADB nor Fastboot can ever recognize that my XZP is there. I've done this many times with other phones. I'm positive I have the correct drivers. I'm on a PC with Windows 10. Any suggestions?
Click to expand...
Click to collapse
I know it sounds stupid, but do you have usb debugging on in developer settings?

Beetle84 said:
I know it sounds stupid, but do you have usb debugging on in developer settings?
Click to expand...
Click to collapse
No it doesn't sound stupid. I actually forgot to do that in the past. However, this time it is on...

Beetle84 said:
I know it sounds stupid, but do you have usb debugging on in developer settings?
Click to expand...
Click to collapse
droidnew said:
No it doesn't sound stupid. I actually forgot to do that in the past. However, this time it is on...
Click to expand...
Click to collapse
I still haven't figured this out if anyone has an idea...
Would factory reseting help at all?

droidnew said:
I still haven't figured this out if anyone has an idea...
Would factory reseting help at all?
Click to expand...
Click to collapse
You can try, but I don't think a factory reset would help. I mean, fastboot should work regardless if you have the drivers installed (drivers will automatically install anyway). Does the blue led light up when you attempt to connect your phone via fastboot?

If you are trying to access ADB via Powershell in Windows 10 it doesn't work. It works with CMD prompt(Admin).
If you have tried with CMD and it didn't work, you may have to try reinstalling the drivers after booting to "Disable Signed Driver Enforcement" in Windows 10.

gowthamachandran said:
If you are trying to access ADB via Powershell in Windows 10 it doesn't work. It works with CMD prompt(Admin).
If you have tried with CMD and it didn't work, you may have to try reinstalling the drivers after booting to "Disable Signed Driver Enforcement" in Windows 10.
Click to expand...
Click to collapse
iArvee said:
You can try, but I don't think a factory reset would help. I mean, fastboot should work regardless if you have the drivers installed (drivers will automatically install anyway). Does the blue led light up when you attempt to connect your phone via fastboot?
Click to expand...
Click to collapse
The blue light does come on when I connect. I have also booted the computer and did the "Disable Signed Driver Enforcement" but I will try again...

gowthamachandran said:
If you are trying to access ADB via Powershell in Windows 10 it doesn't work. It works with CMD prompt(Admin).
If you have tried with CMD and it didn't work, you may have to try reinstalling the drivers after booting to "Disable Signed Driver Enforcement" in Windows 10.
Click to expand...
Click to collapse
I wound up doing this again, and the drivers installed. Maybe they didn't install last time, or I installed more drivers and got the right one in this time.. But, I am now able to connect to ADB and FASTBOOT. Thanks for the help guys!!

I can't unlock bootloader any one have tips to do it..
I got messages att i must install usb drive.. But i don't know how i will this.. I road in sony website but its don't resolve the problem.

Qusay86 said:
I can't unlock bootloader any one have tips to do it..
I got messages att i must install usb drive.. But i don't know how i will this.. I road in sony website but its don't resolve the problem.
Click to expand...
Click to collapse
If you are struggling to find the Google USB drivers for ADB then perhaps unlocking your bootloader is not for you.

Didgesteve said:
If you are struggling to find the Google USB drivers for ADB then perhaps unlocking your bootloader is not for you.
Click to expand...
Click to collapse
Is this the problem?

I would suggest to use a live Linux box, things will be much easier.

uzerzer said:
I would suggest to use a live Linux box, things will be much easier.
Click to expand...
Click to collapse
Absolutley, if he can't fanid any USB drivers then building a Linux box will be a doddle:laugh:

droidnew said:
I wound up doing this again, and the drivers installed. Maybe they didn't install last time, or I installed more drivers and got the right one in this time.. But, I am now able to connect to ADB and FASTBOOT. Thanks for the help guys!!
Click to expand...
Click to collapse
May i know which driver you use?

Locked in "Device State: locked"

I flashed a ROM that got my device hard bricked in the process, I had to use MsmDownloadTool to recover and I indeed successfully unbricked my device. With stock OOS I enabled oem unlock from developer settings to root again but I can't pass from that, for some reason the bootloader doesn't want to unlock even though the option is enabled. I tried the command 'fastboot oem unlock' already, the device can't make fastboot connections. Help. Please.

vulkhead said:
I flashed a ROM that got my device hard bricked in the process, I had to use MsmDownloadTool to recover and I indeed successfully unbricked my device. With stock OOS I enabled oem unlock from developer settings to root again but I can't pass from that, for some reason the bootloader doesn't want to unlock even though the option is enabled. I tried the command 'fastboot oem unlock' already, the device can't make fastboot connections. Help. Please.
Click to expand...
Click to collapse
Reboot the computer.
Reboot the phone.
Try a different cable.
Try a different port.

tech_head said:
Reboot the computer.
Reboot the phone.
Try a different cable.
Try a different port.
Click to expand...
Click to collapse
Sadly didn't make a difference

vulkhead said:
Sadly didn't make a difference
Click to expand...
Click to collapse
Try "fastboot devices" to see if the phone is seen.

tech_head said:
Try "fastboot devices" to see if the phone is seen.
Click to expand...
Click to collapse
It doesn't, nothing shows up. All drivers are installed.

vulkhead said:
It doesn't, nothing shows up. All drivers are installed.
Click to expand...
Click to collapse
Is USB debugging on?

devilrulz4ever said:
Is USB debugging on?
Click to expand...
Click to collapse
Every basic step to root a device has not been left behind.

vulkhead said:
It doesn't, nothing shows up. All drivers are installed.
Click to expand...
Click to collapse
[~]#fastboot devices
83c709f4 fastboot
If it doesn't show up, forget about what the phone is doing.
You need to figure out the driver situation on your computer.
If you can try a different computer.
Are you using Windows? What version?
I'm on a Mac and have zero issues.

yep, its your driver that is the issue; un install what ever you have installed driver wise, and start again..
oh, and your phone isn't "hard" bricked, or even "soft" bricked; bricked con notates a DOA phone, and yours is neither..
that term is abused and misused here constantly..