Hello!
My RazrI got into a bootloop (red boot animation) without any reason (the phone worked since over a year without any tweaking around with stock firmware). I got it into fastboot and tried to flash CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml with RSD but at command 4 (reboot bootloader) it failed. I also tried the MEDFIELD unbrick fix, but this didn't help also. So I executed each fastboot command from the RSD xml manually. I flashed gpt, motoboot, boot, recovery and motobp with success. But I got an error on system:
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 701911720 is not a multiple of the block size 4096
a few other lines with this block size problem then:
sending sparse 'system' (99096 KB)...
error: write_sparse_skip_chunk: don't care size 701911720 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 701911720 is not a multiple of the block size 4096
OKAY [ 9.108s]
Writing 'system'...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Fail to erase partition
FAILED (remote failure)
The same result with flashing cdrom.
Then I tried to erase the system with fastboot erase system and got the following error:
erasing 'system'...
FAILED (remote: Permission denied)
I also tried to erase the cache with the following result:
erasing 'cache'...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase cache fail
FAILED (remote failure)
My bootloader is unlocked. After getting the first time into fastboot, now the phone hangs on the "unlocked bootloader" screen for some time and the resets und loops this way.
Is there any hope to get it working again?
Thanks!
You need to use mfastboot to flash system. It won't work with fastboot.
mfastboot is a modified fastboot to work with large system files.
Sent from my XT1095 using Tapatalk
AGISCI said:
You need to use mfastboot to flash system. It won't work with fastboot.
mfastboot is a modified fastboot to work with large system files.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Thank You for the tip. Sadly, mfastboot didn't help either. I got the following result:
Multi-Flash is enabled!
sending 'system' (102400 KB)...
OKAY [ 9.850s]
writing 'system'...
OKAY [ 0.435s]
sending 'system' (102400 KB)...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Failed to erase partition
(bootloader) Failed to write mmc
OKAY [ 10.990s]
writing 'system'...
FAILED (remote failure)
sultan70 said:
Thank You for the tip. Sadly, mfastboot didn't help either. I got the following result:
Multi-Flash is enabled!
sending 'system' (102400 KB)...
OKAY [ 9.850s]
writing 'system'...
OKAY [ 0.435s]
sending 'system' (102400 KB)...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Failed to erase partition
(bootloader) Failed to write mmc
OKAY [ 10.990s]
writing 'system'...
FAILED (remote failure)
Click to expand...
Click to collapse
U got most likely a emmc error. Can't be fixed till this date or I don't know anyone that has fixed this problem.
All Razr I's have this. Some have just luke that they will never encounter this.
D:\platform-tools>fastboot erase userdata
******** Did you mean to fastboot format this ext4 partition?
Erasing 'userdata' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
D:\platform-tools>fastboot flash boot boot.img
Sending 'boot' (12392 KB) OKAY [ 0.297s]
Writing 'boot' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
D:\platform-tools>fastboot flash cache vendor.img
Sending 'cache' (36012 KB) OKAY [ 0.819s]
Writing 'cache' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
D:\platform-tools>fastboot flash system system.img
Sending sparse 'system' 1/5 (257072 KB) OKAY [ 5.833s]
Writing 'system' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Hello everyone,
First of all, excuse my poor english. I'm going directly to the point: I've tried to flash the google GSI+GMS ("https://developer.android.com/topic/generic-system-image/releases"). Flashing vbmeta goes fine but, when I try to flash the system.img I receibe next message: "Invalind sparse image".
I've investigated and I found that the image is a raw image so I've converted to sparse image using "img2simg <input original image> <output sparse image>".
When I flashed the new sparse image everything looks fine (no sparse error and starts to copy first block) but flashing fails after a few seconds.
Here you can find the error messages:
For image in gsi+gms zip:
./Android/Sdk/platform-tools/fastboot flash system Descargas/gsi_gms_arm64-QP1A.190771.020-5800535/system.img
Invalid sparse file format at header magic
For sparsed image:
./Android/Sdk/platform-tools/fastboot flash system system.img
Sending sparse 'system' 1/5 (488281 KB) OKAY [ 28.073s]
Writing 'system' OKAY [ 0.001s]
Sending sparse 'system' 2/5 (488281 KB) FAILED (remote: 'Error: Last flash failed : Invalid Parameter')
fastboot: error: Command failed
Anyone can help me? thanks a lot!
{
"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.
Hi All,
The issue i am encountering (with my mi a2 ) is the following:
Start: All was working, and i did a restart of the phone;
Effect: The phone did not start up any more and kept hanging on -android one- splash
Analysis: I can still start the phone in fastboot mode, and can still connect with ADB and fastboot
(this is correctly installed and working with my other M2 phones.. also cables are correct and using usb 2 etc..)
Problem: When flashing, every second flash command seems to fail:
example log:
E:\platform-tools>fastboot flash storsec storsec.mbn
Sending 'storsec' (48 KB) OKAY [ 0.011s]
Writing 'storsec' OKAY [ 0.001s]
Finished. Total time: 0.020s
E:\platform-tools>fastboot flash mdtpsecapp_b mdtpsecapp.img
Sending 'mdtpsecapp_b' (1057 KB) FAILED (remote: 'Error flashing partition.')
fastboot: error: Command failed
E:\platform-tools>fastboot flash mdtpsecapp_b mdtpsecapp.img
Sending 'mdtpsecapp_b' (1057 KB) OKAY [ 0.026s]
Writing 'mdtpsecapp_b' OKAY [ 0.001s]
Finished. Total time: 0.031s
E:\platform-tools>fastboot flash mdtpsecapp_a mdtpsecapp.img
Sending 'mdtpsecapp_a' (1057 KB) FAILED (remote: 'Error flashing partition.')
fastboot: error: Command failed
E:\platform-tools>fastboot flash mdtpsecapp_a mdtpsecapp.img
Sending 'mdtpsecapp_a' (1057 KB) OKAY [ 0.035s]
Writing 'mdtpsecapp_a' OKAY [ 0.000s]
Finished. Total time: 0.040s
In theory just repeating the flash commands will get it done; HOWEVER some flashes have bigger images like system
E:\platform-tools>fastboot flash system_a system.img
Sending sparse 'system_a' 1/6 (516064 KB) FAILED (remote: 'Error flashing partition.')
fastboot: error: Command failed
E:\platform-tools>fastboot flash system_a system.img
Sending sparse 'system_a' 1/6 (516064 KB) OKAY [ 11.452s]
Writing 'system_a' OKAY [ 0.000s]
Sending sparse 'system_a' 2/6 (514680 KB) FAILED (remote: 'Error flashing partition.')
fastboot: error: Command failed
After the first flashed chunk the second part fails and the link between phone and pc hangs; I need to reboot the phone in fastboot again to get control again;
(sadly i cannot directly flash part 2of 6 since its one command)
------------------------------------------
Additional findings:
When i try to boot the twrp image for my phone (below latest version)
E:\platform-tools>fastboot boot twrp-3.7.0_9-0-jasmine_sprout.img
Sending 'boot.img' (32164 KB) OKAY [ 0.738s]
Booting OKAY [ 10.315s]
Finished. Total time: 11.079s
The flash goes well (because its the first flash command) and the phone restarts to boot;
Sometimes it actually boots in the twrp menu but 98% of the times it hangs on the twrp splash screen
Additional findings:
I read something about encryption etc so i tried to wipe stuff (with wipe command)
This always seem to result in a hang on erasing cache
(COULD BE that cache is not used or available in Mi a2??)
E:\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 0.053s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 12285943 4k blocks and 3072000 inodes
Filesystem UUID: 50443726-8896-11ed-ab67-67ab2caed3b8
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (260 KB) OKAY [ 0.008s]
Writing 'userdata' OKAY [ 0.001s]
Erasing 'cache' ^C
------------------------------------
ALL in all i cannot get my phone to work anymore since flashing seems to hang every second flash command
This also means i cannot get a working stable STOCK rom put back on my phone;
Does anybody have some ideas or tips on how to fix this?
Personally i think there is something wrong with the memory disk inside the phone? Corrupted? Bad sectors?
Maybe i should look in the direction of formatting something?
All input / help will be appreciated;
Regards
Tom
I assume phone is fully unlocked. Otherwise search for Test-Point / EDL guide.
> When flashing, every second flash command seems to fail
- Try to use another USB 2.x slot, for example in an external USB hub (most modern monitors have one built-in). Note that USB3.x slots are not fully supported with MiA2 drivers.
- Maybe update fastboot.exe with latest platform tools (https://developer.android.com/studio/releases/platform-tools)
- Recheck installed Win64 USB drivers with USBDeview (http://www.nirsoft.net/utils/usb_devices_view.html)
> Sometimes it actually boots in the twrp menu but 98% of the times it hangs on the twrp splash screen
- "Official" TWRP is buggy,
- use the working one by @Nebrassy
[RECOVERY] [UNOFFICIAL] TeamWin Recovery Project
#include /* * Your warranty is now void. * * We are not responsible for bricked devices, dead SD cards, * thermonuclear war or you getting fired because the alarm app failed. Please * do some research if you have any concerns...
forum.xda-developers.com
Downloads for : Xiaomi Mi A2 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
> cache is not used or available in Mi a2
I believe so, yet "fastboot -w" used to work for everybody ... or RAM went south
Have you tried to switch A/B slots to previously installed ROM in TWRP or fastboot?