[ALL_IN_ONE][R/Q] Xperia 5 II ROMS - Sony Xperia 5 II ROMs, Kernels, Recoveries, & Othe

[ALL_IN_ONE][R/Q] Xperia 5 II ROMS - Sony Xperia 5 II ROMs, Kernels, Recoveries, & Othe

ken442266 said:
Code:
#include <std_disclaimer.h>
/*
* 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.
*/
Notes:
20210316: LineageOS is out.
So i merge all threads into one thread.
For Lineage18.1, PEP, EvoX will get another update cause i make wrong build type.
Thanks again for nezorflame, Big thanks.
Old lineage17.1 and RR are just old rom with new thread.
New build for lineage18.1 and PEP fix the issue about 5Ghz hotspot
Important Information:
1. This ROM has nothing related to ODM images! So you don't need to ask/install anything like that, just follow the instructions.
2. This ROM will never work with any versions of Google Camera (GCam)!
3. For VoLTE, you need to boot into stock firmware and enable it before flashing this ROM!
ROMS:
[Android 10 - Vendor 10 = ROM Version is Android 10 and you must using stock 10 vendor for booting]
[Android 11 - Vendor 11 = ROM Version is Android 11 and you must using stock 11 vendor for booting]
LineageOS 17.1 - Android 10 - Vendor 10
AFH
LineageOS 18.1 - Android 11 - Vendor 11
MEGA (20210316 New Update)
EvolutionX Elle - Android 11 - Vendor 11
MEGA
RROS - Android 10 - Vendor 10
AFH
PixelExperience Plus - Android 11 - Vendor 11
MEGA
Looking For CinemaPro And PhotoPro:
Click Here
How To Flash:
Unlock bootloader is necessary.
1. Install fastbootd drivers, guidance
2. Put your device into fastboot by volume up key.
Code:
// reboot to fastbootd
fastboot reboot fastboot
// flash it
fastboot set_active a
fastboot flash boot boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot erase metadata
fastboot flash system system.img
fastboot flash product product.img
// earse userdata
fastboot erase userdata
Bugs:
FP Not working in Third Apps
Also thanks to:
BBN Shion Sjll
nezorflame (This build won`t come out so fast without his server)
Source:
Kernel Source
Device vendor
Device Tree
Feel free to donate me:
Paypal
Click to expand...
Click to collapse
Thanks for all your hard work! How stable is EvoX compared to the current RR build? I'm looking to move up to Android 11 finally and want to see if that is my next ROM

Jayram2000 said:
Thanks for all your hard work! How stable is EvoX compared to the current RR build? I'm looking to move up to Android 11 finally and want to see if that is my next ROM
Click to expand...
Click to collapse
comparing stabilize. RR is better.

Which Rom is better LineageOS 17.1 or RROS?

Bellitsch89 said:
Which Rom is better LineageOS 17.1 or RROS?
Click to expand...
Click to collapse
It depends

Bellitsch89 said:
Which Rom is better LineageOS 17.1 or RROS?
Click to expand...
Click to collapse
RROS is more feature rich, but has a higher overhead so it depends on what you value. For my case, RR lasts me plenty long and I love having features so its my go to.

I will have a Lots of Features. For example color theming, satusbar theming and notification bar theming.
I think then is RROS better for me?

Bellitsch89 said:
I will have a Lots of Features. For example color theming, satusbar theming and notification bar theming.
I think then is RROS better for me?
Click to expand...
Click to collapse
rocking RROS here, it's the better choice for now

Okay Thanks at all. I will try RROS

Bellitsch89 said:
Okay Thanks at all. I will try RROS
Click to expand...
Click to collapse
If it's okay for you to stay on a10 and not have any more updates then go for it ^^
Personally I don't care to stay on a10..for now haha

flyl0 said:
If it's okay for you to stay on a10 and not have any more updates then go for it ^^
Personally I don't care to stay on a10..for now haha
Click to expand...
Click to collapse
I will stay on Android 10. Android 11 I will give a try later

Do you have a link to the github repositories? The bottom two links don't work and looking at your repos doesn't show any PeP or other than the kernel.
Thanks a ton!

eqbirvin said:
Do you have a link to the github repositories? The bottom two links don't work and looking at your repos doesn't show any PeP or other than the kernel.
Thanks a ton!
Click to expand...
Click to collapse
It's closed source for now

Whilst trying to flash the product.img (Lineage 18.1), I get the following error:
writing 'product_a' 2/2...
FAILED (remote: Operation not permitted)
Whilst trying to flash product.img (PEP), I also get the following error:
writing 'product_a' 6/6...
FAILED (remote: Operation not permitted)
I have OEM unlocked my device, and I am flashing files via 'fastbood'. Any suggestions?
Edit: I fixed the issue myself, the problem was down to out of date fastboot drivers on Linux. Downloading the latest 'platform-tools' from Google solved the issue.

Cannot fully display Chinese

Question about LOS 18 for this phone....Is VoLTE/Sony Cinema working perfectly on all carriers, or do they use some strange Sony Modem thingy that needs customizations?

baboon23 said:
Question about LOS 18 for this phone....Is VoLTE/Sony Cinema working perfectly on all carriers, or do they use some strange Sony Modem thingy that needs customizations?
Click to expand...
Click to collapse
Yes it will work if you enable voLTE before flashing the rom, and you can download the apk of Sony Cinema and installing it like a normal apk.

Do we have anyone maintaining any Xperia 5 II ROMs any more?
With @ken442266 selling his phone, it doesn't seem like anyone else is picking up the mantle. The only "active" ROM thread I see here is Havoc-OS and that seems to only be Android10.

LineageOS 18.1 - Android 11 - Vendor 11
MEGA (20210316 New Update)
This rom,Why no Chinese?

ALLANNIE said:
LineageOS 18.1 - Android 11 - Vendor 11
MEGA (20210316 New Update)
This rom,Why no Chinese?
Click to expand...
Click to collapse
This is targeting for non-chinese users.

Related

[RECOVERY][grus] KudProject's Unofficial TWRP 3.5.2_9-1 [16-05-2021]

This is basically a tl;dr thread.
I don't want to make a thread that everyone will lazy to read.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. It's 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.
Disclaimer
Code:
/*
* Your warranty might not be void (thanks Xiaomi). However...
*
* 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 RECOVERY
* 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.
*/
Requirements
Xiaomi Mi 9 SE (of course)
Unlocked bootloader
Some knowledge on how to deal with your device... and patience.
Flashing InstructionsI assume you've done (very) basic steps on preparing to flash your device.
Reboot device to bootloader. If device is powered off, press and hold Power + Volume Down button until tinkering Mi Bunny with "FASTBOOT" text appears.
Optional: Flash stock vbmeta with the following command (attached if needed):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Under same directory as TWRP image and ADB/Fastboot executables (if ever required), type this command:
Code:
fastboot flash recovery twrp-3.x.x-y-KudProject-grus.img
Where x and y are version of TWRP you're going to flash.
IMPORTANT: After flashing, immediately press and hold Power + Volume Up for about 10 seconds to reboot to recovery.
Swipe the option to allow modifications. This will prevent stock ROM from replacing recovery, however be aware that you might need to reflash stock vbmeta with disabled verity after that to be able to boot stock ROM!
Downloads
Webserver | MEGA
Old releases only: OSDN | AndroidFileHost
Known Issues
/dev/null
Special Thanks
Dees_Troy and everyone behind TWRP
Everyone on Mi 9 SE community
Device Sources
TWRP repository fork
Device tree
Kernel source

Changelogstwrp-3.5.2_9-1-KudProject-grus
Merged TWRP source changes up to 25 April 2021 (UTC+8)
Updated kernel to MoeSyndrome kernel based on Android 10
Mount firmware partition as read-only
Added support for formatting Cust partition in GUI
twrp-3.4.0-0-KudProject-grus
Merged TWRP source changes up to 22 June 2020 (UTC+8)
Supports decryption of userdata on Android 10-based MIUI and custom ROMs using Android 10 crypto blobs (might not be backwards compatible)
Restored system and vendor (non-image) backup support
Added support for backing up persist (and the image)
Build some blobs from source
Updated remaining blobs from V11.0.2.0.QFBEUXM
Updated prebuilt kernel to latest Pie
twrp-3.3.1-3-grus-20190802
Switched to source-built kernel
Updated blobs from MIUI China developer 9.7.4
Added support for F2FS in kernel (tell me if decryption breaks on this file system though)
Added persist into fstab
Added vendor-side touch firmware
Get CPU temperature from proper thermal zone
Disabled vbmeta checks
Only allow image backups for system and vendor
Symlinked /system to /system_root/system for backward compatibility
Misc stuffs
TWRP and f2fs-tools upstream changes
twrp-3.3.1-2-grus-20190609
Fixed wrong USB-OTG mount point
twrp-3.3.1-1-grus-20190603
Updated prebuilt kernel and DTBO from MIUI China developer 9.5.30
Corrected vendor image flashing
Support for wiping /vendor
Support for flashing and backup up (as part of boot) DTBO
Defined TW_SCREEN_BLANK_ON_BOOT
(Properly) excluded TWRP app
Included private recovery configuration
twrp-3.3.1-0-grus-20190531
Initial build.

Notes
Don't use fastboot boot to boot the recovery; it'll proceed to boot system instead using recovery's kernel. If this happens with your current kernel's boot image security patch being older than recovery one, you're basically busted as FBE keys are upgraded the time newer combination of system + vendor + boot image security patches are detected.
If you're out of luck in this situation, the only way to resolve is to format data (just backup your data to somewhere safe before doing so).
If you flash disabled vbmeta, you can't flash stock MIUI zips until the original vbmeta is restored.

Wrapped key support is added into recovery just for anticipation, although not defined by default in fstab.
I can't test it since EEA device so far is on March ASB as of V10.2.5.0 stable.
Otherwise, basic functionalities including decryption should work.
Edit: grus doesn't have anti rollback enabled at this moment, but Xiaomi may enable it in the future...

it is save changed from wzsx150 twrp ? or must on fastboot ?

bonbibonkers said:
it is save changed from wzsx150 twrp ? or must on fastboot ?
Click to expand...
Click to collapse
If already on any version of TWRP, just flash it using Flash Image option to recovery partition.

ok, gonna test it out , many thanks great work ??

Thanks! working so far so good

krasCGQ said:
If already on any version of TWRP, just flash it using Flash Image option to recovery partition.
Click to expand...
Click to collapse
Working fine when flashing from wzsx150 twrp version.

krasCGQ said:
If already on any version of TWRP, just flash it using Flash Image option to recovery partition.
Click to expand...
Click to collapse
i already flash it, worked good. but the CPU Temps is little misreading, i think.... it can go up to 80° C lol

rzki03 said:
i already flash it, worked good. but the CPU Temps is little misreading, i think.... it can go up to 80° C lol
Click to expand...
Click to collapse
Just ignore it. That same CPU temperature glitch also happens on sirius.

Wow, finally an *actual* twrp
Sent from my Mi 9 SE using Tapatalk

krasCGQ said:
Just ignore it. That same CPU temperature glitch also happens on sirius.
Click to expand...
Click to collapse
okay then. thank you!

@krasCGQ
Hey, in next release can you add the option to backup and recover dtbo partion/image like with this recovery https://forum.xda-developers.com/mi-9-se/how-to/recovery-twrp-lr-team-wzsx150-v3-3-0-t3926219 ?
Thanks

denzel09 said:
@krasCGQ
Hey, in next release can you add the option to backup and recover dtbo partion/image like with this recovery https://forum.xda-developers.com/mi-9-se/how-to/recovery-twrp-lr-team-wzsx150-v3-3-0-t3926219 ?
Thanks
Click to expand...
Click to collapse
So this release doesn't have Backup/Restore working?

luisbelmont said:
So this release doesn't have Backup/Restore working?
Click to expand...
Click to collapse
Yes, it has. My request was a bit different.

denzel09 said:
Yes, it has. My request was a bit different.
Click to expand...
Click to collapse
Oh, perfect! Thank you. What advantages does your request have?

luisbelmont said:
Oh, perfect! Thank you. What advantages does your request have?
Click to expand...
Click to collapse
To backup and recover dtbo image before and after flashed this custom kernel: https://forum.xda-developers.com/mi...nel-okitakernel-v1-0-mi-9-se-27-2019-t3934029

Thanks for the work! Great seeing you here after ZenFone 2 and Redmi Note 4. Hopefully a KudKernel will be in the works(if not already).

puppetminds said:
Thanks for the work! Great seeing you here after ZenFone 2 and Redmi Note 4. Hopefully a KudKernel will be in the works(if not already).
Click to expand...
Click to collapse
Kinda off-topic, but well rebasing over CAF is a tough job...
Sent from my Mi 9 SE using XDA Labs

[TREBLE] Pie VENDOR-IMAGE to boot Pie-GSI on X01BD

Code:
/*
* Your warranty is now void.
*
* We're 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 TREBLE
* SUPPORT 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.
*
*/
Alright so this is only done on user demand since GSI's were not booting with stock and custom rom vendor images
Install Instruction:
* Flash OFFICIAL TWRP
* Format /system, /data and /cache
* Flash vendor zip:
https://sourceforge.net/projects/arrow-os/files/EXTRAS/X01BD/P-GSI-Vendor.zip/download
* Flash boot.img:
https://sourceforge.net/projects/arrow-os/files/EXTRAS/X01BD/boot_permissive.img/download
* Install any Pie GSI system image using TWRP (Install image -> choose your system.img -> select system partition)
* Reboot
Known issues:
You tell me
Bug report:
All bug reports without any logs will just be ignored.
Where can i find GSI?
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Working GSI's:
* PhhAOSP pie
* ArrowOS GSI 9.x
* AOSiP GSI pie
Lemme know and I'll update it here!
Contributors
@kubersharma, @bauuuuu
(GPL kernel source: https://github.com/ArrowOS-Devices/...tree/9e41580d6c9fb2d5d896fef5ac5403a12d882d00 for the bootimge (kernel inside) linked)
PS: Generic System Image are made to support all treble devices but do not expect it to work as perfectly as a device specific build nor expect to have everything working!
ENJOY

reserved

reserved

Is it for real?

Will sGsi roms boot.?

Anubhav_singh said:
Will sGsi roms boot.?
Click to expand...
Click to collapse
This is basically for properly made GSI (built from sources for example: the one from phhusson or based on his sources)
I am not sure if OEM ported (sGSI) will boot
But we will see what we can do. Thanks

Wow, thanks for this. You and Bauuuuu always surprise us.

Will android q gsi boot

reverseflash said:
Wow, thanks for this. You and Bauuuuu always surprise us.
Click to expand...
Click to collapse
+1

@kubersharma the vendor image does not seem to work with OEM ported GSIs. I've tested MIUI but that got stuck on Asus logo, didn't reach the bootanimation.
I've attached a zip (2 logs), one was tested with the vendor image on this thread and second with default Arrow vendor.

As the OP says it's for source built pie GSIs

There is a huge background story on how messed the treble is in our device right now thanks to Asus, for having too much blob dependency on system.

If someone wants to try Q GSI dp6 (Generic or Pixel) should give a try after flashing my latest (20190812) LineageOS 16.0 build
https://sourceforge.net/projects/ku...12-UNOFFICIAL-X01DB-user-release.zip/download

kubersharma said:
If someone wants to try Q GSI dp6 (Generic or Pixel) should give a try after flashing my latest (20190812) LineageOS 16.0 build
https://sourceforge.net/projects/ku...12-UNOFFICIAL-X01DB-user-release.zip/download
Click to expand...
Click to collapse
I tried pixel gsi but that didn't even reach bootanimation. Did you flash any additional patches?
Edit: I flashed permissiver and fix_zygote.

Thank you kuber and bauuua for your work for our device

Please make one too for X00RD. Plz ?

Need of Vendor For Android 10 OOS
Need vendor for android 10 Oxygen OS ...it's time you havent updated vendors Dev's...thanks in advance

Hi, @kubersharma. Sorry for the off-topic question but I have an Asus Zenfone 4 (ZE554KL) on which with the Oreo and Pie upgrade ASUS standardized BLOBs but does not created a dedicated vendor partition, so no official treble support. I wish I could flash the GSIs on it. The part of creating the vendor partition is no problem, but would you have any tips or tutorials on how to properly move the files from /system/vendor to /vendor in a functional way and the boot img hack needed to boot? Thank you very much!

does it work on android 10??

hi thank you for the rom. Can you make one for zs551kl(zenfone 4 pro) thank you very much

[DISCONTINUED][R][20210314][ROM][UNOFFICIAL] LineageOS 18.1 for Xperia 5 II

Code:
#include <std_disclaimer.h>
/*
* 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.
*/
NOTICE:
This is the last update before i sold this phone.
[Please make sure you updated to 58.1.X (Which is Android11)]
+ Camera key and Assist Key Fix
+ Update to R based
+ Fix the issue about 5Ghz hotspot
+ March Security Update
About LineageOS:
LineageOS is a free, community built, aftermarket firmware distribution of Android 11.x (R),
which is designed to increase performance and reliability over stock Android for your device.
All the source code for LineageOS is available in the LineageOS GitHub repo.
And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website : http://lineageos.org
About LineageOS Legal : http://lineageos.org/legal/
Important Information:
1. This ROM has nothing related to ODM images! So you don't need to ask/install anything like that, just follow the instructions.
2. This ROM will never work with any versions of Google Camera (GCam)!
3. You need to flash Stock Android 11 before flashing this ROM.
4. For VoLTE, you need to boot into stock firmware and enable it before flashing this ROM!
5. If you came from SODP ROMs, you need to go back to official Android 11 firmware, and boot into launcher.
6. Please make sure you are using Android 11 Stock ROM [Version > 58.1.X] before flash this.
7. Still in developing. May have some unexpected bugs.
Downloads Links
LineageOS 18.1:
Unofficial-build: Link (MEGA)
Looking For CinemaPro And PhotoPro:
Click Here
Google Applications (optional):
NikGApps: https://nikgapps.com
Information: Flash the GApps before the first boot. If not, a clean flash is recommended.
Flashing and updating
How to flash
Make sure you upgraded to Official Android 11 from Sony
Unlock bootloader is necessary.
Download latest platform-tools from google
1. Install fastbootd drivers, guidance
2. Put your device into fastboot by volume up key.
3. Enter fastbootd:
Code:
fastboot reboot fastboot
4. Flash LineageOS:
Code:
fastboot set_active a
fastboot flash boot boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot erase metadata
fastboot flash system system.img
fastboot flash product product.img
5. If you are first time to flash LineageOS, Wipe the old userdata:
Code:
fastboot erase userdata
GApps:
Download my OrangeFox Recovery then flash it
Root access:
Flash Magisk in recovery.
SD CARD Notice:
Format you sdcard into 'FAT32' if your sdcard can NOT be use in this system
Issues and reports:
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Share a log of the error with Logcat for example
Bugs:
LDAC (Not sure)
FP Not working in Third Apps
Also thanks to:
BBN Shion Sjll
nezorflame (This build won`t come out so fast without his server)
The LineageOS Team
The CyanogenMod Team
Source:
Kernel Source
Device vendor
Device Tree
Feel free to donate me:
Paypal
Screenshots:
{
"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"
}

Oh wow it was quick lol thanks a lot for this build once again. Fortunately, there are developers like you.
I have a few questions though :
1. Which version of Magisk will work for root on this build?
2. Can I install full or stock NikGapps without any issues?
3. Does the issue with the sd card mentioned in the post about LOS 17.1 been fixed?
Have a beautiful day.

Stuck on boot on Lineage logo. Have already upgraded to A11 before this, so it might be connected.
Will try to grab logcat.

flyl0 said:
Oh wow it was quick lol thanks a lot for this build once again. Fortunately, there are developers like you.
I have a few questions though :
1. Which version of Magisk will work for root on this build?
2. Can I install full or stock NikGapps without any issues?
3. Does the issue with the sd card mentioned in the post about LOS 17.1 been fixed?
Have a beautiful day.
Click to expand...
Click to collapse
Both Nik's and OpenGApps latest packages should be fine, but you may have issues regarding the size - I wasn't able to install our stock package due to insufficient space.

Nezorflame said:
Stuck on boot on Lineage logo. Have already upgraded to A11 before this, so it might be connected.
Will try to grab logcat.
Click to expand...
Click to collapse
Nezorflame said:
Both Nik's and OpenGApps latest packages should be fine, but you may have issues regarding the size - I wasn't able to install our stock package due to insufficient space.
Click to expand...
Click to collapse
Damn so we can't install full or stock Gapps/NikGapps on LOS 18.1 ?
Anyway i can stay on A10 and flash this rom right ?

As OP said, yeah.

ken442266 said:
Code:
#include <std_disclaimer.h>
/*
* 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.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 11.x (R),
which is designed to increase performance and reliability over stock Android for your device.
All the source code for LineageOS is available in the LineageOS GitHub repo.
And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website : http://lineageos.org
About LineageOS Legal : http://lineageos.org/legal/
Important Information
1. This ROM has nothing related to ODM images! So you don't need to ask/install anything like that, just follow the instructions.
2. This ROM will never work with any versions of Google Camera (GCam)!
3. You need to flash Stock Android 10 before flashing this ROM.
4. For VoLTE, you need to boot into stock firmware and enable it before flashing this ROM!
5. If you came from SODP ROMs, you need to go back to official Android 10 firmware, and boot into launcher.
6. You don`t need to upgrade to R vendor (58.1.X).Just stay at Q vendor 58.0.X will be fine.
7. Still in developing. May have some unexpected bugs.
Downloads Links
LineageOS 18.1:
Unofficial-build: Link (AFH)
Google Applications (optional):
NikGApps: https://nikgapps.com
Information: Flash the GApps before the first boot. If not, a clean flash is recommended.
Flashing and updating
How to flash
Make sure you upgraded to Official Android 10.0 from Sony
Unlock bootloader is necessary.
Download latest platform-tools from google
1. Install fastbootd drivers, guidance
2. Put your device into fastboot by volume up key.
3. Enter fastbootd:
Code:
fastboot reboot fastboot
4. Flash LineageOS:
Code:
fastboot set_active a
fastboot flash boot boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot erase metadata
fastboot flash system system.img
fastboot flash product product.img
5. If you are first time to flash LineageOS, Wipe the old userdata:
Code:
fastboot erase userdata
GApps:
Download Lineage Recovery
Flash and boot into Recovery then choose Apply update - Apply from ADB, then sideload the gapps package on your PC with adb tool:
Code:
adb sideload <PATH OF GAPPS>
Root access:
Flash Magisk in recovery.
Issues and reports:
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Share a log of the error with Logcat for example
Bugs:
LDAC (Not sure)
Also thanks to:
BBN Shion Sjll
The LineageOS Team
The CyanogenMod Team
Source:
Kernel Source
Device vendor
Device Tree
Screenshots:
View attachment 5194147View attachment 5194149View attachment 5194151
Click to expand...
Click to collapse
Awesome!, did you manage to get the SD card working?

Nezorflame said:
Stuck on boot on Lineage logo. Have already upgraded to A11 before this, so it might be connected.
Will try to grab logcat.
Click to expand...
Click to collapse
The OP says you should use the stock android 10 firmware as a basis, so I'd imagine thats your issue.

Jayram2000 said:
The OP says you should use the stock android 10 firmware as a basis, so I'd imagine thats your issue.
Click to expand...
Click to collapse
Not really - the first post states that "You don`t need to upgrade to R vendor (58.1.X)", that doesn't imply that with R vendor the phone won't boot. If that's the case, then the initial quote is kinda misleading.
In any case, I'll just try Q vendor as well and see how it goes.

So I've been testing different vendor setups and yes, using R vendor will render the ROM not to boot - it doesn't get past the initial boot animation loop.
So I guess it'd be better to correct the first post stating that users MUST use Q vendor in order to be able to boot.

Apparently the sd card bug is still there too..

flyl0 said:
Apparently the sd card bug is still there too..
Click to expand...
Click to collapse
Yup, it doesn't get detected as properly formatted, OS wants me to reformat it.

Nezorflame said:
So I've been testing different vendor setups and yes, using R vendor will render the ROM not to boot - it doesn't get past the initial boot animation loop.
So I guess it'd be better to correct the first post stating that users MUST use Q vendor in order to be able to boot.
Click to expand...
Click to collapse
Thanks for correct. Yeah, You have to use Q vendor.

It's a shame because I will not use this build if my sd card is not recognized

So about sd card issue. I`m not sure what cause this issue. And when i trying to solve this.
It just works fine on my sd card. So i do not know how to solve it as i can`t get some details on it.
So if anybody can provide logcat for format && access sd card that can be great.
By the way. PixelExperience Eleven is on the way.

ken442266 said:
So about sd card issue. I`m not sure what cause this issue. And when i trying to solve this.
It just works fine on my sd card. So i do not know how to solve it as i can`t get some details on it.
So if anybody can provide logcat for format && access sd card that can be great.
By the way. PixelExperience Eleven is on the way.
View attachment 5194959View attachment 5194961
Click to expand...
Click to collapse
I have a 128gb SDXC card from Samsung, I can try again. How can I capture the logcat for the SD?

TIP 1 : If you have an sd card and want to use it on this build you have to format the sd card to fat32, then it will work just fine.
TIP 2 : If you want Gapps on LOS, make sure to choose the core gapps or basic gapps only.

my apologies if this has been answered somewhere. What prevents GCAM from running on xperia devices with either stock or custom roms?

teostar said:
my apologies if this has been answered somewhere. What prevents GCAM from running on xperia devices with either stock or custom roms?
Click to expand...
Click to collapse
The answer is : "SONY"

Works well so far with the SD card formatted to FAT32. Now I have another device for my OpenGApps build testing
Let's hope exFAT support comes soon <3 great work!

Development [ROM][OFFICIAL] LOS-Modded 19.0[DISCONTINUED]

Code:
/*
* 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.
*/
LineageOS Modded is a free, community built, aftermarket firmware distribution of Android 12 (S), which is designed to increase performance and reliability over stock Android for your device.
LineageOS Modded is based on the Android Open Source Project and LineageOS with extra contributions from many people within the Android community.
All the source code for LineageOS Modded is available in the LineageOS Modded Github repo.
Make sure to wipe userdata, ensure you have at least taken one stock OTA!
Flashing Instructions:-
TinyFastbootScript:-
Make sure to wipe userdata
1. Download TinyFastbootScript
2. Download the ROM named *Images*
3. Unpack TinyFastbootScript and the ROM into the same directory
4. Run the bat file for TinyFastbootScript
5. Choose latest fastboot version
6. Place device in bootloader mode
7. Run the command for flashing custom firmware
8. Done!
Fastboot Method:-
1. Download the Images zip
2.
Code:
fastboot update *Images*.zip
3. Reboot and enjoy!
Bugs :
Permissive
Safetynet
DualSIM
Some Settings Functions
* Drop a comment down below if you need any help, you can also Join https://t.me/electimonrel on telegram if you need any help.
Downloads:
Lineage-Modded:
https://build.lolinet.com/file/lineage/nio/
Contributors
@Electimon, @erfanoabdi, @dianlujitao
Source Code: moto-sm8250
Version Information
Status: Beta
Jan 06: initial release

Amazing work

awesome

Great work on the ROM electimon, smoothest available, and the battery management is excellent.

Hi,
I think scoped storage doesn't work properly on my Moto Edge S with Lineage 19. I'm trying to use some apps that require it, but they crash every time I try to add a directory, like aethersx2 for example.

Hi all
I successfully installed the Rom but only sim 1 work
How to activate two sims please .
Thanks all

Makhreta said:
Hi all
I successfully installed the Rom but only sim 1 work
How to activate two sims please .
Thanks all
Click to expand...
Click to collapse
check again the above bug list

bawitdol said:
check again the above bug list
Click to expand...
Click to collapse
Yes i know ,
so this mean no solution for this problem ?

Makhreta said:
Yes i know ,
so this mean no solution for this problem ?
Click to expand...
Click to collapse
Some people on Telegram have reported both sims working by flashing Evolution X, then flashing to los-modded 19 without wiping. Your results may vary though

Beetle84 said:
Some people on Telegram have reported both sims working by flashing Evolution X, then flashing to los-modded 19 without wiping. Your results may vary though
Click to expand...
Click to collapse
but i cannot find evolution x rom for this device ???!!!

Makhreta said:
but i cannot find evolution x rom for this device ???!!!
Click to expand...
Click to collapse
Motorola Moto G100 / Edge S
The Motorola Moto G100 / Edge S is a 6.7" phone with a 1080x2520p resolution display. The Qualcomm SM8250-AC Snapdragon 870 5G chipset is paired with 6/8GB of RAM. The main camera is 64+16+2MP and the selfie camera is 16+8MP. The battery has a 5000mAh capacity.
forum.xda-developers.com

is it android 12?

i tried version 18 and the two sims is o.k

HOW TO INSTAL MAGISK in this rom
1. download TWRP 3.5.2 and magisk 23.0
2. command <fastboot boot twrp.img> in bootloader mode
3. command <adb push magisk.zip /sdcard> in twrp
4. flash magisk.zip file
5. reboot to system
^^

Works great thanks!
having some issues with Android Auto showing black display since switching to this tho?
anyone know how to fix?

Is there a newer build?

xisa11 said:
Is there a newer build?
Click to expand...
Click to collapse
Under development

Just wondering what the differences would be between thins and the non-modded Lineage? I'm assuming more features, add-ons, but what are they?

Hello and thanks to everyone who is working on these different Roms for the g100!
One question, which is the most stable Rom for the g100 (without Google) to use as an daily driver?
Is this Rom 19.0 capable as an daily driver?
Thank you

How do I flash this on Linux ?. I suppose it is a bunch of fastboot commands but I am not sure.

[ROM] [12.1] [OFFICIAL] AICP 17.1 [OOS12] [instantnoodle]

{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS), we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q-S with a base of AOSP repositories and some additions from LineageOS for device-specific repositories.
If there are any bugs we will sort them out if it concerns our codebase. This ROM isn't LineageOS supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns 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. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning, we would like to thank:
LineageOS & CM (R.I.P.) team
Evolution X Team & @AnierinB
GZOSP team
@maxwen and the rest of the OmniRom team
DU team
Resurrection Remix team
AOSiP team
Whole Android Community
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 17.1
Download link: https://dwnld.aicp-rom.com/
Please note that official builds will be deleted from our servers every month due to maintenance services.
Starting with AICP 15 we will be storing a copy of the most recent release here: https://media.aicp-rom.com/vault/.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Google Apps:
We recommend MindTheGapps as it has been thoroughly tested and it works well with the ROM, some other minimal (and others) GApps packages could have issues, so try using MindTheGapps if you have any issues with other GApps packages
MindTheGapps: Download from HERE
Due to new light sensor, autobrightness is a mess for now. But will be fixed soon I hope.
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but the discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Does this ROM include GApps or do I have to flash them separately?
A. No, we do not include prebuilt GApps, because of possible licensing issues with Google Software and because some users do not want GApps preinstalled as they want to use alternative services like MicroG or just prefer flashing a GApps "flavor" of their liking.
Q. Does this ROM use the camera or gallery app from stock?
A. It depends on the device. In most cases, these apps include proprietary libs/code and cannot be included in the device trees on GitHub or we risk having the ROM banned from GitHub. In this case, we might try to make them installable (separate from the ROM zip), or we might provide a version of these apps with the ROM that doesn't include any proprietary libs. It's also sometimes the case that these apps are simply not included because we didn't feel the need to do so for the device in question.
Q. Does this ROM have Extended/Scrolling screenshot?
A. No, extended screenshot was implemented using an app extracted and modified from manufacturer firmware/system images and is proprietary as well. It led to the closing of many ROM's sources on GitHub.
Q. Does this ROM have FaceUnlock?
A. No, FaceUnlock was also an app extracted and modified from some manufacturers. Even Google removed the Trusted Face (FaceUnlock) feature for security reasons on Android 9.0/10.x. Adding the modified feature did the same to ROM sources as described above.
Q. Can you add (insert favorite weather provider)?
A. No, we cannot add more weather providers as the implementations change and we (the ROM) now have to pay for most services, and that is not cheap, so we decided to use the best free service that we could find, the only way to add your own is for users to apply for their own API key to use their preferred service.
Q. Does this ROM have private official builds with the above proprietary libs included?
A. No, we believe in open source software, this way users know what's in the build and can replicate it themselves, all official builds are built on our build servers using the public sources from GitHub, and no one can (or would) add their own private sources to the build.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is how users can/should install updates most of the time, this can be done with the built-in updater service or with a custom recovery.
Q. How do I 'dirty flash' builds?
A 1. For "A only" devices: Wipe the System, Cache, and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
A 2. For "A/B" devices": Wipe the ART/Dalvik cache. Flash the ROM, reboot to the recovery, flash GApps, your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to lose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to lose root. Now swipe to flash and reboot afterward.
Using the ROM:
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. Do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get, and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section on the AICP Extras main page.
The ROM should contain everything you need to enjoy Android S. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM zip file.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)16.08.2022 Weeklies were the last builds based on OOS11 base.Starting with 23.08.2022 Builds, we are switching to OOS12 Base.BE ADVISED !!!!DO NOT FLASH NEW WEEKLY OVER 16.08.2022 Builds via OTA. Please follow the instructions in the 2nd post for FW update first, then you can flash New Weeklies.
If you are flashing using adb sideload, GAPPS needs to be flashed on every dirty flash as it's mentioned above.
If you are flashing using OTA, no need to flash GAPPS, .
Currently supported Root Solution:
Magisk versions >= feel free to report. Didn't tested myself.
Instructions for OTA ("Over-The-Air" Updates) on "A only" devices (not A/B):
Using on board recovery will be enough mostly for your operations.
Instructions for OTA ("Over-The-Air" Updates) on "A/B" devices:
Open the updater app, download the update, then press install and wait for the process to finish (feel free to let it run in the background), then press reboot when prompted, there isn't any need to flash GApps separately
If you want to contribute to AICP, or if you want to see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
GitHub - AICP/kernel_oneplus_sm8250
Contribute to AICP/kernel_oneplus_sm8250 development by creating an account on GitHub.
github.com
Device tree source:
AICP/device_oneplus_instantnoodle
Device tree for OnePlus 8. Contribute to AICP/device_oneplus_instantnoodle development by creating an account on GitHub.
github.com
Follow this guide if you want to extract the vendor blobs
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on GitHub
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Contributors:
(mention all the devs who have contributed to your device tree, kernel, vendor, etc,
only mention the main ones though, probably the top four or so, otherwise this list will be a mile long xD)
Information:
ROM OS Version: 12.1
Kernel: Linux 4.19.11-perf
ROM {Firmware|Vendor} required: Latest OOS 12 (At least C20/21 firmware)
Status: STABLE
Release Date: 23-08-2022
You want to see a "normal" night at the "DEV office", click here!!

For further support you can visit our TG Channel:
AICP Support Channel for OnePlus 8 Devices
PLEASE BE ADVISED - YOU MUST UPDATE TO OOS12 FIRMWARE BEFORE INSTALLING THE 8/23 UPDATE.

If you are on OOS11 based Stock or Custom ROM:
Best approach is to flash stock OOS11 and update to the latest for your device OOS12 OTA.
While it's done, you can follow the flashing instructions over stock OOS12 given below.
Click to expand...
Click to collapse
The current firmware upgrade path is available here as found on the Op8 series Telegram support group:
Spoiler
1. Boot up AICP recovery
2. Go to "Advanced" -> "Enable ADB"
3. Check your DDR type using the following command:
adb shell getprop ro.boot.ddr_type
or in case getprop returns an empty value, use:
adb shell cat /proc/devinfo/ddr_type
4. Download firmware (C33 recommended, minimum C20/21 required) from here:
FirmWares - Google Drive
drive.google.com
5. Go to "Advanced" -> "Enter fastbootd"
6. Execute following commands after opening a command line in the fw directory:
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all featenabler featenabler.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all imagefv imagefv.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all logo logo.img
fastboot flash --slot=all mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all multiimgoem multiimgoem.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all spunvm spunvm.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all uefisecapp uefisecapp.img
7. Flash correct XBL files
* For DDR type 0 (DDR4):
fastboot flash --slot=all xbl_config xbl_config.img
fastboot flash --slot=all xbl xbl.img
* For DDR type 1 (DDR5):
fastboot flash --slot=all xbl_config xbl_config_lp5.img
fastboot flash --slot=all xbl xbl_lp5.img
8. Boot your recovery from here and then install the new update:
Android12L - Google Drive
drive.google.com
9. Now, you can update via OTA safely.
IF YOU ARE ON STOCK OOS12
These instructions are for you:
Spoiler
Thanks to @Anierin_Bliss
First Time Install / Clean Flash
1. Have an unlocked bootloader & OOS 12 (C20 - C33) flashed to both slots.
2. Download vbmeta, recovery, ROM and GAPPS (optional) for your device from here: https://drive.google.com/drive/folders/1A2SeD6YFKJ2S-iiAKmyfgnrEeJz8zjNm
3. Reboot to bootloader
4.
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
5. While in recovery, navigate to Apply update -> Apply from ADB
6. adb sideload ROM.zip -> reboot recovery -> adb sideload GAPPS.zip
7. Format data, reboot to system & Enjoy !

Hi thanks all for your tremendous efforts
If we are on OOS 12 then do we have to revert to OOS11 ?

adsxlnc said:
Hi thanks all for your tremendous efforts
If we are on OOS 12 then do we have to revert to OOS11 ?
Click to expand...
Click to collapse
We are preparing OOS 12 based trees. Till then, yes - please go back to latest OOS 11 then flash AICP. 12.1

What a pleasant surprise, love your work semdoc, can't wait to get home and flash this.

Wow great rom, I was looking for one with the built in adblock and no gapps. Fast, smooth, and very light weight. I also love the custom work you did on the QS <3

Amazing work, I like the easy to follow instructions as well. I was on the Tmobile version that was OOS 11. After a long research I flashed the global version of OOS 10, then OTA to OOS 11. I tried to flash multiple different A12 roms, but all of them crashed. This was the only A12 rom that worked for me. The system runs smoothly, I also like all the added features. I used MindTheGapps and Magisk 25.1, both work correctly. I then used Konabess to overclock the gpu to 925 MHz.

Issilar said:
Amazing work, I like the easy to follow instructions as well. I was on the Tmobile version that was OOS 11. After a long research I flashed the global version of OOS 10, then OTA to OOS 11. I tried to flash multiple different A12 roms, but all of them crashed. This was the only A12 rom that worked for me. The system runs smoothly, I also like all the added features. I used MindTheGapps and Magisk 25.1, both work correctly. I then used Konabess to overclock the gpu to 925 MHz.
Click to expand...
Click to collapse
Have you try Nameless rom ever brother,, i have the same t mobile version of ur phone,, nameless isnt work for me. qualcomn crash damp happened

Hiya! I've turned on the always-on display, and have noticed that i have to turn the screen on to get the fingerprint sensor to work (most of the time. I think it's active a few seconds after screen lock?)! Is there any way around this? OxygenOS seemed to turn the sensor on with a finger press no matter the AOD state
cheers!

Hey I was on T-Mobile Android 11. I tried to unlock the bootloader and flashed this ROM. The phone does not capture the network anymore. Also the GAPPS installation via adb sideload is failing. Any idea?

ditomathew said:
Hey I was on T-Mobile Android 11. I tried to unlock the bootloader and flashed this ROM. The phone does not capture the network anymore. Also the GAPPS installation via adb sideload is failing. Any idea?
Click to expand...
Click to collapse
I've had other roms do this before, run MSM restore tool, then unlock bootloader (and adb debugging) then re do the installation

RogueVisual said:
I've had other roms do this before, run MSM restore tool, then unlock bootloader (and adb debugging) then re do the installation
Click to expand...
Click to collapse
Thanks I did that, and now I reinstalled.

allen-evan said:
Have you try Nameless rom ever brother,, i have the same t mobile version of ur phone,, nameless isnt work for me. qualcomn crash damp happened
Click to expand...
Click to collapse
Nameless works just fine on my device, TMO OP8

Small but IMPORTANT note for anybody experiencing issues coming from OOS and trying this for the first time. I could not get the ROM to boot until I flashed the "copy partitions" zip from Lineage. (https://wiki.lineageos.org/devices/...suring-all-firmware-partitions-are-consistent).
Until I flashed this I would install the ROM and then try to reboot to recovery and it would go straight to the bootloader. If I switched back to the other slot I could get back to recovery but could not proceed further.
So my install instructions looked like this: (because I was doing some trial and error I had installed the ROM a few times hence it being here twice)
adb sideload ROM.zip (I believe you can skip this one but cannot say for certain) -> adb sideload copy-partitions.zip -> adb sideload ROM.zip -> reboot to recovery -> adb sideload GAPPS.zip -> reboot to system
If you get stuck on the bootloader you can use fastboot to check your active slot and then switch back to the previous slot to get back into recovery.
Check current slot:
Code:
fastboot getvar all
Look for the line that says:
Code:
(bootloader) current-slot
The two options are "a" or "b". Then switch to the other slot with:
Code:
fastboot --set-active=a
OR
Code:
fastboot --set-active=b
Another small note, "Apply Update > Install from ADB" (terms are from memory, should be close enough) inside of the Lineage Recovery is what you are looking for to enter adb sideload mode. I had used TWRP previously and didn't know how to get this working at first in Lineage Recovery.

is it possible
to install with official twrp recovery ??

Does this rom works with OnePlus 8 Verizon 5G UW (IN2019)? Does the SIM work?

I tried using the Android 12 based builds but end up in soft-bricked state every time where only MSM can recover. Why is this?
I have T-Mobile OP8, unlocked. I just MSM back to A10, unlock bootloader, convert to global, update to latest A11, install lineage recovery, flash EU A12 firmware, flash ROM, reboot to bootloader -> softbricked at this point with QDLoader in device manager.
Tried asking in telegram but the bot banned me for flooding for sending exactly 1 message.

graycorgi said:
I tried using the Android 12 based builds but end up in soft-bricked state every time where only MSM can recover. Why is this?
I have T-Mobile OP8, unlocked. I just MSM back to A10, unlock bootloader, convert to global, update to latest A11, install lineage recovery, flash EU A12 firmware, flash ROM, reboot to bootloader -> softbricked at this point with QDLoader in device manager.
Tried asking in telegram but the bot banned me for flooding for sending exactly 1 message.
Click to expand...
Click to collapse
ROM {Firmware|Vendor} required: Latest OOS 11

Larkin24 said:
ROM {Firmware|Vendor} required: Latest OOS 11
Click to expand...
Click to collapse
They have ones for Android 12 firmware on their support telegram channel for this device (link in OP). I only posted here because their telegram bot bans you without warning if you type too long of a message.

graycorgi said:
They have ones for Android 12 firmware on their support telegram channel for this device (link in OP). I only posted here because their telegram bot bans you without warning if you type too long of a message.
Click to expand...
Click to collapse
SORRY NO OOS 11
I have the same phone OOS 11 Firmware.
Latest tmoble Firmware
OnePlus Updates Tracker
An automated channel that tracks OnePlus Oxygen and Hydrogen OS ROMs releases. https://github.com/androidtrackers/oneplus-updates-tracker More automated channels that you may like: @yshalsager_projects Developed by: @yshalsager
t.me

Database Info

welcome