Develop Bugs

Why cant I ever seem to restore my backups?

For the life of me, I cant figure out why I can never restore my back ups after testing out various roms and kernels. I know it has something to do with the kernels and/or recoveries that are used when backing up and restoring but I cant seem to figure it out. Every time I try to restore a backup I usually get an MD5 mismatch and it fails. I THOUGHT that if I did the backup and restore using the SAME kernel/recovery versions that it would work, but that doesnt seem to be working. Is there something I am missing? Ill give you an example in case you have any tips.
I was running Calks v1.5 for awhile, then decided I wanted to try the AOKP rom. As noted in the AOKP thread, to restore, Odin the EL26 CWM kernel/recovery and run a back up. So I Odin the kernel/recovery, ran the backup, then attempted a restore just to see if it worked. Successfully able to restore from within that same CWM session. So I Odin EL26 CWM again, and this time flashed the AOKP and gapps and rebooted into AOKP. No problem there. Messed around with AOKP (which is awesome) but wanted my daily back so I Odin the EL26 CWM again, and tried to restore the Calk 1.5 and got the MD5 mismatch.
What am I doing wrong?

Are you renaming them? They can't have any spaces in the name, must be something like aokp_may10 instead of aokp may 10
Sent from my SPH-D710 using Tapatalk 2

Son of a *****!!! lol I definitely renamed the backups after they completed so I would know which one was which. And definitely had spaces in the names. So thats screwing up the MD5 hash? If I rename them back to what they were will they work?

I used to get that all the time if I copied the nandroid off to the pc and back.
Anyway, if that's not the case for you, I think it's because you are on a totally different version of recovery.
Wipe the phone using Calk's Format All, install Calkulin's v1.5 rom from scratch, boot into recovery and THEN do your restore.
Edit: Well, I saw you beat me to it on the post. LOL
I'll be your Plan B then.

tdunham said:
I used to get that all the time if I copied the nandroid off to the pc and back.
Anyway, if that's not the case for you, I think it's because you are on a totally different version of recovery.
Wipe the phone using Calk's Format All, install Calkulin's v1.5 rom from scratch, boot into recovery and THEN do your restore.
Click to expand...
Click to collapse
Nah I did the backup and attempted restore from EL26 CWM (so I could flash the ICS rom "safely"). I also didnt copy them from the SD card so hopefully thats one less reason for the failure. Thanks

ryan2202 said:
Son of a *****!!! lol I definitely renamed the backups after they completed so I would know which one was which. And definitely had spaces in the names. So thats screwing up the MD5 hash? If I rename them back to what they were will they work?
Click to expand...
Click to collapse
That im not sure of, but try to rename with no spaces and report back
Sent from my SPH-D710 using Tapatalk 2

!!! It f*cking worked lol. Many many thanks!! And to think of all the time I have wasted reloading roms from scratch... :beer:

Glad that worked! The bright side is your an expert at flashing roms now!
Sent from my SPH-D710 using Tapatalk 2

ryan2202 said:
!!! It f*cking worked lol. Many many thanks!! And to think of all the time I have wasted reloading roms from scratch... :beer:
Click to expand...
Click to collapse
Lol I remember having this problems back in the days of the galaxy s, I've spent so many hours setting everything up all the time more than testing the roms itself, until I asked this same question.
Sent from my SPH-D710 using Tapatalk 2

Nandroid Restore Help

I'm new to Samsung Android phones, and new to the E4GT, so I need a little help.
I always flash the zip for the EL26 CWM5 recovery like instructed, soooo, here is my issue.
I'm running AOSP and thought I would try CM10 JB, soooo, I flashed into EL26, performed a full nandroid to my Ext SD. I flashed JB and gave it a shot. For issues known to all, I wanted to switch back
So, I went into recovery, flashed the EL26 recovery and rebooted recovery, I then restore the nandroid backup I just made, rebooted, went to the Samsung screen (with the yellow !). After some time, about 20-30 seconds, it goes to a black screen indefinately until I pull the battery.
Any ideas? I have yet to get a nandroid to work on this device. Had no issues at all on my 3D. I'm sure I'm doing something wrong.
TIA,
Tee Jay

You need to flash the AOSP kernel. Well first can you boot into recovery or download mode
Sent from my SPH-D710 using XDA

g_ding84 said:
You need to flash the AOSP kernel. Well first can you boot into recovery or download mode
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Yeah I can get into recovery fine, so I flashed an AOSP kernel and then my wifi didn't work.

Is it not connecting?
Sent from my SPH-D710 using XDA

g_ding84 said:
Is it not connecting?
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Nope, won't even turn on. But if I do a full clean flash of the exact ROM, it works fine.

I'm by far no expert but I'd say the kernel is being replaced by the gb recovery kernel when you flash back for your safe recovery.I personally keep a couple various recoveries so I can nandroid backup on the kernel native to the Rom and then the backup will contain the proper kernel.I think I got that right.so....nandroid b4 recovery has been my habit.

Had this issue before, minus the yellow triangle....anytime you're on an aosp rom and do a nand via el26, the nand stores the last kernel used (which is GB el26). After you restore, wipe cache and dalvik and then flash an aosp kernel, probly one from chris41g. Reboot and should he good to go.
Sent from my SPH-D710 using xda app-developers app

dante32278 said:
Had this issue before, minus the yellow triangle....anytime you're on an aosp rom and do a nand via el26, the nand stores the last kernel used (which is GB el26). After you restore, wipe cache and dalvik and then flash an aosp kernel, probly one from chris41g. Reboot and should he good to go.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Right, I tried that with my AOKP backup, I was able to boot. But then my WiFi wasn't working because of something to do with the Kernel I'm assuming

Can you flash TWRP using CWM?

Is it possible?
Ive heard TWRP is the better recovery for JB and ICS, currently i have CWM but would like to get TWRP before flashing CM10/AOKP.
Can i just load the recovery zip file and flash in CWM?

Yes you can, but you're mistaken about TWRP being a better recovery for AOSP Jelly Bean roms. Using CWM 6.0.1.4 I never got one random reboot or SoD. I first flashed CM10 official nightly using TWRP 2.2.2.0 and got a random reboot waiting for the initial 10 minute wait to finish. Then I got another one playing around with the power button checking to see the consistency of the CRT animation. I switched over to official CWM 6.0.1.4 using rom manager and never had an issue afterwards. Aside from the usual graphics glitch here and there.
Sent from my SGH-T989 using xda premium

I guess if i have 6.0.1.4 i should be good to go right?
I suppose neither is the "wrong" one to use. Plus i have used Nandroid backups since last year.
Thanks!

Khameleon said:
I guess if i have 6.0.1.4 i should be good to go right?
I suppose neither is the "wrong" one to use. Plus i have used Nandroid backups since last year.
Thanks!
Click to expand...
Click to collapse
Personally I think TWRP is the better recovery. Its feature set is awesome such as queing files to flash and what not. But I really do believe these roms play favorites. Touchwiz roms seem to work the best when using TWRP. AOSP roms seem to work best with CWM. I use both recoveries and switch between TWRP for DARKSIDE Evolution and CWM for AOSP jelly bean roms.
Sent from my SGH-T989 using xda premium

I have only flashed JB twice with TWRP 2.3.1 and have had zero RRs or SODs(so far)
Reading the changelog it seems to have shifted more towards JB, but im a noob so wth do i know haha
TWRP is shhhweet

CWM 6027 Touch from ATT forum

Alright....so alittle history. kc_exactly is to blame and to thank for this. He just got me thinking. Especially with people starting to test the JB port from houstonn. Which only flashes with CWM.
Disclaimer: You do this at your own risk!! Can't blame anybody but yourself if it messes things up!
I installed sk8erwitskil's Touch CWM 6.0.2.7 v14.4.7 from the ATT forums here. http://forum.xda-developers.com/showpost.php?p=34567118&postcount=1.
I wanted to see if it would work as kc had said in a post earlier. And it did and does!!! CWM backup works using .tar. I haven't tried dedup yet.
So what's the purpose of this post you ask? Well, from what I've found out so far, we can install CWM, create a backup using .tar which is default, and restore with it. In "mount and storage" I formated system, data, cache. In advanced, I formated dalvic cache. Pretty much wiping out the phone and it restored just fine. Actually 4 times so far.
So, and again, part of this has been said by kc_exactly, if you keep TWRP, AND CWM6027 recoveries, your ROM of choice, and backups in both TWRP and CWM on your Internal storage you'll be able to bounce back and forth testing the JB port or whatever else will require CWM.
I've done this multiple times now and it's worked everytime!!!
Make a TWRP backup
Install CWM 6027, reboot to system
reboot to recovery and make a CWM backup using .tar
That's it!!
Now each time you want to use a different recovery, just install it, reboot to recovery and restore your backups.
Maybe this is old news, or even a "No sh*t Sherlock" thing. But our CWM had too many issues, and I'm really liking sk8erwitskil's Touch version. And it seems to be working well. I was in CWM for at least 10min straight and it never got hot.
It does have somewhat of a learning curve, so make sure you read sk8's instuctions on the first 2 posts.

Re: CWM6027Touch from ATT forum
engine95 said:
Alright....so alittle history. kc_exactly is to blame and to thank for this. He just got me thinking. Especially with people starting to test the JB port from houstonn. Which only flashes with CWM.
Disclaimer: You do this at your own risk!! Can't blame anybody but yourself if it messes things up!
I installed sk8erwitskil's Touch CWM 6.0.2.7 v14.4.7 from the ATT forums here. http://forum.xda-developers.com/showpost.php?p=34567118&postcount=1.
I wanted to see if it would work as kc had said in a post earlier. And it did and does!!! CWM backup works using .tar. I haven't tried dedup yet.
So what's the purpose of this post you ask? Well, from what I've found out so far, we can install CWM, create a backup using .tar which is default, and restore with it. In "mount and storage" I formated system, data, cache. In advanced, I formated dalvic cache. Pretty much wiping out the phone and it restored just fine. Actually 4 times so far.
So, and again, part of this has been said by kc_exactly, if you keep TWRP, AND CWM6027 recoveries, your ROM of choice, and backups in both TWRP and CWM on your Internal storage you'll be able to bounce back and forth testing the JB port or whatever else will require CWM.
I've done this multiple times now and it's worked everytime!!!
Make a TWRP backup
Install CWM 6027, reboot to system
reboot to recovery and make a CWM backup using .tar
That's it!!
Now each time you want to use a different recovery, just install it, reboot to recovery and restore your backups.
Maybe this is old news, or even a "No sh*t Sherlock" thing. But our CWM had too many issues, and I'm really liking sk8erwitskil's Touch version. And it seems to be working well. I was in CWM for at least 10min straight and it never got hot.
It does have somewhat of a learning curve, so make sure you read sk8's instuctions on the first 2 posts.
Click to expand...
Click to collapse
This looks promising. Thanks for "guinea pigging" it.
Sent from my LG-LS970 using xda app-developers app

Xiutehcuhtli said:
This looks promising. Thanks for "guinea pigging" it.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I'm glad I tried it too!
Right now I'm in flashaholics heaven. I have a TWRP ICS backup, a CWM ICS backup, and a CWM JELLYBEAN backup!! I'm able to play with whatever blows up my skirt. OK pants.
To all the *****y posts about this phone not going anywhere? Stay away!! We have a hellava DEV crew that is moving right along. And I'm lovin it!!!

engine95 said:
Thanks. I'm glad I tried it too!
Right now I'm in flashaholics heaven. I have a TWRP ICS backup, a CWM ICS backup, and a CWM JELLYBEAN backup!! I'm able to play with whatever blows up my skirt. OK pants.
To all the *****y posts about this phone not going anywhere? Stay away!! We have a hellava DEV crew that is moving right along. And I'm lovin it!!!
Click to expand...
Click to collapse
what i did was after i flashed jelly bean and restored my apps and stuff, i re installed twrp and made a backup so i never have to switch from twrp to cwm.

Re: CWM6027Touch from ATT forum
But don't we need to use CWM to flash and/or update houstonn updates?
Sent from my LG-LS970 using xda premium

Thanks for the info, this works great on my OG!

roguejam said:
Thanks for the info, this works great on my OG!
Click to expand...
Click to collapse
Works Great!!!

engine95 said:
But don't we need to use CWM to flash and/or update houstonn updates?
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
If I'm reading the thread correctly, the idea is that you make a backup including the recovery so you can switch back and forth at will.

VoluntaryMan said:
If I'm reading the thread correctly, the idea is that you make a backup including the recovery so you can switch back and forth at will.
Click to expand...
Click to collapse
I'm not sure if this is a question, or a comment? So I'll take it as a question.
You are correct. It's been working great for me so far. I'll bet I've restored over 20 times now and it's worked great. I've put it through all its paces and it's worked fine. I've tested and played with houstonn JB and I gotta say I really like JB!
So from what I can tell, we can use this recovery, and do whatever we want. Play with JB for a while, then switch back to ICS.
Sent from my LG-LS970 using xda premium

engine95 said:
I'm not sure if this is a question, or a comment? So I'll take it as a question.
Click to expand...
Click to collapse
I was trying to answer your question. Looks like you figured it out already though.

VoluntaryMan said:
I was trying to answer your question. Looks like you figured it out already though.
Click to expand...
Click to collapse
My bad then. Well, I guess I gave everybody an update.
Sent from my LG-LS970 using xda premium

wifi not working
i just flash it twice on lg e970 at&t....my wifi is not working any help................

gomzy85 said:
i just flash it twice on lg e970 at&t....my wifi is not working any help................
Click to expand...
Click to collapse
This is an older recovery. And the wifi has to do with the ROM, more than likely. Go to the TWRP thread or the root guide, under Working Recoveries. There you'll find the newest recoveries. KK included.
Then go to the ROM thread that you flashed and your answer is probably there. If not, ask there.
Sent from my LG-LS970 using XDA Premium 4 mobile app

first time using custom recovery

why didnt i start with clockworkmod instead of twrp. for hours now i thought i was doing something wrong while trying to restore a rom. it turns out the newest twrp is buggy. why are people recomending the latest twrp when it it so buggy.

I think most people still recommend 2.5.0.2, because 2.6 is so buggy...
Sent from my SGH-M919 using XDA Premium 4 mobile app

Nexus 6 said:
why didnt i start with clockworkmod instead of twrp. for hours now i thought i was doing something wrong while trying to restore a rom. it turns out the newest twrp is buggy. why are people recomending the latest twrp when it it so buggy.
Click to expand...
Click to collapse
Yes, TWRP has issues, use CWM. I'm using it for a while. So far so good
Sent from my SGH-M919 using xda app-developers app

TWRP is my preferred recovery and I've had zero issues with version 2.5.0.2 since I got this phone.

Nexus 6 said:
why didnt i start with clockworkmod instead of twrp. for hours now i thought i was doing something wrong while trying to restore a rom. it turns out the newest twrp is buggy. why are people recomending the latest twrp when it it so buggy.
Click to expand...
Click to collapse
I had exactly the SAME expirence.although I'm not new at rooting and using custom roms this being a new device for me I took everyone's advice and installed twrp. it was so buggy that it almost bricked my device. it got stuck on the introduction screen I couldn't get into tecovery or get out of the screen.i Eben pulled battery and it continued on that screen. finally finally I was able to get into the recovwry system, I rebooted and immediately I downloaded cwm recovert touvh wick has been wonderful ever since. That said, I thought this expirence with twrp was mine alone until ive heard of similiar complaints. I would NOT recommend twrp to ANYONE myself.i couldn't even flash a rom on it. I'm stocking with cwm recovery where its solid and works well

Nexus 6 said:
why didnt i start with clockworkmod instead of twrp. for hours now i thought i was doing something wrong while trying to restore a rom. it turns out the newest twrp is buggy. why are people recomending the latest twrp when it it so buggy.
Click to expand...
Click to collapse
I am clueless as to why anyone would want to use TWRP as well lol. CWM has always done its job.

When I restore a backup that I made, do I have to wipe anything before or after the restore process?