[SOFF] Hboot mod - Clean Mask And clean splash

[simonsickle]

So, while I see that there was a hboot list already posted, but it was not said how it was done. So I decided to work on this and post how..

NOTE: You will need hex edit skills, and knowledge. Bricking your device is your own fault. I take no blame, nor do I feel bad if you cant read.


For SOFF to SON mask
Find S-OFF
Replace the First F with an N and the second with a space.

RED TEXT REMOVAL:
Find the red text that is listed on the screen when booting. You will find it, just ctrl+f. Now replace letters with the space.
DO NOT REPLACE 00 IN HEX. IF YOU SEE 2E YOU DO REPLACE IT WITH 20

REMOVE TAMPERED
Find TAMPERED
overwrite the *** TAMPERED *** with all spaces. DO NOT get anything beyond that scope.

More mods on the way. Starting with the removal of Powered by android from the bottom.

THIS IS FOR SPRINT ONLY!!!
DOWNLOAD
MD5: 665c0b2e7a60e8c698da43a4ae372e21

After checking md5 to flash
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip m8_whl_hbootmod.zip
fastboot reboot-bootloader

Done! Enjoy your hboot. Please note this is just for educational purposes, and I posted the hboot so if your learning you can compare There is another thread, and this is how he did it.

For splash screens:
For stock HTC splash without "powered by android" at bottom -> here
MD5: 94348f2b13f9020267f57dee0dd2fa47

Stock htc no android YELLOW HTC logo -> here
MD5: 5b498645995f4df4a4523e87d9bc969f

To flash:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip nameof.zip
fastboot reboot


Enjoy!

 

[JT man]

Nice guides buddy thanks for contributing...

Sent from my SM-N900T using Tapatalk

 

[simonsickle]

I have got the Verizon splash screen (no powered by android at the bottom) and I've successfully flashed it. I will post more about it tomorrow.

Sent from my 831C using Tapatalk

 

[simonsickle]

Added splash screens to OP

 

[MassStash]

What's the block to set for flashing splashes? Was going to make some splash screen flushables other day, but ignorant to how to find out which block needs to be configured. Assumed I couldn't just use m7 splashes, and may flash to wrong place and Bork stuff haha

~m8whl modded stock
2.265 Max ¦ 300 Min
ondemand
row

 

[simonsickle]

Lol. ... Just use the zip

Sent from my 831C using Tapatalk

 

[Sloth]

Lol. ... Just use the zip

Sent from my 831C using Tapatalk

Can we replace the splash1.img with myowncreation.img?

 

[simonsickle]

Can we replace the splash1.img with myowncreation.img?

Yeah. But they use a new bmp color scheme now...that's how I got the yellow . Total accident

Sent from my 831C using Tapatalk

 

[Sloth]

Yeah. But they use a new bmp color scheme now...that's how I got the yellow . Total accident

Sent from my 831C using Tapatalk

I was thinking of using something like this...

 

[simonsickle]

If I get time I'll work on fixing the tool. But until then I'm working on some big projects

Sent from my 831C using Tapatalk

 

[Sim-X]

Very nice write up. :good:

So I have an old m7 splash I would like to use. Would I have to modify the .img file at all or can I just pull the android-info from one of these zips and put it with my .img that was made for the m7?

 

[MassStash]

Need new thread for splash talk brah

~Jflteusc on OctOS
KToonsez Kernel
1.998 Max ¦ 189 Min ¦ 702 Screen Off
Ktoonsified v5 Setup

 

[lucky_515]

hey,i flashed this hboot zip..it changed in bootloader screen,to locked,and s-on..witch is very cool,and was really easy,i diddnt think it was gonna change it to locked,i diddnt read that part,thought was only gonna change to s-on and a clean splash screen without the red text..one thing that does concern me thoughg,mu os also changed all the way back to 1.5 something,im sorry cant remember the exact num without going back to it..but is this normal??cause i just took the update via RUU last week to the latest firmware..should i be concerned about this?it just got changed with the zip i flashed right?ive got to still be latest firmware,cause all this was ,was a modified hboot zip...anyways,just wanted to know if you knew it also changes the os version?,cought me off gaurd..lol..thank you for the work though,looks lot better

 

[Sloth]

hey,i flashed this hboot zip..it changed in bootloader screen,to locked,and s-on..witch is very cool,and was really easy,i diddnt think it was gonna change it to locked,i diddnt read that part,thought was only gonna change to s-on and a clean splash screen without the red text..one thing that does concern me thoughg,mu os also changed all the way back to 1.5 something,im sorry cant remember the exact num without going back to it..but is this normal??cause i just took the update via RUU last week to the latest firmware..should i be concerned about this?it just got changed with the zip i flashed right?ive got to still be latest firmware,cause all this was ,was a modified hboot zip...anyways,just wanted to know if you knew it also changes the os version?,cought me off gaurd..lol..thank you for the work though,looks lot better

There are more up to date masked hboots in Android Dev

 

[simonsickle]

Bootloader updates are pretty useless. It's kind of like bios updates really. All of the other firmware stays, but this remains. I don't feel a need to update something that still works is all

 

[Captain_Throwback]

Bootloader updates are pretty useless. It's kind of like bios updates really. All of the other firmware stays, but this remains. I don't feel a need to update something that still works is all

On the M8, HBOOT needs to be updated for the newer software versions to even boot.

So in this case, it's like the new OS added a feature that requires a BIOS update. It happens.

But, as was stated, there are newer version out there. You might just want to add a disclaimer that this will only work with 1.xx based ROMs, because once you move up to 2.xx and 3.xx, you'll have issues (like WiFi not working).

I guess you haven't been keeping up with the firmware situation on this device . . .

 

[simonsickle]

On the M8, HBOOT needs to be updated for the newer software versions to even boot.

So in this case, it's like the new OS added a feature that requires a BIOS update. It happens.

But, as was stated, there are newer version out there. You might just want to add a disclaimer that this will only work with 1.xx based ROMs, because once you move up to 2.xx and 3.xx, you'll have issues (like WiFi not working).

I guess you haven't been keeping up with the firmware situation on this device . . .

I'm currently using this hboot with the newest firmware and can use stock and cm just fine, no issue in any regard. Maybe GSM has this issue, but I do not (and I develop for myself, and share with others anyways). Everyone can use whichever one they feel that's the best, but as I said, this works for me and I won't change anything on an unfounded basis for this model.

 

[Captain_Throwback]

I'm currently using this hboot with the newest firmware and can use stock and cm just fine, no issue in any regard. Maybe GSM has this issue, but I do not (and I develop for myself, and share with others anyways). Everyone can use whichever one they feel that's the best, but as I said, this works for me and I won't change anything on an unfounded basis for this model.

Not sure how you're managing that, but good for you, I guess. Everyone else has issues with the old HBOOT on the new base ROMs. Since there are other options, I suppose It doesn't matter anyway.

 

[benny3]

Im using firewater's hboot without any issues and im on the latest firmware

 

[simonsickle]

Im using firewater's hboot without any issues and im on the latest firmware

Just proves, Humanity is very susceptible to the placebo effect... How many new things have we bought, just because they're new and therefore better, only to find out we spent a couple hundred dollars on a piece crap.