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...
Related
This Guide is simple and is straight the point, but is helpful and may come in handy for those who experience a hard-bricked phone or missing file in your phone like I did. Basically, nandroid is not a FULL backup, it only backs up your system, data, sd-secure, and boot partitions. A low level backup does every partition on your phone (even low level ones) and puts it on your sdcard. Now note that a full backup can create quite a large backup size total.
Credits to XDA user closeone for teaching me how to do this:
In a terminal emulator app perform this command in your terminal:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0.img
(Quoted from closeone)
That command is a disk to file command with the parameter if (Input file) of mmcblk0 (the entire device) and the parameter of (output file) to the SD Card as a file called mmcblk0.img
Click to expand...
Click to collapse
the "0" basically says "the whole phone" and as such backs it up. This will back up your radios, system, data, and every other partition you didnt even know existed in your phone.
I have been around android for a long time, but I did not know this, I hope this helps someone.
A couple of things you should mention: you're not responsible for any issues which may or may not arise or user errors.
Secondly, if the if= and the of= get reversed, well it would overwrite the phone's info, at least to the point DD can't run or encounters an error and stops.
Sent from my LG-P999 using xda premium
How do you restore this back to the device?
and if this restores without an issue, this might be a solution to the infamous ICS Brick bug in Samsung Galaxy Note and Galaxy SII.
Reverse the if= and the of= "if" is input file "of" output file. Think of this as being similar to making an ISO of a CD or DVD. And depending on what utilities are available and how the device is recognized, it could be a solution. If the device is recognized by a program which can flash .img files, for example for my phone we have nvflash which can. CWM can also be scripted to write them.
Sent from my LG-P999 using xda premium
Волк said:
Reverse the if= and the of= "if" is input file "of" output file. Think of this as being similar to making an ISO of a CD or DVD. And depending on what utilities are available and how the device is recognized, it could be a solution. If the device is recognized by a program which can flash .img files, for example for my phone we have nvflash which can. CWM can also be scripted to write them.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I am not sure about the reverse... a working file system needs to be remounted as read+write before it can be overwritten. I am guessing this COULD be done in recovery mode using adb shell but still quite risky. If anything, I have a feeling it can hardbrick the device unless the boot and recovery partitions are left untouched. Comments?
Thank you, this is what I was looking for!
I want to encrypt my device, thus I won´t be able to backup with Clockworkmod afterwards.
Does this command also backup /sdcard1? That would be odd somehow, because you cannot write the backup to a partition you are just about to backup itself...
How can I issue this command with adb?
I would like to connect my device to my Linux workstation, use adb to issue the backup command and write the backup to my local harddrive. How could I do that with adb?
Best regards
papperlapapp said:
Thank you, this is what I was looking for!
I want to encrypt my device, thus I won´t be able to backup with Clockworkmod afterwards.
Does this command also backup /sdcard1? That would be odd somehow, because you cannot write the backup to a partition you are just about to backup itself...
How can I issue this command with adb?
I would like to connect my device to my Linux workstation, use adb to issue the backup command and write the backup to my local harddrive. How could I do that with adb?
Best regards
Click to expand...
Click to collapse
Wow talk about a blast from the past lol. Honestly man I left the dev scene for about a good year and some months up until.... two days ago lol, so I'm rusty as all get out. I'd have to get back on my stuff to answer it for you to be honest. Even at the time of my creating this, I didn't necessarily KNOW how to do it, closeone just taught me how and I felt like this could have possibly saved someone from a potentially disastrous encounter, I wasn't knowledgeable enough to tell you much is what I'm trying to say.
I have a generic rooted tablet and im unable to find a custom recovery and i want to send my rom to a dev who can or want to made cwm/twrp for me, so this is my question: is it a safe way to copy my actual rom? Im asking that cuz im scared to brick my tablet. Thanks
acuicultor said:
I have a generic rooted tablet and im unable to find a custom recovery and i want to send my rom to a dev who can or want to made cwm/twrp for me, so this is my question: is it a safe way to copy my actual rom? Im asking that cuz im scared to brick my tablet. Thanks
Click to expand...
Click to collapse
Is the tablet rooted? I might be able to look at it, give me a PM.
Sent from my HTC One using xda app-developers app
{
"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"
}
These are the specs. Thanks
Is this possible to do without a rooted phone? What about via adb shell or as an external device?
http://forum.xda-developers.com/showthread.php?t=1818321 showed more advance function for low level backup.
would you please explain how you reach the point where you can run the dd command?
awambawamb said:
would you please explain how you reach the point where you can run the dd command?
Click to expand...
Click to collapse
dd is a Linux command, so you should do adb shell from your Windows Command Prompt. Obviously abd should be installed beforehand.
http://www.theandroidsoul.com/how-to-install-adb-on-windows-full-guide/
Well, I am beginner, if this is not what you asked, sorry in advance
I need mmcblk0.img from someone please for htc m8s if anyone has ir can get a hold of cheers ?
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
Hello everyone today I bring to the table a constantly updated guide.
In my free time I will add to this guide my many methods of creating a stock os out of Nubias OS whilst retaining nubias gaming suite,lights, etc. I know many feel cheated on antutu scores because Nubia presented 510k and most people couldnt even attain 450k on a RM3S.
Well the ones I have worked on easily hits 515k in the max optimal conditions, whilst hitting 505k-510k in concurrent runs or runs in regular conditions. YES the phone thermal throttles, eventually leaving a reduced score of 450k-470k, HOWEVER that is higher than the current reported average of 435k.
Todays method shall be called Method #1
METHOD #1
REMOVE WOODPECKER- Nubias tracker
Background: it logs information from your phone including sensitive personal app information. This program (binary) runs 24/7 and dumps logs to root and to internal storage. If youre connected to internet data or wifi, it will connect to nubias servers amd start dumping information, I have reproducible evidence through a packet dumper.
This program runs from the moment you first boot your phone till when its broken or out of battery. Unless removed. Yes I know you can opt-out but that is simply a facade, it ALWAYS runs anyway.
Removal- a10-a11
1.Obtain a root file explorer or use twrp to perform the steps below
2. Using your explorer navigate to root and put in the search wood
3.Wait for it to load the files and remove them ALL, delete them, shamwow them.
4. If there are files that arent removable change their permissions to none, these are created by woodpecker on boot and will be gone when done.
5.Repeat 2, 3, and 4 but use Wood (to be clear perform the search with a capital W, it matters for some explorers.)
5. Open your init.rom.rc it is located in the root directory remove the lines that are associated with woodpecker. You can remove freezerd lines as well for less agressive ram management but will require additional steps.
6.Enter your vendor build.prop and change woodpeckers line to false, it is the only line containing the word woodpecker.
7.Reboot and perform a search, you will see no woodpecker files show up.
8.System ram usage will decrease by an average of 200mb, Phone temps idle lower(by a very small amount admittably), network usage will decrease.
For those thinking is this illegal? Unfortunately not, Nubia is operating on the same legal grounds any other company data harvesting is. Feel free to research.
A9- Same as above but woodpeckers permissions must be set to none, then after a reboot it is deletable.
Done.
Method #2
I really recommend reinstalling the game launcher and home launcher as user apps as well, or modifying your preferred launchers code to call nubias recents(attached to nubia launcher)but it will require the nubia launcher installed ideally as a user app not system user 0. This is the current only working method to use a custom launcher with RECENTS on Nubia A11 OS I will update this more indepth when I next log in.
6/01/2021
Method #3 A10-A11 (Android 10 & 11)
Tcpdump has been added as a binary in all RM3 & 3S A11 updates and some A10 it is highly recommended to remove permissions, and delete the bin. It will be located in your system bins. You can also search for it with tcpdump entered in a root explorer.
I will continue to add more in my free time!
Wouldn't removing the woodpecker app do the trick?
Interested on this. However, I'm unable to find init.rom.c even using search. Could you give what's the partition name / folder where it is located?
danishajaz said:
Wouldn't removing the woodpecker app do the trick?
Click to expand...
Click to collapse
Nope, its simply there to fool you, regardless theres a woodpecker in the system bin.
leipnacht said:
Interested on this. However, I'm unable to find init.rom.c even using search. Could you give what's the partition name / folder where it is located?
Click to expand...
Click to collapse
What rom version are you using? If you cant locate the init file that creates it on boot, maybe youre on A9, for A9 removing the file in system bin should be enough from my memory but I dont have an A9 available to test it out right now, you could always look through the inits there arent many, youll find many more things that you may want to change as well. Anyways let me know which rom youre running and ill be glad to debug further
Updated for Tcpdump removal, nubia secretly snuck this binary into their rom, there is absolutely no reason at all they should have a binary capable of sniffing ALL OF YOUR INTERNET TRAFFIC preinstalled.
SilentDevGuy said:
What rom version are you using? If you cant locate the init file that creates it on boot, maybe youre on A9, for A9 removing the file in system bin should be enough from my memory but I dont have an A9 available to test it out right now, you could always look through the inits there arent many, youll find many more things that you may want to change as well. Anyways let me know which rom youre running and ill be glad to debug further
Click to expand...
Click to collapse
This was last March 2021 so it's probably A9.
I'm using the CN ROM and it's on Android 11 now and has root access by Magisk
I can now see the init.rom.c file
What's the name of file explorer you are using?
I tried deleting using FX File Explorer it says can't delete, file is read-only
Also I tried deleting using adb shell and even used su root, can't delete it
{
"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"
}
RED MAGIC 3
ROOTED ANDROID 11 CHINA ROM
USE
MIXPLORER,,APK
GO TO ROOT FOLDER SEARCH TYPE
''WOOD''
GO TO THE LOCATION OPEN FOLDER OR FILE
AND
SLECT FILE PROPERTY
CHANGE PERMISSION
644 rw-r-r
THEN DELETE
{
"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"
}
Swift Backup can backup your important data in minutes! Its quick, efficient and boasts an elegant design for a refreshing backup experience.
- Google Play.
I tried for Call backups and it works great....... Now thinking to make my apps backup too.
I am using this backup app since long time and it is really a very good reliable app.
Hi... can anyone tell me how to restore if i have backup from Poco F3 and want to restore on K30 Pro Zoom ?
and the devices already rooted.
Because last time, i cant restore even already copy the backup folder to new device.,.. Swift backup app cannot found my backup. (offcourse with same google account)
On LineageOS 18.1 with Magisk I'm not able to backup and restore any App data
The Backup process says "Complete", but when I look at the SwiftLogger I see the following error
ApkReader: Output for file /storage/emulated/0/SwiftbBackup/... [ERROR: dump failed because assets could not be loaded]
Click to expand...
Click to collapse
That is probably the reason why it won't restore.
Any idea what to do or where to look?
Ps: I'm just using the local version for now.
Hi everybody,
I switched to Swift Backup from Titanium Backup, and I got lost in the labyrinth of Swift's interface. I took a backup of all my apps, then a nandroid backup with TWRP and then I switched to a different rom.
In this operation, I forgot to back up Swift's password (I wish it could be disabled), so now I'm wondering: is there a way to recover the password for Swift from the nandroid backup? Can it be found in /data/data for example?
How do I change the backup location on this Swift app ?
How do I pick a specific folder ?
LucasBS1 said:
How do I change the backup location on this Swift app ?
How do I pick a specific folder ?
Click to expand...
Click to collapse
Anyone ?
LucasBS1 said:
Anyone ?
Click to expand...
Click to collapse
If you don't know the answer, read the FAQ.
Can I use a custom folder location for my backups on the device or in cloud?
kubalav said:
If you don't know the answer, read the FAQ.
Can I use a custom folder location for my backups on the device or in cloud?
Click to expand...
Click to collapse
Oh... There is a FAQ
Wasn't even finding an official forum
Thanks
A terrible directive for an advanced app. They certainly won't see my money
I'm on the Pixel 7 Pro and finally had the occasion of needing to restore my wallpaper; and it confirmed what I had feared when initially looking at it from the app -- while it was the correct picture/image, it ended up being off-center and zoomed without being able to correct it.
Anyone else having this issue? Know of a workaround or explanation?
simplepinoi177 said:
while it was the correct picture/image, it ended up being off-center and zoomed without being able to correct it.
Click to expand...
Click to collapse
The explanation is simple: backup apps are unreliable. They only have different limitations. Swift is no exception, as I'm finding many.
This is how you may investigate:
[Root]/data/system/users/0/wallpaper_info.xml
This file carries the wallpaper settings.
I would compare this file before and after customizing the wallpaper to memorize the differences.
Then I would back it up and immediately restore it using Swift
If there is a difference between before and after the backup, you found the cause.
Since I grew tired of relying on these backup apps, I make manual copies of these files you will see around these folders, the folders beying /data/system/, and /data/system/users/0
LucasBS1 said:
A terrible directive for an advanced app. They certainly won't see my money
Click to expand...
Click to collapse
Besides the inability to specify the backup dir, I found another problem: Swift encrypts everything.
On titanium, one can extract the app and the data from the ZIPs. Here, I can't.
Moreover, by using apps like Solid Explorer I can make a copy of other apps, with it's clear name, icon, and ready to install (and on a more organized manner).
The only advantage over Titanium is the backup of permissions, but being that the only one, I'd remove the "best app to backup" from the title of this thread.
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.