I'm running unlocked stock 183.46.10. The file system for my data partition is F2FS, and I believe it should be EXT4. I found this out by trying to install Bliss, and not getting past the boot animation screen. The suggested "fix" is to change data file system to EXT4.
Do custom recoveries "remember" the file system that was backed up? If I back up my system and then change file systems, when I go to restore, do I need to revert back to my original file system?
[EDIT] I answered my own question - TWRP does "remember" the original file system backed up, and will issue a warning that the restored system may not boot if you are restoring using a different file system. I went ahead and restored my backed up system, but now, my data partition is using EXT4 instead of F2FS. So far, all seems to work OK.
Related
Hi all,
I have a nexus 7 running Android 4.1.2 stock w/ root. Some months ago, I disabled the OTA update notification - but I can't seem to remember how!
I want to now re-enable OTA updates so that I can update to the latest android version, and not lose my installed apps.
I've searched the device for FOTAKill.apk inside /system/app, and its not found
I've also searched for frozen / hidden apps using Titanium Backup Pro... nothing
When I enter Settings -> About Tablet -> System Updates... it says I'm up to date... but I'm not, considering I'm running 4.1.2.
Any help or pointers in re-enabling OTA is appreciated!!
- make a full nandroid backup.
- using fastboot, flash the system.img file from the 4.2.2 factory image to the system partition.
- using your custom recovery, reflash a SuperSU root kit bundle.
- using the custom recovery, wipe cache and dalvik-cache.
If you don't like the result, restore the nandroid backup and proceed in a different fashion. It will probably break things like stickmount and any other changes that you caused in /system.
Note the above method is for use by lazy and sloppy users. A better approach is to make TiBu backups of only your market apps, bite the bullet, and start from scratch with a flash & (new) configuration of a pure stock ROM. In any case, every conceivable procedure should start with making a full nandroid backup and getting it copied to a safe place off the tablet.
I will also say that unless odd problems crop up, the portions of the factory install procedure (using fastboot) that deal with erasure or flashing of the userdata partition should be skipped, as these steps completely wipe your /data storage - including your /sdcard area in /data/media/0 and any CWM/TWRP nandroid backups!
It's not really clear why these steps would be needed unless the /data ext4 filesystem in the userdata partition got corrupted somehow. A more sly approach would be to use the custom recovery's "factory reset" procedure to clean up /data - either before or after flashing the factory ROM - and completely skip anything that touches the userdata partition in the factory install instructions.
good luck
I found my data and cache partition corrupted, and i dont know why.
I don't know anyway to fix it but do SBF flash (so far I am doing the THIRD SBF flash today, really frustrating)
[edit] why i think data and cache partition corrupted:
1. I couldn't mount data and cache and psd partition in recovery, but i can mount sdcard (and can't unmount system partition, is it supposed that system can't be unmounted?)
2. when i booted up the system(Kayant's AOKP), the size of internal memory is 0.0B, as shown in the settings->storage
[/edit]
Is there any to fix without doing SBF flash?
another question:
How to prevent it/any precaution so that the partition wont mess up? (I probably did some wrong thats why the partition was messed up, but I have no idea what I had done wrong)
here is what i did:
I had had this problem before so I do a SBF flash and the problem is gone.(I installed Kayant's AOKP rom -4.1jb)
Yesterday I decided to flash another rom (that was Quarx's cm10.1 rom) i did a nandroid backup first, then installed the rom and installed some apps, after that I installed Kayant's Slim rom(from the new aokp paradise), i found some bug and at last decide to return to Kayant's AOKP rom. I installed the 2nd Init boot menu(coz i did the nandroid backup with CWMrecovery, not TWRP), and problems came while restoring it. It failed to restore /data partition, I tried more times but couldn't fix this. So at last I turned to SBF flashing.
I flashed and rooted it with SuperOneClick and installed 2nd Init boot menu then install the AOKP rom(didn't restore the nandroid this time) then factory reset-ed it with stock recovery, and I found the /data and /cache partition messed up again(obviously the partition isn't messed up right after SBF flashing because i can install the 2nd Init app).
Now I am doing the third SBF flash.
You shouldn't have formatted data and cache with stock recovery. That was a mistake in your second attempt.
hotdog125 said:
You shouldn't have formatted data and cache with stock recovery. That was a mistake in your second attempt.
Click to expand...
Click to collapse
should I use aroma wiper and do a ext4 wipe if i am going to flash jb roms (like cm10/android 4.1 or higher), to prevent messing it up?
is it necessary to do wipe before or after install a new rom?
besides, any idea why the partition messed up/ failed to restore data when i do a nandroid restore, when i tried to restore with cwm recovery within 2nd Init boot menu installed on Kayant's Slim rom?
dicksonlok said:
besides, any idea why the partition messed up/ failed to restore data when i do a nandroid restore, when i tried to restore with cwm recovery within 2nd Init boot menu installed on Kayant's Slim rom?
Click to expand...
Click to collapse
Yes, format to ext4 for JB ROMs. Full wipe not necessary but recommended.
Start afresh, install the ROM and restore data.
Plus, you shouldn't have installed 2ndinit again. You should have installed dual recovery and tried.
Got same problem, data and cache partition corrupted.
Fortunately I have TWRP installed so I went to File System utility and format data and cache (I choose ext3).
Then restored previous backup and everything worked like before!
Hi. I accidentaly changed file system of data partition to EXT4 and now when I try to restore my backup I get a warning that the backup was done with f2fs file system. The problem is that TWRP is not showing up the f2fs option when I go to change file system menu. Any help?
Thanks!
I think you can restore the data anyway? I backed up my ext4 data partition, formatted it as f2fs and then restored the backup and it gave me the warning but it worked anyway. If it doesn't let you proceed, reflash TWRP and try again.
hernaner28 said:
Hi. I accidentaly changed file system of data partition to EXT4 and now when I try to restore my backup I get a warning that the backup was done with f2fs file system. The problem is that TWRP is not showing up the f2fs option when I go to change file system menu. Any help?
Thanks!
Click to expand...
Click to collapse
What ROM are you trying to restore, may I ask?
jeshanp said:
I think you can restore the data anyway? I backed up my ext4 data partition, formatted it as f2fs and then restored the backup and it gave me the warning but it worked anyway. If it doesn't let you proceed, reflash TWRP and try again.
Click to expand...
Click to collapse
Yes i could restore it but it worries me that I can't keep the original stock filesystem. I never changed it and I would like to have it as it was, there must be a reason it is f2fs and not ext4.
corlatemanuel said:
What ROM are you trying to restore, may I ask?
Click to expand...
Click to collapse
It is a stock backup.
Thanks for your replies.
I seem to have a damaged data partition on my Nook HD. All attempts to wipe, restore or write to the partition are unsuccessful using multiple TWRP versions and CWM. Attempts to flash ROMs, including all stock ROMs are unsuccessful. Once in a while I see a warning: "This /data backup was made with ext4 file system! The backup may not boot unless you change back to ext4." (Yes, that's ext4 x 2, but restoring usually just exits on an error).
Does anyone know a way to reformat or otherwise repair my /data partition?
Thank you.
Hello guys,
I had Lineage OS installed on my Galaxy S10+ and it got into boot loop after my phone lost power a few times because of low battery. The system halts at the Lineage Logo animating forever.
The problem is I canont access encrypted files on /data partition as it seems default Samsung encryption is used (and I have not disabled encryption when I was installing Linaage - I know - my mistake...) What I'm thinking to do is to do a dirty flash of the same system or an upgrade.
But before I will do it, I would like to do full backup of /data partition - sector by sector, so if my dirty flash won't work I can restore /data partition again and try to fix it again without loosing my data.
So my question is: How can I backup whole /data partition as an image? And how can I restore it?
My system is going into boot-loop, but I can get into recovery.
Thank you very much!!!
Encryption keys not withstanding it's the user partition that's likely been corrupted. You see where I'm going with this?
You try safe mode?