Hi,
I have Moto G4 Plus (XT1643) (India Version), and It doesn't support USA LTE bands. So I was trying to unlock the LTE bands using this guide
I used the NV Calculator App, which is available on playstore to calculate the values and unlock the bands mentioned in Moto G4 Plus's gsmarena page.
2G bands GSM 850 / 1900 - XT1644 (USA)
3G bands
4G bands LTE band 1(2100), 2(1900), 3(1800), 4(1700/2100), 5(850), 7(2600), 8(900), 12(700), 13(700), 17(700), 25(1900), 26(850), 41(2500) - XT1644 (USA)
Even after setting the NV values to the following, LTE is not working.
NV ID Value
6828 1099562031327
6829 1099562031327
1877 2621440
0441 0
0946 0x0028
2954 0
It would be great if someone could post the above NV ID values of Moto G4 Plus (US Version)
Thanks
For LTE, the 06828 is the only one that's needed, the 06829 reads "inactive".
Orig in XT1644 US is 1099561965791 see the attached (unmodified value, after flashing the N, was identical in MM). That is 1,2,3,4,5,7,8,12,13,25,26,41. Band 17 is not needed, it's just a subset of 12, AT&T was forced by FCC to allow all the band 12 devices "in" their 17. Actually all the new AT&T devices come with 12.
However, the appropriate RF block (amplifier) might not be installed. For example I have changed my numbers to include the LTE band 20 (rural EU), but on my latest trip to EU, in the zone that I knew there is band 20 avail, I still got only H+ (luckily the LTE speed there wasn't that much better than H+). I have checked and the new NV value was still present (on an Asus Laser 2 ZenFone the OS was re-writing the original value at reboot). So for me the modding didn't help.
I think that the other items are different because of CDMA support.
00441 input 0 - 0
0041 input 0x3 - BC0
00946 - 0
002954 - 0
001877 -562950069305735
001878 - 201
06828 - 1099561965791
Good luck and... report back.
Hi guys,
New thread since previous one wasn't related to initial post.
So I have a Dirty Santa'd LS997, and I want to run a US996 based rom for the top screen. I am in Canada with Fido.
When running on an AOSP based rom like LineageOS, I get LTE working out of the box with no issues!
When running on a US996 based rom, I have to go through hoops to get LTE working and it is not persistent. Once the connection is lost I have to redo the procedure.
The procedure I have to do is as follows:
- Go in Network Mode
- Disable Global, enable LTE/GSM/UMTS
- Set submode to "GSM/GPRS/EDGE only" or "UMTS/HSPA/HSPA+ Only"
- Wait for 3g/HSPA connection to be active
- Set Submode to "LTE/LEgacy 3GPP Multi"
- LTE now works until I get disconnected/connect to wifi. Once disconnected, it will never reconnect unless I redo these steps.
I checked the APN settings over and over again, and they are correct and set automatically. They are the exact same as Fido recommends: http://www.fido.ca/consumer/content/configure-unlocked-device-guide
I know my phone is compatible with LTE from Fido since:
- I get an LTE connection with AOSP based roms and temporarily via US996 roms.
- LTE specs for both phones:
LS997: LTE band 2(1900), 3(1800), 4(1700/2100), 5(850), 7(2600), 12(700), 25(1900), 26(850), 41(2500)
US996: LTE band 2(1900), 3(1800), 4(1700/2100), 5(850), 7(2600), 12(700), 13(700), 17(700), 20(800), 25(1900)
Source: http://www.gsmarena.com/lg_v20-8238.php
Fido requires 700 MHz on Band 17, 1700/2100 MHz on Band 4, 2600 MHz on Band 7
Source: http://www.fido.ca/consumer/content/configure-unlocked-device-guide
Bands 4 and 7 are a perfect match, and band 17(700) is a subset of band 12(700), so the LS997 should be 100% compatible.
Source: https://en.wikipedia.org/wiki/LTE_frequency_bands​
Would anyone have an idea why this is happening? Any ideas on how to fix it? Could this be related to the radio version?
Thanks
Update if someone ever runs into this problem.
I setup the APNs as if it were NOT an LTE device (used Fido-core-appl1.apn instead of LTEMOBILE.APN), left network on global, and it seems to have fixed the connection issues. I now get a data connection normally, from 3g to LTE when available.
This is the product page in eBay:
m.ebay.com/itm/201909374302
It says the product has no regional lock. It'll be used in India. What are the prerequisites for it to work without any problems just like an Indian S8? VoLTE and SPay are must. Am I supposed to use an US sim in it for 5 minutes? Anything like that? What does no regional lock mean?
Yes , you can use in India.
2G bands GSM 850 / 900 / 1800 / 1900 - SIM 1 & SIM 2
3G bands HSDPA 850 / 900 / 1700(AWS) / 1900 / 2100
4G bands LTE band 1(2100), 2(1900), 3(1800), 4(1700/2100), 5(850), 7(2600), 8(900), 17(700), 20(800), 28(700)
http://techpp.com/2015/12/28/4g-lte-india-guide/ - Band 40 & 41 missing , but other Bands is ready
What does no regional lock mean?
They havent a Sim Lock (like A&T,telecom etc..) so can you all card of the world.
dayl1ght said:
Yes , you can use in India.
2G bands GSM 850 / 900 / 1800 / 1900 - SIM 1 & SIM 2
3G bands HSDPA 850 / 900 / 1700(AWS) / 1900 / 2100
4G bands LTE band 1(2100), 2(1900), 3(1800), 4(1700/2100), 5(850), 7(2600), 8(900), 17(700), 20(800), 28(700)
techpp.com2015/12/28/4g-lte-india-guide
Band 40 & 41 missing , but other Bands is ready
What does no regional lock mean?
They havent a Sim Lock (like A&T,telecom etc..) so can you all card of the world.
Click to expand...
Click to collapse
Hey. Thanks for the reply. I'm worried if Samsung Pay can be used directly in India. I'm confused because this might not have the required firmware.
I know what's network locked.
I don't clearly understand the "not regional locked". Does that mean I can use it India by inserting an Indian SIM with VoLTE and SPay working perfectly?
does anyone know if this 8 Pro is compatible to the visible Network?
I would be interested in knowing this also.
tdamocles said:
does anyone know if this 8 Pro is compatible to the visible Network?
Click to expand...
Click to collapse
You can get Visible to work on any custom ROM or phone that exists - if you know what you're doing. I've gotten it to work anywhere.
Burt Squirtz said:
You can get Visible to work on any custom ROM or phone that exists - if you know what you're doing. I've gotten it to work anywhere.
Click to expand...
Click to collapse
Any tips? My OnePlus 8 Pro has the APN settings showing up when putting in my Visible SIM but no service.
Calizorz said:
Any tips? My OnePlus 8 Pro has the APN settings showing up when putting in my Visible SIM but no service.
Click to expand...
Click to collapse
Have a screen shot of this? Do the apns look like the pic?
Sent from my GM1917 using Tapatalk
View attachment 5000881
{
"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"
}
tdamocles said:
Have a screen shot of this? Do the apns look like the pic?
Sent from my GM1917 using Tapatalk
View attachment 5000881
Click to expand...
Click to collapse
Here's how my APN looks
Calizorz said:
Here's how my APN looks
Click to expand...
Click to collapse
What phone was previously used on visible? Just to troubleshoot....put sim in previous phone to verify that it works.
Sent from my GM1917 using Tapatalk
Debating the pro or the 8ua on Verizon when it drops. Anyone know if the Verizon specific 8 UA will be the 12gb 256 version. Read it somewhere. Blows there not selling the pro
I used the SIM in my OnePlus 7T and it works on that phone still
Calizorz said:
I used the SIM in my OnePlus 7T and it works on that phone still
Click to expand...
Click to collapse
Bet you it's verizon's side which is screwy. I remember on the 7pro when the firmware wasn't compatible at one point and the apns' didn't even show.
Is this the Chinese version 8pro or is it the North American version?
not sure about this accuracy but look below:
3G bands HSDPA 800 / 850 / 900 / 1700(AWS) / 1800 / 1900 / 2100
4G bands LTE band 1(2100), 2(1900), 3(1800), 4(1700/2100), 5(850), 7(2600), 8(900), 12(700), 13(700), 17(700), 18(800), 19(800), 20(800), 25(1900), 26(850), 28(700), 32(1500), 34(2000), 38(2600), 39(1900), 40(2300), 41(2500), 42(3500), 46(5200), 66(1700/2100) - EU
LTE band 1(2100), 2(1900), 3(1800), 4(1700/2100), 5(850), 7(2600), 8(900), 12(700), 13(700), 17(700), 18(800), 19(800), 20(800), 25(1900), 26(850), 28(700), 29(700), 30(2300), 34(2000), 38(2600), 39(1900), 40(2300), 41(2500), 46(5200), 48, 66(1700/2100), 71(600) - NA
LTE band 1(2100), 2(1900), 3(1800), 4(1700/2100), 5(850), 7(2600), 8(900), 12(700), 17(700), 18(800), 19(800), 20(800), 26(850), 34(2000), 38(2600), 39(1900), 40(2300), 41(2500), 46(5200) - IN
LTE band 1(2100), 2(1900), 3(1800), 4(1700/2100), 5(850), 7(2600), 8(900), 12(700), 17(700), 18(800), 19(800), 20(800), 26(850), 34(2000), 38(2600), 39(1900), 40(2300), 41(2500) - CN
tdamocles said:
Bet you it's verizon's side which is screwy. I remember on the 7pro when the firmware wasn't compatible at one point and the apns' didn't even show.
Is this the Chinese version 8pro or is it the North American version?
not sure about this accuracy but look below:
3G bands HSDPA 800 / 850 / 900 / 1700(AWS) / 1800 / 1900 / 2100
4G bands LTE band 1(2100), 2(1900), 3(1800), 4(1700/2100), 5(850), 7(2600), 8(900), 12(700), 13(700), 17(700), 18(800), 19(800), 20(800), 25(1900), 26(850), 28(700), 32(1500), 34(2000), 38(2600), 39(1900), 40(2300), 41(2500), 42(3500), 46(5200), 66(1700/2100) - EU
LTE band 1(2100), 2(1900), 3(1800), 4(1700/2100), 5(850), 7(2600), 8(900), 12(700), 13(700), 17(700), 18(800), 19(800), 20(800), 25(1900), 26(850), 28(700), 29(700), 30(2300), 34(2000), 38(2600), 39(1900), 40(2300), 41(2500), 46(5200), 48, 66(1700/2100), 71(600) - NA
LTE band 1(2100), 2(1900), 3(1800), 4(1700/2100), 5(850), 7(2600), 8(900), 12(700), 17(700), 18(800), 19(800), 20(800), 26(850), 34(2000), 38(2600), 39(1900), 40(2300), 41(2500), 46(5200) - IN
LTE band 1(2100), 2(1900), 3(1800), 4(1700/2100), 5(850), 7(2600), 8(900), 12(700), 17(700), 18(800), 19(800), 20(800), 26(850), 34(2000), 38(2600), 39(1900), 40(2300), 41(2500) - CN
Click to expand...
Click to collapse
It's the NA 8 Pro. Visible is weird and makes manufacturers enable support for the service to work or something. The 7 Pro and 7T both had software updates enabling Visible support so I guess I'll have to wait or swap carriers
Calizorz said:
It's the NA 8 Pro. Visible is weird and makes manufacturers enable support for the service to work or something. The 7 Pro and 7T both had software updates enabling Visible support so I guess I'll have to wait or swap carriers
Click to expand...
Click to collapse
It looks as though they have the support in the firmware because the APNs are coming up.
Sent from my GM1917 using Tapatalk
Calizorz said:
I used the SIM in my OnePlus 7T and it works on that phone still
Click to expand...
Click to collapse
When you look in your visible info, what device does it show?
Sent from my GM1917 using Tapatalk
I've been doing extensive research on this as well, being a new Visible convert. I joined them with the OP8 and Visible works on stock perfectly, but I couldn't get ANY custom roms to work because apparently Visible's version of the OP8 is ever-so-slightly different that ROMs just WOULD. NOT. FLASH. So, got an unlocked OP8 Pro (IN2025) and Visible works perfectly on OOS (confirmed across multiple versions of Android 10 and 11). Custom roms will flash via fastboot method, but none will recognize Visible SIM. crDroid on A11 won't let me into Network Settings at all, but SIM info in the status bar of the lock screen shows "No SIM inserted - Visible" telling me it sees the Visible SIM in one of the two slots. But that's as far as I've been able to get with that.
Resurrection Remix will flash and sees the SIM as a Verizon SIM. It populates the APN settings with StraightTalk, Verizon, and Xfinity Mobile (another MVNO using Verizon), but the 4 Visible-specific APN entries in the stock apn-conf.xml file found in /system/product/etc are missing on Resurrection. Stock OOS 11 has them included, which leads me to believe it's an APN thing, along with whatever other "carrier integration" that may go on deeper in the ROM. But, being that these partitions are all locked read-only, I can't replace the apn-conf in Resurrection with the one pulled from stock.
TL;DR recap - OP8 Pro running OOS works with Visible hot off the MSM tool flash. But crDroid and Resurrection can't connect to the network, presumably because the APN settings needed are missing. If there's anybody that has the capability of looking into this or baking these settings into the roms that needs information from stock, pulled images, etc. I would be more than happy to contribute to help bring Visible support to these roms.
Thanks!
More info! APN settings can be "overwritten" with a Magisk module, but that still won't get the job done because crucial vendor files are missing from ROMs built off of AOSP, PE, LOS, etc. So when a rom comes out, there's no point in testing it if it wasn't explicitly built with Verizon/Visible people in mind, since the vendor blobs are going to be missing from all of them based off of the same structure.
If there's any developers interested in pursuing this challenge, there's a gathering of people that would be willing to step up for testing and possibly even contribute to a "bounty" of sorts. I can't speak for all, but I'm certainly open to contributing to developers that are going above and beyond this way!