Related
Note :
Do not erase/flash Bootloader file preloader.img or preloader.bin
fastboot erase preloader
fastboot flash preloader preloader.img
Do not erase/flash partition table file pgpt.img/gpt.img or pgpt.bin/gpt.bin
fastboot erase pgpt or gpt
fastboot flash pgpt or gpt pgpt.img or gpt.img
About :
With this guide you will restore stock firmware and re-lock your device bootloader.This guide is from Moto E4 Mediatek variant SKU XT1760 but can work with any Moto E4 Variant. Just grab the partition info and partition name in fastboot mode with fastboot command "fastboot getvar all". But this step isn't necessary if you take backup with miracle tool. It will dump whole firmware in scatter format. So, no need to worry if you have a different variant of Moto E4
This guide will give you the following :
PHP:
<bootloader> : warranty (YES)
<bootloader> : unlocked (NO)
<bootloader> : secure (YES)
>> device unlocked (we cannot remove this warning !)
Requirement :
• Place all the firmware files here:
C:\Program Files\Minimal ADB and Fastboot\HERE
• A laptop/Desktop
• Unlocked Bootloader
• Enabled USB Debugging
• Moto E4 Any Variant
• USB Cable
• Minimal Adb & Fastboot Tool
• Miracle Tool
• Adb & Fastboot Commands
Step 1 : Boot into bootloader mode
Switch off your device
Hold power button and volume down button
When you see START release buttons
This is fastboot mode
Step 2 : Reboot into bootloader
Note : i recommended you to use a laptop than that of desktop. For continuous power supply. Fully charge your laptop battery.
Connect with USB Cable
Open fastboot command window
Type fastboot command:
PHP:
fastboot reboot bootloader
Now your device in fastboot mode
--- Do not disconnect ---
Step 3 : Flashing stock factory images
Type these fastboot commands:
Erasing partitions first
if you have a different variant of Moto E4, just write all the partitions name except bootloader(preloader) in a text file and replace them with the below partition names.
PHP:
fastboot erase boot
fastboot erase efuse
fastboot erase expdb
fastboot erase flashinfo
fastboot erase frp
fastboot erase hw
fastboot erase keystore
fastboot erase lk
fastboot erase logo
fastboot erase metadata
fastboot erase nvdata
fastboot erase nvram
fastboot erase oem
fastboot erase oemkeystore
fastboot erase otp
fastboot erase para
fastboot erase persist
fastboot erase proinfo
fastboot erase protect1
fastboot erase protect2
fastboot erase recovery
fastboot erase seccfg
fastboot erase secro
fastboot erase tee1
fastboot erase tee2
fastboot erase utags
fastboot erase system
fastboot erase userdata
--- Do not disconnect ---
Now flash stock factory images
PHP:
fastboot flash boot boot.img
fastboot flash efuse efuse.img
fastboot flash expdb expdb.img
fastboot flash flashinfo flashinfo.img
fastboot flash frp frp.img
fastboot flash hw hw.img
fastboot flash keystore keystore.img
fastboot flash lk lk.img
fastboot flash logo logo.img
fastboot flash metadata metadata.img
fastboot flash nvdata nvdata.img
fastboot flash nvram nvram.img
fastboot flash oem oem.img
fastboot flash oemkeystore oemkeystore.img
fastboot flash otp otp.img
fastboot flash para para.img
fastboot flash persist persist.img
fastboot flash proinfo proinfo.img
fastboot flash protect1 protect1.img
fastboot flash protect2 protect2.img
fastboot flash recovery recovery.img
fastboot flash seccfg seccfg.img
fastboot flash secro secro.img
fastboot flash tee1 tee1.img
fastboot flash tee2 tee2.img
fastboot flash utags utags.img
fastboot flash system system.img
--- Do not disconnect ---
Step 4 : Re-lock bootloader
Type this fastboot command
PHP:
fastboot oem lock
Hit volume up button
Again type fastboot command
PHP:
fastboot reboot
Step 5 : Fix for system image sparse chunk
Used only when fastboot command failed to write system in system partition else when you see "sparse chunk error" wait for 10 minutes. you will see 1/20 or something operations. if not or command ended up with chunk error than use this command.Use this fastboot command:
PHP:
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 system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash system system.img_sparsechunk.17
fastboot flash system system.img_sparsechunk.18
fastboot flash system system.img_sparsechunk.19
fastboot flash system system.img_sparsechunk.20
Step 6 : Do not use this fastboot command
PHP:
fastboot erase preloader
This will wipe bootloader from bootloader partition and your device ended up with permanent Hard brick.
Step 7 : Fix for bootloader(fastboot) drivers
if your device isn't recognized in fastboot mode, Download USB Drivers from below attachment. Select manually "android_winusb.inf" file while updating driver software.
Download Link :
https://drive.google.com/file/d/0B0Oo-yXGY-zUMG1XRG52dFZpV1k/view
Step 8 : How to dump stock firmware
Thread link below:
https://forum.xda-developers.com/moto-e4/how-to/how-to-backup-stock-rom-moto-e4-variants-t3654976
Guide to fix boot_dataerr in miracle tool if it failed to dump stock rom
Look at the log window in miracle tool there in driver part you will see MTK preloader USB COM PORT#7. We don't need Preloader driver right now, we need MTK Android DA USB COM PORT#7. The solution is update your device driver software to fix this problem else you won't able to dump firmware in scatter format also we don't have official factory images. This is the only method to revert on purely unrooted stock firmware.
Step 9 : Minimal Adb & Fastboot download link
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
This is my last thread in Moto E4 forum and i won't support this device anymore.
Does this work for all variants?
andMego said:
Does this work for all variants?
Click to expand...
Click to collapse
yes, work with all variants.
already mentioned in OP.
kartik verma said:
This is my last thread in Moto E4 forum and i won't support this device anymore.
Click to expand...
Click to collapse
After you came here and cluttered the forum with a crap load of pointless threads and posts? I love it! Thanks.
amarc78 said:
After you came here and cluttered the forum with a crap load of pointless threads and posts? I love it! Thanks.
Click to expand...
Click to collapse
pointless threads and posts
so my posts are useless. sorry if my posts aren't fit into your expectation.
kartik verma said:
pointless threads and posts
so my posts are useless. sorry if my posts aren't fit into your expectation.
Click to expand...
Click to collapse
Personally I'm very thankful for this post, as I couldn't figure out how to do it myself. I was able to reflash stock and lock the bootloader but it wouldn't boot since it always said it was modified, so I just returned my previous e4 with the bootloader unlocked and the noverify thing flashed.
my phone refuses to verify boot.img
KyleBryant said:
my phone refuses to verify boot.img
Click to expand...
Click to collapse
will it asks for boot.sig or anything else. let me know
I figured it out
KyleBryant said:
I figured it out
Click to expand...
Click to collapse
How?
Motorola doesn't release verified boot images. The reason it wouldn't boot for me is because I forgot to flash the no verity file lol
KyleBryant said:
Motorola doesn't release verified boot images. The reason it wouldn't boot for me is because I forgot to flash the no verity file lol
Click to expand...
Click to collapse
How do I lock the bootloader and get it to verify the boot image?
No idea
andMego said:
How do I lock the bootloader and get it to verify the boot image?
Click to expand...
Click to collapse
fastboot oem lock (relock the bootloader)
their is nothing to do with boot image. verification is for system if you changed something and didn't disable verity " MOUNT FLAG /system ro wait,verify" your device ain't gonna boot into system.
dm-verity can be disabled by two ways either remove "verify" or change the default.prop values "ro.secure=0".
kartik verma said:
fastboot oem lock (relock the bootloader)
their is nothing to do with boot image. verification is for system if you changed something and didn't disable verity " MOUNT FLAG /system ro wait,verify" your device ain't gonna boot into system.
dm-verity can be disabled by two ways either remove "verify" or change the default.prop values "ro.secure=0".
Click to expand...
Click to collapse
Before I returned my other e4 I flashed the stock images with rsdlite and then did fastboot oem lock but then the phone wouldn't boot since it said it was modified so I had to unlock the bootloader again and flash the noverify thing in TWRP. How should I have done it to be able to return the phone with the bootloader locked?
andMego said:
Before I returned my other e4 I flashed the stock images with rsdlite and then did fastboot oem lock but then the phone wouldn't boot since it said it was modified so I had to unlock the bootloader again and flash the noverify thing in TWRP. How should I have done it to be able to return the phone with the bootloader locked?
Click to expand...
Click to collapse
" it said it was modified"
First of all remove all the changes you have done in system else if you don't know where you have done changes wipe system partition and reflash system image in system partition.
don't flash gpt.img, pgpt.img, bootloader.img in fastboot mode also do not erase data in fastboot mode "fastboot erase userdata". your device must be charged upto 80% if you want your device boot after a clean flash.
as i am also facing over discharged problem.
kartik verma said:
" it said it was modified"
First of all remove all the changes you have done in system else if you don't know where you have done changes wipe system partition and reflash system image in system partition.
don't flash gpt.img, pgpt.img, bootloader.img in fastboot mode also do not erase data in fastboot mode "fastboot erase userdata". your device must be charged upto 80% if you want your device boot after a clean flash.
as i am also facing over discharged problem.
Click to expand...
Click to collapse
Kartik dude tell me if this is possible....
To roll back I flash unmodified stock boot image and flash stock recovery through fastboot - reboot system - reset -relock bootloader.....can I able to do this?
drganbds said:
Kartik dude tell me if this is possible....
To roll back I flash unmodified stock boot image and flash stock recovery through fastboot - reboot system - reset -relock bootloader.....can I able to do this?
Click to expand...
Click to collapse
follow this method :
erase partitions only if you have factory images
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase boot
fastboot flash boot boot.img
erase system if you done changes in system partition. if not leave this step
fastboot erase system
fastboot flash system system.img
kartik verma said:
follow this method :
erase partitions only if you have factory images
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase boot
fastboot flash boot boot.img
erase system if you done changes in system partition. if not leave this step
fastboot erase system
fastboot flash system system.img
Click to expand...
Click to collapse
Excellent then do me a favour buddy I need stock recovery and unmodified boot images of Moto e4 mediatek variant.
drganbds said:
Excellent then do me a favour buddy I need stock recovery and unmodified boot images of Moto e4 mediatek variant.
Click to expand...
Click to collapse
i will upload official factory images when i get free time
Can anybody provide with the flashing instruction for moto g5
yolomonkey said:
Can anybody provide with the flashing instruction for moto g5
Click to expand...
Click to collapse
Assuming you have fastboot installed on your pc
Download firmware and unzip to where you have fastboot
Open command prompt at fastboot location with firmware
type the following although I have marked lines that you should not use unless you have to as flashing wrong firmware can damage your device
Code:
fastboot oem fb_mode_set Only required if you wish to relock bootloader - if not skip it
fastboot flash partition gpt.bin Do not use unless you want to repartition your device - incorrect file will damage your phone
fastboot flash bootloader bootloader.img Do not use unless you want to replace the bootloader - flashing wrong file will hard brick
fastboot flash logo logo.bin No need to flash if you are going to flash a custom rom after and have already flashed a modded version
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata Will erase everything on internal storage but you need to do it
fastboot erase customize Not sure about this - might be for other device
fastboot erase clogo Not sure about this - might be for other device
fastboot oem fb_mode_clear Only required to relock bootloader if you used the very first command
fastboot reboot
NOt working
My device keeps booting to the recovery
even though i flashed my recovery. it boots to twrp
yolomonkey said:
My device keeps booting to the recovery
even though i flashed my recovery. it boots to twrp
Click to expand...
Click to collapse
have you read the FAQs on my twrp thread because the answer is there (assuming you have flashed a custom rom and can boot it through the bootloader by selecting start)
TheFixItMan said:
have you read the FAQs on my twrp thread because the answer is there (assuming you have flashed a custom rom and can boot it through the bootloader by selecting start)
Click to expand...
Click to collapse
could you please link it. I am so grateful for you replying this fast
yolomonkey said:
could you please link it. I am so grateful for you replying this fast
Click to expand...
Click to collapse
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
FAQs are on 2nd post
Guyzzz after erase config through fastboot .... Won't get onto O.S I used xfstk , flash raw file through fastboot , all done good but while start system stucked. .. recovery stills remains
Sideload via adb done.. system stucked
Upgrade through adb to M but stucked at boot
Unlock bootloader via fastboot works installed TWRP flash custom ROM also stucked at boot
While wipping or installing shows error on TWRP...
Unable to mount Config
Help me guyzzz is this is a mother board issue ??
user531xda said:
Guyzzz after erase config through fastboot .... Won't get onto O.S I used xfstk , flash raw file through fastboot , all done good but while start system stucked. .. recovery stills remains
Sideload via adb done.. system stucked
Upgrade through adb to M but stucked at boot
Unlock bootloader via fastboot works installed TWRP flash custom ROM also stucked at boot
While wipping or installing shows error on TWRP...
Unable to mount Config
Help me guyzzz is this is a mother board issue ??
Click to expand...
Click to collapse
well this is issue with partition. if you are on twrp try to repair it with advanced wipe and repair option. use xFSTK. and then flash raw with commands not with AFT
sukhwant717 said:
well this is issue with partition. if you are on twrp try to repair it with advanced wipe and repair option. use xFSTK. and then flash raw with commands not with AFT
Click to expand...
Click to collapse
On TWRP there's no config column to select
On mount tab on TWRP I got config column but can't able to tick (select) it
I done xfstk 10 20 times and flash with fastboot commands with your thread everything seems good on PC and device but after last command fastboot reboot it reboots to system and stuck there before the setup wizard
sukhwant717 said:
well this is issue with partition. if you are on twrp try to repair it with advanced wipe and repair option. use xFSTK. and then flash raw with commands not with AFT
Click to expand...
Click to collapse
I leaved device for 1 hour nothing happens
Reboot to recovery then format data then reboot still stucked at boot logo... Update through adb sideload .. update from adb complete then reboot and after that still stuck on boot logo...
Unlock bootloader then flash TWRP and try custom rom they also stuck on boot logo
Help me m stucked and really need help
user531xda said:
Help me m stucked and really need help
Click to expand...
Click to collapse
device can not boot untill and unless config partition is formatted. there are lot of things you can try.
fastboot erase config
fastboot erase cache
fastboot erase data
fastboot erase factory
then without reboot flash raw firmware with commands
sukhwant717 said:
device can not boot untill and unless config partition is formatted. there are lot of things you can try.
fastboot erase config
fastboot erase cache
fastboot erase data
fastboot erase factory
then without reboot flash raw firmware with commands
Click to expand...
Click to collapse
Done but still same , also tried fastboot -w but not worked ... Can I use fastboot format config?? If yes then how because I think it needs partition size and partition type for the format command through fastboot
user531xda said:
Done but still same , also tried fastboot -w but not worked ... Can I use fastboot format config?? If yes then how because I think it needs partition size and partition type for the format command through fastboot
Click to expand...
Click to collapse
format command itself format it as ext4 type. you can simply use fastboot format config.
another thing you can try is.
fastboot oem start_partitioning
fastboot oem wipe config
fastboot oem stop_partitioning
you can also try format config command after starting partitioning. try once without starting partitioning if not works second time try after partitioning. use wipe command only after starting partitioning
---------- Post added at 09:33 AM ---------- Previous post was at 09:33 AM ----------
user531xda said:
Done but still same , also tried fastboot -w but not worked ... Can I use fastboot format config?? If yes then how because I think it needs partition size and partition type for the format command through fastboot
Click to expand...
Click to collapse
format command itself format it as ext4 type. you can simply use fastboot format config.
another thing you can try is.
fastboot oem start_partitioning
fastboot oem wipe config
fastboot oem stop_partitioning
you can also try format config command after starting partitioning. try once without starting partitioning if not works second time try after partitioning. use wipe command only after starting partitioning
sukhwant717 said:
format command itself format it as ext4 type. you can simply use fastboot format config.
another thing you can try is.
fastboot oem start_partitioning
fastboot oem wipe config
fastboot oem stop_partitioning
you can also try format config command after starting partitioning. try once without starting partitioning if not works second time try after partitioning. use wipe command only after starting partitioning
---------- Post added at 09:33 AM ---------- Previous post was at 09:33 AM ----------
format command itself format it as ext4 type. you can simply use fastboot format config.
another thing you can try is.
fastboot oem start_partitioning
fastboot oem wipe config
fastboot oem stop_partitioning
you can also try format config command after starting partitioning. try once without starting partitioning if not works second time try after partitioning. use wipe command only after starting partitioning
Click to expand...
Click to collapse
Thanks alot sir...really thanks it worked ..ty ty :fingers-crossed:
user531xda said:
Thanks alot sir...really thanks it worked ..ty ty :fingers-crossed:
Click to expand...
Click to collapse
glad to know that helped
sukhwant717 said:
format command itself format it as ext4 type. you can simply use fastboot format config.
another thing you can try is.
fastboot oem start_partitioning
fastboot oem wipe config
fastboot oem stop_partitioning
you can also try format config command after starting partitioning. try once without starting partitioning if not works second time try after partitioning. use wipe command only after starting partitioning
---------- Post added at 09:33 AM ---------- Previous post was at 09:33 AM ----------
format command itself format it as ext4 type. you can simply use fastboot format config.
another thing you can try is.
fastboot oem start_partitioning
fastboot oem wipe config
fastboot oem stop_partitioning
you can also try format config command after starting partitioning. try once without starting partitioning if not works second time try after partitioning. use wipe command only after starting partitioning
Click to expand...
Click to collapse
Hi guys.
I have the same problem. But
"fastboot oem start_partitioning
fastboot oem wipe config
fastboot oem stop_partitioning"
not working for me...
FAILED (remote: unknown command)
finished. total time: -0.000s
My Redmi 4x have propably broken partitions. I didn't flash global soft because his stopped... A lot of errors, problems.
I will eraseing/format cache, userdata, system, config etc.
Only TWRP 3.0.3 has working but only when i flash with fastboot and boot. When twrp are stuck, i must flash once again with fastboot...
When I am in twrp, command adb devices see my phone like "8h231h8921 recovery"
Please, help!
WARNING: if the gpt.bin flash did not work, please stop and do not continue with the rest of the commands. It has been brought to my attention that software upgrades to the phone has changed the gpt and may not allow you to go back to the original stock firmware.
For all of you who DID NOT do a System image backup in TWRP and then found out your backup doesn't work.
First get your stock firmware here, the only place to get Moto stock firmware!
https://firmware.center/firmware/Motorola/Moto E4 Plus/Stock/
Then get fastboot. Google fastboot or grab the one from here: This one still works:
https://forum.xda-developers.com/showthread.php?t=2317790
If your fastboot directory isn't in your $PATH or you don't know how to do that, then copy fastboot into the same folder where you unzipped your stock firmware.
Got to the folder where you put everythig, open up a command or powershell prompt. Hold down shift, right click, "open command window here".
Now for the fun. You veterans can just look at the flashfile.xml to see the order. Those of you who are new, here are the commands you need to do. You could probably copy the entire thing and past it in your command window at one time. But I like to type it out.... line by line. You know, old school.
Commands:
Code:
fastboot oem fb_mode_set
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem 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 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
the command to erase ddr will probably fail, but that shouldn't affect anything. I have tested by bringing my Moto E4 Plus that was running Lineage OS back to 100% stock. Of course, then I went right back to Lineage
Outstanding. Thank you for the post. I'm sure this will get used quite a bit. I did do a backup but it's always nice to have contingencies at the ready.
Sent from my Nexus 10 using XDA Premium HD app
I know this may sound like a stupid question, but which firmware package should I download and use for the Device purchased straight from Motorola? There are quite a few there and I don't want to flash the wrong one. This device was supposed too work on any US carrier and I would like to keep it that way, but my carrier is Verizon. All I had to do, when I got the device was install my Verizon Sim out of my Nexus 6 and it worked great. I do test for Cricket network too and that is a GSM radio so as I said, I would like it to have the firmware that would have come right from Motorola for this specific device. Thank you in advance.
glockman4519 said:
I know this may sound like a stupid question, but which firmware package should I download and use for the Device purchased straight from Motorola? There are quite a few there and I don't want to flash the wrong one. This device was supposed too work on any US carrier and I would like to keep it that way, but my carrier is Verizon. All I had to do, when I got the device was install my Verizon Sim out of my Nexus 6 and it worked great. I do test for Cricket network too and that is a GSM radio so as I said, I would like it to have the firmware that would have come right from Motorola for this specific device. Thank you in advance.
Click to expand...
Click to collapse
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
aj2333 said:
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thank you very much. You sir are an awesome person.
I have another question and forgive me for being a pain but all steps went ok but at the end where the re-boot takes place it just keeps flashing back and forth from a black screen with "Bad Key" in the upper left corner and then to a screen with a colorful circle that says "erasing". I figured it was just doing a factory reset but it just keeps flashing back and forth between the 2 screens. Any idea what to try ? I tryed to boot to recovery and get the same thing. Thank you for any help.
glockman4519 said:
I have another question and forgive me for being a pain but all steps went ok but at the end where the re-boot takes place it just keeps flashing back and forth from a black screen with "Bad Key" in the upper left corner and then to a screen with a colorful circle that says "erasing". I figured it was just doing a factory reset but it just keeps flashing back and forth between the 2 screens. Any idea what to try ? I tryed to boot to recovery and get the same thing. Thank you for any help.
Click to expand...
Click to collapse
Did you remember to do an fastboot OEM fb_mode_clear?
no I didn't do that. I will go back over your instructions and re-do it. Thank you again for your assistance. I usually don't bug people for help and try to fix things on my own so I really appreciate you help.
Sent from my G3223 using XDA Premium HD app
Actually that is the command input right before the reboot command so I guess I did do that command. I will research this more and thank you for your help once again.
glockman4519 said:
Actually that is the command input right before the reboot command so I guess I did do that command. I will research this more and thank you for your help once again.
Click to expand...
Click to collapse
The cmd commands above aren't written correctly for carrier unlocked E4 Plus's. Hlos.bin isn't in the unlocked stock ROM, NON-HLOS.bin is. Also, "flasty" should be flash. Here is the correct commands. This worked on my unlocked phone.
Code:
fastboot oem fb_mode_set
fastboot flash gpt 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 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
doodalydoo said:
The cmd commands above aren't written correctly for carrier unlocked E4 Plus's. Hlos.bin isn't in the unlocked stock ROM, NON-HLOS.bin is. Also, "flasty" should be flash. Here is the correct commands. This worked on my unlocked phone.
Click to expand...
Click to collapse
You Sir are the man. I can't thank you enough for your help.
Update: Awesome.... It worked like a charm. I have everything copied now in case I hit the wall again. Thank you once again.
So I have used this and it worked great. However does anyone know when the firmware in that download will be updated to the latest version?
XT1775 rom's is possible install on XT1776 ?
almao11 said:
XT1775 rom's is possible install on XT1776 ?
Click to expand...
Click to collapse
Not Stock ROM, no. Custom ROMs should work fine tho
---------- Post added at 11:41 AM ---------- Previous post was at 11:32 AM ----------
For OP @zerogun & those of you wondering which stock ROM Firmware to grab for Boost Mobile's XT1776 (owens), I used this one and it worked 100%. The Fastboot cmd list in the 10th post or so i nears perfect, (all the rest is Golden) except that for the Boost Mobile FW's:
fastboot flash oem.img
..needs to actually be:
fastboot flash oem.img_sparsechunk.0
fastboot flash oem.img_sparsechunk.1
Cool miner malware that pops up on firmware.center.
mattleft said:
Cool miner malware that pops up on firmware.center.
Click to expand...
Click to collapse
I haven't had that problem. Have you scanned your PC for virus/malware?
I would like to relock my bootloader but on this firmware it says the boot is not signed. Can I relock it after I do the ota as they should be signed then right?
bcrichster said:
Not Stock ROM, no. Custom ROMs should work fine tho
---------- Post added at 11:41 AM ---------- Previous post was at 11:32 AM ----------
For OP @zerogun & those of you wondering which stock ROM Firmware to grab for Boost Mobile's XT1776 (owens), I used this one and it worked 100%. The Fastboot cmd list in the 10th post or so i nears perfect, (all the rest is Golden) except that for the Boost Mobile FW's:
fastboot flash oem.img
..needs to actually be:
fastboot flash oem.img_sparsechunk.0
fastboot flash oem.img_sparsechunk.1
Click to expand...
Click to collapse
Did this allow you to use a non Boost/Sprint sim card?
Thanks,
Victor
mindstream98 said:
Did this allow you to use a non Boost/Sprint sim card?
Thanks,
Victor
Click to expand...
Click to collapse
I read in another thread that it was possible by using a Custom ROM but haven't tried it myself..
Although the Custom ROMs should work on several Carriers, this is a "Completely Back to Stock" thread..
Running an Xp3r!meπt with my XT1776
zerogun said:
For all of you who DID NOT do a System image backup in TWRP and then found out your backup doesn't work.
First get your stock firmware here, the only place to get Moto stock firmware!
https://firmware.center/firmware/Motorola/Moto E4 Plus/Stock/
Then get fastboot. Google fastboot or grab the one from here: This one still works:
https://forum.xda-developers.com/showthread.php?t=2317790
If your fastboot directory isn't in your $PATH or you don't know how to do that, then copy fastboot into the same folder where you unzipped your stock firmware.
Got to the folder where you put everythig, open up a command or powershell prompt. Hold down shift, right click, "open command window here".
Now for the fun. You veterans can just look at the flashfile.xml to see the order. Those of you who are new, here are the commands you need to do. You could probably copy the entire thing and past it in your command window at one time. But I like to type it out.... line by line. You know, old school.
Commands:
Code:
fastboot oem fb_mode_set
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem 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 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
the command to erase ddr will probably fail, but that shouldn't affect anything. I have tested by bringing my Moto E4 Plus that was running Lineage OS back to 100% stock. Of course, then I went right back to Lineage
Click to expand...
Click to collapse
I used this to go back to stock, now my phone wont even turn on, at all.
Are we able to change slots in fastboot?
what are the fastboot commands?
Thanks!
This maybe?
Code:
fastboot --set-active=b (if your current active slot is a)
fastboot --set-active=a (if your current slot is b)
https://forum.xda-developers.com/pixel-xl/help/multiple-bootloader-slots-t3600228
lucky_strike33 said:
Are we able to change slots in fastboot?
what are the fastboot commands?
Thanks!
Click to expand...
Click to collapse
fastboot set_active a
fastboot set_active b
Either works