Hi all,
Not even sure I'm in the right place, still I'd like to share my own experience after upgrading to Oreo last few days. So moderators, if you guys find this irrelevant, or it is in the wrong place, please help me move it accordingly.
I am using XZ F8332. Last few days I decided to say hello to Oreo after some time being patient with the pretty annoying "Upgrade your system" notification. I finally managed to have a fully working Oreo + DRMfix + Magisk + SafetyNet passed and root. Unfortunately good things usually come with bad things too...
At first, I was trying to patch my boot image using ta_poc method. Believe me ta_poc seems to be working on Oreo too, I got all the DRM functionalities working thanks to munjeni & serajr. However, it doesn't seem to be working with both Magisk and SuperSU. I tried all recent versions of those two e.g. Magisk v14, Magisk v14.5 beta, SuperSU v2.79 SR3, SuperSU v2.82 SR5, etc... ALL cause bootloops! I had to come to a conclusion that any methods that patch your modified (with ta_poc) boot image will cause bootloops. There's one thing I didn't try: SuperSU system mode which installs to /system. What's the point of system-less then? But it's up to you to try this.
The above means you are most likely gonna lose root if you go with ta_poc on Oreo. So I had to give ta_poc up and go with DRMfix instead. I got into a few troubles then.
I was initially trying to keep my userdata intact, so I didn't do a full wipe, I actually wiped everything except only my userdata (including data in sdcard). DRMfix didn't fix at all. All I got was only "FIDO_KEYS: Provisioned", the rest was "general error!" and of course DRM functionalities didn't work. I did some search, followed some guides saying about removing these directories: /data/credmgr, /data/drm and /data/mediadrm. There's even a script named "SafetyNet-Cleaning-Tools" also does exactly the same. Perhaps I wasn't that lucky enough. It just didn't work. Until I had to pull all of my data out, do a FULL WIPE including userdata, DRMfix worked then.
Next thing is to get Magisk (or SuperSU) working to have root. I knew recent update of SuperSU causes Xperia devices into bootloops. I also used Magisk on Nougat too. Why not now? So I flashed Magisk v14. Uh oh... I met my old dear friend again, Mr. Bootloops. So Magisk v14 doesn't work on Oreo. But v14.5 beta does. That's how I got it fully working.
Then I pushed my data back to sdcard (including a nandroid of course), did a restore DATA ONLY in TWRP and manually delete the folders mentioned above. After phone started, everything went back. I smiled.
Some existing Magisk modules started to work without any problems. But some other they need busybox. Without any thoughts, I immediately installed osm0sis' busybox installer, the one on Magisk repo. Weirdly it said "Magisk is not activated". I tried other modules, same issue. So only existing modules work, I couldn't install any new modules using Magisk Manager. "Use TWRP then" I thought. I went to TWRP and flashed the busybox installer. My old dear friend came and said "Hi! Bootloops!!" to me again. This time I used Magisk uninstaller to clear magisk files and re-flashed it again. I was able to get back in. I tried YashdSaraf's busybox universal installer. Same issue. Maybe I haven't tested well enough or maybe I went completely wrong way, but looks like busybox isn't working on Oreo? Also, I'm not sure this is the right way to do it, or we have to "clean install" Magisk too? Like uninstall everything first and re-install module by module all over again?
Also, after some Magisk uninstalls and reflashs, suddenly my DRMfix was no longer working. It displayed "general error!" in Service tests -> Security. I tried to fastboot the modified boot image again. Not working. There's no way to get it back except a FULL WIPE. I didn't get it. System-less approach is supposed to have nothing to do with our files. Somehow it does leave some traces, which we need a FULL WIPE to get rid of it? Maybe it isn't just the 3 folders mentioned above, there's maybe more?
Additionally, on Oreo I got some other bad stuffs:
- Adaptive brightness keeps adjusting, going darker and brighter very very quickly. It's no doubt an Oreo's bug.
- Cannot open Titanium Backup. It crashes right after you open it. I tried v8.0 and v8.1. Same issue. Maybe it's because busybox isn't installed?
- I have a feeling battery drains issue comes back. Looks like its consuming more battery than latest Nougat I'm not sure. Haven't got time to do some stats yet.
Last but not least. When I was pulling / pushing data to / from, I noticed that the storage space somehow changed! My phone is 64gb but the second time I got it fully working, it said "storage is 80% full..." and when I opened Settings -> Storage it showed only 21gb! What I did to get it fixed was to run fastboot format userdata. Then I let the phone start normally (without old data), after finishing setup, I turned off and went to TWRP to restore DATA ONLY. Problem solved. I got my storage back. But I have never figured out why. Maybe something wrong with adb pull / push in recovery?
If you've read down this far, I hope my experience could somehow help you avoid encountering the problems that I did.
Me personally I think I will go back to Nougat and stay low for a while. You understand why. Another reason is I also wanna try the "official" xposed for nougat for a little more. rovo89 is freaking awesome. man, he's a legend.
References:
I used this tool to patch my boot image (kernel). This tool origins by tobias.waldvogel but I used the "unofficial" one here and here modified by serajr for the ta_poc method. Thank you guys for this amazing tool.
Magisk latest versions here
SuperSU v2.82 SR5, v2.79 SR3
SuperSU System Mode v2.82 SR5 here
osm0sis' Busybox installer here
YashdSaraf's Busybox universal installer here
Special thanks to serajr, juanpirulo, munjeni, rovo89 and tobias.waldvogel for your amazing works & supports. I dont tag you guys here coz I dont wanna bother you guys
Been there... I feel like that phone don't want to work with poc and Magisk...
FakeMobile said:
Been there... I feel like that phone don't want to work with poc and Magisk...
Click to expand...
Click to collapse
ta poc needs to be rebuild, but munjeni probably dont wanna work in his tool anymore. But serajr´s tool works well so you can root xz oreo with magisk. cheers
Yeah it what I have atm, but I still can't mirror cast to my tv because it not real drm keys
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.
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.
Hello there, back in the day (2019 in March or April the phone shipped with Android 9) I rooted my galaxy S10+ Exynos with Magisk and stock recovery (because TWRP method did not exist yet or did but non twrp method looked safer, I forgot the reason)
Then I forgot about TWRP and even upgraded to Android 10 like this:
(standard procedure, download android with Friya, then patch ap file with magisk, then flash it with odin)
Well I used my phone as always, forgot about twrp, but always had a little voice in my head telling me, that twrp is good idea, what if something happens, I would at least be able to copy my data)
So I decided to flash twrp, to ease my mind a bit, and also be able to copy apps to /system/priv-app
So I am using Android 10 (see no reason to upgrade, what I need is there I prefer OneUI 2.0 over later versions and I dont want to make my device slower or loose some obscure api function that I dont even know exists until I need it)
Now, can I just use official twrp app and let it do its thing (I have root), or do I need to download twrp with the app, but prepatch it with magisk before I install it? (I read conflicting info, on xda they say you need to prepatch it, while on twrp guide: https://twrp.me/samsung/samsunggalaxys10plus.html
They say to just use the app if you already have root, so I am confused now
It seams using the app is the easiest and most safe method
Thanks for Anwsering and Best Regards
only in case recovery and boot share the same partition, you will lose magisk after flashing TWRP (does not apply)
alecxs said:
only in case recovery and boot share the same partition, you will lose magisk after flashing TWRP (does not apply)
Click to expand...
Click to collapse
well, I gues this did apply to me, because I tried to flash TWRP with the app (latest version: twrp-3.7.0_9-2 that the app offered, it offered 2 files .img or .img.tar, and I chose to flash .img), and now my phone cannot boot, its stuck in download mode it says with red letters
kernel: Could not do normal boot, (DT LOAD failed)
I don't know know what happened, I only flashed recovery, and bootloader is unlocked
adb doesn't work
I cannot even get to recovery
So what now? Can at least flash TWRP somehow back so I can get ot my files (I have most of my videos on an SD card, but 2 or 3 are on internal storage )
I would reflash Android 10 anyway if it wasn't for the files
you can flash recovery.img as tar file but that is useless for backup stock ROM userdata. if you still have the magisk_patched.tar you can flash it to get your data back. don't flash unpatched stock boot.img this will most likely result in data loss.
I would first try older TWRP as DT LOAD failed (device tree) looks like TWRP problem to me.
alecxs said:
you can flash recovery.img as tar file but that is useless for backup stock ROM userdata. if you still have the magisk_patched.tar you can flash it to get your data back. don't flash unpatched stock boot.img this will most likely result in data loss.
Click to expand...
Click to collapse
OK
after installing TWRMP
3.4.0 I got into recovery
I guess the latest version twrp-3.7.0_9-2 is broken (because I tried flashing from Odin and I got the same error
but 3.4.0 works now
Well then I got into a non rooted android state (I couldnt boot into the rooted one because if I held volume up I just got into TWRMP)
I do have my magisk patched AP file (I did keep that), so I tried flashing it by odin to get into rooted state again, but then got scared because I was aftaid it would delete my data, so pulled the plug out, immediately after I discovered its flashing system.img (it just started)
thats where I interupted it
<ID:0/035> SingleDownload.
<ID:0/035> dt.img
<ID:0/035> dtbo.img
<ID:0/035> system.img
<ID:0/035> __XmitData_Write
<ID:0/035> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So then phone would not boot, not in TWRMP not in android anymore, so I flashed TWRMP again and now at least
I am in TWRMP (I can see my files, but they are encrypted (they have wierd names but size does seam to match my files)
So how do I reflash android now, without messing with /data partition?
or can I somehow backup just data partition, reflash android and flash /data back?
let the magisk_patched.tar flash, just make sure you don't flash CSC (HOME_CSC is fine it won't erase userdata)
alecxs said:
let the magisk_patched.tar flash, just make sure you don't flash CSC (HOME_CSC is fine it won't erase userdata)
Click to expand...
Click to collapse
Yey, that did it (that was scarry), now root works, as well as android 10 (for some reason Magisk Manager does not open (but all the magisk modules work)
Now, I did patch this ap file back in the day I updated android to 10 so
I used Magisk Manager 7.4.1.291c718b
and if I remember corecly (thanks got I recorded everything) I patched the AP file for Magisk 20.2-11b7076a)
Now I have Magisk Manager 8.0.7 installed
So after I downgraded my Magisk manager to 7.5.0 it opened
Now I just have to figure out how to install Magisk v21.4 which is the version that belongs to my Magisk Manager 8.0.7, because Magisk Manager won't let me install a custom magisk, it only wants to download the latest version
you can install latest Magisk apk and patch stock boot.img again. Anyway I would do a backup with Migrate and adb pull -a /sdcard first.
or you can paste this url as custom channel and install older magisk if you want to.
https://raw.githubusercontent.com/topjohnwu/magisk_files/b0694fad86/stable.json
alecxs said:
you can install latest Magisk apk and patch stock boot.img again. Anyway I would do a backup with Migrate and adb pull -a /sdcard first.
Click to expand...
Click to collapse
aha, I see
is there any other way besides patching my AP file again? (I mean Magisk can clearly update itself somehow)
I mean, Magisk Manager does open (but only version 7.5.0, not version 8.0.7), and I have root its just that I don't have Magisk Manager 8.0.7
So how do I install a specific Magisk version from Manager? (I did try to install like a Magisk module, but now I am stuck in download mode again, so lets install Android 10 again )
look in the json for download link
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
https://github.com/topjohnwu/magisk_files/commits/master/stable.json
https://github.com/topjohnwu/magisk-files/commits/master/stable.json
alecxs said:
look in the json for download link
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
https://github.com/topjohnwu/magisk_files/commits/master/stable.json
https://github.com/topjohnwu/magisk-files/commits/master/stable.json
Click to expand...
Click to collapse
OK, after I installed Android again (with my older prepatched magisk)
Not sure what happened but now Magisk Manager 8.0.7 opens and says I have 20.2-11b7076a installed
of course as this combo should not exist, magisk Manager cannot see any modules (modules are there in /data/adb/modules and they do work, its just that Magisk Manager cannot see them installed, which means you can not easly delete them and you could install them over and over again, since Manager would not know that they are there)
So now I need to find a way to update to Magisk 21.4
So how would I do that (I tried the module install method before (I downloaded 21.4 from official github release pages) , but that just got me stuck into download mode again, so any other way, is there a patcher for computer maybe?
I mean I can only install the latest version, even if I disable internet, I cannot select a specific version
refer to post #8
Thanks, after spending 3hours to get into magisk I decided to share my procedure (because I forget it a lot)
FIrst: make sure your phones last state was power off (you can eather power off from red button or from recovery)
Then turn phone on and start holding power button + bixby + volume up, and count to 10 then release (not 11, 10, if you count to 11 you will get to recovery)
To try out if you are in magisk mode (without ruining your saved wifi passwords), you can plug the phone into the charger, if it turn on normaly, you are in magisk, if it shows battery charging, then you are not in magisk mode)
OK, I tried updating Magisk with https://raw.githubusercontent.com/topjohnwu/magisk_files/b0694fad86/stable.json
but for some wierd reason, it doesn't want to update, its stuck on 20.2-1
OK,. I tried installing Magisk Manager v7.4.1 and when launching it, it said that it patched dtbo.img and it needs reboot, so after I reboot, I am stuck on download mode again
It sayd: DT table header check fail
well, lets install Android 10 a third time
wait, you're booting into recovery to get into Magisk? you can use Nemesis kernel to skip this.
https://forum.xda-developers.com/posts/81316371
alecxs said:
wait, you're booting into recovery to get into Magisk? you can use Nemesis kernel to skip this.
https://forum.xda-developers.com/posts/81316371
Click to expand...
Click to collapse
Yes I am, but its allright, I am used to this
one day I will have to compile my own kernel anyway (to add some drivers to the phone)
Now I have to figure out why Magisk 21.4 won't install
I tried patching my AP file with it, but no matter what I do, I cannot get into it for some reason? (even my trust and tried method does not get me into it, while it got me into 20 all the time)
Is this version broken?
Whats the latest magisk version that still supports Magisk Hide (usefull thing that always worked for me)
With Nemesis kernel no need for button dance, it boots straight into Magisk. Magisk Hide exist up to v23 but there is also unofficial Magisk v25
[Discussion] Magisk Delta - Another unofficial third-party Magisk fork
This is not an officially supported topjohnwu project. If you are looking for official Magisk source, please go to this page Introduction Custom Magisk fork by HuskyDG. Sync with official Magisk adding back MagiskHide...
forum.xda-developers.com
alecxs said:
only in case recovery and boot share the same partition, you will lose magisk after flashing TWRP (does not apply)
Click to expand...
Click to collapse
Magisk needs the ramdisk of the recovery/TWRP to patch it. If flashing a non-prepatched image you will lose root.
WoKoschekk said:
Magisk needs the ramdisk of the recovery/TWRP to patch it. If flashing a non-prepatched image you will lose root.
Click to expand...
Click to collapse
Yea, I discovered that already
Now I am trying to get it back and failing
UPDATE: after installing Magisk 23 (last version that has Magisk Hide), prepatching AP file, and flashing it like 10th time, I finaly have root
Do I dare to try TWRP again? (I guess I need to prepatch it with Magisk before I install it with odin? (but which file do I install there are 2 files provided (twrp-3.4.0-2-beyond2lte.img.tar or twrp-3.4.0-2-beyond2lte.img)?
patch the tar file