Related
UPDATE 06 OCT 2019: I will be returning to the project next week...
Apologies for my long silence over the past few months. After the initial release of this ROM I started focusing on getting the fingerprint sensor to work, which after some struggle I got it working. I then began spending time on removing non-FLOSS apps, services and providers that comes with lineageOS and replacing them with even better FLOSS alternatives. I made some good progress on this and created an automated build script for this. I also wanted to make the installation of the ROM easier, so I even created a script that automates the entire flashing procedure for you....yip...it's pretty cool On the security side I also made some good progress: I've applied several recommended hardening patches to the base system, and also patched the flawed mac-address randomization implementation that still exists in android today.
As I got close to preparing for release, google decided to stop support for maps-api V1 which is used by migrog. This completely broke all map views in apps and even started crashing the mobile browser. Because of the complexity of the android build workflow and tool-chain, I initially thought I screwed something up, but it was only after a couple of days of pulling my hair out people started reporting it on github. I had to wait for the mapbox implementation of microg to be released, and it eventually came a few weeks later.
It was shortly after the release that my personal priorities changed. I've been occupied (visa related) with that ever since but I'm happy to report that I should be able to return back to the project next week. Obviously some time has passed, so I will have to get up to speed with the latest releases of all of the repos and get that merged with my local changes, but that should only take a day. Hopefully there won't be many breaking changes, and if that is the case then I should be in a position to release V2 in about two weeks!
Cheers,
fanix (git-repo here: https://github.com/FaN11X?tab=repositories). Once you see commits you'll know I've started.
New build is available apparently.... don't know if it's the same dev..
UPDATE 08 MAY 2019: I'm in the process of adding support for the in-display fingerprint sensor. Stay tuned.
This is a lineageos 16.0 build from source on 25 April using latest source. The ROM is has been prepatched for system lavel signature spoofing based on the MicroG Android Pie patch (url removed, sigh). I did however change the protection level from "Dangerous" to "Signature|Restricted". This is a more secure way of enable signature patching as it requires the app using signature spoofing to be privaliaged, in other words, it needs to be installed to /system/priv-app in order for it to be granted this permission. This means that you wont be at risk of downloading and installing apps that might abuse signature spoofing.
The ROM also passes FULL SafetyNet with microg installed. It uses a custom build from Nanadroid which contains all the latest code changes which you wont find in there official releases as its not yet been packaged as a release. This solved many issues for me, like safetyNet now passing which allows me to install and run banking applications (like Barclay's Mobile Banking) and also uber seems to work just fine using the UnifiedNLP backend providers.
This custom ROM has NO google related apps or code, and you have the ability to switch on google released integration services through the microg services menu.
WORKING
So far... everything I've tested. (except fingerprint)
NOT WORKING
On-display fingerprint.
Installation steps:
1. Restore to stock firmware. I recommend the following Fastboot ROM as thats the one I used. *url removed* (download file search google "equuleus global images V10.2.2.0.PECMIXM")
2. Put device in fastboot mode (adb reboot bootloader or Power Button + Vol Down)
3. Flash using MiFlash (Find it on google and be sure to select the "FLASH ALL.bat" option at the bottom and NOT the LOCK on, otherwise you will relock your device)
4. After flashing the stock ROM, let it boot up, then enable developer options and USB debugging.
5. Flash TWRP
* adb reboot bootloader
* fastboot erase recovery
* fastboot flash TWRP_equuleus_1102.img
* fastboot boot TWRP_equuleus_1102.img
6. Once in TWRP, goto WIPE and select DATA. Enter the word "yes" and once it is complete, go back to main menu, RESTART=>RECOVERY to reboot and automatically boot back into recovery.
7. Goto WIPE again, but this time WIPE DalvicCache, SYSTEM & Cache by selecting all 3 and wiping them (NO NOT RESTART AFTER THIS STEP
8. Once wipe is complete, push the content from the download folder provided below to the sdcard folder of the phone.
* adb push download_folder_containing_all_the_files /sdcard/
example: adb push /home/fanix/Downloads/lineageosrom /sdcard/
9. Once complete, you are now ready to flash lineage ROM. Select the lineageos zip file and flash it. (filename => lineage-16.0-20190425-UNOFFICIAL-equuleus.zip)
10. Once complete, you can then reboot to system to load lineage. After going through the lineage setup, you can then install microg (if you want)
Optional - Installing microg (from latest nanodroid) FULL SAFETYNET SUPPORTED
* Boot into TWRP (adb reboot recovery)
* Goto INSTALL, and select the following file: (NanoDroid-microG-20.7.92.20190424.zip).
* NOTE: This will install microg, including MsfProxy and UnifiedNLP with 4 backend providers. It will also install Aurora Store & Fake store.
* When install is complete, reboot and once in lineage, you can configure microg. You can log into google store using Aurora, either with your own account or their anonymised account. This allows you to download anything form the google app store, including apps that require verification, like mobile banking apps.
* If you want, you can test your SafetyNET using Magisk. You can find the magisk manager in the download folder. Install that and test SafetyNET. You do NOT need to root your phone to test this, you can simply install the manager. If you want to root your phone, simply boot back into TWRP and select the magisk 19.0 zip file and that will then also root your device.
Enjoy!
DOWNLOAD LINK:
https://drive.google.com/open?id=1aJ...bkaHPw86sgHYMj
I've contacted one of the mods and asked if thye could post the link. Hope they do, otherwise if someone has the ability to post links then message me and i'll PM you the download link which you can then share to the thread.
Cheers
fanix
Hi fanix-uk,
Thank you very much! Is 3D face recognition working or just the 2d with the front camera?
mateHD said:
Hi fanix-uk,
Thank you very much! Is 3D face recognition working or just the 2d with the front camera?
Click to expand...
Click to collapse
Not sure, I haven't tried it. To be honest I've never used that feature on this phone before.
fanix-uk said:
Not sure, I haven't tried it. To be honest I've never used that feature on this phone before.
Click to expand...
Click to collapse
I tried it. Face unlock works with google smartlock. It use IR sensor, not the front camera, but it isn't 3D. So it works without light, but less secure than the stock rom version.
Btw. the rom works perfectly. Thanks again.
Is possible to have the miui camera with this rom?
mateHD said:
I tried it. Face unlock works with google smartlock. It use IR sensor, not the front camera, but it isn't 3D. So it works without light, but less secure than the stock rom version.
Btw. the rom works perfectly. Thanks again.
Click to expand...
Click to collapse
You are most welcome! Thanks for testing it... I'm working on a new release with some really cool features, including
Updated, hardened kernel.
Wireguard kernel module built into kernel.
Removal of non-FOSS apps/providers/services and replace with FOSS alternatives
Weather provider integration with openweathermap.
In-display fingerprint
perillo95 said:
Is possible to have the miui camera with this rom?
Click to expand...
Click to collapse
I can try and grab the camera app and drivers from stock and package it for you, but won't be including proprietary software in this build. I'll keep you posted.
fanix-uk said:
You are most welcome! Thanks for testing it... I'm working on a new release with some really cool features, including
Updated, hardened kernel.
Wireguard kernel module built into kernel.
Removal of non-FOSS apps/providers/services and replace with FOSS alternatives
Weather provider integration with openweathermap.
In-display fingerprint
Click to expand...
Click to collapse
Looking forward to it. I will probably try the current version as soon as I'm allowed to unlock my bootloader.
fanix-uk said:
I can try and grab the camera app and drivers from stock and package it for you, but won't be including proprietary software in this build. I'll keep you posted.
Click to expand...
Click to collapse
With miui camera and the in-display fingerprint would be a perfect ROM, Great work
thanks a lot for LOS!
Q: do i need to install gapps after ROM?
eerastov said:
thanks a lot for LOS!
Q: do i need to install gapps after ROM?
Click to expand...
Click to collapse
Yes.
Whats up with the new version? Can i help somehow?
Thanks
Hi Fanix
I really appreciate what you have done for Mi8 Pro. If you did not share your work here, I think I nearly sell my phone, as the MIUI is pretty trash.
Also, thanks for your progress on adding in-display finger sensor, after you done it I feel you can create one link for donation. I really hope you can keep develop on this phone and make LOS Andorid Q available in the future.
Kind regards
One of Mi8 Pro users
---------- Post added at 07:51 AM ---------- Previous post was at 07:47 AM ----------
I flashed this rom on my phone, it works really well. And I flashed a Gapps on my phone, work well as well. I did not flash the Nanadroid on my phone, is it necessary? I just worry about it becasue you said something related to SafetyNet, ahaha. I do not know if I do not have it, is my phone still safe?
Thanks a lot again.
fanix-uk said:
UPDATE 08 MAY 2019: I'm in the process of adding support for the in-display fingerprint sensor. Stay tuned.
This is a lineageos 16.0 build from source on 25 April using latest source. The ROM is has been prepatched for system lavel signature spoofing based on the MicroG Android Pie patch (url removed, sigh). I did however change the protection level from "Dangerous" to "Signature|Restricted". This is a more secure way of enable signature patching as it requires the app using signature spoofing to be privaliaged, in other words, it needs to be installed to /system/priv-app in order for it to be granted this permission. This means that you wont be at risk of downloading and installing apps that might abuse signature spoofing.
The ROM also passes FULL SafetyNet with microg installed. It uses a custom build from Nanadroid which contains all the latest code changes which you wont find in there official releases as its not yet been packaged as a release. This solved many issues for me, like safetyNet now passing which allows me to install and run banking applications (like Barclay's Mobile Banking) and also uber seems to work just fine using the UnifiedNLP backend providers.
This custom ROM has NO google related apps or code, and you have the ability to switch on google released integration services through the microg services menu.
WORKING
So far... everything I've tested. (except fingerprint)
NOT WORKING
On-display fingerprint.
Installation steps:
1. Restore to stock firmware. I recommend the following Fastboot ROM as thats the one I used. *url removed* (download file search google "equuleus global images V10.2.2.0.PECMIXM")
2. Put device in fastboot mode (adb reboot bootloader or Power Button + Vol Down)
3. Flash using MiFlash (Find it on google and be sure to select the "FLASH ALL.bat" option at the bottom and NOT the LOCK on, otherwise you will relock your device)
4. After flashing the stock ROM, let it boot up, then enable developer options and USB debugging.
5. Flash TWRP
* adb reboot bootloader
* fastboot erase recovery
* fastboot flash TWRP_equuleus_1102.img
* fastboot boot TWRP_equuleus_1102.img
6. Once in TWRP, goto WIPE and select DATA. Enter the word "yes" and once it is complete, go back to main menu, RESTART=>RECOVERY to reboot and automatically boot back into recovery.
7. Goto WIPE again, but this time WIPE DalvicCache, SYSTEM & Cache by selecting all 3 and wiping them (NO NOT RESTART AFTER THIS STEP
8. Once wipe is complete, push the content from the download folder provided below to the sdcard folder of the phone.
* adb push download_folder_containing_all_the_files /sdcard/
example: adb push /home/fanix/Downloads/lineageosrom /sdcard/
9. Once complete, you are now ready to flash lineage ROM. Select the lineageos zip file and flash it. (filename => lineage-16.0-20190425-UNOFFICIAL-equuleus.zip)
10. Once complete, you can then reboot to system to load lineage. After going through the lineage setup, you can then install microg (if you want)
Optional - Installing microg (from latest nanodroid) FULL SAFETYNET SUPPORTED
* Boot into TWRP (adb reboot recovery)
* Goto INSTALL, and select the following file: (NanoDroid-microG-20.7.92.20190424.zip).
* NOTE: This will install microg, including MsfProxy and UnifiedNLP with 4 backend providers. It will also install Aurora Store & Fake store.
* When install is complete, reboot and once in lineage, you can configure microg. You can log into google store using Aurora, either with your own account or their anonymised account. This allows you to download anything form the google app store, including apps that require verification, like mobile banking apps.
* If you want, you can test your SafetyNET using Magisk. You can find the magisk manager in the download folder. Install that and test SafetyNET. You do NOT need to root your phone to test this, you can simply install the manager. If you want to root your phone, simply boot back into TWRP and select the magisk 19.0 zip file and that will then also root your device.
Enjoy!
DOWNLOAD LINK:
https://drive.google.com/open?id=1aJ...bkaHPw86sgHYMj
Click to expand...
Click to collapse
hello I have tried treble version but i got MusicFX Force Close i hope you can fix this
and maybe you can port Miui Camera on this ROM thanks for your work
I found a bug :
NFC is not found in Settings and NFC Icon on status bar is error
Edit :
sometimes when opening the camera, freeze and got pop-up cannot be connected to the camera
And for musicFX is working...
Thanks
fanix-uk said:
UPDATE 08 MAY 2019: I'm in the process of adding support for the in-display fingerprint sensor. Stay tuned.
This is a lineageos 16.0 build from source on 25 April using latest source. The ROM is has been prepatched for system lavel signature spoofing based on the MicroG Android Pie patch (url removed, sigh). I did however change the protection level from "Dangerous" to "Signature|Restricted". This is a more secure way of enable signature patching as it requires the app using signature spoofing to be privaliaged, in other words, it needs to be installed to /system/priv-app in order for it to be granted this permission. This means that you wont be at risk of downloading and installing apps that might abuse signature spoofing.
The ROM also passes FULL SafetyNet with microg installed. It uses a custom build from Nanadroid which contains all the latest code changes which you wont find in there official releases as its not yet been packaged as a release. This solved many issues for me, like safetyNet now passing which allows me to install and run banking applications (like Barclay's Mobile Banking) and also uber seems to work just fine using the UnifiedNLP backend providers.
This custom ROM has NO google related apps or code, and you have the ability to switch on google released integration services through the microg services menu.
WORKING
So far... everything I've tested. (except fingerprint)
NOT WORKING
On-display fingerprint.
Installation steps:
1. Restore to stock firmware. I recommend the following Fastboot ROM as thats the one I used. *url removed* (download file search google "equuleus global images V10.2.2.0.PECMIXM")
2. Put device in fastboot mode (adb reboot bootloader or Power Button + Vol Down)
3. Flash using MiFlash (Find it on google and be sure to select the "FLASH ALL.bat" option at the bottom and NOT the LOCK on, otherwise you will relock your device)
4. After flashing the stock ROM, let it boot up, then enable developer options and USB debugging.
5. Flash TWRP
* adb reboot bootloader
* fastboot erase recovery
* fastboot flash TWRP_equuleus_1102.img
* fastboot boot TWRP_equuleus_1102.img
6. Once in TWRP, goto WIPE and select DATA. Enter the word "yes" and once it is complete, go back to main menu, RESTART=>RECOVERY to reboot and automatically boot back into recovery.
7. Goto WIPE again, but this time WIPE DalvicCache, SYSTEM & Cache by selecting all 3 and wiping them (NO NOT RESTART AFTER THIS STEP
8. Once wipe is complete, push the content from the download folder provided below to the sdcard folder of the phone.
* adb push download_folder_containing_all_the_files /sdcard/
example: adb push /home/fanix/Downloads/lineageosrom /sdcard/
9. Once complete, you are now ready to flash lineage ROM. Select the lineageos zip file and flash it. (filename => lineage-16.0-20190425-UNOFFICIAL-equuleus.zip)
10. Once complete, you can then reboot to system to load lineage. After going through the lineage setup, you can then install microg (if you want)
Optional - Installing microg (from latest nanodroid) FULL SAFETYNET SUPPORTED
* Boot into TWRP (adb reboot recovery)
* Goto INSTALL, and select the following file: (NanoDroid-microG-20.7.92.20190424.zip).
* NOTE: This will install microg, including MsfProxy and UnifiedNLP with 4 backend providers. It will also install Aurora Store & Fake store.
* When install is complete, reboot and once in lineage, you can configure microg. You can log into google store using Aurora, either with your own account or their anonymised account. This allows you to download anything form the google app store, including apps that require verification, like mobile banking apps.
* If you want, you can test your SafetyNET using Magisk. You can find the magisk manager in the download folder. Install that and test SafetyNET. You do NOT need to root your phone to test this, you can simply install the manager. If you want to root your phone, simply boot back into TWRP and select the magisk 19.0 zip file and that will then also root your device.
Enjoy!
DOWNLOAD LINK:
https://drive.google.com/open?id=1aJ...bkaHPw86sgHYMj
Click to expand...
Click to collapse
Current anything is good ！
thanks a lot again
Any news plss
Any news?
Still others are maintaining this rom, looking forward to updating
I was willing to bring up the rest of the hardware and make this device official, but I don't have the device. Is there any interest in donating a device for such purpose?
bgcngm said:
I was willing to bring up the rest of the hardware and make this device official, but I don't have the device. Is there any interest in donating a device for such purpose?
Click to expand...
Click to collapse
Would love to be in a position to do that. However, I have just had my OnePlus 6T stolen, and now need my Mi 8 Pro as a daily driver. Would be happy to donate to get the fingerprint reader working on AOSP / GSI-Treble ROMs for the MI 8 Pro.
Hi All. Just thought I'd quickly mention the method of updating OOS if you are rooted for anyone new to this or to anyone who's forgotten.
Disclaimer: This works for me, I've just done it. Backup your phone just in case. I'm not responsible for your actions or the consequences of your actions. You merely adopted the dark, I was born into it etc etc.
Process:
1- Disable or uninstall all Magisk modules and Overlays (Substratum etc). Otherwise you may end up in a bootloop.
2- Download the FULL version of the ROM (it will be around 2gb). Make sure it's the correct version for your device/region. (eg Global, EU, India etc).
3- Move the downloaded file to your internal storage (root directory).
4- Open the system update app under Settings -> System -> System Updates.
5- Select the cog icon at the top left and select Local Upgrade.
6- Choose the file you've downloaded and let the phone update.
7- DO NOT REBOOT!
8- Open Magisk Manager and select Install (for Magisk not Magisk Manager)
9- Select Install and on the next popup screen make sure you select Install to Inactive Slot (After OTA).
10- Reboot after Magisk has installed
11- Profit :good:
Works great as usual. Thanks.
bowlandspoon said:
Hi XDA peeps. Just thought I'd quickly mention the method of updating OOS if you are rooted for anyone new to this or to anyone who's forgotten.
Disclaimer: This works for me, I've just done it. Backup your phone just in case. I'm not responsible for your actions or the consequences of your actions. You merely adopted the dark, I was born into it etc etc.
Process:
1- Download the FULL version of the ROM (it will be around 2gb). Make sure it's the correct version for your device/region. (eg Global, EU, India etc)
2- Move the downloaded file to your internal storage (root directory).
3- Open the system update app under Settings -> System -> System Updates.
4- Select the cog icon at the top left and select Local Upgrade.
5- Choose the file you've downloaded and let the phone update.
6- DO NOT REBOOT!
7- Open Magisk Manager and select Install (for Magisk not Magisk Manager)
8- Select Install and on the next popup screen make sure you select Install to Inactive Slot (After OTA).
9- Reboot after Magisk has installed
10- Profit :good:
Click to expand...
Click to collapse
Don't forget to disable or uninstall all magisk modules and overlays (Substratum etc). Otherwise you can end in a bootloop.
xx00xx1990 said:
Don't forget to disable or uninstall all magisk modules and overlays (Substratum etc). Otherwise you can end in a bootloop.
Click to expand...
Click to collapse
Thanks, will add this to OP.
FLAWLESS PROCESS! Thank you!
Sent from my IN2025 using Tapatalk
Just because the "uninstall all magisk modules" seemed to be something passed from long time ago, I tried without touching the modules at all. Booted just fine. Feel free to not disable any modules and try that way. Will save you time
Cubox. said:
Just because the "uninstall all magisk modules" seemed to be something passed from long time ago, I tried without touching the modules at all. Booted just fine. Feel free to not disable any modules and try that way. Will save you time
Click to expand...
Click to collapse
And just because your modules didnt cause bootloop everyone elses dont either? Dont spread misinformation
pyry666 said:
And just because your modules didnt cause bootloop everyone elses dont either? Dont spread misinformation
Click to expand...
Click to collapse
First of all, I'm not spreading misinformation. I'm just telling about my experience. Any user who has a bootloop after upgrading without disabling modules can easily remove them from recovery (after flashing the one with adb enabled). This step to disable all modules is not mandatory for everyone and will make you waste time for nothing.
Second, if the argument is that because some users might get a bootloop, why not just do a data wipe every time you upgrade as well? Being overly cautious can be useful in some situations, but not here. If you get a bootloop, you can fix it easily. If you don't, you saved 10-20m from your life reinstalling everything.
pyry666 said:
And just because your modules didnt cause bootloop everyone elses dont either? Dont spread misinformation
Click to expand...
Click to collapse
This has happened to me on several different devices. I never do an update without disabling my magisk modules.
I've done this 4 times now with zero issues:
Take system update from OnePlus in settings and install as well.
Don't reboot
Reinstall magisk on main slot, then inactive slot from inside the magisk app.
Reboot
That's it.
My 2 cents. The Call Recorder module has been the culprit of the bootloop in my experience.
I had bootloop using these steps bellow:
1- Disabled all Magisk modules.
2- Downloaded the FULL version of the ROM (around 2gb).
3- Used Local Upgrade.
4- Waited and let the phone update.
5- I did not reboot
6- Opened Magisk Manager and Installed it to Inactive Slot
7- Rebooted
8- Worked everyting ok after reboot (root persisted)
9- Reenabled magisk modules
10- Rebooted
11- BOOTLOOP
12- I disabled all modules via TWRP and then system booted correctly.
13- Uninstalled all modules and installed them again.
I had the Call Recorder module so I may cause the bootloop. I think the safest method is to uninstall all modules before update and then install it again after successful update
<3
Just wanted to say, thank you so much for this guide
It's been a while since I last rooted my 7t. Current oos 10.3.6. Magisk manager v8.0.3. Magisk was 20.4 I think.
So fetch rewards app detected root. I went to add the app to the magisk hide, cleared fetch rewards storage and still root was detected. Tried to run the rename option in the magisk settings but it appears to hang during the process. Phone screen timed out and when I get back into it, the hide magisk manager status pop up was still there. Rebooted the phone, went back to magisk manager. While magisk manager shows it's still installed, magisk is not. Safety net checks still passed.
To reinstall magisk, I need to get the patched oos image, correct?
Thanks
Hi
Think from the magisk manager app you would just install to inactive slot and reboot?
Refer to the Magisk root for 7T thread for patched boot image and instructions.
When I installed a root checker, it showed that I'm still rooted.
All this started when I used the Magisk function to repackage magisk's file name in an attempt to hide it from Fetch Rewards.
noodlenoggan said:
When I installed a root checker, it showed that I'm still rooted.
All this started when I used the Magisk function to repackage magisk's file name in an attempt to hide it from Fetch Rewards.
Click to expand...
Click to collapse
Ok I don't know what I'm missing but I can't seem to find that fetch rewards app in my play store to install and test at my end. Second, Magisk isn't installed according to you manager screenshot... So I'm at a loss. But their are threads better able to assist your efforts to have Magisk root up and running first cause I not knowledgeable enough to state why your root check detects root yet the manager does not indicate root installed.
But I'll hopefully be of more help and provide you this:
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
So I'll copy and paste from the link above:
HOW TO UPDATE a ROM and KEEP ROOT:
Before all Disable all magisk modules
Be sure to use Canary Magisk Manager and Canary Magisk (debug)
You can update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- In Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
So from thier I'd assume you need only the following:
- Open Magisk Manager;
- In Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
But I am unsure so please verify b4 attempting.
Or may be someone else can confirm here?
Good luck and please consider letting me know how you made out. Thanks
I jumped on the xda magisk support forum and was able to sort out the whole mess I was in.
The android app is called Fetch - Receipts Scanner by Fetch Rewards. It's in Google store.
Hopefully for anyone else that is in the same situation will find their solution as I did below.
What I learned from the Magisk forum and closer examination of my phone were:
- Magisk and Magisk Manager are two separate components. Magisk handles the root and Magisk Manager handles additional root related features. Magisk Manager is not required to have a rooted phone continued to be rooted. I was not aware of this.
- When the repackaging routine was started, Magisk Manager did indeed repackaged and installed itself. There was not indication that the process completed successfully as the spinning progress icon did not stop. I had renamed it MagMan as part of the repackaging routing and was expecting the original icon Magisk icon to show for MagMan. Sorry, I had not read the Magisk Manager instructions and simply made a lot of assumptions of the repackaged process. What happened was that I assumed Magisk Manager would just switch over the new name as part of the repackaging routine. Also I didn't pay close enough attention that the new repackaged app, MagMan, which was literally next to Magisk Manager mainly because it had a generic Android icon instead of the Magisk Manager icon and was overlooked. This whole entire time, I was focusing on the original Magisk Manager app and icon but all of the functionality of Magisk Manager now resided in MagMan. I've uninstalled the original Magisk Manager app and now use the repackaged version.
The Fetch Rewards app was added to the Magisk Hide section via MagMan and it's now working properly.
Thanks for following up.
noodlenoggan said:
Thanks
Click to expand...
Click to collapse
Sweet - glad you have success. Enjoy
I just did more or less the same thing... Hid Magisk manager... Forgot... Flashed full update no prob... Installed new Magisk Manager (along with the previously hidden install of Magisk manager).
Then finally figured out to uninstall the hidden Magisk manager... Then, Magisk manager and was able to install Magisk Root. All good now lol. Glad your up and running.
This worked for me yesterday, but make sure to reboot the phone after doing the "hide magisk" option in Magisk Manager settings. The name also does not have to be "MagMan" it can be anything of your choice.
I also noticed that the proxy app (with blank icon) might not open but if it fails to open just force close it and try again, that seemed to make it open for me.
noodlenoggan said:
I jumped on the xda magisk support forum and was able to sort out the whole mess I was in.
The android app is called Fetch - Receipts Scanner by Fetch Rewards. It's in Google store.
Hopefully for anyone else that is in the same situation will find their solution as I did below.
What I learned from the Magisk forum and closer examination of my phone were:
- Magisk and Magisk Manager are two separate components. Magisk handles the root and Magisk Manager handles additional root related features. Magisk Manager is not required to have a rooted phone continued to be rooted. I was not aware of this.
- When the repackaging routine was started, Magisk Manager did indeed repackaged and installed itself. There was not indication that the process completed successfully as the spinning progress icon did not stop. I had renamed it MagMan as part of the repackaging routing and was expecting the original icon Magisk icon to show for MagMan. Sorry, I had not read the Magisk Manager instructions and simply made a lot of assumptions of the repackaged process. What happened was that I assumed Magisk Manager would just switch over the new name as part of the repackaging routine. Also I didn't pay close enough attention that the new repackaged app, MagMan, which was literally next to Magisk Manager mainly because it had a generic Android icon instead of the Magisk Manager icon and was overlooked. This whole entire time, I was focusing on the original Magisk Manager app and icon but all of the functionality of Magisk Manager now resided in MagMan. I've uninstalled the original Magisk Manager app and now use the repackaged version.
The Fetch Rewards app was added to the Magisk Hide section via MagMan and it's now working properly.
Thanks for following up.
Click to expand...
Click to collapse
This worked for me yesterday on Android 9 (OP5T), but make sure to reboot the phone after doing the "hide magisk" option in Magisk Manager settings. The name of the proxy app also does not have to be "MagMan" it can be anything of your choice.
I also noticed that sometimes the proxy app didn't open and if this occurred I just force closed it and then it seemed to work. Anyways good luck hope it works for someone else
How to root and pass SafetyNet on Sony Xperia 10 III (XQ-BT52)Tested on firmware 62.0.A.3.163.
Disclaimer:
This guide assumes you're familiar with the concepts of rooting, Magisk, SafetyNet, fastboot, adb and so on. I will explain why things are done but if I explained everything it would become too long.
This guide is limited to getting root and apps working on the stock Sony ROM. It doesn't cover installing other ROMs.
You can mess up your phone if you don't know what you're doing. This is not a beginner's guide.
Before you do anything else, do these preparations:
Make sure your device is updated to the latest firmware. Getting updates after you unlock the bootloader will be more complicated.
Use XperiFirm to grab a copy of your current firmware (after you've updated it). It can run on Linux too, either via Mono or in a virtual machine. It's basically just a downloader, it doesn't need any fancy hardware access.
Screenshot everything under Settings > System.
Open the dialer and enter *#*#7378423#*#*. Screenshot everything in the service submenus.
Unlock developer options (tap Settings > About > Build number 7 times) then find it under Settings > System > Advanced. Activate USB debugging. Activate OEM unlocking.
Install the Android SDK Platform Tools. On Linux they're most likely in a package provided by your distro.
Copy the screenshots to your PC because the phone will be reset at some point.
Boot into fastboot by turning the phone off, then connect it to PC via USB, and press POWER and VOLUME UP together. The phone led will turn blue. On PC run fastboot devices and make sure it lists your phone and has the serial number you got from the service menu.
Unlocking the bootloader:
This is the point of no return as far as warranty is concerned!
This will factory reset the phone! Make sure you got everything you needed off it.
Obtain the unlock code (you will need the IMEI of the 1st SIM slot).
Boot into fastboot, check again that fastboot devices lists the phone.
Issue the unlock command using the code you got earlier: fastboot oem unlock 0x<unlock code here>
Reboot the phone (you can say fastboot reboot). It will say "can't check for corruption" and "erasing" a couple of times but will eventually boot up to the factory setup.
Enabling Magisk & root:
Download the latest Magisk apk to the phone and install it. Right now that means v24+.
Open boot_X-FLASH-ALL-8A63.sin from the original firmware with any archive manager (it's a tar.xz), 7zip will work fine.
Extract boot.000, rename it to boot.img and put it on the phone.
Open the Magisk app, next to "Magisk" tap "install", choose "Select and patch a file", pick the "boot.img" file.
Download the patched img to PC (will be next to boot.img called something like magisk_patched-24100_MKPRJ.img).
Boot into fastboot, check again that fastboot devices lists the phone.
Flash the patched boot image: fastboot flash boot magisk_patched-24100_MKPRJ.img
Must say OKAY. Can then reboot the phone (you can say fastboot reboot).
Open the Magisk app again, it should say "installed" now next to "Magisk". Also the Superuser and Modules buttons should now be enabled.
Go into Magisk settings and activate "Hide the Magisk app". This is NOT MagiskHide, it does not hide Magisk from other apps, it hides the Magisk Manager app from other apps. More on this later.
Go into Magisk settings and activate Zygisk. This is a built-in replacement for Riru going forward.
Reboot!
Install a root checker app and verify that you get a prompt from Magisk to give root and that the checker says it got root.
Important changes about Magisk:
Riru is now obsolete. It has been replaced by a feature built-into Magisk called Zygisk (which is essentially Riru running in Zygote). It is strongly recommended to go into Magisk settings and activate Zygisk (even if you don't use Riru modules). Do not install Riru anymore. All modules that needed Riru should have Zygisk versions by now unless they're abandoned.
Magisk no longer maintains a module repository, To find and install modules install Fox's Magisk Module Manager. It's a dedicated module management app that supports the old Magisk repo as well as new ones. Inside Magisk you can still enable/disable/remove/install manually and can also update if the module has an update URL, so you can do without Fox if you get your modules directly from their XDA or GitHub pages.
MagiskHide has been replaced by a new feature called Deny list (it's in Magisk settings). It's much more powerful because the apps & processes added to the deny list will be completely excluded from anything based on Magisk so it's impossible for them to detect leaks anymore. On the downside, excluded apps can't be affected by any Magisk or LSPosed modules (LSPosed will grey out such apps and say "it's on the deny list".) This feature should be used sparingly (see below) because Magisk still does a good job of evading detection.
Passing SafetyNet:
Install YASNAC to check your SafetyNet status. At this point you're probably not passing either Basic or CTS check.
Go into Magisk settings. Enable "Enforce deny list". Enter "Configure deny list", find Google Services, check it, expand it, and select only the process ending in .gms and the one ending in .gms.unstable.
Reboot. Check YASNAC. At this point you should be passing Basic check but probably not CTS.
Install Universal SafetyNet Fix (aka USNF) by kdrag0n in Magisk. (Some GIS ROMs already include what this module does, so if you install a GIS ROM you may not need it.) This module hijacks the CTS verification and drops an error which causes the Google service to fall back to Basic verification, which we already fixed in the previous step.
Reboot. Check YASNAC. At this point you should be passing both Basic and CTS. That's it!
You may need to clear storage & cache for Google Play & Services. Go to Settings > Apps & notifications > See all apps, select "All apps", find them in the list, clear storage/cache and reboot. After that try searching for a restricted app such as Netflix on the Play store, if it shows up in results you're all good.
Remember to also add to deny list other apps that try to detect if you're using root, like banking apps.
Other SafetyNet related fixes:
People using non-stock GIS ROMs will probably need module MagiskHide Props Config by Didgeridoohan. This will install a props command line util that you can use (as root) to force Basic attestation, apply extra Magisk hiding techniques, spoof device fingerprint, change the way fingerprinting is checked, or even impersonate another device altogether. Install, reboot, enter adb shell, type su to go root (will need to grant root to shell on the phone when prompted), then run props and follow the options.
People running extra-stubborn banking apps (or other apps that try to detect root extra-hard) that don't work even when added to the Magisk deny list can try module Shamiko by LSPosed. This module adds extra hiding techniques for the apps on the deny list. Please note that Shamiko will disable the Magisk "enforce deny list" option but that's ok, that's an extra feature, the deny list is in effect even without it.
Working apps and modulesPlease note that this list is limited to stuff that I personally use. I can't and won't install other stuff to test it.
Root apps:
AFWall(+): Works, but configure it to use its own internal busybox and iptables. Applying rules fails occasionally and you need to retry.
Call Recorder by skvalex: Recording works out of the box, no fiddling required with either headset of mic recording.
JuiceSSH, Termux etc. and other terminal apps: No issues getting root with su.
Busybox: you can install zgfg's module which exposes Magisk's internal Busybox to the rest of the system (bonus: will be updated with Magisk); or you can install osm0sys's module which contains a standalone separate Busybox. As of now both of them provide Busybox 1.34.
MyBackup Pro: Works fine. Used it to transfer 15k+ SMS messages from Android 8.
Solid Explorer: Can access root partitions without issues.
Tasker: No issues.
Titanium Backup: Works but will hang when restoring APKs whose target API doesn't support the ROM's Android version (ie. APKs you can't install directly either).
OAndBackupX: Modern alternative to Titanium, works perfectly.
XPERI+: Version 6 works well and allows you to remap the assistant button and has another couple of features. Version 7 crashes.
Magisk modules:
AFWall Boot AntiLeak
Backup
Builtin BusyBox
Magisk Bootloop Protector
MagiskHide Props Config
Shamiko
SQLite for ARM aarch64 devices
Systemless Hosts (comes with Magisk, enable it in settings)
Universal SafetyNet Fix
Zygisk LSPosed
LSPosed modules:
App Settings Reborn: Works well. May require a couple of reboots before the targeted apps start showing the modifications.
Disable Flag Secure: com.varuns2002 is working, sort of. Please read the module's page. Apps got wise to rooted devices ignoring FLAG_SECURE so now they use hardware DRM or detect screenshots and show you something else (Netflix). So it works only in older versions of apps, or apps that haven't bothered to detect screenshots.
GravityBox [R]: Everything I tried works perfectly.
Physical Button Master Control: The module works as intended, the companion config app has some issues, hopefully they'll be solved soon.
XPrivacyLua: Works perfectly. No issues with SafetyNet.
Not working:
...
Other tested and working Root Apps:
AdAway
Fox's Magisk Module Manager
Franco Kernel Manager
Termux
Not testet yet:
Call Recorder
FolderSync
Total Commander
Vanced Manager
WireGuard
Other tested and working Magisk modules:
1Controller - 1 Module to support all Controllers
Call Recorder - SKVALEX
F-Droid Privileged Extension
Move Certificates (version by Androidacy)
Other tested and working LSPosed modules:
BubbleUPnP AudioCast
//Note for those who wants to know actual information. Thanks to V0latyle for pointing it out.
V0latyle said:
SafetyNet components like CTSProfile are no longer applicable, as SafetyNet has been replaced by Play Integrity. All of Google's apps such as GPay have long since switched.
More information here.
Click to expand...
Click to collapse
Recently i faced the problem where my CTS profile failed and thus Google Wallet (GPay) wasn't able to work properly.
I managed to fix this, and so decided to share my expirience to help thus in need to fix this issue aswell.
Previously i had this setup for around whole year which did work until now:
Device: oneplus 9 pro
Firmware: oos 11 11.2.10.10
Kernel: from Arter97
Magisk: Magisk Alpha 23.0 + magisk hide + module universal safetynet fix 1.1.1
Problem: Google Wallet (GPay) won't work / CTS profile failed
Now, these are steps which did help me to solve the issue:
1. Rolled back to stock kernel (boot, dtbo, vendor_boot partitions)
2. Set up Magisk Alpha 25205
Spoiler: How did you install Magisk Alpha 25205?
(there are different methods, like manual patch of stock kernel and then flasshing it via fastboot, or flashing it via TWRP (Keep in mind, that in this case you have to preinstall TWRP before installing custom kernel)
3. Activate Zygisk
4. Select in DenyList menu: Google Play Services, Google Play Store, Google Wallet (GPay) and other apps which you'd like to not find out about your modified system
5. DO NOT ENABLE Enforce DenyList option
6. Install Magisk modules: Shamiko 0.5.2 | Universal SafetyNet Fix 2.3.1 for Zygisk | MagiskHide Props Config 6.1.2
7. Using any terminal app, select newer Fingerpring thanks to MagiskHide Props Config module
Spoiler: How do i do that?
1. open any terminal app
2. type "su" (without quotes)
3. type "props"
4. now you can edit your device fingerprint)
8. Clear data of the following apps: Google Play Store, Google Services, Google Wallet (GPay)
9. Reboot
10. Now, when you open up your Google Wallet (GPay) app, it may work OR message that says that it's updating and you can't use it while the process isn't done may appear.
11. If you encounter such message, change your device language to other one and then open up Google Wallet (GPay) app again
12. Now the app should open up, it may take some time to update it's interface to the latest one
Google Wallet (GPay) now works fine and CTS profile passes succesefully.
Have a nice day
more_than_hater said:
Recently i faced the problem where my CTS profile failed and thus Google Wallet (GPay) wasn't able to work properly.
I managed to fix this, and so decided to share my expirience to help thus in need to fix this issue aswell.
Previously i had this setup for around whole year which did work until now:
Device: oneplus 9 pro
Firmware: oos 11 11.2.10.10
Kernel: from Arter97
Magisk: Magisk Alpha 23.0 + magisk hide + module universal safetynet fix 1.1.1
Problem: Google Wallet (GPay) won't work / CTS profile failed
Now, these are steps which did help me to solve the issue:
1. Rolled back to stock kernel (boot, dtbo, vendor_boot partitions)
2. Set up Magisk Alpha 25205
Spoiler: How did you install Magisk Alpha 25205?
(there are different methods, like manual patch of stock kernel and then flasshing it via fastboot, or flashing it via TWRP (Keep in mind, that in this case you have to preinstall TWRP before installing custom kernel)
3. Activate Zygisk
4. Select in DenyList menu: Google Play Services, Google Play Store, Google Wallet (GPay) and other apps which you'd like to not find out about your modified system
5. DO NOT ENABLE Enforce DenyList option
6. Install Magisk modules: Shamiko 0.5.2 | Universal SafetyNet Fix 2.3.1 for Zygisk | MagiskHide Props Config 6.1.2
7. Using any terminal app, select newer Fingerpring thanks to MagiskHide Props Config module
Spoiler: How do i do that?
1. open any terminal app
2. type "su" (without quotes)
3. type "props"
4. now you can edit your device fingerprint)
8. Clear data of the following apps: Google Play Store, Google Services, Google Wallet (GPay)
9. Reboot
10. Now, when you open up your Google Wallet (GPay) app, it may work OR message that says that it's updating and you can't use it while the process isn't done may appear.
11. If you encounter such message, change your device language to other one and then open up Google Wallet (GPay) app again
12. Now the app should open up, it may take some time to update it's interface to the latest one
Google Wallet (GPay) now works fine and CTS profile passes succesefully.
Have a nice day
Click to expand...
Click to collapse
Hello, thanks for posting but I have a question here. In step 7, in "props" I have to choose an option from Google smartphones and according to the Android I am on. Well, the module is outdated and no option appears with Android 13, which is my case. What do I do now?
Ursaotns said:
Hello, thanks for posting but I have a question here. In step 7, in "props" I have to choose an option from Google smartphones and according to the Android I am on. Well, the module is outdated and no option appears with Android 13, which is my case. What do I do now?
Click to expand...
Click to collapse
It seems that there exists an unofficial fork of this magisk module
And, as i understand, it's not that important to choose exactly the same android ver as yours, you can go up and down.
more_than_hater said:
It seems that there exists an unofficial fork of this magisk module
And, as i understands, it's not that important to choose exactly the same android ver as yours, you can go up and down.
Click to expand...
Click to collapse
Thanks. It helped a lot! I was able to resolve the issue here on my OnePlus Ace (10R) on Android 13 and OxygenOS 13. Only thing left for me to solve here is to remove youtube from the system as Wakelocks. Do you have any idea how to remove it permanently? Would you help me?
Ursaotns said:
Thanks. It helped a lot! I was able to resolve the issue here on my OnePlus Ace (10R) on Android 13 and OxygenOS 13. Only thing left for me to solve here is to remove youtube from the system as Wakelocks. Do you have any idea how to remove it permanently? Would you help me?
Click to expand...
Click to collapse
How to Stop Wakelocks from Any Android App Without Root
Have you ever wondered why your Android phone eats your battery life so fast when the screen is off? Wakelocks! Here's a tutorial on how to stop wakelocks!
www.xda-developers.com
SafetyNet components like CTSProfile are no longer applicable, as SafetyNet has been replaced by Play Integrity. All of Google's apps such as GPay have long since switched.
More information here.
I recently faced similar issue, but with newest version of Company portal (Intune) app as I have a work profile.
After updating the app it started detecting I am rooted maybe due to the mentioned change.
I already had configured the zygisk, deny list and safety net fix.
I found 2 ways to fix it.
1 As a workaround to download grade the app with previous version.
2. I just installed latest shamiko and disable enforcement of the deny list. I didn't used the MagiskHide Props Config. Basically all the steps mentioned above, but without MagiskHide Props Config. For now all is fine. I didn't had issues with gpay so far.
I am on Oneplus 9Pro OOS 13 F.72