Solution to application loss in a2sd + state

Http://bbs.gfan.com/android-213772-1-1.html

Using the a2sd + and SD partition schemes Friend The a2sd + may suddenly become invalid after a certain boot, and several losses may occur at the same time. ApplicationProgram Symptoms or installation Software Insufficient space.
In this case, an error occurs in the ext partition of the SD memory card. After the error is fixed, you can re-enable a2sd + and retrieve the original application.

Like restoring the FAT partition, this can be done through fsck. Run the command to change from fsck_msdos to fsck.
However, if you use the fix SD: ext option in the recovery version, you can directly select the fix in the recovery version.

Restart after repair Mobile phone , A2sd + can be re-enabled, the space is no longer insufficient, and the lost program can also be retrieved.

Note the following operations that may easily cause this problem:
1. It is recommended that you shut down the machine after it is turned on (no matter what package or patch you have, or whether it is wipe). Without this operation, it is easy to cause installation of software. System An error occurred while restarting the ext partition.
2. Do not be superstitious about the fast restart of various restart Software Function To fully store installed software and other data, it is best to use the Shutdown option instead of restarting quickly. It is a good habit to use the quick restart only when you know what you are doing.
3. When you need to remove the memory card, wait patiently for the system to shut down normally.Battery Pull the card, after the black screen is still waiting for about 5-8 seconds, although the black screen, but this time the shutdown operation has not been completed, the trade rashly unplug the battery is easy to cause ext damage.

Recovery

1. Reboot system now -- restart

2. USB-MS toggle-Connect USB directly in recovery mode without exiting this mode

3. Backup/restore -- Backup and Restore
3-1. NAND backup -- NAND backup
3-2, Nand + ext backup -- NAND backup (the system is backed up together with the ext partition)
3-3. NAND restore -- restore (that is, restore the last backup of 3-1 and 3-2)
3-4. Bart backup -- Bart backup (including system and ext partitions)
3-5. Bart restore -- restore the last Bart backup
NAND backup is similar to system backup, while Bart is like a ghost backup on a PC.
NAND backup does not back up ext partitions (that is, if the second partition is not partitioned, ignore this)
if your app2sd program is installed in the second partition, you cannot use NAND to restore it.
bar t can be backed up to the ext partition and restored with Bart. The whole system can be restored so that it is exactly the same as before the backup, there will be no loss of file information (including contacts, text messages, images, audio and video, etc. If you have many items installed, backup and recovery will be slow)

 

4. Flash zip from sdcard--from The. Zip Rom in the SDK root directory

 

5. Wipe -- clear
5-1. Wipe data/factory reset -- clear memory data and cache data
5-2. Wipe Dalvik-Cache -- clear cache data + data in ext partition
5-3, wipe SD: ext partition -- only clear data in the ext partition
5-4, wipe battery stats -- clear battery data
5-5, wipe rotate settings -- clear the data set in the Sensor

6. Partition sdcard -- partition SD card
6-1. Partition SD -- automatically partitions the SD card.
6-2. Repair SD: EXT -- fix ext partition
6-3, SD: ext2 to ext3 -- convert ext2 to ext3 (recommended)
6-4, SD: ext3 to ext4 -- convert ext3 partition to ext4 partition (not recommended for C4 card, c6 card recommended)

7. Other -- others
7-1. Fix APK uid mismatches -- fix the APK Program
7-2. Move apps + Dalv to SD -- move programs and virtual caches to the SD card (this is not app2sd)
7-3. Move recovery. log to SD-move the fl log file to the SD card
(After this operation is performed, a "recovery. log" file will appear in the root directory of the SD card, that is, the fl log file)

8. Power Off-Shutdown