Develop Bugs

[REQUEST] Idiot's Guide

In the N1 General forum there was a great post done - 100% Fool Proof Guide to rooting & ROMs, and I was hoping that we could start a similar thread here.
Please feel free to comment on this post - it is my hope that we can put together a great document for newbs like me in the future. THIS thread is for suggestions on what should be in the guide, not the guide itself. I will reserve the second post for compiling suggestions over the next couple of days.
I just ordered my Desire, and it should be with me in a week or two. I am disturbed by the USB/A2SD issues being encountered by some, and so when I root I want to get it right
imHo, the guide should include:
1) Definitions of Rooting, unlocking, goldcards, generic, kernel, radio and how these relate to future OTA updates. These are concepts which I am familiar with, but feel I know just enough to be dangerous to myself/my device
2) A ballpark comparison of the unique characteristics of ROMs available today (stock-like, minimalist, sense-free, tethering, etc)
3) A step-by-step guide to the most recommended flashing updates people are using today
4) Things to bear in mind if you are a win-x64 user (I understand this is a tripping point for some)

[Reserved for collating ideas]
1) Terminology:
Rooting
Unlocking
Goldcards
Generic
Kernel
Radio
OTA updates, and how they may be affected by flashing your Desire
2) Current ROMs available and their unique characteristics
3) Guide to flashing your desire
4) Win64 users - what to bear in mind

And a big warning that this rooting process can cause unexpected pain on your bank balance if you are unlucky at the minute

I'd say to use the TinyCore method as I had nothing but issues doing it using W7 x64 - there's a guide on MoDaCo that's simple as anything - only a fool would get it wrong!!!
Find it here:
http://android.modaco.com/content/h...inux-download-and-guide-easiest-and-best-way/
And my USB still works fine, not had any issues since rooting and am now happily using an MCRr2 ROM cooked to my liking

I'd have to agree. Tiny Core Linux was so simple to use. I'd never used Linux before and even I could do it!
I did see paul's tweet saying a new safer more reliable method was coming this week hopefully. If that's the case I'll be rooting like mad again!
New, safer, more reliable root method for Legend and Desire coming up next week (all being well). #mcr 7:28 PM May 14th via Tweetie http://twitter.com/PaulOBrien

Only issues I've had was flashing the radio as part of a ROM - wouldn't have it so gonna try it on its own later this evening. Would be nice to get it all in one ROM but meh

EddyOS said:
I'd say to use the TinyCore method as I had nothing but issues doing it using W7 x64 - there's a guide on MoDaCo that's simple as anything - only a fool would get it wrong!!!
Find it here:
http://android.modaco.com/content/h...inux-download-and-guide-easiest-and-best-way/
And my USB still works fine, not had any issues since rooting and am now happily using an MCRr2 ROM cooked to my liking
Click to expand...
Click to collapse
u guys are getting it wrong!!!!!!
me too i was saying the same thing last week when i was reading about the bricks and stuff. i didnt have any problems till 2 days ago. well let me tell you that the unrooting process went out wonderful... nothing wrong. i even flashed all the roms possible and even started cooking and porting some roms for my own use too.
the problem is not whether the method is complex or not. the ''brick'' does not happen while you are rooting the phone. nobody actually knows what triggers the damage. some get it on 1st attempt, some after 5-6 flashes, and some like me after numerous ones.
so in my opinion, i dont think you can say this is a safe method bla bla bla and i try to discourage ppl wanting to root ''for the moment''.

deeren said:
u guys are getting it wrong!!!!!!
me too i was saying the same thing last week when i was reading about the bricks and stuff. i didnt have any problems till 2 days ago. well let me tell you that the unrooting process went out wonderful... nothing wrong. i even flashed all the roms possible and even started cooking and porting some roms for my own use too.
the problem is not whether the method is complex or not. the ''brick'' does not happen while you are rooting the phone. nobody actually knows what triggers the damage. some get it on 1st attempt, some after 5-6 flashes, and some like me after numerous ones.
so in my opinion, i dont think you can say this is a safe method bla bla bla and i try to discourage ppl wanting to root ''for the moment''.
Click to expand...
Click to collapse
I totally agree, I try to at least warn people that there is a fair chance they will brick their device but this thread is about the best and easiest way to root.
At the end of the day if people know the risks and still want to go for it, then they may as well come here for the easiest method

just a quick question guys as im a total noob in android and rooting, does this method also works with the desire and does not require a goldcard?

cez10 said:
just a quick question guys as im a total noob in android and rooting, does this method also works with the desire and does not require a goldcard?
Click to expand...
Click to collapse
This method is for the desire!
If you choose to root, then you will only need a goldcard if your handset was network supplied and branded. If for example you bought it and it came in a plain box, and had no network branding on the software then you can do it without the gold card. I got mine from the Carphone Warehouse so it was unlocked and unbranded. I just rooted with the standard SD card.
The software number on my unbranded device is 1.15.405.4. Hope this helps.

Refer to this

1) Nothing is foolproof. If you're a fool, don't root.
2) Foolproof implies pragmatic. The N1 is designed (basically) to be rooted so there's a universal method for all. The Desire wasn't, so things liks different bootloaders, branded phones and goldcards makes everyone just that little bit different. I mean, the HTC memory protection mean things like Adfree don't work out of the box (causes phone to reboot) - if you create a foolproof method we're just going to get threads about "zomg why wont dis app wrk on my fone" because they expect to be spoonfed everything.

Question About Rooting the Note 2

Hi guys,
Considering switching to the Note 2 on AT&T. I've been debating it but think I'm going to make the switch with the comfort of AT&T's return policy. My concern is this: What if I take the phone, root it, flash a custom rom and something goes wrong. Is this like iPhone jailbreaking which voids the warranty or what? I'd hate to switch and then brick the phone and have no recourse. Just wondering, thanks.

Trust me nothing will go wrong rooting or flashing - all you have to ensure is that you take your time to read and understand the instruction (not to mention that you'll have to follow em precisely). Even if you get into soft bricks its easily re storable. Hard bricks are rare these days and happen only when some people do utter senseless (no offense) things like flashing Rom of another origin . Moreover you can always open threads of this sort for any help if you get stuck somewhere
leap before you think

Yeah, just a little nervous because after rooting my Nexus 7 I almost bricked it somehow. I'm not tremendously technologically advanced, but I'm no slouch.
I have a Mac. Is this a guide you'd recommend?
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-galaxy-note-2-on-mac-osx/

JJ2525 said:
Yeah, just a little nervous because after rooting my Nexus 7 I almost bricked it somehow. I'm not tremendously technologically advanced, but I'm no slouch.
I have a Mac. Is this a guide you'd recommend?
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-galaxy-note-2-on-mac-osx/
Click to expand...
Click to collapse
At this point you can entirely root and flash new roms without the use of a computer. There's an apk on here, exynos exploit, that will root you in a snap. From there, you install a new recovery (cwm or twrp), and then flash yourself silly.
-----
I would love to help you, but help yourself first: ask a better question
http://www.catb.org/~esr/faqs/smart-questions.html

(HELP) TMO HTC One- keep wiping and still end up in bootloop

I got a new HTC One m8 from Tmobile a few weeks ago and instantly went to root and find out about S on and how I can get rid of it. I followed a rooting tutorial on unlockr diligently and unlocked bootloader and installed TWRP and SuperSU. I moved on to S-off the device and got to the last step of the tutorial where it starts to "chug" bottles(Firewater). After the first bottle, it tells me I'm out of luck and that my phone is patched. This confused me. Does this mean that my phone is forever stuck S-on? or does it mean that the developers of firewater haven't developed an S-off method for the newest version of HTC's software and that I simply have to wait.
This is just my first problem, even though I can't flash custom ROMs I was fine because I was willing to give the stock ROM a chance and just tweak it with root privileges, but no, the next time I had to restart for some various reason it starts bootlooping every few minutes. I swear I didn't do anything wrong when rooting. Is it just too new and the newest HTC software makes the rooting process obsolete making it impossible to root?
So I end up wiping the phone not being able to save all the pictures I took on my trip in the mountains. My phone is still rooted but the phone is wiped. I go about thinking the solution is fixed and when I decide to nandroid backup, I go into recovery, do a simple backup and when I restart it goes straight back to the infuriating bootloop. A simple nandroid backup shouldn't make it go into a bootloop.
So I decide to relock the bootloader, install the stock recovery and software again and start over. Maybe I really did mess up rooting. I go through the process again and low and behold my phone goes into a bootloop again.
I'm so sick and tired of this phone and I'm not sure why it always seems to happen to me. I follow the tutorials closely and it always ends up ****ting on me.
It recently went into a bootloop after a good 3 day run where I managed to keep the phone on the entire time. Had to restart because the wifi antenna wasn't working and another bootloop ensued. I decided to make this thread to see if any other new users are experiencing similar difficulties and seeing if anyone knows a cause or maybe a solution. Right now in the process of unrooting and going back to stock.
It would be a shame if there really is no way for me to unlock the full potential of my new phone. Almost wishing I had bought a nexus.
Thank you for anyone who was willing to read that and to anyone who takes the time to write a response. Thanks!

westonnate said:
I got a new HTC One m8 from Tmobile a few weeks ago and instantly went to root and find out about S on and how I can get rid of it. I followed a rooting tutorial on unlockr diligently and unlocked bootloader and installed TWRP and SuperSU. I moved on to S-off the device and got to the last step of the tutorial where it starts to "chug" bottles(Firewater). After the first bottle, it tells me I'm out of luck and that my phone is patched. This confused me. Does this mean that my phone is forever stuck S-on? or does it mean that the developers of firewater haven't developed an S-off method for the newest version of HTC's software and that I simply have to wait.
This is just my first problem, even though I can't flash custom ROMs I was fine because I was willing to give the stock ROM a chance and just tweak it with root privileges, but no, the next time I had to restart for some various reason it starts bootlooping every few minutes. I swear I didn't do anything wrong when rooting. Is it just too new and the newest HTC software makes the rooting process obsolete making it impossible to root?
So I end up wiping the phone not being able to save all the pictures I took on my trip in the mountains. My phone is still rooted but the phone is wiped. I go about thinking the solution is fixed and when I decide to nandroid backup, I go into recovery, do a simple backup and when I restart it goes straight back to the infuriating bootloop. A simple nandroid backup shouldn't make it go into a bootloop.
So I decide to relock the bootloader, install the stock recovery and software again and start over. Maybe I really did mess up rooting. I go through the process again and low and behold my phone goes into a bootloop again.
I'm so sick and tired of this phone and I'm not sure why it always seems to happen to me. I follow the tutorials closely and it always ends up ****ting on me.
It recently went into a bootloop after a good 3 day run where I managed to keep the phone on the entire time. Had to restart because the wifi antenna wasn't working and another bootloop ensued. I decided to make this thread to see if any other new users are experiencing similar difficulties and seeing if anyone knows a cause or maybe a solution. Right now in the process of unrooting and going back to stock.
It would be a shame if there really is no way for me to unlock the full potential of my new phone. Almost wishing I had bought a nexus.
Thank you for anyone who was willing to read that and to anyone who takes the time to write a response. Thanks!
Click to expand...
Click to collapse
If you wanna fix it quick then just do an RUU (t-mobile one) and after you've done that use Sunshine to root, unlock and S-OFF your phone. All though Sunshine costs $25 it is a sure fire to work.
You can find a tutorial for the RUU in the t-mobile forum I believe, not sure as im replying to this before I go to bed but it should have one. If by some chance "TMO" doesn't mean T-Mobile then my bad. Anyways if you get confused take your time and do your research or wait for someone else or me to assist you further.
Also if you used Xposed then that could be the problem, I've had it randomly bootloop me after days of use, just google the Xposed deactivate script zip or Uninstaller script and flash it to remove it. If you don't have it then don't do this part.
Lastly I doubt you'll regret buying an M8 after you get it setup properly, it's a great phone but of course that's just mine and a lot of people's opinion. Anyways good luck and hope one of my solutions fix it! If not then don't be afraid to ask more questions or request further assistance whether from me or someone else.

S1L3nTShaDoWz said:
If by some chance "TMO" doesn't mean T-Mobile then my bad.
Click to expand...
Click to collapse
It does, although T-Mobile is a huge carrier in Europe, and AFAIK only the US T-Mob variant has an RUU (and not immediately clear what version the OP has).

You can flash custom roms without s-off, and have you tried wiping cache and fixing permissions? Idk if that'd solve it or not but worth a try.

Rooting without exploding the device? Have not had an HTC in a long time.

Just ordered my HTC 10, excited...and nervous as I've not had a new device (like long term) in... like over 1.5 years. :S I'm mainly hoping the microSD card slot likes my 128GB U1 x633 card so I can finally have enough space for all my vinyl rips, and then I hope the DAC is as good as they say.
So anyway, I've been reading all of this stuff about rooting and loosing the radio connection and something about the data encryption breaking everything O.O!!! Holy crap. I just wanna root it, find a good rom and dev to support and enjoy it. This is what I do on my current daily driver, my old OPO. I've been trying to look around, search, and read to make sure that I avoid all of these issues mentioned but so far I've not found a concrete explanation of why said issues happen. Not new to rooting/flashing at all, but HTC devices always seemed to of been touchy when it came to custom stuff, and I don't want to explode this thing. My main problem is that I've been away from HTC for.... well since early 2014.
My current knowledge of android stuffz tells me to:
1) Unlock Bootloader via ADB
2) Flash TWRP/Other Customer Recovery
3) Find sweet rom, flash and spend hours customizing
4) Flash xposed and go crazy with modules until the phone explodes and then scale it back to a realistic level
5) Enjoy Phone
6) Cake
HOWEVER... I remember HTC devices having a bit more complication due to things like... RUU and firmware.. I don't even remember what RUU means lol... But I remember when I had my M8 I was always fighting these dang firmware issues. While I ended up with a fantastic experience, I remember fighting for almost 2 months or so to get it to behave. Battery was out of control, phone was crashing, camera exploding. Oh man it sucked, but finally someone really cool was like... "Yo dude I had these issues, this is what you have to do with HTC stuff" , and after a full hour of flashing shiz I had the phone running smoothly and behaving correctly. Something about... you had to flash each level of the firmware and then reboot and...something. Like you couldn't just skip to the latest firmware? I don't remember exactly.
So anyway, the main question I have is. Could someone either
A.) Point me in the direction of a post or something to study to understand what to do and not do. I've searched but not really found anything solid. Something for folks who've been off the HTC scene for a while.
B.) If there isn't really a single post on this, perhaps if someone doesn't mind explaining this (even pm is fine) to me so I don't explord this expensive mofo and cry.
C.) Give me a hug, because I am nervous about having a new device O.O , it's been so long and I'm so used to Cm13 and xposed and all that jazz. I is be scared.
I would be grateful to any and all help/support.
Anyway, thanks in advanced guys and gals. :3

Locklear308 said:
Just ordered my HTC 10, excited...and nervous as I've not had a new device (like long term) in... like over 1.5 years. :S I'm mainly hoping the microSD card slot likes my 128GB U1 x633 card so I can finally have enough space for all my vinyl rips, and then I hope the DAC is as good as they say.
So anyway, I've been reading all of this stuff about rooting and loosing the radio connection and something about the data encryption breaking everything O.O!!! Holy crap. I just wanna root it, find a good rom and dev to support and enjoy it. This is what I do on my current daily driver, my old OPO. I've been trying to look around, search, and read to make sure that I avoid all of these issues mentioned but so far I've not found a concrete explanation of why said issues happen. Not new to rooting/flashing at all, but HTC devices always seemed to of been touchy when it came to custom stuff, and I don't want to explode this thing. My main problem is that I've been away from HTC for.... well since early 2014.
My current knowledge of android stuffz tells me to:
1) Unlock Bootloader via ADB
2) Flash TWRP/Other Customer Recovery
3) Find sweet rom, flash and spend hours customizing
4) Flash xposed and go crazy with modules until the phone explodes and then scale it back to a realistic level
5) Enjoy Phone
6) Cake
HOWEVER... I remember HTC devices having a bit more complication due to things like... RUU and firmware.. I don't even remember what RUU means lol... But I remember when I had my M8 I was always fighting these dang firmware issues. While I ended up with a fantastic experience, I remember fighting for almost 2 months or so to get it to behave. Battery was out of control, phone was crashing, camera exploding. Oh man it sucked, but finally someone really cool was like... "Yo dude I had these issues, this is what you have to do with HTC stuff" , and after a full hour of flashing shiz I had the phone running smoothly and behaving correctly. Something about... you had to flash each level of the firmware and then reboot and...something. Like you couldn't just skip to the latest firmware? I don't remember exactly.
So anyway, the main question I have is. Could someone either
A.) Point me in the direction of a post or something to study to understand what to do and not do. I've searched but not really found anything solid. Something for folks who've been off the HTC scene for a while.
B.) If there isn't really a single post on this, perhaps if someone doesn't mind explaining this (even pm is fine) to me so I don't explord this expensive mofo and cry.
C.) Give me a hug, because I am nervous about having a new device O.O , it's been so long and I'm so used to Cm13 and xposed and all that jazz. I is be scared.
I would be grateful to any and all help/support.
Anyway, thanks in advanced guys and gals. :3
Click to expand...
Click to collapse
I was in the same boat haven't owed an HTC since the Fuze running Windows lol and have been a loyal Samsung user since the S1 so the whole adb fastboot thing was a little overwhelming. I followed the guide in the forum and had a few hiccups but overall went pretty smooth. Adb is definitely not as user friendly as Odin on a Sammy device but not to difficult. My only tips would be make sure you have all the latest drivers, twrp, and adb installed. It seems pretty hard to permanently brick a device these days from my experience so I wouldn't worry to much. As far as the radio not working, as long as you keep your device encrypted you won't lose your radio. I'm sure the devs will find a fix for this soon enough. Enjoy your new 10!
Edit: I'm using a lexar 128gb 633x U1 micro sd and all is well. Worked with adoptable storage also but felt a little sluggish so I went back to using it as external storage.

AndroiderM said:
I was in the same boat haven't owed an HTC since the Fuze running Windows lol and have been a loyal Samsung user since the S1 so the whole adb fastboot thing was a little overwhelming. I followed the guide in the forum and had a few hiccups but overall went pretty smooth. Adb is definitely not as user friendly as Odin on a Sammy device but not to difficult. My only tips would be make sure you have all the latest drivers, twrp, and adb installed. It seems pretty hard to permanently brick a device these days from my experience so I wouldn't worry to much. As far as the radio not working, as long as you keep your device encrypted you won't lose your radio. I'm sure the devs will find a fix for this soon enough. Enjoy your new 10!
Click to expand...
Click to collapse
Well I am comfortable in adb :3 so that's not a worry. So un-enecrypting it is just an option, and I should just avoid it for now? What is the advantage of un-encrypting it?
What guide did you use? Also, what about all this firmware and ruu stuff?
Sorry for so many questions... Lol this thing wasn't cheap and I am nervous , BTW what setup do you have? Root? ROM?
Thanks for replying :3

Locklear308 said:
Well I am comfortable in adb :3 so that's not a worry. So un-enecrypting it is just an option, and I should just avoid it for now? What is the advantage of un-encrypting it?
What guide did you use? Also, what about all this firmware and ruu stuff?
Sorry for so many questions... Lol this thing wasn't cheap and I am nervous , BTW what setup do you have? Root? ROM?
Thanks for replying :3
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-10/how-to/guide-root-optionally-s-off-radio-t3373025
From what I understand unencrypting breaks the radio. With it unencrypted you would get slightly better performance and boot times I think. I would definitely avoid it for now. I'm currently using twrp with Viper 10 rom. I've also used leedroid and still trying to find which one I prefer. I've only had my 10 for 3 days lol so I haven't found my sweet setup just yet. I left s-on for now as I don't really need it off.
No idea about the firmware and ruu stuff. I made a backup of stock rom before I started flashing. I'm pretty sure there is or will be a repo with factory firmware, radios, etc. I don't know what ruu stands for either lol.
---------- Post added at 06:56 AM ---------- Previous post was at 06:51 AM ----------
Did you get carrier or unlocked version

AndroiderM said:
http://forum.xda-developers.com/htc-10/how-to/guide-root-optionally-s-off-radio-t3373025
From what I understand unencrypting breaks the radio. With it unencrypted you would get slightly better performance and boot times I think. I would definitely avoid it for now. I'm currently using twrp with Viper 10 rom. I've also used leedroid and still trying to find which one I prefer. I've only had my 10 for 3 days lol so I haven't found my sweet setup just yet. I left s-on for now as I don't really need it off.
No idea about the firmware and ruu stuff. I made a backup of stock rom before I started flashing. I'm pretty sure there is or will be a repo with factory firmware, radios, etc. I don't know what ruu stands for either lol.
---------- Post added at 06:56 AM ---------- Previous post was at 06:51 AM ----------
Did you get carrier or unlocked version
Click to expand...
Click to collapse
Unlocked, at least that's what the guy on Swappa marked it as. *fingers crossed*
Got it for 510. One scratch on the metal
Alright so I will back things up and avoid the radio breaking stuff. I will check that link, thanks man

Locklear308 said:
Unlocked, at least that's what the guy on Swappa marked it as. *fingers crossed*
Got it for 510. One scratch on the metal
Alright so I will back things up and avoid the radio breaking stuff. I will check that link, thanks man
Click to expand...
Click to collapse
No problem, mine has two scratches on metal too lol but guy gave me $200 and unlocked htc 10 w uh oh protection and original receipt for my s7e at&t branded locked bootloader ?. Was a no brainer for me

Locklear308 said:
Just ordered my HTC 10, excited...and nervous as I've not had a new device (like long term) in... like over 1.5 years. :S I'm mainly hoping the microSD card slot likes my 128GB U1 x633 card so I can finally have enough space for all my vinyl rips, and then I hope the DAC is as good as they say.
So anyway, I've been reading all of this stuff about rooting and loosing the radio connection and something about the data encryption breaking everything O.O!!! Holy crap. I just wanna root it, find a good rom and dev to support and enjoy it. This is what I do on my current daily driver, my old OPO. I've been trying to look around, search, and read to make sure that I avoid all of these issues mentioned but so far I've not found a concrete explanation of why said issues happen. Not new to rooting/flashing at all, but HTC devices always seemed to of been touchy when it came to custom stuff, and I don't want to explode this thing. My main problem is that I've been away from HTC for.... well since early 2014.
My current knowledge of android stuffz tells me to:
1) Unlock Bootloader via ADB
2) Flash TWRP/Other Customer Recovery
3) Find sweet rom, flash and spend hours customizing
4) Flash xposed and go crazy with modules until the phone explodes and then scale it back to a realistic level
5) Enjoy Phone
6) Cake
HOWEVER... I remember HTC devices having a bit more complication due to things like... RUU and firmware.. I don't even remember what RUU means lol... But I remember when I had my M8 I was always fighting these dang firmware issues. While I ended up with a fantastic experience, I remember fighting for almost 2 months or so to get it to behave. Battery was out of control, phone was crashing, camera exploding. Oh man it sucked, but finally someone really cool was like... "Yo dude I had these issues, this is what you have to do with HTC stuff" , and after a full hour of flashing shiz I had the phone running smoothly and behaving correctly. Something about... you had to flash each level of the firmware and then reboot and...something. Like you couldn't just skip to the latest firmware? I don't remember exactly.
So anyway, the main question I have is. Could someone either
A.) Point me in the direction of a post or something to study to understand what to do and not do. I've searched but not really found anything solid. Something for folks who've been off the HTC scene for a while.
B.) If there isn't really a single post on this, perhaps if someone doesn't mind explaining this (even pm is fine) to me so I don't explord this expensive mofo and cry.
C.) Give me a hug, because I am nervous about having a new device O.O , it's been so long and I'm so used to Cm13 and xposed and all that jazz. I is be scared.
I would be grateful to any and all help/support.
Anyway, thanks in advanced guys and gals. :3
Click to expand...
Click to collapse
I'm on my third htc10. Exploded last two after rooting haha. Really not hard mate. Just read the guides provided and ask any questions you need. Most ppl on XDA will be helpful, and some will reply like me lol.
BTW, simple answer, unlock phone via HTC Dev, then flash Viper. Done.

purple patch said:
I'm on my third htc10. Exploded last two after rooting haha. Really not hard mate. Just read the guides provided and ask any questions you need. Most ppl on XDA will be helpful, and some will reply like me lol.
BTW, simple answer, unlock phone via HTC Dev, then flash Viper. Done.
Click to expand...
Click to collapse
Alright neato, so do I need to ensure I let it download any and all OTA's for the firmware before doing anything? Is s-off safe to get as well in regards to the issues I referred to in my OP above?
And his is this viper? Does it allow things like settings similar to cm and also allow for xposed?
Thanks for replying man, I feel more comfortable now as it sounds like there isn't anything crazy required to safely root this thing . Phew!!

Locklear308 said:
Alright neato, so do I need to ensure I let it download any and all OTA's for the firmware before doing anything? Is s-off safe to get as well in regards to the issues I referred to in my OP above?
And his is this viper? Does it allow things like settings similar to cm and also allow for xposed?
Thanks for replying man, I feel more comfortable now as it sounds like there isn't anything crazy required to safely root this thing . Phew!!
Click to expand...
Click to collapse
I got an M9 for my wife not that long ago and just had my 10 show up today and gonna root. Just do like the other dude said. Find a guide that says how to use HTC dev to unlock the bootloader. You can't just enter a command in adb like "unlock bootloader" and have it work. Go to the HTC dev website, make an account, pick your device and it walks you through the steps of unlocking the bootloader. That's really the only semi-difficult part IMO. Then proceed as normal. Download twrp, make a stock nand, download ROM, su binaries, kernel, etc. etc. go to recovery and flash. I'm sure there's a couple other steps in their but that's the basics.
As for Viper, it tends to come with so many mods built in, I'd personally be kind of reluctant to use xposed with it to to much modifying. It's a great ROM, but so is leedroid You can try each and see what you like, but if you want to more safely use xposed I'd personally go with leedroid.

DroidIt! said:
I got an M9 for my wife not that long ago and just had my 10 show up today and gonna root. Just do like the other dude said. Find a guide that says how to use HTC dev to unlock the bootloader. You can't just enter a command in adb like "unlock bootloader" and have it work. Go to the HTC dev website, make an account, pick your device and it walks you through the steps of unlocking the bootloader. That's really the only semi-difficult part IMO. Then proceed as normal. Download twrp, make a stock nand, download ROM, su binaries, kernel, etc. etc. go to recovery and flash. I'm sure there's a couple other steps in their but that's the basics.
As for Viper, it tends to come with so many mods built in, I'd personally be kind of reluctant to use xposed with it to to much modifying. It's a great ROM, but so is leedroid You can try each and see what you like, but if you want to more safely use xposed I'd personally go with leedroid.
Click to expand...
Click to collapse
Oh right, I do remember about the whole HTC dev website thing. I was mainly just concerned with the firmware issues and stuff that I had before.
Is there any kind of limitations for reasons not to upgrade to the highest available firmware? Something like, maybe the highest one can't be rooted yet or something like that. I just want to make sure that I don't shoot myself in the foot haha.
Thank you all for your help

Locklear308 said:
Oh right, I do remember about the whole HTC dev website thing. I was mainly just concerned with the firmware issues and stuff that I had before.
Is there any kind of limitations for reasons not to upgrade to the highest available firmware? Something like, maybe the highest one can't be rooted yet or something like that. I just want to make sure that I don't shoot myself in the foot haha.
Thank you all for your help
Click to expand...
Click to collapse
Hey, I'm not sure about firmware not being able to be rooted but the best way to go about it (what I did anyway) is to unlock the phone via htcdev.com, flash a custom recovery (Latest TWRP which has also worked around the encryption stuff?) and then back up everything other than the data partition. That way, no matter what you do, you always have something to revert back to. The reason for not backing up data is due to the encryption. From my understanding, restoring an encrypted data partition would break things. Once you have the phone unlocked and recovery sorted, you are free to flash viper etc. and root the phone using SuperSU. I'm sure you are aware unlocked devices are quite easy to root so whatever you flash will most likely be on latest firmware, already rooted.
As for installing OTAs etc., you need unmodified system and recovery which is where the backups kick in. Simply back up your data on an SD card (pictures etc. not the actual partition) and restore the system-image and recovery. This should reset the phone although I'm not sure if it'll wipe anything and allow you to do OTA updates. Alternatively, get the latest firmware for your device from htcdev (again, not sure if they have firmware on there) and use that instead.
If any of the information above is incorrect or missing steps, someone feel free to correct me.

Updating question

Ok, I start this off with the fact that this is my first phone with the whole slot A&B thing. I've done a ton of reading but it's still very confusing to me. I'm very confused on what exactly to do when it comes to updates. I'm stock rooted with TWRP installed on slot A. I'm also on the December build. I would like to update but I don't know what the easiest way to go about it is to be honest. I feel like an idiot but I guess that's because I'm really old school when it comes to this stuff. My rooting/roming goes back to the Samsung Captivate and countless other phones up until it got to be too much of a hassle to get a phone from a carrier that could be messed with. Now that I have rambled on, I thought it would be different getting a Pixel but this whole slot thing has me all confused. I basically want to stay stock rooted for now and possibly try a kernel down the line but I'm very happy with stock for now. Any advice would be greatly appreciated.
Thanks

pside15 said:
Ok, I start this off with the fact that this is my first phone with the whole slot A&B thing. I've done a ton of reading but it's still very confusing to me. I'm very confused on what exactly to do when it comes to updates. I'm stock rooted with TWRP installed on slot A. I'm also on the December build. I would like to update but I don't know what the easiest way to go about it is to be honest. I feel like an idiot but I guess that's because I'm really old school when it comes to this stuff. My rooting/roming goes back to the Samsung Captivate and countless other phones up until it got to be too much of a hassle to get a phone from a carrier that could be messed with. Now that I have rambled on, I thought it would be different getting a Pixel but this whole slot thing has me all confused. I basically want to stay stock rooted for now and possibly try a kernel down the line but I'm very happy with stock for now. Any advice would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
@Homeboy76 will get you squared away :good:
https://forum.xda-developers.com/pi...-android-9-0-pie-unlock-t3857195/post77944292

Badger50 said:
@Homeboy76 will get you squared away :good:
https://forum.xda-developers.com/pi...-android-9-0-pie-unlock-t3857195/post77944292
Click to expand...
Click to collapse
Thanks for the reply. I've read throughout that thread numerous times and I still can't determine the easiest way to update my phone and the necessary steps to take to get there. I just want to be stock rooted like I am now but don't know what steps to take to get there. Like do I need to unroot first, relock bootloader? I'm sure all those answers are in that thread but I'm probably just too dense to see them. I haven't really had a solid rooted phone in like 3 years so I'm used to things being done way different. Some times I miss my old HTC Inspire/Desire HD. There was so much development for that phone and it was all very straightforward.

pside15 said:
Thanks for the reply. I've read throughout that thread numerous times and I still can't determine the easiest way to update my phone and the necessary steps to take to get there. I just want to be stock rooted like I am now but don't know what steps to take to get there. Like do I need to unroot first, relock bootloader? I'm sure all those answers are in that thread but I'm probably just too dense to see them. I haven't really had a solid rooted phone in like 3 years so I'm used to things being done way different. Some times I miss my old HTC Inspire/Desire HD. There was so much development for that phone and it was all very straightforward.
Click to expand...
Click to collapse
This guide is how I update the monthly security patches. It is predicated on the notion that you have the latest platform-tools (28.0.1) and that your computer and phone are communicating well. It doesn't not require you to switch slots, and it will not wipe your data, and, you do not have to unroot before you begin. Happy flashing, and good luck
And never ever ever relock the bootloader! :crying:

Badger50 said:
This guide is how I update the monthly security patches. It is predicated on the notion that you have the latest platform-tools (28.0.1) and that your computer and phone are communicating well. It doesn't not require you to switch slots, and it will not wipe your data, and, you do not have to unroot before you begin. Happy flashing, and good luck
And never ever ever relock the bootloader! :crying:
Click to expand...
Click to collapse
Awesome, thank you very much for that. Yeah, I figured that about the bootloader. Does it matter if I have TWRP installed? That's the one main confusing thing to me. How you can have TWRP installed or not installed. I'm used to absolutely having to have TWRP or some other kind of custom recovery installed. But like I said it's been quite a while since I was really able to root/ROM a phone. I was basically forced to move to AT&T and opted for the Active line of Galaxy phones since I have little kids plus even the phones that were rootable and such seemed like more of a hassle than it was worth. The last phone I had that had some good development was probably the LG G3 on T-MOBILE. For some reason the T-MOBILE version had an unlocked bootloader or could be unlocked, don't remember exactly. But then a coworker got a Pixel 2XL and I got the itch again, not knowing how much had really changed though. Ok, I think I've rambled on enough now. Thanks again for the help.

pside15 said:
Awesome, thank you very much for that. Yeah, I figured that about the bootloader. Does it matter if I have TWRP installed? That's the one main confusing thing to me. How you can have TWRP installed or not installed. I'm used to absolutely having to have TWRP or some other kind of custom recovery installed. But like I said it's been quite a while since I was really able to root/ROM a phone. I was basically forced to move to AT&T and opted for the Active line of Galaxy phones since I have little kids plus even the phones that were rootable and such seemed like more of a hassle than it was worth. The last phone I had that had some good development was probably the LG G3 on T-MOBILE. For some reason the T-MOBILE version had an unlocked bootloader or could be unlocked, don't remember exactly. But then a coworker got a Pixel 2XL and I got the itch again, not knowing how much had really changed though. Ok, I think I've rambled on enough now. Thanks again for the help.
Click to expand...
Click to collapse
Doesn't matter if you have twrp installed or not. When you fastboot the update, it'll wipe it out anyway :good: