yashsingh1/xdaforums huggingface dataset:
[HTC One S] arjundas86:
Okay. It seems that the best path forward for me is to S-OFF using the Firewater tool (since my device is HTCDEV unlocked/rooted, and having S-OFF means I won't need to unlock bootloader again after running RUU).

Then I'll run the newest Rogers RUU from AndroidRUU.

At this point, I should be on hboot 2.15 and still bootloader unlocked, right?

If I'm right about all that, then I should just have to install a custom recovery and be able to flash the 4.4 ROM I want. Correct?
[HTC One S] LS.xD:
Newest Rogers RUU ist HBoot 1.84 as it seems. Once you're S-OFF and have superCID you need to change your CID to unbranded (HTC__001) and flash e.g. unbranded RUU with HBoot 2.15.
[HTC One S] arjundas86:
Hmm... I see. Things are getting clearer, but still a little confused about SuperCID stuff.

Will running Tmobile US RUU work? That's the one from the guide I read in my first post. He suggests that RUU to get hboot 2.15.

Once I get S-OFF, then I should get SuperCID. I thought with SuperCID (i.e. 11111111), I can run any RUU. Or should I still manually set CID to HTC__001 before running Tmobile US RUU?
[HTC One S] LS.xD:
To run a RUU NOT MATCHING your stock CID you need S-OFF // SuperCID. You cant install TMobile RUU at first :/

I would act like this:

Run latest Rogers RUU --> READ FACEPALM GUIDE CAREFULLY. There is how to gain SuperCID and then S-OFF. Once done you can change CID to whatever you want and run a (unbranded) RUU with HBoot 2.15.

But that is just what i thought about it. I suggest to let someone else CONFIRM the way suggested by me first.
[HTC One S] Rapier:
Have you tried anything yet? If NO. then STOP. Don't do anything and don't upgrade your firmware/hboot yet. It could happen you won't need this. I am on hboot 1.06 and I'm running fine any ROM including KitKat ones. That requirement for a higher firmware is coming from an old issue that was before with earlier Android versions (from the versions that used 3.4.x kernel and up), making SOME phones to misbehave (reboots or other issues). It could be that your phone handles it right and in that case you won't need to upgrade if you don't want to.

WHY? You should not only upgrade your firmware but also to S-Off. It is not required but it makes your life easier. And these procedures bear some risks even if they were successful for others. And why should you risk anything unless it's mandatory? The point is you have a hboot lower than 1.09. There are not to many left and people are tempted to forget, but hboot lower than 1.09 means you're like an S-Off. You can flash radios and kernels from recovery as on any other S-Off device. Only thing you can't do is to remove those red letters from the boot splash screen...that is you can't flash another firmware. But hopefully you might not need it.

OK. All these being said, I would suggest you to first try to see if the ROM works OK on your phone like it is and only if it doesn't you should think about S-Off, upgrading firmware and things like this.

Now, what you have to do is download the ROM you would like...any ROM, and before flashing it follow my guide HERE to change the updater script in the ROM's ZIP to allow flashing the ROM on lower hboots. It is very easy, I do this usually in 1 min, I would suggest to use method 2 that's much easier than to follow all detailed steps in method 1. If you have any questions or unclear things ask but I think it's easy enough.

If after this you cannot boot the ROM or have it working, then you can think of upgrading firmware
[HTC One S] LS.xD:
[MENTION=1045770]Rapier[/MENTION]

thank you for the provided help as usual :)

Are there any advantages by unsing HBoot 1.06?? I'm on 2.15 // S-OFF // SuperCID // No red letters // "tampered" removed
[HTC One S] Rapier:
For you? NO. You're better than me :)

The story is like this. I bought the phone in 2012. At that time, the highest hboot was 1.14 I believe (don't remember exactly) and there was no S-Off method available (they appeared later). There was something else tho. The lower hboots (1.09 and lower) permitted to write in the kernel partition or radio partition like an S-Off device. HTC then covered this in the higher hboots. So even if there was no S-Off method, there was a downgrade method that was used to downgrade the hboot from whatever you had to 1.09 or below. I downgraded mine to 1.06...don't ask why I didn't choose 1.09, I thought that was the RUU I considered to be fine for me at that time.

Now being on hboot 1.06 I can do anything except I cannot flash firmwares directly. So I cannot flash a new hboot with red letters removed for example. But I don't care about this...I can flash radios or kernels or splash screens like any S-Off user. The procedure for getting latest firmware and S-Off seems a little bit risky and I've read about alot of issues or problems from people who failed or tried countless times to reach that. So I've asked myself why should I do that if I don't need it?

Then it came the rumor and there were some brick cases of devices that were having some Android 4.3 ROMs and were not on latest firmware (in the meantime 2.13 and 2.15 hboots arise and also the S-Off method). It proved to be not the firmware fault after all. But CM team has included a check in the updater script of the ROM ZIP, to validate if the hboot was 2.13 or 2.15...if not, the flash won't happen. It's a simple assert command present there at the beginning of the script that do the check. As CM team was the pioneer in having the newest Android version ROMs available, everybody based initially their ROMs/builds on CM...so the check in the script was automatically carried over to all the ROMs out there. And it's still here.

As I've tested and I could run fine those ROM's (by removing the check before flash), I noticed that this requirement does not apply to everyone. Some could run fine the ROMs even if they're not on the "latest" firmware.

So that's why I am on 1.06...cause I don't know why should I go through some risky procedures when I don't need to.
[HTC One S] arjundas86:
I did read in more than one thread that you MUST have hboot 2.15 to install KitKat roms. Also, on CyanogenMod website, it says:

Firmware compatibility:

CM 10.1-11.0: HBOOT 2.13.0000, 2.15.0000, 2.15.4444.​

But no, I haven't done anything yet. So first of all, I'll make a nandroid backup and then just try factory reset, wipe cache/dalvik, and flash a CM 11 ROM, and see if it works. I'll post here whether it worked or not, I won't have time to do this until the weekend though.

Thanks, btw.

I don't get what you're saying. It is still worth getting S-OFF, or it is not?
[HTC One S] LS.xD:
I beg to differ answering first:

Just try if you can install your preferred rom, AFTER you edited the "updatescript" as suggested by [MENTION=1045770]Rapier[/MENTION].

IN CASE you have problems with the new rom you should get S-OFF + upgrading HBoot to 2.15+
[HTC One S] arjundas86:
Yes, you're right. That's what I meant. I will delete the updater-script lines that Rapier mentioned before trying to install CM11.

If it doesn't work, at least I can restore to my backup, without risk of bricking.

Then I can try the hboot update and s-off if required.

Thanks.
[HTC One S] Rapier:
Yes, they say so. Then I'm the living proof that this requirement is not true...sorry for that. I've explained above to LS.xD where this requirement came from. The point is that you might have the ROM working even if you're on 1.08 and in this case you won't need to upgrade if you don't want

It's depending on what you want. If you want to get rid of that red warning, to have the latest hboot and to have less trouble when flashing ROMs then yes, it worth it. If you just want to upgrade your firmware to 2.15 (to match the ROM requirements) but do not want to make the S-Off, you will have to flash the kernel separately in fastboot mode, after each ROM flash. Also you won't be able to flash a radio. That's why I said that if you are going to upgrade the firmware you should get S-Off as well

BUT, if you're NOT going to upgrade your firmware and you'll be lucky to have the ROM working, you won't need to S-Off since your current hboot is lower than 1.09 and allows you to flash radios and kernels directly from recovery.

And at this point, as you said, it worth a try like you are now and only if it's not working like this you should upgrade and do S-Off. I guess is much easier and less risky to remove 4 lines from that script and flash the ROM to see if it's working, than to go through the firmware upgrade & S-Off procedures
[HTC One S] arjundas86:
Hey Rapier,

I'm having trouble doing getting the zip signed.

I tried the zip signer you had in your guide, as well as a bunch of other zip signing programs, but none of them seem to do the job. I keep getting Error: Status 7.

Not getting bootloops or anything like that, so I was able to restore to my backup. No harm done.
[HTC One S] Rapier:
I've told you to use the second method since it's faster and doesn't require any signing. :) Do like this:

- open the ZIP with Windows Explorer and copy/extract from the ZIP the updater-script

- modify the file as in the guide

- open the ZIP with a file archiver...I use WinRAR, don't know if it works with others

- delete the updater-script from archive and drag and drop the modified updater-script over the same location in WinRAR. A window asking for confirmation to add to archive will open. Don't change anything, just press ok. The modified updater-script will be added in the same location in the zip

- you're done

Doing it like this you don't extract all the archive and you don't need signing since you're using the same archive. And it's much faster
[HTC One S] arjundas86:
Sorry, I forgot to mention in my previous post. I tried this method first, since you recommended it. But it didn't work, and that's why I tried the method with the signer. Unfortunately, all of them are giving me script errors (Status 7).

Another thing I notice is that when I open the original ROM zip file in WinRAR, there is a column to the right that says "signed by SignApk". When I try to sign the newly created zip, although the program says "successfully signed," there is nothing in the WinRAR file that says "signed by ..."
[HTC One S] Rapier:
You must do something wrong. I do this for months and it's working. Are you using winrar? The official one? I have the same and it's working. Oh... Error 7 means usually you're not saving the script properly. You should open it with notepad++ not another program. And you should just delete those lines leaving no spaces and blank lines in place. Then you should just close notepad++ by the X in the upper right corner and when asked if you want to save press yes. Don't save it in another format or choose any other saving option cause you might break it

EDIT: If you can, upload here the updater-script from the ROM you wanna flash. I'll edit it and upload it for you. Then you just have to drag&drop it in the ZIP using WinRAR

Sent from nowhere over the air..
[HTC One S] arjundas86:
Hmm... that's exactly what I'm doing. I'll try editing the script again... but yes, I've been using the official WinRAR and Notepad++ (the one from your link actually). Anyway, I'll try it again with the second method (that doesn't require signing).
[HTC One S] Rapier:
Upload the script here as well just to be sure. The original script not the one modified by you.
[HTC One S] arjundas86:
I have uploaded both the original and my modified script. I compressed them into rar files because xda website doesn't allow upload of files without extensions, and also so that I could change the names without changing the filename on the actual script.
[HTC One S] Rapier:
Attached is the script having those lines removed. Just take it out from the zip drag&drop it onto the ROM zip opened with WinRAR. Before dragging there delete the file from the zip
[HTC One S] arjundas86:
Ok I think I figured out what was going on, and it's really weird and annoying. The zip file was not being copied to my phone /sdcard/ properly. When I tried yesterday, I was using adb push to move the ROM zip to the sdcard. And it would say that it was done, no errors, and it looked like it was successful. But every time I tried to run, I got Status 7 error.

Today, my phone was already booted into Android, so I hooked up to computer via USB and tried to copy the zip over from within Windows. Well, it was not transferring properly. It would freeze at about half-way and not continue, and then give me some error like the phone rejected it or some reason and couldn't copy. I tried using AirDroid, and it was still getting stuck and wouldn't finish copying. Then I rebooted into recovery, and tried to push the zip onto the phone. Everything looked fine, like before. So I booted back into Android, hooked up via USB, and checked in Windows - this is what I found:

The actual file size: 192 MB

Size of file on phone: 162 MB

So clearly the file was not being copied properly. I don't understand why I can't copy stuff onto my phone anymore. Any thoughts...??

Gonna keep trying from Windows, via USB... because adb push clearly isn't working. I'll update here what happens.
[HTC One S] LS.xD:
I successfully unbranded and upgraded a One S by --> S-OFF --> change CID --> Run unbranded RUU. Had no issues at all. May still be an option :)
[HTC One S] arjundas86:
I was able to copy the ROM zip over to the phone finally. Just took a lot of patience - I waited and made sure my phone didn't fall asleep (seemed like that might be a factor), and it took almost half an hour, but finally did copy the zip over. Checked the file size and everything seemed okay.

This is the CM11 zip where I removed the updater_script and replaced it with Rapier's updater_script. Still getting Status 7 error.

I guess I have to go with S-OFF and flash RUU to update to hboot 2.15. :(
[HTC One S] Rapier:
It has no sense... It should work. Are you on latest official TWRP? Or at least on the one having selinux?

Sent from nowhere over the air...
[HTC One S] arjundas86:
No, the recovery I'm using is CWM v5.8.3.1. It's worked for me so far, so I never bothered upgrading/updating. Do you think that would make a difference though?
[HTC One S] LS.xD:
You need CWM 6.0.4.4+ or modified 2.6.3.0 or higher ;) As these can handle the new SELinus Status of KitKat and 3.4 Kernels :P
[HTC One S] Rapier:
Well you should have started with this :) As LS.xD pointed out, for flashing KK ROMs you'll need a recovery with SELinux support. There is a CWM that has this (PhilZ CWM I believe but I'm not sure since I don't use CWM) and there is an unofficial TWRP 2.6.3.0 with selinux support that you can download from almost every KK ROM thread in OP. Recently TWRP made also the official 2.7.0.0 recovery that has SELinux support and I would recommend you that one since that's the one I am also using.

All your errors came from the fact you were using the wrong recovery. Could be that also your initial modified ROM ZIP would flash OK. Flash one of those recoveries as you like but make sure it has SELinux suport. Try flashing the ROM after that
[HTC One S] arjundas86:
Ohh! I had actually mentioned my recovery right in my original post.

But anyway, thanks a to both of you for pointing this out! I will definitely get one of the newer recoveries and try it again soon! :)

Downloading TWRP 2.6.3.0 right now.
[HTC One S] Rapier:
If you download 2.6.3.0, make sure you're downloading a selinux moded one from a KK ROM thread not the official one from the link I gave. The official 2.6.3.0 does not support selinux, only the latest 2.7.0.0 does

Sent from nowhere over the air..
[HTC One S] arjundas86:
Just wanted to check before doing it... but do I have to do anything special for going from CWM to TWRP? Can I just do

fastboot flash recovery recovery.img

or do I have to remove CWM somehow?

I tried to install TWRP from Goo Manager app, and it didn't work. Now my device won't even boot into recovery - at all. It looks like recovery is about to load, and then it just reboots again, into Android.

In the past, I've also tried to install a newer version of CWM recovery from ROM Manager app, and that didn't work either.

EDIT:

I tried flashing TWRP 2.7.0.0 from fastboot, and it didn't work. In the command window, it says Sending recovery, then Writing recovery, then Finished. But when I try to go into recovery, it can't. It reboots again, and into Android.

EDIT:

I was able to flash TWRP 2.6.3.0-selinux. Back in business!
[HTC One S] arjundas86:
So I have working TWRP 2.6.3.0 with selinux - I got it from: http://xdaforums.com/showthread.php?t=2528113

But I still am not able to flash CM11 rom. I downloaded the latest snapshot, modified it as instructed by Rapier, and tried flashing it. In TWRP, it said "successful", but it gives me bootloop.

Then I tried flashing the boot.img via fastboot USB, and it didn't help either.
[HTC One S] Rapier:
What might be the problem now is the way you're flashing the boot.img via fastboot. Please detail the exact steps you make for flashing the kernel and also the output from the command prompt.

If in TWRP you have the message that the flash was successful, then it is. Only thing remaining is the kernel flash.

If none of the above will work, it could be that you need to upgrade the firmware to 2.15. Might be that your phone does not work on KK with older hboot
[HTC One S] arjundas86:
I extracted the boot.img from the ROM zip, moved it to the fastboot folder on my computer, then ran command prompt from there. I put the phone in bootloader mode. Then tried fastboot devices from the command prompt, and that verified that the device was responding via USB. Then I ran:

fastboot flash boot boot.img

from the command line. The output was along the lines of Sending boot, OK, Writing boot, OK.

I'll try all the steps again, and report the exact output from TWRP and from flashing boot.img.
[HTC One S] Rapier:
The steps are correct.... I wish you just had a bad try. If now doesn't work again, I guess the only solution for you is to upgrade the firmware :(
[HTC One S] arjundas86:
Did a wipe. Output:

Updating partition details...
Formatting Cache using mke2fs...
Done.
Formatting Data using mke2fs...
Done.
Wiping Android Secure
Updating partition details...

Then I flashed the zip file. Output:

Installing '/sdcard/CM11-ROM
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Updating partition details...

At the top it says "Zip Install Complete"

At the bottom, there's buttons for Home, Wipe cache/dalvik, and Reboot System. And in between these buttons, in blue, it says "Successful."

Then I clicked the "wipe cache/dalvik" button. The output was:

Formatting cache using mke2fs...
Done.
Updating partition details...
Wiping Dalvik Cache Directories...
-- Dalvik Cache Directories Wipe Complete!

Updating partition details...

At the top, it says Cache & Dalvik Wipe Complete.

(In blue) Successful

Then from command prompt over fastboot USB, I did: fastboot flash boot boot.img

sending 'boot' (6078 KB)...
OKAY [ 0.947s]
writing 'boot'...
OKAY [ 1.537s]
finished. total time: 2.485s

Still only getting bootloop... I guess it's time to give up on this method, and go for S-OFF and update to hboot 2.15...
[HTC One S] Rapier:
Guess so...sorry about that. :(
[HTC One S] arjundas86:
No worries. Thanks for all the help - both of you guys! :)

Now, I'm thinking, first I'll S-OFF. Can I just run the Firewater or Rumrunner tools directly with hboot 1.08? If you're not sure, that's okay, I'll just read more and find out.
[HTC One S] Rapier:
For almost 1 and a half year I've stayed S-On since I was on hboot 1.06 and didn't really need it. I've got S-Off just this week and I've used Rumrunner cause I found it easier to use. Didn't work from the very first try, there was an issue with the drivers. But after I made ADB/fastboot to work properly, it took less than 10 min from the first try. I flashed TwistedKat to try the S-Off since I've read some users successfully gaining S-Off while they were on Twisted. For you this is not possible since it is a KK ROM and you just tried one. Best is to have a Sense based ROM to start
[HTC One S] arjundas86:
I JUST got S-OFF. Firewater didn't work for me, but Rumrunner did. :)

Like you, at first neither was working, and then I updated adb and HTC drivers and fixed root access to adb, and then Rumrunner worked. It took 20 minutes or so.

EDIT:

I tried flashing CM11 once again, just to see. Still didn't work.

I got CID now. I'll run an appropriate RUU to get hboot 2.15.
[HTC One S] Rapier:
You don't have to change your CID. I didn't do that. There were issues reported by some users when going back and forth through the firmwares and I didn't wanted to change it. Just take the firmware ZIP you would like (I used a moded 2.15 that has the red warning removed) and inside that ZIP you'll find a text file...just put your CID in that text file the same as the other CIDs are there and the firmware will flash.

What you'll have to do is the following:

- in a command prompt having your phone in fastboot mode issue the "fastboot getvar all" command. This will show you the CID and Model ID (MID) of your phone

- open the firmware zip and modify the "android-info.txt" file to include your CID and Model ID (MID) if it's the case

Now the firmwmare ZIP will flash without giving you invalid CID or MID error

You can find this info and also the firmware ZIP files through amability of Flashalot in his thread HERE
[HTC One S] arjundas86:
Sorry, what I meant in my last post was that I had already gotten SuperCID.

I'm not sure what you mean when you're talking about flashing firmware ZIP. I thought the only way to change hboot version was by running a RUU. Is this a less risky way to update hboot?

I did a bit more reading into running RUUs, and it sounded riskier to me than what I've done so far (more likely to brick by accident). Plus I've seen contradicting statements on what to do (i.e. first lock the bootloader, then run RUU vs. no need to lock bootloader). Also regarding flashing a RUU when I have superCID, that it is risky.

For now, I just installed ViperOneS 3 (based on JellyBean 4.2, with Sense). If I find this unstable, or in a few months maybe, when there are more stable KitKat ROMs out there, I'll re-visit this... Just a little worried about the whole running a RUU thing.
[HTC One S] Rapier:
You DON"T need to run a RUU for upgrading your firmware if you're S-Off. Being S-Off (you said it worked for you), you just have to flash a firmware zip in recovery like you do with a ROM ZIP. And you can find firmware ZIP-s in the thread I've linked to you in my previous post. You have there the firmware ZIPs. Don't play with RUUs or relocking bootloader or things like this. Those were all things to do if you were not S-Off and if you play with them you might even loose your S-Off
[HTC One S] arjundas86:
Ahh, that makes sense now. I did not know those kind of firmware zips existed! Yes, S-OFF worked for me.

Thanks! This I feel comfortable doing :)

Should I change my CID back to what it was? Or with CID 11111111, I can flash any of those?

EDIT: Got the answer from the thread you linked above: Yes I can flash the firmware with superCID.
[HTC One S] Rapier:
Or, you can check my previous post, I told you there how to modify the android-info.txt in the firmware ZIP to match your current CID. This info is also in the thread I've linked to you
[HTC One S] arjundas86:
Thanks buddy! It worked, I'm now hboot 2.15. Now to try some KK ROMs! :)
[HTC One S] KitStarVP:
this is for villec2 or s4 ?????
[HTC One S] LS.xD:
Is about the S4.
[Galaxy S 4 Mini General] Sam Solomon:
I saw the GT-9195 isnt updated with 2014 Update on "I9195XXUBNB3"

All are 4.2.2 ..Waiting for 4.4 :p
[Galaxy S 4 Mini General] ert69:
Whats the point of your thread?
[Galaxy S 4 Mini General] Jonny:
Thread closed as its useless.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] EwOkie:
Ok deleted some bloatware on a friends S4 Mini and must have deleted the clock from lockscreen (left side on display)

Not the one at the top right...but the dash clock

Help please as not sure which one it is :confused: