Related
It looks like /data/cache is mainly used by Market for storing downloads. Quite a bit of space can be taken up there. And it looks like one can just relocate that to storage (with root);
Code:
su
mkdir /storage/cache
cd /data
rm -rf cache
ln -s /mnt/storage/cache /data/cache
/data/cache won't be available for any apps that need it directly on boot, and those apps may crash, but I haven't noticed anything like that happening on my A43.
As usual with such tricks, use at your own risk and make a backup.
If you don't understand what this Modification is doing, why it needs to be done, or what possible benefits come from it, then...
PLEASE DO NOT TRY THIS MOD.
***Even tho it is impossible to brick your phone when flashing this i still highly recommend you UNDERSTAND what you are attempting to do before you do it. If someone explains you are freeing up internal memory from other places not using it and you still have to ask what the benefit is, then you obvisouly dont fully understand the mod and your phone and should turn away now.***
Thank You.
Now onto the mod: Heres a quick description of what this mod is doing. Pretend your phone is a pizza cut into 3 even pieces. Each piece is memory for /cache, /system, /data. Your anorexic sister "aka cache" doesn't eat a lot so most of her slice will always be left, your fat obese brother "/data" always eats his whole slice and is left wanting more. You are healthy "/system" and only eat what you need and never less never more.
What this mod is doing is taking that original pizza and RE-CUTTING the slices to better fit whose eating them, so since your anorexic sister barely eats and your obese brother is always hungry it takes all the extra pizza "aka memory" from your sister and gives it to your brother. As for you "aka /system" you only eat exactly what you need "aka the size of the rom and files it install" so it resizes your own slice to exactly the number it needs to install the rom and its gapps/files and leaves you with just a little wiggle room.
I recently tried the v1.5.8 on the gsm hero n it worked pretty well,before i used2have 170mb of internal memory with my decked for life now after applying this mod i have about 300 mb + which means i dont need a freaking ext4 partition for all my crap! xD
PLEASE USE CLOCKWORK RECOVERY IT WILL NOT WORK ON AMON-RA:
although in the cdma forums they used adb,i didnt feel like using it n didnt cause any issues
Original Files and Instructions: Firerats Original G1/MT3G thread found Here
Media fire link - Download!
(please note i've tried only the 1.5.8 version n it runs fine!)
After you read through firerats original instructions just know that itll be slightly different on your hero!
1. Click on the link i posted above and download these files: FR-recovery-v1.5.3-CustomMTD_S.zip and FR-boot-v1.5.3-CustomMTD_S.zip
2. Put both those files onto your SDCard.
3. While in your SDCard, make a .txt file named "mtdpartmap.txt"
4. Open your new mtdpartmap.txt file and
if ur using an aosp rom cm6 or cm7 type this into the txt
Code:
mtd 95 15
(The 95 here refers to /system size, and 15 to /cache partition size)
If you are using a larger Sense Rom then type
Code:
mtd 175 15
(This is just an approximation)
5. Once all 3 files are saved on the root of your SDCard, reboot your phone into recovery
6. Format/Wipe your system and cache.
7. Flash the file: FR-recovery-v1.5.X-CustomMTD_S.zip
8. Once the file is done flashing, it'll prompt you to wipe cache, system, and dalvik again.
after wiping cache system and dalvik reboot back into recovery
9.Flash CM7 or CM6 rom if you used 95 for /system or Flash your larger Sense Rom if you used 175 for /system
9.a.Optionally, flash any kernel you may be choosing to use.
10.Flash the file: FR-boot-v1.5.X-CustomMTD_S.zip
11.Click the top option on your recovery menu to reboot your system.
12.Once your system is fully booted you can go into menu > settings > sd card and internal storage , and check all the new added internal memory you have.
FYI : anytime you flash a new rom after this mod, or flash a new kernel to a currently flashed rom, you will ONLY NEED TO FLASH THE SECONDARY FIRERAT BOOT file named "FR-boot-v1.5.X-CustomMTD_S.zip".
so say after this mod you want to try a new kernel, you flash the kernel, flash boot, and reboot the system.
or say you want to flash a new cm7 nightly update, you flash the new rom/update, flash boot, reboot.
or say u want a new nightly and a new kernel, you flash the nightly, flash the kernel, flash the boot, reboot.
its very simple, if anything u flash overwrites current kernel specifications, u need to flash the boot file to make sure it knows how to set itself up. this goes for nandroid back ups as well.
A lil more help- i was using the decked rom so to actually check how much memory was consumed by /system i opened the terminal emulator typed in this
Code:
# su
# df -h
to show me memory consumption.
the command will tell you what % you are using on your system. if you are at 60% then you can go ahead and decrease your /system value in your mtdpartmap.txt to about 2mb over the value it says you are using. so if your rom uses 115mb of /system you can change your mtd to "mtd 117 2".
So if you are getting an error while trying to flash a rom after doing this modification you most likely don't have enough /system space and will want to up your value to something more then enough like "mtd 200 4" then run the above code and re-scale down back to 2mb over what the current rom is using.
Credits-
Foo_Blyat over at the cdma forums based on whose guide i could get this work on our hero and rewrite this guide
Firerat for even making this mode which is BRILLIANCE!!!!!
Proof?
heres a couple of my personal screen-shots after using the mod
{
"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"
}
notice the internal memory and tell me i'm ****ting u ppl
Enjoy
Is it possible to do a nand backup of my current rom, do this mod, and then restore the nand backup? Or does it only work with a fresh flash of a new rom?
Also, could you please explain exactly what the two numbers in the mtdpartmap.txt file are referring to. Thanks.
Woohoo, it works!!
OK, first I'll answer my own questions. It is possible use a nand restore, which is what I did. Secondly, the first number in the txt file refers to the system partition and the second refers to the cache partition. Whatever is left over goes to the data partition.
I decided to be cautious in my numbers. I left the cache partition exactly as it was (130!) and only reduced my system partion by 60mb (still leaving ~10mb of wiggle room in the system partition).
So now I have 60mb extra in internal storage! Sweet!
treesurf said:
Woohoo, it works!!
OK, first I'll answer my own questions. It is possible use a nand restore, which is what I did. Secondly, the first number in the txt file refers to the system partition and the second refers to the cache partition. Whatever is left over goes to the data partition.
I decided to be cautious in my numbers. I left the cache partition exactly as it was (130!) and only reduced my system partion by 60mb (still leaving ~10mb of wiggle room in the system partition).
So now I have 60mb extra in internal storage! Sweet!
Click to expand...
Click to collapse
Nice
Sry I wasn't more accurate, the first number is the system partition and second is the cache partition, cache doesn't need alotta memory perhaps u should make it 35 thereby getting 100mb of data more btw which rom?
Sent from my Hero using xda premium
what can I say ? It simply worked. I used clockworkmod to make a backup of my current ROM first (I am running the latest Heroine) then repartitioned following your instructions, restored the previously backup and voilà, swimming in a sea of free megabytes :
# df -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.5M 0 95.5M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_st
/dev/block/mtdblock3 180.0M 169.8M 10.2M 94% /system <<< was 100% before
/dev/block/mtdblock5 255.8M 153.6M 102.1M 60% /data <<< was more then 90% before
/dev/block/mtdblock4 30.0M 4.2M 25.8M 14% /cache <<< to be safe, I could probably lower it further to 15 as per instructions
/dev/block//vold/179:1
7.4G 5.9G 1.5G 80% /sdcard
I believe that was done earlier. But devs pulled out.
http://forum.xda-developers.com/showthread.php?t=913245
http://forum.xda-developers.com/showthread.php?t=755204
Cheers!
EDIT: I re-read the threads - it appears tha everything worked fine, maxima just bought a new phone
I'm so going to try this tomorrow, I have absolutely NO time today xD more cache is nice
bharat_goku said:
Nice
Sry I wasn't more accurate, the first number is the system partition and second is the cache partition, cache doesn't need alotta memory perhaps u should make it 35 thereby getting 100mb of data more btw which rom?
Sent from my Hero using xda premium
Click to expand...
Click to collapse
When I fill up my new 80mb of /data then I'll think about reducing the cache.
I'm using DeckedForLife ROM.
I always use a "move dalvik-cache to /cache" script. It is a tad safer I guess?
THIS IS CUTE. Gona try it ....
riemervdzee said:
I always use a "move dalvik-cache to /cache" script. It is a tad safer I guess?
Click to expand...
Click to collapse
Yeah, I tried it too. Pretty neat script, but unfortunately it does not increase system partition size.
Also I got suspicions that system is cleaning cache from time to time by deleting older files so as well dalvik files.
edit: proof pics are not visible. Maybe I did not understand everything, but is it possible to make it permanent mod?
It's permanent until you flash your next ROM. So you just need to flash the FR-boot-v1.5.X-CustomMTD_S.zip file after flashing any ROM/nand backup and it will continue to use whatever partition settings you have put in the text file.
For personal use this mod is fine, but if I'm building a custom ROM for public use I need to go through very complicate ROM flash explanation with possibility to brick the phone at the end.
Ok,tried this and it's super . However, I have some strange "problems".
I have set partitions to 100 for system and 30 for cache right from the beginning. If I boot into rom right after flashing, without changing kernel, everything is as it should be. Have over 300 MB on internal storage etc. As soon as I change kernel usb tethering becomes disabled (when I plug the cable it still says that's not connected when I enter "tether menu" ) and nothing helps, not changing kernel, reverting to old one, nothing. Second thing is "power menu", only three options appear in here, reboot, recovery and screenshot. Silent and airplane mode, profiles and power off options don't appear . And finally, when I try to wipe dalvik cache this message pops in recovery :
E: Can't mount /dev/block/mmcblk0p2
(File exists )
Dalvik Cache wiped.
It seems that dalvik is wiped in the end? What's this partition used for?
First two problems go away if I flash some rom without messing with partitions but last one stays
Can someone else please check usb tether and power boot thingy on their phone?
Sent from my Hero using Tapatalk
What ROM do you use?
What recovery do you use?
OP said that AmonRA is not tested, only CWM.
Using decked for life and cwm recovery.
Sent from my Hero using Tapatalk
aca89 said:
Ok,tried this and it's super . However, I have some strange "problems".
I have set partitions to 100 for system and 30 for cache right from the beginning. If I boot into rom right after flashing, without changing kernel, everything is as it should be. Have over 300 MB on internal storage etc. As soon as I change kernel usb tethering becomes disabled (when I plug the cable it still says that's not connected when I enter "tether menu" ) and nothing helps, not changing kernel, reverting to old one, nothing. Second thing is "power menu", only three options appear in here, reboot, recovery and screenshot. Silent and airplane mode, profiles and power off options don't appear . And finally, when I try to wipe dalvik cache this message pops in recovery :
E: Can't mount /dev/block/mmcblk0p2
(File exists )
Dalvik Cache wiped.
It seems that dalvik is wiped in the end? What's this partition used for?
First two problems go away if I flash some rom without messing with partitions but last one stays
Can someone else please check usb tether and power boot thingy on their phone?
Sent from my Hero using Tapatalk
Click to expand...
Click to collapse
When u changed kernel did u flash the boot.zip file again?
Also I believe ur changing from .29 to .35 kernel? Did u apply the USB fix by erasmux??
Abt the power menu just wait a bit it comes back...
I made a mistake of implementing move dalvik cache to SD,I think that's causing errors in the
Wipe
Just plug ur fone into ur comp and
Open console go to ur sdk directory and try this command adb remount /dev/block/mmcblk0p2
Not sure if the command is ryt,Bt just give it a try...
Sent from my Hero using xda premium
Thanks for your efforts.
I used Fireat's path already on my G1 (meanwhile I sold it).
It saved me from using ext partition for data, which is in no way a speed booster.
Maybe it's a dumb question, but shouldn't it be possible to integrate this patch in a ROM?
The steps described in your post are easy to understand and absolutely not complicated (for fellows that often change ROMs).
bharat_goku said:
When u changed kernel did u flash the boot.zip file again?
Also I believe ur changing from .29 to .35 kernel? Did u apply the USB fix by erasmux??
Abt the power menu just wait a bit it comes back...
I made a mistake of implementing move dalvik cache to SD,I think that's causing errors in the
Wipe
Just plug ur fone into ur comp and
Open console go to ur sdk directory and try this command adb remount /dev/block/mmcblk0p2
Not sure if the command is ryt,Bt just give it a try...
Sent from my Hero using xda premium
Click to expand...
Click to collapse
I've already done all of that several times (trying out on a few roms) and now I came back to decked and all of the sudden everything works . Menus are back and tethering works.
"/dev/block..." thing is still there. Tried your command but it doesn't help although it's properly written. I read somewhere that formating helps but in my case it doesn't, already tried. So, if you got any other idea I'll gladly try it. In the meantime I'm gonna enjoy the free space on internal storage .
Thanks for help btw.
Sent from my Hero using Tapatalk
Amon Ra
Well, I think I can definitively say this doesn't work on Amon Ra. The second reboot into recovery has to be done via a complete switch off. Tried reinstating from nand backup, but final reboot either sticks on HERO or (sometimes) semi boots into ROM, but without desktop...
Wanted to undo the error of trying this, so downloaded the REMOVE script and flashing that using same procedure, with and without BOOT script, same difference. Tried flashing ROM again, clean. Same difference. So actually I'm a bit stuck.
Any thoughts from anyone how to get back to a safe spot from here and starting over? (Prefer to avoid hard reset!)
Have you tried changing system and cache values in txt file to original ones, or at least something close to them, and then flashing boot.zip. Just a thought, don't know if It's actually going to change something.
Sent from my Hero using Tapatalk
Hey guys
let me give you some background informatie as to what happend
I went on a flashing spree today and I bumped into something irritating!
I've flashed JBSourcery V4.5 but it didn't satisfy my personal needs (didn't have some mods that I liked).
So back into recovery, factory reset, cache wipe... all the standard cleaning stuff. Next on my list was
LiquidSmooth and that's where my problem started. I was in recovery, wiped the lot and wanted to flash
LiquidSmooth which was already on my SDcard (I came prepared ) So I chose "Install ZIP from SD" and
my heart skipped a beat. Normally I'd see all my folders on my SD... Now I only saw "0", "Legacy" and "obb".
I kept my cool and opened each one untill I found my SD contents which where stuffed into the "0" folder.
No big deal... I could flash LiquidSmooth so everything was fine. Next one was XenonHD. Still same problem
but I could flash my stuff.
Long story short, how do I get my internal memory back to how it was?
Something on a side note though, It's only like that in recovery. If I connect my phone via USB it's normal. (Samsung Galaxy Nexus -> Internal Memory -> ...)
Ideas are welcome!
Thanks in advance! :good:
diSke
Move them with Root Explorer or hook it up to the comp and move them. Or check out some of the other threads about the /0/ folder, there are allot of them.
WiredPirate said:
Move them with Root Explorer or hook it up to the comp and move them. Or check out some of the other threads about the /0/ folder, there are allot of them.
Click to expand...
Click to collapse
Oh great... and I added one to the lot... Sorry guys!
Didn't think of searching with the "0" folder as keyword.
Thanks though for the reply and solution!
One quick question, do you know if the "Legacy" and "obb" folders are important?
I'm sure they are significant for some reason, but I am unsure of their specific purpose. I would for sure keep them in tact.
Hmmm... I moved them and now all my sd card files are scattered around...
Some in legacy, some in "0", some in media... probably best to wipe the lot and start from scratch?
From another post about Android 4.2's filesystem setup:
Cilraaz said:
Source: init.tuna.rc
Code:
on init
# See storage config details at [URL="http://source.android.com/tech/storage"][COLOR=#0066cc]http://source.android.com/tech/storage[/COLOR][/URL]
mkdir /mnt/shell/emulated 0700 shell shell
mkdir /storage/emulated 0555 root root
export EXTERNAL_STORAGE /storage/emulated/legacy
export EMULATED_STORAGE_SOURCE /mnt/shell/emulated
export EMULATED_STORAGE_TARGET /storage/emulated
# Support legacy paths
symlink /storage/emualted/legacy /sdcard
symlink /storage/emualted/legacy /mnt/sdcard
symlink /storage/emualted/legacy /storage/sdcard0
symlink /mnt/shell/emulated/0 /storage/emulated/legacy
[...]
# virtual sdcard daemon running as media_rw (1023)
service sdcard /system/bin/sdcard /data/media /mnt/shell/emulated 1023 1023
class late_start
[...]
Click to expand...
Click to collapse
You said which ROMs you flashed, but what version of Android are you on now? It sounds like you might be back on 4.1.x, since you're seeing 0, legacy, and obb in /sdcard.
If you went back to 4.1.x, then 0, legacy, and obb are not important. Only /data/media matters on 4.1.x. If you are on 4.1.x, go to /data/media/0 and copy all of the files there to /data/media, then reboot. That will fix your setup. Once that's done and 0, legacy, and obb are all empty, they are safe to delete.
If you are on 4.2 or 4.2.1, then the above quote is accurate. Your information should be in /data/media/0 and the system should be properly fuse mounting and symlink'ing to showyour data into /sdcard.
When moving files around, it's usually best to do it at the source (within /data/media) so you don't have to worry about the fuse mounts and symlinks causing a problem.
I switched from 4.1 to 4.2.1.
Problem is I started switching things around and now my sd card files seem te be everywhere.
Can't figure out what is what...
I moved everything from "data/media/0" to "data/media"
but now my system can't find my files.
When I try to move everything back it says "unable to execute the command"
diSke said:
I switched from 4.1 to 4.2.1.
Problem is I started switching things around and now my sd card files seem te be everywhere.
Can't figure out what is what...
I moved everything from "data/media/0" to "data/media"
but now my system can't find my files.
When I try to move everything back it says "unable to execute the command"
Click to expand...
Click to collapse
As my post said, if you're on 4.2.1, your files should be in /data/media/0. You'll see copies of them in multiple places (/storage/emulated/legacy, /sdcard, /mnt/shell/emulated/0, /mnt/sdcard, /storage/sdcard0, and /data/media/0), but these are fuse mounts and symlinks. Your data only "physically" exists in one place: /data/media/0. After rebooting, your files should be found in /sdcard, rather than /sdcard/0. If not, then you might have the multiple 0 folder issue (e.g. /data/media/0/0/0, which ends up being /sdcard/0/0) from having an outdated version of your recovery.
Long story short, if you're on 4.2.1, then any files from your "SD Card" should be found in /data/media/0. If you're on 4.1.x, then they should be in /data/media.
If you're getting that error when trying to copy from /data/media to /data/media/0, then you'll need to check that /data/media is mounted as r/w and that you have write permission to the 0 folder within it. You should also be copying these files around as root (either through terminal emulator or a root file browser like Root Explorer).
Cilraaz is correct, however if you are looking for an easy way to straighten it out you can do the following.
Copy everything you want to save to the computer.
Reboot into recovery and format data. (Not wipe data actually format.)
Reboot phone and data partition will be good to go again.
Copy files back from computer and you should be as you were previously.
Of course all other data will be gone but I'm sure if you are a crack flasher you can get all that back.
G-Nexus Sent
ifly4vamerica said:
Cilraaz is correct, however if you are looking for an easy way to straighten it out you can do the following.
Copy everything you want to save to the computer.
Reboot into recovery and format data. (Not wipe data actually format.)
Reboot phone and data partition will be good to go again.
Copy files back from computer and you should be as you were previously.
Of course all other data will be gone but I'm sure if you are a crack flasher you can get all that back.
G-Nexus Sent
Click to expand...
Click to collapse
Good call on the computer backup. You don't need to wipe data, though. Just backup what you want to save from storage to your computer, then flash userdata.img from the stock 4.2.1 ROM, which will wipe out and re-create the /data/media partition. Then when you reboot, the fuse mounts and symlinks will be properly recreated and you can use MTP to copy your data back (or adb push it to /data/media/0 or /sdcard).
Thanks guys.
Fixed it differently though, Completely wiped everything again and started from scratch.
Made a backup earlier of everything I wanted to save except for messages which I forgot (damnit)
But it's all good now
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Hi there! I have a problem with my phone, every app keeps force close becouse data file system is read only. Factory reset helps, but after next reboot it happens again. Had a 2.3.6 LL2 ROM Kyrillosv5. Flashing with odin to any 2.3 didnt help. Flashed to 4.1 and no problem for now. I think the problem was caused by restoring any app data with TitaniumBackup. Maybe someone knows what happend?
Logcat in attachment if someone wants.
Similiar problem with fix is here: fix
Msiiek said:
Hi there! I have a problem with my phone, every app keeps force close becouse data file system is read only. Factory reset helps, but after next reboot it happens again. Had a 2.3.6 LL2 ROM Kyrillosv5. Flashing with odin to any 2.3 didnt help. Flashed to 4.1 and no problem for now. I think the problem was caused by restoring any app data with TitaniumBackup. Maybe someone knows what happend?
Logcat in attachment if someone wants.
Click to expand...
Click to collapse
Maybe the permission (?)
Sent from my GT-I8160 using xda premium
I had identical issue, no one in this and general android forum was able to help me. So I had to find solution on my own.
It seems, that CWM formatting procedure has bugs, and after some restarts, e2fsck tries to repair filesystem, but it can't because of non standard(?) structure on partition.
This is my thread:
http://forum.xda-developers.com/showthread.php?t=2279524
Get your own mke2fs binary and boot into CWM, connect ADB and format /data using mke2fs. This works fine with e2fsck. No more this problem, just don't use CWM to format/restore /data, just backup/restore it via dd.
If you want to go back to old stable GB and need help, write me a PM, I'll send you gtalk/jabber.
Thanks will pm you if I would like to back to gb. Probably I will just go back to gb to try your fix. I had cwm 5 and did format /data. Restoring from backup helped until next reboot. The same issue and very strange. One more time thanks
I had same issue i fixed it by flashing rom with with odin and ticking option with repartition, it completely erased everything, cwm wipe data cache didnt fix my issue, something went corrupt, I had forces immediately after reboots
Flash a GB or JB ron with PIT file, that has the repartition info. Fixed my issues, currently on XXMC8 workibg absolutely great n smooth and amazing battery life much better than GB
Sent from my GT-I9300
JB does not have this bug... It's all about GB.
Sent from my GT-I8160 using xda app-developers app
buaser said:
I had identical issue, no one in this and general android forum was able to help me. So I had to find solution on my own.
It seems, that CWM formatting procedure has bugs, and after some restarts, e2fsck tries to repair filesystem, but it can't because of non standard(?) structure on partition.
This is my thread:
http://forum.xda-developers.com/showthread.php?t=2279524
Get your own mke2fs binary and boot into CWM, connect ADB and format /data using mke2fs. This works fine with e2fsck. No more this problem, just don't use CWM to format/restore /data, just backup/restore it via dd.
If you want to go back to old stable GB and need help, write me a PM, I'll send you gtalk/jabber.
Click to expand...
Click to collapse
So, If I want solve this problem, I can't use CWM Recovery to restore my owm data?
(Although It can restore by TitaniumBackup, but CWM is more convenient than TitaniumBackup...)
Andther question is....Where I can find mke2fs binary?
Sorry for my poor English.
@buaser:
Can you upload mke2fs binary please? I'm suffering this error right now and can't use my phone...
E:
I formated /data via an adb shell with the command "busybox mke2fs /dev/block/mmcblk0p5".
The command was sucessfully and made a brand new ext4 filesystem. But one mount option has changed after that: data=writeback.
Before formating the option was "data=ordered", like on /system
Code:
# mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,noatime,nodiratime,mode=755 0 0
devpts /dev/pts devpts rw,noatime,nodiratime,mode=600 0 0
proc /proc proc rw,noatime,nodiratime 0 0
sysfs /sys sysfs rw,noatime,nodiratime 0 0
none /sys/kernel/debug debugfs rw,noatime,nodiratime 0 0
none /acct cgroup rw,noatime,nodiratime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,noatime,nodiratime,mode=755,gid=1000 0 0
tmpfs /dev/shm tmpfs rw,noatime,nodiratime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,noatime,nodiratime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p3 /system ext4 rw,noatime,nodiratime,commit=60,barrier=1,[COLOR="Red"]data=ordered[/COLOR],noauto_da_alloc 0 0
/dev/block/mmcblk0p2 /modemfs ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p4 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,commit=60,barrier=0,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p7 /efs ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p5 /data ext4 rw,nosuid,nodev,noatime,nodiratime,commit=30,barrier=0,[COLOR="Red"]data=writeback[/COLOR],noauto_da_alloc 0 0
/dev/block/mmcblk0p1 /mnt/.lfs j4fs rw,noatime,nodiratime 0 0
/dev/block/vold/179:8 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:17 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:17 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,noatime,nodiratime,size=0k,mode=000 0 0
#
Does somebody know how to fix that?
Later i will do a fsck to check if partion is clean and checkable now...
E again:
fsck was successful:
Code:
~ # e2fsck -v /dev/block/mmcblk0p5
e2fsck 1.41.11 (14-Mar-2010)
/dev/block/mmcblk0p5 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 8822 has zero dtime. Fix<y>? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -35182
Fix<y>? yes
Free blocks count wrong for group #1 (2542, counted=2543).
Fix<y>? yes
Free blocks count wrong (231604, counted=231605).
Fix<y>? yes
Inode bitmap differences: -8822
Fix<y>? yes
Free inodes count wrong for group #1 (5868, counted=5869).
Fix<y>? yes
Free inodes count wrong (76679, counted=76680).
Fix<y>? yes
/dev/block/mmcblk0p5: ***** FILE SYSTEM WAS MODIFIED *****
3320 inodes used (4.15%)
375 non-contiguous files (11.3%)
3 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 370/21/0
87883 blocks used (27.51%)
0 bad blocks
0 large files
2575 regular files
730 directories
0 character device files
0 block device files
2 fifos
0 links
0 symbolic links (0 fast symbolic links)
4 sockets
--------
3311 files
~ # e2fsck -v -f /dev/block/mmcblk0p5
e2fsck 1.41.11 (14-Mar-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
3320 inodes used (4.15%)
375 non-contiguous files (11.3%)
3 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 370/21/0
87883 blocks used (27.51%)
0 bad blocks
0 large files
2575 regular files
730 directories
0 character device files
0 block device files
2 fifos
0 links
0 symbolic links (0 fast symbolic links)
4 sockets
--------
3311 files
~ #
I hope my /data won't die anymore.
Writeback option is ok, don't worry about that. Just check via e2fsck if there is all OK on /data partition. Remember to umount /data first.
The bug is probably in CWM 5, so backups work, but restoring /data makes disaster, so rather backup/restore data partition via dd command.
It would be fantastic, if some developer of CWM comments this thread.
As I have little time, I made primitive scripts to backup and restore /data partition via dd command. Scripts can be launched via CWM 5.
The backup image (data.img) of mmcblk0p5 is stored on /sdcard and restored from there also.
Remember to unmount data from CWM menu and mount sdcard!
It works for me (CWM 5, GB 2.3.6), but I can't promise it will work for you.
Check the script for bugs if you want.
Have fun, but on your own risk
Yeah, this version of CWM sucks. I restored via "tar xf ..." from a CWM-backup
Did it boot correctly after that? Or did you need to fix permissions? Wifi works fine?
Yes, till now my phone works normal after restoring via tar, no fix permission or other magic needed.
Hey all,
Since that file is making my backup restores to fail, I had been wondering what is it for and if that can be safely deleted?
It is quite huge tbh, and increase considerably backup sizes.
Being very close in size to the total ramsize I wonder if that would not be something like a ram dump of some kind, generated upon error or to start OS faster, some kind of hibernate.sys maybe.
Code:
begonia:/data/vendor # ls -lah dumpsys/
total 2.8G
drwxrwxr-x 2 system system 4.0K 2020-07-21 20:33 .
drwxrwx--x 39 root root 4.0K 2020-07-28 13:19 ..
-r-------- 1 root root 5.6G 2020-07-28 10:00 mrdump_preallocated
Since it makes my TWRP backup restore fail, I wonder if I could safely delete it either prior backup or from backup archive itself so restore does not fail.
Technically when restore fail on that file which is quite at the end of the backup, it kind of success restoring everything anyway, still some files are probably missing and I dont like errors.
If any of you know about this file, please let me know.
Thank you.
Regards!