I've looked at a few threads but they seem to involve flashing before rooting...
Is there a way to root without flashing? if so... how?
Thanks
You can unlock the bootloader without flashing by booting into Bootloader modem (power off device, then power on while holding Power+VOL UP) and typing fastboot oem unlock into ADB from your computer.
But you cannot gain root access, use a custom recovery, or use a custom ROM without flashing. The "Flashing" you're hearing about is via Fastboot which allows the flashing of custom recoverys, or boot.imgs.
The one-click methods that might have allowed this in the past were based on exploits in the stock ROM/kernel. The Nexus S might contain similiar flaws to be exploited later(no current methods work fyi), but right now the easiest way to gain root is by doing what I said above or from the threads in the development section dedicated to it (also linked in the stickied FAQ if you don't know where to start).
Given that it's also possible to just as easily relock the bootloader(e.g. for warranty purposes), it's likely it will be some time before the exploits are searched for/discovered.
unremarked said:
You can unlock the bootloader without flashing by booting into Bootloader modem (power off device, then power on while holding Power+VOL UP) and typing fastboot oem unlock into ADB from your computer.
But you cannot gain root access, use a custom recovery, or use a custom ROM without flashing. The "Flashing" you're hearing about is via Fastboot which allows the flashing of custom recoverys, or boot.imgs.
The one-click methods that might have allowed this in the past were based on exploits in the stock ROM/kernel. The Nexus S might contain similiar flaws to be exploited later(no current methods work fyi), but right now the easiest way to gain root is by doing what I said above or from the threads in the development section dedicated to it (also linked in the stickied FAQ if you don't know where to start).
Given that it's also possible to just as easily relock the bootloader(e.g. for warranty purposes), it's likely it will be some time before the exploits are searched for/discovered.
Click to expand...
Click to collapse
abit confused by what your saying...
I'm interpreting what your saying as
"you can boot a boot loader/recovery without actually flashing it. It just boots that as a temporary and then apply superuser.apk, su" ???
sinatosk said:
abit confused by what your saying...
I'm interpreting what your saying as
"you can boot a boot loader/recovery without actually flashing it. It just boots that as a temporary and then apply superuser.apk, su" ???
Click to expand...
Click to collapse
The bootloader is built into the phone, there's nothing to flash for that.
Think of it as a pre-recovery. Fastboot is a feature in the Android SDK which works with the bootloader to flash things such as recovery, or boot.imgs prior to actually having a custom recovery/root. However, it does require the bootloader to be unlocked which is where the fastboot oem unlock command comes in. Once you have a custom recovery on your phone, you flash things like normal.
From the stickied FAQ:
unremarked said:
Q: How do I root/unroot the Nexus S?
Check the development section links below for more detail, but you gain root on the Nexus S by booting the phone into fastboot (aka the bootloader) mode and typing "fastboot oem unlock." This will wipe your phone and it's SD card partition. To unroot it, again boot into fastboot mode and type "fastboot oem lock."
Step 1: http://forum.xda-developers.com/showthread.php?t=878786
Step 2: http://forum.xda-developers.com/showthread.php?t=875875
Click to expand...
Click to collapse
The first step helps you set up the SDK and drivers. The second step will tell you how to root, install recovery, and flash Superuser.
Out of interest is there a step 3 that tells us how to reverse all of the above in the event of having to return the phone?
xspyda said:
Out of interest is there a step 3 that tells us how to reverse all of the above in the event of having to return the phone?
Click to expand...
Click to collapse
No, I'll add one, but generally Best Buy employees don't check things like the recovery or bootloader to see if a phone is rooted or not.
Anyhow, if you if you flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 it will restore you completely to stock, including the recovery. After that, it's just a matter of going back into the boatloader/fastboot mode and typing fastboot oem lock.
That is the only way to return to stock until Google puts out the official recovery stuff.
Fair enough, thanks for that. One question, will this actually restore to a state my nexus s was received in? Reason I ask is that I thought this was an adapted nand - although I understand this is the only option right now.
My retailer is perhaps a little more clued up than the the average best buy employee so is there anything in the software that can identify this as being a none original Google image?
Thanks again.
unremarked said:
No, I'll add one, but generally Best Buy employees don't check things like the recovery or bootloader to see if a phone is rooted or not.
Anyhow, if you if you flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 it will restore you completely to stock, including the recovery. After that, it's just a matter of going back into the boatloader/fastboot mode and typing fastboot oem lock.
That is the only way to return to stock until Google puts out the official recovery stuff.
Click to expand...
Click to collapse
this is why I started this thread... Google not released the official recovery
I already have the SDK setup, I code android applications ... no fastboot in there though. May have to compile that myself or use the one from the thread
thanks for your help...
xspyda said:
Fair enough, thanks for that. One question, will this actually restore to a state my nexus s was received in? Reason I ask is that I thought this was an adapted nand - although I understand this is the only option right now.
My retailer is perhaps a little more clued up than the the average best buy employee so is there anything in the software that can identify this as being a none original Google image?
Thanks again.
Click to expand...
Click to collapse
It will restore your phone to the state it was received in if it had shipped with Android 2.3.1. The OTA should be fairly well known to anyone you're returning it to.
I don't think so. It's entirely possible that Samsung might have something tucked away deep inside the phone, either hardware or software, but I highly doubt it. And, if there were, I think only their technicians who are trained in the intricacies of this device would know about it. As far as I understand, that NAND is completely stock without any modifications. I'll admit I haven't read the entire thread. At the very most, it may have the Superuser.apk and related binaries but I don't think so.
sinatosk said:
this is why I started this thread... Google not released the official recovery
I already have the SDK setup, I code android applications ... no fastboot in there though. May have to compile that myself or use the one from the thread
thanks for your help...
Click to expand...
Click to collapse
Ah, sorry, I'm having a hard time with explaining stuff. Some threads I'll jump in to try and help assuming the guy knows about ADB, root, system vs SD partitions, et al then find out not so much. Other threads, I'll end up making myself look silly.
Fastboot should just be an .exe file within the SDK's tool's section. You don't actually have to run it, though. Everything involving fastboot operates through CMD just like ADB, only you begin the obviously differently. (fastboot flash blahblahblah vs adb push blahblabhlah).
unremarked said:
It will restore your phone to the state it was received in if it had shipped with Android 2.3.1. The OTA should be fairly well known to anyone you're returning it to.
I don't think so. It's entirely possible that Samsung might have something tucked away deep inside the phone, either hardware or software, but I highly doubt it. And, if there were, I think only their technicians who are trained in the intricacies of this device would know about it. As far as I understand, that NAND is completely stock without any modifications. I'll admit I haven't read the entire thread. At the very most, it may have the Superuser.apk and related binaries but I don't think so.
Ah, sorry, I'm having a hard time with explaining stuff. Some threads I'll jump in to try and help assuming the guy knows about ADB, root, system vs SD partitions, et al then find out not so much. Other threads, I'll end up making myself look silly.
Fastboot should just be an .exe file within the SDK's tool's section. You don't actually have to run it, though. Everything involving fastboot operates through CMD just like ADB, only you begin the obviously differently. (fastboot flash blahblahblah vs adb push blahblabhlah).
Click to expand...
Click to collapse
well yeah I know about ADB... just nothing about rooting
Hmm the phone shipped with 2.3 and I have yet to update but as 2.3.1 is an official update I can't see that being reason not to accept a return.
I'm so extremely new to this forum (and any forum, for that matter) that I just have an overload of questions. I've taken the time to read some stickies for noobs and that you should always read and search before posting but I am impatient (I tried and failed).
I recently got a gorgeous, red htc one m8 from Verizon. This phone is bomb, and a total step up from my previous galaxy s3, but now I really want to root for the first time and see where it can take me.
I'd like to backup my phone before following the instructions to root, and the resources I've gotten don't seem promising and I was really just wanting to know what would be best to save EVERYTHING from multimedia to my somewhat custom settings. (?)
Please don't hate me. I'm so new. If I ever get to the point of rooting this thing are there any personal recommendations on where to begin after I've rooted (or threads that already have that stuff)?
The rooting process (including soff) wipes no data. After you get root, you can install an app like titani backup or helium backup to backup individual data. You also want to do a nandroid backup in recovery the second you install a custom recovery, so you have a cushion to fall in in a bad situation
wtoj34 said:
The rooting process (including soff) wipes no data. After you get root, you can install an app like titani backup or helium backup to backup individual data. You also want to do a nandroid backup in recovery the second you install a custom recovery, so you have a cushion to fall in in a bad situation
Click to expand...
Click to collapse
Thank you!
Now I've just got to google nandroid backup and custom recovery. These are honestly my baby steps with this, should I even root without knowing all this stuff or will it just get easier?
letsmoshjosh said:
Now I've just got to google nandroid backup and custom recovery. These are honestly my baby steps with this, should I even root without knowing all this stuff or will it just get easier?
Click to expand...
Click to collapse
I would say you need to read read read. The s-off procedures for either firewater our sunshine are damn near idiot proof so there's little to no risk of damaging things there. However, once you have the ability to flash things in a custom recovery the risk goes way up. As long as you're not flashing unverified experimental files or accidentally flashing files for a different model then today's recoveries make it pretty easy. Also, make a nandroid before you change just about anything through recovery. Happy flashing.
cntryby429 said:
I would say you need to read read read. The s-off procedures for either firewater our sunshine are damn near idiot proof so there's little to no risk of damaging things there. However, once you have the ability to flash things in a custom recovery the risk goes way up. As long as you're not flashing unverified experimental files or accidentally flashing files for a different model then today's recoveries make it pretty easy. Also, make a nandroid before you change just about anything through recovery. Happy flashing.
Click to expand...
Click to collapse
All of the above are true. Please revisit the thread if you have any issues setting up ADB on your machine before you attempt firewater (S-OFF). The big thing for me was making sure I got everything installed properly before I flashed. Once you do the root process be it Samsung, HTC, et al... you will find it is remarkably easy.
If you're looking for a custom ROM, be sure to stick to the Verizon HTC One M8 forums only unless you're directed there by a thread. Before you flash anything at all, just make sure you're solid on the process. Many times, there are awesome people who take the time to make a video about the process from start to end. Those will probably enormously useful for you on your first foray.
Again, ask around and read up! As cntryby429 said, read as much as you possibly can. The truth is, the devs do far more work than we could ever imagine as far as root goes.
Cheers!
letsmoshjosh said:
I'm so extremely new to this forum (and any forum, for that matter) that I just have an overload of questions. I've taken the time to read some stickies for noobs and that you should always read and search before posting but I am impatient (I tried and failed).
I recently got a gorgeous, red htc one m8 from Verizon. This phone is bomb, and a total step up from my previous galaxy s3, but now I really want to root for the first time and see where it can take me.
I'd like to backup my phone before following the instructions to root, and the resources I've gotten don't seem promising and I was really just wanting to know what would be best to save EVERYTHING from multimedia to my somewhat custom settings. (?)
Please don't hate me. I'm so new. If I ever get to the point of rooting this thing are there any personal recommendations on where to begin after I've rooted (or threads that already have that stuff)?
Click to expand...
Click to collapse
I've been where you are! It's a little daunting finding all the information and getting it sorted.
You will have to do your own reading and do lot of it, but here's a little summary to get you pointed in the right direction.
The only known root method for the M8 is WEAKSAUCE. It provides temp root, meaning you loose root with each reboot but the app will re-root the phone automatically about 30 sec after booting. Servicable but not very elegant.
Root with Weaksauce is a pre-requisite to everything below.
If you want permanent root and/or run a custom rom on this phone you have to S-off, unlock the bootloader and flash a custom recovery (in that order).
For S-off and bootloader unlock (accomplished at the same time) there are two methods:
FIREWATER: free, but does not work on all M8s. Try it - it'll either work or fail. Follow the instructions on the Firewater website to the letter
SUNSHINE: from the same devs that made Firewater, guaranteed to work on all M8s and it'll cost you $25. Well worth it in my opinion.
Once you have S-off and an unlocked bootloader you can install a custom recovery like TWRP or CWM (I recommend the former). Find instructions on the respective websites.
Once you have the custom recovery installed, you can
- flash SuperSU for permanent root
- make a nandroid (total system backup or image) of your stock rom or any rom you have currently installed
- flash a custom rom
This should get you started. Read everything three times, ask twice, flash once.
Edit: Could you do me a favor? Change the title of your thread to something like: Step-by-Step instructions for rooting/roming the M8?
It would make it easier to find for users in a similar situation.
Hoping some kind soul will take a few minutes to get me up to speed on what I need to know about hacking the M8.
I am not a total newb, and have lingered around XDA for a while. I've rooted many phones and tablets, even worked with cooking my own ROMS for android and older winmo 4+ years ago. I've just not been involved in the scene and am just about to get my new M8 and would like a crash course.
I really don't mind reading - so if someone has a great all-in-one guide they recommend, I'll certainly start with that...its just the endless searching for the up-to-date info I'm looking to avoid. I actually prefer to understand what I'm doing rather than just click "unlock"
Top most questions in my mind:
1) The biggest thing I would like to know to start is the best way to backup/up protect my device before I do anything to it.
I'd like to be able to return it to total stock (minus any impossibility in re-locking a bootloader) in case I mess things up or need to return, etc.
2) Current best methods for rooting, unlocking, etc. I just want to make sure I'm not doing something out of date that might be more effort than necessary/dangerous.
3) I see this new TWRP thing...which looks like an alternate to CWM. Which is better for me to use for M8?
4) Any M8 specific big dangers to watch out for to prevent bricking.
I always look to XDA for the best advice, but sometimes the site is difficult to navigate to find the most clear explanation.
TIA!
TraderJack said:
Hoping some kind soul will take a few minutes to get me up to speed on what I need to know about hacking the M8.
I am not a total newb, and have lingered around XDA for a while. I've rooted many phones and tablets, even worked with cooking my own ROMS for android and older winmo 4+ years ago. I've just not been involved in the scene and am just about to get my new M8 and would like a crash course.
I really don't mind reading - so if someone has a great all-in-one guide they recommend, I'll certainly start with that...its just the endless searching for the up-to-date info I'm looking to avoid. I actually prefer to understand what I'm doing rather than just click "unlock"
Top most questions in my mind:
1) The biggest thing I would like to know to start is the best way to backup/up protect my device before I do anything to it.
I'd like to be able to return it to total stock (minus any impossibility in re-locking a bootloader) in case I mess things up or need to return, etc.
2) Current best methods for rooting, unlocking, etc. I just want to make sure I'm not doing something out of date that might be more effort than necessary/dangerous.
3) I see this new TWRP thing...which looks like an alternate to CWM. Which is better for me to use for M8?
4) Any M8 specific big dangers to watch out for to prevent bricking.
I always look to XDA for the best advice, but sometimes the site is difficult to navigate to find the most clear explanation.
TIA!
Click to expand...
Click to collapse
1) The best most efficient way of backing up your device is to make a Nandroid backup with a recovery such as CWM or TWRP, but of course there will always be times where you could do something simpler to solve your problem such as disabling the Xposed framework but how? My phone is stuck in a bootloop, how would I disable it? The answer is when installing the framework make sure to first in the settings select to create flashable zips (manual) then once they are created go back and do the 'Classic' method. Now I'm sure if you're as new as you say you are you most likely don't know what Xposed is, it is a separate framework which allows you to customize your ROM to do things similar to what a 'Custom' ROM would normally always do. Most people don't think before installing these modules and end up soft-bricking their device and have to use their Nandroids to restore them but the way I mentioned is far simpler.
2) The utmost best method currently available (and only available) for rooting, unlocking, S-OFF & etc is currently Sunshine, you can read up about it here. Sadly and or not so sadly it costs $25 per device but it will do everything you will need to get started such as S-OFF (Security OFF, S-ON prevents writing to the /system partition and some other things I can't remember), Bootloader unlock & root.
3) Personally I prefer TWRP because it just feels like it has more ease of use towards it but thats just my opinion. There is an alternative to it which is CWM as you mentioned or 'PhilZ' CWM, Philz CWM is a touch-based version which to my experiences is a bit buggy but it works. I personally recommend TWRP but you might as well play around with them and see which one you like best.
4) Biggest danger of them all: To my knowledge that is, attempting to revert to S-ON. That is the most dangerous thing I am aware of at the moment but there may be something more dangerous but from what I know that is the most risky thing that is HTC based and or anything based.
This can be considered a good "All in one guide" for you to follow, it has pretty much everything I can think of at the moment.
An alternative to that one would be this one excluding all of the stuff involving Weaksauce and Firewater as Firewater does not work on newer devices and already rooted users don't have a use for Weaksauce. Still though it's a good tutorial for flashing a recovery and rooting.
Here is a solid tutorial on how to revert to stock if you ever decide to (once more do NOT attempt S-ON).
& if you're interested in using ROM's for other carrier variants of your phone then this one may be of interest to you.
Lastly, if you're concerned about any warranty things then as long as you do an RUU like the one mentioned in the 'Reverting to Stock' thread you will have no problems with it even if you're bootloader is unlocked and you're S-OFF. Why you may be wondering?? HTC sometimes ships phones already S-OFF/Bootloader unlocked and also I sort of think they just don't really care... you know as long as you didn't mess the phone up.
-----------------------------------------------------
If you have any further questions, I left something unclear or you just need me to elaborate further on something then feel free to ask further questions and I recommend doing your own research on these things before attempting them. Good luck and happy modding!
TraderJack said:
Hoping some kind soul will take a few minutes to get me up to speed on what I need to know about hacking the M8.
I am not a total newb, and have lingered around XDA for a while. I've rooted many phones and tablets, even worked with cooking my own ROMS for android and older winmo 4+ years ago. I've just not been involved in the scene and am just about to get my new M8 and would like a crash course.
I really don't mind reading - so if someone has a great all-in-one guide they recommend, I'll certainly start with that...its just the endless searching for the up-to-date info I'm looking to avoid. I actually prefer to understand what I'm doing rather than just click "unlock"
Top most questions in my mind:
1) The biggest thing I would like to know to start is the best way to backup/up protect my device before I do anything to it.
I'd like to be able to return it to total stock (minus any impossibility in re-locking a bootloader) in case I mess things up or need to return, etc.
2) Current best methods for rooting, unlocking, etc. I just want to make sure I'm not doing something out of date that might be more effort than necessary/dangerous.
3) I see this new TWRP thing...which looks like an alternate to CWM. Which is better for me to use for M8?
4) Any M8 specific big dangers to watch out for to prevent bricking.
I always look to XDA for the best advice, but sometimes the site is difficult to navigate to find the most clear explanation.
TIA!
Click to expand...
Click to collapse
The above post about covers it. Only thing I would like to add is I much prefer Phil's touch recovery based on CMW and try firewater method for soft and unlocking boot loader before paying for sunshine. It may or may not work. But could possibly save you the cash.
mdorrett said:
The above post about covers it. Only thing I would like to add is I much prefer Phil's touch recovery based on CMW and try firewater method for soft and unlocking boot loader before paying for sunshine. It may or may not work. But could possibly save you the cash.
Click to expand...
Click to collapse
Philz recovery is amazing, have you used the M8 unified builds yet? Or are you still sticking to the last Verizon build?
Sent from my HTC6525LVW using Tapatalk
Thanks all. I will certainly read up on what you've written and follow up with any questions I may have.
So I read a little bit on the posts above... Ick...when I was deciding on the M8 I checked to see if it was all hackable and apparently found the positive information for only the old methods and didn't realize a $25 price tag was the *only* way to really unlock the phone.
I mean...I don't totally begrudge the devs charging for it...but honestly I've never heard of this before in the 8-10 years I've been modding with smartphones of charging for this. While $25 may be nothing compared to a $700 unlocked phone, it sure is a heck of a lot more than $0, which was where the previous bar was set. You'd think $5 or $10 would be a better place to start.
Of course, it doesn't look like I have any other option though. I do have some more questions:
1) What are the pieces that sunshine does that can't be done elsewhere? It looks like there are several root methods - so is sunshine the only way to S-OFF or is it also the only way to unlock the bootloader?
2) If I don't do sunshine, and therefore can't S-OFF (and maybe can't unlock bootloader), can I still root? If so, is it only a temp unroot? And is there really a downside to that?
3) In all honesty, while I'd like to have everything unlocked, I think I will be happy with a root for now if that's enough to do some hacks (like maybe energy saving and wifi tether, etc.). Will I be able to do those with just root? I'm not really clear on the actual purpose of the S-OFF vs. the unlocked boot loader. Maybe in a few months I will be tired of the stock ROM and cough up the dough.
4) In order to do the backups to revert to stock, what steps must I first obtain and can I do those steps for free (aka no Sunshine) and are they reversible? IOW, what's the minimum I must "hack" the device in order to get a stock backup and/or to recover it.
Finally - when did the "firewater" method stop working? Is it newer hardware being shipped or a certain firmware/OS level update that blocked it? It sounds pretty unlikely that it will work for a new phone, but it won't hurt to try if it doesn't, right?
thanks again for the jump start....I think just jumping in and doing is the best way to learn, but I don't want to leap without protecting myself at the outset.
TraderJack said:
So I read a little bit on the posts above... Ick...when I was deciding on the M8 I checked to see if it was all hackable and apparently found the positive information for only the old methods and didn't realize a $25 price tag was the *only* way to really unlock the phone.
I mean...I don't totally begrudge the devs charging for it...but honestly I've never heard of this before in the 8-10 years I've been modding with smartphones of charging for this. While $25 may be nothing compared to a $700 unlocked phone, it sure is a heck of a lot more than $0, which was where the previous bar was set. You'd think $5 or $10 would be a better place to start.
Of course, it doesn't look like I have any other option though. I do have some more questions:
1) What are the pieces that sunshine does that can't be done elsewhere? It looks like there are several root methods - so is sunshine the only way to S-OFF or is it also the only way to unlock the bootloader?
2) If I don't do sunshine, and therefore can't S-OFF (and maybe can't unlock bootloader), can I still root? If so, is it only a temp unroot? And is there really a downside to that?
3) In all honesty, while I'd like to have everything unlocked, I think I will be happy with a root for now if that's enough to do some hacks (like maybe energy saving and wifi tether, etc.). Will I be able to do those with just root? I'm not really clear on the actual purpose of the S-OFF vs. the unlocked boot loader. Maybe in a few months I will be tired of the stock ROM and cough up the dough.
4) In order to do the backups to revert to stock, what steps must I first obtain and can I do those steps for free (aka no Sunshine) and are they reversible? IOW, what's the minimum I must "hack" the device in order to get a stock backup and/or to recover it.
Finally - when did the "firewater" method stop working? Is it newer hardware being shipped or a certain firmware/OS level update that blocked it? It sounds pretty unlikely that it will work for a new phone, but it won't hurt to try if it doesn't, right?
thanks again for the jump start....I think just jumping in and doing is the best way to learn, but I don't want to leap without protecting myself at the outset.
Click to expand...
Click to collapse
1) sunshine is the only way to s-off if firewater doesn't work. It pushes an exploit that turns the secure flag off so s-off is achieved, then it pushes a separate exploit to unlock the bootloader. You may be able to change your phone carrier ID so htc dev can s-off your phone, but it doesn't do everything sunshine does.
2) without using sunshine you can still have temporary root with weaksauce, but it's really limited. Since your phone is still s-on, it isn't able to write to the system partition. It means you lose root on every reboot, and you have to wait up to a minute for weaksauce to root again.
Also without an unlocked bootloader you are unable to flash a custom recovery, which means you can't make a nandroid. Not having a nandroid sucks because if you soft brick your phone you have no choice but to go completely back to stock. Not a great situation to be in.
Any root framework or application that requires modification of your system folder won't work.
There's no question paying $25 for sunshine is worth it.
3) here's the some definitions:
S-on = security flag on, system write protected
S-off = security flag off, system write enabled
Unlocked bootloader: ability to flash custom kernels and Recoveries.
Having access to a custom recovery is everything. Allows easy backup capabilities in case a rom modification goes bad. Allows super user permissions to be flashed directly into the system partition to allow permanent root. And gives you the ability to keep an unlocked bootloader without worry that Verizon will patch the current exploit.
Even on a stock rom it's worth it to have an unlocked bootloader. The modifications you're referring to require a custom recovery, and even if you could install them without it, it's still recommended to have a nandroid available in case your phone doesn't boot afterwards. I'm still running stock myself.
4) getting back to stock isn't easy. Verizon or HTC didn't release an official ruu. You'd have to flash the unofficial ruu, then turn your flags back to S-on, and hope it doesn't detect anything weird and flag your phone as tampered. The information was already linked to you in earlier posts, you just have to read up on it.
5) firewater stopped working on newer hardware versions, has nothing to do with firmware versions. There's no harm in trying it, but it most likely won't work on a new phone.
Sent from my HTC6525LVW using Tapatalk
BadUsername said:
1) sunshine is the only way to s-off if firewater doesn't work. It pushes an exploit that turns the secure flag off so s-off is achieved, then it pushes a separate exploit to unlock the bootloader. You may be able to change your phone carrier ID so htc dev can s-off your phone, but it doesn't do everything sunshine does.
2) without using sunshine you can still have temporary root with weaksauce, but it's really limited. Since your phone is still s-on, it isn't able to write to the system partition. It means you lose root on every reboot, and you have to wait up to a minute for weaksauce to root again.
Also without an unlocked bootloader you are unable to flash a custom recovery, which means you can't make a nandroid. Not having a nandroid sucks because if you soft brick your phone you have no choice but to go completely back to stock. Not a great situation to be in.
Any root framework or application that requires modification of your system folder won't work.
There's no question paying $25 for sunshine is worth it.
3) here's the some definitions:
S-on = security flag on, system write protected
S-off = security flag off, system write enabled
Unlocked bootloader: ability to flash custom kernels and Recoveries.
Having access to a custom recovery is everything. Allows easy backup capabilities in case a rom modification goes bad. Allows super user permissions to be flashed directly into the system partition to allow permanent root. And gives you the ability to keep an unlocked bootloader without worry that Verizon will patch the current exploit.
Even on a stock rom it's worth it to have an unlocked bootloader. The modifications you're referring to require a custom recovery, and even if you could install them without it, it's still recommended to have a nandroid available in case your phone doesn't boot afterwards. I'm still running stock myself.
4) getting back to stock isn't easy. Verizon or HTC didn't release an official ruu. You'd have to flash the unofficial ruu, then turn your flags back to S-on, and hope it doesn't detect anything weird and flag your phone as tampered. The information was already linked to you in earlier posts, you just have to read up on it.
5) firewater stopped working on newer hardware versions, has nothing to do with firmware versions. There's no harm in trying it, but it most likely won't work on a new phone.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
It also seems that firewater has nothing to do with hardware versions either. As I have a buddy with same hardware versions as me and FW worked perfectly. I am not exactly sure why FW works for some and not others.
---------- Post added at 08:07 AM ---------- Previous post was at 08:06 AM ----------
Also as far as changing CID I have not found a way to do this with out having S-Off already. If there is one please point me in the right direction. Thank you!
mdorrett said:
It also seems that firewater has nothing to do with hardware versions either. As I have a buddy with same hardware versions as me and FW worked perfectly. I am not exactly sure why FW works for some and not others.
---------- Post added at 08:07 AM ---------- Previous post was at 08:06 AM ----------
Also as far as changing CID I have not found a way to do this with out having S-Off already. If there is one please point me in the right direction. Thank you!
Click to expand...
Click to collapse
I guess I meant hardware variation, not version, it's not something you can simply check, but the internals of each phone is different. If htc used different manufacturers for the same internals it'll break firewater. The hardware version number would look the same.
Sent from my HTC6525LVW using Tapatalk
So I've read up on a good bit of what you've all posted - again thanks for that.
My M8 will be here tomorrow and I plan to use it for a few days without any tampering to ensure that I like the phone and that the reception in my home is adequate (problem had on my last upgrade attempt a year ago to a Razr M with Verizon). If all looks good, I will attempt the firewater method this weekend. If unsuccessful, I think my plan is probably to just play with the stock configuration for a month or two just to get used to working with a modern android version (I'm coming from a Droid 2 with large areas of pixel smear...so anything will be an improvement).
Hopefully, after a couple months if I am feeling like I want to tinker, sunshine will have come down in $$ or there is another working method. If not, I'll pay for it if I feel it's worth what I'll gain at that time. In all honesty, I like knowing I have the power to do whatever I want on my phone, but because I use my phone day in and out for business, I'm not often that adventurous in constant flashing ROMs as I want a very stable experience and don't want to take the time to constantly flash and restore.
I do have a few follow-up questions from some of my reading:
1) My understanding is that S-Off is also equivalent to a bootloader unlock. And that if you S-OFF, there is no need to also unlock the bootloader (it's either done as part of it, or simply not needed since S-Off overrides any boot lock). Is this correct?
2) Is CID unlock necessary to flash custom ROMs? Does doing a CID unlock also have the same benefit of a SIM unlock? Some pages I read indicate that setting to the superCID (11111111) is basically the same as a region unlock and therefore your SIM is also unlocked?
3) Since you can apparently gain temp root with weaksauce, is it possible to use this temproot with xposed framework? Or is S-off still required to apply the xposed framework modules?
thanks!
TraderJack said:
So I've read up on a good bit of what you've all posted - again thanks for that.
My M8 will be here tomorrow and I plan to use it for a few days without any tampering to ensure that I like the phone and that the reception in my home is adequate (problem had on my last upgrade attempt a year ago to a Razr M with Verizon). If all looks good, I will attempt the firewater method this weekend. If unsuccessful, I think my plan is probably to just play with the stock configuration for a month or two just to get used to working with a modern android version (I'm coming from a Droid 2 with large areas of pixel smear...so anything will be an improvement).
Hopefully, after a couple months if I am feeling like I want to tinker, sunshine will have come down in $$ or there is another working method. If not, I'll pay for it if I feel it's worth what I'll gain at that time. In all honesty, I like knowing I have the power to do whatever I want on my phone, but because I use my phone day in and out for business, I'm not often that adventurous in constant flashing ROMs as I want a very stable experience and don't want to take the time to constantly flash and restore.
I do have a few follow-up questions from some of my reading:
1) My understanding is that S-Off is also equivalent to a bootloader unlock. And that if you S-OFF, there is no need to also unlock the bootloader (it's either done as part of it, or simply not needed since S-Off overrides any boot lock). Is this correct?
2) Is CID unlock necessary to flash custom ROMs? Does doing a CID unlock also have the same benefit of a SIM unlock? Some pages I read indicate that setting to the superCID (11111111) is basically the same as a region unlock and therefore your SIM is also unlocked?
3) Since you can apparently gain temp root with weaksauce, is it possible to use this temproot with xposed framework? Or is S-off still required to apply the xposed framework modules?
thanks!
Click to expand...
Click to collapse
1) s-off is not equivalent to bootloader unlock, they are different things. S-off is needed to unlock bootloader.
2) super cid is only needed if swapping carriers, it allows another rom specific to any carrier to be flashed. If you flash any rom on Verizon it won't work, so you have to use a compatible Verizon rom anyways.
3) maybe, I never use xposed anyway because it breaks some apps I use. My guess is that it would be hit or miss depending on what the module does.
Sent from my HTC6525LVW using Tapatalk
TraderJack said:
So I've read up on a good bit of what you've all posted - again thanks for that.
My M8 will be here tomorrow and I plan to use it for a few days without any tampering to ensure that I like the phone and that the reception in my home is adequate (problem had on my last upgrade attempt a year ago to a Razr M with Verizon). If all looks good, I will attempt the firewater method this weekend. If unsuccessful, I think my plan is probably to just play with the stock configuration for a month or two just to get used to working with a modern android version (I'm coming from a Droid 2 with large areas of pixel smear...so anything will be an improvement).
Hopefully, after a couple months if I am feeling like I want to tinker, sunshine will have come down in $$ or there is another working method. If not, I'll pay for it if I feel it's worth what I'll gain at that time. In all honesty, I like knowing I have the power to do whatever I want on my phone, but because I use my phone day in and out for business, I'm not often that adventurous in constant flashing ROMs as I want a very stable experience and don't want to take the time to constantly flash and restore.
I do have a few follow-up questions from some of my reading:
1) My understanding is that S-Off is also equivalent to a bootloader unlock. And that if you S-OFF, there is no need to also unlock the bootloader (it's either done as part of it, or simply not needed since S-Off overrides any boot lock). Is this correct?
2) Is CID unlock necessary to flash custom ROMs? Does doing a CID unlock also have the same benefit of a SIM unlock? Some pages I read indicate that setting to the superCID (11111111) is basically the same as a region unlock and therefore your SIM is also unlocked?
3) Since you can apparently gain temp root with weaksauce, is it possible to use this temproot with xposed framework? Or is S-off still required to apply the xposed framework modules?
thanks!
Click to expand...
Click to collapse
1) No, s-off simply allows you to write to the /system partition and do some other stuff like RUU's and etc that i cant think of at the moment but no it is not equivalent to bootloader unlock. Bootloader unlocking allows you to flash recoveries, roms, scripts, kernels, etc. S-OFF allows the more advanced stuff like firmware flashing in fastboot. (at least I think that's what s-off does)
2) Super CID allows you to flash ROM's made for other carriers. So if you set your CID to super CID or another carriers CID then you could flash their ROMS and receive OTA Updates from them. It does not allow Sim unlock and or is not a Sim unlock.
3) I'm quite sure that weak sauce only allows access to /system/xbin but I may be wrong BUT in the case I'm right then no you cannot use xposed without S-OFF because without S-OFF you can't flash a system write enabled kernel to allow it.
Ok... so two more questions:
1) Verizon M8 is already SIM unlocked, correct?
2) I can see that firewater/sunshine do both an S-off and bootloader unlock. However, they don't seem to differentiate between these two things, simply stating they do both. Is there another stand-alone method to unlock the bootloader and if so, do you gain anything having an unlocked boot loader but not s-off? I know you can unlock the bootloader on all the other M8 variants via HTCdev, but they have blocked Verizon.
TraderJack said:
Ok... so two more questions:
1) Verizon M8 is already SIM unlocked, correct?
2) I can see that firewater/sunshine do both an S-off and bootloader unlock. However, they don't seem to differentiate between these two things, simply stating they do both. Is there another stand-alone method to unlock the bootloader and if so, do you gain anything having an unlocked boot loader but not s-off? I know you can unlock the bootloader on all the other M8 variants via HTCdev, but they have blocked Verizon.
Click to expand...
Click to collapse
1) No, you have to manually unlock it.
2) HTCDev is the only way that I've heard about for unlocking the bootloader alone & the only thing different is you wouldn't be able to flash firmware I believe.
S1L3nTShaDoWz said:
1) No, you have to manually unlock it.
Click to expand...
Click to collapse
http://htcsource.com/2014/06/how-to-sim-unlock-the-htc-one-m8-for-free/
"Verizon: the HTC One (M8) from Verizon is SIM unlocked right out of the box."
Also found this on Verizon's Global Ready policy FAQ:
http://www.verizonwireless.com/support/faqs/InternationalServicesandRoaming/faq_global_phone.html
"We do not lock our 4G LTE devices, and no code is needed to program them for use with another carrier."
Some info on this thread people seem to indicate it is already unlocked:
http://forum.xda-developers.com/showthread.php?t=2730159
So are those sources above incorrect? I can't find any guide on how to SIM unlock the M8 on verizon... this is why I'm thinking it was already unlocked?
TraderJack said:
http://htcsource.com/2014/06/how-to-sim-unlock-the-htc-one-m8-for-free/
"Verizon: the HTC One (M8) from Verizon is SIM unlocked right out of the box."
Also found this on Verizon's Global Ready policy FAQ:
http://www.verizonwireless.com/support/faqs/InternationalServicesandRoaming/faq_global_phone.html
"We do not lock our 4G LTE devices, and no code is needed to program them for use with another carrier."
Some info on this thread people seem to indicate it is already unlocked:
http://forum.xda-developers.com/showthread.php?t=2730159
So are those sources above incorrect? I can't find any guide on how to SIM unlock the M8 on verizon... this is why I'm thinking it was already unlocked?
Click to expand...
Click to collapse
It is sim unlocked, you can take it into any carrier and it'll work. The only reason it wouldn't work is if you don't have the correct bands to get LTE or GSM data.
Sent from my HTC6525LVW using Tapatalk
So i got my M8 yesterday and could already tell that reception wise it was much better than my previous upgrade attempt with the RAZR M.
Since there aren't a lot of options for customizable phones anymore with VZW, I've decided to keep it and am happy to report that firewater worked for me to S-OFF!
I had some issues with weaksauce and superSU...the latter not seeming to want to run, but eventually I determined that it wasn't necessary to actually run and update the app to get firewater to work (even though I never got any toast pop-ups from weaksauce after boot).
Firewater ran find and unlocke me after 4 bottle chugs.
I then had some problems loading on CWM. The reason is that on the CWM site the list the M8 down at the very bottom away from all the other HTC devices (including the HTC One - which they don't qualify as the M7 or M8). I accidentally flashed the recovery for the M7 since that is what was listed. After that I couldn't get into any recovery, although the phone still booted. When I realized what happened, I was a little peeved that they so carelessly listed these on their site that I chose not to continue using the stock CWM even though I prefer it's streamlined approach.
I went ahead an installed this version of PhilZ CWM:
http://forum.xda-developers.com/showthread.php?t=2725348
It sounded like you guys were praising this one, and I do prefer CWM. Even though it sounds like TWRP is more popular now, I saw several threads where it seemed like there were issues with TWRP doing funky stuff that CWM users didn't have issues with.
So, after I got that on I removed weaksauce and SuperSU.
What I would like to do now is probably reset to factory defaults and do a nandroid backup. Then, I would like to perma-root.
Some questions on this:
1) Do i need an SD card to nandroid backup? It appeared to work when I started a backup without an SD card...I didn't let it finish, but I'm not sure this method will work. I want to make sure I have a backup that I can use to revert to stock. I do have an sd card coming, but if I can do a successful backup without one I will go ahead.
2) Do I use all the default settings in Philz/CWM for the backup, or do I need to tweak anything in the advanced to ensure that I get *everything* that would be stock on the phone?
3) I saw some method that involved flashing a supersu update to get perma-root? Is this the best method?
Thanks again for all the help.
TraderJack said:
So i got my M8 yesterday and could already tell that reception wise it was much better than my previous upgrade attempt with the RAZR M.
Since there aren't a lot of options for customizable phones anymore with VZW, I've decided to keep it and am happy to report that firewater worked for me to S-OFF!
I had some issues with weaksauce and superSU...the latter not seeming to want to run, but eventually I determined that it wasn't necessary to actually run and update the app to get firewater to work (even though I never got any toast pop-ups from weaksauce after boot).
Firewater ran find and unlocke me after 4 bottle chugs.
I then had some problems loading on CWM. The reason is that on the CWM site the list the M8 down at the very bottom away from all the other HTC devices (including the HTC One - which they don't qualify as the M7 or M8). I accidentally flashed the recovery for the M7 since that is what was listed. After that I couldn't get into any recovery, although the phone still booted. When I realized what happened, I was a little peeved that they so carelessly listed these on their site that I chose not to continue using the stock CWM even though I prefer it's streamlined approach.
I went ahead an installed this version of PhilZ CWM:
http://forum.xda-developers.com/showthread.php?t=2725348
It sounded like you guys were praising this one, and I do prefer CWM. Even though it sounds like TWRP is more popular now, I saw several threads where it seemed like there were issues with TWRP doing funky stuff that CWM users didn't have issues with.
So, after I got that on I removed weaksauce and SuperSU.
What I would like to do now is probably reset to factory defaults and do a nandroid backup. Then, I would like to perma-root.
Some questions on this:
1) Do i need an SD card to nandroid backup? It appeared to work when I started a backup without an SD card...I didn't let it finish, but I'm not sure this method will work. I want to make sure I have a backup that I can use to revert to stock. I do have an sd card coming, but if I can do a successful backup without one I will go ahead.
2) Do I use all the default settings in Philz/CWM for the backup, or do I need to tweak anything in the advanced to ensure that I get *everything* that would be stock on the phone?
3) I saw some method that involved flashing a supersu update to get perma-root? Is this the best method?
Thanks again for all the help.
Click to expand...
Click to collapse
1) You don't need an SD card but I recommend it because if you ever encounter the dreaded "encryption" glitch that some AOSP ROM's have then you'll lose everything on your internal storage. I also recommend you back your Nandroid backups to your computer or some other sort of storage too so that if you ever encounter it or somehow manage to lose it then you can get it back.
2) It doesn't really matter what settings you choose or at least it never has for me but it should backup everything (ROM & apps)
3) Yes, that is the best method for getting perma-root is to flash the SuperSU zip in your recovery. You can find the latest version of the flashable zip at Chainfire's thread over here or the direct download link to the flashable zip here on his official website
Also I'd like to apologize for the invalid information I gave you yesterday on the SIM unlocking, my bad on that. I've had a cold for the past few days and it's been making me lazy lol.
S1L3nTShaDoWz said:
1) You don't need an SD card but I recommend it because if you ever encounter the dreaded "encryption" glitch that some AOSP ROM's have then you'll lose everything on your internal storage. I also recommend you back your Nandroid backups to your computer or some other sort of storage too so that if you ever encounter it or somehow manage to lose it then you can get it back.
2) It doesn't really matter what settings you choose or at least it never has for me but it should backup everything (ROM & apps)
3) Yes, that is the best method for getting perma-root is to flash the SuperSU zip in your recovery. You can find the latest version of the flashable zip at Chainfire's thread over here or the direct download link to the flashable zip here on his official website
Also I'd like to apologize for the invalid information I gave you yesterday on the SIM unlocking, my bad on that. I've had a cold for the past few days and it's been making me lazy lol.
Click to expand...
Click to collapse
1) Ok...but to get my first stock backup so I can proceed with everything else, it's safe to nandroid to internal memory? Where exactly will it place a nandroid backup if I don't have an SD card?
2) I was looking at the Misc Nandroid Settings like "include /preload" "use TWRP mode" etc. No reason to use anything but the defaults?
3) Cool...as soon as I have my nandroid I will go that route.
No worries about the SIM data...you guys have helped accelerate me pretty fast, and I'm thrilled that firewater worked. I'd now just like to get my full backup so I can begin fully migrating to the new phone and having fun
TraderJack said:
1) Ok...but to get my first stock backup so I can proceed with everything else, it's safe to nandroid to internal memory? Where exactly will it place a nandroid backup if I don't have an SD card?
2) I was looking at the Misc Nandroid Settings like "include /preload" "use TWRP mode" etc. No reason to use anything but the defaults?
3) Cool...as soon as I have my nandroid I will go that route.
No worries about the SIM data...you guys have helped accelerate me pretty fast, and I'm thrilled that firewater worked. I'd now just like to get my full backup so I can begin fully migrating to the new phone and having fun
Click to expand...
Click to collapse
Yeah it's safe, it will be stored in a folder called TWRP/Backups/Phone_Id_Here/ in the storage/emulated/0 folder (in root Explorer).
Also you can change them around to what you like, it doesn't matter.
& glad we could help!
Hello guys,
Don't know if I should root my phone..if I root my phone can I go totally stock without problems (no boot warning and so on)?
And also is there a solution to get Netflix in hdr and better resolution with unlocked bootloader?
And which why should I root / which apps are really recommend to let me root
manutoxic said:
Hello guys,
Don't know if I should root my phone..if I root my phone can I go totally stock without problems (no boot warning and so on)?
And also is there a solution to get Netflix in hdr and better resolution with unlocked bootloader?
And which why should I root / which apps are really recommend to let me root
Click to expand...
Click to collapse
You should post your question on https://forum.xda-developers.com/oneplus-7-pro/help
No, rooting requires you to unlock your bootloader which means you will get the boot warning. I think there was a workaround for previous phones but I wouldn't recommend it. Google forced OEMs to add the warning.
Judging by your questions though, I would seem that you already knew the answers.
First of all, please search the forum, or just take a look at the threads at least, before making new threads. There is already a lengthy discussion on this exact question, right on the top page of Q&A: https://forum.xda-developers.com/oneplus-7-pro/help/root-yes-t3936633
And another here: https://forum.xda-developers.com/on...ens-unlock-bootloader-features-loose-t3932323
And here: https://forum.xda-developers.com/oneplus-7-pro/help/advantages-unlocking-bootloader-t3938457
Note that unlocking the bootloader and root go hand in hand. So even though 2 of the thread subject lines refer to unlocking the bootloader, a lot of the discussion involves root as well.
We really don't need a new thread, every time someone comes on here that can't make their own decision about root/no root. A decision that can be based on readily available info, that existed even before the above discussions existed!
Feeling charitable today, so I'll answer your questions as well as I can (my responses below in red font):
manutoxic said:
Don't know if I should root my phone..if I root my phone can I go totally stock without problems (no boot warning and so on)?
Return to full stock ROM, and relocking the bootloader should get rid of the boot warning, etc. I haven't tried it personally (restore to stock) but do a search if you want to verify, the info probably exists.
And also is there a solution to get Netflix in hdr and better resolution with unlocked bootloader?
Not sure yet (just got the phone and rooted it). There is a modded Netflix apk (older version, not for this device specifically) that some folks say will get back the 720p. But others report that it is still only 480p with the modded apk. And no HDR (as the apk is an old version that doesn't support it).
And which why should I root / which apps are really recommend to let me root
Root isn't typically achieved with an "app". But there is a toolkit that performs most of the functions. Although, all you really need is a couple files, and typing a couple fastboot commands. And frankly, if you don't know how to you fastboot, you really shouldn't be messing with root in the first place. My recommendation would be the method: unlock the bootloader, fastboot boot TWRP, in TWRP flash the TWRP installer zip, flash Magisk root, done. Pretty easy, and I did it with zero issues.
Click to expand...
Click to collapse
A wise man once said: If you have to ask, don't root.
B3311 said:
A wise man once said: If you have to ask, don't root.
Click to expand...
Click to collapse
Mr. XDA said that