Related
i want to to be safe. i have a tmobile variant and i would like to flash a stock unlocked and/or international rom or developer edition rom. i am guessing this will work but i will have to use gpe or tmobile radios. i haven't seen a clear path to this and i wish it was as easy as fastbooting or just flashing the proper stock nandroid. i am confused, between all the FUU's RUU's, different firmwares etc etc. is there a guide i overlooked to do this?
btw, i've converted to gpe but i went back for various reasons. the gpe just didn't have all the proper drivers to make it the premium phone the m8 is and be stock android, because i much preferred stock but sense is not too bad. helluva lot better than touchwiz. i am just concerned and don't want to brick. i had problems going back to sense. flashing my nandroid after the RUU just failed and failed. i thought i was gonna have to change underwear and get kleenex. ended up flashing my nandroid without md5 check and have had no problems since. i am aware of the CID situation and understand that. i assume i can do this with all 1's or a EU or unlocked cid. i think i understand the MID thing but would appreciate it if somebody clarified it for me. i assume that whatever i end up flashing i need to change my MID to the appropriate MID or change it in android-info.txt or is there where i'm wrong?
anyways, hoping somebody would give some magical link to a thread i overlooked. i am backing up my latest nandroid to my laptop right now and when that is done i am going all the way stock to tmobile version. hopefully in the next hour or so i'll get my answer or direction to the appropriate thread and can just convert to dev or unlocked edition. tmobile variant just has way too much bloat and things i changed like a dozen files for carrier iq block. changing to htc edition firmware will minimize the things i need to do when it's time to ota. anyways, if you made it this far thanks. and even more thanks if you're that person that gets me going in the right direction. i am almost proficient at adb/fastboot so i don't need to be handheld on that.
nevermind. went off without a hitch. was worried because previous restores from nandroids didn't go so well. i'm flashed and tmobile splash didn't show so i am pretty sure i am eu now.
Alright everyone, I did search for a similar topic before creating this thread, but I found none. If I missed it, please link me to it. Thanks!
So I'm about to trade my T-Mobile LG G3 for a T-Mobile HTC One M8. I'd like to convert it over to a GPE. Are there any specific things that I have to know about the device (software version etc.) before I make the trade?
For example, was there a recent software update that stopped us from being able to convert it into a GPE device?
Thanks in advance guys. I really appreciate it.
ZenithHammerhead said:
Alright everyone, I did search for a similar topic before creating this thread, but I found none. If I missed it, please link me to it. Thanks!
So I'm about to trade my T-Mobile LG G3 for a T-Mobile HTC One M8. I'd like to convert it over to a GPE. Are there any specific things that I have to know about the device (software version etc.) before I make the trade?
For example, was there a recent software update that stopped us from being able to convert it into a GPE device?
Thanks in advance guys. I really appreciate it.
Click to expand...
Click to collapse
Not sure about a software update preventing it. So long as you can achieve S-Off, I believe it can be converted. I did mine some time ago, found that I missed Sense 6 a lot and my signal strength was pretty low. Radios from GPE are compatible with T-Mobile LTE but the GPE system doesn't work as well with T-mobile signal. Even tried changing radios, no luck. I'd suggest trying a GPE rom that you can flash over the standard rom to see if you like it. Its much easier to flash a sense rom back to the phone than it is to convert a GPE'd phone back to sense.
phil.culler said:
Not sure about a software update preventing it. So long as you can achieve S-Off, I believe it can be converted. I did mine some time ago, found that I missed Sense 6 a lot and my signal strength was pretty low. Radios from GPE are compatible with T-Mobile LTE but the GPE system doesn't work as well with T-mobile signal. Even tried changing radios, no luck. I'd suggest trying a GPE rom that you can flash over the standard rom to see if you like it. Its much easier to flash a sense rom back to the phone than it is to convert a GPE'd phone back to sense.
Click to expand...
Click to collapse
Got it. If memory serves, you can go to the HTC site and request the bootloader be unlocked, correct? So as far as rooting and unlocking the bootloader, it's a walk in the park, no matter the software version, right?
ZenithHammerhead said:
Got it. If memory serves, you can go to the HTC site and request the bootloader be unlocked, correct? So as far as rooting and unlocking the bootloader, it's a walk in the park, no matter the software version, right?
Click to expand...
Click to collapse
Yes you can unlock the bootloader through HTCDEV. When you go through the process make sure to choose "all other devices" instead of One (M8). I had trouble with my code until I chose all other devices. Might be fixed by now. I believe to root you have to have S-Off which is only possible through Sunshine unless something has changed. Sunshine will cost you $25. There may be a method of rooting which will allow you bypass S-Off now. Haven't looked into it for a while.
phil.culler said:
Yes you can unlock the bootloader through HTCDEV. When you go through the process make sure to choose "all other devices" instead of One (M8). I had trouble with my code until I chose all other devices. Might be fixed by now. I believe to root you have to have S-Off which is only possible through Sunshine unless something has changed. Sunshine will cost you $25. There may be a method of rooting which will allow you bypass S-Off now. Haven't looked into it for a while.
Click to expand...
Click to collapse
Fantastic. You sir are the reason why XDA has such a great reputation. :good:
ZenithHammerhead said:
Fantastic. You sir are the reason why XDA has such a great reputation. :good:
Click to expand...
Click to collapse
Just doing my part, and trying my best. Most of all, I refuse to answer a question with "OMG this has been answered eleventy-million times!!! USE GOOGLE!!!" Not saying your question was answered before, just having a vent.
In case you're interested, http://forum.xda-developers.com/showthread.php?t=2708589 is the thread I used to make my conversion and it worked exactly as they said it would. Just try a GPE rom first before you do the full conversion. I was sure I would like GPE much better than sense...and I was as wrong as I could be.
Ever since I got my m9's I have been a flashing fool! I absolutely love it. But I recently learned a trick to improve my reception so I decided I would share.
I live in a city and my reception should always be 5 bars but ever since I got my phones I was only getting 3 bars max regardless of firmware or rom. I know because I have flashed them all. I have a developers edition and an AT&T edition m9 and both phones got the same reception.
well about a month ago I just wanted to try an experiment so I took my att m9 and changed the cid and mid to match a tmoble version. I then flashed the 1.32 firmware and then ran the tmobile Ruu. As a result I then had a stock t-mobile edition m9. But for the first time I had full bars for my reception!
Naturally I then flashed twrp and put a cutom rom back on it but I had the volte and wifi calling along with full bars reception. So put I that observation in the back of my mind and carried on with my business.
Well recently the tmobile update came out and I just flashed the firmware package that sneakyghost (thanks btw for your firmware files) put up and updated the custom rom I was on. But I noticed immediately afterwards my reception returned to 2-3 bars again. I really didn't care too much but then the rom I was using started acting funny. The developer decided to mess with the cpu cores on his update and in extreme power save mode over night it would eat 10% of my battery. And that is something I can't tolerate...
So, I decided to run the 1.32 tmobile (that's my carrier) RUU on my m9 and then accept the 2.7 ota. My reception then returned to 100%. after that I reflashed twrp and super su and restored all my data.
I told my wife about the reception and she wanted me to do the same on her phone (the dev edition) and so I did and got the same results....
So moral of this long post is that if you have poor reception than flashing an ruu for your carrier just might be the trick. This in return will save battery life.
If you decide to try it let me know if it worked. Thanks
This is the link with instructions on how to change your phone from one carrier to another. clsA gives instructions to convert ATT model to developer edition. But you can change your cid to whatever you carrier is and flash accordingly.
Tmobile cid= T-MOB010
At&T and develop edition cid can be found in the link. Also make sure your mid match the firmware you flash. Tmobile mid is 0PJA12000
bigp951 said:
Ever since I got my m9's I have been a flashing fool! I absolutely love it. But I recently learned a trick to improve my reception so I decided I would share.
I live in a city and my reception should always be 5 bars but ever since I got my phones I was only getting 3 bars max regardless of firmware or rom. I know because I have flashed them all. I have a developers edition and an AT&T edition m9 and both phones got the same reception.
So moral of this long post is that if you have poor reception than flashing an ruu for your carrier just might be the trick. This in return will save battery life.
Click to expand...
Click to collapse
I noticed my reception also being worse than my Galaxy S5. In fact, when I woke up I found that my phone was roaming! I never had that issue with the S5. I found it strange. Wi-Fi signal also isn't as good as on the S5. I don't know if it's all the metal or the terrible Snapdragon 810.
I wish your method involved changing something in build.prop lol, that would be simpler and quicker. I'm on a custom ROM also, not by my own will but because I bought the phone like that, I have no idea how to go back to stock AT&T without root and to be able to accept OTAs. I am S-On right now.
Ramsey said:
I noticed my reception also being worse than my Galaxy S5. In fact, when I woke up I found that my phone was roaming! I never had that issue with the S5. I found it strange. Wi-Fi signal also isn't as good as on the S5. I don't know if it's all the metal or the terrible Snapdragon 810.
I wish your method involved changing something in build.prop lol, that would be simpler and quicker. I'm on a custom ROM also, not by my own will but because I bought the phone like that, I have no idea how to go back to stock AT&T without root and to be able to accept OTAs. I am S-On right now.
Click to expand...
Click to collapse
There are a ton of excellent guides in the forum to either change ROMs or return to stock. I think you have to be s-off though. When I want to return to stock I just run an RUU. but remember to back up everything you want to keep because the phone will be completely wiped
bigp951 said:
There are a ton of excellent guides in the forum to either change ROMs or return to stock. I think you have to be s-off though. When I want to return to stock I just run an RUU. but remember to back up everything you want to keep because the phone will be completely wiped
Click to expand...
Click to collapse
I can't find any good guide here for the M9. Weird huh? I've been here since 2008, read countless excellent guides for many phones, and let me tell you that in the past guides were clear and informative. Now all I see is people writing random text all over the place, no clear steps, and information isn't always updated. Probably younger people are writing them, no problem, but it's not helping me understand how to do it.
There's a guide that still says that HTC hasn't yet allowed the bootloader to be unlocked for the M9, and yet when you go there you realize that HTC allows us to unlock it now.
Anyways, my point is, I can't find a good guide, it's not that I'm being prideful, it's just that I have indeed searched and can't find a clear guide. I'm not sure if most assume we have to be S-off? In the past people used to mention "you have to be rooted, or unrooted, or unlocked bootloader, or S-on or S-off". Now it's not very clear so I'm confused, especially since those guides have so many links that I don't know what to download and each is 2GB. You're not the first to tell me that xda has many excellent guides without pointing me to one for the M9 haha.
I want a better reception among other things as it worries me that it was roaming out of nowhere and I'd love to go back to stock as I am not a fan of custom ROMs (except for on my 2010 Galaxy S1 lol).
I have to admit this is the most confusing phone when it comes to modding it or removing root to OTA.
I tried to run an RUU for AT&T latest Android 5.1 (when I was running stock 1.32) and it failed many times, even though I unrooted and locked bootloader. I miss the days of ODIN flashing in download mode =(.
I'm happy the ROM I'm using is stable but still.
Ramsey said:
I can't find any good guide here for the M9. Weird huh? I've been here since 2008, read countless excellent guides for many phones, and let me tell you that in the past guides were clear and informative. Now all I see is people writing random text all over the place, no clear steps, and information isn't always updated. Probably younger people are writing them, no problem, but it's not helping me understand how to do it.
There's a guide that still says that HTC hasn't yet allowed the bootloader to be unlocked for the M9, and yet when you go there you realize that HTC allows us to unlock it now.
Anyways, my point is, I can't find a good guide, it's not that I'm being prideful, it's just that I have indeed searched and can't find a clear guide. I'm not sure if most assume we have to be S-off? In the past people used to mention "you have to be rooted, or unrooted, or unlocked bootloader, or S-on or S-off". Now it's not very clear so I'm confused, especially since those guides have so many links that I don't know what to download and each is 2GB. You're not the first to tell me that xda has many excellent guides without pointing me to one for the M9 haha.
I want a better reception among other things as it worries me that it was roaming out of nowhere and I'd love to go back to stock as I am not a fan of custom ROMs (except for on my 2010 Galaxy S1 lol).
I have to admit this is the most confusing phone when it comes to modding it or removing root to OTA.
I tried to run an RUU for AT&T latest Android 5.1 (when I was running stock 1.32) and it failed many times, even though I unrooted and locked bootloader. I miss the days of ODIN flashing in download mode =(.
I'm happy the ROM I'm using is stable but still.
Click to expand...
Click to collapse
I can see where you think my guide has a lot of links, but all you need to do is determine what your phone is now and choose the correct link for your device. To figure out your current Firmware just reboot your phone to download mode and it tells your OS version right their.
now you know your version download the one your on now or a newer version and RUU back to stock, It's actually easier than Odin
Read my entire instructions to convert to developer edition and you'll see it's not all that hard.
S-off is a pretty vital step if you plan on flashing your phone much at all, and is well worth the $25 price. But it's not needed if you just want your AT&T phone back to stock. Just lock the bootloader (fastboot oem lock). and Run the RUU.exe and your done you have a stock phone.
If your worried about the modified status you'll have to pay for the s-off to remove it.
clsA said:
I can see where you think my guide has a lot of links, but all you need to do is determine what your phone is now and choose the correct link for your device. To figure out your current Firmware just reboot your phone to download mode and it tells your OS version right their.
now you know your version download the one your on now or a newer version and RUU back to stock, It's actually easier than Odin
Read my entire instructions to convert to developer edition and you'll see it's not all that hard.
S-off is a pretty vital step if you plan on flashing your phone much at all, and is well worth the $25 price. But it's not needed if you just want your AT&T phone back to stock. Just lock the bootloader (fastboot oem lock). and Run the RUU.exe and your done you have a stock phone.
If your worried about the modified status you'll have to pay for the s-off to remove it.
Click to expand...
Click to collapse
Thanks for the answer. I saw yours a week ago and I skimmed through it and since it needs S-Off, I kept it for later. I have a question for you and I'll PM you if that's fine as I don't want to take over this thread.
clsA said:
and is well worth the $25 price.
Click to expand...
Click to collapse
S-off is only $25 now? Dang I paid 50 for each phone.
Ramsey said:
I have to admit this is the most confusing phone when it comes to modding it or removing root to OTA.
Click to expand...
Click to collapse
cLSA is very knowledgeable on the m9. When I first made the swith from Samsung to HTC I didn't know jack. But in the past few months I have realized the m9 is the easiest phone to customize that I've ever owned. If cLSA can't help you (I'm sure he's a busy guy) than I'm sure I could. I'm moving and dont have internet yet (right now I'm typing from my phone) but I can always turn on my hotspot and lend a hand.
First thing I recommend doing is to make sure you're adb and fastboot are updated to the latest version. Also make sure you have ever all the right drivers installed.
I'd also recommend getting s-off. Just makes life easier knowing you can flash anything you want (including older firmware). And if a stock phone is what you want than you can turn it back on
If your adb is working then with you phone plugged in and USB debugging clicked open a command prompt (as administrator) and type adb devices. You should then look at Your phone and grant the phone adb privelages. Following that you should see your phones serial number on your pc.
If you see that adb is installed properly, if not then go back and install adb properly. Pm me if you want me to walk you through anything.
Hello,
It has been a while since I have needed to do hard tinkering with a phone. Coming from a Moto X, the HTC scene is new to me.
I finally got the chance and acquired a new phone, a Verizon HTC M9 (himawl). Having read around here and there, info about this particular variant is scarce, but from what I gather, there seems to be trouble with unlocking bootloader, flashing, and installing a custom ROM. Coming from Moto X, I find the amount of bloatware and stock theme in applications/settings completely HIDEOUS.
Also, checking around I see things like S-OFF (security off from what I understand), temp-root, URR, and sunshine (an application from what I gather), and they just keep adding to the things I've read and I don't fully understand.
So to keep things short, I was wondering if someone could help me in what I NEED to get a functioning Cyanogen on a Verizon M9. Also if the bug with camera and bluetooth has been resolved.
1. Can the bootloader for "himawl" be unlocked?
2. Do I NEED S-OFF to flash a custom recovery? If so, can sunshine do it? Do I need to sent it to someone? (Being from Mexico, that can be tricky)
3. After flashing recovery, which ROM would best be suited for my needs (stable, functioning things, no bloatware)?
Sorry for this being long, but wanted some help consolidating all the bits and pieces out there...
P.S.
I dont CARE about verizon apps or advanced calling, as being from Mexico, I dont get ANY benefit from them being there..
OblivionWielder said:
Hello,
It has been a while since I have needed to do hard tinkering with a phone. Coming from a Moto X, the HTC scene is new to me.
I finally got the chance and acquired a new phone, a Verizon HTC M9 (himawl). Having read around here and there, info about this particular variant is scarce, but from what I gather, there seems to be trouble with unlocking bootloader, flashing, and installing a custom ROM. Coming from Moto X, I find the amount of bloatware and stock theme in applications/settings completely HIDEOUS.
Also, checking around I see things like S-OFF (security off from what I understand), temp-root, URR, and sunshine (an application from what I gather), and they just keep adding to the things I've read and I don't fully understand.
So to keep things short, I was wondering if someone could help me in what I NEED to get a functioning Cyanogen on a Verizon M9. Also if the bug with camera and bluetooth has been resolved.
1. Can the bootloader for "himawl" be unlocked?
2. Do I NEED S-OFF to flash a custom recovery? If so, can sunshine do it? Do I need to sent it to someone? (Being from Mexico, that can be tricky)
3. After flashing recovery, which ROM would best be suited for my needs (stable, functioning things, no bloatware)?
Sorry for this being long, but wanted some help consolidating all the bits and pieces out there...
P.S.
I dont CARE about verizon apps or advanced calling, as being from Mexico, I dont get ANY benefit from them being there..
Click to expand...
Click to collapse
No idea if there is cyanogen mod for the m9.
There is an AOSP ROM for m9 - candyrom (Google it)
Yes you need S-OFF or an unlocked bootloader to flash a custom recovery.
For Verizon you have 1 option - sending device to someone with a java card. A little searching goes along way.
http://forum.xda-developers.com/verizon-one-m9/general/m9-java-card-t3063247
andybones said:
No idea if there is cyanogen mod for the m9.
There is an AOSP ROM for m9 - candyrom (Google it)
Yes you need S-OFF or an unlocked bootloader to flash a custom recovery.
For Verizon you have 1 option - sending device to someone with a java card. A little searching goes along way.
http://forum.xda-developers.com/verizon-one-m9/general/m9-java-card-t3063247
Click to expand...
Click to collapse
Thanks for the response. What I mean with the question is that if I needed BOTH to flash a custom firmware, but from what I gather in your response either one i manage ought to do the trick .
I already have a copy of candy waiting for it.
I guess Ill search someone in mexico that can do java card. Thanks for the info
andybones said:
No idea if there is cyanogen mod for the m9.
There is an AOSP ROM for m9 - candyrom (Google it)
Yes you need S-OFF or an unlocked bootloader to flash a custom recovery.
For Verizon you have 1 option - sending device to someone with a java card. A little searching goes along way.
http://forum.xda-developers.com/verizon-one-m9/general/m9-java-card-t3063247
Click to expand...
Click to collapse
And while Candy isn't exacty CM, it's based off of it - kinds CM+. Works well.
Hello, so I'm going to be receiving my HTC One M9 tommorrow morning, and I was hoping the XDA community could help me with some fundemental questions regarding my new phone.
So, first off, this is a Verizon version, but I'm 95% certain that it comes factory unlocked. HTC6535LVWSG. I hear some people have issues rooting/S-OFFing the Verizon version (VZW at least, but I don't think mine is), but if it's not that version (or already unlocked, for that matter), does that mean that I will be able to load up any recovery from here? Assuming that I've gotten a recovery installed (my past phone was an EVO 3D, which I've tinkered quite a bit with), will I be able to use ROMs posted here? Or will I need to use specially made Verizon ROMs?
All of that aside, do you know where I can find the Marshmellow RUU that I heard just came out for the M9? As mentioned in the earlier paragraph, will I need a special GSM version for it?
EDIT: I found the news post at HTC, I'm assuming that it would work for any M9.
Thanks for anyone who responds!
Dino10or said:
Hello, so I'm going to be receiving my HTC One M9 tommorrow morning, and I was hoping the XDA community could help me with some fundemental questions regarding my new phone.
So, first off, this is a Verizon version, but I'm 95% certain that it comes factory unlocked. HTC6535LVWSG. I hear some people have issues rooting/S-OFFing the Verizon version (VZW at least, but I don't think mine is), but if it's not that version (or already unlocked, for that matter), does that mean that I will be able to load up any recovery from here? Assuming that I've gotten a recovery installed (my past phone was an EVO 3D, which I've tinkered quite a bit with), will I be able to use ROMs posted here? Or will I need to use specially made Verizon ROMs?
All of that aside, do you know where I can find the Marshmellow RUU that I heard just came out for the M9? As mentioned in the earlier paragraph, will I need a special GSM version for it?
EDIT: I found the news post at HTC, I'm assuming that it would work for any M9.
Thanks for anyone who responds!
Click to expand...
Click to collapse
NO! SLOW DOWN!
If you get a Verizon M9 do not flash anything!! Unless its specifically for the Verizon M9 or the developer of the ROM/Kernel states it will work with CDMA or Verizon M9's.
As of right now only the GSM Marshmallow update is out. Do not flash this RUU/update on a Verizon M9. It's better if you start off by just looking around for Verizon M9 threads. Ask questions in other threads if that particular ROM or file will work on a Verizon M9 or better yet read through most if not all the posts in those threads because more often than not someone in your shoes has already asked the same question.
But if you received a locked/S-ON device do not update/change anything on that phone until you've freshen up on whether or not S-OFF/Rooting is available for the software that comes already on it. It'll save you the headache of playing around with a new phone and it auto updates now your stuck without S-OFF.
Also don't ask questions in "General" that's what the Q&A section is for.
Congratulations! I think you'll be pleased with the M9.
Diaclaimer: I'm a hobbyist and not an expert - you should do some reading of threads and
research before attempting to hack your phone.
A few things:
- you may find better help in the Verizon HTC M9 forums (http://forum.xda-developers.com/verizon-one-m9)
- S-OFF is currently only possible on Verizon's variant of the M9 via a Java Clip. They're expensive, but there are fellow XDA members who own them and are willing to use theirs on your phone, usually for a reasonable fee
- until your bootloader is unlocked (pretty sure that your phone will NOT come that way - Verizon is not user-friendly) or you are S-OFF, you will not be able to flash a custom anything (recovery or ROM). Attempting to do so may render your phone unusable.
- Marshmallow has been released officially for the developer/unlocked variant of the M9, which is GSM-only. The Verizon variant is CDMA; the RUU will fail to install on your device.
Hope this is helpful. You probably have a bit more effort to go through to be able to hack your phone, but it's very doable and worth the effort. The M9 is a solid device and all the moreso once you have S-OFF (or an unlocked bootloader) and root.
Unfortunately, UPS Next Day Air has failed me, with yet another delay, so I won't have the phone today. :v
I know it's already paid off, and I'm pretty sure it's factory unlocked. What determines if it's a VWZ version or not? How does this affect my modding processes? I hear of several people who can do stuff to "non-VWZ" versions.
dottat said:
Not for the vzw m9. Big difference is the versions they can do already can use htc dev to bootloader unlock and root. Vzw is another can of worms because we need a root exploit before anything can happen.
Click to expand...
Click to collapse
So, I got the phone today. It was supposed to be delayed but I guess they managed to deliver it! I have to go, so the phone is gonna sit here for a couple hours, but it can boot into the bootloader (I'm not sure if this is a sign that it can be unlocked, but we'll see, I guess.)
Dino10or said:
So, I got the phone today. It was supposed to be delayed but I guess they managed to deliver it! I have to go, so the phone is gonna sit here for a couple hours, but it can boot into the bootloader (I'm not sure if this is a sign that it can be unlocked, but we'll see, I guess.)
Click to expand...
Click to collapse
Any phone can boot into the bootloader. To determine your phone's status, you'll need to look at the upper left corner when you are in bootloader mode: does it say 'unlocked' or 'locked'? Similarly, does it say 'S-ON' or 'S-OFF'?
First of all you should, in my opinion, deal with the differences of a CDSM to a GSM device in detail and read especially the Verizon specific threads in this forum very carefull.
Seconed to it you should pick up the full information about block based OTA politics, and the major changes regarding moddifications to Android 5.1.1. If never done before you should also read the basic threads abaut unlocking, rooting, fastboot as well as adb commands. If need for further help occurs it is hightly important to be able to explain when, where and assumingly why a problem/error occured.
Besides this have fun with your One M9!
HTCNerdYoda said:
First of all you should, in my opinion, deal with the differences of a CDSM to a GSM device in detail and read especially the Verizon specific threads in this forum very carefull.
Seconed to it you should pick up the full information about block based OTA politics, and the major changes regarding moddifications to Android 5.1.1. If never done before you should also read the basic threads abaut unlocking, rooting, fastboot as well as adb commands. If need for further help occurs it is hightly important to be able to explain when, where and assumingly why a problem/error occured.
Besides this have fun with your One M9!
Click to expand...
Click to collapse
Ah, I know the ins and outs of adb and fastboot already, as I've had my fair share of working with the HTC bootloader-- however I just wanted to clarify some things that I had not previously known. Thanks for the advise, though.
Guys please, anyone can verify that the buttons (power and volume) are a bit 'down after a few months of use??