Good day,
I've had my M8 for a couple years with no issues. A couple weeks ago it started disconnecting data and calls.
I noticed the SIM state keeps changing (i.e. unknown, ready) and cycling back and forth with the message "preparing SIM card".
If I let the phone sleep a bit, airplane mode will often show "turning off" and greyed out.
Tried a new SIM, no change.
Restored an earlier NAND, saved before the problem showed up, no change.
Was on the phone with the network provider (straight talk), no change.
Aside from running TWRP it's still the original VZW version Kitkat 4.4.2
I'm not sure how to trouble shoot this. If it's hardware, firmware?
Just wondering if anyone has encountered the issue. I read a couple posts elsewhere, but no insights.
Thanks
You have the M8 right? as this section if specific to the M8s (a different device from the M8). I know it's a bit confusing (not crazy about the forum structure on that note).
If so (M8), then it sounds similar to the guy in this thread: https://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-sim-emergency-calls-t3836108
Not the first guy (who replaced the screen) but the 2nd post (which happened spontaneously).
Besides the thing I suggested in that thread (Scotch tape on SIM trick, and/or flashing RUU - in your case Verizon only!) I don't think there is too much that can be done, as it might be a hardware failure.
redpoint73 said:
You have the M8 right? as this section if specific to the M8s (a different device from the M8). I know it's a bit confusing (not crazy about the forum structure on that note).
If so (M8), then it sounds similar to the guy in this thread: https://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-sim-emergency-calls-t3836108
Not the first guy (who replaced the screen) but the 2nd post (which happened spontaneously).
Besides the thing I suggested in that thread (Scotch tape on SIM trick, and/or flashing RUU - in your case Verizon only!) I don't think there is too much that can be done, as it might be a hardware failure.
Click to expand...
Click to collapse
Thanks for the reply. I'll try the tape trick. Flashing a newer RUU is an option. Re-flashing the firmware is something I am going to try.
I did read another post that did that, and no-joy. I'll keep poking around. For expedience I bought a LG G6 today, new. The US cell version unlocked. I will say the HTC M8 feels more solid still.
I should mention that Wifi, and bluetooth work fine. I can re-establish call/data connection temporarily with a reboot. Oddly, the the connection/SIM seems more stable at my office than at home. Makes me wonder if it's in the network, or it aggravates the issue.
PS - thanks for clarifying the forum, I missed the "s" in the title. I do have the M8 only.
I'll post, if I fix anything.
Cremnomaniac said:
Flashing a newer RUU is an option. Re-flashing the firmware is something I am going to try.
Click to expand...
Click to collapse
Certainly can't hurt to install a newer RUU. If nothing else, it's typically good from a security perspective to have the phone as updated as possible.
Something I eluded to earlier, but just to be clearer: Make sure you only try RUUs specific for Verizon M8. Those RUUs can be found here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
RUU for any other version M8 are not compatible with your device. Flashing them will result in a radio brick!
redpoint73 said:
Certainly can't hurt to install a newer RUU. If nothing else, it's typically good from a security perspective to have the phone as updated as possible.
Something I eluded to earlier, but just to be clearer: Make sure you only try RUUs specific for Verizon M8. Those RUUs can be found here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
RUU for any other version M8 are not compatible with your device. Flashing them will result in a radio brick!
Click to expand...
Click to collapse
Thanks for heads up. I do have all the appropriate RUU's already 4.4.4 to 6.0 S/on and S/off
I did a lot of research before, but at some point I got busy and never followed through. I have another LG phone here. So now is as good a time as any to update. I still enjoy my M8. Hardware trouble shooting is beyond my skill level, but does anyone do it?
Related
So, I previously had an optimus v, which is like the easiest phone to root and get roms for and what not. Well i was hoping that the One V would be the same, it was not.
So I tried to install some rom that i liked after going through the unlocking and rooting process,and it had a restarting problem where every 5-15 seconds after it would boot it would restart. I found a solution (kind of) to that but most of the links where dead so i had to find them on my own. It led me to putting a custom kernel on it and that did not fix it, so i saw something that getting the OTA update that came out a while ago could cause this, and the only way to return it was to use RUU (i still had a custom kernel at this point, i think) so i got the (hopefully) correct recovery.img from RUU and i flashed that and the next step is to relock the device, so i did via command prompt, and i started RUU up again and it was doing its thing and ended in an error 155. I have tried several times and it has still not worked. I found some stuff saying that the HBOOT i have which is 1.57 doesnt have a supported RUU or something to that effect ( i found lots of conflicting information).
So now i am stuck with a phone that only goes to the bootloader menu and because its relocked i cant flash anything to it.
I have tried fastboot oem unlock and that came up with a command error, and everything else i try to flash just fails.
Any help is welcome and a thank you in advance to anyone that helps.
matterlord1 said:
So, I previously had an optimus v, which is like the easiest phone to root and get roms for and what not. Well i was hoping that the One V would be the same, it was not.
So I tried to install some rom that i liked after going through the unlocking and rooting process,and it had a restarting problem where every 5-15 seconds after it would boot it would restart. I found a solution (kind of) to that but most of the links where dead so i had to find them on my own. It led me to putting a custom kernel on it and that did not fix it, so i saw something that getting the OTA update that came out a while ago could cause this, and the only way to return it was to use RUU (i still had a custom kernel at this point, i think) so i got the (hopefully) correct recovery.img from RUU and i flashed that and the next step is to relock the device, so i did via command prompt, and i started RUU up again and it was doing its thing and ended in an error 155. I have tried several times and it has still not worked. I found some stuff saying that the HBOOT i have which is 1.57 doesnt have a supported RUU or something to that effect ( i found lots of conflicting information).
So now i am stuck with a phone that only goes to the bootloader menu and because its relocked i cant flash anything to it.
I have tried fastboot oem unlock and that came up with a command error, and everything else i try to flash just fails.
Any help is welcome and a thank you in advance to anyone that helps.
Click to expand...
Click to collapse
You should be able to flash a stock RUU for your device while it's in the bootloader menu from here:
http://androidfiles.org/ruu/?developer=Primo
make sure to download the correct RUU for your carrier/radio band and if its GSM (PRIMOU) or CDMA (PRIMOC), or you can screw it up more.
What network carrier are you with?
EDIT:, Just re-read your post, sorry. I don't know if anyone has posted a RUU for the updated radio, that Virgin Mobile released, you may need to get ahold of Football on this forum and see if he's still helping find/sell RUU's that you need.
Back in the day I had to get ahold of him to get the RUU for my phone that wasn't listed on any RUU site.
FreakyFreakGA said:
You should be able to flash a stock RUU for your device while it's in the bootloader menu from here:
make sure to download the correct RUU for your carrier/radio band and if its GSM (PRIMOU) or CDMA (PRIMOC), or you can screw it up more.
What network carrier are you with?
EDIT:, Just re-read your post, sorry. I don't know if anyone has posted a RUU for the updated radio, that Virgin Mobile released, you may need to get ahold of Football on this forum and see if he's still helping find/sell RUU's that you need.
Back in the day I had to get ahold of him to get the RUU for my phone that wasn't listed on any RUU site.
Click to expand...
Click to collapse
I don't really know about buying RUU's, that's like blackberry with their pay to unlock the imei thing. although if it saves me from having to buy a new phone ill consider it.
matterlord1 said:
I don't really know about buying RUU's, that's like blackberry with their pay to unlock the imei thing. although if it saves me from having to buy a new phone ill consider it.
Click to expand...
Click to collapse
I paid like $13 for mine, but it gave me piece of mind should the phone ever soft brick or hard brick with boot, that I can recover it and not lose a phone. I don't know if he's even around anymore, but I posted a thread in general asking if he was. I am on Alltel, but one of my family members bought an HTC One V with the updated radio, so for her I couldn't do anything but root. I know there are a few new radio friendly ROM's in the CDMA section of this forum that would of boot with a custom rom and the kernel.
FreakyFreakGA said:
I paid like $13 for mine, but it gave me piece of mind should the phone ever soft brick or hard brick with boot, that I can recover it and not lose a phone. I don't know if he's even around anymore, but I posted a thread in general asking if he was. I am on Alltel, but one of my family members bought an HTC One V with the updated radio, so for her I couldn't do anything but root. I know there are a few new radio friendly ROM's in the CDMA section of this forum that would of boot with a custom rom and the kernel.
Click to expand...
Click to collapse
yeah i found some ROM's that will work only after this happened. In my research i found something about downgrading HBOOT i only saw it on other phones and it did not look like something i wanted to mess with. And my HTC One V is CDMA on Virgin Mobile.
matterlord1 said:
yeah i found some ROM's that will work only after this happened. In my research i found something about downgrading HBOOT i only saw it on other phones and it did not look like something i wanted to mess with. And my HTC One V is CDMA on Virgin Mobile.
Click to expand...
Click to collapse
UPDATE: So i figured it out, I went and i reflashed the Unlock_code.bin file and now its back to unlocked again. Thanks to FreakyFreakGA to doing his best to help me out.
Be sure to flash an OTA-compatible ROM. Try RhythmicROM or CyanPrimo, both of which I've used for a long time and can attest that they are better HTC One V ROMs.
matterlord1 said:
UPDATE: So i figured it out, I went and i reflashed the Unlock_code.bin file and now its back to unlocked again. Thanks to FreakyFreakGA to doing his best to help me out.
Click to expand...
Click to collapse
so matterlord what rom are you running right now? were you ever able to revert back to stock? I am having the same problem you did.
gotts101 said:
so matterlord what rom are you running right now? were you ever able to revert back to stock? I am having the same problem you did.
Click to expand...
Click to collapse
I never tried to go back to stock, I'm running rhythmic ROM, can't link right now but it seems to work pretty well, its slightly faster than stock when all my stuff is on there and the only problem so far is sometimes when you lock the device and then quickly unlock it then it will freeze and restart.
matterlord1 said:
I never tried to go back to stock, I'm running rhythmic ROM, can't link right now but it seems to work pretty well, its slightly faster than stock when all my stuff is on there and the only problem so far is sometimes when you lock the device and then quickly unlock it then it will freeze and restart.
Click to expand...
Click to collapse
Yeah I just flashed Rhythmic. Seems pretty nice by my wifi is having some weird authentication problem. It doesn't seem like there are very many ROMs out there that would work though.
gotts101 said:
Yeah I just flashed Rhythmic. Seems pretty nice by my wifi is having some weird authentication problem. It doesn't seem like there are very many ROMs out there that would work though.
Click to expand...
Click to collapse
Yeah, make sure you find the right version for your radio, virgin mobile made a terrible move by updating it so you cant do much with it.
Or kernel or something, anyways mine was v5.2 and it was a pain, i think there was a lot more kernels available for older versions.
Best of luck, and if you are having problems with authentication then try using WPS, in some cases it fixes those types of problems.
Hey guys, this is my first HTC device. I've been reading through the threads here and in the intl forum and I just wanted to get a little info in one place as to what we can flash for this device. I sent mine off to someone with a Java Card, so now that I'm good to go, I wanted to see what all I (and other VZW users) can do at this early stage in the game. I know that until there is an easier way to S-Off/root/etc than sending your device to someone it is still kinda rocky as to development on this particular device, but I've heard mixed reviews on what ROMs/kernels are good to flash.
I assume that as long as I've got a custom recovery, flashing ROMs on this device would be the same as the other devices I've used... just pick the file in TWRP and flash, right?
As far as ROMs go, I've read that ViperOne works, along with InsertCoin with nothing extra.. just flash and go apparently. As for other ROMs, a little editing and some files from the stock VZW ROM should make them work, right? What files exactly would be needed?
Basically, if you've flashed anything, post your results here. What works, what doesn't, anything I should do before I start flashing myself. Any good threads I should read before I jump in. Thanks guys!
I have a thread about the roms in this forum named VZW M9 roms.
Basically the ones you've named I've tried with success. Also LeeDrOiD rom added Verizon support today. Build 7.5.
jtommyj said:
I have a thread about the roms in this forum named VZW M9 roms.
Basically the ones you've named I've tried with success. Also LeeDrOiD rom added Verizon support today. Build 7.5.
Click to expand...
Click to collapse
I never claimed to be a genius I've read through your thread, that's where I got the ROMs that worked... My brain wasn't working at full capacity when I made the thread. Thanks.
That being said though, lets assume that a soft-brick occurs. How would one go about fixing that? In my experience with the S4 and the device I had previous to that, it was simple to fix a soft-brick as long as I still had recovery access. Would the same be true for the M9? What about reverting to stock.. as in stock recovery, firmware, etc. Also, from what I've seen, adb tends to be used a bit more for this device than others that I'm used to. Not that I have a problem with it, I just haven't used it very much and will likely have to brush up a little bit on the nuances of it. I just don't want to create a $650 paperweight so I want to be absolutely sure that what I'm doing can be fixed, and that I avoid doing things that CAN'T be fixed.
lordcheeto03 said:
I never claimed to be a genius I've read through your thread, that's where I got the ROMs that worked... My brain wasn't working at full capacity when I made the thread. Thanks.
That being said though, lets assume that a soft-brick occurs. How would one go about fixing that? In my experience with the S4 and the device I had previous to that, it was simple to fix a soft-brick as long as I still had recovery access. Would the same be true for the M9? What about reverting to stock.. as in stock recovery, firmware, etc. Also, from what I've seen, adb tends to be used a bit more for this device than others that I'm used to. Not that I have a problem with it, I just haven't used it very much and will likely have to brush up a little bit on the nuances of it. I just don't want to create a $650 paperweight so I want to be absolutely sure that what I'm doing can be fixed, and that I avoid doing things that CAN'T be fixed.
Click to expand...
Click to collapse
Well first thing you need to have a custom recovery flashed.
Then you would need to backup your stock system. If you are in a soft brick then volume up and power being held at the same time should get you out of it.
There should not be a need to refresh firmware since the original firmware is all we have. I do believe an Ruu is being worked on currently.
Final word- if you're unsure,don't!!
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, 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??
Ok, same phone, AT&T HTC M9, now S-Off, TWRP 3.0.2.0, 3.38.502.41 firmware. Tried ARHD 20.0, had no service, flashed boot.img, got service but lost wifi. Tried Viperone M9 4.3, same issue. ICE, same issue. If I have Wifi, I have no service. If I flash boot.img, I get service, but lose Wifi. I'm pulling my hair out right now, as I've searched high and low and I've been looking at my PC and M9 for about 14 hours now. Anyone have any insight?
Does the rom match your firmware version?
Edit: just read your other thread and replied.
The firmware versions are off so I wouldn't trust it. Htc's are crap when it comes to recovery so be careful.
I have stayed on 6.0 with root and s-off, without xposed for a very good reason!.
If I were you, as I said in your other thread, would be going back to stock at this point and hoping for the best that the damage isn't permanent.
Its too risky to mess with htc devices. They don't have an app like odin or one even half as good.
You have a beast of a phone as is. You don't need to beef it up any more than it is.
Beamed in by telepathy.
shivadow said:
Does the rom match your firmware version?
Edit: just read your other thread and replied.
The firmware versions are off so I wouldn't trust it. Htc's are crap when it comes to recovery so be careful.
I have stayed on 6.0 with root and s-off, without xposed for a very good reason!.
If I were you, as I said in your other thread, would be going back to stock at this point and hoping for the best that the damage isn't permanent.
Its too risky to mess with htc devices. They don't have an app like odin or one even half as good.
You have a beast of a phone as is. You don't need to beef it up any more than it is.
Beamed in by telepathy.
Click to expand...
Click to collapse
It's a bit of a long story as to why I decided to root. It's not damaged by any means, if I flash the ROM posted here (https://forum.xda-developers.com/at...ficial-att-3-38-502-12-rom-7-01-2016-t3409354), Wifi and data both work flawlessly, despite it having a different firmware number. The whole ROM is actually decent, but lacks all the customization I want, and for some reason, headphones only work on one side. I hoped this fix would be simple, as so many people seem to run custom ROMs and I'm just over here yelling at my inanimate object
shivadow said:
Does the rom match your firmware version?
Edit: just read your other thread and replied.
The firmware versions are off so I wouldn't trust it.
I have stayed on 6.0 with root and s-off, without xposed for a very good reason!.
If I were you, as I said in your other thread, would be going back to stock at this point and hoping for the best that the damage isn't permanent.
Its too risky to mess with htc devices.
You have a beast of a phone as is. You don't need to beef it up any more than it is.
Beamed in by telepathy.
Click to expand...
Click to collapse
None of the things manlavi did, so far, was risky. The phone didn't take any damage. All he did was flashing a rom that is incompatible with his firmware like many did before him. The only difference is that HTC seems to have changed some more parts of the firmware with the latest AT&T update so that not only the boot image is incompatible. But that only makes it harder to make the rom compatible. The phone doesn't get damaged in any kind.
If he had flashed a firmware that is incompatible with his phone that would be a whole different story. However, before he opened this thread his phone wasn't S-OFF so he wouldn't have been able to do so even if he wanted.
manlavi95 said:
It's a bit of a long story as to why I decided to root. It's not damaged by any means, if I flash the ROM posted here (https://forum.xda-developers.com/at...ficial-att-3-38-502-12-rom-7-01-2016-t3409354), Wifi and data both work flawlessly, despite it having a different firmware number. The whole ROM is actually decent, but lacks all the customization I want, and for some reason, headphones only work on one side. I hoped this fix would be simple, as so many people seem to run custom ROMs and I'm just over here yelling at my inanimate object
Click to expand...
Click to collapse
The headphones might be broken. Did you check whether they work correctly with a different device?
As already said in the other thread you could convert your phone to another GSM variant of the M9. You would need to change your CID and your MID and then you could flash a RUU with a different SKU. However, you need to be aware that you'll lose every AT&T specific tweaks and functions by doing so. Instructions for converting for example to the US dev edition of the M9 are linked in the readme thread.
Alternatively you could try xposed and the sense tool box on a rooted stock rom. This way you could enable many customisations without having to change your firmware. If you choose this option you should get back to the correct stock rom for your firmware by flashing the RUU I linked in your other thread.
Flippy498 said:
None of the things manlavi did, so far, was risky. The phone didn't take any damage. All he did was flashing a rom that is incompatible with his firmware like many did before him. The only difference is that HTC seems to have changed some more parts of the firmware with the latest AT&T update so that not only the boot image is incompatible. But that only makes it harder to make the rom compatible. The phone doesn't get damaged in any kind.
If he had flashed a firmware that is incompatible with his phone that would be a whole different story. However, before he opened this thread his phone wasn't S-OFF so he wouldn't have been able to do so even if he wanted.
The headphones might be broken. Did you check whether they work correctly with a different device?
As already said in the other thread you could convert your phone to another GSM variant of the M9. You would need to change your CID and your MID and then you could flash a RUU with a different SKU. However, you need to be aware that you'll lose every AT&T specific tweaks and functions by doing so. Instructions for converting for example to the US dev edition of the M9 are linked in the readme thread.
Alternatively you could try xposed and the sense tool box on a rooted stock rom. This way you could enable many customisations without having to change your firmware. If you choose this option you should get back to the correct stock rom for your firmware by flashing the RUU I linked in your other thread.
Click to expand...
Click to collapse
I tested the headphones on another rom and my computer, they had no issues with that. I'm working on converting it to the dev edition. I've changed my CID, but I'm a little afraid that this write-up is a bit out of date, so I'm currently searching for the right RUU.
manlavi95 said:
I tested the headphones on another rom and my computer, they had no issues with that. I'm working on converting it to the dev edition. I've changed my CID, but I'm a little afraid that this write-up is a bit out of date, so I'm currently searching for the right RUU.
Click to expand...
Click to collapse
It's linked in my thread, as well. Directly behind the link to the newer version of the conversion guide. However, it doesn't matter whether you use that old 3.x RUU or a newer one. You just need to install some OTAs while being on stock rom, afterwards, if you choose to use the old one. Be aware that most of the custom roms aren't compatible, yet, with the new 4.x firmware. So only update until your device suggests you to install the 4.x OTA.
Flippy498 said:
It's linked in my thread, as well. Directly behind the link to the newer version of the conversion guide. However, it doesn't matter whether you use that old 3.x RUU or a newer one. You just need to install some OTAs while being on stock rom, afterwards, if you choose to use the old one. Be aware that most of the custom roms aren't compatible, yet, with the new 4.x firmware. So only update until your device suggests you to install the 4.x OTA.
Click to expand...
Click to collapse
Currently downloading the 3.35.617.12 RUU and the HTC Fastboot as I don't have an SD smaller than 32GB. I don't know how I've read that entire Q&A a few times over and didn't see that, so thanks as always
manlavi95 said:
Currently downloading the 3.35.617.12 RUU and the HTC Fastboot as I don't have an SD smaller than 32GB. I don't know how I've read that entire Q&A a few times over and didn't see that, so thanks as always
Click to expand...
Click to collapse
You don't need an SD card with less than 32gb if you're on firmware 3.x (and that is what you currently are). With firmware 3.x and above HTC enabled the usage of exfat formatted SD cards for RUU flashing.
Used the SD method, my phone is now running developer edition. Speaking technically once again, I should be able to use ROMs and have them work now, I imagine. Wifi and cellular both work after flashing dev edition.j
manlavi95 said:
Used the SD method, my phone is now running developer edition. Speaking technically once again, I should be able to use ROMs and have them work now, I imagine. Wifi and cellular both work after flashing dev edition.j
Click to expand...
Click to collapse
Correct.
IT WORKS. IT WOOOOOORKS. Thank you so much.