I've watched the video guides about Sunshine S-off but I'm still a bit confused. I currently have a non-rooted, S-ON HTC 10 with a locked bootloader (in other words it's factory new). I want to upgrade to Nougat when it becomes available in the EU, but since I want to have an "S-off LOCKED" + rooted phone I was told that doing the Sunshine method while still being on MM is the best thing to do. To do this, as far as I'm concerned I have to follow these steps:
1.) Download, run and purchase Sunshine.
2.) Select the S-off LOCKED option and start the process.
3.) This is where things become confusing. According to the videos I've watched, now my phone should be encrypted. Since I don't have TWRP, should I use the original recovery program's factory reset option?
4.) Flash TWRP, just like you had your bootloader unlocked. (If I flash TWRP on MM, will I still be able to use it on Nougat?)
5.) Wait for the Nougat OTA and install it. (The update should come automatically, right?)
6.) Root it.
After rooting, I would still get the OTA updates, right? (since I have my bootloader locked)
I would be grateful if someone could verify these steps. Thanks in advance!
bence.szij said:
I've watched the video guides about Sunshine S-off but I'm still a bit confused. I currently have a non-rooted, S-ON HTC 10 with a locked bootloader (in other words it's factory new). I want to upgrade to Nougat when it becomes available in the EU, but since I want to have an "S-off LOCKED" + rooted phone I was told that doing the Sunshine method while still being on MM is the best thing to do. To do this, as far as I'm concerned I have to follow these steps:
1.) Download, run and purchase Sunshine.
2.) Select the S-off LOCKED option and start the process.
3.) This is where things become confusing. According to the videos I've watched, now my phone should be encrypted. Since I don't have TWRP, should I use the original recovery program's factory reset option?
4.) Flash TWRP, just like you had your bootloader unlocked. (If I flash TWRP on MM, will I still be able to use it on Nougat?)
5.) Wait for the Nougat OTA and install it. (The update should come automatically, right?)
6.) Root it.
After rooting, I would still get the OTA updates, right? (since I have my bootloader locked)
I would be grateful if someone could verify these steps. Thanks in advance!
Click to expand...
Click to collapse
There is a lot of questions unanswered.
1. Why do you want S-OFF? Most people don't need it.
2. Do you want Nougat 2.28 full firmware, or only Nougat Android?
3. You need stock recovery to flash an OTA.
4. Current TWRP will not work on Nougat 2.28 firmware, and I think it won't work until HTC release official Kernel source.
5. If you want only the Android Nougat OS, while staying on MM 1.95 Firmware in order to be able to flash TWRP...then why not just flash Viper, ICE or LeeDroid custom ROM?
6. If you do flash custom N ROM, I believe that there are bugs due to using MM firmware. Something to do with Camera and Sound. It's all very complicated.
Summary: Describe what you want and we'll be able to tell you exactly what you need to do.
Kyuubi10 said:
There is a lot of questions unanswered.
1. Why do you want S-OFF? Most people don't need it.
2. Do you want Nougat 2.28 full firmware, or only Nougat Android?
3. You need stock recovery to flash an OTA.
4. Current TWRP will not work on Nougat 2.28 firmware, and I think it won't work until HTC release official Kernel source.
5. If you want only the Android Nougat OS, while staying on MM 1.95 Firmware in order to be able to flash TWRP...then why not just flash Viper, ICE or LeeDroid custom ROM?
6. If you do flash custom N ROM, I believe that there are bugs due to using MM firmware. Something to do with Camera and Sound. It's all very complicated.
Summary: Describe what you want and we'll be able to tell you exactly what you need to do.
Click to expand...
Click to collapse
Thanks for the anwser!
I'll try to anwser your questions (and ask new ones) as precisely as I can.
1.) I want S-OFF because that way the bootlocker can stay locked, and as I've heard you can go S-ON again with Sunshine. That way I don't really have to worry about the "relocked" state and warranty loss. Otherwise the HTCDev method would be perfectly fine for me.
2.) I didn't know that you can use the Nougat OS without upgrading your firmware. Could you please explain the differences between "Nougat 2.28 full firmware" and "Nougat Android"? I tried to do a research but I've failed
3.) So basically if I have TWRP the only way to install system updates is to flash them manually? Also if I stay with stock recovery while being S-off LOCKED will I get the OTAs? And what if I unlock the bootloader?
4.) When do you think HTC will release official Kernel source? Weeks? Months?
5.)- 6.) When I bought my phone in July, I decided not to root it immediately. I've planned to root after installing Android N, and since the EU release is near I've started researching on the process. The only reason I want to S-off now, while being on MM, is that Sunshine might not work after installing the Nougat OTA (I need Sunshine to protect my warranty). I'm not in a hurry, my goal is to have a phone with Nougat, TWRP, root and xposed (maybe an N version of Viper). I don't want to have a buggy phone. If running Nougat/Viper on an older firmware would cause bugs, I'd rather wait with the whole process until the OTA arrives, then install it and unlock my bootloader with HTCDev instead of achieving the "S-off LOCKED" state with Sunshine, even if this means warranty loss.
I hope I could explain things better this time.
bence.szij said:
Thanks for the anwser!
I'll try to anwser your questions (and ask new ones) as precisely as I can.
1.) I want S-OFF because that way the bootlocker can stay locked, and as I've heard you can go S-ON again with Sunshine. That way I don't really have to worry about the "relocked" state and warranty loss. Otherwise the HTCDev method would be perfectly fine for me.
2.) I didn't know that you can use the Nougat OS without upgrading your firmware. Could you please explain the differences between "Nougat 2.28 full firmware" and "Nougat Android"? I tried to do a research but I've failed
3.) So basically if I have TWRP the only way to install system updates is to flash them manually? Also if I stay with stock recovery while being S-off LOCKED will I get the OTAs? And what if I unlock the bootloader?
4.) When do you think HTC will release official Kernel source? Weeks? Months?
5.)- 6.) When I bought my phone in July, I decided not to root it immediately. I've planned to root after installing Android N, and since the EU release is near I've started researching on the process. The only reason I want to S-off now, while being on MM, is that Sunshine might not work after installing the Nougat OTA (I need Sunshine to protect my warranty). I'm not in a hurry, my goal is to have a phone with Nougat, TWRP, root and xposed (maybe an N version of Viper). I don't want to have a buggy phone. If running Nougat/Viper on an older firmware would cause bugs, I'd rather wait with the whole process until the OTA arrives, then install it and unlock my bootloader with HTCDev instead of achieving the "S-off LOCKED" state with Sunshine, even if this means warranty loss.
I hope I could explain things better this time.
Click to expand...
Click to collapse
If you're thankful press the thanks button, it would mean much more than saying you're thankful. It is there for a reason.
By seeing your answers my best advise will be, you don't need to S-OFF.
HTC explicitly states in their full T&C that your warranty is not completely void when you unlock bootload.
Your warranty just becomes conditional, which means that if you brick your device your warranty is void.
Or if any damage to the phone comes as a direct effect of you unlocking your bootloader, then warranty is void.
If the damage/fault is unrelated to you unlocking your bootloader then your warranty should still be AND will be valid.
Has been this way since I first joined the HTC bandwagon with the OneX.
Now regarding waiting for N before rooting. I also advise against this.
When the N sources are released you will be jumping into mostly BETA releases.
These tend to have a few bugs early on, I'd advise to root now while on M which is very stable and full of awesome features.
Wait around until N has some stable ROMs and Kernels.
Answering your other questions:
2) The firmware on your phone is your: "Bootloader, Radio, OpenDSP etc..." These are the deepest software on your phone, and for security and to avoid bricks should stay stock, unless you really know what you are doing. Firmware is not made by Google, but instead by the OEM. This is unique to the hardware on your phone. Android is made by google, and it can be divided into Kernel and OS/ROM.
3) S-OFF I don't know, but if you are S-ON with stock system and stock recovery you should always be able to install OTA even if you have unlocked bootloader.
4) I believe January.
Enjoy root and xposed on MM...get familiar with what is possible and learn as much as possible on a stable configuration.
Once you've learned a bit more about what root is capable of then move on to N when N is stable.
I suggest to learn how to use RUU.exe/RUU.zips before moving to N though.
Kyuubi10 said:
If you're thankful press the thanks button, it would mean much more than saying you're thankful. It is there for a reason.
By seeing your answers my best advise will be, you don't need to S-OFF.
HTC explicitly states in their full T&C that your warranty is not completely void when you unlock bootload.
Your warranty just becomes conditional, which means that if you brick your device your warranty is void.
Or if any damage to the phone comes as a direct effect of you unlocking your bootloader, then warranty is void.
If the damage/fault is unrelated to you unlocking your bootloader then your warranty should still be AND will be valid.
Has been this way since I first joined the HTC bandwagon with the OneX.
Now regarding waiting for N before rooting. I also advise against this.
When the N sources are released you will be jumping into mostly BETA releases.
These tend to have a few bugs early on, I'd advise to root now while on M which is very stable and full of awesome features.
Wait around until N has some stable ROMs and Kernels.
Answering your other questions:
2) The firmware on your phone is your: "Bootloader, Radio, OpenDSP etc..." These are the deepest software on your phone, and for security and to avoid bricks should stay stock, unless you really know what you are doing. Firmware is not made by Google, but instead by the OEM. This is unique to the hardware on your phone. Android is made by google, and it can be divided into Kernel and OS/ROM.
3) S-OFF I don't know, but if you are S-ON with stock system and stock recovery you should always be able to install OTA even if you have unlocked bootloader.
4) I believe January.
Enjoy root and xposed on MM...get familiar with what is possible and learn as much as possible on a stable configuration.
Once you've learned a bit more about what root is capable of then move on to N when N is stable.
I suggest to learn how to use RUU.exe/RUU.zips before moving to N though.
Click to expand...
Click to collapse
Thanks again!
I guess I'll do as you said and do it now. I have only one more question left then: let's say I unlock my bootloader with HTCDev, install TWRP, then root my phone and flash xposed. A few months later Nougat becomes stable and I decide to upgrade. In that case, I would be still using my current firmware, so N based roms would contain bugs, which I don't want. How can I upgrade my firmware in a situation like this?
bence.szij said:
Thanks again!
I guess I'll do as you said and do it now. I have only one more question left then: let's say I unlock my bootloader with HTCDev, install TWRP, then root my phone and flash xposed. A few months later Nougat becomes stable and I decide to upgrade. In that case, I would be still using my current firmware, so N based roms would contain bugs, which I don't want. How can I upgrade my firmware in a situation like this?
Click to expand...
Click to collapse
You're welcome, it's a pleasure to help.
An easy way of getting root is by flashing a custom ROM which already comes with root
I believe that quickly by Feb you should already have a stable N release.
Now to upgrade firmware... That's what the RUU part of my previous answer is for.
HTC are really rooting friendly, so much so they gave us a way to easily and quickly going back to stock. That is called an RUU.
You can search that more in detail to learn about it.
But to update firmware you have two ways, the fast way through RUU, or the slow way by flashing stock ROM via TWRP, then fastboot flash stock recovery and then flash the OTAs.
By doing RUU or via OTA method will update your firmware.
Keep in mind if you plan to use Android Pay or Pokemon Go, this may effect some your decision if you want to go s-off locked status or unlocked bootloader. Everything @Kyuubi10 said is good info, that's just something I would factor into consideration. There may be ways around having an unlocked bootloader and using Android Pay, I'm not the expert there because I don't want google having more of my financial information than they already have. But if you do use it or plan too, that might be something you need to take into consideration before you go unlocked and s-on.
I'm not talking you out of unlocking or anything, I just want you to know in case it's something you need to further consider.
CharliesTheMan said:
Keep in mind if you plan to use Android Pay or Pokemon Go, this may effect some your decision if you want to go s-off locked status or unlocked bootloader. Everything @Kyuubi10 said is good info, that's just something I would factor into consideration. There may be ways around having an unlocked bootloader and using Android Pay, I'm not the expert there because I don't want google having more of my financial information than they already have. But if you do use it or plan too, that might be something you need to take into consideration before you go unlocked and s-on.
I'm not talking you out of unlocking or anything, I just want you to know in case it's something you need to further consider.
Click to expand...
Click to collapse
Actually... I believe you can go unlocked and use android pay.
As long as you don't have root.
You can even have customROM and custom Kernel, but as long as you have no root, and no xposed you should be able to use Android Pay and Pokemon Go.
E.g. MultiROM with 1 rom non-rooted should be possible.
But I may be wrong, so don't quote me.
bence.szij said:
Thanks again!
I guess I'll do as you said and do it now. I have only one more question left then: let's say I unlock my bootloader with HTCDev, install TWRP, then root my phone and flash xposed. A few months later Nougat becomes stable and I decide to upgrade. In that case, I would be still using my current firmware, so N based roms would contain bugs, which I don't want. How can I upgrade my firmware in a situation like this?
Click to expand...
Click to collapse
You're lucky!
HTC released N sources yesterday!!
Will probably get a stable release by mid January.
Kyuubi10 said:
You're lucky!
HTC released N sources yesterday!!
Will probably get a stable release by mid January.
Click to expand...
Click to collapse
Thanks for the info! I've unlocked the bootloader yesterday and I'm planning to flash TWRP and SuperSU tonight?
bence.szij said:
Thanks for the info! I've unlocked the bootloader yesterday and I'm planning to flash TWRP and SuperSU tonight?
Click to expand...
Click to collapse
Don't worry about flashing SuperSU, usually it'll be included in the Custom ROM...if you want to use Custom ROM.
Or even TWRP gives you the option to enable SuperSU, if you wish to stay with stock ROM.
Related
I just got this phone. Android 4.2.2. I was wondering if rooting is still possible. I know that there are issues with unlocking the bootloader like, we can't. So can I still root and have the rooting goodies? If so, can you direct me to the correct method of rooting? All the methods I can find include unlocking the bootloader first and I don't know if I can just skip that step or not.
Thank you for your time.
Time To Shine said:
I just got this phone. Android 4.2.2. I was wondering if rooting is still possible. I know that there are issues with unlocking the bootloader like, we can't. So can I still root and have the rooting goodies? If so, can you direct me to the correct method of rooting? All the methods I can find include unlocking the bootloader first and I don't know if I can just skip that step or not.
Thank you for your time.
Click to expand...
Click to collapse
To answer your question you need to unlock/s-off your phone to root it, I would recommend running the rumrunner tool, installing a customer recovery and then install a custom rom. The reason I say install a custom rom even if you want to remain stock is because you can get a stock rom without any bloat. Most of the bloat apps on the HTC One and pretty much any phone, run in the background as soon as your phone starts, this eats battery life and performance. For a stock rom check out Santod040, he has a good stock rom released, personally I like NuSense and ViperOne they are both very solid roms.
Read this thread - http://forum.xda-developers.com/showthread.php?t=2473644 it is the Rumrunner tool. I believe as long as you DO NOT UPGRADE to 4.3 you can still root/unlock/s-off, after you unlock/s-off you can install whichever rom you like without worrying about losing the ability to have root access.
You will want to get into the bootloader to check which OS version you have and then download the corresponding version of Rumrunner.
Edit:
Be sure to backup your whole phone as soon as you install a customer recovery. After the backup is complete, save a copy on your computer. There will be times when you are tinkering with your phone that you will need to get your phone back to a factory state, you can use a RUU but in my opinion that is more complicated process and you have a higher risk of something going wrong compared to simply restoring a backup.
Okay. Thank you. I will look into this.
I've heard that using towelroot will root your phone but not unlock your bootloader. What does this entail? Can I still use Xposed Installer/ other root apps? Can I recieve OTA updates? Can I unroot again? Are there any downsides?
Looking forward to hearing about any experiences with this app.
Fakusnamus said:
I've heard that using towelroot will root your phone but not unlock your bootloader. What does this entail? Can I still use Xposed Installer/ other root apps? Can I recieve OTA updates? Can I unroot again? Are there any downsides?
Looking forward to hearing about any experiences with this app.
Click to expand...
Click to collapse
I just got my N7 and I unlocked the bootloader. I then used towelroot to root it and it worked fine. I have not flashed a custom recovery so I don't think OTA should be an issue.
But...
utsmaster18 said:
I just got my N7 and I unlocked the bootloader. I then used towelroot to root it and it worked fine. I have not flashed a custom recovery so I don't think OTA should be an issue.
Click to expand...
Click to collapse
It's just that some of my other devices (samsung ones, admittedly) don't get OTA updates since I've rooted them, even though they're available. I've also heard that rooting most devices sort of cuts off the updates, and that towelroot prevents that by leaving the bootloader alone.
Fakusnamus said:
It's just that some of my other devices (samsung ones, admittedly) don't get OTA updates since I've rooted them, even though they're available. I've also heard that rooting most devices sort of cuts off the updates, and that towelroot prevents that by leaving the bootloader alone.
Click to expand...
Click to collapse
After rooting you don't need to worry about updates with a nexus device (or any other really). As you'll notice in the N7 Android Development section, there are a TON of lollipop builds and it hasn't been officially released yet. In other words, all updates will be baked into custom ROM's so there's no need to worry about official updates. And to root a nexus, simply unlock the bootloader and flash a custom recovery like TWRP, there's no need for tools
DroidIt! said:
After rooting you don't need to worry about updates with a nexus device (or any other really). As you'll notice in the N7 Android Development section, there are a TON of lollipop builds and it hasn't been officially released yet. In other words, all updates will be baked into custom ROM's so there's no need to worry about official updates. And to root a nexus, simply unlock the bootloader and flash a custom recovery like TWRP, there's no need for tools
Click to expand...
Click to collapse
Ugh...Yeah I was aware of that. If you read my question again, that was not what I was asking for. My queries were about the towelroot application in particular and if I could recieve OTA updates if I left the bootloader alone. I did not ask for alternatives.
I don't understand why you would rely on an app for root with a locked bootloader on a Nexus device. It's so simple to unlock the bootloader and root. There's only, at a minimum, thousands of guides on how to do it. If you're worried about updates, unlock the bootloader.
nhizzat said:
I don't understand why you would rely on an app for root with a locked bootloader on a Nexus device. It's so simple to unlock the bootloader and root. There's only, at a minimum, thousands of guides on how to do it. If you're worried about updates, unlock the bootloader.
Click to expand...
Click to collapse
Because I've heard unlocking the bootloader stops OTA updates. I don't want to have to download roms as my download speed is abysmal. Google services have (on average) 8 times the normal download speed at my place (no idea why), so I'd much rather recieve OTA updates from Google than download a rom.
Just another thought and I get your question, but if you did unlock the boot loader and then just downloaded the factory image from here https://developers.google.com/android/nexus/images you WOULD be downloading it from Google so you should get the same speeds. Now I know you asked about towelroot and I've not used it, but if you're worried about download speeds the images in that link are directly from Google. I know what you mean though, I have very good download speeds and no matter what I download it does seem like the one's direct from Google are about 25% faster. They've got good networking that's for sure.
Fakusnamus said:
Because I've heard unlocking the bootloader stops OTA updates. I don't want to have to download roms as my download speed is abysmal. Google services have (on average) 8 times the normal download speed at my place (no idea why), so I'd much rather recieve OTA updates from Google than download a rom.
Click to expand...
Click to collapse
Heard that an unlocked bootloader prevents OTAs? I don't know where you heard that, but that's completely wrong. Bootloader state has absolutely no affect on OTAs. What an unlocked bootloader does is give you the ability to have complete control over your device. Flash any rom, flash any recovery, and never have to worry about losing root.
Take some time to read and learn before you start tinkering.
nhizzat said:
Heard that an unlocked bootloader prevents OTAs? I don't know where you heard that, but that's completely wrong. Bootloader state has absolutely no affect on OTAs. What an unlocked bootloader does is give you the ability to have complete control over your device. Flash any rom, flash any recovery, and never have to worry about losing root.
Take some time to read and learn before you start tinkering.
Click to expand...
Click to collapse
When I've rooted my phones in the past, I've stopped recieving OTA updates, even though they put out new ones. My friend who unlocked the bootloader on (and rooted) his nexus 7 also stopped recieving OTA updates. Are you saying that I can unlock bootloader and root my nexus 7 and I'll still receive OTA updates and/or can update to Lollipop when they release it a few weeks later for the device?
Fakusnamus said:
When I've rooted my phones in the past, I've stopped recieving OTA updates, even though they put out new ones. My friend who unlocked the bootloader on (and rooted) his nexus 7 also stopped recieving OTA updates. Are you saying that I can unlock bootloader and root my nexus 7 and I'll still receive OTA updates and/or can update to Lollipop when they release it a few weeks later for the device?
Click to expand...
Click to collapse
USUALLY it's a custom recovery that prevents OTAs not an unlocked bootloader or rooted device.
For example, I have a nVidia Shield which I prefer to get the OTAs for as the stock OS is perfect for my needs. Whenever an OTA is available, I have to reflash the stock recovery, apply the OTA and then I can flash a custom recovery again. I could have chosen to not use a custom recovery but I prefer to - so I just flash the stock one (1.0-3.0Mb size maybe?) and then back to custom after the OTA. takes 2min extra work before and after the OTA.
esmith13 said:
USUALLY it's a custom recovery that prevents OTAs not an unlocked bootloader or rooted device.
For example, I have a nVidia Shield which I prefer to get the OTAs for as the stock OS is perfect for my needs. Whenever an OTA is available, I have to reflash the stock recovery, apply the OTA and then I can flash a custom recovery again. I could have chosen to not use a custom recovery but I prefer to - so I just flash the stock one (1.0-3.0Mb size maybe?) abd then back to custom after the OTA. takes 2min extra work before and after OTA.
Click to expand...
Click to collapse
I can tell you for sure that neither me, nor my friend have flashed custom recovery. Still no updates.
Fakusnamus said:
I can tell you for sure that neither me, nor my friend have flashed custom recovery. Still no updates.
Click to expand...
Click to collapse
What android version and kernel date do you currently show in "About Tablet" at the bottom of the settings screen?
The best way is to use towelroot now, and backup your data with titanium backup, then you can unlock your bootloader if you want for lollipop.
esmith13 said:
What android version and kernel date do you currently show in "About Tablet" at the bottom of the settings screen?
Click to expand...
Click to collapse
I haven't done anything to the tablet yet, it's still brand new. That was my friend with the updateless tablet.
Fakusnamus said:
I haven't done anything to the tablet yet, it's still brand new. That was my friend with the updateless tablet.
Click to expand...
Click to collapse
Question still stands... What Android version and what Kernel date?
Okay...
Okay, this is going on a massive tangent. My question was : If I root the nexus 7 with towelroot, can I still update to lollipop when the update rolls out? What can or can't I do with towelroot? (except not flash custom recovery or roms)
Fakusnamus said:
I haven't done anything to the tablet yet, it's still brand new. That was my friend with the updateless tablet.
Click to expand...
Click to collapse
I don't have it on me right now, but its a brand new one, and I've done nothing to it, so whatever kernel that is. I'm guessing the android version is 4.3 .
esmith13 said:
Question still stands... What Android version and what Kernel date?
Click to expand...
Click to collapse
I don't have it on me right now, but its a brand new one, and I've done nothing to it, so whatever kernel that is. I'm guessing the android version is 4.3 .
Just unlock the bootloader now. It'll save you so much time and headache in the future.
Deleted
YouColdYet said:
Hi. I've been searching for this for quite some time now haven't get any result so I'm wondering if I can be helped by rooting my m8 .. The os is Marshmallow ... Don't wanna brick my phone so its best i asked before i do anything risky
Help!!
Click to expand...
Click to collapse
Hi. you have TWRP?
YouColdYet said:
Hi. I've been searching for this for quite some time now haven't get any result
Click to expand...
Click to collapse
The question was just recently asked and answered (answer applies whether you are GPE or Sense, you haven't specified): http://forum.xda-developers.com/htc-one-m8/help/root-htc-one-m8-gpe-t3285356
So briefly:
1) Unlock the bootloader by HTCDev.com
2) Install TWRP 2.8.7 by fastboot
3) Flash SuperSU 2.64 or later in TWRP
redpoint73 said:
The question was just recently asked and answered (answer applies whether you are GPE or Sense, you haven't specified): http://forum.xda-developers.com/htc-one-m8/help/root-htc-one-m8-gpe-t3285356
So briefly:
1) Unlock the bootloader by HTCDev.com
2) Install TWRP 2.8.7 by fastboot
3) Flash SuperSU 2.64 or later in TWRP
Click to expand...
Click to collapse
Okay thanks, I'm using sense forgot to mention that
Hi. I was s-on, rooted with twrp 2.8.7 on lollipop. went stock, bootloader and rom, updated to MM, wanna do root again. I remember I unlocked bootloader before - was it relocked in the process of going stock? How to check if it is unlocked? other steps 2 and 3 are quite clear by redpoint73
EDIT: yes the unlock was still intact. Managed to get twrp, made backup (thanks for advises), and when it prompted to install or not root, i decided yes... Stuck on boot logo, managed to restore. Now searching for 2.66 supersu and will try to root via twrp again. my m8 is not GPE. fingers crossed
edvinb said:
I unlocked bootloader before - was it relocked in the process of going stock? How to check if it is unlocked?
Click to expand...
Click to collapse
The only way for it to become locked/relocked again, is if you do so manually.
The bootloader screen will tell you the bootloader status: LOCKED, RELOCKED or UNLOCKED
edvinb said:
EDIT: yes the unlock was still intact. Managed to get twrp, made backup (thanks for advises), and when it prompted to install or not root, i decided yes... Stuck on boot logo, managed to restore.
Click to expand...
Click to collapse
The automatic root in TWRP isn't updated for MM, therefore doesn't work, and as you see results in no-boot.
edvinb said:
Now searching for 2.66 supersu and will try to root via twrp again.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
edvinb said:
Hi. I was s-on, rooted with twrp 2.8.7 on lollipop. went stock, bootloader and rom, updated to MM, wanna do root again. I remember I unlocked bootloader before - was it relocked in the process of going stock? How to check if it is unlocked? other steps 2 and 3 are quite clear by redpoint73
EDIT: yes the unlock was still intact. Managed to get twrp, made backup (thanks for advises), and when it prompted to install or not root, i decided yes... Stuck on boot logo, managed to restore. Now searching for 2.66 supersu and will try to root via twrp again. my m8 is not GPE. fingers crossed
Click to expand...
Click to collapse
You rooted your M8 succesfully? @edvinb
I wanna root on marshmallow , i wasnt rooted at all, so i just unblock bootloader, install twrp then flash that supersu 2.67 ?
Is this the correct procedure ? @redpoint73
Stock, S ON, locked bootloader, M8y 2.5 ghz asian version
yes, proceed, I successfully rooted my htc
So, after twrp you installed the newest supersu from redpoint link? @edvinb
Sent from my HTC One_M8 using Tapatalk
Callliope said:
So, after twrp you installed the newest supersu from redpoint link?
Click to expand...
Click to collapse
SuperSU 2.65 is marked as "stable", although any version after that are probably fine, as well.
http://forum.xda-developers.com/apps/supersu
Alternately, if you installed TWRP 3.0.0.0 or later, the built-in root will probably now work correctly on MM. This was not the case at the time of my last post (Post #6 above) where TWRP 2.8.7.0 was the latest version (and not updated to properly root MM).
true, it didn't boot when i tried supersu through the old twrp.
Is there any way available (mode or something) to enable native wifi tethering / wifi tethering on verizon htc one m8 (marshmallow)? I'm using non verizon gsm sim card, unlocked bootloader, s-off, rooted.
mamun.srdr said:
Is there any way available (mode or something) to enable native wifi tethering / wifi tethering on verizon htc one m8 (marshmallow)? I'm using non verizon gsm sim card, unlocked bootloader, s-off, rooted.
Click to expand...
Click to collapse
I answered you in your other post. Please don't post the same question in multiple places.
redpoint73 said:
I answered you in your other post. Please don't post the same question in multiple places.
Click to expand...
Click to collapse
Thanks. I was kind of desperate
Hi. I've been looking for a dummy's guide to rooting my m8. I'm in New Zealand so I'm guessing I have the international version, though I don't actually know how to check. I'm running marshmallow and sense 7. Redpoint73 Can you tell me if the brief instructions from your post on the first page will gain root for me without bricking my phone? I want to be able to install some of the flashy roms from the android development section. Thanks
bryce-bubbles said:
I've been looking for a dummy's guide to rooting my m8. I'm in New Zealand so I'm guessing I have the international version, though I don't actually know how to check. I'm running marshmallow and sense 7. Redpoint73 Can you tell me if the brief instructions from your post on the first page will gain root for me without bricking my phone? I want to be able to install some of the flashy roms from the android development section.
Click to expand...
Click to collapse
You won't brick the phone rooting or flashing a ROM. At least, the chances of bricking are so slim, its probably less likely than bricking from an official OTA update on a stock device. If you start messing with s-off mods, that is a different story. But s-on (and that is all you probably need) its nearly impossible to brick.
Yes, the process I described briefly in Post #3 above will work for just about any M8 variant, with the exception of Verizon.
Vomer's guide is pretty good, although not updated: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
You only need to follow the first parts of the guide that pertain to unlocking the bootloader, and installing custom recovery. And for those parts, I think the only thing that is outdated, is that (depending on your current firmware version) you should probably use a more recent version TWRP: https://dl.twrp.me/m8/
You actually don't need to root to install a custom ROM. Once you have custom recovery TWRP installed, just put the desired ROM on the phone, do a default wipe in TWRP, and flash the ROM.
For more specific help, and determining what M8 version you have: figure out how to use fastboot, then do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
If all this is new to you (and it sounds like it is) my advice is to start reading the available guides and starter threads. I don't personally like "dummy's guide" approaches. Reading and understanding fully, before doing anything, is a much better idea. You actually learn something that way, as opposed to "step-by-step" guides which do the opposite (you accomplish the task, but probably don't really remember or understand what you even did).
And if you have specific questions, just come back here; and we'll be happy to try and help.
redpoint73 said:
You won't brick the phone rooting or flashing a ROM. At least, the chances of bricking are so slim, its probably less likely than bricking from an official OTA update on a stock device. If you start messing with s-off mods, that is a different story. But s-on (and that is all you probably need) its nearly impossible to brick.
Yes, the process I described briefly in Post #3 above will work for just about any M8 variant, with the exception of Verizon.
Vomer's guide is pretty good, although not updated: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
You only need to follow the first parts of the guide that pertain to unlocking the bootloader, and installing custom recovery. And for those parts, I think the only thing that is outdated, is that (depending on your current firmware version) you should probably use a more recent version TWRP: https://dl.twrp.me/m8/
You actually don't need to root to install a custom ROM. Once you have custom recovery TWRP installed, just put the desired ROM on the phone, do a default wipe in TWRP, and flash the ROM.
For more specific help, and determining what M8 version you have: figure out how to use fastboot, then do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
If all this is new to you (and it sounds like it is) my advice is to start reading the available guides and starter threads. I don't personally like "dummy's guide" approaches. Reading and understanding fully, before doing anything, is a much better idea. You actually learn something that way, as opposed to "step-by-step" guides which do the opposite (you accomplish the task, but probably don't really remember or understand what you even did).
And if you have specific questions, just come back here; and we'll be happy to try and help.
Click to expand...
Click to collapse
Thank you so much for the detailed reply. It's given me the confidence I needed to go ahead with this.
I've had some experience. A few years ago I rooted and s-offed a htc sensation. Problem is its so long ago I've forgotten most of what I learned. Hopefully it'll come back to me as I get into it.
I wasn't aware you could flash roms without rooting. Would you be able to tell me what advantages rooting would allow me over simply flashing a rom?
bryce-bubbles said:
I've had some experience. A few years ago I rooted and s-offed a htc sensation. Problem is its so long ago I've forgotten most of what I learned. Hopefully it'll come back to me as I get into it.
Click to expand...
Click to collapse
I bet you'll do fine. The process isn't terribly complicated or difficult. And if you've done it before, then you know how to follow instructions properly, which is really all it takes.
If you get stuck, or have any specific questions; just come back here and ask, and we'll be happy to help.
bryce-bubbles said:
I wasn't aware you could flash roms without rooting. Would you be able to tell me what advantages rooting would allow me over simply flashing a rom?
Click to expand...
Click to collapse
Some folks like to stay on the stock ROM, but have root (such as for using apps that require root). Other than that preference (to stay on the stock ROM), I wouldn't say there are any "advantages". In the past, this setup (stock ROM, but rooted) may have allowed official OTA updates. But that is no longer the case, as even unrooting will still cause an OTA to fail due to "modified" software. Forcing you to restore the appropriate stock (never rooted) ROM in order to OTA. So that negates any advantage of staying on the stock ROM (and rooting) for OTA purposes.
Flashing custom ROM is for folks wanting something different from the stock ROM (and that sounds like your goal). All the custom ROMs are pre-rooted. So you have root, once you flash the ROM.
@redpoint73: i have a HTC one M8 eye. I try to flash twrp and it says success
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20046 KB)...
OKAY [ 2.139s]
writing 'recovery'...
OKAY [ 0.739s]
finished. total time: 2.883s
But then I cannot enter recovery. It keeps going to bootloader. Do you have any idea?
Hi,
So I'm new to these forums and have been browsing all of the rooting guides for my HTC M8. I am running official Marshmallow and really want to root my phone (again) as far I know I have unlocked boot loader. I had to factory reset my phone last year and never got round to re rooting, but now with marshmallow I wish to do so again.
My issue is I can't seem to understand the steps the guides are outlining. I download the links and try and open them, but nothing happens. Is there a step by step fluid guide in rooting my phone? As all the guides I have found have basically blown over my head. I used a toolkit in the past which did everything for me automatically. If no such post exists would someone be able to explain the steps in a simplified manner? (If possible)
Many thanks in advance to any who help
Optcpsi said:
as far I know I have unlocked boot loader
Click to expand...
Click to collapse
This is easy to determine definitely. Boot into bootloader (if you don't know how, ask and I'll explain) and it will either say bootloader is: LOCKED, UNLOCKED or RELOCKED near the top of the screen.
Vomer's guide is dated at this point, but mostly still accurate for what you want to do (root MM); and its the best guide I know of: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
If your bootloader is UNLOCKED, you can skip the whole section on unlocking it, and pick back up the guide again where it says CUSTOM RECOVERY. If the bootloader is LOCKED or RELOCKED, you'll need to do the section for unlocking the bootloader.
AFAIK, the only part of Steps 0 and 1 that is out of date, is the TWRP version. For MM, you should use TWRP 3.0. And somewhat obviously, the fastboot command to flash TWRP will need to have the corresponding file name; rather than the old version number given in the guide's example.
You'll also want to use SuperSU 2.76 (if the SuperSU version is too old, it will fail to root MM and leave you stuck with no boot). But the guide is already rigged to link to the latest stable version (not a particular version number), so presently it already links to 2.76.
Don't continue to Step 2 of the guide. Its not longer accurate, and not needed for root.
redpoint73 said:
This is easy to determine definitely. Boot into bootloader (if you don't know how, ask and I'll explain) and it will either say bootloader is: LOCKED, UNLOCKED or RELOCKED near the top of the screen.
Vomer's guide is dated at this point, but mostly still accurate for what you want to do (root MM); and its the best guide I know of: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
If your bootloader is UNLOCKED, you can skip the whole section on unlocking it, and pick back up the guide again where it says CUSTOM RECOVERY. If the bootloader is LOCKED or RELOCKED, you'll need to do the section for unlocking the bootloader.
AFAIK, the only part of Steps 0 and 1 that is out of date, is the TWRP version. For MM, you should use TWRP 3.0. And somewhat obviously, the fastboot command to flash TWRP will need to have the corresponding file name; rather than the old version number given in the guide's example.
You'll also want to use SuperSU 2.76 (if the SuperSU version is too old, it will fail to root MM and leave you stuck with no boot). But the guide is already rigged to link to the latest stable version (not a particular version number), so presently it already links to 2.76.
Don't continue to Step 2 of the guide. Its not longer accurate, and not needed for root.
Click to expand...
Click to collapse
Thanks for posting, couldn't find an up-to-date tutorial anywhere.
TWRP is asking to keep system read-only and I'm confused. If I allow modificaions, can I automatically never receive OTA updates again?
Will there even be another one for the M8/ will it get Nougat? Anyways, can I still root it with read-only?
Schmix said:
Thanks for posting, couldn't find an up-to-date tutorial anywhere.
TWRP is asking to keep system read-only and I'm confused. If I allow modificaions, can I automatically never receive OTA updates again?
Will there even be another one for the M8/ will it get Nougat? Anyways, can I still root it with read-only?
Click to expand...
Click to collapse
You need to allow modifications for root. At least traditional root. Systemless root, I would think would work if you stay read only - but do the research especially if you don't know the difference between traditional root and systemless root.
You can't install OTA updates with a rooted device in any case, so that point is irrelevant.
If/when ever an OTA comes, you would need to return to stock never rooted ROM and stock recovery, in order to OTA update (there are guides on this forum). This would remove any modification by TWRP.
But that's mostly just FYI/academic. Its extremely unlikely we'll get an OTA update to Nougat. Your best bet for Nougat will be custom ROMs, anyway.
1. UNLOCK bootloader with HTC Dev site.
2. Flash latest twrp recovery
3. Flash Stable v2.65 SuperSU
4. Flash wp mod.
5. Update SuperSU on Play Store.
Latest SuperSU 2.76 zip kills Boomsound. Permissive zip can fix that.
Hey all,
so i have (hopefully) read all those "I'm new to HTC"-threads and an almost infinite amount of additional threads all around the internet and especially here on xda in the htc 10 forum. I think i have figured it out so far, coming from a Galaxy S5 it's quite confusing sometimes as there i would have to get my hands on odin, flash twrp and from there on everything is super easy.
CID/MID
The CID of my device (HTC__034) shows me my device is unbranded and the region is europe. This is like the CSC over at samsung where DBT would be an unbranded german device?
The MID is an identifier for the model, it's model specific and should be the same throughout all regions and carriers (read this on some german android wiki site). It's like SM-G900F over at samsung?
Bootloader
The bootloader is locked by default. To be able to install a custom recovery, root, flash custom roms, etc. pp. i need to unlock the bootloader either over at htcdev (where they will store the information about me unlocking the bootloader) or through sunshine which will also S-OFF my device. Once the bootloader is unlocked, no more OTA updates except installing them "by hand"
S-ON/S-OFF
S-OFF is not needed to flash custom roms, but i may be stuck on some firmware version if it won't get updated anymore. To change firmware version i would need to S-OFF my device.
Also, to flash a radio i would need S-OFF. Is this radio you are all talking about what the modem is over at samsung?
S-ON is default, S-OFF is a sunshine exclusive, XTC2Clip won't work here anymore
Custom recovery
unlock bootloader and if wanted, S-OFF, fastboot install twrp
Root
flash supersu, systemless supersu or magisk and systemless phhsuperuser through twrp
Flashing roms
unlocked bootloader and custom recovery needed, then just flash this baby
Nice work, due diligence is rare these days
You got it all very close, your shouldn't have any trouble.
don't worry about S off
create an account at the HTC Dev website
on Dev site, select unlock bootloader and follow step by step
once bootloader is unlocked, "fastboot flash recovery twrp.img"
reboot into recovery and CREATE FULL BACKUP... save it somewhere safe...
at this point you are safe and don't need to worry about bricking your phone!
you are also now done with the computer, from this point on you can switch roms as much as you like with just your phone.
to install rom, save file to your phone, wipe system, dalvik/cache, then install new file, all from within twrp
Let me know if you need any help
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
Also just to clarify, it is basically the same thing as your s5, but you are replacing Odin with fastboot and adding the one step of unlocking your bootloader first. Don't worry about rooting at first because most custom roms will have it already rooted, so installing the rom will also root... Good luck
S1CAR1US said:
You got it all very close, your shouldn't have any trouble.
don't worry about S off
create an account at the HTC Dev website
on Dev site, select unlock bootloader and follow step by step
once bootloader is unlocked, "fastboot flash recovery twrp.img"
reboot into recovery and CREATE FULL BACKUP... save it somewhere safe...
at this point you are safe and don't need to worry about bricking your phone!
you are also now done with the computer, from this point on you can switch roms as much as you like with just your phone.
to install rom, save file to your phone, wipe system, dalvik/cache, then install new file, all from within twrp
Let me know if you need any help
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
Also just to clarify, it is basically the same thing as your s5, but you are replacing Odin with fastboot and adding the one step of unlocking your bootloader first. Don't worry about rooting at first because most custom roms will have it already rooted, so installing the rom will also root... Good luck
Click to expand...
Click to collapse
First of all, thanks for the answer, just a few more questions^^
S-OFF + unlocked bootloader -> this is what i have on my S5 right now. enabling me to flash and/or **** up everything.
for example take a firmware (bootloader, modem, rom) for s7 and brick my s5 or repartition with a pitfile or whatsoever if i want to
i am able to up-/downgrade firmware from (if it's there) nougat down to marshmallow and back up to nougat
S-ON + unlocked bootloader -> will only give me the possibility to flash new system partition (aka rom), a custom recovery, gain root access and (read about this) flash a kernel. but this won't allow me to update firmware, so as long as i'm on mm, no nougat for me except i relock my bootloader and flash a nougat RUU (check for right MID and CID).
2.1 do i have this right (about the firmware up-/downgrades)?
2.2 the RUUs are basically stock firmware?
S-OFF + locked bootloader
what is up with this configuration? have read it gives me the same options as S-ON and bootloader unlocked?
S-OFF would also allow me to relock bootlader without relocked flag, so it looks as if i never unlocked the bootloader?
AOSP-roms
what configuration do i need to flash aosp roms as soon as there are mor than alpha/beta builds? is S-ON + unlocked bootloader sufficient?
peteter said:
First of all, thanks for the answer, just a few more questions^^
S-OFF + unlocked bootloader -> this is what i have on my S5 right now. enabling me to flash and/or **** up everything.
for example take a firmware (bootloader, modem, rom) for s7 and brick my s5 or repartition with a pitfile or whatsoever if i want to
i am able to up-/downgrade firmware from (if it's there) nougat down to marshmallow and back up to nougat
S-ON + unlocked bootloader -> will only give me the possibility to flash new system partition (aka rom), a custom recovery, gain root access and (read about this) flash a kernel. but this won't allow me to update firmware, so as long as i'm on mm, no nougat for me except i relock my bootloader and flash a nougat RUU (check for right MID and CID).
2.1 do i have this right (about the firmware up-/downgrades)?
2.2 the RUUs are basically stock firmware?
S-OFF + locked bootloader
what is up with this configuration? have read it gives me the same options as S-ON and bootloader unlocked?
S-OFF would also allow me to relock bootlader without relocked flag, so it looks as if i never unlocked the bootloader?
AOSP-roms
what configuration do i need to flash aosp roms as soon as there are mor than alpha/beta builds? is S-ON + unlocked bootloader sufficient?
Click to expand...
Click to collapse
Best way is "S-OFF - LOCKED".
You have the same advantages as with "S-OFF - UNLOCKED", but with "S-OFF - LOCKED" you can go easily back to stock ("S-ON - LOCKED").
You can flash everything AND you can up-/ or downgrade your firmware. So AOSP roms are no problem for you
Never RELOCK your phone.
So the best way is: Unlock your phone with HTC Dev > Flash TWRP > Flash SuperSu > Install sunshine and choose inside the app "S-OFF - LOCKED".
If you want to go back to stock, just flash a RUU.zip and do the s-on command. Thats it.
But, if you still have a firmware version that's compatible with temp root, you don't need to unlock through HTC first. If you're going to spend the Sunshine money anyway, and if your FW version is compatible, go with Sunshine since the beginning.
Also, when you first run TWRP and it asks you if you want to make system writable, say NO. That way, you are able to backup everything untouched and get back to stock in case you want to take OTAs. There are guides that show you how to do it if you decide to stay stock + root/xposed.
Thank you all, so the way would be
download and install sunshine -> done
let sunshine run its tests (temproot etc) -> done and working
(from here on to be done)
pay 25$ and choose S-OFF + LOCKED -> done
fastboot flash recovery twrp.img -> done
i could also do this fastboot boot recovery twrp.img command and then also backup stock recovery? -> no longer available
boot up twrp, no to writable system -> done
nandroid backup (system image, boot) -> done
do what i want, flash custom-rom, aosp-rom, keep stock-rom, flash magisk and systemless phhsuperuser, flash supersu systemless or standard supersu, xposed and whatever makes me hit install in recovery -> done done done
also, never ever RELOCK in case i would S-OFF and UNLOCK
in case i missed something, please enlighten me else i'm of to gain freedom
dastinger said:
But, if you still have a firmware version that's compatible with temp root, you don't need to unlock through HTC first. If you're going to spend the Sunshine money anyway, and if your FW version is compatible, go with Sunshine since the beginning.
Click to expand...
Click to collapse
Okay, I forgot the sunshine temproot. I got my phone from repair last week with latest firmware and it wasn't working. I had to use HTC Dev to unlock first.
peteter said:
Thank you all, so the way would be
download and install sunshine -> done
let sunshine run its tests (temproot etc) -> done and working
(from here on to be done)
pay 25$ and choose S-OFF + LOCKED
fastboot flash recovery twrp.img
i could also do this fastboot boot recovery twrp.img command and then also backup stock recovery?
boot up twrp, no to writable system
nandroid backup
do what i want, flash custom-rom, aosp-rom, keep stock-rom, flash magisk and systemless phhsuperuser, flash supersu systemless or standard supersu, xposed and whatever makes me hit install in recovery
also, never ever RELOCK in case i would S-OFF and UNLOCK
in case i missed something, please enlighten me else i'm of to gain freedom
Click to expand...
Click to collapse
After your nandroid backup you have to reboot TWRP and allow writable system, or you can't flash anything a ROM
Not anything. You can still flash Magisk, Systemless Root, Systemless Xposed or a custom kernel. Basically, you can flash anything that doesn't mess with system. A ROM, for example, will need writable system ofc.
Once again, thanks a lot guys, installed twrp which is now asking me for a password. am i right that i have to enter my decrypt password?
EDIT: Just hit cancel worked
peteter said:
Once again, thanks a lot guys, installed twrp which is now asking me for a password. am i right that i have to enter my decrypt password?
EDIT: Just hit cancel worked
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-10/how-to/psa-htc-10-s-off-s-lock-unlock-t3371264
I got OTA updates with S-OFF I understand it's the recovery that will block OTA. What I did was S-OFF and HTC DEV unlocked bootloader I have not changed either one since. What I was doing to get latest firmware(for US UNLOCKED or developer edition) was flash a stock pmewl RUU not modify it and take OTAs to get the latest firmware. If you have the m10h in the USA, your LTE is crippled. You may want to convert to TMOUS or US unlocked. LTE will turn on at that point, however you won't get the full AWS spectrum. I use WCDMA(3.5G or HSDPA+) exclusively, unless I'm somewhere it won't work, like southern Denver, even then it's crippled. I quickly came to the conclusion that I need a PME with full AWS spectrum. I did have the device converted to US unlocked and on nougat within hours, nougat at the time was not available for my device out of the box. Another thing I sometimes go into recovery and find if didn't mount data partition. Simply re-flashing encryption compatible TWRP fixes this. Either a backup or image flash from TWRP. Or re-flash TWRP using TWRP app or dd from a terminal.
From my experience, whenever TWRP asks for a password that means data did not mount! The latest TWRP from twrp.me the official one is working fine for me.
The only problems I had were in trying to return to a fully stock condition.
Which is useful to do in case you maybe sell the phone after upgrading or something. And it very much depends on where you got your phone on how successful that attempt will be. For instance, my contract allows me to upgrade every two years, but the CID they use (H3G__001), despite the phone basically being unlocked, is not supported anywhere in the form of RUU. I had to S-OFF in order to be able to change the CID to HTC__001 which is the WWE CID but you can also change a significant amount of other stuff.
The other thing that being S-OFF makes easy is updating or rolling back firmware versions and different revisions of android require different firmwares (for instance between Marshmallow and Nougat)
Although, some of it has the potential to brick your phone, which being S-ON prevents. So it depends just how far you want to go and if you'd rather have that saftey net. But beyond that, you do not need S-OFF to install and run custom roms, or recoveries, etc.
Good points. It is risky to S-OFF, last time I flashed a write value to the safety state of an HTC modem was the Evo 4g, locked to Virgin Mobile when I got it. I had to cut a small section of a wire from an ethernet cable after flashing the unlock binary. Using that cable to ground contact points(at the risk of bricking) I read how to bypass some safety and get into diag mode writing some hex value to something else using fastboot.
I got into Android(and Linux) by hacking the HTC Touch Pro 2 and a laptop to flash it with. That was a Microsoft Phone. Using Haret, and installing Android Donut system/kernel images on the sdcard, you could boot into the Android Linux kernel and everything was loaded. It was slow, no cellular connection, it booted as a proof of concept.
Unpractical for daily use, I just kept Windows with the earliest version of the Sense interface, compulsively flashing every new Energy ROM. Then came the HTC HD2, the last Microsoft Phone(before Windows Mobile), my first practical Android phone. Started off booting Froyo using the same sdcard install and Haret psuedo bootloader method. Dark Forces group eventually formatted the EEPROM of the HD2 using a Linux friendly file system and moved Android from the sdcard to the internal memory. Adopting Linux kernel and vendor sources from the HTC Desire, the XDA community hacked together a fringe device.
I had a few HD2s running Android on a foreign device. Even bricked a couple of them flashing European radios. Only to restore them by buying the same not bricked devices with busted screens on eBay.
You can do things with an HTC, not possible otherwise using other Armel hardware . I mean try writing low level binary states to the modem of an Nexus device, not only to re define the locality of where the device was manufactured to function, but even downgrade firmware versions and the respective security patches.
Won't happen, not without Jtag and a few years of bricking devices while you earn an unrequited masters in computer science, as I imagine the phreakers/developers behind Sunshine must have.
My point, if I have one, is the raw potential before the OP and the device we're taking about.
To even look up a device on XDA demands a degree of user autonomy not encouraged by many manufactures. Like those that resort exclusively to advertising and pandering to made for TV "group think" expectations and attitudes of what a device is capable of. Only what is most profitable to most manufactures will work easily on the device without risk of destruction.
End users intolerant of bloatware and advertising, or limiting personal driving, shopping, usage and locality data to services they chose or at least use and know about. Those are examples of what's outside the stock ROM box.
The communications service industry as a whole will lose profits if they don't buy the majority of these inherently open devices and tailor them to fit, for the most part, their ends. I mean yeah, KNOX is secure, and that's a great cover story to isolate open development. Groups of independent developers, builders, and users can take technology in a direction different and less predictable than what is otherwise a profitable direction.
I like to imagine this fora as a nail in the coffin of computer hardware and software development that unnecessarily limits experimentation and inflates security risks to homogenize those capable individuals under the same or similar payroll. Focusing them on profit over communal benefit, as if we can't have both.