yashsingh1/xdaforums huggingface dataset:
[HTC One S] Wel1973:
But it would do it if it had a Recovery Custom .... if I have Stock Recovery, it would not be like that. The red text would leave ....?

And a last question..

It returns the state of S-On when flashing?

I remember in other devices with S-Off of Htc, that when you were loading a Ruu with his Hboot determined previously installed, it was changing the state of this flag, that's why of the previous questions. but only bring back red text.

Thank you very much for your answers. :good:

Greetings.
[HTC One S] touch of jobo:
Neither these original ones nor the modified ones from post#148 affect the S-on/off status. Flashing them does not get you back to s-on.
[HTC One S] trathiang:
Real noob question but I'm paranoid when it comes to hboot. I flashed the 2.15 in order to get rid of the red text on the boot splash. I read somewhere that "fastboot oem lock" on a modified hboot bricks the phone, would that happen with mine if I tried it? Should I flash one of the original hboots you posted first?
[HTC One S] veeny101:
Can you make a black one for 2.15. Thank you.
[HTC One S] touch of jobo:
I don't expect that locking the bootloader will brick you, because you're still s-off.

If you go back to s-on on a modified bootloader, that will probably result in a brick.

But before re-locking OR S-On'ing, I would always RUU the device first.

The boot splash zip's (that change the picture) are not specific to hboot versions. They just don't work on higher (than 1.09) hboots if you're S-On.

So if you're s-off or on a low hboot, then you can just flash the boot splash of your choice or make your own one using the online generator.

The modified hboots that I posted up are just to get rid of the overlaid red warning text. You must be S-Off for those.
[HTC One S] Sneakyghost:
AW: [HOW-TO] Change your Boot Splash + Flashable ZIPs + Online Generator + Warning Go

That dude Scotty-something who runs the restore- to- stock thread pointed out that setting security to ON while on a modified hboot will brick the device, yet there is no risk at all for a simple relock.

sent from viper 2.2 Beta
[HTC One S] fegato:
hello!

I did a REALLY black version of the stock bootsplash as the one posted seemed not exactly black

enjoy :cool:

View attachment bootsplash_reallyblack.zip
[HTC One S] touch of jobo:
That makes sense, as it is basically the same as what donverse did - flashing a modded hboot while s-on - but in the reverse order.

On an unrelated note .. made an engine block splash:
[HTC One S] rootrider:
lol

Nice idea so.
[HTC One S] adamfirari:
after installing new hboot , i cant use fastboot command, it says "remote: not allowed". any idea for my problem?

i want to use fastboot for flashing recovery. i had TWRP.But it gives me problem when installing sence base roms
[HTC One S] touch of jobo:
Is your bootloader (re-)locked?
[HTC One S] adamfirari:
yes
[HTC One S] touch of jobo:
Then that's why. You can't flash a recovery on a locked bootloader.

I bet you could not flash a recovery either before flashing a new hboot; it's unrelated. And I bet that your device was unlocked when you flashed TWRP onto it.
[HTC One S] adamfirari:
maybe flashing recovery related with locked bootloader but fastboot unlocktoken is also not working .
[HTC One S] Sneakyghost:
AW: [HOW-TO] Change your Boot Splash + Flashable ZIPs + Online Generator + Warning Go

Unlock token needs to be renewed when hboot has changed.

Sent from Viper 2.2
[HTC One S] touch of jobo:
What are you saying?

* The unlock token that you used before doesn't work anymore

(This is normal. You have to get a new identifier token and submit it at htcdev.)

OR

* You are unable to get an identifier token via fastboot

(The correct command is: fastboot oem get_identifier_token

what error message do you get?)
[HTC One S] adamfirari:
thanks.i will try to get new unlock code
[HTC One S] LibertyMonger:
Wow this is awesome thanks a bunch for sharing! You know it would be cool if someone could make personalized ones and sell them for a few bucks, I would buy one for my niece! lol. She would love a hot pink peace sign with her name. Thanks again my phone keeps getting better each day cause of all of the great people here!
[HTC One S] Darknites:
Em did you just only found this thread? lol also it wouldn't be hard to make what you want.
[HTC One S] LibertyMonger:
OH NO! I did this with my phone with no issues, just tried the same with my nieces and now it will not power up! Or reboot! I am screwed! I don't know what to do
[HTC One S] Darknites:
What the Hboot mod? if so it bricked I believe, guess you got unlucky.
[HTC One S] LibertyMonger:
Yeah I can't reset it or anything it's bricked! S.O.B.
[HTC One S] Darknites:
Dam that sucks. Didn't think it would do it to you since you did you downgrade and S-Off'd and then a simple mod kills it, that's just messed up.
[HTC One S] LibertyMonger:
My PC recognizes it when I plug it in but it will not reboot or reset. I guess there is nothing I can do huh? This sucks. S-off with Hboot 1.06
[HTC One S] Darknites:
Only JTag or send it to HTC or who ever for you.

Oh did you get sign up on the site?
[HTC One S] LibertyMonger:
I got insurance on it through my carrier, but will unlocking it at HTC effect my insurance? I hope not. Man this is an awful feeling lol. Got greedy!
[HTC One S] touch of jobo:
Are you sure the device was S-Off? On hboot-1.06 and S-On you can technically write to p12 but it bricks. That's what donverse did. (He also had 2 devices; one was s-on.) If you're sure you were S-Off, then I don't know what's happened and whether I should remove those zips I posted.

This is the first instance of a brick from flashing these hboots on an S-Off device. They have been downloaded almost 800x, so probably flashed well over 100x.

If you're in qhsusb mode, you can look into the downgrade process to push a clean hboot-1.06 into p12.
[HTC One S] LibertyMonger:
There is no charging light or reset lights but when I hold power while plugged into USB the PC makes the usb connect and disconnect sounds, but no screen on or power. I wonder if I did some steps in the downgrade thread if I can magically revive it? Has to be some way it seems. Oh well guess I have to call insurance?

---------- Post added at 12:43 PM ---------- Previous post was at 12:40 PM ----------

Thanks man, Yeah it was S-Off. Can you give me a starting point in the downgrade process?
[HTC One S] Darknites:
I just think its the same issue that happened with the JB OTA update when you had SuperCID. Just put a big warning saying this may brick it and S-Off has had its own issues too.

---------- Post added at 04:46 PM ---------- Previous post was at 04:45 PM ----------

Just tell them it it ran of battery and won't turn back on.
[HTC One S] touch of jobo:
Damn!

Did you by any chance use the broken version of TWRP? (I think is it 2.4.3 that has issues.)

This is the thread: [TUT] Downgrade/Unbrick Ville S4

If that doesnt work out, there is always this thread.

I have flashed all of them successfully with superCID. Some even multiple times when I was testing the unmodified ones I posted up later. But yeah, I will add an extra warning that we now have a brick on S-Off.
[HTC One S] Darknites:
Ya it didn't brick everyone but there was a fair few bricks with the OTA and even a few with the downgrade.
[HTC One S] Sneakyghost:
AW: [HOW-TO] Change your Boot Splash + Flashable ZIPs + Online Generator + Warning Go

I was very sure that there will be bricks from this, I even expected it to happen to me. Writing to p12 is always dangerous. One little anomaly in the process is enough to make the device unbootable just due to the nature of that partition. If you have faults while flashing a ROM, you just repeat the process. If you have that with the boatloader, the natural consequence is that it won't boot. Simple.

A big fat warning is a must for this. People need to know that they risk a brick when messing with p12, in fact, p14, the splash, can also brick the device I think.

Sent from Viper 2.2
[HTC One S] LibertyMonger:
I was on TWRP 2.3.3 or whatever it is. I tried the downgrade process from the point where the light is out and Ubuntu isn't detecting USB. So I don't know. I knew the risks so don't feel bad just in case you do lol. No hard feelings, I am just greedy. I should be able to claim it on insurance, in the meantime I will have to give her my One S. But I would still like to work my way out of this if possible.
[HTC One S] Darknites:
You can't and doing anything just makes it worse so I would just send it off.
[HTC One S] LibertyMonger:
Yeah Thanks bro. I shouldn't have any issues with insurance. And luckily I have my GNex or I would have never tried it. It worked for my HTC and it was on TWRP 2.4.2 so I don't know what happened. Thanks guys.
[HTC One S] Darknites:
I just think one of then random things that like to happen to this phone.
[HTC One S] LibertyMonger:
I get my niece on the weekends and I have limited time to update her device. Working with my phone is easy and less stressful so when I update hers the same as mine I rush into it knowing how easy it is and how I have done it a thousand times before but since I am under a time restraint and worried about getting it done right, I get these weird screwed up issues and it turns into a mess. What usually would take me minutes to do with my phone ends up taking hours to do with hers Lmao. So I don't know what went wrong, it's just one of those deals where I should have left well enough alone.
[HTC One S] LibertyMonger:
I claimed it on insurance and they said as long as it doesn't show any physical damage there will be no charge. Next day would have been $35, 2nd day would have been $15 and 2nd business day shipping is free :victory:

Sorry if I made a mess of your thread man, I hope it was my mistake and no one else experiences it.
[HTC One S] touch of jobo:
Of course I feel bad .. well, not happy anyway. It's a nasty thing to happen to anyone. In fact I've been pretty reckless with mine just to prevent this from happening to others.

It would be nice to know that for sure. But since there is no way anymore to find out, we have to assume that there are (unknown) factors that cause brickage on s-off.

..and on a somewhat related note:
[HTC One S] Sneakyghost:
AW: [HOW-TO] Change your Boot Splash + Flashable ZIPs + Online Generator + Warning Go

There's been a very important question a few posts back and no-one stumbled over it.

Which recovery? As you know the later TWRP doesn't flash things right.

I'd put up a big warning regarding TWRP as we don't know for sure that it's NOT been the recovery causing it. There's a srtring likelihood that it's caused by that.

Please inform people about the additional risk right where the downloads are.

If you don't, then you will have reason to feel bad ;)

Sent from Viper 2.2
[HTC One S] touch of jobo:
Already put some more red bold warnings in that post.

Do you know the exact (range of) version(s) of TWRP that are bad?

I think 2.4.3 has issues, I'm not sure about 2.3.x, and AFAIK 2.2.x is good. And all CWMs are good.
[HTC One S] Sneakyghost:
! BRICK VERIFIED AND RECREATED !​

BIG FAT BOLD RED WARINING:​

TWRP 2.4.3.0 WILL BRICK YOUR PHONE WHEN FLASHING MODIFIED (AND POSSIBLY ORIGINAL) HBOOTS!​

Additional VERY IMPORTANT notice from Tecardo:

Recoveries are generally not fit to securely flash a hboot! There is a technical reason for this! The risk of a brick through flashing hboots by means of a recovery is extraordinarily high!

Touch of Jobo, i recommend you pull all recovery zips ASAP and offer only the raw images with a guide on how to flash them, for reasons of user protection!

@Liberty-Monger:

It wasn't entirely your fault. It was a bad thing to happen but you helped finding out and thus helped the community big time to not run into the same issue. Thanks for being the involuntary Guinea Pig! :D :(
[HTC One S] Tecardo:
The splash screen flash should be ok :D
[HTC One S] LibertyMonger:
There's only two things I can think of that was different between the two phones, 1 was TWRP version, hers was 2.3.3 and mine is 2.4.2, it worked with mine and not hers, and I don't think I ever changed her bootsplash image, I think it was still the stock one. Sorry I can't provide any more details.
[HTC One S] Sneakyghost:
Sure it wasn't 2.4.3.0 ? ?

Then that just underlines the necessity to refrain from using ANY recovery to flash hboots.

Tec tried to explain it to me but i didn't quite understand or else i would have explained it here on thread but flashing hboots from within recovery is dangerous.
[HTC One S] LibertyMonger:
WOW sweet dude! Thanks for the pic!! I will most definitely be using that when I get my new replacement and trying this again lol. I'm not scared! Lmao!
[HTC One S] Sneakyghost:
You better flash it with a different method then and not with a recovery anymore...
[HTC One S] LibertyMonger:
I'm absolutely positive hers was 2.3.3 cause i checked it beforehand and I haven't updated her phone since Viper ICS. Mine is 2.4.2

---------- Post added at 08:21 PM ---------- Previous post was at 08:10 PM ----------

Yeah thanks man, I'm all out of thanks or I would give you one lol. I'm enjoying no red warning on my device so I had a 50/50 chance of bricking it I guess lol.

---------- Post added at 08:24 PM ---------- Previous post was at 08:21 PM ----------

Well I can't say i haven't updated it since ICS, I did but it was too early for JellyBean version she wanted to stick with ICS at the time cause of her theme. But it's been a long time since I messed with her phone. It's been since the initial release of s-off

PS... after flashing this hboot mod it flashed successful but went to black screen after reboot.
[HTC One S] Sneakyghost:
You see, while flashing something, even hboot, everything operates in RAM. So you can write any bullsh!t to any partition except live partitions like /system while being booted and you can write to all partitions from recovery, even to the recovery partition (as that is opertional from RAM). This is provided your device is Security-OFF. If it was S-ON, certain partitions would have a write-protect to protect you from exactly what you did.

If you now write to the partition where the bootloader is and it screws up, the phone stays operational until you reboot, simply because the bootloader is not needed during normal operation, its sole task is to load any operating system into RAM from the initial press of the power button.

This of course is a simplified version of the internal ongoings.

This scenario also offers a minimal security if you know about it: since the phone won't brick instantly, you can still write back a healthy hboot with e.g. a "dd" command if you happen to notice that the flash screwed up. You only need to educate yourself on how to detect a failed hboot write, or at least get some intuition for these kinda things, so you keep yourself from hitting reboot if you get that odd feeling.

As long as your phone is live you can recover it.
[HTC One S] LibertyMonger:
I stayed up all night fixing her phone up, upgrading it to Viper 2.2 and making her an AOSP backup nandroid and went to bed around 4am without fixing all of her settings and stuff, then I was looking around in Themes and apps to see if I could find something she would like and then I seen this thread for the first time lol. So I tried it on my device first and then rushed to do hers before it was time for her to leave. I don't know the exact reason why it happened but I do know I need to be more careful. I should have left it alone til next weekend when I had more time. Everything in here is fairly simple and always extremely easy when I do things with my device, cause I am not under any pressure, but when I start fooling with someone elses device I always run into snags and it always takes me longer than usual. It's the pressure of being responsible for someone elses device I guess, I am sure we have all experienced it, where you talk your girlfriend or somebody into jackin up their phone, and you tell them how awesome and easy and how much better it is and it backfires and smacks you in the face Lmao. That is what happened to me. Maybe I should have used the same TWRP as I used for mine. Anyway, it is a step closer to more precautions I guess and I am proud to be the useful idiot Lol.
[HTC One S] Sneakyghost:
maybe baby shoulda woulda been betta.... u never know n we all know that story n all it does it teaches u a painful lesson. mine was coupla hundred bucks a few times, well speaking new devices prices...

Important thing is to learn to closely observe whats going on when trying new things so in case something goes wrong you can tell the community and help others to avoid. Like this time you weren't exactly precise but had an idea what was going on so it was enough for Tec to repro it and that makes sure people will in future avoid this situation. If they're smart enough to read a bit here... So thanks for that dude.
[HTC One S] Darknites:
I like to add that it worked for me on TWRP 2.3.3.0.
[HTC One S] Sneakyghost:
I like to repeat that Tecardo pointed out there is a technical problem with flashing hboots through Recovery which makes the Brick Risk increase a lot.

It has to do with bit-correct write operations which are not guaranteed from recovery. One flipped bit is enough to cause a brick. So this applies to stock hboots too. It is a general warning to flash hboots from recovery.

But otherwise, 2.3 should be OK. 2.4.3.0 is the one which is worst obviously. The version 2.4.4.0 hasn't had much feedback yet.
[HTC One S] Darknites:
Ya I'm in no rush to change it but do you think the manual way is better or just as risky.
[HTC One S] Sneakyghost:
To be quite honest, i have forgotten how to change hboot without using dd.

Which is the same method as Recovery. I am also using dd all the time but i need to reconsider. Its very Late/Early here. nearly 5 AM. Will look into it tomorrow (flashing from fastboot).
[HTC One S] Darknites:
Oh right, not really messed with Hboot other then the downgrade and S-Off and this mod so I think I stop there lol.
[HTC One S] rootrider:
Same thing here.
[HTC One S] Tecardo:
Changing Recovery: Get you a ota firmware.zip

Change the interneal partition (only let the hboot in there and replace it with the hboot you want) and flash how you normally flash a firmware.zip ;)
[HTC One S] Sneakyghost:
AW: [HOW-TO] Change your Boot Splash + Flashable ZIPs + Online Generator + Warning Go

Thanks. That was it. Now I remember.

Here's a step-by-step for n00bies or those who suffer from digital dementia like i do:

I. grab an empty OTA.zip.

II. insert your desired hboot in there just like tec said. You can use 7zip for that (just drag in your hboot and delete the original one)

III. put that into the folder where your ADB.exe and Fastboot.exe sit. Search it if you don't know that (hint hint i copied all adb and fastboot relevant files to C:\Android to have it easier with CMD commands). Once your zip is there, put phone to fastboot mode and then just open command and navigate to that folder (cd c:\android or whatever is your path).

IV. Now type:

1. fastboot oem lock (device should be relocked for this or else the ota.zip won't flash i think, just try without and see if it works)

2. Fastboot oem rebootRUU (this reboots into the RUU mode you usually see when you run a RUU)

3. fastboot flash zip [nameofyourzip].zip (this command can be typed again if it throws an error the first time)

4. fastboot reboot-bootloader (this command will bring you back to bootloader where you can see if your hboot changed)

Alternatively:

4.a. fastboot reboot (that will bring you straight back to your system).

[EDIT]

Numbers I. to IV. are bollocks, don't work like that. check Touch Of Jobo's follow-up post for ready-made zips. Sorry. I am humiliated :D
[HTC One S] touch of jobo:
fastboot

Since it it now considered bad practice to flash hboot in recovery, I have repackaged all the zips to be fastboot flashable in RUU mode.

Recipe:

boot your Ville into fastboot mode,

connect USB cable,

on your PC open a terminal window / command prompt.

fastboot oem rebootRUU

wait for black screen with white HTC text

fastboot flash zip modded_hboot_1.13.0000.zip

(.. or whichever .zip you choose. It should say OKAY)

fastboot reboot-bootloader

To reboot into fastboot mode using the new hboot.

orig_ = unmodified, straight from the RUU.

modded_ = red warning text edited out.

Edit

: @Sneakyghost:

I was just typing that :p

Step I, II and III, are already done.

In step IV, you dont have to be bootloader locked. At least not if you're S-Off. I don't know about S-On.

Edit

: Added hboot 2.16 - orig and modded.
[HTC One S] Sneakyghost:
Yeah mate you seriously ROCK!

I sit here since half an hour taking apart the 3.16 OTA zip and try to reconfigure the updater-script and also try to modify the firmware.zip and i fail.

:banghead:

I now hate myself. I am going to flash a modified hboot to my head with the wrong recovery. I will brick my head. :( :laugh:

[EDIT]

Is that really all there is? An Android-Info.txt plus the hboot-file?

I was looking at the OTA structure and its quite complex due to the included system update. I was trying to take that out for one and secondly i attempted to edit the firmware.zip in there. The updater script has a write_firmware_package command i also had never seen before so i assumed for the whole thing to work i would need to leave the ota.zip structure mostly intact and just edit it according to our needs.

I was totally unaware of the fact that the firmware-package doesn't need to be included into an ota.zip but can rather be flashed straight as is.

Then: how did you manage to edit that firmware.zip? All my archivers where throwing errors????
[HTC One S] touch of jobo:
Uhm .. apparently ;) ... it works for me. I've tested them on my own device.

But then I guess you're flashing firmware in recovery, which is frowned upon. Except that in the case of an OTA it's supposed to be the stock recovery, and trusted to be safe.

I didn't edit any zip file. I just zipped up those 2 files together. Like:

jobuntu:~ jobo$ zip modded_hboot_1.06.0000.zip android-info.txt hboot.nb0
[HTC One S] Sneakyghost:
Yea second mistake of mine: the original OTA Zip flashes some stuff through recovery, although the updater-script looks like its not flashing the actual firmware-zip through recovery, but also not sure. Not very good at reading that code.

Touch, i got an Android-Tasker script (CMD) which i once wrote for myself to accomplish all those bothersome command tasks. I am now editing it to offer a selection of hboots and flash the selected one with a one-click style action.

You OK with that? I'd post it here, just as an additional service. I do that mainly for learning stuff.

[EDIT]

I am having trouble flashing the edited hboots this way. The original hboots flash fine but not the modified ones, not sure where the error is yet.
[HTC One S] touch of jobo:
I'm OK with you posting stuff in here, but a couple of thoughts to consider:

* Flashing hboots doesnt need to be

easy

but it does need to be

safe

. It's not something that people would (

or should!!

) do often. Maybe once to get rid of the red text and once to get back to stock. There is no known advantage of one hboot over another on S-Off anyway.

Also, flashing while booted in android may be somewhat safer from a kernel point of view, but there is so much other stuff going on that the whole environment is less predictable (than in recovery or especially fastboot/RUU mode).

* This thread was supposed to be about boot screen modding. (Yes, I know we took a bit of left turn..)

So it could make more sense to edit your script to convert and flash splashes than hboots, (Writing to p14 is totally safe any time. You can literally dump garbage into it and you get color-noise as a splash.) or open a thread on learning stuff about how to write android tasker commands to mod and manipulate the device.

But again, you're welcome to post anything in here that you feel is appropriate and maybe even useful.

-Jobo

Which one? What error message do you get?