Related
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
jakeyo said:
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Hyun is looking for you at revolutionary irc channel.
Sent from my HTC Incredible S using Tapatalk
I know.. I have spoken to him.
jakeyo said:
I know.. I have spoken to him.
Click to expand...
Click to collapse
Any luck? still unable to flash anything?
jakeyo said:
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
If you go to the development section of the HTC Incredible 2 forum, attn1 has a script tool that uses the latest Revolutionary/Unreovked exploit to downgrade the ROMand HBOOT to a version that is supported by Revolutionary.
If you look at the script, it is pretty simple. You would just need to use an older Virgin Mobile RUU.zip instead of the Inc2 version. It looks like the 2.12.981.2 would be the one to try.
Hang on a second, how did you S-off the Hboot 1.16?
I thought you need S-off to be able to flash a custom Rom...
How did you install Miui?
Am I missing something here?
Doesnt matter if you need S-ON or S-OFF, as long as you get permissions to access root files.
Someone installed a custom bootloader so I can install custom ROM's, and it just works.... apparently the radios are locked though.
So, another day gone by and my phone is still not working. I can use MiUi, but I ran out of data on my 3g sim and wifi doesnt work, so now I have no internet on it.
katu2006 said:
Hang on a second, how did you S-off the Hboot 1.16?
I thought you need S-off to be able to flash a custom Rom...
How did you install Miui?
Am I missing something here?
Click to expand...
Click to collapse
I'm pretty sure no soff will cause the issues he is experiencing, though he doesn't seem to be listening
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
jakeyo said:
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
Click to expand...
Click to collapse
Yes im a noob that has been using android since 2009..
You seem like a supreme douche.
Weren't you the one who was crying about wanting to go back to his iphone lol
jakeyo said:
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
Click to expand...
Click to collapse
You're calling us noobs, but you don't even know what was done on your phone...
What's the following sentence supposed to say?
"It was the boot.img, we swapped it with the MiUi then put back the original one"
To get a custom Rom, you actually have to INSTALL it...To get the custom Rom installed, you need CWM recovery. But if you have HBoot 1.16.000, you can't have a custom recovery yet.
In less your "friend" did a downgrade of the HBoot to 1.13.000, it's unlikely that you have CWM recovery on your phone. Even so, to my knowledge HBoot 1.16.000 does a version check and won't let you downgrade it.
So, the question remains, how did you get CWM recovery on your phone?
katu2006 said:
You're calling us noobs, but you don't even know what was done on your phone...
What's the following sentence supposed to say?
"It was the boot.img, we swapped it with the MiUi then put back the original one"
To get a custom Rom, you actually have to INSTALL it...To get the custom Rom installed, you need CWM recovery. But if you have HBoot 1.16.000, you can't have a custom recovery yet.
In less your "friend" did a downgrade of the HBoot to 1.13.000, it's unlikely that you have CWM recovery on your phone. Even so, to my knowledge HBoot 1.16.000 does a version check and won't let you downgrade it.
So, the question remains, how did you get CWM recovery on your phone?
Click to expand...
Click to collapse
This thread is awesome
no, if I hold down power down and power button I see S-ON and HBOOT 1.16.0000
He typed in commands to give it root permissions, not sure exactly as he remote controlled my computer and typed it in. Then yes, he flashes CWM onto the phone then I installed revolutionary.
Firstly, I went onto the HTC dev site (created an account) and followed the steps to unlock the bootloader. In the end, it was successful, and once it's finished it will wipe the phone (AND WILL STILL SAY s-on)
So then the bootloader is now unlocked, and he did various commands in fastboot. My guess is that he installed CWM from there and it just worked.
at first, cyanogenmod would not boot, so he copied the (boot.img that is working) from MiUi and repled it with cyanogenmod's. The phone booted up and worked. Then he put it back how it was and it now works. Strange, but something must've given it a kick.
I'll repeat myself.
HBOOT 1.16.0000
S-ON
Cyanogenmod &.1 (stable)
Full root access
Need I say more to prove it?
As far as I know, I just cannot flash radios, which actually require the S-OFF....
sorry if I come across as rude, just a long day..
Talk to aftab565 he has the same hboot as you and has arhd running. Sounds like your phone was temp rooted and flashed and I would advise against letting people you don't know take remote access of your pc.
Hopefully it works for him I couldn't help.
Just replied to his thread.
And I know I was aware. I had full control though (could press a certain key to disconnect the connection - and only gave a temporary password) He was only typing in CMD things to do with the phone that I've heard of before
(ADB shell, fastboot recovery etc) and in the end worked well. He said my job is done and disconnect himself, so good guy
Didn't take my eyes off the screen either.
jakeyo said:
Just replied to his thread.
And I know I was aware. I had full control though (could press a certain key to disconnect the connection - and only gave a temporary password) He was only typing in CMD things to do with the phone that I've heard of before
(ADB shell, fastboot recovery etc) and in the end worked well. He said my job is done and disconnect himself, so good guy
Click to expand...
Click to collapse
You gotta give props to these guys for donating their time. Every day there's more talk about h-boot 1.16.0000 so I figure if devs want to keep devin there'll be a rev released eventually.
I really appreciate the amount of work hes done, in total I recon he's spent about 6 hours trying to help me getting it to work.
Never left me by myself, he always helped me through every step and was always there if I needed help. I've now got CM7 thanks to him. If he didn't fix it, I would have a useless phone because I couldn't even put on the stock ROM because of my HBOOT im guessing (I did an OTA update to get 1.16.0000 therefore too new to download)
I think SOME of the custom roms do have support for 1.16.0000 and what you only need is the boot file from them to boot up your non-booting ROM then you're all good.
ok, just to put some closure and sanity on this thread.
Firstly I'm probably bettery know as hyuh on #revolutionary, and it was me who was connected to his PC.
I use teamviewer to connect to people remotely, this allows anyone who doesn't like the look of *anything* I do to diconnect me...The user in front of the PC has full control of my session and I remind them to close teamviewer after we're done.
Secondly to those who think you need to be S-OFF to install a custom ROM or custom recovery, this is simply not true in the case of the 1.16 hboot. If you follow the HTC unlock procedure then you will have sufficient access to the phone to do this, it is not S-OFF just an unlock. Your phone will be in state "S-ON unlocked" This allows certain partitions on the emmc to be written to, and this sufficient for custom ROMs.
Really all that is requird is:
Code:
fastboot flash recovery <recovery.img>
then follow the normal flashing procedures.
In jakeyo's case CM7 would not boot, but MIUI would. When I say it would not boot I do not mean a boot loop here, I mean no boot period. At this point I had expected to need to rebuild a boot image for CM7 for him suspecting that HTC had done something different in the new hboot with paritions or the boot image offset.
The reason for flashing the MIUI boot image on top of CM7 was simple, to get to adb in the boot image. However seeing nothing particularly strange in the boot sequence ( other than the mismatch and resulting bootloop) I decided to reflash the CM7 boot image through fastboot.
The phone booted fully this time without issues.
It appears that the boot image simply did not flash properly from recovery the first time but I don't have a vivo to troubleshoot further.
A couple of things:
1. Don't take the OTA for 1.16 hboot if you haven't already done so.
There is currently no unofficial unlock/S-OFF
There is no RUU to fix the phone if you screw up.
There is nothing in the OTA you can't get in other ways.
2. If you're on 1.16 and want custom ROMs and aren't worried about warranty, go ahead and do unlock from HTC, but bear in mind:
There is no RUU, so you can't go back to stock
You can't flash radios
You can't superCID or similar ( but not needed since there is no RUU )
2a. You don't need any existing root method to exist, there is no exploit involved in any of this, this will work irrespective of the current status of a root expoit existing or not.
2b. The phone does not have to be listed by HTC as being supproted. Any phone with a suitable hboot can be unlocked.
if this:
Code:
fastboot oem get_identifier_token
returns an identifier code then the phone can be ulocked.
globatron said:
ok, just to put some closure and sanity on this thread.
Firstly I'm probably bettery know as hyuh on #revolutionary, and it was me who was connected to his PC.
I use teamviewer to connect to people remotely, this allows anyone who doesn't like the look of *anything* I do to diconnect me...The user in front of the PC has full control of my session and I remind them to close teamviewer after we're done.
Secondly to those who think you need to be S-OFF to install a custom ROM or custom recovery, this is simply not true in the case of the 1.16 hboot. If you follow the HTC unlock procedure then you will have sufficient access to the phone to do this, it is not S-OFF just an unlock. Your phone will be in state "S-ON unlocked" This allows certain partitions on the emmc to be written to, and this sufficient for custom ROMs.
Really all that is requird is:
Code:
fastboot flash recovery <recovery.img>
then follow the normal flashing procedures.
In jakeyo's case CM7 would not boot, but MIUI would. When I say it would not boot I do not mean a boot loop here, I mean no boot period. At this point I had expected to need to rebuild a boot image for CM7 for him suspecting that HTC had done something different in the new hboot with paritions or the boot image offset.
The reason for flashing the MIUI boot image on top of CM7 was simple, to get to adb in the boot image. However seeing nothing particularly strange in the boot sequence ( other than the mismatch and resulting bootloop) I decided to reflash the CM7 boot image through fastboot.
The phone booted fully this time without issues.
It appears that the boot image simply did not flash properly from recovery the first time but I don't have a vivo to troubleshoot further.
A couple of things:
1. Don't take the OTA for 1.16 hboot if you haven't already done so.
There is currently no unofficial unlock/S-OFF
There is no RUU to fix the phone if you screw up.
There is nothing in the OTA you can't get in other ways.
2. If you're on 1.16 and want custom ROMs and aren't worried about warranty, go ahead and do unlock from HTC, but bear in mind:
There is no RUU, so you can't go back to stock
You can't flash radios
You can't superCID or similar ( but not needed since there is no RUU )
Click to expand...
Click to collapse
Get a mod to make a hboot sticky there will be floods of this crap further down the road.
Big question:
If I want a custom ROM that will run root Apps that modify /system, is S-OFF required? Or are there custom ROMs with non-secure kernels?
More minor questions:
When developers (for the M7 etc) put out a custom ROM...
Are all putting out a kernel? are some signed/unsigned? are some secure/insecure?
Must you use a stock-signed kernel if you support folks with S-ON?
Can you boot unsigned kernels with just HTCDev UNLOCKED (and S-ON)? I assume yes, isn't this what CWM and TWRP run on?
S-OFF defeats the secure-kernels ability to keep /system prestine?
Thanks so much!!!
syserr said:
Big question:
If I want a custom ROM that will run root Apps that modify /system, is S-OFF required? Or are there custom ROMs with non-secure kernels?
More minor questions:
When developers (for the M7 etc) put out a custom ROM...
Are all putting out a kernel? are some signed/unsigned? are some secure/insecure?
Must you use a stock-signed kernel if you support folks with S-ON?
Can you boot unsigned kernels with just HTCDev UNLOCKED (and S-ON)? I assume yes, isn't this what CWM and TWRP run on?
S-OFF defeats the secure-kernels ability to keep /system prestine?
Thanks so much!!!
Click to expand...
Click to collapse
yes you can flash custom rom's with s-on and an unlocked bootloader, this is basically why HTC gave you the ability to unlock your bootloader, even they know most users use custom rom's and most are better than their own.
S-off is not required, however, s-off (security off) gives you the ability to do things like backflash, flash different RUU;s, and change firmwares, radios etc, but if you don't know what you are doing or unsure of yourself, it will also no longer stop you from flashing something wrong, making it very easy to mess up or even brick your phone.
and to answer your first question, ive yet to find a custom rom that doesn't come already rooted and with an unsecure kernel, but always be sure to read the op of which rom your interested in as it contains important instructions, even down to which version of recovery you should be using to flash the rom, you'd be very surprised about how many people actually get this wrong and then require help because their rom isn't booting because they couldn't be bothred to read the instructions, it will also state what type of kernel it comes with.
on a different note, you don't you don't have to flash a custom rom, if your happy with your current stock rom, you can just unlock the bootloader, flash a custom recovery and then flash an unsecure kernel like elementalx or kangaroo kernel etc, TWRP recovery itself will set up root for you on exit.
Seanie280672 said:
yes you can flash custom rom's with s-on and an unlocked bootloader, this is basically why HTC gave you the ability to unlock your bootloader, even they know most users use custom rom's and most are better than their own.
S-off is not required, however, s-off (security off) gives you the ability to do things like backflash, flash different RUU;s, and change firmwares, radios etc, but if you don't know what you are doing or unsure of yourself, it will also no longer stop you from flashing something wrong, making it very easy to mess up or even brick your phone.
and to answer your first question, ive yet to find a custom rom that doesn't come already rooted and with an unsecure kernel, but always be sure to read the op of which rom your interested in as it contains important instructions, even down to which version of recovery you should be using to flash the rom, you'd be very surprised about how many people actually get this wrong and then require help because their rom isn't booting because they couldn't be bothred to read the instructions, it will also state what type of kernel it comes with.
on a different note, you don't you don't have to flash a custom rom, if your happy with your current stock rom, you can just unlock the bootloader, flash a custom recovery and then flash an unsecure kernel like elementalx or kangaroo kernel etc, TWRP recovery itself will set up root for you on exit.
Click to expand...
Click to collapse
Thank you for your answer!
I'm beginning to think I don't need S-OFF. I want to be able to back flash and RUU back etc, but it's not necessary. I'm assuming you can back flash HBOOT, where as with S-ON you can never back flash HBOOT.
One thing concerns me... how are unsecure kernels made? (I believe ViperOne, was still secure when I was running it.) Do you have to compile from source? Or can your "unsecurize" a stock secure kernel? Or both?
Thanks!
syserr said:
Thank you for your answer!
I'm beginning to think I don't need S-OFF. I want to be able to back flash and RUU back etc, but it's not necessary. I'm assuming you can back flash HBOOT, where as with S-ON you can never back flash HBOOT.
One thing concerns me... how are unsecure kernels made? (I believe ViperOne, was still secure when I was running it.) Do you have to compile from source? Or can your "unsecurize" a stock secure kernel? Or both?
Thanks!
Click to expand...
Click to collapse
Its my belief that all kernals are built from the stock kernel or the kernel files available from the HTC Dev site, but as im not a developer I cant say for sure, although I would love to learn things like this I just don't have the time and know that it also requires Linux to build a kernal, im clueless when it comes to Linux, and yes it is possible to "unsecurize" a stock kernel, ModPack 007 for lollipop comes with the option to do this very thing, however don't start thinking that an unsecure kernel is so people can hack into your phone, or your phone is going to crash every 5 minutes, its not like that, its unsecure so that you can modify and replace system files etc, ie write protection removed = unsecure kernals.
Kernals like ElementalX and Kangaroo take the modding further than just removing write protection, they add many other features, which can generally be found in the op of each kernel.
If you want to back flash anything, HBOOT, Firmware, RUU etc then you need S-off full stop, theres no other way to do it.
As for S-on, I hate it, I feel totally locked down, im a very big HTC fan and cant wait for the M9, ive owned many HTC's and pretty much the first thing I do after unpacking it and messing about with it for a couple of hours is s-off it, it free's the phone up for anything, however if your not careful and don't know what your doing, you can very easily kill it, s-off means security off, so your device is no longer protected from a bad flash, with s-on it will just error out and boot again in most cases, s-off however in the same situation will turn your nice phone into a paper weight.
when I first got my HTC one M7 it came with HBOOT 1.56, very hard to s-off, firewater was the only tool that could do it, and kept failing, I must of flashed 50+ (probably and exaggeration) rom and kernel combinations to try and get firewater to work, all failed, this was before sunshine s-off was about, thankfully I found a shop in Sheffield which did it by java card, as I travel up there quite a bit it wasn't an issue to get it s-off'd next time I went up there.
Anyone please feel free to correct me if any of this is wrong, like I said im not a dev and its all a learning curve.
Seanie280672 said:
... and yes it is possible to "unsecurize" a stock kernel, ModPack 007 for lollipop comes with the option to do this very thing, however don't start thinking that an unsecure kernel is so people can hack into your phone, or your phone is going to crash every 5 minutes, its not like that, its unsecure so that you can modify and replace system files etc
Click to expand...
Click to collapse
Thanks for all the great info.
I should have clarified my concern about an unsecure kernel. Not that I was worried about getting hacked etc... More I was worried that my options would be limited to only ROMs with a limited number of unsecure kernels. If creating an unsecure kernel was difficult, I'd worry about a shortage. Booting into TWRP for unsecure kernel so I can modify /system is very restrictive to someone that is not used to it.
I compiled my first Linux kernel in 1995. I too want freedom. "Android" is a big field... but HTC and HBOOT are really outside of my Android experience -- it's great to learn so much. Thanks!
Let's not get into the whole debate that millions of others have about sunshine.
Anyway, I have seen conflicting information, and am somewhat confused. Many say you can still install custom roms with S-On and even install custom recoveries, while others say you can't install some roms unless you are S-Off.
Now, I know I can't flash a custom radio while S-On, or "convert" it into a play or dev or whatever edition.
I am fine with that (I assume I can still flash official radios released for it?), I don't want to convert it into a different type of M8 or switch carriers or anything. I just want to have rooted custom roms.
In that regard, just what would I be limited to exactly? Again, half the posts say you can still flash custom and rooted roms with S-On, and others say you need S-Off for custom roms, do they mean custom roms that are for dev/play/etc editions would require S-Off? Or are there custom roms designed for a regular Sprint M8 that would still need S-Off? Or am I even limited to only stock versions/mods of the Sprint rom? What about installing recoveries?
S-off isn't required to flash a ROM, but in some cases you have to flash the kernel separately from the ROM.
Do you mean that I won't be able to flash a kernel separately with S-on? I don't get that, won't roms flash the kernel and other key files to the system partition (which I assume you need to format first before flashing the rom) anyway?
Cyber Akuma said:
Do you mean that I won't be able to flash a kernel separately with S-on? I don't get that, won't roms flash the kernel and other key files to the system partition (which I assume you need to format first before flashing the rom) anyway?
Click to expand...
Click to collapse
Hit the second link in my sig and read the section pertaining to S-on kernel flashing.
I don't understand, what do you mean that you can't write to the /system partition permanently if you are S-On? Wouldn't you need to be able to write to the system partition in order to flash a custom rom your phone?
Cyber Akuma said:
I don't understand, what do you mean that you can't write to the /system partition permanently if you are S-On? Wouldn't you need to be able to write to the system partition in order to flash a custom rom your phone?
Click to expand...
Click to collapse
Meaning any changes that you make are only temporary and won't survive a reboot.
Though again, changes like installing a custom ROM? Or do you not need access to /system to install a custom rom?
It certainly helps to have S-OFF, but I haven't found it all that necessary. I'm currently on the ViperOneM8 3.2.1 with S-ON, and I'm not having any issues. Nothing that cannot be fixed anyway. At one point, I had ran into some trouble when I installed Sense 6 Toolbox (Xposed Mod), played with some settings and then uninstalled it. The trouble was with Venom Tweaks, it just wouldn't run. Thankfully I had a back-up, loaded it up, and it's all good. Other than that, no problem. And I'm not even sure if S-ON was the problem, but I'm assuming that the reason why Venom couldn't boot up was because it had no permission to overwrite some stuff that the xmod sense 6 toolbox left behind. I'm just guessing of course, I'm probably wrong.
But yeah, I would give ViperOneM8 a try, though be careful. Make sure you have all the right firmware installed BEFORE you start doing any rooting. It will save you a lot of headache.
Amer28 said:
At one point, I had ran into some trouble when I installed Sense 6 Toolbox (Xposed Mod), played with some settings and then uninstalled it.
Click to expand...
Click to collapse
Amer28 said:
I'm assuming that the reason why Venom couldn't boot up was because it had no permission to overwrite some stuff that the xmod sense 6 toolbox left behind. I'm just guessing of course, I'm probably wrong.
Click to expand...
Click to collapse
Sorry to keep going on about this, but I am still confused. If you can't permanently write to the /system partition, how were you able to install tools that modify system files? You mentioned that you think the reason was that the Toolbox software you installed left some modified files behind, if S-On means you can't permanently modify those files then how did they survive a reboot?
Would I be able to install a security application like avira onto the system partition with S-On? It has an option to install itself, and it's settings, into a rooted phone so the application (and it's settings) cannot just be wiped from a factory reset. Wouldn't it need to write to the system partition in order to do that?
Come to think of it, I know you can install another bootloader and/or recovery once you are rooted, but wouldn't you also need to be able to access the system partition in order to be able to do that?
I don't get what this unable to permanently write to the system partition while S-On entails since it seems like many things do permanently write to it still.
Cyber Akuma said:
Sorry to keep going on about this, but I am still confused. If you can't permanently write to the /system partition, how were you able to install tools that modify system files? You mentioned that you think the reason was that the Toolbox software you installed left some modified files behind, if S-On means you can't permanently modify those files then how did they survive a reboot?
Would I be able to install a security application like avira onto the system partition with S-On? It has an option to install itself, and it's settings, into a rooted phone so the application (and it's settings) cannot just be wiped from a factory reset. Wouldn't it need to write to the system partition in order to do that?
Come to think of it, I know you can install another bootloader and/or recovery once you are rooted, but wouldn't you also need to be able to access the system partition in order to be able to do that?
I don't get what this unable to permanently write to the system partition while S-On entails since it seems like many things do permanently write to it still.
Click to expand...
Click to collapse
I'm not hundred percent sure on this. I don't do any modding or anything myself, but it is my understanding that you actually 'can' write to the system partition. Just not 'some' stuff. It's essentially like having safe mode on, it just ensures that you don't completely brick the phone.
Again, please do not quote me on any on this. I'm merely humoring the subject, not an expert in any sense of the word.
You can flash virtually any custom ROM with S-On as long as you unlock your Bootloader at HtcDev... I can explain details later on, I am just busy atm...
---------- Post added at 11:09 PM ---------- Previous post was at 10:19 PM ----------
Some more details:
Basically you have 2 options to enable Custom Roms on the HTC One M8
1. Unlock bootloader at http://www.htcdev.com/bootloader/
2. Gain S-Off
For 99% of the ROMs it makes no difference which way you go. You can flash a custom recovery with both ways and you can flash custom ROMs with both ways. There is no such thing as a limitation during writing /system.
The difference is that with S-Off you can change your device IDs (e.g. CID) and in consequence you can flash firmware (like radio firmware, adsp firmware, etc.) that is not meant for your device. So playing with S-Off is quite "risky" you can "easily" achive a brick.
With S-On, you can only flash firmware which is signed for your device.
I would give the recommendation as follows: If you decide to go with S-On (which I would do if you have no specific reason for S-Off) then after flashing a custom recovery, take a backup of your stock ROM. Then, when you need a update of the firmware components, you can restore that backup, flash stock recovery, relock bootloader and use stock OTA to update all firmware components consistently.
elandroido said:
Then, when you need a update of the firmware components, you can restore that backup, flash stock recovery, relock bootloader and use stock OTA to update all firmware components consistently.
Click to expand...
Click to collapse
Wait, so I can't flash an updated radio if I am on a custom rom even if that radio was officially released for my device? I thought even with S-On you would still be able to flash a radio if it was officially released and signed for your device?
Well you can flash a radio which is signed for your device. But the safer way imho is to go the OTA way, because that really dates up everything. There might be other firmware components that can receive an update and when you go OTA everything stays consistent. But oft course you can also take the manual way, if you find a proper firmware zip.
Cyber Akuma said:
Wait, so I can't flash an updated radio if I am on a custom rom even if that radio was officially released for my device? I thought even with S-On you would still be able to flash a radio if it was officially released and signed for your device?
Click to expand...
Click to collapse
You can flash the full, signed firmware such as what OMJ provides in his RUU thread, but you cannot flash unsigned firmware to your device while S-on. You can still update your radios, you just have to jump through a few more hoops to do so, unlike those who have S-off.
You might want to take a look at the first post in the thread linked below for more info:
http://forum.xda-developers.com/showthread.php?t=1680928
Well I've finally rooted my HTC One M7 after months of saying I'll do it soon, I've also flashed the latest CWM recovery on there but now my question is what do I do now? I've downloaded some apps that need root permissions but nothing great. What I want is an OS that uses minimal RAM and battery. I've seen LiquidOS but that runs Android KitKat, are there any that run on Android Lollipop?
Thanks
AJHylton said:
Well I've finally rooted my HTC One M7 after months of saying I'll do it soon, I've also flashed the latest CWM recovery on there but now my question is what do I do now? I've downloaded some apps that need root permissions but nothing great.
Click to expand...
Click to collapse
Normally you only root a phone if you need to use something that requires root privileges. Its like saying: I finally managed to open that locked door to access this room where there is nothing inside that I really need... now what?
What I want is an OS that uses minimal RAM and battery. I've seen LiquidOS but that runs Android KitKat, are there any that run on Android Lollipop?
Click to expand...
Click to collapse
If you want to flash a custom rom, you don't need to root, only need to unlock the bootlaoder and flash a custom recovery (like you already did in the process of rooting). Most custom roms are pre-rooted anyway. There a lot of lollipop roms out there, check in the development section of this forum (Sense 6/7 + Lollipop or GPE lollipop). What will be the best rom for you? Its hard to tell, test a few one yourself, its the best way to find out. If you want something stripped down then probably a GPE rom will fit your needs otherwise if you prefer to have a more "complete" experience I would say go with Sense (6 or 7) rom.
alray said:
Normally you only root a phone if you need to use something that requires root privileges. Its like saying: I finally managed to open that locked door to access this room where there is nothing inside that I really need... now what?
If you want to flash a custom rom, you don't need to root, only need to unlock the bootlaoder and flash a custom recovery (like you already did in the process of rooting). Most custom roms are pre-rooted anyway. There a lot of lollipop roms out there, check in the development section of this forum (Sense 6/7 + Lollipop or GPE lollipop). What will be the best rom for you? Its hard to tell, test a few one yourself, its the best way to find out. If you want something stripped down then probably a GPE rom will fit your needs otherwise if you prefer to have a more "complete" experience I would say go with Sense (6 or 7) rom.
Click to expand...
Click to collapse
I'd like to add - change recovery to TWRP as it's recomended for most ROMs out there
Thank you, I think I'm going to go for ViperOne by Team Venom (http://forum.xda-developers.com/showthread.php?t=2334294)
This is the first time I'll be doing this so any tips or anything you'd advise me on doing?
Thank you
AJHylton said:
Thank you, I think I'm going to go for ViperOne by Team Venom (http://forum.xda-developers.com/showthread.php?t=2334294)
This is the first time I'll be doing this so any tips or anything you'd advise me on doing?
Thank you
Click to expand...
Click to collapse
yep,
Do a Nandroid backup of your current setup before flashing anything so if something goes wrong, you can simply restore that backup and use your phone. Better to save the backup your computer so if its wiped from the phone accidentally, you still have a copy.
read the OP of the ROM you want to flash twice before proceeding
Newer Sense roms (lollipop) requires a recent firmware on your phone to work properly (a 7.xx.xxx.x version). Confirm that before flashing the rom using "fastboot getvar all". The version-main number is your firmware version.
Ask questions if you are unsure about something, better than bricking your phone
You might also want to check if there is a RUU to return your phone back to stock in case you need to in the future. (your version-main will tell you the RUU version you'll need)
alray said:
yep,
Do a Nandroid backup of your current setup before flashing anything so if something goes wrong, you can simply restore that backup and use your phone. Better to save the backup your computer so if its wiped from the phone accidentally, you still have a copy.
read the OP of the ROM you want to flash twice before proceeding
Newer Sense roms (lollipop) requires a recent firmware on your phone to work properly (a 7.xx.xxx.x version). Confirm that before flashing the rom using "fastboot getvar all". The version-main number is your firmware version.
Ask questions if you are unsure about something, better than bricking your phone
You might also want to check if there is a RUU to return your phone back to stock in case you need to in the future. (your version-main will tell you the RUU version you'll need)
Click to expand...
Click to collapse
Thank you very much I think I'm ready to do it I just need to flash TWRP recovery on as I have CWM, the only 2 questions I have are;
Do I need to do anything with the bootloader, its currently unlocked but I've read on other forums some of them require the bootloader to be locked but S-Off or something? There's nothing about this in the Viper install instructions I'm just wondering if it's relevant?
Also an RUU, is that basically a recovery file with an OS? If so would I still need to look into this if I've already done a Nandroid backup?
Thank you for all your help.
AJHylton said:
Thank you very much I think I'm ready to do it I just need to flash TWRP recovery on as I have CWM, the only 2 questions I have are;
Do I need to do anything with the bootloader, its currently unlocked but I've read on other forums some of them require the bootloader to be locked but S-Off or something? There's nothing about this in the Viper install instructions I'm just wondering if it's relevant?
Also an RUU, is that basically a recovery file with an OS? If so would I still need to look into this if I've already done a Nandroid backup?
Thank you for all your help.
Click to expand...
Click to collapse
You don't need S-OFF to flash a custom rom, only an unlocked bootloader with a custom recovery.
A RUU is a factory image. It can reflash the software and firmware back to stock if needed. Its useful to know if there is one for your phone just in case you can't restore your phone using your backup for whatever reason. Tell me what your version-main is and I'll tell you if there is a RUU somewhere.
alray said:
You don't need S-OFF to flash a custom rom, only an unlocked bootloader with a custom recovery.
A RUU is a factory image. It can reflash the software and firmware back to stock if needed. Its useful to know if there is one for your phone just in case you can't restore your phone using your backup for whatever reason. Tell me what your version-main is and I'll tell you if there is a RUU somewhere.
Click to expand...
Click to collapse
Apologies this is a really noob question but how do I find that out because I've been looking at it says about using fastboot in a command window but all I get is "Waiting for device"
edit: apologies I just realised I had to actually be in fastboot mode *duhh* my version main is - version-main: 7.19.401.30
Thank you
AJHylton said:
Apologies this is a really noob question but how do I find that out because I've been looking at it says about using fastboot in a command window but all I get is "Waiting for device"
edit: apologies I just realised I had to actually be in fastboot mode *duhh* my version main is - version-main: 7.19.401.30
Thank you
Click to expand...
Click to collapse
There is no RUU for 7.19.401.30 but there is one for 7.19.401.22 which can be used on your phone if needed in the future. :good:
Hello,
this is just to be sure.
My m7 is out of warranty so I want to try a different ROM.
Either viperone or revolution hd. (unless you guys suggest another one?)
I was reading that I need root to install a rom? is this correct?
also, to root i need to s-off? no? "you will not be able to root or flash a custom ROM unless your turn S-Off" - as in here.
I was trying to S-off with Sunshine from the root ninja... the phone PASSED the first test, but the second was an attemp to Temproot.. which it failed...
Am i doing anything wrong here? shouldn't the phone first be s-off to be able to be rooted?
Thank you!
I was reading that I need root to install a rom? is this correct?
Click to expand...
Click to collapse
You don't need root to install a custom rom, only an unlocked bootloader (+ a custom recovery to flash the rom). You'll often find false statements like this here and there simply because they're some ppl not really understanding the difference between Root/Unlocked bootloader/S-Off bootloader. And also because you're trying to get information from really outdated page like the one you've linked
also, to root i need to s-off?
Click to expand...
Click to collapse
You don't need s-off to root, you only need an unlocked bootloader (+ a custom recovery to flash the super user binaries)
I was trying to S-off with Sunshine from the root ninja... the phone PASSED the first test, but the second was an attemp to Temproot..
Click to expand...
Click to collapse
You need root to use Sunshine but again you don't need S-OFF neither ROOT to flash a custom rom and BTW most custom roms are pre-rooted.
1-Unlock your bootloader
2-Flash the latest TWRP recovery
3-Flash your rom
What root does: Give your Super User access in the ROM
What an unlocked bootloader does: Disables signature verification and write protection for /recovery, /system /radio, /boot partitions so you can flash custom recovery, custom rom, radio, custom kernel.
What S-OFF does: Disables signature verification and write protection to all 37 partitions, gives you endless possibilities including turning your phone into a really expensive paper weight if you don't know what you're doing.
regrettably your answer doesn't help...unlock bootloader, unlock bootloader.....makes an incorrect assumption that the oem unlock is available.
It seems from 1.61 they have removed this option. at least it appears that Vodafone has joined Verizon in this case, and i assume for the others too.
i previously rebranded and s-off and foolishly restored to factory branding/etc and now decided i need to use the phone and am stuck with crap.
moral of the story.....never get one of these $1 phone deals and end up w