Apps FC after applying Speedmod Lagfix on Froyo Stock - Captivate Q&A, Help & Troubleshooting

After getting Clockwork Mod working and making a Nandroid backup, I decided to apply hardcore's Speedmod Lagfix. When it was done I ended up with most of my apps force closing, including Launcher Pro, which made it very difficult to do anything. I was able to switch to TW Launcher so I could do things. I tried to restore some apps and data with TI, but get a message saying my phone won't allow it for security reasons. I was able to previously as I installed Amazon Market app on my rooted Cappy with stock Froyo. I found out after lots of work that if I uninstalled and re-installed apps they worked fine. Hoping to avoid having to do that. I also tried the fix permissions options in recovery to no avail.
Did I do something wrong or have I left a step out in applying the lagfix? My thoughts are I may have to do a nandroid restore, but am hoping not to. My plans are to flash Fasty ROM eventually. Is it better to get this cleaned up first or restore back to stock, without lagfix possibly, and then flash?
Thanks for any assistance.

if you're going to flash a different rom why worry about problems your having on your current os? its kinda like asking this:"windows xp is giving problems should i resolve those before installing windows 7?"
the enabling of the lagfix makes a nandroid backup, wipes everything to format to ext4 and then restores everything. sounds like perhaps that data was corrupted. make a fresh tibu backup, disable lagfix, do a wipey wipe of data, cache, and dalvik from cwm and flash a new rom, and then only restore MISSING APPS + DATA. DO NOT RESTORE ANY SYSTEM DATA.

Thanks for the advice. I'll try it later when I get home. I guess I'm being a bit careful and want to be comfortable in taking the next step. Since this is my only phone for right now, I can't afford to be without it very long. I've been looking for a cheap, broken screen, yet working Cappy on eBay to let me toy around with.

Related

Confused about FRF72

<<Reposted from QA, couldn't move the post myself>>
I'm confused with FRF72, why is it only 2MB?! That is very small. Is this meant to patch the earlier FRF50 which I have running right now?
Even if it is/or isn't a patch, has anyone tried to run the ROM ZIP WITHOUT WIPING so to save from having to restore Titanium backup? I can't be bothered with the whole process until the weekend is over, unless I can upgrade without wiping. Please let me knwo if any of you have attempted to do that and have you succeeded? Thanks.
When I upgraded 2.1 to 2.2 and was curious, I didn't wipe and the 2.2 successfully booted, and everything all the settings and apps were intact, but it was force closing every single time I tried to run any app, so after that, I wiped, and then it was fine.
I don't want to go through that whole process again though, this time being its 2.2 older beta to newer beta, so it might work without a wipe right?
if u dont wipe u will be stuck in a boot loop. i did a nandroid and then flashed it only to land in the loop. then i wiped and flashed and all was well. thank goodness for nandroid

Flashing over a rom?

So im wondering, what is the standard practise, or based on your own experiences. What is the best way to flash over an existing rom using CWM? What do you do to prepare the fone for new rom, wipe user data, dalvik cache, before or after flashing. Just trying to get a good idea of how to do it.
Sent from my SAMSUNG-SGH-I897 using XDA App
going from rom to rom:
put rom.zip on /sdcard/
reboot to recovery
install zip from sdcard
point to rom.zip
flash
reboot
any rom that has been properly done will wipe user data and dalvik cache for you. no need to do it manually
i always flash back to eclair and master clear with odin one click to make sure all files from previous roms are gone then CWM flash new ROM
Pirateghost said:
going from rom to rom:
put rom.zip on /sdcard/
reboot to recovery
install zip from sdcard
point to rom.zip
flash
reboot
any rom that has been properly done will wipe user data and dalvik cache for you. no need to do it manually
Click to expand...
Click to collapse
+1
Except I do clear the caches manually, but that's just because I have OCD.
CremeFraiche said:
i always flash back to eclair and master clear with odin one click to make sure all files from previous roms are gone then CWM flash new ROM
Click to expand...
Click to collapse
lets look at the master clear function shall we?
when you flash to stock...your entire / is stock (RFS, eclair 2.1, /data /system, etc)
essentially, you have just reformatted your root, think of it like formatting your C drive and your sdcard is like a secondary internal drive that contains storage
master clear at this point will only delete items off your /sdcard
roms dont care about your /sdcard, master clear is worthless when you are stock
there was a time where it was necessary to flash to stock to reset the filesystem and then flash the rom. it has not been needed in months, but it continues to get preached as gospel.
even flashing to stock isnt necessary unless you are trying to come from CM7 or MIUI....or if something goes horribly wrong
Thx for info guys, I have flashed a few times and it seemed like now and then my fone must became bogged down and needed to be fully wiped, sound didnt work or lagfix folders bunch of text docs, just seemed cluttered. So if wanted to really clear out junk what would be a good way without having to flash back to stock?
Sent from my SAMSUNG-SGH-I897 using XDA App
Just flash. If you have a problem then back to stock Ans a MC. I have flashed hundreds of time back to stock once.
Sent from my SGH-I897 using XDA Premium App
Pirateghost said:
lets look at the master clear function shall we?
when you flash to stock...your entire / is stock (RFS, eclair 2.1, /data /system, etc)
essentially, you have just reformatted your root, think of it like formatting your C drive and your sdcard is like a secondary internal drive that contains storage
master clear at this point will only delete items off your /sdcard
roms dont care about your /sdcard, master clear is worthless when you are stock
there was a time where it was necessary to flash to stock to reset the filesystem and then flash the rom. it has not been needed in months, but it continues to get preached as gospel.
even flashing to stock isnt necessary unless you are trying to come from CM7 or MIUI....or if something goes horribly wrong
Click to expand...
Click to collapse
I would definitely agree. I have also seen people say to disable lagfix before flashing. I have not done that either and never had any problem.
Would just like to amend the advice already given with the following:
Pre-flashing:
1. Titanium Backup of apps and data
2. Nandroid backup in case something goes boom.
Post-flashing (assuming success):
TB restore of user apps/data only. NEVER RESTORE SYSTEM FILES.
They may not apply to some people, but I feel those are necessary steps for anyone that actually uses their phone daily.
modest_mandroid said:
Would just like to amend the advice already given with the following:
Pre-flashing:
1. Titanium Backup of apps and data
2. Nandroid backup in case something goes boom.
Post-flashing (assuming success):
TB restore of user apps/data only. NEVER RESTORE SYSTEM FILES.
They may not apply to some people, but I feel those are necessary steps for anyone that actually uses their phone daily.
Click to expand...
Click to collapse
why not restore system files? Does this apply if coming from flashing back to stock first, or just flashing from one rom to another?
Glad to hear the advice about not flashing back to stock, that's been one of the major reasons I haven't flashed quite as many rom's as I want, too time consuming.........not to say that i'm not flashing a couple rom's a week, but there's just so many options to try
neophile said:
why not restore system files? Does this apply if coming from flashing back to stock first, or just flashing from one rom to another?
Click to expand...
Click to collapse
Making "search" a standard practice would be very helpful.
Restoring system is known to mess up ROMs in all cases. Though may not be mandatory, but make it a standard practice to flash stock. Takes hardly 10 mins, and helps save big headaches later.
neophile said:
why not restore system files? Does this apply if coming from flashing back to stock first, or just flashing from one rom to another?
Click to expand...
Click to collapse
Incompatibilities across rom versions, mostly. As the guy above me said, restoring system files tends to mess up a rom because you are overwriting part of it with files from a different rom.
There is one caveat, however. If you're flashing back to a rom you originally performed the backup on, you can safely restore system files. For example, if you were running Cog 4.3 and did a full TB backup, then decided to flash Serendipity 6.3, you would want to restore only your user apps and user data. However, if you decided to flash back to Cog 4.3 at some point, you could do a full TB restore without worrying about incompatibilities.
I agree with everyone else. Flashing over another rom seldom causes issues. I make s nandroid backup of my favorite rom with everything setup the way i like it. then flash away trying different roms. When i am done, i just restore my backup and all is good!
I have done a search, couldn't find the specific answer I needed, hence my asking. Could be I wasn't phrasing the search correctly......but here I am.....
To clarify, what do you dpo to get your system settings back after flashing a new rom? I flashed to serendipty 6.4 last night, as per the advice, I didn't restore system files, just apps and data, but that didn't work so well for me. I lost my data connection, could only use my wifi, and had no contacts, or any sms msgs. I don't know what else was missing, but I then went and restored system files, everything came back as needed, and there seems to be no issue......
How do I get my info setting back, or do I just need to manually re-set everything after flashing? Apart from wireless info, msgs and contacts, what else do you lose by not restoring?
Appreciate your help
havent flashed a new rom in a while and forgot if anything extra was needed when flashing a rom over a rom
thx!

[Q] galaxy i9000 looping at bootup.. not getting past the glowing S

I have recently flashed the JVS firmware from samsung firmware, and then followed that up with this CF-Root-XX_OXA_JVS-v4.1-CWM3RFS, flashing via the PDA section in ODIN. My phone has been working perfectly for a few days, no problems at all, until right now when I've gone to restart the phone.. I was having troubles with the market, and I turned my phone off mid-download of an app.. I'm pretty sure it was mid-download and not mid-installation of it..
However, when I turn my phone back on, it'll show the Galaxy S I9000 screen, then go to the next screen with the glowing S, however after that, it just gives a quick, short vibration, and seems to turn off, then do it all over again..
What does this mean? Is there a way I can get out of it without re-flashing the entire firmware? I am still able to get into download mode, but I don't want to lose messages that I have saved on my phone..
Any help is greatly appreciated..
Denno
Ok, so I let the phone go for a while (around 10 minutes), of the screens cycling through as mentioned above, but now it seems to have actually found a way into the phone, and has now loaded up properly.. However, I'm still interested in what the problem could be on the phone??
are u using new market app?
its happened to me once and i reflashed whole firmware starting from 2.1 to 2.3.5 lol just to avoid sh*t like that
When I had 2.2 on there, I had the new market app, however after flashing 2.3.5, it had the old market, so I was downloading apps from the old market at the time..
What do you mean you re-flashed whole firmware from 2.1?
Anyone else have any ideas?
Try to wipe factory reset and wipe cache or try to flash rom again
Wysłano z GT-I9000 z użyciem Tapatalk
Could be a corruption in the bootloader, if it happens again i would reflash. Otherwise just leave it i guess, maybe it was a one off
It happens pretty much all the time now.. I have reflashed the firmware a couple of times.. And it still seems to happen. What would wiping the cache remove? Will I lose any settings or anything that I have on the phone? I have been restoring backups made using titanium, however just apps and data, not system settings..
If it's the bootloader, is there any way of fixing that?
Thanks
Ah that could be the problem. Sometimes when you restore backup they can conflict and thus cause issues like this...
Try only return the data, that works for me. Get app list from the market and after a backup move to external sd. Format internal sd card. Then do an Odin flash with repartition checked. This is designed to get you back to factory state, so you will loose everything. Make sure your backups are not on your internal sd when you format. Also before you flash i think its a good idea to put a copy of your nandroid backup into the internal sd. Or just use a nandroid backup from when you phone was working fine.
Deleting cache does not delete your settings usually, however when deleting dalvick cache it can take up to 30 mins (max i think) to start you phone, but usually its 5/10 mins.
Yes bootloader can be fixed just find a flashable bootloader with a rom or the directions given. Use search for this
Ok thanks for the tips Talon.. Firstly, this nandroid backup that I keep hearing about.. What exactly is that? Is that the backup that I do through Clockwork Mod Recovery? I'm also unsure how to return just the data to apps? I had a look at Titanium Backup, and the only data recovery option is for system data.. Everything else I think I can handle..
Thanks
Yes nandroid backup is the backup through CWM. You should always do one BEFORE you flash anything on your phone. And keep them in a safe place and leave one in your internal sd card.
You should use titanium backup to backup up a single app at a time, not batch. This way you'll have more files and can choose which apps you want to return, and if you only want to return the data. (I have always done it this way, so i dont know if you can pick the apps you want to return if you do backup via batch.). Use the other app i suggested to keep the market links, so you download the app from market first then you install the data once its there.
I suggest you don't return any apps at first see how it goes, then add either a couple or one at a time, again only the app data. (Once you backuo the app individually, flash then, TB, backup/restore press on the app, restore, then pick data only...) If you go from froyo to GB i think you cant do it)
Thank you very much for your reply Talon. I am currently on JVS, and plan to re-flash this exact same firmware, which is the stock firmware, nothing custom..
As for what you've written, it's going to take me a few reads before I can get my head around it, but I just wanted to say thankyou for a quick and detailed reply. I think I might just bite the bullet and figure out which apps I actually use, and just work with them for now..
I'll post back soon hopefully with results.
After getting very frustrated with the phone, I've finally re-flashed back to a seemingly stock situation. Phone is running great, and all problems seem to be gone. Slowly re-downloading apps from the market as I feel that I need them, so I hopefully won't get any interference from the old backups I had..
One more question, how do you make your backups? If you say you don't use the batch mode in Titanium? I can't see any other way that's as easy..
Thanks for your help Talon.
As i said before, backup/restore click on the app you want to back up, and click backup. When you want to restore it, back to the menu, click on the app, click restore, then pick data only longer but safer
Change the location of TB to your exsd if you haven't already, then go to setting find, and it will make it default location
Ahk.. Sounds very time consuming.. lol..
Phone is running like a champ now . Thanks

[Q] A NON-wipe ICS rom?

Is there such a rom? I've checked teamhacksung's CM9 Alpha, Doc's Master ICS, Team ICSSGS, Fusion, and WeUI v0.6.6, and they all say to do a full wipe. Performed a search here and Google for any answers, but didn't find any.
I'm currently running Gingerbread 2.3.5 with Corn kernel, and when I upgraded from Froyo, I performed a full wipe. As many of you know, putting everything back on your phone is a major pain if you do not do a proper backup (I thought I backed up everything using Titanium, but apparently I didn't). Anyway, just curious if there is an ICS rom with a non-wipe option (or a super-cool, full of eye-candy Gingerbread rom with non-wipe).
Oh yeah, is Passion v13 Captivate-flashable? Thanks for any info you may have.
aicirt17 said:
Is there such a rom? I've checked teamhacksung's CM9 Alpha, Doc's Master ICS, Team ICSSGS, Fusion, and WeUI v0.6.6, and they all say to do a full wipe. Performed a search here and Google for any answers, but didn't find any.
I'm currently running Gingerbread 2.3.5 with Corn kernel, and when I upgraded from Froyo, I performed a full wipe. As many of you know, putting everything back on your phone is a major pain if you do not do a proper backup (I thought I backed up everything using Titanium, but apparently I didn't). Anyway, just curious if there is an ICS rom with a non-wipe option (or a super-cool, full of eye-candy Gingerbread rom with non-wipe).
Oh yeah, is Passion v13 Captivate-flashable? Thanks for any info you may have.
Click to expand...
Click to collapse
You need to do a full wipe on your phone since you're coming from a Gingerbread ROM. You may not delete what's on your sdcard if you want to retain it but as for apps, it will be deleted and so are your contacts, messages, etc.
Yuck. Okay, I figured as much, I was just hoping So, a Nandroid back-up is best, right? NOT Titanium?
aicirt17 said:
Yuck. Okay, I figured as much, I was just hoping So, a Nandroid back-up is best, right? NOT Titanium?
Click to expand...
Click to collapse
Yes, Nandroid back-up is good. You could do Titanium Backup as well but a fresh install of the apps would be better. I'm not sure it would work if you backed-up the apps from Gingerbread and install it on ICS, but you could try one app and test it.
aicirt17 said:
Yuck. Okay, I figured as much, I was just hoping So, a Nandroid back-up is best, right? NOT Titanium?
Click to expand...
Click to collapse
You can do a A Nandroid, but don't try restoring that on ICS or you will most likely cause a metric ton of problems. Titanium would be the best way to back up and restore your apps and app data. NEVER restore system data.
mrhaley30705 said:
You can do a A Nandroid, but don't try restoring that on ICS or you will most likely cause a metric ton of problems. Titanium would be the best way to back up and restore your apps and app data. NEVER restore system data.
Click to expand...
Click to collapse
Yep, forgot to mention that. Just backup your Apps and not your System Data.
Okay, wow, all the reading that I have done and I did NOT know that. No system data. Got it. Thank you both!
CM9 builds when upgrading from previous CM9 builds don't need a full wipe... I'm sure the others are the same... So won't be so bad unless you go between them all...
If you are so concerned with keeping your data and not wanting to go through the "pain" of resetting all your apps and such, you should stay with what you have. Instead, use a launcher with ICS themes to get the look of the ICS.
If you can take some pain and make the jump though, ICS offers a way more slicker OS for your Cappy.
Do not use Nandroid backup to restore your apps... TIBU is the one to use! As others said, the best way is to do a fresh (from the market) reinstall of all your apps and then use TIBU to restore your data for those specific apps only...
Edit: Concider this though while you are looking to upgrade. Most of these ICS roms are in beta stage... this means some bugs and other inconveniences... mind you they are minor but they exist. As the devs get these bugs and other issues addressed and update their roms, they would often require a fresh install (full wipe) to ensure best performance. This means that you will have to occasionally do a full wipe of your phone. It's fun to see the latest and greatest the devs have to offer but it also means that you have to do some "hard" work to enjoy the fruits of their labor... just something for you to think about...
I did not see it mentioned so I'll add. Every ROM that has a "no wipe" update is such because it is only a minor update to the existing ROM and not the whole. Even trying to do so results is a miss match of files and programs so at best you'll get FCs all over there place, at worst bootloops.
ICS, is a huge set of changes, including things google merged or removed. So the data from an app on an older version of android would be trying to send/receive info from a program that does not exist anymore and upon not getting what it wants would FC.
If you don't like having to restore everything, then wait from ICS until you see a few no wipe updates. Aside from SGSICS (since it is pure ASOP, and least likely to have any major changes) they all have a fair amount of developing yet to be done.
Now to the question of which type of backup . A nandroid backup is meant to restore your phone to it's current state (minus any partition changes). Tibu is designed for something like ROM hoping, so it only saves apps and their data. To illustrate an example of how to use both: 1 make backups, 2 load ICS ROM, 3 Tibu restore user apps (and user data only), 4 toy with ROM (be it a few hours or days), 5 you don't like it and want to go back, 6 Odin/Heimdall back to GB (to fix partition sizes), 7 restore nandroid and it's like your trip to ICS never happened.
leaked from my ICS- FUSED SGS I897 contaminating you via XDA app.
cvcduty said:
If you are so concerned with keeping your data and not wanting to go through the "pain" of resetting all your apps and such, you should stay with what you have. Instead, use a launcher with ICS themes to get the look of the ICS.
If you can take some pain and make the jump though, ICS offers a way more slicker OS for your Cappy.
Do not use Nandroid backup to restore your apps... TIBU is the one to use! As others said, the best way is to do a fresh (from the market) reinstall of all your apps and then use TIBU to restore your data for those specific apps only...
Edit: Concider this though while you are looking to upgrade. Most of these ICS roms are in beta stage... this means some bugs and other inconveniences... mind you they are minor but they exist. As the devs get these bugs and other issues addressed and update their roms, they would often require a fresh install (full wipe) to ensure best performance. This means that you will have to occasionally do a full wipe of your phone. It's fun to see the latest and greatest the devs have to offer but it also means that you have to do some "hard" work to enjoy the fruits of their labor... just something for you to think about...
Click to expand...
Click to collapse
Cvcduty, you're right about enjoying the fruits of the other devs' labor. If they're willing to put in all that hard work just to keep our Captivates as updated as possible, then the very least I can do is go through 5 minutes of work to flash the roms correctly and in the way the devs intended, and not look for an easier way. I have flashed a couple of times before, I'm just not completely comfortable doing it. But I almost there!
DaNaRkI said:
I did not see it mentioned so I'll add. Every ROM that has a "no wipe" update is such because it is only a minor update to the existing ROM and not the whole. Even trying to do so results is a miss match of files and programs so at best you'll get FCs all over there place, at worst bootloops.
ICS, is a huge set of changes, including things google merged or removed. So the data from an app on an older version of android would be trying to send/receive info from a program that does not exist anymore and upon not getting what it wants would FC.
If you don't like having to restore everything, then wait from ICS until you see a few no wipe updates. Aside from SGSICS (since it is pure ASOP, and least likely to have any major changes) they all have a fair amount of developing yet to be done.
Now to the question of which type of backup . A nandroid backup is meant to restore your phone to it's current state (minus any partition changes). Tibu is designed for something like ROM hoping, so it only saves apps and their data. To illustrate an example of how to use both: 1 make backups, 2 load ICS ROM, 3 Tibu restore user apps (and user data only), 4 toy with ROM (be it a few hours or days), 5 you don't like it and want to go back, 6 Odin/Heimdall back to GB (to fix partition sizes), 7 restore nandroid and it's like your trip to ICS never happened.
leaked from my ICS- FUSED SGS I897 contaminating you via XDA app.
Click to expand...
Click to collapse
DaNaRkI, it's not that I don't like to restore everything (even though that's what I said), it's more like even though I have flashed a couple of times already, I'm still a little uncomfortable doing it. And I have read, I mean read for hours before I took my first step, but it seems like the more I read, I keep finding more new stuff that I probably should have known to start with. Take Nandroid and Tibu for example, I thought they worked exactly the same, but now I know, thanks to you, that there is a BIG difference. AND I learned yesterday (reading somewhere on here) to never ever restore "system data". It's a lot to keep up with if you're a blonde
Thank you for taking the time to explain, it helped a lot!

[Q] OTA Update and Safestrap Clarification

Hello all,
I've been running Eclipse 2.2 on 902 for some time and I've stubbornly refused to switch away from using bootstrap for all my backup needs, however, after reading enough about it I decided to give safestrap a try. I've had a little trouble with the process however and was looking for a little clarity...
My understanding with safestrap was that in addition to giving me a safe (technically unsafe) 2nd partition/access to recovery in case I messed something up, that it would also pretty easily transfer data, apps, etc from one partition to the next, making flashing roms (and I thought updating) much easier and quicker without needing to backup individual portions of my system, Is this correct or am I mistaken?
Onward to what I did (my goal is to update to 905 and install eclipse 3.0) - Installed safestrap, backed up safe and unsafe side. I then went to unsafe and used bootstrap to restore to IMMEDIATELY after I applied the 902 update (had backed it up previously). This backup was literally a stock Bionic which I had updated from 886 all the way to 902, rooted, then installed bootstrap to backup. I then updated this to 905 with no issue, and of course backed it up... From here, my understanding was that I could simply swap over to safe side, then install the eclipse 3.0 through finding a zip in recovery - Recovery would not do this for me. It gave me an error similar to "cannot apply eclipse3.0.zip (bad)"
I tried to push the ROM both without making any changes (just switching from unsafe to safe and immediately trying to apply the zip) and when that didn't work I wiped data, formatted system, and wiped cache/dalvik and got the same error. (the net result through all of this was making my safe side non-responsive, and me ending up restoring safe side system to the initial backup I had made about 30 minutes prior).
Is this working as intended? Should I look at safestrap as purely an extra failsafe to keep me from bricking my phone and not an easier method to flash/update? If I have to expect that I need to go to safe, follow the same path to apply the update as I did on unsafe, then flash 3.0 and restore with titaniumbackup, sms/call log backup, etc, I will, but I just wanted to make sure I'm not misunderstanding something with safestrap that may allow me to make this whole process easier - I'd be much more interested in trying out a variety of ROMs if the restoring of my data wasn't such a hassle when I did it.
Sorry for the long post - I'm long winded and also wanted to get all of the information out there for anyone who may answer.
Thanks in advance!
-Jamie
Guess I was too wordy and nobody wants to read it (or posted in the wrong spot maybe) -
tldr:
Is there a way to use safestrap as having a way to easily transfer data etc from one rom/update to the next? or should I be using it solely to have an extra backup to prevent me from bricking my phone, and just do the longer more arduous methods of restoring data and settings after a rom swap/update?
I'm no expert but I have successfully used Safestrap, installed eclipse 3.0 as well as tried other roms and themes, and have other Android experience as well. Sounded like you may have used bootstrap and Safestrap at the same time. Am I wrong? If not, from my understanding that is a no no. Uninstall bootstrap completely and use Safestrap only. I also upgraded my "unsafe" system to .905 via OTA before attempting 3.0. My first experience with Safestrap, however, was not entirely positive either. I think my download was corrupt because it stopped working correctly. I downloaded again and haven't had any problems since. I followed this guide http://forum.xda-developers.com/showthread.php?t=1455888 and it worked. He's not really all that clear at times. It's also not necessary to factory reset after flashing a new rom. Always do it, but it can be done before too. I always do it before and have no problems. Also if you decide to apply a theme make sure you boot up the new ROM before flashing the theme. This guide was not entirely clear on that and it got stuck in a wicked boot loop that ended with me on stock and Safestrap gone. Keep trying. Hope some of this helped. I'm wordy too
Sent from my Galaxy Nexus using xda app-developers app
Btw, to answer your first question, the best way I've found to transfer user apps from ROM to ROM is with titanium backup. Other data will still be on your sd cards and accessible to the new ROM. I never use titanium to restore system settings and most system apps though. Things tend to get messed up if you try to do this from one rom to another. System apps can be converted to user apps with titanium which is cool then backed up and restored to new ROM. And never restore Google play app with titanium. Some go so far as to say don't restore apps with data but I haven't had any trouble except with core google apps like play, gmail, voice. Usually flash gapps if I have to and restore other core Google apps directly from play store. Sometimes titanium "hangs" on some apps. Not to much trouble with it lately maybe it's fixed used to be a PIA though.Sorry there's still plenty of setup involved any time you want to "dial in" a new ROM.
Sent from my Galaxy Nexus using xda app-developers app
Thanks G-diddy,
To clarify, I knew bootstrap and safestrap didn't play well together. That being said, I did NOT use safestrap to try and restore to a bootstrap backup. I installed safestrap, then swapped to my UNSAFE side, then restored to a previous bootstrap backup (using bootstrap), then OTAd to .905. I then backed up this fresh near stock but rooted .905 with safestrap (thus should never have to use bootstrap ever again). I then tried to swap over to safe and push eclipse 3.0 but had no success... At present my phone has near stock but rooted .905 on my unsafe side, and the same .902 with 2.2 eclipse on my safe side that I've been running for months...
I guess I have no choice but to restore my present safe side to the old bootstrap backup, then manually ota, then install the rom, I just thought that Safestrap would make all of this process easier - in as much as since my unsafe side is successfully updated, I was hoping my safe side would be too, making the process somewhat simpler. Sounds like I'm wrong in this assumption though, unless someone else can say otherwise?
Thanks for the tip on Titanium Backup too, although I've been using the premium version of that for months now, ever since I decided I was going to turn my phone into a toy

Categories

Resources