Related
Ok so FedEx should be here soon with my replacement phone. I want the first thing i do is to back it up completely. I am wondering what the best way of doing this would be. TiBu? will that back up all that i need to save for a future restore to stock. nv_data and everything.
Stephenxda said:
Ok so FedEx should be here soon with my replacement phone. I want the first thing i do is to back it up completely. I am wondering what the best way of doing this would be. TiBu? will that back up all that i need to save for a future restore to stock. nv_data and everything.
Click to expand...
Click to collapse
I'm not really sure what you mean to accomplish. If you want to be able to restore to stock, ODIN is your friend. Backups are usually only important for retaining and restoring changes or data you make. The easy process is to use TiBu on the apps/settings you want. Then copy the TitaniumBackup and any other desired folders to your PC (or external sd) so youc an copy them back and restore from them in the future.
Stephenxda said:
Ok so FedEx should be here soon with my replacement phone. I want the first thing i do is to back it up completely. I am wondering what the best way of doing this would be. TiBu? will that back up all that i need to save for a future restore to stock. nv_data and everything.
Click to expand...
Click to collapse
1. Root the device.
2. Install ROM manager, and busybox.
3. Go to CWM console, and backup ur device. Copy this backup at a safe place.
Till here, u have a device set to the settings u had it delivered to u.
Though there shouldn't be a need, well, would be helpful in case u wanted to for some reason.
When u need to restore to what they sent u, u'd need to go to stock, apply this flash, and remove the root, and the two apps above.
When should you do a full wipe when installing a custom rom and when is it ok to dirty flash? Can someone please explain?
Sent from my HTC One using xda app-developers app
If you're changing bases it's always good to wipe. And if you're changing roms you should always wipe. But if you're just applying an update you might get away with a dirty flash. Save a backup first and you don't risk much with a dirty flash.
Sent from my HTC One using xda app-developers app
lampel said:
If you're changing bases it's always good to wipe. And if you're changing roms you should always wipe. But if you're just applying an update you might get away with a dirty flash. Save a backup first and you don't risk much with a dirty flash.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I apologize if this is a stupid question. When you say change base what exactly do you mean? Is this from one rom to another or a version change on the same rom like 5.0 to 6.0? Or is it a kernal change? If it is a version change would 5.1 to 5.6 be considered changing base?
Thank you very much. Again, I apologize if this is a dumb question. I have read around a little and did not quite get an answer I was comfortable with.
easyrabbit said:
I apologize if this is a stupid question. When you say change base what exactly do you mean? Is this from one rom to another or a version change on the same rom like 5.0 to 6.0? Or is it a kernal change? If it is a version change would 5.1 to 5.6 be considered changing base?
Thank you very much. Again, I apologize if this is a dumb question. I have read around a little and did not quite get an answer I was comfortable with.
Click to expand...
Click to collapse
What rom are you using?
CYNiCAL2KX said:
What rom are you using?
Click to expand...
Click to collapse
I am using VenomOne 5.7.0 but it is more of a general question. I am a bit new to this and want to have a good understanding of everything from the ground up.
---------- Post added at 08:31 AM ---------- Previous post was at 08:23 AM ----------
easyrabbit said:
I am using VenomOne 5.7.0 but it is more of a general question. I am a bit new to this and want to have a good understanding of everything from the ground up.
Click to expand...
Click to collapse
Sorry I meant ViperOne...
easyrabbit said:
I am using VenomOne 5.7.0 but it is more of a general question. I am a bit new to this and want to have a good understanding of everything from the ground up.
---------- Post added at 08:31 AM ---------- Previous post was at 08:23 AM ----------
Sorry I meant ViperOne...
Click to expand...
Click to collapse
'4.19.401.8' that is the current base which is in use by viper. Sometimes it's okay to flash, it's trail and error.
Always make a Nand before you flash, incase anything goes wrong, you can go back to the previous version, like a windows restore point.
A fresh install is wiping data and cache in TWRP it's called a factory reset. This doesn't format the /sdcard/0 so all sd card data remains.
If you were to flash a older base with a newer one, it may work perfectly, it may not, what I do is: Create a Nandroid of system,data,boot. Wipe, then install, then I restore data only. This way the phone tends to be (fairly) just how you left it, with messages, apps etc still remaining.
Like I said, after making a Nand, just flash unless the OP says specifically not to. Then if you have issues, it's a simple case of rolling back by restoring Data, System. I hope this answers your question, I think you'll just get the hang of how it works just by actually giving it ago, not much can really go wrong unless you start flashing things not meant for your phone.
CYNiCAL2KX said:
'4.19.401.8' that is the current base which is in use by viper. Sometimes it's okay to flash, it's trail and error.
Always make a Nand before you flash, incase anything goes wrong, you can go back to the previous version, like a windows restore point.
A fresh install is wiping data and cache in TWRP it's called a factory reset. This doesn't format the /sdcard/0 so all sd card data remains.
If you were to flash a older base with a newer one, it may work perfectly, it may not, what I do is: Create a Nandroid of system,data,boot. Wipe, then install, then I restore data only. This way the phone tends to be (fairly) just how you left it, with messages, apps etc still remaining.
Like I said, after making a Nand, just flash unless the OP says specifically not to. Then if you have issues, it's a simple case of rolling back by restoring Data, System. I hope this answers your question, I think you'll just get the hang of how it works just by actually giving it ago, not much can really go wrong unless you start flashing things not meant for your phone.
Click to expand...
Click to collapse
Thank you very much for the info. So now I understand what the base is. Aside from time or laziness I would think that doing a full wipe is the way to go. Maybe I am wrong but I would rather not take chances.
Right now Iam currently having some issues. I basically did a dirty flash of the same version I am on to clear the theme and it went wrong. It never came back up after an hour in the "starting applications" state. After that I got back in to recovery (TWRP) and did full wipes and installs. They seem to go OK but then the android setup crashes right after the "name your device" part and the launcher wont start (chose Nova). Everything just hangs. I reboot but then it just hangs. I just did my nandroid restore and I am back up and running but not sure what is going wrong. I tried the install a few times with different options but everytime the setup part crashes. So my simple question is now another full blown issue haha.
I love this board tho, everyone is so helpful. One day I hope to be the one giving the advice.
CYNiCAL2KX said:
'4.19.401.8' that is the current base which is in use by viper. Sometimes it's okay to flash, it's trail and error.
Always make a Nand before you flash, incase anything goes wrong, you can go back to the previous version, like a windows restore point.
A fresh install is wiping data and cache in TWRP it's called a factory reset. This doesn't format the /sdcard/0 so all sd card data remains.
If you were to flash a older base with a newer one, it may work perfectly, it may not, what I do is: Create a Nandroid of system,data,boot. Wipe, then install, then I restore data only. This way the phone tends to be (fairly) just how you left it, with messages, apps etc still remaining.
Like I said, after making a Nand, just flash unless the OP says specifically not to. Then if you have issues, it's a simple case of rolling back by restoring Data, System. I hope this answers your question, I think you'll just get the hang of how it works just by actually giving it ago, not much can really go wrong unless you start flashing things not meant for your phone.
Click to expand...
Click to collapse
May I ask, is restoring the data folder similar to adb backup/restore or even titanium? With titanium I could just restore messages or whatever. Doing the whole data folder could put back something I dont want or something I want to get rid of. With my current situation I think this might solve my issue with setup but I really wanted to start from scratch and retweak everything.
Regarding the base, I cant seem to find where I can check that on the device. It is not in settings-about where I would expect to find it.
I am finally working my nerve up to try this again and figure out why the initial android setup is crashing. I am getting more comfortable now especially since I know my nandroid restore works. Good fun but scares the hell out of me at the same time when things go wrong haha....
easyrabbit said:
May I ask, is restoring the data folder similar to adb backup/restore or even titanium? With titanium I could just restore messages or whatever. Doing the whole data folder could put back something I dont want or something I want to get rid of. With my current situation I think this might solve my issue with setup but I really wanted to start from scratch and retweak everything.
Regarding the base, I cant seem to find where I can check that on the device. It is not in settings-about where I would expect to find it.
I am finally working my nerve up to try this again and figure out why the initial android setup is crashing. I am getting more comfortable now especially since I know my nandroid restore works. Good fun but scares the hell out of me at the same time when things go wrong haha....
Click to expand...
Click to collapse
Ususally most issues regarding cross flashed bases are problems derived from the system partition, however i'm not saying it doesn't happen, but I've never really had many issues restoring data. Also, once you back up data , you can install a Nandroid manager app where you can restore certain things from nand backups. This is what I chose to use over things like titanium as it's just another thing to do
CYNiCAL2KX said:
Ususally most issues regarding cross flashed bases are problems derived from the system partition, however i'm not saying it doesn't happen, but I've never really had many issues restoring data. Also, once you back up data , you can install a Nandroid manager app where you can restore certain things from nand backups. This is what I chose to use over things like titanium as it's just another thing to do
Click to expand...
Click to collapse
Thank you very much. I have heard back and forth on wiping the system but had never done it till now. I am still not sure what was happening. in my initial installs I allways removed sense and used Nova. The last time I left Sense and most off the apps. I also 're-downloaded the zip. it worked like a charm. soon I will start investigating kernals and updating firmwae and antennas. Will play with the basics for a while first tho. eventually I would like to try my own. However the bar is set high with venomone.
I am now dealing with sense which is ok bit for me Nova is as close to perfect a launcher for me. still investigating battery lifevetc but will probably do another flash removing sense. venomone fixed everything I didnt like about it for the most part but I love to be able to swipe up or down anywhere to get quickbar and app drawer... still testing tho, I have a full life but definitely want to contribute here... my new obsession.
So, I am a new happy owner of the Moto X VZW Dev Ed. However, Motorola was having a sale last week and said they couldn't give me a price match, but that I could reorder and ship back the other one (which is what I did).
Problem is, I've already updated the first one (I think there were three OTA updates I installed), unlocked and rooted it. Then installed a bunch of stuff, disabled a lot of stuff, etc... I really don't want to do this twice!
My question is if I make a nandroid backup using TWRP (with all options turned on), what is the minimal amount of work I'd have to do to transfer everything to the new phone?
I guess since nandroid backups do not include firmware, it's safest to complete the OTA updates on the replacement phone (unless I know for sure there were no firmware updates installed), unlock, root and lastly restore from the nandroid of the old phone?
etc6849 said:
So, I am a new happy owner of the Moto X VZW Dev Ed. However, Motorola was having a sale last week and said they couldn't give me a price match, but that I could reorder and ship back the other one (which is what I did).
Problem is, I've already updated the first one (I think there were three OTA updates I installed), unlocked and rooted it. Then installed a bunch of stuff, disabled a lot of stuff, etc... I really don't want to do this twice!
My question is if I make a nandroid backup using TWRP (with all options turned on), what is the minimal amount of work I'd have to do to transfer everything to the new phone?
I guess since nandroid backups do not include firmware, it's safest to complete the OTA updates on the replacement phone (unless I know for sure there were no firmware updates installed), unlock, root and lastly restore from the nandroid of the old phone?
Click to expand...
Click to collapse
I would use Philz @hachamacha edition. See the RAZR HD section. If an OTA is needed YES do it first.
The problem is the data partition not the system. Due to your ESN and such.
Hachamacha may help you with some issues.
He is about to do a unified build to include his new X!
---------- Post added at 01:50 PM ---------- Previous post was at 01:26 PM ----------
He just posted the unified
http://forum.xda-developers.com/showpost.php?p=52414440&postcount=78
Thanks, the ESN/IMEI is normally stored in the radio's firmware? Or are you saying there's some file somewhere that also contains that data?
etc6849 said:
Thanks, the ESN/IMEI is normally stored in the radio's firmware? Or are you saying there's some file somewhere that also contains that data?
Click to expand...
Click to collapse
Right data contains phone data. But you may find a way to patch those IDs. Not via *228, as that is for 3g only. Try a complete restore & if you have to wipe data you can.
I do not know what happens when data is loaded from another phone.
aviwdoowks said:
I would use Philz @hachamacha edition. See the RAZR HD section. If an OTA is needed YES do it first.
The problem is the data partition not the system. Due to your ESN and such.
Hachamacha may help you with some issues.
He is about to do a unified build to include his new X!
---------- Post added at 01:50 PM ---------- Previous post was at 01:26 PM ----------
He just posted the unified
http://forum.xda-developers.com/showpost.php?p=52414440&postcount=78
Click to expand...
Click to collapse
Hi aviwdoowks,
I haven't yet posted anything but an intention to post something (how convoluted is that?) ; I have some builds that're up to date, unified, etc, for the *dt versions, but since I can't test until I get one, I hate to dump it on people. If someone doesn't care, then PM me. I'll be around for a few hours today and tomorrow to respond. Just make sure you tell me what device you've got since I just started dev for about 9 or 10 devices today.
Cheers.
hachamacha said:
Hi aviwdoowks,
I haven't yet posted anything but an intention to post something (how convoluted is that?) ; I have some builds that're up to date, unified, etc, for the *dt versions, but since I can't test until I get one, I hate to dump it on people. If someone doesn't care, then PM me. I'll be around for a few hours today and tomorrow to respond. Just make sure you tell me what device you've got since I just started dev for about 9 or 10 devices today.
Cheers.
Click to expand...
Click to collapse
I cannot get multi quote to work.
What do you think of the Op's restore question.
I thought you might come up with a way to restore data to a different X phone.
aviwdoowks said:
I cannot get multi quote to work.
What do you think of the Op's restore question.
I thought you might come up with a way to restore data to a different X phone.
Click to expand...
Click to collapse
Near as I can see (and I just tried multi-q for the first time), it is a myth I copied the original question down below and will look and see.
etc6849 said:
So, I am a new happy owner of the Moto X VZW Dev Ed. However, Motorola was having a sale last week and said they couldn't give me a price match, but that I could reorder and ship back the other one (which is what I did).
Problem is, I've already updated the first one (I think there were three OTA updates I installed), unlocked and rooted it. Then installed a bunch of stuff, disabled a lot of stuff, etc... I really don't want to do this twice!
My question is if I make a nandroid backup using TWRP (with all options turned on), what is the minimal amount of work I'd have to do to transfer everything to the new phone?
I guess since nandroid backups do not include firmware, it's safest to complete the OTA updates on the replacement phone (unless I know for sure there were no firmware updates installed), unlock, root and lastly restore from the nandroid of the old phone?
Click to expand...
Click to collapse
Not sure I'm understanding. Was the first phone not a DE, rather an xt1060 or something like that? If so, which model was it? I'm also awaiting (few days) delivery of my first Moto X DE but have had no other one. Any factory unlockable phone I've had in the past is returned to a somewhat blank condition (/system and /data) as soon as you either a) lock or b) unlock using the Moto website so you'll of course, have to do that much and then slap on SuperSU (or whatever you like for root), busybox, etc.
Minimal amount of work? Stick to one recovery type because making backups is easy. If you want to use TWRP (which is a good recovery) to restore to the new phone, then do it. The easiest part of everything is changing recoveries once unlocked and rooted and you "KNOW" that TWRP can restore TWRP. Yes, Philz Touch can also restore TWRP, but when we build for phones new to us, sometimes, the git is in a state where maybe something isn't working, so why bother taking a chance on wasting all that time.
I've got Philz Touch latest version built for the msm8960dt (the motos/ultra/maxx/and others) but haven't looked into it since I've got no phone yet. My other possible suggestion would be to switch to Philz Touch as soon as I put up a pointer on it (or use an older one if you get your phone before). Stick it on your phone and make a new backup in CWM/Philz format. I'll go through the code and enable the /persist partition so you can get a backup of that. When you get the new DE, goto website, unlock, (which will probably just git rid of /data and /system), and if you want the least amount of guessing what is needed and not needed , just install the DE 4.4.2 image from the site so you'll have the firmware that is desired for that model phone. (radio and /firmware / persist stuff). Then boot to recovery and do the restore of the usual partitions. Use the .xml file in the .zip to figure out the order of the partition flashing for /firmware and radios and any other bits you want to flash. I would just create a batch file with 'fastboot flash 'partitionname' '{name}.img' statements in the exact order as in the .XML file and run it.
I don't know which (if anything but stock) ROM you've used and I'm not sure it matters which flavor it is, but it matters which version it was built from on the Moto so be sure it's apples to apples, since most the ROMs I've looked at seem to require the kernel from whatever was installed before. (the /lib/modules are also built to match that kernel as well and are a part of the /system of that ROM).
Everytime I've gone into a new phone situation and decided I was going to get away with a nandroid restore and voila , it always takes a bit of touch-up work, so pick one recovery, make the backups doing it, and do the restores to the DE using it rather than adding yet another variable. I can't think of one situation where I didn't have to at least use say Titanium Backup to restore the apps (I don't bother with data) because things rarely work out the same way. The other not-so-intuitive thing is that moving things from one phone to another (especially a nonDE to a DE) often bring up a new issue or more so expect to have to do a bit of work. Just be sure to make a good copy of the /sdcard/.. stuff that you need to keep (TitaniumBackup), and other data you need that nandroids don't care about, and back it up to your PC using adb. After you unlock, you can copy it to the target phone, and try the recovery. I really like Philz and I like TWRP as well, but I'd never tell someone they could move for sure from one phone to another without any problem. Best bet is using same recovery type on both ends though. Don't restore /persist or /firmware unless you're certain it's wiped. I mean that 4.4.2 image (.xml.zip) from the website has all the firmware you really want in it at it takes about 2 simple statements from adb to get it on the phone. That's pretty easy. Also, you never know. Might get lucky and a nandroid could be all you need but I'm not holding my breath on that.
Good luck.
before anyone says anything about using a search function let me say that i have searched every page on this site/google/youtube/ etc for an answer or fix
but anyway, so i screwed up and installed an old firmware update (mistakingly thinking it was new) and ran into a ton of issues, that after an extremely long night, i was able to fix.
i managed to load up the stock rom 4.4.2 that i had when i initially unlocked my device, and was hoping to copy over my twrp back up that i made earlier that day. when i make a twrp back up, i usually copy it to my pc to save phone space, and i tried to copy it back, and i put it in the backup folder, and although i can find it in file manager, i cant recover it. looking at the folder it looks like every other backup ive ever made, i have no idea why it wont show. i got a flasher app "Rashr" and it doesnt recognize it as a recovery folder either. does something need to be different? when i tried the twrp app, it selected all the typical boot img etc things but then says that it has to restart and when it does the twrp recovery still doesnt recognize it.
help ideas?
im still actively working it and if anyone finds anything that'll be wonderful thanks
I was helping you yesterday no?
I think what happened when you flashed a 4.1.2 you changed the file structure.
4.2.x and above handle things differently.
If you look in data/media/0/twrp you should find your backup.
I would still suggest running the latest RUU and starting fresh and it will give you the correct file structure.
BD619 said:
I was helping you yesterday no?
I think what happened when you flashed a 4.1.2 you changed the file structure.
4.2.x and above handle things differently.
If you look in data/media/0/twrp you should find your backup.
I would still suggest running the latest RUU and starting fresh and it will give you the correct file structure.
Click to expand...
Click to collapse
this might help too, don't know
Aldo101t said:
this might help too, don't know
Click to expand...
Click to collapse
Maybe you can elaborate on what this does I've never seen it.
BD619 said:
Maybe you can elaborate on what this does I've never seen it.
Click to expand...
Click to collapse
back when 4.1.2 was live, guys flashed to 4.2, and it messed up the file structure, if they went back to 4.1.2, (if I remember correctly)this would fix the file structure.
---------- Post added at 03:45 PM ---------- Previous post was at 03:40 PM ----------
Aldo101t said:
back when 4.1.2 was live, guys flashed to 4.2, and it messed up the file structure, if they went back to 4.1.2, (if I remember correctly)this would fix the file structure.
Click to expand...
Click to collapse
I thought maybe he could flash back to 4.1.2 then flash this, then back up his sdcard to computer then go on to 4.2. or above delete his sdcard on 4.2 or above then restore it from computer, just my thoughts on it.
Aldo101t said:
back when 4.1.2 was live, guys flashed to 4.2, and it messed up the file structure, if they went back to 4.1.2, (if I remember correctly)this would fix the file structure.
---------- Post added at 03:45 PM ---------- Previous post was at 03:40 PM ----------
I thought maybe he could flash back to 4.1.2 then flash this, then back up his sdcard to computer then go on to 4.2. or above delete his sdcard on 4.2 or above then restore it from computer, just my thoughts on it.
Click to expand...
Click to collapse
He flashed a really old rom and lost his ability to use the touch screen.
Not sure if he will be staying on the older rom.
BD619 said:
He flashed a really old rom and lost his ability to use the touch screen.
Not sure if he will be staying on the older rom.
Click to expand...
Click to collapse
yeah, your probably right, just thought I'd throw it out there.
i managed to use the files i used to root my phone to restore my phone back to a usable state. im not exactly sure if its RUU but my phone is basically back to where it was almost 5 months ago, luckily i had did an htc backup about 3 weeks ago, so i didnt quite lose every thing. its back to 4.4.2. im not exactly sure if my issue is making sense.
i have a back up i made on twrp, i cut and paste it to my desktop. when i put it in my twrp backup folder, its treated as if its not there. i can physically search for it and find it within the folder. is there a certain way that backups are made? i just made a backup of my device today, and it created a seperate FAxxxxxxxxx folder, im gonna try and put it in there to see if it helps any, but at this point im thinking i should give up and admit a lost cause.
my devce works, and thanks BD for all the help you gave!! seriously wouldve gone crazy without it.lol
Enishi44 said:
i managed to use the files i used to root my phone to restore my phone back to a usable state. im not exactly sure if its RUU but my phone is basically back to where it was almost 5 months ago, luckily i had did an htc backup about 3 weeks ago, so i didnt quite lose every thing. its back to 4.4.2. im not exactly sure if my issue is making sense.
i have a back up i made on twrp, i cut and paste it to my desktop. when i put it in my twrp backup folder, its treated as if its not there. i can physically search for it and find it within the folder. is there a certain way that backups are made? i just made a backup of my device today, and it created a seperate FAxxxxxxxxx folder, im gonna try and put it in there to see if it helps any, but at this point im thinking i should give up and admit a lost cause.
my devce works, and thanks BD for all the help you gave!! seriously wouldve gone crazy without it.lol
Click to expand...
Click to collapse
You must have ran the RUU file. Once you run the RUU file and you have to unlock everything using the HTC DEV method then yes, you will loose everything because the RUU file will bring your phone as it was coming out of the store.
Can I just restore the twrp generated nandroid on a replacement nexus 6?
not recommended, but you can try; just be prepared to restore it from scratch if it locks up..
NiNJAwitaRaZR said:
Can I just restore the twrp generated nandroid on a replacement nexus 6?
Click to expand...
Click to collapse
Do NOT do this. A nandroid contains files that are device specific. You could end up needing a new replacement.
The replacment is another nexus 6 and I'm talking about the backup that twrp makes.
NiNJAwitaRaZR said:
The replacment is another nexus 6 and I'm talking about the backup that twrp makes.
Click to expand...
Click to collapse
I know what you are talking about. Apparently you do not know just what the nandroid does or what its purpose is. A nandroid is a back up off the partitions on your device and some contain files made per device.
Just save yourself the head ache and set it up fresh. Doesnt take too long.
K thank you for the info
ok, all you people saying no, ive done this a few times with absolutely no issues after. BUT, it has to be done right, or you will have issues. just be sure that you create a nandroid on the new n6 first. then delete that new nandroid and stick the old nandroid in that same exact spot, within that folder. if the nandroid is from a phone thats not a n6, then make sure that only data is backed up and restored, nothing else.
simms22 said:
ok, all you people saying no, ive done this a few times with absolutely no issues after. BUT, it has to be done right, or you will have issues. just be sure that you create a nandroid on the new n6 first. then delete that new nandroid and stick the old nandroid in that same exact spot, within that folder. if the nandroid is from a phone thats not a n6, then make sure that only data is backed up and restored, nothing else.
Click to expand...
Click to collapse
Then you are running a very big risk of messing your imei and baseband up permanently. Nandroid backups include all partitions. They should only be restored on the device it was pulled from. Too many people trying to take the easy way out and being lazy. This leads to people doing warranty returns which to be honest unless you always remained stock and never modded then you should never use.
I'd done this to my one plus one but restore only boot , system and data partitions none other , no problem.. But thus is Nexus 6 , I don't want to take risk.
zelendel said:
Then you are running a very big risk of messing your imei and baseband up permanently. Nandroid backups include all partitions. They should only be restored on the device it was pulled from. Too many people trying to take the easy way out and being lazy. This leads to people doing warranty returns which to be honest unless you always remained stock and never modded then you should never use.
Click to expand...
Click to collapse
wrong.. nandroid backup have whatever partition you included in the backup. DO NOT BACKUP YOUR IMEI!
simms22 said:
wrong.. nandroid backup have whatever partition you included in the backup. DO NOT BACKUP YOUR IMEI!
Click to expand...
Click to collapse
Before telling someone they are wrong. Let alone me. You have to take into account how normal people will do it. Now just from your statement people will be expecting an IMEI partition. When they dont see one they will do a full nandroid and then guess what happens? You have to remember that people understanding what they are doing is not the people that need help with something like this. No one that has any real clue would restore a nandroid from one device to another. Hell most dont even bother with nandroids anymore. They are more noob tools then anything else.