[ROM][11.0_r58]JAGUAR ONEPLUS 8 OFFICIAL V23 Updated August 6, 2022

[optimumpro]

Can I flash this if I skipped may 3 release? I'm on april 15 - V19

Yes, you can.

 

[scorpio76r]

Can I flash this if I skipped may 3 release? I'm on april 15 - V19

*

 

[optimumpro]

May 11. New release V-20.1

1. Redone adaptive brightness
2. Call recording (bug introduced in V-20) fixed
3. Captive portal: added 3 options Standard (Google), Alternative and Disabled; and moved to Settings/Network
4. Fingerprint icons and colors made more transparent, so, now fingerpint works flawlessly.

Download in post #3.

 

[scorpio76r]

May 11. New release V-20.1

1. Redone adaptive brightness
2. Call recording (bug introduced in V-20) fixed
3. Captive portal: added 3 options Standard (Google), Alternative and Disabled; and moved to Settings/Network
4. Fingerprint icons and colors made more transparent, so, now fingerpint works flawlessly.

Download in post #3.

The Jaguar version is showing 20.0 after flashing the 20.1 update. Was

 

[optimumpro]

The Jaguar version is showing 20.0 after flashing the 20.1 update. Was

That's OK. You do have all the changes.

 

[scorpio76r]

That's OK. You do have all the changes.

Thanks for the clarification. I thought I was going crazy for a minute, lol. Thanks again for your work and, keeping the oneplus 8 working great.

 

[scorpio76r]

I usually do not use my phone while walking outside but, today I did. I noticed that I couldn't see my screen. It was dark. When I got out of the sun a little and in to some shade I could see my screen a little and, I went into settings. I saw that my brightness level was at 100% but my screen was dark. I have adapted brightness enabled also. How do I fix this issue with not being able to see my screen when it's sunny outside?

 

[RogueVisual]

I dont see the recorder option in the Phone app, where should it be located?

 

[optimumpro]

I dont see the recorder option in the Phone app, where should it be located?

The record option appears during the call only.

 

[optimumpro]

I usually do not use my phone while walking outside but, today I did. I noticed that I couldn't see my screen. It was dark. When I got out of the sun a little and in to some shade I could see my screen a little and, I went into settings. I saw that my brightness level was at 100% but my screen was dark. I have adapted brightness enabled also. How do I fix this issue with not being able to see my screen when it's sunny outside?

Are you saying that maximum brightness is not enough when at direct sunlight or that the actual brightness is not maximum brightness in your case?

 

[scorpio76r]

Are you saying that maximum brightness is not enough when at direct sunlight or that the actual brightness is not maximum brightness in your case?

Maximum brightness is not enough in my case. This is happening to both of my 8's both on latest version of the rom. I'm not sure sure if this ever happened on oxygen oos but, I'm never going back to that horrible software to see if that happens on it.

 

[crashfly]

I would like to change over to this ROM. I have downloaded the latest v20-1 zip and I downloaded the v20 recovery. However, after following instructions to flash the recovery img and then attempting to reboot to recovery, I get an error of "The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it."

The bootloader is appears to be unlocked according to the still working system on slot a.
It says 'OEM unlocking', "Bootloader unlocked".
Attempting to 'fastboot oem unlock' responds with "Device already : unlocked!", so the device is flashable.

It just appears that recovery.img is somehow corrupted?
Downloaded twice with md5 hash of '9507d66832e591a98353dfadabeb47c9'.

Anyone got any suggestions?

Edit: Nevermind. I just realized this is based off of android 11 and my phone currently has android 12. That would explain it.

 

[optimumpro]

As I said earlier

Edit: Nevermind. I just realized this is based off of android 11 and my phone currently has android 12. That would explain it.

That is NOT the reason. All custom Android 11 and 12 roms require OOS-11 in both slots. So, if you were on a custom 12 rom, you'll be fine with Jaguar, but if you were on OOS-12, then in order to run any custom rom (11 or 12), you need to downgrade to OOS-11 in both slots.

Try recovery from earlier release. You can also use Lineage recovery or even TWRP.

 

[crashfly]

As I said earlier

That is NOT the reason. All custom Android 11 and 12 roms require OOS-11 in both slots. So, if you were on a custom 12 rom, you'll be fine with Jaguar, but if you were on OOS-12, then in order to run any custom rom (11 or 12), you need to downgrade to OOS-11 in both slots.

Try recovery from earlier release. You can also use Lineage recovery or even TWRP.

Because I do not know, I would like to know why OOS-11 is required in both slots?

One would assume that an Android 12 experience requires an Android 12 bootloader. I have not kept up with the custom roms lately because when I purchased my Oneplus 8, the fingerprint reader did not work in the several custom roms I tried. I went back to a rooted stock and was satisfied that I could get what I needed done. Accidentally, my phone updated to Android 12, but I was able to retain root. Unfortunately, the most recent update has rendered my phone without root.

Also, I was under the impression that the [11.0_r55] designation in the thread title implies this is an Android 11 rom. Please inform me if I am wrong.

 

[optimumpro]

Because I do not know, I would like to know why OOS-11 is required in both slots?

One would assume that an Android 12 experience requires an Android 12 bootloader. I have not kept up with the custom roms lately because when I purchased my Oneplus 8, the fingerprint reader did not work in the several custom roms I tried. I went back to a rooted stock and was satisfied that I could get what I needed done. Accidentally, my phone updated to Android 12, but I was able to retain root. Unfortunately, the most recent update has rendered my phone without root.

Also, I was under the impression that the [11.0_r55] designation in the thread title implies this is an Android 11 rom. Please inform me if I am wrong.

Because OOS-12 does not support custom roms. It's not just bootloader, but about 20 other firmware partitions. If you read any custom rom's thread, Android 11 and 12, this is what they all say: OOS-11 in both slots is required.

My rom is Android 11, but as I just said, the requirement is the same for custom 11 and 12 roms.

People should read install instructions and not assume anything. Otherwise, they get into all kinds of trouble. 99.9% of those are self-inflicted.

 

[crashfly]

Because OOS-12 does not support custom roms. It's not just bootloader, but about 20 other firmware partitions. If you read any custom rom's thread, Android 11 and 12, this is what they all say: OOS-11 in both slots is required.

So what leads you to that conclusion that OOS-12 does not support custom roms?
I do not accept statements without something backing that statement up.
And the thread right below this one {[ROM][12.1]CherishOS-3.7[UNOFFICIAL][Oneplus 8][05.14.2022]} does not mention anywhere in its first post about requiring Android 11. Please keep blanket statements like "this is what they all say" from making your statement false.


This rom looks interesting, but I will instead look at an Android 12 rom.

 

[optimumpro]

So what leads you to that conclusion that OOS-12 does not support custom roms?
I do not accept statements without something backing that statement up.
And the thread right below this one {[ROM][12.1]CherishOS-3.7[UNOFFICIAL][Oneplus 8][05.14.2022]} does not mention anywhere in its first post about requiring Android 11. Please keep blanket statements like "this is what they all say" from making your statement false.


This rom looks interesting, but I will instead look at an Android 12 rom.

You should ask that person as to why he didn't put it into his instructions. I don't know. Maybe because he is not a developer, it's not his rom, and he simply compiled it. That's the difference between official and unofficial roms. In the latter case, the compiler has no control over the rom features. Or he just assumed that everyone knows that OOS-12 doesn't support custom roms.

I do my own development and I know that OOS-12 firmware is not usable with custom roms, and I tell my users they need OOS-11 in both slots to install my rom, and so do other developers whether Android 11 or 12. But again, virtually everybody, who ever complained about running into installation problems, did that to him/herself by failing to read instructions.

Best regards.

 

[cjvzla]

Hi, want to dirty flash latest release but when i type adb devices on the cmd window, my device show up but it says unathorized, will this affect the result when i type adb sudeload rom? i don't want to soft brick so i rather ask

 

[optimumpro]

Hi, want to dirty flash latest release but when i type adb devices on the cmd window, my device show up but it says unathorized, will this affect the result when i type adb sudeload rom? i don't want to soft brick so i rather ask

That won't prevent sideloading, but if you want, you can always authorize your PC in Developer options.

 

[cjvzla]

That won't prevent sideloading, but if you want, you can always authorize your PC in Developer options.

thanks...currently sitting at 70% for 20 mins now. you've said before this is normal...should i just let it finish? what could i do if it fails to flash?