Note: I need some feedback to determine if this is *actually* working for people, since where I live, bands 2/4 are the main LTE bands for AT&T and T-Mobile and the International G7 Power (XT1955-2) supports those.
DISCLAIMER: I am not liable for any damage or legal liability caused by this guide or the improper application of it. As usual, do this at your own risk!
With that out of the way, lets do this:
You will need:
1. Your Moto G7 Power/Supra (any version). Not sure if you need to be rooted/bootloader unlocked or not. Mine is has already had both done. My guide to unlocking/rooting the G7 Power is here: https://forum.xda-developers.com/g7-power/how-to/versions-moto-g7-power-supra-magisk-t3923857
2. A usb cable to connect your g7 to a (windows) computer.
3. A windows computer.
4. Qualcomm QPST: (I used version 2.7.477) https://mirrors.lolinet.com/software/windows/Qualcomm/QPST/QPST.2.7.477.zip
5. Motorola USB Drivers: https://support.motorola.com/us/en/drivers
Step 1: Get QPST up and running
First download and install your Motorola USB drivers from earlier. Then download and install QPST. Boot your phone to the bootloader by rebooting and holding the volume down button or by turning off then holding power + volume down until the bootloader menu appears.
Using the volume up/down keys select "BP Tools" and then use the power key to boot the phone. Wait till its done then ensure USB debugging is turned off. If you dont know what that is, then it's probably off.
Go into device manager in windows by pressing windows key+r and typing devmgmt.msc. You'll see 3 devices under "other devices" without drivers (unless you got lucky and they automatically installed, mine didnt). We are intrested in the 3 that are named "moto g(7) power". We only need one of these, but its unclear what the correct one is, so repeat this process for all 3:
Right click and select "update driver"
Click "browse my computer for software"
Click "let me select from a list of availible drivers"
Scroll down to find "ports (com and lpt)"
Select "Motorola" as the manufacturer and "Motorola QC Diag Port" as the model
Ignore the "update driver warning" that comes up
Once you've got those installed, open QPST Configuration from the Start menu. It will show 3 devices, select the one that actually shows an esn. Then click "start clients" and then "Service programming"
Step 2: Unlocking the bands with QPST Service Programming
When QPST Service Programming opens, select your phone and hit OK. Then, click "read from phone" and wait a second for it to finish. Under the tab "UMTS System" you should see a bunch of checkboxes (most of them unchecked). At this point, you probably should click "Save to file" to backup what you're about to change.
You can select with the checkboxes specific bands you want to enable, but dont uncheck any that are already there. Alternatively you can do what I did and #yolo. Check "Any BC" to select them all. Dont mess with any of the other options but the "preferred bands" checkboxes because honestly I have no idea what that might do. When you're ready, click "Write to phone" and wait. I ended up getting an error that the "device stopped responding to read/write commands" and almost had a heart attack, but after closing and reopening QPST and clicking "read from phone" again, everything I had selected and wrote previously was still there.
Now, reboot your phone and give it a shot. You can confirm the changes stuck by booting back into BP tools mode through fastboot then opening QPST Configuration and the QPST Service Programming and clicking "read from phone" again.
Please let me know if this worked for you; if bands you previously could not get started working or if now LTE is working for you when it previously wasnt. You can check this by using the LTE Discovery app on the Play Store https://play.google.com/store/apps/details?id=net.simplyadvanced.ltediscovery&hl=en_US. As I stated earlier, bands 2 and 4 are the main LTE bands in my (rural) area so I cannot confirm this for myself. What I can confirm however that going through this process wont brick your device (unless you really screw up).
Thanks to samwathegreat for his guide here on getting the QC Diag drivers working/the phone showing up as a COM port which is required for this to work: https://forum.xda-developers.com/showpost.php?p=54338876&postcount=3
And thanks to bpear96 who made an older guide for older phones with an older QPST which I was able to graft into this guide for the G7 Power with the newer version of QPST: https://forum.xda-developers.com/moto-g/general/unlock-hspa-bands-moto-g-1700mhz-xt1032-t2878441
I'm still trying to get 5Ghz wifi working on the International model (XT1955-2) but am unsure if that's even a possibility. Any insight on that is welcome too .
Thanks for the great work, very hopeful that you can get 5Ghz wifi working. I've got the G7 power ordered, should be able to try out your guide in a few days, I'll let you know how it works.
Current status?
So its been a while whats the verdict is it possible? Also thanks for posting this guide.
magiricod said:
So its been a while whats the verdict is it possible? Also thanks for posting this guide.
Click to expand...
Click to collapse
Havent gotten any feedback regarding this yet, unfortunately.
Didn't work for me. I tried going old school by using QXDM/NV Browser and editing 06828 record, I think that was the record. It looked like it accepted the entry but the phone hung at boot and upon a second reboot the phone still didn't have the bands.
I also tried changing the device's information using fastboot oem hw utags but that seems to be a dead end. It seems there is an even lower system check before the bootloader/fastboot level. I think we may have to use edl and write the the modem. I just don't know enough about this low level stuff. Still researching though. I'm a little worried about pushing on because I can't afford replace the phone right now and not all the information on how to unbrick the phone is available yet.
I'm sure someone will figure out how to do it.
I tried this out but I haven't had any luck. It asks for a "Service Programming Code" when I try to "read from phone". If I bypass it, it will read, but when I try to write I get an error that it's not allowed.
Any ideas on where I could find the code?
So this is interesting, netmonster reports that I'm currently connected to lte band 66, although LTE Discovery says I'm on band 4. ??
diversenerd said:
netmonster reports that I'm currently connected to lte band 66, although LTE Discovery says I'm on band 4.
Click to expand...
Click to collapse
Has LTE Discovery been updated to show band 66? Last I checked it had not.
For me (XT1955-2) the screen is showing all bands already checked. The only checkbox disabled is the "Any BC".
I dont see 700Mhz but I see one checkbox already checked BC12 (I dont know if this is band 12). Please let me know whats happening...
---------- Post added at 02:33 AM ---------- Previous post was at 02:31 AM ----------
XT-1955-2: Bootloader unlocked and phone rooted.
Since I've had the phone it has been able to get LTE data pretty dang well on Verizon when set to LTE/CDMA ONLY, but can't make calls or SMS. I tried this method of checking bands but when I read from phone it has all bands checked already, except 'Any BC'. Just really hoping I can get this sorted out somehow.
So I have the metro version. It's unlocked, if I switch to visible I won't have access to the proper bands because of the metro rom?
Can someone please share a QCN file for a dual SIM variant?
I need it to compare to my single SIM one, cause I want to enable SIM2 but it has no IMEI.
halp pls?
also, when entering Service Programming Code, leaving it as 000000 doesn't throw any errors and reads well. Haven't tried writing though...
I tired it on my sim-unlocked Metro 1955-5, and did not give me any new LTE band options after i used the app provided..
btw, was the programming code supposed to stay at 00000?
Tolonus said:
XT-1955-2: Bootloader unlocked and phone rooted.
Since I've had the phone it has been able to get LTE data pretty dang well on Verizon when set to LTE/CDMA ONLY, but can't make calls or SMS. I tried this method of checking bands but when I read from phone it has all bands checked already, except 'Any BC'. Just really hoping I can get this sorted out somehow.
Click to expand...
Click to collapse
You get this sorted? I want to switch over to Verizon (tomorrow) but need confirmation that this phone will actually work with Verizon...
Software version: PPOS29.114-134-7
Stock Boot-loader.
illtww said:
You get this sorted? I want to switch over to Verizon (tomorrow) but need confirmation that this phone will actually work with Verizon...
Software version: PPOS29.114-134-7
Stock Boot-loader.
Click to expand...
Click to collapse
Well sorry to say it just isn't going to work with Verizon. This being double confirmed.
Followed steps, only thing not checked was Any BC, checked it, did the write and reboot and its still checked.
Does that mean its working?
Whats Any BC?
im on (XT1955-2)
Tolonus said:
Well sorry to say it just isn't going to work with Verizon. This being double confirmed.
Click to expand...
Click to collapse
It will work on any carrier the Sim has to be unlocked then u can use it any ware
diversenerd said:
Please let me know if this worked for you; if bands you previously could not get started working or if now LTE is working for you when it previously wasnt. You can check this by using the LTE Discovery app on the Play Store As I stated earlier, bands 2 and 4 are the main LTE bands in my (rural) area so I cannot confirm this for myself. What I can confirm however that going through this process wont brick your device (unless you really screw up).
.
Click to expand...
Click to collapse
So I have the -2 dual sim version, when I read from the phone i only had maybe 5 boxes checked off So I checked all boxes and wrote file to phone. all went well. rebooted and checked again and yes all were now active.
BUT I still do not pick up band 12. in my remote area I have band 2 and 12. side by side with my wifes LG she switches between band 2 and 12. and my moto g7 stays on band 2 then drops and has no service.
I still have no wifi calling or wifi texting with the phone. ready to throw it in the trash. any help would be welcome.
Related
Hi, I have an SGH-I747M that was originally purchased through Bell. In an attempt to unlock to make it work on Koodo, I went through SamMobile (after reading there was no way to unlock post 4.3 OTA update) and that seemed to half work.They resell a service from 123unlock.nl which is a client that uses adb or something of the sort to mess with phone files. The program afterwards said "Your phone is now unlocked! However if you don't see any carriers you need to do something in the advanced option and pay another $2x.xx dollars to do so". I didn't feel like giving them any more money at this point because I was upset that what I originally paid for didn't work properly. The fix was apparently an option in the advanced options that was an NVM repair/rebuild or something of the sort. I should have screenshotted the issue but of course didn't.
Now, the phone will boot up and does not offer me a SIM unlock option anymore. When searching for carriers it will ever only find Rogers for some reason. It won't recognize Koodo or Telus or anything of the sort (or bell when my bell SIM is in). Every now and then when it boots up, it will successfully send a text but only within a 5-10 second time frame after boot (I've made 1 phone call as well for 3 seconds). I've tried the Koodo SIM in my own Nexus 5 and works fine so the network is okay at least (plus I called Koodo and they verified on their end things look good... if that makes a difference). The SGS3 won't even accept an original Bell SIM at this point. It's always on either no network, 1 bar or full bars, never anything in between. I've tried flashing different ROMs from Bell stock to Koodo stock and CM11 and it won't work no matter what I do. Under all ROMs it pops up an "ME Returned temporary error" message on the screen.
I'm hoping someone might have seen this issue before or know what's going on with the phone that I can fix. I'm assuming it's something to do with the modem part of the phone that's refusing to connect to carriers but I'm at a loss to fix it. I haven't tried flashing different modems on it yet because I'm unsure which one would be a good fix and no one has had roughly the same issue I could find in 3 days of Googling for this issue. Any ideas are greatly appreciated. Thanks.
sgtcanadian said:
Hi, I have an SGH-I747M that was originally purchased through Bell. In an attempt to unlock to make it work on Koodo, I went through SamMobile (after reading there was no way to unlock post 4.3 OTA update) and that seemed to half work.They resell a service from 123unlock.nl which is a client that uses adb or something of the sort to mess with phone files. The program afterwards said "Your phone is now unlocked! However if you don't see any carriers you need to do something in the advanced option and pay another $2x.xx dollars to do so". I didn't feel like giving them any more money at this point because I was upset that what I originally paid for didn't work properly. The fix was apparently an option in the advanced options that was an NVM repair/rebuild or something of the sort. I should have screenshotted the issue but of course didn't.
Now, the phone will boot up and does not offer me a SIM unlock option anymore. When searching for carriers it will ever only find Rogers for some reason. It won't recognize Koodo or Telus or anything of the sort (or bell when my bell SIM is in). Every now and then when it boots up, it will successfully send a text but only within a 5-10 second time frame after boot (I've made 1 phone call as well for 3 seconds). I've tried the Koodo SIM in my own Nexus 5 and works fine so the network is okay at least (plus I called Koodo and they verified on their end things look good... if that makes a difference). The SGS3 won't even accept an original Bell SIM at this point. It's always on either no network, 1 bar or full bars, never anything in between. I've tried flashing different ROMs from Bell stock to Koodo stock and CM11 and it won't work no matter what I do. Under all ROMs it pops up an "ME Returned temporary error" message on the screen.
I'm hoping someone might have seen this issue before or know what's going on with the phone that I can fix. I'm assuming it's something to do with the modem part of the phone that's refusing to connect to carriers but I'm at a loss to fix it. I haven't tried flashing different modems on it yet because I'm unsure which one would be a good fix and no one has had roughly the same issue I could find in 3 days of Googling for this issue. Any ideas are greatly appreciated. Thanks.
Click to expand...
Click to collapse
Can you check your phone's settings => About Device and let's know what parameters you have there (Android Version, Baseband Version, Build Number>.
You mentioned you can send text or make call within a limited time frame. Was that with the Koodo SIM or the Bell? If the former, it would suggest the phone is unlocked to some extent but you are probably experiencing a baseband failure or need to correct the APN settings. Did you also try doing a factory reset?
Larry2999 said:
Can you check your phone's settings => About Device and let's know what parameters you have there (Android Version, Baseband Version, Build Number>.
You mentioned you can send text or make call within a limited time frame. Was that with the Koodo SIM or the Bell? If the former, it would suggest the phone is unlocked to some extent but you are probably experiencing a baseband failure or need to correct the APN settings. Did you also try doing a factory reset?
Click to expand...
Click to collapse
The information you're asking for is attached.
The texts I got off were from the Koodo SIM. I have updated the APN as well, and I did do a flash back to stock resetting all settings through Kies emergency update. I found a little trick where if you softbrick it by trying to flash 4.1, it'll give you the "Please use kies" error and that'll take you back to full stock 4.3. I'm pretty sure the baseband failure is the option I need to explore but at this point I don't know where to go to fix this.
Edit: I read this online and tried it: "The 4.3 update introduces a "security feature" which requires carrier- or region-locked phones to be activated once on the original locked network before the unlock code will work." The phone didn't recognize any network with the Bell SIM in except "EXT" which I've never heard of before and it did not connect properly so that didn't work. I also read that inputting #7465625*638*# will give me the Samsung SIM unlock menu which it did however I don't think the issue here is with the root and I'd hate to pay $50 at this point to have that not work as well.
sgtcanadian said:
The information you're asking for is attached.
The texts I got off were from the Koodo SIM. I have updated the APN as well, and I did do a flash back to stock resetting all settings through Kies emergency update. I found a little trick where if you softbrick it by trying to flash 4.1, it'll give you the "Please use kies" error and that'll take you back to full stock 4.3. I'm pretty sure the baseband failure is the option I need to explore but at this point I don't know where to go to fix this.
Edit: I read this online and tried it: "The 4.3 update introduces a "security feature" which requires carrier- or region-locked phones to be activated once on the original locked network before the unlock code will work." The phone didn't recognize any network with the Bell SIM in except "EXT" which I've never heard of before and it did not connect properly so that didn't work. I also read that inputting #7465625*638*# will give me the Samsung SIM unlock menu which it did however I don't think the issue here is with the root and I'd hate to pay $50 at this point to have that not work as well.
Click to expand...
Click to collapse
It's unlikely to be the regional lock as this feature means your phone will work with compatible networks in the region but not in other regions. You may, however, run Chainfire's Region Lock Away to be sure <http://forum.xda-developers.com/showthread.php?t=2470551>
Your firmware settings look OK so I'd be doubtful about a corrupted modem. You may still try to re-flash the modem via custom recovery. Download link for the CWM flashable zip is available here ... http://www.androidfilehost.com/?fid=23252070760973552
The guys who sold you the original code seem to have sold a dud as there is no reason for them to be asking for secondary payments and this sounds like the footprint of a regular scam. I'd be surprised though as they seem to be well rated
Larry2999 said:
It's unlikely to be the regional lock as this feature means your phone will work with compatible networks in the region but not in other regions. You may, however, run Chainfire's Region Lock Away to be sure <http://forum.xda-developers.com/showthread.php?t=2470551>
Your firmware settings look OK so I'd be doubtful about a corrupted modem. You may still try to re-flash the modem via custom recovery. Download link for the CWM flashable zip is available here ... http://www.androidfilehost.com/?fid=23252070760973552
The guys who sold you the original code seem to have sold a dud as there is no reason for them to be asking for secondary payments and this sounds like the footprint of a regular scam. I'd be surprised though as they seem to be well rated
Click to expand...
Click to collapse
I've tried reflashing the modem and I've actually paid $50 for the unlock code from Bell, the original carrier. I used the code to get the network unlock menu and inserted the code. I still get between 1-4 bars now with no network access on either network. It's not showing anything except Rogers still in network operator selection.
Any ideas at this point? It refuses to connect to any networks. I'm out of options.
Edit: I don't know if this makes a difference, but when I do root explorer I can't actually find the nv_data.bin file. It doesn't have anything of the sort in the /efs folder.
sgtcanadian said:
I've tried reflashing the modem and I've actually paid $50 for the unlock code from Bell, the original carrier. I used the code to get the network unlock menu and inserted the code. I still get between 1-4 bars now with no network access on either network. It's not showing anything except Rogers still in network operator selection.
Any ideas at this point? It refuses to connect to any networks. I'm out of options.
Edit: I don't know if this makes a difference, but when I do root explorer I can't actually find the nv_data.bin file. It doesn't have anything of the sort in the /efs folder.
Click to expand...
Click to collapse
Please let me understand a few things ... when you first acquired the phone, was it working normally on Bell prior to the first unlock attempt or you never used it at all until you tried Koodo? Secondly, was the unlock code you got from Bell identical to the one you got from the online service?
I'm trying to establish if it is a case of hardware failure not reported by the previous user especially if you bought it pre-owned from the secondary market. If you are not sure of the previous usage history, it could be a faulty or disconnected antenna which may require professional service. On the other hand if you are sure it was working fine prior to the unlock attempt, try the following ...
1) From the dial pad, enter *#197328640#
2) [1] UMTS
3) [1] DEBUG SCREEN
4) [8] PHONE CONTROL
5) [6] NETWORK LOCK
6) [3] PERSO SHA256 OFF
7) Press Menu => Back button and go all the way back to Step 3) above
8) [6] COMMON
9) [6] NV REBUILD
10) [1] NV REBUILD
Reboot and restart and let's see if this does it.
I've got a similar symtom different scenario (sister in-laws phone). I was also only able to see Rogers network on a search. I've got Telus version. It was working fine until it was brought to the Philippines, got unlocked there and brought back to Canada.
I was only able to see Rogers network until I went into the Service Menu (similar to above) and found the option to change the band. I changed it to Automatic. After that I was able to see Telus network. When trying to connect/register it would take a long time and give me an error "Unable to connect, try again later". I still need to do more troubleshooting, but that might be something to look at.
Note: Phone has stock MOD ROM, rooted and unlocked.
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.
Hi, I have followed the hidden menu apk method carefully which didn't change anything in the phone, I took my phone to THREE repair stores in my country, one of them could manage to do calls with it but no mobile data then the other store updated it I think and nothing is working like at start, PLEASE I BEG YOU for help, I am willing to donate once it is fixed. I was told that some ebay sellers remote unlock it but I don't trust them or at least I want the person to try and then I pay him if it works but I don't want to waste my money.
If it helps, it is now on Software version LS992ZV9, android version 7.0, and there is an update waiting to be installed but I still didn't accept it. I read there is a downgrade guide but how can it help or are there other links or guides to follow? Please guide or help me, it's been more than a year I have this brick.
Truepeace said:
Hi, I have followed the hidden menu apk method carefully which didn't change anything in the phone, I took my phone to THREE repair stores in my country, one of them could manage to do calls with it but no mobile data then the other store updated it I think and nothing is working like at start, PLEASE I BEG YOU for help, I am willing to donate once it is fixed. I was told that some ebay sellers remote unlock it but I don't trust them or at least I want the person to try and then I pay him if it works but I don't want to waste my money.
If it helps, it is now on Software version LS992ZV9, android version 7.0, and there is an update waiting to be installed but I still didn't accept it. I read there is a downgrade guide but how can it help or are there other links or guides to follow? Please guide or help me, it's been more than a year I have this brick.
Click to expand...
Click to collapse
As I stated in PM upgrade 1 step to ZVA and stop there never again.
The the hidden menu hack will work....
Thanks a lot for the help, I updated from ZV9 to ZVA and the hiddenmenu guide helped me do phone calls but I still can't have mobile data although I set up the APN correctly and I read the tutorial 3 times.
I noticed that in step 8 it says to "Reboot" then if I go in the Hiddenmenu settings in " LTE Data roam config" where I enabled all bands before reboot, I see that "Bar Roam Enabled" is set back to "Disable" so after a reboot it gets disabled and the "mobile network state" in settings is "connecting". Any idea ? Thanks.
Edit1: If I also go in Access Point Names in the normal settings, the apn I put is not checked although in the Hiddenmenu app it is. (https://i.imgur.com/mYwiRB9.jpg)
And usually the carrier in my country sends a settings sms that automatically adds the apn to the phone but when I request it the setrings sms never arrives as if it is blocked by the phone.
I even tried adding the APN of the second carrier we have in my country using my friend's sim card and his apn settings but same results as before.
I don't understand how calls work but mobile data isn't! Does my carrier requires additional settings in the phone to be unlocked or is my phone super locked? No expert to troubleshoot my problem? Please.
Finally fixed! I followed wildantics steps by starting with a R&D factory reset (maybe it is not required so you can try without it first), then a tip to skip configuring your phone which worked from me is to SPAM tap the power, and volume up and down buttons (and I didn't have any sim card inserted).
Use the hiddenmenucall app, in IOT(CDG2), LTE setting, put Operation Mode to Lab Network, reboot, insert sim, reboot. Then in ModemProtocol, RAT Selection, choose GSM/WCDMA/LTE Auto, then in ModemProtocol, Network Mode, choose Automatic, add your APN by going to IOT(CDG2), LTE Settings, APN settings and in LTE Data roam config, enable all the bands.
Which software version did you have when you tried these steps?
1.) PHONE ORIGINALLY LOCKED TO SPRINT
so i bougt this phone second hand in Europe. The phone had a bad screen and possibly some other damage i don't know about. Anyway, it turned out that the phone was locked to Sprint and i could not use it with my sim-card.
2.) PAID A GUY ON EBAY
https://www.ebay.com/itm/SPRINT-SIM...M-G710PM-CONVERT-TO-UNLOCKED-G7-/302468495217
I paid that guy (i do believe that he is also a member of the XDA community) and he ensured me that the phone was now unlocked and that i could use it with my sim-card. Under settings - hardware info it said model number was G710VM (or VMP or VMW, i don't remember exactly, but it was verizon wireless). the problem was that my phone still could not connect to the network. also, hidden menu *#*#4636#*#* was not accessible. Moreover, wi-fi connectivity was... mixed bag. Sometimes it worked, sometimes it did not work.
(in case the link is dead - he used octoplus to do the thing he did)
(he probably participated in this discussion: https://forum.xda-developers.com/lg-g7-thinq/help/lg-g7-sprint-unlock-t3823449)
3.) UPDATE TO PIE
https://www.****************/2019/06/17/download-and-install-lg-g7-android-9-pie-via-kdz-firmware/
After following these steps to get the Pie update (which i hoped would be the solution to my problems). Phone now reported it was G710ULM. Also, on lock screen in the top left corner it said 'No service - Mobitel'. Mobitel is the service provider here, so i was kinda hopeful, since it seemed that the phone can detect the network, but cannot connect. Hidden menu *#*#4636#*#* was accesible, but it only helped with my wi-fi connection. The 'select radio band' always reports 'selection unsuccessful'. I still could not set network manually or automatically for that matter (always error when i tried). I also tried the 10f firmware (oreo) and some others, but no luck. after i unlocked the bootloader i also performed the 'erase modemst1 modemst2' commands before flashing a new firmware but that also did not help.
(in case the link is dead - basically flashing firmware via LGUP)
4.) UNLOCKING THE BOOTLOADER
https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-bootloader-unlock-g7-thinq-t-t3963568
So this is where it is at at the moment. I followed this steps and now it reports product name LM-V350ULM and 'device state - unlocked' in the bootloader. If i boot it into recovery mode i just get the dead android with the red warning sign and 'no command' written under it. The device could access internet via wi-fi... until i put in the simcard. Now it cannot see the network anymore. If i repeat the command 'fastboot boot 710ULM11g_rootedboot.img' i get wifi back.
5.) THE POINT BEING?
Yeah. the point of this thread is obviously - what can i do to get the network?
This is my first android phone and yeah, quite the introduction to the android world that is.
Obviously i can (hardly, but i can) follow these step-by-step instructions, but apart from that, i have no idea what to do or how to do it. So yeah, this phone is pretty much just a wifi machine unless someone can help me.
I did unlocked my bootloader following this tutorial
https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-bootloader-unlock-g7-thinq-t-t3963568
Why is your device showing V350ULM (that is U.S. Unlocked V35 Thinq)? Reflash G7 pie firmware from Europe and access #*#*4636*#*# and change the network to GSM/WCDMA/LTE and check if it picks up the network.
sinkoo1979 said:
Why is your device showing V350ULM (that is U.S. Unlocked V35 Thinq)? Reflash G7 pie firmware from Europe and access #*#*4636*#*# and change the network to GSM/WCDMA/LTE and check if it picks up the network.
Click to expand...
Click to collapse
it's showing V350ULM because i unlocked the bootloader via the method described here: https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-bootloader-unlock-g7-thinq-t-t3963568
there is no other known method to unlock the bootloader on any LG G7 thinq except for the european version.
If i reflash the G7 pie firmware my bootloader gets locked again. I know because i already did that. While I had that firmware i also dialed *#*#4636#*#*, but when i change the network nothing really happens. If i choose the 'select radio band' sub-menu i always get the 'unsuccessful' message no matter which band i choose.
tws_ifp said:
it's showing V350ULM because i unlocked the bootloader via the method described here: https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-bootloader-unlock-g7-thinq-t-t3963568
there is no other known method to unlock the bootloader on any LG G7 thinq except for the european version.
If i reflash the G7 pie firmware my bootloader gets locked again. I know because i already did that. While I had that firmware i also dialed *#*#4636#*#*, but when i change the network nothing really happens. If i choose the 'select radio band' sub-menu i always get the 'unsuccessful' message no matter which band i choose.
Click to expand...
Click to collapse
I unlocked my bootloader using the same method and it will not lock bootloader if you flash pie firmware (once it's unlocked it's unlocked). And my G7 is showing as G710ULM not V350ULM (using the same method to cross flash firmwares). Make sure to flash European pie firmware.
Hello everyone
I have an LG v30+ running stock android 9 with the global v31a rom.
Today I moved to a new carrier, and after installing new sim, the cellular internet works just fine, but voice calls and sms are not working.
I get the "phone not allowed for voice" message and on the taskbar shown on a "MM" icon.
At first I also received an error windows I attached here.
Moving the new sim to another newer xiaomi phone - everything works fine including calls and sms.
Customer service couldn't fix them from their said claiming it's an issue with phone configurations.
Any idea on how to fix this?
Thanks
I just tested another company's sim card and everything works fine.
So it must be some support from the new carrier
Any idea what can be done before I chose another carrier?
What is the model number (Settings -> General -> About phone -> Hardware info)?
Please share a screendump of your Network status screen (Settings -> General -> About phone -> Network). You can blank out the IP address.
Also, please share screendump of the Testing menu Phone information screen (dial *#*#4636#*#* -> Phone information). Scroll it up 3 lines lines so you don't share IMEI, Phone number, IMSI, but so that we can see all the Provisioned lines.
First thing I would try is a Network settings reset (Settings -> General -> Restart & reset -> Network settings reset) then restart the phone.
It is possible that your carrier only provides voice over VoLTE (and SMS over IMS, which is part of the same feature set). That only works if the phone knows the correct settings for your carrier. That would explain why it works with the newer Xiaomi phone. You can check if you have VoLTE settings in the menu (Settings -> Network menu -> Call). Even if the phone does NOT know your carrier, you may be able to configure it through the Hidden menu (depending on your model number). But it is VERY complicated, and you need detailed information from the carrier about the settings to enter.
Or it could be something else entirely.
On a different note, this thread definitely should have been in the Questions section, not in the Guides section.
KamaL said:
Hello everyone
I have an LG v30+ running stock android 9 with the global v31a rom.
Click to expand...
Click to collapse
Not sure why you are calling 31a "global". It's merely the European H930 31a Pie. I've seen a couple of other people use that term and not sure why... It's not "global" in any way than any other KDZ. (EDIT: I see your screenshot where it says global, which is very strange. Is that some setting? That's just weird.)
Unless you actually have an H930 phone, using the H930 KDZ will not give you the H930 bands or anything. You are still using the LTE/HSPA bands that are on your variant. Some people use H930 firmware on H930D/H930DS for different language options and vice versa. So, "global" is quite an exaggeration. Canada H933 has more LTE bands than any of the V30 variants, so it's really the "global" if any are. (But you can't convert to Canada H933 unless you have a compatible North American variant.)
What variant do you have and what country do you live in?
Ahh, so a European H930. Which country are you in, and who is the carrier?
KamaL said:
I just tested another company's sim card and everything works fine.
So it must be some support from the new carrier
Any idea what can be done before I chose another carrier?
Click to expand...
Click to collapse
I don't know where you live and what variant you actually have, but you are using EU H930 31a KDZ.
For instance, if you are in India and using Jio carrier, you need India H930DS KDZ as Jio is VoLTE only. But H930 31a doesn't have Jio's VoLTE settings... Using "another carrier" which allows legacy HSPA during phone calles would then be why it works on the other carrier but not Jio. To fix that you would need to flash India region H930DS firmware.
I am not saying you live in India or using Jio -- you didn't give us any information about that. I am just giving a real life example of why your phone would work on one carrier but not another.
Also, some carriers make you register your phone. If you just stick the same SIM card in you had from previous phone, it sees it's a different phone and will throw up an error message like that until you call them or go into store and tell them what "new" phone you are using. The "other carrier" may not be such a control freak.
---------- Post added at 10:37 AM ---------- Previous post was at 10:28 AM ----------
TheDannemand said:
Ahh, so a European H930. Which country are you in, and who is the carrier?
Click to expand...
Click to collapse
Since he says he has V30+, I know he doesn't have native H930 phone. There are no H930 V30+. The V30+ are H930G and H930DS and neither on them have firmware numbered "31a".
---------- Post added at 10:44 AM ---------- Previous post was at 10:37 AM ----------
KamaL said:
Hello everyone
I have an LG v30+ running stock android 9 with the global v31a rom.
Today I moved to a new carrier, and after installing new sim, the cellular internet works just fine, but voice calls and sms are not working.
I get the "phone not allowed for voice" message and on the taskbar shown on a "MM" icon.
At first I also received an error windows I attached here.
Moving the new sim to another newer xiaomi phone - everything works fine including calls and sms.
Customer service couldn't fix them from their said claiming it's an issue with phone configurations.
Any idea on how to fix this?
Thanks
Click to expand...
Click to collapse
I see posts from you back in November and you have been on 31a for awhile...
https://forum.xda-developers.com/showpost.php?p=81065243&postcount=852
So, any issues have to be with this new carrier as you have had phone calls on 31a for most of a year now.
Sorry, double post
Thanks everyone for the replies.
@TheDannemand
Some more information about my device:
Country: Israel
Carrier: We4G
Hardware version: LH-H930G.
Looking up using my IMEI number on lg-roms website gives this model: LG V30 Plus TD-LTE
I shared the network menu testing menu you mentioned.
I DO NOT see any VOLTE setting in the Call menu.
I already tried network settings reset.
@ChazzMatt
I have the H930G version. Actually I always follow your guides in that thread to upgrade the version, and I've been on this stock firmware for a year. So it must be something related to the carrier settings I think.
I actually didn't use my country's specific KDZ file as it was released a bit late. I used the european version if I remember well.
Should I flash the local one? According to lg-firmwares and lg-roms website it's this one:
Code:
https://lg-firmwares.com/downloads-file/21127/H930G30a_00_OPEN_IL_OP_0903
Will it have an impact on call services and bands?
Any chance it is really a carrier using VoLTE for calls? I tried asking all kind of questions but didn't get any smart answer from the tech support team.
Also, what do you mean by registering the phone? I never heard about this.
Thanks again!
View attachment 5082915View attachment 5082917View attachment 5082919
For some reason I cannot see your attachments. What I wanted to see was (1) whether you have an LTE connection and (2) whether the phone sees VoLTE as provisioned. In truth, I only need the Phone info screen (from the Testing menu) to see that.
I think it is quite plausible that your carrier requires VoLTE to make calls and that your ROM doesn't support it because it doesn't know your carrier. A ROM for your region probably DOES know your carrier (if they are well established). But it's also possible that it doesn't (if they're newer or changed their VoLTE parameters in recent years).
This was my first thought when I read your post and saw that you were on 4G (which should be LTE, although in USA carrier marketing departments have diluted the term to also cover old 3.5G). And I see that it is ChazzMatt's thought too, with the example from Jio India.
I googled We4G to get a clue if they're VoLTE only, but all the links were in Hebrew
Carriers who don't require VoLTE drop the connection to 3G in order to make calls. This works on every phone that supports LTE because it doesn't require knowledge about your carrier.
However VoLTE relies entirely on VoIP and requires an elaborate login to carrier servers, with security and handshaking to prevent illicit use of their network. And the parameters for that are carrier specific. Each phone has a so-called "buffet" of carrier configs known to that ROM. That's why it matters to use a ROM that knows your carrier.
Thanks for the detailed reply.
I think I'll try the local ROM I mentioned. I just want to be sure it doesn't make a clean wipe if I flash Kdz with LG UP. is that so?
I'm uploading the attachments once again.
Tapatalk is messing with attachments. Here's the last one
KamaL said:
Thanks for the detailed reply.
I think I'll try the local ROM I mentioned. I just want to be sure it doesn't make a clean wipe if I flash Kdz with LG UP. is that so?
I'm uploading the attachments once again. View attachment 5082947View attachment 5082949
Click to expand...
Click to collapse
Thank you. I see your attachments now.
So you do indeed have LTE connection for your mobile data. But the phone doesn't even pick up VoLTE provisioning -- which is the first and most basic step in supporting VoLTE.
I would definitely try the regional ROM, but you should flash with Refurbish or Partition DL -- which means losing data. Sorry.
In fact, since you're doing a Frankenstein, I would flash back to Nougat first using Partition DL (to update the partition table), perform a Master Reset (it may bootloop until you do), then flash up to Pie. Wait for @ChazzMatt to confirm those steps.
Good luck to you
TheDannemand said:
Thank you. I see your attachments now.
So you do indeed have LTE connection for your mobile data. But the phone doesn't even pick up voLTE provisioning.
I would definitely try the regional ROM, but you should flash with Refurbish or Partition DL -- which means losing data.
In fact, since you're doing a Frankenstein, I would flash back to Nougat first using Partition DL (to update the partition table), perform a Master Reset, then flash up to Pie. Wait for Chazz to confirm those steps.
Good luck to you
Click to expand...
Click to collapse
I really hope I can flash it without losing data. I prefer not to back up all data.
That's what I also did in the previous rom upgrades.
Would that be possible?
KamaL said:
I really hope I can flash it without losing data. I prefer not to back up all data.
That's what I also did in the previous rom upgrades.
Would that be possible?
Click to expand...
Click to collapse
I don't see any way to do this safely without losing data. Sorry.
You could skip that carrier and go with one that doesn't require VoLTE (i.e. one which supports the old dropping to 3G for calls). But you won't have the benefits of VoLTE and WiFi Calling. And you may be in the same situation later if that carrier decides to close down their 3G network and go VoLTE only.
KamaL said:
Tapatalk is messing with attachments. Here's the last oneView attachment 5082951
Click to expand...
Click to collapse
Try enabling 'VoLTE Provisioned' on that screen then restarting your phone.
Is there an 'Advanced Calling' menu in Settings?
Two things that might help:
1) Before taking the plunge, put the SIM in your Xiaomi phone and see if you can make a call WITHOUT using VoLTE: One way is if Settings menus allow disabling VoLTE. If no Settings menus, try the same Testing info - Phone info screen and see if VoLTE is provisioned there. I assume it is. But if VoLTE is ALSO not provisioned on the Xiaomi, that means the problem isn't lack of VoLTE on the V30.
2) Just backup the phone using LG Backup, either through Settings -> General menu -> Backup (then transfer file to PC or flash drive) or using LG Bridge. It backs up all app data and most phone settings (though not all). And I was able to use it across different ROM versions and even different ROMs (between H932 and US998).
jptV30 said:
Try enabling 'VoLTE Provisioned' on that screen then restarting your phone.
Is there an 'Advanced Calling' menu in Settings?
Click to expand...
Click to collapse
I can't turn it on unfortunately.
There's a call--> additional settings - - > other settings menu
But I get this error message when I try it, and then I lose LTE connection too.
jptV30 said:
Try enabling 'VoLTE Provisioned' on that screen then restarting your phone.
Click to expand...
Click to collapse
That one is info only, not a toggle -- even though it looks like it.
KamaL said:
There's a call--> additional settings - - > other settings menu
But I get this error message when I try it, and then I lose LTE connection too. View attachment 5082979
Click to expand...
Click to collapse
Yeah, as long as the phone doesn't see it as provisioned, we can forgot about menus and settings.
TheDannemand said:
Two things that might help:
1) Before taking the plunge, put the SIM in your Xiaomi phone and see if you can make a call WITHOUT using VoLTE: One way is if Settings menus allow disabling VoLTE. If no Settings menus, try the same Testing info - Phone info screen and see if VoLTE is provisioned there. I assume it is. But if VoLTE is ALSO not provisioned on the Xiaomi, that means the problem isn't lack of VoLTE on the V30.
2) Just backup the phone using LG Backup, either through Settings -> General menu -> Backup (then transfer file to PC or flash drive) or using LG Bridge. It backs up all app data and most phone settings (though not all). And I was able to use it across different ROM versions and even different ROMs (between H932 and US998).
Click to expand...
Click to collapse
I didn't find settings to turn off VoLTE.
Here are the settings on the xiaomi. It is NOT provisioned apparently.... View attachment 5082983
KamaL said:
I didn't find settings to turn off VoLTE.
Here are the settings on the xiaomi. It is NOT provisioned apparently....
Click to expand...
Click to collapse
The screenshot doesn't include the VoLTE line. But if VoLTE is ALSO not provisioned on the Xiaomi that means the problem if elsewhere, not lack of VoLTE on the V30. So hold off on that Frankenstein for a bit.
I have a client meeting coming up, probably won't have more time today. But this is good news, kind of