Themes / Apps / Mods 📳🔥PixelFlasher for Google Pixel 7 Support Thread.
- Thread starter badabing2003
- Start date
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)
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:
developers.google.com
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:
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google Developers
developers.google.com
Good to see you back @t-ryderWould 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 Developers
I'm heading out now, upon my return or tomorrow (in case I return late) I'll read this in detail, but in the meantime have you checked the built in option SIDELOAD
This is done to flash OTA
PF will reboot to sideload issuing this command
adb reboot sideload
Yes, nice to see you keeping it up. Got me a Pixel 7 after the OnePlus 9 was a letdown and the Realme GT2 pro did not make me happy totally.
So the OTA flashing for non bootloader unlocked devices is already there? I did not check PF for some time now. My bad if I did not get it.
Congrats for your new phone.
Yes OTA flashing is there, and no worries of not seeing it, the UI (not my best skill) is not the best (and the chosen platform doesn't help), some of the features are obscured and can only be discovered by clicking around.
Thank you OP for your hard work and for making our life on Pixel phones much easier 
I rooted my Pixel 7 the day after I bought it, and I can't remember if I disabled dm-verity and avb during the unlocking process (I think I ticked those flags but I'm not 100% sure). How can I check my dm-verity and avb's actual status? If they are disabled, can I re-enable them at the next update through PixelFlasher without being forced to wipe data? Thank you in advance for your answer.
I rooted my Pixel 7 the day after I bought it, and I can't remember if I disabled dm-verity and avb during the unlocking process (I think I ticked those flags but I'm not 100% sure). How can I check my dm-verity and avb's actual status? If they are disabled, can I re-enable them at the next update through PixelFlasher without being forced to wipe data? Thank you in advance for your answer.
So one has to enable advanced options, use custom flash setting to flash the full OTA file in SIDELOAD mode (dropdown menu) ... and there will be no data wipe (since I can't choose KEEP DATA)?
Correct,
You probably want to set the flag `Flash to Inactive Slot` to mimic a true OTA behavior.
I have a problem with disabling verity and verification. I've tried four times and every time it still shows me that verity is enforcing and it says verification error when I use the dump device info
Ok, how do I get that and I have already shut down my computer So I'm assuming that will affect me from getting it but I can retry it
You launch PF and in help menu you choose Generate sanitized support.zip
No need to do anything else
If I wanted to edit the flash-all.bat file in the factory image so that I could do it manually then what would it look like ex: fastboot -w fastboot --disable-verity --disable-verification update image-panther-td1a.221105.001.zip
That would do it, but will also wipe your data.
If you don't want to wipe data remove
-wI took a look at your logs, I don't see errors that would cause it not to work.
As you can see in the logs, this is what PF ran.
The commands match
Code:
chcp 437
@ECHO OFF
:: This is a generated file by PixelFlasher v4.4.0.0
PATH=%PATH%;"%SYSTEMROOT%\System32"
"C:\platform-tools\fastboot.exe" -s REDACTED --slot all --disable-verity --disable-verification flash bootloader bootloader-panther-cloudripper-1.0-9074510.img
"C:\platform-tools\fastboot.exe" -s REDACTED reboot-bootloader
ping -n 5 127.0.0.1 >nul
"C:\platform-tools\fastboot.exe" -s REDACTED --slot all --disable-verity --disable-verification flash radio radio-panther-g5300g-220908-220908-b-9040061.img
"C:\platform-tools\fastboot.exe" -s REDACTED reboot-bootloader
ping -n 5 127.0.0.1 >nul
"C:\platform-tools\fastboot.exe" -s REDACTED --disable-verity --disable-verification --skip-reboot -w update image-panther-td1a.221105.001.zip
echo Switching active slot to the other ...
"C:\platform-tools\fastboot.exe" -s REDACTED --set-active=other
echo rebooting to bootloader ...
"C:\platform-tools\fastboot.exe" -s REDACTED reboot bootloader
echo Sleeping 5-10 seconds ...
ping -n 5 127.0.0.1 >nul
ping -n 5 127.0.0.1 >nul
"C:\platform-tools\fastboot.exe" -s REDACTED --disable-verity --disable-verification --skip-reboot -w update image-panther-td1a.221105.001.zip
echo rebooting to bootloader ...
"C:\platform-tools\fastboot.exe" -s REDACTED reboot bootloader
echo Sleeping 5-10 seconds ...
ping -n 5 127.0.0.1 >nul
ping -n 5 127.0.0.1 >nul
echo flashing pf_boot ...
"C:\platform-tools\fastboot.exe" -s REDACTED --slot all --disable-verity --disable-verification flash init_boot pf_boot.img
echo rebooting to system ...
"C:\platform-tools\fastboot.exe" -s REDACTED rebootREDACTED is your device ID.
How are you check that verity is disabled?
What are you expecting and what are you getting instead?
When I use your PF to dump device info it says verity is enforcing and I want to install a custom kernel and we have to do a data wipe in order to disable verity and verification correct?
I see that you are using Safetynet module, which inherently changes that flag and few others so that is passes Safteynet.
So if I remove the safetynet fix and reboot will it go back to verity not enforcing
I don't know, possibly yes, as SafteyNet alters that.
These are questions best asked in the Kernel threads, I don't personally disable verity or verification as I don't use custom kernels, I wouldn't be the best source of the info.
As far as PF is concerned, it adds the proper flags to the fastboot command if those options are selected, and we can see that in your logs.
I'm still interested to hear back and learn.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2
Check out the verbiage "Once you're enrolled" at the bottom of this page: https://www.google.com/android/beta#devices2
where do you see boot.img ?
In the list you see boot.img?
or just the label to the left.
Select the boot and the console should show you the path and filename. PF knows that it needs to use init_boot with P7
Yeah, flash to inactive.
There is an option to install Magisk Alpha and Magisk Delta are supported, and they can be installed all from PF.
Make sure you only install one, and when installing, make sure you first unhide magisk, if you have one hidden.
After installation if PF says Magisk not found, just update the package name in the PF configuration section (Magisk delta has different package name, soon to be released next PF should do this automatically)2
You had never updated your phone previously?
Just flash to both slots and you should be fine.
Why not go with January update? or better yet on Monday with the February drop?1
You do not need to hide Magisk, as for disabling modules, it all depends on the modules, I don't disable any of mine, but then again the modules I use are basic and safe for updates.
Examples. Systemless hosts, busybox, safetynet fix, ....
You can enable/ disable modules from within PF.1 -
14
This is the support thread of PixelFlasher for Google Pixel 7
PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/updating with extra features.
Basic mode: Should suit most users. Some of the features in basic mode are:
- Simple UI interface, click and go. No more command line, no more placing all files in one directory.
- boot.img management UI, select the boot.img file to patch and click the patch button. Fully Automated patching with Magisk (without user interaction) and perform upgrades without losing root.
No more manually extracting files transferring to the phone, patching / re-flashing and doing multiple reboots.
No more setting airplane mode and clearing storage to retain Safetynet passing. - Display details of boot.img.
- SHA1 checksum.
- Origin (file it was extracted from).
- Whether it is patched or not, and if it is patched.
- What version of Magisk was used to patch it.
- On what device it was patched.
- Date of patching.
- The SHA1 of the source boot.img file.
- Option to Live boot from a choice of boot.img.
- Choose to keep data or wipe data while flashing.
- Ability to flash even if multiple devices are connected to the computer.
- Display information about the phone.
- ID
- Hardware model.
- Current installed firmware (build).
- If it is rooted with Magisk.
- Magisk version (Magisk Tools).
- Magisk Manager version (the app).
- List installed Magisk modules.
- Connection mode (Adb | Fastboot | Sideload | Recovery).
- Bootloader version.
- Android OS API version.
- Convenient quick links to download Android platform tools or device firmware.
- Magisk Manager installation UI, screenshot. Supported versions:
- stable
- beta
- canary
- debug
- Magisk modules management, enable / disable modules selectively, this comes in handy to disable suspect modules before an upgrade screenshot:
- Name
- Version
- Description
- Enabled / Disabled.
- Display Android Platform Tools (SDK) version and warn / block if the version is old.
- Install APK file from the computer onto the device.
- Advanced features are hidden to keep the interface simple and easy to follow.
- A lot of checks and validations for smooth operation.
- Automatic check for program updates.
- The ability to flash custom ROM (with or without patching boot.img)
- Option to flash to both slots.
- Option to flash to inactive slot.
- Options to disable verity and or verification.
- Ability to change the active slot.
- Ability to live boot to custom boot.img (temporary root).
- Ability to boot to recovery.
- Ability to flash custom image: boot, recovery, radio, kernel, ...
- Ability to sideload an image.
- Lock / Unlock bootloader.
- Option to gain temporary root (good for testing or checking things out).
- SOS Disable Magisk modules to get out of bootloop (experimental).
Troubleshooting:
- See this post.
- Generate Sanitized support.zip file (File Menu) and submit that with your report.
4New Release:
Dec 05, 2022 v4.6.0 release
- Added single click button to easily flash just the
boot/init_boot(stock or patched) to the phone. - #39 Display Flash Option changes in the console, and allow flashing to inactive slot in basic mode.
- #39 Do the Magisk backup only when rooted.
- Decouple OTA sideload from needing factory image.
- Other minor improvements.
2
You had never updated your phone previously?
Just flash to both slots and you should be fine.
Why not go with January update? or better yet on Monday with the February drop?2
Looking at your logs I have the following observation.
You started with an old SDK, which is not a good idea, and PF warned you about it, and you chose to proceed regardless. Don't do this again, specially on the latest phones / firmware.
Code:2022-11-17 20:08:35 ERROR: Detected older Android Platform Tools version 29.0.6-6198805 2022-11-17 20:08:51 User accepted older version 29.0.6-6198805 of Android platform tools. SDK Version: 29.0.6-6198805
At this point Magisk was not installed, and your phone was on slot b
You first processed the 220804 firmware file, and when you tried to patch, PF told you that there was no Magisk on your device.
You then manually (outside of PF) installed Magisk Manager 25.2:25200, or if it was hidden, you restored it. (just for my curiosity, which was it?)
You created a patch from 220804 firmware's init_boot
Then followed by creating a patch from 221105 factory image
The above two patches was created by PF using binaries from Magisk Manager.
Tried to flash the patched file and the phone got stuck at fastbootd.
Most likely due to using an older Platform tools.
Code:extracting super_empty.img (0 MB) to disk... took 0.002s Rebooting into fastboot OKAY [ 0.000s] < waiting for REDACTED >
You then upgraded the SDK to
Code:Android SDK Version: 33.0.3-8952118
But at this point your phone was already on slot a in bootloader mode, probably due to the previous botched flashing.
You tried to flash slot a and ran into this issue.
Code:< waiting for REDACTED > fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Still on slot a, next attempt was to flash both slots
This worked without errors and the system booted to slot b
You hid the Magisk Manager
you then processed 221105 factory image, (FYI this is unnecessary, if you do it once, nothing changes if you repeat it)
You patched this time PF using rooted Magisk
Interestingly the generated patch had a different SHA1: f44feb1bc2b8643333af5e14f0a12755b537f076
Whereas the previous patch SHA1 was 8753990ce4374d5a4509e0bae48f54e2553be216
This is a curious case, the only differences are.
875399 was patched using non-hidden Manager binaries
f44feb was patched using rooted Magisk
both same versions of Magisk.
I'd be very interested if you could share these files for me to inspect.
if you could zip the following (replace redacted with your username)
Code:C:\Users\REDACTED\AppData\Roaming\PixelFlasher\boot_images4
You then proceeded to flash to both slots again
Which went well.
End of logs
At this point your system is probably on slot a and working well.
No you didn't, or at least I didn't see that you did, If you don't mind I'd be interested in getting another support.zip from you which would include this along with the Foreign key error you encountered.
That error is benign, as PF knows how to handle it, but it is included so that I can troubleshoot and find the root cause (it happens very rarely and I'm trying to see what conditions are causing that)
Thanks and sorry for the delayed response, it takes time to process these logs.2
You need to download the factory image at the bottom. It's sorted from oldest to newest. So currently TD1A.220804.031 is the latest.
