Related
Well at last, HTC has brought us their method to root HTC Evo 3D & Sensation.. Just register to become a member (dev) and begin rooting your Evo3D. I wanted to show you all what to expect.. and of course there are disclaimers so view screen shots for full details. I have not tried this setup so please give feedback, I do have the phone but it's been rooted by other methods.. just giving fellowship & sharing information. Enjoy!
Go to HTCDev.com to get started.. (This will VOID your warranty, root your phone & give you super human strenghts)
Previous rooting gave phone's the same voided warranty especially servicing in carriers service center, same deal. Revolutionary method also voids warranty so now people have choices.. (Former Sprint Service Mgr)
As informed please give useful feedback if you have used this method so we know where we stand with this and in fact "IF" HTC is helping us out.
Thx to Doomstang for input-
Doomstang said:
Well I think I've finally gotten somewhere...Wireless Tether was just successfully granted Superuser permissions.
This was all done without ever having rooted this phone in the past...so I accepted the OTA update, unlocked with HTC Dev's process, got a working recovery going, and then got Superuser installed.
graffixnyc posted the link to the working recovery so I used that: http://www.multiupload.com/AQ9KV7IME9
Click to expand...
Click to collapse
And Graffixnyc-
graffixnyc said:
This was the version of CWM that booted for me. I flashed through fastboot and also did a nandroid restore just fine. This was the version IEF(from alpharev) gave me on irc
http://www.multiupload.com/AQ9KV7IME9
I was able to get into recovery from selecting recovery from the fastboot method and from doing adb reboot recovery. Sorry for not posting earlier I had finals yesterday and went out after to celebrate
http://www.multiupload.com/AQ9KV7IME9
Click to expand...
Click to collapse
Please make sure all items are installed and up to date.
Google Android SDK zip:
http://developer.android.com/sdk/index.html
Java Runtime Environment:
http://java.com
HTC Sync (Windows Only):
http://www.htc.com/www/help/
Continued "disclosure"
It is our responsibility to caution you that not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty. Please note that unlocking your bootloader does not mean that you will be able to unlock the SIM lock. Unlocking your SIM lock is at the discretion of your operator/carrier and is not part of the bootloader unlocking scope.
Our devices have been designed with our hardware and software specifications in mind and unlocking the bootloader will change the software and may cause unexpected side effects. It is impossible for HTC to ensure the proper functioning of your device after this. In the worst case scenario, it is possible that your device may be physically damaged due to overheating or the behavior of your device might be altered including, but not limited to, hearing aid compatibility (HAC) and specific absorption rate (SAR) values.
Some content on your device may also be invalidated and cannot be accessed any more because of invalid DRM security keys. This includes content that you may have purchased through a 3rd party vendor and through HTC. Furthermore, although you will still be able to receive updates to your device via FOTA (“firmware over the air”), we do not guarantee that updating your device via FOTA will not render your device unusable. Please understand that you will not be able to return your device to the original state and going forward your device may not be held covered under the warranty for all claims resulting from the unlocking of the bootloader. HTC bears no responsibility if your device is no longer usable afterwards.
HTC is committed to assisting customers in unlocking bootloaders for HTC devices. However, due to some of our carrier customers concerns, certain models with specific restrictions may not be able to be unlocked. Please refer to our list of supported devices to see if your device is eligible for unlocking the bootloader.
We strongly suggest that you do not unlock the bootloader unless you are confident that you understand the risks involved. This is a technical procedure and the side effects could possibly necessitate repairs to your device not covered under warranty. If you are still interested in unlocking the bootloader, and you understand the consequences both to your device and to your warranty, then you may refer to the following pages where we have provided the unlocking instructions.
If there's an error you will see screen shot below.. with details on what happened.
So maybe I'm confused about what this does ... I went through the process and everything seems to have worked. Bootloader now shows unlocked. I tried to flash a recovery (both clockworkmod and TWRP) and it seems to flash successfully but when I try to run recovery it just reboots the phone after showing the HTC logo for a minute. I was hoping to install the rooted OTA but not sure what to try next...
nabbed said:
No. I'm not confused about the unlock.
I'm worried about a man who makes a guide about unlocking the device he does not have...
Am I wrong to be worried, about a man, who makes a post, about unlocking a device, he does not have?
Has has tested the method?
Click to expand...
Click to collapse
Yooooo. Godzson is a trusted guy and helps many devs in the community. No sense in flamming him when you'll just start pissing off devs here.
Sent from my PG86100 using Tapatalk
Godzson is a trusted member on here. Don't think you have to worry about him. Why would someone take all this time to write up a post with pics and the info just to mess with people? Smh....... Alot of the devs in the 3d community who do roms and themes don't even have the damn 3d. Don't start turning this community into **** by questioning people trying to help.
gthing said:
So maybe I'm confused about what this does ... I went through the process and everything seems to have worked. Bootloader now shows unlocked. I tried to flash a recovery (both clockworkmod and TWRP) and it seems to flash successfully but when I try to run recovery it just reboots the phone after showing the HTC logo for a minute. I was hoping to install the rooted OTA but not sure what to try next...
Click to expand...
Click to collapse
TWRP doesn't work and CWM Is a hit or miss. You should of tried the stock recovery, I think it had one. Wait till a root for the new boot loader I say.
I think the unlocked just gives partial access to the bootloader if I am correct. Your security flag(s-off) is still on.
Sent from my EVO3D(overclocked) via XDA App
Godzson is only posting to what HTC promised, here a unlocker. He is also a trusted member, who provides a substantial amount of information for the community. Please they are also right to say some dev, and do not have this device and do an amazing job developing for it. let's please keep peaceand move forward..
Why waste your time reposting instructions found on htcdev.com? People want to know what happens after you do the method and how it helps put custom software on your phone.
mwalt2 said:
Why waste your time reposting instructions found on htcdev.com? People want to know what happens after you do the method and how it helps put custom software on your phone.
Click to expand...
Click to collapse
Because sometimes people want to see the process without having to DO the process....
Why question it? Just don't read through 2 pages or more of posts if it's offensive to you.
Yo GODZSON, you do know that the little green android guy isn't the only one that's green around here, don't you? LMFAO. Just look at the noobs trying to flame you, and don't even know anything about you, LOL. Yeah, LOL. Like they got room to talk. Keep up the great work buddy.
On a more serious note, does this method actually allow you to root? Cuz I didn't really see anything on HTC's site, or in your post about rooting. Yet the title states rooting with HTC's unlock method. Just a fyi.
Sent from my PG86100 using XDA Premium App
Well sir maybe doing a lil research would benefit the questions. I did assist with 2 threads in Evo3D (screen pics and 3D converting). I placed this for information to the community and for knowledge to those that may want to see what it looks like and have other options of rooting their phone. I do have the device but's its been rooted therefore I havent tried this "Official" method. Would be nice to ask with some manners in XDA you can get suspended, banned, etc for your actions, this is a community to help each other out.
Thanks to all the fellow dev's for the kind words.. to all the noobs with lack of knowledge no worries we're here for you to help out, much love for you.. hey we all started there at one time
Well I think I've finally gotten somewhere...Wireless Tether was just successfully granted Superuser permissions.
This was all done without ever having rooted this phone in the past...so I accepted the OTA update, unlocked with HTC Dev's process, got a working recovery going, and then got Superuser installed.
graffixnyc posted the link to the working recovery so I used that: http://www.multiupload.com/AQ9KV7IME9
this is a joke!
HTC's unlocked bootloader is a joke, it just says "unlocked" but you cannot flash any new recoveries and you get S-ON. Don't try this folks, stay rooted! My 3D is now officially bricked with HTC method, it's not unlocked at all as you can't do anything with it.
zedomax said:
HTC's unlocked bootloader is a joke, it just says "unlocked" but you cannot flash any new recoveries and you get S-ON. Don't try this folks, stay rooted! My 3D is now officially bricked with HTC method, it's not unlocked at all as you can't do anything with it.
Click to expand...
Click to collapse
I'm very sorry to hear yours was bricked but I was able to flash a working recovery (although the first 2 I tried did fail) and gain SU permissions even with S-ON still showing.
thnx
Doomstang said:
I'm very sorry to hear yours was bricked but I was able to flash a working recovery (although the first 2 I tried did fail) and gain SU permissions.
Click to expand...
Click to collapse
Thanks I actually saw your post and trying that now! We will have ROOT!
It does look like things are working for some starting here in one of the other threads.
Great write up
Lol, sorry HTC. We beat you to it.
Sent from my EVO 3D using XDA Premium App
The unlock is terrible, I got it to work on my Dad's phone, but I could only get into clockwork once, TWRP doesn't work, and only a manual flash of clockwork seemed to work, I tried to get in with Rom Manager for him so he could do a backup, and it wouldn't go either, and it didn't want to go back in for me manually either, just boots up.
Oh well, I managed to root it and get a rom installed. So we shall see how everything goes.
It's S-ON still, which is complete crap.
nfollin said:
The unlock is terrible, I got it to work on my Dad's phone, but I could only get into clockwork once, TWRP doesn't work, and only a manual flash of clockwork seemed to work, I tried to get in with Rom Manager for him so he could do a backup, and it wouldn't go either, and it didn't want to go back in for me manually either, just boots up.
Oh well, I managed to root it and get a rom installed. So we shall see how everything goes.
It's S-ON still, which is complete crap.
Click to expand...
Click to collapse
4.0.1.5 failed for me too.
I started with CWM 4.0.1.4.
I clicked update recovery in ROM Manager and it said 4.0.1.5 successfully installed after I granted it SU permissions. Had it reboot into recovery from ROM manager and the phone just restarted...so I manually went to recovery via HBoot and it fails to load and restarts the phone. I guess I'll push that 4.0.1.4 back to it now.
so the bootloader gets unlocked but yet it stays S-on? wtf lol ?
Hello everyone. I am new to the world of android, but I'm a quick enough learner. Here is my specific problem:
I have an AT&T Atrix 4g. It is currently superuser rooted. It is currently running Android ROM 2.3.4.
Shortly after rooting the device, I downloaded ROM Manager and successfully installed through the application Clockwork Recovery. I tried to select the option to back up the current ROM (the stock android) on my SD card.. however, during the load screen, I got an error message stating
"Failed to boot 2
Starting RSD protocol support"
So doing some research, I came upon the conclusion that the reason I can't backup or really do anything with ROMs is that I needed an unlocked bootloader.
I went to Atrix4ghacks and followed the instructions on how to unlock bootloader and install permanent recovery.
This is the critical part: When I entered into the command prompt "fastboot oem unlock", instead of proceeding normally I got the return message:
"OEM unlock is not implemented"
Again, did a google search and read that Android 2.3.4 on Atrix 4g does NOT allow unlocked bootloaders.
So, the questions that I have that result from this are:
1.) Can someone here confirm that, in fact, I am unable to unlock the bootloader on my phone?
2.) If so, is there a viable workaround that is both reasonably safe and not overly complicated? Please note that I have no backup in case something goes wrong, leading me to
3.) Is there a way to backup my stock 2.3.4 ROM without an unlocked bootloader?
4.) Can I revert safely to an older android version that supports unlocked bootloaders?
5.) Can you actually install new ROMs without an unlocked bootloader?
6.) Am I totally screwed?
HUGE THANKS to anyone who actually bothered reading this, and even more thanks to anyone who can answer/point me in the right direction. Much appreciated!!!
thats becouse u havent flashed yet the bootloader ill give a post related to this and esay way to do it
http://forum.xda-developers.com/showthread.php?t=1182871
and you CANT go back to 2.2 or 2.3 u can hard brick your phone
tufo430 said:
thats becouse u havent flashed yet the bootloader ill give a post related to this and esay way to do it
http://forum.xda-developers.com/showthread.php?t=1182871
and you CANT go back to 2.2 or 2.3 u can hard brick your phone
Click to expand...
Click to collapse
Thanks a ton for that link. I'm sorry to ask once again, but I'm very wary of possibly bricking my phone... so I must ask: Is your solution possible with 2.3.4? Or will the phone softbrick?
If you did the Over The Air (OTA) update to 2.3.4 then yes your phone will softbrick after flashing the bootloader. Re-enter fastboot and issue the unlock commands and everything will be fine when you reboot.
I'm in over my head. Very much so. I've been flashing for years and a friend of mine has handed off his ATT atrix after making some big mistakes. He was rooted and somehow/for some reason deleted CWM and the new OTA ended up getting his device to this point (photo in attachment). I'm not very familiar with RSD, as luckily I've never found myself in a predicament like this. I've been all over this forum, the pudding/fruitcake/fastboot threads, and although I've seen the 'Don't SBF' warnings everywhere, I don't know what else to do, and I don't want to take any more action without knowing the consequences. I think this is a pretty unique situation. I'm asking for a detailed instruction on getting this phone restored (I've seen some say it's not possible, but other places saying a guy figured out a way). I need the specific links, and specific steps (as I've had much issue with broken links). I have access to ubuntu and windows so whichever is more simple is fine. I could try my luck but I'd rather reach out to someone who knows before hand.
*As far as I know the battery is high enough to flash (it's sitting with the battery pulled for now)
I don't care about retaining root, having a custom recovery or anything of that nature. I just need this phone to be in working condition again. Upon that happening we'd be happy to throw 20$ (via paypal) to whoever can get us there. Thanks in advance.
maybe this will help
I was rescued previously by the nice folks on atrixforums. you can reference this link http://www.atrixforums.com/forum/rescue-squad/6164-se-flash-olympus-help.html
Should be able to flash Romracers CWM via fastboot > http://forum.xda-developers.com/showthread.php?t=1204500 then get back into recovery. You can also flash a Fruitcake in fastboot mode > http://forum.xda-developers.com/showthread.php?t=1163009.
From your picture it looks like the bootloader was unlocked before, and maybe need to issue the unlock command again. This thread may help you > http://forum.xda-developers.com/showthread.php?t=1182871
Looks like ya just need to do the fastboot oem unlock commands to unlock the BL and finish the process....
thanks
Thanks for the quick responses guys, I'm off to work now but I'll try this tonight. Once again thank you.
I had the exact same problem, same thing happened with my phone, don't worry, you're okay!
First, are you sure that's the right SBF? I would confirm whether it is because that's the easiest way. Next, do what others have said and try to flash a recovery on it, from there on you can just unlock the phone and flash any rom.
Hope you get it sorted out.
G-Man. said:
Looks like ya just need to do the fastboot oem unlock commands to unlock the BL and finish the process....
Click to expand...
Click to collapse
brandonmangan - based on your screenshot you posted, you need to do the fastboot oem unlock commands, you flashed the pudding sbf with the unlockable bootloader. Get the fastboot drivers installed and then run the commands as they are listed in the pudding thread. Thats ALL you need to do.
Hey all,
I'm fairly new to unlocking/rooting (I'm from the simple iPhone jailbreak world).
I have my Atrix 4G rooted with no issues and ClockworkMod installed... that was the easy part it seems.
Where I am struggling is to figure out IF I can unlock my Atrix 4G and if it is safe to do.
I am running Android 2.3.6 on the Bell network. I see a bunch on unlocks for bootloader 2.3.4 and am confisued if that bootloader version has any relation to the android version? How can I figure out what bootloader I have? Would it also be 2.3.6?
If it is indeed 2.3.6, is it possible to unlock, I see no specific unlocks for that version.
Thanks,
You cant install a different recovery with out being unlocked. so if you can boot into CWM then your phone is already unlocked.
Where did you get the phone? was it new?
Its possible if its used that it was already unlocked and someone RSD back to stock for sale purpose, if its new and you havent unlocked yet then you dont have CWM installed.
Random Canadian said:
You cant install a different recovery with out being unlocked. so if you can boot into CWM then your phone is already unlocked.
Where did you get the phone? was it new?
Its possible if its used that it was already unlocked and someone RSD back to stock for sale purpose, if its new and you havent unlocked yet then you dont have CWM installed.
Click to expand...
Click to collapse
Sorry should have been a little more clear, I have installed ROM Manager and choose the CWM install, but I cannot boot into it, I get a boot error 2 (I think). Sorry phone is at home now so I can't recall exact error will post later.
I got phone 6 month ago, was used phone. I am fairly certain its not unlocked because I cannot boot with CWM, hence cannot install custom ROM.
Thanks for the reply.
Random Canadian said:
You cant install a different recovery with out being unlocked. so if you can boot into CWM then your phone is already unlocked.
Where did you get the phone? was it new?
Its possible if its used that it was already unlocked and someone RSD back to stock for sale purpose, if its new and you havent unlocked yet then you dont have CWM installed.
Click to expand...
Click to collapse
You don't need to be unlocked to have CWM on your Atrix. I had it on at least 1.83 if not the original stock firmware. I know it was possible with only root on 1.83 because that was what I was running up until a month ago and I had CWM on it with a locked bootloader.
cerps said:
You don't need to be unlocked to have CWM on your Atrix. I had it on at least 1.83 if not the original stock firmware. I know it was possible with only root on 1.83 because that was what I was running up until a month ago and I had CWM on it with a locked bootloader.
Click to expand...
Click to collapse
Right, my phone is rooted so I have CWM, just can't boot it. My understanding is because I need to unlock, but I don't know how to unlock because I don't know how to figure out what bootloader I have.
cerps said:
You don't need to be unlocked to have CWM on your Atrix. I had it on at least 1.83 if not the original stock firmware. I know it was possible with only root on 1.83 because that was what I was running up until a month ago and I had CWM on it with a locked bootloader.
Click to expand...
Click to collapse
Locked or it just didnt say unlocked at the top? two very different things.
avalanche333 said:
Right, my phone is rooted so I have CWM, just can't boot it. My understanding is because I need to unlock, but I don't know how to unlock because I don't know how to figure out what bootloader I have.
Click to expand...
Click to collapse
dur im pretty sure that unlocking the boot loader allows unsigned code to run at boot, I could be wrong but I think you two are out to lunch on installing CWM with just root.
That or you can install it but you cant run it because the boot loader wont allow something with out motorolas signature to execute. making the point of if it is or is not, installed, a moot one. Aside from the fact you no longer have any sort of a functional recovery mode.
There is a LOT of info on how to unlock the bootloader and its not exactly hidden. I dont know if its even still done with RSD but that would be a place to start as that is how I did mine in sept of last year.
Random Canadian said:
Locked or it just didnt say unlocked at the top? two very different things.
dur im pretty sure that unlocking the boot loader allows unsigned code to run at boot, I could be wrong but I think you two are out to lunch on installing CWM with just root.
That or you can install it but you cant run it because the boot loader wont allow something with out motorolas signature to execute. making the point of if it is or is not, installed, a moot one
There is a LOT of info on how to unlock the bootloader and its not exactly hidden. I dont know if its even still done with RSD but that would be a place to start as that is how I did mine in sept of last year.
Click to expand...
Click to collapse
Yes I see what your saying, but I am saying that I cannot run CWM. I can only install onto my SD card. But the boot in recovery does not work (ie it will not run CWM). I'll post the error little later tonight when I try at it again.
I realize there is lots of info on unlocking bootloader and I am not concerned about doing the unlock, once I find a way to verify my bootloader version. Ive seen a few posts warning that bootloader must be v 2.3.4 or you can brick the phone.
So I guess ultimately my question is, how can I figure out my bootloader version? Have not seem this answers after some googling.
http://forum.xda-developers.com/showthread.php?t=1136261
Read that and your version will be in settings and then about phone. although I do believe that 234 and 236 unlock via the same method.
If you are going to install Custom roms CM7/9/10 or a blur based then you dont need to even worry about root. otherwise there are instructions in that thread to root that SBF
Random Canadian said:
Locked or it just didnt say unlocked at the top? two very different things.
dur im pretty sure that unlocking the boot loader allows unsigned code to run at boot, I could be wrong but I think you two are out to lunch on installing CWM with just root.
That or you can install it but you cant run it because the boot loader wont allow something with out motorolas signature to execute. making the point of if it is or is not, installed, a moot one. Aside from the fact you no longer have any sort of a functional recovery mode.
There is a LOT of info on how to unlock the bootloader and its not exactly hidden. I dont know if its even still done with RSD but that would be a place to start as that is how I did mine in sept of last year.
Click to expand...
Click to collapse
I'm positive it was locked, running 1.83, and had CWM on it. I bought the phone at an AT&T store myself. I rooted it and put CWM on it. The early version of CWM for the Atrix only was accessible by turning the phone on while plugged into the wall charger that came with the phone.
Hey guys. Need a big hand here. So I have a HTC One on contract from Three in the UK.
I rooted the phone and all that jazz and decided on putting a custom ROM on my device.
However while in TWRP I wiped the phone and seemingly all the contents on it, including TWRP.
Now I have a bricked phone that boots into recovery/ the bootloader only. I've tried flasing
RUU files on but it fails with the error code 140? I don't know much about this I'm quite a noob.
In recovery the information is as follows:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_UL PVT SHIP S-ON RH
HBOOT- 1.54.0000
RADIO-4A. 17. 3250. 14
OpenDSP-v31.120.274.0617
OS-2.24.401.0
eMMC-boot 2048MB
Please help me. I've read through wonderful guides by other patrons on this website but nothing seems to work.
I'm at my wits end.
Thank you in advance for any help.
I know very little about this, but just to brainstorm (and confirm a few basic facts):
When you rooted originally, did you use HTC's bootloader unlocker or a different method to unlock the bootloader?
How are you flashing ROMS? Are you doing everything through the phone (example, using one-touch-root apps) or are you using the Android Debug Bridge?
The bootloader typically comes with options to reboot, boot into recovery, factory reset, etc. Can you confirm that these options have disappeared (or never existed in the first place)?
My knee-jerk reaction is that you didn't use an HTC bootloader unlocker and, therefore, the HTC GUU detects a bootloader mismatch and aborts. Therefore, you need to see if there's a way to flash a stock HTC bootloader (which, I can tell you from experience, is usually a one-way-trip to super-bricking) or see if the bootloader you already have installed can be unlocked through the ADB.
In my very limited experience and understanding of Android, it's generally pretty difficult to wipe the recovery partition from within the phone - one generally as to flash it from ADB or screw with the bootloader in some way to wipe it. I wonder, therefore, whether the recovery partition is just fine but maybe the bootloader is throwing a fit because it's not the HTC default.
I'm sure you've tried or thought of all of this, but since nobody else is stepping up, I thought I'd help brainstorm a bit and keep the thread fresh.
Borden Rhodes said:
I know very little about this, but just to brainstorm (and confirm a few basic facts):
When you rooted originally, did you use HTC's bootloader unlocker or a different method to unlock the bootloader?
How are you flashing ROMS? Are you doing everything through the phone (example, using one-touch-root apps) or are you using the Android Debug Bridge?
The bootloader typically comes with options to reboot, boot into recovery, factory reset, etc. Can you confirm that these options have disappeared (or never existed in the first place)?
My knee-jerk reaction is that you didn't use an HTC bootloader unlocker and, therefore, the HTC GUU detects a bootloader mismatch and aborts. Therefore, you need to see if there's a way to flash a stock HTC bootloader (which, I can tell you from experience, is usually a one-way-trip to super-bricking) or see if the bootloader you already have installed can be unlocked through the ADB.
In my very limited experience and understanding of Android, it's generally pretty difficult to wipe the recovery partition from within the phone - one generally as to flash it from ADB or screw with the bootloader in some way to wipe it. I wonder, therefore, whether the recovery partition is just fine but maybe the bootloader is throwing a fit because it's not the HTC default.
I'm sure you've tried or thought of all of this, but since nobody else is stepping up, I thought I'd help brainstorm a bit and keep the thread fresh.
Click to expand...
Click to collapse
I unlocked the bootloader originally by getting a specific code from HTC and using it through the command prompt I think. I can go into the bootloader and it has all the fastboot, recovery, factory reset business there. Trying factory reset does nothing. I've downloaded HTC toolkit 2.2 and I tried initially pushing ROMS to flash to TWRP, but it would never detect my phone. Then I stupidly did a full wipe through TWRP and now that's disappeared. All that's left is the bootloader now. I've tried forcing RUU updates through the HTC toolkit but it always fails. So does running the normal RUU process. I can't seem to find the correct one for Three UK. The most I've been able to do is re-lock the bootloader and I'm running out of ideas. Thank you for your reply. I feel so helpless!.
If I've read your message correctly, you are doing everything through the HTC toolkit and not through the Android SDK. Frankly, I don't know how the former works. Especially if the HTC Toolkit isn't detecting your phone, you may want to run over to http://developer.android.com/sdk/ and fetch the SDK for your system and set it up. You don't need the ADT Bundle, just the SDK Tools link at the bottom. This may make it easier for other, more knowledgeable people debug your phone, since they all use the SDK. The weaponry you'll be using is all in the <sdk install location>/tools directory, so get a command prompt window pointed there (by the by, are you using Windows, Mac or Linux?)
If you already have your SDK up, or once you do, you'll want to get familiar with the fastboot command, described in this post: forum.xda-developers.com/showthread.php?t=2277112 . What we want to do is see whether we can flash a new recovery ROM.
As long as you don't attempt to flash over the bootloader, you shouldn't super-brick your phone. Based on the message in your original post, your bootloader may have relocked itself. If your first attempt at installing a new recovery ROM doesn't work, then you'll have to use the procedure you used originally to unlock your bootloader. If you've forgotten how to do that, then these instructions (which assume you're using the SDK) should help: http://wiki.cyanogenmod.org/w/Install_CM_for_m7.
You're currently using TWRP, which I've personally found buggy. Until you have a functioning phone again, you may want to use ClockworkMod (CWM) Recovery instead: http://www.clockworkmod.com/rommanager. It has fewer features, but at least they work properly. If flashing ROMs over fastboot is new to you, there are plenty of guides on the Interwebs to help you. I'll also try to walk you through it if you let me know where you're getting stuck. The critical thing, considering that there are many types of HTC One, is to make sure that you flash the ROM that exactly matches your phone. If you flash the wrong ROM, you probably won't break your phone any more than it is, but let's try not to test that theory. If you're not positive which phone you have, say so and we'll help you find out.
Let us know once you have CWM on your phone or where you got stuck. The advantage of using the SDK, too, is that you can copy and paste the output right back to the forum.
I hope I understood everything correctly. Let me know if I haven't.