Did I relocked my oneplus one?

I flashed the cos13 signed full ROM thru twrp 3.0.2-3 by tugapower. After successfully flashing it, I noticed that my recovery goes back to cos recovery, twrp was gone and also rot access. Halp halp halp. :crying:

Htc m9 relocked and s-off .. How can i get root??

Hey guys.. i recently got a second hand m9 and i wanted to root it but when i looked up on YouTube or google i found out about bootloader,s-on,s-off and other stuff... i do not have so much knowledge about these stuff so i figured you guys could help me out..
when i reboot to bootloader on my device it says :
***Software Status: Official ***
*** RELOCKED ***
*** S-OFF ***

So how can i get my device rooted?? I looked up for some answers and saw that i must unlock my bootloader and there was a guide but i feared that i may brick my phone so that's why i would like to know what i should exactly do.. :):):):o:o

Need help to S-ON and remove relocked VWZ Max

Can anyone help or have the files to S-ON and remove relocked on VWZ One Max and Sprint
here is detail both of my phone verizon and sprint one max have broken frames so i filed an insurance claim to get replacements i have received the replacements but need to re-S-ON and remove the relocked from both devices before shipping them back to insurion any help will be appreciated thank you advance

[Q] Relocked bootloader while using custom software, hboot won't detect power button

So, here's the thing, I already posted on a thread but it seems it's actually full of people asking and the guys answering there are stumped with our problems so I came here.

My bootloader is locked because I (stupidly :() relocked it while trying to install a newer firmware via RUU so then it just locked me out and couldn't do anything until I installed the RUU update of the same version I was running.
It's working but not as intended.
I tried unlocking the bootloader again after installing the RUU but no luck, the token works but it just won't detect my power button when I try to accept but the button works perfectly while running the system.

Here's my getvar all:

Code:

---

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4M.32.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: X
(bootloader) imei: X
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.072s

---

HELP! Soft bricked S-ON re-locked bootloader with no system or recovery partitions!

Hi, I am having some serious issues with my HTC One M9 and am wondering if anyone could lend a hand...

A bit of background
Originally, I set out on the task to update to the latest CyanogenMod version, but was having trouble as none of the nightly releases were installing (I was using TWRP and was constantly getting error messages). After much research, I found some instructions to unroot my phone, reinstall the stock image, and then download the OTA update. After this, it said that I would be able to install the latest CyanogenMod build. I went to the HTC ROM download support forum and downloaded the HTC One M9 version 3.35.617.12 ROM, and then proceeded to run the executable. I downloaded the Unlocked/Developer version because I live in Australia and none of options were my carrier (Telstra). This turned out to be a mistake, as after I got half way through the installation, I received the following:

Code:

---

error 131: customer id error

---

The main issue was, that the installer already went through the wiping phase, so my system was completely empty!

Where I messed up...
After my system being wiped, I read several forum posts as to why this error was occurring. I was following the instructions on one of the posts, which said to re-lock my boot loader... So, i ran:

Code:

---

fastboot oem lock

---

This turned out to be a huge mistake, as not only did it not fix the issue, but I cant even access my recovery partition.

Where I am at now
Currently, I can not access anything on my phone. I only have access to the boot loader (which is locked and is S-ON), as well as download mode. I tried to unlock the boot loader again with:

Code:

---

fastboot flash unlocktoken Unlock_code.bin

---

but after completing the steps and rebooting, the phone is still in a re-locked state. I tried to flash twrp back onto the recovery partition, or the stock ROM extracted from the RUU executable, but I would constantly get one of the two errors:

Code:

---

FAILED (status read failed (Unknown error))
FAILED (data transfer failure (Too many links))

---

So, I have a soft bricked phone that is S-ON, has a re-locked boot loader, and has no system or recovery partitions. All of the data was backed up, so I am literally open to anything to get it to a working state again.

Extra info about the phone

Code:

---

htc_himauhl PVT S-ON
LK-1.0.0.0000
RADIO-01.04_U11440601_71.02.50709G_F
OpenDSP-v29.2.6-00492-M8994_0702
OS-2.9.81.5
Sep 30 2015,12:34:35(573756)

cid: TELST001

---

Thank you anyone who can lend a hand :)
- Alex