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

Phone is essentially bricked

Okay, I have the HTC One for Sprint. I flashed it using TWRP 2.5 and I can only currently access the bootloader.
I accidentally wiped everything off my phone and when I plug it in my computer sometimes recognizes it has HTCONE or as Android Device, either way I cannot send files over using adb sideload. Gives me the error that there is no device.
Currently my device somehow also got "unrooted" in the process. I am looking at the phone not being able to transfer any roms I want over to install a new OS nor can I restore it to the old OS.
Is there anything I can do?
PS: I did install the drivers and other devices. If someone can please help me even over teamviewer it would absolutely make my day. I have been troubleshooting this device for about 30 hours straight now.

Since you can access bootloader, you'll probably be ok..
What happens when you try to access recovery?
what happens in "fastboot usb" in your bootloader when you command
Code:
fastboot devices
If your device shows just do
Code:
fastboot flash recovery name_of_recovery.img
Download one of these recoveries (since you have the Sprint version) <- this will get you into recovery if you're not already able to access it..
http://techerrata.com/browse/twrp2/m7wls

yup
redbull123 said:
Since you can access bootloader, you'll probably be ok..
What happens when you try to access recovery?
what happens in "fastboot usb" in your bootloader when you command
Code:
fastboot devices
If your device shows just do
Code:
fastboot flash recovery name_of_recovery.img
Download one of these recoveries (since you have the Sprint version) <- this will get you into recovery if you're not already able to access it..
Click to expand...
Click to collapse
Well I have the recovery since thats the only one I can access. Thing is though neither of my computers can recognize the device and I cannot send the rom necessary to boot the OS.
I can access the Bootloader and I can access the Recovery. I cannot access the memory on the phone in order to send files over

Have you tried flashing the RUU? Hopefully this can help:
http://forum.xda-developers.com/showthread.php?t=2250904

sweetnsour said:
Have you tried flashing the RUU? Hopefully this can help:
http://forum.xda-developers.com/showthread.php?t=2250904
Click to expand...
Click to collapse
would I be able to unlock the bootloader after

iivezaj said:
would I be able to unlock the bootloader after
Click to expand...
Click to collapse
important part is getting the phone working again then worry about unlocking bootloader

Can always try flashing a custom ROM using an OTG cable if you've wiped the OS. I always wipe my storage and OS when I do a clean install and then flash the ROM straight from my flash drive ... Obviously you'll need to fastboot a custom recovery, if you are able to.

CheesyNutz said:
important part is getting the phone working again then worry about unlocking bootloader
Click to expand...
Click to collapse
im going to try the method you linked me

When you're in recovery do adb devices. If it shows your phone you can sideload a ROM.
AT&T HTC One
GPe 4.3

hi bro, that happened to me as well, i have installed usb driver but adb cannot detect my device. I was running windows 8 that time but when i used windows 7 adb was able to detect my device with no issues and i was able to transfer custom rom zip file to it. I dont know if that could help you but i'm just sharing my experience.
Sent from my IRON Phone
---------- Post added at 10:32 PM ---------- Previous post was at 10:27 PM ----------
can you even go to recovery? if yes, try using other computer, preferably windows 7 or xp.
Sent from my IRON Phone
---------- Post added at 10:39 PM ---------- Previous post was at 10:32 PM ----------
sorry i didnt read this.
Sent from my IRON Phone

I can access the bootloader and the recovery (switched to PhilZ touch) and sideloaded a couple roms but NONE of them work. One of the roms boots up and goes in a restart loop after hitting the front page (no icons on the screen just top bar) Even the stock version of htc one for sprint didn't work it kept resetting my device.
I tried using the RUU also but it gives me a bootloader error saying it cannot be restored after a few minutes of loading.

Well every rom so far attempted has been a dead end. CM, AOKP, all have booted and started a restart loop. I am not sure if its my kernal or anything else.
I just need some help. What I did notice is that even if the devices were working I had no cell signal. Someone please help lol

iivezaj said:
Well every rom so far attempted has been a dead end. CM, AOKP, all have booted and started a restart loop. I am not sure if its my kernal or anything else.
I just need some help. What I did notice is that even if the devices were working I had no cell signal. Someone please help lol
Click to expand...
Click to collapse
Where are you getting these ROMs from? Have you tried the ones in the Sprint HTC One forums?
Sent from my HTC One using xda premium

[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.

Nexus 6 Marshmallow stuck in fastboot loop

I have a relatively new Nexus 6. The last phone that I rooted was the old HTC Hero, and things have changed! I had unlocked the bootloader and rooted the phone under 5.1.1 and when I flashed Marshmallow 6.0 yesterday I lost root.
So I decided that I would try to root the phone again. I had problems with the drivers... my PC would recognize the phone when it was powered up normally but as soon as I booted into fastboot I couldn't get ADB to find it.
Then I went to this link: http://www.theandroidsoul.com/marshmallow-root-for-nexus-5-6-7-9-and-player-by-chainfire-84862/
got my fastboot and adb set up and working, followed his instructions to get root, flashed the twrp image, and flashed the SuperSU file. Everything seemed to work properly. Made a complete backup using twerp and transferred it to my PC via USB.
After all this a tap on Reboot System was supposed to restart the phone. Didn't happen.
I'm stuck in a fastboot recovery loop. Whenever I power down and try to turn the phone on I come back to the fastboot screen. When I elect to go into "recovery" it opens the twrp screen on my phone which asks for my pin and then I have the twrp screen with the regular options.
This is new to me... I don't know if access to the twrp screen and its commands is a help or not, but I do realize that the adb and fastboot on my PC is necessary for about anything I need to do and it seems to be working. I believe that I've described my situation accurately...
Any help appreciated!

turnagerg said:
I have a relatively new Nexus 6. The last phone that I rooted was the old HTC Hero, and things have changed! I had unlocked the bootloader and rooted the phone under 5.1.1 and when I flashed Marshmallow 6.0 yesterday I lost root.
So I decided that I would try to root the phone again. I had problems with the drivers... my PC would recognize the phone when it was powered up normally but as soon as I booted into fastboot I couldn't get ADB to find it.
Then I went to this link: http://www.theandroidsoul.com/marshmallow-root-for-nexus-5-6-7-9-and-player-by-chainfire-84862/
got my fastboot and adb set up and working, followed his instructions to get root, flashed the twrp image, and flashed the SuperSU file. Everything seemed to work properly. Made a complete backup using twerp and transferred it to my PC via USB.
After all this a tap on Reboot System was supposed to restart the phone. Didn't happen.
I'm stuck in a fastboot recovery loop. Whenever I power down and try to turn the phone on I come back to the fastboot screen. When I elect to go into "recovery" it opens the twrp screen on my phone which asks for my pin and then I have the twrp screen with the regular options.
This is new to me... I don't know if access to the twrp screen and its commands is a help or not, but I do realize that the adb and fastboot on my PC is necessary for about anything I need to do and it seems to be working. I believe that I've described my situation accurately...
Any help appreciated!
Click to expand...
Click to collapse
how about this, adb NEVER EVER works in fastboot mode. that is reserved exclusively for fastboot. you have to use fastboot to flash a recovery, then the recovery to flash supersu.
---------- Post added at 04:49 PM ---------- Previous post was at 04:48 PM ----------
now it also seems as you have to fastboot flash a factory image as well.

turnagerg said:
I have a relatively new Nexus 6. The last phone that I rooted was the old HTC Hero, and things have changed! I had unlocked the bootloader and rooted the phone under 5.1.1 and when I flashed Marshmallow 6.0 yesterday I lost root.
So I decided that I would try to root the phone again. I had problems with the drivers... my PC would recognize the phone when it was powered up normally but as soon as I booted into fastboot I couldn't get ADB to find it.
Then I went to this link: link removed to satisfy forum policy...
got my fastboot and adb set up and working, followed his instructions to get root, flashed the twrp image, and flashed the SuperSU file. Everything seemed to work properly. Made a complete backup using twerp and transferred it to my PC via USB.
After all this a tap on Reboot System was supposed to restart the phone. Didn't happen.
I'm stuck in a fastboot recovery loop. Whenever I power down and try to turn the phone on I come back to the fastboot screen. When I elect to go into "recovery" it opens the twrp screen on my phone which asks for my pin and then I have the twrp screen with the regular options.
This is new to me... I don't know if access to the twrp screen and its commands is a help or not, but I do realize that the adb and fastboot on my PC is necessary for about anything I need to do and it seems to be working. I believe that I've described my situation accurately...
Any help appreciated!
Click to expand...
Click to collapse
I asked for help before searching thoroughly enough! I figured out that I needed to download another ROM, transfer it into the phone's storage, and install using TWRP. I really didn't understand the capabilities of this fabulous application and had simply flashed it because the thread instructed me to.

Htc desire 626s Stock ROM

Hi, recently I owned my HTC desire 626s but when I was unlocking bootloader and rooting accidentally I broke the system and now sends failure messages all time. could someone make a clean rom stock backup and upload it for flash it?

Could use one too
AlexLeonVader said:
Hi, recently I owned my HTC desire 626s but when I was unlocking bootloader and rooting accidentally I broke the system and now sends failure messages all time. could someone make a clean rom stock backup and upload it for flash it?
Click to expand...
Click to collapse
This would also help me out as i accidentally deleted os while trying to reset with twrp.

Lol... Back up is 5gb.. Not only that, TWRP for this device as of now has bugs and will break root after nandroid restore. Download RUU from HTC website put RUU in adb folder and put phone into download mode. Thru adb type in "fastboot oem rebootRUU". Run RUU on PC (DO NOT UNPLUG USB). Process takes about 10-15mins so be patient and your phone will be back to stock.

I tried it and it finished way to fast. The device is not in adb devices. After accidentaly trying to reset thru twrp now my device wont show up untill i boot into twrp. Any idea of whats wrong. I have the right files in the same location as adb. I have the updates htc drivers for my device.
After typing fastboot oem rebootRUU all i got was a silver htc logo with a security warnig about non htc roms.

f1tzg3r4ld said:
I tried it and it finished way to fast. The device is not in adb devices. After accidentaly trying to reset thru twrp now my device wont show up untill i boot into twrp. Any idea of whats wrong. I have the right files in the same location as adb. I have the updates htc drivers for my device.
After typing fastboot oem rebootRUU all i got was a silver htc logo with a security warnig about non htc roms.
Click to expand...
Click to collapse
Yea ur on the right path. Now open RUU file and let it load and execute on your PC and it should restore stock metro rom. Process takes awhile so be patient

kdayyy said:
Yea ur on the right path. Now open RUU file and let it load and execute on your PC and it should restore stock metro rom. Process takes awhile so be patient
Click to expand...
Click to collapse
After I run ruu.exe for my device nothing happens. I let it sit for an hour. I think I can get this fixed but after accidentally deleting things with twrp tryign to reset now my device is not recognized by adb. I reinstalled the stock recovery thinking that might help and it didnt. I was able to get the rom.zip extracted from the ruu. Do you know what steps I would take to install the rom with the stock recovery. Or do you know how I can reinstall twrp. This phone is about to get thrown against the wall. Its my stupidy for nopt backing up before trying to reset.

f1tzg3r4ld said:
After I run ruu.exe for my device nothing happens. I let it sit for an hour. I think I can get this fixed but after accidentally deleting things with twrp tryign to reset now my device is not recognized by adb. I reinstalled the stock recovery thinking that might help and it didnt. I was able to get the rom.zip extracted from the ruu. Do you know what steps I would take to install the rom with the stock recovery. Or do you know how I can reinstall twrp. This phone is about to get thrown against the wall. Its my stupidy for nopt backing up before trying to reset.
Click to expand...
Click to collapse
Put ur phone in download mode if adb can detect in twrp than it should detect in download mode. It's not gonna show on ur PC that it's detected. Just connected and see if adb work in download mode. Same process download mode and type in "fastboot oem rebootRUU" when it goes to silver HTC logo screen open RUU and run it on your PC make sure you have metropcs RUU
---------- Post added at 09:51 AM ---------- Previous post was at 09:36 AM ----------
Stock recovery doesn't do anything. And why are you extracting RUU? It's not meant to be extracted but to run and execute on adb thru PC

kdayyy said:
Put ur phone in download mode if adb can detect in twrp than it should detect in download mode. It's not gonna show on ur PC that it's detected. Just connected and see if adb work in download mode. Same process download mode and type in "fastboot oem rebootRUU" when it goes to silver HTC logo screen open RUU and run it on your PC make sure you have metropcs RUU
Click to expand...
Click to collapse
I have the stock recovery now and cant figure out how to put twrp back on the phone. Ok put it into download mode and ran
C:\HTC626s>adb devices
List of devices attached
C:\HTC626s>fastboot oem rebootRUU
...
OKAY [ 0.053s]
finished. total time: 0.054s
C:\HTC626s>
as you can see adb doesnt recognize the device. Once the ruu starts the install sheild it loads, I accept terms of the licence and hit next, Then nothing happens. It just sits on ther silver htc logo screen and the ruu installer never shows back up.
https://drive.google.com/file/d/0B7_8Xh6NIsIPOUxFbXNEcnZzTlE/view?usp=sharing
https://drive.google.com/file/d/0B7_8Xh6NIsIPQVkya19vSlBpTmc/view?usp=sharing
When I was trying to reset my phone using TWRP i selected everything and hit wipe. Thats how I got into this mess. Does that tell you anything.

f1tzg3r4ld said:
I have the stock recovery now and cant figure out how to put twrp back on the phone. Ok put it into download mode and ran
C:\HTC626s>adb devices
List of devices attached
C:\HTC626s>fastboot oem rebootRUU
...
OKAY [ 0.053s]
finished. total time: 0.054s
C:\HTC626s>
as you can see adb doesnt recognize the device. Once the ruu starts the install sheild it loads, I accept terms of the licence and hit next, Then nothing happens. It just sits on ther silver htc logo screen and the ruu installer never shows back up.
https://drive.google.com/file/d/0B7_8Xh6NIsIPOUxFbXNEcnZzTlE/view?usp=sharing
https://drive.google.com/file/d/0B7_8Xh6NIsIPQVkya19vSlBpTmc/view?usp=sharing
Click to expand...
Click to collapse
It actually is detected because ur cmd says "<C:\HTC626s>" meaning it's in adb mode and connected. Make sure RUU file is in adb folder. The RUU takes awhile to run. And window will disappear after proceeding, and will run in the PC background and takes approximately 10-20 mins. Took a good 15 mins for me and I don't have the best PC
---------- Post added at 10:17 AM ---------- Previous post was at 10:05 AM ----------
f1tzg3r4ld said:
I have the stock recovery now and cant figure out how to put twrp back on the phone. Ok put it into download mode and ran
C:\HTC626s>adb devices
List of devices attached
C:\HTC626s>fastboot oem rebootRUU
...
OKAY [ 0.053s]
finished. total time: 0.054s
C:\HTC626s>
as you can see adb doesnt recognize the device. Once the ruu starts the install sheild it loads, I accept terms of the licence and hit next, Then nothing happens. It just sits on ther silver htc logo screen and the ruu installer never shows back up.
https://drive.google.com/file/d/0B7_8Xh6NIsIPOUxFbXNEcnZzTlE/view?usp=sharing
https://drive.google.com/file/d/0B7_8Xh6NIsIPQVkya19vSlBpTmc/view?usp=sharing
When I was trying to reset my phone using TWRP i selected everything and hit wipe. Thats how I got into this mess. Does that tell you anything.
Click to expand...
Click to collapse
I've wiped everything before. This is my second HTC device. I had a desire510. Either flash a stable custom ROM which 626s don't have any, or run RUU thru adb is your only option.

I figured it out Thansk for your help I had to run cmd as admin and install this
Microsoft Visual C++ 2008 Redistributable Package (x86)

Because you have the wrong ruu download sprint ruu
:angel::angel:
f1tzg3r4ld said:
After I run ruu.exe for my device nothing happens. I let it sit for an hour. I think I can get this fixed but after accidentally deleting things with twrp tryign to reset now my device is not recognized by adb. I reinstalled the stock recovery thinking that might help and it didnt. I was able to get the rom.zip extracted from the ruu. Do you know what steps I would take to install the rom with the stock recovery. Or do you know how I can reinstall twrp. This phone is about to get thrown against the wall. Its my stupidy for nopt backing up before trying to reset.
Click to expand...
Click to collapse

It Works.
kdayyy said:
Put ur phone in download mode if adb can detect in twrp than it should detect in download mode. It's not gonna show on ur PC that it's detected. Just connected and see if adb work in download mode. Same process download mode and type in "fastboot oem rebootRUU" when it goes to silver HTC logo screen open RUU and run it on your PC make sure you have metropcs RUU
---------- Post added at 09:51 AM ---------- Previous post was at 09:36 AM ----------
Stock recovery doesn't do anything. And why are you extracting RUU? It's not meant to be extracted but to run and execute on adb thru PC
Click to expand...
Click to collapse
I created an account to thank you. Your method worked for me. Thank you so much. My device was soft-bricked from wiping with Cyanogen Recovery. I was stressed out all week looking for a solution and finally found your solution that worked for me. Thank you.

kdayyy said:
Lol... Back up is 5gb.. Not only that, TWRP for this device as of now has bugs and will break root after nandroid restore. Download RUU from HTC website put RUU in adb folder and put phone into download mode. Thru adb type in "fastboot oem rebootRUU". Run RUU on PC (DO NOT UNPLUG USB). Process takes about 10-15mins so be patient and your phone will be back to stock.
Click to expand...
Click to collapse
i know this is an old post but ruu for unlocked 626 is not available on its official website