Development [CLOSED][ROM][OOSCAM][OFFICIAL][OnePlus 9][12.1.0_r22]Nameless AOSP[2022/08/31]

Status
Not open for further replies.
Search This thread

papad13

Senior Member
Jan 23, 2009
76
16
can you please explain this process? coming from oneplus 8 and this part of the process is all new to me i keep getting messages about downgrades and the flash not working.
Just go to another rom-thrend and checkout the process.
1. Unlock bootloader (if it's unlocked ok)
2. Go fastboot and "fastboot vedor,dtbo and boot " images
3. Reboot to recovery from fastboot and factory/data reset.
4. Sideload the ROM "
 

applyscience

Senior Member
Nov 25, 2016
231
75
OnePlus 9

tuckandroll

marcelobra1

Nameless will require at least C62 (C63 is confirmed working and maintainer stated as much. The important part is the lineage image you use.) in both slots. Since c62(or higher) is only available via a incremental update, its not flashed like other images. So you will use a copy script once you are back on OOS, updated and unlocked.


Since i tagged two of you, I may go over more than you need to be told or applicable to, just read and follow whatever part you need help with.

Backup

--------------------------------------------------------------------------
Do a backup with your choice. google alone or a 3rd party offering, if you have more apps than what google offers in the play store(f-droid, etc)
I like migrate.(https://play.google.com/store/search?q=migrate&c=apps) it's a pretty simple process, just follow the prompts. If you use google at all to login, just backup the apps, not adb state, font size, contact, you know the drill.

This will still not backup your files! (pictures/music/downloads) I have no faith in full backup solutions in this stage of android. your best to cloud or copy them out manually.

Get back on OOS/get needed files

----------------------------------------------------------------------------------------------------

  • Use MSMToolkit first to get back to OOS. Start this first and work on getting everything else prepped while you wait between MSM/OOS updates. Update it until it can't be updated anymore.​
  • Unlock the bootloader and let it wipe and get back in, so you can enable adb again.​
  • Download this exact lineage image to extract its dtbo.img, boot.img and vendor_boot.img https://mirror.math.princeton.edu/pub/lineageos/full/lemonade/20220807/
  • *Caution* I have uploaded the 3 img files and copy-partitons.zip to mega.nz if you need. I do not suggest you use them as you are taking yourself out of the process of verification and thus, if something goes wrong, you have no idea if any of these were the cause or not. That being said, if you don't care. all 4 files are right here
  • the easiest way to extract images on windows is to use fastboot enhance (github / XDA Thread)​
    • in fastboot enhance, it's as simple as clicking the payload dumper tab,​
    • clicking browse, select the lineage file you downloaded and once loaded​
    • select the Partitions tab below the original tabs.​
    • While holding down ctrl on your keyboard, click boot, dtbo and vendor_boot, to highlight all 3 at once. click extract.​
    • Put the 3 files where your fastboot latest Namless image zip is.​
  • Download this copy of partitions zip. Put it in your fastboot folder​
  • Grab the latest magisk.apk if you plan on rooting and rename it from .apk to .zip​
  • and of course the latest Nameless image

Copy Partitions/Flash Nameless Time​

-----------------------------------------------------------------------------------

With everything you downloaded in your fastboot folder, type cmd in the top bar to quick open a command prompt with that location as its starting point. You should now be in cmd with your phone connected, fully updated and unlocked again (not root, just unlocked) with adb enabled again. Type
adb reboot bootloader and check your phone, if it's not rebooting, make sure you granted adb access to your pc on the phone itself. you should be prompted once that is ran. Your phone should now be in fastboot. Now flash the 3 image files we got from lineage

fastboot flash dtbo dtbo.img fastboot flash boot boot.im fastboot flash vendor_boot vendor_boot.img

  • boot into the lineage recovery by using the volume keys to change to "boot to recovery" and confirming with the power button or run the command below​
fastboot reboot recovery

  • To copy the current partition to the other. Select Apply Update and then Apply from ADB. Back in the command prompt, type​

adb sideload copy-partitions-20210323_1922.zip

  • Make sure it initiates. Since its signature isn't verified, (i think?) you should have to click yes to force it via your phone.
  • Once complete, click the back arrow and select Advanced>Reboot to Recovery
  • factory reset/format data. Once complete, in the same recovery, back arrow to main menu and apply the Nameless Rom.​

adb sideload Nameless-AOSP_lemonade-12.1-20220825-1712-Official.zip

  • Once this is complete, back arrow, advanced, Reboot to recovery again.​
  • You should notice the recovery is no longer branded with a lineage logo at the top, but with nameless's logo.​
  • Factory reset again.​
  • Reboot after factory if you aren't rooting, but If you want magisk, in the same recovery apply it and then reboot into your phone​

adb sideload Magisk-v25.2.zip


Thank you for joining my ted talk.
 
Last edited:

tuckandroll

Senior Member
Aug 1, 2012
283
61
Rochelle Park, NJ

tuckandroll

marcelobra1

Nameless will require C62 in both slots. Since c62 is only available via a incremental update, its not flashed like other images. So you will use a copy script once you are back on OOS, updated and unlocked.


Since i tagged two of you, I may go over more than you need to be told or applicable to, just read and follow whatever part you need help with.

Backup

--------------------------------------------------------------------------
Do a backup with your choice. google alone or a 3rd party offering, if you have more apps than what google offers in the play store(f-droid, etc)
I like migrate.(https://play.google.com/store/search?q=migrate&c=apps) it's a pretty simple process, just follow the prompts. If you use google at all to login, just backup the apps, not adb state, font size, contact, you know the drill.

This will still not backup your files! (pictures/music/downloads) I have no faith in full backup solutions in this stage of android. your best to cloud or copy them out manually.

Get back on OOS/get needed files

----------------------------------------------------------------------------------------------------

  • Use MSMToolkit first to get back to OOS. Start this first and work on getting everything else prepped while you wait between MSM/OOS updates. Update it until it can't be updated anymore.​
  • Unlock the bootloader and let it wipe and get back in, so you can enable adb again.​
  • Download this exact lineage image to extract its dtbo.img, boot.img and vendor_boot.img https://mirror.math.princeton.edu/pub/lineageos/full/lemonade/20220807/
  • *Caution* I have uploaded the 3 img files and copy-partitons.zip to mega.nz if you need. I do not suggest you use them as you are taking yourself out of the process of verification and thus, if something goes wrong, you have no idea if any of these were the cause or not. That being said, if you don't care. all 4 files are right here
  • the easiest way to extract images on windows is to use fastboot enhance (github / XDA Thread)​
    • in fastboot enhance, it's as simple as clicking the payload dumper tab,​
    • clicking browse, select the lineage file you downloaded and once loaded​
    • select the Partitions tab below the original tabs.​
    • While holding down ctrl on your keyboard, click boot, dtbo and vendor_boot, to highlight all 3 at once. click extract.​
    • Put the 3 files where your fastboot latest Namless image zip is.​
  • Download this copy of partitions zip. Put it in your fastboot folder​
  • Grab the latest magisk.apk if you plan on rooting and rename it from .apk to .zip​
  • and of course the latest Nameless image

Copy Partitions/Flash Nameless Time​

-----------------------------------------------------------------------------------

With everything you downloaded in your fastboot folder, type cmd in the top bar to quick open a command prompt with that location as its starting point. You should now be in cmd with your phone connected, fully updated and unlocked again (not root, just unlocked) with adb enabled again. Type
adb reboot bootloader and check your phone, if it's not rebooting, make sure you granted adb access to your pc on the phone itself. you should be prompted once that is ran. Your phone should now be in fastboot. Now flash the 3 image files we got from lineage

fastboot flash dtbo dtbo.img fastboot flash boot boot.im fastboot flash vendor_boot vendor_boot.img

  • boot into the lineage recovery by using the volume keys to change to "boot to recovery" and confirming with the power button or run the command below​
fastboot reboot recovery

  • To copy the current partition to the other. Select Apply Update and then Apply from ADB. Back in the command prompt, type​

adb sideload copy-partitions-20210323_1922.zip

  • Make sure it initiates. Since its signature isn't verified, (i think?) you should have to click yes to force it via your phone.

  • Once complete, click the back arrow and select Advanced>Reboot to Recovery
  • factory reset/format data. Once complete, in the same recovery, back arrow to main menu and apply the Nameless Rom.​

adb sideload Nameless-AOSP_lemonade-12.1-20220825-1712-Official.zip

  • Once this is complete, back arrow, advanced, Reboot to recovery again.​
  • You should notice the recovery is no longer branded with a lineage logo at the top, but with nameless's logo.​
  • Factory reset again. If you want magisk, in the same recovery apply it and then reboot into your phone​

adb sideload Magisk-v25.2.zip


Thank you for joining my ted talk.
This is amazing Will try later today and report back.
 

tuckandroll

Senior Member
Aug 1, 2012
283
61
Rochelle Park, NJ

tuckandroll

marcelobra1

Nameless will require C62 in both slots. Since c62 is only available via a incremental update, its not flashed like other images. So you will use a copy script once you are back on OOS, updated and unlocked.


Since i tagged two of you, I may go over more than you need to be told or applicable to, just read and follow whatever part you need help with.

Backup

--------------------------------------------------------------------------
Do a backup with your choice. google alone or a 3rd party offering, if you have more apps than what google offers in the play store(f-droid, etc)
I like migrate.(https://play.google.com/store/search?q=migrate&c=apps) it's a pretty simple process, just follow the prompts. If you use google at all to login, just backup the apps, not adb state, font size, contact, you know the drill.

This will still not backup your files! (pictures/music/downloads) I have no faith in full backup solutions in this stage of android. your best to cloud or copy them out manually.

Get back on OOS/get needed files

----------------------------------------------------------------------------------------------------

  • Use MSMToolkit first to get back to OOS. Start this first and work on getting everything else prepped while you wait between MSM/OOS updates. Update it until it can't be updated anymore.​
  • Unlock the bootloader and let it wipe and get back in, so you can enable adb again.​
  • Download this exact lineage image to extract its dtbo.img, boot.img and vendor_boot.img https://mirror.math.princeton.edu/pub/lineageos/full/lemonade/20220807/
  • *Caution* I have uploaded the 3 img files and copy-partitons.zip to mega.nz if you need. I do not suggest you use them as you are taking yourself out of the process of verification and thus, if something goes wrong, you have no idea if any of these were the cause or not. That being said, if you don't care. all 4 files are right here
  • the easiest way to extract images on windows is to use fastboot enhance (github / XDA Thread)​
    • in fastboot enhance, it's as simple as clicking the payload dumper tab,​
    • clicking browse, select the lineage file you downloaded and once loaded​
    • select the Partitions tab below the original tabs.​
    • While holding down ctrl on your keyboard, click boot, dtbo and vendor_boot, to highlight all 3 at once. click extract.​
    • Put the 3 files where your fastboot latest Namless image zip is.​
  • Download this copy of partitions zip. Put it in your fastboot folder​
  • Grab the latest magisk.apk if you plan on rooting and rename it from .apk to .zip​
  • and of course the latest Nameless image

Copy Partitions/Flash Nameless Time​

-----------------------------------------------------------------------------------

With everything you downloaded in your fastboot folder, type cmd in the top bar to quick open a command prompt with that location as its starting point. You should now be in cmd with your phone connected, fully updated and unlocked again (not root, just unlocked) with adb enabled again. Type
adb reboot bootloader and check your phone, if it's not rebooting, make sure you granted adb access to your pc on the phone itself. you should be prompted once that is ran. Your phone should now be in fastboot. Now flash the 3 image files we got from lineage

fastboot flash dtbo dtbo.img fastboot flash boot boot.im fastboot flash vendor_boot vendor_boot.img

  • boot into the lineage recovery by using the volume keys to change to "boot to recovery" and confirming with the power button or run the command below​
fastboot reboot recovery

  • To copy the current partition to the other. Select Apply Update and then Apply from ADB. Back in the command prompt, type​

adb sideload copy-partitions-20210323_1922.zip

  • Make sure it initiates. Since its signature isn't verified, (i think?) you should have to click yes to force it via your phone.

  • Once complete, click the back arrow and select Advanced>Reboot to Recovery
  • factory reset/format data. Once complete, in the same recovery, back arrow to main menu and apply the Nameless Rom.​

adb sideload Nameless-AOSP_lemonade-12.1-20220825-1712-Official.zip

  • Once this is complete, back arrow, advanced, Reboot to recovery again.​
  • You should notice the recovery is no longer branded with a lineage logo at the top, but with nameless's logo.​
  • Factory reset again. If you want magisk, in the same recovery apply it and then reboot into your phone​

adb sideload Magisk-v25.2.zip


Thank you for joining my ted talk.
doing the final OTA now. its C.63 is that going to mess this up?
 

tuckandroll

Senior Member
Aug 1, 2012
283
61
Rochelle Park, NJ

tuckandroll

marcelobra1

Nameless will require C62 in both slots. Since c62 is only available via a incremental update, its not flashed like other images. So you will use a copy script once you are back on OOS, updated and unlocked.


Since i tagged two of you, I may go over more than you need to be told or applicable to, just read and follow whatever part you need help with.

Backup

--------------------------------------------------------------------------
Do a backup with your choice. google alone or a 3rd party offering, if you have more apps than what google offers in the play store(f-droid, etc)
I like migrate.(https://play.google.com/store/search?q=migrate&c=apps) it's a pretty simple process, just follow the prompts. If you use google at all to login, just backup the apps, not adb state, font size, contact, you know the drill.

This will still not backup your files! (pictures/music/downloads) I have no faith in full backup solutions in this stage of android. your best to cloud or copy them out manually.

Get back on OOS/get needed files

----------------------------------------------------------------------------------------------------

  • Use MSMToolkit first to get back to OOS. Start this first and work on getting everything else prepped while you wait between MSM/OOS updates. Update it until it can't be updated anymore.​
  • Unlock the bootloader and let it wipe and get back in, so you can enable adb again.​
  • Download this exact lineage image to extract its dtbo.img, boot.img and vendor_boot.img https://mirror.math.princeton.edu/pub/lineageos/full/lemonade/20220807/
  • *Caution* I have uploaded the 3 img files and copy-partitons.zip to mega.nz if you need. I do not suggest you use them as you are taking yourself out of the process of verification and thus, if something goes wrong, you have no idea if any of these were the cause or not. That being said, if you don't care. all 4 files are right here
  • the easiest way to extract images on windows is to use fastboot enhance (github / XDA Thread)​
    • in fastboot enhance, it's as simple as clicking the payload dumper tab,​
    • clicking browse, select the lineage file you downloaded and once loaded​
    • select the Partitions tab below the original tabs.​
    • While holding down ctrl on your keyboard, click boot, dtbo and vendor_boot, to highlight all 3 at once. click extract.​
    • Put the 3 files where your fastboot latest Namless image zip is.​
  • Download this copy of partitions zip. Put it in your fastboot folder​
  • Grab the latest magisk.apk if you plan on rooting and rename it from .apk to .zip​
  • and of course the latest Nameless image

Copy Partitions/Flash Nameless Time​

-----------------------------------------------------------------------------------

With everything you downloaded in your fastboot folder, type cmd in the top bar to quick open a command prompt with that location as its starting point. You should now be in cmd with your phone connected, fully updated and unlocked again (not root, just unlocked) with adb enabled again. Type
adb reboot bootloader and check your phone, if it's not rebooting, make sure you granted adb access to your pc on the phone itself. you should be prompted once that is ran. Your phone should now be in fastboot. Now flash the 3 image files we got from lineage

fastboot flash dtbo dtbo.img fastboot flash boot boot.im fastboot flash vendor_boot vendor_boot.img

  • boot into the lineage recovery by using the volume keys to change to "boot to recovery" and confirming with the power button or run the command below​
fastboot reboot recovery

  • To copy the current partition to the other. Select Apply Update and then Apply from ADB. Back in the command prompt, type​

adb sideload copy-partitions-20210323_1922.zip

  • Make sure it initiates. Since its signature isn't verified, (i think?) you should have to click yes to force it via your phone.

  • Once complete, click the back arrow and select Advanced>Reboot to Recovery
  • factory reset/format data. Once complete, in the same recovery, back arrow to main menu and apply the Nameless Rom.​

adb sideload Nameless-AOSP_lemonade-12.1-20220825-1712-Official.zip

  • Once this is complete, back arrow, advanced, Reboot to recovery again.​
  • You should notice the recovery is no longer branded with a lineage logo at the top, but with nameless's logo.​
  • Factory reset again. If you want magisk, in the same recovery apply it and then reboot into your phone​

adb sideload Magisk-v25.2.zip


Thank you for joining my ted talk.
It worked! thanks for the detailed assistance you rock.
 
  • Like
Reactions: applyscience

BKZAMAK

Member
Dec 8, 2020
18
0
If i use c62 then flash Nameless 20220825 and c63 then flash Nameless 20220825 is there any difference?
 

applyscience

Senior Member
Nov 25, 2016
231
75
OnePlus 9
If i use c62 then flash Nameless 20220825 and c63 then flash Nameless 20220825 is there any difference?
the OOS starting point shouldn't matter as long as its past c62. C63 has been confirmed 2 comments before yours and the maintainer stated as much in the release announcement of the latest update in this thread. the important part of flashing is what lineage version you use to grab your required image files. (https://mirror.math.princeton.edu/pub/lineageos/full/lemonade/20220807/)

a few posts above, i explained the whole process, if you need help at any point of the process.
 
Last edited:

Z-Blade

Senior Member
Jan 29, 2012
647
274
Perth

tuckandroll

marcelobra1

Nameless will require at least C62 (C63 is confirmed working and maintainer stated as much. The important part is the lineage image you use.) in both slots. Since c62(or higher) is only available via a incremental update, its not flashed like other images. So you will use a copy script once you are back on OOS, updated and unlocked.


Since i tagged two of you, I may go over more than you need to be told or applicable to, just read and follow whatever part you need help with.

Backup

--------------------------------------------------------------------------
Do a backup with your choice. google alone or a 3rd party offering, if you have more apps than what google offers in the play store(f-droid, etc)
I like migrate.(https://play.google.com/store/search?q=migrate&c=apps) it's a pretty simple process, just follow the prompts. If you use google at all to login, just backup the apps, not adb state, font size, contact, you know the drill.

This will still not backup your files! (pictures/music/downloads) I have no faith in full backup solutions in this stage of android. your best to cloud or copy them out manually.

Get back on OOS/get needed files

----------------------------------------------------------------------------------------------------

  • Use MSMToolkit first to get back to OOS. Start this first and work on getting everything else prepped while you wait between MSM/OOS updates. Update it until it can't be updated anymore.​
  • Unlock the bootloader and let it wipe and get back in, so you can enable adb again.​
  • Download this exact lineage image to extract its dtbo.img, boot.img and vendor_boot.img https://mirror.math.princeton.edu/pub/lineageos/full/lemonade/20220807/
  • *Caution* I have uploaded the 3 img files and copy-partitons.zip to mega.nz if you need. I do not suggest you use them as you are taking yourself out of the process of verification and thus, if something goes wrong, you have no idea if any of these were the cause or not. That being said, if you don't care. all 4 files are right here
  • the easiest way to extract images on windows is to use fastboot enhance (github / XDA Thread)​
    • in fastboot enhance, it's as simple as clicking the payload dumper tab,​
    • clicking browse, select the lineage file you downloaded and once loaded​
    • select the Partitions tab below the original tabs.​
    • While holding down ctrl on your keyboard, click boot, dtbo and vendor_boot, to highlight all 3 at once. click extract.​
    • Put the 3 files where your fastboot latest Namless image zip is.​
  • Download this copy of partitions zip. Put it in your fastboot folder​
  • Grab the latest magisk.apk if you plan on rooting and rename it from .apk to .zip​
  • and of course the latest Nameless image

Copy Partitions/Flash Nameless Time​

-----------------------------------------------------------------------------------

With everything you downloaded in your fastboot folder, type cmd in the top bar to quick open a command prompt with that location as its starting point. You should now be in cmd with your phone connected, fully updated and unlocked again (not root, just unlocked) with adb enabled again. Type
adb reboot bootloader and check your phone, if it's not rebooting, make sure you granted adb access to your pc on the phone itself. you should be prompted once that is ran. Your phone should now be in fastboot. Now flash the 3 image files we got from lineage

fastboot flash dtbo dtbo.img fastboot flash boot boot.im fastboot flash vendor_boot vendor_boot.img

  • boot into the lineage recovery by using the volume keys to change to "boot to recovery" and confirming with the power button or run the command below​
fastboot reboot recovery

  • To copy the current partition to the other. Select Apply Update and then Apply from ADB. Back in the command prompt, type​

adb sideload copy-partitions-20210323_1922.zip

  • Make sure it initiates. Since its signature isn't verified, (i think?) you should have to click yes to force it via your phone.
  • Once complete, click the back arrow and select Advanced>Reboot to Recovery
  • factory reset/format data. Once complete, in the same recovery, back arrow to main menu and apply the Nameless Rom.​

adb sideload Nameless-AOSP_lemonade-12.1-20220825-1712-Official.zip

  • Once this is complete, back arrow, advanced, Reboot to recovery again.​
  • You should notice the recovery is no longer branded with a lineage logo at the top, but with nameless's logo.​
  • Factory reset again.​
  • Reboot after factory if you aren't rooting, but If you want magisk, in the same recovery apply it and then reboot into your phone​

adb sideload Magisk-v25.2.zip


Thank you for joining my ted talk.
This is awesome, it should be linked into OP.
 

TMSxXDA

Senior Member
Jun 8, 2009
113
18
Hi, are there any options during installation process to install the rom without GAps, but to keep MicroG? Or maybe to choose which apps will be installed? thank you.
This rom seems the best for me, because it is slightly more privacy oriented since it based on LOS, and have stock camera port.
 

applyscience

Senior Member
Nov 25, 2016
231
75
OnePlus 9
Hi, are there any options during installation process to install the rom without GAps, but to keep MicroG? Or maybe to choose which apps will be installed? thank you.
This rom seems the best for me, because it is slightly more privacy oriented since it based on LOS, and have stock camera port.
Usually, I always prefer managing my own GApps as well but Nameless is a pixel-clone ROM like pixen or Pixel Experience, etc.Offering a Vinilla build isnt really priority for a ROM like that.

I think Nameless is great enough and offers way more than just a Pixel experience, but it is what it is and if any ROM can justify not offering a GApps variant, its one that offers all things pixel can and more.

so no. just debloat what you dont want or find a Gapps optional ROM
 

TMSxXDA

Senior Member
Jun 8, 2009
113
18
Usually, I always prefer managing my own GApps as well but Nameless is a pixel-clone ROM like pixen or Pixel Experience, etc.Offering a Vinilla build isnt really priority for a ROM like that.

I think Nameless is great enough and offers way more than just a Pixel experience, but it is what it is and if any ROM can justify not offering a GApps variant, its one that offers all things pixel can and more.

so no. just debloat what you dont want or find a Gapps optional ROM
Got it, thank you.
Is it a similar situation with crDroid rom to your knowledge? it seems now they also managed to port stock camera, thx.
 

chandu dyavanapelli

Senior Member
Mar 30, 2019
460
931
Hyderabad
OnePlus 8T
OnePlus 9 Pro
New Build up!

Apologize for broken build, Anyway happy to share quick hotfix builds :)

Hotfix changelog:
- Fixed crash in Face & Fingerprint unlock page
- Fixed Instagram or other social media apps get signed out in every reboot

Device changelog:
- Fixed Slow Charging (if anyone still face slow charging then do re-plug charging cable probably this will be happen when device temperature cross above 40°c)
- Fixed OPlus Camera crashing in AI ultra clear mode
- Fixed HDR and LOG submode in movie mode having random Green / Pink screen in recorded videos
- Fixed Long Exposure mode not working for some users
- Merged Linux stable 'v5.4.211' tag in kernel
- Merged CodeLinaro OSS "LA.UM.9.14.r1-20200-LAHAINA.QSSI13.0" tag in kernel
- Improved idle drain
 
  • Like
Reactions: Skye.life and reffu
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 12
    nameless_logo.png

    Nameless AOSP for OnePlus 9 [lemonade]

    Nameless AOSP is based on Android Open Source Project, inspired by Google Pixel. We offer a smooth and stable experience for your device with a selected set of amazing features that provide an exceptional user experience.

    Whats working?
    Everything working :)

    Known issues

    Nothing yet
    You tell me


    Flash Instructions

    Download
    DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED !

    Donate
    Chris Chen PayPal
    Chandu Dyavanapelli PayPal
    UPI ID: [email protected]


    Team
    Chris Chen - Founder & lead Developer
    Chandu Dyavanapelli - Co Founder & lead Developer

    Credits
    Android Open-Source Project
    Pixel Experience
    AospExtended
    Proton AOSP

    LineageOS
    Havoc OS
    Arrow OS
    Krypton


    Others, I may have forgot to mention


    Stay tuned
    Our Telegram Group

    10
    Nameless back :)

    New build up!

    Note
    - Clean flash recommended

    Source Changelog
    - Merged May security patch (android-12.1.0_r5)
    - Introduce automated sleep mode
    - Implement background process killer
    - Added preferred network QS tile to quick switch between 4g/5g
    - Added expanded volume panel
    - Added switch data saver icon
    - Added game props for mobile legends
    - Added customize tiles layout in QS panel
    - Added more hotspot settings (AP Band, Hidden network, Device blacklist etc)
    - Added sound QS tile
    - Added AdGuard & Cloudflare private DNS providers
    - Added Custom carrier label & Carrier label placement
    - Added Dora & Weed status bar icons
    - Allow alert slider changes in pocket mode
    - Allow adding some system apps into app lock list
    - Allow to ignore secure flag for windows (Remove screenshot & screenrecord limits)
    - Allow to force show media controller in volume dialog
    - Allow 2 more columns for qs tiles
    - Allow to hide back gesture arrow
    - Allow to switch slot in recovery for AB devices
    - Disable face enroll on Setup Wizard
    - Force fullscreen for Google Dialer
    - Use Mi 11 Ultra games prop for mobile Legends
    - Refactor updater app
    - Fixed random misplaced qs tiles layout
    - Fixed unconditional qs panel expansion in settings
    - Fixed glitchy charging info on lockscreen
    - Fixed auto answer call triggered even after turning off game mode
    - Fixed notification overlay spam with old messages in game mode
    - Fixed weird lockscreen clock font
    - Fixed partial screenshot
    - Fixed wireless emergency alerts crash in settings
    - Fixed pixel launcher search bar color in light mode

    Device Changelog
    - Initial Android 12.1/12L build
    - Switch to user build
    - Switch to los kernel
    - Improved haptic feedback
    - Improved battery backup and performance
    - Update blobs, configs, props and vendor scripts from LA.UM.9.14.r1-18900-LAHAINA.QSSI12.0
    - Update CarrierConfig from OOS 12 LE2121_11.C.48
    - Fixed WiFi Display
    - Fixed telephony crash on first boot
    - Fixed Warp Charging not displaying in lockscreen
    - Fixed color modes
    - Make slider haptic feedback progressive
    - Refactor OnePlusSettings
    - Refactor and cleanup device tree and sync latest los changes
    7
    Nameless AOSP is updated once every two months?
    Nope. I dropped and re-added support now. New build may be release every 1 or 2 weeks
    4
    New Build Up!

    Source Changelog:
    - Added App Lock
    - Added Face Unlock
    - Added more fonts
    - Fixed gaming mode settings not applied when overlay menu is disabled
    - Removed logo in settings. Simple best :)
    - Misc cleanup and improvement

    Device Changelog:
    - Added DaxUI Dolby Atmos
    4
    New build up

    Note
    - Supported latest Oxygen or Hydrogen OS 11 firmware
    - Dirty flash from early build is fine

    Source changelog
    - Added support to show battery info in settings
    - Improved scheduled AOD/Sleep mode
    - Fixed black theme for QS Panel
    - Improved reTicker
    - NamelessLauncher: Allow to apply themed icon for app drawer
    - NamelessLauncher: Fixed hidden apps
    - PixelLauncher & NamelessLauncher: Import more themed icon
    - Lawnchair: Updated to latest dev build
    - Minor cleanup & improvements

    Device changelog
    - Fixed stutters
    - Disable lockscreen charging remaining time (Reason for disable: It's show inaccurate result)
    - Switched partial blobs back to stock OOS (You may need to repair your bluetooth devices)