How to completely return to stock - HTC One S

Okey so I have tried CM10 and CM10.1 and I don't like the bad internet performance.
So I want to return to stock, I restored my nandroid from the JellyBean 4.5 latest update.
But now I want to S-ON, un-Supercid, and relock my bootloader so I can use the OTA's again.
Can anybody help me with the steps? I just don't want to risk bricking my phone
I already downloaded the RUU for JellyBean but it's one version older as I already have now.
Ps. I have an unlocked european HTC One S S4.
Ps 2. I also know how to do all these steps, but I need the order for them.
Thanks!

Okey so from what I have found I only need to
Put Original CID back > Relock bootloader and flash RUU. is this correct?

jeantje said:
Okey so from what I have found I only need to
Put Original CID back > Relock bootloader and flash RUU. is this correct?
Click to expand...
Click to collapse
if you are on s-off you dont have to relock your bootloader, just boot your phone into fastboot, connect it to your pc and run the ruu as usual.
if you want to get otas change your supercid to a normal one like HTC__001.
for installing ota you should be on stock recovery, which will be automatically flashed if you run the ruu, no need for s-on or relocked bootloader.

To change CID use this command in a adb environment
fastboot oem writecid then whatever CID you need
Sent from my HTC One S using the xda-developers app

NQNH said:
if you are on s-off you dont have to relock your bootloader, just boot your phone into fastboot, connect it to your pc and run the ruu as usual.
Click to expand...
Click to collapse
Are you sure about this? I thought you needed to relock for the RUU to work.
Thanks

nor-ric said:
Are you sure about this? I thought you needed to relock for the RUU to work.
Thanks
Click to expand...
Click to collapse
Not when your s-off
Verstuurd van mijn One S met Tapatalk
---------- Post added at 09:02 PM ---------- Previous post was at 08:56 PM ----------
jeantje said:
Okey so from what I have found I only need to
Put Original CID back > Relock bootloader and flash RUU. is this correct?
Click to expand...
Click to collapse
You forgot stock recovery. Flash manual or use ruu before relock.
There is no reason to sonn again just for ota. They work with soff
There is a good topic in dev section to go from soff unlocked to completly stock sonn locked if you really want it.
I advise only to go back sonn if returning it for warranty or such
Verstuurd van mijn One S met Tapatalk

Related

RUU or a backup TMOB-101

Hi, I really f up.
I can't install roms, and I got TMOB-101.
I tried recently flash a new rom. and didn't backed it up.
please someone send me TMOB-101 backup ot RUU.
HELP!
if you've unlocked your hboot, you need to relock it and then you can install a RUU.
http://www.htconeforum.com/forum/ht...unbrick-restore-htc-one-s-stock-relocked.html
Good luck
No ruu for me there
Sent from my HTC One S using Tapatalk 2
Do you have the TMo USA?
No. I've got t-mob101 (t-mobile Germany)
Sent from my HTC One S using Tapatalk 2
try this:
http://androidfiles.org/ruu/?dir=Ville
Tried this already...
No ruu
Sent from my HTC One S using Tapatalk 2
RUU_Ville_U_TMO_DE_1.77.111.5_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_259421_signed.exe
Really not?
It's a early ruu. I need the 3.16 one
Sent from my HTC One S using Tapatalk 2
lol. There isn't one from TMOB_101 and I really doubt that there ever will be one...
If you want to stick to your CID you should flash this one above and check the OTA updates. Things can be soooo easy...
If you want to go for JB you'll have to change CID to HTC__001 and flash the appropriate RUU. 3.16 will come in by OTA update.
Isn't it will brick my device? (flashing a earlier version then I got)
Sent from my HTC One S using Tapatalk 2
No, it will simply not flash (= exit with an error).
Each RUU/OTA update comes with a certain new bootloader version. Dependant on this version you can upgrade to the next higher hboot but usually not downgrade to a lower hboot. E.g. if youre on 2.15 JB you can't downgrade to 1.14 ICS by RUU anymore. But you are still able to flash custom roms based on whatever android version. The only thing here is with bootloaders > 1.09 the kernel needs to be flashed separately in fastboot mode.
That's where s-off / downgrading bootloader comes into game. As downgrading bootloader is a pain, s-off would be the way to go. For warranty purposes you will be able to restore a stock phone (locked, tampered warning removed, s-on). And if your screen is blank, it will also be blank for TMOB, so there is no need to restore stock.
Look here: http://forum.xda-developers.com/showthread.php?t=2200930
There is the "RUU_Ville_U_ICS_40_S_TMO_DE_2.38.111.10_Radio_1.09 es.50.02.07_2_10.09d.50.04L_ver2_release_287723_signed.exe"
(Android 4.04 version)
rootrider said:
No, it will simply not flash (= exit with an error).
Each RUU/OTA update comes with a certain new bootloader version. Dependant on this version you can upgrade to the next higher hboot but usually not downgrade to a lower hboot. E.g. if youre on 2.15 JB you can't downgrade to 1.14 ICS by RUU anymore. But you are still able to flash custom roms based on whatever android version. The only thing here is with bootloaders > 1.09 the kernel needs to be flashed separately in fastboot mode.
That's where s-off / downgrading bootloader comes into game. As downgrading bootloader is a pain, s-off would be the way to go. For warranty purposes you will be able to restore a stock phone (locked, tampered warning removed, s-on). And if your screen is blank, it will also be blank for TMOB, so there is no need to restore stock.
Click to expand...
Click to collapse
I've got the same Problem.
But I can't SuperCID / S-Off my Phone like here: http://forum.xda-developers.com/showthread.php?t=1671396
It just doesn't work!!!
How could I go back to a Stock ROM ??
I have really no idea
TMOB-101 ?
Which bootloader version?
rootrider said:
TMOB-101 ?
Which bootloader version?
Click to expand...
Click to collapse
hboot-2.15.0000
Golden-One said:
I've got the same Problem.
But I can't SuperCID / S-Off my Phone like here: http://forum.xda-developers.com/showthread.php?t=1671396
It just doesn't work!!!
How could I go back to a Stock ROM ??
I have really no idea
Click to expand...
Click to collapse
I can sent you a twrp nandroid backup from my phone (s4-tmobile germany)
I have backups from the 3.16.111.5.and from the latest 3.16.111.7. They are the stock roms with the supersu added.
If you recover the 3.16.111.5 nandroid backup you will take a OTA update to clean 3.16.111.7 (without supersu).
hi
Can you send me the backups too?
thank you so much!
kevin3688 said:
hi
Can you send me the backups too?
thank you so much!
Click to expand...
Click to collapse
You can find it/them here.
It's just plain stock nandroids. No root - nothing.
rootrider said:
You can find it/them here.
It's just plain stock nandroids. No root - nothing.
Click to expand...
Click to collapse
Thanks a lot!

[Q] Can't update firmware, Unlocked/Tampered S-ON

I want to be able to flash the latest CM10.1 for my AT&T HTC One X. Details about the phone-
Unlocked with HTCDev. Hboot 1.14.0002. Have latest TWRP flashed. Says TAMPERED, UNLOCKED, and S-ON.
I tried a RUU to update the Hboot, but that didn't work.
How can I update the firmware so I can run latest ROMs like CM10.1? I've looked at similar questions, but the answers were for the International Version of the HTC One X.
Any help or suggestions are appreciated.
seth50k said:
I want to be able to flash the latest CM10.1 for my AT&T HTC One X. Details about the phone-
Unlocked with HTCDev. Hboot 1.14.0002. Have latest TWRP flashed. Says TAMPERED, UNLOCKED, and S-ON.
I tried a RUU to update the Hboot, but that didn't work.
How can I update the firmware so I can run latest ROMs like CM10.1? I've looked at similar questions, but the answers were for the International Version of the HTC One X.
Any help or suggestions are appreciated.
Click to expand...
Click to collapse
S-off
Run 3.18 ruu (no need to relock with s-off)
Relash recovery
Flash cm10
Sent from my HTC One XL using xda premium
31ken31 said:
S-off
Run 3.18 ruu (no need to relock with s-off)
Relash recovery
Flash cm10
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Ok, so here's the 2nd question. Somehow I managed to wipe whatever ROM I had on here (CleanROM I think), so it doesn't boot to anything. I've tried flashing CleanROM 6 and 3.20.401.1 Odexed, both error out in TWRP.
I'm assuming I've managed to softbrick it?
seth50k said:
Ok, so here's the 2nd question. Somehow I managed to wipe whatever ROM I had on here (CleanROM I think), so it doesn't boot to anything. I've tried flashing CleanROM 6 and 3.20.401.1 Odexed, both error out in TWRP.
I'm assuming I've managed to softbrick it?
Click to expand...
Click to collapse
Not sure 3.20.401.1 is but what did you do? You didn't do factory reset from bootloader did you?
RollTribe said:
Not sure 3.20.401.1 is but what did you do? You didn't do factory reset from bootloader did you?
Click to expand...
Click to collapse
I might have. What I was trying to do is clean out the phone to sell it, then get it updated, etc. I know in TWRP I ran probably every type of wipe, and I may have run Factory reset from the bootloader. It was a while ago and I set it aside, and now i've come back to it trying to get this phone sorted out.
seth50k said:
I might have. What I was trying to do is clean out the phone to sell it, then get it updated, etc. I know in TWRP I ran probably every type of wipe, and I may have run Factory reset from the bootloader. It was a while ago and I set it aside, and now i've come back to it trying to get this phone sorted out.
Click to expand...
Click to collapse
If you did, then you're not gonna be able to so anything with ROMs. Run an ruu, reunlock, and report back.
RollTribe said:
If you did, then you're not gonna be able to so anything with ROMs. Run an ruu, reunlock, and report back.
Click to expand...
Click to collapse
I've tried running RUU, it gets about halfway and fails. Do I need to flash the stock recovery and relock first, then run a RUU?
U need to relock the bootloader
Use command prompt
"Fastboot oem lock" from fastboot then run the ruu.... I recommend getting s-off as well is very easy and fast and it will save u a lot of troubles in the future plus u will not have to lock the bootloader to flash an ruu
Sent from my HTC One X using xda premium
If you ruu with s-on and supercid you brick.
Be careful with your advice breeze. You'll cause him a brick.
Sent from my One X using xda app-developers app
breezedragon said:
U need to relock the bootloader
Use command prompt
"Fastboot oem lock" from fastboot then run the ruu.... I recommend getting s-off as well is very easy and fast and it will save u a lot of troubles in the future plus u will not have to lock the bootloader to flash an ruu
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yeah, but you need a ROM working to even do the s-off process. So getting a ROM loaded is my main priority at this point. I can get into Bootloader/Fastboot, and I can still get to TWRP. Flashing a ROM from TWRP isn't working, and neither is running the latest RUU from fastboot. I get ERROR 159 when I try to run the latest RUU. So do I need to fastboot oemlock, then try again?
Perhaps running the RUU that was previously on it would work? 2.20, is what firmware was on it last.
seth50k said:
Yeah, but you need a ROM working to even do the s-off process. So getting a ROM loaded is my main priority at this point. I can get into Bootloader/Fastboot, and I can still get to TWRP. Flashing a ROM from TWRP isn't working, and neither is running the latest RUU from fastboot. I get ERROR 159 when I try to run the latest RUU. So do I need to fastboot oemlock, then try again?
Perhaps running the RUU that was previously on it would work? 2.20, is what firmware was on it last.
Click to expand...
Click to collapse
Yeah, you have to run the same/later ruu if you're not S-Off. And you'll have to relock and you can flash stock recovery to be safe (but I think it flashes for you).
---------- Post added at 02:12 PM ---------- Previous post was at 02:11 PM ----------
exad said:
If you ruu with s-on and supercid you brick.
Be careful with your advice breeze. You'll cause him a brick.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
That's not necessarily true, I've ruu'ed with s-on and SuperCID and was fine. It is risky, though.
Unlock, flash a sense rooted rom, soff and then ruu up to 3.18
Sent from my One X using xda app-developers app
RollTribe said:
Yeah, you have to run the same/later ruu if you're not S-Off. And you'll have to relock and you can flash stock recovery to be safe (but I think it flashes for you).
---------- Post added at 02:12 PM ---------- Previous post was at 02:11 PM ----------
That's not necessarily true, I've ruu'ed with s-on and SuperCID and was fine. It is risky, though.
Click to expand...
Click to collapse
I'm able to run the 2.20 RUU so far after relocking, it's about 3/4 of the way done. After this i'll try the latest RUU, then go from there to re-unlock, then S-OFF, THEN reflash TWRP?
seth50k said:
I'm able to run the 2.20 RUU so far after relocking, it's about 3/4 of the way done. After this i'll try the latest RUU, then go from there to re-unlock, then S-OFF, THEN reflash TWRP?
Click to expand...
Click to collapse
Yup, you can swap the last two if you want
RollTribe said:
Yup, you can swap the last two if you want
Click to expand...
Click to collapse
Well shoot...got so close. 2.20 RUU worked, then I did the latest RUU, which completed fine, but now the phone won't turn on, and won't even show a red LED charging indicator. WTF...
seth50k said:
Well shoot...got so close. 2.20 RUU worked, then I did the latest RUU, which completed fine, but now the phone won't turn on, and won't even show a red LED charging indicator. WTF...
Click to expand...
Click to collapse
Yep, looks like it's bricked. http://forum.xda-developers.com/showthread.php?t=2181929
seth50k said:
Well shoot...got so close. 2.20 RUU worked, then I did the latest RUU, which completed fine, but now the phone won't turn on, and won't even show a red LED charging indicator. WTF...
Click to expand...
Click to collapse
Yeah, you have to s-off before running latest ruu. Damn sorry if I was unclear man.
RollTribe said:
Yeah, you have to s-off before running latest ruu. Damn sorry if I was unclear man.
Click to expand...
Click to collapse
It's alright, just a little surprised given the fact that HTC allows you to unlock and such, but their own RUU bricks the phone if in such a state.
I think it might be under warranty still, might try that route. Thanks for the help.
Sorry about your phone. It's Jtagg or new phone.
---------- Post added at 02:34 PM ---------- Previous post was at 02:34 PM ----------
seth50k said:
It's alright, just a little surprised given the fact that HTC allows you to unlock and such, but their own RUU bricks the phone if in such a state.
I think it might be under warranty still, might try that route. Thanks for the help.
Click to expand...
Click to collapse
They state on their site that after unlocking the bootloader, RUU/OTA could brick you.
If you plan to try warranty with HTC, do not mention that you unlocked. They will charge you 200 straight up no matter what you say.
RollTribe said:
That's not necessarily true, I've ruu'ed with s-on and SuperCID and was fine. It is risky, though.
Click to expand...
Click to collapse
But was it the 3.18? It applies specifically for the AT&T 3.18 (and for some 3.17 JB RUUs on other carriers, and reported by some folks on this forum).
If you were able to run the 3.18 RUU successfully with SuperCID and S-on, I believe this is the first I've heard of it.
---------- Post added at 12:37 PM ---------- Previous post was at 12:33 PM ----------
seth50k said:
It's alright, just a little surprised given the fact that HTC allows you to unlock and such, but their own RUU bricks the phone if in such a state.
Click to expand...
Click to collapse
SuperCID as implemented on the AT&T One X is a mod/hack, and therefore not explicitly "allowed" by HTC. They can't really be held responsible for the effects of it.
SuperCID shouldn't be "expected" to brick under these conditions (worked fine with pre-JB RUUs), and nobody here has really been able to explain exactly why the phone bricks from SuperCID. But unfortunately, it does.

ruu stock rom????

my phone run "villec2-jb-4.1.1-deodexed" i down ruu som and run but it faill 155, phone show hboot orlder?????? ruu is ics
who can help me fixx??? thank!!! so much sorry bad english
daothuan said:
my phone run "villec2-jb-4.1.1-deodexed" i down ruu som and run but it faill 155, phone show hboot orlder?????? ruu is ics
who can help me fixx??? thank!!! so much sorry bad english
Click to expand...
Click to collapse
relock your bootloader before you run the RUU
tivofool said:
relock your bootloader before you run the RUU
Click to expand...
Click to collapse
i did, but it faillll have tips ??????
daothuan said:
i did, but it faillll have tips ??????
Click to expand...
Click to collapse
is there a newer RUU that you can run on your device?
http://forum.xda-developers.com/showthread.php?t=2094414
The only tips that I have are
put back stock recovery on your phone if you have changed it. (you will have to unlock bootloader to do this)
relock bootloader.
OH, and one time even though usb debugging was checked on the phone, I had to uncheck it and check it again before the ruu worked.
Will relocking bootloader automatically restore stock recovery? Cause I am trying to return to stock from S-off back to S-on and I am following this guide but in the HTC One S toolkit, the recovery section doesn't have a stock recovery to flash. I can use some help with this also, I want to see if returning phone to stock will fix signal drop issues and if not I will have to return it on insurance. My biggest problems are I do not have an RUU from my carrier so could use some advice as to which one to use? here is the link for RUU's but there isn't one for Cincinnati Bell wireless.
You need S-OFF
Sent from my Nexus 7 using Tapatalk HD

[Q] Relock Bootloader - Fido

Hi,
I want to know if in case I want to relock my bootloader, what's the RUU for? and how can I find one for my carrier? I'm with Fido (Canada), I'm s-on, hboot 2.15, rooted and running CarbonRom. I have the stock OS backup on my pc, and I was reading the steps to go back to stock with a locked bootloader.
Thanks
lucasmedaffy said:
I am on Fido and recently soft-bricked my phone.
I just went back to stock using the OTA ROGERS JB RUU (I found it online). It was a bit more complicated because the OTA zip doesn't have a RUU utility to flash it. There is a thread that will walk you through the steps; XDA's search is down or I would locate it. It took a bit of time but worked.
Click to expand...
Click to collapse
So you say the Rogers RUU will work? and I must use the ruu to lock the bootloader right?
Thanks!
elias.acab said:
So you say the Rogers RUU will work? and I must use the ruu to lock the bootloader right?
Thanks!
Click to expand...
Click to collapse
If you just want to relock the bootloader you can use fastboot
Code:
fastboot oem lock
But, this is probably not what you want to do, right?
RUU = ROM UPGRADE UTILITY. It's an .exe file that lets you install the stock rom on your phone. The RUU needs to match your hboot (and carrier). Get the RUU here:
http://www.androidruu.com/index.php?developer=Ville
Requirements:
- min 30% battery
- HTC drivers installed (devices is recognized by windows)
- USB debugging enabled
- Charging only mode
Hope this helps.
Thank you guys for that!! Theres something I still dont get, and its if I got the backup of the stock os (I dont really wanna relock the bootloader), I dont need the ruu right? But if I want to install the stock os and relock the bootloader (without using the backup) I do need the ruu, am I right?
Thanks
Sent from my One S
lucasmedaffy said:
I followed these instructions: http://forum.xda-developers.com/showthread.php?t=2394165
and I used this RUU: http://www.androidfiles.org/ruu/get....27.50.08L_release_301897nn5lu23br8cg9q7l.zip
Unfortunately I couldn't use the older RUU because they were for ICS (IceCream Sandwich), not JB (JellyBean) and wouldn't install. As I mentioned, it is a few more hoops but the directions are very clear and it worked for me.
Good luck!
EDIT: If you just want to relock your bootloader, you can follow the above step (which is part of flashing the RUU and included in the instructions in the thread I linked to). If you want to reflash stock, follow the full instructions.
Click to expand...
Click to collapse
Thank you guys so much for that!! Theres something I still dont get, and its if I got the backup of the stock os (I dont really wanna relock the bootloader), I dont need the ruu right? But if I want to install the stock os and relock the bootloader (without using the backup) I do need the ruu, am I right? The Ruu installs the stock os for me?
Thanks, and sorry for asking too many questions
Sent from my One S
elias.acab said:
Hi,
I want to know if in case I want to relock my bootloader, what's the RUU for? and how can I find one for my carrier? I'm with Fido (Canada), I'm s-on, hboot 2.15, rooted and running CarbonRom. I have the stock OS backup on my pc, and I was reading the steps to go back to stock with a locked bootloader.
Thanks
Click to expand...
Click to collapse
Your Stock backup will work (you will also need to fastboot flash the boot.img if you are S-ON) to bring you back to your stock ROM.
RUU does that and a whole lot more that a simple backup can do.
Such as:
HBoot
Returns to stock recovery (which in turn will allow to correct partitions and fix unmountable sdcard)
Radio update
Boot.img
Splash screen
Or you could say it updates: Boot/System/Data/Recovery/Radio
---------- Post added at 05:05 PM ---------- Previous post was at 04:55 PM ----------
elias.acab said:
Thank you guys so much for that!! Theres something I still dont get, and its if I got the backup of the stock os (I dont really wanna relock the bootloader), I dont need the ruu right? But if I want to install the stock os and relock the bootloader (without using the backup) I do need the ruu, am I right? The Ruu installs the stock os for me?
Thanks, and sorry for asking too many questions
Sent from my One S
Click to expand...
Click to collapse
If you run your backup and then relock the bootloader, The bootloader will still say "tampered" I believe. This is because the modified recovery will still be there. You would need to unlock the bootloader and flash stock recovery to remove the "tampered" (i think)
So yeah, theoretically it will be just like running a RUU, if you restore your backup, fastboot flash boot.img, flash stock recovery. (assuming you haven't changed radio or hboot)
tivofool said:
Your Stock backup will work (you will also need to fastboot flash the boot.img if you are S-ON) to bring you back to your stock ROM.
RUU does that and a whole lot more that a simple backup can do.
Such as:
HBoot
Returns to stock recovery (which in turn will allow to correct partitions and fix unmountable sdcard)
Radio update
Boot.img
Splash screen
Or you could say it updates: Boot/System/Data/Recovery/Radio
---------- Post added at 05:05 PM ---------- Previous post was at 04:55 PM ----------
If you run your backup and then relock the bootloader, The bootloader will still say "tampered" I believe. This is because the modified recovery will still be there. You would need to unlock the bootloader and flash stock recovery to remove the "tampered" (i think)
So yeah, theoretically it will be just like running a RUU, if you restore your backup, fastboot flash boot.img, flash stock recovery. (assuming you haven't changed radio or hboot)
Click to expand...
Click to collapse
Thank you again, I really appreciate it!!, I totally get it now I'll make sure I re-read these steps when I feel like I wanna go back to stock.

[Q] Unable to get in to recovery or install CWM or TWRP

I'm trying to update a phone I haven't used for a while with a newer ROM, but I'm not able to get in to recovery to do it. It's already rooted with an old ViperOne ROM on and I thought it already had CWM on., but Flashify is telling me it has the stock recovery. I've tried installing CWM and TWRP via Flashify and Fastboot and they've completed without any errors, but I'm never able to get in to it and it boots as normal. I can't even get in to the stock recovery that's supposedly there.
Does anyone have any idea what the problem might be?
Thanks.
Well try this.
Download Rom Manager
It wil flash the CWM by itself and then reboot into the Recovery. Notice what happens.
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
If Helped Click Thanks...
I've tried that too, still just reboots as normal.
Then it might be a Dead Recovery. Well which device are you using. And maybe Flashing your Device back to stock which would flash back the stock recovery.
Hope This Works ..!
---------- Post added at 05:14 PM ---------- Previous post was at 05:12 PM ----------
Tell me wgich device are you using.
HTC One S S4 running Android 4.0.4 ICS
mrkwtrs said:
HTC One S S4 running Android 4.0.4 ICS
Click to expand...
Click to collapse
As first step you should flash the latest JellyBean RUU which will also upgrade your bootloader to 2.15. If your phone is "S-ON" you will have to relock the bootloader before running the RUU. Once done your phone should be fully working again so you can unlock the bootloader again and flash the latest TWRP recovery.
For getting the matching RUU you need to check your CID. Connect your phone in fastboot mode, open commandline and typ:
fastboot getvar all
LS.xD said:
As first step you should flash the latest JellyBean RUU which will also upgrade your bootloader to 2.15. If your phone is "S-ON" you will have to relock the bootloader before running the RUU. Once done your phone should be fully working again so you can unlock the bootloader again and flash the latest TWRP recovery.
For getting the matching RUU you need to check your CID. Connect your phone in fastboot mode, open commandline and typ:
fastboot getvar all
Click to expand...
Click to collapse
OK, Bootloader relocked, back to S-On, CID reset to O2___001.
Would you agree that the RUU is the 7th one down in this list?
mrkwtrs said:
OK, Bootloader relocked, back to S-On, CID reset to O2___001.
Would you agree that the RUU is the 7th one down in this list?
Click to expand...
Click to collapse
NO! You were S-OFF? That made life easier. Unbranded EU firmware is fine BUT I suppose you cant flash it now, as you reverted the CID...
I said, IF you're S-ON...
Best way is get S-OFF again via rumrunner.us, change CID to HTC__001 and then flash the RUU you mentioned before
LS.xD said:
NO! You were S-OFF? That made life easier. Unbranded EU firmware is fine BUT I suppose you cant flash it now, as you reverted the CID...
I said, IF you're S-ON...
Best way is get S-OFF again via rumrunner.us, change CID to HTC__001 and then flash the RUU you mentioned before
Click to expand...
Click to collapse
Just seen an O2 UK RUU further down the list so I'll try that.
mrkwtrs said:
Just seen an O2 UK RUU further down the list so I'll try that.
Click to expand...
Click to collapse
Ok, give it a try, you should go S-OFF anyway as you need HBOOT 2.15 if you want to use roms newer than ICS.
LS.xD said:
Ok, give it a try, you should go S-OFF anyway as you need HBOOT 2.15 if you want to use roms newer than ICS.
Click to expand...
Click to collapse
Think I'm all sorted. Thanks for your help! :good:

Categories

Resources