Database Info

[Resolved] [Q] Factory Reset and "Rom"

Hello,
If you have a Phone which comes preinstalled with stock and Put "X" rom on the Phone, install some junk do some stuff, .
Now If i Click , Settings > Back up and re set > Factory data reset . If i click that option,
Dose it make the phone go to preinstalled STOCK or pre installed "X" Rom?
Thank You very much !
Soled tthanks

First of all which handset are you using
Hit like if i helped you

Flashing a new ROM overwrites the old ROM unless you have something like MultiROM installed to boot multiple ROMs. Factory reset wipes the userdata, cache and dalvik cache leaving your system partition in it's default state.

Username invalid said:
Flashing a new ROM overwrites the old ROM unless you have something like MultiROM installed to boot multiple ROMs. Factory reset wipes the userdata, cache and dalvik cache leaving your system partition in it's default state.
Click to expand...
Click to collapse
Umm, Big thanks for your help!
I'm more of a windows geek,
E.g If i re install windows OS on PC, -- EVERY File, gets deleted and a Brand new, OS is created ( with all new files created)
Now on Android:
If a Factory Reset happens, to Confirm A or B
A) Does the user data, gets deleted But everything else all the other "Hidden" files remain the same
Or
B) Does it happen like Windows, All files get deleted and EVERY file, is re created Brand new.
I want to do B.
Big thanks for helping

Krisshp said:
Umm, Big thanks for your help!
I'm more of a windows geek,
E.g If i re install windows OS on PC, -- EVERY File, gets deleted and a Brand new, OS is created ( with all new files created)
Now on Android:
If a Factory Reset happens, to Confirm A or B
A) Does the user data, gets deleted But everything else all the other "Hidden" files remain the same
Or
B) Does it happen like Windows, All files get deleted and EVERY file, is re created Brand new.
I want to do B.
Big thanks for helping
Click to expand...
Click to collapse
Factory reset is like refreshing Windows 8. It leaves your saved files and operating system intact while erasing your installed programs and Windows settings.
Reformatting is like resetting which will also delete any saved files leaving only the stock OS.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can flash different ROMs and keep the same kernel and recovery like installing different Windows keeping the same BIOS.
If you also want to delete the system OS then you can do it through recovery or Fastboot.
You can not completely wipe your device like a hard drive.

Username invalid said:
Factory reset is like refreshing Windows 8. It leaves your saved files and operating system intact while erasing your installed programs and Windows settings.
Reformatting is like resetting which will also delete any saved files leaving only the stock OS.
You can flash different ROMs and keep the same kernel and recovery like installing different Windows keeping the same BIOS.
If you also want to delete the system OS then you can do it through recovery or Fastboot.
You can not completely wipe your device like a hard drive.
Click to expand...
Click to collapse
Thank you big time, Yes I want to Re format it and re create the system files , But how would I do that
If you also want to delete the system OS then you can do it through recovery or Fastboot
I am kinda new to andriod. Which options and in which steps shall I do . Thank you

Krisshp said:
Thank you big time, Yes I want to Re format it and re create the system files , But how would I do that
If you also want to delete the system OS then you can do it through recovery or Fastboot
I am kinda new to andriod. Which options and in which steps shall I do . Thank you
Click to expand...
Click to collapse
I don't know what device you're using or what's compatible. I know that for Nexus devices you can download the image pack which is like the mobile equivalent of ISO then flash it through Fastboot.

Mount system as writable in TWRP?

As title says can I safely mount system writable in TWRP to modify build.prop? I would like to push pull the file from TWRP as any changes I make while in Android won't save.
I am mha-l29c567b190 with unlocked bootloader and rooted with phh method. My data is still encrypted at this point.
I'm not familiar enough if what I want to do is going to cause a bootloop or something. I know this will modify system so future OTA will break and I'll probably just decrypt data or figure out how to get back to stock.
I do have backups of everything right after TWRP install (except data since again I'm encrypted) so I may be able to restore that too but don't know if that would work on this phone or not. Thanks!

2nd question. Based on my phone setup, could I uninstall phh superuser from Android, boot to TWRP and restore boot and flash stock recovery to get back to stock? Rooting this phone doesn't seem to have the same advantages of any other phone I've owned so might want to revert back.

Good questions
1. Yes. You can mount /system as read/write if you installed phh superuser using manual. There are two options:
- only root
- root + dm-verity off
Dm-verity is kind of phone's security which is protecting important partition to be modified. Even if you have root and mounting system as read/write and doing something with system, your system partition will go stock state after reboot.
But turning dm-verity off removes this protection and you will able to modify system and other partitions.
2.
To get stock state back you need restore stock boot and recovery.
If you modified system, you have to revert all changes.
But sometimes it is too hard to remember all changes, so best way to get stock is:
- flash stock recovery
- flash stock ROM via Firmware Finder (FF)
It is easiest and quick method.

5[Strogino said:
;74089991]Good questions
1. Yes. You can mount /system as read/write if you installed phh superuser using manual. There are two options:
- only root
- root + dm-verity off
Dm-verity is kind of phone's security which is protecting important partition to be modified. Even if you have root and mounting system as read/write and doing something with system, your system partition will go stock state after reboot.
But turning dm-verity off removes this protection and you will able to modify system and other partitions.
2.
To get stock state back you need restore stock boot and recovery.
If you modified system, you have to revert all changes.
But sometimes it is too hard to remember all changes, so best way to get stock is:
- flash stock recovery
- flash stock ROM via Firmware Finder (FF)
It is easiest and quick method.
Click to expand...
Click to collapse
Thank you for the responses. How do I get dm-verify off?

Does anyone know the drivers needed to get ADB to work in TWRP? I have ADB working fine when in Android and fastboot works fine in bootloader. I would like to modify the build.prop and push it back to the phone. I can't seem to do it either inside of twrp file manager, as it sees /system/vendor as a file and not a path.

bhint15 said:
Thank you for the responses. How do I get dm-verify off?
Click to expand...
Click to collapse
Here is SuperRoot without dm-verity: https://forum.xda-developers.com/ma...oot-mate-9-decrypt-data-t3569986/post71346651
Decrypting data is optional. If you don't wanna it, don't format data (skip linked steps)

5[Strogino said:
;74102755]Here is SuperRoot without dm-verity: https://forum.xda-developers.com/ma...oot-mate-9-decrypt-data-t3569986/post71346651
Decrypting data is optional. If you don't wanna it, don't format data (skip linked steps)
Click to expand...
Click to collapse
That's the guide I used but still can't get build.prop edited. My data is encrypted but system won't write while in Android and while in TWRP adb won't work and I can't copy the file over the old one using TWRP file explorer. Guess I'm giving up with root on this phone seems pointless to have done it with O on its way I just hope I can get it back to stock without breaking it to get the OTA (if it ever hits since I'm C567 and this thing hasn't had a damn update since April)

bhint15 said:
That's the guide I used but still can't get build.prop edited. My data is encrypted but system won't write while in Android and while in TWRP adb won't work and I can't copy the file over the old one using TWRP file explorer. Guess I'm giving up with root on this phone seems pointless to have done it with O on its way I just hope I can get it back to stock without breaking it to get the OTA (if it ever hits since I'm C567 and this thing hasn't had a damn update since April)
Click to expand...
Click to collapse
I can't say what happens on new ROMs, cause this guide slightly old. If you installed phh SuperRoot and phh superuser app from play store, you are able to use root. Check it in terminal.
If yes, try to mount system as read/write.
If yes, use Root Explorer and change system files.
Try reboot after that and notice everything works or not.

5[Strogino said:
;74138910]I can't say what happens on new ROMs, cause this guide slightly old. If you installed phh SuperRoot and phh superuser app from play store, you are able to use root. Check it in terminal.
If yes, try to mount system as read/write.
If yes, use Root Explorer and change system files.
Try reboot after that and notice everything works or not.
Click to expand...
Click to collapse
I have root. It prompts and works. Root explorer (or any other app that modified system) will not write to system, it errors out.
Other weird stuff too though, like Xposed installs in TWRP but doesn't work (says not installed)
I really only wanted root to unlock hotspot so it's not that big of deal.

Here is the solution to your problem my friends. Enjoy!
Works like a charm in Android 10 and later.
https://forum.xda-developers.com/t/script-mount-system-as-read-write-android-10.4240703/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

help: make twrp complete backup

hi,
Iam wondering how to make complete backup of xa2 ultra?
In twrp when i try to make it it interrupts on like 50% and gives error 255 (???)
how can i make my complete rom backup? possibly flashable later please?

maxis123 said:
hi,
Iam wondering how to make complete backup of xa2 ultra?
In twrp when i try to make it it interrupts on like 50% and gives error 255 (???)
how can i make my complete rom backup? possibly flashable later please?
Click to expand...
Click to collapse
Probably not enough storage.
Try backing up to an sd card.

hank you for response, but, I actually tryed to backup to SD card wich was empty and had enough space..
maybe some other ideas or suggestions please?

bought new sandisk 64gb card today,
stil getting error 255 and it wont make complete backup
btw, twrp says at beginning that it wants password to decrypt users, i never encrypted anytging on phone and dont know password.. can this be a problem maybe?? hmh

maxis123 said:
bought new sandisk 64gb card today,
stil getting error 255 and it wont make complete backup
btw, twrp says at beginning that it wants password to decrypt users, i never encrypted anytging on phone and dont know password.. can this be a problem maybe?? hmh
Click to expand...
Click to collapse
Do a quick check by go into your Root browser and look in these locations.
/storage/emulated
/data/system/
data/system_ce/
data/system_de/
data/misc/
data/misc_ce/
data/misc_de/
data/user/
data/user_ce/
data/user_de/
If you see any folder named 999 then you have parallel apps enabled on your device. TWRP in it's current form will not allow you to create a backup or restore a backup with parallel apps enabled.
Currently there is only one solution that I have found to be able to delete all of the 999 folders and that is to open a terminal emulator to each of these locations and remove the 999 folders individually. I have found a solution where you can delete the user ID and by doing so it removes all of the 999 folders and not only does it remove the folders they do not return once you reboot your device.

hi, thank You for answer and suggestion, unfortunately i just searched manually and with search in yotalcmd, and cant find any 999 folder.. huh?

how do i delete user id?

i have this lines from /twrp/backup/recovery.log
maybe it helps to figure a problem?
=> set selinux context: ubject_r:system_data_file:s0
failed to lookup tar policy for '/data/data' - 'f41841afcc75d652'
I:Error adding file '/data/data' to '/sdcard1/TWRP/BACKUPS/CQ3001CCRS/2021-07-12--02-26-16_lineage_discovery-userdebug_9_PQ3A190801002/data.ext4.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/sdcard1/TWRP/BACKUPS/CQ3001CCRS/2021-07-12--02-26-16_lineage_discovery-userdebug_9_PQ3A190801002/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.

Do you have multiple account apps?

I am sorry but I'm not sure what does that exactly mean, multiple account apps?

U know one app 2 accounts in that.
Dual apps etc

What are you backing up?

For a complete backup i dont think all partitions need to be selected lol
Only maybe
/system
/storage
Idk etc

just managed to make only /system backup. not sure what exactly is only system, its not a full rom backup? huh
is there any way to make flashable full rom backup at all?
also twrp gave me mesage cannot decrypt users.. heh??

It is your rom backup LMAO
Dont backup everything.
Nothing has space for your full phone.
You should disable.force encryption for that error to stop.

wow I didn't realise that that this is actually my full backup. So that means if I wipe phone now and flash this from twrp I will have all apps and everything again?
Also, please where and how can I force encryption stop?
Thank You so much for all help!

Backup /system /data /storage
Then u will have all apps and stuff.

just tryed it, on /data it interrupts and gives again error 255.. huh.
also please how to disable encryption?

also, is there any other way to make full rom backup except from twrp since this isnt working for me??

Delete your duplicate post.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In TWRP, go in "Advanced" menu => "Terminal" => Type: rm /data/extm -Rf
Then try to create a backup again now.

How To Guide Two ways to backup TB-J706F without unlocking bootloader.

For many users, unlocking the bootloader is unacceptable, because the tablet will stop updating via OTA. However, there are ways to save important partitions without unlocking them, which can be useful in case of damage during flashing or update.
1. The first method is described here. It works, I tested it. The Read button reads the partition to a file, the Load button writes from the image file to the partition.
Disadvantages: you can't copy the whole FS of the tablet at once, you have to copy the partitions one by one.
2. The second way goes here. It works on Linux, Windows, and MacOS. I checked it on the Live CD Mint 20.2. The tablet was recognized, the partition table was read and I successfully copied one boot partition.
Disadvantages: Difficult for Windows users.
Cons: You can copy selected partitions in any combination or the whole tablet at once.
---
It is very likely that these 2 methods will work for other models of tablets as well...

Were you able to use the --skip parameter with edl?
I used --skip=super,userdata the other day but it still backed up those partition (long wait for userdata )

MrCrayon said:
Were you able to use the --skip parameter with edl?
I used --skip=super,userdata the other day but it still backed up those partition (long wait for userdata )
Click to expand...
Click to collapse
Sorry, not tried this option. Will to try later.

MrCrayon said:
Were you able to use the --skip parameter with edl?
I used --skip=super,userdata the other day but it still backed up those partition (long wait for userdata )
Click to expand...
Click to collapse
Yes, you are right. This command not works, it made backup of all partitions. I made issue for author.

f1tm0t said:
Yes, you are right. This command not works, it made backup of all partitions. I made issue for author.
Click to expand...
Click to collapse
My PR has been merged, skipping should work now.

MrCrayon said:
My PR has been merged, skipping should work now.
Click to expand...
Click to collapse
Yes, my issue is same. Can't try this just now, so sad.

Tested fixed version some days ago - now --skip option works fine. Dump of all partitions in one folder (except biggest userdata:
Spoiler: Scr
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I have a question, what about userdata when it is encrypted?
How to get/set the key from the TEE?
Or are the chinese ROMs are unencrypted?
Best regards

CryptMan said:
I have a question, what about userdata when it is encrypted?
Click to expand...
Click to collapse
My userdata permanently unencrypted with no-verity-opt-encrypt. TWRP says "Decrypted with default password"

f1tm0t said:
For many users, unlocking the bootloader is unacceptable, because the tablet will stop updating via OTA. However, there are ways to save important partitions without unlocking them, which can be useful in case of damage during flashing or update.
1. The first method is described here. It works, I tested it. The Read button reads the partition to a file, the Load button writes from the image file to the partition.
Disadvantages: you can't copy the whole FS of the tablet at once, you have to copy the partitions one by one.
2. The second way goes here. It works on Linux, Windows, and MacOS. I checked it on the Live CD Mint 20.2. The tablet was recognized, the partition table was read and I successfully copied one boot partition.
Disadvantages: Difficult for Windows users.
Cons: You can copy selected partitions in any combination or the whole tablet at once.
---
It is very likely that these 2 methods will work for other models of tablets as well...
Click to expand...
Click to collapse
Hi mate,
I've used the method #1 that you linked, to take a full backup of my pad pro (thanks for sharing this, helped a lot since I really wanted to have a backup to restore to out-of-box if needed in the future).
I ended up with 91 partitions saved, but it seems a lot of these partitions would never really get touched or changed, no matter what you do to your tablet (in terms of rooting, custom roms etc), so I wanted to ask you if you could give a break down of what you think are the essential ones that would need to be restored to revert back to "out of the box". For example. I suspect a lot of the partitions house data such as serials, mac addresses, component firmware etc, etc, and such-like which would not need to be written back to the device during a restore.
I'm attaching a pdf I made showing all the partitions available through use of QFIL, if you could reference it in any advice/help with your answer I would be grateful. Thanks

The firmware writes to different sections, in particular to frp and frpinfo and others. If you want to get the tablet back to the same state as you backed it up, you must have a copy of all partitions.
For a regular backup you don't need a copy of all partitions, just the ones you need.
Besides, I recommend to have backups of those partitions that are not in the firmware in case the internal memory fails or human errors (like ticking "Erase all before download" in QFil settings)

f1tm0t said:
The firmware writes to different sections, in particular to frp and frpinfo and others. If you want to get the tablet back to the same state as you backed it up, you must have a copy of all partitions.
For a regular backup you don't need a copy of all partitions, just the ones you need.
Besides, I recommend to have backups of those partitions that are not in the firmware in case the internal memory fails or human errors (like ticking "Erase all before download" in QFil settings)
Click to expand...
Click to collapse
thanks, great explanation, i appreciate it

f1tm0t said:
1. The first method is described here. It works, I tested it. The Read button reads the partition to a file, the Load button writes from the image file to the partition.
Disadvantages: you can't copy the whole FS of the tablet at once, you have to copy the partitions one by one.
Click to expand...
Click to collapse
Hi @f1tm0t ,
i'm going to use method 1), can you please share me how to get the firehose that was mentioned in that article?
Thank you!

khanhj said:
how to get the firehose
Click to expand...
Click to collapse
You need to download rom (firmware) for your device, unzip it in separate folder and point to folder from QPST.

@f1tm0t thank you for your reply.
The reseller send it (TB-J716F) to me with custom global rom and unlock bootloader, so i follow the guide to flash stock Chinese rom and lock bootloader, it worked but widevine L3. Then i put the update.zip to push it through version 14.0.127 with locked bootloader but still widevine L3.
I'm going to backup 5 important partitions: fpinfo, persist, uefivarstore, secdata, frp, then redo all processes again.
BTW do you have any idea what is this: https://github.com/zenlty/Qualcomm-Firehose

in the extracted ROM (ZUI 12) there is 2 firehose which one should i use?

khanhj said:
which one should i use?
Click to expand...
Click to collapse
You must to use prog_firehose_ddr.elf
khanhj said:
BTW do you have any idea what is this: https://github.com/zenlty/Qualcomm-Firehose
Click to expand...
Click to collapse
Sometimes I use this with Linux: https://github.com/bkerler/edl

f1tm0t said:
You must to use prog_firehose_ddr.elf
Sometimes I use this with Linux: https://github.com/bkerler/edl
Click to expand...
Click to collapse
i tried to flash ROM ZUI 12 now i got this
Can you advise what should i do?

As my expirience say - you need unlock bootloader.

f1tm0t said:
As my expirience say - you need unlock bootloader.
Click to expand...
Click to collapse
yes but i dont know how to unlock bootloader at this state.
Thank you for your replies!
--
Edit: oh well, i flash the ROM ZUI 12 again, stick on option Reset State machine and Delete before download, my device able to boot up again to ZUI with unlocked bootloader.
I hope anyone had the same issue can fix it.

Question How to make full pixel 7 backup to image ?

I would like to make a full backup of the system before I update so that I can restore the full system with all applications and their settings in case the update fails.

You'll need TWRP afaik for a full nandroid backup. Which doesn't exist for the P7P I guess.
But Google backup does a pretty good job, excluding the settings. You could also try Migrate or Swift backup, but I don't think full images are possible like in the older days.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

m3ath said:
View attachment 5811723
Click to expand...
Click to collapse
Does this take a full image backup?

krakout said:
Does this take a full image backup?
Click to expand...
Click to collapse
I didn't try it

m3ath said:
I didn't try it
Click to expand...
Click to collapse
As far as I know this just applies to regular file transfer to a PC via USB, it does nothing special and nothing of the sort that OP asked...

I would like to use TWRP but it doesn't seem to work on Pixel 7 yet, I'm looking for something that does just that.

daveyyy said:
I would like to use TWRP but it doesn't seem to work on Pixel 7 yet, I'm looking for something that does just that.
Click to expand...
Click to collapse
Your best bet is to use Swift Backup for your apps/data, backed up to Drive or some other cloud Storage and then after the reset, let Google restore your G-Apps and Phone/Messages/WiFi points, etc while you restore your apps from Swift

krakout said:
Does this take a full image backup?
Click to expand...
Click to collapse
Its for an adb backup, which is pretty similar to what gooble backs up, and respects application manifest flags specifying if an application's data should be backed up or not.

96carboard said:
Its for an adb backup, which is pretty similar to what gooble backs up, and respects application manifest flags specifying if an application's data should be backed up or not.
Click to expand...
Click to collapse
Cheers, googling for it actually gave me results for mtp transfers. Gotta Google me some adb then...

Use DD

Lossyx said:
Use DD
Click to expand...
Click to collapse
What is DD ?

IIRC (this is a normal Linux command, but the method for obtaining an Android backup is pretty old) it is used to get a binary image of your selected partition. Someone correct me if I'm wrong.

@krakout: that's correct, dd is used to create 1:1 bit per bit copies of partitions. When the device is encrypted the issue is that the 1:1 copy contains the encryption. When you do a new clean setup of your phone the encryption key is reset, which will result in the backups not being usable ... this means it should work on non-encrypted devices, but restoring full partitions has always been a risky business.
I do change phones quite often (oder reflash the existing ones ), my process for backup and restore is (you need to be rooted for #1):
Backup/Restore apps and app data using Swift Backup (or free tools like OAndXBackup) - sadly this does not work for all apps (mainly security critical ones like banking apps), but still for most
Backup and restore internal storage using ADB, either with Total/Double Commander and a plugin or using a python tool - connecting the phone via USB. Transfer speed is quite high (depending on phone and PC ~30-150Mbps). Positive here is that you automatically have a full backup of your phone on a PC
use Android native backup/restore for settings

@s3axel thanks for the confirmation and the write up! Seems like indeed these days Swift is probably the best option.
Damn I got excited when you mentioned the TC plugin, thought it was something for the Android version! Not using it on my PC (love my Directory Opus setup!) but I think I'm gonna try this

While it is technically possible to do a "dd" style backup by stopping the zygote service and dd'ing it to something like a USB stick, it won't be useful because the cryptographic keys tied to the data will not be accessible.
Despite being recommended by some people, I would caution against "swift" backup software. This is something you are giving an unprecedented level of access to (for example, it could access the internet, even without internet permission!) and therefore needs to comply with the highest level of trust and security, none of which can be guaranteed by closed source software written by someone you can't even hold accountable.
Instead, I would suggest Neo Backup: https://github.com/NeoApplications/Neo-Backup (also available on F-Droid). This is OPEN SOURCE software, and you are therefore able to read every single line of code to verify that it is actually safe to use.
Others I see have suggested a TWRP backup. Believe it or not, this kind of a backup would actually be very similar to what you would achieve with Neo-Backup. However, the old "nandroid" backup is basically a historical relic -- like a "dd" backup, and didn't last much beyond the very very early solutions since it requires just so much storage space, and because its technically impossible without an external storage device (like an SD card) that is LARGER than the device's total internal storage. Even the name "nandroid" = "nand" + "android". Well direct usage of nand memory is not something you see any more, that was replaced by eMMC, which also was replaced by UFS!

Many thanks for your reply, indeed it is all about trust and I agree with you on that you never know what a software will or can do. However this also applies to the so-called open source software because you (or, more aptly: I as a user) never know whether the distributed binary is really using only the published code parts or something on top....

s3axel said:
Many thanks for your reply, indeed it is all about trust and I agree with you on that you never know what a software will or can do. However this also applies to the so-called open source software because you (or, more aptly: I as a user) never know whether the distributed binary is really using only the published code parts or something on top....
Click to expand...
Click to collapse
F-Droid is a repository for open source software, and they build the open source software themselves (as in the repository, not the software developer), and signed with F-Droid keys. They provide the exact source code archive used to produce the binary, so you know *exactly* what source code was used to build it.
Alternatively, you have the option to build from source yourself. Its not as complicated of a task as it seems as first.

Many thanks and no offense intended ... I'll have a closer look at Neo Backup for the future...

@s3axel wow, how come I missed this solution! From a cursory look, it seems awesome!
Pity it doesn't support backup services, but at least I can use MiXplorer as a document provider to pick up my NAS as a destination...