Database Info

[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

[ROM][7.1.2] AOKP Nougat with built in side bar! [tbltetmo][tbltecan]

{
"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"
}
To God be the glory, my AOKP NOUGAT project finally works!
My fellow T-Mobile-ians, you have been left out of AOSP development long enough! By God's grace I was able to use mickey387's great tbltexx work, and completely adapt it to our tbltetmo after extracting all of the needed firmware from our 6.0.1 stock roms! No data zips are required here! It is all built in!
This is not a dirty unicorn. This is the original unicorn, the AOKP. Now made out of Nougat! That's right, all of the AOKP stuff you love, plus LineageOS, plus a built in side bar, and more! All wrapped up into one! With tons of settings from status bar tweaks to button remaps, it's all here and ready to rumble!
Click to expand...
Click to collapse
**** This is an UNOFFICIAL ROM. Install at your own risk! ****
You must be on a 6.0.1 Bootloader with a 6.0.1 modem! I suggest if you are unsure, flash stock 6.0.1, then install this ROM!
Downloads :
THE AKLU KERNEL CAN BE DOWNLOADED HERE (OPTIONAL - BUT DOES FIX WIFI HOT SPOT ISSUE) :
https://forum.xda-developers.com/no...droid-development/kernel-aklu-kernel-t3558419
Download:
http://www.mediafire.com/file/4ebke9zgq6i76wo/aokp_tbltetmo_nougat_unofficial_2017-05-01_1117.zip
OLD DOWNLOAD:
https://www.mediafire.com/download/cpa96oxnyavaot8
Gapps link:
http://opengapps.org/
-Which I personally tested Arm 7.0 Nano.
No data fix zip is required for T-Mobile phones! This ROM is actually built for the T-Mobile variants (tbltetmo, tbltecan)!
Be sure to follow these installation steps very carefully, as they may be different then what you are used to.
Installation instructions:
-Put your phone on the 6.0.1 Bootloader and Modem
-Download ROM and gapps, and put them on your phone or external storage.
-Reboot into recovery mode - TWRP (I personally installed this using Mickey's 3.0.0-0).
-Backup what you had. (Just to be safe.)
-Wipe. (I personally wipe everything prior to flashing new roms, but at least do the basic wipe.)
-Install Rom.
-Install Gapps. - Optional
-Reboot to system and enjoy!
I do not recommend installing superSU on this ROM! SU permission is already built in, and superSU has been causing problems with the rom. Please read the thread for further details.
What works :
Code:
+ Phone calls/receiving
+ Data 2g/3g/LTE
+ Bluetooth
+ WiFi
+ MTP
+ GPS/Glonass
+ S PEN
+ Split screen
+ The WiFi hotspot does work with the AKLU kernel!
etc....
What doesn't :
Code:
- The edge panel is not implemented at this time. The screen wraps around the edge. But there is an app bar feature under ROM CONTROLS!
- The capacitive buttons work, but do not illuminate.
- The WiFi hotspot does not work with the stock kernel, it does work with the AKLU kernel!
- Fingerprint sensor is really flaky. I got it to work once, but only once. Most times it will not register.
- I have not found any big errors, fault crashes, or problems yet. Please let me know if you find an issue!
This AOKP N ROM was built for the tbltetmo, the T-Mobile Samsung Galaxy Note Edge. I have not tried this on any other device, but you are welcome to try it AT YOUR OWN RISK. You will need to edit the META-INF updater script to accomplish this.
Code:
Disclaimer: AOKP is not responsible for any damages to your device.
All of my work is completely available for any who wish to use or modify it. I didn't make AOKP, the device trees, or vendor blobs. I simply used and edited existing material. A huge thanks should go to those who actually created this stuff.
AOKP XDA Forum: http://forum.xda-developers.com/aokp
Source Code: https://github.com/AOKP
Official website: http://aokp.co/
Device trees: https://github.com/alaskalinuxuser/
ROM OS Version: 7.1.2 Marshmallow
ROM Kernel: Linux 3.10.40
Based On: LineageOS and PA, and AOSP.
Created 2017-02-16
Last Updated 2017-05-02
Change log:
Code:
20170501
+ Edited camera settings to help with third party apps that use the camera.
20170428
+ Fixed recent button.
20170427
+ Synced with AOKP source!
--> Security update to April 5th, 2017
--> New battery icon options.
--> New powermenu torch option.
--> Long press hotspot tile to go to hotspot settings.
+ Added kexec hardboot to both default and AKLU kernels to allow this to work with multirom.
+ Borrowed from mickey to fix the notification led lights for proper color display.
20170316
+ Synced with AOKP source!
--> Security update to March 5th, 2017
--> Numerous AOKP fixes for the ROM itself. See the change-log under Rom control.
+ Added in possible VOIP fix for voip app problems.
20170301
+ Synced with AOKP source!
--> Merged with Android 7.1.1_r21
--> Added PIE controls
--> Security patches updated to Feb 5, 2017
--> Now FULLY supports OMS/SUBSTRATUM
+ Screenshot issue fixed
+ SDcard read from File Manager fixed
20170217:
-Fixed WiFi hot spot issue with AKLU kernel, but must be downloaded from the kernel thread.
20170216:
-First build release.
-Built with AOKP 7.1.1 source
-Added Kernel Adiutor and Omni-Switcher

Thanks!
A huge thanks to the Android Open Kang Project team!
@OldDroid
 @Mickey387
@deadman96385
And all of these great testers (some for other devices, not all helped me test this rom, but helped me test the Note Edge in general, as well as provided valuable feedback!) :
@Aaren11
@xNNism
@beany23
@swecon
@1freedude
@lostinlife33
@faizan'
@gavin10
@brainwasher01
@hosny1964
@xcube1

Features and Screenshots!
Features and Screenshots!
- Advanced Reboot
- Omni-Switcher
- Kernel Adiutor
+ Rom Control:
+ App Launchers
- App Circle Bar
- App Side Bar
- Gesture Anywhere
+ General
- cLock settings
- Recents settings
- Wakelock Blocker
+ Hardware Keys
- Backlight control
- Power button options
- Launch vibration control
- Home button controls
- Recents button controls
- Long press options, double tap options
- Kill app back button option
- Volume buttons wake
- Volume button playback controls
- Keyboard cursor controls
- Volume button reorientation
- IME features
+ Lockscreen
- Media Cover art
- Display music visualizer
- Show weather
- Blur background
- Fingerprint auth vibration
- Double tap to sleep (DT2S)
- Disable quick settings
- Show lockscreen clock and date
- Lockscreen notification count
+ Notification Drawer
- Brightness slider
- Brightness icon
- Rows in portrait and landscape modes
- Columns
- Tile Animations
- Advanced data tile
- Smart pulldown
- Quick pulldown
+ Power Menu
- Animation choices
- Screenshots
- Screenrecord
- Airplane mode
- Sound Panel
+ Sound
- Various sound settings
- Volumn step control
+ Status Bar tweaks
- Network traffic
- Clock style
- Double tap to sleep (DT2S)
- Superuser indicator
- Icon controls
- AOKP logo
+ User interface
- Toast controls
- AOKP animations
- Transparency controls
AND MORE!!!

Notes.
A place for rom notes....
Background image:
https://qlfiles.net/2017/01/07/upload-fractal-images/
The background images that I used in this ROM came from the Quiet Learner. You should check out his mathematical artwork, including 3D mandelbox images!
If the screen looks red-ish, check the settings->display->live display options, you may want to turn them off, it is a low light sensitive display option.
T-Mobile users with device model = unknown:
If you are using a N915T (like myself), the fix is very easy!
-Open /system/build.prop in any text editor
-Anywhere in the file, add this line:
Code:
ro.build.model=SM-N915T
Save and exit, then reboot your phone. You can check "about phone" under settings, you should see yourself as SM-N915T, and apps like XDA should report you as Samsung Galaxy Note Edge.
Apps:
Swiftkey Keyboard - This keyboard can be set so the keyboard does not wrap around the screen.
https://play.google.com/store/apps/details?id=com.touchtype.swiftkey
Spen Command - This app cost a few dollars, but enables the Spen to be somewhat smart again, rather than just a pointer stick.
http://www.emandt.net/Android/SPenCommand/Website/
If you find something else that will help other users, please let me know by posting in the thread!

Hey everyone!
The AKLU kernel is online for the AOKP 7.1.1 Nougat rom! It fixes the WiFi hot spot issue!
https://forum.xda-developers.com/no...droid-development/kernel-aklu-kernel-t3558419
20170217
- Fix WiFi hot spot error for Nougat.
- Overclocked the GPU from 600MHz to 633MHz
- Overclocked the CPU from 2649MHz to 2688MHz
- Added governors: Bioshock, Lionheart, Nightmare, Darkness
- Removed input boost, use cpu boost instead
- Added I/O schedulers: FIOPS, ZEN

Would this work in a ATT version if I replace the modem.bin component? Any possibility of damage to try it?

spoiledsport said:
Would this work in a ATT version if I replace the modem.bin component? Any possibility of damage to try it?
Click to expand...
Click to collapse
Spoiledsport,
That is a great question.
Most AT&T phones have a locked boot loader, do they not? If you have an unlocked boot loader than it is possible to try, and no damage should arise. But if you have a locked boot loader it will fail to flash.
If you get it to flash, I do not know if it will work or not.
This ROM is flashed through TWRP, there is no modem.bin file in it, it doesn't over write the modem file.
Hope that helps!

Thank you for this. Will flash it and the kernel shortly.

Awsome rom. Using since last night absolutely great. Just fingerprint having issue other than that great work...

JeremySS said:
Thank you for this. Will flash it and the kernel shortly.
Click to expand...
Click to collapse
Syed husaain said:
Awsome rom. Using since last night absolutely great. Just fingerprint having issue other than that great work...
Click to expand...
Click to collapse
Thank you for the kind words!

?Hey something is wrong with this ROM for some reason SU Binary is not stable and I can't change SELINUX to PERMISSIVE. So I it won't allow me to change it is there a fix for this I try updating Super SU Binary on Recovery and still doesn't work please fix and am runny 6.0.1 Boot and Modem N915T how cant I fix this for some reason it says not root detected please fix

miguelr4720 said:
?Hey something is wrong with this ROM for some reason SU Binary is not stable and I can't change SELINUX to PERMISSIVE. So I it won't allow me to change it is there a fix for this I try updating Super SU Binary on Recovery and still doesn't work please fix and am runny 6.0.1 Boot and Modem N915T how cant I fix this for some reason it says not root detected please fix
Click to expand...
Click to collapse
Miguelr4720,
You should not install super su on this rom. It has a built in root and controller.
Hope that helps.

Loaded up and so far is running smooth with the exception of some weirdness around the back and recent apps hw buttons. They seem to be acting properly but are not lighting up. I went into ROM control and tried to adjust. Interestingly when I have the screen open for adjusting time on they do light up, but then go black again after closing the adjustment box. There is also no vibration when hitting those 2 buttons. Im not getting anything useful in the logs that I can see. I tried reflashing but no change in behavior. Any suggestions? Am I the only one seeing this?
I'll post this in the International thread too in case it is effecting other models.

By the way, this rom supports substratum in legacy mode.
I tested the inversion ui theme successfully.

ROM: aokp_tbltetmo_nougat_unofficial_2017-02-16_1258.zip
Yea I Dont Know What is Causing this problem the SU Binary is not Install Propertly on You Rom
And I Also Install Your Kernel and The Issue With SU Binary not Detected still Persist And I Still Cant Fix It And You Told Me Not Install SR3-SuperSU-v2.79-SR3-20170114223742.zip So I Have not and the problem still Occurred.
still cant change SELinuxModeChanger to PERMISSIVE.
1. Viper4Android FX Driver Wont Install??
2. Cant View Files on The SD Card On File Manager?
3 .SELinuxModeChanger Wont Work Says Root Not Detected?
Please Test This Problem on Your Side and Leet Me Know if there a New Fix For This.
Or Instruction On How to Install This Rom Correctly on N915T I Have Try all the Method on your Page And Still SU Not Install Property. other Thing Like Grant And Denied is the only thing that works on SuperSU
There Has To Be A Fix For This i dont Understand SuperSU WORKS Grant and Denied
and other things are saying that root is not detected really i dont understand.
I Never Had Seen a Problem Like This Before on the Last Rom 6.0.1 aokp room i never had this issue your Check the Rom Image to see if SU Binary are fully install Correctly on the new rom aokp_tbltetmo_nougat_unofficial_2017.
i try everything i try Re-flashing the Phone On Odin Using The 6.0.1 N915T Image and Re-Root and erase system data factory reset and i am still having the issue with some tools Root Not Installed?

miguelr4720 said:
ROM: aokp_tbltetmo_nougat_unofficial_2017-02-16_1258.zip
Yea I Dont Know What is Causing this problem the SU Binary is not Install Propertly on You Rom
And I Also Install Your Kernel and The Issue With SU Binary not Detected still Persist And I Still Cant Fix It And You Told Me Not Install SR3-SuperSU-v2.79-SR3-20170114223742.zip So I Have not and the problem still Occurred.
still cant change SELinuxModeChanger to PERMISSIVE.
1. Viper4Android FX Driver Wont Install??
2. Cant View Files on The SD Card On File Manager?
3 .SELinuxModeChanger Wont Work Says Root Not Detected?
Please Test This Problem on Your Side and Leet Me Know if there a New Fix For This.
Or Instruction On How to Install This Rom Correctly on N915T I Have Try all the Method on your Page And Still SU Not Install Property. other Thing Like Grant And Denied is the only thing that works on SuperSU
There Has To Be A Fix For This i dont Understand SuperSU WORKS Grant and Denied
and other things are saying that root is not detected really i dont understand.
I Never Had Seen a Problem Like This Before on the Last Rom 6.0.1 aokp room i never had this issue your Check the Rom Image to see if SU Binary are fully install Correctly on the new rom aokp_tbltetmo_nougat_unofficial_2017.
i try everything i try Re-flashing the Phone On Odin Using The 6.0.1 N915T Image and Re-Root and erase system data factory reset and i am still having the issue with some tools Root Not Installed?
Click to expand...
Click to collapse
Miguelr4720,
You should not install SuperSU, because the rom already has root permutation built in.
1. I do not support v4a, but you are welcome to mess with it.
https://forum.xda-developers.com/showthread.php?t=2191223&page=2497
According to the official v4a thread, others cannot get it to work on nougat with SuperSU. PLEASE DIRECT ALL V4A QUESTIONS TO THE OFFICIAL V4A THREAD.
2. Thanks for pointing that out. I see that the built in file manager does not let you look at the SD card. I use the amaze file manager, you can use another manager, until I can fix it.
3. I do not understand the problem. The kernel I made is already selinux permissive. Do you want to set it to enforce instead?

Thank You for Understanding and for finding the fix for it
Thank you for leeting me know and hope you fix soon.? your rom Mr Aka i hope you fix soon the room is really nice I love it and I give you good credits leet me know when its ready and more Stable to be use. your room looks nice and greet on 7.1.1 and i really like it and I love it... SO I WIIL Remain On The OEM stock software rooted I have the backup files from my Original Rom and su bunary are not install on my System i have mine Permit running. Everything works good on mine SuperSU app work and opens. So mine is working OK please leet me know when its ready i love the rom. Am also a fan Dirty Unicorn i love the unlock custom rom running on the latest software 7.0.1 I love the room
Everything works good on mine so I wait and am also running x posed on my System and it works and
Main thing X-posed Dev its working on 7.1.1 framework and he expected to lunch the tool in May Or June
And x posed it's not available 7.1.1 sad hope they fix thanks for doing a greet job and I give you good credits for this new akop custom rom I love it leet me know when the room Becomes a little Better We can be a good Team
X-posed frame-work. .
Viper Works too
DOLBY WORKS.
Thank you for leeting me know when its ready leet me know when is coming. When it becomes more stable to use I can wait for 7.1.1 version to work and become avaliable. With the fix and Also I See its running on beta now so I guess it will take you sever all hours and time. leet me know when is its fix
And have a more stablet rom beta Thank You
T-Mobile N915T Root New York City thank you. Good Credits Good Work

Follow up... After an indeterminate time the back button stops working all together and requires a reboot.

There Are Bugs On The Betta I Dont Recommend to use
JeremySS;71120910]Follow up... After an indeterminate time the back button stops working all together and requires a reboot.
Miguel Rodriguez
Yea there are several bugs on this room and he expecting a fix soon please be patient have you FOUND ANY Fixes For The Room i see you a High Senior???

JeremySS said:
Follow up... After an indeterminate time the back button stops working all together and requires a reboot.
Click to expand...
Click to collapse
Great feedback. I haven't noticed that problem myself, but I reboot frequently. Can you do me a huge favor? When the back button stops working, can you immediately try it 5 times, then pull a log cat and send it to me? Thanks, then I can see the problem.

Software Development [CLOSED] [ROM] [CUSTOM] [INTEL JOYING] GTX joying ROM V9a3 2018-04-22

========================================ACHTUNG===================
=================WARNING==========================================
=====================================================PELIGRO=======
AS WITH ANY UNSUPPORTED SYSTEM MODIFICATIONS, USING THIS MAY LEAD TO A BRICK
IF YOU DON'T KNOW WHAT YOU ARE DOING ( HAVEN'T BRICKED MY SYSTEM YET! ) PLEASE
BE AWARE THAT NO ONE ON THE INTERNET IS RESPONSIBLE FOR ANY DAMAGE TO YOUR
UNIT. ANY PROBLEMS WILL BE CONSIDERED ACTS OF WHATEVER GOD YOU BELIEVE IN.
======PELIGRO=======================================================
================================WARNING============================
===ACHTUNG=========================================================
For FYT SoM (5009/6011/6021/6022/6023) based JOYING / Intel SoFIA units ONLY!
Hello, here is a custom rom based on the SYU Stock Build [sofia3gr_car_64-userdebug 6.0.1 MMB29M eng.bsp.20180110.181524 release-keys]
Your Head Unit MUST ALREADY BE ROOTED! You must be able to obtain Super User access within Android!
Due to Bluetooth, WiFi, and as well as nvram patches in the ROM and bootloader, you must be running Joying 6.0 firmware dated 2017_12_15 or later to install this ROM.
Why this ROM? Simple answer: It's makes your Head Unit faster than running the stock ROM's, has updated Google Apps, and has the bloat removed! It's pre-rooted also!
INSTALLATION INSTRUCTIONS:
Step 1: Unzip the contents to the root of your USB flash drive on your computer, then plug the flash drive into the Joying unit via USB.
Step 2. Use the Android helper application "custom" to install. Download from link below, either on the Head Unit itself, OR on PC and transfer using ADB. Once installed, open the program, and grant superuser privileges when prompted, you'll be presented with screen as here:
{
"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"
}
Step 3: Click INSTALL CUSTOM. Wait for output to say recovery successfully installed!
If you wish to preserve your /data, AKA dirty-flash, click on "Do not wipe data" at this point to prevent your data partition from being wiped.
ALL EXISTING DATA ON UNIT WILL BE ERASED. THIS IS A CLEAN INSTALLATION!
Step 4: click REBOOT TO INSTALL GTX ROM - Your Joying unit will reboot, and installation will automatically proceed through TWRP.
(NOTE! The ROM automatically re-installs stock recovery during installation, so if something goes wrong, you can always restore to the original JOYING firmware.)
Recovery options:
RESTORE STOCK - Restores the original stock recovery
INSTALL CUSTOM - Installs superdave's custom recovery (needed to install this ROM)
VERIFY RECOVERY - tells you which recovery you have installed
Rom Utilities:
(all options on this menu work only if you have custom recovery installed)
"Do Not Wipe Data" Switch - enable this to prevent your /data partition from being wiped when installing the ROM. (Your results may vary. Works for me!)
REBOOT TO TWRP - Reboots to TWRP home screen allowing you to do things
INSTALL GTX ROM- installs joying_gtx stock rom from installation media
Exit - exit custom
Code:
====Includes====
xposed v87 x86
open gapps x86 Nano Feb 2018
ViPER4ANDROID FX
precompiled dalvik cache (first boot 2 minutes)
enabled eth0 at boot at 192.168.65.100 for debugging
ADB enabled
SeSuperuser built-in
Included [custom] app to manage superdavex's custom recovery for easy installation and maintenance
RightCamera (front cam app) modified APK
AOSP android boot animation
Interactive cpu governor:
go_highspeed_load set at 70% CPU load
titanium backup
nova launcher
GVC CallHandler 4 Joying
Amaze File Manager
Xposed modules:
boot manager
gravitybox
no overlay warning
immsersive mode forcer
app settings
fake wifi
GPSSpeedFix
======Removed======
[I]Debug Services:[/I]
usbactive
sqldebug
pekallfmrserver
watchdog
ap_logfs
apk_logfs
log-watch
crashlogd
adbusbmuxd
adbec
bootwatcher
shcmd
fmd
[I]Removed Apps:
[/I]
BasicDreams
BluetoothMidiService
Exchange2
Galaxy4
HoloSpiralWallpaper
LiveWallpapers
LiveWallpapersPicker
NoiseField
OpenWnn
PhaseBeam
PrintSpooler
GooglePinyinIME
RKUpdateService
CaptivePortalLogin
WAPPushManager
[I]removed from /system-priv-app
[/I]ManagedProvisioning
CallLogBackup
OemTelephonyApp
DeviceTest
StressTest
WallpaperCropper
GoogleFeedback
ProxyHandler
CellBroadcastReceiver
[I]Removed FYT APPS[/I] ( these slow the system down considerably, even when not in use )
SYU-1-C9-Calculator-V1.0
Sofia-1-C9-TV-V1.0
JY-1-C9-Video-V1.0
JY-1-C9-TimeWeather-V1.0
SYU-1-FileManager-V1.0
SYU-1-C9-Update-V1.0
Sofia-1-C9-ExDvr-V1.0
SYU-1-C5009-DVR-V1.0
Sofia-1-C9-Gallery-V1.0
JY-1-C9-MUSIC-V1.0
ZBox
note, this is a test release intended for developer users only. no support other than this post is offered. A final version will follow soon once initial testing has been completed.
Download Links
Installer ( unzip, this will help you install the ROM on a STOCK, un-rooted Head Unit ) :
xxxxx Mod Edit
custom V4_9
xxxxxxx Mod Edit
source code
Firmware Download:
V9 ALPHA 3
xxxxxx Mod Edit

Reserved for TWRP instructions.

Q / A:
Q: Do I need to worry about what MCU version I have before I use your rom?
A: Maybe, GTX ROM doesn't touch the MCU, which shouldn't be re-flashed with each install anyway as it usually doesn't change. Whatever MCU version you have, this ROM will work for you, as long as you have an FYT based SoM unit. If you encounter errors, you might need to change the "ro.build.fytmanufacturer" property in /system/app/fyt.prop to match whatever your unit ORIGINALLY came with.
Q: I have a RK3066/RK3188/PX3/PX5 based head unit. Will this ROM work for me?
A: NO! This ROM ONLY works on FYT based head units. This means all Joying Intel units, as well as some from other brands.
Q: I like Live Wallpapers. How do I enable them?
A: Use the built in terminal. type su and hit enter. You now have root. then type in:
Code:
cp -R /system/vendor/oem/LiveWall* /system/app
hit enter again, then reboot!
Q: I don't want to use this ROM anymore, what do i do?
A: Use the helper application, custom, open the program, and click RESTORE STOCK. This will restore the STOCK RECOVERY. Go on Joying's website [link], download the firmware of your choice, and follow their instructions.
Q: Can I use google voice to make hands free calls?
A: You sure can. Use the "Voice Search" app to dial a number using your voice, once at the Google App screen, click on the hamburger menu, and then select GV CallHandler 4 Joying. Make sure your unit is set to a DPI of at least 161dpi or greater, and then clear data on the google app. After you reboot, you should be able to make calls.
Q: How do I view my front camera?
A: If you are using the analog RCA video input, on the back of the unit, you can use the RIGHT CAMERA app to view. Note, than unlike the AUX program, this one will NOT mute the system audio.
Q: How can I fix my GPS speed to calculate 1/kmh or 1/mph steps instead of the default 4 steps?
A: Go to XPOSED INSTALLER, and enable the GPSSpeedFix module. Reboot, and the steps will be fixed.
Q: How can I enable different DPI settings for each application?
A: Go to XPOSED INSTALLER, and enable the App Settings module. Exit the installer, and open the App Settings to make your adjustments. Reboot, and your changes will be visible.
Q: This ROM is fast, but I want more speed, what do I do?
A: Add a fan to your unit, preferably a FAN + Heatsink. Then download an app like SetCPU to lock your CPU to MAX speed. Be careful.
Q: How do I re-assign the hard keys on my unit? Joying says that DVD and EJECT don't work! Is this a lie?
A: Yes! There is a way to re-assign keys, and the DVD and EJECT keys do actually work, the software that comes with the unit is not very good. Check @surfer63's XSofiaTweaker thread for more info on how this works.
Q: I want to send and receive my text messages on my Joying unit...is this possible?
A: Sure! Use third party app like Pulse, or Pushbullet. Works like a charm. I personally use Pulse, it's got the look and feel of a stock SMS app.
Q: Installing the Joying Factory Rom takes like an hour...multiple reboots, then it starts over, then it reboots, then it optimizes apps, then it starts over, again. jeez. How long does your ROM take to install?
A: Installation is less than 4 minutes. First boot is timed at one minute 53 seconds, and there are no crashes or reboots. It just works.
Q: Xposed says there is an update available! Is it safe to update Xposed?
A: NO! Do NOT update Xposed, it will make your unit non-functional! Just say NO!
Q: Am I able to "upgrade" from an earlier version of the ROM to a newer without loosing my data and apps?
A: Yes, read the first post on what option to select in custom. Many others and I have tested, and it works for almost all people, still there is a chance that it could not work.
Q: I need to download the stock Joying firmware so I may use your ROM! Where do I get the latest updates?
A: See here: https://drive.google.com/open?id=1nF5Pgn95_WWGk8S2byb8rR5ko0ss5F_S
Q: is there a video where I can see you install the ROM?
A:

Issues:
-Unable to send text message via google voice app using Pulse SMS, error is "Message couldn't be sent" // If anyone has a fix for this, please let us know
-Google Assistant doesn't work, launching activity manually results in "The Google Assistant doesn't work on this device" / You can fix this by changing the resolution to at least 720. use the command wm size to change the screen resolution or another tool that can change DPI
Release History:
custom helper:
V4_1: Fixed installation issue from micro sd cards.
V4_2: Check OS build fingerprint, will deny install unless you are on 20171215 or later.
V4_3: Updated text on installation screen for easier reading, Updated build detection logic
V4_4: Fixed bug in build detection logic
V4_5: Added no_data_wipe, translations included.
V4_6: fixed reboot to twrp not extracting recovery ota.
V4_7: lbug fixed
V4_8: script improvements
V4_9: prepare for re-write, added performance mode
ROM:
V4: Replaced opengapps with nano version
V5: Updated to 01-10 AOSP Base, Added bluetooth build property from @surfer63, more optimizations.
V6: Added Navi APK, more optimizations, CANBUS firmware included, various stability fixes, ability to "dirty flash", mcud included to prevent bootloops during app optimization, works with 800x600 units now, fixed overlay bug, faster first boot, added ViPER4ANDROID, added USB audio policy modifications.
V7: Fixed LED issues and AMP Options. Updated GAPPS base to 20180226, might need to optimize apps on first boot if you are dirty flashing. Added fyt.prop to /system/app fix various issues.
V8: Changes in the way the installer handles re-installation of stock recovery for disaster recovery situations in which the installation fails and custom recovery remains installed, changed installation logic to to compensate for faulty installation media, twrp bug fixes, fixed twrp restart loop, clear FYT flags on twrp start.
V9 alpha 1:
updated recovery busybox to 1.27
fixed SYU file manager not found in CM Settings
fixed right camera not displaying
updated MCUd build to co-exist with sofia server
eliminate audio pops during rebooting
updated gtx_installer
updated dalvik cache
fixed recovery_maintenance.sh in system and recovery envrionments
recovery maintenance.sh is now functional from recovery console
updated clean_rom.sh
permissions overlay fixed
fixed script logic in install-recovery on 6021 units
include terminal app APK
added nano x86 editor
added network_up.sh to ensure debug network access and SU daemon is always run
v9_alpha_2:
fixed drm video black screen issue
added rom version information to fyt_build.prop
sofiaserver runs audio through all channels during call
v9_alpha_3:
xposed module to prevent xposed from updating framework causing bootloops
added remount command to path
added display calibration app to launcher
include both 5_25 and 9_20 versions of McuUpdateAll.bin in /system/mcu/ (copy the corresponding version to /system/mcu)
keep JET and other apps as user to ease upgrade

V3 Rom link not working?

Just finished upload, Try now.

gtxaspec said:
Just finished upload, Try now.
Click to expand...
Click to collapse
Yes, works fine. Sorry for clicking the links too early
I can't do anything with it now, but a link is so easily clicked.

my joying head units have an internal amp, can I use this ROM?

usa911g said:
my joying head units have an internal amp, can I use this ROM?
Click to expand...
Click to collapse
Yes, no problem at all. If there are bugs we will share them all. Nothing specific for amp or no-amp models.

surfer63 said:
Yes, no problem at all. If there are bugs we will share them all. Nothing specific for amp or no-amp models.
Click to expand...
Click to collapse
because the EQ app for amp or non-amp models is different, so I concern that

usa911g said:
because the EQ app for amp or non-amp models is different, so I concern that
Click to expand...
Click to collapse
Actually it is one and the same app with different screen-layouts and functionality depending on the hardware.

The digital amp software is included.

Reserved.
As soon as I have time I will try this rom

the russian hackers at 4pda are using the following build.prop mods, anyone care to chime in? if they actually do something, I will include them.
Code:
ro.rk.install_non_market_apps=true
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
persist.telephony.support.ipv4=1
persist.telephony.support.ipv6=1
persist.sys.purgeable_assets=1
ro.wifi.channels=14
media.stagefright.enable-http=true
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=false

I have no idea about the build props.
The custom V3 app did install the recovery image in one go. I do not know whether you improved something or the previous time was a glitch on my system when it gave that verification error.
I installed the V3 ROM. It works fine. It seems indeed faster than the original joying stock rom.
From what date are the GAPPS? The unit is trying to update all gapps. It is not really useful to have everything pre-odexed for a quick start (and it really is a quick start), when it immediately starts updating once you have finished the Google account setup.
(I myself also prefer the GAPPS micro package. I don't need and want google photos, youtube, google fit, etc. on my head unit.)
My JET apk is only partly working. At this moment I do not know why.
Replacing apps with mods (radio, BT, sofiaserver) works again now the apps are installed in /system/app
Copying the launcher.sh to /data does work. The launcher.sh works with the SofiaServer keymod as well as with the Xposed module sofiaservercustomkeymod (the one that uses the launcher.sh).
Installing a newer version ór installing one of the xposed modules currently doesn't work as it requires the package installer. The default package installer has been replaced by the googlepackageinstallers from the gapps. As such I can easily work around it by simply writing the apps to their folder in /system/apps. As soon as I upload my modules to the global xposed repository it is no problem anymore anyway as the Xposed installer can install it. I will still looking into why that one can install and my app not. I will also uninstall the google installer and replace it with the default package installer and see what happens.
And with regard to the customkeymod xposed module with settings screen: The settings screen itself works fine, but I still can't use the settings from my app. They stay empty.

Ok, if you think the microgapps is lighter I can cook that in.

gtxaspec said:
Ok, if you think the microgapps is lighter I can cook that in.
Click to expand...
Click to collapse
You might even consider nano or pico gapps and let users just install whatever else they need manually.

I'll do nano on v4 release which will be out tonight.

gtxaspec said:
I'll do nano on v4 release which will be out tonight.
Click to expand...
Click to collapse
Is Viper4Android working on this ROM?
Some time ago you said that you will investigate why is not working on the stock Joying but you never returned with an answer, can you please share your findings if you have any?
Thank you !
---------- Post added at 07:05 AM ---------- Previous post was at 07:03 AM ----------
surfer63 said:
(I myself also prefer the GAPPS micro package. I don't need and want google photos, youtube, google fit, etc. on my head unit.)
Click to expand...
Click to collapse
I second this .... I also prefer things kept extremely simple !

haven't tested viper. I will install it tonight and test it tomorrow morning on my drive.

[ROM][11][flox][OFFICIAL] crDroid 7.31Google Nexus 7 2013 repartitioned

{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Flox is how LineageOS has chosen to name the repartitioned version of flo, which means that if you haven't repartitioned your Nexus 7 2013 you must repartition it before even trying to flash this. Please read LineageOS instructions here before trying anything.
Pre-installation:
Recovery (TWRP Lineage Recovery)
gapps arm (MindTheGapps OpenGapps)
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/mantinan/android_kernel_google_msm
Device: https://github.com/LineageOS/android_device_asus_flox
Download:
ROM
Known issues:
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.
Visit official website @ crDroid.net
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs

bestiatester said:
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Flashing Instructions:
Flox is how LineageOS has chosen to name the repartitioned version of flo, which means that if you haven't repartitioned your Nexus 7 2013 you must repartition it before even trying to flash this. Please read LineageOS instructions here before trying anything.
Pre-installation:
Recovery (TWRP Lineage Recovery)
ROM (Download from here)
gapps arm (MindTheGapps OpenGapps)
Sources:
ROM: https://github.com/crdroidandroid
Download:
ROM
Known issues:
Battery is shown as charging at 0 mA.
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.
Visit official website @ crDroid.net
crDroid <device> Telegram
crDroid Community Telegram
Donate to help our team pay server costs
Click to expand...
Click to collapse
OH MY GAWD I'M IN LOVE everything working great here. This rom is surprisingly smooth with MicroG installed. Long live the Nexus 7!

Mr.Conkel said:
OH MY GAWD I'M IN LOVE everything working great here. This rom is surprisingly smooth with MicroG installed. Long live the Nexus 7!
Click to expand...
Click to collapse
Can you share the steps you used to get microG to work? I am having a hard time getting them to work on LOS 18.1 and This ROM as well!

GeekyTanuj said:
Can you share the steps you used to get microG to work? I am having a hard time getting them to work on LOS 18.1 and This ROM as well!
Click to expand...
Click to collapse
Well the steps can be different on Los 18.1 because Signature spoofing is not built in to Los but it is on Crdroid which makes it was less of a pain because you don't need Xposed for things to work correctly.
So starting with Crdroid go about your normal setup and install Magisk per normal. Afterwards you're going to need to select a package from this link normally minimalAP or the Standard package should be just fine. These packages have everything you need to get MicroG working with the Google Play store the only difference between minimal is Aurora Services and the location backends which a tablet doesn't necessarily need but it depends on what you use it for.
After flashing this through recovery follow these steps..
Initial Setup:
- Complete the setup wizard actions as you prefer
- Open the app drawer and long-press on Play Store to choose the App Info button
- Go to Permissions, then Additional permissions and change Spoof package signature to Allow, go back to home screen afterward
- Run the microG Settings app — The rest of these instructions are taken almost directly from https://gitlab.com/Nanolx/NanoDroid/-/blob/master/doc/microGsetup.md
- Choose Self-Check at the top of the list, and start tapping on the second item, System grants signature spoofing permission which should prompt a permission request
- Everything should now be checked on the Self-Check screen, go back to main microG Settings screen
- Choose Google device registration and enable the Register device switch, then go back
- Choose Cloud Messaging and enable the Receive push notifications switch, then go back
- SafetyNet doesn't actually work or pass right now, but you can try enabling it in the same manner as above
- Choose Location modules and enable at least one "Network-based Geolocation module" and one "Address lookup module". I usually only turn on Deja Vu Location Service from the top list; it seems to work well enough for driving directions here, and of course choose Nominatim from the lower list because it's the only one there
- This is important: Reboot now before you add a Google account or do anything else to the Play Store app
- After rebooting, go back into microG Settings app and make sure that all of the Self-Check items are still checked, and then make sure that Google Device Registration, Cloud Messaging, and SafetyNet are still enabled — if they were not, enable them.
- Now get app info for Play Store, clear cache (yes, again), then launch the app
- Add your Google account, and verify that it will show your app library — Purchased apps won't show as paid-for yet, this will take approximately 24 hours until Google decides it likes your new Android ID
- Open Settings app, then Accounts then choose your Google account, then chose Personal info & privacy, and make sure Allow apps to find accounts is enabled
- That should be everything!
Then after a few hours (a day or so) you should have complete access to you paid apps and you're good to go. Let me know if you need anything else!

Mr.Conkel said:
Well the steps can be different on Los 18.1 because Signature spoofing is not built in to Los but it is on Crdroid which makes it was less of a pain because you don't need Xposed for things to work correctly.
So starting with Crdroid go about your normal setup and install Magisk per normal. Afterwards you're going to need to select a package from this link normally minimalAP or the Standard package should be just fine. These packages have everything you need to get MicroG working with the Google Play store the only difference between minimal is Aurora Services and the location backends which a tablet doesn't necessarily need but it depends on what you use it for.
After flashing this through recovery follow these steps..
Initial Setup:
- Complete the setup wizard actions as you prefer
- Open the app drawer and long-press on Play Store to choose the App Info button
- Go to Permissions, then Additional permissions and change Spoof package signature to Allow, go back to home screen afterward
- Run the microG Settings app — The rest of these instructions are taken almost directly from https://gitlab.com/Nanolx/NanoDroid/-/blob/master/doc/microGsetup.md
- Choose Self-Check at the top of the list, and start tapping on the second item, System grants signature spoofing permission which should prompt a permission request
- Everything should now be checked on the Self-Check screen, go back to main microG Settings screen
- Choose Google device registration and enable the Register device switch, then go back
- Choose Cloud Messaging and enable the Receive push notifications switch, then go back
- SafetyNet doesn't actually work or pass right now, but you can try enabling it in the same manner as above
- Choose Location modules and enable at least one "Network-based Geolocation module" and one "Address lookup module". I usually only turn on Deja Vu Location Service from the top list; it seems to work well enough for driving directions here, and of course choose Nominatim from the lower list because it's the only one there
- This is important: Reboot now before you add a Google account or do anything else to the Play Store app
- After rebooting, go back into microG Settings app and make sure that all of the Self-Check items are still checked, and then make sure that Google Device Registration, Cloud Messaging, and SafetyNet are still enabled — if they were not, enable them.
- Now get app info for Play Store, clear cache (yes, again), then launch the app
- Add your Google account, and verify that it will show your app library — Purchased apps won't show as paid-for yet, this will take approximately 24 hours until Google decides it likes your new Android ID
- Open Settings app, then Accounts then choose your Google account, then chose Personal info & privacy, and make sure Allow apps to find accounts is enabled
- That should be everything!
Then after a few hours (a day or so) you should have complete access to you paid apps and you're good to go. Let me know if you need anything else!
Click to expand...
Click to collapse
Thanks for this guide! Really helped me get things going smoothly! Love this ROM.

Hi,
I need dt2w but i can't activate it, does thé kernel support it?
Can you Hello me please?
Thanks you

jojo33680 said:
Hi,
I need dt2w but i can't activate it, does thé kernel support it?
Can you Hello me please?
Thanks you
Click to expand...
Click to collapse
you need to use the Exkernel to enable dt2w. Here's the latest one: Link.

I am running an old 7.0 Resurrection ROM on my N7.
TWRP is installed & bootloader unlocked so I suspect I would just need to repartition & install?
No clue why ADBgives me these errors in powershell.
fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ fastboot
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

For those who have partition with a different method like me that is NOT flox so they can flash other ROMs, replace this in the ROM zip. All I did was remove assert get prop that checks to make sure your tablet is the right one for the ROM. It won't flash if you're not using flox repartition so I changed it to allow it to flash. I have 1.6gb of system space and am able to flash this ROM, opengapps pico, magisk and custom kernel with no issues running a non flox repartition.
updater-script
drive.google.com

Hi!
In the known issues I descrived:
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.
Can anybody please confirm that this is happening also for you?
And if you know why it is failing or even better, how to fix it... that would be great
Thanks in advance.

bestiatester said:
Hi!
In the known issues I descrived:
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.
Can anybody please confirm that this is happening also for you?
And if you know why it is failing or even better, how to fix it... that would be great
Thanks in advance.
Click to expand...
Click to collapse
I confirm I have the same problem

Hello all,
I follow the guides and the installation went smoothly, thanks for the really good job you've done.
I'm new in the crDroid world so sorry if the question seems stupid: As the power button of the Nexus 7 is not easy to access, how can I activate the double tap to wakeup ?
Some years ago the tablet was installed with aicp, and the DT2W was working. So I'm a little bit disappointed if it is not working now.
Thanks.

Davidtre07 said:
DT2W
Click to expand...
Click to collapse
This material will help you: 01 ... 02 ... 03 ... 04

lyushiK said:
This material will help you: 01 ... 02 ... 03 ... 04
Click to expand...
Click to collapse
With Anykernel installed works like a charm !
Thanks.

Davidtre07 said:
With Anykernel installed works like a charm !
Thanks.
Click to expand...
Click to collapse
If you have a patch or pointer to the code that makes it work... just let me know and I'll try to add it.

I'm testing a patch for the charge current to be shown ok, seems to work, if all the tests are ok I'll ship it in with the next release.

No I don't have any patch to propose, I just followed the links provided by @lyushiK.
As far I understood, to work you have to recompile a kernel with DT2W hability and you have to activate it with the right flag in the kernel.
From my side what I've done:
Installed Magisk (patched boot.img)
Installed this kernel: https://androidfilehost.com/?fid=7161016148664820402
And to finish added to magisk this module: https://github.com/ipdev99/mModule_dt2w
Reboot and it works !

In Magisk I see the module is looking in /sys/ for "doubletap*" or "dt2w*" or "wake_gesture".
If it found one of the files then activate it (echo 1 in the file)
But still, you have to have the right kernel !

Thanks very much, this Rom is so smooth and running great. The only thing I've noticed is that the icon size and text is very small when using the tablet in landscape mode but fine in portrait mode. Any changes I make to the icon size from the settings apply in portrait but when switched to landscape stay as really small, is there any setting I have missed to enlarge them?

Thank you for the great work!
Just for feedback: I can confirm the camera issue, too, though it doesn't bother me.
Another small thing I noticed: during the initial setup my device was called Pixel 6 Pro (first I thought, I chose the wrong image) but in the settings it says correctly "Nexus 7".

How To Guide [OUTDATED - PLEASE USE UNOFFICIAL LINEAGEOS INSTEAD] Installing a GSI on Samsung M12/A12.

I am deleting this guide since M12 will soon recieve an unofficial build of LineageOS 19.1. Don't ask when, as I'm not the lead developer but I helped with it

Update 1: I figured out how to make script run on boot. Instructions revised. If you followed earlier check them again
Update 2: Magisk 24.1 is now stable. Instructions revised.
Update 3: I contacted phh and he implemented the script inside his trebleapp. Instructions revised and modified trebleapp is attached. NOTE: GSIs newer than 7/Feb/2022 will include this workaround by default.
Update 4: This guide is now unnecessary now that unofficial LineageOS is very close to release

Achievement unlocked: flashed GSI with FBE enabled! ​
{
"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"
}
In short, I've successfully done flashing of @phhusson's latest version of Android 12 GSI (which is v402 as of today). To do this, I needed to modify the multidisabler script so it won't disable FBE, format the userdata using the stock recovery, flash TWRP, resize tmpfs to proper size, push GSI image into tmpfs and flash it using TWRP. I used the securized image with vndklite variant, since there was no securized images for regular vndk releases (but it seemed that vndk was working better for me, at least I have no USB connection anymore where with VNDK I was able to have USB debugging). Maybe I'll try re-flashing it once I'll patch the regular images and securize them (since I'm on *nix, I can just mount them and modify their contents) and take an approach of finding how Samsung ROMs are working OK. For now, I need to take a break from all bootloops I had in the process of FBE flashing .
Anyway, the goal of this experiment was to use GSI ROMs as a daily driver and having FBE disabled could otherwise cause a serious problem on device loss.
So, onto the list what's been tested (that wasn't noted before):
Screen locking – it seems that the workaround for the screen is not applied before unlocking the phone, probably because the app is not running yet. This might work with the script used as postfs module.
EDIT: I've found some notes in the Magisk documentation that both post-fs data and late_start services are run after data is decrypted, which basically means applying this workaround using Magisk seems to be pointless for now (maybe not after PPH app will stop providing the workaround)... Probably the best option would be patching the ROM itself, either with flashable ZIPs or directly before flashing it (most GSIs can be mounted under Linux and tweaked).
Adaptive brightness – not working, since all virtual sensors are not working for now. Might be easy to fix through as I've found some stuff in the official ROM that I had an idea to experiment with putting them into GSIs (as a Magisk module, to avoid a breakage).
USB – as I said, a data transfer via USB is not working for me for some reason. It worked for me once I had VNDK Android 12 GSI installed (same version).
Booting with stock kernel – I had some successful attempts doing that, but it further was a cause of a bootloop, at least once I had installed Magisk. Therefore, I'll recommend patching the Magisk the way as in tutorial (after patching the kernel) to have everything working for now.
For people who wants to play with stock images but don't know how: you can use simg2img, lpunpack and Linux to extract and mount the official ROM image in approach of finding there some tips like in initrc services why some stuff is working fine on Samsung while it doesn't on GSIs. Maybe I would tinker with it a bit, trying to export a few services and libraries in an approach to create a Magisk module with all stuff needed to have a fully functional GSI, but I'm tired of modding for now, especially when this is my first Samsung phone I had to deal with.
Edit: Typo fixes, added additional text formatting.

Amazing work. If you need testers feel free to PM me. As a sidenote, poking in sysfs led me to believe that android is sending the info needed to read the proximity but the kernel is sending garbage which gets interpreted as the sensor not being triggered. Also phh should have added the workaround into his trebleapp starting from phh AOSP 12 v401, so aside from installing magisk no post install workarounds should be needed.
Attached is a photo of what cmd_result reads when a whatsapp voice message is played which reads proximity to play the message in the earpiece and turn screen off when proximity is triggered

ap4ss3rby said:
Also phh should have added the workaround into his trebleapp starting from phh AOSP 12 v401, so aside from installing magisk no post install workarounds should be needed.
Click to expand...
Click to collapse
Unfortunately, the commit was reverted as of master branch, so we should prepare for it to stop to work unless phh will work on it before releasing an another version. Also I wrote that the workaround didn't seem to apply itself before unlocking the phone (FBE encrypted) the first time and therefore decrypting sensitive data after boot. For now this makes it an requirement when using PHH app to unlock the phone before it sleeps so the touch is going to be responsive.
Anyway, it seems that even Magisk (v24.1) is not capable of running the services before data is decrypted, so now I have no idea how to bypass that in other way than patching the ROM itself and creating the `initrc` service... Anyway, this is also a hint that what samsung is doing starts before basically everything, so no APK file nor script is going to really fix it since they are meant to start after data is decrypted...

SB3P said:
Unfortunately, the commit was reverted as of master repo, so we should prepare for it to stop to work unless phh will work on it before releasing an another version. Also I wrote that the workaround didn't seem to apply itself before unlocking the phone (FBE encrypted) the first time and therefore decrypting sensitive data after boot. For now this makes it an requirement when using PHH app to unlock the phone before it sleeps so the touch is going to be responsive.
Anyway, it seems that even Magisk (v24.1) is not capable of running the services before data is decrypted, so now I have no idea how to bypass that in other way than patching the ROM itself and creating the `initrc` service... Anyway, this is also a hint that what samsung is doing starts before basically everything, so no APK file nor script is going to really fix it since they are meant to start after data is decrypted...
Click to expand...
Click to collapse
I guess for now we have two options:
A: Build custom kernel/vendor specifically for GSIs that correctly reports sensors as GSIs expect them to
B: Fix GSI issues through Magisk services implementing various workarounds in scripts. (an example is the touchscreen sleep/wake issue)

ap4ss3rby said:
Attached is a photo of what cmd_result reads when a whatsapp voice message is played which reads proximity to play the message in the earpiece and turn screen off when proximity is triggered
Click to expand...
Click to collapse
Also that's interesting those virtual sensors are still present, I personally thought that Samsung made it the way there's an virtual device create as on Linux and there's their proprietary software running somewhere in the system that uses the camera as an input and calculates it to provide the data... On the other hand, when I think about that logic, even some (if not all) virtual devices on Linux (e.g. v4l2loopback) needs to have their module loaded with the kernel to work. I'm glad at least there's no need to reinvent the wheel and no one really needs to recreate the entire algorithm for it if it's going to be in the kernel sources...
ap4ss3rby said:
I guess for now we have two options (...)
Click to expand...
Click to collapse
I feel like the B option is worse than patching the GSI ROMs, either via flashable ZIPs or on your own... This is because I couldn't find anything in docs that would let me run services before /data is going to be decrypted... Personally, I've made myself a such service using the statically-compiled Linux ARM binary (non-NDK, using GNU libs – yes, it is still runnable on Android as well) – it applies the workaround for now both when screen is turned on and off (I had no idea on which event it should really run, so I made it to run on both just to be safe) by watching the file changes based on (AFAIK) filesystem events – so it has a major advantage over your script, as it won't run in endless loop, yet watch the file responsible for brightness to change and then do its job. But even with that, TSP doesn't seem to make touch available immediately and it is still expected to be revived after 1-2 seconds.
Also, as of the methods of applying these workarounds, the other way could be modifying the ramdisk (maybe with the help of Magisk, which I believe has documented how it's actually doing it itself and how others could modify the root and init as Magisk does to load files before the OS will properly initalize itself. Yet I don't like an idea of messing myself with the boot partition, at least for now...

Debug info: I tried flashing stock to grab logs from the touchscreen driver. The logs attached here do not appear at all on an unpatched GSI (I.E flashing the GSI as is without any touch workaround).

ap4ss3rby said:
Hi, I installed LineageOS 18.1 GSI on my M127F. I want to share my guide to installing this GSI.
Code:
DISCLAIMER:
By following this guide you accept that you
may do irreversible damage to your phone.
If something breaks the responsibility is
yours only. If you want stable software that
is guaranteed to work 100% don't follow
this guide.
I assume you are running a fully stock system and and locked bootloader and firmware U3/U4.
Installing TWRP and custom kernel
Enable Developer Options by tapping on software information > build number 7 times
Enter developer options then toggle OEM Unlocking on.
Power off your phone.
Hold Vol Up + Vol Down then plug in your phone to enter download mode
THIS WILL ERASE ALL YOUR DATA AND VOID YOUR WARRANTY. Follow on screen instructions to unlock your bootloader. THIS WILL ERASE ALL YOUR DATA AND VOID YOUR WARRANTY
After this you want to download and install attached Orangefox recovery using odin. After odin is done flashing enter recovery
Format data (not wipe) in recovery
Enter terminal and type multidisabler twice
Reboot to system and verify that under security encryption is disabled
Download TWRP and custom kernel for your phone
Reboot into recovery and locate the downloaded twrp image
Select recovery.
Reboot into recovery
Install kernel, then wipe cache and reboot. You should now see that it is complaining about some internal issue. This is normal.
Installing the GSI
Download your favorite ROM from the list provided below. You want to install an arm64 a/b image.
Extract the image file
Reboot to recovery.
Select install then install image
Locate the GSI image
Select install system
After that is done return to recovery and select factory reset.
Reboot then do setup (if applicable) then download attached magisk and phh trebleapp. If your phone is stuck on bootanimation check under to fix it.
IMPORTANT: DO NOT LET THE SCREEN TURN OFF OR YOU WILL HAVE TO REBOOT TO MAKE TOUCH WORK AGAIN.
Install attached magisk
Open magisk and click on install then direct install
Download and install the attached phh-treble app apk.
Touch should now work. Enjoy your GSI.
Extras
Magisk 24.1
Open Magisk
Go to settings
Update Magisk Manager app to version 24.1
Relaunch Magisk then install magisk
Choose direct instal
Migrating to patched trebleapp
Download and install attached trebleapp
Open your root file manager
go to /data/adb/service.d
Delete the script you added earlier
Tips in case things don't work
In case after rebooting to the GSI the phone bootloops:
Download stock image from wherever you download your firmware (I use a python program called samloader)
Extract the AP of the downloaded firmware
Find userdata.img.lz4 and create a .tar archive only containing this file
Reboot to download mode
In odin select AP then locate the newly created .tar archive Then click on flash
Reboot
Continue from step 7 under the "Installing the GSI" portion of the guide
To revive the touchscreen using ADB:
In case you didn't grant adb root access but installed magisk, run adb shell then su. A root access for the app shell will appear. Grant root permission
Plug in phone to a computer with ADB
adb shell
su
cat /sys/class/sec/tsp/cmd_result
echo check_connection > /sys/class/sec/tsp/cmd
What works:
Boots
RIL
Fingerprint
Main rear camera
Front camera
Sleep/Wake (workaround in steps above, may need to sleep wake several times before it works)
WiFi
Flashlight
Rotation
Magisk 24
90Hz (M12 only. A12 doesn't have 90Hz refresh rate)
LineageOS 18.1
LineageOS 19
CAOS (GApps variant available)
phh AOSP 11 v313
phh AOSP 12 v400h
Untested
GPS
Flashing GApps. (I use fdroid and aurora store on LineageOS and CAOS has built in GApps)
USB-OTG
A127F
M127G
If I didn't list it under broken or working I didn't try it or forgot to test it.
Broken
Double tap to wake. Touchscreen turns off and I have no idea how to keep it alive while lcd is off
MTP
Virtual Proximity. Screen will stay on in phone calls and WhatsApp will always play voice messages through speaker
Flashlight brightness. Flashlight will always stay on weakest brightness with no way to adjust.
Adaptive refresh. The framerate you set in phh addons is what you get. Be prepared for slightly reduced battery.
You tell me (even though I probably don't have the solution)
Bugs
You may need to wait a little bit before touchscreen responds or sleep/wake several times before screen responds after turning the screen off
Credits
@physwizz for kernel, TWRP and orangefox
@phhusson for implementing workaround in trebleapp as well as GSI list
me for touch workaround
Links
Kernels and recoveries: https://t.me/a127f_res/113
GSIs: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Click to expand...
Click to collapse
Great guide.
Well done

Thanks for the great guide. Unfortunately, I don't know how to resize tmpfs. Can anybody tell me how to do that? I only have 4 GB or less on my Samsung Galaxy A12 with 64 GB of Storage (it should have, it only shows something like 3 or 4 gigabytes like I mentioned)

matahbeyz said:
Thanks for the great guide. Unfortunately, I don't know how to resize tmpfs. Can anybody tell me how to do that? I only have 4 GB or less on my Samsung Galaxy A12 with 64 GB of Storage (it should have, it only shows something like 3 or 4 gigabytes like I mentioned)
Click to expand...
Click to collapse
You don't have to resize TMPFS if you don't want to have FBE encryption or have the external SD card (you can use microSD for flashing, which might be a better choice if you need to flash a larger devices). Also you can't resize TMPFS to 64 GB, it uses your RAM to store regular data instead of storage (this is basically the concept of TMPFS). What I was mentioning is that /data won't work under FBE and custom recoveries for now, so you need to use your RAM instead if you don't have any external storage device to save images somewhere via ADB.
As of resizing the TMPFS, you should be able to find some Linux tutorial how to do that, on Android this is works basically the same (even on both Linux and Android you have /tmp directory with TMPFS by default).
Anyway, I've decided to share some stuff that you may need for that. Here's the multidisabler script I was using for flashing GSIs with FBE encryption preserved. I was also working on the native binary that would work as the workaround for the touchscreen so it can be used instead of the script. The advantages are that it actually listens to filesystem events and therefore does not need to read file in loop in order to get the information if brightness has changed. Maybe I'll share it with you once I find it to be ready, right now I'll just share my multidisabler script with patches.
BTW, I've tested LineageOS GSIs (both 11 and 12) and noticed they behave completely different, no matter of variant (the USB actually uses some driver, which is not fully compatible with M12 but close enough to provide basic communication through ADB). I guess pphusson just changed something and now these drivers aren't applied by default, yet I think I've noticed the issues with Bluetooth's HSP/HFP profiles which as I remember was not the case with latest stable pphusson's vanilla Android 12 GSIs. Now I just hope these problems are going to be resolved in the next builds of Android's GSIs with phhusson's patches and with the knowledge that MTP just worked fine on TWRP I used, there's a little hope that we will gain the proper combination of drivers/firmware to have both USB and Bluetooth functional at the same time someday.
I've also approached patching the kernel under newer kernel base 4.19.112, yet I gave up on properly resolving its conflicts. I may work on that as well in order to patch some vulnerabilities, with a hope that I'll succeed updating kernel as closest to the latest patch as possible. The 4.19.112 is going to be just a test if Samsung is capable of actually booting from it and if I may be able to use git with common human logic and my limited programming skills to actually patch it the way it would do so (without much understanding about the code itself, yet basic knowledge about C syntax). For now I've only succeed reproducing the upstream Linux kernel commit structure from 4.19.111, with a single additional commit for Samsung changes and another one for physwizz ones.

can anyone guide me how to unlock bootloader on Samsung Galaxy M12G ?

@SB3P Thanks so much. Sorry for my late reply, but thank you!

SB3P said:
Achievement unlocked: flashed GSI with FBE enabled! ​View attachment 5533799​In short, I've successfully done flashing of @phhusson's latest version of Android 12 GSI (which is v402 as of today). To do this, I needed to modify the multidisabler script so it won't disable FBE, format the userdata using the stock recovery, flash TWRP, resize tmpfs to proper size, push GSI image into tmpfs and flash it using TWRP. I used the securized image with vndklite variant, since there was no securized images for regular vndk releases (but it seemed that vndk was working better for me, at least I have no USB connection anymore where with VNDK I was able to have USB debugging). Maybe I'll try re-flashing it once I'll patch the regular images and securize them (since I'm on *nix, I can just mount them and modify their contents) and take an approach of finding how Samsung ROMs are working OK. For now, I need to take a break from all bootloops I had in the process of FBE flashing .
Anyway, the goal of this experiment was to use GSI ROMs as a daily driver and having FBE disabled could otherwise cause a serious problem on device loss.
So, onto the list what's been tested (that wasn't noted before):
Screen locking – it seems that the workaround for the screen is not applied before unlocking the phone, probably because the app is not running yet. This might work with the script used as postfs module.
EDIT: I've found some notes in the Magisk documentation that both post-fs data and late_start services are run after data is decrypted, which basically means applying this workaround using Magisk seems to be pointless for now (maybe not after PPH app will stop providing the workaround)... Probably the best option would be patching the ROM itself, either with flashable ZIPs or directly before flashing it (most GSIs can be mounted under Linux and tweaked).
Adaptive brightness – not working, since all virtual sensors are not working for now. Might be easy to fix through as I've found some stuff in the official ROM that I had an idea to experiment with putting them into GSIs (as a Magisk module, to avoid a breakage).
USB – as I said, a data transfer via USB is not working for me for some reason. It worked for me once I had VNDK Android 12 GSI installed (same version).
Booting with stock kernel – I had some successful attempts doing that, but it further was a cause of a bootloop, at least once I had installed Magisk. Therefore, I'll recommend patching the Magisk the way as in tutorial (after patching the kernel) to have everything working for now.
For people who wants to play with stock images but don't know how: you can use simg2img, lpunpack and Linux to extract and mount the official ROM image in approach of finding there some tips like in initrc services why some stuff is working fine on Samsung while it doesn't on GSIs. Maybe I would tinker with it a bit, trying to export a few services and libraries in an approach to create a Magisk module with all stuff needed to have a fully functional GSI, but I'm tired of modding for now, especially when this is my first Samsung phone I had to deal with.
Edit: Typo fixes, added additional text formatting.
Click to expand...
Click to collapse
Could you explain how you done this.... i mean please explain step by step... i am using Galaxy M12G Varient....thanks in advance

milindbhaliwade said:
Could you explain how you done this.... i mean please explain step by step... i am using Galaxy M12G Varient....thanks in advance
Click to expand...
Click to collapse
If you would see the *untested* section at the initial post of this thread, it is unknown whetever this works or not for M127G phones (if it bootloops it might not work at all). Anyway, here's how I did it on M127F (at least how I remember this):
1. I did steps from 1-6, I believe I skipped 7 since I was aware it will mess something up with the data partition.
2. I modified the multidisabler script and pushed it to my phone via the ADB (to TMPFS). You can find this script pushed as xz compressed file. Before executing multidisabler script I have done a backup of the recovery and system partitions (using dd tool) which I am going to reflash later.
3. I rebooted to download mode and flashed TWRP image.
4. After TWRP ended flashing, I booted into the recovery. I flashed the physwizz kernel and then my own GSI image as it was described in the instructions at the initial post. Just remember that /data partition is not functional with FBE and TWRP so you need to push your images somewhere else like microSD card or TMPFS partition. OTG might work here as well, this is something I haven't tested yet through...
5. Once you are done with flashing you need to restore the original recovery partition via the download mode. TWRP won't boot the GSIs with FBE encryption enabled actually it does boot now for me, yet I still recommend switching to stock recovery if your phone bootloops or you need to format/wipe userdata partition. You can then safely format your /data partition with the stock recovery.

ap4ss3rby said:
Hi, I installed LineageOS 18.1 GSI on my M127F. I want to share my guide to installing this GSI.
Code:
DISCLAIMER:
By following this guide you accept that you
may do irreversible damage to your phone.
If something breaks the responsibility is
yours only. If you want stable software that
is guaranteed to work 100% don't follow
this guide.
I assume you are running a fully stock system and and locked bootloader and firmware U3/U4.
Installing TWRP and custom kernel
Enable Developer Options by tapping on software information > build number 7 times
Enter developer options then toggle OEM Unlocking on.
Power off your phone.
Hold Vol Up + Vol Down then plug in your phone to enter download mode
THIS WILL ERASE ALL YOUR DATA AND VOID YOUR WARRANTY. Follow on screen instructions to unlock your bootloader. THIS WILL ERASE ALL YOUR DATA AND VOID YOUR WARRANTY
After this you want to download and install attached Orangefox recovery using odin. After odin is done flashing enter recovery
Format data (not wipe) in recovery
Enter terminal and type multidisabler twice
Reboot to system and verify that under security encryption is disabled
Download TWRP and custom kernel for your phone
Reboot into recovery and locate the downloaded twrp image
Select recovery.
Reboot into recovery
Install kernel, then wipe cache and reboot. You should now see that it is complaining about some internal issue. This is normal.
Installing the GSI
Download your favorite ROM from the list provided below. You want to install an arm64 a/b image.
Extract the image file
Reboot to recovery.
Select install then install image
Locate the GSI image
Select install system
After that is done return to recovery and select factory reset.
Reboot then do setup (if applicable) then download attached magisk and phh trebleapp. If your phone is stuck on bootanimation check under to fix it.
IMPORTANT: DO NOT LET THE SCREEN TURN OFF OR YOU WILL HAVE TO REBOOT TO MAKE TOUCH WORK AGAIN.
Install attached magisk
Open magisk and click on install then direct install
Download and install the attached phh-treble app apk.
Touch should now work. Enjoy your GSI.
Extras
Magisk 24.1
Open Magisk
Go to settings
Update Magisk Manager app to version 24.1
Relaunch Magisk then install magisk
Choose direct instal
Migrating to patched trebleapp
Download and install attached trebleapp
Open your root file manager
go to /data/adb/service.d
Delete the script you added earlier
Tips in case things don't work
In case after rebooting to the GSI the phone bootloops:
Download stock image from wherever you download your firmware (I use a python program called samloader)
Extract the AP of the downloaded firmware
Find userdata.img.lz4 and create a .tar archive only containing this file
Reboot to download mode
In odin select AP then locate the newly created .tar archive Then click on flash
Reboot
Continue from step 7 under the "Installing the GSI" portion of the guide
To revive the touchscreen using ADB:
In case you didn't grant adb root access but installed magisk, run adb shell then su. A root access for the app shell will appear. Grant root permission
Plug in phone to a computer with ADB
adb shell
su
cat /sys/class/sec/tsp/cmd_result
echo check_connection > /sys/class/sec/tsp/cmd
What works:
Boots
RIL
Fingerprint
Main rear camera
Front camera
Sleep/Wake (workaround in steps above, may need to sleep wake several times before it works)
WiFi
Flashlight
Rotation
Magisk 24
90Hz (M12 only. A12 doesn't have 90Hz refresh rate)
LineageOS 18.1
LineageOS 19
CAOS (GApps variant available)
phh AOSP 11 v313
phh AOSP 12 v400h
Untested
GPS
Flashing GApps. (I use fdroid and aurora store on LineageOS and CAOS has built in GApps)
USB-OTG
A127F
M127G
If I didn't list it under broken or working I didn't try it or forgot to test it.
Broken
Double tap to wake. Touchscreen turns off and I have no idea how to keep it alive while lcd is off
MTP
Virtual Proximity. Screen will stay on in phone calls and WhatsApp will always play voice messages through speaker
Flashlight brightness. Flashlight will always stay on weakest brightness with no way to adjust.
Adaptive refresh. The framerate you set in phh addons is what you get. Be prepared for slightly reduced battery.
You tell me (even though I probably don't have the solution)
Bugs
You may need to wait a little bit before touchscreen responds or sleep/wake several times before screen responds after turning the screen off
Credits
@physwizz for kernel, TWRP and orangefox
@phhusson for implementing workaround in trebleapp as well as GSI list
me for touch workaround
Links
Kernels and recoveries: https://t.me/a127f_res/113
GSIs: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Click to expand...
Click to collapse
try to install @phhusson (system-squeak-arm64-ab-vndklite-gapps-secure.img) GSI using above method on Samsung Galaxy M12G (SM-M127G) BUT failed to boot up
facing following issue:
1) unable to boot in OrangeFox Recovery
2) boot in TWRP Recovery but not detected MicroSD Card
3) samehow manage to push Kernal.zip, SystemGSI.img by adb push file_name_with_extension /sdcard BUT not flash properly as TWRP reboot again and again in 2-3 minutes
so friends, don't try this method on Samsung Galaxy M12G (SM-M127G) unless Senior member come up with this specific model

For anyone who has starred this thread, I and other devs have released a proper build of LineageOS with /vendor. Aside from VoLTE (which I don't think worked in GSIs anyways) everything should work. Moderators, please close this thread

ap4ss3rby said:
For anyone who has starred this thread, I and other devs have released a proper build of LineageOS with /vendor. Aside from VoLTE (which I don't think worked in GSIs anyways) everything should work. Moderators, please close this thread
Click to expand...
Click to collapse
LineageOS is not only GSI available, I think someone might still find it useful if they want to flash another ROMs. Also Phhuson's GSI also contains some features that unofficial GSI release don't have (i.e. flashlight control in Phhusson's app), so they still might be useful for someone.
This is why I think it is better to not close this thread and maybe revive original guide.

SB3P said:
LineageOS is not only GSI available, I think someone might still find it useful if they want to flash another ROMs. Also Phhuson's GSI also contains some features that unofficial GSI release don't have (i.e. flashlight control in Phhusson's app), so they still might be useful for someone.
This is why I think it is better to not close this thread and maybe revive original guide.
Click to expand...
Click to collapse
Our rom is built completely from source, not a GSI, and it is more or less a complete replacement of stock firmware. If you want you can use a GSI over that instead, and it should function much better than just replacing stock firmware

ap4ss3rby said:
Our rom is built completely from source, not a GSI, and it is more or less a complete replacement of stock firmware. If you want you can use a GSI over that instead, and it should function much better than just replacing stock firmware
Click to expand...
Click to collapse
I haven't said GSI are better, I personally use this unofficial LineageOS build. But what I've said, GSI brings much more variety of picking the OS you can install. Even Linux can be installed on phones nowadays using GSI with only Halium-patched kernel as an requirement. This is why I think leaving this tutorial archived (no updates, interest on fixing bugs etc.) is better than removing it.