A friend of mine asked me to help them with their galaxy nexus. They attempted to root it and now it's not working. If I turn it on normally I get a Google logo and lock. I can start it in fastboot mode and recovery. In all cases Windows recognizes that a device is plugged in, I get a chime when it's plugged and unplugged, but it does not show up as a device even when mounted in CWM. As far as fastboot goes I'm sure the drivers are installed properly, it detects other devices correctly but this one doesn't show up. Is this fixable or is the device bricked? Any help would be appreciated.
Sent from my A0001 using XDA Free mobile app
What do you get when you type: fastboot devices. And what is in the Windows device manager window when the phone is connected?
Sent from my Galaxy Nexus using XDA Free mobile app
mrgnex said:
What do you get when you type: fastboot devices. And what is in the Windows device manager window when the phone is connected?
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Nothing is listed when I type fastboot devices. The windows device manager shows "Android 1.0"
Bklynrx7 said:
Nothing is listed when I type fastboot devices. The windows device manager shows "Android 1.0"
Click to expand...
Click to collapse
Yeah thats a driver problem. Click on Android 1.0 and click on update drivers then search for the google or Samsung fastboot drivers and install them.
Sent from my Galaxy Nexus using XDA Free mobile app
mrgnex said:
Yeah thats a driver problem. Click on Android 1.0 and click on update drivers then search for the google or Samsung fastboot drivers and install them.
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, that worked perfectly. The problem I'm having now is that I can't get it to mount so I can transfer an image to it. It worked perfectly in fastboot and I was able to install TWRP but neither fastboot or windows picks it up as a mounted location. Twrp shows everything except for system is mounted and even when I mount system it still does not show up.
Thanks for getting me this far.
Sent from my A0001 using XDA Free mobile app
Bklynrx7 said:
Thanks, that worked perfectly. The problem I'm having now is that I can't get it to mount so I can transfer an image to it. It worked perfectly in fastboot and I was able to install TWRP but neither fastboot or windows picks it up as a mounted location. Twrp shows everything except for system is mounted and even when I mount system it still does not show up.
Thanks for getting me this far.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
No problem The bootloader is not for transferring files. If you want to transfer files you can use adb push or adb sideload in recovery.
Sent from my Galaxy Nexus using XDA Free mobile app
mrgnex said:
No problem The bootloader is not for transferring files. If you want to transfer files you can use adb push or adb sideload in recovery.
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Yea, that's the problem, adb push doesn't detect the device, and windows doesn't detect it as a storage volume I can transfer files to. When I try to push to sdcard it cant locate the volume. Do I have to change the drivers for that? I haven't had that issue with any other device.
Yeah it seems like a driver problem. What does Windows device manager display?
Sent from my Galaxy Nexus using XDA Free mobile app
mrgnex said:
Yeah it seems like a driver problem. What does Windows device manager display?
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Device manager shows the category: "SAMSUNG Android Phone" which contains the device "Google Galaxy Nexus ADB Interface".
Weird. What if you type "adb devices"?
Sent from my Galaxy Nexus using XDA Free mobile app
Related
Terminal isn't working as adb doesn't detect my phone.
For example running adb shell returns "error: device not found"
Adb devices gives a empty list.
Any suggestions on how to fix?
Sent from my HTC One X using xda app-developers app
Three choices:
1. Switch to MTP: Settings > storage > menu btn
2. Use ADB wireless
3. Use ASB in recovery
Sent from my IceCold One X
treebill said:
Terminal isn't working as adb doesn't detect my phone.
For example running adb shell returns "error: device not found"
Adb devices gives a empty list.
Any suggestions on how to fix?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
It's probably because you don't have adb drivers.
Make sure the drivers are installed.
Are you using windows 8?
Sent from my GT-N8000 using Tapatalk HD
csec said:
It's probably because you don't have adb drivers.
Make sure the drivers are installed.
Are you using windows 8?
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
I'm using the terminal on the phone itself, it was working but suddenly stopped.
Adb is working fine from my PC.
Edit: just plugged in phone to PC and got "usb device no recognised" then car mode was enabled on my phone.... thinking maybe is CM
Sent from my HTC One X using xda app-developers app
So basically I've read everywhere that you need to install all the drivers. So I've done that. Then I've downloaded Hasoon2000 extracted to my desktop, opened it up and as soon as I get to the 'get token id' the cmd prompts me with:
C:\users\craig\desktop\htc is not recognised as an internal or external command'
What am I doing wrong here? I've uninstalled and reinstalled the drivers, uninstalled every other thing that I thought may conflict with the drivers but to no avail.
Sent from my HTC One X using xda app-developers app
Craiglivesey94 said:
So basically I've read everywhere that you need to install all the drivers. So I've done that. Then I've downloaded Hasoon2000 extracted to my desktop, opened it up and as soon as I get to the 'get token id' the cmd prompts me with:
C:\users\craig\desktop\htc is not recognised as an internal or external command'
What am I doing wrong here? I've uninstalled and reinstalled the drivers, uninstalled every other thing that I thought may conflict with the drivers but to no avail.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
no-one here can see what you are, or more importantly are not, doing so it is really difficult to answer your question. but rest assured that if you follow the instructions to the letter it will work so you have obviously missed a step. I used the same all in one for my hox last year and it worked without problem. all I can think of at the minute, as it is cmd you are having the problem with, is that maybe the path you have located your files in is invalid. or maybe you don't have debugging turned on
Craiglivesey94 said:
C:\users\craig\desktop\htc is not recognised as an internal or external command'
Click to expand...
Click to collapse
Cmd told you right there what's wrong, that command was not recognised you need to doubt check what you're typing
Sent from my HTC One X using xda app-developers app
nogotaclue said:
no-one here can see what you are, or more importantly are not, doing so it is really difficult to answer your question. but rest assured that if you follow the instructions to the letter it will work so you have obviously missed a step. I used the same all in one for my hox last year and it worked without problem. all I can think of at the minute, as it is cmd you are having the problem with, is that maybe the path you have located your files in is invalid. or maybe you don't have debugging turned on
Click to expand...
Click to collapse
1. I installed all the drivers
2. I Downloaded Hasoon2000
3. I extracted to desktop
4. I open it and follow the steps.
USB debugging is enabled. What am I doing wrong? Could it be that drivers aren't installing properly?
Sent from my HTC One X using xda app-developers app
Craiglivesey94 said:
1. I installed all the drivers
2. I Downloaded Hasoon2000
3. I extracted to desktop
4. I open it and follow the steps.
USB debugging is enabled. What am I doing wrong? Could it be that drivers aren't installing properly?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
does the pc recognise your device? ie, does it show up in explorer as a drive
---------- Post added at 11:43 AM ---------- Previous post was at 11:39 AM ----------
treebill said:
Cmd told you right there what's wrong, that command was not recognised you need to doubt check what you're typing
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
well actually if he is using the toolkit he is not typing anything, he is just pressing the button for each step and the toolkit is "typing" the command so it cant be spelling
nogotaclue said:
does the pc recognise your device? ie, does it show up in explorer as a drive
Click to expand...
Click to collapse
Yeah I can go into the sd card through my computer and it's shows up as 'HTC One X'. It even recognises it on HTC sync.
Sent from my HTC One X using xda app-developers app
Craiglivesey94 said:
Yeah I can go into the sd card through my computer and it's shows up as 'HTC One X'. It even recognises it on HTC sync.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
ok, when in the booloader can you see "fastboot usb" on phone screen?
nogotaclue said:
ok, when in the booloader can you see "fastboot usb" on phone screen?
Click to expand...
Click to collapse
I put my phone in bootloader, then connected USB, then fastboot USB appears. Then I try 'get token ID' and the cmd appears with the same text as before 'not recognised as an internal or external device'
Sent from my HTC One X using xda app-developers app
Craiglivesey94 said:
I put my phone in bootloader, then connected USB, then fastboot USB appears. Then I try 'get token ID' and the cmd appears with the same text as before 'not recognised as an internal or external device'
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I've PM'ed you
Craiglivesey94 said:
I put my phone in bootloader, then connected USB, then fastboot USB appears. Then I try 'get token ID' and the cmd appears with the same text as before 'not recognised as an internal or external device'
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Make sure that there aren't any spaces in the path to the toolkit.
Sent from my HTC One using Tapatalk 4
Hello folks, i am having trouble trying to get adb to recognize my device. Every time i try to do adb reboot, daemon starting etc... And then after it says device not found. I tried uninstalling and reinstalling the drivers for thehtc one m8 and yet it still doesnt work. Please help me as i want to gain s-off
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Are you using a pc running Windows 8. That was my problem. Worked fine on an old laptop running Windows 7
Sent from my HTC One_M8 using XDA Premium 4 mobile app
BubooBear said:
Hello folks, i am having trouble trying to get adb to recognize my device. Every time i try to do adb reboot, daemon starting etc... And then after it says device not found. I tried uninstalling and reinstalling the drivers for thehtc one m8 and yet it still doesnt work. Please help me as i want to gain s-off
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
same happened with me. It turned out there was a prompt on my M8's screen asking for permission for my computer to use USB debugging. I gave it access and adb was working fine.
I had the same problem on windows 8. I installed HTC sync and everything worked fine.
Make sure USB debugging is enabled.
When you connect your phone and use the 'adb devices' command for the 1st time your phone will give an USB debugging RSA prompt. Click ok and you will be good to go in windows 7. Just run the 'adb devices' command again (or click on the UP arrow on the KB, this will replicate the last typed command) to check it sees it.
Windows 8 - No idea
grentuu said:
Make sure USB debugging is enabled.
When you connect your phone and use the 'adb devices' command for the 1st time your phone will give an USB debugging RSA prompt. Click ok and you will be good to go in windows 7. Just run the 'adb devices' command again (or click on the UP arrow on the KB, this will replicate the last typed command) to check it sees it.
Windows 8 - No idea
Click to expand...
Click to collapse
I must have missed that prompt, is there a way for me to do anything that will have that prompt show up one more time? I am running windows 7.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
BubooBear said:
I must have missed that prompt, is there a way for me to do anything that will have that prompt show up one more time? I am running windows 7.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Turn off usb debugging. Give the phone a reboot.
Turn USB debugging on again and connect it to your PC again
Look at the phone It should come up again. Make sure it is set to 'always authorise'
Type adb devices = profit
grentuu said:
Turn off usb debugging. Give the phone a reboot.
Turn USB debugging on again and connect it to your PC again
Look at the phone It should come up again. Make sure it is set to 'always authorise'
Type adb devices = profit
Click to expand...
Click to collapse
I had the same issue on my Windows 8 pc.. I was able to rectify the adv device not found issue by going into device manager , clicking on the HTC one icon and manually installing the drivers by browsing through my computer and using my Nexus adb drivers and everything worked fine after that
Download htc sync, you'll need those drivers. Then follow grentuu's instructions.
umjammerlammy said:
Download htc sync, you'll need those drivers. Then follow grentuu's instructions.
Click to expand...
Click to collapse
Thanks a ton. I had just plugged my m8 in after a fresh win8.1 install and couldn't figure out why I could copy files but not see it under ADB after the adb google driver install.
Canadianreaper said:
Thanks a ton. I had just plugged my m8 in after a fresh win8.1 install and couldn't figure out why I could copy files but not see it under ADB after the adb google driver install.
Click to expand...
Click to collapse
Glad I could help!
I had the same problem using Windows 8.1. adb and fastboot were definitely installed correctly as I already used them for flashing other ROMs on my Nexus 7. The solution in my case was to download and install the HTC Sync Manager. After installing the hsm the adb and fastboot commands worked perfectly.
Best regards,
B.
So I'm trying to flash the L preview. I plug my n7 in and do adb devices and it shows up, I adb reboot bootloader and it boots into the boot loader, but while in it if I do adb devices nothing comes up and if I do the flash-all.bat it just stays stuck on waiting on device. And yes I have USB debugging, and just updated drivers and installed SDK fresh. This just seems odd.
Sent from my LG-D801 using xda premium
C-4Nati said:
So I'm trying to flash the L preview. I plug my n7 in and do adb devices and it shows up, I adb reboot bootloader and it boots into the boot loader, but while in it if I do adb devices nothing comes up and if I do the flash-all.bat it just stays stuck on waiting on device. And yes I have USB debugging, and just updated drivers and installed SDK fresh. This just seems odd.
Sent from my LG-D801 using xda premium
Click to expand...
Click to collapse
When you are in bootloader mode, the correct command to list devices is: fastboot devices
Let me know if that command gives you a device id.
If it does not, then you must get your drivers situated.
mdamaged said:
When you are in bootloader mode, the correct command to list devices is: fastboot devices
Let me know if that command gives you a device id.
If it does not, then you must get your drivers situated.
Click to expand...
Click to collapse
Well not working while using the flash-all.bat would still indicate it's not recognized in boot loader mode. Which is weird when it is while its on.
Sent from my LG-D801 using xda premium
Any ideas?
Sent from my LG-D801 using xda premium
C-4Nati said:
Any ideas?
Sent from my LG-D801 using xda premium
Click to expand...
Click to collapse
I already suggested what needs to be done, you need to get your drivers working correctly. There are different drivers for the different modes.
Here is what I did to get my N7 2013 recognized in every possible mode: http://forum.xda-developers.com/showthread.php?p=50253887#post50253887
Do you have a syncing program for your handset/tab installed?
If so I'd uninstall it as they tend to take over the USB when you plug your device in, changes the USB port com ID and only meant for an up and running system and not in bootloader/recovery/etc
As for an actual response as in an ID/model/etc using adb or fastboot I've never seen it shown when I've tried it even with official and unofficial drivers others have had responses with!! ..but not had any problems flashing except with a sync program on pc
(personally never use sync progs since then )
Bashing away at my HTC Desire C
I accidentally flashed a candykat ROM which was intended for my nexus 7 2013 and now it just boots and says in very tiny letters750)fastboot mode started in upper left hand corner of screen. I was able to reflash the recovery on there but there is no way to boot to it. I did make 2 backups though thank goodness. What can I do?
Sent from my Nexus 7 using XDA Premium 4 mobile app
willdiddy said:
I accidentally flashed a candykat ROM which was intended for my nexus 7 2013 and now it just boots and says in very tiny letters750)fastboot mode started in upper left hand corner of screen. I was able to reflash the recovery on there but there is no way to boot to it. I did make 2 backups though thank goodness. What can I do?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Plug in your phone to your computer, with the proper drivers installed and blah blah, then download ADB, navigate to the folder, hold shift and right click inside the folder and press "open command window here" and type "adb reboot recovery" to boot into your recovery. Hope this helps!
eBoody said:
Plug in your phone to your computer, with the proper drivers installed and blah blah, then download ADB, navigate to the folder, hold shift and right click inside the folder and press "open command window here" and type "adb reboot recovery" to boot into your recovery. Hope this helps!
Click to expand...
Click to collapse
When I try this I get the error message: adb server is out of date. killing... *daemon started I successfully* error: device not found
Sent from my Nexus 7 using XDA Premium 4 mobile app
I also have windows 8.1 installed and in device manager under ADB it shows: Fastboot interface (Google USB ID). I did install the proper lg g3 d851 driver
Sent from my Nexus 7 using XDA Premium 4 mobile app
willdiddy said:
I also have windows 8.1 installed and in device manager under ADB it shows: Fastboot interface (Google USB ID). I did install the proper lg g3 d851 driver
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Take a look at this thread. Never tried with LG but done it numerous times with my Samsungs.
http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
Well I fixed the problem just fine with this guide. Make sure you use the microusb cable that came with your G3. A box might pop up and say connection to server failed.....Try again in a moment, just move this box aside and let the program do its magic. Worked like a charm!!! Saved me fifty bucks on buying a new one.
willdiddy said:
Well I fixed the problem just fine with this guide. Make sure you use the microusb cable that came with your G3. A box might pop up and say connection to server failed.....Try again in a moment, just move this box aside and let the program do its magic. Worked like a charm!!! Saved me fifty bucks on buying a new one.
Click to expand...
Click to collapse
Glad it worked! :good: