Database Develop

[Q] HTC one bricked? stuck on HTC logo

Hi I was rooting my HTC one and was able to do so successfully. Then I tried to flash roms and it didn't work with TWRP so I tried clockwork. That's when everything went to hell. I was stuck in the bootloader loop and it just kept booting to that. Then I tried to follow this guide
http://forum.xda-developers.com/showthread.php?t=2258809
and I did method 1 but when I ran one of the commands I saw failed. Now my HTC One is just stuck on the screen with a silver HTC logo and I can't even turn it off. I would really appreciate any insights and advice. I tried doing it on my own but clearly I kept ****ing up and could really use some help.

limache said:
Hi I was rooting my HTC one and was able to do so successfully. Then I tried to flash roms and it didn't work with TWRP so I tried clockwork. That's when everything went to hell. I was stuck in the bootloader loop and it just kept booting to that. Then I tried to follow this guide
http://forum.xda-developers.com/showthread.php?t=2258809
and I did method 1 but when I ran one of the commands I saw failed. Now my HTC One is just stuck on the screen with a silver HTC logo and I can't even turn it off. I would really appreciate any insights and advice. I tried doing it on my own but clearly I kept ****ing up and could really use some help.
Click to expand...
Click to collapse
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)

Toxicoblivion said:
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)
Click to expand...
Click to collapse
I've got to ask. A bright light? Is he doing surgery as well? What's the reason for the light?
Sent from my HTCONE using xda premium

Quis89 said:
I've got to ask. A bright light? Is he doing surgery as well? What's the reason for the light?
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
for some reason multiple people have reported successful reboots under bright light in which previously (sometimes within minutes) earlier would not work in a dark environment. i have no idea why it works, but ive heard it work enough times, its worth adding it in.

Toxicoblivion said:
for some reason multiple people have reported successful reboots under bright light in which previously (sometimes within minutes) earlier would not work in a dark environment. i have no idea why it works, but ive heard it work enough times, its worth adding it in.
Click to expand...
Click to collapse
It's thought this is a safety feature so that you can't accidentally long press power and restart in dark places like your pocket.

@rider5512 Sounds right to me. Thanks for clarifying.

Toxicoblivion said:
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)
Click to expand...
Click to collapse
Thanks Toxic!!- so I tried that and I'm back in the bootloader now! I guess the bright light made a difference as I messed up my phone last night. It didn't buzz but now I'm back in the bootloader. How should I go about fixing this now that I can access the bootloader and recovery? I really don't want to half ass this again lol.
It also says "TAMPERED" "RELOCKED" on the top as well.
I'm thinking of following the instructions for method 2 from this thread.
http://forum.xda-developers.com/showthread.php?t=2258809
Would this be correct or do I need to do anything else first?

limache said:
Thanks Toxic!!- so I tried that and I'm back in the bootloader now! I guess the bright light made a difference as I messed up my phone last night. It didn't buzz but now I'm back in the bootloader. How should I go about fixing this now that I can access the bootloader and recovery? I really don't want to half ass this again lol.
It also says "TAMPERED" "RELOCKED" on the top as well.
I'm thinking of following the instructions for method 2 from this thread.
http://forum.xda-developers.com/showthread.php?t=2258809
Would this be correct or do I need to do anything else first?
Click to expand...
Click to collapse
Method 2 looks good.
Just remember that you will have to unlock your bootloader again. You will probably have to request a new token at htcdev.
Then flash recovery from toolkit and sideload and install new rom.

crushalot said:
Method 2 looks good.
Just remember that you will have to unlock your bootloader again. You will probably have to request a new token at htcdev.
Then flash recovery from toolkit and sideload and install new rom.
Click to expand...
Click to collapse
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?

limache said:
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?
Click to expand...
Click to collapse
fastboot erase cache

limache said:
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?
Click to expand...
Click to collapse
You need to flash a new custom recovery again before you can boot into it and sideload. You won't be able to do that until you unlock your bootloader again.
You do have to do the whole process of unlocking the bootloader and installing a custom recovery from the toolkit.
You will need to get a new unlock token from htcdev (however you did it before, manually or with the toolkit) since you can only use the unlock token's once it seems. No biggie, just need to do the process again to get that new token you will need to unlock you bootloader before you will be able to do anything in recovery.

crushalot said:
You need to flash a new custom recovery again before you can boot into it and sideload. You won't be able to do that until you unlock your bootloader again.
You do have to do the whole process of unlocking the bootloader and installing a custom recovery from the toolkit.
You will need to get a new unlock token from htcdev (however you did it before, manually or with the toolkit) since you can only use the unlock token's once it seems. No biggie, just need to do the process again to get that new token you will need to unlock you bootloader before you will be able to do anything in recovery.
Click to expand...
Click to collapse
Thank you crushalot!
So I am following this guide.
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
I successfully unlocked the bootloader and now I need to flash the recovery. In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?
Edit - Okay so I used Hasoon's toolkit to flash the recovery and I think it worked. However, now I am trying to sideload the rom and having issues. I selected "ADB Sideload a ROM" and i manually went into recovery and TWRP (the toolkit can't send it into recovery for some reason). I selected "sideload a rom" on the HTC and then it shows you a bar that says "Swipe to sideload". I wasn't sure if I needed to do that or not but I tried running the toolkit and sideloading the rom and i got "error: closed" in command prompt.
in TWRP there are messages saying "unable to mount /data, recreate data/media folder, internal storage etc".

limache said:
Thank you crushalot!
So I am following this guide.
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
I successfully unlocked the bootloader and now I need to flash the recovery. In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?
Edit - Okay so I used Hasoon's toolkit to flash the recovery and I think it worked. However, now I am trying to sideload the rom and having issues. I selected "ADB Sideload a ROM" and i manually went into recovery and TWRP (the toolkit can't send it into recovery for some reason). I selected "sideload a rom" on the HTC and then it shows you a bar that says "Swipe to sideload". I wasn't sure if I needed to do that or not but I tried running the toolkit and sideloading the rom and i got "error: closed" in command prompt.
in TWRP there are messages saying "unable to mount /data, recreate data/media folder, internal storage etc".
Click to expand...
Click to collapse
"In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?"
That is done in order to give root access to the currently installed rom. You are going to install a new rom, so you don't have to do that until you get the rom installed.
You are now the 3rd user I have run into that is having the issue where you can't mount anything in recovery and I'm not sure why. Some users report that re locking and unlocking the bootloader fixes this, but you just did that, so I'm not sure why this is happening.
Within the toolkit try the perm root option? Perhaps there is something I can't think of since I rooted mine, the day I got it awhile back.
"Rooting The Device To root your device, first make sure you have unlocked the bootloader and installed a custom recovery. Next, select the ‘Perm Root’ option (the last one) from the Extras section and follow the instructions to get root access in no time."
To any other advanced users who may be able to answer this:
Does the recovery need the installed rom to have the SU binaries before it can mount the system in recovery? Does recovery need to be granted SU though some other means before mounting?

crushalot said:
"In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?"
That is done in order to give root access to the currently installed rom. You are going to install a new rom, so you don't have to do that until you get the rom installed.
You are now the 3rd user I have run into that is having the issue where you can't mount anything in recovery and I'm not sure why. Some users report that re locking and unlocking the bootloader fixes this, but you just did that, so I'm not sure why this is happening.
Within the toolkit try the perm root option? Perhaps there is something I can't think of since I rooted mine, the day I got it awhile back.
"Rooting The Device To root your device, first make sure you have unlocked the bootloader and installed a custom recovery. Next, select the ‘Perm Root’ option (the last one) from the Extras section and follow the instructions to get root access in no time."
To any other advanced users who may be able to answer this:
Does the recovery need the installed rom to have the SU binaries before it can mount the system in recovery? Does recovery need to be granted SU though some other means before mounting?
Click to expand...
Click to collapse
Okay I just tried Perm room - nothing happened except it showed 776 KB/s. I remember a few days ago there was a system update from HTC and I updated it OTA - would that affect this at all?
Just to be clear, I run the program, go into recovery, go into adb sideload, then I select the rom on the PC. Then I swipe across the bar to mount the rom and then it fails to mount and I get "error closed" in command prompt.

I know it is a pain in the ass, and users not familiar with adb/fastboot commands and using the toolkit mess it up.
Flashing recovery in fastboot after you pointed to your adb/fastboot folder you need to do:
fastboot erase cache
fastboot flash recovery name-of-your-recovery.img
fastboot erase cache
As you got it flashed successfully but you have problems sideliadung it with adb, get yourself a OTG cable and a USB storage stick, put the custom ROM.zip on there and then choose 'flash .zip from external storage' or s.thing like that. I don't know if that option is available in TWRP but it is in ClockworkMod.
Once you have booted successfully up into the ROM, go back into recovery and do a Nandroid back up, and keep it on that stick and on the internal storage if your One!
Good luck
Sent from my HTC One using xda premium

hardstuffmuc said:
I know it is a pain in the ass, and users not familiar with adb/fastboot commands and using the toolkit mess it up.
Flashing recovery in fastboot after you pointed to your adb/fastboot folder you need to do:
fastboot erase cache
fastboot flash recovery name-of-your-recovery.img
fastboot erase cache
As you got it flashed successfully but you have problems sideliadung it with adb, get yourself a OTG cable and a USB storage stick, put the custom ROM.zip on there and then choose 'flash .zip from external storage' or s.thing like that. I don't know if that option is available in TWRP but it is in ClockworkMod.
Once you have booted successfully up into the ROM, go back into recovery and do a Nandroid back up, and keep it on that stick and on the internal storage if your One!
Good luck
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.

limache said:
Okay I just tried Perm room - nothing happened except it showed 776 KB/s. I remember a few days ago there was a system update from HTC and I updated it OTA - would that affect this at all?
Just to be clear, I run the program, go into recovery, go into adb sideload, then I select the rom on the PC. Then I swipe across the bar to mount the rom and then it fails to mount and I get "error closed" in command prompt.
Click to expand...
Click to collapse
Yes, every user that I encountered with this issue had done an OTA update. Not exactly sure why or how that is causing these issues.
Yes, your procedure for sideload is correct, however you are unable to flash anything or use recovery at all because when in recovery the internal storage won't mount, so it can't perform any actions.
Need to do some more reading for: unable to mount in recovery
---------- Post added at 01:54 PM ---------- Previous post was at 01:49 PM ----------
limache said:
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.
Click to expand...
Click to collapse
I don't think the toolkit is the issue. The cache erase can also be done from the toolkit with the Erase Cache in the Commands section. Never hurts to try this, but the issue is not being able to mount storage in recovery. I think you could install either recovery and it wouldn't matter as they would both have the same issue. Generally, I prefer TWRP anyway.
You can't access the phones internal storage when connected via USB when the phone is in recovery or fastboot. So that is normal.

limache said:
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.
Click to expand...
Click to collapse
crushalot said:
Yes, every user that I encountered with this issue had done an OTA update. Not exactly sure why or how that is causing these issues.
Yes, your procedure for sideload is correct, however you are unable to flash anything or use recovery at all because when in recovery the internal storage won't mount, so it can't perform any actions.
Need to do some more reading for: unable to mount in recovery
---------- Post added at 01:54 PM ---------- Previous post was at 01:49 PM ----------
I don't think the toolkit is the issue. The cache erase can also be done from the toolkit with the Erase Cache in the Commands section. Never hurts to try this, but the issue is not being able to mount storage in recovery. I think you could install either recovery and it wouldn't matter as they would both have the same issue. Generally, I prefer TWRP anyway.
You can't access the phones internal storage when connected via USB when the phone is in recovery or fastboot. So that is normal.
Click to expand...
Click to collapse
Hmmm okay so the other poster's suggestion was to get an OTG cable (a micro usb to USB cable right?) and connect the USB with the ROM directly the phone. Do you think this would be a big difference or no? I just don't know if the issue is the internal storage itself or the mode of pushing the ROM.
Otherwise, I'm pretty much scratching my head and have no idea what else I could do =/.

Just for anyone else who's having issues, I've tried using TWRP's install function with the OTG cable but it still doesn't mount. Just letting people know.

if you are noob to recover your phone you can try some services like this
i revived my HTC one by them
http://goo.gl/1DMXlq

[Q] Soft brick(?)/usb drivers issue

Hey all! I'm having some big problems getting my phone working. I was running Venom One rom for a while but then decided to try out something else and installed the CM 11S. Again phone worked perfectly but I got used to using Venom so I wanted to go back to it. And that's where I fu**ed it I think... I've installed the rom (I'm using T.W.R.P 2.7.1.1, standard cache and data format) like previously and again everything went smoothly with no errors. However, when I restarted the phone it got stuck on HTC logo. But it wasn't stuck like you couldn't do anything, I could lock the screen and when I unlocked it it would present me with the usual lock screen, time, taskbar etc. but when you unlocked it it went back to the HTC logo after a while an error popped up saying that the htc dialler was not responding. I haven't came across something like that ever before... So I went back to recovery and flashed the system again and again I had the exact same issue. So then I went and formatted everything including my internal storage, and that's where I made the biggest mistake. I forgot that I had the rom zip on internal storage and I'd lose it if I format the partition. No problem you'd say BUT I can't copy anything onto the phone.
When I connect the phone to my PC in recovery mode it just refuses to mount!! No matter which partition I want to mount, nothing comes up in my computer. I went on to the device manager and surely enough the HTC One is an unknown device... I tried side-loading the rom but the adb can't connect to the phone. I tried re-installing the HTC sync just to make sure I definitely have the usb drivers but still no luck. ADB devices command shows no devices connected. I've run out of ideas and I'm regretting my decision to try different roms...
I really don't want to buy a new phone so if anyone has ANY ideas please right it down. Thanks in advance!

bboybtek said:
Hey all! I'm having some big problems getting my phone working. I was running Venom One rom for a while but then decided to try out something else and installed the CM 11S. Again phone worked perfectly but I got used to using Venom so I wanted to go back to it. And that's where I fu**ed it I think... I've installed the rom (I'm using T.W.R.P 2.7.1.1, standard cache and data format) like previously and again everything went smoothly with no errors. However, when I restarted the phone it got stuck on HTC logo. But it wasn't stuck like you couldn't do anything, I could lock the screen and when I unlocked it it would present me with the usual lock screen, time, taskbar etc. but when you unlocked it it went back to the HTC logo after a while an error popped up saying that the htc dialler was not responding. I haven't came across something like that ever before... So I went back to recovery and flashed the system again and again I had the exact same issue. So then I went and formatted everything including my internal storage, and that's where I made the biggest mistake. I forgot that I had the rom zip on internal storage and I'd lose it if I format the partition. No problem you'd say BUT I can't copy anything onto the phone.
When I connect the phone to my PC in recovery mode it just refuses to mount!! No matter which partition I want to mount, nothing comes up in my computer. I went on to the device manager and surely enough the HTC One is an unknown device... I tried side-loading the rom but the adb can't connect to the phone. I tried re-installing the HTC sync just to make sure I definitely have the usb drivers but still no luck. ADB devices command shows no devices connected. I've run out of ideas and I'm regretting my decision to try different roms...
I really don't want to buy a new phone so if anyone has ANY ideas please right it down. Thanks in advance!
Click to expand...
Click to collapse
don't worry, you'll not have to buy another phone. Your issue is one of the most common issue we see here. First I will recommend you to use twrp 2.7.1.1 only to flash CM11 based roms and use twrp 2.6.3.3 or 2.6.3.4 for any Sense based roms.
You will first need to fix your drivers issue so you can adb push or adb sideload the rom to your phone again. there is a guide linked in my signature (nkk71's guide). In this thread, there is instruction (in the FAQ #2) about how to solve drivers issues.
When your drivers issue are solved, flash twrp 2.6.3.3:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then boot in twrp 2.6.3.3 and adb push or sideload venom and hopefully it will be able to boot and it will be stable.

alray said:
don't worry, you'll not have to buy another phone. Your issue is one of the most common issue we see here. First I will recommend you to use twrp 2.7.1.1 only to flash CM11 based roms and use twrp 2.6.3.3 or 2.6.3.4 for any Sense based roms.
You will first need to fix your drivers issue so you can adb push or adb sideload the rom to your phone again. there is a guide linked in my signature (nkk71's guide). In this thread, there is instruction (in the FAQ #2) about how to solve drivers issues.
When your drivers issue are solved, flash twrp 2.6.3.3:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then boot in twrp 2.6.3.3 and adb push or sideload venom and hopefully it will be able to boot and it will be stable.
Click to expand...
Click to collapse
The only weird thing is, I used the 2.7.1.1 to flash the sense rom in first place and everything worked fine :/ . Anyway, thanks for the shout! :good: I'll give it a try right now and see how it goes.

Right, I'm having problems installing the drivers for some reason. The ones downloaded from this thread don't seem to be doing anything at all. When click on them they show up for a split second in task manager and then they disappear. No install wizard no nothing. So i downloaded the ones for Windows 7 from here but this just gives me a message that "Windows could not find driver software for your device." . I mean, what the hell?
Edit: Right, after a lot of struggle I've managed to successfully bring my phone back to life! I have no idea what caused the issues with installing the drivers. I've spent ages deleting every trace of HTC drivers, then installed Windows 7 ones and somehow it worked. Then flashed t.w.r.p 2.6.3.3 and venom and it seems to be working smoothly! Hopefully no more problems . Thanks a lot for helping out man!

[Q] Deleted OS and can't install new ROM

Hi, I'll jump right into my issue, as in 3 hours of research I haven't found explanation on internet about my problem :crying:
I need to:
- Install a ROM on my HTC One (international)
I have done this:
- Installed driver in PC
- Unlocked, rooted, tampered
- Installed TWRP
- Wiped everything on the phone (stupidly) including OS, so I have only access to Bootloader and Recovery now
- Somehow the device is now S-ON, I'm not sure if it reverted by itself from S-OFF?
I have tried and doesn't work:
1. Mounting through recovery as MTP to add my ROM zip -> Cannot Copy, Its file size is larger than device limit
2. TWRP option "ADB Sideload" stuck at the screen "Starting ADB sideload feature..." infinitely
3. When running ADB Devices -> under "List of devices attached" is empty
As I've learned all of this just recently, I have incomplete knowledge about the entire process so please treat me like an idiot that I am. Thanks a lot!

zung0207 said:
Hi, I'll jump right into my issue, as in 3 hours of research I haven't found explanation on internet about my problem :crying:
I need to:
- Install a ROM on my HTC One (international)
I have done this:
- Installed driver in PC
- Unlocked, rooted, tampered
- Installed TWRP
- Wiped everything on the phone (stupidly) including OS, so I have only access to Bootloader and Recovery now
- Somehow the device is now S-ON, I'm not sure if it reverted by itself from S-OFF?
I have tried and doesn't work:
1. Mounting through recovery as MTP to add my ROM zip -> Cannot Copy, Its file size is larger than device limit
2. TWRP option "ADB Sideload" stuck at the screen "Starting ADB sideload feature..." infinitely
3. When running ADB Devices -> under "List of devices attached" is empty
As I've learned all of this just recently, I have incomplete knowledge about the entire process so please treat me like an idiot that I am. Thanks a lot!
Click to expand...
Click to collapse
Well it sounds like you just need to repair your drivers and push a Rom to the phone. What Windows version are you running on your pc?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
---------- Post added at 11:17 AM ---------- Previous post was at 11:14 AM ----------
About the s-on / s-off thing. If your phone is s-on then it probably always was. There is only one way to go to s-off to s-on and it requires a very specific fastboot command.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

You could also just grab a USB OTG cable. It's a really short (like, 2 inch long) cable that plugs into the micro-USB port on the phone and has a normal female USB port at the other end. With one of these, you could just copy the ROMs ZIP file onto a thumb drive and flash the ROM from recovery. I know TWRP supports OTG as this is the only way I install my ROMs and do my nandroid backups. It's totally worth the $3!
http://www.amazon.com/s/ref=nb_sb_noss?url=search-alias=aps&field-keywords=otg usb

zung0207 said:
Hi, I'll jump right into my issue, as in 3 hours of research I haven't found explanation on internet about my problem :crying:
I need to:
- Install a ROM on my HTC One (international)
I have done this:
- Installed driver in PC
- Unlocked, rooted, tampered
- Installed TWRP
- Wiped everything on the phone (stupidly) including OS, so I have only access to Bootloader and Recovery now
- Somehow the device is now S-ON, I'm not sure if it reverted by itself from S-OFF?
I have tried and doesn't work:
1. Mounting through recovery as MTP to add my ROM zip -> Cannot Copy, Its file size is larger than device limit
2. TWRP option "ADB Sideload" stuck at the screen "Starting ADB sideload feature..." infinitely
3. When running ADB Devices -> under "List of devices attached" is empty
As I've learned all of this just recently, I have incomplete knowledge about the entire process so please treat me like an idiot that I am. Thanks a lot!
Click to expand...
Click to collapse
OK bro what's your TWRP version? Because for some reason MTP and Sideload both didn't work for me on the newer versions but sideload worked great on 2.6.3.3

zung0207 said:
Hi, I'll jump right into my issue, as in 3 hours of research I haven't found explanation on internet about my problem :crying:
I need to:
- Install a ROM on my HTC One (international)
I have done this:
- Installed driver in PC
- Unlocked, rooted, tampered
- Installed TWRP
- Wiped everything on the phone (stupidly) including OS, so I have only access to Bootloader and Recovery now
- Somehow the device is now S-ON, I'm not sure if it reverted by itself from S-OFF?
I have tried and doesn't work:
1. Mounting through recovery as MTP to add my ROM zip -> Cannot Copy, Its file size is larger than device limit
2. TWRP option "ADB Sideload" stuck at the screen "Starting ADB sideload feature..." infinitely
3. When running ADB Devices -> under "List of devices attached" is empty
As I've learned all of this just recently, I have incomplete knowledge about the entire process so please treat me like an idiot that I am. Thanks a lot!
Click to expand...
Click to collapse
I've found MTP to still be a bit unreliable in twrp
use adb push, sideload, or USB-OTG as mentioned in the Frequently Asked Question sticky page 3
(it also mentions the driver problem)
PS: I also need to update that post, 2.8 series of twrp works fine for most ROMs, if you do get problems (such as with ARHD) then roll back to 2.6.3.3

Danny201281 said:
Well it sounds like you just need to repair your drivers and push a Rom to the phone. What Windows version are you running on your pc?
Click to expand...
Click to collapse
Ok thanks, will do the driver repair now, however the HTC Sync has been working fine up until I screwed things up, still need to repair? I'm using Win 8.1 for this.
synt3k said:
You could also just grab a USB OTG cable. It's a really short (like, 2 inch long) cable that plugs into the micro-USB port on the phone and has a normal female USB port at the other end. With one of these, you could just copy the ROMs ZIP file onto a thumb drive and flash the ROM from recovery. I know TWRP supports OTG as this is the only way I install my ROMs and do my nandroid backups. It's totally worth the $3!
Click to expand...
Click to collapse
Yes! I've got an OTG but doesn't seem to be working - either it's already broken or I don't know how Pls explain how to access OTG from TWRP if I've already placed my ROM .zip to USB?

ss4adib said:
OK bro what's your TWRP version? Because for some reason MTP and Sideload both didn't work for me on the newer versions but sideload worked great on 2.6.3.3
Click to expand...
Click to collapse
It's a new TWRP 2.8.0.2. I've just updated it last week or so. Everytime I restart the device from recovery, it keeps saying this device is unrooted and asks if I want to root even though I've done it on every previous restarts.
nkk71 said:
I've found MTP to still be a bit unreliable in twrp
use adb push, sideload, or USB-OTG as mentioned in the Frequently Asked Question sticky page 3
(it also mentions the driver problem)
PS: I also need to update that post, 2.8 series of twrp works fine for most ROMs, if you do get problems (such as with ARHD) then roll back to 2.6.3.3
Click to expand...
Click to collapse
Yep, I've tried all that as described in my first post (except the OTG which doesn't work), or do you mean something else?
----------------
Update:
If I boot in recovery and mount MTP, my "ADB Devices" command will recognize the phone, how do I take it from here?

zung0207 said:
It's a new TWRP 2.8.0.2. I've just updated it last week or so. Everytime I restart the device from recovery, it keeps saying this device is unrooted and asks if I want to root even though I've done it on every previous restarts.
Yep, I've tried all that as described in my first post (except the OTG which doesn't work), or do you mean something else?
----------------
Update:
If I boot in recovery and mount MTP, my "ADB Devices" command will recognize the phone, how do I take it from here?
Click to expand...
Click to collapse
I do recommend changing to TWRP 2.6.3.3 untill your up and running. Just because it's the most stable version right now.
If adb is detecting your device while in recovery that's good. You can just push your Rom. Rename your Rom file to rom.zip and bit it in your fastboot folder.
Boot your phone to recovery. And connect usb. (you don't need MTP for this) just on the TWRP home screen is fine. In the adb command line type
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes. Once it's done install the Rom with twrp.
Or to use your OTG first you must mount it in the Mounts options. Then you can access it with the TWRP file manager, or by selecting install then changing the working directory. At the top of the install options Select where it says Internal Storage and change it to OTG.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
I do recommend changing to TWRP 2.6.3.3 untill your up and running. Just because it's the most stable version right now.
If adb is detecting your device while in recovery that's good. You can just push your Rom. Rename your Rom file to rom.zip and bit it in your fastboot folder.
Boot your phone to recovery. And connect usb. (you don't need MTP for this) just on the TWRP home screen is fine. In the adb command line type
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes. Once it's done install the Rom with twrp.
Or to use your OTG first you must mount it in the Mounts options. Then you can access it with the TWRP file manager, or by selecting install then changing the working directory. At the top of the install options Select where it says Internal Storage and change it to OTG.
Click to expand...
Click to collapse
Ok, I will install TWRP 2.6.3.3 instead. My OTG cable is busted so that's out for now.
Also this method worked. When I pushed the ROM it was unresponsive, I had to wait for about 7 minutes until it finished.
So I've finished installing Android Revolution HD 81.0 as normal, throws me back to TWRP, but when rebooting to system it says "No OS installed! Are you sure you wish to reboot?" And sure enough, it's stuck at HTC One welcome screen for over 10 minutes.
Seems like there's progress, you've helped a lot but still can't drill it to the end

zung0207 said:
Ok, I will install TWRP 2.6.3.3 instead. My OTG cable is busted so that's out for now.
Also this method worked. When I pushed the ROM it was unresponsive, I had to wait for about 7 minutes until it finished.
So I've finished installing Android Revolution HD 81.0 as normal, throws me back to TWRP, but when rebooting to system it says "No OS installed! Are you sure you wish to reboot?" And sure enough, it's stuck at HTC One welcome screen for over 10 minutes.
Seems like there's progress, you've helped a lot but still can't drill it to the end
Click to expand...
Click to collapse
Mmm! That's strange should install fine with 2.6.3.3. Did you notice any errors during install. Specifically "set_medata_recursive - some changes failed"
Check the md5 of your ARHD download also. You can get a free tool from www.winmd5.com to do that. If the md5 is correct and you see no errors during install.
You can try formatting data in TWRP this will however completely wipe the entire device. Including internal storage. So you will need to push the Rom again.
Also bare in mind it can take up to 15 to 20 mins to pass the HTC logo screen after a clean install. But seeing the No OS installed message is not normal
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Mmm! That's strange should install fine with 2.6.3.3. Did you notice any errors during install. Specifically "set_medata_recursive - some changes failed"
Click to expand...
Click to collapse
Yes! That did happen at the end of my installation. Should I be worried about that?
I'm not familiar with md5 - downloaded and installed it, but clueless about how to use this thing.
The installation was done in previous TWRP, I'm flashing 2.6.3.3 now and will try install ROM again.

zung0207 said:
Yes! That did happen at the end of my installation. Should I be worried about that?
I'm not familiar with md5 - downloaded and installed it, but clueless about how to use this thing.
The installation was done in previous TWRP, I'm flashing 2.6.3.3 now and will try install ROM again.
Click to expand...
Click to collapse
Set meta data recursive means you've used the wrong recovery to install the Rom.
Just flash it with 2.6.3.3 you'll have no problems
EDIT :- for the record MD5 checking should always be done before flashing files to your phone to avoid flashing a corrupt zip or img. MD5 checksum values are normally posted with the download. This is the correct md5 for ARHD 81.
Code:
[SIZE="6"]Android Revolution HD 81.0[/SIZE]
[SIZE="2"]--- [I]MD5 Checksum: 9985BFD22A695AEA7A43BC7E0EB42DBC[/I] ---[/SIZE]
paste the long code into the appropriate box in the checker tool and drag and drop the file on the tool then click verify. It will tell you if they match. If they don't match get a new download
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

zung0207 said:
Hi, I'll jump right into my issue, as in 3 hours of research I haven't found explanation on internet about my problem :crying:
I need to:
- Install a ROM on my HTC One (international)
I have done this:
- Installed driver in PC
- Unlocked, rooted, tampered
- Installed TWRP
- Wiped everything on the phone (stupidly) including OS, so I have only access to Bootloader and Recovery now
- Somehow the device is now S-ON, I'm not sure if it reverted by itself from S-OFF?
I have tried and doesn't work:
1. Mounting through recovery as MTP to add my ROM zip -> Cannot Copy, Its file size is larger than device limit
2. TWRP option "ADB Sideload" stuck at the screen "Starting ADB sideload feature..." infinitely
3. When running ADB Devices -> under "List of devices attached" is empty
As I've learned all of this just recently, I have incomplete knowledge about the entire process so please treat me like an idiot that I am. Thanks a lot!
Click to expand...
Click to collapse
I really have the same problem but my own is s-off seem as your is solve a help please

[Q] 5.0.1 and ADB not finding device

OMG!!! I've hit the end of my rope with this. Let me start off by saying I don't post things, I find answers to them but this problem is killing me.
I have a Sprint Nexus 6 that I am trying to update to 5.0.1. However its being terrible, I reboot into bootloader with with power and volume - or adb reboot bootloader, and attempt to adb sideload (updatefile.zip) and error device not found. I do adb devices and sure enough its not there, however fastboot devices shows it. If I reboot into the OS and issue ADB devices OH **** THERE IS MY PHONE, adb reboot bootloader, and its gone again.
I've tried drivers froom google search direct google usb drivers, naked drivers 0.73, I've uninstalled inside of the os and reinstalled I've uninstalled in bootloader and reinstalled nothing works. I can issue fastboot commands but adb just eats a bag of ****. I also have an issue where adb gives an error that it is out of date and must restart, it then restarts and everything is peachy. I've tried to download something called adb fix, but it says there is nothing wrong. So I have no idea what is going on and if anyone could possibly help me get my phone updated so this notification goes away and I don't go into an OCD rage on everyone around me I would be much appreciative.
Side note
I cannot update via ota, no idea why it says installing then just errors out, I assumed it was because of the unlock, also when I'm in bootloader and I attempt to go into recovery there is just an android dude with his chest open. Now its been a while since I've had a nexus but shouldn't there be like a menu or something there? I also did the whole no encrypt boot.img nonsense here. I thought that was the problem so wiped data and flashed the stock boot.img... I'm seriously out of ideas......

well first off you have the stock recovery... that is the android dude.
I dont really have answers for you but the two things i would try would be a different computer and just using WUG http://www.wugfresh.com/nrt/ i have had issues in the past using an old ADB/fastboot.
If you have modified anything the OTA is going to fail.

Tried on two different computers,I'll try wug. Thanks

first, make sure that you can see the device when it's booted up (assuming usb debug is enabled and the computer is trusted).
other than that, i'm not sure what to say as i've never had that problem (i don't use the updater.zip files though). might be best to just flash the whole 5.0.1 image (minus the cache and userdata).

Maybe I am reading this wrong, but you are trying to adb while in the bootloader?

PaisanNYC said:
Maybe I am reading this wrong, but you are trying to adb while in the bootloader?
Click to expand...
Click to collapse
If you're reading it wrong so am I. Definitely sounds like he is incorrectly trying to use Adb in the bootloader.
---------- Post added at 11:15 PM ---------- Previous post was at 11:13 PM ----------
Lucke said:
first, make sure that you can see the device when it's booted up (assuming usb debug is enabled and the computer is trusted).
other than that, i'm not sure what to say as i've never had that problem (i don't use the updater.zip files though). might be best to just flash the whole 5.0.1 image (minus the cache and userdata).
Click to expand...
Click to collapse
USB debug mode has nothing to do with boot loader or recovery. I'm sure you know this as you said it when booted, but many will read this and think you need debug in recovery or bootloader which wouldn't be true.

No PC connection with adb/sync, fastboot works.

Hi guys,
I am trying to help out a mate and unfortunately dont have much experience with HTC's.
This is where i stand...phone wont be recognized in normal boot, nor in TWRP, so adb is not working at all. FASTBOOT works.
i have been circling around with locking and unlocking the bootloader to try out all the methods of updating the system, RUU fails with error 155. when unlocking, supercid fails with some java error.
To get S-OFF, i definitely need adb to load the "much talked for" file, but that is impossible right now.
RUU normal way fails as i said above, so does FUU with rom.zip (found away to get it out of exe, so it is untouched) as soon as it "updates signatures" it'll fail, I even use the fastboot command with the renamed file firmware.zip ends up saying it cannot verify partition ...adding zip after flash command says file is out of size
I am on 4.20.651.10, and trying to get the latest package, and am out of ideas. I found out the hard way that if i lock back the phone, it wont boot to TWRP and nor on a modified system.
I am really not sure what to do, having adb on would've spared me a lot of trouble. Friend says the USB port has been changed twice, it is so odd to have fastboot and not even a single refresh in Device Manager when i plug the damn phone on...

There are more replies to question threads outside the Help section then in here...
Anyway, i lost fastboot too, and no idea why. tried in two pc's, one of them with 3 different os's, tried two macs, tried even an OTG cable with my other android phone, nothing.
I cant even relock the phone so i can update through the RUU ZIP in the sdcard, but that's a scratched off solution if no USB connection is delivered.
I even tried the S-Off unlocking file on /data/local/tmp, but it doesnt seem to execute from TWRP terminal, and ofc it wont through a booted system either...
I managed to install a custom rom since i have no OS, and tried the "AndroidHtcSync.apk" solution to no avail
i seriously hope anyone has the will to help me...
EDIT: port is definitely fine, as the phone charges from the charger, and fastboot shows "fastboot ac".
EDIT2: fastboot is back... renamed the zip in sdcard, now it fails flashing there too with "Device halted due to large image update fail"