TOOLS REQUIRED:
ODIN to flash the firmware
MAGISK MANAGER to patch firmware
LUCKY PATCHER for Good lock
INTRO:
Hey guys after a lot of experimenting, I was able to root but every time it had some problems like no fingerprint, not able to log in to Samsung account, not able to set secure lock screen (pattern, fingerprint, pin) at all.
But this time I am able to root with no problem whatsoever.
THE REAL REASON WHY YOU'RE HERE:
All you do have to do is patch AP of firmware from magisk and then flash it from Odin.
⦁ Firstly enable developer options by tapping 7 on build number.
For that:
About Phone --- Software Information ---- tap Build number 7 times.
⦁ Enable oem unlocking which is in Developer Option.
Settings---- scroll down all the way --- Developer Options---turn on OEM unlocking
⦁ Then download the firmware file
( suggestion right here from XDA http://shorturl.at/tACU6 )
CAUTION: It's an Indian firmware make sure your LTE band is supported or
Google like this: Model number with firmware attached. Ex: SM-205G firmware download)
⦁ Extract the file wherever you like.
⦁ Open the folder you extracted files and copy the AP file (AP in filename) to your device.
HOW TO PATCH AP:
⦁ Install Magisk Manager in non-rooted phone.
⦁ Open it
and look around until you see Magisk and Magisk Manager.
⦁ Press Install of Magisk (not Magisk Manager)
⦁ Click Install in the next set of options
⦁ Now chose the option "Select and Patch a file"
⦁ Then, locate the AP from your device which means select the file and press open.
⦁ Magisk does its magic and when it finishes,
the required file is named as Magisk_patched.tar in the downloads folder.
Copy it to your PC
⦁ Download Odin if you haven't and open it.
⦁ Click on AP and locate the Magisk_patched.tar, from wherever you had copied it to.
⦁ Now, let Odin do its job. Phone reboots and you set up your device.
⦁ Boom you are good to go. You might need to manually install Magisk Manager Apk.
PRECAUTION: DO NOT flash TWRP, it complicates things.
Update: Been using the device for quite a while now and am yet encounter any problems.
Update 2: Finally got good lock modules working.
Update 3: Nah nah nah no problems yet.
HOW TO USE GOOD LOCK APPS?
Intro:
You might be definitely aware that those apps are not available at Galaxy Store for every country, so you better use Nice Lock (which is found on XDA) along with its downloader companion app. Make sure to help the developer either by in app purchase or rating on Play Store.
⦁ Install Nice lock from Play Store.
⦁ Download and install Lucky Patcher.
BE AWARE OF MALWARES. DONOT DOWNLOAD FROM ****TY WEBSITES.
⦁ I am assuming that you're here you're rooted if not see above guide.
Open lucky Patcher
⦁ Click on "Toolbox"
and then on "Patch to android".
⦁ Click on the third option and press apply. Wait for a while device reboots.
(If you want, repeat the process for 1 and 2 as well.
You can't do all at once but 1 and 2 can be done at once)
⦁ Install the applications from the link below and boom you're good to go.
Link:https://mega.nz/#!3p1XhC7R!ZIsiJLjJS5g6jT7xaP6gkWgcE0hCRa6vTeVFIj0bvHM
Update: Valid for android 10 as well.
Disclaimers : Try it with this in your mind that I'm not responsible if you damage your device and you'll be tripping your knox security which cannot be repaired. That means even if you unroot your device, knox is gone and will never be back.
Will this work on the latest android pie?
Hieuvo said:
Will this work on the latest android pie?
Click to expand...
Click to collapse
It does magnificently. Normal ( flash TWRP and install magisk zip) works well for oreo firmware.
Rooted.ndroid said:
It does magnificently. Normal ( flash TWRP and install magisk zip) works well for oreo firmware.
Click to expand...
Click to collapse
Just tried. Does not work if i chose HOME_CSC, i dont wanna lose my stuff tho.
Hieuvo said:
Just tried. Does not work if i chose HOME_CSC, i dont wanna lose my stuff tho.
Click to expand...
Click to collapse
Just do AP only. Inform me about what happened.
Thank You for trying it out.
Rooted.ndroid said:
Just do AP only. Inform me about what happened.
Thank You for trying it out.
Click to expand...
Click to collapse
Will this delete my data?
Please share more details!
Hi! I am stuck as there is no TWRP for Samsung M20 running on Pie (Andrd. 9)
I went through flashing TWRP that's been shared over most pages over the internet.
It did flash, no failures, but still has the same old stock recovery.
But status on the phone says ''Custom''....besides, I cannot get Super SU to work either, as it says root not detected.
The agenda was to install a custom ROM, now I am stuck getting mu phone rooted.
If you've been able to manage, can you please share step by step instructions, with links to the various downloads you did.
Thanks!
Rooted.ndroid said:
Hey guys after experimenting from day one I was able to root I but this time I have no problems of fingerprint reader, Samsung account or anything whatsoever.
All you do have to do is patch AP of firmware from magisk and then flash it from Odin.
How to patch the AP
Install Magisk Manager in non-rooted phone,open it and select install in Magisk --- two option appear -- download zip and patch something , selected the patching one--- locate the AP of firmware from your device then Magisk does its magic.
Finally flash the AP from Odin.
DONOT flash TWRP, it complicates things. Just boot into system after flashing the AP.
Boom you are good to go. You might need to manually install Magisk Manager Apk.
Update: Been using the device for quite awhile now and am yet encounter any problems.
Update 2: Finally got good lock modules working.
Click to expand...
Click to collapse
Hi! Can you please share the exact steps and apps/tools/softwares you used?
I've almost rooted, but not quite there yet and had to turn back.
Thanks!
Rooted.ndroid said:
Hey guys after experimenting from day one I was able to root I but this time I have no problems of fingerprint reader, Samsung account or anything whatsoever.
All you do have to do is patch AP of firmware from magisk and then flash it from Odin.
How to patch the AP
Install Magisk Manager in non-rooted phone,open it and select install in Magisk --- two option appear -- download zip and patch something , selected the patching one--- locate the AP of firmware from your device then Magisk does its magic.
Finally flash the AP from Odin.
DONOT flash TWRP, it complicates things. Just boot into system after flashing the AP.
Boom you are good to go. You might need to manually install Magisk Manager Apk.
Update: Been using the device for quite awhile now and am yet encounter any problems.
Update 2: Finally got good lock modules working.
Click to expand...
Click to collapse
---------- Post added at 06:04 PM ---------- Previous post was at 06:02 PM ----------
He's asking about pie not Oreo!
Rooted.ndroid said:
It does magnificently. Normal ( flash TWRP and install magisk zip) works well for oreo firmware.
Click to expand...
Click to collapse
Hieuvo said:
Will this delete my data?
Click to expand...
Click to collapse
Most probably. Trying backing up with Google, Samsung and from the apps separately.
Examples respectively:
Photos and files with the help of Google,
Call logs, Bluetooth,Remainders with Samsung
Finally file backup from Nova Backup
Do you have OEM unlocked?
harleycult said:
Hi! Can you please share the exact steps and apps/tools/softwares you used?
I've almost rooted, but not quite there yet and had to turn back.
Thanks!
---------- Post added at 06:04 PM ---------- Previous post was at 06:02 PM ----------
He's asking about pie not Oreo!
Click to expand...
Click to collapse
For the first part see the OP.
And for second, it mentions it works magnificently (for pie) then the method for Oreo.
harleycult said:
Hi! I am stuck as there is no TWRP for Samsung M20 running on Pie (Andrd. 9)
I went through flashing TWRP that's been shared over most pages over the internet.
It did flash, no failures, but still has the same old stock recovery.
But status on the phone says ''Custom''....besides, I cannot get Super SU to work either, as it says root not detected.
The agenda was to install a custom ROM, now I am stuck getting mu phone rooted.
If you've been able to manage, can you please share step by step instructions, with links to the various downloads you did.
Thanks!
Click to expand...
Click to collapse
So you're not able to flash the stock Firmware?
Seems like you're RMM locked.
Follow this up.
And the other thing, I don't think there's any Custom ROM available.
Worked like a charm. Thank you.
Finally got time to install, work perfectly likes stock rom, no problems whatsoever.
Can you post the tutorial on how to install Good Lock.
Thank you very much
Can you post the tutorial on how to install Good Lock.
Rooted.ndroid said:
Hey guys after alot of experimenting I was able to root but every time it had some problems like no fingerprint,not able to log into Samsung account, not able to set secure lock screen (pattern, fingerprint,pin) at all.
But this time I am able to root with no problem whatsoever.
All you do have to do is patch AP of firmware from magisk and then flash it from Odin.
First download your firmware file and extract the file. Copy the AP file (AP in filename) to your device.
How to patch the AP
Install Magisk Manager in non-rooted phone,
open it and select install in Magisk (not Magisk Manager) --- Install -- select and patch a file option ---locate the AP from your device then Magisk does its magic.
Finally flash the AP from Odin by selecting on the second from top.
DONOT flash TWRP, it complicates things. Just boot into system after flashing the AP.
Boom you are good to go. You might need to manually install Magisk Manager Apk.
Update: Been using the device for quite awhile now and am yet encounter any problems.
Update 2: Finally got good lock modules working.
Update 3: Nah nah nah no problems yet.
HOW TO USE GOOD LOCK APPS?
You might be definitely aware that those apps are not available at Galaxy Store for every country, so you better you Nice Lock (which is found on XDA) along with its downloader companion app. Make sure to help the developer either by in app purchase or rating on Play Store. Then the other app you need is Lucky Patcher.
I am assuming dive you're here you're rooted, on lucky Patcher -- toolbox --- patch to android --- patch all one by one. Then download all good lock app you want from nice lock downloader companion and make sure it's on Internal storage.
Now the boring part! Create a modified apk of each application with rebuild function of LP.
Now Install and boom you're good to go.
Tools:
Odin to flash the firmware
Magisk Manager to patch firmware
Lucky Patcher for Good lock
Mention if you need help for Good lock.
My bad looks like I posted in wrong place but still I can help you guys.
Click to expand...
Click to collapse
This metode for oreo or for pie?
Sent from my [device_name] using XDA-Developers Legacy app
nodz13 said:
This metode for oreo or for pie?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Pie
Rooted.ndroid said:
Hey guys after alot of experimenting I was able to root but every time it had some problems like no fingerprint,not able to log into Samsung account, not able to set secure lock screen (pattern, fingerprint,pin) at all.
But this time I am able to root with no problem whatsoever.
All you do have to do is patch AP of firmware from magisk and then flash it from Odin.
First download your firmware file and extract the file. Copy the AP file (AP in filename) to your device.
How to patch the AP
Install Magisk Manager in non-rooted phone,
open it and select install in Magisk (not Magisk Manager) --- Install -- select and patch a file option ---locate the AP from your device then Magisk does its magic.
Finally flash the AP from Odin by selecting on the second from top.
DONOT flash TWRP, it complicates things. Just boot into system after flashing the AP.
Boom you are good to go. You might need to manually install Magisk Manager Apk.
Update: Been using the device for quite awhile now and am yet encounter any problems.
Update 2: Finally got good lock modules working.
Update 3: Nah nah nah no problems yet.
HOW TO USE GOOD LOCK APPS?
You might be definitely aware that those apps are not available at Galaxy Store for every country, so you better you Nice Lock (which is found on XDA) along with its downloader companion app. Make sure to help the developer either by in app purchase or rating on Play Store. Then the other app you need is Lucky Patcher.
I am assuming that you're here you're rooted, on lucky Patcher -- toolbox --- patch to android --- patch all one by one. Install the applications from the link below and boom you're good to go.
https://mega.nz/#!3p1XhC7R!ZIsiJLjJS5g6jT7xaP6gkWgcE0hCRa6vTeVFIj0bvHM
Tools:
Odin to flash the firmware
Magisk Manager to patch firmware
Lucky Patcher for Good lock
My bad looks like I posted in wrong place but still I can help you guys.
Click to expand...
Click to collapse
Up
---------- Post added at 08:18 AM ---------- Previous post was at 08:12 AM ----------
Rooted.ndroid said:
Hey guys after alot of experimenting I was able to root but every time it had some problems like no fingerprint,not able to log into Samsung account, not able to set secure lock screen (pattern, fingerprint,pin) at all.
But this time I am able to root with no problem whatsoever.
All you do have to do is patch AP of firmware from magisk and then flash it from Odin.
First download your firmware file and extract the file. Copy the AP file (AP in filename) to your device.
How to patch the AP
Install Magisk Manager in non-rooted phone,
open it and select install in Magisk (not Magisk Manager) --- Install -- select and patch a file option ---locate the AP from your device then Magisk does its magic.
Finally flash the AP from Odin by selecting on the second from top.
DONOT flash TWRP, it complicates things. Just boot into system after flashing the AP.
Boom you are good to go. You might need to manually install Magisk Manager Apk.
Update: Been using the device for quite awhile now and am yet encounter any problems.
Update 2: Finally got good lock modules working.
Update 3: Nah nah nah no problems yet.
HOW TO USE GOOD LOCK APPS?
You might be definitely aware that those apps are not available at Galaxy Store for every country, so you better you Nice Lock (which is found on XDA) along with its downloader companion app. Make sure to help the developer either by in app purchase or rating on Play Store. Then the other app you need is Lucky Patcher.
I am assuming that you're here you're rooted, on lucky Patcher -- toolbox --- patch to android --- patch all one by one. Install the applications from the link below and boom you're good to go.
https://mega.nz/#!3p1XhC7R!ZIsiJLjJS5g6jT7xaP6gkWgcE0hCRa6vTeVFIj0bvHM
Tools:
Odin to flash the firmware
Magisk Manager to patch firmware
Lucky Patcher for Good lock
My bad looks like I posted in wrong place but still I can help you guys.
Click to expand...
Click to collapse
Can u tell how to do it step by step, point by point ? Plizzz
good lock for m20 without rooting
Hi. Can you tell another way to install good lock modules on galaxy m20 without rooting please ?
nodz13 said:
This metode for oreo or for pie?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
GihanSSMA said:
Hi. Can you tell another way to install good lock modules on galaxy m20 without rooting please ?
Click to expand...
Click to collapse
Nah buddy I wasn't able to run them.
You can install them but they don't function as they are required to.
nodz13 said:
Up
---------- Post added at 08:18 AM ---------- Previous post was at 08:12 AM ----------
Can u tell how to do it step by step, point by point ? Plizzz
Click to expand...
Click to collapse
OP updated
Related
Hello guys,
In recent days, I had seen that some members have issue regarding working xposed that was released previous.
Today, I got a new version of working xposed which is patched by @shakalaca
all credit goes to original developer, I am just posting it here.
I tested it on ze550kl.
it also works on most zenfone series.
prerequisite are same as it was before.
phone must rooted
busy box must installed
root permission must provided to adb shell when asked
just extract archive & first run remov exposed freamework, if there is any non working xposed framework is installed & uninstall xposed apk if installed.
after that reboot system.
not to install frame work first click install xposxed frame work, let process complete & reboot system.
after that click install xposed installer.
now you have working xposed for sdk21 v78 arm64.
Xposed
Work perfect! Thanks!!!
Perfect work. Thanks
rajlko said:
Hello guys,
In recent days, I had seen that some members have issue regarding working xposed that was released previous.
Today, I got a new version of working xposed which is patched by @shakalaca
all credit goes to original developer, I am just posting it here.
I tested it on ze550kl.
it also works on ZenFone 2 2.20.40.13x and ZenFone Selfie 1.13. 40.661
prerequisite are same as it was before.
phone must rooted
busy box must installed
root permission must provided to adb shell when asked
just extract archive & first run remov exposed freamework, if there is any non working xposed framework is installed & uninstall xposed apk if installed.
after that reboot system.
not to install frame work first click install xposxed frame work, let process complete & reboot system.
after that click install xposed installer.
now you have working xposed for sdk21 v76 arm64.
Click to expand...
Click to collapse
It should be pointed out that on my phone query window pops root rights, only after you enter in supersu (my system cant anwer permission adb shell, while manually entered into the application SuperSU)
post updated.
Works great !
edit1
Snapprefs works now
roman.kaskad said:
It should be pointed out that on my phone query window pops root rights, only after you enter in supersu (my system cant anwer permission adb shell, while manually entered into the application SuperSU)
Click to expand...
Click to collapse
sometime pop up for root rights delay due to some mismatch, like you are using patched firmware or boot image of any other system.
Pop window for root right will works well if you have original kernel installed in your phone.
e.g. if you have ze551kl & you are using boot image of ze550kl for root your phone, then you will have this issue.
In patched firmware you may face this issue due to same issue.
Now all the ZE551KL users have to use the ze550kl root method to gain root.
Does that mean all ze551kl users will face the root rights issue?
Sent from my ASUS_Z00TD using Tapatalk
yvg107x said:
Now all the ZE551KL users have to use the ze550kl root method to gain root.
Does that mean all ze551kl users will face the root rights issue?
Sent from my ASUS_Z00TD using Tapatalk
Click to expand...
Click to collapse
Not at all,
it happens some time.
sometime you need to open super user & after that window popup for root right, it happens due to su also.
dose it working with new version .763
BTiwari said:
dose it working with new version .763
Click to expand...
Click to collapse
Yes
roman.kaskad said:
It should be pointed out that on my phone query window pops root rights, only after you enter in supersu (my system cant anwer permission adb shell, while manually entered into the application SuperSU)
Click to expand...
Click to collapse
I had the same issue.. But i fixed it by going to auto start manager... in pre-loaded apps... And switching 'Super Su'option to 'on'...
I think as the app didnt had the the permission to auto start... Prompt only comes only when we go tp app manually.... Anywayzz it worked for me...
BTiwari said:
dose it working with new version .763
Click to expand...
Click to collapse
yes.
flash official xposed-v79-sdk21-arm64.zip normally work fine for me. not patched version.
my decive: ze551kl
not working?
I have the .763 stock firmware on the ZE551KL and rooted with instructions from this thread. It seems to install and "Android is upgrading" pops up, but then there is no Xposed app to install modules from and I've tried installing Xprivacy and BootManager and both say Xposed is not installed. So I guess it didn't work
thefallenghost said:
I have the .763 stock firmware on the ZE551KL and rooted with instructions from this thread. It seems to install and "Android is upgrading" pops up, but then there is no Xposed app to install modules from and I've tried installing Xprivacy and BootManager and both say Xposed is not installed. So I guess it didn't work
Click to expand...
Click to collapse
when you unzip file,there will be three bat files, installxposedframvwork, Installxposedinstaller & removexposedframework.
If you have rooted & install custom recovery, then you may flash zip file from recovery.
if you have not install custom recovery, then unzip file, first run installxposedframework, let process complete, provide root access from you phone when asked, let phone reboot.
after that run installxposedinstaller, let process complete, now you have xposed apk in you phone.
you may also download it from google play store or official thread from developer.
---------------------------------------
rajlko said:
when you unzip file,there will be three bat files, installxposedframvwork, Installxposedinstaller & removexposedframework.
If you have rooted & install custom recovery, then you may flash zip file from recovery.
if you have not install custom recovery, then unzip file, first run installxposedframework, let process complete, provide root access from you phone when asked, let phone reboot.
after that run installxposedinstaller, let process complete, now you have xposed apk in you phone.
you may also download it from google play store or official thread from developer.
Click to expand...
Click to collapse
Ok. When you say I have the apk in my phone, where exactly is it?! I cannot find it... Edit: Nevermind, I had forgotten to run the installer (faceapalm). Sorry...
hi
I can't reboot from Xposed Installer
When I try and reboot through the Xposed Framework I get the following error message everytime:
tmp-mksh: <stdin>[5]: /data/data/de.robv.android.xposed.installer/cache/busybox-xposed: not found
Reboot failed. Please use the device's normal reboot function.
I had busybox installer.
Not sure what else I'm doing wrong?
pedrazadixon said:
flash official xposed-v79-sdk21-arm64.zip normally work fine for me. not patched version.
my decive: ze551kl
Click to expand...
Click to collapse
Thanks for that.
installed and working on Ze551kl with stock rooted rom.
I am now have Adblock installed. woohoo!
ericpeacock79 said:
Thanks for that.
installed and working on Ze551kl with stock rooted rom.
I am now have Adblock installed. woohoo!
Click to expand...
Click to collapse
Last version v85. Work fine.
Only flash the lasted zip.
This module installs the leaked Pixel Launcher and Wallpaper Picker as system apps, to give full Google Now integration.
Got stuck on bootloop. Perhaps it was because I'm using a different system UI/theme (Xperia X) for my Z2.
DawoodSahi said:
Got stuck on bootloop. Perhaps it was because I'm using a different system UI/theme (Xperia X) for my Z2.
Click to expand...
Click to collapse
I don't think that should matter, though I do recall there being compatibility issues with Magisk and Sony devices in general.
jaimbo said:
I don't think that should matter, though I do recall there being compatibility issues with Magisk and Sony devices in general.
Click to expand...
Click to collapse
Not that I know of, everything that I'm using is working very well. That'll include, Phh supersu, systemless xposed, v4a for now.
took a couple of reflashes in the right order but finally got it all working thanks for this, it's pretty awesome.
Tried this module to check out the launcher, very nice. Works well on HTC m8, nice new flavor to try for a bit. Only thing I don't like is not being able to change the date at top of home screen. Wish they made it customised.
Sent from my HTC One M8 using XDA-Developers mobile app
How can I install this? I tried using the downloads section in Magisk Manager and it says "The zip is not a Magisk module!!" and does nothing. Is there a different way for me to install it within Magisk?
Installation worked for me, no error message saying it's not a magisk zip, though i got the same problem from above that i am stuck on my boot screen, device is a samsung galaxy note edge (completly fresh install, latest stock rom, only installed magisk with phh's superuser)
I can't remove it in Magisk Manager. How to remove it completely or is it only remove the 2 apps in /system/app en priv-app?
Sent from my lightning fast SM-G930F (S7)
Is there a way we can get weather instead of the date on the homescreen? TIA
I have weather... maybe you need to download the newer apk from apk mirror ?
Can anyone confirm if the launcher shortcuts work on MM devices?
I have installd pixel launcher module from magisk installer but its not working its showing as follows and there is no ui how to get that
I have rebooted my device many times. But no use
Just a small heads up @jaimbo. The support link in your module is broken (missing a colon).
Bootloop
I'm stuck in a bootloop as well. Any way to uninstall the pixel launcher from recovery?
stryker.x said:
I'm stuck in a bootloop as well. Any way to uninstall the pixel launcher from recovery?
Click to expand...
Click to collapse
yes - flash "Mount-Magisk.zip" file in recovery (from this thread: Collection-magisk-modules. It will mount magisk image to you under /magisk/ folder. Go there and delete whole issues generated module folder. Reboot. Should start now. But... for me (on my device) avery time I mount Magisk image from recovery, I got google account lost, fc few apps, even once whole system ui got fc, so I cant get into my device. Try, risk nothing.
S7E 935F, mahisk v9, Echoerom Nougat deodexed.
this put my s7edge sm g935f into a bootloop. I have no idea what to do. Please help
---------- Post added at 09:36 AM ---------- Previous post was at 08:50 AM ----------
DawoodSahi said:
Got stuck on bootloop. Perhaps it was because I'm using a different system UI/theme (Xperia X) for my Z2.
Click to expand...
Click to collapse
fixed using simplycity's method. i would delete this but i dont know how so for now its just an edit
trinadhchinna7 said:
I have installd pixel launcher module from magisk installer but its not working its showing as follows and there is no ui how to get that
I have rebooted my device many times. But no use
Click to expand...
Click to collapse
which font is that .could you give link pls
Note you can find the zip at https://github.com/Magisk-Modules-Repo/PixelLauncher/archive/master.zip (for "magisk approved" modules at least)
Sort of couldn't find this anywhere for some reason, had to look at where the magisk-manager gets pre-zipped stuff from just replace the repo name for other modules also.
useful when magisk doesnt want to flash+download on its own
pokepokepoke said:
which font is that .could you give link pls
Click to expand...
Click to collapse
Its fords folly if u have blackmart u can get it there
If u r using samsung device and willing to purchase the app then search it in samsung apps
Update (11/09) - This method no longer works with the november security updates from Google as it causes suhide to break.
Here are the steps to follow
If you are already rooted, fully unroot. I do this by doing the following.
1) In the SuperUser app, go to settings and choose to do a full unroot. Choose "No" when it prompts you to restore your stock boot.img
2) Let the system reboot normally.
3) Reboot to recovery
4) If you have Magisk installed, flash the Magisk uninstaller Link
5) If you have suhide installed, flash rm-suhide 0.51 Link
6) Flash your ROM's boot.img extracted from your ROM (simply dirty flashing should also work), or install a custom kernel of your choice
At this point you should have a stock boot.img (or custom kernel) with no traces of SuperUser anywhere
Install SuperUser 2.78 Link
Install suhide 0.55 Link
Reboot into system. Verify that you have root. I'm not 100% sure this is necessary, but I like to do it before proceeding.
Reboot back into recovery.
Flash xsetpropSu.zip (attached to this post) Link
Reboot the system
Install RootSwitch 1.3.3.2 Link
Open up RootSwitch, uncheck disable all SU daemons. Disable Root
Pass SafetyNet
Optional
Using tasker to automatically disable root when certain applications are run. @NYZack made a little writeup here
Credits:
@NYZack - Helping me figure out how to put all of this together
@Captain_Throwback - For help with xsetprop
@Chainfire - SuperSU + SuHide
@topjohnwu - Magisk
work around found
no longer relevant post..
I don't know if the kernel can be modified to pull that trick. Even if someone does though, it's not going to last long. Every bypass you can find, Google can find. Then they know what to fix. The only way to win, is not to play.
And no, you can't lock the bootloader without wiping data.
Well I got it to work...I will turn this thread into a Guide. Who knows how long it will last, but...at least it's working for now.
Thread updated with instructions. I hope this can help someone!
So there's no way to do this without rooting and magisk?
3dawg said:
So there's no way to do this without rooting and magisk?
Click to expand...
Click to collapse
I want root, so I did not try to do that. If your bootloader is unlocked, I do not think there's a way to do it.
Thanks
skaforey said:
Thread updated with instructions. I hope this can help someone!
Click to expand...
Click to collapse
Yes I just followed these instructions and I am green panel. I have to check at a terminal to pay with phone but it probably will work. One note that was kinda unclear in case others do same....It should read :
Turn the Root switch ON....not OFF....when wanting to use AP. You can turn it back on when you want to do other things that require root permissions. I believe this is dynamic and working with the magisk mount point in addition to tricking the boot process into thinking the bootloader is locked.
Thanks so much for this. I was so angry with Google. And I was just going to say FK it and not use AP.
WORKS! Do all the steps in the order he says above and you can turn root off and on at will and have Android Pay work just fine! YAY!
skaforey said:
This thread started as a plea for help, but thanks to @NYZack I have gotten it to work.
Here are the steps to follow
If you are already rooted, fully unroot. I do this by doing the following.
1) If you have suhide installed, download rm-suhide 0.51 Link
2) In the SuperUser app, go to settings and choose to do a full unroot. Choose "No" when it prompts you to restore your stock boot.img
3) Let the system reboot normally.
4) Reboot to recovery
5) Flash rm-suhide 0.51
6) Flash your ROM's boot.img extracted from your ROM (simply dirty flashing should also work), or install a custom kernel of your choice
At this point you should have a stock boot.img (or custom kernel) with no traces of SuperUser anywhere
Install SuperUser 2.78 Link
Install Magisk v8.zip Link
Install suhide 0.55 Link
Reboot into system
Install Magisk Manger 2.1 (apk) Link
Open up Magisk Manager app and go to modules. Click on the + button. Add the following zip for xsetprop Link
Install RootSwitch 1.3.1.2 Link
Reboot system
Using Root Explorer (or some other file manager capable of root access), browse to /magisk/xsetprop and modify post-fs-data.sh . Add the following line to the end of the file, save and exit
Code:
xsetprop ro.boot.flash.locked 1
Reboot system
Open up RootSwitch, uncheck disable all SU daemons. Disable Root
Pass SafetyNet
Click to expand...
Click to collapse
FYI - The latest version of the xSetProp zip (0.2.1 as of this post) handles setting that prop automatically, and has additional logging. I'd recommend using that and you can remove that portion of your guide.
Captain_Throwback said:
FYI - The latest version of the xSetProp zip (0.2.1 as of this post) handles setting that prop automatically, and has additional logging. I'd recommend using that and you can remove that portion of your guide.
Click to expand...
Click to collapse
Thank you! Instructions updated (also tried to give proper credit all around).
I think Chainfire might be in the process of doing something similar without the need for Magisk.
I suppose we could also probably use the xsetprop binary along with a su.d script to run the necessary commands on startup? This would avoid having to use Magisk all together.
If I get some time I might try that out.
No longer works after I reboot the device. It's almost like it knows about my hack. It passes the safety net thing with green screen yet I get message saying that can't verify blah blah...your phone might be rooted! I've updated to 0.2.1 of the xprop and double checked the other things like suhide and magisk and so on. Wth ... Less than a day and Google changed something? I'm baffled. Help!
Pkt_Lnt said:
http://www.xda-developers.com/android-safetynet-now-reportedly-tripped-by-unlocked-bootloaders/
Click to expand...
Click to collapse
Thanks so much for taking the time to write this out.
I am 100% successful with M ROMs like ResRemix
However on my Nexus 6 with N ROMs (like Nitrogen or cDroid) I can't get SafetyNet to pass this way. With Root Switch I can get PoGo to work but following these instructions to a T I still don't have green SN
I wonder if it is the kernel ? What kernel have you been successful with?
Lastly are you aware of any way to find success with 7.1 ROMs?
---------- Post added at 12:31 AM ---------- Previous post was at 12:27 AM ----------
photolarry said:
No longer works after I reboot the device. It's almost like it knows about my hack. It passes the safety net thing with green screen yet I get message saying that can't verify blah blah...your phone might be rooted! I've updated to 0.2.1 of the xprop and double checked the other things like suhide and magisk and so on. Wth ... Less than a day and Google changed something? I'm baffled. Help!
Click to expand...
Click to collapse
Is the message you are getting coming up with SafetyNet or with PoGo ... or when ??
jcrompton said:
Thanks so much for taking the time to write this out.
I am 100% successful with M ROMs like ResRemix
However on my Nexus 6 with N ROMs (like Nitrogen or cDroid) I can get SafetyNet to pass this way. With Root Switch I can get PoGo to work but following these instructions to a T I still don't have green SN
I wonder if it is the kernel ? What kernel have you been successful with?
Lastly are you aware of any way to find success with 7.1 ROMs?
---------- Post added at 12:31 AM ---------- Previous post was at 12:27 AM ----------
Is the message you are getting coming up with SafetyNet or with PoGo ... or when ??
Click to expand...
Click to collapse
Yea I know I think it's something to do with either the kernel I've selected or perhaps suhide no longer works...I'm not sure what the deal is. I'm running Franco #55 and even without root, I get failure but inside the testing app ...see attached
Thanks for this write-up! I was able to pass SafetyNet in both apps while running Pure Nexus 7 w/ Stock OpenGapps.
I think one key thing that was skipped in the OP - be sure your ROM is SafetyNet compatible to begin with. I've run numerous ROMs that even before Google started checking bootloaders, wouldn't pass SafetyNet even if unrooted. For example, I just tried the OP method with Despair's new 7.1 ROM and it failed (probably won't work on 7.0 either). But with Pure Nexus 7.0 it works great.
MrBrady said:
Thanks for this write-up! I was able to pass SafetyNet in both apps while running Pure Nexus 7 w/ Stock OpenGapps.
I think one key thing that was skipped in the OP - be sure your ROM is SafetyNet compatible to begin with. I've run numerous ROMs that even before Google started checking bootloaders, wouldn't pass SafetyNet even if unrooted. For example, I just tried the OP method with Despair's new 7.1 ROM and it failed (probably won't work on 7.0 either). But with Pure Nexus 7.0 it works great.
Click to expand...
Click to collapse
I'm using stock Rom and only custom kernel so this should work on Nbd90z....I'd think. Last test was dreaded message but I'm trying to add few things to suhide blacklist. We shall see
I get the green screen. But then when I tap at store nfc terminal...it claims error....I'm going to try hiding nfc service, and what I think is play services based on uid chainfire explained. I'll try a small purchase and remember to screen capture the error if occurs
skaforey said:
Thank you! Instructions updated (also tried to give proper credit all around).
I think Chainfire might be in the process of doing something similar without the need for Magisk.
I suppose we could also probably use the xsetprop binary along with a su.d script to run the necessary commands on startup? This would avoid having to use Magisk all together.
If I get some time I might try that out.
Click to expand...
Click to collapse
I built the mod for people that were already using Magisk. If you're not using Magisk, then of course you can try just putting the binary in /su/xbin and put the post-fs-data.sh in /su/su.d and see if that works for setting the props at boot time.
I don't use Xposed, so using Magisk + phh's Superuser was my target for the module. I also did try the su.d method with SuperSU, but it wasn't working on my device. I also didn't want to have to use RootSwitch. But feel free to unpack the zip and try whatever combinations you want.
photolarry said:
No longer works after I reboot the device. It's almost like it knows about my hack. It passes the safety net thing with green screen yet I get message saying that can't verify blah blah...your phone might be rooted! I've updated to 0.2.1 of the xprop and double checked the other things like suhide and magisk and so on. Wth ... Less than a day and Google changed something? I'm baffled. Help!
Click to expand...
Click to collapse
Still working for me. Are you sure you disabled root in Root Switch? It automatically re-enables upon logon. Also be sure your xsetprop file is correct.
You can check by using the getprop command
skaforey said:
Still working for me. Are you sure you disabled root in Root Switch? It automatically re-enables upon logon. Also be sure your xsetprop file is correct.
You can check by using the getprop command
Click to expand...
Click to collapse
I'm using it for android pay not pogo. And I did. I'm sure the prop is right or wouldn't get green go. It's an error from AP saying something about unable to verify and might be rooted....or words to that effect
Has anyone has success in installing this on Android 5.0 samsung S4 ? I followed the instructions and the manager just says not installed.
Unless you provide more details and installation logs it's gonna be hard to help...
Didgeridoohan said:
Unless you provide more details and installation logs it's gonna be hard to help...
Click to expand...
Click to collapse
What details would you like to know? I flash it and then later restart but the manager was not there so I tried to install it from saving the apk file that I downloaded. But it just said it was not installed and later I found out I lost root from trying to flash Xposed on my phone.
I am very new to this and tried to follow the tutorials and videos but its not working cause I thought using Magisk I can install the seamless Xposed.
Those recovery/installation logs would be a good start.
You're muddling up the details a bit...
Was the Manager not installed or did it report that Magisk wasn't installed? And you lost root? But you said you couldn't install Magisk... Are you already rooted? That might cause issues.
Being nice and clear and detailed (what is being flashed, version numbers, what's already done, what works, what doesn't work, with logs, etc) in your descriptions would help.
Didgeridoohan said:
Those recovery/installation logs would be a good start.
You're muddling up the details a bit...
Was the Manager not installed or did it report that Magisk wasn't installed? And you lost root? But you said you couldn't install Magisk... Are you already rooted? That might cause issues.
Being nice and clear and detailed (what is being flashed, version numbers, what's already done, what works, what doesn't work, with logs, etc) in your descriptions would help.
Click to expand...
Click to collapse
I hope this is clearly for you!
1. I flash the file with TWRP with success
2. The phone got stuck on samsung logo
3. Root was removed.
4.I had to re flash stock and it is working again.
5. How do I get the logs of Magisk if my phone keeps looping?
I wanted to use Magisk to see if Xposed would work but it looks like i can't even get Magisk to work on my samsung i9500 with original rom. This same thing happens with Xposed where everything goes smoothly with flashing it in recovery and then a boot loop on the logo. Others on this forum have been complaining about this too and perhaps the developer might have not considered odexed rom like samsung for these wonderful apps to work?
I am going back to Kitkat where i don't have these issues and I can use Xposed.
Hi,
I was running stock ROM with stock recovery plus Magisk v16 and MagiskManager v5.9.1 on my Galaxy S8 and Nougat. As far as I remember I did install MagiskManager using adb, pushed, patched and pulled the boot.img, flashed it using Heimdall. Both apk and patched_boot.img are available on my hard disk...
I then updated MagiskManager using the in app update. Afterwards I used the "direct install" to update Magisk. That took me to 20.4 / 8.0.2. I don't remember if it asked to install the runtime.
I installed modules busybox, sqlite3 and movecertificates, but with no effect (e.g. there is no /system/bin/sqlite3, no nc in my path, user certs remain user certs). I also can't find any indication in MagiskManager that modules are installed.
I didn't have time to figure out what's wrong and tried to revert back to my old versions.
That's what I did: Full uninstall from MagiskManager 8.0.2. Reboot without Magisk, adb push MagiskManager-v5.9.1.apk. Flash my old patched_boot with Magisk v16 using Heimdall. But unfortunately that gives me Magisk Manager stuck on the splash sceen. No applet can get root access, e.g. su on adb shell blocks (needs ctrl+c). Ok, uninstalled MM.
I installed the stock boot img in the intention to load MM 8.0.2 before I flash M 20.4. That didn't accept my pattern for the "your device is encrypted" screen. Well... I flashed M 20.4 patched boot.img again. After first try it shows an integrity issue and offers to wipe the phone.
* Anyway to go from here besides wipe?
* What residuals might be blocking when returning to the old versions?
* Why are modules not working on current version?
Thank you
urbancubb said:
* Why are modules not working on current version?
Click to expand...
Click to collapse
Are they current module zips, or ones that you had laying around from before updating? The modules might be using outdated installation scripts (that's my prime suspect at least).
* What residuals might be blocking when returning to the old versions?
Click to expand...
Click to collapse
Magisk v16 is soooo old. It's gonna be almost impossible to give any kind of help with that. Better to update to a current Magisk release.
* Anyway to go from here besides wipe?
Click to expand...
Click to collapse
I have no idea, you'd wan't someone who knows Samsung for that. Your device's forum might be a good place to start.
Didgeridoohan said:
Are they current module zips, or ones that you had laying around from before updating? The modules might be using outdated installation scripts (that's my prime suspect at least).
Click to expand...
Click to collapse
I installed them from within Magisk Manager from the online repo.
I noticed that this might be the case, but as there was updates this year I think on at least two of them and none worked, I think its a general problem and not caused by the module itself. Any module I could use to test wich works for sure?
Didgeridoohan said:
Magisk v16 is soooo old. It's gonna be almost impossible to give any kind of help with that. Better to update to a current Magisk release.
Click to expand...
Click to collapse
Which didn't work... We'll see.
Didgeridoohan said:
I have no idea, you'd wan't someone who knows Samsung for that. Your device's forum might be a good place to start.
Click to expand...
Click to collapse
Good hint, I started a new thread.
Thank you!
For the modules issue, the only way to know for sure what happened is to look at the install logs and the Magisk log for the following reboot.
So if you get things up and running again, and the issue still persists, make sure to provide those.
One thing I didn't think of before: I recently tried the SafatyNet check (which failed), maybe the failed reboot was the first one after checking, I don't remember exactly.