A user with a bricked Pixel 7 Pro contacted us, and here's what we were able to find out.
Recently, a user with a prototype Pixel 7 Pro came to our Google News group. Unfortunately, his device was bricked by Google, so we were unable to get much information. However, we did determine the following based on early boot logs:
⢠The Pixel 7 Pro likely uses the Samsung S6E3HC4 display panel. For comparison, the Pixel 6 Pro uses the S6E3HC3. 9to5Google earlier said there was "no indication" that this display will appear on the Pixel 7 Pro, but boot logs show this panel is being used. Also that it will have a 3120x1440 resolution.
⢠The second-generation Tensor chip may still be using Arm Cortex-A55 cores for its little cores. This is according to a line in the BL31 log, which is the final EL3 bootloader stage. According to this line, a CPU workaround is being applied for the cortex_a55 cores. It would be very odd for a Cortex A55 workaround to be used if the Tensor 2 didn't have A55 cores.
⢠Speaking of CPU, the Tensor 2 will still have a 4+2+2 CPU cluster
⢠Other components mentioned in the boot logs include the CS40l26 haptic driver IC from Cirrus Logic, the ST21NFC NFC chip from STMicroelectronics.
⢠We can also confirm the codenames for the Pixel 7 (panther) and Pixel 7 Pro (cheetah). Codenames for other boards/products are also revealed in ABL, including "cloudripper" (dev board), "ravenclaw" (possibly Pixel 6 Pro outfitted with GS201 for testing), and "felix" (likely Pixel 7a). Interestingly, the previously leaked "lynx" codename isn't mentioned here.