yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] centro714:
today all of the sudden my phone stalled/froze for the very first time.

I ended up removing the battery to force a restart. once it booted up, my time was off and the date was set to December 31, 1999 (kinda weird since its the day before y2k.)

Anyway, has this happened to anyone? And what causes this?

Thanks
[Samsung Epic 4G Touch] Freeroot:
It hasn't happened to me and I haven't heard of it happening. Tell me about your phone. Are you rooted? Have a from? If so, which one? I believe the time and date are actually found through your data connection (or wifi). Maybe try updating prl and restart. If anything, I think the ics ota update occurs tomorrow, so that will undoubtedly fix it.
[Samsung Epic 4G Touch] SAShady:
Must have got the prince virus
[Samsung Epic 4G Touch] centro714:
I'm rooted and running calk v2.9.2

My phone had been solid until I updated to calk3.0. So now i'm flashed back down to 2.9.2 and things are good until the stall.
[Samsung Epic 4G Touch] kingsway8605:
Great scott! If you are reading this centro714, it seems that when you pulled your battery, it caused a ripple in the space-time continuum leading you to travel back to the date December 31st, 1999. Meet my former self at the Silver Spring diner on first and third street in Baltimore, MD at precisely 8:14pm PST and he, or I, will be able to help you return to the future.
[Samsung Epic 4G Touch] someguyatx:
Tonight you should party like its 1999
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PeterGuru:
How would you feel if you could make a Nandroid backup, wipe your device clean, flash a new ROM, restore all your personal apps (with settings, SMS messages, and call log intact), all in about 10 minutes?

Too good to be true? After all, you probably remember what they say about things that sound too good to be true. Normally you shouldn’t believe it. In this case, though, it’s real, and it works! Many people in the DIET ICS ROM thread have already tried it, with amazing success.

As always, there’s a caveat. You perform the following procedures at your own risk. I will not be held responsible for any damage, frustration, anger, sadness, or suicides that may result from your decision to implement this process.

CAUTION: This method of data recovery will work under a wide variety of situations; however, you must consider the following:

1)	When going from a stock or stock-based ROM to another stock or stock-based ROM, this method should work very well. It doesn’t matter if it’s the same ROM as long as both are based on a stock ROM.

2)	When going from a stock or stock-based ROM to an AOSP-based ROM, such as CM or AOKP, this method may/will not work. Similarly, when going from an AOSP-based ROM to a stock or stock-based ROM, this method may/will not work.

Use common sense, and always follow instructions provided by the ROM Developer.

This method also removes any concern as to whether or not you need to wipe because the process involves doing a full wipe, which only adds about 30 seconds to the procedure.

Here we go …

1.	Boot into Recovery

2.	Make a Nandroid backup

3.	Wipe data/factory reset

4.	Wipe cache partition

5.	Wipe Dalvik Cache

6.	Flash ROM

7.	DO NOT REBOOT – STAY IN RECOVERY

8.	Select backup and restore

9.	Select advanced restore

10.	Select the Nandroid backup you made above

11.	Select Restore data

12.	Select Yes – Restore data

13.	WAIT!

14.	REBOOT

If all goes according to plan, you will arrive at your home screen with all apps in place, and with all settings intact, including stored text messages, and your call log.

Shockingly easy, isn’t it? After all, it is ALWAYS suggested that you do a Nandroid before you flash any new ROM, so this procedure will ALWAYS have you completely up-to-date.

Okay, you can hit the thanks button now. ;)

Peter

(formerly PeterHTC)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lessthanzach:
Good to see you here from the one x. I'm glad to be back on Sammy. One x just had too many bugs for me and no memory card was a deal breaker.

This tutorial seems legit, I'm just concerned that doing this could overwrite mods the rom developer implements and cause issues. Any response to that concern?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RubenRybnik:
Usually use Titanium Backup myself, so I can selectively select which apps to restore with data. If you're going from a stock based ROM( stock modified ) to AOSP ( CM, AOKP, or any of their kangs ) then I don't think I'd recommend this shotgun method of restoring. However Stock -> Stock this is very fast and shouldn't cause any issues.

About mods, not sure, most mods are going to be in /system so those should be fine, however anything themed will be overwritten I believe. ( CWM wipes and restores, not an additive restore correct? )
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PeterGuru:
I completely agree ...

Yes, Titanium has the advantage of allowing you to selectively restore apps, etc.

I completely agree. If you're sticking with a stock-based ROM, or up-dating almost ANY existing ROM, then this method should work just fine; however, like you said, I would not recommend it if going from stock to AOSP, or vice versa.

I would also agree concerning the mods, which are almost always in /system, and aren't the theme files anywhere BUT in the data folder? Please correct me if I'm wrong.

Peter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PeterGuru:
Same here ...

I would have to agree. I had far too many little glitches with my ONE X and ONE XL that were just too annoying. So far I could not be happier with the S3.

Peter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CZ Eddie:
Good tip, Peter. I never knew about that one and it will come in handy for me!

Am I the only one who also formats /system in Recovery?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Yze:
thank you for this! im jumping from stock to diet ics and this tip helped a lot.

im also coming from about a months use of HTC One X. its only been one day with this sg3 and i already prefer it over the htc one x.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] P8TRIOT:
Is ROM Manager still advisable or did Koush move on and it is an abandoned project like some of the reviews suggest in the Google Play store? I used to use this to flash and manage my NANDROID's and it was super easy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lessthanzach:
I just used his Rom manager to flash the AT&T recovery and it works great.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] P8TRIOT:
When I had my old Droid X2 (MB870), this is the method I used all the time, and it was very simple and straightforward, if I am understanding you correctly, this method is conditional in that you have to be coming from an existing flashed ROM? So for instance I just rooted yesterday through Odin but am still on stock, this method wouldn't work for me? It would be awesome if this could be utilized universally for what ever (rooted state), is this in fact the case or what exactly is the specific condition if any?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PeterGuru:
I will be adding a cautionary note to the first post ...

Although this will work under many different circumstances, there are a few very important restrictions, which I will add to the first post in a few minutes.

Peter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dahlem:
Not to with this but there is a software update be AT&T if installed will it take away root?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PeterGuru:
Carrier up-dates may be disabled ...

Although I would like someone to confirm this, it is my belief that, if you root your device, then software up-dates from the carrier no longer work.

Peter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkeyman:
This works fine with ApOcAlYpSe 7_10_12 ROM

This method I can confirm works perfectly with the ApOcAlYpSe 7_10_12 ROM by smartguy044. I installed the Rom and restored everything from a previous stock setup that I did a nandroid of right before flashing. From start to finish the whole process took me less than the 10min as advertised. Just thought I would share just in case anyone was on the fence or concerned about using this with the ApOcAlYpSe 7_10_12 ROM. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PeterGuru:
Thank you for the confirmation ...

Thank you for the confirmation.

I hope this helps those who are afraid to flash new ROMs because the entire process (from Nandroid to installing all apps and re-establishing settings), can take hours. I never really trusted Titanium, even though many do, so before hearing about this method, it would take me anywhere from 2-6 hours to get my device back to exactly how I want it, with all settings re-established. Flashing and installing apps wasn't the issue, which took me less than an hour. It's opening every single app and adjusting the settings that often took hours.

Peter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wgarrido:
You really don't have to worry about restoring data if you flash a ROM that doesn't format the data partition. I have found that some/most don't wipe data. So you can just flash the ROM and reboot and go on your way. Of course do make a backup just in case.

I use TiBu 100% of the time. Never had it not work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkeyman:
You are correct in your suggestion "If" the Rom installed does not wipe or format the data. This is obviously a alternate, fast method for restoration of user data if needed in a pinch or just as a normal way of getting your configuration and apps back to the way you had them configured previously (either stock or on another similar installed ROM).

I am not sure what you meant by you use TiBu and not have it work? When restoring from TiBu you should always just restore missings Apps with Data and avoid anything System related as it would most likely overwrite anything that a ROM customization may have just installed and will cause issues whether minor or even serious. I would suggest only messing with system restore items if you absolutely know what you are doing. That aside I agree with Peter as TiBu as good as a backup as it is, its time consuming...but its another precautionary backup method needed as a just in case.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wgarrido:
I was just saying that TiBu hasn't lost data or anything. I know about restoring system data. I have gotten away with restoring some of it in the past.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
OTA's should work with root as long as you are on stock and haven't altered your build.prop. On that note, I haven't heard anything about a Rogers update?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PeterGuru:
I haven't heard anything from Rogers, either ...

I haven't heard anything from Rogers regarding an up-date, either.

And thank you for answering the OTA question.

Peter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
No problem. Apparently the att update was to disable the universal search capability of searching the phone's internals, limiting it to web searches. This was a defensive move by Samsung to prevent another Apple patent lawsuit, similar to the galaxy nexus issue. Luckily in Canada we don't have this issue, so I don't anticipate a Rogers update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PeterGuru:
I've been following that issue, too.

Yes, I've been following that lawsuit, as well as the million others files by Apple (shaking head).

Peter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Yeah, so now there's two features (that I know of) that Apple's patent trolling has killed on our phones:

1) Universal Search (I actually do use this often, as it's much quicker than scrolling through my drawer to eyeball the appicon)

2) Clickable addresses and phone numbers. This was already removed from the HTC OneX, but not the S3 yet (hmm... or was it?)

Hopefully somebody provides a modified gapps package when it's finally updated again. Call it: gapps-with-an-apple-****you.zip or something. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Zoandroid:
Rooted my Verizon GS III today, installed ROM Mgr, then flashed the non-touch version of CWM Recovery. The first nandroid I have made so far has a date code of 1970-01-05.x.x.x?? What's up with that? Any of you folks on the over versions of the GS 3 seeing this when you make a nandroid with CWM Recovery?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 613BulletProof:
Mine did the same actually.. Restoring wasn't a problem though...

Noob questions guys... I know just about every Rom DEBLOATS your phone with software that usually comes preinstalled with the phone that you can't uninstall.. I flashed a ROM and after rebooting everything was gone along with useless apps that came with the phone, I liked that a lot, however following these instructions I restored from my NANDROID back up, which then reinstalled all the apps, i mean ALL OF THEM, i thought it would only reinstall the apps i downloaded from the Google Play market, all the bloated apps are on my phone again, is there a solution to this or workaround? Im still flashed with the rom but its not really DEBloated anymore after i restored from the back up, im trying to uninstall certain apps that the stock rom would not allow me to such as Facebook AT&T Navigation etc etc..

thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] malinois16:
You could download titanium backup from the market and frezze or uninstall apps that you don't want.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkeyman:
The 1970 issue is a known issue with the latest CWM recovery (I am currently on 5.8.4.5, later versions still do not see the ext sdcard yet)...Head over to the threads (http://xdaforums.com/showthread.php?t=1766253 )for details. It does not effect your backups at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Zoandroid:
OK, thanks. The way you worded that, does it mean I could possibly use an older version of CWM Recovery if I wanted to do so?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkeyman:
Yes...But (there's always a BUT) do your homework. I know there were a few previous versions that had the ext sdcard problem on them too. But I don't see a need to go back unless you are bent on it for some reason...All seem to have the dating issue on them. But flash away if it makes you feel better and keeps the world as you know it from imploding in on itself. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
With external sd card and most else working, I would advise to stay on this version of cwm. Just go into your file explorer and rename your backups.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Zoandroid:
Thanks for both replies. The actual issue for me is not so much the screwy date in the file name, but where the file is stored. I oppose the growing tendency to have a segment of internal memory named "SD Card", because I'm seeing most apps (including CWM) which generate files I want to keep backed up defaulting to the "first instance" of the path named "SD Card" to save their files. Now I agree that true SD cards can have failures too, but files stored on them are much more "safe" if a device suddenly has a catastrophic failure than files retained in its internal memory. Add to that on many devices this chunk of internal storage is rather small compared to being able to swap out real SD Cards. So, I prefer my files be saved on the external card. It also makes for easier backup operations to need only work with files in one place.

I have started emailing app developers for the apps I use that have this issue, and suggesting they put a user configurable setting in the app to tell it where to put its files. Of the three I wrote so far, all have replied they like the idea and plan to implement it in future releases. OR - device designers could get a little more original with the name of the internal storage area.

For now I am manually copying these internal storage folders periodically to the real SD Card. I'd like to find a utility to automate the process, perhaps one I can schedule to run every night while the phone charges. Anyone know of such an app?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CZ Eddie:
This method worked well for me going from one release of AOKP to an updated release.

Kept all my AOKP system settings, afaik. My custom pull-down and everything else I've looked at are the same as before.

Thanks, Peter.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkeyman:
Zoandroid there should be an option in CWM to run your nandroid backups to the internal or external cards (I currently have all my backups to my 32gb card) Unless you are using a version of CWM as stated earlier that will not see the External SD card mount you must update your version of CWM to a version which has ext sd available. Aside from that most of the apps I use within the settings, allow you to specify your save drive and folder (like TiBu for instance) and alot of times when you go pro on these apps the settings stick so when you change devices or in my case clean flash ROMs all the time and restore the settings are stickied and will set right back or be restored from a backup. In the case of the new SGSIII the External SD naming was changed (From ext_sdcard to now ExtSDcard) and so were the settings on my Apps. I agree we do need a standars and it adhered to but such is the community of Open Source...you get alot of development from many different areas and different ways of doing things. So as with most things in this community you have to try and be flexible and make things work best for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasonziter:
DUDE. YOU ROCK. Why didn't anyone tell me about this for the two years I was flashing with my EVO 4G. Well, they probably did I just never saw it.

Thanks again !!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Zoandroid:
I am running CWM Recovery v5.8.4.9, and I can not find any setting in it that would allow me to specify where it is to store nandroid backup files. I see under Mounts and Storage there is a "mount /external_sd" command, but if that is what you are suggesting, it isn't very clear to me. Could you please point me to where this setting is?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkeyman:
Sorry I was not precise. In recovery you have backup, which saves your backups to to the extSdCard in a folder called Clockworkmod>backup>1970xxxx file. Within the same CWM directory in recovery there is another option to save your backups to the internal SDcard. These backups will be saved into the same named folder as previously mentioned only onto the internal SD as an alternative to the external save. You do not use the Mounts area at all. Once you have a save you can move the file to anywhere and if you want to restore at that point you can point CWM advance restore to retrieve the backup from wherever you move it too and store it at (internal or external). Hope this helps or clears things up for you.

BTW where did you get the CWM 5.8.4.9 version? Are you testing? The only versions for the S3s that I have seen are up to 5.8.4.7 and that was still having the external sd not seen issue. The working version of CWM touch that I know that works for our phones is 5.8.4.5 (but still has the 1970 naming bug). Just wondering.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Zoandroid:
Hi,

I told ROM Manager to install CWMR (not the touch version) and 5.8.4.9 is what it installed. There was no decision on versions offered. ROM Mgr. 5.0.0.8 shows both current and latest recovery as 5.4.8.9 at the top of its screen.

I have Recovery open, and see:

-reboot system now

-install zip from sdcard

-wipe data/factory reset

-wipe cache partition

-backup and restore

-mounts and storage

-advanced

Where do I go from there to tell it which location to put nandroids? I haven't changed anything and it defaults to the INTERNAL "SD Card".

-backup and restore just has:

- backup

- restore

- advanced restore

- Go Back

If I select backup, it immediately launches into creation of the nandroid.

- advanced does not have an option to set location either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nidhish91:
Will this work on my Defy too??

S3nt fr0m my D3fy/w1u1 GB st4BL3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xThe Enforcer:
Great thread!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kr3w1337:
It can be done faster than that actually.

Do the following:

Format /system

Wipe dalvik

Install ROM

Wipw cache

Reboot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] malinois16:
And how is that going to restore you apps from the app store and app data?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kr3w1337:
Apps are stored in /data which you aren't formatting so there is nothing to restore as you aren't going to wipe them to begin with. Which makes the entire process faster.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkeyman:
The ways you guys are talking about are clean install methods which are good IF you want to do it that way and want to redo passwords/settings on everything. Peters solution gives the installer the option of restoring ALL data and APPS as previously installed at the last (Good Backed up) state of use...NO Downloads or changes required (Unless any said app has been updated by its developer...then it will need to updating). But as stated in the OP once rebooted you should be at a ready state of use right after install no extra or long setup delays needed. :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kr3w1337:
The steps I stated keep your settings as well as app settings.

Notice step 11 OP which says to restore data. If you don't format data to begin with then it will have the same effect without needing the backup.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PeterGuru:
You're right ...

You're right. It should work just as well, and save a bit of time in the process; however, I'm a firm believer in wiping. One thing that wiping does is ensure a clean system. Beginning from a clean slate is almost always the best way to go, especially when trying to troubleshoot potential problems.

Many ROM developers note in their OPs that if you don't do a full wipe, they are unwilling to help when it comes to problems. Performing step 2, and then steps 8-12 in my OP should only add about 5-6 minutes to the overall time, which could help to resolve issues, and provide some peace of mind.

Peter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PeterGuru:
Like you, I used to be quite wary of flashing ROMs because, I thought, oh no, it's going to take me hours, not just to install each individual app (I have about 120 of them), but more importantly, and more time-consuming, to up-date each one with the correct settings. This method works so well, I now never hesitate to flash a new ROM.

I never knew about the Advanced Restore feature within Recovery (both CWM and TWRP) until one member mentioned it a few weeks ago. I wish I could recall that member's name, as it is he/she who truly deserve the thanks.

Peter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Amon37:
Ok so noob question here, I have a ROM flashed now and my phone where I like it, If I want to try a new ROM and then restore why wouldn't it restore the old ROM? I thought that was the point of making the backup? maybe I just have never done the advanced restore and that's where the difference is.