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.
Related
Hello!
Quick question: I'm in Britain and have an unlocked s-off M8. What would happen if I flashed a Verizon/Sprint One (for example) M8 rom on my phone? Would it simply not make calls? Would it brick the phone? I'm intrigued to know.
Cheers.
Em
Might be risky. I don't know if anyone here has tried.
The hardware may even be different (for Sprint and Verizon CDMA variants vs. GSM versions). Some claim yes, others say no. And I haven't seen definitive evidence either way, so that part is not clear either.
I think a couple folks here bricked mixing the variants when flashing TWRP recovery (GSM recovery on a CDMA variant)? But from what I understand that is something that was fixed in TWRP.
I wouldn't risk it, unless you have a compelling reason to do so. May I ask why? I figured there was more development on the GSM version, anyway. Or just asking academically?
redpoint73 said:
Might be risky. I don't know if anyone here has tried.
The hardware may even be different (for Sprint and Verizon CDMA variants vs. GSM versions). Some claim yes, others say no. And I haven't seen definitive evidence either way, so that part is not clear either.
I think a couple folks here bricked mixing the variants when flashing TWRP recovery (GSM recovery on a CDMA variant)? But from what I understand that is something that was fixed in TWRP.
I wouldn't risk it, unless you have a compelling reason to do so. May I ask why? I figured there was more development on the GSM version, anyway. Or just asking academically?
Click to expand...
Click to collapse
Thanks for the fullness of your reply. Much appreciated.
As for your question: I've been wondering since got my M8. I've mainly had a Nexus 5 for the past few months and there's never been alternate versions. I noticed that there's a CM12 ROM flying around, and I'm a flash addict, so the hypothetical became slightly more actual.
Although if there's a chance of a brick, then it can stay in the land of hypotheticals
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 XDA.
I am new here and it's my first post, so I hope you can bear with me and any information that I am not be knowledgeable of.
I have an HTC M8 International Varient which supports Bands 3,7,8 and 20 for LTE. Unfortunately, my carrier is supporting Band 1 as far as I know.
I have been searching the internet for a couple of days already and I need a bit of help.
I have done the following:
-Installed TWRP
-Rooted Device
-Able to get Device in DIAG Mode through ADB (Not DM Command Service Screen. I cannot get the Modem Screen in anyway)
-QPST and QXDM/DFS CDMA were able to detect the device
-They were able to read the NV Values
At that point things should work, well...they are not. My problem is I cannot write the new band values to the NV. I read the values, edit them, write them, read them again and they are reverted back to what they were previously.
I have searched the internet a little, some people said you need S-OFF, while others said I need a custom ROM and a custom Kernel to disable the Anti Tamper Mechanism, which at this point I have no clues yet.
If I need S-OFF, I need to use Sunshine which is paid. And honestly, I am not interested to pay that much just to get LTE. I heard about Moonshine. Has any one used it?
Can anyone experienced shed some light on this matter please?
Thank you
well you can't change the values on the international m8 as it GSM
this process can only done on Verizon m8
as i read it before some people report that it doesn't work with sprint and all the GSM devices ( m8 )
Sent from my HTC M8 using XDA Labs
Above post is correct. Changing NV values won't stick on your M8 version. S-off won't change that, from what I've seen.
Another method which may work, would be to get s-off, and flash another versions radio/firmware (that supports the desire LTE band). May also need to change CID, MID depending on the radio/firmware flashed.
However its not guaranteed that you will even have LTE service after that. We've seen lots of such cases: radio firmware changed, but LTE still not working.
So the money spent on s-off may be wasted, so its not particularly recommended to try it (since you're obviously hesitant to spend the money, anyway).
Yamadron said:
If I need S-OFF, I need to use Sunshine which is paid. And honestly, I am not interested to pay that much just to get LTE. I heard about Moonshine. Has any one used it?
Click to expand...
Click to collapse
Moonshine is really old, and won't work on this device. Same with firewater, if you stumble on that. No point in trying either of those.
Sunshine is really your only option, and you have to pay for it.
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.
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?