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
Related
Hi all,
Seen many topics about this topic but no solutions.
I'm trying to restore my phone to stock but I have the dual problems of:
A. Not having a working rom/android state to boot into
B. Unfortunately, after trying various stock methods, no longer recognizes fastboot commands (e.g., fastboot devices lists nothing). I connected previously so this is not an issue
Is there anything to be done to restore to stock or am I simply screwed?
I am working from a Mac OS X computer but can access Windows if it helps.
Thanks in advance.
none_of_the_above said:
Hi all,
Seen many topics about this topic but no solutions.
I'm trying to restore my phone to stock but I have the dual problems of:
A. Not having a working rom/android state to boot into
B. Unfortunately, after trying various stock methods, no longer recognizes fastboot commands (e.g., fastboot devices lists nothing). I connected previously so this is not an issue
Is there anything to be done to restore to stock or am I simply screwed?
I am working from a Mac OS X computer but can access Windows if it helps.
Thanks in advance.
Click to expand...
Click to collapse
does adb recognize it if you let it boot normally? if it gets to booting the kernel and adb recognizes it you may be able to push the system files manually via terminal. from there you can add recovery and at least have that option....but you would have to be very careful if you can't get to fastboot.
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?
Hey all. Done a lot of searching and have tried a lot of solutions but I'm still having the same problem.
A friend of mine brought me her phone (AT&T HTC One X Plus) that she had soft bricked my trying to root and flash his own rom by herself. Trying to fix it, she accidentally relocked the bootloader and also wiped the recovery from the device. She said she wanted it re-rooted and CyanogenMod 10.1 installed. I told her I could do it for her. I have unlocked the bootloader through htcdev, flashed on the new recovery (using CWM v6.0.2.7) and now all I need to do is transfer the actual ROM to the phone and then install it. I can't, however, for the life of me get this phone to communicate with the computer/ADB. Fastboot recognizes it fine, I can type put the phone in fastboot mode and type 'fastboot oem get_identifier_token' and it will give me the identification number of the phone and other details, so I know it's communicating with it, but when I type 'adb devices', nothing shows up. And it's the "adb push filename.zip /sdcard/" command that I have to use. I have also tried going through the recovery and mounting the /sdcard/ and /data/ and /system/ to the computer, with no luck. Whenever I click on the "mount sd" through the recovery, the page just refreshes and puts my selection back at the top making no changes.
Whenever I plug this phone into any of my computers, all of the drivers install except for the HTC MTP driver, as seen here;
img59.imageshack.us /img59/61/driverh.png (Sorry, going to have to fix that link, can't post pictures yet)
I have plugged an HTC One into the computer and it downloads all the drivers just fine and communicates with adb. Same thing with my Note 2.
Any help would be really appreciated.
Thanks,
John
iBlameLag said:
Hey all. Done a lot of searching and have tried a lot of solutions but I'm still having the same problem.
A friend of mine brought me her phone (AT&T HTC One X Plus) that she had soft bricked my trying to root and flash his own rom by herself. Trying to fix it, she accidentally relocked the bootloader and also wiped the recovery from the device. She said she wanted it re-rooted and CyanogenMod 10.1 installed. I told her I could do it for her. I have unlocked the bootloader through htcdev, flashed on the new recovery (using CWM v6.0.2.7) and now all I need to do is transfer the actual ROM to the phone and then install it. I can't, however, for the life of me get this phone to communicate with the computer/ADB. Fastboot recognizes it fine, I can type put the phone in fastboot mode and type 'fastboot oem get_identifier_token' and it will give me the identification number of the phone and other details, so I know it's communicating with it, but when I type 'adb devices', nothing shows up. And it's the "adb push filename.zip /sdcard/" command that I have to use. I have also tried going through the recovery and mounting the /sdcard/ and /data/ and /system/ to the computer, with no luck. Whenever I click on the "mount sd" through the recovery, the page just refreshes and puts my selection back at the top making no changes.
Whenever I plug this phone into any of my computers, all of the drivers install except for the HTC MTP driver, as seen here;
img59.imageshack.us /img59/61/driverh.png (Sorry, going to have to fix that link, can't post pictures yet)
I have plugged an HTC One into the computer and it downloads all the drivers just fine and communicates with adb. Same thing with my Note 2.
Any help would be really appreciated.
Thanks,
John
Click to expand...
Click to collapse
ADB only works when the rom is loaded with usb debugging on. It's a shell for command line direct to your phone. Furthermore, recovery does not use MTP, it uses generic mass storage device.
It seems you're not the only one having issues mounting with CWM. I don't know much about it because CWM has very little compatibility with the HTC ONEXL(This forum) whereas you seem to have the ONEXPLUS there. Different phone, but if TWRP is compatible with your phone you can try mounting using TWRP instead? I understand that at one point a specific version or set of versions perhaps(like I said, we don't use CWM much for this phone) had issues mounting so you can check to make sure you have the latest version of CWM as I am pretty sure they've since fixed the issue. If you are using the latest version, you can also try issuing "fastboot erase cache" while in bootloader/fastboot to clear cache which may fix your issue.
Good luck. For better help it may be best to post in the one x+ forum subsection.
exad said:
ADB only works when the rom is loaded with usb debugging on. It's a shell for command line direct to your phone. Furthermore, recovery does not use MTP, it uses generic mass storage device.
It seems you're not the only one having issues mounting with CWM. I don't know much about it because CWM has very little compatibility with the HTC ONEXL(This forum) whereas you seem to have the ONEXPLUS there. Different phone, but if TWRP is compatible with your phone you can try mounting using TWRP instead? I understand that at one point a specific version or set of versions perhaps(like I said, we don't use CWM much for this phone) had issues mounting so you can check to make sure you have the latest version of CWM as I am pretty sure they've since fixed the issue. If you are using the latest version, you can also try issuing "fastboot erase cache" while in bootloader/fastboot to clear cache which may fix your issue.
Good luck. For better help it may be best to post in the one x+ forum subsection.
Click to expand...
Click to collapse
Thank you, flashed over twrp and the computer recognizes it. Thanks so much for your help!
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
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?