Problem with lineageos updates - Xiaomi Mi A1 Questions & Answers

When I install an update from the Lineageos system this reminds Magisk and the TWRP, and if I install from TWRP you always have error "signature mismatch" even if I downloaded the same update or other updates.

Install update via lineage updater, then boot TWRP Flash magisk and twrp

an expert computer friend of mine said that there should be a configurable device setting, perhaps in the developer settings, to remove the twrp installation which should consequently also not remove magisk. does anyone know the method? even if it is difficult I can do it, or even a method to install via twrp the system that should not give problems whatsoever.

Related

How do I flash Magisk to my Meizu m3 note?

Each time that I boot the phone up into recovery mode and select the system upgrade option it tells me that the firmware is corrupt (for Magisk). I was able to get the latest version of Flyme (6.1.0.0G) flashed to my phone without the firmware corrupt showing, however, I cannot for Magisk. How do I flash Magisk to my phone without the firmware becoming corrupt?
Nox_ said:
Each time that I boot the phone up into recovery mode and select the system upgrade option it tells me that the firmware is corrupt (for Magisk). I was able to get the latest version of Flyme (6.1.0.0G) flashed to my phone without the firmware corrupt showing, however, I cannot for Magisk. How do I flash Magisk to my phone without the firmware becoming corrupt?
Click to expand...
Click to collapse
You cannot flash Magisk zip or any other zip from STOCK Meizu recovery.
You need custom recovery for it.
With STOCK recovery you ONLY can flash official Meizu firmware zips.
Only thing you can do is to root phone with root privileges option in Flyme account section in phone settings (you must have Flyme account created).
After you enable root privileges download Magisk manager APK from official XDA thread and install it(NOT ZIP,ONLY APK FILE!!!!).
And when you install Magisk Manager DO NOT TRY to install modules since you dont have custom recovery.

How to update Magisk?

I have fullmics rom (not sure if that matters) with Magisk installed.
Magisk needs updating, but I just can't figure out how to do it and feel like an idiot now.
In Magisk manager, I press install, go through the confirmation dialogue and then choose "patch boot image file" (I've already downloaded the zip).
I then need to choose a file from that zip to patch the boot image, but I don't have a clue which one to choose. I've tried a few that I guessed could work but no luck and the update process is not self explanatory unfortunately....
The strange thing is that the Magisk manager now also says that Magisk is not installed an the phone is not rooted. Did this break because of the failed update, or is the update failing because I somehow lost root? How can I get Magisk back on my phone, it was part of the installation process with fullmics. Should I dirty flash fullmics again to get magisk reinstalled?
I ended up making a back up in twrp as a precaution before moving on to re-flashing magisk. Strangely enough after rebooting (but before re-flashing magisk) magisk was fine again and also had root back.
No idea what had broken but obviously a simple reboot fixed it.

Rooting OREO (41.3.A.2.24)

I was waiting for a root enabler for oreo (41.3.A.2.24), and I could find https://forum.xda-developers.com/xperia-x-performance/how-to/guide-stock-kernel-root-twrp-drm-fix-41-t3711837.
But this link is for version 41.3.A.0.401 and it does not work for everybody including me.
Since androplus still didn't bring out a new version of his kernel I tried the method from the above link.
But I'm using newer versions than in the description, I use TWRP 3.2.0, Magisk manager 5.2.2 and Magisk 15.2.
I can install the new version, twrp, the new boor image and Magisk 15.2.
I can boot and Magisk runs but the Safetynet control failes and Magisk does not enable root.
On the installation of the boot image, twrp and magisk I got some messages (marked in red)
unable to mount storage
failed to mount
Before I tried with magisk manager 5.5.1 and magisk 15.1 but then I got stuck at boot time at the sony logo.
Does anybody have a way to root Oreo (the latest version), enable DRM and enable root?
Ok I started all over again and I noticed I didn't follow the procedure first time.
So I excluded the FOTA kernel but whatever else I check no full wipe is done, I can always see the previous installed apps, it does not matter if I check Cust-reset, master-reset or reset-wipe-reason, the system is not wiped.
So that's my first problem, how to wipe the previous install.
Flashing the rom seems to be OK, same thing for flashing boot_oreo.img and twrp-3.1.1-0-dora.img.
I'm not sure about twrp 3.2.0.0 because this version is off-line now, so I tried with TWRP 3.1.1.0 and 3.2.1.0 but they all gave me the same result.
Problems start when I have to flash drmfix.zip, safety-net cleaner or magisk 15.2. The procedure tells me the flash is ok but have a look at thet attached images, I get errors while flashing. One picture for drmfix, one for safety-net-cleaner and one for magisk 15.2
After flashing all of this I can boot successfully but when I try to get root in ES File Explorer pro, it does not work. When I go into Magisk and try the afety-net check I get ctsProfile false and basicIntegrity False.
So the rom does work but I do not get root.
I tried all of this with the Italian rom 41.3.A.2.24.R1E ? I can start all over again with the UK version 41.3.A.2.24.R2E but I do not know if this makes any sense.
So can anybody tell me what to do to get it all going?
deboopi2 said:
I was waiting for a root enabler for oreo (41.3.A.2.24), and...
Click to expand...
Click to collapse
1 - Do use always Adrian DC latest fully working TWRP build for dora.
2 - You don't need a 3rd party kernel to achieve that, instead, you can easily create your own one, based always on stock kernel!
Thats the SELinux's problem.
Flash this first then flash magisk
https://forum.xda-developers.com/xp...ment/mod-sony-stock-patcher-xperia-x-t3528148

Can't install november update

1. I booted TWRP to make Nandroid. I saw this error: E:recv error on uevent
2.I opened Magisk Manager/Uninstall/Restore Image
3.Tried to updated Android: failed
4.I rebooted phone and SafetyNet check failed
5.Booted TWRP and flashed magisk.zip
6.SafetyNet check failed, root check failed
So I tried this
1.I booted TWRP
2.flashed magisk-uninstaller.zip
3.rebooted phone
4.updating Android failed, SafetyNet check failed
So I flashed magisk.zip and I have root at least but I am without the November update. Any idea what's wrong?
In TWRP mount /system read-only. You also must revert any changes you've done to system. Flash newest Magisk uninstaller in TWRP > Mount system read-only in TWRP > Boot and try to apply OTA update.
I must say reverting system back to read-only didn't help me. I haven't been able to figure out why my OTAs fail even when Magisk is uninstalled and system r/o. Doesn't really bother me because I flash stock images provided in this forum, so far so good.
PS You might want to skip the November update, I've read only negative things about it (battery drain; SIM PIN bug that will prevent you from booting the phone if you're not using English language).
The problem is that I didn't make any system changes. I could update Android a month ago without any problem. From then on I installed just two apps: Microsoft To-Do & Moy game. I didn't do anything else. Just using already installed apps... Of course, I always used an option "Keep read only" while using TWRP. But something must be broken, even I uninstall Magisk completely via TWRP, Root checker app shows me "root access is not properly installed in this device. Anyway, I think the fastest way to solve my problem, without losing my data, is to flash a fastboot image.

LOS PIE unencrypted updating bootlooping phone

So I'm running the 03/25/2019 Lineage OS microG build for my OP5, it is Android Pie and I have the latest codeworkxx TWRP 03/11/2019 and PIE firmware.
When flashing the rom (clean install) I decided to go unencrypted this time so I used the following force encryption disable zip found bellow after I clean flashed/installed the rom...
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
...followed by flashing magisk right after. Everything worked, LOS PIE is installed and unencrypted/rooted perfectly.
Problem I am having is that now when I try and install the weekly builds through the Android OS updater, it does it's thing, reboots to recovery, installs the update, magisks then re-installs through the survival addon.d script but then the phone just gets stuck into a bootloop. While reading the install messages in TWRP it does mention that magisk is removing dm-verity for what it's worth.
Does this have something to do with magisk or the LOS ROM having an "encrypted kernel" by default and how I am installing an encrypted kernel/update over an unencrypted phone? Or is this some issue with magisk?
Does this mean if I want to flash weekly updates while keeping unencrypted status I will have to dirty flash them by downloading the zip, manually placing it in my storage, booting to recovery, flashing, then flashing the encryption disable zip again and finally Magisk instead of of just pressing a button in the Android OS updater?
Luckily I restored successfully from a backup but I'm wondering is I screwed myself over here setting up my rom without encryption. Never had this issue updating with the weekly builds when my phone was encrypted.
What do you guys think?
Alright well I managed to update my ROM without bootlooping, just like I thought instead of being able to use the built in OS update manager that does everything for you I have to manually download/transfer file to my phone, flash rom update, flash force encryption disable zip and then magisk again.
While this is an alright workaround for now, is there anyway to regain the stock updating functionality built into the rom while remaining unencrypted and having it NOT bootloop my phone each time? What if I want to use addonSU instead of Magisk, I don't think the disable encryption zip works unless you flash Magisk right after unless I have to update the rom, flash the disable zip, flash magisk, remove magisk and then use addonSU.

Categories

Resources