A20e Data Recovery without root? - Samsung Galaxy A20 Questions & Answers

Hi,
Samsung Galaxy A20e SM-A202F/DS Android 11
My intention is to delete some photos that have been accidentally deleted.
All Windows Trial Applications I tried require root to be able to execute deep scan.
Is it possible to execute deep scan without root?
For example using download or recovery mode or copy the data partition to PC and scan using testdisk?
And if not is it possible to undo root / reset the knox counter?
Thank you in advance.
How to recover a deleted file from /data partition?
I factory reset my rooted Android M phone but now I realize that there was a file in the /data directory which I need. Is it possible to create an image (.img or something similar) of the /data
android.stackexchange.com
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
a20e:/ $ mount | grep 'on /data'
/dev/block/mmcblk0p32 on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,resgid=5678,i_version)
/dev/block/mmcblk0p32 on /data/user/0 type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,resgid=5678,i_version)
tmpfs on /data_mirror type tmpfs (rw,seclabel,nosuid,nodev,noexec,relatime,size=1394256k,nr_inodes=348564,mode=700,gid=1000)
/dev/block/mmcblk0p32 on /data_mirror/data_ce/null type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,resgid=5678,i_version)
/dev/block/mmcblk0p32 on /data_mirror/data_ce/null/0 type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,resgid=5678,i_version)
/dev/block/mmcblk0p32 on /data_mirror/data_de/null type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,resgid=5678,i_version)
/dev/block/mmcblk0p32 on /data_mirror/cur_profiles type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,resgid=5678,i_version)
a20e:/ $ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 3.9G 3.8G 126M 97% /
tmpfs 1.3G 1.3M 1.3G 1% /dev
tmpfs 1.3G 0 1.3G 0% /mnt
/dev/block/dm-1 542M 467M 76M 87% /product
/dev/block/dm-2 504M 316M 188M 63% /vendor
tmpfs 1.3G 0 1.3G 0% /apex
/dev/block/mmcblk0p29 45M 24K 45M 1% /omr
/dev/block/mmcblk0p28 390M 17M 373M 5% /cache
tmpfs 1.3G 0 1.3G 0% /mnt/sde
/dev/block/mmcblk0p32 23G 11G 11G 51% /data
/dev/block/mmcblk0p4 16M 432K 15M 3% /efs
/dev/fuse 23G 12G 11G 51% /storage/emulated

Related

Need someone to run an adb command for me

Need a small favor in return for all the help I've given those with kindle fires. I don't have a kindle fire and need some information from someone that does.
Anyone that knows how, I need them to run (if they're using the stock kindle firmware, not cm7):
Code:
adb shell df
Then paste me the results either here or in a PM.
If you're wondering what that information is, it's the partition sizes and disk space of your kindle. I need it for something I am working on that will benefit people that can't restore their device due to excessive noobness
Thanks!
Sent from my Kindle Fire using xda premium
df, followed by df -h
~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 228588 32 228556 0% /dev
tmpfs 228588 0 228588 0% /mnt/asec
tmpfs 228588 0 228588 0% /mnt/obb
/dev/block/platform/mmci-omap-hs.1/by-name/system
516040 286784 229256 56% /system
/dev/block/platform/mmci-omap-hs.1/by-name/userdata
1145996 288472 857524 25% /data
/dev/block/platform/mmci-omap-hs.1/by-name/cache
258016 4232 253784 2% /cache
/dev/block/platform/mmci-omap-hs.1/by-name/splash
4795 1591 3204 33% /dropbox
/dev/block/vold/179:12
5243884 2141684 3102200 41% /mnt/sdcard
/dev/block/vold/179:12
5243884 2141684 3102200 41% /mnt/secure/asec
/dev/block/dm-0 71632 69304 2328 97% /mnt/asec/com.ea.simcitydeluxetab_full_azn-1
/dev/block/dm-1 11424 10232 1192 90% /mnt/asec/kemco.wws.eog.hd.amazon-1
/dev/block/dm-2 3124 2040 1084 65% /mnt/asec/com.quoord.tapatalkxdapre.activity-1
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 223.2M 32.0K 223.2M 0% /dev
tmpfs 223.2M 0 223.2M 0% /mnt/asec
tmpfs 223.2M 0 223.2M 0% /mnt/obb
/dev/block/platform/mmci-omap-hs.1/by-name/system
503.9M 280.1M 223.9M 56% /system
/dev/block/platform/mmci-omap-hs.1/by-name/userdata
1.1G 281.7M 837.4M 25% /data
/dev/block/platform/mmci-omap-hs.1/by-name/cache
252.0M 4.1M 247.8M 2% /cache
/dev/block/platform/mmci-omap-hs.1/by-name/splash
4.7M 1.6M 3.1M 33% /dropbox
/dev/block/vold/179:12
5.0G 2.0G 3.0G 41% /mnt/sdcard
/dev/block/vold/179:12
5.0G 2.0G 3.0G 41% /mnt/secure/asec
/dev/block/dm-0 70.0M 67.7M 2.3M 97% /mnt/asec/com.ea.simcitydeluxetab_full_azn-1
/dev/block/dm-1 11.2M 10.0M 1.2M 90% /mnt/asec/kemco.wws.eog.hd.amazon-1
/dev/block/dm-2 3.1M 2.0M 1.1M 65% /mnt/asec/com.quoord.tapatalkxdapre.activity-1
~ #
Sent from my Kindle Fire using xda premium
Thanks guys!
If I need anything else, I will ask
Basically, I want to try to automate recovery using fastboot with a graphical app I'm writing in QT (so it'll work on windows, linux and osx). I need to make a system image (system.img), so needed to know what the block size is. That should cut down on a lot of the questions asked.
ty very much

Can not access 5GB data partiton

Hi I am running with cyonogenmod 7.1.
When i go to settings>storage. it reads
Total Space = 5.09GB and Available Space = 4.69GB
And when i type df in adb i got
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 246064 32 246032 0% /dev
tmpfs 246064 0 246064 0% /mnt/asec
tmpfs 246064 0 246064 0% /mnt/obb
/dev/block/mmcblk0p2 72134 40 72094 0% /rom
/dev/block/mmcblk0p5 451118 162464 265362 38% /system
/dev/block/mmcblk0p6 5336664 144408 4921164 3% /data
/dev/block/mmcblk0p7 350021 46736 285214 14% /cache
But when i turn on USB storage in my PC i got MyNOOKColor drive and when i go to properties it shows only 829MB free space.
mejack03 said:
Hi I am running with cyonogenmod 7.1.
When i go to settings>storage. it reads
Total Space = 5.09GB and Available Space = 4.69GB
And when i type df in adb i got
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 246064 32 246032 0% /dev
tmpfs 246064 0 246064 0% /mnt/asec
tmpfs 246064 0 246064 0% /mnt/obb
/dev/block/mmcblk0p2 72134 40 72094 0% /rom
/dev/block/mmcblk0p5 451118 162464 265362 38% /system
/dev/block/mmcblk0p6 5336664 144408 4921164 3% /data
/dev/block/mmcblk0p7 350021 46736 285214 14% /cache
But when i turn on USB storage in my PC i got MyNOOKColor drive and when i go to properties it shows only 829MB free space.
Click to expand...
Click to collapse
Originally Nook Colors were partitioned to have 1GB data space (used for downloaded apps and associated data-settings, B&N stuff) and 5GB user space for user media (MyNookColor). This was changed mid last year by B&N to allocate 5GB for Data and only 1GB for user space. When you mount on the PC you only see the 1GB partition.
When running CM7 this new split is inappropriate as you are not downloading lots of B&N content.
Check out this thread. Personally I went for a 2G data and 4G user as that allows plenty of room for downloaded apps whereas 1G could get tight.
http://forum.xda-developers.com/showthread.php?t=1094371

Get Extra 295MB from "hidden" partition

Unlike my sgs1 which has all its partitions used, the Galaxy Tab 10.1 appears to have a "hidden" partition that seems to do absolutely nothing (at least on CM10). I saw it on the siyah kernel thread. By adapting that idea to the GTab 10.1 you can run this script
Code:
mount -o,remount,rw /
mkdir /storage/sdcard1
busybox mount /dev/block/mmcblk0p10 /storage/sdcard1
busybox chmod -R 777 /storage/sdcard1
you will have access to that extra 295MB that's apparently just sitting there collecting virtual dust. It's indeed legitimate:
Code:
Filesystem Size Used Free Blksize
/dev 360M 48K 360M 4096
/mnt/asec 360M 0K 360M 4096
/mnt/obb 360M 0K 360M 4096
/system 568M 371M 197M 4096
/cache 440M 80M 360M 4096
/data 13G 8G 4G 4096
/efs 11M 4M 7M 4096
/storage/sdcard0 13G 8G 4G 4096
/storage/sdcard1 295M 12M 282M 4096
[email protected]:/ $ mount | grep mmcblk0p10
/dev/block/mmcblk0p10 /storage/sdcard1 ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
Just thought I would share the finding. You would have to run that script at boot or whenever you wanted it.
Nice find! Thanks for the info :thumbup:
Sent from my SGH-I747 using xda premium
Nice find, Where will it "put" the additional space, ie will it add it to the storage, system etc...
Sent from my GT-N7100 using Tapatalk 2
RavenY2K3 said:
Nice find, Where will it "put" the additional space, ie will it add it to the storage, system etc...
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
The script I suggested will make it like a second sd card. It will be in /storage/sdcard1.
Sent from my GT-I9300
Might try that. What terminal emulator did you use. There are so many?
rob2011 said:
Might try that. What terminal emulator did you use. There are so many?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=jackpal.androidterm
thanks. ill give that a try
Some additional information...
On Toldo's rom these partition is used for other things.
Code:
/dev 360M 68K 360M 4096
/mnt/asec 360M 0K 360M 4096
/mnt/obb 360M 0K 360M 4096
/system 568M 513M 55M 4096
/cache 440M 7M 433M 4096
/data 13G 8G 4G 4096
/efs 11M 8M 3M 4096
/mnt/sdcard 13G 8G 4G 4096
[B]/preload 295M 216M 78M 4096[/B]
That partition is named /preload and holds some other things.
Code:
[email protected]:/preload # ls -a
CPW
Common_app
DBT
ITV
KOR
XEF
XEO
XEU
The only partion that holds data is /Common_app.
Code:
[email protected]:/preload/Common_app # ls -a
Aurora.apk
Bluesea.apk
HoloSpiralWallpaper.apk
Kobo.apk
PolarisOffice.apk
PressReader.apk
ReadersHub_EUR.apk
Swype.apk
Zinio.apk
So for users outside CM this partition is not free. It can be used but only 78MB are free.
I think this partition will be made while booting, so files on it will be copied while booting.
But i am can be totaly wrong. I have to searvh for it first.
Update about /preload:
What i have found is the following:
Code:
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /efs ext4 /dev/block/mmcblk0p1 (null) 0
2 /recovery emmc /dev/block/mmcblk0p2 (null) 0
3 /boot emmc /dev/block/mmcblk0p3 (null) 0
4 /system ext4 /dev/block/mmcblk0p4 (null) 0
5 /cache ext4 /dev/block/mmcblk0p5 (null) 0
6 /data ext4 /dev/block/mmcblk0p8 (null) 0
7 [B]/preload[/B] ext4 /dev/block/mmcblk0p10 (null) 0
After a test i have seen that the partition is read only. But ES File Explorer says: rwx r-x r-x
Means that a User can read, write and excute, Group and Others only read and execute.
Lucky the guys who are using CM. But no issue at all, the USB post is working perfect for
external media. At the end a good find...

[Q] /system ext3 strangely formated

Hi,
I've been struggling for days installing any custom rom into my defy.
When I finally checked the log, I saw it interrupted with "no space left on device" about halfway through.
But there still is space, only 32% are in use (~100MB of~ 300MB).
/system just ran out of inodes.
Finally I succeeded after I removed most of the terminals in /etc/terminfo/* from the latest nightly before installing it. (CM10, 20130110, that is)
df -i /system
Filesystem Inodes Used Available Use% Mounted on
/dev/block/mmcblk1p21 1968 1915 53 97% /system
I don't understand, how come /system only has ~2000 inodes (typical should be ~10k)?
(I'm not the first owner, so I don't know what happened to the device before...I got it with some Vodafone branded firmware on it, but you never know..)
I'm afraid of simply formatting it, because bootmenu and recovery seem to be running from /system, and formatting might render the device nonfunctional.
How do I get back to a proper fs?
Is there a way to safely format /system?
Or should I better tune2fs?
Anyone seen this before?
Thanks,
mcr42
Ran out of inodes! ("No space left on device")
I seem to have the same problem. A few days after doing a fresh install of CyanogenMod7.2 + Googleapps, I start to get Gapps and other processes crashing all the time. Looking in the logfiles using "adb logcat -d" even immediately after bootup, it reports:
W/BatteryStats( 2274): Error writing battery statistics
W/BatteryStats( 2274): java.io.FileNotFoundException: /data/system/batterystats.bin.tmp (No space left on device)
and indeed I have lots of space, but no inodes left at all:
df -k .
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mmcblk1p25
130837 97898 32939 75% /data
df -i .
Filesystem Inodes Used Available Use% Mounted on
/dev/block/mmcblk1p25
1296 1296 0 100% /data
Can anyone suggest what's going on and how to fix it?
Thanks,
Richard
P.S. As a bit of background, I wonder if things have got messed up on an earlier install when a while back after using S2E to move most things to an ext4 partition on the SD card, I later used S2E to revert the system to normal, but it crashed half-way through the process. I believe that is sorted now as "mount" doesn't report looking for anything on sd-ext partition (which I have removed since anyway):
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk1p21 on /system type ext3 (ro,relatime,barrier=1,data=ordered)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
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/mmcblk1p24 on /cache type ext3 (rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered)
/dev/block/mmcblk1p25 on /data type ext3 (rw,nosuid,nodev,noatime,nodiratime,data=ordered)
/dev/block/loop7 on /pds type ext3 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered)
ramfs on /tmp type ramfs (rw,relatime,relatime)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
CM10 latest nightly is the unofficial late august build by sunnyqeen. If you have custom recovery, flash AROMA wiper (search) and fully wipe system, data and cache in ext4 and then immediately flash ROM and gapps.
Is there a way to increase the number of inodes on /data?
Following up my email, I've been looking through the full list of files on /data (the number closley tallies with the 1296 inodes available). There were quite a few (but not excessive number) of debug files in /data/system/dropbox which I've deleted to free up a few inodes. However 1296 inodes doesn't seem sufficient. Does this tally with what most people have on their Defy phones? Grateful if someone could connect to their phone and run the following:
adb shell df -i /data
I have seen there have been reports of ClockworkMod Recovery prior to version 6 corrupting inodes:
http://forum.xda-developers.com/showthread.php?t=2111734
Grasping at straws, could this be what is happening resulting in a loss of inodes?
(Rebooting to (Cyanmod) recovery mode on my phone reports "Bootmenu Recovery v5.0.6" - does that tie in with CWM v5 then?)
Richard

recover photos on wiped Internal Storage

i accidentally wiped my Internal Storage, and with that all my photos that were in the DCIM folder. I tried some Google Play file undelete software, but unfortunately my photos were not recovered.
i've found some site with a tutorial here https://www.dflund.se/~jokke/androidfilerecovery/ , on how to extract the Internal Storage partition to a raw file, and then with testdisk it should be possible to analyse the image and find for recoverable files.
The command to extract the Internal Storage should be
Code:
/adb shell su -c "cat /dev/block/mmcblk0" | pv > mmcblk0.raw
and i've done all the steps in the tutorial.
at some point i get a message that the reported size of the partition is not correct and i can't get to the point where i should be able to see deleted files.
is there any other way to find and restore my wiped photos? (directly via ADB or any other way )
using the DF command in an ADB shell gives
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 1878584 692 1877892 1% /dev
tmpfs 1878584 0 1878584 0% /mnt
/dev/block/mmcblk0p42 2539312 1373916 1149012 55% /system
/dev/block/mmcblk0p43 56627428 21661152 34949892 39% /data
/dev/block/mmcblk0p41 253920 184 248496 1% /cache
/dev/block/mmcblk0p37 28144 4256 23236 16% /persist
/dev/block/mmcblk0p1 81872 77360 4512 95% /firmware
/dev/block/mmcblk0p2 1048288 176 1048112 1% /bt_firmware
/data/media 56627428 21661152 34949892 39% /storage/emulated
is there a video tutorial that i can watch?
And so did it work i kinda have the same situation as you

Categories

Resources