yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] Nazo:
Man I am glad to find this thread. I was just coming to the realization that there was absolutely no chance Titanium Backup would ever work again the hard way. I didn't realize it hadn't been updated since 2019... That has been one of my most absolutely essential apps for as long as I've even been using Android. It has saved my bacon on so many occasions. Now I find myself having to manually reinstall and reconfigure everything from scratch that the normal system backup can't do because Titanium Backup simply can't function on modern Android versions and all my backups from it are worthless. Termux alone has been true pain with so much to reconfigure since I'm not using the ancient appstore version that probably wouldn't even work anymore anyway. (I really wish they'd contact Google or something and get that removed.)

I'm kind of liking the look of this Neo Backup people have mentioned. I like that the full software is open source. No licensing stuff to deal with like with Titanium Backup. Was kind of an annoying problem to have to restore the license first before I could use it. Software of this sort of nature really should be free and open.

EDIT: Still doesn't work with everything it seems. Oh well. Guess one has to make do with whatever is available.

Looks like Swift Backup can work with pickier things such as Termux. I don't like the push to "premium," but it may be the better app for me perhaps. Thank goodness something works. I just hope I don't have to alternate between both to cover all my apps.

There are alternatives you know. Several places (such as APKMirror) offer mirrors of apps (at least the free ones.) But you may want to look at Aurora Store as a sort of more universal alternative since it can access the Google Play app store without using Google services at all. (Though you'll still need at least MicroG for some of the actual apps on it. Probably not for that though.)

I'm not sure which is better, but it sort of sounds like Neo Backup may still be for those of us with root, so this may be a moot point, but this is just a FYI for those who are trying to completely disconnect Google services or use more minimal setups like MicroG that there are alternate ways to get apps like those.

Well, TWRP used to do that. I'm not sure what's going on with it though. I was pretty shocked to find no updates since last year, no official support for Android 13+, and quite a range of popular devices unsupported. I bought a Pixel 4a 5G solely for how well supported it would be by third parties and lo and behold the last pixel in there predates it (though I doubt 3.7.0 would work with the latest LineageOS anyway.) If you can find a working version of TWRP for your device the partition backup and restore process may still work even if things like installation of the latest OS builds perhaps may not. You can possibly just use fastboot boot without flashing it at all even.
[General Questions and Answers] xerel89:
Actually I use swift backup, it's an good alternative to magrite
[General Questions and Answers] EngineerMind:
What exactly did not work with Termux when using NeoBackup?
[General Questions and Answers] Nazo:
Termux seems to be kind of tricky. When many things (such as Neo Backup) attempt to restore it, it comes up saying "unable to create bootstrap" (or something roughly to that effect -- I don't care to break it just to repeat the error message.) The long version of what's going on is that Termux requires the ability to have and set binaries as executable as well as some other things like creating symlinks that it can't do outside of its own /data/data/com.termux location. The problem -- I think -- seems to be permissions. When data is restored from several backup tools such as Neo Backup, TitaniumBackup, or etc I think maybe it's not correcting permissions or something. Perhaps related to the fact that it has a new "user" and "group" from the previous install (unless you just happen to end up with it installed at the same point in a new setup it's almost never going to be the same.) Though if it's not that I admit I'm not really sure what it is. All I can say for sure is Swift Backup is the only one so far that seemed to be able to fully restore it, permissions and all. (With the added bonus that it kept the user password working for things like sshd -- even its own backup script that mostly just tars everything couldn't do that -- or perhaps wouldn't since its tar backup is unencrypted.)

I realize I should mostly just rely on the tar backup method anyway, but I feel like this issue with it points to issues that can happen with other things if they use similar methods to the stuff it does for anything -- though I admit Termux is largely a unique case on its own. Mostly. (Eventually they seriously do need to move to other methods too really. Maybe a virtual filesystem image or something. But when this method seemed to work well enough with newer Android versions they just left it at that for now it seems.)
[General Questions and Answers] EngineerMind:
Just a FYI that might fix the issue...

In NeoBackup, there is a setting (in Settings...Service) called "Restore Permissions" which will restore the original permissions when an backup is restored.
[General Questions and Answers] Nazo:
Looks like that was already ticked on by default and I never turned it off, so I guess that didn't fix it. And I may be wrong about that being the exact issue. I do know some things at least look like they are properly restored, but maybe not the full filesystem structure (it has a lot after all.) I never looked into if there was some way I could make it log or something to see the exact specifics and I never looked over the entire structure after a failed restore, I just know when it says that error it means it's unable to create the initial program files it needs to work -- and it would only be trying to setup initial program files if it could not access the ones that were already there (which is really kind of incorrect handling anyway if they physically are already there since it needs to take different actions in that circumstance.) Honestly I wish it had more of a failsafe if it's unable to setup those initial files for any reason where you're given just a simple busybox or somesuch to be able to access things and maybe fix stuff.
[General Questions and Answers] EngineerMind:
Luckly, NeoBackup is still being actively modified by the developers.

So, now is the best time to report any problems to the devs so they will have a much higher chance of being looked at because once an app stabilizes, the developers usually move onto something else, and the chances of getting bug fixes are greatly reduced.

Issues · NeoApplications/Neo-Backup

backup manager for android. Contribute to NeoApplications/Neo-Backup development by creating an account on GitHub.

github.com
[General Questions and Answers] Nazo:
I know I probably should make an issue. Not sure if I have the patience to do so or not though. It's a bit of a set of hoops on its own many times (and some projects are even almost hostile towards people doing so or at least do the whole "Soup Nazi" thing.) The main problem is just figuring out what even to give them (logs or whatever) and dealing with it in itself requires a bit of time and effort that sometimes one gets tired of doing. But I would rather support an open source project than a closed, commercial one I admit, so I probably will at some point. Especially in this day and age where a lot of software like this on the market can be a bit... questionable... (Though as far as I could determine Swift Backup does seem legit, I've seen some go bad -- especially as they change hands. Actually, that's an issue that all the current app stores -- Apple, Google, and even Microsoft -- seriously need to address since some software actually changes hands and then starts adding bad things in, taking advantage of the fact that it was approved on the app store previously and thus not being rechecked properly after the changeover.)

The active development thing is a bit tricky though. I've seen stuff that's quite old for outdated stuff still getting at least some work done and occasional actual interaction even with issues. One project for a niche modding software has a dev so active that they have actually DMed me on Discord to get information on an issue and directly and immediately solved a problem (amazing, seriously. Amazing.) Conversely I've seen some stuff that is practically brand new just basically ignore everything as thousands of issues piled up, just doing their own thing, blissfully unaware of what the users were saying. I find it especially interesting though in this case because Titanium Backup was actually a commercial software (albeit not terribly expensive) and, in fact, should have been pulled from the market (or at least made free) when it was abandoned and stopped working. They likely still get profits from some people who don't refund in time (and, after all, you don't know it's broken until you actually try to restore something...) You don't generally see commercial, paid software just get abandoned without a word like that without some sort of action being taken (eg the market pull.)

I do have a bit of a kneejerk at the sort of "flashy" way Neo Backup looks and acts in general though. I know that's silly, but it reminds me of a lot of those low grade free apps that do bad things in the background.
[General Questions and Answers] Nazzz:
Just tried Swift Backup, and it successfully managed to back up and restore all my apps that don't have proper cloud backup (e.g. some older games). Looks like I've found the alternative to TB.
[General Questions and Answers] Jeetu:
Anyone confirm that Titanium backup app is working after root on Android 13 or not?

need alternative which can make multiple data backup of same app.
[General Questions and Answers] EngineerMind:
Just read page 3 of this thread.
[General Questions and Answers] Nazo:
NeoBackup for open, SwiftBackup for mostly free. SwiftBackup seems to restore data slightly better in a handful of cases (I've run across two apps maybe in total) but otherwise there isn't much difference (so the more open NeoBackup makes more sense for most use cases and my suggestion is to use it unless you run into something specifically requiring SwiftBackup.) NeoBackup can be found on F-Droid or Github.
[General Questions and Answers] Jeetu:
Thanks for Suggestions.

Can you confirm Can we make multiple backups of data from same app. As far i have read in Swift backup only 1 backup is allowed for every app.
[General Questions and Answers] EngineerMind:
In the time you took to post the question and wait for a reply, you could have installed it and found the answer to that question as well as other quetions you will probably have ;)
[General Questions and Answers] Nazo:
While I do agree with your basic point, I don't really think that's very constructive or helpful as a whole. If you don't know, just don't post... The implication is they did actually check first before asking anyway.

NeoBackup supports setting a large number of backups. Swift Backup is a bit more complicated though. It has an option that says "archive old version of an app backup" which I believe essentially saying two backups, but it's confusingly worded. As far as I can tell that is actually what it does mean, but I can definitely see why people wouldn't even realize that it exists as an option with that confusing wording. (It sort of implies it only backs up the app itself but the full wording seems to mean it's the full backup.)

My recommendation is still NeoBackup if it works for all your apps.
[General Questions and Answers] Shadeclan:
I recommend

My preference for de-Googled phones (no Google Play) is Migrate but it seems to have disappeared from the Google Playstore as well as F-Droid. The last XDA post on Migrate makes it look as if the application has been abandoned and, in any case, is not working with Android 14.

Backing up your phone for transfer to an new phone, for upgrades and to try out different ROMs really seems to be the Achilles heal of de-Googling - and it seems like every new iteration of Android throws a new monkey-wrench into the works. Phone rooting seems to be getting more and more difficult. Backup solutions need to contend constantly with these issues.

I created this thread a long time ago and I guess I shouldn't be surprised that this is still an issue.
[General Questions and Answers] Nazo:
Yes, though to be fair, it's partially a good thing. The biggest thing that seems to have broken stuff is further and further still encapsulation and separation. Apps can gather less data without permission, can do less with exploits, etc etc. For example, the problem I ran into when backing up Termux is the fact that each app is given its own (semi-)randomly generated username in the *nix part of the OS and permissions within its own application directory are set to that, whereas a lot of things didn't properly correct the permissions to reflect the new username when reinstalling. (It's too bad encapsulation hasn't reached a point they get filesystem images or something instead of access to an existing partition.) To be fair, that's hard to fix... It has to find the new username, then go through the app folder and correct permissions on every file... It certainly makes for a challenge to keep up with all that.

As long as they don't actually take away our ability to surpass all this when we absolutely know what we're doing it's good, but it does make it a moving target for specialized apps like this since they have to incorporate those changes. I feel like Google at least isn't considering abandoning leaving root as a thing that actually exists (despite some of their latest tendencies towards a more anti-consumer model modeled after some of the stuff Apple & co do,) but quite a lot of OEMs are certainly making it harder (getting especially sick of everyone accommodating Verizon and their straight up outright hostility towards their own consumers.) As long as we can at least get access to this much though it should always be possible -- just a matter of the software designers figuring it out.

FWIW LineageOS does have its own backup system (the confusingly named "Seedvault" which stores backups, not random seeds, lol) that is presumably pretty reliable now. NeoBackup can get almost everything and SwiftBackup seems to get the rare cases that it misses.
[General Questions and Answers] lysaer:
I just made a backup before updating my ROM, went to restore my phone and any app that is restored just crashes, can confirm it is not working
[General Questions and Answers] doggydog2:
TitaniumBackup is dead💀 for years, 3C Toolbox backup died a year later (low restorability), NeoBackup is the name of the game now. Very very high restorability, with some quirks commented here. Overall very good, and easier to operate.
[General Questions and Answers] IronTechmonkey:
TiBU has problems with adaptive icons and split apks (and probably other things); It can still back up some older apps but not enough to be considered viable for most people. For my usage (on Android 11) Swift backup has been quite good and is even better than Titanium Backup was at handling app permissions but it does not allow multiple backups of different app versions (only 2). I used the TiBU unfreeze/run-freeze widget until recently creating Tasker widgets for that.
[General Questions and Answers] IronTechmonkey:
As stated by the SBU's developer here: https://swiftapps.org/faq#multiplebackups

"Please look for alternatives if keeping arbitrary multiple backups of apps is essential for you."

LOL "arbitrary". I can understand wanting to keep things simple and manageable regarding # of backups but that is a fairly dismissive turn of phrase for a type of back-up archiving that is probably important to many of us. A crude workaround is to copy the Swift backup folder elsewhere at intervals and date-name the folders. This is not practical to maintain over time but I have pulled an older backup out of such a folder.
[General Questions and Answers] IronTechmonkey:
Indeed the SBU description is not clear but you've got it right, the backups are complete if we set them to be so. From my experience using SBU on several devices for about 1 year it goes like this:

- Backup the app (first backup - which in my case includes App, data, and external data) is primary backup.

- As long as app version (and package name?) remains the same then new backups will overwrite the previous ones and there will be no "archived" backup.

- When a new app version is detected the old backup becomes the "archived" backup and the newer version will become the primary backup.

- As long as new app version remains the same then subsequent backup will overwrite primary backup but archive backup will remain static.

- At the next app version/package change - lather rinse repeat.

Although SBU has been very good for one-shot backups between ROM changes or refreshes and SBU performs quite well, the lack of ongoing archival backups is a limitation for app and ROM testing. Thanks for the reference to NeoBackup, if I get back into serious app testing I'll check it out.
[Blu Vivo 5] zombie_ryushu:
Do you think there is any way that a Project Treble Rom could be made for this device allowing installation of GSI images? I still use my Vivo 5.
[Blu Vivo 5] KKShedge:
Definitely need a treble rom for Vivo 5. I tried to build it myself but no success. We also need latest TWRP to flash GSI as the version that supports Vivo 5 will not be able to flash GSI.
[Blu Vivo 5] zombie_ryushu:
Please keep trying. attempt to get others to help you if possible.
[One (M9) Q&A, Help & Troubleshooting] nader.nader:
My phone comes into Boot loop and cannot enter to recovery mode or download mode, only bootload

I've tried to flash a hosd files but it doesn't sucsess to enter download mode

Can anyone help me to find all hosd files available to try it on my phone
[OnePlus 3 Questions & Answers] plskillme:
Are we going to get custom roms based on this official rom?
[BLU R1 HD Questions & Answers] zombie_ryushu:
Would it be possible to get a Project Treble Rom made for this Device? Using say the Marshmellow Drivers? I still have my R1 HD and would like to see it updated and I am wondering if Project Treble can help that.
[Google Pixel 2 XL Questions & Answers] youssefkr:
Hi, I was wondering if I could update magisk directly from the app ? my phone is obviously rooted but with stock recovery.

Or do I have to just ADB it ?

Also, is it better to just flash TWRP permanetly ?

Thanks :D
[Google Pixel 2 XL Questions & Answers] Badger50:
Interesting question, with an interesting answer. Maybe yes and maybe no! The P2XL is one of the most interesting devices in recent memory. Personally, I have updated magisk several times through magisk manager. Until the May update that is, at least for me. Magisk versions 19+ has bootlooped me every time, yet 18.1 works fine. Yet, there are several other users that have had zero problems with the latest twrp and magisk versions as well. So, who knows what your device will do. You don't need to necessarily install twrp, since you can temporarily fastboot into twrp, and then flash magisk, or you can adb it, it's your call. Just be prepared for a bootloop, or, it may work fine. Best of luck to you, and sorry for my ambiguous answer, but then again, that's how the P2XL is :cool:
[Google Pixel 2 XL Questions & Answers] youssefkr:
Now I'm more confused lol

Thanks for the answer though :D
[Google Pixel 2 XL Questions & Answers] Badger50:
Makes 2 of us. Heck, if I were you, I'd just let magisk manager update itself to the latest versions and see what happens. At worst, you'd, have to fastboot into twrp, flash the magisk uninstaller, then flash 18.1 again to acquire root again. Only bad thing is that you'd have to instal your modules again.
[Google Pixel 2 XL Questions & Answers] youssefkr:
So I just updated via the app (19.2) and it went well, not bootloops or whatsoever :D
[Google Pixel 2 XL Questions & Answers] Badger50:
Congrats! Lucky duck. This issue is still perplexing me. The P2XL is just like a box of chocolates..."Ya never know what your gonna get" :laugh:
[Google Pixel 2 XL Questions & Answers] dallas90733:
I'm having the same issue in beta Q 3.. everything I try to update it through magisk, it will not install at all.

Just get a error that reads, " app did not install".
[Google Pixel 2 XL Questions & Answers] Droid_Nut:
Just updated yesterday to 19.2 through the manager yesterday. Running Q Beta 3. No problems.
[Upgrading, Modifying and Unlocking] kimlung:
Hi

I am a HK user with Operator "3(3G)" subscribed. I have failed to connect the 3G network and always connected to 2G network with "roaming icon" always only.

My Version:

PDA: i780DXHC4

Phone: i780DXHC4

Anyone can help to solve the 3G connection problem?

Any one can also resolve the "roaming icon" in 2G setting?
[Upgrading, Modifying and Unlocking] BiGreat:
It's wired...

I have the same problems as you, but i'm in US
[Upgrading, Modifying and Unlocking] jameshuang:
I belive you can use 3G setting after configure the Phone Setting in Lok Chun.

3-3G and 3-2G are two separate operator (technical prespective) Roaming icon will be up when you "roam" from 3-3G to 3-2G in other generation USIM (R1 - R5)
[Upgrading, Modifying and Unlocking] kimlung:
I have resolved the problem after change a new unit from the shop. Maybe hardware problem. Thx anyway
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Valera1978:
I'm not responsible for any damage to your device of any sort.

By flashing this you take responsibility of anything that happens.

Process at your own risk!

If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.

Instructions

1. Install custom recovery - use my twrp

2. Download the zip(s) - firmware and Magisk (optional)

3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei

4. Full wipe all

5. Flash firmware and Magisk

Information

This is native tablet port with normal keyboard, animations and other stuff.

My port based on:

framework and apps: T510XXU1ASCE and T515XXU1ASCK (new Tab A 10.1 SM-T510\515) Android 9.0 with 2019-03-01 security patch

libs and etc: A600NKSU1ZSB6 (SM-M105F) Android 9.0 with 2019-02-01 security patch

kernel: based on M105FDDU1ASB2 (SM-M105F) Android 9.0 3.18.91

Additional

1. Added OC for CPU (1690MHz - Kernel Adiutor, EX Kernel Manager) and GPU (default 1001, in OC 1146MHz - EX Kernel Manager)

2. Added themes from A600N

3. new wlan driver driver 4.0.10.206A_20181017 (from A600FNXXU3BSC5)

Links

LTE version:

1. 20190523: https://drive.google.com/file/d/1tK1F92bTWaaOBqUbkyVL8j3Sw50B0kre/view?usp=sharing

WiFi version:

1. 20190523: https://drive.google.com/file/d/1v2OM_IL8SCq5rLxOG1Vy21syd2KTq-Zd/view?usp=sharing

Magisk

Before run Magisk installer in TWRP - you need run small script - https://drive.google.com/file/d/1ZnnKHtDAl0ioHjQXiNO6wErZN8odsO0P/view?usp=sharing

It's simply unmount /cache partition and then mount it as /vendor. After run the script, you can install Magisk. If Magisk Manager does not appear in the list of apps - extract magisk.apk from Magisk installer and manually install it.

Sources

Kernel: https://github.com/Valera1978/android_kernel_samsung_exynos7870

Thanks

Thanks to Samsung
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] alanloax:
good morning Valera! I've been waiting for this a lot, since Samsung Pie is very good rom, I've already downloaded and flashed it. I just had time to try the basics and everything seems to work and the Ui is nice. Then I will make a good revision. Thank you very much for your great works!