[HowTo] Enabling dual-SIM on single-SIM devices - X Play Q&A, Help & Troubleshooting

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.

Related

[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!!!

Google Wallet working for I-9300 in US

Hey guys, I just got GW working for my unlocked and rooted SGS3 i9300 by combining the how-to from GW for US variants (HERE) and MoDaCo latest patched GW (HERE). So here are the steps (obviously your phone has to be rooted and is using TW; not sure about other roms; I'm using the latest JB leak LI8):
1. Nandroid backup
2. Using Root Explorer (ES will not work as reported from other source), modify the /system/build.prop:
LOOK FOR THESE LINES:​
Code:
ro.build.model=GT-I9300
ro.product.name=m0xx
ro.product.device=m0
TO​
Code:
ro.product.model=htc_jewel
ro.product.name=htc_jewel
ro.product.device=htc_jewel
Then save it. RE will automatically backup the old one as build.prop.bak.
3. Download the latest GW from HERE to sd card
4. Move the GW.apk to system/app
5. Restart the phone
6. Start GW, sign in, add your cards, etc
7. Back to RE, delete the new build.prop, and then change the old build.prop.bak to build.prop, so S-voice can work properly (or else you'll get network error)
8. Restart the phone again
9. Enjoy your GW at 711 or elsewhere (I had it work at 711)
10. Another nandroid backup would be useful
11. Don't restore this GW by Titanium Backup whenever installing a new TW-based rom. Instead, reset (in-app setting) and delete GW from the phone. Flash a TW rom, then follow the steps again.
PS: I assume most of you know how to work with RE and nandroid; you can search xda for instructions.
Disclaimer: I'm not sure if this method works with other JB leaks, ICS, or other custom roms (don't mention CM, since it's another whole world )
Credit: ogdobber (GW for US variants), PaulOBrien (Patched GW)
No replies? Wow.
Thanks for posting this. I'm running the latest Wanamlite ROM, which is based on Touchwiz JB. I know that one of the modifications is a "modified build.prop" file for increased market compatibility. Do you think that it not being 100% stock ROM will prevent me from trying this?
Maybe because there's similar thread in themes and apps section.
And I think its even older than oggdober thread and op has been the first to figure out HTC_jewel thingy.
Sure it dealt with UK customers in the title, but the rest is identical. Then they blacklisted us (the test of the world) and we stopped caring.
All said it does not mean in its current form it is not usefull for us customers (only).
Testing JKay alpha on GT-I9300
got this set up yesterday but haven't had a chance to test it out yet at a store.
I have done the procedure similar to this with my S2 so I figured this shouldnt be that hard. Well I follow the Instructions and it gets all set up however when i got o add my debit card it says "Request Failed, Please try again" and no mat7ter how many times i try to do it it still wont go through. Any ideas as to why?

[HOW-TO][TEST] Change 4G bands (ZE551ML)

Update: so far, described method doesn't unlock other bands. Need to find other ways.
Disclamer: You are doing this at your own risk.
The key point: Allowed bands are written in /system/vendor/firmware/telephony/ze550ml_XX_726x.tlv where XX is your region TW, WW, US, CN, etc.. Don't confuse by ze550ml in the name. It's for ZE551ML! I don't know how it is in ZE550ML, but should be the same according to name.
Region is hardcoded in SFI table OEM1. SFI is similar to ACPI found in PC. Flashing of firmware doesn't change this part. You may change firmware region to whatever you want, but region of your phone will remain the same and 4G band will remain the same as you had out of the box.
Since bootloader is locked, we cannot spoof SFI tables in kernel. But we can replace /system files.
So, if you have rooted Zenfone 2, then you can copy ze550ml_WW_726x.tlv to ze550ml_TW_726x.tlv if you want to convert TW model to WW model. (Similar for CN->WW). You need to open /system partition for write access (R/W). You can do everything in Root Explorer.
It may be that ze550ml_XX_726x.tlv files are protected by check-summ and name, so replacing the file my brake radio functionality. In this case you have to return you original ze550ml_XX_726x.tlv file and try another method described below.
Open file /system/etc/catalog/V1_DSDA_ZE550ML_TW/telephony_config/V1_DSDA_ZE550ML_TW_726x.xml in any text editor and replace text inside ze550ml_TW_726x.tlv to ze550ml_WW_726x.tlv. Or you can copy file /system/etc/catalog/V1_DSDA_ZE550ML_WW/telephony_config/V1_DSDA_ZE550ML_WW_726x.xml to /system/etc/catalog/V1_DSDA_ZE550ML_TW/telephony_config/V1_DSDA_ZE550ML_TW_726x.xml.
Don't forget to reboot your phone before try 4G.
Unfortunately, i cannot test it by myself because my carrier work on 1800MHz which presents in all regions. So, i simply won't see any difference between regions.
Please report here about results.
Will hopefully be able to try it this weekend on my CN version (still need to root and update firmware first) and will report back!
So far, no go. Still trying to make sure I did it right but I believe I did. Still only seeing H+ and if I change it to LTE Only in the Device information menu I get no signal whereas I still had a LTE signal on my Nexus 4.
I did the following:
Copy file /system/etc/catalog/V1_DSDA_ZE550ML_US/telephony_config/V1_DSDA_ZE550ML_US_726x.xml to /system/etc/catalog/V1_DSDA_ZE550ML_CN/telephony_config/V1_DSDA_ZE550ML_CN_726x.xml
EDIT: I did get an LTE signal quickly after I set the preferred network type to LTE only, but once I set it back to LTE/GSM auto it went away. Still trying to get t back but so far nothing.
Need to wait for bootloader unlock. In this case, it's possible to compile custom kernel with spoofed region.
All this is based in theory that hardware in all region are the same. If hardware different, then change of region is impossible.
hkdmjack said:
EDIT: I did get an LTE signal quickly after I set the preferred network type to LTE only, but once I set it back to LTE/GSM auto it went away. Still trying to get t back but so far nothing.
Click to expand...
Click to collapse
But if you don't change files, setting LTE-only doesn't give you LTE signal?
update: check folder /local_cfg/telephony_config
check if your changes reflected there. If not, then change xml file there.
don't forget to reboot.
Ok lets see if i am reading this right.
IF this works does it mean i can buy a China . CN . Zenfone 2 and them make it into a WW version so all 4 bands work ?
I am in the UK and need all 4g bands to work.
jacko5 said:
Ok lets see if i am reading this right.
IF this works does it mean i can buy a China . CN . Zenfone 2 and them make it into a WW version so all 4 bands work ?
I am in the UK and need all 4g bands to work.
Click to expand...
Click to collapse
The key word is "IF". Still no confirmation. May be need more changes. There is region mention also in /factory partition.
sorg said:
But if you don't change files, setting LTE-only doesn't give you LTE signal?
Click to expand...
Click to collapse
As far as I could tell. I got a weak signal on band 4 after making the changes, but I guess not strong enough that it's not connecting or drops pretty much right away if I'm reading the results from my LTE Discovery app right.
sorg said:
update: check folder /local_cfg/telephony_config
check if your changes reflected there. If not, then change xml file there.
don't forget to reboot.
Click to expand...
Click to collapse
Yup, rebooted but will try this tonight if I can find the time.
Screenshot is what I see in LTE Discovery when I set preferred network to LTE. It shows band 12 and earlier I saw band 4. Only difference is I performed the first suggestion this time, but I didn't revert my earlier change. It looks like I'm getting these two bands now but if you look up too there is no network connection.
By first suggestion I mean this:
So, if you have rooted Zenfone 2, then you can copy ze550ml_WW_726x.tlv to ze550ml_TW_726x.tlv if you want to convert TW model to WW model. (Similar for CN->WW). You need to open /system partition for write access (R/W). You can do everything in Root Explorer.
It may be that ze550ml_XX_726x.tlv files are protected by check-summ and name, so replacing the file my brake radio functionality. In this case you have to return you original ze550ml_XX_726x.tlv file and try another method described below.
I basically copied everything from ze550ml_US_726x.tlv to ze550ml_CN_726x.tlv.
Strange.
Oh, and I did check that other file and my initial change appears there as well.
Quick update. This morning as I was driving to work I saw the data indicator change from H/H+ to 4G a few times. I tried to run speedtest while on 4G, and got up to ~ 32 Mbps down but it did not work when speedtest tried to test the upload speed. Unfortunately it was only in a small area so I had it for all of 15 minutes or so.
hkdmjack said:
Quick update. This morning as I was driving to work I saw the data indicator change from H/H+ to 4G a few times. I tried to run speedtest while on 4G, and got up to ~ 32 Mbps down but it did not work when speedtest tried to test the upload speed. Unfortunately it was only in a small area so I had it for all of 15 minutes or so.
Click to expand...
Click to collapse
In /factory partition, there is several mentions of region.
/factory/PhoneInfodisk/country_code
/factory/PhoneInfodisk/PhoneInfo_inf
These files are not text, but binary. So, you need HEX editor to modify (region is coded by letters as usual TW, WW, CN, etc.).
And don't forget to backup these files, because it's not part of a firmware. If you lost/tamper them, then only backup copy can save you.
I recommend to backup whole /factory folder to be safe.
sorg said:
In /factory partition, there is several mentions of region.
/factory/PhoneInfodisk/country_code
/factory/PhoneInfodisk/PhoneInfo_inf
These files are not text, but binary. So, you need HEX editor to modify (region is coded by letters as usual TW, WW, CN, etc.).
And don't forget to backup these files, because it's not part of a firmware. If you lost/tamper them, then only backup copy can save you.
I recommend to backup whole /factory folder to be safe.
Click to expand...
Click to collapse
Thanks for the recommendation. I've been making backups of each file that I edited, just in case. Anyway tonight going to try a hard reset tonight because I've been having some other issues, then reflash the pre-root image and go from there.
sorg said:
Disclamer: You are doing this at your own risk.
The key point: Allowed bands are written in /system/vendor/firmware/telephony/ze550ml_XX_726x.tlv where XX is your region TW, WW, US, CN, etc.. Don't confuse by ze550ml in the name. It's for ZE551ML! I don't know how it is in ZE550ML, but should be the same according to name.
Region is hardcoded in SFI table OEM1. SFI is similar to ACPI found in PC. Flashing of firmware doesn't change this part. You may change firmware region to whatever you want, but region of your phone will remain the same and 4G band will remain the same as you had out of the box.
Since bootloader is locked, we cannot spoof SFI tables in kernel. But we can replace /system files.
So, if you have rooted Zenfone 2, then you can copy ze550ml_WW_726x.tlv to ze550ml_TW_726x.tlv if you want to convert TW model to WW model. (Similar for CN->WW). You need to open /system partition for write access (R/W). You can do everything in Root Explorer.
It may be that ze550ml_XX_726x.tlv files are protected by check-summ and name, so replacing the file my brake radio functionality. In this case you have to return you original ze550ml_XX_726x.tlv file and try another method described below.
Open file /system/etc/catalog/V1_DSDA_ZE550ML_TW/telephony_config/V1_DSDA_ZE550ML_TW_726x.xml in any text editor and replace text inside ze550ml_TW_726x.tlv to ze550ml_WW_726x.tlv. Or you can copy file /system/etc/catalog/V1_DSDA_ZE550ML_WW/telephony_config/V1_DSDA_ZE550ML_WW_726x.xml to /system/etc/catalog/V1_DSDA_ZE550ML_TW/telephony_config/V1_DSDA_ZE550ML_TW_726x.xml.
Don't forget to reboot your phone before try 4G.
Unfortunately, i cannot test it by myself because my carrier work on 1800MHz which presents in all regions. So, i simply won't see any difference between regions.
Please report here about results.
Click to expand...
Click to collapse
Thank you for this information. I do not have a rooted ze551ml is there a way to root the ze551ml yet? I may have to attempt this when I get the moment. For now I will be monitoring this thread.
Mine is WW, I am in the US and I only get H+
sorrow777 said:
Thank you for this information. I do not have a rooted ze551ml is there a way to root the ze551ml yet? I may have to attempt this when I get the moment. For now I will be monitoring this thread.
Mine is WW, I am in the US and I only get H+
Click to expand...
Click to collapse
http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
Another quick update. I did both the first and second method in the first post, and LTE pops up sporadically. After doing the first method I lost signal (I wasn't even prompted to enter in my SIM PIN) until I also applied the second method, both times copying over the WW text over to the CN file. I've seen both band 2 and band 4, but it cuts in and out and the speeds are slow where I currently am. H+ also cuts in and out so I'm starting to wonder if I possibly got a phone with a bad radio. Ugh.
hkdmjack said:
Another quick update. I did both the first and second method in the first post, and LTE pops up sporadically. After doing the first method I lost signal (I wasn't even prompted to enter in my SIM PIN) until I also applied the second method, both times copying over the WW text over to the CN file. I've seen both band 2 and band 4, but it cuts in and out and the speeds are slow where I currently am. H+ also cuts in and out so I'm starting to wonder if I possibly got a phone with a bad radio. Ugh.
Click to expand...
Click to collapse
At which frequency bands does your ISP transmit FDD-LTE data?
Does anyone know why I can make calls but not receive them on my zenfone2 ? I have a T-Mobile Sim but I can do everything else just not receive call I need some help
Sent from my ASUS_Z00AD using XDA Free mobile app
graphO said:
At which frequency bands does your ISP transmit FDD-LTE data?
Click to expand...
Click to collapse
I'm receiving LTE signal on bands 2 and 4, but more prevalently 4.
And how can you see which LTE band is working?

Need HELP @ Note 3 ( SM-N9002 / SM-N9009 ) SIM2 Call Audio/Mic Routing & MagMa-NX ROM

Need HELP @ Note 3 ( SM-N9002 / SM-N9009 ) SIM2 Call Audio/Mic Routing & MagMa-NX ROM
Got my hands on this one beautiful piece of Samsung Galaxy Note3 SM-N9002 Dual-Sim, and it had this odd version of Chinese samsung rom on it, as it comes from factory, half apps installed that comes with it was in Chinese and had no play store etc and was on 4.xx android, so I went and did my research, found working TWRP, managed to install it OK, then tried few beautiful ROM versions and found MagMa-NX (note7 ported ROM) works wonderfully well, zero crashes etc etc and it also has kernel support for SM-N9002 during installation which I chose to use, all features work 100% and everything works ok, all but SIM#2 call audio.
I mean, I have signal on both sim cards simultaneously OK, I can make and receive calls and all would seem ok, but when dialed to or from SIM#2 there is no audio coming out from earpiece or loudspeaker and mic dont seem to activate as even if I try to record call which feels like muted for both caller and receiver ends, call audio recorder while recording does not pick up any sound trough phone microphones, so I think its something to do with settings in some file not done right or else I dont know what I could be doing wrong.
both sim cards worked 100% ok before ROM flash, but now I'm lost because I cant even flash back to old stock rom, and yes I have gathered original android 4.xx rom but it fails flashing via ODIN every time, so my best bet is on doing some DIY on current MagMa-NX note7 port rom... I wonder if there are any fellows who I could buy the paypal-beer for great help sorting me out on this DIY project? Please PM me or post here if you feel like you could collaborate in resolving this dilemma for me... would highly appreciate folks
I will keep an eye out
I think I figured something. Everytime I attempt to make a phone call on this, I get to choose from which sim card should I dial, #1 or #2 , but what I have noticed now is that I am being asked "SIM1" or "Slot2" ... SLOT 2 I thought? That may be the reason that audio routing doesnt work well for this... tried searching build.prop but this string is not there and I just dont know where to search for this string to get this fixed, anybody can chime in?
Thanks
Did you figure it out ? As i have the same problem with the same rom in addition that when i call anyone and he is on a call i don't get notified with " call waiting
Mr.Ultimate said:
Got my hands on this one beautiful piece of Samsung Galaxy Note3 SM-N9002 Dual-Sim, and it had this odd version of Chinese samsung rom on it, as it comes from factory, half apps installed that comes with it was in Chinese and had no play store etc and was on 4.xx android, so I went and did my research, found working TWRP, managed to install it OK, then tried few beautiful ROM versions and found MagMa-NX (note7 ported ROM) works wonderfully well, zero crashes etc etc and it also has kernel support for SM-N9002 during installation which I chose to use, all features work 100% and everything works ok, all but SIM#2 call audio.
I mean, I have signal on both sim cards simultaneously OK, I can make and receive calls and all would seem ok, but when dialed to or from SIM#2 there is no audio coming out from earpiece or loudspeaker and mic dont seem to activate as even if I try to record call which feels like muted for both caller and receiver ends, call audio recorder while recording does not pick up any sound trough phone microphones, so I think its something to do with settings in some file not done right or else I dont know what I could be doing wrong.
both sim cards worked 100% ok before ROM flash, but now I'm lost because I cant even flash back to old stock rom, and yes I have gathered original android 4.xx rom but it fails flashing via ODIN every time, so my best bet is on doing some DIY on current MagMa-NX note7 port rom... I wonder if there are any fellows who I could buy the paypal-beer for great help sorting me out on this DIY project? Please PM me or post here if you feel like you could collaborate in resolving this dilemma for me... would highly appreciate folks
I will keep an eye out
Click to expand...
Click to collapse
Which CSC did you choose?
I did not figure anything out guys... as I was trying to get this working, I tried every CSC option possible... none worked. Which should have been the one that's working for this models?
in fact Im thinking of selling this beauty of note3, its almost new... in case someone interested I have it... because I would love note7 port rom on this, and nothing else... PS I could live with it being just single-sim option, it works but not perfect as sim #2 is useless then... signal there and texts only works for it as described above...
at the moment its on stock adroid 5.0 and its all 100% ok and fine, flawless, but its boring!
Mr.Ultimate said:
I did not figure anything out guys... as I was trying to get this working, I tried every CSC option possible... none worked. Which should have been the one that's working for this models?
in fact Im thinking of selling this beauty of note3, its almost new... in case someone interested I have it... because I would love note7 port rom on this, and nothing else... PS I could live with it being just single-sim option, it works but not perfect as sim #2 is useless then... signal there and texts only works for it as described above...
at the moment its on stock adroid 5.0 and its all 100% ok and fine, flawless, but its boring!
Click to expand...
Click to collapse
Well, i know that mixer paths are different on single sim and dual sim phones.
Can you extract from stock rom the file "/system/etc/mixer_paths.xml" and overwrite the one in custom rom ?
I think I tried something similar if not exact with no success .. let me repeat the process just in case...
PS also, I will try and dump both versions of these files. Is there anything else I may need to dump from stock rom 5.0 rom?
Mr.Ultimate said:
I think I tried something similar if not exact with no success .. let me repeat the process just in case...
PS also, I will try and dump both versions of these files. Is there anything else I may need to dump from stock rom 5.0 rom?
Click to expand...
Click to collapse
There are some specific binaries and libs, but i'm pretty sure magma rom already inject them during flash when you select n9002 as variant.
Dumping the CSC folder is a good idea too.
zlazaar said:
There are some specific binaries and libs, but i'm pretty sure magma rom already inject them during flash when you select n9002 as variant.
Dumping the CSC folder is a good idea too.
Click to expand...
Click to collapse
cool, which is the csc folder to be exact? will there should there be any conflicts between 5.0 stock android and 6.0 in magma rom when doing CSC trick?
thanks
Mr.Ultimate said:
cool, which is the csc folder to be exact? will there should there be any conflicts between 5.0 stock android and 6.0 in magma rom when doing CSC trick?
thanks
Click to expand...
Click to collapse
Path : /system/csc
Indeed, conflits may happen. But just dump it and let we examine it.
Ok here is what I managed to try, I backed up stock rom android 5.0 all working state mixer files from etc dir, then flashed magma rom again, backed up those same files for restoration to working state, replaced files with ones extracted while on 5.0 stock android, reboot device, no sound whatsoever, phone wont even buzz keypad dialtones or connect dial phonecalls just hangs. So I went and restored back original magmanx rom mixer files, reboot, but still no success... so now I have just finished restoring 5.0 again, will dump csc folder and share with you. will also need to charge my battery a bit because @ 30% cant expect much to happen when flashing magma nx...
Thanks for the help amigo!!!
Alright, tried merging csc from 5.0 to magmanx 6.0, no luck. then tried after this to merge mixer file from 5.0 to magmanx 6.0 , no luck, back at square1....
files attatched both versions... obviously something wasnt done right from looong time ago and had never been reported, been forgotten... in regards of 9002 users..
https://forum.xda-developers.com/attachment.php?attachmentid=4154927&stc=1&d=1495202856
Mr.Ultimate said:
Alright, tried merging csc from 5.0 to magmanx 6.0, no luck. then tried after this to merge mixer file from 5.0 to magmanx 6.0 , no luck, back at square1....
files attatched both versions... obviously something wasnt done right from looong time ago and had never been reported, been forgotten... in regards of 9002 users..
https://forum.xda-developers.com/attachment.php?attachmentid=4154927&stc=1&d=1495202856
Click to expand...
Click to collapse
Indeed, the mixer_paths of TW6 is missing the whole part concerning "cp2" (second sim).
I'm not a reel dev but i tried to add missing parts from TW5.
Can you please try the attached mixer_paths on magma ? (don't touch csc).
zlazaar said:
Indeed, the mixer_paths of TW6 is missing the whole part concerning "cp2" (second sim).
I'm not a reel dev but i tried to add missing parts from TW5.
Can you please try the attached mixer_paths on magma ? (don't touch csc).
Click to expand...
Click to collapse
amazing, will try in few mins
no success, exact same fail of global audio post merging files... any more ideas... ? really appreciate your effort man, really do!
Mr.Ultimate said:
no success, exact same fail of global audio post merging files... any more ideas... ? really appreciate your effort man, really do!
Click to expand...
Click to collapse
Did you checked correct permissions before reboot ?
I'm afraid the problem is deeper than mixer paths.
I'll try to digg more.
I enable root explorer in third party file manage, grant permission, copy file from sd card to system/etc, prompt to overwrite -grant, overwrite complete, power off phone from power-button menu, power on, done. is this bad/incorrect procedure? magmanx has root from stock, when I navigate root dir I get access grant prompt, I grant it and then I can modify whatever.
please let me know what else I could do? maybe there are specific files I could look in to dump out of working 5.0 rom? Thanks!
or maybe just directory content filenames that could/would make sense by their name etc?
its weird, I think its something to do with the kernel itself... maybe Im wrong, but I dont think 9002/9008 kernels were ever made properly to be tested thus the errors... I cant even find any other kernels for 9002 other than included in magmanx and it aint working well anyway
Mr.Ultimate said:
I enable root explorer in third party file manage, grant permission, copy file from sd card to system/etc, prompt to overwrite -grant, overwrite complete, power off phone from power-button menu, power on, done. is this bad/incorrect procedure? magmanx has root from stock, when I navigate root dir I get access grant prompt, I grant it and then I can modify whatever.
please let me know what else I could do? maybe there are specific files I could look in to dump out of working 5.0 rom? Thanks!
or maybe just directory content filenames that could/would make sense by their name etc?
its weird, I think its something to do with the kernel itself... maybe Im wrong, but I dont think 9002/9008 kernels were ever made properly to be tested thus the errors... I cant even find any other kernels for 9002 other than included in magmanx and it aint working well anyway
Click to expand...
Click to collapse
The file "mixer_paths.xml" must have permission set to 0644 (like other files in /system/etc directory).
And try darklord Kernel.
6044 is as per read/write permissions for user enabled, as per this link http://permissions-calculator.org/decode/0644/ , I assume these permissions will auto set after moving replacing file do they not?
Where do I obtain the darklord kernel? I was pretty sure it comes with it... let me re-do the rom and take some snips as I go
Mr.Ultimate said:
6044 is as per read/write permissions for user enabled, as per this link http://permissions-calculator.org/decode/0644/ , I assume these permissions will auto set after moving replacing file do they not?
Where do I obtain the darklord kernel? I was pretty sure it comes with it... let me re-do the rom and take some snips as I go
Click to expand...
Click to collapse
Sorry i just noticed you already have darklord kernel.
And set permission like other files in this directory (if not already done by your file manager).

Categories

Resources