Closed AskAlice closed 4 months ago
I don't see anything you pasted above that demonstrates that PixelFlasher has even attempted to do anything, let alone cause the issues you so boldly claim. Without a support file, there's no telling of what you have done and and what had happened. Please update the title of the ticket to properly reflect reality.
As for the errors you encountered, this is known issue unrelated to PixelFlasher, and PixelFlasher has a workaround to overcome the issue, had you done a simple search in the issues you would have found the proper solution for it. https://github.com/badabing2005/PixelFlasher/issues?q=rl_trim_arg_from_keyseq
ah right here you are sir support_2024-06-24_07-42-01.zip
i also emailed you a journalctl snippet that has some coredumps of adb
yeah i normally would have used the web flasher to go back to stock though I thought it might be easier to avoid a first boot with a rooted init_boot, though didn't get that far. I left it plugged into the computer overnight and it got very warm. now the usb descriptor does not enumerate.
it's not a big deal I think i will just trade it in at ubreakifix and use my pixel 6 XL for now. i did look into flashing with the exynos tools both for windows 7 and the one made for linux. i recompiled it to match the usb device id of the pixel but by that point my device had stopped responding even if disconnected/reconnect with/without button combinations.
I read somewhere that the API level 34 or 35 platform tools are buggy in some distructive way, though i'm not too versed as to why that might be
context: i was stuck on an old build of EvolutionX rom, checked wipe on a factory (google) build and hit flash
For starters, I don't trust package managers installed Android Platform Tools. The fact that you had to do this
then ran pixel flasher, it gave me some errors so i simlinked into lib64 some bins is a bad start.
The best way is to download Google published Android Platform Tools (link available in the help menu as well as the icon/button to the left of Android Platform Tools selection.
Considering that you provided a support.zip, please go ahead and delete the log data from your messages, support.zip not only redacts your sensitive data, it is also encrypted in case anything accidentally is revealed, it's the best way to provide logs without leaking anything.
Looking at your logs, this part indicates where you ran into an issue.
Sending sparse 'super' 3/22 (254972 KB) OKAY [ 6.821s]
Writing 'super' OKAY [ 0.992s]
Sending sparse 'super' 4/22 (254972 KB) OKAY [ 6.803s]
Writing 'super' OKAY [ 1.029s]
Sending sparse 'super' 5/22 (254972 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
[liblp] Partition system_b will resize from 0 bytes to 860135424 bytes
[liblp] Partition system_dlkm_b will resize from 0 bytes to 11145216 bytes
[liblp] Partition system_ext_b will resize from 0 bytes to 295944192 bytes
[liblp] Partition product_b will resize from 0 bytes to 3758469120 bytes
[liblp] Partition vendor_b will resize from 0 bytes to 698417152 bytes
[liblp] Partition vendor_dlkm_b will resize from 0 bytes to 27504640 bytes
[liblp] Partition system_a will resize from 0 bytes to 17076224 bytes
❌ 2024-06-23 16:36:55 ERROR: Encountered an error while running flash script.
This is a communication issue, and as much as I would want PixelFlasher not to encounter this issue, it is totally out of PixelFlasher, this could happen for many reasons,
If you look at what PixelFlasher executed (it's in the logs)
#!/bin/sh
# This is a generated file by PixelFlasher v6.9.6.0
# cd /home/alice/.local/share/PixelFlasher/factory_images/shiba-ap2a.240605.024
# pf_boot.img: /home/alice/.local/share/PixelFlasher/boot_images4/dd83d031859dcee189418c9c8e8c8b7ff087cd03/init_boot.img
# Android Platform Tools Version: 35.0.1-11580240
"/opt/android-sdk/platform-tools/fastboot" -s REDACTED flash bootloader bootloader-shiba-ripcurrent-14.5-11693900.img
"/opt/android-sdk/platform-tools/fastboot" -s REDACTED reboot-bootloader
sleep 5
"/opt/android-sdk/platform-tools/fastboot" -s REDACTED flash radio radio-shiba-g5300i-240308-240517-b-11857457.img
"/opt/android-sdk/platform-tools/fastboot" -s REDACTED reboot-bootloader
sleep 5
"/opt/android-sdk/platform-tools/fastboot" -s REDACTED --skip-reboot -w update image-shiba-ap2a.240605.024.zip
This is the same thing as flash_all.sh script, adapted to your image / Android Platform Tools path, options selected. You would have ran into the same issue had you ran flash_all.sh
Sorry to hear that your device is bricked, but that's no thanks to PixelFlasher, you can blame Google for that.
ah okay fair... hmm i guess bad cable :( was far away from me on the desk ty for taking a look, i just wanted to make sure your scripting wasn't in some way different, seems that's not the case
I double checked my platform tools version as I had recently been doing some oculus development.
then ran pixel flasher, it gave me some errors so i simlinked into lib64 some bins The device was then booted on automatically from what i could tell.. I was surpised it never entered fastbootd or anything. sooo it yielded the google logo. Then it said my device is corrupt. and now it's just in exynos USB DL mode, responding only to serial at 4800 baud