Database Develop

[Q] xt862 can't use cdma 3G

My phone is Verizon Droid 3 XT862.
It can't use cdma 3g or 1x network.
SMS and voice is normal. WIFI is normal too.
If i use GSM card, same problem appears.
I flashed the rom , changed the file named 'ppp-rils.option'.
But nothing happened.
Please help me.
thanks.

powerword said:
My phone is Verizon Droid 3 XT862.
It can't use cdma 3g or 1x network.
SMS and voice is normal. WIFI is normal too.
If i use GSM card, same problem appears.
I flashed the rom , changed the file named 'ppp-rils.option'.
But nothing happened.
Please help me.
thanks.
Click to expand...
Click to collapse
Fully restore your phone using my Fast / Easy unbrick method, just search the general section. (All it does is restore your phone to complete stock.)
You can try other stuff, but this method seems to fix most issues that aren't "easy" to fix.

I will try this method.
But I want to know if there are something can be changed or flashed other than this rom.
I want to fix my phone's network.
It not work on cdma , gsm or wcdma.
I flash xt883 rom, but nothing happened.
Can i flash radio? Change hardware setting.
who can tell me.

powerword said:
I will try this method.
But I want to know if there are something can be changed or flashed other than this rom.
I want to fix my phone's network.
It not work on cdma , gsm or wcdma.
I flash xt883 rom, but nothing happened.
Can i flash radio? Change hardware setting.
who can tell me.
Click to expand...
Click to collapse
You don't need the xt883 ROM in order to use the phone on any foreign gsm. The phone must be unlocked by Verizon, then you need to flash the xt883 radio.img, then edit/replace the build.prop. I would flash back to stock first, since the xt883 is a weird ROM, but you probably don't have to. There are already plenty of threads where the explanations have been given, so look around: search Verizon D3 on T-Mobile, D3 on AT&T/T-Mobile, etc.
You will have to turn off 'automatically select operator' in settings and choose manually the one you're using. T-Mobile users will only get edge and below, while AT&T users will get 3g.
Droid 3 with stock xt862 ROM working on T-Mobile via xt883 radio.img & custom build.prop

BenSWoodruff said:
You don't need the xt883 ROM in order to use the phone on any foreign gsm. The phone must be unlocked by Verizon, then you need to flash the xt883 radio.img, then edit/replace the build.prop. I would flash back to stock first, since the xt883 is a weird ROM, but you probably don't have to. There are already plenty of threads where the explanations have been given, so look around: search Verizon D3 on T-Mobile, D3 on AT&T/T-Mobile, etc.
You will have to turn off 'automatically select operator' in settings and choose manually the one you're using. T-Mobile users will only get edge and below, while AT&T users will get 3g.
Droid 3 with stock xt862 ROM working on T-Mobile via xt883 radio.img & custom build.prop
Click to expand...
Click to collapse
I flashed xt862 rom .
Calls and text is OK whether GSM or cdma.
Network is wrong whether GSM or cdma.
I changed APN settings, nothing happened.
What can i do next.

powerword said:
I flashed xt862 rom .
Calls and text is OK whether GSM or cdma.
Network is wrong whether GSM or cdma.
I changed APN settings, nothing happened.
What can i do next.
Click to expand...
Click to collapse
I'm not sure what is wrong with your connection, but mine has problems sometimes where the phone will not recognize any available gsm networks. It's sometimes like this after I reboot my phone, but if changing my settings doesn't work, rebooting again will usually work.
Is your phone unlocked by Verizon? Did you flash the xt883 radio.img since changing your ROM? Did you replace your build.prop file with the tweaked one? I will try to find these resources for you if you still need them, but you should be able to find them by searching if you haven't already. After doing these things, you just have to reboot then go to your settings and tell it to prefer gsm. On T-Mobile, you wont get umts. On AT&T you will get gsm and umts.
In settings, you need to select wifi & network settings -> mobile networks -> network mode -> then choose gsm/umts, back to mobile networks -> under gsm/umts settings, click select network, then choose gsm only for T-Mobile or automatic for AT&T, then click operator select, select network and choose your operator. Select automatically will have a check box next to it and you should deselect it. I didn't have to put in my apn settings, because my sim card provides those automatically.
If these settings tweaks don't work for you then I really have no clue what will fix it because it is likely that something else is wrong. I can't be of much more help without seeing the device. I would suggest to keep playing around in settings and just use your head to see why it's not connecting. If you are getting voice and text service on your carrier, data shouldn't be a problem if your settings are done correctly.
Good luck!
Droid 3 with stock xt862 ROM working on T-Mobile via xt883 radio.img & custom build.prop

[Q] XT862 (Veriz): No connection, baseband & IMEI 'unknown', sim not detected

Hi,
I just recently bought (second hand, on eBay - that was my first mistake...) a Verizon Droid 3 (so presumably an XT862?). It is failing to connect to any network, and is not detecting my SIM card. I'm in Australia, so there is no CDMA network here (but GSM on 850, 900, and 2100; UMTS 850, 2100).
The peculiar thing is that the Baseband is 'unknown' in the phone 'About' screen. Likewise, the IMEI, IMEI SV, Network, MEID, MIN, ERI and PRL are unknown. I don't know how many of these relate to the network, but I can't imagine an 'unknown' baseband is a good thing.
The phone is ostensibly 'unlocked', but shouldn't it connect to networks for emergency calls? (which is doesn't), even if it is locked and so doesn't detect my SIM?
The listed Kernel version in 2.6.35.7-g790a33c [email protected] #1
Build number is 5.5.1_84_D3G-55
I haven't rooted it or anything, and just did a wipe from the bootloader but to no avail.
I haven't tried reflashing it with the Fast/easy unbrick technique, because I don't want to go messing with the device if I'm just going to have to return it.
So in brief, the questions are:
1. Is it likely a flash would fix this problem? Does anyone have any experience with this problem? (I did search, but none of the answers really covered it)
2. Does the fast/easy unbrick take it back to stock? If so, which stock - Verizon?
3. Can I do the fast/easy unbrick? It doesn't fix the thing to CDMA does it (there was no indication it does in the relevant thread, I'm just being paranoid).
Cheers,
Fighting disappointment

Hi
Sorry to hear that. I think your phone have radio problems.
Some time ago i have this type of problem when installing ICS or any other rom with the xt860 radio inside a stock verizon rom.
Do the easy unbrick method that you post to back to stock rom and radio.
And after that see that if the baseband, imei appear correct.
If the phone ask you the subsidy code the phone is not unlocked.
Try that and post it here.

FFU5y said:
Hi,
So in brief, the questions are:
1. Is it likely a flash would fix this problem? Does anyone have any experience with this problem? (I did search, but none of the answers really covered it)
2. Does the fast/easy unbrick take it back to stock? If so, which stock - Verizon?
3. Can I do the fast/easy unbrick? It doesn't fix the thing to CDMA does it (there was no indication it does in the relevant thread, I'm just being paranoid).
Cheers,
Fighting disappointment
Click to expand...
Click to collapse
1) try this http://forum.xda-developers.com/showthread.php?t=1406812
I heard it solves problems for those with an unlocked phone but cannot connect to GSM
2) Yes. To XT862 verizon 5.6.890
3) I don't see why not

Awesome, thanks guys.
I've decided to contact the seller and see what resolutions they offer before I go and do anything that may prevent me being able to return the phone.
With some luck (probably a lot of luck) they will permit me to reflash the phone to see if it fixes the problem, and still return the phone if it doesn't resolve the problem.
In that case, I'll post the results here so others can see what the outcome was.
Cheers.

Just an update: neither the unbrick method, not the XT883 radio.img fixed the problem, sadly.
Cheers for the help anyways.

Same Problem on brandnew Verizon XT862
Hi Guys,
I have the same problem here. I got a Droid3 from an american friend. Some keys didnt work lately. And as it was still under warranty, I did send it to him and he sent the exchanged new device back to me. So it's not activated or anything. May this be the problem? It does not even activate radio. No question for SIM, no SIM detected. No IMEI, no baseband version. Strange.
Is it possible to send it to motorola, so they "activate" it? I can't connect verizon from germany(infos?).
Maybe it could be done with radiocomm???
Would be glad about any help!

FFU5y said:
Just an update: neither the unbrick method, not the XT883 radio.img fixed the problem, sadly.
Cheers for the help anyways.
Click to expand...
Click to collapse
Find a solution? Im also from Australia and thinking of doing the same thing as u, i.e buying locked Verizon Droid 3 n unlocking
Sent from my NexusHD2 using Tapatalk 2

FFU5y said:
Hi,
I just recently bought (second hand, on eBay - that was my first mistake...) a Verizon Droid 3 (so presumably an XT862?). It is failing to connect to any network, and is not detecting my SIM card. I'm in Australia, so there is no CDMA network here (but GSM on 850, 900, and 2100; UMTS 850, 2100).
The peculiar thing is that the Baseband is 'unknown' in the phone 'About' screen. Likewise, the IMEI, IMEI SV, Network, MEID, MIN, ERI and PRL are unknown. I don't know how many of these relate to the network, but I can't imagine an 'unknown' baseband is a good thing.
The phone is ostensibly 'unlocked', but shouldn't it connect to networks for emergency calls? (which is doesn't), even if it is locked and so doesn't detect my SIM?
The listed Kernel version in 2.6.35.7-g790a33c [email protected] #1
Build number is 5.5.1_84_D3G-55
I haven't rooted it or anything, and just did a wipe from the bootloader but to no avail.
I haven't tried reflashing it with the Fast/easy unbrick technique, because I don't want to go messing with the device if I'm just going to have to return it.
So in brief, the questions are:
1. Is it likely a flash would fix this problem? Does anyone have any experience with this problem? (I did search, but none of the answers really covered it)
2. Does the fast/easy unbrick take it back to stock? If so, which stock - Verizon?
3. Can I do the fast/easy unbrick? It doesn't fix the thing to CDMA does it (there was no indication it does in the relevant thread, I'm just being paranoid).
Cheers,
Fighting disappointment
Click to expand...
Click to collapse
Read this, it worked for me.
http://forum.xda-developers.com/showthread.php?t=1686911

someone solve this problem?

I bought a new unlocked D3 from an online vendor who shipped it from Hong Kong.
I stuck in my Optus SIM and it just 'worked'.
I'm running hashcodes's CM10 on it at the moment.
So the phone is perfectly capable of working in Australia.
You might have to enable 'world mode' in the Wireless and Networks settings before it will talk to the SIM. It's been a while since i've run the 'stock' OS.
Just reassuring you the phone is capable of working down under - as mine does.

I am also having this problem and have tried many things to fix it, without luck. Anyone got a solution?

FIX MIN
Flash Verizon DROID 3 OTA 5.6.890 to phone_psouza4
GOOGLE THIS FILE AND DOWNLOAD. FIX MIN
JUST FASTBOOT
EXTRACT THE FOLDER
OPEN IT
ONE CLIC
LET ME KNOW

arnaldito said:
Flash Verizon DROID 3 OTA 5.6.890 to phone_psouza4
GOOGLE THIS FILE AND DOWNLOAD. FIX MIN
JUST FASTBOOT
EXTRACT THE FOLDER
OPEN IT
ONE CLIC
LET ME KNOW
Click to expand...
Click to collapse
Tried this and maaaany other potential fixes, with no luck :crying:

dinosaur swagg said:
I am also having this problem and have tried many things to fix it, without luck. Anyone got a solution?
Click to expand...
Click to collapse
I figured this out after having the problem several times the radio imei number is wrong even if you have did the *228 and ##PROGRAM with the correct info. I found that when you check the System IMEI with a 3rd party software it will shot something like 3112000xxxxxxxxxx or something of the sort. MTKdroidTools has the ability to let you correct this issue.

[HOWTO] / [GUIDE] SPH-L720 Domestic SIM Unlock T-Mobile:AT&T:metroPCS:Straighttalk

[HOWTO] / [GUIDE] SPH-L720 Domestic SIM Unlock T-Mobile:AT&T:metroPCS:Straighttalk
Streamlined Guide for Domestic T-Mobile GSM Unlock for SPH-L720
Credit for all of this goes to @autoprime and @nicotheandroidguy
A few notes: I used Windows 7 for the odin flashes , my phone is a SPH-L720 and it is not active on the Sprint network, also the sim card from t-mobile was inactive (brand new from t-mobile store.) and it has a bad esn. I am located in the Phoenix az market so I'm able to take advantage of the 1900mhz band that tmobile has here.
I'm unsure of how this will work with mnvos or other primary carriers and frankly I don't care at the moment, this is my primary phone. Update: confirmed hspa+ for tmobile, metroPCS, straight talk and AT&T.
I HAD MY NEW UNACTIVATED TMOBILE SIM CARD IN THIS ENTIRE TIME
1) First I reverted my rom to a stock MF9 rooted touchwiz rom, instructions and one click odin here:http://forum.xda-developers.com/showthread.php?t=2486134 I’m trying not to straight copy and paste someone else’s work so take a look at that post if you need a clean start. If you are coming from non stock you will need to boot into stock recovery and wipe data/cache before you get started. (I also later used SAC’s rom after a failed attempt at an AOKP fix and it worked as well ) you can switch to any ROM later and the unlock will stick.
2)I rebooted the phone and followed the instructions listed here in post #1 http://forum.xda-developers.com/showthread.php?t=2415587
3) I went to the dialer and typed *#0011# which brought me to the "service mode" Menu.
IF YOU HAVE TROUBLE GETTING THE HIDDEN MENU TO OPEN DO NOT FEAR! I had a ton of trouble at first. In some builds you need to activate an option by adding a line to your build.prop or changing the no flag in efs/hiddenmenu to ON. Google it, there is a ton of help out there.
4) Press the left menu softbutton (the menu button that lights up and vibrates when you touch it) then press the either the button “select” or “Key Input” and type the number 1 or 2 into the box, if nothing happens press menu and select the “back “ button then repeat. This app is sort of like a tin can radio, you can kind of tell that it’s working, but it doesn’t work well.
Depending on if you pressed 1 or 2 in the dialogue box it will take you into either an UMTS or CDMA menu. If you are in the umts menu, press the menu button and select back, this should then proceed to the next step.
5) Select CDMA, then 1.COMMON, press next page twice until you reach page three of COMMON and select 8.PREF MODE SET and select GSM_WCDMA_ONLY
6) Press menu and back until you are at the main menu and select [1]UMTS, then select [1]DEBUG SCREEN, then select [6]PHONE CONTROL, select [2]FAKE SECURITY CONTROL and make sure it is set to ON
7)Press menu and back and select [3] NAS CONTROL. We are going to check a few different settings in this menu so remember how to get here cause I don’t want to repeat myself.
[1] CIPHERING CONTROL = OFF
[2] INTEGRITY CONTROL =ON
[3] SIM CLASS CONTROL = UMTS
[4] REVISION CONTROL = DO NOT TOUCH
[5] RRC(HSPA) CONTROL = DO NOT TOUCH
[6] DUALMODE IMPROVEMENT CONTROL= DO NOT TOUCH
[7] NAS AVOID SECURITY CONTROL= OFF, 0
[8] BIP BLOCK = 1
8) Press menu and back twice, you should be on the PHONE CONTROL menu. Select [7] NETWORK CONTROL, select [1] GFC and make sure that it is set to [1]GSM/(E)GPRS/WCDMA REL8 .
9) Press menu and back and select [2] BAND SELECTION and select WCDMA/GSM ALL for both WCDMA and GSM band preferences. I selected the ALL choice for LTE as well even though I know it isn’t supported for TMOBILE.
10) Under the NETWORK CONTROL menu we just came from select [4] AQUISITION ORDER and change it to [3]UMTS_GSM
11) Press menu and back until you are in the PHONE CONTROL menu and select [5] SIMULATION , press the [2] SW WATCHDOG button 6(six) times and then the [3] HW WATCHDOG 6(six) times. Nothing will happen at all to let you know if you have done this correcctly but as soon as you finish the sixth press on HW WATCHDOG reboot the phone manually:manually:manually IMMEDIATELY . I’m not sure what this does or why this works but @nicotheandroidguy seems to have divined that this is the vital part of the process.
YOUR PHONE STILL WILL NOT HAVE DATA OR VOICE WHEN YOU REBOOT FROM THE WATCHDOG TAPS DO NOT PANIC!!!!!!!!!!! (hopefullly you have your towel with you)
12) WIFI that sonofa up and search for apn settings shortcut and build.prop editor in the Play Store.
Go into the build.prop editor and add the following two lines:
ril.sales_code=LOL
ro.csc.sales_code=LOL
REBOOT PHONE MANUALLY now.
Now Install and create a shortcut on the home screen and select to open. Press the menu soft key and select add apn.
Use:
Name: T-Mobile
APN: epc.tmobile.com or fast.t-mobile.com (for LTE devices)
Proxy:
Port:
Username:
Password:
Server:
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS proxy:
MMS port:
MMS protocol: WAP 2.0
MCC: 310
MNC: 260
Authentication type:
APN type: default,supl,admin,dun,mms
13) Go into your android settings, select wireless networks, you should see the network mode set as wcdma only do not change this, we set this in the Service Mode Menu , Check that your roaming settings are set to for roaming data/ international data etc.also make sure that there are no roaming guards left on. (roaming guards will only allow you to uncheck GSM and GSM data under international roaming.)
14) reboot
15) profit
At this point I had full access to the TMOBILE UMTS/HSPA+ network and voice/text/mms were working.
At this point you may change roms, be careful not to update past mf9 as you may be unable to downgrade to mdc. YOU MUST DOWNGRADE TO MDC MODEM FOR THIS TO WORK.
If you use a non touchwiz rom you can still access the tellinfo menu by pressing *#*#4636#*#* and selecting WCDMA only and manually adding the apn.
GOOD LUCK! let me know what needs changed in the guide as well.
If you have questions it's useful to know your Baseband /kernel/ rom.

Nice. Will it work with t-mobile in Los Angeles?
Sent from my SPH-L720 using XDA Premium 4 mobile app

Thank you for this thread, I will try again with these steps.
A few notes:
imbmiller said:
3) i went to the dialer and typed *##0011# which brought me to the "service mode" menu.
Click to expand...
Click to collapse
This should be *#0011# I believe
imbmiller said:
5) Select CDMA, then 1.COMMON, press next page until page three of COMMON and select 8.PREF MODE SET and selet GSM_WCDMA_ONLY
Click to expand...
Click to collapse
I had to go 9. NEXT PAGE > twice before doing 8.

gibrannz said:
Nice. Will it work with t-mobile in Los Angeles?
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
According to this :https://t-mobile.jive-mobile.com/#jive-document?content=/api/core/v2/documents/5736
Yes it will. Hspa+ only though.
the.joeba said:
Thank you for this thread, I will try again with these steps.
A few notes:
This should be *#0011# I believe
I had to go 9. NEXT PAGE > twice before doing 8.
Click to expand...
Click to collapse
Np Man, and good catch, fixed. I'll check out that step 8/9 and fix accordingly.

Thank you so very much. I believe opening up the bands made the difference, but I'm now connected to T-Mobile.
You rock so much!

the.joeba said:
Thank you so very much. I believe opening up the bands made the difference, but I'm now connected to T-Mobile.
You rock so much!
Click to expand...
Click to collapse
HELL YEAH MAN! I'm stoked that you were able to get it working. I pulled most of this info from the other threads but I'm glad if it made it easier.

got working for att post paid
Thanks to everyone here.

ka26 said:
Thanks to everyone here.
Click to expand...
Click to collapse
Most excellent! If you fiddle with acquisition order and make it gsm_umts it might identify your network type correctly.

My 1st newbie post:
Thanks for OP's excellent post!:good:
I have a Sprint Galaxy S4 is with stock MF9 (not unlocked).
I have spent days reading about how to get a rooted/unlocked MJA S4. But still could not find answer to the questions:
1. Will this also unlock international sim?
I guess yes, as domestic is harder to unlock. But want to hear the confirmation.
2. You mentioned you used MF9 rooted.
If I unlock it, then update to MJA, will that void the unlock?
3. Does this unlock works with MJA? If it works, do I need to unlock MJA first?
4. If I want a rooted & unlocked S4 with stock MJA, what is the simplest way and the correct order to achieve this goal?
Can I update to MJA, then root, then unlock?
Or do I need to root the MF9, then unlock, then update to MJA, then root?
If I update to MJA first, I can't go back to MF9, correct?
Thank you very much!
staplestaples

staplestaples said:
My 1st newbie post:
Thanks for OP's excellent post!:good:
I have a Sprint Galaxy S4 is with stock MF9 (not unlocked).
I have spent days reading about how to update to MJA and root/unlock it.
But still could not find answer to the questions:
1. Will this also unlock international sim?
I guess yes, as domestic is harder to unlock. But want to hear the confirmation.
2. You mentioned you used MF9 rooted.
If I unlock it, then update to MJA, will that void the unlock?
3. Does this unlock works with MJA? If it works, do I need to unlock MJA first?
4. If I want a rooted & unlocked S4 with stock MJA, what is the simplest way and the correct order to achieve this goal?
Can I update to MJA, then root, then unlock
Do I need to root the MF9, then unlock, then update to MJA, then root?
Thank you very much!
staplestaples
Click to expand...
Click to collapse
Ok
1)i am unsure of whether mja can be unlocked internationally or domestic . If you read the first direction it actually instructs you to downgrade to mdc modem. I'm pretty sure the reason has to do with the options available to you in the hidden menu.
2)i used mf9 rooted as a starting point to downgrade to mdc to perform the international unlock. Autoprime said in the thread that upgrading to mf9 would keep the u lock however I haven't successfully upgraded to mf9 and kept the domestic unlock. I'm going to try to get it to work today but not with mja until there is a reliable downgrade option.
3)i have no idea. I wouldn't suggest trying until there is a reliable downgrade option.
4)i would really slow down and read the international unlock guide from @autoprime I think it will answer a lot of your questions. Like I said I would wait to upgrade to mja if you want a for sure domestic Sim unlockunlock.

Thank you very much, imbmiller.
I will just wait patiently for the MJA solutions before upgrading to MJA/root/unlock.
imbmiller said:
Ok
1)i am unsure of whether mja can be unlocked internationally or domestic . If you read the first direction it actually instructs you to downgrade to mdc modem. I'm pretty sure the reason has to do with the options available to you in the hidden menu.
2)i used mf9 rooted as a starting point to downgrade to mdc to perform the international unlock. Autoprime said in the thread that upgrading to mf9 would keep the u lock however I haven't successfully upgraded to mf9 and kept the domestic unlock. I'm going to try to get it to work today but not with mja until there is a reliable downgrade option.
3)i have no idea. I wouldn't suggest trying until there is a reliable downgrade option.
4)i would really slow down and read the international unlock guide from @autoprime I think it will answer a lot of your questions. Like I said I would wait to upgrade to mja if you want a for sure domestic Sim unlockunlock.
Click to expand...
Click to collapse

So would this also work for AT&T sim? has anyone else tried? Btw, was thinking of updating to 4.3 and MJA but i guess i will have to hold off on that if i want sim unlock international or domestic? I am on MF9 with sim international unlock right now. Would I have to go down to MDC to get this to work?
Also, if you want to go back to sprint again, how would you do it?

wildpig1234 said:
So would this also work for AT&T sim? has anyone else tried? Btw, was thinking of updating to 4.3 and MJA but i guess i will have to hold off on that if i want sim unlock international or domestic? I am on MF9 with sim international unlock right now. Would I have to go down to MDC to get this to work?
Also, if you want to go back to sprint again, how would you do it?
Click to expand...
Click to collapse
You can use MF9, MDL and MDC for the domestic unlock.
Sent from my Nexus 4 using XDA Premium 4 mobile app

Hi thanks so much for putting this together all in one place!
Hi I'm on MF9, rooted, locked.
So really the two major steps are:
1. Do int'l unlock first (autoprime)
2. Then do domestic unlock
My question - after you get both unlocks working and say you have your phone working on tmobile, what do you need to do to get it working on Sprint... rather, is the phone operatable on both Sprint and Tmobile? Or do you have to do some tinkering to get it back to working on Sprint again. I'd like to have the flexibility of popping SIMs in and out and switching carriers at will, Sprint included (b/c I don't want to cancel Sprint just yet...eventually, but not immediately). Thanks!
---------- Post added at 09:59 AM ---------- Previous post was at 09:53 AM ----------
Another question
When you're tinkering with swapping out modems and APN settings, does doing a nandroid backup prior help so when you have an "oh sh!t" moment, you can just do a full restore...? Or is what's backed up in nandroid outside (excludes) these changes? Thanks.

laoh said:
Hi thanks so much for putting this together all in one place!
Hi I'm on MF9, rooted, locked.
So really the two major steps are:
1. Do int'l unlock first (autoprime)
2. Then do domestic unlock
My question - after you get both unlocks working and say you have your phone working on tmobile, what do you need to do to get it working on Sprint... rather, is the phone operatable on both Sprint and Tmobile? Or do you have to do some tinkering to get it back to working on Sprint again. I'd like to have the flexibility of popping SIMs in and out and switching carriers at will, Sprint included (b/c I don't want to cancel Sprint just yet...eventually, but not immediately). Thanks!
---------- Post added at 09:59 AM ---------- Previous post was at 09:53 AM ----------
Another question
When you're tinkering with swapping out modems and APN settings, does doing a nandroid backup prior help so when you have an "oh sh!t" moment, you can just do a full restore...? Or is what's backed up in nandroid outside (excludes) these changes? Thanks.
Click to expand...
Click to collapse
OK the answer to the first question is to put your sprint sim card back in then put your phone back in to lte/cdma auto through the tell info app through Google play device info then change it in to lte/cdma auto.
Answer to the second question is that the nandroid might help you in a oh sh!t moment but the modem and settings for the unlock stay after a factory rest but a other update could kill it. A stock Odin flash and dailing ##72786# could also kill both unlocks.
Sent from my Nexus 4 using XDA Premium 4 mobile app

Someone on this thread got it to work. I'm unsure if Att has hspa+ tho so you might be relegated to edge

Nevermind, it works on Metro it just matters the SIM http://forum.xda-developers.com/showpost.php?p=47624568&postcount=568

Did you install hiapn and add the apn? What baseband are you on? What rom and kernel? I'm not super positive about mvno s but I'd probly go back to the beginning and start over.

imbmiller said:
Did you install hiapn and add the apn? What baseband are you on? What rom and kernel? I'm not super positive about mvno s but I'd probly go back to the beginning and start over.
Click to expand...
Click to collapse
Sorry I had to edit my post. It did work. There are two different GSM SIMs the one with the dot seemed to work. I Got Edge, 3G, and H+. It is awesome. I also still have 3G with Sprint with the SIM in. I got two phones in one. Thanks.

So I've been on T-Mobile for the last 24 hours but my HSPA+ signal is weak and slow (under 1mb), while my co-worker on T-Mobile (and a T-Mobile phone) has full HSPA+ signal and speed (5-9mb).
Any thoughts on what could be the cause?
I'm running CM11 on MDC. I'll try some other combinations tonight to see if things change.

How should I downgrade or enable GSM/WCDMA option on Sprint LG G4 LS991?

Hey, guys this is my first post here on XDA so please apologize me for any inconvenience.
I bought LG G4 Sprint i.e., LS991 yesterday from someone else I don't have contact with him now. The sim card which works on 3G was working fine when I bought it. But, then I tried to go in settings and then to mobile network and I opened the list of network bands and unfortunately I was only able to find only two option that are 1. CDMA/LTE and 2. CDMA.
I was forced to select one from it and boom no signals at all and status says searching for service. Where is the GSM option? I'm sure that this phone is already unlocked and it is from Sprint.
Also, I'm on the latest software version that is LS991ZVD. Can I go back to ZV6 International ROM or will it brick my device?!

emad26 said:
Hey, guys this is my first post here on XDA so please apologize me for any inconvenience.
I bought LG G4 Sprint i.e., LS991 yesterday from someone else I don't have contact with him now. The sim card which works on 3G was working fine when I bought it. But, then I tried to go in settings and then to mobile network and I opened the list of network bands and unfortunately I was only able to find only two option that are 1. CDMA/LTE and 2. CDMA.
I was forced to select one from it and boom no signals at all and status says searching for service. Where is the GSM option? I'm sure that this phone is already unlocked and it is from Sprint.
Also, I'm on the latest software version that is LS991ZVD. Can I go back to ZV6 International ROM or will it brick my device?!
Click to expand...
Click to collapse
Bro, I found this on this site:
1. go to settings and add new APN manually (fill the values according to your carrier).
2. in the APN type input "default,dun,fota".
3 .save.
4. Restart phone and you are good to go.
Works like a charm... The signal loss thing happened to me too. Don't select either option after you fix it. Go to backup and reset and reset your network settings. I think this is what I did to solve the problem.

emad26 said:
Hey, guys this is my first post here on XDA so please apologize me for any inconvenience.
I bought LG G4 Sprint i.e., LS991 yesterday from someone else I don't have contact with him now. The sim card which works on 3G was working fine when I bought it. But, then I tried to go in settings and then to mobile network and I opened the list of network bands and unfortunately I was only able to find only two option that are 1. CDMA/LTE and 2. CDMA.
I was forced to select one from it and boom no signals at all and status says searching for service. Where is the GSM option? I'm sure that this phone is already unlocked and it is from Sprint.
Also, I'm on the latest software version that is LS991ZVD. Can I go back to ZV6 International ROM or will it brick my device?!
Click to expand...
Click to collapse
you cannot downgrade has antirollback yuo will brick possibly hardbrick.
i dont know the method but i believe there is possibility even without root but dont quote me on tht
as mine has managed to stay on zv6 since day one

attempting to permanently enable band 28 on tencent+WW rom?

Band 28 can be force enabled via Network Signal Guru and works, but it does not persist upon exiting the app.
Is there any method to do so permanently?

So far:
1) "EfsTools.exe setModemConfig -p lte.json" does not work with either the WW or CN+b28 configs.
2) QPST 2.7 does not read the modem configs properly
3) QXDM does not read the LTE files, returns an error. Also the newest version on xda appears to be from 2009.
4) DFS tools fails to do anything. It reads all bands as active and setting bands to write didnt do anything
5) network signal guru settings do not persist upon exiting the app, but can be used to temporarily enable b28 for testing purposes. For best results, disable all other LTE bands.
6) /policyman/ files do not contain anything pending to band28, using "<include> 28 </include>" in carrier_policy_original.xml_Subscription01 does nothing.
7) band 28 is apparently enabled by default on SIM2 (thanks @attachsnow ), but this is incompatible with homerSP's VoLTE/VoWi-FI guide???
I suspect there's a hidden file that temporarily overwrites the main config files every boot, bit i lack the skill to find out. Either that, or SIM1 has some special configs or hardware issues with B28 that SIM2 does not

Have the same problem here. I found that sim 2 can use band 28 but not in sim 1.
Could you share more information for this?
Maybe we can found some files in vendor folder that is the same as country value.

attachsnow said:
Have the same problem here. I found that sim 2 can use band 28 but not in sim 1.
Could you share more information for this?
Maybe we can found some files in vendor folder that is the same as country value.
Click to expand...
Click to collapse
I'm no android developer, just a "power user" at best. I merely tested every guide for enabling VoLTE or bands for any android phone on xda I could find. I wouldn't have the skill to make up a new method.
Band 28 is detected on SIM2 without needing network guru app's lock, but i cannot get the VoLTE guide to work with it. Guess it's still something, maybe we can force volte on sim2.

I've tried a bunch of things to enable bands myself, including band 28, but I have yet to find a solution - anything I do just seems to revert when rebooting and I have no clue what causes that.
I have updated EfsTools to allow writing the settings for the second SIM, you can find it here: https://github.com/HomerSp/EfsTools/releases/tag/0.10-modded-1.2.
Simply download that, and run this, and you should be good to go on the second SIM slot (no need to re-run the other commands):
Code:
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -s 1

Now I'm wondering what restrictions are on SIM2 as it appears to only detect 3g b5 and 4g b28? I will test a bit further

deltarz said:
Now I'm wondering what restrictions are on SIM2 as it appears to only detect 3g b5 and 4g b28? I will test a bit further
Click to expand...
Click to collapse
Seems to work fine here, though I get the same exact bands enabled as I do on SIM1, so there's sadly no difference there.

Small update: I'm not entirely sure we can completely trust the list of LTE bands listed Network Signal guru. I say this because toggling the bands there doesn't seem to do anything, but more importantly, I modified /policyman/carrier_policy.xml and removed the LTE band I'm usually connected to (B1) and rebooted. After booting again it would no longer connect to LTE, but this wasn't reflected at all in Network Signal Guru - it still had all bands except 28 ticked.
As a test you could try writing this to efs:
https://gist.github.com/dc57c830fef5a0690709b3a95842bafa
Code:
EfsTools.exe writeFile -i carrier_policy.xml -o /policyman/carrier_policy.xml
That will disable all bands except B28. My carrier doesn't support that band, so I can't check if it works myself.
Here's the stock carrier_policy.xml if you want to restore it after testing:
https://gist.github.com/cb4cd5114013add0432eeb1afdc26ce9

HomerSp said:
Small update: I'm not entirely sure we can completely trust the list of LTE bands listed Network Signal guru. I say this because toggling the bands there doesn't seem to do anything, but more importantly, I modified /policyman/carrier_policy.xml and removed the LTE band I'm usually connected to (B1) and rebooted. After booting again it would no longer connect to LTE, but this wasn't reflected at all in Network Signal Guru - it still had all bands except 28 ticked.
As a test you could try writing this to efs:
https://gist.github.com/dc57c830fef5a0690709b3a95842bafa
Code:
EfsTools.exe writeFile -i carrier_policy.xml -o /policyman/carrier_policy.xml
That will disable all bands except B28. My carrier doesn't support that band, so I can't check if it works myself.
Here's the stock carrier_policy.xml if you want to restore it after testing:
https://gist.github.com/cb4cd5114013add0432eeb1afdc26ce9
Click to expand...
Click to collapse
I agree. Well, it's not that important anymore but, Network Signal Guru's bands do not apply to SIM2. It still shows B28 as disabled. Forcing toggles do nothing to anything in SIM2 besides forcing a reconnect on both SIMs. That and how the bands never persist upon exiting the app for SIM1 does imply that it can't be trusted whenever things are changed.
Anyway, I can connect to b 3,5,7 & 28 for 4G just fine, which is all of Telstra. They do have some rare b1 & b8 sites but I don't know where they are to test that. However, I would assume they work. 3G is harder to test as they only use B3.
If you need any further testing on B28 matters, let me know.
For now, the SIM2 workaround is good enough. Highly doubt there'll come a time where the SIM2 slot dies before anything else breaks or the phone is replaced, or the situational requirement of two B28 SIMs.

If we use Network Signal guru to check B28 only on sim 1 slot, use NetMonster app that it shows B28 is connected.
But there is no CA with B28. So it has a little difference with sim 2 slot.

Is there any update?

If I root my phone, will network guru open band 20 on my UK version phone?

On kimovil site they say the tencent ultimate version (512gb/12gb) ram has all bands, including 28 and MiMO 4x4. Anyone can confirm this, please? Thanks in advance! ROG Phone 2 512gb/12gb on Kimovil

Had B28 working with WW rom on Tencent phone in second sim slot. Now updated to Android 10 second slot fix is broken, that band is gone now.
I fastboot back to Android 9 with raw rom and that didn't bring back b28. Have no idea where to go from here, I was relieved to finally have 4G where I live.

onlyadequate said:
Had B28 working with WW rom on Tencent phone in second sim slot. Now updated to Android 10 second slot fix is broken, that band is gone now.
I fastboot back to Android 9 with raw rom and that didn't bring back b28. Have no idea where to go from here, I was relieved to finally have 4G where I live.
Click to expand...
Click to collapse
Yes, I found that android 10 will let second slot missing Band 28. Could you share your flash back android 9 method? Are you using one raw file or 21 img file? Thank you.

attachsnow said:
Yes, I found that android 10 will let second slot missing Band 28. Could you share your flash back android 9 method? Are you using one raw file or 21 img file? Thank you.
Click to expand...
Click to collapse
Went to this thread and downloaded the first WW raw https://forum.xda-developers.com/rog-phone-2/how-to/1910-64-ww-update-t4021947 put phone into fastboot mode, flashall_AFT.cmd back to Android 9. Note that my bootloader is locked, but from looking around it seemed like I didn't need to unlock it to roll back.
Sorry don't know what 21 image file is, I'm new to this stuff.

onlyadequate said:
Went to this thread and downloaded the first WW raw https://forum.xda-developers.com/rog-phone-2/how-to/1910-64-ww-update-t4021947 put phone into fastboot mode, flashall_AFT.cmd back to Android 9. Note that my bootloader is locked, but from looking around it seemed like I didn't need to unlock it to roll back.
Sorry don't know what 21 image file is, I'm new to this stuff.
Click to expand...
Click to collapse
Could you please provide fastboot.log file after you rollback?
Maybe we could see which file cannot flash back.

attachsnow said:
Could you please provide fastboot.log file after you rollback?
Maybe we could see which file cannot flash back.
Click to expand...
Click to collapse
Here's the log file
https://pastebin.com/acCDD66i

onlyadequate said:
Here's the log file
https://pastebin.com/acCDD66i
Click to expand...
Click to collapse
Hi, just a guess. Have you ever try flash CN android 9 Rom again then flash back to WW?

attachsnow said:
Hi, just a guess. Have you ever try flash CN android 9 Rom again then flash back to WW?
Click to expand...
Click to collapse
I've thought about flashing back to cn, but haven't done it yet. Use a different phone now but I'll try your idea sometime