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.
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.
I have my at&t htc one x on 4.0.4, bootloader locked, hboot 1.14.0002 S-on
evita pvt ship. i bought from amazon used, how can i update from 4.0.4 to a higher firmware and if i try use software update it searches for a bit then i get error what can i do?
Do you want to stay stock or install custom ROMs? The two processes will be very different so I need to know which way you want to go before advising you.
Sent from my Evita
---------- Post added at 02:42 AM ---------- Previous post was at 02:40 AM ----------
Also, do you have adb/fastboot installed on your PC? If not you're going to need that, Google search "xda minimal adb and fastboot" and the first result should be a thread that details how to install it easily.
Sent from my Evita
If you want to update to the latest "official" firmware, you can download the RUU at the following webpage, and follow the directions where it says "Manual system update instructions":
http://www.htc.com/us/support/htc-one-x-att/news/
This will update you to Jellybean 4.1.1, which is the latest that has been released for the AT&T version.
Be aware this will wipe any date on the phone, so backup anything you want to keep.
EDIT: As timmaaa advised below, CID needs to be verified before running the above RUU. If SuperCID is present with s-on, running the RUU will brick the device.
Hang on, we need to check his SuperCID status before he runs a jb RUU, the phone is used. We don't want a brick on our hands.
Sent from my Evita
timmaaa said:
Hang on, we need to check his SuperCID status before he runs a jb RUU, the phone is used. We don't want a brick on our hands.
Click to expand...
Click to collapse
Very true. I assumed that since the phone is still bootloader LOCKED, that its bone stock (I also missed the word "used" when I read the OP). But its possible the previous owner changed the CID, but either botched the BL unlocking or didn't get that far.
I've edited my previous post accordingly, to make sure the OP doesn't damage his phone.
Yeah, previous owner could have also spoofed the bootloader text to say locked instead of relocked.
OP, get adb/organised as per my first reply and then we can check out your situation before proceeding.
Sent from my Evita
htc one x
how do u get pass the sid lock to get the slock off
DaShadow14 said:
how do u get pass the sid lock to get the slock off
Click to expand...
Click to collapse
Huh? That makes absolutely no sense. If you want help please do the following:
1- Don't hijack this thread, we're already helping someone else here. Please repost your question in my q&a thread.
2- Tell me exactly what you want to achieve.
3- Tell me your bootloader details.
4- Tell me any other relevant information.
5- Do all this in clear and legible English, and be specific.
PS. There are no such things as a 'sid lock' or 'sloff', as I've said above please post in clear English using terms that actually exist.
Sent from my Evita
ok im going to try super cid do i need to root my phone 1st and i want stock unless custom is more better and stable.
Stock ROM is stable but so are custom ROMs, plus you get better features with custom ROMs. Before you do anything though you need to decide whether you want to use a stock ROM or a custom ROM. The two processes will vary greatly. Have you installed adb/fastboot like I suggested earlier?
Sent from my Evita
no i didnt get get adb or fastboot i dont know were to get it and ok i'll do custom rom.
ok im roothing and it says * daemon not running. starting it now on port 5037 *
* daemon started successfully *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
its been like this for 5mins now?
What method are you using?
Sent from my Evita
i was using a one click rooting software i deleted it i now have
onexrootattnew.zip but that doesnt want to root it either really and truly i jus wanted to update my software cuz my phone wifi range is seriously low to the point that i have to be right new to a router or 5ft away to catch signal and my bluetooth range basically is 1ft so i wanted to update to fix my problem
There's only one way you can get root. The first thing you need to do is stop getting information from other sites, they don't properly distinguish between firmware versions, and even phone models. Everything you need is here on XDA, it's the only comprehensive Android modification site available.
Click the Everything Evita link in my signature and bookmark that thread, everything you need is compiled in that thread. In that thread navigate to the root section, find the 2.20 root method. Follow the instructions in that thread and you'll have SuperCID. Then you can go to htcdev and unlock your bootloader. Once you have an unlocked bootloader you can install Superuser to root your current ROM, or you can install a custom ROM. If you need help installing a recovery or ROM just click the How-To Guide For Beginners link in my signature.
Sent from my Evita
thanks man i will try it out will get back to u by 2morrow.
my bootloader is unlocked so i can get any custom rom?
Technically, yes. But your phone still needs some updating before you can stay on a custom ROM. Your steps will be as follows:
1. Install TWRP recovery.
2. Install root via SuperSU.
3. Get s-off via Facepalm.
4. Run the 3.18 RUU (this returns your phone to stock but it's essential because this is the step that updates everything)
5. Install TWRP recovery again (official TWRP 2.6 for Sense 5 ROMs and aosp ROMs lower than 4.4, or modified TWRP 2.6.3.0 for 4.4 aosp ROMs).
6. Update firmware via 2.15 firmware package (this step is only necessary if you're planning on installing a Sense 5 ROM). You'll find it in the first post of this thread along with instructions.
7. Install whatever ROM you like.
8. Enjoy.
If you have any questions don't be afraid to ask.
Sent from my Evita
ok ill let u know when im done
Have a look at my How-To Guide For Beginners thread in my signature for detailed instructions on some of those processes.
Sent from my Evita
All, please be aware that S-OFF is not a trivial thing to do - once you are S-OFF, you will NOT be able to go S-ON again, try and you'll have a nice mini paperweight!
You'll find that S-OFF can cause more problems than it can "solve" - a quick search will show that you may (actually, most likely will) have to keep your bootloader LOCKED to boot your ROM - a locked bootloader = no fastboot = no flashing new boot or recovery images. UNLOCKED = boot loop city, with you as the mayor!
The only way to use fastboot would be to run revone via adb shell or the TWRP built-in terminal, boot to hboot, do your fastboot stuff, then revone again to relock the bootloader so you can actually boot your ROM.
The reason that S-OFF became a popular was to remove HTC's system protection - system protection basically removes any changes made to the system and reverts to the original system image every time you reboot. REALLY annoying. S-OFF allows system mods, which is a good thing, BUT: It's NOT necessary, as the proper solution is a custom kernel which removes the system protection without you risking a bricked phone.
Bottom line is, AVOID S-OFF if you can.
S-OFF does have benefits and is very handy in certain situations, but felt that people should also be aware of the risks, and think before doing it, "Do I REALLY need to do this, or can I wait a short time after an Android version upgrade for a modded kernel, or ROM with kernel mods?"
I've now helped 16 members out of soft bricks, it's a long and laborious process - everybody wants the latest and greatest (I know I do!), but a little forethought and patience may save you £500 buying a new phone to get the latest and greatest. There is no claiming on warranty or asking for a refund for your brick.
Is this true, you can't turn s-on again without bricking the phone?
Also I'm currently s-off with an unlocked boot loader and don't suffer any boot loops. Using Magio R3 JB4.22 and JMZ kernel. Maybe you would suffer boot loops with a different setup, I don't know..
Also the kernel I'm using I'm sure has system protection disabled. Does this make s-off pointless for me? Does this do the same as s-off?
cheers.
Sent from my HTC One using Xparent Green Tapatalk 2
You my friend, are a smart man. You've stuck with a stable ROM which has a lot of solid development work which had been tested and verified. JMZ knows exactly what he is doing, and produced a kernel which, as you correctly pointed out, negated the need to s-off. ALL of the issues reported for 4.3 are down to people buggering about with something they don't really understand.
Stay stable.
Just in case I did at some point want to update my rom at a later date to 4.3 or maybe 4.4 when it's released, will I have issues being s-off? And is it possible to undo s-off? Or could I leave it as is without issues? I just want to be clear on this. Cheers.
Sent from my HTC One using Xparent Green Tapatalk 2
RuffBuster said:
Just in case I did at some point want to update my rom at a later date to 4.3 or maybe 4.4 when it's released, will I have issues being s-off? And is it possible to undo s-off? Or could I leave it as is without issues? I just want to be clear on this. Cheers.
Sent from my HTC One using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
There are roms for 4.3 (stock deodexed by tr1gg3r) which have a modded kernel which removes system protection, so no need for s-off - there is a new 4.3 magio rom coming very soon, I've been beta testing for a week.... It's sweeeeeeet! It's going to be about 60% smaller than the usual mini ROM due to getting rid of the massive amount of bloat.... Fast, trim, and battery life is a good 40% better!
When kitkat arrives (in February apparently!), it will be system protected, so I don't doubt the whole "stock/s-off" thing will kick off again - my advice to everyone is to have patience, a modded kernel included in a rom will be available a few days after the OTA....
Going s-off then attempting s-on is very risky.....
Hope this helps!
nelvinchi said:
There are roms for 4.3 (stock deodexed by tr1gg3r) which have a modded kernel which removes system protection, so no need for s-off - there is a new 4.3 magio rom coming very soon, I've been beta testing for a week.... It's sweeeeeeet! It's going to be about 60% smaller than the usual mini ROM due to getting rid of the massive amount of bloat.... Fast, trim, and battery life is a good 40% better!
When kitkat arrives (in February apparently!), it will be system protected, so I don't doubt the whole "stock/s-off" thing will kick off again - my advice to everyone is to have patience, a modded kernel included in a rom will be available a few days after the OTA....
Going s-off then attempting s-on is very risky.....
Hope this helps!
Click to expand...
Click to collapse
so once u s-off, is better to stay s-off right? Unless u have to exchange for warranty or something then u would have to take the risk to s-on. And btw what is that 4.3 Rom? Is it like a stock Rom or sense Rom?
@abzboi "And btw what is that 4.3 Rom? Is it like a stock Rom or sense Rom?"
it is the 4.3 rom that you have been discussing with tr1gg3r84 on his magiorom thread !!
abzboi said:
so once u s-off, is better to stay s-off right? Unless u have to exchange for warranty or something then u would have to take the risk to s-on. And btw what is that 4.3 Rom? Is it like a stock Rom or sense Rom?
Click to expand...
Click to collapse
Warranty - If you touch the bootloader in ANY way, s-off/s-on, whatever, the device is MARKED and no tool or method to re-stock can hide this - if it goes back to HTC and is checked, they WILL know you have messed about with it. Fact.
For whatever reason someone has gone s-off, it's best not to mess about with it, the more modding the messier it gets. Google "back to s-on" and you'll see so many horror stories, and so many "HOW to return to 100% STOCK - 100% working!". Yeah, right.
S-OFF is unnecessary UNLESS you are an actual DEVELOPER, and have a full understanding of android and HTC system. 4.3 came out, people posted OTA's, then everyone found that they couldn't flash it as they were rooted/custom rom/custom recovery - ooooh, if i go back to "stock" i'll be able to install it. Errrr, I think you'll find that the majority of people who attempted to "re-stock" found that, "re-stock" = soft brick.
Stock rom IS sense rom
Braddison said:
@abzboi "And btw what is that 4.3 Rom? Is it like a stock Rom or sense Rom?"
it is the 4.3 rom that you have been discussing with tr1gg3r84 on his magiorom thread !!
Click to expand...
Click to collapse
Indeed it is. I've been beta testing versions for the past couple of weeks, and can confirm it's fast, slim, and de-bloated. Battery life is around 40% better....
@nelvinchi brilliant ! i've came from an galaxy s3 running slim rom and been looking for a superslim rom since gettin a one mini (as we are restricted with storage space).i hope tr1gg3r84 uploads the rom this weekend.
Re: S-off... i have no issues with s-off at the moment(no boot loops etc).will find out if i run in to difficulty when i flash the new MagioRom .
cheers
Braddison said:
@nelvinchi brilliant ! i've came from an galaxy s3 running slim rom and been looking for a superslim rom since gettin a one mini (as we are restricted with storage space).i hope tr1gg3r84 uploads the rom this weekend.
Re: S-off... i have no issues with s-off at the moment(no boot loops etc).will find out if i run in to difficulty when i flash the new MagioRom .
cheers
Click to expand...
Click to collapse
You are s-off - you'll be fine with this as it doesn't require a fastboot flash of the boot.img, so no bootloader unlocking/relocking necessary....
Can I ask (just out of curiosity):
If you are LOCKED/UNLOCKED
hboot version
SuperCID
Current ROM and recovery
Thanks!
cool.
S-off unlocked (used ramrunner not revone)
hboot- 2.19.00
supercid- no
rom- stock sense 5.5 4.3 deodex by tr1gg3r84
recovery- twrp not cwm
i did run into a few issues throughout the whole process to be honest though...After running superwipe it deleted everything,even the rom i was going to flash on sd.
i had to push rom to phone but it failed to flash. i then had to push rom and supersu to /data/local, then rom flashed from there but
couldnt find the md5 but it has worked without any issue since (you had helped me out by this point,thanks again)
cheers
I've just discovered that if you have hboot version 2.21 you will NOT need to re-lock your bootloader to prevent boot loops after going S-Off. However, in order to update your hboot to 2.21, you have to go S-off first, LOL. Just know that you won't be able to boot to anything other than recovery or fastboot until you update your hboot to 2.21. Hope this helps someone some day
Hum...
If i'm :
HBOOT 2.19
S-OFF
SUPERCID
Bootloader unlocked with htcdev
Root
On the stock 4.2.2 rom after purchase
I can't flash the stock rom of tr1gg3r84 or i may brick or have boot loops ?
@PuffDaddy_d Hey im currently S-off, unlocked bootloader ,hboot- 2.19.00 . never had any issues with bootloops no matter what rom I've tried. never had to flash the boot.img via fastboot either!
i take it that you mean we have to update our hboot for tr1gg3r84s new stock 4.4.2 rom or we will face bootloops ??
cheers
Braddison said:
@PuffDaddy_d Hey im currently S-off, unlocked bootloader ,hboot- 2.19.00 . never had any issues with bootloops no matter what rom I've tried. never had to flash the boot.img via fastboot either!
i take it that you mean we have to update our hboot for tr1gg3r84s new stock 4.4.2 rom or we will face bootloops ??
cheers
Click to expand...
Click to collapse
You might be right - I didn't go S-Off until I tried the new 4.4.2 Rom, so it very well could've worked with previous versions.
For the "boot loop city" you refer to while being s-off and unlocked. remove the file /system/bin/hcheck. It will fix that problem. No need to relock and unlock all the time
And why can you NOT go back S-ON?
And the write protection is in kernel and has nothing to do with S-OFF. Well, actually, kernel checks status of S-OFF/S-ON. If its on then don't allow system edits. If it is OFF then allow system edits. You can be s-on with a modified kernel and make changes to system
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.