My Atrix 4g has the boot loader unlocked, rooted, is currently running nottachtrix 1.3 with faux 1.3 kernal.
Before flashing nottachtrix I used Clockworkmod Rom Manager to back up the stock rom.
I tried to restore to the stock rom from the app and it failed, the error was "couldn't open directory. no files found" but by this point it had already removed the existing rom. I installed nottachtrix again with out wiping anything and managed to get the phone back working again as before.
I can't restore any of my backups, even new backups made don't work. The error I'm getting is:
"clockworkMod recovery v5.0.2.0
couldn't open directory.
no files found"
The files are still there in the folder /sdcard /clockworkmod/backup the new backups made are also saved to that folder.
From the report.log:
ui_print("ROM Manager Version 5.0.3.1");
ui_print("13 December 2012");
assert(restore_rom("/sdcard/clockworkmod/backup/Stock_backup", "boot", "system", "data", "cache", "sd-ext"));
parse returned 0; 0 errors encountered
about to run program [/sbin/cp] with 4 args
ROM Manager Version 5.0.3.1
13 December 2012
Checking MD5 sums...
boot.img: OK
cache.ext3.tar: OK
data.ext3.tar: OK
recovery.img: OK
system.ext3.tar: OK
.android_secure.vfat.tar: OK
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/Stock_backup/system.ext3.tar
Restoring system...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.6 (30-May-2009)
Setting current mount count to 1
e2fsck 1.41.6 (30-May-2009)
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), 20633/327680 blocks
loads of random code then.
write error: No space left on device
libaudioflinger.solibstlport.solibui.solibbluetooth.solibsensortest.solibz.solibnvomxilclient.solibstagefright.solibpanorama_jni.solibnvmm_video.solibopencore_mp4local.solibmedia_jni.solibhwmediarecorder.solibctest.solibCamera_gingerbread.solibjni_nwp.solibext2_profile.solibrs_jni.solibsurfaceflinger.solibflashplayer.solibysshared.solibstagefright_froyo.solibstagefright_honeycomb.solibaudio.solibjni_latinime.solibphotoflow.solibnvddk_aes_user.solibdlnasysjni.solibSR_AudioIn.solibpppd_plugin.solibgui.solibnvodm_imager.solibwebcore.solibreverbwrapper.solibbundlewrapper.solibvisualizer.solibsrec_jni.solibcrypto.solibnvrm_channel.solibRS.soError while restoring /system!
result was NULL, message is: assert failed: restore_rom("/sdcard/clockworkmod/backup/Stock_backup", "boot", "system", "data", "cache", "sd-ext")
It says "No space left on device" does that mean on the SD Card or the internal storage? There is 1.02 gb available on the internal storage and 3.35 gb on the sdcard how much is required?
Any help would be very much appreciated!
Jonnym
try placing a folder inside your internal storage naming it just like the cwm recovery folder on your sdcard and with the same structure (clockworkmod/backup/ )put your backup inside , and free some space on your internal storage aswell , then try again i remember reading something about different storage settings for different roms
Sent from the gray stuff inside my skull
demonoid phenomenom said:
try placing a folder inside your internal storage naming it just like the cwm recovery folder on your sdcard and with the same structure (clockworkmod/backup/ )put your backup inside , and free some space on your internal storage aswell , then try again i remember reading something about different storage settings for different roms
Sent from the gray stuff inside my skull
Click to expand...
Click to collapse
Thanks for the reply
Last night I uninstalled CWM and reinstalled it then tried it again, it failed when restoring the backup of the stock rom, but it did restore a old back up of nottachtrix.
I updated CWM sometime after backing up the stock rom, I wonder if that's the problem? Or the backup is corrupt, I have a back up of it on the PC so will try using that instead.
What do you think?
Thanks again for the advice.
Jonnym
Jonnym said:
Thanks for the reply
Last night I uninstalled CWM and reinstalled it then tried it again, it failed when restoring the backup of the stock rom, but it did restore a old back up of nottachtrix.
I updated CWM sometime after backing up the stock rom, I wonder if that's the problem? Or the backup is corrupt, I have a back up of it on the PC so will try using that instead.
What do you think?
Thanks again for the advice.
Jonnym
Click to expand...
Click to collapse
agreed, maybe it's an incompatible backup, or also try selective restore option, and restore partition by partition, make sure to do all necessary wipes
Sent from the gray stuff inside my skull
demonoid phenomenom said:
agreed, maybe it's an incompatible backup, or also try selective restore option, and restore partition by partition, make sure to do all necessary wipes
Sent from the gray stuff inside my skull
Click to expand...
Click to collapse
I'm guessing that's all done in Clockworkmod?
Is there any where I can get an older version of Clockworkrom?
thanks for the help
Jonnym
Jonnym said:
I'm guessing that's all done in Clockworkmod?
Is there any where I can get an older version of Clockworkrom?
thanks for the help
Jonnym
Click to expand...
Click to collapse
Thats not a good idea, you risk a hard brick, or need to rsd flash rom again, im not sure about this but there is an adb way to manually flash each partition regardless of restore being corrupt or not but thats too riskiest
Sent from the gray stuff inside my skull
Related
I recently tried a new ROM and made a Rom Manager recovery restore file prior to changing. Things didn't work out as well as I had hoped and when attempting to restore, it fails at the checking MD5 sum process.
Any way to work around this? I really would like to restore to the previous ROM without starting over.
Anybody? I am not quite sure how the restore file can be created on this phone and then not pass verification?
Any ideas or am I stuck starting over?
sandiegopaneraiguy said:
Anybody? I am not quite sure how the restore file can be created on this phone and then not pass verification?
Any ideas or am I stuck starting over?
Click to expand...
Click to collapse
depending on the type of file format used to backup, the restoring could be done manually but a changed md5sum generally means the files are not the same as the original. this could result in corruption and generally it isnt recommended to restore corrupted files as you run the risk of nothing working.
if you're still wanting to proceeding with attempting to restore files which are different than the original and could be corrupted, off the top of my head, you can probably dd the .img files back and untar the .tar files back.
i would suggest starting over and perhaps copying the backup files over to your desktop instead of only leaving on the sdard. this should help ensure at least one of the copies maintains their integrity.
hope that helps!
You can boot into recovery, and run nandroid via adb shell command line, no md5 checksum file needed. Now if the image is bad, you of course get bad results, but if the checksum is just hosed for some reason, it will work fine.
Put the .win files for the partitions you want to restore in /sdacrd
then issue the command "tar xvpf /sdcard/data.win" or "tar xvpf /sdcard/system.win" from the adb shell while in /data or /system respectively. .win files are what TWRP creates for backups.
I had this happen with TWRP 1.01 or 1.02 once on a good backup that passed the checksum tests when I backed it up.
I was testing the reliability of the TWRP package's nandroid and first one failed.
Once I moved to the newer version, I've not had that issue.
I just received my new 32gb SD card, and am wondering how to ensure that my ext3 partition is also copied over, not just the fat32 files. I have found some other threads regarding this process but I still have some unanswered questions.
FYI, I am using MIUI 1.11.4 on a rooted Acer Liquid E (and malez-recovery, which is based on CM).
1. The general consensus seems to be to do a nandroid backup, partition the new card with gparted, and restore that backup (and obviously copy the fat32 files to my computer and then transfer back). I'd just like someone to tell me I'm correct before I try it.
2. On every single one of the threads I found, it always says to do a nandroid backup. Do they really mean a nandroid+ext backup?! Will the basic nandroid backup do the trick (I don't see how)? I'm concerned about this because I always get errors when I attempt a nandroid+ext backup. I plan to run nandroid-mobile.sh -b -e via adb once my file transfer is complete (stupid slow old sd card + computer), but I'm not confident that it'll work. If it doesn't, what options do I have for accessing the ext3 partition? **UPDATE: I ran nandroid-mobile.sh, and it eventually said "--ext2 specified but unable to mount the ext2 partition". I'm still Googling but I haven't figured out a solution yet. Ideas?
3. Every thread recommends using gparted but provides no justification as to why. Since I am using Windows, the whole process seems over-complicated. Can I not just use the "partition sd card" available through recovery? Why is it better to use gparted?
Thanks for any help you can give a semi-n00b!
skittleys said:
1. The general consensus seems to be to do a nandroid backup, partition the new card with gparted, and restore that backup (and obviously copy the fat32 files to my computer and then transfer back). I'd just like someone to tell me I'm correct before I try it.
2. On every single one of the threads I found, it always says to do a nandroid backup. Do they really mean a nandroid+ext backup?! Will the basic nandroid backup do the trick (I don't see how)? I'm concerned about this because I always get errors when I attempt a nandroid+ext backup. I plan to run nandroid-mobile.sh -b -e via adb once my file transfer is complete (stupid slow old sd card + computer), but I'm not confident that it'll work. If it doesn't, what options do I have for accessing the ext3 partition?
3. Every thread recommends using gparted but provides no justification as to why. Since I am using Windows, the whole process seems over-complicated. Can I not just use the "partition sd card" available through recovery? Why is it better to use gparted?
Thanks for any help you can give a semi-n00b!
Click to expand...
Click to collapse
1. Do that (just do it ; in case anything goes wrong, you can restore the nandroid backup and have your device up and running easily). If you don't create one (make sure you do) you will have a hard time getting your device to work again (and depending on your device, it may not be fixable).
2. Just make a nandroid backup. Some roms have it enabled by default (access to the partition). See here: http://forum.cyanogenmod.com/topic/19160-modhow-to-apps2ext-for-cm7-updated-03312011/.
3. Using GParted is the easiest method (which is why it is recommended): http://gparted.sourceforge.net/.
Theonew said:
3. Using GParted is the easiest method (which is why it is recommended): .
Click to expand...
Click to collapse
Easier than 3 multiple-choice questions in a recovery I've already installed???
Theonew said:
2. Just make a nandroid backup. Some roms have it enabled by default (access to the partition). See here:.
Click to expand...
Click to collapse
I doubt that my ROM does an ext backup by default.... I have now run nandroid-mobile.sh and eventually got the following message: "Warning: --ext2 specified but unable to mount the ext2 partition". I'm still Googling but I haven't yet figured out a solution for this. In the meantime, I have copied /sd-ext to my computer, which might end up being a decent workaround...but I'd still love to know what's going on!
**UPDATE: Something I've noticed...:
If I access the phone after a "normal" reboot, /sd-ext definitely exists (I can see it using simply ls, and also mount and df), but no scripts are available in /sbin.
When I go into recovery, /sbin contains all the scripts (so I can now run nandroid), but /sd-ext doesn't appear!
I've a strong suspicion this is why the partition can't be mounted during the nandroid backup.
So how do I fix this?!
skittleys said:
Easier than 3 multiple-choice questions in a recovery I've already installed???
Click to expand...
Click to collapse
According to others, yes .
skittleys said:
**UPDATE: Something I've noticed...:
If I access the phone after a "normal" reboot, /sd-ext definitely exists (I can see it using simply ls, and also mount and df), but no scripts are available in /sbin.
When I go into recovery, /sbin contains all the scripts (so I can now run nandroid), but /sd-ext doesn't appear!
I've a strong suspicion this is why the partition can't be mounted during the nandroid backup.
So how do I fix this?!
Click to expand...
Click to collapse
You cannot "fix" it. That is one reason but it also really depends on your device. For example: http://www.jayceooi.com/2011/01/12/...tition-on-sd-card-with-clockworkmod-recovery/ - This device is able to do it from recovery and it is easier than the GParted method (at least on that device).
Theonew said:
You cannot "fix" it. That is one reason but it also really depends on your device. For example: - This device is able to do it from recovery and it is easier than the GParted method (at least on that device).
Click to expand...
Click to collapse
I think we're mixing up 2 different issues now.
Forget the partitioning method, I'll just use gparted.
But now there's a major issue: I can't make a nandroid+ext backup. I've used adb to copy everything from my current ext partition and can load it onto the new card's partition, but that might not be an effective solution -- will it break all the symlinks? I'm trying to figure out whether symlinks ultimately store a path (therefore links won't break because the directory structure is still the same) or an address (which will break the links if I'm just copying + pasting). I'm finding conflicting answers.
So now I'm asking about what this error means (why won't it mount), whether the behaviour I described in the "update" above is normal (no sbin in normal mode, no sd-ext in recovery), and what alternatives I have! (Oh, and also my symlinks Qs) Plenty of people using the same recovery have created nandroid+ext backups without problems, and all the posts I'm finding about the issue relate to older versions of AmonRa.
skittleys said:
I think we're mixing up 2 different issues now.
Forget the partitioning method, I'll just use gparted.
But now there's a major issue: I can't make a nandroid+ext backup. I've used adb to copy everything from my current ext partition and can load it onto the new card's partition, but that might not be an effective solution -- will it break all the symlinks? I'm trying to figure out whether symlinks ultimately store a path (therefore links won't break because the directory structure is still the same) or an address (which will break the links if I'm just copying + pasting). I'm finding conflicting answers.
Click to expand...
Click to collapse
It's quite likely that it will break the symlinks (just like .android_secure issues). Are you able to make a nandroid-only backup?
skittleys said:
So now I'm asking about what this error means (why won't it mount), whether the behaviour I described in the "update" above is normal (no sbin in normal mode, no sd-ext in recovery), and what alternatives I have! (Oh, and also my symlinks Qs) Plenty of people using the same recovery have created nandroid+ext backups without problems, and all the posts I'm finding about the issue relate to older versions of AmonRa.
Click to expand...
Click to collapse
What recovery are you using (include version)? It is a known problem for some recovery not being able to have access to the SD-ext partition (e.g. ClockworkMod Recovery 3.0.0.5 on some if not all devices). So you should be able to access the SD-ext partition in recovery, and you should be able to access sbin normally.
Theonew said:
It's quite likely that it will break the symlinks (just like .android_secure issues). Are you able to make a nandroid-only backup?
Click to expand...
Click to collapse
Yes, I can do a nandroid backup of the internal partitions. Also not sure what issues you're referring to. I did some research on symlinks and posted on a linux forum and concluded that it shouldn't break....
Theonew said:
What recovery are you using (include version)? It is a known problem for some recovery not being able to have access to the SD-ext partition (e.g. ClockworkMod Recovery 3.0.0.5 on some if not all devices). So you should be able to access the SD-ext partition in recovery, and you should be able to access sbin normally.
Click to expand...
Click to collapse
(I don't have enough posts to insert URLs) I am using Malez recovery 0.6.1 (current is 0.6.2, nothing in the changelog suggests any relevant fixes though). I've searched extensively and it seems that I'm the only malez user having this problem.
Also, I can access sbin, but its only contents are adbd and ueventd. /sd-ext just plain doesn't show up in recovery mode.
Question: who is the owner of your /system, /sd-ext, and /system/sd partitions?
And a possibly unrelated question: what's the point of running a command through busybox (e.g., busybox ls instead of just ls)?
skittleys said:
Yes, I can do a nandroid backup of the internal partitions. Also not sure what issues you're referring to. I did some research on symlinks and posted on a linux forum and concluded that it shouldn't break....
Click to expand...
Click to collapse
It shouldn't break, but on some roms it does.
skittleys said:
Question: who is the owner of your /system, /sd-ext, and /system/sd partitions?
Click to expand...
Click to collapse
What do you mean?
skittleys said:
And a possibly unrelated question: what's the point of running a command through busybox (e.g., busybox ls instead of just ls)?
Click to expand...
Click to collapse
Busybox adds additional commands that the normal android command system does not have/understand on it's own (It gives you additional LINUX/UNIX based commands). See here: http://busybox.net/about.html.
Theonew said:
What do you mean?
Click to expand...
Click to collapse
When you run ls -l the 3rd and 4th columns show the 'owner' and 'group', respectively. It'll say things like root, system, etc., or maybe 0, 1000, 500, etc.
Theonew said:
Busybox adds additional commands that the normal android command system does not have/understand on it's own (It gives you additional LINUX/UNIX based commands). See here: http://busybox.net/about.html.
Click to expand...
Click to collapse
So there's no point in running a command like ls through busybox, right?
New question:
All that /system/sd contains is a 0-byte file called 'placeholder'. I can't find much info about this, but it sounds like this is intentional. But I know that this is where the ext partition is supposed to mount to. Does yours look like this (in either normal mode or recovery)? (edit: in recovery mode, the placeholder is gone, replaced with another 0-byte file called 'empty')
Also, do you think you could paste the output of mount when run in recovery?
BTW, A2SD seems to work perfectly otherwise. The only oddity I've noticed is that when I run a2sd forcecheck near the end it tries to unmount the partiton and can't.
Code:
[ ] Launching Apps2SD Start Program with forcecheck
[ ] Starting Darktremor Apps2SD in forcecheck mode
[ ] Creating Force Check Flag File...
[ ] Unmounting /dev/block/mmcblk0p2...
umount: can't umount /sd-ext: Device or resource busy
[ ] Rebooting phone...
Ironic that I can't mount it in recovery yet I can't unmount it normally!
CWM 5.8.0.9 for Huawei MediaPad
WARNING !!! DON'T FORMAT AND DON'T WIPE PARTITIONS USING THESE CWM !
I don't know how much this CWM version improves over the existing one by segler11.
However these build were more aimed at compiling and testing the new kernel sources.
I have tested compiling with both arm-eabi-4.4.0 and arm-eabi-4.4.3 with success on Ubuntu 10.04.
This is experimental, however with the new kernel sources it will just be a matter of time.
I have compiled the kernel included in this CWM recovery image but I didn't recompile the complete image.
I took as base Pyramid CWM 5.8.0.9 and I replaced the files from those found on a stock C232B005 kernel.
As the default build configuration I have used the /proc/config.gz of a C232B005 running kernel.
I have tested this CWM to be able to backup these partitions (I have not tested "restore" yet, just checked the tar archives):
boot.img - 12.582.912 (match 12Mb)
recovery.img - 16.777.216 (match 16Mb)
data.ext4.tar
cache.ext4.tar
system.ext4.tar
custom.ext4.tar
as you can see my hand tweaks to "recovery" require the name of "cust" partition to be "custom" instead but I believe this is a no issue while you backup and restore with the same CWM. Suggestions welcome.
BUGS:
data & time on archives are wrong
mount USB storage does not work
adb not enabled in recovery mode
Formats and Wipes do not work don't use them
The "busybox hwclock" applet doesn't work to set the hardware clock of our device.
The "adb shell" is not active while in CWM recovery, I don't know why and this was my objective so if you have suggestion please help.
As usual flash both "recovery" and "recovery2" partitions using "fastboot" and one of the attached CWM recovery:
Code:
fastboot flash recovery recovery-5.8.0.9-HWMOD-eabi-4.4.3.img
fastboot flash recovery2 recovery-5.8.0.9-HWMOD-eabi-4.4.3.img
fastboot reboot
WARNING !!! DON'T FORMAT AND DON'T WIPE PARTITIONS USING THESE CWM !
.:HWMOD:.
.
Reserved CWM HWMOD
This version seemed to work better for me.Tnx dude!
john9 said:
This version seemed to work better for me.Tnx dude!
Click to expand...
Click to collapse
Thank you for trying it.
Remember to absolutely avoid formatting or wiping partitions.
If you need to format/wipe do it ONLY after reinstalling the original "recovery.img" in both "recovery" and "recovery2" partitions and then reset the device from:
"Settings -> Backup and reset -> Factory reset"
ATTENTION !!! You can safely do a wipe or factory reset only after reinstalling the original recovery image.
Sorry for insisting but I don't want to create problems on users devices and I know those operations will create problems.
.:HWMOD:.
Just a note: I used your 4.4.3 version to try making a nandroid backup last night. Good news and bad news.
This morning I inspected the result using the app Nandroid Browser.
Good: Your CWM does successfully backup /data/data. The other CWM that had been posted here did not do so properly.
Bad: Your CWM also backs up the entire internal SD storage contents inside the folder /data/share. It is customary *not* to include this in a nandroid backup because a) you don't want to inflate the file size unnecessarily, and b) you don't want to overwrite the internal SD on a restore.
Idea: After you fix it, and until you manage to get ADB over USB working, maybe you could add a menu option to make a separate backup archive of internal SD to external SD. This would allow a route to save the internal storage if the device becomes unbootable and requires a data wipe.
cmstlist said:
Just a note: I used your 4.4.3 version to try making a nandroid backup last night. Good news and bad news.
This morning I inspected the result using the app Nandroid Browser.
Good: Your CWM does successfully backup /data/data. The other CWM that had been posted here did not do so properly.
Bad: Your CWM also backs up the entire internal SD storage contents inside the folder /data/share. It is customary *not* to include this in a nandroid backup because a) you don't want to inflate the file size unnecessarily, and b) you don't want to overwrite the internal SD on a restore.
Idea: After you fix it, and until you manage to get ADB over USB working, maybe you could add a menu option to make a separate backup archive of internal SD to external SD. This would allow a route to save the internal storage if the device becomes unbootable and requires a data wipe.
Click to expand...
Click to collapse
Thank you for trying it. I wanted to compile/test a kernel with new sources in a CWM.
Yes, in our device the internal memory "/mnt/sdcard" is also mapped under "/data/share".
Unfortunately I don't have the skills (yet) to build a complete recovery image from scratch,
so what I did was just compiling the kernel part of the recovery image, using the new sources.
Then I simply hex tweaked the "recovery" executable of a 5.8.0.9 Pyramid CWM (HTC Sensation).
So, in conclusion, I have no control over what is copied during the backup process of those partitions.
Though I could control which partition is processed by removing them from "fstab", but there is no gain into it.
We will have to wait somebody with the specific knowledge, or maybe I will have some time to learn once I return from holidays.
.:HWMOD:.
Today i have builded bootable CWM 5.5.0.4 from sources, so now we can adjust all what we need
after_silence said:
Today i have builded bootable CWM 5.5.0.4 from sources, so now we can adjust all what we need
Click to expand...
Click to collapse
well done
HI, can anyone share buckup from working device created by CWM.?
Thanks to all.
Hi,
Is it possible to flash update zips from this CWM recovery (like Beats Audio which is in flashable zip format)?
I don't want to use it for backup-recovery.
...and how about doing wipe cache and wipe dalvik cache?
.dredd. said:
Hi,
Is it possible to flash update zips from this CWM recovery (like Beats Audio which is in flashable zip format)?
I don't want to use it for backup-recovery.
...and how about doing wipe cache and wipe dalvik cache?
Click to expand...
Click to collapse
Haven't tried installing a ".zip" archive from CWM but it should work.
Avoid "wiping" and/or "formatting" partitions, they will be messed up.
hwmod said:
Haven't tried installing a ".zip" archive from CWM but it should work.
Avoid "wiping" and/or "formatting" partitions, they will be messed up.
Click to expand...
Click to collapse
The main reason for use of CWM would be to have the possibility of flashing update zips from CWM... but I am afraid of messing up my device... to understand: no problem if I have to reflash the rom but I would not want to cause mistake which could be repaired only by service.
fastboot is always available if something goes wrong and if you flash cwm you wont be able to install official roms because cwm will overwrite stock recovery
so i was stupid and wiped data and cache - then remembered that it said not to - how do i fix this paperweight? i tried fastbooting all the usual partitions (system, boot, userdata, cache, etc) but still nothing - i can get to fastboot but i cant flash any dload updates. any suggestions are greatly appreciated.
flash stock recovery (2 files) from zipped rom via fastboot and then you should be able to flash stock rom
flashed three different stock recoveries to recovery and recovery2 - still only get the media pad logo twice (flashed androidani intl rom before bricking) cant boot to recovery - think the partition table is screwed. is there a way to create partitions from fastboot, and if so, still would be nice to know the names of the partitions to flash as referenced in tmo stock thread.
byt3b0mb said:
flashed three different stock recoveries to recovery and recovery2 - still only get the media pad logo twice (flashed androidani intl rom before bricking) cant boot to recovery - think the partition table is screwed. is there a way to create partitions from fastboot, and if so, still would be nice to know the names of the partitions to flash as referenced in tmo stock thread.
Click to expand...
Click to collapse
The time needed to reformat and rewrite all the firmware partitions (the first time) will be between 10-15 minutes.
Be patient and give enough time to the device to execute all the needed processes.
When the device finally boot it need to completely regenerate dalvik-cache (the first time).
So try again as instructed above, rewrite "BOTH" partitions named "recovery" and "recovery2", both using the same "recovery.img" file found in the latest stock Huawei firmware.
Now extract the stock Huawei firmware archive on your PC and copy the "dload" folder on an empty formatted SDCard, then insert the SDCard in the MediaPad reboot it and wait until success or failure message.
If you wiped partitions you will have to wait more time (20-30m). It may be that after waiting a while a message about "Encryption not possible" could appear, just say no to encryption and let it reset the device.
It already happened to some of us so hope you are also able to recover your tablet.
thanks i will give it a shot - while it is rewriting partitions, should it be on the huawei logo? or should i see the android / gears turning?
byt3b0mb said:
thanks i will give it a shot - while it is rewriting partitions, should it be on the huawei logo? or should i see the android / gears turning?
Click to expand...
Click to collapse
First time restoration takes time on both moments during the 1st Huawei log and even during animation.
Trying to recover a partition that was wiped takes much longer for the OS to show the error.
When I tried wiping "data" and rebooted the device I recall I went for a long walk and when I returned the device was showing the "Encryption failure / Reset" message (about half an hour later).
So I can only suggest that when you retry you wait at least that amount of time (30 min.) with charger connected, whatever happens leave it alone until it display or ask you do something. Let me know if it works when you have tried.
Download links do not work for me. Can you upload in mediafire please?
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?
Can I restore data that I have backed up in CWM form my device to another?
As long as the model is same, yes. What device exactly?
I don't think so, even if they're the same. i've done it once and the cwm log says 'md5sum mismatch!'
azzazelium said:
I don't think so, even if they're the same. i've done it once and the cwm log says 'md5sum mismatch!'
Click to expand...
Click to collapse
If you insist on restoring the backup file do this simple trick on md5 mismatch: open the md5 file in your CWM backup folder, erase its contents. Leave the file empty (0 byte) then restore in peace
Keep in mind md5 mismatch means something changed in the backup file, doesn't matter which device it previously on. Do this on your own risk.
Note: CWM will skip verifying the backup if md5 file is empty.