Database Develop

[Q] Titanium backup not working after Froyo update

Updated my phone to the 2.2 JPM firmware successfully and then applied the root using the CF-Root v1.2 method. Everything working fine so far I applied the new Voodoo-5-pre6-Froyo fix and phone rebooted fine. Now I go to install Titanium backup and it requests root privileges which I confirm but it still says it cannot attain superuser privileges when attemping to run Titanium.
Anyone know what's up? I wouldn't mind getting my old apps back

Simply restart Titanium, happens to me all the time. Once restarted, it should work normally.
However, generally if you have come from a non-froyo ROM, it is recomended that you do not use Titanium to backup, due to the 2.1 system data causing a force closes.

I was looking for the button to thank you because I JUST had the exact same issue. Googled it and brought me here.
Thanks so much. I kept hesistating whether I wanted to try one of the froyo roms since it was taking FOREVER to get the official version and I was tired of waiting around.

@ coboltmarine
I want to flash my galaxy with Froyo (still have 2.1). Therefore I would like to backup my firmware first if something goes wrong so I can re-do everything. Since you said that backing up a non-froyo with titanium is not recommended, which one would you recommend? Do you know any posted thread which could help me in this?
Thanks a lot

[Q] on flashing rom to rooted phone

Hi all, I'm going to not try and sound too noobish, but after reading for hours I still have a couple questions. I have a Moto Droid with 2.2 Froyo that I just rooted. I use Rom Manager last night to put on Cyanogen but when it booted I had lost all apps, contacts, market so I reverted back to stock. I just got titanium backup pro which I read should load all my apps/contacts etc once I load Cyanogen? I just want to make sure I'm running the programs in the correct order.
One other issue I have is that I am currently using Setcpu to overclock to the max it's allowing which is 800 megahertz. Do I need to uninstall this before I load Cyanogen? Because I know that it is going to max me out at 600 unless I load another Kernal to go higher which I would like to do, which is another thing I was looking for instructions to do but having difficulty at least for my model.
I've found some P3 kernals, I'm not sure if theyre compatible with Cyanogen or how I would know which one to get though.
Any help is appreciated, I'm new to the rom stuff but learn fast.

oh man, I was hoping someone would know

anyone? please?

Allright well I've figured out which P3 kernel I am going to use. My latest issue is when I install Cyanogen, all my apps except for Rom Manager and Terminal Emulator are gone. Now I backed up everything with Titanium, but that is gone as well. It seems like a catch 22 to try and restore your apps and the restoring app itself is gone. Any ideas?

Go download titanium from the marketplace and reinstall. Your apps will then be able to be restored. I run cm 6.1 RC4 and use the P3droid 250/1100 MHz kernel. You'll also want to install setCPU from the marketplace to set the cpu speed profiles. Good luck! You'll really dig it once you have everything dialed in.
----
Sent From My AI using my own mediocre intelligence.

Hey Maxnicks, maybe you know the answer to this one as well:
I've only been using CM since 6.0 and I want to finally update it to 6.1 but just a few questions. As far as updating goes, do you have to wipe your data in Rom Manager like you would do going from stock to CM? 2nd, when you update, do you lose all your apps like you do going from stock to a new rom? I used titanium backup before to restore after 6.0, but this time I'm going to update the rom through Rom Manager so it's a little different. Last,I have the P3 Kernal overclocked, will this stay at my current settings or do I need to reinstall it after 6.1 is on there. Sorry for the questions but I tried googling and not much exists comparing CM update vs installing it over stock.

First make a back up of current rom in rom manager in case want/have to flash back. When updating same rom, might be able to get away without wiping, try without if any trouble with 6.1 flash back to previous then try a wipe. On kernel you will have to go into recovery to flash back to the p3 as all roms come with one, usually top out at 600/800 or so. Once flash new rom with gapps all apps should download thru market. I currently am running 6.1 with p3 125-1100 kernel with no problems other than usual launcher re-draw. Good luck
Sent from my Droid using XDA App

[how to] install rom to Bell XT860 without losing ability to return to stock

How to install a custom rom (eg. CM9, Ice Cream Sandwich, Liberty, Maverick, SteelDroid) to a Bell XT860 without losing the ability to revert to stock later.
Why this guide?
I noticed over time that my phone has become slower and more frustrating to use. For example, long pauses when trying to open a program - sometimes it takes an easy 10 or more seconds to open the dialer and dial a number.
I wanted to try a custom rom, but was concerned about the ability to get back to stock, if something goes wrong, or to be able to take advantage of a Bell update if they release a new one. Thanks to the hard work of many on this board, I have discovered how to make this possible and wanted to share with others.
Big thanks to DoomLord, HashCode, Enderoid, Rick#2, Dasilva333, Willis111 and others. Please feel free to make corrections to these instructions.
Note: This has been tested with an XT860 on Bell 2.3.6 firmware. This will probably NOT work on v2.3.4 So if you have 2.3.4, upgrade to 2.3.6 and then these instructions should work. When I first got the phone, it was at 2.3.5 and later was updated OTA (Over the air) by Bell to 2.3.6. To check which firmware you have, Home Screen / Settings / About Phone
Needed:
1. Windows pc (someone else more knowledgeable could probably tell you how to make this work on a Mac)
2. USB cable for connecting your phone.
3. Rooting tool, I highly recommend zergRush method by DoomLord found here:
http://forum.xda-developers.com/showthread.php?t=1321582
4. Safestrap by hashcode
http://hash-of-codes.blogspot.com/p/android-downloads.html
5. Custom rom of your choice.
Step 1:
Root your phone using the DoomLord tool. I used version 3. It was really easy, just follow the instructions on the link above.
Step 2:
Backup existing user programs that you might want to restore on a new system. I used Titanium Backup Pro but there are others.
Step 3:
Please read this page carefully
http://hash-of-codes.blogspot.com/p/how-to-safestrap.html to download and install safestrap v1.08. Note, you should remove any other type of bootstrap (eg. ClockworkMod, ROM Manager) before installing Safestrap.
Step 4:
Now you should be ready to download and try a custom rom. Make sure to do a backup (“Nandroid” backup) of your working system before you try a custom rom so you have something to fall back on in case something goes wrong or you want to return to stock.
Find a rom, download it and save it to a location on your sdcard or ext-sdcard. There’s lots of good candidates for you to test and a good thread with some reviews here:
http://forum.xda-developers.com/showthread.php?t=1384676
To do this, power down your phone after you have run safestrap and clicked to make recovery active. If you did it right, when you turn it on again, you should see a different splash screen that gives you a few seconds to enter the recovery menu by pressing the “menu” button on you device.
You should see “Safestrap Recovery v1.08” and below that “Safe System is: DISABLED”
on a black screen with some green menu choices.
Use the volume keys to scroll up/down and select “backup and restore” by pressing the power button.
The screen should change to show the Nandroid backup menu. You need to make a Nandroid backup of your existing (working) system, which is simply a snapshot of the exact system with all programs, settings, sms’s, call logs, etc. It’s like a snapshot in time in case you need to revert. Select “backup”, then select Internal or External SD Card for the location (I’m not sure it it matters for the location).
Safestrap will backup your system to a Nandroid backup. It takes a few minutes.
After the backup is complete, you can enable the Safe System where you will install custom roms. Scroll down and select “safe boot menu”, then “Toggle Safe System”, then on the next screen confirm your selection. It will backup the original system to a safe area where it can’t be modified (unless you are an advanced user and install a different version of Safestrap but that’s beyond the scope of these instructions).
After Safe System is: ENABLED, scroll down to “Install zip from sdcard”, select your rom, install, reboot and enjoy.
To revert back to your original system, follow these steps:
1. Turn off your phone and reboot into SafeStrap recovery menu.
2. Turn off SafeSystem. (Safe boot menu -> Toggle Safe System)
3. Restore your nandroid backup and reboot.
If you wanted to go further back to stock you could uninstall Safestrap and even unroot using DoomLord’s zergRush tool, which would put you back to stock.
I think that’s it. Hopefully this guide will be helpful to others who want to try a new rom without losing the ability to revert back to stock Bell.

ncho2233 said:
How to install a custom rom (eg. CM9, Ice Cream Sandwich, Liberty, Maverick, SteelDroid) to a Bell XT860 without losing the ability to revert to stock later.
Why this guide?
I noticed over time that my phone has become slower and more frustrating to use. For example, long pauses when trying to open a program - sometimes it takes an easy 10 or more seconds to open the dialer and dial a number.
I wanted to try a custom rom, but was concerned about the ability to get back to stock, if something goes wrong, or to be able to take advantage of a Bell update if they release a new one. Thanks to the hard work of many on this board, I have discovered how to make this possible and wanted to share with others.
Big thanks to DoomLord, HashCode, Enderoid, Rick#2, Dasilva333, Willis111 and others. Please feel free to make corrections to these instructions.
Note: This has been tested with an XT860 on Bell 2.3.6 firmware. This will probably NOT work on v2.3.4 So if you have 2.3.4, upgrade to 2.3.6 and then these instructions should work. When I first got the phone, it was at 2.3.5 and later was updated OTA (Over the air) by Bell to 2.3.6. To check which firmware you have, Home Screen / Settings / About Phone
Needed:
1. Windows pc (someone else more knowledgeable could probably tell you how to make this work on a Mac)
2. USB cable for connecting your phone.
3. Rooting tool, I highly recommend zergRush method by DoomLord found here:
http://forum.xda-developers.com/showthread.php?t=1321582
4. Safestrap by hashcode
http://hash-of-codes.blogspot.com/p/android-downloads.html
5. Custom rom of your choice.
Step 1:
Root your phone using the DoomLord tool. I used version 3. It was really easy, just follow the instructions on the link above.
Step 2:
Backup existing user programs that you might want to restore on a new system. I used Titanium Backup Pro but there are others.
Step 3:
Please read this page carefully
http://hash-of-codes.blogspot.com/p/how-to-safestrap.html to download and install safestrap v1.08. Note, you should remove any other type of bootstrap (eg. ClockworkMod, ROM Manager) before installing Safestrap.
Step 4:
Now you should be ready to download and try a custom rom. Make sure to do a backup (“Nandroid” backup) of your working system before you try a custom rom so you have something to fall back on in case something goes wrong or you want to return to stock.
Find a rom, download it and save it to a location on your sdcard or ext-sdcard. There’s lots of good candidates for you to test and a good thread with some reviews here:
http://forum.xda-developers.com/showthread.php?t=1384676
To do this, power down your phone after you have run safestrap and clicked to make recovery active. If you did it right, when you turn it on again, you should see a different splash screen that gives you a few seconds to enter the recovery menu by pressing the “menu” button on you device.
You should see “Safestrap Recovery v1.08” and below that “Safe System is: DISABLED”
on a black screen with some green menu choices.
Use the volume keys to scroll up/down and select “backup and restore” by pressing the power button.
The screen should change to show the Nandroid backup menu. You need to make a Nandroid backup of your existing (working) system, which is simply a snapshot of the exact system with all programs, settings, sms’s, call logs, etc. It’s like a snapshot in time in case you need to revert. Select “backup”, then select Internal or External SD Card for the location (I’m not sure it it matters for the location).
Safestrap will backup your system to a Nandroid backup. It takes a few minutes.
After the backup is complete, you can enable the Safe System where you will install custom roms. Scroll down and select “safe boot menu”, then “Toggle Safe System”, then on the next screen confirm your selection. It will backup the original system to a safe area where it can’t be modified (unless you are an advanced user and install a different version of Safestrap but that’s beyond the scope of these instructions).
After Safe System is: ENABLED, scroll down to “Install zip from sdcard”, select your rom, install, reboot and enjoy.
To revert back to your original system, follow these steps:
1. Turn off your phone and reboot into SafeStrap recovery menu.
2. Turn off SafeSystem. (Safe boot menu -> Toggle Safe System)
3. Restore your nandroid backup and reboot.
If you wanted to go further back to stock you could uninstall Safestrap and even unroot using DoomLord’s zergRush tool, which would put you back to stock.
I think that’s it. Hopefully this guide will be helpful to others who want to try a new rom without losing the ability to revert back to stock Bell.
Click to expand...
Click to collapse
Good writeup. As a note when your switch back to nonsafe you don't need to restore a nandroid. Actually with safestrap you should rarely have to restore a nandroid as its next to impossible to screw up your device so bad that a restore is required. The stock bell /system stays nice and untouched
Sent from my XT860 using xda premium

Dont you just root, install safestrap and flash paritions to preinstall from stock(to avoid not being able to return to true stock) and not flash the og /system? Obviously works on 2.3.4, 2.3.6 etc any rootable rom capable of running safestrap. You should be able to even use my rom to return to stock deodexed by flashing to /system(non-safe) and removing any custom recovery. It should be very easy to convert that or the og dumps into a system.img for use with rsdlite and even the rest of the stock img files. I'll take a look at it this aft. Thanks for the write up, hope some of this info helps.

Maybe this is the wrong place to ask, but XT860 threads are few and far between in this droid 3 section. But I've got a few questions about this method.
First off, how safe is this from start to finish? I'm by no means new at the whole installing custom roms thing, but there have most definitely been times on all three of the devices I've installed roms on (Nook Color, Milestone, Transformer) where I've gotten a non-booting device that was fixed either because it was so easy to just go into CWM or RSDlite and flash a new rom or revert to stock. Doing anything (I'm not even rooted yet) on my XT860 kind of scares me, because we don't have an sbf or anything. This method seems like its the closest thing we've got, but new things are scary.
Secondly, I read somewhere that ICS uses a different kernel than GB. Would this method be able to deal with that or are we boned (i.e. stuck with the GB kernel and hackarounds) until Moto randomly decides to unlock the bootloader and we can rewrite everything?
And lastly, we can root on bell now? Last time I'd looked into it, I seem to remember flashing firmware from another country and without an easy way to get back to stock, that kind of killed it for me.
Once again, sorry that some of this is kind of off topic, its just kind of hard to know where to read while we're piggybacking on the droid 3 forum.

Tyfighter said:
Maybe this is the wrong place to ask, but XT860 threads are few and far between in this droid 3 section. But I've got a few questions about this method.
First off, how safe is this from start to finish? I'm by no means new at the whole installing custom roms thing, but there have most definitely been times on all three of the devices I've installed roms on (Nook Color, Milestone, Transformer) where I've gotten a non-booting device that was fixed either because it was so easy to just go into CWM or RSDlite and flash a new rom or revert to stock. Doing anything (I'm not even rooted yet) on my XT860 kind of scares me, because we don't have an sbf or anything. This method seems like its the closest thing we've got, but new things are scary.
Secondly, I read somewhere that ICS uses a different kernel than GB. Would this method be able to deal with that or are we boned (i.e. stuck with the GB kernel and hackarounds) until Moto randomly decides to unlock the bootloader and we can rewrite everything?
And lastly, we can root on bell now? Last time I'd looked into it, I seem to remember flashing firmware from another country and without an easy way to get back to stock, that kind of killed it for me.
Once again, sorry that some of this is kind of off topic, its just kind of hard to know where to read while we're piggybacking on the droid 3 forum.
Click to expand...
Click to collapse
Yes we can root, there is no need to flash any other countries fastboot files as long as you are on bell 2.3.6. While bell doesn't have a fastboot package yet(sbf) if you borked your device you can use motofastboot to flash just /system from the fastboot package of another country, and then restore a backup, thus everything stays bell stock.
The best advice is to use safestrap and only flash the safemode. You should always be able to get into CWR with safestrap
And yes we are stuck with the GB kernel for now, which is part of the reason developing ics roms has been so painful
Sent from my XT860 using xda premium

This process does not work for me...
When I load SafeStrap 1.08, I get Recovery State: Not Installed
I try and click the "Install Recovery" button and it goes through a process (preparing something, obtaining root, etc) but the Recovery State never changes
I have an XT860 from Bell (2.3.6) that is running on Rogers (unlocked).
Root works fine for TiBu and Root Explorer....The SuperUser entry for SafeStrap lists allowed and logs a whole bunch of "granted".
Any thoughts?

Caz666 said:
This process does not work for me...
When I load SafeStrap 1.08, I get Recovery State: Not Installed
I try and click the "Install Recovery" button and it goes through a process (preparing something, obtaining root, etc) but the Recovery State never changes
I have an XT860 from Bell (2.3.6) that is running on Rogers (unlocked).
Root works fine for TiBu and Root Explorer....The SuperUser entry for SafeStrap lists allowed and logs a whole bunch of "granted".
Any thoughts?
Click to expand...
Click to collapse
Perhaps you don't have su binary properly installed. I've had this happen with bootstrap. Check that you have su in both /system/bin and /system/xbin
Sent from my XT860 using xda premium

Close...it was busybox. It was present, but borked. Nuked and reloaded..problem fixed.
Many thanks to hashcode for the pointer to busybox being most likely.
Sent from my XT860 using xda premium

Caz666 said:
Close...it was busybox. It was present, but borked. Nuked and reloaded..problem fixed.
Many thanks to hashcode for the pointer to busybox being most likely.
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Now that you say that I remember someone else having the same issue and it turned out to be busybox. I had nearly the same problem with the bootstrap and it ended up being su missing from xbin
Sent from my XT860 using xda premium

OK I tried this and it works perfectly. Thanks man. This is what I needed.

Finally got around to trying this. I'd been in the middle of a move with my pc in a box, but now I've got ICS fully up and running (save for the whole camera thing). Panicked halfway through when I got into a bootloop, but then I wiped everything (forgot the cache the first time) and then everything worked.
I got wifi tether working with the app that was included in the rom, but have any of you had any luck with doing it natively through the settings? I only ask because being able to trigger it from the status bar would be pretty sweet.
edit: did some looking around and it looks like maybe its an issue with shoehorning GSM into a CDMA rom. At least that's the feel I've been getting, I'd love to be wrong.

Thanks for this thread! I hadn't realized there had been developments for the XT-860.
I had unlocked (for use on the Fido network)/rooted my phone and it was working great, then the OTA update from Bell came and I installed that. Now, I seem to have lost root privileges (I guess, obviously).
So, I guess I'm pretty much back to square one.
I would love some advice on how to proceed! I'm thinking of following your directions, and am interested in recommendations for which ROM to install.
What is the problem with the camera with ICS? I use the camera on our phone pretty often so I want a ROM that doesn't break it. Does anyone have some links to some good ROMs to try that work with the XT-860?

twitchcity said:
Thanks for this thread! I hadn't realized there had been developments for the XT-860.
I had unlocked (for use on the Fido network)/rooted my phone and it was working great, then the OTA update from Bell came and I installed that. Now, I seem to have lost root privileges (I guess, obviously).
So, I guess I'm pretty much back to square one.
I would love some advice on how to proceed! I'm thinking of following your directions, and am interested in recommendations for which ROM to install.
What is the problem with the camera with ICS? I use the camera on our phone pretty often so I want a ROM that doesn't break it. Does anyone have some links to some good ROMs to try that work with the XT-860?
Click to expand...
Click to collapse
Use zergrush to root 2.3.6. Picture camera works in ics but you can't record or view video. There's some good gb roms. Give me a few and il shoot you some links
Sent from my XT860 using xda premium

Starting the process now. Can someone please send me a link or two to a good ROM for the XT-860?
I would prefer ICS (I want Chrome on my phone), but if that causes to many problems, a GB recommendation would be fine.

Bell SBF available at the following URL:
http://sbf.droid-developers.org/umts_solana/list.php

ncho2233 said:
How to install a custom rom (eg. CM9, Ice Cream Sandwich, Liberty, Maverick, SteelDroid) to a Bell XT860 without losing the ability to revert to stock later.
Click to expand...
Click to collapse
If there was any interest at all I would have just made a 100% stock bell 2.3.6 that you flash with CWM and then remove the recovery to be 100% stock but the deodex version seems to be good enough, especially to get a phone with a physical problem past bell/motorola reps. I'm downloading and mirroring that bell sbf right now, very nice find pfak! I made a new thread since you didn't but just linked to your post.
twitchcity said:
Starting the process now. Can someone please send me a link or two to a good ROM for the XT-860?
I would prefer ICS (I want Chrome on my phone), but if that causes to many problems, a GB recommendation would be fine.
Click to expand...
Click to collapse
There are many roms on this part of the sub-forum, just look around or try a search with [ROM] as your query (might not work so hot in the d3 dev subforum )
I

twitchcity said:
Starting the process now. Can someone please send me a link or two to a good ROM for the XT-860?
I would prefer ICS (I want Chrome on my phone), but if that causes to many problems, a GB recommendation would be fine.
Click to expand...
Click to collapse
Willis111 said:
If there was any interest at all I would have just made a 100% stock bell 2.3.6 that you flash with CWM and then remove the recovery to be 100% stock but the deodex version seems to be good enough, especially to get a phone with a physical problem past bell/motorola reps. I'm downloading and mirroring that bell sbf right now, very nice find pfak! I made a new thread since you didn't but just linked to your post.
There are many roms on this part of the sub-forum, just look around or try a search with [ROM] as your query (might not work so hot in the d3 dev subforum )
I
Click to expand...
Click to collapse
I have a number of xt860 adapted roms on my computer. Give me a few days to contact the devs and such and I'll see if I can get a stickied thread with xt860 ready roms to make it easy for new comers. Also willis, ignore my other post to you, I'll include that info in aforementioned thread if I can get it going
Sent from my GT-P5113 using xda premium

Endoroid said:
I have a number of xt860 adapted roms on my computer. Give me a few days to contact the devs and such and I'll see if I can get a stickied thread with xt860 ready roms to make it easy for new comers. Also willis, ignore my other post to you, I'll include that info in aforementioned thread if I can get it going
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
You can just use one of the patches (small xt860 patches) to get any rom working on our phones as far as I know.

pfak said:
Bell SBF available at the following URL:
http://sbf.droid-developers.org/umts_solana/list.php
Click to expand...
Click to collapse
thank you for this it will help a ton of peeps

[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

I just cannot do a nandroid backup - help pls

Am on criskelo 11.2 with speedmod kernel 3.13.
All is fine, it appears I have root (titanium etc works) and a check with 'got root' returns an ok response.
The phone is behaving itself nicely and is nice and smooth.
The problem comes when I try and do a nandroid backup using cwm.
It gets a liitle way in and then freezes (forever!)
Things I've tried to cure this...
1) Rolling back to stock GB and then re-rooting, then full 3 wipes, then reinstall criskelo rom.
2) Rolling back to a pre-rooted GB rom, then all 3 wipes, then re-install croskelo
2) Flashing other kernels, notecore etc
3) Installing superuser 3.1.1.zip with cwm and its binary update.zip
4) Installing SuperSU app from play store - it says needs to update binaries, and when I try it just says 'installation failed!'
5) Installing superuser app from play, this time when I try and update binaries it does helpfully say ' remounting /system as rw... fail!'
which leads me to believe this is a root problem, even though no other app is complaining.
6) doing a search on this forum (before you all tell me to do this!)
I have been trying to solve this for over a week now, and it feels like I have read everything on this forum but I may have missed something.
Can anybody steer me in the right direction please?

Maybe you dont need a nandroid backup, it doesnt backup efs anyway.
Could be a kernel issue, or space issue. Not sure.
Sent from my GT-N7000 using Tapatalk 2

baz77 said:
Maybe you dont need a nandroid backup, it doesnt backup efs anyway.
Could be a kernel issue, or space issue. Not sure.
Click to expand...
Click to collapse
Cheers, you might be right, but I have always used nandroid before flashing a new rom,
may I ask what you use to backup then, when you change rom?

jonnybruce said:
Cheers, you might be right, but I have always used nandroid before flashing a new rom,
may I ask what you use to backup then, when you change rom?
Click to expand...
Click to collapse
Have you tried updating cwm? I believe older versions had this problem.
Sent from my GT-N7000 using xda premium

SpyderTracks said:
Have you tried updating cwm? I believe older versions had this problem.
Click to expand...
Click to collapse
No I haven't Spyder, although I have tried a few different roms whic all have differing versions of cwm right?
which one is the latest then, and how do I install it, would it be an update zip?

jonnybruce said:
Cheers, you might be right, but I have always used nandroid before flashing a new rom,
may I ask what you use to backup then, when you change rom?
Click to expand...
Click to collapse
I am a heavy flasher and prevent issues caused by restores to get a clean taste of roms. Nandroids I tried, but I havent found a rom I wanted to go back on always, flash so much that it just takes to long.
Efs with a tool in one if my threads, suggestion by Chasmodo. DrKetan has a good toolbox thread in general section.
I manually backup photos and such with a file explorer. Calander/Contacts/email in gmail,
whatsapp and special app stuff also manually transfer folder from sdcard and back.
Messages I dont care for. Neither made calls list.
Occasionally I do restore app if dissapeared from market with Titanium, but only app, not data. I save backups on external. Cause I clean sdcard also.
Sent from my GT-N7000 using Tapatalk 2

jonnybruce said:
No I haven't Spyder, although I have tried a few different roms whic all have differing versions of cwm right?
which one is the latest then, and how do I install it, would it be an update zip?
Click to expand...
Click to collapse
The latest version for Note N7K is 6.0.1.2.. chek the below link... download option is there
http://www.clockworkmod.com/rommanager/

jonny, i feel your problem is due to partial root.
could you copy files into system in root explorer ?
did adaway work in applying hosts file ?
for criskelo rom too you should choose CF root kernel during the flashing process, then later you may change to your preference

Thanks baz & nokia, much appreciated.
I am running PA 1.99 now and it has the new cwm (you can tell because it has a grey background now!)
And rraaka, you are correct, I cannot copy anything to system
Not sure how I can get full root back though, I have used Dr Ketans rooting tool many times to try and cure this issue as well as flashing pre-rooted GB roms with Odin.
Not sure what else I can do.
But am starting to agree with baz now, I can do without nandroid (it takes ages anyway) and just use titanium to restore.
Everything is working fine with my partial root (except nandroid) anyway so not sure I care anymore!
Am enjoying Paranoid Android by the way, JB is fun.
I do miss the samsung apps though, I don't suppose those have been jellybeaned yet??

nope not yet, nothing Touchwizz like spen etc.
There is a cwm flashable of samsung apps that works pretty good on cm9, not sure if it works on cm10 or jb.
gaining full root shouldnt be to difficult, update binaries and then you know for sure.
The one that has worked wel for me is the ssu only zip from this post but then again thats on stock stuff.
http://forum.xda-developers.com/showthread.php?t=1841288
For custom roms/kernels the ones supplied with it are build in to work out of the box.
Once fully clean install, a nandroid can work but thats fully clean
Sent from my GT-N7000 using Tapatalk 2

Thanks baz, am going to go back to the start (stock ICS) and try that link to try and get my full root back, looks interesting.

Ok, I have full root again now!
here's what I think I remember what I did...
Downloaded the first two Su & busybox zips using method1 on the link that Baz kindly shared with me and popped them on my sd card ready.
http://forum.xda-developers.com/showthread.php?t=1746794
Downloaded and flashed the latest UK Carphone Warehouse stock ICS rom with odin.
Rebooted to stock recovery - applied update zip - flashed first the SU and then Busybox zips downloaded earlier.
Rebooted phone to check all was ok.
Located superSU app and ran it to check - and first it said it didn't recognise my phone model, hmmm...
So I downloaded mobile odin from play and flashed abyss 4.2 kernel
Rebooted to recovery, full 3 wipes and rebooted system.
Ran superSU again and magically it updated binaries and for the first time in 2 weeks it said 'sucessful', I was very pleased!
Rebooted to recovery and flashed Criskelo 11.2 again (have gone back to this from PA until things are a bit more stable)
Restored all my apps from TB all good.
Checked Adaway and it was more than happy to replace host file, and root explorer is also happy.
Cool