Android Open Source Project 6.0
Marshmallow
for
Samsung Galaxy Tab 10.1
(P7510, P7500, SGH-T859)
(p4wifi, p4, p4tmo)
Customizations:
busybox
init.d scripts
CMFileManager
Kernel features:
CPU overclock (1.2Ghz - 1.6Ghz)
CPU voltage control
CPU temperature readings
GPU overclock (400Mhz)
L2 cache optimization
F2FS
SELinux
Voodoo Sound
USB Charging
Updated WIFI driver
ZRAM backports
sdcardfs
Working:
Video
Audio
WIFI
Cellular
GPS
Bluetooth
- Audio playback: working
- File transfer: working
Encryption
Not working / buggy / needs testing:
Camera
- Pictures: working
- Video recording: (not working)
Dock audio
Keyboard dock (untested)
- Likely the same status as Lollipop
Tethering
- USB tethering: working with WIFI
- Bluetooth tethering: (not working)
- WIFI tethering: (untested)
Wireless Display / Miracast
- No compatibility with the outdated video blobs
Installation:
Backup all data
Install TWRP 2.8.7.0 or newer
Wipe cache, dalvik cache, system, data
Install the ROM
Optional step:
- Install gapps pico
- Install Supersu 2.52
Boot the ROM
Enable on screen keyboard by toggling "Show input method"
Downloads:
p4wifi (GT-P7510): WIFI only tablet.
aosp-6.0-p4wifi-20160806.zip
p4 (GT-P7500): Cellular / 3G tablet.
aosp-6.0-p4-20160809.zip
p4tmo (SGH-T859): T-Mobile tablet.
p4wifi and p4 users do NOT install this.
aosp-6.0-p4tmo-20160809.zip
mirror: AndroidFileHost
GApps
http://opengapps.org/
root: SuperSU
BETA SuperSU v.2.52
Mirrors:
Android File Host
Changelog
Code:
August 9, 2016
decatf/android_kernel_samsung_p4
e602201 defconfig: Fix typo while enabling CONFIGFS_FS
August 6, 2016
Update to android-6.0.1_r59
decatf/android_kernel_samsung_p4
2c421f2 fuse: O_DIRECT support for files
3bb1d41 fuse: remove the second argument of k[un]map_atomic()
acf44b5 fuse: verify all ioctl retry iov elements
1b17d75 fuse: postpone end_page_writeback() in fuse_writepage_locked()
d88af9d fuse: break infinite loop in fuse_fill_write_pages()
33c337c fuse: support ioctl on directories
37bb785 FUSE: Notifying the kernel of deletion.
f7c8478 fuse: Add support for shortcircuited read/write for files
d5c6ade Revert "fuse: Add support for shortcircuited read/write for files"
04ed83b fuse: Add support for shortcircuited read/write for files
ab0b217 fs: fuse: Ensure update of fuse inode attributes in shortcircuit
b653a54 fuse: Use iocb->ki_pos instead of pos for shortcircuit writes
b79cfba fuse: Use BUG_ON to check pos validity in fuse_aio_write
786913d fs: fuse: Disable shortcircuit when mmap is called on a file
bfc19a7 vfs: add d_canonical_path for stacked filesystem support
fb6bb3e inotify: Fix erroneous update of bit count
8bae312 Initial port of sdcardfs
568217e get rid of kern_path_parent()
7233db3 sdcardfs: Port to 3.4
a5d5845 sdcardfs: Port to 3.1.10
4cede1c sdcardfs: Changed type-cast in packagelist management
3f69353 sdcardfs: Bring up to date with Android M permissions:
dfc2ff3 sdcardfs: Add support for d_canonicalize
1f80a89 sdcardfs: remove effectless config option
dd5eccf sdcardfs: Remove unused code
1b8979a sdcardfs: remove unneeded __init and __exit
1c16f89 sdcardfs: Truncate packages_gid.list on overflow
560043c ANDROID: sdcardfs: fix itnull.cocci warnings
d3e1021 vfs: change d_canonical_path to take two paths
e587970 fuse: Add support for d_canonical_path
434e90b defconfig: Enable sdcardfs
e7b5ee2 BACKPORT: perf tools: Document the perf sysctls
90bd458 FROMLIST: security,perf: Allow further restriction of perf_event_open
1ccaa78 defconfig: restrict access to perf events
android_device_samsung_p4-common
8404df3 p4-common: Enable sdcardfs
913957d p4-common: Disable EGL_WORKAROUND_BUG_10194508
5f67070 p4-common: sepolicy: Allow kernel to rw wifi efs file
android_vendor_decatf
6bbd9c6 sepolicy: remove BOARD_SEPOLICY_UNION
91f8dc2 sepolicy: Add rule to allow sdcardfs to read package list
8209b59 sepolicy: Fix MTP for sdcardfs
android_bionic
546aae2 bionic: Sort and cache hosts file data for fast lookup
platform_frameworks_base
0454407 mountservice: Shut down volumes before restarting framework
9baa27d mountservice: Don't nuke all volumes when decrypting
android_frameworks_opt_net_wifi
d21014b Revert "Revert "wifi: Set the mode at native layer""
platform_system_core
a052e68 sdcard : Use the fuse shortcircuit option
86faebc sdcard: Allow fuse shortcircuit for all platforms
e06eb06 sdcard: Add support for sdcardfs!
d3a24ca sdcard: Fix sdcardFS check
6ff0e73 sdcard: Pass the umask to sdcardfs correctly
android_external_sepolicy
5d57d80 sepolicy: Add policy for sdcardfs and configfs
July 8, 2016
Update to android-6.0.1_r50
Restore previous WIFI driver
June 15, 2016
TRIM is now merged into this ROM. You don't need to install the TRIM kernel from the other thread.
Update to android-6.0.1_r46
74f7de9 p4-common: TCP buffer settings
93ca209 p4-common: Wifi is no longer built as a module
2133d24 p4-common: Enable dlmalloc
b6808c6 p4-common: Remove unused flags
4692beb tcp: drop SYN+FIN messages
cf415a5 misc: uidstat: avoid create_stat() race and blockage.
3f791c1 usb: gadget: f_fs: Fix enumeration in fullspeed mode
0469e56 usb: gadget: accessory: Fix section mismatch (again)
30fbe2f USB: remove duplicate out endpoint creation in MTP mode
c607c37 pipe: limit the per-user amount of pages allocated in pipes
8e01cbe power: max17042: Reduce logspam
5565950 Revert "Staging: android: binder: Allow using highmem for binder buffers"
bf9b28a Reduce logger size
9c3a8ec mmc: fix integer assignments to pointer
d7bfd4c mmc: sdio: Workaround for dev with broken CMD53
74032a4 mmc: sdio: Fix to support any block size optimally
3f9da59 mmc: sdio: Use multiple scatter/gather list
ed4849d genirq: Always force thread affinity
b1bb34f genirq: Avoid deadlock in spurious handling
c4cb3ae genirq: Fix can_request_irq() for IRQs without an action
aeaeb4de mmc: Restore MMC_CAP_ERASE
fd6a17d mmc: Add sdio_ctrl_power
8bd4f0d arm: tegra: p4: Allocate static dhd info buffer (section 7)
ec9b234 arm: tegra: p4: Built-in wifi
cfb0ab2 arm: tegra: p4: Set wifi chip id to 0x4330
ce80b1b arm: tegra: Conditionalize builtin wifi
2477c3b Revert "net: wireless: Sync with grouper android-5.1.0_r0.4"
e32e74d arm: tegra: p4: Fix build when not builtin wifi
a0d37af net: wireless: Import CFG80211_REG_NOT_UPDATED from klte kernel
62151e1 defconfig: disable loadable modules
a5cf304 net: Backport wireless stack from Galaxy S5 kernel
88d16a6 net: Fix net/wireless backport for 3.1.10
7dbf92b bcmdhd: G900FXXU1CPD7
abf9e8c bcmdhd: fixup for p4
e3c843a bcmdhd: Restore tegra specific irq wake
aa99d0d defconfig: bcmdhd builtin
716bd9c defconfig: Enable CONFIG_CFG80211_ALLOW_RECONNECT
946d13f mmc: tegra: Don't set MMC_PM_KEEP_POWER by default
9a40b65 mmc: host: sdhci: abort suspend if host suspend fails.
8d5d16f mmc: host: sdhci: Don't set MMC_PM_KEEP_POWER when suspending
6f689f2 mmc: Remove Samsung WIFI hacks
April 28, 2016
Fix headphone detection
April 14, 2016
Update to android-6.0.1_r30
March 26, 2016
project art/
20c3c84 Revert "Optimize double/float immediate loading on arm."
8037a8d Re-enable VFPv3-D16 register definitions
d53de19 Disable clang for art compiler on target
project device/samsung/p4-common/
f19dec3 p4-common: Use dalvik.vm.dex2oat-flags to specify backend
0cc66dc p4-common: Remove unused flag
84f022f p4-common: Tweak ksm settings
project frameworks/av/
111a9b9 Revert "mediaplayer: remove use-awesomeplayer developer option"
project frameworks/native/
f1b88cd Configure tablet dalvik heap for 1GB mdpi device
project kernel/samsung/p4/
2b12c4b pipe: iovec: Fix memory corruption when retrying atomic copy as non-atomic
16a60d8 Squash revert Android timerfd support
24bcc61 Android alarm-dev from android-3.4
f519a62 defconfig: enable android-3.4 alarm-dev
4ab42f7 p4_battery: Fix timer slack
7dbdfb5 ARM: 7006/1: Migrate to asm-generic wrapper support
f2b70ff ARM: 7493/1: use generic unaligned.h
33e4372 asm-generic: allow generic unaligned access if the arch supports it
a998f78 Revert "Revert "video: tegra: remove free memory check""
project packages/apps/Settings/
98144ac Revert "developer settings: remove "Use deprecated AwesomePlayer" settings"
project system/core/
6b5492a healthd: increase healthd fast timer to 10mins instead of 1min
March 14, 2016
Fix WIFI driver
March 10, 2016
Update to android-6.0.1_r17
ca6770d Align machine_kexec restart sequence with soft_restart()
b4c0a36 ARM: 7476/1: vfp: only clear vfp state for current cpu in vfp_pm_suspend
f847946 cfq-iosched: fix the setting of IOPS mode on SSDs
a74f780 arm: tegra: Restore tegra2 core/cpu voltage relationship
868ba34 Revert "bound cpu cores to same speed"
c4877ab include/linux/poison.h: fix LIST_POISON{1,2} offset
9c3f030 pagemap: do not leak physical addresses to non-privileged userspace
February 7, 2016
Update to android-6.0.1_r10
February 1, 2016
Add init.modem.rc for p4 and p4tmo
January 31, 2016
hwrotation for Galaxy Tab 8.9
January 28, 2016
Update to android-6.0.1r7
Switch to ICS audio wrapper HAL
Update to latest f2fs-stable
Frequently Asked Questions and Other notes:
Can I upgrade / dirty-flash from Lollipop to Marshmallow?
- You cannot. It must be a clean install.
Can I dirty flash over a previous Marshmallow build?
- Yes.
I thought you said Marshmallow wouldn't work.
- The problem with ART is not solved. The Optimizing compiler backend is producing binaries that crash on the Tegra 2. The Optimizing backend is the new default dex2oat compiler in Marshmallow. The Quick compiler is default backend in Lollipop. It is still in the Marshmallow source so this ROM is using the Quick compiler backend.
SELinux enforcing mode
- The default SELinux mode is permissive mode. The Set_SELinux_enforcing.zip will not work with Marshmallow. That script was setting a system property to toggle SELinux early on in boot. Google has removed the use of this system prop so that method won't work anymore.
- For now you can find some app on F-Droid to set the SELinux mode after boot. It's not ideal but it will do until some better solution arises.
Doze
- This device does not meet the hardware requirement to support Doze.
Themes
- Marshmallow supports RRO (Layers) themes. I will not add CM-12 themes, CM-13 themes, or any other theme engine.
HD video playback issues and Camera issues.
- The video and camera stack are proprietary NVidia software. This means there is no chance of fixing bugs within.
Browser crash when downloading files
- Settings > Apps > Browser > Permissions > Enable Storage permission
Google App force close
- Install GApps Pico.
- Google App now uses the NEON instruction set which the CPU on this device does not support. The pico package does not include the parts of GApps which use the NEON instruction set.
- reference post
Non-NEON Google Apps
Chrome 49.0.x
Donate:
Via Paypal
XDA:DevDB Information
Android 6.0 Marshmallow, ROM for the Samsung Galaxy Tab 10.1
Contributors
decatf
Source Code: https://github.com/decatf
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.1.x
Based On: AOSP
Version Information
Status: Alpha
Created 2015-12-08
Last Updated 2016-12-19
Problem reporting steps:
Got an error? Is something not working for you?
I cannot see what your problem is from here. Save and upload the system logs from your device so that I can see what happening on your device.
How to save system logs:
Root the device by installing SuperSU.
Install SysLog.
Reboot the system.
Reproduce the problem.
Open Syslog app and save the Kernel Log and Main Log.
Send me the log files stored in /sdcard/Syslog.
Share the files on Dropbox or another similar site.
Then PM me a link to the files. Please describe exactly what the issue is.
Some comments to start off.
The ICS audio HAL is not working right in Marshmallow and I think I'd rather try another run at getting the rest of the stuff in the open souce HAL working rather than keep trying to find hacks to keep the old blob alive. Recall that only voice calls and dock audio are not working with the open source audio HAL.
- Voice calls are just passing off audio to the Samsung cellular blobs so I don't think it's that much of a stretch to get working. But this will have to wait until cellular stuff is working in the first place.
- I found some patch for Samsung dock audio. It looks like it might apply to this device as well seeing as it seems to have a similar dock implementation. The patch is in the ROM already so that needs testing.
Cellular probably won't work for at least the first few builds. Other devices on M with a similar cellular radio needed a few new patches to get it working on M. I have put in the patches from L but we will have to trial and error what is needed for M based on other devices as a reference.
Thank you!
I know it's early on, but do you have any expectations as to how well it will run compared to previous Android version?
I appreciate all you've done, but mine never ran that great on the newest roms. It is passable and I appreciate it though.
Sent from my XT1094 using XDA Free mobile app
thank you very much for betting on this tablet , and download and I'll try ... I'm sure you will be able to tune it as we did with lp...
sflesch said:
I know it's early on, but do you have any expectations as to how well it will run compared to previous Android version?
I appreciate all you've done, but mine never ran that great on the newest roms. It is passable and I appreciate it though.
Sent from my XT1094 using XDA Free mobile app
Click to expand...
Click to collapse
The OS appears to perform the same as Lollipop. It's a four year old device. There is nothing that will make it run as well as a modern Android device. You could try setting animation times to zero and set ro.config.low_ram=true.
For Marshmallow I have added L2 cache improvements in the kernel that improves RAM speed benchmarks. That's around 1k score in Antutu.
I understand that. And again I appreciate it. I was just curious what the performance level was. I expected at best it might be similar, but more likely it would, as is typical, use more resources.
I never expected much from my Tab. Finding your ROM was an unexpected surprise. I will try those tweaks. From all of the posts I read, I got the impression that many other tablets ran better than mine. I know fully well that each tablet is different and I don't blame you or the ROM, just my tablet.
Sent from my XT1094 using XDA Free mobile app
decatf said:
The OS appears to perform the same as Lollipop. It's a four year old device. There is nothing that will make it run as well as a modern Android device. You could try setting animation times to zero and set ro.config.low_ram=true.
For Marshmallow I have added L2 cache improvements in the kernel that improves RAM speed benchmarks. That's around 1k score in Antutu.
Click to expand...
Click to collapse
Thank you for keeping this Mastodont alive. I will be doing the switch soon enough... I have been following and installing your Lollipop releases for quite a while now and appreciate very much all the time and effort you have put into these projects...
Sent from my p4wifi using XDA Free mobile app
Definitely wasn't expecting this tbh. You're doing a damn great job at keeping this tab alive decatf. Thank you for that.
Mmmh, I just did the following steps (coming from your version of 5.1.1) :
1) Installed TWRP-2710 from previously installed TWRP-2610
2) Rebooted into 2710 Recovery
3) Full Wipe
4) Install Android 6.0 ROM
5) Install OpenGapps (nano)
6) Install SuperSU 2.52
7) Reboot
Now the P4 is stuck at the Samsung boot logo, so it does not boot up.
Any ideas what I did wrong?
Regards, mistersixt.
mistersixt said:
Mmmh, I just did the following steps (coming from your version of 5.1.1) :
1) Installed TWRP-2710 from previously installed TWRP-2610
2) Rebooted into 2710 Recovery
3) Full Wipe
4) Install Android 6.0 ROM
5) Install OpenGapps (nano)
6) Install SuperSU 2.52
7) Reboot
Now the P4 is stuck at the Samsung boot logo, so it does not boot up.
Any ideas what I did wrong?
Regards, mistersixt.
Click to expand...
Click to collapse
Me too, ive installed twrp 2.8.7.0. Full wipe, install android 6 rom (P4) and use openGapps (pico), install superSU beta 2.52.
My P4 is stuck at samsung boot logo
Anyone able to install the rom successfully?
Anyways thanks decatf for all u have done for our device!
maybe don't use OpenGapps Pico?
on different devices, had issues with OpenGapps Pico versions;
especially on 5.1 and 6.0, pico may be -too- light?
I've had success with slim gapps zero on different devices;
size is similar to OpenGapps nano.
- maybe try WITHOUT any gapps?
- assuming it works, try Open nano, or slim zero?
i'll try myself and report later if I can
cheers
---------- Post added at 10:45 AM ---------- Previous post was at 10:37 AM ----------
I haven't read -too- thoroughly,
but in addition to the 'regular' supersu beta (currently 2.52),
chainfire has a separate "WIP" thread where, at least check,
2.61.. for Marshmallow+.. systemless?.. discussion is still in the 2.52 / beta thread
a) link to the WIP thread: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
b) that said, maybe for our system , 2.52 may be more appropriate?
can anyone compare?
c) hmm.. more reading.. may want to stick with 2.52 for now,
until 2.62 is ready (currently 2.61, but with planned features/fixes for 2.62)
cheer
Same thing, just did another full wipe and installed the p4 ROM only (no gapps, no supersu), and it is still stuck at the Samsung boot logo.
Regards, mistersixt.
spamam1 said:
on different devices, had issues with OpenGapps Pico versions;
especially on 5.1 and 6.0, pico may be -too- light?
I've had success with slim gapps zero on different devices;
size is similar to OpenGapps nano.
- maybe try WITHOUT any gapps?
- assuming it works, try Open nano, or slim zero?
i'll try myself and report later if I can
cheers
---------- Post added at 10:45 AM ---------- Previous post was at 10:37 AM ----------
I haven't read -too- thoroughly,
but in addition to the 'regular' supersu beta (currently 2.52),
chainfire has a separate "WIP" thread where, at least check,
2.61.. for Marshmallow+.. systemless?.. discussion is still in the 2.52 / beta thread
a) link to the WIP thread: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
b) that said, maybe for our system , 2.52 may be more appropriate?
can anyone compare?
c) hmm.. more reading.. may want to stick with 2.52 for now,
until 2.62 is ready (currently 2.61, but with planned features/fixes for 2.62)
cheer
Click to expand...
Click to collapse
It works on my p4wifi. Somebody with an actual p4 needs to try booting it then reboot directly into TWRP and grab the last_kmsg.
Code:
adb pull /proc/last_kmsg
Or
Go to Advanced > File Manager > Go to /proc/ > Tap last_kmsg > Copy File to /sdcard/
P4: wrong updater binary?
hi,
on TWRP 2.8.7.0.. try to install on P4,
but getting error:
E:Error executing updater binary in zip '/sdcard/Android/aosp-6.0-p4-20151207.zip'
maybe the binary is from p4wifi?
anyone on P4 having issues?
I checked the MD5, and it matches.
cheers
---------- Post added at 11:06 AM ---------- Previous post was at 11:04 AM ----------
spamam1 said:
hi,
on TWRP 2.8.7.0.. try to install on P4,
but getting error:
E:Error executing updater binary in zip '/sdcard/Android/aosp-6.0-p4-20151207.zip'
maybe the binary is from p4wifi?
anyone on P4 having issues?
I checked the MD5, and it matches.
cheers
Click to expand...
Click to collapse
hmm. .. donjuan10 on P4 was able to at least flash the files.
what am i doing wrong?
Hope I grabbed the right file:
http://144.76.203.117/tmp/last_kmsg
regards, mistersixt.
decatf said:
It works on my p4wifi. Somebody with an actual p4 needs to try booting it then reboot directly into TWRP and grab the last_kmsg.
Code:
adb pull /proc/last_kmsg
Or
Go to Advanced > File Manager > Go to /proc/ > Tap last_kmsg > Copy File to /sdcard/
Click to expand...
Click to collapse
spamam1 said:
hi,
on TWRP 2.8.7.0.. try to install on P4,
but getting error:
E:Error executing updater binary in zip '/sdcard/Android/aosp-6.0-p4-20151207.zip'
maybe the binary is from p4wifi?
anyone on P4 having issues?
I checked the MD5, and it matches.
cheers
---------- Post added at 11:06 AM ---------- Previous post was at 11:04 AM ----------
hmm. .. donjuan10 on P4 was able to at least flash the files.
what am i doing wrong?
Click to expand...
Click to collapse
more info..
before the error message (in red), a message about mount/symlink:
mount: failed to mount /dev/block/platform/sdhci-tegra.3/by-num/p4 at /system: Device or resource busy
symlink: some symlinks failed
?
It might just be some kernel cmdline options I missed. The reason it boots on my p4wifi is because I'm testing it on multirom which passes off some cmdline options from the host ROM so the problem was not apparent due to that.
Just install the ROM then the kernel. And the rest of the stuff as usual.
p4-kernel-aosp-6.0-20151209.zip
p4tmo-kernel-aosp-6.0-20151209.zip
*** Urgent Update Notice ***
We are deeply sorry about the installation errors and failures happened in v2.80.
The new update v2.81 has rolled out on XDA and Play Store to fix the problem occured in v2.80.
Chainfire has also released a quick fix on XDA, it's at #1445 post (we will post it here soon)
We have noticed the multiple reports from users on both XDA and Play Store regarding update failure and loss of root. As of now, we have rolled out 2.82 to resolve this issue. If it still persist, please reroot your phone with v2.79.
Again, we apologize for all the trouble and inconvenience caused regarding our 2.80 update. There is hardly any excuse on our side and we should have done a better job. In the coming days, Chainfire and us will review this issue again and provide a note on what went wrong and how we fixed it. In future, we will set up a mechanism to make sure cases like this won't happen again.
P.S. Upon reading ALL the comments posted on this thread, Play Store, Facebook and various sites, we understand the frustrations among users and we are swallowing the heated words. But even at moment like this, we are truly grateful for the community members who shared the details of the error (which speed up our detection process) and those who defended us.
We owe you guys a big thank you.
Download:
SuperSU on Google Play:
https://play.google.com/store/apps/details?id=eu.chainfire.supersu
SuperSU Pro on Google Play:
https://play.google.com/store/apps/details?id=eu.chainfire.supersu.pro
TWRP / FlashFire installable ZIP :
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
*** Xperia users, and others experiencing bootloops ***
Please use this version instead: https://forum.xda-developers.com/attachment.php?attachmentid=4164510&d=1496008012
Contact us:
SuperSU Official Website: www.supersu.com
Forum: forum.supersu.com
Facebook: https://www.facebook.com/SuperSU-1024576694301637/?ref=br_rs
Our team's previous announcement (regarding who we are):
Hello everyone, the CCMT team announces the following statement. We hope this can help everyone have a better picture of who we are and what we will be working on:
1. Our team: Founded in U.S, the team currently operates in Beijing, as a subsidiary of JJ World. Our members consist of operations and engineers from top mobile companies in China, US and Spain. Our mission is to make a difference in Android mobile security, via providing clean, reliable apps.
Though CCMT was founded in the U.S. as a full subsidiary of JJ World, the team currently operates in Beijing. Our members consist of operators and engineers from top mobile companies in China, US and Spain. Our mission is to make a difference in Android mobile security, by providing clean and reliable apps.
2. SuperSU’s future: Our next step is to make SuperSU easier and friendlier to use for broader audience. Our primary effort and achievement since partnering with Chainfire is helping new users (who approached us with no knowledge of how to root) and international users who need special assistance crossing the language barrier.
3. Regarding User Improvement Program (with Google Analytics): In future versions, there will be an option to be included in our user improvement program. It’s essentially adding Google Analytics to understand how SuperSU is used. As stated before, we want SuperSU to be friendlier to rookie users, and we need data to help us achieving that goal. Not a fan? You can always go to settings and disable this feature. Note that the user improvement program does not collect nor store personal information.
4. For concerns regarding possible ads in SuperSU: Maintaining the purity and integrity of SuperSU does not conflict with our team’s business strategy. In other words, we will make sure SuperSU is clean and pure, as it should be.
To conclude, we hope this statement can provide a clearer picture of the CCMT team and we are grateful for those who stayed with us along our ups and downs. We thank you for your support, and stay tuned with CCMT!
Changelogs
SuperSU V2.80 is essentially the stable version of V2.79 SR series, now available on both XDA and Google Play Store. For the past few months, Chainfire and the team have decided to rename the beta versions as service release (SR). Thus the next beta version is expected to be named as v2.80 SR1. The reason for this change is partly due to a significant number of websites outside of XDA update their SuperSU when an elevation of version number takes place ( such as 2.76 to 2.77 beta), but they do not label out the beta. Thus the conventional beta release will be assumed as stable version release in many places other than of XDA. Users who only wish for stable versionsmay accidentally update their SuperSU to beta version.
For the full changelogs including currently in development 'service release' / beta versions and older versions, see Chainfire's changelog post here: https://forum.xda-developers.com/showpost.php?p=64916199&postcount=3
What has changed since the last stable release (v2.79):
26.05.2017 - v2.82
- su: Fix su.d scripts running in the wrong mount context (introduced by ODP sdcardfs fix)
- CCMT: Remove Feedback screen and associated permissions
(v2.81 == v2.79 SR3 with patched version code)
24.05.2017 - v2.80
- CCMT: Update language files
- CCMT: Update guide screen
- CCMT: Update privacy policy screen
- CCMT: Updater: remove 4.3 and 5.0 specific upgrade messages, replace with generic; and detect if root must be manually updated
- CCMT: Add feedback screen
- CCMT: Drop support for Android 2.1 and 2.2. Minimum is now 2.3 (SDK 9, up from 7)
11.04.2017 - v2.79 - SR5 - Not publicly released
- su: Update mount namespace separation code to improve sdcardfs compatibility
- su: Fix kernel panic on ODP1/2 on 5X/6P
- su: Fix ODP1 compatibility on Pixel (XL)
- launch_daemonsu: Revert previous ODP1 work-around
- sukernel: Add option to patch out optional /data encryption (encryptable)
- suinit: cleanup /boot
- ZIP: Get boot image from fstab last-effort
- ZIP: Add REMOVEENCRYPTABLE flag to force disable encryption on newer Samsung firmwares
23.03.2017 - v2.79 - SR4 (ODP1/6P/5X only)
- ZIP: Fix slow /dev/random on some devices, apparently freezing install at "Creating image"
- ZIP: Fix LD_LIBRARY_PATH for hex-patch execution
- supolicy: Fix applying deferred allow rules
- supolicy: Fix setting impossible XPERM causing policy corruption
- supolicy: Add policies for ODP1
- launch_daemonsu: Work-around kernel panic on ODP1 on 5X/6P. Forces service mode for ODP1 on all devices.
14.01.2017 - v2.79 - SR3
- Fix erroneously deleting SuperSU's copy of app_process on 6.0 since 2.79-SR1
- GUI: Fix app_process requirement detection when supersu context used
- Fully eliminate sugote binary, no longer needed due to SELinux handling improvements in earlier versions
- Support /system/xbin/sush as default shell
- Adjust LD_PRELOAD filtering to exclude suhide's libraries
- ZIP: Motorola: default to systemless mode
03.01.2017 - v2.79 - SR2
- supolicy: fix some segfaults(NPEs) in pre-7.0 sepolicy handling
- ZIP: write boot block device once instead of twice (@_alexndr)
- (c) 2017 + CCMT
22.12.2016 - v2.79 - SR1
- Expand Samsung detection
- GUI: reworked portions to work with 'supersu' context on 7.0+
- GUI: fix binary update notice when superuser disabled by user in some cases
- su: reworked portions to work with 'supersu' context on 7.0+
- su/GUI: improve responsiveness when device busy on 7.0+
- sukernel: fix cpio restore failure with very short filenames
- sukernel: no longer patches file_contexts(.bin)
- sukernel: revert force seclabel (no longer needed with 'supersu' context)
- supolicy: add "create", "auditallow", "auditdeny" policy commands
- supolicy: support "*" for permission/range parameter of "allow", "deny", "auditallow", "auditdeny", "allowxperm" policy commands
- supolicy: --live/--file no longer apply default patches if custom patches are supplied
- supolicy: --sdk=X option added (required for 7.0+)
- supolicy: reworked all SELinux rules for 7.0+, run as 'supersu' context
- ZIP: Separate slotselect and system_root logic
- ZIP: Adjust system/system_root device and mount-point detection
- ZIP: Fix minor errors in documentation
- ZIP/frp: Explicitly label /su
The old opening post can be found here: http://forum.xda-developers.com/showthread.php?t=1538053
Older changelogs can be found here: http://forum.xda-developers.com/showpost.php?p=64916199&postcount=3
--- reserved ---
--- reserved ---
--- reserved ---
It would be great if "system-mode" rooting will be implemented again...
Thread cleaned. Yes, this is a new thread for SuperSU as it has been taken over by Coding Code Mobile Technology, Inc (CCMT for short). No, you are not allowed to complain and be disrespectful towards these guys or Chainfire. This has been a long time in the making (some reading for you if you missed out) and if you are upset in the direction it is going, feel free not to use it and/or develop your own root solution (since, you know, we're on a developer's site). Nobody here owes you anything.
Nathan
Forum Moderator
Thank you @nathanchance.... ▶.
Dead Cookies leave no trails...
.zip installed after kernel
Galaxy S7 International.
Android 6.0.1
Custom ROM based on G930FXXU1BPH6 (I'm developer)
No interfering apps.
--
[email protected]:/ $ which su
which su
/su/bin/su
[email protected]:/ $ ls -l `which su`
ls -l `which su`
-rwxr-xr-x root root 108480 2016-08-22 07:19 su
[email protected]:/ $ which su
which su
/su/bin/su
[email protected]:/ $ uname -a
uname -a
Linux localhost 3.18.14-prometheus-v1.5.3 #1 SMP PREEMPT Sat Aug 27 10:53:02 EEST 2016 aarch64
[email protected]:/ $
d8389 said:
.zip installed after kernel
Galaxy S7
--
[email protected]:/ $ which su
which su
/su/bin/su
[email protected]:/ $ ls -l `which su`
ls -l `which su`
-rwxr-xr-x root root 108480 2016-08-22 07:19 su
[email protected]:/ $ which su
which su
/su/bin/su
[email protected]:/ $ uname -a
uname -a
Linux localhost 3.18.14-prometheus-v1.5.3 #1 SMP PREEMPT Sat Aug 27 10:53:02 EEST 2016 aarch64
[email protected]:/ $
Click to expand...
Click to collapse
try it vice versa, first supersu and then the kernel. also, you might want to ask for help in the S7 subforums.
ulxerker said:
try it vice versa, first supersu and then the kernel. also, you might want to ask for help in the S7 subforums.
Click to expand...
Click to collapse
same result
I can ask help from myself only...
instalation fail
sony m4 6.01 stock rom
[Size=+1]Thread cleaned. Again.
As was previously pointed out by another moderator this thread is not the place to discuss the handover of SuperSU or how the company needs to prove itself. This thread is solely for the discussion of SuperSU itself. No more off topic please.[/sizE]
d8389 said:
same result
I can ask help from myself only...
Click to expand...
Click to collapse
I have intsalled Susi from store without problems on your ROM.
SuperSU v2.78
I upgraded through TWRP flashable zip,Running smoothly in my Sony xperia E3 ,No su binaries update issues.
Upgraded by playstore. Seems to be working fine.. ?
Question is why did some, not all of my settings change?
2.77 was installed into system and now 2.78 it is not.
(Install backup script for updates is not there now?)
Sent from my SM-T230NU using XDA Labs
Android 4.4.2
Edit:
Took another (fourth reboot) and now all my settings are reset but, I am back to installed system app. (Still no backup script ?)
If you want to stay or be system less it's super su then kernel. Same if switching kernels
Straight from the one and only Straight Shooter. ?
A quick question...
In order to install suhide we need to flash both, suhide and Supersu in order to avoid boot loops.
Since 2.78 now updates from GP how do we accomplish the above?? I can't flash a GP download and I'll possibly have bootloops after installing suhide and before going to GP.
So, what do we do?
Inquiring minds want to know...
Sent from my LG-H901 using XDA Labs
NYLimited said:
A quick question...
In order to install suhide we need to flash both, suhide and Supersu in order to avoid boot loops.
Since 2.78 now updates from GP how do we accomplish the above?? I can't flash a GP download and I'll possibly have bootloops after installing suhide and before going to GP.
So, what do we do?
Inquiring minds want to know...
Click to expand...
Click to collapse
The latest zip is linked in the OP. I flashed it this afternoon with suhide and it's working perfectly.
Just upgraded from 2.76 to 2.78 through recovery (SuperSU in system partition) on both devices. Surprisingly I see two icons of the application, both start 2.78. The only app file is in /system/app.
No idea what is going on.
{
"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"
}
Welcome to the Magisk Release / Announcement thread!
For all up-to-date info and links, please directly check Magisk's GitHub PageInstallation
Download count of previously XDA hosted files: 25,490,945
v1: 8746 v2: 2251 v3: 3790 v4: 1220 v5: 2914
v6: 138838 v7: 119744 v8: 116796 v9: 203836 v10.2: 215176
v11.1: 573322 v11.6:438886 v12.0: 3263706
1300: 274438 1310: 1018692 1320: 403556 1330: 1844372
1350: 39188 1360: 69874 1400: 4456314
1410: 11512 1420: 112020 1437: 247988 1455: 30652
1456: 253042 1468: 85978 1500: 434572 1510: 460120
1520: 927436 1530: 218164 1531: 3143686 1540: 97368
1600: 6043710 1610: 87628 1620: 140382
Changelog
Magisk
v20.3
- [MagiskBoot] Fix lz4_legacy decompression
v20.2
- [MagiskSU] Properly handle communication between daemon and application (root request prompt)
- [MagiskInit] Fix logging in kmsg
- [MagiskBoot] Support patching dtb/dtbo partition formats
- [General] Support pre-init sepolicy patch in modules
- [Scripts] Update magisk stock image backup format
v20.1
- [MagiskSU] Support component name agnostic communication (for stub APK)
- [MagiskBoot] Set proper header_size in boot image headers (fix vbmeta error on Samsung devices)
- [MagiskHide] Scan zygote multiple times
- [MagiskInit] Support recovery images without /sbin/recovery binary. This will fix some A/B devices unable to boot to recovery after flashing Magisk
- [General] Move acct to prevent daemon being killed
- [General] Make sure "--remove-modules" will execute uninstall.sh after removal
v20.0
- [MagiskBoot] Support inject/modify mnt_point value in DTB fstab
- [MagiskBoot] Support patching QCDT
- [MagiskBoot] Support patching DTBH
- [MagiskBoot] Support patching PXA-DT
- [MagiskInit] [2SI] Support non A/B setup (Android 10)
- [MagiskHide] Fix bug that reject process names with ":"
- [MagicMount] Fix a bug that cause /product mirror not created
v19.4
- [MagiskInit] [SAR] Boot system-as-root devices with system mounted as /
- [MagiskInit] [2SI] Support 2-stage-init for A/B devices (Pixel 3 Android 10)
- [MagiskInit] [initramfs] Delay sbin overlay creation to post-fs-data
- [MagiskInit] [SARCompat] Old system-as-root implementation is deprecated, no more future changes
- [MagiskInit] Add overlay.d support for root directory overlay for new system-as-root implementation
- [MagiskSU] Unblock all signals in root shells (fix bash on Android)
- [MagicMount] Support replacing files in /product
- [MagiskHide] Support Android 10's Zygote blastula pool
- [MagiskHide] All random strings now also have random length
- [MagiskBoot] Allow no recompression for ramdisk.cpio
- [MagiskBoot] Support some weird Huawei boot images
- [General] Add new "--remove-modules" command to remove modules without root in ADB shell
- [General] Support Android 10 new APEX libraries (Project Mainline)
v19.3
- [MagiskHide] Hugely improve process monitor implementation, hopefully should no longer cause 100% CPU and daemon crashes
- [MagiskInit] Wait for partitions to be ready for early mount, should fix bootloops on a handful of devices
- [MagiskInit] Support EROFS used in EMUI 9.1
- [MagiskSU] Properly implement mount namespace isolation
- [MagiskBoot] Proper checksum calculation for header v2
v19.2
- [General] Fix uninstaller
- [General] Fix bootloops on some devices with tmpfs mounting to /data
- [MagiskInit] Add Kirin hi6250 support
- [MagiskSU] Stop claiming device focus for su logging/notify if feasible
This fix issues with users locking Magisk Manager with app lock, and prevent
video apps get messed up when an app is requesting root in the background.
v19.1
- [General] Support recovery based Magisk
- [General] Support Android Q Beta 2
- [MagiskInit] New sbin overlay setup process for better compatibility
- [MagiskInit] Allow long pressing volume up to boot to recovery in recovery mode
- [MagicMount] Use proper system_root mirror
- [MagicMount] Use self created device nodes for mirrors
- [MagicMount] Do not allow adding new files/folders in partition root folder (e.g. /system or /vendor)
v19.0
- [General] Remove usage of magisk.img
- [General] Add 64 bit magisk binary for native 64 bit support
- [General] Support A only system-as-root devices that released with Android 9.0
- [General] Support non EXT4 system and vendor partitions
- [MagiskHide] Use Zygote ptracing for monitoring new processes
- [MagiskHide] Targets are now per-application component
- [MagiskInit] Support Android Q (no logical partition support yet!)
- [MagiskPolicy] Support Android Q new split sepolicy setup
- [MagiskInit] Move sbin overlay creation from main daemon post-fs-data to early-init
- [General] Service scripts now run in parallel
- [MagiskInit] Directly inject magisk services to init.rc
- [General] Use lzma2 compressed ramdisk in extreme conditions
- [MagicMount] Clone attributes from original file if exists
- [MagiskSU] Use ACTION_REBOOT intent to workaround some OEM broadcast restrictions
- [General] Use skip_mount instead of auto_mount: from opt-in to opt-out
v18.1
- [General] Support EMUI 9.0
- [General] Support Kirin 960 devices
- [General] Support down to Android 4.2
- [General] Major code base modernization under-the-hood
v18.0
- [General] Migrate all code base to C++
- [General] Modify database natively instead of going through Magisk Manager
- [General] Deprecate path /sbin/.core, please start using /sbin/.magisk
- [General] Boot scripts are moved from <magisk_img>/.core/<stage>.d to /data/adb/<stage>.d
- [General] Remove native systemless hosts (Magisk Manager is updated with a built-in systemless hosts module)
- [General] Allow module post-fs-data.sh scripts to disable/remove modules
- [MagiskHide] Use component names instead of process names as targets
- [MagiskHide] Add procfs protection on SDK 24+ (Nougat)
- [MagiskHide] Remove the folder /.backup to prevent detection
- [MagiskHide] Hide list is now stored in database instead of raw textfile in images
- [MagiskHide] Add "--status" option to CLI
- [MagiskHide] Stop unmounting non-custom related mount points
- [MagiskSU] Add FLAG_INCLUDE_STOPPED_PACKAGES in broadcasts to force wake Magisk Manager
- [MagiskSU] Fix a bug causing SIGWINCH not properly detected
- [MagiskPolicy] Support new av rules: type_change, type_member
- [MagiskPolicy] Remove all AUDITDENY rules after patching sepolicy to log all denies for debugging
- [MagiskBoot] Properly support extra_cmdline in boot headers
- [MagiskBoot] Try to repair broken v1 boot image headers
- [MagiskBoot] Add new CPIO command: "exists"
v17.3
- [MagiskBoot] Support boot image header v1 (Pixel 3)
- [MagiskSU] No more linked lists for caching su_info
- [MagiskSU] Parse command-lines in client side and send only options to daemon
- [MagiskSU] Early ACK to prevent client freezes and early denies
- [Daemon] Prevent bootloops in situations where /data is mounted twice
- [Daemon] Prevent logcat failures when /system/bin is magic mounting, could cause MagiskHide to fail
- [Scripts] Switch hexpatch to remove Samsung Defex to a more general pattern
- [Scripts] Update data encryption detection for better custom recovery support
v17.2
- [ResetProp] Update to AOSP upstream to support serialized system properties
- [MagiskInit] Randomize Magisk service names to prevent detection (e.g. FGO)
- [MagiskSU] New communication scheme to communicate with Magisk Manager
v17.0/17.1
- [General] Bring back install to inactive slot for OTAs on A/B devices
- [Script] Remove system based root in addon.d
- [Script] Add proper addon.d-v2 for preserving Magisk on custom ROMs on A/B devices
- [Script] Enable KEEPVERITY when the device is using system_root_image
- [Script] Add hexpatch to remove Samsung defex in new Oreo kernels
- [Daemon] Support non ext4 filesystems for mirrors (system/vendor)
- [MagiskSU] Make pts sockets always run in dev_pts secontext, providing all terminal emulator root shell the same power as adb shells
- [MagiskHide] Kill all processes with same UID of the target to workaround OOS embryo optimization
- [MagiskInit] Move all sepolicy patches pre-init to prevent Pixel 2 (XL) boot service breakdown
v16.7
- [Scripts] Fix boot image patching errors on Android P (workaround the strengthened seccomp)
- [MagiskHide] Support hardlink based ns proc mnt (old kernel support)
- [Daemon] Fix permission of /dev/null after logcat commands, fix ADB on EMUI
- [Daemon] Log fatal errors only on debug builds
- [MagiskInit] Detect early mount partname from fstab in device tree
v16.6
- [General] Add wrapper script to overcome weird LD_XXX flags set in apps
- [General] Prevent bootloop when flashing Magisk after full wipe on FBE devices
- [Scripts] Support patching DTB placed in extra sections in boot images (Samsung S9/S9+)
- [Scripts] Add support for addon.d-v2 (untested)
- [Scripts] Fix custom recovery console output in addon.d
- [Scripts] Fallback to parsing sysfs for detecting block devices
- [Daemon] Check whether a valid Magisk Manager is installed on boot, if not, install stub APK embedded in magiskinit
- [Daemon] Check whether Magisk Manager is repackaged (hidden), and prevent malware from hijacking com.topjohnwu.magisk
- [Daemon] Introduce new daemon: magisklogd, a dedicated daemon to handle all logcat related monitoring
- [Daemon] Replace old invincible mode with handshake between magiskd and magisklogd, one will respwan the other if disconnected
- [Daemon] Support GSI adbd bind mounting
- [MagiskInit] Support detecting block names in upper case (Samsung)
- [MagiskBoot] Check DTB headers to prevent false detections within kernel binary
- [MagiskHide] Compare mount namespace with PPID to make sure the namespace is actually separated, fix root loss
- [MagiskSU] Simplify su_info caching system, should use less resources and computing power
- [MagiskSU] Reduce the amount of broadcasting to Magisk Manager
- [ImgTool] Separate all ext4 image related operations to a new applet called "imgtool"
- [ImgTool] Use precise free space calculation methods
- [ImgTool] Use our own set of loop devices hidden along side with sbin tmpfs overlay. This not only eliminates another possible detection method, but also fixes apps that mount OBB files as loop devices (huge thanks to dev of Pzizz for reporting this issue)
v16.4
- [Daemon] Directly check logcat command instead of detecting logd, should fix logging and MagiskHide on several Samsung devices
- [Daemon] Fix startup Magisk Manager APK installation on Android P
- [MagiskPolicy] Switch from AOSP u:r:su:s0 to u:r:magisk:s0 to prevent conflicts
- [MagiskPolicy] Remove unnecessary sepolicy rules to reduce security penalty
- [Daemon] Massive re-design /sbin tmpfs overlay and daemon start up
- [MagiskInit] Remove magiskinit_daemon, the actual magisk daemon (magiskd) shall handle everything itself
- [Daemon] Remove post-fs stage as it is very limited and also will not work on A/B devices; replaced with simple mount in post-fs-data, which will run ASAP even before the daemon is started
- [General] Remove all 64-bit binaries as there is no point in using them; all binaries are now 32-bit only.
Some weirdly implemented root apps might break (e.g. Tasker, already reported to the developer), but it is not my fault
- [resetprop] Add Protobuf encode/decode to support manipulating persist properties on Android P
- [MagiskHide] Include app sub-services as hiding targets. This might significantly increase the amount of apps that could be properly hidden
v16.3
- [General] Remove symlinks used for backwards compatibility
- [MagiskBoot] Fix a small size calculation bug
v16.2
- [General] Force use system binaries in handling ext4 images (fix module installation on Android P)
- [MagiskHide] Change property state to disable if logd is disabled
v16.1
- [MagiskBoot] Fix MTK boot image packaging
- [MagiskBoot] Add more Nook/Acclaim headers support
- [MagiskBoot] Support unpacking DTB with empty kernel image
- [MagiskBoot] Update high compression mode detection logic
- [Daemon] Support new mke2fs tool on Android P
- [resetprop] Support Android P new property context files
- [MagiskPolicy] Add new rules for Android P
v16.0
- [MagiskInit] Support non skip_initramfs devices with slot suffix (Huawei Treble)
- [MagiskPolicy] Add rules for Magisk Manager
- [Compiler] Workaround an NDK compiler bug that causes bootloops
v15.4
- [MagiskBoot] Support Samsung PXA, DHTB header images
- [MagiskBoot] Support ASUS blob images
- [MagiskBoot] Support Nook Green Loader images
- [MagiskBoot] Support pure ramdisk images
- [MagiskInit] Prevent OnePlus angela sepolicy_debug from loading
- [MagiskInit] Obfuscate Magisk socket entry to prevent detection and security
- [Daemon] Fix subfolders in /sbin shadowed by overlay
- [Daemon] Obfuscate binary names to prevent naive detections
- [Daemon] Check logd before force trying to start logcat in a loop
v15.3
- [Daemon] Fix the bug that only one script would be executed in post-fs-data.d/service.d
- [Daemon] Add MS_SILENT flag when mounting, should fix some devices that cannot mount magisk.img
- [MagiskBoot] Fix potential segmentation fault when patching ramdisk, should fix some installation failures
v15.2
- [MagiskBoot] Fix dtb verity patches, should fix dm-verity bootloops on newer devices placing fstabs in dtb
- [MagiskPolicy] Add new rules for proper Samsung support, should fix MagiskHide
- [MagiskInit] Support non skip_initramfs devices using split sepolicies (e.g. Zenfone 4 Oreo)
- [Daemon] Use specific logcat buffers, some devices does not support all log buffers
- [scripts] Update scripts to double check whether boot slot is available, some devices set a boot slot without A/B partitions
v15.1
- [MagiskBoot] Fix faulty code in ramdisk patches which causes bootloops in some config and fstab format combos
v15.0
- [Daemon] Fix the bug that Magisk cannot properly detect /data encryption state
- [Daemon] Add merging /cache/magisk.img and /data/adb/magisk_merge.img support
- [Daemon] Update to upstream libsepol to support cutting edge split policy custom ROM cil compilations
Magisk Manager
v7.5.1
- Fix toggling app components in MagiskHide screen
- Update translations
v7.5.0
- Support new MagiskSU communication method (ContentProvider)
- Fix several issues with hidden stub APK
- Support using BiometricPrompt (face unlock)
v7.4.0
- Hide Magisk Manager with stub APKs on Android 9.0+
- Allow customizing app name when hiding Magisk Manager
- Generate random keys to sign the hidden Magisk Manager to prevent signature detections
- Fix fingerprint UI infinite loop
v7.3.5
- Sort installed modules by name
- Better pre-5.0 support
- Fix potential issues when patching tar files
v7.3.4
- App is now fully written in Kotlin!
- New downloading system
- Add new "Recovery Mode" to Advanced Settings
v7.3.0/1/2
- HUGE code base modernization, thanks @diareuse!
- More sweet changes coming in the future!
- Reboot device using proper API (no more abrupt reboot)
- New floating button in Magisk logs to go to bottom
v7.2.0
- Huge UI overhaul
- More sweet changes coming in the future!
v7.1.2
- Support patching Samsung AP firmware
- Much better module downloading mechanism
v7.1.1
- Fix a bug that causes some modules using new format not showing up
v7.1.0
- Support the new module format
- Support per-application component granularity MagiskHide targets (only on v19+)
- Ask for fingerprint before deleting rules if enabled
- Fix the bug that causes repackaging to lose settings
- Several UI fixes
v7.0.0
- Major UI redesign!
- Render Markdown natively (no more buggy WebView!)
- Support down to Android 4.1 (native Magisk only support Android 4.2 though)
- Significantly improve Magisk log disply performance
- Fix post OTA scripts for A/B devices
- Reduce memory usages when verifying and signing boot image
- Drop support for Magisk lower than v18.0
v6.1.0
- Introduce new downloading methods: no longer uses buggy system Download Manager
- Introduce many new notifications for better user experience
- Add support for Magisk v18.0
- Change application name to "Manager" after hiding(repackaging) to prevent app name detection
- Add built-in systemless hosts module (access in settings)
- Auto launch the newly installed app after hiding(repackaging) and restoring Magisk Manager
- Fix bug causing incomplete module.prop in modules to have improper UI
v6.0.1
- Update to use new online module's organizing method
- When fingerprint authentication is enabled, toggling root permissions in "Superuser" section now requires fingerprint beforehand
- Fix crashes when entering MagiskHide section on some devices
- Remove support to Magisk version lower than v15.0
- Ask storage permissions before patching stock boot image
- Update dark theme CardView color
v6.0.0
- Update to latest AndroidX support library
- Fix crashes when online repos contain incomplete metadata
- Optimize BootSigner to use as little memory as possible, prevent OutOfMemoryError
- Support new communication scheme between Magisk v17.2 and Magisk Manager
- Enable excessive obfuscation to prevent APK analysis root detections (still not 100% obfuscated due to backwards compatibility with stable channel)
2016.10.04
Magisk-v7 is quite a significant update compared to v6. A lot has changed, new features are added, and improved compatibility a lot, especially in selinux issues.
Open Source!
My previous releases has some controversy due to the fact that I included closed source property with unexpected intentions. I had worked hard to create/improve open source tools, so that they can fit my own needs. Magisk is now 100% open source, including the binary it uses.
Brand New Magisk Manager
The Magisk Manager is completely a different application compared to the previous crappy app. It has now packed with features, and it is now part of the core experience of Magisk itself. New features and improvements are still planned, so stay tuned in this application's development!
Repo System, Module Management
We've been putting a lot of effort into constructing this repo system. This change is to make installing Magisk Modules a lot more easier. What I'm aiming is to make Magisk something like Xposed, an interface and a platform for developers to work on. Providing a repo system is a good step towards the goal, as it makes installing new stuffs and receiving updates super simple. I also drastically simplified the Magisk Module template. Right now, I believe anyone with basic knowledge can create their own Magisk Module easily. Changing a few values into a config file should make porting existing mods to Magisk much easier.
Safety Net
My decision to remove root management from Magisk seems to cause some debate. People might wonder why I would remove such feature that made Magisk so popular. Well, I have to emphasize again, Magisk is never meant for bypassing Safety Net. The Xposed and root bypasses are some fun projects that I'm messing with what Magisk is capable of. One of the two main reasons I dropped this feature in Magisk is
1. Xposed is no longer working with Safety Net enabled. I had tried to bypass it with some mounting tricks and process killing, but all of those are not able to fix the issue. Soon suhide is available and it is able to bypass Xposed had made me really frustrated, as I do not want to keep working on a "not complete solution".
2. On the open source side, phh is also developing his own "suhide". phh just released a test build for hiding root (link to his test build), I'm gonna take a look and include it into the Magisk version of phh root.
These two methods are much better than the one I was using. It doesn't need a toggle, it is per app basis, and many more. Also, I'm not creating a root solution, I'm creating an interface that root solutions can rely on. So I decide to give the hiding root "responsibility" to the root solutions, not managed by the interface, Magisk, itself.
Just to let all of you know, one of Magisk Manager's future feature will be a GUI to manage these two root hiding solutions. It will need some time to develop, and I also wanted to do some things in the core Magisk side to add this support natively. So please don't be pissed that I dropped the whole root management thing. It is for a bigger plan
Due to a bug in the template zip, there will be issues flashing the zip files if the path has spaces.
This commit in magisk-module-template should fix the issue.
All repos online is updated with this fix, developers please include this patch into your modules.
2016.10.19 Magisk v8
This release is aimed for bug fixes, and most importantly the ability to hide itself from Safety Net's detection.
Template Cache Module Fix
Due to a bug in the template script, if your module is a cache module, your scripts might not be executed correctly, also flashing in Magisk Manager will cause the UI to break.
This particular commit is the fix, only cache modules are needed to be updated, other modules are working fine.
Search Bar in Download Section
Magisk Manager 2.1 brings search bar to the "Downloads Section", so that it's easier to find a module once the list gets too long.
SuperSU Integration
In the previous release (v7), I decided to automatically convert SuperSU into a Magisk module while installing Magisk. In this release (v8), I make Magisk 100% compatible with SuperSU out of box, not needed to modify how SuperSU work in anyway. For v8 and future releases, Magisk will detect SuperSU patched boot image, and only add the required additional patches to the boot image.
Also, I created further integration for Magisk and SuperSU: Magisk will create a script placed in /data/custom_ramdisk_patch.sh when SuperSU detected. What this means is that the next time you upgrade SuperSU by flashing SuperSU zip in custom recovery, Magisk will automatically be injected. You can also apply OTA updates with FlashFire, and enable SuperSU injection, which will also inject Magisk on-the-go!
For users that was using v7 with SuperSU along with the Helper Module, please manually restore your boot image (should be stored in /data/stock_boot.img), and flash the latest SuperSU, then flash Magisk-v8.
Magisk Hide
This feature should've been released a few weeks ago, but university is killing me lately; overwhelming schoolwork prevents me to finalize the tool, so please pardon my absence and lack of support. But it's still better late than nothing .
In the weeks I have been inactive, Safety Net got a couple updates, each makes bypassing more of an hassle. Magisk v8 introduce "Magisk Hide", the tool to properly hide Magisk, preventing Magisk to break Safety Net features. What it can do is hide all Magisk modules' files and mounts from target processes (e.g. Safety Net), including Magisk compatible phh root maintained by myself.
It cannot hide SuperSU, it cannot hide Xposed. If you want to hide any of them, please use suhide developed by Chainfire.
It should not cause issues as I have been testing quite some while, but if you replace some files with Magisk (known: /system/etc/customize/ACC/default.xml), Google Play Service will constantly crash. Due to this fact, this feature is not enabled by default. You have to manually enable it in the settings of Magisk Manager v2.1 after you upgraded to Magisk v8, and reboot to apply the settings.
Right now, you can manage your own hide list with ways similar to suhide, no GUI:
Code:
(All commands should be run in a root shell)
# Show current list
/magisk/.core/magiskhide/list
# Add new process (the package name should work fine)
/magisk/.core/magiskhide/add <process name or package name>
# Remove a process (might need a reboot to make an effect)
/magisk/.core/magiskhide/rm <process name or package name>
The process com.google.android.gms.unstable (Safety Net) will always automatically be added to the list if Magisk Hide is enabled, so if you just want to bypass Safety Net, just enable in Magisk Manager and you're good to go.
Safety Net - The Already Lost Cat-And-Mouse Game
Keep in mind, in the latest update of Safety Net that just happened in a few hours, Google seems to step up the game, and it might got to the point that no modifications are allowed, and might be impossible to bypass.
Currently on my HTC 10, no matter what I did to the boot image, even just a repack of 100% stock boot image, Safety Net will not pass under any circumstances. On the other hand, my Nexus 9 running stock Nougat seems bypass without issues, with root and modules all enabled and working fine. The boot verification might vary from one OEM to another, HTC's implementation might just be one of the first included into Safety Net, but eventually all major OEMs' method will be included, and at that time I think any Android "mod", including custom kernels, will pretty much break Safety Net. These verification should be coded deep into the bootloader, which is not that easy to crack. So the conclusion is that I will not spend that much time bypassing Safety Net in the future.
The attachment is a screenshot about where to enable Magisk Hide in the app
Magisk MultiROM - POC
I spend some time playing with the possibility of Universal MultiROM by only using Magisk.
Surprisingly, it is not that difficult at all! Here is a small POC video demonstrating my HTC 10 dual booting stock rom and CM 13.
No other dependency is required (e.g. modified TWRP recovery, kext kernel patch etc.). You only need Magisk injected into the boot image, and along with proper settings, by swapping out the boot image, you can load any rom systemless-ly.
What this means is that all Magisk supported device can enjoy MultiROM features! What a great news for flashaholics LOL.
NOTE! The process showed in this video in far from what it will be eventually. I will make the process nice and smooth
2016.11.14 Magisk v9
This release comes with significant updates and changes, doing adjustments to pave the road for the next major update v10: the update with Multirom support!
Please spend some time reading this lengthy release note, the most important information are included in quotes, or bolded and colored in RED.
Also, many other fixes not mentioned here are listed in the changelog.
The End of Cache (post-fs) Modules
This shall be the biggest change for this update. One of Magisk's cool feature is that it can mount files before data and build.prop is loaded (post-fs). Most modules only uses this advantage to modify read-only props (e.g. DPI, fake device model etc.) without modifying build.prop, however with a new tool included in this release (will be introduced in the next section), dealing things in post-fs is not needed anymore.
Instead of having both "Cache Modules" and "Normal Modules" at the same time, confusing both developers and users, creating complexity in module management, the decision is made that "Cache Modules" are no longer supported after this update.
How about some features that require mounting in post-fs mode (known: Changing Boot Animation)? No worries, post-fs mode is still there (as Multirom will depend on this), I only removed the interface for modules.
Magisk no longer let you install cache modules, you have to manually add the files you want to replace, which is actually super easy.
You can place your new files into the corresponding location under /cache/magisk_mount, Magisk will automagiskally manage selinux contexts, permissions and the mounting for you.
For example, you want to replace /system/media/bootanimation.zip, copy your new boot animation zip to /cache/magisk_mount/system/media/bootanimation.zip with any root explorer, Magisk will mount your files in the next reboot.
Click to expand...
Click to collapse
Magisk v9 will remove all installed cache modules under /cache/magisk, which is the previous path where cache modules locate.
Further more, to push developers to upgrade their cache modules, the latest Magisk Manager (v2.5) will filter out cache modules, which means cache modules available in the Magisk repo are NOT shown under the "Download" section in Magisk Manager.
Cache Module developers please refer to the following instructions to update your current module:
Take a look at the changes in this commit (if you're famlier with git, you can just cherry pick this commit, and deal with some minor merge conflicts)
Check the "resetprop" section to understand how to change props without using a cache module, and update your modules accordingly. For example, if you want to replace the build.prop, you no longer need to enable "automount", or bind mount the file manually in your script, as nothing will load it again.; instead, you should enable post-fs-data script, and read your new build.prop file with proper commands. If you want to change certain prop values, just switch from post-fs script to post-fs-data script, and instead of calling "setprop", please call "/data/magisk/resetprop" to set your props.
Remember to remove the "cacheModule" entry or set to false in the module.prop file, or else your module will never show up in the Magisk Download section in the Magisk Manager!
New Badass Tool - resetprop
To be honest, this tool itself deserves a new thread on XDA, as it is super powerful and super cool.
"resetprop", originally named "xsetprop", was initially developed by @nkk71 to bypass the crazy tough detections for Safety Net. Developers found method to bypass the check by modifying the kernel source code, which served the need but the solution is far from perfect as it requires the source code to be available and kernel compiling.
The tool was originally made to directly modify the system prop database. With seeing the potential of this tool, I contacted @nkk71 and start collaborating together, which brings the original simple tool into a full-fledged, all-in-one prop management tool.
Here are some technical details:
System props are handled by "init", a binary located in the ramdisk which starts right after kernel is loaded. "props" are supposed to only have a single writer, and multiple reader, which means only the process "init" has the full control to the prop database. We modify the props (by calling setprop) through an interface called property_service, which will pass the request to init; property_service also handles the triggering of "events" that should be triggered by a prop change. What read-only props means is that property_service will block all requests for modifying props starting with "ro.", as those props are not allowed to be changed once set. To overcome this difficulty, we can mimic how init behaves by directly modifying the trie structured database. However we will not be able to trigger events, as we completely skipped the property_service part. This might be ideal for SN bypasses, but not applicable for Magisk, as I want to load any prop, which should trigger some events to make some changes. So we went a step further and added a feature to "delete" a system prop! As a result, by directly deleting the prop entry in the database, then send a request to property_service, property_service will accept the request and trigger events if needed.
The new tool - resetprop can modify/delete any system prop, including read-only props (prop names starting with "ro.")
You can also read a whole build.prop, overwriting all existing props. The binary will be installed to /data/magisk/resetprop.
Here are some examples for cache module developers to adapt to the new changes:
Code:
# Set any prop (with trigger)
/data/magisk/resetprop ro.sf.lcd_density 480
# Set any prop (without trigger)
/data/magisk/resetprop -n ro.crypto.state encrypted
# Delete any prop
/data/magisk/resetprop --delete magisk.version
# Read props from a prop file
/data/magisk/resetprop --file /magisk/somemod/new_build.prop
Click to expand...
Click to collapse
The tool is originally built with AOSP source, I spent some time to make it much more portable.
Here is the link to the NDK-buildable source of the resetprop used in Magisk: https://github.com/topjohnwu/resetprop
Magisk Hide - Greatly Improved
Another update to pass SN, please grab it before it expires lol
People started to panic when Google device to check boot loader / boot-verity etc. As stated in the previous section, resetprop fixes the issue easily with setting all detecting props to the valid values. However, more detection has been added. One of those is that simply adding Magisk directories into PATH will break Safety Net. Not sure if I should be glad because the word "magisk" is now officially on the tech giant's blacklist......
So in order to hide root (here I'm only referring Magisk phh superuser, as SuperSU users shall always rely on CF's suhide, not MagiskHide), I had to change the way things works.
For the new changes that are required to NOT modify PATH, the phh's superuser has to be upgraded.
Please make sure your phh superuser is upgraded to r266-2 (or any version higher).
Older version will NOT work with Magisk v9, please upgrade phh's su before upgrading.
Also, along with the new Magisk Manager v2.5, we finally had an GUI to add/remove apps from the MagiskHide list!
Click to expand...
Click to collapse
Development
I added build.sh into the main Magisk repo, you can call the script and it will guide you with help messages.
Custom version names are supported, both in Magisk and Magisk Manager (if using custom name, update will disable)
So feel free to clone the repo and develop Magisk yourself! Pull requests are appreciated!
For Magisk Manager, you can provide translations for the app, just translate the strings, create a pull request, and I'll merge it into the main app, many thanks!
Those Pixels
I stated before that the new Google Pixel devices are using a complete different partition structure, as the ramdisk is now stored along with the system partition, and a kernel modification is inevitable.
Without much surprise, our mighty developer Chainfire had released a systemless root for Pixel devices. What it does in a nutshell is bringing back the ramdisk to the boot image, and still do modifications in the ramdisk (rootfs). However it still requires 1. custom init binary 2. binary patch directly to the kernel. If I decide to use the provided closed source solution, it shall not be difficult to port Magisk to the Pixels and start all the systemless craziness, but still I need an device to test and debug. In addition, I would love to see if I can create an open source tool to achieve similar results to make Pixel (which means maybe all future devices) running Magisk.
But the huge issue is: I live in Taiwan, and there is no sign that the Pixels will be available for purchase here, well at least not possible in 2016.
I could ask my buddy studying in the US to bring me one when he comes back at the Christmas vacations (which is still quite some time from now, but still better late than nothing.....), however the problem is that Pixel XLs (the model I prefer) are currently out of stock on the online Google Store, and I will never know if ordering now will make the package show up in my friend's place in time before he comes back to Taiwan.
If anyone seeing this post has access/can purchase brand new Pixel XLs (anywhere should be OK), and possible to deliver them to Taiwan in a reasonable time and a reasonable shipping fee, please contact me and I'll be very happy.
Lastly, I just bought my new HTC 10 within a year. I'm just an university student, the money I earn from tuition could afford me the super expensive Pixel device, but any additional donation to support my open source development is highly appreciated . I'd be really happy that many people love my work!
Click to expand...
Click to collapse
Here are some news....
Lack of Support
School have been super busy lately (getting the last metro to home nearly every day...), I have little if any time to spend on Android development. Another big factor is that I'm still waiting for my laptop to be repaired.
Sorry for all the private messages sending to my inbox, I've got way too many PMs that I'm not in the mood to read through dozens and dozens of them, since a large fraction of them are simply just asking for instructions for installing Magisk on their device.
I prefer REAL issues to be opened on Github, as I check them from time to time, and I can keep track of which are not yet resolved.
Build Friendly
I added build script for Unix-like systems (Linux and macOS) and also for Windows. I tested on all three platforms and all of them are working as expected. For people interested in the latest feature added to Magisk but not included into an official release yet, feel free to build it yourself. I automated the process that even people with no experience in NDK or scripting can build it easily.
Also for people willing to report bugs, please test Magisk built against the latest commit before opening issues on Github, thanks a lot!
Magisk Module Repo?
It has been a while since I last updated the Magisk Module Repo. I know there are a few requests for adding their own modules to the repo. I'm gonna change the way for requests to be handled from the current "posting in a request thread on XDA", to most likely handled through Github. When the new way for requests is decided, I'll add the current requests at once, and close the current thread.
I really appreciate every person who is interested in making a Magisk Module and willing to share it with others, once the new method is decided, the requests should be addressed in a timely manner.
Multirom? Updates?
I've spend my extremely limited free time to fix current Magisk issues, and so far (the latest commit on Github) it has improved a lot compared with the current v9 release.
I haven't really spend much time in the multirom feature, however I found an interesting open source project: DualBootPatcher.
It exists for quite a while, and it is very impressive just like the Multirom Tasssadar created. I haven't looked into how DualBootPatcher works, so I'm not sure if it is using similar tactics method that I switch between systems in a super simple way through Magisk.
2017.1.2 Magisk V10
Happy New Year! What is a better way to celebrate 2017 than a Magisk update
Another massive update!
Official Icon
Instead of using the picture grabbed online, the official Icon for Magisk is now live!
Magisk Hide Back On Stage
This is the most awaited fix, isn't it?
The issue of losing root is haunting since day 1 of the release of Magisk Hide, although it can be temporary recovered with a reboot, it is still quite annoying. I spend a lot of time trying to identify the reason, and soon found out that the issue is caused by MagiskHide reacting "too fast". Most processes starts from Zygote, and it requires a small period of time to isolate the mount namespace apart from Zygote. When MagiskHide reacts too quickly, it will unmount all mounts in the Zygote namespace, which literally means that all processes will lose the mounts (including root).
After adding checks and retries before switching namespaces, it leads to another issue: MagiskHide reacting "too slow". When critical files like framework is Magic Mounted, and the unmounting doesn't happen in time, it will break the SafetyNet checking process (Google Play Service FC), and can never recover until a reboot (or full restart of Google Play Service). I added tons of safety precautions (I won't go into the details here, it will be another few hundred of words), and I can "almost" eliminate all possible breakages.
Due to the fact that Magisk Hide DOES NOT hijack app_process (Zygote), it can only react passively, so there is a limitation to the effectiveness.
The best practice is to NOT add a lot of apps in the blacklist of MagiskHide (managed in Magisk Manager), so that the MagiskHide daemon has the time to react.
Personally I only hide SafetyNet (the preset), and it passes all excessive tests without any issue. However my tester still managed to break it a few times when adding 6 additional apps, and having 10+ accounts syncing at the background all the time. So I guess it is good for most users lol
Magic Mount With No Limits
I'm glad to announce that starting from this update, Magic Mount can do ANYTHING! Thanks to the new mirror implementation and some workarounds in the algorithm, it can now handle adding files to /system root (and /vendor root if separate partition). Also thanks to the new MagiskHide, all mounting combinations can pass SafetyNet!
Magisk Powered Custom ROM: One Click to Custom ROM, Another Click You're Back to Stock
I am a member of an HTC custom ROM developer team - Team Venom, and without too much effort, The world's first Magisk Powered Custom ROMhttp://venomroms.com/worlds-first-100-percent-magisk-rom/ was born!
The advantage over traditional full packaged custom rom is that we ROM developers no longer need to port carrier features (Wi-Fi calling, VOLTE etc.) to our ROMs. Users can install Magisk on their stock devices, load the Custom ROM module, reboot and BOOM all done, along with 100% fully working carrier features. Also, it is just cool to load a custom ROM fully systemless, isn't it!
Developers in the HTC 10 community soon realized the "power of Magisk", and currently trying to push out more and more Magisk Custom ROM Modules.
I hope all developers feel the excitement, and port all stock modified custom ROM to be implemented with Magisk!
For ROM developers interested, please check the link and download the zip to get an idea how to create your own Magisk Custom ROM Module!
Magisk Can Now Root Your Device
I decided to fork the phh Superuser and start doing modifications. From Magisk v10 and after, Magisk will root your device with the bundled root if
a. No root installed b. Root that isn't Systemless SuperSU or older Magisk phh versions installed
Right now you still have to install the phh Superuser application, however the root management should move to Magisk Manager soon, please stay tuned.
Currently it is nearly the same as official phh root with only a few tweaks, but I might add more in the future.
Magisk Manager Now On Play Store
It seems that some already found out that Magisk Manager is now available on Play Store! All future updates will be pushed through Play Store.
Download links will still be posted here, since there are still places where Play Store isn't available.
Documentations Updated, Module Template Updated, New Repo Requests
The documentations here on XDA is pretty outdated, I updated them with more info to assist developers and users to create their own modules.
Module template is updated for an addition option to load a prop file.
Repo requests are also updated, please check out the new instructions!
Sorry guys, in v10 (and the v10.1 if you're fast), when updating within the Magisk Manager, my scripts didn't handle the phh upgrading correctly.
For those got stuck with no root, please flash the latest phh zip downloaded in this thread in custom recovery (or Magisk Manager, because it is the only app that have root access).
Sorry for the inconvenience, please forgive me lol, I'm only one man!
2017.1.11
Magisk Manager v3.1
I'm still dealing with my finals (got an exam tomorrow, and 3 more projects to do......), but the online repo is no longer accessible on Magisk Manager, which forces me to push out an update.
Apart from that critical bug fix, it also comes with a lot of updates and improvements, please check the changelog for further info.
Please update your Magisk Manager from Play Store. The direct link is also updated with the new v3.1 version
Magisk v11.0
2017.2.6 Magisk v11.0
Came back from Chinese New Year holiday with some significant updates!
Introducing MagiskSU
Magisk officially becomes its own rooting solution!
Initially I just want to add root management features into Magisk Manager, but ended up updating lots of code.
Since the changes are quite significant, and no longer compatible with older versions, I'll just name it MagiskSU instead of phh Superuser.
The code is based on phh's approach to update the CM Superuser. I spent quite some effort to achieve SuperSU standards, so far the functionality should be nearly equivalent, my only concern now is compatibility, which is what I will focus on in future releases.
Please note, Magisk is still fully compatible and functional with the latest SuperSU (tested against v2.79-SR3)
The Fully Re-factored sepolicy-inject tool
To accompany with the fresh new MagiskSU, I also spent a ton of effort re-factoring the tool sepolicy-inject.
The tool now accepts policy statements, you can get more info about it from from this section of @Chainfire 's wonderful How-To SU documentation.
Basically I aimed to follow the same syntax as SuperSU's supolicy tool, as it is straight forward and same as the .te policy sources. I added a few additional features in sepolicy-inject, you can directly execute the binary with no options to refer to the help info.
See all changes in the changelog
(I named it "sepolicy-inject" instead of "supolicy", since it still differs in many ways (e.g the built-in rules) even though the syntax is now nearly identical. Root app developers might want to handle this difference when live patching sepolicies)
Pseudo SELinux Enforce Mode
Thanks to the new sepolicy-tool, pseudo enforced mode is now possible (the status shows enforced, but actually is permissive).
In some versions of Google Play Services, setting SELinux to permissive causes Safety Net to fail; however some custom ROMs require the system to be in permissive to be fully functional (although it should be considered as a bad practice). This shall be the perfect solution.
This will not be as a switchable option within Magisk Manager, since Google has a history of pulling apps from the Play Store when related to SELinux (see the tragic example of developer @flar2 's awesome app, and there are still more incidents).
MagiskHide binary is now updated to detect the permissive state, patch the current sepolicy to pseudo enforced mode, then switch back to enforced.
ROM developers don't have to change anything, just simply set to permissive on boot with a bundled app or a boot script as usual. If a user decided to enable MagiskHide, it will handle everything itself.
General Purpose Boot Scripts
I removed this feature in Magisk v4 and favored the per-module scripts. Now I decided to bring it back again.
The scripts should be placed in /magisk/.core/post-fs-data.d and /magisk/.core/service.d. The directory name should be self-explanatory.
If you have no idea which to choose, the post-fs-data.d will be a nice bet.
So Magisk will now execute script named post-fs-data.sh in each module, and all files within post-fs-data.d. The same applies to service.
Future
Thank you for everyone providing translations to Magisk Manager, and huge thanks to all donated.
I appreciate all the support, and that is my motivation to continue pumping stuffs out!
I will be maintaining MagiskSU continually; support won't end, at least in the near future.
Magic Mount features and better Magisk Module support are also on my list.
I spent zero time on adding more support to devices in v11, all the effort were put in MagiskSU and MagiskManager and major bug fixes.
The whole project is now in the state I consider "feature-packed" enough, most users/developers haven't used the full potential of the features.
I'll stop adding major new features and instead focusing on bringing Magisk to more devices that currently isn't supported.
And yes, that means I will postpone the long planned but never worked on Multi-ROM feature (I barely spent time on it after the POC video)
Hope you all will enjoy the update
(P.S. It's 9 AM here and I haven't slept. I'll update documentations after some sleep)
Before I got the in-app guides done, here are some tips for you
Many people seems missing these details
2017.2.19 Magisk Manager v4.2
Magisk Manager v4.2 is now live on Play Store. OP direct links are also updated accordingly.
Tons of improvements to the app, check the changelog for more info
Where is the Magisk Update?
I'm aware there are issue in Magisk v11.1 (vendor mount issues, and MagiskSU system rw issue)
I already fixed the system rw MagiskSU issue (so TiBack now 100% functional), you can check the Superuser sources if you're interested into the solution
I'll push an update soon after I fixed all currently known issues, AND add compatibility to more devices.
Please note that I'm only one single man, and also got a real life to deal with, so I can only focus one thing at a time.
I decided to first improve the Magisk Manager application to a point I think it's acceptable. Android application development is quite tedious, I have to put quite some time and effort into it.
After this Magisk Manager update, I will put all my attention on the core Magisk part, so please stay tuned!
New Online Module Info Display
I updated the way Magisk Manager show the details of Online Magisk Modules in the repo.
Previously I let each module include a changelog.txt, donate link, and support link
However, I think it would be better to let module developers to write anything they want
And considering the text rendering needs to be nice and clean, I think Markdown is the best choice here!
You can include links to your thread, links to your donation link, download link for an app required, changelog.... anything!
All Repo Developers Aware!
In Magisk Manager v4.2, the app will read the README.md file within your repo, and render the file properly
The changelog.txt file, support and donate entry within module.prop are no longer read, they can be removed.
Please update your README.md file ASAP to let the new app properly display what your modules do.
Here is an example, I updated the Xposed module's README.md, you can see the results in attachments
This is also a screenshot of what the new UI looks like
Magisk Manager v4.2.5 is live!
Hot fix for Samsung crashes (theoretically, no device to test), also did several adjustments here and there
As usual, full changelog in 2nd post, direct links and Play Store (might need to wait a few hours) are also updated
Sorry for the inconvenience!
Magisk Manager v4.2.6
Finally got the Samsung crash fixed!! Thank you for everyone reporting giving feedback, really appreciate the community!
As a compensate for the frequent updates and inconvenience, I added another feature that was requested to Magisk Manager - add a setting to disable update notifications
Play Store might take a few hours to update, direct link in OP is updated
Finally, I can now focus on the core part, which IMO is much much more important
Device compatibility should be GREATLY improved once the work is done, stay tuned!
For Pixel support though, I'll need to borrow my friend's Pixel XL for a couple of weeks to develop, but this might not happen soon since school is quite busy.
2017.3.21 Magisk v11.5/v11.6
It's about time for some Magisk update!!
Magisk Binary Changes
The original tool sepolicy-inject is now renamed to magiskpolicy. However, for backward compatibility, a symlink named sepolicy-inject will be created, which simply just links to magiskpolicy
The original tool bootimgtools is now renamed to magiskboot, which is a complete rewrite of the existing boot image patching tool. More info later.
Starting from this release, magiskpolicy, sepolicy-inject, resetprop, and if MagiskSU is installed, su, and supolicy (this is NOT the SuperSU supolicy, it just links to magiskpolicy, exists for compatibility) are all added to the PATH, which means you can directly call these commands through shell (and apps) without explicitly calling "/data/magisk/XXXXX"
In a nutshell:
Code:
/sbin/su -> /data/magisk/su
/sbin/resetprop -> /data/magisk/resetprop
/sbin/magiskpolicy -> /data/magisk/magiskpolicy
/sbin/sepolicy-inject -> /data/magisk/magiskpolicy
/sbin/supolicy -> /data/magisk/magiskpolicy
/data/magisk/sepolicy-inject -> /data/magisk/magiskpolicy
New Boot Image Tool: MagiskBoot
I spent a lot of time rewriting the whole boot image patching tool. For now it shall GREATLY improve the compatibility of Magisk. Key features:
Complete rewrite boot image extracting process
Proper MTK header support
Sony ELF type boot image support
Native ramdisk compression method support : gzip, xz, lzma, bzip2, lz4
This means custom kernel developers can now use a different ramdisk compression method with their custom kernels!
Native cpio patching support: auto ramdisk backups, auto ramdisk restores, auto dm-verity patch, auto forencrypt patch, native cpio extract/mkdir/add
This means boot patching process itself does not require root access anymore (it usually does)
Native LG bump and Samsung SEANDROIDENFORCE flag detection
More Magisk installation methods shall come soon!
I believe some of the features above do not exist in any existing rooting methods, I hope this will bring more users on the Magisk bandwagon
MagiskSU Fixes
In all current open source root methods, a common issue is that some apps (most well-known: Titanium Backup) cannot properly mount /system to read-write. Here I'll only briefly explain the technical details.
After spending very many hours, the victims are narrowed down to programs that directly use the "mount" system calls instead of calling the "mount" command. Also, the issue does not only happens to /system, but instead any read-only partitions. The only way to remount them to rw is through the toybox implementation of the mount command, which should be the default of all devices. This means that any external mount command (e.g. busybox) cannot remount them to rw either. After digging through the AOSP toybox source code and some search through the commits, I finally found the culprit: this commit in AOSP. What that commit does in a nutshell is that all blocks mounted read-only will be locked to read-only.
So starting from this release of MagiskSU, all blocks will be unlocked when the daemon is started (this does NOT break your system integrity, meaning it does not break OTAs), everything should work fine.
Another subtle change is that the command "-cn" will not do anything starting from now. All root developers can call the "-cn" command on both SuperSU and MagiskSU, it shall work in both cases.
I had tried to add the "-cn" command in the previous release, which only exists in SuperSU, but it was not implemented correctly, and apps depending on it will not work correctly.
However, this "context switch" command is originally added to SuperSU due to the way it managed selinux back in the old days. The way I deal with selinux, starting from Magisk v7 (Chainfire switched to similar method in his latest beta) DOES NOT need any context change, as all root procedures and processes are running in a permissive domain (in Magisk's case it's a domain that allows everything, which is slightly different to permissive. This is because permissive does not work on Sammy)
Magic Mount Vendor Issues
In Magisk v11.1, devices with a separate vendor partition (newer Nexus devices) will fail to properly magic mount files in vendor, the most common issue is using the ViPER4Android Magisk module.
It is now fixed in v11.5
Module Template Update
The Magisk Module Template is now updated. All developers please adapt your modules to the newer version
An entry in module.prop called template now indicates the template version number.
In future Magisk Manager updates, it will only show the modules that are using the latest two versions of the template.
e.g. If the latest template version is v13, only v13 and v12 modules will be showed in the repo
This gives the time for developers to update their modules, but also enforcing them to adapt to newer scripts, so I don't need to support the old template formats.
I apologize that I was busy and didn't add the existing module requests, I'll add them once you have migrated your module to the latest template
Also please note that I will NOT add modules that ONLY change some props using resetprop, as this is a upcoming feature to Magisk Manager in the near future.
What's Next?
Magisk v11.1 got over 500K downloads! Thank you for all the support!
The next short term goal is to add more features into MagiskManager (including the mentioned prop management, and a new installation method)
The long term goal will be migrating the current script-based magic mount to C program, which shall be run as a daemon in the background, combining resetprop, magiskhide etc. all-in-one. This will take some time to finish though.
For the long awaited Pixel support, I think I'll start working on it, but the complexity of that device might take a very long time for me to understand, since I do not own the device. I can only borrow my friend's device for not that long of a period of time, so progress shall be really slow. I'll not get the Pixel device now, because I don't think it is worth the price and the hassle for me to import it into Taiwan, but I'll definitely get the Pixel 2 to replace my current daily driver lol.
Magisk v11.6 Hotfix
The issue turns out to be a veeeery minor issue, but causes the whole script unable to run correctly on Samsung devices.
Also, I fixed the incorrect value for selinux prop patching for MagiskHide, so people with selinux issues should now be settled.
I guarantee all future releases will go through serious beta testing, especially Samsung devices. This project is in a scale that these kind of mistakes cannot be tolerated.
I'm sorry for all the inconvenience the previous release gave you, and the mess and headaches for all broken devices.
The Module Template is again updated. This bug will also affect module templates, so please update accordingly, thanks!!
But still, I hope you will enjoy this new release
2017.3.31 Magisk V12.0
The major version bump should label this release as a stable release (at least this is what I hope)
This release is thoroughly tested by all my testers, especially focusing on Samsung devices
Unless major issues, the next release should be a complete new redesign, and requires more time, more info later
The FAQ in OP is updated, please check them out!!!
Samsung, Samsung, oh Samsung
My previous release was widely criticized for breaking tons of Samsung devices, the rating on Play Store also reflected this fact
Thanks to helpful testers and developers, we ironed out all the quirks of Sammy, and in addition added more Samsung specific features.
One is adding proper support for Samsung permissive kernels. Another is faking KNOX to 0x0 if MagiskHide enabled.
Is that good enough to compensate my mistakes in the last release?
Sepolicy Live Patch Moved
Another critical update is that the sepolicy live patching is now moved from the post-fs-data mode to the service mode.
This decision is done due to the fact that on some devices (e.g. Samsung), there are too much to patch, which greatly delays the bootup time if the live patching is done in a blocking stage. However, this will require some updates for the minimal sepolicy rules.
The minimal patch is now a little more complete, which requires 20-80KB of ramdisk size (previously 1-4KB). Still not large to be honest.
However, this makes post-fs-data mode NOT completely unrestricted. post-fs-data mode can still do any file related operations, setting system props etc., a lot more than normal users would use. However, service mode would be guaranteed to be executed AFTER the full sepolicy patch is done.
It is recommended to run most scripts in the service mode (service.d/service.sh), except a. mounting files; b. patching system props; c. time critical operations
Magisk Core Only Mode
People complain that Magisk has "too many features", they don't want to use such "complete" solution.
Here I introduce Core Only Mode. It can be enabled in the new Magisk Manager.
What will still be started: MagiskSU, post-fs-data.d, service.d, (if enabled: MagiskHide, systemless hosts, systemless busybox)
What will not be started: Cache (post-fs) mounts, magic mount (system mirror etc.), all modules, all module scripts
So it literally limits Magisk to root + boot scripts. MagiskHide is still there for those who want some Mario Run lol.
Say Goodbye to Outdated Modules
This day finally comes. All modules on the repo that aren't using the latest template (v3 for now) are now hidden.
This not only guarantees that the modules are using the latest scripts, but also a nice way to filter out modules that are no longer maintained by the uploader.
You have to add/update template=(ver) in your module.prop. Magisk Manager will not know if you only updated the scripts
Upcoming Features
Here are some planned features (sorted in priority)
Magisk Manager resetprop GUI
MagiskSU multiuser support
Unified Magisk daemon: As stated before, I'm planning to write Magic Mount in code to achieve more efficiency and features.
All current Magisk features (magiskpolicy, magiskhide, resetprop, superuser, magic mount) will be in a unified daemon
Pixel (XL): Some developers has done some progress, I'll contact them and sort things out
Android O: I bought a Nexus 5X now, finally got some O love
Some details are changed in v12.0, I'll update the documentation (wiki) soon.
Some Recent Updates
I wish I can be more vocal in the forums, so more information can be spread to the community, but being a university student in Taiwan, studying engineering specifically, is not easy.
It has been a while since the last release, I think I would shed some light regarding the next big update.
Unified Binary
First, the most obvious change is that Magisk no longer rely on the overly complicated scripts, but instead replaced with pure C/C++ programs. Along with Magisk's development, more and more features were added, and those cannot be done with scripts are added as binaries (magiskhide, magiskpolicy, resetprop etc.). As a result, in the last build (v12.0) there are tons of binaries scattered, loosely working together with poor communication.
So the first thing to do is to combine everything as a single program, something like busybox, which is a single binary that acts as multiple utilities. This took me quite some time to finish, especially merging the existing superuser with other parts that also requires daemon connection. Another tricky part is to port the spaghetti shell script into proper C code. The good news is that both of them are done (though, some small bugs might exist and I'm currently hunting them down)
No More Busybox!
Second is the decision to remove the bundled busybox. Initially I added busybox into Magisk due to lack of proper commandline tools in native Android environment (e.g. lack of losetup in Android 5.0), and also many selinux specific options for several utilities do not exist in official AOSP toolbox/toybox. The big problem is that the busybox causes more issues than I would ever expect. Many features in v12 are implemented to only work with that specific busybox bundled with Magisk. However due to the variety of configurations of custom roms, the assumption that the target busybox is always there, working as expected obviously isn't true, leading to numerous breakage and headaches. This is one of the reason why tons of issues submitted to Github are not addressed, because all pre-v13 are haunted with the same issue - the environment Magisk is running is a mess.
However, thanks to ditching shell scripts completely, currently I handle everything by natively calling system calls, or by implementing the functions directly into the binary (another tedious task...). So Magisk now works as a complete package itself, no more dependency and requirements in the environment. Due to this change, the Magisk Manager would need to include a busybox in order to provide the environment to install Magisk modules/Magisk updates, which I think many tracking the development on Github would already notice this change.
Those wondering how to add busybox if they want? I'll release a new module in the repo.
Android O
Finally, Android O support! As expected, Android O has quite some security changes, but since I'm gonna start everything from scratch anyway, things are all quickly sorted out. Also thanks to the arrival of my Nexus 5X, I can finally test things on an actual device, as a result Magisk is now 100% working on Android O DP1. The module template might need some slight updates regarding Android O changes, please stay tuned for the announcement!
Of course, tons of other improvements are also included, I won't list all of them here and will leave them for the release post and changelogs. Updates to Magisk Manager are also work in progress (application development is very tiresome...). There are still tons of features/support bugging in my mind and I would hope I can implement all, but the reality and school prevents me to do so, I am now aiming more towards a stable release rather than rushing out poorly designed features and making me regret in future maintenance lol.
I won't have time to publish lots of informative posts as this one, for those who are interested in the active development of Magisk/Magisk Manager, please keep track of the Github repos. I always keep the development work transparent, anyone curious can spend a little effort to build it themselves and have a sneak peak of what's currently going on. Just keep in mind that the cutting edge master branch does not always work properly
- MultiFunctionsPlus Is The Successor Of MultiFunctions
- The Main Difference: The Pre-Activated Functions = Flashing MultiFunctionsPlus + Activator = Flashing MultiFunctions Only Or Deactivating The Pre-Activated Functions = Flashing MultiFunctionsPlus Only = Flashing MultiFunctions + Deactivator
Click to expand...
Click to collapse
MultiFunctionsPlusPage 1 Of 2Introduction:
A Module To Do The Next Functions [Clearing DalvikCache-PlayStoreWithServices-MagiskHideList, Changing The SELinux Mode, Booting The Android Into Safe Mode, Opening Magisk In Core Only Mode, Controlling The Virtual Memory (Swap), Changing The Swappiness Value, Keeping MagiskDaemon-MagiskHide Running, Changing DoubleTap2Wake(DT2W) Status, Fixing PlayStore Device Certification Status - Passing SafetyNet, Enabling The Low Ram Configurations, Disabling The Other Magisk Modules, Disabling The Magisk General Scripts & More].
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring Apps, Modules, Scripts Or HideList, Check Activator (+Bootloop/Bootscreen/Blackscreen Resolver For Apps, Modules, Scripts & HideList) In Below
- P.S. All Functions Are Deactivated/Disabled By Default And The Needing To Activate Each Wanted Function Is Described In Below
- P.S. All Functions Can Be Used With Any-Rooting-Tool Except The Ones For Magisk Users Only As Described In Below
Current Version: MultiFunctionsPlus v1.0.3.4.2.4B7 - Activator v1.0.0.17A4.0.0 - QuickFix4Busybox v0.0.0.0.0.3
Recommendations:
- For Magisk Users Only, Disabling MagiskCoreOnlyMode From The Section Of Settings In Magisk Manager & Rebooting The Device Are Required To Load The Modules
- For Activating Any Function Using Any Root File Explorer Such MiXplorer To Access The Part Of Data Thru Root, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/<TheFunction>/Inactive And Then Reboot The Device
- P.S. In-Case Of Moving/Deleting The File Of Disable In Error, Deleting The Folder Of Status (/data/DreamerMods/MultiFunctionsPlus/Status) & Rebooting The Device Will Create The File Of Disable Again
- Activator Is A Bootloop/Bootscreen/Blackscreen Resolver For Apps, Modules, Scripts & HideList (P.S. MultiFunctionsPlus Is Required To Be Flashed Before Using Activator) So Actually There Is No Needing To Flash It To Use Any Function Such SELinuxModeInverter
- After Flashing The Module Of Activator & Rebooting The Device, It Will Do Its Functionality & Remove Itself
- P.S. For Any Magisk Version Below v14.0(1400), Use Any Method To Flash The Module As Described In Below Except Magisk Manager
- P.S. For Some Versions Of Magisk, Use QuickFix4Busybox As A Resolver For The Issue Of Internal Magisk Busybox Which Prevents Some Of Commands From Executing
Created: Nov.30.2019
Updated: Feb.22.2020
Download Link: Click Here (To Ensure That The Module Will Work Properly, Kindly Do What Are Mentioned In The Description)
** Magisk Installer: It Supports Magisk Only
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To v20.1(20100)
- For The Module Which Is Ended Its Name With v19000P (Or MMTEx1.x), It Supports Magisk v19.0(19000) To The Latest Version
** Unity Installer: It Supports Any-Rooting-Tool Such SuperSU, Lineage-AddOnSU & Magisk
- P.S. If You Flash The Same Version Of Module Twice, The Module Will Remove Itself But If The Version Of Second Time Is Higher Than The Version Of First Time, The Module Will Update/Upgrade Itself
- For The Module Which Is Ended Its Name With Unity1.5.x, It Supports Magisk v15.3(1530) To The Latest Version
- For The Module Which Is Ended Its Name With Unity1.5.4Ax, It Supports Magisk v8(800) To The Latest Version
- For The Module Which Is Ended Its Name With Unity4.x, It Supports Magisk v18.0(18000) To The Latest Version
- For The Module Which Is Ended Its Name With Unity5.x, It Supports Magisk v19.0(19000) To The Latest Version
Installation:
- Magisk Manager --> Modules --> Add (+) --> Choose The Downloaded File --> Reboot
- Or Flash It Thru A Custom-Recovery Such TWRP Recovery --> Reboot
- Or Flash It Thru ADB Sideload --> adb sideload TheFileNameOfModule.zip --> Reboot (P.S. Renaming The File To Have A Short One Is Recommended Such mfm.zip Before Using ADB Sideload)
- Or Using A Flash-Tool (Flasher) Such EX Kernel Manager, FK Kernel Manager, FlashFire Or Flashify --> Flash ZIP File --> Reboot
The Description: (1)
1- DalvikCache Cleaner (Advanced Dalvik/ART Cache Cleaner)
- Clearing The Dalvik Cache
- Doing The Same Functionality Of Wiping Dalvik/ART Cache Thru TWRP Recovery
- Removing All Remnants Of The Uninstalled Apps & Resolving/Fixing Some Issues With The Installed Apps
- Maybe It Takes About 5 Min. To Finish The Process
- After Doing Its Functionality, Check The Free Space Of Internal Storage Which Should Be Increased/Maximized A Little Bit
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of DalvikCacheCleaner, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/DalvikCacheCleaner/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
2- PlayStoreWithServicesData Cleaner (Advanced PS-GMS Data Cleaner)
- Clearing The Data Of Google Play Store & Google Play Services
- One Of The Methods To Resolve/Fix The Battery Draining & Re-Check PlayStore Device Certification Status
- After Doing Its Functionality, Check PlayStore Device Certification Status (Google PlayStore --> Settings --> Play Protect/Device Certification) Which Should Be Hidden For A While During Getting Its Status From Google
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of PlayStoreWithServicesDataCleaner, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/PlayStoreWithServicesDataCleaner/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
3- MagiskHideList Cleaner (Including MagiskHide Enabler & MagiskHideList Backup) [For Magisk Users Only]
- Clearing MagiskHideList [All Added Apps/Activities/Processes In MagiskHideList]
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Adding App/Activity/Process To MagiskHide, Use The Function To Clear All Apps/Activities/Processes From MagiskHideList Which Maybe Caused The Bootloop/Issue
- Activating The Function = Doing Its Functionality, Taking A Backup Of HideList & Disabling Itself
- For Activating The Functionality Of MagiskHideListCleaner, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskHideListCleaner/Inactive And Then Reboot The Device
- Additional Feature (Deactivating The Main Function + Activating The Sub-Function Of BackUp [Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskHideListCleaner/BackUp/Inactive And Then Reboot The Device] = Taking A Backup Of HideList)
- Additional Feature (Deactivating The Main Function + Putting A Copy Of The File Of HideList.txt Into The Folder Of Retrieving [Copy The File Of HideList.txt From /data/DreamerMods/MultiFunctionsPlus/MagiskHideListCleaner/BackUp/HideList.txt To /data/DreamerMods/MultiFunctionsPlus/MagiskHideListCleaner/BackUp/Retrieving And Then Reboot The Device] = Retrieving/Restoring The Last Saved MagiskHideList)
- Additional Feature (Activating The Sub-Function Of HideEnabler [Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskHideListCleaner/Hide/Inactive And Then Reboot The Device] = Enabling MagiskHide Once At Every Booting)
Click to expand...
Click to collapse
4- SELinuxMode Inverter (Advanced SELinux Mode Changer/Manager)
- Inverting The Default Android SELinuxMode During Startup ([From Permissive To Enforcing] Or [From Enforcing To Permissive])
- The Function Changes The SELinuxMode For The Entirety Of The Device's Uptime Until Next Reboot
- The Default Android SELinuxMode Can Be Either Enforcing Mode Or Permissive Mode Which Depends On The Installed/Flashed Rom/Kernel
- SELinux Enabled Kernel/SELinux Development Mode Is A Main Point To Use The Function (The Installed/Flashed Rom/Kernel Must Have The Ability To Switch Between Enforcing Mode & Permissive Mode)
- Enforcing Mode Is Preferable For Security (Specially Banking Apps) & Permissive Mode Is Preferable For Mods (Specially Audio Mods)
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of SELinuxModeInverter, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SELinuxModeInverter/Inactive And Then Reboot The Device
- Some Issues Which Are Related To Rooting-Tool/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Resolving The Issue Of Bootloop/Bootscreen/Blackscreen Which Changes The SELinuxMode Within 5 Min. After Rebooting & The Fast Mode Can Be Used For Changing The SELinuxMode At Booting But You Need Firstly To Do What Are Mentioned In The General Steps]
- For Activating The Fast Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SELinuxModeInverter/Wait/Active And Then Reboot The Device
=============================
The General Steps- SELinux Enabled Kernel/SELinux Development Mode Is Required Which Means The Installed/Flashed Rom/Kernel Has The Ability To Switch Between Enforcing Mode & Permissive Mode
- To Check The Above Mentioned Ability, Install Terminal Emulator From PlayStore --> Open It -->
-----> For Getting The Current Android SELinuxMode, Write su --> Click On Enter --> Write getenforce (Most Devices) Or sestatus (Some Devices) --> Click On Enter
-----> For Setting The Current Android SELinuxMode, Write su --> Click On Enter --> Write setenforce 0 (For Permissive Mode) Or setenforce 1 (For Enforcing Mode) --> Click On Enter
-----> Check Again The Current Android SELinuxMode
-----> If The Mentioned Steps Worked/Succeeded, Activate The Function Of SELinuxModeInverter
-----> Enforcing Mode Is Preferable For Security (Specially Banking Apps) & Permissive Mode Is Preferable For Mods (Specially Audio Mods)
-----> If The Mentioned Steps Didn't Work/Succeed, It Means The Flashed Rom/Kernel Hasn't The Ability To Switch Between Enforcing Mode & Permissive Mode So Flash Another Rom/Kernel Which Supports The Ability Of Changing SELinux Mode
- P.S. Maybe The Flashed Rom/Kernel Hasn't The Ability To Switch Between Permissive Mode & Enforcing Mode During Startup So You Can Use Only The Wait Mode (Not The Fast Mode)
Click to expand...
Click to collapse
5- SafeMode Enabler
- Booting The Android Into SafeMode
- In-Case Of Facing A Bootloop Issue Due To Installing/Configuring An App, Use The Function To Remove Any App/Its Data Manually Which Maybe Caused The Bootloop/Issue (Rebooting The Device Manually Is Required To Get Back To The NormalMode)
- The Function Disables All Installed Apps (User Apps) & Also The Root Access By Enabling SafeMode & After Booting, Remove The Data/Uninstall Any App Which Caused The Bootloop/Issue (From Settings --> Apps --> The App --> Storage --> Clear Data/Uninstall) Then Reboot
- SafeMode Gives The Device The Ability To Not Open Any App Which Is Installed As A User App, And A "Safe Mode" Badge Will Appear In The Lower Left Corner Of The Screen
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of SafeModeEnabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SafeModeEnabler/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
6- MagiskCoreOnlyMode Enabler [For Magisk Users Only]
- Opening Magisk In CoreOnlyMode
- In-Case Of Facing A Bootloop Issue Due To Flashing A Module, Use The Function To Remove Any Module Manually Which Maybe Caused The Bootloop/Issue (Disabling MagiskCoreOnlyMode & Rebooting The Device Are Required To Load The Modules)
- The Function Disables All Magisk Modules By Enabling MagiskCoreOnlyMode & After Booting, You Can Disable MagiskCoreOnlyMode From The Section Of Settings In Magisk Manager Then Removing/Disabling The Module(s) Which Caused The Bootloop/Issue From The Section Of Modules In Magisk Manager Then Reboot
- CoreOnlyMode Gives The Device The Ability To Get Into The Android Directly With User Interface Which Means The User Can Use The Device With All Features/Functionalities Except Magisk Modules Even Before Removing The Module(s) Which Caused The Bootloop/Issue
- Enabling CoreOnlyMode Keeps MagiskSU, MagiskHide & Systemless Hosts Activated, But No Modules Are Loaded/Enabled
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of MagiskCoreOnlyModeEnabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskCoreOnlyModeEnabler/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
7- Swap Controller (RAM Management)
- Swap Is A Part Of Android RAM Management Which Depends On 2 Important Factors Which Are Swap Space & Swappiness Value
- Swap Is A Virtual Memory Which Allows Physical Memory RAM To Be Extended Using A Portion Of Internal Storage Where Android Moves Inactive Processes/Apps Into Virtual Memory To Make Space For New/Active Ones
- The Function Is Divided Into 2 Sub-Functions [SwapEnabler & SwapDisabler] For Improving Responsiveness/Performance
- SwapEnabler Re-Calculates Swap Space & Sets The New Size But SwapDisabler Sets Swap (Total) Size To Be 0 [It Can Be Checked Using DiskInfo From PlayStore]
- The Default Swappiness Value Is 35 For SwapEnabler & 0 For SwapDisabler
- The Function Disables Also KSM/UKSM For Reducing The Battery Drain & Lowering The CPU Usage
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of SwapEnabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SwapController/Enabler/Inactive And Then Reboot The Device
- For Activating The Functionality Of SwapDisabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SwapController/Disabler/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
8- Swappiness Changer (RAM Management)
- Swap Is A Part Of Android RAM Management Which Depends On 2 Important Factors Which Are Swap Space & Swappiness Value
- Swap Is A Virtual Memory Which Allows Physical Memory RAM To Be Extended Using A Portion Of Internal Storage Where Android Moves Inactive Processes/Apps Into Virtual Memory To Make Space For New/Active Ones
- There Are 3 Levels Of Swappiness Value [Low For 10, Mid For 30 & High For 60] For Improving Responsiveness/Performance [It Can Be Checked Using DiskInfo From PlayStore]
- The Function Disables Also KSM/UKSM For Reducing The Battery Drain & Lowering The CPU Usage
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of Low Swappiness, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SwappinessChanger/Low/Inactive And Then Reboot The Device
- For Activating The Functionality Of Mid Swappiness, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SwappinessChanger/Mid/Inactive And Then Reboot The Device
- For Activating The Functionality Of High Swappiness, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SwappinessChanger/High/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
9- MagiskDaemonHide Keeper (MagiskDaemon-MagiskHide Running Keeper) [For Magisk Users Only]
- The Function Is Divided Into 2 Sub-Functions [HideKeeper & DaemonKeeper] For Keeping Both Of MagiskDaemon & MagiskHide Running (Which Is Recommended To Be Used If Only Needed)
- HideKeeper Aims To Resolve The Issue Of Intermittent Work Of MagiskHide By Re-Enabling MagiskHide Every A Certain Time
- DaemonKeeper Aims To Resolve The Issue Of Losing Root Access Randomly (Or Magisk Is Not Installed) By Re-Starting MagiskDaemon Every A Certain Time
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of HideKeeper, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDaemonHideKeeper/Hide/Inactive And Then Reboot The Device
-----> Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Re-Enabling MagiskHide Every 36 Min. & The Fast Mode Can Be Used Re-Enabling MagiskHide Every 18 Min.]
-----> For Activating The Fast Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDaemonHideKeeper/Hide/Wait/Active And Then Reboot The Device
- For Activating The Functionality Of DaemonKeeper, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDaemonHideKeeper/Daemon/Inactive And Then Reboot The Device
-----> Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Re-Starting MagiskDaemon Every 10 Min. & The Fast Mode Can Be Used Re-Starting MagiskDaemon Every 5 Min.]
-----> For Activating The Fast Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDaemonHideKeeper/Daemon/Wait/Active And Then Reboot The Device
Click to expand...
Click to collapse
10- DT2WStatus Inverter (DoubleTap2Wake Enabler/Disabler)
- Inverting The Default DT2W Status During Startup ([From Disabled To Enabled] Or [From Enabled To Disabled])
- The Function Changes The DT2W Status For The Entirety Of The Device's Uptime Until Next Reboot
- The Default DT2W Status Can Be Either Enabled Or Disabled Which Depends On The Installed/Flashed Rom/Kernel
- The Installed/Flashed Rom/Kernel Must Support The Feature Of DT2W (DoubleTap2Wake)
- Activating The Function = Inverting The Default DT2W Status
- For Activating The Functionality Of DT2WStatusInverter, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/DT2WStatusInverter/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
11- MagiskDeviceSpoofingTool Enabler (Device Emulator For Device Certification & SafetyNet) [For Magisk Users Only]
- Fixing PlayStore Device Certification Status & Passing SafetyNet
- The Function Changes Some Properties Of Build.Prop For The Entirety Of The Device's Uptime Until Next Reboot
- The Function Changes The Device Fingerprint To Another Certified One (Currently Pixel 2 XL)
- MagiskHide Must Be Working Properly Which Is A Main Point To Pass SafetyNet
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of MagiskDeviceSpoofingToolEnabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDeviceSpoofingToolEnabler/Inactive And Then Reboot The Device
- Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Resolving The Issue Of Blackscreen & The Fast Mode Can Be Used For Resolving The Issue Of Non-Persistent After Rebooting]
- For Activating The Fast Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDeviceSpoofingToolEnabler/Wait/Active And Then Reboot The Device
- P.S. The Device's Fingerprint Can Be Checked Using Device Info HW From PlayStore - SafetyNet Can Be Checked Using Either Magisk Manager Itself Or SafetyNet Helper Sample From PlayStore - Root Detection Can Be Checked Using RootBeer Sample From PlayStore
- P.S. Maybe Activating Both Functions Of PlayStoreWithServicesDataCleaner & DalvikCacheCleaner Are Required
- P.S. The Most Famous Reasons Of Root Detection Are Magisk Itself, Installed Rom/Kernel, Loaded Prop, Installed App, File/Folder In The Internal/External Storage & External Connection Thru Internet
Click to expand...
Click to collapse
12- LowRamConfig Enabler (RAM Management)
- Enabling The Low Ram Configurations For Low Ram Device
- The Function Changes The Low Ram Configurations For The Entirety Of The Device's Uptime Until Next Reboot
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of LowRamConfigEnabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/LowRamConfigEnabler/Inactive And Then Reboot The Device
- Some Issues Which Are Related To Rooting-Tool/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Resolving The Issue Of Blackscreen & The Fast Mode Can Be Used For Resolving The Issue Of Non-Persistent After Rebooting]
- For Activating The Fast Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/LowRamConfigEnabler/Wait/Active And Then Reboot The Device
Click to expand...
Click to collapse
13- MagiskModules Disabler [For Magisk Users Only]
- Disabling The Other Magisk Modules
- In-Case Of Facing A Bootloop Issue Due To Flashing A Module, Use The Function To Remove Any Module Manually Which Maybe Caused The Bootloop/Issue
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of MagiskModulesDisabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskModulesDisabler/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
14- MagiskGeneralScripts Disabler [For Magisk Users Only]
- Disabling All Magisk General Scripts Of /data/adb/service.d & /data/adb/post-fs-data.d
- In-Case Of Facing A Bootloop Issue Due To Flashing A Module Or Placing A Script, Use The Function To Remove That Script Manually
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of MagiskGeneralScriptsDisabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskGeneralScriptsDisabler/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
General Info:
- To Disable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Check Box/The True Icon --> Reboot
- To Enable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Uncheck Box --> Reboot
- To Uninstall The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Bin Icon --> Reboot
- To Disable The Module For All Users [Non-Magisk Users & Magisk Users], Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/Status/Active And Then Reboot The Device
- To Enable The Module For All Users [Non-Magisk Users & Magisk Users], Delete The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/Status/Active And Then Reboot The Device
- To Uninstall The Module For All Users [Non-Magisk Users & Magisk Users] (Unity), Re-Flash The Module
>>>Dreamer(3MF)<<<
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
Other Modules
----------------------------------------------------------------------------------------------------------------
MultiFunctionsPlusPage 2 Of 2
Changelog:
v1.0.3.4.2.4B7: Improving The Code & Updating The Function Of [MagiskDeviceSpoofingTool Enabler] To Emulate "Pixel2XL"
v1.0.3.4.2.4B6: Fixing Minors, Improving The Code & Supporting All Magisk Versions From Magisk v8(800) To The Latest Version
v1.0.3.4.2.4B4: Fixing Minors, Improving The Code & Supporting All Magisk Versions From Magisk v13.1(1310) To The Latest Version
v1.0.3.4.2.4B0/2: Improving The Code & Updating To Magisk v20.x
v1.0.3.4.2.4/4A1: Fixing Minors & Improving The Code
v1.0.3.4.2.3L: Improving The Code
v1.0.3.4.2.3F: Improving The Code, Adding The Function Of [MagiskModules Disabler] For Disabling The Other Magisk Modules & The Function Of [MagiskGeneralScripts Disabler] For Disabling The Magisk General Scripts
v1.0.3.4.2.3A/B: Improving The Code, Adding The Function Of [MagiskDeviceSpoofingTool Enabler] For Passing The SafetyNet & The Function Of [LowRamConfig Enabler] For Enabling The Low Ram Configurations
v1.0.3.4.2.2: Initial Release
Click to expand...
Click to collapse
The Description: (2)
*** Re-Flashing The Module Of MultiFunctionsPlus With Keeping The Same Configurations:
- Re-Flash The Module Of MultiFunctionsPlus (Don't Reboot) & Move The Folder Of MultiFunctionsPlus From The Folder Of 4U [/data/DreamerMods/4U/MFP] To The Folder Of DreamerMods (/data/DreamerMods) Then Reboot
Click to expand...
Click to collapse
*** Activator (+Bootloop/Bootscreen/Blackscreen Resolver For Apps, Modules, Scripts & HideList): Activating Some Functions Of MultiFunctionsPlus For Once To Resolve Some Issues (P.S. MultiFunctionsPlus Is Required To Be Flashed Before Using Activator)
- Flash The Module Of MultiFunctionsPlus (Don't Reboot) & Flash The Module Of Activator (Reboot Now) For Activating Some Functions [DalvikCache Cleaner, MagiskHideList Cleaner, SafeMode Enabler, MagiskCoreOnlyMode Enabler, MagiskModules Disabler & MagiskGeneralScripts Disabler] For Once To Resolve Some Issues
- Booting The Android Into SafeMode For Giving The Ability To Remove Any App/Its Data Manually Which Maybe Caused The Bootloop/Issue (Rebooting The Device Manually Is Required To Get Back To The NormalMode)
- Clearing DalvikCache For Removing All Remnants Of The Uninstalled Apps & Resolving/Fixing Some Issues With The Installed Apps
- Clearing All Apps/Activities/Processes From MagiskHideList Which Maybe Caused The Bootloop/Issue [For Magisk Users Only]
- Disabling The Other Magisk Modules Which Maybe Caused The Bootloop/Issue [For Magisk Users Only]
- Disabling All Magisk General Scripts Which Maybe Caused The Bootloop/Issue [For Magisk Users Only]
- Opening Magisk In CoreOnlyMode To Deactivate All Modules For Giving The Ability To Remove Any Module Manually Which Maybe Caused The Bootloop/Issue (Disabling MagiskCoreOnlyMode & Rebooting The Device Are Required To Load The Modules) [For Magisk Users Only]
- Flashing/Re-Flashing The Module Of Activator Will Activate The Above Mentioned Functions (Even-If Magisk Is In Core Only Mode For Magisk Users)
Click to expand...
Click to collapse
*** Execution Mode: The Execution Mode Of Script/Module
- There Are 2 Modes [Execution In Normal Mode & Execution In Background Mode]
- Execution In Normal Mode: Executing The Script/Module Based On The Priorities Of Rooting-Tool/Rom/Kernel Itself Is Maybe A Proper Mode For Some Cases
- Execution In Background Mode (The Default One): Resolving The Issue Of Blocking The Other Scripts/Modules From Starting Early Due To The Execution Time Of Code Is Long & Also Related To Rooting-Tool/Rom/Kernel Itself (Such Losing The Functionality Of Xposed After Installing The Module Or Activating Any Function)
- For Activating Execution In Normal Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/Status/Background/Active And Then Reboot The Device
- For Activating Mode Of Execution In Background Mode, Delete The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/Status/Background/Active And Then Reboot The Device
Click to expand...
Click to collapse
*** FAQ/Notes:
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring Apps, Modules, Scripts Or HideList, Check Activator (+Bootloop/Bootscreen/Blackscreen Resolver For Apps, Modules & HideList) In Above
- After Flashing The Module Of Activator, MagiskHideList Will Be Cleared And For Retrieving/Restoring The Last MagiskHideList, Check The Function Of MagiskHideList Cleaner In Above
- All Functions Are Deactivated/Disabled By Default And The Needing To Activate Each Wanted Function Is Described In Above
- In Case Of Deleting The Folder Of Any Unwanted Function Such SELinuxModeInverter (/data/DreamerMods/MultiFunctionsPlus/SELinuxModeInverter) & Rebooting The Device, The Code Will Not Check The Unwanted Function Which Is Equivalent To The Permanent Deactivation/Removal Of The Unwanted Function So The Same Step Can Be Done With Any Unwanted Function (P.S. For Retrieving/Restoring The Unwanted Function, Deleting The Folder Of Status & Rebooting The Device Are Required)
- P.S. Deleting The Folder Of Status (/data/DreamerMods/MultiFunctionsPlus/Status) & Rebooting The Device Will Create The File Of Disable Again
- For Activating Any Function, Copying The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/<TheFunction>/Inactive (P.S. Negating The Negation Is A Form Of Affirmation) & Rebooting The Device Are Required
- Disable MagiskCoreOnlyMode From The Section Of Settings In Magisk Manager Which Is Required As An Essential Step To Activate Any Function (Disabling MagiskCoreOnlyMode & Rebooting The Device Are Required To Load The Modules)
- For Re-Flashing The Module Of MultiFunctionsPlus With Keeping The Same Configurations, Check The Details In Above
Click to expand...
Click to collapse
*** In-Case Of Failure: After Doing Successfully The Above Mentioned Steps
- During The Installation Process, Take The Screenshot After Flashing The Module & Send It
- Send These Logs (/data/MultiFunctionsPlus.log, /data/DreamerMods/MultiFunctionsPlus/Log/MultiFunctionsPlus.log, /data/DreamerMods/MultiFunctionsPlus/Log/MultiFunctionsPlusData.log & /data/DreamerMods/MultiFunctionsPlus/Log/MultiFunctionsPlusOld.log)
- Complete Info About The Device, The Used Rom, The Used Kernel & The Used Rooting-Tool
- Send The Folder Of DreamerMods (/data/DreamerMods)
- Send The Screenshots Of (Magisk Manager --> Main Screen, Magisk Manager --> Modules, Magisk Manager --> SuperUser & Magisk Manager --> Log --> SuperUser) [For Magisk Users Only]
- Send Magisk Log (Magisk Manager --> Log --> Magisk) [For Magisk Users Only]
- Send The Screenshot Of SuperUser Of The Used Rooting-Tool [For Non-Magisk Users]
- Send Full Logcat (Using Logcat Extreme From PlayStore)
Click to expand...
Click to collapse
>>>Dreamer(3MF)<<<
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
Other Modules
----------------------------------------------------------------------------------------------------------------
Reserved For News/Updates #0
Reserved For News/Updates #1
Reserved For News/Updates #2
Waiting for upload, don't see them yet.
Sent from my SM-N910F using Tapatalk
u81 said:
Waiting for upload, don't see them yet.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
Could I Ask You To Send The Screenshots Of The Following?
-Settings --> Apps --> Instagram --> Storage
-Settings --> Apps --> WhatsApp --> Storage
-Settings --> Apps --> Messenger --> Storage
-Settings --> Apps --> SoundCloud --> Storage
u81 said:
Waiting for upload, don't see them yet.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
Check This Post https://forum.xda-developers.com/ap...al-media-cache-advanced-t3799155/post76705484.
Don't have sound cloud
{
"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"
}
YouTube attached as well
Sent from my SM-N910F using Tapatalk
YouTube screenshot
Sent from my SM-N910F using Tapatalk
I'm only updated to Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify a few hours ago so the current storage usage is possibly much smaller than normal. (Data not wiped)
It should be up to normal size by tomorrow, I'd say.
Sent from my SM-N910F using Tapatalk
u81 said:
I'm only updated to Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify a few hours ago so the current storage usage is possibly much smaller than normal. (Data not wiped)
It should be up to normal size by tomorrow, I'd say.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
Kindly Send Also A Screenshot Of Your Internal Storage (Unhide Option Should Be Selected)
Is this what you're looking for?
Sent using Tapatalk
Samsung Note4 - SM-910F - Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify
Motorola G5S+ - Stock
u81 said:
Is this what you're looking for?View attachment 4517147
Sent using Tapatalk
Samsung Note4 - SM-910F - Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify
Motorola G5S+ - Stock
Click to expand...
Click to collapse
No, From Your File Browser.
Is this what you're looking for?
If not, please share your screenshot and I'll find how to get that screenshot from my phone
Sent using Tapatalk
Samsung Note4 - SM-910F - Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify
Motorola G5S+ - Stock
Deleted
Will these do?
Sent using Tapatalk
Samsung Note4 - SM-910F - Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify
Motorola G5S+ - Stock
I was thinking about one thing related to your modules. They're useful, but it'll be kinda messy sometime, since you're creating a lot of different modules, separately.
Since all of them have similar purposes (clear caches from something), how about you merge all of them into a single module, with an interactive terminal interface? I guess it'd be a great update, and not only easier to you to maintain and organize all of those modules, but easier to others to find them and use. Just a quick thought.
abacate123 said:
I was thinking about one thing related to your modules. They're useful, but it'll be kinda messy sometime, since you're creating a lot of different modules, separately.
Since all of them have similar purposes (clear caches from something), how about you merge all of them into a single module, with an interactive terminal interface? I guess it'd be a great update, and not only easier to you to maintain and organize all of those modules, but easier to others to find them and use. Just a quick thought.
Click to expand...
Click to collapse
Currently There Are 8 Modules [WiFi Connection State On Status Bar - App Shortcut & Widget In Notification Area - SELinux Mode Inverter (Advanced SELinux Mode Changer) - Microsoft Intune Company Portal Hider - Tez Hider - Clear Dalvik Cache (Advanced Dalvik/ART Cache Cleaner) - Clear Google PlayStore With Services Data (Advanced PS-GMS Data Cleaner) - Clear Social Media Cache (Advanced Social Media Apps Cache Cleaner)] So What Do You Think?
Dreamer(3MF) said:
Currently There Are 8 Modules [WiFi Connection State On Status Bar - App Shortcut & Widget In Notification Area - SELinux Mode Inverter (Advanced SELinux Mode Changer) - Microsoft Intune Company Portal Hider - Tez Hider - Clear Dalvik Cache (Advanced Dalvik/ART Cache Cleaner) - Clear Google PlayStore With Services Data (Advanced PS-GMS Data Cleaner) - Clear Social Media Cache (Advanced Social Media Apps Cache Cleaner)] So What Do You Think?
Click to expand...
Click to collapse
Nice, but I was talking specifically about these cache related modules, not the others, I forgot to mention that. Merging them into a single module seems to be a nice idea. But well, just a thought as I said.