Related
Hello,
I wanted to test the Engineering Mode and I followed the guide posted on twitter by fsociety (Used the adb method to enter the 'angela' code). Turning engineering mode on had no visible impact but on subsequent reboot, I lost root and Safetyet got violated (More specifically, CTS).
Setup:
OnePlus 5
OxygenOS 4.5.14
Magisk (latest)
This setup used to work fine and SafetyNet was intact. Things got bad after unlocking the engineering mode.
This is what I have done so far:
Tried *#8011# code to reset settings but I have no luck.
Re-installed the ROM (dirty flash)
Uninstalled Magisk and re-installed Magisk. (but still no root)
Installed SuperSU (systemless) but no luck rooting the phone.
Tried setting "setprop persist.sys.adb.engineermode 0" and "setprop persist.sys.adbroot 0"
Can someone tell me what I can do to fix this?
There's a debloat app in the themes and apps section. You can remove the engineering mode bloatware and see if that helps. You can also try a clean flash instead of a dirty one. If that doesn't work either you can always format your data with TWRP which will wipe everything on the phone except TWRP, use a computer to copy the ROM zip and Magisk to your phone and flash them in TWRP. If you do a clean flash or the latter I would set up the phone fresh instead of from an Android cloud backup because the cloud backup will restore some OOS settings and data and might restore your problem.
There are probably less drastic ways to solve your problem but I don't know them. Good luck.
It got fixed somehow. I ran the *#8011# code and used my computer to set the ADB properties. I flashed TWRP again and installed Magisk and bam! It worked!
I'm rooted using Magisk and I'm using ElementalX kernel, I do not have TWRP installed as I want to get OTAs... my question is, can I re-ecrypt my data without losing Magisk? I remember TWRP having problems decrypting the partition when I first tried to install Magisk/EX so, in case I lose Magisk, can I reinstall Magisk/EX in TWRP or Fashfire once I re-encrypt my device? (i.e. can TWRP decrypt "user encrypted" data partitions? and/or can Magisk run from an encrypted data partition?)
jhonyrod said:
I'm rooted using Magisk and I'm using ElementalX kernel, I do not have TWRP installed as I want to get OTAs... my question is, can I re-ecrypt my data without losing Magisk? I remember TWRP having problems decrypting the partition when I first tried to install Magisk/EX so, in case I lose Magisk, can I reinstall Magisk/EX in TWRP or Fashfire once I re-encrypt my device? (i.e. can TWRP decrypt "user encrypted" data partitions? and/or can Magisk run from an encrypted data partition?)
Click to expand...
Click to collapse
You have a premise incorrect here... If you are not 100% stock, you CANNOT take an OTA, even if you have stock recovery... you have modified the kernel, ramdisk image (Magisk), and likely the system partition (if not, why did you bother to root?), so OTA updates will FAIL. Even with FlashFire they are less there is less than a 50% success rate with this device when rooted.
Although I haven't tried in a long time, TWRP should handle encryption fine, as long as you know the password/PIN... I can't speak for ElementalX specifically, but it is a mainline kernel so I think it should be fine.
The point is that once you have unlocked the bootloader, your device security is pretty much zero... that is kind of a given, encryption helps safeguard your private information, but unlocked bootloader negates FRP and anyone could just fastboot TWRP, wipe and enjoy using your device. This is one of the reasons (of several) that I have stopped unlocking the bootloader and rooting anymore.
My question was mainly about Magisk and TWRP working with encrypted partitions.
About the security, I'm aware of the implications and I just want to keep my data safe, which is more important than the device itself.
As for the device modifications, AFAIK ElementalX uses the ramdisk just as Magisk does, it doesn't write anything to the kernel partition, also, I haven't modified /system at all; all possible modifications I've done have been through Magisk modules and Xposed (which I installed systemlessly of course). The main reason I rooted is indeed Xposed so I can use stuff like NeoPowerMenu, Whatsapp Extensions, ActivityForceNewTask, etc.
Given the fact that I've only modified the ramdisk so far, are you sure that I can't accept OTAs? (I know they'll break my current setup, but it should be easy to fix)
jhonyrod said:
My question was mainly about Magisk and TWRP working with encrypted partitions.
About the security, I'm aware of the implications and I just want to keep my data safe, which is more important than the device itself.
As for the device modifications, AFAIK ElementalX uses the ramdisk just as Magisk does, it doesn't write anything to the kernel partition, also, I haven't modified /system at all; all possible modifications I've done have been through Magisk modules and Xposed (which I installed systemlessly of course). The main reason I rooted is indeed Xposed so I can use stuff like NeoPowerMenu, Whatsapp Extensions, ActivityForceNewTask, etc.
Given the fact that I've only modified the ramdisk so far, are you sure that I can't accept OTAs? (I know they'll break my current setup, but it should be easy to fix)
Click to expand...
Click to collapse
Positive... 99% sure they will fail. And although Xposed may be installed systemless, it's modules still modify /system.
I am trying to re-root my SM-T380 after updating to Pie and am following the latest process per [TWRP 3.2.1-1] [ROOT] Tab A SM-T380/T385 - 10/02/2018 but am running into some issues with steps 3 & 4.:
Boot to TWRP
Format the Data partition (not wipe) using the FORMAT DATA button under Wipe options
Install the memory decryption patch
Assume this is the file found in Ashyx's siganture Samsung encryption disable patch but I can't find any mirrors when trying to download it. Is this the right file for the memory decryption patch?
Install the modified kernel
The file for the SM-T380 found in this post appears to be for the T380DXU3CSI5 but the current stock image is T380DXU3CSL2 for the latest firmware installation (Jan 2020 security patch). I assume a new kernel is needed for this latest version. Is that the case? Also, the file is in tar format but need in zip format to flash in TWRP. Is it as simple as repackaging the tar into a zip file instead?
Install Magisk
Thanks for the help!
I will write out what I just got to work with the latest update of Android Pie for the Samsung Galaxy Tab A T380 running T380DXU3CSL2, security patch January 2020. I have tried all of the methods on the main TWRP/Root thread (which is now closed) and only had success with one.
To clarify, yes - using the patched boot.img from ashyx that was made from T380DXU3CSI5 WILL work with T380DXU3CSL2 (latest as of time of writing) just fine. Make sure to flash Stock first and OEM Unlock.
Ashyx does give some files still needed in his/her first post on the main TWRP thread, but the boot image and the DM-verity are buried within a 66 page thread. Out of respect for ashyx's wishes I will not direct link to files. Get TWRP from the first post here. The patched boot image and DM verity no encrypt get from the guide here by user zfk110. Pg. 65 of the TWRP thread. The guide itself did not work for me though. Just grab the files.
So, files you will need:
>twrp_3.2.3-1_sm-t380_oo_4119.tar (TWRP)
>T380DXU3CSI5_patched_boot_111119.tar (boot.img inside the .tar)
>Latest Magisk version here
>Tab_A_2017_Pie_forced+encryption_disabler-1.zip (no-verity-no-encrypt)
Not only have I found RMM Bypass unnecessary, but in my many trials I think maybe it was causing an issue for me. Perhaps someone much smarter than I can explain, but there is no setting in build.prop to need it - I did check.
TWRP/Root:
>Flash TWRP with Odin with "Auto Reboot" setting turned off: (file: twrp_3.2.3-1_sm-t380_oo_4119.tar in AP slot)
>Boot straight to TWRP (home + vol down + power to get out of download mode then as soon as the screen flashes swap to home + vol up + power),
>In TWRP main menu press "Wipe" and the "Format Data", type "yes" to proceed.
>Reboot to TWRP by going back to main menu of TWRP, select "Reboot" then "Recovery"
>Install boot.img to your boot partition from your external SD card in TWRP (there is a YT video how to do this within TWRP if you need help, just Google it. The file you need is: T380DXU3CSI5_patched_boot_111119.tar then extract boot.img from that for TWRP (use ZArchiver or a program that will unzip .tar). It MUST be in .img to install it with the TWRP "Image" button. TWRP won't even read that the .tar is there, and I don't recommend Odin for this)
>Install Magisk from your external SD card (I used the latest, 20.4 just fine)
>Install the DM-Verity Forced Encryption Patch from your external SD card (file: Tab_A_2017_Pie_forced+encryption_disabler-1.zip)
>Wipe Cache and Dalvik
>Reboot to System
Notes:
Boot image must be first before flashing the others. I tried it after Magisk et.al as with a number of people's directions and several other configurations in addition both in TWRP and with Odin (and the other boot image as well on the thread: t380_boot_pp.img - no luck on XSA for me at least) and it caused a bootloop every time. I don't know why. The smart guys are on the TWRP thread but it's closed (and confusing). I just try things.
To the other OP question here - use the later version of the DM-verity patch - the original one (no-verity-no-encrypt_ashyx) you are referring to is a different size and structure (I have it archived) so it is probably necessary to use the Tab_A_2017_Pie_forced+encryption_disabler-1.zip. It's on pg.65 on zfk110's guide that I linked above (though again, the guide itself did not work for me).
Edit: I know someone could find this method out from the big thread but I know what it is like to feel newby and get confused and want to give up. And the number of different methods and files on that dang thread was a bit maddening honestly and frequently in direct conflict with each other.
Thank you for the guide Winston Churchill, I tried following it for my device Samsung Tab A T380 (build T380DXU3CTH4) but I am stuck at installing Magisk. The patched boot.img is installed successfully but when I go to the system and Magisk does not appear so I have to install it manually with Magisk.apk file. Then when I check the status it says "Installed N/A, Ramdisk Yes, A/B No, SAR No" and root is not active.
I really appreciate any help on this!!
Many thanks Winston Churchill, this worked for me after many failed efforts using other methods and procedures.
Just one or two cautions, as I had to go through the process twice -- because the first time I got locked out with an "unauthorized" firmware notice on the first reboot. I'm not sure if it was because I did not flash the RMM Bypass the first time, or I didn't make sure my OEM Unlock was showing after flashing TWRP, etc. At any rate, I ended up with the RMM Prenormal state.
So I started over . . .
- Odin-flashed my Pie version 3CSI5 one more time
- Setup, went through the time and software update thing to get OEM Unlock to show, and enabled USB Debugging
- Odin-flashed twrp_3.2.3-1_sm-t380_oo_4119.tar
- In TWRP, ran Format Data, rebooted recovery and Formatted again (this has been necessary or advised for other Samsung devices in the past, so I did it here too)
- Then flashed in TWRP:
--- (1) boot.img
--- (2) Magisk 20.4
--- (3) Tab_A_2017_Pie_forced+encryption_disabler-1.zip
--- (4) RMM-State_Bypass_Mesa_v2.zip.
- Wiped Dalvik and Cache
- Rebooted to system
- Made sure OEM Unlock showed and USB Debugging was enabled
- Installed Magisk Manager 7.5.1
- Opened Magisk Manager and made sure Magisk was installed (sometimes it takes a reboot to see Magisk, and sometimes I've actually had to go back into TWRP and reflash it).
All good. So I installed my usual root-needed apps, Speed Software Root explorer, Titanium Backup, Adaway and Power Toggles. All are now rooted and working (including Titanium Backup!!!) and my Android Pie appears to be very stable. Soooo . . . quickly back to TWRP to run a Backup in case something breaks!
I have never had so much trouble rooting any Android device before. The T380 is a nice size and very nice weight, but man oh man . . . I was beginning to wonder if I would ever get it rooted. I can't tell you how much I appreciate (finally) finding this thread and specifically your post.
Moondroid said:
Many thanks Winston Churchill, this worked for me after many failed efforts using other methods and procedures.
Just one or two cautions, as I had to go through the process twice -- because the first time I got locked out with an "unauthorized" firmware notice on the first reboot. I'm not sure if it was because I did not flash the RMM Bypass the first time, or I didn't make sure my OEM Unlock was showing after flashing TWRP, etc. At any rate, I ended up with the RMM Prenormal state.
So I started over . . .
- Odin-flashed my Pie version 3CSI5 one more time
- Setup, went through the time and software update thing to get OEM Unlock to show, and enabled USB Debugging
- Odin-flashed twrp_3.2.3-1_sm-t380_oo_4119.tar
- In TWRP, ran Format Data, rebooted recovery and Formatted again (this has been necessary or advised for other Samsung devices in the past, so I did it here too)
- Then flashed in TWRP:
--- (1) boot.img
--- (2) Magisk 20.4
--- (3) Tab_A_2017_Pie_forced+encryption_disabler-1.zip
--- (4) RMM-State_Bypass_Mesa_v2.zip.
- Wiped Dalvik and Cache
- Rebooted to system
- Made sure OEM Unlock showed and USB Debugging was enabled
- Installed Magisk Manager 7.5.1
- Opened Magisk Manager and made sure Magisk was installed (sometimes it takes a reboot to see Magisk, and sometimes I've actually had to go back into TWRP and reflash it).
All good. So I installed my usual root-needed apps, Speed Software Root explorer, Titanium Backup, Adaway and Power Toggles. All are now rooted and working (including Titanium Backup!!!) and my Android Pie appears to be very stable. Soooo . . . quickly back to TWRP to run a Backup in case something breaks!
I have never had so much trouble rooting any Android device before. The T380 is a nice size and very nice weight, but man oh man . . . I was beginning to wonder if I would ever get it rooted. I can't tell you how much I appreciate (finally) finding this thread and specifically your post.
Click to expand...
Click to collapse
So many conflicting instructions - Why exactly are people flashing this modified boot image and then magisk? Correct me if Im wrong, but isnt that what installing magisk DOES (patches the boot image) when you rename the magisk apk to a zip and install in TWRP? I only FINALLY got this working after I ignored the patched boot.img step completely and simply - flash twrp in odin, reboot rocovery, format data, reboot recovery, flash magisk, disable verity whatever, reboot system..
Dick_Stickitinski said:
So many conflicting instructions . . .
. . . isnt that what installing magisk DOES (patches the boot image) when you rename the magisk apk to a zip and install in TWRP? . . .
Click to expand...
Click to collapse
Magisk patches boot.img for Root access. Sometimes there are also other reasons for flashing a boot.img. I'm not an Android coder so I can't explain every reason why flashing boot.img might be necessary in this case.
. . . "rename the magisk apk to a zip" . . . you renamed a Magisk Manager apk to "zip" for flashing in TWRP? How did that work?
At any rate, my method worked for me and yours (however you actually did it) worked for you. I can say for sure that Android itself can be quirky, for example, my recent experiences with a Galaxy S9 on Pie where, after reflashing the exact same build 5-6 times -- because trying to set a security PIN for some screwy reason kept crashing the system (?!!) -- from one reflash to the next I got different app-disabling experiences. For example, a few built-in apps (like google movies etc) showed the option to Uninstall instead of the expected Disable. The same generic reason why an S8 G950U on Pie v8 can be rooted successfully using @jrkruse's Extreme Syndicate method, and other S8 G950s on Pie v8 will brick. Quirky? Weird, I don't know, can't explain, I just go with the flow as it flows and count my blessings when it works.
Moondroid said:
. . . "rename the magisk apk to a zip" . . . you renamed a Magisk Manager apk to "zip" for flashing in TWRP? How did that work?
Click to expand...
Click to collapse
Yeah, you can rename the APK to zip & flash it in TWRP
The Magisk Manager APK can now be flashed from within TWRP
Magisk is now distributed as part of the Manager APK, meaning you no longer need to flash a separate ZIP file from a custom recovery.
www.xda-developers.com
However, I spoke too soon... I got it to stop bootlooping and actually got it to boot into system, and magisk manager is installed, but still not rooted. When flashing magisk in recovery again (or even extracting the boot.img & patching it in magisk manager, it recognizes it as a magisk-patched boot.img, but it's still not rooted. This tablet is frustrating the hell out of me, I'm about to say the hell with it & toss it.
Dick_Stickitinski said:
Yeah, you can rename the APK to zip & flash it in TWRP
The Magisk Manager APK can now be flashed from within TWRP
Magisk is now distributed as part of the Manager APK, meaning you no longer need to flash a separate ZIP file from a custom recovery.
www.xda-developers.com
Click to expand...
Click to collapse
As of January last year, okay. On older phones/tabs I almost always go with older Magisk versions that were more current with the older device's firmware.
Dick_Stickitinski said:
However, I spoke too soon... I got it to stop bootlooping and actually got it to boot into system, and magisk manager is installed, but still not rooted. When flashing magisk in recovery again (or even extracting the boot.img & patching it in magisk manager, it recognizes it as a magisk-patched boot.img, but it's still not rooted. This tablet is frustrating the hell out of me, I'm about to say the hell with it & toss it.
Click to expand...
Click to collapse
Just a suggestion, maybe try using an older Magisk. I flashed Magisk v20.4 in TWRP and Magisk Manager v7.5.1 after booting to system. Older Magisk (zip and Manager) can be found on topjohnwu's GitHub.
Note, doing it this way, I always have to reboot one more time to see Magisk fully installed and working.
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?
Is there any way to have this phone rooted with encryption working? I would use Lineage, but it doesn't support VoLTE. I'm aware that TWRP will very likely never work again once the phone is encrypted, but that just means that I would have to flash everything I need before encrypting.
I'm on AO 20h ROM currently. My idea was (after making sure I never need TWRP again)
1. Flash stock 20h kernel zip without dm-verity and forced encryption disabled
2. Flash stock 20h boot.img (not sure if this step is necessary)
3. Reboot into system
Does this have the possibility of working? If not, what do I need to do to make this work?
Also, where can I find the stock kernel and boot.img?
I attempted to just flash the boot.img I extracted from the 20h kdz. This didn't work, because when I rebooted it just brought me to fastboot every time.
Edit: Second attempt was to extract the 20h kdz to get both the boot.img and the system.bin files. Then I patched the boot.img with Magisk Manager on my other phone, and moved it back to the sd card. To get the system.img from the 52 binary files, I used the KDZ Extractor which has an option to merge system files into an image. My plan was to flash from TWRP the system.img and then the patched boot.img, but when I went to install the system image, I got a warning message that the image was too big. It shows as 6GB on my computer, and the system partition is 5.4GB.
The only other idea I had in mind was to flash the 20h kdz, but interrupt the installation before it boots for the first time and "encrypts", then go into fastboot and flash the modified boot.img, but this seems excessively risky.
Edit Again: I DID IT!
And I'm not even locked out from using TWRP! Though I'm stuck on Nougat - 10p - with the method I used.
1. Patch extracted 10p boot image with Magisk app
2. Flash 10p with LGUP
3. Flash TWRP to recovery with Lafsploit, reboot to recovery
4. Factory reset from TWRP
5. While still in TWRP, flash the patched boot.img from 1.
Now my next goal is to deodex and try to get signature spoofing working so I can use MicroG. I've tried the Smali Patcher, which appeared to work, but it gets stuck on the T-Mobile splash screen. Same thing happens when I try to install Xposed with any method.
Hi there Pineapple!
Not too many people do care about H918 anymore. I am just like you trying to get something done, so reading everything I can find. I will point out the things I've learned already, but do remember I am not a dev, nor a senior member, not even a very experienced one.
So, above you were saying :
1. Flash stock 20h kernel zip without dm-verity and forced encryption disabled
2. Flash stock 20h boot.img (not sure if this step is necessary)
Well, the "boot.img" contains the Kernel and the Ram Disk, or at least this is what I've read in Android Internals - Jonathan Levin [1st Ed] free on his site. So, now it should be clear that if you'd do 2, it will overwrite 1.
About Encryption and Root:
ENCRYPTION:
Encrypt your phone before rooting, -> root, -> apply ROM. Not the other way around! Tested on Android 4-6.
Once you root or install various ROMs you lose the ability to encrypt your device.
You will have either hanging, rebooting, or the animation stalling
Discussed: http://forum.xda-developers.com/showthread.php?t=2791587 and
http://androidforums.com/threads/how-to-encrypt-a-rooted-device.866968/
Un-root if already rooted. Encrypt. Re-root.
If you Root with SuperSu, you have to manually kick start SuperSU when rooting after the encryption is in effect
Also see about issues with TWRP and Encryption in some devices
(Unable to decrypt the data partition on boot due to bug in TWRP)
(yep, H918, and it seems to be happening on stock ROMs as opposed to AOSP)
not sure if on H918 it is related or not to TWRP bug
Secure Boot (aka dm-verity) also complicates persistent rooting. <- look like you already took measures here
Xposed:
Xposed now also exists as a MAGISK MODULE, so no longer DETECTED if installed thru MAGISK <-try this
Had some issues with Android 7 (Nougat) but most were fixed. <-maybe try different version?
De-Odex
Why? Are you going to be theming your apps? AFAIK,
ODEX = (pre) Optimized Dalvik Exe file format (compressed, not fully compiled yet), separate from .apk
android apps are stored in .apk packages, not as easy nor fast to run as if already Odex-ed
De-Odexing just means having your apps on ROM sort of "collected" back to ".apk". You need that where you want to have an easy access to app resources, i.e. for theming.
QUESTIONS:
1. Could you, please, post the versions of all the components you've used? Like TWRP, Magisk..
2. So, microG doesn't work on rooted stock Nougat on H918? (Damn, I wanted to de-google)
Descent2 said:
So, above you were saying :
1. Flash stock 20h kernel zip without dm-verity and forced encryption disabled
2. Flash stock 20h boot.img (not sure if this step is necessary)
Well, the "boot.img" contains the Kernel and the Ram Disk, or at least this is what I've read in Android Internals - Jonathan Levin [1st Ed] free on his site. So, now it should be clear that if you'd do 2, it will overwrite 1.
About Encryption and Root:
ENCRYPTION:
Encrypt your phone before rooting, -> root, -> apply ROM. Not the other way around! Tested on Android 4-6.
Once you root or install various ROMs you lose the ability to encrypt your device.
You will have either hanging, rebooting, or the animation stalling
Discussed: http://forum.xda-developers.com/showthread.php?t=2791587 and
http://androidforums.com/threads/how-to-encrypt-a-rooted-device.866968/
Un-root if already rooted. Encrypt. Re-root.
If you Root with SuperSu, you have to manually kick start SuperSU when rooting after the encryption is in effect
Also see about issues with TWRP and Encryption in some devices
(Unable to decrypt the data partition on boot due to bug in TWRP)
(yep, H918, and it seems to be happening on stock ROMs as opposed to AOSP)
not sure if on H918 it is related or not to TWRP bug
Secure Boot (aka dm-verity) also complicates persistent rooting. <- look like you already took measures here
Click to expand...
Click to collapse
Yes, while doing this I did learn that the boot image contains the kernel. Looking back, that statement seems silly now that I know that. You are correct about encrypting before root. I did boot into the ROM and did the initial setup, then went back to TWRP (which thankfully had no error decrypting) to flash Magisk via the patched boot image. I did get rid of secure boot too, but I don't know if it was necessary in this case.
Descent2 said:
Xposed:
Xposed now also exists as a MAGISK MODULE, so no longer DETECTED if installed thru MAGISK <-try this
Had some issues with Android 7 (Nougat) but most were fixed. <-maybe try different version?
Click to expand...
Click to collapse
I tried three different ways of installing Xposed. First was through the Magisk Module, but this just made me get stuck on the T-Mobile screen. Had to remove the module from TWRP. Second was "systemlessly" as described here: https://magiskroot.net/install-systemless-xposed-framework-nougat/ . This had the same result. Third was by using only the Xposed Installer 3.1.5 apk, which didn't seem to do anything at all.
Descent2 said:
De-Odex
Why? Are you going to be theming your apps?
Click to expand...
Click to collapse
Deodexing the ROM is necessary to add signature spoofing, which is necessary to install MicroG, so it can pretend to be the real Google Play Services. Usually in the past I've done this with the Nanodroid patcher https://nanolx.org/nanolx/nanodroid but it didn't work here, which was odd because it did work on the Alpha Omega Oreo ROM (which didn't have working encryption).
Descent2 said:
QUESTIONS:
1. Could you, please, post the versions of all the components you've used? Like TWRP, Magisk..
2. So, microG doesn't work on rooted stock Nougat on H918? (Damn, I wanted to de-google)
Click to expand...
Click to collapse
1. The TWRP that's on the laf partition is the one that FWUL 2.7 installed. The TWRP that's on my recovery is 3.5.2_9-0-h918.img. This is the latest official release. To unpack the boot image from the stock kdz, I used LG Firmware Extract 1.2.6.1. I moved the boot image onto another phone which had the latest Magisk Manager app on it (23.0) to patch it with Magisk.
2. Not so far it hasn't. I've deleted everything Google with System App Uninstaller, /d/gapps, and adb. So I'm going without Google Services or MicroG for now. I'd like to change that though, since MicroG makes it far more livable.
So, you have the same end goal as I do - privacy. Have you considered buying the de-googled phone from Brax?
Honestly, this never ending enigma with H918 has me wondering if I should just do that. I mean, I don't sweat some learning and work, but now that the V20 forum is basically dead....
Descent2 said:
Have you considered buying the de-googled phone from Brax?
Honestly, this never ending enigma with H918 has me wondering if I should just do that. I mean, I don't sweat some learning and work, but now that the V20 forum is basically dead....
Click to expand...
Click to collapse
That reminds me of the people on ebay who try to sell 12 year old Thinkpads for 3-4x what they're worth just because they flashed coreboot on them. Except it's way easier to install a custom ROM on a Pixel than it is to flash coreboot. The Pixels are also very different phones than the V20 - no removable battery, ir blaster, 3.5mm jack, good DAC - but if you want the most private and secure smartphone, a Pixel with GrapheneOS (not Lineage) is what you want. Flash it yourself, it's way easier to do it to Pixels than LG's.
Same here.
May-be not that crazy, 3-4 times, but yeah, he sells Google Pixel 4 XL 128 GB with lineage for over $700 where that same phone is $380 on Swappa, lol. It's not as drastic as you memory of e-bay, but it is twice the worth, still.
But then again, considering how much Rob is doing for the community to propagate the awareness, may-be this isn't all that high of a price. Some busy people won't even blink at his prices, but would never invest this much time to decipher everything. Sadly, I, myself is a sucker for the know how, instead of focusing on making money.
You are right in that I did pick this phone as "last phone with removable battery" myself. I actually do remove the battery from time to time when I don't want to be tracked, and drop the phone in the steel covered glove compartment, where no weaker field communication can ever reach it.
Hey, thank you so much for the version numbers, if I decide to go that way, I'll use those exact ones! (So far, do not want to cross into ARB1, but it seems that the lafsploit only works with 10p...)
You know, the Patcher is also available from NanoDroid installed as a Magisk module. Their (Nano) description here:
GitHub - Nanolx/NanoDroid: [MIRROR] See https://gitlab.com/Nanolx/NanoDroid for main repository
[MIRROR] See https://gitlab.com/Nanolx/NanoDroid for main repository - GitHub - Nanolx/NanoDroid: [MIRROR] See https://gitlab.com/Nanolx/NanoDroid for main repository
github.com
states that NanoDroid includes:
on-device framework-patcher for microG support (signature spoofing), with automatic de-odexing up to Android 8.1
Is that the method you tried?
Nanolx says that his patcher patches the sig spoofing support into one of the three locations: Magisk NanoDroid module, Magisk itself and /system. When you were using the patcher, did you see any of these choices?
Also, do you know that the dev of Magisk now works for Google? Now, I know that absolute majority of people would not see anything weird here, but I do, cause I don't trust Google, and thus want to de-google my phone. Specifically, a small conflict of interest while working for google and developing a software that supposed to oversee and support the escape from that same Google by de-googling the phone. Some stockholders might find this quite funny and demand that something is done about this.
I would try older Magisk. I know from other threads, that on 10p, some of the versions of Magisk that did work were: 16.0, 21.0, 21.4 ...
Descent2 said:
You know, the Patcher is also available from NanoDroid installed as a Magisk module. Their (Nano) description here:
GitHub - Nanolx/NanoDroid: [MIRROR] See https://gitlab.com/Nanolx/NanoDroid for main repository
[MIRROR] See https://gitlab.com/Nanolx/NanoDroid for main repository - GitHub - Nanolx/NanoDroid: [MIRROR] See https://gitlab.com/Nanolx/NanoDroid for main repository
github.com
states that NanoDroid includes:
on-device framework-patcher for microG support (signature spoofing), with automatic de-odexing up to Android 8.1
Is that the method you tried?
Nanolx says that his patcher patches the sig spoofing support into one of the three locations: Magisk NanoDroid module, Magisk itself and /system. When you were using the patcher, did you see any of these choices?
Also, do you know that the dev of Magisk now works for Google? Now, I know that absolute majority of people would not see anything weird here, but I do, cause I don't trust Google, and thus want to de-google my phone. Specifically, a small conflict of interest while working for google and developing a software that supposed to oversee and support the escape from that same Google by de-googling the phone. Some stockholders might find this quite funny and demand that something is done about this.
I would try older Magisk. I know from other threads, that on 10p, some of the versions of Magisk that did work were: 16.0, 21.0, 21.4 ...
Click to expand...
Click to collapse
As long as Magisk itself is FOSS and hasn't been proven to be spyware, I'll trust it. The later versions actually have gotten better about privacy, since it now doesn't require internet. And the goal of the Magisk project isn't to de-google your phone. It can aid in de-googling, because you can uninstall system apps, but Magisk is just to gain root.
As for how I tried to use the patcher, I tried from TWRP, which gave me the error "failed to mount /system unsupported a/b device," and then if I tried to flash it from Magisk Manager it gave the error "failed to deodex services.jar"
When you say you tried to flash it from TWRP / Magisk Manager, it is not clear to me if you understand that Nano Patcher is also available as a Magisk module, and if you have tried to add that Magisk nano module or used the Patcher by itself as provided by NanoDroid in a stand alone installer. Since I haven't used Magisk yet myself, I do not know if has the flashing capability and that is what you referred to, or if that meant you added the module. Like I said, still learning here.
I do understand that Magisk is only a systemless root , not a patcher or microG.
The H918 is not an A/B device. Not on Nougat nor Oreo in any case. Obviously, you know that.
So, your device is being misidentified as a much newer device.
I think that if you had tried a version of Magisk or the Patcher that is not YET aware of A/B devices, then possibly such mis-identification would not happen.
Of course the fact that it happens thru TWRP, gives Magisk somewhat an alibi.
I still think it is worth trying. May-be older Patcher first, then with older Magisk.
I keep holding Magisk in my attention because without it doing its job correctly, you could not take the next step, the one that isn't working.
Finally, Try some of these: https://download.lineage.microg.org/h918/ ROMs, they already have signature spoofing handled. I would think an older one might work, as I saw several threads mentioning that the later versions of LOS don't run well on H918.
Also, here is thread you might want to read and post your situation into:
[MODULE/SYSTEM] NanoDroid 23.1.2.20210117 (microG, pseudo-debloat, F-Droid + apps)
NanoDroid NanoDroid is a installer for various OpenSource related things, most noticably microG and F-Droid. It supports direct /system installation, both devices with or without A/B partition scheme, aswell as Magisk Mode (module) installation...
forum.xda-developers.com
That thread discusses NanoDroid used as a Magisk Module, and there are few users experiencing a similar situation (with different errors) and some advices.
Descent2 said:
When you say you tried to flash it from TWRP / Magisk Manager, it is not clear to me if you understand that Nano Patcher is also available as a Magisk module, and if you have tried to add that Magisk nano module or used the Patcher by itself as provided by NanoDroid in a stand alone installer. Since I haven't used Magisk yet myself, I do not know if has the flashing capability and that is what you referred to, or if that meant you added the module. Like I said, still learning here.
Click to expand...
Click to collapse
I'm taking the nanodroid patcher zip from their website and attempting to flash in TWRP, which I've successfully done before on other phones. I also tried using the same zip and installing it as a module in Magisk. I don't think there's a separate file meant specifically for use as a Magisk module. I believe the a/b error in TWRP has something to do with the fact that when I'm in TWRP and I go into the "Mount" menu and select System, the check box only remains ticked for about 5 seconds, then it automatically unmounts again. No idea what the problem is there. I suspect if that weren't an issue, I'd get the same exact error that I get when trying to use the patcher with Magisk.
As for LineageOS for MicroG, that's what I was using before going back to stock, and it was great. But it's sadly unusable as a phone because of the lack of VoLTE. If not for that, this could easily be my "forever phone" with the huge battery.
I'm also now having a strange issue where many system functions (recents, settings menus, autorotate, second screen, statusbar) are running unusably slow, while any other app runs perfectly fine. I have to do more testing to figure out what this is, though. Edit: stuck at T-Mobile logo again. Gonna try to do all this with stock Oreo.
Oops, I am sorry, I forgot, you have said that in your first post that you already tried LOS, man. So, we are stuck? It gets stuck on T-Mobile splash, meaning this is a bootloop, or rather a bootfreeze. I think your other issues must be related to this issue that is preventing you from patching for signature spoofing.
I've been reading up trying to find what is going on with your phone, and I stumbled against this:
You simply swipe the bar to allow TWRP to make modifications to your /system partition. Swiping on this particular screen, you are giving TWRP permission to mount your /system partition as R/W (Read & Write) as opposed to the default of /system being mounted as R/O (Read Only). However, please beware and know what you are doing. If you so much as mount /system as R/W via TWRP, regardless if you actually make changes, a kernel secured with dm-verity (device mapping verification) will prevent your device from booting into the Android OS. Never mount /system as R/W without first verifying whether your kernel has dm-verity enabled. If dm-verity or AVB 2.0 (Android Verified Boot) is enabled, flashing a systemless root script like Magisk 16.0 will patch dm-verity to disabled, as well as disable force encryption in the fstab.
You said you disabled the secure boot. This is aka dm-verity .
Now in your case, you are using the encryption, which needs dm-crypt to be active, correct? These two are related because they both are managed by a DM - device mapper.
When you said you have disabled the secure boot (dm-verity), do you mean that you have maybe chose some options when patching the boot.img with Magisk ? Or did you do it thru some other method?
I keep seeing references to "No Verity Opt Encrypt" without a good explanation of what it is or how to use it or when to use it. I am curious if you have applied that or not, and if you did, where did you read about it.
So, my current thinking is that if you actually failed to disable the dm-verity, this should take you to the bootloop or freeze. May-be DM failed to separate the two and kept both enabled?
The fact that you have touched the /system as r/w according to green above, should trip the dm-verity to bootloop you, if dm-verity is somehow still enabled.
I still do not understand though, why you are receiving a failure to patch.
Also, you have mentioned that you have used a "Smali Patcher". Knowing nothing about nothing, I of course assumed you meant to type "Small Patcher" , i.e. some patcher. Now cleaning up the details I looked it up. Oops. It is actually a real thing. It supposed to examine your system in step 1, and generate a Magisk module, and in step 2, you add that module to Magisk and check it as enabled. I just want to confirm that this is exactly what you have done and this brought you to T-mobile splash screen.
I actually may try LOS for microG, what version did you have that was great?
Because from what I was reading the LOS for 918 has many issues (no 5G tether, no 2nd screen, no WiFi call, etc)
Descent2 said:
Oops, I am sorry, I forgot, you have said that in your first post that you already tried LOS, man. So, we are stuck? It gets stuck on T-Mobile splash, meaning this is a bootloop, or rather a bootfreeze. I think your other issues must be related to this issue that is preventing you from patching for signature spoofing.
I've been reading up trying to find what is going on with your phone, and I stumbled against this:
You simply swipe the bar to allow TWRP to make modifications to your /system partition. Swiping on this particular screen, you are giving TWRP permission to mount your /system partition as R/W (Read & Write) as opposed to the default of /system being mounted as R/O (Read Only). However, please beware and know what you are doing. If you so much as mount /system as R/W via TWRP, regardless if you actually make changes, a kernel secured with dm-verity (device mapping verification) will prevent your device from booting into the Android OS. Never mount /system as R/W without first verifying whether your kernel has dm-verity enabled. If dm-verity or AVB 2.0 (Android Verified Boot) is enabled, flashing a systemless root script like Magisk 16.0 will patch dm-verity to disabled, as well as disable force encryption in the fstab.
You said you disabled the secure boot. This is aka dm-verity .
Now in your case, you are using the encryption, which needs dm-crypt to be active, correct? These two are related because they both are managed by a DM - device mapper.
When you said you have disabled the secure boot (dm-verity), do you mean that you have maybe chose some options when patching the boot.img with Magisk ? Or did you do it thru some other method?
I keep seeing references to "No Verity Opt Encrypt" without a good explanation of what it is or how to use it or when to use it. I am curious if you have applied that or not, and if you did, where did you read about it.
So, my current thinking is that if you actually failed to disable the dm-verity, this should take you to the bootloop or freeze. May-be DM failed to separate the two and kept both enabled?
The fact that you have touched the /system as r/w according to green above, should trip the dm-verity to bootloop you, if dm-verity is somehow still enabled.
I still do not understand though, why you are receiving a failure to patch.
Also, you have mentioned that you have used a "Smali Patcher". Knowing nothing about nothing, I of course assumed you meant to type "Small Patcher" , i.e. some patcher. Now cleaning up the details I looked it up. Oops. It is actually a real thing. It supposed to examine your system in step 1, and generate a Magisk module, and in step 2, you add that module to Magisk and check it as enabled. I just want to confirm that this is exactly what you have done and this brought you to T-mobile splash screen.
I actually may try LOS for microG, what version did you have that was great?
Because from what I was reading the LOS for 918 has many issues (no 5G tether, no 2nd screen, no WiFi call, etc)
Click to expand...
Click to collapse
The "No Verity Opt Encrypt" is a file that disables verity and forced encryption. If you rename the zip, though, you can make it only disable verity or only disable forced encryption. I did flash it with no-dm-verity, but from what you found it looks like Magisk does this for us so it's probably not necessary.
The fact that it bootlooped isn't due to me mounting it. I did that several times before without bootlooping. The issue I had with it was that it automatically unmounted /system after a few seconds, which is why I believe I can't deodex from TWRP.
For the Smali patcher, I don't remember how I attempted to use it. So far my attempts to root and encrypt stock Oreo haven't gotten very far, so I'm going to try this again.
I just used the latest version. I don't use 5G tether so I wouldn't know. The 2nd screen "works" but it just extends the main screen, making the cameras into a notch type thing. I can live without wifi calling, but lte calling won't work, which is, again, the only thing keeping me from using Lineage MicroG.
DUH !
I can't believe sometimes how dumb I actually am. Of course, it says right in the name of the file: "No Verity + Optional Encryption" ! [slamming my forehead into the table] I swear I read it thousand times, but for some reason it did not make any sense to me. I knew it does something about this subject, but I never took it literally!
Thank you for letting me know.
It is cool how the arguments are sent by renaming the patch instead of using the optional parameters. I like that. Magisk does that as well. You flash Magisk.zip and it installs Magisk. You rename it to unistall.zip and flash that, and it uninstalls Magisk.
Please, keep posting if anything changes. If I read something that makes me think I've picked up the scent again, I will let you know. For now I don't know what else to read.
PineappleMousepad said:
I've deleted everything Google with System App Uninstaller, /d/gapps, and adb.
Click to expand...
Click to collapse
You uninstalled Android Device Bridge? I am curious as to why? I mean, yeah, it's Google, but it's most likely harmless, and very useful. Does it call home or something? At some level the entire Android is Google. Yeah it comes from HA, but Google pays. And money talks. I am curious why.
Anyway, I might have found something , I am not sure, but it looks interesting:
So, I am reading this:
Internal Details
The Magic Mask for Android
topjohnwu.github.io
It says:
Paths in /data
Some binaries and files should be stored on non-volatile storages in /data. In order to prevent detection, everything has to be stored somewhere safe and undetectable in /data. The folder /data/adb was chosen...
Click to expand...
Click to collapse
Did removing ADB, somehow messed up the /data/adb folder, and then that messed up Magisk? Is this why some of the operations you have attempted have failed? Like you'd install a module and it would be like you didn't even do anything?
I didn't remove adb. I debloated using System App Uninstaller. For some things that didn't work I used /d/gapps. For other things that didn't work I used adb.
Been messing around with Oreo the past couple days.
I *can* get stock Oreo to work with root and even MicroG - everything works great. Except it refuses to encrypt. The option is there in the menu to "Encrypt Phone". The battery was above 80% and plugged in, I tap the button, and it just takes me to the T-Mobile splash screen and quickly to the lock screen. I know MicroG isn't causing it, since it has this issue with or without MicroG. I get the same result whether I installed 20h from a TWRP flashable zip or if I installed 20h from the kdz with the kdz writer tool https://forum.xda-developers.com/t/tool-kdz-writer.3649818/. It isn't an issue with the recovery partition, as I left that stock and just use TWRP from LAF.
The less ideal option for Oreo at the moment is to have it completely stock from LGUP and just debloat with adb. This means no root or MicroG, but those are the least of the issues. It looks like if you uninstall Google Play Services without also installing MicroG, you get constant error messages saying "Messages has stopped working." No problem, just remove the messages app and use QKSMS, right? Well removing Messages breaks Contacts, which is also the dialer. Removing the dialer and contacts, replacing them with Simple Dialer and Simple Contacts works, but then you get the constant error message "LG IMS has stopped working." Removing LG IMS gets rid of the error messages but, predictably, breaks VoLTE.
Edit: It may not have been Google Play Services that broke the Messages app.
Quick reaction. You are likely right. It probably wasn't the removal of GPS that broke Messaging. There are so many different fixes for that error on the net (which you probably have already mostly tried), that it suggests many different causes for the error.
But, interesting how all that stuff is chained. Almost looks as if intended that way. Don't deny them saying a good bye to google outright, just make it an incredibly deep rabbit hole.
This comes to mind: try "freezing" messaging or anything lower on this chain, in hopes that it is the uninstall that removes some shared dependency and that they haven't thought of you trying to freeze them. I know you wouldn't care all that much if the chain didn't end with VoLTE.