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

[gianm.93]

I followed all the instructions but I can't reboot in recovery os system but just into fastboot mode

 

[Yliastuttu]

I can only speak for myself but it's super stable and smooth and perfect as a daily driver.

Same here!
No bugs found. Used almost 2 weeks now.

 

[ssewk2x]

Well, I finally took the leap today. Just a few odds and ends to report:

1. The "fastboot" method of restoring to stock did not work. It got me into "Qualcomm Crashdump Mode" and I ended up having to MSM back anyway.
2. There are a couple of times you need to reboot to recovery that may not have been covered.
3. sideloading the copy-partitions ZIP is essential before you flash anything else in the Nameless recovery.
4. I was going to see if OrangeFox recovery would work, but I decided not to risk it. Has anyone been braver than me?

 

[reshad2065]

Messenger chat bubble not working.
Anyone facing this?? Please help fixing this.
Except this, everything is working great for me.

 

[GodFather256]

I have a few small bugs. For example, the live display sometimes doesn't work on the lock screen and the re-ticker notifications don't always work either. Otherwise everything works fine

 

[misanekxx]

Hello, thank you for this great ROM. I used fastboot installer to install the latest version. Everything I use works great. I am only sorry that there is no complete translation for my native Czech language. Can I ask the developers to enable TM (translation memory) on crowdin? My friend would be willing to finish the translation then. Thank you


My procedure was the MSM tool for the A11, then a local update to the latest European A12 C21, and finally I created a fastboot installation in both slots for Nameless.

 

[Christos_A]

Well, I finally took the leap today. Just a few odds and ends to report:

1. The "fastboot" method of restoring to stock did not work. It got me into "Qualcomm Crashdump Mode" and I ended up having to MSM back anyway.
2. There are a couple of times you need to reboot to recovery that may not have been covered.
3. sideloading the copy-partitions ZIP is essential before you flash anything else in the Nameless recovery.
4. I was going to see if OrangeFox recovery would work, but I decided not to risk it. Has anyone been braver than me?

Latest OrangeFox 12.1 beta 3 flashed works fine on the latest Nameless build (OOS12 fw)., but I aint sure if it breaks OTA or not. Sadly i wont probably get to test it out as i plan to return to OOS11 firmware, the lack of custom kernels makes the device slow af on my end, plus latest build is a little more buggy than usual

 

[nihil39]

I am on OOS 12 C.21, flashed twice via local upload method. I am trying to flash this rom but from the stock oneplus recovery it is not possible to sideload packages via adb. Do I need another recovery?

I am following these instructions

Thank you

 

[ssewk2x]

Well, I spoke too soon.

1. SwiftBackup flat out refused to restore my stuff. Fantastic
2. Magisk Hide doesn't work on the new Nameless. Everything still detects root, including the authenticator app I have to use to log in to my work network, etc. This is a show-stopper for me.

So, I'm reverting back to the OOS 11 - based Nameless I had before. Hopefully, I can get most of my stuff and functionality back.

 

[alboon2000]

Well, I spoke too soon.

1. SwiftBackup flat out refused to restore my stuff. Fantastic
2. Magisk Hide doesn't work on the new Nameless. Everything still detects root, including the authenticator app I have to use to log in to my work network, etc. This is a show-stopper for me.

So, I'm reverting back to the OOS 11 - based Nameless I had before. Hopefully, I can get most of my stuff and functionality back.

I used this method to hide root and it works :

https://www.droidwin.com/how-to-hide-root-from-apps-via-magisk-denylist/

and https://www.droidwin.com/how-to-pass-safetynet-on-rooted-android-12/
(the first link will point to the second one anyway)
Note that for STEP 2 I used Nexus 6P, as shown in the guide, even though it was written KB2003 on my phone.

 

[sebas156]

Flashed all the components but now I cannot enter recovery mode. It just boots back into fastboot. Turning off also doesn't work (also just boots back into fastboot mode). Any advice?

EDIT:
Ok after scanning this thread for a bit I found some useful advice (followed post #752). My mistake is that I downloaded an older version. The "latest version" button in the download link is actually NOT the latest. Click the one in the list below the button manually. Would be great if OP clarifies this in the instructions tbh.

Before you run the adb command, check adb devices first and make sure it says "sideload". For me sometimes it said unauthorized. Rebooting recovery and replugging the cable worked for me.

One more thing. For other MacOS / Linux users that couldn't use the provided payload_dumper. I used this guide and worked successfully using the python script.

 

[blade227]

Flashed all the components but now I cannot enter recovery mode. It just boots back into fastboot. Turning off also doesn't work (also just boots back into fastboot mode). Any advice?

EDIT:
Ok after scanning this thread for a bit I found some useful advice (followed post #752). My mistake is that I downloaded an older version. The "latest version" button in the download link is actually NOT the latest. Click the one in the list below the button manually. Would be great if OP clarifies this in the instructions tbh.

Before you run the adb command, check adb devices first and make sure it says "sideload". For me sometimes it said unauthorized. Rebooting recovery and replugging the cable worked for me.

One more thing. For other MacOS / Linux users that couldn't use the provided payload_dumper. I used this guide and worked successfully using the python script.

I've mentioned the "download latest" button a few times now, unfortunate that nothing has been done about it. I suspect that most people couldn't install this new update due to that.

 

[kim9096]

Shout out to MadMic #752
Your instructions are so clear I can't mess up.

Some tips for T-Mobile gang. Unlock bootloader while on OOS11. It'll ask for unlock token on OOS12

 

[YuumiMeow]

I followed all the instructions but I can't reboot in recovery os system but just into fastboot mode

dude you may downloaded wrong rom(20220708), make sure your rom is 20220723. do NOT click big green button

 

[Skilstriker]

Now that orangefox works on a12.. a proper installation guide with orange fox would be great. Coming form a galaxy s4, rom flashing has changed a lot like really a lot and thanks to the devs for all the work you are awesome...

 

[sebas156]

Enjoying the ROM for 2 days now.

But NFC is not working anymore. I can't turn it on in QS (button doesn't respond). When click on NFC in settings, this is all I see. I can't turn it on anywhere..

 

[Mondandoblade]

I'm on old nameless build (7/5/22) and I had a friend who had same build and a they did to update rom was skip to the flash firmware step.

Is this true or do I really need to follow all of those steps?

OnePlus 8t tmobile

 

[Sahadev Rathor]

Im on 2022/07/08 build
And now I can't wipe my 256gb storage to flash OOS12.

Please make other flashable update
Otherwise I need to stay on last build for forever

 

[ssewk2x]

Well, I had a critical failure the other night. My phone freaked out, the display went dark, and I couldn't even get it to reboot itself by holding down the power button, nor with power+vol up+vol dwn, nor any other combo. I eventually had to hook up to a computer and then ADB reboot was able to get me back up and running. This was the 2nd time this has happened to me on Nameless ROM.

... and I just cannot have that. If I had been away from the house and needed to call 911, I'd have been screwed.

So .. I'm sorry, but it's back to OOS12 / rooted for me.

However, for those looking to do the upgrade, I suggest using FolderSync to back up your /storage/emulated/0 to somewhere off your device. It's easy to set up and restore, and you can schedule nightly backups of all your stuff. It only syncs what has changed, so after the initial dump, it's pretty quick. That way you can wipe your device and get all your stuff back after installing the new ROM.

Good luck, and thanks for all the hard work, devs.

 

[reshad2065]

Well, I had a critical failure the other night. My phone freaked out, the display went dark, and I couldn't even get it to reboot itself by holding down the power button, nor with power+vol up+vol dwn, nor any other combo. I eventually had to hook up to a computer and then ADB reboot was able to get me back up and running. This was the 2nd time this has happened to me on Nameless ROM.

... and I just cannot have that. If I had been away from the house and needed to call 911, I'd have been screwed.

So .. I'm sorry, but it's back to OOS12 / rooted for me.

However, for those looking to do the upgrade, I suggest using FolderSync to back up your /storage/emulated/0 to somewhere off your device. It's easy to set up and restore, and you can schedule nightly backups of all your stuff. It only syncs what has changed, so after the initial dump, it's pretty quick. That way you can wipe your device and get all your stuff back after installing the new ROM.

Good luck, and thanks for all the hard work, devs.

I faced the same issue man. It was a mini heart attack for me.
Then, I flash latest orange fox recovery instead of the one given with rom, side load the rom and everything is fine then. I think there is a problem with the recovery.