I got my nexus 7 2013 a few weeks ago. It worked great for some time until I decided to flash a kernel that claimed to add support for CIFS windows shares mount. After installing this kernel, when the OS booted, I did not have landscape mode working anymore - only portrait. I decided to do adb full restore to a full backup i made before this step, which seemed to have passed without any errors, but something happened to the recognition of the internal SD memory - applications are not able to use it - I am getting "no external storage" messages when I launch the gallery application and an error when trying to run the google play store - "unfortunetley, google play store has stopped". The device is still starting with only portrait mode.
i then tried to format the device and used TWRP to format everything including the internal memory. After that I reflashed the original rom of google for this device (taken from here https://developers.google.com/android/nexus/images#razorjss15r). The problem is still the same. In TWRP recovery console - I am able to access and push files to and from /sdcard folder with no problems, and see its content with adb shell.
When android loads - cd /sdcard + ls shows that it is empty (even though it does contain files copied to it in recovery console mode) the reason for this is that with ls I can see that "/sdcard" points to "/storage/emulated/legacy" which points to "/mnt/shell/emulated/0" which DOES NOT exist. "/mnt/shell/emulated/" folder exists, but it is empty.
I am unable to use the device - just start the OS (and get the error messages when trying to launch applications). When the OS loads I immediately get the "unfortunetley, google play store has stopped" error without doing anything.
running google earth application when logcat active gives the following output:
--------
E/cutils (10727): Failed to chmod(/mnt/shell/emulated/0, 0): Read-only file system
E/dalvikvm(10727): cannot mountExternalStorage(): Read-only file system
I/ActivityManager( 492): Start proc com.google.earth for activity com.google.earth/.EarthActivity: pid=10727 uid=10024 gids={50024, 3003, 1015, 1028}
D/dalvikvm(10727): No JNI_OnLoad found in /system/lib/libearthmobile.so 0x41dc5158, skipping init
--------
i've attached logcat and dmesg outputs i got.
Any idea how do I solve this? Why are the folder links broken when I am using an original google rom?
I've attached a bug report created using nexus root toolkit 1.78. searching for "failed" word in the log shows the problem happens over and over again as i try to use different applications:
"Failed to mkdir(/mnt/shell/emulated/0): Read-only file system".
i cannot use any application that needs the internal SD storage even though it is mounted to /data and the system reports 25GB available storage as can be seen by searching this log for "FREE SPACE" (df output)
working in "adb shell" as root (after "su"), i cannot write to any of the device's folders - only after executing "mount -o rw,remount /" it becomes possible (and only for the same session of the shell).
It would be very helpful if someone with a working nexus 7 2nd can post he/she's own device's bug report file so I'll be able to compare it to mine and see if i can find any differences. It can be done using the nexus toolkit:
"Launch" -> "Launch Generator" -> "OK" -> "Dump bug report to file" (filter output and alternate buffer log are unchecked).
Is there no one here that has experience with under the hood stuff of android and its filesystem?
Any help/directions will be appreciated.
I have the same problem did you find a solution?
Waledzaki said:
I have the same problem did you find a solution?
Click to expand...
Click to collapse
not yet - we need someone to post his debug info or at least "mount" command output for a working android 4.3+ device. maybe by comparison we'll be able to find what is wrong.
I must say i find the android community is quite disappointing - no one seems to give any directions even though full logs and detailed problem description supplied here.
I'm coming from maemo community (n900 device) which has many way better OS professionals.
liran corleone said:
It would be very helpful if someone with a working nexus 7 2nd can post he/she's own device's bug report file so I'll be able to compare it to mine and see if i can find any differences. It can be done using the nexus toolkit:
"Launch" -> "Launch Generator" -> "OK" -> "Dump bug report to file" (filter output and alternate buffer log are unchecked).
Click to expand...
Click to collapse
I have a new nexus7 (2013) with android 4.4.2 , not unlocked, not rooted. Can i help you with this bug report?
Have you a link to the nexus toolkit?
alligator_asl said:
I have a new nexus7 (2013) with android 4.4.2 , not unlocked, not rooted. Can i help you with this bug report?
Have you a link to the nexus toolkit?
Click to expand...
Click to collapse
you can download it from here: http://www.wugfresh.com/
after starting and choosing your device, press "Launch" button -> "Launch Generator" -> "Dump bug report to file" -> this will create the needed log file.
It would be great if you can post it (the log file) here.
Thanks.
Hello,
I generated this report and looked at him, unfortunately he contains too many personal details such as MAC addresses, SSID's, e-mail addresses, used apps, calendars and many others. I think, I can only post parts here. Can you tell me which parts you need?
alligator_asl said:
Hello,
I generated this report and looked at him, unfortunately he contains too many personal details such as MAC addresses, SSID's, e-mail addresses, used apps, calendars and many others. I think, I can only post parts here. Can you tell me which parts you need?
Click to expand...
Click to collapse
These sections are important (search for these strings in the log file):
KERNEL LOG
SYSTEM LOG
EVENT LOG
LAST KMSG
FILESYSTEMS & FREE SPACE
if there is a problem to publish it here, maybe you can send me on private?
it would be great if you can post these section from a log file which was created in the following way (in order to produce a clean log):
reboot the device, run an application that uses the internal storage (google earth for example) and recreate the log.
Thanks.
liran corleone said:
reboot the device, run an application that uses the internal storage (google earth for example) and recreate the log.
Click to expand...
Click to collapse
I did so, and here are the logs:
alligator_asl said:
I did so, and here are the logs:
Click to expand...
Click to collapse
i already found very interesting differences, although i'm not sure yet how this should be fixed:
in KERNEL LOG (dmesg):
Working device:
<6>[ 6.572631] EXT4-fs (mmcblk0p30): mounted filesystem with ordered data mode. Opts: barrier=1,data=ordered,nomblk_io_submit,errors=panic
<7>[ 6.572784] SELinux: initialized (dev mmcblk0p30, type ext4), uses xattr
<6>[ 6.578033] EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: barrier=1,data=ordered,nodelalloc
<7>[ 6.578155] SELinux: initialized (dev mmcblk0p4, type ext4), uses xattr
Non working device:
<6>[ 6.130340] EXT4-fs (mmcblk0p30): mounted filesystem with ordered data mode. Opts: barrier=1,data=ordered,nomblk_io_submit,errors=panic
<7>[ 6.130462] SELinux: initialized (dev mmcblk0p30, type ext4), uses xattr
<3>[ 6.131042] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem
<3>[ 6.198333] fs_mgr: Cannot mount filesystem on /dev/block/platform/msm_sdcc.1/by-name/persist at /persist
<3>[ 6.198425] init: fs_mgr_mount_all returned an error
"df" on working device:
Filesystem Size Used Free Blksize
/dev 902.9M 128.0K 902.8M 4096
/sys/fs/cgroup 902.9M 12.0K 902.9M 4096
/mnt/asec 902.9M 0.0K 902.9M 4096
/mnt/obb 902.9M 0.0K 902.9M 4096
/system 827.8M 700.9M 126.9M 4096
/cache 551.7M 9.9M 541.8M 4096
/data 26.4G 2.9G 23.6G 4096
/persist 14.5M 4.2M 10.2M 4096
/mnt/shell/emulated 26.4G 2.9G 23.6G 4096
"df" on non working device missing 2 mount points, and found a new one:
Filesystem Size Used Free Blksize
/dev 902.9M 128.0K 902.8M 4096
/sys/fs/cgroup 902.9M 12.0K 902.9M 4096
/mnt/asec 902.9M 0.0K 902.9M 4096
/mnt/obb 902.9M 0.0K 902.9M 4096
/system 827.8M 690.2M 137.5M 4096
/cache 551.7M 13.2M 538.6M 4096
/data 26.4G 337.4M 26.1G 4096
/mnt/secure 902.9M 0.0K 902.9M 4096
May be, this helps a little bit:
Code:
e:\Prog\android-sdk-windows\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ mount
mount
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
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 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/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,nodelalloc,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/ $
alligator_asl said:
May be, this helps a little bit:
Code:
e:\Prog\android-sdk-windows\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ mount
mount
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
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 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/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,nodelalloc,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/ $
Click to expand...
Click to collapse
i suggest you keep the full log and full file structure (list of all files in all folders) - just in case you will get to this situation also.
liran corleone said:
i already found very interesting differences, although i'm not sure yet how this should be fixed:
in KERNEL LOG (dmesg):
Working device:
<6>[ 6.572631] EXT4-fs (mmcblk0p30): mounted filesystem with ordered data mode. Opts: barrier=1,data=ordered,nomblk_io_submit,errors=panic
<7>[ 6.572784] SELinux: initialized (dev mmcblk0p30, type ext4), uses xattr
<6>[ 6.578033] EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: barrier=1,data=ordered,nodelalloc
<7>[ 6.578155] SELinux: initialized (dev mmcblk0p4, type ext4), uses xattr
Non working device:
<6>[ 6.130340] EXT4-fs (mmcblk0p30): mounted filesystem with ordered data mode. Opts: barrier=1,data=ordered,nomblk_io_submit,errors=panic
<7>[ 6.130462] SELinux: initialized (dev mmcblk0p30, type ext4), uses xattr
<3>[ 6.131042] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem
<3>[ 6.198333] fs_mgr: Cannot mount filesystem on /dev/block/platform/msm_sdcc.1/by-name/persist at /persist
<3>[ 6.198425] init: fs_mgr_mount_all returned an error
"df" on working device:
Filesystem Size Used Free Blksize
/dev 902.9M 128.0K 902.8M 4096
/sys/fs/cgroup 902.9M 12.0K 902.9M 4096
/mnt/asec 902.9M 0.0K 902.9M 4096
/mnt/obb 902.9M 0.0K 902.9M 4096
/system 827.8M 700.9M 126.9M 4096
/cache 551.7M 9.9M 541.8M 4096
/data 26.4G 2.9G 23.6G 4096
/persist 14.5M 4.2M 10.2M 4096
/mnt/shell/emulated 26.4G 2.9G 23.6G 4096
"df" on non working device missing 2 mount points, and found a new one:
Filesystem Size Used Free Blksize
/dev 902.9M 128.0K 902.8M 4096
/sys/fs/cgroup 902.9M 12.0K 902.9M 4096
/mnt/asec 902.9M 0.0K 902.9M 4096
/mnt/obb 902.9M 0.0K 902.9M 4096
/system 827.8M 690.2M 137.5M 4096
/cache 551.7M 13.2M 538.6M 4096
/data 26.4G 337.4M 26.1G 4096
/mnt/secure 902.9M 0.0K 902.9M 4096
Click to expand...
Click to collapse
did u find any solution or there is non?!
Waledzaki said:
did u find any solution or there is non?!
Click to expand...
Click to collapse
didn't find one yet - i am currently using it without the SD storage - installing the apks manually (the ones that does not require it).
Still nothing ?
liran corleone said:
didn't find one yet - i am currently using it without the SD storage - installing the apks manually (the ones that does not require it).
Click to expand...
Click to collapse
Still no solutions ? thanks in advance
have to bring this from the dead, i made a new post about this exact same issue with no response, you are obviously far more knowledgeable on this subject so i hope a dev sees this or someone who knows a fix can chime in.
have you found a fix yet though?
Got this one fixed.
Steps:
Root your device
Boot into android and enable USB debugging
Connect device to PC
Start up "adb shell", then type in "su"
A supersu prompt would pop up on the device, agree to give adb shell root permissions.
In adb shell execute "make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist"
In adb shell type "exit" twice to quit.
Execute "adb reboot".
Fixed.
Related
Here's the deal, I flashed a clockwork port for the kindle fire that I made. It was 100% useless as of now because of the one hardware button that we have to work with. I sent Koush a message on twitter asking if there is a possibility to have a long press and quick/short press differentiate between scrolling down and actually selecting the item on the menu but he hasn't gotten back to me yet but I'm sure he's working on it
Very good news! Hopefully something comes of this. I want to look at the code for TWRP 2.0 and see if that can be ported over to the fire, its touch control.
Sent from my Kindle Fire
you got partition table for fire yet ? i am looking for boot partition
cat /proc/mounts....
Code:
# cat /proc/mounts
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
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/splash /dropbox ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/vold/179:12 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:12 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
#
cat /proc/partitions
Code:
# cat /proc/partitions
major minor #blocks name
179 0 7553024 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 196608 mmcblk0p4
179 5 16384 mmcblk0p5
179 6 65536 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 524288 mmcblk0p9
179 10 1164288 mmcblk0p10
179 11 262144 mmcblk0p11
179 12 5254144 mmcblk0p12
#
cat /proc/filesystems
Code:
# cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev devtmpfs
nodev binfmt_misc
nodev debugfs
nodev sockfs
nodev usbfs
nodev pipefs
nodev anon_inodefs
nodev rpc_pipefs
nodev devpts
ext3
ext2
ext4
nodev ramfs
vfat
msdos
nodev nfs
nodev nfs4
#
ls /dev/block/platform/mmci-omap-hs.1/by-name
Code:
# ls /dev/block/platform/mmci-omap-hs.1/by-name
media
cache
userdata
system
splash
boot
backup
recovery
dfs
dkernel
bootloader
xloader
#
Probably doesn't help. But I guess it was worth a shot. I'm not sure what the partitions are mapped to. :/
using root explorer i can tell that
/dev/block/platform/mmci-omap-hs.1/by-name/boot
is symlinked to
/dev/block/platform/mmci-omap-hs.1/mmcblk0p7
so if you wanted to mount boot
you could type
mount -o rw,remount /boot
i believe..
well i did a dd if= from the phone to the sdcard, but now we can just grab the boot.img from the update on amazon's site
Can you post pictures? This is the main reason I am not trading my fire for a nook.
http://i.imgur.com/9zWTk.jpg just gettings rid of those error messages now. had the wrong filesystem for /cache
I love you.screw the nook.
Wow JackpotCalvin! How were you able to flash the clockwork recovery? Also are you still able to load your KF as normal?
really nice work
another way to mount things as is done in the init.rc:
mount [email protected]/system system
so for rw..."mount -o rw,remount -t ext4 [email protected] /system"
anyway mounts are as follows:
backup -> mmcblk0p6
boot -> mmcblk0p7
bootloader ->mmcblk0p2
cache -> mmcblk0p11
dfs -> mmcblk0p4
dkernel -> mmcblk0p3
media -> mmcblk0p12
recovery -> mmcblk0p5
splash -> mmcblk0p8
system -> mmcblk0p9
userdata -> mmcblk0p10
xloader -> mmcblk0p1
well we're at a bit of a road block as of right now as we have no way to navigate through the menu, we can just press OK and reboot the kindle. also, pressing reboot now does not start the device normally, it just reboots into clockwork. i'm looking for the flag that the OS puts in /cache or /data to trigger a recovery reboot because pressing reboot now does not remove that flag so it will continue to reboot into clockwork unless you do a little hackery to put the stock recovery back on it and then reboot it into the stock recovery and make it fail the signature verification this fluke update.zip i made. we need to find a way to make a fail safe to reboot into recovery as well in case when we start roming, something goes wrong
Do you think something like this might work?
https://market.android.com/details?id=com.koushikdutta.rommanager&hl=en
JackpotClavin said:
when we start roming,
Click to expand...
Click to collapse
Emphasis mine. I can't wait. Great work so far, this seems to be going a lot faster than I imagined at first. I wish I had the programming chops to become a dev, instead i just look on from the sidelines, and maybe monetarily support projects when and where I can.
Awesome work guys. I've got the Nook Tablet but thought I'd pop over to see how it's going. Again, awesome work.
Sent from my Nook Tablet using Tapatalk
littleemp said:
Do you think something like this might work?
https://market.android.com/details?id=com.koushikdutta.rommanager&hl=en
Click to expand...
Click to collapse
The official clockword mod does not support the fire yet... if that's what you're asking. That is what OP is trying to do.
JackpotClavin said:
Here's the deal, I flashed a clockwork port for the kindle fire that I made. It was 100% useless as of now because of the one hardware button that we have to work with. I sent Koush a message on twitter asking if there is a possibility to have a long press and quick/short press differentiate between scrolling down and actually selecting the item on the menu but he hasn't gotten back to me yet but I'm sure he's working on it
Click to expand...
Click to collapse
How did you boot into recovery?
well i've just made a clockwork backup of my current system. i believe ive found a way that we can manage to "navigate" through the menu, even though it's a real pain in the ass to do
JackpotClavin said:
well i've just made a clockwork backup of my current system. i believe ive found a way that we can manage to "navigate" through the menu, even though it's a real pain in the ass to do
Click to expand...
Click to collapse
Sounds like we may have to be connected to our PC to run the commands...??
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
In the past I've done this from the recovery shell. But TWRP 3.0.0.1 does not offer this option under advanced wipe ... From the adb shell while booted into Pure Nexus i see a make_f2fs binary ... but have never attempted to format partitions from the booted system ...
Code:
1|roo[email protected]:/ # make_f2fs
F2FS-tools: mkfs.f2fs Ver: 1.4.0 (2014-10-18)
Error: Device not specified
Usage: mkfs.f2fs [options] device [sectors]
[options]:
-a heap-based allocation [default:1]
-d debug level [default:0]
-e [extension list] e.g. "mp3,gif,mov"
-l label
-o overprovision ratio [default:5]
-s # of segments per section [default:1]
-z # of sections per zone [default:1]
-t 0: nodiscard, 1: discard [default:1]
sectors: number of sectors. [default: determined by device size]
Code:
1|[email protected]:/ # mount
rootfs / rootfs ro,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=919280k,nr_inodes=229820,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /dev/cpuset cgroup rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent 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
/sys/kernel/debug /sys/kernel/debug debugfs rw,seclabel,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=919280k,nr_inodes=229820,mode=750,gid=1000 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,size=919280k,nr_inodes=229820,mode=755,gid=1000 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/platform/soc.0/f9824900.sdhci/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/soc.0/f9824900.sdhci/by-name/vendor /vendor ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/soc.0/f9824900.sdhci/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/platform/soc.0/f9824900.sdhci/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/platform/soc.0/f9824900.sdhci/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,nodelalloc,errors=panic,data=ordered 0 0
/dev/block/platform/soc.0/f9824900.sdhci/by-name/modem /firmware vfat ro,context=u:object_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
tmpfs /storage tmpfs rw,seclabel,relatime,size=919280k,nr_inodes=229820,mode=755,gid=1000 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
http://4pda.ru/forum/dl/post/7694971/recovery.img
luis666 said:
http://4pda.ru/forum/dl/post/7694971/recovery.img
Click to expand...
Click to collapse
Hey, thanks - but I'm getting a 404 at that link. Is that a version of TWRP or another recovery that will let me use F2FS?
+1
Use jolla kernel's recovery, flash it. It has the option to change the file system to f2fs.
RonnellTapawan said:
Use jolla kernel's recovery, flash it. It has the option to change the file system to f2fs.
Click to expand...
Click to collapse
After that, can i flash FLASH-kernel(with f2fs support) and still have f2fs?
axiel7 said:
After that, can i flash FLASH-kernel(with f2fs support) and still have f2fs?
Click to expand...
Click to collapse
after you change the file system to f2fs, it will be retained unless you change it again to ext4 or format it again (not sure about this one). in short, yes, you can flash 'flash' kernel and use any rom you want. also, i advice not to use other twrp anymore because jolla's twrp is much better.
Hi everyone,
as I said in the title, android doesn't see the internal storage.
I installed LineageOS 17.1 using GSI file by Andy Yan: lineage-17.1-20200511-UNOFFICIAL-treble_arm64_avN.img.x
The ROM works perfectly (except for long boot time).
So the phone was factory reset / wipe cache and therefore is empty. But android shows only 700Mo available... I hope you can help me on this one.
More informations:
- phone: Ulefone Armor 3T.
- 64Gb internal memory.
- not rooted.
- no access to recovery whatsoever (another problem...).
I am a new user so I can't link to outside links for screenshots but I can give you some information in text format:
1. The result of the "adb shell dumpsys mount" command:
Disks:
Volumes:
VolumeInfo{emulated}:
type=EMULATED diskId=null partGuid= mountFlags=PRIMARY|VISIBLE mountUserId=-10000 state=MOUNTED
fsType=null fsUuid=null fsLabel=null
path=/storage/emulated internalPath=/data/media
Records:
Primary storage UUID: null
Internal storage (null) total size: 8000000000 (8388608000000000 MiB)
Local unlocked users: [0]
System unlocked users: [0]
Isolated storage, local feature flag: 0
Isolated storage, remote feature flag: 0
Isolated storage, resolved: true
mObbMounts:
mObbPathToStateMap:
Last maintenance: 2020-06-01 15:13:49
Click to expand...
Click to collapse
2. a screenshot of the DiskInfo android app (ask me and I'll send you the image link via pm):
It shows that "/storage", "/storage/self", "/dev", "/mnt", "/storage", "/apex" are TMPFS mount points with "0 bytes used" or "unknown size".
3. 'Storage' menu in android settings:
it shows everything at 0 bytes except for 'System' at 7.9/8Go used.
4. Result of the "adb shell dumpsys devicestoragemonitor":
Known volumes:
Default:
level=NORMAL lastUsableBytes=69894144
mSeq=1 mForceState=UNKNOWN
Click to expand...
Click to collapse
5. Result of "adb shell dumpsys diskstats"
Latency: 1ms [512B Data Write]
Recent Disk Write Speed (kB/s) = 5176
Data-Free: 105016K / 789904K total = 13% free
Cache-Free: 105016K / 789904K total = 13% free
System-Free: 1839044K / 3666816K total = 50% free
Click to expand...
Click to collapse
6. Result of "adb shell cat /proc/mounts"
rootfs / rootfs ro,seclabel 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,gid=3009,hidepid=2 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
/dev/block/platform/bootdevice/by-name/system /system ext4 ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr 0 0
/dev/block/dm-0 /vendor ext4 ro,seclabel,relatime,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
debugfs /sys/kernel/debug debugfs rw,seclabel,relatime 0 0
none /dev/stune cgroup rw,relatime,schedtune 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /config configfs rw,relatime 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /dev/cpuset cgroup rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
tracefs /sys/kernel/debug/tracing tracefs rw,seclabel,relatime 0 0
tmpfs /apex tmpfs rw,seclabel,relatime,mode=755 0 0
/dev/block/platform/bootdevice/by-name/system /apex/[email protected] ext4 ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr 0 0
/dev/block/platform/bootdevice/by-name/system /apex/com.android.runtime ext4 ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr 0 0
/dev/block/platform/bootdevice/by-name/system /apex/[email protected] ext4 ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr 0 0
/dev/block/platform/bootdevice/by-name/system /apex/com.android.tzdata ext4 ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr 0 0
/dev/block/platform/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/bootdevice/by-name/protect1 /vendor/protect_f ext4 rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/dev/block/platform/bootdevice/by-name/protect2 /vendor/protect_s ext4 rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/dev/block/platform/bootdevice/by-name/nvdata /vendor/nvdata ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/bootdevice/by-name/nvcfg /vendor/nvcfg ext4 rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
none /system/lib64/vndk-26/libsoftkeymasterdevice.so tmpfs rw,seclabel,nodev,relatime,mode=755 0 0
none /vendor/bin/teed tmpfs rw,seclabel,nodev,relatime,mode=755 0 0
none /system/lib/vndk-26/libsoftkeymasterdevice.so tmpfs rw,seclabel,nodev,relatime,mode=755 0 0
none /system/lib/vndk-27/libsoftkeymasterdevice.so tmpfs rw,seclabel,nodev,relatime,mode=755 0 0
none /system/lib64/vndk-27/libsoftkeymasterdevice.so tmpfs rw,seclabel,nodev,relatime,mode=755 0 0
none /vendor/lib/libmtk-ril.so tmpfs rw,seclabel,nodev,relatime,mode=755 0 0
none /vendor/lib64/libmtk-ril.so tmpfs rw,seclabel,nodev,relatime,mode=755 0 0
/dev/block/platform/bootdevice/by-name/system /vendor/overlay/SysuiDarkTheme/SysuiDarkThemeOverlay.apk ext4 ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr 0 0
/dev/block/platform/bootdevice/by-name/system /vendor/etc/usb_audio_policy_configuration.xml ext4 ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr 0 0
/dev/block/platform/bootdevice/by-name/system /apex/[email protected] ext4 ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr 0 0
/dev/block/platform/bootdevice/by-name/system /apex/com.android.conscrypt ext4 ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr 0 0
/dev/block/platform/bootdevice/by-name/system /apex/[email protected] ext4 ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr 0 0
/dev/block/platform/bootdevice/by-name/system /apex/com.android.media.swcodec ext4 ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr 0 0
/dev/block/platform/bootdevice/by-name/system /apex/[email protected] ext4 ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr 0 0
/dev/block/platform/bootdevice/by-name/system /apex/com.android.media ext4 ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr 0 0
/dev/block/platform/bootdevice/by-name/system /apex/[email protected] ext4 ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr 0 0
/dev/block/platform/bootdevice/by-name/system /apex/com.android.resolv ext4 ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr 0 0
/dev/block/dm-1 /data ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,resuid=10010,errors=panic,data=ordered 0 0
/data/media /mnt/runtime/default/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid 0 0
/data/media /storage/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid 0 0
/data/media /mnt/runtime/read/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=23,derive_gid 0 0
/data/media /mnt/runtime/write/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid 0 0
/data/media /mnt/runtime/full/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid 0 0
Click to expand...
Click to collapse
7. Result of "adb shell mount"
rootfs on / type rootfs (ro,seclabel)
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,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
/dev/block/mmcblk0p30 on /system type ext4 (ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr)
/dev/block/dm-0 on /vendor type ext4 (ro,seclabel,relatime,data=ordered)
none on /acct type cgroup (rw,relatime,cpuacct)
debugfs on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
none on /dev/stune type cgroup (rw,relatime,schedtune)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)
none on /config type configfs (rw,relatime)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
none on /dev/cpuset type cgroup (rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent)
pstore on /sys/fs/pstore type pstore (rw,seclabel,relatime)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,seclabel,relatime)
tmpfs on /apex type tmpfs (rw,seclabel,relatime,mode=755)
/dev/block/mmcblk0p30 on /apex/[email protected] type ext4 (ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr)
/dev/block/mmcblk0p30 on /apex/com.android.runtime type ext4 (ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr)
/dev/block/mmcblk0p30 on /apex/[email protected] type ext4 (ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr)
/dev/block/mmcblk0p30 on /apex/com.android.tzdata type ext4 (ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr)
/dev/block/mmcblk0p31 on /cache type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered)
/dev/block/mmcblk0p9 on /vendor/protect_f type ext4 (rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered)
/dev/block/mmcblk0p10 on /vendor/protect_s type ext4 (rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered)
/dev/block/mmcblk0p7 on /vendor/nvdata type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered)
/dev/block/mmcblk0p6 on /vendor/nvcfg type ext4 (rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
none on /system/lib64/vndk-26/libsoftkeymasterdevice.so type tmpfs (rw,seclabel,nodev,relatime,mode=755)
none on /vendor/bin/teed type tmpfs (rw,seclabel,nodev,relatime,mode=755)
none on /system/lib/vndk-26/libsoftkeymasterdevice.so type tmpfs (rw,seclabel,nodev,relatime,mode=755)
none on /system/lib/vndk-27/libsoftkeymasterdevice.so type tmpfs (rw,seclabel,nodev,relatime,mode=755)
none on /system/lib64/vndk-27/libsoftkeymasterdevice.so type tmpfs (rw,seclabel,nodev,relatime,mode=755)
none on /vendor/lib/libmtk-ril.so type tmpfs (rw,seclabel,nodev,relatime,mode=755)
none on /vendor/lib64/libmtk-ril.so type tmpfs (rw,seclabel,nodev,relatime,mode=755)
/dev/block/mmcblk0p30 on /vendor/overlay/SysuiDarkTheme/SysuiDarkThemeOverlay.apk type ext4 (ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr)
/dev/block/mmcblk0p30 on /vendor/etc/usb_audio_policy_configuration.xml type ext4 (ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr)
/dev/block/mmcblk0p30 on /apex/[email protected] type ext4 (ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr)
/dev/block/mmcblk0p30 on /apex/com.android.conscrypt type ext4 (ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr)
/dev/block/mmcblk0p30 on /apex/com.android.media.swcodec[email protected] type ext4 (ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr)
/dev/block/mmcblk0p30 on /apex/com.android.media.swcodec type ext4 (ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr)
/dev/block/mmcblk0p30 on /apex/[email protected] type ext4 (ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr)
/dev/block/mmcblk0p30 on /apex/com.android.media type ext4 (ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr)
/dev/block/mmcblk0p30 on /apex/[email protected] type ext4 (ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr)
/dev/block/mmcblk0p30 on /apex/com.android.resolv type ext4 (ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr)
/dev/block/dm-1 on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,resuid=10010,errors=panic,data=ordered)
/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)
/data/media on /storage/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid)
/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)
/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)
/data/media on /mnt/runtime/full/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid)
Click to expand...
Click to collapse
8. More info on disks:
* Partitions (source: BYNAME)
* /dev/block/mmcblk0p24: (boot) (32 MiB)
* /dev/block/mmcblk0p1: (boot_para) (1 MiB)
* /dev/block/mmcblk0p31: cache (432 MiB)
* /dev/block/mmcblk0p4: (expdb) (20 MiB)
* /dev/block/mmcblk0p34: (flashinfo) (16 MiB)
* /dev/block/mmcblk0p5: (frp) (1 MiB)
* /dev/block/mmcblk0p19: (gz1) (16 MiB)
* /dev/block/mmcblk0p20: (gz2) (16 MiB)
* /dev/block/mmcblk0p22: (lk) (1 MiB)
* /dev/block/mmcblk0p23: (lk2) (1 MiB)
* /dev/block/mmcblk0p25: (logo) (8 MiB)
* /dev/block/mmcblk0p15: (md1dsp) (16 MiB)
* /dev/block/mmcblk0p14: (md1img) (64 MiB)
* /dev/block/mmcblk0p8: (metadata) (32 MiB)
* /dev/block/mmcblk0p6: vendor/nvcfg (32 MiB)
* /dev/block/mmcblk0p7: vendor/nvdata (64 MiB)
* /dev/block/mmcblk0p21: (nvram) (64 MiB)
* /dev/block/mmcblk0p26: (odmdtbo) (16 MiB)
* /dev/block/mmcblk0p3: (para) (0 MiB)
* /dev/block/mmcblk0boot0: (preloader_a) (4 MiB)
* /dev/block/mmcblk0boot1: (preloader_b) (4 MiB)
* /dev/block/mmcblk0p13: (proinfo) (3 MiB)
* /dev/block/mmcblk0p9: vendor/protect_f (8 MiB)
* /dev/block/mmcblk0p10: vendor/protect_s (9 MiB)
* /dev/block/mmcblk0p2: (recovery) (32 MiB)
* /dev/block/mmcblk0p33: (sdrpmb) (24 MiB)
* /dev/block/mmcblk0p12: (sec1) (2 MiB)
* /dev/block/mmcblk0p11: (seccfg) (8 MiB)
* /dev/block/mmcblk0p16: (spmfw) (1 MiB)
* /dev/block/mmcblk0p17: (sspm_1) (1 MiB)
* /dev/block/mmcblk0p18: (sspm_2) (1 MiB)
* /dev/block/mmcblk0p30: system (3,584 MiB)
* /dev/block/mmcblk0p27: (tee1) (5 MiB)
* /dev/block/mmcblk0p28: (tee2) (9 MiB)
* /dev/block/mmcblk0p32: (userdata) (54,463 MiB)
* /dev/block/mmcblk0p29: (vendor) (656 MiB)
Click to expand...
Click to collapse