Good morning, lovely HTC ONE owners!
Yesterday, I manually deleted a folder from my HTC ONE containing an important file. I have tried finding a software or app to restore that folder, but it seems that none of them can detect the symlinked pseudo SD card of the HTC ONE.
Is there any chance to get back my data? In the future, I will use the app 'Dumpster', which only throws files into a special trash bin where files can be restored if necessary...
SecUpwN said:
but it seems that none of them can detect the symlinked pseudo SD card of the HTC ONE.
Click to expand...
Click to collapse
which filesystem?
We need to know which file you deleted
tryin said:
which filesystem?
Click to expand...
Click to collapse
Thanks for helping, guys. The HTC ONE doesn't have an SD card, thus only offering 32 GB of internal memory. I guess that part has no filesystem, correct me if I'm wrong.
matt95 said:
We need to know which file you deleted
Click to expand...
Click to collapse
A file inside a folder with the extension *.bck - it was a settings file created by another app. It is important to me because it contains phone numbers I have not written down. What to do?
I don't think you'll get it back man....
matt95 said:
I don't think you'll get it back man....
Click to expand...
Click to collapse
Darn. Maybe it's gods will. For other peeps reading this: Install DUMPSTER to avoid deletion without being able to recover files. This recycle bin will keep your deleted files for a set amount of time and delete them for good afterwards. If I had only known this app before, this wouldn't have happened.
SecUpwN said:
...32 GB of internal memory. I guess that part has no filesystem, correct me if I'm wrong.
Click to expand...
Click to collapse
No filesystem..!? Mmm it sound a bit strange... .
There are some nice tools for data carving, take a look at Foremost and Scalpel. Quite easy to use, could recover your files...
tryin said:
No filesystem..!? Mmm it sound a bit strange... .
There are some nice tools for data carving, take a look at Foremost and Scalpel. Quite easy to use, could recover your files...
Click to expand...
Click to collapse
I got an HTC with 32 GB internal storage, you tell me which file system this thing has, please. ^^ You receive a big THUMB UP for your recommendations, are there recommendable APPS for recovery?
SecUpwN said:
I got an HTC with 32 GB internal storage, you tell me which file system this thing has, please. ^^ You receive a big THUMB UP for your recommendations, are there recommendable APPS for recovery?
Click to expand...
Click to collapse
:/ $ 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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /dev/timer_group cgroup rw,relatime,timer_slack 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,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
/dev/block/dm-0 /mnt/asec/com.nuance.swype.dtc-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/stericson.busybox.donate-2 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-2 /mnt/asec/com.gameloft.android.ANMP.GloftA8HM-2 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-3 /mnt/asec/com.eclipsim.gpstoolbox.pro-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-4 /mnt/asec/com.koushikdutta.backup.license-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-5 /mnt/asec/com.eightyeightgames.tenmillion-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p35 /system ext4 ro,seclabel,noatime,nobarrier 0 0
/dev/block/mmcblk0p37 /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc 0 0
tmpfs /data/qcks tmpfs rw,seclabel,relatime,size=20480k,mode=750,gid=1000 0 0
tmpfs /data/efs tmpfs rw,seclabel,relatime,size=20480k,mode=750,gid=1000 0 0
tmpfs /data/secure/data tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/block/mmcblk0p36 /cache ext4 rw,seclabel,nosuid,nodev,noatime,nobarrier 0 0
/dev/block/mmcblk0p22 /devlog ext4 rw,seclabel,nosuid,nodev,noatime,nobarrier,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p31 /firmware/mdm vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p16 /firmware/q6 vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
@BenPope, what's that supposed to be?
SecUpwN said:
@BenPope, what's that supposed to be?
Click to expand...
Click to collapse
That would be the list of filesystems, their mount points and parameters on my phone.
As you can see, it's not as simple as "a filesystem".
It is possible, try this guide: htc phone photo file recovery
hope this helps.
jackthomas251 said:
From phone it's much more complicated.
Click to expand...
Click to collapse
But not impossible?
Re: File Recovery after Deletion
I have also done this kind of mistake previously then my friend told me about Remo Android Recovery software and seriously it worked for me as a miracle. I got back all my accidentally deleted photos. You can give a try to this to recover your deleted folder. Hope you will get success.
This topic is like more than a month old, I guess there's nothing to rescue anymore. But thanks for the hints, everyone should install DUMPSTER beforehand.
Even worse.... I deleted storage/emulated/0 folder on my htc one
Ok. So check this ish..... I was tryna free up room on my htc one, so i went into file manager, was lookin for unnecessary stuff to delete, and thats when i notice.. Inside the emulated folder are 2 folders, one named "0" and one named "legacy" so after going back and forth one to the other... I realized that the same exact files and folders as the other, so my retarded asss deleted one thinking it was a whole duplicated folder. Ok, yeah, i messed that one up bad. How could i be so stupid? So i looked up some claims of some solutions, downloaded the pc software they swore would recover everything. Nada... Zip. Zero... What can i do? The htc one is no removable sd card or battery and my phone is not rooted.... Please get back at me on this... Im beginning to think,an htc csr or one of the smartest phone dudes on this forum will know how or what to do... :crying::crying::angel:
Oh yeah i forgot....
I think i should add that when i deleted the 0 folder, it wiped the legacy one as if it were its mirror or something
datbitch said:
I think i should add that when i deleted the 0 folder, it wiped the legacy one as if it were its mirror or something
Click to expand...
Click to collapse
Sorry pal, no chance to recover anything. If you continued to use your phone after erasing all of that, it has been overwritten multiple times already. To make sure such thing does not happen again, install ES File Explorer and enable the RECYCLE BIN in the options - thus, you can recover deleted files easily. And for cleaning your device, always use SD Maid.
Related
when i go to the shell of my devices, i put mount; and show me this:
rootfs / rootfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
/dev/block/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,noatime,vfat,llw,check=no,gid/uid/r
wx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,noatime,vfat,llw,check=no,gid/uid/rw
x,iocharset=utf8 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexe
c,noatime,nodiratime,uid=1000,gid=1015,fmask=0002, dmask=0002,allow_utime=0020,co
depage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noati
me,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0 002,allow_utime=0020,codepage=
cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000
0 0
what is mi internal and external memory?
thank you for you answers!!!
damn thats confusing lol
what exactly are you looking for ?? What do you want to know about your internal / external memory
im a little confused
Second column is usually the mountpoint, so, your external SD card is most likely:
Code:
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexe...
so, it's mounted at /mnt/sdcard/external_sd, and the device file is /dev/block/vold/179:9
Interestingly it's also mounted as /mnt/secure/asec
Not sure about the internal one... not finding anything that sounds right :O
i have the two memorys bricked, internal and external, and when i run the command try to find /dev/block/mmcblk0 to execute the parted /dev/block/mmcblk0 , no exist...
i find the external sd in /dev/block/vold/179:9, but i could find the internal memory! to fixit
blubxd said:
Second column is usually the mountpoint, so, your external SD card is most likely:
Code:
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexe...
so, it's mounted at /mnt/sdcard/external_sd, and the device file is /dev/block/vold/179:9
Interestingly it's also mounted as /mnt/secure/asec
Not sure about the internal one... not finding anything that sounds right :O
Click to expand...
Click to collapse
okey the external is /dev/block/vold/179:9
but the internal?!
Can you help mw please??? I send this mesg from my i9000 but i cant use the sd internal and external. Any solution to this?
i m going to show you my mount :
Code:
# mount
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
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
/dev/stl14 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/stl13 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioch
arset=utf8 0 0
/dev/stl12 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=u
tf8 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=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:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.speedsoftware.rootexplorer-1 vfat ro,dirsync,nosui
d,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859
-1,shortname=mixed,utf8,errors=remount-ro 0 0
#
i try to recover my efs partitions with odin but nothing to work ,
i transform my backup stl5.rfs > efs.rfs > efs.tar
for using with odin : make a error invalid binary model
so i don t know how to repair this issue
thank you to help me !!!!
There's no way to restore the efs to this device
This was sent from a Galaxy Ace. Problem?
so how i can repair that ?
just with box?
You cannot repair the efs partition
Sent from my GT-S5830 using xda premium
i dont think is not posible to repair this issue ...
if i have one backup ? like stl5.rfs
i try with terminal but no working ...
may be just only with box like z3x i can to repair ...
or someone can to tell me how to recover like 000000 imei ?
thank you
celica7 said:
i dont think is not posible to repair this issue ...
if i have one backup ? like stl5.rfs
i try with terminal but no working ...
may be just only with box like z3x i can to repair ...
or someone can to tell me how to recover like 000000 imei ?
thank you
Click to expand...
Click to collapse
The Galaxy Ace has a closed up efs partition that until the best of devs do not know how to recover . It's useless to ask , just send it for repair .
This was sent from a Galaxy Ace. Problem?
Ok, there seems to be very little information regarding rooting this particular model. I am infinitely irked by the stupid Samsung copy/paste bug with the only options to fix are wipe(which I did once and the bug returned), root or return/buy new device.
Wipe I did once. Bug returned. Return? Ugh...that is a severe PITA to do here (went through it once with a bad GT 7"). Rooting is the next...err...'easiest' option. The problem is, there is little information on XDA regarding this particular model. I saw one thread that started but the user never followed up with giving out his partitions info. So here is mine and hopefully some kind soul will help me root this (f)sucker and all will be well and right with the world again. I'm not really looking for extra features(althoughthey would be a nice perk), I just want to fix this copy/paste issue (and maybe the stupid sporadic switch from wifi-to-4G without requiring a reboot).
Partition info:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=111 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
tmpfs /mnt/usb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p24 /system ext4 ro,relatime,user_xattr,acl,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p28 /data ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p25 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p27 /preload ext4 ro,relatime,user_xattr,acl,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p21 /efs ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /tombstones ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p13 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/mmcblk0p17 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
Please let me know if there is any other info needed.
DragonDon said:
Ok, there seems to be very little information regarding rooting this particular model. I am infinitely irked by the stupid Samsung copy/paste bug with the only options to fix are wipe(which I did once and the bug returned), root or return/buy new device.
Wipe I did once. Bug returned. Return? Ugh...that is a severe PITA to do here (went through it once with a bad GT 7"). Rooting is the next...err...'easiest' option. The problem is, there is little information on XDA regarding this particular model. I saw one thread that started but the user never followed up with giving out his partitions info. So here is mine and hopefully some kind soul will help me root this (f)sucker and all will be well and right with the world again. I'm not really looking for extra features(althoughthey would be a nice perk), I just want to fix this copy/paste issue (and maybe the stupid sporadic switch from wifi-to-4G without requiring a reboot).
Partition info:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=111 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
tmpfs /mnt/usb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p24 /system ext4 ro,relatime,user_xattr,acl,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p28 /data ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p25 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p27 /preload ext4 ro,relatime,user_xattr,acl,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p21 /efs ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /tombstones ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p13 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/mmcblk0p17 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
Please let me know if there is any other info needed.
Click to expand...
Click to collapse
im not sure if this is going to help you but http://forum.xda-developers.com/showthread.php?t=2679066
Thanks Quantra! That just may come in handy.
Well as the title says, while installing twrp I erased cache. Now recovery loops, so how do I rebuild my cache? Does anyone know? I'm rooted, S-off, running stock KK up to date.
godzilla61 said:
Well as the title says, while installing twrp I erased cache. Now recovery loops, so how do I rebuild my cache? Does anyone know? I'm rooted, S-off, running stock KK up to date.
Click to expand...
Click to collapse
Reinstall twrp?
Sent from my lunar powered Inverted ViperONE using Tapatalk 2
That was the first thing I tried, no-joy!
godzilla61 said:
That was the first thing I tried, no-joy!
Click to expand...
Click to collapse
Re flash the stock kitkat update. Clearing your cache shouldn't have broke recovery or the rom. You either wiped something you shouldn't have and didn't tell us or somethings broken with your copy of TWRP
Kraizk said:
Re flash the stock kitkat update. Clearing your cache shouldn't have broke recovery or the rom. You either wiped something you shouldn't have and didn't tell us or somethings broken with your copy of TWRP
Click to expand...
Click to collapse
Some folks execute a "fastboot erase cache" after flashing a recovery. Do not do that! Instead, either "fastboot format cache" or leave it alone. The fastboot erase cache command just blows the file system away and leaves you with an unmountable /cache partition until it's formatted (wipe will do that if you end up with errors about 'cannot mount /cache').
Click to expand...
Click to collapse
The second quote is from the dev, now on to my question, how do I rebuild my cache partition? There has to be a way without loosing everything....
godzilla61 said:
The second quote is from the dev, now on to my question, how do I rebuild my cache partition? There has to be a way without loosing everything....
Click to expand...
Click to collapse
rebuild your cache partition? or your cache filesystem? two totally different things.
if your disk is wrecked (partitions no longer valid) you're likely into RUU.
If your disk is fine (partitions are there, just no file system), TWRP should boot fine, it'll just piss and moan about /cache not being there. If it keeps restarting to the curtain (the TWRP graphic while booting) no big deal -- adb should still be up. If it does come up, you can 'wipe cache' and it'll rebuild the file system for you. Either that or use fastboot to format it.
Either way -- if you actually placed interesting stuff on /cache (why would you do that?), it's gone. The cache partition is 99% useless to users, so it would surprise me if you put stuff there.
Here's what I'd do:
1) Boot TWRP (get my 2.7.1.1 version, fastboot flash it, start it up);
2) plug the phone into usb:
3) adb shell
4) mount
copy/paste what that last command says and let's see what's really up. If TWRP won't boot, you have bigger problems than you lead us to believe.
Ok, more info: phone works. no recovery it just keeps showing the curtain over and over...... So now ADB....can't do a thing with it. Can't fastboot flash anything.....error: cannot load 'openrecovery-m7wls-2.7.1.1-06-05-2014' so what now?
[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
/sys/kernel/debug /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
none /dev/timer_group cgroup rw,relatime,timer_slack 0 0
/dev/block/mmcblk0p37 /system ext4 ro,seclabel,noatime,data=ordered 0 0
/dev/block/mmcblk0p39 /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto
_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p38 /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered
0 0
/dev/block/mmcblk0p22 /devlog ext4 rw,seclabel,nosuid,nodev,noatime 0 0
/dev/block/mmcblk0p30 /carrier ext4 rw,seclabel,nosuid,nodev,noatime,grpid,data=
ordered 0 0
/dev/block/mmcblk0p33 /firmware/mdm vfat ro,relatime,fmask=0000,dmask=0000,allow
_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro
0 0
tmpfs /data/qcks tmpfs rw,seclabel,relatime,size=20480k,mode=750,gid=1000 0 0
tmpfs /data/efs tmpfs rw,seclabel,relatime,size=20480k,mode=750,gid=1000 0 0
/dev/block/mmcblk0p16 /firmware/q6 vfat ro,relatime,fmask=0000,dmask=0000,allow_
utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro
0 0
tmpfs /data/secure/data tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_i
d=1023,default_permissions,allow_other 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,use
r_id=0,group_id=0,allow_other 0 0
[email protected]:/ $
Click to expand...
Click to collapse
godzilla61 said:
Ok, more info: phone works. no recovery it just keeps showing the curtain over and over...... So now ADB....can't do a thing with it. Can't fastboot flash anything.....error: cannot load 'openrecovery-m7wls-2.7.1.1-06-05-2014' so what now?
Click to expand...
Click to collapse
I have no idea why you think /cache is your problem:
"/dev/block/mmcblk0p38 /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0"
It mounted fine.
As for flashing TWRP, you have to give fastboot an actual file:
"error: cannot load 'openrecovery-m7wls-2.7.1.1-06-05-2014"
The file is (assuming you didn't rename it) "openrecovery-m7wls-2.7.1.1-06-05-2014.img" -- there's an extension on the end.
If you did rename it, then you didn't place the file where you have fastboot. Either give the *full path* to the .img file, or move (or copy) it to the directory in which fastboot exists.
Thanks for taking the time to help! This gave me a reason to update my tool box for android. It's funny I never had to use a file ext. before when installing. It was that simple! So twrp is up and running again, I wonder why it was looping.....for another time perhaps. Thanks once again tdhite!!!
Whenever I try and move an app to the SD card from Manage Applications it says not enough storage space, even though it has plenty of space. Is read/write being disabled in 5.0.1. doing that? Seems likely, just since it's not saying access denied etc figured I'd check if I wasn't hitting some other issue.
Xeddicus said:
Whenever I try and move an app to the SD card from Manage Applications it says not enough storage space
Click to expand...
Click to collapse
if you have a spare SD card i'd copy all the data to Your computer and
try a different SD card
if this does not work you have a bad tablet and need to return it
Ricci
on 5.0.0 not all apps move to sd for me. I dont understand how the 5.0.1 update changes sd cards but it is aparently meant to stop apps writing to the sd card
i can only move apps to SD if its formated vFat (Fat32). (same for anything applied by the Android 5 SD-permission system)
it doesn´t seem to work on exFat, ext3, ext4
DoubleDeepDroid said:
i can only move apps to SD if its formated vFat (Fat32). (same for anything applied by the Android 5 SD-permission system)
it doesn´t seem to work on exFat, ext3, ext4
Click to expand...
Click to collapse
That's weird, how do you know the format of the card once it's inserted into the device? Or do you format fat32 before installing?
ldeveraux said:
That's weird, how do you know the format of the card once it's inserted into the device? Or do you format fat32 before installing?
Click to expand...
Click to collapse
you can check the format with me.kuder.diskinfo app (cannot post link as a new user) for instance.
i format the cards on my workstation.
the Fire (5.0.1) formats cards as exFat as far as i remember,
so you cannot select them in the android 5 write permission choser.
just wondering if anyone has figured out these issues,i want to mount my sdcard as rw ext4 preferably to bypass the filesize limitations of fat filesystem. I have reformatted to ext4 and it says "Unformatted SD Card". but i pushed cancel, and entered...
Code:
[email protected]:/ # mount -rw -t ext4 dev/block/mmcblk1p1 storage/sdcard1/
[email protected]:/ # mount
rootfs / rootfs ro,seclabel,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
none /dev/cpuctl cgroup rw,relatime,cpu 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
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,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
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/media_rw tmpfs rw,seclabel,relatime,mode=755,uid=1000,gid=1000 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro,seclabel,relatime,discard,nodelalloc,errors=panic,commit=1,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
dev/block/mmcblk1p1 /storage/sdcard1 ext4 rw,seclabel,relatime,data=ordered 0 0
[email protected]:/ # ls storage/sdcard1/
Android
DCIM
LOST.DIR
lost+found
my B&N downloads
(these are my backed up files)
i know i didnt get all the places that the extsdcard is actually mounted to, my apps that are installed on the sdcard wont work!! of course its all the ones i want to work with. And i can still see the files in my file browser.