I got a replacement Mytouch from T-Mobile yesterday and was just about to flash a new rom on it and begin restoring apps, but I was wondering if a nandroid restore would work between my old phone and the new one. I've seen people posting stock backups before, but I'm not sure if there is anything that comes up while the phone is used that would be specific to that one device. Is there anything in a backup that would tie it to just that one phone?
Yeah, i need to know this too. I assume you can though.
kitsunisan said:
I got a replacement Mytouch from T-Mobile yesterday and was just about to flash a new rom on it and begin restoring apps, but I was wondering if a nandroid restore would work between my old phone and the new one. I've seen people posting stock backups before, but I'm not sure if there is anything that comes up while the phone is used that would be specific to that one device. Is there anything in a backup that would tie it to just that one phone?
Click to expand...
Click to collapse
I've heard of people doing it but never tried myself. Try it and report back.
The worst that can happen is a boot loop. Then just wipe, reflash and go on with your original plan.
I did it Friday, since no one here seemed to have an answer. Seems to work just fine, I haven't had any major issues yet.
kitsunisan said:
I did it Friday, since no one here seemed to have an answer. Seems to work just fine, I haven't had any major issues yet.
Click to expand...
Click to collapse
Awesome, thanks!
I've done it once in a G1 when my girlfriend switched phones. Just use fastboot to flash the backed up nandroid files.
yes from my experience with the nexus one you should be fine. No issues restoring nandroid to another phone.
Related
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.
OK, congratulate me!! Thanks. I did it on the first try, no issue or hiccups what-so-ever.
Now for the info. I'm not sure that anyone will be interested, but I'm guessing other people in my position at least might be.
I'm very experienced with computers, but not working directly with rooting/unlocking devices. But I would say anyone who reads up a bit and can follow directions properly could pull it off pretty easily.
So I run 2.2.2, and I used superoneclick 1.6.3.
After opening superoneclick, I switched it from psneuter to rageagainsthecage. I had no idea if I was supposed to do this, but I read all about rageagainstthecage, and never heard of psneuter.
I had my phone connected to my PC, and I left my SD in the phone, but I unmounted it in settings. I have used ADB before, so I knew the drivers were installed and working, and I hit the button root.
After reading this site, http://forum.xda-developers.com/showthread.php?t=803682, I started with debugging off, and turned it on as it said. I then turned it off, but didn't get a chance to turn it back on and off and on, so I just turned it back on (debugging) when it got to "Waiting for device" for the second time.
That was it! It asked to test and see if root was in fact accomplished, and it was. I then installed setCPU (which is basically the only reason I wanted to do this) and as far as I can tell it seems to be working fine.
I have been reading a lot about this for the past few days, but the actual procedure only took a couple of minutes. Keeping in mind, of course, that I already had ADB and drivers working.
Nothing was wiped off my phone, which surprisingly was hard to confirm on the web. I did read somewhere that only unlocking wipes data, but still, you never know.
I hope this helps anyone else who is new and unsure of the process, and I'd be happy to answer any other specific questions based on what I have learned of the last week or so. I know that people hesitate to ask questions in case they have already been asked lots of times, but are buried and hard to find (because that's the position I was in ).
Thanks for posting your "rooting" experience. I'm sure there are people that will find it helpful.
I think when I did mine, it was something along the lines of:
fastboot-oem-unlock
fastboot flash recovery <whatever>
reboot into recovery and flash rom
Other than the ability to install custom ROM's I've yet to see a huge deal in rooting my phone. Anyone care to tell me what I can do with a rooted N1 that is a must have? So far I tried to change some fonts, which didn't work, and discovered that I have to install a custom ROM to change the color of the notification bar, and I can't make the default Google music and news widgets slightly transparent. So educate me, what's the huge deal with rooting, aside from a custom ROM?
Set cpu of course like being said. I remember the first time I rooted my phone was universal androot it was a breeze. Then I lost root and use super one click to gain out back. Root really easy as well
Sent from my Nexus One using XDA App
- Backup application, like MyBackup, can backup your app data(including game save...) if your device is rooted.
Hi N1 owners.
I also just root my N1 with superoneclick 1.6.3
After that I flashed CM 6.1.1 and yesterday I tried CM7. Everything has worked fine for me so far, but I have some questions, I hope someone can answer.
1/Can I just flash random roms on top of each other, like i did from cm6 - cm7?
2/ Can I always restore backups, nomatter what rom I come from or to?
3/ when/if official GB come out, can I flash a stock rom and get the OTA update right away?
Sorry, if I ask silly questions ..
Built in trackball colors, call blocker, hide frequently called list in the favorites tab, remove unnecessary apps, tmobile wifi calling, notification bar power toggles, trackball wake and unlock, quiet hours, themes, etc., etc., etc. Just off the top of my head. Oh, and Gingerbread!!!
Sent from my Nexus One using Tapatalk
Some apps want to bypass the home screen "5 second rule" like widget locker, you need root. I setup a widget to reboot (nice!).
brettbellaire said:
...I did read somewhere that only unlocking wipes data, but still, you never know.
Click to expand...
Click to collapse
Unlocking the Bootloader wipes data, rooting does not. This is probably what you read.
offenberg said:
Hi N1 owners.
I also just root my N1 with superoneclick 1.6.3
After that I flashed CM 6.1.1 and yesterday I tried CM7. Everything has worked fine for me so far, but I have some questions, I hope someone can answer.
1/Can I just flash random roms on top of each other, like i did from cm6 - cm7? Yes you can. Often if the ROM is the next version in a series, you can flash without wiping data or cache, but some ROMs require you to do this first.
2/ Can I always restore backups, nomatter what rom I come from or to? A Nandroid backup can be reinstalled from any ROM, or even just from Recovery if there is no ROM.
3/ when/if official GB come out, can I flash a stock rom and get the OTA update right away? Yes. Either restore your stock ROM Nandroid backup or a passimg.zip.
Sorry, if I ask silly questions ..
Click to expand...
Click to collapse
offenberg said:
Hi N1 owners.
I also just root my N1 with superoneclick 1.6.3
After that I flashed CM 6.1.1 and yesterday I tried CM7. Everything has worked fine for me so far, but I have some questions, I hope someone can answer.
1/Can I just flash random roms on top of each other, like i did from cm6 - cm7?
2/ Can I always restore backups, nomatter what rom I come from or to?
3/ when/if official GB come out, can I flash a stock rom and get the OTA update right away?
Sorry, if I ask silly questions ..
Click to expand...
Click to collapse
1. As a rule, if you are going from 1 ROM to another totally different ROM, it's always a good idea to wipe. It only takes a few seconds to sign back in to everything. You can bypass immediate sign in and activate wifi if you need it.
2. Nandroids can be reinstalled anytime. However, a nandroid does not contain your HBOOT and Radio. So if you updated those to use a specific ROM, they would stay in place with the nandroid restore.
3. When GB does finally make it out to our specific device, there is no way you would get an OTA before the ROM devs here had you up and running.
***Also note, the 1-click root tools may or may not work right away with the OTA 2.3. So to anyone that rooted using those tools and unrooted to hurry up and get an OTA, you may be stuck on stock until it gets fixed.
Know-Fear said:
1. As a rule, if you are going from 1 ROM to another totally different ROM, it's always a good idea to wipe. It only takes a few seconds to sign back in to everything. You can bypass immediate sign in and activate wifi if you need it.
Click to expand...
Click to collapse
I agree, do a full wipe if it's a new ROM. Titanium Backup is a great way to get all of your apps and data back after installing the new ROM.
bigmout said:
I agree, do a full wipe if it's a new ROM. Titanium Backup is a great way to get all of your apps and data back after installing the new ROM.
Click to expand...
Click to collapse
So what do you lose (if anything) when flashing a new ROM if you backup and do things the right way?
Another question would be if you just flash a new kernal do you lose any/all data?
brettbellaire said:
So what do you lose (if anything) when flashing a new ROM if you backup and do things the right way?
The only thing you'd lose is the old rom
Another question would be if you just flash a new kernal do you lose any/all data?
Click to expand...
Click to collapse
Nope
Sent from my Nexus One using XDA App
kmiloco49 said:
Nope
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Interesting... Thanks!
@ brettbellaire
I've rooted before, and lost root when ota's came. I've rooted again using superoneclick, and am contemplating cm7. But I feel very cautious about flashing a different rom, I'd cry if I bricked my phone. However, I'm probably going to do it during the next week (unless gingerbread ota arrives).
Andy
Sent from my Nexus One using XDA App
Hmmm, I have been anxious for GB too.... but I'm not sure it's worth it. I don't think it's such a big update. I don't think there's too much of a danger of brinking these days.
I have been contemplating doing what I have to to overclock, see what kind of a difference that makes...
bigmout said:
I agree, do a full wipe if it's a new ROM. Titanium Backup is a great way to get all of your apps and data back after installing the new ROM.
Click to expand...
Click to collapse
I am a newbie to root. Can Titanium Backup restore the paid apps? because some apps require online verification with Google at the first time of use.
Also, Z4root does not work on my N1. I want to use superoneclick but where can I find the driver for my win7? thanks
unroot
is it possible to go back and unroot the phone? i.e. hide the padlock during phone startup ..I am using N1 ForYo 2.2.2..Thanks
zmalach said:
is it possible to go back and unroot the phone? i.e. hide the padlock during phone startup ..I am using N1 ForYo 2.2.2..Thanks
Click to expand...
Click to collapse
If you see the padlock, you've got an unlocked boot-loader. This can't be re-locked.
Sent from my Nexus One using XDA App
I have a 32GB N7 that I share with my girlfriend. I quickly learned that if I flash a new ROM, that whole other user's info is gone.
After trying to restore apps and info using both Titanium and ROM Toolbox, I couldn't get it to function like it was before.
I tried to restore to a backup I made prior to doing this and it won't get past the boot screen. I can safely assume that whole other user account is gone. The question is, how can I bring that from one ROM to another? Or how can I restore back to a previous ROM that had it setup?
engagedtosmile said:
I have a 32GB N7 that I share with my girlfriend. I quickly learned that if I flash a new ROM, that whole other user's info is gone.
After trying to restore apps and info using both Titanium and ROM Toolbox, I couldn't get it to function like it was before.
I tried to restore to a backup I made prior to doing this and it won't get past the boot screen. I can safely assume that whole other user account is gone. The question is, how can I bring that from one ROM to another? Or how can I restore back to a previous ROM that had it setup?
Click to expand...
Click to collapse
I could be wrong about this as I am very new to serious mucking around in Android but...
Were ROMs you were using previously based on 4.1.x or older? I know that it is only a very recent version of Android that has proper multi-user support (4.2.2 has it for instance.. I'm not sure about 4.2.1 etc..) and thus now places a "0" folder in which the main user's data is saved, and then there will be "10', "11" etc.. for subsequent users. I'm not sure if your data is gone or not depending on your exact situation, but there are issues that can come from trying to get recovery/data from "pre-MultiUser" and "post-MultiUser" ROMs. Sometimes you may be able to manually move or stipulate where you want to recover from etc... others, it may be gone. There was a post about this from TeamWin and their TeamWinRecoveryProject that explains a bit more of it... http://teamw.in/DataMedia
Not sure if this is helpful, but it is worthwhile to look into regarding multi-user Android.
I am having same problem as OP. I share the N7 with my wife and when I flashed ROM I wasnt able to restore any of her data through Titanium, but it would let me restore everything that was on my main user account. Had to switch back to stock rom nandroid, and her data was still gone and mine was all intact. Now she won't let me put a custom rom on If anyone has any suggestions/fixes I'd really appreciate it. Thanks!
ProbyWaN said:
I am having same problem as OP. I share the N7 with my wife and when I flashed ROM I wasnt able to restore any of her data through Titanium, but it would let me restore everything that was on my main user account. Had to switch back to stock rom nandroid, and her data was still gone and mine was all intact. Now she won't let me put a custom rom on If anyone has any suggestions/fixes I'd really appreciate it. Thanks!
Click to expand...
Click to collapse
Probably had to have titanium on both accounts, then created the account after ROM flash and titanium restore on both accounts sperately
Sent from my Nexus 7 using xda app-developers app
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.
Mostly just out of curiosity I flashed a new ROM this weekend. I decided I like pure nexus better so I flashed my backup from twrp but wound up in bootloop. Even though I've never had issues restoring ROMs with MANY other devices, I still followed the directions for backing it up very carefully. I also did a full wipe before trying to restore it. In fact after the 3rd attempt I accidentally wiped internal storage. So that wasn't the issue.
Only thing I can figure is I was using elemental kernel when I made the backup so maybe that was the problem? I don't see why it would matter (or how that would work--removing the kernel, make backup, flash kernel again...) but I'm really stumped on how I went wrong.
KLit75 said:
Mostly just out of curiosity I flashed a new ROM this weekend. I decided I like pure nexus better so I flashed my backup from twrp but wound up in bootloop. Even though I've never had issues restoring ROMs with MANY other devices, I still followed the directions for backing it up very carefully. I also did a full wipe before trying to restore it. In fact after the 3rd attempt I accidentally wiped internal storage. So that wasn't the issue.
Only thing I can figure is I was using elemental kernel when I made the backup so maybe that was the problem? I don't see why it would matter (or how that would work--removing the kernel, make backup, flash kernel again...) but I'm really stumped on how I went wrong.
Click to expand...
Click to collapse
What partitions did you backup/restore?
Heisenberg said:
What partitions did you backup/restore?
Click to expand...
Click to collapse
Well Ive got the right guy to talk to Pretty sure it was what you suggested (system/data/boot/vendor boxes)
But I don't recall if I checked everyone to restore. However, I did store the backup on my computer. Even though I've since got everything back I can try again to restore it. But can you just confirm which I should check when I restore it?
I'll be certain to pay closer attention next time. Its just that this is one thing I had never struggled with. Thanks
KLit75 said:
Well Ive got the right guy to talk to Pretty sure it was what you suggested (system/data/boot/vendor boxes)
But I don't recall if I checked everyone to restore. However, I did store the backup on my computer. Even though I've since got everything back I can try again to restore it. But can you just confirm which I should check when I restore it?
I'll be certain to pay closer attention next time. Its just that this is one thing I had never struggled with. Thanks
Click to expand...
Click to collapse
I recommend restoring system, data, boot, and vendor. Just make sure you're not restoring system image or vendor image.
Heisenberg said:
I recommend restoring system, data, boot, and vendor. Just make sure you're not restoring system image or vendor image.
Click to expand...
Click to collapse
So simple. Thanks a lot!
KLit75 said:
So simple. Thanks a lot!
Click to expand...
Click to collapse
Let me know if you get it booting.
Heisenberg said:
Let me know if you get it booting.
Click to expand...
Click to collapse
Well yes. Thanks again. However, I've got something funky going on. Pin pointing is hard but yea the backup restored. Then I tweaked elemental kernel (nothing crazy, used stable profiles) maybe it was that and an xposed mod (thinking ifont because its one I only just started using lt recently). Anyway when I rebooted to install drivers for viper I got stuck in bootloop. This time I couldn't restore my backup. So I factory reset and reflashed pure nexus. Due to the time I couldn't try and restore the backup again but will try tonight. If I wasn't so hasty I could've deleted the modules list in twrp then maybe booted up but I'm not 100% it has anything to do with xposed. One other factor, it was using dark stock theme.
EVERYTHING I mentioned I've done/run on this ROM without issues but there's a combination of things that's causing the bootloop I think.