Last time, before flashing RemICS UX, I did a backup on the ROM that I was using which is Bionic 2 ROM. I used CWM version 6 when backing it up. Then I made a copy of "backup" and "blobs" to my PC. I then tried to restore the Bionic 2 ROM after playing with RemICS UX but MD5 mismatched. Anyone knows why?
Related
I applied Rogue FC06 Kernel Recovery to Calk's FC06 ICS ROM and everything looked working fine with CWM recovery thru Rom Toolbox and Manager.
Before this Rogue FC06 Kernel, CWM was failing on ICS Rom. It was not even launching.
Now backup thru CWM recovery looks working fine but, recovery is not working.
Any one else tried this?
[Update]
Nandroid backup failed on AFV MD5 Checksum verification (screen attached).
Nandroid verifiation failed second time after the fresh nandroid backup using CWM 5.0.2.7 thru Rom Toolbox.
It's only failing from data.ext4.tar file.
--> Got the MD4 Sum data manually using AFV for data.ext4.tar file and changed MD5 Checksum data from nandroid.md5 file.
--> Ran the nandroid verification again and it successfully finished. (second screenshot)
--> Going back to Rom Toolbox and invoked the Reboot Recovery -> CWM Recovery 5.0.2.7
--> ran restore again with the file just manually fixed and verified
--> Getting MD5 mismatch! error message
--> Rebooted system (went back to FC06 Rom)
--> Redo the nandroid verification and it failed again > MD5 checksum changed again
<CWM 5.0.2.7 is based on the CM7 and it does not work properly on CM9>
--> Recovering system from Nandroid backup made from Rogue FC06 Recovery Kernel
<Conclusion>
If you are an expert in this area, you can do it with your own way but if you don't know howto, just stick with nandroid backup and recovery with Rogue Recovery. So far, this is the only one working fine for me.
Why use toolbox and manager to do any flashing ... wow you must really trust everyone in the world ...just use cwm to flash until all these bricks stop or you may be going to sprint when you don't have to
Sent from my SPH-D710 using xda premium
Epix4G said:
Why use toolbox and manager to do any flashing ... wow you must really trust everyone in the world ...just use cwm to flash until all these bricks stop or you may be going to sprint when you don't have to
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I know your concern. But what I'm trying to do is just verifying the CWM recovery thru various method.
This is my first ever post on this awesome website. I have an Xperia play which i just modded(after Sony cancelled ICS).
I installed Cyanogen Mod 7.2 three days ago. After that I backed it up using the clockwork mod backup.
Then I installed ICS beta and later the cyanogen mod 9. I couldn't get the camera to work and videos weren't streaming from websites(through the mobile player). So I decided to restore the CM7 backup I had made earlier. I backed up my current rom, cleared the cache and did factory reset(all in recovery) and then restored the CM7 mod. It was successfully restored but then my phone got stuck in the boot loop where I just see the starting screen of CM7 with the arrow revolving around the android. I had to take out the battery and then restore the CM9 again to get my phone to boot.
Where did I go wrong? Am I supposed to install CM7 again from zip file and then restore? Or is my backup corrupted?
napsterstiffler said:
This is my first ever post on this awesome website. I have an Xperia play which i just modded(after Sony cancelled ICS).
I installed Cyanogen Mod 7.2 three days ago. After that I backed it up using the clockwork mod backup.
Then I installed ICS beta and later the cyanogen mod 9. I couldn't get the camera to work and videos weren't streaming from websites(through the mobile player). So I decided to restore the CM7 backup I had made earlier. I backed up my current rom, cleared the cache and did factory reset(all in recovery) and then restored the CM7 mod. It was successfully restored but then my phone got stuck in the boot loop where I just see the starting screen of CM7 with the arrow revolving around the android. I had to take out the battery and then restore the CM9 again to get my phone to boot.
Where did I go wrong? Am I supposed to install CM7 again from zip file and then restore? Or is my backup corrupted?
Click to expand...
Click to collapse
did you flash a GB kernel? Restoring a nandroid doesn't restore the kernel.
Sent from my R800x using Tapatalk 2
Thank you for the swift reply. I didn't. I am really new at this so you'll have to pardon my ignorance. Will i have to flash the GB kernel with fastboot? Where can I get this kernel and is there a particular version I have to use? Thanks again.
Hi all,
I'm on Aokp build 38
I checked my goo.im app (goomanager) and checked checked for update. And I got one. It's build 39. How do I go around to update this?
Do I need to make a titanium backup? Or whatnot?
Can I get some help please.
I'm only new to rooting.
Please be gentle. Lol
Sent from my Galaxy Nexus using Tapatalk 2
you could backup your stuff with titanium backup, but I'd just dirty flash this over #38. Has worked for me since the last 4 builds.
Always do a NANDroid backup before flashing, just in case.
edit: by "dirty flash" I mean: just download the build 39' .zip, boot into your custom recovery, and flash it over your current build AFTER doing a full backup. Than flash the google-apps again, if wanted, reboot and see if it works for you
okay thanks.
but how do i do a NANDroid backup?
sorry for the one million and one questions. lol
Boot into recovery ... go down to Backup and restore and select Backup.
There are (at least) two ways to backup your phone.
1) Via CWM (clockworkmod recovery). Navigate the menus, there's a backup option there. It will be saved to your phone.
2) Use the Galaxy Nexus Toolkit. It's available here on the forums.
So... I flashed AGAT_Recovery tREC_v0.2.2 and was intending to restore a "nandroid" backup from before I wiped my phone. First of course I made a backup (just Stock Rooted ROM I used to flash the recovery partition). I then tried to restore the previous image of my custom ROM and the restore failed. Investigated and found that the filenames in the nandroid backup folder were named differently from previous nandroid backups I had taken:
system.ext4.tar (0 bytes)
system.ext4.tar.a (large)
data.ext4.tar (0 bytes)
data.ext4.tar.a (large)
I'm not sure how the backup format changed as I don't recall updating the recovery partition, I'm wondering if some ROM I installed did this for me (if so thanks a lot). Looks like this:
http://forum.xda-developers.com/showthread.php?t=2194171
So trying to be clever, I deleted the 0 byte files and renamed all of the stupid .a files to the original (I had no .b, .c files etc.) Then I did a restore.
The restore completed successfully but com.android.Phone was crashing on startup repeatedly, the launcher wasn't working properly and basically the image wasn't usable.
I then decided that it wasn't worth all the trouble and I would just restore to the backup I had taken of the Stock Rooted ROM immediately prior to this whole mess starting (using AGAT_Recovery tREC_v0.2.2). The restore completed successfully but the O/S didn't boot at all (it just showed a black screen after POST of the Samsung logo).
For now I've reflashed stock using ODIN.
So basically my question is: why is this so complicated? Am I missing something here? Is AGAT_Recovery 0.2.2 not a good choice for a recovery partition?
Is the recovery you are trying to restore the sane recovery you are currently running.
I've gotten stuck by being in a different version of the same recovery and it just didn't work. I had to be in the same recovery in order to do a restore.
Just a thought
Bt is right. You should always use the same cwm to restore that you used on the backup. And the latest Agat recovery is essentially bugfree, which is 0.3.5. So I would use that. And it's not difficult, at all . Just takes a few "oh craps" to get it down pat!
Sent from my SPH-D710 using xda premium
thanks
jdsingle76 said:
Bt is right. You should always use the same cwm to restore that you used on the backup. And the latest Agat recovery is essentially bugfree, which is 0.3.5. So I would use that. And it's not difficult, at all . Just takes a few "oh craps" to get it down pat!
Click to expand...
Click to collapse
I suspect part of the reason I couldn't restore the one backup image was because I wasn't using the same version, or perhaps even product. Doesn't explain why the older version of Agat couldn't restore its own backup though. I'll try the newer version out. Thanks!
It's too bad the utilities don't write out some metadata about the format used, what product/version did the backup, etc.
philipdl71 said:
I suspect part of the reason I couldn't restore the one backup image was because I wasn't using the same version, or perhaps even product. Doesn't explain why the older version of Agat couldn't restore its own backup though. I'll try the newer version out. Thanks!
It's too bad the utilities don't write out some metadata about the format used, what product/version did the backup, etc.
Click to expand...
Click to collapse
That was an earlier kernel that probably still had bugs. Could have been a bad backup. It happens. The latest kernel will do solid backups/restores and serve as a very dependable dd. Good luck.
Sent from my SPH-D710 using xda premium
Had two backups created with clockwork mod and flashed a diff ROM and after a bit decided it wasn't for me. So i decided to go back to my previous backup which was beanstalk and when I tried to restore it I got error message saying md5 match failed so i tried to restore the other backup i had from a couple weeks back of a diff rom and got the same error message..anyone know why? Only thing I did was rename the backups so I identify them apart.
Never had a issue restoring backups using twrp which is recovery I preferred but a lot of the newer ROMs mostly 4.4 are requiring cwm.
sent from a note taker w/beanstalk 4.4
Nvm please close thread
sent from a note taker w/beanstalk 4.4
booma428 said:
Had two backups created with clockwork mod and flashed a diff ROM and after a bit decided it wasn't for me. So i decided to go back to my previous backup which was beanstalk and when I tried to restore it I got error message saying md5 match failed so i tried to restore the other backup i had from a couple weeks back of a diff rom and got the same error message..anyone know why? Only thing I did was rename the backups so I identify them apart.
Never had a issue restoring backups using twrp which is recovery I preferred but a lot of the newer ROMs mostly 4.4 are requiring cwm.
sent from a note taker w/beanstalk 4.4
Click to expand...
Click to collapse
I had a similar issue. This is how I fixed it
In recovery...
1.) Wiped the device 3x
2.) Wiped Cached 3x
3.) Wiped Delvik cache 3x
4.) Installed TWR through Odin
5.) Flashed CWM 6.0.4.3
6.) Flashed cm11 4.4
7.) Flashed Odexed Gapps
8.) Flashed SuperSU
Hope it helps