yashsingh1/xdaforums huggingface dataset:
[Magisk] toolhas4degrees:
You have to uninstall from the magisk app, reboot, install old magisk 23 then fastboot flash the patched boot img from that version of magisk.
[Magisk] davidmoore0:
That did the trick. Thanks mate! Glad to be back in the green :')
[Magisk] magjir:
The fix for me was to remove "magisk.db" from /data/adb/. When I downgraded, magisk crashed (as seen in log) and wasn't recognized in app. Only after removal of .db, the older v23000 was correctly started.
[Magisk] xscope44:
I had exactly same issue, so I am going to try uninstall magisk from app now.
[Magisk] xscope44:
This helped me. I am now back on Magisk 23000 with MagiskHide feature.
[Magisk] ssdd28561:
Newest alfa builds still have MagiskHide if you decide not to use Zygisk. So this change is going to canary and stable versions. Module repository is definitely gone.

At this point I'm using https://github.com/Fox2Code/FoxMagiskModuleManager app, that checks module updates from

https://github.com/Magisk-Modules-Alt-Repo

https://github.com/Magisk-Modules-Repo

View attachment 5443155
[Magisk] wiz.wiz:
Hi, I rooted my Pixel 6 (non pro) but also have the issue with "magisk hide" which disappeared.

I understood I had to :

1) through magisk app, click on "uninstall magisk", then reboot system

2) reboot fastboot and flash unpatched boot.img

3) install magisk v23 ? and patch boot.img

=> This step fails : "Unable to unpack boot image, installation failed"

=> Am I using the right magisk version ??? If not, where can I retrieve the correct one ?

4) reboot fastboot and flash patched boot.img

Thanks or your help
[Magisk] Didgeridoohan:
That's not an "issue", it's by design. And v23 won't work on the Pixel 6, you need build 23010 or newer.

A couple of options are available. Stay on the current official Canary and following releases, or use one of the custom unofficial Magisk releases that are available with MagiskHide added back in (you can find them if you look through the general support thread).

As far as I've seen, Deny list is just about as useful for hiding root as MagiskHide (but there are of course differences).

Never use any other source for downloading Magisk other than John's Github (or whatever unofficial build you want to use). That link you're providing/using is not an official source and if you're really unlucky you'll be downloading and installing malicious files...
[Magisk] wiz.wiz:
Hi, thanks a lot for the explanations !

not having Magisk Hide is actually an issue for me. I understood that it's been removed "on purpose" by the author (since he's been hired by Google, strange coincidence no ?), but not having it prevents a few apps from working (Revolut banking app), and the deny list seem not to operate with that app at least.

I will remove the link of my post not to lead other people to that same unofficial source.

I will also look at the unofficial releases, is there one you would recommend ?
[Magisk] Didgeridoohan:
Of course it's not a coincidence that the nature of MagiskHide changed when John joined the Google security team. Changing MagiskHide to the Deny list was already well underway before that though...

I tested the Revolut app on my device right now, and as soon as I added it to the Deny list it stopped complaining about root and started without issue.

I don't use any unofficial builds, so I have nothing to recommend...
[Magisk] wiz.wiz:
maybe I missed something yesterday when I tested it.

I tried again, but my Revolut version (installed from local apk) is too old : I can't install/update as the phone is "not certified" on play store.

I have to look at how to workaround it. There was "magikhide props config" I think, but not sure it is going to work with this magisk version.

Edit : the app "mywellness" seem to detect root despite magiskhide (on my wife's previous phone), but works fine with the deny list
[Magisk] Didgeridoohan:
If you're on the stock Google firmware you're not going to need MagiskHide Props Config. You will most likely need the Universal SafetyNet Fix though, and more specifically the v2.2.0 release (or newer, but that's the latest release as of writing this). Currently only available to the developer's Patreon supporters, but should become publicly available in a not too distant future. That is likely the only way you're going to pass SafetyNet and the your Play Store certified (unless you use some of the experimental unofficial Magisk releases so that you can use earlier releases of the Universal SafetyNet Fix).

Note: to get the Play Store certified once you pass SafetyNet you likely will have to clear data for the Play Store.
[Magisk] wiz.wiz:
Thank you for all this explanation. I will wait for the public availability I think.

Did you use this module to install "Revolut" app, as you tested it ?

I tried to download the apk through a web apk downloader, but it came as a zip file, which I've not been able to install (with pm install, no matter renaming it to .apk or .xapk)
[Magisk] AnonVendetta:
Try renaming it to an apks extension, rather than apk or xapk. It could be a split app. Open the zip first and see if there are apk files with "split" in the name. I use Total Commander or Split APK Installer for these.

It's also possible that it's failing to install because it's not "correct" for your CPU architecture. Like, you can't install arm64 split APKs on a 32 bit only arm device.
[Magisk] wiz.wiz:
no "split" in the name.

I tried with mixplorer and adb shell pm install (and even copying the apks in /data/local/tmp/) :

bruno@PC-Bruno:/media/Donnees/Telephonie/apk$ adb shell pm install com.revolut.revolut_0_apps.evozi.com.apks

Error: Unable to open file: com.revolut.revolut_0_apps.evozi.com.apks

Consider using a file under /data/local/tmp/

Error: Can't open file: com.revolut.revolut_0_apps.evozi.com.apks

Exception occurred while executing 'install':

java.lang.IllegalArgumentException: Error: Can't open file: com.revolut.revolut_0_apps.evozi.com.apks

at com.android.server.pm.PackageManagerShellCommand.setParamsSize(PackageManagerShellCommand.java:572)

at com.android.server.pm.PackageManagerShellCommand.doRunInstall(PackageManagerShellCommand.java:1337)

at com.android.server.pm.PackageManagerShellCommand.runInstall(PackageManagerShellCommand.java:1303)

at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:193)

at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)

at android.os.ShellCommand.exec(ShellCommand.java:38)

at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:24612)

at android.os.Binder.shellCommand(Binder.java:950)

at android.os.Binder.onTransact(Binder.java:834)

at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4818)

at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:8506)

at android.os.Binder.execTransactInternal(Binder.java:1184)

at android.os.Binder.execTransact(Binder.java:1143)

bruno@PC-Bruno:/media/Donnees/Telephonie/apk$ unzip -l com.revolut.revolut_0_apps.evozi.com.apks

Archive: com.revolut.revolut_0_apps.evozi.com.apks

Length Date Time Name

--------- ---------- ----- ----

106860349 1980-00-00 00:00 com.revolut.revolut.apk

ApkPure.com

30411 1980-00-00 00:00 icon.png

ApkPure.com

2961817 1980-00-00 00:00 config.en.apk

ApkPure.com

2576899 1980-00-00 00:00 config.de.apk

ApkPure.com

2548227 1980-00-00 00:00 config.es.apk

ApkPure.com

2527747 1980-00-00 00:00 config.it.apk

ApkPure.com

2556419 1980-00-00 00:00 config.pt.apk

ApkPure.com

24570011 1980-00-00 00:00 config.xxxhdpi.apk

ApkPure.com

2691587 1980-00-00 00:00 config.fr.apk

ApkPure.com

2658819 1980-00-00 00:00 config.ja.apk

ApkPure.com

3142147 1980-00-00 00:00 config.ru.apk

ApkPure.com

57116466 1980-00-00 00:00 config.arm64_v8a.apk

ApkPure.com

2109 1980-00-00 00:00 manifest.json

ApkPure.com

--------- -------

210243008 13 files
[Off-topic] Cleaner007:
Hello!

I'm looking for some good app for disk space reporting. Does anybody know something like this? (i know only Directory Size but not being sure whether its worth using).

Thanks:rolleyes:
[Off-topic] DaveShaw:
I use the old freeware version of SpaceMonger and have done since before it became part of a comercial product.

Letme know if you need the .exe, I'll post it on Monday when I am back at work.

Ta

Dave
[Off-topic] Cleaner007:
DaveShaw, спасибо.:)
[Off-topic] DaveShaw:
пожалуйста, (You're welcome).

I think that's right. :p

Ta

Dave
[Off-topic] Cleaner007:
Yeh that's right. From Russia with love:D
[Off-topic] AllanIsKing:
Directory Report

Hi Cleaner007

Try Directory Report

http://www.file-utilities.com

Cool features

No cute animals
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] xxseva44:
The ir is most likely consumer ir related so, we'll have to tweak it until it starts working
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
I was discussing the same thing with @askermk2000 a while ago and that seems to be the case, as not even gamma kernel had a working IR on the branch he tested, and neither the IR files or the git log of it shows any relevant difference on the IR when compared to Lineage's sources. I will keep the disclaimer about it for now because it makes things clearer as there is some confusion about the IR being a kernel problem, so the less convoluted it is to the user for the time being, the better.

Edit: Also, if you need any logs about the infrared while testing it, i can help (i even have some older ones describing the behaviour). Just hit me up when needed since my device will be mostly used as a development phone for the time being.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] xxseva44:
It's more likely an issue with the implementation of the ir drivers not playing well with consumerIR or vise versa. Atm ir only works on the older versions of gamma as they weren't upstreamed like los 18
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Aethera:
Hello when I try to flash Swan-H918-Stable.zip on an h918 I get "Unsupported device. Aborting..."
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
Huh... that's strange. I must have messed something up during the anykernel zipping procedure on that model. I'm almost pushing an update to the kernel, so i'll be back in a while with a fix for that.

Edit: Yeah, it was something in the script file, i forgot to change the H910 to H918 on that specific variant flashable. Sorry for that.

I just pushed the file with the fixed script for all the models i checked. If you could test that, i would appreciate it.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Aethera:
Just successfully flashed the new Swan-H918-Stable.zip thank you!

$ uname -a
Linux localhost 3.18.113-Swan-g24ffa95cf1b3-dirty #1 SMP PREEMPT Wed Oct 20 00:18:37 -03 2021 aarch64
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
No worries, glad to help.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
Some of those errors are due to the massive amount of debug flags i disabled in the kernel (it still tries to load many of them up for some reason). Are you facing any bugs on the device so far? My H910 also prints many "errors" similar to these but it works just as fine as when it used Lineage's stock kernel, but i didn't test other variants so i don't know if this kernel works fine on them as well.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Aethera:
One thing I'm noticing is that the adb USB connection keeps breaking. I run 'adb shell' and it connects then after a few seconds disconnects. It never did this before.

EDIT: Now it stopped doing it. For a while it kept disconnecting but now it is staying connected.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
That's weird, some time ago when i started taking logs to debug the IR i managed keep running the adb logcat for quite a while with no problems whatsoever. Is there a certain amount of time that it takes to happen?

Edit: Oh, ok then. Might have been some random issue with adb's connection. If any other problem arises, do tell.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Aethera:
Unfortunately the phone is still crashing at random intervals (was happening before using this kernel).

10-31 19:17:56.642 0 0 E : Fatal error on the modem.

10-31 19:17:56.642 0 0 E : modem subsystem failure reason: sleep_target.c:305:.

10-31 19:17:56.647 0 0 E M-Notify: General: 8
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
I see.. well, i tried searching this sleep_target.c that seems to be related in some manner to the problem in the kernel directory but there is no file with such a name. It could be something ROM-related, but i can't rule that out yet. Are there any other logs with more info about it?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Aethera:
I will try to do some various types of log filtering over the next day or so to see if I can get more information.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Aethera:
Looks like most if not all info about sleep_target.c is in Chinese. For example:

https://cloud-tencent-com.translate...auto&_x_tr_tl=en&_x_tr_hl=en-US&_x_tr_pto=nui

This one appears to have more detail: https://www-cnblogs-com.translate.g...auto&_x_tr_tl=en&_x_tr_hl=en-US&_x_tr_pto=nui
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
Yeah, and the problem is... none of the files the article talks about are present in the kernel's source. tlmm_bsp for example also returns no results here. The fact that you log referenced a specific line from the file means it actually is present somewhere, but i'm not able to ascertain where exactly it is. I'll have to look at it in more details later.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Aethera:
It is related to the Qualcomm MSM8996 system-on-chip. Perhaps it is embedded in the firmware. It appears there's some way to enable a debug mode for the modem and access various flags and voltage levels. This would explain why the error seems to be power-related. The device is trying to throttle the voltage to a "bottom current" which is a minimal current when the device is sleeping and for whatever reason it's crashing.

FYI here is a tool which can extract a MSM8996 modem image.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] xxseva44:
What variant? And did you ever crossflash?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
Ok, so it means that those files might actually be located inside the modem partition? I can see how a improper voltage can lead to kernel crashes (Undervolting the SoC's Kryo cores themselves too hard does the same thing, crashing the phone into either a black screen or a green one with some tracing info about the files that caused the problem), but how do we even go about testing if the modem is the one causing the problem? I'm not familiar with the modem images and structures at all so i doubt i would be able to fix those things, especially the voltages since we probably have no voltage table to determine which voltages are acceptable, too high, or too low.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] xxseva44:
His modem partition is either corrupted in a weird way OR he's running the wrong firmware for it, simple reflash of the modem firmware would fix it
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
According to their first messages, it's a H918.

Yeah, that's what i am also assuming after taking a look at the LOS 18.1 thread. It might have something to do with the way he flashed the firmware there, because the non-KDZ files available for the H918 do not include all the things needed to completely revert or update everything, because then it would be just a KDZ but more convoluted.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] xxseva44:
Yea if he's having fingerprint issues then he's on the oreo modem(fingerprint firmware is in the modem partition, why? idk), he'll need to reflash the nougat modem. Isn't too hard to do, he can do it via lgup or fastboot
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] xxseva44:
There are a couple twrp flashables which also restore the nougat firmware
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] minhduongtrung:
Me too, vs995 Cherish os
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
Strange, because the VS995 apparently has the correct device identifiers (vs995 and VS995) in the zip. Does your device show a different string when flashing other zips?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] imrankhan500:
Hello, I am new to all these custom ROMs and stuff, I would like to ask you. can I use Lineage os 17.1, it has a battery drainage issue. so, can I use it on my LG v20 h918? Have A Wonderful Day.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
Well i didn't test it on LOS 17.1 since the kernel is mainly intended for LOS 18.1 and Lighthouse but considering how interchangeable this phone's kernels are, there is a good chance that you can use it there. To do that, just download the zip and open it, open anykernel.sh in a text editor, change the line "do.droidcheck=1" to "do.droidcheck=0", save it back in the zip and then flash it. If the kernel works, i will consider it compatible with Android 10 and make some changes to make flashing it on A10 as quick as it is on A11.

Small edit just for clarification: Since you said you are quite new to this stuff, backup your boot partition in twrp before flashing the kernel, because your phone will bootloop if the kernel fails to work on LOS 17.1. If you have any doubts about the kernel, or just prefer that i make some specific changes to the zip so that you can test it on 17.1, just ask.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] minhduongtrung:
I used Cherish H910 to install my vs995, I tried flashing Swan-H910-H915-Stable.zip and it still failed to install.

Swan-VS995-Stable.zip both October 25th and October 31st failed to install
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
Thankfully the H910-H915 version didn't get flashed, or else you would have probably be stuck in a bootloop. Since you have a VS995, i will get a zip without device checks and host it for you to download. If it flashes and no bugs or glitches happen afterwards, your phone is just using a different model string according to your recovery. I'll be back shortly.

Edit 2: Problem should be fixed on newer kernel zips.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] imrankhan500:
Sir, it's also my daily driver, I can't test it. Since I get most of the calls on it. Sir help me, I am not a much of codder, Lineage os 17.1, drains my battery on "LG V20 h918". so, please help me out I am a noob.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
Sorry but i can't really guarantee you that the kernel will work, but i can give you a zip that MIGHT likely work on android 10 / LOS 17.1 without failing during the flash procedure. But nonetheless i recommend you to make a backup of your boot partition (in TWRP just go to backup, select "boot" and back it up, makes restoring the system if the kernel fails a matter of a few minutes instead of hours) before flashing it. I am telling you that you will need to test it because i do not have a H918, and my H910 is running android 11 as well, so the only report i have for now is that it works on H918 as long as it is running LOS 18.1 or another Android 11-based ROM.

If you need me to make that specific zip for you, just say the word.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] imrankhan500:
Please send me. Do u have anyother customer kernels that will work. I am another question, i have for you, will the volte work. My most problem is the battery life brother.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
-Link removed-.

Unfortunately no, i don't have any other custom kernels specifically for android 10/LOS 17.1. There was a kernel by lybxlpsv tailored for LOS 17.1 but according to their own words, the stock kernel was more stable to be used as a daily driver. As for the VoLTE, it seems to be a ROM problem and not a kernel one because of LG's lack of source codes for it.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] minhduongtrung:
Done! Swankernel has been installed successfully! Thanks!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] imrankhan500:
If i install 18.1, Is there away tio get Volte working?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
Great! If there are any problems or you have any idea of an improvement that can be made to the kernel, please share! I also managed to find what caused that problem you faced on the vs995 zip. The fix for it should be available by default on the next big kernel update that is scheduled to come out in a few hours, hopefully it makes things less complicated in the future.

AFAIK, no. VoLTE is one of those things that are seemingly broken anywhere that isn't LG's stock rom, which is also quite outdated. Talking to one of the ROM devs for this device might shed some light about the current state of that feature.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] josephww:
Latest version of LinageOS H910 (AT&T)

After flash cannot boot past the Lineage OS splash screen with stable and extreme version and also after "Wipe Dalvik Cache".
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
Strange, the Stable version should be working just fine since i only fixed the USB changing when connected to a PC in the newest version. The undervolt changes were quite minimal and the values weren't increased.

Does the phone bootloop with it or does it go to a black/green screen with a stack trace of what's gone wrong?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
Just pushed a small "fix" for what i think is causing that problem. If you could download the latest h910 stable zip, i would appreciate it. If it still fails to boot, it might be the USB fix that's causing problems. Which is weird because it doesn't happen here at all.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] xxseva44:
Try grabbing a logcat, it'll help figure out what the issue is
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] ROMSG:
Works Great! My thermals are massivly improved and it works on Anroid 9 as well. Just have to edit the install script.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
All the way down to Android 9? That's impressive. I'll have to change the first post to account for that then. thank you very much for testing!

Edit: Just to check something... is your device a H910? I pushed a minor change only for it just so that @josephww could test it and i'm not sure if it was fixed there. If your device isn't a H910/H915, then i guess it was something else causing the problem over there.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Electrolite_XYZ:
Wow this Kernel is amazing! Thermals improved massively and the V20 runs much faster and smoother now. I'm able to do things that were impossible before like browse the web while watching Youtube.

Everything is faster while somehow the phone runs much colder. Need to test if I can take a few photos on GCam without crashing.

I'm using H990DS with Lineage 18.1. During throttle test 1 core stayed at 70C while others were around 60-65C (I'm using a thermal pad).

Spoiler content hidden.

I bought a V60 as a replacement but now I don't even need it anymore, it's a shame I can't refund it now. Amazing job and thanks for all the devs keeping this phone alive. Might try Lighthouse later but I'm lazy to back up all my data for migration.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] AShiningRay:
Thanks! Happy to know the kernel is being useful to others as well. And a bit of a spoiler (xxseva already hinted at it in a few places, lol), but there's definitely a lot more coming for the V20, G5 and G6, although i can't share many details about it nor a ETA of when it will arrive. But if/when it arrives, you can expect Android 12 with a kernel that's essentially the best parts of Swan and mk2000 mashed together.