Hi Everyone,
I have an P5110 running stock Samsung 4.04 ICS firmware it's rooted and has cwm touch recovery installed and titanium backup pro (root) installed.
My question is this how do i verify a Nanodroid backup ?
I have read it checks the backups before a restore.
However, When running version 5.xx of CWM recovery it failed twice to restore data and since i couldn't i find a way to check the data before i restored it.
Data was overwritten, however cwm reported a fail to write to data, and sure enough no data had been written but /data had been formatted.
Is their a way to verify a backup before i choose to restore it ?
i am now using ClockworkMod-Recovery_6.0.1.0
thanks
Col
Related
So my Nexus was acting really slow (I'm on 4.2.1), so I decided to backup via CWM and then factory reset, and do an Advanced Restore to restore my data. I backed up and did factory reset, but when I went to restore my backup, it couldn't be found. Apparently 4.2 moved the default CWM location to search "data/media/" and I didn't have my backups there (obviously). So I moved the clockworkmod folder from /sdcard/ to data/media/ and tried to restore. It gave me an MD5 mismatch, so I researched that, found a solution, and did restore. Unfortunately, that bricked my Nexus 7 so I had to restore via the ToolKit.
My question is…is there any possible way I can restore my data to my now factory-fresh (4.2.1) Nexus 7 from the backup I made? I have the backup and the blobs.
Bump, the same thing just happened to me and I dont want to create a new thread. Is there any way to restore a 4.1.2 backup from a device running 4.2.1? Thanks in advance
EDIT: I solved it by booting into CWM and then pushing the rom, full wiping and installing again
Hi everybody,
First of all I want to say thanks to this community because I found a lot of informations here and solved many problems I had.
I searched all the day and I don't know what to do with the issue I get now...
I decided to install JellyBlast V3 on my Galaxy Y GT-S5360. Before that I made a backup of my stock ROM with ClockWorkMod (v5.0.2.6) and then I installed JBV3.
All was allright and I wanted to restore my datas only from the backup with the CWM advanced restore. That didn't work (Maybe because I can't restore datas from a different ROM?)
So, I wanted to make a complete restore from the same backup to get all my datas back, but I get the following message :
"data.img not found. Skipping restore of /data
.android_secure.img not found. Skipping restore of /scard/.android_secure.
Restore complete!"
The phone can boot up but my datas are not restored at all.
I explored the backup folder and there is no "data.img"... but in some resolved threads I read people didn't have it neither... and I am a big optimist so I kept searching...
I tried to restore again but with another zip file of CWM (who resolve some bugs) I found here http://forum.xda-developers.com/showthread.php?p=27475895
But It failed again with the same issue.
I read that if the kernel changed the restoring is not possible anymore so a previous kernel have to be installed (http://forum.xda-developers.com/showthread.php?p=27475895 )
To be sure, I installed a stock ROM with Odin by following this http://forum.xda-developers.com/showthread.php?t=1465800
I picked the S5360_XXKL3_OXXKL1_XXKL3 bundle.
Since I installed the fresh ROM I tried to restore datas again, but I got the same issue again...
So, I want to understand why I get this error ?
Maybe flashing with a stock ROM is not enought to replace the present kernel by the original one ?
Thanks for enlighted me (and sorry for my english)
By any chance is your CWM called gt-s5360CWM or something
You have to backup with a clean CWM and restore with the same clean CWM
Sent from my
you'll never know
darkshadow246 said:
By any chance is your CWM called gt-s5360CWM or something
You have to backup with a clean CWM and restore with the same clean CWM
Sent from my
you'll never know
Click to expand...
Click to collapse
Indeed, the first CWM I used to create the backup was "GT-S5360_CWM.zip" but the restore doesn't work.
The second CWM I tried is called "CWM_bla_bla.zip" and the restore failed with this one too.
I think the backup I made is not proper
Thank you for your help.
PS : if my backup is corrupted, is there a way to recover at least my contacts with a backup explorer or something ?
EDIT : I think my backup is definitely not good, I made another one with the "unbugged" CWM and It makes more files including a "data.rfs.tar" file...
Hello, I am a novice at best when it comes to this. That being said I have successfully Unlocked my boot-loader, rooted and installed roms to my phone. Recently when using TWRP 2.7 I noticed that it would not mount data when restoring my backup. I then noticed it would not mount data when creating a new backup while using TWRP 2.7. I then installed CWM latest recovery. It does the same thing. In the process I got stuck in CWM and had to AP Fastboot to stock 4.4.2. Now with CWM it will not mount data when doing a backup. I cant load a rom without having a secure backup. What can I do? Need help! Calling all devs!
Device: Samsung Galaxy S4 (SGH-I337M)
Android:5.0.1
Rooted
cwm custom recovery touch version.
When I do a Nandroid backup it seems to do successfully but I see errors in the log file.
And when I restore using the same backup after it finishes restore process, all the services stop working (example: google.app ....)
I attach screenshots and log file for backup process.
Please explain why this is happening and how to fix it.
Thanks
Sam
____________
As lennyz & Reaper suggested I switched to twrp, both backup and restore are working smoothly.
Thanks for help.
CWM isn't updated anymore. So you should either swith to TWRP or Philz (thought Philz isn't updated anymore either but it still works).
Maybe that could fix it. Also make sure you have plenty of space left when you make a nandroid. Something like 5gb when you are on TW rom.
Use PhilZ, as it is based on CMW, so it should work with your backups. If you don't care about the backups anymore then go with TWRP. Haven't had any problems with TWRP so far.
Hi experts,
I would very much appreciate some help regarding the following:
I have a Samsung Galaxy S5 SM-G900F with factory installed stock rom G900FXXU1BPA2 (Android 5.0). I used the SkipSoft Unified Android Toolkit 1.4.5 to root the phone and install TWRP recovery (2.7.1.0-klte as recommended by Unified Android Toolkit). I made a first Nandroid Backup and was able to successfully restore this backup (I restored boot, system and data to verify that Nandroid restore works). I then used Titanium Backup to restore my apps from another phone, and all was well.
A week or so later I wanted to modify something I wasn't sure I wanted to keep (using apktool). I therefore made a second Nandroid backup and then proceeded to make modifications to the phone. After I saw the result, I didn't like it, and therefore restored the second Nandroid backup. After rebooting, the phone gave a flurry of forced stops ("Unfortunately XXX has stopped"). It is not a bootloop but I can't do anything meaningful with the phone other than restart it.
To try and resolve this, I used TWRP to wipe cache and dalvik cache and rebooted. The phone went through the lengthy "Android is upgrading" process but the result was the same: all my apps force stop.
I then decided to try and restore the original first Nandroid backup (which I had been able to restore successfully earlier), and this resulted in the same issue. Since I have several backups of this first backup I was able to verify that the files were good. Also did MD5 checksum verification in TWRP and it all checked out.
Using Odin, I was able to restore a stock ROM from SamMobile (G900FXXU1BOL1_G900FOJK1BOL1_ILO) and after restart, the phone works as usual, but of course all my apps and data were gone.
I was then able to use TWRP to restore only boot and system from the second backup, so I would be back on the exact same ROM that my phone came with, and this worked just fine; the phone started as if factory restored.
I then used TWRP to restore only data, and this resulted again in the same problem: all apps force close. Note that this is a restore of data only to the same phone running the exact same ROM that the Nandroid backup was made on, and it still did not work.
I have been thinking about this issue and searching through the various forums but I did not find anyone having this same exact issue. Here are some questions I came up with:
1. Is TWRP 2.7.1.0 completely compatible with this phone and with Android 5.0? Would it help if I installed a newer version of TWRP? Would I be able to restore Nandroid backups made with TWRP 2.7.1.0 with TWRP 3.X?
2. Assuming my second Nandroid backup is not corrupt, is there a better (less intrusive) restore I can do of the apps? Can Titanium Backup read TWRP 2.7.1.0 backups and restore them, including SMS?
3. What could be the reason for TWRP 2.7.1.0 restore not to be working properly? I did activate the fingerprint reader after the first Nandroid Backup, but if that is the issue I would have expected that first backup (in which fingerprints were not yet enabled) to restore properly and it doesn't.
Would appreciate any help!
Thanks,
AH
That version of TWRP is pretty old, possible it doesn't fully support 5.0
Grab 3.0.0.0 from here (newer versions are not fully bug free yet)
https://dl.twrp.me/klte/
Flash .tar version with ODIN 3.10.7
TiBu can read Nandroid backups and restore apps yes
Not sure about SMS
The method you used to root and flash TWRP is not a usual method used here, most of us use ODIN to flash TWRP and then flash SuperSU from recovery
or use CF Auto Root to root, and then flash TWRP with ODIN
I'd flash stock again, factory reset, and then flash TWRP and SuperSU, then try restoring your apps with TiBu
*Detection* said:
That version of TWRP is pretty old, possible it doesn't fully support 5.0
Grab 3.0.0.0 from here (newer versions are not fully bug free yet)
dl.twrp.me/klte
Flash .tar version with ODIN 3.10.7
Click to expand...
Click to collapse
Thanks *Detection*! I installed TWRP 3.0.0.0 as per your instructions and restored just data. Same result as before.
Then I used TWRP 3.0.0.0 to restore the entire backup including system, boot, recovery, and data. Same result (of course I lost TWRP 3.0.0.0 and was back on TWRP 2.7.1.0).
This exercise was useful for one reason: I now know that TWRP 3.0.0.0 is able to read Nandroid backups from TWRP 2.7.1.0.
This is quite crazy but I seem to be unable to restore a full Nandroid backup and get a working system.
Am going to try Titanium Backup.
Thanks again!
AH