So I've been encountering this problem whenever I'm trying to do anything to the Modem Partitions on the Essential Phone:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
PM1LHMA7C1303309 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
FAILED (remote: Flashing is not allowed for Modem Partitions
)
finished. total time: 0.032s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modemst1 modemst1.img
target reported max download size of 536870912 bytes
sending 'modemst1' (2048 KB)...
OKAY [ 0.765s]
writing 'modemst1'...
FAILED (remote: Flashing is not allowed for Modem Partitions
)
finished. total time: 0.794s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
FAILED (remote: Flashing is not allowed for Modem Partitions
)
finished. total time: 0.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modemst2 modemst2.img
target reported max download size of 536870912 bytes
sending 'modemst2' (2048 KB)...
OKAY [ 0.168s]
writing 'modemst2'...
FAILED (remote: Flashing is not allowed for Modem Partitions
)
finished. total time: 0.240s
And... flashing the img file using
Code:
fastboot flash modem_a or modem_b
didn't provide the result I wanted.
If anyone have some inputs would be really appreciated. Thanks...
Did you unlock critical? I don't remember the exact commands but it's similar to unlocking the bootloader.
gk1984 said:
Did you unlock critical? I don't remember the exact commands but it's similar to unlocking the bootloader.
Click to expand...
Click to collapse
I did. I've done both
Code:
fastboot flashing unlock
and
Code:
fastboot flashing unlock_critical
I'll be trying to flash older essential fastboot.img(s) to see wether that would change anything. Because from the r/essential on reddit, people actually were able to flash onto the modemst partitions.
reddit*com/r/essential/comments/9e9to8/invalid_sim_network_locked_fix_for_the_september/
I was doing the automatic steps, but the phone literally doesn't respond to .bat file provided. So I tried doing it manually, and it was when I hit this partition problem.
If it's not asking to much, would someone confirm wether or not flashing onto this partition is possible? Thanks
You must unlock and downgrade bootloader (old android 7 rom) on last android 7 and 8,9 roms you cannot flash modemst part bcs security patches
flash NMK24B factory image first and after unlock_critical you can flash modemst parts
download rom from here https://www.essential.com/developer/current-builds
and after flash modemst parts you can flash android 8.1 rom and check if is it unlocked bcs after flash modemst parts phone stay in locked state on android 7
veisen said:
You must unlock and downgrade bootloader (old android 7 rom) on last android 7 and 8,9 roms you cannot flash modemst part bcs security patches
flash NMK24B factory image first and after unlock_critical you can flash modemst parts
download rom from here essential*com/developer/current-builds
and after flash modemst parts you can flash android 8.1 rom and check if is it unlocked bcs after flash modemst parts phone stay in locked state on android 7
Click to expand...
Click to collapse
So I've been trying to flash the NMK24B, I hadn't been successful these previous days, but I found a trick from this youtube video;
youtube*com/watch?v=RrMLqSXcxjI
So I'll proceed to flash the modemst partitions, and give you guys update.
Phone is Sim Unocked Now
So this is the manual process to do all this, if your phone isn't responding to the automatic procedure according to https://www*reddit*com/r/essential/comments/9e9to8/invalid_sim_network_locked_fix_for_the_september/.
Flash NMK24B on fastboot by running flashall.bat. If it's not sending package to the phone, then install Minimal ADB and copy fastboot.exe from Minimal ADB directory to NMK24B directory, the run the flashall.bat.
After the above procedure you will boot into adroid, re-enable usb debugging, then go to fastboot again. Open cmd from Minimal ADB and flash modemst, which you can find from reddit post above on Essential Unlock>Data>Modemst:
Code:
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
Resources are from the reddit post above. Credits goes to the creator of this trick (in which I do not know who).
Need your help. I just accidently selected radioband USA settings on my htc one m8. Now the network is completely gone. I saw on the internet to erase my modemst1 and modemst2 using fastboot. But it says that "failed (remote:not allowed). What does this mean? And how it'll allow me?
---------- Post added at 09:49 AM ---------- Previous post was at 09:45 AM ----------
Khan97bilal said:
Need your help. I just accidently selected radioband USA settings on my htc one m8. Now the network is completely gone. I saw on the internet to erase my modemst1 and modemst2 using fastboot. But it says that "failed (remote:not allowed). What does this mean? And how it'll allow me?
Click to expand...
Click to collapse
I also have s off. Bootloader unlocked. And device rooted.
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?
Hello experts, i'm diving directly into main problem. My phone directly powered off when i using phone. when i try to open, stuck on android one logo.
i tried to flash new rom via MiFlash. But its giving strange errors.
Also i tried to format data via twrp, but it stucks after i swipe. i tried also wipe system,dalvik, cache, but same thing happened. stucking after i swipe.
I think phone bricked.
Today i tried to flash all img files via fastboot like this;
Code:
fastboot erase boot_a
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash sbl1 sbl1.img
fastboot flash sbl1bak sbl1.img
fastboot flash rpm rpm.img
fastboot flash rpmbak rpm.img
fastboot flash tz tz.img
fastboot flash tzbak tz.img
fastboot flash devcfg devcfg.img
fastboot flash devcfgbak devcfg.img
fastboot flash dsp dsp.img
fastboot flash sec sec.dat
fastboot flash splash splash.img
fastboot flash misc misc.img
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system_other.img
fastboot flash lksecapp lksecapp.img
fastboot flash lksecappbak lksecapp.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlibbak cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cmnlib64bak cmnlib64.img
fastboot flash keymaster keymaster.img
fastboot flash keymasterbak keymaster.img
fastboot flash userdata userdata.img
fastboot set_active a
fastboot reboot
I moved my tissot images to adb folder and started.
But after i tried whole codes in powershell with copy paste, giving "(command write failed (Invalid argument))" error in 2nd img file. Thats really interesting. first img file transfered succesfully but 2nd one is giving error.
And i decided to flash step by step, aand BUM. i dont getting any error while flashing step by step. But if i try to flash for example 2 img file, its giving error.
I moved forward like this until system.img file give me error again.
Code:
fastboot flash system_a system.img
target reported max download size of 534773760 bytes
erasing 'system_a'...
OKAY [ 0.096s]
sending sparse 'system_a' 1/5 (522236 KB)...
OKAY [ 11.986s]
writing 'system_a' 1/5...
OKAY [ 3.926s]
sending sparse 'system_a' 2/5 (521866 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 16.308s
I flashed all img files except system.img and system_other.img. only this 2 files giving error.
And i realized that 2 file sizes are big and fastboot trying to parse files while flashing. 1st parsed file transfering succesfully but after it goes to 2nd parsed file its giving "(command write failed (Invalid argument))" error. My fastboot has some strange problem about 2nd flash code lines. I dont know why.
What can i do to flash this 2 system img file via fastboot?
my problem solved after i break apart my phone. no need help now.