yashsingh1/xdaforums huggingface dataset:
[HTC One S] rc420head:
Yeah you should be good to go. If you want to check go to settings /about/software information /more and under kernel it will be 3.4.x (assuming your still on the JB ota)
[HTC One S] JohnYossarian:
Hi,

I want to update my Stock Rom, but I am not certain how to do. I have a T-mobile branded device with 2.38.111.10 on it and HBOOT 1.14.0002.

I already rooted my device and changed the CID from TMOB_101 to SuperCID and then to HTC__102 and relocked my bootloader.

I thought I just have to run a RUU with a higher software number, but it always cancels the installation with an error (159).

Any help`?
[HTC One S] JohnYossarian:
Yes I am
[HTC One S] rc420head:
OK good now follow the Instructions in op to update your firmware.

After that flash any rom that you like.

If you like the stock feel but want some cool add ons flash this one

http://xdaforums.com/showthread.php?p=40703140
[HTC One S] JohnYossarian:
Ok, can I keep my HTC__102 CID or should I have to change it to TMOB010? It is an european device.
[HTC One S] rc420head:
Change it to T-MOB010 when flashing firmware found here in post #2 (firmware checks cid) after that you can change it back. Since your s-off just do it in fastboot "fastboot write Cid T-MOB010"
[HTC One S] khan.orak:
Can that be due to a MID mismatch?
[HTC One S] rc420head:
Cid mismatch but no need to run RUU just update firmware and flash new rom of choice
[HTC One S] forgiven90:
This is maybe a dumb question, but I searched for a ICS RUU and can't zero in on anything got a quick sugg?
[HTC One S] khan.orak:
http://xdaforums.com/showthread.php?t=2094414

All RUU's are here.
[HTC One S] JohnYossarian:
So I did, what you said: I changed my CID from HTC__102 to T-MOB010, diwnloaded your firmware.zip and flashed it as described.

During the procedure I get following output:
[HTC One S] forgiven90:
You need to flash the firmware zip two times, like as soon as you get that error message just flash again.
[HTC One S] rc420head:
Yeah what he said \|/ :D
[HTC One S] forgiven90:
Ok bear with me here... I downloaded a RUU here from this site the first time I had problems so I'm a bit wary (it was a euro RUU. BUT I've heard good things about this 2.21 version) ... My question is this, if I try this RUU: RUU_Ville_U_ICS_40_S_HTC_Europe_2.21.401.10_Radio_1.06s.50.02.27_2_10.08.50.04L__release_271119_signed.exe

will I hve a problem with the T-MO CID? or since I'm s-off should I just leave it at 11111111?
[HTC One S] rc420head:
11111111 is fine for RUU. Firmware is what you need T-MOB010 to flash (at least the firmware in post 2 does)
[HTC One S] JohnYossarian:
When I flash the firmware.zip two times, I just receive the error message two times.
[HTC One S] rc420head:
Is your phone a T-mobile branded phone or HTC branded? They are two different model #'s
[HTC One S] rc420head:
I'm Going for fast hike I'll be back in 2-3 hours.
[HTC One S] JohnYossarian:
The first time I switched my phone on, it showed some stuff from T-Mobile and the CID was before rooting etc. T-MOB101. The reseller also sold it as simlock and netfree with an T-Mobile (Germany) branding.
[HTC One S] rc420head:
Try this firmware http://www.mediafire.com/?mc1mh05p669hspm and report back if it worked, you might still have to flash it twice if you get error after first flash.
[HTC One S] forgiven90:
Needing some help... I have downloaded and flashed 3 different RUUs (2 euro and 1 T-MO) and they all boot but as soon as I unlock the screen I get a black screen with only a notification bar that is unresponsive, then the system F/C and the device starts to bootloop. The first time I went ahead and flashed the new firmware.zip and everything seemed fine until I restored my DarkSense 2.5.0 rom then no radio and soon it started bootlooping too. I'm flashing all these with SuperCID except the firmware.zip. Hboot and radio changes on all of the RUU's, including the firmware.zip. I haven't tried fastbooting the boot.img because I'm s-off... I'm out of ideas here. Maybe I need a very specific RUU??

If it helps any my model # is PJ40110 HTC branded gray...
[HTC One S] rc420head:
What firmware did you use ? The one in post #2 if so try the one I posted a few posts above.
[HTC One S] forgiven90:
Yes I used the second post one... Does it not matter that these RUU/ROM's are not functioning first? I was reading in the other Firmware thread about somebody with my exact problem but hadn't found a response to his problem yet. another said we need to do a full wipe before we flash our desired rom/backup too.. But I'll try this other link u posted now and report back, thanks!
[HTC One S] rc420head:
Some have said you might have to flash an old ruu with a lower hboot in it (like ics) then do the Euro firmware.zip from a few posts back
[HTC One S] forgiven90:
Quick but important question, do I change my CID to the T-MOB010 or I also saw a T-MOB101 or leave it as 11111111?
[HTC One S] rc420head:
for that one 11111111 or HTC__102 should work.

i think i'm going to change the name of this thread because its more for t-mobile branded phones, this thread http://xdaforums.com/showthread.php?t=2322755 is better for international phones but ill still try and help anyone here.
[HTC One S] yz250il:
Thanks, for now I'm on CM10.1 but I do have a screen shot after I I did the Ota and it's like that, so in good to go. :beer:

Is it the right place to ask how to get the RUU to work when it's in *. Zip and not an EXE?
[HTC One S] rc420head:
Idk never do it I would assume you extract it first then exe would be in extracted folder?
[HTC One S] yz250il:
I didn't do anything yet. I just downloaded the file:

OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.zip

I'm not sure how to use it, do i need to unlock the bootloader again? flash back the stock recovery first? or just flash it with TWRP 2.3.x....?

I only ask because for some reason my rooted stock JB 3.16 update nandroid is not working , kept getting black screen, can see why....

Thanks
[HTC One S] khan.orak:
That's not an RUU, that's an OTA. You cannot flash it just like that. You need to have everything Stock to Flash that. Stock ROM, Recovery etc.

That's what I have found out about OTA's up till now. You cannot use it if you are on anything other than a STOCK ROM.

RUUs are the easiest to get stock.
[HTC One S] JohnYossarian:
It did work! Now I have the HBOOT 2.15. Can I just use any RUU now? I want to get rid off this annoying T-Mobile Sounds.

EDIT: Did use a RUU and it works like a charme! Thank you so much for your efforts to get my phone working as intended.
[HTC One S] rc420head:
Just want to thank everyone for helping each other out, that's what this threads for. Remember to go to the original post and hit that thanks button if I helped you in anyway:D also head over to mkinney88's thread and hit his thanks button

http://xdaforums.com/showthread.php?p=40703140

This thread was his idea I just agreed to do it. :what:

Also please speak up if there are any unanswered questions (I may of missed or forgot about you).
[HTC One S] ardax:
I think a full ROM OTA can be flashed to non-stock phones. You'd have to pull the firmware package out and install that first (to take the device back to stock firmware/recovery), then boot into recovery and flash the OTA zip from there. OTA updates can only be applied to stock phones though -- they typically only contain patches to the stock items.

That said, this is very much a case of "just because you can doesn't mean you should."

Agreed. It's far easier to use an RUU then mess around with OTA zips. But if the OTA zip is the only thing available, then it might work in a pinch.
[HTC One S] khan.orak:
So that means that in order to flash OTA one has to be on stock ROM.

Also the firmware.zip is to be flashed via fastboot, correct???
[HTC One S] HeXDeMoN:
You have the same problem as me and a few other people who have tried to upgrade the firmware. You cant be s-off anymore or you will get that black screen. As soon as you s-on you will be able to fully boot up but then you will have a signal issue and noones found a way to really fix. vatsaman has luck with disabling fast dormancy, I didnt try that for myself yet as I bought a nexus 4.

Kinda hoping someone will solve this issue so I can give the phone to my sister.
[HTC One S] khan.orak:
I think that somehow, even after S-OFF, an MID or Model ID mismatch can result in errors(?)

I think that RUU should be used which supports one's MID.
[HTC One S] HeXDeMoN:
It wouldn't hurt, but his specific problem is the firmware update messed up somehow or someway and now he will never be able to boot up any rom/ruu while being S-Off until someone figures out a fix.
[HTC One S] real187:
S-off isnt the real probleem.

Its the mid mismatch, and because of the s-off it writes to the phone regardless, ending up in a ****ed up result.

OP should specify devices that are supported. By mid and cid. Saves trouble.

A tmob eu device, is different in mid than a USA tmob device.

People especially noobs should do it the normal (easy) way. RUU/ota the official way.

If that dont work then use this method.

(its like that in the other tread).

That said, OP method should work without problems.

Verstuurd van mijn HTC One S met Tapatalk
[HTC One S] rc420head:
That's what I was thinking too I'll change the op when I get home from work.

Thank you for your input

Edit: now I'm going to ask a noob question :what: how does one find there mid?
[HTC One S] real187:
Via fastboot.

Fastboot getvar all (instead of all u can also use mid or cid)

You could also ask People to post mid/cid who did the firmware update successfully just to confirm multiple devices. It would only make this tread better.

Verstuurd van mijn HTC One S met Tapatalk
[HTC One S] HeXDeMoN:
Well how does one fix the mid? Because running the RUU doesn't fix our issue, I've done it 30 or so times various different TMOUS ones. If you have a method you think will work then please share, I will guinea pig for it.
[HTC One S] real187:
Mid can't be changed, we don't have a proper eng hboot.

Solution? I don't know but I will give my thoughts no problem.

What's your device like?

S-off? What hboot? Origin of device? Branded? Bought brand new? Cid? Original cid? Last stock softwareversion you where on?

Verstuurd van mijn HTC One S met Tapatalk
[HTC One S] khan.orak:
CID Getter from play store also shows CID and MID. CID at the top and model ID in the line "[ro.aa.modelid] = xxxxxxxx"
[HTC One S] HeXDeMoN:
Sorry for late reply just got out of work.

Do you want to know what it currently is? or what it was when I flashed firmware.zip?

Currently:

1. s-on *phone wont boot with s-off anymore*

2. 1.09

3. ebay

4. Tmobile USA *but I replaced the glass with a HTC branded one*

5. Used but Ive had it like a year now

6. T-MOB010

7. T-MOB010

8.1.84.531.2 710rd

When I flashed firmware.zip: *I actually flashed it fine 2x, the 3rd time *when mkinney88 updated it, is when I soft bricked it*

1. s-off

2. 2.15

3. ebay

4. Tmobile USA *but I replaced the glass with a HTC branded one*

5. Used but Ive had it like a year now

6. supercid

7. T-MOB010

8. Whatever the latest tmous stock jb rom is.

Btw my mid is PJ4011000 currently
[HTC One S] rc420head:
#2. 2.35? Is that your hboot? I've never seen 2.35 newest for t-mobile us is 2.15

Do you still have soft brick?
[HTC One S] HeXDeMoN:
Typo sorry,

No and yes? when you go back to S-On you can do anything you want but as soon as you go back to s-off then its non-stop bootloops. You'll get to the lockscreen and open it and it will be a white screen saying preparing storage, then after a few seconds will reboot and goto a black home screen where you can do nothing and then it just keeps bootlooping to the black screen every few seconds.

Then if you go back to S-On you can boot up fine but your signal/radio will be messed up. It's possible to get the signal working but it will constantly go out and you have to turn off data on and off to get it back. One person had luck with turning off fast dormancy and they didnt lose signal anymore.
[HTC One S] real187:
Will reply tommorow (4 wat its worth), I don't live stateside, its to late over here.

Verstuurd van mijn HTC One S met Tapatalk
[HTC One S] mkinney88:
I have soft bricked my phone and fixed it. Symptoms same no signal and if I s-off no boot. But I was s-offing with facepalm then I tried moonshine and behold no problems and the reason is look at the files you flash via facepalm ...... Hint hint its a firmware.zip which causes the problem I believe moonshine uses exploits in the boot loader so try that and then update your radios !!!!

---------- Post added at 11:12 PM ---------- Previous post was at 11:07 PM ----------

Also the posted firmware is for S4 devices fyi
[HTC One S] rc420head:
You really are the man aren't you!!

First I forgot to put s4 in op

Second I didn't even think of s-off method (I used facepalm long ago and forgot about moonshine)
[HTC One S] HeXDeMoN:
I've used moonshine twice to s-off and it would have the same issue. Although both times I used it when I was on 3.14.531.17. I guess it wouldn't hurt to try it on 3.14.531.11, is that what you used it on?
[HTC One S] mkinney88:
Okay when you do facepalm s-off look at the pj4010000 see whats in in? radio, rcdata, partitions ect. Now look at the steps.... what you are doing is flashing the firmware from a RUU for the HTC ONE S with HBOOT 2.15 and with a oem boot after you are using the writing option to write the s-off flag partition. So what you really should do is S-on and RUU or whatever you want to do and then use the firmware.zip from your RUU or the current one from the OP here and do that same steps but!!!!! with the firmware from the OP NOT FROM FACEPALMS
[HTC One S] real187:
My thoughts ;)

The mid thing is weird, because i have read that s-off/s-on tmob scid devices could run eu jb regardless of mid, but afterwards got ****ed with otas (think with secured 04 mmcblk) Also when activating s-on while on the eu jb it sometimes also ****ed up the device.

Why did you do the 3rd flash?

Where those files based on the same softwareversion? The .17

Since we don't now the content of all the partitions and the containing files it could also mismatch in there somewhere.

I think also noticed that when ruuing a device.

If files are the same they won't always be overwriten, files like hboot.

The unlocking loop when s-off also accurs when on completely stock rom? Also with stock recovery.

Also an older ics Ruu still won't run? When you do s-off.

Also you did try S-off on softwareversion you where on when you did it the first time?

You also tried, running ics stock (in s-on state). Then doing the official ota (still s-on state). Then when all updates are done going soff.

On your last post.

The .17 is that the latest update with the secured 04 mmcblk? (That's causing problems with getting supercid?).

With the supercid method back in the days, I did a extra step. I did the supercid (hexedit method), s-off. Then afterwards I wrote back my original 04 blk file again,

Because cid changing could now be done trough fastboot.

Verstuurd van mijn HTC One S met Tapatalk
[HTC One S] mkinney88:
changing cid can only be done by fastboot via S-OFF S-ON you need to hex edit
[HTC One S] HeXDeMoN:
So you want me to use the facepalm method but using firmware.zip from official ruu or the one in OP? Including the soffbin3.zip part of it?

Interesting I read the facepalm thread and it seems more people then I thought have the same issue as I do now.

Why did you do the 3rd flash?

Cause im dumb? lol I have a habbit of wanting everything completely updated and mkinney88 said he updated his firmware.zip so I flashed it *which btw I dont blame him at all, he even stated its not needed to update if you already used his other one*

Where those files based on the same softwareversion? The .17

I dunno its what was in mkinney88 thread

Since we don't now the content of all the partitions and the containing files it could also mismatch in there somewhere.

I think also noticed that when ruuing a device.

If files are the same they won't always be overwriten, files like hboot.

The unlocking loop when s-off also accurs when on completely stock rom? Also with stock recovery.

yes, I can be complete stock just running a fresh ruu boot up play with phone can do anything i want restart as many times as I want. As soon as I s-off then it bootloops

Also an older ics Ruu still won't run? When you do s-off.

Actually I think everytime I did it, I went to JB rom first, I'll try from ICS with facepalm

Also you did try S-off on softwareversion you where on when you did it the first time?

yup

You also tried, running ics stock (in s-on state). Then doing the official ota (still s-on state). Then when all updates are done going soff.

Just did that right before this post, used OTA to get to JB then used moonshine.. bootloops

On your last post.

The .17 is that the latest update with the secured 04 mmcblk? (That's causing problems with getting supercid?).

not sure?

With the supercid method back in the days, I did a extra step. I did the supercid (hexedit method), s-off. Then afterwards I wrote back my original 04 blk file again,

Because cid changing could now be done trough fastboot.
[HTC One S] mkinney88:
Just the firmware part use the facepalm soffbin
[HTC One S] HeXDeMoN:
hmm now I cant unlock the bootloader, here is what I did

1. ran RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed.exe

2. changed to supercid

3. went s-on

4. started facepalm process

5. got stuck here

C:\adb>adb shell su -c "/data/local/tmp/soffbin3"

/system/bin/sh: su: not found

My genius forgot to root because I read (unlock/custom recovery is optional) but just a few words before that it said to be rooted

6.Anyways I attempt to unlock my bootloader

C:\adb>fastboot flash unlocktoken Unlock_code.bin

sending 'unlocktoken' (0 KB)...

OKAY [ 0.148s]

writing 'unlocktoken'...

FAILED (remote: unlock token check failed)

finished. total time: 0.169s

7. I create a new unlock token at htcdev which "works" I get to the menu to volume up and hit power button... phone reboots , I goto bootloader and its still locked. I tried it several times and it stays locked even when it says it was successful

C:\adb>fastboot flash unlocktoken Unlock_code.bin

sending 'unlocktoken' (0 KB)...

OKAY [ 0.149s]

writing 'unlocktoken'...

(bootloader) unlock token check successfully

OKAY [ 0.009s]

finished. total time: 0.164s

Gonna start from scratch re run the ruu and try again i guess
[HTC One S] HeXDeMoN:
Well now its really bricked after running a ruu

I have the black screen/qhusb_dload problem
[HTC One S] rc420head:
Can you get into bootloader?
[HTC One S] rc420head:
Here's the link for jtag repair, I'll post this in op too.

http://xdaforums.com/showthread.php?p=37136553
[HTC One S] forgiven90:
I had thot of pursuing this jtag option too, but I'm in Mexico so really wouldn't be very easy for me... Would someone be interested in writing up a sort of tutorial on this s-on/s-off thing? I think I follow the discussion but would like to be sure before I started. Or maybe I should just s-on and flash some older stock ROM and get rid of the device before I'm tempted to flash something on it again! :silly:
[HTC One S] rc420head:
What your phone current status? (bricked, soft bricked, working with problems, fine)

What are you trying to accomplish?
[HTC One S] forgiven90:
I had spent some time in this thread earlier http://xdaforums.com/showthread.php?p=43604836#post43604836 But ya soft bricked, phone only bootloops with everything I have tried I've spent hours on this and finally put the thing in a box in the drawer! this looks the most promising yet tho...
[HTC One S] real187:
Read last post in that topic.

Then bring it in for warranty if you still have it.

that person bricked his device while trying to fix it.

read a few post back in this tread what he tried.

Verstuurd van mijn HTC One S met Tapatalk
[HTC One S] Mooncalled:
I've been trying to narrow down why most phones do this but some do not,
Can you post your
1.mid
2.cid
3.hboot
4.how did you update your firmware
5.whete did you get your firmware
On my firmware thread please.

Per your request in the Illusion ROM thread: http://xdaforums.com/showthread.php?t=2229674&page=164

1. USA T-Mobile One S (S4)

2. T-MOB010 (fastboot getvar cid)

3. 2.15.000

4. OTA updates from T-Mo initially

5. Downloaded RUU from: http://androidfiles.org/ruu/

6. S-On
[HTC One S] rc420head:
OK so looks like you've done it the right way with using ruu to upgrade if you want you can try this method.

Get the firmware.zip from post 2

Then do this

1. fastboot oem lock

2. fastboot erase cache

3. fastboot oem rebootRUU

4. fastboot flash zip firmware.zip, and you might get an error

5. fastboot flash zip firmware.zip again and it should pass and install a bunch of files should take about 2 minutes.

6. the phone does NOT reboot on its own so #7

7. fastboot reboot or fastboot reboot-bootloader

After this you will have stock recovery so you have to reclaim twrp2.3.3
[HTC One S] Mooncalled:
Doing all this will fix my data drop issues with illusion rom? Also, I'm on TWRP 2.5.
[HTC One S] rc420head:
IDK I used this firmware and method and I have never had data drop issues but others have do the same thing and had nothing but data drop issues. So do at your own risk.
[HTC One S] andrewt328:
Im on viper one s 2.0 with jellybean 4.1.1 and 3.4.1 kernel...i have never done the firmware update i dont think...if i try flashing a rom like illusion, will it work or bootloop or brick?

thanks
[HTC One S] rc420head:
if your on kernel 3.4.x then you have the new firmware already but illusion 2.1 will only flash if you have hboot 2.15, give it a try you will not brick. there are 3 things that will happen

1. boots fine and your all good

2.install fails (then your not on hboot 2.15)

3.boot loops (then just restore your backup)

dont forget to fastboot the boot.img if your not s-off
[HTC One S] andrewt328:
yea im on hboot 1.09, and im s-on...Im kinda scared of doing the whole supercid and soff process...so im guess im going to boot loop due to my hboot, how do i upgrade to 2.15...thanks a bunch man
[HTC One S] rc420head:
Follow instructions in op and download firmware.zip from 2nd post
[HTC One S] stoana:
I have no data drops at all..

I'm S-On

1.MID:PJ4010000

2.CID:T-MOB102

3.HBOOT: 2.15.0000

4.,5.Firmware: Went back to stock from my nandroid, relocked my bootloader, flashed the original recovery, ran the ota update and unlocked my phone after that again.

Radio:1.11.50.05.28
[HTC One S] andrewt328:
Ok I just want to make sure im doing this right...when looking a build prop editor i find this....with this setup can i follow the instructions in op to get supercid, s-off, then update my firmware?

1.mid----ro.aa.modelid: PJ010000

2.cid----ro.aa.maincid: HTC_001

3.hboot---1.09

4.how did you update your firmware---?

5.where did you get your firmware---?

Additional:

I have a tmobile branded phone, but i was flashing some europe radios a while back and i think that may have debranded my device?

ro.product.brand: htc_europe

ro.build.project: Ville_JB_45_S:301814

ro.build.id: JRO03C

ro.cwkey: HTC_001

ro.carrier: unknown

ro.build.fingerprint: htc_europe/ville/ville:4.1.1/JRO03C/128506.8:user/release-keys

ro.ril.vmail.22210: 42020, Vodafone IT

ro.product.version: ViperOneS 2.2.0

Kernel version: 3.4.10-ElementalX-4.3+aaron@bella#1 SMP PREEMPT

Baseband Version: 1.08ts.50.02.16_10.08e.50.04L

Thanks for any help!
[HTC One S] rc420head:
Get cid from fastboot "fastboot read cid"
[HTC One S] andrewt328:
ok did the fastboot and my cid is T-MOB010
[HTC One S] rc420head:
OK good

Don't get s-off yet

Follow instructions in op but keep T-MOB010 cid and don't s-off use firmware in post#2

After your done with firmware and have locked bootloader again and flashed TWRP then if you wish you can s-off using moonshine.
[HTC One S] andrewt328:
I cannot open the links in the op...says they do not exist

edit: found the twrp recovery dl on their site...but is it best to use 2.3.3? why not 2.5 or 2.6?

thanks