yashsingh1/xdaforums huggingface dataset:
[HTC One S] Tim2246:
Wow seems simple enough.

So i just need to upgrade my hboot too 2.15 then right?

I downloaded the one you had a link too in the previous post. So how do you flash the hoboot?

is it done through twrp or? easiest way ?

so should I unpack the ruu? or just flash the ruu exe the same way you outlined here and let it do the whole thing?

My big fear is i dont want to lose my s-off and i see on this thread people are losing it?

And lastly a honest opinion please.

the ruu i refered to above is it the newest and can i or will i need to change the radios to like an earlier radio like i am on now to still work with tmobile?

---------- Post added at 10:12 AM ---------- Previous post was at 10:01 AM ----------

Quick side not.

I love the rom I am on but fro example i had a full charge at bed time round 1:30 a.m just got up and is is roughly 10:11 a.m havent used the phone but noticed i am at 24% battery life.

And i already tried wiping cache, dalvic and so fourth and it dont change it.

Is this normal behavior for jelly bean?
[HTC One S] scotty1223:
Flash the hboot as an ruu from Fastboot.

I would definately not say bad battery life is a characteristic of JB. You may just have too many things syncing. Battery life is decent on one one s and one xl.

I personally do not recomend changing radios outside of hboot and other firmware. I always run a complete ruu so everything works together.

---------- Post added at 05:19 PM ---------- Previous post was at 05:17 PM ----------

After you have hboot 2.15,you can extract Rom.zip and run from Fastboot,or just run the .exe.

no one is losing s off from running an ruu. Radio s off stays in place until you purposely change it back to s on.
[HTC One S] Tim2246:
Wante d to take a minute and say Thank You,

I do have a few things syncing both gmail, and my Hotmail are set to push as to to get them as they come in as well as facebook sync.

So in your opinion should I change the hboot?

Like I said I current am using trickdroid 9.1 jb rom which is based off the rom the jb 4.1.1. But have the old hboot 1.4

Does it make a difference.

Is the 2.15 a better hboot?

as far as radio goes.

I get awesome wireless performance and great reception. did notice some screen tear in my news widget at times but livable just occasionally

Honest opinions are always needed.

I guess the reason im asking is,

Should I run the ruu so everything matches?

Or is the rom im using now better performing and feature filled?

and will it work properly on my carrier properly.

I use Tmobile.

Last and final ?

With running the ruu i'll still get the ota right or should I avoid them?

.

---------- Post added at 12:47 PM ---------- Previous post was at 12:05 PM ----------

INFOzip info parsing...

INFOchecking model ID...

FAILED (remote: 41 model id check fail)

finished. total time: 1.867s

Can i change the model id or would it be bad to due so?

my phone is an htc One s bought from t-mobile last year. As i stated i have unlocked, rooted and s-off to cid HTC__001

Just trying to upgrade my hboot to 2.15 instead of 1.14

so i can run the wwe jb ruu
[HTC One S] cannondaleV2000:
so im cangeing the part that starts with T-MOB0 right could someone tell me exactly what numbers to change
[HTC One S] Tim2246:
just the t-mobo10

Change it to 11111111 or HTC__001

Thats 2 undescores after HTC just make sure it is 8 characters.

And dont try to super cid the wwe ru as it has bricking issues. instead try using HTC__001 depending on your model id.
[HTC One S] scotty1223:
you cant change the modle ID on the phone. you can change it on the android info text document,then rezip it. it prolly will flash that way. you can also superCID,so the model id check is ignored.thats what i did- im superCID and that same file flashed fine for me(also t mobile model PJ4011000)

superCID is fine for running RUUs. some folks got jammed up trying to OTA with superCID, as the stock recovery was doing checks that RUUs dont. ive run the RUU with superCID,no issues.

if you want to run RUUs with HTC__001 or some other CID,you may have to edit the android info text document in order to show the phone the correct model id and cid. with s off,there are no signiture checks,so you can do that ;)
[HTC One S] AndroidAutobot:
worked for me. Thanks for the heads up! =)
[HTC One S] cicciocant:
is it true that is not possible to supercid jellybean devices?
[HTC One S] NQNH:
you can get supercid if you are on jellybean, that is not the problem.

you only cant (!) flash OTAs when you are on supercid, this will brick your phone.
[HTC One S] aegentirony:
Thanks for this...Rooted latest tmobile ruu supercid and soff...Thanks for this!
[HTC One S] Evil-Monkey:
Does Super CID affect play store comparability? Example, making certain apps not compatible if you attempt to redownload?
[HTC One S] ryanshew:
No you need the multi dpi play store

HTC_One_S | S-OFF | DeviantXone_2.0 | Twisted_III
[HTC One S] Evil-Monkey:
I have an inverted version, stock playstore also didn't work. I'm mobile right meow but ill look into it when I'm at my laptop.

Thanks!
[HTC One S] Flashalot:
no super cid

it looks like this dose not work on the tmobil jellybean build i have tried this about 20 times and no luck
[HTC One S] carquote:
I'm having the same issue. I've tried several times and everything seemingly goes fine until I run the fastboot oem readcid command and it still shows T-MOB010. I have no idea what the problem could be. I would greatly appreciate some help with this.

K:\Cell\HTC One S\ADB>adb shell

adb server is out of date. killing...

* daemon started successfully *

shell@android:/ $ su

su

root@android:/ # dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4

dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4

2+0 records in

2+0 records out

1024 bytes transferred in 0.001 secs (1024000 bytes/sec)

root@android:/ # exit

exit

shell@android:/ $ exit

exit

K:\Cell\HTC One S\ADB>adb pull /sdcard/mmcblk0p4

adb server is out of date. killing...

* daemon started successfully *

166 KB/s (1024 bytes in 0.006s)

K:\Cell\HTC One S\ADB>adb push mmcblk0p4MOD /sdcard/mmcblk0p4MOD

adb server is out of date. killing...

* daemon started successfully *

66 KB/s (1024 bytes in 0.015s)

K:\Cell\HTC One S\ADB>adb shell

adb server is out of date. killing...

* daemon started successfully *

shell@android:/ $ su

su

root@android:/ # dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4

dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4

2+0 records in

2+0 records out

1024 bytes transferred in 0.007 secs (146285 bytes/sec)

root@android:/ # adb reboot bootloader

adb reboot bootloader

* daemon not running. starting it now on port 5038 *

* daemon started successfully *

error: device not found

1|root@android:/ # exit

exit

1|shell@android:/ $ exit

exit

K:\Cell\HTC One S\ADB>adb reboot bootloader

adb server is out of date. killing...

* daemon started successfully *

K:\Cell\HTC One S\ADB>fastboot oem readcid

... INFOcid: T-MOB010

OKAY [ 0.010s]

finished. total time: 0.011s

K:\Cell\HTC One S\ADB>adb push mmcblk0p4MOD /sdcard/mmcblk0p4MOD

adb server is out of date. killing...

* daemon started successfully *

50 KB/s (1024 bytes in 0.020s)

K:\Cell\HTC One S\ADB>adb shell

adb server is out of date. killing...

* daemon started successfully *

sshell@android:/ $ su

ssu

/system/bin/sh: ssu: not found

127|shell@android:/ $ su

su

shell@android:/ # dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4

dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4

2+0 records in

2+0 records out

1024 bytes transferred in 0.008 secs (128000 bytes/sec)

shell@android:/ # exit

exit

shell@android:/ $ adb reboot bootloader

adb reboot bootloader

* daemon not running. starting it now on port 5038 *

* daemon started successfully *

error: device not found

1|shell@android:/ $ exit

exit

K:\Cell\HTC One S\ADB>adb reboot bootloader

adb server is out of date. killing...

* daemon started successfully *

K:\Cell\HTC One S\ADB>fastboot oem readcid

... INFOcid: T-MOB010

OKAY [ 0.011s]

finished. total time: 0.012s

K:\Cell\HTC One S\ADB>
[HTC One S] Flashalot:
Every thing looks right but the cid is not turning to 11111111 I couldint even do exit after pushing the mmcblk0p4MOD my phone would reboot
[HTC One S] Evil-Monkey:
adb is out of date, search how to update it. Un-install HTC sync manager first, then update adb and fastboot.

echó en Android
[HTC One S] jamus28:
Can anyone please confirm if they took the tmobile OTA then successfully went superCID and S-off after?

I would like to know for a friend.

I can't tell if the reports have been from just a few people using bad drivers or incorrect procedures.
[HTC One S] Sneakyghost:
All I've heard is that the S-OFF exploit no longer works after the recent updates and I won't risk testing it for sure. Glad I have S-OFF.

mobile post
[HTC One S] NQNH:
my update works fine, still have s-off, but I'm not on supercid because Ive read that supercid will brick phones when doing otas.
[HTC One S] scotty1223:
I guarantee you this is more than folks using old drivers or outdated adb utilities. Whether some of you want to admit it or not,this is a real prollem and some phones have been introduced to write protection on mmcblk4-5 preventing a cid change.

The issue may be more complex and have more factors involved than just the OTA. Maybe model number,build date,cid,I don't know.

The bottom line here is if it doesn't work,you'll need to wait for a new exploit.

The lesson to be learned is always take advantage of exploits while they work. Updates may patch them,so it is extremely foolish to think "I'll just ota,then root" or to ever unroot for any other reason than a legitimate warranty claim.
[HTC One S] carquote:
After having tried everything I can think of, including the suggestion of updating adb and fastboot, I'm still unable to achieve SuperCID. I see no reason why other than the above explanation. I never had a need for SuperCID and just flashed a T-mobile based custom JB rom. I guess now I have to wait and hope for a new exploit.
[HTC One S] donb123:
adb and fastboot have absolutely nothing to do with hex editing a file and re-writing a partition using dd! That's ridiculous.

That said, my version of hboot- 2.15 (presumably it's hboot that inhibits this), doesn't allow me to use this exploit. Every time I reboot and check the CID it's gone back to TMOwhatever
[HTC One S] Evil-Monkey:
I'm sorry to hear that. The only thing that comes to mind now is the brick downgrade or waiting. Although waiting doesn't break your phone. I downgraded my phone using brick downgrade but I didn't do it overnight, I read and read. And then read lol.

I'm pretty sure I didn't say that updating the adb drivers and fastboot would fix all the problems but having everything up to date has saved my phone more than once.

echó en Android
[HTC One S] Flashalot:
But if im correct the you can't use it on the euro jb which might apply to the T-Mobile jb
[HTC One S] Evil-Monkey:
I'm not exactly sure. I would have to go back and re read some of that thread since I did that quite some time ago.

Edit: OP states that on the envita side, it may cause permanent bricks if you took JB OTA. But you need unlocked bootloader and recovery to even consider it. I'm guessing most people relocked and went back to stock recovery, rendering this method useless anyways.

If I had an easy method to unbrick my device I would try it since Ive done the downgrade before. But I can't afford it if in case I the JB OTA permanently bricks the Ville.

echó en Android
[HTC One S] ryanshew:
I don't think anyone successfully completed the brick downgrade after taking any JB OTA. That's when all the bricks started happening, I can't remember even one permanent brick before JB with that method. HTC definitely changed something which majorly screws us....bastards, :banghead:

HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
[HTC One S] OCedHrt:
For those with a working hboot, is there any reason why an app with root can't be made to do to necessary steps to change CID?
[HTC One S] scotty1223:
yes. write protection ;)

it doesnt matter wether an app is trying to modifiy a write protected partition,or the user. write protected is write protected. otherwise,and app could have been made a long time ago to give us radio s off!

remember how long we dealt with unlocked/s on hoping for s off? this is the same,except its now been applied to the memory blocks that house the CID as well as the one that houses the secureflag.
[HTC One S] OCedHrt:
But adb shell is exempt? I suppose that is the vulnerability then? TIL.
[HTC One S] scotty1223:
you can appear to write to the protected blocks from the booted OS. you can redump them,and the change will appear to be permanent.the WP is applied during boot,where the actual,original memory block is used,not the one youve changed.

in other words,just because you can change things from within an adb shell,it doesnt mean that they will stick permantly
[HTC One S] real187:
No I had done it on the latest www EU jb with no problems. 2.15 hboot

It seems to apply on the tmob jb update.

Verstuurd van mijn One S met Tapatalk
[HTC One S] scotty1223:
no,its not just the t mobile update. ive seen reports of it working and not working on other versions. there is a user on AF on 3.16.1500.7 and GLOBA001 cid.
[HTC One S] real187:
Oke then. But these are relative new updates. still. People had all the time to do supercid on old sw. If you have not done it before the update why do it afterwards. :confused:

Verstuurd van mijn One S met Tapatalk
[HTC One S] scotty1223:
i agree people need to learn to take advantage of exploits before they are patched.

however,not everyone has had one since they came out. lots of folks are just now picking them up,with the updates allready installed.
[HTC One S] f10a:
I am already rooted, unlocked bootloader, s-on, running the stock unknown TMO JB 1.5A rom and want to get s-off.

how can I get CID 1111111 without going through the htcdev lock/unlock instructions in the op?

thanks!
[HTC One S] machv5:
I used the link and followed the how-to and I was able to change my CID without having S-OFF.
[HTC One S] xxquicksh0txx:
He posted that over almost a year ago.... :banghead:
[HTC One S] d3ckart:
Hi , when I open the file in the Hex editor instead of CWS__001 I get HTC__102 . Is that ok ? I change this value to 11111111?

Thanks
[HTC One S] NQNH:
sure.. so your phone has a german unbranded cid.

but sure you can change this to supercid
[HTC One S] d3ckart:
Im in the process of making it S-off , thats why I asked
[HTC One S] NQNH:
yes, and I said "you can" which sould answered your question :P

the CWS tin the guide is only an example
[HTC One S] ryanshew:
Yes, that is your cid...there are many different ones depending on carrier, location, etc... For example, mine was ROGER001 (or something similar, can't remember off the top of my head).

HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
[HTC One S] Fanagoreca:
Hi, I can't push modified file with ADB. What I miss?!?:confused:
[HTC One S] scotty1223:
Start reading at post 331
[HTC One S] Fanagoreca:
Umm... it's not possible to do this after update, right?!?:confused:
[HTC One S] Flashalot:
No
[HTC One S] scotty1223:
Some have claimed it to still work. Most others have not had success. There are factors that we still do not know. The conclusion I've personally made is that the jb ota has introduced write protection on mmcblk's 4 and 5,at least on some models.
[HTC One S] Fanagoreca:
Yep, for some guys work, but others reported "no luck" . I tried 2-3 times this on custom rom, and now going to do this on official sense. But I.m pretty sure, that doesn't matter.

Thank you for answers!

Edit

===========

I have successfully got s-cid , and S-of.
[HTC One S] Sneakyghost:
Sorry for quickly dropping in here. Haven't gotten the time to read back. Has anyone with a fail after the OTA tried to revert back with the previous RUU (same hboot) and see if it enables writes to p4 again? Naturally, the RUU doesn't change p4 at all but I'm still hoping the write fail might rather be a kernel induced block instead of a no write flag in the partition.

I'd be interested to know what happens if someone flashes back with a RUU and reports how it went.

Or if that had already been tried, could you guys let me know?

Thanks.

Mobile Post
[HTC One S] Fanagoreca:
For me It was successful, after OTA update to change cid. That is on h-boot 2.15 , and stock JB-sense.
[HTC One S] donb123:
super cid no workie

For those that are asking:

I did not take an OTA rather I didn't pay attention to having superCID and s-off in the instrux for mckinney's rom ---> HTC One S USA T-Mobile JellyBean Update * Stock * Rooted * Deodexed * APM <---. I suspect that it was somewhere in firmware.zip that hosed up my ability to change CID. I do not get errors. I simply hex edit the partition, dd it back, it acts like it worked, but you reboot and nada.

Where is this old RUU people are suggesting to try? I'm game.
[HTC One S] Sneakyghost:
RUU can be obtained from http://www.androidfiles.org/ruu/?developer=Ville i think it was. It's the 3.16 for WWE. You can flash any T-Mob ROM on top later I think. Thanks for trying.

Please research if there's any adverse effects for your network when running a WWE RUU before flashing a T-Mob ROM, like bad radio config or something like that. I'm not sure there's T-Mob RUU's with hboot 2.15 you could take.

Mobile Post
[HTC One S] scotty1223:
so you had multiple failures,then success? please share as many details as you can think of,no matter how small they may seem :)
[HTC One S] ryanshew:
If he is tmobile, he won't be able to run any, except for his current one which was just released, but it's the same firmware he is already on.

Need someone with an unbranded phone to try, but don't think it will let them since it would be a lower radio. Not sure if that matters, I've never even run a ruu before.

HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
[HTC One S] Fanagoreca:
Yes, i have multiple failures, but that was on custom rom. I have restored stock sense-rom from nandroid, and then i trayed to push moded file, for first time ADB returned " no such a file, or directory" ...or something like this. Then i decided to change descriibtion of command.

Usually is deskribed so .... " / flash "bla-bla-bla / ..., i only changed and described so \ flash bla-bla-bla\, and this time adb returned ...flashed ...0.004 sec. or something else... Then i make next steps, and cid was changed.

Please excuse my poor english language.:rolleyes:
[HTC One S] donb123:
I do have Tmo. Thanks.
[HTC One S] radeonmaya:
HTC One S T-Mobile H-boot 2.15.0000 can't super CID
[HTC One S] nashwing:
Phone has only been RUU'd with the latest TMOB JB RUU

Bootloader 2.15

Appears to write to p4:

dd if=/sdcard/mmcblk0p4mod of=/dev/block/mmcblk0p4
2+0 records in
2+0 records out
1024 bytes (1.0KB) copied, 0.049321 seconds, 20.3KB/s

but rebooting to bootloader and looking at CID shows T-MOB010 still

C:\Android\platform-tools>fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.016s]
finished. total time: 0.016s

Hopefully this is more descriptive...

EDIT: Got a replacement from T-MOB that came with the JB installed. Same results with new phone. Exactly.
[HTC One S] Crono88:
this is a problem already known. For now there aren't solutions
[HTC One S] cicciocant:
I post my experience.

This is my initial situation:

C:\HTC\Data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.161.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxxxxx
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3769mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

So I was just in jellybean ROM.

I did SuperCID and S-OFF and all is ok.

I returned to my CID VODAP102 and flashed thiis OTA: OTA_Ville_U_JB_45_S_Vodafone_UK_3.16.161.10-3.16.161.9_release_314595ks2c3r4s9728x22k

Now I'm in this situation:

C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.15.50.05.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.161.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3862mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

S-OFF is still present.

Writecid is still possible.
[HTC One S] ryanshew:
Yes, but you were already s-off, we already know nothing will take that away (currently anyways). The issue is if you are s-on to start

HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
[HTC One S] scotty1223:
he was s on to start:

he is one of the lucky ones that have been able to still superCID after the JB update.
[HTC One S] ryanshew:
In the order he has it written, he says he did s-off before he took the latest ota. That is the one causing problems.

HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
[HTC One S] deepblade:
Someone is working on fixing this method after taking OTA? I'm also stuck at my current CID and can't change it.
[HTC One S] scotty1223:
"moonshine" s off is coming soon for the dna and one... maybe it can be adapted? otherwise,theres always jtag if you get too impatient! :)
[HTC One S] jamizzal:
i was able to get this to work in one shot and get s off soon after, quick question i can flash whatever hboot i want now if im correct right?
[HTC One S] scotty1223:
yes.but now that youre s off,you have no real reason not to run the newest ;)
[HTC One S] jamizzal:
wait why would i want to do that? I can't flash radios with any hboot past 1.09 or 1.13 if im correct. Or am i missing something?
[HTC One S] scotty1223:
Newer generally is better. you can easily change radios with any hboot while s off. you'll just need to do it a little differently.
[HTC One S] jamizzal:
would you mind informing me of how its done? I have been out of the loop for a while, im 3 or so months late to the s-off party as you can see haha.
[HTC One S] scotty1223:
In a nutshell:

-any image is simply packed up with an android info text document. I'm sure you can find radio downloads allready packed up.

-place the zip into adb/fastboot folder.

-put phone into fastboot,open cms.

-flash:

Fastboot erase cache

Fastboot oem rebootRUU

Fastboot flash zip zipname.zip

Fastboot reboot
[HTC One S] jamizzal:
thanks i will definitely try that, would you happen to know where the list of radios is here? Or is this an alternative? http://xdaforums.com/showthread.php?p=34271913
[HTC One S] scotty1223:
That looks like an alternative. Ive never used it,I prefer to do things manually whenever I can.
[HTC One S] jamizzal:
ahh true ima try the alternative see if it works since all the radios are there, if not do it manually. Either way, you my good sir have earned many thanks.
[HTC One S] adeebulrehman:
Hi shootind5nukes,

I have a issue when trying this.

First when I try to do commad su, "Su" is not recognized as an internal or external command,

Second When I copy the file via TWRP2.5 and edit the TMUS010 with 11111111 or HTC 001 via Hexa Editor the file size changes.

Can you please give me some more advices.

Thanks and Regard's