Develop Bugs

[ROM][All Quarks][8.1][LOS 15.1 Unofficial][Discontinued]

Sorry all, but I will no longer be able to create stable/testable builds. My phone died and I ended up getting a Pixel 2 XL instead. I tried to continue building but compilation has been failing and I can lo longer test anything.
Latest update: 2018-10-13 To view a changelog, you can visit https://review.lineageos.org/#/q/status:merged+branch:lineage-15.1 for a rough idea up to the build date.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi all. I was able to compile this stock build of LOS 15.1 thanks to the efforts/hard works of @bhb27 and those over at Lineage OS. It has some minor extra features (like RR) including notification light, some tiny performance/battery tweaks, and the ability to install Motorola apps. It is otherwise stock LOS 15.1. The other authors/devs and I assume no responsibility if you damage your device somehow.
Please don't feel pressured to update any more often than you wish .
Notes:
Sometimes on the first install it will not find your network/sim card. If so, restart your phone and/or wipe cache.
My recommendations to install:
Install TWRP if you haven't already
3.2.3 - https://www.androidfilehost.com/?w=files&flid=39562 (forum:http://forum.xda-developers.com/mot...recovery-twrp-2-8-7-0-touch-recovery-t3180308)
Perform a backup of your current system/ROM (if coming from another ROM).
Perform a factory reset/wipe (if coming from another ROM).
Install the .zip
Install the appropriate google apps.
http://opengapps.org/. I would think nano or micro is best, ARM, and 8.1
Wipe dalvik/art cache if you install another kernel (best is fgl27's: https://androidfilehost.com/?w=files&flid=278501)
Reboot and enjoy
Here is the link to the latest ROM on the hosting website:
[2018-10-13]https://androidfilehost.com/?fid=1322778262904026799
Previous Builds:
https://androidfilehost.com/?w=files&flid=278725&sort_by=date&sort_dir=DESC
Optional Components:
BHB27 Kernel: https://androidfilehost.com/?w=files&flid=278501
BHB27 Kernel Adiutor: https://www.androidfilehost.com/?w=files&flid=48767
Remove SU/Root: https://mirrorbits.lineageos.org/su/addonsu-remove-arm-signed.zip (Lineage OS extras:https://download.lineageos.org/extras)
TurboToast: https://play.google.com/store/apps/details?id=com.bhb27.turbotoast
I'll be back to post updates fairly regularly (~ every few weeks), but I also work full time in addition to being a dad (those of you who are know how that is ) and won't really be able to respond to PMs very well. The sources I used can be found under the post on XDA here at https://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3811195 (device, vendor, and kernel trees). Thanks and God bless.

Thanks. Besides @bhb27, you've been one of the really consistent contributors for Quark.

Thanks!

Omg, there isn't words.
Thank you BHB27, Calsulfer and all the community.

Hi again all. Here's another update with major fixes (including working bluetooth audio) thanks to @bhb27!
https://androidfilehost.com/?fid=5862345805528043867

Hi, i don't knwo why I have selinux and trust systems alerts, somebody have the same trouble.

Wow thanks so much guys!
Bugs I've found: Magisk v16.6 doesn't work (breaks installing things from the playstore error 963), and using Supersu v2.82 I'm unable to restore apps using Titanium Backup.

rammx said:
Hi, i don't knwo why I have selinux and trust systems alerts, somebody have the same trouble.
Click to expand...
Click to collapse
Selinux is currently permissive, so it will give you a warning until bhb27 can finish the security policies (slightly less secure until then).
Also, the lockscreen bug will be fixed in the next release (kernel issue). You can flash bhb27's custom kernel to fix this with the current version of the ROM as well.

darkghost568 said:
Wow thanks so much guys!
Bugs I've found: Magisk v16.6 doesn't work (breaks installing things from the playstore error 963), and using Supersu v2.82 I'm unable to restore apps using Titanium Backup.
Click to expand...
Click to collapse
Supersu is probably giving you issues since root is already built into the ROM. You would most likely have to remove it using the link in the first post (optional components section). I don't know it's compatibility at that point though.

calsurferpunk said:
Supersu is probably giving you issues since root is already built into the ROM. You would most likely have to remove it using the link in the first post (optional components section). I don't know it's compatibility at that point though.
Click to expand...
Click to collapse
I was having problems with Magisk, not SuperSU. In any case, I removed SuperSU using the script and added back root using the Lineage Root ARM extras script, and I'm still having the same problems trying to restore app data or freeze system apps using Titanium Backup.

darkghost568 said:
I was having problems with Magisk, not SuperSU. In any case, I removed SuperSU using the script and added back root using the Lineage Root ARM extras script, and I'm still having the same problems trying to restore app data or freeze system apps using Titanium Backup.
Click to expand...
Click to collapse
Where you able to make magisk work or just sicked with the built in Su? I was looking for Magisk cause R-tard banks make apps that doesn't work with a rooted phone and magisk can solve that.::cyclops:

E398 said:
Where you able to make magisk work or just sicked with the built in Su? I was looking for Magisk cause R-tard banks make apps that doesn't work with a rooted phone and magisk can solve that.::cyclops:
Click to expand...
Click to collapse
I wasn't able to get Magisk to work, and currently I'm running on built-in Su. I'm waiting for the ROM to get updated in someway that will hopefully fix Magisk compatibility.

Another bug I've found is that sometimes upon reboot it says I have no SIM inserted and I get no cell service. A second reboot usually fixes the issue, but still something to potentially look into.

Hi again all. Here's another update with all of the latest changes:
https://androidfilehost.com/?fid=5862345805528047834

calsurferpunk said:
Hi again all. Here's another update with all of the latest changes:
https://androidfilehost.com/?fid=5862345805528047834
Click to expand...
Click to collapse
Thank you! Your hard work is much appreciated
FYI: This latest update did not fix Magisk (v16.6) compatibility for me. With Magisk flashed, installing apps from the app store fails with error 963, and I can't even install local apks from my sdcard. Uninstalling Magisk and flashing the LineageOS extra SU zip fixes the issue. I prefer Magisk to integrated SU because there are some Magisk modules I like.

darkghost568 said:
Thank you! Your hard work is much appreciated
FYI: This latest update did not fix Magisk (v16.6) compatibility for me. With Magisk flashed, installing apps from the app store fails with error 963, and I can't even install local apks from my sdcard. Uninstalling Magisk and flashing the LineageOS extra SU zip, fixes the issue. I prefer Magisk to integrated SU because there are some Magisk modules I like.
Click to expand...
Click to collapse
Thank @bhb27. He does all the hardest work ?. For the little that I do putting the code together, you are welcome though.

@calsurferpunk
I just tried your new ROM and I really like it. But I too had a problem with the sim not being recognized therefore, no cell service. I drive for a living and have to have reliable service. Don't know if you can solve that, but I'll keep trying your newer updates. Thanks again for all of your hard work.

nnjimmy59 said:
@calsurferpunk
I just tried your new ROM and I really like it. But I too had a problem with the sim not being recognized therefore, no cell service. I drive for a living and have to have reliable service. Don't know if you can solve that, but I'll keep trying your newer updates. Thanks again for all of your hard work.
Click to expand...
Click to collapse
Bhb mentioned this happening before and apparently resetting the cache helps. If not that, sometimes reinstalling clean fixes it. I wouldn't know what causes it, but that's what I had to do when it happened to me once on an older version. I'm on Verizon and it's currently still working for me.

I've done two clean installs and wiped cache and Dalvik cache numerous times. It recognizes my sim card for a few minutes, I make a call successfully, and then I lose service. Any help would be greatly appreciated.

nnjimmy59 said:
I've done two clean installs and wiped cache and Dalvik cache numerous times. It recognizes my sim card for a few minutes, I make a call successfully, and then I lose service. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Were you using the stock kernel (included with ROM) or bhb's (https://androidfilehost.com/?w=files&flid=278501)? I always flash his afterwards (also requires cache reset)
Also, I flashed over the previous ROM version (non clean/dirty flash), so I don't know if installing that first, then the current makes any difference.

[ROM][P905][UNOFFICIAL] CrDroid-5.10 | Android 9.0 20191113

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
This firmware was developed for the p905. It doesn't apply to the p905v at this time because it's bootloader locked and a custom recovery isn't possible.
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using nano gapps.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features
https://github.com/crdroidandroid/crdroid_features/blob/9.0/README.mkdn
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
All
Known Issues
Rotate buggy a bit
Links:
CrDroid Builds
6. 20191113: november security patch: https://drive.google.com/file/d/1Pfu7y84PAaI4zydNm-Yo9GqcCvK0yOwP/view?usp=sharing
5. 20191023: october security patch: https://drive.google.com/file/d/12-h2_sWcYKQUp_Q0gU7j9NlFMTGmM5Rp/view?usp=sharing
4. 20190812: august security patch: https://drive.google.com/file/d/1yq0q2Va6LkavCKiNBO3yqKP-IRkL8MOh/view?usp=sharing
4. 20190708: july security patch, kernel up to orignal msm8974 lineage kernel, small sensors update: https://drive.google.com/file/d/1sDZ9FplHpiGyyuE19BFtdvYsgNNcF2yE/view?usp=sharing
3. 20190528: may security patch: https://drive.google.com/file/d/1ch9ehxLL8jUylr2X1w55MKUDmikhYAiW/view?usp=sharing
2. 20190219: fix flip, fix mic gain: https://drive.google.com/file/d/1BwhkVYPwzrq8ELHE3q_MhhuCejd2BY4E/view?usp=sharing
1. 20190217: https://drive.google.com/file/d/1w7QjUyuTt4YEdBi4RySbmaZg_g3j26ZH/view?usp=sharing
Gapps
https://opengapps.org
Recovery
Use official 3.0.2-0 version from: https://twrp.me/samsung/samsunggalaxynotepro122qcom.html
or use my twrp version: https://forum.xda-developers.com/galaxy-note-pro-12/development/recovery-twrp-3-1-1-0-t3684802
Sources
Sources: https://github.com/crdroidandroid
Device: https://github.com/Valera1978/android_device_samsung_viennalte
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8974
Vendor: https://github.com/Valera1978/android_vendor_samsung_viennalte
Thanks
Thanks to CrDroid team
Thanks to LineageOS team

Thank you very much just flashed it on my P905 running good so far!

Is P905 compatible with P900? I'm not familiar with the pertinent diffrences, if any.

I have recognized 3 things :
The notification ton is playing endless in a loop (e. g. happen after install the App (Battery Charge Limit) and connect the Power.... also after reboot :if the charging Level reached... also after reboot: from the trustagebt
The Mic gain is too low for : sound recorder, recorder from WhatsApp, Phone application from WhatsApp, Livechat(Audio) from Postident.
I try the app Microphone Amplifier. Till a little Mic gain was added, the Record in this app was. ok. Without gain, the volume was to low. Uncomfortable there is. no way to save the gain in the System out from this app.
OK Google for example works without any issues
The P905 does not react anymore of the magnet Flip from the cover to switch the screen on/off

dwkindig said:
Is P905 compatible with P900? I'm not familiar with the pertinent diffrences, if any.
Click to expand...
Click to collapse
Unfortunately P900 and P905 has differ hardware (exynos 5420 vs qcom 800). It's not compatible.

mad0701 said:
I have recognized 3 things :
The notification ton is playing endless in a loop (e. g. happen after install the App (Battery Charge Limit) and connect the Power.... also after reboot :if the charging Level reached... also after reboot: from the trustagebt
The Mic gain is too low for : sound recorder, recorder from WhatsApp, Phone application from WhatsApp, Livechat(Audio) from Postident.
I try the app Microphone Amplifier. Till a little Mic gain was added, the Record in this app was. ok. Without gain, the volume was to low. Uncomfortable there is. no way to save the gain in the System out from this app.
OK Google for example works without any issues
The P905 does not react anymore of the magnet Flip from the cover to switch the screen on/off
Click to expand...
Click to collapse
Thanks for feedback.
Flip - I missed that moment, when I added fixes in kernel for p905. Evening will check flip and build
Audio - look like I took a bit more, already discarded audio fixes. Will check today evening.
playing endless in a loop - need to check it in logs, a bit later, may be today\tomorrow.

Valera1978 said:
Thanks for feedback.
Flip - I missed that moment, when I added fixes in kernel for p905. Evening will check flip and build
Audio - look like I took a bit more, already discarded audio fixes. Will check today evening.
playing endless in a loop - need to check it in logs, a bit later, may be today\tomorrow.
Click to expand...
Click to collapse
Hi Valera, it doesn't flash in my device (a p905 that worked well with your previous images). It says:
E3004: This package is for device: viennalte, viennaltexx; this device is .
Updater process ended with ERROR: 7
Error installing zip file ...
I wiped it before, but still it doesn't work.

ultraradical said:
Hi Valera, it doesn't flash in my device (a p905 that worked well with your previous images). It says:
E3004: This package is for device: viennalte, viennaltexx; this device is .
Updater process ended with ERROR: 7
Error installing zip file ...
I wiped it before, but still it doesn't work.
Click to expand...
Click to collapse
This is twrp question (it cannt return name). Look like you have old one.
In any way - right now you can remove check:
extract from crDroidAndroid-9.0-20190217-viennalte-v5.1.zip file: \META-INF\com\google\android\updater-script
remove first 2 lines (assert(getprop("ro.produ......................................)
and add updated updater-script back in archive

Valera1978 said:
This is twrp question (it cannt return name). Look like you have old one.
In any way - right now you can remove check:
extract from crDroidAndroid-9.0-20190217-viennalte-v5.1.zip file: \META-INF\com\google\android\updater-script
remove first 2 lines (assert(getprop("ro.produ......................................)
and add updated updater-script back in archive
Click to expand...
Click to collapse
Thanks. I opted for installing your TWRP and now it does flash and everything works very well (including hotspot), except the microphone which records too low (I suggest you to look for noise cancelation problems).

I believe, I must check, which version I've installed CM or CRDrois... I'm not sure in this moment... Both versions were released at the same time

OK, the first flash from yesterday was CM.
Today I try this Rom:
Simular with sound loop, if I connect the Power for charging (Google is updating all Apps) Only chance to get it silent : push all to 0 (sounds) the tone is parallel to all other sounds.
With this rom I haven't get Magisk Manager to defekt root (Magisk 18.1). It wasn't an issue with CM. With this rom the manager doesn't detect root???
Maybe it's about the app SuperSu from Playstore? Haven't test it right now. I just flash the ROM one again (wipe cache/data/dalvik) Internal SD not. With CM wasn't it possible to mount an USB Stick via OTG cable.
I try to install SuperSU (root & app) afterwards and also to mount an external USB.......

Short update ;
In this rom I can disable the charging notification... (CrDroid settings, near on right hand) the loop is away... that's the good news.
The bad one : I don't receive root access : nor via SuperSu nor via Magisk... Any Hints? A short time I could see teh root settings in the Dev menu, but the corresponding apk did not see root in anycase

mad0701 said:
Short update ;
In this rom I can disable the charging notification... (CrDroid settings, near on right hand) the loop is away... that's the good news.
The bad one : I don't receive root access : nor via SuperSu nor via Magisk... Any Hints? A short time I could see teh root settings in the Dev menu, but the corresponding apk did not see root in anycase
Click to expand...
Click to collapse
Yes, in CrDroid no root options in devs.
But latest Magisk is working great. Install latest Magisk 18.1, then boot and manually install Magisk Manager apk file.
You can do check "safery net" in the magisk manager - it will complete pass.
P.s. mic fixed, flip should fixed too (but I cannt check it right now) - I can make small update for draft check.

Valera1978 said:
Yes, in CrDroid no root options in devs.
P.s. mic fixed, flip should fixed too (but I cannt check it right now) - I can make small update for draft check.
Click to expand...
Click to collapse
I would be interested in an update to check flip cover.
Thanks a lot for continuing the work for that great tablet!

Valera1978 said:
But latest Magisk is working great. Install latest Magisk 18.1, then boot and manually install Magisk Manager apk file.
.....
Click to expand...
Click to collapse
I have used the same Version.... but the Manager 7.0 doesn't detect the Root (18.1) . I have flashed 18.1 some times, reboot ... the Manager didn't saw root. I checked this 3 times ... in between the CM Version ... no luck ?!?!?
Does you install root systemless or let you TWRP patch the System partion ?

Just installed this, Netflix doesn't seem to be working. Can't install it from the play store. (The app is not compatible with this version)

Mad07 said:
I have used the same Version.... but the Manager 7.0 doesn't detect the Root (18.1) . I have flashed 18.1 some times, reboot ... the Manager didn't saw root. I checked this 3 times ... in between the CM Version ... no luck ?!?!?
Does you install root systemless or let you TWRP patch the System partion ?
Click to expand...
Click to collapse
Just checked in the latest 20190219:
1. install crdroid, magisk
2. load into the firmware. install the magisk manager
3. back to recovery and reinstall magisk
4. load firmware

Yesterday, I forgot my eyeglas at work... so only reflash a backup was possible.
In the evening, I give the 19.02 Version a new try.
I'll believe, I know why Magiask Manager didn't see the root: There was also a Bug-Report in the Magisk-Thread, that, if the old Manager is in the Background, the new Manager didn't see Root. On other Hand, I've read, that Magisk dedect root simular as SuperSu. The SuperSu Manager was automaticaly installed from Google Store during Setup the P905 at the first Startup.... I don't should Forget to uninstall SuperSu after first boot
---------- Post added at 12:01 PM ---------- Previous post was at 11:58 AM ----------
Bluewave653 said:
Just installed this, Netflix doesn't seem to be working. Can't install it from the play store. (The app is not compatible with this version)
Click to expand...
Click to collapse
Same as it was in CM 18 (Orego) I've download the apk direct form Netflix ( you can found the link via help on the Netflix HP )
https://netflixhelp.s3.amazonaws.com/netflix-4.16-200217-release.apk

New try with Version 2
Magisk is woerking after uninstall SuperSu
FlipCover Witz Magnet works
Problems:
After each reboot, the Tablett forgot the Standard Launcher (Nova) and New keyboard(Swiftkey)
If the Tablett shoot down with power cable, the shoot down looks like a litte bit irretation
Also it is not possible to Boot the Tablett Düring active charging.
The charging loop sound just be disabled in the settings
Netflix was installed Form the APP store before rooting, hide Magisk, an nupdate was received, working
Thats the first impression after a few Minuten

Usb OTG looks like, that it doesn't work.
There is in this moment no reaction, if I insert an USB with an OTG cable.
Maybe I must change something in the Dev-Settings?
Gesendet von meinem SM-P905 mit Tapatalk
---------- Post added at 06:17 AM ---------- Previous post was at 05:33 AM ----------
The notification Ton has a problem at all, not only with the charging cable. If a notification occurred, the ton is playing in a loop till I pull down the tiles/notification from the top.
I would expect, that this ton is played only one time

[Install] Xposed / Pixel Always On Display Module [7T/7T Pro]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to get EdXposed working on 7T/7T Pro (Also Pixel Always On Display Module)
Outdated Method
Requirements :
Custom Magisk - Solohsu (After installing nornal magisk Change Update Channel to custom in Magisk settings - Paste the below link - Update Magisk and Magisk Manager ) Note : I couldn't Pass safety net with Solohsu Magisk though
https://raw.githubusercontent.com/solohsu/magisk_files/master/custom_builds/release.json
Riru Core 15+ (Magisk Module)
EdXposed Sandhook v0.4.6.0+ (Magisk Module)
Edxposed Manager (app)
AOD Module by RetroFX
https://www.coolapk.com/apk/com.retrox.aodmod
Tested on OOS 7T and 7T Pro
Blacklist Chrome and Webview in EdXposed if Chrome crashes.
How to get out of a magisk module bootloop without data loss https://forum.xda-developers.com/showpost.php?p=80654897&postcount=3​
EDIT 1 :
Taichi 5.1.5+ is working flawlessly along with safetynet passing. Bootloop issue is fixed. (Official Magisk build is supported)
Modules i tried and working fine :
AOD (works better with taichi compared to EdXposed)
MINMINGUARD
INSTAPREFS
RE ENABLE SCREENSHOT
EDIT 2 : (23 Jan 2020)
New EdXposed supports Official Magisk build
https://forum.xda-developers.com/showpost.php?p=81543921&postcount=62

I managed to get Edxposed v0.4.6.0 (YAHFA) installed with Riru-Core on my OnePlus 7t. Any earlier versions of Edxposed made my phone unable to boot.
I wasn't able to get any modules to work though. The logs kept saying "Cannot load any modules because /data/user_de/0/org.meowcat.edxposed.manager/conf/modules.list was not found"
After some quick google-fu I found this bug report with the same issue: https://github.com/ElderDrivers/EdXposed/issues/310
It sounds like it might be an issue with SELinux. I attempted to set SELinux to permissive, but am unsure if it worked. . . . Long story short, I gave up and wiped my phone clean.
Hope this helps someone out that is smarter than me with this stuff!

sk801 said:
I managed to get Edxposed v0.4.6.0 (YAHFA) installed with Riru-Core on my OnePlus 7t. Any earlier versions of Edxposed made my phone unable to boot.
I wasn't able to get any modules to work though. The logs kept saying "Cannot load any modules because /data/user_de/0/org.meowcat.edxposed.manager/conf/modules.list was not found"
After some quick google-fu I found this bug report with the same issue: https://github.com/ElderDrivers/EdXposed/issues/310
It sounds like it might be an issue with SELinux. I attempted to set SELinux to permissive, but am unsure if it worked. . . . Long story short, I gave up and wiped my phone clean.
Hope this helps someone out that is smarter than me with this stuff!
Click to expand...
Click to collapse
Appreciate the info. I also gave it a try when I got my device yesterday.
If you don't want to have to wipe your device after tinkering around with Magisk modules, you can use fastboot to boot the image "fastboot boot image-new.img" (not flash) created by Tulsadiver in this post(https://forum.xda-developers.com/showpost.php?p=80547561&postcount=46), then delete the modules in Magisk Manager, and reboot. No data lost.

Thanks to your post i tried to install Xposed and it worked, but no module is working. I don't know how to set SELinux to permissive and if this solves the issue
I've read something about a custom Magisk Version to allow "those sepolicies present" but you have to flash this via TWRP - which we don't have on the 7T ... hm, i'm pretty lost

sk801 said:
I managed to get Edxposed v0.4.6.0 (YAHFA) installed with Riru-Core on my OnePlus 7t. Any earlier versions of Edxposed made my phone unable to boot.
I wasn't able to get any modules to work though. The logs kept saying "Cannot load any modules because /data/user_de/0/org.meowcat.edxposed.manager/conf/modules.list was not found"
After some quick google-fu I found this bug report with the same issue: https://github.com/ElderDrivers/EdXposed/issues/310
It sounds like it might be an issue with SELinux. I attempted to set SELinux to permissive, but am unsure if it worked. . . . Long story short, I gave up and wiped my phone clean.
Hope this helps someone out that is smarter than me with this stuff!
Click to expand...
Click to collapse
Thanks for sharing info!
Maybe I would give a try to Tai Chi. I badly want AOD with no notification LED in our device.

cucumbersmell said:
If you don't want to have to wipe your device after tinkering around with Magisk modules, you can use fastboot to boot the image "fastboot boot image-new.img" (not flash) created by Tulsadiver in this post(https://forum.xda-developers.com/showpost.php?p=80547561&postcount=46), then delete the modules in Magisk Manager, and reboot. No data lost.
Click to expand...
Click to collapse
That's super helpful! I'm definitely going to try that the next time I mess around with things.

For anyone wondering, Tai Chi module is not working as well. Reboots into fastboot.

I gave Edxposed v0.4.6.0 (Sandhook) a try and it boots to the bootloader, as I suspected it would. Tried with both Magisk v20 and Magisk Canary.
From what I've read they have xposed working on the OP7 and OP7Pro. Haven't read anything about the OP7TPro yet, but I'm guessing it'll boot to the bootloader like the OP7T does.
Hopefully OnePlus sent or will send out phones to one of the devs who uses xposed like C3C076 who created Gravitybox.

Updated OP to get XPOSED and AOD working.

Does it work with Greenify? I tried it with normal YAHFA EdXposed and Greenify didn't recognize the module while EdXposed did "activate" it... Weird

Aswin08 said:
Note : I couldn't Pass safety net with Solohsu Magisk though
Click to expand...
Click to collapse
You can use the No Device Check xposed module (https://repo.xposed.info/module/com.pyler.nodevicecheck) to at least get "ctsProfile: true". Unfortunately, basicIntegrity will still be false.

Hey OP!
The OP7T Pro has an installer for those that aren't rooted yet and want the modded Magisk version for EdXposed compatibility and it should work on the 7T non-pro.
[Magisk][ROOT][EdXposed]Auto install tool - Magisk Installer for OnePlus 7T Pro = (https://forum.xda-developers.com/7t-pro/how-to/magisk-auto-install-tool-magisk-t4001471)
I was already rooted, so haven't tried it myself, but it may speed up the process for those who aren't yet rooted.

cucumbersmell said:
Hey OP!
The OP7T Pro has an installer for those that aren't rooted yet and want the modded Magisk version for EdXposed compatibility and it should work on the 7T non-pro.
[Magisk][ROOT][EdXposed]Auto install tool - Magisk Installer for OnePlus 7T Pro = (https://forum.xda-developers.com/7t-pro/how-to/magisk-auto-install-tool-magisk-t4001471)
I was already rooted, so haven't tried it myself, but it may speed up the process for those who aren't yet rooted.
Click to expand...
Click to collapse
Yeah I checked it, but am not sure if they have used same custom version of Magisk like here or different.
If its same thn safetynet would fail again.

Edexposed is up and running! For some reason my safetynet has no problems. I have no idea why.
So far I have MinMinGuard and Greenify working. GravityBox doesn't work, but I can definitely live with that for now.

sk801 said:
Edexposed is up and running! For some reason my safetynet has no problems. I have no idea why.
So far I have MinMinGuard and Greenify working. GravityBox doesn't work, but I can definitely live with that for now.
Click to expand...
Click to collapse
Which one did you use? I am looking to install Greenify also...
PD: Have you noticed (although I think it is too soon to ask) any battery improvements with Greenify?

sk801 said:
Edexposed is up and running! For some reason my safetynet has no problems. I have no idea why.
So far I have MinMinGuard and Greenify working. GravityBox doesn't work, but I can definitely live with that for now.
Click to expand...
Click to collapse
I got what you got in post#2. So, wondering what's your steps now?

sk801 said:
Edexposed is up and running! For some reason my safetynet has no problems. I have no idea why.
So far I have MinMinGuard and Greenify working. GravityBox doesn't work, but I can definitely live with that for now.
Click to expand...
Click to collapse
Are you using this as your Update Channel in Magisk?
https://raw.githubusercontent.com/solohsu/magisk_files/master/custom_builds/release.json
Which version of EdXposed are you using?
EdXposed-SandHook-v0.4.6.0_beta.4471
or
EdXposed-YAHFA-v0.4.6.0_beta.4471
Gravitybox is the main reason I use xposed, but I've also got modules for Burnt Toast Revived and Smooth System Progress Bars running with no issues.
It's great getting xposed features through EdXposed so quickly on newer android versions! I remember the wait for xposed back in the day.

Poesini said:
Which one did you use? I am looking to install Greenify also...
PD: Have you noticed (although I think it is too soon to ask) any battery improvements with Greenify?
Click to expand...
Click to collapse
zyu0090 said:
I got what you got in post#2. So, wondering what's your steps now?
Click to expand...
Click to collapse
cucumbersmell said:
Are you using this as your Update Channel in Magisk?
https://raw.githubusercontent.com/solohsu/magisk_files/master/custom_builds/release.json
Which version of EdXposed are you using?
EdXposed-SandHook-v0.4.6.0_beta.4471
or
EdXposed-YAHFA-v0.4.6.0_beta.4471
Gravitybox is the main reason I use xposed, but I've also got modules for Burnt Toast Revived and Smooth System Progress Bars running with no issues.
It's great getting xposed features through EdXposed so quickly on newer android versions! I remember the wait for xposed back in the day.
Click to expand...
Click to collapse
So after about 24 hours of running edexposed I started noticing some bugs. Mainly I stopped receiving text messages until I rebooted my phone. I experienced the same thing and worse on my last phone the Essential PH-1 when things like this weren't really supported. I don't know what causes it. So be wary and don't blame me if a bricked phone happens or your alarm stops working and you're late for work. (Don't ask me how I know )
Nevertheless I followed what @Aswin08 has in the first post:
Update Magisk through Solohsu channel:
https://raw.githubusercontent.com/solohsu/magisk_files/master/custom_builds/release.json
Install Riru-Core through Magisk download
Install EdXposed-SandHook-v0.4.6.0_beta.4471
https://github.com/ElderDrivers/EdXposed/releases/tag/v0.4.6.0

sk801 said:
Install EdXposed-SandHook-v0.4.6.0_beta.4471
https://github.com/ElderDrivers/EdXposed/releases/tag/v0.4.6.0
Click to expand...
Click to collapse
I'm running the YAFHA version and was trying to determine if one is performing differently than the other in regards to Safety Net, modules that work/don't work, etc.

cucumbersmell said:
I'm running the YAFHA version and was trying to determine if one is performing differently than the other in regards to Safety Net, modules that work/don't work, etc.
Click to expand...
Click to collapse
Have you noticed any instabilities on YAFHA? With any modules or the system in general?
It would be nice to a have GravityBox working and stable on this device.

Magisk 24.1 downgrade: warning!

This morning Magisk notified me about the update available (from 23.0 to 24.1). To cut the long story short, it was a complete failure and I was able to revert back to 23.0.
First upgrade went unsuccessful. Magisk stopped loading. Root was lost. Yet it has succeeded to write something into boot, so uninstalling app and reinstalling 23.0 didn't help. Reboot into patched BL didn't give 23.0 root permissions to patch the BL. I have succeeded to patch stock BL with 24.1 and boot into that, then install 24.1. This has root but fails safety net. Now you need to manually flash safetynet-fix-v2.2.0.zip because Magisk does not do magisk hide anymore. That is lost and module library is lost, plus safety net check tool is lost too. OK, with the fix it can pass the basic check, but for example Citi mobile app sees the root anyway. I have decided to downgrade to 23.0 because I only see a loss in functionality without any benefits.
Now you cannot patch BL with 23.0 if you have 24.1 there. You cannot do it if you flash stock BL but have traces of 24.1 app. The only thing which worked for me: in the functional 24.1 app select 'uninstall magisk', 'complete uninstall', then do root from start: install app 23.0, boot into patched with 23.0 BL, direct install from the app. Half a day is lost.
To prevent it from offering any further upgrade I went into app settings, selected custom update channel and pasted there a link to the 23.0 manifest from github. So long as the project is there that shall work.
Bottom line: beware magisk above 23.0!

Bro , you got wrong, just upgraded magisk 24.1,
please read the changelogs of new version ....
https://github.com/topjohnwu/Magisk/releases
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

unknow91 said:
Bro , you got wrong, just upgraded magisk 24.1,
please read the changelogs of new version ....
https://github.com/topjohnwu/Magisk/releases
View attachment 5522143View attachment 5522145View attachment 5522147
Click to expand...
Click to collapse
I was not happy with the whole experience and with the final result when it was finally working. If someone is like me here is the warning and the way to downgrade or prevent an upgrade.
Then an important thing to note: this is the point when the author went to the other side of the barricade, which is reflected in the changelog. From this point it will be a completely different app.

magisk hide not working?

So bad. Same Problem. Magisk Sygisk not working with XPosed. I need Xposed and Magisk Hide/Sygisk.
Thats a wrong change. Wjy they do that? Its so bad. It was wokring and in a new version not. Bad change in Magisk history.

To prevent it from offering any further upgrade I went into app settings, selected custom update channel and pasted there a link to the 23.0 manifest from github.
Click to expand...
Click to collapse
@rampitec, can you please share the link?

MasterBody said:
magisk hide not working?
Click to expand...
Click to collapse
It is removed from magisk. That's in the whatsnew.

thexile said:
@rampitec, can you please share the link?
Click to expand...
Click to collapse
That's the stable 23.0 from github: https://raw.githubusercontent.com/t...4e59f631280cc26ccc6d40a7cf04f7f37/stable.json

MasterBody said:
magisk hide not working?
Click to expand...
Click to collapse
setting, configure denylist

@rampitec:
You're my liberator after I spent hours with that crap. I wonder how you came up with the URL as I could only find the resolved host topjohnwu.github.io mentioned a Wireshark capture to see what the Magisk app tries to retrieve when the default "stable branch" is selected. Maybe I was overcomplicating things.
Anyway, while I might be missing something here in general, it is difficult not to indulge oneself in a rant because what kind of a retarded bull**** is that to remove a feature (whether being replaceable by that Zygisk stuff with yet again addition effort or not yet to be seen) which allows to get apps at least halfway running by hiding the fact of having root access (whereas the necessity also only arises thanks to moronic programming and nowadays pseudo-security paranoia, especially by insecure-by-definition banking apps on the very same device) with no damn easy way to downgrade again or at least select the version one wants.
It is beyond comprehension why also that Magisk manager doesn't offer to simply select the version of preference in case a newer one breaks what was working before. God forbid, instead, even the version 23.0 apparently tries to load parts of the newer 24.1 one now which leads to (non-working) duplicates of the manager ("Magisk" & by default "Settings" then) instead of repackaging itself to only one instance of course.
It is annoying enough that regular application providers forces users into that constant having-to-update-crap but it is almost real life satire for me that even nominally sophisticated ones such as that John Wu Magisk guy* follows the same idiocy.
* who owes me hours of my lifetime while I owe you at least a beer, rampitec!

Everyone needs to start posting their devices and if they are 64 bit ONLY or 64 bit and 32 bit capable because Magisk 24.1 does not support any device that supports 32 bit. If you subscribe to TopJohn Wu, on Twitter, you get notifications with explanations.
https://twitter.com/topjohnwu?t=e4SCxqjXOBnGIqQLc1uNJg&s=09
We can not understand why you get the results you have unless we know your device and OS and you need to know if your device is 64 bit ONLY, or 64 bit and 32 bit capable.
Pete R

little-endian said:
@rampitec:
You're my liberator after I spent hours with that crap. I wonder how you came up with the URL as I could only find the resolved host topjohnwu.github.io mentioned a Wireshark capture to see what the Magisk app tries to retrieve when the default "stable branch" is selected. Maybe I was overcomplicating things.
Click to expand...
Click to collapse
Not much of my work really. Found a link on youtube how to set the channel to some version. Go to github magisk repo, browse for needed version, select view file, select "raw", copy the URL of the page. This is the update channel.

Thank you! It worked for me. After going back to 23, I have changed the update channel url to 0.0.0.0, so there is no update at all. And it's back to normal again.

rampitec said:
That's the stable 23.0 from github: https://raw.githubusercontent.com/t...4e59f631280cc26ccc6d40a7cf04f7f37/stable.json
Click to expand...
Click to collapse
Application hiding process is done, thank you very much. I've been editing the 23.0 version with apktool m for hours. I couldn't think that only the url link would be the solution to get rid of the version upgrade, I was surprised and a very good idea came to my mind. I will integrate the url into the classes.dex file. The new version is a complete disgrace, too bad, don't install it. Tr to En Google Translate

Have you ever seen that Magisk 23 recognizes the root but when update it gets N/A and the app doesn't work but SuperUser still get access. I tried to do trough Path Boot andZip Odin(S7 Edge Android 8.0)
I formatted the device, re-do Stock Rom but dont work.
the App 24, 24.1 or Canary keeps not working (N/A). Less than 8.0.7 work normally
I applied a custom with Android 10,11 and 12. It works

You can patch boot.img over magisk 23.0 apk installer in android and flashed this patch_magisk_boot.img over fastboot / adb on pc. Magisk 23.0 is now work. Downgrade 24.1. Magisk Hide is back and edxposed works.

tI tried to do this, but the magisk 23 app doesn't allow me to patch without updating to 24.1 first..

RootPoG0 said:
tI tried to do this, but the magisk 23 app doesn't allow me to patch without updating to 24.1 first..
Click to expand...
Click to collapse
uninstall magisk befor. magisk root and app.

rampitec said:
...Half a day is lost...
To prevent it from offering any further upgrade I went into app settings, selected custom update channel and pasted there a link to the 23.0 manifest from github. So long as the project is there that shall work.
Bottom line: beware magisk above 23.0!
Click to expand...
Click to collapse
rampitec said:
That's the stable 23.0 from github: https://raw.githubusercontent.com/t...4e59f631280cc26ccc6d40a7cf04f7f37/stable.json
Click to expand...
Click to collapse
Thank you! I had a feeling something weird was going on and I was ignoring the update notification for a few days now. Good thing I did some digging before installing magisk 24.1.

Hello! I'm on a galaxy s9+ running android 10.
I didn't pay attention and clicked on update, and i regret it so much!
i am on magisk 24.1 with zygisk and ramdisk both set to "yes".
I have the uiversal safetynet fix v2.2.1 and google play services and play store hidden on the denylist
I can't pass safetynet, it fails on "basic integrity" and on "cts profile match"
so upset i updated!

[HELP] Magisk question

Hi!
Yesterday i did fresh install / ROOT my RN8P (EEA - V11.0.3.0.PGGEUXM) after long time and i installed magisk V23 (to test if Magisk hide working yet on some app) but when im tryed to
install SafetyNet (V 2.1.1) it tell me to install Riru but to install Riru now i have to install Magisk V24 altleast.....
So my question is...its better i install again last version of magisk (V25.2)?
There is any module that working like magisk hide? i was out of modding for some month so im not up to date yet....
Any answer will be apprecitated ty!

Yes, I prefer installing Magisk 25.2 as it comes with Zygisk which hides itself from other apps.
If that still doesn't works then you can install Shamiko. A module for Zygisk which hides root completely from the device.
If your device doesn't pass the SafetyNet test after installation then it's probably because of the Magisk patched image flashed into the device since nowadays apps can detect if it's a stock android or not.
But I am pretty sure that there are other modules to hide that too.
Sent by me from A50s with TWRP and S12 Revolt Corvus OS.

Someone Anyone said:
Yes, I prefer installing Magisk 25.2 as it comes with Zygisk which hides itself from other apps.
If that still doesn't works then you can install Shamiko. A module for Zygisk which hides root completely from the device.
If your device doesn't pass the SafetyNet test after installation then it's probably because of the Magisk patched image flashed into the device since nowadays apps can detect if it's a stock android or not.
But I am pretty sure that there are other modules to hide that too.
Sent by me from A50s with TWRP and S12 Revolt Corvus OS.
Click to expand...
Click to collapse
- Ok ty so much! so its better im upgrade to last version because its better then v23?
- The problem of installing SafetyNet on V23 its because u need to install Riru that dont support anymore the V23!
So u need to upgrade mandatory to V24 wich make it useless because the last version its better then V24!
PS
I has already had installed v25 but some game detect it and dont let me play that why i downgrade to V23...

Someone Anyone said:
Yes, I prefer installing Magisk 25.2 as it comes with Zygisk which hides itself from other apps.
If that still doesn't works then you can install Shamiko. A module for Zygisk which hides root completely from the device.
If your device doesn't pass the SafetyNet test after installation then it's probably because of the Magisk patched image flashed into the device since nowadays apps can detect if it's a stock android or not.
But I am pretty sure that there are other modules to hide that too.
Sent by me from A50s with TWRP and S12 Revolt Corvus OS.
Click to expand...
Click to collapse
Ok im installed again Magisk v25.2 and installed last safetynet (2.3.1) but its me or they removed safetynet check from magisk??? why they did that???
How to check if my safetynet is passed???
Also i noticed ALL modules is gone....
Wich modules i have to install also???
Also i noticed my Zygisk is marked as yes and ramdisk as no....my ramdisk need to be set as yes?
ty so much.

roberto_1986 said:
Ok im installed again Magisk v25.2 and installed last safetynet (2.3.1) but its me or they removed safetynet check from magisk??? why they did that???
How to check if my safetynet is passed???
Also i noticed ALL modules is gone....
Wich modules i have to install also???
Also i noticed my Zygisk is marked as yes and ramdisk as no....my ramdisk need to be set as yes?
ty so much.
Click to expand...
Click to collapse
Hey!
Sorry for the late reply.
Well for safety net check you have to update the app or simply it isn't available for your device.
You can download the official SafetyNet check app from Playstore.
For ramdisk it depends on your Firmware.

roberto_1986 said:
- Ok ty so much! so its better im upgrade to last version because its better then v23?
- The problem of installing SafetyNet on V23 its because u need to install Riru that dont support anymore the V23!
So u need to upgrade mandatory to V24 wich make it useless because the last version its better then V24!
PS
I has already had installed v25 but some game detect it and dont let me play that why i downgrade to V23...
Click to expand...
Click to collapse
For game detection you have to go to Zygisk > Select Apps for list > Save > Enforce list > Reboot.

Someone Anyone said:
For game detection you have to go to Zygisk > Select Apps for list > Save > Enforce list > Reboot.
Click to expand...
Click to collapse
Im installed both app and magisk to last version! also i have installed EEA MIUI V11.0.3.0.PGGEUXM A9 is the stock firmware! Any other module u suggest i have to install???
I remember i had installed busy box and other modules that i dont remember!
Another weird thing is when im made fresh install seems like most app didnt update to last version why???
ty again for your answer^^
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

roberto_1986 said:
Im installed both app and magisk to last version! also i have installed EEA MIUI V11.0.3.0.PGGEUXM A9 is the stock firmware! Any other module u suggest i have to install???
I remember i had installed busy box and other modules that i dont remember!
Another weird thing is when im made fresh install seems like most app didnt update to last version why???
ty again for your answer^^
View attachment 5791443
Click to expand...
Click to collapse
Magisk Patch blocks the Google Framework for some time that's why most of the time it is suggested to complete the setup without internet.
For ramdisk your device might not have one but it shouldn't be a problem.
Do you have TWRP installed?

roberto_1986 said:
Im installed both app and magisk to last version! also i have installed EEA MIUI V11.0.3.0.PGGEUXM A9 is the stock firmware! Any other module u suggest i have to install???
I remember i had installed busy box and other modules that i dont remember!
Another weird thing is when im made fresh install seems like most app didnt update to last version why???
ty again for your answer^^
View attachment 5791443
Click to expand...
Click to collapse
You might also have flashed Magisk in recovery partition just like me.
However it will work just normal.

Someone Anyone said:
You might also have flashed Magisk in recovery partition just like me.
However it will work just normal.
Click to expand...
Click to collapse
Hi!
Yes i have installed LR TWRP 3.3.1 - 1104
That is a variant of TWRP recovery!
I remember this was the only recovery that work for my RN8P because the other make my phone stuck...now idk if there is other recovery that work...there is better one?
Also what did u mean for ""Magisk Patch blocks the Google Framework for some time that's why most of the time it is suggested to complete the setup without internet.""
I have rooted my phone many time and this never happend...so what i have to do?
I have to make again fresh install and install every app before the ROOT?
Or this will fixed after couple time???
what i have to do???
Ty again for your support!!!

roberto_1986 said:
Hi!
Yes i have installed LR TWRP 3.3.1 - 1104
That is a variant of TWRP recovery!
I remember this was the only recovery that work for my RN8P because the other make my phone stuck...now idk if there is other recovery that work...there is better one?
Also what did u mean for ""Magisk Patch blocks the Google Framework for some time that's why most of the time it is suggested to complete the setup without internet.""
I have rooted my phone many time and this never happend...so what i have to do?
I have to make again fresh install and install every app before the ROOT?
Or this will fixed after couple time???
what i have to do???
Ty again for your support!!!
Click to expand...
Click to collapse
I don't think that you have to root it again.
It is going to get fixed in a couple of time.
I had suggest you would Install Orange Fox since old stuff results in Faulty.

The TWRP 3.6.1 is better for nt8pro

Someone Anyone said:
I don't think that you have to root it again.
It is going to get fixed in a couple of time.
I had suggest you would Install Orange Fox since old stuff results in Faulty.
Click to expand...
Click to collapse
Hi!
I dont know whats happend because i have ROOT my pone many time without issue but now after made fresh install and rooted again my phone i receive "no sim card" after root and upgraded to last version on magisk (25.2 )
Another weird thing is after couple reboot the icon "no sim card" disappeare and my root is gone....any tip pls???