After reading countless threads about RUUing or OTAing to the 3.18 Jellybean software, I think I know what everything means. But just to be safe, I want to confirm some things before I try anything. I have never been on a stock firmware other than when I got my phone, and it came on the 2.20 ICS software.
1. I used the SuperCID method to unlock my bootloader. I've read that having SuperCID will screw up the update to jellybean. But, I've also read that having s-off will bypass the CID check when updating, making the update work normally.
My phone has a CID of 1111111 (SuperCID), and is also s-off. Does this mean if I flash back to a stock ICS rom and OTA up to jellybean, everything will be alright? After all of the info I've sifted through, my personal answer is 'yes, everything will work.'
2. If I do proceed with an update to JB, will I still have S-off and/or a root? I've looked at the facepalm s-off thread under the Original Development section, and see no mention of a compatibility or incompatibility with Jellybean. This is the first HTC device I've ever owned, so I'm not as familiar with s-off as some of you may be. I did find this from searching the s-off thread... http://forum.xda-developers.com/showthread.php?p=38197741
If I recall correctly, I was running Viper XL when I s-off'd. It was a jellybean firmware at that time, probably built from the jellybean stock firmware. My personal answer to the question is 'yes, I will still be s-off, but I still don't know about a root.'
As far as a root goes, I'm at a loss of what to look for. I don't see a thread dedicated to a jellybean root, but then again, I'm not as well rounded with troubleshooting as others.
Sent from my HTC One XL using Tapatalk 2
S-off will stick until you manually undo it. Whether you ruu, flash roms, whatever. Only way to lose s-off is to do fastboot oem setsecurityflag 3. Root is software so it's set within the rom. All the custom roms have root by default. With an unlocked bootloader any rom that doesn't have root can have root by flashing su. Consider root as having administrator on windows. If you don't have windows installed there's no administrative access to have right? Hence it doesn't stick but is built into the roms you flash.
S-off eliminates security checks so you you can ruu, flash anything and there won't be any checks that say hey, this isn't the right device or hey, this bootloader is unlocked, you can't ruu..
Just make sure not to flash anything not intended for the evita.
Hopefully this makes sense.
If you have any other questions, do not hesitate to ask.
Sent from my HTC One X using xda app-developers app
exad said:
S-off will stick until you manually undo it. Whether you ruu, flash roms, whatever. Only way to lose s-off is to do fastboot oem setsecurityflag 3. Root is software so it's set within the rom. All the custom roms have root by default. With an unlocked bootloader any rom that doesn't have root can have root by flashing su. Consider root as having administrator on windows. If you don't have windows installed there's no administrative access to have right? Hence it doesn't stick but is built into the roms you flash.
S-off eliminates security checks so you you can ruu, flash anything and there won't be any checks that say hey, this isn't the right device or hey, this bootloader is unlocked, you can't ruu..
Just make sure not to flash anything not intended for the evita.
Hopefully this makes sense.
If you have any other questions, do not hesitate to ask.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks, this pretty much answered all of my questions so if I just wanted a rooted stock rom, I would just follow the steps in the root guide that involve pushing and installing the su binary, and ignore the extra ones that involve changing the CID?
I can't seem to find any links to stock rooted for ICS (it's a preference to me over JB, sorry ) anymore. My thoughts were to run the 2.20 RUU and root it, which seems like a valid option based on your response
Sent from my HTC One XL using Tapatalk 2
Ics is obsolete. If you really want stock rooted Ics.
You're correct.
Run an ics ruu
Flash twrp, flash su
Sent from my HTC One X using xda app-developers app
tyessen said:
My phone has a CID of 1111111 (SuperCID), and is also s-off. Does this mean if I flash back to a stock ICS rom and OTA up to jellybean, everything will be alright? After all of the info I've sifted through, my personal answer is 'yes, everything will work.'
Click to expand...
Click to collapse
If the goal is JB, then I'd recommend the JB RUU, rather than the OTA. RUU is a much cleaner and problem-free install.
'yes, everything will work' is a bit too presumptive to me. You can never be sure that everything will be okay. Modding your phone always has its risks, even under the safest of circumstances. But S-off will prevent the particular case of a (virtually guaranteed) brick caused by installing the RUU or OTA with SuperCID + S-on.
redpoint73 said:
If the goal is JB, then I'd recommend the JB RUU, rather than the OTA. RUU is a much cleaner and problem-free install.
'yes, everything will work' is a bit too presumptive to me. You can never be sure that everything will be okay. Modding your phone always has its risks, even under the safest of circumstances. But S-off will prevent the particular case of a (virtually guaranteed) brick caused by installing the RUU or OTA with SuperCID + S-on.
Click to expand...
Click to collapse
I didn't mean everything as in it will be right out of the box, no errors or problems by that, sorry. I meant that the flash/RUU would complete successfully and I would be running a stock firmware again.
And like I said, I've never ran the official JB firmware, so I'll give it a try and see how the battery holds out. I know ICS had a much better life than other JB custom roms out there, but then again, custom means extra (most of the time).
So, maybe I'll just head straight for the jellybean RUU instead. My only concern is that the h-boot would update, and that sets off a little flag in my head with s-off problems (even though it was confirmed it would stay in place until I manually went back to s-on).
Sent from my HTC One XL using Tapatalk 2
tyessen said:
I didn't mean everything as in it will be right out of the box, no errors or problems by that, sorry. I meant that the flash/RUU would complete successfully and I would be running a stock firmware again.
Click to expand...
Click to collapse
Again, I would never assume that everything will be "completely successful". Even running the RUU under safest of circumstances has its risks. People have bricked their phones running the RUU with a completely stock device. However, its very unlikely.
S-off removes the particular issue of a near automatic brick if you have SuperCID and S-on. There should be no other particular high risk factors, that are currently known and within your control (which is what I think you are trying to get at). You will most likely be okay. But its impossible to remove all risk. Anything that updates hboot and radio has the risk of bricking the device, if it everything does not go exactly right. But aside from being sure you don't mess with the phone or computer while its flashing, its just an unlikely random event, outside of your control.
tyessen said:
And like I said, I've never ran the official JB firmware, so I'll give it a try and see how the battery holds out. I know ICS had a much better life than other JB custom roms out there, but then again, custom means extra (most of the time).
Click to expand...
Click to collapse
I would not jump to the conclusion that ICS has better battery life JB (custom or otherwise). I'd say that quite a few people have had better battery life on JB. There are lots of variables at play. Simply RUUing to the newer radio might improve your battery life. Or might even make it worse.
Battery life is always better experienced for yourself, rather than taking for granted what you read from others.
Related
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
First android phone it's a AT&T One X, i'll be using it on the Bell network. Got a good deal on Kijiji and I didn't ask enough questions apparently, lol.
The phone is clearly not stock, took me several hours to piece that together. I get it, I'm a noob. I can tell it's running Cleanrom 4.5. I want to get it back to something close to stock. I plan to learn all about rooting/roms but I want to do it from a vanilla phone so that I get to actually do it myself.
I googled and found a tutorial (link). I deleted the 'su' file and superuser.apk. I followed the rest of the steps and it didn't seem to do anything, just rebooted back into cleanrom.
I kept googling and now I'm following this guide: http://forum.xda-developers.com/showthread.php?t=1859714
I guess i'm going to flash from an RUU now ? My CID is 11111111, so I've read that means I have superCID and any RUU will work. I want to get to JB eventually, so can I just flash direct to the Europe 3.14 JB from HTCRUU? Or go with one of the ICS versions?
Am I doing this right?
No no no!
Edit: still writing but wanted to say don't flash that ruu
If you want completely stock you need to use fast boot and boot into hboot and run fastboot OEM lock
(You may need to search around to learn how do that)
Then run this ruu. http://beta.androidfilehost.com/?fid=9390077933525139511
Sent from my One X using Tapatalk 2
that is for the wrong phone
only place you should look at is here AT&T, Rogers HTC One X, Telstra One XL
Its good your asking the questions now if you want to go completely stock run an ruu which means relicking the bootloader and running it ill link you to some guides in a sec
---------- Post added at 07:43 AM ---------- Previous post was at 07:43 AM ----------
Oh and like others said don't use that ruu! We have the one XL
cleanrom 4.5 is pretty good and close to stock but adds quick settings, debloated, power menu and some other tweaks. i would keep it how it is and just learn about how custom roms work. you can learn how to use twrp in its current state and maybe learn how to use some root apps.
just so you know your phone is the evita not the endeavoru.
Thanks for the replies.
I haven't tried flashing anything yet so don't worry. I'm taking it slow.
I've already been into fastboot. Figured that out because it was a required step in the guides I said I was trying to use. I have all the drivers installed and I'm able to talk to the phone via fastboot at the comand prompt.
LOL, thanks for letting me know my phone is Evita. I guess I can delete the 600mb RUU I downloaded
I'm a little unclear about HBOOT vs. fastboot. I can get into the bootloader and go to the fastboot USB mode... is this analogous to HBOOT?
So my steps right now are:
1) Download correct RUU, Evita 2.20 ICS - I've also seen people discussing 1.85 vs 2.20, why chose one over another?
2) fastboot oem lock
3) Install RUU while phone is in bootloader mode
That right?
I would strongly suggest to slow down, and learn more about what root is and means, before going back stock. Root is just a change in permissions. You gain absolutely nothing by unrooting, and lose quite a bit. You lose the ability to do all sorts of mods to your phone, flash custom ROMs, use apps that require root like Adaway and Titanium Backup (and many others), remove carrier bloatware, activate tethering, and much more.
People have gone through great pains to find root methods for our device (and other Android devices). Many come on here looking for these root methods, for the awesome benefits that root means. I've seen very few, if any, people before you that have said "crap I accidentally got a rooted device, and don't want root". Think about that one for a while.
Plus, CleanROM 4.5 is already based on a more updated firmware version than any of the official AT&T RUUs. Plus it includes a lot of cool features and optimizations. Again, going from CleanROM to stock is a step backwards, not forwards, and you are gaining nothing, and losing quite a bit. Another thing about CleanROM, is that it is devoid of the AT&T bloatware (and there is a lot). Keep in mind that on the stock AT&T ROM, the bloat is not removable without root, so you are stuck with quite a few crappy apps that you will never use. That alone is a huge reason to have a rooted device. Also bear in mind that stock AT&T does not allow tethering (unless you have a data plan that allows it) and has other stock HTC apps (like FM radio) disabled. These cannot be enabled unless you have root.
Another thing, is that you will not get Jellybean any faster on stock than rooted. While its true that rooted, this phone will not be able to take the OTA when it rolls out (hasn't happened yet). But a stock rooted JB firmware will almost certainly be posted here on XDA, that is safely flashable on a rooted device. This often happens within a couple days of the OTA starting to roll out, if not faster. Sometimes even before the OTA, as sometimes the official RUUs get leaked before the OTA. All it takes is for a dev to get his hands on the files, apply root, and upload it here. Learning how to flash such a file to your device is very simple. Not much more than: download the file to your phone, boot into recovery, and press "install". So yet again, stock gains nothing over being rooted.
While its true that root is not for everyone. But if you've already found this place, and learned what things like RUU, bootloader, and fastboot are, then you probably already know more than most folks do about Android. You may feel in over your head, but it really just takes a few hours of reading to learn the fundamentals. And with that knowledge, you can do so much more with your phone than you can without root.
redpoint73 said:
I would strongly suggest to slow down, and learn more about what root is and means, before going back stock. Root is just a change in permissions. You gain absolutely nothing by unrooting, and lose quite a bit....
Click to expand...
Click to collapse
I appreciate the advice, thanks. To be clear, eventually I will probably bring the device back to where it is now. I've used linux before so I have an understanding of the permissions system and the added benefits of root.
My goal here is to get the phone back to stock so that I can learn the rooting/flashing process from the start, not the end. I understand why that might seem counterintuitive but I'm a very hands on person and I'll learn more of the theory by walking through the process than reading about how somebody else hacked this device to get where it is now.
Sure I'm making extra work for myself but I know what im getting into.
Sent from my HTC One X using xda app-developers app
echoboomer said:
I appreciate the advice, thanks. To be clear, eventually I will probably bring the device back to where it is now. I've used linux before so I have an understanding of the permissions system and the added benefits of root.
My goal here is to get the phone back to stock so that I can learn the rooting/flashing process from the start, not the end. I understand why that might seem counterintuitive but I'm a very hands on person and I'll learn more of the theory by walking through the process than reading about how somebody else hacked this device to get where it is now.
Sure I'm making extra work for myself but I know what im getting into.
Click to expand...
Click to collapse
You should have said so from the start, then. This pretty much negates everything I just typed above.
Its admirable that you want to learn the process from scratch, and its the opposite attitude of most n00bs here.
My advice, as another mentioned above, is stick to XDA, and don't follow instructions from random Googled sites. Most of those sites don't clearly delineate between our phone (Snapdragon S4) and the international (Tegra3) version, and following instructions for the international version is a great way to brick your phone.
Other than that, lock the bootloader, run the RUU, and have fun. Also check your hboot version. If its anything but 1.14, don't run the 2.20 RUU. You will want the 1.73 or 1.85 RUU instead, as the 2.20 RUU will update the hboot to 1.14, which plugs the holes by which boot.img and radios can be flashed from recovery. Unless you want to create ever MORE work for yourself, as the hboot can be downgraded using a Linux computer, lol!
Be sure to check out my index thread, as most anything you will need is here: http://forum.xda-developers.com/showthread.php?t=1671237
Thanks, sounds like I'm on the right track.
Also check back to my OP, I did say that I wanted to learn the whole process but I wanted to do it from stock. sorry you typed all that out but in sure it will help some other noob down the line.
Last thing, 1.85 vs 2.20?
Sent from my HTC One X using xda app-developers app
ChummyDays said:
2.20 has the new hboot, and that means that you have to extract the boot.IMG out of the ROM and flash it through fast boot. With 1.85 you just flash the ROM.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Cool thanks, I found a tutorial last night on how to extract boot.IMG from the ruu exe. I think I'm good to go.
Sent from my HTC One X using xda app-developers app
You might be confused. You shouldn't have to pull a boot.img from an RUU typically, only from a custom ROM zip. And only if you are on boot 1.14.
Sent from my HTC One X using xda app-developers app
Probably confused. Here's what I see in the boot loader.
***
Tampered
Unlocked
Evita PVT Ship S-ON RL
HBOOT-1.09.0000
Radio-0.19as.32.09.09_L
OpenDSP-v28.1.0.32.0504
eMMC-boot
***
Sent from my HTC One X using xda app-developers app
echoboomer said:
HBOOT-1.09.0000
Click to expand...
Click to collapse
This is what you want to see, and why you need to be sure to use the 1.85 RUU.
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
Hi,
I'm still on 4.4.2 and wish to backup, S-OFF, root, and upgrade to 5.x (open to trying a custom ROM). I'm completely new to this and have a couple questions:
In what order should things be done? My guess is the order listed above?
Can I just follow the instructions in the stickies (firewater, etc), or are they out of date?
If upgrading to a non-Sense ROM, will software (camera, sound, etc) work as well?
If you have any tips/suggestions/advice/things you wish you'd known, I'd greatly appreciate it. Thanks!
1.Go here.
Download APP/EXE version (which i did).
Follow the instruction & flash the exe ruu.If you encounter problem when flashing,just flash this latest hboot & reflash the app exe ruu.Do this only if you encount with any flashing error.
Let it reboot.That's all .
2.No matter which rom you are flasing SENSE or SENSLESS,just flash the latest firmware first.Then you can flash any rom.
Before you go loading RUUs I would recommend turning s-off first. For that you have to use sunshine. Firewater is discontinued and won't work even if you have the files. You would have to run sunshine BEFORE upgrading to lollipop because it hasn't (yet) been updated to work on the lollipop update. Hope this isn't too late of advice.
Caspid said:
Hi,
I'm still on 4.4.2 and wish to backup, S-OFF, root, and upgrade to 5.x (open to trying a custom ROM). I'm completely new to this and have a couple questions:
Can I just follow the instructions in the stickies (firewater, etc), or are they out of date?
If upgrading to a non-Sense ROM, will software (camera, sound, etc) work as well?
If you have any tips/suggestions/advice/things you wish you'd known, I'd greatly appreciate it. Thanks!
Click to expand...
Click to collapse
Hi,
Follow this xda thread to root http://forum.xda-developers.com/xperia-z/general/guide-how-to-root-10-5-1-0-283-t2872873.
After rooting, install NUT's dual recovery. Then download pre-rooted zip for Android 5.0.2 from development section and flash through revovery.
Sent from my C6602 using xda Forums PRO
SurenderK said:
Hi,
Follow this xda thread to root http://forum.xda-developers.com/xperia-z/general/guide-how-to-root-10-5-1-0-283-t2872873.
After rooting, install NUT's dual recovery. Then download pre-rooted zip for Android 5.0.2 from development section and flash through revovery.
Sent from my C6602 using xda Forums PRO
Click to expand...
Click to collapse
These instructions are for a different phone. It's the same for the M8?
cntryby429 said:
Before you go loading RUUs I would recommend turning s-off first. For that you have to use sunshine. Firewater is discontinued and won't work even if you have the files. You would have to run sunshine BEFORE upgrading to lollipop because it hasn't (yet) been updated to work on the lollipop update. Hope this isn't too late of advice.
Click to expand...
Click to collapse
What, really? Even for 4.4.2? I thought sunshine was only required for later versions.
Caspid said:
These instructions are for a different phone. It's the same for the M8?
What, really? Even for 4.4.2? I thought sunshine was only required for later versions.
Click to expand...
Click to collapse
So I don't know what that guy is talking about. Steer clear of that advice.
The only way to unlock the bootloader of a Verizon m8 is sunshine and it also turns s-off which is sweet. Firewater worked for older versions, I actually used it myself many months ago. Shortly after sunshine released for the m8 they turned off the online part of Firewater. Sunshine does cost $25 but I donated more than that as a thanks for Firewater, it seems fair.
Once s-off you will be able to do pretty much whatever you want, flash recovery (which can then flash custom roms), upgrade firmware, downgrade firmware, flash radios, etc. However this also means that you can brick your phone if you don't know what you're doing. Definitely don't go following instructions instructions for another phone.
It you don't mind sense, flashing doddat's stock rooted RUU is a one step process and you're done.
If you want bloat removed, the ability to make nandroid, and the many features of custom roms then you need to flash TWRP recovery and you can go to town. If you want bloat removed then there are some pretty good sense based roms. I ran viper Rom for a while and was pretty happy. Then there's gpe and cm based roms. As far as I know most are pretty bug free.
Just be careful. Like I said, s-off allows you to do both awesome and detrimental things to your phone. Know what you're doing, how to do it, and most importantly how to undo it before you do anything.
cntryby429 said:
So I don't know what that guy is talking about. Steer clear of that advice.
The only way to unlock the bootloader of a Verizon m8 is sunshine and it also turns s-off which is sweet. Firewater worked for older versions, I actually used it myself many months ago. Shortly after sunshine released for the m8 they turned off the online part of Firewater. Sunshine does cost $25 but I donated more than that as a thanks for Firewater, it seems fair.
Once s-off you will be able to do pretty much whatever you want, flash recovery (which can then flash custom roms), upgrade firmware, downgrade firmware, flash radios, etc. However this also means that you can brick your phone if you don't know what you're doing. Definitely don't go following instructions instructions for another phone.
It you don't mind sense, flashing doddat's stock rooted RUU is a one step process and you're done.
If you want bloat removed, the ability to make nandroid, and the many features of custom roms then you need to flash TWRP recovery and you can go to town. If you want bloat removed then there are some pretty good sense based roms. I ran viper Rom for a while and was pretty happy. Then there's gpe and cm based roms. As far as I know most are pretty bug free.
Just be careful. Like I said, s-off allows you to do both awesome and detrimental things to your phone. Know what you're doing, how to do it, and most importantly how to undo it before you do anything.
Click to expand...
Click to collapse
So instead of making a new thread my question is similar to the guys above. I am on 4.4.2 but already have S-off and root, TWRP installed etc. I have had the phone since launch and have been happy enough to not worry about updating or changing anything too much.
Anyhow, I am now interested in updated, I read a few months ago that 4.4.2 should update to 4.4.3 before going to 4.4.4. Is this still the case if I only want to go to 4.4.4? Still the case if I go all the way up to 5.0.1?
Second, apologies if the answer is the same as above but I just want to be sure I am clear, I am s-off already, will I need sunshine moving forward for after I updated? Or since I am s-off already will I stay that way and be able to root without any additional steps after updating?
Resputan said:
So instead of making a new thread my question is similar to the guys above. I am on 4.4.2 but already have S-off and root, TWRP installed etc. I have had the phone since launch and have been happy enough to not worry about updating or changing anything too much.
Anyhow, I am now interested in updated, I read a few months ago that 4.4.2 should update to 4.4.3 before going to 4.4.4. Is this still the case if I only want to go to 4.4.4? Still the case if I go all the way up to 5.0.1?
Second, apologies if the answer is the same as above but I just want to be sure I am clear, I am s-off already, will I need sunshine moving forward for after I updated? Or since I am s-off already will I stay that way and be able to root without any additional steps after updating?
Click to expand...
Click to collapse
I recall that idea of necessary incremental upgrades being passed around for my previous HTC device, the Rezound. I suspect that it's not true although I certainly don't know enough to support that statement. My suspicion is that if you were to flash any of the RUUs which were posted by dottat you will successfully boot any of our official software versions regardless of what version you're coming from. This presumes the prerequisite that you're s-off in order to permit downgrading (if you choose) and/or use of some of his s-off-required RUUs. With as full-proof as those RUUs seem to be, the worst case scenario is that your device bootloops requiring another RUU. I don't know that you're at all too much risk of bricking your phone provided you are flashing files that are meant for your exact model (be weary of flashing international/AT&T RUUs and such to a verizon phone) and are following instructions.
Regarding sunshine, as long as you don't issue specific fastboot commands to relock the bootloader or turn s-on, then you should have no further use for Sunshine. The only reason I can see someone taking updates incrementally is if they want to take them OTA. However, if you're s-off then I would highly recommend just using an RUU. None of the RUUs or firmware update zips will relock the bootloader or turn s-on. I can think of very few reasons to do either of those with the exception of returning to full stock for a warranty return. I believe that all of the RUUs will restore stock recovery, but since they don't relock the bootloader, you can always just flash back your custom recovery via fastboot or bootloader and re-root your stock rom. Alternatively, once you have a custom recovery you can flash any one of the many custom roms which will almost certainly come pre-rooted.
Let's see, I forgot when I bought this phone, but I remember not liking the phone much, used it for a while for some light usage, and threw it back in storage..and forgot about it. Found it a few days ago, and since I'm sending my Zenfone 2 to warranty, probably gonna use this device until I get back the Asus. Might as well gonna buy a new phone after getting some cash together, anyway, stuck with this tiny device for a while. Just realized that it has only 1GB for apps, although it says 8GB on the box. Weird. So I decided to root the device to get rid of some pre installed junks. I only rooted some Samsung devices before, htc procedures are quite different. Unlocked, and rooted. It's running on 4.2.2 JB, k2_ul LTE version, and hboot is 2.1 as far as I can recall. And then, after rooting and all, noticed that I can't delete those pre-installed stuff even with the root, so just froze them, which I could of done without rooting in the first place. Not much on SV over the internet, but all I gathered is that on the bootloader screen, s-on needs to be s-off in order to modify or remove something system related from the phone, I think. Tried to do that, but couldn't find any methods online for Jelly Bean 4.2.2. Only option I think, is the rumrunner, but their website is kaput. As you can see, the dilemma I am in now. I understand, nobody cares about this phone, not even HTC even after the release. Just need some basic information.. where do I go from here. I swear I will throw this phone back into the darkness once I get my main device back/buy a new one, but for a while, have to live with it..
>Any way to turn the security off, s-off for the 4.2.2 JB ?
>Or just flash a custom rom, not that the phone has many other roms. I think flashing requires the s-off too.
>Or find a way to move apps to other partitions of the phone..i.e, Internal memory or MicroSD, which I have no clue how to do. :silly:
I just want some space on the phone, and bloatware vanished. Helps are appreciated !
dunhill1410 said:
>Any way to turn the security off, s-off for the 4.2.2 JB ?
Click to expand...
Click to collapse
Well, if rumrunner don't work, Sunshine app should work to get S-off, as far as i know. Sunshine is not free, it cost 25 USD.
Another way to disable write protection for S-on devices is this -> http://forum.xda-developers.com/showthread.php?t=2575240
But i never used this, so don't ask me how to do.
>Or just flash a custom rom, not that the phone has many other roms. I think flashing requires the s-off too.
Click to expand...
Click to collapse
Flashing custom roms will also work on S-on devices. Just read and follow the guides how to flash in the rom threads. S-on will require some extra steps, which are usually mentioned in this threads.
dunhill1410 said:
(...) Weird. So I decided to root the device to get rid of some pre installed junks.(...)
Click to expand...
Click to collapse
You can many of these applications simply off in the options of the system.
old.splatterhand said:
Well, if rumrunner don't work, Sunshine app should work to get S-off, as far as i know. Sunshine is not free, it cost 25 USD.
Another way to disable write protection for S-on devices is this -> http://forum.xda-developers.com/showthread.php?t=2575240
But i never used this, so don't ask me how to do.
Flashing custom roms will also work on S-on devices. Just read and follow the guides how to flash in the rom threads. S-on will require some extra steps, which are usually mentioned in this threads.
Click to expand...
Click to collapse
Well, rumrunner worked. Their website is down, and while in the bathtub, got the idea about the web archive/wayback machine. Et Voila ! Thanks, regardless. I have uploaded the HTC Universal Rumrunner version if anyone needs it. Pretty easy.
http://d-h.st/t5r0
Did you successfully root your SV? I rooted mine without problem, I still keep the stock 4.2.2 JB and HTC Sense.
I like the SV for its small size and excellent signal reception. The removable battery is also a plus.
I'm a professional [desk] diver.