| 18 Aug 2021 |
 samueldr | I assume pixel 6 will still allow enrolling custom keys, but I wonder how it will differ, if it will differ | 17:50:32 |
 danielrf | I shouldn't have said Pixel 5a. There's some work that would still need to happen in an upstream project before we can support that device (https://github.com/aospalliance/android-prepare-vendor) | 17:51:54 |
 Xe (xe/they) | oh heck the 5a isn't going to be launched in canada regardless lol | 17:52:20 |
| samueldr | 5a is a likely candidate for this all to work though | 17:52:22 |
| danielrf | Yes, I would expect it would be working within a few months at most | 17:52:34 |
| Xe (xe/they) | i may go to a 4a then | 17:52:35 |
 cde | In reply to @danielrf:matrix.org
I shouldn't have said Pixel 5a. There's some work that would still need to happen in an upstream project before we can support that device (https://github.com/aospalliance/android-prepare-vendor) I'm betting we can just cp redfin | 17:52:36 |
| cde | or bramble | 17:52:58 |
| danielrf | Lets hope! | 17:53:04 |
| Xe (xe/they) | lol the pixel 4a(5g) and the pixel 5 are out of stock in google devices canada | 17:54:09 |
| Xe (xe/they) | wonder if i should go through bell for it lol | 17:54:16 |
| samueldr | AFAIK for pixel devices canadian carriers models are the totally unlocked variant | 17:55:05 |
| samueldr | not like verizon | 17:55:10 |
| * samueldr grumbles | 17:55:12 |
| samueldr | poisoning the well of second-hand pixel phones in north america | 17:55:27 |
| Xe (xe/they) | yeah, it probably doesn't matter either way because i'm kinda tethered to bell with actually unlimited data | 17:55:48 |
| Xe (xe/they) | would have to transfer from an esim to a psim though | 17:56:03 |
 hmenke | danielrf: We should maybe add to the installation docs that the user has to make sure they're flashing the correct device before running ./flash-all.sh. On the https://matrix.to/#/#grapheneos:grapheneos.org channel I heard that flashing the wrong image can brick the device. | 18:30:23 |
| hmenke | * danielrf: We should maybe add to the installation docs that the user has to make sure they're flashing the correct device before running ./flash-all.sh. On the #grapheneos:grapheneos.org channel I heard that flashing the wrong image can brick the device. | 18:30:32 |
| danielrf | Redacted or Malformed Event | 18:30:39 |
| danielrf | hmenke: Hmm I thought there were checks that prevented that | 18:32:31 |
| danielrf | ah, so, for instance, in image-crosshatch-2021.04.22.20.zip that would get fastboot updated, there's an android-info.txt that contains this: | 18:33:31 |
| danielrf | require partition-exists=product
require version-bootloader=b1c1-0.3-7065185
require version-baseband=g845-00166-210105-B-7062333
| 18:33:38 |
| danielrf | * require partition-exists=product
require version-bootloader=b1c1-0.3-7065185
require version-baseband=g845-00166-210105-B-7062333
| 18:34:01 |
| danielrf | * require board=crosshatch
require partition-exists=product
require version-bootloader=b1c1-0.3-7065185
require version-baseband=g845-00166-210105-B-7062333
| 18:34:10 |
| danielrf | and it does prevent running fastboot update against a non-crosshatch device | 18:34:59 |
| danielrf | but maybe you're right that flash-all.sh which flashes the bootloader and radio as well don't have similar checks | 18:35:30 |
| danielrf | Probably still a good idea to add a note anyway | 18:37:00 |
| Xe (xe/they) | when setting your own custom root of trust, is there a way to get rid of the custom OS warning? | 18:39:44 |
| danielrf | Nope, we can't change that. | 18:41:31 |
