Database Develop

[ROM] AOSP 10 [Gcam] [Open Devices]

AOSP 10.0 for Xperia 10 II
Based on Sony Open devices project
Code:
/*
*Disclaimer
*
* Your warranty may be void.
*
* We're not responsible for bricked devices, dead OTGs or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Unlock bootloader is necessary!
Download Link: Androidfilehost
How to flash:
1. Unzip the ROM. install fastboot driver on your computer.
Then Download latest platform-tools from Google! Link
2. Phone enters fastboot mode. Then run:
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
4. Download OEM image from Sony dev world
For AOSP 10 you need to download: Software binaries for AOSP Android 10.0 – Kernel 4.14 – Seine (latest)
5. Unzip OEM image then run:
Code:
fastboot flash oem_a <Your-Path-of-OEM-Image.img-Edit this>
fastboot flash oem_b <Your-Path-of-OEM-Image.img-Edit this>
6. Hold power key + volume down, you will boot into recovery. Choose Wipe data/factory reset to reset your phone.
7. Choose enter fastboot, you need to install fastbootd Drivers, follow this please Link
Then run :
Code:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
8. Reboot and Enjoy
Gcam You could use this one.
Recovery for flashing Gapps: Link
TWRP A broken one: twrp-20201115-SODP.zip
Kernel source : sonyxperiadev
Other source : sonyxperiadev

Bug:
Front cam
Ugly Search box?
Disable search app, it will disappear.

Reserved

Thanks for manual.
I get to point number 7, but then writes it to me
"Sending sparse 'system' 1/2 (785636 KB) OKAY [19.208s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed"
Where is mistake?

Thapsus-cz said:
Thanks for manual.
I get to point number 7, but then writes it to me
"Sending sparse 'system' 1/2 (785636 KB) OKAY [19.208s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed"
Where is mistake?
Click to expand...
Click to collapse
Read guidance carefully please:
6. Hold power key + volume down, you will boot into recovery. Choose Wipe data/factory reset to reset your phone.
7. Choose enter fastboot, then run :
Click to expand...
Click to collapse

woooow finally : ) you are like a god. i was about to sell my phone, it's been collecting dust since i bought it.

About GCAM app, link expired, could you please update? Because I don't know which version I should download

Meloferz said:
About GCAM app, link expired, could you please update? Because I don't know which version I should download
Click to expand...
Click to collapse
https://www.celsoazevedo.com/files/android/google-camera/f/changelog1483/

Sjll said:
Read guidance carefully please:
Click to expand...
Click to collapse
Thank you for the advice. if i put enter fastboot, then i can't put in adb command. <waiting for any device>

Thapsus-cz said:
Thank you for the advice. if i put enter fastboot, then i can't put in adb command. <waiting for any device>
Click to expand...
Click to collapse
Sorry, I forgot you are using Windows, not Linux.
Drivers：
https://c.mi.com/oc/thread-3312019-1-0.html

Sjll said:
Sorry, I forgot you are using Windows, not Linux.
Drivers：
https://c.mi.com/oc/thread-3312019-1-0.html
Click to expand...
Click to collapse
I also have Linux, I'll try it there. Thanks

Hi,
can you also provide a rom without gapps?
Regards

[ROM][ResurrectionRemix 8.6.x][RAV*/SOFIA*][UNOFFICIAL][NO GAPPS]

{
"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"
}
Resurrection Remix Q
Code:
[SIZE="4"]/*
* Your warranty is now void.
*
* I am 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 about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/SIZE]
​Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome ​
combination of performance, customization, power and the most new features, brought directly to your Device.​
​
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!​
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.​
​
​
Install the stock recovery.img if you have previously installed twrp.
1. Extract the zip to your adb/fastboot directory, reboot to bootloader and open a CMD window.
2. Reboot your device into fastbootd mode.
Code:
fastboot reboot fastboot
3. Flash boot, system, product, and vbmeta images.
Code:
[/B][/B][/CENTER]
[B][CENTER]fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
​
4. Wipe userdata.
Code:
fastboot -w
5. Reboot, Profit.
(OPTIONAL)
6. If you want to install TWRP/gapps/magisk, do so after you continue through the installation steps to the home screen.
If you have the Moto G8/G Fast and your display cutout is not right, enable the overlay via ADB:
Code:
adb shell cmd overlay enable org.omnirom.overlay.moto.rav
ROM Download
GApps
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
AICP
Crdroid
AOSIP
DU
Xtended
Evolution X
Bliss
Omni Team
And Of Course To All The Supporters, Donators And Users
Join our Telegram channel : https://t.me/resurrectionremixchat
1. Starting screen casting/mirroring causes a reboot.
2. The in-built screen recorder also causes a reboot when started.
Dodgy Screen Recorder Fix :laugh:: Download and install the attached apk below, change the quick setting tile to the new one at the bottom of the list, and you should be able to record. (Its the screen recorder app from BlissRom, nothing malicious )
3. Let me know :good:
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.
​

To update to the latest version without wiping:
UPDATING FOR GAPPS/MAGISK USERS
1. Install the images as usual in fastbootd
2. Power off and boot to TWRP
3. Install GAPPS and/or Magisk
4. Reboot, profit.
UPDATING FOR NON GAPPS/Magisk USERS
Skip steps 2. and 3. from above.

Cant figure out which drive i uploaded the old files to at the moment
But heres the 8.6.9 May security patch update.
Not much new, added a KCAL enabled kernel as default, and added a color control app (root needed), fixed face unlock (g power) and added the moto clock widgets.
RR - May Patch - Google Drive
drive.google.com
TWRP zip and fastboot d images, no gapps only. Theres also some flame gapps in the folder too that i use and work well.

I can't install this ROM. It gives me the following error when flashing in fastbootd:
Code:
C:\adb>fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.002s
C:\adb>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.005s]
< waiting for any device >
Finished. Total time: 18.053s
C:\adb>fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 1.486s]
Writing 'boot_a' OKAY [ 0.406s]
Finished. Total time: 1.955s
C:\adb>fastboot flash system system.img
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
I've checked everything and I've got enough space on the HDD. What could be happening?

NeoSDAP said:
I can't install this ROM. It gives me the following error when flashing in fastbootd:
Code:
C:\adb>fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.002s
C:\adb>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.005s]
< waiting for any device >
Finished. Total time: 18.053s
C:\adb>fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 1.486s]
Writing 'boot_a' OKAY [ 0.406s]
Finished. Total time: 1.955s
C:\adb>fastboot flash system system.img
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
I've checked everything and I've got enough space on the HDD. What could be happening?
Click to expand...
Click to collapse
Try flashing product instead of system first.

Always appreciate the work you put in! I'm currently running the unofficial Lineage OS build, and I'm waiting to flash something new until an official ROM is released for this phone. Are you working on making any of your ROMs official? I know its a ton of work, but if nobody's planning on making anything official any time soon I may end up switching to one of your unofficial ROMs to get the latest security updates.

_huck_ said:
Always appreciate the work you put in! I'm currently running the unofficial Lineage OS build, and I'm waiting to flash something new until an official ROM is released for this phone. Are you working on making any of your ROMs official? I know its a ton of work, but if nobody's planning on making anything official any time soon I may end up switching to one of your unofficial ROMs to get the latest security updates.
Click to expand...
Click to collapse
Personally, I'm not going to make official builds, but I believe the crdroid Dev is going to try.
Not sure about the other guys/girls.

I am SO HAPPY that resurrection remix has just come out for the Moto G Power. I have been waiting!!! I just saw this today, but I can't seem to get it to work.. As seems to happen when people are trying to root the moto G power.. The touch screen will stop working.. I did get mine to root, using this page:
Messed up trying to root
i know there are other threads on this topic. But after going through them I cant find the fix. I unlocked bootloader and tried to root. Its seems to have worked, but the touchscreen no longer works. I used lmsa to download the stock rom...
forum.xda-developers.com
But I do not know how to apply the same fix after I try to install resurrection remix? I do not have touch screen working after I load.
I am using adb, not sure it twrp is available for moto g power yet, and if that would be the way to get it to work?
I'm using moto g power, sofia variant (usa).. XT2041-4

I tried again and I'm actually getting the following errors:
PS C:\adb> fastboot flash boot boot.img
target reported max download size of 805263360 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.418s]
writing 'boot'...
OKAY [ 0.821s]
finished. total time: 2.248s
PS C:\adb> fastboot flash system system.img
target reported max download size of 805263360 bytes
sending sparse 'system' (786388 KB)...
OKAY [ 18.732s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 18.749s
PS C:\adb> fastboot flash product product.img
target reported max download size of 805263360 bytes
sending 'product' (575564 KB)...
OKAY [ 12.511s]
writing 'product'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 12.539s
PS C:\adb>

@cxskate
You aren't in fastbootd. You are in fastboot mode. From the screen you are at in the above screenshot, type fastboot reboot fastboot.
You should reboot to a new screen with fastbootd in red across the top.
Flash the images there.

I'm still having a problem...
My phone does not enter into FastBootD mode... The screen on my phone doesn't change at all when I enter the command, and my computer adb window reads the following:
Please any advice? Very much appreciated.
PS C:\adb> fastboot reboot fastboot
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
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
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> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
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
PS C:\adb>

Beetle84 said:
Personally, I'm not going to make official builds, but I believe the crdroid Dev is going to try.
Not sure about the other guys/girls.
Click to expand...
Click to collapse
So, based on this I installed it last night, and so far so good! Couple little things don't quite work 100%, but its totally usable. Thanks OP!!

_huck_ said:
So, based on this I installed it last night, and so far so good! Couple little things don't quite work 100%, but its totally usable. Thanks OP!!
Click to expand...
Click to collapse
Awesome! What are the little things? I'll add to the bug list

I'm going for a Degoogled setup and this rom is the first one that worked with microg without hassles. I installed minMicrog standard and Majisk, toggled the baked in signature spoofing, and was up and running in minutes. VERY AWESOME!

Hello ! I would love to try your rom, but when trying to flash boot.img, i got this error : "FAILED (remote: Download is not allowed on locked devices)".
So i realized my bootloader was still locked.
To unlock the bootloader, i have to type "fastboot oem get_unlock_data", but it returns "FAILED (remote: Command not supported in default implementation)".
Do you have any idea how to fix this ?
Thanks

etienne_9000 said:
Hello ! I would love to try your rom, but when trying to flash boot.img, i got this error : "FAILED (remote: Download is not allowed on locked devices)".
So i realized my bootloader was still locked.
To unlock the bootloader, i have to type "fastboot oem get_unlock_data", but it returns "FAILED (remote: Command not supported in default implementation)".
Do you have any idea how to fix this ?
Thanks
Click to expand...
Click to collapse
Google 'unlock Motorola bootloader'
You need a code from Motorola.

Beetle84 said:
Google 'unlock Motorola bootloader'
You need a code from Motorola.
Click to expand...
Click to collapse
TX for answering. Thats what i did, and i was reading this official Motorola tutorial to get the code. It asks to type the command "fastboot oem get_unlock_data". So im stuck here for now...
I know this is a bit off topic, but i wonder you managed to do it somehow in order to test your build.

etienne_9000 said:
TX for answering. Thats what i did, and i was reading this official Motorola tutorial to get the code. It asks to type the command "fastboot oem get_unlock_data". So im stuck here for now...
I know this is a bit off topic, but i wonder you managed to do it somehow in order to test your build.
Click to expand...
Click to collapse
Did you tick the OEM unlock allowed option in developer settings?

Trying to figure out how to load gapps on with adb now??
I actually was finally able to enter FastBootD mode using a different method I found on youtube, but wasvstill getting errors when I tried to flash.. FAILED (remote: No such file or directory)
UPDATE I copied all the new files to the adb folder on the C: drive and i got it to work.. Got RR up and running, but still..
I'm trying to figure out how to load gapps on with adb now??
Method I used to get fastboot D:
(
),

Beetle84 said:
Did you tick the OEM unlock allowed option in developer settings?
Click to expand...
Click to collapse
Yes i did. Just tried again to "fastboot oem get_unlock_data" and still getting "FAILED (remote: Command not supported in default implementation)"

[RECOVERY][3.5.1][UNOFFICIAL] TWRP Xiaomi Mi 10 Pro [cmi]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
Code:
/*
*
* 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 about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Decryption work
- Otg work
- Vibrator
- Zip Flash
- Mtp/adb
- F2FS support
- Fastbootd
- Adb sideload
- Backup restore and image flash
Not working:
-Tell me
INSTALLATION:
1. Download the TWRP image file to your PC.
2. Put your device into fastboot.
3. Type the following command to flash the recovery:-
Code:
fastboot flash recovery "name_of_recovery.img"
4. On installation of TWRP , to boot the recovery do:-
Code:
fastboot boot "name_of_recovery.img"
The device will automatically reboot into TWRP.
5-A. You are using Xiaomi.eu Miui or custom Rom?
You can enjoy with a functional Data Decrypt
5-B You are using Miui EEA - Global -Cn or any custom rom that doesn't ship custom vbmeta.
6. Download this zip, copy by pc or using otg and flash this zip that will prevent twrp replacing.​​7. 7. Download VbMeta and flash by fastboot​​
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
​7. Reboot into twrp (Take longer Time) ​​
Code:
fastboot boot "name_of_recovery.img"
​8. Format Data and Reboot​
NOTES:
By Command fastboot boot, recovery will decrypt everytimes you need, also with Global Rom and without patched vbmeta.
Download:
TWRP
VbMeta
(Version tag will follow vendor, a lower version tag than your vendor does not mean that recovery will not work)
Donation:
PayPal: paypal.me/manuelbiancodev
Kernel Source: Prebuilt kernel extracted from https://bigota.d.miui.com/V12.2.6.0.RJBMIXM/miui_UMIGlobal_V12.2.6.0.RJBMIXM_2bd819937d_11.0.zip
Telegram Group: @MBsRoom

Can it be flashed through TWRP?

What's the preferred option - installation as a default recovery or rather booting from PC?
I ask because majority of recent recoveries tend to fall in fastboot bootloop and were not working properly with MTP nor decryption once flashed

New instructions for eea and global miui user, post updated

Firmware xiaomi.eu 21.2.24, installed recovery 3.5.0_10 (MBTWRP_12.2.5_CMI), accepts the password, decryption is successful, the system section in the recovery explorer sees but, when trying to create a backup, writes that "not all users are decrypted" and asks decrypt user XSpace (999) and enter his password. My current password is failing. If you ignore the decryption of this user, and try to continue creating the archive, the system partition is not in the backup list (although it is mounted beforehand).
What could be the problem and how to fix it?

New Release!
-Merged 3.5.1 teamwin recovery changes
-Cleaned and ordered twrp flags
-Support to system_ext ro mount
-Improvements into usb managing

manuelbianco said:
New Release!
-Merged 3.5.1 teamwin recovery changes
-Cleaned and ordered twrp flags
-Support to system_ext ro mount
-Improvements into usb managing
Click to expand...
Click to collapse
when i boot in this latest, i can't flash all custom, like hentaiOS.
When i am on 12.2.5 ( previous ) it works.
But how can i switch/flash twrp img file when i a, on your twrp?
When i choose install and use image, in wich slot is recovery?

New Release!
-Merged teamwin recovery changes
-Workaround for mtp after format data
(After format data, reboot to recovery, now mtp is working, unmount data and re-mount data or reboot to recovery to flash or manage data files)

Thanks

Gr8 work! decryption and data workarounds are working as described

Hi,
I flash my mi 10 pro with the Mi flashtool to V12.2.5.0.RJAMIXM_20210123.0000.00_11.0_global and after that I follow your description.
After:
- C:\adb>fastboot flash recovery MBTWRP_14-03-2021_CMI.img
target reported max download size of 805306368 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.890s]
writing 'recovery'...
OKAY [ 0.476s]
finished. total time: 3.367s
- install no_replace_twrp_avb2.zip under TWRP
- C:\adb>fastboot flash vbmeta vbmeta.img
target reported max download size of 805306368 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.008s]
writing 'vbmeta'...
OKAY [ 0.010s]
finished. total time: 0.018s
- fastboot boot MBTWRP_14-03-2021_CMI.img
It is not possible to mount the storage
Maybe someone have an idea?

why you trying to boot from local img in the last step?

mi 10 pro andriod11 test ok~
great work~~~thx

manuelbianco, I love you. This is awesome! Finally someone solving the TWRP problem on CMI. We should all donate money for your efforts! Any patreon or paypal link to send you a beer or dinner?​

underlines said:
manuelbianco, I love you. This is awesome! Finally someone solving the TWRP problem on CMI. We should all donate money for your efforts! Any patreon or paypal link to send you a beer or dinner?​
Click to expand...
Click to collapse
Thanks
Pay Manuel Bianco using PayPal.Me
Go to paypal.me/manuelbiancodev and type in the amount. Since it’s PayPal, it's easy and secure. Don’t have a PayPal account? No worries.
www.paypal.me

manuelbianco said:
Thanks
Pay Manuel Bianco using PayPal.Me
Go to paypal.me/manuelbiancodev and type in the amount. Since it’s PayPal, it's easy and secure. Don’t have a PayPal account? No worries.
www.paypal.me
Click to expand...
Click to collapse
I moved to Thailand and just wanted to open a Paypal account to donate to you. Turns out, Paypal isn't accepting registrations from Thailand since August 2020.

Hello, I can decrypt it directly after flashing in, but it can’t be decrypted normally after updating the flashing package. What should I do with this?

Twrp 3.5.2 Released !

manuelbianco said:
Twrp 3.5.2 Released !
Click to expand...
Click to collapse
I use 3.5.1. I updated it from with in twrp. There is no problem and no bug. But I did not see any changes. And it still opens late.
My device mi 10 pro

slawekking said:
Hi,
I flash my mi 10 pro with the Mi flashtool to V12.2.5.0.RJAMIXM_20210123.0000.00_11.0_global and after that I follow your description.
After:
- C:\adb>fastboot flash recovery MBTWRP_14-03-2021_CMI.img
target reported max download size of 805306368 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.890s]
writing 'recovery'...
OKAY [ 0.476s]
finished. total time: 3.367s
- install no_replace_twrp_avb2.zip under TWRP
- C:\adb>fastboot flash vbmeta vbmeta.img
target reported max download size of 805306368 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.008s]
writing 'vbmeta'...
OKAY [ 0.010s]
finished. total time: 0.018s
- fastboot boot MBTWRP_14-03-2021_CMI.img
It is not possible to mount the storage
Maybe someone have an idea?
Click to expand...
Click to collapse
Damn, I have the same Problem. I used a older Version and it worked to mount /Data. But sadly the /system_root is not compatible with the MIUI 12.5 EU Rom.
Dont know, maybe it's a bug in the recent Version. I get the Error "unable to mount /data/media/TWRP/.twrps", when I try to change the File Format.
But TWRP is installed on the System and I can access the folder under /data, and see the folders, but no data.

Android 13 build instructions

We are happy to announce that we now have launched AOSP build instructions for Android 13!
The Xperia Open Source Project (Xperia Open Devices) is an initiative created to guide the developers step-by-step on how to build AOSP for their unlocked Xperia devices. Our instructions will show you how to prepare your environment, how to download all the necessary tools, and how to download and configure the code before you can build AOSP images and flash them on your own device.
New AOSP build instructions for Android 13 | Developer World
developer.sony.com

I was wondering if someone has some (successfull) experience on building AOSP for Android 13 and flashing it to the Xperia 1 II?
Also the build guide mentions flashing the vendor (OEM) image to the device at step 7. This image is available for various android versions and devices, but not for Android13 (https://developer.sony.com/develop/open-devices/downloads/software-binaries). So how would this work for the EDO (1 II) where kernel 4.19 (27 July) Android12 is the latest.
Trying myself:
building was successful
1. [fixed i guess] question on what vendor image to choose; found some other answers from jerpelea that a12 can be used.
2. [fixed i guess] flashing not so much; flashing system gives the error 'No such partition.' Has to do with super partitions. Entered fastbootd with the command fastboot reboot fastboot.
3 [ fixed ] flashall from fastbootd says:
Checking 'product' FAILED
Device product is 'pdx203'.
Update requires 'XQ-AT51'.
fixed with fastboot --force flashall command.
4 [ in progress ] Xperia 1 II now boots into Android13 BUT stuck on bootanimation. Can adb in device though....things keep crashing in a loop
AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
Call to getInstalledModules before metadata loaded
any help is appreciated

[ROM] [TIRAMISU] [AOSP] [OOS12] [kebab] [lemonades] riceDroidOSS v10.2 android project [OFFICIAL]

riceDroid for OnePlus 8T|9R [kebab][lemonades]
{
"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"
}
What is riceDroid?
* Ricedroid is a FREE OPENSOURCE Android Operating System based on LineageOS and crDroid, that aims to provide necessary "ricing" aka customizations for ANDROID while being fast and stable. This operating system is highly inspired by Oxygen OS (10-11) and nothingOS, we strive to make things different but not too far from AOSP.
What is RiseUI?
* RiseUI is the name for our firmware skin/user interface.
Terminology
* The term \'rice\' is used to describe a person's unix desktop where \'ricing\' is an act where someone customizes their desktop such as the changing icons, panels or system interface.
source: https://jie-fang.github.io/blog/basics-of-ricing
Based on Android 13 | Tiramisu QPR1
What's working?
Most basic stuffs
Bugs and Issues
Please tell me with a logcat attached
Variants available
CORE build only - comes with basic gapps, no setupwizard
Device specific changes
Based on OOS 12 Firmware, Flashing OOS 12 firmware is a must before installing, boots on OOS13 firmware but touchscreen doesn't work
Shipped with OOS Camera - most features exposed working.
Shipped with Chaeyo.0 kernel - based from OOS 12 kernel source - CFS scheduler focused kernel.
Credits
LineageOS kebab team - for most of device/kernel tree changes
chandu078 - base device/vendor tree
cjh1249131356 - oneplus camera source
Notes
I will only maintain Official GMS core variant based on OOS 12 due to limited free time. Other variants will be officially maintained by sir manidreddy a.k.a Lord Itachi
If you have any type of concerns, please address it here, I'll try to accommodate as soon as I see the message.
Changelog
Source Changelog
Download link
riceDroid-13.0-202302220426-kebab-v10.2-CORE-OFFICIAL.zip
Installation Guide
Fastboot - recommended method
1. Download SDK platform tools here and follow this tutorial
2. Reboot to fastboot
3. Enter fastboot mode
4. Perform flashing commands listed on attached file: fastboot-commands
5. Enter recovery mode
6. Wipe data/cache/dalvik-cache
7. Sideload preferred zip files (magisk, gapps etc.)
8. Reboot to system
Sideload - recommended for those who were able to flash oos 12 on both A/B slots
1. fastboot flash recovery.img from firmware payload.bin
2. Reboot device into recovery mode
3. Enter ADB sideload mode
4. adb sideload ROM.zip
5.Wipe data/cache/dalvik-cache
6. Sideload preferred zip files (magisk, gapps etc.)
7. Reboot to system ​
Android OS version: 13.0.0_r30
Security patch level: February 2023
Build author/Device Maintainer: dlwlrma123
Device tree source code: https://github.com/ricedroidOSS-devices/device_oneplus_kebab
Device vendor source code: https://github.com/ricedroidOSS-devices/vendor_oneplus_kebab
Kernel source code: https://github.com/ricedroidOSS-devices/android_kernel_oneplus_sm8250
Firmware source code: https://github.com/ricedroidOSS
Firmware created by: The ricedroidOSS Team

Changelog:
01/21/23 - Filename: riceDroid-13.0-202301210506-kebab-v10.1-CORE-OFFICIAL.zip
- prevented unknown device error when performing adb sideload
- removed experimental changes from prebuilt/default kernel
- resized partitions for flashable packages support (gapps addons etc)
02/22/23 - Filename: riceDroid-13.0-202302220426-kebab-v10.2-CORE-OFFICIAL.zip
- fixed misc bug from source
- fixed dolby effects
- portrait video mode is a bit usable
- last update for kebab from me, my oneplus 9R got a vertical green line after trying OOS 13, so i will be selling the device at a low price and will shift to another device.

Wonderful to see riceDroid on 8T. I have been using it on Xiaomi 11T pro and love riceDroid.
I am currently on OOS 13 firmware on kebab. Do I have to downgrade it to OOS 12 firmware? If so, which version of the firmware?
Would this version be okay to flash riceDroid?
OP8T_DDR4_Android12_C36_IN_Firmware
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

RainGater said:
Wonderful to see riceDroid on 8T. I have been using it on Xiaomi 11T pro and love riceDroid.
I am currently on OOS 13 firmware on kebab. Do I have to downgrade it to OOS 12 firmware? If so, which version of the firmware?
Would this version be okay to flash riceDroid?
OP8T_DDR4_Android12_C36_IN_Firmware
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Hi! Downgrading to OOS 12 firmware is a must to avoid flashing related problems, about the version, i believe any version is fine.

dlwlrma123 said:
Hi! Downgrading to OOS 12 firmware is a must to avoid flashing related problems, about the version, i believe any version is fine.
Click to expand...
Click to collapse
Thanks. I don't see installation instructions as I am currently on latest Nameless A13 ROM with OOS 13 firmware.
So, basically
1. adb reboot recovery
2. sideload the OOS 12 firmware
3. sideload ROM
4. sideload Magisk 25.2
5. sideload NikGapps OMNI A13 as I need setup wizard to copy data from Google backup (NikGapps-omni-arm64-13-20230111-signed.zip)
6. wipe Data
7. reboot to system
Does it sound right?

RainGater said:
Thanks. I don't see installation instructions as I am currently on latest Nameless A13 ROM with OOS 13 firmware.
So, basically
1. adb reboot recovery
2. sideload the OOS 12 firmware
3. sideload ROM
4. sideload Magisk 25.2
5. sideload NikGapps OMNI A13 as I need setup wizard to copy data from Google backup (NikGapps-omni-arm64-13-20230111-signed.zip)
6. wipe Data
7. reboot to system
Does it sound right?
Click to expand...
Click to collapse
Oh dear, i forgot to add the installation guide, thanks for this. I'll add a guide in a few minutes. As per your installation, i believe the method is same for other roms, you may want to use fastboot method (fastboot enhanced or native fastboot) to avoid recovery installation errors

dlwlrma123 said:
Oh dear, i forgot to add the installation guide, thanks for this. I'll add a guide in a few minutes. As per your installation, i believe the method is same for other roms, you may want to use fastboot method (fastboot enhanced or native fastboot) to avoid recovery installation errors
Click to expand...
Click to collapse
I can flash nikgapps OMNI (NikGapps-omni-arm64-13-20230111-signed.zip)) along with Magisk, correct? Since you are only providing core, would it be a problem to flash OMNI?

RainGater said:
I can flash nikgapps OMNI (NikGapps-omni-arm64-13-20230111-signed.zip)) along with Magisk, correct? Since you are only providing core, would it be a problem to flash OMNI?
Click to expand...
Click to collapse
i can only recommend nikgapps addons to avoid conflict with google apps shipped with core.

dlwlrma123 said:
i can only recommend nikgapps addons to avoid conflict with google apps shipped with core.
Click to expand...
Click to collapse
Hmmm... I am not able to install setup addon (NikGapps-Addon-13-SetupWizard-20220908-signed.zip) as it's giving me this error: Skipping setupwizard due to insufficient space. Bummer!

RainGater said:
Hmmm... I am not able to install setup addon (NikGapps-Addon-13-SetupWizard-20220908-signed.zip) as it's giving me this error: Skipping setupwizard due to insufficient space. Bummer!
Click to expand...
Click to collapse
It seems like i wasn't able to setup partitions spaces for flashable zips, I will create a new build with this problem addressed, Sorry for the inconvenience..

dlwlrma123 said:
It seems like i wasn't able to setup partitions spaces for flashable zips, I will create a new build with this problem addressed, Sorry for the inconvenience..
Click to expand...
Click to collapse
I was about to flash.. should i wait for this new build ? Also the fastboot enhance link isn't working.

alp47470 said:
I was about to flash.. should i wait for this new build ? Also the fastboot enhance link isn't working.
Click to expand...
Click to collapse
Hello, fastboot enhance link updated, thanks for noticing! The current build is fine if you're just gonna flash magisk but if you are going to flash external gapps, its better to wait for the new build. Ill upload the new build after testing.

dlwlrma123 said:
Changelog:
01/21/23 - Filename: riceDroid-13.0-202301210506-kebab-v10.1-CORE-OFFICIAL.zip
- prevented unknown device error when performing adb sideload
- removed experimental changes from prebuilt/default kernel
- resized partitions for flashable packages support (gapps addons etc)
Click to expand...
Click to collapse
Fixed version has been pushed for changelogs, please refer to post#2

Nic
dlwlrma123 said:
Fixed version has been pushed for changelogs, please refer to post#2
Click to expand...
Click to collapse
Nice. Thanks for quick fixes
Can you please confirm if the build has in-built app lock ?

alp47470 said:
Nic
Nice
Can you confirm if the build has in-built app lock ?
Click to expand...
Click to collapse
Yes, it has in-built applock feature.

Thanks for this beautiful rom. After flashing i noticed that there is some dullness when seeing photos or wallpapers (like more on the darker side). Tried all display calibrations like vivid, saturated etc. Is that normal?
Flashed based on 12.c.36 using adb sideload for OnePlus 9r

dlwlrma123 said:
Fixed version has been pushed for changelogs, please refer to post#2
Click to expand...
Click to collapse
Thank you for the quick fix. BTW, will I be able to flash the full Gapps or only the add-ons?

dlwlrma123 said:
Changelog:
01/21/23 - Filename: riceDroid-13.0-202301210506-kebab-v10.1-CORE-OFFICIAL.zip
- prevented unknown device error when performing adb sideload
- removed experimental changes from prebuilt/default kernel
- resized partitions for flashable packages support (gapps addons etc)
Click to expand...
Click to collapse
I am getting the error when sideloading the ROM. Please see the attacehd image. I downloaded again and still the same error.
EDIT: Now, my partitions are corrupted and even when flashing through fastboot, I am getting partition not found errors. How do I get it working now? Only MSM or will it boot now even after the "partition not found" errors?
Code:
Sending 'boot_a' (98304 KB) OKAY [ 3.370s]
Writing 'boot_a' OKAY [ 0.384s]
Finished. Total time: 4.936s
Sending 'dtbo' (24576 KB) OKAY [ 0.896s]
Writing 'dtbo' OKAY [ 0.109s]
Finished. Total time: 1.072s
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (785977 KB) OKAY [ 28.109s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'system_ext' (388144 KB) OKAY [ 14.265s]
Writing 'system_ext' FAILED (remote: '(system_ext_a) No such partition')
fastboot: error: Command failed
Sending 'odm' (172264 KB) OKAY [ 6.317s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system' 1/2 (777676 KB) OKAY [ 28.438s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (764421 KB) OKAY [ 27.478s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.005s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.065s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.012s]
Writing 'vbmeta_system' OKAY [ 0.017s]
Finished. Total time: 0.105s
Sending 'recovery' (98304 KB) OKAY [ 3.534s]
Writing 'recovery' OKAY [ 0.339s]
Finished. Total time: 3.935s

dlwlrma123 said:
Fixed version has been pushed for changelogs, please refer to post#2
Click to expand...
Click to collapse
Now, my 8T is stuck in a current image have been destroyed and cannot boot stage. smh

RainGater said:
Now, my 8T is stuck in a current image have been destroyed and cannot boot stage. smh
Click to expand...
Click to collapse
Damm.. well do MSM i guess