Related
Hi, I am currently using Note 5 on another carrier. I have messed up some settings and need the carrier partition from a Sprint Activated Note 5. This can be pulled of easily from a rooted Note 5 and doesn't contains any personal information.
-- On a rooted Note 5 N920P, run adb shell as ROOT (su)
---use following command to pull Carrier partition to sdcard
--- dd if=/dev/block/platform/15570000.ufs/by-name/carrier of=/sdcard/sprint_note5_Carrier.img
Zip and share on any file hosting website.
Any help will be appreciated. Thanks in advance.
Hey!
I found this thread with fully compile-able code for android on most hardware platforms, I see it uses system level modifications to do its business, and would love to see it rolled into a magisk module. I regularly use external hard drives on my Pixel 2 XL for a plethora of reasons and really need legit exFat and NTFS support as I use flash kernel and I cant merge the code myself (my only machine couldn't handle the compiling). Anyway, If possible, making a ZIP that is universal and has the binaries for arm, arm64, and all x86 variants would be pretty great!
GitHub: https://github.com/Lurker00/Android-fs
XDA: https://forum.xda-developers.com/android/development/exfat-ntfs-fuse-drivers-easy-build-t3126413
I am not magisk-ninja so anyone who can help make this happen OR educate me in the process of doing so (and who can compile the above Git files for arm64 and send them to me) would be very much appreciated! I am willing to learn to help the community!
Over and out
thomasamas said:
Hey!
I found this thread with fully compile-able code for android on most hardware platforms, I see it uses system level modifications to do its business, and would love to see it rolled into a magisk module. I regularly use external hard drives on my Pixel 2 XL for a plethora of reasons and really need legit exFat and NTFS support as I use flash kernel and I cant merge the code myself (my only machine couldn't handle the compiling). Anyway, If possible, making a ZIP that is universal and has the binaries for arm, arm64, and all x86 variants would be pretty great!
GitHub: https://github.com/Lurker00/Android-fs
XDA: https://forum.xda-developers.com/android/development/exfat-ntfs-fuse-drivers-easy-build-t3126413
I am not magisk-ninja so anyone who can help make this happen OR educate me in the process of doing so (and who can compile the above Git files for arm64 and send them to me) would be very much appreciated! I am willing to learn to help the community!
Over and out
Click to expand...
Click to collapse
Hi. I just started working on this yesterday.
It seems like the perfect method to install additional filesystem support.
I am currently able to manually mount exfat or ntfs sdcard images on my phone (LG Aristo 2, Android 7).
However, a great deal has changed in how filesystem support is added to an existing kernel. Lurker00's code is for Android 4.4.2.
If you want to work together on it, I would be more than happy to do so. I will try to get together what I have so far in a post later today.
FYI, this is a TWRP installable .zip that has Lurker00's compiled binaries for arm64-v8a, armeabi-v7a, x86 and x86_64.
It also installs init.d scripts that supposedly support auto mounting of exFat and NTFS partitions. That part is not working for me, as I think it is setup for Android 5 and before. However the mount binaries work for manually mounting exFat or NTFS partitions.
Just install the .zip from TWRP.
https://forum.xda-developers.com/attachment.php?attachmentid=4600419&stc=1&d=1537390717
Hey! I just saw this, I can try my best but I was assuming it wouldn't be an android thing but rather a Linux/android kernel thing. Is there a way we can Abstract the mounting from android, solely into the kernel, basically leaving Android unaware that the introduced file system is not "officially supported"? I'm assuming FUSE can do this.
Edit: spelling.
tecknight said:
Hi. I just started working on this yesterday.
It seems like the perfect method to install additional filesystem support.
I am currently able to manually mount exfat or ntfs sdcard images on my phone (LG Aristo 2, Android 7).
However, a great deal has changed in how filesystem support is added to an existing kernel. Lurker00's code is for Android 4.4.2.
If you want to work together on it, I would be more than happy to do so. I will try to get together what I have so far in a post later today.
FYI, this is a TWRP installable .zip that has Lurker00's compiled binaries for arm64-v8a, armeabi-v7a, x86 and x86_64.
It also installs init.d scripts that supposedly support auto mounting of exFat and NTFS partitions. That part is not working for me, as I think it is setup for Android 5 and before. However the mount binaries work for manually mounting exFat or NTFS partitions.
Just install the .zip from TWRP.
https://forum.xda-developers.com/attachment.php?attachmentid=4600419&stc=1&d=1537390717
Click to expand...
Click to collapse
How exactly do you manually mount them? (your method)
Edit: also! I was thinking maybe this could become a kernel patch that I could alert kernel devs to? (see my above comment)
And... Thanks for all the hard work to get this going. Tell me how I can help!
thomasamas said:
How exactly do you manually mount them? (your method)
Edit: also! I was thinking maybe this could become a kernel patch that I could alert kernel devs to? (see my above comment)
And... Thanks for all the hard work to get this going. Tell me how I can help!
Click to expand...
Click to collapse
I installed the .zip file that I posted earlier using TWRP.
This installs these binaries to /system/xbin:
mount.exfat
mkfs.exfat
fsck.exfat
dumpexfat
exfatfsck
exfatlabel
mkexfatfs
mount.exfat-fuse
ntfs-3g
ntfsfix
probe
I then inserted an exFat formatted SDCard into my phone and Android told me the device was corrupt.
That is due to the fact that Android no longer uses probe to determine the filesystem of a device, it now uses a program called blkid.
I would like to figure out how to add a new supported filesystem type to blkid
In any event, I mounted my exFat sdcard by launching a shell from adb, running su to get root and then I created a folder named exfatsd in the /mnt folder. I then ran this command:
mount.exfat /dev/block/mmcblk1 /mnt/exfatsd
The mount succeeded and I was able to browse the sdcard from /mnt/exfatsd
When I typed mount to enumerate the mounts, this is the entry I saw for my sdcard:
/dev/block/mmcblk1 on /mnt/exfatsd type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
By the way, even as i was browsing the exfat sdcard, Android still had a notification up telling me that my sdcard was corrupt
Is there any legit documentation on blkid?
I haven't found any, but I haven't given up on this project either. I have been busy on a couple of other things lately, but I still would like to see this work.
Making progress on this on my LG cv1 ROMs
I just wanted to let you know that I now have exFAT and NTFS support working on my phone, even though the kernel does not have support for either filesystem..
I am mounting the Micro SD using a script that runs under Magisk from the:
post.fs.data.d folder
This folder contains scripts that are to run immediately after the /data filesystem is mounted.
My script is checking the Micro SD device using the blkid command.
The blkid command will indicate the type of filesystem residing on the device, even if the kernel won't mount it.
So I use the results from the blkid command to issue mount commands myself using the binaries created by lurker00.
Here is the script I am using, it is really quite short:
Code:
#!/system/bin/sh
#
# mount NTFS / exFAT
# 06/07/2019 by TecKnight
# This script checks the inserted Micro SD--
# If Micro SD is formatted exFAT or NTFS, it mounts it
sdcard_device=`blkid /dev/block/mmcblk1`
sdcard_part1=`blkid /dev/block/mmcblk1p1`
# Uncomment next 2 lines to troubleshoot
# echo $sdcard_device > /cache/sdcard_device.txt
# echo $sdcard_part1 > /cache/sdcard_part1.txt
# output from blkid command looks like this:
# /dev/block/mmcblk1p1: LABEL="e" UUID="CEDC-3F3A" TYPE="exfat"
# create mount point
mkdir /mnt/media_rw/extsd
# mount approriate filesystem if it resides on device directly
case "$sdcard_device" in
*exfat*) mount.exfat /dev/block/mmcblk1 /mnt/media_rw/extsd ;;
*ntfs*) ntfs-3g /dev/block/mmcblk1 /mnt/media_rw/extsd ;;
esac
# mount approriate filesystem if it resides on first partition of device
case "$sdcard_part1" in
*exfat*) mount.exfat /dev/block/mmcblk1p1 /mnt/media_rw/extsd ;;
*ntfs*) ntfs-3g /dev/block/mmcblk1p1 /mnt/media_rw/extsd ;;
esac
FYI: The reason I am checking /dev/block/mmcblk1 (the actual SD card itself) and dev/block/mmcblk1p1 (the first partition on the sdcard) is that depending on where the sdcard is formatted exFAT or NTFS, it could be on the disk itself or within a parrition. This way, I will catch it either way and mount it correctly.
I was thinking of creating a subroutine to cycle through the block devices to determine the sdcard device.
This would make it compatible with practically every device.
Then I could turn the whole thing into a Magisk module.
There are still 2 minor issues that I am having:
1. The phone still displays a notification about the sdcard being corrupt. You just have to clear the notification and it never reappears.
2. The mounted card is not identified as an external SD by android.
However, the exFAT or NTFS filesystem is mounted at /mnt/media_rw/extsd and is browseable and the filesystem is readable and writable.
Tell me what you think.
TWRP installable .zip to install NTFS/exFAT suport
OK, this is a installable .ZIP that will copy the binaries to /system/xbin and copy the mounting script to:
/data/adb/post-fs-data.d.
This should enable NTFS/exFAT support to most phones.
Requirements:
1. You must have Magisk installed
2. Your Micro SD''s device address must be:
/dev/block/mmcblk1. This is the case on most devices running Android 6 or higher.
If your Micro SD's device address is different, you can fix it by modifying:
/data/adb/post-fs-data.d/mount_ntfs_exfat.sh
replacing /dev/block/mmcblk1 with the device address of your external Micro SD.
Download the installer here:
https://forum.xda-developers.com/attachment.php?attachmentid=4773292&stc=1&d=1559992139
tecknight said:
OK, this is a installable .ZIP that will copy the binaries to /system/xbin and copy the mounting script to:
/data/adb/post-fs-data.d.
This should enable NTFS/exFAT support to most phones.
Requirements:
1. You must have Magisk installed
2. Your Micro SD''s device address must be:
/dev/block/mmcblk1. This is the case on most devices running Android 6 or higher.
If your Micro SD's device address is different, you can fix it by modifying:
/data/adb/post-fs-data.d/mount_ntfs_exfat.sh
replacing /dev/block/mmcblk1 with the device address of your external Micro SD.
Download the installer here:
https://forum.xda-developers.com/attachment.php?attachmentid=4773292&stc=1&d=1559992139
Click to expand...
Click to collapse
Hi,
I know this post isn't new, but I tried installing this zip file and it tells me that my bootloader in't unlocked even though I'm pretty sure it's unlocked,
any way around this?
rachelld said:
Hi,
I know this post isn't new, but I tried installing this zip file and it tells me that my bootloader in't unlocked even though I'm pretty sure it's unlocked,
any way around this?
Click to expand...
Click to collapse
Same here. Maybe the template is to old? Also could use this module.
aCIDsLAM said:
Same here. Maybe the template is to old? Also could use this module.
Click to expand...
Click to collapse
Try this one:
https://www.androidfilehost.com/?fid=4349826312261782012I removed the check for
ro.boot.bl_unlock_complete = true
---------- Post added at 11:08 PM ---------- Previous post was at 11:06 PM ----------
rachelld said:
Hi,
I know this post isn't new, but I tried installing this zip file and it tells me that my bootloader in't unlocked even though I'm pretty sure it's unlocked,
any way around this?
Click to expand...
Click to collapse
Try this one:
https://www.androidfilehost.com/?fid...26312261782012
I removed the check for
ro.boot.bl_unlock_complete = true
I could flash it, using TWRP. In Magisk itself, it told me me, its no magisk module. Anyway. Thanks!
@thomasamas
@tecknight
Is this thread dead ?
Has these drivers been tested on Android 11 ?
I have a custom ROM and would like to use my SDCard with NTFS/exFAT but the ROM only supports FAT32.
KineSight said:
@thomasamas
@tecknight
Is this thread dead ?
Has these drivers been tested on Android 11 ?
I have a custom ROM and would like to use my SDCard with NTFS/exFAT but the ROM only supports FAT32.
Click to expand...
Click to collapse
+1
tecknight said:
TWRP installable .zip to install NTFS/exFAT suport
OK, this is a installable .ZIP that will copy the binaries to /system/xbin and copy the mounting script to:
/data/adb/post-fs-data.d.
This should enable NTFS/exFAT support to most phones.
Requirements:
1. You must have Magisk installed
2. Your Micro SD''s device address must be:
/dev/block/mmcblk1. This is the case on most devices running Android 6 or higher.
If your Micro SD's device address is different, you can fix it by modifying:
/data/adb/post-fs-data.d/mount_ntfs_exfat.sh
replacing /dev/block/mmcblk1 with the device address of your external Micro SD.
Download the installer here:
https://forum.xda-developers.com/attachment.php?attachmentid=4773292&stc=1&d=1559992139
Click to expand...
Click to collapse
Actually, this still works! Have tested this on A11 OctaviOS GSI. You still need to have Magisk installed, but you don't necessarily have to install this as a Magisk module.
Don't flash the .zip file from TWRP, it doesn't do anything (at least not for me). Just unzip everything in the .zip file into a folder. Then, take the files inside the xbin folder and put it into /system/xbin (as per instructions). Make sure those files have execute permissions. I just set the xbin folder with full execute permissions and apply to all child files in the folder, by using Root Explorer.
Next, do the same thing by taking the script and chuck that into /data/adb/post-fs-data.d. Again, give this script full execute permissions.
Reboot phone and voila, it should work! You should also see that the script is loaded and running in Magisk logs.
Oh and the reason why Magisk is required is because Magisk creates that "post-fs-data.d" folder after it is installed. If you put scripts into /data/adb/service.d or /data/adb/post-fs-data.d, they will automatically get executed by Magisk and run with superuser rights.
chaoscreater said:
Actually, this still works! Have tested this on A11 OctaviOS GSI. You still need to have Magisk installed, but you don't necessarily have to install this as a Magisk module.
Don't flash the .zip file from TWRP, it doesn't do anything (at least not for me). Just unzip everything in the .zip file into a folder. Then, take the files inside the xbin folder and put it into /system/xbin (as per instructions). Make sure those files have execute permissions. I just set the xbin folder with full execute permissions and apply to all child files in the folder, by using Root Explorer.
Next, do the same thing by taking the script and chuck that into /data/adb/post-fs-data.d. Again, give this script full execute permissions.
Reboot phone and voila, it should work! You should also see that the script is loaded and running in Magisk logs.
Oh and the reason why Magisk is required is because Magisk creates that "post-fs-data.d" folder after it is installed. If you put scripts into /data/adb/service.d or /data/adb/post-fs-data.d, they will automatically get executed by Magisk and run with superuser rights.
Click to expand...
Click to collapse
Hello, I did everything as you said and it worked normally, but now SELinux is turned off. This is normal?
i have same issue. But i cant find xbin folder
my device is Samsung M51 on custom os
I converted this twrp zip into a magisk module https://github.com/phhusson/treble_experimentations/files/8948418/ntfs-exfat-support.zip
Hi.
I'm using Ancient OS A13 and I can't access my SD Card.It asks for format and after formatting it still asks for format.
it still works on my pc and twrp recovery. Unfortunately, this fix isn't working. Also, there is not any xbin folder in system.
What should I Do?
Hi
Since no one reads this bit of the OP, let's get to it. Credit to Cloudxddd for posting the sd card fix in another thread.
Enable ADB shell
On your Tablet:
Open the settings app
Scroll down to 'About tablet'
Select 'Software information'
Continuously tap on 'Build number' over and over until at the bottom of the screen you see a toast saying "Developer mode has been enabled"
Go back to the main settings page and scroll down, select the new 'Developer options' button
Enable 'USB debugging' (press OK to confirm)
On Ubuntu:
Install ADB: sudo apt install adb
Plug your tablet into your PC via USB
Start ADB and check your device is connected: adb devices (if more than one device is listed, unplug your second android phone/tablet
You may need to approve the connection on your tablet
Run ADB shell: adb shell
Remove stock apps (bloatware)
In ADB shell (see above):
List the apps installed: pm list packages
Removing some apps will cause your tablet to brick (fixed by doing a factory reset from the recovery menu), so be careful
Search APK Mirror for the package name if you don't know what app you're looking at
To uninstall an app from your user but keep it on the device: pm uninstall -k --user 0 <packagename>
Reboot the device to ensure it can boot successfully: reboot
Reply below with the apps you removed and whether it was successful / safe
Reinstall that app: cmd package install-existing <package name> (or do a factory reset if it failed)
Completely remove the app and reclaim the space if you're certain it can be removed safely: pm uninstall <packagename>
Reboot the device to ensure it can boot successfully: reboot
Note: Some apps reinstall when you reboot.
Apps that might be safe to remove - Please reply with updates
Package nameApp nameSafe to remove?com.samsung.android.video
Samsung video playerYescom.samsung.android.app.dofviewer
com.samsung.android.app.siofviewer
Samsung live focus?
com.samsung.android.app.dressroom
Samsung wallpapers?
com.sec.android.widgetapp.webmanualSamsung user manualYescom.samsung.android.allshare.service.mediashareSamsung nearby service?com.samsung.android.app.clockpackSamsung clock style?com.google.android.apps.youtube.musicYoutube musicYescom.sec.android.app.bluetoothtestSamsung bluetooth test?
com.samsung.app.newtrimSamsung video trimmer?com.samsung.android.app.shareliveSamsung quick share?
com.samsung.android.scloudSamsung cloud?
com.samsung.android.stickercenterSamsung sticker center?
com.android.chromeGoogle chrome?com.google.android.apps.mapsGoogle maps?
com.google.android.apps.docsGoogle docs?
com.sec.android.gallery3dSamsung gallery?com.google.android.apps.tachyonGoogle DuoYescom.sec.android.app.soundaliveSamsung soundalive?com.microsoft.skydriveMicrosoft onedriveYescom.netflix.mediaclient
com.netflix.partner.activationNetflixYescom.google.android.youtubeYoutubeYescom.google.android.videosGoogle play movies and tvYes
Enable apps to SD
In ADB shell (see above):
List disks: sm list-disks
Partition the disk to be used entirely for apps to SD: sm parition <DISK> private
Partition a percentage of the disk to be used for apps to SD: sm partition <DISK> mixed <number>
Reboot: reboot
Open the 'Settings' app and and select 'Apps'
Select an app
Tap 'Storage'
Tap 'Change' to move it to the SD card (if the app supports this)
Thanks for this! will try today!
.
Hi,
Thanks for sharing. It does delete...but everytime i reboot it comes back...
lukyjay said:
Hi
Since no one reads this bit of the OP, let's get to it. Credit to Cloudxddd for posting the sd card fix in another thread.
Enable ADB shell
On your Tablet:
Open the settings app
Scroll down to 'About tablet'
Select 'Software information'
Continuously tap on 'Build number' over and over until at the bottom of the screen you see a toast saying "Developer mode has been enabled"
Go back to the main settings page and scroll down, select the new 'Developer options' button
Enable 'USB debugging' (press OK to confirm)
On Ubuntu:
Install ADB: sudo apt install adb
Plug your tablet into your PC via USB
Start ADB and check your device is connected: adb devices (if more than one device is listed, unplug your second android phone/tablet
You may need to approve the connection on your tablet
Run ADB shell: adb shell
Remove stock apps (bloatware)
In ADB shell (see above):
List the apps installed: pm list packages
Removing some apps will cause your tablet to brick (fixed by doing a factory reset from the recovery menu), so be careful
Search APK Mirror for the package name if you don't know what app you're looking at
To uninstall an app from your user but keep it on the device: pm uninstall -k --user 0 <packagename>
Reboot the device to ensure it can boot successfully: reboot
Reply below with the apps you removed and whether it was successful / safe
Reinstall that app: cmd package install-existing <package name> (or do a factory reset if it failed)
Completely remove the app and reclaim the space if you're certain it can be removed safely: pm uninstall <packagename>
Reboot the device to ensure it can boot successfully: reboot
Note: Some apps reinstall when you reboot.
Apps that might be safe to remove - Please reply with updates
Package nameApp nameSafe to remove?com.samsung.android.video
Samsung video playerYescom.samsung.android.app.dofviewer
com.samsung.android.app.siofviewer
Samsung live focus?
com.samsung.android.app.dressroom
Samsung wallpapers?
com.sec.android.widgetapp.webmanualSamsung user manualYescom.samsung.android.allshare.service.mediashareSamsung nearby service?com.samsung.android.app.clockpackSamsung clock style?com.google.android.apps.youtube.musicYoutube musicYescom.sec.android.app.bluetoothtestSamsung bluetooth test?
com.samsung.app.newtrimSamsung video trimmer?com.samsung.android.app.shareliveSamsung quick share?
com.samsung.android.scloudSamsung cloud?
com.samsung.android.stickercenterSamsung sticker center?
com.android.chromeGoogle chrome?com.google.android.apps.mapsGoogle maps?
com.google.android.apps.docsGoogle docs?
com.sec.android.gallery3dSamsung gallery?com.google.android.apps.tachyonGoogle DuoYescom.sec.android.app.soundaliveSamsung soundalive?com.microsoft.skydriveMicrosoft onedriveYescom.netflix.mediaclient
com.netflix.partner.activationNetflixYescom.google.android.youtubeYoutubeYescom.google.android.videosGoogle play movies and tvYes
Enable apps to SD
In ADB shell (see above):
List disks: sm list-disks
Partition the disk to be used entirely for apps to SD: sm parition <DISK> private
Partition a percentage of the disk to be used for apps to SD: sm partition <DISK> mixed <number>
Reboot: reboot
Open the 'Settings' app and and select 'Apps'
Select an app
Tap 'Storage'
Tap 'Change' to move it to the SD card (if the app supports this)
Click to expand...
Click to collapse
I've tried enable apps to sd . I've done everything as above and all seems to work but I still can't transfer any apps to sd card .
Johnseventythree said:
I've tried enable apps to sd . I've done everything as above and all seems to work but I still can't transfer any apps to sd card .
Click to expand...
Click to collapse
Yep, same. I split the card 50/50. After a reboot, the actual card even showed as only half the size. But there was just no button at all in any app´s storage settings. And I know what to look for! Because my thine actually has that exact button. To me this looks like Samsung just flat out disabled the feature.
I just hope someone comes up with an answer to samsungs mess up as the tablet is good . Would rooting the tablet make it so I could save apps to the sd card .
I did this on my Windows laptop. ADB wouldn't recognize the tablet until I downloaded the drivers from Samsung and installed them. I hadn't had to install anything other than the Google drivers until now.
grabber5.0 said:
I did this on my Windows laptop. ADB wouldn't recognize the tablet until I downloaded the drivers from Samsung and installed them. I hadn't had to install anything other than the Google drivers until now.
Click to expand...
Click to collapse
Oh rite could you possibly post a link to the drivers please. When I open ADB it shows the serial number of my table so I just thought all was OK but maybe installing the official drivers from samsung will solve this issue . Thanks mate .
Johnseventythree said:
Oh rite could you possibly post a link to the drivers please. When I open ADB it shows the serial number of my table so I just thought all was OK but maybe installing the official drivers from samsung will solve this issue . Thanks mate .
Click to expand...
Click to collapse
Here is the link for the Samsung USB drivers: https://developer.samsung.com/mobile/android-usb-driver.html
Without the drivers, ADB does not show the device at all, so I think you're fine.
grabber5.0 said:
Here is the link for the Samsung USB drivers: https://developer.samsung.com/mobile/android-usb-driver.html
Without the drivers, ADB does not show the device at all, so I think you're fine.
Click to expand...
Click to collapse
Oh right well I've done everything it says and nothing has changed I still don't have the option to save apps to memory card . I'll try the drivers and thankyou for the link . Why samsung has done this is beyond me ..
lukyjay said:
Hi
Since no one reads this bit of the OP, let's get to it. Credit to Cloudxddd for posting the sd card fix in another thread.
Enable ADB shell
On your Tablet:
Open the settings app
Scroll down to 'About tablet'
Select 'Software information'
Continuously tap on 'Build number' over and over until at the bottom of the screen you see a toast saying "Developer mode has been enabled"
Go back to the main settings page and scroll down, select the new 'Developer options' button
Enable 'USB debugging' (press OK to confirm)
On Ubuntu:
Install ADB: sudo apt install adb
Plug your tablet into your PC via USB
Start ADB and check your device is connected: adb devices (if more than one device is listed, unplug your second android phone/tablet
You may need to approve the connection on your tablet
Run ADB shell: adb shell
Remove stock apps (bloatware)
In ADB shell (see above):
List the apps installed: pm list packages
Removing some apps will cause your tablet to brick (fixed by doing a factory reset from the recovery menu), so be careful
Search APK Mirror for the package name if you don't know what app you're looking at
To uninstall an app from your user but keep it on the device: pm uninstall -k --user 0 <packagename>
Reboot the device to ensure it can boot successfully: reboot
Reply below with the apps you removed and whether it was successful / safe
Reinstall that app: cmd package install-existing <package name> (or do a factory reset if it failed)
Completely remove the app and reclaim the space if you're certain it can be removed safely: pm uninstall <packagename>
Reboot the device to ensure it can boot successfully: reboot
Note: Some apps reinstall when you reboot.
Apps that might be safe to remove - Please reply with updates
Package nameApp nameSafe to remove?com.samsung.android.video
Samsung video playerYescom.samsung.android.app.dofviewer
com.samsung.android.app.siofviewer
Samsung live focus?
com.samsung.android.app.dressroom
Samsung wallpapers?
com.sec.android.widgetapp.webmanualSamsung user manualYescom.samsung.android.allshare.service.mediashareSamsung nearby service?com.samsung.android.app.clockpackSamsung clock style?com.google.android.apps.youtube.musicYoutube musicYescom.sec.android.app.bluetoothtestSamsung bluetooth test?
com.samsung.app.newtrimSamsung video trimmer?com.samsung.android.app.shareliveSamsung quick share?
com.samsung.android.scloudSamsung cloud?
com.samsung.android.stickercenterSamsung sticker center?
com.android.chromeGoogle chrome?com.google.android.apps.mapsGoogle maps?
com.google.android.apps.docsGoogle docs?
com.sec.android.gallery3dSamsung gallery?com.google.android.apps.tachyonGoogle DuoYescom.sec.android.app.soundaliveSamsung soundalive?com.microsoft.skydriveMicrosoft onedriveYescom.netflix.mediaclient
com.netflix.partner.activationNetflixYescom.google.android.youtubeYoutubeYescom.google.android.videosGoogle play movies and tvYes
Enable apps to SD
In ADB shell (see above):
List disks: sm list-disks
Partition the disk to be used entirely for apps to SD: sm parition <DISK> private
Partition a percentage of the disk to be used for apps to SD: sm partition <DISK> mixed <number>
Reboot: reboot
Open the 'Settings' app and and select 'Apps'
Select an app
Tap 'Storage'
Tap 'Change' to move it to the SD card (if the app supports this)
Click to expand...
Click to collapse
Brilliant! I almost quit initially but then realized you spelled partition wrong.
List disks: sm list-disks
Partition the disk to be used entirely for apps to SD: sm parition <DISK> private
Partition a percentage of the disk to be used for apps to SD: sm partition <DISK> mixed <number>
But after that it still didn’t work. But I heard Rona cheering me on. Dug into the crates of Google and found this and it worked! I used AppMgr III to move the apps. I was able to move Amazon successfully.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mydjtl said:
Brilliant! I almost quit initially but then realized you spelled partition wrong.
List disks: sm list-disks
Partition the disk to be used entirely for apps to SD: sm parition <DISK> private
Partition a percentage of the disk to be used for apps to SD: sm partition <DISK> mixed <number>
But after that it still didn’t work. But I heard Rona cheering me on. Dug into the crates of Google and found this and it worked! I used AppMgr III to move the apps. I was able to move Amazon successfully.
View attachment 5217751
Click to expand...
Click to collapse
mydjtl said:
Brilliant! I almost quit initially but then realized you spelled partition wrong.
List disks: sm list-disks
Partition the disk to be used entirely for apps to SD: sm parition <DISK> private
Partition a percentage of the disk to be used for apps to SD: sm partition <DISK> mixed <number>
But after that it still didn’t work. But I heard Rona cheering me on. Dug into the crates of Google and found this and it worked! I used AppMgr III to move the apps. I was able to move Amazon successfully.
View attachment 5217751
Click to expand...
Click to collapse
Amazing it worked flawlessly thankyou so much my daughters tablet has space again and she's not lost any of her apps . Respect to ya ....
mydjtl said:
Brilliant! I almost quit initially but then realized you spelled partition wrong.
List disks: sm list-disks
Partition the disk to be used entirely for apps to SD: sm parition <DISK> private
Partition a percentage of the disk to be used for apps to SD: sm partition <DISK> mixed <number>
But after that it still didn’t work. But I heard Rona cheering me on. Dug into the crates of Google and found this and it worked! I used AppMgr III to move the apps. I was able to move Amazon successfully.
View attachment 5217751
Click to expand...
Click to collapse
I followed these steps, and everything seems to work. Only some apps can be moved to the SD card, but that's not surprising.
However, after rebooting, Android decides that the app data is corrupted, and forces me into safe mode, from which a factory reset is the only solution.
So this only works for me if I never reset or power off the device.
Have to say, I'm never buying Samsung again. I've just had so many issues with this device. Even trivial stuff, like not being able to connect to Wifi via WPS when setting up the device (or when doing a factory reset)
After rebooting, I the tablet doesn't restart - it boots into Android Recovery, and the rescue summary shows I get NullPointerException: Attempt to invoke virtual method WindowManagerService.detectSafeMode() on a null object reference.
according to me, this method doesn't seem to work. i've got a 64gb microsd, followed the steps as indicated, after reboot the sd card shows up as "corrupted" and everytime a format is needed. unfortunately, moving apps to sd seems to be not possible. such a shame since the tab s7 can do it and this one not. hope that with android 11 update (if ever there will be) they enable this feature.
kitamurt said:
according to me, this method doesn't seem to work. i've got a 64gb microsd, followed the steps as indicated, after reboot the sd card shows up as "corrupted" and everytime a format is needed. unfortunately, moving apps to sd seems to be not possible. such a shame since the tab s7 can do it and this one not. hope that with android 11 update (if ever there will be) they enable this feature.
Click to expand...
Click to collapse
for me it works !
did you understand how adoptable storage works ??? no, then read this!
'adoptable-storage' tag wiki
Q&A for enthusiasts and power users of the Android operating system
android.stackexchange.com
i did the following and it works for me:
1. format your inserted SD-Card in the Tab A7 and dismount the SD-card after formatting
2. enable USB-debugging and connect with adb console to Tab A7
3. enter the following commands
Code:
adb shell
sm list-disks adoptable
i got the result
Code:
disk:179,32
my SD-card is 128GB size and i want 32GB (25% of total SD-Card)
for use as internal adopted storage
therefore i want 96GB (75% of total SD-Card) as external SD-card
to do this use the following commands (as adviced in posting #12)
Code:
sm set-force-adoptable true
sm partition disk:179,32 mixed 75
sm set-force-adoptable false
then i rebooted my Tab A7 and mounted the external SD-card (which shows 86,9GB)
the internal storage shows two items
1. internal storage 32GB
2. SD-Card adopted storage ( it doesnt tell you the adopted storage size but
it says 100GB used out of 128GB) which means 28GB are free for further usage,
at this point i have moved already all apps which are moveable to external storage.
i use the app "AppMgr III" as App 2 sd - utility
there are no errors or other problems after rebooting or during normal use.
it just works
hth
tiwag
tiwag said:
for me it works !
did you understand how adoptable storage works ??? no, then read this!
'adoptable-storage' tag wiki
Q&A for enthusiasts and power users of the Android operating system
android.stackexchange.com
i did the following and it works for me:
1. format your inserted SD-Card in the Tab A7 and dismount the SD-card after formatting
2. enable USB-debugging and connect with adb console to Tab A7
3. enter the following commands
Code:
adb shell
sm list-disks adoptable
i got the result
Code:
disk:179,32
my SD-card is 128GB size and i want 32GB (25% of total SD-Card)
for use as internal adopted storage
therefore i want 96GB (75% of total SD-Card) as external SD-card
to do this use the following commands (as adviced in posting #12)
Code:
sm set-force-adoptable true
sm partition disk:179,32 mixed 75
sm set-force-adoptable false
then i rebooted my Tab A7 and mounted the external SD-card (which shows 86,9GB)
the internal storage shows two items
1. internal storage 32GB
2. SD-Card adopted storage ( it doesnt tell you the adopted storage size but
it says 100GB used out of 128GB) which means 28GB are free for further usage,
at this point i have moved already all apps which are moveable to external storage.
View attachment 5261485
i use the app "AppMgr III" as App 2 sd - utility
there are no errors or other problems after rebooting or during normal use.
it just works
hth
tiwag
Click to expand...
Click to collapse
thx, found out that the sd card was not working correctly. tried with another one and worked flawlessly!
update: the method seems to be very unstable, if compared to app installed on internal memory. anytime i try to run an app, it's ok for 10-15 minutes, then suddenly blocks and reboots. this happens everytime and once rebooted, it will show that apps are not installed on ext sdcard; temporary fix when rebooted again, but it's very bothering.
FYI those methods work but are limited as you can't move certain apps or can't move their data sometimes.
If you're looking for even more space, I'd recommend App2sd (by Vicky Bonick, NOT the appMgr iii automatisation thing). You'll have to format your sd card with two partitions :
- one FAT32, that will be used as a "standard" sd card, visible by the device and all
- one F2FS, that will be used to link apps to sd card and will be invisible to most of the apps.
when asked to provide su.dpost-fs-data.d/service.d adress I used :
Code:
/data/adb/service.d
But, yes it requires root access. I'm still giving it a try but so far this is the only method that I've managed to move stuff like Genshin impact and its 8GB of data that somewhat disappear into thin air using other methods.
EDIT : after messing around for a few hours. This method is still not perfect ... I have troubles moving some obb files with it. But it's still worth a shot
tiwag said:
for me it works !
there are no errors or other problems after rebooting or during normal use.
it just works
hth
tiwag
Click to expand...
Click to collapse
Thanks, followed your guide and initially it worked correctly.
I also rebooted the table and it still worked.
However now (after a shutdown) the SD card is recognized as corrupt / damaged (translated).
It is still part of the adoptable storage.
I earlier reported it didn't work anymore after a reboot.
However checking a few days later it works again.
I guess it ran out of battery and rebooted.....
Thanks.
It works great on my SM-T500. I was able to use my 64GB SD Card as Device Storage. I was able to move Asphalt 8 game from Internal Storage to SD Card
I need to debloat my newly purchased Redmi Note 11 Pro+.
Care to assist regarding requirements:
1. Windows 64bit ONLY........CORRECT?
2. ADB drivers.
3. https://github.com/Szaki/XiaomiADBFastbootTools Szaki Xiaomi ADB fast tools.
4. Do I require this..... https://adoptium.net/?variant=openjdk14 looks its for 32 bit?
5. Phone in developer mode.....android debug enabled.
In which order should I install?
Hoping to hear from you experts.
Thanks.
You can debloat any device with adb for this you need a computer and your device with usb debugging enabled. First install package name viewer from play store and select your app which you want to delete. You will get a com.this.type string you have to remember it. Now you have to open your computer and write these commands
adb devices(Allow any requests on your device (
adb shell
pm uninstall -k --user 0 com.your.package
You have uninstalled the system bloat!
In this guide we will see step by step how to debloat the Galaxy Tab S8
First of all we have to enable: Developer Options
Settings->About tablet->Software information->(tap 7 times)Build number
After that we will enable: OEM Unlocking & USB Debbuging
Settings->Developer Options->OEM Unlocking(ON) & USB Debbuging(ON)
On the next step we need to download & install : ADB & Fastboot tools
Once you install the tools, connect your {Tablet} - {PC}
Select: USB Debbuging & Open your: Terminal
We are almost there
Now i will make a short explanation in order to understand what are we doing exactly & how we will do it.
What is ADB?
ADB provides us with commands that can be used to debug Android devices,
installing or uninstalling apps and getting information about a connected device.
adb shell
This command activates the remote shell command console on the connected Android smartphone or tablet.
adb shell pm uninstall -k --user 0
Using this, you can easily uninstall the unwanted system apps. To be able to execute it, you must issue 'adb shell' command first.
You can then use 'pm uninstall -k --user 0' followed by the Android app package name as shown below.
pm uninstall -k --user 0 com.whatsapp_2.20.apk
This command can help you if you want to remove all the bloatware from your phone.
Please note that most system apps don't have the 'Uninstall' option on the device but this command works magically.
If you don't know the app package name for the apps you want to remove, you can use adb shell pm list packages to find it out.
adb shell pm list packages
Using the above ADB Shell command, you can print the list of the app package names for all apps installed on your Android device.
You can use this command with different parameters to get a more specific list of app packages.
For instance, if you want to list the system apps only, use
adb shell pm list packages -s
In order to list all third-party apps installed on your Android phone or tablet, you issue the following command.
adb shell pm list packages -3
Do you want ADB Shell to show the list of all enabled or disabled apps on your device,
try the command with '-d' (disabled apps) and '-e' (for enabled apps) parameter.
adb shell pm list packages -d
adb shell pm list packages -e
Now, if pm list command troubles you or you are unsure that you are making the right choice you should stop right there
(uninstalling the wrong app might harm your tablet's operating system) and use another method for identifying which app you want to uninstall.
(GUI method - Graphical User Interface) For example: APK Inspector will provide you with a detailed list of installed packages (plus their icon) on your device, once you select an app, extra details will be shown to you & that's how you will get the correct name.of.the.app
Thanks for your time ❤
Reserved
I really appreciate this write-up it has been a big help..
I use my OnePlus 9 pro with ADB and fastboot for Android NDK to debloat..
and that application inspector is a God send so again. thank you
I don't know if it was just a fluke or what but when I rebooted after successfully deleting digital well-being my tablet booted up super fast...
either way I'm good.
Awesome thanks for the tip. Is using "install" put the app back if I screw up something?
So it really doesn't uninstall just uninstalls from your app draw?
striker59 said:
So it really doesn't uninstall just uninstalls from your app draw?
Click to expand...
Click to collapse
For the os, it is like it has been uninstalled. But you don't free disk space, as the data of the app are still there. They just been hidden from os. That's why you can have back the app again just with an adb command again.
Man I used this to shut down numerous apps on all of my Android devices. Samsung and Verizon apps. Thanks!
Went back in to uninstall more apps. Device is recognized but adb shell won't load. The last time I used adb it was for my phone.
Figured it out, had to revoke USB debugging on my tablet. Delete on the computer c:user.android and restart (actual path on the computer could be different than what I stated).
Hi there.
Can anyone confirm, if it is save to remove the phone app from the device since it is connected to this samsung feature "calls/ messages on other Galaxy devices"? Actually i fully wanne get rid of this feature and app since i don´t use a galaxy phone.
Can someone share experiences/ideas according this topic?
Stogie87 said:
Hi there.
Can anyone confirm, if it is save to remove the phone app from the device since it is connected to this samsung feature "calls/ messages on other Galaxy devices"? Actually i fully wanne get rid of this feature and app since i don´t use a galaxy phone.
Can someone share experiences/ideas according this topic?
Click to expand...
Click to collapse
I have Debloated it (adb frozen) months ago. Didn't have any problem. You can always enable it again.
Am I right? If i debloat I don't clean up the system space used from the os ?
nofear5888 said:
Am I right? If i debloat I don't clean up the system space used from the os ?
Click to expand...
Click to collapse
You won't earn more free space. Apps are still there after Debloating.
sosimple said:
For the os, it is like it has been uninstalled. But you don't free disk space, as the data of the app are still there. They just been hidden from os. That's why you can have back the app again just with an adb command again.
Click to expand...
Click to collapse
@striker59
You remove the app for the current user but its still inside system's root directory.
You don't gain storage.
What you can achieve tho if you remove/disable the unnecessary services without causing softbrik or error spamming 'service has stop working' is a lightweight $user who uses less ram, your phone's overall performance is better and the battery reduction is slower.