Develop Bugs

December update not rootable?

Hi Y'all,
I just dirty flashed the December update, and then attempted to patch boot.img with magisk and flash that with fastboot, same as I've always been doing on Android 10 without fail. However, this time, it starts to boot, I get ADB, it bootloops twice, then goes back to fastboot with an error saying something to the effect of "no available slots"
I re-patched and it came out with the same md5sum of b1d09aa00e3376f3d4ceba4e97b99eae
I was able to get an adb logcat on both attempted boots, they're too large for any paste service so I threw them on a VPC I have
http://irc.killingkittens.net/logcat1.txt
http://irc.killingkittens.net/logcat2.txt
Magisk Canary, manager version 7.4.1-72edbfc4 (260)
Magisk 20.2-72edbfc4 (20108)
Happy to provide any other info that would help.

Worked fine for me.

I update ota by magisk method and work fine.
http://www.mediafire.com/view/k1r6pzneqwcrp4d/Screenshot_20191203-112633.png/file

phoe zay said:
I update ota by magisk method and work fine.
http://www.mediafire.com/view/k1r6pzneqwcrp4d/Screenshot_20191203-112633.png/file
Click to expand...
Click to collapse
I see that you're on older versions of both Magisk and Manager than I am. Which update channel are you on?

OK, root worked on my wife's P3. Canary 7.4.1-72edbfc4 (260) Manager an 20.2.72-edbfcr (20108) Magisk after flashing patched. Both show up to date. Install was a hyrbrid of flash-all and OTA. Still nobody seams to have found a reason why the flash-all (no -w) fails in fastbootd at product, but if you then switch to recovery while still on and then ADB sideload the OTA all is fine. 29.0.5 platform tools of course.

Works as normal for me.
I always sideload ota and then patch the boot.img from the full download

sliding_billy said:
OK, root worked on my wife's P3. Canary 7.4.1-72edbfc4 (260) Manager an 20.2.72-edbfcr (20108) Magisk after flashing patched. Both show up to date. Install was a hyrbrid of flash-all and OTA. Still nobody seams to have found a reason why the flash-all (no -w) fails in fastbootd at product, but if you then switch to recovery while still on and then ADB sideload the OTA all is fine. 29.0.5 platform tools of course.
Click to expand...
Click to collapse
Are you saying that if I update by having the phone in fastboot mode and running flash-all with -w removed than the phone update fails or gets wiped?
I had that experience last month where my phone was wiped even with -w removed! I would like to avoid getting wiped this time!

swieder711 said:
Are you saying that if I update by having the phone in fastboot mode and running flash-all with -w removed than the phone update fails or gets wiped?
I had that experience last month where my phone was wiped even with -w removed! I would like to avoid getting wiped this time!
Click to expand...
Click to collapse
Thankfully, no. I can't speak for any possible error when doing a flash-all (without -w), but the one that fails with the "sending product FAILED (Write to device failed (Invalid argument))" just shows a press any failure in command prompt and press any key to continue. The phone remains in fastbootd where you can use the volume keys and power to select recovery he use the keys again to select "sideload OTA from ADB" and while it is waiting use the "adb sideload [OTA path/filename].zip" command in commander and it acts as if you used the sideload in the first place changing slots, not erasing any data/settings/apps. I am not 100% sure yet, but I tend to think that the script is now acting differently if used without the -w but started without flashing stock .boot to both slots to unroot and remove any non-stock kernel. I have been doing it that way for 3+ years now on a Pixal, Piixel XL, Pixel 3 and Pixel 3 XL without issue until last month. I wanted to try it one more time this month after messing with my path and such, but I guess I will have to wait until January to try again. The 3 XL is on Havoc, so I can't test that one. My proposed instructions before doing it are 1)disable all modules, 2)reboot to system, 3)go to BL, 4)Flash previous stock .boot to both slots, 5)boot to system, 6)go to BL, 7)flash-all (without -w), 8)cross your fingers.

Can someone give me the md5 of the patched boot.img from this release? Or, upload a working patched file?
The specific error I got was "no valid slot to boot"
I tried flashing each slot manually, same error. I see that happened a year ago and it related to magisk versions: https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-root-pixel-3-xl-magisk-t3856712/page2

I always update via flash-all with -w option removed.
Did the same this time and no issues.
Not sure how to attach the patched boot as it is too large.
Here is the patched md5:
02536812e6b2e09e4707f98d65e7918f magisk_patched.img

I have the same problem with the same version of Magisk as you and the -w flag in flash-all didn't make a difference.

nomisunrider said:
I always update via flash-all with -w option removed.
Did the same this time and no issues.
Not sure how to attach the patched boot as it is too large.
Here is the patched md5:
02536812e6b2e09e4707f98d65e7918f magisk_patched.img
Click to expand...
Click to collapse
Completely different md5 as me when I try either magisk canary or stable! Can you please upload it to something like https://mega.co.nz/ and generate a share link?

DOMF said:
Completely different md5 as me when I try either magisk canary or stable! Can you please upload it to something like https://mega.co.nz/ and generate a share link?
Click to expand...
Click to collapse
Well, crap, I was able to get the same md5sum by flashing Canary-non-debug, but I still get the crash back to the bootloader with the error "no valid slot to boot"
Anyone have any suggestions before I try a full wipe?

I'm rooted in December but my network connectivity took a serious downgrade with it.

I'm having the same problem on Pixel 3, it just can't boot after patching the boot.img :\

sliding_billy said:
Still nobody seams to have found a reason why the flash-all (no -w) fails in fastbootd at product,...
Click to expand...
Click to collapse
I found the reason:
Bad cable -> Solution: try another cable,
bad USB port -> Solution: try another port or computer,
or old SDK version -> download and update.
Definitely one of these.
Anyway, I also have the problem with bootloop after patch.

Worked just fine here flashing full image (-w) and then applying the patched boot.img from Magisk (20108). Not sure what is going on, but make sure you are on the latest binaries 29.0.5 (October 2019)

v12xke said:
Worked just fine here flashing full image (-w) and then applying the patched boot.img from Magisk (20108). Not sure what is going on, but make sure you are on the latest binaries 29.0.5 (October 2019)
Click to expand...
Click to collapse
Ugh I don't wanna wipe, especially without having taken a TiBu backup first (I know, bad me, it's just worked every time flawlessly so far!)
I'm on 29.0.5.1
Code:
~ fastboot --version
fastboot version 29.0.5-1
Installed as /usr/bin/fastboot
but now that you mention it, I've run into an issue with Arch's implementation of android-tools in the past. Will try from my mac tomorrow.

DOMF said:
Ugh I don't wanna wipe, especially without having taken a TiBu backup first (I know, bad me, it's just worked every time flawlessly so far!) I'm on 29.0.5.1
Click to expand...
Click to collapse
You wouldn't need to wipe... just fastboot flash the original (stock) boot.img and then get it sorted once back into System. Best of luck :good:

v12xke said:
You wouldn't need to wipe... just fastboot flash the original (stock) boot.img and then get it sorted once back into System. Best of luck :good:
Click to expand...
Click to collapse
When I got into the bootloop after applying the Magisk modified boot.img, flashing stock boot.img didn't fix it for me. I had to flash-all again to get it to boot.
I have the latest Canary Magisk Manager 7.4.1-72edbfc4(260) installed, but I also tried the stable channel and still had the same problem. I noticed that my phone faile SafetyNet over ctsProfile: false. Could my problems be related to not un-hiding Magisk? And thinking back, I may not have rebooted after disabling my modules before I started flashing.

Uninstall Magisk Module from stock recovery

I installed a Magisk Module, called Notch killer or something to that effect from magisk downloads. Reboot caused my phone to not boot, but be stuck on the boot animation forever.
Is there a way to uninstall the module alone or recover the system without losing data. I am more concerned about the storage card data and would like to keep that for sure. Any insights / help is greatly appreciated.

srikaran said:
I installed a Magisk Module, called Notch killer or something to that effect from magisk downloads. Reboot caused my phone to not boot, but be stuck on the boot animation forever.
Is there a way to uninstall the module alone or recover the system without losing data. I am more concerned about the storage card data and would like to keep that for sure. Any insights / help is greatly appreciated.
Click to expand...
Click to collapse
If u search properly there is already a thread about this

v.konvict said:
If u search properly there is already a thread about this
Click to expand...
Click to collapse
Thanks for the pointer. I did go through all the threads and did find similar issue already addressed. For anyone that's keen, I ended up installing the stock boot.img and that ensured that I could boot. Out of curiosity, I tried to flash the patched boot.img and that ended up in the same loop again. Will search further as to how to remove that module first and then flash the patched boot.img, that should work somehow, not sure yet.
https://forum.xda-developers.com/oneplus-7t/help/magisk-modules-causing-bootloop-t3981427

OK, finally got everything back to running the way it was. After getting the stock boot image, to root it again, I followed the following steps.
1. Download the full OTA image
2. Install Payload Dumper
3. Extract recovery.img using the Payload Dumper from the full image (Payload.bin)
4. Extract the recovery.img using Android Image Kitchen.
5. Modify the default.prop to enable adb in ramdisk folder
6. Repackaged the recovery.img
7. Flashed the modified recovery.img to recovery partition.
8. Booted to recovery.
9. On the PC, went into adb shell, navigated to /data/adb/modules and identified the rogue magisk module and deleted that folder completely.
10. Booted back to bootloader
11. Flashed the stock recovery back to the recovery partition.
12. Rebooted to recovery, just to verify that everything was intact.
13. Rebooted to bootloader
14. Installed the patched boot.img for root
15. Reboot the system
That made it work as it was before without any issues. Thanks a ton to the great community that had already solved these issues. Here are the links to the forum posts and tools used.
How to Root: https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Patched boot.img (10.3.0, Indian version): https://forum.xda-developers.com/oneplus-7t/how-to/oneplus-7t-10-3-0-indian-hd1901-t4021047
Payload Dumper: https://github.com/vm03/payload_dumper
Android Image Kitchen: https://forum.xda-developers.com/showthread.php?t=2073775
ADB in recovery: https://forum.xda-developers.com/7t-pro/development/recovery-oxygen-os-stock-recovery-adb-t3991865
Remove Magisk Modules: https://forum.xda-developers.com/oneplus-7t/how-to/magisk-twrp-root-module-uninstall-t4002843

10.0.11 Global - ADB Enabled - Insecure Recovery
I've tested it on my OP7T, worked for me.
https://drive.google.com/file/d/1FgngmAJQ-GKc0nIjngcspkU_xzwb-Y7T/view?usp=sharing
Please follow this guide on how to remove magisk modules
https://forum.xda-developers.com/7t-pro/how-to/guide-remove-magisk-modules-twrp-t3995677

Twrp can't decrypt data

Hey everyone,
After updating to the last stable version of xiaomi.eu I wanted to reflash magisk but when I boot into recovery I'm not asked for any password yet my data is still encrypted.
I tried running #twrp decrypt password in the terminal but it fails.
Has anyone here encounter the same problem?

Tom403 said:
Hey everyone,
After updating to the last stable version of xiaomi.eu I wanted to reflash magisk but when I boot into recovery I'm not asked for any password yet my data is still encrypted.
I tried running #twrp decrypt password in the terminal but it fails.
Has anyone here encounter the same problem?
Click to expand...
Click to collapse
Why don't you install Magisk by patching Boot image from Magisk Manager and flashing the patched image from Fastboot.
Just for Magisk, you don't need (to bother with) TWRP

zgfg said:
Why don't you install Magisk by patching Boot image from Magisk Manager and flashing the patched image from Fastboot.
Just for Magisk, you don't need (to bother with) TWRP
Click to expand...
Click to collapse
Won't that replace my recovery with the stock one?
I'd like to keep twrp

Tom403 said:
Won't that replace my recovery with the stock one?
I'd like to keep twrp
Click to expand...
Click to collapse
You flash the patched Boot image from Fastboot, so Recovery (and other partitions) remains the one you have currently installed.
Also, just patching in Magisk Manager does not affect either Recovery, Boot (Vendor, etc)
When patching Boot image by Magisk Manager make sure you take the options:
-Preserve ADM dm-verity: YES
-Preserve force encryption: YES
-Recovery mode: NO

zgfg said:
You flash the patched Boot image from Fastboot, so Recovery (and other partitions) remains the one you have currently installed.
Also, just patching in Magisk Manager does not affect either Recovery, Boot (Vendor, etc)
When patching Boot image by Magisk Manager make sure you take the options:
-Preserve ADM dm-verity: YES
-Preserve force encryption: YES
-Recovery mode: NO
Click to expand...
Click to collapse
Ok, I'll do that then
Thanks for the help ?

Tom403 said:
Ok, I'll do that then
Thanks for the help ?
Click to expand...
Click to collapse
For the Boot image you have to patch boot.img extracted from zip/recovery package of your stock ROM
But you can also backup Boot partition by TWRP and then let Magisk Manager patch the backup boot.emmc.win file

Is it safe to assume that Tom403 didn't find any love at the end of the encrypted rainblow? I JUST WANT to verify, This IS the same situation that used to be remedied by deleting locksettings.db and a files with .key extension?? No such luck for anymore, wow, what a setup for future-screwing your users Google!! Dicks

goo. said:
Is it safe to assume that Tom403 didn't find any love at the end of the encrypted rainblow? I JUST WANT to verify, This IS the same situation that used to be remedied by deleting locksettings.db and a files with .key extension?? No such luck for anymore, wow, what a setup for future-screwing your users Google!! Dicks
Click to expand...
Click to collapse
Okay, I may have found a lightbulb somewhere in the tunnel that may be whats required for others as well to unencrypt when deleting .keyfiles is no longer an option having version greater than PIE. It's in the form of in a recovery log from a recent, perhaps backup attempt, that states the version of Orange Fox recovery I had (11.0) and also says fbe encryption in use and info like the following that looks very promising... I'd really appreciate if someone that knows more than me to let me know if I'm on the right path and guide me in if so... heres part of the LOG that gives me hope --
ased Encryption is present
e4crypt_initialize_global_de
Determining wrapped-key support for /data
fbe.data.wrappedkey = false
calling retrieveAndInstallKey
Key exists, using: /data/unencrypted/key
Using SoftwareWrappedKeymaster1Device from Google for encryption. Security level: TRUSTED_ENVIRONMENT, HAL: [email protected]::IKeymasterDevice/default
Determining wrapped-key support for /data
fbe.data.wrappedkey = false
Added key 90117251 (ext4:72f7ca8ad834ad5d) to keyring 322439018 in process 546
Added key 866183642 (f2fs:72f7ca8ad834ad5d) to keyring 322439018 in process 546
Added key 321684719 (fscrypt:72f7ca8ad834ad5d) to keyring 322439018 in process 546
contents mode 'aes-256-xts' filenames 'aes-256-heh'
Wrote system DE key reference to:/data/unencrypted/ref
e4crypt_ini
Thanks in advance for any help with this

Tom403 said:
Hey everyone,
After updating to the last stable version of xiaomi.eu I wanted to reflash magisk but when I boot into recovery I'm not asked for any password yet my data is still encrypted.
I tried running #twrp decrypt password in the terminal but it fails.
Has anyone here encounter the same problem?
Click to expand...
Click to collapse
thanks for the terminal command

Question Tried installing magisk on top of lineageos, now stuck in boot loop

Hello,
I followed the official steps for LOS and gapps and all went well. Then I followed the official steps for magisk and I extracted boot.img and patched it fine. I'm fairly certain I have the global version (live in Canada, bought from aliexpress, it said global version) so I found the firmware online. Then I pushed it via fastboot to boot_a and boot_b. I'm not sure if this was right... Anyway, after this was done, I rebooted and then got stuck in the LOS boot logo. Rebooting and trying to flash stock boot.img that I extracted doesn't work, trying to flash lineageos recovery.img doesn't work (no such parititon). When it reboots to recovery it's the stock recovery. I can't do anything but go to fastboot mode and then nothing flashes.
Help??
References:
Redirecting…
Installation
The Magic Mask for Android
topjohnwu.github.io
Thanks!

One more note. When patching boot.img, magisk docs say to ensure recovery is checked. I didn't find this option, so assume it was checked by default as the docs said. Perhaps it was unchecked and, idk, I deleted my recovery partition?

sburry said:
One more note. When patching boot.img, magisk docs say to ensure recovery is checked. I didn't find this option, so assume it was checked by default as the docs said. Perhaps it was unchecked and, idk, I deleted my recovery partition?
Click to expand...
Click to collapse
try downloading magisk23.0.apk and rename it by uninstall.zip save it to your phone you can save it through recovery mtp enabled, after saving it try flashibg the uninstall.zip reboot to system and comeback here

Hi guys i have problem with magisk also, can't pass safetynet ctsprofile

Leejhay1714 said:
Hi guys i have problem with magisk also, can't pass safetynet ctsprofile
Click to expand...
Click to collapse
under the settings of magisk tap magiskhide and click systemless host then check again the safety net if not working
install riru on your magisk reboot your phone
go to google search universal safetynet fix the site is github and install it for riru not zygisk take note after downloading it flash it on your magisk reboot phone

khazzey said:
under the settings of magisk tap magiskhide and click systemless host then check again the safety net if not working
install riru on your magisk reboot your phone
go to google search universal safetynet fix the site is github and install it for riru not zygisk take note after downloading it flash it on your magisk reboot phone
Click to expand...
Click to collapse
I forget tell that i do all of that because i search first for i post here and non of that can fix ctsprofile

Leejhay1714 said:
I forget tell that i do all of that because i search first for i post here and non of that can fix ctsprofile
Click to expand...
Click to collapse
the best way to fix your safetynet is to change to another custom rom that supports cts with or without root

khazzey said:
the best way to fix your safetynet is to change to another custom rom that supports cts with or without root
Click to expand...
Click to collapse
How sad i love los since cyanogenmod day

Leejhay1714 said:
How sad i love los since cyanogenmod day
Click to expand...
Click to collapse
you can also try magisk canary to bypass safety net universal safety net for zygisk

khazzey said:
try downloading magisk23.0.apk and rename it by uninstall.zip save it to your phone you can save it through recovery mtp enabled, after saving it try flashibg the uninstall.zip reboot to system and comeback here
Click to expand...
Click to collapse
So I fastboot flash uninstall.zip?

sburry said:
So I fastboot flash uninstall.zip?
Click to expand...
Click to collapse
flash it on your recovery

khazzey said:
flash it on your recovery
Click to expand...
Click to collapse
flash first twrp on your poco f3

khazzey said:
flash first twrp on your poco f3
Click to expand...
Click to collapse
if you dont have custom recovery yet

khazzey said:
you can also try magisk canary to bypass safety net universal safety net for zygisk
Click to expand...
Click to collapse
How? Do you have a link

Leejhay1714 said:
How? Do you have a link
Click to expand...
Click to collapse
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com

khazzey said:
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Gonno try this, thanks a lot

khazzey said:
flash first twrp on your poco f3
Click to expand...
Click to collapse
I had flashed LineageOS recovery, but i can't even get back into recovery now, or reflash recovery.
$ fastboot flash recovery lineage-18.1-20210819-recovery-h910.img
Sending 'recovery' (26844 KB) OKAY [ 0.943s]
Writing 'recovery' FAILED (remote: '(recovery_a) No such partition')
fastboot: error: Command failed
edit: shoot I was mixing up steps from another phone. shouldn't rely on ctrl + R bash history!
I was able to flash lineageos recovery, had to flash it to boot, not to recovery. reinstalling LOS itself now.
guess I'll try the process again, with the patching of boot.img, but this time ensure recovery is checked. that should be ok right?

Leejhay1714 said:
Gonno try this, thanks a lot
Click to expand...
Click to collapse
please update me if its working

sburry said:
I had flashed LineageOS recovery, but i can't even get back into recovery now, or reflash recovery.
$ fastboot flash recovery lineage-18.1-20210819-recovery-h910.img
Sending 'recovery' (26844 KB) OKAY [ 0.943s]
Writing 'recovery' FAILED (remote: '(recovery_a) No such partition')
fastboot: error: Command failed
edit: shoot I was mixing up steps from another phone. shouldn't rely on ctrl + R bash history!
I was able to flash lineageos recovery, had to flash it to boot, not to recovery. reinstalling LOS itself now.
guess I'll try the process again, with the patching of boot.img, but this time ensure recovery is checked. that should be ok right?
Click to expand...
Click to collapse
to change your recovery boot you phone into fastboot mode connect phone to pc open sdk platform tools in cmd then type fastboot boot twrp.img (the twrp name plus the extension file of recovery) after temporary flashing copy the twrp img to your phone and go to advance tab of twrp flash recovery ramdisk choose the twrp img

khazzey said:
to change your recovery boot you phone into fastboot mode connect phone to pc open sdk platform tools in cmd then type fastboot boot twrp.img (the twrp name plus the extension file of recovery) after temporary flashing copy the twrp img to your phone and go to advance tab of twrp flash recovery ramdisk choose the twrp img
Click to expand...
Click to collapse
Alright so I did get LOS reinstalled and the magisk app. I also realize that when I patch boot.img, I don't need to check the recovery box, because it's not a recovery image, it's a boot image. This all goes smoothly, but then the device is stuck in boot loop. I can just reinstall the LOS recovery but I'd like to get magisk working. Is it possible to have both of these?

Question Help!!!!!! Boot failure / stuck in fastboot

Need help. I used AFT to flash April - good, I rebooted and flashed magisk patched image made with stable 25.2 - good, flashed Kirisakura Raviantha Kernel v1.0.2 - good. Magisk said update to 26.1 so I did. I did direct install to update to 26.1. My P6P rebooted ok. power off and now stuck in fastboot mode showing device state= unlocked, boot slot: a, Enter reason: boot failure. I've tried to flash stock boot.img to both slots and the new april bootloader.img to both slots....the phone won't boot past fastboot screen. It won't go into recovery mode either. Please help!!!!!!!!
PS platform tools v33.0.3

jcp2 said:
Need help. I used AFT to flash April - good, I rebooted and flashed magisk patched image made with stable 25.2 - good, flashed Kirisakura Raviantha Kernel v1.0.2 - good. Magisk said update to 26.1 so I did. I did direct install to update to 26.1. My P6P rebooted ok. power off and now stuck in fastboot mode showing device state= unlocked, boot slot: a, Enter reason: boot failure. I've tried to flash stock boot.img to both slots and the new april bootloader.img to both slots....the phone won't boot past fastboot screen. It won't go into recovery mode either. Please help!!!!!!!!
PS platform tools v33.0.3
Click to expand...
Click to collapse
Try using Android Flash Tool to get back to stock.

I tried. it failed.
Flash Failed​Device failed to boot into userspace fastboot. This usually indicates that the build you are flashing does not boot. Device serial logs can be helpful to determine the root cause of the failure

jcp2 said:
I tried. it failed.
Flash Failed​Device failed to boot into userspace fastboot. This usually indicates that the build you are flashing does not boot. Device serial logs can be helpful to determine the root cause of the failure
Click to expand...
Click to collapse
Then just manually flash ROM files in fastboot

jamescable said:
Then just manually flash ROM files in fastboot
Click to expand...
Click to collapse
is there a write up somewhere with adb commands?

Use PixelFlasher and the latest full update.

AlDollaz said:
Use PixelFlasher and the latest full update.
Click to expand...
Click to collapse
tried that as well
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

I'm not sure of the commands. Fastboot flash recovery "recovery.img" , same with the other files inside the zip inside the stock rom zip file
If i ran into this issue I'd try fastboot -w and fastboot update a custom rom.

jcp2 said:
is there a write up somewhere with adb commands?
Click to expand...
Click to collapse
Most need to be flashed in fastbootd I think. So to get there, fastboot reboot fastboot. You can flash recovery( boot, dtbo and vendor boot) in regular fastboot. That should fix everything because it will fully get rid of magisk

I used AFT and forced flashed partitions / wiped (kept bootloader unlock) and it's alive again!

Simply out of curiosity - what made you update magisk? Are there "must have" features in the new release?

StanWiz said:
Simply out of curiosity - what made you update magisk? Are there "must have" features in the new release?
Click to expand...
Click to collapse
Release Magisk v26.1 · topjohnwu/Magisk
Changes from v26.0 [App] Fix crashing when revoking root permissions [MagiskInit] Always prefer ext4 partitions over f2fs when selecting the pre-init partition [General] Restore module files' cont...
github.com
See for yourself, but the sepolicy and Zygisk updates I would consider "must haves". Of course, if you're still running an Android 5 device you won't be happy: Magisk 26.1 dropped Android 5 support.

Strephon Alkhalikoi said:
Release Magisk v26.1 · topjohnwu/Magisk
Changes from v26.0 [App] Fix crashing when revoking root permissions [MagiskInit] Always prefer ext4 partitions over f2fs when selecting the pre-init partition [General] Restore module files' cont...
github.com
See for yourself, but the sepolicy and Zygisk updates I would consider "must haves". Of course, if you're still running an Android 5 device you won't be happy: Magisk 26.1 dropped Android 5 support.
Click to expand...
Click to collapse
I'm all for change but I don't enjoy being a guinea pig .lol
If I have an application ( magisk 25.2) that works flawlessly I will hold off a few days prior to jumping on the band wagon ( unless the new version has something I really need) - more often than not there are issues. I prefer to read about them rather than experiencing on my own skin. Hence my question.

StanWiz said:
I'm all for change but I don't enjoy being a guinea pig .lol
If I have an application ( magisk 25.2) that works flawlessly I will hold off a few days prior to jumping on the band wagon ( unless the new version has something I really need) - more often than not there are issues. I prefer to read about them rather than experiencing on my own skin. Hence my question.
Click to expand...
Click to collapse
Not everyone thinks as you do. I update as soon as a new version is released, but I also know what I'm doing.

Strephon Alkhalikoi said:
Not everyone thinks as you do. I update as soon as a new version is released, but I also know what I'm doing.
Click to expand...
Click to collapse
It's not a question of knowledge but rather the things that are beyond ones control - possibility of bugs in the code. For example look what happened recently with platform tools.

@jcp2 With all the things you flash, you should also know what that is. Then it would be much easier for you to figure it out why your device is in an unbootable state.
Magisk, Kernel, fastbootd... have one thing in common: your boot.img!
It doesn't make sense to let Magisk patch your boot.img and installing a custom kernel without Magisk installed afterwards. In that case Magisk gets overwritten.
Your fastbootd is only a binary and located in the recovery's /sbin folder. Due to the fact that your P6P is an A/B slot device, your recovery is part of the boot.img.
Flash your stock boot.img from the image-raven-BUILD_NO.zip that you'll find inside your firmware download.

I had already tried flashing stock boot image to both slots. I had to use AFT and force flash all partions. I'm up and running/ rooted. I just have to reinstall apps .

Android flash tool is by far the easiest way to go for sure. Happy you got it fixed

{Mod edit: Quoted post has been deleted. Oswald Boelcke}
6. fast boot flash
That ADB Command does nothing.
The correct command is:
fastboot flash boot boot.img if you want to flash the boot.img

{Mod edit: Quoted post has been deleted. Oswald Boelcke}
You should give us the correct command. The syntax is (see fastboot -h):
Code:
flash PARTITION [FILENAME] Flash given partition, using the image from
$ANDROID_PRODUCT_OUT if no filename is given.
you can't use "fast boot" for a binary that's called "fastboot(.exe)".