Flashing an RUU with s-on and unlocked bootloader - AT&T HTC One (M8)

So I'm trying to flash the 1.58.502.1 RUU but I am s-on with an unlocked bootloader. And from the sound of things the only way to relock the bootloader is by going s-off which I don't want to pay $25 to do.
My current software is 1.12.502.8 but the current baseband matches up with the baseband from 1.58.502.1 (1.16.21331931. LA11G_20.31A.4145.02L). Are there any work arounds that you guys can think of, can I just flash the RUU since the basebands match up?

---

From what I've read it seems you do in fact need to S-OFF to relock the bootlooader.
Here's the thing,if you S-OFF than you won't need to relock the bootlooader to achieve what your looking to do .S-OFF enables you to flash all sorts of variations assuming they are for your specific device.
I will tell you that the $25 spent to have a safe hassle free S-OFF exploit is worth every cent.

---

You do not need to s-off to relock the bootloader.
"fastboot oem lock" from adb command prompt connection, while in fastboot mode is all you need to do.
Put your recovery back to stock first for safety but RUU should do that for you, better safe than sorry though...
- Sent from a payphone ...

---

Iconic24 said:
So I'm trying to flash the 1.58.502.1 RUU but I am s-on with an unlocked bootloader. And from the sound of things the only way to relock the bootloader is by going s-off
Click to expand...
Click to collapse
I don't know where you guys are getting this from. S-off is in no way required to relock the bootloader.
Further, s-off is not required to run an RUU (another common misconception, that I don't know where people get); unless you are trying to "break the rules" and either run an older RUU ("downgrade") or run another carrier's RUU.
Iconic24 said:
My current software is 1.12.502.8 but the current baseband matches up with the baseband from 1.58.502.1 (1.16.21331931. LA11G_20.31A.4145.02L). Are there any work arounds that you guys can think of, can I just flash the RUU since the basebands match up?
Click to expand...
Click to collapse
As long as you are using an AT&T RUU, you can run an RUU for any version number that is equal to or greater than the main version on the phone. The only thing you can't do is run an older RUU ("downgrade") with s-on.
But since you are on the oldest AT&T version (1.12) and there is no 1.12 RUU anyway; you can therefore run any AT&T RUU. This includes 1.58, 2.23, and any new RUUs that come in the future.

---

ruu
Oh my, I know this is necro thread but it is the closest to what I am trying to achieve and google search led me to it. So if I am on SkyDragon GPE 4.4.4 flashed on top of Stock Sense 4.4.2, hboot 3.16, tampered, unlocked, rooted, s-on there is no problem for me to go RUU and update to 5.x.x? However, shall I use RUU for 4.4.4 or 4.4..2? Thanks if anyone replies

---

?
i am thinking of just using a toolkit to root and unlock the bootloader but before i do that i gotta ask is it worth it ?

---

xCellHD said:
i am thinking of just using a toolkit to root and unlock the bootloader but before i do that i gotta ask is it worth it ?
Click to expand...
Click to collapse
Is it worth it to unlock the bootloader? That question is impossible to answer without knowing your individual desires, preferences and what you want from the device.
I gave an answer to a similar question a few days ago: http://forum.xda-developers.com/htc-one-m8/help/to-root-to-root-t3102598
If you are asking "is using a toolkit worthwhile"; I would say NO. The toolkits are not up to date, and therefore install obsolete versions of TWRP (which causes issues) and I personally recommend to do the steps "manually" as its not very hard, ande also a good learning experience that will yield better results.
My personal opinion, ditch the toolkits.
---------- Post added at 10:28 AM ---------- Previous post was at 10:22 AM ----------
innocencex said:
Oh my, I know this is necro thread but it is the closest to what I am trying to achieve and google search led me to it. So if I am on SkyDragon GPE 4.4.4 flashed on top of Stock Sense 4.4.2, hboot 3.16, tampered, unlocked, rooted, s-on there is no problem for me to go RUU and update to 5.x.x?
Click to expand...
Click to collapse
It sounds like you just flashed the GPE ROM, and did not "fully convert" to GPE with the RUU. You can confirm this by booting into hboot, if the hboot screen is white, its still the Sense hboot. GPE hboot is black.
Assuming you just flashed a GPE ROM, you can just RUU to current Sense RUU (5.0). You will need to relock the bootloader to RUU, since you are s-on.
innocencex said:
shall I use RUU for 4.4.4 or 4.4..2?
Click to expand...
Click to collapse
Just run the 5.0 RUU. No need to run intermediate RUUs or run them sequentially. OTAs need to be installed in sequence. RUUs do not.

---

redpoint73 said:
Is it worth it to unlock the bootloader? That question is impossible to answer without knowing your individual desires, preferences and what you want from the device.
I gave an answer to a similar question a few days ago: http://forum.xda-developers.com/htc-one-m8/help/to-root-to-root-t3102598
If you are asking "is using a toolkit worthwhile"; I would say NO. The toolkits are not up to date, and therefore install obsolete versions of TWRP (which causes issues) and I personally recommend to do the steps "manually" as its not very hard, ande also a good learning experience that will yield better results.
My personal opinion, ditch the toolkits.
---------- Post added at 10:28 AM ---------- Previous post was at 10:22 AM ----------
It sounds like you just flashed the GPE ROM, and did not "fully convert" to GPE with the RUU. You can confirm this by booting into hboot, if the hboot screen is white, its still the Sense hboot. GPE hboot is black.
Assuming you just flashed a GPE ROM, you can just RUU to current Sense RUU (5.0). You will need to relock the bootloader to RUU, since you are s-on.
Just run the 5.0 RUU. No need to run intermediate RUUs or run them sequentially. OTAs need to be installed in sequence. RUUs do not.
Click to expand...
Click to collapse
Sir I'm using GPe ROM to my HTC m8..it's S-ON "Unlocked" I can't unlock my bootloader.

---

Prvrt said:
Sir I'm using GPe ROM to my HTC m8..it's S-ON "Unlocked" I can't unlock my bootloader.
Click to expand...
Click to collapse
If it says UNLOCKED in bootloader, that means the bootloader is already unlocked.
Or are you trying to relock your bootloader?
It's not clear exactly what you are trying to do, or what steps you've already taken. I know you're new to the forum, so please try to provide as much detail as possible when asking for help. If youknow how, do fastboot getvar all, and post the result (delete IMEI and serial number before posting).

---

redpoint73 said:
If it says UNLOCKED in bootloader, that means the bootloader is already unlocked.
Or are you trying to relock your bootloader?
It's not clear exactly what you are trying to do, or what steps you've already taken. I know you're new to the forum, so please try to provide as much detail as possible when asking for help. If youknow how, do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
Im trying to root my phone again and unlock the bootloader..but i cant access when my phone is in Hboot my phone cant read on my laptop..and after i open it connect but my USB debugging is in "charging only" and i put it back again in MTP and after i put it in Hboot it disconnect again.. idont know if my laptop or my debugging mode

---

Prvrt said:
Im trying to root my phone again and unlock the bootloader..but i cant access when my phone is in Hboot my phone cant read on my laptop..and after i open it connect but my USB debugging is in "charging only" and i put it back again in MTP and after i put it in Hboot it disconnect again.. idont know if my laptop or my debugging mode
Click to expand...
Click to collapse
You do not need to unlock the bootloader if it says "UNLOCKED" near the top of the screen in bootloader. This specifically means the bootloader is already unlocked.
However, you will (somewhat obviously) need fastboot working if you want to flash TWRP via fastboot. There other means to install TWRP, since you also have working OS (TWRP app for instance). However, working fastboot is really valuable (possibly even critical in some situations) when modding the phone, so my recommendation would be to troubleshoot the problem, and have fastboot working (even despite the existence of "workaround" methods to install TWRP).
You actually do not need debugging enabled to use fastboot (only for adb, which is related to fastboot by there are distinct differences - so try to keep that in mind). Although having debugging enabled would not hurt anything (and obviously you will need it, if you want to use adb).
Another thing to note, the MTP connection mode selected in OS (charge only, file transfer, etc.) has not bearing once you are no longer in OS (when in bootloader) and fastboot will work regardless of whether there is even a working OS.
Fastboot connectivity issues are most usually on the PC side. Try a different USB port, different cable, re-install HTC Sync and HTC drivers. You can also try going into Windows Device Manager, finding the phone, then pick the option to manually select drivers, and select the "generic" Android MTP drivers. I often have to do this to make my PC "see" the M8 on fastboot/adb.

---

redpoint73 said:
You do not need to unlock the bootloader if it says "UNLOCKED" near the top of the screen in bootloader. This specifically means the bootloader is already unlocked.
However, you will (somewhat obviously) need fastboot working if you want to flash TWRP via fastboot. There other means to install TWRP, since you also have working OS (TWRP app for instance). However, working fastboot is really valuable (possibly even critical in some situations) when modding the phone, so my recommendation would be to troubleshoot the problem, and have fastboot working (even despite the existence of "workaround" methods to install TWRP).
You actually do not need debugging enabled to use fastboot (only for adb, which is related to fastboot by there are distinct differences - so try to keep that in mind). Although having debugging enabled would not hurt anything (and obviously you will need it, if you want to use adb).
Another thing to note, the MTP connection mode selected in OS (charge only, file transfer, etc.) has not bearing once you are no longer in OS (when in bootloader) and fastboot will work regardless of whether there is even a working OS.
Fastboot connectivity issues are most usually on the PC side. Try a different USB port, different cable, re-install HTC Sync and HTC drivers. You can also try going into Windows Device Manager, finding the phone, then pick the option to manually select drivers, and select the "generic" Android MTP drivers. I often have to do this to make my PC "see" the M8 on fastboot/adb.
Click to expand...
Click to collapse
I try on cmd my phone response. I type unlocktoken it works and after I type unlock code bin it success too but my phone didn't show the logo of unlock code and didn't reboot. But in my cmd it says successfully

---

Prvrt said:
I try on cmd my phone response. I type unlocktoken it works and after I type unlock code bin it success too but my phone didn't show the logo of unlock code and didn't reboot. But in my cmd it says successfully
Click to expand...
Click to collapse
You previously indicated UNLOCKED. Does it say UNLOCKED near the top of the bootloader screen?
Also, please refrain from quoting my whole entire post; as it clutters up the thread. I know it's the default when responding. But just leave in what is directly relevant to your response, and delete the rest.

---

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.502.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT45SWM06618
(bootloader) imei: XXXXXXXXXXXXXXX ( Deleted)
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.125s
Bootloader - Unlocked
Recovery - TWRP
Rooted - Yes
Custom ROM - Resurrection Remis 5.8.5 Final
if want to go back to stock what is procedure
i have below RUU
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502. 5_combined.exe
can i run this exe after relock the bootloader?

---

hotspot problem
i'm using htc one m9 at&t in india. i'm unable to turn on hotspot or bluetooth tethering. i heard a solution that i need to unlock bootloader and install cutome rom or edit some line in sql editor. so my question which is the safest method? could anyone please tell me the answer:crying:

---

Ashok_gajjala said:
i'm using htc one m9 at&t in india. i'm unable to turn on hotspot or bluetooth tethering. i heard a solution that i need to unlock bootloader and install cutome rom or edit some line in sql editor. so my question which is the safest method? could anyone please tell me the answer:crying:
Click to expand...
Click to collapse
This forum section is for the M8, not the M9. Anything we say here about the M8, may or may not be correct for the M9.

---

have a simple question I'm on firmware 3.16.617.2 there is update 3.16.617.3 if I am s-on unlocked Bootloader and attempt to flash RUU advance to 3.16.617.3 from earlier .2 will this relock my Bootloader ? as I don't want to relock it again my goal is to stall unlocked S-on .