Related
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
http://forum.xda-developers.com/showthread.php?t=2113150
see if work, first do a nandroid backup, then download this and the uninstaller, then flash this and reboot, if this dont work go back to twrp and flash uninstall, the best feature cant be used, that is frandom, we need a kernel with a module to use this, it is 50 times faster that random!
Have you tried this?
bryanchapman9999 said:
Have you tried this?
Click to expand...
Click to collapse
no
TWRP 2.5.0.0 reboots my device while performing a restore. It usually happens during the DATA phase. I've tried two different restores and the same thing happens. Thanks
If you need more detail, i'll do my best to provide.
sorryihaveaids said:
TWRP 2.5.0.0 reboots my device while performing a restore. It usually happens during the DATA phase. I've tried two different restores and the same thing happens. Thanks
If you need more detail, i'll do my best to provide.
Click to expand...
Click to collapse
I've actually been getting random freezes and reboots in TWRP myself, in the last 2 weeks or so, since I've gone flash-crazy. Have you been flashing a lot?
dibblebill said:
I've actually been getting random freezes and reboots in TWRP myself, in the last 2 weeks or so, since I've gone flash-crazy. Have you been flashing a lot?
Click to expand...
Click to collapse
I wouldn't say flash-crazy, but i've tried two different roms in the past two days. It's not really freezing either. It will just start to restore, make it half way through, and reboot. My rom will be restored but none of my data.
sorryihaveaids said:
TWRP 2.5.0.0 reboots my device while performing a restore. It usually happens during the DATA phase. I've tried two different restores and the same thing happens. Thanks
If you need more detail, i'll do my best to provide.
Click to expand...
Click to collapse
Yep, seems to be happening a lot. One suggestion was to revert to 2.4 or even 2.3.3.0. I tried that, and thought the problem was solved, but then it happened again, so I figured what the hell, I'll go back to 2.5.
You're right, it always happens during the data restore, but so far the second attempt at restoring always succeeds, so it's more annoying than anything. I can't recall it ever happening on my phone, though, so I wonder if it's a device issue. Also my phone is running JB 4.1.2 and my N10 is on 4.2.2.
Sent from my Nexus 10 using Tapatalk HD
Ive noticed this problem as well. Hopefully it will be fixed in later releases.
brGabriel said:
Ive noticed this problem as well. Hopefully it will be fixed in later releases.
Click to expand...
Click to collapse
So yesterday I went to flash a new ROM and TWRP froze immediately after doing a Factory Reset Wipe. Nexus kept bootlooping and then getting stuck on the TEAMWIN screen. Was able to get into the bootloader and flash the stock image and unroot through the Nexus Toolkit. I lost all my data though. So my question is, if you can get to bootloader mode and the toolkit recognizes it in bootloader mode, can you recover data without having to do what I did and wipe the device? For future reference sake. God I need to get better about backing up my data on my PC.
Anyone found the solution to this? I am not able to restore my data ( During the resotre in TWRP it goes blackscreen and then just reboots. I've triel like 10 times already..
ky3bmu4 said:
Anyone found the solution to this? I am not able to restore my data ( During the resotre in TWRP it goes blackscreen and then just reboots. I've triel like 10 times already..
Click to expand...
Click to collapse
I had the same issue. Its most likely a corrupt backup and can't be solved. But if you've successfully restored that backup before try reflashing the recovery. Just a tip that somebody else gave me. Use philz cwm touch recovery. It has no issues and more reliable then other recoveries.
Sent from my Nexus 10 using xda app-developers app
abdel12345 said:
I had the same issue. Its most likely a corrupt backup and can't be solved. But if you've successfully restored that backup before try reflashing the recovery. Just a tip that somebody else gave me. Use philz cwm touch recovery. It has no issues and more reliable then other recoveries.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Yes, i'm thinking the same. Maybe it also because the backup was huge (maybe like 4 gb).
But I am not really sure if it is corrupted because the system restores fine and data do not, but it fails in different places, i.e. it may reboot in 30 seconds and may reboot in 2 minutes...
Hi everyone! I recently decided to install the 4.4.2 rom on my Galaxy Note 3 N9005 and I didn't like it because it obviously was buggy as ,entioned in the thread. So I wanted to go back to my nandroid backup which I had made before installing the rom. It all went right in CWM and no errors, so I rebooted my phone and got stuck at the glowing samsung logo, so after many fixes and things I tried which didn't work I flashed a pre-rooted stock rom for it and it all went well. I managed to restore to my nandroid finally and then I unlock my phone to find a "com.google.process.gapps has been stopped" message which wont go away when I tap "OK". It just comes back and gives me one second untill it comes back again. I really need help since I need my phone for work, I have tried reinstalling all the gapps, wont work, I have tried reflashing the stock rom and restoring my nandroid again, I have tried deactivating "Downloads" in the app manager but that wont fix it either and finally I have tried clearing the "app data" for all my apps but again, no luck. If anyone would be able to help me I would appriciate it very much. Thanks in advance!
You're probably gonna have to go back to complete stock. Grab your stock image and flash via odin, boot it up and see if it gives you the error without installing custom recovery and your backup. That way you'll know where the error lays.
Sent from my SM-N9005 using XDA Premium 4 mobile app
radicalisto said:
You're probably gonna have to go back to complete stock. Grab your stock image and flash via odin, boot it up and see if it gives you the error without installing custom recovery and your backup. That way you'll know where the error lays.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Forgot to mention but when I return to complete stock there isn't such a message, only when I restore to my nandroid. I also tried restoring from an older backup which I had made like 2 months ago and the same problem remains, "com.google" message is still there. Any suggestions or should I just start over?
mikey429 said:
Forgot to mention but when I return to complete stock there isn't such a message, only when I restore to my nandroid. I also tried restoring from an older backup which I had made like 2 months ago and the same problem remains, "com.google" message is still there. Any suggestions or should I just start over?
Click to expand...
Click to collapse
Sounds like a dodgy backup or it somehow got corrupted, I'd start over to save any headaches for future reference -- It's a headache I know, but safer I think. You could hang five, see if anyone else chimes in with any other ideas though
radicalisto said:
Sounds like a dodgy backup or it somehow got corrupted, I'd start over to save any headaches for future reference -- It's a headache I know, but safer I think. You could hang five, see if anyone else chimes in with any other ideas though
Click to expand...
Click to collapse
Yeah i'm probably gonna have to start over from scratch, thank you so much for te super fast reply, I appriciate your answer and help. As you suggested I will keep staying on this thread to see if anyone has the fix. If not i'm just gonna reflash this thing again.
And again, thank you so much for the fast reply I appriciate it alot.
mikey429 said:
Hi everyone! I recently decided to install the 4.4.2 rom on my Galaxy Note 3 N9005 and I didn't like it because it obviously was buggy as ,entioned in the thread. So I wanted to go back to my nandroid backup which I had made before installing the rom. ...
Click to expand...
Click to collapse
A nandroid backup is simple but monolithic. Most people also use Titanium Backup for the ability to restore selective stuff, or to restore to a completely different model of phone.
I had same issue
Bith titanium and nandroid restore.
Well only way to save your self. Completing wizard of first startup with feeling google..
And just restore user apps and data with titanium except google stuff..
This is the only healthy restore method so far i know that gapss.com keeps kool
Sent from my SM-N900 using xda app-developers app
So I somehow managed to go to settings and disable Play Services with the one second time line that I had before the message appears again, and the message stopped. So it must be something with Play Services. Since i'm new to android (and the Note 3 is my first android phone) I want to ask if there is a way to maybe reinstall Plaay Services?
mikey429 said:
Hi everyone! I recently decided to install the 4.4.2 rom on my Galaxy Note 3 N9005 and I didn't like it because it obviously was buggy as ,entioned in the thread. So I wanted to go back to my nandroid backup which I had made before installing the rom. It all went right in CWM and no errors, so I rebooted my phone and got stuck at the glowing samsung logo, so after many fixes and things I tried which didn't work I flashed a pre-rooted stock rom for it and it all went well. I managed to restore to my nandroid finally and then I unlock my phone to find a "com.google.process.gapps has been stopped" message which wont go away when I tap "OK". It just comes back and gives me one second untill it comes back again. I really need help since I need my phone for work, I have tried reinstalling all the gapps, wont work, I have tried reflashing the stock rom and restoring my nandroid again, I have tried deactivating "Downloads" in the app manager but that wont fix it either and finally I have tried clearing the "app data" for all my apps but again, no luck. If anyone would be able to help me I would appriciate it very much. Thanks in advance!
Click to expand...
Click to collapse
Hi, there! I just got almost the same issue like you. Once update to custom 4.4.2, any nandroid backups which worked right before getting GAPPS' FC constantly. :crying: Try double wipes, flash 4.3 gapps full package, stop&restart android download, uninstall google play store update, etc. nothing can fix it. Only way stop the popup error, is flash stock rom. But, consequently, lose root access, even with the same method that rooted the stock rom before. I'll heard some guy said the 4.4.2 has different partition from 4.3 or older android rom. But don't mention how to restore the old partition way. So, hope anyone can help us out, thanks a lot.
Hey guys, not exactly sure where to post this since this has happened to me both with AICP and now once with Dark Rom. So simply put I am just using my phone and then randomly it soft reboots. I hurry and take some logs before the next. Then the next. Then it keeps doing this with each time between getting shorter until it just won't fully boot up without wiping dalvik and cache.
I am using Dark Rom at the moment with A2017U version and the stock kernel that comes with Darkrom. However I believe I did have it with LlamaSweet as well. The only modifications I have done are magisk and trying out jococ v2 tweak which I doubt either is the cause.
Has anyone had ant issues like this or does anyone know how to fix it? I hate knowing it's random and it may make my alarm clock not go off if it is in a bootloop.
Hope to get some help with this! Thanks!
JTruj1ll0923 said:
Hope to get some help with this! Thanks!
Click to expand...
Click to collapse
Just realized the zip posted has only files that are blank.... So here is a log I grabbed from TWRP. Hopefully this will help instead!
JTruj1ll0923 said:
Just realized the zip posted has only files that are blank.... So here is a log I grabbed from TWRP. Hopefully this will help instead!
Click to expand...
Click to collapse
No idea, not a dev. But I've read somewhere that Magisk 14.5 might be the culprit. I had this exact same problem on LineageOS. I made a backup of the system that was doing this, then wiped system and data, flashed LOS, booted it, then went to TWRP, wiped system and data, and restored the backup (only system, boot and data backed up). That solved it until you rebooted or the phone just decided to reboot itself...
Choose an username... said:
No idea, not a dev. But I've read somewhere that Magisk 14.5 might be the culprit. I had this exact same problem on LineageOS. I made a backup of the system that was doing this, then wiped system and data, flashed LOS, booted it, then went to TWRP, wiped system and data, and restored the backup (only system, boot and data backed up). That solved it until you rebooted or the phone just decided to reboot itself...
Click to expand...
Click to collapse
By doing this what would be the benefit? From what I can see you are basically back at point A by restoring the files. But yeah I do have magisk 14.5 installed... I had some problems with 14 but I'll see if I can get it to work this time. Thanks!
JTruj1ll0923 said:
By doing this what would be the benefit? From what I can see you are basically back at point A by restoring the files. But yeah I do have magisk 14.5 installed... I had some problems with 14 but I'll see if I can get it to work this time. Thanks!
Click to expand...
Click to collapse
Yes, it seems like it would do nothing, but it actually fixed my phone every time.
Maybe you can try the magisk uninstaller zip, dunno
Choose an username... said:
Yes, it seems like it would do nothing, but it actually fixed my phone every time.
Maybe you can try the magisk uninstaller zip, dunno
Click to expand...
Click to collapse
Thats Interesting. Well it happened again and logs were empty again... So I moved back to magisk 14.0 if that doesn't work I'll try restoring system and data.
@JTruj1ll0923,,
Hi,
you can try to backup before hard reset your phone. Usually, the LlamaSweet and DARK ROM are not compatibile with A2017G, so ZTE stock ROM would be a better choice.
William Guo said:
@JTruj1ll0923,,
Hi,
you can try to backup before hard reset your phone. Usually, the LlamaSweet and DARK ROM are not compatibile with A2017G, so ZTE stock ROM would be a better choice.
Click to expand...
Click to collapse
Thanks but I have a a2017u. Don't know if that makes much a difference though.