A factory reset reformats the phone's user-data partition, but it's not a "secure" wipe; it doesn't overwrite everything with zeroes. If you want to be sure everything is erased, you can encrypt the phone first (which overwrites all the data with encrypted versions of itself), then do a factory reset (which sets up a new unencrypted filesystem).
It seems like manufacturers are removing the "Format as Internal" feature on newer phones. Perhaps because it's in their interest to force us to upgrade our devices after running into memory frustrations.
So after a long and frustrating process, this eventually method worked for me. I had to make two alterations:
I used the MTK ADB driver instead of the ...
Android supports fstrim but it only works if the phone is idle for a long time while charging
It's not so. On newer versions, Android runs fstrim with a daily schedule, provided that the conditions meet. Or it should run on a reboot if not run for 3+ days. See this answer for details and how you can run fstrim manually.
FRAGMENTATION ON FLASH MEMORY:
Try doing what it suggests... run e2fsck -b 8193 /dev/block/platform/msm_sdcc.1/by-name/userdata. If that doesn't work, try running mke2fs /dev/block/platform/msm_sdcc.1/by-name/userdata.
You can also boot into fastboot mode and run fastboot erase userdata.
If none of these work, please elaborate on this "long story". How did you mess up your data ...
Related question: How to detect filesystem type of un-mounted partition?
Just to complete some missing pieces:
Usually we use mount command to see mounted filesystems, it works without root e.g. from a terminal emulator app or adb shell:
/dev/block/sda1 on /mnt/media_rw/C8BA-D0E2 type sdfat ...
/dev/block/sda2 on /mnt/media_rw/C78E-434F type ...
The Nokia 6.1 has a reported issue with using SD card as internal storage,
detailed on the XDA Forum.
The ability to use an sdcard as internal storage is avaiable with build 00WW_3_206_SP01
However, users have found files put on to the sdcard get corrupted at random 4096-byte boundaries.
In terms of options open to you, Google Play does ...
Honestly speaking, It depends on the manufacturer. As far as I am aware, the company has to get some license from Microsoft to include NTFS support. Speaking from experience, most (high-end) Samsung and HTC phones do while custom roms typically do not.
The only sure-shot method to confirm is by trying it out with an extra sd card...
TL;DR: Every Android uses FAT32. The Cluster size depends on the release. Existing partitions will be preserved. It will always use quick format.
After some more research here is the process as it was coded in the Android source code:
The Setting App displays a few confirmations then uses the Intent: Intent(ExternalStorageFormatter.FORMAT_ONLY)...
That very much depends on the type of backup you are talking about. As the photo was deleted, none of the usual backup approaches would cover it: a backup only takes what is there, not was was deleted.
How to recover that photo (if possible) depends not at last on where it was stored:
external SDCard: safely remove it from the device, and use a card reader ...
NO. Unless you perform a backup before, you lose all app data during a Factory Reset.
A factory reset or master reset is a full restore of an electronic device to its factory settings. Such electronic devices include handheld computers such as PDAs and mobile phones. It entails deleting all information stored in the device. This is essentially ...
The reason is, at least with Samsung devices and cards larger than 32GB, Samsung or Android formats the card with the exFAT file system, but incorrectly identifies the partition type as "FAT32 (LBA)", or partition type "c" or "0c" in the card's partition table.
If you format the card with exFAT using Windows or the Android partitioning app Aparted, it will ...
Easy solution for anybody with a card-reader in their pc. (Relaid from: forum.xda-developers.com/)
Place the card in your PC's card reader and determine the drive designation (i.e., G:\, H:\, etc.)
Download the fat32format utility in GUI version from here: http://www.ridgecrop.demon.co.uk/guiformat.exe. Click on the picture to retrieve the file.
Launch the ...
No. Internally formatted external sd card is not included in mmcblk0. dd dumps files, in your case the block device file mmcblk0 which includes all partitions, GUID partition table (GPT) and any free space in between partitions.
External SD card is a separate flash memory chip, so exposed by a different block device available at path something like /dev/...
A few points on four partitions:
Dedicated first partition exFAT or NTFS or FAT32 (whichever Android permits and gives optimum performance) to store apps, photos and media.
For apps consider Application Class but that's expensive. Others will exert performance penalty more or less. On filesystem selection, the biggest downside with FAT32 is its 4GB ...
If it's just the APK files, you could use the getapk script provided in the tools/ directory of my little helper Adebar, calling it e.g. with getapk user to retrieve all user-installed apps. You won't be interested in system apps, but for completeness:
Extracting APK files from a connected device.
getapk lets you extract a single app's APK, ...
As well as being in the right format, there are two types of SDXC cards. For devices that say that cards above 32gb may not be supported, they only support the V2 Sd card, and devices that say they support above 32gb, the take both v2 and v3. V1 is now redundant.
The Solution: Thanks to the guys on This Thread I figured it out. I also used the same tool they described, Minitool Partition Wizard, though I'm sure you could use any partition tool.
In windows on an SDXC card you can only format in ExFAT and NTFS. With a third party tool, you can make the card a FAT partition. Once you do this, the card is recognized in ...
This limitation is not due to the FAT filesystem : Since 4.4, Android only lets a special user group write on the card.
Your card could be in NTFS, or EXT or whatever more, you'll have the same problem.
The only way to bypass this limitation is to root your device, and install some 3rd party apps/patchs, or manuallay edit some files.
Firstly, some background
Anti Virus. Android devices are not susceptible to viruses as Windows machines are. To understand more see this Is an antivirus really needed for Android?. So, installing anti virus is not helping any, unless it scans for malware also
Malware. Malware in Android devices works by losing itself into /system ,i.e., behaving as if it is ...
Things you can do:
Downgrade to your stock ROM and install a good antivirus and run a complete device scan because some of them are powerful enough to remove viruses from system files in priveledged user mode.
Install Ubuntu Touch instead of android as shown in this guide. The guide is actually primarily for nexus devices but you can make it work for Galaxy ...
I've already found an similar issue: SD card supported by Android 4.2.2
Here you would find this answer:
I have looked into this issue before, and as it stands at the moment,
native android does not support exFAT or NTFS.
Support for additional formatting types are included in some ROMs
because they have been specifically coded to do so such as ...
CWM is long dead, let it stay that way.
You are advised to use the latest TWRP recovery, which has an interactive graphic interface, has a more powerful and thorough wipe function, and has an inbuilt file explorer so that you could just look inside /system to see if the wipe indeed worked (don't forget to mount /system before looking in, though).
First, for reinstalling you'll need a ROM specifically matching your device (there's no such thing as a "generic installer" for Android, see e.g. Can I install a ROM made for a different device and Why are there not generic phone OS installers?)
Second, for a "clean start", it is possible to "wipe" all mentioned partitions – but usually not with the stock ...
We all know that the matter concerning bricking a device is complex and often confusing, so let's make some clearance.
Meaning of bricking
Bricking, if considered literally, means "to have a device so unusable it could be a brick". This, on mobile devices, is an umbrella term for two different things:
soft brick: as a result of flashing or ...