Related
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.
Moto g7 play Android 9 and 10 Factory Firmware Stock Images
Info Updated on 23-11-2020
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi there. I have found the moto g7 play stock images mirrored in lolinet servers for Android 9, and from motorola servers for Android 10. Go and download the image you need
Android 9 Stock direct download links
Here is the repository of stock ROMs for g7 play codename chanel from Lollinet
Android 10 Stock direct download link
Finally, Android 10 has arrived!! Here is the link to the Android 10 stock rom for moto g7 play, from Motorola Cloud servers.
The download stops sometimes but can be ressumed. I suggest use Free Download Manager, Internet Download Manager (IDM) or Flashget for download without interrrumptions.
https://bit.ly/381Y2rE
---------------------------------------------------------------------------------------------------------------
How to flash your Stock Android 9 or Android 10 ROM:
If you can't get your Android 10 update via OTA, follow these instructions:
Step 0: Install Motorola Drivers through Motorola Device Manager, you can download official companion here
Step 1: Extracting Fastboot and Firmware Images:
Extract zip for chosen Firmware Image to a folder with a simple directory structure. For example: C:\motog7play-firmware\
Download the adb fastboot from Google official links according to your operating system:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
https://dl.google.com/android/repository/platform-tools-latest-linux.zip
And unzip into the firmware folder
Step 2. Reboot the phone into 'Bootloader mode' and preparing PC for flashing
In Windows there's two ways:
2.1 Entering Fastboot mode:
------------------------------------
i) The 'hardware' way.
a) Unplug the USB cable and power off the phone.
b) Press and hold 'Volume down' then power on the phone.
c) Connect USB cable to your computer.
ii) The 'software' way.
a) Enable developer mode on the Moto g7 play (Settings-> 'About Phone'. Tap 7 times on 'Build Number')
b) Enable USB debugging. (Settings -> 'Developer options' -> 'USB Debugging' -> check)
c) Connect phone to computer via USB, you should see a new ADB device detected and drivers installed.
d) Open Command Prompt, navigate to the Firmware / ADB folder (i.e CD C:\motog7_firmware ) and type:
Code:
adb reboot-bootloader
In Linux:
2.2 Linux:
Entering Fastboot mode:
------------------------------------
i) The 'hardware' way.
a) Unplug the USB cable and power off the phone.
b) Press and hold 'Volume down' then power on the phone.
c) Connect USB cable to your computer.
ii) The 'software' way. (Requires ADB to be already installed - see below)
a) Enable developer mode on the Moto G (Settings-> 'About Phone'. Tap 7 times on 'Build Number')
b) Enable USB debugging. (Settings -> 'Developer options' -> 'USB Debugging' -> check)
c) Connect phone to computer via USB
d) Navigate to the Firmware folder, right-click and open terminal and type:
Code:
adb reboot-bootloader
Installing ADB / Fastboot:
-------------------------------------
Flashing via Linux LiveCD: (Put factory firmware files on an external usb drive / pen)
--------------------------------
a) Download some Ubuntu LiveCD latest distro
b) Burn to DVD or write to USB pen
c) Restart PC, Boot from DVD into Ubuntu
d) Open Terminal and type the following:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
e) Test fastboot by typing: sudo fastboot devices
You should see:
<serial number> fastboot
f) You are now ready to flash the fastboot files
Step 3: Write Fastboot Commands for Android 9
Do commands manually, one at a time - checking that each one returns an [OKAY] in the cmd (windows) or konsole (linux)
NOTE: Do not simply copy and paste these commands! - system.img_sparsechunks may differ in number and name.
Always check contents of folder you're working with. You must flash all of the sparsechunk files you have.
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot reboot
Step 3 alternative: Write Fastboot Commands for Android 10
Do commands manually, one at a time - checking that each one returns an [OKAY] in the cmd (windows) or konsole (linux)
NOTE: Do not simply copy and paste these commands! - system.img_sparsechunks may differ in number and name.
Always check contents of folder you're working with. You must flash all of the sparsechunk files you have.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash logo logo.bin
fastboot flash dtbo dtbo.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase DDR
fastboot erase cache
fastboot erase carrier
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Regional Variants and their Android 9 download Links
The moto g7 play has seven known variants: XT1952-1 (Europe), XT1952-2 (Latin america), XT1952-3 (United States), XT1952-4 (United states, Sprint carrier), XT1952-6 (United states, Metro PCS carrier), XT1952DL (United States, Tracfone carrier) and XT1952-T (United States, T-Mobile carrier). It is also known in some US Carriers as moto g7 optimo
FCC technical data can be found here
Official Android 9 ROMS suggested for XT1952-2 (Latin America Dual Sim)
Latest build: April 2020 security patch
Retail Generic ROM - RETAIL Channel (1.7 Gb) (April 2020 security patch): CHANNEL_RETAIL_9.0_PPYS29.105-134-12_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
This ROM works and fit mostly on all latin american countries, and also may work in another g7 play variants
View old ROM links for other countries here
Argentina (2 Gb) (October 2019 security patch): XT1952-2_CHANNEL_RETAR_9.0_PPYS29.105-134-2_cid50_subsidy-DEFAULT_regulatory-XT1952-2-ARGENTINA_CFC
Brasil (2 Gb) (October 2019 security patch): XT1952-2_CHANNEL_RETBR_9.0_PPYS29.105-134-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Costa Rica (2 Gb) (October 2019 security patch): XT1952-2_CHANNEL_RETLA_9.0_PPYS29.105-134-4_cid50_subsidy-DEFAULT_regulatory-XT1952-2-COSTARICA-DS_CFC
México (2 Gb) (October 2019 security patch: XT1952-2_CHANNEL_OPENMX_9.0_PPYS29.105-134-2_cid50_subsidy-DEFAULT_regulatory-XT1952-2-MEXICO_CFC
Regional Variants and their Android 10 download Links
Apparently, the OTA released rom works like a charm (at least in my Moto g7 play XT1952-2 model) because is a non attached to carrier ROM, being very closer to the Retail ROM
Official Android 10 ROM for XT1952-2 (Latin America Dual Sim)
Latest build: October 2020 security patch
Retail Generic Android 10 ROM - RETAIL Channel (1.8 Gb) (October 2020) from Lolinet Mirrors (Download Latest): https://mirrors.lolinet.com/firmware/moto/channel/official/RETAIL/
This ROM worked without problems with Colombian mobile operators (I tested each different simcard carriers from my relatives). So, there's no excuse to work in other latin american countries, and also may work in another g7 play variants
Success verbatim for the stock image on XT1952-6 (United states, Metro PCS carrier) purchased at a store a week ago.
CHANNEL_RETAIL_9.0_PPYS29.105-134-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Only hiccup was
fastboot flash boot boot.img
Sending 'boot_a' (32768 KB) OKAY [ 0.887s]
Writing 'boot_a' (bootloader) Image signed with key bad key
But that's expected as motorola doesn't sign any official images :/
This did not unlock my SIM, but it does give me the boot.img I'll need to patch with magisk in order to have a recovery based root... not ideal, but it'll do.
Update:
The G7 Play has no "Recovery" partition. Recovery mode is just an argument to the boot.img and some signature checks disabled. So flash your patched image to the boot partition.
Update 2:
Don't flash retail images, specially the modem, to the Metro Phone!!! you may experience temporary LTE bans
I have a XT1952-T, got it both bootloader and SIM unlocked, and flashed the RETUS XT1952-4 firmware on it about a month ago. No more carrier bloatware.
xtermmin said:
I have a XT1952-T, got it both bootloader and SIM unlocked, and flashed the XT1952-3 firmware on it about a month ago. No more carrier bloatware.[/QUOTE
Have you noticed weak signal since doing this? I've also flashed a T variant but with the XT1952-4 firmware and the strongest I get is -109 dbm.
Click to expand...
Click to collapse
JohnSmith8786 said:
xtermmin said:
I have a XT1952-T, got it both bootloader and SIM unlocked, and flashed the XT1952-3 firmware on it about a month ago. No more carrier bloatware.[/QUOTE
Have you noticed weak signal since doing this? I've also flashed a T variant but with the XT1952-4 firmware and the strongest I get is -109 dbm.
Click to expand...
Click to collapse
XT1952-4 is meant for Sprint, so that could be the issue. Flash XT1952-3 instead.
EDIT: Sorry, I meant the RETUS version of XT1952-4, not the Sprint version.
Click to expand...
Click to collapse
XT1952-4 is meant for Sprint, so that could be the issue. Flash XT1952-3 instead.[/QUOTE]
Can you post a link to that file? The only XT1952-3 I seem to find are for vzw
JohnSmith8786 said:
XT1952-4 is meant for Sprint, so that could be the issue. Flash XT1952-3 instead.
Click to expand...
Click to collapse
Can you post a link to that file? The only XT1952-3 I seem to find are for vzw [/QUOTE]
Go to the firmware link in the OP: https://mirrors.lolinet.com/firmware/moto/channel/official/
Scroll down and click on RETUS (Retail US)
EDIT: Whoooops, I said XT1952-3 earlier, I meant the RETUS version of XT1952-4! Moto makes this so confusing... What I linked to above is the unlocked model's firmware.
[/QUOTE] EDIT: Whoooops, I said XT1952-3 earlier, I meant the RETUS version of XT1952-4! Moto makes this so confusing... What I linked to above is the unlocked model's firmware.[/QUOTE]
I flashed it anyway against my better judgement lol (over the lastest unlocked RETUS version) lost my (the wife's) IMEI when I flashed back to the RETUS not entirely sure why. Had a heck of a time trying to register the Sim card, flashing back to stock TMO firmware didn't work either. I even fastboot flashed by cmd line with no luck. Flashed the VZW firmware and I had signal.... So I flashed the lastest RETUS and the modem files from the VZW firmware and I'm fine (This is strange to me because it's a TMO revvlry not a VZW branded phone) The question I'm indirectly asking is why did I lose my IMEI? I stayed on PIE... Also curious to know if anyone has had this happen before and how they fixed if they did.
Moto G7 play Stock image required
I have a XT1952-2, purchased from local supplier. I need to know which stock image is form my G7 play.
Build number: channel-userdebug 9 PPY29.68-23 2de9intcfg.test-keys
fossyfosser said:
Success verbatim for the stock image on XT1952-6 (United states, Metro PCS carrier) purchased at a store a week ago.
CHANNEL_RETAIL_9.0_PPYS29.105-134-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Only hiccup was
fastboot flash boot boot.img
Sending 'boot_a' (32768 KB) OKAY [ 0.887s]
Writing 'boot_a' (bootloader) Image signed with key bad key
But that's expected as motorola doesn't sign any official images :/
This did not unlock my SIM, but it does give me the boot.img I'll need to patch with magisk in order to have a recovery based root... not ideal, but it'll do.
Update:
The G7 Play has no "Recovery" partition. Recovery mode is just an argument to the boot.img and some signature checks disabled. So flash your patched image to the boot partition.
Update 2:
Don't flash retail images, specially the modem, to the Metro Phone!!! you may experience temporary LTE bans
Click to expand...
Click to collapse
Can you elaborate on "temporary LTE bans"
JohnSmith8786 said:
Can you elaborate on "temporary LTE bans"
Click to expand...
Click to collapse
Did you find out what he meant by the LTE bans?
thetojo said:
Did you find out what he meant by the LTE bans?
Click to expand...
Click to collapse
No, never did...
Well twas worth a shot thanks
JohnSmith8786 said:
Can you elaborate on "temporary LTE bans"
Click to expand...
Click to collapse
What he really meant to say is loss of LTE. Different carriers use different radio bands for service, so if you flash the wrong modem you'll have signal problems.
Hello everyone,
I tried flashing stock, but get some problems.
Device:
XT1952-1
RETEU
I have downloaded this stock:
XT1952-1_CHANNEL_RETEU_9.0_PPYS29.105-134-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Spaceminer told me, that before TWRP etc. I have to look that A and B are not empty so I tried flashing stock to get it safe (am I right that flashing stock would both partitions flash?)
PC-System:
Linux debian
Problem:
$ fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modema' (65280 KB)...
OKAY [ 2.669s]
writing 'modema'...
(bootloader) Invalid partition name modema
FAILED (remote failure)
finished. total time: 2.670s
--------
$ fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsga' (11120 KB)...
OKAY [ 0.456s]
writing 'fsga'...
(bootloader) Invalid partition name fsga
FAILED (remote failure)
finished. total time: 0.457s
--------
There is always a "a" at the filenames.
modem -> modema
fsg -> fsga
How should I handle this?
Thanks for your help
@ggg777
Use the latest fastboot from the Android sdk or use the latest fastboot portable from xda. If you already are, then try specifying the slot with boot_a or boot_b.
Spaceminer said:
@ggg777
Use the latest fastboot from the Android sdk or use the latest fastboot portable from xda. If you already are, then try specifying the slot with boot_a or boot_b.
Click to expand...
Click to collapse
Thanks, I will try that
Hi. I tried flashing a couple of different versions of XT 1952-2 (such as RETAIL, RETBR) on my phone but everytime i try to run my phone the accelerator sensor seems to be inverted.
I've searched all over and most of the forums say that it happens probably because the proper version of the stock rom wasn't flashed.
The first time I got this phone it had loads of probably developer-esque apps such as battery tracer, bugs2go (if that's what it's called), etc.
Another interesting thing is that my bootloader is in engineering mode and i suspect that might be the reason my accelerator seems to be inverted.
I also tried to root my phone hoping i could modify some related files but everytime i flashed magisk, it doesn't root the phone.
Here's the bootloader if that explains something....
AP Fastboot Flash Mode (Not Secure)
BL:MBM-2.1-channel_retail-6bae60c-190618
Baseband: M632_17.61.01.99p CHANNEL_LATAMDSDS_CUST
Product/Variant: channel XT1952-2 32GB DVT1A
I've been super frustrated with this and any response would be more than appreciated. Thanks.
hassanmuj said:
Hi. I tried flashing a couple of different versions of XT 1952-2 (such as RETAIL, RETBR) on my phone but everytime i try to run my phone the accelerator sensor seems to be inverted.
I've searched all over and most of the forums say that it happens probably because the proper version of the stock rom wasn't flashed.
The first time I got this phone it had loads of probably developer-esque apps such as battery tracer, bugs2go (if that's what it's called), etc.
Another interesting thing is that my bootloader is in engineering mode and i suspect that might be the reason my accelerator seems to be inverted.
I also tried to root my phone hoping i could modify some related files but everytime i flashed magisk, it doesn't root the phone.
Here's the bootloader if that explains something....
AP Fastboot Flash Mode (Not Secure)
BL:MBM-2.1-channel_retail-6bae60c-190618
Baseband: M632_17.61.01.99p CHANNEL_LATAMDSDS_CUST
Product/Variant: channel XT1952-2 32GB DVT1A
I've been super frustrated with this and any response would be more than appreciated. Thanks.
Click to expand...
Click to collapse
When you say you magisk...have you tried to reboot to recovery mode from bootloader screen?..
My device...
Code:
Baseband Version: M632_26.100.01.120.01R CHANNEL_SUPER_CUST
Kernel Version: 4.9.112-perf+ [email protected] #1 32-bit
Java Virtual Machine: ART 2.1.0
Android Version: 9
Build Number: PPYS29.105-134-9 (cd8e0)
Build Fingerprint: motorola/channel_reteu/channel:9/PPYS29.105-134-9/cd8e0:user/release-keys
Build Description: channel_reteu-user 9 PPYS29.105-134-9 cd8e0 release-keys
Build Date: Mon Feb 10 12:39:21 CST 2020
Just patched mine
A useful trick when updating magisk version.... Patch the stock boot img in magisk manager, use the Flasher within ex kernel manager app to flash new boot img.... Reboot recovery... Saves all the fastboot stuff you do first time round
If anyone gets ahold of the Android 10 soak test let me know because I want it. I got approved for it, but I'm unable to download it. The last ota "160-4" will break your ability to grab it. Stay on 160. The official build releases in 30 days if everything goes well.
After installing LOS 17.1 I had no cell network (wifi worked).
I found a tip here that recommended to use
fastboot erase modemst1
fastboot erase modemst2
But that made things worse. I not only have no network, now the IMEI is gone, phone number not detected.
I tried now to flash modem from stock rom:
fastboot flash modem NON-HLOS.bin
but this didnt help either....
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.