Root nandroid back up question....

[rick311]

if i do a nandroid back up, and then get a refurb eris, can i restore that backup to the new phone?

 

[scary alien]

if i do a nandroid back up, and then get a refurb eris, can i restore that backup to the new phone?

Yes, you will probably have to rename the directory above the "BDS-ccyymmdd-hhmm" directory to match the ID of your new phone.

You can find this via the "adb devices" command from the Android SDK's adb utility or I believe its in the back of your phone under the battery. I thought that there was a software way to obtain it...gimme a second and I'll see.

 

[scary alien]

Rick,

I poked around and did some searching...can't find a file on the device that returns the serial number. But I do know that its on the back of the phone under the battery as "s/n" (serial number).

I even tried a couple of apps that purported to report it...they only list the MEID that the Settings -> About phone already lists.

You can do the "adb device" thing, or, when you do re-root, just do a Nandroid backup on the new phone and see what directory he made it. Then, just move your old backups to the same directory and Nandroid should be able to see it just fine.

Cheers!

 

[roscuthiii]

Damn scary, your knowledge of the inner-workings of Android is getting to be, well, scary. Have you considered opening up your own tech support hotline?

 

[scary alien]

Damn scary, your knowledge of the inner-workings of Android is getting to be, well, scary. Have you considered opening up your own tech support hotline?

Lol, I don't know about that . The gold-standard around here is erisuser1.

Most of what I've learned comes from reading through the threads and trying to make sense of them. I stand on the shoulders of other, more knowledgable folks (or at the least the ones that have made mistakes and were kind enough to share their solutions).

Its funny, but I've been a computer geek/nerd for a long time now (hobby and career-wise), and it used to be that when I got home from work, I wanted nothing to do with computers. Now, these Android phones have really piqued my interest and gotten me excited again..."Hi, my name is scary alien and I'm addicted to Android." .

 

[erisuser1]

Yes, you will probably have to rename the directory above the "BDS-ccyymmdd-hhmm" directory to match the ID of your new phone.

You can find this via the "adb devices" command from the Android SDK's adb utility or I believe its in the back of your phone under the battery. I thought that there was a software way to obtain it...gimme a second and I'll see.

adb shell getprop ro.serialno

An even easier way is just to make a nandroid backup on the new phone and it will create the directory of the correct name for you - them just move the older nandroid backup into that folder (or all of em, for that matter).

eu1

 

[rick311]

adb shell getprop ro.serialno

An even easier way is just to make a nandroid backup on the new phone and it will create the directory of the correct name for you - them just move the older nandroid backup into that folder (or all of em, for that matter).

eu1

EU1, you're the man! any progress on the dropped calls on the froyo roms?

 

[erisuser1]

EU1, you're the man! any progress on the dropped calls on the froyo roms?

It is very hard to know for sure - I am trying to make something that only rarely happened happen never. It is a bit difficult to be confident you have done something meaningful when the symptom of the cure is that "nothing happens" - and the problem didn't really happen all that often in the first place.

What would be helpful is if there is someone out there that experiences this problem regularly - like once or more per day. Then it would be much more obvious if a patch was actually having a positive effect.

If that happens to anyone reading this with that kind of frequency, and you are willing to help out testing, let me know - I will put together a "flashable" patch to make it easier to install using the normal Amon_RA flashing procedures (no wipe).

eu1

 

[rick311]

It is very hard to know for sure - I am trying to make something that only rarely happened happen never. It is a bit difficult to be confident you have done something meaningful when the symptom of the cure is that "nothing happens" - and the problem didn't really happen all that often in the first place.

What would be helpful is if there is someone out there that experiences this problem regularly - like once or more per day. Then it would be much more obvious if a patch was actually having a positive effect.

If that happens to anyone reading this with that kind of frequency, and you are willing to help out testing, let me know - I will put together a "flashable" patch to make it easier to install using the normal Amon_RA flashing procedures (no wipe).

eu1

my phone does it at least once every other day. make the flashable patch and if my next phone (to be delivered tuesday) does it, ill flash it and let you know my results.

 

[erisuser1]

my phone does it at least once every other day. make the flashable patch and if my next phone (to be delivered tuesday) does it, ill flash it and let you know my results.

Thanks - I'll try to get it put together tonight.

eu1

 

[erisuser1]

my phone does it at least once every other day. make the flashable patch and if my next phone (to be delivered tuesday) does it, ill flash it and let you know my results.

[ Edit ] - Deprecated as of 2010/09/20 - (it has no effect; the crashes continue. Sorry for wasting anybody's time)


I put up flashable .zips that allow you to install the test (two files), and also uninstall them (and recover whatever you were using before) when you are done testing. Those can be found in this XDA post

Thanks in advance for your help.

eu1