• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[Fix] TWRP data mount issue on Oreo for any TWRP (Update)

Search This thread

dr.ketan

Recognized Developer / Recognized Contributor
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
 

Attachments

  • N8_Data_mount_fix_Magisk.zip
    1.4 MB · Views: 14,298
  • N8_Data_mount_fix_SuperSU.zip
    3.7 MB · Views: 10,018
Last edited:

dr.ketan

Recognized Developer / Recognized Contributor
Thank you Dr.Ketan I am experiencing this problem.
I guess twrp will do an update

Envoyé de mon SM-N950F en utilisant Tapatalk
Yes this is temporary fix, lots of users were facing lots pain with this issue, at least this will get some relief meanwhile.
 

Flame Red

Senior Member
Nov 5, 2012
756
182
Samsung Galaxy Z Fold2
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

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!
 

طوني تبولة

Senior Member
Apr 8, 2011
162
30
DC Metro
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
 
Last edited:

jeraldbro

Senior Member
Jun 15, 2012
159
37
Google Pixel 5
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?
 

shouren04

Senior Member
Feb 17, 2013
1,092
400
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?

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.
 
Last edited:

dr.ketan

Recognized Developer / Recognized Contributor
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?
You need to flash oem fix just after flashing twrp before you reboot
 

Top Liked Posts

  • There are no posts matching your filters.
  • 27
    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
    5
    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
    3
    Thank you Dr.Ketan I am experiencing this problem.
    I guess twrp will do an update

    Envoyé de mon SM-N950F en utilisant Tapatalk
    Yes this is temporary fix, lots of users were facing lots pain with this issue, at least this will get some relief meanwhile.
    2
    For now only with magisk?
    I will make new later today to work on both
    2
    Hello i have a samsung Galaxy s8 and the same problem but your fix dont work can you help me ?
    Check your S8 S8+ forum, I have posted separately for your device