I've been looking for hours but couldn't find anything which solves my problem, so here goes (pasted from Stack Exchange):
So, I'm really hoping that I haven't bricked my phone and that someone can help me figure out how to fix this.
I can't remember exactly the steps I took to mess it up so spectacularly, but they included trying to flash to the M2 snapshot of CyanogenMod 11 from a ViperOne ROM, relocking the bootloader, attempting to restore to a stock RUU (and failing because I accidentally downloaded an unsigned version), reUNlocking the bootloader, and formatting via TWRP.
Fastboot appears to recognise that the phone is plugged in (it reads FASTBOOT USB on the bootloader screen), and Windows 8 sees the device in Device Manager. However, when I attempt to do anything with ADB it returns error: device not found, so I can't use rebootRUU or push files to the /sdcard/ directory, and I have no ROMs to flash.
The bootloader screen reads:
Code:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.841.1
eMMC-boot 2048MB
Jun 21 2013,23:03:15.0
FASTBOOT USB
It also appears that I am able to use FastBoot to lock and unlock the bootloader using the unlock bin file I created earlier today, yet fastboot devices returns nothing and fastboot reboot returns < waiting for devices >.
Is there anything I can do short of using a USB-OTG cable to sideload a custom ROM?
I would be inconceivably grateful for any help which gets me closer to getting my phone working again. Thanks in advance!
brutalspoon said:
I've been looking for hours but couldn't find anything which solves my problem, so here goes (pasted from Stack Exchange):
So, I'm really hoping that I haven't bricked my phone and that someone can help me figure out how to fix this.
I can't remember exactly the steps I took to mess it up so spectacularly, but they included trying to flash to the M2 snapshot of CyanogenMod 11 from a ViperOne ROM, relocking the bootloader, attempting to restore to a stock RUU (and failing because I accidentally downloaded an unsigned version), reUNlocking the bootloader, and formatting via TWRP.
Fastboot appears to recognise that the phone is plugged in (it reads FASTBOOT USB on the bootloader screen), and Windows 8 sees the device in Device Manager. However, when I attempt to do anything with ADB it returns error: device not found, so I can't use rebootRUU or push files to the /sdcard/ directory, and I have no ROMs to flash.
The bootloader screen reads:
Code:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.841.1
eMMC-boot 2048MB
Jun 21 2013,23:03:15.0
FASTBOOT USB
It also appears that I am able to use FastBoot to lock and unlock the bootloader using the unlock bin file I created earlier today, yet fastboot devices returns nothing and fastboot reboot returns < waiting for devices >.
Is there anything I can do short of using a USB-OTG cable to sideload a custom ROM?
I would be inconceivably grateful for any help which gets me closer to getting my phone working again. Thanks in advance!
Click to expand...
Click to collapse
I've had some problems with the phone not being detected with Windows 8 and with the USB 3.0 due to the driver issue. However, it worked like a charm in Windows 7 and by using a regular 2.0 version.. Check this out and let know if the problem still happens
Hit Thanks if this helped you
haran_rulez said:
I've had some problems with the phone not being detected with Windows 8 and with the USB 3.0 due to the driver issue. However, it worked like a charm in Windows 7 and by using a regular 2.0 version.. Check this out and let know if the problem still happens
Hit Thanks if this helped you
Click to expand...
Click to collapse
Actually, I'm running Windows 8 in a VM on a MacBook Pro with USB 2.0 ports - which was more likely to be causing the problem, Windows 8 or USB 3?
I guess I could create a Windows 7 or XP VM and see if that fixes anything... I never had any luck getting adb/fastboot to work on OS X, so I don't know if it would be useful trying to make it work now.
brutalspoon said:
Actually, I'm running Windows 8 in a VM on a MacBook Pro with USB 2.0 ports - which was more likely to be causing the problem, Windows 8 or USB 3?
I guess I could create a Windows 7 or XP VM and see if that fixes anything... I never had any luck getting adb/fastboot to work on OS X, so I don't know if it would be useful trying to make it work now.
Click to expand...
Click to collapse
I'm sure you won't face these issues in Win 7... All the best...
Fixed it!
haran_rulez said:
I'm sure you won't face these issues in Win 7... All the best...
Click to expand...
Click to collapse
Actually, getting adb and fastboot up and running on OS X did seem to help - VMs and Windows 8 probably didn't help. Also, I went into recovery and did a few cycles of formatting the filesystem and rebooting into recovery again, and suddenly adb/fastboot were working again, so I've got CyanogenMod 11 up and running. It's hard to say what actually fixed it!
For anybody else who stumbles across this thread having the same problems I did, first do what haran_rulez said - make sure you're using a USB 2 port, check your cable and make sure it's not dodgy at all. If that doesn't work, try another computer. Don't do what I did and try to sort it through a VM - that's just silly!
TWRP seemed to be playing silly buggers with device formatting, too; try going to Wipe > Format Data and formatting everything before rebooting and trying adb/fastboot again - it might just fix it.
brutalspoon said:
Actually, getting adb and fastboot up and running on OS X did seem to help - VMs and Windows 8 probably didn't help. Also, I went into recovery and did a few cycles of formatting the filesystem and rebooting into recovery again, and suddenly adb/fastboot were working again, so I've got CyanogenMod 11 up and running. It's hard to say what actually fixed it!
For anybody else who stumbles across this thread having the same problems I did, first do what haran_rulez said - make sure you're using a USB 2 port, check your cable and make sure it's not dodgy at all. If that doesn't work, try another computer. Don't do what I did and try to sort it through a VM - that's just silly!
TWRP seemed to be playing silly buggers with device formatting, too; try going to Wipe > Format Data and formatting everything before rebooting and trying adb/fastboot again - it might just fix it.
Click to expand...
Click to collapse
Nice to see that it's fixed for you.. Good luck
Sent from my HTC One using xda app-developers app
Related
Hi All,
Need help. I installed the ICS ROM upgrade using the RUU from HTC dev on my wife's Incredible S and while the install process seemed to go well, when the phone booted up, the touchscreen and screen buttons were completely unresponsive (not laggy, it is completely frozen).
I have tried a factory reset from the hboot menu. The result is the same; the phone gets to the android home screen and connects to the cell network, but no touch screen or screen buttons working.
To make matters worse, it no longer connects to the PC via USB. The PC sees a device; calls it an "Android 1.0", but I can't interact with it. I have tried to force update the correct drivers, but no luck. HTC sync says there is no device connected; have uninstalled and reinstalled it several times. Have also tried a second computer.
I also tried to reinstall the ICS ROM from an SD card using fastboot with the PG32IMG.zip file. Again the install process seemed to go smoothly, but at the end no touchscreen.
I was going to try the stock gingerbread ROM using the SD card fastboot, but from what I've read, going backwards is not an option.
Both the cell provider (Virgin Canada) and HTC customer support were not able to help. The phone is past warranty and they want us to send it in for repairs.
Device is currently showing:
Locked
vivo pvt ship s-on rl
Hboot-2.03.0000
Radio-3831.19.00.19_M
emmc-boot
I've done a bunch of searching, but haven't been able to find anything quite like this. Any help would be greatly appreciated.
t2795 said:
Hi All,
Need help. I installed the ICS ROM upgrade using the RUU from HTC dev on my wife's Incredible S and while the install process seemed to go well, when the phone booted up, the touchscreen and screen buttons were completely unresponsive (not laggy, it is completely frozen).
I have tried a factory reset from the hboot menu. The result is the same; the phone gets to the android home screen and connects to the cell network, but no touch screen or screen buttons working.
To make matters worse, it no longer connects to the PC via USB. The PC sees a device; calls it an "Android 1.0", but I can't interact with it. I have tried to force update the correct drivers, but no luck. HTC sync says there is no device connected; have uninstalled and reinstalled it several times. Have also tried a second computer.
I also tried to reinstall the ICS ROM from an SD card using fastboot with the PG32IMG.zip file. Again the install process seemed to go smoothly, but at the end no touchscreen.
I was going to try the stock gingerbread ROM using the SD card fastboot, but from what I've read, going backwards is not an option.
Both the cell provider (Virgin Canada) and HTC customer support were not able to help. The phone is past warranty and they want us to send it in for repairs.
Device is currently showing:
Locked
vivo pvt ship s-on rl
Hboot-2.03.0000
Radio-3831.19.00.19_M
emmc-boot
I've done a bunch of searching, but haven't been able to find anything quite like this. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Can you provide a link to this RUU or the complete filename?
t2795 said:
Hi All,
Need help. I installed the ICS ROM upgrade using the RUU from HTC dev on my wife's Incredible S and while the install process seemed to go well, when the phone booted up, the touchscreen and screen buttons were completely unresponsive (not laggy, it is completely frozen).
I have tried a factory reset from the hboot menu. The result is the same; the phone gets to the android home screen and connects to the cell network, but no touch screen or screen buttons working.
To make matters worse, it no longer connects to the PC via USB. The PC sees a device; calls it an "Android 1.0", but I can't interact with it. I have tried to force update the correct drivers, but no luck. HTC sync says there is no device connected; have uninstalled and reinstalled it several times. Have also tried a second computer.
I also tried to reinstall the ICS ROM from an SD card using fastboot with the PG32IMG.zip file. Again the install process seemed to go smoothly, but at the end no touchscreen.
I was going to try the stock gingerbread ROM using the SD card fastboot, but from what I've read, going backwards is not an option.
Both the cell provider (Virgin Canada) and HTC customer support were not able to help. The phone is past warranty and they want us to send it in for repairs.
Device is currently showing:
Locked
vivo pvt ship s-on rl
Hboot-2.03.0000
Radio-3831.19.00.19_M
emmc-boot
I've done a bunch of searching, but haven't been able to find anything quite like this. Any help would be greatly appreciated.
Click to expand...
Click to collapse
it should be fine to run a gingerbread ruu. just dont go any earlier or you will have a paperweight!
Nonverbose said:
Can you provide a link to this RUU or the complete filename?
Click to expand...
Click to collapse
The filename was:
RUU_VIVO_ICS_35_S_HTC_WWE_4.14.405.2_Radio_20.76.30.0835U_3831.19.00.19_M_release_281519_signed.exe
I also tried the Gingerbread ROM via SD card, but it gave me an error saying it was an older version.
t2795 said:
The filename was:
RUU_VIVO_ICS_35_S_HTC_WWE_4.14.405.2_Radio_20.76.30.0835U_3831.19.00.19_M_release_281519_signed.exe
I also tried the Gingerbread ROM via SD card, but it gave me an error saying it was an older version.
Click to expand...
Click to collapse
You won't be able to run GB ruu without hboot downgrade, but that will require bootloader unlocking via htcdev site.
nlooooo said:
You won't be able to run GB ruu without hboot downgrade, but that will require bootloader unlocking via htcdev site.
Click to expand...
Click to collapse
Yes, but the problem in doing that is that I cannot get a useful connection to the PC. The bootloader unlocking method on the htcdev site seems to require a PC connection.
Try uninstalling HTC Sync and installing drivers provided on revolutionary installation instructions page.
With no connection to pc you will find it very difficult, if not impossible to rectify. is it a problem with your phone micro USB or your pc USB. I faced the same issue and found it was my micro connection (which also led to charging issues) got it replaced at phone repair shop cost me $80 au. Now everything works great.
Sent from my Incredible S using xda app-developers app
t2795 said:
The filename was:
RUU_VIVO_ICS_35_S_HTC_WWE_4.14.405.2_Radio_20.76.30.0835U_3831.19.00.19_M_release_281519_signed.exe
I also tried the Gingerbread ROM via SD card, but it gave me an error saying it was an older version.
Click to expand...
Click to collapse
You might have more luck with the Canadian variant. Run the ruu utility until it gets to the first screen, the phone doesn't need to be connected at this point. Open start menu on pc and type %temp% in the run/search bar. A temp window should appear. In this window search for rom.zip and copy the file to your desktop.
Rename rom.zip to PG32IMG.zip, place it on the root of your sdcard somehow (another phone or sdcard reader) insert back in phone and start phone into hboot (power + vol down) phone will scan and find the file and prompt install, accept and wait. After installation check your touchscreen and let us know how it went.
if this doesn't fix it, I think you might be looking at a hardware fault.
facing similar issue, just want to ask anyone having issue with ICS/JB, no matter what rom i flash, its still nt smooth
So I've trying for 2 days straight now to get anything work in fastboot on Windows 8.1 x64 and really am out of ideas...
Fastboot devices does nothing, fastboot oem get_identifier_token just waits for devices to show up.
I connect my HTC One on my USB 3.0 port and when it is in fastboot it shows up as My HTC in device manager.
I tried many drivers but nothing seems to work. Tried installing other usb 3.0 drivers, but no luck at all...
USB 2.0 gives device enumeration failed...
Here is some more info on my device:
S-OFF
HBOOT 1.54
RADIO 4A.17.3250.14
OpenDSP v31.120.274.0617
OS 2.24.401.8
Anybody can help me?
petemt said:
So I've trying for 2 days straight now to get anything work in fastboot on Windows 8.1 x64 and really am out of ideas...
Fastboot devices does nothing, fastboot oem get_identifier_token just waits for devices to show up.
I connect my HTC One on my USB 3.0 port and when it is in fastboot it shows up as My HTC in device manager.
I tried many drivers but nothing seems to work. Tried installing other usb 3.0 drivers, but no luck at all...
USB 2.0 gives device enumeration failed...
Here is some more info on my device:
S-OFF
HBOOT 1.54
RADIO 4A.17.3250.14
OpenDSP v31.120.274.0617
OS 2.24.401.8
Anybody can help me?
Click to expand...
Click to collapse
I have the same problem. Searchng for a solution since 2 month now.
same Problem here @ Win 8.1 64-bit
S-ON
HBOOT-1.44.0000
RADIO 4.A.14.3250.13
OpenDSP-v26.120.274.0202
Anyone has news?
Need HBOOT 1.55 so update to 4.3 and you'll be good to go
I got sinless 4.3. So Can you name a rom wich you are Sure that does?
Sent from my HTC One using Tapatalk
Also had the same problem, had to use the spare laptop.... Which unfortunately now been upgraded to 8.1 as well lol...
I've installed many 4.3 ROMs and I still have hboot 1.44, could you be more specific?
Sent from my HTC One using xda app-developers app
Found a Solution:
Change USB3.0 Driver from Microsoft to Intel's Driver following this instruction: http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
NOTE: If you've an PC with Intel Processor 4th Gen, you've to read the first comment of the Instruction and do what it's said.
after this, you'll get fastboot cmds run in bootloader.
kind regards
madejackson said:
Found a Solution:
Change USB3.0 Driver from Microsoft to Intel's Driver following this instruction: http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
NOTE: If you've an PC with Intel Processor 4th Gen, you've to read the first comment of the Instruction and do what it's said.
after this, you'll get fastboot cmds run in bootloader.
kind regards
Click to expand...
Click to collapse
While this potentially holds the solution, it's some serious-level ****. I tried this in an attempt to solve the exact same problem about a month ago, and I ended up reinstalling Windows. Because my USB drivers were all ****ed up, I was unable to pull files from the system, so it was a clean install, minus all my music and games and jazz. :/
I'm pretty sure I didn't do anything wrong, so I don't know what happened, but if you're going to follow the directions on the above thing, make sure you do exactly what the **** you're told. As a reminder: it never hurts to have a backup of your Windows install.
Also, it looks like the modified 4th-gen drivers (stock drivers won't install on > Win7) listed in the top comment are now out-of-date, with no replacement. You'll do exactly what I did if you try it on a Haswell CPU with the listed modified drivers. I'd currently consider it a dead end.
So, again, this is complicated. If you're here on XDA, it's assumed you know what you're doing, so maybe go ahead, but this was your warning.
I already gave that a shot, resulting in my USB port not working
Sent from my HTC One using Tapatalk
Zak Jones! said:
While this potentially holds the solution, it's some serious-level ****. I tried this in an attempt to solve the exact same problem about a month ago, and I ended up reinstalling Windows. Because my USB drivers were all ****ed up, I was unable to pull files from the system, so it was a clean install, minus all my music and games and jazz. :/
I'm pretty sure I didn't do anything wrong, so I don't know what happened, but if you're going to follow the directions on the above thing, make sure you do exactly what the **** you're told. As a reminder: it never hurts to have a backup of your Windows install.
Also, it looks like the modified 4th-gen drivers (stock drivers won't install on > Win7) listed in the top comment are now out-of-date, with no replacement. You'll do exactly what I did if you try it on a Haswell CPU with the listed modified drivers. I'd currently consider it a dead end.
So, again, this is complicated. If you're here on XDA, it's assumed you know what you're doing, so maybe go ahead, but this was your warning.
Click to expand...
Click to collapse
petemt said:
I already gave that a shot, resulting in my USB port not working
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I have a Lenovo Yoga 2 Pro --> 4th Gen Haswell i7-4500
Installing Driver following instruction went fine. I have access to my phone now.
Probably you've done something wrong.
I also can't flash any ROMS above 4.3... Still on HBoot 1.54
ADB does work though when the phone is booted so I really don't understand this.
Hi all, first of all let me say what a good site/forum/community and good work you been doing !! I tried everything i could to unlock the boot on my htc desire c . I can connect the phone to htc sync manager . then i turn off the phone and boot to bootloader , and windows/usb ports / htc drivers wont recognize the phone so i cant unlock the bootloader , tried the latest htc driver latest HTC Sync Manager . but seems i cant get the identifier token in anyway. In command line after do fastboot oem get_identifier_token i get "waiting for device" i get a message in task bar saying windows cant recognize this device.
Im new to this forum / but im usually good follow steps , idk what im doing wrong im doing my best . hope someone can help me get through this , i would love to have some good ROM's in this phone
Win 8.1 pro x64
Htc desire C
*** Locked ***
Golfu pvt ship s-on rl
Hboot- 1.31.0000
Radio-1.10.98.15
eMMC- Boot
Jul 12 2012
Sorry about my english and punctuation .
Thanks in advance
Uninstall sync manager (and possibly drivers - unsure but I would)
You only need the drivers to communicate with your handset, sync manager is blocking handset and waiting for a running system
Uninstall sync manager (+ drivers)
Install Only drivers for your handset
Once you're finished flashing/rooting/etc and you have your phone as you like/want it, by all means re-install sync manager but uninstall to reflash a ROM etc
Also check forums for best Windows 7/8 drivers (known to have problems)
Bashing away at my HTC Desire C
Hi i did all of that and didnt work win 8.1 just dont detect it . but i tryed in my brother computer with windows 7 and i done it i installed cyanogenmod. thank you for everything
Antagonist42 said:
Uninstall sync manager (and possibly drivers - unsure but I would)
You only need the drivers to communicate with your handset, sync manager is blocking handset and waiting for a running system
Uninstall sync manager (+ drivers)
Install Only drivers for your handset
Once you're finished flashing/rooting/etc and you have your phone as you like/want it, by all means re-install sync manager but uninstall to reflash a ROM etc
Also check forums for best Windows 7/8 drivers (known to have problems)
Bashing away at my HTC Desire C
Click to expand...
Click to collapse
My guess is the drivers for Win8 in that case
If all else fails WinXP as last resort for Windows.
Glad it helped
Bashing away at my HTC Desire C
I'd really suggest using Linux. I ran into the same problem, but it was easily fixed by puting "sudo" in front of my commands (sudo gives administrativne privilege on Linux). Maybe you should try running Command Prompt by right clicking it, then -> Run as Administrator?
It was the same when I was initially trying to root my phone, all the guides for Windows seemed exhaustively complicated and in the end they didn't work and somehow I ran into a Linux rooting guide and I did it in no time.
got the same problem in windows 8...got to get back to 7 :S problem solved
Hey there this is the usb problem fix for wind 8.1 just download the zip and do as instructed it's workin awesome
Cannot unlock HTC Desire C bootloader
Makerrr said:
Hey there this is the usb problem fix for wind 8.1 just download the zip and do as instructed it's workin awesome
Click to expand...
Click to collapse
Hello there I am new to this website but I hope I can get some help with this annoying issue. I have tried everything I have been on HTC Dev website and tried to unlock the bootloader but it keeps getting stuck on 'waiting for device' after I put the token command in which is 'fastboot oem get_identifier_token'. I have the latest drivers installed and am using a Windows 8.1 machine. All the information I can find from bootloader is this:
GOLFU PVT SHIP S-ON RL
HBOOT-1.28.0000
RADIO-1.19.98.02
eMMC-boot
May 17 2012, 16:198:28
I hope anyone will be able to help with this and hopefully point out something I could of missed.
supermario1995 said:
Hello there I am new to this website but I hope I can get some help with this annoying issue. I have tried everything I have been on HTC Dev website and tried to unlock the bootloader but it keeps getting stuck on 'waiting for device' after I put the token command in which is 'fastboot oem get_identifier_token'. I have the latest drivers installed and am using a Windows 8.1 machine. All the information I can find from bootloader is this:
GOLFU PVT SHIP S-ON RL
HBOOT-1.28.0000
RADIO-1.19.98.02
eMMC-boot
May 17 2012, 16:198:28
I hope anyone will be able to help with this and hopefully point out something I could of missed.
Click to expand...
Click to collapse
head over this thread http://forum.xda-developers.com/showthread.php?t=2598155 download the USB.zip from attachaments extact the x64 or x86 depending on your structure run franken-usb.bat as Administrator reboot your system and install adb drivers
i strongly suggest not using it. It messes with other usb devices for me.
How recent are your PC's?
Ensure your system has USB 2.0 available!!!
My guess is that part of the problem is the handset doesn't communicate well with USB 3.0, some things are basic as in 'what is it that's attached' 'the connected device needs driver "X" to use it' but on actual communication there's too much of a speed difference.
That's my guess anyway as doing the previous in my postings my system never had a problem with connected device
Sent from my B1-730HD using XDA Free mobile app
hi guys. i have another kind of problem. i tried to unlock the bootloader in htcdev.com . all the steps went well except the last one when i want to choose to unlock the bootloader. the power button at that step won't work and i can't do the last step. but if i want to choose NO it will work. plz help me. anyone knows what the problem is?
Hello guys,
Even though I am a member of this site for a few years, this is my second post.
Recently, I decided to root my HTC Desire 500. I am a newbie in this topic, ( even though I rooted 2-3 devices, but they were old, so I just used SuperOneClick or Z4Root) so I tried to google it, and found some pretty good guides, but I always faced problems. One guide what I was following is this one: http://forum.xda-developers.com/desire-500/general/how-to-root-install-cwm-twrp-install-t2804938
So first, I tried to unlock the bootloader. I headed to this site: http://www.htcdev.com/devcenter and followed the instructions. I installed the HTC sync as well. I turned off my phone, and launched the bootloader mode. The HTC sync popped up, and scanned my music, but in the left corner I saw a sign: No phone connected...
That was prety worrying for me, but after that, the Windows told me that it can't recognise the connected device. I continued anyway, downloaded the fastboot binary,but I got another error when I tried to run the "fastboot oem get_identifier_token" command, something like: the program can't launch because the AdbWinApi.dll is missing, then it just stopped working. I quickly grabbed the dll from the internet, and ran the command again, but I got another error message: <waiting for device>, and now I don't know how to continue. I tried plugging my phone in when it was turned on, and now everything recognised it, so somehow when it's turned off, the Windows can't identify it. USB debugging is turned on, and fastboot is turned off in the phone's settings. Some more info, that can be helpful: this is what I see in bootloader mode:
Code:
****LOCKED****
Z4U PVT SHIP S-ON RL
HBOOT-1.01.001
RADIO-14.08.36Q4.26
OS-1.10.401.3
eMMC-boot
Aug 1 2013,15:50:50.0
It's a single SIM version.
Maybe the android SDK is missing, as I later noticed, so I headed to this site: http://developer.android.com/sdk/index.html , and clicked on "Installing the SDK", but now I don't know which one should I install: http://i.gyazo.com/5aaf558bfceea91b15963ebaa2351368.png or maybe I have to download something from here? http://i.gyazo.com/221bab07354c3f60675cd3e492d15e65.png I have no idea...
As I told before, I am a beginner, so please be detailed when replying, and I am sorry for wasting your time guys if it's that easy, but I was unable to find the solution... I also have several other questions in this topic after solving the problem, so please stay in touch with me. Any help would be really appreciated.
even i faced the same prob...waiting to see if someone replies..
update: Hey bro, are you trying in windows 8 or 8.1? I was trying on the same. But now I tried with Windows 7 and it is successful. The issue here is when the phone is in fastboot mode windows 8 is unable to recognise the device. In windows 7 it does. try this,
Akhyll said:
even i faced the same prob...waiting to see if someone replies..
update: Hey bro, are you trying in windows 8 or 8.1? I was trying on the same. But now I tried with Windows 7 and it is successful. The issue here is when the phone is in fastboot mode windows 8 is unable to recognise the device. In windows 7 it does. try this,
Click to expand...
Click to collapse
I realised this as I tried to find a fix myself. Thanks for the update tho
Hello everyone! I would like to chnage the rom on my device, and for that I need to flash the kernel via fastboot/bootloader.
I have a problem. Windows sees my device as an unrecognized device. I don't think that the problem is in drivers because other devices such as Nexus 7 2012 and Xiaomi mi pad 2 work.
When I connect it to the PC on the phone's screen shows hboot usb plug but after several seconds windows says that this device is a unrecognized one and on the phone's screen it is hboot again.
Please help me
P.S unlocked, s-off, cwm recovery, ADB is working fine.
p.p.s I think the probleam appeared after I did the s-off thing
Are you sure your phone is HTC Desire C ?!?!?!
How did you S-OFF it?
If you have access to another computer/laptop, can you install drivers from scratch in there? I guess it's a driver issue (for this specific phone not your other phones!)
idoit said:
Are you sure your phone is HTC Desire C ?!?!?!
How did you S-OFF it?
If you have access to another computer/laptop, can you install drivers from scratch in there? I guess it's a driver issue (for this specific phone not your other phones!)
Click to expand...
Click to collapse
It is for sure a HTC Desire C. I would be very thankful if you send me those driver, or post a link for them.
I found the s-off instruction on 4pda.ru
photos of bootloader an the phone:
ht tps://i.img safe. org/0c90 c0f96e.jpg
ht tps://i.img safe. org/0c90 a81c6d.jpg
Please remove the spaces in links
Oh can you please send me the forum post from 4pda.ru that you followed to S-OFF your Desire C ? I don't understand Russian.
The HBOOT on my Desire C is different from the snapshots you sent:
GOLFU PVT SHIP S-ON RL
HBOOT-1.28.0000
RADIO-1.06.98.13M2
eMMC-boot
May 17 2012, 16:19:28
What I normally do (if you are on Windows), using System Restore, restore your computer back to a date before this happened. Then I connect my phone and let Windows come up asking for driver, go to Device Manager and choose the folder for generic adb drivers. What I have found working best for me is this: http://forum.xda-developers.com/showthread.php?t=2317790
idoit said:
Oh can you please send me the forum post from 4pda.ru that you followed to S-OFF your Desire C ? I don't understand Russian.
What I normally do (if you are on Windows), using System Restore, restore your computer back to a date before this happened. Then I connect my phone and let Windows come up asking for driver, go to Device Manager and choose the folder for generic adb drivers. What I have found working best for me is this: http://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
http:// 4pda.ru /forum/index.php ?showtopic=457424& st=1720#entry31041535 (S-off) remove spaces in link
The problem is that I have changed my pc since this happened. I have a fresh windows install, so this is also a reason that tells me the problem is not in the drivers.
Good news. I have installed lubuntu on a usb flash drive and booted from it. There i installed adb and fastboot drivers, and guess what? it started to work)) finally
I am glad to hear that.
The file soff-golfu.zip is not available anymore (posted by Creeplays). Do you have it?
Should I use rumrunner_proto_0.7.1.zip file. I'd appreciate if you can tell me how to S-Off this phone.
soff-golfu.zip is different from rumrunner_proto_0.7.1.zip ?
idoit said:
I am glad to hear that.
The file soff-golfu.zip is not available anymore (posted by Creeplays). Do you have it?
Should I use rumrunner_proto_0.7.1.zip file. I'd appreciate if you can tell me how to S-Off this phone.
soff-golfu.zip is different from rumrunner_proto_0.7.1.zip ?
Click to expand...
Click to collapse
htt ps:// drive.go ogle.com/file/d/0B9x8D7LzR J21NGNk dUVYMG9Uc WM/view?usp=sharing (soff-golfu.zip/ as usually remove spaces )
By the way why do you need s-off?
Thanks for the upload.
Oh I just want to play a bit more with this little phone. I don't know about you?, but I kind of like it to be honest.
idoit said:
Thanks for the upload.
Oh I just want to play a bit more with this little phone. I don't know about you?, but I kind of like it to be honest.
Click to expand...
Click to collapse
So do I. But It lags so much when the wifi or the browser is opened. By the way it happens on all the roms I have installed