A: After digging into the SuperSu script I found the culprit. The script that was being called during the "ramdisk patch" part wasn't working. I deleted it, which got readded during a new install of the SuperSu and it worked.
Q:I'm trying to install systemless supersu and it's failing after "Calling user ramdisk patch script". I suspect I might need to reinstall the boot.img as I uninstalled magisk and I think it tweaked it. Is the stock one available somewhere?
Thanks
Just download any incremental update zip to the version you need (ex. if you need the 3.2.7 boot img, download the 3.2.6 to 3.2.7 zip) and flash the boot.img inside the zip.
Great, thanks for the help! I'll try that out.
Hi, just wondering, which scripts did you delete from SuperSU? I'm having the same problem :/
Delete /data/custom_ramdisk_patch.sh to fix it.
Related
I've updated with the OTA from H14 to H15. I restored the stock recovery beforehand and the update went without Problems.
Before starting the update I tried to "unroot" which also was stated neccessary by SuperSU in two dialogs. But this failed and might be the origin of the problem.
Afterwards SuperSU could not find the su binary so I tried to flash it via TWRP 3.0.2.0 which failed after the line "creating ramdisk backup".
Next I tried to dirty flash the H15 Rom, which also went without problems, but the SuperSU install failed at the same point.
I've attached the logfile of the aroma installer, containing the superSU logfile.
The phone works for the moment, without root / superSU but I would like to have it back
Does anyone have an idea / need more informations / can otherwise help ?
Henry
How to install Magisk & Xposed? I keep getting bootloops.. "no digest file found"
So I have a Pixel XL, stock, nougat 7.1.2 (Aug NHGE47Q).
I have tried the following steps:
Boot TWRP 3.1.1-1
Flash TWRP 3.1.1-1
Flash Elemental 7.1.2 kernel
Flash newest Magisk 14.5 beta (since 14.0 doesn't support pixel, right?)
Flash TWRP 3.1.1-1
What am I doing wrong?
I tried it a few times and no good. I did notice it says something about "no digest file found", which I assume is the problem.. ? I tried a combination of things like with and without wiping cache/dalvik. Or not flashing TWRP at the end. I search around and couldn't find updated instructions on this process. Help will be appreciated!
P.S. Also, if I update to Oreo, I can't get Xposed, right? (as in the systemless version via Magisk) because that's the only reason why I haven't updated yet.
smithilberry said:
So I have a Pixel XL, stock, nougat 7.1.2 (Aug NHGE47Q).
I have tried the following steps:
Boot TWRP 3.1.1-1
Flash TWRP 3.1.1-1
Flash Elemental 7.1.2 kernel
Flash newest Magisk 14.5 beta (since 14.0 doesn't support pixel, right?)
Flash TWRP 3.1.1-1
What am I doing wrong?
I tried it a few times and no good. I did notice it says something about "no digest file found", which I assume is the problem.. ? I tried a combination of things like with and without wiping cache/dalvik. Or not flashing TWRP at the end. I search around and couldn't find updated instructions on this process. Help will be appreciated!
P.S. Also, if I update to Oreo, I can't get Xposed, right? (as in the systemless version via Magisk) because that's the only reason why I haven't updated yet.
Click to expand...
Click to collapse
I'm not sure about Oreo I think you can but you can't get certain modules or things like Xposed but double check that cuz I'm not sure
Secondly if you wanna flash 14.2 or 14.3 at the bottom of the magisk post where you download it will have the different versions to choose from any version after 14.0 supports the pixel
try flashing magisk by itself and see if that helps I know when I flash it with anything else it just doesn't show up and doesn't work but if you want when it bootloops flash the uninstaller and flash your boot image and that will fix the bootloop but do it again copy the log from twrp and put it on your computer and upload it here it will say exactly where it fails and what's wrong with it so we can help better
smithilberry said:
So I have a Pixel XL, stock, nougat 7.1.2 (Aug NHGE47Q).
I have tried the following steps:
Boot TWRP 3.1.1-1
Flash TWRP 3.1.1-1
Flash Elemental 7.1.2 kernel
Flash newest Magisk 14.5 beta (since 14.0 doesn't support pixel, right?)
Flash TWRP 3.1.1-1
What am I doing wrong?
I tried it a few times and no good. I did notice it says something about "no digest file found", which I assume is the problem.. ? I tried a combination of things like with and without wiping cache/dalvik. Or not flashing TWRP at the end. I search around and couldn't find updated instructions on this process. Help will be appreciated!
P.S. Also, if I update to Oreo, I can't get Xposed, right? (as in the systemless version via Magisk) because that's the only reason why I haven't updated yet.
Click to expand...
Click to collapse
According to elementalx.org/devices/pixel/ the right elemental kernel is 1.15.
I've done this exact process too and ran into many issues, I would recommend as follows, I've had a lot of success with this. I got Magisk working under 14.2 , twrp 3.1.1-1 , and elemental 1.15. I could not get any of them working correctly with any other versions or in any other order - this worked for me.
reflash stock with flash_all and factory reset
fastboot boot twrp 3.1.1-1
check "never show" and swipe
adb sideload twrp-3.1.1-1.zip
adb sideload VerifiedBootSigner-v8.zip
reboot recovery
sideload again
adb sideload your new ROM here if you want that
adb sideload twrp-3.1.1-1 again, had to do this for PureNexus, cause recovery was overwritten
adb sideload VerifiedBootSigner-v8.zip again
reboot recovery
adb sideload ElementalX-P-1.15.zip
reboot recovery (might not be necessary)
adb sideload Magisk-v14.2(1420).zip - I got this from the Arise Aroma installer package in another thread
adb sideload VerifiedBootSigner-v8.zip again
reboot system, enable systemless hosts and magisk hide on google services framework and play store. magisk hide only works with a kernel that supports it so if your elemental is working you should be fine.
reboot again, then install busybox, I used stericsons from play store. I also installed the selinux switcher for permissive mode. I installed these to get Arise / Viper to work and I think they are required for xposed too.
Magisk modules should work from there, including the xposed installer, but xposed will cause safetynet to fail. I could not get magisk modules to work with 14.3, have not tested other versions, but 14.2 worked.
I did not let twrp install it's apk from recovery mode, or let magisk download it's update, I downloaded both APKs separately.
I remember having many issues with the order of install for magisk versus elemental. I'm pretty sure what worked for me is elemental, then magisk as I put here. but if you run into issues it might have to be magisk then elemental.
blanken_ship said:
According to elementalx.org/devices/pixel/ the right elemental kernel is 1.15.
I've done this exact process too and ran into many issues, I would recommend as follows, I've had a lot of success with this. I got Magisk working under 14.2 , twrp 3.1.1-1 , and elemental 1.15. I could not get any of them working correctly with any other versions or in any other order - this worked for me.
reflash stock with flash_all and factory reset
fastboot boot twrp 3.1.1-1
check "never show" and swipe
adb sideload twrp-3.1.1-1.zip
adb sideload VerifiedBootSigner-v8.zip
reboot recovery
sideload again
adb sideload your new ROM here if you want that
adb sideload twrp-3.1.1-1 again, had to do this for PureNexus, cause recovery was overwritten
adb sideload VerifiedBootSigner-v8.zip again
reboot recovery
adb sideload ElementalX-P-1.15.zip
reboot recovery (might not be necessary)
adb sideload Magisk-v14.2(1420).zip - I got this from the Arise Aroma installer package in another thread
adb sideload VerifiedBootSigner-v8.zip again
reboot system, enable systemless hosts and magisk hide on google services framework and play store. magisk hide only works with a kernel that supports it so if your elemental is working you should be fine.
reboot again, then install busybox, I used stericsons from play store. I also installed the selinux switcher for permissive mode. I installed these to get Arise / Viper to work and I think they are required for xposed too.
Magisk modules should work from there, including the xposed installer, but xposed will cause safetynet to fail. I could not get magisk modules to work with 14.3, have not tested other versions, but 14.2 worked.
I did not let twrp install it's apk from recovery mode, or let magisk download it's update, I downloaded both APKs separately.
I remember having many issues with the order of install for magisk versus elemental. I'm pretty sure what worked for me is elemental, then magisk as I put here. but if you run into issues it might have to be magisk then elemental.
Click to expand...
Click to collapse
Thanks for the directions!
However, before I try this, I have one question... what is "VerifiedBootSigner-v8.zip"?
After searching, I see a bunch of information on the May security patch, but nothing talking about the August security patch (which is what I'm on). That being said, does it still apply?
You don't need Xposed, magisk has plenty of modules, but after rooting, flash the verified boot signer to allow for stock boot. It patches the boot image. Android 8 methods fixed this issue
Here is how you flash a kernel with the stupid 2 slots LOL...
Rom installed and ALREADY BOOTED INTO the OS That rom.
Reboot to TWRP 3.2.1-0
Flash Kernel and Flash TWRP 3.2.1-0.ZIP followed by rebooting recovery (i usually hit reboot system hold volume down until i get to bootloader and then choose recovery (reboot recovery doesnt always work))
Flash Magisk 15.0 or 15.1 on Oreo and i believe 14.3 and down will work better for Nougat.
Reboot buddy!!! All is good in the world.
Mikkey81 said:
Here is how you flash a kernel with the stupid 2 slots LOL...
Rom installed and ALREADY BOOTED INTO the OS That rom.
Reboot to TWRP 3.2.1-0
Flash Kernel and Flash TWRP 3.2.1-0.ZIP followed by rebooting recovery (i usually hit reboot system hold volume down until i get to bootloader and then choose recovery (reboot recovery doesnt always work))
Flash Magisk 15.0 or 15.1 on Oreo and i believe 14.3 and down will work better for Nougat.
Reboot buddy!!! All is good in the world.
Click to expand...
Click to collapse
WAAAAAAIIIIIT!!!! you need to be on Magisk 15.0 just failed multiple times and realized that was the last thing I Updated to 15.1..
Make sure you're flashing 15.0.
Can we get Xposed yet on Oreo with Magisk? I see it says there are 4 different options available in the module section of Magisk. One is labeled "Xposed framework". All the others are labeled "Xposed Framework SDK 25" down to 19. Which one should be used for Oreo?
I'm on the global rom. Twrp works fine but the moment I install magisk v19.3 or v19.2 my phone bootloops to twrp
Any ideas? I can run magisk uninstaller and it resolves the bootloop.
Have you tried flashing no-verity-force-encrypt zip? It sometimes helps. I often flash it, just to be save. I have no clue what it does but sometimes it helps haha
It's caused by some Magisk module. I had the same problem when I installed ViperFX. Uninstall Magisk, install it again and then try to install modules one by one to find which one is causing the bootloops.
Don't just install uninstall. It only getting you to twrp after installing magisk. Try magisk manager recovery, you can google it and remove all modules you have after installing magisk. You can reboot and install your module again afterwards.
I havent installed any modules. It's a clean install of magisk. I get a popup asking "requires additional Setup".
If I let that run, it reboots after the Setup. And I'm left with it bootlooping.
Again, no modules installed.
How do you install Magisk to get this popup? Is it the direct install from Magisk manager?
I always install the zip in TWRP. Maybe that will solve your problem if you didn't try this method already.
The other fix could be the zip file mentioned by shisaya24. I used to install it on my previous phone to fix bootloops.
maciek90 said:
How do you install Magisk to get this popup? Is it the direct install from Magisk manager?
I always install the zip in TWRP. Maybe that will solve your problem if you didn't try this method already.
The other fix could be the zip file mentioned by shisaya24. I used to install it on my previous phone to fix bootloops.
Click to expand...
Click to collapse
I install via twrp.
Hello, this morning I found my poco f3 updated to Miui 12.5.3.0 (I was on 12.5.0.0) even though I had automatic updates disabled. After the automatic update I lost my root via magisk and twrp in recovery. No problem, I got twrp installed again, then I proceeded to install magisk v23.0 from TWRP, as I had done after 12.5.0.0. update.
Afterwars phone is stuck in a bootloop. I reflashed stock boot image, recovering the phone, but I ave been unable to install magisk in 12.5.3.0, I tried copying boot.img to the phone, then using magisk manager to patch the boot image, then flash the patched image trough fastboot, with the same result.
Anyone knows how to make magisk work in this new update?
Thank you
suloku said:
Hello, this morning I found my poco f3 updated to Miui 12.5.3.0 (I was on 12.5.0.0) even though I had automatic updates disabled. After the automatic update I lost my root via magisk and twrp in recovery. No problem, I got twrp installed again, then I proceeded to install magisk v23.0 from TWRP, as I had done after 12.5.0.0. update.
Afterwars phone is stuck in a bootloop. I reflashed stock boot image, recovering the phone, but I ave been unable to install magisk in 12.5.3.0, I tried copying boot.img to the phone, then using magisk manager to patch the boot image, then flash the patched image trough fastboot, with the same result.
Anyone knows how to make magisk work in this new update?
Thank you
Click to expand...
Click to collapse
Try flashing the older patched boot.img on the new stock firmware.
On the 12.5.3.0 ill patched boot.img from 12.5.1.0 and all right.
Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended
i have the same issue of auto updated and lost my root access.
Which boot.img I should Magish'd to get the root access again?
Currently installing my twrp
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
if Flash Current TWRP fails, go to Backup > Refresh Sizes and try Flash Current TWRP again
Click to expand...
Click to collapse
Currently at the Resizing stage
Edit 1: failed, I have the error bootctrl error that prevent me from installing after resizing.
I have flashed the twrp3.5.2 directly to boot resulting in bootloop and needed to install the Boot.img from the 12.5.1 from the previous bulit
Edit: actually I can ignore that error.
Magisk installed but safety checked failed even I have the "universal safety check module installed "
Also the app thoax isn't working
I'd try removing all magisk modules, installing stock 12.5.3, then using magisk apk to create patched boot.img and flash it with fastboot (fastboot flash boot magisk_boot_patched.img)
Also, maybe try flashing bot boot_a and boot_b? I had a problem were my active boot partition changed and phone became even more broken.
suloku said:
Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
Might wanna also uncheck Automatic system updates in the Developer settings to be safe.
suloku said:
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
There is a setting in the Xiaomi system updater that had by default checked auto-update. That setting need to be disabled/unchecked as well.
Since you have root with Magisk, can also Force stop or debloat the updater app, so the system will not update itself.
suloku said:
Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
I had the same issue on Redmi Note 9 Pro (joyuse). Based on your tip I've removed some modules from `data/adb/modules` and my device is finally booting normally. Thanks!
So, I accidentally uninstalled Magisk Manager after rooting the phone. I read somewhere on GitHub that Magisk hard-codes something (App ID?) into the boot image which is later installed.
So my question is, can I install Magisk Manager again, then patch the image, flash the image again without corrupting something?
Thanks in advance!
If you patched yout boot.img, you can install Magisk Manager again from github.
RheinPirat said:
If you patched yout boot.img, you can install Magisk Manager again from github.
Click to expand...
Click to collapse
Thanks!
That works without re-flashing the boot.img?
Yes. Because you have already patched and flashed the boot.img. The boot image is patched untill you flash a stock boot.img.
You can factory reset and delete the app as much as you want, it will not be effective at getting rid of root. So nothing to worry about