[ROM][OFFICIAL][OOS CAM][OnePlus 8T/9R][12.1.0_r11]Nameless AOSP[2022/07/23]

Search This thread

wizzman

Senior Member
Apr 26, 2011
152
25
Senlis
Xiaomi Mi 9
OnePlus 8
When i write this command: fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img, I've this message: C:\Android\fastboot.exe: unknown option -- disable-verity (and --disable-verity --disable-verification is greyed out), someone can help me ?
 

kairi033

Senior Member
Sep 3, 2012
60
3
I just stumbled upon this Custom Rom today after rolling back to A11 last week just to be able to use VOLTE again. I was using A12 C.33 and there is no way to toggle on the VOLTE provision on A12 without root.

quick question/clarifications

1.) I saw in this thread that the widevine is working - are they talking about widevine L1? does this mean with an unlocked bootloader widevine L1 is still working?
2.) If I flash this custom ROM, do still need to activate my carrier's VOLTE using the PDC method? if yes. would be still the same procedure with OOS?
[a.) reboot FTM b.)ADB shell, c.) set.prop...... d.) open PDC e.) change active VOLTE profile]

Thank you.
 

janvs

Member
Jun 21, 2022
7
2
OnePlus 8T
When i write this command: fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img, I've this message: C:\Android\fastboot.exe: unknown option -- disable-verity (and --disable-verity --disable-verification is greyed out), someone can help me ?

From the wiki:
  • Use cmd, NOT powershell
  • Make sure platform-tools is the latest version
  • Make sure that the files you are going to flash are in the same folder with platform-tools
  • Make sure you opened cmd in the folder where platform-tools are
 
  • Like
Reactions: wizzman

Kapitastic

Member
May 5, 2015
12
2
I've managed to install the room, but I'm dissapointed to see that the 0.6 zoom in the camera doesn't work, is it normal? IN the first post it says that everything works fine. Well this doesn't work hahah.
 
Last edited:

blade227

Member
Jan 9, 2013
10
2
Hey guys,

I've asked this before but noone seems to have answered. I see that Wireguard is included in the source code for the Kernel, however after rooting and installing wireguard I am not able to enable the kernel backend. Anyone have a solution?
 

Bl4ck R1ver

Member
Apr 20, 2016
11
0
Guys, I need some help. I followed the instructions and everything went well until the last restart in the recovery. After the restart - black screen. I tried to install the rom again, but the recovery does not work aswell. I flashed the recovery image again, but still - black screen. I already unbricked the phone and installed the OOS12, but I want to try again with the Nameless ROM. Any idea what could went wrong? Thanks in advance!
 
Last edited:

rodken

Senior Member
Jan 11, 2010
1,264
518
You can't mess up a OnePlus phone.
That was the theory until I came across some developers that have either corrupted their data and/or partition on their device testing and building a new ROM/Kernel to a point that the motherboard does not and will not enter EDL Mode.
 

kim9096

Member
Oct 17, 2016
20
4
That was the theory until I came across some developers that have either corrupted their data and/or partition on their device testing and building a new ROM/Kernel to a point that the motherboard does not and will not enter EDL Mode.
I'm speaking as someone who just bricked a Xiaomi phone. Had to buy tool from sketchy telegram guy. Then finally can EDL unbrick the damn phone
 

dy2592

Senior Member
Oct 11, 2006
701
66
Guys, I need some help. I followed the instructions and everything went well until the last restart in the recovery. After the restart - black screen. I tried to install the rom again, but the recovery does not work aswell. I flashed the recovery image again, but still - black screen. I already unbricked the phone and installed the OOS12, but I want to try again with the Nameless ROM. Any idea what could went wrong? Thanks in advance!
Same thing for me. Last step after failing at 47%, I factory reset and wipe/format data.
Restarting the devices just gets me a black screen. No loading logo and eventually after a few minutes it will reboot continue this in a loop.
 

rodken

Senior Member
Jan 11, 2010
1,264
518
Same thing for me. Last step after failing at 47%, I factory reset and wipe/format data.
Restarting the devices just gets me a black screen. No loading logo and eventually after a few minutes it will reboot continue this in a loop.
The consortium of flashing fails/stops at 47% is somewhat of a known bug with ADB. It happened with me on 4 phones at exactly 47% too. I simply rebooted the phone after the few seconds of sitting at 47% and found it had actually successfully been flashed.

Factory reset or wiping data after the 47% might render your device useless.
 

dy2592

Senior Member
Oct 11, 2006
701
66
The consortium of flashing fails/stops at 47% is somewhat of a known bug with ADB. It happened with me on 4 phones at exactly 47% too. I simply rebooted the phone after the few seconds of sitting at 47% and found it had actually successfully been flashed.

Factory reset or wiping data after the 47% might render your device useless.
I actually tried this 2 times. The first time format data. I just tried to reboot and it had the blackscreen. The 2nd time I tried to follow the exact step by step in case I missed something and formatted data, same black screen.
 

rodken

Senior Member
Jan 11, 2010
1,264
518
I actually tried this 2 times. The first time format data. I just tried to reboot and it had the blackscreen. The 2nd time I tried to follow the exact step by step in case I missed something and formatted data, same black screen.
I missed the part where you have tried to install utilizing the fastboot method.

Sideload can be finicky. I've seen it fail and cause a lot of problems, where simply flashing from other means works just fine.
 

dy2592

Senior Member
Oct 11, 2006
701
66
I missed the part where you have tried to install utilizing the fastboot method.

Sideload can be finicky. I've seen it fail and cause a lot of problems, where simply flashing from other means works just fine.
oh I didnt know you could flash custom roms via command "fastboot update </path/to/your/RomFile.zip>.
Will try that now
 
  • Like
Reactions: rodken

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    There is no guide how to update from 12 to 13, but thanks. I guess the process is the same.

    It's in there, see attached.

    Just make sure you have C.33 or C.36 firmware in both slots.
    1
    did anyone compare the battery life of nameless aosp a13 to oos 12? (8t,thanks in advance)
    Battery life on Nameless A13 is definitely better. YMMV.
    1
    Hi. This rom (A13) is smoother and faster than OOS12 (OnePlus 8T). Thanks for this amazing rom. But it seems I'm the only one whose battery drains faster than OOS. What could it be?
    1
    got a new update today
  • 50
    nameless_logo.png

    Nameless AOSP for OnePlus 8T/9R [Unified Build] [kebab]

    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

    16
    New build up!

    Source Changelog:
    - Merged android-12.0.0_r32
    - Added App Lock
    - Added Face Unlock
    - Added more fonts
    - Fixed circle battery QS tinting
    - Fixed navbar inverse layout not working after reboot
    - Fixed gaming mode settings not applied when overlay menu is disabled
    - Removed logo in settings. Simple best :)
    - Misc cleanup and improvement

    Device Changelog:
    - Switch to DaxUI for dolby
    - Improved audio experiences
    - Fixed echo's in calls
    - Fixed low Mic issues in calls
    - Misc cleanup and improvement
    12
    I went through this yesterday evening and hit many snags and confusions due to looking up different posts... So I thought I'd write down my process in the hope it helps others.

    Before you begin
    • Backup of all Data, Fully charged battery, really backup all your data
    • Know how to use Windows command prompt, move files and folders about in explorer (or know how to set the PATH variable)
    • Follow this guide at your own risk!

    Downloads

    Set-up
    1. Install ADB + QualCom drivers. Reboot is required
    2. To check, connect phone to PC, reboot phone to fastboot, check device manager for anything with a yellow "!". Then repeat when in recovery. If you have issues here Fix this BEFORE continuing

    On PC
    1. Extract Nameless ROM zip
    2. Extract payload extractor zip
    3. copy payload.bin from ROM to payload_input folder where you extracted payload dumper
    4. Command prompt -> run payload_dumper.exe (takes about 5 minutes)
    5. In the payload_output folder will be .img files. You'll need these later

    Roll phone back to Android 11 with MSM tool
    1. Follow msm guide: https://www.getdroidtips.com/oneplus-msm-download-tool/. Took 900s to complete
    2. Complete first boot setup sequence, don't restore any data, skip as must as you can. Don't perform system udpate. Stop apps updating.
    3. Install Oxygen Updater -> Download KB2003_11_C.21 (Android 12) ~3.88Gb
    4. Whilst that's happening: Enable Developer Mode, Enable OEM Unlocking, Enable USB Debugging
    5. Once download complete, copy the update .zip file from root of phone to your PC
    Unlock bootloader
    1. In command window: adb reboot fastboot
    2. In command window: fastboot reboot bootloader (as soon as you press enter to run the command type and run the next one so it's waiting)
      • fastboot oem unlock
    3. Accept the text menu and phone will reboot and wipes itself
    Update phone to Android 12
    1. Clear setup asap, bypass / skip / ignore all you can
    2. Copy downloaded oxygen update from PC to root of phone
    3. Local install using Oxygen download file (ignore the system update) + reboot
    4. Enable USB Debugging
    5. In command window: adb devices -> ensure you're authorised
    6. In command windows: adb reboot fastboot
    On PC
    1. In command window: open the payload_output folder (with the extracted .img files from earlier):
      • fastboot flash boot boot.img
      • fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
      • fastboot flash --disable-verity --disable-verification vbmeta_system vbmeta_system.img
      • fastboot flash recovery recovery.img
    2. Use fastboot menus to reboot to recovery (new blue one)
    3. Press "Install update" -> "ADB Sideload"
    4. In command window: adb devices - ensure it says "sideload" and not "unauthorised"
    5. In command window: adb sideload copy-partitions-20210323_1922.zip
    6. Reboot recovery from menus on phone
    7. In command window: adb devices - ensure it says "sideload" and not unauthorised
    8. In command window: adb sideload Nameless-AOSP_kebab-12.1-20220723-1310-Official.zip
    9. Click back arrow in recovery, then click "Factory reset" -> "Format data/factory reset" -> "Format data"
    10. Click back arrow in recovery, then click "Reboot to system"
    If you miss a step and boot the phone it's likely not going to be stuffed. In this case, force it back to EDL mode (adb reboot edl) or hold the up + down volume buttons for ~40s and start with the MSM tool again.
    11
    New Build up!

    Note
    - Supported latest Oxygen or Hydrogen OS 11 firmware
    - Dirty flash from early build is fine
    - Fingerprint & haptics may not work on custom kernel so don't spam in device support group

    Source changelog:
    - Merged July security patch (android-12.1.0_r11)
    - Switched to GameSpace, with all goods from old GamingMode kept
    - Refactored in-game lock gesture feature
    - Added Status Bar Ticker
    - Added Music QS tile
    - Added Google Lens into screenshot UI
    - Added proximity check on wake toggle
    - Added support to show battery level for AirPods series
    - Added support to reset auto brightness adjustment
    - Added more haptic feedback scenes for supported devices
    - Relax slider haptic feedback strength
    - Dropped slider haptic feedback for some devices
    - Added OPPO Sans
    - Allow receive / send any type of files from Bluetooth
    - Fixed less boring heads up toggle
    - Fixed 2-button navbar option missing
    - Improved partial screenshot
    - Improved pocket mode layout
    - Moved extra dim feature into display settings
    - Show 12L in settings and updated Easter Egg from PUI
    - Updated default wallpaper
    - Updated various system icons
    - Updated various APNs
    - Updated lawnchair to latest dev & Enabled dexpreopt
    - Other cleanup and improvements

    Device changelog:
    - Improved Haptics feedbacks. Enjoy OOS type haptic now :)
    - Improved some Chinese third-party input methods haptic feedback
    - Enable System Wide haptics feedbacks
    - Update blobs from LA.UM.9.12.r1-14200-SMxx50.QSSI13.0
    - Fixed Dolby visualizer effect
    - Attempt to match stock auto brightness behaviour
    - Attempt to fix Google AR Core
    - Fixed audio in screen cast (WiFi Display)
    - OnePlus Settings: Added support to automatically enable high touch sample / tp edge touch mode in games
    - OnePlus Settings: Increased vibrator strength level range to 5 (Only for default kernel)
    - Other cleanup and improvements
    11
    New Build Up!

    Source Changelog
    - Merged May security patch (android-12.1.0_r5)
    - Added AdGuard & Cloudflare private DNS providers
    - Added Custom carrier label & Carrier label placement
    - Added Dora & Weed status bar icons
    - Added optimized charging QS tile for supported devices
    - Allow to hide back gesture arrow
    - Allow to switch slot in recovery for AB devices
    - Refactor QS tiles layout code (Previous settings will be revoked, set again in settings)
    - Fixed partial screenshot
    - Fixed wireless emergency alerts crash in settings
    - Maybe more that I forgot

    Device Changelog
    - Restore old notification haptic intensity