Pretty screwed at the moment. I tried converting my M8 from GPe back to Sense, but somewhere along the lines I messed up, and now my PC can't find it through adb commands.
Phone has no OS on it for me to enable USB Debugging. It's got stock recovery with nothing on the internal or SD for me to flash, and since I can't get my PC to find it, I can't flash a custom recovery for any backups either.
I've tried un/reinstalling HTC drivers, Universal drivers, and some PDA drivers that was suggested elsewhere, and still no luck.
Any suggestions on what I'm missing or what I might be able to try here?
Fastboot (not adb) is more important to you at this point.
Connect the phone in bootloader-fastboot mode. Any response to the command:
fastboot devices
(should return your device serial number - don't post it here).
If so, flash the Sense firmware, then run the desire Sense RUU.
Related
hi,first post on this section . upgraded from the desire bravo,could do with some advice..
purchased a used dhd in good condition,changed housings etc,its running the latest htc 3.12.405.1 sense 3.0 android 2.3.5 .after a good search i realised i would have to downgrade to s-off etc.
my problem is i can't get into fast boot power down volume,pulled battery tried lots of times.
pc will not recognise dhd,installed drivers etc,should be able to sort that one out myself.
but i cant work out why i cant get into fastboot,the phone just restarts
thanks mark
Hi,
Download HTC Sync and install that, that contains all the required USB drivers needed.
As for getting into fastboot, have you disabled HTC "Fastboot"? Its in a setting somewhere. Possibly under Settings>Applications or Settings>Development. Make sure that is unticked.
If you take your battery out & reinsert, hold vol down then press power. That should do it for you. If not, enable USB Debugging and use adb to get into the bootloader with,
Code:
adb reboot bootloader
You will need the SDK or a thinned down adb package. Which you can grab from HERE.
You will need the USB drivers for that to work.
EDIT: Just re-read your post. If you have HTC Sync installed and you still cannot get it detected then there maybe an issue with either the handset or your computer. Check "Device Manager" when its plugged in to see if there is a conflict.
htc sinc was allready on pc from desire bravo,well just the drivers.have tried the htc fastboot uncheck earlier no good,re installed htc sinc as i thought it may be different for dhd,but its not.
pc will not pick up device,says drivers not installed.i know they are as the bravo worked fine.
i had read somewhere that unrooted dhd can be usb bricked,there is a fix by some french chap on here,but i cant do that because cant get into fastboot.
need to get into fastboot first i think,to see whats what,device could allready be s-off dont know.
strange
edit: volume button was not working correctly lol, s-on,now to sort out the drivers,downgrade and flash a nice rom
I made a bizare mistake trying to flash mod for menu button on odexed htc stock rom. Now I am stucked on HTC ONE logo.Device is unlocked by htcdev.com. I can flash/access custom recovery through fastboot but I have nothing on sdcard of the device. Also I am having problems with adb recognizing the device. I have tried all the currently available recovery images and in only one (Doom version) there is an option to mount usb mass storage but the computer (Win7 x86, htc drivers) doesn`t recognize it. Tried to flash Stock RUU, got Unknown Error 155.
Does anyone have an idea how to make it work or at least with adb conectivity problem, mount of usb storage... anything that might help?
Thank you all in advance
UPDATEroblem solved, the trick was to relock the bootloader in order to install stock RUU. BTW, I am trying to resolve this for 2 days, and i have found the solution on this same forum (that I searched at least 1.000.000 times) only couple of minutes after posting the problem.
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 have an HTC One M8 by T-Mobile, running the latest firmware, unlocked, rooted and on Android 5.0 Lollipop with the stock recovery. (I put the stock recovery back on because I had no need for the custom at the time and charging would bring me through the recovery and be real annoying).
I had no problem doing all of this but now (a few weeks later) I need to get the custom recovery back on in order to flash a new ROM.
Problem is, I'm connecting my phone to my computer and I can't get ADB to connect, HTC Sync Manager shows there's no device connected and windows explorer only shows a new CD Drive connected and mounted on (F that doesn't work and does not act as a storage platform for my phone.
What I have tried:
Disabling USB Debugging
Restarting Phone
Re-enabling USB Debugging
Un-installing HTC Sync Manager
Force installing "androidusb.INF"
uninstalling HTC Sync Manager, unplugging phone, disabling usb debugging, turning off phone and then going back through again, installing, plugging in turning on and enabling.
Really puzzled here, need to connect to ADB to flash custom recovery to go back to my stock ROM.
Try using the generic Android MTP drivers in Device manager. Of course you could also check all the basics as well.
Try a different port or a different cable. Try to kill the adb server and restart it. Can also try revoking the USB permissions and accepting again when prompted on the device.
Though you don't really need adb to flash the recovery, it needs to work in Fastboot mode. ADB will only work in a running OS or in a recovery, fastboot of course from fastboot mode, which is what you'll need in order to flash the recovery. You won't need USB debugging enabled for it either.
Try some of the stuff above, especially if maybe it's a cable or port issue.
I realize you may find a solution before even considering the option below ⬇
http://forum.xda-developers.com/showthread.php?t=2965030
If you have an extra rooted device and get the cable coming you will never have to worry about troubleshooting drivers again considering after an ruu or a conversion you will go through the possible issues of drivers more than once
I've changed my CID,MID,flashed recovery with this method.
Being S-OFF I've not needed to try an ruu through ruu mode but would guarantee it will do the job
I just bought a new computer yesterday, after installing the lightweight adb/fastboot program to my dell inspiron windows 8.1 laptop. I realized when I try to see the devices connected to adb by the command : adb devices, the only that pops up is list of devices attached, but show nothing. Here's the guide I followed http://forum.xda-developers.com/showthread.php?t=2778239
I'm guessing it has something to do with the drivers.....any help appreciated......
Here's the link I used to installed minimal adb and fastboot http://forum.xda-developers.com/showthread.php?t=2317790
Try uninstalling HTC Sync and any HTC drivers, then try to re-install, and see if that helps.
If no, uninstall any HTC software and drivers. Connect phone, go to Device Manager, and see if the device shows up. If so, select the option to manually select drivers (ignore any prompts to automatically install HTC Sync, etc.) and pick the Generic Android MTP drivers.
See if that works, although Win 8.1 has been known to be more problematic connecting to this device than previous Win builds.
Well I finally got it to work..I never installed the HTC sync software. I found a good link of compatible drivers for my 8.1. I didn't realize the phone had to be in bootloader mode to use fastboot commands though. That's a new thing forbme. If I remember correctly, I could use fastboot commands while the android was in its GUI/ROM format...
I've already switched cid yo gpe cod, but I'm probably going yo switch to dev edition
jxcorex28 said:
Well I finally got it to work..I never installed the HTC sync software. I found a good link of compatible drivers for my 8.1. I didn't realize the phone had to be in bootloader mode to use fastboot commands though. That's a new thing forbme. If I remember correctly, I could use fastboot commands while the android was in its GUI/ROM format...
Click to expand...
Click to collapse
Fastboot commands only work in fastboot mode. Its always been this way.
adb commands work in the OS or recovery, but not in bootloader or fastboot.
For some reason I was thinking the opposite...god, I'm retarded. I went ahead,and downloaded the entire SDK anyhow. Everything's up to speed