Database Info

[Q] Desire S USB Brick

Hi all,
I have a friend and he came to me with a problem with his "Desire S" that I assume as "USB Brick". Here's the symptoms:
When I plugged into any computer, the phone doesn't come out with options about Disk Drive, HTC Sync, USB Teethering, nor Internet Pass-through, but just charge only. I did UNCHECK the remember option tick. The phone just charge
I go to bootloader:
instead of normal "fastboot usb" I get only "fastboot AC". The phone just charge.
The phone itself is fine: I can use card reader to put zip files into the sdcard and flash in recovery etc. But as i said fastboot usb doesn't detect, and adb push of course doesn't work as well.
USB Debugging is checked, "fast boot" in Menu>settings>power is unchecked.
from what I read across in the internet I'm positive that the issue I'm dealing here is USB brick.
So here's my question: Anyone faces the same problem and have fix for it?

have you tried flashing a different rom ?

DuTY09 said:
have you tried flashing a different rom ?
Click to expand...
Click to collapse
yea. possible 90% of all the roms out there. lol. Thanks for helping

ultimatepichu said:
yea. possible 90% of all the roms out there. lol. Thanks for helping
Click to expand...
Click to collapse
and you get the same results on every rom ?

DuTY09 said:
and you get the same results on every rom ?
Click to expand...
Click to collapse
yup all has the same result.
it's similar to USB bricking issues for the Desire. Just that their fix works on their phone but not here. :/

a google search found this http://androidforums.com/htc-desire-s/458357-solved-usb-bricked.html not sure if will help but you never no. if not have you tried flashing a ruu.

DuTY09 said:
a google search found this http://androidforums.com/htc-desire-s/458357-solved-usb-bricked.html not sure if will help but you never no. if not have you tried flashing a ruu.
Click to expand...
Click to collapse
i saw that as well. the only problem is that flashing ruu requires fastboot no? (running the .exe file from pc which the phone is connected)
That's the part where mine can't work. Anything that must be done from comp doesn't work.
Thanks!

ultimatepichu said:
i saw that as well. the only problem is that flashing ruu requires fastboot no? (running the .exe file from pc which the phone is connected)
That's the part where mine can't work. Anything that must be done from comp doesn't work.
Thanks!
Click to expand...
Click to collapse
Im not sure what to do then mate but good luck in your ventures and hope you sort it

Why are you trying to solve HW problem with SW?
I don't know what is "USB brick", but there's no such thing. While you can screw up USB access in the OS, there's no way you can screw it up in the bootloader. If you read well and put attention, you'll see that all "USB brick" threads in Desire were in OS, and fastboot worked. The most likely reason for USB not working in fastboot is physical - one of the USB pins disconnected, either bent inside the microUSB socket of the phone (most likely), or broke off the main board (less likely). So the required fix is physical as well.

Jack_R1 said:
Why are you trying to solve HW problem with SW?
I don't know what is "USB brick", but there's no such thing. While you can screw up USB access in the OS, there's no way you can screw it up in the bootloader. If you read well and put attention, you'll see that all "USB brick" threads in Desire were in OS, and fastboot worked. The most likely reason for USB not working in fastboot is physical - one of the USB pins disconnected, either bent inside the microUSB socket of the phone (most likely), or broke off the main board (less likely). So the required fix is physical as well.
Click to expand...
Click to collapse
Okay thanks, as I've said I don't know much about this issue either, and I thought it's like the common issues faced in Desire thread.
From the outward look it seems to me that the pins are fine. So i guess it is the pin on the mainboard got disconnected?
if so, is it possible for me to return to stock from this stage?

I guess you want to return your phone under warranty. You can try to flash the stock ROM through creating and flashing PB99IMG.ZIP (google it to see what it is and what it does - it's a file from SD card that is automatically flashed by HBOOT).
If you have no warranty - I'd suggest taking it to the nearest decent phone lab. If I'm not mistaken, the price for fixing will be low.
The pins might look fine, but one of the 5 might not be protruding enough to touch the plug pins.

Just to check some obvious things
Have you tried more than one PC?
Have you tried more than one USB cable?
Did you ever instal HTC drivers? You should find HTC sync exe in root of sd card
And just to correct a possible typo in the post above
- rename it to "PG88IMG.zip" (case sensitive)
- put it on the root of your SD card
- reboot into hboot and wait.
wyped form ym Dersie S unsig XAD Permuim

Jack_R1 said:
I guess you want to return your phone under warranty. You can try to flash the stock ROM through creating and flashing PB99IMG.ZIP (google it to see what it is and what it does - it's a file from SD card that is automatically flashed by HBOOT).
If you have no warranty - I'd suggest taking it to the nearest decent phone lab. If I'm not mistaken, the price for fixing will be low.
The pins might look fine, but one of the 5 might not be protruding enough to touch the plug pins.
Click to expand...
Click to collapse
Sadly the warranty expired not long time ago. :S Okay, I'll tell him to take to the nearest phone lab.
ben_pyett said:
Just to check some obvious things
Have you tried more than one PC?
Have you tried more than one USB cable?
Did you ever instal HTC drivers? You should find HTC sync exe in root of sd card
And just to correct a possible typo in the post above
- rename it to "PG88IMG.zip" (case sensitive)
- put it on the root of your SD card
- reboot into hboot and wait.
wyped form ym Dersie S unsig XAD Permuim
Click to expand...
Click to collapse
Tried on both his and my laptop. My DHD works fine with my comp and my cable so it's definitely not the cable problem. As for drivers, it should make sound when the phone is plugged in but it's not. And if my DHD works, I don't see any reason why the DS can't.
And thanks for more clarification about flashing the PG88IMG.zip in hboot

have had the same problem with my dhd. The problem seems to be intermittent on my phone, in that i got it working a few weeks ago by following the suggestions for the desire usb brick problem.(yes it did work for desire hd too)
By this i mean after numerous tries i got my laptop to be recognized at least in my computer(even though the sd card would not show)After
i used sdk tools and command promt and entered:-
fastboot oem eraseconfig
fastboot oem enableqxdm 0
fastboot oem boot
in that order.
After this my dhd mounted fine in 2 laptops at home and one pc
However about 2 days ago its has just stopped being rexcognized by my laptop or pc again,I have tried several times over the last few days but nothing works
I am convinced now it is an intermittent h/w propblem,
I am now using my phone explorer to access the sd card over wi fi so i don't have to remove it and insert it in laptop sd slot.

If the phone is recognized by PC in fastboot mode, and phone screen shows "FASTBOOT USB" - it isn't a HW problem.
If the phone isn't recognized in fastboot mode - it is a HW problem.
This is a simple and 100% way to distinguish between so-called "USB bricks" and HW failure of USB slot / one of the USB lines.

My phone does show every time in fastboot usb , but if i send a command via adb get 'waiting for device'.
However as I said in my previous post it was connecting every time a few days ago on 2 laptops and 1 pc.
Nothing has changed on the phone or the laptops since but now it has stopped responding again. It will not connect on laptop with or without using adb
I am going to try some different roms over the next few days, currently using Leedroid 5.1.1, but i am siick of spending hours and hours on it.
I think I can live with using my phone explore over wi fi(although its slower) and if I do need to copy something faster on or off the sd card, I unmount it and us it on my laptop slot with and SD adaptor

Fastboot and ADB are TWO DIFFERENT ENTITIES.
You can't send ADB command when in fastboot.
You can't send fastboot command when in ADB.
To have ADB functional, you need the kernel to be loaded properly and at least start of Android boot.
To have fastboot functional, all you need to do is reboot to bootloader.

Jack_R1 thanks for the info.
I get waiting for device in fastboot usb mode and if I try adb commands with phone booted its no use because the pc or laptop does not even see the phone in device manager

If you get "waiting for device" - make sure all the drivers are installed in Windows. Look in Device Manager, see if you can find "Android bootloader" or "Android 1.0" device.
If there's none - you might have a HW problem on your hands.

I'm sure its a harware problem, but i have no problem charging , either from mains or usb from laptop or pc & sd card card works fine within phone.
Things I have tried on 2 laptops and 1 pc:-
uninstalled /reinstalled htc drivers and adb drivers
uninstalled htc sync totally and installed drivers only from Ace hack kit tools folder
tried different roms(gingerbread and ICS)
went back to stock rom 1.32
After trying all the above the phone is not recognized in laptop/pc device manager
I've decide the next phone I have will be one with 16gb or 32gb internal memory which is plenty, no need for sd card lol

Phone wont connect

Hi guys
Desire S.
Unrooted, no custom recovery, basically everything default.
HBoot 2.00.0002
.
To root, i need the 0.98 version.
Using HTCdev.com, i tried to unlock, but at step 5, where i should type fastboot oem get_identifier_token, the phone doesnt come up at all, and cmd just continues to wait for device.
Before you ask, I HAVE (i hope) followed all steps.
This includes updating drivers manually, using htc sync (latest and older versions), swapping usb port and cable, reunzipping adb and fastboot material from other sources, and reading for a decent number of hours throughout xda and other external forums and guides.
But there is still no success.
Anyone help please? I don't just want fast, "get it working for me" type answers, but actually want to know why it refuses to greet me!
Cheers
BTW, i'm on a windows 8.1 laptop, and have updated the relevant drivers, still to no avail.

InV15iblefrog said:
Hi guys
Desire S.
Unrooted, no custom recovery, basically everything default.
HBoot 2.00.0002
.
To root, i need the 0.98 version.
Using HTCdev.com, i tried to unlock, but at step 5, where i should type fastboot oem get_identifier_token, the phone doesnt come up at all, and cmd just continues to wait for device.
Before you ask, I HAVE (i hope) followed all steps.
This includes updating drivers manually, using htc sync (latest and older versions), swapping usb port and cable, reunzipping adb and fastboot material from other sources, and reading for a decent number of hours throughout xda and other external forums and guides.
But there is still no success.
Anyone help please? I don't just want fast, "get it working for me" type answers, but actually want to know why it refuses to greet me!
Cheers
BTW, i'm on a windows 8.1 laptop, and have updated the relevant drivers, still to no avail.
Click to expand...
Click to collapse
your phone must be in FASTBOOT bootloader mode..not in the HOME of your ROM..
if you don't wan to turn off your phone first and pressing volume down + power to go to bootloader..then you can using a adb command on cmd while your phone is still in the HOME of your ROM.. type "adb reboot bootloader" then select "FASTBOOT" now you can type "fastboot oem get_identifier_token"
don't forget to disabled Fast boot mode and enable USB Debuging first from the system settings and just connect your phone to pc as charge mode..
hope this help..

Sorry mate. Tried that before your post though.
However the person for whom I was doing this no longer needs it doing, and plans for a newer device, so I no longer have this device available. Thus, i thanked you, since it was a cue for me to mention that.
Cheers.

This model of HTC is died

HTC ONE S (Ville C2). Cannot access the bootloader

Hi all, firstly i'll state that i've searched for this issue, been through the stickies and cannot find a solution for my problem:
I currently have an HTC One S (Ville C2) with the unofficial CM 11 Kitkat using the 3.4 kernel (phone is S-ON). I've had it a while and have been using custom roms with no issues, until now.
Yesterday my phone ran out of battery. Upon charging it will instantly boot to recovery (TWRP 2.6.3.0 with SE Linux support) without showing the HBOOT or in fact allowing me to hold power + volume down to access it, it just seems like it is not there anymore. I am also unable to access the phone from my computer to allow me to use fastboot adb or anything.
I have the latest HTC sync, android SDK, adb drivers but nothing will allow the computer to see my phone with either adb sideload or mounting the sdcard.as USB mass storage.
I guess i have 2 issues:
1) accessing the bootloader to use fastboot as it is S-ON therefore fixing the busted ROM
2) accessing the phone via a computer to fix the bootloader or copy any files to the phone for fixing
If anyone is able to help it would be much appreciated.
Thanks

[Q] AT&T HTC One X stuck in boot loop & usb connection not recognized by pc

Hello guys,
So I have an unlocked, unroot AT&T HTC One X, running stock rom JB 4.1.2 & Sense 4. The other day I was just using it when all of a sudden the phone froze & stop responding. I pressed and held the power button, trying to reset it. Ever since then, it had been stuck in a boot loop ("HTC -quietly brilliant" appeared, then reboot). I did not have any recovery like TWRP installed or anything similar. When I tried to enter HBoot, this is what I get"
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012,18:37:14:-1
and a bunch of options as usual. I tried everything from factory reset, clear storage, to recovery, but nothing works. I tried fastboot then install the RUU, but when I plug the phone in the USB port, it is not recognized by my pc. When I opened cmd and type "fastboot device", it says <waiting for device> and nothing happened.I have already installed HTC Sync Manager and the driver, but the problem is still there. Can anyone please help me? I'm a total noob and don't know what to do now. I just want to wipe everything clean and return it to stock.
Any help would be greatly appreciated. Thanks!

dxbach12 said:
Hello guys,
So I have an unlocked, unroot AT&T HTC One X, running stock rom JB 4.1.2 & Sense 4. The other day I was just using it when all of a sudden the phone froze & stop responding. I pressed and held the power button, trying to reset it. Ever since then, it had been stuck in a boot loop ("HTC -quietly brilliant" appeared, then reboot). I did not have any recovery like TWRP installed or anything similar. When I tried to enter HBoot, this is what I get"
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012,18:37:14:-1
and a bunch of options as usual. I tried everything from factory reset, clear storage, to recovery, but nothing works. I tried fastboot then install the RUU, but when I plug the phone in the USB port, it is not recognized by my pc. When I opened cmd and type "fastboot device", it says <waiting for device> and nothing happened.I have already installed HTC Sync Manager and the driver, but the problem is still there. Can anyone please help me? I'm a total noob and don't know what to do now. I just want to wipe everything clean and return it to stock.
Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
Are you sure the device is unlocked? It says locked in your bootloader screen. Did you perform a factory reset from the bootloader? That causes the sd card to become corrupt on modified devices, so if you've done that you've created another problem for yourself. Whatever you do, absolutely do not run an RUU, you'll brick your phone. S-on + SuperCID + jb RUU = brick, that's assuming your phone is modified like you say, but it isn't worth the risk. What happens when you enter recovery? And did you have fastboot working previously or have you installed it since this happened?
Sent from my Evita

timmaaa said:
Are you sure the device is unlocked? It says locked in your bootloader screen. Did you perform a factory reset from the bootloader? That causes the sd card to become corrupt on modified devices, so if you've done that you've created another problem for yourself. Whatever you do, absolutely do not run an RUU, you'll brick your phone. S-on + SuperCID + jb RUU = brick, that's assuming your phone is modified like you say, but it isn't worth the risk. What happens when you enter recovery? And did you have fastboot working previously or have you installed it since this happened?
Sent from my Evita
Click to expand...
Click to collapse
My bad, I mean the device is sim-unlocked (I used it with t-mobile). I did try the factory reset from the bootloader, and it seems like I do have a corrupt sd card, just like you suggested. When I enter recovery, the phone reboot, and stuck in boot loop again. I also agree that install the RUU with s-on is a recipe for a bricked phone. I never had fastboot working before, I just tried it for the sake of installing the RUU.
Do you think that the phone's microusb port is broken?

Ok, so an RUU is possibly safe for you, if the phone has never been modified in the past. The only way to be sure of this is to check the CID but to do that you need a working fastboot connection. The command is this:
Code:
fastboot oem readcid
If it comes back as CWS__001 you're safe to run an RUU, but if it comes back as 11111111 (or anything else) it isn't safe.
When you connect the phone to your PC while the phone is in bootloader mode what does it say on the screen of the phone? It should either say fastboot usb or fastboot ac. If it says fastboot usb your usb port is fine, if it says fastboot ac there could be a problem with the data pins on the port.
Sent from my Evita

timmaaa said:
Ok, so an RUU is possibly safe for you, if the phone has never been modified in the past. The only way to be sure of this is to check the CID but to do that you need a working fastboot connection. The command is this:
Code:
fastboot oem readcid
If it comes back as CWS__001 you're safe to run an RUU, but if it comes back as 11111111 (or anything else) it isn't safe.
When you connect the phone to your PC while the phone is in bootloader mode what does it say on the screen of the phone? It should either say fastboot usb or fastboot ac. If it says fastboot usb your usb port is fine, if it says fastboot ac there could be a problem with the data pins on the port.
Sent from my Evita
Click to expand...
Click to collapse
Yeah, I tried to look up my CID too, but the pc doesnt recognize the phone. When I connect the phone to the pc and I enter the fastboot menu, there're 4 options: bootloader, reboot, reboot bootloader, and power down. It says fastboot usb when I move down to the 3 bottom options.
Still, when I typed in "fastboot oem readcid" in cmd, it stills says < waiting for device >. Could I be setting up the fastboot wrong?

dxbach12 said:
Yeah, I tried to look up my CID too, but the pc doesnt recognize the phone. When I connect the phone to the pc and I enter the fastboot menu, there're 4 options: bootloader, reboot, reboot bootloader, and power down. It says fastboot usb when I move down to the 3 bottom options.
Still, when I typed in "fastboot oem readcid" in cmd, it stills says < waiting for device >. Could I be setting up the fastboot wrong?
Click to expand...
Click to collapse
You can try "fastboot devices" to see if its connecting, beyond that you can check device manager to check if your PC can actually see the device, but perhaps hasn't installed it properly.

For fastboot to work properly you need fastboot installed (obviously), you need the proper drivers installed, you need to be using a usb 2.0 port, and you need to be using the original HTC cable (or one that's known to have good data transmission properties). Do you meet all those requirements? If you have drivers installed how did you install them? The fact that fastboot usb shows up on your screen suggests that the port on your phone is ok. What os are you running on your PC?
Sent from my Evita

timmaaa said:
For fastboot to work properly you need fastboot installed (obviously), you need the proper drivers installed, you need to be using a usb 2.0 port, and you need to be using the original HTC cable (or one that's known to have good data transmission properties). Do you meet all those requirements? If you have drivers installed how did you install them? The fact that fastboot usb shows up on your screen suggests that the port on your phone is ok. What os are you running on your PC?
Sent from my Evita
Click to expand...
Click to collapse
This may be where the problem lies. I don't have an OEM HTC data cable. I've been using a 3rd party one, and before the boot loop problem, the cable works fine. I tried both USB 2.0 port and 3.0 port, but neither works. The pc runs Windows 8.1. I install the driver using "HTC Driver Installer.msi" from another thread on XDA. Still, in device manager, the phone is shown as "Unknown USB Device (Device Failed Enumeration)". I tried to update the driver using local files with no luck.

Ok, your problem is Windows 8.1, there are no compatible fastboot drivers. You need to downgrade to Windows 8 or lower and you should be fine.
Sent from my Evita

timmaaa said:
Ok, your problem is Windows 8.1, there are no compatible fastboot drivers. You need to downgrade to Windows 8 or lower and you should be fine.
Sent from my Evita
Click to expand...
Click to collapse
Sorry for the delayed response, I have been away on business.
So I tries the fastboot on my wife's win 7 pc and it works, finally. When I ran fastboot oem readcid, it returns CWS_001. It looks like I can install the RUU after all.
What guide would you recommend me following? I tried to google one but there're just too many.
Thanks in advance!

All you need to do is connect your phone in fastboot mode and run the RUU exe in Windows. Make sure HTC Sync Manager is uninstalled, make sure no other programs are running, and make sure screen saver/hibernation is turned off. All you need to do is follow the prompts.
Sent from my Evita

timmaaa said:
All you need to do is connect your phone in fastboot mode and run the RUU exe in Windows. Make sure HTC Sync Manager is uninstalled, make sure no other programs are running, and make sure screen saver/hibernation is turned off. All you need to do is follow the prompts.
Sent from my Evita
Click to expand...
Click to collapse
I put the phone in fastboot, ran the RUU, and after a few prompts, clicked "Update", I reached the screen where it says "Waiting for bootloaders" with a status bar. Then after a while (seems like the bootloader fails?), Error [171]: USB Connection Error screen pops up. I gues this is because I can't boot the phone up and select USB debugging as the connection mode. What can I do now? Is it possible to fix the bootloader or put the phone is USB debugging mode?
Thanks!

dxbach12 said:
I put the phone in fastboot, ran the RUU, and after a few prompts, clicked "Update", I reached the screen where it says "Waiting for bootloaders" with a status bar. Then after a while (seems like the bootloader fails?), Error [171]: USB Connection Error screen pops up. I gues this is because I can't boot the phone up and select USB debugging as the connection mode. What can I do now? Is it possible to fix the bootloader or put the phone is USB debugging mode?
Thanks!
Click to expand...
Click to collapse
It has nothing to do with the usb debugging option, I've run RUUs with no OS on my phone before, they do not require that. The problem is your usb connection, this can be sure to multiple things. Are you using a usb 2.0 port? Are you using an original HTC cable or a cable that's known to work with adb/fastboot? You're not still using the PC with Windows 8.1 on it are you?
Sent from my Evita

timmaaa said:
It has nothing to do with the usb debugging option, I've run RUUs with no OS on my phone before, they do not require that. The problem is your usb connection, this can be sure to multiple things. Are you using a usb 2.0 port? Are you using an original HTC cable or a cable that's known to work with adb/fastboot? You're not still using the PC with Windows 8.1 on it are you?
Sent from my Evita
Click to expand...
Click to collapse
Let me tried borrowing someone else's cable. I was using a LG G2 one, so that could be a usb 3.0 cable.

You didn't answer my question, what OS are you using on the PC now?
Sent from my Evita

timmaaa said:
You didn't answer my question, what OS are you using on the PC now?
Sent from my Evita
Click to expand...
Click to collapse
Sorry. It's Windows 7 Professional SP1.

Ok, check the cable and check the port too.
Sent from my Evita

timmaaa said:
Ok, check the cable and check the port too.
Sent from my Evita
Click to expand...
Click to collapse
Ok, so far I have tried connecting the phone to the usb 2.0 port of the win 7 sp1 laptop using:
- 3rd party usb 2.0 cable
- OEM LG G2 cable (probably usb 3.0)
- OEM Kindle usb 2.0 cable
None have works so far. Every time, error [171] pops up.
Could it be a problem with the battery? The RUU recommends charging the phone at least to 30%. When I plug a charger in the phone, the boot loop continues, so I don't think my phone is charging.

dxbach12 said:
Ok, so far I have tried connecting the phone to the usb 2.0 port of the win 7 sp1 laptop using:
- 3rd party usb 2.0 cable
- OEM LG G2 cable (probably usb 3.0)
- OEM Kindle usb 2.0 cable
None have works so far. Every time, error [171] pops up.
Could it be a problem with the battery? The RUU recommends charging the phone at least to 30%. When I plug a charger in the phone, the boot loop continues, so I don't think my phone is charging.
Click to expand...
Click to collapse
So the phone bootloops even when in the bootloader?
Sent from my Evita

timmaaa said:
So the phone bootloops even when in the bootloader?
Sent from my Evita
Click to expand...
Click to collapse
No, that doesnt happen. When it's not in HBOOT, that happens. I'm charging it while putting in HBOOT right now.

Phone does not communicate with PC

Hi there,
Firstly, I'd like to introduce the device I have issue with:
HTC One S (ville)
HBoot 2.15.0000
S-Off
CID-11111111
Radio-1.35a.32.45.27_10.144.32.34aL
Recovery - TWRP v2.8.7.0
I had installed there CyanogenMod 12.1 from this thread.
Before I had installed CM 12.1, I have installed stock software with RUU (RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4) and I made a backup with TWRP.
Since I had some (known) issues with the ROM - sometimes camera was not accessible and required reboot, sometimes the volume in a call was low, and space for apps got quickly populated - I thought clean-up of the phone and HBoot 2.16 would do. Recently I had another issue - my phone was not recognized by PC and I could not access internal SD card. So, first thing I thought should fix/bring USB connection back to life, was returning to previous, unused and working OS from the backup. No success...
My phone is not detected neither in fastboot mode nor ADB, and I have checked it on many PCs and OSs - Windows XP, Windows 8.1, Windows 10, Linux Mint 17.3. It is not listed with connected USB devices. When in fastboot, it shows only "fastboot AC" as if I would be connected to charger. I have tried many USB cables and I have connected another phone via these cables, everything was running. It is definitely something with the phone not willing to communicate with PC. There is one moment it is detected - while booting (or when I boot to bootloader) Windows can see unrecognized device (error: "device descriptor request failed").
The internal memory is fully accessible from phone at /storage/sdcard0, but it cannot be mounted to PC. I tried mounting the memory via TWRP, also without success.
At the moment I have a phone which is working with stock Android 4.1.1; I am inclined to suppose that I am even able to flash CM 12.1 again. What bothers me is the USB connection - fastboot seems to be vital to fix any 'major' OS failure, and AFAIR it is required to flash Hboot 2.16. Well, I could live with my phone like that, but I hope this is not the beginning of the end for my One S! Do you know what could be wrong there?

Update: Managed to install CM12.1 - I did something wrong for the first time, now it is runnig. Still no USB connection.

Update: I have managed to install newest recovery TWRP 3.0.2-0. Still, can't connect phone via USB.
Please. Anyone has a clue?