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.

Huge mistake

Hey guys ,let's get straight. I'm totally dumb.
After flashing Lollipop factory img which reseted my internal storage (made a backup on PC), today I decided to try AOSP. Downloaded with my phone, flashed it. But the file was corrupted (bad download or something). Results : I only had that rom on my internal storage, my phone won't boot. I thought I could use NRT, although it as always worked fine, now it keeps telling me "adb device not found", "no fastboot devices". So, actually I can't do anything and I can't see what can I do.. already tried reinstalling drivers, but windows isn't even showing my nexus 4 on device manager
Looks like I need help, and sleep too..

Pedrau said:
Hey guys ,let's get straight. I'm totally dumb.
After flashing Lollipop factory img which reseted my internal storage (made a backup on PC), today I decided to try AOSP. Downloaded with my phone, flashed it. But the file was corrupted (bad download or something). Results : I only had that rom on my internal storage, my phone won't boot. I thought I could use NRT, although it as always worked fine, now it keeps telling me "adb device not found", "no fastboot devices". So, actually I can't do anything and I can't see what can I do.. already tried reinstalling drivers, but windows isn't even showing my nexus 4 on device manager
Looks like I need help, and sleep too..
Click to expand...
Click to collapse
Hmm can you get at least to the bootloader menu. If you can, there's still hope. At this time, you're better off using the manual commands rather than the NRT (the NRT use a set of pre-configured scripts and doesn't always end up where you would like to) Have you tried to also plug your device inside another USB port?

zaclimon said:
Hmm can you get at least to the bootloader menu. If you can, there's still hope. At this time, you're better off using the manual commands rather than the NRT (the NRT use a set of pre-configured scripts and doesn't always end up where you would like to) Have you tried to also plug your device inside another USB port?
Click to expand...
Click to collapse
Yes I can acces to bootloader and TRWP. Tried another USB port, another USB cable, using manual commands it says " <waiting for device>" and nothing happen..

What drivers are you using. I use the Google usb driver available here
http://developer.android.com/sdk/win-usb.html
How to install these drivers here
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
You also need the android platform tools installed on your pc for adb and fast boot commands to work. I use this installer
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have completed these steps on your PC before you connect it to your nexus.

venu123 said:
What drivers are you using. I use the Google usb driver available here
http://developer.android.com/sdk/win-usb.html
How to install these drivers here
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
You also need the android platform tools installed on your pc for adb and fast boot commands to work. I use this installer
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have completed these steps on your PC before you connect it to your nexus.
Click to expand...
Click to collapse
Thanks buddy , but my drivers were fine before all this. And now i can't reinstall it that way since my nexus isn't even showing up on device manager, I used another method from NRT. Gonna test on w7..
EDIT: Problem solved using windows 7. There seems to have problem with drivers on windows 8.1

Yes, in windows 8 you need to disable driver signature enforcement. In windows 7 no problem.

venu123 said:
Yes, in windows 8 you need to disable driver signature enforcement. In windows 7 no problem.
Click to expand...
Click to collapse
I didn't have to on Windows 8.1.

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.

Bricked my 6p and computer wont recognise it

Ok, so i managed to brick my nexus 6p, it will not boot into android, stupid as i am i do not have a backup on the phone, and on top of that, windows does not recognise my device in bootloader mode. Of course i have tried installing USB drivers, but strangely my computer will not even recognise that im plugging in a USB device, i/e it wont even make the USB connected sound.
Not really sure what to do, but im hoping anyone could maybe help me out, thanks!

axeeeel said:
Ok, so i managed to brick my nexus 6p, it will not boot into android, stupid as i am i do not have a backup on the phone, and on top of that, windows does not recognise my device in bootloader mode. Of course i have tried installing USB drivers, but strangely my computer will not even recognise that im plugging in a USB device, i/e it wont even make the USB connected sound.
Not really sure what to do, but im hoping anyone could maybe help me out, thanks!
Click to expand...
Click to collapse
How did you brick it? What drivers are you using?

Heisenberg said:
How did you brick it? What drivers are you using?
Click to expand...
Click to collapse
I tried to install franco kernel on my chroma rom, and it just wouldn't boot.
Also, I am using the drivers installed by the unified android toolkit.

axeeeel said:
I tried to install franco kernel on my chroma rom, and it just wouldn't boot.
Also, I am using the drivers installed by the unified android toolkit.
Click to expand...
Click to collapse
Do you still have the Chroma zip on your phone? I'm guessing not, but if you do just flash that. You could try uninstalling the drivers that you currently have and installing the drivers from the Android SDK. I have a link to the SDK download page and instructions on how to install it in my guide. Otherwise, do you have access to a Linux machine? No drivers required for Linux, you just need to install the Android SDK and adb and fastboot should work out of the box so to speak. Or if you don't have access to a Linux machine you could even create a bootable Linux usb and do it that way.

Heisenberg said:
Do you still have the Chroma zip on your phone? I'm guessing not, but if you do just flash that. You could try uninstalling the drivers that you currently have and installing the drivers from the Android SDK. I have a link to the SDK download page and instructions on how to install it in my guide. Otherwise, do you have access to a Linux machine? No drivers required for Linux, you just need to install the Android SDK and adb and fastboot should work out of the box so to speak. Or if you don't have access to a Linux machine you could even create a bootable Linux usb and do it that way.
Click to expand...
Click to collapse
I just came back home from buying a new USB cable, and apparently it was just my cable (original 6p cable) that wasnt working... Terribly sorry for wasting your time, i appreciate it though!

axeeeel said:
I just came back home from buying a new USB cable, and apparently it was just my cable (original 6p cable) that wasnt working... Terribly sorry for wasting your time, i appreciate it though!
Click to expand...
Click to collapse
No problem at all, glad to see you're up and running again.

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?