Develop Bugs

[Q] Blinking Android Error Screen

I installed the new update on my rooted phone accidentally and it went into a bootloop. I went into recovery mode and clicked erase cache, but my phone died before it was done erasing. Now whenever I start my phone after the ASUS loading screen, and sleeping android with a red warning signal and the text 'ERROR' start flashing every three seconds. I can get to the bootloader screen fine, but when I click recovery mode and the phone restarts, its just shows the blinking android error screen and I can get the recovery mode option by pressing power+up.
When plugged into my computer, adb doesn't recognize a device is connected (I have all the drivers). So I'm stuck right now.
Please any help would be greatly appreciated!

Same thing happened to me, finally while in the bootloader I used fastboot to restore it, I used the big ZIP file from Asus website and did a fastboot sideload of it

fastboot?
How do I go into fastboot from bootloader?
Thanks!

You are in the bootloader, it should display "waiting for fastboot command" or something like this, in a command prompt on your PC type "fastboot devices" and your devive should appear there.

Next
Magister54 said:
You are in the bootloader, it should display "waiting for fastboot command" or something like this, in a command prompt on your PC type "fastboot devices" and your devive should appear there.
Click to expand...
Click to collapse
kk perfect it shows my device, what do I exactly type to sideload the zip? I placed the zip file in the adb folder. Do I type 'adb sideload xxx.zip' ?

argh no you can only sideload from ADB, you must go into recovery to use adb sideload, you cannot use it from fastboot
In recovery mode you have to select "apply update from ADB" first

Magister54 said:
argh no you can only sideload from ADB, you must go into recovery to use adb sideload, you cannot use it from fastboot
In recovery mode you have to select "apply update from ADB" first
Click to expand...
Click to collapse
From bootloader I go to recovery mode, it restarts goes to the error screen, but when I press power+up nothing happens. The error screen just keeps blinking. If I can just get into recovery mode ugh

G0BI said:
From bootloader I go to recovery mode, it restarts goes to the error screen, but when I press power+up nothing happens. The error screen just keeps blinking. If I can just get into recovery mode ugh
Click to expand...
Click to collapse
Ok, it took me a few minutes to get into stock recovery, too! From bootloader, boot into recovery. Wait for the "installing update" screen to turn to Android error bot. Then hold down power button and quickly press volume up and then release both buttons at the same time! If done correctly, you'll successfully boot into stock recovery. If not, keep trying! It can take a while to get the timing right. Stock recovery on this device is very annoying!

Blinking Error Screen
rlaw said:
Ok, it took me a few minutes to get into stock recovery, too! From bootloader, boot into recovery. Wait for the "installing update" screen to turn to Android error bot. Then hold down power button and quickly press volume up and then release both buttons at the same time! If done correctly, you'll successfully boot into stock recovery. If not, keep trying! It can take a while to get the timing right. Stock recovery on this device is very annoying!
Click to expand...
Click to collapse
So the blinking Error screen isn't a problem? I've gotten into stock recovery before pretty easily, but the error screen wasn't blinking when I got in.

G0BI said:
So the blinking Error screen isn't a problem? I've gotten into stock recovery before pretty easily, but the error screen wasn't blinking when I got in.
Click to expand...
Click to collapse
No, it's not a problem! I thought it was as well, no worries - easy mistake to make, especially since getting into recovery mode from that screen can be tricky!

Easy way
Works with problems regarding wipe cache sudden hang or reload and showing android robot with "error" message + no recovery options avilable.
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
get zenfone 2 into fastboot mode (volume + and power) and connect to your windows machine (usb)
install adb drivers and 15 sec package from the link
now go to c: drive and find the abd folder
in that drag fastboot and drop in command prompt *(administrator)
now type fastboot device
you sholud see a device
then type
1) fastboot erase cache
2) fastboot reload
now phone will restart and show error then remove usb cable and switch off the phone
after 10 sec turn on the phone and you will be back...
{
"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"
}

@varunanduri.......... You are a GOD! Nothing from the web helped me except this comment.

Hello.
I need your help.
I bought this phone (Asus Zenfone 2 ZE551ML 4GB/32GB 1.8Ghz) recently on online store. It is CN version but it already came with WW firmware, but not the latest (I believe it was WW 2.20.40.90 but I'm not sure).
Then I tried to update to the latest WW version 2.20.40.139 by putting firmware zip file from asus site in internal memory. The phone recognized this update and started to upgrade. When it reboot, I got an error of a blinking droid with the word "Error" below, and the phone doesn't boot anymore.
I can get to fastboot mode, but no to recovery mode. When trying to enter recovery, I got some errors (cannot mount /cache...) and it goes back to the blinking droid.
I cannot insert images and urls so the text errors include E:failed to mount /cache (Invalid Argument) various times
In fastboot mode I tried erase cache, format cache, format userdata, flashing latest WW recovery, boot, fastboot and system, but nothing resolved issue of blinking droid with error.
I tried other how to that uses a CWM recovery and I can get to that recovery, can clean and wipe, tried installing asus zip firmware from external sd (WW and CN) but without success (I believe it had CN recovery SKU but WW firmware -is this possible?). After rebooting the phone is still in the same error (blinking droid).
Here is fastboot messages (format userdata gave an error):
Code:
C:\adb>fastboot devices
F5AZFG27Z395 fastboot
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.610s]
writing 'recovery'...
OKAY [ 0.470s]
finished. total time: 1.080s
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (11870 KB)...
OKAY [ 0.610s]
writing 'boot'...
OKAY [ 0.450s]
finished. total time: 1.060s
C:\adb>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14824 KB)...
OKAY [ 0.700s]
writing 'fastboot'...
OKAY [ 0.460s]
finished. total time: 1.170s
C:\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 1.220s]
sending sparse 'system' (524056 KB)...
OKAY [ 18.310s]
writing 'system'...
OKAY [ 11.970s]
sending sparse 'system' (517822 KB)...
OKAY [ 17.540s]
writing 'system'...
OKAY [ 12.340s]
sending sparse 'system' (520627 KB)...
OKAY [ 17.560s]
writing 'system'...
OKAY [ 10.890s]
sending sparse 'system' (522703 KB)...
OKAY [ 17.630s]
writing 'system'...
OKAY [ 10.910s]
sending sparse 'system' (154528 KB)...
OKAY [ 5.450s]
writing 'system'...
OKAY [ 3.500s]
finished. total time: 127.320s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.110s
C:\adb>fastboot devices
F5AZFG27Z395 fastboot
C:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.490s]
finished. total time: 0.490s
C:\adb>fastboot format cache
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.390s]
sending 'cache' (6248 KB)...
OKAY [ 0.410s]
writing 'cache'...
OKAY [ 0.390s]
finished. total time: 1.190s
C:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.400s]
finished. total time: 0.410s
C:\adb>fastboot devices
F5AZFG27Z395 fastboot
C:\adb>fastboot format userdata
Creating filesystem with parameters:
Size: 27984359424
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6832119
Block groups: 209
Reserved block group size: 1024
Created filesystem with 11/1708784 inodes and 151285/6832119 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 4.290s]
sending 'userdata' (139033 KB)...
OKAY [ 4.600s]
writing 'userdata'...
FAILED (remote: flash_cmds error!
)
finished. total time: 9.180s
C:\adb>fastboot format cache
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.370s]
sending 'cache' (6248 KB)...
OKAY [ 0.420s]
writing 'cache'...
OKAY [ 0.380s]
finished. total time: 1.170s
C:\adb>fastboot format userdata
Creating filesystem with parameters:
Size: 27984359424
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6832119
Block groups: 209
Reserved block group size: 1024
Created filesystem with 11/1708784 inodes and 151285/6832119 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 4.050s]
sending 'userdata' (139033 KB)...
OKAY [ 4.490s]
writing 'userdata'...
FAILED (remote: flash_cmds error!
)
finished. total time: 8.840s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.108s
C:\adb>
Is there a way to get the phone working again?
Thank you very much.

After flashing the recovery image, you should be able to get into the recovery mode, and sideload the full zip file. Don't flash the system image.

KillerNo2 said:
After flashing the recovery image, you should be able to get into the recovery mode, and sideload the full zip file. Don't flash the system image.
Click to expand...
Click to collapse
Before flashing WW 2.20.40.139 recovery, boot, fastboot and system, I tried flashing only recovery, boot and fastboot from WW 2.20.40.90 but couldn't also get into recovery mode. Always the same error.
Maybe the firmware zip file I copied previously (when the phone was working) to the internal memory was somehow corrupted and it remains there?
Is there anything more I could do?
Thank you very much.

cdiogooliveira said:
Before flashing WW 2.20.40.139 recovery, boot, fastboot and system, I tried flashing only recovery, boot and fastboot from WW 2.20.40.90 but couldn't also get into recovery mode. Always the same error.
Maybe the firmware zip file I copied previously (when the phone was working) to the internal memory was somehow corrupted and it remains there?
Is there anything more I could do?
Thank you very much.
Click to expand...
Click to collapse
I think you should've updated to version .97 first. So download .97 recovery from here,and try it again.

Hello KillerNo2
Could you please share another link, because the one you posted in not working?
Thank you.

cdiogooliveira said:
Hello KillerNo2
Could you please share another link, because the one you posted in not working?
Thank you.
Click to expand...
Click to collapse
It works now.

KillerNo2 said:
It works now.
Click to expand...
Click to collapse
Hello. Recovery .97 didn't work also. It has always the blinking droid and doesn't boot.
I could run tethered (without install) TWRP recovery and tried to install full zip rom, but TWRP couldn't also access /cache partition. TWRP cannot mount cache and system partitions.
Anyone can help?
Thank you very much.

File System type RAW not supported

I have had no luck trying to use flash-all.bat when going to the Nov factory img...
everything seems to go well until the end where it says "Erase successful, but not automatically formatting. File system type raw not supported"
Any ideas here? i cannot get my P3XL to boot past bootloader...

I would hash check the factory image and/or download it again, and make sure your ADB/fastboot/platform tools are on the most current version.

MrGimpGrumble said:
I have had no luck trying to use flash-all.bat when going to the Nov factory img...
everything seems to go well until the end where it says "Erase successful, but not automatically formatting. File system type raw not supported"
Any ideas here? i cannot get my P3XL to boot past bootloader...
Click to expand...
Click to collapse
Go here [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by Homeboy76 do #4 then #8 if you want root. Also, Prerequisites has a link to download SDK Platform tools r28.0.1

fury683 said:
I would hash check the factory image and/or download it again, and make sure your ADB/fastboot/platform tools are on the most current version.
Click to expand...
Click to collapse
Yes, i meant to delete the thread, I actually checked and had to update adb etc..
Thanks!

I know, old thread, but it came up in Google so in case others are looking for an answer to this problem:
# fastboot format system
fastboot: error: Formatting is not supported for file system with type 'raw'.
Try this:
Code:
# fastboot format:ext4 system
Warning: system_a type is raw, but ext4 was requested for formatting.
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 518763 4k blocks and 129792 inodes
Filesystem UUID: 525d9f76-1882-4beb-8da0-848509af4188
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'system_a' (92 KB) OKAY [ 0.003s]
Writing 'system_a' OKAY [ 0.070s]
Finished. Total time: 0.583s

Hey! Can you please update me about solution if you get any

Um... Read my previous post carefully... It is the solution, of at least, it worked for me.

KJ7LNW said:
I know, old thread, but it came up in Google so in case others are looking for an answer to this problem:
# fastboot format system
fastboot: error: Formatting is not supported for file system with type 'raw'.
Try this:
Code:
# fastboot format:ext4 system
Warning: system_a type is raw, but ext4 was requested for formatting.
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 518763 4k blocks and 129792 inodes
Filesystem UUID: 525d9f76-1882-4beb-8da0-848509af4188
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'system_a' (92 KB) OKAY [ 0.003s]
Writing 'system_a' OKAY [ 0.070s]
Finished. Total time: 0.583s
Click to expand...
Click to collapse
When I tried this, it says FAILED (remote: Invalid partition)

[ROM][STOCK][FASTBOOT][OP7T] Stock Fastboot ROMs for OnePlus 7T

Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 7T in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus 7T to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on AFH: https://www.androidfilehost.com/?w=files&flid=300020
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7T
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (You need the latest sdk platform tools, you can find it here
Is reccomended to format data or the rom cannot boot:
Code:
fastboot -w
Others Commands to flash a fastboot rom
Code:
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash LOGO LOGO.img
fastboot flash modem modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash opproduct opproduct.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end.
These ROMs can't be used to update or downgrade your phone but just to restore your phone.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
​

Unfortunately i have not tested this fastboot rom, i did some tests with an user and nothing else, actually you can't flash from normal fastboot mode system, vendor and product images, you need to use "fastboot reboot fastboot" command to reboot in stock recovery with fastbootd enabled, after that using the fastboot commands you can flash system, vendor and product images.
If you have any problems with this fastboot rom or you see errors during the script execution, contact me

Really thanks for this.
Any update on root ?

RohanAJoshi said:
Really thanks for this.
Any update on root ?
Click to expand...
Click to collapse
Unfortunately no, i will check in the next hours, but without a tester should be not easy

mauronofrio said:
Unfortunately no, i will check in the next hours, but without a tester should be not easy
Click to expand...
Click to collapse
I have device.
I can test.
I will pm you my telegram id.
Please check.
Edit : can't pm
My telegram id
RohanAJoshi7

"This will work only if your bootloader is unlocked."
Supposed someone gets into trouble - as seen in another thread with a bricked device.
Wouldn't that happen usually if the bootloader is unlocked?
Like if someone want to do some modifications/tweaking, I believe it requuires to unlock the bootloader.
What other scenario could be happening to get into issues with and locked bootloader?
Please excuse the lack of knowledge on a/b partitions and stuff.
Thank you.

Wifi and speaker did not work anymore after messing with the magisk compatible boot image and/or update to 10.0.3. This fixed it for me, thanks!
Small note though, I was using older drivers which caused some errors while running the bat script. Namely "Flashing is not allowed for Critical Partitions" and " Failed to boot into userspace fastboot; one or more components might be unbootable". After running the 15 seconds adb installer and running the script again everything worked fine: https://forum.xda-developers.com/showthread.php?t=2588979

Rescla said:
Wifi and speaker did not work anymore after messing with the magisk compatible boot image and/or update to 10.0.3. This fixed it for me, thanks!
Small note though, I was using older drivers which caused some errors while running the bat script. Namely "Flashing is not allowed for Critical Partitions" and " Failed to boot into userspace fastboot; one or more components might be unbootable". After running the 15 seconds adb installer and running the script again everything worked fine: https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
please help me Bro My wifi is not working and if someone calls me it auto rejected all call
Do you want to wipe all the data ( Reccomended )[Y/N]?y
Erasing 'userdata' OKAY [ 0.421s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 56734085 4k blocks and 14188544 inodes
Filesystem UUID: 63051112-f179-11e9-b2d0-d132c7036180
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (5024 KB) OKAY [ 0.125s]
Writing 'userdata' OKAY [ 0.000s]
Erasing 'metadata' OKAY [ 0.016s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 1.638s
Sending 'aop' (200 KB) OKAY [ 0.016s]
Writing 'aop' OKAY [ 0.000s]
Finished. Total time: 0.031s
Sending 'bluetooth' (828 KB) OKAY [ 0.031s]
Writing 'bluetooth' OKAY [ 0.000s]
Finished. Total time: 0.078s
Sending 'boot_a' (98304 KB) OKAY [ 2.215s]
Writing 'boot_a' OKAY [ 0.421s]
Finished. Total time: 4.072s
Sending 'dsp' (65536 KB) OKAY [ 1.466s]
Writing 'dsp' OKAY [ 0.234s]
Finished. Total time: 2.496s
Sending 'cmnlib' (384 KB) OKAY [ 0.016s]
Writing 'cmnlib' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.031s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'devcfg' (52 KB) OKAY [ 0.000s]
Writing 'devcfg' FAILED (remote: 'Flashing is
not allowed for Critical Partitions

sandeep chauhan 2722 said:
please help me Bro My wifi is not working and if someone calls me it auto rejected all call
Do you want to wipe all the data ( Reccomended )[Y/N]?y
Erasing 'userdata' OKAY [ 0.421s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 56734085 4k blocks and 14188544 inodes
Filesystem UUID: 63051112-f179-11e9-b2d0-d132c7036180
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (5024 KB) OKAY [ 0.125s]
Writing 'userdata' OKAY [ 0.000s]
Erasing 'metadata' OKAY [ 0.016s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 1.638s
Sending 'aop' (200 KB) OKAY [ 0.016s]
Writing 'aop' OKAY [ 0.000s]
Finished. Total time: 0.031s
Sending 'bluetooth' (828 KB) OKAY [ 0.031s]
Writing 'bluetooth' OKAY [ 0.000s]
Finished. Total time: 0.078s
Sending 'boot_a' (98304 KB) OKAY [ 2.215s]
Writing 'boot_a' OKAY [ 0.421s]
Finished. Total time: 4.072s
Sending 'dsp' (65536 KB) OKAY [ 1.466s]
Writing 'dsp' OKAY [ 0.234s]
Finished. Total time: 2.496s
Sending 'cmnlib' (384 KB) OKAY [ 0.016s]
Writing 'cmnlib' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.031s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'devcfg' (52 KB) OKAY [ 0.000s]
Writing 'devcfg' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
Click to expand...
Click to collapse
And others partitions?

mauronofrio said:
And others partitions?
Click to expand...
Click to collapse
flashing process stop here.
i also try to flash manually but when I give 4th command to flash "fastboot flash cmnlib cmnlib.img" it gives me error now I cany use my phone no sound no wifi no calls please help me

sandeep chauhan 2722 said:
flashing process stop here.
i also try to flash manually but when I give 4th command to flash "fastboot flash cmnlib cmnlib.img" it gives me error now I cany use my phone no sound no wifi no calls please help me
Click to expand...
Click to collapse
if some partition fail is not a problem, you should wait a bit

Found Solution
I download this file from support one plus https://support.oneplus.com/app/answers/detail/a_id/4583/kw/7t and install it from as Local upgrade from system update ( While bootloader is still unlock) and after it completed I reboot my device and Volla!! It works. I was also thinking to sideload same file in case local upgrade not work.

I am getting
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (784696 KB) OKAY [ 18.274s]
Writing 'system' FAILED (remote: 'Partition not found')
ANy ideas???
I can flash other partitions though

suzook said:
I am getting
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (784696 KB) OKAY [ 18.274s]
Writing 'system' FAILED (remote: 'Partition not found')
ANy ideas???
I can flash other partitions though
Click to expand...
Click to collapse
when the device reboot itself in recovery doesn't touch it.

mauronofrio said:
when the device reboot itself in recovery doesn't touch it.
Click to expand...
Click to collapse
I just tried fastboot flash system...it wouldnt work. But what di was the flashall. Thanks

After flashing the stock rom it boots up and everything seems fine. When I try to lock the bootloader I get the "Your device is corrupt. It can´t be trusted anymore and will not boot" I've unlocked the bootloader a few times tried reflashing stock rom but everytime I lock the bootloader I get that error message. Any ideas?
***Downloaded and Installed the stock rom through the system update in settings menu. Locked the bootloader without issues afterwards***

954wrecker said:
After flashing the stock rom it boots up and everything seems fine. When I try to lock the bootloader I get the "Your device is corrupt. It can´t be trusted anymore and will not boot" I've unlocked the bootloader a few times tried reflashing stock rom but everytime I lock the bootloader I get that error message. Any ideas?
***Downloaded and Installed the stock rom through the system update in settings menu. Locked the bootloader without issues afterwards***
Click to expand...
Click to collapse
So after flashed this fastboot rom, you should local update the original .zip rom to be sure that all partitions are replaced

I am stuck on the "The boot loader is unlocked....." and i tried to flash this but i am getting too many errors and post reboot its back on the same screen. Can anybody please help me?
Creating filesystem with parameters:
Size: 232382812160
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 56734085
Block groups: 1732
Reserved block group size: 1024
Created filesystem with 11/14188544 inodes and 938604/56734085 blocks
target reported max download size of 805306368 bytes
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
erasing 'userdata'...
OKAY [ 0.688s]
sending 'userdata' (152025 KB)...
OKAY [ 3.922s]
writing 'userdata'...
OKAY [ 0.000s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 8.001s
error: cannot load 'aop.img'
error: cannot load 'bluetooth.img'
error: cannot load 'boot.img'
error: cannot load 'dsp.img'
error: cannot load 'cmnlib.img'
error: cannot load 'cmnlib64.img'
error: cannot load 'devcfg.img'
error: cannot load 'dtbo.img'
error: cannot load 'LOGO.img'
error: cannot load 'modem.img'
error: cannot load 'oem_stanvbk.img'
error: cannot load 'qupfw.img'
error: cannot load 'storsec.img'
error: cannot load 'multiimgoem.img'
error: cannot load 'hyp.img'
error: cannot load 'imagefv.img'
error: cannot load 'keymaster.img'
error: cannot load 'uefisecapp.img'
error: cannot load 'recovery.img'
fastboot: unknown option -- disable-verity
fastboot: unknown option -- disable-verity
error: cannot load 'opproduct.img'
error: cannot load 'tz.img'
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
error: cannot load 'system.img'
error: cannot load 'vendor.img'
error: cannot load 'product.img'
rebooting...

sathya said:
I am stuck on the "The boot loader is unlocked....." and i tried to flash this but i am getting too many errors and post reboot its back on the same screen. Can anybody please help me?
Creating filesystem with parameters:
Size: 232382812160
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 56734085
Block groups: 1732
Reserved block group size: 1024
Created filesystem with 11/14188544 inodes and 938604/56734085 blocks
target reported max download size of 805306368 bytes
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
erasing 'userdata'...
OKAY [ 0.688s]
sending 'userdata' (152025 KB)...
OKAY [ 3.922s]
writing 'userdata'...
OKAY [ 0.000s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 8.001s
error: cannot load 'aop.img'
error: cannot load 'bluetooth.img'
error: cannot load 'boot.img'
error: cannot load 'dsp.img'
error: cannot load 'cmnlib.img'
error: cannot load 'cmnlib64.img'
error: cannot load 'devcfg.img'
error: cannot load 'dtbo.img'
error: cannot load 'LOGO.img'
error: cannot load 'modem.img'
error: cannot load 'oem_stanvbk.img'
error: cannot load 'qupfw.img'
error: cannot load 'storsec.img'
error: cannot load 'multiimgoem.img'
error: cannot load 'hyp.img'
error: cannot load 'imagefv.img'
error: cannot load 'keymaster.img'
error: cannot load 'uefisecapp.img'
error: cannot load 'recovery.img'
fastboot: unknown option -- disable-verity
fastboot: unknown option -- disable-verity
error: cannot load 'opproduct.img'
error: cannot load 'tz.img'
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
error: cannot load 'system.img'
error: cannot load 'vendor.img'
error: cannot load 'product.img'
rebooting...
Click to expand...
Click to collapse
You should extract all the rom

soft bricked oneplus 7t
mauronofrio said:
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 7T in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus 7T to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on AFH: https://www.androidfilehost.com/?w=files&flid=300020
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7T
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (You need the latest sdk platform tools, you can find it here
Is reccomended to format data or the rom cannot boot:
Code:
fastboot -w
Others Commands to flash a fastboot rom
Code:
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash LOGO LOGO.img
fastboot flash modem modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash opproduct opproduct.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
These ROMs can't be used to update or downgrade your phone but just to restore your phone.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
​
Click to expand...
Click to collapse
Hi mauronofrio
I downloaded your version of twrp for my oneplus 7t and unlocked the bootloader in an attempt to change to Oxygen OS. Unfortunately the system, vendor and product partitions are locked and 0MB so seem to be stuck, can write to the /recovery directory but that's about it. I try to flash it but always get the mount error on those directories. I downloaded the rom in this post and extracted to a folder but not quite clear how to run the bat command.
Any clues or tips would be most appreciated. By the way I somehow deleted the recovery rom so can't even boot into Hydrogen OS anymore.
thanks
Dave

Question How to Flash Stock? I'm Currently Bricked

I tried flashing stock by running fastboot flashall on the output of the payload_dumper dump of the official firmware. Now I can't access the recovery or system, only fastboot.
Here's the output of fastboot -w:
Code:
Erasing 'userdata' OKAY [ 0.386s]
F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 464059800 (226591 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 587] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 621] Filling nat area at offset 0x01a00000
[f2fs_write_root_inode:1210] Writing root inode (hot node), 2b200 0 200 at offset 0x00176640
[f2fs_write_default_quota:1286] Writing quota data, at offset 0002b801, 0002b802
[f2fs_write_qf_inode:1377] Writing quota inode (hot node), 2b200 0 200 at offset 0x00176641
[f2fs_write_default_quota:1286] Writing quota data, at offset 0002b803, 0002b804
[f2fs_write_qf_inode:1377] Writing quota inode (hot node), 2b200 0 200 at offset 0x00176642
[f2fs_update_nat_root:1431] Writing nat root, at offset 0x00001a00
[f2fs_add_default_dentry_root:1628] Writing default dentry root, at offset 0x0002b800
Info: Overprovision ratio = 0.420%
Info: Overprovision segments = 956 (GC reserved = 484)
[f2fs_write_check_point_pack: 774] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 911] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack: 938] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack: 950] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack: 961] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack: 969] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack: 989] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1010] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1029] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1062] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.005s]
Writing 'userdata' OKAY [ 0.004s]
Erasing 'metadata' OKAY [ 5.136s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 6.587s
And here's the output of fastboot flashall:
Code:
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: 6af15dad
--------------------------------------------
android-info.txt syntax error: ECHO is on.
Setting current slot to 'a' OKAY [ 0.010s]
Sending 'boot_a' (196608 KB) OKAY [ 4.590s]
Writing 'boot_a' OKAY [ 0.540s]
Sending 'dtbo' (8192 KB) OKAY [ 0.204s]
Writing 'dtbo' OKAY [ 0.031s]
Sending 'vbmeta' (8 KB) OKAY [ 0.002s]
Writing 'vbmeta' OKAY [ 0.001s]
Sending 'vbmeta_system' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Sending 'vendor_boot' (98304 KB) OKAY [ 2.163s]
Writing 'vendor_boot' OKAY [ 0.290s]
Sending 'odm' (55656 KB) OKAY [ 1.377s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
The reason it says syntax error: ECHO is on. is because I tried to make an empty file with echo > android-info.txt. I forgot that doesn't work.

Guess I'll just send it in for a replacement.

nrmh said:
Guess I'll just send it in for a replacement.
Click to expand...
Click to collapse
fastbootd (not fastboot) your payload img or wait for MSM

Was in a similar boat, message oneplus for a remote session and they will send you the rom files and let someone fix it remotely

Steve0007 said:
fastbootd (not fastboot) your payload img or wait for MSM
Click to expand...
Click to collapse
I don't think I can get to fastbootd. Powering on with Vol Up + Down brings me to fastboot mode. Running fastboot reboot fastboot brings me straight back to fastboot mode. And running fastboot reboot recovery or powering on with Vol Down brings me to a "QUALCOMM CrashDump Mode" screen.
Do you have a rough idea of when MSM would be available?
awsan said:
Was in a similar boat, message oneplus for a remote session and they will send you the rom files and let someone fix it remotely
Click to expand...
Click to collapse
Where do I send them the message?

I'll hop in your same boat. Reached out to OnePlus 'cause I'm stuck in a fastboot loop. I'll keep you updated about what happens
UPDATE: Just got out of an online chat with a OnePlus tech support person. I walked through my fastboot loop problem. The supporter let me know my case would be escalated and said something about a remote session. They also said I'd get the files within 48hr.
UPDATE 2: This is my first phone with A/B paritions. When I hopped back to the other it's working. I don't pass SafetyNet, and we're still waiting on OP's full zip for the AA as far as I'm aware. Looks like it's time for patience to kick in.

nrmh said:
I don't think I can get to fastbootd. Powering on with Vol Up + Down brings me to fastboot mode. Running fastboot reboot fastboot brings me straight back to fastboot mode. And running fastboot reboot recovery or powering on with Vol Down brings me to a "QUALCOMM CrashDump Mode" screen.
Do you have a rough idea of when MSM would be available?
Where do I send them the message?
Click to expand...
Click to collapse
Go to support chat and ask for a remote session

Development [ROM][TIRAMISU][martini] [UNOFFICIAL] riceDroid 8.5 [AOSP][24/11/22]

{
"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"
}
riceDroid for OnePlus 9RT [martini]
What is riceDroid?
* RiceDroid is an opensource android operating system that aims to bring the necessary system modifications while being neat, stable and fast.
What is RiseUI?
* RiseUI is the name for our firmware skin/user interface.
Terminology
* The RICE in the project refers to rice(food) itself, but in a sense it is indeed the term RICING in linux.
Based on Android 13 | Tiramisu
What's working?
Wi-Fi
RIL
NFC
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
Lights
Sound/vibration
Known Issues
• You tell me
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download link: IMAGES / OTA
Spoiler: Flashing requirements (IMPORTANT)
- If you have OnePlus 9RT CN (MT2110) , You can only flash it if you converted to OOS before, Don't flash it over ColorOS 12.1
Spoiler: Flashing requirements (IMPORTANT)
- You have to be on OxygenOS 12.1 C.07 to be able to flash this rom
- Those who are on OOS13 or those who downgraded from OOS13 to OOS12 in the past:
- YOU HAVE TO INSTALL FLASH A12 ROLLBACK PACKAGE TWICE ( device needs to reboot after each flash session ), this will make sure oos13 is completely gone from your device else it will cause a brick.
- If you rollbacked before from OOS13 to OOS12.1 , Flash Rollback package once so that OOS12.1 get written in the inactive slot
Steps to properly rollback and cross-check u don't have oos13 on your inactive slots
Spoiler: Flashing instructions
Unlocked the bootloader of you device (there are pretty much guides around XDA, go give a check)
A working usb cable
A computer
platform-tools installed (v32 or above)
A backup of your data
A brain (jk, but, make sure you know what you are doing)
Let's begin
Download the Images zip
Boot into Bootloader mode (hold power + both vol until you see fastboot mode logo)
- use adb reboot bootloader from system if you cant boot manually
fastboot -w
fastboot update filename.zip
Done
Spoiler: Instructions for updating
Download OTA zip on pc
Reboot to recovery Select "Apply update" Select "Apply from ADB"
Now on you pc use command := adb sideload <drag drop file here>
It will take around 5 mins to install
Note: Dont panic if update stops installing at 47% After update is installed ,You will get a confirmation on PC Now you can reboot and enjoy your updated os
Support Group
​
Android OS version: 13.0.0
Security patch level: 05-11-2022
Build author/Device Maintainer: inferno0230
Special thanks to abhinavgupta371 for helping out
Firmware source code: https://github.com/RiceDroid
Kernel source code: https://github.com/Abhinavgupta371/kernel_oneplus_sm8350
Firmware created by: The riceDroid Team

Device Changelogs: (24/11/22)
-Fixed Face unlock
-Fixed "Long press on fingerprint sensor to unlock phone" not working
-Added More UDFPS icon

@inferno0230 Please check your PM inbox. Thank you.
-Regards: Badger50

hmm. Oneplus 9RT mt2111 here, coming from A12.1 c.07
No success with this install, Using your instructions I get:
Code:
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 470920600 (229941 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 626] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 660] Filling nat area at offset 0x01a00000
[f2fs_write_root_inode:1274] Writing root inode (hot node), 2b800 0 200 at offset 0x00178176
[f2fs_write_default_quota:1350] Writing quota data, at offset 0002be01, 0002be02
[f2fs_write_qf_inode:1407] Writing quota inode (hot node), 2b800 0 200 at offset 0x00178177
[f2fs_write_default_quota:1350] Writing quota data, at offset 0002be03, 0002be04
[f2fs_write_qf_inode:1407] Writing quota inode (hot node), 2b800 0 200 at offset 0x00178178
[f2fs_update_nat_root:1461] Writing nat root, at offset 0x00001a00
[f2fs_add_default_dentry_root:1658] Writing default dentry root, at offset 0x0002be00
Info: Overprovision ratio = 0.420%
Info: Overprovision segments = 963 (GC reserved = 484)
[f2fs_write_check_point_pack: 819] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 975] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1002] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1014] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1025] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1033] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1053] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1074] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1093] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1126] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.005s]
Writing 'userdata' OKAY [ 0.013s]
Erasing 'metadata' OKAY [ 4.919s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 4096 4k blocks and 4096 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'metadata' (44 KB) OKAY [ 0.003s]
Writing 'metadata' OKAY [ 0.006s]
Finished. Total time: 6.010s
C:\platform-tools\platform-tools>fastboot update RiceDroid-userdebug-031022.inferno0230.zip
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: 25551e57
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.004s]
Setting current slot to 'b' OKAY [ 0.009s]
extracting boot.img (192 MB) to disk... took 0.344s
archive does not contain 'boot.sig'
Sending 'boot_b' (196608 KB) OKAY [ 4.961s]
Writing 'boot_b' OKAY [ 0.408s]
archive does not contain 'init_boot.img'
extracting dtbo.img (24 MB) to disk... took 0.032s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (24576 KB) OKAY [ 0.621s]
Writing 'dtbo' OKAY [ 0.028s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta' OKAY [ 0.001s]
extracting vbmeta_system.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system' OKAY [ 0.001s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_vendor' OKAY [ 0.001s]
extracting vendor_boot.img (192 MB) to disk... took 0.247s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot' (196608 KB) OKAY [ 4.963s]
Writing 'vendor_boot' OKAY [ 0.375s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
And then it returns to AOSP recovery, I tried two types of platform tools v32 and above, no success
edit: to those that hit this error like me and want to recover, use the ColorOS to OxyOS A.07+ fastboot migration firmware on the other thread, and use install.bat/sh in bootloader fastboot
(if that doesn't work make sure you switch to slot b - this is what I had to do trying to figure that out blind - either use fastbootenhance or the boota/b switch commands to get to alternate boot partition)

hello, i would like to make roms for this phone, can you please give me the tree files? device tree kernal tree and all that? i coudln't find it anywhere onliine, thank you!!!!. Also really thanks for the rom, I'm installing rn.

strelokcyka said:
hmm. Oneplus 9RT mt2111 here, coming from A12.1 c.07
No success with this install, Using your instructions I get:
Code:
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 470920600 (229941 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 626] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 660] Filling nat area at offset 0x01a00000
[f2fs_write_root_inode:1274] Writing root inode (hot node), 2b800 0 200 at offset 0x00178176
[f2fs_write_default_quota:1350] Writing quota data, at offset 0002be01, 0002be02
[f2fs_write_qf_inode:1407] Writing quota inode (hot node), 2b800 0 200 at offset 0x00178177
[f2fs_write_default_quota:1350] Writing quota data, at offset 0002be03, 0002be04
[f2fs_write_qf_inode:1407] Writing quota inode (hot node), 2b800 0 200 at offset 0x00178178
[f2fs_update_nat_root:1461] Writing nat root, at offset 0x00001a00
[f2fs_add_default_dentry_root:1658] Writing default dentry root, at offset 0x0002be00
Info: Overprovision ratio = 0.420%
Info: Overprovision segments = 963 (GC reserved = 484)
[f2fs_write_check_point_pack: 819] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 975] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1002] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1014] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1025] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1033] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1053] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1074] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1093] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1126] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.005s]
Writing 'userdata' OKAY [ 0.013s]
Erasing 'metadata' OKAY [ 4.919s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 4096 4k blocks and 4096 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'metadata' (44 KB) OKAY [ 0.003s]
Writing 'metadata' OKAY [ 0.006s]
Finished. Total time: 6.010s
C:\platform-tools\platform-tools>fastboot update RiceDroid-userdebug-031022.inferno0230.zip
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: 25551e57
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.004s]
Setting current slot to 'b' OKAY [ 0.009s]
extracting boot.img (192 MB) to disk... took 0.344s
archive does not contain 'boot.sig'
Sending 'boot_b' (196608 KB) OKAY [ 4.961s]
Writing 'boot_b' OKAY [ 0.408s]
archive does not contain 'init_boot.img'
extracting dtbo.img (24 MB) to disk... took 0.032s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (24576 KB) OKAY [ 0.621s]
Writing 'dtbo' OKAY [ 0.028s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta' OKAY [ 0.001s]
extracting vbmeta_system.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system' OKAY [ 0.001s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_vendor' OKAY [ 0.001s]
extracting vendor_boot.img (192 MB) to disk... took 0.247s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot' (196608 KB) OKAY [ 4.963s]
Writing 'vendor_boot' OKAY [ 0.375s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
And then it returns to AOSP recovery, I tried two types of platform tools v32 and above, no success
edit: to those that hit this error like me and want to recover, use the ColorOS to OxyOS A.07+ fastboot migration firmware on the other thread, and use install.bat/sh in bootloader fastboot
(if that doesn't work make sure you switch to slot b - this is what I had to do trying to figure that out blind - either use fastbootenhance or the boota/b switch commands to get to alternate boot partition)
Click to expand...
Click to collapse
If you are able to boot into aosp recovery you can use recovery rom and sideload it
Also, were u on oos12.1 at the time of flashing rom?

inferno0230 said:
If you are able to boot into aosp recovery you can use recovery rom and sideload it
Also, were u on oos12.1 at the time of flashing rom?
Click to expand...
Click to collapse
As I said. Followed instructions and was coming from stock oos a12.1 c0.7. Only can assume the boot partition was loaded on the wrong one
(that explains the errors but I'm not game enough to try the whole process again and now I'm kind of stuck back of Android 11 due to recovering from the issue. Maybe when someone uploads a c.07 fastboit firmware I will try again but for me OTA is broken.)

this rom is actually really great. i love this rom, i just have a biit problem with the vibration sensor, its not as good as stock, bit i got like a thousand things better then the stock rom, thanks a lot man. Keep up the good work!!

strelokcyka said:
As I said. Followed instructions and was coming from stock oos a12.1 c0.7. Only can assume the boot partition was loaded on the wrong one
(that explains the errors but I'm not game enough to try the whole process again and now I'm kind of stuck back of Android 11 due to recovering from the issue. Maybe when someone uploads a c.07 fastboit firmware I will try again but for me OTA is broken.)
Click to expand...
Click to collapse
Sorry to stray once again from the rom but this will be the last post -- but its important for those who get stuck for any reason like I did
You can update from stuck OTA, using the Oxygen Updater via playstore, they supply an alternative apk link to help flash the zip without using the OOS Settings.

你好，我是来自中国的用户，在这里我的5G没办法正常使用，就算是打开了也仅仅显示4G，希望伙计可以改进一下，还有就是 更新的时候可以在这个论坛发一下吗？源锻造里看不懂，但是我是真心喜欢这个系统，比我之前用过的都简洁，好看。感谢！

How is going the battery life of this ROM?

battery life is great for me, running everything, wifi bluetooth 120 hertz, high brightness, running many apps, only daily driver, (lite) gamaing but last charge 21 hours ago, im not super heavy user, but i can last 2 days, plus charging so so fast too

How can I return to stock rom. Pls help