Okay, so basically as the title says, I want to get back to rfs since I want to use cwm, and because ever since I flashed icy fusion I don't even get the speed benefits of ext4, even though all my partitions are supposedly still in ext4 format (weid, I know). Now I don't want to lose my data, and for some reason my Odin packages I try to make never work and just brick my device, so here is my idea. Could I make dumps of my partitions using terminal emulator, then somehow flash those using cwm? Or is it not possible? Thank You.
Sent using Tapatalk
iJimaniac said:
Okay, so basically as the title says, I want to get back to rfs since I want to use cwm, and because ever since I flashed icy fusion I don't even get the speed benefits of ext4, even though all my partitions are supposedly still in ext4 format (weid, I know). Now I don't want to lose my data, and for some reason my Odin packages I try to make never work and just brick my device, so here is my idea. Could I make dumps of my partitions using terminal emulator, then somehow flash those using cwm? Or is it not possible? Thank You.
Sent using Tapatalk
Click to expand...
Click to collapse
Well, klin's kernel works with cwm, so if you make a backup from there (or use an existing backup), rename it from .ext4 to .rfs (basically using the ext4 converting instructions in reverse), you *should* be able to get back to rfs. To answer your second question, yes, you can dump your partitions, but you would need to create an odin-flashable package with them, and dd (the command you would use) dumps retain the filesystem (so ext4 dumps are flashed as ext4, and so on).
Yes, but am I correct in thinking if I enter cwm to create a nandroid, my data partition will be wiped because of the cwm bug with ext4? What I am trying to do is make a backup without losing my data. I might just have to lose my data and restore apps with titanium backup.
Sent using Tapatalk
iJimaniac said:
Yes, but am I correct in thinking if I enter cwm to create a nandroid, my data partition will be wiped because of the cwm bug with ext4? What I am trying to do is make a backup without losing my data. I might just have to lose my data and restore apps with titanium backup.
Sent using Tapatalk
Click to expand...
Click to collapse
Klin's kernel's CWM seems to NOT wipe your data, at least in my experience, so you should be good to go if you flash it.
hanthesolo said:
Klin's kernel's CWM seems to NOT wipe your data, at least in my experience, so you should be good to go if you flash it.
Click to expand...
Click to collapse
Hmm, I didn't realize that, thanks for the tip!
Sent using Tapatalk
http://forum.xda-developers.com/showthread.php?t=1620255
Hey, I just saw this on the portal, looks like it could be a solution to the problem?
Sent using Tapatalk
Okay so, true to your word, klin's r3 doesn't have the bug. Unfortunately I now get an error when I try making a nandroid. It gets to "backing up /cache..." then gives me " Unable to find mounted volume: /cache
Error finding an appropriate handler" and immediately returns to the main menu without finishing the nandroid. Any ideas what to do? Would wiping cache be safe with this problem?
Some updates: wiping cache did nothing to fix the problem. I can dump the cache partition fine using terminal emulator and the dd command. When I use the "mount" command, cache is not listed in the partitions.
This is starting to creep me out. I think something to do with it is after flashing icyfusion going from klassic r5 with all partitions converted to ext4, I started getting rfs-like io preformance (quadrant benchmarks), even though "mount" said all partitions are still ext4.
Sent using Tapatalk
If you want to get back to rfs that bad do the following.
1. make a nandroid backup
2. change the .ext4 to rfs like when you want to convert
3. flash the total recovery method with the STOCK kernel.
4. Then flash a kernel that supports the .tar backup (klin or terrasilent)
5. restore your backup and you should be in rfs with your backup.
Me I use terrasilent and I don't lose data when I backup. Maybe when you change the .ext4 to .rfs try to unmount using the computer before the device.
Well, if you read my above posts you can see that I can't make a nandroid because of something concerning the cache partition. It cancels there. Thank you for replying!
Sent using Tapatalk
iJimaniac said:
Well, if you read my above posts you can see that I can't make a nandroid because of something concerning the cache partition. It cancels there. Thank you for replying!
Sent using Tapatalk
Click to expand...
Click to collapse
Oh didin't read the cache part... Hmm you can always make a backup of your data partition and then make a nandroid backup from terrasilent.
I am not exactly sure if it is the kernal's fault, or something messed up with partitions. I doubt terrasilent would fix it. I have also now tried restoring the cache partition from a previous nandroid, and it restores (I guess), but it still gives me the same error when backing up.
Sent using Tapatalk
Sorry for abandoning this thread, I forgot about it . Perhaps you can mount it manually? Try using the partition listed when you are booted into android to mount it eg. Mount /Dev/block/stlx. I also suppose that to fix all of this easily, you can return to stock with a pit, but you will have too have a backup of your data.
I tried and get:
# mount /Dev/block/st11
mount: can't find /Dev/block/st11 in /etc/fstab
Sent using Tapatalk
iJimaniac said:
I tried and get:
# mount /Dev/block/st11
mount: can't find /Dev/block/st11 in /etc/fstab
Sent using Tapatalk
Click to expand...
Click to collapse
its stl not st
zaclimon said:
its stl not st
Click to expand...
Click to collapse
Whoops, typo, here is direct copy/paste from terminal emulator;
$ export PATH=/data/local/bin:$PATH
$ su
# mount /Dev/block/stl11
mount: can't find /Dev/block/stl11 in /etc/fstab
#
Sent using Tapatalk
iJimaniac said:
Whoops, typo, here is direct copy/paste from terminal emulator;
$ export PATH=/data/local/bin:$PATH
$ su
# mount /Dev/block/stl11
mount: can't find /Dev/block/stl11 in /etc/fstab
#
Sent using Tapatalk
Click to expand...
Click to collapse
it's because of the caps *d*. You should write
# mount /dev/block/stl11
Same result:
$ export PATH=/data/local/bin:$PATH
$ su
# mount /dev/block/stl11
mount: can't find /dev/block/stl11 in /etc/fstab
#
Sent using Tapatalk
iJimaniac said:
Same result:
$ export PATH=/data/local/bin:$PATH
$ su
# mount /dev/block/stl11
mount: can't find /dev/block/stl11 in /etc/fstab
#
Sent using Tapatalk
Click to expand...
Click to collapse
can you send me your /etc/recovery.fstab to see if /cache is in it? and which rom are you using?
Umm, I don't have a recovery.fstab, just a "vold.fstab" and a "fstab". I am using icy fusion.
Sent using Tapatalk
Related
I have now seen a number of cases of the EFS partition getting wiped / corrupted on the SGS II, leaving users with an effectively useless phone.
With this in mind, i've written a little init.d script for my ROM which backs up the EFS partition on boot if a backup does not already exist. A non intrusive safety net for users if you will.
The script just needs a suitable boot image that runs init.d, although it could easily be tacked onto the end of install-recovery.sh if that's not the case.
I'd love to encourage all developers to use this script for users' sake!
You can download the script here - http://cl.ly/2j0p0R3F07052m2T2u0e - but it's very simple, here's the code...
Code:
#!/system/bin/sh
# EFS auto backup script for Samsung Galaxy S II
# By @paulobrien - http://s2.MoDaCo.com
mount /dev/block/mmcblk0p11 /sdcard
if [ ! -f /sdcard/efs.autobackup.img ];
then
dd if=/dev/block/mmcblk0p1 of=/sdcard/efs.autobackup.img
fi
umount /sdcard
Note the manual mount / umount of sdcard is necessary because this happens late in the boot process.
Cheers!
P
Hats of to you Paul.Although I have already made a backup of my EFS folder,such a script would save MANY people from A LOT of trouble.
tolis626 said:
Hats of to you Paul.Although I have already made a backup of my EFS folder,such a script would save MANY people from A LOT of trouble.
Click to expand...
Click to collapse
i havent...never did. i think i wiped about a hundred times now and flashed and reflashed...is it possible to recover the efs folder?
haasgo said:
i havent...never did. i think i wiped about a hundred times now and flashed and reflashed...is it possible to recover the efs folder?
Click to expand...
Click to collapse
If your phone is working, it means your EFS partition is still there...
You can back it up using the many tutorials out there in the forum...
Sent from my GT-I9100 using XDA Premium App
Problem is that the users who read how to backup EFS folder fall in to two category s those that read up first and would have backed up EFS and those that only pick the manual up after something is broke .
This script would be a saver for many of the second group and big thanks to Paul and i hope devs do run with it .
jje
I would like to adapt your script for Nexus S.
Once i got the img file of efs partition, how do can a make a script for restoring thet img file to efs partition?
Or what to do with that img file?
EDIT: @ paul - One more question - how do I mount /sdcard on Nexus S through the script? mount command in the Terminal Emulator shows my /dev/blocks/vold/179:3 as mount point, but if I use that mount point in the script it won't mount the /sdcard. Any idea?
EDIT2: I got it working with this command:
mount /dev/block/platform/s3c-sdhci.0/by-name/media /sdcard
and I got the efs.autobackup.img on my sdcard.
How do I restore the efs.autobackup.img to efs partition?
Thanks Paul this is a very useful utility hope it gets sticky
May i ask what conditions these people are falling foul of getting the EFS wiped? Is it rouge roms/cwm zips, wiping to much in recovery, Odin flashing?
Curious so i may steer clear, have a backup but staying away is half the battle
paulobrien said:
You can download the script here - http://cl.ly/2j0p0R3F07052m2T2u0e - but it's very simple, here's the code...
Code:
#!/system/bin/sh
# EFS auto backup script for Samsung Galaxy S II
# By @paulobrien - http://s2.MoDaCo.com
mount /dev/block/mmcblk0p11 /sdcard
if [ ! -f /sdcard/efs.autobackup.img ];
then
dd if=/dev/block/mmcblk0p1 of=/sdcard/efs.autobackup.img
fi
umount /sdcard
Click to expand...
Click to collapse
Hi Paul, I have modified your script so that it makes a tar file, tar file keeps the permissions for the efs partition and its easier to restore. Here it is:
Code:
#!/system/bin/sh
# EFS auto backup script for Samsung Galaxy S II
# By @paulobrien - http://s2.MoDaCo.com
mount /dev/block/mmcblk0p11 /sdcard
if [ ! -f /sdcard/efs_autobackup/efs-backup.tar.gz ];
then
mkdir /mnt/sdcard/efs_autobackup
busybox tar zcvf /sdcard/efs_autobackup/efs-backup.tar.gz /efs
fi
umount /sdcard
mynamesteve said:
Thanks Paul this is a very useful utility hope it gets sticky
May i ask what conditions these people are falling foul of getting the EFS wiped? Is it rouge roms/cwm zips, wiping to much in recovery, Odin flashing?
Curious so i may steer clear, have a backup but staying away is half the battle
Click to expand...
Click to collapse
Some hit "wipe EFS" in ODIN.
It's possible to mess up a zip badly enough to wipe EFS
A normal wipe shouldn't do it, but a bad CWM build could in theory do it...
A dodgy "virus" could do it, if it were targetting rooted phones, or had a root exploit.
That's why I keep an EFS backup on my PC and off-site
brainmaster said:
Hi Paul, I have modified your script so that it makes a tar file, tar file keeps the permissions for the efs partition and its easier to restore.
Click to expand...
Click to collapse
Nope dd is much better, but safer to have both, but dd should be used with bs=4096k option.
how to restore the efs folder?
how to restore the efs folder?
Please, need to restore EFS, not sure what happened but tried installing Cognition R3 and lost my EFS, I do however have a prior efs.autobackup. Please help.
I saw a thread on the international S2 forum regarding the importance of backing up the /efs folder on the phone so you don't lose the phones imei. I was wondering if this is still a necessity on our phone as well? And if so is there a different process to do it than what they used? They used terminal commands to back it up using terminal Emulator or ADB.
This is the thread:
http://forum.xda-developers.com/showthread.php?t=1068193
Its very important..ask me..i lost my IMEI and dint have a back up of the efs folder..had to go to the store and get a new phone under warranty.
Please make a backup of it.
After 2 months, someone just had EFS corruption last week - so yes, now I think it's a good idea to back it up.
IMO it would be a good idea to image the partition too...
Entropy512 said:
IMO it would be a good idea to image the partition too...
Click to expand...
Click to collapse
Can you verify the partition? Is 0p3 the right one, or is it 0p1? I coundn't find a definitive answer by searching.
For some reason I thought it was p3, but I was wrong. It's p1:
Code:
/dev/block/mmcblk0p1 on /efs type ext4 (rw,nosuid,nodev,noatime,barrier=1,journal_checksum,data=ordered)
To back it up, get ADB working, and run the following using ADB while the phone is in CWM recovery and /sdcard is mounted (It often is not when you first enter CWM, mount it in the Mounts and Storage menu if it is not) (If you do this when the phone is running, you may back it up as it is getting written to, which could result in a bogus backup)
Code:
adb shell dd if=/dev/block/mmcblk0p1 of=/sdcard/efs_backup.img
Thanks for the verification entropy!
Sent from my SAMSUNG-SGH-I777 using XDA App
Entropy512 said:
Code:
/dev/block/mmcblk0p1 on /efs type ext4 (rw,nosuid,nodev,noatime,barrier=1,journal_checksum,data=ordered)
Click to expand...
Click to collapse
I don't know much about linux commands. Is this how you verified the partition?
Also, am I correct in assuming that if the partition is backed up, it would not be necessary to back up the efs directory using a file explorer? Or is there a reason to have both?
You can also run the command from entropy in terminal emulator on your phone. Do su first to get root and enter the dd command to do your backup.
Sent from my SGH-I777
creepyncrawly said:
I don't know much about linux commands. Is this how you verified the partition?
Also, am I correct in assuming that if the partition is backed up, it would not be necessary to back up the efs directory using a file explorer? Or is there a reason to have both?
Click to expand...
Click to collapse
I verified it by executing the following command and looking at the output:
Code:
mount
It may be easier to restore a folder backup - not sure. A partition backup is the best way to guarantee you got EVERYTHING in that partition, byte-for-byte.
That's crazy. Cause I don't understand how you learn stuff like that but thanks(aka I'm gonna go do this since I mess with my phone alot.) I followed amk28's troubles. What's the difference between efs backup pro and this mehod? They both backup images
Entropy512 said:
For some reason I thought it was p3, but I was wrong. It's p1:
Code:
/dev/block/mmcblk0p1 on /efs type ext4 (rw,nosuid,nodev,noatime,barrier=1,journal_checksum,data=ordered)
To back it up, get ADB working, and run the following using ADB while the phone is in CWM recovery and /sdcard is mounted (It often is not when you first enter CWM, mount it in the Mounts and Storage menu if it is not) (If you do this when the phone is running, you may back it up as it is getting written to, which could result in a bogus backup)
Code:
adb shell dd if=/dev/block/mmcblk0p1 of=/sdcard/efs_backup.img
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I777 using XDA App
I was running Bricked Kang but installed the new build of cherry but now the old bricked rom's kernal is still a boot option, how can i remove this kernal from my touchpad and delete the entry in moboot?
I had the Bricked installed myself, and decided to go back to the stock CM9 kernel (since I was having FC issues with certain apps).
Here's what I did:
Open up Terminal Emulator
Type the following:
Code:
su <enter>
mount -t remount,rw /boot <enter>
cd /boot <enter>
rm uImage.CM <tab> <enter> (press Tab until the CM-Bricked is filled in)
echo "CyanogenMod" > moboot.default <enter> (this will set you back to defaulting CyanogenMod. If you want another, use the name of the uImage.<whatever> for Cherry (just put everything after the uImage. part)
reboot <enter>
That'll remove the Bricked Kernel from your boot options, and set your default to Cherry (or in my example, CyanogenMod). Make sure you have the proper Wifi modules installed from your Cherry install, and you should be good to go.
Hope that helps, mate.
I'm having the same problem and that proposed solution did not work...I got a Read only file error...thanks, though...
You have to make sure you mount the /boot partition before you try and do the changed. If it isn't mounted, you get that error.
Sent from my cm_tenderloin using xda premium
ve6ay said:
You have to make sure you mount the /boot partition before you try and do the changed. If it isn't mounted, you get that error.
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
Could you elaborate on how to do that please? The CM_Bricked thing has been bothering me as well.
Thanks in advance!
I had the exact problem and instead of playing around with the instructions I just went to a backup I had before the install.
It worked like a charm for me. If you have a recent backup on CWM don't hesitate to use it .
Hi guys as you know our Xperia 2011 use yaffs2 for the mtd partitions, but it doesn't have too.
I bit the bullet, formated system, cache and data as ext4 from updater-script, knowing that alliance (nightelf) kernels had support for this.
It boots and runs lovely
Sent from my MT11i using XDA
mpiekp said:
Hi guys as you know our Xperia 2011 use yaffs2 for the mtd partitions, but it doesn't have too.
I bit the bullet, formated system, cache and data as ext4 from updater-script, knowing that alliance (nightelf) kernels had support for this.
It boots and runs lovely
Click to expand...
Click to collapse
Any noticeably difference? Run any benchmarks? I never understood why SE used yaffs2 for phones, same as why ext4 isn't supported by default, but that's other story
Anw, I guess now you can only install rom via .zip from CWM? Or maybe even flashtool wouldn't complain, but I guess PCC would complain for sure
p.s. respect for trying that
report pros and cons
Lol to revert just flash s zip that formats as yaffs, will try flashtool, although don't expect an issue as it basically raw writes the sin, which are complete img files including filesystem.
Benchmarks would be pointless, due to running experimental build anyway so nothing to compare to, but things like file manger appear more responsive.
All I can say is try it, make sure the updater-binary you use can accept 4 arguments for format and mount (hint the one in codename can), place that into any Rom zip and edit the updater-script.
So the format line is like this
format("ext4", "MTD", "system", "0");
Sent from my MT11i using XDA
Wonderful and brave find!! ext4 are supposed to be safer (journalism), but can have some overhead.
I have seen a script that even converts live yaffs2 to ext4 in some other forum, so that formatting is not required.
Otherwise, after format, you can restore the backups!
I am really interested to know if the partitions can be resized, so that we can have more space for /data (instead of 100 mb /cache and such a large /system)
Actually having checked how its mounted, it appears to have ignored the fs type
Still I'm going to persue this, what are the default part sizes? Esp part mtd1 where vendor gets mounted as on gb vendor is empty
Sent from my MT11i using XDA
mpiekp said:
Actually having checked how its mounted, it appears to have ignored the fs type
Still I'm going to persue this, what are the default part sizes? Esp part mtd1 where vendor gets mounted as on gb vendor is empty
Sent from my MT11i using XDA
Click to expand...
Click to collapse
Maybe those links help you understand :
http://forum.xda-developers.com/showthread.php?t=1566846
http://forum.xda-developers.com/showthread.php?t=1449917
how can we check the type of our partitions?
I'm researching a bit, and people say that yaffs2 is better than ext4 for NAND memory.
I need to research a bit more on this matter.
I am here to learn.Thanks for sharing.
termagazis said:
how can we check the type of our partitions?
Click to expand...
Click to collapse
FOUND IT! :D
Install Terminal emulator
AND TYPE THIS:
su
Click to expand...
Click to collapse
df
Click to expand...
Click to collapse
It gives you all the info you need. If you won't type su, it would not give you MTD partitions' info.
Searched this http://www.computerhope.com/unix/udf.htm according to the image shown here http://forum.xda-developers.com/showthread.php?t=1566846 did I realised that.
400 for system is excessive, should be safe to bring down to 300, forget vendor 6m is not worth worrying.
With /cache that could be another 200mb for data.
Also boot is a worry, formatting the blocks of mtd doesn't appear to work, could rewrite the array, but may kill boot, which would be a hard brick.....
Sent from my MT11i using XDA
Yaffs designed for nand flash based embedded systems
Ext4 is not for that
Sent from my MT11i using XDA
leajian said:
FOUND IT! :D
Install Terminal emulator
AND TYPE THIS:
It gives you all the info you need. If you won't type su, it would not give you MTD partitions' info.
Searched this http://www.computerhope.com/unix/udf.htm according to the image shown here http://forum.xda-developers.com/showthread.php?t=1566846 did I realised that.
Click to expand...
Click to collapse
in the image you gave it doesnt say in what format is every partition.(yaffs or ext3,ext4)
termagazis said:
in the image you gave it doesnt say in what format is every partition.(yaffs or ext3,ext4)
Click to expand...
Click to collapse
In that case, just time
mount
Click to expand...
Click to collapse
in Terminal Emulator and see that every partition is reported on what filesystem it is.
More info @ http://www.cyberciti.biz/faq/linux-how-to-determine-find-out-file-system-type/
Or run it as root
Sent from my MT11i using XDA
yacloo said:
Yaffs designed for nand flash based embedded systems
Ext4 is not for that
Sent from my MT11i using XDA
Click to expand...
Click to collapse
Before you will notice any degradation of NAND, you will sell this phone and forget about it, so...
I made a mess
do I change file system? dont i change it? good or bad?
Actually, it is that easy.
However, all the kernels are set to mount as yaffs, so you also need to unpack and edit the config files in the kernel too.
Sent from my MT11i using XDA
While trying to restore an old backup of stock 2.3.6 on my Atrix 4g (ATT) from Jokersax CM9, I recieved an error while restoring "/system". This is what showed up:
Rom Manager version 5.0.0.7
August 22, 2012
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error while restoring /system!
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log.
Please open ROM Manager to report the issue.
A bit of background...So, I rooted and unlocked the bootloader of my Atrix 4g about two weeks ago, and everything went fine. I then decided to flash Jokersax CM9 on my Atrix, so I backed up the stock 2.3.6 that I was on at that time. I then used CM9 for the next two weeks, but then decided I wanted to go back to stock, and I received the error. Btw, I used ROM Manager for backups and restore, and had flashed CWM recovery properly. Also, the backups I had created of CM9 earlier wouldn't restore because of the missing MD5 file.
I was curious why it wouldn't restore properly. Is it just a bad backup or is something wrong with my internal sd card? Anyway, what should I do if I want to restore the backup?
Thanks in Advance!
Anything interesting or useful in /sdcard/clockworkmod/recovery.log?
No file
ravilov said:
Anything interesting or useful in /sdcard/clockworkmod/recovery.log?
Click to expand...
Click to collapse
Actually if I go into /sdcard/clockworkmod, I can't find the recovery.log file. It might have been moved but I don't recall ever messing with the files.
Md5sum miss match possibly?
Sent from my MB860 using xda premium
Md5sum mismatch
stevendeb25 said:
Md5sum miss match possibly?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
If it was Md5sum mismatch, how would I fix it?
Actually I didn't rename the backup and it has no spaces, so I don't know what it would be...
According to your log, there is nothing wrong with your backup, or else the "Checking MD5 sums" part would have caught it.
There is also no way of a MD5 sum mismatch, for the same reason.
The only thing I can think of is there's something wrong with copying the backup to the phone (specifically, the /system partition). You can hook the phone to the computer right after you try restoring the backup and run adb shell, then run this:
Code:
cat /cache/recovery/log
cat /cache/recovery/last_log
See if that has something revealing.
Or, maybe the recovery has some problems wiping your /system for some reason. In that case, you can also try this (also within adb shell):
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p12 bs=512 count=1000
That will wipe the beginning of the /system partition, so the recovery will be forced to format it. Use this at your own risk.
Then after that try restoring your backup again.
ravilov said:
According to your log, there is nothing wrong with your backup, or else the "Checking MD5 sums" part would have caught it.
There is also no way of a MD5 sum mismatch, for the same reason.
The only thing I can think of is there's something wrong with copying the backup to the phone (specifically, the /system partition). You can hook the phone to the computer right after you try restoring the backup and run adb shell, then run this:
Code:
cat /cache/recovery/log
cat /cache/recovery/last_log
See if that has something revealing.
Or, maybe the recovery has some problems wiping your /system for some reason. In that case, you can also try this (also within adb shell):
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p12 bs=512 count=1000
That will wipe the beginning of the /system partition, so the recovery will be forced to format it. Use this at your own risk.
Then after that try restoring your backup again.
Click to expand...
Click to collapse
I'll definitely try that, I'm not gonna have a chance to do it soon though. I'll get back to you as soon as I do.
Thanks for all the answers anyway!
Did this work? I have had a similar issue with my Atrix, too. I can do an "Advanced Restore" and restore all partitions but /system.
Issue restoring stock rom backup
I loaded epritner's CM10 rom and am getting the same error when attempting to restore the backup of the stock rom. Reviewing the report.log i see that there is a space issue writing to the \system partition but dont know how to proceed. Any help would be appreciated. Attached is the log output...
Restoring system...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.11 (14-Mar-2010)
Setting current mount count to 1
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
/dev/block/mmcblk0p12: 11/81920 files (0.0% non-contiguous), 20632/327680 blocks
deleted
nvmm_sorensondec.axf
deleted
Protips.apk
deleted
CarDock.odex
deleted
GoogleServicesFramework.odex
deleted
Glam_alert.ogg
deleted
libopencore_player.so
deleted
tar: write error: No space left on device
defaults.xml
deleted
Error while restoring /system!
result was NULL, message is: assert failed: restore_rom("/sdcard/clockworkmod/backup/Atrix4g", "boot", "system", "data", "cache", "sd-ext")
in2slack said:
I loaded epritner's CM10 rom and am getting the same error when attempting to restore the backup of the stock rom. Reviewing the report.log i see that there is a space issue writing to the \system partition but dont know how to proceed. Any help would be appreciated. Attached is the log output...
Click to expand...
Click to collapse
in2slack, did you try these steps from ravilov? If so, did you get an error?
ravilov said:
According to your log, there is nothing wrong with your backup, or else the "Checking MD5 sums" part would have caught it.
There is also no way of a MD5 sum mismatch, for the same reason.
The only thing I can think of is there's something wrong with copying the backup to the phone (specifically, the /system partition). You can hook the phone to the computer right after you try restoring the backup and run adb shell, then run this:
Code:
cat /cache/recovery/log
cat /cache/recovery/last_log
See if that has something revealing.
Or, maybe the recovery has some problems wiping your /system for some reason. In that case, you can also try this (also within adb shell):
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p12 bs=512 count=1000
That will wipe the beginning of the /system partition, so the recovery will be forced to format it. Use this at your own risk.
Then after that try restoring your backup again.
Click to expand...
Click to collapse
Were you able to find a solution? I'm facing the exact same issue
Same here I installed the AtrICS ROM for a play around after backing up my MIUI ROM. Decided to go back to the MIUI ROM and I get the error when trying to restore. I've got a load of application data that I've lost if I can't get this ROM restored. It seems that the AtrICS ROM, as good as it is, has changed something.
Any thoughts anyone? It seems to be a file system thing? As if the System partion is the wrong type, or not large enough?
I went back from atrICS to epinter by backup today. I had no problems what so ever so it is not an atrICS related issue, my steps were:
1. format /cache
2. format /data
3. format /system
4. format /dalvik-cache
5. recover epinter
have you tried to use format system before recovery? maybe there is some residual file that can't be overwritten...
Thanks for your reply.
I did try formatting System before restoring and still got the same error when restoring.
However, I ignored it and rebooted and I was back at MIUI and able to recover my files
I've the exact same problem.
In the /cache/recovery/last_log, I've found a message:
write error: No space left on device
Click to expand...
Click to collapse
I don't understand why there is no space left on /system... the size of partitions should not change, isn't it?
After checking /system partition size and system backup, I saw that the backup completely fills the partition:
[email protected]:/ # df
Filesystem Size Used Free Blksize
[...]
/system 309M 309M 3K 1024
[...]
Click to expand...
Click to collapse
I faced the same issue
I faced the same issue and would request experienced users to take a look at my log file and advise me
Okay did anyone try anything of this I faces same problem and idk what to do.
Solved - Non conventional method
I solved this problem using a non conventional method.
I used "advanced restore" to restore boot, data and cache.
So, I copied "system.ext3.tar" to my computer and extract it using winrar. Then, using the files I created a flashble zip and flash it using "install zip" option.
It worked!
If someone wants, I could post a tutorial here later.
danilocps87 said:
I solved this problem using a non conventional method.
I used "advanced restore" to restore boot, data and cache.
So, I copied "system.ext3.tar" to my computer and extract it using winrar. Then, using the files I created a flashble zip and flash it using "install zip" option.
It worked!
If someone wants, I could post a tutorial here later.
Click to expand...
Click to collapse
Sorry to ressurect the topic, but I can't restore even /system and /data.. gives me error, and MD5 is fine.
Backing up .android_secure...
.
com.trust5.odp-1.asec
com.quoord.tapatalkxda.activity-1.a
com.loudtalks-1.asec
com.whatsapp.wallpaper-1.asec
com.music.download-1.asec
com.facebook.orca-1.asec
me.pou.app-2.asec
com.kiloo.subwaysurf-2.asec
com.davidamado.MetalGearOuterHeaven
Backing up cache...
.
lost+found
dalvik-cache
recovery
last_log
log
No sd-ext found. Skipping backup of sd-ext.
Generating md5 sum...
chmod: /sdcard/clockworkmod/blobs/02c/§☻‼/♀~|♫: No such file or directory
chmod: /sdcard/clockworkmod/blobs/235/∟/☺>☼>♣~: No such file or directory
Backup complete!
Checking MD5 sums...
boot.img: OK
cache.ext4.dup: OK
data.ext4.dup: OK
system.ext4.dup: OK
.android_secure.vfat.dup: OK
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/2013-06-30.03.16.22//data.ex
t4.dup
Restoring data...
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
warning: wipe_block_device: Discard failed
Unable to copy file ./backup/processed
data
user
0
idd
etc
bluetooth_bdaddr
wlan_macaddr
light_themes
GNB_DEBUG.txt
backup
processed
Error while restoring /data!
Click to expand...
Click to collapse
Can someone answer that? Thank you!!
I have the same issue
danilocps87 said:
I solved this problem using a non conventional method.
I used "advanced restore" to restore boot, data and cache.
So, I copied "system.ext3.tar" to my computer and extract it using winrar. Then, using the files I created a flashble zip and flash it using "install zip" option.
It worked!
If someone wants, I could post a tutorial here later.
Click to expand...
Click to collapse
Can you please post a tutorial? I am experiencing the same issue.
Edit : I've searched the whole internet and some say that i can't restore the system because my cwm backup of the stock system is to large (315 MB to be precise) while the system partition has 320 MB.It look like i need to have more free space, like 10-15MB .Any ideas on how i might to that?