So I left Apple, came to Android, rooted my VZW GS3. First time I've ever done anything like this, so I'm new to it. I backed up EVERYTHING using TiBu, did the IMEI backup, Full system/image backup using CWM, unlocked bootloader, etc. Then I flashed to Synergy r46 (august 20th - yesterday's release).
Now I'm at work and my back-up pulled my contacts via Verizon's server, but how do I get back EVERYTHING else? SMS/MMS logs, call logs, apps, app data, etc? Do I need to download TiBu again (fresh from google market) and then load my backups off my Ext-SD card, or what? I guess I'm a bit confused as to where my TiBu items were even stored/saved...I assume it was the ExtSD card, otherwise I would have lost them all upon flashing to Synergy, correct?
Any help to get all my apps and data back on my newly Synergized phone would be awesome!!!! Thanks in advance!!!
Yes download titanium and then point it to the directory you had your back ups saved to (its sd card by default, and which is your phone storage btw) then tab to backup/restore click the check, then once your app data populates, and select run next to restore apps and data.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 02:56 PM ---------- Previous post was at 02:55 PM ----------
And no flashing roms will not wipe all your user data unless you do a complete wipe.
Sent from my SCH-I535 using Tapatalk 2
I used titanuium backup pro to back up all my Apps and system data. And when I flash a new rom I just redownload titanium pro and it automatically restores all my Apps and system data. It is the easiest app I have used. So to answer ur question.....back up ur apps with titanium then after flashing a new rom go and redownload titanium and restore your system data and apps or just apps alone if that's what u prefer? Does that answer ur question or would u like more detailed instructions?
Sent from my SCH-I535 using xda app-developers app
Welcome to android!
Sent from my SCH-I535 using Tapatalk 2
Another very nice feature of Titanium Backup is its ability to pull data from CWM nandroids. There have been a few times where I was quick to flash a new rom without doing a backup of my apps. This has saved me much time from having to re-flash the nandroid backup, backup via TB, then re-flash to the new rom.
voodoomanx said:
And no flashing roms will not wipe all your user data unless you do a complete wipe.
Click to expand...
Click to collapse
This is one thing that scares me...I don't quite understand what's being wiped or how to perform a full wipe. I hope I don't do this on accident on day...When I flashed the ROM, I basically booted into CWM recovery and installed from there....I was unable to install by opening the ROMs ZIP file via ROM Manager. When I tried to install this way, it failed.
Can somebody confirm if I flashed correctly, just to put my worries to rest? Here's how I did it...
I backed everything up, unlocked bootloader, and tried to install Synergy r46 via ROM manager, but I had problem. I had the ZIP for the ROM downloaded to my Ext-SD card, like the installation instructions say. I then opened ROM Manager and went to "install ROM from SD card." The phone rebooted and opened in CWM to install...But kept having problems finding some "path" or something.
So I decide to wing it and rebooted into CWM. I cleared davik cache(sp?), then user data, then navigated to my Ext-SD and selected the ROM ZIP to install. Now, everything seems fine and it says it installed successfully, but I still think I installed in a way that wasn't described.
Is this a legit install and is this how most people flash ROMs, from booting directly into CWM, or should ROM manager have worked for me via "install ROM from SD card???" If so, why didn't ROM Manager work for me?
Rather urgent question: When I restore my items, do I want to click "RESTORE MISSING APPS + ALL SYSTEM DATA?" ill this restore the bloatware that was on my phone prior to flashing????? If so, is there any way around it
Thanks a bunch! Just waiting on an answer to the later questions before I restore.
Weioo said:
This is one thing that scares me...I don't quite understand what's being wiped or how to perform a full wipe. I hope I don't do this on accident on day...When I flashed the ROM, I basically booted into CWM recovery and installed from there....I was unable to install by opening the ROMs ZIP file via ROM Manager. When I tried to install this way, it failed.
Can somebody confirm if I flashed correctly, just to put my worries to rest? Here's how I did it...
I backed everything up, unlocked bootloader, and tried to install Synergy r46 via ROM manager, but I had problem. I had the ZIP for the ROM downloaded to my Ext-SD card, like the installation instructions say. I then opened ROM Manager and went to "install ROM from SD card." The phone rebooted and opened in CWM to install...But kept having problems finding some "path" or something.
So I decide to wing it and rebooted into CWM. I cleared davik cache(sp?), then user data, then navigated to my Ext-SD and selected the ROM ZIP to install. Now, everything seems fine and it says it installed successfully, but I still think I installed in a way that wasn't described.
Is this a legit install and is this how most people flash ROMs, from booting directly into CWM, or should ROM manager have worked for me via "install ROM from SD card???" If so, why didn't ROM Manager work for me?
Rather urgent question: When I restore my items, do I want to click "RESTORE MISSING APPS + ALL SYSTEM DATA?" ill this restore the bloatware that was on my phone prior to flashing????? If so, is there any way around it
Thanks a bunch! Just waiting on an answer to the later questions before I restore.
Click to expand...
Click to collapse
I am wondering if you didn't do the full wipe. If you are using CWM v6.0.1.0 then there is no option labeled "user data" it is "wipe data/factory reset" which is the full wipe like I mentioned.
As far as doing it correctly, as you may have already noticed there is more than one way to do about anything. Personally, I still use CWM v6.0.1.0 and flash the zips there.
P.S. I see you are enjoying your freedom of losing your apples!
Also, tell me how your r46 is working ... I have held off at r23 while they are playing around with kernels and ramdisk tweaks for awhile.
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
dan_joegibbsfan said:
I am wondering if you didn't do the full wipe. If you are using CWM v6.0.1.0 then there is no option labeled "user data" it is "wipe data/factory reset" which is the full wipe like I mentioned.
As far as doing it correctly, as you may have already noticed there is more than one way to do about anything. Personally, I still use CWM v6.0.1.0 and flash the zips there.
P.S. I see you are enjoying your freedom of losing your apples!
Also, tell me how your r46 is working ... I have held off at r23 while they are playing around with kernels and ramdisk tweaks for awhile.
Click to expand...
Click to collapse
I'm fairly certain I did "wipe data/factory reset," I just wasn't sure how it was labeled when I typed that out, but that's really ringing a bell. I think I may have gotten the errors before (using ROM Manager) because I hadn't factory reset? Seems to me I'm good to go! However, my question regarding TiBu still remains.
Edit: In regards to informing you about r46, I'm not sure what to report as I've never used a previous Synergy and have no idea how to compare, other than to the rooted stock ROM. I have heard reports of battery life being worse than the stock ROM, and I can confirm this. I've barely used the phone since I flashed to Synergy and it's dropped 15% battery life in ~3 hours. Seems faster than before but I'm unsure.
nguyenvn said:
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
Click to expand...
Click to collapse
I started getting that sort of behavior so I just restored back to my stock rooted backup and reflashed Synergy 1.7 r23 and then reflashed the theme I'm using. I thought my issues came from other modifications I had tried so I will try to remember to report back to this post tomorrow and tell you if I'm still having those similar issues or if I'm stable again.
dan_joegibbsfan said:
I started getting that sort of behavior so I just restored back to my stock rooted backup and reflashed Synergy 1.7 r23 and then reflashed the theme I'm using. I thought my issues came from other modifications I had tried so I will try to remember to report back to this post tomorrow and tell you if I'm still having those similar issues or if I'm stable again.
Click to expand...
Click to collapse
Was 1.7 r23 supposed to be a really stable release? I read through some of the Synergy thread and didn't see anyone having the issues I had. I felt like I was doing something wrong.
nguyenvn said:
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
Click to expand...
Click to collapse
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
voodoomanx said:
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I used the EZ-unlock app in the play store. I did see that a custom kernel was loaded however when i flashed back to my nandroid (stock rooted) I am back on the orignal kernel. Would the way I rooted have an effect on the reboots? I used the non flash method by Noxious Ninja.
voodoomanx said:
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I agree I have yet to have Synergy boot loop although I'm still on 1.7. I would try to wipe cache and dalvik cache and see if that helps or you could be over clocking to high.
Sent from my Transformer TF101 using xda premium
nguyenvn said:
Was 1.7 r23 supposed to be a really stable release? I read through some of the Synergy thread and didn't see anyone having the issues I had. I felt like I was doing something wrong.
Click to expand...
Click to collapse
I don't know the answer to that specifically. All I know was that I was stable before another modification I made (that said it wouldn't work but I tried it anyway). Since restoring from backup and reloading Synergy and theme I have not seen any weird rebooting anymore.
nguyenvn said:
Would the way I rooted have an effect on the reboots? I used the non flash method by Noxious Ninja.
Click to expand...
Click to collapse
I'm not familiar with that method. I've only used Odin, even when I did have to redo everything I used Odin to stock de-bloated rooted .md5 then CWM'd from there.
So I'm giving it another shot on r50. I made sure to clear dalvik, cache and data. After flashing It gave me the reboot problems again. I installed system tuner to change the cpu back to 1.5. Maybe it's from the overclock but we'll see how it goes. Is everyone leaving it overclocked on 1.9 not having issues?
nguyenvn said:
So I'm giving it another shot on r50. I made sure to clear dalvik, cache and data. After flashing It gave me the reboot problems again. I installed system tuner to change the cpu back to 1.5. Maybe it's from the overclock but we'll see how it goes. Is everyone leaving it overclocked on 1.9 not having issues?
Click to expand...
Click to collapse
That may very well be the issue. 1.9ghz is a very aggressive overclock, and i wouldn't be surprised if was unstable on a good number of phones. Synergy's supposed to boot at 1.5ghz max by default - I don't know whether that was successfully implemented. I personally think it's silly to OC such a capable phone, anyway. Back in the days of the Droid 1, an overclock from the stock 550mhz to 800mhz-900mhz was an enormous improvement. Today, the only thing OCing the S3 gets you is a <10% improvement in Quadrant, more heat, possible instability, and no perceptible difference outside of those silly synthetic benchmarks.
Anyway, in this thread, there seems to be a fair bit of confusion as far as what's what in the android partitions. I'll give you a short rundown.
"aboot" is what's referred to here as the bootloader. It checks to see whether the next partition in the boot sequence, "boot", is authorized. When you unlocked your bootloader, you overwrote aboot with a version that does not perform that check.
"boot" contains your kernel. If your ROM has a custom kernel, it contains a boot.img to overwrite boot.
"system" is the meat of the OS. This is primarily what ROMs flash.
"data" contains all of your apps and settings. When you perform a factory reset, you're reformatting data. If you're flashing a ROM that is significantly different from what you're on now, some of those old settings and data can cause errors, force closes, random reboots, and boot loops. When in doubt, wipe data before flashing a new ROM. When going from one version of a ROM to a newer, very similar version of the same ROM (nightly to nightly), you probably don't need to wipe data, but make a backup just in case. dalvik-cache is also in data; if you wipe data, you've automatically wiped the dalvik cache. It's redundant to wipe data and then wipe dalvik cache.
"cache" is just that, the cache partition. Clearing it won't make you loose anything, at least not anything Android won't silently replace.
So far it seems to be pretty stable on r50. I installed system tuner and brought it down to 1.5 Ghz. I'm not sure why 1.9 is set to default. Doesn't seem like a good idea to me. Thanks all for the help/advice.
I followed the instructions exactly on this page: http://forum.xda-developers.com/showthread.php?t=1663169
CM9 seemed to work fine for a while. I installed Titanium Backup and brought back my apps and just a bit of system data (contacts, voicemail, texts, etc). After I had restored those things, it said it suggested a reboot. I did that, but now it just reboots over and over. I can't get in to the OS for more than a few seconds before it reboots again. Help please!
As that thread specifies, I have a MX2 from CSpire. For now I don't care so much about getting CM9 working as just getting my phone back to a working state. I have both a nandroid and titanium backup on the sd card. I just need very specific instructions on how to get back to the way it was (2.3.6) given that I can't get in to the OS.
Edit: Pulling the battery doesn't resolve anything
Does it let you stay in long enough to remove the app/settings you restored? Are you able to get into recovery mode at all?
If you can get into recovery you might first want to try Fix Permissions and see how that works. If this does not solve it then consider doing a factory wipe and start restoring your apps/settings again one by one and rebooting in between until you get to the particular one that started your reboot problem.
What ROM were you on prior to CM9? Although they should be largely universal sometimes there are some slight changes in custom ROMs that might work well in many other ROMs but not in a select few. Other times it is an app that is not compatible.
The post below might be of some help since your phone seems to have a different method of getting into recovery than what I have dealt with so far.
http://forum.xda-developers.com/member.php?u=4395758
Factory Restore DX2
This might help. It's a factory restore, like you just bought it. http://forum.xda-developers.com/showthread.php?t=1317707
After much sweat, tears, and button pressing, I have gotten it back to stock CM9 and it seems to be behaving as expected. I am going to install apps one by one and reboot between every install. Hopefully I'll find the culprit soon enough.
So I was able to successfully root my AT&T HTC One X and decided I wanted to install the CM 10 ROM (1st ROM install). I did all the data backups with Titanium, downloaded the latest zip files from cyanogenMod (both the 12/13 and 12/14 nightly versions), transferred them to my phone, booted into recovery (TWRP), did a back-up, did a system wipe, flashed the ROM and then did a reboot. However, when it boots it gets stuck in the boot-up screen (bootloop) and doesn't do anything. I have read on this and it keeps saying to wipe system data again and flash the ROM again and it keeps doing this. I want to install this ROM, but I need some help. Any suggestions on what I did wrong?
Note: I accidentally posted this in the Android Q&A section, so I apologize for the double post. I just think this is probably the best place to get my answer.
Did you flash the boot.img?
I did, but incorrectly the first time. I flashed it the right way and everything is working good. Then only problem I have now is when restoring from Titanium Backup it gives me an error from a process called com.android.phone (I think that is what it said). So I wiped it again and rebooted and everything is fine. I can reinstall all the apps, but what could cause that? Could it be some of the data backed up doesn't cooperate with this ROM? Either way I love the CM10 ROM.
jon8105 said:
I did, but incorrectly the first time. I flashed it the right way and everything is working good. Then only problem I have now is when restoring from Titanium Backup it gives me an error from a process called com.android.phone (I think that is what it said). So I wiped it again and rebooted and everything is fine. I can reinstall all the apps, but what could cause that? Could it be some of the data backed up doesn't cooperate with this ROM? Either way I love the CM10 ROM.
Click to expand...
Click to collapse
if they are backups from sense, that *MAY* cause problems, but don't quote me on that. I don't use sense, can't say for sure
OK, maybe that is why. Not a big deal since I haven't had the One X too long. Thanks for the help guys.
Good to know
Hi
Was running CM10 nightly from 12 Dec. Bluetooth froze while in car. I rebooted phone. It never came back up after booting, just looping Cyanogenmod logo.
Went into recovery, did a Nandroid, restored my previous backup from the 11th. Still looping Cyanogenmod logo.
Got home. Reflashed stock kernel. Went into recovery and flashed CM10 stable after wiping. Comes up with HTC logo, then black.
Tried to go back into recovery. Comes up with HTC logo, then goes black.
Now it lets me into fastboot, and into the bootloader menu, but recovery does not work. Neither does booting normally. Tried reflashing kernel AND recovery (stable TWRP). It just keeps looping the HTC logo.
HBOOT is 1.14.
Help, please. I'm going to destroy this piece of ****.
If all else fails, run a RUU and skip the thread.
yea, just ruu. i ruu'd a few days ago for kicks.
some car chargers and even wall chargers can make ur phone go wonky, my old moto backflip would randomly press buttons if i used a non-motorola charger.
on a side note, i never used the word "wonky" until this forum.
try running "fastboot erase cache"
also try a clean install instead of restoring nandroid, im assuming your also fastbooting the boot.img from all your nandroid backups. if not they probably wont boot.
strange...
I would say ruu and retry as well.. Sometimes accessories can make a phone go haywire.. Besides the phone is not a piece of crap.Roms can never give you complete stability while stock unrooted can.
Yep. Thanks. Had to start from scratch with Sense again. Now on CM10 stable (and stable CM10 kernel). Hopefully it doesn't lose its mind again, I'm going overseas soon. Sigh.
For anyone who has a similar catastrophe - Titanium recovered most (but not all) of my apps from my TWRP backup. I guess my data partition was slightly corrupt. AppExtractor restored my SMS database from the backup too.
I hate phones.
Passa91 said:
Yep. Thanks. Had to start from scratch with Sense again. Now on CM10 stable (and stable CM10 kernel). Hopefully it doesn't lose its mind again, I'm going overseas soon. Sigh.
For anyone who has a similar catastrophe - Titanium recovered most (but not all) of my apps from my TWRP backup. I guess my data partition was slightly corrupt. AppExtractor restored my SMS database from the backup too.
I hate phones.
Click to expand...
Click to collapse
I always export my contact list to /sdcard if a change is made and then backup to google just in case
Passa91 said:
Yep. Thanks. Had to start from scratch with Sense again. Now on CM10 stable (and stable CM10 kernel). Hopefully it doesn't lose its mind again, I'm going overseas soon. Sigh.
For anyone who has a similar catastrophe - Titanium recovered most (but not all) of my apps from my TWRP backup. I guess my data partition was slightly corrupt. AppExtractor restored my SMS database from the backup too.
I hate phones.
Click to expand...
Click to collapse
I'd suggest keeping a boot.IMG and a stock ROM on the SD card along with adb drivers so you can fix it with a computer without downloading anything.
Sent from my Nexus 4 using xda premium
I was tinkering with my TF101 and sort of accidentally (lol) overwrote my installation of Timduru's KatKiss-4.3.1_029.zip with his KatKiss-4.4.2_016.zip without wiping anything before doing so. (Actually didn't have any data to speak of - as I formatted and wiped in proper fashion on the install of KatKiss-4.3.1_029), and it hadn't been run for more than a couple of days.
I've developed a severe addition to ROM experimentation, and so may install and backup every few days it seems. Don't have a nickname for that habit yet, but I sense that they are many similar addicts around this site.
What I would like to know, since all seems, at least to this n00b, to be just fine - what "might" happen w/ my TF101 since the overwrite of a newer ROM?
Staying put, until I hear from a forum guru, or at least anyone with more experience than me (and that will include most all members).
Thanks,
Cal
If you overwrite a ROM with a different one (different android version, or by a different developer) you may run into issues where it will not boot, or it may run poorly, random reboots, sleep o death.
When changing ROMs it is HIGHLY recommended to wipe the system, caches and the data partition (wiping data is not the same as FORMAT DATA in TWRP). There are some system settings stored in the /data/ partition that may conflict with different ROMs.
Most of TimDuru's KatKiss ROMs you can forward flash (even to new versions of Android) but you CANNOT go backwards. I flashed from 4.2.2 to 4.3 without wiping data and had no issues. However, if you tried to flash from 4.3 to 4.2.2 without wiping data, it will not boot until you wipe the data partition.
I have not tried this with the 4.4 version of his ROM (I am still on 4.3 for now.)
Oh, and yes, the addiction is called CrackFlashing.
Always ALWAYS make a backup in TWRP before flashing a new ROM or even an upgrade to the current ROM. If you want to go back to 4.3, make a backup and then use Titanium Backup Pro version to extract any apps and data from the 4.4 version and restore to 4.3. Do not restore any system settings or apps.
frederuco said:
<snipped a bit>
When changing ROMs it is HIGHLY recommended to wipe the system, caches and the data partition (wiping data is not the same as FORMAT DATA in TWRP). There are some system settings stored in the /data/ partition that may conflict with different ROMs.
Most of TimDuru's KatKiss ROMs you can forward flash (even to new versions of Android) but you CANNOT go backwards. I flashed from 4.2.2 to 4.3 without wiping data and had no issues. However, if you tried to flash from 4.3 to 4.2.2 without wiping data, it will not boot until you wipe the data partition.
Oh, and yes, the addiction is called CrackFlashing.
Always ALWAYS make a backup in TWRP before flashing a new ROM or even an upgrade to the current ROM. <some stuff snipped>
Click to expand...
Click to collapse
Ahh...then the addiction is obviously not curable unless one destroys the tablet, BUT the new ROM may be just fine as is, I take it. That was what I was hoping to hear.
Thanks, and any idea when a new experimental ROM will come from Tim? Just felt a slight twitch. I've tried the other team's creations and seem to only feel really satisfied with Kits - (guess 'CrackFlashing' addiction picks a really hard one to withdraw from).
Many thanks!
Cal
Cal-123 said:
Ahh...then the addiction is obviously not curable unless one destroys the tablet, BUT the new ROM may be just fine as is, I take it. That was what I was hoping to hear.
Thanks, and any idea when a new experimental ROM will come from Tim? Just felt a slight twitch. I've tried the other team's creations and seem to only feel really satisfied with Kits - (guess 'CrackFlashing' addiction picks a really hard one to withdraw from).
Many thanks!
Cal
Click to expand...
Click to collapse
I think it will be a while until timduru starts to work in a experimental rom , since there is no Android 5 yet.
But Tim has marked katkiss as stable and for my daily use it is. But you could try 4.4.2.
schwigi said:
I think it will be a while until timduru starts to work in a experimental rom , since there is no Android 5 yet.
But Tim has marked katkiss as stable and for my daily use it is. But you could try 4.4.2.
Click to expand...
Click to collapse
Read the original post again -- I've been on the 4.4.2_16 forever now it seems!! The urge to try something new is over-bearing! :silly: :victory:
Ah-Ha! I see that Tim's put up a new 'stable' one. KK 4.4.2_17! Yeah!! This should be a super easy fix for the 'crack-itis' I have developed...as I will overwrite this one also.