Fastboot devices won't show anything etc..
I am trying to unlock the phone.
I don't have an OS etc. and also have formatted my PC, since the last time I was able to detect my phone on fastboot.
I have tried installing drivers on windows but it won't change anything (I have one more HTC M9 which will be detected by fastboot)
Doesn't get detected on ubuntu too...
i was able to find *hard* an OTA that works.
turned out to be a hardware issue.
Related
Hello all!
I have a major, major, problem. Last night I wanted to flash a new ROM, so I had everything wiped from my sdcard so it will be like new again. Sadly, I was retarded enough to also do a wipe on /system. Now there is no Android OS loaded on my phone anymore and no ROMs on my internal sdcard to flash it.
The phone would boot up and will be stuck on the screen with the white Google logo and the white unlocked lock.
I am still able to boot into Download mode, Fastboot mode and CWM. The bootloader is also unlocked.
The problem is that none of my PCs and Laptops would recognize my phone, not even trying numerous tutorials and reading different similar threads.
http://forum.xda-developers.com/showthread.php?t=1760787
http://forum.xda-developers.com/showthread.php?t=1869380
http://forum.xda-developers.com/showthread.php?t=1379875
http://forum.xda-developers.com/showthread.php?t=2370684
http://forum.xda-developers.com/showthread.php?t=1529058
http://forum.xda-developers.com/showthread.php?t=1777593
Also Odin and GNEX Toolkit doesn't see that my device is plugged in, both in Fastboot mode and Download mode, so I cannot flash with that either.
I hope someone had experienced the same problem or knows a solution to my problem.
Thanks in advance!
you have a driver problem. you need to uninstall your drivers and reinstall them.
So normally my PC would detect my phone even without it having any data or OS on it?
Could you maybe point out for me what kind of drivers I actually need? I have tried so many I got really confused.
iKaosTony said:
So normally my PC would detect my phone even without it having any data or OS on it?
Could you maybe point out for me what kind of drivers I actually need? I have tried so many I got really confused.
Click to expand...
Click to collapse
Focus on getting the correct fastboot drivers installed, and try to get your computer to recognize the phone when you type "fastboot devices" while connected via USB.
Flash a stock image from Google in fastboot mode. Boot into it at least once in order to regenerate the internal storage partition, before futzing around with custom recovery, root and new ROMS etc. If you flash CWM/TWRP without first booting once into the OS, you may be unable to write files to internal storage hence blocking any further progress.
I have tried almost everything to get the drivers installed on all the PCs I have at home, non of them is regocnizing my device.
tried it on both Windows 7 64Bit and Windows XP 32Bit.
Is my warrenty void if the bootloader is unlocked?
iKaosTony said:
I have tried almost everything to get the drivers installed on all the PCs I have at home, non of them is regocnizing my device.
tried it on both Windows 7 64Bit and Windows XP 32Bit.
Is my warrenty void if the bootloader is unlocked?
Click to expand...
Click to collapse
You're holding it wrong. Either that or your USB port/USB cable has died.
Hey guys,
So, I tried to turn my T-Mobile into a GPE. Everything went OK, pushed the RUU - and it hanged for a long time, so I quit out. Tried pushing it again, ADB not detecting the phone anymore - reinstalled drivers, rebooted everything - phone detected on pc as "My HTC", still no device detected in ADB. Rebooting the phone leads to the white HTC screen, booting into bootloader works but it's black for some reason, and I'm unable to boot into recovery - The OS text is red and reads "OS-3.32.531.2 (2.12.1700.1)". I've been trying to look for a solution for the past couple of hours but all the solutions require ADB to work, and all the solutions to get ADB to work are not solving it, so at this point I'm kinda stuck.
Any and all help would be appreciated greatly.
Thanks in advance!
I don't know if there's a t-mobile ruu available but if so, you can try and run that. I would simulate the battery pull first and then see if it recognizes it. From what you described for your os, mine would show that during the process of upgrading firmware
There is a T-mobile ruu in T-mobile one m8 general
Is it possible to run an RUU when the PC doesn't recognize the device properly?
Salabrin said:
Is it possible to run an RUU when the PC doesn't recognize the device properly?
Click to expand...
Click to collapse
Nope. It uses adb/fastboot.
Try uninstalling all HTC Sync and HTC drivers. Then plug the phone, go to Device Manager, find the device and select the option to manually select a driver, then pick Generic MTP Android Device (or something like that).
Also, bootloader screen on GPE is supposed to be black.
So I ran an RUU, it gives me an image error - I changed the CID earlier to install GPE, is that what might be causing the issue? If so, is there a way to change the CID without adb(Still can't get it to detect the phone)?
I'm using a windows 7 laptop with the normal drivers installed, and i have recently worked on an htc m9 and an m8. adb works fine on all my other devices. i reboot to bootloader and the computer instantly detects the connection and fastboot works. as soon as i boot into twrp, the usb disconnected sound goes off, and there is no mtp or adb. same thing with the os (newest stock system image). what the hell is going on?
Sieger179 said:
I'm using a windows 7 laptop with the normal drivers installed, and i have recently worked on an htc m9 and an m8. adb works fine on all my other devices. i reboot to bootloader and the computer instantly detects the connection and fastboot works. as soon as i boot into twrp, the usb disconnected sound goes off, and there is no mtp or adb. same thing with the os (newest stock system image). what the hell is going on?
Click to expand...
Click to collapse
can you confirm that "fastboot devices" returns your unit's serial number?
while "an htc m9 and an m8" work you still need Nexus-specific driver
please quote the USB's VID/PID from W7 device manager while in TWRP and/or OS
alternatively, post UsbTreeView_report
yes, fastboot works fine. i had to reflash the newest system image several times while trying to figure out why the tablet kept bootlooping after deleting bloatware off of the system partition (the google app doesn't like to be frozen or deleted anymore). the problem is that the n7 isn't even detected via USB outside of the bootloader. I'm assuming that the proper nexus driver is installed, but i cant just "update driver" with the official google drivers, because the tablet isn't detected by windows.
Hello,
Ever since the latest oxygen os update, my device got wiped from it's root and twrp. And for the past week when I have been trying to reroot it (w/ the bootloader unlocked) it won't even bother to detect the devices. I have tried reinstalling the drivers, using and different port, fasboot.exe, rebooting my pc, etc but nothing is working. Also, it detects it as an ADB device.
I really need this to be fixed asap as I will be sending my device for a screen repair and will loose all my data if I don't root my device and use titanium backup.
~ ronaldonater.
I have the same issue and am curious how this is fixed. I have Windows 10 and the oneplus three. ADB recognizes device and "adb reboot bootloader" reboots the phone into bootloader. Then "fastboot devices" just says searching for devices. I am tired of having to use my widows 7 laptop each time. Any help would be greatly appreciated.
My phone not recognised on pc. Not even on twrp. I reinstaled drivers, adb..., nothing. Then i tryied on pc at work. Booom! it works. When I arrived home i've reinstaled windows on my laptop. 100% works.
had the very same issue. the phone would detect properly on my work laptop running Win 7 but wouldn't recognise on my home PC running Win10. Tried every ADB tool and driver available out there. But nothing seemed to work.
Problem is with driver conflicts.
Then tried the age old method of factory reseting my PC, installed Minimal ADB tool and voila!!!
everything started like a charm.
First of all go into Windows drivrs and select hidden drivers and delete your entire driver history for that machine and reboot, then connect your phone whilst it's booted up so it can install.
Connect phone in fastboot and let it install. After this you need to manually update the driver for the phone unless it's already showing "android bootloader interface" in device manager. Finally check over android SDK so it's up to date and you'll be good to go.
I've been researching and trying to sort this out on my own for a while now. I've turned up nothing, so I figured I'd ask for some help. I'll try to provide as much information as possible here.
I was attempting to unlock and root my Razer Phone from my Windows PC. I plugged it in and had it recognized over ADB with no issue. I sent "adb reboot bootloader" to start things off. Once it was in download mode, I sent the "fastboot -i 0x1532 devices" command to make sure it was recognized. It wasn't. I checked devices manager, and sure enough, it was not picking up the Google driver that every other device I own works with. I attempted to update the driver manually by pointing it to the inf file. It gave me an error stating that the driver is not designed to work with 64-bit Windows. I found that odd, as this is the exact same driver that I've used with my other devices for this stuff. I plugged in my HTC 10, since that was nearby. It was recognized via fastboot like it always was. Same cable I was using with the Razer and everything.
I booted to Linux Mint on the same machine and tried the same stuff. It would pick up the Razer only in fastboot, but not ADB. In fastboot, I could detect it with "fastboot -i 0x1532 devices", and it showed up just fine. When I attempted to run "fastboot -i 0x1532 flashing unlock" it just gave me the fastboot command reference list. (I don't have a screenshot, but it looked like this, in case you're unsure what I am referring to.) I rebooted back to the system and double checked that I had checked "Enable OEM Unlock", and I had done that already. I double checked everything with my HTC 10, and again, it all works fine on the HTC 10. ADB and fastboot are both recognized correctly on Linux.
So armed with this information, I moved over to my Linux server. I used a different cable this time, and got a similar result. The Razer phone was recognized over ADB and I was able to get into fastboot. Once there, it was detected with the fastboot devices command. I attempted to run the unlock command, and again was presented with the fastboot reference list as before. Double checked with the HTC 10, and all was workign fine with that device.
Does anyone have any ideas, or is it possible that it's the Razer phone that's the problem? I may have access to a Mac laptop later on, and I could attempt this from there, but this is getting nuts. I don't think I've ever had this much trouble getting into a device before.
Yeah I had this as well, basically you may have the latest drivers but are missing the latest adb/Fastboot executables. Apparently they have changed a few commands in the newer one and that way of unlocking isn't in the old version. Just google for the adb/Fastboot package from the Google site, can remember the exact name but it was the first hit on Google. I just extracted the whole zip to a directory and used it right from there. The reason you are getting the help screen from Fastboot is cause for that version at least, your giving it an illegal command.
I got the same problem till I put my usb in a usb 2.0 in the back of the pc in a highlight usb port witch I read after on Asus Website that suppose to charge your phone if you turn off your pc so basically a always on usb. Also I managed to unlock and brick my device only with one cable I tried 4 cables none of them worked .so for you to keep In mind
Try different cables
Try usb 2.0
Try driver from twrp for razer phone thread that worked for me
Seems to be an ongoing issue for me on my main desktop. I grabbed my old development laptop out of the closet, booted it up, and I was able to get everything recognized and working. I tried doing some more work this morning on my desktop and noticed that I'm having driver issues elsewhere, so it seems to be an issue with this machine. I'm still not sure why the Linux installation on the same machine was exhibiting the same issue, though.