I've been going through some Rom/Flashing issues with my HTC One S and having the RUU for my device to start all over again flashing back to stock recovery, relocking the phone and using the RUU to get myself back to stock.
To give you a run down. I just got my phone and I've spent the last month figuring this whole thing out due to this amazing online community on here.
I use TWRP 2.2 as my recovery, unfortunately I dived in, and failed to back up my original non-rooted stock Rom but that's still ok.
[I know nooby but bearing in mind this has all taken place within like, two weeks.] I used to switch effortlessly between MIUI v4 and the stock rooted HTC Sense 4.0.4 android just by backing up and restoring the roms but then I flashed to Paranoid Android and I think I fiddled with something during that flashing process which is why I'm probably getting some arbitrary technical issues now and I'd like to start over!
So anyways, any of you fine gentlemen and possibly ladies out there who could point me in the direction of a Uk HTC One S T-mobile RUU?
Thanks
Unfortunately none. I need one, too.
Sent from my locked, tampered ville
What do you need yours for exactly? Maybe I can help you out
Sent from my HTC One S using xda app-developers app
I have a tampered bootloader, and the flag needs to be reset. That's why I need one. And I have a T-Mobile CID.
I know there are ways to tamper and/or change the CID but I don't particularly want to do that myself.
Sent from my HTC One S using xda app-developers app
I can't change CID, because I don't have an unlocked bootloader.
Sent from my locked, tampered ville
You can use hassoon's HTC one s all in one kit to unlock the bootloader can't you?
Sent from my HTC One S using xda app-developers app
Do a full wipe, flash something like ARHD, change the CID, flash HTC Europe RUUs.
Yes, but I don't want to root... I need to restore from an RUU because that will remove my tampered flag.
Sent from my locked, tampered ville
usaff22 said:
Yes, but I don't want to root... I need to restore from an RUU because that will remove my tampered flag.
Sent from my locked, tampered ville
Click to expand...
Click to collapse
I had a similar issue with my orange uk branded one s but after installing twrp i was able to change my cid from orange to a generic htc cid. I then re installed stock recovery, relocked the bootloader and then was able to install the european ruu. This worked fine and bootloader no longer says tampered although it does say relocked. I believe this is the best you can get if the bootloader has been unlocked at some stage.
norniron said:
I had a similar issue with my orange uk branded one s but after installing twrp i was able to change my cid from orange to a generic htc cid. I then re installed stock recovery, relocked the bootloader and then was able to install the european ruu. This worked fine and bootloader no longer says tampered although it does say relocked. I believe this is the best you can get if the bootloader has been unlocked at some stage.
Click to expand...
Click to collapse
How do you change the CID using twrp? What rom do you flash?
Sent from my HTC One S using xda app-developers app
fastboot oem writecid HTC__001
I have never unlocked though. Only tampered. So it's still locked but tampered.
Sent from my locked, tampered ville
Amilka said:
How do you change the CID using twrp? What rom do you flash?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I just started the phone in twrp recovery and followed this guide to change cid :
http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
i then installed this ruu after relocking bootloader :
http://forum.xda-developers.com/showthread.php?t=1861981
Related
Hi there!
i have a htc one s phone, originally with a "HTC__K18" cid which i've changed to "HTC__001".
i've read a lot about debranding it, switching its rom to a european one and get OTAs, and i understand that i can only switch to Super-CID in order to get the RUU to work. however - i won't be able to install the JB OTA.
my question is - can i install the RUU with Super-CID, then change it back to "HTC__001" and install the OTA?
thanks,
Yossi
Doea anyone know where I can find the answer?
Sent from my HTC One S using xda app-developers app
The unbranded RUU should work if your CID is HTC__001
Sent from my One S using Tapatalk 2
Which one should I choose from the ruu link on the sticky post?
I tried the European ones and it failed..
Sent from my HTC One S using xda app-developers app
yossif89 said:
Which one should I choose from the ruu link on the sticky post?
I tried the European ones and it failed..
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
What error message did it give?
Sent from my One S using Tapatalk 2
Now I've tried the JB European ruin, and got Error 132 signature/validation error..
Sent from my HTC One S using xda app-developers app
You might want to redownload the RUU. Is the latency on your connection good?
hmm..
i don't think this is the problem.. it said that i should find another rom which suits my device.
yossif89 said:
i don't think this is the problem.. it said that i should find another rom which suits my device.
Click to expand...
Click to collapse
Whats the mid of the device? Is it correct for the ruu? Tried it in fastboot USB mode?
You can even try it without a simcard inserted.
And is this on a relocked device or still unlocked?
And whats your current boot version?
Verstuurd van mijn HTC One S met Tapatalk
real187 said:
Whats the mid of the device? Is it correct for the ruu? Tried it in fastboot USB mode?
You can even try it without a simcard inserted.
And is this on a relocked device or still unlocked?
And whats your current boot version?
Verstuurd van mijn HTC One S met Tapatalk
Click to expand...
Click to collapse
my mid is PJ4010000.
I don't know if it's the right RUU for my device - i don't know which is the right one, since i've changed the cid and my old cid doesn't have any RUU available.
i've locked, rooted, changed cid and then relocked the device, so there's should be no problem with that.
should i do something with the mid? is it safe to change it?
yossif89 said:
my mid is PJ4010000.
I don't know if it's the right RUU for my device - i don't know which is the right one, since i've changed the cid and my old cid doesn't have any RUU available.
i've locked, rooted, changed cid and then relocked the device, so there's should be no problem with that.
should i do something with the mid? is it safe to change it?
Click to expand...
Click to collapse
oke your mid is fine for the ruu.
this cannot be changed yet (as far as i know)
and what is your current hboot version?
if your still on 2.xx you can also try ro run a older ruu and then do the ota (do not do it on supercid!!)
remember an ruu with a older hboot than your original cannot be flashed (downgrade) if your not s-off
as usaff22 said have you tried downloading another source of the ruu.
have you restored the stock recovery before relocking and running the ruu?
if you are not s-off you have to restore the stock recovery before running the ruu.
tried it without a inserted simcard?
tried the ruu with phone in fastboot usb mode? (heard of people geting error on 1st try but when starting the ruu again it went tru the whole process).
Thanks for your reply!
I'll try everything and let you know if it went fine.
Do you have another source for the OTA?
Sent from my HTC One S using xda app-developers app
I can't seem to be able to get the Viper One S ROM running on my phone, but I could when I came from stock.
My One S is 4.2.2 root box
TWRP 2.4.4
HBOOT 1.14
S-OFF SuperCID 11111111
And I know what RUU to use
But I was wondering if I had to do anything besides lock the bootloader.
Do I just run the RUU?
No writing secure flags, changing CID or having to S-On?
Because I don't want to mess up and brick my device.
Sent from my HTC One S using xda app-developers app
You didn't search good enough.
In every get back to stock topic the minimal requirement are asked and given several times.
Verstuurd van mijn HTC One S met Tapatalk
lmfaohd2 said:
I can't seem to be able to get the Viper One S ROM running on my phone, but I could when I came from stock.
My One S is 4.2.2 root box
TWRP 2.4.4
HBOOT 1.14
S-OFF SuperCID 11111111
And I know what RUU to use
But I was wondering if I had to do anything besides lock the bootloader.
Do I just run the RUU?
No writing secure flags, changing CID or having to S-On?
Because I don't want to mess up and brick my device.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Try the OTA and the Ruu need to lock your bootloader vie cmd fastboot oem lock and unlock vie the same unlock_code
That's all I know
okay so ive already bricked 1 device because of the ota update my question is can i root/re-unlock the boot loader with out bricking this device? also ive been reading that htcdev now blocks supercid 111111 so if going to try getting another unlocktoken will i need to fastboot write cid 222222? also if my device is S-Off then why is it when i try to write in fastboot it returns the error Failed(Remote Not Allowed)... where in my evo 3d allows writing and it also is S-Off and Relocked
Current Specs:
Android 4.1.1
Software build:3.18.502.6 710RD
HBOOT INFO
*** RELOCKED***
EVITA PVT SHIP S-OFF RL
CID- 11111111
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
S-off on our device does not let you write certain things with a locked bootloader. Why? I'm not really sure.
You can't brick unlocking the bootloader unless you're crazy stupid and doing things wrong.
Do you not have the original unlock token from when you unlocked last time?
If not, does your current rom have root? If so you should be able to hex edit your Cid.
If not you're sol until 3.18 root comes out.
Sent from my HTC One X using xda app-developers app
exad said:
S-off on our device does not let you write certain things with a locked bootloader. Why? I'm not really sure.
You can't brick unlocking the bootloader unless you're crazy stupid and doing things wrong.
Do you not have the original unlock token from when you unlocked last time?
If not, does your current rom have root? If so you should be able to hex edit your Cid.
If not you're sol until 3.18 root comes out.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I actually have 5 different tokend for 5 different one x devices and i dont want to flash wrong token
FragmentedLogik said:
I actually have 5 different tokend for 5 different one x devices and i dont want to flash wrong token
Click to expand...
Click to collapse
Why not? what will happen?
exad said:
Why not? what will happen?
Click to expand...
Click to collapse
just hesitant on flashing it seeing how the recent OTA update hard bricked one of my Devices and i cant find a place to purchase a RIFF box, so im kinda trying to avoid hard bricking my 2nd device today
http://www.ort-jtag.com/ you can order them for 150.00 usd plus shipping.
Sent from my One X using xda premium
You'll have to wait until 3.18 root is achieved then unfortunately as you cannot change your CID in your phone's current state.
For future reference, don't bother relocking the bootloader after achieving s-off on this phone. It's pointless and creates issues like this.
exad said:
You'll have to wait until 3.18 root is achieved then unfortunately as you cannot change your CID in your phone's current state.
For future reference, don't bother relocking the bootloader after achieving s-off on this phone. It's pointless and creates issues like this.
Click to expand...
Click to collapse
okay but to verify i am s-off if i flash the unlock token what are the chances of a brick? mainly asking because i am wanting to do the 3 button remap mod and the new elemental kernel as well and only reason i relocked the bootloader and ran the JB ruu is because my basebands all except for lte kept losing signal at random
Can he not write a different cid since he's s off?
a box of kittens said:
Can he not write a different cid since he's s off?
Click to expand...
Click to collapse
Apparently not. Which doesn't surprise me as there are many things I could not do with s-off and a locked bootloader. This seems to be a quirk of the one xl
Can't he fastboot oem writecid if he's already supercid tho
Sent from my VENOMized HoxL
area51avenger said:
Can't he fastboot oem writecid if he's already supercid tho
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Read the OP. He says it errors when trying to write a new cid.
Sent from my HTC One X using xda premium
With the evita, s-off + super cid is not enough, you require an unlocked bootloader aswell.
I cannot boot into ROM, but stuck at Bootloader. And I'm relocked.
The only thing I have is Fastboot USB.
I would like to RUU into a Stock ROM. How to do so?
Well ruu should be pretty self explanatory. If you are in the boot loader just run the ruu. Since you are relocked shouldn't take much work. Are you s-off? Why not just grab an AT&T ROM and flash it over. Sure it will be rooted, but delete the super user app
Sent from my Carbon-ize Evita using xda-developers app
Yeah, I just figured it. RUU was some executable file. I thought it was more complicated. No I'll just leave it like this and not S-Off, thanks. Apparently I'm not more than 30% battery though. But how do I see the battery from the Bootloader screen?
I dont believe you can. Only from recovery. Just let it charge for about 20-30 mins and you should be good
Sent from my Carbon-ize Evita using xda-developers app
If you have supercid and s-on running a ruu will brick your phone just a warning
Sent from my HTC One X using Tapatalk 2
How do I check if I have SuperCID or not?
And apparently the device name is GT-9100 which seems wrong...?
There is command in fastboot I think it is fastboot get cid but not sure do you have a att phone
Sent from my HTC One X using Tapatalk 2
Nope, I do not. I do not need to worry about that then.
No you should be ok att phones are the only ones that had to change there cids to unlock bootloader
Sent from my HTC One X using Tapatalk 2
Fastboot oem readcid
Sent from my One X using xda app-developers app
exad said:
Fastboot oem readcid
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Thanks couldn't remember what it was
Sent from my HTC One X using Tapatalk 2
Oh no! Can anyone please help me?
None of the RUUs work.
I'm Asian and I tried all:
1.88.707.2 ( Error 170, bad USB )
2.23.707.2 ( Error 170 )
This is the only one that I could select ROM and upgrade.
3.17.707.1 ( Less than 30% error is result of previous fail, so reboot. Actual Error 155 )
And I'm S-ON
hboot 1.09
radio 0.17a.32.09.16_2
OpenDSP - What's this and is it useful for my situation?
eMMC - boot
Apr 2 2012, 21:08:21
I think probably I can only install 3.17 RUU is because my last working ROM was CM10.1. After that I tried Sense ROMs but many failed hence I thought of doing Relock and RUU.
Is there any other thing I can do in my bootloader state? I tried Factory Reset.
Is it possible I attain S-OFF from here and flash recovery and flash OTA from there?
Or even better yet, can I try doing OTA from this state?
Aerodeath said:
And I'm S-ON
hboot 1.09
radio 0.17a.32.09.16_2
OpenDSP - What's this and is it useful for my situation?
eMMC - boot
Apr 2 2012, 21:08:21
I think probably I can only install 3.17 RUU is because my last working ROM was CM10.1. After that I tried Sense ROMs but many failed hence I thought of doing Relock and RUU.
Is there any other thing I can do in my bootloader state? I tried Factory Reset.
Is it possible I attain S-OFF from here and flash recovery and flash OTA from there?
Or even better yet, can I try doing OTA from this state?
Click to expand...
Click to collapse
I thought if you ran the ruu with s on you could brick...just obtain s off and then run the ruu
Sent from my Carbon-ize Evita using xda-developers app
I can't successfully S-OFF because I can't get into Android, stuck at bootloader.
And I'm not on AT&T, I don't need superCID and I can't change it to 11111111 either...
My CID is HTC__044
version-main is 1.88.707.2
Bootloader relocked
hBoot now 2.14?!
RUU_Evita_UL_hTC_Asia_WWE_1.88.707.2_R3_Radio_0.17a.32.09.16_2_10.88.32.17L_release_263455_signed should work but it didn't...
Never mind, everything seems to be working now.
It seemed that my hboot was too low to attempt RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_Radio_0.23a.32.09.29_10.128.32.34a_release_298958_signed and Running as Administrator helped too.
Aerodeath said:
I can't successfully S-OFF because I can't get into Android, stuck at bootloader.
And I'm not on AT&T, I don't need superCID and I can't change it to 11111111 either...
My CID is HTC__044
version-main is 1.88.707.2
Bootloader relocked
hBoot now 2.14?!
RUU_Evita_UL_hTC_Asia_WWE_1.88.707.2_R3_Radio_0.17a.32.09.16_2_10.88.32.17L_release_263455_signed should work but it didn't...
Never mind, everything seems to be working now.
It seemed that my hboot was too low to attempt RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_Radio_0.23a.32.09.29_10.128.32.34a_release_298958_signed and Running as Administrator helped too.
Click to expand...
Click to collapse
I'm telling you this because I don't want you to go through what I did.
I'm on a telus one x, did not need super cid to unlock my bootloader. I relocked and flashed stock recovery, ran RUU. The RUU completed successfully but my phone was a full brick. Only JTAG would have saved it.
If you want to RUU, re-unlock your bootloader, flash recovery, flash stock rooted sense rom, hex edit your CID to 11111111 and S-OFF, then RUU. It's a lot safer now that you've unlocked your bootloader and rooted.
exad said:
I'm telling you this because I don't want you to go through what I did.
I'm on a telus one x, did not need super cid to unlock my bootloader. I relocked and flashed stock recovery, ran RUU. The RUU completed successfully but my phone was a full brick. Only JTAG would have saved it.
If you want to RUU, re-unlock your bootloader, flash recovery, flash stock rooted sense rom, hex edit your CID to 11111111 and S-OFF, then RUU. It's a lot safer now that you've unlocked your bootloader and rooted.
Click to expand...
Click to collapse
It's okay, I was running an international One XL, and luckily RUU was smooth, now the problem is solved and my phone has been sold and changed hands .
I have a One XL with o2 Germany Branding (CID: O2___102)
HBOOT 2.14
S-ON
ROM installed: CM 10.1
I want to relock it and flash a Stock ROM. Reason is that I want to send it to warranty.
As far as I know the HBOOT of the ROM must not be older than 2.14 and I can't find an appropriate ROM.
1. fastboot oem lock
2. launch RUU (I tried some, but it did't work)
Do I have to flash a Stock Recovery after that?
Running an RUU returns the phone to being completely stock, including recovery. I hope your don't have SuperCID or you're gonna brick. Click the link in my signature, you'll find RUU threads there.
Sent from my Evita
timmaaa said:
Running an RUU returns the phone to being completely stock, including recovery. I hope your don't have SuperCID or you're gonna brick. Click the link in my signature, you'll find RUU threads there.
Sent from my Evita
Click to expand...
Click to collapse
And what if none of these RUUs work?
O2:
OTA_EVITA_UL_JB_45_S_O2_DE_3.17.207.1_0.23a.32.09. 29_10.128.32.34a_release_2990766qakrzbj4mpslnsy.zi p
OTA_EVITA_UL_ICS_40_S_O2_DE_2.29.207.1-1.92.207.3_release_272963z2vl7cdycjk01nm4.zip
fly23 said:
And what if none of these RUUs work?
O2:
OTA_EVITA_UL_JB_45_S_O2_DE_3.17.207.1_0.23a.32.09. 29_10.128.32.34a_release_2990766qakrzbj4mpslnsy.zi p
OTA_EVITA_UL_ICS_40_S_O2_DE_2.29.207.1-1.92.207.3_release_272963z2vl7cdycjk01nm4.zip
Click to expand...
Click to collapse
Those are ota updates... A ruu is an exe file that is run from Windows
Sent from my HTC One XL using xda app-developers app
The available o2 RUUs are too old
Sent from my One X using Tapatalk 4
So you run an older RUU and then take OTAs, you can't just flash OTA files, it won't work. You need to return the phone to being completely stock first though, s-on, original CID, locked bootloader, original recovery.
Sent from my Evita
I tried this file: RUU_EVITA_UL_ICS_40_S_O2_DE_2.29.207.1_Radio_0.19as.32.09.20_3_10.107.32.25L_release_272946_signed.exe, it didn't work (contentual: Error 170, USB Error)
The XL is S-ON (never was S-OFF), bootloader is relocked (fastboot oem lock), then I launched the RUU.exe.
What I read is, that I can't flash older ROMs (what ever that means). So, what can I do if the o2-RUUs are to old? Can I downgrade the HBOOT?
edit: Can I downgrade HBOOT with the JET (http://forum.xda-developers.com/showthread.php?t=1940512) and then ran a RUU?