I recently traded out my SCLD for an AMOLED model. Should I be able to restore my nandroid backup without any consequences?
Well, I tired it, and for what's it worth, it definitely worked!
Hm I had heard you couldn't use the same nandroid on different phones due to each phone having an individual phone ID.
Sent from my ADR6300 using XDA App
k_nivesout said:
Hm I had heard you couldn't use the same nandroid on different phones due to each phone having an individual phone ID.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
In terms of securing your personal data, it's ill-advised. By restoring his nandroid to a different phone, the OP has cloned the android_ID from the original device to the new one. If his old phone goes into the CLNR cycle or if he traded it to another customer, both phones are potentially going to be doing some wonky stuff. Any apps that use the android_ID as an identifier are going to push/pull data to/from both phones.
So what would you suggest, since I'm planning on selling the 1st phone? Would a full wipe and flashing a fresh ROM do the trick and prevent this "wonky stuff" from happening?
You should be able to change your android_ID by RUU'ing a different build of the OS... for example, go back to 2.1.
While I can do the same thing, and it was fun sending him porn 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.
Click to expand...
Click to collapse
http://androidforums.com/incredible...05-warning-do-not-share-nandroid-backups.html
Related
Getting a replacement Dinc tomorrow, makeing a backup of my current setup. Question will that nandroid backup work on a replacement phone. Obviously s-off and rooted?
Sent from my ADR6300 using XDA App
IIRC, you can't do a Nandroid backup to a different phone, since there's some software/hardware ID's that could possibly conflict. Not 100% on this, but I'm pretty sure this is what I've seen.
Device ID in the backup image won't match the new one, hence odd behavior, if it'll even boot.
Sent from my ADR6300 using XDA Premium App
Assuming the same hardware version, it will work but is ill-advised. You'll be cloning the android_ID from the old device onto the new.
If your old phone isgetting sent back in, the odds are that it's going to be repaired and sent to someone else as a warranty replacement. As such, there's a risk that both phones will share the same android_ID. What that means to you is that any app that uses the android_ID as an identifier is going to push/pull data to and from both handsets.
At the very least, this is an unwelcome annoyance. Depending on what you and the other person have installed, it can also be a significant compromise of your data.
Best practice would be to simply backup your apps with Titanium and then restore them onto the new phone.
I am about to go to verizon and get my incredible replaced under a manufacturing defect. I just read on HTC's site that their warranty covers for 12 months... quiet generous.
the power button is stuck "on" all the time.. for example if I battery pull and put it back in it starts powering up without ever pushing the power button. I heard this was a common issue with the older incredibles.
GOOD thing I was rooted cause for now... optical track wake is a lifer saver. If it wasn't for that feature I would have to battery pull or wait for a phone call every time I wanted to use my phone.
Anyways... is it a good idea to use my backup ROMs on my old incredible on my new incredible? Or should I just play it safe and start from scratch?
najaboy said:
If there's a chance that your okld phone is going to be refurbed and sent out as a CLNR, then I'd advise against it. Along with your apps and data, you'll also be cloning the android_ID from the old device onto the new one. Best practice would be to simply restore apps using Titanium.
Click to expand...
Click to collapse
najaboy said:
Apps and services that utilize the android_ID as an identifier are going to push/pull data from any and all handsets bearing that identifier... something to bear in mind when restoring nandroids across devices.
Click to expand...
Click to collapse
From "Nand backup on different phone?"
No is the short answer, device id is different.
Sent from my ADR6300 using XDA Premium App
sweet. thanks for the quick reply.
I did this back in my D1 days when the audio went out and I swapped it for a replacement, was it a good idea? probly not. Did I care? nope.
I just lost my phone and unfortunately need to get a $100 replacement from Asurion two weeks (approx, whenever they release it.) before I upgrade to the Galaxy Nexus...Can I use a Nandroid backup of my old phone on my new replacement incredible when I get it? Or do the hardware differences matter and will cause it to be unreliable and crash?
Unfortunately, the differences between the two and other more granular stuff like device id stored in the backup would cause many many issues, were it even bootable.
Sent from my ADR6300 using XDA Premium App
EvanVanVan said:
I just lost my phone and unfortunately need to get a $100 replacement from Asurion two weeks (approx, whenever they release it.) before I upgrade to the Galaxy Nexus...Can I use a Nandroid backup of my old phone on my new replacement incredible when I get it? Or do the hardware differences matter and will cause it to be unreliable and crash?
Click to expand...
Click to collapse
as long as the phones are the same ie. if you used an AMOLED to AMOLED or SLCD to SLCD device it should work. the worst it is going to do is not boot. i would recommend having a rom on your phone sd card and try it. If anything happens you can always RUU with the .exe to get it back to working order.
Thanks guys, yeah I guess its worth a shot, I'm not sure what the new screen is or even what my old screen was...but as you said the worst that'll happen is it wont boot. I really only need it till I can get the Galaxy Nexus, even if it is a little unreliable for the time being..
EvanVanVan said:
Thanks guys, yeah I guess its worth a shot, I'm not sure what the new screen is or even what my old screen was...but as you said the worst that'll happen is it wont boot. I really only need it till I can get the Galaxy Nexus, even if it is a little unreliable for the time being..
Click to expand...
Click to collapse
New screen will be slcd. Its really hard to get an amoled. When did you buy the other incredible?
Sent from my sexy assistant. (AMOLED HTC Incredible)
1st gen preorder...the phone almost made it..
You more than likely had a AMOLED then.
EvanVanVan said:
1st gen preorder...the phone almost made it..
Click to expand...
Click to collapse
yeah then the nandroid might not work unless you get another AMOLED because thats what the OG incredible was. if you try to restore it your touch screen will not work.
i mean if you really want to try it better say a little prayer first.
yeah, had a feeling that was the answer thanks...oh well at least all the important stuff was on the sd card and the contacts were on google
smtom said:
Unfortunately, the differences between the two and other more granular stuff like device id stored in the backup would cause many many issues, were it even bootable.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
I think so ha ha..
I don't get why some people have issues with their that I don't have and I have problems that other people have when we are using the same device (are we?) Galaxy W. What I know is that, the difference between all our phones is the baseband, right? Does that make a difference to anything?
Sent from my GT-I8150
imadiu said:
I don't get why some people have issues with their that I don't have and I have problems that other people have when we are using the same device (are we?) Galaxy W. What I know is that, the difference between all our phones is the baseband, right? Does that make a difference to anything?
Sent from my GT-I8150
Click to expand...
Click to collapse
not only that, but their usage pattern also contributes a lot
Sent from my GT-I8150 using xda premium
imadiu said:
I don't get why some people have issues with their that I don't have and I have problems that other people have when we are using the same device (are we?) Galaxy W. What I know is that, the difference between all our phones is the baseband, right? Does that make a difference to anything?
Sent from my GT-I8150
Click to expand...
Click to collapse
It depends on our customization and so forth like someone using their phone mainly for gaming would lose their battery quicker than someone who just has theirs for calling people and so forth. It depends on the user so of course people would have different problems even though the phone itself is the same.
imadiu said:
I don't get why some people have issues with their that I don't have and I have problems that other people have when we are using the same device (are we?) Galaxy W. What I know is that, the difference between all our phones is the baseband, right? Does that make a difference to anything?
Sent from my GT-I8150
Click to expand...
Click to collapse
As JA*G above stated, people customise their phones differently, which can cause significant differences when flashing, etc.
Also, a lot of issues arise from restoring backups from programs such as Titanium Backup, or Nandroid (CWM). Restoring backups, especially between different versions of Android, can lead to a lot of random issues, and stability problems.
Personally, I am in your shoes. I always full-wipe, and never ever back anything up. I'd rather manually download and re-install all my Apps, and use a memory card to keep my photos and music safe, than run the risk of not getting a 'clean flash'.
That said, there are countless users who have never had an issue restoring backups. It's all in how diligent you are at following instructions, your patience, and your ability to understand rather than just ask blind questions
juzz86 said:
That said, there are countless users who have never had an issue restoring backups. It's all in how diligent you are at following instructions, your patience, and your ability to understand rather than just ask blind questions
Click to expand...
Click to collapse
But not everyone gets the same result even after following the instructions given by the devs for each custom rom. Really left me bewildered and i can't help them when they have a problem that i don't have... Helpless
Thats just the way it is. You cannot please every one as they say. Its that simple.
Sent from my GT-I8150 using xda premium
Karmalot said:
Thats just the way it is. You cannot please every one as they say. Its that simple.
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
This is true. You've also gotta remember that everyone uses a different brand cable to connect, they use a different USB controller, different drivers, different OSes etc.
You may just be onto a great setup for flashing and stability. It's taken me a long time, a few bricks and a lot of reading, but I'm finally there too :good:
Sometimes, even the subtle nuances of the method you use can make all the difference, like when you plug the cable, whether you wait until everything is installed properly, whether you restart the PC after every install etc. Diligence plays a big part in getting it right
Not every phone is built equal, either. Especially Samsung phones. Two alongside each other rarely have the same fit-and-finish. I definitely think their quality control could do with a little bit of a kick in the pants :good:
juzz86 said:
This is true. You've also gotta remember that everyone uses a different brand cable to connect, they use a different USB controller, different drivers, different OSes etc.
You may just be onto a great setup for flashing and stability. It's taken me a long time, a few bricks and a lot of reading, but I'm finally there too :good:
Sometimes, even the subtle nuances of the method you use can make all the difference, like when you plug the cable, whether you wait until everything is installed properly, whether you restart the PC after every install etc. Diligence plays a big part in getting it right
Not every phone is built equal, either. Especially Samsung phones. Two alongside each other rarely have the same fit-and-finish. I definitely think their quality control could do with a little bit of a kick in the pants :good:
Click to expand...
Click to collapse
And for some reason people still don't get. They don't realize we cannot do much for them, and i quote "it all starts with you". Searching, reading,understanding, if you made mistakes, search, read and try to understand more. I myself experienced bricks, i ask for some help, but still its myself who fixed my wonder.
Sent from my GT-I8150 using xda premium
juzz86 said:
snip......
Also, a lot of issues arise from restoring backups from programs such as Titanium Backup, or Nandroid (CWM). Restoring backups, especially between different versions of Android, can lead to a lot of random issues, and stability problems
Click to expand...
Click to collapse
Can I just rake slight issue with you regarding including Android backup above....
Of course, as we know, Nandroud is basically a snapshot of your Device partitions at a given point in time.
It really is useful to get back to how your system was at that time, particularly if you gave screwed up and need to recover...you don't need to wioe or anything, as the Nabdroid restore formats the partitions before restoring data...so you can get back to that point in time with the ROM you had.....very different from App backups with TB, where you are wanting to restore your Apps to a new ROM or version!!!
Sent either from my Sammy GT-i8150 or my Momo11 Bird Tablet!!
irishpancake said:
Can I just rake slight issue with you regarding including Android backup above....
Of course, as we know, Nandroud is basically a snapshot of your Device partitions at a given point in time.
It really is useful to get back to how your system was at that time, particularly if you gave screwed up and need to recover...you don't need to wioe or anything, as the Nabdroid restore formats the partitions before restoring data...so you can get back to that point in time with the ROM you had.....very different from App backups with TB, where you are wanting to restore your Apps to a new ROM or version!!!
Sent either from my Sammy GT-i8150 or my Momo11 Bird Tablet!!
Click to expand...
Click to collapse
Absolutely my friend, I don't disagree in the slightest. It is a very handy tool that can save a lot of time and effort, as long as you adhere to a few rules
For me, though, the most important thing about a new flash is that I get the absolute minimum 'junk' and the absolute best experience and performance from it. In the past I used to backup almost daily, and could restore at any point in time. Nandroid is an excellent tool for those who keep the same ROM etc. installed forever, as that's how it works best.
When you flash a new kernel, new Android version, new recovery etc, you run the risk (it certainly doesn't always happen) of it restoring things to the wrong place, restoring launchers over launchers, frameworks over frameworks etc. All of this can lead to some of the random instabilities that people experience, plus the force closes etc.
Your mileage may vary, of course, and everyone is different. I don't dispute your point at all - it's just not for me
There is a lot of fear going around with people worried about bootlooping. I think it would be good to get some rough idea of what the chances are for this to occur through at least one means. So I want to find out just how many people this is effecting and how many (here) it is not.
I've rooted and flashed darthstalker on 3 different note 3's also upgraded them to v2 and no issues here. I read everything I needed on twrp, flashing, and not restoring.
All 3 devices are doing exceptionally well.
Sent from my SM-N900T using xda app-developers app
elracing21 said:
I've rooted and flashed darthstalker on 3 different note 3's also upgraded them to v2 and no issues here. I read everything I needed on twrp, flashing, and not restoring.
All 3 devices are doing exceptionally well.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Why not vote on the poll? Also have you restored?
I've flashed numerous times on my Note and never had any boot looping issues. Just followed the steps and all is well.
Sent from my SM-N900T now Free
Restoring nandroid works for me
I did a nandroid backup from my darthstalker v2 rom. Then after that I was using the phone one day and my signal went out on the phone and never come back on. I put the phone back to stock and took it to tmobile ( which tmobile never checked the bootloader to see if the knox counter was tripped ). The realized the phone was defective and gave me a brand new one. I got home and rooted the device. After that I backed up the current rom and moved the nandroid back up of darthstalker v2 to the new folder location. I installed darthstalker v2, I then did a factory reset, wiped system, cache, and dalvik cache. After that I restored the nandroid back up only restoring the system and data. The rom loaded right up and I have no problems whatsoever. All this was on the latest twrp I installed from the goomanager app. Seems that restoring nandroids is working just fine in my case.
I wonder if anyone with the boot loop restored only system and data...
I'm thinking that restoring more than those two options may play a role in this.
sgh-TWEAKED-889©
Warrior1975 said:
I'm thinking that restoring more than those two options may play a role in this.
sgh-TWEAKED-889©
Click to expand...
Click to collapse
maybe because the other people getting boot loops from doing TB restores and that has to do with data right?, only thing i believe they can recover but we couldn't. I got my new note after giving up yesterday and i wont be the one to try that theory lol.
stress1ner said:
maybe because the other people getting boot loops from doing TB restores and that has to do with data right?, only thing i believe they can recover but we couldn't. I got my new note after giving up yesterday and i wont be the one to try that theory lol.
Click to expand...
Click to collapse
Haha same here...
Sent from my SPH-L900 using Tapatalk 2
I've flashed a stock deodexed rom and both versions of Darthstalker. Restored data only w/TWRP every time w/no bootloops whatsoever. Still probably gonna play it safe & just do TB restores until they figure out exactly what's causing all this though.
HughesNet said:
There is a lot of fear going around with people worried about bootlooping. I think it would be good to get some rough idea of what the chances are for this to occur through at least one means. So I want to find out just how many people this is effecting and how many (here) it is not.
Click to expand...
Click to collapse
Knowledge is power, so know this..
DO NOT RESTORE A BACKUP, PERIOD, END OF STORY.
I'm going to attribute this issue to the Knox security Samsung decided to include on the Note 3. I am of the opinion that whether it be the Knox container, partition, security issue, it could have been avoided by Samsung offering Knox related security to people who want it, not just including it on every device sold to the masses, most of which could care less about toting around top secret documents on their devices used mostly for social entertainment.
Just a poor decision in my opinion, which they're going to realize shortly, or already have. Reason being the pending release of a "Developer's" version of the Note 3..
Sent from my SM-N900T using XDA Premium 4 mobile app
Steve Lazarus said:
Knowledge is power, so know this..
DO NOT RESTORE A BACKUP, PERIOD, END OF STORY.
I'm going to attribute this issue to the Knox security Samsung decided to include on the Note 3. I am of the opinion that whether it be the Knox container, partition, security issue, it could have been avoided by Samsung offering Knox related security to people who want it, not just including it on every device sold to the masses, most of which could care less about toting around top secret documents on their devices used mostly for social entertainment.
Just a poor decision in my opinion, which they're going to realize shortly, or already have. Reason being the pending release of a "Developer's" version of the Note 3..
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I can promise you one thing Steve I will not considering I was the first one to have a boot looping note 3. I don't want to see that happen again.
Sent from my SM-N900T using Tapatalk 4
Steve Lazarus said:
Knowledge is power, so know this..
DO NOT RESTORE A BACKUP, PERIOD, END OF STORY.
I'm going to attribute this issue to the Knox security Samsung decided to include on the Note 3. I am of the opinion that whether it be the Knox container, partition, security issue, it could have been avoided by Samsung offering Knox related security to people who want it, not just including it on every device sold to the masses, most of which could care less about toting around top secret documents on their devices used mostly for social entertainment.
Just a poor decision in my opinion, which they're going to realize shortly, or already have. Reason being the pending release of a "Developer's" version of the Note 3..
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Stuff is pretty easy to remove either way. Typical carrier stunt. Nothing new.
This only proves the point that if you are incapable of diagnosing issues on your own, you shouldn't be messing with core related system apps, messing around with beta-ish recoveries, etc. Root and leave it alone if you don't know what you are doing.
And titanium backup is terrible. Most users I see that have problems with boot looping, force closes, etc... Are causing the issue. Hard to believe the device randomly decided to start having issues on its own.
d474corruption said:
This only proves the point that if you are incapable of diagnosing issues on your own, you shouldn't be messing with core related system apps, messing around with beta-ish recoveries, etc. Root and leave it alone if you don't know what you are doing.
Click to expand...
Click to collapse
If that was the case, xda would be a very quiet place.
Sent from my SM-N900T using Tapatalk 4
d474corruption said:
Stuff is pretty easy to remove either way. Typical carrier stunt. Nothing new.
This only proves the point that if you are incapable of diagnosing issues on your own, you shouldn't be messing with core related system apps, messing around with beta-ish recoveries, etc. Root and leave it alone if you don't know what you are doing.
And titanium backup is terrible. Most users I see that have problems with boot looping, force closes, etc... Are causing the issue. Hard to believe the device randomly decided to start having issues on its own.
Click to expand...
Click to collapse
I agree and disagree.. If we were to live by your motto, Google and Android development wouldn't be where they are now. The end user has doors open in front of them once they root for the first time, or flash their first custom ROM, and from there the imagination starts working it's magic.
Some first time rooters / modders go on to become great application developers due to the unfounded landscape they discover once they delve into writing code.. It's not rocket science to root, flash, tweak, mod. However, it does get tricky once a manufacturer makes a device with features that create problems doing the most menial of things. Knox was put on a device sold to the masses, which as stated, most of which could care less about toting around top secret documents, as compared to checking Facebook, email, YouTube, their favorite sites and forums.
The end user needs to do their research before just tossing themselves into the fire . But as we've seen thus far regarding this issue, even developers are still trying to figure it out. Most dev's encourage the end user to actually understand what the cause and effect of what it is they're doing. Also how they (the end user) can do the same thing with a different outcome using an alternative route, code etc..
You start alienating people from this process, we all suffer.
Sent from my SM-N900T using XDA Premium 4 mobile app
kabuk1 said:
I've flashed a stock deodexed rom and both versions of Darthstalker. Restored data only w/TWRP every time w/no bootloops whatsoever. Still probably gonna play it safe & just do TB restores until they figure out exactly what's causing all this though.
Click to expand...
Click to collapse
They just did. Apparently TWRP doesn't restore the EFS partition properly, causing a bootloop. If you don't restore the EFS partition, you'll be fine (which you would never have to do anyway unless you somehow blew up your IMEI and modem configuration).