Database Users

Nandroid won't backup my ext4 partition?

I'm currently using data2ext with B 0.8, and I have a 2gb ext4 partition. I tried performing a backup using BlaY0's "Customized CWM 3.0.1.3 fake-flash with ext4 support". However, I get a message saying something along the lines of "Couldn't mount sd-ext. Sd-ext backup may not be supported on this device."
Any ideas? Is it unable to backup a ext partition larger than 1gb? Is there any alternative to a nandroid backup?
EDIT: Damn, is this cause I cheated when partitioning the SD card?

I guess the problem is in ext4 feature huge_files. Even tho my customized CWM has ext4 support, it lacks huge files support (files over 2TB). This feature however is set by default when formatting ext4 partition. It can be turned off using tune2fs. Consult mr. Google on how to use tune2fs.
Sent from my HTC Legend

i tried turning off huge_file support but i still cant nandroid the ext4 partition created with the customised fake flash.
from adb shell in latest CWM recovery i tried:
tune2fs -O ^huge_file /dev/block/mmcblk0p2
/data/data/com.koushikdutta.rommanager/files/e2fsck -fpDC0 /dev/block/mmcblk0p2
Click to expand...
Click to collapse
then rebooted but still not love with nandroid mountind the ext4 partition

fixed my problem:
i had reverted to using CWM 2.5.0.7 gui / update.zip which does not support ext4
so going back to blay0's custom update.zip (3.0.1.3) I can now nandroid backup my ext4 partition. (i have still got huge_files turned off as per above)
Just dunno how to use blay0s version with rom recovery gui, but no biggie

[Q]help i soft bricked my phone

hi guys i am in a big mess
1)i tried installing official 2.3.5 final and my phone(u8800) started bootlopping after factory reset i managed to start it once.
2)i restarted my phone after rooting it and had again bootloops that i didnt ever manage to overcome.
3)so i desided that i should reflash official(and the desaster started)update failed on 99% and the worst bootloader locked .
4)i tried installing an official froyo also failed at 99% but bootloader unlocked
5)now i am on ubuntu able to see pink screen files but unfortunately i dont have dd back up but i have many back ups from cwm on my sd from custom roms is there any posibility to unbrick my phone?
ps for admin sorry for same thread but the other started writing in some unknown language to me

Can you access recovery?
So you downgraded to 2.2, which version B138?
can you try to access recovery? official will do for factory reset, if doesn't start again try to flash it again, and after that do wipe and factory reset from recocery...
I managed to downgrade like that also failed at 99% but with factory reset the phone started normally...

Atanasov Goran said:
So you downgraded to 2.2, which version B138?
can you try to access recovery? official will do for factory reset, if doesn't start again try to flash it again, and after that do wipe and factory reset from recocery...
I managed to downgrade like that also failed at 99% but with factory reset the phone started normally...
Click to expand...
Click to collapse
1)yes my 2.2 froyo is 138 from how to root ginerbred thread and after this flash i lost adb compatibility in windows so now i am in ground zero if ther is a way to flash something from ubuntu or backtrack in bootloader mode because even after that still no access to phone not even from pc on cwm to see my sd card
2)in simple boot my phone stacks on huawei logo,i can also get to recovery menu and finaly and i think the most helpfull i can get pink screen and mount my files on linux.
3)i have also try to recover in last saved working recovery (custom rom)
4)i think that something went wrong with my partitions but i realy need help from a developer because i dont know what to do

try this
try to wipe/factory reset from the official recovery, should start normaly after that, my phone did the same when i downgraded from 2.3 stoped at 99% and said that the update failed but after a factory reset booted normaly

Maybe a partition is damaged.
Try from linux on pink screen to check partitions for errors. Maybe you can fix it like this and after to successfully flash the update.

dancer_69 said:
Maybe a partition is damaged.
Try from linux on pink screen to check partitions for errors. Maybe you can fix it like this and after to successfully flash the update.
Click to expand...
Click to collapse
can you give some info how to do that i see 3 partitions of 105mb,235 and recovery partition only who auto mount and on gparted i see 4gb unreachable
do you mean just to check disk this partitions ?

I haven' t specific infos, I'm using linux very rear the last year. I think that you can use the fsck tool of linux. You can find a lot of info about how to check partitions for linux if you search on google. Just be careful to not format them or erase them.

Tranos said:
can you give some info how to do that i see 3 partitions of 105mb,235 and recovery partition only who auto mount and on gparted i see 4gb unreachable
do you mean just to check disk this partitions ?
Click to expand...
Click to collapse
You should see 13 partitions total if you look at the drive with parted or gparted etc.. And yeah you could run fsck on all the ext3/ext4/fat32 partitions. But if you don't see all the 13 partitions in parted / gparted then I think the partition table is damaged or some weird bootloader lock issue.

after some tries and stock reflashes i am now on official cwm recovery and trying to wipe data/factory resets returns me an error :
E:cant mount @(or /dev/block/mmcblk0p13) both wipe and format same error
can you candly send me the official recovery files and what should i have in(i think something after so many custom roms failed)
and this are the partitions i can see now

You could run gparted and note down all partitions which are ext3, ext4 or fat32. Then you can check the disks with "sudo fsck /dev/sdxx". Also I can post my partition table later when I'm on my comp so you could compare it to yours.
Sent from my u8800 using xda premium

thies are all partitions but i think there are too many anallocated
Code:
GNU Parted 2.3
Using /dev/sdd
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Error: Invalid partition table on /dev/sdd -- wrong signature 0.
Ignore/Cancel? i
Model: Qualcomm MMC Storage (scsi)
Disk /dev/sdd: 3959MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 252MB 252MB primary fat32
2 252MB 252MB 512kB primary boot
3 252MB 255MB 3072kB primary
4 255MB 3959MB 3704MB extended
5 268MB 281MB 12,6MB logical
6 336MB 472MB 136MB logical ext3
7 537MB 537MB 512kB logical
8 604MB 607MB 3146kB logical
9 671MB 678MB 7168kB logical
10 738MB 741MB 3146kB logical
11 805MB 808MB 3146kB logical
12 872MB 1103MB 231MB logical ext3
(parted)
2 partitions are missing

Here's how mine looks. I'm guessing you don't have a dd backup of the whole phone? Anyway if your partition table is messed up, it would be possible to clone my partition table. Only the partition table, and leaving all other data intact. It would probably be a good idea also to check with others if the partition table is always exactly the same on all phones, or if there are different flash mems or something with diff. tables. Also did you run fsck on 1,6,12 and 13?
Code:
$ [B]sudo parted /dev/sdc[/B]
GNU Parted 2.3
Using /dev/sdc
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) [B]p[/B]
Model: Huawei eMMC Storage (scsi)
Disk /dev/sdc: 3959MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 252MB 252MB primary fat32
2 252MB 252MB 512kB primary boot
3 252MB 255MB 3072kB primary
4 255MB 3959MB 3704MB extended
5 268MB 281MB 12.6MB logical
6 336MB 472MB 136MB logical ext4
7 537MB 537MB 512kB logical
8 604MB 607MB 3146kB logical
9 671MB 678MB 7168kB logical
10 738MB 741MB 3146kB logical
11 805MB 808MB 3146kB logical
12 872MB 1103MB 231MB logical ext2
13 1141MB 1770MB 629MB logical ext4
14 1812MB 3959MB 2147MB logical fat32
(parted)

do you know how ican fix my partitions again or should i sent it to service tbh it is huawei fault that my phone doesnt work now

I checked my partition table(I have 2.3 installed, not 2.2) and are same that ksata' s, except partition 12 which is in ext3, not ext2.
But I think that on 2.2 rom the partition table has 12 partitions and not 14(I've used command cat /proc/mounts some times when a was on 2.2 rom and always partitions count was until 12). So, I don' t think that it' s something wrong with the partition table.
But maybe some of the existing partitions is damaged and when update tries to write on it, gets an error and update stops.
You can check the ext2/3/4 partitions from gparted. First umount a partition end then check it(if you right click on a partition these options are available on the menu)

Looks like I have bricked mine too.. pretty badly. When updating to 2.3 if fails at step 2 (40 %) and shows "update failed" (same with 2.2). Can't access recovery either. In pink screen Windows and Ubuntu doesn't mount any partitions..
Looks like I have to send it in to change motherboard, but if any have suggestions how to fix it please tell me
ps. was on Cm7 before this happened.

skifyr123 said:
Looks like I have bricked mine too.. pretty badly. When updating to 2.3 if fails at step 2 (40 %) and shows "update failed" (same with 2.2). Can't access recovery either. In pink screen Windows and Ubuntu doesn't mount any partitions..
Looks like I have to send it in to change motherboard, but if any have suggestions how to fix it please tell me
ps. was on Cm7 before this happened.
Click to expand...
Click to collapse
Try to flash using internal SD card. Also, one user reported that removing battery worked.

Blefish said:
Try to flash using internal SD card. Also, one user reported that removing battery worked.
Click to expand...
Click to collapse
How to access internal when you can't boot (not even to recovery)? Tried to remove battery, but didn't work..

1)i managed to solve my problem by using the genokolars re-partition to stock from modaco and the partition zip that is at a reply of him not post start thank you everybody for the try .and after reflashed the chinese stock 162
2)but now i have nulled imei can i restor it by some clock works recoveries or ther is no way to restore it(i dont have dd back up)

skifyr123 said:
How to access internal when you can't boot (not even to recovery)? Tried to remove battery, but didn't work..
Click to expand...
Click to collapse
Have the same issue. Did you try to work it out somehow?
Try look at my thread here:
http://forum.xda-developers.com/showthread.php?t=1466953

[Q] Can't mount /dev/block/mmcblk0p8

I would like some help please.
Have bricked my a500 during attempt to falsh vach leaked ICS.
Switchme was used before clearing data and I forgot to delete a profile. This is I think the cause of my problem.
I cannot proceed with any ROM flashing until data partition is cleared.
I am using RA-ICONIA-3.15 recovery kernel.
I can mount and format CACHE SYSTEM FLEXROM partitions.
Attempting to mount data this is the message
E:Can't mount /dev/block/mmcblk0p8 (File exists)
Now my poor A500 will not get past 'acer'screen when trying to boot.
Question 1: How can I restore access to the DATA partition?
Question 2: How do I wipe my internal storage and start over?
I have a nand backup before this started on external SD card. Uncertain if I should restore this.
Thanks in advance.

DrPlumEU said:
I would like some help please.
Have bricked my a500 during attempt to falsh vach leaked ICS.
Switchme was used before clearing data and I forgot to delete a profile. This is I think the cause of my problem.
I cannot proceed with any ROM flashing until data partition is cleared.
I am using RA-ICONIA-3.15 recovery kernel.
I can mount and format CACHE SYSTEM FLEXROM partitions.
Attempting to mount data this is the message
E:Can't mount /dev/block/mmcblk0p8 (File exists)
Now my poor A500 will not get past 'acer'screen when trying to boot.
Question 1: How can I restore access to the DATA partition?
Question 2: How do I wipe my internal storage and start over?
I have a nand backup before this started on external SD card. Uncertain if I should restore this.
Thanks in advance.
Click to expand...
Click to collapse
try this
If you are using Thor's CWM. And his recovery only;
Here are the steps to completely wipe all internal data. And give it a clean internal system (according to Thor)
Note: Optional Formatting.
If you really want to remove EVERYTHING in Internal Memory, at this point, go to Backup and Restore. Select "Toggle backup and restore of internal storage (/data/media). Enable this setting by selecting it. By default, it is disabled. Then proceed to the formatting steps. This will format the Entire Internal Memory when you proceed.
Note, this will format EVERYTHING in internal memory (not ext sd card)
Select Go Back, Goto Mounts and Storage
1. Format System
2. Format Cache
3. Format Dalvik
4. Format Flexrom
After you reboot, I believe it resets back to the defaults.
try to install the rom with the normal procedures.
this what i used and it worked great no problems
note** i am just fowarding info that was passed to me. and this will erase you backups
---------------------------------------------------------------------------------------------
IF you are running RA Revamped Recovery, then you may want to contact Drellisdee at his thread;
http://forum.xda-developers.com/show....php?t=1459821
He knows the procedures to do the same.it's a tricky process, and he knows more about his recovery than I do.

Thank you for the prompt response. Already tried your recipe with no luck.
I need access to the DATA partition and do not know how to go about that. Once have access to the internal disk, would like to know how to completely wipe this if that what it takes.
Thanks
PS: If I truly have bricked the device it is still in 12mo warranty, so will contact Acer care centre if no tricks work.
PPS: Maybe I now have excuse needed to upgrade to Tegra 3 device. The Acer Iconia A700 looks tempting

i think i have seen something like that when fixing mine but did not touch it....as im not a pro, hopefully somone with a litle more in depth knowledge sees this and can help.
sorry

Have you tried restoring your nandroid backup? This has recovered the error for me on my phone before when the /data partition became corrupt. Worth a shot.

Sadly, restoration of the nandroid backup was not successful.
I have notice that I pressed wrong volume button when attempting the hard reset. Will try the correct procedure later after work. Hopefully a proper hard reset then restore with one of Vache stock roms will have me up and running.
UPDATE: Sadly hard reset fails to load. My poor a500 needs resuscitation at acer clinic

I had the exact same problem, although I caused the problem in a different manner. You need to be able to use adb to get it going again. If you are not familiar with adb, do a search and you can find plenty of help. That's what I had to do. Unfortunately, my skills with adb are pretty much non-existent, so I can't really help you with that part.
Once you get adb going on your computer and it recognizes your A500, follow these steps:
You will need to boot into my recovery and open adb shell.
This will cause loss of all data contained on /data which will lose your /data/media.
From adb shell:
mount (This is to check data isn't mounted. If mounted use "umount data")
mke2fs -j -b 4096 /dev/block/mmcblk0p8
tune2fs -O extents,uninit_bg,dir_index -C 1 /dev/block/mmcblk0p8
e2fsck -fy /dev/block/mmcblk0p8
After this is done your file system on /data will be fixed. You can install the ROM of your choice. Good luck!
(These instructions were originally provided to me by drellisdee)

Thanks for the answer on your previous post. I fixed my /data mount.
Love to unbrick my acer for the 50th time
Did not have this error tho, before I tried to convert the /data mount to ext4

DrPlumEU said:
I would like some help please.
Have bricked my a500 during attempt to falsh vach leaked ICS.
Switchme was used before clearing data and I forgot to delete a profile. This is I think the cause of my problem.
I cannot proceed with any ROM flashing until data partition is cleared.
I am using RA-ICONIA-3.15 recovery kernel.
I can mount and format CACHE SYSTEM FLEXROM partitions.
Attempting to mount data this is the message
E:Can't mount /dev/block/mmcblk0p8 (File exists)
Now my poor A500 will not get past 'acer'screen when trying to boot.
Question 1: How can I restore access to the DATA partition?
Question 2: How do I wipe my internal storage and start over?
I have a nand backup before this started on external SD card. Uncertain if I should restore this.
Thanks in advance.
Click to expand...
Click to collapse
If you switch the A500 off and whilst switching it on hold the volume up button and start toggling the rotation lock on and off it should clear the internal memory completely. Then flash an update.zip from a MicroSD. Otherwise use the Iconia software update tool that's floating around in APX mode. Make sure you have your UID for this

Ping192 said:
Did not have this error tho, before I tried to convert the /data mount to ext4
Click to expand...
Click to collapse
That's exactly what caused my problem. Glad you are working again.

Resolved by great customer support...
To close this thread I wish to congratulate the Acer customer support team in Plymouth who have restored my Acer Iconia A500 to working order in under a week.
It is upgraded OTA to Android 3.2.1.
As still in warranty, no charge for the failure of the hard-drive partitioning!
Great work. Good customer service.

thanks lovable people in this thread
thanks lovable people in this thread you solved my problem . especially Dr. McKnight (23rd February 2012, 03:48 PM) back in the beginning of the thread. His solution using thor's recovery was enough to solve my problem. Wonderful and thank you
/Mikkel

spoupard said:
From adb shell:
mount (This is to check data isn't mounted. If mounted use "umount data")
mke2fs -j -b 4096 /dev/block/mmcblk0p8
tune2fs -O extents,uninit_bg,dir_index -C 1 /dev/block/mmcblk0p8
e2fsck -fy /dev/block/mmcblk0p8
Click to expand...
Click to collapse
When I do the "mke2fs -j -b 4096 /dev/block/mmcblk0p8" command from adb's shell, it takes forever (I let it run for hours). Something I was thinking about, could I simply "rm -rf /dev/block/mmcblk0p8" first, and then run the above commands? Also, should I not add the "-t ext4" option to the mke2fs command?

kerijan2003 said:
When I do the "mke2fs -j -b 4096 /dev/block/mmcblk0p8" command from adb's shell, it takes forever (I let it run for hours). Something I was thinking about, could I simply "rm -rf /dev/block/mmcblk0p8" first, and then run the above commands? Also, should I not add the "-t ext4" option to the mke2fs command?
Click to expand...
Click to collapse
Try in fastboot mode execute:
fastboot -w

[Q] Yet another bricked defy. can't restore cwm backup

Hi,
well... what can i say... i bricked my beloved defy. =(
How it happened:
Since Quarx's CyanogenMod 7 i used several CyanogenMod Versions from Quarx und Epsylon until about 2 weeks ago. I had the CM10 (4.1.2) Version from 11.05. installed.
Then i saw Quarx new release from 16.06.
Before i flashed the new version i made a full backup with cwm 5.7.0. Then i installed the new version trough cwm. everything look fine. But there wen't something really wrong. After rebooting the phone got stuck even before 2ndinit. I tried it several times but the the phone wasn't booting any more.
I thought: no problem. I have a backup. Let's restore is quickly. The easiest way to me was:
- start the phone in bootloader
- flash a stock sbf with rsd lite (sbf: JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_UCAJRDNFRYORTCOREEU_P023_A008_HWp3_Service1FF.sbf
- root the phone with superoneclick
- install 2ndinit for defy (SndInitDefy_2.3.apk i think it's cwm 5.0.3.1)
- restore backup
but here the problem beginns trying to recover /system(log from recovery):
2013-06-17.15.18.36:
logo.img is present. 1024 kB
recovery.img is present. 8192 kB
devtree.img is present. 512 kB
boot.img is present. 8192 kB
data.ext3.tar is present. 1039389 kB
system.ext3.tar is present. 323612 kB
Checking MD5 sums...
./system.ext3.tar: OK
I:couldn't find default type
Found new backup image: /sdcard/clockworkmod/backup/2013-06-17.15.18.36//system.ext3.tar
Restoring system...
Skip system unmount, remount read-only
Remount /system read-only
I:/system is not safe to format
I:Erasing from device...
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Skip system unmount, remount read-only
Remount /system read-only
50-cm.sh60-baseband.sh70-bootmenu.sh70-gapps.sh80-battd.shApollo.apkApplicationsProvider.apkAudioEffectSettings.apkBackupRestoreConfirmation.apkBluetooth.apkBrowser.apkCMFileManager.apkCMFileManagerThemes.apkCMWallpapers.apkCalculator.apkCalendar.apkCalendarProvider.apk
..... and so on and so on. (is quite a long list ).....
Error while restoring /system!
Problem while restoring system !
-------------------------------------------------------
i tried so many things like:
- install cm10 an try restoring with cwm 5.7.0 (same error)
- different stock sbf's (makes no difference)
- extracting system.ext3.tar and copying i to /system with adb (stops copying at about 50%)
and much much more... i forgot the rest ^^
the thing is.... i have no idea what exactly is going wrong. In my opinion it's here in the log: "Remount /system read-only". how should cwm be able to write the backup into system i it is mounted as "read-only".
im working on it since the last 2 weeks and it is getting super frustrating =(
Hopefully someone has better ideas than me? I would appreciate it.
At least: thanks for reading!

There are 2 possibilities according to me (I may be wrong:silly
1. Your backup might be corrupt -> try another backup
2. Your eMMC memory chip may be corrupt -> send your phone for service
TRY Wipe system cache and data then restore.
OR
Install CM10 with cwm (example 26 March build), restore only data, then dirty flash the latest CM10 (only wipe cache and dalvik). Old builds of CM10 can cause problems.

hotdog125 said:
There are 2 possibilities according to me (I may be wrong:silly
1. Your backup might be corrupt -> try another backup
2. Your eMMC memory chip may be corrupt -> send your phone for service
TRY Wipe system cache and data then restore.
OR
Install CM10 with cwm (example 26 March build), restore only data, then dirty flash the latest CM10 (only wipe cache and dalvik). Old builds of CM10 can cause problems.
Click to expand...
Click to collapse
Thank you for your answer!
I believe the backup files are ok. md5 is ok and the recovery log says: backup ok, but internal storage.... is weired.
Maybe a fried eMMC. But how? And buying a new phone is sadly way cheaper than service.
I wiped cache and data endless times. But no luck.
Is it possible to wipe (format) system?
I installed different versions from cm10 and they are running fine. But i really would like to restore my backup. There's a lot of work in it. =(
Tried this also 2 times: http://forum.xda-developers.com/showthread.php?t=1807899
But with this method, the phone won't boot up and got stuck in a bootloop. Can't even see the cm logo. An it makes no difference what version of CM10 is installed.

dediknight said:
Thank you for your answer!
I believe the backup files are ok. md5 is ok and the recovery log says: backup ok, but internal storage.... is weired.
Maybe a fried eMMC. But how? And buying a new phone is sadly way cheaper than service.
I wiped cache and data endless times. But no luck.
Is it possible to wipe (format) system?
I installed different versions from cm10 and they are running fine. But i really would like to restore my backup. There's a lot of work in it. =(
Tried this also 2 times: http://forum.xda-developers.com/showthread.php?t=1807899
But with this method, the phone won't boot up and got stuck in a bootloop. Can't even see the cm logo. An it makes no difference what version of CM10 is installed.
Click to expand...
Click to collapse
Yes, wiping system is important in this case. The option is present on the main screen of CWM.

hotdog125 said:
Yes, wiping system is important in this case. The option is present on the main screen of CWM.
Click to expand...
Click to collapse
I would like to format /system. But how? I can't find this option in cwm (5.7.0).
- Reboot system now
- Apply update from sdcard
- Wipe data/factory reset
- Wipe cache partition
- Install zip from sdcard
- Backup and restore
- Mounts and storage
- Advanced
- Power off
- Exit Recovery
- Go Back
It is possible to format some unmounted partitions in "Mounts and storage". But if i unmount /system there is only the option to "remount /system" but nothing linke "format /system".

dediknight said:
I would like to format /system. But how? I can't find this option in cwm (5.7.0).
- Reboot system now
- Apply update from sdcard
- Wipe data/factory reset
- Wipe cache partition
- Install zip from sdcard
- Backup and restore
- Mounts and storage
- Advanced
- Power off
- Exit Recovery
- Go Back
It is possible to format some unmounted partitions in "Mounts and storage". But if i unmount /system there is only the option to "remount /system" but nothing linke "format /system".
Click to expand...
Click to collapse
My bad. You can try Defy full wiper (DO NOT REBOOT AFTER FULL WIPE).

hotdog125 said:
My bad. You can try Defy full wiper (DO NOT REBOOT AFTER FULL WIPE).
Click to expand...
Click to collapse
Thank you very much. Sadly, it wasn't the solution to my Problem. But the error messages getting a bit clearer now ^^.
Here is the recovery log:
-- Installing: /sdcard/defy_fullwipe_ext3.zip
Finding update package...
I:Update location: /sdcard/defy_fullwipe_ext3.zip
Opening update package...
Installing update...
FULL WIPE FOR MOTO DEFYmount: failed to mount /dev/block/mmcblk1p21 at /system: Device or resource busy
mount: failed to mount /dev/block/mmcblk1p25 at /data: Device or resource busy
mount: failed to mount /dev/block/mmcblk1p24 at /cache: Device or resource busy
.
..
...
....
.....
......
.......
........
.........
..........
...........
***********
script result was [because /system got wiped]
Congrats, your ass is now wiped
!!Do not reboot now!!
If you do, you will have to flash an SBF
because /system got wiped
Install from sdcard complete.
2013-06-17.15.18.36:
logo.img is present. 1024 kB
recovery.img is present. 8192 kB
devtree.img is present. 512 kB
boot.img is present. 8192 kB
data.ext3.tar is present. 1039389 kB
system.ext3.tar is present. 323612 kB
Checking MD5 sums...
./system.ext3.tar: OK
I:couldn't find default type
Found new backup image: /sdcard/clockworkmod/backup/2013-06-17.15.18.36//system.ext3.tar
Restoring system...
Skip system unmount, remount read-only
Remount /system read-only
E:format_volume failed to unmount "/system"
Error while formatting device /system!
Problem while restoring system !
--End of log--
OK, somehow the devices are "busy" so the wipe script couldn't wipe. Although in cwm it said it was successful.
So i tried unmounting /system, /cache and /data before running the script. Here's what i got:
-- Installing: /sdcard/defy_fullwipe_ext3.zip
Finding update package...
I:Update location: /sdcard/defy_fullwipe_ext3.zip
Opening update package...
Installing update...
FULL WIPE FOR MOTO DEFYmount: failed to mount /dev/block/mmcblk1p21 at /system: Device or resource busy
mount: failed to mount /dev/block/mmcblk1p25 at /data: Invalid argument
mount: failed to mount /dev/block/mmcblk1p24 at /cache: Device or resource busy
unmount of /data failed; no such volume
script result was [because /system got wiped]
.
..
...
....
.....
......
.......
........
.........
..........
...........
***********
Congrats, your ass is now wiped
!!Do not reboot now!!
If you do, you will have to flash an SBF
because /system got wiped
Install from sdcard complete.
--End of log--
Is it possible to do something about the "busy" partitions. Whatever they're busy doing

Check out these threads, not sure they'll help - http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/.
AND http://forum.xda-developers.com/showthread.php?p=20707200
Your partitions may be in the wrong format.
EDIT - You can try starting from sbf, then installing your preferred CM10 release, and then extracting the backups into the respective directories using ES file explorer (only the files that you've changed).
EDIT 2 - Install CM10 with clockworkmod (not TWRP) and then go to bootmenu (press go back on the main screen of recovery), and then format system and data to ext4, and then try restoring backup. <------ try this first

why??
sir. i tried this 2 xperia ROM. my unit is OT 918n. i completed the installation of BRAVIA_LACV--Es_V4 & Xperia by Jarey..
why is it the screen wont work. i mean the touch panel. so i can setup the setting at 1st boot. why it wont work the touch panel??
and 1 thing. i backup 1st my phone before i follow this instraction. just keeping safe. and if i restore the backup it stock in the white alcatel with sounds. just in their always repeating it will not continue to the main menu. WHy? can you answer it please.

chawnix said:
sir. i tried this 2 xperia ROM. my unit is OT 918n. i completed the installation of BRAVIA_LACV--Es_V4 & Xperia by Jarey..
why is it the screen wont work. i mean the touch panel. so i can setup the setting at 1st boot. why it wont work the touch panel??
and 1 thing. i backup 1st my phone before i follow this instraction. just keeping safe. and if i restore the backup it stock in the white alcatel with sounds. just in their always repeating it will not continue to the main menu. WHy? can you answer it please.
Click to expand...
Click to collapse
You are in the wrong device forum.
Sent from my Nexus 7 using Tapatalk

:good::fingers-crossed:Thank you, i have a similar problem. My battery's Defy was completly discharge. Normaly, i plug my Defy, wait for 10 % charging, and i turn it on and i let the battery charging all night. But, i forgot to turn my defy on, and the morning when i turn it on, the cyanogen 7 logo bootloop.
I do a wipe system reset to factory, the defy turn on, and when i restore my backup, bootloop again.
I do what hotdog125 write, i was thinking its works, but it didn't.
I lost my data, :crying::crying::crying::crying: but i have a nice cyanogen 10 bootloop :laugh::laugh::laugh:

I finaly restore my defy with a backup do with recorvery when my phone make a bootloop.
I put cyanogen 7 and i found an application name Nandroid Manager http://forum.xda-developers.com/showthread.php?t=2044414 , 1,46 euros, that permit to restore all or a part of the backup you do.
I restore my apps, my sms, my mms, my call log etc... i want to keep. My contact was backup on my gmail account.
Like i saw it works, i put cyanogen 11 and redo the partial restore.
My defy was fine, and increased from mb525 to mb526 when i install Cyanogen 11.
I recommand when you have an android phone to root it, put an recorvery, put Nandroid Manager and backup with recorvery regularly, you could restore all your phone if you don't change your rom, or resotre partial data if you change your rom.
Thank you to your site.:laugh::highfive:

[Q] Stuck on encrypted boot

I rooted my i9500.
I flashed CM ROM and encrypted my device.
Later I updated my CM ROM using recovery mode.
When I powered on my device I was asked to enter my encryption password.
After taht I am stuck at the Android logo (decrypting logo).
I tried the following using recovery mode:
- I wiped /data
- I wiped cache
- I wiped Dalvik cache
- I set it to factory settings
All this didn't help.
I found 2 (for me not working) solutions:
mke2fs -t ext4 /dev/block/mmcblk0p12
and
mke2fs -t ext4 /dev/block/mmcblk0p15
No success.
Does anyone have a suggestion?
Thank you in advance!

The logic when booting is that vold tries to mount /data and if that fails, tries to read the master key from the crypto footer, setup decryption and then tries to mount it again.
So, formatting /data should be enough, but I think simply using the 'wipe' options from most recovery will only try (and fail) to delete files on the previously mounted filesystem. I don't know which partition is mounted as /data on your device, but the CM tree for i9500 suggests it's mmcblk0p21, not 12 or 15.