yashsingh1/xdaforums huggingface dataset:
[HTC One S] touch of jobo:
If your recovery is good, it is safer than while booted, because less other stuff is going on. I guess what it comes down to is that kernels used in recoveries are under less scrutiny than those used in full roms, so there is a higher chance of issues slipping through unnoticed. (Unnoticed until someone does something different and bricks.)

Ha! You dont have to be polite if you think its cheesy (I do .. my scrapbooking skillz). But you said peace and pink so I figured rainbow. :eek: If you do like it, here is the gimp file so you can change the text.
[HTC One S] Sneakyghost:
Hboot Flasher batch script

Read your post too late. Work done so i will post it. Took me ages because when scripting fastboot oem rebootRUU with a flash zip command in succession, it always fails and it took me ages to figure out there needs to be a wait inbetween because fastboot oem rebootRUU doesn't seem to wait whereas the normal fastboot reboot contains a wait for device function somehow.

Here's the Flasher packed in a self extracting WinRAR archive:

LINK to HBOOT Flasher

13th of may 2013

- Added option 16: open CMD Prompt (to be able to quickly change CID when the zips refuse to flash...)

05th of may 2013:

-corrected an error in the script.

-inserted a confirm for S-OFF and Product at launch-time

If i understand this right, the RUU mode can also flash to p14 as splash, can't it? i mean the RUU would also update that part wouldn't it? So actually i can just adapt this script to flash the respective splash files but i would need to know how to name them correctly so its not flashing the p14 to p12 or some evil sh!t like that :laugh:

would you know how that would look like correctly done?

[EDIT]

The Hboot files all contain HTC__001 in the Android-info.txt file. I just had one user who could not flash them on his HTC__102 device.

If you happen to get error 42 wrong customer ID and get stuck in RUU Mode, please just run this command in CMD: "fastboot oem writecid HTC__001" and then repeat the hboot flash. It will be good then. Avoid rebooting the phone, just leave it stuck where it is and do the writecid command, then repeat the hboot flash. I updated the script so that option 16 opens a command prompt for you in the right place.

Also i forgot to point out this: the flasher script does NOT reboot the phone when its finished to give u a chance to see if everything worked good. You have to pick option 14 (reboot to bootloader) or 15 (reboot to system) afterwards to reboot. The green progress-bar on the phone will stop at about 3/4 of the way. That is normal! It only moves on when you do the reboot command!

It basically is to hold it there in case anything went wrong. If i had done the reboot automatically and say, the hboot got erased but not flashed, it would brick instantly. This way, you can catch errors and then decide to reboot if all went well.
[HTC One S] touch of jobo:
If you add a file called "splash1.nb0" to the zip, it goes into p14.

So you can flash each of them separately or together.

I tried it.

-Jobo

. o O (you can also think wifi and radio)
[HTC One S] Sneakyghost:
cool thanks man. I love messing with scripts. But tomorrow... :D
[HTC One S] LibertyMonger:
My new phone is on it's way set to receive it on Monday! Very happy I had the insurance, turns out I don't have to pay a penny. And I have my HTC One S all fixed up and ready for her with this bootsplash...
[HTC One S] LibertyMonger:
Does anyone know of the best TWRP or the most favored? 2.4.2 has been working for me but still seems a little buggy
[HTC One S] Darknites:
Re: [HOW-TO] Change your Boot Splash + Flashable ZIPs + Online Generator + Warning Go

2.3.3.0
[HTC One S] LibertyMonger:
Yeah thats what I thought, that is why I left hers on 2.3.3.0 but it didn't work out very well lol. I doubt it was it's fault but I am skeptical of it now! Lmao
[HTC One S] Darknites:
Re: [HOW-TO] Change your Boot Splash + Flashable ZIPs + Online Generator + Warning Go

It's the one I used but did keep the same hboot so not sure if that helped but doubt it.
[HTC One S] LibertyMonger:
Hey Darknites, do you know how I can make this bootanimation.zip work with our HTC? It's a flashable zip for my nexus, Hot pink Baked version
[HTC One S] Darknites:
Re: [HOW-TO] Change your Boot Splash + Flashable ZIPs + Online Generator + Warning Go

What's up with it? It need resizing but should still work if named right.

Edit, it's not a flashable zip but animation zip.
[HTC One S] Sneakyghost:
AW: [HOW-TO] Change your Boot Splash + Flashable ZIPs + Online Generator + Warning Go

As Tec pointed out, it's not necessarily bound to that recovery. The process of writing to the chip is dangerous in recovery, it is somehow prone to inaccuracy and thus it can happen on every recovery. We just thought it might be caused by one of the buggy versions originally but it's not that.

Sent from Viper 2.2
[HTC One S] LibertyMonger:
Well HTC bootanimations are located differently, nexus it is in system/media. So I'm not sure if flashing this would work
[HTC One S] Darknites:
Re: [HOW-TO] Change your Boot Splash + Flashable ZIPs + Online Generator + Warning Go

See edit, what rom are you using.
[HTC One S] Sneakyghost:
AW: [HOW-TO] Change your Boot Splash + Flashable ZIPs + Online Generator + Warning Go

Go to /system/customize/resources with a root explorer and check the naming of the boot animations in there. Then rename yours the same way and copy and replace it in that path.

Easier: put it on your SD card and use venom tweaks app to enable it. That works only on viper of course ;)

Sent from Viper 2.2
[HTC One S] LibertyMonger:
Lol. Well it is the Baked bootanimation so just to be a smartass, you tell me? Lmao JK buddy, I'm running your ROM
[HTC One S] Darknites:
Re: [HOW-TO] Change your Boot Splash + Flashable ZIPs + Online Generator + Warning Go

Lol then it should be the same but remember it's not flashable so you need to do it manually or reuse another zip to flash it.
[HTC One S] LibertyMonger:
Yeah Duh I should have opened the zip before asking then i would have known. I can replace it just the same as my nexus it's just a different path. Thanks Guys
[HTC One S] Darknites:
Re: [HOW-TO] Change your Boot Splash + Flashable ZIPs + Online Generator + Warning Go

It should be the same system/media
[HTC One S] LibertyMonger:
Yeah ok since it is AOSP ROM. I just confused myself and made it harder than it is. I'm not used to messing with the bootanimations and splash screens on HTC yet. I only know enough to be dangerous lmao. Anyway one more thing before I clutter this thread up too much, I need to find the older versions of TWRP but if you can link me it would be great. Thanks dude
[HTC One S] Darknites:
Re: [HOW-TO] Change your Boot Splash + Flashable ZIPs + Online Generator + Warning Go

There a link on there site for older builds on goo.
[HTC One S] cwalton4077:
Re: [HOW-TO] Change your Boot Splash + Flashable ZIPs + Online Generator + Warning Go

I have S off 1.14 hboot do I hvae to downgrade if I'm s off?
[HTC One S] touch of jobo:
No. If you're S-Off, you can flash your own custom splash regardless of hboot version.

But if you want to get rid of the red warning text, you have to flash a modded hboot. If you decide to do that, I'd suggest you take one that's fastboot flashable and that's the same version you have now.

-Jobo
[HTC One S] LibertyMonger:
So I got my replacement today, brand spankin new in a sealed box with new charger included. They always say to keep your battery and your charger cause you will need it, they always have me worried I'm gonna get some used device but they always send me a new one lol. It's too bad they don't have removable batteries anymore. Which is bull****, you know why right? So they can kick on a mic or cam or tracking to spy on or catch you if needed lol. No matter what they always have the power! That is why it is a smart phone. Pretty damn smart of them to create devices that we cannot put down and they can have complete access to your privacy whenever they want! Ha!

Anyway I am to greedy I will be back at this thread at some point, I have to start all over again. I guess go through the unlock process, flash a recovery then root, then downgrade and then s-off? Thank you guys for your support through these terrible times Lol. But having insurance like this makes it a pretty fun adventure! Haha. Now I am a little more nervous about it all though. But cannot resist the temptation! :fingers-crossed:
[HTC One S] Darknites:
Lol and no need to downgrade just S-Off.
[HTC One S] Sneakyghost:
AW: [HOW-TO] Change your Boot Splash + Flashable ZIPs + Online Generator + Warning Go

Yeah mate you didn't get a vital part there. Don't do the downgrade! It is obsolete, dangerous and stupid to try since we have a much safer S-OFF.

Sent from Viper 2.2
[HTC One S] LibertyMonger:
Is it possible to use a .gif pic for bootsplash? animated pic?
[HTC One S] touch of jobo:
No. It must be raw rgb565 format.

However, you can use a .gif file as your source to generate a flashable splash zip using the online generator. (I wouldn't recommend it, as you probably lose color depth.)

No animations tho.
[HTC One S] LibertyMonger:
I seen a pic I liked but it was animated, I didn't care for the animation, just wanted the pic lol. Thanks man
[HTC One S] LibertyMonger:
So I am itching to try flashing the no-red warning hboot again lol. Is it considered safe to flash in fastboot mode now?
[HTC One S] Sneakyghost:
AW: [HOW-TO] Change your Boot Splash + Flashable ZIPs + Online Generator + Warning Go

Nothing wrong with trying right? :D I'm sure your insurance covers experimental hboot flashing :-p

"Safe" is a pretty relative term with NAND writing. Safe would be determined by some cool means to recover from a bad write operation in my humble opinion.

Not having such renders any write to boot critical partitions a dangerous adventure...

Sent from Viper 2.2
[HTC One S] LibertyMonger:
:victory: Ha! I did it! Couldn't resist the urge and the challenge! My HTC One S is complete with total freedom! Lol. Thanks for this and thanks for the help guys. :victory:
[HTC One S] proxuser:
here is my one

http://www72.zippyshare.com/v/77536622/file.html

generate yourself ;)
[HTC One S] Phantom Pt. II:
I love the Google splash screen! Thanks.

Tempted to try to get rid of the red text.. but sounds tricky.
[HTC One S] Darknites:
Its the same as S-Off unless you do the more risky flashable zip one.
[HTC One S] touch of jobo:
The recovery flashable zips have so far produced 1 brick for unknown reasons (and 1 on an S-On device with low hboot). It's considered safer to flash in RUU mode, but slightly more work - it involves typing. :p

But since you must be S-Off, you have already modded and flashed p4 to get supercid and flashed a zip in RUU mode to get S-Off.

(Flashing p4 is actually more awkward/brave than you probably realize. The cid and imei and stuff are not stored in p4 but in p5. p4 is actually the first extended partition that points to p5 and to the next extended partition that in turn points to p6 etc.. But p4 is 2 blocks; the 1st block is an EMBR and the 2nd one overlaps with the 1st block of p5. Anyway .. I don't know why I wrote this. As you were.)

-Jobo
[HTC One S] Phantom Pt. II:
Re: [HOW-TO] Change your Boot Splash + Flashable ZIPs + Online Generator + Warning Go

Yea true I did do similar stuff to get super cid and s-off. But don't have a PC near atm. Would you really not advise the recovery flashable zips? :) I might just try that, unless I can do it via Terminal Emulator on my phone. :P

Think I have 1.14.0002
[HTC One S] Sneakyghost:
AW: [HOW-TO] Change your Boot Splash + Flashable ZIPs + Online Generator + Warning Go

It might not be as tricky as it seems after all. I had made quite a fuss about that brick back then because it seemed to be a hint towards how dangerous recovery based flashes are to that partition and Tecardo backed it up by claiming there were specific problems with NAND write operations executed from recovery which he explained to me on a technical level I couldn't quite follow. It all sounded pretty reasonable and still does to me, BUT: then again, most people made that trip safe...

Sent from Viper 2.2
[HTC One S] touch of jobo:
You can manually dd in terminal. Just extract the hboot image from the zip. But this is just as (un)safe as flashing in recovery, provided that you have a solid recovery (!!). It's nice to know that your decision depends on whether you can convince me to not advice against it. :p It's been done a lot. I've personally flashed all of them at least once and some more. But I would be negligent if I didn't mention that it did produce a brick that we can not explain.

Edit: Keep getting ninja'd by Sneaky

Edit2: I'd say that typing on a touch screen keyboard is more dangerous than just flashing in recovery
[HTC One S] Phantom Pt. II:
Re: [HOW-TO] Change your Boot Splash + Flashable ZIPs + Online Generator + Warning Go

Haha sorry. I guess I'll do it the safe way someday soon when I'm on my pc. ;) thanks
[HTC One S] Sneakyghost:
Lol man sorry on the first Edit - i just felt the urge to put some ease on the that hysteria with the recovery flashes. I felt that i maybe overreacted with that bold red warning a few pages back. Still, it is something to consider. So i hijacked your thread again. I hope you forgive me.

On your second Edit: i totally, absolutely agree. Running a dd command from within a terminal emulator with a touch keyboard is totally hazardous if one hasn't gotten the time and peace to absolutely verify each letter before sending enter to the command prompt.
[HTC One S] Phantom Pt. II:
Re: [HOW-TO] Change your Boot Splash + Flashable ZIPs + Online Generator + Warning Go

Flashed in recovery and survived. Wuhu. Thanks a lot for this.
[HTC One S] ehsanuetian:
these flashable zips are for model PJ4010000. ia m getting error and hboot is not being downgraded. i have PJ4011000, can i just flash the nbo file in recovery. or plz tell me how to make zip for modded hboot 1.06 for my model. i am s-off and cid is htc__001
[HTC One S] touch of jobo:
The zips form post #274 are for PJ4010000, yes. You can edit the model number in the android-info.txt file. (I am not going to do that for you, because I can not test it on my own device, and I don't want to post flashable zips without testing first. Especially not on such a critical part of the device.)

Flashing in RUU mode is considered safer than flashing in recovery. But many including myself have flashed in recovery without issues. It depends how much you trust your recovery.

It's possible to 'manually' dd the .nb0 file in recovery (or even while fully booted into the OS), from an adb shell:

dd if=/sdcard/hboot.nb0 of=/dev/block/mmcblk0p12

..but if you're going to do that, it is easier to use the zips from post #148

-Jobo
[HTC One S] ehsanuetian:
Thanks a lot. Just flashed hboot 1.06 from post 148, via TWRP 2.3.3, successfully.
[HTC One S] nor-ric:
Hello, I'm S-off, unlocked, and I'd like to get rid of the tampered flag and of the red warning text.

I understand I should flash "modded_hboot_1.14.0004.zip" at first.

And then I should reflash mine (which is 1.14.0002) using "orig_hboot_1.14.0002.zip" or "modded_hboot_1.14.0002.zip"? I guess the modded one, right?

But in the post above you said:

How am I supposed to check my model number? In the software information in the settings menu there's nothing similar.
[HTC One S] ryanshew:
Just try to flash it...if it don't flash, then you are the other model id. In that case, you would have to edit it so that it will flash.

And yes, you want the modded hboot zip...the original will bring your red warning text back.

HTC_One_S | S-OFF | DeviantXone | Bubba_3.7b_SoftOV
[HTC One S] nor-ric:
Thanks ryanshew!

Just one more thing: does flashing a RUU get rid of tampered and red warning? If that's the case I would just wait the time that I need to flash a RUU and avoid this procedure. Or is this procedure needed in any case?
[HTC One S] ryanshew:
I've never flashed a RUU, so I don't know, but I believe you have to do it this way here..I have flashed a number of the modded hboots in recovery just to see differences between them (which is nothing noticeable by the way). But I do have both the red writing gone and the tampered gone.

Apparently, flashing it in fastboot is supposed to be safer. Just read through the thread for more info...there are links to this info in the OP.

HTC_One_S | S-OFF | 1.06_Hboot | 1.13_Radio | DeviantXone | Komodo_Ville_1.7GHz_[4-6-13]
[HTC One S] nor-ric:
I'm trying to fastboot flash the zip but I fail:

I suppose I have to edit something...

Edit: the content of the android-info.txt is the following:

I think:

1) I have cid HTC__405

2) mainver in the file is 3.16.401.8, while I'm still on 4.0.4 rom (mainver 2.31.401.5)

3) hboot preupdate is 1, while I come from 1.14.000.2.

Don't know about the other values.

I guess the modelid is correct, since the cmd output stopped me on the customer-id check. Am I safe editing the android-info.txt with notepad++ and changing HTC__001 with my HTC__405? Anything else about that hbootpreupdate and 3.16.401.8 mainver?

Thanks
[HTC One S] rootrider:
Flashing 1.14.0004 will do that. In case it doesn't, flash a lower hboot first (e.g. 1.06) and then 'upgrade' to1.14.0004.

Any RUU will restore the original bootloader and with it the red warning text. But once you removed 'tampered' it will not come back. At least it didn't here.
[HTC One S] nor-ric:
I'm trying to flash the bootloader, but it doesn't work for me. I have posted the output in my previous post.
[HTC One S] ryanshew:
Yes, you can do that, or since you are s-off, just change your cid...probably easier. I think I did this with super cid.

HTC_One_S | S-OFF | 1.06_Hboot | 1.13_Radio | DeviantXone | Komodo[02-13]
[HTC One S] touch of jobo:
It seems to be CID mismatch.

I thought that CID would not matter when you're S-Off, but apparently it does.

Did you change your CID back after you got S-Off? You can change the CID in the zip file or change the CID on your device. I'm pretty sure (but maybe someone can confirm) that people have RUU-flashed these on SuperCID. Personally, I changed my CID to HTC__001 after S-Off. On S-Off it's really easy to change the CID using fastboot oem writecid.
[HTC One S] ryanshew:
Make sure you follow the directions I quoted here if you are not going to just flash in recovery.

you must first "fastboot oem rebootRUU"

Then you can "fastboot flash zip"

HTC_One_S | S-OFF | 1.06_Hboot | 1.13_Radio | DeviantXone | Komodo[02-13]
[HTC One S] nor-ric:
I went to superCID and fastboot flash the zip. It worked! Took me a heartache because the green progress bar in ruu-mode was stuck at 3/4 and didn't go on... The command prompt said everything was ok though. I rebooted and it was working... Fiuuuuuu...
[HTC One S] ehsanuetian:
If you are s-off, unlocked, have twrp recovery 2.3.3.0, you can easily flash any hboot from post 148, in recovery. They are modded and will remove red warning.
[HTC One S] ryanshew:
He's aware of that, he's just trying to do it the "safer" way.

HTC_One_S | S-OFF | DeviantXone | Bubba_3.7b_SoftOV
[HTC One S] cicciocant:
SEMI OT

It's possibile to repack supersu.zip to to be fastboot flashable in RUU mode?

This for root devices witouth unlock bootloader and flash modified recovery.
[HTC One S] Sneakyghost:
I think technically it is as we can see from the OTA.zip's, which can also replace, remove and add stuff to system, but you'd need to ask someone to script that for you, as the script used here flashes a full partition only.

mobile post
[HTC One S] rootrider:
It has already been done here.

Sorry for OT gentlemen.

--- edit

oops, not for locked phones I think. Well, locked is locked.
[HTC One S] rootrider:
My personal favourite. Thanks to James White for 'la femme'.
[HTC One S] touch of jobo:
On a locked bootloader you can only flash stuff that's signed with HTC private keys. We can't do that.

-Jobo
[HTC One S] proxuser:
a new one black htc and speakers of htc one, hard to see them, they are up and down side

download (flashable zip)

http://www21.zippyshare.com/v/60077834/file.html

psd here

http://www18.zippyshare.com/v/17120581/file.html

enjoy
[HTC One S] -droidberg-:
Thanks

It looks great! Thanks, i'm using the bakck htc logo one, and red watermark is gone
[HTC One S] essentialmindz:
simple black and white laughing man...
[HTC One S] touch of jobo:
I bet that one looks nice inverted. White on black.
[HTC One S] essentialmindz:
i lost the files in a format, but i did make this one as well:

EDIT: Here, also inverted the other one:
[HTC One S] Evil-Monkey:
Hello

couple of pics re-sized ready for your edits.

Cheers!
[HTC One S] Sneakyghost:
RUUmode hboot flasher script

Edited my RUU-Mode hboot flashing script with latest hboots and stuff for your convenience, dear flashaholics. Go ahead changing your hboots back and forth in RUU mode. Contains all hboots listed by Touch Of Jobo earlier on in this thread.

Download: Post #280

Contains all hboots listed in Post #274

Changes: just corrected an Error in the script i found today and inserted a confirm page at launch time so users are not trying to flash hboots on S-ON devices (if they can read, this should suffice as safety).

[EDIT]

The Hboot files all contain HTC__001 in the Android-info.txt file. I just had one user who could not flash them on his HTC__102 device.

If you happen to get error 42 wrong customer ID and get stuck in RUU Mode, please just run this command in CMD: "fastboot oem writecid HTC__001" and then repeat the hboot flash. It will be good then. Avoid rebooting the phone, just leave it stuck where it is and do the writecid command, then repeat the hboot flash. I updated the script so that option 16 opens a command prompt for you in the right place.

Also i forgot to point out this: the flasher script does NOT reboot the phone when its finished to give u a chance to see if everything worked good. You have to pick option 14 (reboot to bootloader) or 15 (reboot to system) afterwards to reboot. The green progress-bar on the phone will stop at about 3/4 of the way. That is normal! It only moves on when you do the reboot command!

It basically is to hold it there in case anything went wrong. If i had done the reboot automatically and say, the hboot got erased but not flashed, it would brick instantly. This way, you can catch errors and then decide to reboot if all went well.
[HTC One S] Sneakyghost:
Interesting log. Where did you get that? Or how? The "failed" is a status that is not referring to the actual update process, I have seen that a couple of times on other fastboot command logs. It's referring to the print out (status read failed - too many links). Replace "links" with "lines" and it sounds more familiar :D

So you actually didn't get to see the end of your log...

The part which indicates that your hboot flashed correct is at the top. Look where it says status finished and then "OKAY".

the following log shows how the hboot tries to determine the hardware components and partitions on the chip and then jump to the kernel, which might have failed.

I'd suggest you do "fastboot reboot" and not boot as that is doing something that had also been used by the exploit to gain s-off (booting out of RUU mode) and since I'm not really sure what that boot sequence does I would advise not to use it. Maybe touch of jobo can elaborate on this. Surely, he knows.

If the reboot out of RUU mode also doesn't let the phone boot, do fastboot erase cache. If that doesn't help either, reflash your kernel.

The hboot of your phone is ok. Nothing wrong there according to your log.

Mobile Post
[HTC One S] Bigdrago:
Thanks.

When the install bar for HBOOT showed 75% It wouldn't move anymore.. So I did fastboot oem boot

Seems like everything here is correct now. Installed the HBOOT and the newest RUU (3.16), changed CID to my default (norwegian) and did S-On.

Howto reflash kernel, and where do I get it?