Database Develop

Magisk v17 Failed to Install

I attempted to go from Magisk v16 to Magisk v17 from the app, Install > Patch Boot Image File > Magisk-v17(1700).zip and I get the below .
I opened up Root Checker and it let me know that the device no longer has Root.
- Copying image to cache
- Device platform: arm64-v8a
- Existing zip found
- Extracting files
! Installation Failed
Magisk Log File
- Copying image to cache
- Device platform: arm64-v8a
- Existing zip found
- Extracting files
boot_patch.sh[73]: can't create /proc/self/fd/: Is a directory
MagiskBoot v17.0(17000) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
No boot image magic found!
boot_patch.sh[91]: can't create /proc/self/fd/: Is a directory
boot_patch.sh[91]: can't create /proc/self/fd/: Is a directory
! Installation failed
Device Stats
Nexus 6P
Lineage 15.1
TWRP - latest
Any help would be greatly appreciated.

monteie2016 said:
I attempted to go from Magisk v16 to Magisk v17 from the app, Install > Patch Boot Image File > Magisk-v17(1700).zip and I get the below .
I opened up Root Checker and it let me know that the device no longer has Root.
- Copying image to cache
- Device platform: arm64-v8a
- Existing zip found
- Extracting files
! Installation Failed
Magisk Log File
- Copying image to cache
- Device platform: arm64-v8a
- Existing zip found
- Extracting files
boot_patch.sh[73]: can't create /proc/self/fd/: Is a directory
MagiskBoot v17.0(17000) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
No boot image magic found!
boot_patch.sh[91]: can't create /proc/self/fd/: Is a directory
boot_patch.sh[91]: can't create /proc/self/fd/: Is a directory
! Installation failed
Device Stats
Nexus 6P
Lineage 15.1
TWRP - latest
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Happened with me also...i gues the only solution is you have to uninstall mafisk via magisk uninstaller and flash it once again via whatever recovery you are using...i am also using lineage os 15.1 but with RN4....

Happened to me as well. HTC u11, ViperU 1.8.0, Android 7.1.1, TWRP 3.2.2. Tried flashing it though TWRP got a bootloop. Had to revert back to my previous nan which luckily I made yesterday.

I attempted the same, now my galaxy s6 is in a boot loop

Look other posts in this section - you should flash latest uninstaller before Magisk v17 package. It seems that some residues from v16 prevent v17 from installing correctly.

^^^^^^^^^^

how to uninstall magisk completely without custom recoery

Hello Guys
I can not install Magisk v17.1
I delete it complete with the uninstaller
And then flashed again in TWRP, but dont work
Magisk icon is not visible and I can not manually install the Magisk Manager
Pls Help

edkmho said:
how to uninstall magisk completely without custom recoery
Click to expand...
Click to collapse
I had to reflash stock (OTA sideload version, in stock recovery) via adb sideload. Essential phone. Wifi is working now, didn't lose any data.

I'm also having the issue on my OnePlus 5T. I was running v16.0, and when I tried to flash the v17.1 zip in TWRP like usual, but it said zip signature verification failed. I flashed the Magisk uninstaller zip and tried again, but still had the same problem. I've lost root, but all my data is still intact and it never had boot issues.

After using uninstaller in recovery, restart into recovery to flash v17

aydinbahadir88 said:
And then flashed again in TWRP, but dont work
Magisk icon is not visible and I can not manually install the Magisk Manager
Click to expand...
Click to collapse
Do you update from 16.0? If Yes test following:
Download the seperate MagiskManager-v5.9.1.apk
Make sure that you adb is working, connect your phone to computer
Code:
adb devices
must show your phone, if not adb is not proper set
Code:
adb install MagiskManager-v5.9.1.apk
if you get a error message like
the sign with the installed apk has not matsched..aborted
Click to expand...
Click to collapse
the uninstaller not proper delete the old magisk manager
try
Code:
adb uninstall com.topjohnwu.magisk
the result must be an sucess
then again
Code:
adb install MagiskManager-v5.9.1.apk
result must also sucess
Reboot, voiala its done....
You see the Magisk Manager

Does anyone have a working solution?

1.download magisk 17.zip from inside magisk 16
2. uninstall magisk 16 (i do from inside, not twrp)
3. instal magisk 17.zip from twrp
4. open magisk 17 and get notification for downloaded magisk 17.apk
5. download and instal it,
tested by my phone
mi5 Lineage Os 15.1

How I recovered from this on a Pixel 2 XL
I'll chime in with my experience here, as it might save someone else a lot of time if they are at my skill level with this stuff (which is only moderate, I suppose, although I do always get things to work eventually!).
As of yesterday, I had a Pixel 2 XL, rooted with Magisk, and working great. This morning, during the middle of the night, Magisk innocently asks if I want to upgrade to a new version. I was very tired (in fact, I think I was sleeping when my phone buzzed to alert me of the upgrade message) and don't even know how I responded except that it was "yes" to the upgrade part. By the time I'd fully awakened, I had a phone that waw in a boot loop. I went back to sleep, figuring I'd have better luck looking at it after a little rest.
Getting out of the boot loop was easy: I just reinstalled the August 2018 factory image for the phone. However, getting Magisk reinstalled was an adventure. I saw posts that said I should run the Magisk uninstaller, but when I did it just said that Magisk was already uninstalled. And yet, whenever I tried to apply either v16.0 or v17.1, I got errors (error codes 1, 2, and 255 at different times).
Up until this event, I'd always upgraded Magisk by installing it via TWRP. However, that was not working, so I thought I needed to try patching the boot image, something I'd never done before. Because I'd never done it before, it took me a while to understand the steps, which are actually quite simple. This is where I'm hoping I might save someone some time. Basically, my fear was not knowing which file the "boot image" was. Seasoned Android veterans might get a chuckle out of this, and that's fine, but I was looking at the file in the factory image download and basically saw only two image files: bootloader-taimen-tmz20j.img and radio-taimen-g8998-00253-1805232234.img. I was trying to figure out if either of those could be the boot image, and they both seemed pretty big to be a boot image! Finally it dawned on me that the much larger file in the directory was a zip archive (named image-taimen-ppr1.180610.009.zip). I looked inside there, and sure enough, there was a rather small file named boot.img. I was pretty sure that was the "boot image" file!
Here's what I did after that, again just hoping to help anyone who finds themselves in the same predicament I was in: Magisk is broken, root isn't working, and I can't install any of the Magisk *.zip images via TWRP.
- First, I downloaded a copy of Magisk Manager: this version is named MagiskManager-v5.9.1.apk.
- Next, I ran a couple adb commands to send the Magisk Manager apk and the stock boot.img to my phone:
Code:
adb push MagiskManager-v5.9.1.apk /sdcard/Download
adb push boot.img /sdcard/Download
- Next, I installed /sdcard/Download/Magisk-Manager-v5.9.1.apk by nagivating to it (I use ES File Manager) and launching it from there.
- Next I opened Magisk Manager
- Magisk Manager detects that there is a newer version available and asks if I want to upgrade
- I said yes
- I told it that I wanted to patch a boot image
- I chose /sdcard/Download/boot.img as the "unpatched" (stock) boot image
- Magisk Manager churned away for maybe half a minute and then produced a new file called patched_boot.img, saved in the same directory as boot.img.
After that, all I had to do was run these commands:
Code:
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot reboot
As soon as the phone restarted, I opened Magisk Manager again and it verified that its upgrade was successful, and root began working for me again also.
Like I said, I hope this helps someone else. If not, it's probably good for me to just write it all out anyway.
Cheers,
Sky Captain

_sky.captain_ said:
I'll chime in with my experience here, as it might save someone else a lot of time if they are at my skill level with this stuff (which is only moderate, I suppose, although I do always get things to work eventually!).
As of yesterday, I had a Pixel 2 XL, rooted with Magisk, and working great. This morning, during the middle of the night, Magisk innocently asks if I want to upgrade to a new version. I was very tired (in fact, I think I was sleeping when my phone buzzed to alert me of the upgrade message) and don't even know how I responded except that it was "yes" to the upgrade part. By the time I'd fully awakened, I had a phone that waw in a boot loop. I went back to sleep, figuring I'd have better luck looking at it after a little rest.
Getting out of the boot loop was easy: I just reinstalled the August 2018 factory image for the phone. However, getting Magisk reinstalled was an adventure. I saw posts that said I should run the Magisk uninstaller, but when I did it just said that Magisk was already uninstalled. And yet, whenever I tried to apply either v16.0 or v17.1, I got errors (error codes 1, 2, and 255 at different times).
Up until this event, I'd always upgraded Magisk by installing it via TWRP. However, that was not working, so I thought I needed to try patching the boot image, something I'd never done before. Because I'd never done it before, it took me a while to understand the steps, which are actually quite simple. This is where I'm hoping I might save someone some time. Basically, my fear was not knowing which file the "boot image" was. Seasoned Android veterans might get a chuckle out of this, and that's fine, but I was looking at the file in the factory image download and basically saw only two image files: bootloader-taimen-tmz20j.img and radio-taimen-g8998-00253-1805232234.img. I was trying to figure out if either of those could be the boot imag, and they both seemed pretty big to be a boot image! Finally it dawned on me that the much larger file in the directory was a zip archive (named image-taimen-ppr1.180610.009.zip). I looked inside there, and sure enough, there was a rather small file named boot.img. I was pretty sure that was the "boot image" file!
Here's what I did after that, again just hoping to help anyone who finds themselves in the same predicament I was in: Magisk is broken, root isn't working, and I can't install any of the Magisk *.zip images via TWRP.
- First, I downloaded a copy of Magisk Manager: this version is named MagiskManager-v5.9.1.apk.
- Next, I ran a couple adb commands to send the Magisk Manager apk and the stock boot.img to my phone:
Code:
adb push MagiskManager-v5.9.1.apk /sdcard/Download
adb push boot.img /sdcard/Download
- Next, I installed /sdcard/Download/Magisk-Manager-v5.9.1.apk by nagivating to it (I use ES File Manager) and launching it from there.
- Next I opened Magisk Manager
- Magisk Manager detects that there is a newer version available and asks if I want to upgrade
- I said yes
- I told it that I wanted to patch a boot image
- I chose /sdcard/Download/ as the "unpatched" (stock) boot image
- Magisk Manager churned away for maybe half a minute and then produced a new file called patched_boot.img, saved in the same directory as boot.img.
After that, all I had to do was run these commands:
Code:
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot reboot
As soon as the phone restarted, I opened Magisk Manager again and it verified that its upgrade was successful, and root began working for me again also.
Like I said, I hope this helps someone else. If not, it's probably good for me to just write it all out anyway.
Cheers,
Sky Captain
Click to expand...
Click to collapse
I too have a Pixel 2XL but had a much easier upgrade experience. I downloaded the latest version of Magisk files (3 files: MagiskManager-v5.9.1.apk, Magisk-uninstaller-20180901, and Magisk-v17.1 from here https://www.xda-developers.com/magisk-v17-1-android-pie-a-b-support/) and put them on my phone.
Rebooted into recovery TWRP run the Magisk-uninstaller-2018090 file, then ran Magisk-v17.1 rebooted and all worked (thanks to ALL the developers out there!!!)
I'm running rooted Pie (standard google Pie) with Rootchecker, 4.4.153-FlashKernal-Wahoo-v3.06, Greenify, AdAway, and of course Magisk 17.1.
Hope this helps.

akohle said:
After using uninstaller in recovery, restart into recovery to flash v17
Click to expand...
Click to collapse
flashed uninstaller in recovery
flashed v17
rebooted
it worked

If patch boot image is getting failed in magisk latest version v17.1 then enable storage permission for magisk app manually in Device/OS setting. Now patch boot image again, It will get patched successfully.

I
pierro78 said:
flashed uninstaller in recovery
flashed v17
rebooted
it worked
Click to expand...
Click to collapse
OK...im a relative newbie here...first post actually....but Im a bit stuck in a fastboot boot loop
LG G5 tmobile running fulmics
I decided to try this exact process to get my root back by updating Magisk
booted into TWRP through ADB
flashed uninstaller using TWRP
(cleared cache/dalvik)
flashed v 17.1 (not 17) using TWRP
(cleared cache/dalvik)
rebooted
now i'm stuck in fastboot bootloop….can reboot from fastboot but nothing else
any advice would be appreciated!
update: I am able to get to TWRP using reboot command and holding power and volume down. flashed uninstaller wiped cache/dalvik...rebooted into TWRP long way and then installed 17....still fastboot at startup again

Art1mis said:
If patch boot image is getting failed in magisk latest version v17.1 then enable storage permission for magisk app manually in Device/OS setting. Now patch boot image again, It will get patched successfully.
Click to expand...
Click to collapse
many thanks for the tip!!
spent like an hour trying to figure out why my pixel 2 was failing to patch the boot image.
Allowed storage permissions, flashed the patched boot and now im rooted

[GUIDE] OTA updates with Magisk

If you have managed to root your phone with Magisk, getting updates after that for the stock ROM isn't always a smooth thing. Here are some steps to be successful with updates.
1. Open Magisk Manager and disable all installed modules by unchecking the circle for each.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please note that steps 2-4 can be done with the stock 1+ updater so long as it senses that you are rooted and offers to download a full rom. So a note about magisk hide which is used to hide root. Make sure you haven't managed to hide root for any process related to the 1+updater or it won't know you are rooted and will offer incremental updates.
2. Install Oxygen Updater (This app may become abandoned in 2019 requiring the use of the stock updater which is slower or manually downloading roms.) https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
3. Open the app, verify that your device is identified correctly. Open it's settings and set Update Method to "Full Update"
4. Check for an update and download it. Make sure you end up with a full 2GB ROM image not an incremental small one. It will be in the root of internal storage.
DO NOT use Oxygen Updater to update the phone (unless you have TWRP and that is for a different GUIDE)
5. Open the built in OnePlus updater: Settings - System - System Updates - Gear - Local Upgrade and select the newly downloaded update. TAKE NOTE while it is installing which slot it is installing too. It will say something like "inactive slot a". Remember this as it is the "new" slot.
6. After it has installed DO NOT reboot the phone or you will lose root. Open Magisk Manager and install Magisk, even though it says "installed". Select the option when it prompts for "after OTA". This will install magisk in the boot partition of the new slot.
7. Reboot and If all went well you shouldn't boot loop and you'll be running the new slot. If you want TWRP (optional), install the zip now from Magisk->Modules->+ (sign) then select the TWRP zip file and install it. Do NOT reboot. Then do a "Direct Install" of Magisk again, then reboot.
8. Open Magisk Manager and go to the downloads section and reinstall the modules you want to use. Do this from the Downloads screen or using the + button on the Modules screen. This will install them in the current slot.
DO NOT simply reenable the modules with the check mark or you will boot loop. Some modules aren't listed in Magisk and can't be automatically moved from slot to slot. If you installed one of those previously, you must reinstall it with the plus button manually from the modules tab.
You should be done now.
Oh no I'm boot looping: Don't panic.
1. Make sure you have adb/fastboot 1.4.3 or newer on a PC https://forum.xda-developers.com/showthread.php?t=2317790
2. Boot the phone into Bootloader/fastboot either through the recovery menu or VolDn + Pwr
3. If in step 5 above the inactive slot was "a", issue the command from a PC command prompt:
fastboot --set_active=b
or vice versa
fastboot --set_active=a
If you are not sure which to use try one or fastboot getvar current-slot
4. Then: fastboot reboot
This will allow the phone to boot into the last good ROM version. Now you figure out what went wrong.
Another option If your phone didn't retain root, you can stay in the unrooted slot. download a rooted boot image of your firmware version, place it in the your fastboot pc directory, reboot the phone to fastboot and issue the command: fastboot boot boot.img (or whatever the downloaded image is called.) this is a temporary root that is non destructive. Then do a direct install from Magisk manager even though it already says installed. That will permanently root your boot copy. Then install your modules.
Here is the 9.5.11 1917AA rooted boot image https://www.dropbox.com/s/6csxd9zaa4mihwk/boot_a_backup_2019-08-04_19-05-29.img?dl=0
If your phone looped right after flashing, you may not have disabled Magisk modules properly. You can still disable them from the good slot, swap active slots again using fastboot and see if it boots into the new ROM. If not, swap back to the good old slot again and start over flashing again from the beginning.
If you looped after reenabling your modules, it is possible you only enabled one but didn't install it into the new slot. Again swap back to the good slot and disable the modules. Swap back to the new slot and install the modules again even if Magisk thinks they are there.
If all else fails, you can stay in the good old slot until you sort things. If you are looping in both slots then something really went bad and you have to flash back a full ROM from fastboot. See this thread
https://buzzfire.de/xda/t3931424
Then root again using the rooted boot image above.
You may be able to boot into the old rooted slot and root the new slot with the ota option also.
If you have issues where stuff like Wifi doesn't work, then somewhere along the line or previously you flashed a (boot) image that didn't match the /system image in the slot you were working on. This error will persist in that slot every time you use that slot until it gets a fixed set of images.
Hope this helps!

I updated to 9.5.7 yesterday with following process, which was very simple (also used the same exact process to update to 9.5.6 last week):
Note: This assumes your device is already bootloader unlocked and has developer options enabled.
Download latest twrp.zip to your phone
Download latest magisk.zip to your phone
Download latest twrp.img to your pc
Allow oxygen updater to download/install OTA. It will say 'your device is rooted, a full image will be downloaded'. (If you're not already rooted, this process will still work)
After it completes the installation, do not select reboot. Instead, hold power button and press reboot to bootloader (make sure you enabled Advanced reboot in settings to see that option)
In fastboot and connected to pc, run from pc: fastboot flash boot twrp-3.3.1-3-guacamole.img (or whatever latest version is - you need to do this step because the OTA wipes out twrp if you already had it installed)
Reboot phone to twrp recovery
Flash install the twrp.zip you downloaded above
Flash install the magisk.zip you downloaded above
Reboot System
Done
Using this method, I haven't needed to change the slots at all, as the OOS updater takes care of that and the twrp/magisk flash installs each to both slots. This method preserves all data/settings/root (but I still do a twrp backup just prior to doing the update). I had tried the magisk install OTA to inactive slot option a few times but it never worked for me. This method also eliminates the need to download any patched boot images.

If you are on bootloop, just simply flash magisk_uninstaller.zip on twrp
boot into system > then flash magisk on twrp again.

Perfect manual and working great

gtelnet said:
I updated to 9.5.7 yesterday with following process, which was very simple (also used the same exact process to update to 9.5.6 last week):
Note: This assumes your device is already bootloader unlocked and has developer options enabled.
Download latest twrp.zip to your phone
Download latest magisk.zip to your phone
Download latest twrp.img to your pc
Allow oxygen updater to download/install OTA. It will say 'your device is rooted, a full image will be downloaded'. (If you're not already rooted, this process will still work)
After it completes the installation, do not select reboot. Instead, hold power button and press reboot to bootloader (make sure you enabled Advanced reboot in settings to see that option)
In fastboot and connected to pc, run from pc: fastboot flash boot twrp-3.3.1-3-guacamole.img (or whatever latest version is - you need to do this step because the OTA wipes out twrp if you already had it installed)
Reboot phone to twrp recovery
Flash install the twrp.zip you downloaded above
Flash install the magisk.zip you downloaded above
Reboot System
Done
Using this method, I haven't needed to change the slots at all, as the OOS updater takes care of that and the twrp/magisk flash installs each to both slots. This method preserves all data/settings/root (but I still do a twrp backup just prior to doing the update). I had tried the magisk install OTA to inactive slot option a few times but it never worked for me. This method also eliminates the need to download any patched boot images.
Click to expand...
Click to collapse
You Sir are the good damn man i have spent 3hrs trying to update to 9.5.9 cheers boss!!

Will this method work if I was a TMobile OnePlus 7pro which converted to international running 9.5.8 currently?

Yes if you are offered the aa rom in the updater

@larsdennert I guess you may well know about this:
https://forum.xda-developers.com/oneplus-7-pro/help/oxygen-updater-shutting-november-t3948339

I just start the update under settings, system, syst update
It found new update and tell me he need to download full ROM (I have rmagisk installed).
While it was downloading full ROM I uninstall magisk from magisk app.
After update finish before restart I installed magisk again (option after ota update) and restart.
Now I'm updated and with magisk installed
Inviato dal mio GM1913 utilizzando Tapatalk

SlyUK said:
@larsdennert I guess you may well know about this:
https://forum.xda-developers.com/oneplus-7-pro/help/oxygen-updater-shutting-november-t3948339
Click to expand...
Click to collapse
Yes I'm thinking, In the worst case it may be possible to use the stock updater as it senses root and downloads the full update now. Simply substitute the step where oxygen updater is used to download with the stock updater.
There may be a slightly longer delay before the stock updater offers an update as 1+ does it in waves. I have to hand it to 1+for even offering updates as most phones won't.

hi experts,
what and where to set or unset to make sure there is NO auto OTA update?
How do I control the update time on my op7p?
I'd like to avoid surprise of getting update in background that would / can remove root, magisk and etc that were manually added?
as example I use xXx over magisk and I's like to be prepared ahead of time to apply the OTA update
thanks for the education.

The 1+ updater has a setting to auto download updates or not. You can change it.

If we have TWRP installed could we get a guide for using the updater app?

kirschdog1 said:
If we have TWRP installed could we get a guide for using the updater app?
Click to expand...
Click to collapse
This is the method i use. Screenshot it from a thread here on XDA and unfortunately cannot remember the posters name to give credit. But it is the job!

kirschdog1 said:
If we have TWRP installed could we get a guide for using the updater app?
Click to expand...
Click to collapse
I used a method that didn't require uninstalling Magisk modules or even booting into recovery (unless you have issues):
1.) Download FULL OTA from 1+ updater (should be approximately 2gb)
2.) Disable all Magisk modules and substratum themes
3.) Install OTA manually via the system updater in Settings > System > System Updates > Gear in upper right > Local Upgrade **DON'T REBOOT!!!**
4.) Search for TWRP Retention Script in Magisk, install **DON'T REBOOT!!!**
5.) Re-install Magisk from the main page in Magisk Manager App (OTA Option) **REBOOT**
6.) Re-enable Magisk modules and any substratum themes **REBOOT**
If you get stuck in a bootloop due to a Magisk module causing issues (EdXposed did this to me) you can:
Boot Into Recovery (Volume Down + Power Button) > Advanced > File Manager > Navigate to data/adb/modules > Click module you want to disable / delete > Hit bottom right checkmark > Delete > Hit Home > Reboot System
Magisk modules I'm currently running in 9.5.10 with no issues:
- Google Dialer Framework
- Google Product Sans
- liboemcrypto disabler
- OnePlus Google Launcher
- Renovate Ice
- Substratum
- ViperFX
- xxxNoLimitsxxx

i.Design said:
I used a method that didn't require uninstalling Magisk modules or even booting into recovery (unless you have issues):
1.) Download FULL OTA from 1+ updater (should be approximately 2gb)
2.) Install OTA manually via the system updater in Settings > System > System Updates > Gear in upper right > Local Upgrade **DON'T REBOOT!!!**
3.) Disable all Magisk modules and substratum themes
4.) Search for TWRP Retention Script in Magisk, install **DON'T REBOOT!!!**
5.) Re-install Magisk from the main page in Magisk Manager App **REBOOT**
6.) Re-enable Magisk modules and any substratum themes **REBOOT**
If you get stuck in a bootloop due to a Magisk module causing issues (EdXposed did this to me) you can:
Boot Into Recovery (Volume Down + Power Button) > Advanced > File Manager > Navigate to data/adb/modules > Click module you want to disable / delete > Hit bottom right checkmark > Delete > Hit Home > Reboot System
Magisk modules I'm currently running in 9.5.10 with no issues:
- Google Dialer Framework
- Google Product Sans
- liboemcrypto disabler
- OnePlus Google Launcher
- Renovate Ice
- Substratum
- ViperFX
- xxxNoLimitsxxx
Click to expand...
Click to collapse
Question. How do you know it was edxposed module? I'm currently trying to track down. Why I'm still getting SOD after updating from 9.5.9 to 9.5.10

Pvt WhoOkid said:
Question. How do you know it was edxposed module? I'm currently trying to track down. Why I'm still getting SOD after updating from 9.5.9 to 9.5.10
Click to expand...
Click to collapse
I assumed it was and disabled it first, did a reboot and booted up fine. It was a good guess
Best bet would be to delete all modules and start from scratch if you're not sure. It depends what kinds of modules you run.
I had issues of bootloop where I would get past the unlocked message and boot up animation but then would freeze with my background showing only (no launcher, no status bar, etc).

i.Design said:
I assumed it was and disabled it first, did a reboot and booted up fine. It was a good guess
Best bet would be to delete all modules and start from scratch if you're not sure. It depends what kinds of modules you run.
Click to expand...
Click to collapse
Yeah back to the drawing broad for me. Luckily I don't run many modules. Just edXposed , xXx and Riru Core.

Pvt WhoOkid said:
Yeah back to the drawing broad for me. Luckily I don't run many modules. Just edXposed , xXx and Riru Core.
Click to expand...
Click to collapse
I was running Riru Core, edXposed and ended up dropping both, it wasn't worth the hassle for me since I run Renovate Ice and it does most of the tweaks I want from GravityBox (reason I was running Xposed).

Pvt WhoOkid said:
Yeah back to the drawing broad for me. Luckily I don't run many modules. Just edXposed , xXx and Riru Core.
Click to expand...
Click to collapse
Try disabling all the modules and see if you can boot into 9.5.10 slot. If it does, reinstall them (then reenable them)

Pixel 5 w/ Jan Update - Flash of patched boot.img = loop

Hi all,
I seem to be struggling with my usual process of getting root on my Pixel 5.
I installed the latest Canary build of the Magisk Manager and patched my base boot.img and then flashed it and the phones goes into an infinite loop. Only way to get out of it is to flash-all.bat (w/out the -w). Any ideas on why this process, which I've used even on my previous P2XL, is no longer working?
When I open the manager, it says my installed version is 8.0.4 (4770) and the latest version is 6d88d8ad (4770) (15) but I can't update.

I have the January release and the same magisk version, and my device boots fine. What steps did you do to patch the boot.img file and how did you flash the patched magisk_patched.img file?

Amd4life said:
I have the January release and the same magisk version, and my device boots fine. What steps did you do to patch the boot.img file and how did you flash the patched magisk_patched.img file?
Click to expand...
Click to collapse
This is the process I follow each month/followed for this update:
Download and extract FW
Edit flash-all.bat to remove the -w
Run flash-all.bat while at bootloader screen
Copy \redfin-rq1a.210105.003\boot.img to device
Open Magisk Manager Canary (latest) and click on "Install"
Select "Select and Patch a File"
Copy \download\magisk_patched_0eKAS.img to platform-tools folder on PC
At bootloader screen, run: fastboot flash boot magisk_patched_0eKAS.img
Reboot
I've been using that process for months, going back to my Pixel 2 XL and used that process (with different .img names obviously) last month even for the December update on this here Pixel 5.
Only way to get out of the loop is to re-run step 3.

IlyaKol said:
Hi all,
I seem to be struggling with my usual process of getting root on my Pixel 5.
I installed the latest Canary build of the Magisk Manager and patched my base boot.img and then flashed it and the phones goes into an infinite loop. Only way to get out of it is to flash-all.bat (w/out the -w). Any ideas on why this process, which I've used even on my previous P2XL, is no longer working?
When I open the manager, it says my installed version is 8.0.4 (4770) and the latest version is 6d88d8ad (4770) (15) but I can't update.
Click to expand...
Click to collapse
Have you tried using Magisk latest beta? I ended up using beta for January for whatever reason and had no issue. I'd upload my boot.img but I'm a Verizon user and not sure if it'll work for you. "magisk_patched_dnuD3.img"
Magisk v21.2 (21200)
Magisk Manager v8.0.4 (4768) (15)

andybones said:
Have you tried using Magisk latest beta? I ended up using beta for January for whatever reason and had no issue. I'd upload my boot.img but I'm a Verizon user and not sure if it'll work for you. "magisk_patched_dnuD3.img"
Magisk v21.2 (21200)
Magisk Manager v8.0.4 (4768) (15)
Click to expand...
Click to collapse
Let me give that a whirl in a bit.

IlyaKol said:
Let me give that a whirl in a bit.
Click to expand...
Click to collapse
andybones said:
Have you tried using Magisk latest beta? I ended up using beta for January for whatever reason and had no issue. I'd upload my boot.img but I'm a Verizon user and not sure if it'll work for you. "magisk_patched_dnuD3.img"
Magisk v21.2 (21200)
Magisk Manager v8.0.4 (4768) (15)
Click to expand...
Click to collapse
I installed 8.0.4 but when I try to patch the image with it, it fails. When I try to sideload 21.2 or 20.4, it says:
E:footer is wrong
E:Signature verification failed
E:error: 21
Install from ADB completed with status 2.
Installation aborted.

I was able to patch the image after changing to the beta channel. However, it started to loop again and eventually went back to bootloader with the reason being "no valid slot to boot". I've flash-all.bat'ed again and am back to working. I don't understand why I can't get this to work.

I also had an inability to boot after I tried to do the December update using Minimal ADB. No valid slot.
I switched to a new platform tools install, and the same procedure has now worked twice. How old is your platform tools install?

If anyone is having problems patching the stock boot.img, you can upload it and I can patch it and re-upload it for you.

earlgrey_44 said:
I also had an inability to boot after I tried to do the December update using Minimal ADB. No valid slot.
I switched to a new platform tools install, and the same procedure has now worked twice. How old is your platform tools install?
Click to expand...
Click to collapse
It was pretty new/latest version but I went ahead and just re-downloaded the factory image and platform tools and am trying again...
If it matters, I'm back to Canary manager and here is what my patch screen says:
Code:
- Device platform: arm64-v8a
- Magisk Manager: 8.0.4 (4770)
- Install target: 6d88d8ad (21201)
- Copying image to cache
- Unpacking boot image
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
- Repacking boot image
- Output file *path*
- All done!
My actual flash output is:
Code:
> fastboot flash boot magisk_patched_Mx5Yh.img
Sending 'boot_a' (98304 KB) OKAY [ 2.277s]
Writing 'boot_a' OKAY [ 0.312s]
Finished. Total time: 2.918s
UPDATE:
I got it working this time around using a fresh new factory image and platform tools download.
I'm actually wondering if, in my haste, I actually used the bootloader image, not the boot img...but wouldn't Magisk have complained? lol.
Who knows, but looks like my issue is resolved! Thanks all for having me try things like a new platform tools download.

Development [RECOVERY][UNOFFICIAL] TWRP 3.7.0 for 2021 Galaxy Tab A8 10.5 [SM-X200]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Notes:
What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this impressive tablet.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for metadata encryption (which causes mounting errors in log)
Downloads:
twrp_3.7.0_12-2_X200XXS1CWA3.tar.md5
twrp_3.7.0_12-2_X200XXS1CWA3.img
Change Log:
v3.7.0_12-2 (2023-02-28):
Updated to X200XXS1CWA3 (Android 13) OEM stock kernel (Jan 2023 Update).
v3.7.0_12-1 (2023-01-22):
Updated to X200XXU1CVL5 (Android 13) OEM stock kernel (Dec 2022 Update).
v3.7.0_12-0 (2023-01-01):
Fixed issue with MTP sometimes not starting until state is toggled in the Mount panel.
Switched to TWRP 3.7.0 release built from new AOSP-12.1 branch.
Updated to X200XXS1BVJ1 (Android 12) OEM stock kernel (Oct 2022 Security Update).
v3.7.0_11-1 (2022-10-24):
Adjusted dynamic partition size and removed redundant backup image.
v3.7.0_11-0 (2022-10-09):
Updated to TWRP 3.7.0 release built from AOSP-11 branch.
Updated to X200XXU1BVI6 (Android 12) OEM stock kernel.
v3.6.2_11-1 (2022-09-11):
Fixed Fastboot Mode (fastbootd) so that dynamic partitions (system, product, vendor) can be managed in TWRP.
v3.6.2_11-0 (2022-09-04):
Initial TWRP 3.6.2 release built from AOSP-11 branch.
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
Reboot to Recovery
What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch the boot.img file. More details on this process are available here. Note that you should just patch the boot.img file and not the whole AP tarball, since this device's bootloader doesn't like the empty vbmeta.img that Magisk will provide.
Source:
android_device_samsung_gta8wifi
Donations:
Your support is always appreciated! Just click here.

Additional Notes:
Ian's Multidisabler script has an issue on this device preventing it from disabling stock recovery auto-restoration. I'm hoping that a fix is forthcoming.
If you root this device with Magisk, be sure to patch only the boot.img file. Patching the AP tarball will generate a blank vbmeta.img, which this device's bootloader doesn't like for some reason.

Works on LTE version sm-x505 ??
Also which is better tab A7 or tab A8 ??

works perfectly. what i did was after rooting with magisk, i downloaded the official twrp app from playstore and downloaded your img to my tab. then i just flashed it from within the app. no issues.

Magendanz said:
Notes:
What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this impressive tablet.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for metadata encryption (which causes mounting errors in log)
MTP doesn't start until you disable and reenable in the Mount panel
Downloads:
twrp_3.6.2_11-0_X200XXU1AVG1.tar.md5
twrp_3.6.2_11-0_X200XXU1AVG1.img
Change Log:
v3.6.2_11-0 (2022-09-04):
Initial TWRP 3.6.2 release built from AOSP-11 branch.
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
Reboot to Recovery
What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch the boot.img file. More details on this process are available here. Note that you should just patch the boot.img file and not the whole AP tarball, since this device's bootloader doesn't like the empty vbmeta.img that Magisk will provide.
Source:
android_device_samsung_gta8wifi
Donations:
Your support is always appreciated! Just click here.
Click to expand...
Click to collapse
I am so delighted to see that there is major development for this device.
This will open the door for future custom ROMs.
Thank you Magendanz for your effort in bringing this to us.

I can say that is working as expected, thank you so much man. I thought that with TWRP we could be able to install a GSI ROM at least, but nothing at all lol

Tony Ronaldo Matute said:
I can say that is working as expected, thank you so much man. I thought that with TWRP we could be able to install a GSI ROM at least, but nothing at all lol
Click to expand...
Click to collapse
I think it's possible, but just using ChonDow_Flasher didn't work for me...I suspect because the bootloader isn't seeing an AVB hash footer on the GSI image. I had a similar experience when I built TWRP without the hash footer.
Unfortunately, I'm getting a segmentation error when trying to add a hash footer to the GSI using avbtool. It's probably a partition size issue, but I haven't had the time to troubleshoot.

Magendanz said:
I think it's possible, but just using ChonDow_Flasher didn't work for me...I suspect because the bootloader isn't seeing an AVB hash footer on the GSI image. I had a similar experience when I built TWRP without the hash footer.
Unfortunately, I'm getting a segmentation error when trying to add a hash footer to the GSI using avbtool. It's probably a partition size issue, but I haven't had the time to troubleshoot.
Click to expand...
Click to collapse
I had tried different ways also but I give up, the only thing that I can think now is try to use the "reboot to bootloader" feature in TWRP. But well, this processor is going me crazy.

Magendanz said:
Reserved
Click to expand...
Click to collapse
Once we get TWRP can't we just flash Magisk's zip file within TWRP like normally we do?
Also, after restart the tablet, when I tried to get back into TWRP it took me back to Android regular recovery. I had to flash TWRP again using Odin, after enabling MTP, local storage doesn't mount, I wasn't able to copy data in it.

zfk110 said:
Once we get TWRP can't we just flash Magisk's zip file within TWRP like normally we do?
Also, after restart the tablet, when I tried to get back into TWRP it took me back to Android regular recovery. I had to flash TWRP again using Odin, after enabling MTP, local storage doesn't mount, I wasn't able to copy data in it.
Click to expand...
Click to collapse
No, you should patch the boot.img using the Magisk app, then flash it using TWRP or pack in a tarball and use Odin. Don't patch the whole AP, as Magisk will substitute a blank vbmeta.img that the bootloader on this device doesn't like.

Rularick5 said:
works perfectly. what i did was after rooting with magisk, i downloaded the official twrp app from playstore and downloaded your img to my tab. then i just flashed it from within the app. no issues.
Click to expand...
Click to collapse
Was just going to try this method but I'm on AVC1...I'm assuming I need to be on AVG1?

As long as the binary number is the same, im assuming dont quote me, you should be able to flash avg1 then magisk then twrp. Just update to the latest firmware.

I figured that's what I had to do but was trying to avoid that....just rooted a week ago and had no idea about AVG1.
So if I want to upgrade to AVG1 or any other firmware in the future I have to do the whole process again of patching boot.img, flashing through Odin, factory reset and setting up everything again? There's no way to upgrade and retain root?

Not unless you can recieve ota while rooted.

New release is posted...
Downloads:
twrp_3.6.2_11-1_X200XXU1AVG1.tar.md5
twrp_3.6.2_11-1_X200XXU1AVG1.img
Change Log:
v3.6.2_11-1 (2022-09-11):
Fixed Fastboot Mode (fastbootd) so that dynamic partitions (system, product, vendor) can be managed in TWRP.

Magendanz said:
New release is posted...
Downloads:
twrp_3.6.2_11-1_X200XXU1AVG1.tar.md5
twrp_3.6.2_11-1_X200XXU1AVG1.img
Change Log:
v3.6.2_11-1 (2022-09-11):
Fixed Fastboot Mode (fastbootd) so that dynamic partitions (system, product, vendor) can be managed in TWRP.
Click to expand...
Click to collapse
Any news for GSI?

Tony Ronaldo Matute said:
Any news for GSI?
Click to expand...
Click to collapse
I successfully tested fastbootd with OEM images, but the LineageOS GSI I tried was still getting kernel panics. I assume it has to do with this bootloader's AVB 2.0 requirements, which we can't seem to work around in the usual way with a blank vbmeta.img.

Magendanz said:
I successfully tested fastbootd with OEM images, but the LineageOS GSI I tried was still getting kernel panics. I assume it has to do with this bootloader's AVB 2.0 requirements, which we can't seem to work around in the usual way with a blank vbmeta.img.
Click to expand...
Click to collapse
"OEM images", so the Google GSI? Also, maybe could the vb meta zip disabler works?

Tony Ronaldo Matute said:
"OEM images", so the Google GSI? Also, maybe could the vb meta zip disabler works?
Click to expand...
Click to collapse
No, the OEM for this device is Samsung. Please provide a link for this vbmeta disabler, since I've just been using the ones generated by Magisk and my own using avbtool make_vbmeta_image --out vbmeta.img.

Magendanz said:
No, the OEM for this device is Samsung. Please provide a link for this vbmeta disabler, since I've just been using the ones generated by Magisk and my own using avbtool make_vbmeta_image --out vbmeta.img.
Click to expand...
Click to collapse
So, first you can try this disabler:
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
as well, you can try to use this fastbootd command:
[Solved] VBmeta Flashing and Disable Verity Verification Command Problem
Thought to share with you guys, as many of people like me face problem while disabling the verification while flashing VBMETA.img. Most of the time the below command does not work and causes bootloop, when Installing Custom recovery. So i...
forum.xda-developers.com

Themes / Apps / Mods 📳🔥PixelFlasher for Google Pixel 7 Support Thread.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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 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.

Placeholder

Placeholder

Placeholder

Hi, thank you for doing this. My rooted pixel 7 pro is prompting me to install a security update. I tried to update via pixel flasher.
Flashed with the latest platform tools from offical android site and downloaded the latest factory image. Pixelflasher showed no error
And then my phone still prompts me to download updates,
phone android version = 13
build = TD1A.220804.009.A2
android security update = sept 5 2022
Did I flash the old factory image? or am I doing something wrong? or the pixel update prompt is an error?

dangercl0se said:
Hi, thank you for doing this. My rooted pixel 7 pro is prompting me to install a security update. I tried to update via pixel flasher.
Flashed with the latest platform tools from offical android site and downloaded the latest factory image.
And then my phone still prompts me to download updates, phone android version = 13 and build = TD1A.220804.009.A2
Am I flashing the old factory image? or am I doing something wrong? or the pixel update prompt is an error?
Click to expand...
Click to collapse
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.

@dangercl0se , like what @Tiebe says.

Tiebe said:
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.
Click to expand...
Click to collapse
thank you, i am noob.
badabing2003 said:
@dangercl0se , like what @Tiebe says.
Click to expand...
Click to collapse
all good, operator error!
thank you so much for making this, saved me so much time!!!

New Release:
Oct 27, 2022 v4.3.1.0 release
Bug Fix: Magisk modules not listed on MacOS / Linux

Ok so im currently Bootloader unlocked, rooted and custom kernel on Slot B. I would like to update Slot A with verity and verification disabled using the same firmware currently in Slot B. Do I select processed firmware zip first or can I jump right to the patched magisk.img. I tried switching slots and flashing the firmware(no patched init_boot.img) with verity and verification disabled first. It goes through the steps and ends on the Fastbootd screen. When I reboot, it reboots 3 times and ends up on slot b. Not sure what Im doing wrong. I even tried checking "flash to inactive slot" and still boots to slot B.

schmeggy929 said:
Do I select processed firmware zip first or can I jump right to the patched magisk.img.
Click to expand...
Click to collapse
If you intend to flash the firmware on that slot, then yes, you have to select it.
schmeggy929 said:
I tried switching slots and flashing the firmware(no patched init_boot.img) with verity and verification disabled first. It goes through the steps and ends on the Fastbootd screen. When I reboot, it reboots 3 times and ends up on slot b. Not sure what Im doing wrong. I even tried checking "flash to inactive slot" and still boots to slot B.
Click to expand...
Click to collapse
This sounds like the flashing is not going past fastbootd stage.
I have read reports that it takes long in that stage (even doing things manually) with no feedback, so make sure you are waiting long enough.
You should also make sure your cable / USB drivers are good, and preferably use USB 2.0 port.
Few reboots and then back to B indicates that A is not bootable.

badabing2003 said:
If you intend to flash the firmware on that slot, then yes, you have to select it.
This sounds like the flashing is not going past fastbootd stage.
I have read reports that it takes long in that stage (even doing things manually) with no feedback, so make sure you are waiting long enough.
You should also make sure your cable / USB drivers are good, and preferably use USB 2.0 port.
Few reboots and then back to B indicates that A is not bootable.
Click to expand...
Click to collapse
Looks like third time's a charm, I also swapped my usb type-c to type-c cable with a USB-A cable.

When the next update comes around, is it recommended to check the box for "Flash to both slots" along with checking disable Verity and verification?

schmeggy929 said:
When the next update comes around, is it recommended to check the box for "Flash to both slots" along with checking disable Verity and verification?
Click to expand...
Click to collapse
I don't disable verity and verification, Magisk patches properly.
However if you are using custom ROM, then you want to check with the ROM maker if either or both are necessary.
As for monthly update, I recommend you flash to inactive slot, not both slots, this way it is similar to OTA A/B, ie if anything goes wrong, your current setup in the current slot is not effected.

badabing2003 said:
I don't disable verity and verification, Magisk patches properly.
However if you are using custom ROM, then you want to check with the ROM maker if either or both are necessary.
As for monthly update, I recommend you flash to inactive slot, not both slots, this way it is similar to OTA A/B, ie if anything goes wrong, your current setup in the current slot is not effected.
Click to expand...
Click to collapse
thank you, I will "Flash to inactive slot" route. And yes for now, the available Kernels require Verity and verification disabled. I only want to have both slots verity and verification disabled just in case something goes wrong and I have to boot the other slot. I do not want to have to full wipe because I booted a verity and verification enabled slot.

New 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.

Typically I do everything manually but I decided to try this tool out on OSX and so far everything has worked flawlessly. Thank you for your work.

This is my first time using PixelFlasher; I usually do updates the manual way. I'm trying to install the November update and after flashing I'm getting the message about the device being corrupted.
If I hit the power button to continue it boots fine and everything seems to be good, but when doing this manually with the browser based Android flash tool, I don't end up with this message that I have to manually continue through.
Anyone have a guess as to what I'm doing wrong? FWIW, I'm trying to do this update while keeping data. TIA.
Edit: Attached Support.zip

dpotter38 said:
This is my first time using PixelFlasher; I usually do updates the manual way. I'm trying to install the November update and after flashing I'm getting the message about the device being corrupted.
If I hit the power button to continue it boots fine and everything seems to be good, but when doing this manually with the browser based Android flash tool, I don't end up with this message that I have to manually continue through.
Anyone have a guess as to what I'm doing wrong? FWIW, I'm trying to do this update while keeping data. TIA.
Edit: Attached Support.zip
Click to expand...
Click to collapse
FYI, I was able to get this fixed by flashing the Oct init_boot, then manually patching the November init_boot and flashing it.
I must have missed it the first time, but when trying to patch the November init_boot there was an error in the PixelFlasher console, "Foreign Key constraint failed", but it still showed the patched boot file as available in the list. Just wanted to put this out here in case anyone else runs up against a similar issue.

dpotter38 said:
This is my first time using PixelFlasher; I usually do updates the manual way. I'm trying to install the November update and after flashing I'm getting the message about the device being corrupted.
If I hit the power button to continue it boots fine and everything seems to be good, but when doing this manually with the browser based Android flash tool, I don't end up with this message that I have to manually continue through.
Anyone have a guess as to what I'm doing wrong? FWIW, I'm trying to do this update while keeping data. TIA.
Edit: Attached Support.zip
Click to expand...
Click to collapse
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.
dpotter38 said:
FYI, I was able to get this fixed by flashing the Oct init_boot, then manually patching the November init_boot and flashing it.
I must have missed it the first time, but when trying to patch the November init_boot there was an error in the PixelFlasher console, "Foreign Key constraint failed", but it still showed the patched boot file as available in the list. Just wanted to put this out here in case anyone else runs up against a similar issue.
Click to expand...
Click to collapse
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.