Develop Bugs

Help, soft bricked my device.

I was attempting to unlock/root and long story short, now I have TWRP installed, and I can get to FASTBOOT but if i try to boot normally I get the Nexus logo, and no further. When I unlocked, I installed TWRP then loaded it. After leaving TWRP it said 'Seems you are not rooted, want to root"? or something to that effect. I clicked YES and now I'm stuck. Since I had just unlocked it, it *should* have reset my entire device(which was all stock anyway) so I am not sure what went wrong. I have been trying everything I know but I'm now out of ideas. Would appreciate any help. I see now that the version of SuperSu that it would have pushed would have been wrong, would that be preventing the tablet from booting?

If you can mount in fastboot you're not bricked. You tried to check md5 and push the recovery image again? And also try to throw new ROM on it.
Sent from my HTC One using xda app-developers app

ronni.rasmussen said:
If you can mount in fastboot you're not bricked. You tried to check md5 and push the recovery image again? And also try to throw new ROM on it.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
It wont boot so I don't know how to put anything on it, it's empty and doesn't show up in windows. Also I don't know what you meant exactly by push the recovery image again. Twrp is working fine. Sorry I am hardly a pro at this stuff.

Landara said:
It wont boot so I don't know how to put anything on it, it's empty and doesn't show up in windows. Also I don't know what you meant exactly by push the recovery image again. Twrp is working fine. Sorry I am hardly a pro at this stuff.
Click to expand...
Click to collapse
Try to get to fastboot and connect PC and check if it connects. You will need the USB drivers installed
Sent from my HTC One using xda app-developers app

ronni.rasmussen said:
Try to get to fastboot and connect PC and check if it connects. You will need the USB drivers installed
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.

Landara said:
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.
Click to expand...
Click to collapse
Then it should be possible to flash and push recovery and ROM to device even get a stock image back.
Which recovery image did you install?
And did you flash any ROM or kernel?
Sent from my HTC One using xda app-developers app

Landara said:
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.
Click to expand...
Click to collapse
I would suggest you just restore your N7 back to stock. No need for root yet, seriously! But this should help get you going in the right direction.
Power it off completely. Hold Power + Volume down until it boots into the bootloader. Run the following commands:
fastboot devices (to confirm you are connected)
fastboot flash recovery recovery.img
If you haven't unlocked your N7 yet, run fastboot oem unlock first.

ronni.rasmussen said:
Then it should be possible to flash and push recovery and ROM to device even get a stock image back.
Which recovery image did you install?
And did you flash any ROM or kernel?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I put TWRP on there, immediately after unlocking. So it should have been completely stock since as far as I know it wipes it when you unlock. After putting TWRP on there, i told it to reboot normally(from within TWRP) and it detected that I was not rooted and asked me if I wanted to install SuperSu. I said yes and now it will not boot to the operating system. It boots fine to Bootloader and Recovery. And I am certain it's connected to my PC because I can even tell it ADB REBOOT BOOTLOADER/RECOVERY and that works. But I don't see how I can load a ROM onto it if I can't access it via windows. I don't know how to get a ROM onto the SD card. Surely there could be a way but I don't know it.

Landara said:
I put TWRP on there, immediately after unlocking. So it should have been completely stock since as far as I know it wipes it when you unlock. After putting TWRP on there, i told it to reboot normally(from within TWRP) and it detected that I was not rooted and asked me if I wanted to install SuperSu. I said yes and now it will not boot to the operating system. It boots fine to Bootloader and Recovery. And I am certain it's connected to my PC because I can even tell it ADB REBOOT BOOTLOADER/RECOVERY and that works. But I don't see how I can load a ROM onto it if I can't access it via windows. I don't know how to get a ROM onto the SD card. Surely there could be a way but I don't know it.
Click to expand...
Click to collapse
Start over by downloading recovery, Superuser and a clean stock rom image.
But before that you could try to reset all data in recovery (factory reset) and cache if you haven't tried.

http://forum.xda-developers.com/showthread.php?t=2380913
Thanks to this thread I have booted! Still have to root it but now that I know that you have to flash the NEW SuperSu not the one TWRP flashed for me, I shouldn't have a problem Thanks so much for your help everyone!

Landara said:
http://forum.xda-developers.com/showthread.php?t=2380913
Thanks to this thread I have booted! Still have to root it but now that I know that you have to flash the NEW SuperSu not the one TWRP flashed for me, I shouldn't have a problem Thanks so much for your help everyone!
Click to expand...
Click to collapse
Super

[Q] S-Off Recovery problem

Hello! Hi, I'm kinda new to all of this, and I downloaded all of this today. I've been reading a lot and watching a lot of videos, yet I nothing really seems to fix my devices problem.
I have a HTC One on the Verizon carrier and I have just recently S-Off'd it using Rumrunner (I used the Rom checker to make sure it was unlocked and it even says it is whenever i enter bootloader). Although I was successfully able to unlock my device, I seem to have trouble with entering into recovery mode. Whenever I try to go into Recovery mode, my device reads "Entering Recovery mode" in pink at the top for about 10-20 seconds. Then all of a sudden it just goes black and it reboots as if I had never even chosen to go into recovery mode. I don't know if this holds any significance, but I've noticed that my boot up logo only has "HTC ONE" on it, the writing "simply beautiful" is now removed.
I have tried using cmd and ADB to clear the cache, I've tried using ClockManager from Rom Manager, and I've tried multiple times on regular mode. None of them really seem to work and I don't really understand why. Can anyone please offer me some suggestions? Thank you.
Seriously I only want a transparent theme for my HTC One that's all LOL

@Cinestra hey so I'm also kind of new to this but I can try to help. So what custom recovery did you flash?

Chilidog said:
@Cinestra hey so I'm also kind of new to this but I can try to help. So what custom recovery did you flash?
Click to expand...
Click to collapse
I think the person didn't flash one. Flash twrp through fastboot. Don't use ROM manager cwm is getting old
Sent from my HTC6500LVW using xda app-developers app

cstrife999 said:
I think the person didn't flash one. Flash twrp through fastboot. Don't use ROM manager cwm is getting old
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Hello, thank you i very much appreciate your advice. I did not try flashing yet.
I just tried to flash TWRP by using Fastboot and the CMD. However I still get no luck. I entered everything in the command prompt fine and it responded nicely. However, whenever I try to go to Recovery mode, the screen just says "entering recovery mode...." and then just turns black 15 seconds later and reboots again :S

Cinestra said:
Hello, thank you i very much appreciate your advice. I did not try flashing yet.
I just tried to flash TWRP by using Fastboot and the CMD. However I still get no luck. I entered everything in the command prompt fine and it responded nicely. However, whenever I try to go to Recovery mode, the screen just says "entering recovery mode...." and then just turns black 15 seconds later and reboots again :S
Click to expand...
Click to collapse
Hmm... That is strange indeed...
Sent from my HTC6500LVW using xda app-developers app

I had the same problem and discovered that when i enter stock recovery, when the black screen appears, i had to press power+vol up to get it to show up. You may have to press them several times to get the timing right. Hope that helps!

cstrife999 said:
I think the person didn't flash one. Flash twrp through fastboot. Don't use ROM manager cwm is getting old
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
when I got my phone back from sonic, twrp wouldn't install for me so I had to use CWM.
OP should probably try both and make sure he's following the instructions here:
http://forum.xda-developers.com/showpost.php?p=45513789&postcount=2

I'm quite new to rooting as well. Seems we are having the same problem. I was able to get beaups' s-off exploit to work without any problems. When I load into HBoot it says the phone is unlocked and I've also used a Root Checker to determine the phone is rooted.
My next step was to try and install TWRP using fastboot. I ran a command prompt window using administrator rights during the whole process. Everything seemed to install just as it should. The problem is when I try to boot into recovery I'm having the same problem as Cinestra. I simply get the HTC logo screen with "Entering Recovery..." in pink letters at the top of the screen for around 15 seconds, then it reboots as if it would normally and restart the phone as usual. I have tried to reinstall the custom recovery step by step, using 'fastboot erase cache' before and after as well as using an older version of TWRP just in case that would help. Again, everything seems to install just fine but I still can not boot into recovery. I've also tried to see if the GooManager app would be of some help, but that is also not working for me.
I've since also tried flashing CWM but the same situation occurs. Install seems fine but no luck booting into recovery. ROM Manager was a no go as well.
I just can't figure this out. I've tried different cables, deleted and reinstalled HTC drivers/adb/fastboot, and multiple recovery images. I just gave beasleyj62's suggestion of holding down the power/volume down buttons after it goes to black when it starts to restart but that just put me into a bootloop sadly. Had to hold down the power button a few times to get it to boot correctly again. Any help on this would be greatly appreciated. Cheers.
I would also just like to add a little more info on my device in case this will help troubleshoot this. I'm using a Verizon HTC One with Software Number 1.10.605.10.

Same problem here. Tried flashing from fastboot, using goomanager, using rom manager, and from within the terminal emulator (can't find the command now but i think it was on the TWRP site).
Fastboot gives every indication it works, goomanager and rom manager give an error, and the emulator method appeared to work.
Tried to fastboot both TWRP and clockworkmod but neither worked.
At work right now but still investigating...
*edit: goomanager error states 'no recoveries found for your device.'

carassius-one said:
Same problem here. Tried flashing from fastboot, using goomanager, using rom manager, and from within the terminal emulator (can't find the command now but i think it was on the TWRP site).
Fastboot gives every indication it works, goomanager and rom manager give an error, and the emulator method appeared to work.
Tried to fastboot both TWRP and clockworkmod but neither worked.
At work right now but still investigating...
*edit: goomanager error states 'no recoveries found for your device.'
Click to expand...
Click to collapse
ROM manager and goomanager are not supported you have to flash Twrp or CWM via fastboot
Sent from my HTC6500LVW using XDA Premium 4 mobile app
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
I wonder if you guys are having problems because you tried to use rom manager or goomanager and it messed something up...
Sent from my HTC6500LVW using XDA Premium 4 mobile app

Chilidog said:
ROM manager and goomanager are not supported you have to flash Twrp or CWM via fastboot
Click to expand...
Click to collapse
Thanks. That answers that part of the question.

Chilidog said:
ROM manager and goomanager are not supported you have to flash Twrp or CWM via fastboot
Sent from my HTC6500LVW using XDA Premium 4 mobile app
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
I wonder if you guys are having problems because you tried to use rom manager or goomanager and it messed something up...
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Didn't realize they weren't supported. Sadly, I don't think they are the culprit here. I tried to flash using fastboot first. I attempted it with 'openrecovery-twrp-2.6.3.0-m7.img' first then with the older version 'openrecovery-twrp-2.6.1.0-m7.img' next. It was the same issue with both. I didn't attempt using GooManager until after I had used fastboot, though GooManager just failed to initialize the install. I mean it didn't even run or change anything as far as I can tell, and simply gave an error back saying "No recoveries were found for your advice".
Did the same thing with CWM and ROM Manager. I installed CWM from fastboot. Only after seeing the same thing happen when I tried to install TWRP did I give ROM Manager a shot. This also just gave an error message without initializing any install. Thanks for the input though.

Prizm432 said:
Didn't realize they weren't supported. Sadly, I don't think they are the culprit here. I tried to flash using fastboot first. I attempted it with 'openrecovery-twrp-2.6.3.0-m7.img' first then with the older version 'openrecovery-twrp-2.6.1.0-m7.img' next. It was the same issue with both. I didn't attempt using GooManager until after I had used fastboot, though GooManager just failed to initialize the install. I mean it didn't even run or change anything as far as I can tell, and simply gave an error back saying "No recoveries were found for your advice".
Did the same thing with CWM and ROM Manager. I installed CWM from fastboot. Only after seeing the same thing happen when I tried to install TWRP did I give ROM Manager a shot. This also just gave an error message without initializing any install. Thanks for the input though.
Click to expand...
Click to collapse
Yeah...I tried the fastboot method first too, for both TWRP and CWM. I really doubt that is the problem.

Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
carassius-one said:
Yeah...I tried the fastboot method first too, for both TWRP and CWM. I really doubt that is the problem.
Click to expand...
Click to collapse

godhamba said:
Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
Click to expand...
Click to collapse
1. I think it was 3 or 4 pours. Seemed to work flawlessly.
2. Still trying to learn which includes learning what an ruu is. Maybe that is my problem. I ran rumrunner and then have been trying to flash a recovery ever since...with no other steps.

godhamba said:
Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
Click to expand...
Click to collapse
1. Nope, I had no issues while doing the S-Off. It took 3 pours for me.
2. I haven't used any RUU for this. So you suggest going back to S-On and locked, then using the RUU? Sorry, still new to the whole process so just want to be clear on procedure. Yeah, I've been considering going back to complete stock and starting from scratch again. I'll give that a go later tonight if I can't come up with anything else.
Thanks.

No, no. The only RUU available is a decrypted one, which can only be flashed while S-OFF. So the ideas I put down were distinct, and not steps. My thought is that either (i) you return yourself to full stock and non-root as is explained in a thread in this subforum, or alternatively, (ii) flash the RUU to get a fully untouched setup (the RUU contains the factory "rom", bootloader and recovery and will return it to being fresh from the factory) on the device and then flash the recovery.
Prizm432 said:
1. Nope, I had no issues while doing the S-Off. It took 3 pours for me.
2. I haven't used any RUU for this. So you suggest going back to S-On and locked, then using the RUU? Sorry, still new to the whole process so just want to be clear on procedure. Yeah, I've been considering going back to complete stock and starting from scratch again. I'll give that a go later tonight if I can't come up with anything else.
Thanks.
Click to expand...
Click to collapse

Cinestra said:
I just tried to flash TWRP by using Fastboot and the CMD. However I still get no luck. I entered everything in the command prompt fine and it responded nicely. However, whenever I try to go to Recovery mode, the screen just says "entering recovery mode...." and then just turns black 15 seconds later and reboots again :S
Click to expand...
Click to collapse
I had the same problem and yesterday I posted my fix in this Forum's TWRP thread.
I had been using
openrecovery-twrp-2.6.3.0-m7.img
What I really needed was
openrecovery-twrp-2.6.3.0-m7vzw.img
Go here: http://goo.im/devs/Flyhalf205/M7VZW/openrecovery-twrp-2.6.3.0-m7vzw.img

beasleyj62 said:
I had the same problem and discovered that when i enter stock recovery, when the black screen appears, i had to press power+vol up to get it to show up. You may have to press them several times to get the timing right. Hope that helps!
Click to expand...
Click to collapse
Thanks for your solution, unfortunately though, it doesn't seem to work.
jpradley said:
I had the same problem and yesterday I posted my fix in this Forum's TWRP thread.
I had been using
openrecovery-twrp-2.6.3.0-m7.img
What I really needed was
openrecovery-twrp-2.6.3.0-m7vzw.img
Click to expand...
Click to collapse
Hmm alright so you suggest flash this other version of TWRP instead? That would make sense because the link looks like it's specialized for Verizon. I will try that out today!
godhamba said:
Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
Click to expand...
Click to collapse
1. It took me about 3 pours. That is an interesting thought and I think it may very well be valid, but I would prefer not to reset or relock my device though.
2. I have not decrypted RUU yet because I was unfamiliar with the term. I may try this if the new TWRP code does not work

@Prizm432 it looks like you are flashing the wrong Twrp zip. It has to end in m7vzw.zip
Sent from my HTC6500LVW using XDA Premium 4 mobile app

TWRP 2.6.3.3 Problems

Has anyone successfully installed TWRP 2.6.3.3 (http://techerrata.com/browse/twrp2/m7) on your HTC One? I have tried all three methods on installing it and I can't seem to get it to stick on my phone.
Method one: Goo.im app
From the menu, selecting Install OpenRecoveryScript and selecting Yes results in No recoveries were found for your device.
Method two: ADB / Terminal
Opened up an ADB shell and used dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p34 which successfully installed it. Rebooting to recovery goes to the HTC screen that says Entering recovery and then reboots the device for a normal startup.
Method three: Fastboot
Booting into the bootloader and selecting the fastboot option in order to run fastboot flash recovery recoveryfilename.img successfully installed. Rebooting to recovery goes to the HTC screen that says Entering recovery and then reboots the device for a normal startup.
Holding volume down + power and selecting Recovery from the bootloader also reboots to the HTC screen that says Entering recovery and then reboots the device for a normal startup.
No idea how to get this installation to stick. Can anyone help out?

the twrp for m7 doesn't work.
the twrp for m7vzw is the one you need.

raphytaffy said:
Has anyone successfully installed TWRP 2.6.3.3 (http://techerrata.com/browse/twrp2/m7) on your HTC One? I have tried all three methods on installing it and I can't seem to get it to stick on my phone.
Method one: Goo.im app
From the menu, selecting Install OpenRecoveryScript and selecting Yes results in No recoveries were found for your device.
Method two: ADB / Terminal
Opened up an ADB shell and used dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p34 which successfully installed it. Rebooting to recovery goes to the HTC screen that says Entering recovery and then reboots the device for a normal startup.
Method three: Fastboot
Booting into the bootloader and selecting the fastboot option in order to run fastboot flash recovery recoveryfilename.img successfully installed. Rebooting to recovery goes to the HTC screen that says Entering recovery and then reboots the device for a normal startup.
Holding volume down + power and selecting Recovery from the bootloader also reboots to the HTC screen that says Entering recovery and then reboots the device for a normal startup.
No idea how to get this installation to stick. Can anyone help out?
Click to expand...
Click to collapse
I used Flashify from the Play Store and it worked perfectly. The recovery held and was able to flash CM11. My fastboot has been screwed ever since I upgraded to Win8.1 so Ive been using that app as an alternative.
EDIT- Using the correct one as the previous post alluded to would also be a great idea. I didn't even catch that.

wiredout46 said:
the twrp for m7 doesn't work.
the twrp for m7vzw is the one you need.
Click to expand...
Click to collapse
Ah thanks, didn't even notice that. Working great now. If anyone comes to this thread looking for the m7vzw image, it can be found here: http://goo.im/devs/Flyhalf205/M7VZW

raphytaffy said:
Ah thanks, didn't even notice that. Working great now. If anyone comes to this thread looking for the m7vzw image, it can be found here: http://goo.im/devs/Flyhalf205/M7VZW
Click to expand...
Click to collapse
2.6.3.3 is in the verizon htc one original development subforum. just flashed it and it works fine.

Guys help! Installed TWRP 2.6.3.3. specifically for installation Maximus HD after installation did WIPE and accidentally formatted storage on which lay installer Maximus 30 HD, how do I copy installer again on storage, because mode Bootloader - Fastboot USB can not get access to it?

How come I can't find VZW TWRP 2.6.3.3?
and only can find 2.6.3.4?
sorry, just curious

andybones said:
How come I can't find VZW TWRP 2.6.3.3?
and only can find 2.6.3.4?
sorry, just curious
Click to expand...
Click to collapse
2.6.3.3 had the charging bug no?
if you need it, i have a copy of it.

Problem
Hey
I was flashing my htc to CM11 and it says that flash was successful, but now my htc one stuck when you try to power on it says only HTC quietly brilliant and wouldnt go on. What should I do ?

peca_slo said:
Hey
I was flashing my htc to CM11 and it says that flash was successful, but now my htc one stuck when you try to power on it says only HTC quietly brilliant and wouldnt go on. What should I do ?
Click to expand...
Click to collapse
Did you wipe data before or after flashing?

Flyhalf205 said:
Did you wipe data before or after flashing?
Click to expand...
Click to collapse
yes i did i have rot the cm10.2 but it stuck on logo screen of cm

peca_slo said:
yes i did i have rot the cm10.2 but it stuck on logo screen of cm
Click to expand...
Click to collapse
You did flash the Verizon recovery and Verizon rom?

Flyhalf205 said:
You did flash the Verizon recovery and Verizon rom?
Click to expand...
Click to collapse
Yes I did but I think this is not a good verzion for me cuz i have m7-ul model, but now I can do nothing with the phone. It would be good if i could get it back to stock

peca_slo said:
Yes I did but I think this is not a good verzion for me cuz i have m7-ul model, but now I can do nothing with the phone. It would be good if i could get it back to stock
Click to expand...
Click to collapse
Might be better to go to the ul variant thread at http://forum.xda-developers.com/htc-one

Can't Flash TWRP after installing MaximusHD
So I am a noob at this stuff and successfully flashed TWRP 2.6.3.3. I installed the MaxHD ROM shortly after following all instructions that I could find. I ran into bootloop and had to revert to an old firmware then flashed the current firmware and viola MaxHD booted right up. However, now I can not flash TWRP back as my recovery. Everytime I flash it and go into recovery it goes into MaxHD ROM. If anyone has any ideas they are much appreciated.
Also, I have read for over three weeks on these boards before posting even my first post so I have tried to research the problem if anyone was wondering that.

Jaayyrod said:
So I am a noob at this stuff and successfully flashed TWRP 2.6.3.3. I installed the MaxHD ROM shortly after following all instructions that I could find. I ran into bootloop and had to revert to an old firmware then flashed the current firmware and viola MaxHD booted right up. However, now I can not flash TWRP back as my recovery. Everytime I flash it and go into recovery it goes into MaxHD ROM. If anyone has any ideas they are much appreciated.
Also, I have read for over three weeks on these boards before posting even my first post so I have tried to research the problem if anyone was wondering that.
Click to expand...
Click to collapse
Is MaxHD a Verizon rom? That could be an issue if it's not. Also, the latest TWRP is 2.7.0.8. Haven't had any issues with it. Are you flashing it with fastboot commands? You might try the app Flashify.
Sent from my HTC6500LVW using Tapatalk

brholt6 said:
Is MaxHD a Verizon rom? That could be an issue if it's not. Also, the latest TWRP is 2.7.0.8. Haven't had any issues with it. Are you flashing it with fastboot commands? You might try the app Flashify.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Good call...it is not for the Verizon HTC One. Thanks much.
It doesn't say it's not in the write up about the ROM...I had to dig into the replies to see if anyone else asked.

Can't flash a recovery ROM to HTC One Verizon

I might be doing something wrong but I can't flash any recovery ROMs to my HTC One. I used rumrunner S-off today and gained root access with my stock ROM. I tried using command prompt to flash a TWRP recovery ROM, and it only worked once but now whenever I try to do it it says either "cannot load image" or gives me a partition error.
I tried going into recovery with the one I flashed and when it says entering recovery mode it either goes into a continuous reboot cycle or proceeds to the lockscreen. I tried using flashify today too and it says my device isn't compatible with any of the recovery ROMs.
Please help, I'm so frustrated and all I want to do is flash Android Revolution to my HTC! Also, was I supposed to factory reset my phone before all this? Because I still have all my apps, photos, data, etc.
P.S. I'm a noob at this stuff so I might be doing something wrong.

Try Flashify from the play store. Put the recovery on the Flashify app and flash if.
sent from my HTC One

jbh00jh said:
Try Flashify from the play store. Put the recovery on the Flashify app and flash if.
sent from my HTC One
Click to expand...
Click to collapse
No luck. Flashify won't install anything

ak074 said:
we will need more information about what all you've been trying and the results.
s-off was successful?
bootloader locked/unlocked?
what are you typing into the cmd prompt?
result from that cmd?
where did you get the recovery from? are you sure it's for the vzw htc one?
etc...
Click to expand...
Click to collapse
S-off was successful.
Bootloader is unlocked (And somehow the phone became rooted in the process)
cmd prompt: fastboot flash recovery recovery.img
cmd prompt kept saying something about unable to load the image
Got the recovery from ClockWork Mod - It is Verizon HTC One version
Thank you guys for your concern but I figured it all out. I used an all-in-one toolkit and it flashed my recovery without a problem. Now I have a Nandroid backup for stock rooted ROM, and flashed BoneStock onto my device! It is all working great and my battery life rocks!

shadowskaya said:
No luck. Flashify won't install anything
Click to expand...
Click to collapse
OK first off make sure the recovery you are trying to flash ends in m7vzw.img second, Flashify doesn't work for everyone so you might have to do it from adb on your computer. And finally, there is no android revolution rom for the Verizon htc one.

The developer of Flashify has a thread in Android developing and hacking/ apps and games / Flashify. Sometimes these threads have updates posted before the play store does. Start at the back of the thread and read toward the beginning,find the latest info faster (about a 25 page thread).
Sent from my Galaxy Tab 10.1

shadowskaya said:
Thank you guys for your concern but I figured it all out. I used an all-in-one toolkit and it flashed my recovery without a problem. Now I have a Nandroid backup for stock rooted ROM, and flashed BoneStock onto my device! It is all working great and my battery life rocks!
Click to expand...
Click to collapse
You should try to do these things without using all-in-one kits. It's best to know what was done in case something goes wrong in the future. My guess is you were most likely trying to flash the wrong recovery.
Well, at least you're up and running!

karn101 said:
You should try to do these things without using all-in-one kits. It's best to know what was done in case something goes wrong in the future. My guess is you were most likely trying to flash the wrong recovery.
Well, at least you're up and running!
Click to expand...
Click to collapse
Thank you for the tip, I will remember that the next time I flash a recovery to something. It was the correct recovery, but for some reason the fastboot and adb wouldn't flash it. Maybe I just needed a reboot of pc or something...

Had the same issue after s-off with twrp. Ended up flashing cwm touch instead and it works just as well. Although I do miss twrp.
Sent from my One using XDA Premium 4 mobile app

New Verizon HTC one S-off but can not access recovery

I just got an HTC one from Best Buy Mobile (Verizon) yesterday. Turned S-Off using runrunner. Verified root but can not access recovery. I had the same issue with a S4 but it was a known issue for all that has updated to the 4.3.
I have tried all the suggestions in flashing TWRP. I am wondering if this is a Verizon related issue? Maybe they are putting something on their phones to prevent recovery?
HELP!!!!

Something is really jacked up with my phone. It kept saying Unfortunately Amazon has stopped. Over and over again. So I gave up and went to do a factory restore and data wipe. I first went to Super user and removed permanent root. I then tried to do a factory wipe through settings/backup & reset reset phone. It still gave me issues trying to enter recovery mode. It would get hung up and then reboot to a sort of safe mode version of the OS. (with a red disclaimer at the bottom). Then I tried to do factory reset by holding the volume down and power. Its doing the same thing. At this point I don't are about root I just want a working phone.
Any suggestions?

Flash twrp from the xda thread here and then flash arom. What exactly are you doing to flash it?
Sent from my One using xda app-developers app

I have tried flashing a recovery. Now I dont have root and cant do anything. It will not let me even upgrade firmware. I tried to get it back to stock. My recovery is jacked up.

adodson927 said:
I have tried flashing a recovery. Now I dont have root and cant do anything. It will not let me even upgrade firmware. I tried to get it back to stock. My recovery is jacked up.
Click to expand...
Click to collapse
OK, so you are s-ff, is your bootloader unlocked?
IF you are not on stock recovery YOU CANNOT run an update

I'm s-off bootloader unlocked. I have no recovery. Not even stock.
Sent from my HTC6500LVW using XDA Premium 4 mobile app

adodson927 said:
I'm s-off bootloader unlocked. I have no recovery. Not even stock.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
.. you have to have a recovery..
I think?
can you successfully fastboot flash a custom recovery? If not can you fastboot the stock recovery..?
To be completely honest, I would just run the RUU. should fix you right up

You could boot into RUU and flash the decrypted stock rom zip to get back to straight stock. The zip reflashes stock recovery. I don't see why that wouldn't work.
Edit: Oops. Didn't even notice andy just recommended the same thing lol. My fault.

adodson927 said:
I'm s-off bootloader unlocked. I have no recovery. Not even stock.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thats odd, i thought you had to have a recovery of some kind.
Here is what I would do:
Lets try Flashing CWM instead of TWRP in fastboot I will post it, and I will also post the stock recovery there to as well.
https://www.dropbox.com/s/kk2esdrx1g1b50p/recovery-clockwork-touch-6.0.4.5-m7vzw.img
the image is easily installed via an unlocked bootloader with the following command:
fastboot flash recovery imagename.img
in this case: fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7vzw.img
See if it actually takes, and report back any errors.
If for some reason it does not, try booting into bootloader/fastboot then push the stock recovery:
https://www.dropbox.com/s/hgzgq84svzahvnv/htconerecovery_signed.img
Hopefully that will at least take and try to push CWM again , reboot bootloader and reboot into recovery . I am hoping that does it for you.
Go here: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip and dump SU on the root of your SD card and flash the SU.
I have seen people have all kind of weird issues with rum runner and I am just glad i had the official java card method used on mine. I also tend to just use a stock ROM which is just de-bloated.
Anyways I have used Santod040 roms in case i need to go back to pure stock ROM only: http://forum.xda-developers.com/showthread.php?t=2485319
You will need the odex one to run any OTA
The firmware is a different thing to flash.
here are the checksums:
htconerecovery_signed.img
MD5: E3F5208454689BE7F09835D4A60953A8
SHA-1: 1B0734D97732039528159AD1409AFEE858B5E9F1
SHA3-256: E0741EB77E5DEBEA932EE74F374FAC9E1037776178944279E8B12832C30E2546
recovery-clockwork-touch-6.0.4.5-m7vzw.img
MD5: 21A386CB920C485844E3BE0727351838
SHA-1: 312350D7383850915A648E2060AA2FC72B5EA08F
SHA3-256: 78B0C42CD62D3EB2B18BF62B544FC86878A56199DB96D13F26EA65663A822932

Thanks guys!
I was able to install TWRP and also Superuser.
Here are the instructions I used. Maybe they will help someone else like me.
Power off your device, then press and hold Power and Volume Down until you're in the bootloader menu. Highlight FASTBOOT and press Power. You should see Fastboot USB highlighted in red.
Download the latest version of TWRP for your phone and carrier. Rename file to twrp.img.
Open a command prompt on your computer and navigate to your SDK directory. Type "fastboot flash recovery twrp.img" and hit Enter.
Then I backed up my stock rom using TWRP
In TWRP's main menu, tap Reboot. It will tell you that you're not rooted and ask you to install SuperSU, so swipe to confirm. When you reboot your phone, you should see a notification that you need to install the SuperSU app. Open the notification and select TWRP, since the app from Google Play only works with S-OFF.
Worked flawlessly.
I installed NuSenseONE max and I love it so far.

adodson927 said:
Thanks guys!
I was able to install TWRP and also Superuser.
Here are the instructions I used. Maybe they will help someone else like me.
Power off your device, then press and hold Power and Volume Down until you're in the bootloader menu. Highlight FASTBOOT and press Power. You should see Fastboot USB highlighted in red.
Download the latest version of TWRP for your phone and carrier. Rename file to twrp.img.
Open a command prompt on your computer and navigate to your SDK directory. Type "fastboot flash recovery twrp.img" and hit Enter.
Then I backed up my stock rom using TWRP
In TWRP's main menu, tap Reboot. It will tell you that you're not rooted and ask you to install SuperSU, so swipe to confirm. When you reboot your phone, you should see a notification that you need to install the SuperSU app. Open the notification and select TWRP, since the app from Google Play only works with S-OFF.
Worked flawlessly.
I installed NuSenseONE max and I love it so far.
Click to expand...
Click to collapse
how else were you trying to flash a recovery ?!?

Goo.im app as well as ROM Manager, ROM Toolbox can flash recoveries. I've notice there isn't much compatibility with the m7vzw though. You can also use terminal command's from the device. All of these require root access though.
Sent from my One using XDA Premium 4 mobile app

Hey everyone, so my problem is that i did run rumrummer the way it said on the directions and i double checked my rom version type countless times. It says that i am unlocked and s-off, but i cant access recovery. I tried flashing recovery with fastboot command prompt, and still no luck. It gives me a "error: cannot open 'open.img', I navigated to the folder that it is located in and executed the command properly every time. I also dont know how to flash superuser using flashboot, so any help will be very much appreciated. Also I'm kinda new to rooted, I have some experience from a few years back, but dont remember everything.

Jo5ton1018 said:
Hey everyone, so my problem is that i did run rumrummer the way it said on the directions and i double checked my rom version type countless times. It says that i am unlocked and s-off, but i cant access recovery. I tried flashing recovery with fastboot command prompt, and still no luck. It gives me a "error: cannot open 'open.img', I navigated to the folder that it is located in and executed the command properly every time. I also dont know how to flash superuser using flashboot, so any help will be very much appreciated. Also I'm kinda new to rooted, I have some experience from a few years back, but dont remember everything.
Click to expand...
Click to collapse
place the name.img file in the same folder as the adb and fastboot executables, open command prompt as administrator for that directory, then type "fastboot flash recovery name.img" substitute name.img for the actual name of the file including extension and make sure there are no quotes around it. also, use "fastboot devices" or "adb devices" to make sure your phone is being recognized.

I got it to work, finally. Thanks for the reply pointedge. I beat u to it earlier in the day and forgot to post up again that I got it. It was like u said, I just had the file in the wrong folder.
Sent from my HTC6500LVW using XDA Premium 4 mobile app

nrfitchett4 said:
how else were you trying to flash a recovery ?!?
Click to expand...
Click to collapse
I'm willing to bet he flashed the wrong recovery. It's happened to a lot of people.