[ROM][11.0_r55]JAGUAR ONEPLUS 8 OFFICIAL V20.1 Updated May 11, 2022

[optimumpro]

You're forgetting the MSM tools have readback mode. This allows an attacker to backup all the partitions anyway and flash them later, so bootloader lock doesn't have much practical security. Also, MSM tools can be modified, so I'm pretty sure you can disable wipe on flash. Regardless, the backup method removes any tangible security benefits.

Regarding recoveries being able to unlock bootloader, I'm not sure that's possible. You have to boot into fastboot bootloader mode, not fastboot recovery mode to unlock the bootloader. Unless someone comes up with a bootloader attack, it's quite difficult to unlock bootloader from recovery.

I wasn't saying recovery could unlock bootloader, but rather, if OEM unlock is allowed, anyone could unlock from fastboot. Also, at least on Onepluses, recovery does the wiping, so if recovery is erased, there would be no wiping data. If OEM unlock is disabled, no fastboot action would be possible. Also, I think, although I never checked, that if EDL is disabled in kernel, that might prevent MSM flashing/backup.

 

[razercortex]

Ah, I see. Yes, OEM unlock does allow unlocking from fastboot, and the recovery is definitely in charge of wiping data, so I guess you can bypass it? Then again, I'm not sure how you'd remove verified boot on a locked bootloader. Might be nice to try.

Disabling EDL might be nice for security, but it's a very bad decision. It basically means your phone becomes a paperweight if there are no other recovery options available.

 

[optimumpro]

Ah, I see. Yes, OEM unlock does allow unlocking from fastboot, and the recovery is definitely in charge of wiping data, so I guess you can bypass it? Then again, I'm not sure how you'd remove verified boot on a locked bootloader. Might be nice to try.

Disabling EDL might be nice for security, but it's a very bad decision. It basically means your phone becomes a paperweight if there are no other recovery options available.

Verified boot - it's a matter of what partition is included. On my phone, everything is locked. For those who flash Gapps, system partitions are not included.

 

[passion8059]

Would you consider adding in display profile such as wide display gammut for richer colour?

 

[optimumpro]

Would you consider adding in display profile such as wide display gammut for richer colour?

The rom has it in Settings/Display/Nightdisplay. It has Standard, DCI-P3, Wide and sRGB.

 

[passion8059]

The rom has it in Settings/Display/Nightdisplay. It has Standard, DCI-P3, Wide and sRGB.

Cheers. Layout was different from other ROMs. Thanks

 

[blair.sadewitz]

You're forgetting the MSM tools have readback mode. This allows an attacker to backup all the partitions anyway and flash them later, so bootloader lock doesn't have much practical security. Also, MSM tools can be modified, so I'm pretty sure you can disable wipe on flash. Regardless, the backup method removes any tangible security benefits.
.

What? Are you serious? You're aware of readback mode and don't understand the security implications? If you rethink it, you will.

If you have an unlocked bootloader, the phone will boot or flash anything! Anyone could take your phone, plug it into their USB port, and:

fastboot boot twrp.img

Now they have a full-featured environment in which to do anything they want. Sure, userdata is encrypted, but so what? They can unpack your boot image and modify it to their heart's content! The possibilities are limited only by one's creativity! Ever flash magisk? Well, magisk is essentially the skeleton of a rootkit. Even a dilettante like me could manage all sorts of nefarious things without too much exertion!

An unlocked bootloader breaks the entire Android security model. Why do you think optimumpro bothered to support bootloader locking?

 

[blair.sadewitz]

You're forgetting the MSM tools have readback mode. This allows an attacker to backup all the partitions anyway and flash them later, so bootloader lock doesn't have much practical security. Also, MSM tools can be modified, so I'm pretty sure you can disable wipe on flash. Regardless, the backup method removes any tangible security benefits.

Regarding recoveries being able to unlock bootloader, I'm not sure that's possible. You have to boot into fastboot bootloader mode, not fastboot recovery mode to unlock the bootloader. Unless someone comes up with a bootloader attack, it's quite difficult to unlock bootloader from recovery.

Next time you unlock the bootloader, take the time to think about the message it prints on the screen! They aren't just saying that to mess with you. Every word is literally true. Read the message and really think it over.

https://www.reddit.com/r/LineageOS/comments/n7yo7u

 

[razercortex]

Next time you unlock the bootloader, take the time to think about the message it prints on the screen! They aren't just saying that to mess with you. Every word is literally true. Read the message and really think it over.

https://www.reddit.com/r/LineageOS/comments/n7yo7u

I'm not talking about bootloader unlocking. I'm talking about readback mode and the fact it can bypass bootloader locks. It means you shouldn't give your phone to anyone but yourself.

 

[blair.sadewitz]

I'm not talking about bootloader unlocking. I'm talking about readback mode and the fact it can bypass bootloader locks. It means you shouldn't give your phone to anyone but yourself.

Huh? It just dumps the partitions. That will get you precisely nowhere. Well, what do you mean by "bypass bootloader locks"?

Userdata is normally encrypted.

 

[blair.sadewitz]

I'm not talking about bootloader unlocking. I'm talking about readback mode and the fact it can bypass bootloader locks. It means you shouldn't give your phone to anyone but yourself.

Regarding what you said above: you seem to be somewhat confused. You said "it's not possible to unlock the bootloader from recovery". Well, of course not! The recovery is a kernel. You can't unlock the bootloader (unless there is some exploit, and if you have that, this conversation is irrelevant because it's all broken anyway) in recovery because you've already booted!

No one can get at anything unless they can decrypt userdata (_perhaps_ e.g. the NSA could do that if they really wanted to, that's about it). If the bootloader is unlocked, they could do an "evil maid" attack as that document I included mentions. Again, as I said, this is why bootloader locking exists: so you that you can be certain that what you are booting hasn't been tampered with.

 

[razercortex]

Regarding what you said above: you seem to be somewhat confused. You said "it's not possible to unlock the bootloader from recovery". Well, of course not! The recovery is a kernel. You can't unlock the bootloader (unless there is some exploit, and if you have that, this conversation is irrelevant because it's all broken anyway) in recovery because you've already booted!

No one can get at anything unless they can decrypt userdata (_perhaps_ e.g. the NSA could do that if they really wanted to, that's about it). If the bootloader is unlocked, they could do an "evil maid" attack as that document I included mentions. Again, as I said, this is why bootloader locking exists: so you that you can be certain that what you are booting hasn't been tampered with.

I seriously don't want to fight you over this. You can choose to believe what you want.

 

[yaseen015]

Bro cud enable set pattern/password lock to the recovery so that it will make it more secure.

 

[optimumpro]

Regarding what you said above: you seem to be somewhat confused. You said "it's not possible to unlock the bootloader from recovery". Well, of course not! The recovery is a kernel. You can't unlock the bootloader (unless there is some exploit, and if you have that, this conversation is irrelevant because it's all broken anyway) in recovery because you've already booted!

No one can get at anything unless they can decrypt userdata (_perhaps_ e.g. the NSA could do that if they really wanted to, that's about it). If the bootloader is unlocked, they could do an "evil maid" attack as that document I included mentions. Again, as I said, this is why bootloader locking exists: so you that you can be certain that what you are booting hasn't been tampered with.

He is not confused, he is just talking about the fact that MSM tool can wipe the phone and even dump your partitions. But when he says that from the security point of view, locked bootloader doesn't provide any benefits, he is wrong:

Locked bootloader also allows AVB-2 to work, which means if partitions are locked, any change or attack via the internet, even if it succeeds, will be reversed on reboot. So, even if someone managed to install an invisible keylogger on such a phone, a simple reboot would get rid of it.

 

[blair.sadewitz]

He is not confused, he is just talking about the fact that MSM tool can wipe the phone and even dump your partitions. But when he says that from the security point of view, locked bootloader doesn't provide any benefits, he is wrong:

Locked bootloader also allows AVB-2 to work, which means if partitions are locked, any change or attack via the internet, even if it succeeds, will be reversed on reboot. So, even if someone managed to install an invisible keylogger on such a phone, a simple reboot would get rid of it.

Oh. Well, sure, it can dump your partitions, but so what? Userdata is encrypted. Anyone with a mobile device who cares about security (I am not disparaging those who don't care much about it, BTW) should assume that an attacker will be able to access internal storage directly.

Re: bootloader. YES. That is exactly the point. The 'v' in AVB is key, heh. The sanctity (for some reason using that word here is hilarious to me) of the boot chain is critical.

Your keylogger example is what I meant by "evil maid attack". And the best rootkit I've ever seen is already available: magisk! ;-)

Incidentally, have you tried bkerler/edl on GitHub? It's pretty awesome.

Oh, BTW, do you have USB gadget support in your kernel?

 

[blair.sadewitz]

Bro cud enable set pattern/password lock to the recovery so that it will make it more secure..

Well, someone could just fastboot boot another recovery unless the bootloader is locked ;-)

FYI:

Support Direct Boot mode | Android Developers

developer.android.com

 

[yaseen015]

Well, someone could just fastboot boot another recovery unless the bootloader is locked ;-)

FYI:

Support Direct Boot mode | Android Developers

developer.android.com

Yes on locked bootloader if the recovery has pattern/pin lock no one cud wipe date which wud make it more secure that's what I meant. What do you think?

 

[optimumpro]

February 8. New release, V-17

1. February security patches
2. Android r52
3. Regular webview, as opposed to bromite
4. Toggle to hide statusbar clock when launcher is active
5. New recovery that fixes 'not enough space' issues with some Gapps

Download in post #3.

 

[blair.sadewitz]

February 8. New release, V-17

1. February security patches
2. Android r52
3. Regular webview, as opposed to bromite
4. Toggle to hide statusbar clock when launcher is active
5. New recovery that fixes 'not enough space' issues with some Gapps

Download in post #3.

You fixed the gapps problem? Awesome! That is why I gave up on this--and I didn't want to, either. This is the best ROM overall for this device, IMHO.

 

[optimumpro]

You fixed the gapps problem? Awesome! That is why I gave up on this--and I didn't want to, either. This is the best ROM overall for this device, IMHO.

Well, this has to be confirmed, as I don't have Gapps on my phone, but I think Bromite webview was the reason, the phone couldn't connect to Google services.