yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7] badabing2003:
I looked at your log file, for support issues, please ask them in the forum, not only it benefits others who would run into similar issues, someone other than myself could help you out, and you won't have to wait for my availability.

Furthermore support files generated in PF redact all sensitive information, which is safer to post than and direct log file, not only that, it has additional items that are not in the logs, which are important when troubleshooting, things like file structure, database, visual event analysis .. (all redacted of course).

I see two issues.

1- You're using a problematic Magisk version, PF warned you about it, but you chose to proceed regardless.

2- You have Magisk modules that could be incompatible with Android 14, you should first update all modules then disable them (at least the ones that potentially could cause issues) then repeat the process.

These for example

Pixelify enabled v2.2
Pixelify uninstaller services enabled 1
Advanced Charging Controller (ACC) enabled v2023.8.19

And you're better off with

Universal SafetyNet Fix enabled v2.4.0-MOD_1.3

Note 2.0

Few considerations that makes this not feasible / useful.

I can't tell from the firmware name that you're doing a major OS upgrade, unless I hard code into the app to recognize specific firmware names / dates, which I don't like to do unless it is absolutely necessary,

In any case, regardless of the OS version, the only time both slots are bootable, if they are identical, so even if one has Android 13 August and flashes Android 13 September, only September slot would work.

If you want to downgrade, even from September to August, you'd have to wipe.

Historically, two slots being bootable was not possible, until it was discovered that it is possible with full OTA if both slots are flashed the same firmware. (One could be rooted, and the other stock, that works, but they both have to be the same build / version)

Unlike Firmware flashing, where you can control which slot you want to flash and you can also flash both slots with one go, with OTA sideloading, it is always the inactive slot, and always no wipe.

There is no possibility of dual slot flashing.

If you want to flash both slots, you repeat the flashing one more time.

So if you're on A, it flashes to B, you boot to B, and it finalizes, then you repeat, and this time it will flash A.

Technically it is possible to avoid booting and making PF repeat the process, but I rather not, I prefer the user to understand the process, make sure the other slot is fully functional and only then flash the other, this way, you always have something to fall onto if flashing went sideways.

To summarize, it's really advisable to do the twice flashing with every release, as the OS upgrade release is no exception.

The only exception to this is when there is a bootloader rollback concern, which we've only seen once, and in fact PF checks (hardcoded) if you're phone is upgrading from a version that would fall into this situation, and warn you to make sure to flash both slots.
[Google Pixel 7] eegee-za:
Hi @badabing2003 thank you for taking the time to explain in detail. I was not sure if the log files had sensitive data, and that is why I sent it privately. I will try again next weekend.

Here are my takeaway points from the experience:

Post the log files publicly, they are already redacted

Interact more with the forum members, for increased knowledge sharing and support

Unhide Magisk before patching, otherwise it will use the "root" method no questions asked instead of the "app" method

Disable all Magisk modules, as a safety net (no pun) to rule out any incompatibilities

Don't downgrade the USF version based on another forum post, first check if the latest has an issue and don't enable it right off the bat (based on previous point)
[Google Pixel 7] Cpm0813:
When I do update my P7 to A14, if I just use the factory image and update like I normally do monthly, will that be enough, or do I have to do extra steps?
[Google Pixel 7] t-ryder:
Yep, that's what I did. Flashed to both slots tho. All good. My P7 on A14 runs very nice. Had no need for a full wipe. Maybe backup your stuff before the upgrade. I always do so by using Swift Backup and ADB Explorer (on Windows).
[Google Pixel 7] badabing2003:
Nope, post the support file created by PF.

The logs are not sanitized, the process of creating support.zip does the redaction and packaging into support.zip

Yep

This is only necessary, if the app is newer than the root, if they are at the same version, you don't need to unhide, because you can use the root to create a patch.

Always a good idea, Safetynet so far has not posed any problems, but many others do.

No I suggested that you use

Universal SafetyNet Fix enabled v2.4.0-MOD_1.3

instead of

Universal SafetyNet Fix enabled v2.4.0-MOD_2.0

Which would be a downgrade, you can read up about it in SafetyNet threads.

You can, but my preferred method is using full OTA, see this post for details and the linked post there why i think it is better.
[Google Pixel 7] badabing2003:
Update Release:

Oct 11, 2023 v5.8.1.0 release

Added data for Pixel 8, Pixel 8 Pro

Build workflow update, sha256 checksums are now published along the binaries.
[Google Pixel 7] t-ryder:
Today my P8 arrived. Thanks dude, you're awesome.
[Google Pixel 7] badabing2003:
I'm jealous;)
[Google Pixel 7] Cpm0813:
I tried using a patched OTA. Something went wrong about 75% of the way into uploading/serving the file and now phone keeps saying corrupted. Help!

Edit: Somehow I was able to get to a point where I was able to attempt to flash the patched OTA again, which actually succeeded this time. Unfortunately, I seem to have lost root.

Also, PixelFlasher never indicated it was done, so I don't know if it actually finished properly or not.
[Google Pixel 7] t-ryder:
Post support/log file package to see what went wrong.
[Google Pixel 7] badabing2003:
What @t-ryder says.
[Google Pixel 7] Cpm0813:
PixelFlasher_2023-10-15_21h20m38s is where it only got to 75%.

Thank you!
[Google Pixel 7] badabing2003:
I looked at your support files.

The current state of your phone is:

Selected Device on 2023-10-16 06:16:21:
Device ID: REDACTED
Device Model: panther
Device Active Slot: a
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: d4e552d0:26301
Magisk Path: /data/app/~~EKtvFJTJT1ZXpv9ZdvjUzA==/com.topjohnwu.magisk-8xiFAtNYJUl7UoH14PITOQ==/base.apk
Checked for Package: com.topjohnwu.magisk

The reason it is not rooted is because it never got to flashing the patch after completing the OTA flash

This is a sign of bad connection or the phone was unplugged before the flashing was complete.

serving: 'C:\Users\REDACTED\Downloads\panther-ota-up1a.231005.007-16d1f4a7.zip' (~94%)
Total xfer: 2.00x
rebooting to bootloader ...
Sleeping 5-10 seconds ...
Reading current slot value ...
Current slot: [a]
Comparing the current slot with the previous active slot ...
"Current slot has changed, this is good."
flashing pf_boot ...
< waiting for REDACTED >

As for your first failure at 75%

Again, it's a sign of bad connection / wire / usb driver / port or the phone removed.

serving: 'C:\Users\REDACTED\Downloads\panther-ota-up1a.231005.007-16d1f4a7.zip' (~74%)
serving: 'C:\Users\REDACTED\Downloads\panther-ota-up1a.231005.007-16d1f4a7.zip' (~75%) adb: failed to read command: No error
[Google Pixel 7] t-ryder:
@Cpm0813 Check that you use the original USB cable, or a real high quality data cable for flashing. Make sure there are no problems with the USB port(s), hub and/or controller(s) or any adapters.

Check your windows device manager. I once tried to flash my Pixel 7 with a cable I trusted, but always lost connection during flashing the factory image. Made me freak out, so I did some analysis and found the cable to be faulty/low quality.

Try different USB Ports, try USB ports with different USB versions. Check if you have latest Google USB drivers installed properly. Check if your antivirus solution causes problems.
[Google Pixel 7] Cpm0813:
I use the Anker PowerLine+ USB 3.0 cable, https://www.amazon.com/dp/B01M5GMZ6X , which I have always found to be a great cable, attached to a USB 2.0 port, which I find more reliable than my USB 3.0 port on my laptop. In this post, https://xdaforums.com/t/stock-a14-now-available.4634351/#post-89087626 , it is discussed to use Platform tools 34, due to hanging after reboot, which may be what happened to me. It rebooted directly into a operable Android configuration, not to another screen to continue the flashing process.

Edit: I went through the process again; I think it was fully successful this time, please see attached.
[Google Pixel 7] t-ryder:
Until further notice all users should only use platform-tools_r33.0.3 which is linked below. There have been many reports for months now regarding massive problems with the newer platform tools.

Proton Drive

Securely store, share, and access your important files and photos. Anytime, anywhere.

drive.proton.me
[Google Pixel 7] badabing2003:
Well said,

Unless you're on a Mac which has issues with 33.0.3 not being able to get into userspace fastboot (fatsbootd).

34.x does not need to get into fastbootd hence it works better on a MacOS
[Google Pixel 7] manjaroid:
I have the Anker silicone version but spent the bigger bucks for its power delivery. For Pixel flashing Amazon may still have Google branded USB-A to USB-C cables. I bought some a couple years ago for about $7 per for connecting Pixels to computers without USB-C. My main laptop has USB-C but I prefer flashing through a USB-A port and the $7 cable never fails. Never have problems because of USB 3.0 either.
[Google Pixel 7] badabing2003:
New Release:

Oct 18, 2023 v5.8.2.0 release

Added `Wipe` option (only available in custom flashing), this will wipe userdata after flashing, required for first time vbmeta verification disabling.

Added validation checks to make sure A and B slot vbmeta verity / verification states match.

Added a warning when toggling `Disable Verification` to inform about the the potential wipe implications.

Display both slots verity / verification states when displaying device details.

Extract vbmeta.img if found to easily select it for patching.

Improved paste button which now dynamically selects what to paste based on the custom flash option selection.
[Google Pixel 7] Base2:
@badabing2003 ,

Downloaded PixelFlasher_Ubuntu_22_04 v5.8.2.0. When run it pops up About PixelFlasher Version 5.8.1.0, Update Version v5.8.2.0 is available.

...My bad, should have replied in the main support thread, Oh well, not going to double post....
[Google Pixel 7] badabing2003:
You're probably are still running 5.8.1.0

If you check the status bar and see that it shows 5.8.2.0 and you're still getting the update notification, then please create a support file.

However I strongly suspect that somehow you're still running 5.8.1.0
[Google Pixel 7] Base2:
@badabing2003

My double bad.... You're correct, when I overwrote(tried) the file to my executables directory from the download it failed silently the first time. I've been a linux user since '92(Yggdrasil) and I don't usually make mistakes like that.

On a slightly different subject set up a wireless adb debugging instead of Usb that I usually use before starting PixelFlasher, pressed the scan button and selected the tcpip connection. When I opened the adb wireless manager window nothing was listed. Where is the information stored?

I've tried this with both adb platform tools 33.0.3 and 34.0.3.

What is the proper way to invoke adb wireless debugging? I'm obviously getting dumber with age....
[Google Pixel 7] badabing2003:
Yeah, Google complicated the Wireless debugging for security reasons, in the past it would always be listening on port 5555, but now you have to:

Enable both options

View attachment 6023046

Authorize for your wifi network when it prompts you (when you toggle Wireless debugging)

Then you have to click on Wireless debugging again to enter its settings.

View attachment 6023049

Next you have to pair it with your phone by clicking on Pair device with pairing code

This will give you something like this

View attachment 6023050

Next in PF Wireless manager fill in the 3 values and hit the Pair button

View attachment 6023052

This will only pair your device, you're still not connected. :) (don't blame me, talk to Google)

Your device should display that it successfully paired, and should list your PC in the paired devices section, and normally should take you back to wireless debugging page

There will be IP:Port part there. (Note, the port is now different than the port you used when pairing)

In PF, type in the IP and the port, and hit Connect.

If everything goes as planned, you should be connected, PF should say so, and show in history (in green) the details, it should also drop down the device selection, and you can select the device.
[Google Pixel 7] Base2:
Didn't have a problem with any of that, I can establish a wireless debugging session. I completed all of those steps.

[

adb connect 192.168.32.144:46553

connected to 192.168.32.144:46553

]

My question is about the empty adb wireless manager window.... The intent would appear to be to record wireless connections and allow for easy re connection to previously established connections from inside of PixelFlasher. And / or annotating or modifying previously established connections. No? I can't really analyse the code very well, I'm not a python guy. More fortran, c, cobol(once upon a time) and assembly.
[Google Pixel 7] badabing2003:
If you establish connection through PF, the history will be filled, and you would be able to reconnect by clicking on a line from history and hitting the connect button (assuming that parameters like ip / port has not changed and your device is still paired, by the way, if you disable wireless debugging and enable it back, the port changes)

PF has no way of knowing what kind or connections you have made outside of PF, if there was a way, it would defeat the point of all the measures Google has taken to securing wireless connection.
[Google Pixel 7] Base2:
OK

$ adb kill-server # start over clean

$ ./PixelFlasher_Ubuntu_22_04 # I run PF

PF starts adb:

adb -L tcp:5037 fork-server server --reply-fd 4

But: there is not connection to adb so I can't open an adb shell (defined as Linux Shell: /usr/bin/konsole in Settings) to start a first tcpip connection:

$ adb connect xxx.xxx.xx.xxx:zzzzz

The scan button does nothing because there is no established connection to detect and I can't use the adb wireless manager window because it is empty. How do I establish a first wireless connection from inside PF? Is there another way? I'm really missing something here.
[Google Pixel 7] badabing2003:
Please follow the steps from this post, and tell me where it's not working (if it is not working).

You realize that the list being empty or not has nothing to do with establishing a connection, the list is a history of wireless connection attempts you have made in PF.

You don't need to have a history to be able to connect.

Unless I'm not understanding you, I don't see any issue.
[Google Pixel 7] Base2:
Ah, I now see My issue with the wireless manager window on linux. Expanded the window horizontally and the entry fields are on a right sidebar, not in a popup window... Started all over from scratch again, deleted my paired device on my phone, deleted PF application files, killed adb, and followed the post intended exactly.

Now I can now make a wireless connection and get a "Device Info" so I'm a lot further along. Will continue to explore the program a bit so I'm thoroughly familiar with this mode before I have to flash next month's update.

Thank you so very much for your help, attention, and superlative support. You're the best! (Somebody must have been slipping me a cups of dumbass instead of coffee in the morning the month....)
[Google Pixel 7] badabing2003:
Just keep in mind, although you can perform adb commands over wireless, you can't flash with fastboot or sideload, which is what is used to flash the device.
[Google Pixel 7] banshee28:
Well, I have been flashing my P7P for months w/o issues. However today I decided to update my daughters P7 to the latest A14, and apparently got a boot loop!

This phone was already rooted running latest Magisk Canary (maybe part of the issue), and maybe 2 months with no updates. I tired to install latest stable Magisk using PF but of course the Dev version was newer so I could not easily and left it alone.

It proceeded to flash then on fastbootd got stuck for a long time. So after 15 mins of PF being hung and phone not moving from that screen, I choose to reboot from the fastbootd screen. IT booted and has the google logo for about 2 seconds then reboots.

Any advice here?
[Google Pixel 7] badabing2003:
It looks like a communication issue.

Sending sparse 'product_b' 1/12 (262112 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed

Make sure you have a good connection, latest USB drivers. good cable, USB 2.0 port ...

And try again, if it does not run into communication issue, it should fix it.
[Google Pixel 7] banshee28:
WOW, I got it working!!! :LOL:

Not sure what the problem was, possibly even a bad cable? I normally never use PF for fastboot commands, and honestly never had to use fastboot commands directly. I was about to do so, then figured since I was in fastboot already would PF see it, and of course it it. This is by design, I guess I just got a bit anxious!

PF seen is as "fastboot", and I simply choose all the same options already there and it worked as expect!
[Google Pixel 7] banshee28:
Yep, was just posting that's what I was thinking too, thanks man! I need some new high quality USB cables, LOL
[Google Pixel 7] omegalulred:
So I have rooted the phone and everything is ok, now i want to update with the OTA zip file and KEEP all my data

Magisk is hidden, so i have to setup the hidden package name in Pixel Flasher settings.

Download latest OTA for my phone (P7)

Connect phone and select it on Pixel Flasher drop down

Select phone image (previously downloaded image)

Patch image

Select patched image and flash phone

View attachment 6025409

Is it that simple? Do i get to keep everything on my phone? Magisk, modules etc.

I'm dumb so just trying to make sense of it all, and to keep my data, def don't want to wipe the phone

Send help please and thanks
[Google Pixel 7] badabing2003:
1. It's good to do that, but if you're rooted, PF can use the rooted Magisk to create a patch.

4. I'm assuming that is the one from step 2 and not some past OTA image.

Before flashing, it is always a very good idea to click on Magisk Modules Manager and disable modules (some are known to be safe, but if you don't know if your modules are safe, you're better off disabling them)

Yes it is that simple.
[Google Pixel 7] ldeveraux:
I don't use the Full OTA image because it doesn't check the option to Keep Data. DOes it still keep all the data despite that?
[Google Pixel 7] badabing2003:
If you read the OP of the main thread you'd find your answers and most likely few more that you're prepared to ask next.

If you don't find the answers you seek, please post.
[Google Pixel 7] ldeveraux:
I sympathize that we as developers assume that users should have read all of our documentation. I also recognize that that's not really how XDA works ;)
[Google Pixel 7] badabing2003:
All or our documentation is a stretch, I don't read all documentation of every software I use, I glance briefly, and try to intuitively figure out the usage, but when I have a question, or something I don't understand, I fallback to the documentation / FAQ, and in case of posts on a forum, I quickly read the first page, definitely OP, and few of the most recent posts / pages to see if my questions are answered.

Is it too much to expect that? I believe it is even in the forum rules.
[Google Pixel 7] ldeveraux:
Nobody reads the forum rules either...
[Google Pixel 7] omegalulred:
Ok wait a moment, flashing OTAs doesn't keep data. Oof
[Google Pixel 7] simplepinoi177:
It might not be in the Forum Rules (except maybe for Rule #1 "Search before posting....Whether you have a question...it's very likely that someone has already asked that question or shared that news.; but it doesn't directly pertain to reading the OP), but what you mention at the end of your first paragraph definitely is pointed out to in the thread Forum Etiquette

TheByteSmasher said:​

4.

***REMEMBER THE 5 MINUTE RULE***

The 5 minute rule, as it applies to conversations, states that “You must be a part of a conversation for at least 5 minutes prior to asking a question.”​

a. This same rule applies in forums as well. Read at least 10 pages or 2 days’ worth of posts PRIOR to asking a question.​

b. There is little more that will set off seasoned forum members that the save question being asked 2 or 3 pages in a row because someone figured they would just “Pop on” and ask a question in the first topic they thought was appropriate.​

​

7.

READ THE OP

.​

a. The OP (Original Poster) is the individual who creates a thread. Commonly OP is the term used for the first post(s) on the first page of a thread, such as this one. I'll be referring to the common definition of the initial few posts.​

b. A lot of the redundant posts have already been answered in the OP.​

c. Failure to read the OP (+ the other initial post by the Topic’s creator) often leads to post after post of members saying the same thing…READ THE OP.​

😅👍
[Google Pixel 7] Randomsanity:
I just followed the steps in the main pixel flasher thread and my device did not get rooted. It's still showing as an x in pixel flasher.

Magisk app is showing up when booted, but it shows as installed: n/a.

Do I have to follow the steps again from the start? Been a while since I rooted a device.
[Google Pixel 7] badabing2003:
You shouldn't need to, but it's hard to tell where it failed without a support file, besides the steps cover different paths, and just saying I followed the steps does not tell me much.

On the other hand providing a support file tells me exactly what was done at what point and I don't have to ask you about all the interactions you did with the app and in what sequence.

Obviously any interactions with the phone directly outside of the app will still be a black hole.