I need help on flashing TWRP Treble - Device Repair

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

Related

can NOT install magisk v16.0 on lineage 14.1 ?

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

Help problem installing Magisk v.16 on AEX Oreo 8.1 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:
Install TWRP Pitch Black and Install Magisk for Treble ROM

Magisk v.16 not able to install on AEX ROM OREO 8.1

[ 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

[HELP] How do I dump dmesg from a phone that is experiencing bootloop? (using the original OS) // Bootloop on Huawei Enjoy 7 Plus

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

Magisk on Lineage OS 18.1 GSI

Hello. I will describe it briefly:
I'm about to flash my Redmi 6A(cactus), to Lineage OS 18.1 via GSI using OSS(ALPS)-vendor on arm64. I have read some information and it says that installing Magisk could cause a bootloop. I want to know if it is true.
Which image do I want to use - https://sourceforge.net/projects/andyyan-gsi/files/lineage-18.x/
Image - lineage-18.1-20220715-UNOFFICIAL-arm64_bgS-vndklite.img.xz
P.S. I haven't started flashing yet, I want to consider all the little things and conventions before flashing the phone.

Categories

Resources