hi
can not install magisk 16.0 on lineage 14.1 for i9100 ?
how fix this ERROR ?
Try this (I can not assure you that this will work, since I don't own your device):
1 - Open your LineageOS build zip with some file manager.
2 - Extract the "boot.img" file to somewhere else.
3 - Now go to twrp, tap install, then install image, find and flash the "boot.img" you just extracted.
4 - Don't reboot yet, go back and try to flash magisk, then reboot if you succeed.
It worked with me once. Worth a try.
--
Have you tried the beta version already?:
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
sajjads24 said:
hi
can not install magisk 16.0 on lineage 14.1 for i9100 ?
how fix this ERROR ?
Click to expand...
Click to collapse
The S II is quite an old device, and I believe it never got officially updated past Android KitKat, right? Might be why...
Even though the OS is updated by a custom ROM, the boot image may lack the necessary parts for Magisk to patch. At least, that's what your log shows...
You might get more help if you ask around in your device's forum.
Edit: Yup... https://forum.xda-developers.com/showpost.php?p=76705332&postcount=25084
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
Hello, Im new and I dont rlly know where to make a thread for my problem so I just decided to put it here.
So I manually updated my LOS 14.1 to 15.1 with the GApps updated as well but after that in the magisk manager app it says that Magisk is not installed. I found a few threads regarding it and I think Im a step away to fixing my problem. The thing is, I dont know how to install TWRP Treble. I cant seem to flash it with the official TWRP as it does not show the img file of it.
My device is Redmi Note 4x mido
Hi there,
Looking for some assistance to root on Lineage OS 17 for my S10. I had previously rooted my stock rom before installing the custom rom. However, I realized that Magisk is not registering on LOS. I tried to reroot via zip on TWRP with no success. Any ideas on how I can root again? Would I have to reroot on my stock rom again before installing LOS?
Thanks
vehz said:
Hi there,
Looking for some assistance to root on Lineage OS 17 for my S10. I had previously rooted my stock rom before installing the custom rom. However, I realized that Magisk is not registering on LOS. I tried to reroot via zip on TWRP with no success. Any ideas on how I can root again? Would I have to reroot on my stock rom again before installing LOS?
Thanks
Click to expand...
Click to collapse
try to patch boot.img from your ROM by using Magisk Manager and flash boot.img from magisk patched in TWRP
ISoreo said:
try to patch boot.img from your ROM by using Magisk Manager and flash boot.img from magisk patched in TWRP
Click to expand...
Click to collapse
could you please walk me through this step by step? sorry this is my first experience in rooting after a long time
vehz said:
could you please walk me through this step by step? sorry this is my first experience in rooting after a long time
Click to expand...
Click to collapse
1. install the Magisk Manager into your phone
2. extracted your rom that you installed to your phone find the boot.img and copy to somewhere in your phone
3. go to magisk manager click install and select "select and patch a file"
4. find your boot.img that your are already copied and select it
5. after finish patched magisk will give you "magisk_patched.img" then reboot to the TWRP recovery
6. select install then select install image
7. find "magisk_patched.img" then select to install in boot.img
8. reboot
ISoreo said:
1. install the Magisk Manager into your phone
2. extracted your rom that you installed to your phone find the boot.img and copy to somewhere in your phone
3. go to magisk manager click install and select "select and patch a file"
4. find your boot.img that your are already copied and select it
5. after finish patched magisk will give you "magisk_patched.img" then reboot to the TWRP recovery
6. select install then select install image
7. find "magisk_patched.img" then select to install in boot.img
8. reboot
Click to expand...
Click to collapse
I've just tried this but now my S10 is stuck on boot warning. Was I supposed to do a full wipe too?
Edit: Resolved now. There was a custom Magisk boot.img specifically for Lineage OS root
vehz said:
I've just tried this but now my S10 is stuck on boot warning. Was I supposed to do a full wipe too?
Edit: Resolved now. There was a custom Magisk boot.img specifically for Lineage OS root
Click to expand...
Click to collapse
Hi @vehz! Same situation here: I'd like to root my S10e on Lineage 17.1. Could you tell me where you found the Magisk boot.img for Lineage OS root? Many thanks!
jonapiron said:
Hi @vehz! Same situation here: I'd like to root my S10e on Lineage 17.1. Could you tell me where you found the Magisk boot.img for Lineage OS root? Many thanks!
Click to expand...
Click to collapse
You will need to do a format/wipe, flash multi_disabler.zip then flash the new updated LOS rom, then Magisk.img
Below link for the updated LOS rom and Magisk .img
This is from the official LOS thread.
https://drive.google.com/drive/folders/1UdPbIbM3luYIiOdXMXb7raAnWLERjssh
beyond0lte folder is for S10E.
vehz said:
You will need to do a format/wipe, flash multi_disabler.zip then flash the new updated LOS rom, then Magisk.img
Below link for the updated LOS rom and Magisk .img
This is from the official LOS thread.
beyond0lte folder is for S10E.
Click to expand...
Click to collapse
Oh I'm so stupid, I had seen the Magisk boot img in the files but ended up using another one... It seems to work now, thank you sooo much!!
It still cannot pass SafetyNet check (ctsProfile), I'll investigate that...
I had the same issue with lineage 17.1 in xperia z2 when using the latest magisk version 21.4 , solved by flashing an older version (magisk version 20.4).
I am trying root Lineage 18.1 on my s10. I have tried differtent magisk-files from TWRP, but still no root access.
What are the required files for 18.1 for Galaxy s10 and steps to get root-access?
Hafizp5100 said:
I had the same issue with lineage 17.1 in xperia z2 when using the latest magisk version 21.4 , solved by flashing an older version (magisk version 20.4).
Click to expand...
Click to collapse
Dude, thanks so much. I faced the exact same problem with my Z2, now it's running magisk just fine. You saved me a bunch of headaches.
i have been using Lineage 18.1 mi mix for a while now. but then i realized it did not come with root management in the settings.
really missed that feature. can anybody show me a way on how to root?
i tried using magisk and stuck on how to extract boot.img from payload.bin there are no payload.bin file on the compressed rom zip
if anybd can show me a simpler way to root the device that would be awesome
thx in advance
Do you have TWRP? If so, I would just download Magisk 21.4.zip and install it from TWRP.
Another option is to get the 22.1 or 23.0 apk, rename it as a .zip and install from TWRP (it's what I am using now).
I have installed the newest magisk, with Orange fox recovery from https://forum.xda-developers.com/t/...y-project-r11-1_1-for-mi-mix-lithium.4334321/
Zero issue, clean magisk apk renamed to zip iirc. (official guide)
Previously issues I had with twrp (touchscreen not working, or one version working with old fw incompatiable with 18.1).
I use a Huawei Enjoy 7 Plus (CMCC, model TRT-TL10A) with EMUI 5.1.3 (Android 7.0). I got my phone unlocked, flashed (a modded version of) TWRP 3.1.1, and then Magisk v23.0 at first. However, my phone bootlooped. Switching to Canary (23001) doesn't help either, probably because its changelog shows that it has no difference to the existing Magisk v23.
So I wanted to open an issue about this on the Magisk GitHub repo. However, it asked me to provide dmesg data, but I have no idea on how to do such a thing when my phone is unable to start up.
Please tell me how to do this. If there is any workaround with the bootloop issue, please let me know. Thanks.
MightyPandora8 said:
I use a Huawei Enjoy 7 Plus (CMCC, model TRT-TL10A) with EMUI 5.1.3 (Android 7.0). I got my phone unlocked, flashed (a modded version of) TWRP 3.1.1, and then Magisk v23.0 at first. However, my phone bootlooped. Switching to Canary (23001) doesn't help either, probably because its changelog shows that it has no difference to the existing Magisk v23.
So I wanted to open an issue about this on the Magisk GitHub repo. However, it asked me to provide dmesg data, but I have no idea on how to do such a thing when my phone is unable to start up.
Please tell me how to do this. If there is any workaround with the bootloop issue, please let me know. Thanks.
Click to expand...
Click to collapse
Don't know how to pull it. But to fix your situation. Flash the stock boot img via fastboot. Remove magisk app. Install canary then repatch your boot img via magisk then flash the patched boot.img through twrp or fastboot
I would try to gain root before flashing twrp. Then you know where the issue lies