Unlocked my Bootloader recently.
Flashed almost all the best ROMs available. But can't get root access in any of them except Resurrection Remix. The root access on RR works coz it is prerooted and needs a small addonSU to activate it fully. Coutresy of LineageOS/CyanogenMod.
Magisk would give out "Cannot mount /vendor" "Error:1". I tested it on all the latest builds of all the ROMs(AOSP, AOiSP, dotOS, Cardinal etc..)
Tried flashing Magisk versions out there including the treble version of the beta. Also tried the flashing 'boot.img' trick. Still the same thing shows up.
My device : Redmi Note 4 SD
Recovery : Redwolf/TWRP(tried with both of them)
Has anyone been experiencing the same issue??? Has anyone figured out a solution??
Also, RR also seems to give out the same error when flashing Magisk. When I installed Titanium Backup, it said I have 16 cm-SU installed. Can't find a way to uninstall or remove it either.
uncannyjish said:
Unlocked my Bootloader recently.
Flashed almost all the best ROMs available. But can't get root access in any of them except Resurrection Remix. The root access on RR works coz it is prerooted and needs a small addonSU to activate it fully. Coutresy of LineageOS/CyanogenMod.
Magisk would give out "Cannot mount /vendor" "Error:1". I tested it on all the latest builds of all the ROMs(AOSP, AOiSP, dotOS, Cardinal etc..)
Tried flashing Magisk versions out there including the treble version of the beta. Also tried the flashing 'boot.img' trick. Still the same thing shows up.
My device : Redmi Note 4 SD
Recovery : Redwolf/TWRP(tried with both of them)
Has anyone been experiencing the same issue??? Has anyone figured out a solution??
Also, RR also seems to give out the same error when flashing Magisk. When I installed Titanium Backup, it said I have 16 cm-SU installed. Can't find a way to uninstall or remove it either.
Click to expand...
Click to collapse
I think all the ROMs you listed are Treble ROMs. They require a special Treble version of Magisk which is usually linked in the ROM threads
Noter2017 said:
I think all the ROMs you listed are Treble ROMs. They require a special Treble version of Magisk which is usually linked in the ROM threads
Click to expand...
Click to collapse
I tried the treble versions of magisk too. Even tried the beta. No luck.
Figured it out
uncannyjish said:
Unlocked my Bootloader recently.
Flashed almost all the best ROMs available. But can't get root access in any of them except Resurrection Remix. The root access on RR works coz it is prerooted and needs a small addonSU to activate it fully. Coutresy of LineageOS/CyanogenMod.
Magisk would give out "Cannot mount /vendor" "Error:1". I tested it on all the latest builds of all the ROMs(AOSP, AOiSP, dotOS, Cardinal etc..)
Tried flashing Magisk versions out there including the treble version of the beta. Also tried the flashing 'boot.img' trick. Still the same thing shows up.
My device : Redmi Note 4 SD
Recovery : Redwolf/TWRP(tried with both of them)
Has anyone been experiencing the same issue??? Has anyone figured out a solution??
Also, RR also seems to give out the same error when flashing Magisk. When I installed Titanium Backup, it said I have 16 cm-SU installed. Can't find a way to uninstall or remove it either.
Click to expand...
Click to collapse
So it was a problem with the treble implementation of the ROM. I was installing treble ROMs using the stock TWRP/Redwolf recovery. These recoveries install the ROM but don't work or make the /vendor partition. This has led many people to believe that there is something wrong with their phone. Anyway, flashing a custom treble recovery did the job. Although not each one of them is perfect, TWRP_3.2.1-7_mido-treble by @NFound is the best one.
Solved every problem faced by me till now. Custom Magisk for Redmi Note 4 is available and works like a charm.
Magisk-v16.3-mido-treble
It seems no one faced this issue before, anyway this would help the new comers like me.
Thanks.
Couldn't get
I am using RR ROM Oreo since 2 weeks and finding ways to root it
But can't find any way to do it
Addonsu is not working
Treble magisk is not working
I need to change my recovery
But the ROM ended up encrypting my internal storage
So should I clean data to format and remove encryption
Or I can directly install a new recovery ?
Format then wipe everything. With a help of a pc or a laptop download a treble supported recovery or the Firefox recovery(search it).Then try again.
Related
Hi,
hopefully someone could point me in the right direction.
So I have a Kate device.
It's been unofficially unlocked ( requested code in February, still haven't received anything ), however up until this point everything was working fine.
The problem is I can't dirty update over LOS nightlies for some reason ( both via updater and manual TWRP flash ) - stuck at boot animation ( 30+ mins ) Clean flash works fine. Problem started somewhere in March builds.
I have updated TWRP and I believe I have the proper FW, since everything works when doing a clean flash.
I'm not using any custom kernels, mods or anything like that, just SU addon + opengapps.
Any ideas?
Thanks
No idea...clean flash works...which is strange...have you tried other roms too?
For official unlock, you waited too long for code LOL. I never received any code and im officialy unlocked. You should write to them so they can manually give you permission.
You should flash via EDL latest china dev and then unlock it...
Denis:) said:
No idea...clean flash works...which is strange...have you tried other roms too?
For official unlock, you waited too long for code LOL. I never received any code and im officialy unlocked. You should write to them so they can manually give you permission.
You should flash via EDL latest china dev and then unlock it...
Click to expand...
Click to collapse
Haven't tried others, I enjoy using LOS
As far as unlock goes, unless this is actually the thing that is causing the issue, I'm also just fine with unofficial.
feiks said:
Haven't tried others, I enjoy using LOS
As far as unlock goes, unless this is actually the thing that is causing the issue, I'm also just fine with unofficial.
Click to expand...
Click to collapse
I think it is the su addon.
after u dirty flash, do not install su addon, because your device need to build up dalvik cache.
so after dirty flashing, when the device successfully boot up, reboot to recovery again and flash su arm64 addon.
Thanks for suggestion, but unfortunately it also does not help.
The only thing I haven't tried is not installing su addon at all ( when doing clean flash ), but that kind of defeats the point of having custom rom in my opinion.
Also I couldn't find any references to this ( apart from migration issues back when CM became LOS ) on LOS thread, everything seems to be working fine for everyone else, regardless of unlock or su.
Are there any other partitions that should be wiped upon clean install, besides system/data/cache/dalvik?
Simoom Sadik said:
I think it is the su addon.
after u dirty flash, do not install su addon, because your device need to build up dalvik cache.
so after dirty flashing, when the device successfully boot up, reboot to recovery again and flash su arm64 addon.
Click to expand...
Click to collapse
I don't use LOS , but what I've heard is the latest nightly has made changes to updater app so clean flash ROM and try next build & one more option is to use LOS updater from play store , make sure you have latest TWRP & it's setup after installing ROM
Sent from my Redmi Note 3 using Tapatalk
Use only ZCX twrp.
Updater process ended with ERROR 7 (happening lots now?)
Never or rarely encountered this before but is happening with lots of Kenzo roms..any ideas as to why?
Same here :x
thiagoserrao said:
Same here :x
Click to expand...
Click to collapse
I got Nitorgen OS on but everything else will not work.
rslatara said:
I got Nitorgen OS on but everything else will not work.
Click to expand...
Click to collapse
I'm using Lineage OS, and i can't update :/
may be firmware problem
Actually this is happening because of the updated modem.. all the roms (lineage, nitrogen os, etc) first checks the required modem number and then proceeds to further installation. To solve this.. either go to the meta data folder of your ROM.ZIP and edit the updater script to delete the (modem checking) line.. or elz flash the previous or old modem.. it will work fine
every recovery i flash gives me ERROR 7 :/
i have a 'kate' and befor i used to flash roms without issue. kenzo roms and flash kate modem done.
but phone crashed. and now im back on miui beta 7.10.19 unlocked bootloader flashed twrp (all the twrp possible btw i tried all i could find) they all dont want to flash a custom i tried 7 different ZIP of custom roms... 4 versions of RR 5.7.4 and 2 of 5.8.4, flashed modem zips still error 7
does anybody know how to fix this.....
reggiexp said:
every recovery i flash gives me ERROR 7 :/
i have a 'kate' and befor i used to flash roms without issue. kenzo roms and flash kate modem done.
but phone crashed. and now im back on miui beta 7.10.19 unlocked bootloader flashed twrp (all the twrp possible btw i tried all i could find) they all dont want to flash a custom i tried 7 different ZIP of custom roms... 4 versions of RR 5.7.4 and 2 of 5.8.4, flashed modem zips still error 7
does anybody know how to fix this.....
Click to expand...
Click to collapse
Use redwolf recovery never had this problem, i have a kate.
And recommend you Nitrogen os 8.1 for kate
I'm on redmi note 4 mido, I've installed the latest RR ROM version goes like rr_20180514.zip ( tried all may builds) but installation of ROM and gapps has no issue but can't flash a root like previous RR ROMs.
The SuperSU.zip gets aborted after [sepolicy > failed , aborting] and magisk ends with error 1 ( tried flashing ROM boot.IMG ) no use.
Titanium backup won't work without root and all my data cannot be transfered to may build , anyone with same problem or any solution? Need help
most_curious said:
I'm on redmi note 4 mido, I've installed the latest RR ROM version goes like rr_20180514.zip ( tried all may builds) but installation of ROM and gapps has no issue but can't flash a root like previous RR ROMs.
The SuperSU.zip gets aborted after [sepolicy > failed , aborting] and magisk ends with error 1 ( tried flashing ROM boot.IMG ) no use.
Titanium backup won't work without root and all my data cannot be transfered to may build , anyone with same problem or any solution? Need help
Click to expand...
Click to collapse
You are probably using a Treble ROM, flash Magisk for Treble ROMs. It is linked in your ROM's thread.
SuperSU doesn't work on Treble ROMs
Thanks man, will try
Hey guys, I'm trying to install LineageOS GSI (arm64 A/B) on my Mi A3 and seem to be having some trouble getting the GSI to actually boot successfully.
I have already done my research both on XDA and elsewhere online, yet most threads focused on the device seem to be of little to no use and/or filled with spam replies that only serve to confuse people looking into this.
A quick note regarding the aforementioned threads:
I don't mean to sound disrespectful to the community, but honestly, bashing somebody over why they'd rather install anything but your own fav piece of software is completely ridiculous.
Without further ado, my case goes as follows:
I'm starting fresh with the latest stock firmware, after having unlocked my bootloader ofc (critical too), I've successfully installed TWRP, wiped, installed the system image and yet after rebooting I'm just greeted with good ol' Fastboot, at which point I either directly flash the stock firmware and try again or wipe my data and whatnot (through TWRP, if reinstalled) and still end up with Fastboot.
Therefore, I have to ask you guys:
Has anyone previously successfully installed any GSI rom on the Mi A3?
Did you flash the system img while on stock firmware or a previously flashed custom rom (ie Pixel Experience)?
Is there any need for any special patch similar to the ones used for MIUI based Xiaomi phones?
Did you face any other issues while trying to flash a GSI?
My intention is to eventually install microG using Nanodroid.
Thanks for asking. I was trying to flash Havoc, crDroid and MSM-Xtended Android 10 GSIs but I can't boot the phone.
I have flashed lots of GSIs in the past, but this is really intriguing me, I can't boot on Mi A3. Wiping or formatting data does not solve, neither Permissiver or Disable Dm-verity zips did the job... :crying:
I successfully bootet the LineageOS GSI yesterday. I was not coming from stock though. I think this process should work assuming you already bootet to TWRP:
1. flash the GSI image to system partition using TWRP
2. flash the TWRP installer to keep your recovery
3. (not sure if needed) flash no fde patch
4. optional: flash some other stuff like Magisk and gapps
5. wipe data and dalvik
I think it rebooted to recovery on my first try but worked after flashing everything again. I probably made some mistake on my first attempt but just make sure to try again before giving up.
Also there's this tutorial but it's not at all what I did to get it working:
https://forum.xda-developers.com/mi-a3/how-to/tutorial-flash-custom-rom-mi-a3-t3977169
I don't know what happened, but when I try to flash pixel experience 12 on this using TWRP, it says that "devices on super may not mount
until rebooting recovery", I've tried a lot of fixes but none of them worked, when I flashed orangefox it flashed and worked, but I'm getting a similar mounting error on that as well, please help, I'm desparate
If you want to install a custom rom, use the recommended procedure for that rom. The rom developer gives you a proven procedure.
PE is not intended to be installed from TWRP or OFOX.
StaryMuz said:
If you want to install a custom rom, use the recommended procedure for that rom. The rom developer gives you a proven procedure.
PE is not intended to be installed from TWRP or OFOX.
Click to expand...
Click to collapse
yeah, but i cant even flash magisk or anything.
I normally use Magisk and it goes flash from all recoveries. Only the recovery must correspond with the ROM.
"devices on super may not mount until rebooting recovery"
Click to expand...
Click to collapse
Had the same problem. Solution for me was to use MiFlashTool to go back to stock.
Then flashed Twrp again and I was able to flash custom rom.
ScarletSkies1234 said:
I don't know what happened, but when I try to flash pixel experience 12 on this using TWRP, it says that "devices on super may not mount
until rebooting recovery", I've tried a lot of fixes but none of them worked, when I flashed orangefox it flashed and worked, but I'm getting a similar mounting error on that as well, please help, I'm desparate
Click to expand...
Click to collapse
This is actually how Virtual A/B works. That's not an error.