Database Users

[GUIDE] Galaxy Tab Network Unlock

**UPDATE**
This method causes your serial number to change to 00000000 (which isn't a problem as such as this isn't currently used for anything) but there is a new method which involves directly hex editing the nv_data.bin file, which may be faster and does not change your serial number. You can find the details here: http://forum.xda-developers.com/showthread.php?t=843323.
**UPDATE**
First up I'll say that I'm not incredibly familiar with Galaxy S firmware changes/modding, and this mostly builds on work done in these areas, so not all these steps may be necessary but they worked for me. If someone can suggest a faster way to do this/unnecessary steps then please go ahead and reply with them!
This unlocked my Network Locked Australian Galaxy Tab and so I assume should work for others.
You should back up your /efs/ folder before you proceed as you may need this to undo if something goes wrong.
*I take no responsibility if something goes wrong!*
Requirements:
Root access
repair_nv_data.zip (from http://forum.xda-developers.com/showpost.php?p=8942669&postcount=94)
Java
Busybox
The Android SDK for ADB, Root Explorer or some similar file system explorer/editor
(If you have US firmware with no Phone software, you may need to flash European firmware as described here: http://forum.xda-developers.com/showthread.php?t=838250 ).
Firstly, on your phone dial *#7465625# and check if the Network Lock is set to [ON], if so then your phone is locked (duh), so continue.
1. Use Superoneclick (http://forum.xda-developers.com/showthread.php?t=812367) to root your phone (the other z4root method may work as well, but this isn't what I used).
2. Either use ADB or some other method to rename or delete (backup first):
/efs/nv_data.bin.md5
/efs/.nv_data.bak
/efs/.nv_data.bak.md5
(I just used Root Explorer to rename them to something else).
3. Restart your phone and then go into the /efs/ directory and see if the 'nv_data.bin.md5' file has been re-created by your phone, as long as it has been created then you can proceed.
4. Go to http://forum.xda-developers.com/showpost.php?p=8942669&postcount=94 and download the repair_nv_data.zip file (the credit for all of this mostly goes to that thread and helroz).
5. Install 'busybox' from the Market. Once you install it, you actually have to run it and properly install it (the Market app is basically an installer) - the files in the above zip have a dependency on this.
6. Extract the above zip to your PC, plug in your Tab in USB debugging mode. Run the Step 2.bat from the extracted file. You may need to allow the script super user access several times. This should copy the /efs/ and a bunch of files into a directory with a french name.
7. Run the Reparation_nv_data.jar file. (You will need Java for this step.) It will prompt you to enter two numbers, which are your pseudo-unlock codes. I entered '11111111' and '11111111' (eight 1's) both times. This rewrites the nv_data.bin file to be simunlocked with these details.
8. Run the Step 4.bat. Your superuser app (the one installed when you rooted using SuperOneClick) will need you to allow each command to have root access so keep an eye on your Tab. You may need to press y/n a few times if you encounter errors. This is uploading the edited nv_data.bin onto your Tab.
This batch file will stop several times and need you to hit a key when it pauses. My Tab rebooted halfway through this batch file - when it did this I waited for it to fully reboot back to the lock screen before pressing a key to make the script continued while the Tab was actually able to respond to its commands.
9. Towards the end of its execution it rebooted a second time. It paused during loading up and had some yellow writing on the screen saying it was updating media (I assume it was rebuilding the nv_data.bin). Leave it for a minute and it will prompt you to reboot/some other options. Just press whatever it wants (home I think) to reboot the phone - you don't want any of the other recovery options.
10. Go into your dialer and put in *#7465625# again and (hopefully) voila! Your phone should no longer be network locked. Try a SIM from a different provider to make sure.
Enjoy!
Edit: I had to go out and actually buy a prepaid SIM to confirm that all was working with a different provider. Attached are screen caps of my Tab on two different networks, as well as the network status screen, making/receiving calls etc. all works on both.

Awesome man, thanks.
This is much better than the 2 month wait we had for Galaxy S unlocking.

Hello, I'm french and i use your post to unlock my Galaxy TAB SFR ''réunion island'' and she is unlock thanks for your AMAZING post for unlock TAB
Ps: For unlock my TAB by SFR REUNION, he tell me 150 Euros.... Vive smithdc & helroz

Works well! I had little trouble running java on windows7. But changing compatibility mode to windowsxp sp3 and check run this program as an administrator solved the problem.
Thanks for easy guide!

tacoda, you mean for running the .jar file? or for installing Java itself? (I assume the former).

Sweeet thx , curious if unlocking the AT&T version has hardware only set to AT&Ts 3G frequencies, so 3g wont work on tmobile or is it capable of running 3g on tmobile with a unlocked AT&T tab?

smithdc said:
tacoda, you mean for running the .jar file? or for installing Java itself? (I assume the former).
Click to expand...
Click to collapse
Running the jar file. I didnt know how to run it.
Sent from my SGH-T959 using XDA App

Does the sim card and/or sd card should or should not be plugged in during the unlocking progress?

It shouldn't make a difference Zeron.Wong.

jay_jay_n said:
Sweeet thx , curious if unlocking the AT&T version has hardware only set to AT&Ts 3G frequencies, so 3g wont work on tmobile or is it capable of running 3g on tmobile with a unlocked AT&T tab?
Click to expand...
Click to collapse
Traditionally, AT&T and T-Mobile hardware used different radios, it was more than just firmware. That's also true on the little brother Galaxy S series, the Vibrant has a different radio than the Captivate (though the Vibrant radio DOES have 1900 band in the hardware, for some reason).

Kudos to smithdc for this awesome guide! I saved a lot of money thanks to him. Congrats again.

Bump, is there any way to sticky/pin this for people?

So your saying if I use this method and install my tmous unlimited sim I can get calls and 3g or do I need a prepaid sim

I'm not sure on how T-Mobile are blocking, but if it IS my IMEI then you would have to use a SIM from a different network.
If they are blocking your IMEI on their network, then you would have to use a SIM from a different network (as a different network, wouldn't be blocking this IMEI number). Changing it to a different SIM on the same network won't help as your IMEI is for the device itself.

I just want to clarify something..
I have a T Mobile Tab and want to use a SIM I have for ATT.
Will I have to flash my device with the EU firmware first in order to get the phone software on it..then do the rest of the unlocking steps?
Assuming thats correct..after unlocking it I then can put my ATT sim card in and it should work for calls and data (Edge only) with not having to tweak any setting at all? Or do I have to set up my wap.cingular connections for the data like on a WM phone on ATT?
And if I want to get back to original out-of-the-box firmware from T Mobile (like if I had to send it in for repair) I just have to flash stock T Mobile firmware and its back completely to original?
Thanks..and wow am I loving this TAB !!!

You'll need to set up your APN data for AT&T, yes.

Thanks for the fast reply. As for the flashing of the EU rom..is that the only/best way so far in order for me T Mobile Tab to get the radio software on it. I was thinking I saw an APK for the radio software someplace but did not know what way was better.
I just want to be 100% sure bfr I take the jump to unlocking and playing with the phone part
thanks

I got a quick couple of questions:
1. If I restore original firmware (Canadian), does it relock my phone?
2. Where can I get the Canadian firmware release? I see EURO and US, but no Canadian.

I read on one of the other threads that sim unlock method also changes your imei number. Is this really case?

clubtech said:
I read on one of the other threads that sim unlock method also changes your imei number. Is this really case?
Click to expand...
Click to collapse
Yes, it will set your IMEI to a bogus one that will get your T-Mobile internet access disabled after 1/2 hour.

[Guide] Update any Motorola Charm to lates T-Mobile firmware (Working 2G / 3G)

Hey Guys,
The Admins decided to basically add the Charm forums into the Flipout forums, so far only the main forum heading has been changed, hopefully the admins will do the rest of the changes soon.
In the meanwhile, i thought it would be useful to post useful threads on the charm porting, basically since flipout and charm are the same phone with a different design, these should be applicable with respective changes to flipout also.
[Guide] Update any Motorola Charm to lates T-Mobile firmware (Working 2G / 3G)
Author : victory144
Thread : http://forum.xda-developers.com/showthread.php?t=1384837
Content :
victory144 said:
[URL="http://support.t-mobile.com/docs/DOC-1741"]List of improvements, from T-Mobile Documentation.
[/URL]
I AM NOT RESPONSIBLE FOR ANY DAMAGE THAT THIS GUIDE MAY CAUSE. TESTED AND WORKING. FOLLOW AT YOUR OWN RISK!
Warning: Flashing T-Mobile sbf will update the Bootloader, so cant downgrade or flash other sbf.
This guide is for update any Motorola Charm w/o brand to the latest T-Mobile update with fully working 2G/3G network, and get many improvements (Best of all Stability and Battery).
If you have official US T-Mobile Charm you don't need this. as it can be updated normally.
Requirements:
* Any sbf file that currently work (2G/3G) with the corresponding Mobile Providers Link.
* T-Mobile 03.90.7 BLUR firmware sbf file. Link from the Wiki.
* RSD Lite 4.6 Link from the Wiki.
* Moto Android Depacker Link.
* SuperOneClick for Root Internal link.
* Root explorer NO LINK! (Or via ADB).
Click to expand...
Click to collapse
Guide:
A- Backup from the running firmware.
1. Root the phone (any method).
2. Install Root Explorer (alternatively can use ADB or terminal emulator).
3. Backup this folder and save a copy in the computer. "etc\motorola\bp_nvm_default".
Click to expand...
Click to collapse
B- Extract BP from the sbf (That currently work with your 2g/3g network).
1. Open Motorola Android Depacker --> Open From File -->Browse the sbf
2. Click "Split To Folder" this will generate a folder with the same name of the sbf.
3. Remove all split files except this one "CG45.smg" (BP Firmware file).
Click to expand...
Click to collapse
C- Mod T-Mobile sbf.
1. Open Motorola Android Depacker --> Open From File -->Browse the sbf (T-Mobile one).
2. Click "Split To Folder" --> browse to the splitted folder.
3. Replace and overwrite the "CG45.smg" with the one from B.
4. Open Motorola Android Depacker --> "Open File Folder" --> Browse T-Mobile split folder.
5. Click on "Compile File" this will generate "firmware.sbf" with BP that work with the phone.
Click to expand...
Click to collapse
D- Install T-Mobile Mod sbf.
1. Backup any needed phone data.
2. Install and open RSD Lite --> Click on "..." --> Browse to "firmware.sbf"
3. Connect the phone to the computer.
4. Wait until phone show as connected in the RSD Lite--> click "Start".
5. Wait until RSD Lite finish. --> Configure "Moto blur" account.
Optional: It's possible to restore "clockworkmod" backup using polovinamozga's Bootstrapped Recovery.
http://forum.xda-developers.com/showpost.php?p=14796425&postcount=412
Click to expand...
Click to collapse
E- Restore network.
1. Root the phone (using SuperOneClick).
2. Install Root Explorer.
3. Copy this folder from step "A" to the SD Card "bp_nvm_default".
4. open Root Explorer --> Navigate to "sdcard" --> navigate to "bp_nvm_default" folder.
5. "Multi-select" these files:
File_Audio
File_Audio2
File_GSM
File_Seem_Flex_Tables
generic_pds_init
Click to expand...
Click to collapse
6. Then press "Copy" --> Navigate to "etc\motorola\bp_nvm_default" --> "Mount RW".
7. Paste --> Overwrite all the files.
8. IMPORTANT Select all copied files (from step E-5) and change permission to rw-r--r--.
9. Reboot phone...Then add the APN of the corresponding network provider.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Credit for all Tools Creator.
Sorry about any grammatical/spell English error.
Click to expand...
Click to collapse
Credits to the respective author and aforementioned credits.

Thanks for the clear guide. Had a lot of difficulty with this back a year or two ago when I first got my Charm.
Does anyone know if the T-Mo (1700/2100) and 850/1900/2100 Charms have any hardware differences? Or is the 3G bands support purely in software?
I'm actually wondering if it's possible to do the opposite of this guide. That is, flash my existing deblur SBF, but with the T-Mobile BP files, to convert my Telus Charm into one that works on T-Mobile/Wind/Mobilicity.

ergosteur said:
Thanks for the clear guide. Had a lot of difficulty with this back a year or two ago when I first got my Charm.
Does anyone know if the T-Mo (1700/2100) and 850/1900/2100 Charms have any hardware differences? Or is the 3G bands support purely in software?
I'm actually wondering if it's possible to do the opposite of this guide. That is, flash my existing deblur SBF, but with the T-Mobile BP files, to convert my Telus Charm into one that works on T-Mobile/Wind/Mobilicity.
Click to expand...
Click to collapse
yes you can but you will have to download telus sbf and T-mobile sbf, then replace firmware of t-mo sbf with that of the telus then copy bp files from telus to t mo, its given in the guide.
but after flashing t-mo ROM you can flash any other sbf other than. t mo as the bootloader gets updated.
but you could try the reverse to obtain a telus ROm working on T mo. Don't have either of these, so can't test it out also.

Cool, thanks. Will try it and report back.
Sent from my Galaxy Nexus using xda premium

Link to the sbf file is dead.

So this is supposed to enable 3g internet connection as well?.. i did everything and managed to use 2g and 3g to calls and sms.. but i cant see the internet connection option..

eetu1923 said:
So this is supposed to enable 3g internet connection as well?.. i did everything and managed to use 2g and 3g to calls and sms.. but i cant see the internet connection option..
Click to expand...
Click to collapse
You'll need to update the apn settings for your carrier. Look around on the forums or search web, there are instructions. Your carrier's website could be helpful too, for example Bell Mobility (Canada): http://support.bell.ca/Mobility/Sma..._Nexus_One_for_the_Bell_Mobility_HSPA_network

ergosteur said:
You'll need to update the apn settings for your carrier. Look around on the forums or search web, there are instructions. Your carrier's website could be helpful too, for example Bell Mobility (Canada): http://support.bell.ca/Mobility/Sma..._Nexus_One_for_the_Bell_Mobility_HSPA_network
Click to expand...
Click to collapse
Well my Carrier is Telcel in Mexico, but i have already created the APN settings for it.. but thers no option to turn on the data services... in some other forum they told me that the baseband frecuencies arent compatible and the only way of getting my 3g data back is to restore the device to the original LATAM firmware.. which i guess im not able to do since i cant go back from the TMOBILE bootloader..
PLease tell me im wrong and that there is a way of doing this..
Im gbuessing maybe sending it to motorola and they could do some magic?...

eetu1923 said:
Well my Carrier is Telcel in Mexico, but i have already created the APN settings for it.. but thers no option to turn on the data services... in some other forum they told me that the baseband frecuencies arent compatible and the only way of getting my 3g data back is to restore the device to the original LATAM firmware.. which i guess im not able to do since i cant go back from the TMOBILE bootloader..
PLease tell me im wrong and that there is a way of doing this..
Im gbuessing maybe sending it to motorola and they could do some magic?...
Click to expand...
Click to collapse
Hmm, weird, so you copied the bp_nvm_default files as above, and your 3G is working for calls but not for data?
Maybe try re-flashing the ROM?
I have a Charm that was originally on Telus (Canada), they use the same frequencies as Telcel (850/1900) for HSPA. Flashed the T-Mobile sbf and lost 3G, but replacing the bp_nvm_default files made the 3G work with Telus again. Took a couple of tries though - it's a bit finicky. Had to re-flash T-Mobile ROM a couple of times before the mod worked.

ergosteur said:
Hmm, weird, so you copied the bp_nvm_default files as above, and your 3G is working for calls but not for data?
Maybe try re-flashing the ROM?
I have a Charm that was originally on Telus (Canada), they use the same frequencies as Telcel (850/1900) for HSPA. Flashed the T-Mobile sbf and lost 3G, but replacing the bp_nvm_default files made the 3G work with Telus again. Took a couple of tries though - it's a bit finicky. Had to re-flash T-Mobile ROM a couple of times before the mod worked.
Click to expand...
Click to collapse
You are giving me hope here hehe ..
Well i did replaced the bp_nvm_default files...
You see after the flash of the Tmobile rom i had to do that in order for the phone to recognize the Telcel network.. so after i replaced the bp_nvm_default files, it worked and i can make calls.. and access 2g and 3g networks..
Then i went to wireless settings and added the APN info for telcel.. MMS, GPRS, and 3G... Everything ok there or so it seems..
Then i went to Data Delivery Settings.. but there is no option to turn off the Data services for 3g or 2g for that matter...
I have seen this in some other T Mobile roms (in a droid 2)....
Any clues..?? do you have a way to enable 3g data in your settings?...

eetu1923 said:
You are giving me hope here hehe ..
Well i did replaced the bp_nvm_default files...
You see after the flash of the Tmobile rom i had to do that in order for the phone to recognize the Telcel network.. so after i replaced the bp_nvm_default files, it worked and i can make calls.. and access 2g and 3g networks..
Then i went to wireless settings and added the APN info for telcel.. MMS, GPRS, and 3G... Everything ok there or so it seems..
Then i went to Data Delivery Settings.. but there is no option to turn off the Data services for 3g or 2g for that matter...
I have seen this in some other T Mobile roms (in a droid 2)....
Any clues..?? do you have a way to enable 3g data in your settings?...
Click to expand...
Click to collapse
Gave my Charm to my brother. I can probably check with him tomorrow and report back.

ergosteur said:
Gave my Charm to my brother. I can probably check with him tomorrow and report back.
Click to expand...
Click to collapse
Please doo

Hey guys, I got stuck on T-Mo firmware T-Mobile_MB502_02.60.5_1FF_01, trying to unlock my phone but the band of my operator is for 850-1900, so no phone calls.
I followed this tutorial and it looks that it worked but after RSD finishes and restart the phone, I'm geting the message "SIM network unlock phone" does this means that:
--- it is recognizing the band of my operator (Claro - Colombia) but I need to use one of the services that offers the unlock code like "unlockallcellular.com"?--- that was the point of doing the flash anyways...
or
--- for step "E- Restore network" I need the files from the - "bp_nvm_default" - folder from a actual working Charm on my network? I'm using the ones given on http://forum.xda-developers.com/showthread.php?t=903969&page=4 (TELUS) is there any unlocked ones?
or
--- Am I doing anything wrong? :crying::crying::crying::crying: I've done the procedure like 10 times...
Thanks in advance for any help!!!

[HowTo] Enabling dual-SIM on single-SIM devices

Hi,
follow the steps below to enable dual-SIM functionality on a single-SIM XT1562 device.
IMPORTANT: Read the following before performing any of the steps below!
This HowTo is only for XT1562 devices. This has been reported to not work on XT1563 devices.
The second SIM in your phone will have an IMEI of "0" (as there was none set during manufacturing). In some countries like the UK, many providers don't allow phones with such an IMEI, so you will not be able to use SIM cards from these providers as your second SIM.
Only one SIM (the one used for data connection) can use 3G/LTE bands. The other SIM card can only use 2G bands (this is a hardware limitation of the device). In some countries like Sweden, some providers sell cards that can only use 3G and not 2G, so you will not be able to use these cards as "secondary" (calls/messages only) SIM.
If you plan to do a Nandroid backup or use Titanium Backup for your data currently on your phone (because you don't want to copy your data by hand) or if you want to flash a custom ROM like CyanogenMod, you will need to unlock your Moto X Play (instructions below). Note that in this case your device warranty will be void.
Here are the steps to enable dual SIM functionality:
If you want, make a backup of all your data. You can copy your files by hand, to not lose your warranty.
If you don't copy your files by hand but with Nandroid backup or Titanium Backup (to restore app data as well), you will have to unlock your device, and therefore lose warranty (Refer to this guide for unlocking: http://www.gammerson.com/2015/08/steps-how-to-unlock-bootloader-of-moto-x-play.html. Note that all your data will be lost, and your device warranty will be void.). In this case, easiest way is to boot up a custom recovery (see this thread) and make a Nandroid backup to an external SD card. Alternatively backup the apps with Titanium Backup and copy the internal SD card files by hand.
Flash a dual-SIM stock firmware: Find a stock firmware that matches your region best on this site (search for "XT1562" and "DS" for dual-SIM). Follow this guide completely for flashing the firmware on your device.
If you are fine with the stock ROM and don't need a custom ROM like CyanogenMod, and you copied your files and data by hand without root, you are now finished and can use your dual SIM phone.
If you want to flash another ROM, or restore a Nandroid backup or Titanium Backup, please continue with the following steps.
Flash your favorite ROM (e.g. @squid2's CM 12.1, it's running great), or stay with the stock ROM.
Unlock your Moto X Play (if not done for the backup before yet): Refer to this guide for unlocking: http://www.gammerson.com/2015/08/steps-how-to-unlock-bootloader-of-moto-x-play.html. Note that all your data will be lost, and your device warranty will be void.
If you're on stock ROM, flash a custom recovery (see this thread again) and root your device by flashing SuperSU from the recovery.
Restore your Nandroid or Titanium backup.
If you're not on stock ROM, add the following lines (needs root) to a new file /data/local.prop or append it at the bottom of /system/build.prop:
Code:
ro.gsm.data_retry_config=default_randomization=2000,max_retries=infinite,1000,1000,80000,125000,485000,905000
persist.radio.plmn_name_cmp=1
persist.radio.force_get_pref=1
persist.radio.multisim.config=dsds
I'd prefer the /data/local.prop, as you do not need to make the change on every ROM update.
If you're on CM 13, you will have to add this line as well:
Code:
ro.telephony.ril.config=simactivation
Make sure that either file has read/write permissions 644 and is owned by root:root (with 'chown'). To ensure the r/w 644 permissions, go into the properties of the file (e.g. with ES File Explorer), and check that the file is readable and writable (rw, or 6) by the owner, and readable (r, or 4) for the group and others.
Finally, reboot one last time.
Disclaimer: I do not take responsability for any damage that may be caused to your device or for the warranty that will be void after following this HowTo. Please make sure you have an appropriate device (XT1562) before flashing the dual-SIM stock firmware.
Credits go to @ALD76 for originally posting the build.prop/local.prop modifications above, and to all the testers who risked their devices to try this out and encourage other users. And to @heisert, for mentioning that unlocking is not necessary for flashing official firmwares. And to @GtrCraft, for the local.prop modification line on CM 13.
Have fun and enjoy your dual-SIM phone.
jellysheep

What is your base model and rom? I have XT1562 on UK rom obviously it's only single sim so for me to get it to work im guessing I would need to flash a base rom that has a dual sim enabled modem such as the Asian rom.
Have you tried this?
Sent from my XT1562 using Tapatalk

Interested in this also - from the other thread, I think most were successful with the Asian variant (unsure of the EXACT rom name). IMEI will be blank, some have had it work anyway, others not.
I'm interested in this thread now, as the other one was messy, full of "it can't be done" and people discussing removing the plastic, etc... If someone can suggest the exact name of the stock ROM that works and what variant or ROM they had previously, maybe we can get a more definitive answer.

jellysheep said:
Hi,
many Moto X Play users like @Quasar have reported a working second SIM card after flashing a dual-SIM ROM and/or adding a few lines to build.prop/local.prop:
With the lines above in build.prop, I get the "SIM cards" menu in system settings, however it always reports SIM 2 as empty (though card is inserted that works as SIM 1).
Do you have any ideas how to fully enable the second SIM card?
Thanks, jellysheep
Click to expand...
Click to collapse
Did you flash the XT1562_LUX_RETASIA_DS_5.1.1_LPD23.118-12_cid7_subsidy-DEFAULT_CFC firmware first ?

ALD76 said:
Did you flash the XT1562_LUX_RETASIA_DS_5.1.1_LPD23.118-12_cid7_subsidy-DEFAULT_CFC firmware first ?
Click to expand...
Click to collapse
No, but I'll try that as soon as the download has finished. Thanks for the hint :thumbup:

@jellysheep
Done. CM with DS on a SingleSim Device RetEu.
It's just a question of the right Baserom. I tryed the french Firmware plus the trick from the initial post and it works.
You will lose data connection until you do the trick, so make sure you are in a wlan area to set uo your device.
here is a fast link to the base rom:
https://drive.google.com/file/d/0BxY75MbFAKsXcExRbnd3VXg1Mmc/view?usp=docslist_api
The trick I mentioned:
Add the following text to your build.prop (it's in the system folder). I didn't test the option with a local.prop .
ro.gsm.data_retry_config=default_randomization=200 0,max_retries=infinite,1000,1000,80000,125000,4850 00,905000
persist.radio.plmn_name_cmp=1
persist.radio.force_get_pref=1
persist.radio.multisim.config=dsds

@odysseus84: Thanks for the firmware link! :thumbup:
It worked on my german XT1562, and restoring the Nandroid backup (CM12.1) went fine as well. Now I have the same system as before, but with dual sim enabled.

jellysheep said:
@odysseus84: Thanks for the firmware link! :thumbup:
It worked on my german XT1562, and restoring the Nandroid backup (CM12.1) went fine as well. Now I have the same system as before, but with dual sim enabled.
Click to expand...
Click to collapse
You're welcome. It is just a bit annoying that we have to reenable DS after a flash. I wasn't able to do it with the local.prop

odysseus84 said:
You're welcome. It is just a bit annoying that we have to reenable DS after a flash. I wasn't able to do it with the local.prop
Click to expand...
Click to collapse
You mean after a CM upgrade, when just /system is flashed?
You just have to put the mentioned lines in /data/local.prop, and make sure it has user root:root and permissions 644 (just like build.prop).

Does this need to be done using CM or can it be done with stock rom?? Very intrigued

milestoneman said:
Does this need to be done using CM or can it be done with stock rom?? Very intrigued
Click to expand...
Click to collapse
Using the official dual-sim firmware that you flash anyway works fine. Just take care to select the right firmware version (model and region).
EDIT: But you will need root to add the needed lines to build.prop/local.prop.

I've got an XT1562 EU
just to be extra xautious, which firmware?

milestoneman said:
I've got an XT1562 EU
just to be extra xautious, which firmware?
Click to expand...
Click to collapse
Have a look here:
http://forum.xda-developers.com/mot...single-sim-t3194533/post62790748#post62790748
You most likely need something called XT1562_LUX_RETASIA_DS_5.1.1_LPD23.118-12_cid7_subsidy-DEFAULT_CFC

To further ad to the discussion:
You can just add the lines to a stock XT1563 (Canadian) and it will show you the 2nd SIM.
I know because I have done it.
BUT the problem is (I'll discuss further below) that it doesn't give you a 2nd IMEI for the 2nd SIM which in Canada and lot of other countries is a no go.
A lot of countries require 1 IMEI per SIM so dual SIM phones require 2 IMEI. This isn't iron clad - China doesn't have this requirement and some EU & South American countries don't either. However if you're Moto X Play is having issues with 2 SIM's (non stock units) it will be because your location requires the 2nd IMEI. It is possible to add a second IMEI number to the phone but you are going into dubious legal territory IMO. That's why I'm not going to spell it out for you here but rest assured that if you google it you will find the necessary information on how to add the IMEI for the second SIM slot.
IMO the IMEI number missing on the second SIM slot is the only thing different once you have added the lines to the build.prop from above posts.
Properly modded with the 2nd IMEI + build.prop a single SIM Moto X Play would be identical to it's dual SIM cousin IMO.

Tim3tripp3r said:
To further ad to the discussion:
You can just add the lines to a stock XT1563 (Canadian) and it will show you the 2nd SIM.
I know because I have done it.
Click to expand...
Click to collapse
I was seeing crashes while trying to modify settings for the second SIM.
Is everything working (other than not having the IMEI)?

Unlocked bootloader, got TWRP, rooted, downloaded firmware
Will try tomorrow as too late now
thanks for your help - hoping it works
---------- Post added at 01:19 AM ---------- Previous post was at 12:23 AM ----------
Curiosity got the better of me. I did the build prop changes, running Asian dual sim firmware but sim slot 2 always show no signal. It reads the sim as it shows the phone number.

@jellysheep Thank's for your Tipp for the local.prop. I had to add the file too the group 0000-Root. Now it works.
Maybe you could mark the thread as [How to] and put the Guide into the initial post, so people do not have to search the whole thread.
Tanks again

odysseus84 said:
@jellysheep Thank's for your Tipp for the local.prop. I had to add the file too the group 0000-Root. Now it works.
Maybe you could mark the thread as [How to] and put the Guide into the initial post, so people do not have to search the whole thread.
Tanks again
Click to expand...
Click to collapse
Yeah, I had planned to do exactly this, thanks for reminding me. [emoji106]

So anyone in the UK got this working?

I did this to my single-sim (which was supposed to be a dual-sim version, damn you retailer!)
I flashed the EU dual-sim firmware.
I get to put in my pin etc for the second sim, but the second simcard slot doesn't have an IMEI. So it can't register on a network.

Xfinity Mobile Data Not Working

Hi,
Is anyone else having a problem with Xfinity Mobile data? I can make phone calls, but I can't get any data connection. This was a phone I bought from Sprint, and due to their messed up unlock system, it got relocked, so I manually unlocked it by using this method: https://forum.xda-developers.com/showpost.php?p=75994498&postcount=360
After that, the phone got unlocked successfully. It accepted a TMO sim, and I was able to update to newer firmware. Today, I decided to put it on my Xfinity Mobile line, and I just can't make data work. Any help would be appreciated.
Thank you,

OK. I think I narrowed down the problem. APN setting has VZWINTERNET. It's supposed to be COMCAST.RSLR.VZWENTP based on what I read on the internet. The problem is, I can't edit or add a new APN. I saw someone else talking about this APN setting problem, and his was resolved with the April security patch https://forums.androidcentral.com/e...cant-add-edit-apn-all-sudden-lost-4g-lte.html
I have that security patch already installed, but my problem persists. I can't change APN. Any help would be appreciated.

It's possible Xfinity locks the APN settings or that it has something to do with yours being the Sprint version. I would power the phone down and remove the SIM. Power the phone on with no SIM card and when you are booted up go into settings and reset the network settings. Power down again and insert your Xfinity SIM. That should ensure that the new SIM populates all the network settings.

jhs39 said:
It's possible Xfinity locks the APN settings or that it has something to do with yours being the Sprint version. I would power the phone down and remove the SIM. Power the phone on with no SIM card and when you are booted up go into settings and reset the network settings. Power down again and insert your Xfinity SIM. That should ensure that the new SIM populates all the network settings.
Click to expand...
Click to collapse
Thank you for replying. That did not work. I don't think it's Xfinity. The problem is that APN gets locked to VZW instead of Xfinity's APN, which is why data doesn't work. I can put a TMO sim card in it and it works fine, so I don't know that there is something wrong with the phone itself. If you have any other suggestions, I would appreciate it. I'm desperate to get this working.

goldentequila said:
Thank you for replying. That did not work. I don't think it's Xfinity. The problem is that APN gets locked to VZW instead of Xfinity's APN, which is why data doesn't work. I can put a TMO sim card in it and it works fine, so I don't know that there is something wrong with the phone itself. If you have any other suggestions, I would appreciate it. I'm desperate to get this working.
Click to expand...
Click to collapse
In a Reddit thread, a user says you need to disable Enhanced LTE:
Under Settings > More > Cellular Networks, disable "Enhanced 4G LTE Mode" and set "System select" to "Automatic"
Haven't tried it myself, but I'm thinking of switching to XM and would like to know how this works out for you.

Get your original Xfinity phone factory reset the original Xfinity phone put your Sim in go through activation. This should work for you this also fixes volte on Xfinity If your volte ever gets deactivated. Anyway from what has happened to my other phones sometimes the apn can get changed on the Sim and got carried over somehow. Resetting the original Xfinity phone will bring the Sim settings back to the Sim card thus fixing your apn settings.
(Another way is to use another phone to edit the apn settings)
I also have Xfinity mobile and it's working fine. Just sometimes my apn gets uncheck and I don't know why
If you messed with bands.
Also make sure you go and download hidden settings from the playstore if you messed with your bands and selected American bands you need to select automatic bands if you messed with radio information page settings.
I messed with bands and it caused phone calls to not work.
---------- Post added at 10:08 AM ---------- Previous post was at 09:31 AM ----------
The Sim saves apn settings and I did notice the first time using this essential phone I had 2 options in the apn and I read carefully which one to select. It may have saved the incorrect information to the Sim. I did this once on a Moto phone and I thought if I put Verizon apns instead of Comcasts I could get better speeds. But I caused my data to stop working. I reset the Moto phone and u still had the problems. I looked for the apn for Comcast couldn't find it. Then I thought of either editing the apn using another phone or using the original Xfinity phone. But it does get saved for sure. I ran into this issue before and I'm pretty sure this will resolve the problems.

goldentequila said:
Thank you for replying. That did not work. I don't think it's Xfinity. The problem is that APN gets locked to VZW instead of Xfinity's APN, which is why data doesn't work. I can put a TMO sim card in it and it works fine, so I don't know that there is something wrong with the phone itself. If you have any other suggestions, I would appreciate it. I'm desperate to get this working.
Click to expand...
Click to collapse
Ever get this resolved?

rootnooby said:
Ever get this resolved?
Click to expand...
Click to collapse
Yes. I manually sideloaded Beta Oreo build, even though my phone already had the official OTA Oreo on it. That fixed the connection issue altogether.

goldentequila said:
Yes. I manually sideloaded Beta Oreo build, even though my phone already had the official OTA Oreo on it. That fixed the connection issue altogether.
Click to expand...
Click to collapse
Wow. Glad to hear your issue is resolved. Who would ever think of going back to a beta build from an official build to fix a connection issue! I may try Xfinity mobile in the near future. Thank you.

rootnooby said:
Wow. Glad to hear your issue is resolved. Who would ever think of going back to a beta build from an official build to fix a connection issue! I may try Xfinity mobile in the near future. Thank you.
Click to expand...
Click to collapse
Yea, it was just a desperate move lol. Glad it'll be helpful for others.

I had the worst time making the XFinity mobile work on Android Pie with the October patches in place and finally got it working. Basically, there was no way to edit the APN configuration even with root on the device via actual Android. What I did to fix this was the following...
-Followed the rooting procedure to get TWRP and Fastboot installed
-I then used "Termux" to copy the APN points configuration file to a writable location. In my case I copied the file from "\system\etc\apns-conf.xml" to a "\sdcard\Download". Keep a copy of the original file.
-I then simply copied the file over to my computer and opened it in NotePad++. I did a search for the following string in single quotes: 'carrier="Verizon"\n mcc="311" '
-This should pull up 5 results in the search and you should confirm that each of the lines has the mnc value set to 480, 'mnc="480"'. On each of the sections that came up, I switched the following variables as shown below...
apn="COMCAST.RSLR.VZWENTP"
authtype="0"
protocol="IP"
roaming_protocol="IP"
-Once you have edited the file, copy it to a writable location on the device, like "/sdcard/Download".
-This then requires rebooting into recovery mode with TWRP and you will need to make sure you have encryption and a PIN disabled on your device to make sure you have full access to the device file system.
-Within the main TWRP page, select "Mount" and you will need to have the "System" and "Data" partitions selected.
-Return to the main page and select "Advanced" and then "File Manager".
-Next, locate the original apns-conf.xml that you copied earlier. It should show up as being in "/system/system/apns-conf.xml". Click on that file, and select "chmod 755".
-Next, navigate to where you have the edited apn file located. Copy that file over to replace the apns configuration file at "/system/system/apns-conf.xml". Just make sure you have a backup of that original file before replacing it.
-Finally, reboot your phone into the OS and you should magically have Xfinity mobile working.
This took a lot longer than I wanted to spend getting it working, but I believe this is because of the carrier ID and MCC being shared with Verizon instead of a separate one for XFinity mobile which forces it to default to the first Verizon APN setting which doesn't allow this to work. There are other ways to edit the APN configuration file, however I found it was quickest to do the actual file replacement with TWRP since that gives you full file system root access.

bschaff1 said:
I had the worst time making the XFinity mobile work on Android Pie with the October patches in place and finally got it working. Basically, there was no way to edit the APN configuration even with root on the device via actual Android. What I did to fix this was the following...
-Followed the rooting procedure to get TWRP and Fastboot installed
-I then used "Termux" to copy the APN points configuration file to a writable location. In my case I copied the file from "\system\etc\apns-conf.xml" to a "\sdcard\Download". Keep a copy of the original file.
-I then simply copied the file over to my computer and opened it in NotePad++. I did a search for the following string in single quotes: 'carrier="Verizon"\n mcc="311" '
-This should pull up 5 results in the search and you should confirm that each of the lines has the mnc value set to 480, 'mnc="480"'. On each of the sections that came up, I switched the following variables as shown below...
apn="COMCAST.RSLR.VZWENTP"
authtype="0"
protocol="IP"
roaming_protocol="IP"
-Once you have edited the file, copy it to a writable location on the device, like "/sdcard/Download".
-This then requires rebooting into recovery mode with TWRP and you will need to make sure you have encryption and a PIN disabled on your device to make sure you have full access to the device file system.
-Within the main TWRP page, select "Mount" and you will need to have the "System" and "Data" partitions selected.
-Return to the main page and select "Advanced" and then "File Manager".
-Next, locate the original apns-conf.xml that you copied earlier. It should show up as being in "/system/system/apns-conf.xml". Click on that file, and select "chmod 755".
-Next, navigate to where you have the edited apn file located. Copy that file over to replace the apns configuration file at "/system/system/apns-conf.xml". Just make sure you have a backup of that original file before replacing it.
-Finally, reboot your phone into the OS and you should magically have Xfinity mobile working.
This took a lot longer than I wanted to spend getting it working, but I believe this is because of the carrier ID and MCC being shared with Verizon instead of a separate one for XFinity mobile which forces it to default to the first Verizon APN setting which doesn't allow this to work. There are other ways to edit the APN configuration file, however I found it was quickest to do the actual file replacement with TWRP since that gives you full file system root access.
Click to expand...
Click to collapse
You couldn't cut and paste the file back with a root file manager? Maybe a magisk module? And does this lock you to Verizon?
Sent from my PH-1 using XDA Labs

avd said:
You couldn't cut and paste the file back with a root file manager? Maybe a magisk module? And does this lock you to Verizon?
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
I'm sure there are other ways to get the file back there, but I found my approach to be a quick bypass for other methods of getting root.
Regarding Verizon, It would probably break a Verizon connection for a sim carrier code of 311480. However, since this post is about Xfinity mobile, this is the quick way I got it working. In the future I want to change the priority on the APN configurations which may allow Xfinity mobile and Verizon to play nicely. The issues that have caused this are Android Pie restricting people from changing settings on the phones they own and Xfinity mobile being either too lazy or cheap to commit to their own carrier code and provide that information to manufacturers.

bschaff1 said:
I'm sure there are other ways to get the file back there, but I found my approach to be a quick bypass for other methods of getting root.
Regarding Verizon, It would probably break a Verizon connection for a sim carrier code of 311480.
Click to expand...
Click to collapse
Breaking a Verizon contract for sim carrier code would be a drastic move, considering.. The only money you have to spend is $5 on a Verizon prepaid phone card. Go into a Verizon corporate store and they will give you a sim, ( it's $20 if you don't go to the corporate store)
Sent from my mata using XDA Labs

Missing GSM and LTE bands on Ebay E5823

I recently got not one, not two, but three ebay E5823's and was having trouble connecting to T-Mobile bands (3G and 4G) in the US
digging in, I managed to get into the service menu and discovered that the bands I need are disabled. Note that the phone remains on Edge all the time
I've read old threads like this https://forum.xda-developers.com/cr...ad-progress-please-leave-im-updating-t2871269 and this https://forums.oneplus.com/threads/...-qualcomm-devices-oneplus-one-edition.193610/ about unlocking certain disabled bands on Qualcomm devices, however all of the download links for the QXDM software seem to have disappeared. I did manage to find a copy of QPST but I'm not sure I trust it.
Qualcomm
I've tried flashing US and German firmware from the xperia-flashtool, but I don't think that overwrites the radio firmware
Has anyone else seen this? I assume I've got Chinese models? does anyone have a working link for QXDM?

The same thing happens with the b20 band (800mhz) with a z5c bought from China by ebay. I tried to connect the z5c by ADB via USB with QPST - Dfs tools qualcomm and it is not possible with the drivers available for Z5C, on the other hand with a Z3C I had no problems in modifying the bands.If I managed to connect the Z5C by ADB wifi but it does not allow writing anything. I can only send ADB commands but I can not access the z5c modem as these softwares require. I'm always talking about the Kernel-Firmwares I've had in my Z5c, maybe with others if Dfs tools detects it as & MI_04 as these softwares require.
At the moment I leave it as impossible because I think that these devices bought in china or are mobile development or are mobile with baseband and blocked features such as NFC or mirrorlink

trancazo71 said:
The same thing happens with the b20 band (800mhz) with a z5c bought from China by ebay. I tried to connect the z5c by ADB via USB with QPST - Dfs tools qualcomm and it is not possible with the drivers available for Z5C, on the other hand with a Z3C I had no problems in modifying the bands.If I managed to connect the Z5C by ADB wifi but it does not allow writing anything. I can only send ADB commands but I can not access the z5c modem as these softwares require. I'm always talking about the Kernel-Firmwares I've had in my Z5c, maybe with others if Dfs tools detects it as & MI_04 as these softwares require.
At the moment I leave it as impossible because I think that these devices bought in china or are mobile development or are mobile with baseband and blocked features such as NFC or mirrorlink
Click to expand...
Click to collapse
Did you find anyone else trying to do this? I can spin up a windows box, but I also don't have one handy, so I've yet to see how well QPST works.
I think I may just send this back, but it's troubling that there must be a stockpile of Z5C's out there with bands disabled being sold on the internet. I'd like to figure this one for that reason alone (so many perfectly good devices going to waste)

If you had heard about Sony products sold online that lack any of the specifications you can have in the local market and in fact I have a document that informs you of it as a development unit. Sony takes care not to violate laws and licenses such as the use of nfc or mirrorlink that are not allowed in all countries and that apparently are not limited to a simple change of stock firmware. Sony's own online repair software rejects the repair of mobile phones that are outside of the area to which they were destined, and Sony's own technical repair services do not take charge of imported smartphone from ebay. I think that it is not just about functionalities controlled by the drm keys, but also the programming of their chipset. there was a time that wasted many hours trying to make mirrorlink work in an import z5c and it was impossible for the car to detect it as a compatible device, when in its ROM it includes the necessary system files for it. To finish, I told you that even using the tools to modify code in qualcomm chipset and checking the modification of the band in * # * # service # * # *, in fact there is no change in the bands even if it shows as done. At least this is my experience with this type of smartphone and sony bought from Hong Kong or China.
I forgot. In the attempt to use band 20 in the z5c, I have flashed dozens of baseband and stock firmware from several countries that use 800 mhz for 4g in their networks and although using * # * # info # * # * could change the country of the base band, there was no effect with respect to each specific band.

stratosmacker said:
...
Click to expand...
Click to collapse
trancazo71 said:
...
Click to expand...
Click to collapse
Would you chaps be good enough to link to either the eBay auction or the eBay seller that you bought these from, so that others can avoid the same mistake? I'm sure there is more than one seller that is distributing these phones, so buyers may not be safe anyway, but at least we can steer people away from known-bad auctions.
Thanks!!
-- Nathan

Also, for what it's worth, the band list shown in that screen shot *exactly* matches the one for the Japan-market-only (manufactured for DoCoMo) Z5c variant model SO-02H, as you can see here: http://phonedb.net/index.php?m=device&id=8900&c=sony_xperia_z5_compact_td-lte_so-02h__sony_suzuran
I thought it wasn't supposed to be possible (at least according to other posts I've read) to flash E58x3 firmwares on SO-02H, and I also believe all of those have non-unlockable-bootloaders as well. It's almost like these Chinese refurbishers have a stockpile of SO-02H motherboards, and have managed to figure out how to shoehorn the E5823 firmware on them. I think this probably also explains why NFC doesn't work on these either, nor can be made to work (see the other thread).
Either that or it is an E5823 but somehow the baseband got flashed with the DoCoMo one. If that's the case, I'm not sure how you undo that...
I also have yet to see a E58x3 that shows anything other than "HWC_Kitakami_Com_010" for "HW Config rev:". Every single reference I have found for "HWC_Kitakami_Com_009" so far is about a Z3+. I haven't found any screenshots of the Service > Configuration screen from a DoCoMo Z5c, though.
-- Nathan

You can "shoehorn" docomo or other carrier variants with stock firmware by rewriting an xml file before bundling the .ftf to the model you wish it to be, it does not rewrite carrier info, imei, lock status, etc. Rewriting the boot configuration to test is another story (I have tested this extensively and there are many quagmires when altering the files the bootloader writes the boot status as); there is a thread where these two go back and forth about a software you can purchase to write straight to the loader itself and change the lock status, albeit losing the imei #'s was an issue if the process was not done correctly ( https://forum.xda-developers.com/xperia-xz1/how-to/update-xz1sov36-bootloader-allow-to-yes-t4140775 ). Maybe this is the software they are using on these 810s along with the xml modificaton to "repackage" these as a factory unlocked e5823? I will have to check out the software you recommended to write to the bands/frequencies and see if I am able to successfully include the 800 frequency with what is more than likely a phone from the same batch of z5 compacts that stratosmacker ended up with.

&(*) said:
You can "shoehorn" docomo or other carrier variants with stock firmware by rewriting an xml file before bundling the .ftf to the model you wish it to be, it does not rewrite carrier info, imei, lock status, etc. Rewriting the boot configuration to test is another story (I have tested this extensively and there are many quagmires when altering the files the bootloader writes the boot status as); there is a thread where these two go back and forth about a software you can purchase to write straight to the loader itself and change the lock status, albeit losing the imei #'s was an issue if the process was not done correctly ( https://forum.xda-developers.com/xperia-xz1/how-to/update-xz1sov36-bootloader-allow-to-yes-t4140775 ). Maybe this is the software they are using on these 810s along with the xml modificaton to "repackage" these as a factory unlocked e5823? I will have to check out the software you recommended to write to the bands/frequencies and see if I am able to successfully include the 800 frequency with what is more than likely a phone from the same batch of z5 compacts that stratosmacker ended up with.
Click to expand...
Click to collapse
do you know where i can find instructions on rewriting xml file to flash different bundle via flashtool. my problem is i backed up my ta on e5803 , unlocked bootloader, flashed via recovery custom rom , now my device shows as e5823 on flashtool , trying to go back to stock e5803 but fashtool gives me "the bundle doesnt match the connected device" error.
i need to flash e5803 stock .54 back to my phone to restore my ta.
thanks

sabotage154 said:
do you know where i can find instructions on rewriting xml file to flash different bundle via flashtool. my problem is i backed up my ta on e5803 , unlocked bootloader, flashed via recovery custom rom , now my device shows as e5823 on flashtool , trying to go back to stock e5803 but fashtool gives me "the bundle doesnt match the connected device" error.
i need to flash e5803 stock .54 back to my phone to restore my ta.
thanks
Click to expand...
Click to collapse
I can tell you: edit the fwinfo.xml before bundling. Open Xperifirm, before closing Xperifirm you need to edit the fwinfo.xml file (and you can delete the bundled file to repack the already downloaded firmware, in case you already have the ftf created). Change the reference of 5803 to 5823 in that file, what you are essentially doing is telling the compiler to bundle the .ftf for that model, a 5823 (which is what you are currently running); however, you just downloaded a system.sin for a 5803 that it doesn't unpack or read, only on boot will this change occur after flashing it. You are using windows or linux? You might need help finding the download folder for Xperifirm that your flash program is bundling from. If you need extra help, let me know. I'm assuming you came from a custom rom that wrote system unconditionally.

Ican tell you one thing.... these Sonys Z5 compacts are refubrished So-O2H with cracked firmware from E5823....
Opened bootloader.... Rooted....
They cannot have LTE 800 BC20 and sometimes also don´t accept GSM network.... these phones are hand maked at Pakistan.... so if they fall down home even on carpet, they will be totally crashed.... display, or rear case.... this is the difference between originals and these.... originals can fall and no problem....
Quality 0 ZERO..... copy okey....
95% of all Z5 compacts are these fakes..... Ebay nd so on....
so be carefull what you buy....
Originals have this IMEI 35428207---- that is important!
It si something like a car VIN number..... it begins same numbers.... and it is okey....

There are also some models with original so-02h firmware, there jumps fakin japan funky ninja and you know sh!t.... these are not cracked to E5823.... the are locked! these are funky.... lots of rice everywhere.... what a fak....
but no you dont get LTE 20 nono only fun....joke... jumping ninja locked botloader. Ninja

M1cr0n Cell said:
There are also some models with original so-02h firmware, there jumps fakin japan funky ninja and you know sh!t.... these are not cracked to E5823.... the are locked! these are funky.... lots of rice everywhere.... what a fak....
but no you dont get LTE 20 nono only fun....joke... jumping ninja locked botloader. Ninja
Click to expand...
Click to collapse
Were you on some kind of stimulants when you wrote this? Why so many smiley face emojis after every few words. Wow, and your reply really isn't helpful.
I have an E5823 here that I know for a fact was unlocked, I used it on other networks before but as the OP said, T-mobile isnt working. they run a different band that these E5823's do not have unlocked as they said LTE/3G etc is not working with them and tmobile.
If we could find a way to enable the bands it would be fixed and working, but for now nobody has figured a way to do it. My E5823 was imported from the european market. That is why it's missing some bands. As all of them should be which were not FCC cleared. the FCC regulates what bands could operate in which countries at that point in time which was 2014-2015 and this phone did not have authorization to unlock those bands.
So now we just have to wait and see if there is ever a way to fix it.