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
Related
Has any of you guys tried the newest TWRP 3.2.0.0 for OnePlus 3T? Did you find a bug?
Thanks.
Info: http://www.androidpolice.com/2017/1...g-better-support-oreo-roms-pixel-2-bug-fixes/
Download TWRPfor OP3T from the official site: https://dl.twrp.me/oneplus3t/
I wonder if it triggers dmverity and how to avoid it if we just want to upgrade twrp...
jojlse said:
I wonder if it triggers dmverity and how to avoid it if we just want to upgrade twrp...
Click to expand...
Click to collapse
I assume you flash the updated Recovery followed by the patched firmware, which i assume you already have? I don't even know if the firmware is necessary but whenever i flash anything i also re-flash the patched firmware while I'm at it. No reason not to.
Alright, DM-Verity will be cleared if you flash the newest Magisk beta, and TWRP 3.2.X.X is working fine. I don't think Teamwin would release an official version of TWRP without making sure it's completely free of bugs. It flashes Oreo ROMs (Cardinal Xtended, N2Os) and also flashed OOS 5.0 very well. Add-ons such as Magisk and Magisk Modules flashed flawlessly.
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
[ 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
Read a similar problem from this thread https://forum.xda-developers.com/k20-pro/how-to/redmi-k20-pro-firmware-10-3-8-0-9-6-13-t3939647
I'm already unlocked and I was gonna stick with the China ROM for now, so I flashed Magisk. After an hour I noticed my root access WAS GONE. So tried restarting it and... bootloop! Magisk uninstaller fixed this BUT I want that Magisk. So I kept retrying... Fastboot, flash TWRP(another issue is TWRP wont stick no matter what it will be replaced by stock recovery), Install magisk, bootloop... Rinse and repeat.
I tried 2 methods installing Magisk. TWRP and the Boot Image Patching using boot.img from latest China ROM miui_RAPHAEL_V10.3.12.0.PFKCNXM_75ea367433_9.0.zip
Im running out of ideas, can anyone here help and share how they fixed it? Thanks!
you should change to Xiaomi EU rom, no issues with Magisk.
Try installing ver 18 or 18.1 magisk i had issues with ver 19 and up on pocof1. Also on pocof1 you had to install dfe (disable force encryption) and them twrp wouldnt be replaced with stock boot recovery. Also any update that comes when twrp is installed will rewrite it to stock recovery.
Wipe userdata/factory reset after installing magisk
I have the same issue and resolve it by install OrangeFox-R10.0_8-Stable & Magisk-v20.1.zip.
Hello everyone, i am new here
I know from the official guides of Magisk that you can NOT flash Magisk from recovery or use a custom recovery if you have no ramdisk(if i understood correctly) and that you must patch your recovery and flash it back to the phone using Odin or other flashing software..
So there are this indian videos showing how they rename Magisk.apk to Magisk.zip and flash it from TWRP and its successful even tho Magisk clearly showes "ramdisk: no"...most of the videos use Magisk V22.0
So my question is it really possible to flash Magisk.zip (obtained by renaming Magisk.apk) from recovery(TWRP) without having ramdisk? Has something changef and the developers forgot to update the official guides??
For reference here is one video in English doing that
Magisk works fine ramdisk=no. However I noticed when you set a pin and reboot the TWRP pin shows preboot and does not work to log in. I'm wondering if magisk patched the TWRP recovery instead of stock recovery would this work? Because of this issue I have had to flash several times. I'm using the Cherish GSI and everything works great except the pin issue.
Oukitel K9 Cherish GSI
nation888888 said:
Magisk works fine ramdisk=no. However I noticed when you set a pin and reboot the TWRP pin shows preboot and does not work to log in. I'm wondering if magisk patched the TWRP recovery instead of stock recovery would this work? Because of this issue I have had to flash several times. I'm using the Cherish GSI and everything works great except the pin issue.
Oukitel K9 Cherish GSI
Click to expand...
Click to collapse
Yes, magisk can patch twrp and it seems to work well for me