Database Info

[ROOT][TOOL][VRALHE][VRALHD] SuperSU Root w/ Out Flashing

TESTED AND WORKS ON THE NEW VRALHE AND VRALHD IN ADDITION TO ALL OF THE OTHERS
(EXCEPT THE NEW LEAK I535VRBLI5) I AM WORKING ON IT
BOTH DEODEXED AND ODEXED
​
This is a modified version of debugfs that installs SuperSU instead of SuperUser. The only other way I was aware of that would install SuperSU without having to install SuperUser first, was Chainfire's method using a CWM zip and flashing. You use this version of debugfs just as you would normally from here . There are a few changes, but if you have used debugfs before, you will have no trouble.
THIS MODIFIED DEBUGFS IS 100% STABLE/UPDATED SCRIPT 10/09/2012!!!
DOWNLOAD: SuperSu_GS3_Debugfs_r2b.7Z
MIRROR: here MIRROR2: here
MD5: FE4F03407F8CACF8575714CED91CC843
DOWNLOAD: SuperSu_GS3_Debugfs_r2b.MD5
MIRROR: here MIRROR2: here
MD5: 44F4BE5F7E1A41CCEA14822A3D5E8F54
MODIFIED Debugfs
{
"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"
}
Opening SuperSU for the FIRST time
-------
-------
Roots PERFECTLY
--
--
--
Phone Number, Device Status and IMEI are ALL GOOD
-------
ALL CREDITS GO TO:
* miloj, for the debugfs root method for the Asus TF300T
* sparkym3, for his script for rooting the Asus Transformer Prime - this is a modified version of that script
* Chainfire, for the SU files/binaries and Supersu
* Noxious Ninja, for making Debugfs work w/the SGS3
I am a Flash-O-Holic and I love my rooted devices. I really like to use SuperUser for some devices, BUT for some devices I would rather use SuperSU. They are both great APPS.
But, if you are extremely anal like I am, you like things to be as clean as possible. And even if you root your device and install SuperUser so that you can install SuperSU afterwards, you still have to go back and uninstall SuperUser (if you want to). I am sure there is nothing left behind, but I like everything to be fresh.
-
I did not like having to install SuperUser and then afterward insstall SuperSU and then delete SuperUser, etc, etc. So, I came up with this method using the Debugfs script and Chainfire's SuperSU.
-
I give all credits to Noxious Ninja for getting this to work wth the Samsung Galaxy S III for Verizon.
I simply changed a little of the script and swapped out the binaries and APK.[/FONT]
-
-
DON'T FORGET TO HIT THE "THANKS" BUTTON IF YOU LIKED IT!
-
-
-
I was not the one who made this tool and I really can only accept about 25% of the credits for this tool. I just modified/scripted debugfs to use SuperSU instead of SuperUser.
Noxious Ninja was the one who modified it to work with the Samsung Galaxy S III.
I used/modified his script. I found out it was okay to modify this tool as long as the PROPER CREDITS were given.
I also used some of Chainfire's files obviously for SuperSU.
This is Noxious Ninja's credit list for the original creators.
Noxious Ninja said:
Credits:
* miloj, for the debugfs root method for the Asus TF300T
* sparkym3, for his script for rooting the Asus Transformer Prime - this is a modified version of that script
* ChainsDD, for Superuser
Click to expand...
Click to collapse
If you get a chance to donate/thank them, I am sure they would appreciate it.
I made sure that there were links for absolutely EVERYONE that had a hand in debugfs. Inside of the "Donate Menu".
-
-
-
-
-

Reserved
..

Is there any need to wipe any data or other settings? Or is this just a plain simple way to have root access and it does nothing else (which is what I need/want)?

gmm6797 said:
Is there any need to wipe any data or other settings? Or is this just a plain simple way to have root access and it does nothing else (which is what I need/want)?
Click to expand...
Click to collapse
I' sorry, but could you elaborate? If you want to get root from your stock/unrooted ROM, then this is a tool you could use.

For some reason I cant download ....

:victory:
h3llsdr0id said:
I' sorry, but could you elaborate? If you want to get root from your stock/unrooted ROM, then this is a tool you could use.
Click to expand...
Click to collapse
In a lot of the root scripts, it requires the phone to be wiped and cache deleted or cleared.
I wanted to know if this was the case, so I can run multiple backups (since titan backup wont work until rooted)

Can anyone mirror the download to another site?? wont let me d/l from the OP site

they both downloaded fine for me

im getting something about javascript not being enabled on the download site
but its enable...
EDIT
This is what i get...
{"INFO":"failed posted hashcheck","SOLUTION":"please make sure you have javascript enabled for androidfilehost.com. Hit the back button, enable javascript and try again please. we promise we are probably not doing anything nefarious. maybe. no promises though."}

crazydad said:
im getting something about javascript not being enabled on the download site
but its enable...
EDIT
This is what i get...
{"INFO":"failed posted hashcheck","SOLUTION":"please make sure you have javascript enabled for androidfilehost.com. Hit the back button, enable javascript and try again please. we promise we are probably not doing anything nefarious. maybe. no promises though."}
Click to expand...
Click to collapse
Mirrors are up. Let me know if y'all have anymore problems.

THANKS!!!!!!!!!!!!!!!!!!!!!!!!!!!! BTW Awesome work!!

gmm6797 said:
In a lot of the root scripts, it requires the phone to be wiped and cache deleted or cleared.
I wanted to know if this was the case, so I can run multiple backups (since titan backup wont work until rooted)
Click to expand...
Click to collapse
:victory:
I just tested it on my other SGS3 which was running a stock ROM and had not been rooted. I have been installing apps and using it as my personal phone for about a week. I ran the modified debugfs and it rooted my phone perfectly. Just make sure you read the instructions when you run debugfs.
Make sure you have "Uknown Sources" checked off in Security Settings and that you also have enabled "USB Debugging" in Developer Options.
-
-
-
-
-
-

crazydad said:
THANKS!!!!!!!!!!!!!!!!!!!!!!!!!!!! BTW Awesome work!!
Click to expand...
Click to collapse
Thanks A LOT brother.
You can support me by hitting the THANKS BUTTON and everyone else listed in the OP (who created Debugfs and made this all possible) by doing the same.
Support Chainfire and purchase SuperSU Pro!

Thanks so much for this, its perfect !!
I'm just about to root my phone, was reading all the guides and thought how nice it'd be if the DebugFS method had the newer SuperSU instead, and you did all the work already

ECrispy said:
Thanks so much for this, its perfect !!
I'm just about to root my phone, was reading all the guides and thought how nice it'd be if the DebugFS method had the newer SuperSU instead, and you did all the work already
Click to expand...
Click to collapse
Thank you for trying it out. I did it mainly so that there was a way to use SuperSU without having to go through the process of installing and uninstalling or flashing a zip.
In regards to:
ECrispy said:
you did all the work already
Click to expand...
Click to collapse
I was not the one who made this tool and I really can only accept about 25% of the credits for this tool. I just modified/scripted debugfs to use SuperSU instead of SuperUser.
Noxious Ninja was the one who modified it to work with the Samsung Galaxy S III.
I used/modified his script. I found out it was okay to modify this tool as long as the PROPER CREDITS were given.
I also used some of Chainfire's files obviously for SuperSU.
This is Noxious Ninja's credit list that I also added to the OP for the original creators.
Noxious Ninja said:
Credits:
* miloj, for the debugfs root method for the Asus TF300T
* sparkym3, for his script for rooting the Asus Transformer Prime - this is a modified version of that script
* ChainsDD, for Superuser
Click to expand...
Click to collapse
If you get a chance to donate/thank them, I am sure they would appreciate it.
I made sure that there were links for absolutely EVERYONE that had a hand in debugfs. Inside of the "Donate Menu".

will this work on the new ota

johnminator said:
will this work on the new ota
Click to expand...
Click to collapse
Okay. I just took the OTA update just so that I could test this. I sucessfully rooted my phone with SuperSU!!!
But, just in case:
I DO NOT TAKE ANY RESPONSIBILITY IF YOU MESS UP/BRICK YOUR PHONE WHILE TRYING TO ROOT YOUR PHONE WITH THIS MODDED DEBUGFS.
Yes. It just worked on MY phone, but you never know what could happen.
For some reason, my bootloader did not relock (many are saying that their bootloader gets re-locked).

I already have my phone rooted using the original method with SuperUser I would rather use SuperSu can I just use this or would it be easier and safer to just install SuperSu and delete SuperUser?

So this is still going to work on both phones with and without the OTA, right?

LakerStar25 said:
I already have my phone rooted using the original method with SuperUser I would rather use SuperSu can I just use this or would it be easier and safer to just install SuperSu and delete SuperUser?
Click to expand...
Click to collapse
Hey brother.
Both ways seem fine. If it was me (because I am a weird) I would start over from scratch and root with SuperSU.
Or, leave SuperUser on your system and run this tool. Then after it is done running, you won't have to give SuperSU permission through SuperUser to update it's binary, because it will have already installed it with DebugFS. Then you can uninstall SuperUser.
(I.E. You know how when you normally have SuperUser on root66/other ROMS/etc. and you have to install SuperSU and then give it permissions from SuperUser to update it's binary, and then uninstall SuperUser, etc, etc? If you just run this tool, you won't have to go through that whole process)
So are you on the OTA right now?
Please post back and tell us how everything turned out!!!

[Guide] Bypass Safetynet on MM with Custom ROM & Kernel (Looking for testers)

I would first like to say that I cannot guarantee if this works on ALL devices. I was able to get this to work on the Galaxy S6 and posted it on the Galaxy S6 forums, however I am looking for people with other devices to see if it works for them as well (because why not share the bypass love to everyone ) If it works, please post a screenshot to confirm so I can post it on the thread here. Thanks.
(Please note that I am not responsible if your phone bricks etc. Please use at your own risk! Myself and others who have also tested this bypass have had no reported issues of this bypass causing some sort of brick etc., but I cannot guarantee anything.)
*This is a copy and paste of a thread I made on another forums and I felt like sharing it here. If there is any mistakes in the post, please tell me so I can fix it. Thanks.*​__________________________________​
Since October 2016, Google has (yet again) changed their way on how SafetyNet works and how they can now easily figure out if your phone is rooted or not. This caused many issues for rooted Android users who wanted to play games such as PKMNGO and use apps such as Snapchat. However, there is still ways to bypass SafetyNet.
Tested Devices:
- Samsung Galaxy S6
- Samsung Galaxy S5
*Looking for people with other devices to try and see if it works for themselves so I can add the device to the list.*
__________________________________​
Requirements:
- Basic Understanding on how to use Custom Recovery, flashing zip files etc.
- Running on Android 6.0 (Looking for anyone with Android 7 to see if this works for them as well.)
- Phone has a custom recovery (I suggest TWRP) and on a Custom ROM. (Stock roms "should" work too.)
- Rom should have November 1st Security update or older updates. (Have not tested with roms with November 5th Security update and higher.)
- Magisk V10.2 & Magisk Manager 3.0
- SafetyNet Checker
- Phh Super User APK. PlayStore or 2.0 Beta
- Root File Explorer. I suggest Root Browser
- Kernel Adiutor
- Root Checker
(I have had issues trying Xposed on Magisk V9, however it may work on V10.2)
Tutorial
**WARNING: BIG IMAGES** (Had no time to resize them, but will soon.)
Before we begin, I suggest that you make a Nandroid backup through your preferred Custom Recovery. I suggest you use TWRP however CWM "should" work, but I have not tried myself.
Step 1:
Clean Install
The first step 'is' optional, however it is recommended that you do a clean install. I will be using Alexis Rom 8.0 Beta 2 for my Galaxy S6, but any rom should work. (Other than certain GraceUX ports, but am able to get it to work with other ported rom like CoreUi (a MIUI port) for the Galaxy S6). You should also flash a kernel now as well. I use to personally use Arter97 as SuperSU is not installed in this kernel, however Arter97 is slowly starting to become unstable as it hasn't been updated and there is better kernels out there. For this tutorial, I will be using Twisted Kernel.
Step 2:
Removing SuperSU
This step is 'also' optional, but ONLY if your rom/kernel does not automatically install SuperSU for you. In my case, it is automatically installed.
What you will need to do is to go to the SuperSU app, go to settings.
{
"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"
}
Scroll down until you see "Full unroot" and click it.
A popup will come up and click "Continue", then followed by another popup and click "NO".
Once you click no, your phone will freeze and then reboot. You should then install Root Checker to verify if your phone is unrooted.
(If for some reason, you are unable to use the SuperSU app but you know SuperSU is installed, I'd suggest you download UPDATE-unSU-signed.zip and flash it as it will manually remove SuperSU.)
Step 3:
Installing required APKs.
You will now need to install MagiskManager 3.0, SafetyNet Helper Sample, PHH Super User APK, Root Browser and Kernel Adiutor.
Step 4:
Flashing MagiskV10.2
You will need to reboot into your custom recovery and flash "Magisk-v10.2.zip", followed by rebooting. If you receive ERROR: 1 in TWRP when it is trying to mount SU, I suggest reflashing a kernel (and re-remove SuperSU), uninstalling Magisk with MagiskUninstaller (in Magisk thread) and reinstall Magisk V10.2, or reinstalling your rom.
Once you have flashed the file, reboot into System and open Magisk Manager to verify you have installed Magisk. A little pop up will open to allow Magisk to have root. Make sure to click allow and set it so it has root for "Forever".
If it states that root isn't properly installed, manually flash PHH Super User V266-2.
Step 5:
Enabling Magisk Hide
In Magisk Manager, go to the side menu and go to "Settings." You will see an unchecked box that says "Enable Magisk Hide." Select it and reboot. Re-open Magisk Manager and verify that it is now check marked. If the App crashes when you select "Enable Magisk Hide", reboot your phone and retry.
Step 6:
Set Permissions
In Root Browser, go to the directory "/sys/fs/selinux" and find the file "enforce" and the file "policy". On the file "enforce", change the permissions of the file from "644" to "640", and for the file "enforce", change the permissions of the file from "444" to "440". If Phh Super User pops up and asks for root access, click "Allow."
Once you are done, open up SafetyNet Helper Sample and it 'should' pass. If you are getting "Response Validation Failed" and the background is blue, uninstall Magisk by flashing Magisk Uninstaller, flash UPDATE-unSU-signed.zip, then reflash Magisk V10.2. Then, go back to Step 5 and enable Magisk Hide.
Step 7:
Use Kernel Adiutor to automatically set permissions in init.d
This last step is 'optional', however it automates the permission setting as every time you reboot your system, the file permissions will reset. Open up Kernel Adiutor, go to the sidebar and scroll down until you see 'Init.d'. Click it and make sure "Emulate Init.d" is enabled.
Then click the plus button, set the name to "Permissions" and then add the following script:
"chmod 640 /sys/fs/selinux/enforce" and "chmod 440 /sys/fs/selinux/policy" and save the files.
Also allow root access to Kernel Adiutor!
Step 8:
Reboot
Reboot your device, let Kernel Adiutor do its countdown (you will see in the notifications drop down) and once it says "Applying settings completed!", open up Safetynet and you should be passing!
Credits:
topjohnwu - Main developer of Magisk and Magisk Supported Phh Super User
This XDA thread - Helped me figure out how to do this bypass in the first place.
CoreUi Telegram Chat - Helped me test this bypass to see if it worked on different S6 models. Join here!
If I forgot to credit anyone, please tell me.
__________________________________​
If there is any mistakes I made, spelling, phrasing etc., please tell me so I can fix it. Thanks.

Finally I can play again since they added the SafetyNet check! It's been way too long.
Worked perfectly on my Galaxy S5! I'm using the Resurrection Remix KLTE 6.0 for my Galaxy S5 so it came with it's own root. I just searched Root in settings, disabled it, flashed the unroot zip and then I was unrooted. Except for that everything worked the way you described! I forgot to reboot after Magisk Hide so I unrooted and reflashed Magisk but I'm not sure that was needed to be honest. Is SafetyNet Checker really needed? Magisk Manager also has a SafteyNet checker.
When I get more time I will do a backup and flash the 7.1.1 rom too and test if it works.
Complete package with everything needed in the guide for the lazy:
https://mega.nz/#!R18XRZQB!pgGx2LgNV8aqfwhsutmUnC4jay-FTGVR3-a9r3TJaEA

Martan404 said:
Finally I can play again since they added the SafetyNet check! It's been way too long.
Worked perfectly on my Galaxy S5! I'm using the Resurrection Remix KLTE 6.0 for my Galaxy S5 so it came with it's own root. I just searched Root in settings, disabled it, flashed the unroot zip and then I was unrooted. Except for that everything worked the way you described! I forgot to reboot after Magisk Hide so I unrooted and reflashed Magisk but I'm not sure that was needed to be honest. Is SafetyNet Checker really needed? Magisk Manager also has a SafteyNet checker.
When I get more time I will do a backup and flash the 7.1.1 rom too and test if it works.
Click to expand...
Click to collapse
There 'is' a Safetynet checker in Magisk Manager, however it will always say 'CTS Profile error', while SafetyNet Checker will say if its either a CTS error, Response Validation error, Play Store error etc. Maybe it's just a bug in Magisk Manager but if it gets fixed; I'll remove SafetyNet Checker from the tutorial.

xJovs said:
There 'is' a Safetynet checker in Magisk Manager, however it will always say 'CTS Profile error', while SafetyNet Checker will say if its either a CTS error, Response Validation error, Play Store error etc. Maybe it's just a bug in Magisk Manager but if it gets fixed; I'll remove SafetyNet Checker from the tutorial.
Click to expand...
Click to collapse
Can confirm that this works on 7.1.1 roms too! As I mentioned in my other post I use the Resurrection Remix rom.
By the way, you could mention that instead of using root browser to change permissions you could skip that step all together and just add the modification to Kernel Auditor. And instead of rebooting to test it you can just click the "Permissions" addition to execute the script right away just to make sure it works and then do a reboot to confirm.

Thank you so much. it worked

help plse plse give steps by step for 7.1.1(RR)
---------- Post added at 02:58 AM ---------- Previous post was at 02:54 AM ----------
i tried but cts profile mismatch becomes false
Sent from my MotoG3 using Tapatalk

Running a Mi Max here and have to say: Not working!
If i fully unroot the phone (magisk uninstaller / unSU script) then safety net helper gives me a red screen (CTS profile mismatch) but after installing Magisk 10.2 i only get a blueish screen in safetynethelper saying "response validation: fail"

naveenfre said:
help plse plse give steps by step for 7.1.1(RR)
---------- Post added at 02:58 AM ---------- Previous post was at 02:54 AM ----------
i tried but cts profile mismatch becomes false
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
1. Open the Settings app, and go About phone tab and spam click on Version to enable Developer Tools.
2. Do a search in the settings for "Root" and disable Root access.
3. Reboot to Recovery mode and flash this unroot https://forum.xda-developers.com/showpost.php?p=63615067
4. Reboot phone and follow xJovs' guide from step 3
Note: I also used the flashable zip file from the guide to get root and did not install the APK. https://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921
g_BonE said:
Running a Mi Max here and have to say: Not working!
If i fully unroot the phone (magisk uninstaller / unSU script) then safety net helper gives me a red screen (CTS profile mismatch) but after installing Magisk 10.2 i only get a blueish screen in safetynethelper saying "response validation: fail"
Click to expand...
Click to collapse
It might be because of the Kernel but I'm just speculating. Try flashing a new one to see if it helps!

g_BonE said:
Running a Mi Max here and have to say: Not working!
If i fully unroot the phone (magisk uninstaller / unSU script) then safety net helper gives me a red screen (CTS profile mismatch) but after installing Magisk 10.2 i only get a blueish screen in safetynethelper saying "response validation: fail"
Click to expand...
Click to collapse
It will always return blue right after installing Magisk. You need to follow through with the whole tutorial to work. If you have, then it's probably your rom. It happened with me on GraceUX roms.

Latest version of PoGo doesn't appear in magisk hide menu

It works
Thanks! Editing the permission of SElinux files works for me
Nexus 5X
GooglePixelROM v7.0.1
Android 7.1.2
NPG05D
Using Magisk 11.1
Now I can pass SafetyNet and use AndroidPay on a custom ROM

Galaxy Note 3 (N9005) MagmaNX with Magisk v11.1 + MagiskSU
CTS profile match: false
Basic Integrity: false

xJovs said:
I would first like to say that I cannot guarantee if this works on ALL devices. I was able to get this to work on the Galaxy S6 and posted it on the Galaxy S6 forums, however I am looking for people with other devices to see if it works for them as well (because why not share the bypass love to everyone ) If it works, please post a screenshot to confirm so I can post it on the thread here. Thanks.
(Please note that I am not responsible if your phone bricks etc. Please use at your own risk! Myself and others who have also tested this bypass have had no reported issues of this bypass causing some sort of brick etc., but I cannot guarantee anything.)
*This is a copy and paste of a thread I made on another forums and I felt like sharing it here. If there is any mistakes in the post, please tell me so I can fix it. Thanks.*​__________________________________​
Since October 2016, Google has (yet again) changed their way on how SafetyNet works and how they can now easily figure out if your phone is rooted or not. This caused many issues for rooted Android users who wanted to play games such as PKMNGO and use apps such as Snapchat. However, there is still ways to bypass SafetyNet.
Tested Devices:
- Samsung Galaxy S6
- Samsung Galaxy S5
*Looking for people with other devices to try and see if it works for themselves so I can add the device to the list.*
__________________________________​
Requirements:
- Basic Understanding on how to use Custom Recovery, flashing zip files etc.
- Running on Android 6.0 (Looking for anyone with Android 7 to see if this works for them as well.)
- Phone has a custom recovery (I suggest TWRP) and on a Custom ROM. (Stock roms "should" work too.)
- Rom should have November 1st Security update or older updates. (Have not tested with roms with November 5th Security update and higher.)
- Magisk V10.2 & Magisk Manager 3.0
- SafetyNet Checker
- Phh Super User APK. PlayStore or 2.0 Beta
- Root File Explorer. I suggest Root Browser
- Kernel Adiutor
- Root Checker
(I have had issues trying Xposed on Magisk V9, however it may work on V10.2)
Tutorial
**WARNING: BIG IMAGES** (Had no time to resize them, but will soon.)
Before we begin, I suggest that you make a Nandroid backup through your preferred Custom Recovery. I suggest you use TWRP however CWM "should" work, but I have not tried myself.
Step 1:
Clean Install
The first step 'is' optional, however it is recommended that you do a clean install. I will be using Alexis Rom 8.0 Beta 2 for my Galaxy S6, but any rom should work. (Other than certain GraceUX ports, but am able to get it to work with other ported rom like CoreUi (a MIUI port) for the Galaxy S6). You should also flash a kernel now as well. I use to personally use Arter97 as SuperSU is not installed in this kernel, however Arter97 is slowly starting to become unstable as it hasn't been updated and there is better kernels out there. For this tutorial, I will be using Twisted Kernel.
Step 2:
Removing SuperSU
This step is 'also' optional, but ONLY if your rom/kernel does not automatically install SuperSU for you. In my case, it is automatically installed.
What you will need to do is to go to the SuperSU app, go to settings.
Scroll down until you see "Full unroot" and click it.
A popup will come up and click "Continue", then followed by another popup and click "NO".
Once you click no, your phone will freeze and then reboot. You should then install Root Checker to verify if your phone is unrooted.
(If for some reason, you are unable to use the SuperSU app but you know SuperSU is installed, I'd suggest you download UPDATE-unSU-signed.zip and flash it as it will manually remove SuperSU.)
Step 3:
Installing required APKs.
You will now need to install MagiskManager 3.0, SafetyNet Helper Sample, PHH Super User APK, Root Browser and Kernel Adiutor.
Step 4:
Flashing MagiskV10.2
You will need to reboot into your custom recovery and flash "Magisk-v10.2.zip", followed by rebooting. If you receive ERROR: 1 in TWRP when it is trying to mount SU, I suggest reflashing a kernel (and re-remove SuperSU), uninstalling Magisk with MagiskUninstaller (in Magisk thread) and reinstall Magisk V10.2, or reinstalling your rom.
Once you have flashed the file, reboot into System and open Magisk Manager to verify you have installed Magisk. A little pop up will open to allow Magisk to have root. Make sure to click allow and set it so it has root for "Forever".
If it states that root isn't properly installed, manually flash PHH Super User V266-2.
Step 5:
Enabling Magisk Hide
In Magisk Manager, go to the side menu and go to "Settings." You will see an unchecked box that says "Enable Magisk Hide." Select it and reboot. Re-open Magisk Manager and verify that it is now check marked. If the App crashes when you select "Enable Magisk Hide", reboot your phone and retry.
Step 6:
Set Permissions
In Root Browser, go to the directory "/sys/fs/selinux" and find the file "enforce" and the file "policy". On the file "enforce", change the permissions of the file from "644" to "640", and for the file "enforce", change the permissions of the file from "444" to "440". If Phh Super User pops up and asks for root access, click "Allow."
Once you are done, open up SafetyNet Helper Sample and it 'should' pass. If you are getting "Response Validation Failed" and the background is blue, uninstall Magisk by flashing Magisk Uninstaller, flash UPDATE-unSU-signed.zip, then reflash Magisk V10.2. Then, go back to Step 5 and enable Magisk Hide.
Step 7:
Use Kernel Adiutor to automatically set permissions in init.d
This last step is 'optional', however it automates the permission setting as every time you reboot your system, the file permissions will reset. Open up Kernel Adiutor, go to the sidebar and scroll down until you see 'Init.d'. Click it and make sure "Emulate Init.d" is enabled.
Then click the plus button, set the name to "Permissions" and then add the following script:
"chmod 640 /sys/fs/selinux/enforce" and "chmod 440 /sys/fs/selinux/policy" and save the files.
Also allow root access to Kernel Adiutor!
Step 8:
Reboot
Reboot your device, let Kernel Adiutor do its countdown (you will see in the notifications drop down) and once it says "Applying settings completed!", open up Safetynet and you should be passing!
Credits:
topjohnwu - Main developer of Magisk and Magisk Supported Phh Super User
This XDA thread - Helped me figure out how to do this bypass in the first place.
CoreUi Telegram Chat - Helped me test this bypass to see if it worked on different S6 models. Join here!
If I forgot to credit anyone, please tell me.
__________________________________​
If there is any mistakes I made, spelling, phrasing etc., please tell me so I can fix it. Thanks.
Click to expand...
Click to collapse
i have HTC Desire 820 d820u running 6.0.1 mm stock.
is this will be ok to try?????

yo_honey said:
i have HTC Desire 820 d820u running 6.0.1 mm stock.
is this will be ok to try?????
Click to expand...
Click to collapse
Could but I have no idea.

I have tried latest magisk
xJovs said:
Could but I have no idea.
Click to expand...
Click to collapse
Here is full guide https://forum.xda-developers.com/desire-820/general/guide-bypass-safetynet-magisk-t3592508

Doesn't this work for Lollipop or is it just that you haven't tested?

xJovs said:
I would first like to say that I cannot guarantee if this works on ALL devices. I was able to get this to work on the Galaxy S6 and posted it on the Galaxy S6 forums, however I am looking for people with other devices to see if it works for them as well (because why not share the bypass love to everyone ) If it works, please post a screenshot to confirm so I can post it on the thread here. Thanks.
(Please note that I am not responsible if your phone bricks etc. Please use at your own risk! Myself and others who have also tested this bypass have had no reported issues of this bypass causing some sort of brick etc., but I cannot guarantee anything.)
*This is a copy and paste of a thread I made on another forums and I felt like sharing it here. If there is any mistakes in the post, please tell me so I can fix it. Thanks.*​__________________________________​
Since October 2016, Google has (yet again) changed their way on how SafetyNet works and how they can now easily figure out if your phone is rooted or not. This caused many issues for rooted Android users who wanted to play games such as PKMNGO and use apps such as Snapchat. However, there is still ways to bypass SafetyNet.
Tested Devices:
- Samsung Galaxy S6
- Samsung Galaxy S5
*Looking for people with other devices to try and see if it works for themselves so I can add the device to the list.*
__________________________________​
Requirements:
- Basic Understanding on how to use Custom Recovery, flashing zip files etc.
- Running on Android 6.0 (Looking for anyone with Android 7 to see if this works for them as well.)
- Phone has a custom recovery (I suggest TWRP) and on a Custom ROM. (Stock roms "should" work too.)
- Rom should have November 1st Security update or older updates. (Have not tested with roms with November 5th Security update and higher.)
- Magisk V10.2 & Magisk Manager 3.0
- SafetyNet Checker
- Phh Super User APK. PlayStore or 2.0 Beta
- Root File Explorer. I suggest Root Browser
- Kernel Adiutor
- Root Checker
(I have had issues trying Xposed on Magisk V9, however it may work on V10.2)
Tutorial
**WARNING: BIG IMAGES** (Had no time to resize them, but will soon.)
Before we begin, I suggest that you make a Nandroid backup through your preferred Custom Recovery. I suggest you use TWRP however CWM "should" work, but I have not tried myself.
Step 1:
Clean Install
The first step 'is' optional, however it is recommended that you do a clean install. I will be using Alexis Rom 8.0 Beta 2 for my Galaxy S6, but any rom should work. (Other than certain GraceUX ports, but am able to get it to work with other ported rom like CoreUi (a MIUI port) for the Galaxy S6). You should also flash a kernel now as well. I use to personally use Arter97 as SuperSU is not installed in this kernel, however Arter97 is slowly starting to become unstable as it hasn't been updated and there is better kernels out there. For this tutorial, I will be using Twisted Kernel.
Step 2:
Removing SuperSU
This step is 'also' optional, but ONLY if your rom/kernel does not automatically install SuperSU for you. In my case, it is automatically installed.
What you will need to do is to go to the SuperSU app, go to settings.
Scroll down until you see "Full unroot" and click it.
A popup will come up and click "Continue", then followed by another popup and click "NO".
Once you click no, your phone will freeze and then reboot. You should then install Root Checker to verify if your phone is unrooted.
(If for some reason, you are unable to use the SuperSU app but you know SuperSU is installed, I'd suggest you download UPDATE-unSU-signed.zip and flash it as it will manually remove SuperSU.)
Step 3:
Installing required APKs.
You will now need to install MagiskManager 3.0, SafetyNet Helper Sample, PHH Super User APK, Root Browser and Kernel Adiutor.
Step 4:
Flashing MagiskV10.2
You will need to reboot into your custom recovery and flash "Magisk-v10.2.zip", followed by rebooting. If you receive ERROR: 1 in TWRP when it is trying to mount SU, I suggest reflashing a kernel (and re-remove SuperSU), uninstalling Magisk with MagiskUninstaller (in Magisk thread) and reinstall Magisk V10.2, or reinstalling your rom.
Once you have flashed the file, reboot into System and open Magisk Manager to verify you have installed Magisk. A little pop up will open to allow Magisk to have root. Make sure to click allow and set it so it has root for "Forever".
If it states that root isn't properly installed, manually flash PHH Super User V266-2.
Step 5:
Enabling Magisk Hide
In Magisk Manager, go to the side menu and go to "Settings." You will see an unchecked box that says "Enable Magisk Hide." Select it and reboot. Re-open Magisk Manager and verify that it is now check marked. If the App crashes when you select "Enable Magisk Hide", reboot your phone and retry.
Step 6:
Set Permissions
In Root Browser, go to the directory "/sys/fs/selinux" and find the file "enforce" and the file "policy". On the file "enforce", change the permissions of the file from "644" to "640", and for the file "enforce", change the permissions of the file from "444" to "440". If Phh Super User pops up and asks for root access, click "Allow."
Once you are done, open up SafetyNet Helper Sample and it 'should' pass. If you are getting "Response Validation Failed" and the background is blue, uninstall Magisk by flashing Magisk Uninstaller, flash UPDATE-unSU-signed.zip, then reflash Magisk V10.2. Then, go back to Step 5 and enable Magisk Hide.
Step 7:
Use Kernel Adiutor to automatically set permissions in init.d
This last step is 'optional', however it automates the permission setting as every time you reboot your system, the file permissions will reset. Open up Kernel Adiutor, go to the sidebar and scroll down until you see 'Init.d'. Click it and make sure "Emulate Init.d" is enabled.
Then click the plus button, set the name to "Permissions" and then add the following script:
"chmod 640 /sys/fs/selinux/enforce" and "chmod 440 /sys/fs/selinux/policy" and save the files.
Also allow root access to Kernel Adiutor!
Step 8:
Reboot
Reboot your device, let Kernel Adiutor do its countdown (you will see in the notifications drop down) and once it says "Applying settings completed!", open up Safetynet and you should be passing!
Credits:
topjohnwu - Main developer of Magisk and Magisk Supported Phh Super User
This XDA thread - Helped me figure out how to do this bypass in the first place.
CoreUi Telegram Chat - Helped me test this bypass to see if it worked on different S6 models. Join here!
If I forgot to credit anyone, please tell me.
__________________________________​
If there is any mistakes I made, spelling, phrasing etc., please tell me so I can fix it. Thanks.
Click to expand...
Click to collapse
Step 6:
Set Permissions
In Root Browser, go to the directory "/sys/fs/selinux" and find the file "enforce" and the file "policy". On the file "enforce", change the permissions of the file from "644" to "640", and for the file "enforce", change the permissions of the file from "444" to "440". If Phh Super User pops up and asks for root access, click "Allow." Which file gets which perms bud you mention the same file twice.

savvy1968 said:
Step 6:
Set Permissions
In Root Browser, go to the directory "/sys/fs/selinux" and find the file "enforce" and the file "policy". On the file "enforce", change the permissions of the file from "644" to "640", and for the file "enforce", change the permissions of the file from "444" to "440". If Phh Super User pops up and asks for root access, click "Allow." Which file gets which perms bud you mention the same file twice.
Click to expand...
Click to collapse
Yeah I had to change it on my other thread in the GS6 forums. However I'm stopping maintenance of these threads as MagiskHide deals with all that permission stuff automatically now.

Seems to not working on leeco le max 2

[Kernel][6.0/7.0] f2fs-fixed kernel v03

Motorola Stock Kernel with f2fs patched and kcal added
Disclaimer: Your warranty is now void, use at your own risk. YOU are choosing to make these modifications and I am not responsible for any damages these changes might do to your device or sanity.
Why this kernel exists:
As many of you know, there is a bug with the f2fs filesystem in the stock kernel which makes it nearly impossible to use systemless modifications (SuperSU, Magisk) on the Moto Z Play. The flaw and its solution are described here.
I started this project for myself to be able to use systemless modifications again, but I hope some of you will find it useful as well. The kernel for Android 6.0 is based on Motorolas source code release (MPN24.104-44) from here and includes security fixes up to december 2016. The Android 7.0 kernel is based on release MMI-NPN25.137-15 with patch date 2017-01. It has been developed and tested with the European model and ROM, but should work on other variants as well as all retail models share the same boot image.
As of patch level 2017-03, Motorola included the f2fs fix in the official kernel. However, I will continue to work on this kernel for those of you who need the verifiedbootstate patch and kcal.
Warning
This kernel is not meant for 7.1.1 and will break your camera and probably more! Once Motorola release the source code you will find an update here.
Features:
f2fs patched to allow systemless modifications to work
kcal color control
Thats all for now, let me know if you need something else ...
Instructions:
If you previously rooted your phone with the chinese TWRP in system mode I would advise to un-root the phone from the SuperSU app and restore a factory image. However, deleting userdata is not necessary except for the SuperSU app. It might not recognize the new systemless mode otherwise.
Optional, unroot via SuperSU app
Reboot to boatloader / fastboot mode
Flash modified TWRP image Flash @Alberto97 latest TWRP from here
Reboot directly into recovery
Optional, remove forced encryption (see below)
Check with TWRP file manager that /data/.supersu is not present, otherwise delete the file.
Flash kernel zip
Flash SuperSU
Reboot the device
Remove forced encryption (optional):
Download attached RemoveForceEnc.zip
Flash file from TWRP
Wipe userdata (in TWRP or use 'fastboot erase userdata' in fastboot mode)
Credits:
Thanks to @Alberto97 for his work on addison.
Thanks to @erfanoabdi and @ryzion for the RemoveForceEnc.zip found on the Moto Z forum (in this post).
@fortunz for testing kcal functionality
Download:
03/22/2017 - Android 7.0.0 Kernel v03: Mega
03/23/2017 - Android 6.0.1 Kernel v03: Mega
Archive:
Modified TWRP: androidfilehost No longer needed, flash latest TWRP from @Alberto97
02/18/2017 - Android 7.0.0 Kernel v02: androidfilehost, Mirror: Mega
02/02/2017 - Android 6.0.1 Kernel v02-test: androidfilehost
01/28/2017 - Android 6.0.1 Kernel v01: androidfilehost
Sources: Github
Changelog:
03/22/2017 | 6.0.1 / 7.0.0 | v3
Added kcal color control. Patch
02/18/2017 | 7.0.0 | v2
Remove verifiedbootstate flag to pass SafetyNet checks. Patch
02/17/2017 | 7.0.0 | v1
Initial release for 7.0
02/02/2017 | 6.0.1 | v2-test
Test build to pass safetynet checks. Removes verifiedbootstate flag. See this patch
01/28/2017 | 6.0.1 | v1
Initial release based in MPN24.104-44 and security bulletins up to december 2016

Is it just enough to flash the sprasechunks ? Is there any need to delete userdata?

Yeah, system sparsechunks should be enough. Additionally, make sure the file '/data/.supersu' does not exist. There was one guide which required the file to force system mode for supersu.

tomparr said:
Yeah, system sparsechunks should be enough. Additionally, make sure the file '/data/.supersu' does not exist. There was one guide which required the file to force system mode for supersu.
Click to expand...
Click to collapse
Great job, it worked, I flashed the lastest SR3-supersu without any issues:good::good::good:
Ran into a bit of trouble, everything flashed without any issues but when I went into the SuperSU APK " no binary is installed" so it seems even though I did flash the sparsechunks , you may need to delete user data.
I was already rooted with the SuperSU that I extracted from the Chinese TWRP.

flashallthetime said:
Great job, it worked, I flashed the lastest SR3-supersu without any issues:good::good::good:
Ran into a bit of trouble, everything flashed without any issues but when I went into the SuperSU APK " no binary is installed" so it seems even though I did flash the sparsechunks , you may need to delete user data.
I was already rooted with the SuperSU that I extracted from the Chinese TWRP.
Click to expand...
Click to collapse
Thanks for testing. Have you tried to delete SuperSU and its app data and flash SR3 again?

Thanks a lot OP, I've been waiting for something like this. I'll give it a go.

tomparr said:
Thanks for testing. Have you tried to delete SuperSU and its app data and flash SR3 again?
Click to expand...
Click to collapse
No I didn't.
Edit: You need to also re-flash the kernel as well as the sparsechunks. It works and I'm rooted with SR3.
Sent from my XT1635-02 using XDA-Developers Legacy app

Hi I have stock reteu with this version twrp of alberto and root with super his SR3 2.79 is this for me? Thank you
{
"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"
}
regards

So if a install this i finally will be able to install adaway? Cause with the root i have i just cant
Sent from my XT1635-02 using XDA-Developers Legacy app

elgringoloco77 said:
So if a install this i finally will be able to install adaway? Cause with the root i have i just cant
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes, running AdAway (and Titanium Backup) was the main reason I started building the kernel.

iron maiden said:
Hi I have stock reteu with this version twrp of alberto and root with super his SR3 2.79 is this for me? Thank you
regards
Click to expand...
Click to collapse
Depends, if you are ok with system mode root, you don't need this.

tomparr said:
Depends, if you are ok with system mode root, you don't need this.
Click to expand...
Click to collapse
Hello and how can I know that I do not need this? What is the advantage of doing those steps? I do not know if you understand me, I feel my English, thank you.
regards

iron maiden said:
Hello and how can I know that I do not need this? What is the advantage of doing those steps? I do not know if you understand me, I feel my English, thank you.
regards
Click to expand...
Click to collapse
Hi, the advantage of this method is that the /system partition is not modified. This makes OTA updates much easier.

tomparr said:
Hi, the advantage of this method is that the /system partition is not modified. This makes OTA updates much easier.
Click to expand...
Click to collapse
Main advantage is that Magisk is supposed to work, and that f2fs is working properly.
Systemless root already does work fine using phh superuser without this kernel.
To have AdAway functionality - which systemless needs SuperSU or Magisk, both don't work without this kernel - you may use dns66 which does not modify hosts, but instead runs a local DNS server. It has very similar functionality and doesn't even need root.
I'd like to have f2fs working, but currently don't have the time to do backup, restore in twrp doesn't work maybe because of broken f2fs, do 4 times update etc. This kernel probably will help me and I thank you very much for publishing it. We'll see when I find the time to test it.

tomparr said:
Hi, the advantage of this method is that the /system partition is not modified. This makes OTA updates much easier.
Click to expand...
Click to collapse
Hi and what flash of these? Does magisk work to hide root in some applications? Do I have to reinstall the firmware before doing this process?very thanks
Flash SuperSU / Magisk / Systemless modification

iron maiden said:
Hi and what flash of these? Does magisk work to hide root in some applications? Do I have to reinstall the firmware before doing this process?very thanks
Flash SuperSU / Magisk / Systemless modification
Click to expand...
Click to collapse
hello what supersu, magisk and systemless I have to install
I have the house z I have reflated the stock now would be good time to install this system no?

iron maiden said:
hello what supersu, magisk and systemless I have to install
I have the house z I have reflated the stock now would be good time to install this system no?
Click to expand...
Click to collapse
You can use the regular SuperSU and Magisk versions from here and here.

tomparr said:
You can use the regular SuperSU and Magisk versions from here and here.
Click to expand...
Click to collapse
Hi, okay, this system is running smoothly. And that twrp? thank you very much @tomparr
Something has failed? Install magisk 10.2 and sr3-supersu-v2.79 thanks
Unistalled Sr3 v279 and installer phhsupersu
regards

iron maiden said:
Hi, okay, this system is running smoothly. And that twrp? thank you very much @tomparr
Something has failed? Install magisk 10.2 and sr3-supersu-v2.79 thanks
regards
Click to expand...
Click to collapse
Root and Magisk look fine. The SafetyNet test is required for Android Pay and other "secure" apps. From what I read, it can fail on newer versions when the bootloader is
unlocked. I found a temporary patch for the kernel in the OnePlus forum which might solve it. I'll prepare a test version for you soon.

tomparr said:
Root and Magisk look fine. The SafetyNet test is required for Android Pay and other "secure" apps. From what I read, it can fail on newer versions when the bootloader is
unlocked. I found a temporary patch for the kernel in the OnePlus forum which might solve it. I'll prepare a test version for you soon.
Click to expand...
Click to collapse
Hello ok very very thanks for job
regards

Custom firmware for FiiO M6, FiiO M7 and FiiO M9

​Custom firmware for FiiO M6, FiiO M7 and FiiO M9​
Hi everone,
My hobby is modding and building ROMs so now I mod FiiO M6 and M7 firmware.
Why? Now you can install playstore and activate third party players like PowerAmp and Neutron or use streaming apps like Spotify or Tidal.
I hope you will enjoy my ROM
Installer Features
Installing MicroGapps and Playstore to download and activate third-party players (Requires my firmware to work)​
Magisk Installer (Requires my firmware to work)​
Mixplorer (File Manager)​
Dark Theme Installing​
Xpossed Framework Installer​
Optimized Fiio Music App​
Optional Tidal Installing​
My Firmware Features
Improved sound (Editing system configurations, Alsa, Updated SoundLibs)​
Optimized system resources​
Magisk (Root)​
Activated WiFi item in settings​
Updated FiiO Music App​
Fake Signatures support​
Activated Init.d​
Useful build.prop tweaks​
Another Bootanimation​
Changed font to Russia font (Ubuntu + Samsung One)​
And many other improvements​
How to install firmware: Youtube Instructions
M7 Firmware link: M7 Firmware
M6 Firmware link: M6 Firmware
M9 Firmware link: M9 Firmware
If you want to thank me financially:
Bitcoin: 1MeMen1FHZ5iut5KYmdJrQKBgk2e8hts7f
Ethereum: 0x4C90b19a78f19a6fbaA191C58cF0E87751588d3c
PayPal: http://paypal.me/antonixo
QIWI: https://my.qiwi.com/Konstantyn-YFrx47iPqT
Installation Instructions
1. Download my firmware and copy it to sd card
2. Go to recovery by off player and turning it on pressing next track and power if you use M7 or volume down and power for M6.
3. Wipe data using vol+ vol- and power buttons select "Wipe data/factory reset" paragraph
4. Press yes and reboot to recovery.
5. Go "Install update from sd card" and select archive with my firmware.
{
"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"
}
6. Now Aroma installer starts. To controll in aroma installer use combination of pressing Power+Vol+ Power+Vol- and Power.
7. Go next page by using Power+Vol+ and select any paragraph you need.
8. Power+Vol+ to start installation.
9. After installation press power and reboot to the system (First loading will take about 3-7 minutes)
FAQ​A: Player becomes laggy!
B: I cannot fix bad processor of FiiO M7. Lags because you start use player another way. You update FiiO Music, install Playstore. Apps require more performance hardware. Try reinstall with old FiiO Music and without Gapps
A: How to go back to original firmware
B: You can easily go back flashing stock rom for FiiO M7 from here - M7 Firmware or for fiio M6 from here - M6 Firmware. Just flash it from recovery like my firmware
A: Why, when entering Magisk, there is a notification about an additional installation?
B: Since the magisk was installed "by hand", he did not unpack the files he needed to the Data section. To fix the problem without the module and install this module
A: Why is there only only my language in the keyboard?
B: Settings - Language & input - Virtual keyboard - Simple keyboard - Language
Uncheck the system languages and put them in the languages you need
A: Stuck on logo/bootloop!
B: Hold the power and pause button, after the screen turns off, press the button down, in recovery, select Wipe data.

Thanks for this, though I've been meaning around with it, magisk doesn't provide proper root, no root apps request and get granted root ever. Am I missing something?

Mentalmuso said:
Thanks for this, though I've been meaning around with it, magisk doesn't provide proper root, no root apps request and get granted root ever. Am I missing something?
Click to expand...
Click to collapse
Did you select magisk app in installer? You have M6 or M7?

tried this on a m9 and no luck im afraid, just stuck at the fiio logo on bootup, left for 30 mins, rebooted to recovery and wiped data again, left for an hour and no difference.

AntonIXO said:
Did you select magisk app in installer? You have M6 or M7?
Click to expand...
Click to collapse
M6, it seems userdata doesn't mount so the magisk data files don't install. You have the correct platform etc for mounting, but I'm not sure why it fails. Otherwise it all works great.

dubsflyt said:
tried this on a m9 and no luck im afraid, just stuck at the fiio logo on bootup, left for 30 mins, rebooted to recovery and wiped data again, left for an hour and no difference.
Click to expand...
Click to collapse
Flash stock firmware through recovery

AntonIXO said:
Flash stock firmware through recovery
Click to expand...
Click to collapse
Yeah sorry should have said, got it working again by flashing stock, but this rom didnt work unfortunately, happy to test again if you release another build or something

dubsflyt said:
Yeah sorry should have said, got it working again by flashing stock, but this rom didnt work unfortunately, happy to test again if you release another build or something
Click to expand...
Click to collapse
I've update rom. Try again.

cannot make it work even with new update:-(

unfortunately same result with the new update on the m9

any news?

installed on my M6 working great, the only thing I cant get working is magisk, I read above about the module zip but can't understand how to install it, apart from that everything is perfect, keep up the great work.

Paris333 said:
installed on my M6 working great, the only thing I cant get working is magisk, I read above about the module zip but can't understand how to install it, apart from that everything is perfect, keep up the great work.
Click to expand...
Click to collapse
Go to magisk, press cancel in window and install module from module menu

Please please update for m9...

Any news ?

m9 업데이트 해주세요 ... 제발 ..

Just tried today's version but it dows not install.
after installing statrs after 2 or 3 seconds it reboots

I seem to have the same issue as Mentalmuso and Paris333; Magisk isn't giving out root permissions on the M6. When I try to flash module.zip via the modules tab in the magisk manager app I get:
Code:
! Unsupported/Unknown image format
! Installation failed
The magisk debug log is only full of:
Code:
su: request from pid={XXXXX}
su: request from uid={XXXXX}
su: request rejected (XXXXX)
for all of the root applications I tried to test it with
but when I go to the "superuser" tab it aggravatingly says "No app has asked for superuser permission yet."
My magisk app is the default non-updated version installed via the proshi_m6_en aroma installer. I did do full factory reset via the debug menu and followed all instructions, so the installation is very clean. Everything that doesn't need root works perfectly fine, xposed even shows up as active. I've tried a few things, like updating to the new v22 magisk app via the v22 magisk manager, but I always just run into the same boot.img unsupported error as above. Maybe I've missed something, let me know if you need anything tested, as I do have a few M6 to play around with that I don't mind bricking.
On an unrelated note: your paypal says you are not accepting payments.

Admiral_Face said:
I seem to have the same issue as Mentalmuso and Paris333; Magisk isn't giving out root permissions on the M6. When I try to flash module.zip via the modules tab in the magisk manager app I get:
Code:
! Unsupported/Unknown image format
! Installation failed
The magisk debug log is only full of:
Code:
su: request from pid={XXXXX}
su: request from uid={XXXXX}
su: request rejected (XXXXX)
for all of the root applications I tried to test it with
but when I go to the "superuser" tab it aggravatingly says "No app has asked for superuser permission yet."
My magisk app is the default non-updated version installed via the proshi_m6_en aroma installer. I did do full factory reset via the debug menu and followed all instructions, so the installation is very clean. Everything that doesn't need root works perfectly fine, xposed even shows up as active. I've tried a few things, like updating to the new v22 magisk app via the v22 magisk manager, but I always just run into the same boot.img unsupported error as above. Maybe I've missed something, let me know if you need anything tested, as I do have a few M6 to play around with that I don't mind bricking.
On an unrelated note: your paypal says you are not accepting payments.
Click to expand...
Click to collapse
try installing magisk manager v7.5.1 , im using that one with success. Getting root access now. I think half of it is actually the super lag we are getting with having play store, i have put together a very stripped down version of the stock firmware, removed a load of useless apps that all take up precious ram. I am simply downloading my preferred streaming app (deezer) and a couple of other useful apps (terminal, root explorer, magisk manager) and storing them all on my ext sdcard to install after clean install. I seem to be having a pretty fluid experience now.

anyone can fix da M9 file? it does not install any file to the device...

[ROM] Samsung Galaxy J8 Debloated+Rooted Stock Rom v7.1 - J810F/G/M/Y/GF - j8y18lte

{
"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"
}
YOU ARE THE SOLE RESPONSINLE FOR WHAT HAPPENS TO YOUR DEVICE. PROCEED WITH CAUTION!​
Hi all! I should have posted this years ago but anyways... This rom is made due to the fact that there is no bug-free rom for Galaxy J8, not even any development going on. So, I decided to de-bloat the latest stock firmware, polish it a bit, configure some settings and fix some of the issues.
Twrp and Root Guide: https://forum.xda-developers.com/t/...d-flash-twrp-j810f-g-m-y-gf-j8y18lte.4479201/
WORKING
Everything that works on stock rom, including VOLTE.​
NOT WORKING
Nothing.
CHANGELOG
Read the "!!! READ ME FIRST !!!" text inside the Google Drive folder.
BLOATWARE LIST
Read the "More Info About Bloatwares" pdf file inside the Google Drive folder.
INSTRUCTIONS​HOW TO MAKE A CLEAN INSTALLATION (WARNING! YOU WILL LOSE ALL YOUR DATA INCLUDING INTERNAL STORAGE -pictures, songs, downloads, files, apps etc.-)
1. Install/Update TWRP (use v3.5.0) (big thanks go to goldfish07)
2. Create backup, INCLUDING VENDOR (everything you need - including your files in internal storage - use an external storage if possible)
3. Reboot into TWRP. Navigate to Wipe/Format Data type yes and apply it. Then, go to Wipe-Advanced Wipe, select ONLY these "Dalvik/Art Cache - System - Vendor - Data - Cache" and format them.
4. Copy "J8_De-Bloated_Stock_Rom_v7.1.zip" to your internal or external storage and flash it.
5. Reboot and enjoy! (it might say "NO OS INSTALLED", it is normal when you format system from advanced wipe and then install the zip, just swipe and system will start) (first boot may take a couple of minutes, please be patient, YOU WILL ONLY SEE THE "SAMSUNG LOGO", NOT the animation and it is NORMAL)
HOW TO MAKE A DIRTY INSTALLATION (ONLY IF YOU ARE COMING FROM ANOTHER VERSION OF DEBLOATED ROM) (YOU WILL NOT LOSE ANY DATA)
1. Open "J8_De-Bloated_Stock_Rom_v7.1.zip" using the latest version of "WinRAR" on pc or the latest version of "RAR" on Android.
2. Go inside the "data" folder and delete the 3 folders (adb, app, system). Do not delete the "local" folder.
3. Copy the "J8_De-Bloated_Stock_Rom_v7.1.zip" to your phone.
4. Reboot into TWRP.
5. Flash the "J8_De-Bloated_Stock_Rom_v7.1.zip".
6. When installation completes, select "Wipe cache/dalvik" and swipe.
7. Reboot and enjoy!
Contributors
goldfish07 (Ayush Bisht) for anykernel and TWRP
Kernel Source (thanks to goldfish07 (Ayush Bisht))
GitHub - goldfish07/android_kernel_samsung_j8y18lte: base: LA.UM.8.6.r1-04700-89xx.0
base: LA.UM.8.6.r1-04700-89xx.0. Contribute to goldfish07/android_kernel_samsung_j8y18lte development by creating an account on GitHub.
github.com
ROM INFO:
Security Patch Level2021-12-01OS VersionAndroid 10PDAJ810FJXU6CVA1
Download: https://tinyurl.com/J8-Debloated-Rom

Reserved

New Update v7.1!
Read the "!!! READ ME FIRST !!!" text inside the Google Drive folder for changelog details.

BNFCTR said:
New Update v7.1!
Read the "!!! READ ME FIRST !!!" text inside the Google Drive folder for changelog details.
Click to expand...
Click to collapse
Hi, thank you firstly.
I installed this rom everythink is ok but no internet connection.
Any solution?

sinanlenfom said:
Hi, thank you firstly.
I installed this rom everythink is ok but no internet connection.
Any solution?
Click to expand...
Click to collapse
Please follow the clean installation steps carefully.

Hi bro thank you so much this rom work perfectly everything work thanks a lot

Download link (https://tinyurl.com/J8-Debloated-Rom) is not working ((
Who can share it?

there is a way to make a ROM to make the touch work, I have a j810m and the touch stopped after updating to Android 10 binary 3 version, I had changed the display and I didn't know I couldn't update

Cheat said:
Download link (https://tinyurl.com/J8-Debloated-Rom) is not working ((
Who can share it?
Click to expand...
Click to collapse
The link is working. Please try using another browser or use vpn.

jabsjrm said:
there is a way to make a ROM to make the touch work, I have a j810m and the touch stopped after updating to Android 10 binary 3 version, I had changed the display and I didn't know I couldn't update
Click to expand...
Click to collapse
While system update check, it also verifies your display originality. If you change your display on untouched stock rom, it will be permanently disabled unfortunately. You should have upgraded to debloated rom or disabled system update apps so that you could keep using changed display. There is no luck fortunately. (you cannot downgrade to Android 9 to solve the issue because bootloader does not allow that)

This and the "More info about bloatwares" is great, thanks for all your efforts. The device is finally usable without stutter even when scrolling.
But there is a small thing -> I think you should remove default magisk so that it can be installed with app and be able to update.

erfto said:
This and the "More info about bloatwares" is great, thanks for all your efforts. The device is finally usable without stutter even when scrolling.
But there is a small thing -> I think you should remove default magisk so that it can be installed with app and be able to update.
Click to expand...
Click to collapse
You're welcome. I configured some of the Magisk settings so that you do not need to do anything so as to be able to successfully pass SafetyNet. Additionally, If I remove default installation of Magisk as an app, stub app will give you error while downloading the app unfortunately. Lastly, Magisk v24.3 is the latest working version for J8. Magisk v25.x versions will bootloop the device. Therefore, do not attempt to update Magisk. Considering these issues, I decided to include Magisk and its configurations. If you still want to remove it, open "J8_De-Bloated_Stock_Rom_v7.1.zip" using the latest version of "WinRAR" on pc or the latest version of "RAR" on Android. Go inside the "data" folder and delete the 2 folders (adb, app). Then flash the .zip.

BNFCTR said:
You're welcome. I configured some of the Magisk settings so that you do not need to do anything so as to be able to successfully pass SafetyNet. Additionally, If I remove default installation of Magisk as an app, stub app will give you error while downloading the app unfortunately. Lastly, Magisk v24.3 is the latest working version for J8. Magisk v25.x versions will bootloop the device. Therefore, do not attempt to update Magisk. Considering these issues, I decided to include Magisk and its configurations. If you still want to remove it, open "J8_De-Bloated_Stock_Rom_v7.1.zip" using the latest version of "WinRAR" on pc or the latest version of "RAR" on Android. Go inside the "data" folder and delete the 2 folders (adb, app). Then flash the .zip.
Click to expand...
Click to collapse
I'm not knowledgable about this but i get it now, thanks for informing !

where i can get non root (magisk) boot.img
i want to uninstall magisk from this rom.
thank you so much dev

X - root said:
where i can get non root (magisk) boot.img
i want to uninstall magisk from this rom.
thank you so much dev
Click to expand...
Click to collapse
just do what was posted above?
BNFCTR said:
... SNIP ... If you still want to remove it, open "J8_De-Bloated_Stock_Rom_v7.1.zip" using the latest version of "WinRAR" on pc or the latest version of "RAR" on Android. Go inside the "data" folder and delete the 2 folders (adb, app). Then flash the .zip.
Click to expand...
Click to collapse

Where are people getting TWRP from? I can't see it listed for the J8 on their website: https://twrp.me/Devices/Samsung/
There's an unofficial one here:
[RECOVERY] TWRP 3.6.x.x for Samsung Galaxy J810G/GF/F/M/Y j8y18lte
TWRP 3.6.x.x for Samsung Galaxy J8 Note: I AM NOT RESPONSIBLE OF ANY DAMAGE WILL HAPPEN AFTER YOU FLASH THIS TWRP , ALWAYS DO BACKUP FIRST DOWNLOAD MODE 1. power off your Samsung J8/On8 2. press & hold both vol+ & vol- keys and insert USB driver...
forum.xda-developers.com

Bro i need galaxy theme is there any solution ?

X - root said:
where i can get non root (magisk) boot.img
i want to uninstall magisk from this rom.
thank you so much dev
Click to expand...
Click to collapse
You can uninstall it from Magisk homepage "Uninstall Magisk". The system may not boot without Magisk. Keep this in mind.

Canyoning.cat said:
Where are people getting TWRP from? I can't see it listed for the J8 on their website: https://twrp.me/Devices/Samsung/
There's an unofficial one here:
[RECOVERY] TWRP 3.6.x.x for Samsung Galaxy J810G/GF/F/M/Y j8y18lte
TWRP 3.6.x.x for Samsung Galaxy J8 Note: I AM NOT RESPONSIBLE OF ANY DAMAGE WILL HAPPEN AFTER YOU FLASH THIS TWRP , ALWAYS DO BACKUP FIRST DOWNLOAD MODE 1. power off your Samsung J8/On8 2. press & hold both vol+ & vol- keys and insert USB driver...
forum.xda-developers.com
Click to expand...
Click to collapse
Here: https://forum.xda-developers.com/t/...d-flash-twrp-j810f-g-m-y-gf-j8y18lte.4479201/

Kevin Ackerman said:
Bro i need galaxy theme is there any solution ?
Click to expand...
Click to collapse
Download the necessary apps from "Deleted Apps" folder inside the Google Drive folder and copy them to corresponding folder and reboot.