Preserving everything stock before flashing. - Samsung Galaxy Nexus

So I am now a very proud owner of a GN and I come from the Vibrant.
I'm used to flashing ROMs kernels etc, but know its different for every phone.
The one thing I didn't do was ever back up my IMEI or anything like that. So before I start flashing on the GN, can anyone help me out with how to back up everything in case I need to go back to stock. Thanks!

Do a Nandroid backup in CWM.

WiredPirate said:
Do a Nandroid backup in CWM.
Click to expand...
Click to collapse
I didn't think nandroid did that. I tout there was a separate file that needed to be saved and extracted.

jzero88 said:
I didn't think nandroid did that. I tout there was a separate file that needed to be saved and extracted.
Click to expand...
Click to collapse
You're correct, nandroid just backs up /system, /data (excl. /sdcar), boot.img and recovery.img. That's it.
I've seen other people back up the following, although I personally can't see a reason to if you don't plan on messing with them (simple rom flashing and wiping will not touch those areas):
the contents of /factory
the efs.img file

efrant said:
You're correct, nandroid just backs up /system, /data (excl. /sdcar), boot.img and recovery.img. That's it.
I've seen other people back up the following, although I personally can't see a reason to if you don't plan on messing with them (simple rom flashing and wiping will not touch those areas):
the contents of /factory
the efs.img file
Click to expand...
Click to collapse
Ya I think the efs.img is what I was thinking about. Plus people flashing and wiping their IMEI numbers which I need for ensquared insurance. But flashing back to a stock image would give you back your IMEI or no? "If wiped"
Sent from my Galaxy Nexus using XDA

jzero88 said:
Ya I think the efs.img is what I was thinking about. Plus people flashing and wiping their IMEI numbers which I need for ensquared insurance. But flashing back to a stock image would give you back your IMEI or no? "If wiped"
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
To be honest, I'm not sure what would wipe your IMEI number.
I think it is stored in two places on your device, and neither of them are touched by flashing ROMs. But go ahead and back up what I mentioned above if you want. It certainly won't hurt (root required of course).

efrant said:
To be honest, I'm not sure what would wipe your IMEI number.
I think it is stored into places on your device, and neither of them are touched by flashing ROMs. But go ahead and back up what I mentioned above if you want. It certainly won't hurt (root required of course).
Click to expand...
Click to collapse
I feel pretty safe with CM9, but if i decide to flash anything else, I think I will. Thanks for the insight
Sent from my Galaxy Nexus using XDA

Related

Nandroid backup ?

Sorry for the dumb question, but a full nandroid backup, is done how? With titanium, or rom manager. Like I said sorry for the dumb question but everything I read just confused me. I'm really not that dumb just need some because I confused myself. Thanks!
Sent from my PC36100 using Tapatalk
I am new to this stuff but I learned pretty quick because I truly love my Evo so I want the best for it! (roms/kernels) but I over think everything so I need a few dumb questions answered from time to time...
JoshEvo
Nandroid backup is done through the recovery menu. Use titanium backup for the apps, sms backup for the texts, and for the contacts, go to contacts, hit menu then export to SD CARD.
Swyped from my sexy EVO.
They aren't dumb questions, you're just starting out. But:
1. Titanium backup is to backup your apps and system, in case you do a clean wipe. backup your apps every so often, especially when you changing roms.
2. If on clockwork recovery, you can backup your rom using it.
3. You can manually backup by turning the off the phone, powering back up, but holding vol+down ad you do, and then in the bootloader screen. Once there, select recovery, then go to backup/restore.
Thanks roxx, you cleared up what I said. You always seem to answer my questions or be in the same thread as me.
Swyped from my sexy EVO.
Cool thanks! I know how to flash roms through rom manager and kernels in recovery. I thought I was doing a nandroid backup by backing up my stock rom before flashing a new one. So I just boot into recovery (rom manager,or root manager) can't remember if it's root manager? But get into recovery and it will say nandroid backup? Once again thanks for helping me. I want to switch to a non-sense rom but don't wanna mess up my Evo!
Sent from my PC36100 using Tapatalk
Re read your answer and got my other question answered thanks all
Sent from my PC36100 using Tapatalk
Got it! Nandroid backup = backup/restore! So if I do a nandroid backup it will backup my phone/rom/etc... As it is now?
Sent from my PC36100 using Tapatalk
jacoballen22 said:
Thanks roxx, you cleared up what I said. You always seem to answer my questions or be in the same thread as me.
Swyped from my sexy EVO.
Click to expand...
Click to collapse
Anytime man, and you made perfect sense. And I'm always floating around.
Just_Josh said:
Cool thanks! I know how to flash roms through rom manager and kernels in recovery. I thought I was doing a nandroid backup by backing up my stock rom before flashing a new one. So I just boot into recovery (rom manager,or root manager) can't remember if it's root manager? But get into recovery and it will say nandroid backup? Once again thanks for helping me. I want to switch to a non-sense rom but don't wanna mess up my Evo!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Well you can boot into recovery from rom manager, just select reboot into recovery. And I believe you're referring to the bootloader screen. And it only says "nandroid' if you're on amon_ra recovery, but nandroid/backup are the exact same thing. On clockwork, navigate to backup/restore, then backup..and it'll take about 2-5 minutes. After that, go back to the main menu, and wipe factory/data, cache, and then go under advanced and wipe the dalvik cache. After that, install zip from sdcard > install zip > select your rom. And when you boot up, log in, blah blah, then use titanium backup to restore your apps but NOT system settings, or you can get some force closes.
If that's the case, why do I need to flash back to stock rom before flashing a new one? If I'm backing up my phone with a custom rom? Or do I flash back to stock then do a nandroid? You can stop me anytime...lol..I am normal...i swear I am
Sent from my PC36100 using Tapatalk
Just_Josh said:
If that's the case, why do I need to flash back to stock rom before flashing a new one? If I'm backing up my phone with a custom rom? Or do I flash back to stock then do a nandroid? You can stop me anytime...lol..I am normal...i swear I am
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Lawlz, you don't have to flash back to the original stock rom before flashing a new one. You just backup your current rom, then flash the new one. You always backup befpre flashing in case something bad happens.
1. Backup/nandroid current rom
2. Wipe factory/data, cache, dalvik cache
3. Flash new rom
4.
And its good to ask questions.
Wow THANK YOU! That makes my life soo much easier. Thank everyone I think I now what I'm doing now and not just doing it! You guys rock!
Sent from my PC36100 using Tapatalk
Just_Josh said:
Wow THANK YOU! That makes my life soo much easier. Thank everyone I think I now what I'm doing now and not just doing it! You guys rock!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Anytime, and glad you've got it clear. Always here to help if ya ever need anything.
If they used the proper term, it might be much less confusing. Backups made from the recovery menu are synonymous with making an image of the phone's entire file structure (similar to acronis trueimage for windows). This includes all the system files, applications, settings, and any related customizations.
Titanium backup on the other hand serves the function of baking up an individual application and its' associated data. I don't think there's an equivalent of this on the pc, but you get the idea.
I still don't know where this term 'nandroid' comes from. I've seen it used both as a noun and verb on here, which only complicates matters for those not familiar with the android terminology.
gpz1100 said:
If they used the proper term, it might be much less confusing. Backups made from the recovery menu are synonymous with making an image of the phone's entire file structure (similar to acronis trueimage for windows). This includes all the system files, applications, settings, and any related customizations.
Titanium backup on the other hand serves the function of baking up an individual application and its' associated data. I don't think there's an equivalent of this on the pc, but you get the idea.
I still don't know where this term 'nandroid' comes from. I've seen it used both as a noun and verb on here, which only complicates matters for those not familiar with the android terminology.
Click to expand...
Click to collapse
'Nandroid' come from amon_ra, its what its listed from you when backup. Nandroid backup/restore. I personally don't know where it came from, but that's where people get it from.
I repeat what I hear, so nandroid could mean asswipe for all I know lol I never looked it up.
Swyped from my sexy EVO.
jacoballen22 said:
I repeat what I hear, so nandroid could mean asswipe for all I know lol I never looked it up.
Swyped from my sexy EVO.
Click to expand...
Click to collapse
I think it was a coined term relating to android, as that is the root of the word.
Nand is the type of flash memory that is used internally on our phones for the android system.
Nand + Android = Nandroid
I'm guessing that's how Amon came up with the name.
ckombo said:
Nand is the type of flash memory that is used internally on our phones for the android system.
Nand + Android = Nandroid
I'm guessing that's how Amon came up with the name.
Click to expand...
Click to collapse
Exactly how.

How to make a flashable ODIN backup?

Hey guys,
I'm looking for some info from a knowledgeable dev on how to create a custom ODIN backup that can be restored using the ODIN executable for Windows? My goal is to create a complete hard image of my entire device (including my apps/personal data) that I can restore at anytime (as if it was never touched since the backup) using ODIN.
If anyone can fill me in on the details I would highly appreciate this.
Thanks in advance.
EDIT: I see some other guides here, here, and here. But I noticed some of the blocks they reference are nonexistant on the Galaxy Nexus.
Update #1: Looking for answer to this - Link to post
Update #2: May have found it - Link to post
Info that may help #1
Info that may help #2
would also like to know how to backup with odin since my nandroids always fail at restoring data and then im forced to fresh install a rom
The Race To Die said:
would also like to know how to backup with odin since my nandroids always fail at restoring data and then im forced to fresh install a rom
Click to expand...
Click to collapse
Yes! Thank you! I'm glad I'm not the only one who has this issue. Are you using Touch CWM 5.8.0.2? Or the regular 5.5.0.4?
open1your1eyes0 said:
EDIT: I see some outdated guides here, here, and here. But I noticed some of the blocks they reference are nonexistant on the Galaxy Nexus.
Click to expand...
Click to collapse
How are these guides outdated? They work just fine for the devices they were written for. The Charge uses a completely different device layout compared to the Nexus. They are meant for completely different phones, hence the reason stuff isn't the same. Someone needs to find the proper names for the items that are dumped, and then an Odin package can be put together, but every device will have it's own guide on how to make the packages.
open1your1eyes0 said:
Yes! Thank you! I'm glad I'm not the only one who has this issue. Are you using Touch CWM 5.8.0.2? Or the regular 5.5.0.4?
Click to expand...
Click to collapse
Haven't tried koush's touch yet. Doesn't look as good to me as the unstableapps touch recovery, but have no luck with unstable or regular cwm recovery
Sent from my Galaxy Nexus using Tapatalk
imnuts said:
How are these guides outdated? They work just fine for the devices they were written for. The Charge uses a completely different device layout compared to the Nexus. They are meant for completely different phones, hence the reason stuff isn't the same. Someone needs to find the proper names for the items that are dumped, and then an Odin package can be put together, but every device will have it's own guide on how to make the packages.
Click to expand...
Click to collapse
I see, so each device has different blocks allocated. I wonder how people figure out what blocks go to what?
The Race To Die said:
Haven't tried koush's touch yet. Doesn't look as good to me as the unstableapps touch recovery, but have no luck with unstable or regular cwm recovery
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I'm assuming you're referring to the first Touch Recovery (Unofficial) that was released? But really? Even the regular CWM doesn't work for you? This is a serious issue if we can't restore backups. How are we the only ones who noticed?
Yes that is the one I am talking about. Creating backups works fine, but restoring always fails while restoring data.
Sent from my Galaxy Nexus using Tapatalk
The Race To Die said:
Yes that is the one I am talking about. Creating backups works fine, but restoring always fails while restoring data.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I can confirm the same on the official Touch CWM 5.8.0.2 however I think I can recall making and restoring backups back when there was only the regular 5.5.0.4. Do you mind flashing that and testing if you can make a backup and restore it again?
open1your1eyes0 said:
I see, so each device has different blocks allocated. I wonder how people figure out what blocks go to what?
Click to expand...
Click to collapse
Look in /dev/block/platform/omap/omap_hsmmc.0/by-name
Those are what you set your "if" path to.
Sent from my Galaxy Nexus using Tapatalk
open1your1eyes0 said:
I can confirm the same on the official Touch CWM 5.8.0.2 however I think I can recall making and restoring backups back when there was only the regular 5.5.0.4. Do you mind flashing that and testing if you can make a backup and restore it again?
Click to expand...
Click to collapse
sure, will report back in a little. could it have been that i ran out of space? i only had 5 or 6 gigs left, but just erased all my backups and now have about 18gb
efrant said:
Look in /dev/block/platform/omap/omap_hsmmc.0/by-name
Those are what you set your "if" path to.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I'll take a look right now.
The Race To Die said:
sure, will report back in a little. could it have been that i ran out of space? i only had 5 or 6 gigs left, but just erased all my backups and now have about 18gb
Click to expand...
Click to collapse
That is possible actually, I only had about 2-3GB left when I had the failed restores. Now that I redid my phone maybe it won't be an issue.
I am very interested in this topic since the stock image for my phone is not available. I would like to have an option to restore the stock image in case of a warranty issue.
I was exploring using ADB backup. Would it make sense to do a factory reset before creating the backup image?
Stuck on 4.0.1
efrant said:
Look in /dev/block/platform/omap/omap_hsmmc.0/by-name
Those are what you set your "if" path to.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
How do you differenciate which one refers to which partition (data, dbdata, system, etc...). I think this is the main issue here.
open1your1eyes0 said:
How do you differenciate which one refers to which partition (data, dbdata, system, etc...). I think this is the main issue here.
Click to expand...
Click to collapse
Not really sure what you are referring to. Each of those is a partition. User data is the data partition, system is the system partition, boot is the boot partition, etc, etc.
Sent from my Galaxy Nexus using Tapatalk
efrant said:
Not really sure what you are referring to. Each of those is a partition. User data is the data partition, system is the system partition, boot is the boot partition, etc, etc.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
EDIT: Disregard I was looking in the wrong directory.
flashed 5.5.0.4 through rom manager
rebooted into recovery
backup completed fine
https://dl-web.dropbox.com/get/Public/IMG_20120208_204435.jpg?w=d80708cb
now making a backup through rom manager just for the hell of it to see if one works over the other
The Race To Die said:
flashed 5.5.0.4 through rom manager
rebooted into recovery
backup completed fine
https://dl-web.dropbox.com/get/Public/IMG_20120208_204435.jpg?w=d80708cb
now making a backup through rom manager just for the hell of it to see if one works over the other
Click to expand...
Click to collapse
Really hope it works.
efrant said:
Look in /dev/block/platform/omap/omap_hsmmc.0/by-name
Those are what you set your "if" path to.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Ok so I figured out which block goes to what partition (here). Now using this, how can I make a flashable package for ODIN? Also do the filenames of the "of" have to be a specific extension or name or it can be named anything? How does ODIN know which "of" file to treat as which partition in that case?
amazingly it worked! must not have had enough space to restore all of the data or something. now to figure out this odin thing. first samsung ive owned so ive never used it, had an og before my nexus.
The Race To Die said:
amazingly it worked! must not have had enough space to restore all of the data or something.
Click to expand...
Click to collapse
Thank you for testing this! I will stick to 5.5.0.4 for now and make sure I have enough space from now on.
FYI, I found another backup method: Link and More Info. For that you need to have the latest adb.exe from the Android SDK. I am attaching it to this post.

[Q] Possible to create a .tgz file to flash (as a backup)?

I have a toro galaxy nexus, and i wanted to create a flashable tgz file with everything in it (radios, system, userdata, boot, bootloader, etc). I wanted to do it because I have my Gnex working wonderfully with a custom ROM, all the apps I wanted installed, with the updated radios and bootloader, etc...was wondering if its possible to "pull" what i have on it now and either put it into a tgz file or a way to do it directly...that way i could just flash it with the rooting kit if ever i got into trouble...
Just make a nandroid backup. I really fail to see how that doesn't do exactly what you you want and with less effort.
063_XOBX said:
Just make a nandroid backup. I really fail to see how that doesn't do exactly what you you want and with less effort.
Click to expand...
Click to collapse
well i think a nandroid backup only backs up; system, data, and boot...but i want to do a tgz file with everything there, so that if instead of going back to stock to clean up my files (if i got a corrupt media file or something going wrong in there), i can go back to a point where everything is right where i want it...i know the factory google tgz file includes; system, data, boot, radio, bootloader, userdata and whatever else i may be missing...
its just to shortcut the "going back to stock" to clean up the system...especially because right now there is no google factory image for 4.2 for the Toro galaxy nexus...
It does lack a radio and bootloader but for the most part its exactly what you're asking for. I'm not sure how likely what you're actually asking for is.
063_XOBX said:
It does lack a radio and bootloader but for the most part its exactly what you're asking for. I'm not sure how likely what you're actually asking for is.
Click to expand...
Click to collapse
Well I was hoping for a full backup of everything...would make it easier to return back to a stable point with a custom rom instead of going back to factory then re flashing everything...
Sent from my Nexus 10 using Tapatalk 2
So again I ask, is it possible? If so, how? Not if I should or shouldn't...
Sent from my Nexus 10 using Tapatalk 2
808phoneaddict said:
So again I ask, is it possible? If so, how? Not if I should or shouldn't...
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
Omapflash
Sent from my i9250
Seriously?
Nandroid and do regular backups.............
Beamed from my Maguro.

Confusion about /0 directory / 4.2.2

I'm considering upgrading to a 4.2.2 ROM. Been doing some reading, particularly about the /0 folders in the SD card.
I saw it suggested that a person NOT switch back down to 4.1.X from 4.2.2. Anyone have OK experience doing that? I want to be able to go back if for some reason I want to.
I'm on 4.1.1 TW based ROM. From what I read, I should have /data/Media folder, but I don't . Either I'm confused, or what I read was wrong, or I mis-interpreted it. Comments?
Thanks for any thoughts.
ewingr said:
I'm considering upgrading to a 4.2.2 ROM. Been doing some reading, particularly about the /0 folders in the SD card.
I saw it suggested that a person NOT switch back down to 4.1.X from 4.2.2. Anyone have OK experience doing that? I want to be able to go back if for some reason I want to.
I'm on 4.1.1 TW based ROM. From what I read, I should have /data/Media folder, but I don't . Either I'm confused, or what I read was wrong, or I mis-interpreted it. Comments?
Thanks for any thoughts.
Click to expand...
Click to collapse
You can gon ack and forth and be just fine but just make sure you back up your imei and efs folder and you are golden.
The only reason is that you can loose your imei go back BUT its rare. If you.do a full wipe is recommended and not just system and factory reset i.e. /data as well.
A ext sd card is best so you can avoid all of that and a good file explorer like root explorer.
Sent from my SAMSUNG-SGH-I747 using xda premium
hednik said:
You can gon ack and forth and be just fine but just make sure you back up your imei and efs folder and you are golden.
The only reason is that you can loose your imei go back BUT its rare. If you.do a full wipe is recommended and not just system and factory reset i.e. /data as well.
A ext sd card is best so you can avoid all of that and a good file explorer like root explorer.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Really appreciate your input. I have been proceeding in the direction you recommend.
I presume that restoring /DATA after moving from 4.1.1 to 4.2.2 is not something I should do. Better to restore apps from Tibu (not system), and data for those apps as required.
I also anticipate making a Nandroid of current system, with hopes of restoring to that if I'm not happy with the new ROM I would experiment with. Maybe doing a full wipe, etc. before restoring that Nandroid would be a good idea too.
Your thinking on all this is correct.
ewingr said:
Really appreciate your input. I have been proceeding in the direction you recommend.
I presume that restoring /DATA after moving from 4.1.1 to 4.2.2 is not something I should do. Better to restore apps from Tibu (not system), and data for those apps as required.
I also anticipate making a Nandroid of current system, with hopes of restoring to that if I'm not happy with the new ROM I would experiment with. Maybe doing a full wipe, etc. before restoring that Nandroid would be a good idea too.
Click to expand...
Click to collapse
Sounds good. I never restore /data but in the overly cautious camp haha. Happy flashing
Sent from my SAMSUNG-SGH-I747 using xda premium
hednik said:
Sounds good. I never restore /data but in the overly cautious camp haha. Happy flashing
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
It actually works great, but I only do it if same version of ROM, ie 4.1.1, updated to another or newer 4.1.1.

TWRP recovery to a replacement phone--what should I restore?

Ok, so I had to get a replacement Note 4 due to camera hardware issues. I made a TWRP backup of my original phone, now I want to restore things on my new phone. My question is what should I restore? The things I backed was everything I could:
Boot
Recovery
System
Data
Cache
EFS
Modem
Should I restore everything? I get the feeling that I shouldn't try to restore EFS for some reason, but I am not sure. Anything I definitely should not restore on the new device? Thanks
Sent from my SM-N910P using XDA Free mobile app
What version firmware was the first on and what about the replacement? Were they both the same? Both nk2?
beezar said:
Ok, so I had to get a replacement Note 4 due to camera hardware issues. I made a TWRP backup of my original phone, now I want to restore things on my new phone. My question is what should I restore? The things I backed was everything I could:
Boot
Recovery
System
Data
Cache
EFS
Modem
Should I restore everything? I get the feeling that I shouldn't try to restore EFS for some reason, but I am not sure. Anything I definitely should not restore on the new device? Thanks
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
Recovery, system (if same fw version), data, modem. All should don't give you any trouble. Efs I Dont know but think it could be device specific but now sure. I wouldnt do that one myself. Boot may have some device specifics in it as well that makes me nervous. But someone with the proper knowledge might chime in past what my comfort limits are.
flyhighx said:
What version firmware was the first on and what about the replacement? Were they both the same? Both nk2?
Click to expand...
Click to collapse
Whoops, missed this post. Yes, they are both NK2.

Categories

Resources