Related
Hi, friends. Sorry, but my english is bad.
I tell you, I flash my firmware stock XT1575 6.0, but failed to be carried out correctly. Motorola have installed the drivers, as should be. I tried to flash with RSD Lite 6.2.4, and using commands in both made the same mistake at the same stage flashing. This is the error:
C:\Users\Lisandro\Desktop\platform-tools>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (41686 KB)...
OKAY [ 1.041s]
writing 'modem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.059s
Bootloader is unlocked.
I'm from Argentina, I tried a SIM Personal and working properly, test it with a SIM Claro AR and does not work, try registar network and tells me: "The selected network (Claro AR) is not available".
From already thank you very much.
I hope to resolve this soon.
Regards!
Lisandro4m41 said:
Hi, friends. Sorry, but my english is bad.
I tell you, I flash my firmware stock XT1575 6.0, but failed to be carried out correctly. Motorola have installed the drivers, as should be. I tried to flash with RSD Lite 6.2.4, and using commands in both made the same mistake at the same stage flashing. This is the error:
C:\Users\Lisandro\Desktop\platform-tools>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (41686 KB)...
OKAY [ 1.041s]
writing 'modem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.059s
Bootloader is unlocked.
I'm from Argentina, I tried a SIM Personal and working properly, test it with a SIM Claro AR and does not work, try registar network and tells me: "The selected network (Claro AR) is not available".
From already thank you very much.
I hope to resolve this soon.
Regards!
Click to expand...
Click to collapse
Modem flash fails frequently, repeat the command until it returns OK (may take 2 or 3 times) then continue. Make sure to follow all the steps in order, the order is important.
acejavelin said:
Modem flash fails frequently, repeat the command until it returns OK (may take 2 or 3 times) then continue. Make sure to follow all the steps in order, the order is important.
Click to expand...
Click to collapse
Ok, thanks. I'll keep trying. Do you think that these commands are properly sorted?
fastboot oem fb_mode_set oem
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.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
Lisandro4m41 said:
Ok, thanks. I'll keep trying. Do you think that these commands are properly sorted?
fastboot oem fb_mode_set oem
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.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
Click to expand...
Click to collapse
Depends on the firmware you are using.. according to Moto that isn't the right process, but using the latest MXPE firmware from here it appears correct. It is best to look in the firmware ZIP and find the flashfile.xml file and follow that, open it in a reasonable XML capable editor (not Notepad, but Notepad++ works well) and you can see the exact process step by step.
In looking at the file, pay attention to the steps with "operation" in them, those are the fastboot commands.
acejavelin said:
Depends on the firmware you are using.. according to Moto that isn't the right process, but using the latest MXPE firmware from here it appears correct. It is best to look in the firmware ZIP and find the flashfile.xml file and follow that, open it in a reasonable XML capable editor (not Notepad, but Notepad++ works well) and you can see the exact process step by step.
In looking at the file, pay attention to the steps with "operation" in them, those are the fastboot commands.
Click to expand...
Click to collapse
Thanks! Right now I'm downloading the firmware of the Motorola official page. I hope it works. Thanks again!
I downloaded the firmware from the official website, but I can not install it, how I go about flashing?
Lisandro4m41 said:
I downloaded the firmware from the official website, but I can not install it, how I go about flashing?
Click to expand...
Click to collapse
Where is it failing?
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Where is it failing?
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
I do not know from where to start installing, to decompress the RAR I downloaded, unzip a file I can not open. Basically, once you downloaded the firmware from the Motorola, how do I install it?
Lisandro4m41 said:
I do not know from where to start installing, to decompress the RAR I downloaded, unzip a file I can not open. Basically, once you downloaded the firmware from the Motorola, how do I install it?
Click to expand...
Click to collapse
It is a .gz file, you extract it like a ZIP/RAR file with a tool like 7-Zip.
The file from Moto is rather old, the one I linked above ( http://forum.xda-developers.com/showpost.php?p=67343754&postcount=171 ) is the current release.
You flash it like you stated earlier.
acejavelin said:
It is a .gz file, you extract it like a ZIP/RAR file with a tool like 7-Zip.
The file from Moto is rather old, the one I linked above ( http://forum.xda-developers.com/showpost.php?p=67343754&postcount=171 ) is the current release.
You flash it like you stated earlier.
Click to expand...
Click to collapse
Yes, I unzipped the .gz file. I managed to get the folder with the files, but following the commands of the Motorola, I pulled the same mistake when creating the thread. You are downloading the most current version. Still I do not understand what the error:
(Bootloader) failed validation Preflash
FAILED (remote failure)
What is the cause of that?
Lisandro4m41 said:
Yes, I unzipped the .gz file. I managed to get the folder with the files, but following the commands of the Motorola, I pulled the same mistake when creating the thread. You are downloading the most current version. Still I do not understand what the error:
(Bootloader) failed validation Preflash
FAILED (remote failure)
What is the cause of that?
Click to expand...
Click to collapse
Usually it means either the bootloader is still locked (which we know your's is unlocked) or the file is incorrect for your device. Sometimes it's a random error, try erasing the modemst1 and modemst2 first, then flash NON-HLOS.bin a time or two until it gives and OK and continue from there like normal.
I have not retested flash, but I solved my problem. The problem was that the phone was locked in Claro AR. No relation to the Bootloader error, but got what I wanted haha. Thanks for your time.
Greetings from Argentina.
So I successfully installed TWRP recovery.
I then tried to flash SuperSU, but that gave me a boot loop, so I wanted to try and flash the stock rom again.
I wiped my phone with TWRP.
I wasn't totally sure what the correct version of the ROM was to download. I can't check because the phone is already wiped. It's a UK Moto X Play "lux XT1562 16GB P2C" single sim slot. I had installed an OTA update yesterday. I downloaded XT1562_LUX_RETEU_6.0.1_MPD24.107-52.xml.zip, would that be the correct version? Is there any way to know for sure?
So when I tried to flash the stock rom I ran into problems.
I ran "fastboot flash partition gpt.bin" and I got "(bootloader) Preflash validation failed".
I saw someone say that this could be because you need to flash the correct version of the bootloader first, so I did "fastboot flash bootloader bootloader.img" which was successful, but even after restarting "fastboot flash partition gpt.bin" still failed.
I'm really confused as to what I'm doing wrong. Am I having problems because I'm trying to flash the wrong version of the bootloader, or a version older then that which I had on my phone before wiping? Is this the kind of error you'd get if you were trying to downgrade, or should that work fine?
Help greatly appreciated!
Edit: Should I possibly try flashing 5.1.1 X_Play_UK_Retail_XT1562_LPD23.118-10_CFC.xml.zip or is flashing an older version a bad idea?
Have you used this method? You have to export the zip file, its not a flashable zip and then you fastboot all the files via adb.
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
---------- Post added at 03:40 AM ---------- Previous post was at 03:39 AM ----------
Also I think that its not considered bricked when you still open fastboot. Brick means there's no way to flash anything at all wich is really hard to happen
tavares_one said:
Have you used this method? You have to export the zip file, its not a flashable zip and then you fastboot all the files via adb.
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
---------- Post added at 03:40 AM ---------- Previous post was at 03:39 AM ----------
Also I think that its not considered bricked when you still open fastboot. Brick means there's no way to flash anything at all wich is really hard to happen
Click to expand...
Click to collapse
Sorry, should have said "soft-bricked".
Looking at the guide you linked, it doesn't seem to suggest anything different from what I'm already doing. I'm following the how-to-unroot-the-motorola-moto-x-play guide on theunlockr.
It fails when I try and flash gpt.bin
Code:
❯ fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.143s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.740s
and on the bootloader logs is says
Code:
cmd: getvar:partition-type:partition
cmd: getvar:max-download-size
cmd: download 00008000
cmd: flash:partition
version downgraded for primary_gpt
johtso said:
Sorry, should have said "soft-bricked".
Looking at the guide you linked, it doesn't seem to suggest anything different from what I'm already doing. I'm following the how-to-unroot-the-motorola-moto-x-play guide on theunlockr.
Click to expand...
Click to collapse
You should try the Motorola device manager, it helped me once, when I deleted ALL and couldn't acces the phone anymore. Worked very easy, at least you get full access again va ADB.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Dio-Genes said:
You should try the Motorola device manager, it helped me once, when I deleted ALL and couldn't acces the phone anymore. Worked very easy, at least you get full access again va ADB.
Click to expand...
Click to collapse
I already have access to the phone, I have bootloader and recovery, just no firmware, but can't get flashing of the stock firmware to work.
johtso said:
I already have access to the phone, I have bootloader and recovery, just no firmware, but can't get flashing of the stock firmware to work.
Click to expand...
Click to collapse
I have read somewhere gpt.bin was not to flash under certain circumstances, don't remember exactly, but you can try without to see.
And i my case ( in france) my rom was a retasia (bought on amazon)
The normal process is below, but look your unziped files, you can have sparsechunk.7 sparsechunk.8 too
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
fablebreton said:
I have read somewhere gpt.bin was not to flash under certain circumstances, don't remember exactly, but you can try without to see.
And i my case ( in france) my rom was a retasia (bought on amazon)
The normal process is below, but look your unziped files, you can have sparsechunk.7 sparsechunk.8 too
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
...
Click to expand...
Click to collapse
Flashing boot.img doesn't work either
Code:
❯ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.032s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.770s
johtso said:
Flashing boot.img doesn't work either
Code:
❯ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.032s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.770s
Click to expand...
Click to collapse
Your bootloader is unlocked ?
fablebreton said:
Your bootloader is unlocked ?
Click to expand...
Click to collapse
Yes, I've unlocked my bootloader, and successfully flashed TWRP. Bootloader says "Device is UNLOCKED. Status Code: 3"
johtso said:
Yes, I've unlocked my bootloader, and successfully flashed TWRP. Bootloader says "Device is UNLOCKED. Status Code: 3"
Click to expand...
Click to collapse
try this command in fastboot:
Code:
fastboot getvar all
and see if it tells you anything about your current firmware and flash exactly the same one. Look for
Code:
(bootloader) ro.build.fingerprint:
line.
johtso said:
Yes, I've unlocked my bootloader, and successfully flashed TWRP. Bootloader says "Device is UNLOCKED. Status Code: 3"
Click to expand...
Click to collapse
if impossible with stock and if Twrp ok why not flash a custom rom
minimale_ldz said:
try this command in fastboot:
Code:
fastboot getvar all
and see if it tells you anything about your current firmware and flash exactly the same one. Look for
Code:
(bootloader) ro.build.fingerprint:
line.
Click to expand...
Click to collapse
Thanks for the pointer, didn't know about this command!
Bare in mind that I've already fully wiped the phone in TWRP, and I also successfully flashed the bootloader (and just the bootloader) from the 6.0.1 rom I mentioned above. Would this not affect the output?
This is what I get:
Code:
(bootloader) ro.build.fingerprint[0]: motorola/lux_reteu/lux:6.0.1/MPDS2
(bootloader) ro.build.fingerprint[1]: 4.107-52-5/5:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.5.lux_reteu.r
(bootloader) ro.build.version.full[1]: eteu.en.EU
johtso said:
Thanks for the pointer, didn't know about this command!
Bare in mind that I've already fully wiped the phone in TWRP, and I also successfully flashed the bootloader (and just the bootloader) from the 6.0.1 rom I mentioned above. Would this not affect the output?
This is what I get:
Code:
(bootloader) ro.build.fingerprint[0]: motorola/lux_reteu/lux:6.0.1/MPDS2
(bootloader) ro.build.fingerprint[1]: 4.107-52-5/5:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.5.lux_reteu.r
(bootloader) ro.build.version.full[1]: eteu.en.EU
Click to expand...
Click to collapse
Looks like you've got this one:
http://www.filefactory.com/file/qqz...S24.107-52-5_cid7_subsidy-DEFAULT_CFC.xml.zip
try it and see what it says
minimale_ldz said:
Looks like you've got this one:
http://www.filefactory.com/file/qqz...S24.107-52-5_cid7_subsidy-DEFAULT_CFC.xml.zip
try it and see what it says
Click to expand...
Click to collapse
Ah interesting! That seems to be a slightly different variant? MPDS2 instead of MPD2.. any idea what that means?
Nearly downloaded, will give it a go and see what happens!
Edit: It worked! You're an absolute life saver! So confusing that those two ROM are named so similarly..
johtso said:
Ah interesting! That seems to be a slightly different variant? MPDS2 instead of MPD2.. any idea what that means?
Nearly downloaded, will give it a go and see what happens!
Click to expand...
Click to collapse
No idea what it means, but both your getvar info and linked firmware are MPDS. Anyway - good luck.
Hello all, I need your help. I tried everything and i can't unbrick my phone. After an OTA, then reebot the system stucks in the bootloader with the "Failed to validate boot image".
I can't unlock the OEM to flash a stock rom:
Code:
fastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.010s]
finished. total time: 0.010s
Please, help me (sorry for my bad english)
Edd95 said:
Hello all, I need your help. I tried everything and i can't unbrick my phone. After an OTA, then reebot the system stucks in the bootloader with the "Failed to validate boot image".
I can't unlock the OEM to flash a stock rom:
Please, help me (sorry for my bad english)
Click to expand...
Click to collapse
Just flash stock firmware from bootloader.
Here is the firmware download link:-https://firmware.center/.zdrive/z_gdrive_viewer.php?ID=0Bw_NsGJYGFyVa1RkUC1tM3RrWVk
Link for minimal ADB:-https://androidfilehost.com/?fid=745425885120698566
---------- Post added at 07:55 AM ---------- Previous post was at 07:50 AM ----------
Step 1:*Install*Minimal adb and fastboot and extract the downloaded*rom*to the same folder where you have installed Minimal And fastboot package.
Step 2: After extracting open command prompt in that folder (where you have extracted the*rom/ the adb and fastboot folder)
Step 3: Now*boot*your*phone*into your bootloader by pressing volume down+*power*button*at the same time.
Step 4: Type the following in your command prompt: fastboot*devices
If it detects your*device*move to the next step, if it does not then you will have to*install*drivers*for your*device.
Step 5: Now Copy the following*code*and paste it to your command prompt:
mfastboot oem fb_mode_set
mfastboot*flash*logo logo.bin
mfastboot*flash*boot*boot.img
mfastboot*flash*recovery recovery.img
mfastboot*flash*dsp adspso.bin
mfastboot*flash*oem oem.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*system*system.img_sparsechunk.4
mfastboot*flash*system*system.img_sparsechunk.5
mfastboot*flash*system*system.img_sparsechunk.6
mfastboot*flash*system*system.img_sparsechunk.7
mfastboot*flash*modem*NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot*flash*fsg fsg.mbn
mfastboot erase*cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Step 6: This will completely wipe your*data*and*install*stock 7.0*on your potter*device.*
Step7:-reboot your device.
(Note:-use this codes only, to flash firmware as your device is having a latest bootloader there is a chance of hard brick, don't use other codes.)
Done.
riyan65 said:
Just flash stock firmware from bootloader.
Click to expand...
Click to collapse
Hi riyan, I tried to flash the stock firm: POTTER_RETAIL_7.0_NPNS25.137-92-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml but im getting errors like:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
FAILED (remote failure)
finished. total time: 0.180s
And nothing happens, but it appears with the fastboot devices comm.
Edd95 said:
Hi riyan, I tried to flash the stock firm: POTTER_RETAIL_7.0_NPNS25.137-92-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml but im getting errors like:
And nothing happens, but it appears with the fastboot devices comm.
Click to expand...
Click to collapse
It seems your trying to flash a old version of the stock rom try with different one with a latest stock rom and then flash bootloader with same version you have in your phone then try to flash full stock
riyan65 said:
Try to just flash bootloader with same version you have in your phone then try to flash full stock
Click to expand...
Click to collapse
How can I get the version that my phone already have? I don’t remember what it was before the OTA (and then the brick)
Ty
Edd95 said:
How can I get the version that my phone already have? I don’t remember what it was before the OTA (and then the brick)
Ty
Click to expand...
Click to collapse
When you don't know on what firmware you were nobody else can. Where do you come from?
If it's India or Brazil the 92-14 build should be safe as it is the latest available so you can't downgrade.
If you're from Europe/US etc the 93-10 build is the latest available. You find both here:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Sent from my Moto G5 Plus using XDA Labs
I get that error with minimal adb, use this system wide version, never failed me:
https://forum.xda-developers.com/showthread.php?t=2588979
Also, make sure you installed moto drivers:
https://drive.google.com/file/d/0B3byUPGqbBw_ZjdiWF8wNmkwc28/view
Wolfcity said:
When you don't know on what firmware you were nobody else can. Where do you come from?
If it's India or Brazil the 92-14 build should be safe as it is the latest available so you can't downgrade.
If you're from Europe/US etc the 93-10 build is the latest available. You find both here:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Hi again, I from Chile (LATAM) so Brazil build would work?
TY, and sorry for being a noob about this
Cupcake 1.5 said:
I get that error with minimal adb, use this system wide version, never failed me:
https://forum.xda-developers.com/showthread.php?t=2588979
Also, make sure you installed moto drivers:
https://drive.google.com/file/d/0B3byUPGqbBw_ZjdiWF8wNmkwc28/view
Click to expand...
Click to collapse
Hi Cupcake! I'll give it a try, ty for the advice, I'll post later what I get
I'm getting errors like this:
Code:
C:\adb>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.026s
but the phone it's connected and appears:
Code:
C:\adb>fastboot devices
35af6194 fastboot
Suggestions?
Edd95 said:
I'm getting errors like this:
but the phone it's connected and appears:
Suggestions?
Click to expand...
Click to collapse
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
FAILED (remote failure)
finished. total time: 0.180s
The first set of outputs (slot-count:not found and slot-suffixes:not found) is no failure.
It's just that Minimal ADB and Fastboot is checking if you've got a device with two slots like the Pixel devices with their A/B architecture. I get them too every time I use it. The failure message is supposed to be after that and is most probably the same like
Code:
C:\adb>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.026s
which is related to the bootloader as you wrote in your first post.
Have you flashed a firmware in the past that was older than the one you were running?
Than your bootloader has been downgraded and when you wanted to apply the OTA the bootloader was not the one the OTA expected.
Have you flashed some stock firmware in the past before applying the OTA?
If yes you have a real problem. In that case I would try to flash a TWRP flashable build:
https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
Sent from my Moto G5 Plus using XDA Labs
sorry to post the same old ask for help. im on PPOS29.114-16-7-2
I unlocked because I thought there would be more to do if I did. then noticed not much going on. id like to get security updates without all the trouble . ive noticed people having problems with relocking. I just would like the right way laid out for me and I will give it a shot. also when you say enter the commands in for fastboot do I copy from text editor and do it or do then one at a time. lot of commands
I appreciate all help
thanks
millede74 said:
sorry to post the same old ask for help. im on PPOS29.114-16-7-2
I unlocked because I thought there would be more to do if I did. then noticed not much going on. id like to get security updates without all the trouble . ive noticed people having problems with relocking. I just would like the right way laid out for me and I will give it a shot. also when you say enter the commands in for fastboot do I copy from text editor and do it or do then one at a time. lot of commands
I appreciate all help
thanks
Click to expand...
Click to collapse
You can script them if you know how to make one. Otherwise enter them one at a time. You only need to flash this once so if you do them once each it doesn't take a long time.
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash dtbo dtbo.img
fastboot flash logo logo.bin
fastboot flash boot boot.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 system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
then
Code:
fastboot oem lock
you may have to repeat this last lock command until it works. I had to do it 4-5 times.
I really appreciate the help. Thanks. Do I need to put boot image or 29.114-16-7-2 extract file in tools folder and do this?
millede74 said:
I really appreciate the help. Thanks. Do I need to put boot image or 29.114-16-7-2 extract file in tools folder and do this?
Click to expand...
Click to collapse
fastboot needs to be in the folder with the 29.114-16-7-2 files.
Thanks
Note that you need to run the fastboot oem lock command a few times in the beginning (before you flash) and after you flash a few more times for this to completely work!
Did like said and pretty much everything after fb_mode_set said command failed
Didn't do nothing to phone I can tell. I stopped after trying bootloader
What's wrong
millede74 said:
Did like said and pretty much everything after fb_mode_set said command failed
Didn't do nothing to phone I can tell. I stopped after trying bootloader
What's wrong
Click to expand...
Click to collapse
Do them one at a time and post the results of each command here so we can see.
Sorry won't be able to try again till tomorrow. One question. If I run lmsa what will it do if I use rescue after downloading system image?
millede74 said:
Sorry won't be able to try again till tomorrow. One question. If I run lmsa what will it do if I use rescue after downloading system image?
Click to expand...
Click to collapse
It does the same thing as the commands above. The process is just automated.
This is what i get when running
ptn107 said:
It does the same thing as the commands above. The process is just automated.
Click to expand...
Click to collapse
C:\ProgramData\LMSA\Download\RomFiles>fastboot dev
ZY225FR3QL fastboot
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem
mmand erases all user data.
(bootloader) Please re-run this command to continu
OKAY [ 0.014s]
Finished. Total time: 0.020s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem
oid images now
(bootloader) Then re-run this command to lock
OKAY [ 0.018s]
Finished. Total time: 0.024s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.009s]
Finished. Total time: 0.014s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.009s]
Finished. Total time: 0.015s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.008s]
Finished. Total time: 0.015s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.010s]
Finished. Total time: 0.016s
C:\ProgramData\LMSA\Download\RomFiles>fastboot getvar max-sparse-size
max-sparse-size: 268435456
Finished. Total time: 0.006s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem fb_mode_set
OKAY [ 0.005s]
Finished. Total time: 0.011s
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash partition gpt.bin
fastboot: error: cannot load 'gpt.bin': No such file or directory
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash bootloader bootloader.img
fastboot: error: cannot load 'bootloader.img': No such file or directory
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash modem NON-HLOS.bin
fastboot: error: Failed to identify current slot
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash fsg fsg.mbn
fastboot: error: Failed to identify current slot
C:\ProgramData\LMSA\Download\RomFiles>
Correct me if I'm wrong but doesn't lmsa download the firmware as a zip file in C:\ProgramData\LMSA\Download\RomFiles ? If that's the case you need to make sure the files are extracted before running commands.
Moto G5 Plus unaltered went into boot loop, result; imei 0, "failed to validate",
Hi all,
I stumbled on this forum while trying to figure out a way to rescue my husband's Moto G5 Plus. Yesterday it went into a constant loop of restarts, at best functioning for 5 minutes before suddenly restarting for seemingly no reason.
He is not technically proficient enough to do any error seeking, let alone booting or flashing a new rom, so for all intents and purposes the phone is unaltered except doing the standard android updates, adding common apps and so on.
Well, the phone eventually ended up in fastboot flash mode where it keeps giving the error: faild to pass validaton, backup to fastboot. I found the menu option for barcodes and both imei and SKU are set to 000000000000 or how every many 0's. Date is set to 01-01-1970, but serial number is intact.
We tried installing Software Repair Assistant, but it keeps going on "Processing device information" for hours with no result.
Also tried installing the Lenovo Moto Smart Assistant for the Rescue mode, but it gives me "Failed to match the connected device".
Ideally we would like to find a way to bring back the contents of the phone if at all possible. I found a thread regarding imei 0 issue but I couldn't see if that would also wipe all contents so I am hesitant to try that without further research.
Being a slightly paranoid lawyer, my husband doesn't believe in backing up his stuff to cloud based solutions, so all his photos of the kids (and more) are per now toast. He has a new phone (and a slightly more modern approach to cloud backups) so there is no rush to fix NOW, but we'd like to know if there's any point in trying to restore or if we should go ahead with hacks to render it wiped but usable.
Does anyone here know of a good way to resolve this issue?
MrsMotz said:
Hi all,
I stumbled on this forum while trying to figure out a way to rescue my husband's Moto G5 Plus. Yesterday it went into a constant loop of restarts, at best functioning for 5 minutes before suddenly restarting for seemingly no reason.
He is not technically proficient enough to do any error seeking, let alone booting or flashing a new rom, so for all intents and purposes the phone is unaltered except doing the standard android updates, adding common apps and so on.
Well, the phone eventually ended up in fastboot flash mode where it keeps giving the error: faild to pass validaton, backup to fastboot. I found the menu option for barcodes and both imei and SKU are set to 000000000000 or how every many 0's. Date is set to 01-01-1970, but serial number is intact.
We tried installing Software Repair Assistant, but it keeps going on "Processing device information" for hours with no result.
Also tried installing the Lenovo Moto Smart Assistant for the Rescue mode, but it gives me "Failed to match the connected device".
Ideally we would like to find a way to bring back the contents of the phone if at all possible. I found a thread regarding imei 0 issue but I couldn't see if that would also wipe all contents so I am hesitant to try that without further research.
Being a slightly paranoid lawyer, my husband doesn't believe in backing up his stuff to cloud based solutions, so all his photos of the kids (and more) are per now toast. He has a new phone (and a slightly more modern approach to cloud backups) so there is no rush to fix NOW, but we'd like to know if there's any point in trying to restore or if we should go ahead with hacks to render it wiped but usable.
Does anyone here know of a good way to resolve this issue?
Click to expand...
Click to collapse
Is your device is rooted??? Or it on completely on stock ROM???
And what the last thing you do which cause this problem.
riyan65 said:
Is your device is rooted??? Or it on completely on stock ROM???
And what the last thing you do which cause this problem.
Click to expand...
Click to collapse
It's not rooted, completely stock except following the recommended updates.
As far as I know, he did not do anything except charging the phone at night, and in the morning it had restarted, then kept restarting all day until ending in fastboot with "failed validaton".
MrsMotz said:
It's not rooted, completely stock except following the recommended updates.
As far as I know, he did not do anything except charging the phone at night, and in the morning it had restarted, then kept restarting all day until ending in fastboot with "failed validaton".
Click to expand...
Click to collapse
Then it quite hard to recover data, but not least. You can try flashing the device from this procedure.
Here is the procedure:-
Step 1: Download your potter rom from the following link: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
"POTTER_RETAIL_8.1.0_OPSS28.85-17-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" download the following zip.
Step 2: Download Minimal adb and fastboot from the following link: https://androidfilehost.com/?fid=745425885120698566
Step 3: Install Minimal adb and fastboot and extract the downloaded rom to the same folder where you have installed Minimal And fastboot package.
Step 4: After extracting open command prompt in that folder (where you have extracted the rom/ the adb and fastboot folder)
Step 5: Now boot your phone into your bootloader by pressing volume down+ power button at the same time.
Step 6: Type the following in your command prompt: fastboot devices
If it detects your device move to the next step, if it does not then you will have to install drivers for your device.
Step 7: Now Copy the following code and paste it to your command prompt:
fastboot oem fb_mode_set
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 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 clogo
fastboot oem fb_mode_clear
fastboot reboot
Now your device will boot, if not try holding power button for 10sec then it reboot it self. If it won't boot then flash the device again with the following command
[Note:- this will erase all user data]
fastboot oem fb_mode_set
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 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
This will boot you device for sure.
riyan65 said:
Then it quite hard to recover data, but not least. You can try flashing the device from this procedure.
...
Step 6: Type the following in your command prompt: fastboot devices
If it detects your device move to the next step, if it does not then you will have to install drivers for your device.
Step 7: Now Copy the following code and paste it to your command prompt:
fastboot oem fb_mode_set
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 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 clogo
fastboot oem fb_mode_clear
fastboot reboot
Now your device will boot, if not try holding power button for 10sec then it reboot it self. If it won't boot then flash the device again with the following command
[Note:- this will erase all user data]
fastboot oem fb_mode_set
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 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
This will boot you device for sure.
Click to expand...
Click to collapse
OK, I tried the first bunch of commands. This is the result I got:
C:\ADB>fastboot devices
6be2e0bf fastboot
C:\ADB>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.013s
C:\ADB>
C:\ADB>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.084s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.107s
C:\ADB>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.603s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.807s
C:\ADB>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.738s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.981s
C:\ADB>fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.584s]
writing 'dsp'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition dsp
FAILED (remote failure)
finished. total time: 0.606s
C:\ADB>fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (104608 KB)...
OKAY [ 3.643s]
writing 'oem'...
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.714s
C:\ADB>fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (258396 KB)...
OKAY [ 8.946s]
writing 'system'...
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.017s
C:\ADB>fastboot flash system system.img_sparsechunk.1
target reported max download size of 534773760 bytes
sending 'system' (256514 KB)...
OKAY [ 8.872s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.896s
C:\ADB>fastboot flash system system.img_sparsechunk.2
target reported max download size of 534773760 bytes
sending 'system' (246302 KB)...
OKAY [ 8.489s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.530s
C:\ADB>fastboot flash system system.img_sparsechunk.3
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 9.057s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.149s
C:\ADB>fastboot flash system system.img_sparsechunk.4
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 9.063s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.092s
C:\ADB>fastboot flash system system.img_sparsechunk.5
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 9.070s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.096s
C:\ADB>fastboot flash system system.img_sparsechunk.6
target reported max download size of 534773760 bytes
sending 'system' (250531 KB)...
OKAY [ 8.684s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.725s
C:\ADB>fastboot flash system system.img_sparsechunk.7
target reported max download size of 534773760 bytes
sending 'system' (262059 KB)...
OKAY [ 9.034s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.073s
C:\ADB>fastboot flash system system.img_sparsechunk.8
target reported max download size of 534773760 bytes
sending 'system' (254142 KB)...
OKAY [ 8.763s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.796s
C:\ADB>fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (71921 KB)...
OKAY [ 2.495s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 2.522s
C:\ADB>fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.019s
C:\ADB>fastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.034s
C:\ADB>fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (3012 KB)...
OKAY [ 0.126s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.146s
C:\ADB>fastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.034s
C:\ADB>
C:\ADB>fastboot erase clogo
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.018s
C:\ADB>fastboot oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.021s
C:\ADB>fastboot reboot
MrsMotz said:
OK, I tried the first bunch of commands.
Click to expand...
Click to collapse
Chances are the gpt got corrupted as well..
Try
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 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
Everything will be wiped. Also make sure you downloaded the latest firmware. 17-6-2 is the latest.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Same issue, same results!
My Moto G5 Plus XT1687 experienced the same type of failure just over a month ago. First, it began randomly rebooting (never a good sign...), then my entire sms history disappeared (every sms AFTER that moment, however, behaved normally: received and listed/logged as new messages)... Then, about two days later, I woke up to a bricked phone. My phone was never rooted. Around the time of the random reboots, I had allowed my phone to update apps (I can't remember which happened first -- random reboots or app updates. I do know that I chose to update apps at that time because the phone was laggy and not behaving [even though there was ample unused storage available, and no apps stood out as memory hogs, etc.]). (Developer mode was enabled, but probably not USB debugging.)
On the barcode screen, my phone displays an IMEI of all zeros, a SKU of all zeros, and a date of 01-01-1970 (there is a serial number that may or may not be the original. It does not appear anywhere on the box label [where my actual IMEI and other numbers/codes are printed]).
I have tried flashing POTTER_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info (as well as a few older ones -- just to try) using variations* of the standard code, above (*with and without "flash partition gpt.bin" and "flash bootloader bootloader.img"...). I have not yet taken the leap of including "erase userdata", however, because I am worried about losing anything that might not have been backed up... (And if every single previous line of code has failed, will adding "erase userdata" toward the end make a difference...?)
Down the list, the results are identical to the ones posted here by MrsMotz: "FAILED (remote failure)", "failed to erase", "failed to validate", "failed to flash", "invalid signed image", etc. (I've also tried using the Lenovo Moto Smart Assistant Flash/Rescue tool [which I imagine is supposed to perform essentially the same function as flashing ROM manually] to no avail ["Failed to match connected device"]!)
I can't afford a new phone! I desperately need to make this one work again. What am I missing? Why did my phone self-brick, and how can I fix it?
Same issue, same results! Update
On the barcode screen, my phone displays an IMEI of all zeros, a SKU of all zeros, and a date of 01-01-1970 (there is a serial number that may or may not be the original. It does not appear anywhere on the box label [where my actual IMEI and other numbers/codes are printed]).
Click to expand...
Click to collapse
So, the "serial number" currently showing on my phone is not the real/actual/original serial number. My real serial number went the way of my real IMEA, I guess! Is this normal when a phone is bricked? Also, might the loss of my phone's genuine identifiers be contributing to the inability be "validated" or "recognized"...?
mahuba3 said:
So, the "serial number" currently showing on my phone is not the real/actual/original serial number. My real serial number went the way of my real IMEA, I guess! Is this normal when a phone is bricked? Also, might the loss of my phone's genuine identifiers be contributing to the inability be "validated" or "recognized"...?
Click to expand...
Click to collapse
Seems to be a hardware issue. No IMEI, no serial, date reset to 1970...
Also the random reboots and the other things happening before are pointing to that direction.
So you're still able to reach fastboot mode and flash stock firmwares. When you say you were never rooted I suspect your bootloader is still locked?
If so I'm out of ideas, there isn't much you can do with an bootloader locked device.
I'm pretty sure that your hardware is the problem, so service center (depending on the country you live in) or buying a new device seem to be the only ways to go.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
Seems to be a hardware issue. No IMEI, no serial, date reset to 1970...
Also the random reboots and the other things happening before are pointing to that direction.
So you're still able to reach fastboot mode and flash stock firmwares. When you say you were never rooted I suspect your bootloader is still locked?
If so I'm out of ideas, there isn't much you can do with an bootloader locked device.
I'm pretty sure that your hardware is the problem, so service center (depending on the country you live in) or buying a new device seem to be the only ways to go.
Click to expand...
Click to collapse
Thank you ... But darn
Bootloader is locked (screen says "oem_locked"). But, yes, I am able to reach fastboot mode. And the bootloader logs come through each time I attempt to flash anything...
PS My phone, purchased new, is only two and a half years old (I usually hold onto them much longer!). But... I did drop it into the pool at the YMCA several months ago... It had been "misbehaving" (background apps crashing) prior, but after four days in rice and silica packets, it came out working just as well as before...
@mahuba3: Any luck bro? I am also having the same issue, if you have fixed your phone, share me the details please.
mahuba3 said:
Thank you ... But darn
Bootloader is locked (screen says "oem_locked"). But, yes, I am able to reach fastboot mode. And the bootloader logs come through each time I attempt to flash anything...
PS My phone, purchased new, is only two and a half years old (I usually hold onto them much longer!). But... I did drop it into the pool at the YMCA several months ago... It had been "misbehaving" (background apps crashing) prior, but after four days in rice and silica packets, it came out working just as well as before...
Click to expand...
Click to collapse
Moto g5 plus
Any solution
I have the same problem
I'm having a very similar issue, but I can't login to bootloader screen. It just starts on a screen saying "start up failed" and when I try to run the commands you say it responds with an error
> fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.016s
> fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.016s
SAme problem here too, Just two days ago, woke up to this bricked phone.
hello there im facing the same issue i would like to recover my files from the phone. i dont care if i could use the phone further pls reply.
same problem here! i'm on a linux pc
Help needed! (newbie here)
I have a moto g5 plus (potter) and it is locked on this screen. I already tried to use the motorola recovery program but he doesn't recognize it because imei appears 0000000. I need help to bring it back to life (my computer is linux) and if possible to install the factory rom on it.
{
"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"
}
Facing the same issue, can anyone help?