Database Users

Titanium Backup FC

I have rooted my Vibrant but when i try to back up my apps, titanium back fc's anyone else having this issue?

Yes i'm having the same problem also...wonder if there's a possible fix for this.

Can anyone else confirm that titanium backup is not working?
I sent the developer my logcat. hopefully he can resolve this issue...

I am also having force close issues. Can usually restore an app or two then it force closes on me.

Broken for me too.
Sent from my SGH-T959 using XDA App

I was able to do a backup, but the odd thing is none of my apps showed up at all. Just system settings. But no FC's.

would one of you take a logcat and post it. I will then proceed to send to the developer to see if we can get this fixed.

i have been working w/ the dev, i can confirm this is fixed and i assume there will be an update soon.
EDIT: attached the patched 3.3.0 version.

Awesome news, I had the same problems!

Hi everyone,
I don't own a Samsung phone so thanks a lot for your help in solving this.
The bug-fixed version 3.3.1 is released on the Market, and backups should work fine now.
I'll be adding more Samsung love in the future
Have a great Sunday !

It now works but it still wont detect my user apps after the update.

I never had fc's, but Titanium hasn't been able to back up my apps. I'm assuming it isn't looking in the right place for them, but not sure if there is an option to change that.
Sent from my Vibrant using XDA App

Bschwartz40 said:
It now works but it still wont detect my user apps after the update.
Click to expand...
Click to collapse
I am no longer having any issues after update, i just tried a batch->backup user apps. and worked without a problem

T.I backup is awesome and Joel is great on support!
Can't wait for my Vibrant to get here!!

Ok I got it working, forgot about updating Busybox. App works great now! Thank you Joel!

hpz937 said:
I have rooted my Vibrant but when i try to back up my apps, titanium back fc's anyone else having this issue?
Click to expand...
Click to collapse
Wow... I installed the Modaco Froyo r5 with a2sd+, but right after installing it, it sends my Desire in a continuous boot loop. WTF!
Anyone else have this issue? I´m installing Titanium backup v3.2.1

all my apps and backups showed up but i cant manage to restore anything. it just kinda sits there. anyone figure out how to get things going? i used the apps busybox didnt help at all.

smellyfungus said:
all my apps and backups showed up but i cant manage to restore anything. it just kinda sits there. anyone figure out how to get things going? i used the apps busybox didnt help at all.
Click to expand...
Click to collapse
I do not have that issue. however depending on the size of the apps being installed it can take a bit of time to install. Does it say it is restoring or anything or nothing at all?

hpz937 said:
I do not have that issue. however depending on the size of the apps being installed it can take a bit of time to install. Does it say it is restoring or anything or nothing at all?
Click to expand...
Click to collapse
it just sits there at 0% on whatever app is first. if i close it out that first app manages to install but without data. the one time i did leave it on for around 10 mins it managed to install two apps.
is there any special thing i need to do before i do a restore?
note these apps are from chromatic 3.7 w/ my g1
edit: just tried new setting under restoration, although its not as fast as doing it on my g1 I managed to get things restored

I am slo having an issue where Titanium says its restoring, but just sits there doing nothing. SOmehow Ive managed to get it to restore once, but I had to wipe and now I cant get it to restore for the life of me. Tried w/ original busybox and the one that downloads inside titanium, both w/o success. Seems that titanium has some sort of issue w/ the Galaxy S.
Has anyone found a solution that allows you to restore your apps? Thanks!
EDIT: Whats really strange is if I try to hide titanium, relaunch it, and try and backup. It gives the message "backup already in progress" but for whatever reason it moves onto the next app...so strange

Force close loop

Hey. Well, let me first say I've literally spent the past 12+ hours working on my phone. I am exhausted mentally. I searched the forums and I was shocked to see that only one topic came up about it and it wasn't even about force closes. It was a 100+ page CM post.
I rooted for the first time today using a method posted on these forums + extra info I found about adding the OTA radio leak, and installed UV Hydra kernels. I got Rom manager and flashed Skyraider 2.2 Sense. I booted a few times too and all was good. I swear I thought I was doing it all right taking it slow, rreading all of the info over and over. A true noob. Everything was all cozy until I got my old apps and tried to make a backup with Titanium.
It's so cliche to say it but I need serious help. I don't know what to do and I'm near tears after all this work. I have dozens of force closes going on immediately after boot and even thereafter. At one point it asked me to reset up the phone. I can't run any app because they force close immediately.
I don't know if it's the Rom, something else, or me.
I know this is long winded. Please forgive me. And if this is in the wrong forum section, please forgive that too.

Do a full wipe in recovery and flash the rim and kernel again...but upon restoring, only restore downloaded apps, not system apps.
I remember when it took 12+ hours just to get root (for some people anyway) those were the days.
Sent from my ADR6300 using XDA App

lilsaphyre said:
Hey. Well, let me first say I've literally spent the past 12+ hours working on my phone. I am exhausted mentally. I searched the forums and I was shocked to see that only one topic came up about it and it wasn't even about force closes. It was a 100+ page CM post.
I rooted for the first time today using a method posted on these forums + extra info I found about adding the OTA radio leak, and installed UV Hydra kernels. I got Rom manager and flashed Skyraider 2.2 Sense. I booted a few times too and all was good. I swear I thought I was doing it all right taking it slow, rreading all of the info over and over. A true noob. Everything was all cozy until I got my old apps and tried to make a backup with Titanium.
It's so cliche to say it but I need serious help. I don't know what to do and I'm near tears after all this work. I have dozens of force closes going on immediately after boot and even thereafter. At one point it asked me to reset up the phone. I can't run any app because they force close immediately.
I don't know if it's the Rom, something else, or me.
I know this is long winded. Please forgive me. And if this is in the wrong forum section, please forgive that too.
Click to expand...
Click to collapse
Wow, That sounds like a seriously horrific days. Not sure if I can help, but i'll sure as hell try to. Can you verify that you Baseband Version is 2.05.00.06.11?
Did you create a nandroid backup of before you flashed any of the kernels? If you did I would restore that backup as I know some people have had issues running the old .29 hydra kernels with 2.2 roms. Or was this the new .32 kernels you flashed?
If you did not create a nandroid backup I would recommend flashing the leaked OTA from 8/1 located here, http://forum.xda-developers.com/showthread.php?t=742242, this is a leak of what will be close to the stock 2.2 htc will release in the near future. Remember to wipe data, wipe cache, and wipe dalvik cache(located in "advanced" of recovery.) As soon as you flash that and can verify it is working create a nandroid backup of it before you add any apps, I would recommend signing into your gmail, testing camera and camcorder, make a call, sending and receiving both an sms and mms, 3g data check, and then creating the nandroid when you see those are working. After you create that nandroid then start installing apps. Hopefully this can help you out a little bit. If you have any questions, you can pm me and i'll do my best to try and help you out more.

jdkoreclipse said:
Indeed that does seem horriffic. I think he restored system apps from ti backup tho. Ive never saw anything like this that wasnt ti backup related.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I didn't see you response until after I posted and you are most likely correct. I remember now, when i tried to restore system apps when i had a droid eris, that was not a fun day. Hopefully it's an easy fix and a learning experience, easiest way to learn is to make a mistake. Even though my answer is most likely not the solution to his problem, IMHO it's essential to always keep a nandroid of stock on your sdcard at all times, just in case.

Wow I see alot of info and I'm going to work with some of it but let me add this before I start dinking around today.
Right after I posted last night, I sat on the edge of my bed and had a thought. I had made a nandroid backup when I had almost every app back on my phone. The only ones I ones I didn't have when I got stuck were, Shoot me, Titanium backup, Adfree Android, and Tasker. Tasker being the only one I had before root. The others I picked up after.
SO! I told the phone to use the backup I had and I passed out to sleep.
I'm up now lol and thankfully I'm a stay at home mom so I can mess with this.
The backup made it a working phone again! Which is good. And this morning I had a second thought. When I opened Titanium backup last night, I got a message at the bottom of my screen that said Titanium had set itself up right... but it wouldn't go away. It kept looping itself. I thought it was just a fluke. Oh god... and NOW to think about it, that's WHY I rebooted in the first place. BECAUSE in the midst of it being weird, I tried to do a backup OMG. I wonder...
My Software says
Baseband 2.05.00.06.11
Kernel has a 32 in it

Alright I'm doing this nice and slow making backups along the way.
The only quirky thing that has happened is Titanium backup started spamming me again that it had been given superuser permissions so once again I had to reboot but this time it came up. Slow.... but it came up.
I guess what I"m trying to say is that I don't have a clue now what caused it.
OH! And my kernel is a 32 that came with the rom? The UV one I forgot to put on lol. It's on my SD card but I hadn't installed it. That one is a 29.
I just found a post on Android Forums where 2 people has this happen to them last night as well on Incredibles. They were without root.

If they were without root it could be a phone defect, I was going to recommend selecting fix permissions from rom manager.
EDIT: If ur running froyo try to only use .32 kernels. New kernels r up on Hydra website that are .32 check those out
Sent from my ADR6300 using XDA App

restore nandroid on SLCD?

i used to have an AMOLED inc from the day it was released. it just broke, and it got replaced with a brand new SLCD. i rooted it, and itll restore my nandroid's from before, but when i reboot out of the recovery, itll just hang at my boot splash screen. if i install the same rom (cyan 6.1, miui 11.19) from fresh, itll boot into the rom.
any idea? no big deal as i have my apps backed up with TB, but id like to restore back to my rom so all my settings are back.
also- on miui 11.19, after a while i started getting reboots every like 30 seconds. not sure why.

Trying to restore an AMOLED nandroid to a SLCD phone probably isn't going to work well due to the different hardware drivers. In short, you're trying to restore incompatible display software onto your phone.
That being said, restoring a nandroid from another phone is never a good idea unless your old phone has been destroyed or is still in your hands. Otherwise, there's a distinct probability that if the old phone is repared and sent out as a FRU, both devices would share the same android_id. As such, apps that you purchase could be involuntarily pushed the another user and vise versa.

Gotcha. ill delete those backups and install MIUI fresh, and then back it up from my new phone.
its still safe to restore apps+data from titanium backup right? (not system data, just apps/appdata)

You need a kernel that supports slcd. Your nandroid will work, but the kernel needs to be change to use the slcd display. All the system stuff is the same.
Restore the nandroid then apply the appropriate kernel afterwards before rebooting. Your system should work again.
If your nandroid is stock HTC you'll need a stock kernel. For slcd of you are running an aosp rom you'll need an soap kernel.
Sent from my ADR6300 using XDA App

how do i know which kernels will work with SLCD? or does the dev specify that in the thread for each kernel?

Most times the devs will say. Most times... remember kernels are specific to the type of build, aosp or HTC.
ufvj217 said:
how do i know which kernels will work with SLCD? or does the dev specify that in the thread for each kernel?
Click to expand...
Click to collapse
Sent from my ADR6300 using XDA App

linuxmotion said:
You need a kernel that supports slcd. Your nandroid will work, but the kernel needs to be change to use the slcd display. All the system stuff is the same.
Restore the nandroid then apply the appropriate kernel afterwards before rebooting. Your system should work again.
If your nandroid is stock HTC you'll need a stock kernel. For slcd of you are running an aosp rom you'll need an soap kernel.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Restoring the nandroid will, however, introduce the aforementioned security hole.

najaboy said:
That being said, restoring a nandroid from another phone is never a good idea unless your old phone has been destroyed or is still in your hands. Otherwise, there's a distinct probability that if the old phone is repared and sent out as a FRU, both devices would share the same android_id. As such, apps that you purchase could be involuntarily pushed the another user and vise versa.
Click to expand...
Click to collapse
Can you explain why. Or provide a link that can. Never heard of that security hole, but would like to know more about it because What your saying seems probable.
Sent from my ADR6300 using XDA App

linuxmotion said:
Can you explain why. Or provide a link that can. Never heard of that security hole, but would like to know more about it because What your saying seems probable.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Search is blocked from my LAN at work. However, if you search adrynalyne's posts, he was the one who discovered it. IIRC, he had posted the exact details over at androidforums.com. Essentially, he and a friend had restored a nandroid backup from one of their phones onto the other. From there, they noted that when one person installed an app using Appbrain's web installer, it was pushed to both phones.
ETA: found it...
http://androidforums.com/incredible...05-warning-do-not-share-nandroid-backups.html
adrynalyne said:
Warning. Do Not Share Nandroid Backups
--------------------------------------------------------------------------------
Even if your apps aren't there, and no personal information has been entered on a fresh wipe.
If someone asks for a stock Nandroid backup, kindly tell them to get lost
contagous and I learned the hard way. I sent him a completely tweaked and clean nandroid, with none of my personal info or anything like that. He has been using it and it works great.
Until AppBrain fast web installer is used. See, it IDs your device by the Android_ID, which is unique to every phone, or is supposed to be.
Nandroid backups will record this device ID, and clone it onto another device. Well, when contagous installs an app using the web installer, I get it. Without a prompt or nothing.
While I can do the same thing, and it was fun sending him pron apps and sexy men wallpapers, it has a real potential for a security nitemare. I trust contagous, but let this serve as a warning to everyone. Its also not so simple as installing another ROM and factory reset. So far as I can tell, as long as you stay on the same build OS, you will keep the same ID. The only thing that changed my ID to something else was going back to 2.1.
So friends, don't let friends share nandroids. If you do, play it smart, and delete all but the system and boot images and recalculate the md5.
Click to expand...
Click to collapse
and
adrynalyne said:
LOL,
Yeah here's the thing. Device ID and Android_ID are not the same.
YES, a nandroid WILL overwrite the Android_ID of devices and can cause security issues. Its like cloning a mac address.
Point in case, appbrain fast web installer uses it to identify devices. I know this, because I tested it, and CONFIRMED it with the devs.
Najaboy is correct.
I and another forum member were sending each other apps via our own accounts on app brain.
Any other app that uses the same method of identifying devices in the cloud also pose this same problem.
Moral of the story:
Be smart and don't use the same Nandroid on another phone unless you know how to erase cloned Android_IDs.
Click to expand...
Click to collapse

Hmm. That's good information to know!
Sent from CM Nightly 11-20 using Tapatalk.

What about a Titaniumm Backup? Any issues there going AMOLED to SLCD?

wpbear said:
What about a Titaniumm Backup? Any issues there going AMOLED to SLCD?
Click to expand...
Click to collapse
nope. those are simple just apps being restored, so no issues there.

Titanium backuo will restore some personal settings as well, correct?

wpbear said:
Titanium backuo will restore some personal settings as well, correct?
Click to expand...
Click to collapse
correct.

[Q] Can you restore between two phones?

I got a replacement Mytouch from T-Mobile yesterday and was just about to flash a new rom on it and begin restoring apps, but I was wondering if a nandroid restore would work between my old phone and the new one. I've seen people posting stock backups before, but I'm not sure if there is anything that comes up while the phone is used that would be specific to that one device. Is there anything in a backup that would tie it to just that one phone?

Yeah, i need to know this too. I assume you can though.

kitsunisan said:
I got a replacement Mytouch from T-Mobile yesterday and was just about to flash a new rom on it and begin restoring apps, but I was wondering if a nandroid restore would work between my old phone and the new one. I've seen people posting stock backups before, but I'm not sure if there is anything that comes up while the phone is used that would be specific to that one device. Is there anything in a backup that would tie it to just that one phone?
Click to expand...
Click to collapse
I've heard of people doing it but never tried myself. Try it and report back.
The worst that can happen is a boot loop. Then just wipe, reflash and go on with your original plan.

I did it Friday, since no one here seemed to have an answer. Seems to work just fine, I haven't had any major issues yet.

kitsunisan said:
I did it Friday, since no one here seemed to have an answer. Seems to work just fine, I haven't had any major issues yet.
Click to expand...
Click to collapse
Awesome, thanks!

I've done it once in a G1 when my girlfriend switched phones. Just use fastboot to flash the backed up nandroid files.

yes from my experience with the nexus one you should be fine. No issues restoring nandroid to another phone.

Is there a way to access Apps on a soft-bricked phone?

I'm stuck at the boot-screen of Deck's 1.2 rom, however, I can still access HBOOT and Clockwork Mod Recovery.
I don't see an explicit option, but is there a way I could access Apps or other data to save as a back-up?
I foolishly deleted my rom back-up, and last time I used Titanium Backup was a few weeks ago, so it's not a good option. Thanks!

Android 17 said:
I'm stuck at the boot-screen of Deck's 1.2 rom, however, I can still access HBOOT and Clockwork Mod Recovery.
I don't see an explicit option, but is there a way I could access Apps or other data to save as a back-up?
I foolishly deleted my rom back-up, and last time I used Titanium Backup was a few weeks ago, so it's not a good option. Thanks!
Click to expand...
Click to collapse
As long as the .zip for the ROM doesn't wipe /data, you could reflash "Deck's 1.2 ROM hopefully fixing your issue and not losing your apps.

mattykinsx said:
As long as the .zip for the ROM doesn't wipe /data, you could reflash "Deck's 1.2 ROM hopefully fixing your issue and not losing your apps.
Click to expand...
Click to collapse
I already tried wiping cache and dalvik, reflashing the rom, and I still get stuck in a boot-loop =/
Thanks for the suggestion though.

Android 17 said:
I already tried wiping cache and dalvik, reflashing the rom, and I still get stuck in a boot-loop =/
Thanks for the suggestion though.
Click to expand...
Click to collapse
You could wipe /boot and /system as well and reflash and see if that fixes it.

mattykinsx said:
You could wipe /boot and /system as well and reflash and see if that fixes it.
Click to expand...
Click to collapse
I just tried that and it didn't work either. This is maddening.
The last thing I remember doing was tinkering with the lockscreen settings in the advanced settings. I set up a rotary revamped lockscreen with Dolphin Browser HD as my custom application. I have Dolphin saved to SD too, but I don't see why such a small thing would cause constant bootloops.
It ran fine before 1.2 stable and messing with the lockscreen.

Android 17 said:
I just tried that and it didn't work either. This is maddening.
The last thing I remember doing was tinkering with the lockscreen settings in the advanced settings. I set up a rotary revamped lockscreen with Dolphin Browser HD as my custom application. I have Dolphin saved to SD too, but I don't see why such a small thing would cause constant bootloops.
It ran fine before 1.2 stable and messing with the lockscreen.
Click to expand...
Click to collapse
I have titanium backup run every night along with my call log back up app and go sms to back up texts.
Prevents this kind of thing.
Nothing you've said you have done explains a boot loop.

mattykinsx said:
I have titanium backup run every night along with my call log back up app and go sms to back up texts.
Prevents this kind of thing.
Nothing you've said you have done explains a boot loop.
Click to expand...
Click to collapse
That's a good idea. I usually just use Titanium backup when I'm doing a full wipe or flashing a ROM with significant updates, but since I'd been using Deck's for a while and having no issues whatsoever really and just updating incrementally, I didn't think to backup in a while.
I had actually backed-up the ROM prior to flashing 1.2 stable, but I needed to delete it to make room to back up the newer version, and I didn't think it'd be a big deal since it was stable for a few boots. I guess I got too comfortable.
This is ridiculous, I didn't make any changes to the ROM or flash any new radios or anything of the sort that should cause a bootloop.
I do also use the Theme Manager MattedBlues theme but I've been using that for over a week or so with no issues, so I doubt that's the cause.
Oh well, thanks for the ideas though.

Android 17 said:
That's a good idea. I usually just use Titanium backup when I'm doing a full wipe or flashing a ROM with significant updates, but since I'd been using Deck's for a while and having no issues whatsoever really and just updating incrementally, I didn't think to backup in a while.
I had actually backed-up the ROM prior to flashing 1.2 stable, but I needed to delete it to make room to back up the newer version, and I didn't think it'd be a big deal since it was stable for a few boots. I guess I got too comfortable.
This is ridiculous, I didn't make any changes to the ROM or flash any new radios or anything of the sort that should cause a bootloop.
I do also use the Theme Manager MattedBlues theme but I've been using that for over a week or so with no issues, so I doubt that's the cause.
Oh well, thanks for the ideas though.
Click to expand...
Click to collapse
Sorry I took my Xanax to sleep or else I'd likely be able to think of some kind of solution.
Hopefully someone else can help you out.

I think in CWM if you mount System&Data /apps you could utilize adb pull..... Also did you set up any custom partitions, a2sd, data2ext, ect... ?
Sent from my HERO200 using XDA App

Actually thanks for the suggestions guys, I managed to dig up an older version of the rom saved on my downloads folder and flashed it and booted.
For some odd reason, an older release labeled as experimental works better than the 1.2 stable...
It's strange too because I looked around Deck's thread and no one else reported any problems similar to what I was having at all.
For all intents and purposes it appears to be very stable and functional for everyone BUT me
Thanks for the suggestions though. I guess I'll hold off on flashing any roms for a while or wait for a newer version and try flashing with a full wipe.

Cool glad you got her going.
Kaaameeehameeehaaaaaa!