Database Info

[Q] Worst-case scenario regarding S-OFF, root, bootloader

I've searched (both xda and external sites) and I've read through many threads but I still don't have clear answers to these questions so I'd appreciate any help anyone can provide. I'm an Atrix user so I'm assuming a worst-case scenario mindset in order to properly weigh my options before upgrading.
1. What issues would HOX users face if the devs are never able to achieve S-OFF?
I think the normal behavior for S-ON is that you are not able flash kernels or radios. However, the devs have currently figured out a way to flash kernels on the HOX despite the lack of S-OFF. Similarly, there may also be a way to flash radios despite the lack of S-OFF too but this has not yet been achieved. I think S-OFF also lets a user resize partitions but I'm not sure why this would be a huge issue. Is this all more or less correct?
2. 1.85 devices can have their bootloaders unlocked once a new root exploit is found for that firmware, right?
My concern is that I'll get a 1.85 and be permanently stuck with an AT&T/HTC ROM.
This all comes down to the HOX vs. SGS3 for me. I really prefer the HOX but I'm not willing to risk being stuck with the AT&T ROM. Of course, this could be moot because we don't yet know whether or not AT&T will be able to convince Samsung to make an exception to their bootloader policy like they were able to do with HTC.
Thanks again for your help.

I think AT&T phones are being shipped with 1.73 right now which is capable of being rooted. Someone correct me if I'm wrong.

Yes if the htc has 1.73 it can be rooted. Then the cid can be changed to unlock the bootloader through htc dev. After that you lock the bootloader back and upgrade to 1.85. Then you re unlock the bootloader and install cwm and after installing cwm flash SU for root on 1.85. As for Samsung EHH..

1. As far as I know all you've stated is correct, if a dev wants to pop in to correct me by all means you can. There are some kernels that are "flashable" not neccessarily stable though just because of the lack of a source code. And the DCM by viperboy is pretty awesome.
2. Yes they will be able to. Most people are stuck on 1.85 because they were too eager and updated before any development. They're not really all to blame it's just human nature. But as far as I know there is no current development for root because the method from 1.73> to root> to CWM is getting the primary focus. Phones as of right now are being shipped with 1.73 IF you can even get your hands on one. It's hard because of all the customs issues.
Both phones will be excellent and both will get great development. I've just been an HTC guy so I like the HOX. However if you want "right now development" the GS3 might be a better choice in all honesty depending on what AT&T decides on the BL. But HOX development is moving along quite nicely. My phone kicks ass!

Thanks, everyone.
@Shaddy-Z
So in your opinion the lack of progress in obtaining root for 1.85 is mainly due to a smaller current need and not because of some new or challenging hurdle? Would you expect a new method to pop up once a majority of phones begin shipping with 1.85? What would you put the odds at? I know this is not apples to apples but I have residual skepticism carried over from the Atrix bootloader affair. The devs were basically thwarted/defeated and the unlock was only achieved as a result of an anonymous/unsanctioned leak.

Just saw this post: http://forum.xda-developers.com/showthread.php?t=1693624 It appears they are shipping now with 1.85...

You do not need s-off to flash kernels. You can flash them through fastboot just fine, as long as you have an unlocked bootloader. You just can't flash them through recovery until we have s-off. I really don't think s-off is even needed. It would be nice to have but it doesn't stop you from doing anything except flashing radios. I was in the same situation when I was using the Vivid. I didn't even s-off my Vivid when the tool was released because I didn't need it.

pside15 said:
You do not need s-off to flash kernels. You can flash them through fastboot just fine, as long as you have an unlocked bootloader. You just can't flash them through recovery until we have s-off. I really don't think s-off is even needed. It would be nice to have but it doesn't stop you from doing anything except flashing radios. I was in the same situation when I was using the Vivid. I didn't even s-off my Vivid when the tool was released because I didn't need it.
Click to expand...
Click to collapse
Actually they have found a way to.flash kernels and radios in recovery.
Sent from my HTC One X using xda premium

In this thread it is mentioned that everything can be flashed though custom recovery now http://forum.xda-developers.com/showthread.php?t=1639972&page=99
so s-off is not limiting us anymore

So... No need for s-off now then? :thumbup:
Sent from my HTC One X using xda premium

[Q] How can i root after installing ics ruu?

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.

[Q] Thing I must know before I purchase a HOX

So Guys black friday is around the corner and I plan to upgrade from my dated HTC Aria. I'm obviously looking at the HOX and the S3 and just by personal preference am leaning towards the HOX (ATT version). However what is really worrying me is that the HOX seems to be locked down quite a bit. I'm not a dev or anything I just want to be able to flash custom rom and experience senseless android in jellybean. So I have some questions...
1) If I buy a HOX with the 2.02 version what are my options rooting wise or am I just screwed?
2) I'm coming from a rooted Aria where rom flashing was easy with clockworkmod recovery. I been lurking this forum and it seems like a painful process now and what is this boot.img thing.
3) Also if anyone isn't to annoyed by my lack of knowledge could you explain what the "S-ON/S-OFF" is as well as the limitation with the fact that HTC locked the boot loader?
I like the HOX but am getting scared away by the fact that this phone is so locked up.

sunny342 said:
So Guys black friday is around the corner and I plan to upgrade from my dated HTC Aria. I'm obviously looking at the HOX and the S3 and just by personal preference am leaning towards the HOX (ATT version). However what is really worrying me is that the HOX seems to be locked down quite a bit. I'm not a dev or anything I just want to be able to flash custom rom and experience senseless android in jellybean. So I have some questions...
1) If I buy a HOX with the 2.02 version what are my options rooting wise or am I just screwed?
2) I'm coming from a rooted Aria where rom flashing was easy with clockworkmod recovery. I been lurking this forum and it seems like a painful process now and what is this boot.img thing.
3) Also if anyone isn't to annoyed by my lack of knowledge could you explain what the "S-ON/S-OFF" is as well as the limitation with the fact that HTC locked the boot loader?
I like the HOX but am getting scared away by the fact that this phone is so locked up.
Click to expand...
Click to collapse
First off, when you get it rooted... DONT FLASH ICJ.
Second, when you get it downgrade you hboot via the JET tool or manually through the WIP Unbrick evita thread by Absolutelygrim. Then in the JET tool thread, you'll find a way to RUU down grade. Choose 1.85 Then you won't have to worry about flashing the boot.img in fastboot. All that is, is a way to bypass AT&T's safe gaurd programming. They tried to make it so the boot.img couldn't be formed in recovery. That's only with the 2.20 firmware though.
Third, IDK. I'm still learning why S-OFF is like gold. Someone else might be able to answer that one but, not me.

1) 2.20 firmware is fully rootable, and has been for a few weeks now. Worries about there not being a root method for 2.20 are outdated, and no longer apply.
2) First off, CWM is not recommended for this device. It never officially supported the Snapdragon S4 variant, and was just a port, with serious known issues. A different custom recovery, TWRP is recommended, and works great.
With the 1.14 hboot that comes with the 2.20 firmware, the hole by which boot.img was flashed via recovery was plugged. So whenever you flash a new ROM, you need to extract boot.img from the ROM zip, and flash it separately via fastboot (phone connected to your PC). Or as previously mentioned, you can downgrade the hboot to eliminate this step.
Aside from that, flashing ROMs on TWRP is just as easy as CWM on your Aria (once you have bootloader unlocked and TWRP installed).
3) S-Off means all security off. It hasn't yet been achieved yet on this device. But with an unlocked bootloader, you can flash ROMs and other mods. With a downgraded hboot, you can flash radios. So there isn't much that S-Off would give you, that isn't already possible. Being able to get SIM unlock for free might be possible with S-Off, as well as turning off the warning flag that the bootloader was unlocked. But for the most part, that is really it. For most uses, S-Off simply is not needed. S-On and bootloader unlock fulfills most needs.
All that said, are you aware the One X+ is being released by AT&T tomorrow? It features a slightly faster CPU/GPU and much more internal storage. Unless you are on a budget, that is probably the phone I would go for at this point. But I think it also remains to be seen about root and bootloader unlock for the One X+.

Another aria convert, yay. As stated above, you shouldn't have any concerns about this device. TWRP is actually much easier to use than CWM. The flashing boot.IMG separately is something you won't need to do once you downgrade the firmware.
And as said above, I'd just get a one x+ if I had the money. We only get 9.93GB of SD storage space on this phone.
Sent from my HTC One XL

Hello guys, i am also thinking about getting this phone, but i've been searching this forum and it seems that flashing ROMs is a bit complicated, and i'm not sure..
What are the pros and cons of unlocking the bootloader? could i brick the phone by doing that?
Is there a guide for noobies like me, a tutorial or something? sorry.. i'm new to this.. :fingers-crossed:

p3terr said:
Hello guys, i am also thinking about getting this phone, but i've been searching this forum and it seems that flashing ROMs is a bit complicated, and i'm not sure..
What are the pros and cons of unlocking the bootloader? could i brick the phone by doing that?
Is there a guide for noobies like me, a tutorial or something? sorry.. i'm new to this.. :fingers-crossed:
Click to expand...
Click to collapse
Would you be getting the AT&T version, or another variant?
Setting the phone up for flashing ROMs is a bit more complicated than some other manufacturers. But this is just how it is for HTC, they have an increasing degree of security on their phones.
You have to unlock the bootloader, which really isn't all that hard. Then install custom recovery and you can flash ROMs. The AT&T version has the extra steps of temp root, SuperCID before you can unlock the bootloader.
Once the phone is setup, flashing ROMs is just like any other phone. With the exception of having to extract boot.img from the ROM zip and flashing via fastboot. But I believe this only applies to the AT&T version with the 1.14 hboot. Even so, you can downgrade the hboot, so you don't have to do the extra step of manually flashing boot.img.
Bricking the phone while unlocking the bootloader is unlikely. But its always a possibility with any mods. Unlocking the bootloader wipes the phone (not really an issue if you are doing it right away after buying) and you also have to confirm that you understand that unlocking the bootloader may void your warranty. Other than that, there is no real "con" to it.

I just finished unlocking bootloader, rooting, installing venom Rom and putting beastmode custom kernel on my [email protected] hox. It's easy now even with 2.2. Just download the all in one tool kit found in the stickied thread for the hox. Does almost all work for you.
Flashing Rom there after word was very similar to cwm was. Loaded it on my internal storage and flashed via recovery
Sent from my HTC One XL using xda app-developers app

redpoint73 said:
1) 2.20 firmware is fully rootable, and has been for a few weeks now. Worries about there not being a root method for 2.20 are outdated, and no longer apply.
2) First off, CWM is not recommended for this device. It never officially supported the Snapdragon S4 variant, and was just a port, with serious known issues. A different custom recovery, TWRP is recommended, and works great.
With the 1.14 hboot that comes with the 2.20 firmware, the hole by which boot.img was flashed via recovery was plugged. So whenever you flash a new ROM, you need to extract boot.img from the ROM zip, and flash it separately via fastboot (phone connected to your PC). Or as previously mentioned, you can downgrade the hboot to eliminate this step.
Aside from that, flashing ROMs on TWRP is just as easy as CWM on your Aria (once you have bootloader unlocked and TWRP installed).
3) S-Off means all security off. It hasn't yet been achieved yet on this device. But with an unlocked bootloader, you can flash ROMs and other mods. With a downgraded hboot, you can flash radios. So there isn't much that S-Off would give you, that isn't already possible. Being able to get SIM unlock for free might be possible with S-Off, as well as turning off the warning flag that the bootloader was unlocked. But for the most part, that is really it. For most uses, S-Off simply is not needed. S-On and bootloader unlock fulfills most needs.
All that said, are you aware the One X+ is being released by AT&T tomorrow? It features a slightly faster CPU/GPU and much more internal storage. Unless you are on a budget, that is probably the phone I would go for at this point. But I think it also remains to be seen about root and bootloader unlock for the One X+.
Click to expand...
Click to collapse
I am aware of the One X+ but I am on a budget and the slight performance boost to me doesn't justify the price. Radio shack will have the HOX for free on blackfriday. Also thanks for the answers to the questions your comment cleared up alot for me.
ECEXCURSION said:
Another aria convert, yay. As stated above, you shouldn't have any concerns about this device. TWRP is actually much easier to use than CWM. The flashing boot.IMG separately is something you won't need to do once you downgrade the firmware.
And as said above, I'd just get a one x+ if I had the money. We only get 9.93GB of SD storage space on this phone.
Sent from my HTC One XL
Click to expand...
Click to collapse
ARIA FTW lol. I need the upgrade to the HOX. Only 9.9GB sucks pretty bad but I can make it work. If only I too had the money for the one X+

You don't need to wait for black friday to get the HOX for free. It's currently free on ATT on Amazon Wireless, and has been for a couple weeks.
If you follow instructions properly and read up on everything necessary, unlocking, rooting, and flashing the HOX is a breeze; 2.20 only introduces one additional, straightforward step.

exygenysys said:
You don't need to wait for black friday to get the HOX for free. It's currently free on ATT on Amazon Wireless, and has been for a couple weeks.
Click to expand...
Click to collapse
Im eligible for a qualified upgrade on my family plan so I can't take advantage of the new contract deal.

[Q] Having difficulties understanding S-Off

Hello,
I got the htox first day out was super excited, was happy with stuck for awhile and then rooted and unlocked on 1.82 (one click made it easy) and unlocked on the dev site. I ran for a long time on KingKang ROM 4.1 and just recently started geting bored and wanted to upgrade more. I have been bouncing around on 4.2.2 Roms like liquidsmooth/xylon (Btw thx azn and Rohan), but I am noticing all these different things saying S-OFF required. I have wiped everything off the phone and tried diff kernels but always seem to have more issues then everyone else (Screen on in calls, FC, Random reboots). Thinking I missed something? Do I need to update to S-OFF everything talks about 2.22 and OTA for S-OFF? My bootloader screen is saying EVITA PVT SHIP S-ON RL. sorry if this is poorly put together
Was I supposed to update to 2.20 then push ota and s-off? or is there a way to s-off on older versions. How do I see what version I was on prior to my root I want to make sure it was 1.82.

Don't update if your rooted unless you have s-off
http://forum.xda-developers.com/showthread.php?p=38909732
[Public Service Announcement] Read before installing the AT&T Jellybean OTA or RUU
Have you attempt s-off yet? Might he a good idea.
Sent from my One X using xda premium

I would not s-off or do anything else to your phone until you have a better handle on what you're doing. It's obvious from that post that you lack a good understanding of these changes you want to make (not surprising since you one-clicked).
S-off is just a security setting, not something you install or update to. It's not dependent on software version. You need to read up on what it means, since it removes almost all restrictions on changes you can make. Good if you know what you're doing, dangerous if you don't.
These random issues you're experiencing seem to occur when running Jelly Bean roms on older firmware. I was on 1.82 and had the same reboot issues. I ran the 3.18 ruu and it cleared things up--but you must be s-off before doing it or you may brick your phone.

What iElvis said.
S-off just means "security off" or that all security checks are bypassed. That is all. Its not going to magically fix any random bugs, in and of itself.
I've also had the phone since release, until very recently have been S-on, and flashed many a custom ROM with none of the issues you describe for the most part (only a few random reboots which were very probably a ROM issue). Its more likely due to kernel mismatches, issues with the ROM itself, or possibly other user error (improper wiping before flashing the ROM).
This is one of those instances, if you don't know what it is, you probably shouldn't be doing it. So at a minimum, do your homework and read up.

I suggest leaving a stock rom with root to do s-off without problems.

iElvis said:
I would not s-off or do anything else to your phone until you have a better handle on what you're doing. It's obvious from that post that you lack a good understanding of these changes you want to make (not surprising since you one-clicked).
S-off is just a security setting, not something you install or update to. It's not dependent on software version. You need to read up on what it means, since it removes almost all restrictions on changes you can make. Good if you know what you're doing, dangerous if you don't.
These random issues you're experiencing seem to occur when running Jelly Bean roms on older firmware. I was on 1.82 and had the same reboot issues. I ran the 3.18 ruu and it cleared things up--but you must be s-off before doing it or you may brick your phone.
Click to expand...
Click to collapse
Do you really notice a difference since 3.18? I mean the 4.2.2 ROMs I been on run pretty good, although not flawless. I been on 1.85 and been wanting to try the latest, just worried about the touchscreen outcome. I know there's a tut on downgrading touchscreen but I always ask myself if its necessary... Don't fix what isn't broken right lol...
But if you genuinely think it cleared up a few things I might give it a go..
Sent from my One X using Tapatalk 2

So I have been rooting for awhile (since my 8525) I just don,'t remember anything to do with the soff. I am no expert was just hoping there was an thread someone could point me to about it' I read the article above but once again it is geared towards 2.20 not 1.82
Sent from my One X using xda app-developers app

Touretts said:
So I have been rooting for awhile (since my 8525) I just don,'t remember anything to do with the soff. I am no expert was just hoping there was an thread someone could point me to about it' I read the article above but once again it is geared towards 2.20 not 1.82
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
S-OFF has nothing to do with software or hboot verison. It's a security flag. S-ON means security checks are done prior to/during RUU and flashing of some things.
S-OFF means no security checks are done, flash whatever you want.
Sometimes just because something is changed and a security check is done, for example, if your CID is different from what the RUU you are running expects it to be, your phone bricks.
For the record, the amount of phones you've rooted has nothing to do with knowledge or experience as most phones are crazy easy to root and technically require no knowledge to do so and it's very possible not to brick while remaining ignorant. Your chances of bricking are much lower if you understand what you are doing and every phone is different any way. so.. yeah.

S-off is specific to Android and specific to HTC devices (and certain ones at that). There are several threads in the this (AT&T One X) forum that discuss what s-off means, and what it enables you to do, so just do a search a read up.

I can see this ending badly.

OK I didn't know it was HTC only. I will read more than ty.
Sent from my One X using xda app-developers app

InflatedTitan said:
Do you really notice a difference since 3.18? I mean the 4.2.2 ROMs I been on run pretty good, although not flawless. I been on 1.85 and been wanting to try the latest, just worried about the touchscreen outcome. I know there's a tut on downgrading touchscreen but I always ask myself if its necessary... Don't fix what isn't broken right lol...
But if you genuinely think it cleared up a few things I might give it a go.
Click to expand...
Click to collapse
It depends on what you mean by "not flawless." Don't do it if you just want to be "smoother." I did it out of frustration with the 10+ random reboots I was getting every day because of the wifi bug. That was cleared up. My phone has been running very smoothly, but if you decide to do it, be sure you understand the touchscreen firmware thing.

S-off in a nutshell allows you to flash kernels via recovery instead of using fast boot. And if your gonna try and get s-off you need to be somewhat familiar with adb. If you don't know what I'm talking about then you probably shouldn't attempt it.
sent from my jellybammed one x

So much info im getting very confused! ruu's and s off.....

Had my HTC ONE S for a while now
When i first got it i followed all the guides to unlocking the bootload and rooting etc and ended up running viper rom, and various others along the way. You know how it is!
Anyhow i was fiddling once and some how managed to delete the sd card and it wouldnt mount.
I fixed that and im not sure if its a coincidence but i now have random call drops even with a good signal. radio randomly coming on and music apps closing...........mainly when using head phones....................
The following is what was suggested to me.................
Sneakyghost said:
Not easy. I'd say do S-OFF as the very first thing (well relatively, of course do the unlock, do the SuperCID, then...). S-OFF ensures you can just flash any RUU and no matter if locked or unlocked or on custom ROM or not.
You can also only do SuperCID and flash any RUU.
Once done, pick the 3.16 WWE RUU. Please do NOT do the OTA which is offered on that RUU if you do not have S-OFF yet as that OTA disables any chance to get S-OFF currently.
If you happen to sit in the US and are on Tmobile, check HERE for latest tmob RUU because you might want Wifi calling and such. Else, just select any you like. I recommend WWE though.
Not really hard then once you got S-OFF. The hard part is understanding S-OFF procedure. If you get that done everything else is pretty easy. There is a thread for S-OFF with a good guide.
Regarding GPS Fix from Crypted: http://forum.xda-developers.com/showthread.php?t=1563226 (have that open in my browser always cause its a magic little fix)
Click to expand...
Click to collapse
Apparently my htc one s is a international one?
Your CID "HTC__001" Suggests you have an international one X and not a carrier locked one xl. You will need to post in the international one x forums.
Click to expand...
Click to collapse
Any ideas on what i do now as i cant find a htc one s international forum?
EDIT: regarding the above, no one seemed sure and i couldnt seem to find a definitive answer so rather than messing around changing the cid and risking a brick. Some one suggested RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe
as my radio is 1.06es 50.02.31 and the 2.31 works with hboot of 1.14 which mine also is....................
after all this im even more confused lol!
So currently ive relocked the bootloader using fastboot and run the above RUU and im back to stock i believe?
What would one suggest?
im on hboot 1.14.0002 and radio is 1.06es i believe.
Ideally id like to get back to viper rom
Might test for a few days if i can resist a custom rom just to check
thanks

Even I'm on hboot 1.14.. Get an S-OFF, flash a latest radio ie., 1.15. That should work.

so ifi flash s off i can run any run any ruu without risk of bricking? by changing the cid thing thanks?

Gavin01 said:
so ifi flash s off i can run any run any ruu without risk of bricking? by changing the cid thing thanks?
Click to expand...
Click to collapse
Risk of bricking came from.SUPER-CID and OTA update, also downgrading h-boot.

first get supercid, then get S-off, then change cid back to original or desired one. if you have a international S4 device original cid wil do fine.
then ruu what you want, s-off simplifies flashing of ruus and roms and more things.
if you might update the device with latest jb without S-off you cant get S-off no more (as of now), you now have the option.
you can always revert back.

Right guys im still not reallty understanding all this sorry.
My phones now coming up with OTA update which i understand i shouldnt run as this then blocks all chance of getting S-Off in the future?
As i understand it my HTC one is a international one so i dont need to change the cid?
So i need to do is get S-Off and run another RUU?
Ill try and follow the guide to S-Off but even that im struggling with Can anyone tell me what RUU i should be running when i manage to get S-Off. My details are above in the first post i think>?
Thanks for your patience.

You need supercid to get soff (face palm)
Then change cid back to original HTC one. To do any otas you want.
Advice:
Before you start. look at your current software version Google the ruu from that info, save the file. When need to ever change back in the future, and then ota back to latest version.
Verstuurd van mijn One S met Tapatalk

im still scared of this super cid thing as ive read a few people have bricked their phones
Although i keep getting the annoying message that a system update is available so i must try and do something soon.
Unless i just go straight to viper

Gavin01 said:
im still scared of this super cid thing as ive read a few people have bricked their phones
Although i keep getting the annoying message that a system update is available so i must try and do something soon.
Unless i just go straight to viper
Click to expand...
Click to collapse
If it's just the message you want to get rid of, just turn off automatic update checks.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black&Blue_Inverted_Sense | Bulletproof_1.4
Inverted Sense _4+_and_5_click me

Hello
Ok .. since i see some nice gentlemen here responding to queries with patience .. I'd like to post one myself.
I obtained S-Off the very next day i got my One S .. things were running smooth on stock. Looked out for some ROMS and finally installed one. Now I want to revert to my stock ROM while maintaining S-off/root. My problem is only that i don't find this ROM stable or the kernel .. just want to revert to stock.
Will flashing 3.16 WWE RUU take me back to stock firmware and kernel?
Would really appreciate the help