Magisk Canary Update
app-release_981ccabb-25210.apk
Notes:
app-release_981ccabb-25210.apk
Notes:
- Tap 3 dots (...) across from 10.x MB, Tap Download
It depends on the Custom ROM you are trying to install. That is why I wrote this in the OP: OP, ~ ~ ~ Part III - OTHER ~ ~ ~ 1. Custom ROMs, • Need help with a Custom ROM?,is there any way we can install magisk on Android 13 over a custom from? everytime I flash magisk in twrp it takes me to bootloader
Yup done that, did not find much help so i thought I'll expand my area of seeking supportIt depends on the Custom ROM you are trying to install. That is why I wrote this in the OP: OP, ~ ~ ~ Part III - OTHER ~ ~ ~ 1. Custom ROMs, • Need help with a Custom ROM?,
3. If you are trying to install a Addon(s) {Custom Kernel, Magisk, etc.} to the Custom ROM you installed: Search the thread of the Custom ROM you installed or the thread of the Addon you want to add to your Custom ROM for answer(s)/solution(s) to your question(s)/problem(s). If you don't find an answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM or Addon (Custom Kernel, Magisk, etc.) thread.
Some XDA Members are reporting the Adaway module does not work withIs 981ccabb-25210 still broken or fixed?
Edit: broken version...
Always on the edgeSDK Platform-tools
Several members of the XDA community have
written posts that SDK Platform-tools r34.0.1 broken. Problem: fastbootd not working
SDK Platform-tools r33.0.3 is attached : OP post #769
Excellent suggestion, I added a link to SDK Platform-tools rev. 33.0.3 to the OP and attach SDK Platform-tools rev. 33.0.3 to the same post, kinda.Always on the edge(thank you)
Nevertheless, why not add this same alert to OP or / and attach r33.0.3 to the same post?
Just wondering if there is a reason not to use rev. 34.0.0?Excellent suggestion, I added a link to SDK Platform-tools rev. 33.0.3 to the OP and attach SDK Platform-tools rev. 33.0.3 to the same post, kinda.
just 3 or 4 posts before yours, @Homeboy76 clearly stated the reason, it applies to 34.0.0 and 34.0.1
just 3 or 4 posts before yours, @Homeboy76 clearly stated the r
I actually had to go back to page 38 around Feb 21/22 to see 34.0.0 specifically mentioned as having a problem, and it was one person in a bootloop state. I followed the procedure here using 34.0.0 and it is working flawlessly, except when the Pixel 5 was booted in fastbootd, the Windows 10 PC would not recognize the device, but I loaded another driver so it was recognized at https://www.droidwin.com/how-to-install-fastboot-drivers-in-windows-11/just 3 or 4 posts before yours, @Homeboy76 clearly stated the reason, it applies to 34.0.0 and 34.0.1
Are you saying that it worked after you installed a driver from that post?I actually had to go back to page 38 around Feb 21/22 to see 34.0.0 specifically mentioned as having a problem, and it was one person in a bootloop state. I followed the procedure here using 34.0.0 and it is working flawlessly, except when the Pixel 5 was booted in fastbootd, the Windows 10 PC would not recognize the device, but I loaded another driver so it was recognized at https://www.droidwin.com/how-to-install-fastboot-drivers-in-windows-11/
Now that I think about it, I don't know why I did not get it from Google! Thanks for raising that mistake. I checked all the SHA256 hashes for the files and they all match with the files from your Google link. Also, the device manager shows the driver as signed by Google and did not prompt during the driver installation saying anything about not signed. Below is a screenshot from the Device Manager on PC.Are you saying that it worked after you installed a driver from that post?
I personally would not dare trust that.
1- Source is not from the official Google.
2- Unisgned, yet it says Google?
The error is telling your what your problem is.now im attempting to flash a ROM but i get this message
C:\platform-tools>adb devices
adb server version (32) doesn't match this client (41); killing...
* daemon started successfully
List of devices attached
-end of output-
Are you using SDK Platform-tools r. 34.0.1?just picked up a pixel 5 and it updated to android 13. OEM unlocking is enabled, USB debugging as well and the toggle for developer options is also on. I did a fresh install of platform-tools and the device is shown when adb devices is typed into the CMD Im able to reboot using fastboot and seems everything is working except when i enter fastboot flashing unlock its only pulls up the help section for adb. Any help on what I may have done wrong would be appreciated, thanks
fastboot --version
at the prompt. If a adb/fastboot is found delete the folder containing them. Also, check the path environment for paths to them and remove it.fastboot flashing unlock
and press enter.fastboot reboot
at the Command Prompt and press enter.fastboot flashing lock
fastboot reboot
fastboot flash boot boot.img --slot all
adb wait-for-device shell magisk --remove-modules
fastboot Reboot
flash-all
at the Command Prompt and press enter.flash-all
at the Command Prompt and press enter.adb wait-for-device shell magisk --remove-modules
fastboot Reboot
fastboot flash boot --slot all boot.img
fastboot flash boot "name of patched boot".img
without the quote marks at the Prompt and press enter.fastboot reboot
at the Prompt and press enter.fastboot flash boot boot.img --slot all
adb wait-for-device shell magisk --remove-modules
fastboot devices
to verify communication with phone. It should return your phone's serial number.You should have your stock image you can push over. I do not think replacing the boot image with another patched image would disable anything. You can also use adb to remove any modules. Regardless heres my patched boot image and the command to remove modules. Power off, connect phone enter this command, hold power button to boot phone.is there a magisk boot img with modules disabled?. i have a boot loop and need a boot img with it disabled.