Need blankflash for moto z xt1650 OREO... please!!!! thx
I need it too
I need it too!
Here is the blank flash I used to solve my problem. I was on oreo but had bootloop issues, flashed gpt.bin then had the qusb issue.
Then I flashed blankflash_NCLS26.118-23-13-6-5_15.zip. This was blank flash worked for me, I hope it works for you.
Please do this at your own risk. After that, flash gpt.bin then use RSD Lite to flash full rom. Or download RSD_Lite_Motorola_XML_To_Batch_Script.zip for windows 8 and windows 10 users, to convert firmware to fastboot flashable file then run the flashfile.bat. adb and fastboot drivers should be installed for fastboot mode to work.
I have attached all the files.
Goodluck.
blankflash_oreo.zip:
Opening device: \\.\COM42
Detecting device
...cpu.id = 2375 (0x947)
...cpu.sn = 4266641337 (0xfe4fc7b9)
Opening singleimage
Loading package
Failed identify board. Wrong package?
ERROR: error loading package
Check qboot_log.txt for more details
Total time: 0.009s
_flash_singleimage()->error loading package
it is not for moto z
Use the first one blankflash_NCLS26.118-23-13-6-5_15.zip. that's the one I used
---------- Post added at 07:24 AM ---------- Previous post was at 07:22 AM ----------
p.m.6 said:
blankflash_oreo.zip:
Opening device: \\.\COM42
Detecting device
...cpu.id = 2375 (0x947)
...cpu.sn = 4266641337 (0xfe4fc7b9)
Opening singleimage
Loading package
Failed identify board. Wrong package?
ERROR: error loading package
Check qboot_log.txt for more details
Total time: 0.009s
_flash_singleimage()->error loading package
it is not for moto z
Click to expand...
Click to collapse
Use the other one. That's the one I used
THIS IS THE ERROR OF THE FIRST FILE:
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM42
[ 0.003] Detecting device
[ 0.006] ...cpu.id = 2375 (0x947)
[ 0.006] ...cpu.sn = 4266641337 (0xfe4fc7b9)
[ 0.006] Opening singleimage
[ 0.074] Loading package
[ 0.089] ...filename = singleimage.pkg.xml
[ 0.095] Loading programmer
[ 0.138] ...filename = programmer.elf
[ 0.139] Sending programmer
[ 0.215] Handling things over to programmer
[ 0.216] Identifying storage type
[ 0.223] Waiting for firehose to get ready
[ 3.254] ...UFS
[ 3.254] Identifying CPU version
[ 3.261] ...MSM8996 3.1
[ 3.262] Determining target secure state
[ 3.265] ...secure = yes
[ 3.318] Configuring device...
[ 3.337] Skipping UFS provsioning as target is secure
[ 3.337] Configuring device...
[ 3.350] Skipping 'setbootablestoragedrive' as target is secure
[ 3.350] Flashing GPT...
[ 3.374] Flashing partition:0 with gpt_main0.bin
[ 3.375] Initializing storage
[ 3.504] Target NAK!
[ 3.504] ...ERROR: Failed to initialize (open whole lun) UFS Device slot 0 part
ition 0
[ 3.505] ...ERROR: Failed to open the device 3 slot 0 partition 0
[ 3.506] ...INFO: Device type 3, slot 0, partition 0, error 0
[ 3.507] ...WARN: Get Info failed to open 3 slot 0, partition 0, error 0
[ 3.508] ...ERROR: Failed to get device info slot:0artition:0
[ 3.508] ...GetStorageInfo Failed - storage_device_get_info() returned FALSE
[ 3.509] ...ERROR 14: Line 1284: HANDLE_STORAGE_INFO_FAILURE
[ 3.510] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage
()->init_storage()->firehose_do_fmt()->do_recipe()->NAK
[ 3.510] Check qboot_log.txt for more details
[ 3.511] Total time: 3.548s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->gpt_flash
()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->NAK
D:\blankflash\blankflash>pause
Press any key to continue . . .
p.m.6 said:
blankflash_oreo.zip:
Opening device: \\.\COM42
Detecting device
...cpu.id = 2375 (0x947)
...cpu.sn = 4266641337 (0xfe4fc7b9)
Opening singleimage
Loading package
Failed identify board. Wrong package?
ERROR: error loading package
Check qboot_log.txt for more details
Total time: 0.009s
_flash_singleimage()->error loading package
it is not for moto z
Click to expand...
Click to collapse
p.m.6 said:
THIS IS THE ERROR OF THE FIRST FILE:
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM42
[ 0.003] Detecting device
[ 0.006] ...cpu.id = 2375 (0x947)
[ 0.006] ...cpu.sn = 4266641337 (0xfe4fc7b9)
[ 0.006] Opening singleimage
[ 0.074] Loading package
[ 0.089] ...filename = singleimage.pkg.xml
[ 0.095] Loading programmer
[ 0.138] ...filename = programmer.elf
[ 0.139] Sending programmer
[ 0.215] Handling things over to programmer
[ 0.216] Identifying storage type
[ 0.223] Waiting for firehose to get ready
[ 3.254] ...UFS
[ 3.254] Identifying CPU version
[ 3.261] ...MSM8996 3.1
[ 3.262] Determining target secure state
[ 3.265] ...secure = yes
[ 3.318] Configuring device...
[ 3.337] Skipping UFS provsioning as target is secure
[ 3.337] Configuring device...
[ 3.350] Skipping 'setbootablestoragedrive' as target is secure
[ 3.350] Flashing GPT...
[ 3.374] Flashing partition:0 with gpt_main0.bin
[ 3.375] Initializing storage
[ 3.504] Target NAK!
[ 3.504] ...ERROR: Failed to initialize (open whole lun) UFS Device slot 0 part
ition 0
[ 3.505] ...ERROR: Failed to open the device 3 slot 0 partition 0
[ 3.506] ...INFO: Device type 3, slot 0, partition 0, error 0
[ 3.507] ...WARN: Get Info failed to open 3 slot 0, partition 0, error 0
[ 3.508] ...ERROR: Failed to get device info slot:0artition:0
[ 3.508] ...GetStorageInfo Failed - storage_device_get_info() returned FALSE
[ 3.509] ...ERROR 14: Line 1284: HANDLE_STORAGE_INFO_FAILURE
[ 3.510] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage
()->init_storage()->firehose_do_fmt()->do_recipe()->NAK
[ 3.510] Check qboot_log.txt for more details
[ 3.511] Total time: 3.548s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->gpt_flash
()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->NAK
D:\blankflash\blankflash>pause
Press any key to continue . . .
Click to expand...
Click to collapse
Can I know how you came about the brick?
Muito obrigado!
hypafly said:
Here is the blank flash I used to solve my problem. I was on oreo but had bootloop issues, flashed gpt.bin then had the qusb issue.
Then I flashed blankflash_NCLS26.118-23-13-6-5_15.zip. This was blank flash worked for me, I hope it works for you.
Please do this at your own risk. After that, flash gpt.bin then use RSD Lite to flash full rom. Or download RSD_Lite_Motorola_XML_To_Batch_Script.zip for windows 8 and windows 10 users, to convert firmware to fastboot flashable file then run the flashfile.bat. adb and fastboot drivers should be installed for fastboot mode to work.
I have attached all the files.
Goodluck.
Click to expand...
Click to collapse
Muito obrigado! Nada havia resolvido até esse momento, apenas o seu funcionou para mim, Thk my brother.
Pode me explicar ?
rssangel said:
Muito obrigado! Nada havia resolvido até esse momento, apenas o seu funcionou para mim, Thk my brother.
Click to expand...
Click to collapse
pode me explicar por favor...
hypafly said:
Here is the blank flash I used to solve my problem. I was on oreo but had bootloop issues, flashed gpt.bin then had the qusb issue.
Then I flashed blankflash_NCLS26.118-23-13-6-5_15.zip. This was blank flash worked for me, I hope it works for you.
Please do this at your own risk. After that, flash gpt.bin then use RSD Lite to flash full rom. Or download RSD_Lite_Motorola_XML_To_Batch_Script.zip for windows 8 and windows 10 users, to convert firmware to fastboot flashable file then run the flashfile.bat. adb and fastboot drivers should be installed for fastboot mode to work.
I have attached all the files.
Goodluck.
Click to expand...
Click to collapse
Im with oem locked now.
in adb says "failed remote failure"
i try with officcial 7.11 and 8.0
any ideas? thx
kilombero said:
Im with oem locked now.
in adb says "failed remote failure"
i try with officcial 7.11 and 8.0
any ideas? thx
Click to expand...
Click to collapse
Flash the stock 8.0 Oreo ROM from here https://forum.xda-developers.com/moto-z/development/stock-moto-z-8-0-firmware-t3805226
Use the RSD tool mentioned in the op. Or use RSD Lite. It should work.
hypafly said:
Flash the stock 8.0 Oreo ROM from here https://forum.xda-developers.com/moto-z/development/stock-moto-z-8-0-firmware-t3805226
Use the RSD tool mentioned in the op. Or use RSD Lite. It should work.
Click to expand...
Click to collapse
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.241s
C:\Users\Rodri\Downloads\adb-fastboot-latest\adb-fastboot-latest>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (7792 KB)...
OKAY [ 0.240s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name xbl
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name pmic
(bootloader) Invalid partition name hyp
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.317s
it doesnt work... FUUUUUCK! hahahaha
Hello-
I installed w 8.1 to try this... and doesnt work
when i execute the command "fastboot flash partition gpt.bin" in cmd say this:
Microsoft Windows [Versión 6.3.9600]
(c) 2013 Microsoft Corporation. Todos los derechos reservados.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
4881a40a fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (142 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.234s
FUCCCCCCKKK!!! hahahaha
im in :
BL: 91.09(*) (sha-7de07a7, 2018-02-20
Baseband:
Product/Variant: sheridan 000000000000 32gb P3B
Oem_locked
Fuccccck haa
kilombero said:
Hello-
I installed w 8.1 to try this... and doesnt work
when i execute the command "fastboot flash partition gpt.bin" in cmd say this:
Microsoft Windows [Versión 6.3.9600]
(c) 2013 Microsoft Corporation. Todos los derechos reservados.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
4881a40a fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (142 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.234s
FUCCCCCCKKK!!! hahahaha
im in :
BL: 91.09(*) (sha-7de07a7, 2018-02-20
Baseband:
Product/Variant: sheridan 000000000000 32gb P3B
Oem_locked
Fuccccck haa
Click to expand...
Click to collapse
you must have the bootloader unlocked for flash that rom
eLaDiio said:
you must have the bootloader unlocked for flash that rom
Click to expand...
Click to collapse
the bootloader before the hardbrick was unlocked. after the blankflash its blocked.
i got a new and beuty paperweight? jaja
kilombero said:
the bootloader before the hardbrick was unlocked. after the blankflash its blocked.
i got a new and beuty paperweight? jaja
Click to expand...
Click to collapse
ajhjahjahja could be, but i supposed if you have access to the fastboot commands you could unlock the bootloader, btw why not flash a 7.11 stock rom?, later reboot on bootloader and flash the oreo stock full rom or sideload the oreo update(but i think this could make other hardbrick)
kilombero said:
the bootloader before the hardbrick was unlocked. after the blankflash its blocked.
i got a new and beuty paperweight? jaja
Click to expand...
Click to collapse
good day,
I don't know about the Moto Z but the Moto G5S (I own) can be unbricked via full dump and
sdcard boot
https://forum.xda-developers.com/moto-g5s/how-to/blank-flash-montana-t3765150
perhaps it helps
kind regards
eLaDiio said:
ajhjahjahja could be, but i supposed if you have access to the fastboot commands you could unlock the bootloader, btw why not flash a 7.11 stock rom?, later reboot on bootloader and flash the oreo stock full rom or sideload the oreo update(but i think this could make other hardbrick)
Click to expand...
Click to collapse
when i try to unlock with commands in cmd it throws me an error. im really stuck here.
any update on the blankflash for bl 91.09? I accidentally downgraded to 7.1 and phone now hardbricked. Last BL is 91.09. Phone is still being detected in devman. Any help is appreciated. Thanks!
here is the logs when trying to use blankflash_NCLS26.118-23-13-6-5_15
**** Log buffer [000001] 2018-08-26_10:30:21 ****
[ 0.000] Opening device: \\.\COM3
[ 0.003] Detecting device
[ 4.012] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.012] Check qboot_log.txt for more details
[ 4.013] Total time: 4.017s
[ 4.014]
[ 4.014] qboot version 3.40
[ 4.014]
[ 4.014] DEVICE {
[ 4.014] name = "\\.\COM3",
[ 4.014] flags = "0x64",
[ 4.014] addr = "0x61FE5C",
[ 4.014] api.bnr = "0x2EB2C98",
[ 4.014] }
[ 4.014]
[ 4.014]
[ 4.014] Backup & Restore {
[ 4.014] num_entries = 0,
[ 4.014] restoring = "false",
[ 4.014] backup_error = "not started",
[ 4.014] restore_error = "not started",
[ 4.014] }
[ 4.014]
Related
Looks like there is a new update online at motorola-global-portal.custhelp.com
XT1624 01-SEP-16 MPJ24.139-64 6.0.1 1046 6.0.1 1046 Download
Since I have the amazon ad version it gave me the amazon version.
ATHENE_AMZ_MPJ24.139-64_65_cid50_amz.tgz
I hope we can still flash the regular nonamazon moto G4 image.
link to the update download? I dont see it going to motorola-global-portal.custhelp.com
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images#
But you need to be logged into your motorola account to see it
If you cant find it i'll upload it to one of my servers
ATHENE_AMZ_MPJ24.139-64_65_cid50_amz.tgz
https://mega.nz/#!V99VHAwR!VfH7Zg3a5...bkpWFM3ZJsmEqQ
---------- Post added at 02:20 AM ---------- Previous post was at 02:17 AM ----------
I installed the RootJunkie firmware ATHENE_MPJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml.zip on my Amazon XT1624 and I have the bootloader unlocked. Will this update lock my bootloader? Does this update includes the ads from Amazon?
I doubt it will relock the bootloader, but since its the amazon software version, the ads will be back
Rempala said:
I doubt it will relock the bootloader, but since its the amazon software version, the ads will be back
Click to expand...
Click to collapse
RootJunkie says otherwise. He says it could lock the bootloader.
http://forum.xda-developers.com/showpost.php?p=68508421&postcount=382
Not sure but those of us that flashed the stock moto image should stay away from this. Mine now tells me
{
"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"
}
Sent from my SM-N900P using Tapatalk
wormy123789 said:
Not sure but those of us that flashed the stock moto image should stay away from this. Mine now tells me View attachment 3863640
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
When you flashed the firmware, did it lock the bootloader? If it did, did you unlocked it with Unique ID Moto emailed you?
mine was never unlocked. that in its self may be the issue as well. Im looking for ways to get mine back up and running
Danny1976 said:
When you flashed the firmware, did it lock the bootloader? If it did, did you unlocked it with Unique ID Moto emailed you?
Click to expand...
Click to collapse
as expected moto support was un helpful. the only thing they would say was to send it in to them.
wormy987123 said:
mine was never unlocked. that in its self may be the issue as well. Im looking for ways to get mine back up and running
as expected moto support was un helpful. the only thing they would say was to send it in to them.
Click to expand...
Click to collapse
Did you try flashing the new firmware with RSDLite? Try flashing RootJunkie Firmware with RSDLite. http://rootjunkysdl.com/files/?dir=Moto G 4th Gen XT1625/Firmware
Danny1976 said:
Did you try flashing the new firmware with RSDLite? Try flashing RootJunkie Firmware with RSDLite. http://rootjunkysdl.com/files/?dir=Moto G 4th Gen XT1625/Firmware
Click to expand...
Click to collapse
I flashed it with fastboot. Rsdlite would work if there was an .xml file
Sent from my SM-N900P using Tapatalk
wormy123789 said:
I flashed it with fastboot. Rsdlite would work if there was an .xml file
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
RootJunkie firmware file has the XML file. Try that and see if it works
Danny1976 said:
RootJunkie firmware file has the XML file. Try that and see if it works
Click to expand...
Click to collapse
I did, it fails signature verification for me
Sent from my SM-N900P using Tapatalk
here is the output from terminal Michaels-MacBook-Pro:ATHENE_AMZ_MPJ24.139-64_65_cid50_amz michaelballard$ cd /Users/michaelballard/Downloads/ATHENE_MPJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml
Michaels-MacBook-Pro:ATHENE_MPJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml michaelballard$ ./rsd-flash.sh servicefile.xml
___ ____ ____ _____ ____ ___ ____ ____ __ ________ _ _
/ _ \/ _ \/ _ \/_ _/_ / / / / / \/ / //_/\ \/ / / __/ _ \/ \/ \
/ , _/ |_| / |_| / / / / // / /_/ / / < \ /_/ /_/ |_| / , , \
/_/|_|\____/\____/ /_/ \___/\____/_/\_/_/\_/ /_/_/___/\____/_/ \/ \_\
----------------------------------------------------------------------------
Welcome to RSD Lite For Mac and Linux press enter to start your flash
----------------------------------------------------------------------------
max-sparse-size: 268435456
finished. total time: 0.008s
...
OKAY [ 0.004s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.041s
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.142s]
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 'aboot'
(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 'keymaster'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.512s]
finished. total time: 0.655s
target reported max download size of 536870912 bytes
sending 'logo' (1848 KB)...
OKAY [ 0.067s]
writing 'logo'...
OKAY [ 0.073s]
finished. total time: 0.140s
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.634s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.798s
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.632s]
writing 'recovery'...
(bootloader) Security version downgrade
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.797s
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.630s]
writing 'dsp'...
OKAY [ 0.439s]
finished. total time: 1.069s
target reported max download size of 536870912 bytes
sending 'oem' (124713 KB)...
OKAY [ 4.772s]
writing 'oem'...
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 4.827s
target reported max download size of 536870912 bytes
sending 'system' (257282 KB)...
OKAY [ 9.786s]
writing 'system'...
(bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.846s
target reported max download size of 536870912 bytes
sending 'system' (258607 KB)...
OKAY [ 9.874s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.889s
target reported max download size of 536870912 bytes
sending 'system' (260204 KB)...
OKAY [ 9.416s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.432s
target reported max download size of 536870912 bytes
sending 'system' (250512 KB)...
OKAY [ 8.645s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.658s
target reported max download size of 536870912 bytes
sending 'system' (254492 KB)...
OKAY [ 8.752s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.770s
target reported max download size of 536870912 bytes
sending 'system' (257841 KB)...
OKAY [ 9.058s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.072s
target reported max download size of 536870912 bytes
sending 'system' (256191 KB)...
OKAY [ 8.884s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.906s
target reported max download size of 536870912 bytes
sending 'system' (150189 KB)...
OKAY [ 5.377s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.391s
target reported max download size of 536870912 bytes
sending 'modem' (76861 KB)...
OKAY [ 2.761s]
writing 'modem'...
OKAY [ 1.981s]
finished. total time: 4.742s
erasing 'modemst1'...
OKAY [ 0.029s]
finished. total time: 0.029s
erasing 'modemst2'...
OKAY [ 0.029s]
finished. total time: 0.029s
target reported max download size of 536870912 bytes
sending 'fsg' (1896 KB)...
OKAY [ 0.073s]
writing 'fsg'...
OKAY [ 0.086s]
finished. total time: 0.159s
erasing 'DDR'...
OKAY [ 0.008s]
finished. total time: 0.008s
...
OKAY [ 0.004s]
finished. total time: 0.004s
---------------------------------------------------------
Please check for errors then press enter to reboot device
---------------------------------------------------------
wormy123789 said:
I did, it fails signature verification for me
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Have you tried installing this image of a Stock Amazon OEM image. But I think it needs TWRP, but I am not sure.
http://rootjunkysdl.com/files/Moto ...d/Amazon-Stock-6.0.1-2016-07-11--19-36-54.zip
Danny1976 said:
Have you tried installing this image of a Stock Amazon OEM image. But I think it needs TWRP, but I am not sure.
http://rootjunkysdl.com/files/Moto ...d/Amazon-Stock-6.0.1-2016-07-11--19-36-54.zip
Click to expand...
Click to collapse
yeah for that i would need twrp installed
wormy987123 said:
yeah for that i would need twrp installed
Click to expand...
Click to collapse
You probably are more tech savvy than me, but I would try using Moto Fastboot and see if it gets past the verification.
http://forum.xda-developers.com/gen...ng-mfastboot-exe-to-unbrick-motorola-t3203518
---------- Post added at 05:26 PM ---------- Previous post was at 05:15 PM ----------
wormy987123 said:
yeah for that i would need twrp installed
Click to expand...
Click to collapse
Try this with the Moto Fastboot:
If you downloaded a firmware with .xml.zip extension, follow these steps:
Type the following commands in the cmd window one by one and press Enter key after each command line. Make sure that you see OKAY message on cmd after executing each command:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Your phone will reboot automatically.
Wait till your device boots up. Go through the initial setup and enjoy!
Just FYI to people here:
The image that was posted on Moto's site is for the XT1624, the Indian Moto G4. This is not supposed to be flashed on another model, like the US XT1625. If you try to flash it on another model, regardless if you have an unlocked bootloader or not, you're gonna have a bad time.
xtermmin said:
Just FYI to people here:
The image that was posted on Moto's site is for the XT1624, the Indian Moto G4. This is not supposed to be flashed on another model, like the US XT1625. If you try to flash it on another model, regardless if you have an unlocked bootloader or not, you're gonna have a bad time.
Click to expand...
Click to collapse
Where did you get that info from? Please post a link.
when i reboot it , it can't open
i was unlock BootLoader,
all 7.11 system image was been recovery, not useful
reboot it
your device is it can not be trusted and may not to work properly
visit this link on an other device
g.co/ABH
press power to pause boot
ADB command code
C:\ADB>flash-all
Sending 'bootloader' (2901 KB) OKAY [ 0.212s]
Writing 'bootloader' (bootloader) Device State : Unlocked
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[bct] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_preboot_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[hboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtbootwb0] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[tos] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[sp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[gp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[pt] unzipping & flashing...
(bootloader) ...... Successful
OKAY [ 5.463s]
Finished. Total time: 5.684s
rebooting into bootloader OKAY [ 0.036s]
Finished. Total time: 0.040s
< waiting for any device >
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: 3.50.0.0143
Baseband Version.....: N/A
Serial Number........: HT4ADJT01784
--------------------------------------------
Checking product OKAY [ 0.003s]
Checking version-bootloader OKAY [ 0.004s]
extracting boot.img (8 MB) to disk... took 0.027s
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
extracting recovery.img (10 MB) to disk... took 0.033s
archive does not contain 'recovery.sig'
extracting system.img (1453 MB) to disk... took 8.673s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (122 MB) to disk... took 0.785s
archive does not contain 'vendor.sig'
Couldn't parse erase-block-size '0xUnknown command'.
Couldn't parse logical-block-size '0xUnknown command'.
F2FS-tools: mkfs.f2fs Ver: 1.10.0 (2018-01-30)
Info: Disable heap-based policy
Info: Debug level = 0
Info: Label =
Info: Trim is disabled
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 53714944 (26228 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
Info: Overprovision ratio = 1.240%
Info: Overprovision segments = 328 (GC reserved = 169)
Info: format successful
Couldn't parse erase-block-size '0xUnknown command'.
Couldn't parse logical-block-size '0xUnknown command'.
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 65536 4k blocks and 65536 inodes
Filesystem UUID: 177cbd32-7522-11e8-8a10-bd7422ec86f1
Superblock backups stored on blocks:
32768
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'boot' (8636 KB) OKAY [ 0.552s]
Writing 'boot' (bootloader) Device State : Unlocked
OKAY [ 0.829s]
Sending 'recovery' (11204 KB) OKAY [ 0.662s]
Writing 'recovery' (bootloader) Device State : Unlocked
OKAY [ 0.946s]
Sending sparse 'system' 1/4 (478340 KB) OKAY [ 24.143s]
Writing sparse 'system' 1/4 (bootloader) Device State : Unlocked
OKAY [ 20.047s]
Sending sparse 'system' 2/4 (468227 KB) OKAY [ 23.647s]
Writing sparse 'system' 2/4 (bootloader) Device State : Unlocked
OKAY [ 19.934s]
Sending sparse 'system' 3/4 (499117 KB) FAILED (command write failed (Unknown error))
Finished. Total time: 108.734s
Press any key to exit...
can anybaby help me? how to fix it?
my English not good。
夏默秋殇 said:
when i reboot it , it can't open
i was unlock BootLoader,
all 7.11 system image was been recovery, not useful
reboot it
your device is it can not be trusted and may not to work properly
visit this link on an other device
g.co/ABH
press power to pause boot
ADB command code
C:\ADB>flash-all
Sending 'bootloader' (2901 KB) OKAY [ 0.212s]
Writing 'bootloader' (bootloader) Device State : Unlocked
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[bct] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_preboot_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[hboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtbootwb0] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[tos] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[sp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[gp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[pt] unzipping & flashing...
(bootloader) ...... Successful
OKAY [ 5.463s]
Finished. Total time: 5.684s
rebooting into bootloader OKAY [ 0.036s]
Finished. Total time: 0.040s
< waiting for any device >
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: 3.50.0.0143
Baseband Version.....: N/A
Serial Number........: HT4ADJT01784
--------------------------------------------
Checking product OKAY [ 0.003s]
Checking version-bootloader OKAY [ 0.004s]
extracting boot.img (8 MB) to disk... took 0.027s
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
extracting recovery.img (10 MB) to disk... took 0.033s
archive does not contain 'recovery.sig'
extracting system.img (1453 MB) to disk... took 8.673s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (122 MB) to disk... took 0.785s
archive does not contain 'vendor.sig'
Couldn't parse erase-block-size '0xUnknown command'.
Couldn't parse logical-block-size '0xUnknown command'.
F2FS-tools: mkfs.f2fs Ver: 1.10.0 (2018-01-30)
Info: Disable heap-based policy
Info: Debug level = 0
Info: Label =
Info: Trim is disabled
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 53714944 (26228 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
Info: Overprovision ratio = 1.240%
Info: Overprovision segments = 328 (GC reserved = 169)
Info: format successful
Couldn't parse erase-block-size '0xUnknown command'.
Couldn't parse logical-block-size '0xUnknown command'.
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 65536 4k blocks and 65536 inodes
Filesystem UUID: 177cbd32-7522-11e8-8a10-bd7422ec86f1
Superblock backups stored on blocks:
32768
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'boot' (8636 KB) OKAY [ 0.552s]
Writing 'boot' (bootloader) Device State : Unlocked
OKAY [ 0.829s]
Sending 'recovery' (11204 KB) OKAY [ 0.662s]
Writing 'recovery' (bootloader) Device State : Unlocked
OKAY [ 0.946s]
Sending sparse 'system' 1/4 (478340 KB) OKAY [ 24.143s]
Writing sparse 'system' 1/4 (bootloader) Device State : Unlocked
OKAY [ 20.047s]
Sending sparse 'system' 2/4 (468227 KB) OKAY [ 23.647s]
Writing sparse 'system' 2/4 (bootloader) Device State : Unlocked
OKAY [ 19.934s]
Sending sparse 'system' 3/4 (499117 KB) FAILED (command write failed (Unknown error))
Finished. Total time: 108.734s
Press any key to exit...
can anybaby help me? how to fix it?
my English not good。
Click to expand...
Click to collapse
Have you tried flashing images 1 at a time? Fastboot flash system system.img
Fastboot flash vendor vendor.img
Etc.
madbat99 said:
Have you tried flashing images 1 at a time? Fastboot flash system system.img
Fastboot flash vendor vendor.img
Etc.
Click to expand...
Click to collapse
yes ,the code
C:\ADB>fastboot flash bootloader bootloader-flounder-3.50.0.0143.img
Sending 'bootloader' (2901 KB) OKAY [ 0.210s]
Writing 'bootloader' (bootloader) Device State : Unlocked
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[bct] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_preboot_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[hboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtbootwb0] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[tos] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[sp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[gp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[pt] unzipping & flashing...
(bootloader) ...... Successful
OKAY [ 5.447s]
Finished. Total time: 5.677s
C:\ADB>fastboot reboot-bootloader
rebooting into bootloader OKAY [ 0.040s]
Finished. Total time: 0.040s
C:\ADB>fastboot reboot-bootloader
rebooting into bootloader OKAY [ 0.026s]
Finished. Total time: 0.027s
C:\ADB>fastboot flash boot boot.img
Sending 'boot' (8622 KB) OKAY [ 0.520s]
Writing 'boot' (bootloader) Device State : Unlocked
OKAY [ 0.834s]
Finished. Total time: 1.356s
C:\ADB>fastboot flash system system.img
Sending sparse 'system' 1/4 (478340 KB) OKAY [ 24.182s]
Writing sparse 'system' 1/4 (bootloader) Device State : Unlocked
OKAY [ 19.999s]
Sending sparse 'system' 2/4 (468231 KB) OKAY [ 23.622s]
Writing sparse 'system' 2/4 (bootloader) Device State : Unlocked
OKAY [ 19.938s]
Sending sparse 'system' 3/4 (499117 KB) FAILED (command write failed (Unknown error))
Finished. Total time: 95.634s
C:\ADB>fastboot flash cache cache.img
Sending 'cache' (6248 KB) OKAY [ 0.349s]
Writing 'cache' (bootloader) Device State : Unlocked
OKAY [ 0.712s]
Finished. Total time: 1.073s
C:\ADB>fastboot flash vendor vendor.img
Sending 'vendor' (125361 KB) OKAY [ 5.914s]
Writing 'vendor' (bootloader) Device State : Unlocked
OKAY [ 5.715s]
Finished. Total time: 11.640s
C:\ADB>fastboot reboot
Rebooting
Finished. Total time: 0.057s
C:\ADB>
Not sure why that 3rd system sparse chunk is failing. And not even trying the 4th.
Maybe try flashing twrp to recovery and flash a custom rom. Maybe LineageOS.
the recovery photo 。
{
"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"
}
[url]https://forum.xda-developers.com/album.php?albumid=14996&pictureid=57661[/URL]
madbat99 said:
Not sure why that 3rd system sparse chunk is failing. And not even trying the 4th.
Maybe try flashing twrp to recovery and flash a custom rom. Maybe LineageOS.
Click to expand...
Click to collapse
The twrp can't load internal Storage 。 when i select storage ,it's 0 MB
i only try fix it in fastboot。
夏默秋殇 said:
The twrp can't load internal Storage 。 when i select storage ,it's 0 MB
i only try fix it in fastboot。
Click to expand...
Click to collapse
Make sure you have the newest twrp. Format data. Not wipe. Format. In twrp wipe-->advanced wipe-->format-->internal storage. Maybe fastboot erase userdata
madbat99 said:
Make sure you have the newest twrp. Format data. Not wipe. Format. In twrp wipe-->advanced wipe-->format-->internal storage. Maybe fastboot erase userdata
Click to expand...
Click to collapse
it's failed
E:Unable to find partition size for '/boot'
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/vebdor_image'
E:Unable to find partition size for '/misc'
E:Unable to find partition size for '/persistent'
E:Unable to find partition size for '/system_image'
E: primary block device 'dev/block/platform/sdhci-tegra.3/by-name/UDA' for mount point '/data' is not present!
E:Unable to set bootlader message.
Failed to mount '/cache'(Invalid argument)
Updating partition details....
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/system' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Full SELinux support is present
Failed to mount '/cache' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Unable to wipe Data
can somebody help me?
hello?anybody?
hello?
Please make sure you are on a recent version of the adb tools. links for multi os download
Can you try 'fastboot format system' while in bootloader? Does it do a format? If it does you could try the full flash procedure again.
Perhaps twrp recorvery can also help.
flash twrp on your device by using 'fastboot flash recovery twrp-file-you-downloaded.img & fastboot boot twrp-file-you-downloaded.img'
In twrp you should try the format function.
Hi
Hey all.. Im not exactly new here . I just read and read
FMFL
Got same error while LOCKING Bootloader thingy .....
Just keep trying to boot to recovery (Power and and Vol DN then quickly UP) that took me all of 5 minutes to gain the upper hand but I did prevail.... 9 took me hours to get the nutz to hit the Flash Button kept going back and forth re reading a lot of useless **** on a few other sights dont know why i even looked there When all the stuff is always right here
Really its because of all you people here.
Thank you for all the reading keeps my mind young!
Ron T
IT Dept.
Deskside support partner
AECOM
Mississauga, ON
aecom.com
Imagine it. Delivered
---------- Post added at 01:44 AM ---------- Previous post was at 01:41 AM ----------
wow I cant say ****? Tee Hee
No i dont post nearly enough
Roffl I had a couple sites with forums only for satellite TV Hacking I left everything wide open .. ya a few bans but it was needed i guess LOL
CYa
Thx
Ron T
IT Dept.
Deskside support partner
AECOM
Mississauga, ON
aecom.com
Imagine it. Delivered
hallo
help me with the current image have been destroyed and can not boot
hello xda communities i have a realme c1 device after updates my phone show these thing ,,the current image have been destroyed and can not boot.please flash the corrrect image or contact custamer service,,
also show these options-
power off
restart
recovery mode
fastboot mode
back to previous page
and
i can not flash it because of this -
Device state - Locked:
please help me please
goldi gupta said:
hello xda communities i have a realme c1 device after updates my phone show these thing ,,the current image have been destroyed and can not boot.please flash the corrrect image or contact custamer service,,
also show these options-
power off
restart
recovery mode
fastboot mode
back to previous page
and
i can not flash it because of this -
Device state - Locked:
please help me please
Click to expand...
Click to collapse
Try asking in a Realme forum. You posted in Nexus 9, and old tablet Google produced prior to the Pixel line.
Hi,
I entered 0 (zero) before the serial number (I have 7 digit serial number), got an img file from Lenovo. In the "tool all in one" program I unlocked the bootloader. Unfortunately, after restarting the phone does not turn on. I can see only Lenovo logo. What ideas how to fix it?
I'm attempting to downgrade from Android 11 to Android 10 for a plethora of reasons. These are the instructions I am following:
Gordstor instructions
I have done the following:
I enabled "OEM Unlocking"
I unlocked the bootloader.
I enabled "USB debugging".
I found my Software Channel and I believe it is "RetUS".
I determined that my phone does not use fastbootd.
I installed LMSA on my Windows 10 PC.
I downloaded what I believe is the correct Android 10 firmware, "XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml"
I renamed it "SOFIA_RETAIL_RPMS31.Q1_54_13_7_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml"
I moved it to "C:\ProgramData\RSA\Download\RomFiles\"
I then set my Moto G Power (2020) in fastboot mode and plugged it into my PC via USB C cable.
From within LMSA, I rescued my moto, which I was hoping would be my last step.
LMSA attempts to push image to phone, but only gets to 32%. at that point,, I get the error message: "FASTBOOT FLASH SINGLE PARTITION. Flash failed. Please tray again."
Below is output from fastboot getvar all and fastboot getvar is-userspace.
Any help greatly appreciated.
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-sofia_retail-2c4117ea2d6-211002
(bootloader) product: sofia
(bootloader) board: sofia
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZY227QFDWG
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 1C00A4C4
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805263360
(bootloader) reason: Volume down key pressed
(bootloader) imei: 357244102645879
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 08-26-2020
(bootloader) sku: XT2041-4
(bootloader) carrier_sku: XT2041-4
(bootloader) battid: SB18C57585
(bootloader) battery-voltage: 3972
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retus
(bootloader) ro.build.fingerprint[0]: motorola/sofia_retail/sofia:11/RPM
(bootloader) ro.build.fingerprint[1]: S31.Q1-54-13-7/57bd6:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.qcom: LA.UM.9.11.r1-02100-NICOBAR.0
(bootloader) version-baseband: M6125_43.45.03.49R SOFIA_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.14.180-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Sat O
(bootloader) kernel.version[4]: ct 2 10:30:41 CDT 2021
(bootloader) git:xbl: MBM-3.0-sofia_retail-1186df2c3-211002
(bootloader) git:xbl_config: MBM-3.0-sofia_retail-1186df2c3-211002
(bootloader) git:rpm: MBM-3.0-sofia_retail-2579863-211002
(bootloader) git:tz: MBM-3.0-sofia_retail-da525ab0-211002
(bootloader) git:hyp: MBM-3.0-sofia_retail-da525ab0-211002
(bootloader) git:devcfg: MBM-3.0-sofia_retail-da525ab0-211002
(bootloader) git:cmnlib: MBM-3.0-sofia_retail-da525ab0-211002
(bootloader) git:cmnlib64: MBM-3.0-sofia_retail-da525ab0-211002
(bootloader) git:keymaster: MBM-3.0-sofia_retail-cf01af6-211002
(bootloader) gitrov: MBM-3.0-sofia_retail-da525ab0-211002
(bootloader) git:abl: MBM-3.0-sofia_retail-2c4117ea2d6-211002
(bootloader) git:qupfw: MBM-3.0-sofia_retail-319dab9-211002
(bootloader) git:uefisecapp: MBM-3.0-sofia_retail-da525ab0-211002
(bootloader) frp-state: protected (77)
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C55260
(bootloader) primary-display: tm_ft8756_fhd_vid
(bootloader) secondary-display:
fastboot getvar is-userspace
is-userspace: no
Finished. Total time: 0.000s
Click to expand...
Click to collapse
Note that if I download the latest stock firmware via LMSA, I am able to push it to the phone via the rescue operation. This is good news, but does not help me resolve my issue.
Maybe the A10 firmware I'm attempting to push to it is not the correct one?
I also tried switching to fastbootd via these commands,
fastboot reboot fastbood AND adb reboot fastbootd.
Neither worked.
I'm at a stand still at the moment. Anybody have any suggestions?
The saga continues...
I finally decided to do the downgrade using the commands in the flashfile.xml file.
Everything appeared to go well. However, once the phone rebooted, it entered an infinite reboot cycle.
I did manage to stop it from rebooting and using Rescue and Smart Assistant I was able to push A11 stock firmware. So at least it's not bricked, but I'm back to square one.
ezjamm
What I discovered after upgrading to XT2041-4_SOFIA_RETUS_11_RPMS31.Q1-54-13-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC with fastboot flash commands pasted into a terminal:
The bootloader can't be downgraded. Bootlooping ensues when mixing old and new among some of these: partition bootloader radio bluetooth dsp logo. I flashed 11 firmware of all of those, then successfully installed LineageOS with image flashing in fastbootd (boot system vbmeta product).
Don't flash TWRP, because that overwrites fastbootd. Instead, fastboot boot twrp.img from the bootloader if you need it.
Hi danrex,
Thanx for the suggestions. It's going to take me a while to decipher what you wrote though.
Can you expand on what you wrote above? I honestly only understood about 30%. I'm only 3 weeks old when it comes to xda and hacking an android phone.
Thanx,
ezjamm
fastboot getvar is-userspace
Click to expand...
Click to collapse
fastbootd is Motorola's userspace fastboot invoked from the bootloader unless fastbootd has been replaced by TWRP:
# fastboot reboot fastboot
# fastboot getvar is-userspace
is-userspace no: bootloader
is-userspace yes: fastbootd (or TWRP in fastboot mode if I recall correctly)
fastbootd mode is needed for fastboot flashing some parts like a custom vbmeta (verified boot meta) for a non-stock ROM.
What I discovered after upgrading to XT2041-4_SOFIA_RETUS_11_RPMS31.Q1-54-13-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Click to expand...
Click to collapse
That's Android 11 stock firmware.
fastboot flash commands pasted into a terminal
Click to expand...
Click to collapse
After upgrading to the bootloader from the Android 11 firmware above:
With the phone in the bootloader, connected to a PC, I ran "fastboot flash bootloader bootloader.img" for the older Android 10 bootloader.img. The Android 11 bootloader refused to allow the downgrade, producing a flashing error. This may explain why you saw the error about failing to flash a single partition when attempting rollback to Android 10 firmware after installing Android 11 firmware.
Bootlooping ensues when mixing old and new among some of these: partition bootloader radio bluetooth dsp logo.
Click to expand...
Click to collapse
Bootlooping is endless rebooting like you described. It happened on a family member's Moto G Power when I tried to mix the Android 11 bootloader with parts of Android 10 firmware.
Don't flash TWRP, because that overwrites fastbootd. Instead, fastboot boot twrp.img from the bootloader if you need it.
Click to expand...
Click to collapse
TWRP takes the place of fastbootd with its own userspace fastboot mode. It might not work 100% as a replacement. As a recovery it's finicky with the A/B slots and installing to the inactive slot with a zipped ROM.
my heart is RACING! after 1.5 full days of many attempts to downgrade from A11 to A10 FASTBOOTD IS THE ANSWER omg. so, I used Motorola-XML-To-Batch-Script-master with stock firmware XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml many times from bootloader with nothing but boot loops. went into fastbootd just for the hell of it and ran the bat. BOOM! back to stock 10! will update if flashing roms works soon. Woo!!! I am in tears x'D
EXCELLENT news. I will try your steps above. However, if I recall correctly from my previous attempts, I was unable to get into fastbootd. I'll try again.
danrex said:
What I discovered after upgrading to XT2041-4_SOFIA_RETUS_11_RPMS31.Q1-54-13-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC with fastboot flash commands pasted into a terminal:
The bootloader can't be downgraded. Bootlooping ensues when mixing old and new among some of these: partition bootloader radio bluetooth dsp logo. I flashed 11 firmware of all of those, then successfully installed LineageOS with image flashing in fastbootd (boot system vbmeta product).
Don't flash TWRP, because that overwrites fastbootd. Instead, fastboot boot twrp.img from the bootloader if you need it.
Click to expand...
Click to collapse
Hi danrex,
How did you boot into fastbood?
What does this mean, "(boot system vbmeta product)"?
I finally downgraded back to A10. Like auhsoj200 above, I'm excited.
What prevented me from success for two months was getting into fastbootd. No matter what I tried I could not get into it. Turns out, in order to execute the command "adb reboot fastboot" the phone cannot be in recovery mode. It has to be on, in normal operational mode. Who knew? Most of you I'm sure. I did not.
At any rate, I may write a detail HOWTO as I have to repeat the steps for my wife's Moto G Power 2020.
Wonderful news!
I'm thinking about doing this as well because I didn't even know about the whole 10 being needed to be able to flash any of the non stock roms (or any rom really). I of course thinking everything was like a normal phone, just let it run all of the dozen or so OTA updates it had available before I unlocked the BL and rooted. Bad move now I'm on the 11 firmware above and I can't flash any rom. I don't mind all that terrible much as this is my 2nd phone who's purpose serves just as a navigation device and a Viper4Android enhanced music and podcast player. My problem though is it can be quite laggy at times not really the software's fault too much it's not the world's most powerful processor and I'm running Maps doing turn by turn + Viper4Android audio processing with several of it's plugins enabled in a hot car. BUT I know from past experience with other phones the Pixel Experience rom tends to make lesser hardware devices a little more fluid in day to day use so I wanted to try it.
Anyway.... Do you guys think that's worth rolling back for? I've never done it and my fastboot knowledge is somewhat limited but I have it installed already obviously as I recently unlocked the BL and rooted via the Magisk patched boot.img method which worked and that's how I'm running mine right now.
Danng, I'm having no luck either.... I've enabled USB Debugging and OEM bootloader unlock, but when running the script I get a whole bunch of errors saying Downloads and Erase in not allowed on locked device. Tried a whole bunch of other methods with no luck either.
I'm super bummed... bought this phone specifically to root and install custom rom and turns out it came with Android 11 already on it.
Tested the auhsoj200 approach on my Moto G8 (Rav-XT2045-1), worked well so far, no bootloping error. In my case, the state of my moto is like this:
Unlocked bootloader
USB Debugging activated
I followed the steps in this tutorial (using method 1) and successfully reached the fastbootD. Then with this other tutorial I managed to get my flashfile.bat
Once your smartphone is in fastbootD, run the bat file in your computer, It doesn't take that long and within a few minutes you will have your motorola in Android 10 again
Dohva said:
Tested the auhsoj200 approach on my Moto G8 (Rav-XT2045-1), worked well so far, no bootloping error. In my case, the state of my moto is like this:
Unlocked bootloader
USB Debugging activated
I followed the steps in this tutorial (using method 1) and successfully reached the fastbootD. Then with this other tutorial I managed to get my flashfile.bat
Once your smartphone is in fastbootD, run the bat file in your computer, It doesn't take that long and within a few minutes you will have your motorola in Android 10 again
Click to expand...
Click to collapse
this fixed my bootloop, sofia
had to flash 11 first, then boot system and adb reboot fastboot to get to fastbootd and flash 10 and booted no problem
funny thing is when I was bootlooped I could get fastbootd manually through bootloader>recovery, but downgrade from there kept bootlooping.
Having some degree of success... But eventually, my device is bootlooping, and after timing out, i see:
Boot Failed
No bootable A/B Slot
So I'm assuming the partitions were done incorrectly.
It was a bit of a journey to get to this point, I'll outline my steps in greater detail for others who wish to follow. I ran into a few issues that haven't been documented yet.
I followed the two tutorials suggested by Dohva. Here are a couple extra things I had to do:
Must install Motorola USB Drivers to enable your PC to see the android device with Fastboot. (Initially, when I ran the .bat file, the terminal would perpetually say <waiting for any device>. The motorola drivers fix this)
Must unlock the motorola device, otherwise the device won't accept the flash.
Set the android USB config to picture transfer protocol (PTP) (I'm not sure if this actually helped... I tried it at some point along the way before the previous two steps. Not sure if it made a difference)
Dohva said:
I followed the steps in this tutorial (using method 1) and successfully reached the fastbootD. Then with this other tutorial I managed to get my flashfile.bat
Click to expand...
Click to collapse
I obtained the firmware from lolinet.com. I'm not sure if it's where everyone else got their firmware, but it's what I tried first. But this is the firmware that resulted in the bootlooping and Boot Failed error after the flash.
I also tried firmware from firmwaresupport.com, but I had the same outcome.
At this point I'm out of luck, and would appreciate any recommendations!
Here is the output of the flash operation.
As you can see, when it gets to "Writing partition" the bootloader responds with "No suitable package". So I imagine this is a problem...
Code:
max-sparse-size: 268435456
Finished. Total time: 0.001s
OKAY [ 0.002s]
Finished. Total time: 0.003s
Sending 'partition' (37 KB) OKAY [ 0.002s]
Writing 'partition' (bootloader) no suitable package!
FAILED (remote: '')
fastboot: error: Command failed
Sending 'bootloader' (14204 KB) OKAY [ 0.372s]
Writing 'bootloader' (bootloader) no suitable package!
FAILED (remote: '')
fastboot: error: Command failed
fastboot: error: Failed to identify current slot
Sending 'radio' (199577 KB) OKAY [ 4.803s]
Writing 'radio' (bootloader) no suitable package!
FAILED (remote: '')
fastboot: error: Command failed
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
Sending 'super' (232496 KB) OKAY [ 5.575s]
Writing 'super' OKAY [ 0.056s]
Finished. Total time: 5.640s
Sending 'super' (262140 KB) OKAY [ 6.369s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 8.602s
Sending 'super' (262140 KB) OKAY [ 6.313s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 10.216s
Sending 'super' (236804 KB) OKAY [ 5.690s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 7.258s
Sending 'super' (262140 KB) OKAY [ 6.324s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 6.337s
Sending 'super' (260592 KB) OKAY [ 6.269s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 7.549s
Sending 'super' (262140 KB) OKAY [ 6.312s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 8.200s
Sending 'super' (262140 KB) OKAY [ 6.325s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 6.377s
Sending 'super' (257980 KB) OKAY [ 6.203s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 8.881s
Sending 'super' (262140 KB) OKAY [ 6.321s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 6.355s
Sending 'super' (262140 KB) OKAY [ 6.304s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 7.508s
Sending 'super' (262140 KB) OKAY [ 6.290s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 7.486s
Sending 'super' (262140 KB) OKAY [ 6.271s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 7.472s
Sending 'super' (262140 KB) OKAY [ 6.325s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 6.346s
Sending 'super' (259316 KB) OKAY [ 6.223s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 7.437s
Sending 'super' (33112 KB) OKAY [ 0.799s]
Writing 'super' OKAY [ 0.000s]
Finished. Total time: 0.976s
Erasing 'carrier' OKAY [ 0.008s]
Finished. Total time: 0.010s
Erasing 'userdata' OKAY [ 0.180s]
Finished. Total time: 0.181s
Erasing 'metadata' OKAY [ 0.006s]
Finished. Total time: 0.007s
Erasing 'ddr' OKAY [ 0.003s]
Finished. Total time: 0.005s
fastboot: error: Failed to identify current slot
OKAY [ 0.002s]
Finished. Total time: 0.002s
-------------------------------------------------------------------------
please scroll up and check your flash for any errors
-------------------------------------------------------------------------
Press any key to continue . . .
Is there any way to get back to android 10? I have tried all the methods mentioned above but still not working.
Hey Guys i need help
I want to go back to the original OS from GrapheneOS. But whenever I want to flash the Google Stock Image via Fastboot, an error appears. The online flash tool from Google also breaks off when flashing.
Fastboot Error:
FAILED (remote: failed to flash partition (system_b))
Why did you flash a custom rom if you have no clue on what you are doing? Ask the rom developer your question.
Always research and read about what modding you are interested in.
Lesson learned!
"Biffer"??
What kind of adb tools are you using?
vandyman said:
Why did you flash a custom rom if you have no clue on what you are doing? Ask the rom developer your question.
Always research and read about what modding you are interested in.
Lesson learned!
Click to expand...
Click to collapse
The device was from ebay with custom rom installed. That's why I wanted to go back.
ExodusCrowley said:
Hey Guys i need help
I want to go back to the original OS from GrapheneOS. But whenever I want to flash the Google Stock Image via Fastboot, an error appears. The online flash tool from Google also breaks off when flashing.
Fastboot Error:
FAILED (remote: failed to flash partition (system_b))
Click to expand...
Click to collapse
Are you using the latest Platform Tools?
ExodusCrowley said:
The device was from ebay with custom rom installed. That's why I wanted to go back.
Click to expand...
Click to collapse
Ah I see.
Download the Pixel factoy image. Unzip it. Run flash-all.bat. There are a few how to guides on this. Or just follow the Google developers guide.
Android platform - tools versions 32 or 33 will work on your PC for adb/fastboot commands.
Make sure you install the official Google usb driver on your PC or the platform tools will not work right.
Lughnasadh said:
Are you using the latest Platform Tools?
Click to expand...
Click to collapse
yes
target reported max download size of 261095424 bytes
sending 'bootloader_b' (10862 KB)...
OKAY [ 0.343s]
writing 'bootloader_b'...
(bootloader) Flashing pack version slider-1.0-8062051
(bootloader) flashing platform gs101
(bootloader) Validating partition ufs
(bootloader) Validating partition ufs
(bootloader) Validating partition partition:0
(bootloader) Validating partition partition:1
(bootloader) Validating partition partition:2
(bootloader) Validating partition partition:3
(bootloader) Validating partition bl1_b
(bootloader) Validating partition pbl_b
(bootloader) Validating partition bl2_b
(bootloader) Validating partition abl_b
(bootloader) Validating partition bl31_b
(bootloader) Validating partition tzsw_b
(bootloader) Validating partition gsa_b
(bootloader) Validating partition ldfw_b
(bootloader) Flashing partition ufs
(bootloader) Flashing partition ufs
(bootloader) Flashing partition partition:0
(bootloader) Flashing partition partition:1
(bootloader) Flashing partition partition:2
(bootloader) Flashing partition partition:3
(bootloader) Flashing partition bl1_b
(bootloader) Flashing partition pbl_b
(bootloader) Flashing partition bl2_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition bl31_b
(bootloader) Flashing partition tzsw_b
(bootloader) Flashing partition gsa_b
(bootloader) Flashing partition ldfw_b
(bootloader) Loading sideload ufsfwupdate
OKAY [ 2.954s]
finished. total time: 3.298s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.018s
target reported max download size of 261095424 bytes
sending 'radio_b' (80220 KB)...
OKAY [ 3.111s]
writing 'radio_b'...
(bootloader) Flashing pack version g5123b-93368-211225-M-8029609
(bootloader) Flashing partition modem_b
OKAY [ 0.316s]
finished. total time: 3.436s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.009s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 1.270s
target reported max download size of 261095424 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (16 MB) to disk... took 0.142s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (849 MB) to disk... took 62.433s
archive does not contain 'system.sig'
extracting system_other.img (22 MB) to disk... took 0.400s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took -0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (459 MB) to disk... took 31.867s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: slider-1.0-8062051
Baseband Version.....: g5123b-93368-211225-B-8029609
Serial Number........: 1C231FDF6002U5
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.009s]
checking version-baseband...
OKAY [ 0.009s]
sending 'boot_b' (65536 KB)...
OKAY [ 1.999s]
writing 'boot_b'...
OKAY [ 0.279s]
sending 'dtbo_b' (16384 KB)...
OKAY [ 0.567s]
writing 'dtbo_b'...
OKAY [ 0.077s]
sending sparse 'system_b' 1/4 (254972 KB)...
OKAY [ 9.461s]
writing 'system_b' 1/4...
(bootloader) image size (894066688) biffer than partition size (0)
FAILED (remote: failed to flash partition (system_b))
finished. total time: 12.578s
Press any key to exit...
Click to expand...
Click to collapse
Complete flash log
Platform Tools and Android USB drivers are up to date
After flashing via Linux it worked.
ExodusCrowley said:
Complete flash log
Platform Tools and Android USB drivers are up to date
Click to expand...
Click to collapse
Something is not updated right in your Pc.
alin919 said:
Something is not updated right in your Pc.
Click to expand...
Click to collapse
I have no idea where the error was. It worked with Linux.
Hi everyone. I am trying to wipe my pixel 6, as I want to install a custom rom.
When trying to wipe, this happens.
fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: variable (partition-type:cache) not found)
erasing 'userdata'...
OKAY [ 0.191s]
erasing 'cache'...
FAILED (remote: partition not found)
finished. total time: 0.196s
When trying to flash a bootloader, It gives me this error:
sending 'bootloader' (11506 KB)...
OKAY [ 0.269s]
writing 'bootloader'...
(bootloader) Flashing pack version slider-1.2-8318357
(bootloader) flashing platform gs101
(bootloader) Validating partition ufs
(bootloader) Validating partition ufs
(bootloader) Validating partition partition:0
(bootloader) Validating partition partition:1
(bootloader) Validating partition partition:2
(bootloader) Validating partition partition:3
(bootloader) Validating partition bl1_a
(bootloader) Validating partition pbl_a
(bootloader) failed: invalid rollback counter
(bootloader) image(pbl_a): rejected, fails validation
(bootloader) failed to validate partition (pbl_a)
FAILED (remote: failed to flash partition (bootloader))
finished. total time: 0.347s
I believe these two errors are connected, but I am not sure why this is happening. I am aware google did something regarding preventing bootloader rollback with android 13, and I recall accidentally installing it OTA once and having to rollback to 12.
You flashed Android 13 at some point (the "invalid rollback counter" error). Once Android 13 is installed you cannot install older bootloaders. Period.
The other error? Raw format means no formatting at all. In essence you have a blank drive. You may want to try restoring using Google's flash tool prior to installing your chosen ROM.