Database Users

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.

Soft brick, no fastboot or adb in bootloader mode. $25 bounty

The phone is in bootloop. I believe that the partition for system and other things were formatted. I can access the bootloader, however when I plug into PC it is not detected. (I have reinstalled drivers to make sure there is no issue) My PC recognizes my nexus 5x just fine. I can boot into recovery as well but pc does not detect the device even when I go to ADB side load. If the phone is off and I plug into the PC phone shows charging but nothing happens on the PC. Any ideas or help would be appreciated. $25 bounty the person with the magic answer.

What does the CMD output when you type in "fastboot devices", while your device is connected in bootloader mode?
P.S. You might want to remove the bounty. There is no need for that. People here can and will help you for free. :good:

DJBhardwaj said:
What does the CMD output when you type in "fastboot devices", while your device is connected in bootloader mode?
P.S. You might want to remove the bounty. There is no need for that. People here can and will help you for free. :good:
Click to expand...
Click to collapse
It looks for the devices, then a blank space then back to the cmd prompt.

ppbatman said:
It looks for the devices, then a blank space then back to the cmd prompt.
Click to expand...
Click to collapse
Just to confirm, while you do this, your device is in bootloader mode?
Also, have you tried it on another PC?

DJBhardwaj said:
Just to confirm, while you do this, your device is in bootloader mode?
Also, have you tried it on another PC?
Click to expand...
Click to collapse
Yes sit, in bootloader mode. Have tried 3 PC's all the usb ports and 2 usb cables. Im stumped.

ppbatman said:
Yes sit, in bootloader mode. Have tried 3 PC's all the usb ports and 2 usb cables. Im stumped.
Click to expand...
Click to collapse
While your device is connected, do you see anything unusual in Control Panel > Device Manager?
---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------
ppbatman said:
Yes sit, in bootloader mode. Have tried 3 PC's all the usb ports and 2 usb cables. Im stumped.
Click to expand...
Click to collapse
Also, have you tried a factory reset from within the stock recovery?

DJBhardwaj said:
While your device is connected, do you see anything unusual in Control Panel > Device Manager?
---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------
Also, have you tried a factory reset from within the stock recovery?
Click to expand...
Click to collapse
I can't see anything come up in device manger at all. There is no stock recovery it has cyanogen recovery, I did factory reset from this recovery multiple times to no avail. I

ppbatman said:
I can't see anything come up in device manger at all. There is no stock recovery it has cyanogen recovery, I did factory reset from this recovery multiple times to no avail. I
Click to expand...
Click to collapse
That drives me clueless too. It most probably seems like a driver issue. You might want to dig in more?

DJBhardwaj said:
That drives me clueless too. It most probably seems like a driver issue. You might want to dig in more?
Click to expand...
Click to collapse
I appreciate the help. I have tried multiple different drivers with multiple tools. I might try it on a mac to see if I can get it to recognize the phone. Could it be something where the phone was not put into debug mode and not stuck that way?

ppbatman said:
I appreciate the help. I have tried multiple different drivers with multiple tools. I might try it on a mac to see if I can get it to recognize the phone. Could it be something where the phone was not put into debug mode and not stuck that way?
Click to expand...
Click to collapse
Also, I have access to an Octobox through a friend of mine. I wouldn't know where to begin but, I know these are used in some cases to recovery phones.

I suggest you to try with a Linux or Mac machine, as drivers are not required in such cases.
Are you sure you don't have a defective cable?

Cero92 said:
I suggest you to try with a Linux or Mac machine, as drivers are not required in such cases.
Are you sure you don't have a defective cable?
Click to expand...
Click to collapse
I agree.
Sounds like a defective cable.
I have a Mac so I never worry about drivers and such.

Can you remove all drivers and what not that you've installed, all tools and everything, reboot your PC.
Install this: http://forum.xda-developers.com/showthread.php?p=48915118
Say YES to all options, install the drivers it asks you too.
Reboot your PC again.
Plug device in, while in bootloader mode, try "fastboot devices" again. If nothing happens, reboot-bootloader again from the phone, while keeping the device plugged in.

ppbatman said:
Also, I have access to an Octobox through a friend of mine. I wouldn't know where to begin but, I know these are used in some cases to recovery phones.
Click to expand...
Click to collapse
I would say, first check on a Mac or other Windows machines. See if Device Manager shows anything?

Wiltron said:
Can you remove all drivers and what not that you've installed, all tools and everything, reboot your PC.
Install this: http://forum.xda-developers.com/showthread.php?p=48915118
Say YES to all options, install the drivers it asks you too.
Reboot your PC again.
Plug device in, while in bootloader mode, try "fastboot devices" again. If nothing happens, reboot-bootloader again from the phone, while keeping the device plugged in.
Click to expand...
Click to collapse
I will definitely try this tonight when I get home from work. Thanks very much for the suggestion.

tech_head said:
I agree.
Sounds like a defective cable.
I have a Mac so I never worry about drivers and such.
Click to expand...
Click to collapse
I don't think the cable is defective, I've tried 3 cables not so far and they all work with other devices.

ppbatman said:
I will definitely try this tonight when I get home from work. Thanks very much for the suggestion.
Click to expand...
Click to collapse
If it does work, I don't want the $25.
I want you to donate the $25 to @BeansTown106 - preferably under my name, but that last bit isn't required
For those who are unaware, Beans is the developer of PureNexus ROMs.

Wiltron said:
If it does work, I don't want the $25.
I want you to donate the $25 to @BeansTown106 - preferably under my name, but that last bit isn't required
For those who are unaware, Beans is the developer of PureNexus ROMs.
Click to expand...
Click to collapse
No problem at all, it will be the best $25 I even spent. Not having this phone work is major butt hurt

tech_head said:
I agree.
Sounds like a defective cable.
I have a Mac so I never worry about drivers and such.
Click to expand...
Click to collapse
Plugged it in to the mac and still nothing. Mac has fastboot and adb installed, confirmed it working with nexus 5x. Im at a loss here.

ppbatman said:
Plugged it in to the mac and still nothing. Mac has fastboot and adb installed, confirmed it working with nexus 5x. Im at a loss here.
Click to expand...
Click to collapse
You might wanna take it to the service center. Of course, tell them that it just didn't reboot after an OTA installation.

Bricked moto x pure that wont connect to computer through usb

Please help! I am somewhat a noob and I have a bricked Moto X pure. My phone bricked when i was installing supersu from the twrp. Now it can get into bootloader but all the data on my phone is deleted including twrp. For me this would be an easy fix but of course, my phone does not sense the usb cord. I have tried a couple usb cords to connect to my pc but none of them will work. Am i stuck into a paradox if i dont find a way to get my usb cord to work? Pleaser Help!!!

enochthegreat said:
Please help! I am somewhat a noob and I have a bricked Moto X pure. My phone bricked when i was installing supersu from the twrp. Now it can get into bootloader but all the data on my phone is deleted including twrp. For me this would be an easy fix but of course, my phone does not sense the usb cord. I have tried a couple usb cords to connect to my pc but none of them will work. Am i stuck into a paradox if i dont find a way to get my usb cord to work? Pleaser Help!!!
Click to expand...
Click to collapse
Honestly, if your phone can't talk to your computer with fastboot in the bootloader, your pretty much screwed.
How did you root? What specific version and steps did you take?

I used the hiensberg guide https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
What do you think is the best option from here?

Are you trying to get into fastboot with it connected to computer?

Iceburn1 said:
Are you trying to get into fastboot with it connected to computer?
Click to expand...
Click to collapse
No im already in fastboot mode. Im just trying to restore my devioe so that it works. When i power on my phone it displays the unlocked bootloader warning then goes into fastboot mode. The screen reads-
"Start up failed: Your device didnt start up succesfully. Use the software repair assistant on computer to repair your device. Connect your device to your computer to get the software repair assistant. AP Fastboot Flash Mode (Secure) Error: failed to load kernel! Fastboot reason: fall-through from normal boot mode"
On top of this my device will not connect to my computer through usb and all my data is deleted included twrp. I really dont know what to do

acejavelin said:
Honestly, if your phone can't talk to your computer with fastboot in the bootloader, your pretty much screwed.
How did you root? What specific version and steps did you take?
Click to expand...
Click to collapse
I was thinking of downloading the whole operating system on a micro sd card then connecting it to my phone.
Would that work?

enochthegreat said:
I was thinking of downloading the whole operating system on a micro sd card then connecting it to my phone.
Would that work?
Click to expand...
Click to collapse
No... Factory images and custom recovery can only be loaded with fastboot.
So if you connect you phone in the Bootloader to your PC and do "fastboot devices" what is the response? And what OS?

acejavelin said:
No... Factory images and custom recovery can only be loaded with fastboot.
So if you connect you phone in the Bootloader to your PC and do "fastboot devices" what is the response? And what OS?
Click to expand...
Click to collapse
The response is no devices attached. I am android 6.0

enochthegreat said:
The response is no devices attached. I am android 6.0
Click to expand...
Click to collapse
I meant your PC's operating system... I assume Windows? Which means it is likely a driver issue, does it show up in device manager?

enochthegreat said:
The response is no devices attached. I am android 6.0
Click to expand...
Click to collapse
Have you tried rsd lite it might recognize your device?

acejavelin said:
I meant your PC's operating system... I assume Windows? Which means it is likely a driver issue, does it show up in device manager?
Click to expand...
Click to collapse
My pc operating system is windows vista and my device used to show up on device manager. I used to be able to plug the usb and be able to look at my phone saying device connected

enochthegreat said:
"Start up failed: Your device didnt start up succesfully. Use the software repair assistant on computer to repair your device. Connect your device to your computer to get the software repair assistant. AP Fastboot Flash Mode (Secure) Error: failed to load kernel! Fastboot reason: fall-through from normal boot mode"
Click to expand...
Click to collapse
Do you have this when you boot into bootloader/fastboot mode?
Power off, vol - & power?
I think you can't repair it in home.
It looks like you flashed something wrong or something in wrong place.
F.e.: twrp into boot partition.

jonomods said:
Have you tried rsd lite it might recognize your device?
Click to expand...
Click to collapse
Hmm i just tried that and no device showed up. I think after this im just gonna buy a fresh usb cord and if that does work i am scarping this phone. I overall had a very bad experience with this phone anyways. Ill get back to you once i try.

But you had unlocked and flashed TWRP, right? So fastboot worked at one time and you understand how to use it, generally at least?

acejavelin said:
But you had unlocked and flashed TWRP, right? So fastboot worked at one time and you understand how to use it, generally at least?
Click to expand...
Click to collapse
Yes fastboot worked at one time and so did twrp. I had reached the last stage of rooting which was installing supersu when the whole thing crashed. After my phone stopped working i went into recovery mode and used twrp to format my data and delete everything. Since then i havent been able to plug in a usb or go into recovery mode

enochthegreat said:
Yes fastboot worked at one time and so did twrp. I had reached the last stage of rooting which was installing supersu when the whole thing crashed. After my phone stopped working i went into recovery mode and used twrp to format my data and delete everything. Since then i havent been able to plug in a usb or go into recovery mode
Click to expand...
Click to collapse
Hmm... Sounds like bad luck, hopefully a new, quality cable will take care of it for you

Looks like it was all bad luck. A day after I bricked my phone my charger port broke

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..