This is my installation process [last post is OK]
https://forum.xda-developers.com/galaxy-s5/help/wifi-problem-flashed-lineageos-t3576865
Below are screens from CATLOG [not full tho]
If I try to update binaries in TWRP it stops [nothing in TWRP logs about SU], restarts and stops during Lineage loading screen forever.
So I flash ROM again, and SuperSU from TWRP to fix it.
I was reading that after flashing SuperSU - during first restart it should ask me something like "DO you want to keep root" - it doesn't happen.
SuperSU has no apps listed with root access, but root is OK. TitaniumBackup works, but I'm afraid some of the apps doesn't work properly
Now I'm using
lineage-14.1-20170329-nightly-klte-signed.zip
addonsu-ARM-signed_14.1
SM-G900F
Is there a way to have it done?
I remember like trough a fod that once I was setting permissions in Terminal for some files before updating SU? AM I correct?
Thanks for reding
Hi,
With LineageOS, you must only use one root method otherwise problems will occur. The addonSU zip and SuperSU are not the same thing.
The provided root SU zip from Lineage should be enough to give root permissions for apps. If you want to use SuperSU instead of the SU provided by the Lineage team, you must not flash the addonSU zip.
Saber said:
Hi,
With LineageOS, you must only use one root method otherwise problems will occur. The addonSU zip and SuperSU are not the same thing.
The provided root SU zip from Lineage should be enough to give root permissions for apps. If you want to use SuperSU instead of the SU provided by the Lineage team, you must not flash the addonSU zip.
Click to expand...
Click to collapse
I have tried to flash everything and indeed only addonsu-ARM-signed_14.1 is working from TWRP level. Although SuperSU from APK is working OK [latest SR4].
So root seems to be fine for browsing into root or TB! is not complaining about root, but I can not update SU binary - I have also updated Lineage to today's nightly - same thing.
I've used an S4 with lineage and flashing supersu doesn't work. ONE app in particular will not work because the su part of lineage (and old cyanogenmod) doesn't cooperate; it needs supersu for some reason. I was originally on Cyanogenmod from about a year ago, and tried flashing supersu and had this very problem, which is why I tried lineage, but lineage doesn't work and I cannot flash supersu either. I can install from the play store, but it won't update the binary; flashing in recovery fails (in both older cyanogenmod and lineage os) at the boot image patcher step.
supersu 2.79 said:
Finding boot image
Boot image: /dev/block/mmcblk0p20
Extracting ramdisk
Decompressing ramdisk
Failure, aborting
Click to expand...
Click to collapse
The only reason I'm having to resort to this is because Samsung has a problem with their s7 screens failing and won't do a recall...so I'm having to use an older phone and trying to setup my rooted apps, all of which work with the standard Cyanogenmod root or lineage+su addon, except for one app.
EDIT:
Ah-ha, system mode may be the solution, but I'm still trying to get it to boot without getting stuck! I haven't tinkered with supersu in well over a year, and I didn't even know there were two methods for it now.
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
I was waiting for a root enabler for oreo (41.3.A.2.24), and I could find https://forum.xda-developers.com/xperia-x-performance/how-to/guide-stock-kernel-root-twrp-drm-fix-41-t3711837.
But this link is for version 41.3.A.0.401 and it does not work for everybody including me.
Since androplus still didn't bring out a new version of his kernel I tried the method from the above link.
But I'm using newer versions than in the description, I use TWRP 3.2.0, Magisk manager 5.2.2 and Magisk 15.2.
I can install the new version, twrp, the new boor image and Magisk 15.2.
I can boot and Magisk runs but the Safetynet control failes and Magisk does not enable root.
On the installation of the boot image, twrp and magisk I got some messages (marked in red)
unable to mount storage
failed to mount
Before I tried with magisk manager 5.5.1 and magisk 15.1 but then I got stuck at boot time at the sony logo.
Does anybody have a way to root Oreo (the latest version), enable DRM and enable root?
Ok I started all over again and I noticed I didn't follow the procedure first time.
So I excluded the FOTA kernel but whatever else I check no full wipe is done, I can always see the previous installed apps, it does not matter if I check Cust-reset, master-reset or reset-wipe-reason, the system is not wiped.
So that's my first problem, how to wipe the previous install.
Flashing the rom seems to be OK, same thing for flashing boot_oreo.img and twrp-3.1.1-0-dora.img.
I'm not sure about twrp 3.2.0.0 because this version is off-line now, so I tried with TWRP 3.1.1.0 and 3.2.1.0 but they all gave me the same result.
Problems start when I have to flash drmfix.zip, safety-net cleaner or magisk 15.2. The procedure tells me the flash is ok but have a look at thet attached images, I get errors while flashing. One picture for drmfix, one for safety-net-cleaner and one for magisk 15.2
After flashing all of this I can boot successfully but when I try to get root in ES File Explorer pro, it does not work. When I go into Magisk and try the afety-net check I get ctsProfile false and basicIntegrity False.
So the rom does work but I do not get root.
I tried all of this with the Italian rom 41.3.A.2.24.R1E ? I can start all over again with the UK version 41.3.A.2.24.R2E but I do not know if this makes any sense.
So can anybody tell me what to do to get it all going?
deboopi2 said:
I was waiting for a root enabler for oreo (41.3.A.2.24), and...
Click to expand...
Click to collapse
1 - Do use always Adrian DC latest fully working TWRP build for dora.
2 - You don't need a 3rd party kernel to achieve that, instead, you can easily create your own one, based always on stock kernel!
Thats the SELinux's problem.
Flash this first then flash magisk
https://forum.xda-developers.com/xp...ment/mod-sony-stock-patcher-xperia-x-t3528148
hi ppl
it was rooted before. used twrp and some custom roms. but later it unrooted somehow.
I tried flashing super su, magisk and ioroot. supersu and magisk turn with an error msg
io root made it stuck on bootloader animation so I flashed a backup.
how to root it?
thx in advance
1) flash latest twrp http://www.gregtwallace.com/lgg2-projects/twrp/ - then reboot into twrp
2) made absolutely all wipes incl internal and data (delete all stuff) - then reboot into twrp
3) connect to usb - and simply copy rom, gapps, and root solution what you want to flash
latest stable magisk for twrp - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
latest supersu for twrp - Recovery Flashable.zip http://www.supersu.com/download
3) flash the rom what you wanted and flash gapps
3) flash magisk or supersu
(if android 7.1.2 or higher of course - I recommend magisk, because of working nfc pay features, a lot of great systemless addons etc...)
if you prefer old lollipop rom (for example CloudyG2_3.3 ) - it supersu only.
This is the correct sequence - which will eliminate problems with the firmware. If you deleted and installed the root earlier (as you say)
I tried flashing super su, magisk and ioroot. supersu and magisk turn with an error msg
Click to expand...
Click to collapse
jeezes)) you already killed the rom.... and then restore the all this restores backup, this is a "dirty flash" with a bunch of "remnants". I recommend to do clean flash it in the specified sequence and everything will be ok.
You will spend a couple of 1-2 hours only on installing (and setting) completely all applications. It is not so difficult. But it will save you from a bunch of nonsense questions...
If you actually don't have TWRP recovery installed or old Kit kat Rom - this is absolutely another question and the instructions will not work for you. Also, Kit Kat and Lollipop based ROMs does not support Magisk - because of this error.
zemix said:
1) flash latest twrp http://www.gregtwallace.com/lgg2-projects/twrp/ - then reboot into twrp
2) made absolutely all wipes incl internal and data (delete all stuff) - then reboot into twrp
3) connect to usb - and simply copy rom, gapps, and root solution what you want to flash
latest stable magisk for twrp - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
latest supersu for twrp - Recovery Flashable.zip http://www.supersu.com/download
3) flash the rom what you wanted and flash gapps
3) flash magisk or supersu
(if android 7.1.2 or higher of course - I recommend magisk, because of working nfc pay features, a lot of great systemless addons etc...)
if you prefer old lollipop rom (for example CloudyG2_3.3 ) - it supersu only.
This is the correct sequence - which will eliminate problems with the firmware. If you deleted and installed the root earlier (as you say)
jeezes)) you already killed the rom.... and then restore the all this restores backup, this is a "dirty flash" with a bunch of "remnants". I recommend to do clean flash it in the specified sequence and everything will be ok.
You will spend a couple of 1-2 hours only on installing (and setting) completely all applications. It is not so difficult. But it will save you from a bunch of nonsense questions...
If you actually don't have TWRP recovery installed or old Kit kat Rom - this is absolutely another question and the instructions will not work for you. Also, Kit Kat and Lollipop based ROMs does not support Magisk - because of this error.
Click to expand...
Click to collapse
thx bro. I did all the steps but it seems same problem going on. sure I want the latest of everything. better updated all. so, using the latest twrp, I wipe all data then format all data then again wipe everything
this aosp rom and gapps worked perfectly. then flashed teh magisk but again its unrooted.
it installs magisk perfectly but root checker says its not rooted. anyway thx for help
btw, aosp rom android 9 has a bluetooth bug. giving a bluetooth stopped message every 10 seconds.
so any advice anout that problem?
you must grant root permission when popup (magisk) appears.
its not automatically
popup similar as in supersu
root works excellent on d802 with Magisk
for example Es File Explorer or any Root Checker
---------- Post added at 17:12 ---------- Previous post was at 17:10 ----------
I use 7.1.2 android based AospExtended v 4.6
because latest pie rom has bugs and not stable
Screenshot https://i.imgur.com/6IcIvJx.jpg
slabongrade said:
thx bro. I did all the steps but it seems same problem going on. sure I want the latest of everything. better updated all. so, using the latest twrp, I wipe all data then format all data then again wipe everything
this aosp rom and gapps worked perfectly. then flashed teh magisk but again its unrooted.
it installs magisk perfectly but root checker says its not rooted. anyway thx for help
btw, aosp rom android 9 has a bluetooth bug. giving a bluetooth stopped message every 10 seconds.
Click to expand...
Click to collapse
flash magisk.zip and install magisk.apk to root android 9
zemix said:
you must grant root permission when popup (magisk) appears.
its not automatically
popup similar as in supersu
root works excellent on d802 with Magisk
for example Es File Explorer or any Root Checker
---------- Post added at 17:12 ---------- Previous post was at 17:10 ----------
I use 7.1.2 android based AospExtended v 4.6
because latest pie rom has bugs and not stable
Click to expand...
Click to collapse
zemix said:
Screenshot https://i.imgur.com/6IcIvJx.jpg
Click to expand...
Click to collapse
elffoh said:
flash magisk.zip and install magisk.apk to root android 9
Click to expand...
Click to collapse
zemix said:
you must grant root permission when popup (magisk) appears.
its not automatically
popup similar as in supersu
root works excellent on d802 with Magisk
for example Es File Explorer or any Root Checker
---------- Post added at 17:12 ---------- Previous post was at 17:10 ----------
I use 7.1.2 android based AospExtended v 4.6
because latest pie rom has bugs and not stable
Click to expand...
Click to collapse
zemix said:
Screenshot https://i.imgur.com/6IcIvJx.jpg
Click to expand...
Click to collapse
elffoh said:
flash magisk.zip and install magisk.apk to root android 9
Click to expand...
Click to collapse
I used supersu and it turned out to be "certification verify" problem. OS not running because of this problem but says rooted. so I can still reach twrp but it really become annoying. this is my old phone and will use as 2nd in my Thailand trip soon.
what to do now? can I use unrooted with a sim card? with no problem?
Please, don't use this nonsense "overquoting" when you answer to someone. Have some respect to the forum rules, and users.
if you want stable rom for LGG2-D802 flash
1) aosp extended based on 7.1.2 or 8.1 versions of Android.
2) flash gapps nano
3) flash magisk zip
4) after rom starts - do the first quick settings - then open Magisk (and if needed update the Magisk manager)
Do not flash both (supersu and magisk) risk to brick the phone.
"device not certified" messege will be always if you use Supersu. It's obviously. Using supersu you unable to use apps like Google pay or any banking apps, because of system root.
Magisk is systemless solution, that's why Google do not recognize Magisk's root. And Play Store on about screen always show "Your device is certified". Also you can Hide root from some apps using Hide option in Magisk manager (it's very useful for local banking apps).
I have a suspicion that you used an older version of Android KitKat (official). And now you try to flash a new Rom (above the Android 7.1.2+). You can't do this. Because you must have Lollipop bootloader. You must be an Android Lillipop first. And then (get Root, then TWRP). And after all that - you will be able to flash some of Rom we are talking about.
zemix said:
Please, don't use this nonsense "overquoting" when you answer to someone. Have some respect to the forum rules, and users.
if you want stable rom for LGG2-D802 flash
1) aosp extended based on 7.1.2 or 8.1 versions of Android.
2) flash gapps nano
3) flash magisk zip
4) after rom starts - do the first quick settings - then open Magisk (and if needed update the Magisk manager)
Do not flash both (supersu and magisk) risk to brick the phone.
"device not certified" messege will be always if you use Supersu. It's obviously. Using supersu you unable to use apps like Google pay or any banking apps, because of system root.
Magisk is systemless solution, that's why Google do not recognize Magisk's root. And Play Store on about screen always show "Your device is certified". Also you can Hide root from some apps using Hide option in Magisk manager (it's very useful for local banking apps).
I have a suspicion that you used an older version of Android KitKat (official). And now you try to flash a new Rom (above the Android 7.1.2+). You can't do this. Because you must have Lollipop bootloader. You must be an Android Lillipop first. And then (get Root, then TWRP). And after all that - you will be able to flash some of Rom we are talking about.
Click to expand...
Click to collapse
Oh Finally!
dowloaded aosp 8.1 and all done. I was trying to use android 9 to be updated. But, pie becoming to be a "creampie" to me so I listened your word. and did it
just opened recovery mode and deleted all the zips. and copied new ones and flashed in order
1) aosp extended 8.1
2) open gapps nano for 8
3) magisk beta (yes this time I tried beta ver and it worked!)
after settings etc. checked with root checker and it was ok. so magisk.apk is not necessary now
thx again bro
HT10 Stock ROM with Majisk, Xposed, and Busybox
ROM Version: HT10 6.0-V01-20170622
The System, Boot, Recovery, and assorted app files for the working setup are zipped as a Titanium backup and needs to be installed from recovery within the Titanium app; available as freeware on the Play Store. The file is packaged as a zip for upload, but will need to be unzipped and placed in the root of your Internal SD directory so that Tianium Backup can recognise it and restore to your device. I have included the individual files that were involved, in case anyone feels like starting from scratch. They include the Homtom HT10 ROM, The MediaTek SP_Flash_Tool_v5.1552_Win (whith which to flash your ROM, TitaniumBackup.zip (which you will simply flash to a non-rooted Stock HT10 ROM from the app on the running device), the Systemless Magisk v. 19.0, Magisk Manager v7.1.1 and the Xposed_Framework_(SDK_23)-89.3_(Systemless) by topjohnwu and his intrepid team of devs, and the TWRP 3.0.3 recovery by Mebhius which has proved so very useful.
Stock ROM installed with Majisk. The ROM is rooted, the root is systemless (Thanks to Majisk),additional modules within Majisk include a systemless Xposed Module. Gravitybox added within Xposed. Busybox added as an additional Majisck module. I have included screenshots of the Majisk status screen, Pokemon Go working on an unsigned and otherwise rooted ROM, and of course, the settings About Phone page. My contribution is by no means revolutionary in anyway, but the results are tested and working. Hopefully, until more work can be done in Lineage, this ROM will allow you to have more freedom and flexibility with the stock ROM.
Long and sort of it: I flashed a clean ROM (making sure to flash the TWRP recovery instead of stock, reboot to System, reboot, then, to recovery. Flash Majisk 9.0, Reboot back into recovery flash the systemless Xposed framework, reboot to system, verify install, flash selected downloads, Install the Xposed Installer apk and the Magisk Manager.apk, reboot. Once root is established, it is verified to be systemless, a root exploerer needs to be installed so you can locate the installed bits of TWRP, Mgisk, and Xposed in System/Bin and Xbin, as well as the Internal SD and either rename or move them discretely away from the prying eyes of apps that will try to verify your root and block you. Then test, test, test, and test some more.
I have found that once verything is installed, verified, and cleaned, you can simply Magisk Hide Magisk for Play Services, Play Store, Google Services Framework, and the desired (Play Store app) like PokemonGo. Then, set Magisk to Core Only Mode in settings, Make sure that Magisk hide is selected, Systemless Hosts are selected, Clear the repo cache, clear data for the deired app, in this case PokemonGo, reboot and have at it. Expect some hung boots in the process. Pull the battery and keep at it. Dont be afraid to master reset or reflash and start from scratch. And dear Lord, dont start importing personal data in bulk until you feel youve reached a stable system build and made the appropriate backups.
Or you can simply restore the files I've provided, reboot, and start your testing there. The choice is yours.
I have made similar inroads with the Lineage 13 ROM for HT10, ported by Nukeer9578 with limited success. There is still much work to be done. I would say, however, that Nukeer9578 got me started with working on the HT10 and I'm grateful for the challenge.
If you are new to this sort of thing, I would advise consulting XDA developers, Google web, and Youtube for further instructions; it is all spelled out if you have the time and patience.
※Please make a backup of your device before installing or updating ROM
XDA:DevDB Information
HT10 Stock ROM with Majisk, Xposed, and Busybox, Tool/Utility for all devices (see above for details)
Contributors
mven45
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2019-03-30
Created 2019-04-02
Last Updated 2019-04-19
Thread closed https://forum.xda-developers.com/android/software/homtom-ht10-stock-rom-mod-root-root-hide-t3917395
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?