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

Search This thread

optimumpro

Senior Member
Jan 18, 2013
7,535
14,891
OnePlus 8
Short answer: no - don't ever do that. Your phone will not boot.

Longer answer: Still no. But the reason why is that the bootloader being "locked" means that it will only boot code that is cryptographically signed by the manufacturer's private key. You can't change the key it uses to validate this because it's likely embedded in secure hardware or something crazy like that. Custom ROMs, by definition, are not signed using the manufacturer's private key, and neither is the custom recovery you have to use with them. Even if you root your stock ROM, you still have to unlock the bootloader because rooting modifies the kernel, which causes the digital signature to be invalid.

So, you can only have a locked bootloader on stock, un-rooted, unmodified, software .. which is the whole point of locked bootloaders in the first place. Many manufacturers won't even allow you to unlock their bootloaders anymore. At least OnePlus is still staying away from that horrible bandwagon.

Good luck.
Your information is incorrect. All Onepluses allow locking bootloader with a custom key, which means that a custom rom could run on locked bootloader. This is possible even with Magisk. My rom (Jaguar) is one example. There are others...
 
  • Like
Reactions: rodken

ssewk2x

Senior Member
Oct 24, 2010
1,374
1,388
Detroit, MI
OnePlus 8T
Your information is incorrect. All Onepluses allow locking bootloader with a custom key, which means that a custom rom could run on locked bootloader. This is possible even with Magisk. My rom (Jaguar) is one example. There are others...
Fascinating - I did not know that. Thanks for the correction. I would like very much to figure out how this works...
 

card13

Senior Member
Nov 27, 2008
442
158
32
Washington State
OnePlus 3T
OnePlus 5
@skanadian and @JrkSoldierX When the OP8T first came out, the reason behind it was, the Global FW was released on Google Servers and could only be downloaded via OTA Delta (Small Package) or when OnePlus decided (at their whim or some internal policy they never publicly discussed) when it was time to release a Full Update File via their website. During that time it was discovered the EU version didn't have enough noticeable differences between it and Global version to cause issues. As for why now, I can only assume the issue hasn't been overcome (and probably never will).
 
  • Like
Reactions: JrkSoldierX

JrkSoldierX

Member
Dec 6, 2012
41
8
@skanadian and @JrkSoldierX When the OP8T first came out, the reason behind it was, the Global FW was released on Google Servers and could only be downloaded via OTA Delta (Small Package) or when OnePlus decided (at their whim or some internal policy they never publicly discussed) when it was time to release a Full Update File via their website. During that time it was discovered the EU version didn't have enough noticeable differences between it and Global version to cause issues. As for why now, I can only assume the issue hasn't been overcome (and probably never will).
Thank you for the reply, I understand the reason now. Would flashing EU mess with US carriers like AT&T and TMobile? I think that's our main concern here. Thanks
 

card13

Senior Member
Nov 27, 2008
442
158
32
Washington State
OnePlus 3T
OnePlus 5
@JrkSoldierX I can confirm for T-Mobile that no there is no major issues (as I have T-Mobile, and there might be something I just haven't seen it). I can't speak on AT&T or VZW (Here's a starter https://forum.xda-developers.com/t/kb2005-no-5g-or-voice-over-wifi.4478209/#post-87306851 and https://forum.xda-developers.com/t/guide-fix-enable-5g-and-dss.4206461/page-8#post-87169905) but I remember before I had switched phones that the issues of cross-flashing and the use of US Carriers were minimal.
 

AkiraBBQ

Senior Member
Mar 19, 2011
76
11
Is the current charging behaviour inherited from OOS12? After upgrading to OOS12 a month ago, the phone lost all USB-PD charging capabilities. I've tested OOS12 with several PD sniffers and chargers, the phone never tried to initiate any PD profiles. It only charges at standard [email protected], or strangely QC2/3.0 [email protected] 18W when battery is <50%. Under OOS11, 8T charges at PD [email protected] 27W when <~50%, and PD [email protected] 15W after. The oneplus community forum does not give a f__K as usual.

I thought it was my phone's usb problem. But no, after reverting back to OOS11 using MSM Tools, the PD charging is instantly back. Now I am on latest Nameless, once again PD is not working. However Nameless is still better than OOS12 since OOS12 somehow deliberately slows down the charging further (down to ~5W) when the screen is on. When my phone sits in my car with Waze + GPS + Bluetooth, the phone does not charge at all under OOS12. With Nameless, it charges ok but is still slow.

Is it possible to change the USB charging behaviour or is it built into the OOS12 drivers?
 

kim9096

Member
Oct 17, 2016
17
3
Is the current charging behaviour inherited from OOS12? After upgrading to OOS12 a month ago, the phone lost all USB-PD charging capabilities. I've tested OOS12 with several PD sniffers and chargers, the phone never tried to initiate any PD profiles. It only charges at standard [email protected], or strangely QC2/3.0 [email protected] 18W when battery is <50%. Under OOS11, 8T charges at PD [email protected] 27W when <~50%, and PD [email protected] 15W after. The oneplus community forum does not give a f__K as usual.

I thought it was my phone's usb problem. But no, after reverting back to OOS11 using MSM Tools, the PD charging is instantly back. Now I am on latest Nameless, once again PD is not working. However Nameless is still better than OOS12 since OOS12 somehow deliberately slows down the charging further (down to ~5W) when the screen is on. When my phone sits in my car with Waze + GPS + Bluetooth, the phone does not charge at all under OOS12. With Nameless, it charges ok but is still slow.

Is it possible to change the USB charging behaviour or is it built into the OOS12 drivers?
Have you tried AwakenOS? This one has been much more stable on my 8T. Best thing is it's on OOS11 and comes with OOS Camera.
 

crazyVII

Senior Member
Jul 16, 2008
299
18
Hey there, today morning I installed 'Nameless-AOSP_kebab-12.1-20220823-2345-Official.zip' as OTA of 'Nameless-AOSP_kebab-12.1-20220723-1310-Official.zip' (working before without problems).
It ended up in a bootloop with an combination of black screen and "take care bootloader unlocked" screen,
did it endlessly.

I attached it to a PC, did a reflash of things in installation guide, incl. recovery, NOT able to boot into recovery anymore even if flashed brand new. Device bricked at the moment.
Any ideas what's broken?

Thanks in advance. Probably, take care!
 

Harish Sandesh

New member
Sep 26, 2017
4
1
Moto G4 Plus
Moto G5S Plus
Hey there, today morning I installed 'Nameless-AOSP_kebab-12.1-20220823-2345-Official.zip' as OTA of 'Nameless-AOSP_kebab-12.1-20220723-1310-Official.zip' (working before without problems).
It ended up in a bootloop with an combination of black screen and "take care bootloader unlocked" screen,
did it endlessly.

I attached it to a PC, did a reflash of things in installation guide, incl. recovery, NOT able to boot into recovery anymore even if flashed brand new. Device bricked at the moment.
Any ideas what's broken?

Thanks in advance. Probably, take care!
You need to flash C33 firmware before updating to the latest build.
 
  • Haha
Reactions: crazyVII

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Can I also follow this if I am on the Nameless 12.1-20220708-0926-Official Build? :)
    Yes I think so, you just need to check if that build is based on OOS11 or OOS12 Firmware.
    1
    Using 9R LE2100 (China version, but with OOS)

    Switched from stock OOS 12, C33 version to this amazing ROM.

    Everything works!!! Fast charge, refresh rate, winevine are all OK. Battery life is great. Thank you ROM DEVs :)

    Just some notes here to help others who might encounter issues:

    - I made sure both slot have OOS 12 C33 firmware by forcing the local update for C33 twice.

    - I flashed recovery to both slots with:

    Code:
    fastboot flash recovery_a recovery.img
    fastboot flash recovery_b recovery.img


    The whole process went smoothly, without any hiccup. Not even being stuck at 47% as mentioned in the original guide. The whole thing just passed cleanly.
    1
    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
    1
    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.
    Disable wide angle correction or whatever it's called from settings
    1
    Disable wide angle correction or whatever it's called from settings
    yeah that worked, I'm a total noob, thanks a lot!
  • 48
    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
    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
    11
    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.