Themes / Apps / Mods 📳🔥PixelFlasher for Google Pixel 7 Pro Support Thread.
- Thread starter badabing2003
- Start date
Slim2none4u
Senior Member
- Oct 28, 2011
- 880
- 544
- 49
I am flashing now. Will report back.Sooo the first preview of A14 dropped. Who's gonna try flashing it?
A NOTE!!
When using PF to do this it gives a warning about the Phone (mine being Bramble 4a5G) that you are flashing, in my case bramble-beta.
Edit: Added Support zip just for info.
Edit2: All went well and maintained root. I did disable all modules before hand.
This was all just a test to see if it works.
PLEASE DO NOT TAKE THIS AS A GUIDE!
Last edited:
I updated to the new version and everything went smoothly.
I also managed to keep the root this time. No user errors.
Slim2none4u
Senior Member
- Oct 28, 2011
- 880
- 544
- 49
So looking at this further, it appears I have 3.8 installed already.
Code:
Python 3.8.10
Code:
$ which python3
/usr/bin/python3
would be good to have option to restore stock kernel inc other partitions when you swap kernels.
instead of flashing manually or just doing a full reflash
instead of flashing manually or just doing a full reflash
I'm not sure I follow.
How would you do it manually, and how will the tool figure out your intent and do it for you?
If you're flashing multiple partitions, which by the way are in the image.zip file, and you want to be selective, it's going to take a lot more time, extracting those, and the flashing one by one.
flashing image.zip would be the easier / faster and clearer way, besides it does not require additional UI that could confuse users that don't need such advanced features.
Did I understand the request correctly?
On my Windows install using 4.7 and the lattest Platform tools 33.0.3, it starts off fine but when the phone reboots it shows unable to detect device. Its rooted and when connected to the PC all adb cmd's work perfectly.
Also, even though its rooted and working fine, it shows the "x" vs check-mark under ADB Connected Devices status. Could that be the issue?
Also, even though its rooted and working fine, it shows the "x" vs check-mark under ADB Connected Devices status. Could that be the issue?
Update: I guess I lost the option to allow root access to shell during the last update and never realized it. Added that and now it shows up as "rooted".
However flashing still shows "No device is seletectd" after rebooting. I know I had this issue before trying to remember what the solution was.
However flashing still shows "No device is seletectd" after rebooting. I know I had this issue before trying to remember what the solution was.
Last edited:
Yes that is true. You understood fine. Guess only option is manually doing it as it depends on what partitions the kernel changed.
Just a heads up/warning not to use the new version 34 of platform tools, at for whatever reason Goole seems to have done something funky, as it seems to skip booting into fastbootd and tries to flash the final few petitions without it, except it can't so it fails and will just lead to a bootloop.
I can't think of any way it adding smarts to PF to select the right partitions, the only future potential improvement I can see is that have UI similar to Odin, listing all the images in a file, or should I be listing partitions on the device?
And allowing you to select multiple of them.
Although a minor improvement, I'm not sure if it is worth the trouble.
If this interests you I suggest you submit feature request at GitHub.
It won't be a priority, but it could get done one day.
Thanks for the heads up, I'll keep an eye.
Are these widespread issues or isolated cases?
I also had this issue yesterday. I think they mistakenly released it as there is no patch notes for it.
You didn't lose that option,
You never had it set in the first place.
Looks at these logs, check the dates and the line about "Device is Rooted"
Code:
Selected Device on 2023-02-06 23:00:03:
Device ID: REDACTED
Device Model: cheetah
Device Active Slot: b
Device Mode: adb
Device is Rooted: False
Device Build: TQ1A.230105.002.A1
Device API Level: 33
Device Architecture: arm64-v8a
Device Bootloader Version: cloudripper-1.0-9231809
Magisk Manager Version: 831a398b:25206
Checked for Package: com.topjohnwu.magisk
Selected Device on 2023-02-10 19:35:24:
Device ID: REDACTED
Device Model: cheetah
Device Active Slot: b
Device Mode: adb
Device is Rooted: False
Device Build: TQ1A.230105.002.A1
Device API Level: 33
Device Architecture: arm64-v8a
Device Bootloader Version: cloudripper-1.0-9231809
Magisk Manager Version: 831a398b:25206
Checked for Package: com.topjohnwu.magisk
Selected Device on 2023-02-10 19:38:49:
Device ID: REDACTED
Device Model: cheetah
Device Active Slot: b
Device Mode: adb
Device is Rooted: False
Device Build: TQ1A.230105.002.A1
Device API Level: 33
Device Architecture: arm64-v8a
Device Bootloader Version: cloudripper-1.0-9231809
Magisk Manager Version: 831a398b:25206
Checked for Package: com.topjohnwu.magisk
Selected Device on 2023-02-10 19:41:18:
Device ID: REDACTED
Device Model: cheetah
Device Active Slot: b
Device Mode: adb
Device is Rooted: False
Device Build: TQ1A.230105.002.A1
Device API Level: 33
Device Architecture: arm64-v8a
Device Bootloader Version: cloudripper-1.0-9231809
Magisk Manager Version: 831a398b:25206
Checked for Package: com.topjohnwu.magisk
Selected Device on 2023-02-10 19:44:11:
Device ID: REDACTED
Device Model: cheetah
Device Active Slot: b
Device Mode: adb
Device is Rooted: False
Device Build: TQ1A.230105.002.A1
Device API Level: 33
Device Architecture: arm64-v8a
Device Bootloader Version: cloudripper-1.0-9231809
Magisk Manager Version: 831a398b:25206
Checked for Package: com.topjohnwu.magisk
Selected Device on 2023-02-10 19:47:45:
Device ID: REDACTED
Device Model: cheetah
Device Active Slot: b
Device Mode: adb
Device is Rooted: False
Device Build: TQ1A.230105.002.A1
Device API Level: 33
Device Architecture: arm64-v8a
Device Bootloader Version: cloudripper-1.0-9231809
Magisk Manager Version: 831a398b:25206
Checked for Package: com.topjohnwu.magisk
Load time: 11 seconds
Selected Device on 2023-02-10 19:51:53:
Device ID: REDACTED
Device Model: cheetah
Device Active Slot: b
Device Mode: adb
Device is Rooted: False
Device Build: TQ1A.230105.002.A1
Device API Level: 33
Device Architecture: arm64-v8a
Device Bootloader Version: cloudripper-1.0-9231809
Magisk Manager Version: 831a398b:25206
Checked for Package: com.topjohnwu.magisk
2023-02-10 20:00:03 Scanning for Devices ...
1 Device(s) are found.
Selected Device on 2023-02-10 20:00:04:
Device ID: REDACTED
Device Model: cheetah
Device Active Slot: b
Device Mode: adb
Device is Rooted: True
Device Build: TQ1A.230105.002.A1
Device API Level: 33
Device Architecture: arm64-v8a
Device Bootloader Version: cloudripper-1.0-9231809
Magisk Manager Version: 831a398b:25206
Checked for Package: com.topjohnwu.magisk
Magisk Version: 831a398b:25206
Magisk Config SHA1: 5a03a7d73f5b7a2d4fa11ea3615945be8475dcc1
Magisk Modules:
De-bloater enabled v1.0
Selected Device on 2023-02-10 20:05:37:
Device ID: REDACTED
Device Model: cheetah
Device Active Slot: b
Device Mode: adb
Device is Rooted: True
Device Build: TQ1A.230105.002.A1
Device API Level: 33
Device Architecture: arm64-v8a
Device Bootloader Version: cloudripper-1.0-9231809
Magisk Manager Version: 831a398b:25206
Checked for Package: com.topjohnwu.magisk
Magisk Version: 831a398b:25206
Magisk Config SHA1: 5a03a7d73f5b7a2d4fa11ea3615945be8475dcc1
Magisk Modules:
De-bloater enabled v1.0
Systemless Hosts enabled 1.0
Flash Mode: dryRun
Custom Flash Options: True
Disable Verity: False
Disable Verification: False
Flash Both Slots: False
Force: False
Verbose Fastboot: True
Temporary Root: False
Flash To Inactive Slot: False
Selected Device on 2023-02-10 20:07:50:
Device ID: REDACTED
Device Model: cheetah
Device Active Slot: b
Device Mode: adb
Device is Rooted: True
Device Build: TQ1A.230105.002.A1
Device API Level: 33
Device Architecture: arm64-v8a
Device Bootloader Version: cloudripper-1.0-9231809
Magisk Manager Version: 831a398b:25206
Checked for Package: com.topjohnwu.magisk
Magisk Version: 831a398b:25206
Magisk Config SHA1: 5a03a7d73f5b7a2d4fa11ea3615945be8475dcc1
Magisk Modules:
De-bloater enabled v1.0
Systemless Hosts enabled 1.0On 2023-02-10 20:00:04 you must have enabled that option, but you did not flash after that (you only did a dry run) to say that you lost it after flashing, that should not happen at all, and all this time I have never seen that happen.
Also keep in mind, after flashing is completed or anytime you reboot from fastboot to System PF will always show no device is detected / selected.
That is because, for PF to detect that a device is connected, it needs to keep the script running and constantly doing adb check, and the reboot could take time, meanwhile you would be under the impression that flashing is not completed and PF will appear hung.
It is by design that as soon as flashing is completed, PF clears the device selection and reports that flashing is complete.
If you want to select your device again, you should do a scan and then select the device.
I only know it to occur on the Pixel 7 Pro as that is the device I own, but judging from the release notes that Google did put out and the nature of the issue, I suspect it will likely affect any device that relies on rebooting to the userspace fastbootd as part of the update process, though I have no idea what (if any) other devices also require this.
For what it's worth I've created an issue in Google's issue tracker in the hope that it will be picked up and fixed sooner by someone who has a much deeper knowledge of Android then I.
Google Issue Tracker
Last edited:
flashed February patch over jan patch and magisk delta root was retained including data on pixel 7
all went good. thanks
I use flash on both slots for dirty upgrade without formatting. I also tick disable verity and verification across every flash. is it fine to do ?
all went good. thanks
I use flash on both slots for dirty upgrade without formatting. I also tick disable verity and verification across every flash. is it fine to do ?
I could not flash the latest image to my P7Pro. Always got this error:
The phone did not boot anymore. The only way to get it booting again was to use the website flasher from google
Code:
Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)The phone did not boot anymore. The only way to get it booting again was to use the website flasher from google
Similar threads
Top Liked Posts
-
4
If it ever comes up for you guys that a bootloop happens because of a Magisk module, there's also the option to running the adb command:adb wait-for-device shell magisk --remove-modulesso that it doesn't erase everything set up in Settings like it does in Safe Mode (supposedly from what I've read, haven't experienced it myself). You'll have to re-install all the modules, but for most people that's more preferable than re-initializing and setting up everything in Settings...
But I, too, am fascinated by the "Special Magisk" build!4
Some clarification about this.
For starters all the credit goes to @gecowa6967 (I just included it in PF), he's the one who came up withthis special build, and it's based of Magisk Canary 25203, although it's not very difficult to clone the Magisk repo and build it from any code base by merging his changes. You can read all about it here.
In any case, almost certainly the version won't matter as the use for this is just to get an opportunity to disable the modules.
adb wait-for-device shell magisk --remove-modulesdoes not always work when you are bootlooping, unless the device gets into adb mode briefly, which would allow the execution of the magisk command, it won't work, and a lot of times a bootloop never gets into adb mode.
Furthermore, even the combo button booting to safe mode does not always work, you can read it in the linked post, it's a timing issue / Magisk issue.
This is not a cure for all bootloops, if you are bootlooping due to a Magisk modules, then you can flash stock boot and be able to boot to system, as the module won't load.
And you can't disable Modules unless you're rooted (chicken and egg situation)
If this is the case, you can uninstall Magisk Manager, install the special version, flash a patch.
Now you are rooted but modules are not loading, and you should be able to disable module,, flash a normal patch and get going again.3
Stand alone Clock, Battery Icon Gone, etc. Mods - Thread starter: TulsadiverOn March 18, you had your P7P already on March release and rooted.
With Modules enabled.
So I don't follow what you tried to do.
The logs may show this but the phone doesn't. I disabled the modules via PF on my very first flash back on the 17th.
I don't see anywhere that you disabled modules, and tried to flash again? stock? why?
As the phone was in a boot loop if I flashed stock I could boot up, just no root. I have flashed probably around 6 or 7 times since then.
I know for a fact that Systemless Hosts and Universal SafetyNet Fix can be left enabled without causing issues, but I don't know anything about Tulsadriver.
It removes the battery icon.
So you flashed stock, and created a patch and tried to flash just the patched boot? Yes
Are you bootlooping after that or just the phone is in bootloader mode? Once I flash the patched boot i end up in a boot loop.
I don't see it in the logs.
You've paid attention to this note right? Yes, however I am not sure of the intent of this question, without further clarification of your intent I am not sure this answers your question the way you are asking.
Thanks for the above I hope I have clarified the points you are asking about.
Tulsadiver Mod may need updating for the March 2023 firmware update.3
You might believe you had all the modules disabled when your bootloops started, but the logs don't lie, they can't be there out of thin air.On March 18, you had your P7P already on March release and rooted.
With Modules enabled.
So I don't follow what you tried to do.
The logs may show this but the phone doesn't. I disabled the modules via PF on my very first flash back on the 17th.
I don't see anywhere that you disabled modules, and tried to flash again? stock? why?
As the phone was in a boot loop if I flashed stock I could boot up, just no root. I have flashed probably around 6 or 7 times since then.
I know for a fact that Systemless Hosts and Universal SafetyNet Fix can be left enabled without causing issues, but I don't know anything about Tulsadriver.
It removes the battery icon.
So you flashed stock, and created a patch and tried to flash just the patched boot? Yes
Are you bootlooping after that or just the phone is in bootloader mode? Once I flash the patched boot i end up in a boot loop.
I don't see it in the logs.
You've paid attention to this note right? Yes, however I am not sure of the intent of this question, without further clarification of your intent I am not sure this answers your question the way you are asking.
Thanks for the above I hope I have clarified the points you are asking about.
Yes I see earlier on March 18, your were on December release and had only 3 modules which you disabled
Code:Selected Device on 2023-02-18 08:58:46: Device ID: REDACTED Device Model: cheetah Device Active Slot: b Device Mode: adb Device is Rooted: True Device Build: TQ1A.221205.011 Device API Level: 33 Device Architecture: arm64-v8a Device Bootloader Version: cloudripper-1.0-9231809 Magisk Manager Version: Magisk Path: None Checked for Package: com.topjohnwu.magisk Magisk Version: 25.2:25200 Magisk Config SHA1: 1384d5ad7ee8ca37ad0de2b20ca44dd2a4d8bc0a Magisk Modules: Systemless Hosts enabled 1.0 Universal SafetyNet Fix enabled v2.4.0-MOD_1.2 Zygisk - LSPosed disabled v1.8.5 (6649)Code:Opening Magisk Modules Manager ... 2023-02-18 09:01:41 User Pressed Ok. Module: Systemless Hosts state has changed, DISABLING the module ... Disabling magisk module hosts ... Module: Universal SafetyNet Fix state has changed, DISABLING the module ... Disabling magisk module safetynet-fix ... Module: Zygisk - LSPosed state has not changed, Nothing to do. [Kept DISABLED]
And flashed February image. (first you did a dry run before flashing)
At, 9:19 you were rooted on February release
You had 5 modules, 3 of which enabled.
Code:Selected Device on 2023-03-18 09:19:36: Device ID: REDACTED Device Model: cheetah Device Active Slot: b Device Mode: adb Device is Rooted: True Device Build: TQ1A.230205.002 Device API Level: 33 Device Architecture: arm64-v8a Device Bootloader Version: cloudripper-1.0-9288096 Magisk Manager Version: Magisk Path: None Checked for Package: com.topjohnwu.magisk Magisk Version: 25.2:25200 Magisk Config SHA1: 5657f3ea760bb2201873f67c89d000ff1491ef4f Magisk Modules: AOSP Mods (Full version) disabled 2.6.0 Tulsadiver Remove Battery Icon enabled v1 Systemless Hosts enabled 1.0 Universal SafetyNet Fix enabled v2.4.0-MOD_1.2 Zygisk - LSPosed disabled v1.8.6 (6712)
You disabled the modules
And flashed March release.Code:Opening Magisk Modules Manager ... 2023-03-18 09:22:53 User Pressed Ok. Module: AOSP Mods (Full version) state has not changed, Nothing to do. [Kept DISABLED] Module: Tulsadiver Remove Battery Icon state has changed, DISABLING the module ... Disabling magisk module Tulsadiver_Mods_For_Removing_Battery ... debug: "C:\Users\REDACTED\Desktop\AndroidUpdate_March2023\platform-tools\adb.exe" -s REDACTED shell "su -c 'touch /data/adb/modules/Tulsadiver_Mods_For_Removing_Battery/disable'" Module: Systemless Hosts state has changed, DISABLING the module ... Disabling magisk module hosts ... debug: "C:\Users\REDACTED\Desktop\AndroidUpdate_March2023\platform-tools\adb.exe" -s REDACTED shell "su -c 'touch /data/adb/modules/hosts/disable'" Module: Universal SafetyNet Fix state has changed, DISABLING the module ... Disabling magisk module safetynet-fix ... debug: "C:\Users\REDACTED\Desktop\AndroidUpdate_March2023\platform-tools\adb.exe" -s REDACTED shell "su -c 'touch /data/adb/modules/safetynet-fix/disable'" Module: Zygisk - LSPosed state has not changed, Nothing to do. [Kept DISABLED]
And yes you ran into issues and the phone was in recovery mode and then bootloader mode, but you eventually got it working rooted on March release at 9:57 with 3 modules enabled.
Code:Selected Device on 2023-03-18 09:57:33: Device ID: REDACTED Device Model: cheetah Device Active Slot: b Device Mode: adb Device is Rooted: True Device Build: TQ2A.230305.008.C1 Device API Level: 33 Device Architecture: arm64-v8a Device Bootloader Version: cloudripper-1.0-9618366 Magisk Manager Version: Magisk Path: /data/app/~~tskLuhNaN-GZpri7UAu57w==/com.topjohnwu.magisk-KsKj7DnmAFYjEc12NvGP4g==/base.apk Checked for Package: com.topjohnwu.magisk Magisk Version: 25.2:25200 Magisk Config SHA1: 4d938d3c7bab8b0ca7accccef2aa07eefd20602d Magisk Modules: AOSP Mods (Full version) disabled 2.6.0 Tulsadiver Remove Battery Icon enabled v1 Systemless Hosts enabled 1.0 Universal SafetyNet Fix enabled v2.4.0-MOD_1.2 Zygisk - LSPosed disabled v1.8.6 (6712)
But you kept on flashing again, I don't understand why
Code:============================================================================== 2023-03-18 09:58:28 PixelFlasher 4.8.1.0 Flashing Phone ============================================================================== Android Platform Tools Version: 33.0.3-8952118
You tried more flashing, you even loaded Raven image (not sure why)
and again you were in good state at 10:30
Code:Selected Device on 2023-03-18 10:30:19: Device ID: REDACTED Device Model: cheetah Device Active Slot: b Device Mode: adb Device is Rooted: True Device Build: TQ2A.230305.008.C1 Device API Level: 33 Device Architecture: arm64-v8a Device Bootloader Version: cloudripper-1.0-9618366 Magisk Manager Version: Magisk Path: None Checked for Package: com.topjohnwu.magisk Magisk Version: 25.2:25200 Magisk Config SHA1: 4d938d3c7bab8b0ca7accccef2aa07eefd20602d Magisk Modules: AOSP Mods (Full version) disabled 2.6.0 Tulsadiver Remove Battery Icon enabled v1 Systemless Hosts enabled 1.0 Universal SafetyNet Fix enabled v2.4.0-MOD_1.2 Zygisk - LSPosed disabled v1.8.6 (6712)
And again at 10:34
Code:Selected Device on 2023-03-18 10:34:20: Device ID: REDACTED Device Model: cheetah Device Active Slot: b Device Mode: adb Device is Rooted: True Device Build: TQ2A.230305.008.C1 Device API Level: 33 Device Architecture: arm64-v8a Device Bootloader Version: cloudripper-1.0-9618366 Magisk Manager Version: 25.2:25200 Magisk Path: /data/app/~~rSGL9RijF_SWcyOpJ_655w==/com.topjohnwu.magisk-YM6wK9dkpKoVR4WDuGf_qg==/base.apk Checked for Package: com.topjohnwu.magisk Magisk Version: 25.2:25200 Magisk Config SHA1: 4d938d3c7bab8b0ca7accccef2aa07eefd20602d Magisk Modules: AOSP Mods (Full version) disabled 2.6.0 Tulsadiver Remove Battery Icon enabled v1 Systemless Hosts enabled 1.0 Universal SafetyNet Fix enabled v2.4.0-MOD_1.2 Zygisk - LSPosed disabled v1.8.6 (6712)
Tell me, are you flashing multiple phones?
Because this cycle of being in good state and then flashing again kept on going.
Code:============================================================================== 2023-03-18 10:36:46 PixelFlasher 4.8.1.0 Flashing Phone ============================================================================== Android Platform Tools Version: 33.0.3-8952118 2023-03-18 10:36:46 Flashing device REDACTED ...Code:Selected Device on 2023-03-18 11:00:00: Device ID: REDACTED Device Model: cheetah Device Active Slot: b Device Mode: adb Device is Rooted: True Device Build: TQ2A.230305.008.C1 Device API Level: 33 Device Architecture: arm64-v8a Device Bootloader Version: cloudripper-1.0-9618366 Magisk Manager Version: 25.2:25200 Magisk Path: /data/app/~~rSGL9RijF_SWcyOpJ_655w==/com.topjohnwu.magisk-YM6wK9dkpKoVR4WDuGf_qg==/base.apk Checked for Package: com.topjohnwu.magisk Magisk Version: 25.2:25200 Magisk Config SHA1: 4d938d3c7bab8b0ca7accccef2aa07eefd20602d Magisk Modules: AOSP Mods (Full version) disabled 2.6.0 Tulsadiver Remove Battery Icon enabled v1 Systemless Hosts enabled 1.0 Universal SafetyNet Fix enabled v2.4.0-MOD_1.2 Zygisk - LSPosed disabled v1.8.6 (6712)
This was the last time your phone was rooted and in good state, and had 3 modules enabled.
But then you flashed again stock (SHA1: 4d938d3c7bab8b0ca7accccef2aa07eefd20602d)
Code:============================================================================== 2023-03-18 11:01:18 PixelFlasher 4.8.1.0 Flashing Phone ==============================================================================
Which booted to an unrooted state (as expected)
Code:Selected Device on 2023-03-18 11:08:08: Device ID: REDACTED Device Model: cheetah Device Active Slot: b Device Mode: adb Device is Rooted: False Device Build: TQ2A.230305.008.C1 Device API Level: 33 Device Architecture: arm64-v8a Device Bootloader Version: cloudripper-1.0-9618366 Magisk Manager Version: Magisk Path: None Checked for Package: com.topjohnwu.magisk
And finally this today
Which basically an attempt to flash a patched image (
730259795e63e29e940e851f309a9f7761cca8da)
, and then another attempt to patch stock image.
Probably because you are bootlooping, but please realize that the last state before your flashed stock, was a rooted phone on March release with 3 active modules.
Unless of course these are logs from different devices..
It's not uncommon to think that the phone is in a particular state (example modules disabled) but it actually is not, it happens to all of us, just peruse the thread and see the mistakes we make, myself included.
to recover from a bootloop caused by Magisk modules you can do the following.
Unhide + Uninstall Magisk Manager
Click on Magisk installer button and choose the special Magisk
You can read the notes
and follow the steps.
When you create a patch with this special Magisk, you get root, but modules will not be loaded.
This gives you a chance to disable the modules reboot and then apply the normal Magisk patch
Good luck.2
First, Boot Safe Mode on your phone. After, Safe Mode boots up, reboot.
Second, repatch the March 2023 init_boot.img.
Third, flash the NEW repatch March 2023 init_boot.img.
Do you have root?
If yes, install your Magisk modules individually and reboot after each module.
If a module does not install or work, that module needs updating. -
11New Release:
Mar 14, 2023 v4.8.1 release
- #47 Feature request: Added partition manager - Allows to erase partitions, and / or dump / backup partitions to PC.
- Added more visual troubleshooting event flows.
- Added warning message for when Android platform tools versions 34.0.0 and 34.0.1 are used.
- Improved support.zip redactions.
- Added Support.Zip generator button on the Main screen.
- APK Install option can now set the ownership to Play Store Market (useful for Android Auto)
- Check and warn the user when Magisk Canary versions 25207, 25208, 25209 and 25210 are being used.
- Bug fixes and other improvements.
7
For anyone else looking for the latestadbthat actually works, here are the official links to adb/fastboot 33.0.3:
https://dl.google.com/android/repository/platform-tools_r33.0.3-windows.zip - Windows
https://dl.google.com/android/repository/platform-tools_r33.0.3-darwin.zip - Mac
https://dl.google.com/android/repository/platform-tools_r33.0.3-linux.zip - Linux
Google doesn't keep the links to previous versions of adb on the platform-tools page.6
@badabing2003 is going to ask you to pull a log and post it here. May as well get a head start and do that so he can see where the issue is6New Release:
Mar 14, 2023 v4.8.1 release
- #47 Feature request: Added partition manager - Allows to erase partitions, and / or dump / backup partitions to PC.
- Added more visual troubleshooting event flows.
- Added warning message for when Android platform tools versions 34.0.0 and 34.0.1 are used.
- Improved support.zip redactions.
- Added Support.Zip generator button on the Main screen.
- APK Install option can now set the ownership to Play Store Market (useful for Android Auto)
- Check and warn the user when Magisk Canary versions 25207, 25208, 25209 and 25210 are being used.
- Bug fixes and other improvements.
-
48
This is the support thread of PixelFlasher for Google Pixel 7 Pro
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 manual steps) 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 (or init_boot.img for Pixel 7 / 7 Pro).
- 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 or patched image.
- Flash just the boot / init_boot image.
- Choose to keep data or wipe data while flashing.
- Ability to flash even if multiple devices are connected to the computer.
- Option to flash to inactive slot.
- Display information about the phone.
- ID
- Hardware model.
- Device architecture.
- 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.
- Active slot.
- Android OS API version.
- Convenient quick links to download Android platform tools or device firmware.
- Magisk Manager installation UI, screenshot. Supported versions:
- stable (official)
- beta (official)
- canary (official)
- debug (official)
- alpha
- delta
- special build that disables modules, used to recover from bootloops due to bad module(s) when safe mode does not work.
- Magisk Backup Manager, screenshot.
- List all Magisk backups currently on the device.
- Highlight the one that is backup of the current installed version.
- Delete backups.
- Manually add backup from PC.
- Auto Backup: PixelFlasher figures out what needs to be backed up, and if it finds it on the PC, it creates the backup.
- 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 (an app) 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.
- Package (Application) Manager, screenshot:
- Disable (Freeze)
- Enable
- Uninstall
- Install APK
- Download APK
- Multi-Select
- Show Package Details.
- 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).
For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.
Troubleshooting:
- See this post.
- Generate Sanitized support.zip file (File Menu) and submit that with your report.
28New Release:
Feb 05, 2023 v4.7.0 release
- Added Magisk Backup Manager:
- List all Magisk backups currently on the device.
- Highlight the one that is backup of the current installed version.
- Delete backups.
- Manually add backup from PC.
- Auto Backup: PixelFlasher figures out what needs to be backed up, and if it finds it on the PC, it creates the backup.
- Added Reset on Magisk Manager package name setting to reset to default: com.topjohnwu.magisk
- Linux / Mac build.sh now switches to the PixelFlasher folder if it is run from elsewhere.
- Magisk installer improvements:
- When installing Magisk Alpha or Delta, PixelFlasher updates the configuration to match the package name to the respective Magisk package.
- Magisk installer window displays the package name.
- You can now copy to clipboard, the download URL and package ID.
- Magisk Manager columns are now wider for better readability.
- Package Manager improvements:
- Added Search / Filter option.
- Show count of filtered packages.
- Application Name (label column).
- "Get Application Names" Button to resolve all package application names. This is a slow process, hence PixelFlasher caches them.
- Button to download (pull) APKs from the device. (Multiple downloads in one shot is also supported).
- Other under the hood improvements.
- When selecting a firmware or ROM file, sha256 is printed to console and displayed on hover, to validate if it matches the published sha256.
- More verbose logging that helps with troubleshooting.
- Double click on "ADB Connected Devices" to invoke adb kill-server which is handy at times, specially when dealing with Wifi ADB.
- Moved existing links under Help Menu | Links, and added few more handy links.
- Added timestamp to support.zip filename.
- On request, spinning cursor with text "Please be patient ..." is now displayed in red.
- Flashing to inactive slot is now in basic configuration instead of advanced configuration.
- Preparation work for version 5.0 DB improvements.
14New Release:
Feb 12, 2023 v4.8.0 release
- #50 Support for Android 14 Developer Preview for Pixel 7 and Pixel 7 Pro
- #48 Do not allow patching with hidden Magisk (stub) and adb shell not granted root rights.
- Block using Android Platform Tools version 34.0.0 and display a warning because it has known issues
- Disable Magisk Backup Manager button if root access to adb shell is not granted.
- Button to Open adb shell connected to the selected device.
- Work in Progress: Generate graphical activity log to visualize the activity and speed up troubleshooting.
14New Release:
Nov 09, 2022 v4.4.0 release
- New feature: Font and Font size should be configurable by the user #33
- New feature: Added WiFi-ADB connect / disconnect button. Left click to connect, Right click to disconnect.
Handy to access a device remotely.
Note: This only works in adb mode, so no fastboot or flashing features work for remote devices, but for patching / installing apks, managing Magisk modules it works well (basically anything that is done in adb).
I personally use this to test patching on remote devices, and also use it to access / install apps to my watch. - Ground work for future features: Get installed Package list, and list which are disabled, enable / disable / uninstall apps. (Will be available in future release).
- Move Flash Option Flash to inactive slot to Basic mode from Advanced mode..
- Minor UI Improvements
- If Magisk does not create a backup attempt to trigger Magisk to create one.
- Update readme to include Pixel 7 / 7P specific info.
13Pre-Release:
Oct 13, 2022 v4.2.0 pre-release
- Support for Pixel 7, 7p (init_boot extraction and patching / flashing).
- Added Pixel 7 / 7p partitions flashing options to custom flash.
- Improved patching process using boot_patch, add more patch file validations.
- Check for Magisk backup and trigger Magisk to backup if missing.
- Add more logging messages for troubleshooting.
- Code optimization / improvements.
- Bug Fix #28 Error when opening download link without a device selected.
- Added set_version script to easily set the product version.
- Print path of the selected boot to console, for easy copy / paste.
