yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8] amajamar:
First of all, thank you for your hard work on this. Your app worked flawlessly for me a couple of weeks ago setting up my P8. In the past I have manually done this, but your app is great.

My question is, since I plan on taking OTA's in the future, but did not know about the above quoted post, and I rooted my phone with your app, as indicated in the instructions, did I not set up the device to take OTA's without a wipe? Because I got the phone set up just the way I want it...

Thanks in advance for you help.
[Google Pixel 8] badabing2003:
As is indicated in the guide.

OTA never wipes.
[Google Pixel 8] amajamar:
Sorry, I accidentally quoted the wrong post. See above, that's what I was concerned about. Thanks.
[Google Pixel 8] badabing2003:
My response does not change.

If you are setup properly and plan to do OTA, and don't change the verity / verification states from your current state, then there will be no wipe concerns.
[Google Pixel 8] badabing2003:
Update Release:

Dec 29, 2023 v6.5.1.1

Support for PlayIntegrityFix 15.1 added keys.

Improved auto-fill (from device) missing fields.

Dec 29, 2023 v6.5.1.0

Added Bulk Reprocess json file(s) (detects module flavor / version and outputs compatible format, similar to previously included Reprocess Pif feature which only applied to the Active Pif).

Get donor device's Pif print, now outputs @osm0sis v5 fork format print (needless to say, donor device must be connected).

Adding to Pif favorites now auto-fills the label with device brand and device model.

Other minor improvements.
[Google Pixel 8] badabing2003:
-double post- deleted
[Google Pixel 8] amajamar:
Great thanks for your reply. Have a good new years!
[Google Pixel 8] badabing2003:
New Release:

Dec 30, 2023 change log:

Pif Manager option to Force First API to 25 (some prints like Xiaomi.eu are missing the value and that would cause newer devices to fail Device Integrity).

Pif Manager options are now saved so that each time you open Pif Manager, the last settings are loaded.

Bug Fix: Enable checkboxes in Magisk Modules.

In Magisk Modules, add VersionCode column.

Better positioning of Pif Manager with respect to the parent window.
[Google Pixel 8] clueless_stranger:
Hey there,

Thanks a lot for Pixel Flasher! I'm planning on using it in near future, once I receive my Pixel 8. I was wondering if the Pixel Flasher integrates https://github.com/daboynb/PlayIntegrityNEXT/tree/main Play Integrity NEXT, as it seems like there are otherwise problems with using banking apps and Google Wallet: https://xdaforums.com/t/banking-apps-not-working-with-magisk-and-lsposed-pixelxpert.4647861/
[Google Pixel 8] badabing2003:
PlayIntegrityNext is nothing other than an older version of PlayIntegrityFix (stripped) that gets prints from Xiaomi.eu apk.

You're better off using latest @osm0sis module, and finding a pif print.

You have the option to grab xiaomi.eu print in PixelFlasher just like it does in PlayIntegrityNext, but why do that if you can get some random print (that is less commonly utilized) by clicking on Get TheFreeman193 button instead.

See below, on why I decided not to support PlayIntegrityNext

PlayIntegrityNEXT support · Issue #136 · badabing2005/PixelFlasher

Hey! Thanks for all your work! Could you please add support for https://github.com/daboynb/PlayIntegrityNEXT It has the same custom pif.json location as the original module (/data/adb/pif.json)

github.com
[Google Pixel 8] clueless_stranger:
Thanks for getting back to me so quickly! I must say, I've become a noob...

(The last time I flashed a ROM or rooted my phone was back in 2015, when I had a Sony Xperia Z Ultra... I then switched to a Blackberry Passport, and after that, a Nokia Flip 2720 - yes, a dumb phone! - that I've been using until now. I remember back in the days, before my Android days, when I had an iPhone 4 and all I had to do was click a single button and my iPhone would be jailbroken, Cydia would be installed and the jailbreak would stick, even after every subsequent iOS update...)

Anyways, all I basically want is to root my phone in order to use the AI features only available to the US as a Canadian thanks to GMS Flags, all the while being able to still use Google Wallet and my banking apps...

Is the PIF managed automatically while flashing in Basic Mode so that banking apps and Google Wallet works, or does one have to go into the PIF Manager of Pixel Flasher and fiddle around for such apps to work? I noticed you had added screenshots to the Github, so I'm guessing that a guide is in the works...

Thanks again for your work, and your almost daily updates are really impressing!
[Google Pixel 8] badabing2003:
For rooting, see the main thread's OP or at Github

To get wallet working, you need to get into the PIF game, and that is separate from rooting.

There is a guide already written, if you check the Main thread's 3rd post, you'd see it.
[Google Pixel 8] badabing2003:
Latest Release:

Dec 30, 2023 v6.5.3.0 change log:

Added Smart Paste Up to simplify getting operational for beginners.

It automatically sets the First API to 25 if it is not set, otherwise keeps the value.

It automatically reprocesses the output window content, to meet module / version requirements.

It automatically pastes the processed data into Active Pif window

If Auto Update pif.json is checked.

Updates the correct pif.json on the device.

Kills the unstable GMS.

Runs Play Integrity Check if Auto Check Play Integrity is selected.

Updated screenshot for the guide.

Pif guide in OP is updated as well.
[Google Pixel 8] badabing2003:
New Release:

Jan 07, 2024 v6.6.0.0 change log:

New Feature: Download any Google device firmware or full OTA directly in PixelFlasher.

Automatic detection and notification if an update is available for the selected device.

New feature: Cancel / reset OTA update pushed by Google (need to be used prior to a reboot). Binary graciously provided by @capntrips.

Removed outdated links from help menu.

kdrag0n's safetynet-fix

Displax's safetynet-fix

Added new links to the help menu

osm0sis's PlayIntegrityFork

chiteroman's PlayIntegrityFix

TheFreeman193's Play Integrity Fix Props Collection

Full OTA Images for Pixel Phones / Tablets

Factory Images for Pixel Phones / Tablets

Full OTA Images for Pixel Watches

Factory Images for Pixel Watches

Full OTA Images for Pixel Beta 14

Factory Images for Pixel Beta 14

Enable Magisk Kitsune patch creation using Magisk core component (previously disabled due to incompatibility and patches were only created using the manager).

Miscellaneous improvements, bug fixes and code refactoring
[Google Pixel 8] t-ryder:
You could or maybe should write to these AV vendors telling them it's false positives... Bitdefender is going totally nuts on Pixel Flasher.
[Google Pixel 8] badabing2003:
It's hopeless and never ending.

I've done it in the past with virus total, but chasing multiple lazy anti virus vendors is futile.
[Google Pixel 8] c19932:
hey guys,

im trying to upgrade with Jan build (did Dec before with success) with pixelflasher, but somehow this time im getting this error

2024-01-07 16:14:41 ERROR: Encountered an error while flashing

Traceback (most recent call last):

File "Main.py", line 3768, in _on_flash

File "modules.py", line 2861, in flash_phone

TypeError: argument of type 'NoneType' is not iterable

did a search and didnt find anything. could someone help me out please? Thanks!
[Google Pixel 8] badabing2003:
Please create a support file so that i can troubleshoot.
[Google Pixel 8] c19932:
here it is. Thanks a lot for your help
[Google Pixel 8] c19932:
I figured it out. I renamed the image .zip file back to the original name (shiba-ota-uq1a.240105.004-bdf10181.zip) and it worked!
[Google Pixel 8] Toastking:
Hi,

So far I've been able to dodge all the root detection mechanisms on the Pixel 8, but it's honestly way too much effort having to keep track of all the custom modules and changes and so on, so I want to give up root since there are no real advantages apart from Lucky Patcher.

So, my question is, if I have used Pixel Flasher so far to flash the patched stock images, what do I need to do now to lose root? I want to go back to stock only, no magisk needed anymore. Do I just use Pixel Flasher to flash a ROM without the patching step?

Also, do I need to re-lock the bootloader in order to re-enable automatic OTA updates from Google? If yes, will locking the bootloader wipe the device?

Thanks in advance
[Google Pixel 8] badabing2003:
You want to unroot.

Select the stock boot and Flash it to both slots.

If you plan to lock the bootloader, I would make sure that both slots are fully on latest (flashing stock OTA) twice in a row before locking the bootloader, and making sure both slots are bootable.

And yes, when you lock the bootloader a wipe will be performed.
[Google Pixel 8] badabing2003:
Bugfix Release:

Jan08, 2024 v6.6.0.1 change log:

Bug Fix: Toolbar menus were interfering with the download menus and triggering a download when toolbar was modified.
[Google Pixel 8] m0yP:
Thank you for creating this amazing tool. I just received my Shiba yesterday and rooted it without any issues thanks to this amazing piece.

I'm old school so I kind of miss the CMD commands but this is way better and easier for everyone.

My only question and it's mainly to confirm: next month's update is just a matter of downloading OTA, patching it with Magisk and flash it over? I don't wanna loose root and don't want to setup again everything.
[Google Pixel 8] badabing2003:
Yep exactly,

And for good measure if you want, flash twice in a row and you'll get both slots bootable.
[Google Pixel 8] lorenzin:
Please help! After a failed attempt to OTA-update my rooted Pixel 8 (running patched November OTA, flashed to both slots) to the January OTA with PixelFlasher, my device got stuck with error that it was corrupted and booted to just a black screen with "android" fading in and out. Support file attached...

I downloaded PixelFlasher 6.6.01 and OTA shiba-ota-uq1a.240105.004-bdf10181, ran PixelFlasher, scanned and found my Pixel 8, processed and patched the OTA, selected the Patched file, and clicked Patch Pixel Phone. It looked it was proceeding normally, then this happened:

serving: 'C:\Users\Lisa\Documents\Pixel 8\OTA\shiba-ota-uq1a.240105.004-bdf10181.zip' (~63%)

serving: 'C:\Users\Lisa\Documents\Pixel 8\OTA\shiba-ota-uq1a.240105.004-bdf10181.zip' (~64%) adb: failed to read command: No error

Error: The sideload command encountered an error, aborting ...

You should manually reboot to system if necessary.

2024-01-10 11:36:38 ERROR: Encountered an error while running flash script.

theCmd: "C:\Users\Lisa\AppData\Roaming\PixelFlasher\factory_images\shiba-ota-uq1a.240105.004\flash-pf.bat"

Return Code: 1.

Stdout: .

Stderr: None.

Aborting ...

2024-01-10 11:36:38 INFO: Flashing was aborted.

This could be user initiated or a problem encountered during flashing.

2024-01-10 11:36:38 Getting device: 38311FDJH004DX state ...

Current device mode: ERROR

You might need to manually reboot your device.

I hit the power button to reboot, and it gave a frightening red error "Your device is corrupted. It can't be trusted and may not work properly", and when I continued, it gave the warning error about the bootloader being unlocked, then the Google logo, and now it's just stuck at this "android" screen.

Update: I was able to hold down the power button until it turned off, then use power+volume down to get into bootloader screen, then tried fastboot set_active other to force it to boot from both a and b slots. Getting the same error and behavior on both slots. Not sure what to do next - I'd rather not sideload the OTA zipfile (and lose root) unless I have to. Would it help to flash the November patched init_boot.img, since that's what was on here before?

Any suggestions greatly appreciated!
[Google Pixel 8] badabing2003:
This looks like a communication issue.

Make sure USB drivers from help menu are installed

Make sure you're using good cable, and not touching anything while flashing

USB port could be a factor, usually USB 2.0 is more reliable

Don't use USB hub

If it doesn't work, try on another PC, it's definitely communication issue.

How to recover?

If you are in recovery mode, after making sure of the above, do the OTA sideload again.

If that doesn't work, get into bootloader mode, and use factory image to flash in PixelFlasher instead of OTA.

The preference is OTA.

Don't worry about the corrupt message, flashing OTA will most likely fix it, and it is harmless.
[Google Pixel 8] badabing2003:
New Release:

Jan 10, 2024 v6.6.1.0 change log:

Changed PixelFlasher icons to dark icon (artwork provided by @T-Ryder).

Potential fix for #144, when getting firmware / ota download links, fallback to ignore ssl errors, if ssl errors are encountered.

Add ssl verify ignore fallback to any download (also display warning).

Add button in Pif Manager to convert key=value format (similar to env or older .prop format) to json format.

Device Info now gets props as root if the device is rooted.

Miscellaneous minor fixes and improvements.
[Google Pixel 8] lorenzin:
Thank you very much!!!!! I switched to a USB-C to USB-C cable and tried again, and it worked. I really appreciate your help...

Dumb question: when I flashed the OTA back in November, I did it twice, which I thought meant both the active and the inactive slot would have the new rooted OTA image. My impression was that if I had a future problem flashing an update, I could manually switch to the inactive slot and my phone would still work.

In this case, after the first attempt to flash failed and led to the "device is corrupted" error, when I rebooted into fastboot and manually switched to the other slot, I still got the same error. Was my original impression incorrect? (I tried searching for an answer to this question but didn't find anything obvious. If there's somewhere I should have looked and didn't, I would really appreciate a pointer to help me understand better!)
[Google Pixel 8] badabing2003:
Your assumption is correct, to a certain extent.

One of the requirements for both slots to be functional is that they both have to be on the same firmware version.

The minute you flashed the January OTA, and although it failed halfway, it had written enough to be different and hence your weren't able to both to the alternate slot.

That is a a guess because after failure, I don't see anything in the logs.
[Google Pixel 8] t-ryder:
Sounds like a f* up cable. Use a proper high quality data cable for flashing, and try different USB 2.0 ports. Make sure your onboard USB hub has correct drivers and no errors in device manager and you got the Google USB drivers installed properly. I once had a recurring flashing error on my Pixel 7 with a ****ty cable always screwing up at around ~60% when flashing images. Checked my USB ports, bought proper pricy cable and go.

EDIT: See you got it fixed. Good.

Folks, get rid of ****ty cables and buy some ANKER or other USB-C high quality data cables.
[Google Pixel 8] tzyoong:
Could I flash the Android QPR2 Beta 3 to my UQ1A.240115.004 (Android 14 Stable) using OTA?
[Google Pixel 8] badabing2003:
I would expect the answer to be yes. However I have not tried it myself so can't say for sure.

Perhaps other users who might have tried it can chime in.
[Google Pixel 8] superwahwah:
hello, in order to flash the new january version with root and magisk, should I patch again the new file and deactivate magisk first?
[Google Pixel 8] badabing2003:
Please check the guide in the OP of the main thread, and if any step is not clear, ask your question.

Your question suggests that you're not familar with the process, and the guide should explain all that.
[Google Pixel 8] superwahwah:
ok I will check, I did it onece last month and I am not familair with the process in indeed. That's why I ask but without check, my bad
[Google Pixel 8] Koeties:
I just wanted to add my sincere thanks to @badabing2003. Received my P8 yesterday afternoon and had it rooted and set up in a *flash*, including Playstore Integrity. Everything was a breeze. Many thanks for this excellent tool.
[Google Pixel 8] AggresiveSoldier:
I have installed the Evolution rom with custom recovery and everything.

Can i use this tool to revert back to full stock if i ever need to in the future?

During Evo installation one needs to install a new boot, dtbo, vendor_kernel_boot and vendor_boot.

Also has a custom recovery now.
[Google Pixel 8] badabing2003:
Yes, if and when you decide to go back, you just have to flash full stock to both slots, possibly wipe as well.

And only after making sure you've done that you should consider locking bootloader (if that's what you want)
[Google Pixel 8] tosho1:
I am just flashing the January OTA to my Pixel 8 and got the folloiwn log entries:

What does this mean?

Flashing was successfull, anyway.

btw. I had to download the image manually. PixelFlasher found an image, asked for the download location on my (Linux) PC, but no file there. :confused:

PixelFlasher resides on a nfs-share. Could this be a problem? I tried downloading ti nfs and to local disk. None of them worked.
[Google Pixel 8] badabing2003:
That is the message you'd see when the update payload is being streamed (sideloaded) onto your phone.

The download takes time, and it only shows up in the folder when it is complete.

Create a support file and I'll take a look if anything failed.
[Google Pixel 8] tosho1:
Sorry, my pasted code was misleading. My question was about these two lines:

Current active Slot is: [b]
Current inactive Slot is: [b]

The same slot is active and inactive at the same time? Is it some quantum magic 👻 ?
[Google Pixel 8] badabing2003:
That shouldn't happen, if you could be kind enough to generate a support file and attach it, I'll look into it and get it fixed before I release the next version.
[Google Pixel 8] m4j0r4:
My device kept going in a bootloop after a Magisk module was updated or installed. I thought flashing the patched firmware I had originally made would solve this but I got myself in a world of trouble. The device can be flashed but simply won't leave fastboot mode anymore. tried doing Flash boot and Flash Pixel Phone option but both don't solve the issue. I downloaded and flashed the same ota file I used when I patched the boot file I wanted to flash. Any guidance on what I am doing wrong here would be much appreciated cause I'm a bit at sea over what is the issue here.
[Google Pixel 8] badabing2003:
Curious, which module update caused this?

When a bad module causes bootloop, the very first thing we try is flash stock and see if the system boots normal.

Don't worry your modules won't disappear, they will just not kick in.

So try Jan OTA and select the stock boot and not the patched boot, and report back if the phone boots properly.

Then we'll tackle getting you rooted and modules enabled.
[Google Pixel 8] m4j0r4:
Downloaded and installing stock boot, however the device seems to keep returning to the fastboot state (see attached image) and doesn't seem to be able to go into ADB mode and reboot to system
[Google Pixel 8] badabing2003:
I need to see a support file to determine what is going on
[Google Pixel 8] m4j0r4:
The device keeps looping in flash
[Google Pixel 8] badabing2003:
You're trying to flash OTA.

OTA flashes in sideload mode, for the device to be able to get into sideload mode it first needs to be in recovery mode.

If you cannot get into recovery mode, then you won't be able to flash OTA.

Try putting the device into recovery mode using button (whatever it is for your device)

Or alternately considering that you are in bootloader mode, you can download and flash the factory image.

Once you get back to system you can flas OTA afterwards if you want to have both slots bootable.
[Google Pixel 8] m4j0r4:
Okay, sorry for the late update I had to travel from place to place and had no battery charger for my laptop, so I chose to let it all wait until I had a wall socket within reach. I was facing the problem with pixelflasher that the device would not reboot in to any other mode than the fastboot mode from the earlier picture. Neither flashing image factory or other updates would work.

So I decided to go the old fashion way and went to C:\Users\Administrator\AppData\Local\Android\Sdk\platform-tools cmd.exe fastboot devices:

38111FDJH005WQ fastboot

fastboot flash boot boot.img

C:\Users\Administrator\AppData\Local\Android\Sdk\platform-tools>fastboot flash boot boot.img

Sending 'boot_a' (65536 KB) OKAY [ 1.550s]

Writing 'boot_a' OKAY [ 0.128s]

Finished. Total time: 1.740s

C:\Users\Administrator\AppData\Local\Android\Sdk\platform-tools>fastboot reboot

Rebooting OKAY [ 0.000s]

Finished. Total time: 0.003s

And this actually rebooted my phone (pixel 8) in to the recovery state where you see the dead android and the ''error'' message. device rebooted and the file system started booting up again without the fasboot bootloop! However, bootloop kept on going so I launched pixelflasher again and booted the january update patch which was also able to (since the device was ADB bootable again) patch the magisk file in to the boot. flashing worked and device booted to safemode. used pixelflasher to reboot system and system worked as normal except Magisk needed additional intall from the app.

@badabing2003 I attached a support file for you that was made from the moment after I was able to flash the boot through fastboot.exe, Perhaps there is an interesting challenge for you to find out why the platform tools regular fastboot did manage to reflash the boot.img whilst pixelflasher could not seem to achieve it at that moment, <-- absolutely not meaning to say this as a ''meh meh uuuuuh platform tools fastboot could do it but pixelflasher couldn't mweh mweh mweh ;'( ) but perhaps you can find something helpfull for a future software update! Or point out to me at exactly which point I started being a dumb-ass :p

Last but not in the very least, thank you so very much Badabing for responding so quickly to my questions and helping me out with this. It's really highly appreciated that you use your skills and knowledge to help everyone get better instead of being snobby. You are one of the people that makes XDA the worldwide place to go to whenever questions arise or if help is needed. YOU ROCK!!!