Helló eveyone!
I have a little problem here.
I installed some magisk modules on my phone recently. And when I rebooted my phone, under the mi booting logo appeared an opened lock icon and next to it "unlocked" and all my magisk modules disappeared from my phone, what should I do? There wasnt any problems before with magisk. I only instlled some emoji mods and a sound mod now and this happened
(if theres some issue with my post here, I will delete it as soon as I got some help, sorry if I caused trouble just posting here)
Help please
it happen to me too, on Miui 9 from Xiaomi.eu ROM, some modules installed but when i reboot all modules gone.
i have too the opened lock and text " unlocked " , maybe a magisk bug, i've switched to Magisk Beta now, and all modules keep after reboot.
Same for me with Xiaomi.eu-Nightly-Rom on Miui 9.
Device is Redmi Note 3 (MTK-Hennessy).
Magisk-Version is v.15.3 stable.
Module installation always works fine, then after reboot all modules are gone.
First thought that it could be a problem with the f2fs-bug, but data-partition is ext4 formatted.
I searched the forum with a number of key words and didn't find this problem . Have been working on 2 samsung devices with nougat, J730G/ds and A520F. have tried all 2.82 variants of supersu, though my ultimate goal is to be able to do systemless SBIN install to use suhide.
even without the no-verity-no-encrypt patch, Installing 2.82 causes substantial delay in pattern/pin unlock. This is reported sporadically elsewhere on samsung devices with supersu (usually no version mentioned). Not sure on other manufacturers. delay actually seems worse when I just format data and include the no-verity patch when rooting. the lag is also present if I don't root and just put the patch in as well. so both supersu 2.82 and no-verity can independently cause pin/pattern unlock lag.
SuperSU 2.79 is fine, no lag, and impossible with SuHide.
I have done a number of variations on trying to not have encryption without wiping data, etc. I have also tried clearing cache, etc (one post said that worked for them).
Is this a 'known' issue, and is there any possible workaround? Is there something obvious I might be missing?
Any guidance appreciated, I really am banging my head against a wall with this.
edit -
A reply elsewhere says this is due to no-verity patch being integrated into Supersu 2.82. Is there a way to de-integrate it? (is it necessary?)
Might have a solution.
try at your own risk. Expect to lose all data. You can brick your device. Not responsible for bricked devices, lost data, etc. assume all of the above will happen. I had multiple 'corrupt data' boots forcing start-overs etc. a test device is best.
note - you do NOT wipe data, you do NOT flash no-verity-no-encrypt
The issue seems like it is removing forced encryption - that triggers the pattern unlock lag.
What I have worked out so far - 1) clean firmware install
2) reboot to blue screen installing etc., once that is over, boot to download, NOT to android.
3) flash twrp.
4) boot immed. to recovery
5) flash aroma/su config - set 'keep forced encryption' i put systemless sbin install also because I wanted suhide. everything else I left o default
6) immed. flash suupersu 2.82 sr5
7) reboot immmed. to recovery, again (if Ididn't do this part, what followed didnt come out right)
8) reflash supersu as per 6) this is mentioned in chainfire's first post on suhide 1.09, but he didn't suggest rebooting recovery first, that was trial and error.
9) flash suhide
10) finally, boot to android. from this point, data will not mount in twrp.
i have working suhide, passing safetynet, and no pattern unlock lag, and (so far, still testing it) no other apparent abnormalities. will update if i find any.
lots of trial and error and no idea how random it finally working was.
can i flash it while my device already rooted ? im facing the lock screen lag issue.
but my SU is from magisk
leo31 said:
can i flash it while my device already rooted ? im facing the lock screen lag issue.
but my SU is from magisk
Click to expand...
Click to collapse
i do not know at all how this would work. I have started with stock firmware flash every single time.
DullPeon said:
i do not know at all how this would work. I have started with stock firmware flash every single time.
Click to expand...
Click to collapse
that is bad :|
i already found the fixer, just download 3rd lockscreen apps with fingerprint support, now i dont facing any lag while unlocking with any security lockscreen (ex.pattern , password , etc)
but actually this is still annoying me a bit, but as long my lockscreen are not freezing, its oke
thanks for your help bruh! i will try to reflash my rom with newest superSU on weekend
I have the same problem but sometimes it doesnt work at all and i would get locked out of my phone.
Magisk worked fine on the Android P PP2 beta. Just upgraded to the new PP3 and Magisk 16.4 doesn't seem to work. It flashes fine in TWRP, but Magisk Manager says it's not installed. Just want to check if others are experiencing the same before I assume it's just me and start troubleshooting.
I'm running a Pixel XL.
Same in my pixel 2 XL
I tried patching the boot.img and I got an error
I flashed 16.4 on my Pixel with PP3 and it installed fine. Root seems to work as expected, but modules dont install.
Having the s ame issue. Can't unpack and patch boot.img.
I was able to fix this by disabling phone encryption (set unlock to swipe as opposed to pin, print etc'), re downloading the latest Magisk image, flashing it with TWRP, booting Android, running Magisk Manager (which only half worked a this stage), then finally rebooting Android. All is working fine now and I have been able to re-engage encryption and register fingerprints without further issue.
SirLoinOfBeef said:
I was able to fix this by disabling phone encryption (set unlock to swipe as opposed to pin, print etc'), re downloading the latest Magisk image, flashing it with TWRP, booting Android, running Magisk Manager (which only half worked a this stage), then finally rebooting Android. All is working fine now and I have been able to re-engage encryption and register fingerprints without further issue.
Click to expand...
Click to collapse
I flashed 16.4 and for some reason worked... but only couple of minutes then suddenly root dissapeared :/
For me works with no problems.
I disabled all modules (just to avoid problems), dirty flashed dp3 over dp2, removed lockscreen password (again, just to avoid possible problems with twrp).
Booted twrp img, then in recovery:
- flashed latest twrp.zip
- rebooted recovery
- I flashed Flash Kernel just because I like it
- Straight after magisk 16.4
- rebooted.
Then I re-enabled all modules and set the password back. Super smooth and zero problems, root survives every reboot, no crashes or freezes of any kind. Also if I download modules they all works.
Still can't get it installed. I am trying to patch the boot.img file via Magisk Manager.
I get:
Code:
- Device platform: arm64-v8a
- Extracting files Failed!
! Installation failed
Installation went fine for me and root/safetynet work, however after a few minutes it all fails. Rebooting will get it working again for a little while but it will eventually fail after a short time.
djuniah said:
Installation went fine for me and root/safetynet work, however after a few minutes it all fails. Rebooting will get it working again for a little while but it will eventually fail after a short time.
Click to expand...
Click to collapse
I assume you installed through TWRP?
joderme said:
I assume you installed through TWRP?
Click to expand...
Click to collapse
Yes, i flashed through TWRP. I basically have done the same thing TENN3R mentioned above minus a kernel install. I've tried it a few times now with no luck. Pixel XL btw.
What's working:
Wi-Fi
Bluetooth
Mobile Network (Calling, Data, etc.)
Signal Strength
GPS
NFC
Audio (Stereo Speakers)
Camera
Fingerprint Sensor
HDMI
MTP
Call Recording
HWC
Encryption
SELinux Enforcing
OTA Updates
Bugs:
?
Notes:
If you are not on Q BL it will not boot.
I would suggest 3.2.3 TWRP or the included lineage recovery
For encryption to work make sure you are on 3.2.3 twrp and haven't formatted /data with any newer versions, issue described here.
Use a stock unmodified vendor and update whenever available, we are using our own fstab now for optional encryption and adoptable storage support so we don't need to touch the vendor.
If you go back to an official build after this with stock vendor, you will be force encrypted on first boot.
These builds are based on the official lineage device trees and kernel, but with more flexibility and my preferred configuration.
Lineage Recovery will be uploaded with each build and if you will only be running this rom i suggest to switch to it.
Instructions:
Make sure TWRP has been installed and is functional
Download the latest build and latest stock vendor.img that is available (optionally gapps and magisk if needed)
Reboot to recovery
Wipe data and cache (required if you switch from other ROMs)
Flash the vendor image
Flash the latest build (then gapps and magisk if needed)
Reboot
How to update builds?
OTA or manually like below
Do not wipe anything unless stated in the changelog
Flash only the rom.zip and it will automatically reinstall your gapps, magisk etc
use /system/addon.d if you would like to keep system mods after an update
Downloads:
Lineage-17.1: (mega) https://mega.nz/#F!0McClQKJ!ic8c0LEYF3zGSo_Ivv1nSw
Lineage-17.1: (github) https://github.com/synt4x93/OTA/releases
Google Apps: https://opengapps.org/
Telegram Channel:
@godlike9810
Paypal:
synt4x.93
XDA:DevDB Information
LineageOS 17.1, ROM for the Samsung Galaxy S9/+
Contributors
Synt4x.93, Erfanoabdi
Source Code: https://github.com/synt4x93/
ROM OS Version: Android 10
ROM Kernel: Linux 4.9.226
ROM Firmware Required: Q BL / Q Vendor
Version Information
Status: Stable
Created: 01-04-2020
Last Updated: 05-06-2020
temp
Great ROM really smooth but only one issue i have is when i try to record the screen with internal sound (gaming) it will mute the sound from the speaker and it's working fine Evox (sorry for my bad English
Hello everyone! Not sure how many people here already been trying this ROM from the Telegram group, but was wondering if anyone has the following issue. Google Chrome seems to become really laggy in the evening hours on my phone, but is fine during the day. Basically scrolling and animations within Chrome are really slow causing bad performance. Wanted to confirm if it's just me as Rob said the issue doesn't seem to happen with the Note 9 and see if anyone here has any suggestions? I am running DTB4 BL and vendor with TWRP 3.2.3.0.
so everything good other than Android Auto? Well done!
Great news! Thanks a lot for keeping our device alive and updated!
Can't wait to try this one out. I assume it's working fine as a daily driver?
geronimoge said:
Great news! Thanks a lot for keeping our device alive and updated!
Can't wait to try this one out. I assume it's working fine as a daily driver?
Click to expand...
Click to collapse
Yup, been using it for several weeks. No odd reboots and stuff, just very stable.
How can I check for the right BL?
What does it mean "Q BL"?
Thanks
EDIT:
Never mind, I found it! :good:
..ok, stupid question, but where can I get q bl?
Do I need to use odin to flash just bl from one of q roms or is there just q bl to download somewhere?
Great rom, thanks for this, I came from the LOS 16 and LOS 17.1 of the 09/01 and all good until now
Here is a link for download q bootloader
https://mega.nz/#F!oFJ1nK5Z!eWD2AU4CQxWSdA_kxxRkHA
vendor images and bootloader zip are taken from devbase rom by alexndr so big thank for his work
current vendor version
S9/S9+ : DTB5
N9 : DTB6
Hoooly ****, I tried to make dirty flash from LOS 16(with replacing bl and vendor, of course), with just cache and dalvik cache wipe, and everything just WORKS fine.
This is AMAZING!
So:
1. twrp - wipe dalvik and cache,
2. twrp - flash bl,
3. twrp - flash vendor, but vendor from OP(!),
4. twrp - flash ROM,
5. twrp - flash opengapps.
Damn, it saved me reinstalling 132 apps, and setting all accounts all over.
What's great - all settings are kept from previous OS.
Of course, I lost viperfx and all magisk-related plugs(list of plugins is still there, so all I needed to do was reinstalling plugins ), but, still, this is great.
Great, glad all went good for you
Thanks for working instructions and links!
Thanks a lot! :victory:
I guess it's to much to ask for those information from a developer...
Side note: there is a boot loader for DTB5 only, but the modified vendor for LOS is DTB4. It works, though.
I did update from the 09/01/2020, so far found two issues:
1. After installing White Wolfs Kernel, UI seems to crash after unlocking via pattern, returning me back to unlock pattern. Had to wipe and re-install (dirty install of LOS didn't solve the issue ).
2. AFWall doesn't work. Applying rules fails leaving the system without internet access.
First one is not that important, but I'd like a firewall on my device...
Anyway: Thanks for the work on the LOS.
HackAR
DeCo59 said:
Here is a link for download q bootloader
https://mega.nz/#F!oFJ1nK5Z!eWD2AU4CQxWSdA_kxxRkHA
vendor images and bootloader zip are taken from devbase rom by alexndr so big thank for his work
current vendor version
S9/S9+ : DTB5
N9 : DTB6
Click to expand...
Click to collapse
xo.en said:
1. twrp - wipe dalvik and cache,
2. twrp - flash bl,
3. twrp - flash vendor, but vendor from OP(!),
4. twrp - flash ROM,
5. twrp - flash opengapps.
Click to expand...
Click to collapse
Great work! ROM works great, even Google pay is working good!
I just installed your ROM. It is very nice that the keyboard is now bigger then the one of theolder version and my new bluetooth headset is finally working.
Unfortunately, I cannot get ctsProfile to pass.
Does anyone have ctsProfile passing?
Edit: nevermind, should have read the docs of MagiskHide Props, the last module did the config automatically...
All the best,
Daniel
Hack_AR said:
After installing White Wolfs Kernel, UI seems to crash after unlocking via pattern, returning me back to unlock pattern. Had to wipe and re-install (dirty install of LOS didn't solve the issue ).
Click to expand...
Click to collapse
Same here, can’t unlock after installing White Wolf kernel. Furthermore, the phone is in Emergency calls only mode, as if there is no SIM card.
How to “undo” or otherwise solve this?
Hack_AR said:
2. AFWall doesn't work. Applying rules fails leaving the system without internet access.
First one is not that important, but I'd like a firewall on my device...
Anyway: Thanks for the work on the LOS.
Click to expand...
Click to collapse
I have the same problem. I'm still on LOS 16 as a daily driver because of this (and because of its awesome battery live). I will keep testing though...
Also my thanks for the great work on LOS!
oldipp said:
Same here, can’t unlock after installing White Wolf kernel. Furthermore, the phone is in Emergency calls only mode, as if there is no SIM card.
How to “undo” or otherwise solve this?
Click to expand...
Click to collapse
I had the problem that the first boot after upgrade went without problems (or PIN prompt in my case) but after that, when entering the correct PIN, the screen got black and then locked again. If I entered the wrong PIN, the phone told me so.
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Good luck,
Daniel
Speedmatze said:
I'm still on LOS 16 as a daily driver because of this
Click to expand...
Click to collapse
I didn't have the problem with the old 09/01/2020 version, so you ca try it, or wait for the fix
---------- Post added at 12:35 PM ---------- Previous post was at 12:21 PM ----------
Weirdly enough, my system doesn't have this file. BUT, another try of White Wolfs kernel just worked. It seems this is an obsolete file, that some times is left behind confused and causes problems in the kernel.
Hofedan said:
I had the problem that the first boot after upgrade went without problems (or PIN prompt in my case) but after that, when entering the correct PIN, the screen got black and then locked again. If I entered the wrong PIN, the phone told me so.
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Good luck,
Daniel
Click to expand...
Click to collapse
Hofedan said:
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Click to expand...
Click to collapse
It was too late for me to remove that file, because I had encrypted /data, was no longer able to access it from within LOS, and I don’t know if TWRP can decrypt /data. If it happens to you, I would suggest to seize the opportunity while LOS still unlocks on the first boot to delete that locksettings file. In any case, having a backup is a must, because I am not sure this will actually work.