Related
Hey guys,
I saw these two codenames flying around here and I just wanted to know what the difference is.
Greetz.
forgiveMySin said:
Hey guys,
I saw these two codenames flying around here and I just wanted to know what the difference is.
Greetz.
Click to expand...
Click to collapse
These are product numbers, the m8_ul is the sim unlocked/unbranded model, whereas the m8_wl is the Verizon carrier model
More info and how to check your number below:
http://droider.eu/2014/09/20/htc-one-m8-models/
gsmyth said:
whereas the m8_wl is the Verizon carrier model
Click to expand...
Click to collapse
Some additional observations: Based on your link, codenames with wl, wlv or whl are for CDMA variants (Sprint, Verizon).
While all GSM variants are essentially the same hardware (only some minor cosmetic differences on some carrier branded versions) the CDMA variant is actually different hardware and should be avoided unless your carrier uses CDMA (probably want to avoid unless you are on US Sprint or Verizon).
Additionally, you should not flash any mods on a GSM variant that are intended for CDMA versions; or vice versa. Doing so may result in a brick!
Thanks you two,
I already knew that with CDMA, but thanks anyway
redpoint73 said:
Some additional observations: Based on your link, codenames with wl, wlv or whl are for CDMA variants (Sprint, Verizon).
While all GSM variants are essentially the same hardware (only some minor cosmetic differences on some carrier branded versions) the CDMA variant is actually different hardware and should be avoided unless your carrier uses CDMA (probably want to avoid unless you are on US Sprint or Verizon).
Additionally, you should not flash any mods on a GSM variant that are intended for CDMA versions; or vice versa. Doing so may result in a brick!
Click to expand...
Click to collapse
What hardware is different? This is news to me . . . How are all the AOSP ROMs unified then? How is the HK adsp flashable on all variants?
Captain_Throwback said:
What hardware is different? This is news to me . . . How are all the AOSP ROMs unified then? How is the HK adsp flashable on all variants?
Click to expand...
Click to collapse
Would have been nice if we actually had service manuals to make these types of comparisons without having to disassemble the phone just to take a look at actual hardware differences.
But it's not like they'd put in something like that seeing as the phone only costs $700 At least they could have a service manual book that they can sell seperately.
http://provinspc2.free.fr/ftpSM/index.php/HTC/
...
Captain_Throwback said:
What hardware is different? This is news to me . . . How are all the AOSP ROMs unified then? How is the HK adsp flashable on all variants?
Click to expand...
Click to collapse
I was told over and over when I first started messing with my phone that I couldn't flash an international version of a ROM on my VZW phone but I thought really, how different can they be?
I live outside the US and don't use CDMA at all and couldn't get my ****ty MVNO provider to work for data no matter how many APN settings I tried. I flashed a int'l version of the ROM and then the stock VZW kernel.
It works 100% fine, I have none of the verizon crap on my phone including perpetual roaming notifications. LTE hasn't worked (I think there's a band difference with my type of phone) but I don't really want to pay a bunch extra for it anyway so I don't care; i'll stick with 3G and wifi.
I'm not going to go flash some non-VZW firmware or anything but you're not going to brick your phone with a non-CDMA ROM. You just might have a phone that doesn't want to connect to the network or access wifi.
AmbitiousDonut said:
I'm not going to go flash some non-VZW firmware or anything but you're not going to brick your phone with a non-CDMA ROM. You just might have a phone that doesn't want to connect to the network or access wifi.
Click to expand...
Click to collapse
I'd tread carefully about doing any such thing. I've seen at least 1 or 2 folks on here that bricked their CDMA M8 after flashing a GSM ROM or recovery (can't remember precisely which).
---------- Post added at 10:39 AM ---------- Previous post was at 10:33 AM ----------
Captain_Throwback said:
What hardware is different? This is news to me . . . How are all the AOSP ROMs unified then? How is the HK adsp flashable on all variants?
Click to expand...
Click to collapse
Maybe I've got the details wrong. But that was my understanding based on post by others. And as just mentioned, I've seen at least a report or 2 of bricking after flashing a GSM mod on a CDMA phone.
I just saw it mentioned on another thread that CM11 supports CDMA variants, so I'm curious about that as well. But if the hardware is the same, why are the recoveries (at least TWRP) different? I'm asking as much as making a point here, as again I'm curious.
I'd still maintain folks should not flash ROMs not meant for their type (GSM versus CDMA); or at a minimum to tread very carefully if you decide you want to. It should go without saying, if a ROM is not stated to support your carrier version, you should proceed with caution and at least do some research before proceeding.
And not sure what the intent of the OP is; but if they are looking to make a purchase, I also do not recommend any of the CDMA variants unless your carrier has a CDMA network (which is very unlikely unless you are on Verizon or Sprint in the US).
redpoint73 said:
I'd tread carefully about doing any such thing. I've seen at least 1 or 2 folks on here that bricked their CDMA M8 after flashing a GSM ROM or recovery (can't remember precisely which).
---------- Post added at 10:39 AM ---------- Previous post was at 10:33 AM ----------
Maybe I've got the details wrong. But that was my understanding based on post by others. And as just mentioned, I've seen at least a report or 2 of bricking after flashing a GSM mod on a CDMA phone.
I just saw it mentioned on another thread that CM11 supports CDMA variants, so I'm curious about that as well. But if the hardware is the same, why are the recoveries (at least TWRP) different? I'm asking as much as making a point here, as again I'm curious.
I'd still maintain folks should not flash ROMs not meant for their type (GSM versus CDMA); or at a minimum to tread very carefully if you decide you want to. It should go without saying, if a ROM is not stated to support your carrier version, you should proceed with caution and at least do some research before proceeding.
And not sure what the intent of the OP is; but if they are looking to make a purchase, I also do not recommend any of the CDMA variants unless your carrier has a CDMA network (which is very unlikely unless you are on Verizon or Sprint in the US).
Click to expand...
Click to collapse
The recoveries aren't different (anymore) - at least not TWRP.
The hardware is the same on all M8 variants (besides Dual SIM). The radios differ, and there is some carrier customization in the ramdisk and build.prop. But that's it.
redpoint73 said:
I'd tread carefully about doing any such thing. I've seen at least 1 or 2 folks on here that bricked their CDMA M8 after flashing a GSM ROM or recovery (can't remember precisely which).
---------- Post added at 10:39 AM ---------- Previous post was at 10:33 AM ----------
Maybe I've got the details wrong. But that was my understanding based on post by others. And as just mentioned, I've seen at least a report or 2 of bricking after flashing a GSM mod on a CDMA phone.
I just saw it mentioned on another thread that CM11 supports CDMA variants, so I'm curious about that as well. But if the hardware is the same, why are the recoveries (at least TWRP) different? I'm asking as much as making a point here, as again I'm curious.
I'd still maintain folks should not flash ROMs not meant for their type (GSM versus CDMA); or at a minimum to tread very carefully if you decide you want to. It should go without saying, if a ROM is not stated to support your carrier version, you should proceed with caution and at least do some research before proceeding.
And not sure what the intent of the OP is; but if they are looking to make a purchase, I also do not recommend any of the CDMA variants unless your carrier has a CDMA network (which is very unlikely unless you are on Verizon or Sprint in the US).
Click to expand...
Click to collapse
I would bet 99% they bricked it from installing the wrong recovery and not the wrong ROM. Or it was for a totally different phone, not just the GSM version of the ROM for their phone.
Correct me if I'm wrong (still new to this), but I didn't think the ROMs changed enough (like partitions and such) to actually brick the phone if you say, select the wrong one in aroma on install. If you were to flash a different recovery, or hboot, or....pretty much anything other than a ROM, I could see there being issues. Or flashing anything (ROM included) for a totally different phone (like the m7), as opposed to the other cell provider variant of the same phone.
But, like you said, I wouldn't get a CDMA phone unless I absolutely had to....and in my case it was $100 for a brand new CDMA m8 as opposed to the $600 for the int'l version I ideally wanted. Opportunity cost of $500 and CDMA phone was worth it to me. At least now I can help people traveling to Europe with their Verizon phone and whether or not certain things will work....
AmbitiousDonut said:
I would bet 99% they bricked it from installing the wrong recovery and not the wrong ROM. Or it was for a totally different phone, not just the GSM version of the ROM for their phone.
Correct me if I'm wrong (still new to this), but I didn't think the ROMs changed enough (like partitions and such) to actually brick the phone if you say, select the wrong one in aroma on install. If you were to flash a different recovery, or hboot, or....pretty much anything other than a ROM, I could see there being issues. Or flashing anything (ROM included) for a totally different phone (like the m7), as opposed to the other cell provider variant of the same phone.
But, like you said, I wouldn't get a CDMA phone unless I absolutely had to....and in my case it was $100 for a brand new CDMA m8 as opposed to the $600 for the int'l version I ideally wanted. Opportunity cost of $500 and CDMA phone was worth it to me. At least now I can help people traveling to Europe with their Verizon phone and whether or not certain things will work....
Click to expand...
Click to collapse
This isn't necessarily true. While most of the variants share the same partition layout, the Verizon variant has an extra partition, shifting out the number of the block devices by one when compared to the other variants. If the ROM zip flashed uses the block device number for flashing, this can indeed "soft brick" a device.
NOTE: This is NOT a hardware difference. It's the same nand/emmc, just partitioned slightly differently for Verizon.
Captain_Throwback said:
This isn't necessarily true. While most of the variants share the same partition layout, the Verizon variant has an extra partition, shifting out the number of the block devices by one when compared to the other variants. If the ROM zip flashed uses the block device number for flashing, this can indeed "soft brick" a device.
NOTE: This is NOT a hardware difference. It's the same nand/emmc, just partitioned slightly differently for Verizon.
Click to expand...
Click to collapse
I don't have a dog in this hunt, since I've got a GSM M8, so this is just out of curiosity.
Couldn't you S-off, switch your CID/MID to Sprint, and run a Sprint RUU to "fix" that, then reload the Verizon radio to recover network function? That assumes that both Sprint and Verizon phones use the same radio hardware, of course.
jshamlet said:
I don't have a dog in this hunt, since I've got a GSM M8, so this is just out of curiosity.
Couldn't you S-off, switch your CID/MID to Sprint, and run a Sprint RUU to "fix" that, then reload the Verizon radio to recover network function? That assumes that both Sprint and Verizon phones use the same radio hardware, of course.
Click to expand...
Click to collapse
I refuse to speculate about the effects of doing something like this. As this goes beyond the purview of this thread, I will digress.
Captain_Throwback said:
This isn't necessarily true. While most of the variants share the same partition layout, the Verizon variant has an extra partition, shifting out the number of the block devices by one when compared to the other variants. If the ROM zip flashed uses the block device number for flashing, this can indeed "soft brick" a device.
NOTE: This is NOT a hardware difference. It's the same nand/emmc, just partitioned slightly differently for Verizon.
Click to expand...
Click to collapse
Interesting, didn't know that. Thanks.
I guess since I learned how to use adb/fastboot for things instead of relying on an app like Flashify I've gotten a bit more fearless about potentially soft-bricking it. I figure worst case I'll learn something new and be using my old N4 until I get it fixed.
AmbitiousDonut said:
Interesting, didn't know that. Thanks.
I guess since I learned how to use adb/fastboot for things instead of relying on an app like Flashify I've gotten a bit more fearless about potentially soft-bricking it. I figure worst case I'll learn something new and be using my old N4 until I get it fixed.
Click to expand...
Click to collapse
Yeah partition is out by one which is why some Verizon users had a bootloop when flashing TWRP.
TWRP developers place the command as
Code:
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43
instead of
Code:
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p44
As the recovery on the GSM is in block43 but block 43 on the Verizon was the boot partition. :laugh:
BerndM14 said:
Yeah partition is out by one which is why some Verizon users had a bootloop when flashing TWRP.
TWRP developers place the command as
Code:
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43
instead of
Code:
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p44
As the recovery on the GSM is in block43 but block 43 on the Verizon was the boot partition. :laugh:
Click to expand...
Click to collapse
That's been updated for a while now, though . . .
Captain_Throwback said:
That's been updated for a while now, though . . .
Click to expand...
Click to collapse
Yeah I know, just adding to your post about the 1 extra partition on Verizon and how it caused some "fun" early on by having them "flash" recovery to boot partition because the partition block was out by 1.
AmbitiousDonut said:
I would bet 99% they bricked it from installing the wrong recovery and not the wrong ROM. Or it was for a totally different phone, not just the GSM version of the ROM for their phone.
Click to expand...
Click to collapse
That could be. I'm just throwing out what I can remember reading.
I'll still maintain that one should take care flashing anything that doesn't specifically support the CDMA variant, or verified to work by others. Even if a brick is not possible when flashing a GSM ROM, other issues can still occur. I'm seeing a couple other posts right now where the Sprint/Verizon GPS files are apparently different, causing GPS to be broken after flashing some ROMs.
Like Post #12 put well, I don't have a dog in this myself either. Just mentioning what I've see reported as FYI to others.
---------- Post added at 12:49 PM ---------- Previous post was at 12:41 PM ----------
Captain_Throwback said:
this goes beyond the purview of this thread
Click to expand...
Click to collapse
In think much of this discussion has gone far beyond what the OP intended. But interesting, nonetheless!
---------- Post added at 12:52 PM ---------- Previous post was at 12:49 PM ----------
Captain_Throwback said:
The hardware is the same on all M8 variants (besides Dual SIM). The radios differ, and there is some carrier customization in the ramdisk and build.prop. But that's it.
Click to expand...
Click to collapse
I stand corrected. I've seen more than a few posts about not flashing ROMs and other things between the versions (GSM vs. CDMA), and there being a hardware difference. So I was just relaying what I read.
Thanks for setting me straight.
redpoint73 said:
That could be. I'm just throwing out what I can remember reading.
I'll still maintain that one should take care flashing anything that doesn't specifically support the CDMA variant, or verified to work by others. Even if a brick is not possible when flashing a GSM ROM, other issues can still occur. I'm seeing a couple other posts right now where the Sprint/Verizon GPS files are apparently different, causing GPS to be broken after flashing some ROMs.
Like Post #12 put well, I don't have a dog in this myself either. Just mentioning what I've see reported as FYI to others.
---------- Post added at 12:49 PM ---------- Previous post was at 12:41 PM ----------
In think much of this discussion has gone far beyond what the OP intended. But interesting, nonetheless!
---------- Post added at 12:52 PM ---------- Previous post was at 12:49 PM ----------
I stand corrected. I've seen more than a few posts about not flashing ROMs and other things between the versions (GSM vs. CDMA), and there being a hardware difference. So I was just relaying what I read.
Thanks for setting me straight.
Click to expand...
Click to collapse
I have tried weaksauce and it won't open. I'm on 5.0. how is this puppy rooted? I tried kingroot but I keep getting root auth error
jerryspring said:
I have tried weaksauce and it won't open. I'm on 5.0. how is this puppy rooted? I tried kingroot but I keep getting root auth error
Click to expand...
Click to collapse
Which "puppy" would that be? This thread refers to two different variants (m8_ul versus m8_wl) which also have different root methods.
For most M8 versions (m8_ul) root method is to unlock bootloader, flash custom recovery and flash SuperSU.
I've read that the att version of this has a locked bootloader. I've also skimmed and read there are different versions of the bootloader for this phone as well.
My question is that I'm going to try to buy one off ebay but I want to make certain that I can root and install custom roms and kernels. I don't care about warranty info so thats no problem. However can you root on any bootloader or only the old one? If there is any info on this I'd to read about it. I just don't want to buy an updated phone and not be able to do anything with it like I did my optimus g pro which is not properly unlocked. Because if the bootloader effects this then I'll have to ask selllers what version it has and they likely won't know. I also read there are different modems and such with this. I just want to make sure i have total control over this phone unlike some that haven't been hacked thoroughly.:angel:
So if anyone wants to call me a noob and direct me towards a thread here I would gladly appreciate it.
The T-Mobile version DOES NOT have a locked bootloader, only Knox. Make sure you get an SM-N900T if you don't like locked bootloaders. The AT&T version is labeled SM-N900A, verizion is SM-N900V, and sprint is SM-N900P. All except the SM-N900T (and the Canadian SM-N900W8) have locked bootloaders.
Rather than start a new thread, I got a note3 in the mail. I know its an n900t but i don't know anything else about it yet.
my question is, I've seen a few things that say hlte and hltetmo. I'm researching how to do this stuff so I kinda know about it when the phone gets here. My question is, Ive seen this on the cyanogenmod website and twrp website.
Whats the difference? if any? I assume the tmo versions are for our phones, but if the regular hlte work then why the "split" in versions?
also what is generally the "best" most compatible recovery? I've seen cwm, philz cwm and twrp. I was just wondering if someone could just tell me which is the most stable
I just got the phone so i'll be looking into whats the best but if anyone has any suggestions for my previous post I'ld greatly appreciate it
I suggest avoid 'hlte' and always choose 'hltetmo'. 'hlte' might be the international version and with some things, like custom Recovery, it will cause boot-loops on the SM-N900T. When you see something contradicting what I just wrote assume it to be true for only that thing.
Frank
I recently got my Harman Kardon edition M8. One thing which disappointed me is the battery life. And I've tried a couple of ROMs. Both gave me around or less than 5hrs SOT. But that isn't enough for me, especially after seeing people get over 7.5 hrs..
Also, I see that Sprint version has very low dev support. So my question is, can I use international ROMs with my Sprint phone? My phone is unlocked, S-OFF and I use 3G only. No 4G.
Thanks.
I would suggest only to run ROMs that specifically stated to support your Sprint (CDMA) variant.
redpoint73 said:
I would suggest only to run ROMs that specifically stated to support your Sprint (CDMA) variant.
Click to expand...
Click to collapse
I know that's the better option. But, I saw a post on a thread where he installed the international version and he did some tweaks and everything was working fine for him.
My question, anyways I'm using it as a GSM phone only. So wouldn't it work fine?
Thanks for the reply.
edios123 said:
I know that's the better option. But, I saw a post on a thread where he installed the international version and he did some tweaks and everything was working fine for him.
My question, anyways I'm using it as a GSM phone only. So wouldn't it work fine?
Click to expand...
Click to collapse
Not necessarily. It has nothing to do with how you use your phone. It has to do with the fact that the Sprint & Verizon CDMA variants actually are different in hardware. Therefore, there is some difference in the ROMs. And no guarantee that permanent damage may even occur from flashing mods meant for the GSM version. In fact, some CDMA users bricked their phones flashing earlier TWRP builds meant for the GSM variant. This has since been fixed within TWRP. But just a worst case example.
If a ROM has been verified to work by someone else to work on Sprint, than its probably ok. But if there isn't prior verification, you are taking a chance; and should be prepared to live with the consequences, whatever they may be.
redpoint73 said:
Not necessarily. It has nothing to do with how you use your phone. It has to do with the fact that the Sprint & Verizon CDMA variants actually are different in hardware. Therefore, there is some difference in the ROMs. And no guarantee that permanent damage may even occur from flashing mods meant for the GSM version. In fact, some CDMA users bricked their phones flashing earlier TWRP builds meant for the GSM variant. This has since been fixed within TWRP. But just a worst case example.
If a ROM has been verified to work by someone else to work on Sprint, than its probably ok. But if there isn't prior verification, you are taking a chance; and should be prepared to live with the consequences, whatever they may be.
Click to expand...
Click to collapse
Thanks for the info. I never knew that a software could damage hardware permanently. Can you please give an example of what would go wrong?
Sent from my 831C using XDA Free mobile app
edios123 said:
Thanks for the info. I never knew that a software could damage hardware permanently. Can you please give an example of what would go wrong?
Click to expand...
Click to collapse
I believe partitioning on the phones is different. If you install software that over-writes hboot or radio partitions, or the partition tables, you phone is going to brick. There might be other ways in which software can brick a device. But this is the example I know about.
The above happened to some folks that tried to install TWRP (older builds) meant for the GSM version, onto the VZN/Sprint versions. TWRP has since been updated to prevent this. But its one example of how software can brick the device.
There are also countless other examples on other devices, where folks tried to install a ROM or other mod meant for another hardware, and bricked their devices.
redpoint73 said:
I believe partitioning on the phones is different. If you install software that over-writes hboot or radio partitions, or the partition tables, you phone is going to brick. There might be other ways in which software can brick a device. But this is the example I know about.
The above happened to some folks that tried to install TWRP (older builds) meant for the GSM version, onto the VZN/Sprint versions. TWRP has since been updated to prevent this. But its one example of how software can brick the device.
There are also countless other examples on other devices, where folks tried to install a ROM or other mod meant for another hardware, and bricked their devices.
Click to expand...
Click to collapse
Is there no way to bring a device back after bricking it?
Thanks!
Sent from my 831C using XDA Free mobile app
edios123 said:
Is there no way to bring a device back after bricking it?
Thanks!
Click to expand...
Click to collapse
Not without opening the phone and JTAG; or replacing the motherboard.
A true brick (and that is the only time I use the word "brick" here) is something you do not want to risk, trust me.
redpoint73 said:
Not without opening the phone and JTAG; or replacing the motherboard.
A true brick (and that is the only time I use the word "brick" here) is something you do not want to risk, trust me.
Click to expand...
Click to collapse
Oh okay. Thanks a lot for the info.
I'll +1 tomorrow since my thanks is limited to 8 per day.
Flashing a GSM rom to CDMA rom is possible but useless imo. Phone antenna will not work (calls, message etc) and you will most likely get stuck in a boot loop. Hard bricking it is also possible. 100% not recommended
redpoint73 said:
Not without opening the phone and JTAG; or replacing the motherboard.
A true brick (and that is the only time I use the word "brick" here) is something you do not want to risk, trust me.
Click to expand...
Click to collapse
TempestZ said:
Flashing a GSM rom to CDMA rom is possible but useless imo. Phone antenna will not work (calls, message etc) and you will most likely get stuck in a boot loop. Hard bricking it is also possible. 100% not recommended
Click to expand...
Click to collapse
Well, I took the risk and flashed Sky Dragon v6 yesterday.
Fun fact is that the Sprint version did NOT work while the GSM version worked/works flawlessly!
I'm kind of confused.
Sent from my One M8
edios123 said:
Well, I took the risk and flashed Sky Dragon v6 yesterday.
Fun fact is that the Sprint version did NOT work while the GSM version worked/works flawlessly!
I'm kind of confused.
Click to expand...
Click to collapse
What kernels in AROMA did you choose for each installation? This probably matter more than the AROMA carrier selection. In the kernel selection, it clearly states that Skydragon kernel is needed for CDMA devices, and standard kernel is for GSM only.
My guess is that you picked Sprint as the carrier, than incorrectly picked the Skydragon kernel = DOESN'T WORK
Then you picked the GSM generic install with the Skydragon custom kernel = WORKS
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??
I believe that anyone that bought a US unlocked phone directly from HTC was/is able to use it with Verizon out of the box, correct?
If so, why do I need/want to flash the Verizon radio to get a working phone after converting to the US unlocked version from the Verizon version I purchased?
I assume "normal" people that bought the unlocked phone are not flashing the Verizon radio.
Posted from my phone, forgive any spelling errors.
GSM vs CDMA?
JustinChase said:
I believe that anyone that bought a US unlocked phone directly from HTC was/is able to use it with Verizon out of the box, correct?
If so, why do I need/want to flash the Verizon radio to get a working phone after converting to the US unlocked version from the Verizon version I purchased?
I assume "normal" people that bought the unlocked phone are not flashing the Verizon radio.
Posted from my phone, forgive any spelling errors.
Click to expand...
Click to collapse
The unlocked HTC 10 doesn't support Verizon, it never has.
In order to use it on Verizon, people have always flashed the Verizon radio or firmware (which includes the radio). I don't know why HTC did it like this, but that's the way it is.
Sources:
HTC site saying what carriers the dev/unlocked HTC 10 supports.
Verizon is not listed.
The (possibly original) thread on the topic.
tl;dr for us lazy folk: No, it's ALWAYS been like that. The dev/unlocked HTC 10 has never supported Verizon and has never worked properly with Verizon out of the box.
Ariac Konrel said:
The unlocked HTC 10 doesn't support Verizon, it never has.
In order to use it on Verizon, people have always flashed the Verizon radio or firmware (which includes the radio). I don't know why HTC did it like this, but that's the way it is.
Sources:
HTC site saying what carriers the dev/unlocked HTC 10 supports.
Verizon is not listed.
The (possibly original) thread on the topic.
tl;dr for us lazy folk: No, it's ALWAYS been like that. The dev/unlocked HTC 10 has never supported Verizon and has never worked properly with Verizon out of the box.
Click to expand...
Click to collapse
Ah, that's why. Weird they did it that way, but at least I understand now. Thanks.
Hoping for nougat VZW firmware soon [emoji39]
Posted from my phone, forgive any spelling errors.
JustinChase said:
Ah, that's why. Weird they did it that way, but at least I understand now. Thanks.
Hoping for nougat VZW firmware soon [emoji39]
Posted from my phone, forgive any spelling errors.
Click to expand...
Click to collapse
Ehhh, same to me.
If you don't need WiFi calling, VoLTE or whatever go for any of the custom ROMs if you are into that.
I recommend Viper10.
Thanks. I'm currently running leedroid, but will try viper10. I've read he has advanced calling working already. Either way, I'll check it out.
Posted from my phone, forgive any spelling errors.
JustinChase said:
Thanks. I'm currently running leedroid, but will try viper10. I've read he has advanced calling working already. Either way, I'll check it out.
Posted from my phone, forgive any spelling errors.
Click to expand...
Click to collapse
He does and I can see it.
The video option is grayed out, but it is also not on my plan so that might not be the ROMs fault.
HD voice is operational.