Hello, I was trying to flash gpe rom to my MOTO G, it didnt work so I flashed sysem version 14.85.2.fakcin_umtsds.asiaretail.en.03, WIFI works, but non of the sims work.
I was trying to "radio on" in *#*#4363#*#* but nothing.
I worked with this article http://forum.xda-developers.com/showthread.php?t=2542219
can someone please give me a modem to flash? or just help me somehow?
_______________________________
there is just one rom that worked properly and showed the two sims. but, the modem as I already said didnt work so I took a NON-HLOS.bin from another rom and flashed it
HTML:
fastboot flash modem NON-HLOS.bin
fasboot erase modemst1
fastboot erase modemst2
fastboot reboot
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.
Hey. So I recently rooted my G7 Power via the Magisk method shared by u/diversenerd. After soft-bricking the phone in my first attempt and restoring it to stock, I was successful. Unfortunately, I've run into a problem: I no longer can use the phone as an actual phone.
I have two SIM cards: Mint for my main driver (Moto G7 Power), and Ting for my backup (Moto G5 Plus). After double-checking that the SIM card is inserted into the Power correctly, I checked to make sure something wasn't wrong with the SIM itself. Both the Ting and Mint SIMs work fine in the G5 Plus, but neither are recognized in the G7 Power. What can I do to resolve this issue?
What firmware?
maddstealth said:
Hey. So I recently rooted my G7 Power via the Magisk method shared by u/diversenerd. After soft-bricking the phone in my first attempt and restoring it to stock, I was successful. Unfortunately, I've run into a problem: I no longer can use the phone as an actual phone.
I have two SIM cards: Mint for my main driver (Moto G7 Power), and Ting for my backup (Moto G5 Plus). After double-checking that the SIM card is inserted into the Power correctly, I checked to make sure something wasn't wrong with the SIM itself. Both the Ting and Mint SIMs work fine in the G5 Plus, but neither are recognized in the G7 Power. What can I do to resolve this issue?
Click to expand...
Click to collapse
Assuming you flashed the right firmware.
try
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
sd_shadow said:
Assuming you flashed the right firmware.
try
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Click to expand...
Click to collapse
Very much still a noob with messing with flashing and such. I'm assuming I need to extract the firmware zip into platform_tools prior to inputting these commands in Command Prompt?
Grim truth said:
What firmware?
Click to expand...
Click to collapse
... I'm sorry for my ineptness, how do I find the firmware version? I don't see it anywhere in the system settings. Do I have to use ADB to locate it?
maddstealth said:
... I'm sorry for my ineptness, how do I find the firmware version? I don't see it anywhere in the system settings. Do I have to use ADB to locate it?
Click to expand...
Click to collapse
Join us in the telegram group I can help you better
Grim truth said:
Join us in the telegram group I can help you better
Click to expand...
Click to collapse
Can't do that when telegram requires a mobile number to sign up...
maddstealth said:
Can't do that when telegram requires a mobile number to sign up...
Click to expand...
Click to collapse
Ah telegram has a computer app as well. But I had your issue. It's the baseband, you need to flash a newer firmware if your not on june get on june. The firmware ends with 134. If you need the link let me know
Grim truth said:
Ah telegram has a computer app as well. But I had your issue. It's the baseband, you need to flash a newer firmware if your not on june get on june. The firmware ends with 134. If you need the link let me know
Click to expand...
Click to collapse
I didn't mean to sound mean, I was just away from home when I tried to sign up for Telegram.
The link would be helpful, just to make sure I don't mess this up. I can handle the flashing from there.
maddstealth said:
I didn't mean to sound mean, I was just away from home when I tried to sign up for Telegram.
The link would be helpful, just to make sure I don't mess this up. I can handle the flashing from there.
Click to expand...
Click to collapse
No worries bud. https://mirrors.lolinet.com/firmware/moto/ocean/official/
There's the link they will have the current firmware for your carrier
Problem Solved!
Grim truth said:
No worries bud. https://mirrors.lolinet.com/firmware/moto/ocean/official/
There's the link they will have the current firmware for your carrier
Click to expand...
Click to collapse
Hey, just checking in. I just applied the modem erasure and replacement, and that patched things right up! Many thanks to you, Grim! Same to you, Sd Shadow.
which firmware is for the Unlocked US version?
model PAEB0006US
I flashed RETUS, and i have the No sim card error.
i ran these...:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Still no sim card error.
endleesss said:
which firmware is for the Unlocked US version?
model PAEB0006US
I flashed RETUS, and i have the No sim card error.
i ran these...:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Still no sim card error.
Click to expand...
Click to collapse
You flashed full firmware?
Okay, so the phone was my wife's, had LTE with stock firmware.
Got her a new phone so I took this one and did full flash from fastboot using the latest retail image (used lenovo restore app).
Flashed lastest Lineage OS image. Can't get anything other than 3G.
Flashed latest stock image both with Lenovo, AND manually via fastboot.
Still no LTE. (sim has LTE on my moto x4 so the sim is fine)
Flashed modem from RETAIL instead of RETUS. still no LTE.
Restored TWRP backup of Lineage... of course, no LTE.
Just for giggles, I put my wife's sim card in to test. still no LTE.
My guess, baseband issue?
If I select LTE under preferred network type, I get LTE, but phone and SMS don't work.
If I have it on Global it doesn't work, if I have it on LTE/CDMA/EvDo/GSM/WCDMA I get phone and 3g but no LTE and a lot of times the signal just drops.
Anyone have ideas?
I have a EU version (XT1955-4), and I didn't get any modem or GPS with lineageos. Since I had flashed lineage to slot b and I had overlooked the "copypartitions" part, the modem didn't work at all, since it was an old version or the wrong one.
I did the following:
- Downloaded my "stock" firmware version, for me RETEU.
- Boot to fastboot
- flash the following from the stock firmware zip to current slot:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Modem then worked including LTE. My guess is that "RETUS" should be the correct one in the United States.
vasq10 said:
I have a EU version (XT1955-4), and I didn't get any modem or GPS with lineageos. Since I had flashed lineage to slot b and I had overlooked the "copypartitions" part, the modem didn't work at all, since it was an old version or the wrong one.
I did the following:
- Downloaded my "stock" firmware version, for me RETEU.
- Boot to fastboot
- flash the following from the stock firmware zip to current slot:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Modem then worked including LTE. My guess is that "RETUS" should be the correct one in the United States.
Click to expand...
Click to collapse
unfortunately I have tried that, and to no avail.
Are you sure you flashed it to both slots?
Pretty sure. I'm thinking I might try a full wipe using the Lenovo software first, and see what happens. When I select in the options "CDMA/EvDo Auto" I get 3G with phone, and when I do "LTE" I get LTE but no phone. I have no options for VoLTE in the settings. Global won't connect to anything. So It's obvious that the OS/firmware is capable of connecting to the specified bands.