riceDroid for OnePlus 9 Pro [Lemonadep]
What is riceDroid?
* Ricedroid is an operating system based on lineage/crdroid, that aims to provide necessary "ricing" for android while being fast and stable.
Terminology
* The rice in the project name can be referred to "rice" (food) itself, but in a sense it is indeed the term "ricing" in linux.
Based on Android 12
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
Known issues
Nothing yet
You tell me
CORE GAPPS BUILD AVAILABLE
Download
Android OS version: 12.1.0_r7
Security patch level: 2022 06 23
Build author/Device Maintainer: Red Prez16
Device Source code: https://github.com/RedDeviceTrees
Source code: https://github.com/RiceDroid
Kernel source code: LineageOS Kernel
ROM Developer: dlwlrma123
My Telegram Group: Red's Room
downloading. will revert with feedback.
any flashing instructions. all files are included in the download zip folder i.e. rom, boot, vendor_boot and dtbo.img. thanks
vsinha71 said:
any flashing instructions. all files are included in the download zip folder i.e. rom, boot, vendor_boot and dtbo.img. thanks
Click to expand...
Click to collapse
Yes, all image files and the OTA file itself is included in one package.
This is one of the best roms which I have used. Blazing fast and feature rich. The customisation options available is by far the most in this rom. Even from the crdroid perspective. Thanks for this wonderful rom.
Just one query which gapps can I flash over the available gapps in the rom. Since this has minimal gapps I need to install quite a few more gapps which I use.
Many thanks
Please write Install instruction.
this?
- Boot to Bootloader
- Flash the boot Image
- Flash the vendor_boot Image
- Flash the dtbo Image
- Reboot to Recovery Mode
- “Apply Update” and select “Apply from ADB”
- Adb sideload riceDroid-12.1-202206230059-lemonadep-v2.5-GAPPS.zip
[email protected] said:
Please write Install instruction.
this?
- Boot to Bootloader
- Flash the boot Image
- Flash the vendor_boot Image
- Flash the dtbo Image
- Reboot to Recovery Mode
- “Apply Update” and select “Apply from ADB”
- Adb sideload riceDroid-12.1-202206230059-lemonadep-v2.5-GAPPS.zip
Click to expand...
Click to collapse
So close! First, flash the dtbo image. Than the vendor_boot image, than the boot image.
vsinha71 said:
This is one of the best roms which I have used. Blazing fast and feature rich. The customisation options available is by far the most in this rom. Even from the crdroid perspective. Thanks for this wonderful rom.
Just one query which gapps can I flash over the available gapps in the rom. Since this has minimal gapps I need to install quite a few more gapps which I use.
Many thanks
Click to expand...
Click to collapse
There wouldn't be enough space to install another Google Applications package. I just recommend downloading and installing the Google Applications you need from the Google Play Store.
Red Prez16 said:
So close! First, flash the dtbo image. Than the vendor_boot image, than the boot image.
Click to expand...
Click to collapse
I've never had a problem doing this out of order and I don't see why you would as long as you're not rebooting inbetween.
EtherealRemnant said:
I've never had a problem doing this out of order and I don't see why you would as long as you're not rebooting inbetween.
Click to expand...
Click to collapse
Fair enough. That's just what the LineageOS guide says. So that's just the way I do it.
Red Prez16 said:
Fair enough. That's just what the LineageOS guide says. So that's just the way I do it.
Click to expand...
Click to collapse
Yeah it's very strange the way that the LineageOS guide breaks things down but I suppose having one way for everyone to do things cuts down on human error along the way. I imagine a lot of us have been flashing boot first though simply because that's alphabetical order and it's both natural for our brains to work that way as well as it's also the default directory order listing for those who drag and drop.
EtherealRemnant said:
Yeah it's very strange the way that the LineageOS guide breaks things down but I suppose having one way for everyone to do things cuts down on human error along the way. I imagine a lot of us have been flashing boot first though simply because that's alphabetical order and it's both natural for our brains to work that way as well as it's also the default directory order listing for those who drag and drop.
Click to expand...
Click to collapse
Maybe, but I always have issues doing it out of order.
Red Prez16 said:
There wouldn't be enough space to install another Google Applications package. I just recommend downloading and installing the Google Applications you need from the Google Play Store.
Click to expand...
Click to collapse
ok thanks. the rom is super and running really smooth.
Hi, is this rom fixes the aosp stutter bug on this device?
vsinha71 said:
ok thanks. the rom is super and running really smooth.
Click to expand...
Click to collapse
No problem! Also, I'm glad to hear that!
Very impressive rom.smooth and snappy.nice job!!
gillim74 said:
Very impressive rom.smooth and snappy.nice job!!
Click to expand...
Click to collapse
Thank you!
vsinha71 said:
ok thanks. the rom is super and running really smooth.
Click to expand...
Click to collapse
and battery backup ?
Mayabee said:
and battery backup ?
Click to expand...
Click to collapse
so far really good. charging speed is fantastic. let me run it a few days more to be assess it correctly.
vsinha71 said:
so far really good. charging speed is fantastic. let me run it a few days more to be assess it correctly.
Click to expand...
Click to collapse
can i install it from other custom rom
Related
YuanweiOS is based Candy7(Special thanks to Candy7 team).The main aim is to make ROM smooth and to add only necessary Features. We wanted to give the users a fun, fully customizable ROM. We will keep this ROM smooth and best in performance side and minimal on features side.
YuanweiOS Github
Disclaimer: We are not responsible for bricked devices, dead SD cards, thermonuclear war, or the current economic crisis caused by you following these directions. YOU are choosing to make these modificiations, andif you point your finger at me for messing up your device, I will laugh at you.
FEATURES
Battery bar
Multi-window
Status bar customization
Advanced power menu
Buttons settings:
-Long-press/double-tap actions
-Volume rocker
Brevent
Magsik
And so on ...
Flashing Steps:
Coming from another rom
1) Download YuanweiOS.zip
2) Download OpenGapps
3) Boot into recovery (TWRP)
4) Full wipe (Dalvik Cache, Cache, System, Factory Data Reset)
5) Flash YuanweiOS.zip
6) Flash Gapps
7) Reboot
Updating from previous YuanweiOS release
1) Download YuanweiOS.zip
2) Boot into recovery
3) Flash YuanweiOS.zip
4) Reboot
Special thanks to CandyRoms, LineageOS, SlimRoms, Omni, TeslaROM, and all the rest who make their source open. We can't do this on our own.
Webside
[ROM]YuanweiOS
ROM:
[ROM]YuanweiOS-kiwi
Contributors
jsbeyond,Yihao
Source Code:
https://github.com/yuanwei-os
https://github.com/yuanwei-os/android_device_huawei_kiwi/
https://github.com/yuanwei-os/android_kernel_huawei_kiwi/
Thanks: @crpalmer @BadDaemon
ROM OS Version: 7.1.2
ROM Kernel: Linux 3.1.x
Version Information
Status:Stable
Created 2017-07-18
Last Updated 2017-07-18
Welcome back Elan.
screenshots？
screenshots？
Devil_GBY said:
screenshots？
Click to expand...
Click to collapse
screenshots click on red screenshot option
Screenshots
@jsbeyond
Thanks for the UNHOLY.
Its running good on my L22 with a few glitches.
1. Not able to install modules (Viper & Atmos) from Magisk-13.0. Modules are downloaded though but I have flash them through TWRP only.
2. Not able to update Magisk from 13.0 to 13.2.
-Tried updating it, no success.
-Tried uninstalling the older version and installing newer version thru TWRP. The newer version installs but , After boot it does not load up.
subodhverma21 said:
@jsbeyond
Thanks for the UNHOLY.
Its running good on my L22 with a few glitches.
1. Not able to install modules (Viper & Atmos) from Magisk-13.0. Modules are downloaded though but I have flash them through TWRP only.
2. Not able to update Magisk from 13.0 to 13.2.
-Tried updating it, no success.
-Tried uninstalling the older version and installing newer version thru TWRP. The newer version installs but , After boot it does not load up.
Click to expand...
Click to collapse
i have no this issue
https://plus.google.com/communities/112720517052084764225
good job，thanks !
https://t.me/yuanweios
looks good but...
unholy development seriously? that is a bad boot animation, goes against my religion, definitely changing it.
other then that, the rom looks amazing!!! this might be my daily driver from now on.
Awesome
I like your ROM and have been using it for two weeks now. How or where can i get update to this ROM?
Thanks:good:
abolatito said:
I like your ROM and have been using it for two weeks now. How or where can i get update to this ROM?
Thanks:good:
Click to expand...
Click to collapse
seems like this ROM is abandoned...
crayonicle said:
seems like this ROM is abandoned...
Click to expand...
Click to collapse
OP is busy with real life. That explains it.
itisiryan said:
OP is busy with real life. That explains it.
Click to expand...
Click to collapse
well it's been like 2 or 3 months, I expected at least 1 update in that time, oh well, this was a good ROM as it was...
crayonicle said:
well it's been like 2 or 3 months, I expected at least 1 update in that time, oh well, this was a good ROM as it was...
Click to expand...
Click to collapse
Yeah. But he didn't update his other ROMs too.
itisiryan said:
Yeah. But he didn't update his other ROMs too.
Click to expand...
Click to collapse
oh ok
crayonicle said:
oh ok
Click to expand...
Click to collapse
But you can check his AFH account every now and then. I once saw him working on O.
itisiryan said:
But you can check his AFH account every now and then. I once saw him working on O.
Click to expand...
Click to collapse
omg thx so much for telling me, gonna try the LOS 15 unofficial O hope it works !
crayonicle said:
omg thx so much for telling me, gonna try the LOS 15 unofficial O hope it works !
Click to expand...
Click to collapse
Sadly it doesn't for the moment.
Kang kernel
By Sjll
Notice: Beware of bricking device!
This a new kernel for stock 10. It's aim to optimize the kernel and provide better user experience.
I had cherry-picked some commits from other SDM845 devices like M i8 and Oneplus 6T. So it's a fusion kernel, though I don't know whether these commits could improve our performance.
I share the source codes, so you could tweak the kernel by yourself. Ok, don't forget to share your work with us.
Download: Github
Note:
1. For XZ2, boot.img already included Magisk.
2 Internal problem is normal, ignore it.
CAF Version: LA.UM.8.3.r1-07600-sdm845.0.
Linux Version:4.9.206-r25-rel
Recommand to use EX kernel Manager
Feature:
1. GPU OC to 835 Mhz.
2. Thanks: Hide unlocked state from @j4nn
3. Qcacld wlan driver.
4. Remove useless drivers.
5. zram to lz4.
6. Increase priority of RT thread.
7. AVB flag removed.
8. WireGuard support.
9. Disabled some logs in kernel.
10. Newer CAF buff and Linux version.
11. Cpufreq and drm drivers optimization.
12. Schedutil optimization.
13. Energy model improved.
14. New I/O governor (Maple & Zen)
15. Blu_schedutil CPU governor( More Powersave ) Need to enable manually
16. IOsched optimization.
17. DTS eagle driver.
18. KLAPSE Color manager. Need EX kernel Manager
19. boeffla_wl_blocker supported.
20. adrenoboost supported, disable it by default.
21. etc..
How to flash:
HTML:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
Vbmeta.img see Attach Files
If there is a dtbo.img, then:
HTML:
fastboot flash dtbo dtbo.img
I provide a new thermal configuration, see Attach Files, download it and replacing the same file in vendor/etc. You will get the full performance of SDM845.
Source code: Github
ROM OS Version: 10.0
ROM Kernel: Linux 4.9
Contributors
Sjll
Created 2020-02-26
FIRST! Muahahaha
Thank you like always.
MartinX3 said:
FIRST! Muahahaha
Thank you like always.
Click to expand...
Click to collapse
Is it possible to port it on aosp10/los17 with osmosis anykernel?
thanks! can I flash on xz2 compact h8314?
nos1609 said:
Is it possible to port it on aosp10/los17 with osmosis anykernel?
Click to expand...
Click to collapse
It's the stock kernel
Completely incompatible with the SODP project
Thank you for this! I got a slight increase in Antutu benchmark score, especially in GPU and UX tests. Hide unlock status is also working, Sony started to send me updates for system apps. Been using for an hour and it's smooth af. will update this comment if I encounter any issues or other improvements in longer term.
MartinX3 said:
FIRST! Muahahaha
Thank you like always.
Click to expand...
Click to collapse
Thank you ,too, Martin!
I build a new twrp for 10. But I stucked at TWRP logo.
ADB seems works, but no authorized.
Here is the tree.
https://github.com/sjllls/android_device_sony_akari/tree/twrp-10
nos1609 said:
Is it possible to port it on aosp10/los17 with osmosis anykernel?
Click to expand...
Click to collapse
No, this kernel is only for stock, not SODP.
nikkdib said:
thanks! can I flash on xz2 compact h8314?
Click to expand...
Click to collapse
No, you can't, but I will provide a version for xz2c after source code is updated to latest.
You could upload the boot.img of xz2c. I need it. Because I don't want to download the whole FTF firmware of XZ2c. It's too large.
Faruk.ErdaL said:
Thank you for this! I got a slight increase in Antutu benchmark score, especially in GPU and UX tests. Hide unlock status is also working, Sony started to send me updates for system apps. Been using for an hour and it's smooth af. will update this comment if I encounter any issues or other improvements in longer term.
Click to expand...
Click to collapse
Thanks, if there is any bugs, feedback to me please. I will try to solve it.
Sjll said:
Thank you ,too, Martin!
I build a new twrp for 10. But I stucked at TWRP logo.
ADB seems works, but no authorized.
Here is the tree.
https://github.com/sjllls/android_device_sony_akari/tree/twrp-10
Click to expand...
Click to collapse
Yay
Nice, I wanted to look into TWRP at weekend
You could try to set
ro.debuggable=1
ro.adb.secure=0
Or build an -eng TWRP.
Sjll said:
No, you can't, but I will provide a version for xz2c after source code is updated to latest.
You could upload the boot.img of xz2c. I need it. Because I don't want to download the whole FTF firmware of XZ2c. It's too large.
Click to expand...
Click to collapse
thanks! this is the boot image of xz2c from stock italian firmware .532 (android 10)
https://drive.google.com/open?id=1aKZiVIa6T3k7ZJ7mGWw_hWPCHkkxzRAj
nikkdib said:
thanks! this is the boot image of xz2c from stock italian firmware .532 (android 10)
https://drive.google.com/open?id=1aKZiVIa6T3k7ZJ7mGWw_hWPCHkkxzRAj
Click to expand...
Click to collapse
Done, try it and feedback, thanks.
Sjll said:
Done, try it and feedback, thanks.
Click to expand...
Click to collapse
i need to patch with magisk manager first if i want root yes?
nikkdib said:
i need to patch with magisk manager first if i want root yes?
Click to expand...
Click to collapse
Yes, you can. It should work fine with Magisk.
Sjll said:
Yes, you can. It should work fine with Magisk.
Click to expand...
Click to collapse
ok i patch with magisk and flash. for now all is fine. I will test. in next release you add more features? like more governor for cpu or undervolt?
nikkdib said:
ok i patch with magisk and flash. for now all is fine. I will test. in next release you add more features? like more governor for cpu or undervolt?
Click to expand...
Click to collapse
Done, try V1.5 please.
Does the kernel already include magisk?
Edit: V1.7 crashed device after boot, gives the warning there's an internal problem with your device then reboots.
Faruk.ErdaL said:
Does the kernel already include magisk?
Edit: V1.7 crashed device after boot, gives the warning there's an internal problem with your device then reboots.
Click to expand...
Click to collapse
After first crash files in /sys/fs/pstore giving you the crash reason
MartinX3 said:
After first crash files in /sys/fs/pstore giving you the crash reason
Click to expand...
Click to collapse
yes but it crashes when it says phone is starting... so I can't really get into my files and have to leave for university in 10 minutes, I'll give it another try in the evening and provide logs if possible
Faruk.ErdaL said:
yes but it crashes when it says phone is starting... so I can't really get into my files and have to leave for university in 10 minutes, I'll give it another try in the evening and provide logs if possible
Click to expand...
Click to collapse
After crash go into Fastboot mode and flash the working kernel back (with magisk)
Then the device boots and you get the files
Just don't boot one time too much or the pstore will be wiped.
Faruk.ErdaL said:
Does the kernel already include magisk?
Edit: V1.7 crashed device after boot, gives the warning there's an internal problem with your device then reboots.
Click to expand...
Click to collapse
For XZ2, it already included Magisk. Internal problem is normal, just ignore it. All works fine for me.
Provide your phone type please.
So today with some testers i managed to make root on OnePlus 8 Pro, I want to specify that 95% of the work was done by @topjohnwu (Magisk creator).
I will explain 2 different guides:
First Root Guide:
This guide is for a specific rom version, so you will need to use a specific patched boot.img
- Download the patched_boot.img
- Reboot your device in bootloader-fastboot mode
- Flash the patched_boot.img in the boot partition:
Code:
fastboot flash boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
Second Root Guide:
This guide is more generic than the first one, you should use this one if you are unable to find a specific patched boot.img
- Download a patched_boot.img (you should try with the latest one)
- Reboot your device in bootloader-fastboot mode
- Boot the patched_boot.img:
Code:
fastboot boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
- Click on Install, then direct install and wait the end of the process
- Reboot the device
TIPS:
You can get the stock boot images from the fastboot rom: Fastboot ROMs
HOW TO UPDATE a ROM and KEEP ROOT:
Before all Disable all magisk modules
Be sure to use the latest stable Magisk
You can update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- In Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
Download:
Patched/Stock Boot Images:
https://www.androidfilehost.com/?w=files&flid=308380
or
https://sourceforge.net/projects/fastbootroms/files/OnePlus 8 Pro/Patched-Stock-Boot/
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Donations:
Credits:
I want to specify somethings:
Codename:
OnePlus 8: instantnoodle
OnePlus 8 Pro: instantnoodlep
OnePlus 8 Pro 10.5.4BA (Europe) stock rom link: https://otafsg1.h2os.com/patch/amaz...ygen_15.E.13_OTA_013_all_2004111446_df409.zip
First of all, thank you for the awesome work!
Could you explain a bit what are the modifications made to boot.img?
pijiman said:
First of all, thank you for the awesome work!
Could you explain a bit what are the modifications made to boot.img?
Click to expand...
Click to collapse
I just patched it with magisk, so it only contains in addition magisk
Wow, that was fast, thanks a lot guys
Before flashing the patched_boot.img you need to unlock the bootloader.
Tick the "Advanced reboot" under Developer options
Then reboot your device in bootloader-fastboot mode
fastboot oem unlock
Many thanks for the quick Root my Device
mauronofrio said:
I just patched it with magisk, so it only contains in addition magisk
Click to expand...
Click to collapse
Do you know if it passes SafteyNet with Magisk Hide enabled? Assuming not since Google now uses hardware signatures vs spoofable software ones.
Awesome, I had a bit of a struggle trying to find the full stock ROM link, thanks.
I have a follow up question: what are the features needed from Magisk and Magisk Manager that require the Canary release? I can't find anything in their changelog and my curiosity is getting the best of me
pijiman said:
I have a follow up question: what are the features needed from Magisk and Magisk Manager that require the Canary release? I can't find anything in their changelog and my curiosity is getting the best of me
Click to expand...
Click to collapse
Canary builds are not needed.
xocomaox said:
Do you know if it passes SafteyNet with Magisk Hide enabled? Assuming not since Google now uses hardware signatures vs spoofable software ones.
Click to expand...
Click to collapse
Sure does
xByt3z said:
Sure does
Click to expand...
Click to collapse
That's interesting. Thanks!
Does this mean Google Pay still works? Thanks
l_p_4_7 said:
Does this mean Google Pay still works? Thanks
Click to expand...
Click to collapse
Yes.
Great work!
Im just sad that my fav kernel devs from OP7P wont be purchasing 8 Pro so no Smurf or SkyDragon kernel!
Nekromantik said:
Great work!
Im just sad that my fav kernel devs from OP7P wont be purchasing 8 Pro so no Smurf or SkyDragon kernel!
Click to expand...
Click to collapse
SkyDragon dev is awesome! I had that on my LG G3!
xocomaox said:
SkyDragon dev is awesome! I had that on my LG G3!
Click to expand...
Click to collapse
Yeah due to increased price I am worried we wont get as much development on 8 Pro. I might get back into situation I was in on 7 pro 5g which had non existent development
Nekromantik said:
Great work!
Im just sad that my fav kernel devs from OP7P wont be purchasing 8 Pro so no Smurf or SkyDragon kernel!
Click to expand...
Click to collapse
feel free to compile them for us
I have a patched img for the global AA device! Would you like to add it to your post?
This is not my build. Credit ny-hardcore for all the hard work on this. I'm just posting it.
Screen call is broken.
This is Lineage 18, Android 11 custom rom for the Pixel 4a Sunfish
If you do not want root, you can stop after step 6
1. Reboot to bootloader
2. fastboot flash --slot all boot recovery.img https://drive.google.com/file/d/1Hh7D_UbnnoTRr1XbC9i0-dvtFgbuFqrP/view?usp=sharing
3. Reboot to recovery
4. factory reset
5. adb sideload lineage-18.0-20201209-UNOFFICIAL-sunfish.zip
https://mega.nz/file/cUlVXApI#NbzUJ6UlyQvyPTitKnW7uJG_tHrsfYor9O0dH4yIiWc
6. Reboot to system
7. Install Magisk Manager https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
8. Reboot to bootloader
9. fastboot flash boot magisk_patched.img https://drive.google.com/file/d/1cONN9Ev0jdAHaRSeOeYyeRTONJ-yO_8-/view?usp=sharing
10. Reboot to system
Could you please provide a kernel and device source tree for this? I have an in-progress diff which I am working to get 18 running fully on the device. It doesn't boot yet, and I would like to know what I messed up.
liamwhite said:
Could you please provide a kernel and device source tree for this? I have an in-progress diff which I am working to get 18 running fully on the device. It doesn't boot yet, and I would like to know what I messed up.
Click to expand...
Click to collapse
Based on the fact that this is NOT my work as stated above, I'm NOT at liberty to tell you. No offense. I would contact xda member edmontonchef and ask him. He's the one who sent it to me. I would like to think this wouldn't be a issue because if it was mine, I wouldn't care, but it's not.
This is my build.
Device tree is based of DU trees (r11x branch) and vendor (also r11x)
Kernel is flar2 kernel with wifi merged in.
ny-hardcore said:
This is my build.
Device tree is based of DU trees (r11x branch) and vendor (also r11x)
Kernel is flar2 kernel with wifi merged in.
Click to expand...
Click to collapse
I'm using it right now. Great Rom. Thank you!!! Hope you don't mind I shared it.
Does this support signature spoofing?
Espio419 said:
Does this support signature spoofing?
Click to expand...
Click to collapse
Would doubt it, if it's just vanilla LOS
ny-hardcore said:
This is my build.
Device tree is based of DU trees (r11x branch) and vendor (also r11x)
Kernel is flar2 kernel with wifi merged in.
Click to expand...
Click to collapse
Are Gapps included. Looking for a non gapps rom
EggZenBeanz said:
Are Gapps included. Looking for a non gapps rom
Click to expand...
Click to collapse
No gapps. Minimal Google play service function are included in build.
Espio419 said:
Does this support signature spoofing?
Click to expand...
Click to collapse
No
TheSayaMan said:
No gapps. Minimal Google play service function are included in build.
Click to expand...
Click to collapse
Actually it contains gapps/Google play.
ny-hardcore said:
Actually it contains gapps/Google play.
Click to expand...
Click to collapse
I guess I assumed wrong. I thought he was referring to having to flash a seperate gapps zip.
Espio419 said:
Does this support signature spoofing?
Click to expand...
Click to collapse
i'm working on a microg edition using the notes from the guy who made the microG build for 4a 5G
ny-hardcore said:
i'm working on a microg edition using the notes from the guy who made the microG build for 4a 5G
Click to expand...
Click to collapse
Oh yeah! Would love to see that. I'm ready to hop from my pixel 3xl once there's a non gapps ROM available
New build updated in OP. Thank Senior Member ny-hardcore for this.
Changes: Lineage sources and kernel updated with latest google update. The boot.img was updated in the payload to eliminate a second boot flash after sideloading rom for working WiFi. Please report any bugs that I may have missed. Also, I never dirty flash over anything. They more than likely cause problems. I did a clean install of this. If you are on the previous build of this, I DO NOT recommend dirty flashing it.
TheSayaMan said:
New build updated in OP. Thank Senior Member ny-hardcore for this.
Changes: Lineage sources and kernel updated with latest google update. The boot.img was updated in the payload to eliminate a second boot flash after sideloading rom for working WiFi. Please report any bugs that I may have missed. Also, I never dirty flash over anything. They more than likely cause problems. I did a clean install of this. If you are on the previous build of this, I DO NOT recommend dirty flashing it.
Click to expand...
Click to collapse
Flashed and running well. WiFi worked right away. I noticed the boot.IMG in the op has stock recovery so I used the derpfest boot.IMG for flashing instead.
Also it's still November ASB?
Edmontonchef said:
Flashed and running well. WiFi worked right away. I noticed the boot.IMG in the op has stock recovery so I used the derpfest boot.IMG for flashing instead.
Also it's still November ASB?
Click to expand...
Click to collapse
I haven't been able to check everything out. One thing I just noticed is that I am unable to pass safetynet with it but not a big deal for me.
Edmontonchef said:
Flashed and running well. WiFi worked right away. I noticed the boot.IMG in the op has stock recovery so I used the derpfest boot.IMG for flashing instead.
Also it's still November ASB?
Click to expand...
Click to collapse
The boot in OP will work as well so take your pick and yes I did notice its still November. He's working on another build though.
TheSayaMan said:
The boot in OP will work as well so take your pick and yes I did notice its still November. He's working on another build though.
Click to expand...
Click to collapse
december hasnt been merged in lineage sources
Is the boot.img a twrp recovery or? I am coming from stock, so would i need to touch twrp at all for this?
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Official site
Unofficial site
Source Code
Code:
#include <std_disclaimer.h>
/*
*
* 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.
*
*/
This is the AOSP ROM for the Sony Xperia XZ2 (akari)
This ROM build will always mainly based on Sony AOSP Code and maybe include cherry-picks.
I plan to make monthly builds, after a new security patch level, if there is no need for a critical hotfix.
FAQ:
fastboot & adb
https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
https://wiki.lineageos.org/adb_fastboot_guide.html
https://developer.android.com/studio/releases/platform-tools
Stuck at SONY logo? Maybe you need to flash the OEM binary to oem_a and oem_b, while just oem is not enough.
Bugtracker:
SODP Bugtracker -> If you think the problem is in SODP
My Bugtracker -> If you think the problem is in my implementation
Bugreport:
A bugreport needs
Code:
logcat -b all
and a way to reproduce the issue.
A crash of the system requires the content of the /sys/fs/pstore folder as bug report
Be aware that a second reboot erases this folder
A crash to the recovery partition requires additionally the content of the /dev/block/by-name/misc partition
You get the content via `cat /dev/block/by-name/misc partition > /path/to/output/file.txt`
To rescue a not responding phone:
VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.
Thank you very much for your help, code contribution & testing! (Random order):
@jerpelea, the sony employees and their volunteers (people like you and me) coding this wonderful piece of software
@dhacke for providing a download server
And many thanks to the few donators!
A telegram group for technical SODP stuff:
https://t.me/xda_tv
Download & Installation
Download ROM:
Android File Host
FTP-Server from @dhacke
Download Drivers:
OEM (Tama) binaries
GCAM Camera App:
GCAM Issue
Suggested GCams
Installation with a recovery:
fastboot flash oem _a oem_*.img (Only needed until the device receives mainline support by SODP)
Flash the ROM in a recovery
Reboot into recovery just to make sure you're on the new slot
OpenGapps (Requires TWRP or a custom ROM recovery)
Dual Sim Patcher (Requires TWRP or a custom ROM recovery)
(In case a modification prevents your device from booting) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Flash the ROM without a recovery:
Extract the payload.bin from the .zip file
Extract the .img files with the Playload Dumper
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot -w (Wipes your internal storage and the userdata; only if needed)
Now you got the AOSP recovery, to please continue with the normal installation
fastboot flash oem_a oem_*.img (Only needed until the device receives mainline support by SODP)
fastboot flash vendor vendor.img
fastboot flash system system.img
News
26.06.2023
android-13.0.0_r52 (June security patchlevel)
Click to expand...
Click to collapse
26.05.2023
android-13.0.0_r43 (May security patchlevel)
Click to expand...
Click to collapse
Compiling AOSP is working again since LTS kernel 6.1.30
Click to expand...
Click to collapse
12.04.2023
android-13.0.0_r38 (April security patchlevel)
Click to expand...
Click to collapse
04.04.2023
android-13.0.0_r35 (March security patchlevel)
Click to expand...
Click to collapse
Fixed build issue
Click to expand...
Click to collapse
07.10.2022
android-13.0.0_r7 (October security patchlevel)
Click to expand...
Click to collapse
OTA.zip generation is working again
Click to expand...
Click to collapse
08.09.2022
android-13.0.0_r4 (September security patchlevel)
Click to expand...
Click to collapse
06.09.2022
android-13.0.0_r1 (August security patchlevel)
Click to expand...
Click to collapse
Thanks, @MartinX3! There are no Android 13 SW binaries for the Tama platform in the Sony servers. Should we make use of the ones for Android 12, instead?
casouzaj said:
Thanks, @MartinX3! There are no Android 13 SW binaries for the Tama platform in the Sony servers. Should we make use of the ones for Android 12, instead?
Click to expand...
Click to collapse
You're welcome
As far as I know it's fine to use the A12 binaries for now on the tama devices.
The A13 binaries will come later.
Thanks, @ MartinX3!
How to install Gapps?
I followed the installation instructions, but it ended up in a recovery loop: after some minutes of boot animation, it restarts to the stock recovery. After some attempts with the same results, I'm now back to my previous setup, AwakenOS 2.10. Will wait for it to be updated to A13. Thanks, anyway!
Thanks for the test but without logs it can't get fixed
casouzaj said:
I followed the installation instructions, but it ended up in a recovery loop: after some minutes of boot animation, it restarts to the stock recovery. After some attempts with the same results, I'm now back to my previous setup, AwakenOS 2.10. Will wait for it to be updated to A13. Thanks, anyway!
Click to expand...
Click to collapse
The same here. Bootloop: /
osa355 said:
The same here. Bootloop: /
Click to expand...
Click to collapse
Looogs
pstore from the recovery would be helpful. <3
I wonder if the stock A10 ROM would be required beforehand. In my case, I started from A12.1.
casouzaj said:
I wonder if the stock A10 ROM world be required beforehand. In my case, I started from A12.1.
Click to expand...
Click to collapse
Luckily the stock Voodoo for every new stock rom version only needs to be done once in your device UFS lifetime.
(Of course booting to the desktop after the google assistant to apply every firmware upgrade).
(And it should be done for the right LTE region if you move the country/provider for the best signal strength experience, since the old sony devices had different rom regions for the lte providers)
casouzaj said:
I wonder if the stock A10 ROM world be required beforehand. In my case, I started from A12.1.
Click to expand...
Click to collapse
I installed stock Android 10 and had to restart without the Android animation screen. As I installed directly from Lineage 19.1 it was at least an Android boot screen. I don't have logs because I don't know how to save them: /
MartinX3 said:
Luckily the stock Voodoo for every new stock rom version only needs to be done once in your device UFS lifetime.
(Of course booting to the desktop after the google assistant to apply every firmware upgrade).
(And it should be done for the right LTE region if you move the country/provider for the best signal strength experience, since the old sony devices had different rom regions for the lte providers)
Click to expand...
Click to collapse
sorry to post here but you have the dm closed.can you patch the walkman apk in order to work? see here->https://forum.xda-developers.com/t/...es-a100-nw-a100-series.4324181/#post-87388081
With my own compiled A13: (+ latest TAMA SW for A12)
On startup message: "There's an internal problem with your device. Contact your manufacturer."
For about a minute phone lagging - then working normally.
Camera not working, BT/WIFI working.
Upd: some issues with branch rep sync, compiled old A12...
alexisnik199111 said:
sorry to post here but you have the dm closed.can you patch the walkman apk in order to work? see here->https://forum.xda-developers.com/t/...es-a100-nw-a100-series.4324181/#post-87388081
Click to expand...
Click to collapse
Sorry, but its a pure AOSP ROM for SODP devices.
Hacks could raise the amount of issues.
08.09.2022
android-13.0.0_r4 (September security patchlevel)
Click to expand...
Click to collapse
I have now tried to install the newly released build on a XZ3 in the house. Again, a recovery loop. The difference is that in the XZ3 there is no boot animantion, and it takes a lot longer to boot to recovery. I have attached the recovery.log (zipped) file.
casouzaj said:
I have now tried to install the newly released build on a XZ3 in the house. Again, a recovery loop. The difference is that in the XZ3 there is no boot animantion, and it takes a lot longer to boot to recovery. I have attached the recovery.log (zipped) file.
Click to expand...
Click to collapse
Thank you but was there a pstore like described in the first post?
Sadly the log of the recovery doesn't help, since the recovery works.
MartinX3 said:
Looogs
pstore from the recovery would be helpful. <3
Click to expand...
Click to collapse
Sorry for the noob question, but where to find this pstore?