Related
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
Google helpfully updated my Pixel 3 (with Magisk) OTA to Android 10.
I've followed the instructions to move to the Canary/Canary Debug channel, updated Magisk Manager, uploaded to the phone both the OTA and recovery images, but Magisk is unable to patch:
Code:
- Device platform: arm64-v8a
- Copying image to cache
1618+0 records in
1618+0 records out
1656832 bytes (1.5 M) copied, 0.005972 s, 265 M/s
1085+1 records in
1085+1 records out
1111628 bytes (1.0 M) copied, 0.005266 s, 201 M/s
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
- Unpacking boot image
! Unsupported/Unknown image format
! Installation failed
I've tried with these factory images:
blueline-ota-qp1a.191005.007-e5bf373b.zip
blueline-qp1a.191005.007-factory-c36610c6.zip
Extracting boot.img from either of those images, uploading to the phone "Download" directory and attempting to patch isn't possible. Magisk Manager does not show boot.img at all in the file selection list, even though it is there, verified by both Astro file manager as well as adb shell and PC file sharing.
Suggestion what to try next?
I gave it a shot and downloaded the factory image to test. Had no issues patching the boot image file with Magisk Canary 20001 on my OP3T using Manager 245. Something's obviously wrong (and you're not the only one reporting this), but I've no idea what...
Didgeridoohan said:
I gave it a shot and downloaded the factory image to test. Had no issues patching the boot image file with Magisk Canary 20001 on my OP3T using Manager 245. Something's obviously wrong (and you're not the only one reporting this), but I've no idea what...
Click to expand...
Click to collapse
Hi, I flashed coltos5.1 on my op3t yesterday to give a try with Android 10 but I'm unable to install magisk 20 (downloaded from Magisk Manager 7.3.5). I tried from TWRP and also by patching the boot file (extracted from the ROM). How have you been able to flash it ? Which ROM are you using ?
coolrick said:
Hi, I flashed coltos5.1 on my op3t yesterday to give a try with Android 10 but I'm unable to install magisk 20 (downloaded from Magisk Manager 7.3.5). I tried from TWRP and also by patching the boot file (extracted from the ROM). How have you been able to flash it ? Which ROM are you using ?
Click to expand...
Click to collapse
I have not yet tried 10 on my 3T. I merely tested patching the Pixel 3 Android 10 boot image, and that worked without problem. On my device, I have to add...
Right now I downloaded ColtOS and tried patching the boot image. That worked without issue (can't test flashing it though, of course), so what problems do you have?
Didgeridoohan said:
I have not yet tried 10 on my 3T. I merely tested patching the Pixel 3 Android 10 boot image, and that worked without problem. On my device, I have to add...
Right now I downloaded ColtOS and tried patching the boot image. That worked without issue (can't test flashing it though, of course), so what problems do you have?
Click to expand...
Click to collapse
Thanks for the quick reply - Patching was not a problem but then it doesn't boot. I got the oneplus logo but it doesn't go further (no bootloop, I stays on the logo and doesn't do anything).
coolrick said:
Thanks for the quick reply - Patching was not a problem but then it doesn't boot. I got the oneplus logo but it doesn't go further (no bootloop, I stays on the logo and doesn't do anything).
Click to expand...
Click to collapse
Getting off-topic... Replied here: https://forum.xda-developers.com/ap...systemless-t3432382/post80522263#post80522263
coolrick said:
Thanks for the quick reply - Patching was not a problem but then it doesn't boot. I got the oneplus logo but it doesn't go further (no bootloop, I stays on the logo and doesn't do anything).
Click to expand...
Click to collapse
I just refollow everything from the magisk guide (https://topjohnwu.github.io/Magisk/install.html#boot-image-patching) and retry the Boot Image Patching. This time it was OK - My OP3T endly boot up fine. Anyway, thanks for your help.
Magisk, TWRP and Android 10
coolrick said:
Hi, I flashed coltos5.1 on my op3t yesterday to give a try with Android 10 but I'm unable to install magisk 20 (downloaded from Magisk Manager 7.3.5). I tried from TWRP and also by patching the boot file (extracted from the ROM). How have you been able to flash it ? Which ROM are you using ?
Click to expand...
Click to collapse
I think Magisk and TWRP don't support Android 10 quit well. I got the same error message.
I've been waited for Magisk v21 released by John Wu this morning, but I ran into some problems
What I've done
- download stock image file from Google official site
- follow the instruction given by John Wu at GitHub wiki
- run command
Code:
adb shell magisk --remove-modules
- when i flash the patched boot.img file, it stuck on the *G logo* with progress bar under it.
- After a certain period of time, it comes back to bootloader with a prompt saying: "no valid slot to boot".
What i've tried:
- redo all processes, no working
- switch active slot to both a & b, none working
- re-patch the stock boot.img file use different Magisk Manager version. The ones i tried: v8.0.0-Beta(offers Magisk v21), v8.0.0-Stable(offers Magisk v20.4), Canary version (offers Magisk Canary who claims to support android 11)
- change the command
HTML:
fastboot flash boot ***.img
to
HTML:
fastboot flash boot_a ***.img
&
HTML:
fastboot flash boot_b ***.img
then run
HTML:
fastboot reboot
. same result as said before
Basic info:
- Device: Pixel 3 (blueline), android 11 (build number RP1A.200720.009), latest android security update & Google play system update.
- Magisk: Magisk Manager v8.0.0 (released hours ago), Magisk v21 is suppose to be installed
Is patched boot.img filesize ~32 or ~64mb?
I ran into the same problem. My phone is a Pixel 2 XL running Android 11. However, I was not patient enough to wait for the "no valid slot to boot" message. After waiting for 5-10 minutes, I did a factory reset.
I followed the installation instruction that were posted by John Wu.. (As a new user, I am not allowed to post an outside link)
The displayed Magisk installation messages do not suggest a problem:
- Device platform: arm64-v8a
- Copying image to cache
- Unpacking boot image
- Checking ram disk status
- Stock boot image detected
- Patching ram disk
- Repacking boot image
***************************
Output file is written to
/storage/emulated/0/Download/magisk_patched.img
***************************
- All Done!
The boot.img and magisk_patched.img files have both a file size of 41943040 bytes. This is a different from previous Magisk version. For instance, with Magisk 20.4 and Android 10, the file sizes of boot.img and magisk_patched.img were 41943040 and 25747456, respectively. Thus, the patched file was smaller than the original.
done
dmk16 said:
Is patched boot.img filesize ~32 or ~64mb?
Click to expand...
Click to collapse
the stock & patched boot.img are both 65535KB large, which is weird and also mentioned by @red stapler
red stapler said:
I ran into the same problem. My phone is a Pixel 2 XL running Android 11. However, I was not patient enough to wait for the "no valid slot to boot" message. After waiting for 5-10 minutes, I did a factory reset.
I followed the installation instruction that were posted by John Wu.. (As a new user, I am not allowed to post an outside link)
The displayed Magisk installation messages do not suggest a problem:
- Device platform: arm64-v8a
- Copying image to cache
- Unpacking boot image
- Checking ram disk status
- Stock boot image detected
- Patching ram disk
- Repacking boot image
***************************
Output file is written to
/storage/emulated/0/Download/magisk_patched.img
***************************
- All Done!
The boot.img and magisk_patched.img files have both a file size of 41943040 bytes. This is a different from previous Magisk version. For instance, with Magisk 20.4 and Android 10, the file sizes of boot.img and magisk_patched.img were 41943040 and 25747456, respectively. Thus, the patched file was smaller than the original.
Click to expand...
Click to collapse
Seems like we're in the same boat here lol, is this enough proof for a legit bug issue to John?
red stapler said:
The boot.img and magisk_patched.img files have both a file size of 41943040 bytes. This is a different from previous Magisk version.
Click to expand...
Click to collapse
DaddyTony said:
the stock & patched boot.img are both 65535KB large, which is weird and also mentioned by @red stapler
Click to expand...
Click to collapse
The patched boot image is supposed to be the same size as the original now.
From the v21 changelog:
[MagiskBoot] Pad boot images to original size with zeros
Click to expand...
Click to collapse
nogaff said:
The patched boot image is supposed to be the same size as the original now.
From the v21 changelog:
Click to expand...
Click to collapse
Glad to hear, hope this indicates patch is successfully done?
Why not:
adb reboot bootloader
fastboot boot twrp-xxxx.img
adb push magisk-xxxx.zip /tmp
adb shell twrp install /tmp/magisk-xxxx.zip
adb reboot system
Let the magisk zip update script figure everything out...
Its what i do on Pixel 2 XL, works every time...10/11
So far, what we've seen that is causing issues with Android 11 and Magisk is usually either having incompatible modules installed (the brand new Safe Mode should take care of that, see the FAQ for details), or having TWRP installed to your device (it'll cause a conflict and the device won't boot, install the stock recovery and only use TWRP booted).
I forgot to mention that I didn't install or use a custom recovery, such as TWRP. Using the stock recovery.
73sydney said:
Why not:
adb reboot bootloader
fastboot boot twrp-xxxx.img
adb push magisk-xxxx.zip /tmp
adb shell twrp install /tmp/magisk-xxxx.zip
adb reboot system
Let the magisk zip update script figure everything out...
Its what i do on Pixel 2 XL, works every time...10/11
Click to expand...
Click to collapse
Sorry but i don't think Pixel 3 have Teamwin (TWRP) support of android 11?
Didgeridoohan said:
So far, what we've seen that is causing issues with Android 11 and Magisk is usually either having incompatible modules installed (the brand new Safe Mode should take care of that, see the FAQ for details), or having TWRP installed to your device (it'll cause a conflict and the device won't boot, install the stock recovery and only use TWRP booted).
Click to expand...
Click to collapse
I forgot to mention that i run this command before install magisk patched boot.img
Code:
adb pm shell magisk --remove-modules
I didn't have TWRP installed on my device, don't seem to have TWRP for Pixel 3 on android 11.
DaddyTony said:
Sorry but i don't think Pixel 3 have Teamwin (TWRP) support of android 11?
Click to expand...
Click to collapse
Theres no TWRP support of my Pixel 2 XL either, but it works
We just dont install it, we fastboot to it
73sydney said:
Theres no TWRP support of my Pixel 2 XL either, but it works
We just dont install it, we fastboot to it
Click to expand...
Click to collapse
Just tried boot into TWRP img, failed. It just says:
Code:
FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
Googled it & find out TWRP's a deprecated/no longer recommended way to install Magisk. And according to John Wu's installation instruction, it is no longer supported in modern models.
Due to this reason, we no longer recommend installing Magisk through custom recoveries on modern devices.
Click to expand...
Click to collapse
BTW he also said the "patch image" method is guaranteed to work 100% lol, should we let him know hhh
--------------------
edit:
Just find out Pixel 3 (blueline) has **NO** official support of TWRP v3.4+, but Pixel 3 XL (crosshatch) has it. How ironic.
and I wonder if TWRP v3.4+ support android 11?
DaddyTony said:
Just tried boot into TWRP img, failed. It just says:
Code:
FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
Googled it & find out TWRP's a deprecated/no longer recommended way to install Magisk. And according to John Wu's installation instruction, it is no longer supported in modern models.
BTW he also says the "patch image" method is guaranteed to work 100% lol, should we let him know hhh
Click to expand...
Click to collapse
Hmmm, disappointing
Ive literally tried the image patch method once, a lot of faffing about, I always use the TWRP method, easy peasy at least for older device
....we no longer recommend installing Magisk through custom recoveries on modern devices. The custom recovery installation method exists mostly for legacy support.
Download the Magisk installer zip
Reboot to custom recovery
Flash the zip and reboot
Check whether Magisk Manager is installed. If it isn’t installed automatically, manually install the APK.
Click to expand...
Click to collapse
Guess ill be happy to remain a legacy device user
This saved my day:
Code:
fastboot --set-active=b
You might need to use "a" instead.
In my case the kernel was loaded and started and Android startup was hanging.
I guess we have to wait until this is fixed.
Edit: Pixel 3a XL, latest Android 11
Hey all, i have a pixel 2 XL and I'm also stuck in bootloop. However i can't find how to do a factory reset. Could you help me?
polyxn said:
Hey all, i have a pixel 2 XL and I'm also stuck in bootloop. However i can't find how to do a factory reset. Could you help me?
Click to expand...
Click to collapse
Which version of Android?
Do you have TWRP installed?
If you do people have been posting that going to Advanced, then tapping Fix Bootloop may work
Otherwise find the boot image of the ROM you have installed, and flash that to the device
If youre on Android 11 on the Pixel, as i found out myself via bootloop, do NOT install TWRP, just fastboot to it to flash zips
M66B said:
This saved my day:
Code:
fastboot --set-active=b
You might need to use "a" instead.
In my case the kernel was loaded and started and Android startup was hanging.
I guess we have to wait until this is fixed.
Edit: Pixel 3a XL, latest Android 11
Click to expand...
Click to collapse
I used this command (and tried to boot in slot a), the patched img still won't boot.
Did you managed to flash Magisk with patched boot file?
[UPDATE/KEEP ROOT GUIDE] OCT 2020 (RP1A.201005.004) "FLAME" Magisk/Stock Boot Images
IF YOU ARE STILL ON AUGUST (ANDROID 10/Q) BUILD, PLEASE FOLLOW THE SEPTEMBER GUIDE (click here) FIRST! AND READ ALL WARNINGS AND ADDITIONAL INFO IN FIRST 2 POSTS!
PLEASE NOTE: I STILL HAVE NOT UPDATED TO ANDROID 11 YET, SO PLEASE FLASH AT YOUR OWN RISK AS ASSISTANCE FROM ME WILL BE VERY LIMITED. PLEASE BE KIND TO ONE ANOTHER AND HELP EACH OTHER OUT!
PLEASE DROP A THANKS IF YOU STILL FIND THESE GUIDES HELPFUL! :good:
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 "FLAME" ONLY, NOT PIXEL 4 XL "CORAL"!!
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: https://twitter.com/topjohnwu/status/1272136975022084097?s=19
ALL FILES BELOW ARE FOR "RP1A.201005.004, Oct 2020"!
Magisk Canary v21.0 Patched Boot Image: https://www.androidfilehost.com/?fid=10763459528675562385
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=10763459528675562112
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=10763459528675562113
[SAFETYNET INFO]: Again, I'm not updating myself yet, so I'm not sure about this. I will update this info as others report back. On Android 10, using the MagiskHide Props Config module (or an alternate module created by Displax, though I prefer Didgeridoohan's module) and choosing option 2 - Force BASIC key attestation would force BASIC HW attestation and allow SafetyNet to pass again. This works perfectly for me, and I even run additional mods including EdXposed. I'm not sure if this works on Android 11, and I won't be able to confirm myself for a while. If anybody tries it, please let me know and I'll update this section. The module and info on using it can be found here: https://forum.xda-developers.com/ap...just search for it in the Magisk Manager app.
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "11.0.0 (RP1A.200720.009, Sep 2020)". But the general idea is the same for other builds, you just need the correct files for your device.
flame-rp1a.200720.009-factory-dtbo.img: https://www.androidfilehost.com/?fid=10763459528675562111
flame-rp1a.200720.009-factory-boot.img: https://www.androidfilehost.com/?fid=10763459528675562110
September 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/flame-ota-rp1a.201005.004-9e17c7b4.zip
DO NOT BOOT BACK INTO O/S UNTIL ALL STEPS ARE COMPLETED - THIS ENSURES EVERYTHING BOOTS BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot flame-rp1a.200720.009-factory-boot.img
3. fastboot flash dtbo flame-rp1a.200720.009-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload flame-ota-rp1a.201005.004-9e17c7b4.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot flame-rp1a.201005.004-magisk_patched-21.0.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)
This is a 100% seamless update that requires no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
-------------------
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
just want to report happily that i waas able to update to october with no problems using your guide. followed your september guide yesterday and then october today. no problems at all, buttery smooth mate! thanx..!
The instructions are great as a reminder,
I only work on the console every month or two and without the bullet points I wouldn't always be able to finish the update so quickly.
Thank you very much ?
So.. I've rooted and taken OTA's and rerooted dozens of times.. But I finally got around to factory resetting now stable is here. On OCT build, i flash the patched boot img and upon rebooting, Magisk shows I'm still not rooted. Any advice?
Update: Flashed canary debug apk. patched stock boot img, and flashed. now rooted. wierd
What about if I'm not rooted and on the October update for Android 11? I've tried a couple different times to root and I always get a fail when I try to flash the patched boot image.
Hey,
here is a quick guide:
=== you need these websites ===
https://developers.google.com/android/images
https://developers.google.com/android/ota
https://github.com/topjohnwu/magisk_files/tree/canary
step by step
1. download https://github.com/topjohnwu/magisk_files/archive/canary.zip
that's Magisk
2. copy app-debug.apk on your Pixel 4 (XL) and install the app
3. Open an Image (NOT OTA!) with 7-zip, there is another big zip-file inside, extract boot.img and dtbo.img
4. Copy boot.img on your Phone, download-folder, just like Magisk.apk
5. Open Magisk and Patch boot.img -> magisk-patched.img
6. Copy magisk-patched.img on your PC
7. now simply proceed as described in the instructions above.
Nothing can go wrong with these self-patched files
i5lee8bit said:
8. fastboot flash boot flame-rp1a.201005.004-magisk_patched-21.0.img
Click to expand...
Click to collapse
Hey guys, novice rooter here:
Can someone explain this step to me? Where do I get this file from if im on the beta version of Magisk?
Fwaiiiz said:
Hey guys, novice rooter here:
Can someone explain this step to me? Where do I get this file from if im on the beta version of Magisk?
Click to expand...
Click to collapse
load canary magisk apk: https://github.com/topjohnwu/magisk_files/blob/canary/app-debug.apk and install, then update magisk in the app
go to: https://developers.google.com/android/images
read
and download factory image for your pixel phone - 11.0.0 (RP1A.201105.002, Nov 2020) is last image for flame https://dl.google.com/dl/android/aosp/flame-rp1a.201105.002-factory-351561c6.zip
unzip the image, and you get another zip file: image-flame-rp1a.201105.002.zip
unzip image-flame-rp1a.201105.002.zip and you get a file named boot.img
copy boot image to your phone
patch boot image with magisk - you have made the magisk patch yourself ? now copy the magisk-patched.img from your phone to your pc, that's the file you ask for, but for the November Update
I hope you can now Update all you want
(Problems I had when attempting a "dry" flash and patch:)
Just got the phone today (November 18) then attempted to flash the boot.img after patching it with magisk manager (after magisk patches the boot.img it renames it to "magisk_patched.img"). Got the usb debugging authorized after updating my adb drivers. If you want to make sure your phone is authorized you may need to run commands: adb kill-server and adb devices to check and stop/restart adb.
Anyone able to get it flashed? Getting error:
Code:
FAILED (remote: Failed to write to partition Not Found)
after running
Code:
fastboot flash boot magisk_patched.img
from fastboot, bootloader is unlocked. Running version
Code:
bramble-rd1a.200810.022.a4 (October)
I'd recommend patching up to the November update: Settings, System, System Update to the newest November update (11.0.0 (RD1A.201105.003.C1, Nov 2020).
EDIT: I'd recommend installing 15 second ADB https://forum.xda-developers.com/showthread.php?t=2588979, then overwriting it with the newest adb tools from google. 15 second ADB will add the ADB folder to your system's PATH (ENVIRONMENT VARIABLES) allowing you to run adb commands from any folder (not just the folder adb resides in).
Ok, updating to usb_driver_r13-windows.zip and platform-tools_r30.0.5-windows.zip and updating the build to the Nov RD1A.201105.003.C1 will report back lol
EDIT 2: So yeah, update your drivers and platform tools, successfully patched it:
Code:
fastboot flash boot magisk_patched.img
OUTPUT:
Code:
Sending 'boot_b' (98304 KB) OKAY [ 2.310s]
Writing 'boot_b' OKAY [ 0.480s]
Finished. Total time: 3.122s
How to flash and patch:
https://www.xda-developers.com/google-pixel-4a-how-to-unlock-bootloader-root-pass-safetynet/
Prerequisites:
Download the applicable factory image https://developers.google.com/android/images The Pixel 4A 5G is codenamed "Bramble" (Pull down your shade or look in Settings, "About phone" for Build number) and extract the boot.img from factory image, then transfer it to phone and patch it with magisk manager:
Open Magisk manager -> select ‘Install’ -> ‘Select and Patch File’ -> select your boot.img file
The patched boot image should be found inside your Download folder
After magisk patches it, mount your phone's storage, copy to your computer and flash it from fastboot. Hold down the Power and Volume Down buttons to enter fastboot.
Run command
Code:
fastboot flash boot magisk_patched.img
Platform Tools (includes ADB)
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Usb Drivers
https://dl.google.com/android/repository/usb_driver_r13-windows.zip?hl=ru
Magisk
Direct Link https://github.com/topjohnwu/Magisk/releases/download/v21.1/Magisk-v21.1.zip
Direct Link https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.3/MagiskManager-v8.0.3.apk
Magisk Releases page (in case of an update to magisk or magisk manager) https://github.com/topjohnwu/Magisk/releases/
VIPER4Android (great Digital Signal Processor)
I have been struggling with getting Viper4Android installed.
Stop-gap here:
I flashed this one, but it's distorting my external speakers and is buggy, but it does process...so BE CAREFUL. This will get you there until a more stable version is out. And the video was just taken down. All you have to do is flash it with Magisk here's a link:
https://drive.google.com/file/d/17-NTL0miBYzk4o4v26MstAL9lOPXF3GN/view?usp=sharing
AdAway (system-wide ad blocking)
tried version 5.10 with no luck, let me know if it works for you.
AdAway 4.34 working for me on Android 11.0.0 (RD1A.201105.003.C1, Nov 2020)
Here: https://f-droid.org/repo/org.adaway_40304.apk
AdAway 4.36 (haven't tested)
https://f-droid.org/repo/org.adaway_40306.apk
Make sure to enable "Systemless Hosts" in Magisk Manager before attempting to enable ad-blocking. It's under Settings (the cog/gear in the top right) in the Magisk section.
Good luck all!
Good to see someone working on this. My phone won't be here until tomorrow.
The last time I had trouble flashing, I wasn't running the canary build of Magisk.
Thanks for info and reply on other thread...long time I use this stuff haha
I'm seeing install fail from magisk when I try to patch image .I'm on latest November build
View attachment 5138555
After successfully fastboot unlocking, when I try to patch my boot.img I get the following error from Magisk:
Code:
-Device platform: arm64-v8a
- Copying image to cache
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
! Installation failed
- Repacking boot image
! Unable to repack boot image!
I first tried using the Australian factory image, labelled "11.0.0 (RD1A.201105.003.A1, Nov 2020, AU carriers)" and got the above error.
Then I tried with the Australian + Japan factory image, labelled "11.0.0 (RD1A.200810.020, Oct 2020, AU & JP carriers)" and got the same error.
What fixed it was switching to the BETA update channel in Magisk manager.
Once I changed to the BETA channel I saw in the changelog that they added support for a new boot.img format used by Pixel 5 and Pixel 4a 5G.
Anyone who ends up here from Google, swap to the beta update channel in Magisk manager .
andrew207 said:
After successfully fastboot unlocking, when I try to patch my boot.img I get the following error from Magisk:
Code:
-Device platform: arm64-v8a
- Copying image to cache
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
! Installation failed
- Repacking boot image
! Unable to repack boot image!
I first tried using the Australian factory image, labelled "11.0.0 (RD1A.201105.003.A1, Nov 2020, AU carriers)" and got the above error.
Then I tried with the Australian + Japan factory image, labelled "11.0.0 (RD1A.200810.020, Oct 2020, AU & JP carriers)" and got the same error.
What fixed it was switching to the BETA update channel in Magisk manager.
Once I changed to the BETA channel I saw in the changelog that they added support for a new boot.img format used by Pixel 5 and Pixel 4a 5G.
Anyone who ends up here from Google, swap to the beta update channel in Magisk manager .
Click to expand...
Click to collapse
Thanks for info ..I changed to beta but still having issues patching boot IMG..is this correct Magisk
{
"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"
}
Do you have a custom recovery installed? I'm trying to figure out how to install Magisk, but I can't find a custom recovery, neither TWRP nor ClockworkMod.
WhiteAsIce said:
Do you have a custom recovery installed? I'm trying to figure out how to install Magisk, but I can't find a custom recovery, neither TWRP nor ClockworkMod.
Click to expand...
Click to collapse
There's no custom recovery. You need to fastboot flash a patched boot.img as described in this guide: https://www.xda-developers.com/googl...ass-safetynet/ using the links from the OP.
Just make sure you're using the latest platform tools, download the matching factory image and change magisk manager to "beta mode" before patching the boot.img.
Android 10 and TWRP
Simma said:
There's no custom recovery. You need to fastboot flash a patched boot.img as described in this guide: https://www.xda-developers.com/googl...ass-safetynet/ using the links from the OP.
Just make sure you're using the latest platform tools, download the matching factory image and change magisk manager to "beta mode" before patching the boot.img.
Click to expand...
Click to collapse
WhiteAsIce said:
Do you have a custom recovery installed? I'm trying to figure out how to install Magisk, but I can't find a custom recovery, neither TWRP nor ClockworkMod.
Click to expand...
Click to collapse
More information on Android 10 and TWRP, though there are some devices slowly getting support for TWRP. Haven't heard clockworkmod in a long time.
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
lmt1979 said:
[...]
Adaway (system-wide ad blocking)
tried version 5.10 with no luck, let me know if it works for you.
Adaway 4.34 working for me on Android 11.0.0 (RD1A.201105.003.C1, Nov 2020)
Here: https://f-droid.org/repo/org.adaway_40304.apk
Adaway 4.36 (haven't tested)
https://f-droid.org/repo/org.adaway_40306.apk
Make sure to enable "Systemless Hosts" in Magisk Manager before attempting to enable ad-blocking. It's under Settings (the cog/gear in the top right) in the Magisk section.
[...]
Click to expand...
Click to collapse
Got v5.1.0 (from F-Droid) working properly with Magisk running with systemless hostfile. Try installing BusyBox (i have v1.32.0 installed) to '/system/bin', which will be used by Adaway (instead of running native commands on root level, which apparently cause the issue).
I can't seem to flash version of Viper in Magisk, it won't let me. I've also tried every combination of the latest viper versions, and their settings, and nothing will run. Perhaps it will on the next version of Magisk. I had posted in the Magisk forum, and none of the suggestions helped.
If anyone has any luck, let us know!
mmarcz said:
I can't seem to flash version of Viper in Magisk, it won't let me. I've also tried every combination of the latest viper versions, and their settings, and nothing will run. Perhaps it will on the next version of Magisk. I had posted in the Magisk forum, and none of the suggestions helped.
If anyone has any luck, let us know!
Click to expand...
Click to collapse
The linked version worked for me after trying the magical downloaded version. I had the audio modification library and audio compatibility modules installed. I don't remember the exact sequence bit all I have now is the posted module l.
It does have some odd issues with file storage. I can save a new preset but putting my old one in the viper folder in internal storage doesn't work. I also can't rename or delete presets. I ended up having to go to /root/storage/self/primary which seems to be internal storage by another path. Pasting my presets in that viper folder worked. No idea how systemless works so can't even guess what's going on.
mmarcz said:
I can't seem to flash version of Viper in Magisk, it won't let me. I've also tried every combination of the latest viper versions, and their settings, and nothing will run. Perhaps it will on the next version of Magisk. I had posted in the Magisk forum, and none of the suggestions helped.
If anyone has any luck, let us know!
Click to expand...
Click to collapse
Just flash the https://drive.google.com/file/d/17-NTL0miBYzk4o4v26MstAL9lOPXF3GN/view?usp=sharing with Magisk. Choose "Modules" the right option on the bottom https://drive.google.com/file/d/1BWLVPtypCjCiqUSEHiRc8sCuMtjqKdY5/view?usp=sharing
lmt1979 said:
Just flash the https://drive.google.com/file/d/17-NTL0miBYzk4o4v26MstAL9lOPXF3GN/view?usp=sharing with Magisk. Choose "Modules" the right option on the bottom https://drive.google.com/file/d/1BWLVPtypCjCiqUSEHiRc8sCuMtjqKdY5/view?usp=sharing
Click to expand...
Click to collapse
Thank you!!!!! Works as advertised!!!!
This was 75% of the reason I bought a pixel!!!
I'm so happy this morning, you have no idea.
It was even processing Amazon music, which didn't work before, so far so good. I only had a chance to listen in the car for 5mins this morning.
mmarcz said:
Thank you!!!!! Works as advertised!!!!
This was 75% of the reason I bought a pixel!!!
I'm so happy this morning, you have no idea.
It was even processing Amazon music, which didn't work before, so far so good. I only had a chance to listen in the car for 5mins this morning.
Click to expand...
Click to collapse
If it stops processing, long press on the icon on the desktop, select App info, Force Stop and reopen and it'll usually start up again. I had to do this much more often on my Pixel 3 than I have on the 4A 5G.
I've followed the steps posted above. Flashed the Drive file in magisk but I'm still getting abnormal status, audio format unsupported. Tips?
VerneVerne said:
I've followed the steps posted above. Flashed the Drive file in magisk but I'm still getting abnormal status, audio format unsupported. Tips?
Click to expand...
Click to collapse
If you're sure you're rooted, some people have noted they needed to use/install Audio Modification Library and possibly Busybox. I'd attempt to clear the cache on Magisk and Viper4Android, as well.
I am on the November build and did not need Audio Modification Library, audio compatibility module (Magisk) or Busybox. I'm using Magisk 21.1 (21180) and Magisk Manager 8.0.3 (314)(14). There's a "puzzle piece" on the far right of the new Magisk Manager menu that has "Install from Storage", this is where I pointed to the Viper.zip and flashed it.
lmt1979 said:
If you're sure you're rooted, some people have noted they needed to use/install Audio Modification Library and possibly Busybox. I'd attempt to clear the cache on Magisk and Viper4Android, as well.
I am on the November build and did not need Audio Modification Library, audio compatibility module (Magisk) or Busybox. I'm using Magisk 21.1 (21180) and Magisk Manager 8.0.3 (314)(14). There's a "puzzle piece" on the far right of the new Magisk Manager menu that has "Install from Storage", this is where I pointed to the Viper.zip and flashed it.
Click to expand...
Click to collapse
Tried all the above. No luck though. I remember it being very finicky on my pixel 3. I'll try again when I'm not actually at work. Thanks for the help though
VerneVerne said:
Tried all the above. No luck though. I remember it being very finicky on my pixel 3. I'll try again when I'm not actually at work. Thanks for the help though
Click to expand...
Click to collapse
I've been glhaving issues too after it worked for awhile. Couldn't deal with no presets thing so tried different Magisks, etc with no luck and now it won't process. I'll update if I find something.
EDIT: the module at https://zackptg5.com/android.php#viper works if run in legacy mode.
EDIT AGAIN: can't save presets for some reason with above module but the ViperFX XDA Labs release before the most current one works in legacy mode https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
VerneVerne said:
I've followed the steps posted above. Flashed the Drive file in magisk but I'm still getting abnormal status, audio format unsupported. Tips?
Click to expand...
Click to collapse
You need to go into the settings for the app force stop it and then reopen it.
lmt1979 said:
You need to go into the settings for the app force stop it and then reopen it.
Click to expand...
Click to collapse
I've already tried. Started from scratch. Still unsupported status.
Edit: after reading somewhere on here that if you use legacy mode it will process. Followed all steps, set it to legacy and now it works. Thank you everyone