Google Internal
#lynx Google Pixel 7a DVT Source • Bricked by Google Follow @GoogleInternal
#lynx
More pictures of the Pixel 7a DVT1.0
Source
• Bricked by Google
• Asset tags on back
Follow @GoogleInternal
More pictures of the Pixel 7a DVT1.0
Source
• Bricked by Google
• Asset tags on back
Follow @GoogleInternal
Google Pixel Buds 2 Engineering Sample
• Stickers on the inside of the case
• Engraving on the side and top of earbuds
• More engravings on the hinge
Follow @GoogleInternal
• Stickers on the inside of the case
• Engraving on the side and top of earbuds
• More engravings on the hinge
Follow @GoogleInternal
#hammerhead
LG Nexus 5 prototype
• taped off camera
• hole in rear housing
• diagnostics apps
Follow @GoogleInternal
LG Nexus 5 prototype
• taped off camera
• hole in rear housing
• diagnostics apps
Follow @GoogleInternal
Forwarded from Mishaal's Android News Feed
Google's method of remotely bricking leaked/stolen phones (like the Pixel 7a that recently made the rounds) is actually open source!
They generate what's called a "brick OTA" that wipes the following partitions:
vbmeta
vbmeta_a
vbmeta_b
vbmeta_system_a
vbmeta_system_b
boot
boot_a
boot_b
vendor_boot
vendor_boot_a
vendor_boot_b
init_boot
metadata
super
userdata
This "brick OTA" is pushed to devices via GOTA (Google OTA) and can be installed on both "test-keys" and "release-keys" builds, but a serial number is required before a "brick OTA" can be installed on "release-keys" builds.
Many OEMs don't use GOTA, but a lot of them now do use update_engine, so Google's new automated "Android Brick OTA generator" tool might find some use outside of Google.
They generate what's called a "brick OTA" that wipes the following partitions:
vbmeta
vbmeta_a
vbmeta_b
vbmeta_system_a
vbmeta_system_b
boot
boot_a
boot_b
vendor_boot
vendor_boot_a
vendor_boot_b
init_boot
metadata
super
userdata
This "brick OTA" is pushed to devices via GOTA (Google OTA) and can be installed on both "test-keys" and "release-keys" builds, but a serial number is required before a "brick OTA" can be installed on "release-keys" builds.
Many OEMs don't use GOTA, but a lot of them now do use update_engine, so Google's new automated "Android Brick OTA generator" tool might find some use outside of Google.