[SM-J500FN] How to safely remove bloatware from Galaxy J5 (2015)? - Samsung Galaxy J5 Questions & Answers

Hello there. My device is running out of space despite all external apps have been moved to SD card.
My current configuration:
Model: SM-J500FN
Internal memory: 8 GB
System: Android 6.0.1
SELinux: enforcing
Modem: J500FNXXU1BQC1
KNOX: 0x0 (not tripped)
Mount points:
Code:
1|[email protected]:/ $ df
Filesystem Size Used Free Blksize
/dev 681.6M 144.0K 681.4M 4.0K
/sys/fs/cgroup 681.6M 12.0K 681.5M 4.0K
/mnt 681.6M 0.0K 681.6M 4.0K
/mnt/secure 681.6M 0.0K 681.6M 4.0K
/system 2.0G 1.9G 84.8M 4.0K
/data 4.7G 4.7G 29.8M 4.0K
/efs 9.8M 332.0K 9.4M 4.0K
/cache 192.8M 3.2M 189.6M 4.0K
/persist 3.9M 104.0K 3.8M 4.0K
/firmware 64.0M 11.5M 52.5M 16.0K
/firmware-modem 64.0M 44.6M 19.3M 16.0K
/persdata/absolute 4.8M 96.0K 4.8M 4.0K
/storage 681.6M 0.0K 681.6M 4.0K
/mnt/knox 4.7G 4.7G 29.8M 4.0K
/mnt/shell/enc_media 4.7G 4.7G 0.0K 4.0K
/storage/emulated 4.7G 4.7G 0.0K 4.0K
/data/enc_user 4.7G 4.7G 29.8M 4.0K
/mnt/shell/enc_emulated 4.7G 4.7G 0.0K 4.0K
/storage/0000-0001 14.8G 2.6G 12.2G 32.0K
I cannot view content of /data directory:
Code:
ls /data
opendir failed, Permission denied
Do I need to root my phone to view and modify /data partition and to uninstall bloatware apps? What do I really need to grant access to /data from adb or any other shell? Do I need to change SELinux from enforcing to permissive? Are there any other protections except SELinux and standard Linux access control? Will rooting the device even let me view and modify /data?
Any known method without tripping KNOX?
I also tried:
Code:
pm uninstall --user 0 com.package.name
am start -a android.intent.action.DELETE -d package:com.package.name
Uninstalling preinstalled apps this way doesn't free space.
I tried to install TWRP with Odin but I was unable to enter recovery after rebooting phone (even after rebooting it manually). System boots normally and replaces TWRP with original recovery. But KNOX flag is still 0x0. What triggers tripping e-fuse? It looks like flashing something to AP does not trip KNOX. Is it related with DM verity phase at boot?
Well, if you know a way without tripping KNOX and lowering system security to access /data and uninstall bloatware completely, then it will be preferred way. If phone needs to be rooted, is TWRP + Magisk/SuperSU recommended way or flashing SuperSU by Chainfire installation script via Odin? I looked at the script (Chainfire's SuperSU) and there are 2 ways to root phone: replacing system files or patching boot image (+ changing SELinux to permissive, disabling DM verity, modifying fstab). Will all of these methods trip KNOX to 0x1?

Related

APPS2SD newbie help please please

can anyone help me?? I don't get the line /system/sd to continue procedure for installing apps on SD card..... I have Amon Ra 1.6 recovery but original ROM.....
I must change ROM or any good and expert user can help me to resolve this enigma?
List of command via Windows 7 consolle CMD terminal.
List of devices attached
HT9AWLG02845 device
C:\A21\tools>adb remount
remount succeeded
C:\A21\tools>adb shell
# dd if=/sdcard/busybox of=/system/xbin/busybox
dd if=/sdcard/busybox of=/system/xbin/busybox
/system/xbin/busybox: cannot open for write: No such file or directory
# dd if=/sdcard/busybox of=/system/bin/busybox
dd if=/sdcard/busybox of=/system/bin/busybox
1283+1 records in
1283+1 records out
657372 bytes transferred in 0.305 secs (2155318 bytes/sec)
# chmod 4755 /system/bin/busybox
chmod 4755 /system/bin/busybox
# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 93.0M 0 93.0M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 150.0M 136.5M 13.5M 91% /system
/dev/block/mtdblock5 165.1M 149.2M 15.9M 90% /data
/dev/block/mtdblock4 150.0M 4.9M 145.1M 3% /cache
/dev/block//vold/179:1
6.6G 3.0G 3.6G 46% /sdcard
#
# su
# ls -l /data
lrwxrwxrwx root root 2010-06-14 01:35 drm -> /data/local
-rwxrwxrwx media system 44 2010-07-15 22:35 awbautocal.bin
drwxr-xr-x system system 2010-06-24 14:42 tombstones
drwxrwx--t system misc 2010-06-14 01:36 misc
drwxrwx--x system system 2010-06-14 01:35 app-private
-rw-rw-rw- root shell 91 2010-07-02 22:34 reboot.chk
drwxrwx--x system system 2010-07-17 22:52 data
drwxrwx--x system system 2010-07-17 22:52 dalvik-cache
drwxrwx--x system system 2010-07-17 22:52 app
drwx------ root root 2010-07-11 17:17 property
drwxrwx--x shell shell 2010-06-14 01:36 local
drwxrwxrwx bluetooth bluetooth 2010-06-28 22:05 btips
-rw-rw-rw- media system 14 2010-07-10 13:14 StreamingPacketLost.txt
drwxrwx--x system system 2010-07-12 00:12 anr
prw-r--r-- system system 2010-06-14 19:36 gps_nmea_fifo
drwxrwxr-x system system 2010-07-17 22:52 system
drwxrwx--- root root 1980-01-06 03:12 lost+found
#su
# busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 93.0M 0 93.0M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 150.0M 136.5M 13.5M 91% /system
/dev/block/mtdblock5 165.1M 148.5M 16.7M 90% /data
/dev/block/mtdblock4 150.0M 4.8M 145.2M 3% /cache
/dev/block//vold/179:1
6.6G 2.8G 3.8G 42% /sdcard
#

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

[Q] Low /system space on watch?- G Watch R

Hi i noticed i currently have low system space on my g watch r, tried to reset the watch, also tried reset the watch by installing the system.img again. but still the system only have 33mb left.
anyone else having such issues. or an idea how to fix it?
Code:
Filesystem Size Used Free Blks
/dev 232.9M 20.0K 232.9M 4096
/sys/fs/cgroup 232.9M 12.0K 232.9M 4096
/mnt/asec 232.9M 0.0K 232.9M 4096
/mnt/obb 232.9M 0.0K 232.9M 4096
/system 248.0M 215.0M 33.0M 4096
/cache 248.0M 17.6M 230.4M 4096
/data 2.9G 529.0M 2.4G 4096
/persist 11.7M 84.0K 11.7M 4096
/mnt/shell/emulated 2.9G 529.0M 2.4G 4096
same with lg g watch
FettleifIsMyUserName said:
Hi i noticed i currently have low system space on my g watch r, tried to reset the watch, also tried reset the watch by installing the system.img again. but still the system only have 33mb left.
anyone else having such issues. or an idea how to fix it?
Code:
Filesystem Size Used Free Blks
/dev 232.9M 20.0K 232.9M 4096
/sys/fs/cgroup 232.9M 12.0K 232.9M 4096
/mnt/asec 232.9M 0.0K 232.9M 4096
/mnt/obb 232.9M 0.0K 232.9M 4096
/system 248.0M 215.0M 33.0M 4096
/cache 248.0M 17.6M 230.4M 4096
/data 2.9G 529.0M 2.4G 4096
/persist 11.7M 84.0K 11.7M 4096
/mnt/shell/emulated 2.9G 529.0M 2.4G 4096
Click to expand...
Click to collapse
This is completely fine. Low space on /system will not cause any problems on your device. Apps, data and ART cache are stored in /data and /cache respectively, the only time /system is ever touched is during an update or if you for some reason install apps to the system partition (possibly to make them survive a factory reset?)
Other than that, you should never need to worry about the space on /system. The current update solutions patch the partition contents directly (hence the reason why if you change something on /system, you're ineligible for OTAs)

A20e Data Recovery without root?

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

Categories

Resources