Hello everyone, I just upgraded my phone to Dual SIM Marshmallow yesterday while leaving the bootloader intact and without losing any data (as far as I can tell). Yes, this is a dirty flash operation, so proceed with caution.
First a little bit of gibberish: Because I got tired of waiting around for the European 6.0 update, and also having interest in the Dual SIM function anyway, I inspected the gpt.bin of both XT1562 RETEU and XT1562 RETASIA with gpt_parser.py
Turns out: the userdata partition wouldn't suffer from misalignments by flashing a different partition table:
India gpt.bin gpt_parser.py output:
Code:
[-] Partition 42
[-] Partition type GUID: 1B81E7E6-F50D-419B-A739-2AEEF8DA3335
=> Partition type: unknown partition, UNKNOWN
[-] Unique partition GUID: 86E734CA-D096-B657-DA2D-095F241A084A
[-] First LBA: 7634944
=> Disk Offset: 0xE9000000
[-] Last LBA: 7634943
=> Disk Offset: 0xE8FFFE00
[-] Attribute flags: 1152921504606847000, UNKNOWN
[-] Partition Name: userdata
Europe gpt.bin gpt_parser.py output:
Code:
[-] Partition 42
[-] Partition type GUID: 1B81E7E6-F50D-419B-A739-2AEEF8DA3335
=> Partition type: unknown partition, UNKNOWN
[-] Unique partition GUID: 0C44D2CF-AFB9-7EEE-2FAE-03E3E1D02EB8
[-] First LBA: 7634944
=> Disk Offset: 0xE9000000
[-] Last LBA: 7634943
=> Disk Offset: 0xE8FFFE00
[-] Attribute flags: 1152921504606847000, UNKNOWN
[-] Partition Name: userdata
If you're not scared by the above feel free to proceed. The following worked for me, keep in mind that I can't know for sure if this will work out with your setup, so if you follow these instruction, you do so at your own risk:
1. I started out with LPD23.118-10 XT1562 RETEU with locked bootloader - userdata was encrypted.
2. I flashed LPD23.118-10 XT1562 RETASIA (a.k.a. Indian, and the version number is important because the OTA upgrade will only work with that - there was a faster google drive link somewhere I can't find it, sorry, will update the post if someone sends me a link) firmware like described here, but note the crucial difference:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
fastboot erase userdata is missing before the reboot because we want to keep our current settings and apps data that can't be backed up (looking at you org.thoughtcrime.securesms)
3. Boot normally, etc. it will optimise some apps because cache was erased etc. Dual SIM should be enabled now!
4. If you want to pop into the Marshmallow world without waiting till you get OTA notifications, grab the update, place it in the root directory of your SD card, and check for system updates.
5. Wait a long time while it upgrades, boots and optimises.
6. Happily check out your Android version: 6.0 and System version: 25.11.18.lux_retasia_ds.retasiaall.en.03 reteu (yes, apparently it recognises that it's a reteu phone - a little scary but everything is fine for now)
7. ???
8. PROFIT
I already switched my data/voice plan around making use of the Dual SIM ability. It works great and now I pay a couple euros less while keeping my old number! Keep in mind though, you should use two different network providers, if the same provider sees an IMSI try to log in twice poop might get shagged up. (Also, if you use an MVNO, make sure the infrastructure providers they use are also different)
Play safe and happy (dirty) flashing
Edit: fixed link
mxnd said:
...
1. I started out with LPD23.118-10 XT1562 RETEU with locked bootloader - userdata was encrypted.
2. I flashed LPD23.118-10 XT1562 RETASIA (a...
Click to expand...
Click to collapse
From where did you download that LPD23.118-10 XT1562 RETASIA ROM.
I can't find it on filefactory site.
00sand00 said:
From where did you download that LPD23.118-10 XT1562 RETASIA ROM.
I can't find it on filefactory site.
Click to expand...
Click to collapse
Here moto.shreps.fr/?dir=Moto%20X%20Play%20%28lux%29/rom/stock
What should I do if I want to make the same, but with Single-SIM and clean install?
@mxnd
Dude, you rock.
Converted uk x play single to dual sim and everything works. Data intact
Now going for marshmallow
Updated marshmallow India.
So far so good, everything seems ok.
PanOptikum said:
What should I do if I want to make the same, but with Single-SIM and clean install?
Click to expand...
Click to collapse
As far as I can tell, only dual sim phones have gotten a 6.0 update so far. No idea what takes them so long
mxnd said:
Hello everyone, I just upgraded my phone to Dual SIM Marshmallow yesterday while leaving the bootloader intact and without losing any data (as far as I can tell). Yes, this is a dirty flash operation, so proceed with caution.
Click to expand...
Click to collapse
Awesome Job Mate!!!
At the link there is a retasia marshmallow firmware too. Is it not easier to upgrade directly to marshmallow instead of the asian version of lollipop and then to marshmallow with the ota update
Jeso said:
At the link there is a retasia marshmallow firmware too. Is it not easier to upgrade directly to marshmallow instead of the asian version of lollipop and then to marshmallow with the ota update
Click to expand...
Click to collapse
Yeah, I haven't downloaded and/or inspected the gpt partitioning of that. I would assume everything would stay in the same place there too, but verifying with the python script above is probably a good idea. I thought this was the safest route and it worked If anybody experiments, I'll happily update the post.
bablu048 said:
Here moto.shreps.fr/?dir=Moto%20X%20Play%20%28lux%29/rom/stock
Click to expand...
Click to collapse
Is taht the dual sim version? in the code name does not apears "DS"
kamarilla said:
Is taht the dual sim version? in the code name does not apears "DS"
Click to expand...
Click to collapse
yes all indian versions are dual sim.
you can get it from here also https://github.com/motoxplay/stock
Superb popped my tray out and there was a blank got it out
And there's a nice picture sim 2 underneath :good:
Where can I get firmware for asiaretail_pacific?
Excellent guide
I'm following XDA since several years but I never posted.
I followed your guide and with a bit of attention I was able to reflash my Moto X Play from single sim eu to dual sim asia/eu.
I moved from XT1562_LUX_RETEU_6.0.1_MPD24.107-52 (single sim) to XT1562_LUX_RETASIA_DS_6.0.1_MPD24.107-52 (dual sim dual standby).
A check with gpt_parser.py gives same result than on original post, so I decided to try this.
This is the exact command sequence I gave (only differs in the /sparsechunk/ section because it has 9 chunks instead of 7 of the original guide. Note that EU firmware has 8 chuncks and asia has 9 chunks, so be careful and inspect zip package before flashing).
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
Now phone is working, SIM1 is correctly registered and now I have a dual sim phone. I don't have a second sim yet so I can't test, but in the settings there is the additional SIM menu.
Some questions:
* IMEI of SIM2 is zero. Is this a problem with carriers? Is there a way to have an IMEI for SIM2 too?
* Should the phone see the update to MPD24.107-70 or not? Now it is not seeing it (software up to date)
Thank you all for the guide and for the answers.
EDIT: After some hours, the phone stopped detecting SIM1. So I had no SIM working. After some readings I flashed the single sim european software back. I still need to read something to properly achieve this conversion. Every suggestion is appreciated
acehigh1971 said:
I'm following XDA since several years but I never posted.
I followed your guide and with a bit of attention I was able to reflash my Moto X Play from single sim eu to dual sim asia/eu.
I moved from XT1562_LUX_RETEU_6.0.1_MPD24.107-52 (single sim) to XT1562_LUX_RETASIA_DS_6.0.1_MPD24.107-52 (dual sim dual standby).
A check with gpt_parser.py gives same result than on original post, so I decided to try this.
This is the exact command sequence I gave (only differs in the /sparsechunk/ section because it has 9 chunks instead of 7 of the original guide. Note that EU firmware has 8 chuncks and asia has 9 chunks, so be careful and inspect zip package before flashing).
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
Now phone is working, SIM1 is correctly registered and now I have a dual sim phone. I don't have a second sim yet so I can't test, but in the settings there is the additional SIM menu.
Some questions:
* IMEI of SIM2 is zero. Is this a problem with carriers? Is there a way to have an IMEI for SIM2 too?
* Should the phone see the update to MPD24.107-70 or not? Now it is not seeing it (software up to date)
Thank you all for the guide and for the answers.
EDIT: After some hours, the phone stopped detecting SIM1. So I had no SIM working. After some readings I flashed the single sim european software back. I still need to read something to properly achieve this conversion. Every suggestion is appreciated
Click to expand...
Click to collapse
I did exactly the same a few days ago. I flashed the Asia firmware and then I flashed RR (a custom rom) and forced second SIM with the fastboot command and now it looks like this:
(I cropped the IMEI SIM1 out.)
And it's working like this. Currently I'm using only 1 SIM but I tested it with a second SIM and both works.
I got the 1562 (EU/Germany) version.
I hope that helped you!
Sent from my XT1562 using XDA-Developers mobile app
So you didn't have problems of SIM1 not detected?
Is the sim1 working ok?
My question is: probably asia firmware contains a different modem partition and it does not enable all the frequencies of my european phone.
acehigh1971 said:
So you didn't have problems of SIM1 not detected?
Is the sim1 working ok?
My question is: probably asia firmware contains a different modem partition and it does not enable all the frequencies of my european phone.
Click to expand...
Click to collapse
No, SIM1 is working with both SIM cards (congstar and O2).
Hmm, I don't think so, because it worked well for me too, but I can't confirm this 100%.
Sent from my XT1562 using XDA-Developers mobile app
Ok,
I did the procedure again from the beginning. After reboot and android optimization, I removed SIM card from slot 1 and booted again without sim.
Then shutdown, inserted SIM and then powered on. I got a notification that a new sim is present and I can configure it. From then it worked fine with one sim (I only have one at the moment).
Somewhere I read there is a bug with some custom firmware not reading both SIMs, and probably I met this bug also with an original firmware.
BUT ANYHOW, there are some serious drawbacks to this stock firmware replacements:
1) IMEI of SIM2 is 0. I don't know which operators block IMEI 0 and which don't care. Googling for info does not provide meaningful results for my country (IT). But in general this could be a problem, especially if you go abroad and you don't know the details for each operator.
2) OTA do not come if, like in my case, I have a RETASIA reteu mixed device.
There are some clever posts in this thread: http://forum.xda-developers.com/moto-x-play/help/enabling-dual-sim-single-sim-devices-t3225546 where these notes are pointed out, with practical tests.
Based on this, for the moment I decided to go back to RETEU reteu single sim sw... sigh.
He cant go back, the Asia DS one is newer as the RETEU. Only with open Bootloader he can install a older one. (there is a thread in General also.)
Got no Problems with 2 Sims (O2 and german Telekom) with the DS FW on 2 RETEU Play Devices (only with Custom FW )but there is a command to fix it.
On one Device (open Bootloader and out of Warrenty i´m back on older EU FW).
He have to wait on a newer EU FW or open the bootloader (with risks) if he would back to.
(btw.: i read on some Countrys is not legal to use a Sim with no Imei + the second Sim is not detected.)
edit: maybe it would be a good idea to wipe the whole device, and start fresh?
Already reverted to reteu
Assuming you are referring to me (... He can't go back ...), I already switched back to reteu firmware.
I did all these experiments with same build level for both versions (reteu and retasia): MPD24.107-52.
This confirms me 2 things:
* Frankenstein phones like this do not get ota updates (during the time I stayed with retasia I didn't receive upgrade notification (even checking manually). And I should, because there is a new sw for retasia already available (MPD24.107-70).
* If I stay with the same build level, the partition scheme is the same so I can go back and forth between versions, with locked bootloader and without erasing userdata. The benefit in doing this is zero for me at the moment, but this is another story. It was an interesting experiment. I learned a lot.
XT1541 Android 6.0.1 MPIS24-107-55-2-5
Phone upgraded using @lost101 factory image.
Flashing done manually excluding erase of userdata and upgrade of bootloader.
Everything is working fine, except upgrading of modem partition (NON-HLOS.bin).
If I upgrade modem partition, phone boots, Android starts without issues but, when I enter PIN of SIM and it registers network, after some minutes, phone resets.
To fix the issue, I must restore dd image of previous modem partition.
So, I'm stuck with baseband M8916_2020610.17.03.21.26R OSPREY_EMEA_CUST.
Inspecting in logcat, I see that last messages before reboot are coming from Widewine processes.
Any suggestions?
Keep in mind that I DON'T WANT to factory reset and/or wipe data partition.
Modem stack (NON-HLOS.bin and fsg.mbn, along with clearing modemstX partitions) must be done as a set and must match the kernel... You can't just flash a different baseband, it must match your ROM is stock, although you could try with a third party kernel.
I've cleared modemst1 and modemst2 partitions.
Also, my actual fsg.mbn is the latest.
With original and unchanged NON-HLOS.bin, I've upgraded system to Marshmallow without troubles and I've used various kernels (stock and 3rd party) without issues.
The problem relies only with the newest NON-HLOS.bin after LP. I'm unable to flash ANY of these.
Before installing custom ROM I was erasing the partition of my phone using fastboot commands.
Curiously I used
Code:
fastboot erase all
command. It erase all my data and partitions from the phone memory.
After the when I installed custom ROM is saw network is not working, then I checked *#06# and noticed IMEI1 = 0 and IMEI2 = 0.
Then I Downloaded the Stock ROM and flashed it. But still the IMEI = 0. I have also flashed
Code:
fastboot flash modem NON-HLOS.bin
, but still there IMEI = 0. :crying:
Guys, I request you please help me over here to change the IMEI Number of my Moto G3 XT1550.
Did you find any solution for this? I lost my IMEI with lineageos17.1 OTA update. Need help for me.
i have a few questions, and it's stumping me bad. i got a pixel sailfish on ebay and its in a bootloop. i have tried flashing factory images, ota's, fastbooting twrp and factory resetting and still...loop. sometimes in twrp it will flash the rom, but will freeze and random reboot. i have tried formatting system, vendor and then flashing factory images and to no avail...bootloop. one time i was able to flash nougat factory, and it actually booted. i went ahead and fastbooted twrp...then bam...bootloop again. i need some help. even when i boot into each slot, there is different baseband versions and bootlooder version on each slot. is this normal? should not both slots have same bootloader and baseband version? could this be my bootloop issue?
to reiterate, when i was able to boot the nougat factory, i had fastboot -w, format system and vendor then flashed the nougat fw and it stuck. now i have nothing. can anyone help?
Here are some pics of bl screens. this is result after formatting userdata and flashing latest stock firmware. android 10.
also noted that sometimes when trying to format system, it says no dtbo img. i notice on fw flash that it says no dtbo.img on the flash.
now when i flash nougat, i get "ramdump writing to ext4 file"
it didnt do this when the same nougat fw was successful
Rootmaster906 said:
now when i flash nougat, i get "ramdump writing to ext4 file"
it didnt do this when the same nougat fw was successful
Click to expand...
Click to collapse
You flashed your firmware to both slots and still show different bootloader on each?
Rootmaster906 said:
Here are some pics of bl screens. this is result after formatting userdata and flashing latest stock firmware. android 10.
also noted that sometimes when trying to format system, it says no dtbo img. i notice on fw flash that it says no dtbo.img on the flash.
Click to expand...
Click to collapse
Sailfish doesn't have a dtbo.img. Just system, system_other, boot, and vendor so don't worry about that.
I have xiaomi mi s2. And i have chinese miui that i wanted to change to global version. I did it but when i was turning it on, there was xiaomi logo, then i saw lock screen for few seconds and then it turned off. I searched for solution but i screwed up and now i am stuck on fastboot mode. And i tried to fix that too but nothing works.
If someone have any ideas i will be very happy.
I am afraid that you cannot flash Global MIUI version to a Chinese model.
You have to flash
- Chinese rom to Chinese model;
- Global version customized to Chinese model (which, unfortunately, I do not have links...).
Hope you find one shortly.
To fix your issue, first of all, back up your data if still possible.
Boot into fastmode
-fastboot erase system
- fastboot erase cache
- fastboot erase userdata
- fastboot erase recovery
Be careful: this method will wipe out all your data.
then, clean-flash a rom.