Related
Hello, so I decided to reflash my ROM because I kept running into issues, and I didn't uninstall Magisk before doing so.
Then when I tried flashing Magisk it showed me error 1. Flashing the uninstaller gives the same error. Magisk Manager shows that it is not installed, Root Checker states that the device is unrooted, and so far the only app that mentioned my phone being rooted is LastPass.
What can I possibly do to reinstall Magisk so it's back on my device in its full grace?
I checked other posts and either they are not related to my problem or didn't help
Phone: Xiaomi Redmi Note 4 Snapdragon, Recovery: official TWRP non-treble, ROM: latest build of official AOSP Extended
Maybe try dirty flashing and flashing Magisk again?
Not Sally when Magisk is already installed, I can flash it again with no problem. Weird that you're having these issues. ?
LennyTheCat said:
Hello, so I decided to reflash my ROM because I kept running into issues, and I didn't uninstall Magisk before doing so.
Then when I tried flashing Magisk it showed me error 1. Flashing the uninstaller gives the same error. Magisk Manager shows that it is not installed, Root Checker states that the device is unrooted, and so far the only app that mentioned my phone being rooted is LastPass.
What can I possibly do to reinstall Magisk so it's back on my device in its full grace?
I checked other posts and either they are not related to my problem or didn't help
Phone: Xiaomi Redmi Note 4 Snapdragon, Recovery: official TWRP non-treble, ROM: latest build of official AOSP Extended
Click to expand...
Click to collapse
Did you wipe everything? Wipe system and data before re flashing your rom.
@LennyTheCat To be absolutely sure what's going on you're going to have to provide the recovery log, saved after you've attempted you flash Magisk.
madbat99 said:
Did you wipe everything? Wipe system and data before re flashing your rom.
Click to expand...
Click to collapse
Yes I did
Didgeridoohan said:
@LennyTheCat To be absolutely sure what's going on you're going to have to provide the recovery log, saved after you've attempted you flash Magisk.
Click to expand...
Click to collapse
Will provide later now I have stuff to do
@Didgeridoohan here's the log file
LennyTheCat said:
@Didgeridoohan here's the log file
Click to expand...
Click to collapse
Try updating your TWRP. That has solved "cannot mount vendor" for other Mido users.
https://forum.xda-developers.com/search/forum/5903?query=mido cannot mount vendor
Didgeridoohan said:
Try updating your TWRP. That has solved "cannot mount vendor" for other Mido users.
https://forum.xda-developers.com/search/forum/5903?query=mido cannot mount vendor
Click to expand...
Click to collapse
well, it has installed no problem, but then my phone got stuck in a bootloop after rebooting. I have to reflash everything now, will tell if it worked later
@Didgeridoohan when I install Magisk, the phone keeps running into bootloops. Clean install of the ROM and Gapps seems to work fine. Tried 16.0 and 16.4 packages
LennyTheCat said:
@Didgeridoohan when I install Magisk, the phone keeps running into bootloops. Clean install of the ROM and Gapps seems to work fine. Tried 16.0 and 16.4 packages
Click to expand...
Click to collapse
Well... You're using a Treble ROM, right? So I'm assuming you're using a Treble modified Magisk version (since there's no official Treble support in Magisk yet)... If not, I'm sure you can find the relevant information in your ROM's thread.
Always go to the source...
Didgeridoohan said:
Well... You're using a Treble ROM, right? So I'm assuming you're using a Treble modified Magisk version (since there's no official Treble support in Magisk yet)... If not, I'm sure you can find the relevant information in your ROM's thread.
Always go to the source...
Click to expand...
Click to collapse
I decided to flash Lineage OS and then I flashed the Magisk package included in the post. Now it's working all squeaky and shiny. Thanks for help anyway
I'm doing a clean install of this rom on my Samsung S4 using the Aroma installer (Note: problem not related to aroma - see edits below).
The installer has an option to use Privacy Guard (for phones with a locked bootloader), SuperSU, or Magisk.
If I install Magisk, the phone is stuck at the Samsung logo indefinitely. If I choose either of the other options, it boots fine.
I've tried a number of different ways around this:
1. Choosing the Magisk option in the Aroma installer.
2. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.0 afterwards.
3. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.0 with the updater-script modified (commenting out the two lines) afterwards.
4. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.6 afterwards.
5. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.6 with the updater-script modified (commenting out the two lines) afterwards.
All of the above options - every way I can think of - results in bricking the device.
Is there a way to make this work?
Edit:
1. I'm using TWRP 3.1.1.0, if it matters. And yes, my S4 has an unlocked bootloader (MDL).
2. The phone will boot fine if I choose the Aroma SuperSU option, but I discovered that SuperSU is not installing correctly either. It just doesn't brick my phone.
3. I tried running the NON-aroma rom installer. Then I used UnSU to remove the non-functioning SuperSU, and ran the Magisk 16.0 installer (normal one). Bricked.
Rebooted into recovery, ran the Magisk Uninstaller - it failed, saying "Magisk is not installed".
So I tried installing Magisk again - which installed with no errors. And then I immediately ran the uninstaller, and again it failed, saying that Magisk was not installed. Maybe that's a clue as to what's going on. Because it's clearly not related to the aroma installer anymore.
4. I added the recovery log. This shows me doing a wipe, installing the rom linked to above, flashing Magisk, then flashing the Magisk uninstaller so you can see it say that Magisk was never installed in the first place.
I've been having zero luck getting this to work. Does anyone have any ideas?
Maybe you should read this, https://forum.xda-developers.com/ap...7-universal-systemless-t3473445/post77014053, sounds like the issue you're having and apparently Armoa breaks Magisk install. Also go to general support thread and post logs, etc. You will get more help there.
yung40oz84 said:
Maybe you should read this, https://forum.xda-developers.com/ap...7-universal-systemless-t3473445/post77014053, sounds like the issue you're having and apparently Armoa breaks Magisk install. Also go to general support thread and post logs, etc. You will get more help there.
Click to expand...
Click to collapse
Thank you. However, as I stated above, although I started with the aroma installer, I eventually tried the non-aroma installer and had the exact same problem.
In addition, I also tried the normal versions as well as ones that had been patched as per the instructions on the link you posted.
So whatever is causing this does not appear to be aroma related.
Haphim said:
So I tried installing Magisk again - which installed with no errors. And then I immediately ran the uninstaller, and again it failed, saying that Magisk was not installed. Maybe that's a clue as to what's going on. Because it's clearly not related to the aroma installer anymore.
Click to expand...
Click to collapse
It would be interesting to see the recovery log from that...
It kind of sounds like there's some issue with your recovery. Have you tried letting the Manager patch your ROM's boot image and then flash that to your device manually?
Didgeridoohan said:
It would be interesting to see the recovery log from that...
It kind of sounds like there's some issue with your recovery. Have you tried letting the Manager patch your ROM's boot image and then flash that to your device manually?
Click to expand...
Click to collapse
I tried letting the Manager patch the boot image. I got the boot image by extracting it from the LineageOS rom. However, it would appear that the rom installer Loki's it on the fly, so the extracted rom by itself didn't pass the kernel signature check. This wouldn't be a problem if Magisk Lokied it during the patching process, but apparently it doesn't.
If there's an easy way to get the already lokied boot image off of my phone, I would appreciate being pointed in the right direction and I'll try it again. When installing Magisk, it allegedly backs up the boot image - if so, is there a way for me to recover it?
In any case, I went through the full routine all over again so that I could get the recovery log. I added it to the top post. It shows me doing a wipe, installing the LineageOS rom linked to in the top post, flashing Magisk, then flashing the Magisk Uninstaller immediately afterwards so that you can see it say that Magisk was never installed in the first place.
I just tried using TWRP 3.1.0.0 instead of 3.1.1.0 - no change.
Is there an easy way to extract the current boot.img (not the one from the rom installer, since that hasn't been Loki patched)? If so, I can try the patching through the app again.
Otherwise, if there are any other ideas, I would love to hear them.
Otherwise, I may have no choice but to buy a new phone if this one can no longer be rooted.
I use Magisk since years and my devices got always rooted after its installation, but today it's differenti ad you may see in the attached pic...
I've G8441 and I installed Lineage 16, I'd even like to have root access!
Waiting for your advices to solve my problem!
You need to give more details than that. What have you done and what was the result?
Take a look here:
https://www.didgeridoohan.com/magisk/MagiskHelp
I installed Magisk via TWRP, I can't provide any log but installation ended in the good way (no error) but Magisk is not installed.
I flashed Magisk before ROM and gapps, I rebooted after that and then I installed the rest (ROM and gapps).
That's still quite slim, information-wise...
But, if you flashed your ROM after Magisk there's a good chance that Magisk got overwritten with the stock ROM boot image. And if the LOS addon.d glitched (there's been issues with v2), you'd end up with no root.
Magisk goes last when installing.
Didgeridoohan said:
That's still quite slim, information-wise...
But, if you flashed your ROM after Magisk there's a good chance that Magisk got overwritten with the stock ROM boot image. And if the LOS addon.d glitched (there's been issues with v2), you'd end up with no root.
Magisk goes last when installing.
Click to expand...
Click to collapse
Knowing that Magisk needs to be the last during installation is good! Gotta try this!
Many thanks Didgeridoohan!
i run china k20 pro on indian miui 11.01.0
i installed twrp -21 version
installing magisk 20 provides root access however magisk manager asks to something which results in bootloop to recovery
ignoring that request, the module i wanted to install [energized ] asks for updating to magisk 20.1 which also leads to bootloop to recovery.
is there anything to do ? or just wait for magisk 20.2 to be released and then try it
p.s installing magisk was the only way to prevent redmi recovery from overwriting twrp, i don't know if this has any importance
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
eLcTrOn said:
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
Click to expand...
Click to collapse
yeah i used magisk uninstaller to make the phone work normally
Glad it worked . Are u able to install magisk again ?
eLcTrOn said:
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
Click to expand...
Click to collapse
Dont install Viper4android via magisk. Just download the package and install in via TWRP. Use this guide
I have this exact problem right now but even with other versions of magisk, I encounter the same issue. Any suggestions?
Same problem here with magisk I guess it is a compatibly issue with MIUI 11
Yep, it's a MIUI11 issue and the reason I haven't shifted over to it. I suspect whatever release of magisk is in the pipeline will fix it provided it's been reported.
In the meanwhile I've read 19.4 works; you could try the canary builds if that seems to old for your liking... just be careful.
Had the same problem, its because of data encryption.
You guys need to format data before installing magisk.
winesh said:
Had the same problem, its because of data encryption.
You guys need to format data before installing magisk.
Click to expand...
Click to collapse
Even with data formatting 20.1 causes issues: In fact, it seems latest Magisk build seems to be causing issues on all (or, many) builds of MIUI 11.
For k20 pro, 19.3/.4 seems smartest to install and then update via magisk manager
I believe other phones (mi 9?) need even older versions like 17.2, so I wouldn't be surprised if future updates continue to push the installation build back.
AvgZing said:
Even with data formatting 20.1 causes issues: In fact, it seems latest Magisk build seems to be causing issues on all (or, many) builds of MIUI 11.
For k20 pro, 19.3/.4 seems smartest to install and then update via magisk manager
I believe other phones (mi 9?) need even older versions like 17.2, so I wouldn't be surprised if future updates continue to push the installation build back.
Click to expand...
Click to collapse
I'm hoping the Magisk situation gets fixed. I checked the Magisk support thread and only saw one post about a bootloop with a Mi9T Pro (again, likely data encryption) so I'm given the impression MIUI might be off the radar for Magisk bug fixes.
I've had a couple of issues with Magisk 20.1 on MIUI10 - nothing critical but a couple times Magisk Manager has frozen (i.e. kill the process, relaunch and it works) and a couple hangs when root apps have been launched for the first time (again, kill + relaunch, a few times if necessary). Smooth sailing otherwise but gives me the impression that Magisk isn't without flaws on MIUI. One response was to dump MIUI altogether but I'd rather have a stable hardware experience for now. I tested a lot of custom ROMs on my last device and based on that, I'd like to stick to MIUI for a while.
Out of curiousity what are the other bugs with MIUI11 aside from it not working with encryption?
droident said:
I'm hoping the Magisk situation gets fixed. I checked the Magisk support thread and only saw one post about a bootloop with a Mi9T Pro (again, likely data encryption) so I'm given the impression MIUI might be off the radar for Magisk bug fixes.
I've had a couple of issues with Magisk 20.1 on MIUI10 - nothing critical but a couple times Magisk Manager has frozen (i.e. kill the process, relaunch and it works) and a couple hangs when root apps have been launched for the first time (again, kill + relaunch, a few times if necessary). Smooth sailing otherwise but gives me the impression that Magisk isn't without flaws on MIUI. One response was to dump MIUI altogether but I'd rather have a stable hardware experience for now. I tested a lot of custom ROMs on my last device and based on that, I'd like to stick to MIUI for a while.
Out of curiousity what are the other bugs with MIUI11 aside from it not working with encryption?
Click to expand...
Click to collapse
Other than standard app compatibility issues, I haven't heard of any major MIUI11 bugs, which is fantastic to hear.
I have tried all sorts. MI9T MIUI 11.0.1.0 and magisk just causes recovery bootloop . Gonna try magisk 19.4 if thats a thing mentioned in a previous reply
I use Miui 11.0.3 together with Magisk. I used the following procedure:
1. Copy Magisk 20.1 (for twrp) to your internal storage (e.g. downloads)
2. Install Magisk via TWRP
3. Don't reboot (it will cause bootloop).
4. Do factory reset (it will remove your Data). Your bootloader will remain patched.
5. Reboot your phone, do initial config.
6. Install Magisk Manager and run it so you will see that Magisk is installed.
7. DON'T install additional files suggested by Magisk Manager (or you will end up in bootloop again)
8. Enjoy your rooted K20Pro!
I got the same problem on my k20 pro (with MIUI EU).I try driffent ways provided by magisk official but no one works.I have to flash the system. It's not a good idea for intalling V4A on this phone
XedosMD said:
I use Miui 11.0.3 together with Magisk. I used the following procedure:
1. Copy Magisk 20.1 (for twrp) to your internal storage (e.g. downloads)
2. Install Magisk via TWRP
3. Don't reboot (it will cause bootloop).
4. Do factory reset (it will remove your Data). Your bootloader will remain patched.
5. Reboot your phone, do initial config.
6. Install Magisk Manager and run it so you will see that Magisk is installed.
7. DON'T install additional files suggested by Magisk Manager (or you will end up in bootloop again)
8. Enjoy your rooted K20Pro!
Click to expand...
Click to collapse
Does your phone remain encrypted after you do these steps? I doubt...
For some reasons, I wanna keep my phone encrypted.
I wanted to install Aroma because I want the choice of installing whichever app specifically and mainly so that I can replace stock AOSP apps with Google ones. I tried to do that on top of clean flash RR 8.6.2 which does not comes with any pre-built GApps.
But upon installation on OrangeFox it freezes for 2-3 seconds and gives error 255. This is ARM64 Android 10 Aroma so guess I chose the right version but still the error. I can install others like pico, nano, mini and stock just fine but not aroma.
I even tried previous months versions but no luck. Tried installing ROM, set it up and Aroma separately with going to recovery again but still the same error. I am able to flash ANX camera, custom kernel & Fdecrypt just fine but not this one...
If anybody could help what is the issue.
I too am having this issue with the moto edge (racer). Had issues rooting. TWRP went in, flashed lineage 17.1, rebooted, TWRP gone, LineageOS recovery in its place, attached to USB, flashed TWRP ... AGAIN, rebooted, did a root check, root check said "no bueno". Thought that had something to do with it. Finally got a good copy of SuperSU flashed with "success" confimation. NO ERRORS! rebooted. Let everything run its course, for about 10 minutes (way longer than necessary) then tried to flash OpenGapps 10 Aroma and it fails. tried w/ and w/o signature verification, ARM and ARM64. All of it fails! no matter what version, w/sig ver. I get Error 255. w/o it, I ironically get "Zip Signatured Verification Failed!"
Please, somebody heeeeeellllllp
Skorpyun812 said:
I too am having this issue with the moto edge (racer). Had issues rooting. TWRP went in, flashed lineage 17.1, rebooted, TWRP gone, LineageOS recovery in its place, attached to USB, flashed TWRP ... AGAIN, rebooted, did a root check, root check said "no bueno". Thought that had something to do with it. Finally got a good copy of SuperSU flashed with "success" confimation. NO ERRORS! rebooted. Let everything run its course, for about 10 minutes (way longer than necessary) then tried to flash OpenGapps 10 Aroma and it fails. tried w/ and w/o signature verification, ARM and ARM64. All of it fails! no matter what version, w/sig ver. I get Error 255. w/o it, I ironically get "Zip Signatured Verification Failed!"
Please, somebody heeeeeellllllp
Click to expand...
Click to collapse
UPDATE: For some reason Aroma wasn't giving me error logs but, after trying "full", I noticed the error message was that my device is ARM64. Then, after trying 9.0 and 10 ARM64, (both full versions, not aroma) I found in the logs that there was insufficient space to install. The log for some reason, claims the full version needs 1.7 TB?! So I grabbed a copy of OpenGApps 10 ARM64 pico and that worked. I got basic play store function, that's all I really needed. . . Do not ask why I didn't think of that sooner. Hope this helps poster or anyone else. \m/