Hi guys.
After installing the xt1625 ROM stock without ADS from amazon, which did not work.
Currently my phone does not turn on the display, the lower led flashes, I connected to the PC installing the ROM stock applying the changes. The proble is that it does not start.
https://forum.xda-developers.com/moto-g4/development/unbrick-hard-bricked-moto-g4-amazon-t3486578
These are the results of the ADB.
C:\adb>astboot oem fb_mode_set
"astboot" no se reconoce como un comando interno o e
programa o archivo por lotes ejecutable.
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.024s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.157s]
finished. total time: 0.200s
C:\adb>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.134s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) will pass: flash:aboot
(bootloader) will pass: flash:rpm
(bootloader) will pass: flash:tz
(bootloader) will pass: flash:hyp
(bootloader) will pass: flash:cmnlib
(bootloader) will pass: flash:keymaster
(bootloader) will pass: flash:sbl1
(bootloader) committing: bootloader.default.xml ...
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboo
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'keymaster.mbn' to 'keymaste
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.498s]
finished. total time: 0.654s
C:\adb>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (1848 KB)...
OKAY [ 0.073s]
writing 'logo'...
OKAY [ 0.064s]
finished. total time: 0.156s
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.551s]
writing 'boot'...
OKAY [ 0.390s]
finished. total time: 0.961s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.550s]
writing 'recovery'...
OKAY [ 0.400s]
finished. total time: 0.968s
C:\adb>fastboot flash dsp adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.540s]
writing 'dsp'...
OKAY [ 0.260s]
finished. total time: 0.817s
C:\adb>fastboot flash oem oem.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'oem' (253893 KB)...
OKAY [ 8.100s]
writing 'oem'...
OKAY [ 5.914s]
finished. total time: 14.031s
C:\adb>fastboot flash oem oem.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'oem' (227328 KB)...
OKAY [ 7.326s]
writing 'oem'...
OKAY [ 6.452s]
finished. total time: 13.794s
C:\adb>fastboot flash system system.img_sparsechunk.
target reported max download size of 536870912 bytes
sending 'system' (261790 KB)...
OKAY [ 8.401s]
writing 'system'...
OKAY [ 6.246s]
finished. total time: 14.666s
C:\adb>fastboot flash system system.img_sparsechunk.
target reported max download size of 536870912 bytes
sending 'system' (252965 KB)...
OKAY [ 8.100s]
writing 'system'...
OKAY [ 5.481s]
finished. total time: 13.596s
C:\adb>fastboot flash system system.img_sparsechunk.
target reported max download size of 536870912 bytes
sending 'system' (255295 KB)...
OKAY [ 8.165s]
writing 'system'...
OKAY [ 5.619s]
finished. total time: 13.797s
C:\adb>fastboot flash system system.img_sparsechunk.
target reported max download size of 536870912 bytes
sending 'system' (256631 KB)...
OKAY [ 8.200s]
writing 'system'...
OKAY [ 5.639s]
finished. total time: 13.854s
C:\adb>fastboot flash system system.img_sparsechunk.
target reported max download size of 536870912 bytes
sending 'system' (256412 KB)...
OKAY [ 8.160s]
writing 'system'...
OKAY [ 5.516s]
finished. total time: 13.691s
C:\adb>fastboot flash system system.img_sparsechunk.
target reported max download size of 536870912 bytes
sending 'system' (256741 KB)...
OKAY [ 8.174s]
writing 'system'...
OKAY [ 5.704s]
finished. total time: 13.893s
C:\adb>fastboot flash system system.img_sparsechunk.
target reported max download size of 536870912 bytes
sending 'system' (256027 KB)...
OKAY [ 8.216s]
writing 'system'...
OKAY [ 5.772s]
finished. total time: 14.001s
C:\adb>fastboot flash system system.img_sparsechunk.
target reported max download size of 536870912 bytes
sending 'system' (223276 KB)...
OKAY [ 7.164s]
writing 'system'...
OKAY [ 9.936s]
finished. total time: 17.118s
C:\adb>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (76861 KB)...
OKAY [ 2.484s]
writing 'modem'...
OKAY [ 1.131s]
finished. total time: 3.629s
C:\adb>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.037s]
finished. total time: 0.046s
C:\adb>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.041s]
finished. total time: 0.052s
C:\adb>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (1904 KB)...
OKAY [ 0.073s]
writing 'fsg'...
OKAY [ 0.069s]
finished. total time: 0.156s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.024s]
finished. total time: 0.032s
C:\adb>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.095s]
finished. total time: 0.102s
C:\adb>fastboot erase customize
erasing 'customize'...
OKAY [ 0.021s]
finished. total time: 0.030s
C:\adb>fastboot erase clogo
erasing 'clogo'...
OKAY [ 0.026s]
finished. total time: 0.033s
C:\adb>fastboot erase DDR
erasing 'DDR'...
OKAY [ 0.014s]
finished. total time: 0.021s
C:\adb>fastboot oem fb_mode_clear
...
OKAY [ 0.009s]
finished. total time: 0.017s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.018s
Thanks for your time, I thank you in advance
Related
[IOON] OPT RESET & Recovery Tool
Hi everyone,
I have created a Recovery Tool for the OPT. IOON is a OPEN SOURCE Project this mean that everyone can share ideas and develop. However if you have ideas please share.
IOON should be the (NON OFFICAL) OFFICAL Recovery Tool. It fix software bricks, wifi issues, fingerprint, imeu, simcard & bluetooth. And new features will follow.
Please note I’m a human if I do something wrong please tell me
I want that IOON should be a community Project developed for the Community by the Community
Note:
For Windows and Linux
IOON recover the partitions over fastboot
Fastboot is required !
Warning
You do this on your one risk. I’m not responsible for any damage. I’m also not responsible:
If your alarm clock is not working and you gets fired.
If you phone will get overheat
If the phone don’t turn on.
Features
1) Erase everything
2) Back to stock
2.1) Oxygen 2.1
2.2) Oxgen 3.0
3) [Auto] custom Recovery
4) Auto root
IOON erase:
Cache
Userdata & Userdata_64
System
Modem
Modemst1
Modemst2
And More
Instructions:
1) Download and install fastboot
2) Download the ZIP file
3) Extract the ZIP file
$ sudo unzip restore.zip
4) Move in the folder
$ cd restore
5) Type:
sudo chmod +x restore.sh
sudo ./restore
[now a Menu should pop up]
Select Erase
Select back to stock
Select custom recovery (please select costum recovery if something goes wrong you have access to your phone & and file storage )
Download the newest oxygen version
Reboot into recovery [Press volume button down and power button at the same time]
Connect your phone with PC
Drag and Drop the oxygen version on your phone
Go to flash
Select oxygen version and click on flash
Click on change recovery
Reboot
Done!
Solves:
Fingerprint BUG ( 50 % changes ) [If it is a software Brick]
Fix IMEU BUG
Wifi and simcard and bluetooth should now work
Fix crashes after flashing a android 6 ROM
Bugs:
Downloads
Version 1.0 Deleted
Version 1.1 :Mod Edit link removed.
Version 1.2 Uploaded soon!
Source Code
https://github.com/deltaxflux/IOON
I now my English is bad :angel:
Wrong Link....
Updated !
Or try this one http://www.mediafire.com/download/1jf67jsvlm1thr5/restore.zip
Yes it's work ! Thanks
@deltaxflux Instructions are more from linux POV.. need commands for windows..
@s_vohra I will add the Instruction soon, let me work on the windows version
Hello,
@deltaxflux
I would like to erase all partitions and recreate them from scratch.
Is it possible with this tool?
If so, how?
jukyO said:
Hello,
@deltaxflux
I would like to erase all partitions and recreate them from scratch.
Is it possible with this tool?
If so, how?
Click to expand...
Click to collapse
@deltaFlux,
used erase option.
Now my Internal storage is 9 Gb only. Solution?
jukyO said:
@deltaFlux,
used erase option.
Now my Internal storage is 9 Gb only. Solution?
Click to expand...
Click to collapse
What did u do ?
Notice: IOON will not longer developt because I'm to busy at the moement and there better reset tools out there
deltaxflux said:
What did u do ?
Notice: IOON will not longer developt because I'm to busy at the moement and there better reset tools out there
Click to expand...
Click to collapse
used Erase option.
recovered all partitions except EFS (modemst1, modemst2) - mmcblkop17 and mmcblk0p18.
I have backed up EFS through TWRP recovery, but it does not contain modemst1 and modemst2, but 'oem_stanvbk', which is mmcblk0p20.
Do you have an idea? Can I recreate mmcblkop17 and mmcblk0p18 again?
How does restore of EFS works?
So u have root? Try the back to stock option -) root -) custom recovery modemst1 and modemst2 will be restored After reboot into recovery. Go to wipe -> advanced wipe -> select the partitions -> select recovery / repaire
to this twice !
After flash the oxygen 2.21 ROM. It should work if not contact me
deltaxflux said:
So u have root? Try the back to stock option -) root -) custom recovery modemst1 and modemst2 will be restored After reboot into recovery. Go to wipe -> advanced wipe -> select the partitions -> select recovery / repaire
to this twice !
After flash the oxygen 2.21 ROM. It should work if not contact me
Click to expand...
Click to collapse
Link to OOS 2.2.1? Some special version or any?
Sent from my A0001 using XDA-Developers mobile app
deltaxflux said:
So u have root? Try the back to stock option -) root -) custom recovery modemst1 and modemst2 will be restored After reboot into recovery. Go to wipe -> advanced wipe -> select the partitions -> select recovery / repaire
to this twice !
After flash the oxygen 2.21 ROM. It should work if not contact me
Click to expand...
Click to collapse
Did that.
Output of tool:
#########################################################
# #
# OPT [RECOVERY] 1.1 < Fluxion Is The Future > #
# by Deltax #
# #
#########################################################
Select your option
1) Back to stock
2) Root
3) Erase all
4) Custom recovery
5) Reboot
6) Exit
#> 1
#########################################################
# #
# OPT [RECOVERY] 1.1 < Fluxion Is The Future > #
# by Deltax #
# #
#########################################################
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.048s]
finished. total time: 0.048s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.490s]
finished. total time: 0.490s
erasing 'recovery'...
OKAY [ 0.028s]
finished. total time: 0.028s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 1.477s]
finished. total time: 1.477s
erasing 'userdata_64'...
FAILED (remote: Partition table doesn't exist
)
finished. total time: 0.020s
erasing 'modem'...
OKAY [ 0.038s]
finished. total time: 0.038s
erasing 'modemst1'...
OKAY [ 0.032s]
finished. total time: 0.032s
erasing 'modemst2'...
OKAY [ 0.031s]
finished. total time: 0.031s
erasing 'recovery'...
OKAY [ 0.024s]
finished. total time: 0.024s
#########################################################
# #
# OPT [RECOVERY] 1.1 < Fluxion Is The Future > #
# by Deltax #
# #
#########################################################
target reported max download size of 536870912 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.057s]
writing 'aboot'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.057s]
writing 'aboot'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
sending 'apdp' (256 KB)...
OKAY [ 0.039s]
writing 'apdp'...
OKAY [ 0.024s]
finished. total time: 0.063s
target reported max download size of 536870912 bytes
sending 'bluetooth' (1024 KB)...
OKAY [ 0.057s]
writing 'bluetooth'...
OKAY [ 0.031s]
finished. total time: 0.087s
target reported max download size of 536870912 bytes
sending 'boot' (21165 KB)...
OKAY [ 0.531s]
writing 'boot'...
OKAY [ 0.179s]
finished. total time: 0.710s
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.022s]
sending 'cache' (6248 KB)...
OKAY [ 0.186s]
writing 'cache'...
OKAY [ 0.072s]
finished. total time: 0.280s
target reported max download size of 536870912 bytes
sending 'config' (512 KB)...
OKAY [ 0.048s]
writing 'config'...
OKAY [ 0.026s]
finished. total time: 0.074s
target reported max download size of 536870912 bytes
sending 'ddr' (1024 KB)...
OKAY [ 0.057s]
writing 'ddr'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.077s
target reported max download size of 536870912 bytes
sending 'devinfo' (1 KB)...
OKAY [ 0.040s]
writing 'devinfo'...
OKAY [ 0.020s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'dpo' (1 KB)...
OKAY [ 0.040s]
writing 'dpo'...
OKAY [ 0.020s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'driver' (32768 KB)...
OKAY [ 0.800s]
writing 'driver'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.816s
target reported max download size of 536870912 bytes
sending 'fsc' (1 KB)...
OKAY [ 0.040s]
writing 'fsc'...
OKAY [ 0.020s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'fsg' (1536 KB)...
OKAY [ 0.066s]
writing 'fsg'...
OKAY [ 0.034s]
finished. total time: 0.100s
target reported max download size of 536870912 bytes
sending 'hyp' (512 KB)...
OKAY [ 0.048s]
writing 'hyp'...
OKAY [ 0.028s]
finished. total time: 0.076s
target reported max download size of 536870912 bytes
sending 'hyp' (512 KB)...
OKAY [ 0.048s]
writing 'hyp'...
OKAY [ 0.027s]
finished. total time: 0.076s
target reported max download size of 536870912 bytes
sending 'keystore' (512 KB)...
OKAY [ 0.048s]
writing 'keystore'...
FAILED (remote: image is not a keystore file)
finished. total time: 0.072s
target reported max download size of 536870912 bytes
sending 'limits' (1 KB)...
OKAY [ 0.040s]
writing 'limits'...
OKAY [ 0.020s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'LOGO' (16384 KB)...
OKAY [ 0.409s]
writing 'LOGO'...
OKAY [ 0.144s]
finished. total time: 0.553s
target reported max download size of 536870912 bytes
sending 'misc' (1024 KB)...
OKAY [ 0.057s]
writing 'misc'...
OKAY [ 0.030s]
finished. total time: 0.087s
target reported max download size of 536870912 bytes
sending 'modem' (81920 KB)...
OKAY [ 1.983s]
writing 'modem'...
OKAY [ 0.626s]
finished. total time: 2.609s
target reported max download size of 536870912 bytes
sending 'msadp' (256 KB)...
OKAY [ 0.049s]
writing 'msadp'...
OKAY [ 0.026s]
finished. total time: 0.075s
target reported max download size of 536870912 bytes
sending 'oem_dycnvbk' (10240 KB)...
OKAY [ 0.268s]
writing 'oem_dycnvbk'...
OKAY [ 0.096s]
finished. total time: 0.364s
target reported max download size of 536870912 bytes
sending 'oem_stanvbk' (10240 KB)...
OKAY [ 0.269s]
writing 'oem_stanvbk'...
OKAY [ 0.098s]
finished. total time: 0.368s
target reported max download size of 536870912 bytes
sending 'param' (1024 KB)...
OKAY [ 0.057s]
writing 'param'...
OKAY [ 0.035s]
finished. total time: 0.092s
target reported max download size of 536870912 bytes
sending 'persist' (32768 KB)...
OKAY [ 0.800s]
writing 'persist'...
OKAY [ 0.261s]
finished. total time: 1.061s
target reported max download size of 536870912 bytes
sending 'pmic' (128 KB)...
OKAY [ 0.039s]
writing 'pmic'...
OKAY [ 0.021s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'pmic' (128 KB)...
OKAY [ 0.039s]
writing 'pmic'...
OKAY [ 0.021s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'reserve1' (8096 KB)...
OKAY [ 0.214s]
writing 'reserve1'...
OKAY [ 0.097s]
finished. total time: 0.311s
target reported max download size of 536870912 bytes
sending 'reserve2' (16192 KB)...
OKAY [ 0.410s]
writing 'reserve2'...
OKAY [ 0.138s]
finished. total time: 0.547s
target reported max download size of 536870912 bytes
sending 'rpm' (500 KB)...
OKAY [ 0.048s]
writing 'rpm'...
OKAY [ 0.027s]
finished. total time: 0.075s
target reported max download size of 536870912 bytes
sending 'recovery' (28144 KB)...
OKAY [ 0.688s]
writing 'recovery'...
OKAY [ 0.232s]
finished. total time: 0.921s
target reported max download size of 536870912 bytes
sending 'sbl1' (1024 KB)...
OKAY [ 0.057s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
sending 'sbl1' (1024 KB)...
OKAY [ 0.057s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
error: cannot load 'sdi.img': No such file or directory
target reported max download size of 536870912 bytes
sending 'sec' (128 KB)...
OKAY [ 0.039s]
writing 'sec'...
OKAY [ 0.023s]
finished. total time: 0.062s
target reported max download size of 536870912 bytes
sending 'ssd' (8 KB)...
OKAY [ 0.040s]
writing 'ssd'...
OKAY [ 0.021s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'tz' (1024 KB)...
OKAY [ 0.057s]
writing 'tz'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
sending 'tz' (1024 KB)...
OKAY [ 0.057s]
writing 'tz'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 0.223s]
sending 'userdata' (510526 KB)...
OKAY [ 12.347s]
writing 'userdata'...
OKAY [ 3.906s]
finished. total time: 16.477s
target reported max download size of 536870912 bytes
sending 'userdata_64' (515143 KB)...
OKAY [ 12.662s]
writing 'userdata_64'...
FAILED (remote: partition table doesn't exist)
finished. total time: 12.678s
So those 5 failed:
erasing 'userdata'...
OKAY [ 1.477s]
finished. total time: 1.477s
erasing 'userdata_64'...
FAILED (remote: Partition table doesn't exist
)
finished. total time: 0.020s
sending 'ddr' (1024 KB)...
OKAY [ 0.057s]
writing 'ddr'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.077s
target reported max download size of 536870912 bytes
writing 'driver'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.816s
target reported max download size of 536870912 bytes
writing 'keystore'...
FAILED (remote: image is not a keystore file)
finished. total time: 0.072s
target reported max download size of 536870912 bytes
writing 'userdata_64'...
FAILED (remote: partition table doesn't exist)
finished. total time: 12.678s
After reboot to recovery, under wipe-advance wipe there is:
Dalvik
System
Data
Internal Storage
Cache
If I try to mount system, cannot do it.
Internal storage shows 9 Gb.
Do you have another ideas?
Thanks!
Just reset it with Qualcomm tool
http://forum.xda-developers.com/oneplus-2/general/guide-official-stock-reset-to-oos-2-2-0-t3290707
[
omrij said:
Just reset it with Qualcomm tool
http://forum.xda-developers.com/oneplus-2/general/guide-official-stock-reset-to-oos-2-2-0-t3290707
[
Click to expand...
Click to collapse
Did that 1st. Removed tampered bit before the procedure. No go.
Still
oem_nv_backup the nv partition is invalid
is shown.
Anyone knows how to check if modemst1 modemst2 blocks/partitions are created properly?
Will this erase internal storage too?
I want to use this tool because my FP sensor isnt working so i wanna give it a try
LOL9988 said:
Will this erase internal storage too?
I want to use this tool because my FP sensor isnt working so i wanna give it a try
Click to expand...
Click to collapse
It'll wipe everything, but I wouldn't use it because some of your partitions don't need to be wiped and some of the fastboot commands in the restore.sh file are wrong and will cause issues
For example:
sudo fastboot flash userdata userdata.img will flash the 16GB version's userdata.img even if you have a 64GB version of the phone.
sudo fastboot flash userdata_64 userdata_64G.img won't work because there is no userdata_64 partition - it's called userdata on both versions.
TBH, you're better off using advanced wipe in TWRP to wipe internal storage.
Waiting for the windows version to see if this app do the miracle fixing the second IMEI number on my phone, I tried everything already. Thanks for make this app.
Sent from my unknown using Tapatalk
iam newbie and want to try this solution to repair my fingerprint how to?
BEWARE, DO NOT SELECT ERASE OR IT WILL ERASE ALL YOUR MODEMS AND WONT BE ABLE TO GET THEM BACK. MY PHONE'S IMEIs ARE BROKEN. BOTH IMEI SHOW 0 AND CANNOT CONNECT MY PHONE TO ANY CELLPHONE COMPANY
Hi everyone! I have a problem with my Moto E XT1021. Some time ago I updated my device to Lollipop. Everything was ok but after a while it stopped working... Meantime I changed my device, so i put my Moto E in a drawer! Now I wanna use it again, but I have a lot of problem with fastboot (that's the only stage that works on my phone).
I tried to repeat the process for install the original firmware (http://forum.xda-developers.com/showthread.php?t=2755857) but i had always the same errors:
Code:
[email protected]:# fastboot flash partition gpt.bin
target reported max download size of 299892736 bytes
sending 'partition' (32 KB)...
OKAY [ 0.072s]
writing 'partition'...
(bootloader) Preflash validation failed
[COLOR="Red"]FAILED[/COLOR] (remote failure)
finished. total time: 0.650s
[email protected]:# fastboot flash motoboot motoboot.img
target reported max download size of 299892736 bytes
sending 'motoboot' (1669 KB)...
OKAY [ 0.149s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 3.263s]
finished. total time: 3.412s
[email protected]:# fastboot flash logo logo.bin
target reported max download size of 299892736 bytes
sending 'logo' (527 KB)...
OKAY [ 0.113s]
writing 'logo'...
OKAY [ 0.155s]
finished. total time: 0.268s
[email protected]:# fastboot flash boot boot.img
target reported max download size of 299892736 bytes
sending 'boot' (10200 KB)...
OKAY [ 0.411s]
writing 'boot'...
(bootloader) Preflash validation failed
[COLOR="red"]FAILED[/COLOR] (remote failure)
finished. total time: 1.121s
[email protected]:# fastboot flash recovery recovery.img
target reported max download size of 299892736 bytes
sending 'recovery' (10280 KB)...
OKAY [ 0.412s]
writing 'recovery'...
OKAY [ 1.785s]
finished. total time: 2.197s
[email protected]:# fastboot flash system system.img_sparsechunk.0
target reported max download size of 299892736 bytes
sending 'system' (242987 KB)...
OKAY [ 7.674s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
[COLOR="red"]FAILED[/COLOR] (remote failure)
finished. total time: 8.332s
[email protected]:# fastboot flash system system.img_sparsechunk.1
target reported max download size of 299892736 bytes
sending 'system' (256535 KB)...
OKAY [ 8.104s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
[COLOR="red"]FAILED[/COLOR] (remote failure)
finished. total time: 8.188s
[email protected]:# fastboot flash system system.img_sparsechunk.2
target reported max download size of 299892736 bytes
sending 'system' (257126 KB)...
OKAY [ 8.121s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
[COLOR="red"]FAILED[/COLOR] (remote failure)
finished. total time: 8.183s
[email protected]:# fastboot flash system system.img_sparsechunk.3
target reported max download size of 299892736 bytes
sending 'system' (45848 KB)...
OKAY [ 1.515s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
[COLOR="red"]FAILED[/COLOR] (remote failure)
finished. total time: 1.570s
[email protected]:# fastboot flash modem NON-HLOS.bin
target reported max download size of 299892736 bytes
sending 'modem' (46232 KB)...
OKAY [ 1.531s]
writing 'modem'...
OKAY [ 4.763s]
finished. total time: 6.294s
[email protected]:# fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.055s]
finished. total time: 0.055s
[email protected]:# fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.054s]
finished. total time: 0.054s
[email protected]:# fastboot flash fsg fsg.mbn
target reported max download size of 299892736 bytes
sending 'fsg' (648 KB)...
OKAY [ 0.110s]
writing 'fsg'...
OKAY [ 0.165s]
finished. total time: 0.275s
[email protected]:# fastboot erase cache
erasing 'cache'...
OKAY [ 0.369s]
finished. total time: 0.369s
After few try i unlocked bootloader, and the process was done ok (also if i read "Device is locked. Status code:0" is it normal?).
I tried to flash CWM or TWRP but without success. Always the same error: failed to validate system image.
Someone can help me?
Sorry for my english...
superazo said:
Hi everyone! I have a problem with my Moto E XT1021. Some time ago I updated my device to Lollipop. Everything was ok but after a while it stopped working... Meantime I changed my device, so i put my Moto E in a drawer! Now I wanna use it again, but I have a lot of problem with fastboot (that's the only stage that works on my phone).
I tried to repeat the process for install the original firmware (http://forum.xda-developers.com/showthread.php?t=2755857) but i had always the same errors:
After few try i unlocked bootloader, and the process was done ok (also if i read "Device is locked. Status code:0" is it normal?).
I tried to flash CWM or TWRP but without success. Always the same error: failed to validate system image.
Someone can help me?
Sorry for my english...
Click to expand...
Click to collapse
First unlock bootloader then flash twrp
What steps u r using to flash TWRP??
Ujwal Agrawal said:
What steps u r using to flash TWRP??
Click to expand...
Click to collapse
If you already unlocked boot loader
Then flash twrp in fastboot command
Fastboot flash recovery twrp.3.x.x.img
Rajendran Rasa said:
First unlock bootloader then flash twrp
Click to expand...
Click to collapse
I unlocked bootloader (with this guide: http://forum.xda-developers.com/showthread.php?t=2753110) then i tried flash recovery with this guide: http://forum.xda-developers.com/moto-e/general/root-moto-e-rooting-flashing-recovery-t2802971.
I tried with CWM and TWRP too!
superazo said:
I unlocked bootloader (with this guide: http://forum.xda-developers.com/showthread.php?t=2753110) then i tried flash recovery with this guide: http://forum.xda-developers.com/moto-e/general/root-moto-e-rooting-flashing-recovery-t2802971.
I tried with CWM and TWRP too!
Click to expand...
Click to collapse
https://dl.twrp.me/condor/
Try the latest TWRP
Ujwal Agrawal said:
Try the latest TWRP
Click to expand...
Click to collapse
Tried...
Code:
fastboot flash recovery twrp-3.0.2-0-condor.img
target reported max download size of 299892736 bytes
sending 'recovery' (6808 KB)...
OKAY [ 0.244s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.295s
If I reboot and go to "Recovery" voice:
Code:
failed to validate system image
Boot up failed
Hi,
Can someone clarify what this message means and why fastboot is failing?
Thanks
Code:
# fastboot flash aboot aboot_300032.bin
target reported max download size of 536870912 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.036s]
writing 'aboot'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 0.038s
Probably because your phone has unlocked bootloader and needs to be locked .
Instruction how to do that .
https://www.google.rs/amp/s/www.theandroidsoul.com/relock-bootloader-fastboot-android/amp/
Good luck : )
Any ideas how to solve this catch 22? I mean other than using the LG Flash Tool or LG UP. I didn't much success with them.
Thanks
Code:
# fastboot flash modem modem_16384.bin
target reported max download size of 536870912 bytes
sending 'modem' (86016 KB)...
OKAY [ 2.749s]
writing 'modem'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 2.750s
# fastboot oem lock
...
(bootloader) Erasing userdata and cache
OKAY [ 1.881s]
finished. total time: 1.882s
# fastboot flash modem modem_16384.bin
target reported max download size of 536870912 bytes
sending 'modem' (86016 KB)...
OKAY [ 2.775s]
writing 'modem'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 2.776s
greerdd said:
Any ideas how to solve this catch 22? I mean other than using the LG Flash Tool or LG UP. I didn't much success with them.
Thanks
Code:
# fastboot flash modem modem_16384.bin
target reported max download size of 536870912 bytes
sending 'modem' (86016 KB)...
OKAY [ 2.749s]
writing 'modem'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 2.750s
# fastboot oem lock
...
(bootloader) Erasing userdata and cache
OKAY [ 1.881s]
finished. total time: 1.882s
# fastboot flash modem modem_16384.bin
target reported max download size of 536870912 bytes
sending 'modem' (86016 KB)...
OKAY [ 2.775s]
writing 'modem'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 2.776s
Click to expand...
Click to collapse
I have the same problem. Did u solve this ?
exact same problem, is there any solution exist?
Meant to say bootloader said recovery big difference LOL I have the same issue with Pixel experience,Lineage,omni rom there are no errors in terminal or on phone here is the output from my terminal window i just find it odd any answers would be much appreciated thanks.
fastboot flash boot /home/no/pixelimages/PixelExperience_Plus_sofiar-10.0-20
200918-0058-UNOFFICIAL/boot.img *
target reported max download size of 536870912 bytes
sending 'boot_a' (65536 KB)...
OKAY [ *1.795s]
writing 'boot_a'...
OKAY [ *0.506s]
finished. total time: 2.301s
fastboot flash system /home/no/pixelimages/PixelExperience_Plus_sofiar-10.0-
20200918-0058-UNOFFICIAL/system.img *
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/2 (524284 KB)...
OKAY [ 14.571s]
writing 'system_a' 1/2...
OKAY [ *2.775s]
sending sparse 'system_a' 2/2 (473856 KB)...
OKAY [ 12.986s]
writing 'system_a' 2/2...
OKAY [ *2.572s]
finished. total time: 32.905s
fastboot flash product /home/no/pixelimages/PixelExperience_Plus_sofiar-10.0
-20200918-0058-UNOFFICIAL/product.img *
target reported max download size of 536870912 bytes
sending sparse 'product_a' 1/3 (524284 KB)...
OKAY [ 14.380s]
writing 'product_a' 1/3...
OKAY [ *2.776s]
sending sparse 'product_a' 2/3 (524284 KB)...
OKAY [ 14.388s]
writing 'product_a' 2/3...
OKAY [ *2.841s]
sending sparse 'product_a' 3/3 (167696 KB)...
OKAY [ *4.603s]
writing 'product_a' 3/3...
OKAY [ *1.170s]
finished. total time: 40.157s
fastboot flash vbmeta /home/no/pixelimages/PixelExperience_Plus_sofiar-10.0-
20200918-0058-UNOFFICIAL/vbmeta.img *
target reported max download size of 536870912 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ *0.001s]
writing 'vbmeta_a'...
OKAY [ *0.058s]
finished. total time: 0.058s
fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ *0.069s]
finished. total time: 0.069s
Weeaboodesu said:
Meant to say bootloader said recovery big difference LOL I have the same issue with Pixel experience,Lineage,omni rom there are no errors in terminal or on phone here is the output from my terminal window i just find it odd any answers would be much appreciated thanks.
fastboot flash boot /home/no/pixelimages/PixelExperience_Plus_sofiar-10.0-20
200918-0058-UNOFFICIAL/boot.img *
target reported max download size of 536870912 bytes
sending 'boot_a' (65536 KB)...
OKAY [ *1.795s]
writing 'boot_a'...
OKAY [ *0.506s]
finished. total time: 2.301s
fastboot flash system /home/no/pixelimages/PixelExperience_Plus_sofiar-10.0-
20200918-0058-UNOFFICIAL/system.img *
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/2 (524284 KB)...
OKAY [ 14.571s]
writing 'system_a' 1/2...
OKAY [ *2.775s]
sending sparse 'system_a' 2/2 (473856 KB)...
OKAY [ 12.986s]
writing 'system_a' 2/2...
OKAY [ *2.572s]
finished. total time: 32.905s
fastboot flash product /home/no/pixelimages/PixelExperience_Plus_sofiar-10.0
-20200918-0058-UNOFFICIAL/product.img *
target reported max download size of 536870912 bytes
sending sparse 'product_a' 1/3 (524284 KB)...
OKAY [ 14.380s]
writing 'product_a' 1/3...
OKAY [ *2.776s]
sending sparse 'product_a' 2/3 (524284 KB)...
OKAY [ 14.388s]
writing 'product_a' 2/3...
OKAY [ *2.841s]
sending sparse 'product_a' 3/3 (167696 KB)...
OKAY [ *4.603s]
writing 'product_a' 3/3...
OKAY [ *1.170s]
finished. total time: 40.157s
fastboot flash vbmeta /home/no/pixelimages/PixelExperience_Plus_sofiar-10.0-
20200918-0058-UNOFFICIAL/vbmeta.img *
target reported max download size of 536870912 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ *0.001s]
writing 'vbmeta_a'...
OKAY [ *0.058s]
finished. total time: 0.058s
fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ *0.069s]
finished. total time: 0.069s
Click to expand...
Click to collapse
mine is doing the same thing, ever figure out what the cause is?
CorporalCactus said:
mine is doing the same thing, ever figure out what the cause is?
Click to expand...
Click to collapse
No i found a custom rom that worked keep trying roms till you find one that works havoc os worked for me and make sure you are flashing in fastbootd
I was trying to upgrade from Android 11 to 12 with an Android 12 GSI using Fastboot, but whenever I try to install the system.img, it always fails with the error:
(bootloader) Preflash validation failed FAILED (remote failure)
Click to expand...
Click to collapse
I have seen that this error is common if you have the bootloader locked, but mine is unlocked.
Here's the full list of commands I used:
Code:
F:\Programs\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 805261312 bytes
sending 'boot_b' (52224 KB)...
OKAY [ 1.276s]
writing 'boot_b'...
OKAY [ 0.779s]
finished. total time: 2.056s
F:\Programs\Minimal ADB and Fastboot>fastboot flash vbmeta vbmeta.img
target reported max download size of 805261312 bytes
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.005s]
writing 'vbmeta_b'...
(bootloader) WARNING: vbmeta_b anti rollback downgrade, 0 vs 16
OKAY [ 0.036s]
finished. total time: 0.041s
F:\Programs\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 805261312 bytes
Invalid sparse file format at header magic
sending sparse 'system_b' 1/3 (786340 KB)...
OKAY [ 19.870s]
writing 'system_b' 1/3...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 19.962s
Why do I get this error, and is there any way to solve it?
ByteSeb said:
I was trying to upgrade from Android 11 to 12 with an Android 12 GSI using Fastboot, but whenever I try to install the system.img, it always fails with the error:
I have seen that this error is common if you have the bootloader locked, but mine is unlocked.
Here's the full list of commands I used:
Code:
F:\Programs\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 805261312 bytes
sending 'boot_b' (52224 KB)...
OKAY [ 1.276s]
writing 'boot_b'...
OKAY [ 0.779s]
finished. total time: 2.056s
F:\Programs\Minimal ADB and Fastboot>fastboot flash vbmeta vbmeta.img
target reported max download size of 805261312 bytes
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.005s]
writing 'vbmeta_b'...
(bootloader) WARNING: vbmeta_b anti rollback downgrade, 0 vs 16
OKAY [ 0.036s]
finished. total time: 0.041s
F:\Programs\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 805261312 bytes
Invalid sparse file format at header magic
sending sparse 'system_b' 1/3 (786340 KB)...
OKAY [ 19.870s]
writing 'system_b' 1/3...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 19.962s
Why do I get this error, and is there any way to solve it?
Click to expand...
Click to collapse
You need to be in fastboot d to flash system images. In regular fastboot, type fastboot reboot fastboot.
Beetle84 said:
You need to be in fastboot d to flash system images. In regular fastboot, type fastboot reboot fastboot.
Click to expand...
Click to collapse
It seems like that was working, but now I get this error:
FAILED (remote: Operation not permitted)
Click to expand...
Click to collapse
Here's the commands I used:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot_a' (52224 KB)...
OKAY [ 1.373s]
writing 'boot_a'...
OKAY [ 1.584s]
finished. total time: 2.958s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash vbmeta vbmeta.img
target reported max download size of 268435456 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ 0.003s]
writing 'vbmeta_a'...
OKAY [ 0.047s]
finished. total time: 0.050s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/7 (262108 KB)...
OKAY [ 7.087s]
writing 'system_a' 1/7...
OKAY [ 1.746s]
sending sparse 'system_a' 2/7 (262120 KB)...
OKAY [ 7.075s]
writing 'system_a' 2/7...
OKAY [ 1.723s]
sending sparse 'system_a' 3/7 (262112 KB)...
OKAY [ 7.015s]
writing 'system_a' 3/7...
OKAY [ 1.746s]
sending sparse 'system_a' 4/7 (262124 KB)...
OKAY [ 7.001s]
writing 'system_a' 4/7...
OKAY [ 1.736s]
sending sparse 'system_a' 5/7 (262088 KB)...
OKAY [ 7.013s]
writing 'system_a' 5/7...
FAILED (remote: Operation not permitted)
finished. total time: 43.777s
ByteSeb said:
It seems like that was working, but now I get this error:
Here's the commands I used:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot_a' (52224 KB)...
OKAY [ 1.373s]
writing 'boot_a'...
OKAY [ 1.584s]
finished. total time: 2.958s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash vbmeta vbmeta.img
target reported max download size of 268435456 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ 0.003s]
writing 'vbmeta_a'...
OKAY [ 0.047s]
finished. total time: 0.050s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/7 (262108 KB)...
OKAY [ 7.087s]
writing 'system_a' 1/7...
OKAY [ 1.746s]
sending sparse 'system_a' 2/7 (262120 KB)...
OKAY [ 7.075s]
writing 'system_a' 2/7...
OKAY [ 1.723s]
sending sparse 'system_a' 3/7 (262112 KB)...
OKAY [ 7.015s]
writing 'system_a' 3/7...
OKAY [ 1.746s]
sending sparse 'system_a' 4/7 (262124 KB)...
OKAY [ 7.001s]
writing 'system_a' 4/7...
OKAY [ 1.736s]
sending sparse 'system_a' 5/7 (262088 KB)...
OKAY [ 7.013s]
writing 'system_a' 5/7...
FAILED (remote: Operation not permitted)
finished. total time: 43.777s
Click to expand...
Click to collapse
if you update adb, you will see that it gives you an error for no space (atleast for me it did). To fix this, since your phone uses AB partitioning, you will need to do fastboot delete-logical-partition product_a and it should be good since you are using a GSI
Thanks! That worked
GigaPVP said:
if you update adb, you will see that it gives you an error for no space (atleast for me it did). To fix this, since your phone uses AB partitioning, you will need to do fastboot delete-logical-partition product_a and it should be good since you are using a GSI
Click to expand...
Click to collapse
i tried "fastboot delete-logical-partiton product_a" (a partition was active)
but error message occurs "unknown command delete-logical-partiton "
~using latest platform toot
~installing Android 13 GSI arm64+GSM .img
~on pixel 3