Related
Okay, I had a perfectly working Moto X4 (Indian Retail version), rooted and debloated. But then the idea of going back to unrooted struck me and I flashed the ROM with no problem. Then, I went back to the Bootloader (Had USB Debugging turned on and OEM Unlock "NOT" turned on in the Developer Options) and locked the bootloader by running oem lock and then, the Phone won't boot -
It gave me the message --
" Your Device is Corrupt. It can't be trusted and will not boot."
From then, I've tried reflashing the firmware - No luck.
It gives a "Permission denied" message in cmd and fails.
Unlocking the OEM worked with the get_unlock_data but then it asked me to turn on USB debugging in the developer options (and I can' boot the phone past the message).
I've tried booting into recovery, won't work - just the same message. Tried booting into the bootable TWRP - Won't work. Same message.
Fastboot erase cache erases the cache and won't do anything else.
PLEASE HELP ME. PLEASE....
The CMD error log reads as -->
Code:
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot devices
ZY224JGPK4 fastboot
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (37 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.115s]
finished. total time: 0.123s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash bootloader bootloa
der.img
target reported max download size of 536870912 bytes
sending 'bootloader' (9520 KB)...
OKAY [ 0.237s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.344s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash modem NON-HLOS.bin
target didn't report max-download-size
sending 'modem' (95999 KB)...
FAILED (command write failed (No error))
finished. total time: 0.010s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash fsg fsg.mbn
target didn't report max-download-size
sending 'fsg' (5508 KB)...
FAILED (command write failed (No error))
finished. total time: 0.008s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot erase modemst1
erasing 'modemst1'...
FAILED (command write failed (No error))
finished. total time: 0.003s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot erase modemst2
erasing 'modemst2'...
FAILED (command write failed (No error))
finished. total time: 0.002s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash bluetooth BTFM.bin
target didn't report max-download-size
sending 'bluetooth' (4540 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash dsp dspso.bin
target didn't report max-download-size
sending 'dsp' (16384 KB)...
FAILED (command write failed (No error))
finished. total time: 0.002s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash logo logo.bin
target didn't report max-download-size
sending 'logo' (2153 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash boot boot.img
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'boot_a' (19853 KB)...
OKAY [ 0.438s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.453s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_a' (516148 KB)...
OKAY [ 11.396s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 11.400s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_a' (522692 KB)...
OKAY [ 15.666s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.671s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system_a' (521055 KB)...
OKAY [ 15.620s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.626s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system_a' (523959 KB)...
OKAY [ 15.885s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.893s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system_a' (521817 KB)...
OKAY [ 16.218s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 16.226s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system_a' (522195 KB)...
OKAY [ 16.019s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 16.026s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.6
target reported max download size of 536870912 bytes
sending 'system_a' (524276 KB)...
OKAY [ 16.235s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 16.242s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.7
target reported max download size of 536870912 bytes
sending 'system_a' (167142 KB)...
OKAY [ 3.634s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 3.644s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system_b system_ot
her.img
target reported max download size of 536870912 bytes
sending 'system_b' (134369 KB)...
OKAY [ 2.931s]
writing 'system_b'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 2.942s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem_a' (237897 KB)...
OKAY [ 5.203s]
writing 'oem_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 5.209s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot erase carrier
erasing 'carrier'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot erase userdata
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot erase ddr
erasing 'ddr'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.016s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>
At the time of posting there are only stock images available for the Retail US version of the X4. The only way to get back is to have backed up your original rom and also have "OEM Unlock" enabled in dev settings. Try contacting Lenovo and tell them your issue. They may be able to assist you by providing a stock firmware image or by having you send in your device for service.
Hi, i have just made the exact mistake you did. Did you manage to find a way to fix this?
FIX
For anyone that does get this issue i have managed to find a fix.
If you are unable to flash the official firmware (7.1.1/8.0) with locked boot loader then with fastboot enter "fastboot boot boot.img", this worked for me and i was able to get into android and enable OEM unlock to unlock the bootloader and then flash the official firmware.
I couldn't fix it. And the service center is not providing warranty since I've unlocked the bootloader and they're saying it's irreparable and asking me to change the whole motherboard of a 1 month old handset. I'll be bringing the phone back from service center tomorrow and will be trying this method
bot_rosco said:
For anyone that does get this issue i have managed to find a fix.
If you are unable to flash the official firmware (7.1.1/8.0) with locked boot loader then with fastboot enter "fastboot boot boot.img", this worked for me and i was able to get into android and enable OEM unlock to unlock the bootloader and then flash the official firmware.
Click to expand...
Click to collapse
Can you PLEASE FOR the love of God elaborate,please _/|\_
achyut said:
Can you PLEASE FOR the love of God elaborate,please _/|\_
Click to expand...
Click to collapse
First try factory reset (in recovery).
Go into bootloader, use vol buttons till it says boot recovery. It should reboot and show an android on its back. Press power and vol up. Then go down to format. Select the bottom option. It should take a few seconds and select reboot and it mite work if not just follow the above guide.
If that doesnt work,
download the stock firmware (i used 7.1.1) it can be found all over xda.
Use fastboot to boot the boot image e.g.
fastboot boot boot.img
bot_rosco said:
Sure,
download the stock firmware (i used 7.1.1) it can be found all over xda.
Use fastboot to boot the boot image e.g.
fastboot boot boot.img
Click to expand...
Click to collapse
Then? Then it'll boot back normally?? Sorry,I don't have the phone with me yet (it's in service center).
achyut said:
Then? Then it'll boot back normally?? Sorry,I don't have the phone with me yet (it's in service center).
Click to expand...
Click to collapse
It should start to boot, once you have booted you setup the phone and enable oem unlock in the dev options. Go back into bootloader and unlock it with fast boot (fastboot oem unlock) and if it has already been unlocked before it should unlock. If you haven't unlocked the bootloader before, now is the time to do it. Once unlocked flash stock firmware, 7.1.1 or 8.0. good luck
bot_rosco said:
It should start to boot, once you have booted you setup the phone and enable oem unlock in the dev options. Go back into bootloader and unlock it with fast boot (fastboot oem unlock) and if it has already been unlocked before it should unlock. If you haven't unlocked the bootloader before, now is the time to do it. Once unlocked flash stock firmware, 7.1.1 or 8.0. good luck
Click to expand...
Click to collapse
am gonna try it tomorrow and if it works, you're up for a token of gratitude from my side.
bot_rosco said:
First try factory reset (in recovery).
Go into bootloader, use vol buttons till it says boot recovery. It should reboot and show an android on its back. Press power and vol up. Then go down to format. Select the bottom option. It should take a few seconds and select reboot and it mite work if not just follow the above guide.
If that doesnt work,
download the stock firmware (i used 7.1.1) it can be found all over xda.
Use fastboot to boot the boot image e.g.
fastboot boot boot.img
Click to expand...
Click to collapse
I can't boot recovery though, shows the same message
achyut said:
am gonna try it tomorrow and if it works, you're up for a token of gratitude from my side.
Click to expand...
Click to collapse
Good luck
---------- Post added at 03:16 PM ---------- Previous post was at 03:14 PM ----------
achyut said:
I can't boot recovery though, shows the same message
Click to expand...
Click to collapse
i had same, worth a try tho.
bot_rosco said:
Good luck
---------- Post added at 03:16 PM ---------- Previous post was at 03:14 PM ----------
i had same, worth a try tho.
Click to expand...
Click to collapse
You could try booting to the TWRP recovery, i.e. fastboot boot TWRP.img
and then wiping data from there.
jakejm79 said:
You could try booting to the TWRP recovery, i.e. fastboot boot TWRP.img
and then wiping data from there.
Click to expand...
Click to collapse
In think this depends on the firmware as oreo has encryption that does not play nice with twrp so it may not work, worth a try though.
nope. trying fastboot boot boot.img gives a <bootloader> permission denied! message and fails
achyut said:
nope. trying fastboot boot boot.img gives a <bootloader> permission denied! message and fails
Click to expand...
Click to collapse
Use mfastboot not fastboot, you'll have to add this to your tools. It's Motorola fastboot with proper permission.
bot_rosco said:
It should start to boot, once you have booted you setup the phone and enable oem unlock in the dev options. Go back into bootloader and unlock it with fast boot (fastboot oem unlock) and if it has already been unlocked before it should unlock. If you haven't unlocked the bootloader before, now is the time to do it. Once unlocked flash stock firmware, 7.1.1 or 8.0. good luck
Click to expand...
Click to collapse
QWZR said:
Use mfastboot not fastboot, you'll have to add this to your tools. It's Motorola fastboot with proper permission.
Click to expand...
Click to collapse
my computer doesn't recognize mfastboot command. previously I've flashed the ROMs with just fastboot command
achyut said:
my computer doesn't recognize mfastboot command. previously I've flashed the ROMs with just fastboot command
Click to expand...
Click to collapse
You have to download it.
https://androidfilehost.com/?fid=95916177934532795
QWZR said:
You have to download it.
https://androidfilehost.com/?fid=95916177934532795
Click to expand...
Click to collapse
okay, set up and tried flashing, not working. even RSD Lite is giving "phone failed to switch to fastboot mode" error, even though the phone is in fastboot and is recognized as fastboot devices in cmd.
am running out of options now. damn...
any help? anyone??
please....
achyut said:
okay, set up and tried flashing, not working. even RSD Lite is giving "phone failed to switch to fastboot mode" error, even though the phone is in fastboot and is recognized as fastboot devices in cmd.
am running out of options now. damn...
any help? anyone??
please....
Click to expand...
Click to collapse
Have you tried the twrp method that someone mentioned above? Other than that i cant think of anything, sorry.
i have another huawei device, but not honor play.
Now the display can't show me anything even if I press the power button.
Then i connected my phone to my computer and i found that my phone had automatically booted bootloader without showing me anything on its display
i entered fastboot flash recovery recovery.img
it said failed remote command not allowes
i entered fastboot oem relock (password)
it said OKAY
i entered fastboot oem unlock (password)
it said OKAY
i entered fastboot flah boot boot.img
it said failed remote partition length get erro
i used hisuit but it failed when flashing recovery
So i can hardly do anything
how to deal with the problem?
pls help me
thank u
Post proper log.
Bootloader lock or unlock?
It seens that you are tring to flash wrong boot.img cause it shows that length error means boot.img size is higher than the actual partion is
Can you enter erecovery??
Nwereonye said:
Can you enter erecovery??
Click to expand...
Click to collapse
No. the phone cant show me anything. if i try to turn it off, it will restart.(according to my computer)
rajit said:
Post proper log.
Bootloader lock or unlock?
It seens that you are tring to flash wrong boot.img cause it shows that length error means boot.img size is higher than the actual partion is
Click to expand...
Click to collapse
I'm busy these days. I'll post the log some days later
rajit said:
Post proper log.
Bootloader lock or unlock?
It seens that you are tring to flash wrong boot.img cause it shows that length error means boot.img size is higher than the actual partion is
Click to expand...
Click to collapse
Today I download a package for my device from Firmware finder for Huawei. Then I used Huawei Update Extractor to extract some of the files and tried to flash them to my phone. But failed.
Here's the log
PS C:\WINDOWS\system32> fastboot devices
3CG4C16817019572 fastboot
PS C:\WINDOWS\system32> fastboot flash boot C:\Users\yyche\Desktop\update\BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (15494 KB)...
OKAY [ 0.400s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.430s
PS C:\WINDOWS\system32> fastboot flash crc C:\Users\yyche\Desktop\update\CRC.img
target reported max download size of 471859200 bytes
sending 'crc' (161 KB)...
OKAY [ 0.006s]
writing 'crc'...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
PS C:\WINDOWS\system32> fastboot flash fastboot C:\Users\yyche\Desktop\update
error: cannot load 'C:\Users\yyche\Desktop\update'
PS C:\WINDOWS\system32> fastboot flash fastboot C:\Users\yyche\Desktop\update\FASTBOOT.img
target reported max download size of 471859200 bytes
sending 'fastboot' (3128 KB)...
OKAY [ 0.081s]
writing 'fastboot'...
FAILED (remote: Command not allowed)
finished. total time: 0.092s
PS C:\WINDOWS\system32> fastboot flash recovery C:\Users\yyche\Desktop\update\RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (35540 KB)...
OKAY [ 0.914s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.946s
PS C:\WINDOWS\system32> fastboot oem unlock 1**************4
...
FAILED (remote: already fastboot unlocked)
finished. total time: 0.004s
Do not flash the latest version, it seems u r tying to flash Android Pie. Try to flash Oreo (8.0) version of rom or the one that comes factory installed.
{
"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"
}
About US:
Superior OS is a AOSP based custom ROM with some minimal features to fulfill the users demands nowadays.
********************************************
UPDATES WILL BE ADDED TO THIS POST EACH MONTH AS MUCH AS POSSIBLE. CHECK FOR UPDATED LINKS! IM UPDATING THE LINKS TO THE FEB PATCH
********************************************
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
"This is a user friendly thread, all your suggestions are important to us and will be taken into consideration.."
***GAPPS ARE INCLUDED IN ROM***
HOW TO INSTALL:
1. Fastboot -w (in bootloader)
2. Flash images
- fastboot reboot fastboot
- fastboot set_active a
- fastboot flash boot boot.img
- fastboot flash system system.img
- fastboot flash product product.img
- fastboot flash vbmeta vbmeta.img
3. Reboot
AND THATS IT!
****FLASHING MICROG BUILD****
1. Flash all images (same steps above)
2. Boot into rom
3. Reboot into TWRP
4. Flash magisk
5. Flash microg.zip (included in the link provided)
6. Reboot
New Update:
- Added new thermals from Xiaomi
- Improved RAM management
- Performance Optimizations
- Added Pixel Camera blobs
- Added Miracast
Download ROM:SuperiorOS_May-patch
SuperiorOS Core Team
AOSP
Lineage OS
DirtyUnicorns
PixelExperience
AospExtended
Syberia OS
Nitrogen OS
Pixys OS
@bcrichster
@Beetle84
@asineth
@Rondeau79
@gearsofwar567
@kjjjnob
Special thanks:
@vache
Important Links
Loved the ROM? Want to help it imporove? Gift us with some credits!
Superior OS source
Device Trees: https://github.com/h0pk1do/android_device_motorola_sofiar
Vendor Trees: https://github.com/moto-sm6xxx/android_vendor_motorola_sofiar
Kernel Trees: https://github.com/Odin1101/Project-Sofia
Telegram Group
Telegram Channel
EXPERIENCING BUGS?
PLEASE LET ME KNOW!
SuperiorOS Version Name: Xcalibur
Build Type: UNOFFICIAL
Source Code: SuperiorOS
XDAevDB Information
SuperiorOS A11 sofia*/rav*, ROM for the Moto G8 Family
Contributors
Source Code: https://github.com/SuperiorOS
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2021-01-27
Last Updated 2021-03-26
sweet an android 11 rom. can you post instructions on how to flash the images? also can we get a build with gapps? I don't think twrp is useable to flash anything.
fix-this! said:
sweet an android 11 rom. can you post instructions on how to flash the images? also can we get a build with gapps? I don't think twrp is useable to flash anything.
Click to expand...
Click to collapse
i just updated the instructions and if you have the latest twrp, don't worry flashing will work
Getting an error when flashing system.img. Any ideas?
"writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)"
C:\ADB>fastboot devices
ZY22BKVPZ4 fastboot
C:\ADB>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 1.187s]
finished. total time: 1.189s
C:\ADB>fastboot flash boot f:\boot.img
target reported max download size of 805261312 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 2.028s]
writing 'boot_b'...
OKAY [ 0.566s]
finished. total time: 2.601s
C:\ADB>fastboot flash system f:\system.img
target reported max download size of 805261312 bytes
sending sparse 'system_b' 1/2 (720896 KB)...
OKAY [ 24.038s]
writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 24.056s
rpcribari said:
Getting an error when flashing system.img. Any ideas?
"writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)"
C:\ADB>fastboot devices
ZY22BKVPZ4 fastboot
C:\ADB>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 1.187s]
finished. total time: 1.189s
C:\ADB>fastboot flash boot f:\boot.img
target reported max download size of 805261312 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 2.028s]
writing 'boot_b'...
OKAY [ 0.566s]
finished. total time: 2.601s
C:\ADB>fastboot flash system f:\system.img
target reported max download size of 805261312 bytes
sending sparse 'system_b' 1/2 (720896 KB)...
OKAY [ 24.038s]
writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 24.056s
Click to expand...
Click to collapse
Okay so two things :
1. For whatever reason it's flashing to the B partition which it shouldn't.
2. You need the latest platform-tools
Before you flash again, fastboot -w and then type
Fastboot set_active a
I'll adjust that in the instructions
Getting a different error with the latest version of platform-tools.
"Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed"
C:\adb2>fastboot devices
ZY22BKVPZ4 fastboot
C:\adb2>fastboot -w
Erasing 'userdata' OKAY [ 0.042s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.010s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 0.087s
C:\adb2>fastboot set_active a
Setting current slot to 'a' OKAY [ 0.309s]
Finished. Total time: 0.315s
C:\adb2>fastboot flash boot f:\boot.img
Sending 'boot_a' (65536 KB) OKAY [ 2.013s]
Writing 'boot_a' OKAY [ 0.552s]
Finished. Total time: 2.587s
C:\adb2>fastboot flash system f:\system.img
Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed
rpcribari said:
Getting a different error with the latest version of platform-tools.
"Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed"
C:\adb2>fastboot devices
ZY22BKVPZ4 fastboot
C:\adb2>fastboot -w
Erasing 'userdata' OKAY [ 0.042s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.010s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 0.087s
C:\adb2>fastboot set_active a
Setting current slot to 'a' OKAY [ 0.309s]
Finished. Total time: 0.315s
C:\adb2>fastboot flash boot f:\boot.img
Sending 'boot_a' (65536 KB) OKAY [ 2.013s]
Writing 'boot_a' OKAY [ 0.552s]
Finished. Total time: 2.587s
C:\adb2>fastboot flash system f:\system.img
Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
Which device do you have?
rpcribari said:
Getting an error when flashing system.img. Any ideas?
"writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)"
C:\ADB>fastboot devices
ZY22BKVPZ4 fastboot
C:\ADB>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 1.187s]
finished. total time: 1.189s
C:\ADB>fastboot flash boot f:\boot.img
target reported max download size of 805261312 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 2.028s]
writing 'boot_b'...
OKAY [ 0.566s]
finished. total time: 2.601s
C:\ADB>fastboot flash system f:\system.img
target reported max download size of 805261312 bytes
sending sparse 'system_b' 1/2 (720896 KB)...
OKAY [ 24.038s]
writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 24.056s
Click to expand...
Click to collapse
XT2041-4
rpcribari said:
XT2041-4
Click to expand...
Click to collapse
We have the same exact device, where are you? Are you in bootloader? Or are you in fastbootd?
Hello gearsofwar567. in the post you mention that its possible to use the twrp to flash this? does that mean i can flash the twrp and do a backup and then go back to android 10 if i use twrp instead of flashing this directly? or does it come with some kind of recovery that can do backups?
also... i will gladly flash this and test it for you but i would like to wonder what features are software defect?
basically this is android 11 before moto released it which is fine but i am nervous about the recovery itself lol
gearsofwar567 said:
We have the same exact device, where are you? Are you in bootloader? Or are you in fastbootd?
Click to expand...
Click to collapse
Good call. I was just in the bootloader. I've now upgraded to TWRP 3.5 and found the reboot into fastboot mode and successfully flashed the system.img and remaining images. However now am getting the error:
failed to mount '/vendor' (invalid argument)
failed to mount '/product' (invalid argument)
I flashed the rom, installed twrp and installed gapps. so far it's running flawless on my device. the only concern I have is updates. when you flash twrp it seems to wipe out fastbootd. any suggestions on how to fix this?
rpcribari said:
Good call. I was just in the bootloader. I've now upgraded to TWRP 3.5 and found the reboot into fastboot mode and successfully flashed the system.img and remaining images. However now am getting the error:
failed to mount '/vendor' (invalid argument)
failed to mount '/product' (invalid argument)
Click to expand...
Click to collapse
are you in fastboot or fastbootd? you cant flash the images in standard fastboot mode for some reason.
Will this get updates? I have never used an unofficial rom before and I don't know how reliably updated they are.
fix-this! said:
are you in fastboot or fastbootd? you cant flash the images in standard fastboot mode for some reason.
Click to expand...
Click to collapse
I guess I don't understand the difference between fastboot and fastbootd. From TWRP 3.5 I'm going to Reboot then Fastboot.
bitscott84 said:
Hello gearsofwar567. in the post you mention that its possible to use the twrp to flash this? does that mean i can flash the twrp and do a backup and then go back to android 10 if i use twrp instead of flashing this directly? or does it come with some kind of recovery that can do backups?
also... i will gladly flash this and test it for you but i would like to wonder what features are software defect?
basically this is android 11 before moto released it which is fine but i am nervous about the recovery itself lol
Click to expand...
Click to collapse
So basically this:
1. You cannot flash the rom via twrp, you must flash the images per the instructions
2. No you cannot currently make backups with twrp because of dynamic partitions. Still trying to work that out
3. Software defects, that is something you would have to find out for yourself when you flash. The status of the rom said "stable"
rpcribari said:
Good call. I was just in the bootloader. I've now upgraded to TWRP 3.5 and found the reboot into fastboot mode and successfully flashed the system.img and remaining images. However now am getting the error:
failed to mount '/vendor' (invalid argument)
failed to mount '/product' (invalid argument)
Click to expand...
Click to collapse
Is it not booting?
fix-this! said:
I flashed the rom, installed twrp and installed gapps. so far it's running flawless on my device. the only concern I have is updates. when you flash twrp it seems to wipe out fastbootd. any suggestions on how to fix this?
Click to expand...
Click to collapse
Good to hear and there will be updates. In TWRP, hit the "reboot" tab and the tile That says "fastboot" is the new fastboot built into twrp
halliessed said:
Will this get updates? I have never used an unofficial rom before and I don't know how reliably updated they are.
Click to expand...
Click to collapse
You'll get updates faster than Motorola
January 5th 2021 is latest patch
gearsofwar567 said:
Is it not booting?
Click to expand...
Click to collapse
No it doesn't boot. It just keeps rebooting back to the bootloader.
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 4.615s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Device Error)
finished. total time: 4.615s
Stuck in FASTBOOT ...
Flash fastboot ROM
Setting current slot to 'a' OKAY [ 12.421s]
Finished. Total time: 12.517s
Rebooting OKAY [ 0.098s]
Finished. Total time: 3.115s
Rebooting, then back to FASTBOOT
Solved!!
I got help from Xiaomi support
Helen17 said:
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 4.615s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Device Error)
finished. total time: 4.615s
Stuck in FASTBOOT ...
Click to expand...
Click to collapse
i had the exact same problem, but someone on the site has solved the problem and repaired my phone on distance but against fee, if you want i can send you the link for him.
Helen17 said:
Solved!!
I got help from Xiaomi support
Click to expand...
Click to collapse
how to solved?
My phone is no flash,no root, no USB debugging. Can't boot after OTA update today, stuck at Fastboot Mode, can't start. the error message is "failed to load/verify boot images"
I download Redfin from Factory Images for Nexus and Pixel Devices, run flash-all.bat, error message:
Code:
Sending 'bootloader_a' (8762 KB) OKAY [ 0.328s]
Writing 'bootloader_a' FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.048s]
Finished. Total time: 0.051s
Sending 'radio_a' (149796 KB) OKAY [ 3.886s]
Writing 'radio_a' FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.050s
--------------------------------------------
Bootloader Version...: r3-0.4-8351081
Baseband Version.....: g7250-00202-220422-B-8489468
Serial Number........: 09
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.169s]
Checking 'version-bootloader' OKAY [ 0.178s]
Checking 'version-baseband' OKAY [ 0.139s]
Setting current slot to 'a' FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
Press any key to exit...
I run:
[ICODE]# fastboot flashing unlock
FAILED (remote: 'Error getting device locked state Not Ready')
fastboot: error: Command failed[/ICODE]
fastboot boot boot.img
Sending 'boot.img' (98304 KB) OKAY [ 2.400s]
Booting FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
fastboot devices
09aaaaaaaaaa fastboot
please help me
Have you tried simply re-flashing?
Sewdohe said:
Have you tried simply re-flashing?
Click to expand...
Click to collapse
yes, but it can't open, He still remains in "Fastboot Mode" and cannot be started
Barbet is Pixel 5a.
Redfin is Pixel 5
andybones said:
Barbet is Pixel 5a.
Redfin is Pixel 5
Click to expand...
Click to collapse
sorry, I look my download folder, it is "redfin-sq3a.220705.003.a1-factory-b193f96f"
Evolv X said:
sorry, I look my download folder, it is "redfin-sq3a.220705.003.a1-factory-b193f96f"
Click to expand...
Click to collapse
Did using the correct file fix your problem?
NO, and I use Google Online, Bug can't
V0latyle said:
Did using the correct file fix your problem?
Click to expand...
Click to collapse
Evolv X said:
NO, and I use Google Online, Bug can't
Click to expand...
Click to collapse
Could you be a bit more detailed? I don't understand.
Same, I don't understand. It appears you're trying to flash for the wrong phone...
If your bootloader is locked, you cannot flash anything in fastboot/bootloader.
Try sideloading the OTA again.
Getting this issue...are you able to fix it?