Guys, this is just happened.. I backup my stock ROM with Full Backup with TAR format and External SD as location, when I wanna take a look the MicroSD in my PC (run on linux), the contents of clockwordmod folder is bunch of files with strange symbol name..? errors..?
{
"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"
}
I can't delete it in any OS because of that name symbols. Any solution..?
Motorola RAZR MAXX (XT910 GSM), BMM 0.3.4, ICS 4.0.4 (Stock), Liquid Smooth 4.2.2 (3rd slot)
tridentcore said:
Guys, this is just happened.. I backup my stock ROM with Full Backup with TAR format and External SD as location, when I wanna take a look the MicroSD in my PC (run on linux), the contents of clockwordmod folder is bunch of files with strange symbol name..? errors..?
I can't delete it in any OS because of that name symbols. Any solution..?
Click to expand...
Click to collapse
chkdsk may be of help. UNIX tools (Linux. MacOS X etc.) such as dosfsck aka fsck.vfat are usually unable to fix badly corrupted FAT. However, the best solution would be to format the card (which will reinitialise the FAT) and restore data from backup.
Vatazhka said:
chkdsk may be of help. UNIX tools (Linux. MacOS X etc.) such as dosfsck aka fsck.vfat are usually unable to fix badly corrupted FAT. However, the best solution would be to format the card (which will reinitialise the FAT) and restore data from backup.
Click to expand...
Click to collapse
Before this, already happened once and I tought is there's a problem with my MicroSD filesystem and after that I backup all of my data and do full format overwrite using Linux Mint and copy all of my data back to MicroSD. And this time happened again.
Any chance my MicroSD got hardware errors..?
You can check kernel log after you test your card e.g. by issuing the following command: dd if=/dev/block/mmcblk1 of=/dev/null bs=128k (it's a read-only test, superuser is required).
Did you notice any sudden reboots? Is your device overclocked and/or undervolted? These can contribute to data loss.
Vatazhka said:
You can check kernel log after you test your card e.g. by issuing the following command: dd if=/dev/block/mmcblk1 of=/dev/null bs=128k (it's a read-only test, superuser is required).
Did you notice any sudden reboots? Is your device overclocked and/or undervolted? These can contribute to data loss.
Click to expand...
Click to collapse
nope, everything is still default stock ROM with most of system apps freezed.. no sudden behavior or anything, everything is work fine in my stock ROM except the BMM Full Backup result in the screenshot above... I wanna try to buy another MicroSD as backup storage in case the one I'm using is defected.
Related
{
"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"
}
^^That's what's at the root of my gtab's /sdcard.
Also, there used to be two folders in that that I had created and are no longer there.
Here's what I was doing immediately before I noticed this:
I'm currently using TnT Lite. I need to be able to access wifi at work but my company uses EAP encryption and TnT doesn't have a setting for EAP. I decided that rather than switching roms, I would just switch settings menus (using the files found here: http://forum.xda-developers.com/showthread.php?t=857939).
Stupid me, I downloaded them to /sdcard2 rather than /sdcard. I booted into clockworkmod and tried to install the zip from the sdcard but clockworkmod couldn't find anything. I realized my mistake and rebooted the gtab and hooked up the usb to my pc. That's when I noticed the file corruption.
Everything still seems to work as it did before, I just don't have access to any of the files that were in those folders.
In case it matters, one folder held the TnT Lite rom and the other held several videos.
Does anyone have any idea what could have caused this?
Should I try to delete the corrupted files?
Any help with this is much appreciated.
I don't claim to know why this happens this is just what I did to fix my problem.
I noticed this on my gtab also, to the point my cal program wouldn't open. The only way I could fix it was to do an sd partition to it fix the issue. There are instructions on how to do that with cm8. This is from memory so please double check, go to the advanced options choose sd partition 2048/0. Please note that this wipes the sd card so back up prior.
I still get a few of those weird files buy not like before.
same thing happened to me but hasn't come back after
re-partitioning with cwm ... maybe that is the fix
I would *really* like to know why this happens (that and why
the sdcard2 gets wiped out sometimes).
Basically, you dare not trust android with any important data
and you never know if what's on it will disappear suddenly
Unfortunately, this makes the tablet just a toy
So is the best option really just to re-partition the sd card?
If I end up re-partitioning, will I have to flash the ROM over again? Or does partitioning just remove the user data?
Quote: will I have to flash the ROM over again?
No
Going to sell my DNA but I want to wipe it. I am first going to do the traditional wipe and re-install the ROM. Then I want to clean off the SD card. I have TWRP. If I do a wipe of just the internal sd card will it keep my system untouched so I can boot into the ROM?
Connect the phone to PC, delete all files on the phone, place stock ROM onto the phone, boot to recovery do a full wipe (system,data,cache,dalvik) The ROM should still be in data/media. Flash it, reboot,connect to PC, delete ROM file and don't run setup.
There may be a better way but as far as I know the internal card contents won't wipe unless you explicitly choose it. If you can do that from recovery then that will work.
Wipe as normal, flash ROM, then in advanced wipe choose internal storage, swipe to wipe, done. Fresh ROM and no SD card contents.
{
"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"
}
Tapatalked from my HTC DNA - Carbon
I have'nt sold a phone in awhile but if there's any photos you don't wnat out I'd look into a way to overwrite the contents of the internal storage as well.
fr4nk1yn said:
I have'nt sold a phone in awhile but if there's any photos you don't wnat out I'd look into a way to overwrite the contents of the internal storage as well.
Click to expand...
Click to collapse
I have a script for that, it uses dd and writes over the entire data partition with zeroes. Takes forever, but literally zeroes out the SD card and the rest of data, so even apps or app data are gone.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
I have a script for that, it uses dd and writes over the entire data partition with zeroes. Takes forever, but literally zeroes out the SD card and the rest of data, so even apps or app data are gone.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
I wouldn't mind using your script.
I don't know where I inspired to do this but it is most efficent way to backup and restore opinion.
Sometimes backuping and restoring partitions like /system /data etc. messing up the device. This method bootup normally all the time after restoring.
krezee:
Complete and foolproof bkp step. Ignoring possibility of typo.
Ability to recover completely as long as recovery is working
Yes thats right so be careful when typing!
You need 16 GB or 32 GB USB memory (formatted with exfat) and OTG CABLE
16 GB or 32 GB depends on memory size which you are using.
Begin with %100 battery every time you backup and restore
because using the OTG takes a lot of power and this process takes 30-40 minutes or more.
Backup Process
Connect your USB memory with OTG cable type it in Terminal emulator
Code:
su
Code:
dd if=/dev/block/mmcblk0 of=/mnt/media_rw/USBstorage1/mmcblk0 bs=4k
Optionally you can turn on flight mode while backupping
If process finished terminal emulator looks like this:
{
"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"
}
Restore Process
1. Connect the OTG cable
2. Boot up to the TWRP recovery
3. Check OTG and /system mounted or not (if not Reboot > Recovery then check again)
4. Advanced > Terminal Command
5. While in root folder " / " press select
6. type:
Code:
dd if=/usb_otg/mmcblk0 of=/dev/block/mmcblk0 bs=4k
It will takes some time and sometimes TWRP lockscreen blinks, locks over and over again. Sometimes you can't unlock lockscreen because it is 5 times locked(or more) It is ok. Leave the phone and check after 20 min.
After process done boot up
Q: Why it is useful so much?
A: This process backup all your partitions in ONE partition --> mmcblk0 and one file.
Q: Can I use for IMEI lost problems
A: Definitely yes.
Q: I will try another rom but what if I don't like?
A: Take a backup like that install your rom and you don't like it restore your backup without messing your phone!
Also HDD/SSD can be used. With external box or usb converter for sure.
Yes you can I would prefer SSD, HDD sounds like power drainer.
In addition you have to format it exfat your SSD or HDD I think, if not device cannot mount the drive.
Edit: You can use mini partition tool to partition and create a partition ext4 and backup in there. Now it doesn't take so long with bs=4k you can use that method with external hdd or maybe ssd.
Complete and foolproof bkp step. Ignoring possibility of typo.
Ability to recover completely as long as recovery is working
Thanks
krezee said:
Complete and foolproof bkp step. Ignoring possibility of typo.
Ability to recover completely as long as recovery is working
Thanks
Click to expand...
Click to collapse
Very important point yes if recovery not working you can't restore
And typo may cause memory full error when recovery process is running
Checking file size can be useful (16 gb or 32 gb when its done)
Thanks for your attention I added to thread.
Hi, I have mate 10 lite: RNE-L21C185B142 with Nougat
I have flashed various TWRP files to get a full backup, but all fail at data, check the following screenshot
createTarkFork() process ended with ERROR: 255
{
"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"
}
I have used an external hard drive as the OTG storage when I tried backup, and also tried another time
with a 32 GB SD card but both show same error at same point. There is no addon.d in my system folder
and also I have tried with enabling/disabling compression when taking backup. And I did unchecked data partition
from Mount in TWRP.
When I go to reboot it shows another error at the end of above screenshot in red color:
E:Error making /data/app/me.twrp.twrpapp-1 directory: permission denied
I have attached both recovery logs. Please suggest what shall I do
It's because of encrypted data, you have to untick data
It also happened to me. It was the twin app's fault. I deactivated it and now it does not give me this error.
gmbengue said:
It's because of encrypted data, you have to untick data
Click to expand...
Click to collapse
Tried with it already, didnt work
ernia66 said:
It also happened to me. It was the twin app's fault. I deactivated it and now it does not give me this error.
Click to expand...
Click to collapse
I dont have any twin app turned on (all apps showing in Twin App are off)
plz help guys
Answer already given... It's because of encrypted data...
For details you can look at this post...
https://forum.xda-developers.com/showpost.php?p=75052881&postcount=340
Remember... Make always a backup of your important datas from internal storage to an external SD Card or to your PC
balthasar said:
Answer already given... It's because of encrypted data...
For details you can look at this post...
https://forum.xda-developers.com/showpost.php?p=75052881&postcount=340
Remember... Make always a backup of your important datas from internal storage to an external SD Card or to your PC
Click to expand...
Click to collapse
The link you posted, I went to full post and got good answers there, thanks bro
Hi there.
I have a Galaxy A50 (SM-A505FN) with 128GB. I rooted it with magisk (original firmware from sammobile (link below), modified on unrooted phone with magisk manager, flashed through download mode and odin).
The issue is that the phone now says it only has 16GB of storage.
Conneced to my PC it also only finds 16GB of internal storage.
I added a picture of what the terminal says the partitions are.
{
"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"
}
I read about correcting partitions with twrp but since i dont have that i want to ask if there is another way to fix this.
Thanks!
www sammobile com/samsung/galaxy-a50/firmware/SM-A505FN/DBT/download/A505FNXXU3ASL6/309345/
i can only see 10 GB on your screenshot. check one of the following
Code:
cat /proc/mtd
cat /proc/partitions
cat /proc/dumchar_info
you can download parted binary and check
Code:
parted /dev/block/sda print
note that the 6263-3234 block in the first screenshot is the sd card. i dont have it encrypted so im wondering why it seems to be mirrored in the /mnt/secure/asec block. i did however click the 'copy files from sd card' when it popped up i believe. but even if that did something, it could only block 64 of my 128 gb.
displaying partitions worked, heres the result:
i see that sda shows the 128gb capacity and sda32 seems to be whats is usable for the phone after taking out all the neccessary partitions.
unfortunately i don't know how knox works, all i can see is /data is not mounted, maybe knox prevents
try to uninstall KNOX with su -c pm disable com.sec.knox.seandroid or something
@mirfatif same problem here, must be something new. i have never seen before. maybe permission problem with magisk or some sort of disk quota
data is mounted /sbin/.magisk/mirror/data
(or /sbin/.magisk/block/data)
aIecxs said:
@mirfatif same problem here, must be something new. i have never seen before. maybe permission problem with magisk or some sort of disk quota
data is mounted /sbin/.magisk/mirror/data
(or /sbin/.magisk/block/data)
Click to expand...
Click to collapse
No idea. Can't conclude anything unless OP performs some troubleshooting steps. Whatever the case is, "/data" must be a mount point. May be something to do with SELinux, or mount namesapce, or new Magisk changes for Android 10. I'm using old Magisk release on Android 9. So may be missing something new.