I flashed a custom rom and now my PC does not recognize my phone. I can't transfer files or fastboot to the phone from the PC.
I wanted to go back to stock, but when I went to flash-all, it stalls at waiting for device.
Not sure what happened, any help solving this would be appreciated.
It's not the drivers in the PC, it's something that happened within the phone.
Gordietm said:
I flashed a custom rom and now my PC does not recognize my phone. I can't transfer files or fastboot to the phone from the PC.
I wanted to go back to stock, but when I went to flash-all, it stalls at waiting for device.
Not sure what happened, any help solving this would be appreciated.
It's not the drivers in the PC, it's something that happened within the phone.
Click to expand...
Click to collapse
Deleted
Gordietm said:
I flashed a custom rom and now my PC does not recognize my phone. I can't transfer files or fastboot to the phone from the PC.
I wanted to go back to stock, but when I went to flash-all, it stalls at waiting for device. Not sure what happened, any help solving this would be appreciated. It's not the drivers in the PC, it's something that happened within the phone.
Click to expand...
Click to collapse
You should also try a different A-C cable. Do you still have a custom recovery or stock? If so you can use adb to push/pull files to the phone and try "update via adb". Have you done a full factory reset?
It's not the cable, I've a few different ones. I can't use adb, because the PC doesn't recognize that Mr phone is connected.
Gordietm said:
It's not the cable, I've a few different ones. I can't use adb, because the PC doesn't recognize that Mr phone is connected.
Click to expand...
Click to collapse
Have you enabled usb debugging , reinstalled the Google usb drivers, is the adb folder all right (maybe re-downlaod an re-install).
gee2012 said:
Have you enabled usb debugging , reinstalled the Google usb drivers, is the adb folder all right (maybe re-downlaod an re-install).
Click to expand...
Click to collapse
I have enabled USB debugging, the adb floder is fine. I still have to try updating the drivers, haven't done that yet. Thanks
Gordietm said:
I have enabled USB debugging, the adb floder is fine. I still have to try updating the drivers, haven't done that yet. Thanks
Click to expand...
Click to collapse
Turns out that restating the PC did the trick.
Everything works now. Thanks for the help.
Related
Hello guys, first of all i wanna thank u for your work, i'm a new user but i follow you by a really some times. Today i decided to install the 4.2.1 ROM on my nexus, i deleted all internal file in recovery mode but now when i connect the telephone on pc it doesn't work, maybe because the usb debugging is off and now i don't have any rom on my cellular phone. The problem is that i can't browse my telephone because my pc don't recognize it. i tryed to install some usb driver but nothing has worked then i can put in the now or old rom. how i can solved this problem? Thank u ( and sorry for my english )
NexusPsy said:
Hello guys, first of all i wanna thank u for your work, i'm a new user but i follow you by a really some times. Today i decided to install the 4.2.1 ROM on my nexus, i deleted all internal file in recovery mode but now when i connect the telephone on pc it doesn't work, maybe because the usb debugging is off and now i don't have any rom on my cellular phone. The problem is that i can't browse my telephone because my pc don't recognize it. i tryed to install some usb driver but nothing has worked then i can put in the now or old rom. how i can solved this problem? Thank u ( and sorry for my english )
Click to expand...
Click to collapse
To enable USB debugging, go to settings>about phone>tap on the build number 7 times. It will tell you "you are now a developer" and your will have USB debugging back
As far as your driver issues go, it sounds like you only installed fastboot drivers and not the regular drivers. Or somehow the regular drivers got deleted. If it was me, I would try rebooting my computer and phone. If that doesn't work, run the driver setup wizard in the Galaxy Nexus Toolkit. The first part of that process is deleting old drivers. It does a very thorough walkthrough on how to do that.
rudeguy said:
To enable USB debugging, go to settings>about phone>tap on the build number 7 times. It will tell you "you are now a developer" and your will have USB debugging back
As far as your driver issues go, it sounds like you only installed fastboot drivers and not the regular drivers. Or somehow the regular drivers got deleted. If it was me, I would try rebooting my computer and phone. If that doesn't work, run the driver setup wizard in the Galaxy Nexus Toolkit. The first part of that process is deleting old drivers. It does a very thorough walkthrough on how to do that.
Click to expand...
Click to collapse
Thanks for the answer, the problem is that i don't have any rom on my telephone atm then i can't go to settings ecc. is there a way to change the usb debugging in recovery mode?
NexusPsy said:
Thanks for the answer, the problem is that i don't have any rom on my telephone atm then i can't go to settings ecc. is there a way to change the usb debugging in recovery mode?
Click to expand...
Click to collapse
so you are running stock 4.2.1?
Or...I guess I'm not understand what condition your phone is currently in.
NexusPsy said:
Thanks for the answer, the problem is that i don't have any rom on my telephone atm then i can't go to settings ecc. is there a way to change the usb debugging in recovery mode?
Click to expand...
Click to collapse
Try connecting your GNex to PC while in recovery mode then use ADB to push any ROM from PC to your /sdcard/ of your GNex in order to flash it.
At worst case, I think you can use a fastboot image to flash your GNex via fastboot.
rudeguy said:
so you are running stock 4.2.1?
Or...I guess I'm not understand what condition your phone is currently in.
Click to expand...
Click to collapse
Now i running nothing, pratically i formatted all internal data because i would use the 4.2.1 version that is on my pc, after the format the computer does not recognize my cellular phone, so atm i don't have any rom on my phone and now i don't know how i can solve that, it could be easy if i can browse the phone on computer
ahmadallica said:
Try connecting your GNex to PC while in recovery mode then use ADB to push any ROM from PC to your /sdcard/ of your GNex in order to flash it.
At worst case, I think you can use a fastboot image to flash your GNex via fastboot.
Click to expand...
Click to collapse
It works, thank u < 3
I wanted to update my ROM, so I downloaded the newest version of Hason2000's Toolkit and was ready to flash the boot.img.
I plug my phone in; both my phone and computer recognizes the connection. I notice that USB Debugging is required so I enable it.
Problem? The computer stop recognizing my phone, the phone sees the connection just fine.
I tried updating the drivers (several times), I tried installing the driver on another computer, no go. Turning off the USB Debugging fixes the problem, but then I can't flash the kernel.
My ROM is IceColdJelly 2.5.1 (old I know), any ideas? :crying:
Metaception said:
I wanted to update my ROM, so I downloaded the newest version of Hason2000's Toolkit and was ready to flash the boot.img.
I plug my phone in; both my phone and computer recognizes the connection. I notice that USB Debugging is required so I enable it.
Problem? The computer stop recognizing my phone, the phone sees the connection just fine.
I tried updating the drivers (several times), I tried installing the driver on another computer, no go. Turning off the USB Debugging fixes the problem, but then I can't flash the kernel.
My ROM is IceColdJelly 2.5.1 (old I know), any ideas? :crying:
Click to expand...
Click to collapse
You should be in fastboot to flash a boot.img.
USB debugging has no effect on fastboot.
Tigerlight said:
You should be in fastboot to flash a boot.img.
USB debugging has no effect on fastboot.
Click to expand...
Click to collapse
Hason2000's All-In-One Toolkit needs USB Debugging to work, it appears to just automate the fastboot commands so I assumed doing it manually would be the same.
I guess I will try it after I DL the files needed, but I still don't understand why USB Debugging stops my computer from seeing the phone.
Metaception said:
Hason2000's All-In-One Toolkit needs USB Debugging to work, it appears to just automate the fastboot commands so I assumed doing it manually would be the same.
I guess I will try it after I DL the files needed, but I still don't understand why USB Debugging stops my computer from seeing the phone.
Click to expand...
Click to collapse
Yes the toolkit uses ADB to automate the reboot into fastboot mode.
And my understanding is that enabling USB Debugging changes the drivers required so that you can access the ADB interface.
I rooted and installed my first ROM using the toolkit, idk y it's different now.
I will try to flash via fastboot and then ask in the toolkit thread as well since these driver are the ones that the came with the toolkit.
EDIT: Whhhhooaa, did it! Cheers for fastboot
Metaception said:
Hason2000's All-In-One Toolkit needs USB Debugging to work, it appears to just automate the fastboot commands so I assumed doing it manually would be the same.
I guess I will try it after I DL the files needed, but I still don't understand why USB Debugging stops my computer from seeing the phone.
Click to expand...
Click to collapse
If you want adb usb drivers, i prefer to install moborobo from Moborobo.com.
Start application,
Plug your device with usb debugging on.
and it will do the work.
Soft bricked(?) my phone. I've got no ROM installed and No ROM/backup on my SD card.my laptop doesnt detect my phone even after re-installing USB device driver (error MTP USB device).
Now I want to use ADB Sideload to push a ROM into my SD card in recovery.
Unfortunately it seems like USB Debugging isn't turned on, it can't find my device.
Is there anyway to turn it on in recovery/ TWRP? any other way to bring back to life?
blinkjona said:
Soft bricked(?) my phone. I've got no ROM installed and No ROM/backup on my SD card.my laptop doesnt detect my phone even after re-installing USB device driver (error MTP USB device).
Now I want to use ADB Sideload to push a ROM into my SD card in recovery.
Unfortunately it seems like USB Debugging isn't turned on, it can't find my device.
Is there anyway to turn it on in recovery/ TWRP? any other way to bring back to life?
Click to expand...
Click to collapse
Maybe fastboot. Try this to keep your data: http://forum.xda-developers.com/showthread.php?t=2377307
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Maybe fastboot. Try this to keep your data: http://forum.xda-developers.com/showthread.php?t=2377307
Click to expand...
Click to collapse
Thanks, problem is USB debugging is not enabled :crying:
I think your problem is incorrect drivers, uninstall your current driver and install this
blinkjona said:
Thanks, problem is USB debugging is not enabled :crying:
Click to expand...
Click to collapse
fastboot has nothing to do with ADB.
thanks a bunch
there's a return to stock thread in general. use that.
Ok so I'm trying to flash L. All of my drivers are updated, I downloaded them again and installed just to be sure, but when I have my Nexus plugged in it still isn't detected, and yes USB debugging is on. I tried adb reboot bootloader and nothing, then I manually went into the bootloader and typed the flash-all command and it stayed stuck on waiting for device. Very frustrating, any help is appreciated.
C-4Nati said:
Ok so I'm trying to flash L. All of my drivers are updated, I downloaded them again and installed just to be sure, but when I have my Nexus plugged in it still isn't detected, and yes USB debugging is on. I tried adb reboot bootloader and nothing, then I manually went into the bootloader and typed the flash-all command and it stayed stuck on waiting for device. Very frustrating, any help is appreciated.
Click to expand...
Click to collapse
Try changing to PTP.
FWIW, I solved my driver issue this way. And mine works with ptp, mtp, debugging on or off.
You can also try using Koushs drivers, but it only is a half-measure fix.
Also sometimes you have to revoke usb auths, and unlock the device and look for the key fingerprint prompt when you first plug it into usb, and reaccept it.
mdamaged said:
Try changing to PTP.
FWIW, I solved my driver issue this way. And mine works with ptp, mtp, debugging on or off.
You can also try using Koushs drivers, but it only is a half-measure fix.
Also sometimes you have to revoke usb auths, and unlock the device and look for the key fingerprint prompt when you first plug it into usb, and reaccept it.
Click to expand...
Click to collapse
Didn't work, followed your steps in the other thread. I guess I'll just have to wait until a flashable zip for L :/
edit- And btw I tried it on both of my hard drives, one with windows 8 and one with windows 7, didn't work on either.
C-4Nati said:
Ok so I'm trying to flash L. All of my drivers are updated, I downloaded them again and installed just to be sure, but when I have my Nexus plugged in it still isn't detected, and yes USB debugging is on. I tried adb reboot bootloader and nothing, then I manually went into the bootloader and typed the flash-all command and it stayed stuck on waiting for device. Very frustrating, any help is appreciated.
Click to expand...
Click to collapse
These are the steps that I've used and have never had any problems with drivers. My brother had the same problem that your having a while back and these steps cleared up his driver problems. Maybe it's worth a shot.
First of all I NEVER let windows automatically install drivers except for a very short time period after a clean install of windows. It makes life easier if windows doesn't jump the gun and try to install what it thinks will work. I always get drivers directly from the manufacturer. After you stop windows from trying to do it's automatic driver install thing plug in your N7 to your computer and open device manager (I usually just type dev in the start search box of W7), find your device, right click and choose Uninstall, check the box for Delete the driver software for this device. When it finishes doing that reboot your computer and unplug your N7. Once your computer has completely booted back up plug in your N7 and open the device manager again. Find your N7 again, right click Update driver software then choose Browse my computer. Find your folder (including the subfolders) with the drivers and let it install, once it finishes unplug your N7 for a few seconds then plug it back in and hopefully it should be all good. If your want it I have a copy of the usb drivers at dropbox from my recently updated sdk install. I would just extract the folder and point the install to the whole folder, if you included subfolders at the install it will find what it needs inside the folder. Make sure you authorize your computer with usb debugging. Good luck! ; )
wantabe said:
These are the steps that I've used and have never had any problems with drivers. My brother had the same problem that your having a while back and these steps cleared up his driver problems. Maybe it's worth a shot.
First of all I NEVER let windows automatically install drivers except for a very short time period after a clean install of windows. It makes life easier if windows doesn't jump the gun and try to install what it thinks will work. I always get drivers directly from the manufacturer. After you stop windows from trying to do it's automatic driver install thing plug in your N7 to your computer and open device manager (I usually just type dev in the start search box of W7), find your device, right click and choose Uninstall, check the box for Delete the driver software for this device. When it finishes doing that reboot your computer and unplug your N7. Once your computer has completely booted back up plug in your N7 and open the device manager again. Find your N7 again, right click Update driver software then choose Browse my computer. Find your folder (including the subfolders) with the drivers and let it install, once it finishes unplug your N7 for a few seconds then plug it back in and hopefully it should be all good. If your want it I have a copy of the usb drivers at dropbox from my recently updated sdk install. I would just extract the folder and point the install to the whole folder, if you included subfolders at the install it will find what it needs inside the folder. Make sure you authorize your computer with usb debugging. Good luck! ; )
Click to expand...
Click to collapse
Thanks mate, didn't work though so I'm not sure what is going on. I'll just wait until zips get created but thanks for the help guys.
Sorry for noob question. Searched Searched xda and can't find anything. Pixel3 xl. Stock Android 10. Rooted. Windows 10 with correct drivers so it sees device. Can transfer files easily. USB debugging enabled. ADB and Fastboot do not see device. Used to work but not now. Tried kill-server and start-server in ADB. Tried different cables, restarting phone and computer. No luck. In fastboot mode (on phone) fastboot devices returns nothing. Totally stumped. Can anyone help. Again apologize for noob question but this has always worked before and I've flashed roms as well as stock numerous times with no issues till now. Help!
Do you have the current platform tools https://developer.android.com/studio/releases/platform-tools.html, and are you in the platform tools directory in command prompt or have your path set correctly?
sliding_billy said:
Do you have the current platform tools https://developer.android.com/studio/releases/platform-tools.html, and are you in the platform tools directory in command prompt or have your path set correctly?
Click to expand...
Click to collapse
I have the latest tools. Path set correctly as far as I can tell. I'm running the commands from the directory. Nothing. What kills me is that I never had this problem before untill I reinstalled Windows with a fresh copy.
Daisymae said:
I have the latest tools. Path set correctly as far as I can tell. I'm running the commands from the directory. Nothing. What kills me is that I never had this problem before untill I reinstalled Windows with a fresh copy.
Click to expand...
Click to collapse
You might need to allow unsigned drivers. Here's one how to, https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
jd1639 said:
You might need to allow unsigned drivers. Here's one how to, https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Click to expand...
Click to collapse
Thanks. Did that. Same thing. Blank list.
Daisymae said:
Thanks. Did that. Same thing. Blank list.
Click to expand...
Click to collapse
I think the easy step to determine if it is a phone or computer issue is to at least try from another computer. The one thing that did just occur to me would be to make sure you are using an A>C USB cable and A port and not a C>C with a C port. The Pixel series has tons of problems with C>C.
Have you recently updated and not re-authorized your phone?
sliding_billy said:
I think the easy step to determine if it is a phone or computer issue is to at least try from another computer. The one thing that did just occur to me would be to make sure you are using an A>C USB cable and A port and not a C>C with a C port. The Pixel series has tons of problems with C>C.
Click to expand...
Click to collapse
Thanks. Don't have another windows computer to try on. Do have an old Mac and it works on that, just not my windows laptop which is what I use. I have no idea what's making this happen. Computer sees the phone just fine.
spotmark said:
Have you recently updated and not re-authorized your phone?
Click to expand...
Click to collapse
Turned usb debugging off then back on again. When I plug in a cable I reauthorize usb debugging but get the same results.
Daisymae said:
Thanks. Don't have another windows computer to try on. Do have an old Mac and it works on that, just not my windows laptop which is what I use. I have no idea what's making this happen. Computer sees the phone just fine.
Click to expand...
Click to collapse
To my previous comment, are you using an A>C cable or the C>C that comes with the phone/charger? Besides that, it still sounds like it could be a driver issue where it is recognizing the phone as a generic USB storage device.
sliding_billy said:
To my previous comment, are you using an A>C cable or the C>C that comes with the phone/charger? Besides that, it still sounds like it could be a driver issue where it is recognizing the phone as a generic USB storage device.
Click to expand...
Click to collapse
I'm using an A-C cable. Same that I used before when it worked. I thought it might be a device driver too but when I plug the phone in the computer immediately sees it and if I open device manager the phone is seen as an android device.
Daisymae said:
I'm using an A-C cable. Same that I used before when it worked. I thought it might be a device driver too but when I plug the phone in the computer immediately sees it and if I open device manager the phone is seen as an android device.
Click to expand...
Click to collapse
If you boot to the bootloader and plug the phone in, does Windows recognize it then?
Daisymae said:
I'm using an A-C cable. Same that I used before when it worked. I thought it might be a device driver too but when I plug the phone in the computer immediately sees it and if I open device manager the phone is seen as an android device.
Click to expand...
Click to collapse
OK, thanks. One thing I can think to do is delete the driver, reboot the phone and computer and then plug in and start over. Make sure to use the Google device driver from the developer page.
ktmom said:
If you boot to the bootloader and plug the phone in, does Windows recognize it then?
Click to expand...
Click to collapse
No. Tried that first thing. Fastboot devices turns up nothing.
sliding_billy said:
OK, thanks. One thing I can think to do is delete the driver, reboot the phone and computer and then plug in and start over. Make sure to use the Google device driver from the developer page.
Click to expand...
Click to collapse
Believe it or not I already did that. I've tried everything with no luck. As I mentioned I was always able to use it before with no problems then this started when I reinstalled a fresh copy of windows.
Daisymae said:
Believe it or not I already did that. I've tried everything with no luck. As I mentioned I was always able to use it before with no problems then this started when I reinstalled a fresh copy of windows.
Click to expand...
Click to collapse
just for the heck of it, do you have other cables. Stranger things have happened that made a difference, and the next suggestion involves reinstalling computer and/or phone. Maybe a live USB Ubuntu disk to see what is working and what is not.
Daisymae said:
No. Tried that first thing. Fastboot devices turns up nothing.
Click to expand...
Click to collapse
I understood fastboot devices doesn't see it, but does Windows show a driver installed for it? I strongly suspect you don't have (the right) drivers properly installed.
ktmom said:
I understood fastboot devices doesn't see it, but does Windows show a driver installed for it? I strongly suspect you don't have (the right) drivers properly installed.
Click to expand...
Click to collapse
Yes. Windows shows a driver installed and when plugging it in identifies it as a Pixel 3 XL.
Daisymae said:
Yes. Windows shows a driver installed and when plugging it in identifies it as a Pixel 3 XL.
Click to expand...
Click to collapse
Do a search for fastboot, if you find more than one delete the one that is not in your Platform-tools folder.
Did you give fastboot execute permission?
Homeboy76 said:
Do a search for fastboot, if you find more than one delete the one that is not in your Platform-tools folder.
Did you give fastboot execute permission?
Click to expand...
Click to collapse
Only one instance of fastboot. Not sure what you mean execute
permissions. You mean on Windows or on the device? Windows has execute permissions. I don't have adb or fastboot on the device.