Stock Android 8.0.0 Factory Firmware
Moto E5 Play (James) xt1921-5
Sprint/Virgin Mobile/Boost Mobile
WARNING: This stock Android 8.0.0 firmware package should not be used in an attempt to downgrade your device to an earlier firmware build. (While downgrading is possible, only the more advanced users should attempt it ) Use this firmware & guide only if your device has never been upgraded beyond Build No. OCP27.91-23. Attempting to downgrade your partition index (gpt.bin) or your bootloader partitions (bootloader.img) can result in a hard-bricked device -- and typically bricked beyond repair. By proceeding further, you are assuming sole responsibility for the integrity and functionality of your device, thus absolving me from any civil liability in the event your device becomes bricked, damaged, or otherwise inoperable.
SPECIFICATIONS:
Android Version: 8.0.0 Oreo
Build No. OCP27.91-23
Kernel Version: 3.18.71
Radio Version: M8920.11.54.11.41R
Security Patch Level: March 1, 2018
APPLICABILITY:
There are any number of reasons to use this restoration guide. If you are running a rooted device with system-based or systemless modifications to your Android OS, and you merely want to return to an unmodified stock configuration, this guide will accomplish that. If your device is soft bricked, stuck in a boot loop or is otherwise malfunctioning from a software standpoint, this guide will repair your phone. Or, perhaps you simply want to return to unmodified stock in order to install an OTA update. Again, this guide is for you.
RESTORATION/FLASHING INSTRUCTIONS:
This guide is written with the assumption that you have at least a rudimentary knowledge of AP Fastboot Mode and basic flashing commands. While this firmware can certainly be installed using RSD-Lite, mFastboot, etc., this guide aims at a basic fastboot installation. This procedure will erase all userdata stored on your device, enables dm-verity (device mapping), and enables default force encryption of the /userdata partition. Please make a backup of any data, files, media, etc. that you want to keep prior to proceeding. This process removes root binaries, BusyBox, root-dependent mods, and restores all OEM and carrier-specific bloatware. This guide also assumes that you have a recent version of the Minimal ADB & Fastboot utilities installed on your PC or laptop, as well as the proper USB device drivers.
1. Download the firmware package from the below link and extract the contents of the archive to your adb/fastboot directory on your PC;
2. Boot your device into AP Fastboot Mode by first powering down your device and then simultaneously holding the Power + Volume Down keys for around 8 seconds, until you see AP Fastboot Mode on your device display;
3. Connect your device to your PC using the OEM supplied or quality-equivalent micro USB to USB syncing cable;
4. Open a command window in the path of your adb/fastboot directory;
5. Enter this command:
fastboot devices
Press Enter/Return
If your device and PC are properly connected, an alpha-numeric string will appear in the command window synonomous to your device serial number;
6. After ensuring a proper connection, execute the following commands:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash dsp adspso.bin
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
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 erase DDR
fastboot erase cache
fastboot erase userdata
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot oem fb_mode_clear
7. Now reboot your device by entering:
fastboot reboot
Press Enter/Return
Upon reboot, your device should be fully restored to stock Android 8.0.0 firmware, Build No. OCP27.91-23, and your device will be fully capable of installing OTA update packages.
DOWNLOAD LINK:
https://drive.google.com/file/d/1v39JAH7gUjjN5-iR8qPln4WS9Hozq88s/view?usp=drivesdk
Over the next few days, I will be adding threads with firmware packages and restoration instructions for other variants of the Moto E5, including the Moto E5 Cruise & the Moto E5 Plus.
You're awesome, Because I somehow disappeared my radio again. lol. Between the rom and this you've singlehandedly rebuilt my phone
Starkiller2 said:
You're awesome, Because I somehow disappeared my radio again. lol. Between the rom and this you've singlehandedly rebuilt my phone
Click to expand...
Click to collapse
Glad it helped you. I'm in the process of updating this thread to reflect the most current firmware build of OCP27.91-23-3 with the June 1, 2018 security patch level.
MotoJunkie01 said:
Glad it helped you. I'm in the process of updating this thread to reflect the most current firmware build of OCP27.91-23-3 with the June 1, 2018 security patch level.
Click to expand...
Click to collapse
somehow I still messed up. now I'm stuck in airplane mode, with mobile radio stuck to off. I've tried everything, rerooting, different apps, programming menu. I give up. lol. even the stuff I did after I soft bricked it isn't working.
@Starkiller2, I will try to help. Who is your carrier? Your mobile service provider in other words.
MotoJunkie01 said:
@Starkiller2, I will try to help. Who is your carrier? Your mobile service provider in other words.
Click to expand...
Click to collapse
Boost mobile. Thanks for the help
Starkiller2 said:
Boost mobile. Thanks for the help
Click to expand...
Click to collapse
Ok. Try this. From the firmware package above, extract two files to your adb/fastboot directory -- NON-HLOS.bin and fsg.mbn. Boot your device into fastboot mode, connect to your PC, and open a command window in your adb/fastboot path. Execute these commands in order:
fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot oem config fsg-id boost
fastboot oem config carrier boost
fastboot erase DDR
fastboot erase cache
fastboot oem fb_mode_clear
Reboot by entering:
fastboot reboot
This process configures your radio firmware partitions for Boost Mobile, reinstalls your radio firmware, and resets all network configurations to the factory default settings. This will typically fix problems with the cell radio, signal strength issues, domestic roaming, no cell signal, etc. Let me know. We can try some different things if need be. Whatever your issue is caused from, just remember it is fixable. Frustrating for sure, but fixable.
MotoJunkie01 said:
Ok. Try this. From the firmware package above, extract two files to your adb/fastboot directory -- NON-HLOS.bin and fsg.mbn. Boot your device into fastboot mode, connect to your PC, and open a command window in your adb/fastboot path. Execute these commands in order:
fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot oem config fsg-id boost
fastboot oem config carrier boost
fastboot erase DDR
fastboot erase cache
fastboot oem fb_mode_clear
Reboot by entering:
fastboot reboot
This process configures your radio firmware partitions for Boost Mobile, reinstalls your radio firmware, and resets all network configurations to the factory default settings. This will typically fix problems with the cell radio, signal strength issues, domestic roaming, no cell signal, etc. Let me know. We can try some different things if need be. Whatever your issue is caused from, just remember it is fixable. Frustrating for sure, but fixable.
Click to expand...
Click to collapse
No go. Whatever it is its causing the mobile radio power switch in the programming menu to keep reverting to the off position. if I try turning it on and running a ping it switches right back off.
Starkiller2 said:
No go. Whatever it is its causing the mobile radio power switch in the programming menu to keep reverting to the off position. if I try turning it on and running a ping it switches right back off.
Click to expand...
Click to collapse
Let me research this a bit. Are you running the latest OTA update? Build OCP27.91-23-3?
yeah I flashed the stock firmware this morning and took it over wifi.
Starkiller2 said:
yeah I flashed the stock firmware this morning and took it over wifi.
Click to expand...
Click to collapse
Ok. I think I know the issue. Repeat the entire firmware restoration process again, just like you done previously, except this time skip gpt.mbn, adspso.bin and bootloader.img. Upon reboot your cell radio should work.
Still nothing. Except now it keeps trying to make me take the update again.
---------- Post added at 09:01 AM ---------- Previous post was at 08:59 AM ----------
Lol. I have a third party warranty thank God. It covers it still. Maybe it's a write off.
Still a negative. now whenever I take the update and try the firmware without the pieces you instructed, it just tries to make me update again. But recovery is working again
Starkiller2 said:
Still nothing. Except now it keeps trying to make me take the update again.
---------- Post added at 09:01 AM ---------- Previous post was at 08:59 AM ----------
Lol. I have a third party warranty thank God. It covers it still. Maybe it's a write off.
Still a negative. now whenever I take the update and try the firmware without the pieces you instructed, it just tries to make me update again. But recovery is working again
Click to expand...
Click to collapse
When it prompted you to accept the OTA, did you accept and install it? Try that and see what happens. Yours is beginning to sound like a hardware issue.
yeah I accepted it every time. lol. Im thinking I may need to just replace it. I had issues with data when I first rooted it but that was my fault and I had it working again. Thank you for all your help.
@MotoJunkie01 Do you happen to have your hands on the Retus or Unlocked firmware for this model? (Moto E5, Play)
maxmotos said:
@MotoJunkie01 Do you happen to have your hands on the Retus or Unlocked firmware for this model? (Moto E5, Play)
Click to expand...
Click to collapse
Give me the exact model number and I'll check.
The latest build is up on my Moto E5 Play Stock ROM thread -- OCPS27.91-23-3
https://forum.xda-developers.com/mo...tock-android-8-0-0-rom-moto-e5-t3806530/page2
Works with XT1944-3?
Was wondering if any of the above stock roms would work with xt1944-3 variant of Moto E5
Can you help me please? Thanks in advance
amn92 said:
Was wondering if any of the above stock roms would work with xt1944-3 variant of Moto E5
Can you help me please? Thanks in advance
Click to expand...
Click to collapse
Who is your mobile provider? I have some firmware for the xt1944-3 but I believe it's the retail. Just added xt1944-3 firmware in my thread. https://forum.xda-developers.com/moto-e5/how-to/firmware-moto-e5-xt1944-4-dual-sim-t3820901
Related
Hi,
after an apparently failed attempt to install the 5.0 OTA update my XT1032 now will boot to a droid lying on its back.
I went to the recovery from there (by pressing VolUp+Power) and did the "factory reset/wipe data" and rebooted.
Same result.
I did "wipe chache". Same result: Droid lying on its back, saying "Kein Befehl" (I guess that means "no command")
I can get into recovery mode (CWM was installed before all this*) so I could try to flash stuff from outside.
But what should I try to flash? I tried flashing a (supposedly) stock system but as soon as I start with "fastboot flash boot boot.img" the phone starts booting again. So I am not really sure what to do now.
Something is seriously wrong with this phone and I would like to restore it to stock settings. I bought it on amazon.DE - so if any one of you guys knows where I could find a truly original stock image for this phone and what to do with it, please let me know.
PS: Right now I can't even get into recovery anymore. The thing just keeps booting and booting. Can't even turn it off.
* meaning: before I flashed the supposed stock recovery that apparently, in combination with the OTA update, got me into this mess
I now followed this guide:
http://forum.xda-developers.com/showthread.php?p=47820707#post47820707
I used option 3b with a 4.4.4 rom ( RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF )
I excuted all these commands. However, upon flashing the boot.img the phone immediately boots (and gets stuck).
So I re-entered fastboot again to finish the job. Everything else went fine.
But the problem persists: When booting, the phone now displays the "Warning: Bootloader unlocked" message for a long time, with a kind of water ripple effect from bottom to top, repeating.
When I switch it off, it switches back on automatically, trying to boot and getting stuck at this screen. Sometimes I get to the droid lying on its back with a red !-Triangle on top. Poor little bugger. Soft bricked.
What can I do to fix this?
I can still enter fastboot.
I assume that yet again I grabbed the wrong ROM.
Is this supposed to be dead? http://sbf.droid-developers.org/phone.php?device=14
I think you might be on lollipop bootloader as you are having a screen flickering issue & downgrading the boatloader might be dangerous.
I'm don't know whether it will solve your problem but try flashing a lollipop firmware.
I'm not allowed to post links. Google for XT 1032 lollipop firmware. I saw one in groupandroid website.
Download the firmware from the site & execute the given commands.
legolas06 said:
I think you might be on lollipop bootloader as you are having a screen flickering issue & downgrading the boatloader might be dangerous.
I'm don't know whether it will solve your problem but try flashing a lollipop firmware.
I'm not allowed to post links. Google for XT 1032 lollipop firmware. I saw one in groupandroid website.
Download the firmware from the site & execute the given commands.
Click to expand...
Click to collapse
Thank you. I got that file.
"adb devices" won't find my phone, though.
"Fastboot devices" does. So I can't use "adb push ..." to move the ROM to the phone.
Also, whatever option I chose from the Fastboot Flash Mode, the phone starts to boot. So I can not "enter" Recovery.
Should I just use "fastboot update rom.zip"? I don't wan't to miss my last chance to revive this phone.
ADB commands will not work in with the phone fastboot mode.
Since fastboot commands do work, you can manually flash each partition from the stock ROM. Entering recovery isn't required to do this.
fertchen said:
Thank you. I got that file.
"adb devices" won't find my phone, though.
"Fastboot devices" does. So I can't use "adb push ..." to move the ROM to the phone.
Also, whatever option I chose from the Fastboot Flash Mode, the phone starts to boot. So I can not "enter" Recovery.
Should I just use "fastboot update rom.zip"? I don't wan't to miss my last chance to revive this phone.
Click to expand...
Click to collapse
I had similar problems & this method worked for me everytime. Sorry I'm a new user & I cannot post the links.
You can search the forum & find the links.
I found a thread in "xda -> moto g general->[FIRMWARE][XT1032-XT1033] Firmware Lollipop Retail Brasil & Asia 5.0.2" by cristiand391. Download the firmware for your device. It will be in BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml.zip. Extract the contents to the fastboot.exe folder where you use regularly. Run the commands in fastbootmode. Please be careful with the commands.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Reboot.
audit13 said:
ADB commands will not work in with the phone fastboot mode.
Since fastboot commands do work, you can manually flash each partition from the stock ROM. Entering recovery isn't required to do this.
Click to expand...
Click to collapse
The problem here is that the phone will boot as soon as I flash the boot.img and the whole thing fails.
Do you see a way out of this situation?
Any way to do this with a .zip ROM?
Have you tried flashing different firmware such as the GPE for your phone?
Does boot.img flash properly? If it does, you could try installing TWRP, boot into TWRP, mount the data partition, and use your computer to copy a custom ROM to the phone fpr flashing.
@Fretchen
That might be because you are on lollipop bootloader & you are trying to flash kitkat bootloader?But I may be wrong. Previously you told that you tried restoring to kitkat & that boot.img is kitkat bootloader. Try with this lollipop firmware.
audit13 said:
Have you tried flashing different firmware such as the GPE for your phone?
Does boot.img flash properly? If it does, you could try installing TWRP, boot into TWRP, mount the data partition, and use your computer to copy a custom ROM to the phone fpr flashing.
Click to expand...
Click to collapse
I now did exactly what legolas06 wrote, using "MoeMoe_BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml"
There were "hab check fails" for recovery and boot but at least the device did not reboot upon flashing the boot.img.
I rebooted it and it is going further than ever before, all the Motorola animations were played but in the end the phone got stuck at the circular blue pool (water) with the bit Motorola 'M' plus the concentric water ripple effect.
I switched it off and on again and then it played through the animations, then updated the apps (total number: 9) and then started the system. Apparently it is working.
Thank you very much, I really appreciate your support.
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
fertchen said:
I now did exactly what legolas06 wrote, using "MoeMoe_BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml"
There were "hab check fails" for recovery and boot but at least the device did not reboot upon flashing the boot.img.
I rebooted it and it is going further than ever before, all the Motorola animations were played but in the end the phone got stuck at the circular blue pool (water) with the bit Motorola 'M' plus the concentric water ripple effect.
I switched it off and on again and then it played through the animations, then updated the apps (total number: 9) and then started the system. Apparently it is working.
Thank you very much, I really appreciate your support.
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
Click to expand...
Click to collapse
Happy that I could help.
You flashed the stock firmware so everything should work again. OTA updates if available would work.
fertchen said:
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
Click to expand...
Click to collapse
I don't know if you can apply OTA updates. Before the OTA update will work, you may need to update all Motorol apps via Play store.
You could wait until a fulkl stock lollipop pop is released for your phone and flash it using fastboot.
You can try different ROMs but stick to the ROMs made for your model. I have an xt1032 and I have installed US Retail, stock Telus, and GPE.
worked for me too, thank you soo much. give this solution a try
legolas06 said:
I had similar problems & this method worked for me everytime. Sorry I'm a new user & I cannot post the links.
You can search the forum & find the links.
I found a thread in "xda -> moto g general->[FIRMWARE][XT1032-XT1033] Firmware Lollipop Retail Brasil & Asia 5.0.2" by cristiand391. Download the firmware for your device. It will be in BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml.zip. Extract the contents to the fastboot.exe folder where you use regularly. Run the commands in fastbootmode. Please be careful with the commands.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Reboot.
Click to expand...
Click to collapse
these steps look soo similar that the ones you can find in other blogs/discussions, but for me, in my case the main difference was the firmware, I tried with a loot of them, but the one that is mentioned in this post, installed smoothly, and with no issues, thank you so much, to post your experience and this solution.
My Best Regards,
Esteban
Hi all.
If you are here, then you have likely experienced issues with custom ROMs not detecting SIM, or you are still experiencing this issue.
I have a XT1562 UK Single-SIM model and have had this problem with EVERY ROM I have tried and it was getting so frustrating.
Over the last few weeks, I have flashed custom ROMs based on CM13 and all have presented the SIM not detected issue. A simple fix was to pop-out the SIM module and reinsert - more often than never, the SIM was detected. Then I would restart (as is often the case with a custom setup) and alas, the SIM was not detectable.
After trying various suggestions from developers, nothing was working until I happened to flash a dualSIM firmware and I haven't looked back. I can now flash EVERY CM13-based ROM with successful SIM detection BUT it takes a few extra steps to get to that stage.
Here are the things you need:
This firmware
This fix
A custom ROM of your choice (Highly recommend crDroid or Temasek)
GAPPS of your choice - I would recommend this
TWRP
Okay - the solution (confirmed working and reliable):
1. Unpack the Firmware into it's own folder
2. Copy across the files to Fastboot folder
3. Restart phone into bootloader (power off first then hold power and volume down)
4. In the Fastboot folder hold shift and right click.
5. Select "open command window here"
6. Connect phone via USB to computer and in command window enter the following commands 1 by 1 making sure "[okay]" is displayed each time:
if nothing happens on screen, then simply use your volume keys on the phone to restart the bootloader
fastboot oem fb_mode_set
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
7. Once completed restart phone and setup as normal.
8. When setup is complete, restart phone into bootloader.
9. Flash TWRP
10. Restart phone into recovery
11. in TWRP, factory reset then flash ROM and GAPPS and DualSIMFix
12. Restart phone and setup. If SIM shows not detected, press "skip" and it should detect after WiFi setup.
Voila! You can now confidently flash ANY CM13-based custom ROM with the added assurance of SIM detection. IF, however, you flash a ROM and SIM is NOT detected, then simply reflash the DualSIMFix.
If this solution works for you, please give credit where it's due - thank me using the thumbs-up icon below AND vote in the poll at the head of this thread
So, you want to say, that i need to flash stock DS ROM
and after that i'll can flash any custom CM13 based ROM and SIM will be detected?
perfectsense72 said:
So, you want to say, that i need to flash stock DS ROM
and after that i'll can flash any custom CM13 based ROM and SIM will be detected?
Click to expand...
Click to collapse
It has worked for me and I have tried everything that has been recommended. Just by determined trial-and-error I have found my solution.
Just to reiterate
and my intention is to generate enough interest to further assist developers of the CM13 custom ROMs.
Click to expand...
Click to collapse
Can you write a sequence of actions? What nuances?
perfectsense72 said:
Can you write a sequence of actions? What nuances?
Click to expand...
Click to collapse
I fastboot flashed XT1562_LUX_RETASIA_DS_6.0_MPD24.65-18.1 (here ); flashed ROM; flashed GAPPS and then flashed DualSIMFix (from here)
I've tested reboots and SIM is detected each time.
I am assuming you know how to flash a stock image - if not let me know.
I am assuming you know how to flash a stock image - if not let me know
Click to expand...
Click to collapse
From PC by fastboot in stock recovery mode, right?
Did you perform any wipe between flashing stocj ROM and flashing CM13 based ROM?
perfectsense72 said:
From PC by fastboot in stock recovery mode, right?
Did you perform any wipe between flashing stocj ROM and flashing CM13 based ROM?
Click to expand...
Click to collapse
Follow this:
1. Unpack the Firmware into it's own folder
2. Copy across the files to Fastboot folder
3. Restart phone into bootloader (power off first then hold power and volume down)
4. In the Fastboot folder hold shift and right click.
5. Select "open command window here"
6. Connect phone via USB to computer and in command window enter the following commands 1 by 1 making sure "[okay]" is displayed each time:
if nothing happens on screen, then simply use your volume keys on the phone to restart the bootloader
fastboot oem fb_mode_set
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
7. Once completed restart phone and setup as normal.
8. When setup is complete, restart phone into bootloader.
9. Flash TWRP
10. Restart phone into recovery
11. in TWRP, factory reset then flash ROM and GAPPS and DualSIMFix
12. Restart phone and setup. If SIM shows not detected, press "skip" and it should detect after WiFi setup.
13. Enjoy - but please let me know if not quite right.
@perfectsense72 - once you are able to confirm fully working, then I'll amend the OP to reflect necessary details for successful detection, etc. Thanks for trying this.
Thank you, i'll try tomorrow.
I can't confirm your problems with single sim modem.
I have german single sim and had problems after flashing french dual sim stock image and then flash cm13 roms.
Sometimes the boot was fine with detected sim and sometimes without detected sim and with random reboots of the device.
After flashing back a single sim stock and completly boot the stock then flash again crdroid no problems appeared again. All fine with detected sim on every boot.
For now I'm using Pac-ROM (LP) and have no problem, I'll try CrDroid soon and I'll let you know.
Jeso said:
Sometimes the boot was fine with detected sim and sometimes without detected sim and with random reboots of the device.
Click to expand...
Click to collapse
This is what I'm aiming to avoid for those with issues such as this. Every firmware flash produced an error on flashing bootloader. The only one to not present me with the error is the 18.1 DS retasia.
This has, I believe, been the key to my issues as well as other users. I can flash any official firmware and use it perfectly well, it's just the custom MM ROMs that are problematic.
moozer said:
fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
Does it lock the bootloader?
(Sorry for noob question)
axxx007xxxz said:
Does it lock the bootloader?
(Sorry for noob question)
Click to expand...
Click to collapse
No - this just re-introduces the stock bootloader for the firmware
So, it's working. Flash Unoficial CM13 after stock DS asian and no problem, both simcards a detected.
Thanks, moozer.
perfectsense72 said:
So, it's working. Flash Unoficial CM13 after stock DS asian and no problem, both simcards a detected.
Thanks, moozer.
Click to expand...
Click to collapse
You're welcome. Checked rebooting the phone? SIM remains?
You can now flash custom ROMs to your heart's content. No need to fart around with firmware flashes. All that you need to check is SIM detection on setup and if necessary flash the SIMfix.
^^
Yes, SIM remains after reboot, everything is OK
Thanks a lot! Worked perfectly for me aswell. Currently running ResurrectionRemix and I've had no problems with the sim card since.
After tried to root my device without the assist of PC (only using apk), my device only starts on AP Fastboot Flash Mode (Secure).
I downloaded the brazilian firmware, tried to flash it but I can't.
Was getting this ERROR: "(bootloader) Preflash validation failed".
My bootloader is locked, so I tried to unlock it following the Motorola's guide. Got my device ID via fastboot, copy and paste on their site and requested the unlock key.
Then again, when I use "fastboot oem unlock CODE"
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.016s
The problem is that I can't pass trough flash mode screen.
I've been reading some threads over here, and one guy which had his bootloader locked on XT1563 tried to flash the Canadian firmware and didn't get any error, then he was able to fully unlock his bootloader and after this he was able to flash the Brazilian firmware.
I didn't try to flash the Canadian firmware yet. How risky is this? There is another way to unlock the bootloader?
If you flash the right firmware for a locked phone (model and version), it won't give the prevalidation error. Then it can boot again and you can turn on the OEM unlock, and unlock the bootloader.
Try to use the right firmware for your phone.
TImMaia said:
After tried to root my device without the assist of PC (only using apk), my device only starts on AP Fastboot Flash Mode (Secure).
I downloaded the brazilian firmware, tried to flash it but I can't.
Was getting this ERROR: "(bootloader) Preflash validation failed".
Click to expand...
Click to collapse
I don't believe it is possible to root without first unlocking your bootloader (which will factory reset your device). What apk were you attempting to install?
MrTooPhone said:
I don't believe it is possible to root without first unlocking your bootloader (which will factory reset your device). What apk were you attempting to install?
Click to expand...
Click to collapse
I'm a real noob at this issue. I tried to root with Kingroot. I took the device to the Motorola Tech Support in my city yesterday afternoon and it is ready to pick up.
Thank you guys for helping me :good::good::good:
TImMaia said:
I'm a real noob at this issue. I tried to root with Kingroot. I took the device to the Motorola Tech Support in my city yesterday afternoon and it is ready to pick up.
Thank you guys for helping me :good::good::good:
Click to expand...
Click to collapse
If you really want to root, you need to follow these instructions. Although you can use the latest version of TWRP, do not use any other version of Supersu except v2.62-3. Any other methods will most likely soft brick your phone.
Boys, is not difficult, not just fiddling around to fix it.
Motorola install drivers
Install ADB and fastboot
Looking for your stock rom here: " github dot com dash motoxplay dash stock dash releases " for example.
Saddled with fastboot Tooda the rom (eye, if downloaded from out there commands, you may be wanting to them upload any image rom, this drove me crazy to me all one day until I realized I was missing two sparsechunk).
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 erase userdata
fastboot reboot
On the subject battery, the XT1563 charge the batt when it is in this mode, we just have to leave it connected to the charger and is loading very slowly.
On the bootloader issue, I have LOCK, and may do so without problems because they look the same version of rom that he had.
About not having DEPURACION USB, I did not have it on, and yet I could do it.
My stay in Fastboot mode I when installing the app Kingroot, and turned off the phone and start no more.
In this way it is solved, 100% sure I did not do myself. Do not try other methods like TWRP or things like that because with locked bootloader will hit the wall every time.
Anyone who needs a hand, ask or send mail.
Sorry if he had been resolved, but it was a big achievement for me, so I leave the info. I cost a lot to buy the cell phone and had ****ed the other day.
Regards!
(Sorry, its googletranslated, im from argentina)
Yeah, what ever @jonatandirocca1 said is right
i also once faced the problem of missing sparse file but after flashing every file you can make your Phone revoke
if you want to install STOCK FIRMWARE , you dont need to unlock bootloader, you just need your phone detected in ADB
I know I'm not the only one who has been having trouble finding the stock firmware for the Moto e5 play xt1921-3 MetroPCS/TMobile variant, code named James, that wasn't posted by @MotoJunkie01 and therefore blocked and undownloadable.
So thanks to @HPLazerJetPrinter1012 who was kind enough to find it on XDA in another section and thanks to @timjames474 for posting it in that thread....
VERY IMPORTANT IMHO THAT YOU BACKUP YOUR IMEI INFORMATION AS SOON AS YOU ROOT YOUR DEVICE, PREFERABLY BEFORE FLASHING A CUSTOM ROM. GOING FROM CUSTOM OREO BACK TO STOCK CAN EASILY ERASE ALL YOUR PHONES IMEI INFO MAKING VOLTE AND 4G AND PHONE INOPERABLE. HAPPENED TO ME AND IT WAS A HUGE P.I.T.A. TO FIX.
Download Links
JAMES_T_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip / MIRROR
This is the newest (at least at the time of post) update, dated Oct 1, 2018
Instructions to revert back to stock firmware and make it so that you can get OTA updates again:
To install, extract the zip file in your adb/fastboot directory and then make sure you are properly connected to your computer by running the command
Code:
fastboot devices
Then, once you confirm you are properly connected, just run the following fastboot commands one line at a time, making sure spelling is correct (or copying and pasting to ensure proper spelling):
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash dsp adspso.bin
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
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 erase DDR
fastboot erase cache
fastboot erase userdata
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot oem fb_mode_clear
After this is complete, simply reboot your device, and as long as you did everything right, you should be back on stock firmware with the ability to receive OTA updates.
Flashing a stock recovery,unencrypting your phone, or rooting will make OTA fail, so i recommend waiting to do those things until you are fully updated (unless you don't care about the latest build).
Just to cover my ass, i had nothing to do with the making of these files and I am simply posting well known information for newer users to help them get back to stock.
Therefore, i claim no responsibility for any damage or bricking of your device.
Have a good day friends and if I helped you out, a 'thanks' would be appreciated :good:
Thanks for posting this. I was actually going to upload it myself. You save me from having to do the work
weakNPCdotCom said:
Thanks for posting this. I was actually going to upload it myself. You save me from having to do the work
Click to expand...
Click to collapse
Not a problem.... I actually found most of the firmwares that MotoJunkie01 had posted, I might repost his firmware post (copy and paste) and replace the links after i upload them to my own Gdrive, when I have time....
AesopRock127 said:
Not a problem.... I actually found most of the firmwares that MotoJunkie01 had posted, I might repost his firmware post (copy and paste) and replace the links after i upload them to my own Gdrive, when I have time....
Click to expand...
Click to collapse
sweet. sounds great man. thank you
NM connection working now
https://mirrors.lolinet.com/firmware/moto/ look here for firmware and make sure its correct one and up to date before flashing it.
AesopRock127 said:
I know I'm not the only one who has been having trouble finding the stock firmware for the Moto e5 play xt1921-3 MetroPCS/TMobile variant, code named James, that wasn't posted by @MotoJunkie01 and therefore blocked and undownloadable.
So thanks to @HPLazerJetPrinter1012 who was kind enough to find it on XDA in another section and thanks to @timjames474 for posting it in that thread....
VERY IMPORTANT IMHO THAT YOU BACKUP YOUR IMEI INFORMATION AS SOON AS YOU ROOT YOUR DEVICE, PREFERABLY BEFORE FLASHING A CUSTOM ROM. GOING FROM CUSTOM OREO BACK TO STOCK CAN EASILY ERASE ALL YOUR PHONES IMEI INFO MAKING VOLTE AND 4G AND PHONE INOPERABLE. HAPPENED TO ME AND IT WAS A HUGE P.I.T.A. TO FIX.
Download Links
JAMES_T_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip / MIRROR
This is the newest (at least at the time of post) update, dated Oct 1, 2018
Instructions to revert back to stock firmware and make it so that you can get OTA updates again:
To install, extract the zip file in your adb/fastboot directory and then make sure you are properly connected to your computer by running the command
Then, once you confirm you are properly connected, just run the following fastboot commands one line at a time, making sure spelling is correct (or copying and pasting to ensure proper spelling):
After this is complete, simply reboot your device, and as long as you did everything right, you should be back on stock firmware with the ability to receive OTA updates.
Flashing a stock recovery,unencrypting your phone, or rooting will make OTA fail, so i recommend waiting to do those things until you are fully updated (unless you don't care about the latest build).
Just to cover my ass, i had nothing to do with the making of these files and I am simply posting well known information for newer users to help them get back to stock.
Therefore, i claim no responsibility for any damage or bricking of your device.
Have a good day friends and if I helped you out, a 'thanks' would be appreciated :good:
Click to expand...
Click to collapse
How did you get your phone to work meaning when I call some one they can't hear me but I can hear them .I re-flashed so many ROMs already that I'm staying on GSI Rom 8.1.0 Hanna metro PC's also I did flash stock Rom and still the see problem maybe it's time for replacement. It's been 3 days searching and asking for help. Maybe device to new idk ..
skullkid383 said:
https://mirrors.lolinet.com/firmware/moto/ look here for firmware and make sure its correct one and up to date before flashing it.
Click to expand...
Click to collapse
dude this link is worth money. amazing. thank you so much.
weakNPCdotCom said:
dude this link is worth money. amazing. thank you so much.
Click to expand...
Click to collapse
Yeah I used it on my Perry before I got hannah so it was first place looked when I needed Hannah fw
Googleme35 said:
How did you get your phone to work meaning when I call some one they can't hear me but I can hear them .I re-flashed so many ROMs already that I'm staying on GSI Rom 8.1.0 Hanna metro PC's also I did flash stock Rom and still the see problem maybe it's time for replacement. It's been 3 days searching and asking for help. Maybe device to new idk ..
Click to expand...
Click to collapse
I got mine to work because I have a James device.... You mention Hannah device so guessing you flashed the wrong firmware and that's the issue. I have the James xt1921-3
AesopRock127 said:
I got mine to work because I have a James device.... You mention Hannah device so guessing you flashed the wrong firmware and that's the issue. I have the James xt1921-3
Click to expand...
Click to collapse
Ok Thanks
I'm glad i could be of assistance,i was actually hunting down root methods for my GFs samsung and saw a video that linked to the user who uploaded it to AFH, rootjunkie was the channel if i recall,so i can't take all of that sweet credit. Yall have fun,but not too much fun
AesopRock127 said:
I know I'm not the only one who has been having trouble finding the stock firmware for the Moto e5 play xt1921-3 MetroPCS/TMobile variant, code named James, that wasn't posted by @MotoJunkie01 and therefore blocked and undownloadable.
So thanks to @HPLazerJetPrinter1012 who was kind enough to find it on XDA in another section and thanks to @timjames474 for posting it in that thread....
VERY IMPORTANT IMHO THAT YOU BACKUP YOUR IMEI INFORMATION AS SOON AS YOU ROOT YOUR DEVICE, PREFERABLY BEFORE FLASHING A CUSTOM ROM. GOING FROM CUSTOM OREO BACK TO STOCK CAN EASILY ERASE ALL YOUR PHONES IMEI INFO MAKING VOLTE AND 4G AND PHONE INOPERABLE. HAPPENED TO ME AND IT WAS A HUGE P.I.T.A. TO FIX.
Download Links
JAMES_T_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip / MIRROR
This is the newest (at least at the time of post) update, dated Oct 1, 2018
Instructions to revert back to stock firmware and make it so that you can get OTA updates again:
To install, extract the zip file in your adb/fastboot directory and then make sure you are properly connected to your computer by running the command
Code:
fastboot devices
Then, once you confirm you are properly connected, just run the following fastboot commands one line at a time, making sure spelling is correct (or copying and pasting to ensure proper spelling):
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash dsp adspso.bin
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
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 erase DDR
fastboot erase cache
fastboot erase userdata
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot oem fb_mode_clear
After this is complete, simply reboot your device, and as long as you did everything right, you should be back on stock firmware with the ability to receive OTA updates.
Flashing a stock recovery,unencrypting your phone, or rooting will make OTA fail, so i recommend waiting to do those things until you are fully updated (unless you don't care about the latest build).
Just to cover my ass, i had nothing to do with the making of these files and I am simply posting well known information for newer users to help them get back to stock.
Therefore, i claim no responsibility for any damage or bricking of your device.
Have a good day friends and if I helped you out, a 'thanks' would be appreciated :good:
Click to expand...
Click to collapse
PLEASE tell me how you fixed the IMEI/SIM not recognized issue. I can't figure this out at all. Thanks!
OMG!!!! This was a god send. Thank you guys for putting this together for us. I thought all hope was lost. My phone is back and running. YaY!!!!!!
weakNPCdotCom said:
dude this link is worth money. amazing. thank you so much.
Click to expand...
Click to collapse
I keep getting unsecured network... Is this an issue from my end?
How do you backup IMEI in TWRP?
EFS?
Mine won't mount data for backup and cache in red
Or should I do it another way?
I have XT1924-2 AND I TOO HAVE IMEI=0 ANY FIXES?
Thank you!
This was very helpful, thanks!
TheLastAlphaUK said:
I have XT1924-2 AND I TOO HAVE IMEI=0 ANY FIXES?
Click to expand...
Click to collapse
Flash most up-to-date software
skullkid383 said:
Flash most up-to-date software
Click to expand...
Click to collapse
That's a weird Necro-Response. Also updating doesn't fix IMEI, (even though this was over a year ago, they would need an IMEI flasher and the box/numbers found somewhere else)
Hey, I just installed June security patch on my Moto G6 and I gotta say this build is super smooth.
I’m getting more than 5-6hrs of SOT and yes DIGITAL WELLBEING IS A SYSTEM APP NOW.
I downloaded the latest firmware from here : https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/
And flashed it via RSD Lite.
Don’t forget to hit thanks
aaryan1596 said:
Hey, I just installed June security patch on my Moto G6 and I gotta say this build is super smooth.
I’m getting more than 5-6hrs of SOT and yes DIGITAL WELLBEING IS A SYSTEM APP NOW.
I downloaded the latest firmware from here : https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/
And flashed it via RSD Lite.
Don’t forget to hit thanks
Click to expand...
Click to collapse
Can I install this patch with Android 9 OTA with Root?
bradz28 said:
Can I install this patch with Android 9 OTA with Root?
Click to expand...
Click to collapse
No, unfortunately not. This is a full wipe/fresh install only. The same rooting method works, but it will have to be a fresh install.
xfrobex said:
No, unfortunately not. This is a full wipe/fresh install only. The same rooting method works, but it will have to be a fresh install.
Click to expand...
Click to collapse
Ok, thanks
Hello, I upgraded my phone through CMD commands in fastboot folder, but now I can't hear nor be heard in calls. I tried already intalling the NON-HLOS.bin from Stock ROM RETAIL OPSS27.104-92-4 and tried with the NON-HLOS.bin from the Sotck ROM from my region OPENMX OPSS27.82-87-8 too, but it didn't work.
Tried turning the phone on Secure Mode to see if it was a problem related with an app but it wasn't the case, also tried couple of times doing factory reset, but it gave the same result.
I was on the RETAIL PPSS29.55-34-1 with NON-HLOS.bin from OPENMX OPSS27.82-87-8 and the calls were fine. Could someone help me, please?
I did all of above with locked bootloader.
Edit:
Now I unlocked bootloader to downgrading to RETAIL PPSS29.55-34-1 with NON-HLOS.bin from OPENMX OPSS27.82-87-8, and it didn't work so I relock bootloader.
mariconojoda said:
Hello, I upgraded my phone through CMD commands in a fastboot folder, but now I can't hear and can't be heard in calls. I tried already intalling the NON-HLOS.bin from Stock ROM RETAIL OPSS27.104-92-4 and tried with the NON-HLOS.bin from the Sotck ROM from my region OPENMX OPSS27.82-87-8, but it didn't work.
Also tried turning the phone on Secure Mode to see if it was a problem related with an app but it wasn't the case, also tried couple of times doing factory reset, but it gave the same result.
I was on the RETAIL PPSS29.55-34-1 and the calls were fine. Could someone help me, please?
All of above with locked bootloader.
Edit:
Now I unlocked bootloader to downgrading, I donwgrade to RETAIL PPSS29.55-34-1 with NON-HLOS.bin from OPENMX OPSS27.82-87-8, it didn't work so I relock bootloader.
Click to expand...
Click to collapse
As you unlocked the bootloader your warranty is gone, plus I didn’t try with CMD commands, I used RSD Lite, so maybe try a fresh install again if problem persists.
aaryan1596 said:
As you unlocked the bootloader your warranty is gone, plus I didn’t try with CMD commands, I used RSD Lite, so maybe try a fresh install again if problem persists.
Click to expand...
Click to collapse
It don't recognize the device
Nevermind I just needed to connect the device in another port, also now the calls work thank you @aaryan1596
How do I install this without RSDLite? The program doesn't work for me at all (v5.7 on Win10), and I do not fully understand how to use fastboot/batch files to install the unpacked .zip file. Thank you for your help.
Edit: I was able to easily install this using Minimal ADB and Fastboot. Simply extract the contents of your .xml.zip file to your Minimal ADB and Fastboot installation folder. Boot your phone into fastboot mode (volume+power down) and copy and paste these commands (you can copy and paste the entire block and they will run sequentially):
Code:
fastboot erase userdata
fastboot erase cache
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase DDR
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash oem oem.img
fastboot flash logo logo.bin
fastboot flash dsp adspso.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
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 vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot erase cache
fastboot reboot
Using this method I was able to easily install to latest version onto my XT1925-6, which shipped with Oreo.
Is there any different between ROM with february security patch and this one (june security patch)?
Has anyone in the UK been able to download this update via system updates yet?
um.z said:
Has anyone in the UK been able to download this update via system updates yet?
Click to expand...
Click to collapse
Just downloading via system updates, channel: retgb.
Well, I received the June 1, PPS29.55-37-4 OTA (retgb channel) at around 9:40pm (Mon 5th Aug, UK time). It took 12 minutes to download the 818.6Mb package over a 4G connection, and a further 26 minutes to install it.
Everything went without a hitch, and all seemed perfectly fine afterwards...
...however, having previously read about the problems reported here on XDA and on the Lenovo/Motorola community support forum regarding recent Pie updates, I decided to perform a factory wipe/reset immediately after the update. A tiresome chore to be sure, having to set everything up again aftwards, but it just seemed the prudent thing to do.
So now, some 19 hours later, my G6 is still working perfectly, with no obvious problems, and it does certainly feel smoother and more responsive than it's predecessor, PPS29.55-24, which I received at the end of March. And, yep, this new 'build' includes Google's Digital Wellbeing app integrated at the system level, so I guess that's something new to tinker around with.
Anyhow, just some thoughts regarding my experience of updating to this latest version of Pie.
Rgrds,
Ged.
test