Status Update
Comments
ch...@google.com <ch...@google.com>
ch...@google.com <ch...@google.com> #3
If you are using Pixel 6 and above
Check if you can go to fastboot mode by pressing the Power button + Volume up button for 30 sec.
If yes, then backup and flash the device (
If not, follow the RMA process.
Please reach out to our RMA support team (
ch...@google.com <ch...@google.com>
ap...@google.com <ap...@google.com> #4
ap...@google.com <ap...@google.com> #5
You need to stand behind your products and be curious enough to want to investigate the issue and help customers resolve them. I am sitting here with a $1000 brick that Google refused to help me with. I gave up until I found this thread........
ap...@google.com <ap...@google.com> #6
I tried to reset a Pixel 6 with Android 15 on it to joint an MDM soloution.
ap...@google.com <ap...@google.com> #7
I fixed my Pixel 6a. Bootloader was locked and OEM unlocking was off.
I sent it to the authorized repair centre and they told me that the motherboard needs replacing. I rejected the repair. When I got my phone back, I realised the bootloader was unlocked. I used the Android Flash Tool and flashed the latest public build. Working as good as new!
ap...@google.com <ap...@google.com> #8
ap...@google.com <ap...@google.com> #9
ap...@google.com <ap...@google.com> #10
ap...@google.com <ap...@google.com> #11
Selling mine for parts or throwing the google pixel 6 pro in the trash thats where it belongs
ap...@google.com <ap...@google.com> #12
ap...@google.com <ap...@google.com> #13
Please follow the below steps and try to flash the latest beta build (AP31.240617.010 ,
-
Press vol down+power to boot the device to fastboot mode, then press vol down x 3 times and power button 1 time to enter the rescue mode. (If the screen shows that "Your device is corrupt", press the power button one more time to proceed). After a while, the device will enter the rescue mode screen. (
https://screenshot.googleplex.com/899G3mYvTQmVcHj ) -
Open
https://pixelrepair.withgoogle.com/steps and navigate to the steps, it will tell you to factory reset & reinstall OTA AP31.240617.010 (https://screenshot.googleplex.com/45BPzcjhvD5iMhQ ) -
Wait until the process is complete. After this step, the bootloader still notifies that the device is corrupted, but it can boot the device up/enter the android home screen. (
https://screenshot.googleplex.com/BPJE7uKniFtHCnU )
(Supported on the unlocked device only)
- Boot the device back to fastboot mode and run the following commands:
$ fastboot snapshot-update cancel
$ fastboot -w
$ fastboot reboot
- The "Your device is corrupt" notice will be gone and the device can boot up normally.
ap...@google.com <ap...@google.com> #14
If the software is not officially released by Google, please consider changing back to the latest public version by
NOT WORKING
ap...@google.com <ap...@google.com> #15
ap...@google.com <ap...@google.com> #16
Please follow the below steps and try to flash the latest beta build (AP31.240617.010 ,
Press vol down+power to boot the device to fastboot mode, then press vol down x 3 times and power button 1 time to enter the rescue mode. (If the screen shows that "Your device is corrupt", press the power button one more time to proceed). After a while, the device will enter the rescue mode screen. (
Open
Wait until the process is complete. After this step, the bootloader still notifies that the device is corrupted, but it can boot the device up/enter the android home screen. (
(Supported on the unlocked device only)
Boot the device back to fastboot mode and run the following commands:
$ fastboot snapshot-update cancel
$ fastboot -w
$ fastboot reboot
The "Your device is corrupt" notice will be gone and the device can boot up normally.
Description
Summary
There is a problem with the R8 shrinker in versions 8.6., 8.7., and 8.8.0, where it improperly strips code related to Java Service Provider Interface (SPI) usage. This issue occurs when a class is provided via the Java SPI API using
ServiceLoader.load(SomeInterface.class)
without direct references from other code. While the service provider class is retained, some of its code is stripped, leading to runtime errors.Affected Versions
Description
The issue arises when using Java SPI to load service providers. Specifically, when a class is loaded using
ServiceLoader.load(SomeInterface.class)
and there are no direct references to it from other parts of the code, R8 retains the service provider class but strips some of its code. This results in aNullPointerException
(NPE) during runtime.Reproduction Steps
Set up a project with the following module structure:
Implement the following code:
MainActivity.kt in the
:app
module:Api.kt in the
:api
module:MyApi.kt in the
:provider
module:add the service provider file (named com.example.api.Spi) in src/main/resources/META-INF/service/ in the provider:
Configure the
build.gradle.kts
in the:app
module as follows:Build the project in release mode with R8 enabled.
Run the application and observe the
NullPointerException
whentestApi()
is called.Expected Behavior
The service provider class and its methods should be fully retained by R8, allowing the application to run without errors.
Actual Behavior
The service provider class is retained, but some of its code is stripped, leading to a
NullPointerException
during runtime.Additional Information
The full source code for reproducing this issue can be found at:https://github.com/zhcnxf/testagp87