Google: Difference between revisions

Line 68:

Google cites their own Developer Distribution Agreement (terms of service for devs), claiming that those apps are "disruptive", as if to imply hacking or cracking. Many people claim that's an invalid excuse, and that the ulterior motive was to increase ad-revenue.

===Pixel devices bricked due to confusing reasons ===

===Pixel devices bricked due to confusing reasons===

Numerous Google Pixel phones have gotten bricked as a result of different use cases, such as accidentally switched slots, flashing custom ROMs or downgrading the bootloader version of the device after an Anti-Rollback (ARB) increment (accidentally or otherwise), or installing the June 2025 update.<ref>{{Cite web |last=Simons |first=Hadlee |date=2025-08-26 |title=Some Pixels are bricked and Google apparently won't help revive them |url=https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |url-status=live |archive-url=http://web.archive.org/web/20260108045933/https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |archive-date=8 Jan 2026 |access-date=2025-09-11 |website=Android Authority}}</ref> The device enters an emergency download state called Pixel ROM Recovery, which is a Google modification of Samsung's EUB mode on Exynos chipsets. In this mode, it refuses to enter Android recovery or Fastboot, making it near impossible to restore the operating system on the device. The only way to fix it is to use Pixel ROM Recovery to boot a special, Google-signed recovery bootloader into RAM and flash a working version of Android from there.

Line 76:

Numerous developers have worked on trying to find a solution to this issue, and have succeeded to varying extents. However, devices bricked due to the ARB trigger remain impossible to fix. Google has not provided any recovery images to resolve this issue, despite there being a sizable post on their bug tracker.<ref name=":4">{{Cite web |date=2025-08-10 |title=Pixel recovery bootloaders lack security reasoning for guarding |url=https://issuetracker.google.com/issues/437705274 |url-status=live |access-date=2025-09-11 |website=Google IssueTracker |archive-url=http://web.archive.org/web/20251004223929/https://issuetracker.google.com/issues/437705274 |archive-date=4 Oct 2025}}</ref><ref>{{Cite web |date=2025-03-12 |title=Pixel devices getting bricked / stuck in Pixel ROM Recovery after flashing AOSP-based builds with Android 15 QPR2 (BP1A.250305.019) |url=https://issuetracker.google.com/issues/402455330 |url-status=live |access-date=2025-09-11 |website=Google IssueTracker |archive-url=http://web.archive.org/web/20260205112358/https://issuetracker.google.com/issues/402455330 |archive-date=5 Feb 2026}}</ref> despite the fact that Google providing the recovery images for the repair will not compromise security, as explained by one of the developers in their report.<ref name=":4" />

=== Phone number requirement for new accounts ===

Since 2020, Google has increasingly forced users to verify phone-numbers via SMS during account registration,<ref>https://support.google.com/accounts/thread/34403939/cannot-create-a-new-google-account-it-is-requiring-a-phone-number-forced-phone-verification</ref><ref>https://reddit.com/r/degoogle/comments/oanh2p/does_google_now_require_a_phone_number_to_make/</ref> to "confirm you're not a bot"{{Citation needed}}. They have a system that immediately detects reuse of numbers, so no accounts can have the same associated number.{{Citation needed}} This, paired with [[YouTube#Forced sign-in|YouTube's sign-in requirement]], makes it impossible for users to share a single "guest" account, as is typically the case for families sharing a smart TV.

==Controversies==

@@ Line 68: / Line 68: @@
 Google cites their own Developer Distribution Agreement (terms of service for devs), claiming that those apps are "disruptive", as if to imply hacking or cracking. Many people claim that's an invalid excuse, and that the ulterior motive was to increase ad-revenue.
-===Pixel devices bricked due to confusing reasons ===
+===Pixel devices bricked due to confusing reasons===
 Numerous Google Pixel phones have gotten bricked as a result of different use cases, such as accidentally switched slots, flashing custom ROMs or downgrading the bootloader version of the device after an Anti-Rollback (ARB) increment (accidentally or otherwise), or installing the June 2025 update.<ref>{{Cite web |last=Simons |first=Hadlee |date=2025-08-26 |title=Some Pixels are bricked and Google apparently won't help revive them |url=https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |url-status=live |archive-url=http://web.archive.org/web/20260108045933/https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |archive-date=8 Jan 2026 |access-date=2025-09-11 |website=Android Authority}}</ref> The device enters an emergency download state called Pixel ROM Recovery, which is a Google modification of Samsung's EUB mode on Exynos chipsets. In this mode, it refuses to enter Android recovery or Fastboot, making it near impossible to restore the operating system on the device. The only way to fix it is to use Pixel ROM Recovery to boot a special, Google-signed recovery bootloader into RAM and flash a working version of Android from there.
@@ Line 76: / Line 76: @@
 Numerous developers have worked on trying to find a solution to this issue, and have succeeded to varying extents. However, devices bricked due to the ARB trigger remain impossible to fix. Google has not provided any recovery images to resolve this issue, despite there being a sizable post on their bug tracker.<ref name=":4">{{Cite web |date=2025-08-10 |title=Pixel recovery bootloaders lack security reasoning for guarding |url=https://issuetracker.google.com/issues/437705274 |url-status=live |access-date=2025-09-11 |website=Google IssueTracker |archive-url=http://web.archive.org/web/20251004223929/https://issuetracker.google.com/issues/437705274 |archive-date=4 Oct 2025}}</ref><ref>{{Cite web |date=2025-03-12 |title=Pixel devices getting bricked / stuck in Pixel ROM Recovery after flashing AOSP-based builds with Android 15 QPR2 (BP1A.250305.019) |url=https://issuetracker.google.com/issues/402455330 |url-status=live |access-date=2025-09-11 |website=Google IssueTracker |archive-url=http://web.archive.org/web/20260205112358/https://issuetracker.google.com/issues/402455330 |archive-date=5 Feb 2026}}</ref> despite the fact that Google providing the recovery images for the repair will not compromise security, as explained by one of the developers in their report.<ref name=":4" />
+=== Phone number requirement for new accounts ===
+Since 2020, Google has increasingly forced users to verify phone-numbers via SMS during account registration,<ref>https://support.google.com/accounts/thread/34403939/cannot-create-a-new-google-account-it-is-requiring-a-phone-number-forced-phone-verification</ref><ref>https://reddit.com/r/degoogle/comments/oanh2p/does_google_now_require_a_phone_number_to_make/</ref> to "confirm you're not a bot"{{Citation needed}}. They have a system that immediately detects reuse of numbers, so no accounts can have the same associated number.{{Citation needed}} This, paired with [[YouTube#Forced sign-in|YouTube's sign-in requirement]], makes it impossible for users to share a single "guest" account, as is typically the case for families sharing a smart TV.
 ==Controversies==