Hey guys, semi-noob here. Here is the situation:
1) encrypted device yesterday (Nexus 5 w/ stock android 4.4.2 and CWM Recovery)
2) 4.4.3 came out, downloaded and installed (yee! new dialer)
3) restarted after install (so excited! :fingers-crossed
4) enter the bootloop
5) try to do fastboot -> recovery mode
6) nope. recovery mode = bootloop
What do, XDA? I searched the forums, and nothing seems to address this. The N5 isn't even showing up on the devices list for my comp (W7 w/ ADB installed and ran before). I can't talk to it through my computer.
haloux said:
Hey guys, semi-noob here. Here is the situation:
1) encrypted device yesterday (Nexus 5 w/ stock android 4.4.2 and CWM Recovery)
2) 4.4.3 came out, downloaded and installed (yee! new dialer)
3) restarted after install (so excited! :fingers-crossed
4) enter the bootloop
5) try to do fastboot -> recovery mode
6) nope. recovery mode = bootloop
What do, XDA? I searched the forums, and nothing seems to address this. The N5 isn't even showing up on the devices list for my comp (W7 w/ ADB installed and ran before). I can't talk to it through my computer.
Click to expand...
Click to collapse
Hi.
Boot into bootloader
open cmd
Type fastboot devices
See if your device gets detected or not.
If yes..you can flash stock factory IMG.
If not make sure u have installed the drivers and adb set up is there.
Sent from my Nexus 5 using XDA Free mobile app
Vivek_Neel said:
Hi.
Boot into bootloader
open cmd
Type fastboot devices
See if your device gets detected or not.
If yes..you can flash stock factory IMG.
If not make sure u have installed the drivers and adb set up is there.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
Thanks for the quick response.
Win7 doesn't even detect the N5. Device manager doesn't even show that it exists (as android device or anything else). I've unplugged and replugged, no sound, multiple different ports.
Whatever you do don't use a toolkit try and fix it.If something else happens trying to diagnosis it would be very hard.Manual installation and fixing is the Best. Plus you learn how to get out of jams.
habitformer said:
Whatever you do don't use a toolkit try and fix it.If something else happens trying to diagnosis it would be very hard.Manual installation and fixing is the Best. Plus you learn how to get out of jams.
Click to expand...
Click to collapse
Will do (or won't do?). Thank you for the advice. Any tips on how to get my system to recognize the device?
So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
Verified that ADB and all SDK software was up to date
Restarted computer to verify USB controller status
Refreshed device manager list before and after plugging in N5.
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.
haloux said:
So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
Verified that ADB and all SDK software was up to date
Restarted computer to verify USB controller status
Refreshed device manager list before and after plugging in N5.
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.
Click to expand...
Click to collapse
I swear I went through this 2 days ago @scarmon25 will tell,we had a late night hangouts session.
I used a one of my many nexus cables and it finally linked up.Not to sound like a jerk but you've got USB debugging on right?
I reread your OP.If.you can get into recovery just restore a back up!!! Than all should be good.
haloux said:
So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.
Click to expand...
Click to collapse
One thing you haven't stated. Do you have the fastboot drivers installed? They're different from adb. Since you're not seeing the device after "fastboot devices", I would check and make sure.
habitformer said:
I swear I went through this 2 days ago @scarmon25 will tell,we had a late night hangouts session.
I used a one of my many nexus cables and it finally linked up.Not to sound like a jerk but you've got USB debugging on right?
I reread your OP.If.you can get into recovery just restore a back up!!! Than all should be good.
Click to expand...
Click to collapse
Yea, USB debugging was on. The recovery mode just yields the dead android.
adrman said:
One thing you haven't stated. Do you have the fastboot drivers installed? They're different from adb. Since you're not seeing the device after "fastboot devices", I would check and make sure.
Click to expand...
Click to collapse
How would I verify that? I assumed that fastboot drivers were installed bc I used them in the past.
Code:
fastboot devices
(yields)
No devices found.
I would do a search here for "windows fastboot drivers". I can't be of much help to you as I haven't used windows for several years now. Also, if you have a working Android device, see if it shows up when connected in bootloader mode as a test.
Sent from my Nexus 5 using Tapatalk
Small breakthrough:
Used a diff cable like someone suggested and my device appeared. Updated device driver and fastboot driver. ADB devices still yields no device attached though.
haloux said:
Small breakthrough:
Used a diff cable like someone suggested and my device appeared. Updated device driver and fastboot driver. ADB devices still yields no device attached though.
Click to expand...
Click to collapse
if you are in fastboot mode (or bootloader) you should use the fastboot command and not the adb.
type: fastboot devices
any signs of life?
Tapatalk-kal küldve az én Nexus 5-el
bitdomo said:
if you are in fastboot mode (or bootloader) you should use the fastboot command and not the adb.
type: fastboot devices
any signs of life?
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Wow. It worked! The device showed up! Thank you guys.
haloux said:
Wow. It worked! The device showed up! Thank you guys.
Click to expand...
Click to collapse
Not sound like a turd but I mentioned using a nexus USB cable in post #7 after mentioning my issue.
Related
This seems very much to be a driver problem. Everything I find says Mac needs no driver for this device though.
dab works fine. android file transfer seems the device file structure fine. only thing not working, is when the device goes into fastboot mode, "fast boot devices" returns nothing. "fastboot oem unlock" sits and 'waiting for device' and never goes any further.
What's going wrong?
Blario said:
This seems very much to be a driver problem. Everything I find says Mac needs no driver for this device though.
dab works fine. android file transfer seems the device file structure fine. only thing not working, is when the device goes into fastboot mode, "fast boot devices" returns nothing. "fastboot oem unlock" sits and 'waiting for device' and never goes any further.
What's going wrong?
Click to expand...
Click to collapse
no driver's necessary, maybe your sdk installation is an old version and needs to be updated for kitkat?
fastboot is 1 word, not 2 as you have listed
you would execute this in the terminal:
./fastboot devices
( might be ./fastboot-mac devices )
ilanzo82 said:
no driver's necessary, maybe your sdk installation is an old version and needs to be updated for kitkat?
Click to expand...
Click to collapse
Yeah… not working at all. adb can see the device. I've never seen the mac fastboot see it. Also, it's fully updated to API 19.
Zepius said:
fastboot is 1 word, not 2 as you have listed
you would execute this in the terminal:
./fastboot devices
( might be ./fastboot-mac devices )
Click to expand...
Click to collapse
autocorrect keeps changing to two words in text boxes other than terminal. It's not finding anything. Others have seen different? That'd be shocking to me. With no drivers installed?
Blario said:
Yeah… not working at all. adb can see the device. I've never seen the mac fastboot see it. Also, it's fully updated to API 19.
autocorrect keeps changing to two words in text boxes other than terminal. It's not finding anything. Others have seen different? That'd be shocking to me. With no drivers installed?
Click to expand...
Click to collapse
I've used both adb and fastboot on a Mac for my Nexus 5, Nexus 4 and Nexus 7.
No drivers needed.
If you have adb and fastboot in the same directory and you can use adb without issues then fastboot should work as long as you've rebooted into the bootloader.
If it's still not working maybe take a look at this writeup about setting up adb and fastboot on a Mac... http://forum.xda-developers.com/showthread.php?t=1917237
Good luck!
Sent from my Nexus 5 using xda app-developers app
chef_christoph said:
I've used both adb and fastboot on a Mac for my Nexus 5, Nexus 4 and Nexus 7.
No drivers needed.
If you have adb and fastboot in the same directory and you can use adb without issues then fastboot should work as long as you've rebooted into the bootloader.
If it's still not working maybe take a look at this writeup about setting up adb and fastboot on a Mac... http://forum.xda-developers.com/showthread.php?t=1917237
Good luck!
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Because I'm on API 19, that means I've already updated the SDK as far as is possible. ADB works. fastboot doesn't. What nexus 5 fastboot driver actually works?
Basically what happened was:
After updating PureNexus on my Pixel XL, I flashed the vendor image to only one slot
Booted system to find endless crash dialogs
Rebooted into recovery to find TWRP gone
Did a Full Wipe under stock recovery, hoping it'd fix things
I can now get back into system, but it's glitchy
Neither adb devices nor fastboot devices see the phone
Troubleshooting I've tried:
Plugged usb-c thumb drive into phone. It works fine, so it can't be the port
Plugged old Nexus 5X into computer. ADB and FB can see it just fine, so it can't be the cable or drivers
Plugged Pixel XL into computer. Phone charges but pulldown notification doesn't appear
I don't know what else to do. Prior to this, I was always able to see my Pixel from ADB/FB. I don't know why it's not working now. I would've thought that a "fastboot devices" from bootloader would at least work, and yet it's not. I can get into stock recovery just fine, but there don't seem to be any helpful options there.
Does anyone know what's going on or any way to remedy the situation?
NOTE: I'm on a Mac
rajah sulayman said:
(crossposting from here as this looks like a more active sub and I'm desperate).
Basically what happened was:
After updating PureNexus on my Pixel XL, I flashed the vendor image to only one slot
Booted system to find endless crash dialogs
Rebooted into recovery to find TWRP gone
Did a Full Wipe under stock recovery, hoping it'd fix things
I can now get back into system, but it's glitchy
Neither adb devices nor fastboot devices see the phone
Troubleshooting I've tried:
Plugged usb-c thumb drive into phone. It works fine, so it can't be the port
Plugged old Nexus 5X into computer. ADB and FB can see it just fine, so it can't be the cable or drivers
Plugged Pixel XL into computer. Phone charges but pulldown notification doesn't appear
I don't know what else to do. Prior to this, I was always able to see my Pixel from ADB/FB. I don't know why it's not working now. I would've thought that a "fastboot devices" from bootloader would at least work, and yet it's not. I can get into stock recovery just fine, but there don't seem to be any helpful options there.
Does anyone know what's going on or any way to remedy the situation?
Click to expand...
Click to collapse
It can be the drivers, Windows isn't going to use the same drivers as the Nexus, unless you manually select them in device manager.
Sent from my PH-1 using Tapatalk
sd_shadow said:
It can be the drivers, Windows isn't going to use the same drivers as the Nexus, unless you manually select them in device manager.
Click to expand...
Click to collapse
But I never had a problem with the drivers before now. I've always been able to ADB my Pixel, which is how I rooted and installed TWRP originally.
rajah sulayman said:
But I never had a problem with the drivers before now. I've always been able to ADB my Pixel, which is how I rooted and installed TWRP originally.
Click to expand...
Click to collapse
do you know how to check which drivers are selected.?
Sent from my XT1254 using XDA Labs
sd_shadow said:
do you know how to check which drivers are selected.?
Click to expand...
Click to collapse
Is it through the Android Studio SDK manager? I remember using that way back when to get everything set up, but I haven't really used it since then.
Actually I just remembered that Mac don't need drivers, right? Per Google:
"Note: If you're developing on Mac OS X or Linux, then you do not need to install a USB driver. Instead see Using Hardware Devices."
Update: Pulled out my Windows laptop and installed everything (drivers, Android Studio, et al) to see if I'd have better luck there.
To test, I first plugged in my working Nexus 5X. Windows immediately recognized it. Pulled up a prompt and adb devices saw the phone no problem.
Unplugged the Nexus and plugged in my Pixel XL. Nothing. No "hardware plugged in" chime, nothing listed under Device Manager, nada. Likewise, the phone itself doesn't acknowledge that it's been plugged in because there's no Android System pulldown.
If it were a driver issue, Device Manager would still at least be able to see the phone (it just wouldn't know what it was). But I'm getting absolutely nothing.
I can only assume that the problem is indeed with the phone itself. I don't know what the problem is exactly, but I know it wasn't there before all of this. Either way, this means my only hope for a fix would have to be through the phone itself. But since Stock Recovery doesn't seem to offer me many options, I have no clue what to do next.
Is there some sort of "secret" key combo or command or something that'll do a low-level format of the phone or something? I'm grasping at straws here, I know, but I honestly don't know what else there is I can do.
-------
Update 2: If I plug it in while in Bootloader, Windows recognizes that a device was connected, but as an "Unknown USB Device (Device Descriptor Request Failed)"
None of the solutions I can think of (or Google) seems to work. Has anyone heard of this problem before? I'm vainly hoping there's a fix out there that I just haven't found yet.
Hello
I need help with my TF700.
I had this tablet for some time. It was unlocked with TWRP and ZOMBI-POP.
Last week I wanted to upgrade it for KIT-Kass 7.1
I wanted to update my TWRP for kang wersion ( 2.8.7.4) through TWRP and during the process it rebooted.
Then I've got a bootloop on normal starting. I can't get into recovery mode through power + vol up - tablet has no respond for that
I can only go to fastboot through power + vol down but when I connect it to windows with adb drivers or to linux(FWUL) it sees no device and no respond for any command.
Do You have any idea what to do ?
Thank You in advance
Sorry to say this but, if you can't send it commands then you are most likely hard bricked. What OS are you running on the computer with fastboot on it? - NP
Nektopoli said:
Sorry to say this but, if you can't send it commands then you are most likely hard bricked. What OS are you running on the computer with fastboot on it? - NP
Click to expand...
Click to collapse
This sounds not so good. I use windows 10 but as I said also I used FWUL to try.
marmacapp said:
This sounds not so good. I use windows 10 but as I said also I used FWUL to try.
Click to expand...
Click to collapse
Do you have access to a Windows 7 computer/laptop. There's an issue with Windows 10 and the fastboot drivers not working together, and causing a problem like yours. - NP
marmacapp said:
This sounds not so good. I use windows 10 but as I said also I used FWUL to try.
Click to expand...
Click to collapse
Found this in another thread, windows 10 fix. - NP
"I used Windows 10 and had to disable driver signature enforcement. Once I did this the PC recognized the tab without issue. "
To disable;
http://www.thewindowsclub.com/disable-driver-signature-enforcement-windows
Thank You for the info, but I have laptop with Windows7 and still the same.
But if I have text on screen like this Starting fastboot USB download protocol can the device still be hard-bricked ?
Maybe I am missing some drivers ?
I would d/l Minimal ADB and Fastboot from here;
https://forum.xda-developers.com/showthread.php?t=2317790
and Universal_Naked_Driver_0.72 here; - NP
https://forum.xda-developers.com/showthread.php?t=2263822
For now the problem is I can not install the "naked driver" because devices manager can not see TF700 when it is connected, so I can't update the driver
Have you tried sending the [fastboot reboot] command to see if the tablet will reboot. When I bricked my TF201t my laptop didn't see it but it still took the commands allowing me to wipe the recovery partition and install the correct TWRP. - NP
Dear Guys
I know that this topic is quite old, but I am still fighting with this problem.
I tryied different drivers, 3 different computers ( two with windows 10 one with windows 7) and I can;t connect to fastboot.
The tablet is in this mode, but when I will use adb and type any command like fastboot reboot - it displays "waiting for device"
Do You have any idea what else can I try ?
Best regards
Hi,
me too! I was using it at lunch - no problem. Got home and turned it on and unrecoverable bootloader error.
Hello everyone !
This morning, out of the blue (I think it was during a Whatsapp automatic backup), my Google Pixel 2 XL shut down. I can't get it started and the phone is stuck on the white screen with the Google Logo. I can access the bootloader and Recovery though, so that's something. I spent my whole day skimming through the forum and other websites/videos. but I only have a slight understanding of what is happening and I'm not sure where my problem lays. Now when I click on the Start option in the bootloader, it just starts back in the bootloader screen.
I've been a bad scholar and did not backup my data. So if there is a solution, I'd rather not factory reset my phone.
Got my phone a month ago.
I unlocked the bootloader and rooted the phone (Magisk).
Stock Rom
Today,
I tried to connect my phone to my computer but so far it is not recognised by my computer and I can't access OEM unlocking/usb modes.
I verified. I have the latest adb and fastboot version on my computer, dowloading the latest SDK platforms tools.
I downloaded the usb driver packages from the SDK manager.
I tried using an universal android adb driver tool.
I've used multiple usb-c to usb-c and usb-c to usb-a cables, on different ports.
I restarted my phone and computer multiple times (just to make sure)
My phone doesn't appear in the Device manager.
I am now completely lost and would really much appreciate your help.
Thank you for reading this. Thank you for helping me !
Sounds bad.....maybe in first instance try letting tge device shut off due to low battery. Maybe this helps to hard reset. So just leave it on in fastboot mode
donkeydances said:
Hello everyone !
This morning, out of the blue (I think it was during a Whatsapp automatic backup), my Google Pixel 2 XL shut down. I can't get it started and the phone is stuck on the white screen with the Google Logo. I can access the bootloader and Recovery though, so that's something. I spent my whole day skimming through the forum and other websites/videos. but I only have a slight understanding of what is happening and I'm not sure where my problem lays. Now when I click on the Start option in the bootloader, it just starts back in the bootloader screen.
I've been a bad scholar and did not backup my data. So if there is a solution, I'd rather not factory reset my phone.
Got my phone a month ago.
I unlocked the bootloader and rooted the phone (Magisk).
Stock Rom
Today,
I tried to connect my phone to my computer but so far it is not recognised by my computer and I can't access OEM unlocking/usb modes.
I verified. I have the latest adb and fastboot version on my computer, dowloading the latest SDK platforms tools.
I downloaded the usb driver packages from the SDK manager.
I tried using an universal android adb driver tool.
I've used multiple usb-c to usb-c and usb-c to usb-a cables, on different ports.
I restarted my phone and computer multiple times (just to make sure)
My phone doesn't appear in the Device manager.
I am now completely lost and would really much appreciate your help.
Thank you for reading this. Thank you for helping me !
Click to expand...
Click to collapse
Flash latest factory image (either 8.1 or DPx/P/9.0).
mrorange2108 said:
Sounds bad.....maybe in first instance try letting tge device shut off due to low battery. Maybe this helps to hard reset. So just leave it on in fastboot mode
Click to expand...
Click to collapse
I'm trying that. Thank you !
xFirefly93 said:
Flash latest factory image (either 8.1 or DPx/P/9.0).
Click to expand...
Click to collapse
Thank you for your answer. How would you do that ? I can't get it to be recognized by my computer.
donkeydances said:
Thank you for your answer. How would you do that ? I can't get it to be recognized by my computer.
Click to expand...
Click to collapse
Have you tried with the Fastboot protocol?
xFirefly93 said:
Have you tried with the Fastboot protocol?
Click to expand...
Click to collapse
Like I said, I can't get my phone to be recognized by my computer so no Fastboot protocol. I am not sure why it doesn't get recognized though.
Hello everybody, I was trying to update my Magisk and that process failed. I thought nothing of it put it off. Tried to restart my phone a few days later and now it's stuck in a fastboot loop. Cannot even go into recovery. So I'm like okay, probably need to reinstall recovery and flash a clean rom again. Try the "fastboot boot recovery.img" command and it's giving me a "waiting for any device". Googling says it's a driver error, but that's strange because I have used my phone on this computer before with ADB and fastboot. Fastboot and ADB commands work fine on my Oneplus 3T.
A week ago I also had the problems after the Magisk update. But connecting to the PC worked normally for me. Once you've installed the drivers, there shouldn't be any problems. You could use a different cable.
Incidentally, Magisk only messed up the boot image. It is sufficient if you flash your boot.img, then the twrp.zip, reboot into recovery, then the magisk.zip.
That was completely enough for me. Cell phone works normally again, without data loss.
Good luck!
Yeah that's exactly what I am trying to do, I can't even flash the boot.img to get into recovery, my computer won't recognize the device for some reason now. Do you know where I can find the drivers? I could only find shady 3rd party sites. Thanks!
Tried installing drivers from here, no change.
Download Latest OnePlus USB Drivers for Windows and Mac
Download The Latest OnePlus USB Drivers For All OnePlus Android Smartphones. We Have Included USB drivers for Both Windows And Apple MAC OS Users. Download Links Given Below.
www.getdroidtips.com
This is installed and works with me
ghost323 said:
This is installed and works with me
Click to expand...
Click to collapse
No joy, looks like that's the same file as the one I downloaded. Thanks for your help anyways.
Now I can't even turn my phone off lol. It woke itself up this morning magically and now whenever I hit power off in fastboot it just boots up again into fastboot. Might have to send it in...the horror
Your phone is crying out for help. It doesn't like to die.
I think you will have tried everything possible. Have you already connected it to another computer with the right drivers? Tried other cables?
ghost323 said:
Your phone is crying out for help. It doesn't like to die.
I think you will have tried everything possible. Have you already connected it to another computer with the right drivers? Tried other cables?
Click to expand...
Click to collapse
Haha yeah, it's like your kid who refuses to go to bed and is throwing a tantrum. Yeah two different computers that are known to have worked with this phone in the past (how I unlocked the bootloader in the first place). Different ports, different cables. It seems like I'm having the same issue that a lot of other people are having with the last Magisk update, except they're able to flash the recovery image in fastboot to get back running.
This is a ****ty situation! That was really a nasty magisk update. I wonder why its consequences are so different, even though it is the same cell phone.
fastboot cannot recognize device but adb can
usb debugging is enabled on device. running latest version of adb, fastboot. Have tried on both mac and win10 but same issue on both. Oneplus 7 pro is running 10.3.0GM21AA >fastboot devices >adb devices List of devices attached 966c8016...
forum.xda-developers.com
Look at this. Maybe it will help you so that your computer recognizes the cell phone again.