Related
Hello everyone, I bought an LG L70 Dual D325F which was soft-bricked hoping it as to be easily fixed via flashing the stock firmware, but to my great surprise, I was unable to access the download mode, I was facing the "DemiGod Crash Handler : DBI Err Fatal!"
{
"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"
}
Then I tried this tutorial, but I after following the thread, the device switch to Qualcomm HS-USB QDLoader 9008, thus I started searching a solution, then I found out about this method, which involved the use of an SD Card, thus it did worked out, and I was able to boot to download mode in order to flash the firmware, but the firmware flashing was getting stuck and then reset while displaying 'ASSERT' in Red at 7%, sometimes at 15% and the maximum I did reach was 33%, before restarting again.
Then after spending hours on google, I found out that the it is normal and that I should keep forcing until 100%, but after my attempt to 33%, the process wouldn't past 7%, thus I googled for another method then I came across a method involving BoardDiag 3.99, thus when I tried it out, but during the test, it EMMC test fails and output the following:
Note: I used the other driver, this was just to show the error which was being output.
Despite that, I did continue with the method and flash the imgs. Then I decided to look inside the files and found out the partition.txt was incorrect, thus I did calculate and created my own using the files from my stock extracted firmware. But still it didn't worked out, thus after I googled, I came across a tutorial which was meant for LG G3 unbrick using BoardDiag, and it the tutorial, the guy mentioned that use the option erase and then switch it back to Read/Write, and it should fix the error, but it didn't worked out. and the EMMC partition was completely wiped. then check I checked the rawprogram xml in BoardDiag, It looked like it was incorrect, but I wasn't able to edit it properly, so I gave up on this one.
Then the next day, I googled and came across a tutorial from XDA that shows how to fix an LG L7 P715, so I started following the tutorial as from Step 4, but I was unable to continue as the application was search for the Sahara XML, I wasn't able to get my hands on. After some research I found out the provided files wasn't compatible with my device, thus I finally got my hands on some of the files.
1. MPRG8x10.hex (It is the eMMC programmer file to help download the bootloader into eMMC, and I guess it can be used with all Snapdragon 200 MSM8x10 processor. And I've already got this file somehow).
2. 8x10_msimage.mbn (It is the bootloader image file and specific to the phone. I wasn't able to get the file, because I wasn't able to determine the proper bootloader file for the device from the stock firmware.)
3. Raw XML and Patch XML files (These XML files contain the partition details of phone. And I don't have these two. And I was unable to even a edit the files properly as I wasn't able to exactly understand what was going on, so I gave up on this one.).
Then the next day, I tried again using the SD Card method, but once the SD Card is inserted, the device shows the Demi-God Crash error. Thus when I hooked it up to my computer, I saw the EMMC as a removable partition but I was unable to format it, thus I tried writing the partition table (PrimaryGPT) to the device, but no success. Then I download a full dump for the D325 and wrote it to the EMMC, but still fails to boot as the EMMC is clean once I unplug it and plug it again. Thus when I hooked up the SD Card through a card reader to my device, it shows that the SD Card was partitioned as a regular emmc for a phone to boot, I did try to to backup the partition table and then restore it to the EMMC, but still in vain. Then I tried to write the files manually using linux to partitions manually, including the system partition, which I did merge the different bin files to one img and then flash it, I took about 10min to fully write it. But still it didn't boot. Well I'm stuck here (am currently trying to write the full dump to the SD card and try to boot of it, if it does boot). I hope that someone will be able to help me out to fix this issue. Thanks in Advance!
Hello,
As a Senior Member you should be able to navigate the site and find the answers you are looking for.
XDA Assist is to help new members navigate the site.
Please have a look at the 2 sticky threads at the top of XDA Assist if you have any further questions.
Thread closed.
Thanks,
Sloth
Stupid question,
I normally use root essentials to make a system backup but I think with op6 it will not backup al the required files anymore I think.
So I want to make the backup true twrp but can someone list the files to backup. As there are also vendor partition listed. So please let me know what to backup exactly to make the correct backup.
Thanks in advance.
Regards ysco..
Bump,
Anyone?
I think you need to backup all partitions.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-restore-backup-twrp-t3807546
Bradden1 said:
I think you need to backup all partitions.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-restore-backup-twrp-t3807546
Click to expand...
Click to collapse
For a successful nandroid you need following partitions:
boot
system image
vendor image (not sure, if image is really needed, haven´t tested) yet
data
Separately an efs-backup is highly recommended which should be copied to an external storage.
Flying Fox said:
For a successful nandroid you need following partitions:
boot
system image
vendor image (not sure, if image is really needed, haven´t tested) yet
data
Separately an efs-backup is highly recommended which should be copied to an external storage.
Click to expand...
Click to collapse
ysco said:
Stupid question,
I normally use root essentials to make a system backup but I think with op6 it will not backup al the required files anymore I think.
So I want to make the backup true twrp but can someone list the files to backup. As there are also vendor partition listed. So please let me know what to backup exactly to make the correct backup.
Thanks in advance.
Regards ysco..
Click to expand...
Click to collapse
the reply is not correct you explicitly don't need exactly those two image partitions to backup because they remain stock intact at all times, they only make your backup huge, up to 14GB instead of only 7-9GB once unchecking them.
of course as always you HAVE TO backup system and vendor, just not the system and vendor images, they serve to keep a clean stock
system available to recover from a soft brick, you can test that by re-locking and re-unlocking the bootloader and/or by formating all partitions
including user data on both slots. it will boot directly into a clean system (setup wizzard) like on first unboxing and this what you boot into then is exactly vendor and system image which remains untouched no matter what you do (except intentionally killing everything with brute force which is not even so easy)
{
"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 shall attach a screenshot to illustrate and much more important ist that if you ever opened parallel apps settings you'd have to delete all
999 folders in root > data > (all 3 misc + all 3 system + both user) folders else you get a 255 error.
Thank you.. i did wonder whether backing up image files was the right way.
magnamentis said:
the reply is not correct you explicitly don't need exactly those two image partitions to backup because they remain stock intact at all times, they only make your backup huge, up to 14GB instead of only 7-9GB once unchecking them.
of course as always you HAVE TO backup system and vendor, just not the system and vendor images, they serve to keep a clean stock
system available to recover from a soft brick, you can test that by re-locking and re-unlocking the bootloader and/or by formating all partitions
including user data on both slots. it will boot directly into a clean system (setup wizzard) like on first unboxing and this what you boot into then is exactly vendor and system image which remains untouched no matter what you do (except intentionally killing everything with brute force which is not even so easy)
i shall attach a screenshot to illustrate and much more important ist that if you ever opened parallel apps settings you'd have to delete all
999 folders in root > data > (all 3 misc + all 3 system + both user) folders else you get a 255 error.
Click to expand...
Click to collapse
That's absolutely correct. I was not precise enough in my post. I recommend a backup of the system image, at least I do it so, because I can not know in advance, whether later a factory set or a clean install will be necessary. So it does not bother me that the backup is a bit bigger then. It does not hurt and costs nothing.
As I said, the thing is, if I wipe system, then I need to flash it again if I did not back up system image - that's my experience.
Or am I wrong; I like to be corrected, especially your knowledge interests me.
magnamentis said:
the reply is not correct you explicitly don't need exactly those two image partitions to backup because they remain stock intact at all times, they only make your backup huge, up to 14GB instead of only 7-9GB once unchecking them.
of course as always you HAVE TO backup system and vendor, just not the system and vendor images, they serve to keep a clean stock
system available to recover from a soft brick, you can test that by re-locking and re-unlocking the bootloader and/or by formating all partitions
including user data on both slots. it will boot directly into a clean system (setup wizzard) like on first unboxing and this what you boot into then is exactly vendor and system image which remains untouched no matter what you do (except intentionally killing everything with brute force which is not even so easy)
i shall attach a screenshot to illustrate and much more important ist that if you ever opened parallel apps settings you'd have to delete all
999 folders in root > data > (all 3 misc + all 3 system + both user) folders else you get a 255 error.
Click to expand...
Click to collapse
why i can not find 999 folders from root ? even i have opened parallel apps
This is not totally a guide! It's only meant for experienced users!
Besides, this topic is never meant for Nokia 3.1 Plus C (TA-1124 RHD), as Nokia 3.1 Plus C uses Qualcomm Snapdragon processor.
Click to expand...
Click to collapse
WARNING!
Downgrade Nokia 3.1 Plus is pretty dangerous!
If you didn't make any backup before, you may break your phone!
During partition backup, you'll need to backup following partitions:
proinfo, nvram, nvdata, protect1, protect2 - and most importantly, fdp!
I needn't to mention about proinfo, nvram, protect1 and protect2. Excluding fdp, all these partitions could be recovered by utilizing MTK-SU.
Let me make brief introduce to FDP partition. On Security Patch Level 0x8 based device (you needn't to care about what it means), there's an extra partition called fdp, might related to remote lockdown feature for anti-theft AFAIK(implemented by FIH Mobile, but unused by HMD).
During SP Flash Tool flashing procedure, this partition is easily get broken, so make sure it's backed up before doing any flashing attempt. This partition cannot be reproduced with any known free method or borrowed from other devices, so once it's damaged and you just don't have backup, your phone will stuck at Magenta State (like picture shown below) and now damaged and not recoverable for free. There's some mysterious GSM tool that capable to fix broken FDP but cost a lot, which unsuitable to explain details here.
{
"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"
}
This is undocumented on source.android.com , definitely something FIH Mobile made themselves. In some cases, it's displayed as " Your device is corrupt. It can't be trusted and please contact support. ".
Besides of that, Nokia 3.1 Plus is not that easy to be downgraded without unlocked bootloader by yourself. To prevent of FRP lock, you should perform regular factory reset at Settings before you downgrade. The only known firmware that acceptable by MTK SP Flash Tool 5.1824 is ROO-2230-0-00WW-B02 on my FIH-Firmware Site. But even that's flashed, the phone still cannot boot properly and will get red state due to system failed dm-verity check when flashed via SP Flash Tool instead of fastboot. However, it could still be possible to boot the phone to recovery and sideload a full OTA. As I don't have bootloader locked Nokia 3.1 Plus right away and limited efforts, cannot write a detailed downgrade guide.
Here's a known full OTA link newer than ROO-2230-0-00WW-B02: https://android.googleapis.com/pack.../0f83ed888b1a5b17d31bb576b9a629d79d097df4.zip
Build version: ROO-225K-0-00WW-B03
Security Patch Level: August 5th, 2019
So, it should be vulnerable to MTK-SU.
Anyone should archive this to somewhere.
Now let's talk about the main topic - internal Android 10 build.
FIH already tested Nokia 3.1 Plus Android 10 internal pretty early (This build for example, October 5th, 2019), but I'm not sure about it's stability. We only made simple test on a Nokia 3.1 Plus TA-1117 (Which is Nokia 3.1 Plus sold in China) and it runs nicely.
Just like Nokia 5.1 Plus, there's no applicable internal OTA packages, instead we only provide full dump. If you don't have unlocked bootloader, you have to install them via MTK-SU leak. The procedure is almost identical to Nokia 5.1 Plus as you'll need to write vbmeta partition individually. As Nokia 3.1 Plus lacks cam_vpu1, cam_vpu2, cam_vpu3 partitions, just ignore errors during flashing cam_vpu1, cam_vpu2, cam_vpu3 partitions.
For some paranoid reason, FIH didn't use 00WW_3_120 as I would expect (they wrote ROO-3120-0-00WW-B02 in systeminfo partition), instead they use 00WW_4_120 in About phone page.
DL: https://www.androidfilehost.com/?fid=4349826312261774372
SHA256: 3140e0ee26f3a23ee479eb4846baaa28a9166c420e76e8e2424a4c223a47682e
Reserved
Reserved #2
sir how to to it 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.
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...