yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6a] jemail:
I am using PixelFlasher_Ubuntu_20_04 5.3.0.0 release on opensuse Linux.

I have downloaded the latest platform tools : platform-tools_r34.0.3-linux.zip

When selecting the platform folder I get:

023-06-07 15:21:13 Selected Platform Tools Path:
/opt/adb.

2023-06-07 15:21:13 ERROR: Android Platform Tools version is not available or is too old.
For your protection, disabling device selection.
Please select valid Android SDK.

SDK Version: None
Adb SHA256: 6e5bc20bfe13dbac79758a10837cf42841e45958c45e33a5fd54496826f3b6ab
Fastboot SHA256: a39af5d5e8e016e71d43a1dfdb2dbd08a0c329593d52f76943572ec7ebd169f9

The hashes are correct for adb and fastboot in /opt/adb.

adb devices reports:

$ adb devices
List of devices attached
xxxxxxxxxxxxxx device (id removed for privacy)

Same error running as user or root.
[Google Pixel 6a] badabing2003:
Please provide support file.
[Google Pixel 6a] jemail:
Clicking the support button when using PixelFlasher_Ubuntu_20_04 5.3.0.0 crashes the app.

I obtained a support zip using PixelFlasher_Ubuntu_22_04 and it is attached here.

The latest PixelFlasher and platform-tools_r34.0.3-windows.zip works correctly with no error about incorrect adb version.
[Google Pixel 6a] badabing2003:
I'm not sure what you mean by the latest works, because the latest logs still show the error.

Can you run this command and tell what you get?

/opt/adb/adb --version
/opt/adb/fastboot --version
[Google Pixel 6a] jemail:
What I mean is the windows version of PixelFlasher.exe 5.3.0.0 with platform-tools_r34.0.3-windows.zip works correctly when launced in Windows 10, of course.

PixelFlasher_Ubuntu_20_04 (5.3.0.0) crashed when clicking the Support button.

PixelFlasher_Ubuntu_22_04 (5.3.0.0) version did not crash when clicking the Support button and provided the support zip I uploaded for you.

The Linux version of PixelFlasher_Ubuntu_22_04 5.3.0.0 is the version causing the problem.

$ /opt/adb/adb --version
Android Debug Bridge version 1.0.41
Version 34.0.3-10161052
Installed as /opt/adb/adb
Running on Linux 6.3.4-1-default (x86_64)

$ /opt/adb/fastboot --version
fastboot version 34.0.3-10161052
Installed as /opt/adb/fastboot
[Google Pixel 6a] badabing2003:
Not sure what to tell you.

Tested it on 3 different environments.

Ubuntu 20.04 in WSL

2023-06-07 13:52:46 Selected Platform Tools Path:

/opt/adb.

SDK Version: 34.0.3-10161052

Adb SHA256: 6e5bc20bfe13dbac79758a10837cf42841e45958c45e33a5fd54496826f3b6ab

Fastboot SHA256: a39af5d5e8e016e71d43a1dfdb2dbd08a0c329593d52f76943572ec7ebd169f9

Ubuntu 22.04 in WSL

2023-06-07 13:54:43 Selected Platform Tools Path:

/opt/adb.

SDK Version: 34.0.3-10161052

Adb SHA256: 6e5bc20bfe13dbac79758a10837cf42841e45958c45e33a5fd54496826f3b6ab

Fastboot SHA256: a39af5d5e8e016e71d43a1dfdb2dbd08a0c329593d52f76943572ec7ebd169f9

Debian Linux 11.7

2023-06-07 14:35:36 Selected Platform Tools Path:

/opt/adb.

SDK Version: 34.0.3-10161052

Adb SHA256: 6e5bc20bfe13dbac79758a10837cf42841e45958c45e33a5fd54496826f3b6ab

Fastboot SHA256: a39af5d5e8e016e71d43a1dfdb2dbd08a0c329593d52f76943572ec7ebd169f9

Did this exactly on all 3 platforms

cd ~
wget https://dl.google.com/android/repository/platform-tools_r34.0.3-linux.zip
unzip platform-tools_r34.0.3-linux.zip
sudo mv platform-tools /opt/adb

I don't have OpenSuse, but I don't expect anything to behave differently.

Basically PF calls adb --version from the path specified

Parses the output and determines the version.

The fact that the version is empty in your case suggests that the output is different.

If you can redirect the output to a file and send me the file, just in case it has some weird characters or formatting is not the same, I can take a look at it.

/opt/adb/adb --version > /tmp/adb_version.txt
[Google Pixel 6a] jemail:
Output of:

/opt/adb/adb --version > /tmp/adb_version.txt

Here are the contents of the text file:

Android Debug Bridge version 1.0.41
Version 34.0.3-10161052
Installed as /opt/adb/adb
Running on Linux 6.3.4-1-default (x86_64)

Here is the output of adb version as an attachment.

Does PixelFlasher need to be run as root, in a root shell or via sudo as a normal user or as a normal user with no elevation?
[Google Pixel 6a] jemail:
I want to update Pixel6a to the latest May security patch using the factory image. I have the factory image. I have installed Magisk 26.1 on the pixel6a using Pixel Flasher (windows version) and patched the boot image.

To update and root using Magisk do I now select the patched boot image and then press the Flash Pixel Phone?

Do I need to unlock the bootloader using and advanced option?

Or does pixel Flasher unlock the boot loader then relock it after flashing the factory image and the patched boot image?
[Google Pixel 6a] badabing2003:
Pixel Flasher "Flash Pixel Phone" expects your phone to be already unlocked.

You can do that one time before attempting to do the flash, keep in mind that anytime you unlock your bootloader, your phone will get wiped (by design)
[Google Pixel 6a] jemail:
Some more info on PixelFlasher adb version none on opensuse.

I installed adb (package android-tools) through zypper then got the output of adb --version:

# adb --version
Android Debug Bridge version 1.0.41
Version 34.0.1-android-tools
Installed as /usr/bin/adb

This is still showing SDK version none in PixelFasher.

Thank you for a wonderful android tool.
[Google Pixel 6a] badabing2003:
Ok,

Try two things.

1- If you download and install from here: https://developer.android.com/tools/releases/platform-tools instead of using package manager, and unpack it in your home, and point PF to platform-tools directory (not the parent) and don't add / remove any files.

2- https://github.com/badabing2005/PixelFlasher/suites/13515342480/artifacts/742829715 see if it makes a difference.
[Google Pixel 6a] jemail:
1. Followed instructions which produces the same error:

2023-06-11 20:16:37 Selected Platform Tools Path:
/home/ian/platform-tools.

2023-06-11 20:16:37 ERROR: Android Platform Tools version is not available or is too old.
For your protection, disabling device selection.
Please select valid Android SDK.

SDK Version: None
Adb SHA256: 6e5bc20bfe13dbac79758a10837cf42841e45958c45e33a5fd54496826f3b6ab
Fastboot SHA256: a39af5d5e8e016e71d43a1dfdb2dbd08a0c329593d52f76943572ec7ebd169f9

$ /home/ian/platform-tools/adb --version
Android Debug Bridge version 1.0.41
Version 34.0.3-10161052
Installed as /home/ian/platform-tools/adb
Running on Linux 6.3.6-1-default (x86_64)

$ /home/ian/platform-tools/fastboot --version
fastboot version 34.0.3-10161052
Installed as /home/ian/platform-tools/fastboot

2. Following the link results in a 404 not found.
[Google Pixel 6a] badabing2003:
2- You would need to sign-in to Github to see it, let me know if it still does not work.
[Google Pixel 6a] jemail:
I tested the zip file you provided with the github link.

The results are the same:

Looking for Android Platform Tools in system PATH environment ...
Found Android Platform Tools in /home/ian/platform-tools

2023-06-12 19:05:21 ERROR: Android Platform Tools version is not available or is too old.
For your protection, disabling device selection.
Please select valid Android SDK.

SDK Version: None
Adb SHA256: 6e5bc20bfe13dbac79758a10837cf42841e45958c45e33a5fd54496826f3b6ab
Fastboot SHA256: a39af5d5e8e016e71d43a1dfdb2dbd08a0c329593d52f76943572ec7ebd169f9
Load time: 1 seconds

I even put PixelFlasher in the same folder as adb and fastboot but I get the same error.

This is a strange problem and I'm not sure what else we could do here. Does PixelFlasher use sudo in any way?
[Google Pixel 6a] badabing2003:
OK try this build.

It adds debug messages.

Enable verbose logging and select the Platform tools
[Google Pixel 6a] jemail:
I will test your new build version on Linux.

In the mean time I'm using the windows version on windows 10.

When performing Flash Pixel Phone while having selected a factory image and the Magisk boot image with wipe ALL data and Flash to both slots, I notice that data is not wiped at all. All apps previously installed are still present and with their previous configuration.

I am assuming that selecting a Factory Image and selecting wipe ALL data should be equivalent to a Factory Reset?

Also when using the Package Manager -> Get all package names there is an error about grep not being an internal or external command.
[Google Pixel 6a] jemail:
Testing with debug PixelFlasher on openSUSE Linux results in:

2023-06-12 22:07:03 Selected Platform Tools Path:
/home/ian/platform-tools.
debug: identify_sdk_version:theCmd: "/home/ian/platform-tools/adb" --version
debug: identify_sdk_version:response.stdout:
debug: identify_sdk_version:response.stderr: /bin/sh: /tmp/_MEIiToDWl/libreadline.so.8: no version information available (required by /bin/sh)
/bin/sh: /tmp/_MEIiToDWl/libreadline.so.8: no version information available (required by /bin/sh)
/bin/sh: /tmp/_MEIiToDWl/libreadline.so.8: no version information available (required by /bin/sh)
/bin/sh: /tmp/_MEIiToDWl/libreadline.so.8: no version information available (required by /bin/sh)
/bin/sh: symbol lookup error: /bin/sh: undefined symbol: rl_trim_arg_from_keyseq, version READLINE_8.2

2023-06-12 22:07:03 ERROR: Android Platform Tools version is not available or is too old.
For your protection, disabling device selection.
Please select valid Android SDK.

SDK Version: None
Adb SHA256: 6e5bc20bfe13dbac79758a10837cf42841e45958c45e33a5fd54496826f3b6ab
Fastboot SHA256: a39af5d5e8e016e71d43a1dfdb2dbd08a0c329593d52f76943572ec7ebd169f9

I have attached support file.
[Google Pixel 6a] badabing2003:
The Python code is bundled into a single executable by PyInstaller.

Pyinstaller does not bundle system libraries like libreadline and expects it to be on the system.

It appears that it is not on your system or there is a mismatch version or is incompatible.

Can you try this on your OpenSuse

sudo zypper search libreadline
sudo zypper install libreadline8

You might also want to update system libraries

sudo zypper update
sudo ldconfig

and test if it got created

ls -l /usr/lib*/libreadline.so*

It should point to the version 8

PF is expecting it to be found on your phone.

I'll update PF to push / use busybox version

Typically toybox should be available

$ which grep
/system/bin/grep
$ ls -l /system/bin/grep
lrwxrwxrwx 1 root root 6 1972-10-04 07:45 /system/bin/grep -> toybox
$ which toybox
/system/bin/toybox

Seeing your flash logs

I see these that I don't like

Warning: skip copying bootloader_a image avb footer (bootloader_a partition size: 0, bootloader_a image size: 12384852).
Warning: skip copying bootloader_b image avb footer (bootloader_b partition size: 0, bootloader_b image size: 12384852).
Warning: skip copying radio_a image avb footer (radio_a partition size: 0, radio_a image size: 96493708).
Warning: skip copying radio_b image avb footer (radio_b partition size: 0, radio_b image size: 96493708).
Writing 'boot_b' (bootloader) unable to update boot image: use unmerged...

Considering that you want to wipe.

Please do the following.

Avoid using Android Platform-Tools 34.x, use 33.0.3

https://dl.google.com/android/repository/platform-tools_r33.0.3-windows.zip - Windows

https://dl.google.com/android/repository/platform-tools_r33.0.3-darwin.zip - Mac

https://dl.google.com/android/repository/platform-tools_r33.0.3-linux.zip - Linux

Select Force option when flashing, and select "Flash both slots" (which you are selecting).
[Google Pixel 6a] jemail:
I'll reply to the linux stuff in this post. I will run all comands in a root bash shell.

zypper search libreadline:

# zypper search libreadline
Loading repository data...
Reading installed packages...

S | Name | Summary | Type
---+--------------------------+---------------------------------------+--------
| libreadline-java | Java Wrapper for the EditLine Library | package
| libreadline-java-javadoc | Javadoc for libreadline-java | package
| libreadline5 | The Readline Library | package
| libreadline6 | The Readline Library | package
i+ | libreadline8 | The Readline Library | package
| libreadline8-32bit | The Readline Library | package

zypper is updated.

ldconfig outputs nothing.

# whereis ldconfig
ldconfig: /usr/sbin/ldconfig /usr/share/man/man8/ldconfig.8.gz

ls -l /usr/lib*/libreadline.so*:

# ls -l /usr/lib*/libreadline.so*
lrwxrwxrwx 1 root root 18 Mar 19 17:18 /usr/lib64/libreadline.so.8 -> libreadline.so.8.2
-rwxr-xr-x 1 root root 352K Mar 19 17:19 /usr/lib64/libreadline.so.8.2
[Google Pixel 6a] jemail:
Setting the options you indicated allowed a complete Factory Flash with all data wiped.

Thank you for the help on this issue.
[Google Pixel 6a] badabing2003:
Based on the output you provided, it appears that libreadline.so.8 is installed on your openSUSE system. However, it seems that the library search path is not properly configured, which could be causing the issue.

Please set the Library path like this.

(preferable to set it in your env, but you can try it in the terminal where you launch ./PixelFlasher from

export LD_LIBRARY_PATH="/usr/lib64:$LD_LIBRARY_PATH"
[Google Pixel 6a] jemail:
After setting the environment variable I get the same error: (I noticed that LD_LIBRARY_PATH did not exist in my environment as a variable so I set it to /usr/lib64 without the colon in my environment)

2023-06-13 09:21:32 Selected Platform Tools Path:
/home/ian/platform-tools.
debug: identify_sdk_version:theCmd: "/home/ian/platform-tools/adb" --version
debug: identify_sdk_version:response.stdout:
debug: identify_sdk_version:response.stderr: /bin/sh: /tmp/_MEIlGwMUt/libreadline.so.8: no version information available (required by /bin/sh)
/bin/sh: /tmp/_MEIlGwMUt/libreadline.so.8: no version information available (required by /bin/sh)
/bin/sh: /tmp/_MEIlGwMUt/libreadline.so.8: no version information available (required by /bin/sh)
/bin/sh: /tmp/_MEIlGwMUt/libreadline.so.8: no version information available (required by /bin/sh)
/bin/sh: symbol lookup error: /bin/sh: undefined symbol: rl_trim_arg_from_keyseq, version READLINE_8.2

2023-06-13 09:21:32 ERROR: Android Platform Tools version is not available or is too old.
For your protection, disabling device selection.
Please select valid Android SDK.

SDK Version: None
Adb SHA256: 6e5bc20bfe13dbac79758a10837cf42841e45958c45e33a5fd54496826f3b6ab
Fastboot SHA256: a39af5d5e8e016e71d43a1dfdb2dbd08a0c329593d52f76943572ec7ebd169f9

Note however that:

# whereis sh
sh: /usr/bin/sh /usr/share/man/man1p/sh.1p.gz

not /bin/sh in the debug message.

Thank you for providing help.
[Google Pixel 6a] badabing2003:
PF runs the command with subprocess.run python command with shell=True

And that uses the system's default shell to execute the command.

In this case it is /bin/sh (nothing is hard-coded)

can you check if there is a symbolic link

ls -l /bin/sh

If not, please create one

sudo ln -sf /usr/bin/sh /bin/sh

And lastly please verify the libreadline version

objdump -p /usr/lib64/libreadline.so.8 | grep -i version

It should be READLINE_8.2
[Google Pixel 6a] G5-User7080:
Okay so I'm like preeeeeetty sure my phone is a P6a, but umm

I tried to do the Full OTA thing since for some reason adb sideload fails from my terminal side,...

Doing the same thing as last month and the month before but it only shows

adb sideload F:\Pixel6a\bluejay-ota-tq3a.230605.010-a67dbf36.zip
serving: 'F:\Pixel6a\bluejay-ota-tq3a.230605.010-a67dbf36.zip' (~0%) adb: failed to read command: No error

Edit:

after rebooting to System PixelFlasher finds it all now, but I'm a bit worried now, when I click "Flash now" for Full OTA it shows this, with "Factory Image" poiting to the OTA, I assume thats fine yes?

and when I take a look at the script used it shows this

"C:\Software\Tools\adb\adb.exe" -s 25131JEGR02308 sideload "F:\Pixel6a\bluejay-ota-tq3a.230605.010-a67dbf36.zip"
echo rebooting to bootloader ...
"C:\Software\Tools\adb\adb.exe" -s 25131JEGR02308 reboot bootloader
echo Sleeping 5-10 seconds ...
ping -n 5 127.0.0.1 >nul
ping -n 5 127.0.0.1 >nul

I'm a bit hung up about it immediately using the "sideload" command while I'm still in system, does it automatically reboot to sideload mode before starting this script or is it intended that I run "adb reboot sideload" in terminal first?

Would you recommend using factory image with the "keep data" option or the "Full OTA" option using ota.zip?
[Google Pixel 6a] badabing2003:
See if bash is another link

ls -l /bin/bash
[Google Pixel 6a] badabing2003:
support file would help me understand the issue
[Google Pixel 6a] G5-User7080:
I didn't actually get to flash anything,.. so idk how much will be in there but here if it helps anything.
[Google Pixel 6a] badabing2003:
In recovery or sideload mode the device model is not identified.

But in adb or fastboot it is.

The last action you took, was in adb, and selected OTA, and it did not complain about the device, because it knew it was bluejay

But you choose to edit the script and then cancelled the OTA flashing.

try again now and let it continue and capture the logs.
[Google Pixel 6a] G5-User7080:
so just to confirm, I can continue like this, attempting an OTA sideload through PF while being booted into System?

I don't wanna end up doing an in-system ota such as the magisk-restore-images thing thats buggy
[Google Pixel 6a] badabing2003:
yes, PF takes care of booting to the proper mode depending on the selections you have made, no need for you to manually boot to a specific mode
[Google Pixel 6a] G5-User7080:
tyvm, it worked like a charm.

here are the logs in case u want them since u newly added the OTA function (thx btw).

also for some reason patching the boot image failed and then it lost adb connection after that, dis- and reconnecting the device and re-scanning solved it.

For the future, would you recommend using this Full OTA method or flashing Factory with keep data?

I've only used OTA sideload til now since I heard it was considered safer, but I don't really know what the difference is actually, since OTA is also just the firmware in a different format afaik.
[Google Pixel 6a] badabing2003:
The reason you lost adb the first time is probably because it got disconnected or you nudged the wire.

2023-06-13 16:09:51 ERROR: Could not push /storage/emulated/0/Download/boot_91cb501f.img
Return Code: 1.
Stdout: adb: error: failed to read copy response
C:\Users\REDACTED\AppData\Roaming\PixelFlasher\boot_images4\91cb501f589879dde613f59bfa2ad3df87dc52e2\boot.img: 1 file pushed, 0 skipped. 144.4 MB/s (67108864 bytes in 0.443s)
adb: error: failed to read copy response
.
Stderr: .
Aborting ...
}

The second time around the device was offline, probably you needed to accept the ADB connection trust dialog,

2023-06-13 16:10:19 ERROR: Could not delete /storage/emulated/0/Download/boot_91cb501f.img
Return Code: 1.
Stdout: .
Stderr: adb.exe: device offline
.
Aborting ...

As for my preference.

I switched to OTA method, and currently I flash both slots OTA (one by one)

It is significantly slower than flashing factory, but at least I have two slots that are bootable, in case anything bad happens.

With Factory flashing, only one slot will be bootable, even if you flash to both.
[Google Pixel 6a] G5-User7080:
so it might still be the wire / usb port after all and that it worked with PF but not manually mightve been just luck? mhhhh

yea the second time I just tried again immediately after, I didnt actually replug anything yet, so makes sense it failed too

don't need any trust dialogues, I disabled the usb authorisation timeout in dev options, the only authorised computer is mine anyway, and I don't wanna risk having no adb when I didnt connect my phone in 7 days and something breaks.

OTA it is alright, why both slots?

Say I'm on slot A, May with rooted boot.img, then I OTA, it'll install June and the corresponding unrooted boot.img to slot B, right?

Then for July, it'll install July and corresponding unrooted boot.img on slot A over May with rooted boot.img?

So lets say July OTA breaks, can't it still fall back to previous stable and rooted June build on slot A?
[Google Pixel 6a] badabing2003:
Right, by the way, if you select the patched boot instead of the stock boot, before hitting the Flash Pixel Phone button (even with OTA), you will get rooted in one shot, you don't have to do it after flashing stock, unless you want to.

The reason you want to flash both slots is to make sure that both slots have the same version of the firmware, because booting to an older firmware is not guaranteed to work without problems. Apps get modified that could only be compatible to the latest firmware.

You might get away with functioning phone, but might also encounter rand crashes / freezes.
[Google Pixel 6a] G5-User7080:
I just prefer to not flash rooted boot.img, I just patch it and then later live boot it and install through Magisk.

That way I can also restore stock boot from Magisk.

How do you flash to both slots though? I only see the option to "flash to inactive slot".

mhh, well you'd probably OTA first, see if it went fine and only then OTA the other slot as well I suppose..

So you are on A, OTA will default to B and switch to B, then wouldn't you just OTA normally again to update A as well, no "flash to other slot" option needed?

Aka do the same thing twice?
[Google Pixel 6a] badabing2003:
Yep, makes sense, and whatever makes you feel safer.

Exactly, and you would see that with Full OTA selected, you can not select Flash To Inactive Slot, or Flash to Both Slots.

You just have to do it two times in a row.
[Google Pixel 6a] jemail:
Output of ls -l /bin/bash:

# ls -l /bin/bash
-rwxr-xr-x 1 root root 872K Mar 19 22:54 /bin/bash
[Google Pixel 6a] badabing2003:
That is the correct, /bin/sh is correctly pointing to/bin/bash and /bin/bash is not an another link

Which brings us back to LD_LIBRARY

I still suspect LD_LIBRARY_PATH is not picked up,

Did you set it in a terminal and then launch PixelFlasher from that terminal, to make sure PF picked it up.

export LD_LIBRARY_PATH=/usr/lib64
echo $LD_LIBRARY_PATH
<full path to pf>

I'm also curious for the output of this command

ldconfig -p | grep readline
[Google Pixel 6a] jemail:
Used the first three commands with correct paths.

$ echo $LD_LIBRARY_PATH
/usr/lib64
/home/ian/platform-tools/PixelFlasher

I still get the same result:

2023-06-15 08:19:58 ERROR: Android Platform Tools version is not available or is too old.
For your protection, disabling device selection.
Please select valid Android SDK.

SDK Version: None
Adb SHA256: 6e5bc20bfe13dbac79758a10837cf42841e45958c45e33a5fd54496826f3b6ab
Fastboot SHA256: a39af5d5e8e016e71d43a1dfdb2dbd08a0c329593d52f76943572ec7ebd169f9
Load time: 3 seconds

Output of ldconfig -p | grep readline:

# ldconfig -p | grep readline
libreadline.so.8 (libc6,x86-64) => /lib64/libreadline.so.8

Again, thank you for trying to resolve this issue.
[Google Pixel 6a] badabing2003:
I would have preferred if you ran with the debug build to see if you got a different debug message with your latest test.
[Google Pixel 6a] jemail:
My apologies, here is the info after setting $LD_LIBRARY_PATH in terminal and launching with full path:

2023-06-15 13:54:37 Selected Platform Tools Path:
/home/ian/platform-tools.
debug: identify_sdk_version:theCmd: "/home/ian/platform-tools/adb" --version
debug: identify_sdk_version:response.stdout:
debug: identify_sdk_version:response.stderr: /bin/sh: /tmp/_MEI42hPn3/libreadline.so.8: no version information available (required by /bin/sh)
/bin/sh: /tmp/_MEI42hPn3/libreadline.so.8: no version information available (required by /bin/sh)
/bin/sh: /tmp/_MEI42hPn3/libreadline.so.8: no version information available (required by /bin/sh)
/bin/sh: /tmp/_MEI42hPn3/libreadline.so.8: no version information available (required by /bin/sh)
/bin/sh: symbol lookup error: /bin/sh: undefined symbol: rl_trim_arg_from_keyseq, version READLINE_8.2

2023-06-15 13:54:37 ERROR: Android Platform Tools version is not available or is too old.
For your protection, disabling device selection.
Please select valid Android SDK.

SDK Version: None
Adb SHA256: 6e5bc20bfe13dbac79758a10837cf42841e45958c45e33a5fd54496826f3b6ab
Fastboot SHA256: a39af5d5e8e016e71d43a1dfdb2dbd08a0c329593d52f76943572ec7ebd169f9
Load time: 1 seconds

Support zip attached.