Hello,
I have a Moto G 7 Plus (a XT1965-3 EU), which I softbricked when aborting an Android update by mistake (power button hold in bag while updating....)
I'm stuck on Android recovery with the message
Code:
Can't load Android system. Your data may be corrupt
. I have two options, Try again or Factory data reset (not an acceptable option).
What I tried so far:
- I tried this tutorial, but Motorola doesn't release the images, and sideloading this image (LAKE_RETAIL_9.0_PPWS29.98-111-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml), gives me this message :
Code:
footer is wrong
Signature verification failed
error: 21
- I tried to call the Motorola support, but they won't give me the OTA image, nor help me in a useful way.
- I wanted to install a custom recovery, but unlocking the oem would wipe everything, so no thanks.
I would rather get all the data than repairing the phone (I got it for free thanks to an Amazon Prime trial...), I have several priceless souvenirs in it, and of course I lost my backup drive when I moved away.
Thank you in advance for your help
NicolasBFR said:
Hello,
I have a Moto G 7 Plus (a XT1965-3 EU), which I softbricked when aborting an Android update by mistake (power button hold in bag while updating....)
I'm stuck on Android recovery with the message
Code:
Can't load Android system. Your data may be corrupt
. I have two options, Try again or Factory data reset (not an acceptable option).
What I tried so far:
- I tried this tutorial, but Motorola doesn't release the images, and
Click to expand...
Click to collapse
I don't know if these still work.
Update Tools
[TOOL][WIN] OTA Updates (Motorola)
[TOOL] Motorola OTA Link Generator Tool
NicolasBFR said:
sideloading this image (LAKE_RETAIL_9.0_PPWS29.98-111-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml), gives me this message :
Code:
footer is wrong
Signature verification failed
error: 21
Click to expand...
Click to collapse
That image is not an OTA, it's the full firmware and is not coded for installing with recovery, it's meant for fastboot mode.
You can try flashing with fastboot.exe
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
sd_shadow said:
I don't know if these still work.
Update Tools
[TOOL][WIN] OTA Updates (Motorola)
[TOOL] Motorola OTA Link Generator Tool
Click to expand...
Click to collapse
Unfortunatly, both require ro.build.version.full to get the appropriate OTA image, and my device won't give it to me with fastboot getvar all . Any idea how I could find it ?
As for Fastboot flash, I would loose the data, which is not an option.
NicolasBFR said:
As for Fastboot flash, I would loose the data, which is not an option.
Click to expand...
Click to collapse
No, only if you use fastboot erase userdata
sd_shadow said:
No, only if you use fastboot erase userdata
Click to expand...
Click to collapse
So, I just have to do fastboot flash with all the .img and sparsechunk files (even though my bootloader is not unlocked and the device not rooted) ?
Why do all internet tutorials erase both cache and userdata ?
And what is the worse that could happen ?
I attached a screen of the archive content:
{
"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"
}
NicolasBFR said:
So, I just have to do fastboot flash with all the .img and sparsechunk files (even though my bootloader is not unlocked and the device not rooted) ?
Why do all internet tutorials erase both cache and userdata ?
And what is the worse that could happen ?
I attached a screen of the archive content:
View attachment 5421721
Click to expand...
Click to collapse
Flashing with a locked bootloader is tricky.
Your best option is using RSD Lite with an old Windows 7 or XP Machine
The servicefile.xml and the flashfile.xml contain the flash commands
the servicefile shouldn't have the userdata line, the flashfile does.
Use Notepad++ to remove the userdata line and save, then flash with RSD Lite.
If that is not an option you can try fastboot.exe
Use the servicefile.xml and the Online FlashFile Converter
run the commands one at a time, if you get an error stop.
and see my Troubleshooting
sd_shadow said:
If that is not an option you can try fastboot.exe
Use the servicefile.xml and the Online FlashFile Converter
run the commands one at a time, if you get an error stop.
and see my Troubleshooting
Click to expand...
Click to collapse
I had USB 3.0 ports so I had the "(bootloader) is-logical:partiti : not found" error.
if you want to know my script (from Online Flashfile converter), is
Bash:
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 bluetooth BTFM.bin
fastboot flash dsp dspso.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
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 carrier
# fastboot erase ddr
fastboot oem fb_mode_clear
echo English - Process concluded!
pause
fastboot reboot
exit
I have a second computer from 2005 with 2.0 USB, I am going to try again in few hours.
Also, all my computers are on Arch Linux (Manjaro) and I download fastboot with pacman,
fastboot --version returns me
Bash:
fastboot version 31.0.2-android-tools
Installed as /usr/bin/fastboot
.
Is my fastboot version ok ?
I am so stupid, I ran the commands above using my old computer, the same fastboot version and with a USB 2.0 port, but with once in a shell script. I don't even have the logs, and now the "Can't load android system" doesn't even appear anymore ! It's just a bootloop.
What should I do ?
Okay @sd_shadow , I used the linux mfastboot recommended by your guides, and this time it managed to flash everything... but I'm back to the bootloader error menu "Can't load Android system"...
Maybe I could flash TWRP recovery (or even just fastboot boot ?), then use it to retrieve userdata and then factory reset ?
EDIT: I tried fastboot boot TWRP.img but I got "permission denied". Maybe there is a custom ROM out there that don't need the userdata ?
Related
Hello guys
Today morning i was on cyanogenmod11 and after some time i decided to restore back to stock Lollipop so i restored a backup of Lollipop system image and suddenly a error poped up saying unable to mount /data /system
I thought this might me minor issue then i tried using fastboot to flash the stock lollipop images
When i started the flashing process i got some serious errors on my cmd
"Failed to erase partition"
"failed to write partition"
And for now only Fastboot Mode is working with UTAG "flashfail" error
i tried to flash recovery images and partition gpt file but no luck looks like my partitions are messed up bad
have a look at my attachments :crying:
any help would be appreciated
Hello ?anyone there?
Sent from my GT-S5830i using XDA Free mobile app
haytham.kenway said:
Hello ?anyone there?
Click to expand...
Click to collapse
Be patient. Not everybody lives in the same timezone. Your posted at 2.32am cet.
gpt.bin and motoboot.img can't be flashed if the version on the device is the same or higher version.
Just ignore these two.
Code:
fastboot oem fb_mode_set
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
That should do it.
doppelhelix said:
Be patient. Not everybody lives in the same timezone. Your posted at 2.32am cet.
gpt.bin and motoboot.img can't be flashed if the version on the device is the same or higher version.
Just ignore these two.
Code:
fastboot oem fb_mode_set
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
That should do it.
Click to expand...
Click to collapse
i followed as u said,executed first command and got "FAILED <Remote failure>"
rest all got same errors as posted in above post
haytham.kenway said:
i followed as u said,executed first command and got "FAILED <Remote failure>"
rest all got same errors as posted in above post
Click to expand...
Click to collapse
Sometimes it's the fastboot version. Try this:
Download Minimal ADB and Fastboot and install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installtion or the desktop shortcut you choose to create and selecting "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
ABC99999999 fastboot
now copy the images into the directory where your command window is open and start flashing.
doppelhelix said:
Sometimes it's the fastboot version. Try this:
Download Minimal ADB and Fastboot and install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installtion or the desktop shortcut you choose to create and selecting "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
ABC99999999 fastboot
now copy the images into the directory where your command window is open and start flashing.
Click to expand...
Click to collapse
dude i know how to flash these images,and i tried latest version of fastboot from google still problem persists
dear brother
i unlock boot-loader and re-lock boot loader once.
now my problem my unlock boot-loader again because my emei is messing And restore efs file.
now i lock my bootloader but my bootloader is not lock. i try again and again.:crying:
whan i flash stock rom i donot use two command that is
"fastboot erase modemst1
fastboot erase modemst2":good:
i try this command
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 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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
fastboot flash logo logo.bin
fastboot flash boot boot.img
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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash boot boot.img
fastboot oem lock
fastboot oem lock command that show
check allow oem unlock in android setting > developer.
but in developer option the oem in already enable show
plz help me to solve this problem
and tale me how i can use 2 command
fastboot erase modemst1
fastboot erase modemst2
here the link the cmd replay and developer option link
{
"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"
}
and developer option
try with this rom https://androidfilehost.com/?fid=673956719939831738 this is latest version 61-5 with March patch
With unlocked bootloader, and with TWRP and magisk root installed, you currently can't install any of the motorola OTA:s.
Below have been tested on XT1965-3 while on RETEU, PPWS29.98-66 (security updates installed up until 1 january 2019), with TWRP 3.3.0 installed and rooted, to update to latest stock rom PPWS29.98-66-2 (security updates installed up until 1 april 2019), without wiping internal storage and /data (i.e. all files, apps and settings untouched).
I take no responsibility what so ever for using this guide. Below worked for me. Be prepared to lose all your files, hard brick your phone etc.
Get latest official stock firmware, I got it from https://forum.xda-developers.com/showpost.php?p=79653779&postcount=6 , unzip it
Connect your phone to your computer with usb-cable. Put your phone in flash mode (power button+volume down), open your terminal application (below tested on macOS and linux), get root
sudo -s
navigate in terminal to folder where you unzipped the full stock rom
check the below commands visavi the files from your downloaded stock rom (below works for version mentioned above - future updates may contain more or fewer for example sparse files).
fastboot getvar max-sparse-size
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 bluetooth BTFM.bin
fastboot flash dsp dspso.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
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 carrier
fastboot erase ddr
fastboot flash logo logo.bin
fastboot reboot
Let your phone reboot and pray
After a hopefully successfull boot with everything still intact, then adb fastboot TWRP and from TWRP reinstall your root.
in flash mode once again
fastboot boot twrp-build-version-lake.img
wedgehog said:
With unlocked bootloader, and with TWRP and magisk root installed, you currently can't install any of the motorola OTA:s.
Below have been tested on XT1965-3 while on RETEU, PPWS29.98-66 (security updates installed up until 1 january 2019), with TWRP 3.3.0 installed and rooted, to update to latest stock rom PPWS29.98-66-2 (security updates installed up until 1 april 2019), without wiping internal storage and /data (i.e. all files, apps and settings untouched).
I take no responsibility what so ever for using this guide. Below worked for me. Be prepared to lose all your files, hard brick your phone etc.
Get latest official stock firmware, I got it from https://forum.xda-developers.com/showpost.php?p=79653779&postcount=6 , unzip it
Connect your phone to your computer with usb-cable. Put your phone in flash mode (power button+volume down), open your terminal application (below tested on macOS and linux), get root
sudo -s
navigate in terminal to folder where you unzipped the full stock rom
check the below commands visavi the files from your downloaded stock rom (below works for version mentioned above - future updates may contain more or fewer for example sparse files).
fastboot getvar max-sparse-size
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 bluetooth BTFM.bin
fastboot flash dsp dspso.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
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 carrier
fastboot erase ddr
fastboot flash logo logo.bin
fastboot reboot
Let your phone reboot and pray
After a hopefully successfull boot with everything still intact, then adb fastboot TWRP and from TWRP reinstall your root.
in flash mode once again
fastboot boot twrp-build-version-lake.img
Click to expand...
Click to collapse
with XT1965-3_LAKE_RETEU_9.0_PPW29.98-111_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml at least for me dirty flash failed, rom didn't boot
did a backup of /data/ to external storage from TWRP with internal storage decrypted (had to boot TWRP from fastboot a couple of times before the decrypt password prompt were shown on boot of TWRP)
did also a backup of internal storage over MTP with TWRP to computer.
then flashed again with below commands, WHICH WILL ERASE INTERNAL STORAGE
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 bluetooth BTFM.bin
fastboot flash dsp dspso.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
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 carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Thereafter successfull boot, reboot to flash mode, boot TWRP again, restore internal storage over MTP from TWRP, restore of data from backup to external storage which were made above
all apps and settings back, and on latest moto firmware.
any chance of capturing the delta OTA's to make them twrp-flashable?
Lupask said:
any chance of capturing the delta OTA's to make them twrp-flashable?
Click to expand...
Click to collapse
Would probably be doable as in almost all other devices in general and older motorola devices in particular have had that. I for one do not have the knowledge of how to do that (and not the time available even if I had that knowledge =) )
I can confirm that at least for me, a dirty flash like the one described in post 1 in this thread worked again with the latest OTA/firmware for RETEU - XT1965-3_LAKE_RETEU_9.0_PPWS29.98-111-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC, when written over the second latest (XT1965-3_LAKE_RETEU_9.0_PPW29.98-111_subsidy-DEFAULT_regulatory-DEFAULT_CFC)
I did however have trouble booting the latest twrp twrp-3.3.1-0-v5.1-lake-jlb from fastboot, phone rebooted after it was sent over adb boot instead of booting twrp it went straight back to fastboot. Tried many times with rebooting to phone home screen in between. But adb fastbooting the older twrp-3.3.0-lake worked straight away, and thereafter installing twrp-3.3.1-0-v5.1-lake-jlb with it's zip worked straight away.
I have tried to get the OTA file for my g7plus from a bugreport.
But it is only 100 Mb rather than the more than 1 Gb is see most roms.
Could it actually be an OTA update? Screenshot of the .zip contents attached.
SvenHee said:
I have tried to get the OTA file for my g7plus from a bugreport.
But it is only 100 Mb rather than the more than 1 Gb is see most roms.
Could it actually be an OTA update? Screenshot of the .zip contents attached.
Click to expand...
Click to collapse
Doesn't seem likely, date is 2009
For reference, here is the line where I found this url:
Code:
12-06 14:19:06.869 5831 14719 D OtaApp : UpdaterEngineHelper:applyPayload, applying payload with downloadUrl = https://dlmgr.gtm.svcmot.com/dl/dlws/1/download/*lots-of-stuff*%3D offsetvalue = 9258 fileSize = 107713236
Lupask said:
any chance of capturing the delta OTA's to make them twrp-flashable?
Click to expand...
Click to collapse
It would be no problem to catch them and make them TWRP flashable. But it's strongly not recommended to do that!! Do an OTA-update only if your device is fully on stock! Otherwise the OTA-update will override incorrect blocks of your partitions and this could crash your entire system irreversible.
starting from the Chinese ROM http://ui.nubia.cn/rom/detail/62
Download download necessary files https://drive.google.com/open?id=16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm
fastboot oem nubia_unlock NUBIA_NX629J
fastboot erase system
fastboot erase modem
fastboot reboot
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash dsp dspso.bin
fastboot flash parameter parameter.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img (if you failed, don't worry, try this step again and again.)
fastboot reboot
enter recovery, use a FAT32 pendrive format, add Chinese ROM, rename it (update.zip) to OTG flash.
Everything works again.
good luck.
emmegitony said:
Download download necessary files https://drive.google.com/drive/folde...Ym?usp=sharing
good luck.
Click to expand...
Click to collapse
404. That’s an error.
The requested URL was not found on this server. That’s all we know.
nabbed said:
404. That’s an error.
The requested URL was not found on this server. That’s all we know.
Click to expand...
Click to collapse
modified link: https://drive.google.com/open?id=16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm
Please help me with your knowledge for a little while. I really need help because my android is bootlooping and this is the only phone I have. I really need your help here.
-I followed this guide with little differences https://forum.xda-developers.com/moto-e5/how-to/guide-root-twrp-moto-e5-play-explained-t3856182
-I took precautions and I downloaded the respective twrp for my phone (moto e5 nora).
-I couldn't make a backup because I'm lower-class college student and I can't afford a micro sd bigger than 4gb (I should have given up here).
-I installed Magisk and i thought it went well because no errors showed (at least that's what I think)
-Bootloop showing some numbers (80012a99-867fda48-...)
-I tried to uninstall using the uninstaller.zip so I could install an older version of Magisk but twrp says "cannot access /data please uninstall with magisk manager" but I just can't do it because android it's bootlooping.
Other data (it may be useful):
-After installing the last version of Magisk, abd won't recognize the phone ("adb devices") but "fastboot devices" will.
-I cannot repair /data but I can format it to ext4,ext2, etc (but it didn't work).
-I'm downloading stock image but I don't know how safe will it be to reinstall the whole Android. I'm afraid I can permanently damage my phone after what I have done here.
This is the first time I post here. I don't usually ask for help, I don't like to bother people. Thanks in advance and forgive me for my English!
FIXED
If someone has the same problem, this is what I did:
1-Download the LAST (this is very important) version ROM. I recommend lolinet (dot) com for our Moto E5.
2-Download adb and decompress the ROM into the adb folder.
3-Open command promt and go to adb's directory.
4-Check that your phone is being recognized by your pc:
Code:
fastboot devices
5- Copy and paste:
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
Then fastboot reboot and there you go!
I'm very glad and I hope you, future readers, find this useful enough to get your phone running as it used to run when we were real happy.