IssueTracker

Hi,

Thanks much for raising this issue. This is one of our known issue, which is not documented. Having phone numbers of this long are very rare. libphonenumber cannot do anything better here.

Reasons:

• JavaScript Number type has limitation of 2^53 (9007199254740992) as the max literal it can hold. When provided more than that like "90018408059449376"(17 digit), JS starts rounding the value. Unfortunately this is within the range of possible phone number length i.e 17 digit.
• Both the alternatives leads to backward-incompatible changes as the type of the field '''national_number''' has to be changed; thus leading to client-side compile issue . Eg: setNationalNumber(1234) / conversions to payloads like JSON.

1. Marking the field as [jstype = JS_STRING]
2. Or using new JS data type BigInt.

We will update FAQ at GitHub stating some of these points. Maybe you can compare with Number.MAX_VALUE and avoid such cases. Or post request to a Java/CPP/PY libphonenumber clients, as these langs have much more matured data type systems.

Added to client FAQ as known issue. https://github.com/google/libphonenumber/pull/2674

We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

Can you try to recover the device using fastboot oem flashing unlock and then flash a working build.

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!

Please follow the below steps and try to flash the latest beta build (AP31.240617.010 ,https://developer.android.com/about/versions/15/release-notes#beta-4.1) and let us know if this helps, if not please share the details of the issues for us to further investigate this issue.

1. 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)

2. 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)

3. 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)

4. Boot the device back to fastboot mode and run the following commands:

$ fastboot snapshot-update cancel

$ fastboot -w

$ fastboot reboot

5. The "Your device is corrupt" notice will be gone and the device can boot up normally.

Thank you for reporting this issue. We have a fix rolling out in an upcoming release.

If you are unable to recover your device (like when you are unable unlock the bootloader) then we request you to reach out to our RMA support team