OOS 9.0.4: "local terminal app" crashes on every launch - OnePlus 6 Questions & Answers

Hi, quick question:
have a rooted OP6 running Stock OOS 9.04.
In Developer Options I enabled useage of the "local terminal" from the "debugging" section.
Every time I try to launch the terminal it crashes / fcs immediately.
Not a big deal, installed termux anyways, but is this a known bug, or is it just my phone?
Root is done through Magisk 18.1 / Magisk Manager 7.

Related

[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

[DEBLOAT] OOS 9.5.x De-bloat (Systemless+Automated+Easily Reversible) [Aug 28]

This script was made to 9.5.8 OP7 OxygenOS, some things can be different in future, so report if something is broken. Use at your own risk and feel free to experiment as this is a systemless mod. You can revert it just disabling the module or following the procedure on the end of thread.
First, the prerequisites:
1- Unlocked bootloader with Magisk and TWRP (you can use temporary TWRP if you please). If you don't know what is that, take a look at the XDA threads about it, it's easy. Please don't ask about "how to unlock bootloader" or "how to install Magisk".
2- Debloater (Terminal Emulator) Magisk module. Download it from Magisk Manager.
3- Any Terminal Emulator app.
4- import-debloat.txt config file. Download it here
5. Backup (yeah, this module doesn't change anything in /system and can be reverted at any time, but backups are always welcome)
6. Magisk Mount script. Download it from here
Magisk mount is needed to "reinstall" system apps by deleting the dummy folders from Magisk partition if something breaks.
If you have everything handy it should be a matter of few seconds to debloat.
Let's deal with useless system apps, temeletry, some ****ty apps. According from the @Tomatot- thread:
Tomatot- said:
-You'll get more privacy: I've removed Qualcomm telemetry, OnePlus telemetry as well as some Google Telemetry (but you can't expect too much as long as you use gapps)
-You'll get better battery life: less apps running in the background, less wakelocks, less services communicating with servers to send telemetry.
-You'll get better performance: for the same reasons. Don't expect a huge difference as our phone is very smooth already.
-The feeling of having a clean device. And this has no price.
Click to expand...
Click to collapse
Debloated apps list (It's the same Tomatot-'s Light app list):
Code:
AntHalService^=/system/app/AntHalService
AutoRegistration^=/system/app/AutoRegistration
BasicDreams^=/system/app/BasicDreams
BookmarkProvider^=/system/app/BookmarkProvider
BTtestmode^=/system/app/BTtestmode
PrintService^=/system/app/BuiltInPrintService
card^=/system/app/card
EasterEgg^=/system/app/EasterEgg
EgineeringMode^=/system/app/EngineeringMode
EngSpecialTest^=/system/app/EngSpecialTest
GooglePrint^=/system/app/GooglePrintRecommendationService
GoogleTTS^=/system/app/GoogleTTS
LogKitSdService^=/system/app/LogKitSdService
NetflixActivation^=/system/app/Netflix_Activation
NetflixStub^=/system/app/Netflix_Stub
NFCTestMode^=/system/app/NFCTestMode
OEMTCMA^=/system/app/oem_tcma
OEMAutoTestServer^=/system/app/OemAutoTestServer
OEMLogKit^=/system/app/OEMLogKit
OnePlusBugReport^=/system/app/OPBugReportLite
OnePlusCommonLogTool^=/system/app/OPCommonLogTool
OPSesAuthentication^=/system/app/OPSesAuthentication
PartnerBoorkmarksProvider^=/system/app/PartnerBookmarksProvider
PhotosOnline^=/system/app/PhotosOnline
PlayAutoInstallConfig^=/system/app/PlayAutoInstallConfig
QdcmFF^=/system/app/QdcmFF
RFTuner^=/system/app/RFTuner
SensorTestTool^=/system/app/SensorTestTool
SoterService^=/system/app/SoterService
Stk^=/system/app/Stk
Talkback^=/system/app/talkback
Traceur^=/system/app/Traceur
UIMRemoteClient^=/system/app/uimremoteclient
Video^=/system/app/Videos
WallpaperBackup^=/system/app/WallpaperBackup
WAPICertManage^=/system/app/WapiCertManage
WIFIRFTestApk^=/system/app/WifiRfTestApk
GoogleFeedback^=/system/priv-app/GoogleFeedback
OnePlusCellBroadcastReceiver^=/system/priv-app/OPCellBroadcastReceiver
Tag^=/system/priv-app/Tag
USBDrivers^=/system/etc/usb_drivers.iso
Reserve^=/system/reserve
RFToolkit^=/vendor/app/Rftoolkit
AmazonShittyApps^=/vendor/etc/apps
Account^=/system/app/Account
OPBackup^=/system/app/Backup
BackupRestoreRemoteService^=/system/app/BackupRestoreRemoteService
CarrierDefaultApp^=/system/app/CarrierDefaultApp
CTSShimPrebuilt^=/system/app/CtsShimPrebuilt
GoogleDrive^=/system/app/Drive
GoogleDuo^=/system/app/Duo
GooglePay^=/system/app/GooglePay
HTMLViewer^=/system/app/HTMLViewer
GooglePlayMusic^=/system/app/Music2
NVBackupUI^=/system/app/NVBackupUI
OnePlusPush^=/system/app/OPPush
YouTube^=/system/app/YouTube
BackupRestoreConfirmation^=/system/priv-app/BackupRestoreConfirmation
CallLogBackup^=/system/priv-app/CallLogBackup
CTSShimPrivPrebuilt^=/system/priv-app/CtsShimPrivPrebuilt
GoogleRestore^=/system/priv-app/GoogleRestore
GoogleBackupTransport^=/system/priv-app/GoogleBackupTransport
GoogleOneTimeInitializer^=/system/priv-app/GoogleOneTimeInitializer
ManagedPrivisioning^=/system/priv-app/ManagedProvisioning
OnePlusWizard^=/system/priv-app/OnePlusWizard
OPAppLocker^=/system/priv-app/OPAppLocker
OnePlusDeviceManager^=/system/priv-app/OPDeviceManager
OnePlusDeviceManagerProvider^=/system/priv-app/OPDeviceManagerProvider
SharedStorageBackup^=/system/priv-app/SharedStorageBackup
Let's start this!
1. Copy the import-debloat.txt config file to the folder /data/cache in the root. (you can copy it by a root explorer or reboot into recovery and copy it by TWRP file explorer)
2. Install the Debloater (Terminal Emulator) Magisk module using the Magisk Manager.
3. Open the terminal emulator app
> Type 'su' and press enter
> Grant root permissions
> Type debloat and press enter.
4. You will see the options to debloat in various categories which are self explanatory. As we have the config file which has a predefined app list to de-bloat stored in /data/cache folder in root already. Type 'i' which says import config and press enter 2 times.
5. Reboot 2 times and you're done most probably if nothing breaks.
Ta-dah! Fully debloated OOS. To keep the debloat after update the ROM, just reflash Magisk and you're fine. You don't need to do the procedure every update.
Read from here if something breaks (from @Sreekant)
If it breaks the system or causes boot-loop which shouldn't be the case as I'm using the OP7 9.5.8 and everything is fine, but well, **** happens. Don't worry! It's pretty easy to reinstall all of them in one click by TWRP.
Did you download the Magisk Mount script which I asked to earlier? If yes, just flash it with TWRP and the magisk will be mounted and accessible in TWRP file explorer. If you didn't download the script earlier, Just adb sideload it in recovery.
After mounting the Magisk in TWRP > Click on Advanced and go to file explorer.
Then delete the app folder of the system app you've uninstalled in /Magisk/terminal_debloater/system/app (/sbin/.core/img/terminal_debloater/system/app) or /Magisk/terminal_debloater/system/priv-app (/sbin/.core/img/terminal_debloater/system/priv-app) then that should undo it.
Click to expand...
Click to collapse
----------------------
Feel free to give any feedback about the script.
Special thanks to:
@Tomatot- (the apps list and some explanations are from his thread)
@Sreekantt (the thread base and original idea from debloat for Poco F1)
@topjohnwu (Magisk developer)
The Debloater (terminal) team
THREAD CLOSED as duplicate of https://forum.xda-developers.com/oneplus-7-pro/how-to/debloat-oos-9-5-x-bloat-systemless-t3962605

[GUIDE] OOS 10.3.8 degoogled, debloated + MigroG

I have successfully degoogled and debloated the latest OOS (atm 10.3.8) and have a working microg setup using nanodroid package. Battery life is nice. 45hrs with 10,5hrs SOT on the first go! Not any unwanted background data moving, success I'd say! So for anyone interested, here are roughly the steps I took.
I couldn't deodex the services.jar with VdexExtractor so I used FakeGapps from Edxposed. Works!
In following guide we will first get a factory state OOS with twrp and root WITHOUT internet. Then we uninstall system app 'android setup', allow internet, get Edxposed working and FakeGapps installed. Then we install Nanodroid package from twrp to get a working microg and setup it and debloat. + Disable trackers using App Manager from F-droid repositories or github. Get it ready for sideloading or use adb. Support the developer!
General guide (everything gets erased):
1. Pure factory installment using MSM tool for 10.3.8 from Oneplus 6 unbrick tools. (XDA forum)
2. The phone starts, go through the initial setup bypassing everything you can. DON'T SETUP ANY WIFI!
3. Immediately switch off mobile data from quick settings, just in case. We dont want android setup to update any apps.
4. Enable unlocking the phone, reboot to bootloader
5. Unlock the bootloader (fastboot oem unlock)
6. Do parts 2 and 3 again (choose Oneplus slate font at this time if you ever want it to work)
7. Enable USB debugging, connect to computer, check 'adb devices' to get the window to allow the computer to appear. (The daemon needs to be running)
This all was to get the phone into pure factory state without automated changes, bootloader unlocked and adb working.
8. Install twrp and magisk. Boot up the phone.
9. Remember! No internet connections yet! Uninstall the system app 'Android Setup'. I used sideloaded AppManager for that. You'll know when you have uninstalled the correct app when the notification of android setup disappears.
10. Reboot
11. Now you can connect to internet.
12. In magisk, install Riru core, (mandatory reboot here!) and Riru Edxposed (2nd reboot)
13. In Edxposed, install FakeGapps and activate it. Reboot.
13. Now you can connect to internet.
This was all done to setup the phone for Nanodroid package and get safely to internet without unwanted updates.
14. Download a nanodroid package from github. I used just the microg version. Flash it from twrp. It should debloat some necessary google stuff, install aurorastore and aurora services and straight up working microg.
15. Check if microg is working and do registrations and enable cloud and location stuff. Reboot.
16. Install any app that uses google cloud service for push notifications and check from microg settings that it shows in the list. Don't continue installing any such apps until it does. Reboot or troubleshoot if necessary with microg related info.
17. Back up current setup from twrp for fallback.
18. Debloat to your heart content, except only disable and force stop the play store. In my case the app is still the official one. Don't use.
19. From AppManager, run disable all trackers, including system apps from 1-click ops.
There! Use some time, and if everything is to your liking, make a backup. Remember to disable trackers from every app you install after you have configured it.
Sidenote: Aurora store did not work when installed systemlessly, but worked fine as a user app
Reserved, just in case

LGv20 H910 Root Step by Step guide to install Oreo Stock & debloat most lgv20 phones running Stock Oreo

STANDARD DISCLAIMER: I am not responsible for any damages caused to your phone. Use this Guide at your own risk there is no warranty or guarantee.
How to Root the H910 and install the Lemon Drop Rom?
1. Disable real time scanning, on the windows virus scanner. Download all the files, save terminal emulator to your microsd card the other two save on your computer, unzip dirtysanta, install usb drivers if using windows. Root your H910 with this guide.
h910_root_pkg.zip "DirtySanta root package"
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
2. [ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED) Note: before you flash the KDZ to downgrade your firmware make a DUMP backup with LGUP all files. You don't need to DUMP system or cache. It will have your EFS.
3. On step3.bat wait for phone to reboot from fastboot mode, when you see the LG logo, pull the battery. Do a factory reset and that will load TWRP How to factory reset the Lgv20.
4. Then format data. Very important, you format data with the older version of twrp that is with dirtysanta.
5. Then power off phone.
Note: This next part is for the H910, you need to get your version of twrp for your model of Lgv20. Latest version of twrp link at the bottom of page
6. Download twrp for the H910 twrp-3.7.0_9-0-h910.img
7. With the phone powered off, hold the down volume button and plug in usb to computer and phone.
fastboot flash recovery twrp-3.7.0_9-0-h910.img
fastbboot reboot
take battery out
put back in
go into twrp by doing a factory reset. How to factory reset the Lgv20
8. Then you want to format data once more with the new version of twrp.
9. power off phone
10. Then go to: [Lemon Drop] A [Debloated] & [DeGooged] [Stock] [Oreo] [Rom] for the H910 & Most Lgv20 phones.
(archived)
Install Oreo on the H910 & debloat ALL lgv20 phones.
Any Lgv20 phone can debloat go to step 13. H910 phones start at step one.
If you are having issues downloading the rom you can try this download manager for Firefox.
Turbo Download Manager
1. Download the following files. And put them on the sdcard.
twrp-3.3.1-0-h910.img
H910_20g_Oreo_full_rooted.zip
h910oreomodem.img
H910_1.0-ezV2020.zip new kernel
adreno+5xx+-+v313+rev23+-+non-treble.zip new gpu drivers
Magisk-v19.0.zip (direct link to github)
MagiskManager-v7.1.1.apk (direct link to github)
2. Restart phone into recovery. (aka twrp)
3. Then install twrp-3.3.1-0-h910.img (The img file can be flashed with twrp you just need to select Install Image, select the file and choose recovery).
4. Reboot phone into Recovery
5. Click wipe then Swipe to factory reset
6. Install H910_20g_Oreo_full_rooted.zip
7. Then install h910oreomodem.img (The img file you can flash with twrp you just need to select Install Image, select the file and choose modem)
8. Then install twrp-3.3.1-0-h910.img (The img file can be flashed with twrp you just need to select Install Image, select the file and choose recovery).
9. Then install Magisk-v19.0.zip
10. Then install adreno+5xx+-+v313+rev23+-+non-treble.zip
11. Then install H910_1.0-ezV2020.zip then wipe dalvik cache
12. If you do not want to debloat Stock Oreo, then go to step 16. Otherwise to go step 14.
13. Any Lgv20 Reboot into twrp. Do steps 14, 15, 17, 18. Can debloat numbers 10 - 18
14. Click on Mount, make sure Mount system partition read-only is unchecked. Mount System. Then open up file manager under advanced.
15. If you want to debloat the H910 phone, these 18 lines can be safely deleted with the trwp file manager. Note these 17 lines should be removed before first boot H910.
01. "/system/priv-app/AMBS" bloatware at&t backup and sync messaging
02. "/system/priv-app/ATT_Lookout" bloatware att lookout
03."/system/priv-app/ATT_AppSelect" bloatware installs unwanted apps in background.
04. "/system/priv-app/ATT_DeviceHelp" bloatware
05. "/system/priv-app/ATT_IQI" bloatware
06."/system/priv-app/ATT_RemoteSupport" bloatware
07. "/system/priv-app/ATT_SNT" bloatware
08. "/system/priv-app/MetricService" bloatware
09. "/system/vendor/app/ATT_HotSpots" bloatware
10. "/system/priv-app/EdenService" bloatware
11. "/system/priv-app/LGDMSClient" OTA Updates
12. "/system/priv-app/LIAInformant" bloatware
13. "/system/app/LGATCMDService" OTA Updates
14. "/system/app/LGFOTA" OTA Updates
15. "/system/vendor/app/SecProtect" bloatware
16. "/system/vendor/bin/triton" It's an antivirus program, slows the phone down.
17. "/system/vendor/bin/tftp_server" Prevents phone from downloading any updates
18. "/system/priv-app/GCUV" Blotware some kind of LGE sign in portal, looks like it may cause a battery drain also.
16. Restart and run setup and update Magisk v23.0 confirmed working.
17. Disable MLT/LDB Use a root file manager
required folders:
/system/vendor/overlay/com.lge.mlt
/system/priv-app/LGLDB
open: "/mpt/enable" change "1" to "0"
change file permissions for "/mpt/enable" to 0444
reboot
18. done
Recommended twrp options for backup.
Boot
Recovery
System Image
data (excl. storage)
EFS
Fimrware
LAF/Download Mode
Optional packages to debloat H910 and ALL Lgv20 phones.
LG Messaging is required, to run the setup, first boot. Most other apps that are not on the list, you can just disable them in Oreo.
If for what ever reason you need to reinstall an app all you need to do is unzip the rom H910_20g_Oreo_full_rooted.zip and locate the "system" file and rename to "system.img" mount it on your computer and copy back the folder to the same location on the phone, reboot. Keep in mind this is the "/system" directory on the phone. File permissions 0644 for apk file.
Free root file manager no ads
[APP][2.2+] MiXplorer v6.x Released (fully-featured file manager)
ALL Lgv20 phones can debloat #07 - #32.
H910 phones can debloat #01 - #31.
These folders can safely be removed.
01. "/system/priv-app/ATT_DriveMode" ATT Drive Mode
02. "/system/priv-app/ATT_CallerNameID" ATT Caller Name ID
03. "/system/vendor/app/DirecTV_Remote" DIRECTTV Remote
04. "/system/vendor/app/DirecTV" DIRECTTV
05. "/system/vendor/app/ATT_UBER" Uber
06. "/system/priv-app/MyATT" My At&t app
07. "/system/app/EditorsSlidesStub" Google Slides
08. "/system/app/EditorsSheetsStub" Google Sheets
09. "/system/app/EditorsDocsStub" Google Docs
10. "/system/app/Music2" Google Play Music
11. "/system/app/Videos" Google Play Movies & TV
12. "/system/app/Drive" Google Drive
13. "/system/app/YouTube" YouTube
14. "/system/app/Maps" Google Maps
15. "/system/app/LatinImeGoogle" Google keyboard
16. "/system/app/Photos" Google Photos
17. "/system/vendor/app/facebook" Facebook
18. "/system/priv-app/facebook-installer" Facebook App Installer
19. "/system/vendor/app/facebook-appmanager" Facebook App Manager
20. "/system/app/Hangouts" Google Hangouts
21. "/system/priv-app/LGEmail" LG Email
22. "/system/app/GoogleInApps" Google In Apps
23. "/system/vendor/bin/xtra-daemon" info
........"/system/vendor/etc/xtra_root_cert.pem"
........"/system/vendor/etc/cacert_location.pem"
24. "/system/app/SDEncryptionHelper" SD Encryption Helper, I don't use SD Encryption.
25. "/system/app/WfdService"
......"/system/bin/wfdservice"
......."/system/etc/init/wfdservice.rc"
......."/system/app/atfwd"
......."/system/vendor/bin/ATFWD-daemon"
........"/system/vendor/etc/init/[email protected]"
.........'/system/vendor/bin/wifidisplayhalservice"
Screen Share may not work, if removed. Been reports of people using this app to hack into the phone, and view everything on your screen via wifi or LTE data reddit
26. "/system/vendor/app/SVIService" This app messes with the auto brightness. With it removed, you can change your brightness level with auto brightness enabled. If it's to bright, turn down the brightness and the phone will remember that setting, next time in the same light level.
27. "/system/etc/init/atrace.rc"
This is for debugging the kernel. Kernel trace logs are stored at "/data/anr/" you can delete them if you want. This slows boot time down and takes up memory. The phone makes a log about the size of 700MB each boot.
28. "/system/priv-app/LGBackup" Slows phone down use twrp to backup up
29. "/system/priv-app/BackupRestoreConfirmation" Slows phone down use twrp to backup up
30. "/system/vendor/overlay/com.lge.sizechangable.weather" Uses cpu cycles
31. "/system/priv-app/LGWeather" Uses cpu cycles
32. "/system/priv-app/Lookout T-Mobile Lookout
Credits, A Special Thank You
@ezzony - for the ezV2020 kernel. XDA
@askermk2000 - for the MK2000 kernel. XDA
@me2151 for DirtySanta. XDA
@clsA for the H910 v20g rom. XDA
@runningnak3d for a great H910 root guide. XDA
@darkknight200 for the H910 Oreo modem drivers. Download Link
at hardreset.info on how to factory reset the Lgv20
at TeamWin TWRP, for TWRP.
at the people over at Magisk, for an Opensource Root.
at XDA, for a Great Platform.
And everyone else that I may have missed that helped with the Lgv20.
Thank you all, for helping make the Lgv20 phone one of the best rooted phones of all time.
how fast is the performance like pubg
DesrtSailor said:
how fast is the performance like pubg
Click to expand...
Click to collapse
I have never played pubg so I cant tell you, I can tell you the UI is faster and I do have one game on my phone Reckless Racing 3 and it seems to play a little faster and does not skip frames that I can see. But keep in mind that the Lgv20 is not the fastest phone around it's a 2016 model. But my guide will help you get the fastest experience out of your phone.
did u run geekbench scores or antutu
how is compared to nougat
DesrtSailor said:
did u run geekbench scores or antutu
how is compared to nougat
Click to expand...
Click to collapse
Yeah I got some benchmarks. I should have uploaded them but I was still working on my guide. Sorry don't have Nougat.
{
"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"
}
My phone has the H91020I update, could I use this method to root? Or I am out of luck.
HAMSATHI said:
My phone has the H91020I update, could I use this method to root? Or I am out of luck.
Click to expand...
Click to collapse
That's a good question, unfortunately I don't have the answer, please ask in this forum.
[ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED)
I am so glad I waited, this guide sounds like exactly what I am looking for! I'll be attempting this tonight on my backup AT&T V20 variant. Thank you
Dream Reality Syndrome said:
I am so glad I waited, this guide sounds like exactly what I am looking for! I'll be attempting this tonight on my backup AT&T V20 variant. Thank you
Click to expand...
Click to collapse
Your welcome.
Darnrain1 said:
Your welcome.
Click to expand...
Click to collapse
I attempted to download the Oreo image several times but it seems the mirror on AFH kept dropping out. Is there another host for that particular image? Should I try to find some other Oreo image?
Dream Reality Syndrome said:
I attempted to download the Oreo image several times but it seems the mirror on AFH kept dropping out. Is there another host for that particular image? Should I try to find some other Oreo image?
Click to expand...
Click to collapse
I have had that happen before with AFH. I used firefox and just pressed retry a lot. Let me think about this maybe I can just upload the files to xda.
Darnrain1 said:
I have had that happen before with AFH. I used firefox and just pressed retry a lot. Let me think about this maybe I can just upload the files to xda.
Click to expand...
Click to collapse
okay I am uploading the files to xda but my upload speed is not that fast. I think this will take an one hr or two. As for package manager and Mixplorer you still should download the apps from the developers.
Dream Reality Syndrome said:
I attempted to download the Oreo image several times but it seems the mirror on AFH kept dropping out. Is there another host for that particular image? Should I try to find some other Oreo image?
Click to expand...
Click to collapse
xda does not allow me to upload the 2.5 gb file. I guess it's to large.
Try firefox and if the download stops press retry and it should continue where it left off. As for using another version you can try but I recommend H910 V20g it seems to be stable.
Darnrain1 said:
xda does not allow me to upload the 2.5 gb file. I guess it's to large.
Try firefox and if the download stops press retry and it should continue where it left off. As for using another version you can try but I recommend H910 V20g it seems to be stable.
Click to expand...
Click to collapse
I will try your method tonight. Thank you for trying!
Dream Reality Syndrome said:
I will try your method tonight. Thank you for trying!
Click to expand...
Click to collapse
Try this downloading extension for Firefox. I was having issues also but this worked for me.
Multithreaded Download Manager by jingyu9575
T
Darnrain1 said:
Try this downloading extension for Firefox. I was having issues also but this worked for me.
Multithreaded Download Manager by jingyu9575
Click to expand...
Click to collapse
This worked out perfectly, thank you!!
My H910 V20 has been up for 18 + days can counting. Very stable install of Oreo.
Darnrain1 said:
STANDARD DISCLAIMER: I am not responsible for any damages caused to your phone. Use this guide at your own risk there is no warranty or guarantee.
This guide will walk you through step by step on how to install Oreo on the H910.
I assume that your phone is already rooted. If not, click on this link below.
[ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED)
You may be wondering why I used v20g version when there is an v20h version out. The v20g version is very stable. And most of the updates from g to h are most likely just carrier updates not OS updates. I went with version 19.0 of Magisk because it's very stable, newer versions may prevent your phone from booting.
How to install Oreo on the H910 with Root
Make sure you have a backup of all your important files from the internal storage before you start. We will be reinstalling the android operating system.
Note: If you have trouble downloading the files you can try this Firefox downloading extension.
Multithreaded Download Manager by jingyu9575
1. Download the following files. And put them on the sdcard. You can use MIXplorer or another root file manager of your choice you just need to be able to install the file manager from the sdcard (no internet).
recovery-twrp-h910-2018-10-18.img
H910_20g_Oreo_full_rooted.zip
h910oreomodem.img
MK2000 kernel 2.0
Magisk Uninstaller
Magisk 19.0
Magisk Manager 7.1.0
[APP][2.2+] MiXplorer v6.x Released (fully-featured file manager)
Package Manager
2. Restart phone into recovery. (aka twrp)
3. Install recovery-twrp-h910-2018-10-18.img (The img file can be flashed with twrp you just need to select Install Image, select the file and choose recovery).
4. Reboot phone into Recovery.
5. Do a format, then do a standard wipe.
6. Install H910_20g_Oreo_full_rooted.zip
7. Then install h910oreomodem.img (The img file you can flash with twrp you just need to select Install Image, select the file and choose modem) Then select Install Zip.
8. Then install H910_v2.0-mk2000.zip
9. Then wipe dalvik cache
10. Then install Magisk-v19.0.zip
11. Then reinstall recovery-twrp-h910-2018-10-18.img (The img file can be flashed with twrp you just need to select Install Image, select the file and choose recovery).
12.. Reboot phone into System.
13. Then after the phone boots up into the setup screen click next and disable cell and wifi data. Internet need's to be off for this whole process.
14. Click next it will ask you to enable but just skip everything.
15. When you get to home screen, put the phone in airplane mode.
16. Open the LG file manager and install MiXplorer from the sdcard and give it root access. (Or use any root file manager you like, as long as you can install the file manager from the sdcard offline.)
17. Open your root file manager go to (root) /system/priv-app/
18. I deleted some folders, this will make your phone run faster. (Bloatware)
ATT_DeviceHelp
ATT_IQI
ATT_Lookout
ATT_CallerNameID
ATT_AppSelect
ATT_RemoteSupport
ATT_SNT
19. Reboot your phone but stay in airplane mode for now.
20. Install com.smartpack.packagemanager_45.apk (aka package manager) from the sdcard.
21. Open Package Manager give it root access, go to system and do a search for the following updates and Uninstall them. (Updates will break your phone because it's rooted.)
com.lge.android.atservice
com.lge.lgdmsclient
com.lge.lgfota.permission
22. Open Magisk go into settings and disable, Check for Updates. I would recommend just staying with Magisk 19.0 it's stable and works well with Oreo.
23. Congratulations on completing the installation process. You can now enable cell data and wifi.
Note: Don't uninstall the built in weather app, it will cause second screen to crash and make your phone unusable. I would recommend using package manager to disable the apps you don't want, that way you can always re-enable them. Also the Amazon app takes up a lot of battery power. The Amazon app is is not well optimized for android at the time of writing this guide.
There is a bug in the latest version of chrome and web view that makes the screen flicker on some apps. To fix this you need to disable chrome and enable chrome and check do not auto update in the play store, and don't update chrome. I use the Kiwi browser it's based off of chromium and you can install chrome extensions.
I have found a fix for the flickering you have to install the updated graphics driver. This driver is for oreo only lgv20, after you flash in twrp you must wipe dalvik cache.
[10/27][Adreno][OREO][Vulkan]Driver for Snapdragon 820/1[V313 REV23 | V330 REV3]
To fix the image retention install this shell script.
LGv20 fix image retention, aka screen burn in. shell script (root only)
Apps & Tweaks. All apps & tweaks are free to use or open source.
Thermal Throttling Fix LGv20 (Stock root only) (fix thermal throttling for gaming)
[APP][2.2+] MiXplorer v6.x Released (fully-featured file manager) (Root file manager, free to use & no ads, there is a paid version on google play store if you want to support the dev.)
[GUIDE] Best Battery Life Possible (Disable LDB & Logging will increase speed of phone) This guide is for the LG G6 but will work with lgv20 phones, NOTE do not change the screen resolution go to the line that says Disabling LDB.
Package Manager (system app uninstaller)
Clock (Deskclock is a fork of the AOSP clock, so it offers all its functions) Good alarm clock.
LGv20 fix image retention, aka screen burn in. shell script (root only) (shell script to fix the screen burn in aka image retention on lgv20.)
Disable find my device administrator account. (Shell script to disable device administrator account.)
Disable lock screen service administrator account. (Shell script to disable lock screen service administrator account.)
Swap memory disabler (Disable zram on lgv20 Magisk Module.)
Sleep Timer (Sleep Timer helps you fall asleep while listening to music or podcasts. When the timer stops, audio playback is gradually lowered then paused.)
[APP] CpuFloat [March27] Floating cpu, gpu, temperatures, deep sleep, network monitor (Shows cpu info and float's on the screen.)
Simple Gallery Pro (Great gallery app for all your photos.)
Build Prop Tweaks
(just copy and past every thing below in /system/build.prop file at the very bottom save and reboot. With this tweak I recommend you have zram enabled.)
# Tweaks
# better multitasking
ro.vendor.qti.sys.fw.bservice_enable=true
ro.vendor.qti.sys.fw.bservice_age=5000
ro.vendor.qti.sys.fw.bservice_limit=5
# extend battery life
wifi.supplicant_scan_interval=180
Issues I had with my lgv20
I had some issues with a magisk module called zram_manager, The apps I had open were acting funny and I had to close them and open them back up again. I don't recommend that magisk module for the lgv20. I just use the stock zram.
I was having a odd issue with the files on my sd card. My file extensions were getting renamed to .0 such as song.mp3.0 so I could not play my music. It was VLC or vanilla music player. I uninstalled both and so far the issue has not returned. For now I am just using MiXplorer to play my music and watch videos on my phone. Update so far it's been a month and no issues with the renaming of my songs.
Click to expand...
Click to collapse
Works 99%, except no data (T-Mo, AT&T H910) - modem file? Anyone else found a solution to no data? (Calls OK, just no network data)
TomJ2 said:
Works 99%, except no data (T-Mo, AT&T H910) - modem file? Anyone else found a solution to no data? (Calls OK, just no network data)
Click to expand...
Click to collapse
I have AT&T, 4G LTE data works. But if you using an AT&T phone on T-Mobile then that may be why the data is not working.
This is what I found on the internet.
Will an unlocked H910 AT&T model support T-Mobile wi-fi calling?
MORE ATT CRAP TO GET RID OF
In order to completely disable fota. i had to get rid of the following (i deleted anything in the system folder with fota in the file name):
/system/apps/lgfota
/system/etc/fota
/system/etc/terms/fota
/system/lib/libfotajni.so
/system/lib64/libfotajni.so
/system/etc/permissions/com.lge.fota.xml
There's also extra att bloatware to get rid of:
/system/app/vvm_att
/system/vendor/app/facebook-appmanager
/system/vendor/app/facebook
/system/vendor/app/directv_remote
/system/vendor/app/directv
/system/vendor/app/att_uber
The only att app you want to leave on the phone is /system/vendor/app/att_hotspots; wifi calling will not work without it.
Now, get ready for some weird stuff....
GOOGLE CRAP TO KEEP
These folders are split up among /system/app and /system/priv-app
googlepackageinstaller (keep to be able to install apk's)
googleextshared (phone boot loops without this)
googleextservices (phone boot loops without this)
webviewgoogle (aurora store at this moment seems to only work with the webview that came with the stock rom and it's browser and will work with no others)
chrome (aurora store at this moment seems to only work with the webview that came with the stock rom and it's browser and will work with no others)
Here's where it gets weirder, but if i figured it out for everyone, it wasn't easy...
GOOGLE CRAP TO GET RID OF AND KEEP WIFI CALLING FUNCTIONAL
This next part is specifically for degoogling and maintaining wifi calling without having google try to update apps the moment you get connected to wifi. I did this in two stages...
PART 1
Get rid of the following:
These folders are split up among /system/app and /system/priv-app
youtube
editors slides
editors sheets
editors docs
photos
maps
hangouts
phonesky
music
videos
google pay
gmail
latininlmegoogle
drive
calculator
velvet
driveactivator
tag
GoogleBackupTransport
GoogleContactsSyncAdapter
googlecalendarsyncadapter
google tts
hotwordenrollment (all hotword enrollment folders)
google in apps
talkback
GoogleFeedback
GooglePartnerSetup
GoogleOneTimeInitializer
SetupWizard
PART 2
After part 1 is complete
A. Boot into android.
B. Connect to wifi.
C. Activate wifi calling.
D. Verify wifi calling works (call your phone, have another phone call your phone, either or for that test).
E. Go into android settings and disable google play services and google framework, restart phone, then confirm wifi calling still works.
F. Reboot phone into twrp, remove gmscore and googleservicesframework (again, you'll find these folders among system/app and /system/priv-app).
G. Congratulations, you've degoogled as much as possible without clawing at the walls wondering why wifi calling isn't working after you degoogled.
MICROG?
Microg works very well on this phone. Microg is pretty much fake google services so you can still run normal apps from the play store.
1. Reboot into twrp and flash nanodroid patcher patckage. This patches the phone to allow signature spoofing; a requirement of microg.
2. Flash nanodroid microg package.
3. Reboot into android.
4. Open microg settings.
5. Go into "self-check" inside of microg settings, allow everything and check off all the boxes in there.
6. Get out of self-check and go into "google device registration" and turn that on.
7. Update to the latest version of aurora store since the nanodroid package include an old one.
8. Go into aurora store after you updated it, allow all it requires, keep it with the "session installer".
9. Once aurora store initial setup is complete, go into "blacklist manager" and check off all the boxes in there.
A. Aurora store will mistake microg as outdated and want to wipe it out with a google play services installation.
B. You don't want aurora store upgrading any of the android operating system files on your phone.
C. Doing this ensures that any app you install from aurora store afterward won't be blacklisted, and aurora store gets relegated for apps you installed and updates for those apps.
10. Consider installing fdroid so you can keep aurora store regularly updated with the newest version.
11. Congratulations, you've degoogled as much as possible without losing wifi calling and still run apps from the play store.
SHORTER BOOT TIME AND SHUTDOWN TIME
Delete the following to shave seconds off boot and shutdown time (your phone will have no more start up noise, turn on 5 seconds faster, and have no more shutdown animation since att's attempt at visualizing a shutdown was very odd).
/system/media/bootanimation.zip
/system/media/shutdownanimation.zip
You can actually get rid of the media folder, but do that if you don't want user interface sounds, or your typical alarm noises (and that's how you don't wake up to a silent alarm the next day if you delete this folder).

[ROM][11.0_r60]JAGUAR XPERIA XA2 ULTRA OFFICIAL V25 Updated October 18, 2022

TELEGRAM CHANNEL ADDED: HERE
TELEGRAM CHAT GROUP: HERE
I normally build roms for Oneplus devices, but one of Xperia users donated and asked to build for Xperia XA2 Ultra. XA2 Ultra doesn't have a lot of options, so, here it is:
I have been building Android roms since 2012 for various devices including multiple Sonys, Lenovo Zuk, Oneplus 3, Oneplus 5, 6, 8 and 9. You can check my Oneplus 6 or Oneplus 6T or Oneplus 8 threads and browse my profile.
Jaguar rom is focused on hardening of AndroidOS and kernel. As such, the rom has hardened bionic, art, framework and tightened security.
1 Rom control with custom Power options, Statusbar, Buttons, Navbar, Quicksettings, Lockscreen, Notifications, Gestures, Themes etc...
2. Heavily modified Art, Bionic System/Vold and System/Security
3. Telephony response to Type Zero sms ('silently acknowledged') disabled
4. Toggle to disable Captive Portal logging.
5. Speakerphone proximity sensor toggle - could be set to automatically switch to speaker when not at the ear
6. IMEI and phone numbers hidden in About menu
7. Built-in encrypted DNS providers, such as: Cloudflare (US); LibreDns (Germany); AdguardDns (Cyprus); and PowerDns (Netherlands)
8. Wakelock and Alarmblocker
9. Fully working Call recording with the button visible in Dialer
10. Deskclock app modified to work with PowerOn alarm. The app will boot the phone 2 minutes before scheduled time to trigger the alarm on time
11. Default Dark mode
12. All regular customizations plus. You tell me which feature is missing.
The rom has 2 versions Vanilla (no Gapps) and Full. So, pick according to your needs.
Install instructions
Xperia AX2 Ultra is somewhat easier to deal with (because it doesn't have virtual partitions). So, the only requirement is to be on the latest stock firmware in both slots, and unlocked bootloader, of course. If you have been using Lineageos 18-19, you already have it. If not, install stock and then use Lineage's copy-partitions zip to populate another slot.
1. Either boot official TWRP and flash the rom followed by factory reset, or boot my recovery and sideload the rom also followed by factory reset.:
The command to boot recovery (from fastboot) is simple:
fastboot boot 'recovery name' (without quotes).
The first boot might take longer, because your phone will be encrypted.
2. Magisk: only versions 24.3 and higher will pass Safetynet. However, don't use TWRP, or any other recovery, because you won't boot. Rather install Magisk as a regular app, take boot.img I provide (the same as recovery), put it on your internal storage and patch from the app. Then install the new image (Magisk will tell you where it would save it) via fastboot: fastboot flash boot boot.img.
Download rom V20.2-VANILLA: Here
Download rom V20.2-FULL: Here
Download recovery (same as boot.img): Here
All subsequent releases will be in post #3.
XDAevDB Information
JAGUAR R, ROM for Sony Xperia AX2 Ultra
Contributors
optimumpro
Kernel Source Code (for now Lineage kernel): Here
ROM OS Version: 11.x R
ROM Kernel: Linux 4.x
ROM Firmware Required: no lower than Android 11 + unlocked bootloader
Based On: AOSP/Lineage/DirtyUnicorn/Crdroid
Version Information
Status: Stable
Current Stable Version: See post #3
Stable Release Date: 2021-01-26
Created: 2021-01-29
Updated: 2022-10-18
Credit: AOSP, Lineage, DU, Crdroid, GrapheneOS, CalyxOS
Why not Android 12? Because Google's major new releases don't become stable until at least r50+. Why? Ask Google. My view is: their primary focus is on advertising revenue, hence, everything else is on the back burner.
In addition, I personally dislike Android 12 (12L): you get some minor UI changes in exchange for giving up more privacy..
Screenshots: see Here
Magisk 25 and LSposed are loading now.
October 18. New release V025:
1. October security patches
2. Android r60
3. System webview to 106.x
4. Ability to disable screenshots saving: when disabled, screenshots are taken, but not saved
Native video still doesn't work and probably will never work due to the phone's low ram
Dirty flashing is fine on a previous release
Download rom V25 VANILLA: Here
Download rom V25 FULL: Here
September 13. New release V-24: major update
1. September security patches
2. Android r59
3.Ability to change clock size in statusbar and quicksettings
4. Rom is now compatible with Magisk 25 and Lsposed
5. AOD is fully working
6. DIaler: toggle for post-call snackbar
7. System webview to 105.x
Native gallery still cannot play videos and probably won't ever, as Jaguar takes more ram than Lineage: XA's 4GB of RAM is simply not enough. Use VLC player, which works fine.
Download rom V24-VANILLA: Here
Download rom V24-FULL: Here
August 21. New release V-23
1. August security patches
2. Android r58
3. Video playing may or may not be fixed (no longer have the device)
Dirty flashing is fine on a previous release
Download rom V-23 VANILLA: Here
Download rom V-23 FULL: Here
July 8. New release V-22
1. July security patches
2. Android r57
3. Automatic sleep/suspend mode (scheduled by a user) in Settings/Battery
4. 'Internet permission missing' issue with several apps fixed. Now, all apps including Googleplay, as well as third party apps, have no problems connecting to the internet (no F/C)
5. Many under the hood improvements
Dirty flashing on top of a previous release is fine. Otherwise, clean flash.
Download rom V-22 FULL: Here
Download rom V-22 VANILLA: Here
Does miracast work in this rom, and when mirroring could it black/turn off the screen. This is possible with the stock firmware and i hope that its also possible with the jaguar rom.
July 8. New release V-22
1. July security patches
2. Android r57
3. Automatic sleep/suspend mode (scheduled by a user) in Settings/Battery
4. 'Internet permission missing' issue with several apps fixed. Now, all apps including Googleplay, as well as third party apps, have no problems connecting to the internet (no F/C)
5. Many under the hood improvements
Download in post #3.
Newpipe does not work and possibly other videoplayback applications, doesn 't work in the browser . Only YouTube video plays. And could you integrate audio boost Ainur narsil, Viper or Sound Enhancement Sony Xperia 10 and then magisk is not needed
​
TheStormRanger said:
Newpipe does not work and possibly other videoplayback applications, doesn 't work in the browser . Only YouTube video plays. And could you integrate audio boost Ainur narsil, Viper or Sound Enhancement Sony Xperia 10 and then magisk is not needed
​
Click to expand...
Click to collapse
That's because you are using MicroG and you have NOT enabled 'signature spoofing' in Settings/Privacy. Most Google apps will NOT work with MicroG, unless signature spoofing is enabled.
optimumpro said:
That's because you are using MicroG and you have NOT enabled 'signature spoofing' in Settings/Privacy. Most Google apps will NOT work with MicroG, unless signature spoofing is enabled.
Click to expand...
Click to collapse
I am using the full version 22. Everything is already installed there. Changing the settings doesn't help. Newpipe and other software always work without Google services and MicroG. It's sad that not all software works. Your firmware is good, including Bluetooth and security tweaks
TheStormRanger said:
I am using the full version 22. Everything is already installed there. Changing the settings doesn't help. Newpipe and other software always work without Google services and MicroG. It's sad that not all software works. Your firmware is good, including Bluetooth and security tweaks
Click to expand...
Click to collapse
The same for me. Video playback doesn't work. I don't have microg installed. Even the video stored on the phone, or the video recorded with the camera doesn't work. Other than that, everything seems to be working great.
Sorry for my English...
My problem is cannot use Video Playing (From Facebook and other app)
If I play video , it show only black screen . How to fix it
[email protected] said:
Sorry for my English...
My problem is cannot use Video Playing (From Facebook and other app)
If I play video , it show only black screen . How to fix it
TheStormRanger said:
I am using the full version 22. Everything is already installed there. Changing the settings doesn't help. Newpipe and other software always work without Google services and MicroG. It's sad that not all software works. Your firmware is good, including Bluetooth and security tweaks
Click to expand...
Click to collapse
branja6 said:
The same for me. Video playback doesn't work. I don't have microg installed. Even the video stored on the phone, or the video recorded with the camera doesn't work. Other than that, everything seems to be working great.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
One of you would have to post a logcat running when you are trying to play videos.
optimumpro said:
One of you would have to post a logcat running when you are trying to play videos.
Click to expand...
Click to collapse
Ok, I installed a clean V22 full and a Newpipe app. And I attach the logcat. Newpipe works fine on the original firmware and Lineage and others
branja6 said:
The same for me. Video playback doesn't work. I don't have microg installed. Even the video stored on the phone, or the video recorded with the camera doesn't work. Other than that, everything seems to be working great.
Click to expand...
Click to collapse
So far the workaround to an extent is using VLC media player, so this may be some type of codec issue... Hopefully it can be resolved soon
August 21. New release V-23
1. August security patches
2. Android r58
3. Video playing may or may not be fixed (no longer have the device)
Download in post #3.
How long is the first load? I feel like it's been loading for a long time now. At least 10 minutes. Installed in twrp the latest version, was coming from stock 8. Didn't read I needed firmware 11+ until just now. Do I just wait for the phone battery to die and try again? I had planned on installing Magisk after boot, but at this point I'm not sure it is even going to boot.
rjdeleon said:
How long is the first load? I feel like it's been loading for a long time now. At least 10 minutes. Installed in twrp the latest version, was coming from stock 8. Didn't read I needed firmware 11+ until just now. Do I just wait for the phone battery to die and try again? I had planned on installing Magisk after boot, but at this point I'm not sure it is even going to boot.
Click to expand...
Click to collapse
You can always shutdown the phone by pressing 'power key' and 'volume up and down' together for 5-10 seconds.
TWRP doesn't flash well and certainly doesn't work when flashing Magisk (you'll get bootloop).
Don't use V23. Use V22. Get recovery from post #1 and flash it in fastboot like this:
fastboot flash boot_a boot.img
then
fastboot flash boot_b boot.img
Disconnect the phone and start it in recovery by pressing 'power button' and 'volume down' at the same time. Once in recovery, wipe system, then side load V22.
optimumpro said:
You can always shutdown the phone by pressing 'power key' and 'volume up and down' together for 5-10 seconds.
TWRP doesn't flash well and certainly doesn't work when flashing Magisk (you'll get bootloop).
Don't use V23. Use V22. Get recovery from post #1 and flash it in fastboot like this:
fastboot flash boot_a boot.img
then
fastboot flash boot_b boot.img
Disconnect the phone and start it in recovery by pressing 'power button' and 'volume down' at the same time. Once in recovery, wipe system, then side load V22.
Click to expand...
Click to collapse
Thank you, in recovery now about to sideload the V22, then I will reboot into the system and then reboot into recovery and sideload the V23 on top. Should I install Magisk before the V23? Or just go straight into V22 to V23? Again, thank you for responding.
rjdeleon said:
Thank you, in recovery now about to sideload the V22, then I will reboot into the system and then reboot into recovery and sideload the V23 on top. Should I install Magisk before the V23? Or just go straight into V22 to V23? Again, thank you for responding.
Click to expand...
Click to collapse
Don't use v23. I will post v24 tomorrow. I described how to apply Magisk in the OP.
ugh, unfortunately cannot sideload to it for some reason:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I am in ADB Sideload though so who knows, maybe I need to switch computers.
rjdeleon said:
ugh, unfortunately cannot sideload to it for some reason:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I am in ADB Sideload though so who knows, maybe I need to switch computers.
Click to expand...
Click to collapse
That means there is no connection between your phone and pc. May be adb drivers etc. Try to open the terminal as administrator.

Categories

Resources