Database Users

Nandroid Backups and Fresh ROM Problem

First, I just wanted to ask if a Nandroid backup on one CDMA hero could be safely used on another CDMA hero. I should specify that there are 2 different versions of RA on the phone...for some reason my phone wouldn't work with v1.5.2 and my brothers wouldn't with 1.2.3
Second,
I am attempting to reinstall Teeter on my phone from the Fresh Rom Pre-Kitchen 0.2 and it simply won't work. Debug on pre-kitchen comes through fine, I have install lock screens on 2 phones from it but couldn't get teeter to reinstall on either.
Any help would be greatly appreciated...thanks

I know for a fact that a Nandroid backup from one device will not work on another, atleast not the whole backup. Some portions of the backup are non-device-specific, while others are. I don't know about the Teeter problem though... I have never tried to reinstall an app. Have you made sure that you have allowed the phone to install from unknown sources?

you could just push it to your phone manually

wtphoto said:
you could just push it to your phone manually
Click to expand...
Click to collapse
+1 on that. Everything always goes more smoothly for me when I do it manually and know exactly what's goin on.

mrinehart93 said:
I know for a fact that a Nandroid backup from one device will not work on another, atleast not the whole backup. Some portions of the backup are non-device-specific, while others are. I don't know about the Teeter problem though... I have never tried to reinstall an app. Have you made sure that you have allowed the phone to install from unknown sources?
Click to expand...
Click to collapse
I've used backups from other phones quite a few times with no problems. one from my phone is currently being used by another member on xda with no problems. my gf got a new hero from sprint (paint chip on end key) and we restored her backup with no problems yet. that was three weeks ago.
I'm not saying your wrong, but my personal experience is otherwise..

I have tried pushing it, and (teeter) will not install, it gives me an error and says that it cannot be installed.
Tomorrow I will try other files to see if they work but other than a corrupt file I'm not sure what the problem could be.

restore nandroid on SLCD?

i used to have an AMOLED inc from the day it was released. it just broke, and it got replaced with a brand new SLCD. i rooted it, and itll restore my nandroid's from before, but when i reboot out of the recovery, itll just hang at my boot splash screen. if i install the same rom (cyan 6.1, miui 11.19) from fresh, itll boot into the rom.
any idea? no big deal as i have my apps backed up with TB, but id like to restore back to my rom so all my settings are back.
also- on miui 11.19, after a while i started getting reboots every like 30 seconds. not sure why.

Trying to restore an AMOLED nandroid to a SLCD phone probably isn't going to work well due to the different hardware drivers. In short, you're trying to restore incompatible display software onto your phone.
That being said, restoring a nandroid from another phone is never a good idea unless your old phone has been destroyed or is still in your hands. Otherwise, there's a distinct probability that if the old phone is repared and sent out as a FRU, both devices would share the same android_id. As such, apps that you purchase could be involuntarily pushed the another user and vise versa.

Gotcha. ill delete those backups and install MIUI fresh, and then back it up from my new phone.
its still safe to restore apps+data from titanium backup right? (not system data, just apps/appdata)

You need a kernel that supports slcd. Your nandroid will work, but the kernel needs to be change to use the slcd display. All the system stuff is the same.
Restore the nandroid then apply the appropriate kernel afterwards before rebooting. Your system should work again.
If your nandroid is stock HTC you'll need a stock kernel. For slcd of you are running an aosp rom you'll need an soap kernel.
Sent from my ADR6300 using XDA App

how do i know which kernels will work with SLCD? or does the dev specify that in the thread for each kernel?

Most times the devs will say. Most times... remember kernels are specific to the type of build, aosp or HTC.
ufvj217 said:
how do i know which kernels will work with SLCD? or does the dev specify that in the thread for each kernel?
Click to expand...
Click to collapse
Sent from my ADR6300 using XDA App

linuxmotion said:
You need a kernel that supports slcd. Your nandroid will work, but the kernel needs to be change to use the slcd display. All the system stuff is the same.
Restore the nandroid then apply the appropriate kernel afterwards before rebooting. Your system should work again.
If your nandroid is stock HTC you'll need a stock kernel. For slcd of you are running an aosp rom you'll need an soap kernel.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Restoring the nandroid will, however, introduce the aforementioned security hole.

najaboy said:
That being said, restoring a nandroid from another phone is never a good idea unless your old phone has been destroyed or is still in your hands. Otherwise, there's a distinct probability that if the old phone is repared and sent out as a FRU, both devices would share the same android_id. As such, apps that you purchase could be involuntarily pushed the another user and vise versa.
Click to expand...
Click to collapse
Can you explain why. Or provide a link that can. Never heard of that security hole, but would like to know more about it because What your saying seems probable.
Sent from my ADR6300 using XDA App

linuxmotion said:
Can you explain why. Or provide a link that can. Never heard of that security hole, but would like to know more about it because What your saying seems probable.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Search is blocked from my LAN at work. However, if you search adrynalyne's posts, he was the one who discovered it. IIRC, he had posted the exact details over at androidforums.com. Essentially, he and a friend had restored a nandroid backup from one of their phones onto the other. From there, they noted that when one person installed an app using Appbrain's web installer, it was pushed to both phones.
ETA: found it...
http://androidforums.com/incredible...05-warning-do-not-share-nandroid-backups.html
adrynalyne said:
Warning. Do Not Share Nandroid Backups
--------------------------------------------------------------------------------
Even if your apps aren't there, and no personal information has been entered on a fresh wipe.
If someone asks for a stock Nandroid backup, kindly tell them to get lost
contagous and I learned the hard way. I sent him a completely tweaked and clean nandroid, with none of my personal info or anything like that. He has been using it and it works great.
Until AppBrain fast web installer is used. See, it IDs your device by the Android_ID, which is unique to every phone, or is supposed to be.
Nandroid backups will record this device ID, and clone it onto another device. Well, when contagous installs an app using the web installer, I get it. Without a prompt or nothing.
While I can do the same thing, and it was fun sending him pron apps and sexy men wallpapers, it has a real potential for a security nitemare. I trust contagous, but let this serve as a warning to everyone. Its also not so simple as installing another ROM and factory reset. So far as I can tell, as long as you stay on the same build OS, you will keep the same ID. The only thing that changed my ID to something else was going back to 2.1.
So friends, don't let friends share nandroids. If you do, play it smart, and delete all but the system and boot images and recalculate the md5.
Click to expand...
Click to collapse
and
adrynalyne said:
LOL,
Yeah here's the thing. Device ID and Android_ID are not the same.
YES, a nandroid WILL overwrite the Android_ID of devices and can cause security issues. Its like cloning a mac address.
Point in case, appbrain fast web installer uses it to identify devices. I know this, because I tested it, and CONFIRMED it with the devs.
Najaboy is correct.
I and another forum member were sending each other apps via our own accounts on app brain.
Any other app that uses the same method of identifying devices in the cloud also pose this same problem.
Moral of the story:
Be smart and don't use the same Nandroid on another phone unless you know how to erase cloned Android_IDs.
Click to expand...
Click to collapse

Hmm. That's good information to know!
Sent from CM Nightly 11-20 using Tapatalk.

What about a Titaniumm Backup? Any issues there going AMOLED to SLCD?

wpbear said:
What about a Titaniumm Backup? Any issues there going AMOLED to SLCD?
Click to expand...
Click to collapse
nope. those are simple just apps being restored, so no issues there.

Titanium backuo will restore some personal settings as well, correct?

wpbear said:
Titanium backuo will restore some personal settings as well, correct?
Click to expand...
Click to collapse
correct.

Restoring backup after TPT

Hello all. I had a go of an ICS rom and had to re-partition to do so - used TPT helper. Problem I have now is I can't restore my CM7 rom from nandroid backup, which I suspect is due to the partitioning thing. I didn't make a note of the original partition sizes though, so I'm wondering how I'm going to go back. Anyone got any suggestions?
Cheers,
Alex

4lex said:
Hello all. I had a go of an ICS rom and had to re-partition to do so - used TPT helper. Problem I have now is I can't restore my CM7 rom from nandroid backup, which I suspect is due to the partitioning thing. I didn't make a note of the original partition sizes though, so I'm wondering how I'm going to go back. Anyone got any suggestions?
Cheers,
Alex
Click to expand...
Click to collapse
What kind of Blade do u have?

Why Has Titanium Become Failboat

I just don't get this. I have used Titanium Pro for years, but on the newest phones it seems to be a bit of a CLUSTERF* and it is getting really damned annoying.
Oh sure, I try the inactive/interactive settings change, but the same crap. Never had to mess with it in the past.
Has Titanium lost their mojo as the premium android backup solution? Is there something new that actually works reliably on Current phones? ARGH
My experiences are with both SuperSU and Superuser.

Barsky said:
I just don't get this. I have used Titanium Pro for years, but on the newest phones it seems to be a bit of a CLUSTERF* and it is getting really damned annoying.
Oh sure, I try the inactive/interactive settings change, but the same crap. Never had to mess with it in the past.
Has Titanium lost their mojo as the premium android backup solution? Is there something new that actually works reliably on Current phones? ARGH
Click to expand...
Click to collapse
Could you be more specific? It works great for me.
Oh, and this is not development...
Support your Devs......

It is still the best Android backup solution
Sent from my LG-D800 using XDA Premium 4 mobile app

I still use it with no problems.

I've noticed no changes, works fantastic for me. Been using pro before it was on the market.

Same here, using it fine on stock rom with cwm recovery and root.

iOSh8er said:
Could you be more specific? It works great for me.
Oh, and this is not development...
Support your Devs......
Click to expand...
Click to collapse
The well documented freezing on restores. I honestly love this app. Don't get me wrong. I was venting a bit. But the first time I've encountered this was on my htc one and now this G2. Not sure why. Since I only got it today, I decided to Factory Restore it and will go from there.
If I offended anyone, please don't be. It was not my intention.

Barsky said:
The well documented freezing on restores. I honestly love this app. Don't get me wrong. I was venting a bit. But the first time I've encountered this was on my htc one and now this G2. Not sure why. Since I only got it today, I decided to Factory Restore it and will go from there.
If I offended anyone, please don't be. It was not my intention.
Click to expand...
Click to collapse
The only time I have had this issue was when I was restoring a 4.2+ feature on a 4.1 ROM (ie Lockscreen widget on Note 2).
I even back everything up from each phone to Dropbox and restore apps with data on a different device. I expected issues with this but was pleasantly surprised.
And I highly doubt you offended anyone I was just curious what issues you were having.
Hope you get it sorted out!
Support your Devs......

Never had a problem with Titanium
Sent from my VZW LG G2

iOSh8er said:
The only time I have had this issue was when I was restoring a 4.2+ feature on a 4.1 ROM (ie Lockscreen widget on Note 2).
I even back everything up from each phone to Dropbox and restore apps with data on a different device. I expected issues with this but was pleasantly surprised.
And I highly doubt you offended anyone I was just curious what issues you were having.
Hope you get it sorted out!
Support your Devs......
Click to expand...
Click to collapse
You sir, might just be a genius This backup was done on the same version of titanium, but it was from a backup done on my previous htc one running a 4.3 rom. that has to be it.
*Kicks self in butt, repeatidly*. Thank you!!

Never had the freeze on restore issue. But it would be annoying if it were a regular problem. I think Joel has done a good job though keeping up with all the changes that Android throws out there. It's a tough row to sow to have an app of that magnitude working all the time on every make, model and OS version.

Worked flawlessly migrating from a DNA to the G2. It's you.

heh. I can't even get it into download mode. I think the problem is I used a "install twrp without root" from the forums here. it seemed to fail. Looking closer it appears to change the kernel stupid me didn't notice first. Looking to restore phone to factory default. Downloading now
Ended up having to have Titanium create an update.zip of my apps. restored via recovery. Odd. Trying Cleanrom today and will see how that goes.

Barsky said:
heh. I can't even get it into download mode. I think the problem is I used a "install twrp without root" from the forums here. it seemed to fail. Looking closer it appears to change the kernel stupid me didn't notice first. Looking to restore phone to factory default. Downloading now
Ended up having to have Titanium create an update.zip of my apps. restored via recovery. Odd. Trying Cleanrom today and will see how that goes.
Click to expand...
Click to collapse
OK, so the problem did seem to due to the backup being created from a 4.3 rom on htc one. After installing the apps using the created update.zip, I then deleted all titanium backups and did a new one from the G2. I then did a factory reset, reinstalled Titanium and then restored without issue. Happy Happy Joy Joy.
Thanks guys.

are you restoring data? restoring data from one version of android to another, or one phone to another especially a diff version, will always give you a problem.
i don't even use titanium to restore apps when i get a new phone..i'd rather my new phone start off clean and build it's own data to backup.

jayochs said:
are you restoring data? restoring data from one version of android to another, or one phone to another especially a diff version, will always give you a problem.
i don't even use titanium to restore apps when i get a new phone..i'd rather my new phone start off clean and build it's own data to backup.
Click to expand...
Click to collapse
only downloaded app data, never system. Also, solved.

Go back to Stock ROM from 1337 ROM

Hi,
A couple of months back I had installed 1337 ROM on my Nook ST. However, I would now like to go back to stock ROM. Is using Nook Manger and selecting Restore factory.zip option the correct way? If not what steps should I follow?
Thanks

Using Nook Manager is the way to go. I know that there is a factory reset option available, though I can't remember that it is called. (I don' have either of my NSTs with me at the moment, so I can't check.)

David0226 said:
Using Nook Manager is the way to go. I know that there is a factory reset option available, though I can't remember that it is called. (I don' have either of my NSTs with me at the moment, so I can't check.)
Click to expand...
Click to collapse
Thanks for the prompt reply, however one thing that is bothering me is that I don't have a factory.zip file. Is it required or is it already present in an internal partition?

bit_junky said:
Thanks for the prompt reply, however one thing that is bothering me is that I don't have a factory.zip file. Is it required or is it already present in an internal partition?
Click to expand...
Click to collapse
I believe it is in the internal partition, but I am not sure if the 1337 ROM changes that or not.

David0226 said:
...
I know that there is a factory reset option available, though I can't remember that it is called.
Click to expand...
Click to collapse
Assuming that both the stock recovery and factory ROM image in the backup partition are intact, one should be able to trigger a reset to factory-fresh condition by using the "8 failed boots" method -- power on the Nook and as soon as the screen flash on press power button to turn it off, do this 8 times.

bit_junky said:
Hi,
A couple of months back I had installed 1337 ROM on my Nook ST. However, I would now like to go back to stock ROM. Is using Nook Manger and selecting Restore factory.zip option the correct way? If not what steps should I follow?
Thanks
Click to expand...
Click to collapse
Have you had any success so far? I just tried 1337 but it didn't work well on my device and restored to the original firmware. However I made a full backup image of my Nook (including boot partition and stock recovery) before installing Clockworkmod.
If you have not made this backup and installed Clockworkmod to your internal memory, it may be a bit more difficult for you to restore to the original firmware.