Database Develop

[Q] Where do I start?

So here's the deal: I bought a HTC ONE back when it was released and I've enjoyed every minute of it, I loved the stock rom - it was smooth and worked like a charm. I have a lot of experience with flashing ROMS, had quite a few HTC phones before this one, but so far haven't tried ANYTHING with the ONE.
I got the update to the latest Android and I noticed there's something about HBOOT 1.44 vs. 1.54 - I checked and I have the 4.2.2 ROM running HBOOT 1.54.
I really want to get into custom roms and start testing a few out; but I have no idea where to start.
Normally I'd pick a guide and work the steps but I'm hesitant now that I've read bits and pieces about this HBOOT thing - I'm not sure what I means, why people are bummed out because they have 1.54 (which I have).
So yeah, I have no idea where to start. Can somebody give me a rundown, some guidelines, what does HBOOT 1.54 mean for me, where do I start?
Thanks,
Michiel.

From what I've read, having HBOOT 1.54 basically means that you can't S-off your device (as this is only available for 1.44). This means that you won't have access to deeper customisation for your phone (flashing different firmware and changing CID). CID determines what region your phone belongs to so this translates to how early you can get official OTA's as some regions get updates earlier than others. Also, if you want to fully transform your phone into a Google Edition HTC One, this is only open to units with a specific CID.
As for firmware, not really clear on what the differences between firmwares are but you can still flash different radios which are a component of firmwares (thus getting some of the benefits of newer firmware anyway).
That being said, you can flash the whole range of custom ROMs and kernels available on these forums provided that you've unlocked your boot loader. Directions for this can be found on the HTC website.
If you want an optimised stock ROM, try ARHD Sense which is basically your stock ROM with many performance improvements (especially when it comes to signal). For more customisation on Sense, you can try ViperOne.
Honestly there are so many excellent ROMs here that you can easily lose days trying every single one. The Google Edition ROMs are excellent too.
Hope this helps!
Sent from my HTC One using XDA Premium 4 mobile app

Thank you both for detailed replies! This helped me ease my mind on the HBOOT-thing. Thanks!

What no one mentioned is that S-off allows you to remove the ****Tampered**** flag from the boot loader.
With S-off you can lock the boot loader. (With S-on it will show Re-Locked)
With S-off you can flash any RUU to return to stock. Without it you can only flash RUU's that match your CID and are newer than your current firmware.
These may not be important to you, but they're good to know before you jump in.
Sent from my HTC One using XDA Premium 4 mobile app

Michiel0211 said:
So here's the deal: I bought a HTC ONE back when it was released and I've enjoyed every minute of it, I loved the stock rom - it was smooth and worked like a charm. I have a lot of experience with flashing ROMS, had quite a few HTC phones before this one, but so far haven't tried ANYTHING with the ONE.
I got the update to the latest Android and I noticed there's something about HBOOT 1.44 vs. 1.54 - I checked and I have the 4.2.2 ROM running HBOOT 1.54.
I really want to get into custom roms and start testing a few out; but I have no idea where to start.
Normally I'd pick a guide and work the steps but I'm hesitant now that I've read bits and pieces about this HBOOT thing - I'm not sure what I means, why people are bummed out because they have 1.54 (which I have).
So yeah, I have no idea where to start. Can somebody give me a rundown, some guidelines, what does HBOOT 1.54 mean for me, where do I start?
Thanks,
Michiel.
Click to expand...
Click to collapse
All you have to do is unlock your bootloader via htcdev.com (note, this will wipe your data) and then flash a custom recovery. You can use this tool http://d-h.st/mas to simplify the process.

CoryTallman said:
What no one mentioned is that S-off allows you to remove the ****Tampered**** flag from the boot loader.
With S-off you can lock the boot loader. (With S-on it will show Re-Locked)
With S-off you can flash any RUU to return to stock. Without it you can only flash RUU's that match your CID and are newer than your current firmware.
These may not be important to you, but they're good to know before you jump in.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh sweet I think I found something helpful. I just got my HTC one 6 days ago. I'm s-off so no tampered tag. Do I need to change my cid to flash any ruu? Do I need s-on to flash ruu's? I'm with Rogers in Canada. No RUU for me but there are ota's. Can I flash a different ruu and then the Rogers ota to bring be back to stock? I have s off can I leave it off so if the hboot gets updated by a future ota it will be ok? Thanks for any help.
Sent from my HTC One using Tapatalk 4

sixty_oz said:
Oh sweet I think I found something helpful. I just got my HTC one 6 days ago. I'm s-off so no tampered tag. Do I need to change my cid to flash any ruu? Do I need s-on to flash ruu's? I'm with Rogers in Canada. No RUU for me but there are ota's. Can I flash a different ruu and then the Rogers ota to bring be back to stock? I have s off can I leave it off so if the hboot gets updated by a future ota it will be ok? Thanks for any help.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
No matter what, you should stay s-off, it does not affect OTA's or RUU's in any way whatsoever. To flash any RUU, you need to be with a cid of 11111111
It's not possible for you to flash an ruu for something else and then flash the rogers ota I don't think

[Q] Unsigned hboot vs. signed hboot

I am running Stock 4.3, rooted and S-OFF. When I flash a 1.44 modified bootloader for the purpose of removing red text the phone starts differently than it does when on the 1.55 signed bootloader. With 1.44 modified hboot when it first starts up you see the htc splash screen disappear for a split second, kinda like a flicker. It also does it going into recovery. When I use the stock 1.55 hboot it starts normal, no flicker. I have tried 1.44 from this source http://forum.xda-developers.com/showthread.php?t=2314921 and have also used one from RegawMod customizer and they both do the same thing. I tried finding 1.44 hboot from moonshine but no luck. Is this normal behavior with the modified 1.44 hboots as far as the flickering goes? Is this because 1.44 are un-signed vs. the signed 1.55?

-Apollo- said:
I am running Stock 4.3, rooted and S-OFF. When I flash a 1.44 modified bootloader for the purpose of removing red text the phone starts differently than it does when on the 1.55 signed bootloader. With 1.44 modified hboot when it first starts up you see the htc splash screen disappear for a split second, kinda like a flicker. It also does it going into recovery. When I use the stock 1.55 hboot it starts normal, no flicker. I have tried 1.44 from this source http://forum.xda-developers.com/showthread.php?t=2314921 and have also used one from RegawMod customizer and they both do the same thing. I tried finding 1.44 hboot from moonshine but no luck. Is this normal behavior with the modified 1.44 hboots as far as the flickering goes? Is this because 1.44 are un-signed vs. the signed 1.55?
Click to expand...
Click to collapse
I think I flashed the same hboot from http://forum.xda-developers.com/showthread.php?t=2314921 but I dont recall seeing what you're describing....I can tell u though, on moonshines hboot, I see the HTC quietly brilliant screen for 5 secs or so

O.M.J said:
I think I flashed the same hboot from http://forum.xda-developers.com/showthread.php?t=2314921 but I dont recall seeing what you're describing....I can tell u though, on moonshines hboot, I see the HTC quietly brilliant screen for 5 secs or so
Click to expand...
Click to collapse
Probably something on my end then. It's no big deal, phone runs fine, I was just curious if anyone else saw this behavior.

T-MOUS S-Off on newest hboot 1.57.0000(what I did)

Let me start off with I think I got lucky. Try this at your own risk. I locked my bootloader and turned my security back on for a TMOUS warranty exchange for the dreaded purple tint in camera. I received my replacement only to find out that in fluorescent lighting the replacement HTC ONE M7 had a greenish tint but only under fluorescent lighting. So I am getting another replacement sent for free. This is where my troubles begin. I decided to unlock my bootloader for my original phone again and root it so I can set everything up again for daily use. I got through all those steps fairly easy. FYI: original phone is on newest TMOUS OTA_M7_UL_K44_SENSE60_MR_TMOUS_5.14.531.1_R-4.19.531.10_release_373019xng22l97gj5szmwv. I then relocked the phone and tried to flash RUU Zip M7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2_decrypted.zip in order to achieve s-off again but to no success. Hboot 1.57.000 with S-ON wasn't having any of it I guess.
I unlocked bootloader and relocked bootloader several times trying several different methods to no success. Oh, my recovery was TWRP 2.7.0.0. At some point I realized that if I was going to return this phone I needed to get s-off again to remove tampered flag and actually lock phone instead of relock. I happened to come across a stock rom that I decided to install in hopes of accomplishing S-off. Stock 3.24.531.3 T-Mobile.zip was the rom. Long story. I know. So here is what I did;
Unlocked bootloader
Flashed TWRP and gained root using WinDroid Universal HTC Toolkit
Installed Stock 3.24.531.3 T-Mobile.zip ROM via TWRP
Phone would not fully boot past HTC ONE Animation screen
powered down and powered back on into bootloader
relocked bootloader and rebooted bootloader
unlocked bootloader again
Phone now booted completely into the stock rom I flashed
Proceeded to use firewater for S-off
Didn't work first time
Powered down phone by holding power button and rebooted normally
Tried firewater again and to my luck the SOB worked and I am S-Off again on newest HTC One TMOUS with an older Stock 3.24.531.3 T-Mobile rom
I'm sorry if I have no links to anything I mentioned but I am new to this so I don't really know how to link to other stuff I found on the site. Thanks to all the great people whose tools and rom I used to achieve S-off again.

Prior to doing those steps firewater would not get past the first chugging stage.

If you got the chugging message you were always going to be able to s off it. Firewater isn't worried about the hboot so much as the version of your cpu as to whether the exploit will work on it
Sent from my HTC One using XDA Premium 4 mobile app

It would get to the chugging and sit there for bit then kick the phone back to root command. It didn't matter how many times I tried it would always do the same thing at the same spot. I would then have to reboot the phone and try again but no success. I'm just sharing what I did and worked for me. Clearly the exploit didn't want to work before I did the steps I took. I wouldn't have spent almost 30 hours of reading and trying to fix the problem I caused otherwise. Maybe it was a fluke or dumb luck. I don't know.

Where can I find this stock rom?

Nevermind this did not work.

[Q] HTC One converted to GPe x2 - Recovery doesn't work

Anyone else converted their M7 to a GPe and are now unable to access the stock recovery? I suspect thats why my two HTC one's aren't OTA updating. Here's the facts:
#1, HTC One, converted a long time ago, updated OTA no problem to 5.0.1. 1st two screenshots are for this phone.
OS = 5.0.1
HBOOT = 1.54
***RELOCKED***
S-OFF
#2, HTC One, just tried to convert. Flashed RUU no problem but recovery wouldn't work right after flashing. 3rd and fourth screenshot are for this phone
OS = 4.4
HBOOT = 1.54
***UNLOCKED***
S-OFF
Am i doing something wrong? Or epic failing?
Thank you

Press power and vol up in the recovery to see the menu.

Unlocked, S-OFF, SuperCID. Flash hboot 1.44?

Hi all. I just unlocked my HTC m7 (GSM) with HTCdev.com and then installed TWRP and used that to install SuperSU. After that, I ran Sunshine to get S-OFF, and then I ran Guru Bootloader Reset in order to remove the "tampered" flag. Then I set SuperCID to 11111111, and I think I'm ready to flash a rom (I"m looking at ViperOne, since I used it on my Sensation and liked it).
I'm on hboot 1.61. Is it worth downgrading to 1.44 so that I can easily get s-on/s-off in the future? If so, should I flash the new hboot before or after the rom? Does it matter?
Thanks all. I spent quite a bit of time flashing and testing roms on my HTC Touch Pro and then my HTC Sensation. I've held off for a couple of years, but I'm looking forward to playing around with my M7 again!

MPenguin said:
(...), I ran Sunshine to get S-OFF
(...)
I'm on hboot 1.61. Is it worth downgrading to 1.44 so that I can easily get s-on/s-off in the future? If so, should I flash the new hboot before or after the rom? Does it matter?
Thanks all. I spent quite a bit of time flashing and testing roms on my HTC Touch Pro and then my HTC Sensation. I've held off for a couple of years, but I'm looking forward to playing around with my M7 again!
Click to expand...
Click to collapse
Your phone is already S-OFF why would you want to turn it back S-ON? Never go back S-ON, the only time it should be done is before sending the phone for repair under warranty. Going back S-ON is the same as intentionally locking your car with the keys left inside... And even if you go back S-ON why hboot 1.44 should make it easier to achieve S-OFF again? You just paid for Sunshine, you can use it as many time as you want on that phone + If you already have paid for Sunshine, its actually the easiest method to S-OFF your phone on any hboot version.
If I buy a SunShine license, can I use it on multiple phones?
No - one license is good for one device. You can reuse SunShine on that device, if necessary, we however NEVER recommending setting your device S-ON
Click to expand...
Click to collapse
ref: http://theroot.ninja/faq.html
Another thing to know is that hboot 1.44 is incompatible with windows 8 and 10, so say goodbye to fastboot connectivity (fastboot commands) after flashing it, unless you are using a Mac, Win7 or Linux.
For your last question, it doesn't matter when you flash the hboot, if you need to flash one. Would recommend to stay on 1.61