Related
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.
When I enter into CMW recovery, and click restore, it only shows the backups i have created in recovery mode, well before flashing a new rom I made a backup with Online Nandroid, but I can't seem to restore it because it doesn't show up in the restore recovery screen. Also, I can't seem to find the path for the restore files from the recovery backups.
Brendan12695 said:
When I enter into CMW recovery, and click restore, it only shows the backups i have created in recovery mode, well before flashing a new rom I made a backup with Online Nandroid, but I can't seem to restore it because it doesn't show up in the restore recovery screen. Also, I can't seem to find the path for the restore files from the recovery backups.
Click to expand...
Click to collapse
Not familiar online nandroids at all, but I'm guessing it stores it somewhere other than /data/media/clockworkmod. You'll have to move the nandroid to the default CWM folder most likely.
CMNein said:
Not familiar online nandroids at all, but I'm guessing it stores it somewhere other than /data/media/clockworkmod. You'll have to move the nandroid to the default CWM folder most likely.
Click to expand...
Click to collapse
Sadly that did not work, it backups with .tar files that CMW isn't capable of reading.. So, I have to use a previous restore.
Brendan12695 said:
Sadly that did not work, it backups with .tar files that CMW isn't capable of reading.. So, I have to use a previous restore.
Click to expand...
Click to collapse
Bummer. As a last resort you don't happen to have CWM set to back up as "dup" under backup type do you?
CMNein said:
Bummer. As a last resort you don't happen to have CWM set to back up as "dup" under backup type do you?
Click to expand...
Click to collapse
Nope, I did check to make sure and it was set to default.
Can you post the log file at /data/local/tmp/onandroid.log
delete. posted in wrong thread.
Hi,
This is the latest soak test backup of Android 5.1 Lollipop. verison 222.21.15.
Download:
https://goo.gl/GGx27V
Download latest TWRP for ghost (Moto X)
https://dl.twrp.me/ghost/twrp-2.8.6.0-ghost.img.html
how to restore,
- copy backup folder to your twrp backup folder
- restore backup (system & boot) via twrp
- wipe data, cache & dalvik cache
- reboot
this is a backup file of system and boot partition. can only be restored with TWRP Recovery. it will not touch your modem, bootloader or any other partition of your phone. backup your current system before resotre this twrp backup. if you have any question, just ask here in thread, xda community will response you..
Click to expand...
Click to collapse
backup made for protect you mess your bootloader or modem with installing brazil firmware to your phone.
testet on xt1052 should work with most moto x variants.
Need more help ? look at this thread.
http://forum.xda-developers.com/moto-x/general/how-to-install-5-1-lollipop-moto-x-t3089594
reserved
Is the last update?
I was waiting for this! Thank you very much, @proxuser!
Restored on my xt1053 over the top of the previous build and kept my data intact. Thanks
Did this fix the speakerphone bug?
Stock recovery
Original recovery from 222.12.15 included? I've updated to 222.12.15 from 222.12.7, but the recovery didn't changed, again :/
scht said:
Original recovery from 222.12.15 included? I've updated to 222.12.15 from 222.12.7, but the recovery didn't changed, again :/
Click to expand...
Click to collapse
It's a TWRP backup so no, it isn't included.
How do I root after restoring the backup? I didn't get the option to install SuperSU after the restore.
Nope
athulele said:
Did this fix the speakerphone bug?
Click to expand...
Click to collapse
I installed and the speakerphone bug is still present. Tried clearing app data for Phone and Dialler apps to no avail.
Side note:
Tried restoring from stock firmware in TWRP. Did not work twice. Got stuck on the Moto Blue Water logo. Third time, it worked inexplicably!
Any infos on what is changed?
Improval of battery life would be most interesting to me.
ron_gangte said:
How do I root after restoring the backup? I didn't get the option to install SuperSU after the restore.
Click to expand...
Click to collapse
There is already a su file in the backup but that didn't work for me too. You have to delete the su file at /system/xbin/ manually via twrp file manager. If you reboot twrp will ask you to root again.
Kiristiba said:
There is already a su file in the backup but that didn't work for me too. You have to delete the su file at /system/xbin/ manually via twrp file manager. If you reboot twrp will ask you to root again.
Click to expand...
Click to collapse
Can't find that folder in twrp
Hi, I rebooted my device and it is not switching on any more. Gets stuck at the Blue Water Moto logo. Waited for more than 10 minutes. Tried restore followed by wipe for cache and data again. But still stuck on blue logo. Any help?
johnrangoo said:
Can't find that folder in twrp
Click to expand...
Click to collapse
Did you mount the system partition?
Kiristiba said:
There is already a su file in the backup but that didn't work for me too. You have to delete the su file at /system/xbin/ manually via twrp file manager. If you reboot twrp will ask you to root again.
Click to expand...
Click to collapse
Thanks!
I found an alternate solution. I flashed the SuperSU zip, and it rooted the phone with no hassle. [emoji2]
I tried to restore it on my xt1052, it keeps saying that No partitions selected for restore. What should I do?
In your TWRP backup directory, there should be a folder with the date (2015-05-12--16-05-56_LPA23.12-15), make sure the image files are in this directory.
When I extracted the rar, it was 2015-05-12--16-05-56_LPA23.12-15\2015-05-12--16-05-56_LPA23.12-15\<image files>
it should be 2015-05-12--16-05-56_LPA23.12-15\<image files>
Can I install this from 4.4.4?
Test it. The proximity sensor also not work for active display.
So I back to 4.4.4 again.
I lost my phone's IMEI trying to do a backup of it, and also lost my baseband. Backups of IMEI didn't work, and also the backup of the rom made with Nandroid backup.
I wanted to copy the folder EFS, cauase someone recommended to backup the IMEI this way. I did it by ES File Explorer, but when copying the folder EFS, appeared an error message like this: "Failed to copy NVRAM" or something like that.
I do not know if it happened in this process or if the EFS folder had already corrupted with other IMEI backups made with various applications (backups that did not serve me at all). Considering that my IMEI continued null / null when I tried to restore them with a lot of applications (Partitions Backup & Restore, Samsung Tools etc)
Maybe it's important to say that before attempting to restore the IMEI by several backups I had done before tried to install other modems to see if the network appears again. But did not.
Finally, I reinstalled the rom stock by Odin and nothing resolved. I continue with the IMEI issue null/null and unknown baseband.
My last attempt was to restore the backup I made the rom the first day I picked up the phone.
The backup I made with Online Nandroid Backup application. Be safe with this backup because on any topic roms here from XDA, the developers says "Do a nandroid backup first." And that's what I did.
In momement when I did the backup with this application, my recovery installed was Philz Recovery (which is based on CWM), it may be important to say that.
But anyway, the backup is saved on my PC, and I had not needed to use it, and thought it would work when I needed it, but it did'nt work.
Once installed the rom again by Odin, did root, and installed the same Philz Recovery (to have less doubt that the backup can be restored without problems with Nandroid Manager), but it didn't work.
I created a folder called "backup" in the clockworkmod folder "and put my backup there (one who has the time and date of creation in the name).
And when I tried to restore the backup by Nandroid Manager application, the only thing that happens is the phone to reboot, without even access at first the recovery. So the backup can't be restored again.
Then I converted the file to ".zip" and I went to recovery and tried to install it, also failed. It appeared some problem related to the "MD5".
So I installed CWM Recovery (not Philz) and tried to restore the backup with Nandroid Manager, did not work, the phone again, just restarted. So I tried to install the backup as a ".zip" from CWM Recovery, and again, there was a new message regarding the "MD5".
So I installed TWRM Recovery, and tried to restore the backup by Nandroid Manager (but the application said the backup was originated by CWM and it could not be restored by another recovery) then I tried installing the ".zip" file by TWRM recovery, and gave some kind of failure, can not remember exactly what, but I think also related to "MD5".
So I tried to fix the problem related to MD5, I saw some threads on XDA saying how to do ... basically tried two methods.
The first attempt was to delete the file "Nandroid.MD5" by Root Explorer and create a new file with the same name and with the same extension.
So I tried again to restore the backup by Nandroid Manager (with Philz Recovery and CWM Recovery), but also failed. Also failed to install a ".zip" file driectly by the recovery with the new file "nandroid.MD5" created. This file ".zip" with MD5 file "probably fixed" I tried to install with the 3 recoveries already mentioned. Did not work. It continued an error related to "MD5".
The second attempt was to try to correct the "MD5" file with the Terminal Emulator, by this commands:
su
# Mount -o remount rw / sdcard
#cd /sdcard/clockworkmod/backup/2012-04-17.10.09.36
#rm nandroid.md5
# md5sum * img> nandroid.md5
Again, I tried to restore the file by Nandroid Manager (with philz Recovery and CWM Recovery) ... And also tried to restore the file ".zip" by both recoveries,includint TWRP Recovery. Nothing worked.
In the backup name has no spaces. And the files inside it are:
boot.img
cache.ext4.tar
data.ext4.tar
efs.ext4.tar
modem.img
recovery.img
recovery.log
system.ext4.tar
I have a backup intact without modification for future experiments.
I do not know what else to do, I just want to restore the backup to see if the network went back, with my IMEI and my baseband losted.
-
I tried to do the right things and looks like it was worse than if I had done nothing.
For example, trying to save the EFS folder by ES Explorer, apparently that destroyed this folder.
But before It had already made a backup of the rom, but I can not restore it.
It would was better If I did nothing to try to forearm... Cause for now I do not know what to do whit these problems...
My last step will be to gather cash to buy a box to put my IMEI back to the phone... = (
Sorry for my Inglês... Translated by Google Translator.
My phone is SM-N9005.
LeandritoG said:
I lost my phone's IMEI trying to do a backup of it, and also lost my baseband. Backups of IMEI didn't work, and also the backup of the rom made with Nandroid backup.
I wanted to copy the folder EFS, cauase someone recommended to backup the IMEI this way. I did it by ES File Explorer, but when copying the folder EFS, appeared an error message like this: "Failed to copy NVRAM" or something like that.
I do not know if it happened in this process or if the EFS folder had already corrupted with other IMEI backups made with various applications (backups that did not serve me at all). Considering that my IMEI continued null / null when I tried to restore them with a lot of applications (Partitions Backup & Restore, Samsung Tools etc)
Maybe it's important to say that before attempting to restore the IMEI by several backups I had done before tried to install other modems to see if the network appears again. But did not.
Finally, I reinstalled the rom stock by Odin and nothing resolved. I continue with the IMEI issue null/null and unknown baseband.
My last attempt was to restore the backup I made the rom the first day I picked up the phone.
The backup I made with Online Nandroid Backup application. Be safe with this backup because on any topic roms here from XDA, the developers says "Do a nandroid backup first." And that's what I did.
In momement when I did the backup with this application, my recovery installed was Philz Recovery (which is based on CWM), it may be important to say that.
But anyway, the backup is saved on my PC, and I had not needed to use it, and thought it would work when I needed it, but it did'nt work.
Once installed the rom again by Odin, did root, and installed the same Philz Recovery (to have less doubt that the backup can be restored without problems with Nandroid Manager), but it didn't work.
I created a folder called "backup" in the clockworkmod folder "and put my backup there (one who has the time and date of creation in the name).
And when I tried to restore the backup by Nandroid Manager application, the only thing that happens is the phone to reboot, without even access at first the recovery. So the backup can't be restored again.
Then I converted the file to ".zip" and I went to recovery and tried to install it, also failed. It appeared some problem related to the "MD5".
So I installed CWM Recovery (not Philz) and tried to restore the backup with Nandroid Manager, did not work, the phone again, just restarted. So I tried to install the backup as a ".zip" from CWM Recovery, and again, there was a new message regarding the "MD5".
So I installed TWRM Recovery, and tried to restore the backup by Nandroid Manager (but the application said the backup was originated by CWM and it could not be restored by another recovery) then I tried installing the ".zip" file by TWRM recovery, and gave some kind of failure, can not remember exactly what, but I think also related to "MD5".
So I tried to fix the problem related to MD5, I saw some threads on XDA saying how to do ... basically tried two methods.
The first attempt was to delete the file "Nandroid.MD5" by Root Explorer and create a new file with the same name and with the same extension.
So I tried again to restore the backup by Nandroid Manager (with Philz Recovery and CWM Recovery), but also failed. Also failed to install a ".zip" file driectly by the recovery with the new file "nandroid.MD5" created. This file ".zip" with MD5 file "probably fixed" I tried to install with the 3 recoveries already mentioned. Did not work. It continued an error related to "MD5".
The second attempt was to try to correct the "MD5" file with the Terminal Emulator, by this commands:
su
# Mount -o remount rw / sdcard
#cd /sdcard/clockworkmod/backup/2012-04-17.10.09.36
#rm nandroid.md5
# md5sum * img> nandroid.md5
Again, I tried to restore the file by Nandroid Manager (with philz Recovery and CWM Recovery) ... And also tried to restore the file ".zip" by both recoveries,includint TWRP Recovery. Nothing worked.
In the backup name has no spaces. And the files inside it are:
boot.img
cache.ext4.tar
data.ext4.tar
efs.ext4.tar
modem.img
recovery.img
recovery.log
system.ext4.tar
I have a backup intact without modification for future experiments.
I do not know what else to do, I just want to restore the backup to see if the network went back, with my IMEI and my baseband losted.
-
I tried to do the right things and looks like it was worse than if I had done nothing.
For example, trying to save the EFS folder by ES Explorer, apparently that destroyed this folder.
But before It had already made a backup of the rom, but I can not restore it.
It would was better If I did nothing to try to forearm... Cause for now I do not know what to do whit these problems...
My last step will be to gather cash to buy a box to put my IMEI back to the phone... = (
Sorry for my Inglês... Translated by Google Translator.
My phone is SM-N9005.
Click to expand...
Click to collapse
try this
plumzup67 said:
try this
Click to expand...
Click to collapse
This is for what?
LeandritoG said:
This is for what?
Click to expand...
Click to collapse
It will restore things you lost just try it you got nothing to lose
Sent from my SM-A800F using Tapatalk
plumzup67 said:
It will restore things you lost just try it you got nothing to lose
Sent from my SM-A800F using Tapatalk
Click to expand...
Click to collapse
Hi friend, reading this thread I think it isn't my case...
http://forum.xda-developers.com/showthread.php?t=2507403
Buy thanks anyway... =)
plumzup67 said:
It will restore things you lost just try it you got nothing to lose
Sent from my SM-A800F using Tapatalk
Click to expand...
Click to collapse
Well, I tried flash it two times... Continues with imei null and unknown baseband...
Now I will try this...
http://forum.xda-developers.com/showthread.php?t=2567133
You never backed up the EFS originally ??
Or if you did what tool did you use ??
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!