So I'm currently running Cyanogenmod 11 nightly 12/31/2014, and I want to get S-Off for my the HTC One S so that I don't have to flash the boot.img every time that I update roms.
I don't know a whole lot about S-Off, and I figured that this would be the right place to get information. Should there be a problem with me having CM11 installed on this device, If so, how would I get around this issue (I read on the Moonshine.io page that I needed the correct firmware, and for my device on T Mobile, it was 3.14.531.11)
Also, a general guide for S-Off would be appreciated too.
-Thanks
Related
Hey guys, I'd like to root and S-OFF my HTC desire s. Which is the best way? The only thing I've done to my phone since I own it is install the official ruu running ICS.
bubi90 said:
Hey guys, I'd like to root and S-OFF my HTC desire s. Which is the best way? The only thing I've done to my phone since I own it is install the official ruu running ICS.
Click to expand...
Click to collapse
Do yourself a favour and read the stickies in the Dev forum, then search the DS forums as this question has been asked and answered countless times already. You need to know and understand what you are doing and why or you risk getting yourself into a situation you will struggle to get out of.
I'm not an absolute beginner. I've already rooted and S-OFF my previous phone, the HTC Desire. I know what I am going to do.
I just wanted to know if the procedure to root this ics ruu is the same as before.
Thanks
If you know what you're going to do - then do it.
If you don't - read the stickies.
This thread is a waste of time, yours and others'.
You cannot S-OFF the default ICS RUU hboot - for that, you will need to downgrade to an older hboot (0.98.x) by flashing an older RUU for your phone (there are threads around here that will let you know how to do that) and then S-OFF.
However, you do not need to S-OFF to root the ICS rom - you only need to unlock the bootloader through htcdev.com. Keep in mind that this voids the warranty. After you unlock the blootloader, you can flash a custom recovery via fastboot commands (search the forum) and then flash the SU (or SuperSU) binary and app in recovery. That's exactly what I had done as soon as the ICS RUU came out. This is hardly a detailed guide, but it's a starting point, good luck.
Alrighty, so, there's a ridiculous amount of confusion about upgrading to 3.4-kernel-based ROMs, and I need some serious help here to make sure I don't brick my phone. I cant be getting a new one right now.
Anyways, basic info of what I've got:
- T-Mobile One S (launch day model)
- hboot 1.06
- 0.16 radio running currently
- CM 10.1 nightly 0607 (June 7th) - Android 4.2.2
- Kernel version 3.0.80
- S-OFF, CID 111111 (however many ones it is, and I S-OFF'd it using the original guide when S-OFF was just initially figured out)
Question: What on Earth do I need to flash and not flash in order to get to 10.2? I rooted my phone the 2nd day I had it, and have never gone back to an official HTC ROM, and I'm 100% sure that I haven't performed any firmware updates outside of flashing CM or ViperS roms.
The official 10.2 build came out today, and I'm anxious to get updated, but scared as hell that I'm gonna brick it, because these guides on which firmware to flash are confusing, and some of the files' links are broken.
Any help would be greatly appreciated. I'm more than capable of following technical instructions, and am plenty familiar with adb and fastboot, it's just that I'm really not sure which things I need to flash and which I DONT.
Thanks XDA.
Follow this thread!
http://forum.xda-developers.com/showthread.php?t=2322755
So I'm probably asking a question that's been asked many times before.. I have the dreaded HTC One X from AT&T. I keep getting references toward the XL, and mine seems to fit the profile as a dual core LTE phone. Anyways, I am dealing with CWS_001 CID and HBOOT 1.14 and would like to upgrade my OS to either stock Jelly Bean or CyanogenMod (this would be my preference) or if someone has a BETTER suggestion than I am open to a better mod. I have seen a few really catchy ones like MAXIMUS that I wanted to try. I have achieved unlocking, rooting, and S-OFF on this device already. After those processes.. my phone downloaded a large system update from AT&T which was Jelly Bean. It will not allow it to install. I presume this is because my device isn't actually approved for that update and something I did in this whole process triggered the server into believing I should have gotten it..
So is there a way for me to update my HBOOT for CyanogenMod or some other form of an upgraded version of Android?
I am currently running:
Android Version 4.0.4
Sense Version 4.0
Software Number 2.20.502.7.710RD
SDK API Level 4.23
Kernel 3.0.8-01558
Anyone out there able to point me in the right direction? Thanks!
acw928 said:
So I'm probably asking a question that's been asked many times before.. I have the dreaded HTC One X from AT&T. I keep getting references toward the XL, and mine seems to fit the profile as a dual core LTE phone. Anyways, I am dealing with CWS_001 CID and HBOOT 1.14 and would like to upgrade my OS to either stock Jelly Bean or CyanogenMod (this would be my preference) or if someone has a BETTER suggestion than I am open to a better mod. I have seen a few really catchy ones like MAXIMUS that I wanted to try. I have achieved unlocking, rooting, and S-OFF on this device already. After those processes.. my phone downloaded a large system update from AT&T which was Jelly Bean. It will not allow it to install. I presume this is because my device isn't actually approved for that update and something I did in this whole process triggered the server into believing I should have gotten it..
So is there a way for me to update my HBOOT for CyanogenMod or some other form of an upgraded version of Android?
I am currently running:
Android Version 4.0.4
Sense Version 4.0
Software Number 2.20.502.7.710RD
SDK API Level 4.23
Kernel 3.0.8-01558
Anyone out there able to point me in the right direction? Thanks!
Click to expand...
Click to collapse
Did you flash TWRP or CWM recovery? Did you just flash su in recovery to achieve root?
exad said:
Did you flash TWRP or CWM recovery? Did you just flash su in recovery to achieve root?
Click to expand...
Click to collapse
I originally started with TWRP as I had used the all in one tool for alot of the process. I then performed the the S-OFF and just now flashed Clockwork because I had read of others with TWRP 2.5 issues installing ROMs. Even in clockwork I can't install the Jelly Bean update on my ICS phone so I'm assuming there is a step I don't know of and cannot find anything for it. Thanks for responding!
acw928 said:
I originally started with TWRP as I had used the all in one tool for alot of the process. I then performed the the S-OFF and just now flashed Clockwork because I had read of others with TWRP 2.5 issues installing ROMs. Even in clockwork I can't install the Jelly Bean update on my ICS phone so I'm assuming there is a step I don't know of and cannot find anything for it. Thanks for responding!
Click to expand...
Click to collapse
You need stock recovery to allow the installation of an OTA. It can be extracted from an OTA zip file.
In short, since you are S-OFF.
1. Flash 3.18 ATT RUU.
2. Flash recovery. I have always used TWRP and had good luck.
3. Save latest CM 10.1 (or other ROM) to your SDCARD.
4. Boot to recovery and flash ROM.
5. Profit!
Thanks alot, to both of you!
I used the RUU and after a few small errors was in fact able to update to HBOOT 2.14 and Android Jelly Bean. The rest should be a cake walk. I'm truly appreciative of how quickly and intelligently you guys helped me out. Thanks again.
Just wanted to thank you guys again.
Over the past 3 days, I have made a successful transition from a crummy stock device on an outdated Android 4.0.4 OS to ViperXL 3.2.8 with the latest ElementalX kernel and I could not be happier.
Could not have done it without you folks!
I have a HTC one XL (s-on, hboot 1.14) with magio rom (4.2) installed. Suddenly my phone stopped getting a network signal. At first I thought its a hardware issue but then I found out it with the software plus its a common issue. Im not an experienced user.
So far I've found out the solutions are
1) Updating the firmware - I have no idea about this. Do I have to install the stock and root again? Is this installing the stock RUU? My CID is all ones, something like 1111111. Will I brick my phone? Do I have to install both th rom and firmware?
2) Beastmod - I feel dumb after reading this thread because it doesnt say what are the requirements to install this. Never installed a kernal before.
http://forum.xda-developers.com/showthread.php?t=2165880
3) Market app - network speed boost - I tried this, workd like a charm in the first.Sent a few texts but as soon as I made a call I lost the network
Due to my lack of knowledge on the subject I'm sacared to experiment because there is a chance of bricking the phone. I understand the issue is related with android 4.2 so a noob proof guide will help everyone who have the issue.
(example - http://forum.xda-developers.com/showthread.php?t=1787148)
kind regards
Whether you decide to update the firmware or install the Beastmode kernel, you will need s-off. You'll find the s-off thread here. You'll almost definitely need to change ROMs temporarily as it seems to be virtually impossible to achieve on a Sense 5 Android 4.2.2 ROM.
The kernel is s-on friendly but many people who are s-on have had trouble installing it. The 2.15 firmware can be found in the first post of this thread, along with instructions on how to flash it. It has nothing to do with returning to stock or RUUs and you don't need to modify your phone other than getting s-off first.
Sent from my Evita
dragz said:
So far I've found out the solutions are
1) Updating the firmware - I have no idea about this. Do I have to install the stock and root again? Is this installing the stock RUU? My CID is all ones, something like 1111111. Will I brick my phone? Do I have to install both th rom and firmware?
Click to expand...
Click to collapse
The firmware package being discussed (for resolving signal drop issues on Sense 5 ROMs) and linked by timmaaa above is not an RUU, but just the hboot, radio, boot.img, media and WiFi modules that came with the "official" Sense 5 OTA. It will only overwrite the modules I named, not the ROM. Nothing else needs to be done (you will still have your current ROM, root, etc.).
You must be s-off to install this.
timmaaa said:
Whether you decide to update the firmware or install the Beastmode kernel, you will need s-off. You'll find the s-off thread here. You'll almost definitely need to change ROMs temporarily as it seems to be virtually impossible to achieve on a Sense 5 Android 4.2.2 ROM.
The kernel is s-on friendly but many people who are s-on have had trouble installing it. The 2.15 firmware can be found in the first post of this thread, along with instructions on how to flash it. It has nothing to do with returning to stock or RUUs and you don't need to modify your phone other than getting s-off first.
Sent from my Evita
Click to expand...
Click to collapse
thank you, it worked
I'll give you the basic background information. I decided to try KitKat and upgraded my firmware to 3.18 and HBOOT[?] 2.14, then upgraded that to 2.15. I am S-OFF and have superCID. I want to use 10 November 2012 nightly of AOKP, found here http://goo.im/devs/rohan/evita/aokp/nightlies. I am currently running CM11.0 with few issues but I don't think it is as stable as my last ROM. Oh right, and the backups I saved don't work and I have tried different versions of TWRP and downgrading from 2.15 to lower than 2.14. Any help is appreciated, sorry if I am unclear, I have been working for hours trying to figure it out, but I am no developer.
Ok, first your touchscreen issue. If you want to run older ROMs you need to downgrade your touchscreen firmware. There is a thread detailing how to do this in our general section.
[EDIT] I was wrong about the location that thread, here it is:
http://forum.xda-developers.com/showthread.php?t=2159863
Now, your backups. Which version of TWRP did you use to create the backups? And which options (system/data/boot/cache, etc) did you check?
Sent from my Evita
Oh no, I am not sure what version of TWRP I used, but I have tried several versions to restore with. I didn't change and things, so whatever was checked default. The links on that thread are dead, or they give me a 404 Not Found page. That is why I have come here to find if there is new links maybe?
What partitions are able to be restored when you attempt a restore? If the links there are dead you might be out of luck with downgrading your ts firmware. You shouldn't need to flash such an old ROM though. Have you tried any other 4.4 ROMs? There are plenty available and they're stable, cm11 is probably the most unstable of them all.
Sent from my Evita
Thank you for your help, I'll post over there anyway seeing if anyone still has the files.
i need help
DevonDeception said:
Thank you for your help, I'll post over there anyway seeing if anyone still has the files.
Click to expand...
Click to collapse
i need to know how downgrade my touch screen firmware.......the xda post for that process has been moved and i cannot find it anywhere. please help me.
i really want the king beatz rom to work, but no touch screen functionality