Hello!
What version of Magisk are you all using for treble roms?
Ever since i install a treble rom (on DotOS for the moment), magisk keeps booting me to fastboot. I've used the 16.4 magisk recommended in the LineageOS thread (Link).
The official Magisk said the following in the release notes for 16.7:
Hot Fix (versionCode: 1671)
Fix booting to fastboot on half-treble devices (OP5/5T on stable OOS, maybe more)
Detect ramdisk partition for Huawei
Click to expand...
Click to collapse
Which seemed promising but when i flashed my phone and boot it doesn't recognize it (no errors during flashing), and Magisk Manager says that Magisk isn't installed.
Any help on this would be very appreciated.
Related
HELP I have researched everywhere on the internet and I'm not sure what to do. I have a REDMI 4A wit AEX ROM OREO8.1 installed, TWRP 3.2.2.0 Official (for Redmi 4A on the twrp website) and tried to flash Magisk v.16. Error 1 mount vendor shows up in twrp. Many YouTubers says I should flash boot.img. I've already flashed the boot.img of the given AEX ROM OREO 8.1, but the same error occurs. I tried to search for answers, and what I found was that apprently aosp oreo ROMs usually are Treble ROMs. Downloaded Termux app and checked if ROM was treble = false = NOT Treble! Then others say I have to flash a modded vendor version of twrp. (Link: (add Https here)/androidfilehost.com/?fid=674106145207489212) Haven't tried it out just wanted to make sure if I should or not, bacuse the last time I tried to flash a different twrp, I had to flash the original one back using ADB...
Btw I had given up at some point and I flashed SuperSU successfully. Why Can I flash SuperSU but not Magisk?? I fully unrooted SuperSU and am ready to try flashing Magisk again. If anyone has any idea how to fix this, pleeeeeease tell me I need Snapchat to work while having root (yes I know I could've used Titanium Backup but that not the point rn)
Thanks in advance!!!
Austin:fingers-crossed:
Install TWRP Pitch Black and Install Magisk for Treble ROM
[ HELP I have researched everywhere on the internet and I'm not sure what to do. I have a REDMI 4A wit AEX ROM OREO8.1 installed, TWRP 3.2.2.0 Official (for Redmi 4A on the twrp website) and tried to flash Magisk v.16. Error 1 mount vendor shows up in twrp. Many YouTubers says I should flash boot.img. I've already flashed the boot.img of the given AEX ROM OREO 8.1, but the same error occurs. I tried to search for answers, and what I found was that apprently aosp oreo ROMs usually are Treble ROMs. Downloaded Termux app and checked if ROM was treble = false = NOT Treble! Then others say I have to flash a modded vendor version of twrp. (Link: (add Https here)//androidfilehost.com/?fid=674106145207489212) Haven't tried it out just wanted to make sure if I should or not, bacuse the last time I tried to flash a different twrp, I had to flash the original one back using ADB...
Btw I had given up at some point and I flashed SuperSU successfully. Why Can I flash SuperSU but not Magisk?? I fully unrooted SuperSU and am ready to try flashing Magisk again. If anyone has any idea how to fix this, pleeeeeease tell me I need Snapchat to work while having root (yes I know I could've used Titanium Backup but that not the point rn)
Thanks in advance!!!
Austin:fingers-crossed:
Yup, you must use TWRP Vendor if you want to use magisk in AEX Oreo.
Han usb Deccan if DHC dry j
Wrong section.
Install TWRP Pitch Black, then install magisk for treble rom
That version may have bugs try the newer versions
Try with Pitch Black recovery or Orange Fox recovery
Same for me and than i using BATIK Recovery for fix it
Solved Magisk error!
I've tried so many Recoveries and after trying more than 5 recoveries and about 7 Different ROM I finally got the answer.
So basically now that Redmi 4A is treble based, hence it has now a new Partitioning vendor based. For that you'll need new Recovery that support vendor mounting. I've tried the other Recoveries mentioned above and all of them are buggy. Go for the official TWRP vendor based Recovery. I found it here :
https://freaksterism.blogspot.com/2018/10/solved-cannot-mount-vendor-magisk.html?m=1
The steps are explained purely for Redmi 4A.
Use pitchblack recovery and all the problems will fix or install supersu and install magisk apk, grant root and install directly and then you can uninstall supersu with unsu zip
Hello,
Until now I could only install magisk 16.4 on the mi8se without getting a bootloop.
Do you know if magisk 17.3 has already solved the problem?
yes, bootloop here too with 17,3
OK thanks...
I leave the subject waiting until magisk 17.4
Any luck??? I've been getting Boot loops with every magisk I flash other than what comes with the recovery Wich is 16.4
j0an said:
Any luck??? I've been getting Boot loops with every magisk I flash other than what comes with the recovery Wich is 16.4
Click to expand...
Click to collapse
Just install latest TWRP 3.2.3 from this thread, and choose Install Root in TWRP, it will instal Magisk 16.6 and working fine with both Android 8.1 and 9.0 of MIUI roms.
https://forum.xda-developers.com/mi-8-se/development/recovery-twrp-recovery-3-2-3-lr-team-t3828854
longnt2007 said:
Just install latest TWRP 3.2.3 from this thread, and choose Install Root in TWRP, it will instal Magisk 16.6 and working fine with both Android 8.1 and 9.0 of MIUI roms.
https://forum.xda-developers.com/mi-8-se/development/recovery-twrp-recovery-3-2-3-lr-team-t3828854
Click to expand...
Click to collapse
Thanks for the information. I must apologize for providing the wrong information, the magisk version I was referring was 16.6 which comes with the twrp. I still trying to get the magisk above 17.0 working... Some of the modules I use like YouTube vanced don't work on magisk below 17.x:crying:
But again .. thank you for the quick response
Did somebody tries magisk 18?
zudo said:
Did somebody tries magisk 18?
Click to expand...
Click to collapse
I did ... And guess what?...... Boot loops :crying: the:crying:
I have installed the latest pie stable on my op 3t. However it would never boot when installing with Magisk.
So for now I have installed it without Magisk and got it to work ok. However now I'm having same problem installing Magisk.
I can install and uninstall it from twrp latest, however when it's installed, it is just stuck on the initial screen with oneplus logo. And never makes it to the circle/dots screen.
I tried using 19. 2, 19.0 Magisk and 18.1.
Is there any logs I can pull or did anyone else have this issue?
Are there any other safe root solutions to try instead?
Any help would be appreciated
anykiel91 said:
I have installed the latest pie stable on my op 3t. However it would never boot when installing with Magisk.
So for now I have installed it without Magisk and got it to work ok. However now I'm having same problem installing Magisk.
I can install and uninstall it from twrp latest, however when it's installed, it is just stuck on the initial screen with oneplus logo. And never makes it to the circle/dots screen.
I tried using 19. 2, 19.0 Magisk and 18.1.
Is there any logs I can pull or did anyone else have this issue?
Are there any other safe root solutions to try instead?
Any help would be appreciated
Click to expand...
Click to collapse
I always flash Magisk BEFORE the first boot. Also no custom kernels, especially not AFTER Magisk flash.
Is this what you did as well?
I couldn't get it to boot up before firstboot. So I went with normal nonroot flash so I could use the phone.
I figured it would not matter if I installed Magisk later.
I might try to reflash everything over again
ast00 said:
I always flash Magisk BEFORE the first boot. Also no custom kernels, especially not AFTER Magisk flash.
Is this what you did as well?
Click to expand...
Click to collapse
topjohnwu says that you flash custom kernel after flashing Magisk
Immortalis said:
topjohnwu says that you flash custom kernel after flashing Magisk
Click to expand...
Click to collapse
Never had this problem until today. So I did some testing.
Magisk 19.1 causes it to get stuck at the OP logo.
I flashed uninstaller, reflashed the ROM, flashed Magisk 19.2 and it worked.
Are you using the 19.2 zip?
ast00 said:
Never had this problem until today. So I did some testing.
Magisk 19.1 causes it to get stuck at the OP logo.
I flashed uninstaller, reflashed the ROM, flashed Magisk 19.2 and it worked.
Are you using the 19.2 zip?
Click to expand...
Click to collapse
Yes, I had problems with 19.1 too, that the phone sometimes (if not always) would boot itself into fastboot mode instead of system, so at that time I moved temporarily to canary builds
I used this zip instead and it worked. Not sure what's different but I'm good now
https://forum.xda-developers.com/oneplus-3t/development/rom-theone3tos-v1-0-t3730932
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.