Why flashing a different radio is not chaning my LTE bands? - HTC 10 Questions & Answers

Guys, I want some opinions on this matter I'm trying to fix.
I bought an Taiwan HTC 10 (M10H) which comes with several LTE bands (not the ones I need).
I'm trying to make this Asian version to work fully as an US unlocked version to get those different bands.
You may have read my posts on this topic on other threads.
But in short, since the unlocked version is the right version for my LTE needs, I unlocked the bootloader and S-OFF the phone to flash RUUs. That went smoothly, and my phone was converted to US-Unlocked (and T-Mobile branded later).
All in hopes of having the very same possibilities, LTE speaking at least (AWS Band is my objective).
But for some reason I'm failing to understand, the LTE bands are locked and not changing after flashing this RUU or the T-Mobile one. I have absolutely the same bands no matter what.
I have also flashed several radios from different versions, but nothing changes.
Failing with the RUUs and Radios, I resorted to changing the LTE Bands with Qualcomm Tools (QPST/QXDM). That failed as well, and it will until we grab a custom -made from scratch- kernel. That remains an open possibility when CM13 is functional.
But I'm still clueless with the failure of flashing RUUs to achieve my needs. If the phone is the same -hardware wise-, why flasing the RUU is not achieving the expected results? (or what is not modifying to prevent my phone to act like an US Unlocked?). I'm not sure what I missing. A hidden partition that remains untouched?
Is there a setting based on my Serial Number? (in my case FA65HBN02308). Because that's pretty much the only value that remains the same after flashing RUUs. Also my phone is still being recognized by windows as an M10H (sometimes just HTC 10). Or maybe this is related with the RIL?
Anyways, you're invited to help

Hello, I guess I'm in a similar situation, I've an HTC 10 bought online which is Unlocked from europe, I'm in México, but it's supposed that LTE works here (Band 4, 1700 MHz) and is supported by the HTC 10. But I can only get 3g and an H symbol. I already went to Telcel (my carrier) to check if it had to do with the chip or apn or something, but no it's the phone.
I unlocked my bootloader, left it S-ON, flashed twrp and super su (following this guide: http://forum.xda-developers.com/htc-10/how-to/guide-root-optionally-s-off-radio-t3373025) and then installed Elemental-X Kernel. I'm on 1.80.401.1

Radio bands are hardware dependent the last I checked. Flashing software wont change the actual radio compatibility. By changing the region, you'll force your phone to get updates with that line, but that's about it.
As for Telcel compatibility, I'm pretty sure that requires AWS LTE. LTE bands need both an uplink and a downlink. Just having one of the two bands (1700) wont make you AWS LTE compatible. You need full AWS B4 (1700/2100).

geotsai said:
Radio bands are hardware dependent the last I checked. Flashing software wont change the actual radio compatibility. By changing the region, you'll force your phone to get updates with that line, but that's about it.
As for Telcel compatibility, I'm pretty sure that requires AWS LTE. LTE bands need both an uplink and a downlink. Just having one of the two bands (1700) wont make you AWS LTE compatible. You need full AWS B4 (1700/2100).
Click to expand...
Click to collapse
According to this site, the phone is fully compatible with the lte band, and is the same model sold internationally. As I mentioned, I unlocked bootloader, flashed recovery, kernel, root (Super Su beta 2.74 I think) could that have disabled the lte?
https://www.frequencycheck.com/carrier-compatibility/pAJDFX/htc-10-lte-a-na-32gb-htc-perfume/telcel-mexico

geotsai said:
Radio bands are hardware dependent the last I checked. Flashing software wont change the actual radio compatibility. By changing the region, you'll force your phone to get updates with that line, but that's about it.
As for Telcel compatibility, I'm pretty sure that requires AWS LTE. LTE bands need both an uplink and a downlink. Just having one of the two bands (1700) wont make you AWS LTE compatible. You need full AWS B4 (1700/2100).
Click to expand...
Click to collapse
Are hardware dependant but this modem supports all LTE bands. Every region just enables and disables needed bands. Of course software can't solve this if your hardware does not support the bands. But the Snapdragon 820 support all the bands. Aside from the display, the rest of the hardware is the very same for every variant (being China the only exception).
Which bands are enabled depends on a set of instructions on Qualcomm NV values.
You can verify this with DFS tools or QXDM from Qualcomm (you need root and Diag Mode also).
The problem so far is that the Qualcomm kernels have an anti-tampering function (source: couple of guides), preventing modifications for GSM. I have already succeded in changing the values for CDMA, and there is another user that has reported the changes to be working on CDMA. But I was unable to do it for GSM. So we have to wait until CM13 works to try this option with a built from scratch kernel.
That still doesn't answer us why I couldn't achieve it. But for eg. mnguyen127 said it worked for him. So confusion continues...(at least for me).

kainanmaki said:
Are hardware dependant but this modem supports all LTE bands. Every region just enables and disables needed bands. Of course software can't solve this if your hardware does not support the bands. But the Snapdragon 820 support all the bands. Aside from the display, the rest of the hardware is the very same for every variant (being China the only exception).
Which bands are enabled depends on a set of instructions on Qualcomm NV values.
You can verify this with DFS tools or QXDM from Qualcomm (you need root and Diag Mode also).
The problem so far is that the Qualcomm kernels have an anti-tampering function (source: couple of guides), preventing modifications for GSM. I have already succeded in changing the values for CDMA, and there is another user that has reported the changes to be working on CDMA. But I was unable to do it for GSM. So we have to wait until CM13 works to try this option with a built from scratch kernel.
That still doesn't answer us why I couldn't achieve it. But for eg. mnguyen127 said it worked for him. So confusion continues...(at least for me).
Click to expand...
Click to collapse
Yeah, I still get Band 4 consistently albeit only in certain areas, which is interesting. The HTC 10 seems to have some interesting default band priorities, so it'll always choose Band 12 over band 4 unless band 12 is unavailable. If I more a mile out of my city to the next city over, all I get is band 4. If I stay in my city, all I get is band 12. I did some experimenting and when I used my LG G3, the phone prioritized band 4. I'm not actually sure if the LG G3 is able to connect to band 12; I just know that it default connects to band 4 in areas where my HTC 10 Taiwan based one won't. Also confirmed with another forum member that his US unlocked phone bought from HTC would default prioritize other lte bands over band 4.
The only methods I used were these: (order might not be perfect)
Fastboot commands
S-OFF
Root
TWRP
Changed MID/CID from Taiwan to US Unlocked
Flashing from 1.3 taiwan to 1.5 U.S Unlocked by using ROM (I think), which caused me to lose root but allowed me to updated to 1.80.617.1 by OTA. Afterwards, I rerooted and installed TWRP (probably some unnecessary extra step but I had to since I realized my radio firmware was out of date with my ROM) and flashed the 1.8 US radios, which updated my radio firmware. I used fastboot to flash the radio firmware, but I didn't do it through download mode. I think I did it through bootloader. I then manually flashed 1.80 firmware which caused me to lose root and TWRP but allowed me to keep my updated radio firmware, my new US unlocked CID/MID, and allows me to receive update directly from HTC on my Taiwan based phone.
I get band 12 and 4 consistently.
Sorry if I couldn't be more helpful

Related

Updating att branded phone t-mobile

I have an s-offed att branded phone on t-mobile. It's running an old ruu t-mobile. I just downloaded an update to lollipop. I can just run the update?
Possibly...
you need to check a few things... what's your phone's cid set to? (you can see this in your boot loader screen).
As a general rule, I've found that if I run t-mobile radio's I have more problems than if I run either a native AT&T or the DEV edition radio and then t-mobile firmware on-top of that radio... my phone doesn't seem to do some of the hspa bands from t-mobile...
check your cid, before you do much of anything else...
If he's running a tmo ruu, i would assume he's running super cid.
I would also have to assume that he's changed the mid to tmo?
scifan, have you considered using DFS to set your bands?
avg2424 said:
.
changed the mid to tmo?
DFS to set your bands?
Click to expand...
Click to collapse
What is the mid and DFS?
I have a Verizon branded m8 and am using a t-mobile mvno
(straight talk) SIM. I am considering changing RoMs from viper one to one off if the t-mobile thread in order to solve this problem of random service disconnections. Should I switch to a different Ruu? Should I have changed the RUU when I was on stock?
I apologize if the this should be on another or is own thread.
Thanks so much!
kyedmipy said:
What is the mid and DFS?
I have a Verizon branded m8 and am using a t-mobile mvno
(straight talk) SIM. I am considering changing RoMs from viper one to one off if the t-mobile thread in order to solve this problem of random service disconnections. Should I switch to a different Ruu? Should I have changed the RUU when I was on stock?
I apologize if the this should be on another or is own thread.
Click to expand...
Click to collapse
DO NOT, repeat DO NOT try to "convert" your Verizon M8 to T-Mob (with T-Mob RUU). The partitioning (possibly hardware) is different. The T-Mob RUU won't work, and may result in a permanent radio brick.
I'm not sure what is causing the service disconnects. Does the issue occur if you only use 2G and 3G? You may consider looking at enabling the proper LTE bands used by T-Mobile. From what I see, the Verizon M8 supports the proper bands that T-Mob uses for 2G and 3G. However, the VZN version only supports one of the two LTE bands (Band 4) used by T-Mob (Bands 4 and 17). Enabling LTE band 17 may or may not help. The missing support for LTE Band 17 may be related to your disconnect issues, but that's just a theory.
The hitch here, is that trying to enable LTE Band 17 requires s-off, which costs $25 by sunshine app (if you are not already s-off). And its not a sure solution, so may be money wasted.
You can take a look at the following threads, on how to enable bands on the Verizon M8. But I don't personally vouch for these:
http://forum.xda-developers.com/htc-one-m8/general/how-to-convert-cdma-m8-sprint-vzw-gsm-t3303812
http://forum.xda-developers.com/htc-one-m8/general/unlock-bands-qualcomm-device-phone-t2880239
Awesome thanks. I paid the 25 dollars for s-off already to root the phone. Sunshine works like a charm.
I'll check out the links you provided. I have a feeling your theory is correct. You described how I felt the problem was but lacked the knowledge to produce words to describe. Thanks again.
I don't know whether this is the right thread to ask this question but if you do know kindly advise me; i recently bought a T-mobile M8 which was imported from USA and had sim unlocked but i don't know other details except that its not rooted (that i checked with supersu). May be it was imported as scrap since it's an old model and may be it was unlocked from t-mobile, i just have no idea. Now the phone is asking me for a few updates which describe to tell me that these are intended to prepare phone for marshmallow update (currently it's on jellybean). Should i allow update to progress or not? i don't want to loose sim unlock.
I recently bought a T-mobile M8 which was imported from USA and had sim unlocked but i don't know other details except that its not rooted (that i checked with supersu). May be it was imported as scrap since it's an old model and may be it was unlocked from t-mobile, i just have no idea. Now the phone is asking me for a few updates which describe to tell me that these are intended to prepare phone for marshmallow update (currently it's on jellybean). Should i allow update to progress or not? i don't want to loose sim unlock.

Replace 1.80.709.1 with 1.80.617.1 (LTE Band Problem)

I received yesterday a taiwanese HTC 10 and it is standing right now at version 1.80.709.1
My problem is that where I live (Uruguay) I need LTE Band 4 (1700-2100) which this version doesn't support.
My question is, if I unlock the bootloader, apply SuperCID (need to change the MID?) and use Sunshine, could I flash the 1.80.617.1 US Unlocked version (or a prior version with radio) in order to be able to use LTE Band 4?
Should I flash an older RUU first and then 1.80.617.1?
Thanks all.
I have band 4 currently on the HTC 10 (taiwan) phone, but what I've noticed is that currently on the 10, this phone seems to prioritize band 12 over band 4. Currently, my phone is on the newest US developer unlocked rom/firmware, s-off, unlocked, with the most recent US radio, using a changed cid/mid US__002, and I still only receive band 4 in certain places (work, for example, I seem to get band 4).
At home, I receive band 12 on my HTC 10, but if I switch my SIM to my LG G3, i'll receive excellent band 4 connection, so at this point, I think the best we can hope for is that someone figures out how to unlock LTE bands on different versions of the phone.
What I'm wondering is if this prioritization only affects our phone, or if it affects even US unlocked phones.
I'm using an Unlocked US phone on the latest firmware and it definitely prioritizes band 12. On my Moto MAXX which didn't have band 12, it would use Band 17 just fine in a lot of places. On the 10 it quickly goes to 12. I've seen it connect to 17, but then pretty rapidly change over to 12. I'm using Straight Talk AT&T.
duowing said:
I'm using an Unlocked US phone on the latest firmware and it definitely prioritizes band 12. On my Moto MAXX which didn't have band 12, it would use Band 17 just fine in a lot of places. On the 10 it quickly goes to 12. I've seen it connect to 17, but then pretty rapidly change over to 12. I'm using Straight Talk AT&T.
Click to expand...
Click to collapse
Out of curiosity, is that a US purchased phone, or is one of the global phones like the Chrome/white/silver variant? I'm curious if this affects all phones or if this just mostly affects the global variants of the HTC 10 (the ones that came with headphones).
Thanks.
mnguyen127 said:
I have band 4 currently on the HTC 10 (taiwan) phone, but what I've noticed is that currently on the 10, this phone seems to prioritize band 12 over band 4. Currently, my phone is on the newest US developer unlocked rom/firmware, s-off, unlocked, with the most recent US radio, using a changed cid/mid US__002, and I still only receive band 4 in certain places (work, for example, I seem to get band 4).
At home, I receive band 12 on my HTC 10, but if I switch my SIM to my LG G3, i'll receive excellent band 4 connection, so at this point, I think the best we can hope for is that someone figures out how to unlock LTE bands on different versions of the phone.
What I'm wondering is if this prioritization only affects our phone, or if it affects even US unlocked phones.
Click to expand...
Click to collapse
Mmm interesting.
So you changed to CID: BS_US002 | MID: 2PS650000 and flashed with TWRP Backup to 1.80.617.1?
kainanmaki said:
Mmm interesting.
So you changed to CID: BS_US002 | MID: 2PS650000 and flashed with TWRP Backup to 1.80.617.1?
Click to expand...
Click to collapse
I went through quite a long process since I wanted my Taiwan based HTC Silver/White phone to run stock US Developer Unlocked and receive OTAs exactly when they were released without having to manually flash through recovery.
To do that, I had to unlock my bootloader, flash TWRP, root my phone, s-off through sunshine, then change my mid/cid to the correct ones you listed (BS_US002 & 2PS650000). When I did this, the most recent update was 1.5 and I went from 1.3 to 1.5 using the stock US Developer Unlocked RUU exe through windows. Once I accomplished that, my system was stock on US Developer Unlocked ROM/Firmware aside from s-off and unlocked bootloader (I lost TWRP & Root).
With the release of 1.8, someone posted the radio IMG files, and for me to flash those on my stock ROM, I had to reinstall TWRP and Root. To flash the radio files, I had to do it through the bootloader (instead of download mode... I don't remember the exact command. It was something like fastboot flash radio "insert radio file").
Once I updated my radio, I wanted to return back to stock ROM so I could receive OTAs, and to do this, I had to flash the 1.8 firmware which removed TWRP and Root, but it kept my updated radio, my updated CID/MID, and kept me on the US Developer unlocked firmware/rom I wanted so that I could still receive the most recent updates through OTA instead of having to manually flash them.
Yeah. Long process, I know, but the end result is essentially what I wanted, which is a US Unlocked White/Silver HTC 10 that could receive the OTAs directly from HTC.
Right now, I am getting band 4 (which is originally missing from the UK/Taiwan/Euro HTC 10s) but it seems like this phone in general seems to want to prioritize band 12 over all other bands. It'll only switch to band 4 if band 12 is non-existent. Interestingly, if I tweak with radio settings, I can force my phone to operate under HSPA+ which has a much higher download/upload speed than band 12 but not nearly as high as band 4.
Band 12 gets me around 7mbps download speed, band 4 gets me like 21-22 mbps download speed, and HSPA+ gets me around 15-17 mbps download speed.
duowing said:
I'm using an Unlocked US phone on the latest firmware and it definitely prioritizes band 12. On my Moto MAXX which didn't have band 12, it would use Band 17 just fine in a lot of places. On the 10 it quickly goes to 12. I've seen it connect to 17, but then pretty rapidly change over to 12. I'm using Straight Talk AT&T.
Click to expand...
Click to collapse
Off topic, sorry, but may I ask how do you know which band your connecting to? Thanks.
omar302 said:
Off topic, sorry, but may I ask how do you know which band your connecting to? Thanks.
Click to expand...
Click to collapse
There's a few apps for it.
LTE Discovery is what I was using.
Thanks. But for some reason it gives me "Unknown" LTE Band.
omar302 said:
Thanks. But for some reason it gives me "Unknown" LTE Band.
Click to expand...
Click to collapse
It does that for me too if I have my phone set only to connect to GSM or something. You might want to look at the settings under mobile date and check what your preferred network is.
I have it on 2G/3G/4G auto, and I double checkedit was connectedto a LTE network & still got unknown. Maybe it is becauseof our operator. Thanks anyway.
mnguyen127 said:
I went through quite a long process since I wanted my Taiwan based HTC Silver/White phone to run stock US Developer Unlocked and receive OTAs exactly when they were released without having to manually flash through recovery.
To do that, I had to unlock my bootloader, flash TWRP, root my phone, s-off through sunshine, then change my mid/cid to the correct ones you listed (BS_US002 & 2PS650000). When I did this, the most recent update was 1.5 and I went from 1.3 to 1.5 using the stock US Developer Unlocked RUU exe through windows. Once I accomplished that, my system was stock on US Developer Unlocked ROM/Firmware aside from s-off and unlocked bootloader (I lost TWRP & Root).
With the release of 1.8, someone posted the radio IMG files, and for me to flash those on my stock ROM, I had to reinstall TWRP and Root. To flash the radio files, I had to do it through the bootloader (instead of download mode... I don't remember the exact command. It was something like fastboot flash radio "insert radio file").
Once I updated my radio, I wanted to return back to stock ROM so I could receive OTAs, and to do this, I had to flash the 1.8 firmware which removed TWRP and Root, but it kept my updated radio, my updated CID/MID, and kept me on the US Developer unlocked firmware/rom I wanted so that I could still receive the most recent updates through OTA instead of having to manually flash them.
Yeah. Long process, I know, but the end result is essentially what I wanted, which is a US Unlocked White/Silver HTC 10 that could receive the OTAs directly from HTC.
Right now, I am getting band 4 (which is originally missing from the UK/Taiwan/Euro HTC 10s) but it seems like this phone in general seems to want to prioritize band 12 over all other bands. It'll only switch to band 4 if band 12 is non-existent. Interestingly, if I tweak with radio settings, I can force my phone to operate under HSPA+ which has a much higher download/upload speed than band 12 but not nearly as high as band 4.
Band 12 gets me around 7mbps download speed, band 4 gets me like 21-22 mbps download speed, and HSPA+ gets me around 15-17 mbps download speed.
Click to expand...
Click to collapse
Thanks, this will help a lot. So you can flash a Radio from 1.8 while being on 1.5? Good to know.
I´ll comment my results when everything is ready.
mnguyen127 said:
I have band 4 currently on the HTC 10 (taiwan) phone, but what I've noticed is that currently on the 10, this phone seems to prioritize band 12 over band 4.. At home, I receive band 12 on my HTC 10, but if I switch my SIM to my LG G3, i'll receive excellent band 4 connection...
Click to expand...
Click to collapse
What software may tell me which particular LTE band my hTc 10 is connected to the 4G network through? As we all know LTE discovery may not..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
kainanmaki said:
Should I flash an older RUU first and then 1.80.617.1?
Thanks all.
Click to expand...
Click to collapse
After gaining S-OFF and changing CID and MID to your new desired region, you better use 1.80.617.1 RUU - after installing it, do hard reset through the stock recovery - just in case..
https://tapatalk.com/shareLink?url=...share_tid=3378540&share_fid=3793&share_type=t
Sent from quite brutal hTc 10 ..
jauhien said:
What software may tell me which particular LTE band my hTc 10 is connected to the 4G network through? As we all know LTE discovery may not..
After gaining S-OFF and changing CID and MID to your new desired region, you should use that older 1.53.617.5 RUU - and then you'll straightway receive the next OTA (when S-OFF and unlocked bootloader won't be any problem for getting OTA).. Again the successfully installed OTA will confirm that there was no mistake done and all is OK. After installing the OTA, do hard reset through the stock recovery - just in case..
Sent from quite brutal hTc 10 ..
Click to expand...
Click to collapse
In fact, I'm planning to SuperCID, and since I'm going to use ViperRom OTA is going to become useless for me. But you´re right that I might first use the correct CID and MID, flash the old RUU, use the OTA update to reach 1.8 and then change to SuperCID.
kainanmaki said:
Thanks, this will help a lot. So you can flash a Radio from 1.8 while being on 1.5? Good to know.
I´ll comment my results when everything is ready.
Click to expand...
Click to collapse
Sorry, that might've been confusing. I made sure to update my radio with the same update I was using, so if I was on 1.8 update, I'd update my old radio with 1.8 radio if that makes sense. However, you probably can update your radio regardless because I noticed that when I updated to 1.8, I was on an outdated radio version before I updated it to the most recent version.
Just to be safe though, I'd match your rom number with the radio it's supposed to come with.
Here's a link with some radios
http://forum.xda-developers.com/htc-10/how-to/radio-htc10-radio-collection-t3398233#post67308774
mnguyen127 said:
Sorry, that might've been confusing. I made sure to update my radio with the same update I was using, so if I was on 1.8 update, I'd update my old radio with 1.8 radio if that makes sense.
Click to expand...
Click to collapse
Perfect, I took me a lot of time to use the unlock from htc.dev (bad token error in fastboot) but now I'm off to TWRP. Thanks again for your help!!
Sorry for slow response, but my 10 is purchased in US through HTC and I was using LTE Discovery to check bands
Time for a recap:
I successfully unlocked bootloader, twrp, root and s-off with sunshine.
Changed CID to BS_US001 and MID to 2PS650000.
Successfully downgraded to 1.53.617.5 with RUU (exe) and applied OTA update to 1.80.617.1.
On 1.53 had the [email protected]_45.00_F Radio and LTE 4 AWS didn't work.
On 1.80 had the [email protected]_51.01_F Radio and LTE 4 AWS didn't work.
Flashed TWRP again and went to ViperROM
Didn't have to flash the radio individually, the RUU did that fo me (and then the OTA update).
Maybe the bands won't activate if you don't flash the radio manually.
But ATM, still no LTE AWS Band 4...which is worrying
I tried to force LTE selection using the *#*#4636#*#* code and it clearly demonstrated that the LTE band is not present even with the correct radio.
So what's next?
I'm going to try the DFS change with QXDM Pro to see if I can activate the band manually (being Qualcomm).
Seems like the last chance to have LTE.
kainanmaki said:
Time for a recap:
I successfully unlocked bootloader, twrp, root and s-off with sunshine.
Changed CID to BS_US001 and MID to 2PS650000.
Successfully downgraded to 1.53.617.5 with RUU (exe) and applied OTA update to 1.80.617.1.
On 1.53 had the [email protected]_45.00_F Radio and LTE 4 AWS didn't work.
On 1.80 had the [email protected]_51.01_F Radio and LTE 4 AWS didn't work.
Flashed TWRP again and went to ViperROM
Didn't have to flash the radio individually, the RUU did that fo me (and then the OTA update).
Maybe the bands won't activate if you don't flash the radio manually.
But ATM, still no LTE AWS Band 4...which is worrying
I tried to force LTE selection using the *#*#4636#*#* code and it clearly demonstrated that the LTE band is not present even with the correct radio.
So what's next?
I'm going to try the DFS change with QXDM Pro to see if I can activate the band manually (being Qualcomm).
Seems like the last chance to have LTE.
Click to expand...
Click to collapse
Yeah, sounds like you're essentially where I'm at with my phone. I do get band 4 LTE, but the phone seems to only connect to it when no other bands exist. I've been researching methods to unlock the bands, but there isn't anything out there that's guaranteed yet, so I'm waiting for more developers to tinker a bit before I gamble bricking my phone. Sorry I couldn't help you more;
mnguyen127 said:
Yeah, sounds like you're essentially where I'm at with my phone. I do get band 4 LTE, but the phone seems to only connect to it when no other bands exist. I've been researching methods to unlock the bands, but there isn't anything out there that's guaranteed yet, so I'm waiting for more developers to tinker a bit before I gamble bricking my phone. Sorry I couldn't help you more;
Click to expand...
Click to collapse
You were of immense help. On the other hand, your path was bit different.
I went for the RUU and just took the OTA (checking that the radio was automatically flashed -it was-)
But you flashed the radios after changing the firmware, so I still have to try that one before heading to riskier places.
If I do end doing it the hard way with success, I'll tell you straight away since the QXDM tool can also determine which bands are enabled and disabled (and you could put away band 12). I just need band 4 because it's the only one for LTE for my carrier and it will only compete with HSPA+ bands.

SUCCESS:: LTE Band 17 (AT&T / MVNO) working on G930v

Hello, All.
I've successfully completed my quest in getting my Verizon Galaxy S7 to work with AT&T's primary LTE band; Band 17.
At first I was using the PE1 firmware with root. I first used Phone INFO (for Samsung) app to access the service code 2263. On PE1, only the factory Verizon-supplied bands were showing as supported. Band 12/17 were not showing in the service menu.
I took my chances and flashed the G930U firmware (found on the AT&T S7 forum of all things) and booted the phone with my AT&T SIM card. I ran LTE Discovery and achieved profit. Band 17 was working with the same signal as the iPhone 6S the SIM card came out of.
Also, the 930U firmware completely debrands the phone, which is perfect since I'll be using it on AT&T. After I confirmed band 17 I proceeded to root using the normal method of flashing the engboot and installing the root/SuperSU package per the root instructions. I did not use the Verizon PE1 debloater/fixes .zip files to make necessary tweaks, post root. I performed the tweaks manually (wifi fix, CPU governer: interactive, and SecurityLogAgent) .. Let me know if I'm missing anything in those regards please.
The ONLY thing I can't do now is view all the LTE bands in 2263 Service Mode. I get a "RAT Selection option: is restricted".. I want to see if all LTE bands are unlocked now. If you know of another way to see all the supported LTE bands, please let me know!
I now have exactly what I was set out to accomplish and it's great. The S7 is replacing my iPhone 6S on AT&T and I will be buying a Note 7 to replace the S7 on Verizon. If/when root is achieved on the Note 7 I will do the same and replace the Note 7 on Verizon with the iPhone 7 (I cycle my personal/business phones as a guilty pleasure if you can't tell already)
Screen shots attached
nice work, thanks for taking the plunge
Just did the same on a friend's S7 that he was trying to get on Cricket's LTE, as the VZW firmware kept him on HSPA+ at most. All I had to do was flash the AT&T firmware and bam, LTE. I forgot to check what band it was on but at least it's an additional proof of concept.
Thanks for the info!
Can u link that ROM
I haven't tried with Samsung, however, most phones with Qualcomm modems can be accessed via QXDM or similar PC software. Often the so called hacked HTC modem driver will allow QXDM to communicate with the phone.
There are XDA threads detailing how to access the appropriate LTE bands and selecting bands of choice using the above method.
AT&T and VzW both use bands 2 and 4, so you probably have all the bands that you need covered already.
xdadevnube said:
I haven't tried with Samsung, however, most phones with Qualcomm modems can be accessed via QXDM or similar PC software. Often the so called hacked HTC modem driver will allow QXDM to communicate with the phone.
There are XDA threads detailing how to access the appropriate LTE bands and selecting bands of choice using the above method.
AT&T and VzW both use bands 2 and 4, so you probably have all the bands that you need covered already.
Click to expand...
Click to collapse
The factory Verizon firmware did NOT have LTE band 12 or 17 unlocked so I was only getting HSPA+ with little spurts of band 2/4 LTE every once in a while with the AT&T SIM card in it. Flashing the 930U unlocked band 12/17 for me so I have full LTE coverage in the same spots where I only had HSPA+ before.
parin11 said:
Can u link that ROM
Click to expand...
Click to collapse
http://forum.xda-developers.com/att-galaxy-s7/how-to/xda-community-love-g930u-t3415875
One thing to note also is that the G930U firmware auto detects your carrier settings and has you restart after first boot. I'm assuming it will unlock correct bands depending on the carrier SIM you use. The G930U firmware does NOT, however, like the Verizon SIM. Upon updating carrier settings with a Verizon SIM installed, the device will reboot into recovery. Every time you power on the device it will prompt you to update the carrier settings and will have you reboot again.. back into recovery. Rinse and repeat. I had to refresh the U firmware to get my band 12/17 back after putting the Verizon SIM in.
MrBaltazar said:
One thing to note also is that the G930U firmware auto detects your carrier settings and has you restart after first boot. I'm assuming it will unlock correct bands depending on the carrier SIM you use. The G930U firmware does NOT, however, like the Verizon SIM. Upon updating carrier settings with a Verizon SIM installed, the device will reboot into recovery. Every time you power on the device it will prompt you to update the carrier settings and will have you reboot again.. back into recovery. Rinse and repeat. I had to refresh the U firmware to get my band 12/17 back after putting the Verizon SIM in.
Click to expand...
Click to collapse
That happened to me when I rooted on the ufirmware forced to reboot.
Sent from my SM-G930U using XDA-Developers mobile app
MrBaltazar said:
Hello, All.
I've successfully completed my quest in getting my Verizon Galaxy S7 to work with AT&T's primary LTE band; Band 17.
At first I was using the PE1 firmware with root. I first used Phone INFO (for Samsung) app to access the service code 2263. On PE1, only the factory Verizon-supplied bands were showing as supported. Band 12/17 were not showing in the service menu.
I took my chances and flashed the G930U firmware (found on the AT&T S7 forum of all things) and booted the phone with my AT&T SIM card. I ran LTE Discovery and achieved profit. Band 17 was working with the same signal as the iPhone 6S the SIM card came out of.
Also, the 930U firmware completely debrands the phone, which is perfect since I'll be using it on AT&T. After I confirmed band 17 I proceeded to root using the normal method of flashing the engboot and installing the root/SuperSU package per the root instructions. I did not use the Verizon PE1 debloater/fixes .zip files to make necessary tweaks, post root. I performed the tweaks manually (wifi fix, CPU governer: interactive, and SecurityLogAgent) .. Let me know if I'm missing anything in those regards please.
The ONLY thing I can't do now is view all the LTE bands in 2263 Service Mode. I get a "RAT Selection option: is restricted".. I want to see if all LTE bands are unlocked now. If you know of another way to see all the supported LTE bands, please let me know!
I now have exactly what I was set out to accomplish and it's great. The S7 is replacing my iPhone 6S on AT&T and I will be buying a Note 7 to replace the S7 on Verizon. If/when root is achieved on the Note 7 I will do the same and replace the Note 7 on Verizon with the iPhone 7 (I cycle my personal/business phones as a guilty pleasure if you can't tell already)
Screen shots attached
Click to expand...
Click to collapse
With flashing the 930u firmware being possible would it be possible to then get twrp recovery working? Debating on trying just because I have an extra s7
eg2_Justin said:
With flashing the 930u firmware being possible would it be possible to then get twrp recovery working? Debating on trying just because I have an extra s7
Click to expand...
Click to collapse
Unfortunately no. Bootloader is still locked and we cannot flash custom recoveries at this time.
MrBaltazar said:
Unfortunately no. Bootloader is still locked and we cannot flash custom recoveries at this time.
Click to expand...
Click to collapse
Ahh I figured that was the case
Currently on stock. I get LTE with a att sim card until i place a call then it reverts to 3G. Any known issues with this method? I would really enjoy having full LTE coverage if possible
XxCyberHackerxX said:
Currently on stock. I get LTE with a att sim card until i place a call then it reverts to 3G. Any known issues with this method? I would really enjoy having full LTE coverage if possible
Click to expand...
Click to collapse
Have this issue as well on VZW mvno.
Illogi.xbone said:
Have this issue as well on VZW mvno.
Click to expand...
Click to collapse
I'm hoping this method can eliminate that issue. I just need multiple people to confirm this works (too scared to try it without feedback)
XxCyberHackerxX said:
I'm hoping this method can eliminate that issue. I just need multiple people to confirm this works (too scared to try it without feedback)
Click to expand...
Click to collapse
The issue I have is with the U Firmware. However, the method does not trip knox. Make a Smartswitch backup and give it a go. If it still doesn't work flash back to AT&T stock and restore from your backup.
OP: if you haven't been able to allow the RAT selection i'd suggest this.
go to Service mode main menu (either broadcast cmd 27663368378 or app like shortcut master), 2. ue setting > 1. setting > 1. protocol > 5. sim > 4. EF_RAT Free Supporting > 1. EF rat free supporting on (select even if it shows on)> now RAT Free Support.
Then business as usual.
XxCyberHackerxX said:
Currently on stock. I get LTE with a att sim card until i place a call then it reverts to 3G. Any known issues with this method? I would really enjoy having full LTE coverage if possible
Click to expand...
Click to collapse
Your call is being transmitted over LTE so the data reverts back to Hspa during the call. Mine does this but returns to LTE after I hang up.
MrBaltazar said:
Your call is being transmitted over LTE so the data reverts back to Hspa during the call. Mine does this but returns to LTE after I hang up.
Click to expand...
Click to collapse
Thanks for the explanation. So at this point what is the point of this method? Does unlocking the band lead to a stronger signal?
XxCyberHackerxX said:
Thanks for the explanation. So at this point what is the point of this method? Does unlocking the band lead to a stronger signal?
Click to expand...
Click to collapse
You unlock the band that AT&T primarily uses for LTE. Much more LTE signal throughout the nation on band 17.

Frequency unlock

Hello guys, I have an HTC M8 and I would like to know if there is any method to unlock LTE Band 38(2600) because I've searched on Google and I've seen some methods for Sprint ones and AT-T, but I'm not sure if that method will work for me. My phone is not locked on any carrier, it's the international one. Maybe you guys could give me some links or something like that, thanks in advance.
The method to unlock the bands only applies to the M8 "CDMA" variants Sprint and Verizon (and I don't think it even works on Sprint). It doesn't apply to the AT&T version, but I think you may just be mixing up AT&T with Verizon.
Changing band support on the "GSM" versions (including the international) is typically done by another method: getting s-off ($25 by sunshine app) and flashing another version's radio firmware (may also need to change CID). But even then, when the radio with the proper band support is flashed, we've seen cases where the user still is not able to get LTE service on their M8. I haven't seen a good explanation, and no fix for this. So the money spent on sunshine may be wasted.
Further, I don't know of any carrier version that natively supports LTE band 38. So I don't even know if there is a radio version for you to flash, in the first place.
http://www.gsmarena.com/htc_one_(m8)-6074.php
A further caution, if you choose to go the s-off route, is that changes made under s-off can be dangerous and even result in permanent damage. So be sure you know what you are doing, before proceeding.

Flashing G930U to G930V

What are the steps to flash g930u on g930v?
I just purchased S7 from the ebay. Unfortunately it is a verizon version and I am not a fan to say at least. I am on ATT and also planning to travel, so I need many more LTE bands than G930V has. It is running G930VVZW4BRC3
- is it true that additional LTE bands can be enabled on any Qualcomm device? If not, at least I want to flash G930U onto G930V to get rid of crapware.
- I had downloaded the latest G930U firmware from the updato.com G930UUEU4BRD1. Is that the files to flash or are there various files around here on XDA, with fixes applied
- Do I just flash all the files from the zip via Odin?
is this guide still relevant? https://www.reddit.com/r/GalaxyS7/comments/5izd45/snapdragon_flash_unlocked_u_firmware_with_other/
If you flash a newer U variant than your V variant that should be all that's needed. I went directly from BRA1 Verizon to BRA1 U AT&T without issue
Edit: As for odin files, plenty of builds out there but make sure you go with one ~2gb in size. Otherwise itll just be a partial update (~200mb normally). U and V are identical hardware so you won't get software issues other than xyz carrier app not being there (or depending on provider of SIM, data might also be an issue).
Reddit link looks valid but it's basically "get odin and flash your build that would work given your current software and model" (I had to go to generic V variant firmware from U before returning to verizon V variant as Verizon's recovery didn't like the U model). If issues, try different builds or different Odins
Thanks!
What confused me the most is: https://www.phonemore.com/compare/p...m-g930v-vs-samsung-galaxy-s7-sm-g930a/3257631
Basically, it looks like g930v is missing some of the LTE bands.
I was able to install the latest G930U firmware, but now it is proving itself rather hard to verify what band my phone is using. It says LTE, but plenty of apps claim to display the LTE band, but none seem to do so.
JupoozunEd3 said:
Thanks!
What confused me the most is: https://www.phonemore.com/compare/p...m-g930v-vs-samsung-galaxy-s7-sm-g930a/3257631
Basically, it looks like g930v is missing some of the LTE bands.
I was able to install the latest G930U firmware, but now it is proving itself rather hard to verify what band my phone is using. It says LTE, but plenty of apps claim to display the LTE band, but none seem to do so.
Click to expand...
Click to collapse
https://forum.xda-developers.com/sp.../guide-enabling-additional-lte-bands-t3563474
this thread is a guide on how to enable certain bands on the phone being limited by firmware, as far as the hardware goes every s7 snapdragon have all the same contents just the firmware locking out to make it difficult to switch carriers.
kani!bal said:
https://forum.xda-developers.com/sp.../guide-enabling-additional-lte-bands-t3563474
this thread is a guide on how to enable certain bands on the phone being limited by firmware, as far as the hardware goes every s7 snapdragon have all the same contents just the firmware locking out to make it difficult to switch carriers.
Click to expand...
Click to collapse
I figured it out. There is a code *#2263# that displays the band information. However, if SIM is in, it complains that "RAT selection is locked,". By removing the SIM, and rebooting, the *#2263# works and you can enable/disable bands.

Categories

Resources