[Fix] TWRP data mount issue on Oreo for any TWRP (Update) - Samsung Galaxy Note 8 Guides, News, & Discussion
TWRP data mount fix for oreo
As many users are facing issue because of data mount issue with TWRP on oreo, till it get fixed here is temporary solution.
Download file according root method you are using
1. For Magisk
2. For SuperSU
Installation :
- Flash downloaded file from recovery - Ignore if any message with red color regarding data mount while flashing
- Reboot to system (This step is Must)
- Done !
Now again you can reboot to recovery to check for data mount fix.
PS : You need to reflash this again after every time you flash Kernel/Root/ROM
This can be use with any working TWRP for N8/any kernel stock/custom
Credits : Credits : @Chainfire @topjohnwu @osm0sis and some International forum discussion for original idea
Thank you Dr.Ketan I am experiencing this problem.
I guess twrp will do an update
Envoyé de mon SM-N950F en utilisant Tapatalk
baloo30310 said:
Thank you Dr.Ketan I am experiencing this problem.
I guess twrp will do an update
Envoyé de mon SM-N950F en utilisant Tapatalk
Click to expand...
Click to collapse
Yes this is temporary fix, lots of users were facing lots pain with this issue, at least this will get some relief meanwhile.
For now only with magisk?
kenpaci said:
For now only with magisk?
Click to expand...
Click to collapse
I will make new later today to work on both
works for me on magisk
Envoyé de mon SM-N950F en utilisant Tapatalk
Fix updated - Now it can work on any TWRP/Kernel (working on N8). Also provided for both Magisk/SuperSU root method
PS : You need to flash again whenever you flash ROM/Kernel/Magisk/superSU
dr.ketan said:
Fix updated - Now it can work on any TWRP/Kernel (working on N8). Also provided for both Magisk/SuperSU root method
PS : You need to flash again whenever you flash ROM/Kernel/Magisk/superSU
Click to expand...
Click to collapse
Thank you Dr Ketan. I tried from scratch with the newest fix and now I have my carrier back and TWRP working and everything wonderful. Thank you for all your help and work on this!
So am I correct in saying I flash twrp then the ROM of choice then this fix?
marcushesketh1991 said:
So am I correct in saying I flash twrp then the ROM of choice then this fix?
Click to expand...
Click to collapse
Exactly
Also if you need to flash magisk/supersu then you have to flash this fix again after that
dr.ketan said:
Exactly
Also if you need to flash magisk/supersu then you have to flash this fix again after that
Click to expand...
Click to collapse
Awesome thanks our for the help
Hero
Thank you Dr.ketan. Do i have to flash this every time i flash a new rom?
Wahaj_Alden said:
Thank you Dr.ketan. Do i have to flash this every time i flash a new rom?
Click to expand...
Click to collapse
yes
Actually whenever you flash magisk/Supersu. (most ROM does that)
Thanks for the fix Dr. Katen.
I just applied it and it fixed the /data mounting issue in TWRP; However, Now I'm facing a new issue with Magisk not saving Superuser granting authorizations for root apps.
Every time I open Adaway, for example, I get the notification asking me to grant it Superuser access eventhough I have already given it that authorization few minutes ago. Same applies with every root app. I've checked the Superuser section of Magisk app and it is empty.
So I decided to uninstall the Magisk App and reinstall it again and it didn't help. Rebooting also didn't help
Code:
03-28 20:10:31.357 3219 3219 I Magisk : * Creating /sbin overlay
03-28 20:10:31.358 3219 3219 I Magisk : * Mounting mirrors
03-28 20:10:31.358 3219 3219 I Magisk : mount: /sbin/.core/mirror/system <- /dev/block/platform/11120000.ufs/by-name/SYSTEM
03-28 20:10:31.358 3219 3219 I Magisk : link: /sbin/.core/mirror/vendor <- /sbin/.core/mirror/system/vendor
03-28 20:10:31.358 3219 3219 E Magisk : mount /data/adb/magisk->/sbin/.core/mirror/bin failed with 2: No such file or directory
03-28 20:10:31.358 3219 3219 I Magisk : bind_mount: /sbin/.core/mirror/bin <- /data/adb/magisk
03-28 20:10:31.358 3219 3219 I Magisk : * Setting up internal busybox
03-28 20:10:31.359 3223 3223 E Magisk : execvpe /sbin/.core/mirror/bin/busybox failed with 2: No such file or directory
03-28 20:10:31.359 3223 3223 I Magisk : Magisk v16.2(1620) daemon started
03-28 20:10:31.489 3223 3226 I Magisk : ** post-fs mode running
03-28 23:10:31.867 3223 3312 I Magisk : ** post-fs-data mode running
03-28 23:10:31.867 3223 3312 I Magisk : * Mounting /data/adb/magisk.img
03-28 23:10:31.996 3223 3312 I Magisk : * Running post-fs-data.d scripts
03-28 23:10:31.996 3223 3312 I Magisk : * Running module post-fs-data scripts
03-28 23:10:31.996 3223 3312 I Magisk : * Loading modules
03-28 23:10:31.996 3223 3329 I Magisk : * Starting MagiskHide
03-28 23:10:31.996 3223 3329 I Magisk : hide_utils: Hiding sensitive props
03-28 23:10:31.997 3223 3329 I Magisk : hide_list: [com.google.android.gms.unstable]
03-28 23:10:32.026 3223 3329 I Magisk : proc_monitor: init ns=mnt:[4026531840]
03-28 23:10:32.861 3223 3521 I Magisk : ** late_start service mode running
03-28 23:10:32.862 3223 3521 I Magisk : * Running service.d scripts
03-28 23:10:32.862 3223 3521 I Magisk : * Running module service scripts
03-28 23:10:34.190 3223 3329 I Magisk : proc_monitor: zygote ns=mnt:[4026533640] zygote64 ns=mnt:[4026533642]
03-28 23:11:13.729 3223 8095 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:11:15.363 3223 8273 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:11:44.435 3223 9931 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:14:05.970 3223 17463 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:14:33.823 3223 18127 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:14:43.171 3223 18311 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:15:12.022 3223 18501 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:15:12.065 3223 18506 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:17:31.625 3223 20852 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:17:31.625 3223 20852 E Magisk : su: cannot find requester
03-28 23:17:31.632 20853 20853 W Magisk : su: request rejected (10194->0)
03-28 23:18:39.193 3223 21503 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:19:01.085 3223 22144 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:19:18.133 3223 22262 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:19:20.712 3223 22376 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:19:29.971 3223 22420 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:19:34.801 3223 22544 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:19:34.831 3223 22550 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:31:11.013 3223 23856 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:31:49.143 3223 24268 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:31:55.675 3223 24339 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:31:55.710 3223 24346 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:32:03.414 3223 24424 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:32:03.447 3223 24430 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:32:09.133 3223 24526 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:32:14.642 3223 24589 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:34:01.110 3223 25126 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:34:01.143 3223 25131 E Magisk : sqlite3 open failure: unable to open database file
03-28 23:35:46.910 3223 25363 E Magisk : sqlite3 open failure: unable to open database file
Says only official released binaries are allowed to be flashed
Alright,
I have the 950F/DS XEF
Installed the latest TWRP, everything went fine
Formatted Data, everything went fine
Installed the Data fix, everything went fine
Booted system, went thru the setup, skipped everything until I got to the home screen
Tried to reboot into TWRP so I could Root. Boot Loop and Red writing at the top. Had to do a clean install. Dreaded 7 days again.
Did I miss something? Did I forget the OEM Patch?
jeraldbro said:
Alright,
I have the 950F/DS XEF
Installed the latest TWRP, everything went fine
Formatted Data, everything went fine
Installed the Data fix, everything went fine
Booted system, went thru the setup, skipped everything until I got to the home screen
Tried to reboot into TWRP so I could Root. Boot Loop and Red writing at the top. Had to do a clean install. Dreaded 7 days again.
Did I miss something? Did I forget the OEM Patch?
Click to expand...
Click to collapse
Yup, forgot OEM patch.
Always flash OEM patch after flashing any rom (or TWRP for the first time)
If flashing Oreo rom, always flash data fix after.
Always flash data fix after if flashing root and/or kernel.
Always flash root after flashing kernel.
S5Sickness said:
Says only official released binaries are allowed to be flashed
Click to expand...
Click to collapse
jeraldbro said:
Alright,
I have the 950F/DS XEF
Installed the latest TWRP, everything went fine
Formatted Data, everything went fine
Installed the Data fix, everything went fine
Booted system, went thru the setup, skipped everything until I got to the home screen
Tried to reboot into TWRP so I could Root. Boot Loop and Red writing at the top. Had to do a clean install. Dreaded 7 days again.
Did I miss something? Did I forget the OEM Patch?
Click to expand...
Click to collapse
You need to flash oem fix just after flashing twrp before you reboot
Guys. A bit quick help please? I forgot to install this zip after installing a new oreo rom. The phone works fine. But I can't mount anything from TWRP. No internal or external. How can I flash this .zip?
Related
[Q] (status 0) installation aborted
Hi All, I'm in the process of learning how to make my own custom ROM for my Hannspree HSG1279 Tablet. I've managed to root the device, install CWM-Based recovery v6.0.3.1, and have taken a Nandroid backup. From that backup I've placed the boot.img and the system.tar files into the orginal_update folder for Android Kitchen 0.224 - by dsixda. I've proceeded with creating a working directory, which the contents is the boot.img, system, and META-INF. The Working folder information is as follows: Android OS version : 4.2.2 Device : gs702a Model : HSG1279 ROM Name : 20131219E-V1.2.0_HJT-FW8963-10.1-0x27-0x06 Rooted (Superuser app + su) : NO Rooted (unsecured boot.img) : UNKNOWN BusyBox installed : YES BusyBox run-parts support : UNKNOWN Apps2SD (Apps to EXT) enabled : NO /data/app enabled : NO Custom boot animation allowed : NO Nano text editor installed : NO Bash shell support : NO /system/framework is deodexed : NO /system/app is deodexed : NO radio.img found : NO ROM will wipe all data : NO During the process of creating the rom, I have declined the option to optimize the APK files by zipaligning them, I simply want to get a functioning rom first before I test optional features. I have selected to use updater-script and update-binary in ROM's ZIP file. The rom has also been signed. Where I have trouble is during installation of the rom. I wipe / factory reset the device then attempt installation, however the error im given is "Error in /sdcard/rom.zip (status 0) installation aborted". I have tried to research this error before coming on here and asking, however I haven't been able to find a straight answer. My research indicated that its possibly something to do with META-INF, and the updater script, however beyond that I'm not sure how to proceed. Any assistance would be greatly appreciated .
Safety Net profile pass
• Enable magisk hide from magisk settings, that should pass basicintegrity, if it passes then proceed • install Termux • Open Magisk > Install BusyBox and MagiskHide Props • Reboot • After restarting the device, open Termux and type 'su' (without quotes), press enter • Grant superuser access, then type 'props' (without quotes) • type ' 1 ' • type ' f ' • type ' 22 ' (POCO) • type ' 2 ' (Poco X2) • If you are on pie , type ' 1 ', if you are on Android 10 • type ' y ' The device will restart, and the Safetynet will be PASSED Tested on multiple devices (should work on any device) NOTE - CURRENTLY CTS DEAD ON STOCK MIUI THANKS TO GOOGLE
[VENDOR] [surya/karna] Unified - All Custom ROMS [10] & [11]
PHP: /* * I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...). * Please do some research if you have any concerns about features included in the products you find here before flashing it! * YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. * Your warranty will be void if you tamper with any part of your device / software. * Same statement for XDA. */ FEATURES . The first, the one and the only custom vendor for dynamic partition in the world : I challenge you all to show me who did it before ! . If you find any custom rom with similar work since the first release of this one : it is just a copied and a stolen work [fake Google roms +++] !!! . Compatible with all regions / basebands / firmwares / device variants . Works with All AOSP/CAF based ROMs [10] & [11], Experimental, Official & Unofficial [TESTED] . May works on fake Google roms but i don't take any responsibility . Mount RO/RW available with no bootloop after reboot ! [Magisk/SU required] . SafetyNet passed . Full test passed : audio, ril, wifi, bt, fm radio, camera, sensors, fp scanner, nfc, ... . All known hardware issues on custom roms are fixed : camera, wifi, bt, hdr playback, chrome ... and overheating ! . Custom Kernel with stock zImage [untouched +++] IMPORTANT ! . NO firmware change is needed from the user side, so don't repeat this question many times ... just read up again ! . Formatting /data is required when you flash this vendor the first time +++ . Never go back to the previous versions due to the possible build.fingerprint change [Old releases are automatically removed] +++ . Dirty Update : always delete with file/root explorer or in TWRP this folder : /data/property and reboot You must delete these files & folders in /product partition from your custom rom [File/Root explorer needed] : /product/vendor_overlay/29/etc/audio /product/vendor_overlay/29/etc/audio_policy_configuration.xml /product/vendor_overlay/29/etc/audio_policy_engine_configuration.xml /product/vendor_overlay/29/lib/soundfx /product/vendor_overlay/29/lib64/soundfx & /product/vendor_overlay/29/etc/wifi /product/vendor_overlay/29/overlay & finally /product/vendor_overlay/29/etc/qdcm_calib_data_nt36672c_huaxing_fhd_video_mode_dsi_panel.xml /product/vendor_overlay/29/etc/qdcm_calib_data_nt36672c_tianma_fhd_video_mode_dsi_panel.xml Already included in this vendor ... and since i'm the original author ! [ OPTIONAL ] If you have the madness and the paranoia with security like Google, you can still relock /vendor again to the stock RO state ... But you will not be able to mount /vendor RW again even with root until you reflash the provided vendor.zip again ! How to [terminal or adb shell] : su tune2fs -O verity /dev/block/dm-1 ******* !!! MIUI Users : sorry for you, but this is for custom ROMS " ONLY " TROLLS & NOOBS, stay away ... Please ! !!! Prerequisite: POCO X3 NFC = surya POCO X3 [no NFC] = karna No matter where you live : india, china, russia, europe, usa or africa ... ! Kernel Source [Prebuilt] : Here Created : 2021-02-27 Latest Update : 2021-03-21 DOWNLOAD
RESERVED for "Changelog" Update : [2021-03-21] Highly Recommended ! - overlay folder [/vendor] : secure & total remove ... R.I.P forever ! You can now remove it from here too ... with no issue : /product/vendor_overlay/29/overlay [As always : no /data formatting is required if done in the previous builds !] Update : [2021-03-20] fix compatibility with all custom roms [10] & [11] +++ : - build : preserve AVB structure [R/W still available in root mode] - tune2fs : restore some stock feature flags [dir_index, huge_file, extra_isize] - fstab [kernel & vendor] : small update - vendor selinux : property_contexts fix - build.prop : clean-up Update : [2021-03-18] clean-up & rework from scratch : . all audio config [over 20 files +++] . all media_codecs config . new mixer_paths [=> Exclusive] - true resampling fix : r.i.p audio crackling and all audio issues in UX, Dialer, emulators ... etc [forever] - improve audio & camera recording - audio/video playback [Speaker, Headphones & BT] : Hi-Fi quality, loud & noiseless [but first, you must delete these files with your File/Root Explorer: /product/vendor_overlay/29/etc/audio /product/vendor_overlay/29/etc/audio_policy_configuration.xml /product/vendor_overlay/29/etc/audio_policy_engine_configuration.xml /product/vendor_overlay/29/lib/soundfx /product/vendor_overlay/29/lib64/soundfx] Update : [2021-03-12] - move to global 12.0.8.0 as firmware base [boot & vendor] - ramdisk : . disable mi_thermald and re-enable again thermal-engine [on all custom roms : mi_thermald breaks the proximity sensor & suspend service in deepsleep => avoid hand wave gesture & AOD to work properly !] . clean up & update - vendor_selinux : add more camera permissions in property_contexts - media_codecs : remove unused .xml - ueventd.rc : rework from scratch Update : [2021-03-07] - ramdisk : . update cpuset & schedtune settings . improve memory multitasking . make that "damn" fingerprint truly responsive . enable UFS powersaving . some clean-up & disable MIUI audio service - media_profiles : . rework from scratch . add slow motion profile support : up to 1080p/120 fps & 720p/960 fps . front video camera : add 4K support - build.prop : => update parameters for : camera, ril, performance, playback ... and more Update : [2021-03-05] - rework from scratch : init.qcom.sh & init.qcom.post_boot.sh - ramdisk : clean-up and add init.qcom.power.rc . fix CPU instability : set 300 mHz as CPU minimum frequency for all cores / update schedutil governor parameters . cpu_boost : improve touch responsiveness . add built-in display power saving [for both huaxing & tianma panels] - vendor permissions : rebuild from scratch / fix wronlgy settled paths (by Xiaomi) in some qti.xml - camera : rework from scratch ISO/lowlight config - remove dummy hbtp folder ... since there is no binary to load or device specific config - targetconfig : update CoreCtlCpu to [0,6] - build.prop : clean up and move NFC parameters to build_surya.prop - [Bonus] : Wi-Fi signal improved (x2) !!! . 2.4 Ghz : 144 => 300 . 5 GHz : 433 => 866 [but first, you must delete this folder, with your File/Root Explorer : /product/vendor_overlay/29/etc/wifi ] Update : [2021-03-01] - update msm_irqbalance.conf - update audio_effects.conf & remove audio_effects.xml - universal vbmeta & vbmeta_system added Update : [2021-02-27] - initial release - rework all build.prop (vendor & odm) from scratch - debloated from unused MIUI folders, files & configs - Kernel : . enforcing selinux by default . workqueue enabled in cmdline => better dynamic refresh rate handling by the CPU & stellar deep-sleep . fstab reworked from scratch
the image you made is for enable rw or not? my phone is poco x3 nfc surya
janhammer504 said: To make things clear : POCO X3 NFC = surya POCO X3 (no NFC) = karna No matter where you live (india, china, russia, europe, usa or africa) ... Choose the right vendor.img for your device ! [Both images were tested by me] Click to expand... Click to collapse please share the surya image
aallii2 said: please share the surya image Click to expand... Click to collapse check the DOWNLOAD link up !
janhammer504 said: check the DOWNLOAD link up ! Click to expand... Click to collapse tnx bro i'm downloading n i'll test
its not working after restart didnt boot n just go to recovry
aallii2 said: its not working after restart didnt boot n just go to recovry Click to expand... Click to collapse Wich firmware version you had just before flashing ??? The vendor provided must match the firmware version that you have !!!
janhammer504 said: PREREQUISITE - adb enabled (developer options) - root (Magisk/SU) - adb for Windows (Minimal ADB and Fastboot, provided) - USB cable always connected LIVE Flashing : adb shell su dd if=/sdcard/vendor.img of=/dev/block/dm-1 View attachment 5232189 Reboot your phone right away ... then use your File/Root Explorer to test the mount RO/RW option and reboot again to check that there is no bootloop ! (Optional) If you have the madness and the paranoia with security like Google, you can still re-enable AVB/Verity again ... But you will not be able to mount /vendor RW again even with root until you reflash the provided vendor.img again ! tune2fs -O verity /dev/block/dm-1 Check the full tutorial here to build your own custom vendor ... if you want ! DOWNLOAD Click to expand... Click to collapse ... so, I can confirm that this is indeed working nicely, flashed RW vendor for Surya, just for the sake of the functionality, because I'm not sure about benefits I can get from writeable vendor (forgive my ignorance)... ... Thank you very much for your hard work... just FYI I did flash it in Ofox recovery in built-in terminal, and also directly from running Android via Termux, so you don't need PC for it, just saying...
jeryll said: ... so, I can confirm that this is indeed working nicely, flashed RW vendor for Surya, just for the sake of the functionality, because I'm not sure about benefits I can get from writeable vendor (forgive my ignorance)... ... Thank you very much for your hard work... just FYI I did flash it in Ofox recovery in built-in terminal, and also directly from running Android via Termux, so you don't need PC for it, just saying... Click to expand... Click to collapse i use adb shell because terminal is too small for me, and for making tutorial. the benefit ??? well there are a bunch of fixes to do in /vendor... check here for example (the images i provided are clean with no modification, so i let developers or users doing their own modifications)
janhammer504 said: Wich firmware version you had just before flashing ??? The vendor provided must match the firmware version that you have !!! Click to expand... Click to collapse india 12.0.9 magisk 21.4
jeryll said: ... so, I can confirm that this is indeed working nicely, flashed RW vendor for Surya, just for the sake of the functionality, because I'm not sure about benefits I can get from writeable vendor (forgive my ignorance)... ... Thank you very much for your hard work... just FYI I did flash it in Ofox recovery in built-in terminal, and also directly from running Android via Termux, so you don't need PC for it, just saying... Click to expand... Click to collapse hey bro how you flashed in orangefox? i tried but this happened: sh: adb: command not found
aallii2 said: hey bro how you flashed in orangefox? i tried but this happened: sh: adb: command not found Click to expand... Click to collapse in recovery adb not needed, just use dd if=/sdcard/vendor.img of=/dev/block/dm-1
now i cant install any rom : updater process ended with error 7 pls help
aallii2 said: now i cant install any rom : updater process ended with error 7 pls help Click to expand... Click to collapse O.M.G it looks like you never used terminal this is not a flashable file, it's a command line. open terminal in your recovery to do that. or use adb shell
janhammer504 said: O.M.G it looks like you never used terminal this is not a flashable file, it's a command line. open terminal in your recovery to do that. or use adb shell Click to expand... Click to collapse jeryll said: in recovery adb not needed, just use dd if=/sdcard/vendor.img of=/dev/block/dm-1 Click to expand... Click to collapse Now this came: write error: Operation not permitted jeryll said: in recovery adb not needed, just use dd if=/sdcard/vendor.img of=/dev/block/dm-1 Click to expand... Click to collapse Now this came: write error: Operation not permitted
Use Minimal ADB and Fastboot.zip, it's the simplest and the fastest way. Unzip and click on Minimal ADB and Fastboot.exe type : adb shell su It works like terminal in Windows. You can't go wrong ! Follow the instructions (1 post) !
aallii2 said: india 12.0.9 magisk 21.4 Click to expand... Click to collapse wtf man, you should pick vendor.img from karna folder not surya !
janhammer504 said: Use Minimal ADB and Fastboot.zip, it's the simplest and the fastest way. Unzip and click on Minimal ADB and Fastboot.exe type : adb shell su It works like terminal in Windows. You can't go wrong ! Follow the instructions (1 post) ! Click to expand... Click to collapse i installed 12.0.7.0 global with magisk 22.0 then flashed vendor.img v12.0.7.0 but when restarted it stucked n i pressed power .phone boot but root explorer can't mount rw n just added shell in magisk
Patching boot.img (Magisk)?
Hi there, When Magisk (or adbd insecure) "patched the boot.img", and created a new file "magisk-patched-25200_random-string", - what did Magisk do to boot.img extracted from stock firmware; - what does "patching" mean in the context? Thanks in advance. Regards, Wen
magisk will replace init binary with its own magiskinit and install its root stuff (modified SELinux policy rules with secontext u:r:magisk:s0 for magisk su daemon) and more. https://topjohnwu.github.io/Magisk/details.html#pre-init you have to flash that patched image from fastboot back to device yourself in order to obtain root access.
aIecxs said: magisk will replace init binary with it's own magiskinit and install it's root stuff (modified SELinux policy rules with secontext u:r:magisk:s0 for magisk su daemon) and more. https://topjohnwu.github.io/Magisk/details.html#pre-init you have to flash that patched image from fastboot back to device yourself in order to obtain root access. Click to expand... Click to collapse Ok, I'll look into it.
Btw: adbd Insecure v2.00 by @Chainfire won't modify boot partition, only latest SuperSU v2.79 SR3 by @Chainfire predecessor to Magisk does (although origin of systemless-root idea was born from Magisk)
Question [Resolved] Magisk problem with lineage 20
Hi i have installed latest android 13 stock on t220 after i make a customAP of gsi lineage 20.0 arm64-bvs-vndklite after i make a magisk patched AP and all working but when i open magisk i have this error "su file detected that does not belong to magisk,please remove other superuser programs" but magisk work perfectly Plz how can i solve
izimen said: Hi i have installed latest android 13 stock on t220 after i make a customAP of gsi lineage 20.0 arm64-bvs-vndklite after i make a magisk patched AP and all working but when i open magisk i have this error "su file detected that does not belong to magisk,please remove other superuser programs" but magisk work perfectly Plz how can i solve Click to expand... Click to collapse Delete /system/xbin/su /system/etc/init/su.rc /system/bin/phh-su /system/bin/phh-securize.sh su app in /system/app/phh.superuser Together with *disable toggle SuperSU in phh-treble setting
yshiv666 said: Delete /system/xbin/su /system/etc/init/su.rc /system/bin/phh-su /system/bin/phh-securize.sh su app in /system/app/phh.superuser Together with *disable toggle SuperSU in phh-treble setting Click to expand... Click to collapse thanks all are good now