Thanks for that. Safe mode only disables modules instead of removing them, and it doesn't mess up with settings in my case.
Special Magisk is a very good alternative.
Themes / Apps / Mods 📳🔥PixelFlasher for Google Pixel 7 Pro Support Thread.
- Thread starter badabing2003
- Start date
Special Magisk is a very good alternative.
interesting...I'll keep it in mind...I just read other users talking about how running safe mode erases the settings or something...or else the praises of that adb command wouldn't be prevalent...
EDIT: quick Google search states that some homescreen shortcuts might disappear and all non-Google login will have to be signed back in...or something...
Widgets do reset, yes, but I have them saved already within the respective apps (Elixir, Chronus, Digital Clock, etc). So whenever safe mode is triggered, it's the matter of a single click on the hollow widget to restore it from the saved settings.
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-modules does 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.
I am fascinated by the quoted post. I hate to pester you about it, but in the aspiration of simple better knowledge on the subject matter, what is this linked post? The link in the quoted post seems to be gecowa6967's post explaining how he came to creating the modified Magisk...
Sorry if it's totally going over my head and I'm totally missing something obvious...
Is there a way (another) to Uninstall Magisk Manager if you've hidden Magisk but forgotten the app it was renamed to...?
HipKat
Recognized Contributor
Not sure what you're trying to grasp, I linked the post so that you can see why it was needed and how it was addressed.
I mentioned that you can do the same with any Magisk codebase, but if you are asking to learn how you can build your own Magisk from Github, there are posts about that, basically you'd have to clone the repo, modify/adjust the actions and obviously make the necessary code changes you want to build from, but that's not the point of my above post.
Yes you can know a hidden Magisk's package name.
Install TB Checker from play store and it would tell you.
Yeah...sorry for the confusion and lack of clarification...i, myself, wouldn't just suddenly forget what i renamed Magisk when hiding it, but apparently another member here seemed to have lost it somehow and I'm trying to walk them through uninstalling it. That's why I couldn't be clearer in my original post asking...
I simply remembered it (unhiding and uninstalling magisk) here recently so I thought I'd shoot a shot and ask here...and you came through! So thank you!
UPDATE: just checked it, and I can't seem to find if/where the app shows what the Magisk Manager app is renamed as....
Last edited:
HipKat
Recognized Contributor
You don't see an app in your app drawer that doesn't seem right?? I just name mine Settings1, fwiw.
yeah...it's kinda confusing and the member hasn't responded so...
FWIW, the member is on a Pixel 3, so I couldn't remember much of how Android Pie or Q worked, but IIRC, you couldn't necessarily hold down on an app (in the app drawer or homescreen) and click App Info like you can today -- you had to go into the Settings and App section or something to get into an app info. Harder still if the member doesn't remember the app name...
But the member was rather confusing as the member stated that it would force close when attempting to open -- so how could you not know the app name it was renamed as?!?!
Hi guys, can I get some help please?
I have a 7 pro that is/was stucked on google logo. Phone is entering fastboot mode normally.
When I tried to flash it with flasher first few steps went fine, but then flasher froze and I got whole bunch of messages that the archive doesn't contain all kind of .sig files etc.
Unfortunately I don't know what caused this problem, I was guessing It won't be a problem flashing it since it goes to fastboot mode fine.
Here is the log if that can help.
Tnx in advance.
I have a 7 pro that is/was stucked on google logo. Phone is entering fastboot mode normally.
When I tried to flash it with flasher first few steps went fine, but then flasher froze and I got whole bunch of messages that the archive doesn't contain all kind of .sig files etc.
Unfortunately I don't know what caused this problem, I was guessing It won't be a problem flashing it since it goes to fastboot mode fine.
Here is the log if that can help.
Tnx in advance.
Looks like a communication issue.
Try another cable
Try another usb port (preferably usb2)
Make sure you don't touch the cable, phone during flashing.
Try flashing again, if it fails, provide a support file.
It looked liked that to me as well. I don't have a type c port on my laptop, waiting a friend to bring me the adapter. I was using my oneplus cable.
Are there some things that I have to pay attention to regarding versions of boot and firmwares?
Since I don't know what was done to cause this problem I am not sure if I can flash older firmwares or not. I have downloaded november firmware btw.
Tnx one more time.
Are there some things that I have to pay attention to regarding versions of boot and firmwares?
Since I don't know what was done to cause this problem I am not sure if I can flash older firmwares or not. I have downloaded november firmware btw.
Tnx one more time.
Typically you don't need to flash older firmware,
You're using a good version of Android Platform tools
But without full logs, I don't know other details like Magisk version, modules used, your existing firmware, what you selected as boot image ...
Thanks for creating this most useful tool! The first round of flashing went flawless.
Regarding the correct procedure to flash to the inactive slot for monthly updates. Is activating the option enough or does the user have to manually switch the active slot at some point? In other words, can flashing to inactive slot be left activated for each update and PixelFlasher will do the rest?
Regarding the correct procedure to flash to the inactive slot for monthly updates. Is activating the option enough or does the user have to manually switch the active slot at some point? In other words, can flashing to inactive slot be left activated for each update and PixelFlasher will do the rest?
HipKat
Recognized Contributor
The default is to flash to the inactive slot. You can change it to, however you wish, but most of us just let it flash to the inactive slot each month.
Update: manage to fix it after several tries. Not touching phone while in fastbootd mode helped 
Tnx guys for such awesome tool. Keep up the good work.
Tnx guys for such awesome tool. Keep up the good work.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
21New Release:
June 01, 2023 v5.2.0.0 release
- Update build workflows
- Add payload_dumper functionality to PixelFlasher to handle OTA files, thanks to vm03 for sharing source code.
- Added rules engine code to better / easier management of the UI widgets enabling / disabling.
- Auto detect Pixel OTA image and extract boot / init_boot / vbmeta for patching and flashing.
- Add Full OTA mode, which flashes full OTA image, while optionally retaining root, and best of all, for A/B devices, both slots are bootable, you can even have one rooted and one not.
15New Release:
May 19, 2023 v5.0.0.1 release
- #75 Bug fix, when device is in bootloader, type error.
- #74 Added Support for Pixel 7a (lynx)
- Configuration option to define the file manager to use on Linux (default: Nautilus)
- Configuration option to define the terminal emulator to use on Linux (default: gnome-terminal).
- Support for additional types of Factory / ROM files.
- Checksum validation of firmware / ROM files (if part of the checksum is in the name, otherwise just display)
- New advanced option, ability to choose the patching method (with recommendations).
- Added Recovery Image patching option.
- Advanced option to enable the use of busybox shell (default off).
- Auto detect firmware / rom with init_boot and use init_boot for creating patches, this way future firmware don't have to be manually added to PixelFlasher.
- Auto detect devices with init_boot and use init_boot for flashing, this way future devices don't have to be manually added to PixelFlasher.
- Auto-popup the detected devices dropdown after a scan, to make it obvious to select that next. (Thanks @pndwal for the idea)
- Show SHA-256 of adb and fastboot binaries, as Google keeps on messing up Android Platform-tools, it's necessary to whitelist / blacklist specific binaries.
- #66, when checking the patched files internal SHA1, provide a confidence rating.
- Check, valdiate and warn if necessary when flashing an image patched with Magisk Zygote64_32, as there are wipe implications, provide links to documentation.
- Added fastbootd testing to Dry Run.
- Added Github actions to build all the targets on Github.
- Code refactoring, bug fixes and improvements
14New Release:
June 06, 2003 v5.3.0.0 release
- Added Github Action build on Windows 2019 with Python 3.8 to support Windows 7.
- PixelFlasher now supports loading and processing Samsung Firmware (at least my Samsung's
), it would extract AP, BL, CSC, Home_CSC ... and then extract boot.img.lz4 from AP and unpack the lz4.
When creating a patch from the set boot.img, PixelFlasher will also create boot.tar to be flashed as AP to retain root.
If there was a way to pre-load odin with the extracted files, flashing could also be automated.
I know, what does PixelFlasher have anything to do with Samsung firmware? I added it for my own use.
10New Release:
May 25, 2023 v5.1.0.0 release
- Support for Android platform tools version 34.0.3, and automatic setting of ANDROID_PRODUCT_OUT environment to workaround a regression introduced in version 34.0.3
- Temp workaround to avoid selecting root method patching when Magisk Delta is detected.
- Nicer looking / clearer manual patching dialog.
- When a Pixel device is selected, PixelFlasher now displays additional information about the device's support.
Things like: Device name, version end date, security update end date, Android version, name, codename, release date, end date. - Boot image list box now displays the applied PixelFlasher patch method.
- Auto-resize boot image list box columns for better readability.
- Precautionary cleanup up of leftover files on the phone in case root detection software keys on presence of such files.
- #77 added attrict3 to requirements.txt in case it helps with certain builds (it shouldn't be needed).
- Bug fixes and improvements.
10Update:
June 03, 2003 v5.2.0.2 release
- #76 Get a better build with Github action to support more Linux based platforms (no functionality changes).
-
55
This is the support thread of PixelFlasher
(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).
Note: This thread is meant for issues and problems faced in Google Pixel 7 Pro devices, generic issues that are device agnostic should be discussed in the main thread.
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:
If you need support or assistance, the best way to get is by generating a support file from within PixelFlasher.
You can hit that big Support button on the main screen, or select it from the Help menu.
The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.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.
25New Release:
Apr 10, 2023 v4.8.2 release
- Include additional Magisk versions in the check to display a warning dialog when the user has installed one of the known versions to have issues.
- Display USNF related flag values when selecting a device.
- Check the downloaded Google firmware checksum to match the one in the filename and warn if it does not.
- Link to download Google USB Driver is added in the help menu.
- Added more visual troubleshooting event flows.
- Install APK now defaults to Non Market.
- Added Install APK cancel option.
- You can now select an app in package manager and right click to launch it on the phone.
- Minor bug fixes and other improvements.
21New Release:
June 01, 2023 v5.2.0.0 release
- Update build workflows
- Add payload_dumper functionality to PixelFlasher to handle OTA files, thanks to vm03 for sharing source code.
- Added rules engine code to better / easier management of the UI widgets enabling / disabling.
- Auto detect Pixel OTA image and extract boot / init_boot / vbmeta for patching and flashing.
- Add Full OTA mode, which flashes full OTA image, while optionally retaining root, and best of all, for A/B devices, both slots are bootable, you can even have one rooted and one not.
16New Release:
Apr 30, 2023 v4.10.0 release
- Added no reboot option, with this option selected, after flashing is completed, the phone will not reboot to system, giving a chance to take other actions before reboot.
- Added built-in file editor, you can now edit the flash script before running, in case you want to customize it (needless to say, should only be used if you know what you're doing)
- Added a button to open an explorer in working directory, useful for people who want full control, perform manual actions by following guides, but using PixelFlasher to do the prep work.
- Made the Firmware and Rom Process buttons, full with text. It wasn't obvious for some.
- Detect and handle Magisk Zygote64_32 automatically, thanks to @Namelesswonder for adding the necessary marker.
- Added Magisk Backup Manager:
