Related
Hi guys! I am having some issues when trying to install magisk. I am currently running the latest twrp-3.2.2-0-enchilada. When trying to install magisk I'm currently having a constant error. Attached are the recovery log and a screenshot.
Magisk Error 1 fix
Hi, it looks as though you are trying to install an unsupported version of magisk you need to use the 16.4 installer not the 16.0 installer this will most likely fix your issue, I hope this helped. PS it is a beta version of magisk not the latest stable build.
16 is the stable build and SHOULD work!
Did for me.
It looks like the problem was a bad install of magisk. I went to the forums of magisk and found an uninstaller. I flashes it and then flashes the stable version. It looks like it worked. I have root back.
I used for a while HAVOC-OS, I completely cleaned my device then flashed Stock OXygen OS 5.1.11, so no TWRP and magisk on device but bootloader is still unlocked.
Next step, I temporrarely booted into TWRP 3.2.1.0-Enchilada.img, then installed TWRP 3.2.1.-enchilada.zip and also Magisk 16.7.zip. Phone booted fine, but I got a notification saying ( There is an internal problem with your device. Contact manufacturer for details). But the phone works fine, and the storage data is correct, but this notification appears after each reboot.
What did I do wrong ? and what should I do to make this notification go away, please let me know.
abati said:
I used for a while HAVOC-OS, I completely cleaned my device then flashed Stock OXygen OS 5.1.11, so no TWRP and magisk on device but bootloader is still unlocked.
Next step, I temporrarely booted into TWRP 3.2.1.0-Enchilada.img, then installed TWRP 3.2.1.-enchilada.zip and also Magisk 16.7.zip. Phone booted fine, but I got a notification saying ( There is an internal problem with your device. Contact manufacturer for details). But the phone works fine, and the storage data is correct, but this notification appears after each reboot.
What did I do wrong ? and what should I do to make this notification go away, please let me know.
Click to expand...
Click to collapse
Use Magisk uninstaller and then install Magisk 16.4. Let Magisk update from there.
tabletalker7 said:
Use Magisk uninstaller and then install Magisk 16.4. Let Magisk update from there.
Click to expand...
Click to collapse
Amazing, it worked ! thnx bro
abati said:
Amazing, it worked ! thnx bro
Click to expand...
Click to collapse
Now keep a copy of Magisk 16.4 on hand. It has always worked on OP6 and many other versions of Magisk cause weird problems. Just let the Magisk manager update things from here.
tabletalker7 said:
Now keep a copy of Magisk 16.4 on hand. It has always worked on OP6 and many other versions of Magisk cause weird problems. Just let the Magisk manager update things from here.
Click to expand...
Click to collapse
17.1 seems fine. I haven't had any problems with it. 16.7 was the culprit.
Barsky said:
17.1 seems fine. I haven't had any problems with it. 16.7 was the culprit.
Click to expand...
Click to collapse
Did you install 17.1 or did you let 16.4 update to 17.1? On the Oreo builds 16.4 was the only one guaranteed to work right, but I was on the Pie betas when I got my hands on 17.1
tabletalker7 said:
Did you install 17.1 or did you let 16.4 update to 17.1? On the Oreo builds 16.4 was the only one guaranteed to work right, but I was on the Pie betas when I got my hands on 17.1
Click to expand...
Click to collapse
This was a clean install of open beta straight to 17.1.
Barsky said:
This was a clean install of open beta straight to 17.1.
Click to expand...
Click to collapse
Yeah the OP installed 5.1.11. He is still on Oreo. He needs 16.4
hi. i have the same pop up msg after a clean install of 17.1 from here - https://forum.xda-developers.com/gr...om-lineageos-17-0-galaxy-grand-prime-t4034919. magisk was not preinstalled on this rom.
my phone specs - samsung galaxy grand prime
sm-g530h - A.P - XXS2BRLI
CP - XXU2BPB2
MSM - 8916
i tried removing assert line from udater script and reflashed ( clean install again). but the pop p appears still. any ideas how to get rid of it? thank you in advance.
Hi everyone,
I had recently upgraded to android 10 (clean flash) and installed TWRP and Magisk and everything was fine. However, one fine day, I performed a random reboot and my phone got stuck in a bootloop. I proceeded to boot into TWRP and flashed Magisk uninstaller and the phone booted again. But now, the problem is that every time I try to flash Magisk, I end up in the same bootloop. I am unsure how to get Magisk installed again and I don't want to Clean flash and set up the device all over again.
Please help me out XDA.
Thank you!
ImperatorShade said:
Hi everyone,
I had recently upgraded to android 10 (clean flash) and installed TWRP and Magisk and everything was fine. However, one fine day, I performed a random reboot and my phone got stuck in a bootloop. I proceeded to boot into TWRP and flashed Magisk uninstaller and the phone booted again. But now, the problem is that every time I try to flash Magisk, I end up in the same bootloop. I am unsure how to get Magisk installed again and I don't want to Clean flash and set up the device all over again.
Please help me out XDA.
Thank you!
Click to expand...
Click to collapse
Hello,
Which instruction did you follow?
What version of rom, twrp and magisk did you have? (maybe with file names).
strongst said:
Hello,
Which instruction did you follow?
What version of rom, twrp and magisk did you have? (maybe with file names).
Click to expand...
Click to collapse
Thank you for the response strongst!
I am using the 10.0.1 GM57AA build right now. Updated directly from 10.0.0 by flashing rom in local updater, then without reboot, flashed twrp installer and magisk in inactiv slot, in magisk iteslf (followed your guide and the one Kollachi had put up).
Magisk version is 20.1 and TWRP version is 3.3.1-70.
Everything was working fine for about two months before one reboot started causing the bootloop. (I made no other changes to magisk before this reboot)
Thanks!
ImperatorShade said:
Thank you for the response strongst!
I am using the 10.0.1 GM57AA build right now. Updated directly from 10.0.0 by flashing rom in local updater, then without reboot, flashed twrp installer and magisk in inactiv slot, in magisk iteslf (followed your guide and the one Kollachi had put up).
Magisk version is 20.1 and TWRP version is 3.3.1-70.
Everything was working fine for about two months before one reboot started causing the bootloop. (I made no other changes to magisk before this reboot)
Thanks!
Click to expand...
Click to collapse
Maybe you did have any magisk modules left?
Have you tried an older magisk version?
strongst said:
Maybe you did have any magisk modules left?
Have you tried an older magisk version?
Click to expand...
Click to collapse
Thanks for the fast response! Yes, I tried Magisk 19.3 ver but got the same issue.
ImperatorShade said:
Thanks for the fast response! Yes, I tried Magisk 19.3 ver but got the same issue.
Click to expand...
Click to collapse
And are there any magisk modules or mods left? It can be the reason for this.
Are there any errors within the log while flashing?
You have the twrp guacamole unified from mauronofrio 3.3.1-70, right? You can try 3.3.1-73 if you want.
There were no errors when flashing. But I'm not sure whether I had disabled Magisk Modules before flashing OxygenOS 10. Anyway, what would be the best way to untwrp and clean flash?
Had anyone tried Magisk 20.2 and manager 7.5.0?
Is it bootloop free with OS 10?
I updated to the canary release through TWRP and I've been good. I'd expect you won't boot loop, but do a backup first if you can.
I updated thru mm ( after updating mm thru mm) and installed the recommended way in app. No issues.
LG G6 Pie
just updated to M 20.2 my LG G6 H870 Pie thru mm and got into bootloop. no way out and reset phone with LG Bridge (LGup not working for me since 9.0) without data loss. tried again from twrp and bootloop again. now flashing last 20.1 and won't install till next update.
I have latest Magisk Canary & Magisk Manager Canary from today, 02.01.2020. Working fine.
Did the Direct Install and all up to date! ?
I have OP6T with Android 10 AND recently updated to magisk 20.2 and Is working fine for me
Modules don't work in Magisk 20.2. They get installed but they don't take effect. I have to go back to Magisk version 20.1.
bjm51591 said:
Modules don't work in Magisk 20.2. They get installed but they don't take effect. I have to go back to Magisk version 20.1.
Click to expand...
Click to collapse
They work fine for me.
No problems here
fix Magisk 20.3
charliezulu said:
just updated to M 20.2 my LG G6 H870 Pie thru mm and got into bootloop. no way out and reset phone with LG Bridge (LGup not working for me since 9.0) without data loss. tried again from twrp and bootloop again. now flashing last 20.1 and won't install till next update.
Click to expand...
Click to collapse
Hi, just installed 20.3 and all is working; reading the log, problems for 20.2 were known with LG.
All is ok!
20.3 everything work fine!
Hi to everyone I'm on magisk 20.1, can I update directly to magisk 20.3 via magisk manager or before I've to uninstall some modules (maybe oos native call) like rom update?
giacomowrc said:
Hi to everyone I'm on magisk 20.1, can I update directly to magisk 20.3 via magisk manager or before I've to uninstall some modules (maybe oos native call) like rom update?
Click to expand...
Click to collapse
I've never had to uninstall modules to update Magisk (I have Swift Installer and xXx modules). Just update the manager app and do direct install of the update.
Just Posted
https://developers.google.com/android/images#sunfish
fronto said:
Just Posted
https://developers.google.com/android/images#sunfish
Click to expand...
Click to collapse
I just checked my 4a with the Check for Updates button under settings and Android 11 is there waiting for me to d/l and install.
I successfully applied the OTA update, then extracted the boot.img from the full image (both versions matching RP1A.200720.011), patched with Magisk, and then flashed it, but now phone wont boot. Just getting the G startup logo for over 10 min now. Has anyone had success with this method? Is there a better way to do it?
Just updated with no issues, but I'm not rooted yet. Only thing I really want is custom accent color (red), so not sure if it's worth rooting.
Sent from my Pixel 4a using XDA Labs
hate to say it but I think at this point that Magisk 20.4 (Manager 7.5.1) cannot root Android 11 on this phone. I have posted this finding on the rooting thread asking if anyone has had success:
https://forum.xda-developers.com/pixel-4a/how-to/guide-unlock-root-pixel-4a-t4153773/page4
I unrooted, applied update, installed Magisk Canary build, patched boot image from downloaded Factory Image, fastboot flash boot... and have successfully rooted my 4a on w/11.
Well I got an email from Google saying that android 11 was waiting for me to download. So I checked updates and it says my device is up to date. So I guess maybe verizon does hold up updates.
moeava said:
I unrooted, applied update, installed Magisk Canary build, patched boot image from downloaded Factory Image, fastboot flash boot... and have successfully rooted my 4a on w/11.
Click to expand...
Click to collapse
where did you find it? nvrmnd https://github.com/topjohnwu/magisk_files/tree/canary
@tcat007 @fronto
For anyone looking to root, you need magisk canary, latest build at time of writing (20424) works fine for me. Took the OTA from 10 to 11 following the magisk OTA update guide here worked like a charm: https://topjohnwu.github.io/Magisk/ota.html
However, somethings seemed to have changed in 11. For audio apps like jdsp and v4a, you'll need to run this in terminal (only needs done once):
Code:
su -c settings put global hidden_api_policy 1
Also note that sbin is gone too (least on pixel 4a) so v4a app install won't work properly (it's being worked on)
fronto said:
I successfully applied the OTA update, then extracted the boot.img from the full image (both versions matching RP1A.200720.011), patched with Magisk, and then flashed it, but now phone wont boot. Just getting the G startup logo for over 10 min now. Has anyone had success with this method? Is there a better way to do it?
Click to expand...
Click to collapse
You need to use latest canary
Stable doesn't yet support 11 afaik
tthalheim said:
You need to use latest canary
Stable doesn't yet support 11 afaik
Click to expand...
Click to collapse
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Yeah I dont like that canary Magisk so I used your advice and flashed the patched boot.img and then went back to stable Magisk. I am a little underwhelmed with Android 11 maybe its just me.
fronto said:
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Click to expand...
Click to collapse
good deal...yeah I figured with the pre-patched boot.img, a lot of people could avoid messing with canary alltogether and just keep normal stable.
Agreed 11 does not seem all that revolutionary. ...but all is working well now with no complaints
Archangel said:
Yeah I dont like that canary Magisk so I used your advice and flashed the patched boot.img and then went back to stable Magisk. I am a little underwhelmed with Android 11 maybe its just me.
Click to expand...
Click to collapse
If you’re running boot imaged patched with magisk canary then your running magisk canary
Sent from my iPad using Tapatalk
Yeah brother all I was saying is that I dont like the canary design for Magisk Manager so I went back to stable for manager only.
jrkruse said:
If you’re running boot imaged patched with magisk canary then your running magisk canary
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Archangel said:
Yeah brother all I was saying is that I dont like the canary design for Magisk Manager so I wet went back to stable for manager only.
Click to expand...
Click to collapse
Oh ok
Sent from my iPhone using Tapatalk
fronto said:
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Click to expand...
Click to collapse
Thank you for the upload. Can this be flashed in magisk? I presume no.
Can you clarify the steps? I'm already on android 10 rooted.
1. Uninstall magisk / Restore image
2.. Download install Android 11 / no reboot
3..... ? Then with patched boot.
Thank you
mustbevick said:
Thank you for the upload. Can this be flashed in magisk? I presume no.
Can you clarify the steps? I'm already on android 10 rooted.
1. Uninstall magisk / Restore image
2.. Download install Android 11 / no reboot
3..... ? Then with patched boot.
Thank you
Click to expand...
Click to collapse
Its not flashed in Magisk. Its flashed using fastboot via a computer connection. With that file, you never need to touch Canary manager.
1. uninstall Magisk but you keep Magisk Manager
2. update to Android 11 via OTA or with full image provided you revise the flash-all to not wipe, or just manually issue each command.
3. make sure your 11 is up and running
4. reboot to bootloader, connect PC
5. fastboot flash boot magisk_patched_sunfish-rp1a.200720.011.img
6. reboot and open regular stable Magisk Manager
enjoy
I've rooted my 4a with magisk with the Aug factory image (android 10). I have the both Titanium Pro and Mybackup Pro - Do either of those programs create an image backup similar to the image I create of my PC using a program like Acronis, so that I could just re-install the Android 10 system if I don't like Android 11? If those programs don't do that is there any program that will do that?
Has anyone else noticed x google enrollment then updating message every (re) boot? I must have done something wrong. I got magisk working nicely. Can install itself, modules, ctsProfile is true, whatevs... But nothing else gets a su toast. Not too worried with it this first week or so.. I'll stab again weekend after next.
Sent from my Pixel 4a using Tapatalk