I have a NS i9020T which was running the latest MIUI ROM until I tried to update it to MIUI ICS. I had noticed, while running pre-ICS, that my computer wouldn't mount USB storage. As a working around (rather that trying to fix the issue) I just FTPed files. When I tried to install MIUI ICS something went wrong (probably corrupt ROM image) and now my NS won't boot.
If I go through Clockwork Recovery to mount USB mass storage, nothing happens. I'm running OS X, but I've tried mounting in Ubuntu 11 and Win7 -- Windows recognizes that there is a device there but the drivers won't recognize it (I think).
Finally, I've tried flashing a new recovery using fastboot but I get "<waiting for device>" in Terminal.
My best guess is that the USB connection is shot, which would probably require me ripping the NS open and tinkering around (which I have zero experience doing).
Does anyone have any ideas for fixing what is likely a permanent brick? I can boot into Win7, OS X, or Linux to troubleshoot. Also I'm on the XDA IRC as "threepape" right now trying to solve this issue.
Thanks in advance!
I was working with threepape on IRC trying to narrow down the issue.
Basically he's had his phone rooted, tried flashing a rom and now it's stuck at the boot screen. He went to connect to his computer and it gave him an error. and wouldn't let him connect his phone to the os. This is a problem.
So he then downloaded kies to see if it would install drivers automatically, downloaded odin and then tried to see if odin would recognize the phone. It did not and his computer gave him the error "unknown USB device, error code 43"
So we reviewed what we could control: trying different cords, checking drivers, etc.
Now we are going to try booting into an osx platform, installing heimdall and seeing if "heimdall detect" prompt will detect the phone. If that doesn't work we're going to either need more help or rule it out as a hardware issue.
<threepape>
Failed to detect compatible download-mode device.
[8:55pm] <ddrt>
so you typed out heimdall, then heimdall detect and it came back with that?
[8:55pm] <ddrt>
and you are 100% it was in download mode?
[8:55pm] <threepape>
yep
[8:56pm] <threepape>
it does ay on my phonee "USB Control Init USB Control Init End"
Click to expand...
Click to collapse
edit: device is not being detected on multiple os using different programs, device will not wipe fully when doing a factory restore through CWM. I am at a loss.
Hi,
I have two HTC One S, one connects to the PC and I have been able to install CM10.1, all is good, other than it doesn't charge the battery no-matter what. The other one, while connected to any USB power, charges the battery but it doesn't allow to get in communication with the same computer that the other one talks with.
1) The two One S are both S4 -
2) The drivers on the PC are OK otherwise they both wouldn't connect, same with fastboot and adb, if it works for one it must (?) work for the other.
3) Swapped cables, no luck, swapped USB port, no luck, various PC and phone reboots...
4) The ONE S that charges but doesn't communicate with the PC is still Locked and has the latest OTA from T-Mobile. I can't unlock the bootloader because, while it can go to HBOTT/Fastboot, it doesn't switch to "fastboot usb" when connected.
5) The ONE S that charges, even if I enable debugging option, it still doesn't show in ADB Devices....
Do you think it is an hardware issue? If it were, how would I go to investigate/fix? (Can it be fixed?)
Is it possible to unlock the bootloader without the USB connection using the stock T-Mobile software?
Anyone?
Thank You
Hardware or Software issue?
Well, no-one has responded to this one. So I thought I might just as well update the status of the issue which is still an issue. How would I be able to understand if the issue is software or hardware? - If the fastboot driver is installed properly, as it works with another phone (exactly the same model, same cable, same port) why doesn't it switch from "fastboot" to "fastboot usb"? How do I tell if there is an issue with the software on the phone or an hardware problem again , on the phone? -
Why, if I enable ADB on the phone then it doesn't show the ADB sign? See, this is a big issue as I can't unlock the bootloader and SIM without access to fastboot (or am I wrong?).
Anyway here are some details about the specific phone:
Model: HTC One S (Ville)
Android Version: 4.0.4
HTC Sense Version: 4.1
Software Number: 2.35.531.12 710RD
HTC SDK API Leve: 4.23
HTC Extension version: HTCExtension_403_1_GA_20
Kernel Version: 3.0.8-01602-gc3009b9
[email protected]#1
SMP Preempt
Baseband Version: 1.13.50.05.25_10.29.50.08L
Browser Version: WebKit/534.30
Info from HBOOT:
LOCKED
VLE PVT SHIP S-ON RL
HBOTT-1.14.0005
RADIO-1.13.50.05.25
OpenDSP-v29.1.0.45.0622
eMMC-boot
Nov 21 2012, 12:17:41
evoarcher said:
Hi,
I have two HTC One S, one connects to the PC and I have been able to install CM10.1, all is good, other than it doesn't charge the battery no-matter what. The other one, while connected to any USB power, charges the battery but it doesn't allow to get in communication with the same computer that the other one talks with.
1) The two One S are both S4 -
2) The drivers on the PC are OK otherwise they both wouldn't connect, same with fastboot and adb, if it works for one it must (?) work for the other.
3) Swapped cables, no luck, swapped USB port, no luck, various PC and phone reboots...
4) The ONE S that charges but doesn't communicate with the PC is still Locked and has the latest OTA from T-Mobile. I can't unlock the bootloader because, while it can go to HBOTT/Fastboot, it doesn't switch to "fastboot usb" when connected.
5) The ONE S that charges, even if I enable debugging option, it still doesn't show in ADB Devices....
Do you think it is an hardware issue? If it were, how would I go to investigate/fix? (Can it be fixed?)
Is it possible to unlock the bootloader without the USB connection using the stock T-Mobile software?
Anyone?
Thank You
Click to expand...
Click to collapse
I have the same problem. The update stated security enhancements, so I'm wondering if they did something to prevent it from being rooted because I had no issue doing it with previous releases.
Don't know which one are you referring to. The problem that it doesn't charge or that it doesn't connect to via usb? - For me the one that doesn't charge is rooted and Cyanogen Mod 10.1 is installed. The other one, the one that doesn't communicate but charges via usb has the stock "from recovery" of T-Mobile. With this one I have tried a hard reset and loaded from recovery. I wish there was a way to put an T-Mobile update.zip on it and re-flash it from recovery.
evoarcher said:
Don't know which one are you referring to. The problem that it doesn't charge or that it doesn't connect to via usb? - For me the one that doesn't charge is rooted and Cyanogen Mod 10.1 is installed. The other one, the one that doesn't communicate but charges via usb has the stock "from recovery" of T-Mobile. With this one I have tried a hard reset and loaded from recovery. I wish there was a way to put an T-Mobile update.zip on it and re-flash it from recovery.
Click to expand...
Click to collapse
My problem was it wouldn't unlock the bootloader. It would only charge. I could sync with htc sync so I know my cable was good and the driver installed properly. After several hours of using the all in one tool, and other programs I've found online, I went ahead and went through the process on htc site to unlock the boot loader again. Boot the phone to bootloader, Press the power button to select it. You should hear some noises on the pc indicating it's recognizing the phone. Now on the pc run the following command through adb. I don't remember doing this the first time I unlocked it, so not sure if this is new or not. Make sure your Unlock_code.bin file is in the same folder as adb
Code:
fastboot flash unlocktoken Unlock_code.bin
Your phone will now have an unlocked bootloader. You may have to reboot the device before you can flash the recovery.
After that is done flash a recovery through adb, I did the htc1s touch from cwm.
Code:
fastboot flash recovery recoveryfilename.img
Now reboot your phone normally, You will need the file SuperSU.zip, get the cwm installable one. I can't post links since I don't have enough posts yet, but simple google search will give you the download for it.
Now mount the htc 1s as a disk drive then copy the SuperSU.zip to the /sdcard, which will be the drive you have in windows, I think it's just over 9gb. So you should have some folders in there, just put it in with the folders. Now reboot the phone through adb to the recovery, and choose to flash zip file from sdcard, then locate the SuperSU.zip and select it. Now reboot the phone, mine rebooted 2x before it booted into where I could use the phone. The phone is now rooted!
My phone doesn't sync. it doesn't switch to adb it's not detected by the PC. A different phone (same model) connects fine same port same PC same cable. In hboot it doesn't turn to USB when I connect the cable.
Sent from my One S using xda app-developers app
evoarcher said:
My phone doesn't sync. it doesn't switch to adb it's not detected by the PC. A different phone (same model) connects fine same port same PC same cable. In hboot it doesn't turn to USB when I connect the cable.
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Does your phone show connected under device manager? Mine has two entries, one for htc device, and one for android adb device. Which driver did you use for the phone, the htc one or the one in the sdk? Also have you tried connecting this phone to another computer to see if the same problem exists of it not being recognized?
I would ultimately take the unrooted one back. If it still doesn't work, the issue is on your end.
This is an eBay phone, so realistically, I can't return it. I was wondering if, to rule out an hardware issue, as I can get to the recovery screen:
-> Android system recovery <3e>
->Use volume key to highlight; click power key to select..
-> Reboot system now
-> Apply update from external storage
-> Wipe data/factory reset
->Wipe cache partition
->Apply update from cache
->Apply update from internal storage.
If I could download in the phone storage or connect an external usb drive, and use this menu to re-load a stock t-mobile update.zip file?
Would it be possible? Would it help?
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
Similar questions to this have been asked before but got no replies so, in desparation, am asking again.
Bought my phone second hand. On starting, it shows the Vodafone logo so assume it's branded.
About Phone -> Software Information shows:
Android Version: 2.3.5HTC Sense version: 3.0Software number: 2.10.161.5
HBOOT shows:
*** UNLOCKED ***SAGA PUT SHIP S-ON RHHBOOT-2.00.0002
Now for the problem:
I'm trying to set S-OFF and root the phone but my PC, running Windows 10, is unable to communicate with the phone when it's in Recovery mode.
The entry for My HTC under Android USB Devices in Device Manager disappears once I start the phone in Recovery mode and connect it to my PC via a USB cable.
At this point Device manager on my PC shows under USB Controllers an entry for an unknown USB Device (Device failed enumeration) and the Hardware Ids show as USB\UNKNOWN.
I'd really appreciate someone familiar with this area throwing some light on what could be going on here and perhaps giving me some pointers on how to resolve this.
there is one quick fix http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337 (for me it worked with the old win 10)
if it doesnt work: the fastest way is to seek a friend with windows 7 and s-off the bootloader
if its s-off you dont need the "fastboot" mode
here is an tutorial http://forum.xda-developers.com/htc-desire-s/general/installing-cm13-untouched-htc-desire-s-t3456585 if you have luck it works with your win 10 too
IMPORTANT: DO NOT UPDATE TO ANDROID 4.0.4 IT KILLS THE POSSIBILITY TO S-OFF YOUR PHONE
Layer_DE said:
there is one quick fix http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337 (for me it worked with the old win 10)
if it doesnt work: the fastest way is to seek a friend with windows 7 and s-off the bootloader
if its s-off you dont need the "fastboot" mode
here is an tutorial http://forum.xda-developers.com/htc-desire-s/general/installing-cm13-untouched-htc-desire-s-t3456585 if you have luck it works with your win 10 too
IMPORTANT: DO NOT UPDATE TO ANDROID 4.0.4 IT KILLS THE POSSIBILITY TO S-OFF YOUR PHONE
Click to expand...
Click to collapse
Thanks for replying but, following the links you gave they all ended with a brick wall. Using VirtualBox I tried using Window 7 and even Windows XP. All attemprt failed miserably.
In all cases Device Manager showed the MyHTC driver installed under Androis USB Devices and working normally. Running command 'adb devices', when the phone was running normally, worked fine but USB connection is lost every time when booting into HBOOT, making fastboot etc impossible.
I've reached the point where I can't waste any more time on this having wasted far too much already. I don't like giving up but this has got me.
bacoms said:
Thanks for replying but, following the links you gave they all ended with a brick wall. Using VirtualBox I tried using Window 7 and even Windows XP. All attemprt failed miserably.
In all cases Device Manager showed the MyHTC driver installed under Androis USB Devices and working normally. Running command 'adb devices', when the phone was running normally, worked fine but USB connection is lost every time when booting into HBOOT, making fastboot etc impossible.
I've reached the point where I can't waste any more time on this having wasted far too much already. I don't like giving up but this has got me.
Click to expand...
Click to collapse
the problem is simple on a windows hosted vm usb passthrought doesnt work with unknown devices
Layer_DE said:
the problem is simple on a windows hosted vm usb passthrought doesnt work with unknown devices
Click to expand...
Click to collapse
If I can drum up any enthusiasm to continue, I'll try and borrow a PC running Windows 7 and try again.
Hello!
I have tried to upgraded my phone to Lineage 18.1 but it did not work.
This is what I did so far:
1) Installed the NEWEST TWRP and unfortunately I have deleted the OS. After that, the USB connection worked fine and I was able to see all files on my phone.
2) I've found a stock recovery.img that I have used and then the problem started. After installing that recovery.img file now I have TWRP (older version) 2.7.0.0 and:
a) when connected through USB , my computer does make sound, but it does NOT recognize my phone any more. Yes, I do have the newest USB drivers installed
b) when connected through USB and when I run this command: fastboot devices, then it DOES shows my device number, but it DOES NOT any devices using adb command.
c) when booting into fastboot, the phone shows just the black screen with the android faded icon.
d) I can boot into TWRP but there is no system or recovery files in there and it look like it's just useless.
I'm not sure what to do next. It looks like the phone is soft-bricked.
Any help will be appreciated.
Thank you
the first thing i would try is flashing twrp 3.6 (the newest) using fastboot. not sure why you would flash an old recovery version. if data recovery is not an issue then the opo is even fixable after a hardbrick (i used to have it). i used the color os method but that was ages ago. now there is a slightly easier way somewhere here on xda if you want the opo to in out of the box condition.
maybe try the whole thing using a secondary old laptop (if possible) or a virtual machine. otherwise i have no idea. sounds like a lot of trial and error might be needed. good luck.