[GUIDE][J7ELTE]MicroG and Xposed for LineageOS 17.1 - Samsung Galaxy J7 Guides, News, & Discussion

Disclaimer
Your warranty is now void.
I am not responsible for any bricked devices.
After some trial and error. I finally got microg running on LOS 17.1 or Android 10/Q. Tested on J700H (should work on J700F, etc. except for T which I assume has different properties)
The installation is quite tricky for some bug reasons (Traditionally Installing Microg will result into, no app notifications.)
So for the people who want to install Microg in their LOS ROM make sure to follow this guide.
For people who doesn't know about MicroG
https://www.reddit.com/r/MicroG/comments/9jceaj
Before we start, there is also this https://lineage.microg.org/. Which gives you preloaded MicroG ROM but the problem is, the ROM itself isn't that updated (Last updated 2-2-2021)
But the good thing is, you only have to flash it with TWRP and voila. You got MicroG and LOS, just a little bit older.
For people who wants to have the latest nightly Lineage OS 17.1 and at the same time having microg follow these steps carefully.
Requirements:
Lineage OS 17.1 https://download.lineage.microg.org/j7elte/ (Download the latest Nightly Zip only, forget the recovery zip)
Working TWRP (if you dont have any https://forum.xda-developers.com/t/...y-amp-amp-amp-root-samsung-galaxy-j7.3203632/) Please be careful
Apply this guide, but change the TWRP file to the latest one here https://dl.twrp.me/j7elte/
Magisk https://github.com/topjohnwu/Magisk/releases/download/v21.2/Magisk-v21.2.zip
MicroG GMS Core https://github.com/microg/GmsCore/r...7.204714/com.google.android.gms-204714034.apk
^^^^^
It's important to download this version else your notifications wont work
File downloaded must be "com.google.android.gms-204714034.apk" DOUBLE CHECK!
For some reason, the latest MicroG automatically closes it's device registration upon exiting the app, thereby disabling Cloud Messaging as a result. Which means notifications wont even show up.
MicroG GSF Proxy https://microg.org/fdroid/repo/com.google.android.gsf-8.apk
OpenGapps [arm, android 10, pico zip] https://opengapps.org/ (But I thought it was microg? Yup this is only temporary but part of the procedure)
Lucky Patcher or anything that can uninstall system apps (I recommend lucky patcher since it doesn't require any play services to run. If you try to uninstall google play services with an app that relies on play services it will crash)
Latest Bootloader, make sure to flash the latest bootloader using odin before proceeding to install LOS otherwise it wont work.
Check sammobile for the latest firmware
NEVER SKIP REBOOT. Else you're just making things complicated.
Go to settings > Tap Build Number 7 times > Developer Options > enable OEM unlock
Reboot to TWRP recovery and Full Wipe (Data, Cache, Dalvik, System)
Install Lineage OS 17.1 (Dont boot to system yet)
Install Magisk Zip
Install Gapps Pico Zip
Boot to System
Run Magisk, just press okay when it tries to update the app on startup. Check if Magisk is Installed: 21.1 (No need to Update App or Magisk if those numbers are shown, if it's N/A then update it)
If magisk asks you to reboot then do it (Especially if you updated it)
On the magisk app, click the puzzle icon on the bottom right. This is the magisk module, now search for Riru, download & Install (after installation dont reboot yet)
Next look for the Riru - EdXposed module (Then reboot)
I'm not sure of this one but check if EdExposed app is present on your homescreen then proceed, if not then search for EdExposed Manager apk, download & install.
If you're doing things right, upon opening EdExposed Manager, framework should be active. If not then retrace your steps
On EdExposed Manager, swipe right, then click download, search for FakeGApps and install. (You need to activate the module then reboot)
Install Lucky Patcher and grant root. Uninstall Google Play Services and Google Services Framework using lucky patcher (Things will start force closing which means it's working, reboot your device)
Install MicroG GMS Core (Make sure you download the file I listed above or else notifications wont work)
Install MicroG GSF
Open MicroG Settings on Homescreen, do a self-check. See if everything is checked, tap to grant it permission. (If system spoofs signature is unchecked, retrace your steps from no. 13)
Restart your phone (do not skip this step)
Open MicroG Settings, turn on Google Device Registration & Cloud Messaging
Restart your phone again (do not skip this step!! notification wont still work at this point)
Install Push Notification Tester on playstore to test
Have a cup of coffee and congratulate yourself. You now have MicroG on Lineage OS 17.1
Long term note: For example if an app notification doesnt work. Check MicroG settings > Cloud Messaging.
If the app doesn't appear there (also if the app exists way before you installed MicroG) you may have to reinstall that app to be able to get notifications
Purpose of this guide: Installing these kind of things are now difficult since Android 10. So many bugs and stuffs not working that's why I created this guide to at least contribute a little.
I'm thankful for the people who Lineage OS, made my phone so smooth.
Credits:
MicroG - https://microg.org/
LineageOS - https://lineageos.org/
Magisk - https://github.com/topjohnwu/
TWRP - https://twrp.me/
Video proof that MicroG works. GCM Notification Test via Discord https://streamable.com/d9f1qy

Related

[Fix] [7.0] Samsung Account Login Password Loop (Magisk 13.1)

Before everything, this trips the Knox Counter. Also, I am not responsible for any device damage, so, do it at your own risk.
You must have a official non modified rom. The only modification allowed is Root with Magisk.
After routing my Galaxy Tab S2 (SM-T810) using Magisk 13.1, I became unable to login in my Samung Account. So, after hours of searching I found pieces of information and put it together on the same thread.
Things you need:
1) Magisk with SafetyNet passed
2) Magisk Hide, Core and systemless hosts enabled
3)Titanium Backup
What to do:
1) Open Titanium Backup and go to Backup/Restore and Search for Samsung Account
2) Press Wipe data to wipe the data from the app
3) Reboot
4) Go to Settings -> Cloud and accounts ->Accounts -> Samsung account -> Profile
5) Login into your account
Now you can use Samsung apps on a Rooted ROM
If your Magisk Does not have SafetyNet passed:
1) Download TWRP Recovery and install it on your device
2) Download Magisk zip installer from the official thread
3) Download VerifiedBootSigner
4) Install on the recovery first the Magisk and then VerifiedBootSigner
5) Then, open Magisk and enable Magisk Hide, Core and systemless hosts
6) Reboot
If you found any error please pm
Sources:
How to pass SafetyCheck - https://android.gadgethacks.com/how...-work-your-rooted-device-with-magisk-0177578/
VerifiedBootSigner - https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Magisk - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Samsung account login loop on Note 5
ZenJB said:
Before everything, this trips the Knox Counter. Also, I am not responsible for any device damage, so, do it at your own risk.
You must have a official non modified rom. The only modification allowed is Root with Magisk.
After routing my Galaxy Tab S2 (SM-T810) using Magisk 13.1, I became unable to login in my Samung Account. So, after hours of searching I found pieces of information and put it together on the same thread.
Things you need:
1) Magisk with SafetyNet passed
2) Magisk Hide, Core and systemless hosts enabled
3)Titanium Backup
What to do:
1) Open Titanium Backup and go to Backup/Restore and Search for Samsung Account
2) Press Wipe data to wipe the data from the app
3) Reboot
4) Go to Settings -> Cloud and accounts ->Accounts -> Samsung account -> Profile
5) Login into your account
Now you can use Samsung apps on a Rooted ROM
If your Magisk Does not have SafetyNet passed:
1) Download TWRP Recovery and install it on your device
2) Download Magisk zip installer from the official thread
3) Download VerifiedBootSigner
4) Install on the recovery first the Magisk and then VerifiedBootSigner
5) Then, open Magisk and enable Magisk Hide, Core and systemless hosts
6) Reboot
If you found any error please pm
Sources:
How to pass SafetyCheck - https://android.gadgethacks.com/how...-work-your-rooted-device-with-magisk-0177578/
VerifiedBootSigner - https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Magisk - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Thanks a million for this post! Everything works like a charm.:good:

[GUIDE] [SD652/MTK] Magisk - How to pass Safetynet check

Hello everyone,
As you might have seen, Google Safetynet APIs have been updated. Since Official Magisk is using old API, when you try to pass Safetynet, it will automatically give you an error like " The response is invalid" or something like that.
So, in order to bypass this issue, I've been searching for a long time and I found a solution.
THIS WON'T WORK WITH XPOSED FRAMEWORK INSTALLED!!
1- Uninstall completely Magisk using official uninstaller.
2- Once the device rebooted, download and install latest unofficial Magisk Manager APK available on this page: https://github.com/ianmacd/MagiskBuilds?files=1
3- Open Magisk Manager and go to Magisk settings
4- Click on Update Channel and choose Custom
5- Insert this URL and click OK : https://raw.githubusercontent.com/ianmacd/MagiskBuilds/master/updates/ianmacd.json
6- Click on Clear Repo Cache
7- Return to Magisk Startpage and check for update
8- Install Unofficial Magisk 16.8
9- Once installation done, reboot your device
10- Go to Magisk Manager and check for Safetynet
If it passed, Congratulations, you're done.
If not, continue.
11- Download this Magisk Module : https://androidfilehost.com/?fid=5862345805528046758
12- Once downloaded, disconnect your phone from Internet (turn of the Wi-Fi, 4g, etc...). It's very important
13- Install the module using Magisk Manager and reboot
14- When reboot done, wait 5 minutes before turning on Internet connection
15- Go to Magisk Manager and check if Safetynet passed.
It should be working, it worked in my case.
Have tried on two devices:
- Leeco x626 with EUI ROM ( Cuoco) using the module
- Leeco x526 with MIUI 10 without the module
FOR EUI ROMs:
You could get an error saying you're using a modified software or something like this, after uninstalling old Magisk.
Do this :
- Download official Magisk uninstaller AND Unofficial Magisk 16.8 ZIP
- Reboot to TWRP Recovery
- Uninstall old Magisk using the uninstaller
DO NOT REBOOT
- Return to TWRP Home menu and install unofficial Magisk 16.8
- Reboot your device and it should be okay
Wow it worked. Thanks a lot bro.
xwml12 said:
Hello everyone,
As you might have seen, Google Safetynet APIs have been updated. Since Official Magisk is using old API, when you try to pass Safetynet, it will automatically give you an error like " The response is invalid" or something like that.
So, in order to bypass this issue, I've been searching for a long time and I found a solution.
1- Uninstall completely Magisk using official uninstaller.
2- Once the device rebooted, download and install latest unofficial Magisk Manager APK available on this page: https://github.com/ianmacd/MagiskBuilds?files=1
3- Open Magisk Manager and go to Magisk settings
4- Click on Update Channel and choose Custom
5- Insert this URL and click OK : https://raw.githubusercontent.com/ianmacd/MagiskBuilds/master/updates/ianmacd.json
6- Click on Clear Repo Cache
7- Return to Magisk Startpage and check for update
8- Install Unofficial Magisk 16.8
9- Once installation done, reboot your device
10- Go to Magisk Manager and check for Safetynet
If it passed, Congratulations, you're done.
If not, continue.
11- Download this Magisk Module : https://androidfilehost.com/?fid=5862345805528046758
12- Once downloaded, disconnect your phone from Internet (turn of the Wi-Fi, 4g, etc...). It's very important
13- Install the module using Magisk Manager and reboot
14- When reboot done, wait 5 minutes before turning on Internet connection
15- Go to Magisk Manager and check if Safetynet passed.
It should be working, it worked in my case.
Have tried on two devices:
- Leeco x626 with EUI ROM ( Cuoco) using the module
- Leeco x526 with MIUI 10 without the module
FOR EUI ROMs:
You could get an error saying you're using a modified software or something like this, after uninstalling old Magisk.
Do this :
- Download official Magisk uninstaller AND Unofficial Magisk 16.8 ZIP
- Reboot to TWRP Recovery
- Uninstall old Magisk using the uninstaller
DO NOT REBOOT
- Return to TWRP Home menu and install unofficial Magisk 16.8
- Reboot your device and it should be okay
Click to expand...
Click to collapse
Didn't work for me. I've tried everything as stated in the instructions. I'm using an x626 and running on EUI 30s room. See what it shows from d pics below
rexmako said:
Didn't work for me. I've tried everything as stated in the instructions. I'm using an x626 and running on EUI 30s room. See what it shows from d pics below
Click to expand...
Click to collapse
Check if you don't have Xposed Framework installed, if yes uninstall it as it won't let the phone pass Safetynet check.
xwml12 said:
Check if you don't have Xposed Framework installed, if yes uninstall it as it won't let the phone pass Safetynet check.
Click to expand...
Click to collapse
I don't think I have Xposed framework, unless it's hidden somewhere in my phone. How do I check for it? I know I have some root apps installed. Apps like es explorer, root explorer and browser, BusyBox, etal
rexmako said:
I don't think I have Xposed framework, unless it's hidden somewhere in my phone. How do I check for it? I know I have some root apps installed. Apps like es explorer, root explorer and browser, BusyBox, etal
Click to expand...
Click to collapse
BusyBox... That's the problem, try without it Installed
xwml12 said:
BusyBox... That's the problem, try without it Installed
Click to expand...
Click to collapse
I just did. I've uninstalled BusyBox and still the same thing. Problem still persist. Or should I just uninstall all my root apps, including root explorer, battery fix and the rest?
After updating magisk I managed to passed safetynet check, but it still wont allow me to launch Fate/Grand Order
Dragladiator said:
After updating magisk I managed to passed safetynet check, but it still wont allow me to launch Fate/Grand Order
Click to expand...
Click to collapse
Use Magisk Hide and click on your desired apps to hide them root access.
xwml12 said:
Use Magisk Hide and click on your desired apps to hide them root access.
Click to expand...
Click to collapse
The Game is still detected Magisk even with after repacking magisk and acitve magisk hide
Dragladiator said:
The Game is still detected Magisk even with after repacking magisk and acitve magisk hide
Click to expand...
Click to collapse
In Magisk options , disable systemless hosts option and reboot .
xwml12 said:
Hello everyone,
As you might have seen, Google Safetynet APIs have been updated. Since Official Magisk is using old API, when you try to pass Safetynet, it will automatically give you an error like " The response is invalid" or something like that.
So, in order to bypass this issue, I've been searching for a long time and I found a solution.
THIS WON'T WORK WITH XPOSED FRAMEWORK INSTALLED!!
1- Uninstall completely Magisk using official uninstaller.
2- Once the device rebooted, download and install latest unofficial Magisk Manager APK available on this page: https://github.com/ianmacd/MagiskBuilds?files=1
3- Open Magisk Manager and go to Magisk settings
4- Click on Update Channel and choose Custom
5- Insert this URL and click OK : https://raw.githubusercontent.com/ianmacd/MagiskBuilds/master/updates/ianmacd.json
6- Click on Clear Repo Cache
7- Return to Magisk Startpage and check for update
8- Install Unofficial Magisk 16.8
9- Once installation done, reboot your device
10- Go to Magisk Manager and check for Safetynet
If it passed, Congratulations, you're done.
If not, continue.
11- Download this Magisk Module : https://androidfilehost.com/?fid=5862345805528046758
12- Once downloaded, disconnect your phone from Internet (turn of the Wi-Fi, 4g, etc...). It's very important
13- Install the module using Magisk Manager and reboot
14- When reboot done, wait 5 minutes before turning on Internet connection
15- Go to Magisk Manager and check if Safetynet passed.
It should be working, it worked in my case.
Have tried on two devices:
- Leeco x626 with EUI ROM ( Cuoco) using the module
- Leeco x526 with MIUI 10 without the module
FOR EUI ROMs:
You could get an error saying you're using a modified software or something like this, after uninstalling old Magisk.
Do this :
- Download official Magisk uninstaller AND Unofficial Magisk 16.8 ZIP
- Reboot to TWRP Recovery
- Uninstall old Magisk using the uninstaller
DO NOT REBOOT
- Return to TWRP Home menu and install unofficial Magisk 16.8
- Reboot your device and it should be okay
Click to expand...
Click to collapse
What if custom ROMs? How do we make them pass the check using any of the above methods?
rexmako said:
What if custom ROMs? How do we make them pass the check using any of the above methods?
Click to expand...
Click to collapse
Working on all ROMS, Custom or Stock. Just follow the guide
error installing new APK:
App not installed. The package conflcts with an existing package by the same name.
x522 Le 2, LineageOS 14.1 official nightly.
help?
EDIT: Nevermind, uninstalled with TWRP and uninstall zip, noy uninstall button in manager. oops!
EDIT2: still fails cts on unofficial 17.2 with unofficial manager 09-20. on leeco x522. help?

MI 9T Nethunter installation

Hello! Has anyone installed official Nethunter 2020-pre3 on this device? If so, could you please describe step-by-step how you managed to do that, what MIUI (or maybe custom ROM) you have, and how it works?
you can install, but you need kernel to get wifi to work. if someone implement nethunter wlan mon to kernel, then you could test vulnerabilities
there is also Andrax, but also requires kernel for monitoring
fotom-dotcom said:
Hello! Has anyone installed official Nethunter 2020-pre3 on this device? If so, could you please describe step-by-step how you managed to do that, what MIUI (or maybe custom ROM) you have, and how it works?
Click to expand...
Click to collapse
my phone is currently running the latest version of miui 11 and when I flash the kali nethunter kernel to my mi 9t, it gets stuck on boot, any solutions or step by step guide on how I can successfully install it?
Flash MIUI fastboot Rom (11.0.5) and boot to the system
Remove your Google and Mi account if you have one
Then install TWRP
Install Disable_DM-Veriety_Forcencrypt(find it on xda)
Reboot recovery
Install magisk and perform format data
Boot to the system and set up the phone
Then install magisk again
Install busybox app from playstore and install busybox itself to /system/xbin
Go to TWRP
Install latest NH image
Go to Mount and untick /System
Install Magisk (for the last time)
Wipe cache and dalvik, then reboot. You should see NH boot animation.
Go to NH app, grant all permissions and start chroot
Go to NH Store, in settings tap on expert mode and untick PrivilegeExtention
Update NH app to the latest version
And you're done! This step-by-step guide should help to install NH and make it work properly. Then just type "apt update && apt -y full-upgrade" in NH terminal and you're good to go
fotom-dotcom said:
Flash MIUI fastboot Rom (11.0.5) and boot to the system
Remove your Google and Mi account if you have one
Then install TWRP
Install Disable_DM-Veriety_Forcencrypt(find it on xda)
Reboot recovery
Install magisk and perform format data
Boot to the system and set up the phone
Then install magisk again
Install busybox app from playstore and install busybox itself to /system/xbin
Go to TWRP
Install latest NH image
Go to Mount and untick /System
Install Magisk (for the last time)
Wipe cache and dalvik, then reboot. You should see NH boot animation.
Go to NH app, grant all permissions and start chroot
Go to NH Store, in settings tap on expert mode and untick PrivilegeExtention
Update NH app to the latest version
And you're done! This step-by-step guide should help to install NH and make it work properly. Then just type "apt update && apt -y full-upgrade" in NH terminal and you're good to go
Click to expand...
Click to collapse
-I just installed Kali NetHunter last week to QFJEUXM v11.0.6 and Disable_DM-Veriety_Forcencrypt is NOT NEEDED (it is only needed for custom ROMs, no need for TWRP, Magisk or NetHunter overlay).
Ofc, every type when bootibg to TWRP (use official 3.4.0), type in your Android screen unlock pin to let TWRP on-the-fly decrypt Data (just like when booting to Android), but keeping your file system encrypted
With DFE you force complete decrypion of your Data - anybody who would boot into TWRP would be able to read/write to your Data without need to know your Androud screen unlock pin
(I don't know why people copy/paste this DFE into every guide: for TWRP, for rooting, etc - it is only needed for installation of custom ROMs because they are usually not properly ported to the device and they don't support stock file encryption, hence encryption must be removed by DFE for custom ROMs to be able to access Data)
- Also, I didn't remove my Google and Mi account, and I didn't format Data - no need for TWRP, not for Magisk, neither for NH.
Upon installing NH, I had all my apps, data, settings as before
- Btw, "apt update && apt -y full-upgrade" is covered by NetHunter app (comed with the installation) go to Custum commands tab, first option there
PS: Custom kernel is included to the pre-built NH image, as well as stock GApps
zgfg said:
-I just installed Kali NetHunter last week to QFJEUXM v11.0.6 and Disable_DM-Veriety_Forcencrypt is NOT NEEDED (it is only needed for custom ROMs, no need for TWRP, Magisk or NetHunter overlay).
Ofc, every type when bootibg to TWRP (use official 3.4.0), type in your Android screen unlock pin to let TWRP on-the-fly decrypt Data (just like when booting to Android), but keeping your file system encrypted
With DFE you force complete decrypion of your Data - anybody who would boot into TWRP would be able to read/write to your Data without need to know your Androud screen unlock pin
(I don't know why people copy/paste this DFE into every guide: for TWRP, for rooting, etc - it is only needed for installation of custom ROMs because they are usually not properly ported to the device and they don't support stock file encryption, hence encryption must be removed by DFE for custom ROMs to be able to access Data)
- Also, I didn't remove my Google and Mi account, and I didn't format Data - no need for TWRP, not for Magisk, neither for NH.
Upon installing NH, I had all my apps, data, settings as before
- Btw, "apt update && apt -y full-upgrade" is covered by NetHunter app (comed with the installation) go to Custum commands tab, first option there
PS: Custom kernel is included to the pre-built NH image, as well as stock GApps
Click to expand...
Click to collapse
Can u help me? https://drive.google.com/file/d/10KY4uZoZknjvQr8qDP7UHLDPInjIQVYg/view?usp=drivesdk
Can you help us with your step by step ? Thank you !
Can you help us with your steps ?
zgfg said:
-I just installed Kali NetHunter last week to QFJEUXM v11.0.6 and Disable_DM-Veriety_Forcencrypt is NOT NEEDED (it is only needed for custom ROMs, no need for TWRP, Magisk or NetHunter overlay).
Ofc, every type when bootibg to TWRP (use official 3.4.0), type in your Android screen unlock pin to let TWRP on-the-fly decrypt Data (just like when booting to Android), but keeping your file system encrypted
With DFE you force complete decrypion of your Data - anybody who would boot into TWRP would be able to read/write to your Data without need to know your Androud screen unlock pin
(I don't know why people copy/paste this DFE into every guide: for TWRP, for rooting, etc - it is only needed for installation of custom ROMs because they are usually not properly ported to the device and they don't support stock file encryption, hence encryption must be removed by DFE for custom ROMs to be able to access Data)
- Also, I didn't remove my Google and Mi account, and I didn't format Data - no need for TWRP, not for Magisk, neither for NH.
Upon installing NH, I had all my apps, data, settings as before
- Btw, "apt update && apt -y full-upgrade" is covered by NetHunter app (comed with the installation) go to Custum commands tab, first option there
PS: Custom kernel is included to the pre-built NH image, as well as stock GApps
Click to expand...
Click to collapse
mapachesan said:
Can you help us with your steps ?
Click to expand...
Click to collapse
Let me try to recall. Maybe I did some unnecessary steps and if I will go again I would try to do it in a more elegant way:
I had
- QFJEUXM v11.0.6
- Hasty kernel
- Magisk Canary, BusyBox for Android NDK (Systemless module, not app from Playstore) and several other Magisk modules
- TWRP 3.4.0
I never used any custom ROM, I never messed up with Persist, formatting Data, FDE and so - and it was not needed here either!!!
I did some backups but TG didn't need to use them, everything was preserved.
So I didn't remove Google or Mi account, didn't even remove lock-screen Pin (probably would be safer, just in case)
Maybe it was not needed but I flashed stock boot.img (to get rid of changes done by Hasty and Magisk).
I rebooted to Android and ofc lost TWRP - I had to flash it from fastboot again.
So I should have rebooted first to TWRP and only then to Android - that way TWRP would be preserved
Then I rebooted to TWRP and flashed nethunter-2020.2-davinci-miui-ten-kalifs-full.zip
Again I did a mistake (I was discussing something with my wife?) that I rebooted to Android and lost TWRP - I should have rebooted first to TWRP to preserve it
So I flashed TWRP again, booted to TWRP, made a backup of Boot image.
Booted to Android, opened Magisk Manager, patched the backed-up boot.emmc.win (Preserve DM and Preserve Encryption both On, Recovery mode Off).
Rebooted to TWRP, wiped Dalwik and Cache, and flashed the patched Boot img.
Rebooted to Android and I had Magisk with all my previous modules (incl. e.g. Viper4Android, BusyBox, etc).
Probably just flashing Magisk zip through TWRP would also work (but I usually prefer patching method)
Everything (apps, data, settings incl. unlock PIN, etc) was preserved.
It means also stock GApps, my Google account, Google apps (you name it) - all continued to work as in the stock firmware
Opened NetHunter app and Kali Chroot manager - granted root and other permissions.
Also, open Custom commands and Update Kali Metapackages (do it every few days to stay up-to-date)
Open also (I forgot, did it few days later), NetHunter Store, Settings, Expert mode and untick Privilege Extention.
Let it update NetHunter app
That's it, to my best memory
Edit:
One more tip, not related to NH but generally to SafetyNet and unlocked Bootloader
Install Magisk Hide Props Config (Magisk module) and reboot.
Run props from Terminal, choose Edit custom props (not Fingerprint option) redefine ro.product.model to e.g. Unknown and reboot - now, SafetyNet will pass!
Ofc, you should have Magisk Hide option in Magisk Manager ticked on (must be rebooted upon)
If Playstore shows Device is not certified, it can be easily fixed:
- AirPlane mode on
- Settings, Apps, Show System apps
- Search for Google and for Playstore app, Services and Framework do Delete Cache and Data
Reboot, AirPlane off, give a time for Playstore to sync and it will show Device is certified
PS:
For Ctrl c command (you will need e.g. for Wifite nethunting), install Hacker's Keyboard from Playstore
Whenever you need terminal, you can use NetHunter terminal (Android option) - it's better than Terminal app from Playstore.
How hunting can look like:
https://mega.nz/file/p5VlRA6b#btALUgFkxxJn0aZQdHs-oLVwTdeCKLSFsTfJrO4dbGc
zgfg said:
Let me try to recall. Maybe I did some unnecessary steps and if I will go again I would try to do it in a more elegant way:
I had
- QFJEUXM v11.0.6
- Hasty kernel
- Magisk Canary, BusyBox for Android NDK (Systemless module, not app from Playstore) and several other Magisk modules
- TWRP 3.4.0
I never used any custom ROM, I never messed up with Persist, formatting Data, FDE and so - and it was not needed here either!!!
I did some backups but TG didn't need to use them, everything was preserved.
So I didn't remove Google or Mi account, didn't even remove lock-screen Pin (probably would be safer, just in case)
I did it, but the NH app doesn't work (version 2020.02) you saw the video uploaded on google drive
Maybe it was not needed but I flashed stock boot.img (to get rid of changes done by Hasty and Magisk).
I rebooted to Android and ofc lost TWRP - I had to flash it from fastboot again.
So I should have rebooted first to TWRP and only then to Android - that way TWRP would be preserved
Then I rebooted to TWRP and flashed nethunter-2020.2-davinci-miui-ten-kalifs-full.zip
Again I did a mistake (I was discussing something with my wife) that I rebooted to Android and lost TWRP - I should have rebooted first to TWRP to preserve it
So I flashed TWRP again, booted to TWRP, made a backup of Boot image.
Booted to Android, opened Magisk Manager, patched the backed-up boot.emmc.win (Preserve DM and Preserve Encryption both On, Recovery mode Off).
Rebooted to TWRP, wiped Dalwik and Cache, and flashed the patched Boot img.
Rebooted to Android and I had Magisk with all my previous modules (incl. e.g. Viper4Android, BusyBox, etc).
Probably just flashing Magisk zip through TWRP would also work (but I usually prefer patching method)
Everything (apps, data, settings incl. unlock PIN, etc) was preserved.
It means also stock GApps, my Google account, Google apps (you name it) - all continued to work as in the stock firmware
Opened NetHunter app and Kali Chroot manager - granted root and other permissions.
Also, open Custom commands and Update Kali Metapackages (do it every few days to stay up-to-date)
Open also (I forgot, did it few days later), NetHunter Store, Settings, Expert mode and untick Privilege Extention.
Let it update NetHunter app
That's it, to my best memory
Edit:
One more tip, not related to NH but generally to SafetyNet and unlocked Bootloader
Install Magisk Hide Props Config (Magisk module) and reboot.
Run props from Terminal, choose Edit custom props (not Fingerprint option) redefine ro.product.model to e.g. Unknown and reboot - now, SafetyNet will pass!
Ofc, you should have Magisk Hide option in Magisk Manager ticked on (must be rebooted upon)
If Playstore shows Device is not certified, it can be easily fixed:
- AirPlane mode on
- Settings, Apps, Show System apps
- Search for Google and for Playstore app, Services and Framework do Delete Cache and Data
Reboot, AirPlane off, give a time for Playstore to sync and it will show Device is certified
PS:
For Ctrl c command (you will need e.g. for Wifite nethunting), install Hacker's Keyboard from Playstore
Whenever you need terminal, you can use NetHunter terminal (Android option) - it's better than Terminal app from Playstore.
How hunting can look like:
https://mega.nz/file/p5VlRA6b#btALUgFkxxJn0aZQdHs-oLVwTdeCKLSFsTfJrO4dbGc
Click to expand...
Click to collapse
>Miui beta chinese 20.7.16
I did it, but the NH app doesn't work (version 2020.02) you saw the video uploaded on google drive
https://drive.google.com/file/d/10KY4uZoZknjvQr8qDP7UHLDPInjIQVYg/view?usp=drivesdk
View attachment 5063369
Irineu F said:
>Miui beta chinese 20.7.16
I did it, but the NH app doesn't work (version 2020.02) you saw the video uploaded on google drive
https://drive.google.com/file/d/10KY4uZoZknjvQr8qDP7UHLDPInjIQVYg/view?usp=drivesdk
Click to expand...
Click to collapse
Sorry but recording by camera or what was very bad, cannot read anything.
Please use stock Screen recorder - see a screenshot.
Also, you can take screenscots by sliding three fingers, this is useful for capturing short lasting notifications and so - second screenshot
Isn't your notification saying something about Chroot (cannot read from your movie) - it should look like on my screenshots
Check slso if root is granted and all permissions given - further screenshots
Edit:
Make sure you also have Busybox for Android NDK (Magisk module) installed
Irineu F said:
>Miui beta chinese 20.7.16
I did it, but the NH app doesn't work (version 2020.02) you saw the video uploaded on google drive
https://drive.google.com/file/d/10KY4uZoZknjvQr8qDP7UHLDPInjIQVYg/view?usp=drivesdk
Click to expand...
Click to collapse
Manually grant all the permissions to the NH app and it should work.
zgfg said:
View attachment 5063369
Sorry but recording by camera or what was very bad, cannot read anything.
Please use stock Screen recorder - see a screenshot.
Also, you can take screenscots by sliding three fingers, this is useful for capturing short lasting notifications and so - second screenshot
Isn't your notification saying something about Chroot (cannot read from your movie) - it should look like on my screenshots
Check slso if root is granted and all permissions given - further screenshots
Edit:
Make sure you also have Busybox for Android NDK (Magisk module) installed
Click to expand...
Click to collapse
on the notification screen, NH says Chroot is not installed, I don't know how to give manual permission, because NH is installed as a System App, so it should have all permissions
Adoantony said:
on the notification screen, NH says Chroot is not installed, I don't know how to give manual permission, because NH is installed as a System App, so it should have all permissions
Click to expand...
Click to collapse
Have you tried?
See my screenstots from previous post.
Settings, Apps, Manage apps, Show system apps, open e.g. NetHunter app, App Permissions...
zgfg said:
Have you tried?
See my screenstots from previous post.
Settings, Apps, Manage apps, Show system apps, open e.g. NetHunter app, App Permissions...
Click to expand...
Click to collapse
https://mega.nz/file/zpYRmYaA#Kav_NBBRi6esWuQ4u0Z9EQDPfLfke2CSwUbZ_hM605o
Adoantony said:
https://mega.nz/file/zpYRmYaA#Kav_NBBRi6esWuQ4u0Z9EQDPfLfke2CSwUbZ_hM605o
Click to expand...
Click to collapse
Your app settings look different, what is exactly your model and firmware (ROM)
https://mega.nz/file/JhE2BKxL#VRl4ph_dQ41b2zdREtRwrgK9hSheWPkMz8ZXp2vNeDo
zgfg said:
Your app settings look different, what is exactly your model and firmware (ROM)
https://mega.nz/file/JhE2BKxL#VRl4ph_dQ41b2zdREtRwrgK9hSheWPkMz8ZXp2vNeDo
Click to expand...
Click to collapse
https://drive.google.com/file/d/10Y1PFZ3BJsVfYK0lj2XIC6OzEOCXr6nJ/view?usp=drivesdk
Rom beta chinese
do you think i should try to use at Rom Global?
Adoantony said:
https://drive.google.com/file/d/10Y1PFZ3BJsVfYK0lj2XIC6OzEOCXr6nJ/view?usp=drivesdk
Rom beta chinese
do you think i should try to use at Rom Global?
Click to expand...
Click to collapse
On their page they it's not specified which stock firmware for Mi 9T the pre-built image is for:
https://www.offensive-security.com/kali-linux-nethunter-download/
I'm using with QFJEUXM 11.0.6 - global eu, MiUI 11, don't know for other firmwares like Chinese, MIUI 12
zgfg said:
On their page they it's not specified which stock firmware for Mi 9T the pre-built image is for:
https://www.offensive-security.com/kali-linux-nethunter-download/
I'm using with QFJEUXM 11.0.6 - global eu, MiUI 11, don't know for other firmwares like Chinese, MIUI 12
Click to expand...
Click to collapse
fingerprint doesn't work does it?
Adoantony said:
fingerprint doesn't work does it?
Click to expand...
Click to collapse
Just tested five times, it worked (now) for me (frankly, better than expected)
Generally, I'm disappointed with this FOD, I've tried all tricks suggested on forums but never made it working satisfactory, with no stock firmware (one day almost reliable, next day completely useless) hence I better stopped using it months ago (before installing NH)
zgfg said:
Just tested five times, it worked (now) for me (frankly, better than expected)
Generally, I'm disappointed with this FOD, I've tried all tricks suggested on forums but never made it working satisfactory, with no stock firmware (one day almost reliable, next day completely useless) hence I better stopped using it months ago (before installing NH)
Click to expand...
Click to collapse
thanks for answering me <3
do you have a telegram?

Fix safety net issue after magisk install ?

Hi. I have a safety net issue after following the rooting tutorial on this post. (to be precise, safety net was fine, i got the issue when i tried to install edexposed)
I've got a "cts profile mismatch".
I tried to get rid of it, uninstall magisk, wipe system, but it's still there.
I would like to try to make a factory reset using an ota file, but i can't find my version of the system.
I was on SKYW1907110OS00MP3 and i updated to SKYW1911010OS00MP5. Does someone have a factory ota update.zip for one of this two version ?
There is the MagiskHide Props Config module ( https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 ) for fixing this kind of issue, but there is no build-in fingerprint for the blackshark 2.
I tried to get one within an OTA file, but i can't find it.
I really don't know if i can do a << adb push stock_boot_b.img /dev/block/bootdevice/by-name/boot_b >> to restore the unpatched version of my rom or if that will brick my phone (or maybe do nothing to solve my issue)
If anyone have an idea, it would be great. Thanks.
Flashing the stock boot image of the ROM currently installed in your device will not cause bootloop. Tried and tested.
To pass Safetynet, you don't need to flash MagiskHide Props Config module. It doesn't really make your device pass Safetynet at all.
To pass Safetynet with EdXposed, follow these steps:
1. Make sure you enable Magisk Hide in the Magisk app.
2. Rename your Magisk package (optional - for banking apps).
3. Flash the latest EdXposed module from this repo: https://ci.appveyor.com/project/ElderDrivers/edxposed/history (the EdXposed in the Magisk app is outdated, and it breaks Safetynet), and the latest EdXposed Manager here: https://github.com/ElderDrivers/EdXposedManager
4. Go to EdXposed Manager's settings and enable App List mode and Pass SafetyNet options, then reboot your device.
Now, the trickiest part (sort of):
5. Clear Google Services Framework, Google Play services, and Google Play Store's data, then check for Safetynet. Sometimes, it still fails after your first attempt so just repeat this step until it passes Safetynet.
That's all. All of these worked 100% on my CN-converted-to-Global Black Shark 2 device. Hope it will work on yours, too.
Woot, thanks a lot, i will try that right away.

Safetynet-fix : Oneplus 6t + LineageOS 19.1 + MindTheGaaps + Magisk

Hello,
It took me some time but I finally did it. I upgraded from Stock to LIneageOS latest version (Android 12L).
It took me some time because I think there was a problem during installation. Each time I installed, Google Play could not connect to wifi.
I followed the officila guide from Lineage : https://wiki.lineageos.org/devices/fajita/install
I suggest you do the same.
After the installation - here is the trick - you need to start and run Lineage OS on your phone.
Then reboot the phone to recovery (press Power + Volume Down during boot for 5 seconds)
Do a Reset of the data - This is the second trick and not explained in the official guide.
Go back to the ADB SIDELOAD and install the latest MindTheGapps : https://wiki.lineageos.org/gapps
Restart and run lineageOS and check that everything is fine.
Now go back to recovery mode and you can install Magisk. https://github.com/topjohnwu/Magisk
(Tip: You can rename the APK to ZIP to install it).
Problem : Safety Net is not passing. I tried everything (installing the safetynet-fix and the MagiskHidePropsConf. No Success! :-(
Good luck
OK. I gave up on the original LineageOS for Android 12.
I installed https://forum.xda-developers.com/t/...-6t-gapps-ota-updates-safetynet-twrp.4494053/
like you would install the default Lineage OS.
Then I booted and it was passing the SafetyNet which is normal as it is not rooted.
TWRP becomes the new bootloader. I
After that I booted back in TWRP tADB SIDELOAD to load the latest Magisk.
I booted and was hiding Magisk and activated Zygisk. I also Enforce deny List and Configure it to Google Play and Google Wallet.
After a reboot it still passes SafetyNet.
SUCCESS!
I just noted that because google recognize the phone as a NEXUS. Surelly because the SAFETY NET is spoofed by the ROM. Not sure of the implications of that!

Categories

Resources