yashsingh1/xdaforums huggingface dataset:
[HTC One S] touch of jobo:
Looks like the image was flashed correctly.

You can fastboot reboot-bootloader to boot into it.

-Jobo

Edit to add: (because I didn't see your later post earlier)

If you ran a RUU, then that has flashed everything: hboot, recovery, boot image/kernel, system image..

What are you trying to do?

-Jobo
[HTC One S] Sneakyghost:
He's just a bit lost and needs orientation I suppose :D

I wonder why he went back S-ON though...

Mobile Post
[HTC One S] Bigdrago:
I'm selling the phone and want everything to be stock :)
[HTC One S] cat2115:
Not if it's just me or i did something.

I ran T-mobile JB RUU, then reset phine + erase everything. I flash twrp 2.3.3.0. Then, fastboot oem rebootRUU, then fastboot flash zip modded_hboot_2.15.0000.zip

Everything went good but at the end, it said Error or Fail cuz of CID error or mismatch (i forgot) but It something to do with CID that it won't flash the custom Hboot.

Mine is CID-T0MOB010
[HTC One S] samco08:
hello thank for your works...

but i have a problem.

I'm trying to downgraged my Hboot from 2.15 to 1.06 to unsimlock my phone.

I'm S-off

I hade not problem to uprgrade.

but for downgrade the terminal say me:

C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot devices

SH24LW405590 fastboot

C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem rebootRUU

...

(bootloader) Start Verify: 0

OKAY [ 0.068s]

finished. total time: 0.075s

C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip mod

ded_hboot_1.14.0004.zip

sending 'zip' (373 KB)...

OKAY [ 0.231s]

writing 'zip'...

(bootloader) zip header checking...

(bootloader) zip info parsing...

(bootloader) checking model ID...

(bootloader) checking custom ID...

FAILED (remote: 42 custom id check fail)

finished. total time: 1.931s

C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot reboot-bootlo

ader

rebooting into bootloader...

OKAY [ 0.066s]

finished. total time: 0.071s

I tryed with two different CID

ORANG202 and HTC__203

but nothing work......:(

It's possible to downgrade when we are S_off ?

*********************************************************

I'm trying with CID 11111111

but now the phone is freezing with the green bar not complet !!!!

what I have to do ?

unplug my phone ?

HELP ME !!!!

*****************************************************

fastboot reboot-bootloader

it work good !!

byby "TAMPERED"
[HTC One S] touch of jobo:
It's not you, it's me.

I made those zip's for HTC__001. They also work on SuperCID. Since you have to be S-Off anyway, I figured most people would be either of those.

So you'll have to change your CID (using writecid now that youre S-Off) or flash in recovery.

Yes, same issue. You need HTC__001 or SuperCID.

It is normal that the progress bar doesn't complete to 100%, but as long as it reports 'OKAY', the flashing was finished and you can reboot into your new bootloader.

-Jobo
[HTC One S] jelbo:
/edit: wrong thread
[HTC One S] rufh_s:
Sorry for the change of track from the topic but needed some help from experts (posted things in Q & A but no comments as yet )

Though this is an S-Off Issue but have been going through the posts here and found posts on partitions.

As the Issue started only after I attempted Updating Security Partitions via softbin3 I feel somthing messd up (again) the partitions

So is there a way I can rest the partitions OR go back to S-On by some how un doing EVERY thing OR any Other solution

(Tried RUU ,Nandroids etc which has not effects on security partitions,can access bootloader and Recovery)

My earlier attempt to S-Off had the same issue,Jtag solved it

Any help appreciated

Regards
[HTC One S] touch of jobo:
I now have two different versions of the online flashable zip generator up. The original one is still up and I also added a new one for the One-M7. (The difference is that the One is 1080x1920 -> P13 instead of 540x960 -> P14.)

Since there are now two different versions, I adapted the php scripts a bit:

The (original) version for the

One-S

returns a .zip named "

bootsplash-ville.zip

" and the new version for the

One

returns a .zip named "

bootsplash-m7.zip

". Nothing else changed, except the name of the .zip file you get.

(It used to be named just "bootsplash.zip", but I'd hate to see people flash the wrong version on the wrong device and end up with a brick.)

-Jobo
[HTC One S] ATSPerson:
Exactly my problem. discussion here - don' get your hopes up. No answers yet.
[HTC One S] syntropic:
question re annoying text

I just flashed a self-created splash image, and then dd/if'd from my phone in a root shell to the correct partition.

It worked, but I have two questions...

1. The silly red text is there.... I just upgraded to a new hboot for the new kernel (I believe it is 2.15) and I have s=off obviously. What do I need to do to get rid of this?

skip the next one... I was getting banding in my image.... when this happens, you need to go into the channels that are problematic (where you can see the banding), and add noise.... just a tiny bit... I used .22

2, My splash as I created it contained a gradient. It wasn't the most artfully created gradient (I was blending two images together), but it looked fine in Pshop. However, when I see the splash screen on boot, it has that annoying banding through the gradient. Does any one know tricks to get rid of this???

Here is the splash screen made.....
[HTC One S] Darknites:
http://xdaforums.com/showpost.php?p=38387544&postcount=148
[HTC One S] touch of jobo:
You don't have to manually convert and dd, you can use the online thing from post #115.

You can flash a modified hboot to get rid of the red text if you are s-off. See link Darknites posted.(You MUST go back to stock hboot before going back to s-on or you WILL brick.)

You photoshop image is (most likely) 24 bit, 8 bit per component, 256 levels. The splash is 16 bit, 5 bits for red and blue and 6 for green. Thats only 32 or 64 distinct levels per component. Hence the banding.

-Jobo

Edit to add: Your picture doesnt show up for me.
[HTC One S] Darknites:
Thanks for the colour info. To get picture right click it and open link in new tab.
[HTC One S] sausje85:
Getting this error on HBOOT 1.06.0000, i'm S-OFF and *** UNLOCKED *** & ***TAMPERED ***

C:\ADB>fastboot flash zip modded_hboot_1.06.0000.zip
sending 'zip' (397 KB)...
OKAY [ 0.221s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 0.255s

Usually this means that my bootloader is locked again.

But since i S-OFF my phone, i didn't touch the loader anymore or anything other then installing new roms/kernels.

Plus the text clearly says that i'm unlocked.. So what could be wrong here?
[HTC One S] touch of jobo:
Did you boot into RUU mode before flashing?

-Jobo
[HTC One S] sausje85:
Oh ffs, i knew something went wrong. So stupid of me, always missing the little things :(

Sorry for wasting your time!
[HTC One S] cuiltheory:
Thank you for the bootloader. I got my own splash boot and bootanimation. I am on 2.15 with s=off. It was easy. Thanks again.
[HTC One S] katak.bali:
sorry for off topic, I'm nubie htc user..

what is hboot? what the different all of them?

thanks :)
[HTC One S] foeti:
Wrong thread. Use search function. There's enough information out there yet....

Gesendet von meinem One S mit Tapatalk 2
[HTC One S] katak.bali:
I'm not ask if I found the answer
[HTC One S] touch of jobo:
hboot is the bootloader.

The hboots I posted in this thread were modified to remove the red warning text overlaid on the boot splash. I also posted the originals so that people can revert.

I don't know of any functional difference between hboot versions, except that generally higher version number means more restrictions. (Edit: except that you have to be s-off to flash a modded hboot, so then thsoe restrictions don't apply anyway.)

-Jobo
[HTC One S] katak.bali:
thanks for your answer bro.

I just confused everybody using different hboot, not the latest one (2.15.000)

and again thanks for your work, I'm using your modded hboot :)
[HTC One S] iElvis:
The online tool is pure awesomeness. But it seems to be down today?
[HTC One S] touch of jobo:
Yes, sorry. I'm having trouble with my internet/ISP lately. (flashing lights on the modem)

Edit: It's online now. Fingers crossed.
[HTC One S] qzem:
[MENTION=1293920]touch of jobo[/MENTION]

Now that HTC One S C2 has S-OFF, would you be se nice and make some of those spalsh screen for us? I could provide partition layout...
[HTC One S] touch of jobo:
If I know the partition number, I can clone and adapt my online generator. Like I did for the One, except in this case the resolution is the same.

I need you to test it for me before I make it public tho. (I would do it myself but I don't own a C2.)
[HTC One S] Sneakyghost:
Wow nice c2 got S-OFF?

Shouldn't it have the identical layout?

mobile post
[HTC One S] touch of jobo:
I would guess so, but my guess is not good enough. (Would you take the gamble?)

Someone who owns the device (like maybe qzem) should confirm it. (By extracting the partition and looking at the data, not by trying to flash a ville splash zip and see what happens.)

-Jobo

Edit: The way to go at that is..

* Boot into recovery, get an adb shell.

* Mount your sdcard partition: mount /sdcard

* Extract p14: dd if=/dev/block/mmcblk0p14 of=/sdcard/p14.img

* Pull the image to your PC: adb pull /sdcard/p14.img

Inside a RUU or OTA, you can find a file named splash1.nb0

The first 1036800 (0xFD200) bytes of your p14.img and this file should be the same. They consist mostly of 0x9D 0xF7 0x9D 0xF7 etc.. (Thats the white background.) If they match, then p14 is your boot splash partition.
[HTC One S] Orical:
The red text is because of the boot image being altered, if it were stock it wouldn't be there. Unfortunately I can't take a screen shot to show you for obvious reasons. I'm still using the image originally posted its pretty cool.

On another note I can't get the splashes to convert to image yet for some reason I can't get it to work, a quick tut would be cool if anyone is interested in posting one up.
[HTC One S] ragnarokmk2:
I have the stock European Vodafone rom, unlocked and rooted, haven't done much modifications, so I guess I have the signed boot image?

Red "build only for dev..." text does not appear...

---------- Post added at 06:53 PM ---------- Previous post was at 06:50 PM ----------

Didn't really get that. Do you need help converting an image to the right raw rgb565 format, or the other way around? Either way I could make a quick tutorial on how to do that, just post which of the two cases should be covered.
[HTC One S] Darknites:
I know about the red text. I put it there because touch of jobo asked ragnarokmk2 about it so I thought it be best to say. Its it a shame the zip don't work for me because I don't get how to do it the manual way :(.
[HTC One S] Orical:
I posted the manual way a few posts ago if you extract the zip and flash just the image it will work.

If you can make a tut on turning a jpeg into a flashable image (raw565) that would be awesome, I used a tool before I never learned how to do it any other way.
[HTC One S] ragnarokmk2:
Converting an image to rgb565 without Linux.

Required tools:

Photoshop or similar for Image cropping.

Paint.NET Image Software (sadly I couldn't get it to work with a Photoshop RAW, so another program must be used, but it's small in size). Download from here: LINK

Rgb565 Plugin. Download from here:Link. After download, extract ALL files and put in \*PaintNET install directory*\FileTypes

Image Preparation

The Image you have to convert to rgb565 must first be in the right resolution. For the HTC One S this is 540x960 If you already have such an image, you can skip to the next part.

1: Open your image with Photoshop (PS).

2: In PS press Ctrl+Alt+I and in the new window to change the height of the image to 960 pixels while maintaining the aspect ratio/constraining proportions.

OPTIONAL: In the rare cases where the resulting image has a width less than 540px, you'll need to use the image resizing tool (Ctrl+Alt+I) again, remove the checkmark at "constrain proportions" and stretch the width of the image to 540. The resulting image would have the right dimensions, but it would look distorted, so it's better to find an image in another aspect ratio.

3: Now that your image is the right height, you must use the Crop tool (press C) and cut out the excess width. Do a rough crop, trying to keep the part of the image you want to have as your splash in the centre of the crop tool.

4: Now it gets a bit tricky. In order to get the precise 540px width, you have to be rather experimental with further crops. Enabling the Grid and the ruler in PS (Ctrl+' and Ctrl+R or View->Show->Grid; View->Rulers) helps immensely. After you have both activated, right click on the top ruler and chose "Pixels"

5: Crop until you get the right width. Note that if you crop from left to right, the 540 mark is aligned with a border on the grid, so just try to match that. You can keep checking the size of your image with Ctrl+Alt+I. If you get it within 5pixels or so, you can also just use that tool to manually set the width to 540px (Remember to uncheck "constrain proportions" first!). Since there are only a few pixels to adjust, the image shouldn't distort too much.

Now that you have your image in the right resolution save it as a Jpeg/BMP/PNG file. Doesn't really matter, since we'll be changing it's format anyway.

Converting to Raw rgb565

1: Open the image in Paint.NET

2: Choose Save as and select "rgb565 Bitmap" as a file type

3: You're basically done. To get it in the correct format for flashing with the zip files from this thread, just rename the file to "splash.565" and put it in the /cache/ folder in the zip.

I know this is a bit of a workaround, but I haven't been able to find a more n00b friendly way of doing it. Hope this helps.
[HTC One S] Orical:
No man that's great, makes total sense and worked awesome. I had everything set up already but didn't see the (.dll) file I had to add to get this to work right. Thanks again for the time it's really easy to understand now time to apply what I have and see what I can put out.

Thanks for pointing out the pixel adjustment too I know in PS it's easy to set properly but this one I'm trying out is almost like Gimp but it has some simple layouts, if I can't get this to do what I want I'll go back to PS and re do my templates and styles, gradients packs etc.

I just wanted to test one out first before doing anything serious but it came out pretty good. This is a splash screen so follow the directions I posted on (page 2) unless some one wants to make it a zip file

https://www.dropbox.com/s/2clfn1rk7mqaq33/540x960 Aktion S.rgb565 I suggest changing the name to (custom.img) prior to DD-ing it. Came out great it's really clear.
[HTC One S] Darknites:
Oh nice one I give that a try.
[HTC One S] touch of jobo:
It would be weird if The Manual Way works and the flashable .zip doesn't, as it does the same thing. But please let us know if this is the case.

I asked about the custom boot image / red text in order to find out why it would work for some but not others, but it now seems that this is not the deciding factor.

The flashable .zip may depend on recovery? But if manually dd-ing doesn't work for some, it means that we're not all equally unlocked. It might be the difference between branded vs. unbranded devices. (I'm unbranded HTC__E11, on CWM5831 and VirtuousV06)

It'd be interesting to know from some people who try this, which methods work, which recovery and boot image they use, and whether they are carrier branded.

@ragnarokmk2: If you dd it manually, does it indicate success? And if you then extract that partition, do you get out what you put in, or the stock splash?
[HTC One S] kaeruil:
Well I tried the flashable zip which didn't work, but it worked fine the manual way. In case it matters my phone is a branded T-Mobile US and I'm using TWRP as my recovery.

Sent from my One S running Axiom S-less
[HTC One S] Orical:
Personally I don't know what the difference is between the two but if the partition is the same (0p14) then it should work either way but I've always found the manual method to be better, I like to know where I'm sending files and learning more about what I'm doing.

Manually should work no matter what, also this is better if you follow the instructions in reflashing your back-up just in case you ever have to bring it in for service. The full backup will restore the phone back to the state it was in when you first ran it. Good for people that are having problems and can't figure out what they messed up when flashing a new Rom doesn't work.

The other thing is I had to wait for someone to post up the partition the splash was at flashing a splash to the wrong partition can brick your device, there has to be a way to know which one it is for your device if its not the same.
[HTC One S] touch of jobo:
The problem with this Full Backup is that your 'sd card' is part of the emmc. It is mmcblk0p36. The 16G image will not fit on the 10G partition.

I found out after I dumped all partitions and was looking at their contents.

This one turned out to be the white 'quietly brilliant' splash. I was happily surprised to find it writable.

-Jobo
[HTC One S] Darknites:
I just tried your way and it didn't work for me. I am right in thinking that I rename the splash.565 out of the zip to custom.img.
[HTC One S] Orical:
Yes and writing it out that way too dd custom not 565. If you follow the steps from after back up it should work unless there's something wrong with the splash, I change the name on my phone by the way I don't do that on the computer.

@ jobo I backed it up and it fit on mine, try it I'm pretty sure it doesn't do the sdcard because mine was only 6gbs then I transfered it to the computer so I can adb it if anything goes wrong. HTC did do us right by unlocking most of it for us to play with, they only consider the hboot to be secured and for good reason, I'm not talking down about people by saying this but it takes time and effort to be good at understanding the software so this is their way of making sure the user doesn't ruin their devices.
[HTC One S] Darknites:
Then i'm lost to why this don't work for me, could it be the same reason I can't flash boot.img? never has worked for me too.
[HTC One S] Orical:
What version of the phone do you have? Is it a US based device or something else. The only thing I can think of is it may be different in some way.
[HTC One S] Darknites:
I got it from o2 in the uk and is the S4. The backup file was 6mb if that means anything.
[HTC One S] Orical:
Yeah man that's the same, not sure what's causing it I'll see if I can find any info on it.
[HTC One S] touch of jobo:
The backup is 6M because that's how big the partition is.

If you cat /proc/partitions you get a list of all emmc partitions and their sizes in 1k blocks. mmcblk0p14 is 6114k.

Which HBOOT are you guys on? I'm on 1.06 but if you've run an RUU or OTA yo may have newer one.

-Jobo
[HTC One S] Darknites:
Thanks for helping guys. I will try another the image, one from the OP and see if that one works, was trying the google one but that will have to wait in till later. I have 1.13 HBOOT which by the looks of things could be stopping me flashing boot.img and what do you mean by this part "cat /proc/partitions"? I did run this RUU "RUU_Ville_U_O2_UK_1.78.206.4_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258707_signed" when it come out.
[HTC One S] Orical:
I'm not sure, I'm on 1.09.000 and I haven't had a problem, the one things I can think

of and I did the same thing when I first started using the manual method and it drove

me crazy was the spaces in between each section of the command, so it goes

dd {space} if=/blahblahblah {space} of=/restofthecommand

I almost always forgot to add the space either between "dd" and "if" or "custom.img" and "of"

everything else should have no spaces between them, some look like they have a

space in the text but those are the only two places, it has to be exact for it to work.
[HTC One S] qzem:
Here you go the partition layout for one S C2.

https://docs.google.com/file/d/0B0nqGhX6QdTbeGNKUXNxOXBxU3M/edit?usp=docslist_api
[HTC One S] Sneakyghost:
You need to change file permissions. People can't see it if not shared directly with their email. You can set it to public read only.

mobile post
[HTC One S] qzem:
It should be visible now.
[HTC One S] Sneakyghost:
Well splash is not in there but it also never was in cat /proc/emmc.

Only way to determine that will be to dump the partitions like jobo said and look at them with a hex editor. Try P14 first. You'll recognize the image data right away as it will show you one long sequence of identical data with a few alterations in the middle (which is the black text :D )

If it's not that partition try any of those that are not in the list.

There are 36 partitions in total. It won't be 4, 3 or 6 most likely and also likely not 1, 2, 3.

Those try only if you tried every other partition.

There's also partition lists from the Ville in this forum which you can use to compare. Thread was done by AKToronto and I posted the lists in there. Go check them out. You'll also see the Ville Plus partition table there. It's identical. I can imagine the VilleC2 being largely the same too.

mobile post
[HTC One S] touch of jobo:
It is NOT the same as on the Ville. Do NOT flash Ville zips on a C2 until someone confirms the splash partition.

It's been confirmed that the splash image is in the same partition on the C2.

-Jobo
[HTC One S] Sneakyghost:
A little nervous? :D

I was only meaning he can use the other tables to compare and learn and I was also saying "I can imagine". That's not stating a fact, that is making an assumption.

I hope he understood that.

mobile post
[HTC One S] qzem:
I will try to provide the right data this evening or tomorrow morning. Thanks for all the info :)
[HTC One S] qzem:
[MENTION=1293920]touch of jobo[/MENTION]

Hey man, I have compared the images you have suggested and they look the same to me. I have uploade it in rar package for you to check it. Do you need anything else to be more sure? When you'll have something ready I can test it.

Cheers

DOWNLOAD
[HTC One S] touch of jobo:
It was in reply to the doc qzem published, not to your post. (But yes, it makes me nervous that I can't test for myself. Also I want to prevent posts like "..ok so I tried the zip, now my phone doesn't boot up, what do I do next?")

Yes, that is the boot splash, alright.

If

that came out of your mmcblk0p14,

then it's safe

to flash boot splash zips generated for the ville.

Let us know if it works out. It most likely will. I will then update that web page to include "..or C2". Either way, p14 is safe to poke into.

-Jobo

Oh .. and congratulations with S-Off to you C2 people.
[HTC One S] qzem:
It is mmcblk0p14, since I have copied your command :). Well that is great news, will try it later today, and see what happens :D.
[HTC One S] arnaldus:
Finally, I hate HTC Boot Splash :D
[HTC One S] mvladimir199:
Greetings!

Please tell me whether you can make the Boot Splash for HTC One S (s3)(s-off,supercid, hboot 3.01.4444)
[HTC One S] touch of jobo:
Since the resolution (qHD) and partition (p14) are the same between the S3 and S4 Ville, the recovery-flashable boot splash zip files in this thread, or generated with the online tool, should work on both.

However, I have no confirmation on this yet and I can not test myself.

(This only goes for splash zips, not for hboot zips. Don't flash an S4 hboot on an S3 device, please.)

-Jobo

Edit to add:

If the zip doesnt work, then please try dd'ing it manually:

* Extract the splash.565 file from the zip.

* Push it to your phone (make sure sdcard is mounted) : adb push splash.565 /sdcard/

* Then, in an adb shell: dd if=/sdcard/splash.565 of=/dev/block/mmcblk0p14
[HTC One S] ryanshew:
I'm trying to use the generator , but the zip keeps coming out corrupted. Does it need to be a certain forms or is the tool just down atm?

For this here:

***Edit: nevermind, Firefox worked:

http://db.tt/Ujj1JZlQ

hTConeS | SoFF | DarKSeNsE | BuLLetprOOf

Dark Sense 5 Theme+Mods_Click Me

Inverted Sense 4+_Click Me