CWM not backing up - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

im using clockwork recovery and im tryung to backup nandroid and its saying
error while backing up boot image
then says error while making a backup image of /data
already deleted the previous nandroid backups and freed unused backup data

lilmikey201 said:
im using clockwork recovery and im tryung to backup nandroid and its saying
error while backing up boot image
then says error while making a backup image of /data
already deleted the previous nandroid backups and freed unused backup data
Click to expand...
Click to collapse
Are you backing up to your external card, and the card cannot be read in Android?

LostInMyHead said:
Are you backing up to your external card, and the card cannot be read in Android?
Click to expand...
Click to collapse
idk. w.e nandroid backs up?

lilmikey201 said:
im using clockwork recovery and im tryung to backup nandroid and its saying
error while backing up boot image
then says error while making a backup image of /data
already deleted the previous nandroid backups and freed unused backup data
Click to expand...
Click to collapse
Sounds to me you got the wrong version of CWM, is it the loki version?

Make sure you have the correct CWM (as mentioned).
Make sure you have enough space wherever you are doing the backup (internal or external). If you have the 16 GB S4 and you already have a lot of stuff on the internal, it might become a problem.
If backing up to external, make sure your card is OK (also as mentioned).
Use GooManager to flash TWRP to your phone, once it is verified working, flash the flashable CWM (fro the DEV section) onto your phone using TWRP. Make sure you read the threads involved with all of this before you do so. Questions you have about it should already be answered there.
Good luck.

He won't be able to install the incorrect version of CWM. It won't install if it is not loki patched.

dxwilliams40 said:
He won't be able to install the incorrect version of CWM. It won't install if it is not loki patched.
Click to expand...
Click to collapse
That's a good point, however, the OP didn't mention if he has the AT&T S4 or another version. If he is using a loki version of recovery on a non AT&T S4 (if that is possible) he might get errors. It might be worth a mention anyway.

scott14719 said:
That's a good point, however, the OP didn't mention if he has the AT&T S4 or another version. If he is using a loki version of recovery on a non AT&T S4 (if that is possible) he might get errors. It might be worth a mention anyway.
Click to expand...
Click to collapse
i have the ATT version

TheAxman said:
Sounds to me you got the wrong version of CWM, is it the loki version?
Click to expand...
Click to collapse
yea i have the loki version
i downloaded the loki_flash and recovery.lok used file explorer and terminal emulator to install it
i backed up throught sd card but wouldnt work from phone memory

lilmikey201 said:
yea i have the loki version
i downloaded the loki_flash and recovery.lok used file explorer and terminal emulator to install it
i backed up throught sd card but wouldnt work from phone memory
Click to expand...
Click to collapse
I suggest you just use TWRP, No issues at all and fyi the Stock image is 5gbs so you need enough memory for that..

Download the auto loki version and flash over your current one then try again.
Sent from my SAMSUNG-SGH-I337 using xda premium

Tuen it has to be the memory. Damn 9 gigs go quick-_- how can we free up space to get the full 16 gb
Sent from my SGH-M919 using xda premium

Related

Clockworkmod not backing up whole rom

Hi,
I am trying to backup my whole rom with the clockworkmod 6.0.1.0 however the folder size of the backup is only around 30MB. Does this only backup recovery, system and boot.
If there a away I can backup my whole rom
mulkman said:
Hi,
I am trying to backup my whole rom with the clockworkmod 6.0.1.0 however the folder size of the backup is only around 30MB. Does this only backup recovery, system and boot.
If there a away I can backup my whole rom
Click to expand...
Click to collapse
This is because as of cwm 6, it saves backups as blobs. When you backup, it will only backup what is different from other backups, and keep the rest as a general backup in a blob.
This is done to save space and reduce the time it takes to backup
So I wouldn't worry, it will restore fine providing you don't delete the blobs it needs
That's my understanding of it anyway
Sent from my Nexus 7
mulkman said:
Hi,
I am trying to backup my whole rom with the clockworkmod 6.0.1.0 however the folder size of the backup is only around 30MB. Does this only backup recovery, system and boot.
If there a away I can backup my whole rom
Click to expand...
Click to collapse
You can change your backup format to tar and then backup. It'll skip creating blobs and backup in tar files.
UPDATE: Sorry, this isn't working for Nexus 7
Sent from my GT-I9103 using xda app-developers app
The problem I have with the blob method is that CWM was using 2 GB of storage for just two backups. So I switched to TWRP but now that I know about the tar option in CWM, I'm switching back.
Edit:
emanoj.i9103 said:
You can change your backup format to tar and then backup. It'll skip creating blobs and backup in tar files.
Click to expand...
Click to collapse
I reinstalled CWM (Pro) but I just cannot find anywhere to change the backup setting to tar. I looked in the app, app settings, and recovery.
Can you please provide details on how to set the backup mode to tar ?
Sent from my Nexus 7
BillGoss said:
The problem I have with the blob method is that CWM was using 2 GB of storage for just two backups. So I switched to TWRP but now that I know about the tar option in CWM, I'm switching back.
Edit:
I reinstalled CWM (Pro) but I just cannot find anywhere to change the backup setting to tar. I looked in the app, app settings, and recovery.
Can you please provide details on how to set the backup mode to tar ?
Sent from my Nexus 7
Click to expand...
Click to collapse
Same here Ive checked all the menus cannot find a option to select tar as backup
BillGoss said:
The problem I have with the blob method is that CWM was using 2 GB of storage for just two backups. So I switched to TWRP but now that I know about the tar option in CWM, I'm switching back.
Edit:
I reinstalled CWM (Pro) but I just cannot find anywhere to change the backup setting to tar. I looked in the app, app settings, and recovery.
Can you please provide details on how to set the backup mode to tar ?
Sent from my Nexus 7
Click to expand...
Click to collapse
mulkman said:
Same here Ive checked all the menus cannot find a option to select tar as backup
Click to expand...
Click to collapse
Sorry People, I just got my Nexus 7 in hands recently. My early phone is a Galaxy R which has this option of choosing backup format as tar in CWM 6. Thought it might well be the same for Nexus 7. Sorry again for posting misleading information. Hope not to repeat again.

[Q] Error OUDhs CWM Touch Recovery Backup

While trying to backup my phone using OUDhs CWM Touch Reqovery 1.0.3.4 to back up my data I get an
Error while making a backup image of /data !
Anyone know what could cause this
Here's what was printed to screen.
SD Card space free: 2652MB
Backing up boot image
Backup of boot image completed
Backing up recovery image
Backup of recovery image completed
backing up system
bacup of system completed
backing up data ..
Error while making a backup image of /data!
My backups are all over 3 gigs doesnt look like you have enough memory
bhp090808 said:
My backups are all over 3 gigs doesnt look like you have enough memory
Click to expand...
Click to collapse
Ugh I feel such a noob. I forgot the newer CWM you must specifically choose to backup to external SD. Thanks bhp090808
desilva79 said:
Ugh I feel such a noob. I forgot the newer CWM you must specifically choose to backup to external SD. Thanks bhp090808
Click to expand...
Click to collapse
No problem I have noob moments every day lol

[Q] Backups not restoring...

Hi, Been doing nandroid backups religiously of my Stock S4 i9505 - MK8 using both ClockworkMod Recovery and also Online Nandroid Backup Pro as well over last few days...
Anyway, I decided to restore my last backup and that's when the problems started... The restore 'seems' to complete correctly and the phone boots up but immediately but there are lots of pop-up's:
Unfortunately, Google Play service has stopped.
Unfortunately, Google Play Store has stopped.
Unfortunately, process com.google.process.gapps has stopped.
Unfortunately, Picasa Uploader has stopped.
Unfortunately, Gmail has stopped. etc,etc
So, I tried some of the other nandroid backups in case that one was corrupt but got the same problem, tried clearing dalvik cache, same result...
Basically for some very strange reason none of the backups result in a stable system..? Any ideas how I get out of this one..?
Appreciated.
Are you trying to restore an online backup with cwm? That's probably the problem
jd1639 said:
Are you trying to restore an online backup with cwm? That's probably the problem
Click to expand...
Click to collapse
I did try that but also restored the backup done in recovery by CWM as well, same result...
topcat888 said:
I did try that but also restored the backup done in recovery by CWM as well, same result...
Click to expand...
Click to collapse
Try wiping data, and the caches and then restore the nandroid
jd1639 said:
Try wiping data, and the caches and then restore the nandroid
Click to expand...
Click to collapse
ok, wiped all caches plus data/reset and then restored a backup done by CWM I think (unfortunately both types of backups are named using the same naming format, look the same and are in the same folder, yes a mistake)... Anyway re-booted, exactly the same problem.
One thing I did notice this time was that the restores don't complete properly and 'finish early' i.e the screen goes black before it's finished and the phone immediately reboots..?
ITry to make sure you use a nandroid created in cwm. Cwm creates an md5 and checks it so if you use a nandroid not createdby it it'll fail.
jd1639 said:
ITry to make sure you use a nandroid created in cwm. Cwm creates an md5 and checks it so if you use a nandroid not createdby it it'll fail.
Click to expand...
Click to collapse
Nope mate tried them all now, all the backups have their respective MD5... Also CWM checks the MD5's of each backup before starting the restore anyway...
I guess I'm a bit stuck on the nandroid restore front and all that's left is to flash a clean stock..? or any other ideas..?
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Ok, an update - Somehow I managed to restore one of the backups but straight away, whilst still in recovery, cleaned and reset it before starting it up and that worked, it got me back to clean working stock, amazingly.!
So that means I can now start again fresh, this time making sure the backups are not corrupt & work, before I need them..!
Cheers
Hi again,
The problem goes on and I don't understand... After restoring the backup and cleaning cache/data reset all was ok in that it loaded no problems... However I keep getting a notification that Storage Space Running Out (Some system functions may not work)...
If you then go into Storage Settings, it reports Total Space as 9.25GB but available space as 355MB... But there are no files stored there, nothing... I used File Manger as well to try to find the files that are taking up all the space but it too reports that there is nothing there taking up the space...? I'm confused..? and worried that if the 345MB gets used by the system, it will then stop working..??
I have installed Root Explorer and list /sdcard it states that 8.91GB used, 329MB free. I think it is old CWM backups that are stored in the int/sd but are hidden that are causing the problem..? CWM can't see them though... I can't find the files that are taking up the space on the int/SD..??
I have also viewed the int/sd files listed when it is connected to pc in MTP mode and again there are no backup files to delete, nothing...yet it reports 329MB free of 9.22 GB...?
Plus I have noticed some of the files/folders have the '01 Jan 1970' date that CWM put on the backup.. MESS..!
I don't get it, where ever I look (using Root Explorer) there are no large files, where are they hidden..??
Basically I just want to completely clear the phone storage of any user data including CWM data (I'll use the ext sd from now on)... Trouble is I'm not sure what I can and can't delete safely..??
Help as always appreciated...
Hi,
quick question is your KNOX showing 0x0 or 0x1
Mizpah said:
Hi,
quick question is your KNOX showing 0x0 or 0x1
Click to expand...
Click to collapse
Hi, It's 0x1
topcat888 said:
Hi, I assume it's Knox 0x1 as I have rooted and custom recovery'ed it, how do you tell..??
Click to expand...
Click to collapse
Ok, after going through every single folder, I have now found a folder under Data/Media/clockworkmod/ which contains amongst other things another folder called backup, that had 3 backups in it, amounting to 8.27GB data..!
Now I have deleted those (as I have other CWM backups on the ext/sd) and I have some room to move again but my question is now, can I somehow reset the phone (not ext/sd) and all of it's contents completely back to stock, CWM has messed things up a bit with 1970 folder/file dates all over the place..??
topcat888 said:
Ok, after going through every single folder, I have now found a folder under Data/Media/clockworkmod/ which contains amongst other things another folder called backup, that had 3 backups in it, amounting to 8.27GB data..!
Now I have deleted those (as I have other CWM backups on the ext/sd) and I have some room to move again but my question is now, can I somehow reset the phone (not ext/sd) and all of it's contents completely back to stock, CWM has messed things up a bit with 1970 folder/file dates all over the place..??
Click to expand...
Click to collapse
That's the main reason I don't like cwm, too many blob folders to make manually cleaning then up easy.
I don't know the i9505 that well but if there is an odin flashable tar file of your current firmware I'd flash that. Then do a factory reset in the stock recovery. That will return your device to like new. You will lose all your apps and data so backup anything you want to keep before you do this
jd1639 said:
That's the main reason I don't like cwm, too many blob folders to make manually cleaning then up easy.
I don't know the i9505 that well but if there is an odin flashable tar file of your current firmware I'd flash that. Then do a factory reset in the stock recovery. That will return your device to like new. You will lose all your apps and data so backup anything you want to keep before you do this
Click to expand...
Click to collapse
yes, that's exactly what I was thinking I might have to do... Any ideas/directions as to where the 'odin flashable file of XXUEMK8' would be, I've looked in the i9505 forum but can't find it..?
topcat888 said:
yes, that's exactly what I was thinking I might have to do... Any ideas/directions as to where the 'odin flashable file of XXUEMK8' would be, I've looked in the i9505 forum but can't find it..?
Click to expand...
Click to collapse
Check on sammobile.com. you'll have to register but it's free. You'll down load a zip file. Use 7-zip to extract the .tar.md5 file from it. Use that in Odin
jd1639 said:
Check on sammobile.com. you'll have to register but it's free. You'll down load a zip file. Use 7-zip to extract the .tar.md5 file from it. Use that in Odin
Click to expand...
Click to collapse
Thanks, I searched for i9505 but there is a firmware for every country except the UK or MK8 listed ..?
topcat888 said:
Thanks, I searched for i9505 but there is a firmware for every country except the UK or MK8 listed ..?
Click to expand...
Click to collapse
Looks like there is an mk8 for UK btu. Not sure what carrier you're on
You have to enable selinux enforcing to make nandroid backups. Philz recovery can do that.
Enviado desde mi GT-I9505
jd1639 said:
Looks like there is an mk8 for UK btu. Not sure what carrier you're on
Click to expand...
Click to collapse
Oh, I couldn't see it..? The phone is unbranded but I use O2...
Conito11 said:
You have to enable selinux enforcing to make nandroid backups. Philz recovery can do that.
Enviado desde mi GT-I9505
Click to expand...
Click to collapse
Where can I read more about that..?
Don't know. .. Flash Philz recovery and enable that setting, then make nandroid.
Enviado desde mi GT-I9505

TWRP Backups keep failing

Hello,
I just S-Off using sunshine and flashed TWRP recovery. I am still running stock rom and everytime I try and backup through TWRP the backup fails on system image. Does anyone know why that would be happening. I don't want to do any new rom installs without a solid backup. Thanks
Adabow12 said:
Hello,
I just S-Off using sunshine and flashed TWRP recovery. I am still running stock rom and everytime I try and backup through TWRP the backup fails on system image. Does anyone know why that would be happening. I don't want to do any new rom installs without a solid backup. Thanks
Click to expand...
Click to collapse
If you're trying to backup to sdCard instead of Internal it will continue to malfunction.
Til something changes, you can backup to Internal and set it to compress the backup so you don't run out of room.
If backing it up doesn't work, you can always use an RUU. As long as you can get into the bootloader, an RUU will fix any problem by flashing the official firmware.
Verizon RUU: http://forum.xda-developers.com/verizon-htc-10/how-to/verizon-official-ruu-1-19-605-9-t3377586
michaelbsheldon said:
If you're trying to backup to sdCard instead of Internal it will continue to malfunction.
Til something changes, you can backup to Internal and set it to compress the backup so you don't run out of room.
Click to expand...
Click to collapse
I am having the same issue trying to backup to my Ext. SD. Could I backup to my internal SD and then manually move the backup file onto the ext SD?
veyec said:
I am having the same issue trying to backup to my Ext. SD. Could I backup to my internal SD and then manually move the backup file onto the ext SD?
Click to expand...
Click to collapse
Haven't tried that, but it would probably work. Thing is, TWRP won't see it on the SDCard, so it would have to go back into Internal if you needed to restore it.

can't extract apps from nandroid made otg with twrp

My phone was stuck in a bootloop where it could only get to recovery. Using the recovery I created a nandroid backup to the a USB stick using an OTG cable. I flashed the stock firmware and got things setup but I can't restore individuals apps from the nandroid. I copied the nandroid from the usb to sd card but it still doesn't work. I tried restoring apps using Nandroid Manager but when the app is launched it gives the error "app has stopped, close app". For some reasons sms succesfully restored but no user apps. I tried restoring with AppExtractor but it gives the error "unable to generate apk listing"
I also have titanium backup pro but couldn't get it to find the location of the nandroid to try extracting with it.
Any ideas? I really just want my messages back from Whatsapp.
My phone had stock Nougat with busybox installed and elementalx kernel. It should be the same environment now as when the backups were made.
@twoplustwo can you tell us why your phone went into bootloop ? If you know then you can restore /data from TWRP and revert the cause of bootloop..
Also can you confirm it's in capital letters as you have mentioned in small letters in another thread that twrp/backups rename them to TWRP/BACKUPS or move them to internal storage.. (in stock ROM if i am not wrong, TWRP folder is not accessible, so try to install custom ROM for temporary purpose, then move backup to internal and then try with titanium backup..)
____Mdd said:
@twoplustwo can you tell us why your phone went into bootloop ? If you know then you can restore /data from TWRP and revert the cause of bootloop..
Also can you confirm it's in capital letters as you have mentioned in small letters in another thread that twrp/backups rename them to TWRP/BACKUPS or move them to internal storage.. (in stock ROM if i am not wrong, TWRP folder is not accessible, so try to install custom ROM for temporary purpose, then move backup to internal and then try with titanium backup..)
Click to expand...
Click to collapse
yes it was in capital letters
the problem in the first place that sent the phone into a bootloop was I installed the OTA security update. I'm running stock rom but I guess because it was rooted and had busybox, that made it incompatible with the update?
twoplustwo said:
yes it was in capital letters
the problem in the first place that sent the phone into a bootloop was I installed the OTA security update. I'm running stock rom but I guess because it was rooted and had busybox, that made it incompatible with the update?
Click to expand...
Click to collapse
If you have TWRP and take update, it don't cause bootloop, but it cause your device to boot into recovery when you turn on your device.. can you confirm if it was bootloop or problem of booting to TWRP ?
I am unable to copy the nandroid to internal storage. I tried using usb to computer and it just does nothing. I tried root explorer and it says 'copy failed' and file manager says 'cannot load'. This only happens with the TWRP folder inside the internal memory specifically.
____Mdd said:
@twoplustwo can you tell us why your phone went into bootloop ? If you know then you can restore /data from TWRP and revert the cause of bootloop..
Also can you confirm it's in capital letters as you have mentioned in small letters in another thread that twrp/backups rename them to TWRP/BACKUPS or move them to internal storage.. (in stock ROM if i am not wrong, TWRP folder is not accessible, so try to install custom ROM for temporary purpose, then move backup to internal and then try with titanium backup..)
Click to expand...
Click to collapse
____Mdd said:
If you have TWRP and take update, it don't cause bootloop, but it cause your device to boot into recovery when you turn on your device.. can you confirm if it was bootloop or problem of booting to TWRP ?
Click to expand...
Click to collapse
I can confirm it was only booting TWRP. So even when I tried to boot to system it just booted to TWRP again.
twoplustwo said:
I can confirm it was only booting TWRP. So even when I tried to boot to system it just booted to TWRP again.
Click to expand...
Click to collapse
You don't need to worry,
Do you have any important data for any app currently ?
Take backup of new important data with titanium.. (and then again take backup from TWRP, for safety )
And then simply restore /data from TWRP backup, it will give you older data back without any bootloop but you will loose new data/messages that you got after flashing/ on current running ROM..
____Mdd said:
You don't need to worry,
Do you have any important data for any app currently ?
Take backup of new important data with titanium.. (and then again take backup from TWRP, for safety )
And then simply restore /data from TWRP backup, it will give you older data back without any bootloop but you will loose new data/messages that you got after flashing/ on current running ROM..
Click to expand...
Click to collapse
Thank you sir! To confirm, when backing up to USB stick with OTG, does the format of the USB matter? Is fat32 safe?
twoplustwo said:
Thank you sir! To confirm, when backing up to USB stick with OTG, does the format of the USB matter? Is fat32 safe?
Click to expand...
Click to collapse
Not familiar with different formats, it should work.. bu t
You can backup to internal storage too, since you don't have to flash fastboot ROM again..
____Mdd said:
Not familiar with different formats, it should work.. bu t
You can backup to internal storage too, since you don't have to flash fastboot ROM again..
Click to expand...
Click to collapse
Just want to confirm everything is working perfect now. Thank you again!

Categories

Resources