Related
will there be a simple root for 2.2? i hear unrevoked isnt trusted t be a full root
In due time
Sent from my PC36100 using XDA App
Rocklee99 said:
will there be a simple root for 2.2? i hear unrevoked isnt trusted t be a full root
Click to expand...
Click to collapse
Unrevoked 3 isn't a "full root", but it is when combined with Unrevoked Forever.
Sent from my HummerPhone using the XDA App
A fulll root and s-off is being worked on for 2.2 OTA.
Noxious Ninja said:
Unrevoked 3 isn't a "full root", but it is when combined with Unrevoked Forever.
Sent from my HummerPhone using the XDA App
Click to expand...
Click to collapse
You are correct.
Sent from my PC36100 using XDA App
Unrevoked isn't exactly needed to root 2.2. Once you've returned to stock 2.1, you can use whatever 2.1 root method you want - I used SimpleRoot.
Beknatok said:
Unrevoked isn't exactly needed to root 2.2. Once you've returned to stock 2.1, you can use whatever 2.1 root method you want - I used SimpleRoot.
Click to expand...
Click to collapse
Once again: The term full root is completely meaningless. You either have root, in which case you can run code as the root user, or you do not. There is no "full root" and there is no "partial root."
There is, in addition to the normal linux access control model, a NAND lock, implemented in hardware, on these phones. This means that without a particular exploit or an ENG bootloader, there is no way to reflash a partition. Luckily, an ENG bootloader was "obtained" "in some way" from HTC. I am not sure of the legal standing of said code, but "it's worked so far."
Now, the ENG bootloader is a signed update. This means that you have to flash the whole thing: you lose all your data, and you lose your 1.40PRI. Also, since the phone is not well and truly S-OFF, if you accept an OTA, you lose your unlocked NAND.
On the other hand, unrevoked forever ALSO unlocks NAND, and it does so at a level below the radio. This means that the update is permanent. If you accept an OTA, S-OFF remains. If you RUU, S-OFF remains. You can flash our s-on.zip update to revert it. Furthermore, every line of code in Unrevoked Forever was developed by us. HTC has no legal standing to tell us to remove it.
rpearl said:
Once again: The term full root is completely meaningless. You either have root, in which case you can run code as the root user, or you do not. There is no "full root" and there is no "partial root."
There is, in addition to the normal linux access control model, a NAND lock, implemented in hardware, on these phones. This means that without a particular exploit or an ENG bootloader, there is no way to reflash a partition. Luckily, an ENG bootloader was "obtained" "in some way" from HTC. I am not sure of the legal standing of said code, but "it's worked so far."
Now, the ENG bootloader is a signed update. This means that you have to flash the whole thing: you lose all your data, and you lose your 1.40PRI. Also, since the phone is not well and truly S-OFF, if you accept an OTA, you lose your unlocked NAND.
On the other hand, unrevoked forever ALSO unlocks NAND, and it does so at a level below the radio. This means that the update is permanent. If you accept an OTA, S-OFF remains. If you RUU, S-OFF remains. You can flash our s-on.zip update to revert it. Furthermore, every line of code in Unrevoked Forever was developed by us. HTC has no legal standing to tell us to remove it.
Click to expand...
Click to collapse
so even if i am already rooted, and did so by simple root, is my nand unlocked? i would think it is right? and even if it is can i still use unrevoked forever?
rpearl said:
Once again: The term full root is completely meaningless. You either have root, in which case you can run code as the root user, or you do not. There is no "full root" and there is no "partial root."
There is, in addition to the normal linux access control model, a NAND lock, implemented in hardware, on these phones. This means that without a particular exploit or an ENG bootloader, there is no way to reflash a partition. Luckily, an ENG bootloader was "obtained" "in some way" from HTC. I am not sure of the legal standing of said code, but "it's worked so far."
Now, the ENG bootloader is a signed update. This means that you have to flash the whole thing: you lose all your data, and you lose your 1.40PRI. Also, since the phone is not well and truly S-OFF, if you accept an OTA, you lose your unlocked NAND.
On the other hand, unrevoked forever ALSO unlocks NAND, and it does so at a level below the radio. This means that the update is permanent. If you accept an OTA, S-OFF remains. If you RUU, S-OFF remains. You can flash our s-on.zip update to revert it. Furthermore, every line of code in Unrevoked Forever was developed by us. HTC has no legal standing to tell us to remove it.
Click to expand...
Click to collapse
Currently. A future update is easily capable of overriding forever.
Sent from my PC36100 using XDA App
Rocklee99 said:
so even if i am already rooted, and did so by simple root, is my nand unlocked? i would think it is right? and even if it is can i still use unrevoked forever?
Click to expand...
Click to collapse
Yes all around.
Sent from my PC36100 using XDA App
Rocklee99 said:
so even if i am already rooted, and did so by simple root, is my nand unlocked? i would think it is right? and even if it is can i still use unrevoked forever?
Click to expand...
Click to collapse
You wouldn't be nand unlocked if u used simple root. After you use that do toasts part two for nand unlock.
Sent from my Evo 4G using Tapatalk
I rooted my phone according the following link http://forum.ppcgeeks.com/showthread.php?t=123714 . I did this after getting the ota. I followed the instructions in the ROOTING AFTER OTA 1.47.651.1 (Full Root). Am running Baked Snack, kernel #5 and riptide's theme. It shows up as android 2.2 but on boot it show in the boot up screens as 2.1. If I did forever can I take the ota and retain root and nand? Is there any benefit to it other then getting PRI 1.4.003? I don't have any problems now, can't check 4G because it's not here in Crystal River,Florida. Thanks for your help in advance
islandreamer said:
I rooted my phone according the following link http://forum.ppcgeeks.com/showthread.php?t=123714 . I did this after getting the ota. I followed the instructions in the ROOTING AFTER OTA 1.47.651.1 (Full Root). Am running Baked Snack, kernel #5 and riptide's theme. It shows up as android 2.2 but on boot it show in the boot up screens as 2.1. If I did forever can I take the ota and retain root and nand? Is there any benefit to it other then getting PRI 1.4.003? I don't have any problems now, can't check 4G because it's not here in Crystal River,Florida. Thanks for your help in advance
Click to expand...
Click to collapse
The reason you are seeing 2.1 on the boot screens is because those boot screens are static png files, not the system actually booting. If you are good with graphics manipulation you can make it say 3.0 (Gingerbread).
kf2mq said:
The reason you are seeing 2.1 on the boot screens is because those boot screens are static png files, not the system actually booting. If you are good with graphics manipulation you can make it say 3.0 (Gingerbread).
Click to expand...
Click to collapse
Thanks for the response! I should have been more specific, the 2.1 I see is really not the boot screen that are rom gods put on their roms but the system checks the phone goes through during boot up. It shows root access and success, initialization , type of processor, memory check and activating android 2.1 setup. Don't know if this means I have 2.1 or not. Under software it shows as android 2.2 just assume that is from hero's rom (Baked Snack).
islandreamer said:
Thanks for the response! I should have been more specific, the 2.1 I see is really not the boot screen that are rom gods put on their roms but the system checks the phone goes through during boot up. It shows root access and success, initialization , type of processor, memory check and activating android 2.1 setup. Don't know if this means I have 2.1 or not. Under software it shows as android 2.2 just assume that is from hero's rom (Baked Snack).
Click to expand...
Click to collapse
kf2mq is right. Android doesn't show any system checks when booting up. Everything you see after the white screen that says htc EVO 4G is all a series of image files carefully placed together as a gif to give you something pleasant to look at. In your case it just so happens that your boot animation mimics a system start-up like you would see on a computer. Mine even has an Energy Star certification in the top, right corner.
If you'd like to change the animation to say 2.2 check this thread out.
http://forum.xda-developers.com/showthread.php?t=754679
SharkUW said:
Currently. A future update is easily capable of overriding forever.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well, not so easily. But it's certainly possible. I would still wait before applying any new OTAs just in case they've figured out the magic way to undo UF without killing all legit dev phones.
Sent from my HummerPhone using the XDA App
onewaycourt said:
kf2mq is right. Android doesn't show any system checks when booting up. Everything you see after the white screen that says htc EVO 4G is all a series of image files carefully placed together as a gif to give you something pleasant to look at. In your case it just so happens that your boot animation mimics a system start-up like you would see on a computer. Mine even has an Energy Star certification in the top, right corner.
If you'd like to change the animation to say 2.2 check this thread out.
http://forum.xda-developers.com/showthread.php?t=754679
Click to expand...
Click to collapse
I will check that out. We must have the same one because the energy star is also on mine. Thank you for the enlightenment everyday I find more I need to learn. Some day I will be able to answer a question instead of ask.
SharkUW said:
Currently. A future update is easily capable of overriding forever.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well... such an update would be very interesting. Since the same exploit is used on the radio code to allow us to set S-ON as to set S-OFF, they would be revealing how to do it.
And quite likely, we'd be able to exploit or use that too.
Furthermore, there's no magic that wouldn't kill all existent testing phones too. There's no way to tell between an unrevoked forever phone and a test phone.
Don't worry... we'll still go through and confirm updates. But the process should be much easier ("hey, you can accept the OTA straight up when you get it") rather than "here is a rooted rom, you lose all your data, but it's basically the same as the update."
rpearl said:
Well... such an update would be very interesting. Since the same exploit is used on the radio code to allow us to set S-ON as to set S-OFF, they would be revealing how to do it.
And quite likely, we'd be able to exploit or use that too.
Click to expand...
Click to collapse
Awesome.
rpearl said:
Furthermore, there's no magic that wouldn't kill all existent testing phones too. There's no way to tell between an unrevoked forever phone and a test phone.
Click to expand...
Click to collapse
Could they keep a list of the MEIDs of all dev phones and selectively push updates based on that?
It's simple if you carefully follow the instructions...
http://forum.xda-developers.com/showthread.php?t=765496
In General terms, this method sets you back to 2.1 and uses Unrevoked Forever to root Stock 2.2 in the end.
i have installed the gingerbread keyboard file on my sd card and have rooted my phone using the visonary method but now i cant seem to get into recovery mode. I have rom manager installed and have flashed clockwork recovery mode. it said that it had sucsessfully installed.
I then flashed it again as i read somewhere that i might need to do it twice as sometimes it dosent work.
when i now click on the recovery option in rom manager all i get is the red triange with the ! in the middle.
any ideas what im doing wrong?
Have tried reading the threads but with 30 plus pages i am now completley confused
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
steviewevie said:
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
Click to expand...
Click to collapse
thanks for the quick reply, i think from what i have read that this s-off thing maybe the problem.
can you tell me how do this please
simple steps please as i am struggling with this
just done the hboot hing and at the top of screen it says
vision pvt ship s-on
hpsauce37 said:
thanks for the quick reply, i think from what i have read that this s-off thing maybe the problem.
can you tell me how do this please
simple steps please as i am struggling with this
Click to expand...
Click to collapse
It's a bit confusing because there is more than one way to do this. But by far the safest way is to follow the guide at http://forum.xda-developers.com/showthread.php?t=857390
Have a good read, then if you're not sure, ask questions in that thread on the process.
steviewevie said:
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
Click to expand...
Click to collapse
S-OFF is a completely different animal. Don't get it confused with being able to boot into recovery.
Sent from my EVO using Tapatalk Pro
rwcj63 said:
S-OFF is a completely different animal. Don't get it confused with being able to boot into recovery.
Click to expand...
Click to collapse
I didn't think you could flash recovery without S-OFF though ? Surely ROM Manager doesn't have the ability to write to the NAND, since the write protection will be on if you're at S-ON ?
steviewevie said:
I didn't think you could flash recovery without S-OFF though ? Surely ROM Manager doesn't have the ability to write to the NAND, since the write protection will be on if you're at S-ON ?
Click to expand...
Click to collapse
Again. S-OFF is a different issue altogether. Being able to write to NAND is a part of the rooting process. Setting security off is not a part of the rooting process. It's a totally different process for a totally different purpose. The caveat would be if unrevoked has been revised to full root and set S-OFF during the same process. I haven't used it in awhile so on that point, I'm not certain.
Sent from my EVO using Tapatalk Pro
rwcj63 said:
Again. S-OFF is a different issue altogether. Being able to write to NAND is a part of the rooting process. Setting security off is not a part of the rooting process. It's a totally different process for a totally different purpose. The caveat would be if unrevoked has been revised to full root and set S-OFF during the same process. I haven't used it in awhile so on that point, I'm not certain.
Click to expand...
Click to collapse
Sorry but that's not right for the DZ/G2. I wonder if you're thinking of how it works on a different Android phone ? The security has been increased on the DZ/G2/DHD compared to, say, the original Desire.
Writing to the system and recovery partitions isn't possible until you get S-OFF. This has nothing to do with rooting, it it because of the increased security on these phones where the NAND is in a hardware write-protect mode for those partitions by default. You can appear to write to the partitions, but it's actually going to cache and is lost when you reboot, until you get S-OFF.
steviewevie said:
Sorry but that's not right for the DZ/G2. I wonder if you're thinking of how it works on a different Android phone ? The security has been increased on the DZ/G2/DHD compared to, say, the original Desire.
Writing to the system and recovery partitions isn't possible until you get S-OFF. This has nothing to do with rooting, it it because of the increased security on these phones where the NAND is in a hardware write-protect mode for those partitions by default. You can appear to write to the partitions, but it's actually going to cache and is lost when you reboot, until you get S-OFF.
Click to expand...
Click to collapse
Actually yes. S-OFF on the EVO is to make sure no matter what, you're always rooted. It came about after the new stock flash would unroot the phone. With S-OFF active, you can flash any stock rom and not lose root. All you would need to do is reflash RA or Clockwork to get back to recovery and flash roms again. Unrevoked forever is the program we used to change the security setting.
So. That is only true for the EVO?
Sent from my EVO using Tapatalk Pro
rwcj63 said:
Actually yes. S-OFF on the EVO is to make sure no matter what, you're always rooted. It came about after the new stock flash would unroot the phone. With S-OFF active, you can flash any stock rom and not lose root. All you would need to do is reflash RA or Clockwork to get back to recovery and flash roms again. Unrevoked forever is the program we used to change the security setting.
So. That is only true for the EVO?
Sent from my EVO using Tapatalk Pro
Click to expand...
Click to collapse
yeah I think so.
The new HTC Desire Z and HD had "better" security from htc, basically you can't write anything to nand (/system) until you perma rooted, even then some things such as recovery needed s-off before we could write to that partition.
im going to have to give up on this
i have tried to follow the guide to get s-off but i find it too complicated. I have my phone rooted with visionary but i think thats as far as im going to get.
tried to install the adb thing and get that working but it never recognises the phone. when i remove the drivers and plug it back in then windows automatically installs the drivers again so i never have the option to manually instll them.
this is just becoming a nightmare
someone make it simple for me please....the thread is pages and pages long and even then it seems there are problems
hpsauce37 said:
im going to have to give up on this
i have tried to follow the guide to get s-off but i find it too complicated. I have my phone rooted with visionary but i think thats as far as im going to get.
tried to install the adb thing and get that working but it never recognises the phone. when i remove the drivers and plug it back in then windows automatically installs the drivers again so i never have the option to manually instll them.
this is just becoming a nightmare
someone make it simple for me please....the thread is pages and pages long and even then it seems there are problems
Click to expand...
Click to collapse
Have you tried my guide on adb ? http://forum.xda-developers.com/showthread.php?t=865685
OK, I can use some help too
I have a DZ with stock ROM, root and s-off and CWR.
In my enthusiasm that I knew how to flash rom updates with clockwork (I am running the Godspeed 1Ghz) I downloaded the Gingerbread keyboard rom update from the G2 forum. I think I jumped off a bit too fast...
And now I am stuck in an infinite boot loop. I can get into Clockwork recovery but it just loops the "HTC Quietly Brilliant" forever including the annoying boot sound...
I tried some suggestions to download and reflash a second time, no effect.
I tried to mount /system before flashing, no effect.
Am I forced to go back to factory now?
Also, I found 2 gingerbread keyboards, one in the G2 forum and one over here.
Anyone know what the difference is? They have a different filesize..
Any help is welcome...
*edit*
OK so now I read that it is only to be flashed on a non-stock ROM... so I am now flashing Cyanogen 6.1
try wiping all the caches...
Lennyuk said:
yeah I think so.
The new HTC Desire Z and HD had "better" security from htc, basically you can't write anything to nand (/system) until you perma rooted, even then some things such as recovery needed s-off before we could write to that partition.
Click to expand...
Click to collapse
Wow. I'm really sorry guys. I never knew that's how non evo worked. That totally sucks.
Sent from my EVO using Tapatalk Pro
rwcj63 said:
Wow. I'm really sorry guys. I never knew that's how non evo worked. That totally sucks.
Click to expand...
Click to collapse
S'alright.
HTC really ramped up the security on these new phones, as Lenny said, with this hardware write-protection on certain partitions. But even given that, I was amazed by just how quickly the guys on the #G2ROOT IRC channel, especially Scotty2, managed to crack it !
It also looks like they've opened the phone even wider than many others before, with the "true" radio S-OFF that they achieved.
You can read up all about it in the Wiki - http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision
Anyone else get stuck with the warning triangle / sign with green android bot logo figure on reboot after OTA 2.3.5?
HTC seems to block the official OTA update to android 2.3.5 on rooted phones:
http://forum.xda-developers.com/showpost.php?p=20091257&postcount=25
Should we reverse engineer the updater to remove the blocking check or do we have a full stock rom for EU with this update to flash using
alquez said:
Clockworkmod Recovery v5.0.2.6 for HTC Wildfire S (Marvel)
Click to expand...
Click to collapse
already?
woprr said:
Anyone else get stuck with the warning triangle / sign with green android bot logo figure on reboot after OTA 2.3.5?
HTC seems to block the official OTA update to android 2.3.5 on rooted phones:
http://forum.xda-developers.com/showpost.php?p=20091257&postcount=25
Should we reverse engineer the updater to remove the blocking check or do we have a full stock rom for EU with this update to flash using
already?
Click to expand...
Click to collapse
Who needs OTA? We have the stock RUU here already.
But did anyone seriously expect a different behavior?
HTC won't unlock the WFS bootloader as we already know... so how can anybody expect they would allow OTA updates on rooted phones?
Since I own HTC Android phones I never saw an OTA update working on a rooted or debranded phone (HTC Tattoo, HTC Desire, HTC Wildfire, HTC Wildfire S).
Before rooting or debranding (unbranding) everything is fine. When we "cross the line" we are on our own.
Any updates must be installed by us. Anyway that shouldn't be difficult to do...
IMHO that should be simple to understand.
I guess installing a modified recovery and then expecting for a free software update would be like showing the middle finger to HTC and still asking for candy.
Android is "open source" software but only until some extent. HTC puts a lot of modifications on their releases (mainly Sense and some addons).
If we want to "kit" or "mod" or phones we should be conscious of what we're doing.
The price to pay for being impatient or for wanting to have complete control of our devices is now pretty obvious.
I'm not saying I agree with this... on the contrary! HTC should unlock the booloader and let us do what we want.
However if we decide to take that path it's our problem.
If I put myself on HTC's boots I understand that rooting/debranding/modifying recovery is a valid reason for voiding warranty and locking future updates. With an user modified phone there is no guarantee that HTC can predict what will happen during the update process.
If something goes wrong there are possibly too many variables involved that are out of their control.
Just my two cents... sorry for my long posts mates.
d33ps1x said:
Who needs OTA? We have the stock RUU here already.
Click to expand...
Click to collapse
And unrooted and probably s-on bootloader after flash?
Forget it. Trash this HTC ****, I backup and participate in sense- less custom roms
woprr said:
And unrooted and probably s-on bootloader after flash?
Forget it. Trash this HTC ****, I backup and participate in sense- less custom roms
Click to expand...
Click to collapse
I don't understand why people buy HTC phones which are mainly "famous" because of Sense and then want to get rid of it.
It's like buying a Ferrari and removing the logo with the horse.
If I wanted a plain Vanilla Android phone there would be plenty of cheaper solutions available. Many of them with custom roms being developed.
So why buy HTC and remove it's main feature?
This is obviously just my opinion. No flaming intended.
Well, it was my first smartphone ever, and what I got for 200€ is a nasty brick of bugs with hours extra work of fixing.
This piece of crap is not even capable of setting the clock correctly without rooting.
Then comes a update and they block my phone.
I'm really fed up of HTC "Quality", and want most of their "commercialware" removed now.
I will never buy any HTC again. I've had it.
d33ps1x said:
Who needs OTA? We have the stock RUU here already.
Click to expand...
Click to collapse
I'm from mobile and I can't find the link for the official RUU. Can you please pm or post the link here? Thx
Sent from my HTC Sensation Z710e using xda premium
That's normal, once you get rooted, you're on your own.
Here.
TerrAme0 said:
I'm from mobile and I can't find the link for the official RUU. Can you please pm or post the link here? Thx
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
The RUU
Kind of off-topic, but on topic for the RUU update. Is it possible to installed Data2SD on this and be greater then 2 GB?
No, it's an official update.
miguelca said:
But did anyone seriously expect a different behavior?
HTC won't unlock the WFS bootloader as we already know... so how can anybody expect they would allow OTA updates on rooted phones?
Since I own HTC Android phones I never saw an OTA update working on a rooted or debranded phone (HTC Tattoo, HTC Desire, HTC Wildfire, HTC Wildfire S).
Before rooting or debranding (unbranding) everything is fine. When we "cross the line" we are on our own.
Any updates must be installed by us. Anyway that shouldn't be difficult to do...
IMHO that should be simple to understand.
I guess installing a modified recovery and then expecting for a free software update would be like showing the middle finger to HTC and still asking for candy.
Android is "open source" software but only until some extent. HTC puts a lot of modifications on their releases (mainly Sense and some addons).
If we want to "kit" or "mod" or phones we should be conscious of what we're doing.
The price to pay for being impatient or for wanting to have complete control of our devices is now pretty obvious.
I'm not saying I agree with this... on the contrary! HTC should unlock the booloader and let us do what we want.
However if we decide to take that path it's our problem.
If I put myself on HTC's boots I understand that rooting/debranding/modifying recovery is a valid reason for voiding warranty and locking future updates. With an user modified phone there is no guarantee that HTC can predict what will happen during the update process.
If something goes wrong there are possibly too many variables involved that are out of their control.
Just my two cents... sorry for my long posts mates.
Click to expand...
Click to collapse
I don't rally want or expect the OTA update, but have it disabled in wifes phone, but it still comes up in menu bar n says update available.
Anyway to stop it displaying this?
Ron173 said:
I don't rally want or expect the OTA update, but have it disabled in wifes phone, but it still comes up in menu bar n says update available.
Anyway to stop it displaying this?
Click to expand...
Click to collapse
Freeze the update notifier with titanium backup
Or just disable automatic update check..
Hello all,
I have some questions about rooting my phone, the HTC One M8. If someone gets a new phone like this one, backs it up after initial setup, roots and does s-off, and then does a second backup (optional).......... is there any reason why that person should need to worry about anything going wrong? I'm replacing my phone and want to know that as long as I back it up before rooting and s-off, I should never have to worry, right?
Also, once you root a phone, you can still get new OTAs right? The rooting doesn't stop that, right? Just a simple yes or no is fine.
Kindly please answer both. I appreciate all those who can shed some light! It seems that rooting is ok as long as you do it (and S-OFF) BEFORE receiving any OTAs, or that's what I think.
Thank You,
RockStar2005
RockStar2005 said:
Hello all,
I have some questions about rooting my phone, the HTC One M8. If someone gets a new phone like this one, backs it up after initial setup, roots and does s-off, and then does a second backup (optional).......... is there any reason why that person should need to worry about anything going wrong? I'm replacing my phone and want to know that as long as I back it up before rooting and s-off, I should never have to worry, right?
Also, once you root a phone, you can still get new OTAs right? The rooting doesn't stop that, right? Just a simple yes or no is fine.
Kindly please answer both. I appreciate all those who can shed some light! It seems that rooting is ok as long as you do it (and S-OFF) BEFORE receiving any OTAs, or that's what I think.
Thank You,
RockStar2005
Click to expand...
Click to collapse
part of rooting is a custom recovery which can block ota's from installing. sometimes the updates can manually be flashed or you can just revert to a stock recovery temporarily but changes to your system can also block the install. as far as the backups it's what ever your comfortable with - I never bother with backups of the stock software and I've never needed one.
Sent from my HTC One_M8 using Tapatalk
lampel said:
part of rooting is a custom recovery which can block ota's from installing. sometimes the updates can manually be flashed or you can just revert to a stock recovery temporarily but changes to your system can also block the install. as far as the backups it's what ever your comfortable with - I never bother with backups of the stock software and I've never needed one.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Ok thank Lampel!
RockStar2005
I have questions pertaining to Rooting the HTC One M8 aswell.
I moved from Samsung's Galaxy line of phones and have always Rooted without hesitation. Reasons being, I have become comfortable with the way they work and am confident I can return it to Stock (no modded counters on it or whatever), if I need to bring it back to my carrier for some reason.
Now I just got my M8, and definitely want to Root it, but all the new terms for HTC phones confuse me a little. Things I need to know before going forward with Rooting are:
1) What is "S-Off"/'S-On"? And what does it mean?
2) If I Root, can I bring it back to Stock where it will look like I did nothing to it so I can return to the store if I need to?
3) I know there are risks when Rooting, but are there things that become "broken" or don't work because of Rooting? Examples would be like Sony's Xperia devices, the Bravia Engine stops working, and so does the Camera (for some models). Those things become "broken" as a security feature for Sony. Did HTC do anything similar?
4) Anything else you might think I need to know before Rooting?
Thanks in advance!
leo9891 said:
1) What is "S-Off"/'S-On"? And what does it mean?
Click to expand...
Click to collapse
I'm not 100% certain on the other questions but maybe I can help with your first question.
Security-ON / Security-OFF. These settings seem specific to HTC. When you purchase a new phone, it will be S-On. This basically means that there are specific areas of your phone that you won't be able to touch, even with root access. However, you can alter the system, boot, and recovery partitions with root access and S-On. S-Off will allow access to the radio and other partitions that you won't be able to access with S-On. S-Off also allows you to change the splash screen. You can check your S-on/S-off status by booting into fastboot (power off phone, press volume down and power until you see the white fastboot screen).
It is my understanding that in order to get S-Off on newer HTC One M8's, Sunshine (http://theroot.ninja/) can be used but it does cost $25. The htcdev.com site has more information on S-On/S-Off along with warnings of why you may not want to go with S-Off here: http://www.htcdev.com/bootloader/about_unlock_process.
janderia said:
I'm not 100% certain on the other questions but maybe I can help with your first question.
Security-ON / Security-OFF. These settings seem specific to HTC. When you purchase a new phone, it will be S-On. This basically means that there are specific areas of your phone that you won't be able to touch, even with root access. However, you can alter the system, boot, and recovery partitions with root access and S-On. S-Off will allow access to the radio and other partitions that you won't be able to access with S-On. S-Off also allows you to change the splash screen. You can check your S-on/S-off status by booting into fastboot (power off phone, press volume down and power until you see the white fastboot screen).
It is my understanding that in order to get S-Off on newer HTC One M8's, Sunshine (http://theroot.ninja/) can be used but it does cost $25. The htcdev.com site has more information on S-On/S-Off along with warnings of why you may not want to go with S-Off here: http://www.htcdev.com/bootloader/about_unlock_process.
Click to expand...
Click to collapse
thanks for your reply, took a day or two after i posted to grab the concept of S-Off/S-On. I'm used to Samsung devices where all you needed was root, and you can do anything.
So I just got the M9 and I'm coming from a Rezound(!). I'm exploring the forums trying to learn about the flashing methods for this phone and what I need to be concerned about and not finding that much in the Vzw M9 area, not complaining, just saying.
So, wondering if reading the other M9 threads and perhaps the M8 threads will help? Is it the same overall method?
I found the thread for TWRP and how to get that on the phone and see that the file name for flashing should be 0PJAIMG.zip... but there's a "download" mode that wasn't on the Rezzy so I'd like to learn more about it all in time for what will possibly be an active Marshmallow season.
Thanks.
First off you need to get S-Off and the only way to do that with the Verizon version is JavaCard/Clip. You will need to send your device to someone who has one, go meet some one who has one, or buy one yourself. Check this thread for who can get your phone S-Off'ed http://forum.xda-developers.com/verizon-one-m9/general/m9-java-card-t3063247
I mailed mine to @dottat and the process was very simple. After that follow the guide you found for installing TWRP and flashing roms will be that same as before.
nrage23 said:
First off you need to get S-Off and the only way to do that with the Verizon version is JavaCard/Clip. You will need to send your device to someone who has one, go meet some one who has one, or buy one yourself. Check this thread for who can get your phone S-Off'ed http://forum.xda-developers.com/verizon-one-m9/general/m9-java-card-t3063247
I mailed mine to @dottat and the process was very simple. After that follow the guide you found for installing TWRP and flashing roms will be that same as before.
Click to expand...
Click to collapse
Thanks for the reply. (I'm 'thanking' so much these days I don't have any more xda thanks to give out)
Yeah, I'm probably going to send it to dottat as well. Have been in touch with him about this already.
I just want to study up on how things work on this phone. When I got the Rezzy it was at the very beginning and that was my first smartphone so luckily I was able to learn along with the progress of the devs figuring out that phone.
Now I'm jumping in midstream and I've forgotten a lot of what I learned before cuz I've been running the same ROM for a couple years. I'm reading the "normal" M9 forums now so see how things work in general on this beast at least.
If you like Sense and Customization the ViperOne 3.5.0 is a hard ROM to beat. Verizon M9's cannot use the recently released ViperOne 4.1.1 since we do not have a MarshMallow Firmware yet.
Yeah, I like Sense. I've never tried not using it though.
Looked for ViperOne and found it under the general M9 ROMs. So that answers something I was wondering about, the ROMs in the general M9 section might be able to be used on the Vzw M9s as well. That's great!
I'm going to get my nano sim today and will take the latest update for this Vzw phone, will I still be able to run that ViperOne version you mentioned?
I attached what my phone is right now, before checking for OTAs. I bought it from Swappa so it may have the latest as it is not rooted or unlocked. (that's what the listing said and it came to me factory wiped, I don't know if I can/should check if it was in the past.)
Thanks!
Feralicious, the M9 is vastly different than the Rezound. M9's don't have hboot, like the Rezound did. M9's can't be S-Offed with the "wire trick." (There's no back to open, for starters). @dottat is the man, liberated my M9. Fastboot USB is done in "download mode" which is accessed from "aboot" (instead of hboot). It looks just like the Rezound's hboot, but it has two relevant options: (1) recovery mode and (2) download mode (as well as factory reset, reboot, and power down). But, unlike with the Rezound, if you connect your M9 to the PC in aboot, nothing happens.
Secondly, writing to \system on the Rezound won't break anything. You can roll backwards and get OTA's. If you EVER write to the \system on an M9, you'll never get an OTA again (unless you have done a nandroid of system-image which you can restore).
It's generally a "more secure" system from HTC's point of view (and has been giving devs the fits for a bit). TWRP is the recovery of choice on the M9. My recollection is that on the Rezound clockworkmod's recovery was preferred.
There are a few more differences. One thing that hasn't changed is the tendency of the handset to overheat.
hgoldner said:
Feralicious, the M9 is vastly different than the Rezound. M9's don't have hboot, like the Rezound did. M9's can't be S-Offed with the "wire trick." (There's no back to open, for starters). @dottat is the man, liberated my M9. Fastboot USB is done in "download mode" which is accessed from "aboot" (instead of hboot). It looks just like the Rezound's hboot, but it has two relevant options: (1) recovery mode and (2) download mode (as well as factory reset, reboot, and power down). But, unlike with the Rezound, if you connect your M9 to the PC in aboot, nothing happens.
Secondly, writing to \system on the Rezound won't break anything. You can roll backwards and get OTA's. If you EVER write to the \system on an M9, you'll never get an OTA again (unless you have done a nandroid of system-image which you can restore).
It's generally a "more secure" system from HTC's point of view (and has been giving devs the fits for a bit). TWRP is the recovery of choice on the M9. My recollection is that on the Rezound clockworkmod's recovery was preferred.
There are a few more differences. One thing that hasn't changed is the tendency of the handset to overheat.
Click to expand...
Click to collapse
Just a note-
I posted a stock nandroid in the 5.1 thread and we also have an ruu that will suffice for users as well.
Sent from my Nexus 6 using Tapatalk
hgoldner said:
Feralicious, the M9 is vastly different than the Rezound. M9's don't have hboot, like the Rezound did. M9's can't be S-Offed with the "wire trick." (There's no back to open, for starters). @dottat is the man, liberated my M9. Fastboot USB is done in "download mode" which is accessed from "aboot" (instead of hboot). It looks just like the Rezound's hboot, but it has two relevant options: (1) recovery mode and (2) download mode (as well as factory reset, reboot, and power down). But, unlike with the Rezound, if you connect your M9 to the PC in aboot, nothing happens.
Secondly, writing to \system on the Rezound won't break anything. You can roll backwards and get OTA's. If you EVER write to the \system on an M9, you'll never get an OTA again (unless you have done a nandroid of system-image which you can restore).
It's generally a "more secure" system from HTC's point of view (and has been giving devs the fits for a bit). TWRP is the recovery of choice on the M9. My recollection is that on the Rezound clockworkmod's recovery was preferred.
There are a few more differences. One thing that hasn't changed is the tendency of the handset to overheat.
Click to expand...
Click to collapse
That's some great info, thanks!
I'm taking notes from everything I'm reading in the general M9 forums, will look for info on doing the nand of system-image.
dottat said:
Just a note-
I posted a stock nandroid in the 5.1 thread and we also have an ruu that will suffice for users as well.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
So you're saying the stock nand and that RUU suffice to rollback?
feralicious said:
That's some great info, thanks!
I'm taking notes from everything I'm reading in the general M9 forums, will look for info on doing the nand of system-image.
So you're saying the stock nand and that RUU suffice to rollback?
Click to expand...
Click to collapse
Yes, @dottat is the guy you need for S-OFF, and, his posts can get you back to stock to take OTA updates (once your S-OFF that really wont matter though).
Perfect answer @hgoldner sums it up exactly ("wire trick" LOL. Scared the crap out of me, but worked like a charm. Miss my Rezound).
sdamark said:
Yes, @dottat is the guy you need for S-OFF, and, his posts can get you back to stock to take OTA updates (once your S-OFF that really wont matter though).
Perfect answer @hgoldner sums it up exactly ("wire trick" LOL. Scared the crap out of me, but worked like a charm. Miss my Rezound).
Click to expand...
Click to collapse
Haha... I was too worried about doing the wire trick and didn't feel I had to do it so I never did. 2 years later went s-off using the software route that had come out.
Now I feel like I'm new to smartphones again since there's so much new stuff to learn about! Just got my sim card in tonight and I'm loving this so far! Glad everything works on the phone too, I think I got a good deal!