yashsingh1/xdaforums huggingface dataset:
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] The Hard Gamer:
ScreEnies here

https://s14.postimg.org/rkmo66ult/Screenshot_20170223_164513.png
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] The Hard Gamer:
First OTA on monday
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] ananwoy:
why android 6 bro?
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] The Hard Gamer:
Basically this ui idea came suddenly to me

And I wanted users to have full control over the system which only xposed can give

So we will move to Nougat when xposed is released for it
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] ananwoy:
Thanks bro.....can u please mention the specialities of this rom?
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] The Hard Gamer:
Its full of surprises
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] mayu19:
The UI name itself says it....but it is still in development stages
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] The Hard Gamer:
YYeah but its quite stable than N
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] mayu19:
Yes bro no doubt....I'll recommend this ROM for MM
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] ananwoy:
Need to flash custom kernel?
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] mayu19:
Flash semar r5 for best battery backup
[Galaxy S6 Edge Q&A, Help & Troubleshooting] SamiRobo:
i want to ask a question that is there any way to prevent airplane mode being turned on or off while screen is lock (with fingerprints, pin or password) on galaxy s6 edge (android 6)?:confused:
[Samsung Galaxy J5 Questions & Answers] claytoncamilleri100:
Hi I have the Samsung Galaxy J5 2015 Model and I am having trouble with the front facing camera. I shows an orange tin on the camera. I am on stock rom with root. Has any one else have this problem?
[Samsung Galaxy J5 Questions & Answers] Amarius1:
Maybe you have the sepia effect enabled in camera effects?
[Samsung Galaxy J5 Questions & Answers] claytoncamilleri100:
no all the effects are off and I also tried to reset the settings with no luck.
[Samsung Galaxy J5 Questions & Answers] Amarius1:
Also tried dling a factory reset and firmware reflash? If they don't work either it means the issue is hardware-wise
[Smart Unlock] angrei:
The app does not work. xiaomi mi4s. Added WiFi network. Lock also works. Sorry of English. I use a translator.
[Galaxy Tab S Q&A, Help & Troubleshooting] Govermans:
Hi all,

Recently I discovered my SM-T800 is charging really slow. This happened after my wife was watching Netflix (with a Chromecast) on it. The app crashed (tablet could not be switched off) and was drained completely. Since then the SM-T800 charges really, really slow…

And when I talk of really slow, I mean: really slow. Like more than two days (!) to charge from (almost) zero to 100%. It does not matter if tablet is in standby (on airplane mode) or switched off completely… When I turn the tablet on, it discharges, even when connected to the original adapter. I have tried several devices on the adapter and cables: they all charge flawless (no adapter/cable issue). I also tried another adapter, which did not make a difference.

Does this mean I need to replace the battery now? Because I can hardly use my tablet normally now…

Many thanks for any thoughts, solutions, etc. :)
[Galaxy Tab S Q&A, Help & Troubleshooting] htrex:
At first, try to charge using another cable and charger. Some cables wear over time and che charging speed can be severely affected.
[Galaxy Tab S Q&A, Help & Troubleshooting] Govermans:
I tried it and it seems to work! Thanks!!
[Galaxy Tab S Q&A, Help & Troubleshooting] saywhat1001:
How hard is it to change the tab S battery
[Galaxy Tab S Q&A, Help & Troubleshooting] Amplificator:
It's pretty easy: https://www.youtube.com/watch?v=VnUEMyDs27I
[Galaxy Tab S Q&A, Help & Troubleshooting] wormwod1027:
If you open the tablet up check to see if the wires coming off the battery itself are fully inserted into the plastic female connector that makes the connection to the tablet itself. You should not see any of the metal adapters crimped onto the wire ends. I had one of them partially visible and it was causing problems that ranged from slow charging to sudden battery level swings. The tablet would glitch to the point of unusable with 80% battery left. If I plugged it in I could use it, but what good is a tablet you have to keep plugged in. I reinserted that one wire fully into the plastic connector and haven't had any issues since. I'll keep my fingers crossed that it'll be that simple for you, but if it isn't no worries. The batteries are inexpensive and the tablet comes apart fairly easily.
[Xiaomi Redmi Pro Questions & Answers] tmdheman:
Guys I use china stable rom in my redmi pro. I bought iit recently.I didn't find any update in my xiaomi redmi pro.I got battery problem also! It is too much lower performance for a 4050mah battery! Hope the next update will solve the problem! If there are any solution of this battery problem manually please suggest me.

Thank u☺
[Xiaomi Redmi Pro Questions & Answers] tafkab60:
Hello !

Rom Updates normallyx do not soplve Battery problems.

Search for the Battery Suckers normally do.

Get Battery Stats , or something similar.
[Samsung Gear S3] jamesearl_chua:
I just got my Gear S3 today and am wondering if there is a way to hide the message preview on messages? I just want it to notify me if I have new messages but I don't want it showing the content.
[Samsung Gear S3] spegma:
u just need to configure ur notificTion of ur messGes, viber, messnger, wechT, etc.
[Android Q&A, Help & Troubleshooting] Bre4kd4nce:
Hi Folks,

i bought a Mobile on the bay and unveild now that it is a fake. The guy refuses to take it back, so i'll stay on it... :crying: Now i'm trying to do the best of it. It seams to show fake Memory specs, 32 GB Storage and 4 GB RAM, i don't know if the specs from CPUZ are correct because it shows only 1 GB Storage what is definitely not right.

The worst Thing is that the network Bar only shows EDGE Connection(doubt this Mobile connects 4G, at least maybe 3G) and i can't add my provider to the Network list. Now i consider to flash a custom ROM, what i allready made with my other Samsung mobiles. Bu i can't find very much about this device on the web.

May some one can give me Advices? Thanks!

[IMG="Factory mode"]https://s1.postimg.org/gaudoru0f/IMG_20170221_171627.jpg[/IMG]

[IMG="Device Info"]https://s11.postimg.org/zftt7g5g3/IMG_20170223_114004.jpg[/IMG]

[IMG="CPU-Z SOC"]https://s11.postimg.org/5cjvt8rkj/IMG_20170223_114039.jpg[/IMG]

[IMG="CPU-Z Device"]https://s11.postimg.org/m1lbp5o5v/IMG_20170223_114054.jpg[/IMG]

[IMG="CPU-Z System"]https://s11.postimg.org/w06abmxlf/IMG_20170223_114109.jpg[/IMG]
[Magisk] Didgeridoohan:
This thread/guide is now closed and will no longer be updated. It is only kept for posterity.

The new guide is stickied at the top of the Magisk forum, right here.
[Magisk] Didgeridoohan:
Changelog

Installing Magisk and Modules - Changelog

2017-07-21

Tasker v5.0 is released. Update "Tasker and MagiskSU" to reflect this.

2017-07-19

Added some links to the Manager apk downloads on GitHub.

Updated and moved "Magisk Manager crashes".

Updated "Module causing issues".

Updated "Nothing works!".

2017-07-17

Slight update to "Boot image patched by other programs".

2017-07-14

Added a new section, "Moving from another systemless root solution to MagiskSU".

Added a new section, "Can't install modules".

Added a new section, "Apps are force closing".

2017-07-13

Added a note about using themes with the Manager under "Magisk Manager is crashing".

2017-07-12

Updated "Boot image patched by other programs".

Added a section about "Long boot time".

Added a section about "Magisk Manager crashes".

2017-07-11

Updated for Magisk v13.1

2017-06-19

Updated info about beta releases.

2017-06-18

Moved "Outdated tips and tricks" to it's own post.

2017-05-25

Some clarifications for SuperSU pre-patched boot image.

2017-05-08

Added "Magisk but no MagiskSU"

Added a link to the solution for no MagiskSU on Sony devices by [MENTION=3246955]Tobi@s[/MENTION].

2017-05-06

Added some clarifying headings.

Added an index in the OP.

2017-05-01

Slight clarification under "Asking for help".

2017-04-19

Added "Starting fresh".

2017-04-14

Added a link to a Magisk module for Tasker compatibility with MagiskSU.

2017-04-09

Updated "Losing root".

2017-04-04

Added "There are no modules".

2017-03-31

Updated for Magisk v12.

Moved old and outdated tips and tricks to the bottom.

2017-03-28

Minor clarification on Module issues.

Updated link to new Modules Collection thread.

2017-03-21

Added information about updating.

Slight restructuring.

2017-03-20

Updated for Magisk v11.6

2017-03-14

Added a link to the Beta snapshot thread.

2017-03-05

Added more ways to make Tasker recognise root with MagiskSU.

2017-03-02

Changelog started.

Refinements.

2017-02-23 - 2017-03-02

Various additions.

Refinements.

2017-02-23

Initial post.
[Magisk] Didgeridoohan:
Old and outdated tips and tricks for "Installing Magisk and Modules"

Unmounting of folders is no longer showed in the Magisk log, since Magisk v13.1.

MagiskHide isn't unmounting folders as it should

If MagiskHide isn't unmounting as it chould for the processes/packages added to the Hide list (there are no "hide_daemon: Unmounted" entries in the log or there are entries showing that the unmount failed ("hide_daemon: Unmount Failed")), see "MagiskHide isn't unmounting folders as it should" below.

If you don't see any entries in the Magisk log for "hide_daemon: Unmounted", MagiskHide isn't functioning as it should and can't hide Magisk from apps and processes that trigger if root is found. There are a few reasons as to why this might happen. See "Kernel logcat support", "Logger buffer size", and "Mount namespace issues" below. Of course, these might not be the only reasons. If you're lucky, one of the solutions below will work for your particular case.

If there are entries in the Magisk log showing that the unmount failed ("hide_daemon: Unmount Failed"), take a look at what folder it's failing for and disable the corresponding Magisk module. If you can't work out what module is causing the issue, disable them all and enable one by one until you find the culprit. If it is one of your installed modules causing the issue, ask for advice in the module's support thread.

It might be that you have to rely on manually starting MagiskHide to make it unmount folders properly (known: some Xiaomi devices/MIUI). See "Starting MagiskHide manually" above.

Busybox is no longer bundled with Magisk since v13.1.

Randomly losing root

Some devices and/or ROMs (known: Lineage OS) have issues with losing root when using MagiskSU. This can sometimes be fixed by disabling busybox in Magisk Manager settings. Some users have also reported success by disabling systemless hosts instead/as well.

Magisk v13+ is fully compatible with stock Sony ROMs.

Sony and MagiskSU

If you're using a Sony device and have the above issue with MagiskSU, you're probably running a stock boot image or otherwise haven't disabled Sony RIC. Don't worry, [MENTION=3246955]Tobi@s[/MENTION] have got the fix for you here.
[Magisk] laggardkernel:
Check the module support thread for update.

Update 20170228

Since a little syntax error in the mounting script from Magisk v11.0-v11.1, mounting link systemless-ly won't success. Hence we choose copy but not to link the su binary for v11.0-v11.1. Don't worry, both methods are systemless.

==========

Great guide. :good:

Just made a simple module try to solve the /sbin/su not detectable problem. This module will look for existing su binary, and create a link as /magisk/su_xbin_bind/system/xbin/su pointing to the real su. The link will also be mounted as /system/xbin/su systemless-ly later.

Installation

Flash it in RECOVERY, then reboot. And you will find a link /system/xbin/su. All the work is done systemless-ly.

Uninstallation

Open Magisk Manager, go to Modules, disable or uninstall the module called "Su xbin_bind". Then it will disappear after reboot.
[Magisk] Didgeridoohan:
Nice! I added a mention of this in the guide. You should get this in the repo...
[Magisk] iubjaved:
Great guide. Apparently this contains almost all the troubleshoot steps and known issues right from the original support thread of Magisk. However it would be complete if you had added the steps that user reported working on various custom roms that are known to not pass safetynet. One of the step is below for pre rooted custom roms :

1. Go back to recovery.

2. Flash unSU.zip by osmosis

3. Flash magisk 10.2

4. Boot to system. Install Phh superuser. Update binary.

5. Update to latest magisk from magist manager. Reboot.

6. Check safetynet, it should work.

This is reported to be working for some user, and some other reported it didn't work. But still worth a try.
[Magisk] Didgeridoohan:
I hadn't seen that one before. Looks a little fishy (updating the phh's superuser binary?), but I'll do some research on that and see if I can work this into the guide somehow.
[Magisk] GuestK0087:
2 posts removed.

Do not discuss or post warez on XDA.

Thank you.

:good:
[Magisk] clodoux:
Sorry
[Magisk] iubjaved:
These steps are from the Magisk thread, i could be wrong about binary update ( considering when installing any superuser, you will get prompt for updating binary?) but rest of the steps are exactly as it was mentioned there. I wish i could link you for reference but i have to go through the whole thread again and search for these . You can post these steps on the magisk support thread for clarification. Great work once again. Good luck!
[Magisk] Xennet:
Hey installed ur module, but still root checker detects no su file symlinks in xbin :crying:
[Magisk] laggardkernel:
Did you reboot your phone after installation? And try to check its existence in /magisk/su_xbin_bind/system/xbin. If the su link exists here, where does it point to?
[Magisk] Xennet:
Yes rebooted. It is activated in magisk. The su link exists in /magisk/su_xbin_bind/system/xbin/. Opening t link directs to su...But how to check it where it directs to..

Really dis is a great module to get t apps dat look for real root location xbin/su...

Please help
[Magisk] laggardkernel:
How about /magisk/su_xbin_bind/auto_mount, does it exist? If not, create an empty file and name it as auto_moint.
[Magisk] Xennet:
auto_mount exists too :rolleyes:
[Magisk] laggardkernel:
Now, I need more detail to figure it out.

1. Where does the su link point to? Does it exist in /system/xbin and /dev/magisk/dummy/system/xbin. Use a explore to check su's position and the Link's property, or use a terminal

su
ls -al /magisk/su_xbin_bind/system/xbin/su

2. What is the version of your magisk? Upload your /cache/magisk.log and /sbin_orig/magisk_mask.sh for me, please.

3. Which ROM are you using and is there any root imbedded?

I'm using an op3 with OOS 3.2.7, Magisk v11.1, and the su_xbin_bind module works well now. It seems you're using an op3 or op3t. So it's weird for me the module don't work on your device.

Much obliged if you could tell me the package name of the root checker app in your picture.
[Magisk] fliptechnologies:
for anyone with a international S7 running stock 7.0 , who all of a sudden lost safety net passing like i did last night,

all you need to do is switch to core-only mode and reboot, and you will pass safety net again.
[Magisk] Didgeridoohan:
That's not limited to any specific device. Since the last SafetyNet update, any device using Magisk v12 have to do this to pass SafetyNet. That, update to v13.0 (still in beta) or use the Universal SafetyNet fix module (link found in the guide).
[Magisk] deathult:
I flashed Magisk v12 on my M2 Note running Lineage OS 14.1 . The manager app says that Magisk is installed but it also says the device is not rooted. Is there something I can do or do I have to use SuperSU? Thanks in advance.
[Magisk] Didgeridoohan:
Jeez... Does anyone read the OP anymore?
[Magisk] noobsgs2:
Any idea why Magisk Hide doesn't work? I'm on Magisk 13.0(54e6a79)

I( 216: 244) proc_monitor: it.archie.ccbcarteprepagate (PID=18310 ns=mnt:[4026543517])
D( 216: 244) proc_monitor: hide daemon response code: 0
I( 216:18363) * Stopping MagiskHide
D( 216:18363) resetprop: setprop [persist.magisk.hide]: [0] by property_service
D( 216: 244) proc_monitor: running cleanup
D( 245: 245) hide_daemon: received termination request
D( 216: 244) proc_monitor: terminating...
I( 216:18366) * Starting MagiskHide
D( 216:18366) resetprop: setprop [persist.magisk.hide]: [1] by property_service
I( 216:18366) hide_pre_proc: Hiding sensitive props
D( 216:18366) resetprop: prop [ro.boot.verifiedbootstate] does not exist
D( 216:18366) resetprop: prop [ro.boot.flash.locked] does not exist
D( 216:18366) resetprop: prop [ro.boot.veritymode] does not exist
D( 216:18366) resetprop: prop [ro.boot.warranty_bit] does not exist
D( 216:18366) resetprop: prop [ro.warranty_bit] does not exist
D( 216:18366) resetprop: getprop [ro.debuggable]: [0]
D( 216:18366) resetprop: getprop [ro.secure]: [1]
D( 216:18366) hide_list: initialize...
I( 216:18366) hide_list: [com.google.android.gms.unstable]
I( 216:18366) hide_list: [it.phoenixspa.inbank]
I( 216:18366) hide_list: [it.archie.ccbcarteprepagate]
I( 216:18366) proc_monitor: init ns=mnt:[4026531840]
I( 216:18366) proc_monitor: zygote ns=mnt:[4026543387]
I( 216:18366) proc_monitor: it.archie.ccbcarteprepagate (PID=18387 ns=mnt:[4026543485])
D( 216:18366) proc_monitor: hide daemon response code: 0
[Magisk] Didgeridoohan:
Take a look at the last 6-7 posts...

Oh!

And read the OP.
[Magisk] Zackptg5:
Whats an OP? Lol :eek:
[Magisk] Didgeridoohan:
The guide's been updated for Magisk v13.1. There might be more to add once the official documentation is updated.
[Magisk] adrenochrome25:
v12 was ok (root&MagiskHide)

v13beta was only ok for root (MagiskHide never worked)

v13.1 get stuck on boot logo : adb report no root available, there's no /data/magisk_debug.log available in twrp filemanager

if there is any other file i can provide for investigation, just ask
[Magisk] Didgeridoohan:
Wrong place. You wan't the support thread.
[Magisk] Spikestrip:
Android Pay updated to version 4.0 today. Magisk v13.1 is still hiding my root from it and allowing me to pay using my phone. Just wanted people to know it's safe to update Android Pay if you use it.
[Magisk] hgoldner:
Yup, working here, too, on a Verizon HTC 10, S-OFF, bootloader unlocked and stock, but running latest Magisk.
[Magisk] dollarbr:
Everything working fine with Magisk v13.1 in a Moto X Style (brazilian "Pure"), hide everything and allowing me to use Netflix as usual =P
[Magisk] HannibalIII:
Hi,

I recently changed my phone frome oneplus 1 to oneplus 5 and I have a problem with one app although magisk hide is activated... It's McDonald's belgium app.

It detects the root...

I didn't had this issue on the oneplus 1

Any clue?

Regards
[Magisk] Didgeridoohan:
Read through post #4 in this thread and see if anything's applicable there. If you need further help there's a section at the bottom ("Asking for help") with tips on how to go about that.
[Magisk] cmstlist:
Yupyup all this. Had to toggle to get it showing SafetyNet passed again.

Also - I had an older 4.x version of Magisk Manager installed on my phone. It installed the 13.1 zip correctly but did not also upgrade the apk and then showed no root after. Installing the APK upgrade from XDA fixed that.
[Magisk] Juls317:
So when I tried to update to 13.1, it basically didn't do anything from what I could tell. Finally got it to update, then lost root. Now I can't get root to stick again. Am I just looking at a position where I have to go from the bottom up and reflash the ROM, kernel, etc.?
[Magisk] HannibalIII:
I didn't found anything so I took the logs and DL it on my Google drive.

I had to togfle magisk as always and safety net is working

There a lot of unstable in the logs compared to the one I see in the post

https://drive.google.com/file/d/0ByGIZS0nyprILW9oS3JrV2FqT0E/view?usp=drivesdk
[Magisk] Didgeridoohan:
Too bad nothing worked. You clearly didn't read the "Asking for help" section properly though... I'll paste it here for you:

(You're asking for support in the wrong thread...)
[Magisk] HannibalIII:
You're right I've been a little fast because of the hurry I'm in for work...

Sorry for that
[Magisk] zakaria12:
i get problem with install magisk modules i get installation error :/
[Magisk] Istvan_86:
Hello,

First of all thanks for all your efforts in Magisk development and Magisk support.

I´m using Magisk in my Pixel C, my OnePlus One and OnePlus 3T. I start using it in v 10.X and lately I was using beta 13 on all devices without problems. When 13.1 was launched I update Magisk on all my devices but on my Pixel C I can´t flash it because of Error: 1. If I flash latest beta zip I don´t have any problems flashing it.

I try all the steps in this thread that I´m able to understand and still Error: 1 also I only find 1 post talking about Error: 1 and it hasn´t enough info to solve my problem.....

What kind of log or whatever must I attach in order to get some help? :D :D :D

Thanks in advance.
[Magisk] Didgeridoohan:
Error 1 can mean many things, you'll have to read the output in TWRP from the flash or read the log to know what it's about. Whenever you have issues while flashing it's the recovery log you need to provide (in TWRP got to Advance - Copy log).

But, in your case you won't need to since there's a bug in v13.1 for the Pixel C. It's been fixed already and will be in the next release. Meanwhile you can try out the latest unofficial snapshot, it has those fixes and should work.

If you continue to have issues I'd like to ask you to post in the support thread since I try to keep this thread clear of support questions. Happy flashing!
[Magisk] Didgeridoohan:
C'mon guys! At least read the OP... Take support questions to the support thread.
[Magisk] Istvan_86:
Really thanks for your fast answer and sorry for posting here, usually I don´t made these errors when I post.

When I arrive home I try the latest snapshot and post the results in the proper thread.

Thanks again.
[Magisk] Didgeridoohan:
I made a new section in post #2, just for you. It's called "Can't install modules".
[Magisk] reddevil08:
[MENTION=4667597]Didgeridoohan[/MENTION]

v1.02 of magisk module to fix TaskerRoot does not work.

v1.01 works fine.

Could you please check your v1.02.zip as v1.01 will stop working after the next magisk update.

I'm using Magisk 13.2 with OOS Beta 10 on OnePlus 3T.

Thanks a lot for making this module.
[Magisk] digitman xxx:
Guys, i try a lot to Unroot my Preroted RR rom 6.0.1 as i have no alternative rom to my device yet. in order to get Magisk(Systemless) with osm0sis Script https://xdaforums.com/showpost.php?p=63615067

then try to extract boot.img from Rom zip and reflash it. it seems to success to unroot and already flash Magisk and yup got Magisk Manager on App drawer also can give apps root access by magisk. but Magisk itself and rom setting force closed everytime try open them So do u have an idea about why this happened or if i miss something here.?

using Latest Magisk 13.2

RR 6.0.1 rom

SM-G7102

Edit: it's only apps preloaded in rom that got root access and working fine eg.(kernel aditure) but for those i setup got force closed..! what does it mean..!??
[Magisk] Didgeridoohan:
Thanks for the heads up! Fixed... Download again.

(I forgot to copy the script to the new zip :laugh:)

You're in the wrong place. Go to the support thread.

You're in the wrong place. Go to the support thread.
[Magisk] pizza_pablo:
With over a thousands posts under your belt I think you are being facetious, but just in case...

"OP" means ORIGINAL POST (the first post in a thread) or ORIGINAL POSTER (the person that wrote the first post in a thread), depending on context used.
[Magisk] Zackptg5:
100% facetious. You'd think people would know considering that's been the response for the past several pages of this thread
[Magisk] pizza_pablo:
I figured, but couldn't resist. The emoticon you used looked befuddled. :cyclops:
[Magisk] Didgeridoohan:
Of the 200-some replies in this thread your "What's an OP" is my clear favourite. :laugh: