Hello there, I have used trwp 3.2.3-1 and 3.2.3-0 by mohann and magisk 18 but, when I install magisk by twrp, nothing appeare. Any idea or solution?
Klirioth said:
Hello there, I have used trwp 3.2.3-1 and 3.2.3-0 by mohann and magisk 18 but, when I install magisk by twrp, nothing appeare. Any idea or solution?
Click to expand...
Click to collapse
First - Stop opening thread as there are many about Magisk
Second - Wait for patched boot image that you will flash / boot from Fastboot
Klirioth said:
Hello there, I have used trwp 3.2.3-1 and 3.2.3-0 by mohann and magisk 18 but, when I install magisk by twrp, nothing appeare. Any idea or solution?
Click to expand...
Click to collapse
Use latest Twrp cosmic with hotboot flash and reboot,no need boot.img patched
Related
Did anyone notice that doing a "fastboot boot boot-patched.img" for installing magisk sometimes hangs during boot or a stock recovery error msg "Could not load Android system. Your data could be corrupt....."
I need a few tries before it boots properly. And then installing the systemless expose module gives a similar error.
edit- It doesn't seem to be happening anymore. I tried reproduce the problem but couldn't get it to hang after many tries.
Others have reported seeing this issue as well.
Use TWRP for Magisk installation + check here https://forum.xda-developers.com/mi-a1/help/rooted-device-freezes-booting-secure-t3819483
_mysiak_ said:
Use TWRP for Magisk installation + check here https://forum.xda-developers.com/mi-a1/help/rooted-device-freezes-booting-secure-t3819483
Click to expand...
Click to collapse
Will installing magisk via TWRP break OTA? I'm assuming you boot(not flash TWRP earlier) into TWRP and flash the Magisk framework zip.
From the thread, it sounds like Magisk 16.7 beta has problems with common apps.
barrack1 said:
Will installing magisk via TWRP break OTA? I'm assuming you boot(not flash TWRP earlier) into TWRP and flash the Magisk framework zip.
From the thread, it sounds like Magisk 16.7 beta has problems with common apps.
Click to expand...
Click to collapse
If you boot TWRP to flash magisk it won't break OTA.
I installed 16.7 yesterday and no problem so far with any app.
pantezuma said:
If you boot TWRP to flash magisk it won't break OTA.
I installed 16.7 yesterday and no problem so far with any app.
Click to expand...
Click to collapse
Do you know why flashing magisk after booting into TWRP won't cause problems VS booting into patched boot.img and installing Magisk via "direct install"?? It didn't cause any big booting issue pre 8.1 for me until the last update.
barrack1 said:
Do you know why flashing magisk after booting into TWRP won't cause problems VS booting into patched boot.img and installing Magisk via "direct install"?? It didn't cause any big booting issue pre 8.1 for me until the last update.
Click to expand...
Click to collapse
I think you booted an image patched with 16.0 and not 16.7 (you can try to get an image patched with 16.7 beta just to verify).
As said before, it seems 16.0 has some issues regarding booting and secure boot solved in 16.7.
Hi there,
In short, I couldn't manage to install new Magisk v17 and v17.1 on my LG V20 H990DS due to the bootloop issue.
Anyone managed to do that ?!
The details:
- I tried to install Magisk V17 through Magisk app, but failed.
- I installed it through TWRP but failed (Bootloop),
- I uninstall it, phone returned to normal
- I tried to install Magisk V17.1 through Magisk app, but failed (Bootloop).
- I installed it through TWRP but failed (Bootloop).
- I uninstall it, phone returned to normal
- I installed Magisk V16.0 and now functioning normal.
Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.
iDefalt said:
Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.
Click to expand...
Click to collapse
I'll try right away.
iDefalt said:
Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.
Click to expand...
Click to collapse
Thank you bro, I followed same steps however, I got a bootloop ;(
MaZeNsMz said:
Thank you bro, I followed same steps however, I got a bootloop ;(
Click to expand...
Click to collapse
I can't say what else would help sorry, those are the exact steps I followed and they worked.
Perhaps you could post in the Magisk part of the forums with some info about your device and see if someone could help.
MaZeNsMz said:
Hi there,
In short, I couldn't manage to install new Magisk v17 and v17.1 on my LG V20 H990DS due to the bootloop issue.
Anyone managed to do that ?!
The details:
- I tried to install Magisk V17 through Magisk app, but failed.
- I installed it through TWRP but failed (Bootloop),
- I uninstall it, phone returned to normal
- I tried to install Magisk V17.1 through Magisk app, but failed (Bootloop).
- I installed it through TWRP but failed (Bootloop).
- I uninstall it, phone returned to normal
- I installed Magisk V16.0 and now functioning normal.
Click to expand...
Click to collapse
This is a magisk issue and shouldn't be posted here
Sent from my LG-H910 using XDA Labs
I had the same problem till I went to twrp recovery and flashed the zip that magisk downloaded and it works great. Only problem left on the side is trying to get Xposed to work again through the new magisk on H918 Super Rom, it's not working ATM but I think it's fixable somehow I guess. Magisk is effecting all phones, not just V20 btw.
Check out the video about the API and safetynet by the YouTuber HighOnAndroid. That video let's u know what's up with magisk the day before new magisk update came.
Is it possible that someone backup and share with me boot partition, and from my side I recover it ?!
I'm running:
ROM: RR-0-v6.1.0-h990-Unofficial
Kernel: Gamma Kernel v26.0.0
Magisk: v17.1
Magisk Manager: v5.9.1
I'm not on stock, but i had no error or problems installing it.
Are you on stock or?
I was able to directly install Magisk 17.1 from Magisk itself without issues.
SebTech33 said:
I'm running:
ROM: RR-0-v6.1.0-h990-Unofficial
Kernel: Gamma Kernel v26.0.0
Magisk: v17.1
Magisk Manager: v5.9.1
I'm not on stock, but i had no error or problems installing it.
Are you on stock or?
Click to expand...
Click to collapse
Rom: Stock,
Kernel: neocore-reboot-v2.5
Magisk: V16.0
KawaiiNek0 said:
I was able to directly install Magisk 17.1 from Magisk itself without issues.
Click to expand...
Click to collapse
Very locky,
I did the same here by I end up with a nice boot loop
MaZeNsMz said:
Rom: Stock,
Kernel: neocore-reboot-v2.5
Magisk: V16.0
Click to expand...
Click to collapse
Have you tried another kernel?
Anyone could test sixaxis compatibility checker?
(free on store)
Only on h990ds. 910 and other never were affected by this problem with previous magisk.
Dont know if v17 solved this problem.
Thanks
SebTech33 said:
Have you tried another kernel?
Click to expand...
Click to collapse
I'll try today, do you recommend any kernel?
SebTech33 said:
Have you tried another kernel?
Click to expand...
Click to collapse
Tried D.O.T.S and failed, bootloop
I am thinking if someone can backup the boot and share it with us. So we can recover it
Regards..
Has anyone found a way to make 17.1 work on the H990DS? It took me several flashes to get it to boot but after a couple restarts it started bootlooping again so I had to downgrade to 16 and 16 works just fine
Just stay on v16 until they can work the bugs out with v17 -- you aren't gaining anything by going to v17.
-- Brian
iDefalt said:
Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.
Click to expand...
Click to collapse
Thanks, that did the trick for me on lg h910r
MaZeNsMz said:
Hi there,
In short, I couldn't manage to install new Magisk v17 and v17.1 on my LG V20 H990DS due to the bootloop issue.
Anyone managed to do that ?!
The details:
- I tried to install Magisk V17 through Magisk app, but failed.
- I installed it through TWRP but failed (Bootloop),
- I uninstall it, phone returned to normal
- I tried to install Magisk V17.1 through Magisk app, but failed (Bootloop).
- I installed it through TWRP but failed (Bootloop).
- I uninstall it, phone returned to normal
- I installed Magisk V16.0 and now functioning normal.
Click to expand...
Click to collapse
Note 26.10.2018 :
I upgraded to Oreo V8.0 from here and everything is fine now
Can anybody help me to root this latest version? Is there any special TWRP to boot and then flash latest Magisk?
Use last cosmicdan twrp and last magisk. Easy.
Cheers
I also cannot root my phone after jan updates. after flashing magisk and reboot, there's a black screen in the middle of bootscreen and it restarts the bootscreen and my phone doesnt get rooted.
tonycapuozzo said:
Use last cosmicdan twrp and last magisk. Easy.
Cheers
Click to expand...
Click to collapse
tried the latest twrp and magisk 18.0 .
*UPDATE*
I forgot to enable oem unlocking and USB debugging.
and also mount system in TWRP before flashing magisk.
cheers!
kupuk23 said:
and also mount system in TWRP before flashing magisk.
Click to expand...
Click to collapse
When next OTA arrives, you will know why it fails to install There is absolutely no reason to mount system partition to flash Magisk.
Plz can anybody plz tell me how to root or unlock camera 2 api in ma a1 latest pie june2020 update
it's a simple procedure
just unlock bootloader then boot into TWRP then flash recovery flasher zip and then flash Magisk zip and reboot
I've flashed all stock firmwares and get root with this simple procedure but note I've used TWRP 3.3.1-0 from Giovix92 because TWRP 3.2.1 flasher zip didn't work on latest firmware and i used Magisk19.3 its the most stable Magisk version in my opinion i never faced any problem with this version
Yesterday I followed this instruction:
https://forum.xda-developers.com/tab-s5e/how-to/galaxy-tab-s5e-sm-t720-root-t3947806
and got my Tablet rooted by Magisk with stock ROM.
Next: I want LinageOs on this device, so I had to install TWRP. For TWRP I followed the links on top of the mentioned XDA-thread:
Go HERE if you are interested in custom recovery (e.g., TWRP).
Click to expand...
Click to collapse
which got me to this page:
https://twrp.me/samsung/samsunggalaxytabs5ewifi.html
There is this advice:
You are therefore strongly advised to first root your device with Magisk and then pre-root a TWRP image before flashing it to recovery.
Click to expand...
Click to collapse
I followed the link in this advice an read both 3 times, but I am not sure, what this means.
Next was wiki.lineageos-page for the TAB S5e:
https://wiki.lineageos.org/devices/gts4lvwifi/install
which I also read, but none the wiser. And for more confusing: in the suitable download-page is besides the linage-file a recovery-image, which is not mentioned anywhere. Or I am blind ...
What I at least did: installed TWRP with the TWRP-app and could boot into this custom recorery and installed LineageOS. The Tab S5 is running fine with LinaegeOS but without root ...
What must be done to root?
Spielmops
I flashed the default TWRP into recovery, installed LineageOS from TWRP, and then followed these instructions: https://forum.xda-developers.com/redmi-note-7/how-to/install-magisk-android-11-r-100-t4162761
I have working installation of TWRP and Magisk now.
If your device does not have ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. ... When Magisk is installed in your recovery, you CANNOT use custom recoveries to install/upgrade Magisk! The only way to install/upgrade Magisk is through Magisk Manager. The app will be aware of your device state and install to the correct partition and reboot into the correct mode.
Click to expand...
Click to collapse
The thread you mentioned, is the normal way which I know. This is a special device!
Spielmops
Spielmops said:
The thread you mentioned, is the normal way which I know. This is a special device!
Click to expand...
Click to collapse
All I can tell you is that I didn't preroot anything. (My device is the LTE variant, but I think it doesn't matter other than needing the correct TWRP and Lineage image).
I started with a stock ROM and locked bootloader.
Unlocked the bootloader and installed the current TWRP image via ODIN (In my case, this one: https://dl.twrp.me/gts4lv/, you will want this: https://dl.twrp.me/gts4lvwifi/).
Installed LineageOS 18.0 and GApps through TWRP sideload.
Booted and set up Lineage.
Downloaded the three files from the thread I linked. Installed them and rebooted in the order given.
Finally, updated Magisk Manager and Magisk to the Beta-Channel (21.1) through Magisk Manager.
Done. I have root.
Finally, updated Magisk Manager and Magisk to the Beta-Channel (21.1) through Magisk Manager.
Click to expand...
Click to collapse
Updated Magisk? I think, there was no Magisk in your device?
Spielmops said:
Updated Magisk? I think, there was no Magisk in your device?
Click to expand...
Click to collapse
aserraric said:
Downloaded the three files from the thread I linked. Installed them and rebooted in the order given.
Click to expand...
Click to collapse
I installed both Magisk Manager and Magisk from the files in the other thread. That is a custom version, which I updated to Beta after installing.
I don't find LOS 18, please give me a hint ...
Spielmops said:
I don't find LOS 18, please give me a hint ...
Click to expand...
Click to collapse
Right here in the ROMs section.
Obligatory disclaimer: LOS 18 is still a preview and more likely to have bugs than 17.1, but I'm more than happy with it so far.
@topjohnwu
Can you tell anything to this problem? I've read this:
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Spielmops
I've installed Lineage a few times now on this devices, and I always use the developers instructions here. Then I flash Magisk from TWRP. If you are using LOS 17.1, I just flash it in TWRP. Modules and such can NOT be flashed in TWRP your tablet will not BOOT.
The only version of Magisk that I've found that works in LOS 18 / Android 11 is 297. Links in this post.
hello geniuses..!!
i tried the basic method to root latest oxygen os IN2021_11.C.21 with magisk 23 zip through fastboot. i follow all the steps like extract boot img than patch with magisk 23 loader and after that patched boot image flashing with fastboot. but it doesn't work. is there compatibility issue with magisk 23..?? please solve this. and also is there any way to install twrp..?
Pretty sure those old Magisk versions don't support OOS12, I know they don't support A12 either - just use the latest one, 25.1.
Ok brother. I understand. And is custom recovery available for Android 12 oos12..?
aakashishere said:
hello geniuses..!!
i tried the basic method to root latest oxygen os IN2021_11.C.21 with magisk 23 zip through fastboot. i follow all the steps like extract boot img than patch with magisk 23 loader and after that patched boot image flashing with fastboot. but it doesn't work. is there compatibility issue with magisk 23..?? please solve this. and also is there any way to install twrp..?
Click to expand...
Click to collapse
I use magisk 25.1 on the same rom without any issues
Any custom recovery available for that rom..?
aakashishere said:
Any custom recovery available for that rom..?
Click to expand...
Click to collapse
Not yet, just keep an eye on the TWRP thread