27
PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phon...
source link: https://forum.xda-developers.com/t/pixelflasher-a-gui-tool-for-flashing-updating-rooting-managing-pixel-phones.4415453/page-12#post-87168183
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.
badabing2003
Senior Member
Sep 17, 2012
I wouldn't be offended at all, the more options you give a person, the more power to them.I think I already know the answer to this, but how offended would you be if I included a link to this thread in my guides? You've done a fantastic job of streamlining the factory image update process, and because your tool allows flashing custom boot images (as well as patching the stock boot image) it's simpler than flashing everything via ADB, while being more flexible than the Android Flash Tool.
Go ahead, I actually encourage it, I would still mention that learning the manual steps gives them power to understand the process, and if they run into issues with a tool, they can get out of trouble because they know the manual steps.
Of course we would both be around to help them out whichever way they choose to root/patch/update.
Reactions: Thebear j koss, elong7681 and V0latyle
Thank you, it worked like a charm in my MacBook. 1st time using it, and it was perfect! ;-)
Reactions: Thebear j koss and badabing2003
Thank you for this excellent piece of cake! I have used once in Win10 OS, and also in Ubuntu 22.04 in my desktop pc (I used the Kali version).
Just a "nice to have", perhaps it can useful, as in my case the Ubuntu partition is close to be out of space, I wonder if you might consider a setting to set elsewhere the folder where the patched rom, and any temp files are generated.
Just a "nice to have", perhaps it can useful, as in my case the Ubuntu partition is close to be out of space, I wonder if you might consider a setting to set elsewhere the folder where the patched rom, and any temp files are generated.
Reactions: badabing2003
badabing2003
Senior Member
Sep 17, 2012
Thank you for this excellent piece of cake! I have used once in Win10 OS, and also in Ubuntu 22.04 in my desktop pc (I used the Kali version).
Just a "nice to have", perhaps it can useful, as in my case the Ubuntu partition is close to be out of space, I wonder if you might consider a setting to set elsewhere the folder where the patched rom, and any temp files are generated.
Linux is great, just create a directory wherever you want and then make a symbolic link to it, I haven't tried it but am sure it would work, if it does not, I'll add a feature.
Reactions: statustray and sronweb
I've added a section on PixelFlasher to all my guides. Thank you for your hard work!
Reactions: Thebear j koss, elong7681 and badabing2003
A fantastic tool. Updated and kept root in 1 click in 211 seconds to be precise. Thank you.
badabing2003
Senior Member
Sep 17, 2012
New release:
July 18, 2022 v3.4.0 release
July 18, 2022 v3.4.0 release
- Improvements to the boot extraction / categorization.
- Live boot option directly from the selected boot.img UI, even though it was possible to live boot previously through the advanced menu, it is now super easy to select a boot.img (patched or otherwise) and Live boot to that image with a click of a button.
- Added warning message in the splash screen and the help about menu, to inform users not to fall for opportunists who are claiming to be the developer of PixelFlasher with a donate button next to the download link. Reminder to all, this program will always be free, ad free, donation free; you should not be solicited for any form of payment.
Reactions: TTcell, Homeboy76 and mko000
I decided to give PixelFlasher (v3.4.0.0) a test drive today and ran into a Magisk version issue.
At this point, I'm not confident that it worked correctly, and will go back to doing it manually.
Please advise.
Thank you.
.:Terra
- Updated Magisk 24.3 => 25.1 (current rooted kernel is 24.3)
- Rebooted phone and verified Magisk is version 25.1 (kernel still 24.3)
- Started PixelFlasher
- Selected: sq3a.220705.003-factory-1c48ad3e.zip
- Went to patch with Magisk
- Returns a patched boot.img stating it is: 24.3:MAGISK (24300)
At this point, I'm not confident that it worked correctly, and will go back to doing it manually.
Please advise.
Thank you.
.:Terra
badabing2003
Senior Member
Sep 17, 2012
I decided to give PixelFlasher (v3.4.0.0) a test drive today and ran into a Magisk version issue.Shouldn't PixelFlasher gracefully handle a Magisk version upgrade and patch to 25.1 instead?
- Updated Magisk 24.3 => 25.1 (current rooted kernel is 24.3)
- Rebooted phone and verified Magisk is version 25.1 (kernel still 24.3)
- Started PixelFlasher
- Selected: sq3a.220705.003-factory-1c48ad3e.zip
- Went to patch with Magisk
- Returns a patched boot.img stating it is: 24.3:MAGISK (24300)
At this point, I'm not confident that it worked correctly, and will go back to doing it manually.
Please advise.
Thank you.
.:Terra
This is purely Magisk.
Upgrading Magisk is not part of PixelFlasher (at least not yet), and possibly I'll leave that outside of this program, as there are many parameters and permutations of Magisk upgrade process, and you can read all about it and potential caveats in the Magisk General thread.
Magisk is two parts, the manager (which is the application you run, the UI) and the Kernel (which provides the root functionality), you can have one without the other or each at different versions.
You just installed the manager, but your Kernel was still at 24.3.
PixelFlasher uses the Kernel component to patch the boot.img (if it detects its presence) otherwise it will merely launch the manager and guide you in the UI to manually patch the boot.img.
Because a kernel was found, it just used it as it is all automatic at that point.
I hope that clarifies the issue.
Top Liked Posts
-
A fantastic tool. Updated and kept root in 1 click in 211 seconds to be precise. Thank you.I've added a section on PixelFlasher to all my guides. Thank you for your hard work!
I wouldn't be offended at all, the more options you give a person, the more power to them.I think I already know the answer to this, but how offended would you be if I included a link to this thread in my guides? You've done a fantastic job of streamlining the factory image update process, and because your tool allows flashing custom boot images (as well as patching the stock boot image) it's simpler than flashing everything via ADB, while being more flexible than the Android Flash Tool.
Go ahead, I actually encourage it, I would still mention that learning the manual steps gives them power to understand the process, and if they run into issues with a tool, they can get out of trouble because they know the manual steps.
Of course we would both be around to help them out whichever way they choose to root/patch/update.So, I've finally decided to try this. Pretty slick. Just a couple suggestions:- Add the ability to select a previously patched boot image, then live boot it. Maybe a little redundant since your tool automatically patches the new boot image.
Happy to hear that you gave a shot.
If I understand you correctly, I believe what you want is already there, see if this does it.
First turn on advanced mode.
You can do that through the File Menu | Advanced Configuration and then select Enable Advanced Options.
The UI should change and you should see additional options.1- Once you create the patched boot.img, select it (highlight)
2- Choose Custom Flash
3- Select boot
4- Hit the Paste button, and it will paste the currently selected boot.img path
5- Select Live boot, or Flash, in your case I suppose you want Live Boot
Ignore the Flash both slots selection from my image, that is not necessary, I just had it on when taking the screenshot and didn't feel like taking another one
6- Hit the flash Pixel Phone and you should get what you want.
You don't see anything scrolling in the Console window (#7)? as it is flashing or patching, you should see the output reflected in the console, if you don't it could be a bug that I need to investigate.- Provide some sort of log readout so the user can see exactly what is happening, as well as the option to save the log file for troubleshooting and review. The program doesn't really tell you what it's doing while it's flashing the factory image, and while I noticed your warning to be patient, it would still be nice to be
Keep in mind that the console only refreshes if the line is complete, ie a newline is sent, there are some parts in the flash output (while extracting data) the output does not have a newline until it completes the extraction, not much I can do there, but that is only one line that should make you wait till it completes, each line should print and scroll.
Also you can turn on the verbose button for the console to get even more verbose logging, I think the app is very verbose to start with, and that options makes it even more verbose, I usually keep it on to see exactly what is happening.
Lastly, if you want to see current or previous logs.
Help menu | Open configuration Folder
Navigate to logs folder and you'd see all the logs.
You can also choose Create Sanitized support.zip from the Help menu.
This will zip up the logs and the configuration details, and redact (sanitize) all personal data (device id, user name ...) It helps with troubleshooting and making the program better.
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK