Related
Hi!
After some experiments , ext4 partition lost property rw .
Installing android_3.2.78.ext4 we give root perm. with rights rw . Ok that is true.
Now just installing ES File Explorer , enabe only Root Explorer and change Home Directory : / we can : copy , mkdir, mov , rm .....anywhere ( this is normal )
But how I lost this right .....
Shut down device or >adb reboot .....when device is open I have tried this command:
>adb shell
/# mount
..........................
/dev/loop0 on / type ext4 (ro,relatime,barrier=1,data=writeback)
............................
Now I can't do even >adb shell mkdir xxx ........cannot create directory xxx Read-only file system .
Expert opinions wait !!!
Add all commands > adb shell mount
.............................................................................................................
c:\Program Files (x86)\Android\android-sdk\tools>adb shell
BusyBox v1.7.2 (2011-12-22 03:11:13 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/ # mount
mount
rootfs on / type rootfs (rw)
/dev/mmcblk0p2 on /mnt/system type ext4 (rw,noexec,noatime,barrier=1,data=ordere
d)
/dev/mmcblk0p4 on /data type ext4 (rw,noexec,noatime,barrier=1,data=ordered)
/dev/loop0 on / type ext4 (ro,relatime,barrier=1,data=writeback)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
usbfs on /proc/bus/usb type usbfs (rw,relatime,devuid=1000,busuid=1000,listuid=1
000)
tmpfs on /tmp type tmpfs (rw,relatime,mode=775,gid=1000)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p1 on /mnt/rawfs type rawfs (rw,relatime)
/dev/block/mmcblk0p2 on /mnt/system type ext4 (rw,nosuid,noexec,noatime,barrier=
1,data=ordered)
/dev/block/mmcblk0p4 on /data type ext4 (rw,nosuid,noatime,barrier=1,data=ordere
d)
/dev/fuse on /mnt/nand type fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id
=1015,default_permissions,allow_other)
/dev/fuse on /mnt/storage type fuse (rw,nosuid,nodev,relatime,user_id=1000,group
_id=1015,default_permissions,allow_other)
/dev/block/vold/179:17 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,
noatime,nodiratime,uid=1000,gid=1023,fmask=0000,dmask=0000,allow_utime=0022,code
page=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/ #
..............................................................................................................
Very very strange!!!! No it's work , I have again rights RW .....strange is that I did nothing.....just maybe I have not used 24 hours ....
So i'm trying to root the ADVD (Avaya Desktop Video Device), which is a tablet (sorta) running Android x86 version 2.1 with a totally custom UI on top.
I can already SSH into the device with admin privileges (I get the "#" symbol).
SU and busybox binaries are already available on it.
But i haven't been able to remount the /system partition as rw.
I tried the mount command, busybox, adb and the "mount /system" app but nothing succeeded.
This is the output of the mount command:
Code:
# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
usbfs /proc/bus/usb usbfs rw,relatime 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,relatime,size=4096k 0 0
/dev/block/sda8 /system squashfs ro,relatime 0 0
/dev/block/sda6 /data ext3 rw,nosuid,nodev,relatime,errors=continue,data=writeback 0 0
/dev/block/sda7 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,data=writeback 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,ioch****t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
I tried running the following command:
Code:
mount -o rw,remount /dev/block/sda8 /system
But it still showed as ro.
Any help would be appreciated.
Any idea?
I have just got my S4 Mini and wondering if is it possible to root it? any guides?
Thanks in advance.
Yes, please root for the S4 Mini. It is a good device. Good choice for S2 owners, whose the s3 is too large
Hmm,
hmm
what you can do is
adb shell
think the command is it's mount:
and then see what partition table you've got
can help others to help you to gain root
Code:
you should end up getting something like this: rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/asec type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
[B]/dev/block/mmcblk0p26 on /persdata/absolute type ext4 (rw,seclabel,nosuid,nodev,relatime,data=ordered)
/dev/block/platform/msm_sdcc.1/by-name/system on /system type ext4 (ro,seclabel,relatime,errors=panic,data=ordered)
/dev/block/platform/msm_sdcc.1/by-name/userdata on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered)
/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered)
/dev/block/platform/msm_sdcc.1/by-name/apnhlos on /firmware type vfat (ro,context=u:object_r:firmware:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/platform/msm_sdcc.1/by-name/mdm on /firmware-mdm type vfat (ro,context=u:object_r:firmware:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/platform/msm_sdcc.1/by-name/efs on /efs type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/data/container on /mnt/shell/container type sdcardfs (rw,nosuid,nodev,relatime,uid=1000,gid=1000)
/data/media on /mnt/shell/emulated type sdcardfs (rw,nosuid,nodev,relatime,uid=1023,gid=1023)
/dev/block/dm-0 on /mnt/asec/com.nuance.swype.dtc-1 type ext4 (ro,dirsync,seclabel,nosuid,nodev,noatime)
/dev/block/dm-1 on /mnt/asec/eu.chainfire.mobileodin.pro-1 type ext4 (ro,dirsync,seclabel,nosuid,nodev,noatime)
/dev/block/vold/179:33 on /storage/extSdCard type vfat [/B](rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
the bold part is those who are "blocks for your device"
But these are for I9505 blocks above, so don't try anything with these with commands etc.
So when will we have root to our device? Has anyone got some news on this?
Root
I woud be gratefull for root methode as well. Samsung is installing so many usefull apps and onlu with root you can uninstal them
devguy10 said:
I have just got my S4 Mini and wondering if is it possible to root it? any guides?
Thanks in advance.
Click to expand...
Click to collapse
+1
So will the S4 mini have a section of it's own? I think it deserves it
*give us root access please!!!!
Did no one Dump the partition info ^^
Sent from my GT-I9505 using Tapatalk 4 Beta
LastStandingDroid said:
Did no one Dump the partition info ^^
Sent from my GT-I9505 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Here is from mine, (LTE, Nordic)
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p20 /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,jou
rnal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journ
al_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,j
ournal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_a
sync_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,context=u:object_r:firmware:s0,relatime,gid=1000,fmask=00
06,dmask=0006,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/container /mnt/shell/container sdcardfs rw,nosuid,nodev,relatime,uid=1000,gid=1000 0 0
/dev/block/dm-0 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/com.koushikdutta.rommanager.license-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/vold/179:33 /storage/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask
=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0
002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/extSdCard/.android_secure tmpfs ro,seclabel,relatime,size=0k,mode=000 0 0
/dev/block/dm-2 /mnt/asec/com.smilerlee.jewels-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
I have a S4 mini from France how do Dump the partition info ?
I'm very interested to root my device i need to access some stuff.
frem said:
I have a S4 mini from France how do Dump the partition info ?
I'm very interested to root my device i need to access some stuff.
Click to expand...
Click to collapse
Adb Shell
Mount
And youll see the info
Sent from my ST25i using xda app-developers app
LastStandingDroid said:
Adb Shell
Mount
And youll see the info
Sent from my ST25i using xda app-developers app
Click to expand...
Click to collapse
how do i get the "adb shell"
frem said:
how do i get the "adb shell"
Click to expand...
Click to collapse
Do you have the android sdk
If yes connect your phone to the pc with the cable make sure you have usb debugging on
And write adb shell
Mount
Sent from my ST25i using xda app-developers app
LastStandingDroid said:
Do you have the android sdk
If yes connect your phone to the pc with the cable make sure you have usb debugging on
And write adb shell
Mount
Sent from my ST25i using xda app-developers app
Click to expand...
Click to collapse
I tried to install the SDK, here is the stuff i downloaded : "adt-bundle-windows-x86_64-20130522"
There is a "SDK Manager.exe" file in it but when I execute it nothing happens :
C:\Users\xxxx\Desktop\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86_
64-20130522>"SDK Manager.exe"
C:\Users\xxxx\Desktop\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86_
64-20130522>
This thread isn't about SDK, please fix your problem somewhere else and let us focus on rooting the Galaxy S4 Mini.
Here is my ADB shell info
s4 mini i9195
united kingdom
mount
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p20 /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,context=ubject_r:firmware:s0,relatime,gid=1000,fmask=0006,dmask=0006,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/data/container /mnt/shell/container sdcardfs rw,nosuid,nodev,relatime,uid=1000,gid=1000 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/dev/block/vold/179:33 /storage/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/extSdCard/.android_secure tmpfs ro,seclabel,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.distractionware.superhexagon-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
devguy10 said:
This thread isn't about SDK, please fix your problem somewhere else and let us focus on rooting the Galaxy S4 Mini.
Click to expand...
Click to collapse
Sorry, I just wanted to help by accessing my info.
By the way there is an other thread started on the same subject : http://forum.xda-developers.com/showthread.php?t=2352807
Anyone had luck finding how to root this i9591 yet? would really love to root my phone
If you can force flash a custom recovery it would work. Just need a working one though
Sent from my GT-I9505 using Tapatalk 4 Beta
Hello all.
I will probably release ClockworkMod recovery and an insecure kernel for the GT-I9195 this weekend. With those installed, root can easily be achieved by using the built in root function in recovery.
I don't know what happened, my battery died, I plugged it in, turned the phone back on, and boom, my phone is throwing errors out left and right, and ES File Explorer is saying '/sdcard/' is not found. I've tried going to storage/emulated/0 & legacy, but I get the same not found message.
Storage in System Settings shows that the storage is still being used, and the file browser in TWRP shows all the files are still there. It just seems like the mount points or bindings got all screwy.
My phone is on the BOF5 firmware, it's stock rooted. I've had no problems restarting my phone, usually have to atleast twice a week. Nothing funky installed, atleast nothing that would mess with the SD card. No SW was uninstalled, just frozen, and it wasn't much [Voicemail, Internet (Browser), Hangouts]
I'm really just hoping that someone, somewhere knows a way to help me fix this so I don't have to restore!
krakerx said:
I don't know what happened, my battery died, I plugged it in, turned the phone back on, and boom, my phone is throwing errors out left and right, and ES File Explorer is saying '/sdcard/' is not found. I've tried going to storage/emulated/0 & legacy, but I get the same not found message.
Storage in System Settings shows that the storage is still being used, and the file browser in TWRP shows all the files are still there. It just seems like the mount points or bindings got all screwy.
My phone is on the BOF5 firmware, it's stock rooted. I've had no problems restarting my phone, usually have to atleast twice a week. Nothing funky installed, atleast nothing that would mess with the SD card. No SW was uninstalled, just frozen, and it wasn't much [Voicemail, Internet (Browser), Hangouts]
I'm really just hoping that someone, somewhere knows a way to help me fix this so I don't have to restore!
Click to expand...
Click to collapse
Youre taking all the fun out of it. Backing up and restoring from scratch is half the fun with android phones. If youre gonna root to have fun, be prepared to do the dirty work as well. JMHO
xxSTARBUCKSxx said:
Youre taking all the fun out of it. Backing up and restoring from scratch is half the fun with android phones. If youre gonna root to have fun, be prepared to do the dirty work as well. JMHO
Click to expand...
Click to collapse
Well, I'm looking to do the dirty work, otherwise I would have just restored the phone from my backup weeks ago. But I don't want to do that, because, honestly, there has got to be a way to see this data. With that said, here is the output from running 'mount' in TWRP and Terminal Emulator:
C:\MiniADB\adb shell
~ # ←[6nmount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1418352k,nr_inodes=154938,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime,size=1418352k,nr_inodes=154938)
pstore on /sys/fs/pstore type pstore (rw,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk0p27 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p27 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p25 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
===========================================================================================================
[email protected]:/ $ su
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1414720k,nr_inodes=153121,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=1414720k,nr_inodes=153121,mode=750,gid=1000 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,size=1414720k,nr_inodes=153121,mode=700 0 0
tmpfs /mnt/secure/asec tmpfs rw,seclabel,relatime,size=1414720k,nr_inodes=153121,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=1414720k,nr_inodes=153121,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=1414720k,nr_inodes=153121,mode=755,gid=1000 0 0
/dev/block/bootdevice/by-name/modem /firmware-modem vfat ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/bootdevice/by-name/apnhlos /firmware vfat ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,norecovery 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/bootdevice/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/bootdevice/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/carrier /carrier ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persdata /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,size=1414720k,nr_inodes=153121,mode=050,gid=1028 0 0
tmpfs /storage/emulated/legacy tmpfs rw,seclabel,nosuid,nodev,relatime,size=1414720k,nr_inodes=153121,mode=050,gid=1028 0 0
[email protected]:/ #
Hopefully someone with BOF5 rooted stock can take a look at their mount points and see if they lineup with what I'm getting
krakerx said:
Well, I'm looking to do the dirty work, otherwise I would have just restored the phone from my backup weeks ago. But I don't want to do that, because, honestly, there has got to be a way to see this data. With that said, here is the output from running 'mount' in TWRP and Terminal Emulator:
Click to expand...
Click to collapse
Thanks for posting this.
Hopefully someone who is still on OF5 can match and compare/contrast whats there or not there. Maybe unrooting and OG5 is the way to go or simply trying it in your laptop(if it has a SD cardslot reader and see if it functions properly there) Might be time to get a new card
SD card is fine, internal memory is fine... Found the issue was a corrupted sdcard pointer, once fixed, phone runs like it should
Here list Mount Partition on Realme 5 Pro.
Mount Partition table on Recovery Realme 5 Pro
=====================================
Code:
0 / ext4 /dev/block/bootdevice/by-name/system 0
1 /cache ext4 /dev/block/bootdevice/by-name/cache 0
2 /data ext4 /dev/block/bootdevice/by-name/userdata 0
3 /vendor ext4 /dev/block/bootdevice/by-name/vendor 0
4 /external_sd vfat /dev/block/mmcblk0p1 0
5 /boot emmc /dev/block/bootdevice/by-name/boot 0
6 /recovery emmc /dev/block/bootdevice/by-name/recovery 0
7 /misc emmc /dev/block/bootdevice/by-name/misc 0
8 /aboot emmc /dev/block/bootdevice/by-name/aboot 0
9 /abootbak emmc /dev/block/bootdevice/by-name/abootbak 0
10 /modem emmc /dev/block/bootdevice/by-name/modem 0
11 /sbl1 emmc /dev/block/bootdevice/by-name/sbl1 0
12 /sbl1bak emmc /dev/block/bootdevice/by-name/sbl1bak 0
13 /rpm emmc /dev/block/bootdevice/by-name/rpm 0
14 /rpmbak emmc /dev/block/bootdevice/by-name/rpmbak 0
15 /tz emmc /dev/block/bootdevice/by-name/tz 0
16 /tzbak emmc /dev/block/bootdevice/by-name/tzbak 0
17 /modemst1 emmc /dev/block/bootdevice/by-name/modem_st1 0
18 /modemst2 emmc /dev/block/bootdevice/by-name/modem_st2 0
19 /static_nv_bk emmc /dev/block/bootdevice/by-name/oppostanvbk 0
20 /oppodycnvbk emmc /dev/block/bootdevice/by-name/oppodycnvbk 0
21 /logo emmc /dev/block/bootdevice/by-name/LOGO 0
22 /reserve4 emmc /dev/block/bootdevice/by-name/reserve4 0
23 /dsp emmc /dev/block/bootdevice/by-name/dsp 0
24 /DDR emmc /dev/block/bootdevice/by-name/DDR 0
25 /devcfg emmc /dev/block/bootdevice/by-name/devcfg 0
26 /mdtp emmc /dev/block/bootdevice/by-name/mdtp 0
27 /cmnlib emmc /dev/block/bootdevice/by-name/cmnlib 0
28 /cmnlibbak emmc /dev/block/bootdevice/by-name/cmnlibbak 0
29 /keymaster emmc /dev/block/bootdevice/by-name/keymaster 0
30 /keymasterbak emmc /dev/block/bootdevice/by-name/keymasterbak 0
31 /apdp emmc /dev/block/bootdevice/by-name/apdp 0
32 /devinfo emmc /dev/block/bootdevice/by-name/devinfo 0
33 /persist ext4 /dev/block/bootdevice/by-name/persist 0
34 /opporeserve ext4 /dev/block/bootdevice/by-name/opporeserve2 0
35 /abl emmc /dev/block/bootdevice/by-name/abl 0
36 /ablbak emmc /dev/block/bootdevice/by-name/ablbak 0
37 /xbl emmc /dev/block/bootdevice/by-name/xbl 0
38 /xblbak emmc /dev/block/bootdevice/by-name/xblbak 0
39 /tmp ramdisk ramdisk 0
Details Permission Mount Partition table on Realme 5 Pro
============================================
Code:
/dev/root on / type ext4 (ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1855184k,nr_inodes=463796,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600,ptmxmode=000)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2) sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime) tmpfs on /mnt type tmpfs (rw,seclabel,nosuid,nodev,noexec,relatime,size=1855184k,nr_inodes=463796,mode=755,gid=1000)
/dev/block/dm-1 on /vendor type ext4 (ro,seclabel,relatime,block_validity,discard,delalloc,barrier,user_xattr)
none on /acct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct)
debugfs on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
none on /dev/stune type cgroup (rw,nosuid,nodev,noexec,relatime,schedtune)
none on /config type configfs (rw,nosuid,nodev,noexec,relatime)
none on /dev/cpuctl type cgroup (rw,nosuid,nodev,noexec,relatime,cpu)
none on /dev/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent)
cg2_bpf on /dev/cg2_bpf type cgroup2 (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime) tracefs on /sys/kernel/debug/tracing type tracefs (rw,seclabel,relatime)
/dev/block/sda10 on /cache type ext4 (rw,seclabel,nosuid,nodev,noatime,data=ordered)
/dev/block/sda14 on /data type ext4 (rw,lazytime,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,resgid=1065,errors=panic,data=ordered)
/dev/block/sde5 on /vendor/firmware_mnt type vfat (ro,context=u:object_r:firmware_file:s0,relatime,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/sde8 on /vendor/dsp type ext4 (ro,seclabel,nosuid,nodev,relatime,data=ordered)
/dev/block/sda2 on /mnt/vendor/persist type ext4 (rw,seclabel,nosuid,nodev,noatime,data=ordered)
/dev/block/sde6 on /vendor/bt_firmware type vfat (ro,context=u:object_r:bt_firmware_file:s0,relatime,uid=1002,gid=3002,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/sdf7 on /mnt/vendor/opporeserve type ext4 (rw,seclabel,nosuid,nodev,noatime,data=ordered)
tmpfs on /storage type tmpfs (rw,seclabel,nosuid,nodev,noexec,relatime,size=1855184k,nr_inodes=463796,mode=755,gid=1000)
/dev/block/sdf7 on /data/oppo/log/opporeserve type ext4 (rw,seclabel,nosuid,nodev,noatime,data=ordered)
/dev/block/sdf7 on /data/oppo/log/stamp type ext4 (rw,seclabel,nosuid,nodev,noatime,data=ordered)
none on /dev/freezer type cgroup (rw,relatime,freezer) adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
none on /dev/blkio type cgroup (rw,relatime,blkio)
/data/media on /mnt/runtime/default/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid,default_normal,reserved=200MB)
/data/media on /storage/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid,default_normal,reserved=200MB)
/data/media on /mnt/runtime/read/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=23,derive_gid,default_normal,reserved=200MB)
/data/media on /mnt/runtime/write/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid,default_normal,reserved=200MB)
/dev/block/vold/public:179:1 on /mnt/media_rw/5F4A-151A type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/mnt/media_rw/5F4A-151A on /mnt/runtime/default/5F4A-151A type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,mask=6)
/mnt/media_rw/5F4A-151A on /storage/5F4A-151A type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,mask=6)
/mnt/media_rw/5F4A-151A on /mnt/runtime/read/5F4A-151A type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=18)
/mnt/media_rw/5F4A-151A on /mnt/runtime/write/5F4A-151A type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=18)
Just Hope can Help Team XDA Development
Can I get info about the partition's size, too?
uaevuon said:
Can I get info about the partition's size, too?
Click to expand...
Click to collapse
Nope, need root to get partition size.
Can this help for installing global firmware on Realme Q?
jaydvn said:
Can this help for installing global firmware on Realme Q?
Click to expand...
Click to collapse
No, it can't! You can flash stock rom of realme 5 pro for Q. But you can flash custom rom if 5 pro for Q.