Root Nandroid won't retore

[JustSomeDude]

Hey guys, I had a weird issue I was hoping you could shed some light on:

I was playing with the Xplod rom for a day, then tried to nandroid back to my MikG 2.55 setup, and got this error:

Oops... something went wrong!
Please check the recovery log!

So (1) where is the recovery log? and (2) Has anyone gotten this error before? I did everything exactly as I always do (in amon-ra, checked everything except "cache" and "sdext"), and didn't even rename it this time yet... the only difference is this time there was the option to check "recovery", and I did check that when creating the nandroid. Could that have been the issue?

I had a nandroid of 2.51 that restored just fine, so it wasn't completely panic-inducing, but I really want to make sure this doesn't happen again. Ideas?

 

[NaterTots]

I have had that same error before and it happened when I

created Nandroid
Loaded Rom on card
wiped
flashed new Rom

If I followed the Tutorial and,
Loaded Rom onto Card
Create Nandroid
Wiped
Flashed new Rom

Then it would be fine.

Maybe it was the recovery thing you mention? Even when flashing a Kernel I have found that just deviateing or skipping a seemingly small step will mess up your Nand restoring ability.
I do have a Nand of the previous Rom I was on but I'm nervous to even try it. I would assume to,

Create Nand of current,
Wipe everything,
Flash older Nand,
Reboot.

I'm sure someone with more knowledge of Nandroids will weigh in.


Naters

 

[andygu3]

Hey guys, I had a weird issue I was hoping you could shed some light on:

I was playing with the Xplod rom for a day, then tried to nandroid back to my MikG 2.55 setup, and got this error:

Oops... something went wrong!
Please check the recovery log!

So (1) where is the recovery log? and (2) Has anyone gotten this error before? I did everything exactly as I always do (in amon-ra, checked everything except "cache" and "sdext"), and didn't even rename it this time yet... the only difference is this time there was the option to check "recovery", and I did check that when creating the nandroid. Could that have been the issue?

I had a nandroid of 2.51 that restored just fine, so it wasn't completely panic-inducing, but I really want to make sure this doesn't happen again. Ideas?

Since I don't keep nandroids around very long, I've always checked everything when making a nandroid and I've never had this issue. It may be an isolated incident but in the future, I would check everything.

Do you have your sd card partitioned? This would be the sd ext check for a nandroid.

 

[funky_muzic]

I had this problem just recently. The problem could be related to the name of the nandroid backup. I change the file name so that I can recognize it as a certain ROM, Date, etc... However when I left spaces in the file name I received the error trying to restore. I then only changed the file name to remove any spaces and the Nandroid restored just fine.

Hopefully this helps. I know I freaked out when my Nandroid would not restore! Good luck

 

[JustSomeDude]

Thanks for the replies, guys.

I actually did not choose sxext (I don't have my card partitioned). And as for renaming, I did rename it, but in the same way I have done dozens of others in the past (no spaces, simply adding _MikG_2-55 to the end). In fact the nandroid that did restore properly was renamed in exactly that same way. So I'm still stumped as to what happened.

 

[Rxpert83]

Nandroids aren't perfect. I've had this issue once before as well.


Thats why its important to always have one that works (one you've tried successfully) backed up somewhere safe with your WiMax keys

 

[JustSomeDude]

Nandroids aren't perfect. I've had this issue once before as well.

Thats why its important to always have one that works (one you've tried successfully) backed up somewhere safe with your WiMax keys

Thanks, as with all technology, that makes sense. Luckily I have three older nandroids on my computer and one on my SD that are proven to work (plus a copy of my wimax keys in dropbox).