yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7] Randomsanity:
I think I screwed up somehow because the device threw a bunch of errors and PixelFlasher locked up.

ERROR: recoery: Failed to read 6 bytes data at offset 235 6496298: I/O Error

Error: recovery: Failed to read footer

Error: recovery: Signature verification failed

error: 21

Install from ADB complete (status 2)

This is what Pixel Flasher shows now:

Getting package com.topjohnwu.magisk path on the device ...

Package Path is: /data/app/~~A4B1t1f4LxSOKmO3PtaGVw==/com.topjohnwu.magisk-e2wE4vSKdnttZztBpHX4mw==/base.apk

Selected Device on 2023-10-27 12:15:15:

Device ID: 29221FDH20070T

Device Model: panther

Device Active Slot: b

Device Mode: adb

Has init_boot partition: True

Device is Rooted: False

Device Build: UP1A.231005.007

Device API Level: 34

Device Architecture: arm64-v8a

Device Kernel Version: 5.10

sys_oem_unlock_allowed: 1

ro.boot.flash.locked: 0

ro.boot.vbmeta.device_state: unlocked

vendor.boot.vbmeta.device_state:

ro.product.first_api_level: 33

ro.boot.warranty_bit:

ro.boot.veritymode: enforcing

ro.boot.verifiedbootstate: orange

vendor.boot.verifiedbootstate:

ro.warranty_bit:

ro.secure: 1

ro.zygote: zygote64

ro.vendor.product.cpu.abilist: arm64-v8a

ro.vendor.product.cpu.abilist32:

Device Bootloader Version: cloudripper-14.0-10529422

Magisk Manager Version: 26.3:26300

Magisk Path: /data/app/~~A4B1t1f4LxSOKmO3PtaGVw==/com.topjohnwu.magisk-e2wE4vSKdnttZztBpHX4mw==/base.apk

Checked for Package: com.topjohnwu.magisk
[Google Pixel 7] badabing2003:
that is a not a support file
[Google Pixel 7] Randomsanity:
Sorry, didn't realize. Thanks for much for the help.
[Google Pixel 7] badabing2003:
Initially your devices was at Build: UP1A.231005.007

Selected Device on 2023-10-27 11:13:24:
Device ID: REDACTED
Device Model: panther
Device Active Slot: b
Device Mode: adb
Has init_boot partition: True
Device is Rooted: False
Device Build: UP1A.231005.007
Device API Level: 34
Device Architecture: arm64-v8a
Device Kernel Version: 5.10
sys_oem_unlock_allowed: 1
ro.boot.flash.locked: 0
ro.boot.vbmeta.device_state: unlocked
vendor.boot.vbmeta.device_state:
ro.product.first_api_level: 33
ro.boot.warranty_bit:
ro.boot.veritymode: enforcing
ro.boot.verifiedbootstate: orange
vendor.boot.verifiedbootstate:
ro.warranty_bit:
ro.secure: 1
ro.zygote: zygote64
ro.vendor.product.cpu.abilist: arm64-v8a
ro.vendor.product.cpu.abilist32:
Device Bootloader Version: cloudripper-14.0-10529422
Magisk Manager Version:
Magisk Path: None
Checked for Package: com.topjohnwu.magisk

You processed the build D:\panther-ota-td1a.220804.009.a2-1ba82532.zip

Created a patch from it and tried to flash init_boot only.

That is not what the steps tell you to do,

You tried to overwrite init_boot with a mismatched patched init_boot.

Then you processed D:\panther-ota-up1a.231005.007-16d1f4a7.zip

Created a patch and then flashed OTA

Your device did not get into sideload mode

==============================================================================
2023-10-27 11:57:50 PixelFlasher 5.8.2.0 Flashing Phone
==============================================================================
Android Platform Tools Version: 34.0.5-10900879
Rebooting device REDACTED for sideload ...
Waiting 20 seconds ...
2023-10-27 11:58:17 Flashing device REDACTED ...
Active code page: 437
Current Active Slot is: [b]
serving: 'D:\panther-ota-up1a.231005.007-16d1f4a7.zip' (~0%) adb: failed to read command: No error

It could be a timing issue with the new platform tools, I see that you are using Android Platform Tools Version: 34.0.5-10900879.

So bottom line is that you have not flashed anything yet.

But you can just flash the patched boot, now that you have created one from the correct version.
[Google Pixel 7] Randomsanity:
Yes, I followed some outdated guidance in another thread the first time, which is why I did it incorrectly :(

Thanks, but I seem to fail when I try to flash just the new patched boot:

==============================================================================
2023-10-27 13:39:48 PixelFlasher 5.8.2.0 Flashing / Live Booting
C:\Users\REDACTED\AppData\Roaming\PixelFlasher\boot_images4\fe0e3cf4dc26f7076c0f526611329c9ae04cc982\magisk_patched_26300_fe0e3cf4_70a2dbd1.img ...
==============================================================================

2023-10-27 13:39:49 ERROR: Flash boot failed!
Return Code: 1.
Stdout: .
Stderr: Sending 'init_boot_b' (8192 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
.
Aborting ...

Is 34.0.5 not the latest? I downloaded earlier today.
[Google Pixel 7] badabing2003:
Double click on the label ADB Connected Devices

This should kill the adb server

Download and select platform tools 33.0.3

try again

if it doesn't work

reboot PC and try again

Make sure you have the latest USB drivers installed (link in help menu) for both adb and fastboot

Use a good cable

Preferably use a USB 2.0 port
[Google Pixel 7] ldeveraux:
Right so I have to have a conversation and make idle chitchat 5 minutes before I ask a question. Good luck with that...

Seemed like a simple ask after I just missed it (it wasn't highlighted, bolded, etc) in the OP. Give me a break.
[Google Pixel 7] simplepinoi177:
I was debating responding to this reply or not, but after taking some time to reflect on it, I'll respond not exactly to ldeveraux, but in the hopes that any new member or someone new to forums that drop by and read this will be made to understand....

Section 4 in the Forum Etiquette thread is not to be taken literally -- you're not to "make idle chitchat 5 minutes", it was a metaphor used as an example that just like "in conversations" -- you may have overlooked or missed the part "as it applies in conversations...the same rule applies in forums as well" (meaning you don't actually conversate in the forum/thread) -- don't just pop in suddenly & randomly and insert a random issue/problem that's what has been discussed for the last "5 minutes" (or literally 2 or 3 pages of the thread in this case -- because, again, the former ["5 minutes"] is a metaphor).

In this case, it was asking if sideloading OTA will wipe (which by design does not) -- which is explained in the OP. Like the Forum Etiquette thread intimates, "There is little more that will set off seasoned forum members...." as it "often leads to post after post of members saying the same thing…"; even (or especially) the OP.
[Google Pixel 7] ldeveraux:
The answer to the question I asked isn't in the OP, it's in one of the linked threads, and even there you have to read through or search hard. I tried searching this thread too for my question, didn't find the answer. I'm sensing a search related pattern here. Regardless, my question was addition to a conversation someone had just started, I didn't think it was out of place. Seems odd to call me out for continuing an on-topic conversation in a public forum, considering I myself am a seasoned forum member and my question didn't set me off.
[Google Pixel 7] badabing2003:
Seriously dude?

You posted in a device specific support thread.

The OP of which has this (see the yellow highlighted part, and the part that reads IMPORTANT)

View attachment 6030079

You can retrace your steps and check again.

Here's your post

To which I responded here:

And you couldn't easily find this?

View attachment 6030082
[Google Pixel 7] tim1aust:
I am having a problem with the platform tools today, I've used PixelFlasher for about the last 4 or 5 updates, without a hitch.

I've updated the platform tools to latest, in /opt/platform-tools.

When I specify the path in the input box, I get the error

/bin/sh: symbol lookup error: /bin/sh: undefined symbol: rl_trim_arg_from_keyseq

and a message stating my android tools is outdated.

Any help would be appreciated.

I am on latest Manjaro Linux, and my phone is P7a

PixelFlasher version is 5.8.2.0-1
[Google Pixel 7] ldeveraux:
Ironically this entire conversation could have been avoided if you had just given the answer when I asked. Guess the lesson is to not ask questions so egos don't get in the way.

Thanks for the cool software, it's very useful. Thanks for not following everyone else to tg.
[Google Pixel 7] badabing2003:
Support file please.

The issues with providing what I posted above (ie providing the extracted details and links) are:

My time, and the more I spend on answering what's already been answered, the less time I have to improve PF and other tools.

Repetition irks me, that's why PF exists (to automate the process)

Having users that expect answers on a platter without putting a minimal effort.
[Google Pixel 7] tim1aust:
Thanks for quick response.

Attached
[Google Pixel 7] ldeveraux:
I told you I put in the minimal effort. Your OP was sparse, I searched, didn't find it. End of story. I'm done being made to feel bad for asking a question about a piece of software. Shame on you for that. I finally see why everyone jumped ship to tg, this place is so welcoming and tolerant.
[Google Pixel 7] badabing2003:
Something must have changed about your shell from last month when it was working and now.

What do you get if you type

/bin/sh
[Google Pixel 7] tim1aust:
this:

[tim1@localhost ~]$ /bin/sh

sh-5.2$
[Google Pixel 7] badabing2003:
And does it work if you select the previous platform tools that you had?
[Google Pixel 7] tim1aust:
Hmnn, I get updates pretty regular, and just apply them. I try to stay up-to-date. I just installed a new kernel (6.6.0-1-MANJARO), I still have my previous kernels and could try booting one of those if you think it may help.

I can look in my cache file and try to backup to a previous platform-tools I guess. What version do you recommend for the platform-tools?

FWIW, I just started Pixelflasher from the new shell created by /bin/sh, and I get the same error about missing symbol.

I'm pretty sure I have always used /opt/platform-tools/, but can't bet my life on it. PixelFlasher was recently updated too.. it used to retain my path in that text box but it was empty when I started it today :(
[Google Pixel 7] badabing2003:
Yes it retains paths, if they are valid.

you previously had 33.0.3-8952118

You can download it from here

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

Unpack it somewhere and point to it in PF.

Does it work?
[Google Pixel 7] tim1aust:
OK, downloaded and extracted to /opt/platform-tools. Had booted my previous kernel (6.5.9-1-MANJARO) also.

Same error.

I have an appt to go to now, so won't be able to respond to any more questions/suggs for about an hour :(
[Google Pixel 7] tim1aust:
Well, I read in Android bulletin that more than a dozen security fixes were made in Nov 1 OTA, so I definitely wanted to update. So, I reverted to the old manual method (uninstall magisk images, sideload OTA, fastboot flash patched Magisk init_boot, etc) to apply this one. Definitely not as cool as using PixelFlasher, but.. I'll try it again next time and hope the dust settles. I really have no idea about that missing symbol, except guessing I have multiple .so's and my libpath is messed up or something.

Thanks for your help.
[Google Pixel 7] badabing2003:
New Release:

Nov 12, 2023 v6.0.0.0 release

More verbose logging and additional debug messages for troubleshooting.

Renamed the Verbose label to Debug.

Improve UI responsiveness when running background tasks.

Automatically detect vbmeta state for both slots, and warn if the selection would have wipe implications (this is for verity / verification disabling).

Removed Check Verity button, (verity / verification), replaced with vbmeta state reporting for both slots as part of device details.

Show Bootloader version as part of device details.

Show slot related details such as slot-retry-count, slot-unbootable, slot-successful as part of device details.

Added Reboot to Sideload option.

Graphical display of device's slot and root status.

In most cases long background processes are automatically killed with proper timeouts (when possible) and reported to unfreeze PixelFlasher.

Reworked device detection / update / refresh, reboots, PixelFlasher now automatically detects device state changes and waits exactly the time until the device state changes to the expected state. Less dependency on arbitrary timeouts.

Improved support logs sanitization.

Detect free space on the computer and block flashing if less than 5G of storage is available.

Refactor flashing function.

More response console widget log messages.

Detect currently installed OS version and block flashing older OTA (Android by default allows flashing but fails to boot).

Detect, warn and block flashing if bootloader is locked for flashes that require bootloader to be unlocked.

Added wipe option for custom flashing to easily wipe the phone when flashing vbmeta to disable verity / verification.

Report if the device is unlockable.

Bug fixes, lots of changes under the hood and miscellaneous improvements.

Added option to delete specified libraries from the PixelFlasher bundle, to let the system library be loaded instead. Needed for newer OSes that require updated libraries. See Symbol Lookup Error #109, and After a large system update (manjaro), do not work now. #111

Additional support for Scrcpy of non-Windows platforms.

Updated XDA links
[Google Pixel 7] badabing2003:
New Release:

Nov 13, 2023 v6.0.1.0 release

Added settings option to enable / disable free storage space check.

Improve storage check to follow symlinks and return the partition free space where the data resides instead of where the symbolic links resides.

Added command line support for specifying PixelFlasher config json file, use -c or --config flag followed by full file path of configuration json file.

Added command line --console (only useful on Linux / Mac) to display all PixelFlasher output to console, useful when troubleshooting.

Further improved handling of large file extraction on low memory computers.
[Google Pixel 7] rexsmith9886:
Downloaded the v6.0.1.0 release and flashed my pixel 7 the November update. everything went well but seems like the reboot gave an error in verbose logs. But in actuality phone booted fine with Magisk patch correctly. No impact on the user end but if you want to know why logs show an error, I have attached the support.zip.

2023-11-14 10:33:45 Getting device: xxxxxx state ...
Rebooting device: xxxxx to system ...
debug: "C:\Users\xxxxx\Downloads\Compressed\platform-tools\fastboot.exe" -s xxxxx reboot
ADB waiting device: xxxxx for device ...
debug: "C:\Users\xxxxx\Downloads\Compressed\platform-tools\adb.exe" -s xxxxx wait-for-device

2023-11-14 10:34:46 ERROR: Command timed out after 60 seconds

Thanks for the awesome tool. Let me know if you need anything.
[Google Pixel 7] badabing2003:
Thanks,

Everything looks good,

I'm curious if the final reboot actually took longer than 60 seconds,

That is just for safety so that PF does appear hung.

If it is taking that long, I can increase the timeout longer than 60 seconds for the final reboot.
[Google Pixel 7] rexsmith9886:
Yeah, it did took longer than 60 seconds in my case. Right, now makes sense why command failed.

60 seconds timeout is fine. My case maybe was out of random
[Google Pixel 7] badabing2003:
Thanks, I'll add another 30 seconds to the timeout, if it reboots faster PF will immediately show the device and be done, so it's just a measure to make sure it never hangs.

90 seconds should be ample enough.
[Google Pixel 7] badabing2003:
Update Release:

Nov 14, 2023 v6.0.1.1 release

Bug fix: Make sure Low memory settings are loaded at startup.

After flashing factory or OTA, on last reboot to system, increase the wait from 60 to 90 seconds to make sure the device loads all the way to system and does not timeout PF. Although the error message is benign, it creates unnecessary anxiety seeing an error message in the console and thinking that something is wrong.

Bug fix: Available storage was not computed correctly on Linux platform.

Fix and speed up MacOS platform build.
[Google Pixel 7] badabing2003:
Update Release:

Nov 15, 2023 v6.0.1.3 release

Cleanup temporary created files when using low memory option.

Don't wait for device to be available in adb when wipe option is selected. (The user would need to setup the phone for the first time, enable developer options and enable debug, which could take a while)

Add more debug messages for troubleshooting.

#117 psutil is not reporting free storage correctly on Linux platform, use shutil module instead.

Print available memory when processing Image.
[Google Pixel 7] badabing2003:
New Release:

Nov 16, 2023 v6.0.2.0 release

Removed Magisk alpha from Install Magisk module (update link is broken).

Added Special Magisk build based on versionCode 26401 that disables loading modules but keeps root, to help getting out of bootloop due to bad modules.

Bug Fix: #117 check for disk flag finally working correctly.

Bug Fix: #118 add wrap boot path in quotation marks.

With dry run selected, don't attempt to flash the patch file.

Block patch flashing if bootloader is locked.

Add settings option to bypass block flashing if bootloader is locked.

Added more debug messages on failures to further ease the troubleshooting efforts.
[Google Pixel 7] nikkiscores:
Hi,

Went to update my Pixel 7, and the new PixelFlasher is complaining that my program tools are too old. I am on Manjaro, have 34.0.4-3 installed via the official repositories. Also tried pointing to 33.0.3 and 34.0.5 in local folders. Same error. I feel like I'm missing something super basic. Output attached. Halp?
[Google Pixel 7] nikkiscores:
sorry, forgot to mention, i did google the problem before posting, saw the github thread and added libreadline* to Delete Bundled Libs. Didn't help. Or should i have added something else?
[Google Pixel 7] nikkiscores:
removed libreadline.so.8 manually, reloaded platform tools in PF, seems to work now!
[Google Pixel 7] badabing2003:
I don't see in your logs that this was done.

Make sure you launch PF, and go straight to settings.

Add the delete lib entry

Restart PF.

If you do it manually, you'd have to do it everytime.
[Google Pixel 7] nikkiscores:
right, that's the step that i skipped! works now.

so now PF is complaining about space. i assume this is space on the computer, not on the phone?

ERROR: Please check available disk space, you do not have safe levels of availabe storage to flash without risk.

Aborting ...

I have 16G free on the /home partition and 8G on the root partition, how much space does it need? (the phone has 50+G free)
[Google Pixel 7] badabing2003:
can you please do this.

1- issue the command df -h and give me the output

2- Enable debug option in PF and restart

View attachment 6034485

3- Give me updated support.zip
[Google Pixel 7] nikkiscores:
sorry, i found the github thread, disabled the free space check and am now (fingers crossed) in the process of flashing. will revert with results.
[Google Pixel 7] badabing2003:
Yeah that works only if you have more space but PF is thinking that you don't.

PF correctly reports that there is 16GB on PF Data drive, but is also reporting that your system drive /tmp has only 3GB

By doing the steps above, I'll get more information to determine if there is a bug or not.
[Google Pixel 7] nikkiscores:
that's what i was gambling on.

hmm, didn't realize it looked at /tmp by itself, i was looking at my partition manager.

>df -h
Filesystem Size Used Avail Use% Mounted on
dev 3.6G 0 3.6G 0% /dev
run 3.6G 1.9M 3.6G 1% /run
/dev/nvme0n1p2 40G 30G 7.8G 80% /
tmpfs 3.6G 91M 3.5G 3% /dev/shm
/dev/loop0 128K 128K 0 100% /var/lib/snapd/snap/bare/5
/dev/loop1 106M 106M 0 100% /var/lib/snapd/snap/core/16091
/dev/loop2 106M 106M 0 100% /var/lib/snapd/snap/core/16202
/dev/loop5 165M 165M 0 100% /var/lib/snapd/snap/gnome-3-28-1804/194
/dev/loop6 165M 165M 0 100% /var/lib/snapd/snap/gnome-3-28-1804/198
/dev/loop3 56M 56M 0 100% /var/lib/snapd/snap/core18/2790
/dev/loop4 56M 56M 0 100% /var/lib/snapd/snap/core18/2796
/dev/loop7 82M 82M 0 100% /var/lib/snapd/snap/gtk-common-themes/1534
/dev/loop8 92M 92M 0 100% /var/lib/snapd/snap/gtk-common-themes/1535
/dev/loop9 168M 168M 0 100% /var/lib/snapd/snap/jimbodicomviewer/9
/dev/loop10 41M 41M 0 100% /var/lib/snapd/snap/snapd/20092
/dev/loop11 41M 41M 0 100% /var/lib/snapd/snap/snapd/20290
tmpfs 3.6G 327M 3.3G 9% /tmp
/dev/nvme0n1p4 186G 161G 17G 91% /home
/dev/nvme0n1p1 510M 300K 510M 1% /boot/efi
tmpfs 729M 188K 729M 1% /run/user/1000

there is no bug, it's true that tmpfs has 3.3G free. i guess you don't need me to do the other steps?

however, my update completed successfully - i suppose it didn't need the full 5G?

is this a new setting in PF6? this didn't happen when i was using PF5 on the same machine just a couple of months ago.
[Google Pixel 7] badabing2003:
Yes, this is a new setting in PF6

It uses System temp to unpack the compressed files like factory / OTA, which tend to be nested.

5GB is just a safety number.

PF does cleanup after it uses it.

In your case it just happened that 3GB was enough to extract the files.
[Google Pixel 7] nikkiscores:
thanks!

so for future reference, how would a responsible user with a <5G tmpfs handle it? i assume manual unpacking using another partition is the only way?
[Google Pixel 7] badabing2003:
You can increase / tmp space

Manual unpacking is not going to help much, unless you want to stitch everything together like PF does so that files end up in PF workspace properly
[Google Pixel 7] badabing2003:
New Release:

Nov 18, 2023 v6.1.0.0 release

Renamed Magisk Modules button to Magisk as it now offers additional settings management.

Add features to manage Magisk settings through PixelFlasher. Needed for Pixel watches, as Magisk Manager app is not watch friendly.

Features available so far:

Enable / disable Magisk modules

Install Magisk module.

Enable / disable Zygisk

Enable / disable Magisk denylist

Add / remove application to Magisk denylist

Grant / deny / SU permissions to an app, with control of: screenshot

Enable / disable notifications

Enable / disable logging

Grant until (Forever, 10 min, 20 min, 30 min, 60 min)

Revoke SU permissions

Added Pixel watches to the devices list to provide additional details when a Pixel watch is selected.

Added icons to the popup menu in App Manager. screenshot

Factory / OTA download link is now a single button with a dropdown list of:

Full OTA Images for Nexus and Pixel Devices

Factory Images for Nexus and Pixel Devices

Full OTA Images for Google Pixel Watch Devices

Factory Images for Google Pixel Watch Devices
[Google Pixel 7] Yahoo1:
Hi. I have a rooted Pixel 7. Everytime I run PF, in connected devices I see "X Probably not root (Magisk Tools not found)". I have changed Magisk Package name in Settings because of hidden Magisk. I use Platform tools 34.0.5 which work just fine. What am I doing wrong? Thank you.
[Google Pixel 7] erezmil:
just to be clear before i start the process

all i need before starting with the pixel flasher is unlocked bootloader and the root itself is through the flasher?

and after the first time, would i be able to get OTAs and remain rooted?

thanks
[Google Pixel 7] badabing2003:
All you need is an unlocked bootloader , factory image, Android platform tools

Everything else is done in PF

And no, if you are rooted, you will not be able to receive OTAs

What you would do instead is every month you would download the latest factory image and flash through PF (same process)
[Google Pixel 7] t-ryder:
Would it be possible to implement an additional mode to flash the official OTA images for locked bootloader devices? I want to keep my BL locked and system non-rooted - tired of the tinkering, but real "in-system" OTA process sucks.

Like starting the app and having an option to switch to unlocked bootoader funny wonderland mode /// OR /// just flash the OTA with one click after (having dev options / ADB enabled) providing the file's path?

Installing OTAs from the regular system update is ridiculously slow sometimes even having just some MB of OTA (because of the slot A/B stuff).

Like having this as mode in Pixel Flasher:

View attachment 5770223

Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com